- openstack-discuss - lists.openstack.org

[neutron] Team meeting - Tuesday 30.06.2020
by Slawek Kaplonski 30 Jun '20

30 Jun '20

Hi, Our today team meeting overlaps with opened event sessions [1] so lets cancel this meeting. See You all on the meeting next week. [1] https://www.openstack.org/events/opendev-2020/opendev-schedule — Slawek Kaplonski Senior software engineer Red Hat

1 0

[neutron] DVR / IPv6 on provider network instead?
by Eric K. Miller 29 Jun '20

29 Jun '20

Hi, Should I assume that the statement: "IPv6 traffic is not distributed, even when DVR is enabled. IPv6 routing does work, but all ingress/egress traffic must traverse through the centralized Controller node. Customers that are extensively using IPv6 routing are advised not to use DVR at this time." is still true in Stein and later (we are running Stein for now, which is why I explicitly mentioned this version)? If so, is there a possibility of using a provider network that is connected to all compute nodes where IPv6 subnets are issued to tenants from a subnet pool, with traffic being routed directly to an external router (not a Neutron router) using Linux Bridge instead of OVS? Yet, still use port security? Just trying to figure out the best way to support IPv6 without forwarding all traffic through a single network node, while using DVR for IPv4. Also, unrelated, but hopefully a quick question... is the "internal" or "external" label on a network just used for filtering lists, such as for "openstack network list --external"? or does it change the behavior of anything? Thanks! Eric

2 2

[neutron] Bug deputy - week of June 22nd
by Slawek Kaplonski 29 Jun '20

29 Jun '20

Hi, Below is my bug deputy summary. It was pretty busy week in Neutron regarding bugs. *High* https://bugs.launchpad.net/neutron/+bug/1885114 - job neutron-tempest-plugin-scenario-openvswitch-iptables_hybrid-ussuri may not be using ussuri Assigned Fixed: https://review.opendev.org/738169 https://bugs.launchpad.net/neutron/+bug/1884906 - L3 agent cannot be manually scheduled Assigned Fixed proposed: https://review.opendev.org/737736 https://bugs.launchpad.net/neutron/+bug/1884808 - [SSL] neutron-rpc-server: RecursionError: maximum recursion depth exceeded while calling a Python object Stable/rocky only, issue caused by old eventlet, Assigned Fix proposed: https://review.opendev.org/#/c/737651/ https://bugs.launchpad.net/neutron/+bug/1884708 - explicity_egress_direction prevents learning of local MACs and causes flooding of ingress packets Unnasigned, It seems that fixes https://bugs.launchpad.net/neutron/+bug/1732067 and https://bugs.launchpad.net/neutron/+bug/1866445 broke other scenarios, *We need someone to take a look into that one* *Medium* https://bugs.launchpad.net/neutron/+bug/1884986 - [OVN] functional test failing TestNBDbMonitorOverTcp test_floatingip_mac_bindings Marked as medium even if it's gate failure because it don't happens often, Assigned, Patch proposed: https://review.opendev.org/738415 https://bugs.launchpad.net/neutron/+bug/1884764 - Some overcloud nodes are missing in the ansible inventory file generated for migration to ML2OVN Assigned, Patches proposed: https://review.opendev.org/#/c/738212/ and https://review.opendev.org/#/c/738192/ https://bugs.launchpad.net/neutron/+bug/1884723 - [OVS] multicast between VM instances on different compute nodes is broken with IGMP snooping enabled Assigned, No patch proposed yet, https://bugs.launchpad.net/neutron/+bug/1884527 - Related dvr routers aren't created on compute nodes Regression introduced with fix for other bug, Assigned, Patch proposed: https://review.opendev.org/737286 *Low* https://bugs.launchpad.net/neutron/+bug/1885547 - [fullstack] OVS interface events isolation error with more than one OVS agent Assigned, Patch https://review.opendev.org/#/c/738446/ *Whishlist* https://bugs.launchpad.net/neutron/+bug/1885261 - Add stateless firewall support to OVS firewall Unassigned, https://bugs.launchpad.net/neutron/+bug/1885262 - Add stateless firewall support to OVN Unassigned, *Opinion* https://bugs.launchpad.net/neutron/+bug/1884504 - nova assume ports with vnic_type=direct-physical use the libvirt interface element when processing network-vif-deleted events *Incomplete* https://bugs.launchpad.net/neutron/+bug/1884532 - inconsistent data in ipamallocations I asked for some more info Would be good if someone who knows IPAM could take a look, *Older bugs which needs some attention* https://bugs.launchpad.net/neutron/+bug/1883321 - Neutron OpenvSwitch DVR - connection problem dvr issue to check by L3 team, https://bugs.launchpad.net/neutron/+bug/1671448 - [RFE] Neutron quota api should be configurable via policy.json — Slawek Kaplonski Senior software engineer Red Hat

1 0

[tc] weekly update
by Mohammed Naser 29 Jun '20

29 Jun '20

Hello 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. # OPEN REVIEW - Add "tc:approved-release" tag to manila https://review.opendev.org/#/c/738105/ - Create starter-kit:kubernetes-in-virt tag https://review.opendev.org/#/c/736369/ - [draft] Add assert:supports-standalone https://review.opendev.org/#/c/722399/ - Add legacy repository validation https://review.opendev.org/#/c/737559/ # PROJECT UPDATES - Add deprecated cycle for deprecated deliverables https://review.opendev.org/#/c/737590/ - No longer track refstack repos in governance https://review.opendev.org/#/c/737962/ - Add Neutron Arista plugin charm to OpenStack charms https://review.opendev.org/#/c/737734/ - Retire puppet-congress https://review.opendev.org/#/c/737145/ # GOAL UPDATES - Update policy in code goal for glance https://review.opendev.org/#/c/738278/ # GENERAL CHANGES - Add storyboard link to migrate-to-focal goal https://review.opendev.org/#/c/738129/ - TC Guide Follow-Ups https://review.opendev.org/#/c/737650/ - Tools: update check-review-status to drop grace period https://review.opendev.org/#/c/736737/ - Remove grace period on resolutions https://review.opendev.org/#/c/735361/ Thanks all. -- Mohammed Naser VEXXHOST, Inc.

1 0

Delegating and routing an IPv6 prefix to an instance
by Christian Rohmann 29 Jun '20

29 Jun '20

Hello OpenStack-Discuss, I have a use case in which an instance / VM is hosting i.e. an OpenVPN gateway which shall be doing some routing / networking by itself. For that purpose one would like to have a global unique IPv6 prefix delegated and routed to it to, which it can in turn give out to its VPN clients. This can and should not be cut out of the on-link network that is provided by Neutron and used to connect the instance itself. If you look at https://community.openvpn.net/openvpn/wiki/IPv6, which has a section *Details: IPv6 routed block* explaining just how that is one intended approach on how to do it. I am now wondering if the existing DHCPv6 prefix delegation implemented in OpenStack is capable of providing a prefix to an instance. Digging a little into what can be found online I ran into this Etherpad doc https://etherpad.opendev.org/p/neutron-kilo-prefix-delegation (linked to on https://wiki.openstack.org/wiki/Neutron/IPv6/PrefixDelegation) There is a list of use-cases, the second one being exactly what I described above: > [...] > > Use cases: > > We need to allocate addresses to ports from an external or > providernetwork, and route them via Neutron routers. > > We wish to allocate whole prefixes to devices (and their specific > neutron port) on demand. A port must be authorised via the API for a > prefix. The prefix could be issued to the device via PD (since the > device has to discover the prefix it's been given). > > [...] But to my understanding the spec used to implement the current IPv6 networking and also prefix delegation mechanism, also mentioned this use case as an "limitation and future enhancement" - see: https://specs.openstack.org/openstack/neutron-specs/specs/liberty/ipv6-pref… Does anyone have any thoughts on this matter of dedicating a prefix and and routingits traffic to a VM, but not just a subnet? Regards Christian

4 8

[all][qa] devstack dropping python 2 support
by Ghanshyam Mann 29 Jun '20

29 Jun '20

Hello Everyone, Devstack has been default to python3 since ussuri release and Victoria cycle is time to drop the support of python2 completely. - https://review.opendev.org/#/c/737455/ Being ussuri as python3-only release and all grenade jobs has been migrated to python3 in ussuri, we are all good here but in case your project is still using the py2 jobs or replying on python2 support in devstack in any extend, do ping us on #openstack-qa channel. We will be keeping USE_PYTHON3 variable support till all consumer remove this, like storlets to adjust the requirement. NOTE: branchless repo keeping common jobs for master and stable branch gate with USE_PYTHON3=False need to keep setting this var for configuring the devstack with right python. For example, tempest-full job definition in tempest master. Such jobs should be run till stable/train only as ussuri onward we tests things on python3 only. -gmann

