January 2021 - openstack-discuss - lists.openstack.org

pip 21 heads-up (Python 2 support gone)
by Radosław Piliszek 24 Jan '21

24 Jan '21

Hello Fellow OpenStackers, Please notice pip 21 was released just yesterday. It means Python 2 is no longer supported. Upgrading pip to latest on Python 2 may render pip unusable (as ancient pip may not consider 21 an unsupported version and install it nonetheless). Similarly, using default get-pip.py on Python 2 no longer works. There is, however, https://bootstrap.pypa.io/2.7/get-pip.py for those that want to use get-pip.py on Python 2. Kind regards, -yoctozepto

1 0

Re: [tripleo][ussuri][centos8] overcloud deploy fails with no valid host was found, GRUB2 cannot mount with regular user
by Ruslanas Gžibovskis 24 Jan '21

24 Jan '21

Should i try keep only ironic-python-agent-ramdisk ? In my overcloud-image yaml? On Sat, 23 Jan 2021, 23:28 Julia Kreger, <juliaashleykreger(a)gmail.com> wrote: > I'm not so sure about that. Note the different > "ironic-python-agent-ramdisk" versus "ironic-agent" in > > https://github.com/openstack/tripleo-common/blob/stable/ussuri/image-yaml/o… > > On Fri, Jan 22, 2021 at 3:02 PM Ruslanas Gžibovskis <ruslanas(a)lpic.lt> > wrote: > > > > Hi all, > > > > I am trying to build some cloud again and failing with [1]. I think this > is a most critical line. It fails during GRUB2 deployment on overcloud > image, I believe main error message is: mount: only root can do that. I > used the following steps to create image: > > > > cp -ar /etc/yum.repos.d repos > > # enable: repos/CentOS-HA.repo > > sed -i "s/enabled=0/enabled=1/g" repos/CentOS-Linux-HighAvailability.repo > > sed -i "s/gpgcheck=1/gpgcheck=0/g" repos/*repo > > export DIB_YUM_REPO_CONF="$(ls $(pwd)/repos/*repo)" > > export STABLE_RELEASE="ussuri" > > source /home/stack/stackrc > > mkdir /home/stack/images > > cd /home/stack/images > > openstack overcloud image build --config-file > /home/stack/overcloud-images-python3.yaml > > openstack overcloud image upload --update-existing > > # openstack overcloud node configure --all-manageable > > > > overcloud-images-python3.yaml file content can be found here [2], just > added additional packages, such as tcpdump, iperf, iptraf and so on... > > And steps from link [3] to set root pass to troubleshoot if needed. > > > > any thoughts? Maybe there were some changes recently (from 22 of > December) PRevious images from there. Thank you for your thoughts and > attention. > > > > [1] http://paste.openstack.org/show/GDYriAXxQniZTPQGJGbH/ > > [2] http://paste.openstack.org/show/2tkVFdwSZ0QMjoJKmOrm/ > > [3] > https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16… > > > > > > -- > > Ruslanas Gžibovskis > > +370 6030 7030 >

1 0

[review] oslo.messaging patterns in various projects
by Erik Olof Gunnar Andersson 24 Jan '21

24 Jan '21

I was helping troubleshoot an issue with Magnum recently and found out that there was a minor issue with how they handle RPC connections, and decided to do an audit of all OpenStack projects and found a bunch that are likely to be experiencing similar issues. The gist of the issue is that most of these projects creates a new rpc transport on every API call. If someone has some time over to help review these fixes, I would be grateful. https://review.opendev.org/c/openstack/magnum/+/770707 - Re-use transport for rpc calls https://review.opendev.org/c/openstack/magnum/+/770720 - Re-use transport for rpc server https://review.opendev.org/c/openstack/blazar/+/771110 - Re-use rpc transport https://review.opendev.org/c/openstack/solum/+/771111 - Re-use rpc transport https://review.opendev.org/c/openstack/murano/+/771341 - Use common rpc pattern for all services https://review.opendev.org/c/openstack/watcher/+/771381 - Use common rpc pattern for all services I tried to use a standardized approach with all of these, but feel free to add any feedback.

1 0

[tripleo][ussuri][centos8] overcloud deploy fails with no valid host was found, GRUB2 cannot mount with regular user
by Ruslanas Gžibovskis 23 Jan '21

23 Jan '21

