Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: End of meeting

...

at UTC 1200: | See it in your timezone and add to your calendar: httpshttp://wwwbit.worldtimebuddy.com/event?lid=100&h=100&sts=25361280ly/2ImG1qH

LCOO General meetings are held in 3 ways:

  1. here in Atlassian Wiki for the formal agenda and notes and action items. 
  2. for audio and video interaction interaction: Webex Join WebEx meeting
    Meeting number (access code): 598 075 654 596 007 477

    Join by phone


    +1-210-795-1110 US Toll


    +1-866-662-9987 US Toll Free


    Global call-in numbers | Toll-free calling restrictions
    Can't join the meeting?

  3. IRC: for those who cannot join via audio or prefer interactive english text/ability to translate we also use IRC.  It is scheduled to the #openstack-meeting channel uc at this time. 

Attendees

Goals

Discussion items

ItemItemWhoNotes
1

Topical session #1 (RBAC) retrospective:  From 156172289 meeting we agreed to schedule the retrospective for 2/1 and touch base this week (1/25) to see if we could finalize topics and attendees.

Original session: 2017.11.30 LCOO Topical - Role Based Access Controls (RBAC)

2 main actions from 11/30 call mentioned again in 1/18 call :

place to add usecase

Policy Decision Point Framework (PDP)

2

Select next Topic and Date/Time of topical session #2

LCOO Topical Session Proposals

From 1/18 meeting we gathered the following:

"Cloud Native Focused Deployments"

  • Jae offered to present for SKT
  • Sanjeev potential presenter for Jio
  • Shintaro - to share direction of cloud native app and legacy app exist side-by-side
  • AT&T - TBD... 

Proposed we schedule Cloud Native  kickoff Topical Session for Feb 15 - 2 hours starting 1200UTC

3

Ongoing Discussion:

  • Should LCOO become a SIG?
  • Change our name (lcoo) so that we appear more inclusive of members who are not Contributors.
4

Ongoing Discussion:

LCOO as an Advocacy/Lobbying type group.  Should this be something we try to do?  Unite our voices to advocate for common priorities in the Community?  Strategy?
Review proposal for the next iteration of LCOO, sent by Ryan Van Wyk - AT&T Executive Stakeholder.  Some of the proposed changes include:
  1. Round robin chairperson - every 6 months
  2. More emphasis on stakeholder level influence on OpenStack direction
  3. 6 face to face meetings/year - PTG, before Summit Board Meetings, Working Group at the Summit

Jamey let the group know he was looking for a new position in AT&T and was likely to need to move from the Chair of this team.

Agreed to start the rotating chair approach

Elise Eiden volunteered to start for Vancouver and alphabetically will be Jaesuk to take on chair for the summit  in fall of 2018.

Agreed to bring our bosses together to agree on Strategic Interests between the LCOO members which we can jointly emphasize in the Vancouver sessions.

Proposed for meetings that the pattern would follow this:

  1. Virtual Meeting to align Strategy - before Summit/PTG
  2. Meeting at Summit PTG.

This would replace every 2 weeks pattern.

Jamey is proposing a meeting to finalize the common strategy for LCOO for the Vancouver summit. This meeting would involve our LCOO Stakeholder (bosses) as well as coordinators.This strategy meeting woudl need to occur by the first week of April. Jamey and Elise to distribute an agenda and purpose and proposed time and location next week. 

2If agreed above  vote on next chairperson
Agreed Elise Eiden is next Chairperson
3

Discuss next steps for Vancouver Summit


https://github.com/openstack/governance-sigs/blob/master/sigs.yaml > need to do ps on this to become sig. I will look further. 


If we agree to become a SIG - then Vancouver would be good for making that transition.

4

Placeholder: Akraino: https://www.sdxcentral.com/articles/news/linux-foundation-opens-edge-akraino-project/2018/02/


Q: If AT&T is preparing for "a new project" with these toolsets (https://treasuremap.readthedocs.io/en/latest/), that might be a good collaboration opportunity via LCOO to initiate, since SKT is already collaborating on Armada. 


Seems to be a potentially popular Topical Session. Could bring the communication providers 5G teams into helping with the upstream efforts.

  •  Jamey McCabe Clarify with AT&T team who is working on Akraino if they are willing to lead a Topical Session.
  •  Elise Eiden (Unlicensed) volunteering to draft a LCOO digest/communication which could cover things like Treasuremap, Akraino and Moon.

Other Action Items/Announcements

...