1 0

Monasca duplicate metrjcs
by junaid soomro 29 Jun '20

29 Jun '20

Hello everyone, I am new to this. my scenario is when i try to get io.read_bytes metric from monasca api it gives me more than one metrics of a singke hostname. Although device is different vda vdb etc. This is fine but when i remove the volume from the vm. Monasca api still sbows its metrics. Ideally it should remove the vdb because i removed it but it does not. why does this happen? Thank you

2 1

RE: [neutron] DVR / IPv6 on provider network instead?
by Eric K. Miller 28 Jun '20

28 Jun '20

> If so, is there a possibility of using a provider network that is connected to all compute nodes where IPv6 subnets are issued to tenants from a subnet pool, with traffic being routed directly to an external router (not a Neutron router) using Linux Bridge instead of OVS? Yet, still use port security? > Just trying to figure out the best way to support IPv6 without forwarding all traffic through a single network node, while using DVR for IPv4. I believe I have a solution, which works for IPv4, where public IP addresses are assigned to a VM's port without the use of floating IPs. I think this approach can work for IPv6, with an upstream DHCPv6 server. My IPv4 approach was to create an internal VLAN on our firewalls, where a public subnet is assigned (statically routed), and a gateway IP is assigned to the firewall. This VLAN is then assigned to a provider network. An OpenStack subnet is created on the provider network for the public subnet range with an allocation range associated with the IPs we want to hand out to VMs, with DHCP enabled. The subnet's gateway property is set to "None", along with DNS servers set, and a "host-route" is added for a default gateway, using our firewall's IP as the gateway. When a server is created on this network, an IP is allocated from the public subnet, the gateway is assigned to our firewall's IP, DNS is set correctly, and security groups work fine on the port. Best of all, traffic is sent/received from the host, not through the network node, so this is a reasonably scalable solution. Eric

1 0

[cyborg][nova] Support flexible use scenario for Mdev(such as vGPU)
by Feng, Shaohe 28 Jun '20

28 Jun '20

Hi all, Currently openstack support vGPU as follow: https://docs.openstack.org/nova/latest/admin/virtual-gpu.html In order to support it, admin should plan ahead and configure the vGPU before deployable as follow: https://docs.openstack.org/nova/latest/configuration/config.html#devices.en… This is very inconvenient for the administrator, this method has a limitation that a same PCI address does not provide two different types. Cyborg as an accelerator management tool is more suitable for mdev device management. One solution as follow： Firstly, we need a vender driver(this can be a plugin), it is used to discovery its special devices and report them to placement for schedule. The difference from the current implementation is that: 1. report the mdev_supported_types as traits to resource provider. How to discover a GPU type: $ ls /sys/class/mdev_bus/*/mdev_supported_types /sys/class/mdev_bus/0000:84:00.0/mdev_supported_types: nvidia-35 nvidia-36 nvidia-37 nvidia-38 nvidia-39 nvidia-40 nvidia-41 nvidia-42 nvidia-43 nvidia-44 nvidia-45 so here we report nvidia-3*, nvidia-4* as traits to resource provider. 2. Report the number of allocable resources instead of vGPU unit numbers to resource provider inventory Example for the NVidia V100 PCIe card (one GPU per board) : Virtual GPU Type Frame Buffer (Gbytes) Maximum vGPUs per GPU Maximum vGPUs per Board V100D-32Q 32 1 1 V100D-16Q 16 2 2 V100D-8Q 8 4 4 V100D-4Q 4 8 8 V100D-2Q 2 16 16 V100D-1Q 1 32 32 so here we report 32G Buffers(an example, maybe other resources) to resource provider inventory 3. driver should also support a function to create certain mdev type, such as (V100D-1Q, V100D-2Q,) Secondly, we need a mdev extend ARQ(it can be a plugin): Here is an example for fpga ext arq: https://review.opendev.org/#/c/681005/26/cyborg/objects/extarq/fpga_ext_arq… The difference is that, we replace the _do_programming to _do_create_mdev For _do_programming, it is used to create a new FPGA function. For _do_create_mdev, it is used to create a new type mdev, it will call the implementation function in vendor driver. At last we need to support a mdev handler for xml generation in nova, we can refer to the cyborg PCI handler in nova So after the above changes： Admin can create different SLA devices profiles such as: {“name”: “Gold_vGPU”, “groups”: [ {“resources:vGPU_BUFFERS”: “16”, “traits: V100D-16Q,”: “required”, }] } And {“name”: “Iron_vGPU”, “groups”: [ {“resources:vGPU_BUFFERS”: “1”, “traits: V100D-1Q,”: “required”, }] } Then a tenant can use Gold_vGPU to create with a VM with V100D-16Q vGPU And another tenant can use Iron_vGPU to create with a VM with V100D-1Q vGPU When ARQ binding during the VM creating, the Cyborg will call the vendor driver to create expected mdev vGPU. And these 2 mdev vGPU can be on same physical GPU card. The mdev extend ARQ and vendor driver can be plugin, they are loose couple with the upstream code. So the downstream can get the upstream code to customize the own mdev extend ARQ and vendor driver. Here vGPU is just an example, it can be other mdev devices. BR Shaohe Feng

3 11

RE: [neutron] DVR / IPv6 on provider network instead?
by Eric K. Miller 28 Jun '20

28 Jun '20

> Also, unrelated, but hopefully a quick question... is the "internal" or "external" label on a network just used for filtering lists, such as for "openstack network list --external"? or does it change the behavior of anything? Regarding my second question, I found some information that indicates --external will share the network with all projects. Whereas the --shared option is only used for sharing a network with a specified list of projects using RBAC rules. It also looks like networks marked as external, not internal, can be specified for the --external-gateway network when creating/updating a router. This has some good info too: https://superuser.openstack.org/articles/tenant-networks-vs-provider-networ… Eric

1 0

[ops][cinder] removal of brocade fczm driver
by Brian Rosmaita 26 Jun '20

26 Jun '20

Brocade no longer supports their cinder Fibre Channel Zone Manager driver [0]. It was marked 'unsupported' in Ussuri and deprecated for removal during the Victoria development cycle. (We just discovered this week that it is in fact unusable in Ussuri as it does not run in Python 3. It does pass all unit tests in Python 3, though.) Its removal will leave cinder with only one FCZM driver, so there has been some interest among Cinder project members in fixing the driver so it will at least run in Python 3.6 and 3.8. However, we don't know at the moment how much effort that will take. Further, without a third-party CI continually testing this driver, we cannot guarantee that once fixed, it will continue to function correctly. (No human can guarantee that any software of sufficient complexity functions correctly, but you know what I mean.) The point of this email is threefold: 1. If nobody is using the Brocade FCZM driver, then maybe we should just go ahead and remove it. So if you are using it, please let us know. 2. According to [0], for OpenStack users after Train, "Brocade encourages customers to perform SAN Zoning operations using other available tools or APIs." So if you are a Brocade user who has successfully configured another solution to replace the Brocade FCZM, the Cinder team (and the wider OpenStack community) would be interested in hearing about it. 3. If you are a consumer of the current cinder Brocade FCZM and are interested in its continued existence, the Cinder team would be interested in discussing with you how we could set up a third-party CI for it. As I said earlier, without the third-party CI, we really have no idea whether this thing works or not. I've already posted a patch to remove the Brocade FCZM driver [1]. (Just so you know we're serious about this.) At our R-16 mid-cycle meeting earlier this week, the Cinder team agreed to make a final decision at our next mid-cycle at week R-9. (Yes, we have two mid-cycles and neither is at the middle of the cycle -- we're already meeting in virtual space, so we also meet in virtual time.) So please communicate your thoughts to us before week R-9 by replying to this email on the mailing list. cheers, brian [0] https://docs.broadcom.com/doc/12397527 [1] https://review.opendev.org/#/c/738148/

1 0

[all][interop] Tasks completed and help for Interop Survey questions
by prakash RAMCHANDRAN 26 Jun '20

26 Jun '20

