Managing OpenStack servers

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

Note

  • The new My Cloud Services console introduced in BMC Cloud Lifecycle Management version 4.5, does not support the Remove Disk, Suspend and Resume TRO operations. Perform these operations using the legacy My Cloud Services Console.
  • An upgraded SOI is not covered under the Quota calculations because Quota management is supported only for the servers provisioned by OpenStack Provider 2.0.00.
  • You might experience incorrect quota calculations for servers provisioned in an upgraded environment. The cloud administrator must ensure that the quota allocation is done properly. 

To start or stop a server

You can start or stop a server by using the new My Cloud Services Console or the legacy My Cloud Services Console:

To use the new My Cloud Services Console to start or stop a server, see Managing servers in a service for details.

 Click here for the legacy My Cloud Services Console.
  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  icon or the Stop  icon.
    • Click the Operator Action  icon, and select the action (Start or Stop).
    • Right-click the server, and choose the action from the Server pop-up menu.

      After the server is started or stopped, the status is Running or Stopped, as shown in the following figure:

To shut down a server

You can shut down a server by using the new My Cloud Services Console or the legacy My Cloud Services Console:

To use the new My Cloud Services Console to shut down a server, see Managing servers in a service for details.

 Click here for the legacy My Cloud Services Console.
  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  icon.
    • Click the Operator Action  icon and select the action (Shutdown).
      The server is shut down.

To manage the system disk of a server

You can perform the following tasks to manage the system disks for a server in an OpenStack service offering:

Adding disks to a server

You can add a disk to a server by using the new My Cloud Services Console or the legacy My Cloud Services Console:

 Click here for the new My Cloud Services Console.
  1. Log on to My Cloud Services portal by using your end-user credentials.
  2. On the left side of the window, in RESOURCE TYPE, click Servers.
    A list of available servers is displayed, as shown in the following figure:


  3. Click the server name to view the server's HARDWARE configuration and add a disk, as shown in the figure below:
  4. In the HARDWARE pane, click Add Disk.
  5. In the Add Disk dialog box, select an available disk size from Optional Disks, as displayed in the figure below:

  6. Click OK.
  7. Click Submit Changes.
  8. In the Submit Changes dialog box, as shown in the following figure, click Yes to confirm the addition of a disk of the selected size to your server:

    The disk is now added for the server.
 Click here for the legacy My Cloud Services Console.
  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  .
  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

    Note

    BMC Cloud Lifecycle Management cloud administrators can increase disk sizes for provisioned OpenStack servers. Also, when a user adds a disk of non-integer size (for example: 0.5 GB), the Add Disk activity fails and the selected disk quota value (0.5 GB) gets deducted from the available disk quota of the user.

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

Viewing disks of a server

To use the new My Cloud Services Console to view the existing disk details of an OpenStack server, navigate to the My Resources > Server configuration and view the details in the HARDWARE pane.

To use the legacy My Cloud Services Console to view the existing disk details of an OpenStack server, see To view the system disks for a server in the legacy console.

Removing disks of a server

To remove the system disks of an OpenStack server, see To remove a system disk from a server in the legacy console.

Notes

  • To remove a disk from a server, you must first stop the server.
  • You can remove only the added disks from a server. You cannot remove the original OS disk assigned when the server was provisioned.
  • You cannot remove the system disks by using the new My Cloud Services Console.

To modify CPU count and memory size for a server

You can modify CPU count and memory size for a server by using the new My Cloud Services Console or the legacy My Cloud Services Console:

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.
  • VMs that are provisioned by using certain specific images of Cloudwatt (for example, CentOS) become unusable if you modify the Flavor (CPU or RAM).
 Click here for the new My Cloud Services Console.
  1. Log on to My Cloud Services portal by using your end-user credentials.
  2. On the left side of the window, in RESOURCE TYPE, click Servers.
    The list of available servers is displayed, as shown in the following figure:


  3. Click the server name to view the server configuration to update the CPU and RAM details, as shown in the figure below:
     
  4. Drag the sliders to the right as shown in the figure below:

  5. Click Submit Changes.
  6. In the Submit Changes dialog box, as shown in the following figure, click Yes to confirm the selected modifications of CPU or RAM to your server:


    The CPU or RAM details as selected for the server is updated.
 Click here for the legacy My Cloud Services Console.
  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 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 .
  5. From the menu, select an available postdeployment modify action.
  6. In the Submit Request dialog box, as shown in the following figure, select your options and click Next.
  7. Review your request details, as shown in the following figure, and click Submit.

To install software on a server

You can install software on a server by using the new My Cloud Services Console or the legacy My Cloud Services Console:

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.

 Click here for the new My Cloud Services Console.
  1. Log on to My Cloud Services portal by using your end-user credentials.
  2. On the left side of the window, in RESOURCE TYPE, click Servers.
    The list of available servers is displayed, as shown in the following figure:



  3. Click the server name to view the server configuration, as shown in the figure below:
  4. In the SOFTWARE pane, select the software to be installed, as shown in the figure below:
  5. Click Submit Changes.
  6. In the Submit Changes dialog box, as shown in the following figure, click Yes to confirm the installation of the selected software on your server:

    The software is installed on the server.
 Click here for the legacy My Cloud Services Console.
  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 list of servers, as shown in the following figure, select the server on which you want to install the software, and click Modify Actions .
  5. From the menu, select an available postdeployment modify action.
  6. In the Submit Request dialog box, as shown in the following figure, select your options and click Next
  7. Review your request details, as shown in the following figure, and click Submit.

    The software is deployed on the server.

To add local OS users on a server

You can add local OS users on an OpenStack server by using the new My Cloud Services Console or the legacy My Cloud Services Console:

Note

To enable postdeployment user provisioning, BMC Cloud Lifecycle Management cloud administrators must first create a BLPackage with local properties and also define the Add local user option and option choice for the Azure Provider. See Creating options and option choices in the OpenStack Provider for details.

 Click here for the new My Cloud Services Console.
  1. Log on to My Cloud Services portal by using your end-user credentials.
  2. On the left side of the window, in RESOURCE TYPE click Servers. 
    The list of available servers is displayed, as shown in the following figure:



  3. Click the server name to view the server configuration.
  4. In the SOFTWARE pane, select Create User option.
  5. Enter the user name and password details.
  6. Click OK.
  7. Click Submit Changes.
  8. In the Submit Changes dialog box, click Yes to confirm the addition of user for the server.
 Click here for the legacy My Cloud Services Console.
  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 list of servers, as shown in the following figure, select the server on which you want to add a local user, and click Modify Actions .
  5. From the menu, select an available postdeployment modify action.

  6. In the Submit Request dialog box, as shown in the following figure, enter the user name and password details and click Next.

  7. Review your request details, and click Submit.

A local user is added on the provisioned VM with the user name and password specified by you.

To suspend or resume a server

The Suspend or 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 icon and select the action (Suspend or Resume).
    • Right-click the server and choose the action from the Server pop-up menu.

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

Note

You cannot suspend multiple servers simultaneously.

Was this page helpful? Yes No Submitting... Thank you

Comments