September 2020 - openstack-discuss

[oslo][release][requirement] FFE request for Oslo lib
by Ghanshyam Mann 11 Sep '20

11 Sep '20

Hello Team, This is regarding FFE for Focal migration work. As planned, we have to move the Victoria testing to Focal and base job switch is planned to be switched by today[1]. There are few oslo lib need work (especially tox job-based testing not user-facing changes) to pass on Focal - https://review.opendev.org/#/q/topic:migrate-to-focal-oslo+(status:open+OR+… If we move the base tox jobs to Focal then these lib victoria gates (especially lower-constraint job) will be failing. We can either do these as FFE or backport (as this is lib own CI fixes only) later once the victoria branch is open. Opinion? [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-September/01706… -gmann

3 6

[InteropWG] Seeking ideas for InteropWG Branding for Open Infra
by prakash RAMCHANDRAN 11 Sep '20

11 Sep '20

Hi all, Please add your ideas for discussions for Forum https://etherpad.opendev.org/p/2020-Wallaby-interop-brainstorming Since any Interop case, it's best presented by PTLs their requirments, like to invite Ironic/metal3/MaaS and Container Projects(Zun,kuryr, magnum, kolla...) to help us define the new Branding strategy for Open Infra projects like (Airship, Starlingx, Kata, Zuul, Openlabs ...) Note we see one opportunity coming out of BareMetal as a Service for Ironic routed through Metal3 which is now a CNCF Sandbox project. The other we see OpenInfa-ready-k8s-container and/or based on Zun- CRI (Docker, Containerd, Kata...), CNI (kuryr) & CSI (?) & COE as Magnum Please add your ideas and time you may need for us to go over these emerging ideas for re-imagining clusters in Open Infra with Baremetal as well VM Nodes over Private & Public clouds. ThanksFor InteropWGPrakash

1 0

[TC][PTG] Virtual PTG Planning
by Kendall Nelson 11 Sep '20

11 Sep '20

Hello! So as you might have seen, the deadline to sign up for PTG time by the end of next week. To coordinate our time to meet as the TC, please fill out the poll[1] that Mohammed kindly put together for us. *We need responses by EOD Thursday September 10th* so that we can book the time in the ethercalc and fill out the survey to reserve our space before the deadline. Also, I created this planning etherpad [2] to start collecting ideas for discussion topics! Can't wait to see you all there! -Kendall & Mohammed [1] https://doodle.com/poll/hkbg44da2udxging [2] https://etherpad.opendev.org/p/tc-wallaby-ptg

1 1

[neutron] Flow drop on agent restart with openvswitch firewall driver
by Alexis Deberg 11 Sep '20

11 Sep '20

Hi All, I'm looking for ideas as we need to upgrade our Neutron deployment and it looks like it would impact workloads a bit much for now to do so and i'm no master of the neutron code... We're running Neutron 14.0.2 with ml2 plugin and firewall_driver set as openvswitch. drop_flows_on_start is default False. Reading at some old bug reports my understanding was that a restart of the neutron-openvswitch-agent should not impact existing flows and be seamless, but this is not what I'm experiencing as I see some temporary drop(s) around when ovs-fctl del-flows/add-flows is called on br-int (either east-west traffic or north-south). I tried switching to iptables_hybrid driver instead and I don't see the issue in that case. e.g when a wget download is happening on an instance while the agent is restarting, I see the following: 2020-09-08 14:26:09 (12.2 MB/s) - Read error at byte 146971864/7416743936 (Success). Retrying I'm a bit lot so i'm wondering if that's expected/known behavior, if a workaround is possible.... Let me know if a bug report might be a better place to dig deeper or not or if you want additional information... or if I missed a closed bug. Thanks !

3 4

[manila][release] Some feature patches will merge today
by Goutham Pacha Ravi 11 Sep '20

11 Sep '20

Hello Stackers, As is unusual, we have found ourselves with a few unmerged feature patches at the wrong side of the feature freeze: [Container driver] Adds share and share server migration: https://review.opendev.org/740831/ [NetApp] Enables configuring NFS transfer limits: https://review.opendev.org/746568 [NetApp] Add support for share server migration: https://review.opendev.org/747048/ [NetApp] Adding support for Adaptive QoS in NetApp driver with dhss false: https://review.opendev.org/740532/ These patches have been getting review attention late in the cycle, and were caught up in CI failures and code collisions. The code changes above are isolated within driver modules in the code that are explicitly configured/optionally enabled by deployers. These changes do not: - introduce any new library dependencies to manila, or - modify the API, DB, RPC, driver interface layers - introduce new requirements into the client library (python-manilaclient) They do introduce translatable exception strings - however, manila has not received translation updates in the past. We're looking to get these merged today. Hope that's okay - do let me know of any gotchas. -- Goutham Pacha Ravi

1 0

"openstack server list" takes 30s
by Tony Liu 11 Sep '20

11 Sep '20

