In this model, an
organizational hierarchy (starting below
/root) contains managed objects owned and managed
exclusively by either
Cisco UCS Central or
Cisco UCS Manager.
Using this approach,
the best practice would be to create the organization with a distinctly global
name where the organization is only populated with globally managed objects. At
the same level within the hierarchy, a corresponding organization would only
contain locally owned managed objects.
Workload in the local
organization would only reference local
pools,
policies,
and
templates.
Workload in the global organization would only reference global
pools,
policies,
and
templatess.
Furthermore, using the
G- prefix in the
organization name would imply global scope for all objects. This reduces the
need for a
G- prefix for
each managed object within the organization.
Cisco UCS Central creates this global organization structure and subsequently
deploys down during the first association of a global service profile. Best
practices dictate that you differentiate the name within this global
organization structure. However, we still recommend using the
G- prefix names
for subordinate pools, policies, VLANs, VSANs, templates, and global service
profiles.