Hi all, It was bit odd to use meetpad instead of irc today, still need to understand how to share multiple screens or desktop on the meetpad.Any help is welcome as hat the procedure will be. Plus apology to Mark for late update on irc to meetpad. Weekly we will be using - (https://etherpad.opendev.org/p/interop) Interop Working Group - Weekly Friday 10-11 AM or UTC 17-18 Lnink: https://meetpad.opendev.org/Interop-WG-weekly-meeting But communication was really better than irc with chat plus verbal+video talk. How to add ircbot to meetpad any suggestions? Following is action Items to follow up. AI-01- GM to update/close? launchpad item - https://blueprints.launchpad.net/refstack/+spec/interop-2020.06With following two references to storyboard for all API guidelines for 2020.06.json.https://storyboard.openstack.org/#!/story/2007509https://story… AI-02 - Survey Questions please add what you seek for your projects? - https://storyboard.openstack.org/#!/story/2007511 6/26/2020 - AT todays Interop call it was decided to add following questions and is being circulated for updates via openstack-discuss list.level 1 Q &A1.Do you use OpenStack Marketplace data for your decision on use of OpenStack Cloud?2.Do you look at Interoperability reports available to you on different offerings in Marketplace portal?3. If you offer OpenStack Cloud do you use the OpenStack logo programs.?4. If you are using Object Storage for your cloud do you use Swift? What would you like to see improve in current Marketplace Logo Program?[1] Do you want to add Interop for kubernetes API conformance for OpenStack and Open Infrastructure Projects?[2] Do you want to add Interop for bare metal service?[3][4] (Add above your suggestions)level 2 Q&A1. Do you use data on add-on programs in the OpenStack Marketplace?1.1 If yes which ones? AI-03 - (for Core + Add-ons for OpenStack Integrated Projects) - Can you volunteer to add tag assert:supports-api-interoperability to your projects?Any comments on what Projects need to do to claim this based on 2020.06 - interop - https://opendev.org/osf/interop/src/branch/master/2020.06.json Can someone take a crack at documenting how to for one project like nova compute api does now? AI-04 - Seeking volunteers to maintain - Refstack - https://opendev.org/osf/refstack AI-05 - Can someone volunteer to present at next Interop meeting Friday 3rd at 17 UTC (10 AM PDT) - https://github.com/cncf/k8s-conformance Any Other suggestions for future events? ThanksInterop team: Prakash/Mark/Ghanshyam/Arkady

1 0

[openstack-discuss][airship-discuss][openstack-helm] Ceph Bluestore
by Roman Gorshunov 26 Jun '20

26 Jun '20

Hello Dominik, Thanks for the question. Please, let me redirect it to the OpenStack-Helm project mailing list, as Airship only consumes Ceph charts from openstack-helm-infra repository (previously from openstack-helm repo). Technically I see that ceph-osd in OpenStack-Helm supports Bluestore [0], so if you would want to deploy with Bluestore, you would need to change Armada documents (e.g. [1][2]) to use Bluestore. [0] https://opendev.org/openstack/openstack-helm-infra/src/branch/master/ceph-o… <https://opendev.org/openstack/openstack-helm-infra/src/branch/master/ceph-o…> [1] https://opendev.org/airship/treasuremap/src/branch/master/site/seaworthy/so… <https://opendev.org/airship/treasuremap/src/branch/master/site/seaworthy/so…> [2] https://opendev.org/airship/treasuremap/src/branch/master/site/seaworthy/so… <https://opendev.org/airship/treasuremap/src/branch/master/site/seaworthy/so…> Best regards, Roman Gorshunov > On 25 Jun 2020, at 17:36, Dominik Bender <db(a)db-itsolutions.com> wrote: > > Hello everyone, > > I need some help with Ceph configuration. What changes need to be made in the charts to use bluestore? > In general I would still be interested in why bluestore is not yet standard in treasuremap? > > Thanks in advance > > -- > Dominik Bender > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss(a)lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss

1 0

OpenStack on CentOS 8 VM using packstack
by Pradeep Antil 26 Jun '20

26 Jun '20

Hi Techies, I am trying to deploy the latest Openstack "ussuri" on CentOS 8 VM using packstack. I have successfully installed it but the issue is that i want to i want to add my interface "enp0s3" to ovs bridge br-ex. On CentOS 7 we can do this via ifcfg-* files using network-scripts. But i am not sure how this can be done on CentOS 8 VM as in this release network is controlled via network manager. On br-ex i will attach an external provider network or a flat network. [image: image.png] I have referred the below steps for the deployment. dnf update -y dnf config-manager --enable PowerTools dnf install -y centos-release-openstack-ussuri dnf update -y dnf install -y openstack-packstack reboot packstack --gen-answer-file=/root/answer.txt Edit answer file CONFIG_NEUTRON_ML2_TYPE_DRIVERS=vxlan,flat CONFIG_NEUTRON_ML2_TENANT_NETWORK_TYPES=vxlan CONFIG_PROVISION_DEMO=n CONFIG_KEYSTONE_ADMIN_PW=P@ssw0rd packstack --answer-file=/root/answer.txt Following is the output of ovs command and interfaces on my centos 8 system [image: image.png] -- Best Regards Pradeep Kumar

2 1

[tc][networking-l2gw] Finish the retirement for networking-l2gw and networking-l2gw-tempest-plugin
by Ghanshyam Mann 26 Jun '20

26 Jun '20

Hello Everyone, networking-l2gw and networking-l2gw-tempest-plugin projects were retired in Ocata[1] but their retirement was not completed. I have started the retirement completion as discussed in TC and neutron team. - https://review.opendev.org/#/q/topic:complete-retirement-networking-l2gw+(s… Please let me know any injection to that. Their development can be continued under opendev as mentioned in this doc - https://governance.openstack.org/tc/reference/dropping-projects.html#contin… [1] https://review.opendev.org/#/c/392010/2 -gmann

5 9

[blazar] Broken CI
by Pierre Riteau 26 Jun '20

26 Jun '20

Hello, The blazar devstack CI jobs are currently failing due to issues related to uwsgi. logs/screen-blazar-a.txt shows: Jun 25 09:26:47.037179 ubuntu-bionic-limestone-regionone-0017387278 systemd[1]: Starting Devstack devstack(a)blazar-a.service... Jun 25 09:26:47.038997 ubuntu-bionic-limestone-regionone-0017387278 systemd[18254]: devstack(a)blazar-a.service: Failed to execute command: No such file or directory Jun 25 09:26:47.039047 ubuntu-bionic-limestone-regionone-0017387278 systemd[18254]: devstack(a)blazar-a.service: Failed at step EXEC spawning /usr/local/bin/uwsgi: No such file or directory Jun 25 09:26:47.039445 ubuntu-bionic-limestone-regionone-0017387278 systemd[1]: devstack(a)blazar-a.service: Main process exited, code=exited, status=203/EXEC Jun 25 09:26:47.039454 ubuntu-bionic-limestone-regionone-0017387278 systemd[1]: devstack(a)blazar-a.service: Failed with result 'exit-code'. Jun 25 09:26:47.039734 ubuntu-bionic-limestone-regionone-0017387278 systemd[1]: Failed to start Devstack devstack(a)blazar-a.service. I think it's our devstack plugin that needs fixing. In the meantime no need to recheck patches, they will keep failing until resolved. Pierre Riteau (priteau)

2 2

[all][tc][goals] Migrate CI/CD jobs to new Ubuntu LTS Focal: Week R-16 Update
by Ghanshyam Mann 25 Jun '20

25 Jun '20

Hello Everyone, Please find the updates on Ubuntu Focal migration community goal. Tracking: https://storyboard.openstack.org/#!/story/2007865 Progress: ======= * devstack and tempest base patches are ready for testing on projects side. Thanks frickler for doing the base work. * neutron, nova project started the testing. Bugs: ==== 1. There is open bug for nova/cinder where three tempest tests are failing for volume detach operation. There is no clear root cause found yet -https://bugs.launchpad.net/cinder/+bug/1882521 We have skipped the tests in tempest base patch to proceed with the other projects testing but this is blocking things for the migration. 2. We encountered the nodeset name conflict with x/tobiko, i have proposed it to consume it form devstack -https://review.opendev.org/#/c/738128/ What work to be done on project side: ============================= This goal is more of testing the jobs on focal and fixing bugs if any otherwise migrate jobs by switching the nodeset to focal node sets defined in devstack. 1. Start a patch in your repo by making depends-on on either of below: devstack base patch if you are using only devstack base jobs not tempest: https://review.opendev.org/#/c/731207/ OR tempest base patch if you are using the tempest base job (like devstack-tempest): https://review.opendev.org/#/c/734700/ Example: https://review.opendev.org/#/c/738126/ 2. If none of your project jobs override the nodeset then above patch will be testing patch(do not merge) otherwise change the nodeset to focal. Example: https://review.opendev.org/#/c/737370/ 3. If the jobs are defined in branchless repo like tempest plugins then you need to override the branches variant to adjust the nodeset on jobs so that only Victoria onwards those jobs run on focal not old stable. Once we finish the testing on projects side and no failure then we will merge the devstack and tempest base patches. Important things to note: =================== * Do not forgot to add the story and task link to your patch so that we can track it smoothly. * Use gerrit topic 'migrate-to-focal' * Do not backport any of the patch. References: ========= Goal doc: https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-j… Storyboard tracking: https://storyboard.openstack.org/#!/story/2007865 -gmann

1 0

[tc] Monthly meeting
by Mohammed Naser 25 Jun '20

25 Jun '20

Hi everyone, Our monthly TC meeting is scheduled for next Thursday, July 2nd, at 1400 UTC. If you would like to add topics for discussion, please go to https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and fill out your suggestions by Wednesday, July 1st, at 1900 UTC. Thank you, Regards, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[cinder] priorities for the next 2 weeks
by Brian Rosmaita 25 Jun '20

25 Jun '20

As mentioned at yesterday's virtual mid-cycle, our top priority right now is to get the milestone-1 items reviewed and re-reviewed. And the specs freeze is next week ... so our *two* top priorities are to get the milestone-1 items reviewed and also review specs. Here is a handy list: volume-local-cache - https://review.opendev.org/#/c/663549/ os-brick - https://review.opendev.org/#/c/700799/ cinder - https://review.opendev.org/#/c/715762/ tempest test case NFS encrypted volume support - https://review.opendev.org/#/c/597148/ brick gpg encryption support - https://review.opendev.org/#/c/709432/ new backend driver - Hitachi - https://review.opendev.org/#/c/712832/ specs: https://review.opendev.org/#/q/project:openstack/cinder-specs+status:open

1 0

[cinder] victoria mid-cycle part 1 summary available
by Brian Rosmaita 25 Jun '20

25 Jun '20

In case you missed yesterday's R-16 virtual mid-cycle session, I've posted a summary: https://wiki.openstack.org/wiki/CinderVictoriaMidCycleSummary It includes a link to the recording (in case you want to see what you missed or if you want to re-live the excitement). Part 2 of the mid-cycle will be held the week of R-9. cheers, brian

1 0

OSF Community Meeting 1 Recording & Slides
by Allison Price 25 Jun '20

25 Jun '20

Hi everyone, Thank you for joining today’s OSF Community Meeting. If you missed the meeting, you have a few options on getting updated on what was covered. You can listen to the recording [1] and check out the slides [2] that were presented this morning. I have also attached a PDF of the slides if that’s easier to access. There will be a second OSF Community Meeting covering the same material tomorrow, Friday, June 26 at 0200 UTC (today, June 25 at 7pm PT). You can find the lineup of speakers and dial-in information here [3]. Stay tuned for the next OSF Community Meeting in July that will cover the OpenStack 10th birthday, and the next all project, quarterly update that will be held in September. Cheers, Allison [1] https://zoom.us/rec/share/vJF_FqPgxGJJQ9bntR7vaqM7N7i_X6a81yQa8vtcxU06amK9p… <https://zoom.us/rec/share/vJF_FqPgxGJJQ9bntR7vaqM7N7i_X6a81yQa8vtcxU06amK9p…> Password: 7W!T*i74 [2] https://docs.google.com/presentation/d/16V82OIYfthb3fFlVoes9jZGKMgDIJZ55F8f… [3] https://etherpad.opendev.org/p/OSF_Community_Meeting_Q2 <https://etherpad.opendev.org/p/OSF_Community_Meeting_Q2> Allison Price OpenStack Foundation allison(a)openstack.org

1 0

Python OpenStack SDK does not return Hypervisor hostname
by Anil Jangam 25 Jun '20

25 Jun '20

I have written a client code as follows. # Get Hypervisor details try: print(f"+----------------------------------------------------------+") print(f"| Hypervisor details |") print(f"+----------------------------------------------------------+") for hypervisor in conn.list_hypervisors(): print(f"Hypervisor is: {hypervisor}") print(f"Hypervisor status: {hypervisor.status}") print(f"Hypervisor vcpus: {hypervisor.vcpus_used}") print(f"Hypervisor type: {hypervisor.hypervisor_type}") print(f"Hypervisor id: {hypervisor.id}") print(f"Hypervisor state: {hypervisor.state}") print(f"Hypervisor host IP: {hypervisor.host_ip}") print(f"Hypervisor running VMs: {hypervisor.running_vms}") print(f"Hypervisor running VMs: {hypervisor.vcpus}") print(f"Hypervisor hostname: {hypervisor.hypervisor_hostname}") print(f"") except EndpointNotFound as exp: print("Error: {}".format(exp)) print(f"") When I print the 'hypervisor' object itself, most of the values are printed as shown below, however when I try to access 'hypervisor.hypervisor_hostname', it throws an exception. +----------------------------------------------------------+ | Hypervisor details | +----------------------------------------------------------+ Hypervisor is: openstack.compute.v2.hypervisor.Hypervisor(status=enabled, service={'host': 'cl3-Compute3', 'disabled_reason': None, 'id': '34db399d-25b9-4004-98b9-2d8bbce7b228'}, vcpus_used=0, hypervisor_type=QEMU, local_gb_used=0, vcpus=52, hypervisor_hostname=cl3-Compute3, memory_mb_used=25600, memory_mb=262032, current_workload=0, state=up, host_ip=192.168.10.116, cpu_info={'arch': 'x86_64', 'model': 'Broadwell', 'vendor': 'Intel', 'features': ['pge', 'avx', 'xsaveopt', 'clflush', 'sep', 'rtm', 'tsc_adjust', 'tsc-deadline', 'dtes64', 'invpcid', 'tsc', 'fsgsbase', 'xsave', 'smap', 'vmx', 'erms', 'xtpr', 'cmov', 'hle', 'smep', 'pcid', 'est', 'pat', 'monitor', 'smx', 'pbe', 'lm', 'msr', 'adx', '3dnowprefetch', 'nx', 'fxsr', 'syscall', 'tm', 'sse4.1', 'pae', 'sse4.2', 'pclmuldq', 'acpi', 'fma', 'vme', 'popcnt', 'mmx', 'osxsave', 'cx8', 'mce', 'de', 'rdtscp', 'ht', 'dca', 'lahf_lm', 'abm', 'rdseed', 'pdcm', 'mca', 'pdpe1gb', 'apic', 'sse', 'f16c', 'pse', 'ds', 'invtsc', 'pni', 'tm2', 'avx2', 'aes', 'sse2', 'ss', 'ds_cpl', 'arat', 'bmi1', 'bmi2', 'ssse3', 'fpu', 'cx16', 'pse36', 'mtrr', 'movbe', 'rdrand', 'x2apic'], 'topology': {'cores': 14, 'cells': 2, 'threads': 2, 'sockets': 1}}, running_vms=0, free_disk_gb=852, hypervisor_version=2012000, disk_available_least=849, local_gb=852, free_ram_mb=236432, id=1130407d-5afd-41f9-bc0c-2d7babda3ce7, location=Munch({'cloud': 'defaults', 'region_name': 'RegionOne', 'zone': None, 'project': Munch({'id': '6d4f1b107bbf4b94832f7ef72df61ef2', 'name': '5g', 'domain_id': None, 'domain_name': 'default'})})) Hypervisor status: enabled Hypervisor vcpus: 0 Hypervisor type: QEMU Hypervisor id: 1130407d-5afd-41f9-bc0c-2d7babda3ce7 Hypervisor state: up Hypervisor host IP: 192.168.10.116 Hypervisor running VMs: 0 Hypervisor running VMs: 52 Traceback (most recent call last): File "/Users/workspace/testprogs/python/opsviz/ops_worker.py", line 321, in <module> main() File "/Users/workspace/testprogs/python/opsviz/ops_worker.py", line 317, in main print_servers() File "/Users/workspace/testprogs/python/opsviz/ops_worker.py", line 115, in print_servers print(f"Hypervisor hostname: {hypervisor.hypervisor_hostname}") File "/Users/inventory/lib/python3.7/site-packages/openstack/resource.py", line 588, in __getattribute__ raise e File "/Users/inventory/lib/python3.7/site-packages/openstack/resource.py", line 582, in __getattribute__ return object.__getattribute__(self, name) AttributeError: 'Hypervisor' object has no attribute 'hypervisor_hostname' Is there anything wrong with the use of the API? How do I get the hypervisor hostname in my application code? Thank you.

3 6

[kolla] Introducing Kolla Kalls
by Radosław Piliszek 25 Jun '20

25 Jun '20

Hi fellow OpenStackers! During yesterday's Kolla meeting [1] I have proposed to have more focused, voice-based sessions related to Kolla development, similarly to what we have for operators with Kolla Klub [1]. The immediate response was rather positive and the name Kolla Kalls has been coined. Since Kolla Klub is running every other Thursday at 15:00 UTC, we decided to use the alternate weeks slot for Kolla Kalls but this can change if need arises. Kolla Kalls got their wiki page already [3] where the agenda will be posted. The first Kall is scheduled on July 9, 15:00 UTC (i.e. in two weeks time from today). The agenda for the first Kall is mostly about trying this meeting approach out. The hottest topic from our PTG is the quality/completeness of our documentation so it is a good topic for our first few sessions. It is likely going to involve CI testing discussions as well. The platform has not been decided on yet. We plan to give OpenDev's Meetpad a test ride and fall back to Google Meet which we practiced well with Kolla Klub and similar events - if Jitsu breaks for us. I learnt Meetpad does not (yet) support recording but we plan to document the meeting in a text form anyhow so we should be fine. Everyone interested in developing Kolla projects, that is Kolla, Kolla-Ansible and/or Kayobe is welcome to join the Kalls. The Kalls will be development-oriented and focus on topics such as implementation discussion, change planning, release planning and housekeeping. [1] http://eavesdrop.openstack.org/meetings/kolla/2020/kolla.2020-06-24-15.01.h… [2] https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_… [3] https://wiki.openstack.org/wiki/Meetings/Kolla/Kall -yoctozepto

1 0

[neutron] Drivers meeting agenda - 26.06.2020
by Slawek Kaplonski 25 Jun '20

25 Jun '20

Hi Neutron drivers, Below is agenda for tomorrow’s meeting. We have 2 RFE to discuss: https://bugs.launchpad.net/neutron/+bug/1882804 - RFE: allow replacing the QoS policy of bound port This one is follow-up after virtual PTG and discussions with Nova team, https://bugs.launchpad.net/neutron/+bug/1828494 - L3 agent’s capacity lets discuss again this proposal with “routers_max” parameter instead of bandwidth (See last comment there) There is also proposed spec (https://review.opendev.org/#/c/729532/) for: https://bugs.launchpad.net/neutron/+bug/1880532 - [RFE]L3 Router should support ECMP Please review it if You can and we will get back to this RFE next week. Ok, that’s all for today. See You all tomorrow on the meeting. — Slawek Kaplonski Senior software engineer Red Hat

1 0

[all][tc][stable][qa] Grenade testing for Extended Maintenance stable
by Ghanshyam Mann 25 Jun '20

25 Jun '20

Hello Everyone, As you know devstack (so does grenade) got broken due to uwsgi new release, the master branch is fixed and stable branches are in progress[1]. But It is hard to maintain or fix the EM stable for those issues. Especially the greande job which depends on the source branch (previous branch of one where the job is running). For example, for stein grenade job, we need to keep rocky branch working and fix if failure. Till now, we have not removed the grenade testing from any of the EM stable branches because they were running fine till now but with uwsgi issues, those are failing and need more work to fix. This triggers the discussion of grenade testing on EM stable branches. Usual policy for grenade testing is to keep the job running from the 'oldest supported stable +1' branch. For example, if stein is the oldest supported stable (in the old stable definition) then run grenade from train onwards. But with the Extended Maintainance model, defining 'oldest supported stable' is not clear whether it is the oldest non-EM(stein) or oldest EM stable(ocata). To make it clear, we discussed this in the QA channel and come up with the below proposal. * 'oldest' is the oldest non-EM. In current time, it is stein. * With the above 'oldest' definition, we will: ** Make grenade jobs as n-v on all EM stable branches (which is till stable/rocky as of today) + on stable/stein also because that is 'oldest' as of today. ** Keep supporting and running grenade job on 'oldest+1' which is stable/train onwards as of today. NOTE: we will make n-v when they start failing and anyone can volunteer to fix them and change back to voting. elod expressed interest to work on current failure. If no objection to the above proposal, I will document it on the grenade documents to follow it whenever we see EM failing and need more work. In Tempest, we already have the EM stable testing policy documented which is to support those till they run fine[2]. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015496.html [2] https://docs.openstack.org/tempest/latest/stable_branch_support_policy.html [3] http://eavesdrop.openstack.org/irclogs/%23openstack-qa/%23openstack-qa.2020… -gmann

5 5

[tripleo] Proposing Francesco Pantano as core on TripleO/Ceph
by Giulio Fidente 25 Jun '20

25 Jun '20

Hi all, Francesco (fmount on freenode) started working on the Ceph integration bits in TripleO more than a year ago now [1], contributing over time to all components, heat templates, validations, puppet and ansible repos. He understood the tight relationship in between TripleO and ceph-ansible and contributed directly to ceph-ansible as well, when necessary [2]. I think he'd be a great addition to the TripleO cores group and I hope for him to work more in the future even outside the Ceph integration efforts. I would like to propose Francesco core for the TripleO group on the Ceph bits. Please vote here or leave any feedback for him. Thanks, Giulio 1. https://review.opendev.org/#/q/owner:fpantano%2540redhat.com+status:merged 2. https://github.com/ceph/ceph-ansible/commits?author=fmount -- Giulio Fidente GPG KEY: 08D733BA

9 8

[neutron][tc][solum] Properly retire networking-onos, solum-infra-guestagent, openstack-ux
by Andreas Jaeger 25 Jun '20

25 Jun '20

These three repositories have been retired by their projects some time ago [1]: - openstack-ux: 2017-02-24 - networking-onos: 2016-11-01 - solum-infra-guestagent: 2016-11-24 They have no contribution and are still setup in Zuul, I'll retire them now following our retirement process [2] and thus remove them from Zuul. See [3] for changes, Andreas Links: [1] https://opendev.org/openstack/governance/src/branch/master/reference/legacy… [2] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-re… [3] https://review.opendev.org/#/q/topic:finish-retire -- Andreas Jaeger aj(a)suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB

1 0

[neutron][dynamic-routing] Adding Jens Harbott and Tobias Urdin to neutron-dynamic-routing core team
by Slawek Kaplonski 25 Jun '20

25 Jun '20

Hi, Recently I asked for new maintainers for the neutron-dynamic-routing project. Tobias Urdin and Jens Harbott stepped in for that. So now I added them both to be core reviewers in the neutron-dynamic-routing project also. -- Slawek Kaplonski Senior software engineer Red Hat

1 0

[cinder] volume list query ("managing" statuses) spec
by Brian Rosmaita 24 Jun '20

24 Jun '20

The spec is https://review.opendev.org/#/c/726070/ I took the action item at today's virtual mid-cycle meeting to summarize the discussion on the review so that the spec can be revised. While doing that, I looked through the code carefully, and I think that the spec is actually on the right track, though there seem to be several bugs associated with this issue. In any case, I just left an enormous comment on the review. I need other reviewers to read through and comment/respond so that haixin and zhangbailin can get some consensus on how to revise the spec. thanks, brian

1 0

[cyborg] Cyborg IRC meeting cancelled this week
by yumeng bao 24 Jun '20

24 Jun '20

Hi all, Cyborg weekly meeting will be cancelled this week since most of the team members will be having the Dragon Boat Festival on Thursday. We will see you next week! Regards， Yumeng

1 0

[kolla] Victoria priorities
by Mark Goddard 24 Jun '20

24 Jun '20

Hi, Hot on the heels of the Ussuri release, we have the results of the votes for Victoria priorities. We voted in etherpad [1], and the results have been added to the whiteboard (L181). Feel free to add your name as an owner on the whiteboard if you would like to be involved. [1] https://etherpad.opendev.org/p/kolla-victoria-priorities Thanks, Mark = Kolla = Infra images (8 votes) https://blueprints.launchpad.net/kolla/+spec/infra-images Owners: Image tiering (6 votes) Avoid breakage of non-core images blocking publishing of all others Owners: Ubuntu focal 20.04 (6 votes) (likely must-have anyway unless we are dropping ubuntu) Owners: Stable branch life-cycle (6 votes) Use stable/<release> rather than versions Owners: Integrate support for pull-retag-push (4 votes) https://storyboard.openstack.org/#!/story/2007731 (original kayobe story) Owners: Kolla depends-on upstream projects to behave as it should (2 votes) Owners: Build, test, promote CI pipeline (2 votes) Build images, test them, promote for general availability Owners: = Kolla Ansible = Let's Encrypt integration - container running certbot, triggers certificate distribution (10 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/letsencrypt-https this would be useful to have for tls everywhere deployment too. Owners: headphoneJames Document, automate and test Octavia resource registration (10 votes) Owners: Document, automate and test Designate resource registration (8 votes) Also designate sink set up for instance dns Owners: yoctozepto Documentation review & refresh (8 votes) Owners: everyone Federated keystone (7 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/add-openid-support Owners: Container health checks (7 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check mix with sanity checks? https://blueprints.launchpad.net/kolla-ansible/+spec/sanity-check-container Owners: mnasiadka Fix the "Ansible may run more handlers than originally planned" with all the extras around config (6 votes) https://bugs.launchpad.net/kolla-ansible/+bug/1863510 Owners: Improve test coverage (the never-ending story) (6 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/kolla-deployment-scena… Multiple regions Owners: Performance & scalability improvements (5 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/performance-improvemen… Owners: mgoddard Implement TLS Backend for all core services with externally exposed API (nova for example) (4 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/add-ssl-internal-netwo… Owners: headphoneJames TLS in other services: (4 votes) MariaDB https://blueprints.launchpad.net/kolla-ansible/+spec/mariadb-ssl-support RabbitMQ https://blueprints.launchpad.net/kolla-ansible/+spec/message-queue-ssl-supp… Memcached https://blueprints.launchpad.net/kolla-ansible/+spec/memcached-ssl-support Owners: Upgrade checkers (4 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/upgrade-checkers Owners: Node removal (decommission) (4 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/remove-node Mark has already done related work for CentOS 8 migration do more than destroy - clean them up! from databases etc. aligns with day-2 ops Owners: Support for reload (e.g. for TLS), also graceful shutdown (4 votes) Owners: Mechanism for distributing certificates to services after deployment (2 votes) Owners: Day 2 ops tools (restart containers, upgrade Docker, prune DBs…) (2 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/docker-upgrade-reconfi… Owners: Capture docker logs (2 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/capture-docker-logs Owners: Nova cells v2 - shared cell controllers, multiple DBs and MQs (0 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/nova-cells-shared-cont… https://blueprints.launchpad.net/kolla-ansible/+spec/cellsv2-rabbitmq-suppo… Owners: = Kayobe = Document configuration walk through (7 votes) https://storyboard.openstack.org/#!/story/2004360 Owners: Support multiple environments from a single kayobe configuration (3 votes) https://storyboard.openstack.org/#!/story/2002009 Owners: priteau Support for multiple deploy image types on overcloud nodes (2 votes) https://storyboard.openstack.org/#!/story/2002098 Owners: Next generation discovery & network configuration (2 votes) https://storyboard.openstack.org/#!/story/2004295 https://github.com/markgoddard/kayobe-switch-config-poc Owners: Replace bifrost with kolla-ansible for seed services (2 votes) https://storyboard.openstack.org/#!/story/2004293 Owners: Easier customization of Kayobe commands (0 votes) https://storyboard.openstack.org/#!/story/2001663 Owners: jovial Command plan that tells you which playbooks will run / Fix dry run (0 votes) Pierre pointed out that -lt provides similar functionality, e.g kayobe overcloud host configure -lt Owners: Inventory exporter (0 votes) Owners:

1 0

[kolla] Ussuri releases available
by Mark Goddard 24 Jun '20

24 Jun '20

Hi, I'm pleased to announce the availability of the first Ussuri releases for all Kolla deliverables: * kolla 10.0.0 (https://docs.openstack.org/releasenotes/kolla/ussuri.html#relnotes-10-0-0-s…) * kolla-ansible 10.0.0 (https://docs.openstack.org/releasenotes/kolla-ansible/ussuri.html#relnotes-…) * kolla-cli 10.0.0 * kayobe 8.0.0 (https://docs.openstack.org/releasenotes/kayobe/ussuri.html#relnotes-8-0-0-s…) Thanks to everyone who contributed to these releases. Some things to note: * Support for CentOS 7 has been dropped. Train provides a migration path from CentOS 7 to 8 * Ceph deployment support and images have been dropped. External Ceph cluster integration should be used instead. * Support for Python 2 has been dropped. * This is the last planned release of kolla-cli. As usual with deprecations, please get in touch if you are able to help support this project. And now onto Victoria! Thanks, Mark

1 0

[largescale-sig] Next meeting: June 24, 8utc
by Thierry Carrez 24 Jun '20

24 Jun '20

Hi everyone, The Large Scale SIG will have a meeting this week on Wednesday, June 24 at 8 UTC[1] in the #openstack-meeting-3 channel on IRC: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200624T08 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting A reminder of the TODOs we had from last meeting, in case you have time to make progress on them: - all to describe briefly how you solved metrics/billing in your deployment on https://etherpad.opendev.org/p/large-scale-sig-documentation - amorin to add some meat to the wiki page before we push the Nova doc patch further - ttx to solve merge conflict and push initial oslo.metrics code in from https://review.opendev.org/#/c/730753/ Talk to you all on Wednesday, -- Thierry Carrez

1 1

[Octavia] multi-arch Amphora
by Tony Breeds 23 Jun '20

23 Jun '20

Hello Octavia team! I have a somewhat obscure question for y'all about the "best way" to run an Amphora in an multi-arch OpenStack. I'm going to start with some level-setting assumptions, the describe my understanding so that if I'm wrong we can correct that before we get to the crux of my question(s) Assumptions ----------- - The build of all objects, amphora guest images etc etc is fine - The deployment of OpenStack is reasonably simple and defined. - An OpenStack that runs entirely on on CPU Architecture (aarch64, ppc64le, x86_64, etc) "works" Bottom line we don't need to care about how the 'bits' are built or installed just that they are :) My Understanding ---------------- When asked to create a loadbalancer. Octavia will spawn an instance (via Nova) running the image tagged in glance with $amp_image_tag[1,2]. This instances shoudl be scheduled closer to the ingress/egress of the network then the workload it's balancing. All communication between the Amphora and Octavia API is via REST (as opposed to RPC) and therefore we won't have any 'endianness/binary bugs' [3] The question(s) --------------- We have an OpenStack that has compute nodes running mixed architectures (aarch64, ppc64le, x86_64, etc) we can ensure that images run on the correct system (either with hw_architecture or aggregates). To make that work today we load an appropriately tagged image into glance and then the amphora just runs on type of system and it's all pretty easy. Can, should, we do better? - Does OVN/DVR alter the perfomance such that there *is* merit in scheduling the amphora closer to the workloads - Should we support multiple Amphora (one per architecture)? - If so should this be exposed to the user? openstack loadbalancer create \ --name lb1 --vip-subnet-id public-subnet \ --run-on aarch64 Yours Tony. [1] https://docs.openstack.org/octavia/latest/configuration/configref.html#cont… [2] There should be only one image tagged as such: https://opendev.org/openstack/octavia/src/branch/master/octavia/compute/dri… [3] https://www.youtube.com/watch?v=oBSuXP-1Tc0

