1 / 20

FI-WARE Testbed Overview Stefano De Panfilis – FI-WARE Testbed Responsible

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

noelle
Download Presentation

FI-WARE Testbed Overview Stefano De Panfilis – FI-WARE Testbed Responsible

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. FI-WARE Generic Enablers • 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

  4. 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 The FI-WARE Testbed

  5. Tesbed V1 Status • Status • 29 GEIsdeployed(http://catalogue.fi-ware.eu/) out of 31 planned • Usage: • https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdEd6bGhLQWtNai1jeGN5UnJMeEdxZ0E#gid=0 • “D” = 12 • 2 overlaps: • VM allocation (safecity and smartagrifood) • ServiceRegistry (finest and smartagrifood) • IM PoCwillnotbebased on “D” • FINSENY didnotcommittohavePoC in theirDoW • “U” = 61 • “E” = 100

  6. Major Achievements • Testbed V1 up and running • Fruitfullcollaborationbetween FI-WARE and UC projects • Testbed “First Impression” UC project survey and “UsageQuestionnaire” • Allprojectsanswered • Quitedetailedcomments • Extremelyuseful, in some casesalreadyimplemented

  7. RoadmaptoTestbed V2 (FI-WARE TechnicalRoadmap) • Migrate allGEIs on top of FI-WARE Cloud • Establishment oftwoenvironments: “stable” and “development” • Testbed V2 willhave: • 3 newGEIsforApps • 3 newGEIsforCloud • 6 newGEIsforIoT • 2 newGEIsfor Data • 3 newGEIsfor I2ND • 5 newGEIsfor Security • DeploymentofTestbed V2 accordingto: • 31 Jul 2013  Testbed V2 up-and-running

  8. High-level Architecture Red.es

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

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

  11. Access the FI-WARE Tesbed • Explore the FI-WARE Catalogue (http://catalogue.fi-ware.eu) • ForaccessaskTestbed Team • HenarMuñoz (henar@tid.es) • Miguel Carrillo (mcp@tid.es) • Stefano De Panfilis (stefano.depanfilis@eng.it) • Communicating the IPsfromwheretoaccess the specificGEIsof interest • Deployyourapplication on the FI-WARE Cloudbyspecifying: • VMs (OS, DBMS – ifany, ram, storage) • If the OS/DBMS isnot free thisshouldbeprovidedby the UC project • IPsfromwheretoaccess 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/FWTestbedStatus

  13. From the Testbed to theOpen Innovation Lab (OIL)

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

  15. 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 FI-WARE Open Innovation Lab

  16. 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 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.com

  18. More developments (2) Managed Access Security to GEs (Release 2): • Single sign-on platform for the testbedbased 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.

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

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

More Related