Manage Container Server Disks

On May 26, 2020, according to CoreOS reaching End of Life, container servers in OnApp also reached End of Life. Please contact support or your account manager on amteam@onapp.com for more details and further assistance. 

Container server storage is provided by disks. A disk is a partition of a data store that is allocated to a specific container server. Disks can be assigned as standard or swap disks. They can also be set as primary (that is, the disk from which an OS will boot).

Managing disks for the entire cloud is handled through the Control Panel's Settings menu. Disks for individual container servers are managed through the Control Panel's Container Servers menu. In this document you can find information on how to manage Container Server disks. 

Do not create multiple partitions on one disk for container servers. OnApp Control Panel supports only one partition per disk. In cases when you change disk partition, the CP might loose control of such a disk and the container server associated with it. If required, create additional disks instead.


Add Disks to Container Servers



Adding a disk to a container server will require that server should be rebooted. If a container server is running when you try to add a new disk to it, you'll be asked to confirm the reboot. To add a disk to a container server:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Click a container server's label to open its details screen.
  3. Click the Storage tab > Disks.
  4. Click the + button or the Create Disk button.
  5. Fill in the details:
    • Specify disk label.
    • Choose the data store to create a disk on from the drop-down list.
    • Move the slider to the right to specify the desired disk size.

Please note that support of secondary disks larger than 2 TB is limited. Certain operations might fail. This will be improved in future releases.

  • If you add a disk larger than 2 TB, you will not be able to mount or create a backup of such disk via OnApp Control Panel. These operations may be performed only manually inside a virtual server. Also, resize will not be possible for such disks.
  • You can perform the following operations with a secondary disk that is larger than 2 TB:
  • OnApp provides a RAW device available inside a VS that you may use. For example, you may create a GPT partition and format it using any available file system which can be mounted inside VS.
    • Move the Swap Space slider to the right if this disk is swap space.

    • Move the Require Format Disk slider to the right if this disk requires formatting.

    • Move the Mounted slider to the right if the disk should be added to FSTAB.

    • Specify its mount point. The maximum length of a Mount Point is 256 characters. Spaces are not allowed. No more than one slash is allowed. If the mount point is not specified the default mount point will be used:  

      /mnt/onapp-disk-#{disk.identifier}
    • Indicate the file system  - ext3 or ext4.

     6. Click the Add Disk button to finish.

Restrictions:

  • If you choose a Solidfire data store, the minimum disk size will be regulated by Solidfire Data Store Zone settings.
  • If container server and the Control Panel server belong to different networks, the hot attach transaction will fail.
  • If an additional disk has been created without  therequire format disk option and formatted/partitioned in another way, resize disk action may work incorrectly. Use the require format disk option when creating an additional disk,otherwise use disk resize option at your own risk.
  • When you add a new disk to acontainerserver, it automatically becomes available to that server.



Edit Container Server Disks



Primary and Swap disks

For primary and swap (Linux, FreeBSD) disks you may only change the label and the size.
You can easily resize disks when needed. The resize will fail if your current usage is greater than the new size you request. Note, that any changes on disk size will lead to reboot of your container server.

You can only increase the size of container server primary disks.


To change disk size:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Make sure your container server is powered off, then click its label to open its details screen.
  3. Click the Storage tab > Disks.
  4. Click the Actions button next to the disk you want to change, then click the Edit link.
  5. Enter a new disk label and size in GB in the fields provided.
  6. Click the Save Disk button. 

If you start Disk Resize transaction and then decide to cancel it, you will get the warning message. Click Proceed if you are sure that the resize is no longer in progress. Otherwise stopping Disk Resize transaction can be a dangerous operation and side effects can include file system corruption.

New disks

For new disks - those which were added after the container server was created - you can edit the following:

  • Label
  • Size
  • Require Format
  • Mounted
  • Mount Point
  • File System


Migrate Container Server Disks



You can migrate disks of your container servers to other data stores, which are allocated to the same Compute resource. Unlike Container Server migration – disk migration requires the reboot of the container server.
To migrate a disk:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Make sure your container server is powered off, then click its label to open its details screen.
  3. Click the Storage tab > Disks.
  4. Click the Actions button next to the disk you want to move to another data store, then click the Migrate button.
  5. On the screen that appears, select a target data store from a drop-down box.

  6. Click Start Migrate. 


  • You can only migrate disks to data stores in data store zones assigned to your bucket. 
  • You cannot migrate a disk to a data store with less capacity than the disk size.
  • If you move an 850GB disk between aggregates with 10GB actual usage, the 'dd' image of the local volume manager will take 850GB space, because the entire local volume manager is copied, includingzero 'dspace which may not be able to be recovered.

Delete Container Server Disks



To delete a disk:

  1. Go to your Control Panel > Cloud > Container Servers menu.
  2. Make sure your container server is powered off, then click its label to open its details screen.
  3. Click the Storage > Disks tab.
  4. Click the Actions button next to the disk you want to delete, then click Delete.
  5. In the pop-up window, move the Force Reboot slider to the right, then select the container server shutdown type.
  6. Move the Required Startup slider to the right to start up the container server automatically after the network is rebuilt.

    Steps 5 and 6 apply to disks ofcontainerservers that are on.

  7. Click the Destroy Disk button.

This will schedule the Transaction Server.