As a vRealize Automation Cloud cloud administrator, you are responsible for managing the access and the budget for your infrastructure resources. You add yourself and two others as administrators. This small team can create the infrastructure and develop the cloud templates that match the business goals of the teams that consume the cloud templates. You and your small team of administrators then deploy the cloud templates for your non-administrator consumers. You don't allow non-administrators to access vRealize Automation Cloud.

In this use case, you are the organization owner and you have a small team where they all have the service administrator role.

The following procedure follows one user all the way through the process. You can do each step for multiple users.

Prerequisites

Procedure

  1. Assign organization roles. Click Identity and Access Management.
    1. Log in to the vRealize Automation Cloud console.
    2. Click Identity and Access Management.
    3. Select the user name and click Edit Roles.
    4. In the Assign Organization Roles drop-down menu, select Organization Member.

      Add users as organization members.
      The organization member role ensures that the user can access the console and any services that you add them to. They cannot manage organization users.
      Leave the Edit Role page open for this user and continue to the next step.
  2. Assign Cloud Assembly Administrator role to yourself and to the one or two other administrators in this scenario.
    The service administrator role has full privileges to add, edit, and delete infrastructure, projects, cloud templates, and deployments. Defining an administrator role for one person and the user role for a different person is covered in Scenario 2. This example uses Sylvia.
    1. Click Add Service Access.
    2. Configure the user with the following value.
      Service Role
      Cloud Assembly

      Cloud Assembly Administrator


      Assign a service administrator role.
  3. Create a project in Cloud Assembly that you use to group resources and manage resource billing for different business groups.
    1. In the console, click the Services tab, and then click Cloud Assembly.
    2. Select Infrastructure > Projects > New Project.
      This user role use case is focused on providing examples of how you can implement user roles, not on creating the fully defined system.

      For information about configuring the infrastructure, see Building your resource infrastructure. For more about projects, see Adding and managing projects.

    3. Enter WebAppTeam as the project name.
    4. Click Users, and then click Add Users.
    5. Enter email addresses for the individuals who can help you build and manage the infrastructure and cloud templates.
      For example, tony@mycompany.com,syliva@mycompany.com.
    6. In the Assign role drop-down menu, select Administrator.
      As Cloud Assembly administrators, these two users already have administrator access to the cloud accounts, infrastructure, and all projects. This step helps you understand the roles used in the later scenarios. In the later scenarios, you define project administrator and project member roles, which have different permissions.
    7. Click the Provisioning tab and add one or more cloud zones.
      Another reminder. This use case is about user roles.
  4. Develop a simple cloud template so that you can test the WebAppTeam project.
    This cloud template section is abbreviated. The focus is users and user roles as defined by projects, not how to create a cloud template.
    1. Select Cloud Templates > New.
    2. For the new cloud template name, enter WebApp.
    3. For Project, select WebAppTeam.

      Select the project for the cloud template.
    4. Select Share only with the project.
      This setting ensures that the cloud template is only available to project members. When you are ready to provide the cloud templates to other teams, you can select Allow an administrator to share with any project in this organization. Sharing the cloud template with other projects means that you do not have to maintain duplicate instances of the same base templates. You can move cloud templates from development projects to production projects so that catalog consumers can deploy to production infrastructure resources.
    5. Click Create.
    6. In the cloud template designer, drag the Cloud Agnostic > Machine component to the canvas.

      For more about configuring cloud templates, see Designing your deployments.

    7. Click Deploy.
    8. Continue iterating on the cloud template until you are ready to provide it to your consumers.
    9. Click Version and release and version the cloud template.
  5. Send the users the log in information using your most common method.

Results

In this use case, you made your two colleagues organization members. You then made Sylvia a Cloud Assembly administrator. You made Tony a WebApp project administrator. This user role configuration only works for small teams where you deliver deployed applications to your consumers rather than providing them with self-service access or a catalog.