May 2022 - openstack-discuss - lists.openstack.org

[largescale-sig] Next meeting: May 25th, 15utc
by Thierry Carrez 25 May '22

25 May '22

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can check how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220525T15 Feel free to add topics to the agenda: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[neutron] Propose Yatin Karel for Neutron core team
by Lajos Katona 25 May '22

25 May '22

Hi Neutrinos, I would like to propose Yatin Karel (IRC: ykarel) as a member of the Neutron core team. Yatin is a long time Openstack developer, and started concentrating to Networking projects in the last few cycles. His experience, proactivity and sharp eye proved to be very helpful both in reviews and fixing issues. His reviews are really valuable and reflect his experience and helpfulness. I am sure that he will be a great addition to the core team. Please vote for his nomination by answering this mail till next Tuesday. Lajos Katona (lajoskatona)

7 6

Need help
by Gk Gk 25 May '22

25 May '22

Hi All, In this link https://docs.openstack.org/nova/queens/user/aggregates.html , there is a warning section about availability zones: "That last rule can be very error-prone. Since the user can see the list of availability zones, they have no way to know whether the default availability zone name (currently *nova*) is provided because an host belongs to an aggregate whose AZ metadata key is set to *nova*, or because there are at least one host belonging to no aggregate. Consequently, it is highly recommended for users to never ever ask for booting an instance by specifying an explicit AZ named *nova* and for operators to never set the AZ metadata for an aggregate to *nova*. That leads to some problems due to the fact that the instance AZ information is explicitly attached to *nova* which could break further move operations when either the host is moved to another aggregate or when the user would like to migrate the instance." My questions are, 1. If a host belongs to an aggregate whose AZ metadata key is set to nova, why is it not possible to know if a default AZ is provided or not ? 2. Why is it a problem when the host is moved to another aggregate ? We can move hosts from one aggregate to another. Right ? 3. Why is it a problem when we migrate the instance ? Thanks Kumar

3 2

[cinder] Bug deputy report for week of 05-25-2022
by Sofia Enriquez 25 May '22

25 May '22

This is a bug report from 05-18-2022 to 05-25-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- No meeting today! High - https://bugs.launchpad.net/cinder/+bug/1974078 "Scheduler doesn't consume space properly for create_volume." Unassigned. Incomplete - https://bugs.launchpad.net/cinder/+bug/1974092 "Cinder-backup tries to take incremental backups of failed previous backups." 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] gate blocker - openstacksdk library - please hold rechecks
by Ronelle Landy 25 May '22

25 May '22

Hello All, We have a blocker on TripleO check/gate/integration jobs detailed in: https://bugs.launchpad.net/tripleo/+bug/1975646 - tripleo tests are failing os_tempest with "openstacksdk library MUST be >=0.99." There is a proposed fix in test now: https://review.opendev.org/c/openstack/tripleo-ci/+/843220. Please hold rechecks until we can either merge the fix or revert the breaking change. Thank you, TripleO CI.

2 1

[nova] Snapshot Image Format
by Ammad Syed 25 May '22

25 May '22

Hi, I am using nova 24.0. I have an image in raw format in glance store. I have created a volume backed instance from raw image. Then I have created the server image using nova api below with *createImage* . https://docs.openstack.org/api-ref/compute/?expanded=create-image-createima… OR via openstack server image create --name <name> <server uuid> The created image I see in glance store is in qcow2 format. I have set this option snapshot_image_format in nova.conf but still it creates the images in qcow2 format. How config need to be done if i need to save server image in raw format ? Ammad

1 0

Re: [GLANCE][VICTORIA] - Multi-backend support with ceph backed swift.
by Gaël THEROND 25 May '22

25 May '22

Sure! However it is specified two times within the official glance configuration, once in glance_store and once in glance.store.swift.store but that last section is really not that well documented. https://docs.openstack.org/glance/latest/configuration/glance_api.html#glan… Le mar. 24 mai 2022 à 17:54, Abhishek Kekane <akekane(a)redhat.com> a écrit : > Hi Gaël, > > Can you try moving default_swift_reference from glance_store section to > particular swift store section, i.e. cold as per your configs. > > I guess that is the issue. > > Abhishek > > On Tue, 24 May 2022 at 7:30 PM, Gaël THEROND <gael.therond(a)bitswalk.com> > wrote: > >> Hi everyone, >> >> I'm currently enabling glance multi backend support for one of our >> platforms and we're facing a weird situation. >> >> This platform is a CentOS 8 Stream based Openstack VICTORIA and when we >> enable the multi-backends feature, the swift store isn't working properly. >> >> When we try to send an image to this store we end up with the following >> error message: >> *"ERROR glance_store._drivers.swift.store - A value for >> swift_store_auth_address is required."* >> >> Here is the complete log trace: >> https://paste.opendev.org/show/bGeCJjSB1C5GwD6JYFvu/ >> >> I'm a bit surprised because according to the error message and the >> glance_store code it means that either my *default_swift_reference* or >> *auth_address *fromthe *default_swift_reference *isn't set. >> >> >> https://opendev.org/openstack/glance_store/src/branch/stable/victoria/glanc… >> >> However as you can see on my glance-api.conf file I've (seems so) >> correctly set the glance_store directive and the store settings: >> >> glance-api.conf: https://paste.opendev.org/show/bjFAPCjlCG6MqINGsIlK/ >> glance-swift.conf: https://paste.opendev.org/show/bcCfBQDj32T3qgiJj3P7/ >> >> I'm only using a single tenant glance container within the admin project. >> What's really weird is this issue still arise and exist with any known >> (to me) combination of configuration. >> >> I've tried to declare the store right within the glance-api.conf file, >> but it's not working. >> I've tried to declare the store right within the glance-api.conf file and >> with the deprecated swift_store_auth_address directive instead of the >> auth_address one, it's not working. >> I've tried to declare the store right within the glance-api.conf file and >> with the deprecated swift_store_auth_address directive plus the >> auth_address one, it's not working. >> I've tried to replace auth_address directive with the deprecated >> swift_store_auth_address within the glance-swift.conf, same error and issue >> again. >> >> When I replace the default_backend value with performance, uploading an >> image works perfectly. >> >> I know that my swift CEPH RGW backed endpoint works as I use it already >> to store data. I've even tried to push an image on it both using CLI >> (openstack object) and cURL API call and it works. >> I'm a bit lost here, so if anyone is having thoughts on this I would be >> happy to hear you! >> >> Thanks a lot everyone! >> > -- > Thanks & Best Regards, > > Abhishek Kekane >

