Agenda and notes - Jan 23rd call
·
Reminder: the Denver CFP ends TODAY!
·
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
·
Update from the Community Meetup
§
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
§
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).
§
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
§
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
§
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
§
Focusing on Network Segment Range merge in neutron - 5 patches still need to merge
·
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
§
No update
§
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
§
No update
§
Working on the multi-OS build spec
§
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)