Container Dashboard Overview

The Container dashboard is divided into five sections, each reflecting the following Container details:

1. The Container Status section of the screen displays:
   • The current status of the Container .
   • The information on the resources consumption by the Container: coming close to, reaching, or going beyond the limits set for the Container generates a resources alert .
   • The current status of the templates and packages. The Container software which does not suggest updating is marked as Up-to-date .
   • The hostname of the Node where the Container is hosted (it is possible to migrate the Container to another one ).
   • The Container last 1, 5, and 15 minutes system load averages.
   • The last performed and next scheduled backups.
   • The total period of time during which the Container has been on without rebooting or stopping.
2. The data to be found in the Container Configuration section have to do with the Container identity - you can see its name and ID. Additionally, you may learn what sample defines the settings of the Container (and apply another one by clicking Change ), and see what OS template the Container is based on (and update the OS template by clicking Update ), and which application templates are currently installed in it (and add a new application template or remove an installed one by clicking Add/Remove ).
3. The Container Network Configuration section allows you to see:
   • the Container hostname (if set);
   • the information on the IP addresses of the Container eth (bridged) and venet0 (routed) interfaces. The information is available only if the IP addresses were set during the Container creation. Clicking Configure opens the screen where you can configure the Container networking settings.
4. The Tasks section provides quick access to performing the following operations:
   • Changing the Container name, description, OS template version, start-up and offline management options (the General Settings link ).
   • Changing the root/Administrator password of the Container (the Password link ).
   • Changing the resources share allocated to the Container (the Resources link ).
   • Configuring the virtual disk volumes of the Container (the Volumes link ). The C: volume is always present in the Container as the mount point for the root.efd image file.
   • Installing new applications to or uninstalling existing ones from the Container (the Templates link ).
   • Changing the Container hostname, IP address, DNS server IP address and search domains and configuring the mode of the Virtual Network adapters (the Network Settings link ).
   • Configuring the network bandwidth of the outgoing traffic for this Container (the Network Shaping link ). To define the default Container network shaping settings on the given Hardware Node, see the Configure Shaping screen .
   • Starting or stopping the Container (the Start/Stop link ). Depending on the Container state, only that operation is accessible that complies with its current state.
   • Restarting the Container (the Restart link ).
   • Managing the services running on the Container except for the xinetd -dependent services (the Services link ).
   • Managing the Container files and folders (the Files link ).
   • Backing up the Container, renewing or removing the existing backup, restoring the Container (the Backups link ).
   • Activating the firewall and configuring its mode (the Firewall link ).
   • Creating a Container clone (the Clone Container link ). A clone is an exact copy of an existing Container.
   • Moving the Container to another Hardware Node (the Migrate Container link ).
   • Launching Parallels Power Panel to manage the Container in a separate window (the Open Parallels Power Panel link).
   • Connecting to the Container via SSH (the Terminal Login link ).
   • Logging in to the Container via Remote Desktop Connection (the Remote Desktop link ).
   • Configuring all the parameters of the backup operation and performing that operation on the current Container (the Back Up Container link ).
   • Saving important data from the damaged Container and repairing the Container by creating a new temporary Container (the Repair Container link) .
   • Recovering the original state of the Container in case you have unintentionally modified, replaced, or deleted any file that is part of an application or OS template, and the action has brought about the Container malfunction (the Reinstall Container link ).
   • If you are managing a Container residing on the Hardware Node with the Linux operating system installed and wish to stop your Container, bear in mind that there is a two-minute timeout for the Container shutdown scripts to be executed. If the Container is not stopped in two minutes, the system forcibly kills all the processes in the Container. The Container will be stopped in any case, even if it is seriously damaged. To avoid waiting for two minutes if you are operating a Container that is known to be corrupt, you may use the Power Off link.
   • Removing the Container if you don't need it any more (the Delete Container link ).
5. The Container Resources section summarizes the information on the current consumption of the CPU, memory and disk share allocated to the Container: the Resources column lists these resources, the Used , Free , and Total columns display the corresponding values in percentage terms and in diagrams. The percent value is calculated not in proportion to the total disk space of the Hardware Node, but in proportion to the quota on using the Node disk space by the Container.

Apart from the operations available in the Tasks section, the Parallels Infrastructure Manager toolbar provides you with access to the following operations:

• starting or stopping the Container (the Start/Stop link);
• restarting the Container (the Restart link);
• backing up the Container (the Backups link on the Manage menu);
• launching Parallels Power Panel to manage the Container (the Open Parallels Power Panel link on the Login menu). You can use this feature if:
  1. The offline management for the Container is enabled.
  2. A valid IP address is assigned to the Container.
  3. The IP address you have used to log in to Infrastructure Manager does not coincide with that of the corresponding Container.
• connecting to the Container via SSH (the Terminal Login link on the Login menu);
• logging in to the Container via Remote Desktop Connection (the Remote Desktop link on the Login menu);
• suspending the selected Container(s): a suspended Container stays put, and so its processes and services do, to be later resumed from the checkpoint. Suspending Containers is a good method to disengage the Hardware Node recourses for a certain period of time or saving the state of current operations which can be quickly launched again afterwards. Remember, that repairing, restarting and reinstalling a suspended Container can change the saved state of the Container, so these actions are not recommended for suspended Containers;
• changing the Container name, description, resources management configuration and start-up and offline management options (the General Settings link on the Configure menu);
• changing the root/Administrator password of the Container (the Password link on the Configure menu);
• changing the network settings (the Network link on the Configure menu);
• configuring the network bandwidth (the Shaping link on the Configure menu);
• changing the Container resource settings (the Resources link on the Configure menu);
• configuring the virtual disk volumes of the Container (the Volumes link on the Configure menu);
• installing new Container applications (the Templates link on the Configure menu);
• changing the firewall settings (the Firewall link on the Configure menu);
• changing the Container resources configuration by changing the sample the Container is based on (the Apply Sample link on the Configure menu).

Please send us your feedback on this help page