management of blueprints
play

Management of Blueprints Fernando Lpez Aguilar TID June 2013 - PowerPoint PPT Presentation

Management of Blueprints Fernando Lpez Aguilar TID June 2013 http://www.fiware.eu The FI-WARE Project Base Platform for Future Service Infrastructures Index 1. Basic Concepts 2. API & Operations 3. Demo The FI-WARE Project


  1. Management of Blueprints Fernando López Aguilar TID June 2013 http://www.fiware.eu The FI-WARE Project – Base Platform for Future Service Infrastructures

  2. Index 1. Basic Concepts 2. API & Operations 3. Demo The FI-WARE Project – Base Platform for Future Service Infrastructures

  3. 1. Basic Concepts The FI-WARE Project – Base Platform for Future Service Infrastructures

  4. Objetive of PaaS Manager • Deploying ¡applica-ons ¡and ¡not ¡only ¡VMs. ¡ • Ad ¡hoc ¡installa-on ¡(not ¡template ¡usage). ¡ • Managing ¡applica-ons ¡in ¡the ¡VMs ¡(install, ¡uninstall, ¡configure, ¡ snapshot…). ¡ • Deploying ¡different ¡environments ¡for ¡that ¡applica-ons. ¡ ¡ EC2 The FI-WARE Project – Base Platform for Future 3 Service Infrastructures

  5. Introduction § The PaaS Manager GE provides a Cloud Portal new layer over the Claudia (IaaS SM GEi). § Orchestrate the provisioning of the PaaS Manager required virtual resources at IaaS level. Claudia SDC GEi § Provide installation and configuration of the whole software stack of an application through SDC GEi. DCRM § Provides a flexible mechanism to perform the deployment, enabling Server multiple deployment architectures. The FI-WARE Project – Base Platform for Future 4 Service Infrastructures

  6. Entities (I) § 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. The FI-WARE Project – Base Platform for Future 5 Service Infrastructures

  7. Entities (II) § 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. The FI-WARE Project – Base Platform for Future 6 Service Infrastructures

  8. Entities (III) § 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. One scaled Tier All in one mix Tier Tier Tier Firewall Firewall Firewall 8080 8080 Tier node Tier The FI-WARE Project – Base Platform for Future 7 Service Infrastructures

  9. 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. The FI-WARE Project – Base Platform for Future 8 Service Infrastructures

  10. No just one component PaaS Manager • Deploy Virtual • Install Products Appliances • Config products for Blueprint. Chef IaaS SM SDC server The FI-WARE Project – Base Platform for Future 9 Service Infrastructures

  11. 2. API & Operations The FI-WARE Project – Base Platform for Future Service Infrastructures

  12. Operations (I): Deploy a Blueprint from Catalogue. § 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. SDC 4) TaskId = installProduct(Server, Product) TaskStatus = getTaskStatus(TaskId) Cloud Portal PaaS Manager IaaS SM 1) BlueprintTemplates[] = listBlueprintTemplate() 3) Status = createvApp(vApp) 2) TaskId = deployBlueprint(BlueprintTemplate) TaskStatus = getTaskStatus(TaskId) The FI-WARE Project – Base Platform for Future 11 Service Infrastructures

  13. Operations (II): Define a new Blueprint Catalogue Template and Deploy. § 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. 1) ProductList[] = listCatalogueProducts() SDC 6) TaskId = installProduct(Server, Product) TaskStatus = getTaskStatus(TaskId) Cloud Portal PaaS Manager IaaS SM 2) Status = addBlueprintTemplate(BlueprintTemplate) 5) Status = createvApp(vApp) 3) BlueprintTemplates[] = listBlueprintTemplate() 4) TaskId = deployBlueprint(BlueprintTemplate) TaskStatus = getTaskStatus(TaskId) The FI-WARE Project – Base Platform for Future 12 Service Infrastructures

  14. Documentation § Open Specification PaaS Manager h t t p s : / / f o r g e . f i - w a r e . e u / p l u g i n s / m e d i a w i k i / w i k i / f i w a r e / i n d e x . p h p / FIWARE.OpenSpecification.Cloud.PaaS § Open Specification SDC h t t p s : / / f o r g e . f i - w a r e . e u / p l u g i n s / m e d i a w i k i / w i k i / f i w a r e / i n d e x . p h p / FIWARE.OpenSpecification.Cloud.SDC § Open Specification IaaS SM h t t p s : / / f o r g e . f i - w a r e . e u / p l u g i n s / m e d i a w i k i / w i k i / f i w a r e / i n d e x . p h p / FIWARE.OpenSpecification.Cloud.SM The FI-WARE Project – Base Platform for Future 13 Service Infrastructures

  15. 3. Demo The FI-WARE Project – Base Platform for Future Service Infrastructures

  16. 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 The FI-WARE Project – Base Platform for Future Service Infrastructures Service Infrastructures

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend