Migration zones

Compute nodes are grouped into migration zones for use by application instances. Essentially, a migration zone provides a way to organize a collection of resources virtually. It consists of a defined set of compute nodes (with any categories and tags) and connectivity to storage (one or more storage pools).

Migration zones act as boundaries around a set of compute nodes of any category or tag. Anytime an application starts in a particular migration zone, it utilizes only the compute nodes in that zone. Migration zones can be useful for departmental or regional boundaries, for specific application computing requirements, or in cases where customers have high security requirements; for example, for service providers that have multiple customers in banking or government and must keep a customer’s computing resources isolated from other customers. The ThinkAgile CP platform guarantees separation without needing to separate hardware physically.

One compute node can belong to one migration zone, and migration zones can connect to one or more storage pools. There is no limit on the number of nodes in a migration zone, and nodes can be added or removed from a migration zone without any impact on running applications. For a migration zone to support application instances, it must be connected to at least one storage pool. The resources in a migration zone must also be allocated to at least one virtual datacenter before they can be used to run application instances. Application instances can migrate among nodes within a migration zone, but cannot migrate to nodes outside of a migration zone.

For more information about working with migration zones, see the following topic:

Migration zones