- openstack-discuss - lists.openstack.org

OpenStack Release Name Voting Now Open!
by Erin Disney 20 Dec '22

20 Dec '22

Hey everyone- It’s that time again to vote for the next OpenStack release name! Here are the finalists: 1. Bandicoot 2. Basalt 3. Bobcat 4. Boomerang Please submit your vote by January 3rd at 11:59pm PT (January 4th at 7:59 UTC). https://civs1.civs.us/cgi-bin/vote.pl?id=E_9c7f7a20a8871b09&akey=5b974247f9… <https://civs1.civs.us/cgi-bin/vote.pl?id=E_9c7f7a20a8871b09&akey=5b974247f9…> Happy voting! Thanks, Erin

2 1

Kolla-ansible openstack deployment with High Availability
by A Monster 18 Dec '22

18 Dec '22

Do I need to deploy and configure PaceMaker and HAproxy or something similar in order to get a HA kolla-ansible openstack deployment? or is it something done automatically? If so, what are the steps I should be taking?

3 2

[cinder] Extending specs deadline to 23rd December
by Rajat Dhasmana 17 Dec '22

17 Dec '22

Hello Argonauts, As per the schedule[1], cinder spec deadline was 16th December, 2022. However, due to unavailability of some core members, less review bandwidth throughout the week (including me) and other factors like bringing cinderlib to a release-able state, we couldn't get the sufficient reviews done and hence will be extending the deadline for all the open specs proposed for 2023.1 (Antelope) release. The new deadline for cinder specs will be 23rd December, 2022. Please make sure your specs are updated and in a reviewable state. [1] https://releases.openstack.org/antelope/schedule.html#a-cinder-spec-freeze Thanks Rajat Dhasmana

1 0

[all][TC] Bare rechecks stats week of 25.07
by Slawek Kaplonski 17 Dec '22

17 Dec '22

Hi, Here are fresh data about bare rechecks. +--------------------+---------------+--------------+-------------------+ | Team | Bare rechecks | All Rechecks | Bare rechecks [%] | +--------------------+---------------+--------------+-------------------+ | requirements | 2 | 2 | 100.0 | | keystone | 1 | 1 | 100.0 | | OpenStackSDK | 3 | 3 | 100.0 | | tacker | 3 | 3 | 100.0 | | freezer | 1 | 1 | 100.0 | | rally | 1 | 1 | 100.0 | | OpenStack-Helm | 14 | 15 | 93.33 | | cinder | 6 | 7 | 85.71 | | kolla | 20 | 25 | 80.0 | | neutron | 4 | 5 | 80.0 | | Puppet OpenStack | 10 | 13 | 76.92 | | OpenStack Charms | 3 | 6 | 50.0 | | nova | 11 | 22 | 50.0 | | tripleo | 8 | 19 | 42.11 | | ironic | 1 | 3 | 33.33 | | Quality Assurance | 1 | 3 | 33.33 | | octavia | 0 | 1 | 0.0 | | OpenStackAnsible | 0 | 1 | 0.0 | | designate | 0 | 1 | 0.0 | | Release Management | 0 | 1 | 0.0 | | horizon | 0 | 1 | 0.0 | +--------------------+---------------+--------------+-------------------+ Those data should be more accurate as my script now counts only comments from last 7 days, not all comments from patches updated in last 7 days. Reminder: "bare rechecks" are recheck comments without any reason given. If You need to do recheck for patch due to failed job(s), please first check such failed job and try to identify what was the issue there. Maybe there is already opened bug for that or maybe You can open new one and add it as explanation in the recheck comment. Or maybe it was some infra issue, in such case short explanation in the comment would also be enough. -- Slawek Kaplonski Principal Software Engineer Red Hat

6 10

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