2 1

[tc][uc] Status update: Uniting TC and UC
by Thierry Carrez 23 Jun '20

23 Jun '20

Hi everyone, A quick status update on that effort. The TC just merged a change[1] that will result in the TC and UC acting as a single body, starting on August 1st, 2020. The date was chosen so that the remaining UC members (Mohamed Elsakhawy and Jaesuk Anh) can finish their term. After that date, the UC mission will be taken over by the elected TC members, and from there on we'll have a single elected body, including developers, operators and end users of the OpenStack software, and inclusive of all types of contributions to the project. In August I'll work to merge the content on the UC governance site and the TC governance site. This will include adding a new file on openstack/governance to add and track voters corresponding to the AUC criteria. Those will be added to the electorate in time for the next round of elections in September. This simplification will make the OpenStack community more easily navigable, and further remove barriers between contributors with an operations background and contributors with a development background. For more information on the motivations behind that change, please read the original thread[2] proposing it. I'd like to personally thank the User Committee members for their support in that transition, and for all the work they accomplished for OpenStack in the past. [1] https://review.opendev.org/#/c/734074/ [3] http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012806… -- Thierry Carrez (ttx)

2 1

[all][qa][gate] Gate Status: week 20-25
by Ghanshyam Mann 23 Jun '20

23 Jun '20

