Open APIs for Open Minds

Campus Party, FI-WARE – Workshop 2

Management of Blueprints

Fernando López (fla@tid.es), Sergio García (sergg@tid.es)

Telefónica I+D, September 2013

(slide available at : http://tinyurl.com/ws2-fiware)

Workshop Agenda

FI-WARE Intro - J. Hierro (TID)

FI-LAB Portal + Deploy your VMs - G. Toffetti (IBM)

Cloud blueprints - F. López and S. García (TID)

Open APIs - J. Kennedy (Intel)

Authorization using IdM - J. Cerviño and A. Tapiador (UPM)

FI-WARE Business Framework - Markus Heller and Thorsten Sandfuchs (SAP)

Connecting sensors to FI-WARE platform - Carlos Ralli (TID)

2

Summary

3

1. Basic Concepts.

2. Demo.

3. Documentation.

4

1. Basic Concepts

Cloud Components

PaaS Manager

• Deploy Servers. • Install any software.• Config the software.

.war

Context BrokerCloud Portal

SDC Chef ServerDCRMSoftware Catalogue

5

PaaS Manager objectives

6

• Deploying applications and not only Servers.• Ad hoc installation (not template usage).

• Managing applications in Servers (install, uninstall, configure, snapshot…).

• Deploying different environments for that applications.

Introduction

7

• The PaaS Manager GE provides a new layer over the DCRM.

• 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, based on Chef or Puppet recipes (coming soon).

• Provides a flexible mechanism to perform the deployment, enabling multiple deployment architectures.

PaaS Manager

SDC GEiDCRM

Server

Cloud Portal

Product Release & Product Instance

• Product Release is any packet software (usually middleware) that is installed previously to the deployment of an application components.

• Contains the information about the software to be installed.

• Product Instance refers to the Product Release already instantiated (with some defined attributes).

• Example: Apache Tomcat, MongoDB, MySQL, etc.

8

Tier Template & Tier Instance

9

• Each application is structured into one or several Tiers.

• A Tier comprises a set of servers with the same virtual image and set of software products 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.

Blueprint Template & Blueprint Instance

10

• 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.All in one Tier

Firewall

node

Firewall

Several Tiers

Firewall

One scaled Tier

8080 8080

Summary of concepts

Blueprint template: fiware1

• Blueprint Template: platform specification to be deployed.

• Tier: Each kind of software and server to be deployed.

• Each Tier can be deployed in one or several servers (e.g. tomcat, 2-5 servers).

• Blueprint Instance: Deployed in the testbed.

Tier 1: Tomcat

Tier 2: Context Broker

Tier 3: MongoDB

Server: 1 Server: 1

Servers: 2-5

Context Broker

Context Broker

11

Chef enables infrastructure as code

• Manage configuration as idempotent resource.

• Put them together in recipes.

• Track it like source code (e.g. using github).

• Configure your servers.

12

13

2. Demo

14

15

16

17

18

19

20

21

22

23

24

25

26

27

3. Documentation• Open Specification PaaS Manager

https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Cloud.PaaS

• Open Specification SDChttps://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Cloud.SDC

http://fi-ppp.eu

http://fi-ware.eu

Follow @Fiware on Twitter !

Thanks !

28