About built-in CVM
CAS CVM is built in CloudOS as a container and is named as CloudOS. It enables you to manage CVK hosts without installing CVM. The built-in CVM has most functions of CAS and uses the similar logic to manage physical resources.
|
|
In this document, CAS CVM is also called CVM, and CAS CVK is also called CVK for simplicity. |
Restrictions and guidelines
A CVM host pool and cluster use the same name. If multiple clusters exist, make sure each cluster has a corresponding compute node created.
You cannot delete the storage volumes used by cloud disks from a CVM or CVK storage pool.
In a bulk migration of cloud hosts, you cannot migrate only the storage of the cloud hosts if the cloud hosts come from different hosts.
CVM does not support editing or deleting the cloud host rules created by OS in the current version.
CVM supports only IPv4 configuration in the current version.
Make sure a minimum of one CVK host exists in a CVM cluster that is already associated with a compute node.
The menus do not refresh automatically after operations are performed on some resources (such as cloud hosts, clusters on CVM, and hosts). You need to refresh the webpage manually to view the latest data.
The menus do not refresh automatically after you create, delete, or migrate clusters, hosts, or cloud hosts. You need to refresh the webpage manually to view the latest data.
Do not migrate a hard disk to a local storage pool. Otherwise, the hard disk cannot function normally.
A shared disk mounted to multiple cloud hosts does not support disk backup.
Do not edit or delete the OS-created cloud host rules on CVM. Otherwise, it cannot synchronize with the affinity group list.