Active Container

The first step in making a container active is to associate its definition with a host. The second step is to set the resource boundaries, namely, to assign the minimum CPU reservation and the memory cap for the container. The container must be associated with a host that can support these resource boundaries. An active container can also be referred to as being deployed, in the sense that the container definition has been pushed out and resides on a host.

When creating an application-based container with the New Container wizard, a match expression can be provided which identifies the processes associated with the application. All processes corresponding to the match expression are then automatically moved under this container. Upon container activation, an entry in the /etc/project database is created on the host that the container is associated with. Correspondingly, the matching processes are then moved under the project name for the container. Once the processes are moved, all resource utilization data is collected and saved for the container.