Hi, I built a Ussuri cluster with 3 controllers and 5 compute nodes. OpenStack CLI ran pretty fast at the beginning, but gets slower over time along with increased workloads. Right now, it takes about 30s to list 10 VMs. The CPU, memory and disk usage are on those 3 controllers are all in the range. I understand there are many API calls happening behind CLI. I'd like to figure out how this 30s is consumed, which call is the killer. Any guidance or hint would be helpful. Thanks! Tony

4 3

[release] Release countdown for week R-4 Sept 14 - 18
by Sean McGinnis 11 Sep '20

11 Sep '20

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the victoria deliverables can be proposed, well ahead of the final victoria release date. General Information ------------------- We are still finishing up processing a few release requests, but the victoria release requirements are now frozen. If new library releases are needed to fix release-critical bugs in victoria, you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in victoria that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By September 24 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/victoria branches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for victoria changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed victoria cycle-highlights yet, you are already late to the party. Please see http://lists.openstack.org/pipermail/openstack-discuss/2020-September/01694… for details. Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 24 (R-3) Final Victoria release: October 14 Open Infra Summit: October 19-23 Wallaby PTG: October 26-30

1 0

[Neutron] number of subnets in a network
by Tony Liu 11 Sep '20

11 Sep '20

Hi, Is there any hard limit to the number of subnets in a network? In theory, would it be ok to put, like 5000 subnets, in a network? Thanks! Tony

4 3

Instance cannot ping external (Lan/Internet) Openstack AllinOne Packstack Virtualbox
by dangerzone ar 11 Sep '20

11 Sep '20

Hi Team, I have been struggling to get the solution. I'm testing openstack and deploying it over virtualbox. I have shared my issue in SO with help from berndbausch <https://stackoverflow.com/users/3548109/berndbausch> and try to share it here also to get more help....as I have create and redeploy few times with different openstack release.. deployment methods..parameters....still the same problem. I don't think my deployment is different with others as i follow the guideline and common practise... just stuck on this problem...please do help and assist me further. Thank you to all.... Below is my environment setup. Windos10_Virtualbox----Centos7------Openstack----VM instance [192.168.0.0/24] - external network/public-ip Pc host - 192.168.0.160 Home Lan GW - 192.168.0.1 Centos7 - 192.168.0.12 (VM virtualbox) Openstack Router GW - 192.168.0.221 Virtualbox VM setting bridge (enp0s3) and promiscuous mode all selinux permissive add rules icmp and ssh. create public-ip 192.168.0.0/24 (pool 220-230) create router create private subnet 10.0.0.0/24 attach router to private subnet create router GW(public-ip) >From LAN I can ping and ssh vm instance but from vm instance i cannot ping to home Lan GW, pc host. VM instance can ping up to centos7 virtualbox and openstack Router GW. Instance created with centos and cirros using direct public-ip and also floating ip. Some instance created with direct public ip and some with private subnet and using floating ip. I have tested with queens, stein, train. With allinone and also using answerfile and all end up I cannot ping external. I follows guideline below:- *hxxps://www.linuxtechi.com/single-node-openstack-liberty-installation-centos-7/ <http://www.linuxtechi.com/single-node-openstack-liberty-installation-centos…>* *hxxps://www.rdoproject.org/install/packstack/ <http://www.rdoproject.org/install/packstack/>* This some of answer file parameters that i edited CONFIG_NEUTRON_L3_EXT_BRIDGE=br-ex CONFIG_NEUTRON_ML2_TYPE_DRIVERS=flat,vxlan CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=extnet:br-ex CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-ex:enp0s3 CONFIG_NEUTRON_OVS_BRIDGES_COMPUTE=br-ex CONFIG_PROVISION_DEMO=n ip netns list qrouter-f6967bba-986e-4bb3-838e-d035a684e2c4 (id: 2) qdhcp-dbd713cd-1af4-4e2c-9c57-d8a675a10608 (id: 1) qdhcp-fa6fb1d6-b65e-4eb2-a4a4-5552fde8bb08 (id: 0) [root@myospackanswer ~(keystone_admin)]# ip netns exec qrouter-f6967bba-986e-4bb3-838e-d035a684e2c4 arp -an ? (192.168.0.211) at <incomplete> on qg-0ba7da31-7f ? (192.168.0.227) at fa:16:3e:ed:19:81 [ether] on qg-0ba7da31-7f (Instance IP) ? (192.168.0.160) at d4:d2:52:73:de:80 [ether] on qg-0ba7da31-7f (host pc IP) ? (192.168.0.1) at 80:26:89:b2:98:50 [ether] on qg-0ba7da31-7f (home router GW) ? (10.0.0.4) at fa:16:3e:01:63:42 [ether] on qr-7e6f9436-40 (private subnet) ip r default via 192.168.0.1 dev br-ex169.254.0.0/16 dev enp0s3 scope link metric 1002169.254.0.0/16 dev br-ex scope link metric 1006192.168.0.0/24 dev br-ex proto kernel scope link src 192.168.0.121 qrouter-f6967bba-986e-4bb3-838e-d035a684e2c4 (id: 2) qdhcp-dbd713cd-1af4-4e2c-9c57-d8a675a10608 (id: 1) qdhcp-fa6fb1d6-b65e-4eb2-a4a4-5552fde8bb08 (id: 0) sudo ip netns exec qrouter-f6967bba-986e-4bb3-838e-d035a684e2c4 ip route default via 192.168.0.1 dev qg-0ba7da31-7f10.0.0.0/24 dev qr-7e6f9436-40 proto kernel scope link src 10.0.0.1192.168.0.0/24 dev qg-0ba7da31-7f proto kernel scope link src 192.168.0.221 ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master ovs-system state UP group default qlen 1000 link/ether 08:00:27:98:9b:a3 brd ff:ff:ff:ff:ff:ff inet6 fe80::a00:27ff:fe98:9ba3/64 scope link valid_lft forever preferred_lft forever 5: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 8a:17:8b:e5:dc:c2 brd ff:ff:ff:ff:ff:ff 6: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 08:00:27:98:9b:a3 brd ff:ff:ff:ff:ff:ff inet 192.168.0.121/24 brd 192.168.0.255 scope global br-ex valid_lft forever preferred_lft forever inet6 2001:e68:5435:d135:a00:27ff:fe98:9ba3/64 scope global mngtmpaddr dynamic valid_lft 86399sec preferred_lft 86399sec inet6 fe80::a00:27ff:fe98:9ba3/64 scope link valid_lft forever preferred_lft forever 7: br-int: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000 link/ether 32:ff:0f:26:18:43 brd ff:ff:ff:ff:ff:ff 8: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether d6:52:08:a9:68:4f brd ff:ff:ff:ff:ff:ff 29: qbr1f637f14-9c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000 link/ether 42:95:e8:c0:a3:07 brd ff:ff:ff:ff:ff:ff 30: qvo1f637f14-9c@qvb1f637f14-9c: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1450 qdisc noqueue master ovs-system state UP group default qlen 1000 link/ether 6e:2e:07:8d:79:86 brd ff:ff:ff:ff:ff:ff inet6 fe80::6c2e:7ff:fe8d:7986/64 scope link valid_lft forever preferred_lft forever 31: qvb1f637f14-9c@qvo1f637f14-9c: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1450 qdisc noqueue master qbr1f637f14-9c state UP group default qlen 1000 link/ether 42:95:e8:c0:a3:07 brd ff:ff:ff:ff:ff:ff inet6 fe80::4095:e8ff:fec0:a307/64 scope link valid_lft forever preferred_lft forever 32: tap1f637f14-9c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast master qbr1f637f14-9c state UNKNOWN group default qlen 1000 link/ether fe:16:3e:05:2d:50 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe05:2d50/64 scope link valid_lft forever preferred_lft forever

