Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Short Description:  Community discussion on where ODL is heading and what we need to do to get there.

  • Detailed Description: Discussion and planning session for ODL Roadmap, features and challenges.  Bonus goal should be to create a wiki page that highlights the areas that we need more development resources and quick onboarding for those features/projects.
  • Topic Leader: Abhijit Kumbhare  Casey Cain
  • Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 20
  • Interested In Attending: If you are interested in this discussion and would like to participate in it, please add your name and email here (one name/email per line please). We'll use this information when building the schedule so that we minimize overbooking people where possible.

JSON-RPC improvements

  • Short Description:  Discuss recent improvements and gather new requirements for future releases

  • Detailed Description: JSON-RPC Ext has recently made some improvements like HTTP/WS bus protocols and AAA. We want to add writing 
  • Topic Leader: Shaleen Saxena (shaleen.external@gmail.com)
  • Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 1-15
  • Interested In Attending: Attend remotely.

...

  • Short Description:  Discuss revealing a new open source tool to facilitate model-to-model translations

  • Detailed Description: This is a public reveal of a proposed ODL tool library that helps facilitate model-to-model translations. We will cover why you might want to use this, what it can and cannot do, and example mappings. This tool follows a "translation by intent" philosophy that emphasizes declarative specifications but allows clients to wade into the translation pipeline from writing no code, to writing schema independent logic, to having full control over every detail of the output.
  • Topic LeaderAllan Clarke
  • Estimated Audience Size (1-15 / 15-30 / 30-50 / >50): 1-15
  • Interested In Attending: If you are interested in this discussion and would like to participate in it, please add your name and email here (one name/email per line please). We'll use this information when building the schedule so that we minimize overbooking people where possible.

Micro-services friendly nimble distribution and extensions

...