Orca uses Cluster on Demand (COD) as a backend resource manager. Since COD is designed as an extension of the Shirako leasing core, Orca can support a ranger of resource managers, if needed. This guide focuses on inventory management as defined by COD. Please refer to this page for definitions of some of the terms used in this guide.
In the current COD model, the data center owns all inventory. Inventory is described in a central database, which is managed by the center administrator. The center administrator is responsible for creating one or more sites and transferring inventory to each site. Inventory can be transfered from the center to a site and vice versa. New inventory items can only be registered by the center administrator. Once an inventory item is added to the center database, it can be transferred to a site.
COD supports a range of inventory types. This page lists all inventory types supported by the system. This page also provides detailed information about the steps to configure and register each inventory type. Here we summarize the configuration and registration process.
The steps required to start managing an inventory item are:
This option is suitable for inventory items that allow the installation of custom software on them, e.g., a virtual machine monitor.
This options is suitable for inventory items that do not allow the installation of custom software on them, e.g., a NetApp filer.
You can find more information about installing the Node Agent service here
The Orca Configuraton Tools can be used to perform some of the tasks described in the previous section.