March 2019 - openstack-discuss - lists.openstack.org

ceilometer 12.0.0.0rc1 (stein)
by no-reply＠openstack.org 21 Mar '19

21 Mar '19

Hello everyone, A new release candidate for ceilometer for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/ceilometer/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/ceilometer/log/?h=stable/stein Release notes for ceilometer can be found at: https://docs.openstack.org/releasenotes/ceilometer/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/ceilometer and tag it *stein-rc-potential* to bring it to the ceilometer release crew's attention.

1 0

[tc] PTG presence
by Thierry Carrez 21 Mar '19

21 Mar '19

Hi TC members and everyone else interested in community stewardship discussions, While trying to solve the conflicts puzzle for PTG room allocation I realized the TC did not request PTG meeting space. We are way past deadline: at this point we can probably still get half-a-day on Saturday afternoon (last day of PTG) if we are interested. We could try for a full day but that would mean reducing some other slots and/or generating extra conflicts, so I'd rather not. What do you think ? Do we want that slot ? Will half a day be enough ? -- Thierry Carrez (ttx)

10 14

[Forum] Feedback - Proposed Forum Schedule
by Jimmy McArthur 21 Mar '19

21 Mar '19

Hello All - The Forum Selection Committee spent some time last week reviewing submissions. A big thank you to all of the community members that took time out of their busy schedules to help us review. We look forward to delving into many great discussions Denver. Also happy to announce we were able to allocate space for all Forum submissions. We ended up moving three of the submissions out into the Working Group room, so if you think yours is missing, it's just waiting for its final home. We worked hard to prevent any conflicts, but please make sure there are no glaring competing time slots. With that in mind.. please have a look at the proposed Forum schedule and let us know if you have any concerns: https://www.openstack.org/summit/denver-2019/summit-schedule?#track=296 Please keep in mind, we may not be able to change a session time, but we will do our best on an as needed basis. Cheers, Jimmy

13 22

congress-dashboard 4.0.0.0rc1 (stein)
by no-reply＠openstack.org 20 Mar '19

20 Mar '19

Hello everyone, A new release candidate for congress-dashboard for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/congress-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/congress-dashboard/log/?h=stable/s… Release notes for congress-dashboard can be found at: https://docs.openstack.org/releasenotes/congress-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/congress and tag it *stein-rc-potential* to bring it to the congress-dashboard release crew's attention.

1 0

openstack-placement 1.0.0.0rc1 (stein)
by no-reply＠openstack.org 20 Mar '19

20 Mar '19

Hello everyone, A new release candidate for openstack-placement for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/placement/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/openstack-placement/log/?h=stable/… Release notes for openstack-placement can be found at: https://docs.openstack.org/releasenotes/openstack-placement/

1 0

[nova][placement] Nova Scheduler Subteam Meeting => Placement Team Meeting
by Eric Fried 20 Mar '19

20 Mar '19

All- Since the nova-scheduler meeting has morphed over the years into 90% placement, 10% nova scheduler, and placement is now under separate governance, I'd like to propose that we: - Rename/re-metadata the meeting to be the placement team meeting, chaired by the placement PTL, in the same time/channel slot - Fold nova scheduler-specific topics into the main Nova meeting (which may include getting a brief summary of scheduler-relevant topics from the placement meeting, if any) I've proposed this change in irc-meetings [1]. If anyone from nova and/or placement has objections or other suggestions, please comment here or there. Thanks, efried [1] https://review.openstack.org/#/c/644992/

1 0

[os-upstream-institute] Mentors for Denver - sign up and sync calls - ACTION NEEDED
by Ildiko Vancsa 20 Mar '19

20 Mar '19

Hi, We are planning two calls to prepare for the Denver Summit. One is some time between March 18 and 20 and the other is the week of April 15 which is the week before the training. The purpose of the first call is to go through the training material and prepare for the training. We will check the slides and the exercises and check whether we have any missing items or things to correct in the Contributor guide. The second call will be for checking back on action items and discuss any last minute administrativa. I created a Doodle poll to find the best times within the two aforementioned periods: https://doodle.com/poll/sgst4mqweeqb3btq Please mark __all the slots__ that can work for you, even if it is not the most convenient time of the day as we will only have two of these calls. If you plan to join the crew for Denver and you haven’t signed up yet on the wiki please do it here: https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions Please let me know if you have any questions. Thanks and Best Regards, Ildikó

1 2

[infra] Ansible versions in Zuul
by corvus＠inaugust.com 20 Mar '19

20 Mar '19

Hi, Yesterday we upgraded Zuul to a version that supports multiple Ansible versions. Previously, Zuul ran jobs under Ansible 2.5. That version will reach end of support in a few weeks, so the upgrade was necessary and timely. Zuul now supports selecting which version of Ansible (2.5, 2.6, 2.7) is used on a per-job basis. The default is the latest release of Ansible, currently 2.7, which means that when we made the upgrade, all jobs in the system immediately began running under 2.7. For most jobs, this has not caused any problems, and therefore, we will maintain the system default at 2.7. We have seen some errors, which generally fall into two categories: 1) Ansible syntax changes. Ansible 2.7 is more strict about invalid syntax than 2.5. If you encounter such an error, it may be easiest and best to simply update the roles or playbooks for the new syntax. If that is not practical, you can temporarily configure the job to run under an older version of Ansible by setting the "ansible-version" job attribute[1]. 2) Ansible module library incompatibility. Ansible modules run on the remote host they are targeting. Therefore if, for example, a job uses the "os_image" module to manipulate an OpenStack image store in a task that appears in a play which targets the "controller" node, then the os_image module will run in a Python interpreter on the "controller" node and it will import openstacksdk. Some jobs may implicitly rely on the fact that devstack installs openstacksdk in the global Python environment on the remote node in order for this to work. However, newer versions of Ansible require newer versions of openstacksdk than are specified by devstack on stable branches. This is a more complicated situation than that above. In this case, it may be simplest to set the job to use the newest working Ansible (whether that is 2.5 or 2.6) to resolve the immediate conflict. If the stable branch at issue will end support before the required version of Ansible, then you can stop there. However, if it must continue to work beyond then, it may be necessary to alter the job to avoid the use of the Ansible OpenStack modules and instead execute openstackclient commands using the shell or command modules. If you do specify an older version of Ansible for a job, be aware that once that version is no longer supported by Ansible, it will be removed from Zuul and the job will then need to be updated. If you have any further questions or see any other problems, please feel free to chat with us in #openstack-infra. -Jim [1] https://zuul-ci.org/docs/zuul/user/config.html#attr-job.ansible-version

1 0

zaqar 8.0.0.0rc1 (stein)
by no-reply＠openstack.org 20 Mar '19

20 Mar '19

Hello everyone, A new release candidate for zaqar for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/zaqar/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/zaqar/log/?h=stable/stein Release notes for zaqar can be found at: https://docs.openstack.org/releasenotes/zaqar/

1 0

[kolla][nova] Kolla/CellsV2 support
by Matthieu Simonin 20 Mar '19

20 Mar '19

Hi all, I'd like to know a bit more about the CellsV2 support in Kolla/Kolla-Ansible. It seems launchpad has two blueprints on the topic [1][2] and some associated patches. Is their a (realistic) target milestone to have cellsv2 support on the trunk ? Best, Matt [1]: https://blueprints.launchpad.net/kolla-ansible/+spec/cellsv2-rabbitmq-suppo… [2]: https://blueprints.launchpad.net/kolla-ansible/+spec/support-nova-cells

2 1