- openstack-discuss - lists.openstack.org

[nova] Wallaby spec review day, round 2
by Balázs Gibizer 20 Nov '20

20 Nov '20

Hi, We had a successful spec review day on Tuesday. Most of the open specs has got reviewer attention. We will do another coordinated spec review round on 1st of December. Cheers, gibi

1 0

[neutron] Drivers meeting 20.11.2020 - cancelled
by Slawek Kaplonski 19 Nov '20

19 Nov '20

Hi, As there is no any new RFE to discuss, lets cancel this week's meeting. Please instead spent some time on reviewing some opened specs to approved RFEs [1]. Especially: * https://review.opendev.org/#/c/729532/ * https://review.opendev.org/#/c/739549/ * https://review.opendev.org/#/c/728628/ Have a great weekend and see You all online :) [1] https://review.opendev.org/#/q/project:openstack/neutron-specs++status:open -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[tripleo] Copying tripleo container images to quay.io
by Arx Cruz 19 Nov '20

19 Nov '20

Hello, I just wrote a tool in go that is right now copying every 2 hours all the containers from rdo registry to quay.io. Right now it's copying all branches: master, victoria, ussuri, train, stein, queens and rocky. You can see the containers in https://quay.io/tripleo{release} for example https://quay.io/tripleomaster The tool basically searches for container build jobs with success status, parse the containers that was built, copy these containers to quay.io and tag it with current-tripleo and the built hash. The code it's based on skopeo, and I did not use it, because there are some other stuff required on quay.io side that requires the use of quay.io api, like create an already public repository, parsing the tripleo container build job, tagging, etc. Also I wanted to play with go :) Right now the code is under review at https://review.rdoproject.org/r/#/c/31133/ and I got it running on our toolbox, and he's an log example (without the --debug flag) time="2020-11-19T12:06:17Z" level=info msg="Copying image centos-binary-horizon:4fad79713786f77292e59fa1c036f588 in tripleoussuri namespace" time="2020-11-19T12:06:18Z" level=info msg="Tagging current-tripleo to sha256:db39e7d43d4c8eec82f61acd4956d7f165b595d515f270f8dabe0c9b009c95f2" "Updated" time="2020-11-19T12:06:19Z" level=info msg="Copying image centos-binary-ceilometer-base:4fad79713786f77292e59fa1c036f588 in tripleoussuri namespace" time="2020-11-19T12:06:20Z" level=info msg="Tagging current-tripleo to sha256:5eee849a9f74d0107cbfd2f456f701be37256ea711079cffcc189d140e8f3176" "Updated" time="2020-11-19T12:06:21Z" level=info msg="Copying image centos-binary-gnocchi-base:4fad79713786f77292e59fa1c036f588 in tripleoussuri namespace" time="2020-11-19T12:06:22Z" level=info msg="Tagging current-tripleo to sha256:5b46ea43d41e56dd81005a234631905a8ad594ef8432ae78542392114956f85e" "Updated" If you want to play around with this, feel free to do so, and any feedback is welcome :) Kind regards, -- Arx Cruz Software Engineer Red Hat EMEA <https://www.redhat.com> arxcruz(a)redhat.com @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

4 4

[release] Meeting Time Poll
by Herve Beraud 19 Nov '20

19 Nov '20

Hello We have a few regular attendees of the Release Management meeting who have conflicts with the current meeting time. As a result, we would like to find a new time to hold the meeting. I've created a Doodle poll[1] for everyone to give their input on times. It's mostly limited to times that reasonably overlap the working day in the US and Europe since that's where most of our attendees are located. If you attend the Release Management meeting, please fill out the poll so we can hopefully find a time that works better for everyone. Thanks! [1] https://doodle.com/poll/7zgvfb8ne54bwhzw -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 1

[oslo][release] Oslo's Transition To Independent
by Herve Beraud 19 Nov '20

19 Nov '20

Greetings, Is it time for us to move some parts of Oslo to the independent release model [1]? I think we could consider Oslo world is mostly stable enough to answer yes to the previous question. However, the goal of this email is to trigger the debat and see which deliverables could be transitioned to the independent model. Do we need to expect that major changes will happen within Oslo and who could warrant to continue to follow cycle-with-intermediary model [2]? The following etherpad [3] is designed to help us to consider which deliverables could be moved. Concerning the roots of this topic, it was raised during the PTG of the Release Management Team [4]. [1] https://releases.openstack.org/reference/release_models.html#independent [2] https://releases.openstack.org/reference/release_models.html#cycle-with-int… [3] https://etherpad.opendev.org/p/oslo-transition-to-independent [4] https://etherpad.opendev.org/p/wallaby-ptg-os-relmgt /me takes off Oslo team hat and puts on release team hat. This kind of transition could be an option for all stable libraries even outside the Oslo scope, don't hesitate to consider this as an option for your projects. Thanks for reading, -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

3 7

NUMATopologyFilter and AMD Epyc Rome
by Eyle Brinkhuis 19 Nov '20

19 Nov '20

Hi all, We’re running into an issue with deploying our infrastructure to run high throughput, low latency workloads. Background: We run Lenovo SR635 systems with an AMD Epyc 7502P processor. In the BIOS of this system, we are able to define the amount of NUMA cells per socket (called NPS). We can set 1, 2 or 4. As we run a 2x 100Gbit/s Mellanox CX5 in this system as well, we use the preferred-io setting in the BIOS to give preferred io throughput to the Mellanox CX5. To make sure we get as high performance as possible, we set the NPS setting to 1, resulting in a single numa cell with 64 CPU threads available. Next, in Nova (train distribution), we demand huge pages. Hugepages however, demands a NUMAtopology, but as this is one large NUMA cell, even with cpu=dedicated or requesting a single numa domain, we fail: compute03, compute03 fails NUMA topology requirements. No host NUMA topology while the instance specified one. host_passes /usr/lib/python3/dist-packages/nova/scheduler/filters/numa_topology_filter.py:119 Any idea how to counter this? Setting NPS-2 will create two NUMA domains, but also cut our performance way down. Thanks! Regards, Eyle

3 5

[cinder] Ceph, active-active and no coordination
by Radosław Piliszek 19 Nov '20

19 Nov '20

Dear Cinder Masters, I have a question for you. (or two, or several; well, actually the whole Kolla team has :-) ) The background is that Kolla has been happily deploying multinode cinder-volume with Ceph RBD backend, with no coordination configured, cluster parameter unset, host properly set per host and backend_host normalised (as well as any other relevant config) between the cinder-volume hosts. The first question is: do we correctly understand that this was an active-active deployment? Or really something else? Now, there have been no reports that it misbehaved for anyone. It certainly has not for any Kolla core. The fact is it was brought to our attention because due to the drop of Kolla-deployed Ceph, the recommendation to set backend_host was not present and users tripped over non-uniform backend_host. And this is expected, of course. The second and final question is, building up on the first one, were we doing it wrong all the time? (plus extras: Why did it work? Were there any quirks? What should we do?) PS: Please let me know if this thought process is actually Ceph-independent as well. -yoctozepto

5 5

Ask a question about nova console
by Yingji Sun 18 Nov '20

18 Nov '20

