Community Summaries
Glance priorities [0]
Nova placement resource provider update [1]
Keystone Upcoming Deadlines [2]
Ironic priorities and subteam reports [3]
Keystone office hours [4]
Nova notification update [5]
Release countdown [6]
Technical committee status update [7]
[0] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124678.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124429.html
[2] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124727.html
[3] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124731.html
[4] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124820.html
[5] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124900.html
[6] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124882.html
[7] – http://lists.openstack.org/pipermail/openstack-dev/2017-November/124875.html
Self-healing SIG created
Adam Spiers announced the formation of a SIG around self-healing. Its scope is to coordinate the use and development of several OpenStack projects which can be combined in various ways to manage OpenStack infrastructure in a policy-driven fashion, reacting to failures and other events by automatically healing and optimising services.
Full thread: http://lists.openstack.org/pipermail/openstack-sigs/2017-November/000170.html
Proposal for a QA SIG
A proposal to to have a co-existing QA special interest group (SIG) that would be a place for downstream efforts to have a common place in collaborating and sharing tests. Example today the OPNFV performs QA on OpenStack releases today and are actively looking for opportunities to share tools and test cases. While a SIG can exist to do some code, the QA team will remain for now since there are around 15 QA projects existing like Tempest and Grenade.
Full thread: http://lists.openstack.org/pipermail/openstack-dev/2017-November/thread.html#124662
Improving the Process for Release Marketing
Collecting and summarizing “top features” during release time is difficult for both PTL’s and Foundation marketing. A system is now in place for PTL’s to highlight release notes [0]. Foundation marketing will work with the various teams if needed to understand and make things more press friendly.
Full thread: http://lists.openstack.org/pipermail/openstack-dev/2017-November/thread.html#124726
[0] – http://git.openstack.org/cgit/openstack/releases/tree/README.rst#n466
Quelle: openstack.org
Published by