Cloud Application Developers use STRATEGIC Service Store for the preparation and creation of applications. As Cloud Application Developers have technical background they have to use advanced capabilities of STRATEGIC Service Store to prepare their applications through the user interface and also by creating scripts when needed.

In order to create a new application and publish it in the STRATEGIC Service Store, a developer start by providing a descriptive application name, application icon and also Description and License type. A “How to get started” section should contain general steps on how a user can deploy and access the application.

It is important to be set accessibility setting to “public” when application is ready to be fully published.

Once the application profile is completed and updated/saved, we need to create new application topology to edit:

After its creation, the topology can be edited in order to set up the desired service through the following editable sections:

Parameters – used for defining user filled input variables which can be used in the service provisioning script(s)

Servers – defining the nodes/VMs that form the application, together with their firewall settings and the provisioning steps/scripts

Scripts – defining provisioning scripts that are used to install and configure services inside VMs

image013

Figure: Defining the application topology through STRATEGIC Service Store

Requirements can be set to specify the needs of the application in OS and hardware level. Specify VM minimal requirements – like “Min. Memory”, “Min. VCPU” – also which VM operating system templates are supported (for example: Ubuntu 12.04). It is important that VM OS templates listed here have to be available from target cloud image catalogue.

Firewall rules can also be added in order to secure the application.

Adding scripts-recipes is the core part of the packaging. Service provisioning inside the VM requires at least a single Recipe to be executed. The scripts can use the input variables defined earlier by the developer and are filled by the users. We have concluded in the simple rule that if the installation process of an application can be executed with scripts, it can be packaged and added to STRATEGIC Service Store. Most common script languages are supported.