January 2022 - openstack-discuss - lists.openstack.org

[tripleo]Making CentOS Stream 9 jobs voting and remove cs8 jobs
by Chandan Kumar 12 Jan '22

12 Jan '22

Hello, By the start of the year 2022, we have added CentOS Stream 9 tripleo non-voting jobs in the check pipeline. Now these jobs seem to be healthy. The TripleO CI team has put a lot of effort into adding these jobs. Now it's time to make them voting. Below is the status of each job: * content provider and Standalone Jobs https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-9-content-prov… * Standalone Sc1 to 4 https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-9-scenario001-… * Standalone sc7, Sc10 and Sc12 https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-9-scenario007-… * Multinode and undercloud jobs https://zuul.openstack.org/builds?job_name=ripleo-ci-centos-9-containers-mu… Here are the plans for moving forward with Master release: * Merge https://review.opendev.org/q/hashtag:%22c9voting%22+(status:open%20OR%20sta… patches to make the above jobs voting and gating. - It means tripleo patches might be seeing a lot of cs8 and cs9 jobs running on the patch and blocking it. * We will keep both cs8 and cs9 jobs running for 1 or 2 weeks. - Note: It might increase the load on infra. * After 2 weeks, we will start removing cs8 jobs from the check and gate jobs. * RDO third party c8 jobs will be still running against tripleo patches until CS9 OVB jobs are proven stable in check. Thank you and please reach out to us for any concerns or queries. With Regards, Chandan Kumar

1 0

[cinder] Bug deputy report for week of 01-12-2022
by Sofia Enriquez 12 Jan '22

12 Jan '22

This is a bug report from 01-05-2021 to 01-12-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1956887 "LVM backed ISCSI device not reporting the same size to nova." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1957073 "rbd: snapshot can't be deleted/unmanaged if its source volume is deleted from backend." Assigned to Takashi Kajinami. Incomplete - https://bugs.launchpad.net/cinder/+bug/1956601"Cinder doc is not reproducible." Unassigned. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[TripleO] Douglas Viroel for tripleo-ci core
by Marios Andreou 12 Jan '22

12 Jan '22

Hello TripleO ( & happy new year :) \o/ ) I'd like to propose Douglas Viroel [1] for core on the tripleo-ci repos (openstack/tripleo-ci, openstack/tripleo-quickstart-extras, openstack/tripleo-quickstart, openstack/tripleo-repos). Doug joined the team last year and besides his code contributions he has also been consistently providing many very useful and thoughtful code reviews. I think he will be an excellent addition to the ci core team. As is customary, let's leave this thread open for a week and if there are no objections or other concerns then we add Doug to the core group next week. thanks, marios [1] https://review.opendev.org/q/owner:viroel%2540gmail.com

11 15

[openstack-helm] No meeting tomorrow
by Gage Hugo 11 Jan '22

11 Jan '22

Hey team, Since there are no agenda items [0] for the IRC meeting tomorrow, the meeting is canceled. Our next meeting will be Jan 18th. Thanks [0] https://etherpad.opendev.org/p/openstack-helm-weekly-meeting

1 0

[Deploy] Can three all-in-one nodes form a OpenStack cluster?
by 韩光宇 10 Jan '22

10 Jan '22

Dear all, I am deploing OpenStack Victoria. Can I make a cluster with three all-in-one nodes? Will this have any problems or points to be aware of? Sorry to bother, Thank you very much. Han Guangyu.

3 4

Monasca in kolla-ansible
by Karera Tony 10 Jan '22

10 Jan '22

Dear Team, I hope all is well. I have deployed Openstack with kolla-ansible and enabled Monasca among the projects. The deployment was successful but unfortunately I can't see Logging in the Dashn=board. Kindly advise If I could be missing something. Regards Tony Karera

2 2

[nova][requirements] fasteners===0.16.3 held back by nova
by Matthew Thode 10 Jan '22

10 Jan '22

This one is simple, and iirc is blocked on upstream fixing something (but cannot find the reference). fasteners===0.16.3 https://review.opendev.org/823470 and https://review.opendev.org/804246 both test this change. -- Matthew Thode

4 4

[glance] Does glance not support using local filesystem storage in a cluster
by 韩光宇 10 Jan '22

10 Jan '22

Deal all, Sorry that maybe I ask a stupid question. But I'm really confused with it and didn't find discuss in glance document(https://docs.openstack.org/glance/latest/). I have a OpenStack Victoria cluster with three all-in-one node in centos8. I implemented it with reference to https://docs.openstack.org/ha-guide/. So this cluster use Pacemaker, HAproxy and Galera. "To implement high availability, run an instance of the database on each controller node and use Galera Cluster to provide replication between them." I found that I will encounter an error If I configure Glance backend to use local storage driver to store image files on the local disk. If I upload a image, this image only will be storaged in one node. But the database only storage the file path of image such as "/v2/images/aa3cbee0-717f-4699-8cca-61243302d693/file", don't have the host information. The database data is same in three node. If I upload a image in node1, image only is storaged in node1. The database of three node stores the local filesystem path of image. And If The create Instance task is assigned to node2, It will find image in node2, but image can't be found in node2. So we get the "Image has no associated data" error. So I want to ask: 1. Wheter glance does not support using local filesystem storage in a cluster? 2. If 1 was right, why do we do this design instead of storing information about the host on which images is located, as nova does with instance. I would appreciate any kind of guidance or help. Thank you, Han Guangyu

5 7

Huge Fake tap device creating on some Compute node || Open vSwitch
by Md. Hejbul Tawhid MUNNA 10 Jan '22

10 Jan '22

1 0

[kolla] Updating libvirt container images without VM downtime
by J-P Methot 09 Jan '22

09 Jan '22

Hi, I'm looking for validation regarding the way Kolla and containers work in regard to upgrading the libvirt containers. Essentially, when you upgrade the libvirt container to a new container image, the container needs to be restarted, thus creating downtime for the VMs. There is no way to avoid this downtime, unless you migrate the VMs to another node and then move them back once the container has restarted, right? -- Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc.

4 4