- openstack-discuss - lists.openstack.org

[election][designate] PTL candidacy for Wallaby
by Michael Johnson 28 Sep '20

28 Sep '20

My fellow OpenStack community, I would like to announce my candidacy for PTL of Designate for the Wallaby cycle. As you probably know I have been the Octavia PTL five times since the Pike release. I will continue to be involved in the Octavia project, but it is time for a change! I feel that allowing for leadership change on projects is healthy and gives others the opportunity to lead. In my downstream day job I am becoming more involved in supporting Designate as part of our OpenStack offering. This means I will be contributing more to Designate and supporting the Designate community. One of my Designate goals for the Wallaby release will be expanding the documentation available. For example, I would like to create some user cookbooks, similar to those in the Octavia documentation, that would guide users through scenarios using Designate. I am also excited to see a proposed patch for DNS “views” in Designate, so I will be supporting that development effort in any way I can help. Thank you for your support and your consideration for Wallaby, Michael Johnson (johnsom)

1 0

[tc] weekly update
by Mohammed Naser 28 Sep '20

28 Sep '20

Hi everyone,Here's an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. We've also included a few references to some important mailing list threads that you should check out. # Patches ## Open Reviews - Add assert:supports-standalone https://review.opendev.org/722399 - Add election schedule exceptions in charter https://review.opendev.org/751941 - Remove tc:approved-release tag https://review.opendev.org/749363 - Clarify impact on releases for SIGs https://review.opendev.org/752699 - Migrate rpm-packaging to a SIG https://review.opendev.org/752661 - Retire openstack/os-loganalyze https://review.opendev.org/753834 - Retire devstack-plugin-pika project https://review.opendev.org/748730 - Reorder repos alphabetically https://review.opendev.org/754097 - Add Ironic charms to OpenStack charms https://review.opendev.org/754099 - Define TC-approved release in a resolution https://review.opendev.org/752256 # Other Reminders - PTG Brainstorming: https://etherpad.opendev.org/p/tc-wallaby-ptg - PTG Registration: https://october2020ptg.eventbrite.com Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

TC Candidacy for Wallaby
by Amy Marrich 28 Sep '20

28 Sep '20

Hey all, I am declaring my candidacy for the Technical Committee. I have served in various leadership positions within the community over the years and feel I have developed a well rounded view of what goes on within OpenStack from the project level up to the OSF Board level. I feel I can represent all members of the community from the folks running small private clouds to the teams running large public clouds. I also feel my experiences helping with OpenStack Upstream Institute, the OpenStack mentoring program, and the Git and Gerrit workshops help me to connect with contributers from those just starting out to those who have been here from the beginning. While I'm admittedly not a developer by profession, I have code and documentation contributions in multiple projects which I think is important in seeing the big picture as to how pieces fit together in the larger OpenStack codebase. Thanks, Amy Marrich (spotz)

1 0

[neutron] Bug deputy report for week of September 21st
by Brian Haley 28 Sep '20

28 Sep '20

Hi, I was Neutron bug deputy last week. Below is a short summary about the 21 (!) reported bugs. -Brian Critical bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1896603 - ovn-octavia-provider: Cannot create listener due to alowed_cidrs validation - https://review.opendev.org/#/c/753302/ * https://bugs.launchpad.net/bugs/1896678 - [OVN Octavia Provider] test_port_forwarding failing in gate - https://review.opendev.org/#/c/753419/ * https://bugs.launchpad.net/neutron/+bug/1896766 - OVN jobs failing due to failed OVS compilation - https://review.opendev.org/#/c/751882/ * https://bugs.launchpad.net/neutron/+bug/1897326 - scenario test test_floating_ip_update is failing often on Ubuntu 20.04 - Possibly related to https://bugs.launchpad.net/neutron/+bug/1896735 - Slawek took ownership High bugs --------- * https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1896506 - keepalived_use_no_track default=True breaks bionic deploys - Needs owner * https://bugs.launchpad.net/neutron/+bug/1896677 - [OVN Octavia Provider] OVN provider fails creating pool without subnet ID - Assigned to haleyb * https://bugs.launchpad.net/neutron/+bug/1896735 - Scenario tests from neutron_tempest_plugin.scenario.test_port_forwardings.PortForwardingTestJSON failing due to ssh failure - https://review.opendev.org/#/c/753552/ proposed * https://bugs.launchpad.net/neutron/+bug/1896827 - port update api should not lose foreign external_ids - https://review.opendev.org/#/c/753833/ proposed * https://bugs.launchpad.net/neutron/+bug/1896945 - dnsmasq >= 2.81 not responding to DHCP requests with current q-dhcp configs - Looks similar to https://bugs.launchpad.net/neutron/+bug/1876094 but that fix is merged - Needs owner * https://bugs.launchpad.net/neutron/+bug/1897095 - [OVN] ARP/MAC handling for routers connected to external network is scaling poorly - https://review.opendev.org/#/c/752678/ proposed Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/1896470 - OVN migration infrared plugin does not remove ML2OVS-specific templates - https://review.opendev.org/#/c/752918/ proposed * https://bugs.launchpad.net/neutron/+bug/1896587 - iptables firewall driver don't drops invalid packets which match some SG rule - Fix for https://bugs.launchpad.net/neutron/+bug/1460741 moved this iptables chain lower, so more investigation required. * https://bugs.launchpad.net/tempest/+bug/1896592 - [neutron-tempest-plugin] test_dhcpv6_stateless_* clashing when creating a IPv6 subnet - Actually a bug in the tempest repo, added component - Fixed in neutron-tempest-plugin with https://review.opendev.org/#/c/560465/ - Marked Incomplete by Rodolfo as he noticed server issues (500's) in the logs * https://bugs.launchpad.net/neutron/+bug/1896733 - [FT] Error while executing "remove_nodes_from_host" method - Needs owner * https://bugs.launchpad.net/neutron/+bug/1896850 - dhcp release fails when client_id is specified - https://review.opendev.org/#/c/753865/ proposed * https://bugs.launchpad.net/neutron/+bug/1896933 - Exception when plugin creates a network without specifying the MTU - https://review.opendev.org/#/c/753717/ proposed Low bugs -------- * https://bugs.launchpad.net/neutron/+bug/1896588 - [Security Groups] When using neutron CLI, if non-existing project is given when listing the SGs, a default SG is created - Rodolfo working on it * https://bugs.launchpad.net/neutron/+bug/1897100 - Improve port listing command - https://review.opendev.org/#/c/754117/ proposed * https://bugs.launchpad.net/neutron/+bug/1897423 - [L3] Let agent extension do delete router first - https://review.opendev.org/#/c/736258/ proposed * https://bugs.launchpad.net/neutron/+bug/1895876 - When accounts.yaml is used neutron_tempest_plugin fails with "Invalid input for tenant_id. Reason: 'None' is not a valid string." - https://review.opendev.org/754782 proposed Wishlist bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1896920 - Unnecessary error log when checking if a device is ready - https://review.opendev.org/#/c/754005/ proposed Further triage required ----------------------- * None

1 0

[requirements][election] PTL candidacy for Wallaby
by Matthew Thode 28 Sep '20

28 Sep '20

