This document discusses a cooperative project between Netzlink Informationstechnik GmbH and the FIWARE Foundation to improve Netzlink's FIWARE workflow. Currently, deploying FIWARE takes about one workday. The project aims to build a Platform as a Service (PaaS) on OpenShift to provide a "1-click" deployment of FIWARE components in minutes. It will include an easy to use marketplace, deployment of General Enablers as Docker containers, and a "pizza team" approach using agile methodology. The outlook describes plans to create a Netzlink Github and professional PaaS offerings by June 2018 to help migration, new applications, and DevOps skills transformation.
4. • German IT Company
• One of the first FIWARE commercial platform and infrastructure providers
to have entered the FIWARE marketplace
• able to offer dedicated FIWARE instances
• making it possible for every customer to access their own FIWARE environment
• agreement with the FIWARE Foundation on the provision of “General
Enablers” (ob. “GEs”)
NETZLINK
WHO WE ARE
5. • Data centre resources exclusively in Germany
• Data protection: Federal Data Protection Act
• Own organization for IT security and IT emergency management
• Use of current technology from current IT market leaders
• Fully redundant IT system
• distributed over several fire sections in one data centre or via multiple data
centres
NETZLINK
NUBO CLOUD
6. • Mission:
• Build an open sustainable ecosystem around public, royalty-free and
implementation-driven software platform standards
• ease the development of new Smart Applications in multiple sectors
• FIWARE platform provides a powerful set of APIs
• ease the development of Smart Applications in multiple vertical sectors
• Open source reference implementation of each of the FIWARE
components is publicly available
➢ multiple FIWARE providers can emerge faster in the market with a low-cost
proposition
FIWARE
ABOUT FIWARE
7. • non-commercial sandbox environment
• Testing technology and applications on the FIWARE Lab by everyone
• deployed over a geographically distributed network of federated nodes
leveraging on a wide range of experimental infrastructures
FIWARE
FIWARE LAB
11. • Working on Fiware IaaS
• (Automated VMs deployment factory)
• Receive IaaS -> Configuration and set up by yourself
• Takes a lot of time! (about one workday until the client is online)
WORKFLOW
STATE OF THE ART
IaaS
Account
Management
FIWARE
Images
Deployment
Configuration
Use
13. Flink Node the Fiware Paas
IMPROVE THE WORKFLOW
Building our PaaS solution
14. • Easy to use marketplace
• “1-Click” roll out
• Ready in minutes!
• Instantly build applications in containers
PROJECT
NEW WORKFLOW
OpenShift
(based on Kubernetes)
Marketplace
Complete
Environment
Choose GEs
Get GEs as
Docker Container
Start working
15. Working on a PaaS based on the IaaS
• OpenShift 3.0,
• Build a test platform
• New integrated toolkit : Jenkins, Git, ELK, Centreon, ….
Need a new work organization : “pizza team”
• Use of the « agile » method with the help of Experts (organization and
knowledge transfer),
• Iterative method : ie. 2 weeks per iteration
• Contributors both Dev and Ops
PROJECT
NEW WORKFLOW
18. FilnkNode
Status und outlook
● PaaS Self-Service
● Self-Service Portal
● Full Managed Development
● Smart Cities Network Platform
● Open Innovation-Platform for
● ISV
● SME
● Industry
● innovators
● University
● R/D department
The New Model and the new Offer
Certified Fiware Provider
31. • Creating a Netzlink Github
• Professional variant
NETZLINK GITHUB
PLANNED FOR 2018
Products
Community
Netzlink
Github
32. 1st OBJECTIVE : MIGRATION
• Help projects from legacy to migrate their applications
systems (in order to manage obsolescence)
• A target of moving a first set of 10 apps in 6 months,
to an up-to-date software stack
• Continue to operate these apps (in a DevOps model)
PROJECT
NEW WORKFLOW
33. 2nd OBJECTIVE : CONQUEST
• Host a new set of 10 strategic business applications
before June 2018 with for some of them the use
of new stacks
• Deliver apps environments faster, using standards
• Benefit from newly offered PaaS functionalities
• Use of the DevOps model
PROJECT
NEW WORKFLOW
34. 3rd OBJECTIVE : TRANSFORM
• Upgrade Comunity team’s skills
• Share these skills and knowledge
• New technical patterns for Cloud Native apps :
• Stateless,
• Micro services,
• No scheduling system
• Design for failure
• Deploy everywhere (independent application from infrastructure )
PROJECT
NEW WORKFLOW
35. Target
● Customer opening :
○ PaaS for Test purpose March 2018
○ PaaS for Build purpose May 2018
○ PaaS for Run purpose June 2018
○ Service offered : out of the box services / no
customisation / use of solution & Editor
standards
● FIWARE Catalog extensions
● Tribute to FIWARE Opensource Community
PROJECT
NEW WORKFLOW
36. • Creating a Netzlink Github
• Professional variant
NETZLINK GITHUB
PLANNED FOR 2018
Netzlink Github
Community
Products