The data required for deploying the service on the hardware selected by the topology completion needs to be injected.
[x] Modify the OpenStack NodeType to be annotated with the tag "hardware" and define required attributes via tags (e.g., hypervisor, login name, password)
[x] Extend the Deploy Workflow Dialog
[x] Retrieve from Winery all Nodetypes that are annotated with the tag "hardware"
[x] Check them for required attributes
[x] Generate a user dialog showcasing all available hardware types with their icons and provide text fields for each
required property.
[x] Adjust dialog 1/3 to show which deployment models must be completed
[x] After step 2/3 the now completed models that shall be deployed prior execution must be deployed
[x] The properties shall also be loadable via env vars for better usability and testing
[x] When confirming the dialog, all nodetypes with fulfilled requirements are saved in a list and subsequently used for completion
[x] Directly after the deployment model completion, hardware properties need to be attached as follows:
[x] For all service tasks deploying a previously completed, i.e. originally incomplete, deployment model NOT on demand, the properties from the dialog shall be used for the deployment process
[x] For all service tasks deploying a previously completed, i.e. originally incomplete, deployment model on demand, the properties from the dialog shall be attached as inputs to the deployment sub-process
The data required for deploying the service on the hardware selected by the topology completion needs to be injected.
The properties shall also be loadable via env vars for better usability and testing