I would like to announce my candidacy for PTL of the Requirements project for the Wallaby cycle. The following will be my goals for the cycle, in order of importance: 1. The primary goal is to keep a tight rein on global-requirements and upper-constraints updates. (Keep things working well) 2. Un-cap requirements where possible (stuff like botocore). 3. Audit global-requirements and upper-constraints for redundancies. One of the rules we have for new entrants to global-requirements and/or upper-constraints is that they be non-redundant. Keeping that rule in mind, audit the list of requirements for possible redundancies and if possible, reduce the number of requirements we manage. Json libs are on the short list this go around. I look forward to continue working with you in this cycle, as your PTL or not. Thanks for your time, -- Matthew Thode

1 0

[blazar][election] PTL candidacy for Wallaby
by Pierre Riteau 28 Sep '20

28 Sep '20

Hi, I would like to self-nominate for the role of PTL of Blazar for the Wallaby release cycle. I have been PTL since the Stein cycle and I am willing to continue. Unfortunately, Blazar has been suffering from low participation in the project. I will keep engaging with current users and potential new ones, in order to get more contributors involved in the project. Thank you for your support, Pierre Riteau (priteau)

1 0

[election][barbican] Add Douglas Mendizábal candidacy for Barbican PTL
by Douglas Mendizabal 28 Sep '20

28 Sep '20

Hello OpenStack, I would like to nominate myself for Barbican PTL. [1] My focus for the new cycle will be to continue the maintenance and development of the project. We will continue to improve usability as well as continue to enable cross-project encryption features. We hope to deliver our first microversion revision early in the Wallaby cycle, so tha we can finally release the Secret Consumers feature. Thanks, Douglas Mendizábal [1] https://review.opendev.org/#/c/754735/

1 0

[election][magnum] Add strigazi candidancy for magnum
by Spyros Trigazis 28 Sep '20

28 Sep '20

Hello stackers, I would like to nominate [0] myself for Magnum PTL. In the recent releases the focus of the team was around our kubernetes driver. I would like to continue that direction for wallaby while trying to improve cloud administrators' management. More specifically: * simplifying addon deployment for our kubernetes driver (the current proposal relies on helm3) * allow control plane resizing * optionally run the clusters' control plane on the cloud operators' tenant * investigate addon upgrades The goal of the project is clearly to be very lean and rely as much as possible on the dependent communities like: kubernetes, containerd, calico, helm and so on. Thank you for considering me, Spyros Trigazis [0] https://review.opendev.org/754727

1 0

[release] Release countdown for week R-2 Sept 28 - Oct 2
by Sean McGinnis 28 Sep '20

28 Sep '20

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the victoria deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- If you have deliverables on a cycle-with-rc model but haven't had a RC1 released yet, please check the proposed RC1 releases at [1]. Without a clear answer, the release management team will be approving those on Monday morning! [1] https://review.opendev.org/#/q/topic:victoria-rc1+status:open Early in the week, the release team will be proposing stable/victoria branch creation for all deliverables that have not branched yet, using the latest available victoria 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/victoria 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/victoria branch before releasing out of the stable/victoria 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 wallaby development, though the focus should still be on finishing up victoria 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 victoria release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targetted 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 victoria version of your project. Upcoming Deadlines & Dates -------------------------- Final Victoria release: October 14 Open Infra Summit: October 19-23 Wallaby PTG: October 26-30

1 0

[elections][placement][blazar] Placement PTL Non-candidacy: Stepping down
by Tetsuro Nakamura 28 Sep '20

28 Sep '20

Hello everyone, Due to my current responsibilities, I'm not able to keep up with my duties either as a Placement PTL, core reviewer, or as a Blazar core reviewer in Wallaby cycle. Thank you so much to everyone that has supported. I won't be able to checking ML or IRC, but I'll still be checking my emails. Please ping me via email if you need help. Thanks. - Tetsuro -- Tetsuro Nakamura <tetsuro.nakamura.bc(a)hco.ntt.co.jp> NTT Network Service Systems Laboratories TEL:0422 59 6914(National)/+81 422 59 6914(International) 3-9-11, Midori-Cho Musashino-Shi, Tokyo 180-8585 Japan

4 3

[Kuryr] Proposing Roman Dobosz for kuryr-kubernetes core
by Michał Dulko 28 Sep '20

28 Sep '20

Hello, I'd like to propose Roman for the core reviewer role in kuryr- kubernetes. Roman was leading several successful development activities during Train and Ussuri cycles: * Switch to use openstacksdk as our OpenStack API client. * Support for IPv6. * Moving VIF data from pod annotations to a KuryrPort CR. He also demonstrated code reviewing skills of an experienced Python developer. In the absence of objections, I'll proceed with adding Roman to the core team next week. Thanks, Michał

5 5

Re: [openstack-ansible] OpenStack Ansible deployment fails, due to lxc containers not having network connection
by Oliver Wenz 28 Sep '20

28 Sep '20

> I would recommend always building an All-In-One deployment in a virtual > machine > so that you have a reference to compare against when moving away from > the 'stock config'. > Documentation for the AIO can be found here > https://docs.openstack.org/openstack-ansible/ussuri/user/aio/quickstart.html I gradually decreased the complexity of my test system towards the 'stock config' to find out what caused the error but it kept showing up. Finally, it vanished when I rebooted the server and my original configuration also completed successfully afterwards. 🤦‍♂️ Thank you for your help and the insights to OSA! Kind regards, Oliver

1 0

[ptl][election][mistral] PTL candidacy
by Renat Akhmerov 28 Sep '20

28 Sep '20

Hi, I'm Renat Akhmerov. I'd like to announce my PTL candidacy for Mistral in Wallaby cycle. In Victoria, we made a huge change related to how we manage actions in Mistral. Previously, all actions were stored in the database and when any Mistral subsystem needed to get info about an action (action definition) it sent a query to DB. So, there wasn't any abstraction responsible for action management. This approach is not flexible and makes refactoring incredibly hard. It also means that it's nearly impossible to deliver actions to the system or alter them in runtime w/o having to reboot a cluster node. In Victoria we introduced the new abstraction called Action Provider. Action providers are fully responsible for delivering actions to Mistral. It is possible to. register many providers in the entry point "mistral.action.providers" in setup.cfg of any Python project (installed within the same Python env as Mistral) and Mistral will be using them all to find actions. So action management is now decoupled from the rest of the system and it's now possible to move away from storing action definitions only in the DB. It's fully up to a particular action provider implentation. Actions can even be dynamically generated, for example, as wrappers around a subset of operating system commands. Another option is. requesting info about actions via some communication protocols like HTTP, AMQP etc. There's still work to polish this all and document properly but the main infrastructure is already available and everyone can implement their own action providers. For W cycle I'd like to proceed with improving Mistral usability (toolset for developing Mistral actions, docs etc.) and address several known scalability issues. As always, anyone is very welcome to join our project. It's a lot of fun to work on it. The best way to get in touch with us is IRC channel #openstack-mistral or the openstack-discuss mailing list (with [mistral] tag in email subject). [1] https://review.opendev.org/#/c/754646/ Cheers Renat Akhmerov @Nokia

1 0

[tripleo][ci] proposing Yatin as tripleo-ci core
by Wesley Hayutin 28 Sep '20

28 Sep '20

Greetings, I really thought someone else had already sent this out. However I don't see it so here we go. I'd like to propose Yatin Karel as tripleo-ci core. You know you want to say +2 :)

19 18

[adjutant][election] PTL candidacy for Wallaby
by Adrian Turjak 27 Sep '20

27 Sep '20

