Skip to content

Meeting minutes: Feb 28, 2019

Jump to bottom
JK Lee edited this page Mar 15, 2019 · 2 revisions

Meeting Time and Location

9:30 am to 12:00 am PDT (GMT - 8), Barefoot Networks, 4750 Patrick Henry Dr, Santa Clara, CA 95054

Attendees

Barefoot Networks: JK Lee, Mickey Spiegel

Cisco Systems: Ramesh Sivakolundu

YANG model revision

This was a working meeting dedicated to revise the YANG model.

One goal is to easily facilitate changes and extensions per each implementation-specific requirement. For example, one may want to encode two different ID data (network ID, switch ID) into the switch ID metadata field. We found YANG model/compiler allows augmentation of a model by defining the extensions in a separate file and compile them together. Since OpenConfig today adopts YANG 1.0, we mainly looked at the Augment feature of YANG 1.0. and decided to use it for extending metadata field sub structure.

As the need to extend the switch ID seems common, we also extended the switch ID field in the main YANG model hosted in the Apps WG: we introduced a mask to the switch ID field, hence one can easily divide the 32b field into 2 sub fields. A more complicated extension on the switch ID or any other fields can be accommodated via the Augment feature of YANG.

In case someone wants to add a new data type or unit, we still recommend to modify the main YANG model hosted in the WG. The use of YANG Augment -- defining an extension outside of the Apps WG YANG model -- is recommended for defining multiple sub-fields inside of a field defined in the YANG model.

Additional decisions made on the YANG model:

  • Add a capability flag (boolean) to each metadata such that each switch/implementation can clearly declare which metadata are supported. So far, the declaration was implicit: not listing a metadata type in the model meaning it's not supported.
  • We also revised and clarified other field definitions such as level 1 and level 2 port types. We deemed that 'interface' is a better term than 'port'. Mickey Spiegel will open a PR with those changes.

Next Steps

  • Next meeting is scheduled for Thursday March 21, 2019. We will discuss the scope of INT (broad vs narrow) and discuss terminology changes such as port to interface.
Clone this wiki locally