Hello Everyone, I am highlighting the few of the gate issues we fixed or in-progress last week 1. uwsgi bug: https://bugs.launchpad.net/devstack/+bug/1883468: Fixed till stable/stein Updates - http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015558.html 2. neutron-greande-multinode failure: In-progress greande base zuulv3 jobs are backported till train[1] which will be required to backport neutron-greande-multinode zuulv3 version. Ussuri backports are not yet merged which need more fixes on neutron CI[2]. Please wait for that backport to merge before recheck. 3. 'tox not found': https://bugs.launchpad.net/devstack/+bug/1884256: Fixed for known failure. This also started happening in many jobs. neutron and python-temepstconf jobs. devstack base integration jobs do not install tox (devstack functional base jobs does). If your job is derived from devstack integration base jobs and run test via tox env then you may need this to fix. NOTE: tempest jobs are all good as devstack's install_tempest() method do install tox for tempest tests run. Fix- https://review.opendev.org/#/c/737016/1 4. 'virtualenv not found': If this is happening on zuulv3 jobs then please refer the Ian's email[3]. if that is happening on legacy jobs then the recommendation is to migrate the jobs to zuulv3 like done for neutron-greande-multinode job. We are facing this issue on nova grenade as well as nova live migration jobs(legacy multinode jobs), there are multiple updates happened on devstack, grenade and image side, so I have reached the nova stable branch patches let's see what all still failing. 5. tempest sanity job failure for 'virualenv not found': Fixed The fix is merged and you can recheck your Tempest patches. Fixed: https://review.opendev.org/#/c/736952/5 6. To fixes all the all failure happening on EM stables, first step we are trying is to move the process-stackviz role from tempest to devstack so that we can apply the fixes for those stable in that role. If it stays in Tempest then fixes cannot be applied to old Tempest used for EM stable testing. More details in these patches[4] [1] https://review.opendev.org/#/q/topic:fix-grenade-multinode-train+(status:op… [2] https://review.opendev.org/#/c/735948/ [3] http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015425.html [4] https://review.opendev.org/#/q/topic:move-stackviz-role+(status:open+OR+sta… -gmann

