September 2019 - openstack-discuss

Long, Slow Zuul Queues and Why They Happen
by Clark Boylan 23 Sep '19

23 Sep '19

Hello, We've been fielding a fair bit of questions and suggestions around Zuul's long change (and job) queues over the last week or so. As a result I tried to put a quick FAQ type document [0] on how we schedule jobs, why we schedule that way, and how we can improve the long queues. Hoping that gives us all a better understanding of why were are in the current situation and ideas on how we can help to improve things. [0] https://docs.openstack.org/infra/manual/testing.html#why-are-jobs-for-chang… Thanks, Clark

3 4

[neutron][drivers][ironic] FFE request - Use openstacksdk for ironic notifiers
by Riccardo Pittau 23 Sep '19

23 Sep '19

Hello fellow openstackers, I'd like to open an FFE request to convert the ironic events notifier from the current ironicclient to openstacksdk with the change https://review.opendev.org/682040 This requires also a bump of the versions of mock and openstacksdk in lower-constraints, included in the CR. The change has been tested in a devstack environment and passes the zuul checks. Thank you! Riccardo Pittau rpittau||elfosardo

4 5

[goals][IPv6-Only Deployments and Testing] Week R-3 Update
by Ghanshyam Mann 23 Sep '19

23 Sep '19

Hello Everyone, Below is the latest updated on IPv6 goal. All the projects have the ipv6 job patch proposed now. Next step is to review then as per mentioned guidelines below or help in debugging the failure. I saw tests are failing for the few projects which need debugging and help from the project team. Summary: The projects still need to prepare the IPv6 job: * None The projects waiting for IPv6 job patch to merge: If patch is failing, help me to debug that otherwise review and merge. * Barbican * Blazar * Cyborg * Tricircle * Vitrage * Zaqar * Glance * Monasca * Neutron * Qinling * Sahara * Searchlight * Senlin * Tacker * Ec2-Api * Freezer * Heat * Ironic * Karbor * Kuryr * Magnum * Masakari * Mistral * Murano * Octavia (johnsom is working on this and will take over the base patch) The projects have merged the IPv6 jobs: * Designate * Murano * Trove * Cloudkitty * Congress * Horizon * Keystone * Nova * Placement * Solum * Telemetry * Watcher * Zun * Cinder * Manila * Swift The projects do not need the IPv6 job (CLI, lib, deployment projects etc ): I have marked the tasks for below project as invalid. * Adjutant * Documentation * I18n * Infrastructure * Kolla * Loci * Openstack Charms * Openstack-Chef * Openstack-Helm * Openstackansible * Openstackclient * Openstacksdk * Oslo * Packaging-Rpm * Powervmstackers * Puppet Openstack * Rally * Release Management * Requirements * Storlets * Tripleo * Winstackers Storyboard: ========= - https://storyboard.openstack.org/#!/story/2005477 IPv6 missing support found: ===================== 1. https://review.opendev.org/#/c/673397/ 2. https://review.opendev.org/#/c/673449/ 3. https://review.opendev.org/#/c/677524/ There are few more but need to be tracked. How you can help: ============== - Each project needs to look for and review the ipv6 job patch. - Verify it works fine on ipv6 and no ipv4 used in conf etc - Any other specific scenario needs to be added as part of project IPv6 verification. - Help on debugging and fix the bug in IPv6 job is failing. Everything related to this goal can be found under this topic: Topic: https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(stat… How to define and run new IPv6 Job on project side: ======================================= - I prepared a wiki page to describe this section - https://wiki.openstack.org/wiki/Goal-IPv6-only-deployments-and-testing Review suggestion: ============== - Main goal of these jobs will be whether your service is able to listen on IPv6 and can communicate to any other services either OpenStack or DB or rabbitmq etc on IPv6 or not. So check your proposed job with that point of view. If anything missing, comment on patch. - One example was - I missed to configure novnc address to IPv6- https://review.opendev.org/#/c/672493/ - base script as part of 'devstack-tempest-ipv6' will do basic checks for endpoints on IPv6 and some devstack var setting. But if your project needs more specific verification then it can be added in project side job as post-run playbooks as described in wiki page[1]. [1] https://wiki.openstack.org/wiki/Goal-IPv6-only-deployments-and-testing

1 0

[neutron] bug deputy report (the week of 2019-09-16)
by Takashi Yamamoto 23 Sep '19

23 Sep '19

here's the list of what we got reported in the week. features (nova bp follow-up) https://bugs.launchpad.net/neutron/+bug/1844131 Boot a VM with an unaddressed port High https://bugs.launchpad.net/neutron/+bug/1844168 [L3] TooManyExternalNetworks: More than one external network exists. A proposed fix: https://review.opendev.org/#/c/682418/ Medium https://bugs.launchpad.net/neutron/+bug/1844124 Not possible to change fixed-ips if port is on routed provider network A proposed fix: https://review.opendev.org/#/c/682489/ https://bugs.launchpad.net/neutron/+bug/1844516 [neutron-tempest-plugin] SSH timeout exceptions when executing remote commands A proposed fix: https://review.opendev.org/#/c/682864/ https://bugs.launchpad.net/neutron/+bug/1844688 "radvd" daemon does not work by default in some containers A proposed fix: https://review.opendev.org/#/c/683207/ Low https://bugs.launchpad.net/neutron/+bug/1844171 Configuration parameter missing at "Configure the layer-3 agent" A merged fix: https://review.opendev.org/#/c/682645/ https://bugs.launchpad.net/neutron/+bug/1844607 log error when create neutron port with wrong subnet A proposed fix: https://review.opendev.org/#/c/683273/ Incomplete https://bugs.launchpad.net/neutron/+bug/1844123 Unable to trigger IPv6 Prefix Delegation https://bugs.launchpad.net/neutron/+bug/1844595 openstackNova(Rocky)--chinese incorrect codes for db character error https://bugs.launchpad.net/neutron/+bug/1844915 Duplicate packets with two networks connected by router Invalid https://bugs.launchpad.net/neutron/+bug/1844097 Redundant ipv6 address(SLAAC/DHCPv6 stateless) created for port It was an intended behavior and the rationale was explained to the submitter.

