Make an empty repository called test that represents our project.The best way to explain subtree merges is to show by example. The 'subrepository' is stored in a folder of the main repository. and clicking on 'Display URI of last query' i would get the URL /api/node/mo/uni/tn-TrentinoNetwork.xml?query-target=self that could be used on a GET POST request to collect info concerning the MO fvTenant = TrentinoNetwork later on.Typically, a subtree merge is used to contain a repository within a repository. By using this rule paired with the tree-based hierarchy of the MIT, you can concatenate the relative names of objects to derive the Dn, providing a unique address in the MIT for a specific object. Relative names are unique in their namespaces, meaning that within the local scope of an MO, there can only ever be one Rn using that name. For the most part, the Rn is a prefix prepended to some naming properties. MOs have relative names (Rn), which are built according to well-defined rules in the model. A more generic form of this naming structure is: For example, top is the package and Root is the class in the name topRoot, and fv is the package (fabric virtualization) and Tenant is the class in the name fvTenant.

Each class has a name, which is composed of the package name and a class name. Within the model, there are different packages that act as logical groupings of classes, with similar entities placed into the same package for easier navigation of the model. The exception to this rule is the root of the tree, which is a special class called topRoot.

All classes have a single parent and can contain multiple children. The classes define the entities that are instantiated as MOs and stored in the MIT. Whenever information is displayed, it is read through the REST API, and when configuration changes are made, they are written through the REST API through it any information can be retrieved, including statistics, faults, audit events - THIRD FLOOR!Īll objects, so, are seen as configurable entities and their structure are represented as classes. The REST API is the interface into the ACI MIT that allows manipulation of the object model state the REST interface is used by the APIC CLI, GUI, and any programming language able to generate standard REST methods as POST, GET and DELETE messages with the payload encapsulated through either JSON or XML encoding, containing the API methods or MO descriptions - SECOND FLOOR!

The APIC REST API ( application programming interface) is a programmatic interface that uses REST (r epresentational state transfer) architecture - FIST FLOOR! :)Īn MO can represent a physical object, such as a switch or adapter, or a logical object, such as a policy or fault - GROUND ZERO! :) Let's start building up the palace from the foundations. MOs are abstractions of the fabric resources. Each node in this tree is an MO and each object in the ACI fabric has a unique distinguished name (DN) that describes the object and its place in the tree (remember, it cannot be renamed once configured, you have to cancel it and reconfigure for renaming, keep in mind when you have to decide the name convention to adopt for of all MOs!!!). The hierarchical structure starts at the top (Root) and contains parent and child nodes. Each node in the tree represents a Managed Object (MO) or group of objects that contains its administrative state and its operational state. but before, just a few concepts as introduction at the topic!įirst of all a link !introduction/aci-programmabilityĪll the physical and logical components that comprise the ACI fabric are represented in a hierarchical management information model (MIM), also referred to as the management information tree (MIT). the brain of ACI solution and how to interact with it. This time we move a little toward the direction of.

Git cola subtree