Provisioning Provider Packs

This section describes the Packs that can be used for provisioning an Environment.

This page includes the following:

Notes:

Provisioning provider Packs can be installed via CLI (About Package Manager ) or GUI (About the Plugin Manager). See: Installing, Upgrading and Importing Packs
These Packs are not compatible with Java 11

PCK.AUTOMIC_PROVISIONING

Note: This Pack must be installed before any vendor Pack.

This is the preliminary Pack for provisioning. It contains the registry container - a VARA object - and the provisioning workflow hooks.

The package provides one provisioning registry (PCK.AUTOMC_PROVISIONING.PRV.PROVISIONING_REGISTRY) within the PROVISIONING/REGISTRY folder and a set of provisioning hooks. Each hook consists of an application workflow, which in turn contains one component workflow. The vendor specific provisioning implementations are then "hooked" into the respective component workflows upon installation by the Package Manager/Plugin Manager.

Subfolder	Object	Description
PROVISIONING/REGISTRY	`PCK.AUTOMIC_PROVISIONING.PRV.PROVISIONING_REGISTRY`	This pack contains the provisioning provider capabilities: @Key = Unique String identifying the provisioning type - the Pack ID. @Value 1 = A string holding a human readable name for the respective provisioning technology. @Value 2 = Workflow identifier (coming from the CONFIG folder). Click on the images to expand them.
PROVISIONING/HOOKS/PROVISION	`PCK.AUTOMIC_PROVISIONING.PRV.APP.PROVISION`	On the Deployment tab of the hook you define the name of the workflow and application/component. These names are matched with the deployment descriptor at execution time. Hooks are extended with every new provider installed. Click on the images to expand them.
PROVISIONING/HOOKS/PROVISION	`PCK.AUTOMIC_PROVISIONING.PRV.COM.PROVISION`
PROVISIONING/HOOKS/DEPROVISION	`PCK.AUTOMIC_PROVISIONING.PRV.APP.DEPROVISION`
PROVISIONING/HOOKS/DEPROVISION	`PCK.AUTOMIC_PROVISIONING.PRV.COM.DEPROVISION`

PCK.AUTOMIC_PROVISIONING.<VENDOR>

A vendor-specific provisioning provider pack provides everything you need to instantiate new/fresh running machines from within the CDA context. Each Pack contains the following objects:

A Stack Provider custom type describing all needed inputs to connect to that specific endpoint.

The "relatedWorkflowIdentifier" system property of this custom type is used to find matching counterparts in workflows.
A Stack Template custom type describing all needed inputs to instantiate a new Stack on the respective provider.

The "relatedWorkflowIdentifier" system property of this custom type is used to find matching counterparts in workflows. There are always two custom types, one of type "Stack Provider" and the other one of type "Stack Template" which align with each other.
Workflows to provision and deprovision a Stack. These workflows are inserted into the hook workflow at package installation time. During runtime the workflow is selected via the relatedWorkflowIdentifier coming from the deployment descriptor.
- Provisioning (creating a Stack + rolling out an Agent + adding a Deployment Target).
- Deprovisioning (disabling the Deployment Target + removing the Agent -also the object from the AE- + tearing down the Stack ).