Hello All, I'm submitting myself as the PTL for Adjutant during the W cycle. The focus is as always to continue maintaining the project to ensure it is operating as expected and as bug free as possible. Wallaby will mostly be about cleaning up some internal systems, and minor features to help with custom plugin support. The hope is to also clean up policy/role in this release, and include some elements of that into the plugin layer, and to start working on more useful user management features. Depending on time and resources, we may start work on async worker support to allow some parts of tasks to be processed asynchronously. Cheers, Adrian Turjak

1 0

[all][elections][ptl][tc] Combined PTL/TC Nominations ending soon
by Jeremy Stanley 27 Sep '20

27 Sep '20

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Sep 29, 2020 23:45 UTC. 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 @ 2020-09-22 23:45:00 UTC Nominations end @ 2020-09-29 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 1 day, 23:12:19 Nominations progress : 71.90% --------------------------------------------------- Projects[1] : 55 Projects with candidates : 18 ( 32.73%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 37 (Adjutant Barbican Blazar Cinder Cloudkitty Cyborg Designate Ec2_Api Freezer Horizon Ironic Karbor Magnum Manila Masakari Mistral Monasca Murano Octavia OpenStack_Charms OpenStack_Helm Oslo Packaging_Rpm Placement Qinling Quality_Assurance Rally Requirements Searchlight Senlin Solum Storlets Tacker Telemetry Trove Watcher Zun) =================================================== Stats gathered @ 2020-09-28 00:32:41 UTC This means that with approximately 2 days left, 37 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… -- Jeremy Stanley on behalf of the OpenStack Technical Election Officials

1 1

[election][tacker] PTL candidacy for Wallaby
by Yasufumi Ogawa 27 Sep '20

27 Sep '20

Hi, I'd like to propose my candidacy for Tacker PTL in Wallaby cycle. In Victoria release, we have released great features required for the latest ETSI NFV standard and made several improvements for Tacker as and as planed in the last vPTG. We also fix issues for migrating to python3 and Ubuntu focal. As a PTL, I've led the team by proposing not only new features, but also things for driving the team such as documentation or bug tracking. It was something hard, but is running well. In Wallaby cycle, I would like to continue to make Tacker be more useful product from not only telco, but also all users interested in NFV. I believe Tacker will be a good reference implementation for NFV standard. We have planed to make Tacker more feasible not only for VM environment, but also container to meet requirements from industries. - Introduce the latest container technology with ETSI NFV standard. - Reinforce test environment for keeping the quality of the product, not only unit tests and functional tests, but also introduce more sophisticated scheme such as robot framework. - Revise wiki and documentation for covering users more. Regards, Yasufumi Ogawa

1 0

[election][heat] PTL candidacy for Wallaby
by Rico Lin 27 Sep '20

27 Sep '20

Hi all, I would like to announce my candidacy for Heat PTL for Wallaby cycle. Over the past couple of cycles, we running Heat dynamically according to requirements. We never stop encouraging people to join us and provide consistent reviews or fixes as much as we can based on priorities. And if those priorities not working for you, that means you must join the community to help. I believe the goals for the next cycle should be community CI stability, cross-project/community scenario tests to ensure what we deliver to users will get higher quality, also to get rid of legacy mode and move everything to convergence mode, and finally container-native support to make sure we provide usable Orchestration services for the container environment. I believe in new features, so we will try to encourage more features and review them as many as possible, but will not plan for team feature goals unless we can trigger more discussion and hands-on.Thank you for taking my self-nomination into consideration. -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

API short reponse time between the S version and the U version
by Zhi CZ Chang 26 Sep '20

26 Sep '20

1 0

[election][swift] PTL candidacy for Wallaby
by Tim Burke 26 Sep '20

26 Sep '20

I'd like to announce my candidacy for Swift PTL for the Wallaby cycle. This past year, Swift celebrated ten years running in production. Much has changed in that time: new features have been developed and polished, versions of Python have come and gone, and clusters have grown to staggering capacities. However, our commitment to operational excellence remains the same. Recently (particularly in the last several months), I've noticed our contributors increasingly have an operator's mindset. We look for more and better ways to measure Swift. We seek to reduce client impacts from config reloads and upgrades. We take greater ownership over the health and performance of our clusters. To a large extent, we're all operators now. The benefits have been enormous. We've improved performance; we've upgraded without disrupting any client requests; we've migrated clusters to Python 3 to position them well for the next ten years. Through it all, clients put ever more data into Swift. The increases in demand bring almost incomprehensible scales. We now see individual clusters sustaining tens of thousands of requests every second. We see containers with a billion objects. We see expansions that are as large as many whole clusters were just a few years ago. This is our next great challenge: how do we move away from a world where expansions are a rarity that may require a bit of a scramble and into a world of constant expansion? How can we effectively manage clusters with thousands of nodes? How do we shift from thinking in terms of petabytes to exabytes? I can't wait to see how we rise to meet this challenge. Tim Burke

1 0

The question about OpenStack instance fail to boot after unexpected compute node shutdown
by Yule Sun 26 Sep '20

26 Sep '20

I saw your message on the website http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005635.ht… . And i have been troubled by the same problem for a long time . I tried to change the parameters resume_guests_state_on_host_boot=True and instance_usage_audit=True in the nova.conf ,but it didn't work . I wonder if you have solved this problem, looking forward your reply, Thank you and best regards. And my instance error looks like this . [cid:e8770762-d2b2-4630-9ce6-4d357dc92cee]

2 1

[election][zaqar] PTL candidacy for Wallaby
by hao wang 26 Sep '20

26 Sep '20

Hi, I want to propose my candidacy and continue serving as Zaqar PTL in the Wallaby cycle. For the Victoria release, the Zaqar team continues to keep the Zaqar stable and reliable, and also some great works have been done. We designed and implemented the Encrypted message in the queue to enhance the security of Zaqar. We also fixed some bugs to meet the python3 requirements. In the Wallaby cycle, I would like to continue serving this project and bring more contributors and the user requires. There are some major works I want to do in W cycle: 1.Finish the Topic resource work, to support all backends. 2.Consider to support more backends that have widely used. 3.Continue to support more security algorithms for encrypted messages. 4.Implement some new requirements from users. 5.keep Zaqar more reliable as usual. Thanks to everyone to support my work and keep contributing to Zaqar. I will do my best in the new cycle.

1 0

[openstack-ansible][election] Candidacy
by Dmitriy Rabotyagov 25 Sep '20

25 Sep '20

Hey everyone! This cycle I've decided to take part in elections and run for PTL of the OpenStack-Ansible project. I feel that OSA nowadays is a solid and stable project, and we're doing a great job to get all features in time and deploy only modern software with our deployments, as well as providing deployers with a high range of different supported options and flexibility. It's rather important to keep up with the progress. And there are main things I'd love to focus on during the upcoming release: # Integration tests coverage for all roles Despite migrating tests for most of the projects to the integrated repo, we still have several projects not covered with proper testing (like Zun). I also would love to pay attention to passing appropriate tempest scenarios for all projects instead of running some default ones. # Cleaning up bugtracker I think one of our highest priorities should be project stability. And taking care of bugs might help us heavily with that. We haven't been paying enough attention to our Launchpad for a while and I think we should change that by cleaning up stale bugs, so we could focus on real ones. Returning bug triage to the meeting might be also an efficient way to handle them. # Roles cleanup We have a lot of things left in code, like workarounds for upgrades, upstream bugs, support for obsolete operating systems, etc. Removal/replacement of deprecated OpenStack options should be also included. # Usage of the new pip resolver Our venv build process relies on provided constraints heavily, which isn't valid in case of the new pip resolver usage, so we will need to make appropriate adjustments into the process to keep the ability to define specific package requirements and use modern pip. Thank you for taking into consideration my nomination.

1 0

Re: [magnum][infra] Can We Delete the OpenDev Fedora Atomic Images Mirror
by feilong＠catalyst.net.nz 25 Sep '20

25 Sep '20

1 0

OpenstackSwift - rclone Copy/Sync Large Objects set (150Mil objects - 80TB) from Tenant PROD1 to PROD2
by prem shivakumar 25 Sep '20

25 Sep '20

Hi Open-stack users, Our current setup: PROD1 Container1 Dir1/Dir2/YYYYMMDD.tar Want to move to: PROD2 Container2_YYYYMM Dir1/Dir2/YYYYMMDD.tar I got all the objects metadata(Object names) using “swift list Container1” I am currently using rclone where I am passing metadata(Object names) info of “Container1”. All the Auth variables exist in rclone.conf. Example command: rclone copy PROD1: Dir1/Dir2/YYYYMMDD.tar PROD2:Container2_YYYYMM/Dir1/Dir2/ YYYYMMDD.tar Currently, I am facing slowness in copying files from PROD1 to PROD2. On an average, It takes about 5s to copy the object from PROD1 to PROD2. If I count the time against 150M its more than 10000Days. I have also tried “rclone sync with —fast-list” it is failing as it is unable to keep the listing in the memory. In this case, is there any easier and faster solution to copy data from Container1 to Container2? Thank you.

1 0

[magnum][infra] Can We Delete the OpenDev Fedora Atomic Images Mirror
by Clark Boylan 25 Sep '20

25 Sep '20

I'm in the process of removing our fedora-30 images and noticed that we are still mirroring Fedora Atomic 28 and 29 images here: https://mirror.dfw.rax.opendev.org/fedora/atomic/stable/. Are these images in use anywhere? I would like to clean them up as they are even more stale than the fedora-30 nodepool images. Using http://codesearch.openstack.org I don't see anything using them but that only searches the master branches of our git repos. Clark

3 3

[election][kolla] PTL candidacy for Wallaby
by Mark Goddard 25 Sep '20

25 Sep '20

Hi, I'd like to nominate myself to serve as the Kolla PTL for the Wallaby cycle. I have been PTL for the last 3 cycles, and would like the opportunity to continue to lead the team. I am pleased with the current state of the project. We have an active community, produce interesting and useful features, and regularly receive positive feedback. As with many contributors in a less certain world, I have felt the squeeze on upstream this cycle. I'd like to thank those who have stepped up to help when downstream (or holiday) means I'm unavailable, and those who generally help out with project admin tasks. This cycle we added two new meetings to the calendar. Kolla Klub started well, with fantastic attendance and some great discussions. Over time engagement has been more variable. I think we need to assess whether to continue regular meetings, and if so, how to keep it interesting. The Kolla Kall is more development oriented, and has been useful for focussing on some specific issues. For this meeting I think we need to be sure that it is the best use of people's time, and be a bit more dynamic about content and attendance. One area where I feel we could improve as a project is in integrating contributors in non-EU/US time zones. Language, culture and time zones can make this a challenge, but everyone benefits from a connected global community. We made a start on improving our documentation this cycle, let's keep pushing on that. Thanks for reading, Mark Goddard (mgoddard)

1 0

[InteropWG] Looking for k8s Ready OpenStack / Open Infra and BMaaS Add-on Conformance Candidates
by prakash RAMCHANDRAN 25 Sep '20

25 Sep '20

Hi all, Here is summary of Friday alternate week calls of Interop(next Oct 9th) join us on meetpad - refer https://etherpad.opendev.org/p/interop We are looking forward to prep work for PTG on October23 Monday & October 30 Friday Interop slots ( https://ethercalc.openstack.org/7xp2pcbh1ncb ) 1. Seeking Candidate for "Kubernetes Ready OpenStack" Branding - need Ideation from different Project teams with variations you seek (see eg.) eg. Distros RHSOP with Cinder CSIVIO with Swift CSI eg. Hosted version Canonical OpenStack Distro with Manila CSISUSE OpenStack with Octavia Load Balances Ingress Controller Add your ideas to - https://etherpad.opendev.org/p/2020-Wallaby-interop-brainstorming 2. Seeking Candidates for OpenStack ready Bare Metal as a Service Add-ons IronicMaaS Add your ideas to - https://etherpad.opendev.org/p/2020-Wallaby-interop-brainstorming All Vendors and PTLs interested in pursuing ideas for their next releases OpenStack or Open Infra release please add your ideas to etherpads above.Reply to this chain and we will try consolidate Interop in Bare metal & K8s era. ThanksPrakash / MarkFor InteropWG

1 0

[tripleo]] tripleo victoria rc1
by Marios Andreou 25 Sep '20

