Time | Item | Who | Notes |
---|
5 min | Openness of our meeting approach. We had a complaint to and reminder from the User Committee that our approach seemed less than open. Determine what change is needed reference: 2017-02-02 LCOO Coordinators Debate points/Options:- We did form initially with the goal to facilitate collaboration of contributors and reduce overhead for non-members. It was basically a formation agreement with Foundation, with one floated alternative being to form some independent team.
- Proposed: Change open up the company profiles section to all. -1 -1 -1
- Proposed: Clarification to UC about restricted pages (Security thing) and sub-teams +1 +1 +1 +1 +1
- Proposed: Do not refer to restricted pages from non-restricted or put disclaimer at this point +1 +1 +1 +1 +1
- Proposed: Move to IRC +1
- Proposed: publish meetings in Youtube: See example of Helm project team:https://www.youtube.com/watch?v=b83bVArDuEg -1
- Proposed: Notify of this (every 2 weeks coordinators) meeting ahead of time via User Committee DL and include link to list of all meetings: Meeting notes. Publish/Announce all standing meetings, so both our main meeting and the roadmap team meetings would be announced in email. +1 { +1 +1 +1
Proposed: Technical Meeting every other week Decide on this in next roadmap meeting - We are not aiming to be as simple as most WG - in the pattern of 1 meeting every 1-2 weeks, so which meetings to broadcast seems a little more difficult.
- Notify of Roadmap meetings ahead of time? (these are every 2 weeks)
- Andy already sent response to clear up possible confusion over openness of meeting minutes and other LCOO Notes.
- Andrew Ukasick and Aditya Mani (Unlicensed) to announce roadmap team meetings in advance via the User Committee email list each time
- Jamey McCabe to announce LCOO Coordinators meeting (main meeting) in advance via the User Committee email list each time
| Jamey, Edgar, Shilla, Andy |
3 min | Co-chair nomination - Is this a good time to have a chair or co-chair other than AT&T. if so nominate and - Related but even deeper: Perhaps update to our Charter and start elections. If it's the right time - perhaps a sub-tem to take it offline. | Jamey |
|
10 min | In 1/26 Roadmap bi-monthly meeting which had attendance from AT&T, Intel, Reliance Jio and SKT, It was suggested for better attendance to meet in US morning times. +1 Related: Communication Plan drafted here. Some possible debate points: - what do we want the composition of these teams to be (seems we want Global) and if so is Asia daytime needed to promote that?
- Is it working? Perhaps we need Asia companies to commit and perhaps lead at these times.
- if we want to support global membership are there better means to coordinate schedules commitment and notification to attend for the US staff
- Proposed: Coordinator meetings should happen US Morning time +1
- if it is not between midnight and 6am here in Korea. +1
- Proposed: Roadmap meetings determined in next weeks meeting +1
- would IRC (versus voice/video) be helpful +1
- would publishing the meeting on Youtube be good. See example of Helm project team:https://www.youtube.com/watch?v=b83bVArDuEg
| All |
|
20 min | Difference between Summit and Forum: https://wiki.openstack.org/wiki/Forum (DEADLINE FEB 6) Discuss presentation ideas for Boston Summit: https://www.openstack.org/summit/boston-2017/call-for-presentations/ - What is value we bring the community?
- What messages do we want to convey?
- How are we positioning ourselves in relation to the OpenStack product working group?
- Do we need to form a sub-team to plan and act on this?
- Do we want a Working Group session for LCOO in Boston? We do have this reqeusted already - Shill did it - I (jamey) see it on my request list. Fantastic!!
Proposed: Joint presentations to introduce LCOO For example, in Barcelona the new (refurbished?) Telecom/NFV Functional Team had sessions to introduce themselves (or so it seemed?) Proposed: Birds of a feather session for LCOO +1 Jamey volunteers to request this Milestones and Action Items leading to Queen's Forum https://www.openstack.org/summit/boston-2017/ - 2/6 FST's kicked off
- 2/20 FST Roadmap for Queens
- 3/6 Draft User Stories
- 3/13 Meet with PWG
- 3/ 27 Submit Forum time slot requests
| Andy, Jamey |
|
5 min | Intel Items Update (Sonu Sreenivasan is joining the call to give an intel update on the 4 items) - Containerization of Control Plane - Kolla. White Paper to available soon.
- Zero downtime upgrade for Core 6 and Ironic (Starting with Ocata and onward). Relted to Rollign Upgrades
- Scale Testing of Core 6 projects at 500 nodes for reliability for specific reference workloads and deployment architecture with injected failures. Looking for feedback on workload and architecture from LCOO
- MOP Documentation for Ease of Installing Openstack using Ansible and Kolla
|
|
|