Hierarchical Representation of Resources

Top Level Hierarchy	Description
System	All the common software modules that make up the EFA infrastructure would come 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 EFA. For example, Fabric, Visibility, Common, Tenant (can be used for grouping all common features like License and Security). This Component tree is extensible for adding new features and add-ons in EFA. All entities are represented as resources in EFA so that they become addressable.

EFA Health Resource Hierarchy

For example,

• Certificate Management: /App/System/Security/Certificate
• Fabric Named Fabric One: /App/Component/Fabric[id=FabricOne]

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

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