25 Sep '20

hello TripleO folks o/ we don't normally/aren't expected to cut release candidates. However after discussion with and guidance from Wes I decided to propose an rc1 as practice since I haven't used the new releases tool before [4]. The proposal is up at [1] but I've set -1 there on request from reviewers; we can't merge that until [2] merges first. If you are interested please check [1] and add any comments. In particular let me know if you want to include a release for one of the independent repos [3] (though for validations-common/libs we need to reach out to the validations team they are managing those AFAIK). thanks, hope you enjoy your weekend! [1] https://review.opendev.org/#/c/754346/ [2] https://review.opendev.org/754347 [3] https://releases.openstack.org/teams/tripleo.html#independent [4] https://releases.openstack.org/reference/using.html#using-new-release-comma…

1 0

[openstack][manila] GenericShareDriver on stein
by Ignazio Cassano 25 Sep '20

25 Sep '20

Hello Stackers, I am testing manila manila.share.drivers.generic.GenericShareDriver with manila.share.drivers.generic.GenericShareDriver. I created in my project an instance with nfs server and it is up and running. In my manila.conf I have specified the instance id, use and password: [locale] share_driver = manila.share.drivers.generic.GenericShareDriver driver_handles_share_servers = false share_backend_name= locale service_instance_user = manila service_instance_passwod = manila service_instance_name_or_id = 5b0fa246-e94b-4a84-b730-7066dfb31fb0 path_to_private_key=~/.ssh/id_rsa path_to_public_key=~/.ssh/id_rsa.pub I have also other backend with netapp drivers and they works fine. The generic drivers reports: 2020-09-25 13:56:13.955 4097174 WARNING manila.share.drivers.generic [req-f0a5294a-3ef2-4226-9fc9-f3b4f35c53f5 - - - - -] Waiting for the common service VM to become available. Driver is currently uninitialized. Share server: None Retry interval: 5 2020-09-25 13:56:14.143 4097174 ERROR manila.share.drivers.generic [req-f0a5294a-3ef2-4226-9fc9-f3b4f35c53f5 - - - - -] string indices must be integers 2020-09-25 13:56:19.144 4097174 WARNING manila.share.drivers.generic [req-f0a5294a-3ef2-4226-9fc9-f3b4f35c53f5 - - - - -] Waiting for the common service VM to become available. Driver is currently uninitialized. Share server: None Retry interval: 5 2020-09-25 13:56:19.340 4097174 ERROR manila.share.drivers.generic [req-f0a5294a-3ef2-4226-9fc9-f3b4f35c53f5 - - - - -] string indices must be integers Seems the instance I created is not available. Please, any help? Ignazio

