tosKer 2.0.1

A TOSCA engine working with Docker container

TosKer is an orchestrator engine capable of automatically deploying and managing multi-component applications specifies in OASIS TOSCA, by exploiting Docker as a lightweight virtualization framework. The novelty of TosKer is to decouple the application-specific components, from the containers used to build their infrastructure. This permits to improve the orchestration of the components and to ease the change of the containers underneath.

• Documentation

• Presentation Slids

Installation

TosKer requires having Docker installed and configured on the machine. In is possible to install TosKer by using pip:

# pip install tosker

The minimum Python version supported is 2.7. It is possible to find other installation methods on the documentation.

Quick Guide

After the installation it is possible to found in /usr/share/tosker/examples the CSAR of two example application, node-mongo.casr and thoughts.csar.

To create and start the thoughts application run the command:

tosker /usr/share/tosker/examples/thoughts.csar create start

It is possible to use the ls command to check that all the components are in the started state:

tosker ls

Now, the application can be accessible on http://127.0.0.1:8080/thoughts.html. Finally, to stop and delete the application run the command:

tosker /usr/share/tosker/examples/thoughts.csar stop delete

License

MIT license

History

0.4.0 (2017-07-10)

• First release on PyPI.

1.0.0 (2017-11-20)

Stable release without Management Protocols.

• Add command log, to show the execution of an operation on a component.

• Add command prune, to remove all TosKer files and restore initial state.

• Improve memory management.

• Improve command line interface.

• Bug fix.

2.0.0 (2017-12-09)

• Switch to Management Protocols to manage the life cycle of the components

• Add support for derived node types.

• Add support for custom interfaces.

• Support custom management protocol defined using policies.

• Support safe execution of plans (list of <component, interface, operation>).

• Improve command line interface.