You create a project to which you add members and cloud zones so that the project members can deploy their cloud templates to the associated zones. As the 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 cloud template, you first select the project to associate it with. The project must exist before you can create the cloud template.
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 cloud template, see Tutorial: Setting up and testing multi-cloud infrastructure and deployments in Cloud Assembly.
- 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 page, 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 Service Broker. The policies apply to Cloud Assembly and 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 cloud templates, 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 Cloud Assembly projects.
- Verify that you configured the cloud zones. See Building your 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 Cloud Assembly resource infrastructure.
- Verify that you have the necessary permissions to perform this task. See What are the vRealize Automation Cloud user roles.
- Determine who you are designating as the project administrator. To understand what the project administrator can do in Cloud Assembly, see What are the vRealize Automation Cloud user roles.
- If you are adding Active Directory groups to projects, verify that you configured Active Directory groups for your organization. See How do I enable Active Directory groups in vRealize Automation Cloud for projects. 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 Users tab.
- To make deployments by project members accessible only to the requesting user, turn off Deployment sharing. To ensure that you can assign the ownership of a deployment to another member of the project, verify that the Deployment sharing is turned on.
- Add users or user groups with assigned roles.
User roles based on groups allows users to come and go from your Active Directory groups rather than requiring the project administrator to constantly update the individual users in the project. For example, if deployment ownership is based on groups, you can change the ownership of a deployment to the group. Any notifications are sent to all the group members, allowing anyone to respond.
- Click the Provisioning tab and add one or more cloud zones.
Add any cloud zones and virtual private zones that contain the resources that support the cloud templates deployed by the project users.
For each zone, you can set a zone priority and you can limit the amount of resources that the project can use. The possible limits include the number of instances, memory, and CPUs. For vSphere cloud zones only, you can configure storage limits for deployed resources that are based on vSphere VM templates and content library items. Storage limits consider the actual capacity for thick and thin resource provisioning so that you cannot over-provision using thin provisioning. First class disks and vSphere independent disks are also considered in the storage limits. Storage limits do not apply to OVA/OVF templates that are outside of the content library.
The storage limits are evaluated when you request a deployment and when you make changes to the deployment using the resize disk, resize boot disk, remove disk, and the update count actions. Like initial provisioning, thick and thin provisioning are considered to prevent over-provisioning. These storage limits do not apply to other resource types such as AWS, Microsoft Azure, or Google Cloud Platform.
As you add each zone and apply limits, don't limit the project resources so narrowly that the members cannot deploy their cloud templates.
When your users submit a deployment request, the zones are evaluated to determine which zones have the resources to support the deployment. If more than one zone supports the deployment, then the priority is evaluated and the workload is placed on the one with the higher priority, which is the lowest integer.
- If the workloads requested for this project take more than two hours to deploy, enter a longer value for the Timeout.
The default value is two hours.
- 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 cloud templates. See Designing your Cloud Assembly deployments.