2 2

[election][Kuryr] PTL candidacy for Wallaby
by Maysa De Macedo Souza 25 Sep '20

25 Sep '20

Hello, I would like to propose my candidacy to be the PTL of Kuryr for the Wallaby cycle. I have been a contributor to Kuryr since the Queens release and was appointed to the Kuryr core team in the Ussuri cycle. I see the following goals for the Kuryr project during the Wallaby cycle: * Improve stability and extend CI: we already included great improvements in our CI, but I believe we must continuously work on it to provide better and quicker feedback when developing new features. As part of that, we should start graduating experimental jobs like the ones using OVN-Octavia driver and Network Policy, and handle issues with jobs requiring more swap. * Address testing gaps for new and existing features: this would avoid regressions and find bugs. Also, improves stability. * Continue extending and improving Kuryr functionalities, such as dual stack, SCTP support and CRDs usage. * Grow the contributor base. I would like to contribute back to the community as a PTL while following great examples of previous PTLs. Thank you, Maysa.

1 0

[rpm-packaging] Proposing Hervé Beraud as new core reviewer
by Javier Pena 25 Sep '20

25 Sep '20

Hi, I would like to propose Hervé Beraud as a new core reviewer for the rpm-packaging project. Hervé has been providing consistently good reviews over the last few months, and I think he would be a great addition to the core reviewer team. Existing cores, please vote on the thread! Regards, Javier Peña

3 3

[tc] monthly meeting
by Mohammed Naser 25 Sep '20

25 Sep '20

Hi everyone, Our monthly TC meeting is scheduled for next Thursday, October 1st, at 1400 UTC. If you would like to add topics for discussion, please go to https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and fill out your suggestions by Wednesday, September 30th, at 1900 UTC. Thank you, Regards, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[tripleo] PTL candidacy for Wallaby
by Marios Andreou 25 Sep '20

25 Sep '20

I would like to nominate myself for the TripleO PTL role for the Wallaby cycle. I think it is obvious that the role of the PTL has changed significantly compared to the early days of TripleO. Most importantly we are (and have been for a while) now organised into self-contained topic squads (deployment, validations, upgrades, networking, storage, ci, etc). Typically technical decisions are driven exclusively within those squads (even if they are done 'in the open' on gerrit and launchpad and opendev-discuss). The role of the PTL then is more about coordination across the squads, ensuring we deliver release targets, keeping bug backlogs in order and facilitating the resolution of any conflicts that arise. I have worked on TripleO since before the Kilo release and have collaborated with many current and past members of the community including engineers and also users/operators. My contributions thus far have been in code/docs/bugs, originally working on upgrades and more recently working on CI. I haven't had the opportunity to work on the 'admin' side of TripleO (besides in the past cutting the occasional release). I am thus especially excited by the prospect of contributing in this new way as PTL, if TripleO will have me! I sincerely promise to give it my best and I am sure that together with the kind help of the current PTL Wes Hayutin we will have a smooth Wallaby cycle, meeting our responsibilities to the foundation and the community. There is (as ever!) a lot of exciting work coming in the Victoria release and continuing in Wallaby including the continued exploration of the removal of Heat as our configuration engine, the new validations repos and framework, the new container builds process, Fast Forward Upgrades II (back with a vengeance), ci component and dependency pipelines, ci parent/child jobs, and I'm sure many more that we will discuss at the coming Wallaby PTG. Two areas I would like to focus on as PTL should you give me the opportunity are: - improve our current documentation/deployment guides - at minimum they must be updated to recent releases and there are many items missing. I am hoping to rally support from the various squads for this. - improve visibility into the various TripleO squads - this may mean re-instating a 'new' weekly/bi-weekly (or other frequency) tripleo meeting or by some new way of collaborating. Again this is really dependent on support from the tripleo community. thank you for your consideration!

1 0

[Neutron] Not create .2 port
by Tony Liu 24 Sep '20

24 Sep '20

Hi, When create a subnet, by default, the first address is the gateway and Neutron also allocates an address for serving DHCP and DNS. Is there any way to NOT create such port when creating subnet? Thanks! Tony

3 4

[election][neutron] PTL candidacy for Wallaby
by Slawek Kaplonski 24 Sep '20

24 Sep '20

Hi, I want to propose my candidacy and continue serving as Neutron PTL in the Wallaby cycle. In the Victoria cycle I proposed a couple of major goals. We achieved most of them, like for example: * add support for metadata over IPv6 in Neutron, * continue adoption of the OVN driver as one of the in-tree Neutron drivers. * find new maintainers for the networking-midonet project so we keep it the * Neutron stadium. In the upcoming cycle I would like to continue work which we started already and focus mostly on: * implement old, unfinished Blueprints like adoption of new engine facade, * continue adoption of the OVN backend in Neutron, closing more feature parity * gaps * switch the OVN driver to be the default backend in Devstack, In addition to the goals mentioned above mentioned, I want to continue work to improve our CI stability and coverage. It is my continuing desire to do my best to help our outstanding team to deliver better software and to grow. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] Drivers meeting agenda - 25.09.2020
by Slawek Kaplonski 24 Sep '20

24 Sep '20

Hi, For tomorrows drivers meeting we again don't have any new RFEs to discuss but I wanted to use this meeting to quickly discuss about 1 bug: https://bugs.launchpad.net/neutron/+bug/1895933 So see You on tomorrows meeting :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[all][election][TC] Candidacy
by Kendall Nelson 24 Sep '20

24 Sep '20

Hello Everyone! I am once again declaring my candidacy for the Technical Committee. This last year I have learned so much about OpenStack and our amazing community. There is never a shortage of work to be done and I feel there is still a lot I can do to help the community as a part of the TC. I served as TC Vice Chair during the second half of my term and I felt like I was able to do a lot to help support Mohammed, the chair and other members of the TC. My work in coordinating the new office hours and our time at the upcoming PTG will enable the future TC to be more accessible and productive. I also lead the community goal to improve the onboarding documentation, further lowering the barrier for new contributors. If elected, I will continue bridging our community with the kubernetes community. I am actively facilitating the conversations between the TC and the k8s Technical Steering Committee at the upcoming PTG meetings to share insight between both of our communities and generally share knowledge about keeping open source communities healthy. I would also like to take a more active role in pushing the unification of the community around a single CLI to simplify openstack operations to better support our users and lessen the load on developers. I think a good first step would be to work with the CLI/SDK team to build a list of items that are blocking project teams from fully implementing all their features in the openstack client. From there we can figure out what is missing from the list, which teams are affected by which blocking items and prioritize what needs to be worked on first. Thank you for your time and consideration. As I said in my platform last year, I love this community and all the awesome people in it, serving on the TC is a great experience and an honor. -Kendall Nelson (diablo_rojo)

1 0

[ironic] Recovering IPMI-type baremetal nodes in 'error' state
by Paul Browne 24 Sep '20

24 Sep '20

Hello all, I have a handful of baremetal nodes enrolled in Ironic that use the IPMI hardware type, whose motherboards were recently replaced in a hardware recall by the vendor. After the replacement, the BMC IPMI-over-LAN feature was accidentally left disabled on the nodes, and future attempts to control them with Ironic has put these nodes into the ERROR provisioning state. The IPMI-over-LAN feature on the boards has been enabled again as expected, but is there now any easy way to get the BM nodes back out of that ERROR state, without first deleting and re-enrolling them? -- ******************* Paul Browne Research Computing Platforms University Information Services Roger Needham Building JJ Thompson Avenue University of Cambridge Cambridge United Kingdom E-Mail: pfb29(a)cam.ac.uk Tel: 0044-1223-746548 *******************

