In this example, you onboard two unmanaged machines as a single vRealize Automation Cloud Assembly deployment and create a single blueprint for all machines in the plan.
When you create a cloud account, all machines that are associated to it are data-collected and then displayed on the vRealize Automation Cloud Assembly, you can use an onboarding plan to allow vRealize Automation Cloud Assembly to manage the machine deployments.page. If the cloud account has machines that were deployed outside of
Verify that you have the required user role. See What are the vRealize Automation Cloud Assembly user roles.
- Review What are onboarding plans in vRealize Automation Cloud Assembly.
- Create and prepare a vRealize Automation Cloud Assembly project.
This procedure involves some of the steps from the basic Wordpress use case. See The WordPress use case.
- Create a project, add users, and assign user roles in the project. See WordPress use case: create a project.
- Create an Amazon Web Services cloud account for the project. See WordPress use case: add cloud accounts.
The Amazon Web Services cloud account in this procedure contains machines that were deployed before the cloud account was added to vRealize Automation Cloud Assembly and by an application other than vRealize Automation Cloud Assembly.
- Verify that the Machines page contains machines to onboard. See Machine resources.
- Go to .
- Click New Onboarding Plan and enter sample values.
Setting Sample Value Plan name VC-sqa-deployments Description Sample onboarding plan for AWS machine for OurCo-AWS cloud account Cloud account OurCo-AWS Default project
- Click Create.
- On the plan's Deployments tab, click Select Machines, choose one or more machines, and click OK.
- Select Create one deployment that contains all the machines and click Create.
- Click the check box next to the new deployment name and click Blueprint....
- Click Create blueprint in Cloud Assembly format.
- Enter a blueprint name and click Save.
Note: When your onboarding plan uses a vSphere machine, you must edit the blueprint after the onboarding process is complete. The onboarding process cannot link the source vSphere machine and its machine template, and the resultant blueprint will contain the
imageRef: "no image available"entry in the blueprint code. The blueprint cannot be deployed until you specify the correct template name in the
imageRef:field. To make it easier to locate and update the blueprint after the onboarding process is complete, use the Blueprint name option on the deployment's Blueprint Configuration page. Record the auto-generated blueprint name or enter and record a blueprint name of your choice. When onboarding is complete, locate and open the blueprint and replace the
"no image available"entry in the
imageRef:field with the correct template name.
- Click the deployment name check box, click Run, and then click Run again on the Run Plan page.
The selected Amazon Web Services machines are onboarded as a single deployment, with an accompanying blueprint.
- Open and examine the blueprint by clicking the Blueprints tab and then clicking the blueprint name.
- Open and examine the deployment by clicking the Deployments tab and then clicking the deployment name.