Versions Compared

Old Version 9

changes.mady.by.user Jamey McCabe

Saved on

compared with

New Version Current

changes.mady.by.user Jamey McCabe

Saved on

Key

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

Date

at UTC 1400: http://bit.ly/2jZ6Qbg

Meeting Link to join: https://join.att.com/meet/jm6819/B4KB04PR or Toll Free : 8443439499 (USA, Global)     Conference ID: 71345239   Call-170202.ics

Attendees

Goals

  • Coordinate Staff, dates and cross company communications
  • Finalize staff for Roadmap Functional Specialty Teams
  • Coordinate staff going to PTG
  • Set Milestones for

    Shintaro Mizuno

  • Jill Sales
  • Megan Rossetti
  • Jaesuk Ahn
  • Kunal Shah
  • Andre Pollard
  • Abdelhadi Chari
  • William Criswell
  • Andrew Ukasick

Goals

  • Resolve recent LCOO communication questions and suggestions
  • Set Activities and Milestones for Boston Summit Queens Forum/Scope submission

Discussion items


Time

ItemWhoNotes/Summary/Decisions
 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:
  1. 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.
    1. Proposed: Change open up the company profiles section to all. -1 -1 -1
    2. Proposed: Clarification to UC about restricted pages (Security thing) and sub-teams +1 +1 +1 +1 +1
    3. Proposed: Do not refer to restricted pages from non-restricted or put disclaimer at this point +1 +1 +1 +1 +1
    4. Proposed: Move to IRC  +1
    5. Proposed: publish meetings in Youtube: See example of Helm project team:https://www.youtube.com/watch?v=b83bVArDuEg -1
    6. 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 invites/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

  1. 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.
  2. Notify of Roadmap meetings ahead of time? (these are every 2 weeks)
  3. 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

Decision: Clarification to UC about restricted pages (Security thing) and sub-teams → Jamey McCabe Action item.  Draft: The LCOO is committed (and motivated as we want to influence and participate in the entire community, to have our progress be in the public.  As we do share with each other non-public company matters for the purpose of Roadmap consolidation we have some materials that individual members create that are not public.  From an  organization security perspective we need to be able to keep these limited to their intended audience and auditable as to who is viewing. These materials will not be open to the public in the Atlassian Confluence Wiki.  Will will make every attempt to be open as to when we do refer to such materials.

Decision: Notify of this and Roadmap (every 2 weeks coordinators meeting) ahead of time via User Committee DL and include link to list of all meetings.  Meeting invites/notes. In essence this will be a weekly communication from LCOO on the User Committee DL,  :  → Jamey McCabe and Andy/Aditya action item

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.

Jamey5 minOpenness of our meeting approach.  Determine what change is needed reference: LCOO WG - Open community practices.msg 5 min

Training/volunteers needed for all staff on:

  1. connecting to Gerrit (https://review.openstack.org) to post and review User Stories
  10

  If it's the right time - perhaps a sub-tem to take it offline.

JameyDecision: No change needed at this time to single Chairperson which remains Jamey McCabe.
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
10

Decision: Will stick with the UTC:1400 for coordiantors meetings.  To see this in pictoral for the timezones of all members see picture at the bottom of LCOO Communication Plan

Decision: For subteam meetings, though they have the guidance of the Communication plan and thus proposed UTC0500 and UTC1400 times they should determine for themselves if, how often, when and even via what mechanism (verbal meeting or IRC)  makes sense. These meetings would also be tracked via Meeting invites/notes page so others in the community would not be excluded.

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?
 Jamey5 minAny new helpful coordination for Ocata:  Ocata Scope Tracker also Ocata Scope per Stackalytics  5 minCoordinate staff and goals for Pike PTG - Atlanta - February 24
  • 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 Megan volunteers to request this Jamey McCabe
  •  Bring following proposed Milestones and Action Items leading to Queen's Forum to 2/9 Roadmap meeting Aditya Mani (Unlicensed)Andrew Ukasick -Andy and Aditya discussed. These subjects will be discussed and decisions made but we will not commit to the list below. Milestones are as yet open for discussion and concensus first.

https://www.openstack.org/

ptg/.  Share attendees:

summit/boston-2017/


  • 2/6 FST's kicked off
  • 2/20 FST Roadmap for Queens
  • 3/6 Draft User Stories
    • Logging User Story asked by PWG to LCOO
    • Disruptive testing story is already proposed and merged! (https://
etherpad
/p/LCOO-PikePTG-Planning
  • 3/13 Meet with PWG
  • 3/ 27 Submit Forum time slot requests
Andy, JameyDecision: Will apply for 2 outward reaching sessions at the Boston Summit, a LCOO introduction (formal presentation) and a Birds of a Feather (Q&A type).  Note this is in addition to the planned face to face working session already requested by Shilla.
5 min

Intel Items Update (Sonu Sreenivasan is joining the call to give an intel update on the 4 items)

    1. Containerization of Control Plane - Kolla.  White Paper to available soon.
    2. Zero downtime upgrade for Core 6  and Ironic (Starting with Ocata and onward). Relted to Rollign Upgrades
    3. Scale Testing of Core 6 projects at 500 nodes for
reliablity
    1. reliability for
specifc referene
    1. specific reference workloads and deployment architecture with injected failures. Jamey spoke to haw this seems realted to proposed 1000 node User Story requested of LCOO.  Sonu clarified that Intel is looking for feedback on workload and architecture from LCOO for this effort.
    2. MOP Documentation for Ease of Installing Openstack using Ansible and Kolla
5 minReview progress at finding staff for Functional Specialty Teams - note that NA-Not applicable is a valid response:20 minMilestones 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

Action items

  •  

Summary: Intel has a number of projects already ongoing which seems to be in alignment with LCOO stated interests.  Intel is presenting them to engender more collaboration and at minimum get input from LCOO.  It was proposed that these be included in kickoff for related FST teams. 

Action items

  •