Next TAPI Call:
|30 mins||TAPI Documentation|
|20 mins||Streaming Model|
|60 mins||Equipment Model: slot and sub slot cases||Arturo Mayoral|
1) How a pluggable equipment (Small-Form-Factor equipment category according the model) can be related to an “Access-port”, which is to the best of our knowledge the entity related to the logical tapi models (tapi-topology:node-edge-point). <n> You are correct that AccessPort is the bridge between the logical model (NEPs etc.) and the PhysicalModel. There is more explanation of this in the ONF Core model document TR-512.6_OnfCoreIm-Physical (I suspect you have this already, but if not, then get https://www.opennetworking.org/wp-content/uploads/2018/12/TR-512_v1.4_OnfCoreIm-info.zip and locate it in there). </n>
This is the block diagram we are trying to construct but we miss the red relationship.
<n> I will use the UML (which should have direct equivalence in the Yang). The relationship is carried by the connectorPin property of AccessPort.
This is of type ConnectirPinAddress:
The property provides you with the UUID of the Equipment, which will let you locate the SFF Equipment. It also provide pin/connector details for more complex cases (for the SFF Equipment, it is probably not that relevant).
Note that the relationship is one way. It is assumed that the client is using the TAPI interface to populate a data base and can set up the reverse navigation itself upon receipt of the AccessPorts. </n>
2) Secondly, if you see the drawing we have depicted two possible equipment configurations.
i. The first possibility is that a “Circuit-Pack” equipment (i.e., a Shelf’s board) does just contain holders equipped with “pluggables” (Small-Form-Factor equipment category according the model). In this case the model is pretty clear.<n> This is the expectation (see also TR-512.6 mentioned earlier). </n>
ii. The second case, a bit more complicated, is that there are multiple sub-slots within a “Shelf” (Sub-Rack equipment category according the model) slot. <n> The expectation is that an equipment has holders and a holder may be occupied by an equipment.
After some discussions on "horizontal vs. vertical" holder models, where a circuit-pack may occupy more slots (horizontal) or a fraction of a slot (vertical), together with the case a same slot may be occupied by a single pack or by two packs, this is the temporary conclusion:
Nigel Davis there can be cases where the slot configuration may follow complex composition rules similar e.g. to the SDH payload structure rules. For further study. The idea here is that all holder schemes within a particular Equipment are declared in a flat structure (as equals) and then any dependencies are stated as rules between holders and groups of holders. So a Slot that could alternatively be considered as two halfslots would have three holders declared where anything present in one of the halfslots would block the full slot. This scheme appears to be least disruptive to an existing equipmet where an unexpected opportunity for use of halfslots becomes available.. The scheme also allows form more flexibility than the simple hierarchies discussed above. Clearly there can be default rules for simple cases and shorthand for expressing the rules for common complex cases.