December 2020 - openstack-discuss

[largescale-sig] Next meeting: December 16, 15utc
by Thierry Carrez 16 Dec '20

16 Dec '20

Hi everyone, We'll have our last 2020 Large Scale SIG meeting this Wednesday in #openstack-meeting-3 on IRC, at 15UTC. You can doublecheck how it translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201216T15 Our main topic will be to review the various scaling stages[1] and identify low-hanging-fruit tasks to do a first pass at improving those pages. [1] https://wiki.openstack.org/wiki/Large_Scale_SIG Feel free to add other topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting Talk to you all later, -- Thierry Carrez

1 1

[kolla] Cancelling next 3 IRC meetings
by Mark Goddard 16 Dec '20

16 Dec '20

Hi, Due to various holidays, we will cancel the next 3 IRC meetings and meet again on 13th January. Regards, Mark

1 0

[ironic] IPA images: CentOS 8, Stream and Debian
by Dmitry Tantsur 16 Dec '20

16 Dec '20

Hi wonderful ironicers! Unless you spend the whole last week under a rock (good for you - I mean it!), you must be already aware that the classical CentOS as we know it is going away in favour of CentOS Stream, and maybe as soon as in the end of 2021! For us it means two things: 1) Bifrost will test with CentOS Stream, which may not 100% match the current stable RHEL. 2) We need to decide what to do with our published DIB images [1], currently based on CentOS 8. I'd like to concentrate on problem #2. We have conducted an experiment of switching to CentOS Stream, and it did not go so well. The image size has increased from ~ 340 MiB to nearly 450 MiB, causing serious issues in CI jobs using it. Because of this we're reverting the switch and considering other options. One is to figure out what causes the size increase and remove packages or manually delete files. We're already doing it quite intensively, so I expect this option to be time-consuming. We'll probably have to repeat this exercise regularly to keep up with the distribution changes. The other option is to switch to another distro. Debian looks promising in this context: 3 years of support and the image size is just 273 MiB. I have a patch [2] up for people who want to try the resulting image on their bare metal machines. What do you think? Are there any concerns with either option? [1] https://tarballs.openstack.org/ironic-python-agent/dib/files/ [2] https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/767158 -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill

4 9

[neutron]CI meetings in next 2 weeks canceled
by Slawek Kaplonski 16 Dec '20

16 Dec '20

Hi, As we discussed during our last meeting, we are going to cancel our CI meetings in next 2 weeks. Have a great holidays and see You all on the meeting at 5.01.2021 -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[stable][requirements][neutron] Capping pip in stable branches or not
by Bernard Cafarelli 15 Dec '20

15 Dec '20