2 3

LVM misconfiguration after openstack stackpack server hang and reboot
by Alan Davis 24 Sep '20

24 Sep '20

This morning my CentOS 7.7 RDO packstack installation of Rocky hung. On reboot some of the VMs won't start. This is a primary system and I need to find the most expedient way to recover without losing data. I'm not using LVM thin volumes. Any help is appreciated. Looking at nova-compute.log I see errors trying to find LUN 0 during the sysfs stage. Several machines won't boot because their root disk entries in LVM are seen as PV and booting them doesn't see them in the DM subsystem. Other machines boot but there attached disks throw LVM errors about duplicate PV and preferring the cinder-volumes VG version. LVM is showing LVs that have both "bare" entries as well as entries in cinder-volumes and it's complaining about duplicate PVs, not using lvmetad and preferring some entries because they are in the dm subsystem. I've verified that, so far, I haven't lost any data. The "bare" LV not being used as part of the DM subsystem because it's server won't boot can be mounted on the openstack host and all data on it is accessible. This host has rebooted cleanly multiple times in the past. This is the first time it's shown any problems. Am I missing an LVM filter? (unlikely since it wasn't neede before) How can I reset the LVM configuration and convince it that it's not seeing duplicate PV? How do I ensure that openstack sees the right UUID and volume ID? Excerpts from error log and output of lvs : --- nova-compute.log --- during VM start 2020-09-24 11:15:27.091 13953 INFO os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - default default] Trying to connect to iSCSI portal 172.10.0.40:3260 2020-09-24 11:15:29.721 13953 WARNING nova.compute.manager [req-fd32e16f-c879-402f-a32c-6be45a943c34 48af9a366301467d9fec912fd1c072c6 f9fc7b412a8446d083da1356aa370eb4 - default d efault] [instance: de7d740c-786a-4aa2-aa09-d447ae7e14b6] Received unexpected event network-vif-unplugged-79aff403-d2e4-4266-bd88-d7bd19d501a9 for instance with vm_state stopped a nd task_state powering-on. 2020-09-24 11:16:21.361 13953 WARNING os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d 1c8 - default default] LUN 0 on iSCSI portal 172.10.0.40:3260 not found on sysfs after logging in. 2020-09-24 11:16:23.482 13953 INFO os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - default default] Trying to connect to iSCSI portal 172.10.0.40:3260 2020-09-24 11:17:17.741 13953 WARNING os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d 1c8 - default default] LUN 0 on iSCSI portal 172.10.0.40:3260 not found on sysfs after logging in.: VolumeDeviceNotFound: Volume device not found at . 2020-09-24 11:17:21.864 13953 INFO os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - default default] Trying to connect to iSCSI portal 172.10.0.40:3260 2020-09-24 11:18:16.113 13953 WARNING os_brick.initiator.connectors.iscsi [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d 1c8 - default default] LUN 0 on iSCSI portal 172.10.0.40:3260 not found on sysfs after logging in.: VolumeDeviceNotFound: Volume device not found at . 2020-09-24 11:18:17.252 13953 INFO nova.compute.manager [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - default defa ult] [instance: de7d740c-786a-4aa2-aa09-d447ae7e14b6] Successfully reverted task state from powering-on on failure for instance. 2020-09-24 11:18:17.279 13953 ERROR oslo_messaging.rpc.server [req-8d15fb6a-6324-471e-9497-587885eef8f6 396aeda6552f44fdac5f878b90325ee1 54af92f2bb494355b96024076184d1c8 - defaul t default] Exception during message handling: VolumeDeviceNotFound: Volume device not found at . 2020-09-24 11:18:17.279 13953 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2020-09-24 11:18:17.279 13953 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 163, in _process_incoming 2020-09-24 11:18:17.279 13953 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) --- lvs output --- I've annotated 1 machine's disks to illustrate the relationship between the volume-*** cinder-volumes vg entries and the "bare" lv seen as directly accessible from the host. There are 3 servers that won't boot, they are the one's who's home/vg_home and encrypted_home/encrypted_vg entries are shown. WARNING: Not using lvmetad because duplicate PVs were found. WARNING: Use multipath or vgimportclone to resolve duplicate PVs? WARNING: After duplicates are resolved, run "pvscan --cache" to enable lvmetad. WARNING: Not using device /dev/sdu for PV yZy8Xk-foKT-ovjV-0EZv-VxEM-GqiP-WH7k53. == backup_lv/encrypted_vg WARNING: Not using device /dev/sdv for PV tHA9ui-eSIO-MDmI-RM3u-3Bf4-Dznb-Ha3XfP. == varoptgitlab/encrypted_vg WARNING: Not using device /dev/sdm for PV 5eoyCa-sMO4-b7O4-jIfh-byZE-L5pS-3lOu0D. WARNING: Not using device /dev/sdp for PV 3BI0nV-TP0k-rgPC-PrjH-FT7z-reMe-ec1spj. WARNING: Not using device /dev/sdt for PV ILdbcY-VFCm-fnH6-Y3jc-pdWZ-fnl8-PH3TPe. == storage_lv/encrypted_vg WARNING: Not using device /dev/sdr for PV zowU2N-oaBh-r4cO-cxgX-YYiq-Kf3q-mqlHfK. WARNING: PV yZy8Xk-foKT-ovjV-0EZv-VxEM-GqiP-WH7k53 prefers device /dev/cinder-volumes/volume-c8da1abf-7143-422c-9ee5-b2724a71c8ff because device is in dm subsystem. WARNING: PV tHA9ui-eSIO-MDmI-RM3u-3Bf4-Dznb-Ha3XfP prefers device /dev/cinder-volumes/volume-0a12012f-8c2e-41fb-aa0c-a7ae99c62487 because device is in dm subsystem. WARNING: PV 5eoyCa-sMO4-b7O4-jIfh-byZE-L5pS-3lOu0D prefers device /dev/cinder-volumes/volume-990a057c-46cc-4a81-ba02-28b72c34791d because device is in dm subsystem. WARNING: PV 3BI0nV-TP0k-rgPC-PrjH-FT7z-reMe-ec1spj prefers device /dev/cinder-volumes/volume-b6a9da6e-1958-46ea-90b4-ac1aebed8c04 because device is in dm subsystem. WARNING: PV ILdbcY-VFCm-fnH6-Y3jc-pdWZ-fnl8-PH3TPe prefers device /dev/cinder-volumes/volume-302dd53b-7d05-4f6d-9ada-8f2ed6e1d4c6 because device is in dm subsystem. WARNING: PV zowU2N-oaBh-r4cO-cxgX-YYiq-Kf3q-mqlHfK prefers device /dev/cinder-volumes/volume-df006472-be7a-4957-972a-1db4463f5d67 because device is in dm subsystem. LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert home centos_stack3 -wi-ao---- 4.00g root centos_stack3 -wi-ao---- 50.00g swap centos_stack3 -wi-ao---- 4.00g _snapshot-05b1e46b-1ae3-4cd0-9117-3fb53a6d94b0 cinder-volumes swi-a-s--- 20.00g volume-1d0ff5d5-93a3-44e8-8bfa-a9290765c8c6 0.00 lv_filestore cinder-volumes -wi-ao---- 1.00t ... volume-c8da1abf-7143-422c-9ee5-b2724a71c8ff cinder-volumes -wi-ao---- 100.00g volume-0a12012f-8c2e-41fb-aa0c-a7ae99c62487 cinder-volumes -wi-ao---- 60.00g volume-990a057c-46cc-4a81-ba02-28b72c34791d cinder-volumes -wi-ao---- 200.00g volume-b6a9da6e-1958-46ea-90b4-ac1aebed8c04 cinder-volumes -wi-ao---- 30.00g volume-302dd53b-7d05-4f6d-9ada-8f2ed6e1d4c6 cinder-volumes -wi-ao---- 60.00g volume-df006472-be7a-4957-972a-1db4463f5d67 cinder-volumes -wi-ao---- 250.00g ... volume-f3250e15-bb9c-43d1-989d-8a8f6635a416 cinder-volumes -wi-ao---- 20.00g volume-fc1d5fcb-fda1-456b-a89d-582b7f94fb04 cinder-volumes -wi-ao---- 300.00g volume-fc50a717-0857-4da3-93cb-a55292f7ed6d cinder-volumes -wi-ao---- 20.00g volume-ff94e2d6-449b-495d-82e6-0debd694c1dd cinder-volumes -wi-ao---- 20.00g data2 data2_vg -wi-a----- <300.00g data data_vg -wi-a----- 1.79t backup_lv encrypted_vg -wi------- <100.00g == ...WH7k53 storage_lv encrypted_vg -wi------- <60.00g == ...PH3TPe varoptgitlab_lv encrypted_vg -wi------- <200.00g varoptgitlab_lv encrypted_vg -wi------- <30.00g varoptgitlab_lv encrypted_vg -wi------- <60.00g == ...Ha3XfP encrypted_home home_vg -wi-a----- <40.00g encrypted_home home_vg -wi------- <60.00g pub pub_vg -wi-a----- <40.00g pub_lv pub_vg -wi------- <250.00g rpms repo -wi-a----- 499.99g home vg_home -wi-a----- <40.00g gtri_pub vg_pub -wi-a----- 20.00g pub vg_pub -wi-a----- <40.00g -- Alan Davis Principal System Administrator Apogee Research LLC