1 0

Ussuri - make added mptsas driver to introspection initramfs load automatically
by Oliver Weinmann 11 Sep '20

11 Sep '20

Hi, I already asked this question on serverfault. But I guess here is a better place. I have a very ancient hardware with a MPTSAS controller. I use this for TripleO deployment testing. With the release of Ussuri which is running CentOS8, I can no longer provision my overcloud nodes as the MPTSAS driver has been removed in CentOS8: https://www.reddit.com/r/CentOS/comments/d93unk/centos8_and_removal_mpt2sas… I managed to include the driver provided from ELrepo in the introspection image but It is not loaded automatically: All commands are run as user "stack". Extract the introspection image: cd ~ mkdir imagesnew cd imagesnew tar xvf ../ironic-python-agent.tar mkdir ~/ipa-tmp cd ~/ipa-tmp /usr/lib/dracut/skipcpio ~/imagesnew/ironic-python-agent.initramfs | zcat | cpio -ivd | pax -r Extract the contents of the mptsas driver rpm: rpm2cpio ~/kmod-mptsas-3.04.20-3.el8_2.elrepo.x86_64.rpm | pax -r Put the kernel module in the right places. To figure out where the module has to reside I installed the rpm on a already deployed node and used find to locate it. xz -c ./usr/lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko > ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/kernel/drivers/message/fusion/mptsas.ko.xz mkdir ./usr/lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas sudo ln -sf /lib/modules/4.18.0-193.el8.x86_64/extra/mptsas/mptsas.ko lib/modules/4.18.0-193.6.3.el8_2.x86_64/weak-updates/mptsas.ko sudo chown root . -R find . 2>/dev/null | sudo cpio --quiet -c -o | gzip -8 > ~/images/ironic-python-agent.initramfs Upload the new image cd ~/images openstack overcloud image upload --update-existing --image-path /home/stack/images/ Now when I start the introspection and ssh into the host I see no disks: [root@localhost ~]# fdisk -l [root@localhost ~]# lsmod | grep mptsas Once i manually load the driver, I can see the disks: [root@localhost ~]# modprobe mptsas [root@localhost ~]# lsmod | grep mptsas mptsas 69632 0 mptscsih 45056 1 mptsas mptbase 98304 2 mptsas,mptscsih scsi_transport_sas 45056 1 mptsas [root@localhost ~]# fdisk -l Disk /dev/sda: 67.1 GiB, 71999422464 bytes, 140623872 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes But how can I make it so that it will automatically load on boot? Best Regards, Oliver

1 0