Requesting Services or Changes to Services
In Commander, you can request a service or request a change to a service the same way that a Service Portal user can make those requests. If workflows have been configured, the requested service or change request automatically goes through the workflow process.
In this topic:
Views > Service Requests
All Access Rights Levels
To request a new service:
- On the Service Requests page, click Request New Service.
Tip: To save time, you can select an existing service request and click Copy Request to copy the service request. You can then make any changes to the pre-populated form, and submit the request.
- On the Services page, for the service you want, click Add to Request to add a service.
Tips: If you can't find the service you need:
- If you're looking for a service shared by another user, make sure Include Shared Services is enabled.
- Enter text in the Search field to filter the list of available services. Only the service name and description are searched (categories aren't searched).
- If categories have been applied to the services you have permission to see, you can filter by category. Only services matching all selected categories are retrieved.
- Complete the form that appears.
- If the Destination form element has been added to the Service form, from the Destination area, select a deployment destination available to you on the cloud account hosting the service you're requesting, or select Let the system decide.
Service catalog costs are updated for each valid destination for the requested service; if you select Let the system decide, the expected destination is displayed.
Note: If the
$DESTINATION$deployment parameter is specified as part of the approval process, it will override your selection.
- When you've completed the Service form, click Next.
- In the Customize Component form, complete the fields.
Tip: If you see the Override icon on this form, you can override the value set for the service as a whole. For example, for a service that contains four components, you could set an expiry date for the service as a whole and then override this date for one of the components. The other three components would take the expiry date from the service. Note that once you have overridden a value for a component, changing the value for the service has no effect for that component. Click the Override icon again to remove the override.
- To add another service to the request, click Add.
Note: If Commander is in single-service request mode, the Add button doesn't appear.
- When you've completed the form, click Submit Request.
You must complete all fields marked with an asterisk (*). Complete the fields in the order they are displayed. If you go back and re-populate fields of a form, you may lose your some of your selections.
- If you request a service request through a copy, don't copy a request submitted in the Service Portal if the service has an assigned key pair. Key pairs are assigned differently in Commander and the Service Portal. See Enabling Key Pair SSH Connections to Amazon EC2 VMs to learn more.
- If you navigate to another page before submitting your request, the contents of your request are saved until you sign out.
You can request a change to a deployed service or virtual service.
Examples of change requests are:
- decommission a database
- change the owner of an auto scaling group
- apply a rightsizing recommendation to a VM
- add more memory, CPU or storage resources to a VM
Views > Inventory
All Access Rights Levels
To request a change to a service:
- Click the Infrastructure or Applications tab.
- Select a service in the tree.
- Select Actions > Change Management > Request Service Change or Request Service Change.
- In the Select Change dialog, select the service request change you want and click OK.
- In the Select Service Change dialog, make configuration changes you want, and click OK to submit the change request.
The menu options available depends on whether you are making a change request for a service or a virtual service.
- If you change custom attribute values for a virtual service, its VM children don't inherit the new values. If you change ownership or expiry information for a virtual service, its children inherit the new values. See also Order of Precedence for Metadata and Other Service Settings.
- Some requests for resource changes may involve an automatic reboot during change request fulfillment. For information on whether a reboot will be performed for resource changes, see When Resource Changes Require Reboots.