Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Managing OpenStack servers


This topic provides instructions for performing the following actions on a provisioned server:

Note

  • An upgraded SOI is not covered under Quota calculations, as Quota management is supported only for the servers provisioned by OpenStack Provider 2.0.00.
  • You may expect incorrect quota calculations for servers provisioned in an upgraded environment. Cloud Administrator must ensure that the quota allocation is done properly. 

To start or stop a server

  1. From the list of servers in the Servers link of the My Services tab in the My Cloud Services Console, highlight the server that you want to start or stop.
  2. Use one of the following methods to perform the action:
    • Click the Start start_button.jpgicon or the Stop stop_button.jpgicon.
    • Click the Operator Action operator_action_button.jpgicon, and select the action (Start or Stop).
    • Right-click the server, and choose the action from the Server pop-up menu.
      serverflyout.png
      After the server is started or stopped, the status is Running or Stopped, as shown in the following figure:
      info_message.png

To suspend or resume a server

The Suspend Resume feature allows you to suspend or resume a provisioned server in OpenStack. You can add functionality to use the Suspend Resume feature by customizing your OpenStack installation as described in Adding-suspend-and-resume-operator-actions.

  1. From the list of servers in the Servers link of the My Services tab in the My Cloud Services Console, highlight the server that you want to suspend or resume.
  2. Choose one of these methods to perform the action:
    • Click the Operator Action operator_action_button.jpgicon and select the action (Suspend or Resume).
    • Right-click the server and choose the action from the Server pop-up menu.
      serverflyout.png

After the server is suspended or resumed, the status is Suspended or Resuming.

To shut down a server

  1. From the list of servers in the Servers link of the My Services tab in the My Cloud Services Console, highlight the server that you want to shut down.
  2. Use one of the following methods to perform the action:
    • Click the Shutdown shutdown.pngicon.
    • Click the Operator Action operator_action_button.jpgicon and select the action (Shutdown).
       The server is shut down.

To add a disk to a server

  1. Log on to BMC Remedy Action Request System (AR System) by using your end-user credentials.
  2. On the left side of the window, click the vertical Applications menu, and select Cloud Lifecycle Management > My Cloud Services Console.
  3. On the My Services tab of the My Cloud Services workspace, click the Servers link.
  4. From the displayed list of servers, as shown in the following figure, select the server to which you want to add a disk, and click Modify Actions  ModifyCPU.gif.
    AddDisk1.png
  5. From the menu, select Add Disk.
  6. In the Submit Request dialog box, as shown in the following figure, select your option and click Next.
    AddDisk2.png

    Note

    BMC Cloud Lifecycle Management cloud administrators can increase disk sizes for provisioned OpenStack servers.

  7. Review your request details, as shown in the following figure, and click Submit.
    AddDisk3.png

To modify CPU count and memory size for a server

Note

BMC Cloud Lifecycle Management cloud administrators can create memory and CPU options and option choices in the OpenStack Provider. For more  information, see Creating-options-and-option-choices-in-the-OpenStack-Provider.

(Applies only for OpenStack Provider 4.1.1) VMs that are provisioned by using certain specific images of Cloudwatt (for example, CentOS) become unusable if you modify the Flavor (CPU or RAM).

  1. Log on to BMC Remedy Action Request System (AR System) by using your end-user credentials.
  2. On the left side of the window, click the vertical Applications menu, and select Cloud Lifecycle Management > My Cloud Services Console.
  3. On the My Services tab of the My Cloud Services workspace, click the Servers link. 
  4. From the displayed list of servers, as shown in the following figure, select the server for which you want to modify memory and CPU option choices, and click Modify Actions ModifyCPU.gif.
    ModifyCPU1.png
  5. From the menu, select an available post-deployment modify action.
  6. In the Submit Request dialog box, as shown in the following figure, select your options and click Next.
    ModifyCPU2.png
  7. Review your request details, as shown in the following figure, and click Submit.
    ModifyCPU3.png

To install software on a server

Note

BMC Cloud Lifecycle Management cloud administrators can create installation software options and option choices for the OpenStack Provider. For more information, see Creating-options-and-option-choices-in-the-OpenStack-Provider.

  1. Log on to BMC Remedy Action Request System (AR System) by using your end-user credentials.
  2. On the left side of the window, click the vertical Applications menu, and select Cloud Lifecycle Management > My Cloud Services Console.
  3. On the My Services tab of the My Cloud Services workspace, click the Servers link.
  4. From the displayed list of servers, as shown in the following figure, select the server on which you want to install the software, and click Modify Actions ModifyCPU.gif.
    SwIns1.png
  5. From the menu, select an available post-deployment modify action.
  6. In the Submit Request dialog box, as shown in the following figure, select your options and click Next
    SwIns2.png
  7. Review your request details, as shown in the following figure, and click Submit.
    SwIns3.png
    The software is deployed on the server.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*