Manage Container Servers

Container Server is a regular VS based on default CoreOS template. This type of server allows the user to customize the server to implement integration with Docker or other container services. In this document you can find information on how to manage Container Servers. 


View Container Servers


To view all container servers deployed in the cloud:

  1. Go to your Control Panel > Cloud > Container Servers menu to see an overview of all container servers in the cloud. 
  2. The page that loads will show the list of container servers together with their: 
    • operating system
    • label. Click the label to see the container server details.
    • VIP status (enabled or disabled). Click the icon to enable/disable VIP status of a particular container server.
    • IP addresses
    • allocated disk size
    • RAM
    • user - the owner of this container server. Click the user name to see the owner details.
    • power status. Click the on/off buttons to change the status.
  3. Click the Actions button next to the container server for the quick access to the list of container server actions (the list of actions displayed depends on the container server status):
    • Reboot
    • Recovery reboot
    • Shutdown
    • Startup
    • Recovery startup
    • Unlock

To search for a particular container server, click the Search icon at the top of the container server list. When the search box appears, type the text you want to search for and click the Search button.


View Container Server Details



To view details of a specific container server:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Click the label of the container server you're interested in.
  3. The screen that appears loads the container server propertiesnotesactivity log and tools for managing your container server.

Container Server Properties

Container server properties page gives a general overview of the container server details:

  • VIP status (on/off). Click the icon to change the status.
  • Template the container server is built on
  • Power status & On/Off/Reboot buttons.

    Clicking the OFF button performs a graceful shutdown and then powers off the container server after the timeout set in Configuration settings.

  • Segregated Container Server. This field appears if the container server is segregated from another container server. Click the label of the container server to view the details of the container server from which the current server is segregated. 
  • FQDN (fully qualified domain name)
  • Compute resource. Click the Compute resource name to see its details
  • Login credentials.To log in, use the following credentials: 
    • user - 'core'
    • password - password from the container server details' page
  • Owner. Click the owner name to see its details.
  • IP Addresses. Only the first five IP addresses are displayed on the container server properties page. To view the list of all container server IP addresses, mouse over IP addresses area or go to the Networking tab > IP Addresses tab.
  • Auto-backups - move the slider to enable or disable auto-backups for this server. For more information refer to Manage Container Server Backup Schedules.
  • Estimated Price per hour. This sum does not take into consideration the free limits for resources set in the bucket. Therefore, the final price for the server might differ from the sum indicated here.

  • CPU(s)
  • CPU priority or CPU units
  • Disk Size
  • Memory
  • CPU Usage (%)
  • Data Sent
  • Data Received

Notes

The Notes section lists brief comments or reminders for a container server. You can add either Admin's or User's notes. The Admin's note will be available to cloud administrators. Click the Actions icon in the Notes section of the page to add admin's or user's note.

Container Server Management

  • Click the Tools button to expand the Tools menu with the container server management options.
  • Use the top menu to manage your container servers' statistics/networking/storage options.


Edit Container Server




You can edit label, CPU and RAM resources for container servers. To edit the a container server:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Click the label of the server you want to edit, to show its details screen.
  3. Click the Tools button and select the Edit Container Server link.
  4. Change label, CPU cores, CPU priority/units and RAM values, and click the Save button.

Rebuild/Build Container Server Manually



If you haven't checked the Build Container Server option during the container server creation process, you will have to do this manually after the container server has been created. Building a container server is the process of allocating physical resources to that container server.

To build a container server manually or rebuild the container server on the same (or another) template:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Click the label of the container server you're interested in.
  3. On the screen that appears, click the Tools button and then click Rebuild Container Server.
  4. On the screen that pops up, enter the encryption passphrase.

  5. Move the Start СS after rebuild slider to the right if you want to have your container server started automatically after it is built.
  6. Click the Rebuild Container Server button to finish.

After you rebuild your container server all data will be lost.

Migrate Container Server



You can migrate container servers using a hot or cold migration method:

  • Hot migration is the migration of container servers with or without disks between compute resources that share common data stores or data store zones.
  • Cold migration is the migration of container servers with disks between compute resources with local storage or across compute zones.

Hot Migration

You can migrate an online container server from one compute resource to another compute resource that are both utilizing local/shared/IS storage or across zones. There are two types of hot migration:

  • Compute Resource - migration of a container server from one compute resource to another
  • Compute Resource and Storage - migration of a container
  • server with disk from one compute resource and data store to another

Compute Resource

To hot migrate container server:

  1. Go to your Control Panel > Cloud > Container Servers.
  2. Click a label of a container server that you want to migrate.
  3. Click the Tools button and click the Migrate Container Server button.
  4. In the Migration Type box, select Compute Resource and click Next
  5. Select a Target compute resource from the box and click Next
  6. At the final step of the wizard, you can see the migration summary and select the following check boxes: 
    • Cold-migrate when hot-migration fails - select the check box to apply cold migration in case of the hot migration failure
    • Are you sure you want to migrate? - select the check box to confirm the hot migration
  7. When you are finished, click the Submit button.

Compute Resource and Storage

To hot migrate container server:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Click the label of a container server you want to migrate.
  3. Click the Tools button and click the Migrate Container Server button.
  4. In the Migration Type box, select Compute Resource and Storage (Hot) and click Next
  5. Select the following destination resources: 
    • Target compute zone - select a destination compute zone. The list includes compute zones that you have access to within the same network (i.e. KVM to KVM but not KVM to Xen). 
    • Target compute resource - select a destination compute resource
    • Target data store for disk - select a destination data store for each disk. The list includes available data stores associated with the compute zone and compute resource that you selected earlier.
  6. At the final step of the wizard, you can see the migration summary and select the following check boxes: 
    • Cold-migrate when hot-migration fails - select the check box to apply cold migration in case of the hot migration failure
    • Are you sure you want to migrate? - select the check box to confirm the hot migration
  7. When you are finished, click the Submit button.

