Deploy TOSCA Workloads in OpenStack via Stand-Alone …€¦ · Deploy TOSCA Workloads in OpenStack...

Deploy TOSCA Workloads in OpenStack via Stand-Alone TOSCA-Parser, Heat-Translator and Murano

Sahdev Zala IBM Advisory Software Engineer OpenStack PTL Heat-Translator and TOSCA-Parser @sp_zala

flickr.

com/

6839

7968

@N0

7

Vahid Hashemian IBM Advisory Software Engineer

OpenStack Core Heat-Translator and

TOSCA-Parser @vahidh

Overview

2

•  What is TOSCA? –  OASIS open standard specification that defines the interoperable description of

services and applications of enterprise workloads hosted on the cloud. –  Enables interoperability and portability and automated management across cloud

providers regardless of underlying platform or infrastructure.

•  What is TOSCA-Parser? –  Parser for TOSCA Simple Profile in YAML

•  What is Heat? –  Heat is an OpenStack orchestration engine that automates launching multiple

composite cloud applications.

•  What is Heat-Translator? –  An OpenStack project to map and translate non-Heat (e.g. TOSCA) templates to

Heat Orchestration Template (HOT).

Liberty Release: Heat-Translator Enhancements

3

•  Project split –  Heat-Translator –  TOSCA-Parser

•  First PyPI release of Heat-Translator and TOSCA-Parser •  OpenStackClient Plug-in •  New shell command •  TOSCA Cloud Service Archive (CSAR) support

– CSAR is a container in ZIP file format which includes TOSCA service template and artifacts required to deploy corresponding cloud application.

•  Support for URL based template and CSAR •  Dynamic loading of custom types in translator

Heat-Translator & Stand-Alone TOSCA-Parser

4

•  Heat-Translator –  https://github.com/openstack/heat-translator –  https://pypi.python.org/pypi/heat-translator

•  TOSCA-Parser –  https://github.com/openstack/tosca-parser –  https://pypi.python.org/pypi/tosca-parser

TOSCA Template

or CSAR

TOSCA-Parser PyPI library

Heat

Orchestration Template

(HOT)

Heat

Deploy

TOSCA Types

Validation

TOSCA Nodes

Tests

Heat-Translator

Map

Validation

Generate

Tests

Heat-Translator architecture

Translation with OpenStackClient or Shell •  OpenStackClient (OSC)

–  openstack translate template --template-file /home/openstack/heat-translator/translator/tests/data/tosca_helloworld.yaml --template-type tosca

–  openstack help translate template

•  Shell –  heat-translator --template-file=/home/openstack/heat-translator/translator/tests/data/tosca_helloworld.yaml --

template-type=tosca

5

TOSCA YAML HOT YAML

Plan for Mitaka Release Cycle •  New PyPI release at a regular interval of around six weeks •  Bug fix PyPI releases as needed •  Development focus:

– development coverage for TOSCA Simple Profile in YAML 1.0 specification

– create CLI validator for TOSCA-Parser – support for nested imports of TOSCA types – mapping to SoftwareComponent resource in Heat – enable deployment of translated stack via Heat-Translator – support for storing TOSCA artifacts in Glance repository – enhance TOSCA templates ecosystem – TOSCA integration in Murano Application Catalog

6

Murano Overview

•  OpenStack’s application catalog that provides application packaging, deployment, and lifecycle management.

•  Uses the notion of “environments” as collections of one or more application packages that can be deployed and managed together.

•  Supports HOT and MuranoPL for application definitions. •  For HOT templates, Murano starts by creating a package out of

the template that will be imported into the application catalog. •  We are expanding Murano and adding TOSCA support by

leveraging Heat-Translator and TOSCA-Parser.

7

Murano Package Creation and Import: HOT

•  An archive package is created from the input HOT template.

•  It is then imported into the application catalog (via command line or UI).

8

Murano Package Creation and Import: TOSCA

•  An archive package is similarly created from a CSAR archive. This step involves validating the CSAR.

•  It is then imported into the application catalog (via CLI or Horizon).

9

Murano Package Creation and Import

•  After the import, the packages will be available in Murano’s Application Catalog. CSAR based packages will be distinguishable by their default logo.

10

Murano Deployment: HOT vs. TOSCA

•  HOT packages are deployed by Murano.

11

•  TOSCA CSAR packages can be deployed by Murano or Heat-Translator.

12

Thank You!