August 2022 - openstack-discuss - lists.openstack.org

[election][Neutron] PTL candidacy for Antelope cycle
by Rodolfo Alonso Hernandez 30 Aug '22

30 Aug '22

Hello all: I would like to announce my candidacy for the role of PTL of Neutron for the Antelope cycle. Let me introduce myself first. I started contributing to OpenStack in Liberty release (2015). I've contributed to several projects, mainly Neutron, neutron-lib, os-ken and os-vif, in addition to Nova and devstack. During the last two years I've been focused on the ML2/OVN integration, QoS and Placement related features and helping on the Neutron CI improvement and stabilization. For this new release, those are the main goals I would like to focus on: * Take care and focus on the approved and merged Neutron specs [1]. Those RFEs should be actively attended by the community, from the spec proposal to the code review. In order to increase the attention of the community on these new RFEs, new ways of tracking them should be proposed (a topic that should be discussed during the PTG). For example, having a core reviewer “godfather” for each RFE. * Continue with the improvement of CI stability. The job done during the last 2 or 3 releases has been impressive, probably the hardest and the most continued effort on the CI in the Neutron community ever. We *must* continue with this effort and the current processes to track the healthiness of the CI. * Start working on the smart NIC / hardware offload testing. The number of backends (ML2/OVS, ML2/OVN, ML2/SR-IOV) make non-viable to test any possible combination. But at least, depending on the available hardware, we would be able to test the stability of those backends with the newest hardware offload NICs. Note: that will imply an external CI support. * Work with users and operators, providing an active channel with them. The goal is to attract customers to be actively involved in the community, participating in the Neutron meetings (team meeting, CI meeting, drivers meeting) or even creating a specific meeting with them in order to capture new needs or issues. * Live migration improvement, specially in ML2/OVN. This feature is still being tested and has not proven to be very stable. There are several core OVN and Neutron efforts right now but we still need to make this feature stable enough to be delivered to customers. A part from those main goals, we should always keep an eye on: * The SQLAlchemy 2.0 migration and any possible issue detected. * The Neutron's stadium ecosystem alive and healthy: this is a permanent goal in any release. The Neutron ecosystem is wide and diverse and it is maintained with few resources. We should focus on those active projects and communities that support their respective repositories. * Still closing the ML2/OVS - ML2/OVN feature gap, that is smaller every cycle. Thank you in advance. Rodolfo Alonso Hernandez (ralonsoh, ralonsoh(a)redhat.com)

1 0

[TripleO] quay.io namespace local mirror using harbor. Quay.io do not list repos/images
by Ruslanas Gžibovskis 30 Aug '22

30 Aug '22

Hi all, I am trying to make a local repo/copy to be able to deploy OSP onsite behind firewall. I have found out from harbor, that Quay.io do not return repos/image anonymously also I have created account in quay.io with my RH account. Later reset quay.io password, so quay.io connection verify works. I can get it as a proxy, or exact image, but not full offline installation. Could you help/suggest any tool that could do a local repo? I have also tried foreman, but it only can sync repo in namespace, not whole namespace. Thank you for your advice and comments. -- Ruslanas Gžibovskis +370 6030 7030

2 1

[kolla] [nova] Rogue AggregateMultiTenancyIsolation filter
by Albert Braden 30 Aug '22

30 Aug '22

We're running kolla train, and we use the AggregateMultiTenancyIsolation for some aggregates by setting filter_tenant_id. Today customers reported build failures when they try to build VMs in a non-filtered region. I am able to duplicate the issue: os server create --image <image> --flavor medium --network private --availability-zone open alberttest1 | 5dd44105-2045-4d53-be43-5f521ddb420b | alberttest1 | ERROR | | <image> | medium | 2022-08-26 18:39:38.977 30 INFO nova.filters [req-342d065a-cd47-4edf-bc4b-3f84b34ab97c 25b53bdb96fb5f9f6e7331d7e03eee0a12c45746a9e8b978858b2140a5275a09 fdcf1553db504c8f82a2b54851a4c262 - 8793b235debf49e6aba6bd1e2bf65360 8793b235debf49e6aba6bd1e2bf65360] Filtering removed all hosts for the request with instance ID '5dd44105-2045-4d53-be43-5f521ddb420b'. Filter results: ['ComputeFilter: (start: 50, end: 50)', 'RetryFilter: (start: 50, end: 50)', 'AggregateNumInstancesFilter: (start: 50, end: 50)', 'AvailabilityZoneFilter: (start: 50, end: 6)', 'AggregateInstanceExtraSpecsFilter: (start: 6, end: 6)', 'ImagePropertiesFilter: (start: 6, end: 6)', 'ServerGroupAntiAffinityFilter: (start: 6, end: 6)', 'ServerGroupAffinityFilter: (start: 6, end: 6)', 'AggregateMultiTenancyIsolation: (start: 6, end: 0)'] Region "open" does not have any properties specified, so the AggregateMultiTenancyIsolation filter should not be active. qde3:admin]$ os aggregate show open|grep properties | properties | This is what we would see if it had the filter active: :qde3:admin]$ os aggregate show closed|grep properties | properties | filter_tenant_id='1c41e088b35f4b438023d081a6f70292,3e9727aaf03e4459a176c28dbdb3965e,f9b4b7dc8c614bb09d66657afc3b21cd,121a5da3dd0b489986908bee7eea61ae,d580ccc4b07e478a9efc2d71acf04cc1,107e14eeda01400988e58f5aac8b2772', closed='true' What could be causing this filter to remove hosts when we haven't set filter_tenant_id for that aggregate?

2 2

[cinder] This week's meeting will be in video+IRC
by Rajat Dhasmana 30 Aug '22

30 Aug '22

Hello Argonauts, As we keep last meeting of the month in video + IRC mode, this week's meeting (tomorrow) will be held in video + IRC mode with details as follows: Date: 31st August, 2022 Time: 1400 UTC Meeting link: https://bluejeans.com/556681290 IRC Channel: #openstack-meeting-alt Make sure you're connected to both the bluejeans meeting and IRC since we do roll call and also discuss topics on IRC (if the author is more comfortable in written format). Thanks and regards Rajat Dhasmana

1 0

[election][nova][placement] Candidating for the Antelope cycle.
by Sylvain Bauza 30 Aug '22

30 Aug '22

Hi Nova and Placement folks, Yet again, I want to help our community for this cycle by working on papers. If you accept me for being Antelope Nova/Placement PTL, it would be my last cycle for it after already two of them (unless nobody runs for this). For the moment, we are not yet done with Zed but I'm happy to see that we have 13 open blueprints that are reviewed and where some of them are from contributors that aren't everyday Nova developers. That's the reason why I wanted to help those on-off contributors that have not a large time for upstream work and that's why we added a Gerrit review label value for them (saying "I want to review as a contributor"). We also tried a new way for discussing about open changes creating a new API microversion and even if it hadn't really needed, I think we could use this way next time if needed. So, what would I like for us to discuss during Antelope then ? Well, at least three points : - given Antelope will be the first 'tick' release, I want to make sure we won't have any issues in Nova or Placement for this cycle, and I also would like to prepare for the 'tock' release. - I would like to discuss with our community how to find some opportunities for new contributors that would like to work on Nova. - as we discussed with operators in the Berlin Summit, I would like to find a way for them to discuss with us and see how they could be in our community even if they're not developers. At least, I'd love to see some operators in our meetings and in our PTG sessions. Thanks, -Sylvain (again, not a leader but just a herder.)

1 0

[all] [oslo.messaging] Interest in collaboration on a NATS driver
by Tobias Urdin 30 Aug '22

