Table Of Contents

Previous topic

Deployment in Shared Apache Web Space

Next topic

Migration to Docker Container

Application Packaging Standard

Last updated 18-Mar-2019

Deployment Process

Service providers follow the instruction in this document when they start using APS applications.

System Wide Configuration

This step helps a provider to make the platform ready to deploy the APS applications based on the Docker images. Normally, it should be done only one time as this creates a system wide configuration to deploy all APS applications that use the same Docker registry.

  1. Ensure the platform is connected to the Docker registry that contains the required APS connector images. For example, if the images are stored in the Docker official registry:

    • Navigate to System > Settings and in the Integration section click on the Docker Registry Settings link.

    • Click Edit and replace the Docker Registry Hostname with docker.io.

      ../../../../_images/docker-registry-official1.png

  2. Navigate to Infrastructure > Service Nodes and ensure the platform has a registered service node assigned the APS Endpoint Node role.

Package Import

The APS application deployment starts with the package import. If you have the administration permissions in the platform, you can import a package following these steps in the provider control panel.

  1. Navigate to Services > Applications.

  2. Use one of the following ways to import APS applications:

    • To import a local file or a file addressed by a URL, click the Import Package button and then select the local file or provide its URL.

      ../../../../_images/import-from-file.png

    • To import APS packages from the APS catalog, switch to the APS Catalog tab, find out and select one or more APS packages, and then click Import packages.

      ../../../../_images/import-from-calalog.png

  3. Click Submit to complete the operation.

Application Instance Installation

Installation of an APS application instance on the platform is needed to establish the secure connection between the APS controller and the application. During this process, the APS controller must generate an application certificate for the application and send it to the application instance through the APS application endpoint. The provider should do this operation in the provider control panel following these directions:

  1. Navigate to Services > Applications and open the imported application on the Instances tab.

  2. Click Install.

  3. Depending of the deployment method, use one of the following options.

    • If the Automatically deploy application’s backend option is available, it means both your platform and the APS package are configured to use the preferable deployment method based on the Docker technique. With this option selected, the platform will create an APS connector and then install an APS application instance in it.

      ../../../../_images/deploy-connector-auto.png

    • The other option implies that you have deployed an APS connector and you know its endpoint URL. In this case, in the Application API end-point URI field, enter the application endpoint URL. It can be similar to https://<endpoint_domain_name>/vpsclouds/. In this case, the platform will install an APS application instance in the specified APS connector.

  4. Click Next.

  5. Enter, if needed, application global properties, which often are connection parameters, such as IP address of the cloud application host, login, and password.

  6. Click Finish to confirm the provisioning.

Conclusion

On completion of the deployment steps, the platform must be connected with the original application through an APS application instance. The APS database contains all APS types of the application to be used for creating APS resources. The application custom UI is integrated with the platfrom control panels.

The next phase for the provider is to create the products that will allow customers to subscribe to the application services as explained in the Product Initialization document.