2017.05.25 LCOO General meeting

• Line 61: Containerized Control Plane Management Development Proposal: Jaesuk Ahn, Jamey McCabe Continue the process to finalize the Containerized Control Plane Development Proposal and on to gap analysis with Kolla and OS-Helm and other projects. https://review.openstack.org/#/c/445386/
• Line 76: Sampath Priyankara Finish gap analysis on Extreme Testing including looking at OSIC, ENOS, Browbeat, AT&T Resiliency Studio and NTTs current and proposed products

• Jamey McCabe General kick-off call for the Development Proposal (cross project effort) week of June 5-9 as agreed with Jaesuk Ahn (Unlicensed)
• Nancy McMurry (Unlicensed) and Jamey McCabe (Unlicensed) find the right AT&T players to bring into the development proposal the AT&T interests

Helm: (Planned for week of June 5)

• Set up a kick off call (what, how, asks) (Jamey)
• How do we collaborate 
  • use review.opestack.org for collaboration
  • Slack/IRC?
• A brief Summary/Milestone/ Deliverable description

Kolla:

• Set up a kick off call (what, how, asks) (Sundar)
• How do we collaborate 
  • use review.opestack.org for collaboration
  • Slack/IRC?
• A brief Summary/Milestone/ Deliverable description

Extreme testing:

Sampath updated the wiki page with task list and current status

Eris - Extreme Testing Framework for OpenStack

• All specialization leads try to use Sampath's page above as a model for getting more deliverable orientation going for these LCOO teams.
• Gautam Divgi (Unlicensed) and Sampath Priyankara to finalize collaboration approach for teh actions specified above and bring any other interested players to the effort. 

Noted in the meting that the Slack Channel for this effort should be used: https://lcoo.slack.com/ #testing

• Line 54: Define governance model in LCOO - See this page /wiki/spaces/LCOO/pages/13175601 which is our way of gathering feedback/proposal for any improvements in the governance of LCOO.  As shared in the Boston session we did a round of improvements just before the Boston Summit including opening up this site to unauthenticated read access.  We can continue to change though - feel free to edit as a sort of proposal there and generate discussion and we can add to a future General session.
  
• Line 56: Log Messages improvement - was a discussion and informal promise to try to combine efforts with LCOO. FYI - not known if active but this Development proposal already exists and might be a place to start:

  https://review.openstack.org/#/c/440309/9/development-proposals/proposed/traceability-in-services.rst

• Line 59: RBAC (Role Based Access Control) - was a discussion that both AT&T and Verizon (and it's known others from past LCOO discussions) would like to start jointly contributing. 
  

Logging:

• Create a page (similar to extreme testing)

• Josh Durbin Next steps and action plan (by Josh)

RBAC

• Andrew Ukasick Initial requirements and concepts gathering (Andy)

• NTT is also interested in this topic

• Line 124:

  
  

  • Better release notes for all projects would help to identfiy what has changed.##all-projects#actionitem
  
  
  • Better description of what happens with mixed versions, i.e agents behind one or two versions.##all-projects#actionitem
  
  
  • TODO: call out projects that are doing upgrade impacts but not documenting them in the release notes.##all-projects#actionitem
  
  
  • Test/certify backward compatibility to n+2   +1

Sent out recap email to openstack-dev

http://lists.openstack.org/pipermail/openstack-dev/2017-May/117239.html

• Each organization with Development team members try to generate response to the TODO: action item and specifically respond to this e-mail

Skip level Upgrade

• (we got feedback from nova devs to put a document plan for n-2 to n upgrade) we can push for that action. (Shintaro)

• Line 192:

  
  

  • Start communicating in the openstack-operators mailing list with the tag 
  
  
  • Will send out a summary of this meeting 
  
  
  • Agree to setup a security  chat forum - either IRC or SLACK (or both)
  
  
  • Next meeting with the ? group?

  
  

Security:

• yeeling lam and Andy to follow up on this

• THose listed to continue e-mail discussion and possibly setup a verbal meeting to help.
• Jamey McCabe Copy the general user-committee mailing list to help larger community and thos not on private e-mail exchanges
• Jamey McCabe Bring summaryto next weeks PWG meeting since Andy notified that they also had taken action item to try to facilitate cross WG.