Conductor CLI
Conductor CLI
Run the Wind River Cloud Platform (WRCP) enrollment and discovery operations using the Conductor CLI.
Upload the Wind River Cloud Platform (WRCP) Blueprint
- Install locally using the Conductor CLI.
cfy blueprints upload --blueprint-id "wind-river-cloud-platform" http://localhost/resources/windriver/cloud-platform/blueprints.tgz
- Install remotely using the CLI.
cfy blueprints upload --blueprint-id "wind-river-cloud-platform" https://<manager-ip>/resources/windriver/cloud-platform/blueprints.tgz
Create Secrets required for the WRCP blueprint deployment
- Add secret “starlingx_username” with the WRCP API administrative user name (default “admin”).
cfy secrets create starlingx_username -s <admin-user>
- Add secret “starlingx_api_key” with the WRCP API administrative user password.
cfy secrets create starlingx_api_key -s <admin-password>
- Add secret “starlingx_cacert” with the WRCP root CA certificate contents.
cfy secrets create starlingx_cacert -f /path/to/certificate/file
Note: These are the default Secret names in the Blueprint and can be specified as input parameters during deployment to be able to specify alternate secrets for different WRCP systems.
Create a Deployment using the WRCP blueprint deployment
- Enter:
cfy deployment create -b "wind-river-cloud-platform" <deployment-name> -i "auth_url=<endpoint-api-url>;user_secret=<secret-name>;password_secret=<secret-name>"
Example:
cfy deployment create -b "wind-river-cloud-platform" "wrcp-system-xyz" -i "auth_url=https://203.0.113.1:5000/v3;user_secret=starlingx_username;password_secret=starlingx_api_key"
Execute the WRCP blueprint deployment
- Enter:
cfy execution start -d <deployment-name> install
Example:
cfy execution start -d "wrcp-system-xyz" install
Discover installed Distributed Cloud Subclouds of System Controllers (if applicable)
- Enter:
cfy execution start -d <deployment-name> discover_and_deploy
Example:
cfy execution start -d "wrcp-system-xyz" discover_and_deploy
A new Deployment will be created and the install workflow executed for each Subcloud. The resulting deployments will be “environments” and can be targets for multi-cloud Service deployments.