Buddies, I hit an issue on nova console. In vm console, it only handles keyboard event, but not mouse event. That is I can only use keyboard in the vm, but not mouse. The backend is vsphere. I can use both keyboard and mouse through vsphere remote console. So where does the issue likely hide ? Is there any option in nova configure file that relates to this issue ? Any feedback would be appreciated. Yingji.

1 1

Clone Cinder-Backed Image (Ussuri)
by Lazuardi Nasution 18 Nov '20

18 Nov '20

Hi, I have made a cinder-backed image where my cinder is RBD-backed. The backing topology of that image is as follows. glance -> cinder -> RBD. Is it possible to clone that image like RBD-backed images? I think the following bluprint is related but I don't know if it has been implemented yet, at least on Ussuri. https://blueprints.launchpad.net/cinder/+spec/clone-image-in-glance-cinder-… Best regards,

2 2

[neutron] HA network issues on Rocky
by Jean-Philippe Méthot 18 Nov '20

18 Nov '20

Hi, We’ve been running an Openstack setup in production for several years and we upgraded it to Rocky last May. We are now creating a router for a new project for the first time since that upgrade and we’ve been running into issues with L3HA for that router. Essentially, the router for this project gets initialized with a faulty HA network. How do I know it’s faulty? -Both Keepalived instances think they are master. -Both HA network ports get the wrong MTU (9000 instead of 8958) -Even if I manually set the proper MTU, VRRP packets don’t get received on the other node -If I then disable and enable the router, MTU gets rolled back to 9000 -If I force the MTU for this port through the neutron database, it will also get rolled back to 9000 once the router gets recreated This setup is using openvswitch and GRE tunnels. I have 7 other projects with L3HA routers running and they do not have this issue, even if I create new routers in them. They are also older projects created before the upgrade to Rocky. This problem is strictly isolated to this new project. I’m not sure exactly what’s going on here and why Openstack isn’t taking encapsulation into account when automatically setting its HA network MTU for this. Any suggestion on how to figure out what’s happening behind the scene? Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc. 4414-4416 Louis B Mayer Laval, QC, H7P 0G1, Canada TEL : +1.514.802.1644 - Poste : 2644 FAX : +1.514.612.0678 CA/US : 1.855.774.4678 FR : 01 76 60 41 43 UK : 0808 189 0423

1 1

Fwd: [sdk] issue in update image method
by Roman Budnyk 18 Nov '20

18 Nov '20

Hello dear developers, I was trying to update image data by calling method *update_image_properties. *Each time I was facing the error: TypeError: existing() argument after ** must be a mapping, not str I did small research in the source code and found a strange solution. Could you please check this place in the code: class BaseImageProxy, method update_image_properties (path /openstack/_base_proxy.py): [image: image.png] When I changed it to the below - everything works (with name, id or image instance): [image: image.png] could you please check on your end, why the construction *if image is None *is using and how can we execute the code *self._connection.get_image(image) *if None is passing as the argument. Many thanks! Regards, Roman

2 4

[cinder] python-cinderclient: API v2 support removed in Wallaby
by Brian Rosmaita 18 Nov '20

18 Nov '20

As announced previously on this mailing list [0], at yesterday's Cinder meeting the Cinder team discussed the timeline for removing Block Storage API v2 support from the python-cinderclient. The Block Storage API v2, which has been deprecated since Pike, will not be present in the OpenStack Wallaby release. The team decided not to delay removing Block Storage API v2 support from the python-cinderclient. Thus, v2 support will *not* be available in the Wallaby python-cinderclient. Given the long deprecation period, we trust that this will not adversely impact too many users. We point out that microversion 3.0 of the Block Storage API v3 is functionally identical to v2; thus scripts that rely on v2 responses should continue to work with minimal changes. We also point out that v3 has been available since Mitaka and has reached microversion 3.62 with the Victoria release; thus it may be worth re-examining such scripts to see what functionality you are missing out on. This email serves both as an announcement and a final call for comments about this proposal. Please reply to this email thread with any comments before next week's Cinder meeting (Wednesday 18 November 2020). Thank you, brian [0] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018531…

1 1

[openstack][stein][cinder] iscsi multipath issues
by Ignazio Cassano 18 Nov '20

18 Nov '20

