FIWARE Global Summit - Provisioning of the FIWARE Orion Context Broker using OpenTOSCA

UweBreitenbücher
Kálmán Képes, Ana Cristina Franco da Silva
kalman.kepes@iaas.uni-stuttgart.de
ana-cristina.franco-da-silva@ipvs.uni-stuttgart.de
Provisioning of the FIWARE Orion
Context Broker using OpenTOSCA
IAAS
&
IPVS

Table of Contents
§ Motivation
§ TOSCA Standard
§ OpenTOSCA Ecosystem Overview
§ Using FIWARE Orion in OpenTOSCA
§ (Discussion J)

UweBreitenbücher
Motivation: IoT Interoperability
Heterogeneity of Sensors, Actuators, and
Applications

Problem and Motivation
4
Building1..n
Sensors1..n
Sensors1..n
Actuators1..n
Building1..n
Application1..n Application1..n
Mobility Health
Manu-
facturing …
HTTP

CoAP
HTTP
…

UweBreitenbücher
Didn‘t we see these kinds of problems
already?

We have seen the same diversity in application management
…

HTTP
Therefore, two integration directions have to be considered
REST
Horizontal Integration Challenge
VerticalIntegrationChallenge
MQTT
REST
IoT
Middleware

Building1..n
Sensors1..n
Sensors1..n
Actuators1..n
Building1..n
Mobility Health
Manu-
facturing …
HTTP
Protocols1…nProtocols1…n
Therefore, two integration directions have to be considered

Building1..n
Sensors1..n
Sensors1..n
Actuators1..n
Building1..n
Mobility Health
Manu-
facturing …
HTTP

Issues: How to achieve…
Interoperability,
Automated Deployment,
Portability,
…
?

Building1..n
Sensors1..n
Sensors1..n
Actuators1..n
Building1..n
Mobility Health
Manu-
facturing …

Motivation
Building1..n
Sensors1..n
Sensors1..n
Actuators1..n
Building1..n
Application1..n
Application1..n
Building1..n
Sensors1..n

Building1..n
Sensors1..n
The Vision of SmartOrchestra
Application1..n
Application1..n
SmartServicei
SmartServicei
Servicen
Other services
SmartOrchestra
Marketplace
Catalog

UweBreitenbücher
On of the questions is:
How to describe the deployment of
cloud and IoT applications in a portable
manner?

UweBreitenbücher
Topology and Orchestration Specification
for Cloud Applications (TOSCA)

TOSCA – Overview
§ The Topology and Orchestration Specification for Cloud Applications (TOSCA) is an
an standard for automating the deployment and management of cloud
applications in a portable manner
§ The major goals of TOSCA are:
§ Automation of Deployment and Management
§ Portability
§ Interoperability
§ Vendor-neutral ecosystem
à OASIS Awards 2017 Open Standards Cup to TOSCA for Cloud Portability
23

TOSCA – Overview
§ There are two versions of TOSCA:
§ Topology and Orchestration Specification for Cloud Applications (TOSCA) Version 1.0
§ Published in November 2013
§ XML-based syntax
§ All concepts of TOSCA
§ Supports declarative and imperative deployment modelling
§ TOSCA Simple Profile in YAML Version 1.0
§ Published in January 2017
§ YAML-based syntax
§ Reduced and simplified concepts of TOSCA
§ Supports only declarative deployment modelling
§ In this workshop, we discuss the XML version of 2013 to explain the fundamental
TOSCA concepts regarding deployment modelling
§ Topology and Orchestration Specification for Cloud Applications (TOSCA) Version 1.0
§ Published in November 2013
§ XML-based syntax
§ All concepts of TOSCA
§ Supports declarative and imperative deployment modelling

TOSCA Overview
25
and
Specification for Cloud
Applications
Application Structure Deployment & Management
Topology Orchestration

TOSCA Overview
26

Node Templates and Relationship Templates
§ TOSCA enables describing the structure of the
application to be deployed in the form of a
directed, acyclic graph
§ Nodes of the graph represent components
§ e.g., an Apache Webserver, a VM, a PHP Application,
or a MySQL database
§ These nodes are called Node Templates
§ Edges of the graph represent relationships
§ e.g., that one componenti is hosted on another
component or connects to another component
§ These edges are called Relationship Templates
28
Account: USTUTT
[…]
AmazonEC2
(AmazonEC2)
EntryPath: /index.php
[…]
My-PHP5-App
(PHP5Application)
Port: 80
Username: Admin
Password: QJtW4
[…]
WebServer
(Apache2.4)
RAM: 8GB
SSHCredentials: […]
[…]
Ubuntu-VM
(Ubuntu16.04VM)
[…]
PHP5
(PHP5)
Node Template
Relationship Template
DA

