June 2022 - openstack-discuss - lists.openstack.org

[Magnum resize Master node root volume/docker volume or resize flavor]
by Nabeel Tariq Khan 13 Jun '22

13 Jun '22

Hi, Is it possible to resize the root volume or docker volume or resize the flavor of master or minion node on openstack magnum? regards, Nabeel Tariq Khan

1 0

Regarding Policy.json entries for glance image update not working for a user
by Adivya Singh 13 Jun '22

13 Jun '22

Hi Team, I have a use case where I have to give a user restriction on updating the image properties as a member. I have created a policy Json file and give the modify_image rule to the particular role, but still it is not working "modify_image": "role:user", This role is created in OpenStack. but still it is failing while updating properties with a particular user assigned to a role as "access denied" and unauthorized access Regards Adivya Singh

3 3

[ironic] No weekly meeting today (June 13)
by Iury Gregory 13 Jun '22

13 Jun '22

Hello Ironicers, I'm still on my way back home from the OIS, I'll not be able to run the upstream meeting I've asked in the irc and people are ok with skipping today's meeting, see you next week! -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

[neutron][networking-l2gw][puppet] Status of networking-l2gw project
by Takashi Kajinami 13 Jun '22

13 Jun '22

Hello team, # I understand networking-l2gw is not under neutron stadium # but adding [neutron] tag hoping it would attract more attention. We found a recent change in neutron[1] broke networking-l2gw[2], and some jobs in puppet repos and rdo, with l2gw enabled, are failing. I proposed a potential fix for the bug[3], but I noticed the project looks unmaintained according to the following points. - No change has been merged for more than 1 year - No release was created since Wallaby - The zuul setting still points the victoria job template (openstack-python3-victoria-jobs-neutron) I'm wondering if anybody is actually interested in maintaining the project. If not, I'll propose retiring the plugin support from puppet (and TripleO because it requires puppet implementation). I appreciate any feedback about this. [1] https://review.opendev.org/c/openstack/neutron/+/837392 [2] https://bugs.launchpad.net/networking-l2gw/+bug/1977980 [3] https://review.opendev.org/c/x/networking-l2gw/+/845141 Thank you, Takashi

2 1

Re: snapshot problem
by Eugen Block 12 Jun '22

12 Jun '22

Have you tried with debug logs? Has it worked with live snapshots before for other instances or did it never work and all snapshots were "cold"? Zitat von Parsa Aminian <p.aminian.server(a)gmail.com>: > Hi > kolla-ansible victoria version with ceph backend without volume > > On Sun, Jun 12, 2022 at 12:45 PM Eugen Block <eblock(a)nde.ag> wrote: > >> Hi, >> >> can you share more details about your environment? Which openstack >> version is it? What is the storage backend? In earlier releases there >> was an option: >> >> #disable_libvirt_livesnapshot = false >> >> but this option has been deprecated. But if you're on an older version >> that could explain it. >> >> Zitat von Parsa Aminian <p.aminian.server(a)gmail.com>: >> >> > When I snapshot from the instance , server will gone away and its not >> > reachable until the snapshot is complete here is the logs : >> > 25c8d676-e20a-4238-a45c-d51daa62b941] instance snapshotting >> > 2022-06-12 09:42:34.755 7 INFO nova.compute.manager >> > [req-786946b1-3d22-489c-bf4d-8b1375b09ecb - - - - -] [instance: >> > 25c8d676-e20a-4238-a45c-d51daa62b941] VM Paused (Lifecycle Event) >> > 2022-06-12 09:42:34.995 7 INFO nova.compute.manager >> > [req-786946b1-3d22-489c-bf4d-8b1375b09ecb - - - - -] [instance: >> > 25c8d676-e20a-4238-a45c-d51daa62b941] During sync_power_state the >> instance >> > has a pending task (image_pending_upload). Skip. >> > 2022-06-12 09:42:57.749 7 INFO nova.compute.manager [-] [instance: >> > 25c8d676-e20a-4238-a45c-d51daa62b941] VM Stopped (Lifecycle Event) >> > 2022-06-12 09:43:06.102 7 INFO nova.virt.libvirt.driver >> > [req-e79e4177-4712-4795-91da-853bc524fac0 >> 93fb420b3c604d4fae408b81135b58e9 >> > ef940663426b4c87a751afaf13b758e0 - default default] [instance: >> > 25c8d676-e20a-4238-a45c-d51daa62b941] Snapshot extracted, beginning image >> > upload >> > 2022-06-12 09:43:08.778 7 INFO nova.compute.manager >> > [req-786946b1-3d22-489c-bf4d-8b1375b09ecb - - - - -] [instance: >> > 25c8d676-e20a-4238-a45c-d51daa62b941] VM Started (Lifecycle Event) >> >> >> >> >>

1 0

[nova][openstack-ansible] "No Valid Host Found" when running on VirtualBox
by Dave Hall 12 Jun '22

12 Jun '22

Hello, I'm trying to run a test/learning cluster on VirtualBox VMs deployed with Openstack-Ansible prior to deploying on real hardware. The playbooks succeed, and the basic functional checks all look good. However, I am unable to deploy an instance due to 'No Valid Host Found'. I have seen that this might be because VirtualBox does not support KVM. But I am also perplexed - I am able to deploy instances on an AIO running in VirtualBox on the same physical host. If there is an easy fix for this please point me in the right direction. If I need to destroy and re-clone my VMs I can try that as well. In an effort to learn, though, I'd really like to learn how to adjust the current deployment. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

2 5

snapshot problem
by Parsa Aminian 12 Jun '22

12 Jun '22

