[Starlingx-discuss] Meeting notes Jan 23 Community Call

[Jones, Bruce E]

Agenda and notes - Jan 23rd call
*         Reminder: the Denver CFP ends TODAY!

  *   https://etherpad.openstack.org/p/edge-cfp-for-industry-events
*         Where are the recordings of our meetings stored?  Do we still need them?
*         Packet micro DC available for demo/PoC work + further collaboration on marketing/outreach in the area of edge - John Studarus

  *   See packet.com for HW configurations that would be available for us to test on the actual physical Edge on real HW.

  *   Packet Boston one 5G/CBRS edge micro data center: https://twitter.com/packethost/status/1062147355108085760

  *   Packet hardware configurations: https://www.packet.com/cloud/servers/

  *   We'd like to brainstorm/storytell for the public how StarlingX and these edge locations can be used by the public

  *   Perhaps a BoF at the Open Infrastructure Summit Denver?

  *   john at openstacksandiego.org or john.studarus at jhlconsulting.com
*         Update from the Community Meetup

  *   Release plan - Ghada
?  https://docs.google.com/spreadsheets/d/1HUwbsaSerzFRuvXVB_qvoGdI0Chx1YiiA2WYHwvIoYI/edit?usp=sharing
?  Mode Of Operation: Project Leads to update the plan weekly prior to the communit call
*         Review of ARs from Community Meetup - Bill
?  https://docs.google.com/spreadsheets/d/1F-JKh8_gLlUzbrUJRbsf4u65yBGVBl8HGe-RnUQoyc4
*         Sub-project status updates

  *   Containers - Frank
?  Container project will cut-over master branch to the container branch in February.
?  Please try to build/run it for testing.  Some folks are reporting issues with accessing the docker repo, WIP to resolve
?  Work is starting in the Test team now, seeing good progress there.
?  There is a feature branch called f/Stein where work to rebase to openstack master is in progress.
?  The cut over will bring us both Container support and Stein (from master).

  *   Distro.other - Cindy
?  CentOS 7.6 upgrade progress is good.  49 sRPM and 600+ RPM packages have been upgraded.
*         Kernel upgrade is still in progress.  Working on resolving driver patches
?  Ceph upgrade still has issues.  We will need multiple Ceph monitors running but this is taking a while.  For now we will just run one Ceph monitor.
*         This is at risk to complete before the branch cut-over as the China teams will be out for NY holiday
?  Python upgrade - 3 repos remaining - config, integ and distcloud.  Hope to have them done by end of January

  *   Distro.openstack - Bruce
?  About a third of the items we are tracking are at risk for Stein.
?  Details can be found here: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing

  *   Build - Cesar
?  Focusing on build for the new architecture and the docker images needed.
?  No known issues on the current build system
?  New spec in progress for the future build system

  *   Networking - Ghada
?  Focusing on Network Segment Range merge in neutron - 5 patches still need to merge
*         https://review.openstack.org/#/q/topic:bp/network-segment-range-management+(status:open+OR+status:merged)
*         Concern that the code will not be fully merged before Chinese New Year; will discuss mitigation in tomorrow's networking meeting
?  Integrating containerized ovs in StarlingX started
*         https://storyboard.openstack.org/#!/story/2004649

  *   DistCloud - Dariush
?  No update

  *   Test - Ada
?  working on setting up containers on systems that do not have internet access.
?  Numan shared test information for sanity test changes for the containers build

  *   Security - Ken
?  No update

  *   MultiOS - Bruce / Cesar
?  Working on the multi-OS build spec

  *   Docs - Michael
?  Spec in progress for changing the doc hierarchy to improve user experience and provide a framework for new documents
?  Please update the API docs if/when you change the APIs
?  We are not seeing the release notes getting populated for changes being made.  There are two steps needed to help us generate release notes
*         Have we discussed the release notes process overall?  What level do we want to provide - every change or high level?
*         What is the policy for when something is release noted?
*         Common openstack policy is that anything that is user visible should have release notes (e.g. bugs, functional changes)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190123/3eebe39d/attachment-0001.html>