Node Types and Relationship Types
§ Both Node Templates and Relationship Templates
are typed to define the semantics of templates
§ Node Types define the semantics of Node Templates
§ e.g., a Node Template may be of Node Type “Apache2.4“
§ Relationship Types define the semantics of
Relationship Templates
§ e.g., a Relationship Template may be of Relationship Type
„hostedOn“ or „SQLConnection“
§ The type system is extensible: New Node and
Relationship Types can be defined arbitrarily
§ Also inheritance is supported
29
= hostedOn
= dependsOn
Account: USTUTT
[…]
AmazonEC2
(AmazonEC2)
[…]
My-PHP5-App
(PHP5Application)
Port: 80
Username: Admin
Password: QJtW4
[…]
WebServer
(Apache2.4)
RAM: 8GB
[…]
Ubuntu-VM
(Ubuntu16.04VM)
[…]
PHP5
(PHP5)
DA
Node Type

Properties
§ To configure the deployment, Node and
Relationship Templates may specify properties
§ For example, to specify that the Apache
Webserver shall serve HTTP requests at port 80
§ Or to specify the desired RAM of a virtual
machine to be provisioned
§ Properties may also contain instance information
at runtime about a node or relationship
§ For example, the IP-address of a provisioned virtual
machine, which is not known at modelling time
§ The properties a Node or Relationship Template
provides and their schemas are defined by the
respective Node or Relationship Type
30
Account: USTUTT
[…]
AmazonEC2
(AmazonEC2)
[…]
My-PHP5-App
(PHP5Application)
Port: 80
Username: Admin
Password: QJtW4
[…]
WebServer
(Apache2.4)
RAM: 8GB
[…]
Ubuntu-VM
(Ubuntu16.04VM)
[…]
PHP5
(PHP5)
DA
Property

Requirements & Capabilities
31
[…]
My-PHP5-App
(PHP5Application)
Port: 80
Username: Admin
Password: QJtW4
[…]
WebServer
(Apache2.4)
RAM: 8GB
[…]
Ubuntu-VM
(Ubuntu16.04VM)
[…]
PHP5
(PHP5)
DA
ReqCanHostVM
Account: USTUTT
[…]
AmazonEC2
(AmazonEC2)
CapCanHostVM
Requirement Capability
§ Requirements and Capabilities can be attached to
Node Templates
§ Each defined Requirement Types has a
requiredCapabilityType defined (matchmaking)
§ For example a Node Template requires a host
§ To identify capable Node Templates able to serve as
host a matching between requirement and capability is
required
§ Based on Req and Cap a suitable Relationship Type
to connect these two can be determine

Deployment Artifacts
§ To specify the implementations of components
Deployment Artifacts (DA) are used
§ For example, a Deployment Artifact can be the
PHP files of a Web application
§ A Deployment Artifact typically specifies one or
more files and some properties about the artifact
§ For example, the type of the files
32
Deployment Artifact
Account: USTUTT
[…]
AmazonEC2
(AmazonEC2)
[…]
My-PHP5-App
(PHP5Application)
Port: 80
Username: Admin
Password: QJtW4
[…]
WebServer
(Apache2.4)
RAM: 8GB
[…]
Ubuntu-VM
(Ubuntu16.04VM)
[…]
PHP5
(PHP5)
DA

Management Interfaces and Management Operations
§ Types may specify Management Interfaces that
define Management Operations
§ Management Operations can be invoked to manage
the respective template
§ For example, to install a component, to start a
component, or to run a script on a component
§ These Management Operations can be called by the
TOSCA runtime or Management Plans (see next)
33
runScript (…)
Management Interface
Management Operation
Account: USTUTT
[…]
AmazonEC2
(AmazonEC2)
[…]
My-PHP5-App
(PHP5Application)
Port: 80
Username: Admin
Password: QJtW4
[…]
WebServer
(Apache2.4)
RAM: 8GB
[…]
Ubuntu-VM
(Ubuntu16.04VM)
[…]
PHP5
(PHP5)
DA