Hi, now that master branches have recovered from pip new resolver use, I started looking at stable branches status. tl;dr for those with open pending backports, all branches are broken at the moment so please do not recheck. Thinking about fixing gates for these branches, older EM branches may be fine once the bandit 1.6.3 issue [1] is sorted out, but most need a fix against the new pip resolver. pip has a flag to switch back to old resolver, but this is a temporary one that will only be there for a few weeks [2] >From a quick IRC chat, the general guidance for us was always to leave pip uncapped, and the new resolver issues are actually broken requirements. But looking at master fixes, these indicate large and complicated changes on requirements and lower-contraints. Neutron fix [3] required a few major linter bumps and major version bumps in l-c. I guess it may be doable as victoria backport, but this will be messy for previous branches. ovn-octavia-provider is a scarier example [4], from stable point of view the change by itself does not look good for backport, even just for victoria. Also, in master, some fixes were possible by bumping versions on dependencies, but how to fix them if the max possible versions have broken deps themselves? So, how do we proceed to fix stable gates? Ideas and feedback will be most welcome [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019292… [2] http://pyfound.blogspot.com/2020/11/pip-20-3-new-resolver.html [3] https://review.opendev.org/c/openstack/neutron/+/766000 [4] https://review.opendev.org/c/openstack/ovn-octavia-provider/+/765872/32/low… -- Bernard Cafarelli

16 21

RE: Re: New Openstack Deployment questions - how will we respond to this change?
by Braden, Albert 15 Dec '20

15 Dec '20

The purpose of my Openstack Deployment email was not only to rant about the decision to kill Centos 8. I want to make sure that we don't blindly go down the easy route of pretending that Centos Stream is an acceptable replacement for Centos. If we do this, we would do a disservice to the community and to everyone who depends on it. The reality is that, at the end of 2021, Centos will no longer exist as a viable production operating system, and everyone who was using it will have to adjust. For companies that already have Centos mirror repositories setup and people managing them, the increased load imposed by Stream will be incremental, but I suspect that the vast majority of companies do not have that infrastructure already setup, and we will need to carefully consider whether our needs are better met by going forward with Stream or switching to another OS. If the OpenStack community decides to continue building on Stream, we should make it crystal clear to operators and users that Stream is not a production-ready OS and that our Stream OpenStack implementation is suitable for testing and development use only, unless they devote substantial resources to mirroring and testing Stream to insulate production clusters from the instability that it will introduce. If we do decide to continue building on Stream, how will we respond to the constant stream of bug reports that will result when Stream changes cause OpenStack components to fail? Many component teams are already understaffed. Will we have the bandwidth to constantly chase changes? Should we replace our Centos builds with RHEL, or with Rocky? Does the community have (or can we find) the resources to do the work of maintaining stable Stream mirrors and only building OpenStack on our stable versions of Stream? Or would it be better to drop Centos support and focus our efforts on operating systems that have not implemented unilateral changes that harm the community? -----Original Message----- From: Braden, Albert Sent: Friday, December 11, 2020 9:10 AM To: openstack-discuss(a)lists.openstack.org Subject: RE: [EXTERNAL] Re: New Openstack Deployment questions Centos Stream is fine for those who were using Centos for testing or development. It's not at all suitable for production, because rolling release doesn't provide the stability that production clusters need. Switching to Centos Stream would require significant resources to be expended to setup local mirrors and then perform exhaustive testing before each upgrade. The old Centos did this work for us; Centos was built on RHEL source that had already been tested by paying customers, and bugs fixed with the urgency that paying customers require. Adding an upstream build (Stream) to the existing downstream (Centos 8.x) was fine, but I'm disappointed by the decision to kill Centos 8. I don't want to wax eloquent about how we were betrayed; suffice it to say that even for a free operating system, suddenly changing the EOL from 2029 to 2021 is unprecedented, and places significant burdens on companies that are using Centos in production. I can understand why IBM/RH made this decision, but there's no denying that it puts production Centos users in a difficult position. I hope that Rocky Linux [1], under Gregory Kurtzer (founder of the Centos project) will turn out to be a useful alternative. {1} https://github.com/rocky-linux/rocky -----Original Message----- From: Luigi Toscano <ltoscano(a)redhat.com> Sent: Thursday, December 10, 2020 3:51 PM To: Thomas Wakefield <dwakefi2(a)gmu.edu>; openstack-discuss(a)lists.openstack.org Cc: Satish Patel <satish.txt(a)gmail.com> Subject: [EXTERNAL] Re: New Openstack Deployment questions CAUTION: The e-mail below is from an external source. Please exercise caution before opening attachments, clicking links, or following guidance. On Thursday, 10 December 2020 15:27:40 CET Satish Patel wrote: > I just built a new openstack using openstack-ansible on CentOS 8.2 > last month before news broke out. I have no choice so i am going to > stick with CentOS. > > What is the future of RDO and EPEL repo if centOS going away. ? Continue as before on CentOS Stream. -- Luigi I apologize for the nonsense below. So far I have not been able to stop it from being attached to my external emails. I'm working on it. E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

3 2

[tripleo][ci] current status
by Wesley Hayutin 15 Dec '20

15 Dec '20

Greetings, *Master*: OVB jobs are working \0/ again [1] Master promoted today, logged a few tempest failures and moved to skiplist *Victoria*: Promoted today OVB jobs all RED waiting [2] *Ussuri*: RED, we need to land 65077 757836 757821 OVB RED *Train*: Most of Upstream is OK [3], update and upgrade jobs need to move to nv imho until fixed [3] non-passing jobs should just be removed [4] *ALL: *We've only merged 17 patches in the last 24 hours, we're usually closer to 30-40+ per day. I'll keep an eye on it, it's only monday. weee [5] [1] https://review.rdoproject.org/zuul/builds?job_name=tripleo-ci-centos-8-ovb-… [2] https://review.opendev.org/c/openstack/tripleo-heat-templates/+/766797 <https://review.opendev.org/c/openstack/tripleo-heat-templates/+/766797> [3] http://dashboard-ci.tripleo.org/d/3-DYSmOGk/jobs-exploration?orgId=1&var-in… [4] https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-7-standalone-u… https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-7-containerize… https://review.opendev.org/c/openstack/tripleo-ci/+/766621 [5] http://paste.openstack.org/show/801030/

1 1

Is Microsoft Windows 2019, 2016 HyperV supported for nova ?
by Nagarjun Rajaraman 15 Dec '20

15 Dec '20

Hi all , Does anyone know if Microsoft Windows 2019, 2016 HyperV supported for openstack nova ? Could only see supported documentation for 2012 & 2012 R2 , what are the steps are need to follow to integrate Hyper V host that runs windows server 2019 . Best Regards , Arjun

2 1

[oslo] No meeting during the next 2 weeks
by hberaud 15 Dec '20

15 Dec '20

Hello Osloers, I'm on PTO during the next 2 weeks so I'll be AFK. I won't be running the next 2 meetings. If someone else from the Oslo team wants to run it, please feel free. Let me wish you happy end of the year parties! Hervé -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

[ovn][neutron] OVN Production Installation Guide
by Malik Obaid 15 Dec '20

15 Dec '20

Hi, I was wondering if there is any comprehensive OVN production installation guide available, or if anyone who has implemented OVN for Openstack Neutron on their Ubuntu based production environment, is willing to provide the guide here, would be a big help. Waiting for you response. Thank you and best regards, Malik Obaid

1 0