When I snapshot from the instance , server will gone away and its not reachable until the snapshot is complete here is the logs : 25c8d676-e20a-4238-a45c-d51daa62b941] instance snapshotting 2022-06-12 09:42:34.755 7 INFO nova.compute.manager [req-786946b1-3d22-489c-bf4d-8b1375b09ecb - - - - -] [instance: 25c8d676-e20a-4238-a45c-d51daa62b941] VM Paused (Lifecycle Event) 2022-06-12 09:42:34.995 7 INFO nova.compute.manager [req-786946b1-3d22-489c-bf4d-8b1375b09ecb - - - - -] [instance: 25c8d676-e20a-4238-a45c-d51daa62b941] During sync_power_state the instance has a pending task (image_pending_upload). Skip. 2022-06-12 09:42:57.749 7 INFO nova.compute.manager [-] [instance: 25c8d676-e20a-4238-a45c-d51daa62b941] VM Stopped (Lifecycle Event) 2022-06-12 09:43:06.102 7 INFO nova.virt.libvirt.driver [req-e79e4177-4712-4795-91da-853bc524fac0 93fb420b3c604d4fae408b81135b58e9 ef940663426b4c87a751afaf13b758e0 - default default] [instance: 25c8d676-e20a-4238-a45c-d51daa62b941] Snapshot extracted, beginning image upload 2022-06-12 09:43:08.778 7 INFO nova.compute.manager [req-786946b1-3d22-489c-bf4d-8b1375b09ecb - - - - -] [instance: 25c8d676-e20a-4238-a45c-d51daa62b941] VM Started (Lifecycle Event)

2 1

[all][tc] What's happening in Technical Committee: summary 10 June 2022: Reading: 5 min
by Ghanshyam Mann 11 Jun '22

11 Jun '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We cancelled this week's meeting. The next TC weekly meeting will be on 16 June Thursday at 15:00 UTC, feel free to add the topic to the agenda[1] by 15 June. 2. What we completed this week: ========================= * Added community infrastructure contributor help in upstream investment[2] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], many items are in-progress. Open Reviews ----------------- * Five open reviews for ongoing activities[4]. New release cadence "SLURP" open items -------------------------------------------------- 1. release notes strategy: Brian proposal for ""SLURP release notes approach is up for review[5]. Improve project governance --------------------------------- Slawek has the framework proposal up and is under review[6]. New ELK service dashboard: e-r service ----------------------------------------------- No update this week. Consistent and Secure Default RBAC ------------------------------------------- We called for the operator's feedback on RBAC new directions, I sent an email about it[7] and also created etherpad to collect feedback in a central place[8]. My humble request is to use this central etherpad for feedback/discussion otherwise it might be difficult for me to collect/know feedback conclusions from a lot of 100s places. We have feedback from the berlin summit but we still encourage operators/local events or so keep adding the feedback and your view on RBAC. Please note that operator feedback is very important for us to proceed on 'scope' in SRBAC. If you are operator or know anyone around you, we request you to provide feedback. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[9]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- No updates on this. Only Adjutant project is leaderless/maintainer-less. We will check Adjutant's the situation again on ML and hope Braden will be ready with their company side permission[10]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11][12]. Project updates ------------------- * None 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[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 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/+/843749 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://review.opendev.org/c/openstack/project-team-guide/+/843457 [6] https://review.opendev.org/c/openstack/governance/+/839880 [7] http://lists.openstack.org/pipermail/openstack-discuss/2022-June/028878.html [8] https://etherpad.opendev.org/p/rbac-operator-feedback [9] https://review.opendev.org/c/openstack/governance/+/836888 [10] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Openstack-Ansible vs Kolla-Ansible -Xena or later
by Dave Hall 10 Jun '22

10 Jun '22

Hello, My question is about OpenStack-Ansible vs. Kolla-Ansible. While I am sensitive to the effort that has been put into both of these projects, what I really need right now is the most fool-proof way to deploy and manage a small production cluster for academic instructional use. I have been working for a couple months with OpenStack-Ansible to deploy a small (3-node) test cluster on VirtualBox VMs in preparation for a larger deployment on real hardware - 6 to 10 nodes. (Details: Debian 11 deployment, Debian 10 infra, compute, and storage nodes) It has been slow going, at least partially due to some issues and limitations with VirtualBox. However, deploying a test cluster on VMs still seems preferable to just diving deployment on real hardware and going through multiple scrubs/reinstalls. Today I saw that Mark asked a question about Kolla-Ansible. So, as a 'beginner', should I shift and look at Kolla-Ansible, or should I stay the course and continue with Openstack-Ansible? What are the pros and cons of each? Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

6 10

[TripleO] move stable/victoria tripleo to End Of Life OK?
by Marios Andreou 10 Jun '22

10 Jun '22

Hello TripleO the tripleo-ci team proposes that we transition the stable/victoria branch across all tripleo repos [1] to End Of Life [2]. Hopefully this is not a suprise to anyone as it has been discussed for a while (most recent discussion I can point to is at Zed PTG [3]). The stable/victoria branch was moved to Extended Maintenance with [4] so we can no longer make any releases for these repos. Victoria is not an active branch for TripleO (not an FFU branch) so we are just merging patches there on the way back to train. Are there any concerns, objections or any other comment? I'll give this a few days and if there are no further comments I'll post the EOL proposal and update here towards the end of next week, regards, marios [1] https://releases.openstack.org/teams/tripleo.html#victoria [2] https://docs.openstack.org/project-team-guide/stable-branches.html#maintena… [3] https://etherpad.opendev.org/p/tripleo-zed-ci-load [4] https://review.opendev.org/c/openstack/releases/+/837982

1 2