Article ID: 129254, created on Aug 15, 2016, last review on Aug 15, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5
  • Plesk Automation 11.5


Customer configured several provisioning attributes for the resources in the OACI Service Template, but VE was provisioned on the "wrong" node which does not have all attributes. How OACI choses proper HW node for VE provisioning?


OA Cloud Infrastructure unlike other modules uses more sophisticated method for choosing node suitable for provisioning. Let me explain both mechanisms that it uses.

The first mechanism is Locations. In Cloud Infrastructure, you can configure standard Operations Automation provisioning attributes to act as Node Location attributes and use them to bind servers of specific customers to specific nodes in Cloud Infrastructure.

The process of configuring a node to host specific servers includes the following steps: 1. Creating a provisioning attribute in Operations Automation. 2. Configuring the attribute to serve as a Node Location attribute. 3. Assigning the Node Location attribute to the node in Cloud Infrastructure. 4. Assigning the Node Location attribute to the CI Virtual Environments Limit resource type. 5. Creating a Service Template and including the CI Virtual Environments Limit resource type in this Template.

Also, Odin Automation for Cloud Infrastructure uses tags to detect nodes that are appropriate for provisioning specific servers based on OS type. The tag assignment mechanism is based on two objects: OS templates and nodes. This mechanism works as follows: 1. You register a node in Cloud Infrastructure and set tags for it. If necessary, you can also configure the tags of an already registered node. 2. You then set up an OS template and assign to it the same tags as the ones assigned to the node. 3. You create a server on the basis of the template you set up in Step 2. 4. The system checks the tags of the template and of all available nodes. If the tags of the template match those of a node, the server is created on this node.

You may obtain more information about these mechanisms in the following guides:

Locations: page 621 of Provider's guide

Tags: page 45 of Deployment guide

Search Words


PACI Attibutes ignored when VE is created

Hardware nodes not available while they are successfully added

e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065 33a70544d00d562bbc5b17762c4ed2b3 5b048d9bddf8048a00aba7e0bdadef37 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF