- openstack-discuss - lists.openstack.org

[i18n] Request to be added as Vietnamese translation group coordinators
by Trinh Nguyen 03 Oct '19

03 Oct '19

Hi i18n team, Dai and I would like to volunteer as the coordinators of the Vietnamese translation group. If you find us qualified, please let us know. Bests, -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

5 7

[all] [tc] [docs] [release] [ptls] Docs as SIG: Ownership of docs.openstack.org
by Alexandra Settle 03 Oct '19

03 Oct '19

Hi all, Quick recap: The documentation team is set to disband as an official project, and make the leap to becoming a SIG (Special Interest Group). This decision is not one we have made lightly, but with the changes of direction since Pike (project documentation belonging with the projects, etc) the need for a centralised documentation team as an official project is no longer integral to producing the software. The transition of the docs team to a SIG has already begun [1] and [2]. The openstackdocstheme, openstack-doc-tools, os-api-ref and whereto have been placed within the remit of the Oslo team and approved. The remaining individuals working on the docs team are sorting through what's left and where it is best placed. In [1], Doug has rightfully pointed out that whilst the documentation team as it stands today is no longer "integral", the docs.openstack.org web site is. An owner is required. The suggestion is for the Release Management team is the "least worst" (thanks, tonyb) place for the website manaagement to land. As Tony points out, this requires learning new tools and processes but the individuals working on the docs team currently have no intention to leave, and are around to help manage this from the SIG. Open to discussion and suggestions, but to summarise the proposal here: docs.openstack.org ownership is to transition to be the responsibility of the Release Management team officially provided there are no strong objections. Thanks, Alex IRC: asettle [1] https://review.opendev.org/#/c/657142/ [2] https://review.opendev.org/#/c/657141/

5 11

[kolla-ansible] migration
by Ignazio Cassano 02 Oct '19

02 Oct '19

Hello, Anyone have tried to migrate an existing openstack installation to kolla containers? Thanks Ignazio

5 16

[openstack-ansible] Stepping down as core reviewer
by Jesse Pretorius 02 Oct '19

02 Oct '19

Hi everyone, While I had hoped to manage keeping up with OSA reviews and some contributions, unfortunately there is too much on my plate in my new role to allow me to give OSA sufficient time and I feel that it's important to not give any false promises. I am therefore stepping down as a core reviewer for OSA. My journey with OpenStack-Ansible started with initial contributions before it was an official OpenStack project, went on to helping lead the project to becoming an official project in the big tent, then on to becoming a successful project with diverse contributors of which I was proud to be a part. Over time I learned a heck of a lot about building and leading an Open Source community, about developing Ansible playbooks and roles at significant scale, and about building, packaging and deploying python software. It has been a very valuable experience through which I have grown personally and professionally. This community's strengths are in its leadership by operators, its readiness to assist newcomers and in striving to maintain a deployment system which is easy to understand and use (while somehow also being ridiculously flexible). As Jean-Philippe Evrard has recently expressed, this is the DNA which makes the community special. As you should all be aware, I am always ready to help when asked and I can also share historical context if there is a need for that so please feel free to ping me on IRC or add me to a review and I'll do my best. My journey onward is working with TripleO in the upgrades team, so you'll still find me contributing to OpenStack as a whole. I'll be hanging out in #tripleo and #openstack-dev on IRC if you're looking for me. All the best, Jesse (odyssey4me)

2 1

OOK,Airship
by Charles 02 Oct '19

02 Oct '19

Hi, We are interested in OOK and Openstack Helm. Has anyone any experience with Airship (now that 1.0 is out)? Noticed that a few Enterprise distributions are looking at managing the Openstack control plane with Kubernetes and have been testing Airship with a view to rolling it out (Mirantis,SUSE) Is this a signal that there is momentum around Openstack Helm? Is it possible to roll out an open source production grade Airship/Openstack Helm deployment today, or is it too early? Thoughts? Charles

1 0

[kuryr][kuryr-libnetwork] Nominating Hongbin Lu to kuryr-libnetwork and kuryr core
by Michał Dulko 02 Oct '19

02 Oct '19

Hi, I'd like to nominate Hongbin Lu to be core reviewer in both kuryr- libnetwork and kuryr projects. Besides saying that he's doing a great job maintaining kuryr-libnetwork I'm simply surprised he don't have +2/-2 rights there and that should definitely get fixed. As there isn't a lot of people maintaining those projects anymore, I'll just skip the voting part and add Hongbin to core teams immediately. Thanks, Michał

1 0

glance 19.0.0.0rc1 (train)
by no-reply＠openstack.org 02 Oct '19

02 Oct '19

Hello everyone, A new release candidate for glance for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/glance/ 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/glance/src/branch/stable/train Release notes for glance can be found at: https://docs.openstack.org/releasenotes/glance/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/glance/+bugs and tag it *train-rc-potential* to bring it to the glance release crew's attention.

1 0

issues creating a second vm with numa affinity
by Manuel Sopena Ballesteros 02 Oct '19

02 Oct '19

Dear Openstack user community, I have a compute node with 2 numa nodes and I would like to create 2 vms, each one using a different numa node through numa affinity with cpu, memory and nvme pci devices. pci passthrough whitelist [root@zeus-53 ~]# tail /etc/kolla/nova-compute/nova.conf [notifications] [filter_scheduler] enabled_filters = enabled_filters = RetryFilter, AvailabilityZoneFilter, ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, ServerGroupAntiAffinityFilter, ServerGroupAffinityFilter, PciPassthroughFilter available_filters = nova.scheduler.filters.all_filters [pci] passthrough_whitelist = [ {"address":"0000:06:00.0"}, {"address":"0000:07:00.0"}, {"address":"0000:08:00.0"}, {"address":"0000:09:00.0"}, {"address":"0000:84:00.0"}, {"address":"0000:85:00.0"}, {"address":"0000:86:00.0"}, {"address":"0000:87:00.0"} ] alias = { "vendor_id":"8086", "product_id":"0953", "device_type":"type-PCI", "name":"nvme"} Openstack flavor openstack flavor create --public xlarge.numa.perf.test --ram 200000 --disk 700 --vcpus 20 --property hw:cpu_policy=dedicated --property hw:emulator_threads_policy=isolate --property hw:numa_nodes='1' --property pci_passthrough:alias='nvme:4' The first vm is successfully created openstack server create --network hpc --flavor xlarge.numa.perf.test --image centos7.6-image --availability-zone nova:zeus-53.localdomain --key-name mykey kudu-1 However the second vm fails openstack server create --network hpc --flavor xlarge.numa.perf --image centos7.6-kudu-image --availability-zone nova:zeus-53.localdomain --key-name mykey kudu-4 Errors in nova compute node 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [req-b5a25c73-8c7d-466c-8128-71f29e7ae8aa 91e83343e9834c8ba0172ff369c8acac b91520cff5bd45c59a8de07c38641582 - default default] [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] Instance failed to spawn: libvirtError: internal error: qemu unexpectedly closed the monitor: 2019-09-27T06:45:19.118089Z qemu-kvm: kvm_init_vcpu failed: Cannot allocate memory 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] Traceback (most recent call last): 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2369, in _build_resources 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] yield resources 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2133, in _build_and_run_instance 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] block_device_info=block_device_info) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 3142, in spawn 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] destroy_disks_on_failure=True) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 5705, in _create_domain_and_network 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] destroy_disks_on_failure) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] self.force_reraise() 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] six.reraise(self.type_, self.value, self.tb) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 5674, in _create_domain_and_network 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] post_xml_callback=post_xml_callback) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 5608, in _create_domain 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] guest.launch(pause=pause) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/guest.py", line 144, in launch 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] self._encoded_xml, errors='ignore') 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] self.force_reraise() 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] six.reraise(self.type_, self.value, self.tb) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/guest.py", line 139, in launch 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] return self._domain.createWithFlags(flags) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 186, in doit 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] result = proxy_call(self._autowrap, f, *args, **kwargs) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 144, in proxy_call 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] rv = execute(f, *args, **kwargs) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 125, in execute 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] six.reraise(c, e, tb) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 83, in tworker 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] rv = meth(*args, **kwargs) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1110, in createWithFlags 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self) 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] libvirtError: internal error: qemu unexpectedly closed the monitor: 2019-09-27T06:45:19.118089Z qemu-kvm: kvm_init_vcpu failed: Cannot allocate memory 2019-09-27 16:45:19.785 7 ERROR nova.compute.manager [instance: ebe4e78c-501e-4535-ae15-948301cbf1ae] Numa cell/node 1 (the one assigned on kudu-4) has enough cpu, memory, pci devices and disk capacity to fit this vm. NOTE: below is the information relevant I could think of that shows resources available after creating the second vm. [root@zeus-53 ~]# numactl -H available: 2 nodes (0-1) node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 28 29 30 31 32 33 34 35 36 37 38 39 40 41 node 0 size: 262029 MB node 0 free: 52787 MB node 1 cpus: 14 15 16 17 18 19 20 21 22 23 24 25 26 27 42 43 44 45 46 47 48 49 50 51 52 53 54 55 node 1 size: 262144 MB node 1 free: 250624 MB node distances: node 0 1 0: 10 21 1: 21 10 NOTE: this is to show that numa node/cell 1 has enough resources available (also nova-compute logs shows that kudu-4 is assigned to cell 1) [root@zeus-53 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/md127 3.7T 9.1G 3.7T 1% / ... NOTE: vm disk files goes to root (/) partition [root@zeus-53 ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 59.6G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 16G 0 part [SWAP] loop0 7:0 0 100G 0 loop └─docker-9:127-6979358884-pool 253:0 0 100G 0 dm ├─docker-9:127-6979358884-4301cee8d0433729cd6332ca2b6111afc85f14c48d4ce2d888a1da0ef9b5ca01 253:1 0 10G 0 dm ├─docker-9:127-6979358884-d59208adcb7cee3418f810f24e6c3a55d39281f713c8e76141fc61a8deba8a2b 253:2 0 10G 0 dm ├─docker-9:127-6979358884-106bc0838e37442eca84eb9ab17aa7a45308b7e3a38be3fb21a4fa00366fe306 253:3 0 10G 0 dm ├─docker-9:127-6979358884-7e16b5d012ab8744739b671fcdc8e47db5cc64e6c3d5a5fe423bfd68cfb07b20 253:4 0 10G 0 dm ├─docker-9:127-6979358884-f1c2545b4edbfd7b42d2a492eda8224fcf7cefc3e3a41e65d307c585acffe6a8 253:5 0 10G 0 dm ├─docker-9:127-6979358884-e7fd6c7b3f624f387bdb3746a7944a30c92d8ee5395e75c76288b281bd009d90 253:6 0 10G 0 dm ├─docker-9:127-6979358884-95a818cc7afd9867385bb9a9ea750d4cc6e162916c6ae3a157097af74578e1e4 253:7 0 10G 0 dm ├─docker-9:127-6979358884-9a7f28d396c149119556f382bf5c19f5925eed5d18b94407649244c7adabb4b3 253:8 0 10G 0 dm ├─docker-9:127-6979358884-b25941b6f115300caea977911e2d7fd3541ef187c9aa5736fe10fad638ecd0d1 253:9 0 10G 0 dm ├─docker-9:127-6979358884-122b201c6ad24896a205f8db4a64759ba8fbd5bbe245d0f98984268a01e6a0c4 253:10 0 10G 0 dm └─docker-9:127-6979358884-bc04120ba59a1b393f338a1cef64b16d920cf4e73400198e4b999bb72a42ff90 253:11 0 10G 0 dm loop1 7:1 0 2G 0 loop └─docker-9:127-6979358884-pool 253:0 0 100G 0 dm ├─docker-9:127-6979358884-4301cee8d0433729cd6332ca2b6111afc85f14c48d4ce2d888a1da0ef9b5ca01 253:1 0 10G 0 dm ├─docker-9:127-6979358884-d59208adcb7cee3418f810f24e6c3a55d39281f713c8e76141fc61a8deba8a2b 253:2 0 10G 0 dm ├─docker-9:127-6979358884-106bc0838e37442eca84eb9ab17aa7a45308b7e3a38be3fb21a4fa00366fe306 253:3 0 10G 0 dm ├─docker-9:127-6979358884-7e16b5d012ab8744739b671fcdc8e47db5cc64e6c3d5a5fe423bfd68cfb07b20 253:4 0 10G 0 dm ├─docker-9:127-6979358884-f1c2545b4edbfd7b42d2a492eda8224fcf7cefc3e3a41e65d307c585acffe6a8 253:5 0 10G 0 dm ├─docker-9:127-6979358884-e7fd6c7b3f624f387bdb3746a7944a30c92d8ee5395e75c76288b281bd009d90 253:6 0 10G 0 dm ├─docker-9:127-6979358884-95a818cc7afd9867385bb9a9ea750d4cc6e162916c6ae3a157097af74578e1e4 253:7 0 10G 0 dm ├─docker-9:127-6979358884-9a7f28d396c149119556f382bf5c19f5925eed5d18b94407649244c7adabb4b3 253:8 0 10G 0 dm ├─docker-9:127-6979358884-b25941b6f115300caea977911e2d7fd3541ef187c9aa5736fe10fad638ecd0d1 253:9 0 10G 0 dm ├─docker-9:127-6979358884-122b201c6ad24896a205f8db4a64759ba8fbd5bbe245d0f98984268a01e6a0c4 253:10 0 10G 0 dm └─docker-9:127-6979358884-bc04120ba59a1b393f338a1cef64b16d920cf4e73400198e4b999bb72a42ff90 253:11 0 10G 0 dm nvme0n1 259:8 0 1.8T 0 disk └─nvme0n1p1 259:9 0 1.8T 0 part └─md127 9:127 0 3.7T 0 raid0 / nvme1n1 259:6 0 1.8T 0 disk └─nvme1n1p1 259:7 0 1.8T 0 part └─md127 9:127 0 3.7T 0 raid0 / nvme2n1 259:2 0 1.8T 0 disk nvme3n1 259:1 0 1.8T 0 disk nvme4n1 259:0 0 1.8T 0 disk nvme5n1 259:3 0 1.8T 0 disk NOTE: this is to show that there are 4 nvme disks (nvme2n1, nvme3n1, nvme4n1, nvme5n1) available for the second vm What "emu-kvm: kvm_init_vcpu failed: Cannot allocate memory" means in this context? Thank you very much NOTICE Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed.

3 3

[qa][stable] tempest.api.volume.test_versions.VersionsTest.test_show_version fails on stable/pike
by Matt Riedemann 02 Oct '19

02 Oct '19

A new test was recently added to tempest [1] which uses the volume API v3 client to list and show versions and compare those against the response schema. It's failing against stable/pike changes [2] presumably because the volume v3 API does not show the (deprecated) v1 API, though I'm a bit confused because the test is doing a GET / and then for each version in the response it's doing a GET /{version}/ so I'm not sure what's up with cinder's pike API version interface where it would list a version but not be able to show it. Anyway, it sounds like this is another case where we're going to have to pin tempest to a tag in devstack on stable/pike to continue running tempest jobs against stable/pike changes, similar to what recently happened with stable/ocata [3]. [1] https://review.opendev.org/#/c/680790/ [2] https://145b0d5be77f0cbe05ff-d67a6226f6eb6d34ab4efd951744a16f.ssl.cf5.rackc… [3] https://review.opendev.org/#/c/681950/ -- Thanks, Matt

3 5

[OSA][openstack-ansible] Stepping down from core reviewer
by Jean-Philippe Evrard 02 Oct '19

02 Oct '19

Hello OSA friends, It's with great sadness that announcing I will be stepping down from OpenStack-Ansible's core role. OSA has been the place where I grew from contributor to OpenStack core for the first time, so it will always keep a special place in my mind :) It's also where I met contributors I can now consider personal friends. It's a project I've helped grow and prosper the last 4 years. I am very happy of what we have all achieved. My last goals in OSA were to simplify it further and a focus on bare metal. Those efforts are either merged or advanced enough nowadays. I consider I have achieved what I wanted to: OSA is now easier than ever to manage, contribute, and deliver. With more experienced people leaving and new people joining, I sure hope the DNA of the project will stay the same: An always welcoming and friendly community, with a no-bullshit and not-too-serious attitude. A project focusing on operator issues and use cases, mentoring contributors to be great members of the OpenStack community. Again, I want to thank you for being an amazing community, and it's been great working with all of you. I think there are still plenty of things OSA can achieve. If you want my opinion, you shouldn't hesitate to contact me. I just don't have enough time to keep up with the reviews, nor am I actively contributing enough to stay at core. All the best, Jean-Philippe Evrard (evrardjp)

5 4

[tc] Weekly update
by Jean-Philippe Evrard 01 Oct '19

01 Oct '19

Hello friends, Here's what need attention for the OpenStack TC this week: 1. We should ensure we have two TC members focusing on next cycle goal selection process. Only Ghanshyam is dealing with this, and we must help him on the way! Any volunteers? Thanks again gmann for working on that. 2. Jimmy McArthur sent us the results of the OpenStack User survey on the ML [1]. We currently haven't analyzed the information yet. Any volunteer to analyse the information (in order to extract action items) is welcomed. It would be great if we could discuss this at our next official meeting, or at least discuss the next steps. 3. Our next meeting date will be the Thursday 10 October. I will be travelling that day, so it would be nice to have a volunteer to host the meeting. For that, our next meeting agenda needs clarifications. It would be great if you could update the agenda (please also write if your absent) on the wiki [2], so that I can send the invite to the ML. I will send the invite on Thursday. 4. We still haven't finished the conversationg about naming releases. There are a few new ideas floated around, so we should maybe drop the current process to take count of the newly proposed ideas (The large cities lists proposed by Nate, the movie quotes proposed by Thierry [9])? Alternatively, if we can't find consensus, should we just entrust the release naming process to the release team? 5. We should decide to deprecate or not the PowerVMStackers team [3] and move it as a SIG. The votes don't reflect this. Thank you everyone! [1]: http://lists.openstack.org/pipermail/openstack-discuss/2019-September/00950… [2]: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [3]: https://review.opendev.org/680438 [4]: https://review.opendev.org/680985 [5]: https://review.opendev.org/681260 [6]: https://review.opendev.org/681480 [7]: https://review.opendev.org/681924 [8]: https://review.opendev.org/682380 [9]: https://review.opendev.org/684688

3 3

networking-midonet 9.0.0.0rc2 (train)
by no-reply＠openstack.org 01 Oct '19

01 Oct '19

Hello everyone, A new release candidate for networking-midonet for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/networking-midonet/ 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/networking-midonet/src/branch/stable/train Release notes for networking-midonet can be found at: https://docs.openstack.org/releasenotes/networking-midonet/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/networking-midonet/+bugs and tag it *train-rc-potential* to bring it to the networking-midonet release crew's attention.

1 0

[nova][ops] Removing Debug middleware
by Eric Fried 01 Oct '19

01 Oct '19

Deployers- There's a Debug middleware in nova that's not used in the codebase since 2010, so we're removing it [1]. BUT Theoretically, deployments could be making use of it by injecting it into the paste pipeline (a ~3LOC edit to your local api-paste.ini). If this is you, and you're really relying on this behavior, let us know. We can either revert the change or show you how to carry it locally (which would be really easy to do). Thanks, efried [1] https://review.opendev.org/#/c/662506/

1 0

[all] [tc] [ptls] PDF Goal Aftermath
by Alexandra Settle 01 Oct '19

01 Oct '19

Hi all, Thanks to all those who worked super hard to achieve the PDF Enablement goal for Train. Things are looking great, and I've already received feedback from downstream about how useful the PDFs are! So that's fantastic. For the sake of the goal, the intention was to have potentially imperfect PDFs and to ensure they're building. In some cases, this does leave room for improvement. In openstack-doc, we've been approached a few times regarding moving forward when there are issues with no known workarounds. So, asking all those that have been working on/building their PDFs and are experiencing issues that can be fixed post-mortem to ensure everything is documented in our Common Problems etherpad [1]. Ensuring everything is documented, means we can work together to identify appropriate workarounds or fixes in the future. We will review all items without a workaround in the short term. Cheers, Alex [1] https://etherpad.openstack.org/p/pdf-goal-train-common-problems -- Alexandra Settle <a.settle(a)outlook.com> IRC: asettle

1 0

Re: [Release-job-failures] release-post job for openstack/releases for ref refs/heads/master failed
by Sean McGinnis 30 Sep '19

30 Sep '19

On Mon, Sep 30, 2019 at 06:23:47PM +0000, zuul(a)openstack.org wrote: > Build failed. > > - tag-releases https://zuul.opendev.org/t/openstack/build/9ee941bea3b8476c98fe6fc17328f1c5 : FAILURE in 15m 10s > - publish-tox-docs-static https://zuul.opendev.org/t/openstack/build/None : SKIPPED > > _______________________________________________ > Release-job-failures mailing list > Release-job-failures(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures I'm not entirely sure what caused the failure here, but it is not really an issue. This was a docs-only change, so there wasn't anything to be tagged. Due to the tag-releases job failing, the publish-tox-docs-static job was skipped. There are other patches going through though, so the docs will get picked up and published very soon, if they haven't been already, so nothing to worry about there. Sean

1 0

[swift] Changing the name of an existing policy (in particular Policy-0)
by Mark Kirkwood 30 Sep '19

30 Sep '19

Hi, We are looking at introducing extra policies to a Swift cluster that was built essentially policy unaware (Swift 2.3). So currently all our containers live in policy id 0 (with name of 'Policy-0'). We would like to rename this so that the likes of 'swift stat' give a more human readable name to this policy (e.g 'Default' or 'All-Regions'). Doing some experimentation it looks like this is safe - but I'm asking here to check that I have not missed anything that would nuke the cluster.... Note we are *not* wanting to meddle with the policy id number. regards Mark

2 1

[cinder] train backport potential bugfixes
by Brian Rosmaita 30 Sep '19

30 Sep '19

With RC-1 released and the stable/train branch cut, any new bugfixes to be included in the Cinder Train release must be (1) merged to master, (2) be proposed as backports to stable/train, (3) approved by the cinder stable-maint team. and (4) merged to stable/train before the final RC deadline (10 Oct). If you are working on such a bugfix, please add it to this etherpad: https://etherpad.openstack.org/p/cinder-train-backport-potential Keep in mind that the gate is always slow around this time of the cycle, so the earlier your fixes are proposed, the more likely they are to actually make it into the release. If you don't have a Cinder bugfix you're working on now, it would be helpful if you could do some exploratory testing on Cinder RC-1. You can checkout the tag from git, or use the release tarball: https://releases.openstack.org/train/index.html#train-cinder cheers, brian

2 1

[cyborg] No IRC meeting this week
by Nadathur, Sundar 30 Sep '19

30 Sep '19

No Cyborg IRC meeting this Wednesday, due to national holiday in China. Regards, Sundar

1 0

tricircle 7.0.0.0rc1 (train)
by no-reply＠openstack.org 30 Sep '19

30 Sep '19

Hello everyone, A new release candidate for tricircle for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/tricircle/ 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/tricircle/src/branch/stable/train Release notes for tricircle can be found at: https://docs.openstack.org/releasenotes/tricircle/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/tricircle/+bugs and tag it *train-rc-potential* to bring it to the tricircle release crew's attention.

1 0

[monasca] Ussuri release planning meeting
by Witek Bedyk 30 Sep '19

30 Sep '19

Hello everybody, as yesterday discussed in the team meeting I'd like to find the best time for the planning meeting for the next release cycle. I though about two 4 hours long time slots. Please fill in your preferences in this Doodle survey: https://doodle.com/poll/ugxr89tqmkfwa5r7 Please also leave any feedback about the times in the etherpad. Please let me know if you would like to move the meeting to some other time or make it shorter (or longer). https://etherpad.openstack.org/p/monasca-planning-ussuri Best greetings Witek

1 1

openstack-heat 13.0.0.0rc1 (train)
by no-reply＠openstack.org 29 Sep '19

29 Sep '19

Hello everyone, A new release candidate for openstack-heat for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/heat/ 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/openstack-heat/src/branch/stable/train Release notes for openstack-heat can be found at: https://docs.openstack.org/releasenotes/heat/

1 0

[neutron] [stable] Proposing Slawek Kaplonski to Neutron Stable core
by Miguel Lavalle 29 Sep '19

29 Sep '19

Hi Stackers, In order to strengthen our stable core team, I want to nominate Slawek Kaplonski to it. Over the past years he has made countless contributions in all areas of the project, has been a member of the core team since two years ago and is the incoming PTL for the U cycle ( https://governance.openstack.org/election/results/ussuri/ptl.html) I will keep this nomination open for a week as customary. Best regards Miguel

6 7

[neutron] bug deputy report for week of 2019-09-23
by Bence Romsics 28 Sep '19

28 Sep '19

Hi All, Next week I'll be out of office, so I'm sending my report a bit early. I won't be able to attend Monday's team meet, but let me please call your attention to the unassigned bugs in this list and the one at the top I could not triage. Still needs triage: * https://bugs.launchpad.net/neutron/+bug/1845360 ARP advertisement issue with DVR Temporary traffic loss with a workaround. My DVR-fu was not enough to process this. Critical: * https://bugs.launchpad.net/neutron/+bug/1845227 new l3 agent router factory breaks neutron-fwaas functional tests Fixed: https://review.opendev.org/652812 High: * https://bugs.launchpad.net/neutron/+bug/1845300 FWaaS tempest tests are failing Unassigned * https://bugs.launchpad.net/neutron/+bug/1845145 [L3] add abilitiy for iptables_manager to ensure rule was added only once Liu is working on a fix: https://review.opendev.org/684237 * https://bugs.launchpad.net/neutron/+bug/1845161 Neutron QoS Policy lost on interfaces In progress, but likely needs another direction for a fix: https://review.opendev.org/684457 * https://bugs.launchpad.net/neutron/+bug/1845557 DVR: FWaaS rules created for a router after the FIP and VM created, not applied to routers rfp port on router-update Swami is working on it, no fix uploaded at the moment. Medium: * https://bugs.launchpad.net/neutron/+bug/1845176 Removing of QoS queue in neutron-ovs-agent fails due to existing references Unassigned * https://bugs.launchpad.net/neutron/+bug/1845364 [fullstack] Race condition when updating the router port information and updating the network MTU Rodolfo is working on it, no fix uploaded at the moment. Low: * https://bugs.launchpad.net/neutron/+bug/1845330 neutron-tempest-plugin API test for list agents failure Slawek is working on it, no fix uploaded at the moment. * https://bugs.launchpad.net/neutron/+bug/1845575 Networking Option 1: Provider networks in neutron Trivial doc-fix: https://review.opendev.org/685267 RFE: * https://bugs.launchpad.net/neutron/+bug/1845622 Decouple allow_address_pair service with security_group Incomplete: * https://bugs.launchpad.net/neutron/+bug/1845603 multiple type networks with different mtu cause vm connectivity problem * https://bugs.launchpad.net/neutron/+bug/1844915 Duplicate packets with two networks connected by router Cheers, Bence (rubasov)

1 0

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

28 Sep '19

# Keystone Team Update - Week of 23 September 2019 ## News ### RC1 is out! Keystone 16.0.0.0rc1 is now available to download[1]. Please try it out and report any bugs you find. The stable/train branch has been created, so release-critical fixes need to be committed in master and then backported to stable/train. [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-September/00975… ## Action Items n/a ## Office Hours When there are topics to cover, the keystone team holds office hours on Tuesdays at 17:00 UTC. We won't hold office hours next week. 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 25 changes this week, including the last few scope type changes needed to complete our policy migration. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 34 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ## Bugs This week we opened 6 new bugs and closed 10. Bugs opened (6) Bug #1845539 (keystone:Low) opened by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1845539 Bug #1845540 (keystone:Low) opened by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1845540 Bug #1845412 (keystone:Undecided) opened by jun923.gu https://bugs.launchpad.net/keystone/+bug/1845412 Bug #1845718 (keystone:Undecided) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1845718 Bug #1842930 (keystonemiddleware:Medium) opened by Morgan Fainberg https://bugs.launchpad.net/keystonemiddleware/+bug/1842930 Bug #1845209 (oslo.policy:High) opened by Ben Nemec https://bugs.launchpad.net/oslo.policy/+bug/1845209 Bugs closed (4) Bug #1842930 (keystone:Medium) https://bugs.launchpad.net/keystone/+bug/1842930 Bug #1840647 (keystone:Undecided) https://bugs.launchpad.net/keystone/+bug/1840647 Bug #1844621 (keystone:Undecided) https://bugs.launchpad.net/keystone/+bug/1844621 Bug #1845412 (keystone:Undecided) https://bugs.launchpad.net/keystone/+bug/1845412 Bugs fixed (6) Bug #1844461 (keystone:High) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1844461 Bug #1805880 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1805880 Bug #1818736 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1818736 Bug #1829453 (keystone:Low) fixed by Vishakha Agarwal https://bugs.launchpad.net/keystone/+bug/1829453 Bug #1829454 (keystone:Low) fixed by Kristi Nikolla https://bugs.launchpad.net/keystone/+bug/1829454 Bug #1843931 (oslo.policy:Medium) fixed by Ben Nemec https://bugs.launchpad.net/oslo.policy/+bug/1843931 ## Milestone Outlook https://releases.openstack.org/train/schedule.html The final Train release will happen in three weeks. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

mistral-dashboard 9.0.0.0rc1 (train)
by no-reply＠openstack.org 28 Sep '19

28 Sep '19

Hello everyone, A new release candidate for mistral-dashboard for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral-dashboard/ 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/mistral-dashboard/src/branch/stable/train Release notes for mistral-dashboard can be found at: https://docs.openstack.org/releasenotes/mistral-dashboard/

1 0