Hello Everyone, I am testing stein with cinder iscsi driver for unity. Since I became crazy on queens, I decided to try with stein. At this time I have only one virtual machine with only one iscsi volume. It was running on podiscsivc-kvm02 and I migrated it on podiscsivc-kvm01. Let me show what multipath -ll displays on podiscsivc-kvm02 after live migration: 36006016006e04400dce5b45f0ac77301 dm-3 DGC ,VRAID size=40G features='1 retain_attached_hw_handler' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=0 status=active | `- 17:0:0:60 sdm 8:192 failed faulty running `-+- policy='round-robin 0' prio=0 status=enabled |- 19:0:0:60 sdk 8:160 failed faulty running `- 21:0:0:60 sdj 8:144 failed faulty running And now on destination node podiscsivc-kvm01: 36006016006e04400dce5b45f0ac77301 dm-3 DGC ,VRAID size=40G features='2 queue_if_no_path retain_attached_hw_handler' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=50 status=active | |- 17:0:0:14 sdm 8:192 active ready running | `- 15:0:0:14 sdl 8:176 active ready running `-+- policy='round-robin 0' prio=10 status=enabled |- 21:0:0:14 sdj 8:144 active ready running `- 19:0:0:14 sdk 8:160 active ready running On source node in /var/log/messages I get: Nov 18 10:34:19 podiscsivc-kvm02 multipathd: 36006016006e04400dce5b45f0ac77301: failed in domap for addition of new path sdl Nov 18 10:34:19 podiscsivc-kvm02 multipathd: 36006016006e04400dce5b45f0ac77301: uev_add_path sleep Nov 18 10:34:20 podiscsivc-kvm02 multipathd: 36006016006e04400dce5b45f0ac77301: failed in domap for addition of new path sdl Nov 18 10:34:20 podiscsivc-kvm02 kernel: device-mapper: table: 253:3: multipath: error getting device Nov 18 10:34:20 podiscsivc-kvm02 kernel: device-mapper: ioctl: error adding target to table Nov 18 10:34:20 podiscsivc-kvm02 multipathd: 36006016006e04400dce5b45f0ac77301: uev_add_path sleep On storage node seems it wotks fine, because the host access migrated from source to destination node. Multipath.conf is the following: blacklist { # Skip the files uner /dev that are definitely not FC/iSCSI devices # Different system may need different customization devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^hd[a-z][0-9]*" devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]" # Skip LUNZ device from VNX/Unity device { vendor "DGC" product "LUNZ" } } defaults { user_friendly_names no flush_on_last_del yes remove_retries 12 skip_kpartx yes } devices { # Device attributed for EMC CLARiiON and VNX/Unity series ALUA device { vendor "DGC" product ".*" product_blacklist "LUNZ" path_grouping_policy group_by_prio path_selector "round-robin 0" path_checker emc_clariion features "0" no_path_retry 12 hardware_handler "1 alua" prio alua failback immediate } } Why it leaves failed faulty running devices ? Is it a correct behaviour ? Every time I migrate my single instance from a node to another the number of files under /dev/disk/by-path increase of 4 (the number of path used for unity storage) on the destination node. I contacted Dell support and they said it is not an a problem of their cinder driver but ti could be related to nova. Please help me !!! I must decide if acquire nfs storage or iscsi storage. On the cinder compatibility drive matrix most vendors are iscsi.

1 2

[octavia] Octavia weekly IRC meeting is cancelled November 25th
by Michael Johnson 18 Nov '20

18 Nov '20

A number of the Octavia community members will be taking vacation next week, so we will be cancelling the meeting next week on the 25th. Enjoy your break! Michael

1 0

[largescale-sig] Next meeting: November 18, 14utc
by Thierry Carrez 18 Nov '20

18 Nov '20

Hi everyone, After a well-deserved break after the Summit and the PTG, the Large Scale SIG is back with regular meetings this Wednesday in #openstack-meeting-3 on IRC, at our new time: 14UTC. See how it translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201118T14 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting Talk to you all later, -- Thierry Carrez

1 1

[tripleo] next meeting Tuesday Nov 24 @ 1400 UTC in #tripleo
by Marios Andreou 18 Nov '20

18 Nov '20

Hello TripleOs reminder our next scheduled irc meeting is ** Tuesday 24th November at 1400 UTC in #tripleo. ** ** https://etherpad.opendev.org/p/tripleo-meeting-items ** Please add anything you want to raise at https://etherpad.opendev.org/p/tripleo-meeting-items This could be anything including review requests, any blocking issues or major ongoing work. Our last meeting was held on the 10th - you can find the logs there http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-11-10-14.… thanks, marios

1 0

Re: Where to send mascot graphic adjustment proposals
by James Cole 18 Nov '20

18 Nov '20

Hi Michael, I’m James Cole, a graphic designer at the Open Infrastructure Foundation. Hopefully I can address some of your questions. Regarding the diagram, I’m told it is managed by Designate in their documentation. We can provide suggestions but ultimately it is up to them how they want to create those docs. You may have to get in touch with an active contributor to that project. Regarding mascot design changes, we’d need broader community input to make edits like that. The mascot designs undergo a community review process with each project when they’re created, so we’re unable to make design changes at this time. If it helps, the mark is vertically aligned with the text, not base aligned. Enlarging the crocodile will probably make it seem disproportionately large compared with other project mascots, which all follow the same design rules. Thanks for flagging the inactive email address for Anne. Would you mind providing the URL of the page you found that address? We will replace it with community(a)openinfra.dev <mailto:community@openinfra.dev> as the contact email for mascots. Thanks for reaching out! James Cole Graphic Designer Open Infrastructure Foundation

2 3

[horizon] Weekly Meeting time poll
by Ivan Kolodyazhny 18 Nov '20

18 Nov '20

Hi team, As discussed during the last meeting, let's vote for a new meeting time for Horizon. You can vote for the current time if it's OK for you: https://doodle.com/poll/a5eeh6h3v356w8ss Feel free to reach me by e-mail or in IRC if you have any questions. Regards, Ivan Kolodyazhny

1 0

Failed to Create Virtual Instances for manila Service Due to neutron and nova Services
by ninad jadhav 18 Nov '20

18 Nov '20

Hi, I am trying to deploy OpenStack, using Openstack installation guide https://docs.openstack.org/install-guide/openstack-services.html#minimal-de… . I am able to launch self-service instance, but during manila(shared-file System) creation I am getting share creation error as per manila-share.log "SSH to default NFS server (10.254.0.0/24) failed. I did all the necessary steps required as per document provided but still not able to create Instances. For Neutron Service I have used Linuxbridge (Networking Option 2). Following are the error logs and configuration file for nova and neutron services. As per my discussion with manila developer manila.conf file looks fine but there is an issue with minimal deploy which allows to create virtual machine but for further manila instance creation its failing due to 1. manila-share.log https://gist.github.com/Ninad-cloud/8c77ccb53df26e6c32505a30c988004c 2. nov-log for instance https://gist.github.com/Ninad-cloud/9129f1c25147e5ee7b874b77e591c9ad 2. controller - neutron all conf files https://gist.github.com/Ninad-cloud/bb25e70007a2bd9ea0848edb081f6525 https://gist.github.com/Ninad-cloud/61b3d357953ddaacc16a926770fbdb72 https://gist.github.com/Ninad-cloud/624a4846157fc294bdfa59093e49fa55 https://gist.github.com/Ninad-cloud/5bb3ad0cb9a38582a7c82816de653693 https://gist.github.com/Ninad-cloud/7366ca93b03f4718a424352fe8ec63e8 https://gist.github.com/Ninad-cloud/56ea190a333cbe0102b676b7de48b7ae 3.compute- neutron all .conf files https://gist.github.com/Ninad-cloud/8b25f38bfcd001177b8f5857f6aacd96 https://gist.github.com/Ninad-cloud/0fba595e3f3cce56695a3fc3c4795d3d https://gist.github.com/Ninad-cloud/c8538c5b00ed2760163c3c73d1247145 https://gist.github.com/Ninad-cloud/73f8bddebf032ea5a5e50023cc7808df 4.controller-nova .conf file https://gist.github.com/Ninad-cloud/4ed5b009a62e9fbc5f9e32ddfb3f1e67 5. compute-nova .conf file https://gist.github.com/Ninad-cloud/f21cd484dd9ad6c0befc66ba3c54457e regards, Ninad

2 3

[kolla] How to recover MariaDB if there's a controller failed to boot?
by Eddie Yen 18 Nov '20

18 Nov '20

Hi everyone, We met an issue few days ago. When we launch Openstack cluster, we found that there's a controller couldn't boot up caused by hardware failure, And MariaDB lost sync after left controllers booted into system. In this case, Can I just mark down the failed controller hostname in inventory file and do mariadb_recovery? Any risk after do this after failure one back online? Many thanks, Eddie.

3 6

[stein][cinder][iscsi] multipath does not seem to detach during live migration
by Ignazio Cassano 18 Nov '20

18 Nov '20

Hello Everyone, I am testing stein with cinder iscsi driver for unity. Since I became crazy on queens, I decided to try with stein. At this time I have only one virtual machine with only one iscsi volume. It was running on podiscsivc-kvm02 and I migrated it on podiscsivc-kvm01. Let me show what multipath -ll displays on podiscsivc-kvm02 after live migration: 36006016006e04400dce5b45f0ac77301 dm-3 DGC ,VRAID size=40G features='1 retain_attached_hw_handler' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=0 status=active | `- 17:0:0:60 sdm 8:192 failed faulty running `-+- policy='round-robin 0' prio=0 status=enabled |- 19:0:0:60 sdk 8:160 failed faulty running `- 21:0:0:60 sdj 8:144 failed faulty running And now on destination node podiscsivc-kvm01: 36006016006e04400dce5b45f0ac77301 dm-3 DGC ,VRAID size=40G features='2 queue_if_no_path retain_attached_hw_handler' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=50 status=active | |- 17:0:0:14 sdm 8:192 active ready running | `- 15:0:0:14 sdl 8:176 active ready running `-+- policy='round-robin 0' prio=10 status=enabled |- 21:0:0:14 sdj 8:144 active ready running `- 19:0:0:14 sdk 8:160 active ready running On source node in /var/log/messages I get: Nov 18 10:34:19 podiscsivc-kvm02 multipathd: 36006016006e04400dce5b45f0ac77301: failed in domap for addition of new path sdl Nov 18 10:34:19 podiscsivc-kvm02 multipathd: 36006016006e04400dce5b45f0ac77301: uev_add_path sleep Nov 18 10:34:20 podiscsivc-kvm02 multipathd: 36006016006e04400dce5b45f0ac77301: failed in domap for addition of new path sdl Nov 18 10:34:20 podiscsivc-kvm02 kernel: device-mapper: table: 253:3: multipath: error getting device Nov 18 10:34:20 podiscsivc-kvm02 kernel: device-mapper: ioctl: error adding target to table Nov 18 10:34:20 podiscsivc-kvm02 multipathd: 36006016006e04400dce5b45f0ac77301: uev_add_path sleep On storage node seems it wotks fine, because the host access migrated from source to destination node. Multipath.conf is the following: blacklist { # Skip the files uner /dev that are definitely not FC/iSCSI devices # Different system may need different customization devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^hd[a-z][0-9]*" devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]" # Skip LUNZ device from VNX/Unity device { vendor "DGC" product "LUNZ" } } defaults { user_friendly_names no flush_on_last_del yes remove_retries 12 skip_kpartx yes } devices { # Device attributed for EMC CLARiiON and VNX/Unity series ALUA device { vendor "DGC" product ".*" product_blacklist "LUNZ" path_grouping_policy group_by_prio path_selector "round-robin 0" path_checker emc_clariion features "0" no_path_retry 12 hardware_handler "1 alua" prio alua failback immediate } } Why it leaves failed faulty running devices ? Is it a correct behaviour ? I contacted Dell support and they said it is not an a problem of their cinder driver but ti could be related to nova. Please help me !!! I must decide if acquire nfs storage or iscsi storage. On the cinder compatibility drive matrix most vendors are iscsi. Ignazio

1 1

[docs] HTTP redirects
by Peter Matulis 18 Nov '20

18 Nov '20

Hi, So I followed instructions [1] to implement redirects and it's not working. Please let me know where I went wrong: https://review.opendev.org/#/c/763067/ Shouldn't the first URL redirect to the second? https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/late… https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/late… Thanks, Peter [1]: https://docs.openstack.org/doc-contrib-guide/redirects.html

3 2

[Victoria][Python-3.9] dhcp-agent problem
by tjoen 17 Nov '20

17 Nov '20

System: LFS. Python-3.9.0, Neutron-17.0.0, oslo.privsep-2.4.0 Got Train+Py37, Usuri+Py38 working with the help of the install-guide. Victoria+Py39 Only eventlet needed a patch. Neutron only for neutron/plugins/ml2/drivers/linuxbridge/agent/arp_protect.py def ebtables(comm, table='nat'): execute = ip_lib.IPWrapper(NAMESPACE).netns.execute - return execute(['ebtables', '-t', table, '--concurrent'] + comm, + return execute(['/usr/sbin/ebtables', '-t', table, '--concurrent'] + comm, run_as_root=True) Possible not necessary but it avoids sudo errors. Controller logs (made readable): [-] Unable to enable dhcp for cb7948eb-e5c0-4764-a653-542c3e864f54.: TypeError: <lambda>() takes 6 positional arguments but 7 were given Traceback (most recent call last): File "/site-packages/neutron/agent/dhcp/agent.py", line 192, in call_driver rv = getattr(driver, action)(**action_kwargs) File "/site-packages/neutron/agent/linux/dhcp.py", line 249, in enable common_utils.wait_until_true(self._enable, timeout=300) File "/site-packages/neutron/common/utils.py", line 703, in wait_until_true while not predicate(): File "/site-packages/neutron/agent/linux/dhcp.py", line 261, in _enable interface_name = self.device_manager.setup(self.network) File "/site-packages/neutron/agent/linux/dhcp.py", line 1675, in setup if ip_lib.ensure_device_is_ready(interface_name, File "/site-packages/neutron/agent/linux/ip_lib.py", line 960, in ensure_device_is_ready if not dev.link.exists or not dev.link.address: File "/site-packages/neutron/agent/linux/ip_lib.py", line 513, in exists return privileged.interface_exists(self.name, self._parent.namespace) File "/site-packages/oslo_privsep/priv_context.py", line 247, in _wrap return self.channel.remote_call(name, args, kwargs) File "/site-packages/oslo_privsep/daemon.py", line 224, in remote_call raise exc_type(*result[2]) TypeError: <lambda>() takes 6 positional arguments but 7 were given Launching an instance: $ openstack server create --flavor m1.nano --image cirros \ --nic net-id=cb7948eb-e5c0-4764-a653-542c3e864f54 --security-group default \ --key-name mykey provider-instance results in status=BUILD and never ACTIVE Other logs on Controller after starting Compute1: Unable to access /var/lib/neutron/dhcp/cb7948eb-e5c0-4764-a653-542c3e864f54/pid; Error: [Errno 2] No such file or directory Ownerships and permissions are OK: drwxr-xr-x 2 neutron neutron 4096 Nov 15 19:49 cb7948eb-e5c0-4764-a653-542c3e864f54/ Anybody with the same problem? I am not a Python programmer so I am at a lost

3 5

[release][infra] Discrepancy between release jobs and the "normal" jobs CI in terms of distro
by Radosław Piliszek 17 Nov '20

17 Nov '20

I did not quote the original subject because it was too long. It was: [release][masakari] - [Release-job-failures] Release of openstack/masakari-monitors for ref refs/tags/(7.0.1|8.0.2|9.0.1) failed Particularly, we are continuing the discussion from: http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018743… Would it be possible what Hervé is proposing? I.e. better segregation of distro per branch of release? I believe it would be a rare situation but surely testing something on Bionic and trying to release on Focal might have its quirks. -yoctozepto

4 4

[release][masakari] - [Release-job-failures] Release of openstack/masakari-monitors for ref refs/tags/(7.0.1|8.0.2|9.0.1) failed
by Herve Beraud 17 Nov '20

17 Nov '20

During the release job for: - masakari-monitors 9.0.1 (ussuri) - masakari-monitors 8.0.2 (train) - masakari-monitors 7.0.1 (stein) uploads to PyPI failed [1][2][3] with: "No package matching 'python-libvirt' is available" [4][5][6] It's due to our recent move to focal [7] where the package 'python-libvirt' is named ''python3-libvirt'.This package is pulled by bindep during the job execution. Current status: Tag (9.0.1, 8.0.2, 7.0.1) was pushed OK No tarball upload No PyPI upload Once the issue is fixed, a new version should be released for the three stables branches. Version 9.0.1, 8.0.2, 7.0.1 these versions will never be uploaded on PyPi as the fix requires new changes in the project repo [8][9][10]. Also notice that on Victoria and Wallaby this bindep requirement have been dropped during the migration testing on ubuntu focal [11]. [1] https://zuul.opendev.org/t/openstack/build/63539177d44b4ea48d3fbfe39a638275… [2] https://zuul.opendev.org/t/openstack/build/778ace86ec8f4ef894d740d81e8f700f… [3] https://zuul.opendev.org/t/openstack/build/919cfc7df1e0408e9d6af4a9e8ef28ee… [4] http://lists.openstack.org/pipermail/release-job-failures/2020-November/001… [5] http://lists.openstack.org/pipermail/release-job-failures/2020-November/001… [6] http://lists.openstack.org/pipermail/release-job-failures/2020-November/001… [7] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018585… [8] https://opendev.org/openstack/masakari-monitors/src/branch/stable/stein/bin… [9] https://opendev.org/openstack/masakari-monitors/src/branch/stable/train/bin… [10] https://opendev.org/openstack/masakari-monitors/src/branch/stable/ussuri/bi… [11] https://opendev.org/openstack/masakari-monitors/commit/03ef3555888fdd0ea38b… -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

3 9

[tc] weekly update
by Mohammed Naser 17 Nov '20

17 Nov '20

Hi everyone, Here's an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. # Patches ## Open Reviews - Add Magpie charm to OpenStack charms https://review.opendev.org/762820 - Move Placement under Nova's governance https://review.opendev.org/760917 - Add Resolution of TC stance on the OpenStackClient https://review.opendev.org/759904 - Remove assert_supports-zero-downtime-upgrade tag https://review.opendev.org/761975 - Add election schedule exceptions in charter https://review.opendev.org/751941 - Clarify the requirements for supports-api-interoperability https://review.opendev.org/760562 - Propose Kendall Nelson for vice chair https://review.opendev.org/762014 ## General Changes - Select JSON to YAML goal for Wallaby cycle https://review.opendev.org/760957 - Adding reno and warnings example for JSON->YAML goal doc https://review.opendev.org/760956 - Add danms liaison preferences https://review.opendev.org/758822 - Add goal for migrate RBAC policy format from JSON to YAML https://review.opendev.org/759881 - Add diablo_rojo liaison preferences https://review.opendev.org/759718 - Add ricolin liaison preferences https://review.opendev.org/759704 - Add gmann liaison preference https://review.opendev.org/758602 - Resetting projects' TC liaisons empty https://review.opendev.org/758600 Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[Freezer] Gerrit breach and commit audit
by caihui_nj＠163.com 17 Nov '20

17 Nov '20

1 0

[neutron] Team meetings today
by Slawek Kaplonski 17 Nov '20

17 Nov '20

Hi, Just a quick reminder that we have neutron team meeting today at 14:00 UTC and neutron CI meeting at 15:00 UTC. Both are on the #openstack-meetings-3 channel. Agenda for the meetings: https://wiki.openstack.org/wiki/Network/Meetings https://etherpad.opendev.org/p/neutron-ci-meetings -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[Freezer] Gerrit breach and commit audit
by caihui_nj＠163.com 17 Nov '20

17 Nov '20

1 0

[infra][kolla] Docker registry pull limits
by Radosław Piliszek 17 Nov '20

17 Nov '20

Hello Everyone, Kolla CI jobs started getting hit by Docker registry pull limits: docker.errors.APIError: 500 Server Error: Internal Server Error ("toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit") It is relatively random as the limit is seemingly per IP address. The question is how we should approach this issue. It seems Docker offers an open source plan that would lift any limits on the kolla namespace. [1] However, we are not entirely sure who should fill out the related form [2]. We believe it should be someone from the infra team but it is not clear. :/ Please share your thoughts. [1] https://www.docker.com/blog/expanded-support-for-open-source-software-proje… [2] https://docs.google.com/forms/d/e/1FAIpQLSd11DjfgeaKSRdqp6Br85MzQQuM4igt-xm… -yoctozepto

1 0

[manila][OSC] Priorities for implementing the OSC share commands
by Maari Tamm 17 Nov '20

17 Nov '20

Hi Everyone! Slowly but steady we are implementing the OpenStack Client for Manila. For the upcoming release we are aiming to implement the following commands, in no particular order: Share Replicas: openstack share replica create / delete / list / show / set / promote / resync Share Replica Export Locations: openstack share replica export location list / show Share Manage/Unmanage: openstack share adopt / abandon Services: openstack share service set / list Share Pools: openstack share pool list User Messages: openstack share message delete / list / show Availability Zones (add support for manila): openstack availability zone list Limits (add support for manila): openstack limits show —absolute /—rate Share Export Locations (ready for reviews: https://review.opendev.org/#/c/761661/ <https://review.opendev.org/#/c/761661/>): openstack share export location list / show Share Snapshots patch II (ready for reviews: https://review.opendev.org/#/c/746458/ <https://review.opendev.org/#/c/746458/>) : openstack share snapshot adopt / abandon openstack share snapshot export location show / list openstack share snapshot access create / delete / list To make this happen we could really use help reviewing the patches, once proposed. As linked above, two patches are currently ready for testing/reviews. We’d also very much appreciate getting some feedback on the list itself. Are we missing something important that would be useful for operators and should be implemented this cycle? If anyone has some commands in mind, please do let us know! Mohammed Naser and Belmiro Moreira, would love to get your thoughts on this as well! :) Thanks, Maari Tamm (IRC: maaritamm)

2 1

[Heat] Fwaas v2 support
by Yves Gd 17 Nov '20

17 Nov '20

Hi, Trying to use a HOT firewall template, I encounter this error: "ERROR: HEAT-E99001 Service neutron is not available for resource type OS::Neutron::Firewall, reason: Required extension fwaas in neutron service is not available." We use fwaas v2, is it supported by heat module on Train version? Our openstack environment is deployed by kolla (9.2.0) with fwaas enabled. I assume "yes" but would like to be sure. Sorry if it's written somewhere but I couldn't find this information. Here is a simple version producing the error: ------------------- heat_template_version: rocky resources: firewall1: type: OS::Neutron::Firewall properties: description: Test fwaas name: Test_fwaas ------------------- Regards, Yves

3 2

[tacker] Skip IRC meeting on Nov 17th
by Yasufumi Ogawa 16 Nov '20

16 Nov '20

Hi tacker team, I am not available to join IRC meeting today. I'd like to cancel the meeting because we may have no topics, the problem of functional test has resolved and no urgent patches. Thanks, Yasufumi

1 0

[neutron] Mixed VLAN / VxLAN Network
by DHilsbos＠performair.com 16 Nov '20

16 Nov '20

All; We're getting ready to set up an OpenStack cloud, and I have some questions about networking. I apologize if this information if available already or if a question like this has already been asked. We intend to slot it in to a location which uses VLANs heavily. In particular, our DMZ is on a VLAN, with the subnet's gateway at our firewall. We plan to use VxLANs within OpenStack. Is it possible to make OpenStack aware of the DMZ VLAN, so that we can use it in projects? Is it possible to use the DMZ VLAN without routing through the OpenStack network node(s)? Thank you, Dominic L. Hilsbos, MBA Director - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

3 2

[SDK][OSC] Meeting Times
by Kendall Nelson 16 Nov '20

16 Nov '20

Hello! In the PTG session today we talked about doing some sort of regular meetings to kind of jump start things after the more recent lack of activity. We discussed beginning with more frequent meetings (a couple across the next few weeks) and then shifting to a more relaxed monthly cadence. I propose 15:00 UTC on the third thursday of each month as our monthly meeting time? If people agree, I will propose a patch :) As for the more frequent ones to keep the momentum from discussion from this week/last week. We could use that time (15 UTC) and date (Thursdays) and maybe just do them on Nov 12 and 19th to keep us moving? That gives us next week to catch up/ take a breath from the last two weeks, but not waiting till after the US Thanksgiving holiday. Let me know what you think! -Kendall Nelson (diablo_rojo)

4 6

[trove] Gerrit breach and commit audit
by Lingxian Kong 16 Nov '20

16 Nov '20

Background: http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html Looking back at the patches merged between 2020-10-01 and 2020-10-20, I can confirm that the trove deliverables repos look OK. --- Lingxian Kong Senior Software Engineer Catalyst Cloud www.catalystcloud.nz

1 0

Re: Trove backup issue (Victoria)
by Lingxian Kong 16 Nov '20

16 Nov '20

(adding openstack-discuss mailing list) Hi Justin, I don't think there is a backup docker image named "openstacktrove/db-backup-mysql5.0", the backup image only support 8.0 and 5.7. You can try "openstacktrove/db-backup-mysql5.7". --- Lingxian Kong Senior Software Engineer Catalyst Cloud www.catalystcloud.nz On Tue, Nov 17, 2020 at 3:26 AM Justin Anstes <janstes(a)gmail.com> wrote: > Hi, > > Apologies to contact you about this issue. I'm sure it's a simple fix but > I've not been able to find much on it. > > I'm testing the current Victoria release. All setup ok just that I'm not > able to backup to Swift, with the following error: > > 404 Client Error: Not Found ("pull access denied for > openstacktrove/db-backup-mysql5.0, repository does not exist or may require > \'docker login\': denied: requested access to the resource is denied") > > It appears to require a Docker login.I've attached the full log just in > case you might need it. Many thanks if you have time to check. > > Kind regards > > Justin >

1 0

[qa][policy] Testing strategy discussion for new RBAC (new scope and default role combinations)
by Ghanshyam Mann 16 Nov '20

16 Nov '20

Hello Everyone, To continue the discussion on how projects should test the new RBAC (scope as well as the new defaults combination), we will host a call on bluejeans on Tuesday 10th Nov 16.00 UTC. Lance has set up the room for that: https://bluejeans.com/749897818 Feel free to join if you are interested in that or would like to help with this effort. -gmann

2 2

[ironic] Review session for API JSON conversion
by Steve Baker 16 Nov '20

16 Nov '20

Due to timezones and the nature of the change series, we're doing some group scheduled review sessions of this series which converts the WSME based REST API to a JSON: https://review.opendev.org/#/q/status:open+topic:story/1651346 Discussion can happen on IRC in #ironic. The first session will be on this Tuesday, 7pm UTC, with a follow-up on Wednesday, 8am UTC. There is a calendar invite which I can add you to on request. cheers

1 0

[monasca] Predictive Analytics
by Giacomo Lanciano 16 Nov '20

16 Nov '20

Hi all, I am new to this community, as I have only recently started using OpenStack in my research. I am working on designing an "intelligent" auto-scaling mechanism, based on resources consumption metrics forecasts, leveraging on Monasca for metrics ingestion and processing. Digging into the Wiki/Documentation, I have stumbled upon the recently retired "monasca-analytics", that seems to cover pretty much (and way more of) what I had in mind to build on top of the monitoring component, to enable proactive auto-scaling decisions. I am very interested in knowing more about why such project has been abandoned and, more importantly, whether the effort has been redirected to another project that I am not aware of. Could you point me to any resource that you consider useful to contribute on these topics? Thanks in advance. Kind Regards. Giacomo -- Giacomo Lanciano Ph.D. Student in Data Science Scuola Normale Superiore, Pisa, Italy https://www.linkedin.com/in/giacomolanciano

2 1

centos-7 infra mirror issues, lp 1904418
by Wesley Hayutin 16 Nov '20

16 Nov '20

Greetings, Just wanted to raise awareness of the following bug https://bugs.launchpad.net/tripleo/+bug/1904418 http://mirror.centos.org/centos/7/rt/x86_64/repodata/repomd.xml is a 404 Thank you!

1 0

RE: Fwd: freezer
by Cyrille CARTIER 16 Nov '20

16 Nov '20

Hi Ali, Last week I’ve got a response in StoryBoard, thanks to Carl : « The bug is fixed in victoria, please update new version. Thanks. » My Colleague confirm that Ussuri version still have the same problem. Is it good for you with Stein ? We're going to test the Victoria version soon, I'll get back to you if it works. Thanks, Cyrille De : Ali Ebrahimpour [mailto:ali74.ebrahimpour@gmail.com] Envoyé : samedi 7 novembre 2020 08:06 À : Cyrille CARTIER <Cyrille.CARTIER(a)antemeta.fr>; smooney(a)redhat.com Objet : Re: Fwd: freezer hi Cyrille,sean thank you for attention I have this problem by requesting a backup with nova i used the ussuri version and two days ago got pull the version by opendev and had not changed and I want to try to install the Stein version with python2. Maybe it works correctly Did you find a solution for versions with python3? On Fri, Nov 6, 2020 at 12:08 PM Cyrille CARTIER <Cyrille.CARTIER(a)antemeta.fr<mailto:Cyrille.CARTIER@antemeta.fr>> wrote: Hi Ali, Which openstack version do you use ? I have a similar problem on my Train plateform (deployed by kolla-ansible), using freezer-scheduler. There are many commit for py3 correction for Ussuri and Victoria branch, in Git repository [1]. Did you try these version? I have already post the problem on StoryBoard [2] and Launchpad [3]. -----Message d'origine----- Objet : Re: Fwd: freezer On Thu, 2020-11-05 at 12:42 +0330, Ali Ebrahimpour wrote: > hi i recently install the freezer api and i have problem with using it > if run this command: > freezer-agent --debug --action backup --nova-inst-id > a143d11d-fa27-4716-9795-e03b4e601df4 --storage local --container > /tmp/ali --backup-name test --mode nova --engine nova > --no-incremental true > --log-file a.log --consistency-check > > and freezer api doesn't work current and error with: > Engine error: a bytes-like object is required, not 'str' > Engine error: Forced stop that looks like a python 3 issue im not sure how active it still is but it looks like its an issue between text string and byte strings > > Adn attach the log > please help me ! > > thank you for attention [1]: https://opendev.org/openstack/freezer [2]: https://storyboard.openstack.org/#!/project/openstack/freezer [3]: https://bugs.launchpad.net/freezer/+bug/1901179 Cyrille

1 0

Victoria RDO Release Announcement
by Amy Marrich 16 Nov '20

16 Nov '20

If you're having trouble with the formatting, this release announcement is available online https://blogs.rdoproject.org/2020/11/rdo-victoria-released/ --- RDO Victoria Released The RDO community is pleased to announce the general availability of the RDO build for OpenStack Victoria for RPM-based distributions, CentOS Linux and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Victoria is the 22nd release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available on the CentOS mirror network at http://mirror.centos.org/centos/8/cloud/x86_64/openstack-victoria/. The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Linux and is a member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS Linux users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. PLEASE NOTE: RDO Victoria provides packages for CentOS8 and python 3 only. Please use the Train release, for CentOS7 and python 2.7. Interesting things in the Victoria release include: - With the Victoria release, source tarballs are validated using the upstream GPG signature. This certifies that the source is identical to what is released upstream and ensures the integrity of the packaged source code. - With the Victoria release, openvswitch/ovn are not shipped as part of RDO. Instead RDO relies on builds from the CentOS NFV SIG. - Some new packages have been added to RDO during the Victoria release: - ansible-collections-openstack: This package includes OpenStack modules and plugins which are supported by the OpenStack community to help with the management of OpenStack infrastructure. - ansible-tripleo-ipa-server: This package contains Ansible for configuring the FreeIPA server for TripleO. - python-ibmcclient: This package contains the python library to communicate with HUAWEI iBMC based systems. - puppet-powerflex: This package contains the puppet module needed to deploy PowerFlex with TripleO. - The following packages have been retired from the RDO OpenStack distribution in the Victoria release: - The Congress project, an open policy framework for the cloud, has been retired upstream and from the RDO project in the Victoria release. - neutron-fwaas, the Firewall as a Service driver for neutron, is no longer maintained and has been removed from RDO. Other highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/victoria/highlights. Contributors During the Victoria cycle, we saw the following new RDO contributors: Amy Marrich (spotz) Daniel Pawlik Douglas Mendizábal Lance Bragstad Martin Chacon Piza Paul Leimer Pooja Jadhav Qianbiao NG Rajini Karthik Sandeep Yadav Sergii Golovatiuk Steve Baker Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all 58 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and redhat-website repositories: Adam Kimball Ade Lee Alan Pevec Alex Schultz Alfredo Moralejo Amol Kahat Amy Marrich (spotz) Arx Cruz Bhagyashri Shewale Bogdan Dobrelya Cédric Jeanneret Chandan Kumar Damien Ciabrini Daniel Pawlik Dmitry Tantsur Douglas Mendizábal Emilien Macchi Eric Harney Francesco Pantano Gabriele Cerami Gael Chamoulaud Gorka Eguileor Grzegorz Grasza Harald Jensås Iury Gregory Melo Ferreira Jakub Libosvar Javier Pena Joel Capitao Jon Schlueter Lance Bragstad Lon Hohberger Luigi Toscano Marios Andreou Martin Chacon Piza Mathieu Bultel Matthias Runge Michele Baldessari Mike Turek Nicolas Hicher Paul Leimer Pooja Jadhav Qianbiao.NG Rabi Mishra Rafael Folco Rain Leander Rajini Karthik Riccardo Pittau Ronelle Landy Sagi Shnaidman Sandeep Yadav Sergii Golovatiuk Slawek Kaplonski Soniya Vyas Sorin Sbarnea Steve Baker Tobias Urdin Wes Hayutin Yatin Karel The Next Release Cycle At the end of one release, focus shifts immediately to the next release i.e Wallaby. Get Started There are three ways to get started with RDO. To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. For a production deployment of RDO, use TripleO and you’ll be running a production cloud in short order. Finally, for those that don’t have any hardware or physical resources, there’s the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. Get Help The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org. The #rdo channel on Freenode IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS and TripleO IRC channels (#centos, #centos-devel, and #tripleo on irc.freenode.net) however we have a more focused audience within the RDO venues. Get Involved To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and #tripleo on the Freenode IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube.

1 0

[edge] Open Geospatial Consortium presentation on the next Edge WG call
by Ildiko Vancsa 16 Nov '20

16 Nov '20

Hi, I’m reaching out to draw your attention to an upcoming presentation on the Edge Computing Group weekly call next Monday. We will have a presentation from the Open Geospatial Consortium where you can learn about their use cases relevant to edge computing and more specifically about the importance of location in that context. In the remaining time on the call we will discuss some of the requirements of the use cases such as location-awareness of infrastructure services and look into collaboration opportunities. The call is on __Monday (November 16) at 1400 UTC__. If you are interested in joining the call and the discussions you can find the dial-in information here: https://wiki.openstack.org/wiki/Edge_Computing_Group#Next_meeting:_Monday_.… Please let me know if you have any questions. Thanks, Ildikó

1 1

[neutron] Bug Deputy Report Nov 9-16
by Lucas Alvares Gomes 16 Nov '20

16 Nov '20

Hi, This is the Neutron bug report of the week of 2020-11-09. Critical: * https://bugs.launchpad.net/neutron/+bug/1903982 - "[neutron-tempest-plugin] Error when executing "hostname" in the VM" Assigned to: Rodolfo Alonso * https://bugs.launchpad.net/neutron/+bug/1903531 - "Update of neutron-server breaks compatibility to previous neutron-agent version" Unassigned High: * https://bugs.launchpad.net/neutron/+bug/1904117 - "Nodes in the OVN scenario multinode jobs can't talk to each other" Assigned to: slaweq * https://bugs.launchpad.net/neutron/+bug/1903985 - " [functional] Timeouts during setting link attributes in the namepaces" Unassigned * https://bugs.launchpad.net/neutron/+bug/1903696 - "Security group OVO object don't reloads and make compatible rules objects" Assigned to: slaweq * https://bugs.launchpad.net/neutron/+bug/1903696 - "Security group OVO object don't reloads and make compatible rules objects" Assigned to: slaweq * https://bugs.launchpad.net/neutron/+bug/1903985 - "[functional] Timeouts during setting link attributes in the namepaces" Unassigned Medium: * https://bugs.launchpad.net/neutron/+bug/1903989 - " Bug in logging potentionally causing neutron to fail" Assigned to: Michal Arbet * https://bugs.launchpad.net/neutron/+bug/1903689 - "[stable/ussuri] Functional job fails - AttributeError: module 'neutron_lib.constants' has no attribute 'DEVICE_OWNER_DISTRIBUTED'" Unassigned * https://bugs.launchpad.net/neutron/+bug/1903433 - "The duplicate route in l3 router namespace results in North-South traffic breaking" Assigned to: yangjianfeng * https://bugs.launchpad.net/neutron/+bug/1903689 - "stable/ussuri] Functional job fails - AttributeError: module 'neutron_lib.constants' has no attribute 'DEVICE_OWNER_DISTRIBUTED" Unassigned * https://bugs.launchpad.net/neutron/+bug/1903982 - " [neutron-tempest-plugin] Error when executing "hostname" in the VM" Assigned to: Rodolfo Alonso * https://bugs.launchpad.net/neutron/+bug/1903989 - " Bug in logging potentionally causing neutron to fail" Assigned to: michalarbet Needs further triage: * https://bugs.launchpad.net/neutron/+bug/1904178 - "[ovn] neutron not support Vlan backed DVR N-Sredirect packet via localnet port," Unassigned * https://bugs.launchpad.net/neutron/+bug/1904041 - " Victoria neutron-db-sync fails with I38991de2b4_source_and_destination_ip_prefix_neutron_metering_rule.py" Unassigned * https://bugs.launchpad.net/neutron/+bug/1903835 - " linuxbridge-agent ERRORS with pyroute2.netlink.exceptions.NetlinkError if ipv6 link local address exist " Unassigned * https://bugs.launchpad.net/neutron/+bug/1903835 - "linuxbridge-agent ERRORS with pyroute2.netlink.exceptions.NetlinkError if ipv6 link local address exist" Unassigned Wishlist: * https://bugs.launchpad.net/neutron/+bug/1904188 - "Include standard attributes ID in OVO dictionaries to improve the OVN revision numbers operation" Assigned to: Rodolfo Alonso

1 0

[kolla] Proposing wu.chunyang for Kolla core
by Mark Goddard 16 Nov '20

16 Nov '20

Hi, I would like to propose adding wu.chunyang to the kolla-core and kolla-ansible-core groups. wu.chunyang did some great work on Octavia integration in the Victoria release, and has provided some helpful reviews. Cores - please reply +1/-1 before the end of Friday 13th November. Thanks, Mark

8 8

CloudKitty deployment on Train and/or Ussuri
by Thode Jocelyn 15 Nov '20

15 Nov '20

Hi, I was looking at the possibilities to have Rating-as-A-Service in our Openstack (currently train but planning to move to Ussuri) and I stumbled upon CloudKitty. I'm currently facing multiple issues with cloudkitty itself and with openstack-ansible. (We are using a containerized deployment with LXC) * I noticed that openstack-ansible has no playbook yet to install a service like CloudKitty even though starting from Ussuri it was added in the ansible-role-requirements.yml. I have created a small patch to be able to install CloudKitty via openstack-ansible and if this is of interest I could potentially submit a PR with this. * The os_cloudkitty role seems to kinda work and only with a relatively old version of CloudKitty. For example, here : https://opendev.org/openstack/openstack-ansible-os_cloudkitty/src/branch/st… since CloudKitty v8.0.0 the section should be named "[fetcher_keystone]", but I found no information as to which CloudKitty version should be used with this role. Does someone have any recommendation as to which version should be used and if there is any interest in improving the role to support more recent versions of CloudKitty? * Even when tweaking the configuration and installing v7.0.0 of Cloudkitty it only fixes cloudkitty-processor, I was never able to make cloudkitty-api work I always get an error like "Fatal Python error: Py_Initialize: Unable to get the locale encoding ModuleNotFoundError: No module named 'encodings'". Any input on this would be greatly appreciated. Cheers Jocelyn

4 5

[nova] MessageUndeliverable from nova-conductor and MessagingTimeout from nova-compute
by Tony Liu 15 Nov '20

15 Nov '20

It's not about connection, but message transmitting. Title is changed. I am having rabbitmq 3.8.4 and nova 21.0.0. When I check rabbitmq queues for compute, I see 3 messages in compute.compute-1 and 0 messages in other compute node queues. In nova-conductor log of all 3 instances, I see "oslo_messaging.exceptions.MessageUndeliverable". In nova-compute log on compute-1, I see "Timed out waiting for nova-conductor." Actually, 4 out of 5 compute nodes have such warning. One compute node has exception "oslo_messaging.exceptions.MessagingTimeout". "rabbitmqctl list_bindings | grep compute-1" shows this. ================================= exchange compute.compute-1 queue compute.compute-1 [] nova exchange compute.compute-1 queue compute.compute-1 [] ================================= Is this some known issue? How did it happen? What's the cause of it and any way to prevent it from happening? Thanks! Tony > -----Original Message----- > From: Arnaud Morin <arnaud.morin(a)gmail.com> > Sent: Saturday, November 14, 2020 2:10 AM > To: Tony Liu <tonyliu0592(a)hotmail.com> > Cc: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > Subject: Re: [nova-compute] not reconnect to rabbitmq? > > Hello, > > What we noticed in our case is that nova compute is actually > reconnecting, but cannot communicate with the conductor because the > queue binding is either absent or not working anymore. > > So, first, which version of nova are you running? > Which version of rabbitmq? (some bugs related to shadow bindings are > fixed after 3.7.x / dont remember x) > > Can you check if you have any queue related to your compute? > something like that: > rabbtitmqctl list_queues | grep mycompute > > Also check the bindings, better using the management interface or > rabbitmqadmin: > rabbitmqadmin list bindings | grep mycompute > > What usually fixed our issue by the past was to delete / recreate the > binding (easy to do from the management interface). > > Cheers, > > -- > Arnaud Morin > > On 14.11.20 - 00:34, Tony Liu wrote: > > Hi, > > > > I'm having a deployment with Ussuri on CentOS 8. > > I noticed that, in case the connection from nova-compute to rabbitmq > > is broken, nova-compute doesn't reconnect. > > I checked nova-conductor who seems keeping trying reconnect to > > rabbitmq when connection is broken. But nova-compute doesn't seem > > doing the same. I've seen it a few times, after I fixed rabbitmq and > > bring it back, nova-conductor gets reconnected, but nova-compute > > doesn't, I have to manually restart it. Anyone else has the similar > > experiences? > > Anything I am missing? > > > > > > Thanks! > > Tony > > > >

2 2

Where to send mascot graphic adjustment proposals
by Michael Chapman 15 Nov '20

15 Nov '20

While doing some work on the designate docs I wanted to replace the logo on the diagrams (for example https://docs.openstack.org/designate/latest/contributor/architecture.html) with the mascot graphics available, specifically the horizontal one here: https://object-storage-ca-ymq-1.vexxhost.net/swift/v1/6e4619c416ff4bd19e1c0… The bottom line of the crocodile is just slightly not aligned with the text, which I think could be improved, and perhaps the crocodile could also be increased in size to match that of the text. In addition, the bottom of the mascots page mentions to contact anne(a)openstack.org which is no longer an active address. Are the above proposed changes reasonable, and is there a new contact available for getting mascot graphics modified? I can change it in the designate diagrams myself but they are marked ND so I don't think that's technically allowed. - Michael

1 0

Which deployment method for ceph (rook|ceph-ansible|tripleo)
by Oliver Weinmann 15 Nov '20

15 Nov '20

Hi, I'm still in the process of preparing a OpenStack POC. I'm 100% sure that I want to use CEPH and so I purchased the book Mastering CEPH 2nd edition. First of all, It's a really good book. It basically explains the various methods how ceph can be deployed and also the components that CEPH is build of. So I played around a lot with ceph-ansible and rook in my virtualbox environment. I also started to play with tripleo ceph deployment, although I haven't had the time yet to sucessfully deploy a openstack cluster with CEPH. Now I'm wondering, which of these 3 methods should I use? rook ceph-ansible tripleo I also want to use CEPH for NFS and CIFS (Samba) as we have plenty of VMs running under vSphere that currently consume storage from a ZFS storage via CIFS and NFS. I don't know if rook can be used for this. I have the feeling that it is purely meant to be used for kubernetes? And If I would like to have CIFS and NFS maybe tripleo is not capable of enabling these features in CEPH? So I would be left with ceph-ansible? Any suggestions are very welcome. Best Regards, Oliver

5 7