Attribute Inheritance Overrides
Attribute inheritance is relevant primarily in multi-tenancy environments where Hitachi Storage Viewer domains are used to partition the database to maintain security controls. In this configuration, a hierarchical structure provides a parent-child relationship that controls access to data and also a structure for inheriting configurations from parents. For example, a Managed Services Partner (MSP) supports many client companies, each with its own Hitachi Storage Viewer domain. See the
Hierarchical Domain Structure for Attribute Inheritance diagram. Attributes created at the MSP domain are inherited by the child domains. In this case, the child domains may want to
Override Inherited Attribute Values, since it is likely that each company would have its own values for an attribute.
Likewise, an enterprise may simply want to use Hitachi Storage Viewer domains to segment the data within its environment. For example, subsidiaries or divisions within an organization have different business assets and therefore different reporting needs. In this case, an enterprise might configure a root domain, with sub-domains for each of its subsidiaries. An attribute defined for the parent company’s domain will be inherited by its subsidiaries.
Use the
Hierarchical Domain Structure for Attribute Inheritance diagram to visualize a hierarchy that supports attribute inheritance.
Figure 24.1 Hierarchical Domain Structure for Attribute Inheritance
Attributes have the following inheritance characteristics, based on a domain hierarchy:
• An attribute at the parent level is visible to all of its children.
Example: An attribute created at Domain A will be visible to all other domains.
• Children inherit attributes and values from any domain that is higher in its hierarchy path.
Example: An attribute created at Domain B will be visible only to Domains C and D. Likewise, an attribute created at Domain A will be visible to both Domains F and G.
• Duplicate attribute names are not allowed in a single hierarchy path. When creating an attribute, Hitachi Storage Viewer checks for duplicate attribute names and it will not create the attribute if it already exists in either a child or parent domain.
Example: Duplicate attribute names cannot exist in the A-F-G Domain path.
• Duplicate attribute names are allowed in sibling hierarchies.
Example: Domain B could have an attribute that is a duplicate of a name in Domain F.