17 Dec '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Dec 14. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-12-14-16.00.log.html * Next TC weekly meeting will be on Dec 21 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Dec 20. 2. What we completed this week: ========================= * The technical elections dates for next cycle is finalized[2], please plan your nominations for open leaderships roles accordingly. 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[3]. Open Reviews ----------------- * Three open reviews for ongoing activities[4]. IMPORTANT: Tox 4 failure and time to fix them -------------------------------------------------------- You might know about Tox 4 failure and currently it is capped as <4 in ensure-tox role. This is going to be uncapped on Dec 21[5] and you might see tox based unit/functional tests job (or any job using ensure-role except devstack based) will start failing. Please plan the testing and fix accordingly. Calling out here as holiday seasons or fixing it in early cycle will help to plan the smooth development cycle and release. Change in Inactive project timeline ----------------------------------------- The proposal for this is under review[6] and positive response so far. Mistral release and more maintainers ------------------------------------------- avanzagh joined TC meeting and updates us that new maintainers from OVHCloud have been added as Core members to help maintaining Mistral. And we also discussed and agreed to continue Mistral in DPL model for this cycle. As next step, avanzagh will discuss the required work to release Mistral or what are the expectations from the release team to consider it as release item. This seems like good progress. We will keep monitor the situation until proposal for Mistral release deprecation is closed[7]. Renovate translation SIG i18 ---------------------------------- * No updates this week and we will track it in TC tracker and update on ML if there is any update. Project updates ------------------- * Add Cinder Huawei charm[8] 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[9]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [10] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://governance.openstack.org/election/ [3] https://etherpad.opendev.org/p/tc-2023.1-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-December/03144… [6] https://review.opendev.org/c/openstack/governance/+/867062 [7] https://review.opendev.org/c/openstack/governance/+/866562 [8] https://review.opendev.org/c/openstack/governance/+/867588 [9] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [10] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[keystone] Holiday Meeting Schedule
by Dave Wilde 16 Dec '22

16 Dec '22

Hello, For the upcoming holidays I’m setting the Keystone meeting schedule as follows: 2022: - 20-Dec: Keystone weekly meeting on IRC - 23-Dec: Keystone Reviewathon on Google Meet - 27-Dec: Cancelled - Keystone weekly meeting - 30-Dec: Cancelled - Keystone Reviewathon on Google Meet 2023: - 03-Jan: Keystone weekly meeting on IRC as usual - 06-Jan: Keystone Reviewathon on Google Meet As always please let me know if you need anything. I hope you have a nice holiday and safe and happy new year! Thanks, /Dave

1 0

Could I deploy openstack in openstack instance
by 韩光宇 15 Dec '22

15 Dec '22

Hello, Could I deploy openstack in openstack instance? When I use a instance just with one network interface. After ip move to brq(using linuxbridge) or br-ex(uring openvswitch), the instance lost connection.  Does anyone know how to set it up? Or suggest me some documentation. I would appreciate any kind of guidance or help. Thank you.

2 1

Re: auto switch of glance-api containers to other controllers
by pradeep 15 Dec '22

15 Dec '22