1 1

[Glance] PTL on Vacation
by Abhishek Kekane 24 Sep '20

24 Sep '20

Hi All, I'm starting my vacations from 28th September and will be back on October 5th. Please direct any issues to the rest of the core team. Also there will be no glance weekly meeting on 01 October [1]. [1] https://etherpad.opendev.org/p/glance-team-meeting-agenda Thanks, Abhishek

1 0

[all][tc][goals] Migrate CI/CD jobs to new Ubuntu LTS Focal: Week R-4 Update
by Ghanshyam Mann 24 Sep '20

24 Sep '20

Hello Everyone, Please find the week R-4 updates on 'Ubuntu Focal migration' community goal. Its time to force the base jobs migration which can break the projects gate if not yet taken care of. Read below for the plan. Tracking: https://storyboard.openstack.org/#!/story/2007865 Progress: ======= * We are close to V-3 release and this is time we have to complete this migration otherwise doing it in RC period can add unnecessary and last min delay. I am going to plan this migration in two-part. This will surely break some projects gate which is not yet finished the migration but we have to do at some time. Please let me know if any objection to the below plan. * Part1: Migrating tox base job tomorrow (8th Sept): ** I am going to open tox base jobs migration (doc, unit, functional, lower-constraints etc) to merge by tomorrow. which is this series (all base patches of this): https://review.opendev.org/#/c/738328/ . **There are few repos still failing on requirements lower-constraints job specifically which I tried my best to fix as many as possible. Many are ready to merge also. Please merge or work on your projects repo testing before that or fix on priority if failing. * Part2: Migrating devstack/tempest base job on 10th sept: * We have few open bugs for this which are not yet resolved, we will see how it goes but the current plan is to migrate by 10th Sept. ** Bug#1882521 ** DB migration issues, *** alembic and few on telemetry/gnocchi side https://github.com/sqlalchemy/alembic/issues/699, https://storyboard.openstack.org/#!/story/2008003 Testing Till now: ============ * ~200 repos gate have been tested or fixed till now. ** https://review.opendev.org/#/q/topic:migrate-to-focal+(status:abandoned+OR+… * ~100 repos are under test and failing. Debugging and fixing are in progress (If you would like to help, please check your project repos if I am late to fix them): ** https://review.opendev.org/#/q/topic:migrate-to-focal+status:open * ~30repos fixes ready to merge: ** https://review.opendev.org/#/q/topic:migrate-to-focal+status:open+label%3AV… Bugs Report: ========== 1. Bug#1882521. (IN-PROGRESS) There is open bug for nova/cinder where three tempest tests are failing for volume detach operation. There is no clear root cause found yet -https://bugs.launchpad.net/cinder/+bug/1882521 We have skipped the tests in tempest base patch to proceed with the other projects testing but this is blocking things for the migration. 2. DB migration issues (IN-PROGRESS) * alembic and few on telemetry/gnocchi side https://github.com/sqlalchemy/alembic/issues/699, https://storyboard.openstack.org/#!/story/2008003 3. We encountered the nodeset name conflict with x/tobiko. (FIXED) nodeset conflict is resolved now and devstack provides all focal nodes now. 4. Bug#1886296. (IN-PROGRESS) pyflakes till 2.1.0 is not compatible with python 3.8 which is the default python version on ubuntu focal[1]. With pep8 job running on focal faces the issue and fail. We need to bump the pyflakes to 2.1.1 as min version to run pep8 jobs on py3.8. As of now, many projects are using old hacking version so I am explicitly adding pyflakes>=2.1.1 on the project side[2] but for the long term easy maintenance, I am doing it in 'hacking' requirements.txt[3] nd will release a new hacking version. After that project can move to new hacking and do not need to maintain pyflakes version compatibility. 5. Bug#1886298. (IN-PROGRESS) 'Markupsafe' 1.0 is not compatible with the latest version of setuptools[4], We need to bump the lower-constraint for Markupsafe to 1.1.1 to make it work. There are a few more issues[5] with lower-constraint jobs which I am debugging. What work to be done on the project side: ================================ This goal is more of testing the jobs on focal and fixing bugs if any otherwise migrate jobs by switching the nodeset to focal node sets defined in devstack. 1. Start a patch in your repo by making depends-on on either of below: devstack base patch if you are using only devstack base jobs not tempest: Depends-on: https://review.opendev.org/#/c/731207/ OR tempest base patch if you are using the tempest base job (like devstack-tempest): Depends-on: https://review.opendev.org/#/c/734700/ Both have depends-on on the series where I am moving unit/functional/doc/cover/nodejs tox jobs to focal. So you can test the complete gate jobs(unit/functional/doc/integration) together. This and its base patches - https://review.opendev.org/#/c/738328/ Example: https://review.opendev.org/#/c/738126/ 2. If none of your project jobs override the nodeset then above patch will be testing patch(do not merge) otherwise change the nodeset to focal. Example: https://review.opendev.org/#/c/737370/ 3. If the jobs are defined in branchless repo and override the nodeset then you need to override the branches variant to adjust the nodeset so that those jobs run on Focal on victoria onwards only. If no nodeset is overridden then devstack being branched and stable base job using bionic/xenial will take care of this. Example: https://review.opendev.org/#/c/744056/2 4. If no updates need you can abandon the testing patch (https://review.opendev.org/#/c/744341/) If it need updates then modify the same patch with proper commit msg, once it pass the gate then remove the Depends-On so that you can merge your patch before base jobs are switched to focal. This way we make sure no gate downtime in this migration. Example: https://review.opendev.org/#/c/744056/1..2//COMMIT_MSG Once we finish the testing on projects side and no failure then we will merge the devstack and tempest base patches. Important things to note: =================== * Do not forgot to add the story and task link to your patch so that we can track it smoothly. * Use gerrit topic 'migrate-to-focal' * Do not backport any of the patches. References: ========= Goal doc: https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-j… Storyboard tracking: https://storyboard.openstack.org/#!/story/2007865 [1] https://github.com/PyCQA/pyflakes/issues/367 [2] https://review.opendev.org/#/c/739315/ [3] https://review.opendev.org/#/c/739334/ [4] https://github.com/pallets/markupsafe/issues/116 [5] https://zuul.opendev.org/t/openstack/build/7ecd9cf100194bc99b3b70fa1e6de032 -gmann