Implementation Artifacts
§ To implement the defined Management
Operations, Implementation Artifacts are used
§ An Implementation Artifact implements a certain
Management Operation and can be executed
§ For example, the runScript operation could be
implemented as Java-based Web Service
§ Install operations of components are often
implemented as SH scripts when they shall be
hosted on a Virtual Machine
34
IA Implementation Artifact
runScript (…)
Account: USTUTT
[…]
AmazonEC2
(AmazonEC2)
[…]
My-PHP5-App
(PHP5Application)
Port: 80
Username: Admin
Password: QJtW4
[…]
WebServer
(Apache2.4)
RAM: 8GB
[…]
Ubuntu-VM
(Ubuntu16.04VM)
[…]
PHP5
(PHP5)
DA

Topology
Template
Topology Template, Service Template, Cloud Service Archive
35
§ A Topology Template represents the
deployment model
§ Contains all Node and Relationship
Templates of the application
§ A Service Template contains one or more
Topology Templates as well as all used
type definitions and artifacts
§ A Service Template can be used also to
package only type defintions or artifacts
§ A Cloud Service Archive (CSAR) is a
archive format standardized by TOSCA to
package Service Templates as well as all
required files, plans, etc. into a ZIP fileAccount: USTUTT
[…]
AmazonEC2
(AmazonEC2)
[…]
My-PHP5-App
(PHP5Application)
Port: 80
Username: Admin
Password: QJtW4
[…]
WebServer
(Apache2.4)
RAM: 8GB
[…]
Ubuntu-VM
(Ubuntu16.04VM)
[…]
PHP5
(PHP5)
DA

Topology Template
Cloud Service Archive (CSAR)
36
Account: USTUTT
[…]
(AmazonEC2)
[…]
(PHP5Application)
Port: 80
Username: Admin
Password: QJtW4
[…]
(Apache2.4)
RAM: 8GB
[…]
(Ubuntu16.04VM)
[…]
(PHP5)
DA
IAIAIA DA
IAIAIA
>
Node Type Definition
Apache2.4
Apache2.4
Apache2.4
Apache2.4
Apache2.4
Apache2.4
Apache2.4
Apache2.4
Apache2.4
Apache2.4
Apache2.4
Relationship Type Definition
hostedOn

TOSCA Overview
40

Management Plans
41
§ Management Plans enable to automate management functionalities
§ For example, to provision the entire application, to scale-out application
components, or to backup the application‘s data
§ They can be triggered either manually for automated management or be used
by the TOSCA runtime for automatic management
à Can be used for imperative deployment modelling
§ Management Plans read information from the Topology Template and from
the application‘s instance model and invoke Management Operations
§ For example, they invoke several install operations in the right order to
provision the entire application

Provision
VM on
OpenStack
Install
MySQL
DBMS
Provision
VM on EC2
Install
Apache
and PHP
Deploy
PHP App
Create
DB
Connect
App with
database
Example Management Plan
§ Example: BPMN Provisioning Plan for a Topology Template that describes a LAMP-Stack
(LAMP = Linux, Apache, MySQL, PHP | Perl | Python)
§ This plan uses several Implementation Artifacts and Deployment Artifacts from the
Topology Template (and the associated files) for execution 44
HTTP POST to the
Amazon EC2 API
Install Apache Webserver
and PHP via APT GET
HTTP POST to the
OpenStack API
Copy App files via SSH
and SCP to the Web Dir
Configure DB
endpoint via SH script
Install MySQL
DBMS via Chef
Create DB
using SQL

Provision
VM on
OpenStack
Install
MySQL
DBMS
Provision
VM on EC2
Install
Apache
and PHP
Deploy
PHP App
Create
DB
Connect
App with
database
45
HTTP POST to the
Amazon EC2 API
and PHP via APT GET
HTTP POST to the
OpenStack API
Configure DB
Install MySQL
DBMS via Chef
Create DB
using SQL
Endpoint
described in IA
Install-Script
is an IA
App files are
contained in DA
SH script is
an IA
SQL schema
is a DA
Chef cookbook
is an IA
Endpoint
described in IA