After migration, the power status of your container server remains the same as before the migration. If you migrate a container server that's running, the whole process is almost unnoticeable. 

Cold Migration

Cold migration enables you to migrate container servers with disks between compute resources with local storage or across compute zones. To cold migrate container server:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Click the label of container server you want to migrate.
  3. Click the Tools button and click the Migrate Container Server link.
  4. In the Migration Type box, select Compute Resource and Storage (Cold) and click Next
  5. Select the following destination resources: 
    • Target compute zone - select a destination compute zone. The list includes compute zones that you have access to within the same network (i.e. KVM to KVM but not KVM to Xen). 
    • Target compute resource - select a destination compute resource
    • Target data store for disk - select a destination data store for each disk. The list includes available data stores associated with the compute zone and compute resource that you selected earlier.
  6. At the final step of the wizard, you can see the migration summary and select the Are you sure you want to migrate? check box to confirm the migration.
  7. When you are finished, click the Submit button.

If you change the compute resource or data store zone, the billing will be changed according to the prices set for that new zone in the bucket. The new estimated price per hour for a VS is displayed at the bottom of the VS migration screen.

After migration, the power status of your container server remains the same as before the migration. If you migrate a container server that's running, the whole process is almost unnoticeable. 
OnApp administrators can control user access over container server migration. Using OnApp permissions, you can allow/forbid users to perform migration of all container servers, or their own servers only. This is handled via the Control Panel's Roles menu.


Set VIP Status for Container Server



If a compute resource fails or reboots, the system migrates container servers to another compute resource, one container server at a time. The order container servers are migrated in is random. However, you can give a server "VIP" status, and this will give that server priority in the migration queue. 

To set or remove VIP status for a container server:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Use the icon in the VIP column next to a required server to change switch on/off the VIP status.


Segregate Container Server



If required, you can instruct OnApp to make sure a container server is never booted on the same compute resource as another specific container server. You can also remove segregation if required.

  • Container servers can only be segregated from other container servers built by its owner.
  • Container servers can only be segregated from container servers within the samecomputezone.
  • Container servers cannot be segregated from container servers running on the same compute resource.
  • The segregated container server is not automatically migrated to anothercomputeresource.

To isolate one container server from another:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Click the label of the container server you want to segregate.
  3. On the screen that appears, click the Tools button, then click Segregate Container Server.
  4. In the dialogue box that pops up, use the drop-down menu to choose a server you want to keep away from.
  5. Click the Segregate Container Server button to finish.

To remove segregation:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Click the label of the container server you want to segregate.
  3. On the screen that appears, click the Tools button, then click Desegregate Container Server.
  4. In the dialogue box that pops up, click the OK button to finish.


Container Server Power Options



To manage container server power options:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Click the label of the required server.
  3. Click the Tools button on the container server's screen to expand the Tools menu.
  4. The Tools menu enables you to perform the following power actions on container servers (the exact list shown depends on the container server status):
    • Reboot Container Server - powers off and then restarts the container server.
    • Reboot in Recovery- powers off and then restarts the container server in the recovery mode.
      For container servers with enabled encryption the temporary login is "root" and password is "recovery".

      For container servers with password encryption disabled, the server root password will be used to reboot in recovery.

    • Suspend  - stops a container server, changes its status to suspended and disables all the other actions on container server, unless unsuspended.

    • Shut Down Container Server – pops up a dialogue box, where you can either Shut Down container server (terminates the container server gracefully), or Power Off container server (terminates the container server forcefully).
    • Startup Container Server - queues a start-up action for a container server that's currently powered off.
    • Startup on Recovery - starts the container server in recovery mode with a temporary login ("root") and password ("recovery").
    • Boot from ISO - boots the container server from an ISO. You can boot container servers from your own ISOs or the ISOs that are uploaded and made publicly available by other users. If you boot a server from an ISO with the RAM requirement larger than the container server's RAM, the transaction will fail.  Make sure that you have enabled the Any power action on own container servers permission for the user to have access to this feature.

      As soon as you boot a container server from the installation ISO, OnApp may lose control of any components (networks, disks) !!! The only available actions will be start and stop a container server. Be aware, that all the contents of the disk may be also deleted.

Container Server Administrative Options



To manage a container server power options:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Click the label of the required container server.
  3. Click the Tools button on the container server's screen to expand the Tools menu.
  4. The Tools menu enables you to perform the following administrative actions on container servers:
    • Reset Root Password - resets the root password for this container server (the password is displayed in container server information).

    • Change Owner - pops up a dialogue box with a drop-down of all users on the system, enabling you to pass ownership of the container server to the user selected from the list. If you have any recipes for this container server, you will be also prompted to confirm if the recipe should be moved to another user. 

      Note that you cannot change the ownership of a recipe which you do not own, even if it is assigned to yourcontainerserver.

Delete Container Server



Shut down the container server before destroying it. If you are deleting a container server that is running, the server will be deleted after the time set in Timeout Before Shutting Down VSs configuration parameter.

To remove the container server from the cloud:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. On the screen that appears, you'll see the list of all container servers in the cloud. Click the label of the server you want to delete.
  3. On the container server's screen, click the Tools button, then select Delete Container Server.

IMPORTANT:

  • You won't be able to restore a container server after deleting it.
  • Deleting a container server removes all data stored on thatcontainerserver.