2 6

[ops][heat][rbac] Call for feedback: Splitting stack to "system" stack and "project" stack
by Takashi Kajinami 24 May '22

24 May '22

Hello, tl;dr We are looking for some feedback from anyone developing their tool/software creating/managing heat stacks, about the new requirement we are considering. Recently we've been discussing the issue with Heat and Secure RBAC work[1]. The current target of SRBAC work requires the appropriate scope according to the resources. - Project resources like instance, volume or network can be created by project-scoped token - Project resources like flavor, user, project or role can be created by system-scoped token This is causing a problem with heat stacks which have both project resources and system resources, because heat currently uses the single token provided by the user in a single stack API call. As part of discussions we have discussed the "split stack" concept, which requires creating separate stacks per scope. This means If you want to create project resources and system resources by Heat, you should create two separate heat stacks and call heat stack api separately using different credentials. While we still need to investigate the feasibility of this option (eg. how smooth we can make the migration), we'd like to hear any feedback about the impact of the "split stack" concept on any external toolings depending on Heat, because this would require some workflow/architecture change in the toolings. If we hear many negative feedback/concerns then we would examine different approaches. Thank you, Takashi [1] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb…

1 1

[GLANCE][VICTORIA] - Multi-backend support with ceph backed swift.
by Gaël THEROND 24 May '22

24 May '22

Hi everyone, I'm currently enabling glance multi backend support for one of our platforms and we're facing a weird situation. This platform is a CentOS 8 Stream based Openstack VICTORIA and when we enable the multi-backends feature, the swift store isn't working properly. When we try to send an image to this store we end up with the following error message: *"ERROR glance_store._drivers.swift.store - A value for swift_store_auth_address is required."* Here is the complete log trace: https://paste.opendev.org/show/bGeCJjSB1C5GwD6JYFvu/ I'm a bit surprised because according to the error message and the glance_store code it means that either my *default_swift_reference* or *auth_address *fromthe *default_swift_reference *isn't set. https://opendev.org/openstack/glance_store/src/branch/stable/victoria/glanc… However as you can see on my glance-api.conf file I've (seems so) correctly set the glance_store directive and the store settings: glance-api.conf: https://paste.opendev.org/show/bjFAPCjlCG6MqINGsIlK/ glance-swift.conf: https://paste.opendev.org/show/bcCfBQDj32T3qgiJj3P7/ I'm only using a single tenant glance container within the admin project. What's really weird is this issue still arise and exist with any known (to me) combination of configuration. I've tried to declare the store right within the glance-api.conf file, but it's not working. I've tried to declare the store right within the glance-api.conf file and with the deprecated swift_store_auth_address directive instead of the auth_address one, it's not working. I've tried to declare the store right within the glance-api.conf file and with the deprecated swift_store_auth_address directive plus the auth_address one, it's not working. I've tried to replace auth_address directive with the deprecated swift_store_auth_address within the glance-swift.conf, same error and issue again. When I replace the default_backend value with performance, uploading an image works perfectly. I know that my swift CEPH RGW backed endpoint works as I use it already to store data. I've even tried to push an image on it both using CLI (openstack object) and cURL API call and it works. I'm a bit lost here, so if anyone is having thoughts on this I would be happy to hear you! Thanks a lot everyone!

1 0

[Monasca] correlating monasca-api metrics resource_id to instance id
by Ivo Palli 24 May '22

24 May '22

Hi all, I'm new to openstack and monasca. I've gotten so far as to retrieve instances with their ID's via the REST API, but I'm running into trouble with getting metrics. The issue is that metrics: - show to which hostname they belong - and you can limit results to a project id But if you have 2 or more servers with the same hostname, you can't link them 1:1 with an instance. Is there a way how I can get that 1:1 link? Regards, Ivo Palli

1 0