30 Aug '22

Hello, Please note that the list provided was just from my own notes and I didn’t put much emphasis on making it complete or accurate. If you think back to the early days of OpenStack the pain was in OpenStack itself, today it’s a challenge instead to manage OpenStack scale and fit into the things we see, like moving OpenStack into containers (for example managed by Kubernetes). I would like OpenStack design to more embrace the distributed, cloud-native approach that Ceph and Kubernetes brings, and the resiliency of Ceph (and yes, I’m a major Ceph enthusiast) and there I’m seeing messaging and database as potential blockers to continue on that path. I’m not saying that’s the only thing, for example stuff like [1] _really_ matter in real world deployments so working on other OpenStack parts for resilience is also crucial. There is things I’m interested in that would impact the overall design, I can list some of them but I think it might be to broad of a subject for this thread. * Like brought up my Mohammed Naser before, I would like to investigate an effort for containers as an OpenStack deliverable for projects * Investigate cloud-native, highly available and resilient alternatives for messaging and database * Make OpenStack more resilient with above and [1] is a great example on what I mean I’ll respond to your questions with my views inline below. P.S The opionions stated here is my own personal opinions and should not be assumed to be the opinions of any other entity. Best regards Tobias [1] https://bugs.launchpad.net/neutron/+bug/1987780 Begin forwarded message: From: Radosław Piliszek <radoslaw.piliszek(a)gmail.com<mailto:radoslaw.piliszek@gmail.com>> Subject: Re: [all] [oslo.messaging] Interest in collaboration on a NATS driver Date: 29 August 2022 at 18:33:15 CEST To: Tobias Urdin <tobias.urdin(a)binero.com<mailto:tobias.urdin@binero.com>> Cc: openstack-discuss <openstack-discuss(a)lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>> Hi Tobias, Good to see RMQ alternatives appearing. A couple of questions from me. On Mon, 29 Aug 2022 at 15:47, Tobias Urdin <tobias.urdin(a)binero.com<mailto:tobias.urdin@binero.com>> wrote: • Do retries and acknowledgements in the library (since NATS does NOT persist messages like RabbitMQ could) What do you mean? Is NATS only a router? (I have not used this technology yet.) It does not persist messages, if there is no backend to respond, the message will be dropped without any action hence why I want the RPC layer in oslo.messaging (that already does acknowledge calls in the driver) to notify client side that it’s being processed before client side waits for reply. • Find or maintain a NATS python library that doesn't use async like the official one does Why is async a bad thing? For messaging it's the right thing. This is actually just myself, I would love to just being able to use the official that is async based instead it’s just me that doesn’t understand how that would be implemented. https://github.com/nats-io/nats.py instead of the one in POC https://github.com/Gr1N/nats-python which has a lot of shortcomings and issues, my idea was just to investigate if was even possible to implement in a feasible way. Finally, have you considered just trying out ZeroMQ? Does not exist anymore. I mean, NATS is probably an overkill for OpenStack services since the majority of them stay static on the hosts they control (think nova-compute, neutron agents - and these are also the pain points that operators want to ease). I don’t think it it, or even if it is, why not use a better solution or stable approach than RabbitMQ? This is also the whole point, I don’t want OpenStack to become or be static, I want it to be more dynamic and cloud-native in it’s approach and support viable integrations that takes it there, we cannot live in the past forever, let’s envision and dream of the future as we want it! :) NATS seems to me to cater for a different use case. It actually caters to a lot of use cases. I might be wrong because I have read only the front page but that is the feeling I have. Cheers, Radek -yoctozepto Begin forwarded message: From: Radosław Piliszek <radoslaw.piliszek(a)gmail.com<mailto:radoslaw.piliszek@gmail.com>> Subject: Re: [all] [oslo.messaging] Interest in collaboration on a NATS driver Date: 29 August 2022 at 20:20:15 CEST To: Sean Mooney <smooney(a)redhat.com<mailto:smooney@redhat.com>> Cc: Tobias Urdin <tobias.urdin(a)binero.com<mailto:tobias.urdin@binero.com>>, openstack-discuss <openstack-discuss(a)lists.openstack.org<mailto:openstack-discuss@lists.openstack.org>> On Mon, 29 Aug 2022 at 20:03, Sean Mooney <smooney(a)redhat.com<mailto:smooney@redhat.com>> wrote: Finally, have you considered just trying out ZeroMQ? ZeroMQ used to be supported in the past but then it was remvoed if i understand correctly it only supprot notificaiton or RPC but not both i dont recall which but perhapse im miss rememebrign on that point. I believe it would be better suited for RPC than notifications, at least in the simplest form. As it’s advertised as scalable and performant I would argue that, why not use it for notifications as well? If anything according to your observations above it’s more suited for that than RPC, even though request-reply (that we can use for RPC) is a strong first-class implementation in NATS as well. I mean, NATS is probably an overkill for OpenStack services since the majority of them stay static on the hosts they control (think nova-compute, neutron agents - and these are also the pain points that operators want to ease). its not any more overkill then rabbitmq is True that. Probably. I agree with that, also if you think about it, how many issues related to stability, performance and outages is related to RabbitMQ? It’s quite a few if you ask me. Just the resource utilization and clustering in RabbitMQ makes me feel bad. It’s here that I mean that the cloud-native and scalable implementation would shine, you should be able to rely on it, if sometimes dies so what, things should just continue to work and that’s not my experience with RabbitMQ but it is my experience with Ceph because in the end the design really matters. i also dont know waht you mean when you say "majority of them stay static on the hosts they control" NATS is intended a s a cloud native horrizontally scaleable message bus. which is exactly what openstack need IMO. NATS seems to be tweaked for "come and go" situations which is an exception in the OpenStack world, not the rule (at least in my view). I mean, one normally expects to have a preset number of hypervisors and not them coming and going (which, I agree, is a nice vision, could be a proper NATS driver, with more awareness in the client projects I believe, would be an enabler for more dynamic clouds). It could, but it also doesn’t have to be that. Why not strive for more dynamic? I don’t think anybody would argue that more dynamic is a bad thing even if you were to have a more static approach to your cloud. Cheers, Radek -yoctozepto

2 2

[publiccloud-sig] Bi-weekly meeting reminder
by Tobias Rydberg 30 Aug '22

30 Aug '22

Hi all, Tomorrow we will have our bi-weekly meeting at 0800 UTC in #openstack-operators. Agenda can be fond here [0]. Feel free to suggest topics to the agenda if you like. Hope to chat with you tomorrow! [0] https://etherpad.opendev.org/p/publiccloud-sig-meeting BR, Tobias Rydberg

1 0

RE: Openstack OVN (Open Virtual Network) HA deployment - running OVN in active/passive mode?
by 박경원 30 Aug '22

30 Aug '22

1 0

[infra][puppet] Old mirror contents in apt-puppetlabs
by Takashi Kajinami 30 Aug '22

30 Aug '22

Hello Infra team, I noticed the contents in the apt-puppetlabs directory in our CI mirror are old. The mirror repository provides puppet 6.23 while the upstream repository provides newer versions such as 6.28. Recently we bumped puppetlabs-mysql in our CI to 13.0.0 which requires puppet >= 6.24.0 and our Ubuntu jobs are failing now at a quite early stage because of the old puppet package. May someone please look into this ? I've checked mirror.iad3.inmotion.opendev.org and mirror.bhs1.ovh.opendev.org but it seems the contents in the directory have not been synced since July, 2021. Thank you, Takashi

2 3

Skyline apiserver can't connect to keystone and given error endpoint not found
by mahdi n 29 Aug '22

