There are two types of OS templates - CT OS templates and VM OS templates. They are propagated differently across the virtualization nodes registered in OACI.
Automatic Propagation of CT OS Templates
The logic of CT OS template propagation in OACI is the following:
When a node is being registered in OACI, it gets a location assigned to it. OACI checks what OS templates are installed on other nodes within this location. If some of those templates are absent on a new node, OACI copies them.
That task is triggered every five minutes on the Instance Manager (IM). During this task the IM executes the "select" request to the database to find which node has missing OS templates.
The "Locations" are implemented to separate the networks the hardware nodes may belong to. The networks may reside in different countries with different languages. Moreover, the networks may be isolated from each other, in that case the OS template copying is not be possible.
Default OS templates of containers are delivered from yum repositories, thus their presence in different locations is expected.
Manual Copying of VM OS Templates Between Virtualization Nodes
VM OS templates created manually on a virtualization node are not propagated automatically to other virtualization nodes registered in OACI.
You can manually copy VM OS template from one node to another by doing the following:
Log in to the destination node via SSH with root credentials and copy OS template to this node from the source node.
scp -r root@hostname_of_source_node:/vz/vmprivate/vm_template_file /vz/vmprivate/
For example, scp -r email@example.com:/vz/vmprivate/w2k12-plesk_onyx-17.0.pvm /vz/vmprivate/
On the destionation node, register the copied VM OS template in Virtuozzo.
prlctl register /vz/vmprivate/template_directory_name
For example, prlctl register /vz/vmprivate/w2k12-plesk_onyx-17.0.pvm
- Register the copied VM OS template in OACI. For more details, refer to http://download.automation.odin.com/oa/7.0/oapremium/portal/en/operations_providers_guide/72277.htm