Hi all, I am trying to build some cloud again and failing with [1]. I think this is a most critical line. It fails during GRUB2 deployment on overcloud image, I believe main error message is: mount: only root can do that. I used the following steps to create image: cp -ar /etc/yum.repos.d repos # enable: repos/CentOS-HA.repo sed -i "s/enabled=0/enabled=1/g" repos/CentOS-Linux-HighAvailability.repo sed -i "s/gpgcheck=1/gpgcheck=0/g" repos/*repo export DIB_YUM_REPO_CONF="$(ls $(pwd)/repos/*repo)" export STABLE_RELEASE="ussuri" source /home/stack/stackrc mkdir /home/stack/images cd /home/stack/images openstack overcloud image build --config-file /home/stack/overcloud-images-python3.yaml openstack overcloud image upload --update-existing # openstack overcloud node configure --all-manageable overcloud-images-python3.yaml file content can be found here [2], just added additional packages, such as tcpdump, iperf, iptraf and so on... And steps from link [3] to set root pass to troubleshoot if needed. any thoughts? Maybe there were some changes recently (from 22 of December) PRevious images from there. Thank you for your thoughts and attention. [1] http://paste.openstack.org/show/GDYriAXxQniZTPQGJGbH/ [2] http://paste.openstack.org/show/2tkVFdwSZ0QMjoJKmOrm/ [3] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16… -- Ruslanas Gžibovskis +370 6030 7030

2 5

[SIG] [all] [TC] [Automation] [Cloud Research] [k8s] [Containers] [Multi Arch] [Packaging] [PowerVMStacker] [Public Cloud] [Resource Management] Updates Required?
by Kendall Nelson 23 Jan '21

23 Jan '21

Hello Everyone! I don't know if any of you have looked at the sigs governance[0] site lately, but there are a number of SIGs that seem to have out of date statuses and/or chairs listed that are no longer active in the community. >From what I can tell, the following list of SIGs could maybe use some updating. - Automation - Cloud Research - Containers - k8s - Multi Arch - Packaging - PowerVMStacker - Public Cloud - Resource Management I have created an etherpad[1] with all the SIGs for more cohesive discussion on changes. Please make comments there! I am happy to push the updates if things need to change; I just need to know what to change it to. Tangentially related, kudos Rico for chairing the most SIGs by far! -Kendall Nelson (diablo_rojo) [0] https://governance.openstack.org/sigs/ [1] https://etherpad.opendev.org/p/2021-SIG-Updates

1 0

Re: [nova] unit testing on ppc64le
by aditi Dukle 22 Jan '21

22 Jan '21

2 3

[infra][ci] no more 3rd party CI test result in gerrit
by Lu, Lianhao 22 Jan '21

22 Jan '21

Hi All, I noticed that we're no longer be able to see the 3rd party CI test results in most of the projects in openstack gerrit, such as nova, neutron. But we can still see them in the ci-sandbox project. I'm wondering how to see those test results in gerrit now? Thanks! BR, -Lianhao

1 0

[tempest] extending python-tempestconf
by Szabolcs Tóth 22 Jan '21

22 Jan '21

Hej! The official tool named python-tempestconf has a parameter named --create, which allows to create the following resources: * CirrOS image (uploads the image based on the location defined with --image parameter), * Flavors (based on default values - DEFAULT_FLAVOR_RAM, DEFAULT_FLAVOR_RAM_ALT, DEFAULT_FLAVOR_DISK - which can be changed with --flavor-min-mem and --flavor-min-disk). In order to verify our specific installation with Tempest, we need to create the basic resources as * Flavors (with extra-spec parameters like hw:mem_page_size). * Networks (one for fixed_network_name and one for floating_network_name). * python-tempestconf is able to find an already existing network created with router:external flag and set it as value for floating_network_name. * Router and port (for routing traffic between internal and external networks). I would like to ask the following: * Is there any particular reason why the basic resource create functionality is limited to the image and flavor? * Are there any plans to extend the basic resource create functionality? * Ability to set extra parameters for the flavors. * Creating networks, routers and ports (based on a user inputs, which can be separate parameters or a specific file). Would the community accept contributions extending python-tempestconf into this direction? -- BR, Szabolcs

3 2

[All] copyright
by Kanevsky, Arkady 21 Jan '21

21 Jan '21

We have in a few places openstack copyright: # Copyright (c) 2020 OpenStack Foundation Should we use OpenInfra copyright going forward? Something like # Copyright (c) 20XX Open Infrastructure Foundation Thanks, Arkady Kanevsky, Ph.D. SP Chief Technologist & DE Dell EMC office of CTO Dell Inc. One Dell Way, MS PS2-91 Round Rock, TX 78682, USA Phone: 512 7204955

3 3

[barbican][release] Barbican deliverables questions
by Herve Beraud 21 Jan '21

21 Jan '21

Hi Barbican Team, The release team noticed some inconsistencies between the Barbican team's deliverables described in the governance’s reference and deliverables defined in the openstack/releases repo (c.f our related meeting topic [1]). First, we noticed that ansible-role-atos-hsm and ansible-role-thales-hsm are new barbican deliverables, and we would appreciate to know if we should plan to release them for Wallaby. The second thing is that barbican-ui (added in Oct 2019) was never released yet and was not ready yet for ussuri and victoria. maybe we should abandon this instead of waiting? Notice that Wallaby's milestone 2 is next week so it could be the good time to update all these things. Let us know your thoughts, we are waiting for your replies. Thanks for reading, [1] http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-re… -- 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-----

2 2