search

ietf-ivy-wg / network-inventory-yang

Other
2 stars 4 forks source link

Unclear boundary for Ivy work #35

Open nigel-r-davis opened 9 months ago

nigel-r-davis commented 9 months ago

It is clear that we do not have a tight enough definition of the boundary on the Ivy work. We need to understand what is in scope and what not. It is not practical to list all things in scope, so instead we need rules against which we can evaluate whether something is in scope or out of scope.

Clearly, there are some things we would all agree are in scope and other things we would agree are out of scope. Identifying the inherent properties of those things will help.

But there are things that we do not agree about and even if we had a complete definition, there are things on the boundary or that straddle the boundary.

I emailed the list with some thoughts on how to organize things on a "map" to help us define the boundary.

I have attempted to sketch a map of things (over simplified in many places) that includes some questions and some sketch definitions. I would be happy to discuss this on our next call. IvyBoundary.pptx

nigel-r-davis commented 8 months ago

I have updated the slide pack to reflect what I presented. IvyBoundary.pptx

nigel-r-davis commented 8 months ago

I think the next action is:

italobusi commented 2 months ago

2024-09-11 Base Network Inventory weekly call

prmanna commented 1 month ago

Base Inventory should include

  1. RFC8348: chassis, backplane, container (slot, ...), power supply, fan, sensor, module (board, ...), cpu, battery, storage device etc a. virtual NE -- Needs to deep dive little more to understand if any field required in base inventory draft. b. Logical Separation - it should be automatically covered Base Inventory. This separation does not create any new entity, instead it needs some association management. c. SAP attachment -
  2. Topology - Separate draft
  3. Software - Separate draft
  4. Location - Separate draft
  5. Entitlement/License - Separate draft
  6. Power - Separate draft (ie. used power, etc). It has a relation with GREEN.

Not in IVY Scope (but has relation)

  1. Access Control - This is operation. Can be separate draft. It will have a relation with policy, user-management. also with Virtual NE management.
  2. Logical/Virtual Operation Control on IVY - Need more deep dive.
italobusi commented 1 month ago

2024-09-25 Base Network Inventory weekly call

Base Inventory should include

  1. RFC8348: chassis, backplane, container (slot, ...), power supply, fan, sensor, module (board, ...), cpu, battery, storage device etc a. virtual NE -- Needs to deep dive little more to understand if any field required in base inventory draft. b. Logical Separation - it should be automatically covered Base Inventory. This separation does not create any new entity, instead it needs some association management. c. SAP attachment -
  2. Topology - Separate draft
  3. Software - Separate draft
  4. Location - Separate draft
  5. Entitlement/License - Separate draft
  6. Power - Separate draft (ie. used power, etc). It has a relation with GREEN.

Not in IVY Scope (but has relation) 1. Access Control - This is operation. Can be separate draft. It will have a relation with policy, user-management. also with Virtual NE management. 2. Logical/Virtual Operation Control on IVY - Need more deep dive.

prmanna commented 1 month ago

Virtual NE vs. Logical NE.pptx

italobusi commented 1 month ago

2024-10-02 Base Network Inventory weekly call

There are differences between VNE and LNE, as outlined by the Virtual NE vs. Logical NE.pptx slides

Logical NEs are considered outside the scope of IVY because they represent logical partitioning of NE resources

More discussion is required on the Virtual NE definition and management (within the scope of the SW network inventory model). The base model has been defined to be open to support other type of NEs, besides physical NEs, as well as SW components via proper augmentations (such as those under definition in the SW network inventory model).

prmanna commented 3 weeks ago

Virtual NE vs. Logical NE.pptx Updated with example for Cisco Virtual NE and stacked switch case.