Cloud Application Lifecycle using OSLC and TOSCA

Body

This demo (OSLC and TOSCA Cloud App Lifecycle) is about a lifecycle of a cloud application.

It is not “THE END-END LIFECYCLE”, it is just one example of the many possible lifecycles you can build with your tools to manage cloud applications.

The goal is to show how OSLC and TOSCA make this easy.

The lifecycle is composed of the following steps:

1. In the first step, a developer imports a TOSCA cloud application package in a definitive software library. The library is implemented with Rational Asset Manager, but any other tool implementing the OSLC Asset Management specification would work as well.
2. In the second step, a librarian publishes the cloud application to a cloud provisioning service that supports the same package format. The provisioning service is implemented with IBM Workload Deployer but any other service implementing the same OSLC Provisioning interface would work.
3. In the third step, an end-user deploys the cloud application from an offering in the self-service catalog in SmartCloud Control Desk. The self-service catalog delegates the operation to the cloud provisioning server through an OSLC interaction.
4. In the forth step,  an administrator logs an incident under the assumption that there is a problem with the cloud application instance that was just created
5. In the final step, an administrator uses all of the linked data that was created in the previous steps together with data from other related management tools, to perform root cause analysis and resolve the problem.

The demo highlights the following benefits of using the OSLC and TOSCA integration approach:

• It is a robust integration between management tools based on OSLC open, community based specifications.
• The lifecycle is easy to adapt to existing customer management tools because they do not collaborate using their native operations and data formats but instead use common operations and data formats. This includes the TOSCA format of the cloud application package that is portable and can be shared by different types of cloud provisioning servers.
• This is a type of integration that blurs the lines between the management tools participating in the lifecycle.

Thanks for watching the video. Let us know what you think!