1 0

zun-ui 4.0.0.0rc1 (train)
by no-reply＠openstack.org 23 Sep '19

23 Sep '19

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

1 0

kuryr-libnetwork 4.0.0.0rc1 (train)
by no-reply＠openstack.org 23 Sep '19

23 Sep '19

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

1 0

Outreachy Application Deadline - Call for mentors and projects
by Samuel de Medeiros Queiroz 21 Sep '19

21 Sep '19

Hi everyone! Outreachy <https://www.outreachy.org/> helps people from underrepresented groups get involved in free and open source software by matching interns with established mentors in the upstream communities. OpenStack is a participating organization in the Outreachy Dec 2019 to Mar 2020 round. If you're interested to be a mentor, please register as a mentor in the Outreachy website and publish your project ideas. According to this round's schedule <https://www.outreachy.org/docs/applicant/#outreachy-schedule>, the initial application is due next week: - *Sept. 24, 2019 at 4pm UTC Initial application deadline * - *Nov. 5, 2019 at 4pm UTC Final application deadline* It is important to get projects submitted *as soon as possible* so that applicants can sign up before the *Sept. 24 deadline*. Once signed up, they will have between *Oct. 1, 2019 to Nov. 5, 2019 to contribute to the projects*. If you have any questions about becoming a mentor or want to sponsor an intern, please contact me (samueldmq(a)gmail.com) or Mahati Chamarthy ( mahati.chamarthy(a)gmail.com) Thank you, Samuel de Medeiros Queiroz

3 2

[keystone] Keystone Team Update - Week of 16 September 2019
by Colleen Murphy 21 Sep '19

21 Sep '19

# Keystone Team Update - Week of 16 September 2019 ## News ### RC1 Status Even after discovering some gaps in our policy migrations we managed to quickly cover them and are on track to close all our RC1-targeted bugs[1] on time! [1] https://launchpad.net/keystone/+milestone/train-rc1 ## Office Hours When there are topics to cover, the keystone team holds office hours on Tuesdays at 17:00 UTC. No office hours next week due to lack of topics. Add topics you would like to see covered during office hours to the etherpad: https://etherpad.openstack.org/p/keystone-office-hours-topics ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 32 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 58 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ## Milestone Outlook https://releases.openstack.org/train/schedule.html We're on target to release RC1 next week. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

[ironic] Tips on testing custom hardware manager?
by Jason Anderson 20 Sep '19

20 Sep '19

Hi all, I am hoping to get some tips on how to test out a custom hardware manager. One of my colleagues is working on a project that involves implementing a custom in-band cleaning step, which we are implementing by creating our own ramdisk image that includes an extra library, which is necessary for the clean step. We already have created the image and ensured it has IPA installed and that all seems to work fine (in that, it executes on the node and we see our code running--and failing!) The issue we are having is that we encounter some issues in our fully integrated environment (such as the provisioning network having different networking rules) and replicating this environment in some local development context is very difficult. Right now our workflow is really onerous as a result: my colleague has to rebuild the ramdisk image, re-upload it to Glance, update the test Ironic node to reference that image, then perform a rebuild. One cycle of this takes a while as you can imagine. I was wondering: is it possible to somehow interrupt or give a larger window for some interactive debugging? The amount of time we have to run some quick tests/debugging is small because the deploy will time out and cancel itself or it will proceed and fail. Thusfar I haven't found any documentation or written experience on this admittedly niche task. Perhaps somebody has already gone down this road and can advise on some tips? It would be much appreciated! Cheers, -- Jason Anderson Chameleon DevOps Lead Consortium for Advanced Science and Engineering, The University of Chicago Mathematics & Computer Science Division, Argonne National Laboratory

2 2

[i18n][tc] The future of I18n
by Thierry Carrez 20 Sep '19

20 Sep '19

Hi! The I18n project team had no PTL candidates for Ussuri, so the TC needs to decide what to do with it. It just happens that Ian kindly volunteered to be an election official, and therefore could not technically run for I18n PTL. So if Ian is still up for taking it, we could just go and appoint him. That said, I18n evolved a lot, to the point where it might fit the SIG profile better than the project team profile. As a reminder, project teams are responsible for producing OpenStack-the-software, and since they are all integral in the production of the software that we want to release on a time-based schedule, they come with a number of mandatory tasks (like designating a PTL every 6 months). SIGs (special interest groups) are OpenStack teams that work on a mission that is not directly producing a piece of the OpenStack release. SIG members are bound by their mission, rather than by a specific OpenStack release deliverable. There is no mandatory task, as it is OK if the group goes dormant for a while. The I18n team regroups translators, with an interest of making OpenStack (in general, not just the software) more accessible to non-English speakers. They currently try to translate the OpenStack user survey, the Horizon dashboard messages, and key documentation. It could still continue as a project team (since it still produces Horizon translations), but I'd argue that at this point it is not what defines them. The fact that they are translators is what defines them, which IMHO makes them fit the SIG profile better than the project team profile. They can totally continue proposing translation files for Horizon as a I18n SIG, so there would be no technical difference. Just less mandatory tasks for the team. Thoughts ? -- Thierry Carrez (ttx)

4 4