1 2

[nova][db][haproxy] Question
by Amjad Kotobi 23 Jun '20

23 Jun '20

Hi, In our control plane cluster which HA setup by - Pacemaker/Corosync - HAProxy When I’m moving virtual IP (VIP) to another node services - nova[api-scheduler-conductor] - cinder - etc… In all logs show ERROR nova.servicegroup.drivers.db DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on '10.60.1.220' ([Errno 111] ECONNREFUSED)") [SQL: u'SELECT 1’] And here is haproxy.cfg ########## global chroot /var/lib/haproxy daemon group haproxy maxconn 16000 pidfile /var/run/haproxy.pid user haproxy defaults log 127.0.0.1 local0 maxconn 16000 option redispatch retries 3 timeout http-request 10s timeout queue 1m timeout connect 10s timeout client 3600s timeout server 3600s timeout check 10s listen galera_cluster bind 10.60.1.220:3306 balance source server controller5 10.60.1.15:3306 check inter 2000 rise 2 fall 5 server controller6 10.60.1.16:3306 backup check inter 2000 rise 2 fall 5 server controller7 10.60.1.17:3306 backup check inter 2000 rise 2 fall 5 ########### I know it’s not service level problem or bug and causing by haproxy and mysql connection. I’m wondering if any experience or idea how to deal with it will be great

