[Starlingx-discuss] Minutes from 7/19/18 Core team call

Jones, Bruce E bruce.e.jones at intel.com
Thu Jul 19 17:43:29 UTC 2018

This file is: https://etherpad.openstack.org/p/stx-cores

Agenda items for the 7/19/18 call:

  *   Recording: https://zoom.us/recording/share/r7hfh1Nw9KFbiQs_pJ_1QN9wL9jKVNJSUsg5zdVOp--wIumekTziMw

  *   Project priorities https://wiki.openstack.org/wiki/StarlingX/Project_Priorities

  *   Build system improvements - Bruce

We reviewed and updated the Project Priorities page on the wiki.  This included discussions on a number of topics including:

*         We agreed that the build issues are the most important near term problem to solve.

*         We discussed how/when to update the "base OS" (CentOS) components of the project.  We agreed that we would start planning an upgrade to CentOS 7.5 and update to newer versions of qemu/libvirt as new sub-projects.

*         Patch upstreaming - can we move to SRPM patches instead of repos?

*         StarlingX staging repos - can we disposition, what is the long term plan?  Near term WR will replace the existing kingbird repo (which isn't really kingbird) with new repos

*         Project decoupling - code changes to make each of the services more independent.  WR is/will drive.

*         We raised addressing the Python2 issues to a higher priority level given the large scope of the work - we need to start sooner.

Meanwhile Bruce has been working to get internal approval for Intel to host StarlingX binaries, and we had a discussion as to the implications of that for the project.  The basic plan is to become a distro with a capital D and build/host all RPM packages in open yum repositories.  We do not yet agree that this is the right approach - it's a ton of work to set up and maintain.  But we have not been able identify a better long term solution so far.  Saul has the lead for this.

Near term there are reviews in flight to address this week's mirror issues.   The team is actively soliciting input for both short and long term solutions to the build issues.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20180719/f5c8a852/attachment.html>

More information about the Starlingx-discuss mailing list