![The FI-WARE Project – Base Platform for Future
Service Infrastructures
The Blueprint that we want to deploy exists in the Catalogue.
• Just get the list of available Blueprint Templates from Catalogue.
The Blueprint has the definition of the Virtual Appliance and Products
associated to the different Tier.
• The Virtual Appliance is sent to the IaaS SM.
• The Products list is sent to the SDC.
Operations (I): Deploy a Blueprint from
Catalogue.
Cloud Portal PaaS Manager
IaaS SM
SDC
1) BlueprintTemplates[] = listBlueprintTemplate()
2) TaskId = deployBlueprint(BlueprintTemplate)
TaskStatus = getTaskStatus(TaskId)
3) Status = createvApp(vApp)
4) TaskId = installProduct(Server, Product)
TaskStatus = getTaskStatus(TaskId)](https://image.slidesharecdn.com/paasmanagerpresentationv1-130617024914-phpapp02/85/FI-Ware-Cloud-PaaS-Presentation-12-320.jpg)
![The FI-WARE Project – Base Platform for Future
Service Infrastructures
The Blueprints have to be defined.
• Specification of the products that will be supported.
• Related to the capacities of the SDC GE.
An Blueprint has to be deployed.
• On demand, just previous to the deployment of an application, or in
advance, in order to enable faster deployments.
Blueprint and Blueprint Instances can be retired, redefined or evolved.
Operations (II): Define a new Blueprint
Catalogue Template and Deploy.
Cloud Portal PaaS Manager
IaaS SM
SDC
1) ProductList[] = listCatalogueProducts()
2) Status = addBlueprintTemplate(BlueprintTemplate)
3) BlueprintTemplates[] = listBlueprintTemplate()
4) TaskId = deployBlueprint(BlueprintTemplate)
TaskStatus = getTaskStatus(TaskId)
5) Status = createvApp(vApp)
6) TaskId = installProduct(Server, Product)
TaskStatus = getTaskStatus(TaskId)](https://image.slidesharecdn.com/paasmanagerpresentationv1-130617024914-phpapp02/85/FI-Ware-Cloud-PaaS-Presentation-13-320.jpg)
FI-Ware Cloud PaaS Presentation
- 1. The FI-WARE Project – Base Platform for Future Service Infrastructures Management of Blueprints Fernando López Aguilar TID June 2013 http://www.fiware.eu
- 2. The FI-WARE Project – Base Platform for Future Service Infrastructures 1. Basic Concepts 2. API & Operations 3. Demo Index
- 3. The FI-WARE Project – Base Platform for Future Service Infrastructures 1. Basic Concepts
- 4. The FI-WARE Project – Base Platform for Future Service Infrastructures • Deploying applications and not only VMs. • Ad hoc installation (not template usage). • Managing applications in the VMs (install, uninstall, configure, snapshot…). • Deploying different environments for that applications. EC2 Objetive of PaaS Manager
- 5. The FI-WARE Project – Base Platform for Future Service Infrastructures Introduction PaaS Manager Claudia SDC GEi DCRM Server Cloud Portal The PaaS Manager GE provides a new layer over the Claudia (IaaS SM GEi). Orchestrate the provisioning of the required virtual resources at IaaS level. Provide installation and configuration of the whole software stack of an application through SDC GEi. Provides a flexible mechanism to perform the deployment, enabling multiple deployment architectures.
- 6. The FI-WARE Project – Base Platform for Future Service Infrastructures Product Release & Product Instance. • Product Release is an installable software (usually middleware) that is installed previous to the deployment of an application components. • Product Release contains the information about the software to be installed, Product Instance refers to the Product Release already instantiated. • Example: Apache Tomcat, MongoDB, MySQL, etc. Entities (I)
- 7. The FI-WARE Project – Base Platform for Future Service Infrastructures Tier & Tier Instance. • An application is structured into Tiers • A Tier comprises a set of Servers that share the same virtual image and where the same set of software products is installed. • Each of this server can to be cloned in order to handle elasticity. • A Tier Instance is the result of instantiating a given Tier definition (Tier template). • Nodes in a Tier are clonable • Example: A farm of web servers serving static web pages in the given portal associated to a CRM application. Entities (II)
- 8. The FI-WARE Project – Base Platform for Future Service Infrastructures Blueprint Template & Blueprint Instance. • Complete software stack required for the deployment of an application. • Includes IaaS resource (Servers, Networks), products, configuration instructions. • Example: an on-line shop application structured into three tiers. Entities (III) Tier All in one Firewall node Firewall Tier mix Tier Firewall One scaled Tier 8080 8080 Tier Tier
- 9. The FI-WARE Project – Base Platform for Future Service Infrastructures Entities (IV) Virtual Appliance (from IaaS SM) • Pre-built software solutions, comprised of one or more Servers that are packaged, updated, maintained and managed as a unit. • Let customers easily acquire, deploy and manage, pre-integrated solution stacks. • This speeds up time to value and simplifies software development, distribution, and management.
- 10. The FI-WARE Project – Base Platform for Future Service Infrastructures No just one component PaaS Manager IaaS SM SDC • Deploy Virtual Appliances Chef server • Install Products • Config products for Blueprint.
- 11. The FI-WARE Project – Base Platform for Future Service Infrastructures 2. API & Operations
- 12. The FI-WARE Project – Base Platform for Future Service Infrastructures The Blueprint that we want to deploy exists in the Catalogue. • Just get the list of available Blueprint Templates from Catalogue. The Blueprint has the definition of the Virtual Appliance and Products associated to the different Tier. • The Virtual Appliance is sent to the IaaS SM. • The Products list is sent to the SDC. Operations (I): Deploy a Blueprint from Catalogue. Cloud Portal PaaS Manager IaaS SM SDC 1) BlueprintTemplates[] = listBlueprintTemplate() 2) TaskId = deployBlueprint(BlueprintTemplate) TaskStatus = getTaskStatus(TaskId) 3) Status = createvApp(vApp) 4) TaskId = installProduct(Server, Product) TaskStatus = getTaskStatus(TaskId)
- 13. The FI-WARE Project – Base Platform for Future Service Infrastructures The Blueprints have to be defined. • Specification of the products that will be supported. • Related to the capacities of the SDC GE. An Blueprint has to be deployed. • On demand, just previous to the deployment of an application, or in advance, in order to enable faster deployments. Blueprint and Blueprint Instances can be retired, redefined or evolved. Operations (II): Define a new Blueprint Catalogue Template and Deploy. Cloud Portal PaaS Manager IaaS SM SDC 1) ProductList[] = listCatalogueProducts() 2) Status = addBlueprintTemplate(BlueprintTemplate) 3) BlueprintTemplates[] = listBlueprintTemplate() 4) TaskId = deployBlueprint(BlueprintTemplate) TaskStatus = getTaskStatus(TaskId) 5) Status = createvApp(vApp) 6) TaskId = installProduct(Server, Product) TaskStatus = getTaskStatus(TaskId)
- 14. The FI-WARE Project – Base Platform for Future Service Infrastructures Open Specification PaaS Manager https://forge.fi- ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Cloud.PaaS Open Specification SDC https://forge.fi- ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Cloud.SDC Open Specification IaaS SM https://forge.fi- ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Cloud.SM Documentation
- 15. The FI-WARE Project – Base Platform for Future Service Infrastructures 3. Demo
- 16. The FI-WARE Project – Base Platform for Future Service Infrastructures Our objective Working together to make it possible: New services for everybody Smart applications Innovative business models Providing the Technology Foundation – Standard interfaces. – Open to other actors (SMEs) – Scalable and demand oriented (cloud) create a solid basis for the Internet of the Future The FI-WARE Project – Base Platform for Future Service Infrastructures
Editor's Notes
- #2: OkLet’s start, My name is Fernando LopezI’m part of the Telefonica’s Team on FIWAREI am going to present this webinar together with Irena Trajkovska (Cloud Portal interface demo) that is based on the PaaS manager Generic Enabler Telefónica Implementation.For any question feel free to do it using the tweeter hash #Blueprint and .@FIWARE and my team can answer it given maximum diffusion of this webinar.
- #3: This is a small index of the presentation. It is divided in 3 sectionsDefinition of the basic concepts that we are using in the PaaS Manager GE.Introduction to the PaaS Manager API and the most important operations of this Generic Enabler. For a more detailed information about the operations provided by this API, please refer to the Open Specification description of this component (reference at the end of this presentation).Last but not least and maybe the most important part of the webinar, we show you a demonstration of how the PaaS Manager works.
- #4: Ok let’s start with the definition of the Concepts.
- #6: SDC -> Software Management and Configuration
- #7: Etcetera /ɛtˈsɛtərə/
- #8: Tier /tɪər/ associated [uh-soh-shee-eyt] Customer Relationship Management (CRM)Flavor [fley-ver] node /noʊd/Comprise [kuhm-prahyz] Clone [klohn]Image [im-ij]
- #9: Example: an on-line shop application structured into three tiers (the farm of web servers, an application servers running business logic and a NoSQL DB).Node [nohd] proxy /ˈprɒksi/
- #12: Capacities of the SDC GE: - the list of products that can be actually installed, configured and used. The definition of environments involves the specification of products and their supported releases as well as the specification of tiers.
- #13: Capacities of the SDC GE: - the list of products that can be actually installed, configured and used. The definition of environments involves the specification of products and their supported releases as well as the specification of tiers.TaskStatus = getTaskStatus(TaskId)