Provision
VM on
OpenStack
Install
MySQL
DBMS
Provision
VM on EC2
Install
Apache
and PHP
Deploy
PHP App
Create
DB
Connect
App with
database
§ Of course, the implementation of such plans is very complex due to technical details
à Requires technical experts of different technologies as we discussed previously
46
HTTP POST to the
Amazon EC2 API
and PHP via APT GET
HTTP POST to the
OpenStack API
Configure DB
Install MySQL
DBMS via Chef
Create DB
using SQL

UweBreitenbücher
OpenTOSCA Ecosystem Overview
67

The OpenTOSCA Ecosystem
TOSCA
Modelling Tool
TOSCA
Runtime
Deploy & ManageModel Instantiate
„Standards-based - Open Source - End-To-End Toolchain“
Amazon
Moodle
Apache
Self-Service
Portal

Creation and modeling of TOSCA applications, including
graphical modeling of topologies and management plans.
Exported as Cloud Service Archive (CSAR) for TOSCA runtime.
Self-ServiceModeling Tool Container

TOSCA runtime & middleware
Processes CSARs, runs plans, manages state, …

Offering the deployed CSARs to the
end user for easy instantiation

UweBreitenbücher
Using FIWARE Orion in OpenTOSCA
77

§ In the following, we show how one can integrate the FIWARE Orion Context
Broker to implement the example scenario
§ 2 basic ways for the Integration of Orion:
§ Building from Source
§ Provisioning from a Docker Image
§ Modeling the scenario:
§ Temperature Publisher
§ Messaging Middleware
§ Temperature Subscriber
ORION
Publish Subscribe

§ Orion in TOSCA, from Source:
§ In TOSCA components may (!) implement the so-called Lifecycle-Interface to expose
Management Operations such as install, configure, start, stop,..

§ .. the implementation of the NodeType (i.e. the Management Operations) are
encapsulated in so-called NodeType Implementations, in our case, basic Bash Scripts

§ As one can see here, a single Implementation Artifact is able to do much under the
hood, but building from source takes time and TOSCA is not a “build tool language”

§ Orion in TOSCA, as a Docker Container:
§ In contrast to implementing the Lifecycle-Interface, we derive now from the
NodeType Docker Container to integrate Orion..

§ .. which enables a TOSCA Runtime to interpret and provision Orion using the
Management Operations of our Docker Engine (!) NodeType

§ As the implementation of Management Operations for the provisioning are now not
within the Orion NodeType but in the DockerEngine NodeType, the “implementation”
is quite easy:

87
§ Orion “Topics” in TOSCA, can be created using a Management Operation:
§ We model a Node Type for Channels/Topics/Entities/Context that holds the
necessary information (AttributeName,..) and create an Operation on the
Orion Container for creating as such..

§ Using FIWARE Orion and OpenTOSCA for our example senario:
§ We now show how to model the deployment model of our scenario based on the
following 3 topologies:
§ Orion as Messaging Middleware, which will host topics where the sensors values will be written
and read from
§ Temperature Publisher, which reads from a Temperature Sensor and sends it to a Topic on
hosted on an Orion instance
§ Temperature Subscriber, which reads from Orion Topic Temperature values and turns on/off a
power socket

§ Using FIWARE Orion and
OpenTOSCA for our example
senario:
§ The Messaging Middleware
Topology with Orion:

senario:
§ The Temperature Publisher
Topology

senario:
§ The Temperature
Subscriber Topology

§ The Big Picture:

§ The Big Picture and what’s the deal now anyway?

Add New Publisher Add New SubscriberScale-Out
Messaging Infrastructure

Deploy!

Building1..n
Sensors1..n
Application1..n
Application1..n
SmartServicei
SmartServicei
Servicen
Other services
SmartOrchestra
Marketplace
Catalog
Deploy!

UweBreitenbücher
Thank you for listening J
Questions ?

Thank you for listening, Questions? J

FIWARE Global Summit - Provisioning of the FIWARE Orion Context Broker using OpenTOSCA

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to FIWARE Global Summit - Provisioning of the FIWARE Orion Context Broker using OpenTOSCA

Similar to FIWARE Global Summit - Provisioning of the FIWARE Orion Context Broker using OpenTOSCA (20)

More from FIWARE

More from FIWARE (20)

Recently uploaded

Recently uploaded (20)

FIWARE Global Summit - Provisioning of the FIWARE Orion Context Broker using OpenTOSCA