OOM Meeting Notes - 2017-10-25

Owned by David S
Last updated: Oct 25, 2017
1 min read

Agenda:

  • Formalize / refine scope for Beijing - 

    • @David S to create initial list and scope visual.

    • @Michael O'Brienand @David S to work on the DevOps epic

    • Add more Consul tests for Beijing release. Create an epic for that.

      • Health checks

      • API checks (put, get, etc)

    • Initial release goals for OOM (Work in progress): OOM for Production-Grade Deployments

      •  @Roger Maitland @John Ng @David S @Sylvain Desbureaux @Roger Maitland @Marc-Alexandre Choquette @Mike Elliott @Borislav Glozman @Avi Chapnick @Michael O'Brien @Arthur Berezin: 

  • One topic for other teams: define guidelines to make sure component teams build their components so that the full extent of K8S features can be used across.

    • @John Ng @David S @Sylvain Desbureaux @Roger Maitland @Marc-Alexandre Choquette @Mike Elliott @Borislav Glozman @Avi Chapnick @Michael O'Brien. @David S to organize.


  • Who's going to the santa clara event?

    • @David S @Marc-Alexandre Choquette @Michael O'Brien @Eric Debeau

    • Let's make sure we demo OOM and CI using K8S at the event. 

      • Deployment and Running with OOM

      • CI: Validate built with deeper health checks with OOM

      • CNCF??

  • DCAE vs OOM:  DCAE may have different requirements, mostly around control and data planes. Need to align on architecture. Maybe OOM should have those capabilities.

  • How do we tag the Amsterdam specific code and make Commits for Beijing independent?

  • OPNFV: