April 2020 - openstack-discuss - lists.openstack.org

[glance][ptg[ Virtual PTG
by Abhishek Kekane 27 Apr '20

27 Apr '20

Hi Stackers, As you have noticed due to the current Covid-19 situation we will be having a virtual PTG for Victoria [1]. The PTG will take place from 1st to 5th June 2020 with various slots [2]. So I created a doodle to ask You what would be the best time slots for You to participate - it's available at [3]. If You are planning to attend this event, please mark what time slots are best for You. I will try to book some slots to fit the needs of the team. If You can attend only on some specific slots, and You will have some topics to discuss, we can try to book some slots in time which will work for You and schedule discussions about Your topics on that slot. As we should book slots in about next 2 weeks, it would be great if You could do this doodle before e.g. end of next week (Friday 24th of April). We also have our etherpad [4] - please add Your name to it (at top) if You are planning to attend this virtual event. And please also add proposals of the topics which You want to be discussed there. If you have any suggestions or doubt you can ping me on IRC (abhishekk) or any glance core member at #openstack-glance. I will compile the responses on 24th April and will book the slots accordingly. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.ht… [2] https://ethercalc.openstack.org/126u8ek25noy [3] https://doodle.com/poll/6a46283tii7gt2aa [4] https://etherpad.opendev.org/p/Glance-Victoria-PTG-planning Thanks & Best Regards, Abhishek Kekane

1 2

[release] Ussuri for vitarge
by Eyal B 27 Apr '20

27 Apr '20

Hi, Is there a reason Vitrage, vitrage client and vitrage-dashboard didn't get a patch for creating the Ussuri branch ? Eyal

2 1

[neutron] Bug deputy report for week of April 20th
by Nate Johnston 27 Apr '20

27 Apr '20

Nate bug deputy notes - 2020-04-20 to 2020-04-27 ------------------------------------------------ Untriaged: - "[VPNaas-DVR]The Traffic is unreachable after the virtual machine is bound to the floating IP" * URL: https://bugs.launchpad.net/bugs/1874392 * Note: Need a VPNaaS expert to look at this one. - "After the vm unbinds the floating ip, there are residual ip rules in the qrouter namespace" * URL: https://bugs.launchpad.net/bugs/1874420 * Version: stable/stein * Unable to reproduce locally Critical: - "[stable/stein] Neutron-tempest-plugin jobs are failing due to wrong python version" * URL: https://bugs.launchpad.net/bugs/1873776 * Version: stable/stein * Assignee: bcafarel * Fix: https://review.opendev.org/721277 - "[L3HA] Keepalived 2.x.x tracks state of virtual_ipaddresses interfaces and router now" * URL: https://bugs.launchpad.net/bugs/1874211 * Assignee: slaweq * Fix: https://review.opendev.org/721799 https://review.opendev.org/721805 High: - "[OVN] Tempest test neutron_tempest_plugin.scenario.test_trunk.TrunkTest.test_trunk_subport_lifecycle fails randomly" * URL: https://bugs.launchpad.net/bugs/1874447 * Unassigned - "[OVN] Stale ports can be present in OVN NB leading to metadata errors" * URL: https://bugs.launchpad.net/bugs/1874733 * Assignee: maciejjozefczyk/lucasgomes * Fix: https://review.opendev.org/722789 https://review.opendev.org/723404 Medium: - "test_multicast_between_vms_on_same_network failures" * URL: https://bugs.launchpad.net/bugs/1873798 * Assignee: lucasgomes * Fix: https://review.opendev.org/721262 - "[OVN] extra_dhcp_opts does not validate any options" * URL: https://bugs.launchpad.net/bugs/1874282 * Assignee: lucasgomes * Fix: https://review.opendev.org/722025 - "Cleanup in neutron_tempest_plugin.api.admin.test_external_network_extension.ExternalNetworksRBACTestJSON may fail in dvr deployments" * URL: https://bugs.launchpad.net/bugs/1875344 * Assignee: slaweq * Fix: https://review.opendev.org/723387 Low: - "[agent][dhcp] When revision_number matches the one in cache it is not considered stale" * URL: https://bugs.launchpad.net/bugs/1874400 * Unassigned Invalid/Incomplete: - "Cannot create fip namespace when dhcp pool is insufficient" * URL: https://bugs.launchpad.net/bugs/1875153 Last week's report by tidwellr: http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014332.ht…

1 0

[ops][cinder] Policy for volume attach/detach
by Massimo Sgaravatto 27 Apr '20

27 Apr '20

I would like to set a policy so that attachments operations can be done only by the user who created that volume. To do that I created this [*] policy.yaml file. I verified that with such policy file: - I am able to attach volumes only for the volumes I created - I can attach my volumes also to instances owned by other users - I can not attach volumes belonging to other users to my instances So far so good. But I am allowed to detach any volume from any instance, even if I am not the owner of that volume, and this is not what I want What am I doing wrong ? Thanks, Massimo [*] # # To be used when another member of the same project can't change something # created by another user of the same project "admin_or_user": "is_admin:True or (role:admin and is_admin_project:True) or user_id:%(user_id)s" # Create attachment. # POST /attachments "volume:attachment_create": "rule:admin_or_user" # Update attachment. # PUT /attachments/{attachment_id} "volume:attachment_update": "rule:admin_or_user" # Delete attachment. # DELETE /attachments/{attachment_id} "volume:attachment_delete": "rule:admin_or_user" # Mark a volume attachment process as completed (in-use) # POST /attachments/{attachment_id}/action (os-complete) "volume:attachment_complete": "rule:admin_or_user"

2 2

[neutron] Virtual PTG planning
by Slawek Kaplonski 26 Apr '20

26 Apr '20

Hi neutrinos, As You probably noticed, there is already plan for Virtual PTG in June. See mail from Kendall [1] for details. So I created doodle to ask You what would be the best time slots for You to participate - it's available at [2]. If You are planning to attend this event, please mark what time slots are best for You. I will try to book some slots to fit needs of the team. If You can attend only on some specific slots, and You will have some topics to discuss, we can try to book some slot in time which will work for You and schedule discussions about Your topics on that slot. As we should book slots in about next 2 weeks, it would be great if You could do this doodle before e.g. end of next week (Friday 24th of April). BTW, we also have our etherpad [3] - please add Your name to it if You are planning to attend this virtual event. And please also add proposals of the topics which You want to be discussed there. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.ht… [2] https://doodle.com/poll/xcd82ea6svs5dben [3] https://etherpad.opendev.org/p/neutron-victoria-ptg -- Slawek Kaplonski Senior software engineer Red Hat

2 2

[release] Release countdown for week R-2, April 27 - May 1
by Sean McGinnis 25 Apr '20

25 Apr '20

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the Ussuri deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/ussuri branch creation for all deliverables that have not branched yet, using the latest available Ussuri release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/ussuri branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/ussuri branch before releasing out of the stable/ussuri branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for Victoria development, though the focus should still be on finishing up Ussuri until the final release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final Ussuri release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the Ussuri version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: May 7 (R-1 week) Final Ussuri release: May 13 Virtual Victoria PTG: June 1-5

2 1

[goals][Drop Python 2.7 Support] Week R-3 Update
by Ghanshyam Mann 25 Apr '20

25 Apr '20

Hello Everyone, Below is the progress on "Drop Python 2.7 Support" at end of R-3 week. Schedule: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html#sc… Highlights: ======== * Storlets is also keeping py2.7 support. py2.7 drop patches are reverted. * Aduit is finished and missing repos patches are also proposed. * Requesting projects listed below to merge the open patches asap. Project not completed the py2.7 drop: ============================ * adjutant-ui: https://review.opendev.org/#/c/714636/ * pythonclient: ** python-barbicanclient: https://review.opendev.org/#/c/699096/ *** gate is already broken. The last patch merged in this repo was 6 months ago so I am not sure it is maintained or not. ** python-zaqarclient: https://review.opendev.org/#/c/692011/ *** This also the same story, not maintained and job is broken already. ** python-adjutantclient https://review.opendev.org/#/c/723128/ * Deployment projects: *** Openstack Charms - Most of them merged, few failing on func job. *** Openstackansible - Centos7 jobs are failing on a few projects. *** Openstack-Helm - No conclusion yet on what else to do from Helm team. *** TripleO: Below repo are found to drop py2.7 during audit **** paunch: https://review.opendev.org/#/c/700560/ **** https://review.opendev.org/#/c/723125/ **** https://review.opendev.org/#/c/723126/ **** https://review.opendev.org/#/c/723127/ * Open review: https://review.opendev.org/#/q/topic:drop-py27-support+status:open Phase-3 status: I did the audit and found a few repos were missed. I have proposed the patches for those (listed above). All other projects have complete the work. I will discuss with the requirement team is anything needs to be done on the requirement side. I feel we should keep going with py2.7 cap in u-c. -gmann

1 0

[openstack-dev] [Tacker]
by Ivandro 24 Apr '20

24 Apr '20

Hello, I have been trying to install the tacker project in a VM, following the instruction from this url: https://docs.openstack.org/tacker/train/install/devstack.html based on devstack but unsuccessful. Is there a link to download an already installed VM with tacker? BR

6 15

Re: [release-announce] keystone_tempest_plugin 0.4.0 (ussuri)
by Thomas Goirand 24 Apr '20

24 Apr '20

On 4/23/20 9:32 PM, no-reply(a)openstack.org wrote: > We are amped to announce the release of: > > keystone_tempest_plugin 0.4.0: Tempest plugin keystone_tempest_plugin > > This release is part of the ussuri release series. > > The source is available from: > > https://opendev.org/openstack/keystone_tempest_plugin This one also has underscores instead of dashes... :/ Thomas

2 1

[user committee] Survey tool research
by Dincer Celik 24 Apr '20

24 Apr '20

Hi everyone! As Kolla project, we are looking for a survey tool to get feedback from our users. We are now on the comparison stage of some popular tools and would like to ask what user committee uses for the user surveys. The current tool seems hard coded to website but I would like to ask if it could be used for a custom survey. Best regards, Dincer

2 1