You create a project to which you add members and cloud zones so that the project members can deploy their blueprints to the associated zones. As the vRealize Automation Cloud Assembly administrator, you create a project for a development team. You can then assign a project administrator or you can operate as the project administrator.
When you create a blueprint, you first select the project to associate it with. The project must exist before you can create the blueprint.
Ensure that your projects support the business needs of the development team.
- Does the project provide the resources that support the team's goals. For an example of how the infrastructure resources and a project support a blueprint, see The WordPress use case.
- Do your project members require or expect their deployments to be shared or private. Shared deployments are available to all the project members on the Deployments tab, not only the deploying member. You can change the deployment sharing state at anytime.
When you share the deployment with project members, the members can run the same day 2 action. To manage the ability of members to run day 2 actions, you can create day 2 policies in vRealize Automation Service Broker. The policies apply to vRealize Automation Cloud Assembly and vRealize Automation Service Broker deployments.
To learn more about the day 2 policies, see How do I entitle deployment users to day 2 actions using policies .
This procedure is based on creating an initial project that includes only the basic configurations. As your development team creates and deploys their blueprints, you might modify to the project. You can add constraints, custom properties, and other options to improve deployment efficiencies. See the articles available in Learn more about vRealize Automation Cloud Assembly projects.
- Verify that you configured the cloud zones. See Building your vRealize Automation Cloud Assembly resource infrastructure.
- Verify that you configured the mappings and profiles for the regions that include as cloud zones for this project. See Building your vRealize Automation Cloud Assembly resource infrastructure.
- Verify that you have the necessary permissions to perform this task. See What are the vRealize Automation Cloud Assembly user roles.
- Determine who you are designating as the project administrator. To understand what the project administrator can do in vRealize Automation Cloud Assembly, see What are the vRealize Automation Cloud Assembly user roles.
- If you are adding Active Directory groups to projects, verify that you configured Active Directory groups for your organization. See Edit group role assignments in vRealize Automation in Administering vRealize Automation. If the groups are not synchronized, they are not available when you try to add them to a project.
- Select New Project. , and click
- Enter the project name.
- Click the User tab.
- To make deployments by project members accessible only to the owner, turn off Deployment sharing.
- Add users with assigned roles.
- Click the Provisioning tab and add one or more cloud zones.
The cloud zones must contain the resources that support the blueprints deployed by the users.
For each cloud zone, you can limit the amount of resources that the project can utilize. The possible limits include the number of instances, memory, and CPUs. For vSphere cloud zones only, your can configure storage limits.
As you add each cloud zone and apply limits, don't limit the project resources so much that the members cannot deploy their blueprints.
- Click Create.
- To test your project with the project cloud zones, click Test Configuration on the Projects page.
The simulation runs a standardized hypothetical deployment test against the project cloud zone resources. If it fails, you can review the details and correct your resource configuration.
What to do next
Get started with blueprints. See Designing your vRealize Automation Cloud Assembly deployments.