Re: OVSDB M3 Status for MDSAL

Multanen, Eric W

Sam and all,

My understanding is that the MDSAL OVSDB is not a complete replication of the OVS schema for this release.

Here's a list of items that I could see being added to the model. Not enough or going too far?

- Ovsdb-node-augmentation
- OVS version
- External_ids
- Other_config
- Supported datapath & port types (e.g. dpdk)
- Ovsdb-bridge-augmentation
- Datapath type (I see Ed's got a patch going for this and flow node)
- Controller
- External_ids
- Other_config
- Protocols
- Ovsdb-termination-point-agumentation
- Ofport
- Mac
- Mac_in_use
- Mtu
- Statistics
- Link_speed
- Link_state
- Options
- External_ids
- Other_config


-----Original Message-----
From: ovsdb-dev-bounces@... [mailto:ovsdb-dev-bounces@...] On Behalf Of Sam Hague
Sent: Friday, March 13, 2015 11:01 AM
To: ovsdb-dev
Subject: [ovsdb-dev] OVSDB M3 Status for MDSAL

Hi all,

we need to report the M3 status next week on 3/19/15. The only status I am unsure of right now is the MDSAL OVSDB.

I think at a minimum we need to ensure the API (yang model) is set. Offest 0 projects have API freeze on 3/19/15 whereas we are offest 2 and have a functionality freeze so we need to answer the following questions to derive a status:

1. What else needs to be done for the model?
2. What is our confidence for delivering the mdsal southbound for the model?

For reference, we have these deliverables for lithium along with the current status:

- bug fixing: green
- sonar: green
- tempest: green
- adsal deprecation: green
- mdsal ovsdb (tentative): yellow

Thanks, Sam
ovsdb-dev mailing list

Join { to automatically receive all group messages.