Manually Provisioning GCP Deployments

Access through:

Views > Inventory > Applications

or

Service Requests > Request Details

Available to:

Administrator, Operator, Operator with Approval Access Rights

When a user has requested a GCP deployment from the service catalog, you can provision it by clicking Deploy at the appropriate level of the tree in the Request Details dialog.

The following sections provide details for the manual deployment wizard. The pages and options displayed depend on whether you're deploying an entire service or a single component.

Note: When deploying an entire service, if the deployment of one or more components fails, Commander will still attempt to deploy other components in the service.

Name & Target page

Naming options: Naming options are not available if you're deploying an entire service as individual components - that is, if you clicked Deploy at the Service level in the Request Details dialog (rather than at the Component level).

GCP mandates that Deployment names comply with RFC 1035. Names must contain between 1 and 63 characters and must match the following regular expression:

[a-z]([-a-z0-9]*[a-z0-9])

Names must start with a letter, end with a letter or digit, and have as interior characters only letters, digits and hyphen.

  • Let the system name this service automatically: Use Commander's Virtual Service naming convention to name this deployment.

    If you select this option, you must edit the Virtual Service naming convention to adhere to GCP's naming rules. The default virtual service naming convention does not adhere to GCP's naming rules.

  • Manually name this service: If you don't want to use the Virtual Service naming convention, enter a name that's unique in the target project.

    If you select this option, you must enter a name that adheres to GCP's naming rules.

Note: You can review the name that will be applied on the Summary page, where you can edit it if necessary.

Deploy Type: Specify the policy for creating the resources in this deployment. The options are:

  • Create Or Acquire: By default, the deployment acquires any existing resources in the target project and creates the rest.
  • Acquire: Select this option if you have a number of resources already in your project, and you want to manage them together, as a single deployment.

Placement Options: Although the option you choose here allows Commander to preselect destination choices for you, you can change those selections throughout this wizard. The available options are:

  • User Specified: No destination is selected; the destination must be selected manually.
  • Automated Deployment: Uses the placement options configured for automated deployment. If you see the error "Automated deployment has not been configured", see Configuring Automated Deployment for Approved Service Requests to learn how to set up automated deployment.

Destination: Select the target project. If you chose Manually name this service and Commander detects that the name isn't unique in the target project, an error is displayed.

Components page

This page appears only when deploying an entire requested service - that is, you clicked Deploy at the Service level in the Request Details dialog, rather than at the Component level. All components in the service are listed. Custom components in the service are listed for information purposes only.

Deselect the components you don't want to deploy at this time.

Components are deployed in the order shown.

Custom Attributes page

Custom attributes allow you to provide more management information about your cloud infrastructure. Add or edit custom attribute values as required. To learn more, see Using Custom Attributes to Add Infrastructure Metadata.

Other Properties page

When deploying an entire service, values entered on this page will be applied only to the components of the service.

If the Expiry Date or Primary Owner form element has been added to the Component request form, users can specify expiry and/or ownership information for requested components. Their selection isn't displayed in the manual Service deployment wizard. In this case, you should deploy each component separately by clicking Deploy at the Component level of the Request Details, rather than at the Service level. Doing so ensures that you won't override the requester's individual selections for all components in the service.

See also Order of Precedence for Metadata and Service Settings.

  • Deployment Name: If you're deploying at the component level, the name that will be applied to the deployment is displayed, according to your settings on the Name & Target page. To change the name, click Edit. In the Modify VM Name dialog, if you enter a name manually, click Validate to ensure that it meets naming requirements and that it's unique in the target project.
  • Expiry Date: Click Edit to set or override the expiry date, or to specify that the service will never expire. See also Managing Service Expirations.
  • Expiry Group: If you're deploying at the component level, you can click Edit and select an expiry group from the drop-down.
  • Maintenance Group: If you're deploying at the component level, you can click Edit and select a maintenance group from the drop-down.
  • Owners: To edit ownership assignment, click Edit. In the Edit Ownership dialog, if the user you assign is a member of an organization, make sure to select the owner's organization to ensure the service is visible to organization members. To assign users, enter a username or email address. See also Assigning Service Ownership.

  • Service Request: When deploying a service request, the Release checkbox is visible and is enabled by default, so that components advance to completion automatically. When the Release checkbox is enabled, if one or more completion workflows have been assigned, the service request is automatically transferred to the completion workflow process. If no completion workflows are assigned, once all components in a service are deployed, releasing the components makes the service visible to the requester (for example, the Service Portal user).
    If there are manual steps in your provisioning process, disable the Release checkbox so that you can carry out these steps before the completion workflow starts. For example, you may need to install software, check operating system patches, or migrate VMs. Click Comment to enter more information for the service request comment log.

Summary page

A summary of your settings is displayed.

Policy Actions: If one or more policies will be triggered once deployment occurs, policy actions are listed here.

Click Finish to deploy the service or component.