Hierarchical Representation of Resources

Top Level Hierarchy	Description
System	All the common software modules that make up the XCO infrastructure are covered under this node. For example, Database, K3s, Services, HA, and Certificate. There can be more sub-nodes under this as deemed necessary.
Component	This node groups all components (features) that are provided by XCO. For example, Visibility, Fabric, Tenant, Asset, and Common. Common groups all features like Firmware, License, and Fault. All entities are represented as resources in XCO so that they become addressable.

XCO Health Resource Hierarchy

Example:

• Certificate Management: /App/System/Security/Certificate
• Fabric named FabricOne: /App/Component/Fabric?name=FabricOne

Representing managed objects (for example, Fabric, Tenant, EPG, Devices, and Interfaces) and the software components (for example, License, Security, and Fault) as resource has the following advantages:

• Generic APIs can be provided for accessing the entities.
• All the resources can also be active participants in the system (for example, raise alerts or alarms).
• It provides a pluggable data model to support newer network types.
• It provides a deterministic way for modeling the operational model.