7 17

[tripleo] rdo infrastructure maintenance
by Wesley Hayutin 24 Sep '20

24 Sep '20

Greetings, There is some maintenance on the rdo infra that is causing check and gate jobs to fail upstream. The situation is actively being worked on at this time. You may find errors in your check / gate jobs.. like the following. TASK [oooci-build-images : Download TripleO source image] 2020-09-24 10:26:35.615996 | primary | ERROR 2020-09-24 10:26:35.617685 | primary | { 2020-09-24 10:26:35.617774 | primary | "attempts": 60, 2020-09-24 10:26:35.617850 | primary | "msg": "Failed to connect to images.rdoproject.org at port 443: [Errno 113] No route to host", 2020-09-24 10:26:35.617929 | primary | "status": -1, 2020-09-24 10:26:35.618001 | primary | "url": "https://images.rdoproject.org/CentOS-8-x86_64-GenericCloud.qcow2" 2020-09-24 10:26:35.618072 | primary | } https://5134c188955ee39fd51b-cd04c057bb6c1703504e41a1dbc31642.ssl.cf5.rackc… Sorry for the trouble, we'll update this email when we're clear. 0/

1 1

[manila] Doc-a-thon event coming up next Thursday (Aug 6th)
by Victoria Martínez de la Cruz 24 Sep '20

24 Sep '20

Hi folks, We will be organizing a doc-a-thon next Thursday, August 6th, with the main goal of improving our docs for the next release. We will be gathering on our Freenode channel #openstack-manila after our weekly meeting (3pm UTC) and also using a videoconference tool (exact details TBC) to go over a curated list of opened doc bugs we have here [0]. *Your* participation is truly valued, being you an already Manila contributor or if you are interested in contributing and you didn't know how, so looking forward to seeing you there :) Cheers, Victoria [0] https://ethercalc.openstack.org/ur17jprbprxx

2 3

[oslo] PTL Non-candidacy: I mean it this time :-P
by Ben Nemec 24 Sep '20

24 Sep '20

I'm eminently familiar with midwest goodbyes, but an entire cycle to actually leave is taking it a bit far, don't you think? :-) Seriously though, this is two cycles in a row that we've had to scramble late in a cycle to finish basic community goals, mostly because of my lack of attention. Now that we've all sort of adapted to the whole global pandemic thing I'm hoping my abdication will stick this time. I'll still be around and try to help out when I can, but it's past time for me to turn the leadership of Oslo over to someone else. We've got a great team and I'm sure any one of them will do a great job! Thanks. -Ben

5 4

[all][elections][tc] Stepping down from the TC
by Jean-Philippe Evrard 24 Sep '20

24 Sep '20

Hello everyone, This is probably not a surprise for most of you, but I think it's worth writing it down: I won't be a candidate for another term at the TC. It was a pleasure to work with all of you. I am not leaving because I don't find the TC interesting anymore, quite the opposite. I will probably still lurk and follow the channels and ML. I just have switched to (yet) another duty at my employer, keeping me away from OpenStack. Next to this, I believe it's good to have some fresh members in the TC, it's been a while I am part of this family now :) For those interested by running the TC: Don't hesitate to run! We need fresh ideas and motivated people. It's not by having always the same people at the helm that OpenStack will naturally or drastically evolve. If you want to change OpenStack, be the change! Thanks to all of you. It was nice. Regards, Jean-Philippe Evrard (evrardjp)

11 11

RE: [tacker] Propose Toshiaki Takahashi for tacker core
by TAKAHASHI TOSHIAKI(高橋　敏明) 24 Sep '20

24 Sep '20

Hi Yasufumi and Team, Thank you so much! I'm glad to join core team. I'll continue to contribute for Tacker community activation! Toshiaki > -----Original Message----- > From: Yasufumi Ogawa <yasufum.o(a)gmail.com> > Sent: Thursday, September 24, 2020 6:43 PM > To: openstack-discuss(a)lists.openstack.org; TAKAHASHI TOSHIAKI(高橋　敏明) > <ts-takahashi(a)nec.com> > Subject: ##freemail## Re: [tacker] Propose Toshiaki Takahashi for tacker core > > On 2020/09/17 4:06, yasufum wrote: > > Toshiaki Takahashi (takahashi-tsc) has been so active for reviewing, > > fixing bugs and answering questions in the recent releases [1][2] and > > had several sessions on summits for Tacker. In addition, he is now > > well distinguished as one of the responsibility from ETSI-NFV standard > > community as a contributor between the standard and implementation for > > the recent contributions for both of OpenStack and ETSI. > > > > I'd appreciate if we add Toshiaki to the core team. > > > > [1] https://www.stackalytics.com/?company=nec&module=tacker > > [2] > > https://www.stackalytics.com/?user_id=t-takahashi%40ig.jp.nec.com&metr > > ic=marks > > Thank you everyone! I've seen only positive responses, so I've added Toshiaki as a > new core of tacker team. > > Congratulations, Toshiaki! > > > > > > > Regards, > > Yasufumi > >

1 0

[tacker] Propose Toshiaki Takahashi for tacker core
by yasufum 24 Sep '20

24 Sep '20

Toshiaki Takahashi (takahashi-tsc) has been so active for reviewing, fixing bugs and answering questions in the recent releases [1][2] and had several sessions on summits for Tacker. In addition, he is now well distinguished as one of the responsibility from ETSI-NFV standard community as a contributor between the standard and implementation for the recent contributions for both of OpenStack and ETSI. I'd appreciate if we add Toshiaki to the core team. [1] https://www.stackalytics.com/?company=nec&module=tacker [2] https://www.stackalytics.com/?user_id=t-takahashi%40ig.jp.nec.com&metric=ma… Regards, Yasufumi

10 9

Error log
by Issac Chan 24 Sep '20

24 Sep '20

Hi all, May you have a look on this log file? I cannot start trove guest instance database normally. Best wishes, Issac

1 0

[neutron][ovn] N/S traffic that needs SNAT (without floating IPs) will always pass through the centralized gateway nodes
by Tony Liu 23 Sep '20

23 Sep '20

Hi, I read "N/S traffic that needs SNAT (without floating IPs) will always pass through the centralized gateway nodes," in [1]. Why is that? Is SNAT on each compute node not supported by OVN, or it's about ML2 driver or provisioning? [1] https://docs.openstack.org/networking-ovn/latest/admin/refarch/refarch.html Thanks! Tony

1 1