29 Aug '22

Skyline apiserver can't connect to keystone and given endpoint not found I install skyline api server and console But Apiserver get error : endpoint not found I attached pictures of this problem Please help me

1 1

[all][elections][ptl][tc] Combined PTL/TC antelope cycle Election Nominations Last Days
by Amy Marrich 29 Aug '22

29 Aug '22

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Aug 31, 2022 23:45 UTC. Should we find that many of the community members were off on vacation this date may get extended pushing the elections out. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2022-08-24 23:45:00 UTC Nominations end @ 2022-08-31 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 2 days, 5:50:21 Nominations progress : 67.95% --------------------------------------------------- Projects[1] : 52 Projects with candidates : 5 ( 9.62%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 47 (Adjutant Barbican Blazar Cinder Cloudkitty Cyborg Designate Freezer Glance Heat Horizon Ironic Keystone Manila Masakari Mistral Monasca Murano Neutron Nova Octavia OpenStackAnsible OpenStackSDK OpenStack_Charms OpenStack_Helm Openstack_Chef Oslo Puppet_OpenStack Quality_Assurance Rally Release_Management Requirements Sahara Senlin Skyline Solum Storlets Swift Tacker Telemetry Tripleo Trove Venus Vitrage Watcher Zaqar Zun) =================================================== Stats gathered @ 2022-08-29 17:54:39 UTC This means that with approximately 2 days left, 47 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[tacker][elections] PTL candidacy for Antelope cycle
by Yasufumi Ogawa 29 Aug '22

29 Aug '22

Hi, I'd like to propose my candidacy for Tacker PTL for Antelope cycle. I have contributed to Tacker as a PTL from Victoria for providing the latest features of ETSI-NVF standard features to enable operators to deploy their services. In the latest cycles, we have developed several supports for deploying CNFs, multi-version APIs for mixed environment of legacy and cutting edge-products provided by several vendors and more. We also have had several collaborative sessions with ETSI NFV for accelerating each activity of standardization and deployment of required features. In the next release, I would like to focus our target more on to develop features for reliability and avairability such as monitoring physical resources in addition to VMs and containers. Best regards, Yasufumi (yasufum)

1 0

[TripleO Wallaby] - Multi-attach Volume showing different files
by Lokendra Rathour 29 Aug '22

29 Aug '22

Hi Team, On TripleO Wallaby deployment, I have tried creating multi-attach type volume, which if I am attaching this volume to two VM, it is getting attached. After mounting the same in each VM, if I am creating the folders in one VM at the mount path, I am not seeing the same on the other VM at the mount path [image: image.png] Ideally if the backend volume is same and if I am understanding the idea correctly, then the content should be same in both the location, as the back is same. Checking at horizon I also see that Volume is showing attached to both the VMs. [image: image.png] Document followed to create this: https://docs.openstack.org/cinder/latest/admin/volume-multiattach.html Please advice -- ~ Lokendra skype: lokendrarathour

3 4

[Neutron] How to add Fake ML2 extension to Neutron?
by Igor Zhukov 29 Aug '22

29 Aug '22

Hi all! Sorry for a complete noob question but I can't figure it out 😿 So if I want to add Fake ML2 extension what should I do? I have neutron server installed and I have the file: https://github.com/openstack/neutron/blob/master/neutron/tests/unit/plugins… How to configure neutron server, where should I put the file, should I create another files? How can I test that it works?

2 7

[xena][placement] Xena placement upgrade leads to 500 on ubuntu focal
by CHANU ROMAIN 29 Aug '22

29 Aug '22

Hello, I just did upgrade my Placement to Xena on Ubuntu Focal (20.04). When I tried to start the process I got this error and all HTTP requests receive an HTTP 500 error: 2022-08-19 15:05:43.960573 2022-08-19 15:05:43.960 43 INFO placement.requestlog [req-f4c4d4f1-5d59-49d3-aa3e-1e8a09fe02fe 3ec54dee59424109913d4628ae8dac4c 19e62bc767484849a2763937883a256e - default default] 192.168.236.5 "GET /resource_providers/791c09ed-57f3- 4bfc-9278-4af6c5c137d8/allocations" status: 500 len: 244 microversion: 1.0\x1b[00m 2022-08-19 15:05:44.094951 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap [req-527dce52-c207-43ee-80f2-016a6f031cf5 3ec54dee59424109913d4628ae8dac4c 19e62bc767484849a2763937883a256e - default default] Placement API unexpected error: unsupported callable: TypeError: unsupported callable 2022-08-19 15:05:44.094973 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap Traceback (most recent call last): 2022-08-19 15:05:44.094977 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 1135, in getfullargspec 2022-08-19 15:05:44.094980 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap sig = _signature_from_callable(func, 2022-08-19 15:05:44.094998 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 2233, in _signature_from_callable 2022-08-19 15:05:44.095001 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap sig = _signature_from_callable( 2022-08-19 15:05:44.095004 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 2304, in _signature_from_callable 2022-08-19 15:05:44.095007 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _signature_from_function(sigcls, obj, 2022-08-19 15:05:44.095010 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 2168, in _signature_from_function 2022-08-19 15:05:44.095013 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap parameters.append(Parameter(name, annotation=annotation, 2022-08-19 15:05:44.095015 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 2491, in __init__ 2022-08-19 15:05:44.095018 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap self._kind = _ParameterKind(kind) 2022-08-19 15:05:44.095021 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap RecursionError: maximum recursion depth exceeded 2022-08-19 15:05:44.095024 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap 2022-08-19 15:05:44.095026 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap The above exception was the direct cause of the following exception: 2022-08-19 15:05:44.095029 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap 2022-08-19 15:05:44.095032 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap Traceback (most recent call last): 2022-08-19 15:05:44.095035 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/fault_wrap.py", line 39, in __call__ 2022-08-19 15:05:44.095038 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return self.application(environ, start_response) 2022-08-19 15:05:44.095040 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/dec.py", line 129, in __call__ 2022-08-19 15:05:44.095043 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap resp = self.call_func(req, *args, **kw) 2022-08-19 15:05:44.095046 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/dec.py", line 193, in call_func 2022-08-19 15:05:44.095049 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return self.func(req, *args, **kwargs) 2022-08-19 15:05:44.095052 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/microversion_parse/middleware.py", line 80, in __call__ 2022-08-19 15:05:44.095055 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap response = req.get_response(self.application) 2022-08-19 15:05:44.095057 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/request.py", line 1313, in send 2022-08-19 15:05:44.095060 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap status, headers, app_iter = self.call_application( 2022-08-19 15:05:44.095063 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/request.py", line 1278, in call_application 2022-08-19 15:05:44.095065 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap app_iter = application(self.environ, start_response) 2022-08-19 15:05:44.095068 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/handler.py", line 215, in __call__ 2022-08-19 15:05:44.095071 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return dispatch(environ, start_response, self._map) 2022-08-19 15:05:44.095074 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/handler.py", line 149, in dispatch 2022-08-19 15:05:44.095077 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return handler(environ, start_response) 2022-08-19 15:05:44.095083 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/dec.py", line 129, in __call__ 2022-08-19 15:05:44.095086 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap resp = self.call_func(req, *args, **kw) 2022-08-19 15:05:44.095089 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/wsgi_wrapper.py", line 29, in call_func 2022-08-19 15:05:44.095092 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap super(PlacementWsgify, self).call_func(req, *args, **kwargs) 2022-08-19 15:05:44.095094 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/webob/dec.py", line 193, in call_func 2022-08-19 15:05:44.095097 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return self.func(req, *args, **kwargs) 2022-08-19 15:05:44.095100 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/util.py", line 64, in decorated_function 2022-08-19 15:05:44.095103 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return f(req) 2022-08-19 15:05:44.095106 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/placement/handlers/allocation.py", line 299, in list_for_resource_provider 2022-08-19 15:05:44.098861 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098864 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098867 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098870 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098873 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098876 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098893 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098896 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098899 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098905 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098907 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.098910 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.098913 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098916 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098919 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.098922 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.098925 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098928 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098930 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098933 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098936 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098939 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098941 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098944 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098947 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098950 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098952 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.098955 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.098958 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098960 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098963 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.098966 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.098968 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098971 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098974 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098977 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098980 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098982 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098985 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 211, in __call__ 2022-08-19 15:05:44.098991 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap if _check(rule, target, cred, enforcer, current_rule): 2022-08-19 15:05:44.098993 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 80, in _check 2022-08-19 15:05:44.098996 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return rule(*rule_args) 2022-08-19 15:05:44.098999 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 255, in __call__ 2022-08-19 15:05:44.099002 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap return _check( 2022-08-19 15:05:44.099004 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3/dist- packages/oslo_policy/_checks.py", line 75, in _check 2022-08-19 15:05:44.099007 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap argspec = inspect.getfullargspec(rule.__call__) 2022-08-19 15:05:44.099010 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap File "/usr/lib/python3.8/inspect.py", line 1144, in getfullargspec 2022-08-19 15:05:44.099013 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap raise TypeError('unsupported callable') from ex 2022-08-19 15:05:44.099016 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap TypeError: unsupported callable 2022-08-19 15:05:44.099018 2022-08-19 15:05:44.077 46 ERROR placement.fault_wrap \x1b[00m Placement-api is deployed in a container, so I got a fresh policy.yaml file. Did someone already face this? Do you have any idea how to fix this? Best regards, Romain

3 3

[Triple0] [Wallaby] External Ceph Integration getting failed
by Lokendra Rathour 29 Aug '22

29 Aug '22

Hi Team, I was trying to integrate External Ceph with Triple0 Wallaby, and at the end of deployment in step4 getting the below error: 2022-08-03 18:37:21,158 p=507732 u=stack n=ansible | 2022-08-03 18:37:21.157962 | 525400fe-86b8-65d9-d100-0000000080d2 | TASK | Create containers from /var/lib/tripleo-config/container-startup-config/step_4 2022-08-03 18:37:21,239 p=507732 u=stack n=ansible | 2022-08-03 18:37:21.238718 | 69e98219-f748-4af7-a6d0-f8f73680ce9b | INCLUDED | /usr/share/ansible/roles/tripleo_container_manage/tasks/create.yml | overcloud-controller-2 2022-08-03 18:37:21,273 p=507732 u=stack n=ansible | 2022-08-03 18:37:21.272340 | 525400fe-86b8-65d9-d100-0000000086d9 | TASK | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_4 2022-08-03 18:37:24,532 p=507732 u=stack n=ansible | 2022-08-03 18:37:24.530812 | | WARNING | ERROR: Can't run container nova_libvirt_init_secret stderr: 2022-08-03 18:37:24,533 p=507732 u=stack n=ansible | 2022-08-03 18:37:24.532811 | 525400fe-86b8-65d9-d100-0000000082ec | FATAL | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_4 | overcloud-novacompute-0 | error={"changed": false, "msg": "Failed containers: nova_libvirt_init_secret"} 2022-08-03 18:37:44,282 p=507732 u *external-ceph.conf:* parameter_defaults: # Enable use of RBD backend in nova-compute NovaEnableRbdBackend: True # Enable use of RBD backend in cinder-volume CinderEnableRbdBackend: True # Backend to use for cinder-backup CinderBackupBackend: ceph # Backend to use for glance GlanceBackend: rbd # Name of the Ceph pool hosting Nova ephemeral images NovaRbdPoolName: vms # Name of the Ceph pool hosting Cinder volumes CinderRbdPoolName: volumes # Name of the Ceph pool hosting Cinder backups CinderBackupRbdPoolName: backups # Name of the Ceph pool hosting Glance images GlanceRbdPoolName: images # Name of the user to authenticate with the external Ceph cluster CephClientUserName: admin # The cluster FSID CephClusterFSID: 'ca3080-aaaa-4d1a-b1fd-4aaaa9a9ea4c' # The CephX user auth key CephClientKey: 'AQDgRjhiuLMnAxAAnYwgERERFy0lzH6ufSl70A==' # The list of Ceph monitors CephExternalMonHost: 'abcd:abcd:abcd::11,abcd:abcd:abcd::12,abcd:abcd:abcd::13' ~ Have tried checking and validating the ceph client details and they seem to be correct, further digging the container log I could see something like this : [root@overcloud-novacompute-0 containers]# tail -f nova_libvirt_init_secret.log tail: cannot open 'nova_libvirt_init_secret.log' for reading: No such file or directory tail: no files remaining [root@overcloud-novacompute-0 containers]# tail -f stdouts/nova_libvirt_init_secret.log 2022-08-04T11:48:47.689898197+05:30 stdout F ------------------------------------------------ 2022-08-04T11:48:47.690002011+05:30 stdout F Initializing virsh secrets for: ceph:admin 2022-08-04T11:48:47.690590594+05:30 stdout F Error: /etc/ceph/ceph.conf was not found 2022-08-04T11:48:47.690625088+05:30 stdout F Path to nova_libvirt_init_secret was ceph:admin 2022-08-04T16:20:29.643785538+05:30 stdout F ------------------------------------------------ 2022-08-04T16:20:29.643785538+05:30 stdout F Initializing virsh secrets for: ceph:admin 2022-08-04T16:20:29.644785532+05:30 stdout F Error: /etc/ceph/ceph.conf was not found 2022-08-04T16:20:29.644785532+05:30 stdout F Path to nova_libvirt_init_secret was ceph:admin ^C [root@overcloud-novacompute-0 containers]# tail -f stdouts/nova_compute_init_log.log -- ~ Lokendra skype: lokendrarathour

3 10

[nova] Changes for out-of-tree drivers
by Rajat Dhasmana 29 Aug '22

29 Aug '22

Hi, I'm working on a nova feature which adds support for rebuilding volume backed instances which modifies the arguments for 'rebuild' method. It adds a 'reimage_boot_volume' parameter which signifies if the user has requested a rebuild operation for a volume backed instance. Currently it is only implemented by the ironic driver in the in-tree drivers. If you're a maintainer of an out of tree driver then you will need to account for it. Thanks and regards Rajat Dhasmana

1 1

Lagging of vm
by Naveen j 29 Aug '22

29 Aug '22

Hi Team. When i create a vm, my vms are lagging so much when I run any application in ubuntu Regards Naveen j

2 2

Questions about High Availability setup
by 박경원 29 Aug '22

29 Aug '22

5 6

[requirement][all] Nose being removed from Debian and Ubuntu: let's remove it from our global requirements
by Thomas Goirand 29 Aug '22

29 Aug '22

Hi, It's no surprise for anyone that's been following it: Nose was deprecated years ago, and now, we're trying to remove it from Debian. Therefore, 49 bugs were filled against the Debian OpenStack package. It'd be nice if upstream OpenStack was also following this move, and removing nose from global-requirements. I'm not sure if it'd be a big deal if that wasn't the case, as I could use a different test runner in Debian, but I very much would prefer if it was the case. Probably Ubuntu will follow the same path, since Nose isn't in main (it's in Universe, meaning Debian maintained...). Your thoughts? Cheers, Thomas Goirand (zigo)

2 1

[neutron] Bug deputy report - week of 22 Aug
by Slawek Kaplonski 29 Aug '22

29 Aug '22

Hi, I was Neutron's bug deputy last week. Here is summary of what happend during this time: ## Critical https://bugs.launchpad.net/neutron/+bug/1987308 - [ovn-octavia-provider] ovn compilation is failing in "ovn-octavia-provider-tempest-master " job - assigned to Fernando, patch proposed https://review.opendev.org/c/openstack/ovn-octavia-provider/+/854008 ## High https://bugs.launchpad.net/neutron/+bug/1987530 - Duplicate external_ip in NAT table lead to loss of N/S connectivity - needs attention ## Medium https://bugs.launchpad.net/neutron/+bug/1987396 - masquerading behavior changed between queens and train - assigned to David Hill, patch proposed already: https://review.opendev.org/c/openstack/neutron/+/854041 https://bugs.launchpad.net/neutron/+bug/1987780 - Nova notifications with error response are not retried - assigned to Szymon Wróblewski https://bugs.launchpad.net/neutron/+bug/1987666 - Race condition when adding two subnet with same cidr to router - unassigned currently ## Low https://bugs.launchpad.net/neutron/+bug/1987281 - Create a method to add multiple IP addresses in one call - assigned to Rodolfo https://bugs.launchpad.net/neutron/+bug/1988026 - Neutron should not create security group with project==None - needs assignment, it seems like low hanging fruit bug to fix for me, ## Whishlist (RFEs) https://bugs.launchpad.net/neutron/+bug/1987378 - [RFE] Add DSCP mark 44 - assigned to Rodolfo, marked by him as an RFE but I don't really think we need to discuss and approve it in the drivers meeting. We discussed that during last drivers meeting and it's already triaged. ## Incomlete https://bugs.launchpad.net/neutron/+bug/1987377 - neutron-metadata-agent the memory usage is increasing, Lajos and Oleg already have some comments on that one, ## Needs attention https://bugs.launchpad.net/cloud-init/+bug/1899487 - cloud-init hard codes MTU configuration at initial deploy time - bug which was reported for cloud-init first but now after long discussion it's on Neutron and we need to check it, -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Openstack OVN (Open Virtual Network) HA deployment - running OVN in active/passive mode?
by 박경원 29 Aug '22

29 Aug '22

1 0

[neutron][elections] PTL non-candidacy for Antelope cycle
by Lajos Katona 29 Aug '22

29 Aug '22

Hi, It was a great pleasure and honor to be Neutron PTL for 2 cycles, thanks everybody for the help and support during this time (actually not just for these cycles but for all). It's not just smoke and ruins around networking after my PTLship, so after all I would say it was a success :-) My main focus was to keep the Neutron team as encouraging and inclusive as possible and work on cooperation with new contributor groups and even with other projects of whom we are consuming in Openstack. It is time to change and allow new ideas and energies to form Networking. I remain and I hope I can help the community in the next cycles also. Cheers Lajos Katona

10 9

Re: container and instances are not working on my dashboard
by test 28 Aug '22

28 Aug '22

1 0

containers ad instances are not working
by Lee, Vincent Z 28 Aug '22

28 Aug '22

[https://res.cdn.office.net/assets/mail/file-icon/png/txt_16x16.png]nova-com… 1.log<https://iowastate-my.sharepoint.com/:u:/g/personal/vincet_iastate_edu/EWerz…> Hi all, I am quite new to Openstack and faced some issues with creating instances and displaying created containers on my Openstack dashboard. I am currently working on multinode Openstack. I am hoping to get some helps and feedbacks about this. I will briefly go through the problems I encountered. When I created an instances on my dashboard, it directly went into error state. I have attached a screenshot as shown below. [cid:6d3cb41a-9176-4209-8e12-d669e05ecf5b] This is my list of hosts. [cid:11a45ab0-b7f8-4c79-a619-131d01121687] When I created a container using both cli and dashboard, two containers were running. However, when I tried to look into my dashboard, those containers were not shown. These are the created containers. [cid:1b05b862-8e1d-4833-a3e0-57b921fd6351] However, when i try to open my dashboard and look for them, they just don't appear on it. So I am not sure what is causing this. [cid:0eff5e44-5690-4590-9682-43410e2d52f1] The version of my Openstack deployment is 21.2.4. I deployed my Openstack using the master branch (latest). I have followed the guidelines provided online (https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html) which uses kolla-ansible. In my /var/log/kolla/zun/ directory, I have only a total of six different log files. [cid:4b28ae60-c42a-4cd4-a063-49431d8b5334] I have attached a sample of my globals.yml, multinode, zun-api and compute-api log file in this email. The below image is a sample of how I setup my openstack as shown below. [cid:8cc989cd-b334-4647-8084-048b499e229e] The below image is the reference of my local network. My controller [cid:6e322de9-216e-48c6-b0a2-7cd3f2465ba1] [cid:4695cd8c-a01c-45b5-9523-e9b9f95a9ebc] [cid:0426c49b-701d-4a9b-aadc-ea9353840f66] [cid:f1e89ed4-fc88-4679-bcb5-0150bef1fd7a] [cid:51c37875-f354-4f18-8a83-619ddb2c19d5] My compute host [cid:aad2498a-52f7-4f81-9c57-cdb49f52de4c] [cid:83c1a81e-342a-4ec0-9d94-c73753152087] Hope to hear from everyone soon. Best regards, Vincent

2 1

[nova] Could I boot instance from volume snapshot in cmd?
by 韩光宇 28 Aug '22

28 Aug '22

Hello, I want boot instance from volume snapshot in cmd, but I never found it in `openstack server create --help` and https://docs.openstack.org/nova/latest/user/launch-instances.html. Could I do it in cmd? I saw that this can be done on horizon Thanks, Han Guangyu

2 1

[heat] ERROR: You are not authorized to use stacks:global_index.
by Boxiang Zhu 28 Aug '22

28 Aug '22

Hi, I deployed the openstack with kolla-ansible. And the openstack_release of globals.yml is master. The version of openstackclient and heatclient is 5.8.0 and 3.0.0. I run command "source /etc/kolla/admin-openrc.sh" to export env of openstack. OS_PROJECT_DOMAIN_NAME=Default OS_USER_DOMAIN_NAME=Default OS_PROJECT_NAME=admin OS_TENANT_NAME=admin OS_USERNAME=admin OS_PASSWORD=xxxxxxxxx OS_AUTH_URL=http://192.168.100.10:5000 OS_INTERFACE=internal OS_ENDPOINT_TYPE=internalURL OS_MANILA_ENDPOINT_TYPE=internalURL OS_IDENTITY_API_VERSION=3 OS_REGION_NAME=RegionOne OS_AUTH_PLUGIN=password Then I try to list all stacks with command "openstack stack list --all-projects". But I got the error messages as followed: ERROR: You are not authorized to use stacks:global_index. I see the policy is "role:reader and system_scope:all". I think the user admin has role reader and also with system_scope:all. ❯ openstack role assignment list +----------------------------------+----------------------------------+-------+----------------------------------+----------------------------------+--------+-----------+ | Role | User | Group | Project | Domain | System | Inherited | +----------------------------------+----------------------------------+-------+----------------------------------+----------------------------------+--------+-----------+ | cd572da356fb4f7ca53c280802299eb0 | fccbdf34d33a407db1b53bed048d1187 | | 840500fb441a442fbcbca30d3a773b2c | | | False | | cd572da356fb4f7ca53c280802299eb0 | 70d3715e7e2246c08c901d0e96038443 | | | 0a6274ff7f994e8cb6f40e13b0d39ca2 | | False | | cd572da356fb4f7ca53c280802299eb0 | 5c100e870cbd4744af6e546fc9215a37 | | | | all | False | +----------------------------------+----------------------------------+-------+----------------------------------+----------------------------------+--------+-----------+ ❯ openstack user show admin +---------------------+----------------------------------+ | Field | Value | +---------------------+----------------------------------+ | domain_id | default | | enabled | True | | id | 5c100e870cbd4744af6e546fc9215a37 | | name | admin | | options | {} | | password_expires_at | None | +---------------------+----------------------------------+ How can I get all the stacks for all projects? Thanks, Best Regards, Boxiang Zhu

2 1

What is the Traffic Flow between Horizon and Swift?
by John van Ommen 27 Aug '22

27 Aug '22

When a user is using Horizon, and they're examining the contents of their containers in Swift, what does the traffic flow look like? I am unable to browse the contents of my Swift containers from Horizon. When I click on the contents of the container I get: "Unable to get the objects in the container" And when I click on the "Services" tab in Horizon, I get: "Unable to get Nova services list" and "Unable to get Cinder services list" John van Ommen

1 0

[Wallaby] Deployment getting failed Randomly
by Lokendra Rathour 27 Aug '22

27 Aug '22

Hi Team, we were trying to deploy OpenStack wallaby, and we see that 4 out of 5 runs deployment is getting failed for mentioned below reasons: *Error:* 2022-08-25 17:34:29.036371 | 5254004d-021e-d4db-067d-000000007b1a | TASK | Create identity internal endpoint 2022-08-25 17:34:31.176105 | 5254004d-021e-d4db-067d-000000007b1a | FATAL | Create identity internal endpoint | undercloud | error={"changed": false, "extra_data": {"data": null, "details": "The request you have made requires authentication.", "response": "{\"error\":{\"code\":401,\"message\":\"The request you have made requires authentication.\",\"title\":\"Unauthorized\"} }\n"}, "msg": "Failed to list services: Client Error for url: overcloud-public.myhsc.com <https://overcloud-public.myhsc.com:13000/v3/services> :13000/v3/services <https://overcloud-public.myhsc.com:13000/v3/services>, The request you have made requires authentication."} Debug logs: pending results.... The full traceback is: File "/tmp/ansible_openstack.cloud.endpoint_payload_qhlqb_qw/ansible_openstack.cloud.endpoint_payload.zip/ansible_collections/open stack/cloud/plugins/module_utils/openstack.py", line 407, in __call__ results = self.run() File "/tmp/ansible_openstack.cloud.endpoint_payload_qhlqb_qw/ansible_openstack.cloud.endpoint_payload.zip/ansible_collections/open stack/cloud/plugins/modules/endpoint.py", line 150, in run File "/usr/lib/python3.6/site-packages/openstack/cloud/_identity.py", line 537, in get_service return _utils._get_entity(self, 'service', name_or_id, filters) File "/usr/lib/python3.6/site-packages/openstack/cloud/_utils.py", line 197, in _get_entity entities = search(name_or_id, filters, **kwargs) File "/usr/lib/python3.6/site-packages/openstack/cloud/_identity.py", line 517, in search_services services = self.list_services() File "/usr/lib/python3.6/site-packages/openstack/cloud/_identity.py", line 501, in list_services error_message="Failed to list services") File "/usr/lib/python3.6/site-packages/keystoneauth1/adapter.py", line 395, in get return self.request(url, 'GET', **kwargs) File "/usr/lib/python3.6/site-packages/openstack/proxy.py", line 668, in request return _json_response(response, error_message=error_message) File "/usr/lib/python3.6/site-packages/openstack/proxy.py", line 646, in _json_response exceptions.raise_from_response(response, error_message=error_message) File "/usr/lib/python3.6/site-packages/openstack/exceptions.py", line 238, in raise_from_response http_status=http_status, request_id=request_id 2022-08-25 19:38:03.201899 | 5254004d-021e-7578-cd65-000000007ad6 | FATAL | Create identity internal endpoint | undercloud | er ror={ "changed": false, "extra_data": { "data": null, "details": "The request you have made requires authentication.", "response": "{\"error\":{\"code\":401,\"message\":\"The request you have made requires authentication.\",\"title\":\"Unautho rized\"}}\n" }, "invocation": { "module_args": { "api_timeout": null, "auth": null, "auth_type": null, "availability_zone": null, "ca_cert": null, "client_cert": null, "client_key": null, "enabled": true, "endpoint_interface": "internal", "interface": "public", "region": "regionOne", "region_name": null, "service": "keystone", "state": "present", "timeout": 180, "url": "http://[fd00:fd00:fd00:2000::368]:5000", "validate_certs": null, "wait": true } }, "msg": "Failed to list services: Client Error for url: https://overcloud-public.myhsc.com:13000/v3/services, The request you have made requires authentication." } DeployCommand that was used: openstack overcloud deploy --templates \ -r /home/stack/templates/roles_data.yaml \ -n /home/stack/templates/custom_network_data.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-conductor.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-overcloud.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ptp.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/tls-endpoints-public-dns.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/inject-trust-anchor-hiera.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/external-ceph.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \ -e /home/stack/templates/overcloud-baremetal-deployed.yaml \ -e /home/stack/templates/networks-deployed-environment.yaml \ -e /home/stack/templates/vip-deployed-environment.yaml \ -e /home/stack/templates/environment.yaml \ -e /home/stack/templates/ironic-config.yaml \ -e /home/stack/templates/enable-tls.yaml \ -e /home/stack/templates/cloudname.yaml \ -e /home/stack/templates/my-additional-ceph-settings.yaml \ -e /home/stack/containers-prepare-parameter.yaml [Issue] we are seeing the deployment is working perfectly once and the same setting is not working perfectly in the second run. the failure rate is high. what can be the reasons behind this? *Note:* Before this, we were deploying with DNS and SSL and it was perfectly working fine in multiple reruns. But after SSL we have seen this random failure. -- ~ Lokendra skype: lokendrarathour

1 1

question about skyline apiserver and console
by mahdi n 27 Aug '22

27 Aug '22

Hello, I want to install ui skyline but I don't know how to install Does the first install the skyline api server next console? or only install skyline console ui? where must I set the keystone url ? skyline have not docs fir develop please help

3 3

[all][tc] What's happening in Technical Committee: summary 2022 Aug 26: Reading: 5 min
by Ghanshyam Mann 26 Aug '22

26 Aug '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 25. Most of the meeting discussions are summarized in this email. Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-08-25-15.00.log.html * Next TC weekly meeting will be on Sept 1 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 31. 2. What we completed this week: ========================= * Retired openstack-helm-addons[2] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], Two are completed and others items are in-progress. Open Reviews ----------------- * Six open reviews for ongoing activities[4]. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- Nomination for the technical election (PTL and Technical Committee) are open now[5]. We are 1 week delay in election so as per TC charter we are adding this delay as exception[6]. Request you to add your nomination before Aug 31 and also ping anyone you know is interested in the PTL or TC position. Define 2023.1 cycle testing runtime ------------------------------------------- I have proposed the testing runtime for the 2023.1 cycle[7], please review and feedback if any. 2023.1 cycle TC PTG planning ------------------------------------ I have started the PTG planning for the TC sessions. * Similar to last coupe of PTG, we are planning "TC + Leader interaction" sessions[8], please vote your available day/time in poll[8]. * I have created the etherpad[10] to collect the TC slots topics and poll to select the TC slot timing[11]. * As you know, we are planning 'Operator Hours' in this PTG where developer and operator and meet for an hour to discuss/feedback. There is a poll to know if operator want to join developer PTG slot of interested to have their own space and let developer jump in there for discussion[12] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[13]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [14] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[15]16]. Project updates ------------------- * Switch requirements to distributed leadership[17] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [19] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/851859 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030094.… [6] https://review.opendev.org/c/openstack/governance/+/854624 [7] https://review.opendev.org/c/openstack/governance/+/854375 [8] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030108.… [9] https://framadate.org/zsOqRxfVcmtjaPBC [10] https://etherpad.opendev.org/p/tc-2023-1-ptg [11] https://framadate.org/yi8LNQaph5wrirks [12] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030114.… [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] https://review.opendev.org/c/openstack/governance/+/849606 [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [17] https://review.opendev.org/c/openstack/governance/+/854685 [18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-5, Aug 29 - Sep 02
by Előd Illés 26 Aug '22

26 Aug '22

Development Focus ----------------- We are getting close to the end of the Zed cycle! Next week on September 1st, 2022 is the Zed-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2023.1 Antelope cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on September 1st, 2022. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/zed branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… September 1st, 2022 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also the deadline for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Zed-3 milestone (feature freeze): September 1st, 2022 (R-5 week) RC1 deadline: September 15th, 2022 (R-3 week) Final RC deadline: September 29th, 2022 (R-1 week) Final Zed release: October 5th, 2022 Next PTG: October 17-21, 2022 (virtual PTG!!!) Előd Illés irc: elodilles

1 0

[Nova] Can't Attach An Encrypted NFS (luksv1) Volume
by Sofia Enriquez 26 Aug '22

26 Aug '22

Hello Nova Team, eharney and I are working on NFS encrypted volume support [1] and [2]. I'm trying to attach an encrypted volume to a nova instance. However, this fails with "libvirt.libvirtError: internal error: unable to execute QEMU command 'blockdev-add': Image is not in qcow2 format" error. I'm using a Devstack environment (nova/cinder master branch). Last week I opened a bug report [3] and I'd like to raise some attention to it. I've proposed a WIP patch [4] with a possible solution that I'd like to get some feedback on or know if should follow a different approach. The problem is that is_luks() returns false for the NFS case, because NFS is using LUKS inside of qcow2 and not regular LUKS. Let me know what you think Thank you Sofia [1] https://review.opendev.org/c/openstack/cinder/+/597148 [2] https://review.opendev.org/c/openstack/cinder/+/749155 [3] https://bugs.launchpad.net/nova/+bug/1987311 [4] https://review.opendev.org/c/openstack/nova/+/854030 -- 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

[charms][elections] PTL candidacy for Antelope cycle
by Alex Kavanagh 26 Aug '22

26 Aug '22

Hi All I would like to put myself forward for another cycle for the Charms PTL for the Antelope cycle. I've been a contributor to OpenStack and Charms since 2016 and a core member since mid 2016. I've also been the PTL for the last 2 cycles. Why do I want to be PTL again? The team has again achieved a huge amount, testing and supporting the charms and packages across multiple Ubuntu LTS releases (bionic, focal and now, jammy) with Charms and OpenStack support back to queens. We've (almost) transitioned to the new Charmhub ( charmhub.io) and will continue to support Queens through to the upcoming Zed release, and onto Antelope. I'd like to continue to support the team as we march forward with the responsibilities of the PTL to smooth the processes. Thanks Alex (tinwood) -- Alex Kavanagh - Software Engineer OpenStack Engineering - Data Centre Development - Canonical Ltd

1 0

[Glance] PTL non-candidacy
by Abhishek Kekane 26 Aug '22

26 Aug '22

Hi all, I'm writing this email to let you know that I'm not going to run for Glance PTL for the Antelope dev cycle, I think it's time for some new ideas and new approaches so it's a good idea to hand over the hat of PTL to a new member of the team. I've been serving Glance PTL since Ussuri, tried my best to keep Glance stable, lots of changes have been made since then, my initial focus was to improve glance-tempest coverage which we managed to do in past cycles. I would like to thank all the members of the Glance team and others for supporting me during this period. My plan is to stick around, attend to my duties as a glance core contributor, and support my successor in whatever way I can to make for a smooth transition. Thank you once again! Cheers, Abhishek Kekane

4 3

[kuryr][elections] PTL candidacy for Antelope cycle
by Roman Dobosz 26 Aug '22

26 Aug '22

Hello, I would like to announce my candidacy to be the Kuryr PTL for the next Antelope cycle. I've been Kuryr contributor since the Ussuri release and became core reviewers member at the end of Victoria cycle. In the upcoming Antelope cycle, I'd like to focus on Kuryr stability and compatibility with upcoming Kubernetes release. Another thing which I'd like to move forward is to eliminate Kuryr services restarts. Thanks, Roman Dobosz (gryf)

1 0

[election][heat][ptl] PTL non-candidacy
by Rico Lin 26 Aug '22

26 Aug '22

Hi all, As the PTL election will soon start, I would like to share my statement on not planning to run another term of Heat PTL. And instead, I encourage anyone (core reviewer or not) who is interested to put their name on. I will definitely still stay around and help with reviews and patches. *Rico Lin*

2 1

Regarding Designate Installation in ansible Playbook
by Adivya Singh 25 Aug '22

25 Aug '22

hi Team, I have made under conf.d a designate. yml file, and rerunning the setup of Openstack-setuphost but still it is not installing a Designate Container in OpenStack. Is there any Reason for this, Something i am doing right Regards Adivya Singh

2 1

[OPS] Participation Poll for OPS Meetup at the PTG
by Amy Marrich 25 Aug '22

25 Aug '22

Hey all, Just putting this on the list for more visibility. On Monday we posted a poll from the OPS Meetup Twitter account for how Operators would prefer to interact with the Developers[0]. The poll closes on Monday but if you don't have twitter please reply here with your preference. We also have a poll for preferred times[1] Thanks, Amy 0 - https://twitter.com/osopsmeetup/status/1561708280455593984 1 - https://doodle.com/meeting/participate/id/bD9kR2yd

1 0

[neutron] Drivers meeting agenda - 26.08.2022.
by Lajos Katona 25 Aug '22

25 Aug '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have the following RFEs to discuss tomorrow: * [RFE] Add a port extension to set/define the switchdev capabilities (#link https://bugs.launchpad.net/neutron/+bug/1987093 ) * [RFE] Add DSCP mark 44 (#link https://bugs.launchpad.net/neutron/+bug/1987378 ) And we have a topic for the On Demand agenda: * (amorin): Add new novaplug mechanism driver ** https://bugs.launchpad.net/neutron/+bug/1986969 ** https://review.opendev.org/c/openstack/neutron/+/854553 [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

DCN and DVR in Openstack wallaby | tripleo
by Swogat Pradhan 25 Aug '22

25 Aug '22

Hi, I have a site1 and a site2. Site1 contains the controller nodes with some compute and storage and in site2 i have compute nodes maybe hci solution for it. site1 has a different network pool and site2 has a different network pool and these cannot be extended to one another. What I want to know is how I am going to configure network to be used by the compute nodes in site2. If i use DVR then i can just create a normal external network which will only be used for site2 and then the traffic doesn't have to go through the network node. Is it the right solution? And is DVR enabled by default or do I have to use the neutron-ovn-dvr.yaml template? And if i use DVR do i have to set the following parameter?: ComputeParameters: NeutronBridgeMappings: "" Is DCN with DVR the correct approach? With regards, Swogat Pradhan

1 0

[all][tc] Technical Committee next weekly meeting on 2022 Aug 25 at 1500 UTC
by Ghanshyam Mann 25 Aug '22

25 Aug '22

Hello Everyone, Below is the agenda for Tomorrow's TC meeting schedule at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * Roll call * Follow up on past action items * Gate health check ** Bare 'recheck' state *** https://etherpad.opendev.org/p/recheck-weekly-summary * 2023.1 cycle PTG Planning ** Schedule 'operator hours' as a separate slot in PTG(avoiding conflicts among other projects 'operator hours') * 2023.1 cycle Technical Election * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

container and instances are not working on my dashboard
by Lee, Vincent Z 25 Aug '22

25 Aug '22

Hi all, I am quite new to Openstack and faced some issues with creating instances and displaying created containers on my Openstack dashboard. I am currently working on multinode Openstack. I am hoping to get some helps and feedbacks about this. I will briefly go through the problems I encountered. When I created an instances on my dashboard, it directly went into error state. I have attached a screenshot as shown below. [cid:c1615736-e4b3-4100-99c0-dfb970ff365f] This is my list of hosts. [cid:8d2f9138-27fd-4cf5-95ca-0cd9038f723c] When I created a container using both cli and dashboard, two containers were running. However, when I tried to look into my dashboard, those containers were not shown. These are the created containers. [cid:61d517f2-c60a-4892-bf88-1a9e0d763b7f] However, when i try to open my dashboard and look for them, they just don't appear on it. So I am not sure what is causing this. [cid:fb9d0f7e-1afa-48c1-bc92-9c8054382b55] Hope to hear from everyone soon. Best regards, Vincent

3 2

[all][elections][ptl][tc] Combined PTL/TC Antelope cycle Election Nominations Kickoff
by Amy Marrich 24 Aug '22

24 Aug '22

Apologies all for the lack of notice to the start of the PTL/TC election season. Unfortunately we are starting late and we are attempting to get back on schedule. We will make sure we send out a reminder notice (or two) for nominations closing. Remember we can't do this without your nominations and folks being willing to lead the projects and the community ======================================================================== Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (4 positions) are now open and will remain open until Aug 31, 2022 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/antelope/<Project_Name or "TC">/<email_address> (for example, "candidates/antelope/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the Zed to Antelope timeframe, Sep 17, 2021 00:00 UTC - Aug 31, 2022 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Sep 07, 2022 23:45 UTC through to Sep 14, 2022 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the Zed to Antelope timeframe, Sep 17, 2021 00:00 UTC - Aug 31, 2022 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the Zed to Antelope timeframe, Sep 17, 2021 00:00 UTC - Aug 31, 2022 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ATCs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ATCs. Please find below the timeline: PTL + TC nomination starts @ Aug 24, 2022 23:45 UTC PTL + TC nomination ends @ Aug 31, 2022 23:45 UTC TC campaigning starts @ Aug 31, 2022 23:45 UTC TC campaigning ends @ Sep 07, 2022 23:45 UTC PTL + TC elections start @ Sep 07, 2022 23:45 UTC PTL + TC elections end @ Sep 14, 2022 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2022-08-31 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials

1 0

[TripleO] Derived Parameters going away
by John Fulton 24 Aug '22

24 Aug '22

It seems this feature was not widely adopted so the current maintainers would like to remove it. We have a proposed patch [1] to remove it from the main branch so it won't be in the TripleO release which accompanies Zed. It's presently in the release which accompanies Wallaby. Note that TripleO is using the independent release model [2]. What is the "Derived Parameters" feature? NFV and HCI overclouds require system tuning. There are formulas which output tuning parameters based on hardware. These parameters may then be provided as input to TripleO to deploy a tuned overcloud. There is an additional method of system tuning called “derived parameters” where TripleO uses inspected hardware data as input and automatically sets tuning parameters [3]. Removing this feature shouldn't block anyone since they can still deploy a tuned overcloud by providing standard parameters. There's also a docs patch [4] explaining how to migrate away from derived to standard parameters. John [1] https://review.opendev.org/q/topic:derive-parameters-cleanup [2] https://review.opendev.org/c/openstack/tripleo-specs/+/801512 [3] https://specs.openstack.org/openstack/tripleo-specs/specs/pike/tripleo-deri… [4] https://review.opendev.org/c/openstack/tripleo-docs/+/854443

1 0

OpenInfra Live - August 25 at 1400 UTC
by Allison Price 24 Aug '22

24 Aug '22

Hi everyone, This week’s OpenInfra Live episode is brought to you by members of the OpenStack community. Episode: Making VDI a first-class citizen in the OpenStack world Learn the importance of having a Virtual Desktop Infrastructure (VDI) with OpenStack. Get to know the VDI use cases. Discover which relevant features are already integrated and which are still missing. You’ll also have the opportunity to meet Bumblebee and enjoy the cute flying insect during a demo! Date and time: Thursday, August 25 at 1400 UTC (9am CT) You can watch us live on: YouTube: https://www.youtube.com/watch?v=juczRNlfg6c <https://www.youtube.com/watch?v=juczRNlfg6c> LinkedIn: https://www.linkedin.com/video/event/urn:li:ugcPost:6966050226767884289/ <https://www.linkedin.com/video/event/urn:li:ugcPost:6966050226767884289/> Facebook: https://www.facebook.com/104139126308032/posts/5359387687449790/ <https://www.facebook.com/104139126308032/posts/5359387687449790/> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Manuel Bentele Andy Botting Radosław Piliszek Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. See you there! Allison

1 0

[neutron][ovn] Gauging community interest in supporting a masquerading forwarding DNS resolver for isolated tenant networks
by Miguel Lavalle 24 Aug '22

24 Aug '22

Hi, As described in this Launchpad bug https://bugs.launchpad.net/neutron/+bug/1902950, in contrast with ML2 / OVS, with ML2 / OVN there is not a masquerading forwarding DNS resolver available to instances on isolated tenant networks. The purpose of this message is to gather feedback from the community as to how much interest there is in providing this functionality under ML2 / OVN. If your organization has interest, please respond to this thread. Even better, register your interest on the topic in the etherpad for the upcoming Antelope PTG (https://etherpad.opendev.org/p/neutron-antelope-ptg) under the "Check of interest on closing ML2/OVN DNS gaps" topic. And of course, attend the conversation in October Best regards Miguel Lavalle

1 0

(no subject)
by ralonsoh＠redhat.com 24 Aug '22

24 Aug '22

The original message was received at Wed, 24 Aug 2022 22:48:10 +0900 from redhat.com [7.150.121.148] ----- The following addresses had permanent fatal errors ----- <openstack-discuss(a)lists.openstack.org>

1 0

High memory use with RabbitMQ on RHEL9 hosts
by Marcin Juszkiewicz 24 Aug '22

24 Aug '22

If you run RabbitMQ on RHEL9 family hosts (CentOS Stream 9, RockyLinux 9, AlmaLinux 9) and you see 1.6GB memory use then consider limiting amount of file descriptors: > EL9 (both CentOS Stream 9 and Rocky Linux 9) have 1073741816 while > CentOS Stream 8 has 1048576 - after lowering it's acceptable > memory usage. https://github.com/rabbitmq/erlang-rpm/discussions/104 for more

1 0

[cinder] Bug deputy report for week of 08-24-2022
by Sofia Enriquez 24 Aug '22

24 Aug '22

This is a bug report from 08-17-2022 to 08-24-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1982945 "[docs] Cannot start VM from disk with burst QoS." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1900406 "RBD support extends for in-use volume." Unassigned. Cheers, Sofia -- 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