1 0

[dragonflow] Finish retiring project
by Sean McGinnis 23 Jun '20

23 Jun '20

This is a notice to make sure folks are aware. I plan on completing the retirement process for the dragonflow project. Dragonflow was removed from official governance in late 2018 with: https://review.opendev.org/#/c/613856/ While removed from governance, the project still had a few occasional contributors. Actual development had already tapered off, but really since removal from governance, activity has dwindled to the occasional gate or requirement related update, or random typo corrections. The last patches that have merged for this repo were in August 2019, and gate jobs have been broken for some time now with no one working on fixing them. This is to serve as an announcement of my intent to follow the retirement process to officially mark the project as retired and clean things up. Please respond here if there are an concerns about this plan. Sean

1 0

[neutron][neutron-dynamic-routing] Call for maintainers
by Slawek Kaplonski 23 Jun '20

23 Jun '20

Hi, During last, virtual PTG we discussed about health of neutron stadium projects (again). And it seems that neutron-dynamic-routing project is slowly going to be in similar state as neutron-fwaas in Ussuri. So there is basically no active maintainers of this project in our community. In Ussuri cycle there was Ryan Tidwell from SUSE who was taking care of this project but AFAIK he is not able to do that anymore in Victoria cycle. So, if You are using this project or are interested in it, please contact me by email or on IRC that You want to take care of it. Usually this don't means like a lot of work every day. But we need someone who we can ask for help e.g. when gate is broken or when there is some new bug reported and there is need to triage it. -- Slawek Kaplonski Senior software engineer Red Hat

6 10

[openstack-helm] Meeting Canceled - June 23rd 2020
by Gage Hugo 23 Jun '20

23 Jun '20

Hello, Today's meeting for OpenStack-Helm is cancelled. We will meet at the regular time next week.

1 0

[kuryr][kuryr-libnetwork]
by Michał Dulko 23 Jun '20

23 Jun '20

Hi, Due to shortage of kuryr-libnetwork core reviewers Hongbin proposed that we should soften the rules a bit and allow merging patches with just one +2. I'm totally fine with that, especially as the volume of changes showing up in the project is pretty small. If nobody will have anything against the idea, I'll just go on and update the docs later this week. Thanks, Michał

2 2

[tripleo] Stop using host's /run|/var/run inside containers
by Cédric Jeanneret 23 Jun '20

23 Jun '20