Hello All Any help is highly appreciated. On Thu, 15 Dec 2022 at 01:41, pradeep <pradeep8985(a)gmail.com> wrote: > Hi Danny, > > Yes, i did, All of them are mounted in all the 3 controllers as well. > > # cat /etc/kolla/globals.yml | egrep > "glance_backend_file|glance_file_datadir_volume" > #glance_backend_file: "yes" > glance_file_datadir_volume: "/glanceimages" > > root@ctrl-1:~# df -h /glanceimages/ > Filesystem Size Used Avail Use% Mounted on > <IPaddress>:/Openstack_fileshare1 150G 888M 150G 1% /glanceimages > > root@ctrl-2:~# df -h /glanceimages/ > Filesystem Size Used Avail Use% Mounted on > <IPaddress>:/Openstack_fileshare1 150G 888M 150G 1% /glanceimages > > root@ctrl-3:~# df -h /glanceimages/ > Filesystem Size Used Avail Use% Mounted on > <IPaddress>:/Openstack_fileshare1 150G 888M 150G 1% /glanceimages > > > On Wed, 14 Dec 2022 at 17:54, Danny Webb <Danny.Webb(a)thehutgroup.com> > wrote: > >> did you change the glance_file_datadir_volume variable? that is >> required for kolla to deploy multiples: >> >> >> https://github.com/openstack/kolla-ansible/blob/ae3de342e48bc4293564a3b532a… >> >> ------------------------------ >> *From:* pradeep <pradeep8985(a)gmail.com> >> *Sent:* 14 December 2022 10:19 >> *To:* Danny Webb <Danny.Webb(a)thehutgroup.com> >> *Subject:* Re: auto switch of glance-api containers to other controllers >> >> >> * CAUTION: This email originates from outside THG * >> ------------------------------ >> Thanks Danny, All >> >> I have found the glance-api containers not deployed in control2 and >> control3 hosts although I have used NFS as my backend and share is enabled >> in all my controllers. >> >> I have tried to deploy the containers in control 2 and 3 as below but see >> some failures. I hope I am not using the wrong command. Am i missing >> something? Please let me know. >> >> *Command used* >> kolla-ansible -i multinode deploy --tags "glance" --limit >> control02.lab,control03.lab -vv >> >> *Errors in deployment* >> >> RUNNING HANDLER [glance : Restart glance-api container] >> ********************************************************************************* >> task path: >> /root/kolla-ansible/venv/share/kolla-ansible/ansible/roles/glance/handlers/main.yml:2 >> >> fatal: [control02.lab]: FAILED! => {"changed": true, "msg": "'Traceback >> (most recent call last):\\n File >> \"/usr/local/lib/python3.8/dist-packages/docker/api/client.py\", line 268, >> in _raise_for_status\\n response.raise_for_status()\\n File >> \"/usr/lib/python3/dist-packages/requests/models.py\", line 940, in >> raise_for_status\\n raise HTTPError(http_error_msg, >> response=self)\\nrequests.exceptions.HTTPError: 500 Server Error: Internal >> Server Error for url: >> http+docker://localhost/v1.41/images/create?tag=yoga&fromImage=quay.io%2Fopenstack.kolla%2Fubuntu-source-glance-api\\n\\nDuring >> handling of the above exception, another exception occurred:\\n\\nTraceback >> (most recent call last):\\n File >> \"/tmp/ansible_kolla_docker_payload_iltg71bi/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", >> line 381, in main\\n File >> \"/tmp/ansible_kolla_docker_payload_iltg71bi/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", >> line 651, in recreate_or_restart_container\\n self.start_container()\\n >> File >> \"/tmp/ansible_kolla_docker_payload_iltg71bi/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", >> line 669, in start_container\\n self.pull_image()\\n File >> \"/tmp/ansible_kolla_docker_payload_iltg71bi/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", >> line 450, in pull_image\\n json.loads(line.strip().decode(\\'utf-8\\')) >> for line in self.dc.pull(\\n File >> \"/usr/local/lib/python3.8/dist-packages/docker/api/image.py\", line 430, >> in pull\\n self._raise_for_status(response)\\n File >> \"/usr/local/lib/python3.8/dist-packages/docker/api/client.py\", line 270, >> in _raise_for_status\\n raise create_api_error_from_http_exception(e)\\n >> File \"/usr/local/lib/python3.8/dist-packages/docker/errors.py\", line 31, >> in create_api_error_from_http_exception\\n raise cls(e, response=response, >> explanation=explanation)\\ndocker.errors.APIError: 500 Server Error for >> http+docker://localhost/v1.41/images/create?tag=yoga&fromImage=quay.io%2Fopenstack.kolla%2Fubuntu-source-glance-api: >> Internal Server Error (\"Get \"https://quay.io/v2/\ >> <https://quay.io/v2//>": net/http: request canceled while waiting for >> connection (Client.Timeout exceeded while awaiting headers)\")\\n'"} >> fatal: [control03.lab]: FAILED! => {"changed": true, "msg": "'Traceback >> (most recent call last):\\n File >> \"/usr/local/lib/python3.8/dist-packages/docker/api/client.py\", line 268, >> in _raise_for_status\\n response.raise_for_status()\\n File >> \"/usr/lib/python3/dist-packages/requests/models.py\", line 940, in >> raise_for_status\\n raise HTTPError(http_error_msg, >> response=self)\\nrequests.exceptions.HTTPError: 500 Server Error: Internal >> Server Error for url: >> http+docker://localhost/v1.41/images/create?tag=yoga&fromImage=quay.io%2Fopenstack.kolla%2Fubuntu-source-glance-api\\n\\nDuring >> handling of the above exception, another exception occurred:\\n\\nTraceback >> (most recent call last):\\n File >> \"/tmp/ansible_kolla_docker_payload_kkez0k31/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", >> line 381, in main\\n File >> \"/tmp/ansible_kolla_docker_payload_kkez0k31/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", >> line 651, in recreate_or_restart_container\\n self.start_container()\\n >> File >> \"/tmp/ansible_kolla_docker_payload_kkez0k31/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", >> line 669, in start_container\\n self.pull_image()\\n File >> \"/tmp/ansible_kolla_docker_payload_kkez0k31/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", >> line 450, in pull_image\\n json.loads(line.strip().decode(\\'utf-8\\')) >> for line in self.dc.pull(\\n File >> \"/usr/local/lib/python3.8/dist-packages/docker/api/image.py\", line 430, >> in pull\\n self._raise_for_status(response)\\n File >> \"/usr/local/lib/python3.8/dist-packages/docker/api/client.py\", line 270, >> in _raise_for_status\\n raise create_api_error_from_http_exception(e)\\n >> File \"/usr/local/lib/python3.8/dist-packages/docker/errors.py\", line 31, >> in create_api_error_from_http_exception\\n raise cls(e, response=response, >> explanation=explanation)\\ndocker.errors.APIError: 500 Server Error for >> http+docker://localhost/v1.41/images/create?tag=yoga&fromImage=quay.io%2Fopenstack.kolla%2Fubuntu-source-glance-api: >> Internal Server Error (\"Get \"https://quay.io/v2/\ >> <https://quay.io/v2//>": net/http: request canceled while waiting for >> connection (Client.Timeout exceeded while awaiting headers)\")\\n'"} >> META: ran handlers >> >> Regards >> Pradeep >> >> >> On Mon, 12 Dec 2022 at 14:54, Danny Webb <Danny.Webb(a)thehutgroup.com> >> wrote: >> >> Kolla only uses a single controller if you use file based backend by >> default. If you want to continue using the file backend, you can use >> something like an NFS share to share images between controllers and then >> change the glance_file_datadir_volume parameter which will result in the >> api being deployed on all controllers >> ------------------------------ >> *From:* pradeep <pradeep8985(a)gmail.com> >> *Sent:* 12 December 2022 04:53 >> *To:* Dmitriy Rabotyagov <noonedeadpunk(a)gmail.com> >> *Cc:* openstack-discuss <openstack-discuss(a)lists.openstack.org> >> *Subject:* Re: auto switch of glance-api containers to other controllers >> >> >> * CAUTION: This email originates from outside THG * >> ------------------------------ >> Any help is highly appreciated. >> >> Thank you! >> >> On Fri, 9 Dec 2022 at 21:46, pradeep <pradeep8985(a)gmail.com> wrote: >> >> Hi Dmitriy, Thanks for the response. Sorry, I forgot to mention that i >> used kolla ansible for deployment. As per kolla docs, glance-api container >> runs only in one controller. So i am looking from kolla perspective if it >> can automatically switch it over other available controllers. >> >> Regards >> Pradeep >> >> On Fri, 9 Dec 2022 at 14:51, Dmitriy Rabotyagov <noonedeadpunk(a)gmail.com> >> wrote: >> >> Hi, >> >> I'm not sure if you used any deployment tool for your environment, but >> usually for such failover there's a load balancer in conjunction with VRRP >> or Anycast, that able to detect when controller1 is down and forward >> traffic to another controller. >> >> As example, OpenStack-Ansible as default option installs haproxy to each >> controller and keepalived to implement VRRP and Virtual IPs. So when glance >> is down on controller1, haproxy will detect that and forward traffic to >> other controllers. If controller1 is down as a whole, keepalived will >> detect that and raise VIP on controller2, so all client traffic will go >> there. Since controller2 also have haproxy, it will pass traffic to >> available backends based on the source IP. >> >> >> пт, 9 дек. 2022 г., 09:06 pradeep <pradeep8985(a)gmail.com>: >> >> Hello All, >> >> I understand that glance-api container run only one controller always. I >> have tried to check if the glance-api container to switch over to the next >> available controller by means of rebooting and stopping the containers, but >> nothing happened. Is there a way to make sure that glance-api container >> switches to other controllers if controller 1 is not available. >> >> Thanks for you help >> >> Regards >> Pradeep >> >> >> >> >> -- >> ----------------------- >> Regards >> Pradeep Kumar >> >> >> >> -- >> ----------------------- >> Regards >> Pradeep Kumar >> >> *Danny Webb* >> Principal OpenStack Engineer >> Danny.Webb(a)thehutgroup.com >> [image: THG Ingenuity Logo] >> www.thg.com >> <https://www.linkedin.com/company/thg-ingenuity/?originalSubdomain=uk> >> <https://twitter.com/thgingenuity?lang=en> >> >> Danny Webb >> Principal OpenStack Engineer >> The Hut Group <http://www.thehutgroup.com/> >> >> Tel: >> Email: Danny.Webb(a)thehutgroup.com >> >> >> For the purposes of this email, the "company" means The Hut Group >> Limited, a company registered in England and Wales (company number 6539496) >> whose registered office is at Fifth Floor, Voyager House, Chicago Avenue, >> Manchester Airport, M90 3DQ and/or any of its respective subsidiaries. >> >> *Confidentiality Notice* >> This e-mail is confidential and intended for the use of the named >> recipient only. If you are not the intended recipient please notify us by >> telephone immediately on +44(0)1606 811888 or return it to us by e-mail. >> Please then delete it from your system and note that any use, >> dissemination, forwarding, printing or copying is strictly prohibited. Any >> views or opinions are solely those of the author and do not necessarily >> represent those of the company. >> >> *Encryptions and Viruses* >> Please note that this e-mail and any attachments have not been encrypted. >> They may therefore be liable to be compromised. Please also note that it is >> your responsibility to scan this e-mail and any attachments for viruses. We >> do not, to the extent permitted by law, accept any liability (whether in >> contract, negligence or otherwise) for any virus infection and/or external >> compromise of security and/or confidentiality in relation to transmissions >> sent by e-mail. >> >> *Monitoring* >> Activity and use of the company's systems is monitored to secure its >> effective use and operation and for other lawful business purposes. >> Communications using these systems will also be monitored and may be >> recorded to secure effective use and operation and for other lawful >> business purposes. >> hgvyjuv >> >> >> >> -- >> ----------------------- >> Regards >> Pradeep Kumar >> >> *Danny Webb* >> Principal OpenStack Engineer >> Danny.Webb(a)thehutgroup.com >> [image: THG Ingenuity Logo] >> www.thg.com >> <https://www.linkedin.com/company/thg-ingenuity/?originalSubdomain=uk> >> <https://twitter.com/thgingenuity?lang=en> >> > > > -- > ----------------------- > Regards > Pradeep Kumar > -- ----------------------- Regards Pradeep Kumar

1 0

[qa] Cancelling next office hours
by Martin Kopec 15 Dec '22

15 Dec '22

Hi everyone, we're cancelling office hours for the next 3 weeks due to the holidays. The next office hour is gonna be on January 10th. Thank you. Enjoy your holidays! -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

kolla-ansible deploy glance with file as a backend on multiple nodes
by A Monster 15 Dec '22

15 Dec '22

I have made a deployment of openstack on multiple centos stream 8 nodes, and used files as a backend for glance service, but according to the documentation, when using file as a glance backend, It can only be deployed on a single node, what can I do to deploy it on multiple servers at once. Thank you.

3 2