15.1 Requesting Business Services

Roles that Can Perform This Task: Cloud Administrator, Organization Manager, Business Service Owner

A deployed business service starts as a request. The request defines the business service, including its name, contract period, and workloads. As soon as you submit the request, it goes through an approval and build process that you can track until the business service is deployed.

Cloud Manager logs the identity of the user who initiates the action for a Change Request. The requester's name is reported in the Events dialog as well as in the email notification for the request (if notification is enabled).

  1. On the main navigation bar, click Business Services, then click the Requests tab.

  2. Click Create to display the Create Business Service Request dialog.

  3. Provide the following details for the business service:

    Service Name: Specify a name that is different than any other business service names for the business group. You can use letters, numbers, and the following special characters: space, hyphen, underscore, apostrophe, percent, ampersand, and period. The name must begin with a letter or number and have a maximum length of 110 characters.

    Start Date: Click to select the date you want the business service to be available.

    Expiration Date: Click to select the date you want the business service to no longer be available. If you don’t want the business service to expire, delete the date from the field.

    Contract Length: If an expiration date is selected, this field displays the total number of months for the contract.

    Organization: Select the organization for which you are creating the business service. You can select the business group before the organization, in which case the correct organization is automatically selected.

    Business Group: Select the business group for which you are creating the business service.

    Creator: Displays your user name.

    Business Purpose: Provide details that explain the purpose or justification for the business service. This information is visible to the business service’s approvers during the request approval process.

  4. Add a workload to the business service:

    1. Click Add to display the Select Workload Template dialog.

      The dialog displays a list of workload templates. A template provides the base settings and costs for the workload.

    2. Select the workload template from which to create the workload, then click OK to display the Configure Workload dialog.

    3. On the Resources tab, configure the workload.

      1. Under Workload, specify a name for the workload.

      2. Select a Service Level to use for this workload.

        NOTE:You must specify a Service Level in order to activate settings on the Windows Settings or Linux Settings tabs.

        If the workload template you have chosen for this workload has an associated resource pricing package that is compatible with the service level you choose, the Resources field becomes active and a list of available resource pricing packages is available for selection.

        You cannot customize the resources for the selected Service Level if they are locked. For additional information about the Resources settings, click the button.

      3. Select a resource pricing package from the list.

        For each resource, the range (that is, the intersection of the values of the resource pricing package and the workload template) of its resources is listed, along with the potential cost savings for the user if the resource pricing package is chosen. The minimum savings (that is “from”) reflects the cost of the workload if you use all of the minimum resource values of this package. The maximum (that is "save up to") reflects the maximum savings if the workload is configured with the maximum resource values for this package.

      4. (Optional) If the Resources settings are unlocked, customize the resources allocated to the workload.

    4. Click the Disks tab to configure the workload’s disks.

      The workload’s mandatory disks are listed. The mandatory disks are created with the workload and cannot be customized.

      If the Add action, located above the list, is available, there are optional disks you can create for the workload. Click Add, then specify the size for the disk.

      For additional information about the Disks settings, click the button.

    5. Click the Networks tab (if it is displayed), select a network interface card, then assign the network and configure the network address and name servers.

      For additional information about the Networks settings, click the button.

    6. (Optional) Click the Windows Settings tab (if it is displayed), then provide the following information, depending on the type of zone.

      CMOS zone: Complete the following settings:

      • Domain Settings:

        Computer Name: Specify the computer name for the virtual machine. Ensure that you specify only the computer name setting (windows) or host name setting (Linux) that is assigned to the machine, and not its fully qualified domain name.

        Domain or Workgroup: Select Domain or Workgroup, then specify the name of the domain or workgroup to which you want the virtual machine added.

        Domain Administrator User ID: This applies only if you are adding the virtual machine to a domain. Specify a domain administrator user ID that can be used to add the virtual machine to the domain specified in the Domain field.

        Domain Administrator Password: This applies only if you are adding the virtual machine to a domain. Specify the password for the domain administrator user ID.

      • Installation Settings:

        Run Once Commands: Specify any Windows Run Once commands that you want run during the first log in to the virtual machine. For information about Windows Run Once commands, see the Microsoft Windows documentation.

        If the administrator user adds a run once command for a workload template, only administrator users can view and modify the option, and the Installation Settings section is hidden from organization users. If the administrator leaves the field empty, organization users can view and use the field.

      EC2 zone: Complete the Installation Settings:

      • Cloud-init Configuration: Specify the appropriate settings.

      OpenStack zone: Complete the Installation Settings:

      • Cloud-init Configuration: Specify the appropriate settings.

      If you do not provide this information at this time, a Build Administrator or Cloud Administrator must provide it during pre-build configuration of the workloads.

      For additional information about the Windows Settings settings, click the button.

    7. (Optional) Click the Windows Licensing tab (if it is displayed), then provide a Windows product key, and registration name.

      If the Cloud Administrator has pre-populated the Windows Product Key field, the data is masked. You cannot copy this data.

      If you do not provide this information at this time, a Build Administrator or Cloud Administrator must provide during pre-build configuration of the workloads. For additional information about the Windows Licensing settings, click the button.

    8. (Optional) Click the Linux Settings tab (if it is displayed), then provide the following information, depending on the type of zone.

      CMOS zone: Complete the Domain Settings:

      • Hostname: Specify the host name to assign to the virtual machine.

      • Domain Name: Specify the domain for the virtual machine (for example, netiq.com or provo.netiq.com).

      • Root Password: Specify the Linux Root password to assign to the virtual machine.

      EC2 zone: Complete the Installation Settings:

      • Cloud-init Configuration: Specify the appropriate settings.

      OpenStack zone: Complete the Installation Settings:

      • Cloud-init Configuration: Specify the appropriate settings.

      If you do not provide this information at this time, a Build Administrator or Cloud Administrator must provide it during pre-build configuration of the workloads.

      For additional information about the Linux Settings settings, click the button.

    9. (Optional) Click the Console Access tab, then set the password for VNC access to the workload.

      If you do not provide this information at this time, a Build Administrator or Cloud Administrator must provide it during pre-build configuration of the workloads. For additional information about the Console Access settings, click the button.

    10. Click OK to save the workload and add it to the Workloads list.

  5. Add any additional workloads to the business service.

    You can add additional workloads by repeating Step 4 or by copying an existing workload and then modifying it as necessary. To copy a workload:

    1. Select the workload to copy, then click Copy.

    2. Select the number of copies to create, and provide a unique name for each copy.

    3. Click OK.

      The new workloads are added to the Workloads list.

    4. Edit each new workload to provide any missing information.

      Each new workload contains as much of the original information as possible, but information such as network addresses, Windows computer names, and Linux host names are not copied because they need to be unique for each workload.

  6. (Optional) Give other users ownership rights to the business service.

    The Users list lets you see any users who have been explicitly assigned ownership rights to the business service. It does not show users who inherit ownership rights to the business service through their roles.

    1. Click the Users tab, then click Add.

    2. Select users from the two lists.

      The Members list displays all users who are members of the business service’s organization. The System Users list displays users who are not members of the organization.

      You can Shift-click and Ctrl-click to select multiple users (or user groups).

    3. Click OK.

      The users are added to the list.

  7. Click Save to add the request to the Requested Services list without submitting it.

    or

    Click Submit to add the request and submit it for approval.