Hello all! While working on podman integration, especially the SELinux part of it, I was wondering why we kept using the host's /run (or its replicated /var/run) location inside containers. And I'm still wondering, 2 years later ;). Reasons: - from time to time, there are patches adding a ":z" flag to the run bind-mount. This breaks the system, since the host systemd can't write/access container_file_t SELinux context. Doing a relabeling might therefore prevent a service restart. - in order to keep things in a clean, understandable tree, getting a dedicated shared directory for the container's sockets makes sense, as it might make things easier to check (for instance, "is this or that service running in a container?") - if an operator runs a restorecon during runtime, it will break container services - mounting /run directly in the containers might expose unwanted sockets, such as DBus (this creates SELinux denials, and we're monkey-patching things and doing really ugly changes to prevent it). It's more than probable other unwanted shared sockets end in the containers, and it might expose the host at some point. Here again, from time to time we see new SELinux policies being added in order to solve the denials, and it creates big holes in the host security AFAIK, no *host* service is accessed by any container services, right? If so, could we imagine moving the shared /run to some other location on the host, such as /run/containers, or /container-run, or any other *dedicated* location we can manage as we want on a SELinux context? I would therefore get some feedback about this proposed change. For the containers, nothing should change: - they will get their /run populated with other containers sockets - they will NOT be able to access the host services at all. Thank you for your feedback, ideas and thoughts! Cheers, C. -- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/

2 3

[tc][election] campaign discussion: how TC can solve the less contributor issue?
by Ghanshyam Mann 22 Jun '20

22 Jun '20

This topic is a very important and critical area to solve in the OpenStack community. I personally feel and keep raising this issue wherever I get the opportunity. To develop or maintain any software, the very first thing we need is to have enough developer resources. Without enough developers (either open or closed source), none of the software can survive. OpenStack current situation on contributors is not the same as it was few years back. Almost every project is facing the less contributor issue as compare to requirements and incoming requests. Few projects already dead or going to be if we do not solve the less contributors issue now. I know, TC is not directly responsible to solve this issue but we should do something or at least find the way who can solve this. What do you think about what role TC can play to solve this? What platform or entity can be used by TC to raise this issue? or any new crazy Idea? -gmann

14 26

[Image-Encryption] current state
by Josephine Seifert 22 Jun '20

22 Jun '20

Hi from the image-encryption-popupteam, we would like to provide a summary of what happened during the last year: 1. Secret Consumers in Barbican [1] As a foundation for the image encryption - and to not accidentally delete a secret, which is still in use - the Barbican team implemented the secret consumers. Their is still some work ongoing for the API part. We will use this feature whenever a image will be encrypted. 2. Specs We wrote Specs to describe, what we Image Encryption is and how it would affect Glance, Cinder and Nova. The Cinder spec got merged [2] . The Glance spec is still being reviewed [3]. And the nova spec is abandoned [4]. Nova is currently not part anymore, because of a missing ephemeral storage encryption needed for a coherent security mode. 3. WIP-patches We implemented two WIP-patches to let Glance devs get a better idea of how image encryption is affecting Glance. We provided a patch for Glance [5] and one for os-brick [6], which handles the encryption and decryption of images. [1] https://review.opendev.org/#/q/project:openstack/barbican+secret-consumer [2] https://review.opendev.org/#/c/608663/ [3] https://review.opendev.org/#/c/609667/11 [4] https://review.opendev.org/#/c/608696/ [5] https://review.opendev.org/#/c/705445/ [6] https://review.opendev.org/#/c/709432/ We appreciate reviews on the spec and the WIP-patches. greetings Josephine (Luzi) & Markus (mhen)

2 1

Q2 Open Infrastructure Community Meetings - June 25th
by Sunny Cai 22 Jun '20

22 Jun '20

Hello everyone, The Q2 OSF Community meetings are only three days away! The project teams are holding two community meetings: one on Thursday, June 25th at 8am PT and another one on the same day at 7pm PT (June 26th at 10am Beijing Time). Here I have attached the calendar invites for the two community meetings. Join us: • Thursday, June 25 at 8am PT (1500 UTC) • Moderator • Jimmy McArthur, OSF • Presenters / Open for Questions • Airship: Alex Hughes • Kata Containers: Eric Ernst • OpenInfra Labs: Michael Daitzman • OpenStack: Ghanshyam Mann • OpenStack 10th birthday: Sunny Cai • StarlingX: Bruce Jones • Zuul: Monty Taylor • OpenInfra / OpenStack Days: Allison Price • Open Infrastructure Summit: Erin Disney • PTG: Kendall Waters • OpenDev: Ashlee Ferguson • Thursday, June 25 at 7pm PT (June 26th at at 0200 UTC/10am China Standard Time) • Moderator: • Sunny Cai, OSF • Presenters / Open for Questions • Airship: Alex Hughes • Kata Containers: Xu Wang • OpenInfra Labs: Michael Daitzman • OpenStack: Rico Lin • OpenStack 10th birthday: Sunny Cai • StarlingX: Yong Hu • Zuul: Clark Boylan • OpenInfra / OpenStack Days: Horace Li • Open Infrastructure Summit: Erin Disney • PTG: Kendall Waters • OpenDev: Ashlee Ferguson Zoom links for each meeting can be found in the calendar hold or here: https://etherpad.opendev.org/p/OSF_Community_Meeting_Q2 <https://etherpad.opendev.org/p/OSF_Community_Meeting_Q2> See you there! Sunny Cai OpenStack Foundation sunny(a)openstack.org <mailto:sunny@openstack.org>

1 0

[tc] weekly update
by Mohammed Naser 22 Jun '20

22 Jun '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. Kristi’s change has been open for quite sometime without much response, I’d like to ask for our TC members to please have a look at it. # OPEN REVIEW - [draft] Add assert:supports-standalone https://review.opendev.org/#/c/722399/ [open for 47 days] - Create starter-kit:kubernetes-in-virt tag https://review.opendev.org/#/c/736369/ # PROJECT UPDATES - Record deprecated cycle for deprecated project https://review.opendev.org/#/c/736084/ - Remove mox3 from governance https://review.opendev.org/#/c/736754/ - Deprecate neutron-fwaas and neutron-fwaas-dashboard master branch https://review.opendev.org/#/c/735828/ - Add openstack-ansible-os_adjutant repo https://review.opendev.org/#/c/736140/ - Retire Paunch https://review.opendev.org/#/c/734855/ - Retire swift-specs https://review.opendev.org/#/c/733901/ - Retire puppet-congress https://review.opendev.org/#/c/737145/ # PROJECTS RETIRED - Remove tricircle project team https://review.opendev.org/#/c/731566/ # GENERAL CHANGES - Remove grace period on resolutions https://review.opendev.org/#/c/735361/ - Tools: update check-review-status to drop grace period https://review.opendev.org/#/c/735361/ - Tools: fix check_review_status for new project-update https://review.opendev.org/#/c/735660/ - Update joining-tc.rst to be general tc-guide.rst https://review.opendev.org/#/c/735660/ - Assign TC Liasons for the Victoria Cycle https://review.opendev.org/#/c/735667/ - Add evrardjp liaison preferences https://review.opendev.org/#/c/735499/ - Add ricolin liaison preference https://review.opendev.org/#/c/735506/ - Add more clarification on project retirement process https://review.opendev.org/#/c/734648/ - Merging TC and UC into a single body https://review.opendev.org/#/c/734074/ # ABANDONED CHANGES - Document project removal and deprecation process https://review.opendev.org/#/c/734930/ Overall, I’m also pretty happy with our bandwidth at landing things with our relaxing governance rules. I'm going to look at more ways we can land more things quicker soon again Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[neutron] netflow exports from open vswitch
by James Denton 22 Jun '20

22 Jun '20

Hello all, Has anyone here configured their Neutron-managed Open vSwitch to export netflow data to a collector? I’ve seen plenty of documentation on how to configure the export, but little-to-nothing regarding this configuration within the scope of an OpenStack cloud. Seems pretty straightforward, but we’re curious as to what the performance impacts might be and whether or not the configuration gets wiped or persists in the OVSDB. Thanks! James Denton

1 0

[neutron] subnet policy for ip allocation
by Ruslanas Gžibovskis 22 Jun '20

22 Jun '20

Hi team, I need that my IP addresses in subnet would not be allocated from the beginning, but it would go to the next IP compared to previous used: instance1 created: 1.1.1.1 Instance2 created: 1.1.1.2 instance1 deleted. instance2 deleted. Instance3 created: 1.1.1.3 (not 1.1.1.1 again) I remember have read about such, do not remember how to google it... -- Ruslanas Gžibovskis +370 6030 7030

2 2

[neutron] Bug deputy report (week starting on 2020-06-15)
by Bernard Cafarelli 22 Jun '20

22 Jun '20

Hello neutrinos, time for a new bug deputy rotation again, here is the list for week 25. Aside from the week highlights (aka multiple gate issues, see Ghanshyam's gate status recap mail), most reported bugs are underway except 1884067 <https://bugs.launchpad.net/neutron/+bug/1884067> (high, filtering issue) and 1884254 <https://bugs.launchpad.net/neutron/+bug/1884254> (low, potential dataplane issues) Critical * ovn based neutron gate jobs failing 100% of times - https://bugs.launchpad.net/neutron/+bug/1883601 OVS compilation failure with latest kernel, fixed in master https://review.opendev.org/735799 * 'tox' not present on devstack based jobs - https://bugs.launchpad.net/devstack/+bug/1884256 Fixed in master: https://review.opendev.org/737016/ High * [API] Filtering by fields not allowed to see is possible for regular users - https://bugs.launchpad.net/neutron/+bug/1884067 Unassigned * Adding a third DHCP agent to the network fails due to binding index error - https://bugs.launchpad.net/neutron/+bug/1883513 Probably introduced by https://review.opendev.org/288271/, fix in progress: https://review.opendev.org/735872 * [ovn] Agent liveness checks create too many writes into OVN db - https://bugs.launchpad.net/neutron/+bug/1883554 OVN Performance hit, fix merged: https://review.opendev.org/735618 * [SRIOV] SR-IOV agent need to have privsep configured - https://bugs.launchpad.net/neutron/+bug/1883757 Fix for SRIOV with macvtap, merged: https://review.opendev.org/735982 * [DHCP] IPv6 "addr6_list" change the "host" file format - https://bugs.launchpad.net/neutron/+bug/1884105 Fix merged: https://review.opendev.org/736778 Medium * [OVN] enable_distributed_floating_ip changes are not applied for existing NAT entries - https://bugs.launchpad.net/neutron/+bug/1883559 Fix in progress: https://review.opendev.org/735613 * Failed to create a duplicate DefaultSecurityGroup (with Calico plugin) - https://bugs.launchpad.net/neutron/+bug/1883730 Fix in progress: https://review.opendev.org/736842 Low * Restart of neutron-ovs-agent may cause data plane breakage - https://bugs.launchpad.net/neutron/+bug/1884254 Unassigned, can happen with rabbitmq connectivity issue * tc_lib (QoS; tc qdisc tbf) uses wrong value for byte/s conversion - https://bugs.launchpad.net/bugs/1884273 kbit/kibit issue, fix in progress: https://review.opendev.org/737044 Wishlist * Neutron should retry http connections when notifying e.g. nova - https://bugs.launchpad.net/neutron/+bug/1883712 Similar to a patch in nova (adding retries parameter to neutron client calls), fix in progress: https://review.opendev.org/736026 Invalid/incomplete * Subnet creation with gateway outside of CIDR is allowed - https://bugs.launchpad.net/neutron/+bug/1884009 As reminded by amotoki, this is intentional, discussed in https://bugs.launchpad.net/neutron/+bug/1335023 * Got unknown error when creating subnet without subnetpool - https://bugs.launchpad.net/python-neutronclient/+bug/1884334 Error missing in openstack CLI command, this was fixed some time ago -- Bernard Cafarelli

1 0

[all][qa] uWSGI release broke devstack jobs
by Andreas Jaeger 21 Jun '20

21 Jun '20

The new uWSGI 2.0.19 release changed packaging (filename and content) and thus broke devstack. The QA team is currently fixing this, changes need backporting to fix grenade as well. On master, change [1] was merged to use distro packages for Ubuntu and Fedora instead of installation from source for uWSGI. CentOS and openSUSE installation is not fixed yet ([2] proposed for openSUSE). Thus, right now this should work again: * Fedora and Ubuntu the devstack jobs on master Other distributions and branches and grenade are still broken. Please do NOT recheck until all fixes are in. If you want to help, best reach out on #openstack-qa. Thanks especially to Jens Harbott for driving this! Andreas [1] https://review.opendev.org/577955 [2] https://review.opendev.org/735519 -- Andreas Jaeger aj(a)suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB

3 3