1. http://www.fi-ware.eu http://www.fi-ppp.eu FI-WARE Testbed Overview Stefano De Panfilis – FI-WARE Testbed Responsible http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Quick_FI-WARE_tour

2. FI-WARE Generic Enablers 1  The FI-WARE Platform comprises a set of technological “Generic Enablers” which are considered general purpose and common to almost any “usage areas”  Generic Enablers will provide open interfaces: To Application Developers (APIs) To support interoperability with other GEs (need for replacement) Usage area projects under the PPP

3. Basic principles about FI-WARE GEs  GE specifications are open (public and royalty-free)  Any implementation of a Generic Enabler (GE) is made up of a set of components which together supports a concrete set of Functions and APIs that are in compliance with open specifications published for that GE  There might be multiple compliant implementations of a given GE  The FI-WARE project will deliver a reference implementation of FI-WARE GEs: Based upon results of previous R&D projects Licensed with no costs within the FI-PPP program Lincesed under FRAND conditions elsewhere 2

4. The FI-WARE Testbed  The FI-WARE Testbed is a case example of a FI-WARE Instance. It: Allows Use Case projects and third parties to run and test Future Internet Applications based on FI-WARE GEs Is aimed to be complete, in the sense that it will comprise reference implementations of all GEs defined in the FI-WARE Architecture It is operated under central control and be accessible from a dedicated website.  FI-WARE partners will provide support to UC projects in deploying their conceptual prototypes on top of the FI-WARE Testbed 3

5. Tesbed V1 Status  Status 29 GEIs deployed (http://catalogue.fi-ware.eu/) out of 31 planned(http://catalogue.fi-ware.eu/  Usage: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGh LQWtNai1jeGN5UnJMeEdxZ0E#gid=0 https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGh LQWtNai1jeGN5UnJMeEdxZ0E#gid=0 “D” = 12 › 2 overlaps: › VM allocation (safecity and smartagrifood) › ServiceRegistry (finest and smartagrifood) › IM PoC will not be based on “D” › FINSENY did not commit to have PoC in their DoW “U” = 61 “E” = 100

6. Major Achievements  Testbed V1 up and running  Fruitfull collaboration between FI-WARE and UC projects Testbed “First Impression” UC project survey and “Usage Questionnaire” › All projects answered › Quite detailed comments › Extremely useful, in some cases already implemented

7. Roadmap to Testbed V2 (FI-WARE Technical Roadmap) (FI-WARE Technical Roadmap  Migrate all GEIs on top of FI-WARE Cloud  Establishment of two environments: “stable” and “development”  Testbed V2 will have: 3 new GEIs for Apps 3 new GEIs for Cloud 6 new GEIs for IoT 2 new GEIs for Data 3 new GEIs for I2ND 5 new GEIs for Security  Deployment of Testbed V2 according to: 31 Jul 2013  Testbed V2 up-and-running

8. High-level Architecture Red.es

9. Physical Distribution of the Platform FI-WARE meeting8... Internet Phase 2 Platform Router firewall Management network Each Server: 8 cores 128 Gb RAM 2 TB HD

10. FI-WARE GEs: testbed Implementation FI-WARE meeting9

11. Access the FI-WARE Tesbed  Explore the FI-WARE Catalogue (http://catalogue.fi-ware.eu)FI-WARE Cataloguehttp://catalogue.fi-ware.eu For access ask Testbed Team › Henar Muñoz (henar@tid.es)henar@tid.es › Miguel Carrillo (mcp@tid.es)mcp@tid.es › Stefano De Panfilis (stefano.depanfilis@eng.it)stefano.depanfilis@eng.it Communicating the IPs from where to access the specific GEIs of interest  Deploy your application on the FI-WARE Cloud by specifying: VMs (OS, DBMS – if any, ram, storage) › If the OS/DBMS is not free this should be provided by the UC project IPs from where to access the VMs

12. Access the FI-WARE Tesbed (2)  If you have issues about a GE installed on the testbed, go to the catalogue (http://catalogue.fi-ware.eu/) and send an email to the contact person  We need a single contact point per UC Trial – not all talking to all! He/she should centralise all requests from and to FI-WARE Please nominate one (+ a deputy)  FI-WARE will grant access to JIRA (once available) to provide support  Testbed General info on: http://www.fi-ware.eu/making-it-happen/  Follow the Testbed status on http://twitter.com/FWTestbedStatushttp://twitter.com/FWTestbedStatus

13. From the Testbed to the Open Innovation Lab (OIL) 12

14. Timeline Internal Testing Release 1 Release 2 Release 3 FI-WARE OPEN INNOV LAB FI-WARE TESTBED UCs Phase I Reqs UCs Trials (Phase II) Developers Engagement FI-WARE INSTANCES Jul’12 Jul’13 UCs Roll-out (Phase III) Jun’14

15. FI-WARE Open Innovation Lab  FI-WARE will work towards building an Open Innovation Lab which combines: The FI-WARE Testbed The FI-WARE Development Support Infrastructure (forge + additional community tools)  It is intended that this Open Innovation Lab be available to third parties (specially SMEs) after the second year 14

16. 15 Launch of the FI-WARE OIL  OIL Launch is planned at the end of July’13  All information relevant to a given FI-WARE GEi or packages of FI-WARE GEis (e.g., Cloud) will be available on the FI-WARE CatalogueFI-WARE Catalogue  Every FI-WARE GEi will have a specific support tracker associated to it where questions, bug reports and enhancement requests can be issued  A FI-WARE OIL general tracker will be setup to cope with more general matters (e.g., creation of accounts, issues accessing or using the environment, etc)

17. More developments IPv6 access to FI-WARE GEs:  Most GEs aren’t natively v6-capable, so we offer a v6 transparent service: v6-to-v4 Proxy strategy massively used for “World IPv6 Launch Day” (June, 2012)  UCs v6-access to GEs available.  UCs Apps VMs provided with extensive ranges of public IPv6 addresses. Currently upon request, we are working to enable automatic processes in the Cloud.  New R&D projects might be more pro-active in IPv6 usage.  EC Work-programme 2013 mention: “Taking into consideration the need to future- proof the work to be done, all Challenge 1 proposals are expected to either use or design for IPv6, as appropriate.”  Commercial deployment is increasing in EU. http://the-internet6.blogspot.comhttp://the-internet6.blogspot.com 16

18. More developments (2) Managed Access Security to GEs (Release 2):  Single sign-on platform for the testbed based on OAuth2.0 FI-WARE Ges.  Provides access to GEs depending on user profiles.  Transparent for GEs, except if access control to specific GE resources needed. 17

19. Summary of useful resources  FI-WARE wiki (http://wiki.fi-ware.eu): FI-WARE wiki  Quick FI-WARE tour Quick FI-WARE tour  FI-WARE FAQ FI-WARE FAQ  FI-WARE Agile FI-WARE Agile  FI-WARE Catalogue (http://catalogue.fi-ware.eu) FI-WARE Cataloguehttp://catalogue.fi-ware.eu  FI-WARE Twitter account FI-WARE Twitter account https://twitter.com/Fiware http://twitter.com/FWTestbedStatus  FI-WARE website (http://fi-ware.eu) FI-WARE website  FI-PPP website (http://fi-ppp.eu) FI-PPP website

20. Thanks !! 19 http://www.fi-ppp.eu Stefano.depanfilis@eng.it