- openstack-discuss - lists.openstack.org

[NOVA] instance hostname vs display_name vs dns_name
by Volodymyr Litovka 30 Jan '20

30 Jan '20

Dear colleagues, I'm using DNS Integration and just faced an issue - after renaming instance, I can't bind port to the instance using new name: 1) I've created intances with name 'devel' 2) then I renamed it to devel (openstack server set --name packager devel) 3) when binding port with dns_name using new name ('packager' in my case), the following error appear: ERROR nova.api.openstack.wsgi PortNotUsableDNS: Port c3a92cf6-b49b-4570-b69b-0c23af1d1f94 not usable for instance 6aa78bd5-099e-4878-a5ac-90262505a924. Value packager assigned to dns_name attribute does not match instance's hostname devel and yes, record in DB still uses an old hostname: mysql> select display_name from instances where hostname='devel'; +--------------+ | display_name | +--------------+ | packager | +--------------+ 1 row in set (0.00 sec) and hostname remains the same (initial) regardless of any changes to display_name. I'm on Rocky. Is it bug or feature and are there ways to work around this? Thank you. -- Volodymyr Litovka "Vision without Execution is Hallucination." -- Thomas Edison

2 2

[goals][Drop Python 2.7 Support] Week R-15 Update (# 2.5 weeks left to complete)
by Ghanshyam Mann 29 Jan '20

29 Jan '20

Hello Everyone, Below is the progress on "Drop Python 2.7 Support" for R-15 week. Schedule: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html#sc… Highlights: ======== * Schedule is to finish the py2-drop from every deliverable (except requirement repo) by m-2 on R13. Only 2.5 weeks left to finish the work. * There are still cases where Tempest and plugins does not work due to py2 drops. New plan & option has been sent in separate ML thread [1] and work in progress. * Few services merged the patches but not all. If your project is in the below list, I request PTLs to review it on priority. Project wise status and need reviews: ============================ Phase-1 status: The OpenStack services have not merged the py2 drop patches: NOTE: This was supposed to be completed by milestone-1 (Dec 13th, 19). * Adjutant * Karbor * Masakari * Tacker * Qinling * Tricircle Phase-2 status: This is ongoing work and I think most of the repo have patches up to review. Try to review them on priority. If any query and I missed to respond on review, feel free to ping me in irc. * Open review: https://review.opendev.org/#/q/topic:drop-py27-support+status:open How you can help: ============== - Review the patches. Push the patches if I missed any repo. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012241.… -gmann

1 0

[largescale-sig] Meeting summary and next actions
by Thierry Carrez 29 Jan '20

29 Jan '20

Hi everyone, The Large Scale SIG held a meeting today. You can access the summary and logs of the meeting at: http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_si… Regarding progress on our "Documenting large scale operations" goal, we turned our collection of relevant articles more as a group background activity than an immediate TODO. The idea is more to remember to add links to the etherpad[1] when we come across relevant content. oneswig mentioned the list to the Scientific SIG, in hopes that it would trigger more entries. [1] https://etherpad.openstack.org/p/large-scale-sig-documentation On the "Scaling within one cluster, and instrumentation of the bottlenecks" goal, nobody filed a scaling story yet on the etherpad[2] set up to collect them. masahito produced a first draft of the oslo.metrics blueprint[3], up for the group review. Finally, oneswig signed up to prepare a show-and-tell about some investigation they have been doing in this area, for presentation at next meeting. [2] https://etherpad.openstack.org/p/scaling-stories [3] https://review.opendev.org/#/c/704733/ Between now and next meeting, group members should prioritize: - Reviewing oslo.metrics draft at https://review.opendev.org/#/c/704733/ and comment so that we can iterate on it - Reading page on golden signals at https://landing.google.com/sre/sre-book/chapters/monitoring-distributed-sys… Other action items: - oneswig to prepare show-and-tell for presentation at next meeting - ttx to add meeting to eavesdrop on a every-two-week cadence - all post short descriptions of what happens (what breaks first) when scaling up a single cluster to https://etherpad.openstack.org/p/scaling-stories The next meeting will happen on February 12, at 9:00 UTC on #openstack-meeting. Cheers, -- Thierry Carrez (ttx)

2 1

[cinder] driver removal policy update (draft)
by Brian Rosmaita 29 Jan '20

29 Jan '20

I've posted a patch updating our third-party driver removal policy along the lines discussed at today's cinder meeting: https://review.opendev.org/704906 Let's continue the discussion in gerrit. I'll update the wiki after we've come to a consensus on the patch. cheers, brian

1 0

[tripleo] Removing the `openstack overcloud plan *` commands
by Dougal Matthews 29 Jan '20

29 Jan '20

Hey all, While doing work on the Mistral to Ansible port I was looking at the openstack overcloud plan commands. These are; - openstack overcloud plan create - openstack overcloud plan delete - openstack overcloud plan deploy - openstack overcloud plan list - openstack overcloud plan export I believe none of these commands make sense in a post-TripleO UI world. There is no other way to interact and update a plan. Deploys are always done via "openstack overcloud deploy" and this deletes the contents of the plan container and repopulates it with the local files[1]. I am therefore proposing that we remove these commands and skip the normal deprecation process. https://review.opendev.org/#/c/704581/1 What do you think? Thanks, Dougal [1]: https://github.com/openstack/python-tripleoclient/blob/3c589979ceb05d732b3c…

3 4

horizon: Trailing spaces removed on passwords
by Orestes Leal Rodríguez 28 Jan '20

28 Jan '20

>From the dashboard openstack is removing the trailing spaces from our user's passwords. We have a modified sql.py backend, that does an ldap bind to an active directory data store. And that works almost always. I say almost because for some users it doesn't work at all. We figure out (and a co-worker also confirmed this) that openstack is removing trailing (also leading?) spaces from the password entered in the dashboard. Also, inside the dashboard trailing spaces are not accepted even when they are equal byte by byte (including the space, I get an error). So this is going on. Do anybody knows where is this removal performed? (python script location, line) So I can remove that since I have users (me included, I have the issue since the very beginning of this deployment) that cannot login. And they can use their Active Directrory passwords from other apps without problem. We are running 'stein' with the latest update for ubuntu 18.04-AMD64.

5 5

[cyborg] No IRC meeting today
by Nadathur, Sundar 28 Jan '20

28 Jan '20

Since many people are traveling on account of the Chinese New Year, there will be no IRC meeting today. Regards, Sundar

1 1

[ops] OpenStack Ops Meetups team meeting 2020-1-20
by Chris Morgan 28 Jan '20

28 Jan '20

Meeting minutes for today's meeting are linked below. This was our first meeting since the very successful (or so I am told) Ops Meetup in London earlier this month, for which the agenda is here https://etherpad.openstack.org/p/LON-2020-OPS-AGENDA and the feedback was collected here https://etherpad.openstack.org/p/LON-2020-OPS-FEEDBACK the meetups team is now turning to looking into what we can arrange for operators at the Vancouver opendev+ptg event and then a second full ops meetup in south korea in september. Watch this space! Chris Morgan on behalf of the openstack ops meetups team <•openstack> Minutes: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2020/ops_meetup_tea… 10:53 AM Minutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2020/ops_meetup_tea… 10:53 AM Log: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2020/ops_meetup_tea… -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[barbican] TPM2.0 backend
by Balázs Gibizer 28 Jan '20

28 Jan '20

Hi, Looking at the Barbican documentation I see that the secrets can be stored on disk (SimpleCrypto backend) or in a HW vendor specific HSM module. Is there a way to use a TPM 2.0 device as the backend of Barbican via something like [1]? Cheers, gibi [1] https://github.com/tpm2-software/tpm2-pkcs11

1 1

[trio2o] Current state, community interest, alternatives
by Vladimir Kozhukalov 28 Jan '20

28 Jan '20

Hi, I am currently looking for a open source solution that is able to expose a single API endpoint for a user to multiple Openstack instances. Partly the idea behind is to stop investing efforts into tuning of Openstack to make it scalable and instead to deploy a bunch of small Openstack regions (say ~100 nodes) and work with them via API frontend. I am aware of Nova Cells, but it is complicated and Nova is not the only Openstack component that needs scaling. All these ad hoc tuning like dedicated RabbitMQ instances just make the system barely maintainable and it is complicated to reproduce. Requirements for a possible solution are: - Single authentication point (I know this is simple and can be for example SAML based federation) - Single point to manage keys and quotas - Possibly L2 connectivity between VMs in different Openstack instances (I know this can be achieved using VPNs, but this is kinda too complicated for a user) - Ability to work with different Openstack versions (need for gradual upgrade) I know Huawei and others implemented PoC for Openstack cascading and then invested some efforts in Trio2o and Tricircle. Tricircle is about cascading Neutron and IMO it is better to use a scalable SDN (like TangstenFabric or OVN). Trio2o looks like what I actually need, but the community interest around Trio2o is very limited (frankly, it looks almost dead). Last few weeks I was experimenting with Trio2o and Devstack with Stein release. It looks working, but the functionality is limited. Is there anyone who is interested in reviving Trio2o and investing into it? Maybe there are other solutions that I am not aware of? -- Best regards, Kozhukalov Vladimir

1 0

[cinder] changes for sqlalchemy 1.3.13
by Brian Rosmaita 27 Jan '20

27 Jan '20

Updating to the latest release of sqlalchemy breaks a cinder unit test. This patch shows the breakage and makes some suggestions about how it could be fixed. I could use some feedback: https://review.opendev.org/704425 thanks! brian

1 0

[neutron] CI meeting date changed
by Slawek Kaplonski 27 Jan '20

27 Jan '20

Hi, Just short info, according to what we agreed on our last CI meeting, it's now changed and will be on Wednesday at 1500 UTC. Please also note that IRC channel is also changed and now it will be on "openstack-meeting-3" You can check [1] for details. [1] https://review.opendev.org/#/c/704200/ -- Slawek Kaplonski Senior software engineer Red Hat

1 0

[ceilometer] Stable releases
by Pierre Riteau 27 Jan '20

27 Jan '20

Hello, Is it planned to release new Ceilometer tarballs for rocky and stein? There are several bug fixes (for example [1]) in stable branches that would be useful to include in a release. If t can help, I can submit patches to the releases repository. Thanks, Pierre Riteau (priteau) [1] https://bugs.launchpad.net/ceilometer/+bug/1801348

2 2

[tripleo] TripleO CI Summary: Sprint 41
by Rafael Folco 27 Jan '20

27 Jan '20

Greetings, The TripleO CI team has just completed Sprint 41 / Unified Sprint 20 (Jan 03 thru Jan 22). The following is a summary of completed work during this sprint cycle: - Fixed the new promoter code and added testing to cover identified bugs. - Manually built CentOS8 containers and documented missing requirements [4]. Started building RHEL8 containers for OSP. - Documented the design for the new component promotion pipeline [3]. Continue to implement the downstream version of the component pipeline. - Addressed necessary changes to promote-hash role to support the new multi-hash component provided by delorean [5]. - Turned the ansible-collect-logs role into an infra-red plugin as part of the shared goals for the combined CI team. The planned work for the next sprint [1] extends the work started in the previous sprint and focuses on CentOS8 container builds as a base requirement to leverage other fronts of work. The Ruck and Rover for this sprint are Wesley Hayutin (weshay) and Chandan Kumar (chkumar). Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Ruck/rover notes to be tracked in etherpad [2]. Thanks, rfolco [1] https://tree.taiga.io/project/tripleo-ci-board/taskboard/unified-sprint-21 [2] https://etherpad.openstack.org/p/ruckroversprint21 [3] https://hackmd.io/5uYRmLaOTI2raTbHWsaiSQ [4] https://hackmd.io/dSagCbocQ4KSVEZR1uf8Tw [5] https://trunk.rdoproject.org/centos8-master/tripleo-ci-testing/delorean.repo

1 0

[largescale-sig] Next meeting: Jan 29, 9utc
by Thierry Carrez 27 Jan '20

27 Jan '20

Hi everyone, The Large Scale SIG will have a meeting this week on Wednesday, Jan 29 at 9 UTC[1] in #openstack-meeting on IRC: [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200129T09 As always, the agenda for our meeting is available at: https://etherpad.openstack.org/p/large-scale-sig-meeting Feel free to add topics to it. We had several standing TODOs out of our January 15 meeting, so I also invite you to review the summary of that meeting in preparation of the next: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012049.… Regards, -- Thierry Carrez

1 0

[Devstack] Unable to find pip2.7 ?
by Martin Chacon Piza 27 Jan '20

27 Jan '20

Dear all, It seems that there is a problem stacking Devstack using the master branch. The problem happens during the step: Installing package prerequisites [ERROR] /home/vagrant/devstack/inc/python:41 Unable to find pip2.7; cannot continue This is the minimum local.conf I used: [[local|localrc]] SERVICE_HOST=192.168.10.6 HOST_IP=192.168.10.6 HOST_IP_IFACE=eth1 DATABASE_PASSWORD=secretdatabase RABBIT_PASSWORD=secretrabbit ADMIN_PASSWORD=secretadmin SERVICE_PASSWORD=secretservice LOGFILE=$DEST/logs/stack.sh.log LOGDIR=$DEST/logs LOG_COLOR=False DEST=/opt/stack USE_PYTHON3=True As a workaround I need to revert the following change, then it ends up properly: commit 279a7589b03db69fd1b85d947cd0171dacef94ee Author: Jens Harbott (frickler) <j.harbott(a)x-ion.de> Date: Mon Apr 16 12:08:30 2018 +0000 Revert "Do not use pip 10 or higher" This reverts commit f99d1771ba1882dfbb69186212a197edae3ef02c. Added workarounds that might want to get split into their own patch before merging: - Don't install python-psutil - Don't run peakmem_tracker Change-Id: If4fb16555e15082a4d97cffdf3cfa608a682997d Any hints? -- Best regards, *Martín Chacón Pizá* *chacon.piza(a)gmail.com <chacon.piza(a)hotmail.com>*

2 3

[neutron] Bug deputy report for week of January 20th
by Lajos Katona 27 Jan '20

27 Jan '20

Hi, I was Neutron bug deputy last week, see my short summary of last week's bugs. Summary: A lot of not serious CI related issue, most of them in progress or even already fixed. As a consequence of networking-ovn code moving old bugs from https://bugs.launchpad.net/networking-ovn were moved to neutron bugs repository in launchpad. - High - https://bugs.launchpad.net/neutron/+bug/1860612 (OVN agent devstack script doesn't support IPv6) - In Progress - Medium - https://bugs.launchpad.net/neutron/+bug/1860209 (Local variable referenced before assignment in "_router_fip_qos_after_admin_state_down_up") - Fix released - https://bugs.launchpad.net/neutron/+bug/1860332 ([CI] gate py3{6,7} jobs timeout ) - Fix Released - https://bugs.launchpad.net/neutron/+bug/1860326 (Kill neutron-keepalived-state-change-monitor fails) - Fix Released - https://bugs.launchpad.net/neutron/+bug/1860488 (Encapsulated DHCP options are not supported in neutron) - In Progress - https://bugs.launchpad.net/neutron/+bug/1860560 ([ovn] lsp_set_address Exception possible when passed empty list of addresses) - In Progress - https://bugs.launchpad.net/neutron/+bug/1860586 ([Tempest] SSH exception "No existing session") - In Progress - https://bugs.launchpad.net/neutron/+bug/1860774([CI] gate functional and fullstack timeouts without reports of the causative test case) - In Progress - https://bugs.launchpad.net/neutron/+bug/1860662 ([OVN] FIP on OVN Load balancer doesn't work if member has FIP assigned on DVR setup) - Low - https://bugs.launchpad.net/neutron/+bug/1860436 ([ovn] Agent liveness checks are flaky and report false positives) - Fix Released - RFE - https://bugs.launchpad.net/neutron/+bug/1860521 (L2 pop notifications are not reliable) - Wishlist - https://bugs.launchpad.net/neutron/+bug/1860338 ([OVS] OVS agent should not plug/unplug smartNIC ports) - This one is related to Smartnic support ( https://bugs.launchpad.net/neutron/+bug/1785608) and os-vif, I suppose drivers team should discuss it. - Moved from OVN: - https://bugs.launchpad.net/neutron/+bug/1689880 ([OVN] The "neutron_sync_mode = repair" option breaks the whole cloud!) - https://bugs.launchpad.net/neutron/+bug/1860273 (Delete static route exception OVN) - https://bugs.launchpad.net/neutron/+bug/1841154 ([OVN][RFE] Make use of external ports) - https://bugs.launchpad.net/neutron/+bug/1832003 ([OVN] Left-over namespaces left in the environment by ovn-metadata-agent) - https://bugs.launchpad.net/neutron/+bug/1813551 ([OVN]Missing ingress QoS in OVN) - https://bugs.launchpad.net/neutron/+bug/1670666 ([OVN] Support native DHCP service for subnet without gateway IP) - https://bugs.launchpad.net/neutron/+bug/1542503 ([OVN] Lacking mechanism to provide proper MTU to instances) - https://bugs.launchpad.net/neutron/+bug/1664475 ([OVN] Can not retrieve where a OVN gateway router lives) - https://bugs.launchpad.net/neutron/+bug/1648525 ([OVN] QoS doesn't work with DVR, vlan tenant networks or provider networks.) - https://bugs.launchpad.net/neutron/+bug/1639835 ([OVN] Add functional testing to kuryr CI job) - https://bugs.launchpad.net/neutron/+bug/1764408 ([OVN] DHCP ports don't recreated after deleting them)

1 0

[goals][Drop Python 2.7 Support] Week R-16 Update (# 3 weeks left to complete)
by Ghanshyam Mann 26 Jan '20

26 Jan '20

Hello Everyone, Below is the progress on "Drop Python 2.7 Support" for R-16 week. Schedule: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html#sc… Highlights: ======== * Schedule is to finish the py2-drop from every deliverable (except requirement repo) by m-2 on R13. Only 3 weeks left to finish the work so I am going to send the status twice a week from now. * Every project has to merge their py2 drop patches on priority. We are/will face more gate issue on py2 things if the transition period is longer. * I have pushed the patches on tempest-plugins and wherever applicable jobs defined in plugin repo have been modified to run on py2 for stable branches and on py3 on the master gate. * Fixing neutron-tempest-plugin failure on stable/rocky by running Tempest on >py3.6 venv[1]. Project wise status and need reviews: ============================ Phase-1 status: The OpenStack services have not merged the py2 drop patches: NOTE: This was supposed to be completed by milestone-1 (Dec 13th, 19). * Adjutant * ec2-api * Karbor * Sahara (its plugins) * Masakari * Tacker * Qinling * Tricircle Phase-2 status: This is ongoing work and I think most of the repo have patches up to review. I will start tracking the progress for unmerged patches form next week. Each project is requested to merge the open patches asap. * Open review: https://review.opendev.org/#/q/topic:drop-py27-support+status:open How you can help: ============== - Review the patches. Push the patches if I missed any repo. [1] https://bugs.launchpad.net/neutron/+bug/1860033 -gmann

1 0

quick question
by Ruchi Rajasekhar 24 Jan '20

24 Jan '20

Would anyone happen to know of any data science platforms that can run on OpenStack? I was looking at Pivotal, Pachyderm but they don't run on OpenStack ☹

6 5

[Telemetry][TC]Telemetry status
by Rong Zhu 24 Jan '20

24 Jan '20

Hi, As discussed with Rico I send a mail to report the telemetry project status. We had already finished some work in Ussuri: 1.Support dynamic pollster feature Thanks Rafael Weingärtner hard working https://review.opendev.org/#/c/677031/ https://review.opendev.org/#/c/691659/ https://review.opendev.org/#/c/691944/ https://review.opendev.org/#/c/694345/ https://review.opendev.org/#/c/693088/ https://review.opendev.org/#/c/694519/ 2.Support aodh-evaluator built-in active/active deployment mode 3.Support threshold type alarm again Thanks, Lingxian https://review.opendev.org/#/c/697566/ https://review.opendev.org/#/c/695997/ Also, We plan to do some work in Ussuri: 1.Add Ceilometer API back Since Gnocchi is out of OpenStack and is unmaintained, we need to add Ceilometer API back again. 2.Mongodb database backend support As this thread [0] discuss, there are still some users still use mongodb as the database backend, we decide to add this support again. License issue should consider and fix by user. The OVH and Catalyst Cloud had fix the mongodb performance issue with some mongodb changes. Gnoochi will still support as the backed. Other database (like influxdb, ES....), we would happy everyone to submit patches to support as the database backed in ceilometer. 3.cpu_utils support This is mentioned many many times, this is a useful metric, so we decide support this again. 4.Support container meters with Zun 5. Acknowledgment of OpenStack-wide Goals I created a storyboard to track Ceilometer Ussuri release to do things in [1]. Free free to add things you want to do in Ussuri release. [0]: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010922… [1]: https://storyboard.openstack.org/#!/board/205 -- Thanks, Rong Zhu

17 34

RE: [cinder][ci] Cinder drivers being Unsupported and General CI Status ...
by SAITO NAOKI(齊藤　直樹) 24 Jan '20

24 Jan '20

Hi Jay, NEC Cinder CI was configured with zuul v2.5 and Jenkins, and has not been working since "Drop Xenial support". We are fixing our CI with zuul v3 using Software Factory mentioned in the last Cinder Ussuri Virtual Mid-Cycle meeting [1]. We installed Software Factory referring to guide [2], and are investigating how we can monitor openstack/cinder events and create cinder test jobs. It will be helpful if cinder-specific examples are available. [1] https://etherpad.openstack.org/p/cinder-ussuri-mid-cycle-planning [2] https://softwarefactory-project.io/r/#/c/17097/ Thanks, Naoki Saito E-Mail: nasaito at nec.com > From: Jay Bryant <jungleboyj at gmail.com> > Sent: Thursday, January 23, 2020 4:51 AM > To: openstack-discuss at lists.openstack.org; inspur.ci at inspur.com; wangyong2017 at inspur.com; Chengwei.Chou at infortrend.com; Bill.Sung at infortrend.com; Kuirong.Chen(陳奎融) <Kuirong.Chen at infortrend.com>; ido.benda at kaminario.com; srinivasd.ctr at kaminario.com; nec-cinder-ci at istorage.jp.nec.com; silvan at quobyte.com; robert at quobyte.com; felix at quobyte.com; bjoern at quobyte.com; OpenStack Development <openstack-dev at zadarastorage.com>; Shlomi Avihou | Zadara <shlomi at zadarastorage.com>; msdu-openstack at groups.ext.hpe.com > Subject: [nec-cinder-ci:76204] [cinder][ci] Cinder drivers being Unsupported and General CI Status ... > > All, > We once again are at the point in the release where we are talking about 3rd Party CI and what is going on for Cinder. At the moment I have analyzed drivers that have not successfully reported results on a Cinder patch in 30 or more days and have put together the following list of drivers to be unsupported in the Ussuri release: > • Inspur Drivers > • Infortrend > • Kaminario > • NEC > • Quobyte > • Zadara > • HPE Drivers > If your name is in the list above you are receiving this e-mail directly, not just through the mailing list. > If you are working on resolving CI issues please let me know so we can discuss how to proceed. > In addition to the fact that we will be pushing up unsupported patches for the drivers above, we have already unsupported and removed a number of drivers during this release. They are as follows: > • Unsupported: > o MacroSAN Driver > • Removed: > o ProphetStor Driver > o Nimble Storage Driver > o Veritas Access Driver > o Veritas CNFS Driver > o Virtuozzo Storage Driver > o Huawei FusionStorage Driver > o Sheepdog Storage Driver > Obviously we are reaching the point that the number of drivers leaving the community is concerning and it has sparked discussions around the fact that maybe our 3rd Party CI approach isn't working as intended. So what do we do? Just mark drivers unsupported and no longer remove drivers? Do we restore drivers that have recently been removed? > We are planning to have further discussion around these questions at our next Cinder meeting in #openstack-meeting-4 on Wednesday, 1/29/20 at 14:00 UTC. If you have thoughts or strong opinions around this topic please join us. > Thank you! > Jay Bryant > mailto:jsbryant at electronicjungle.net > IRC: jungleboyj

4 3

Backup and restore questions
by Tony Pearce 24 Jan '20

24 Jan '20

Is it possible to restore "openstack" to a different cloud? For example, either of the following; 1. Backup Openstack with version "X" and restore to different fresh deployment of the same version or 2. Backup Openstack with version "X" and restore to Openstack Version Y or even later, Z And are there any tools associated with Openstack that achieves this? I think this would come under the term "migration". I've been reading the Openstack docs with regards to backup/restore and doing some trial and error on my side. It appears to me that the "backup/restore" is only applicable for the same system - can anyone confirm it? Are there any options for transferring data to a different Openstack deployment? Thanks in advance *Tony Pearce* | *Senior Network Engineer / Infrastructure Lead**Cinglevue International <https://www.cinglevue.com>* Email: tony.pearce(a)cinglevue.com Web: http://www.cinglevue.com *Australia* 1 Walsh Loop, Joondalup, WA 6027 Australia. Direct: +61 8 6202 0036 | Main: +61 8 6202 0024 Note: This email and all attachments are the sole property of Cinglevue International Pty Ltd. (or any of its subsidiary entities), and the information contained herein must be considered confidential, unless specified otherwise. If you are not the intended recipient, you must not use or forward the information contained in these documents. If you have received this message in error, please delete the email and notify the sender.

2 1

[keystone] Keystone Team Update - Week of 20 January 2020
by Vishakha Agarwal 23 Jan '20

23 Jan '20

# Keystone Team Update - Week of 20 January 2020 ## News ### Roadmap Review The team isn't organizing a midcycle or milestone-ly meetings in this cycle. Instead we decided to utilize the meeting time and go through the ussuri roadmap [1]. We discussed the progress with the card owners and if they need any help with them. Please find the updated status of the cards in the roadmap [1]. [1] https://tree.taiga.io/project/keystone-ussuri-roadmap/kanban ### User Support and Bug Duty Every week the duty is being rotated between the members. The person-in-charge for bug duty for current and upcoming week can be seen on the etherpad [2] [2] https://etherpad.openstack.org/p/keystone-l1-duty ## Open Specs Ussuri specs: https://bit.ly/2XDdpkU Ongoing specs: https://bit.ly/2OyDLTh ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 2 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 40 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ### Priority Reviews * Community Goals https://review.opendev.org/#/c/699127/ [ussuri][goal] Drop python 2.7 support and testing keystone-tempest-plugin https://review.opendev.org/#/c/699119/ [ussuri][goal] Drop python 2.7 support and testing python-keystoneclient * Special Requests https://review.opendev.org/#/c/662734/ Change the default Identity endpoint to internal https://review.opendev.org/#/c/699013/ Always have username in CADF initiator https://review.opendev.org/#/c/700826/ Fix role_assignments role.id filter https://review.opendev.org/#/c/697444/ Adding options to user cli https://review.opendev.org/#/c/702374/ Cleanup doc/requirements.txt https://review.opendev.org/#/c/588211/ Add openstack_groups to assertion https://review.opendev.org/#/c/703578/ Updating tox -e all-plugin command ## Bugs This week we opened 2 new bugs and closed 1. Bugs opened (2) Bug #1860478 (keystone:Low): fetching role assignments should handle domain IDs in addition to project IDs - Opened by Harry Rybacki https://bugs.launchpad.net/keystone/+bug/1860478 Bug #1860252 (keystone:Undecided): security problem，one user can change other user's password without admin - Opened by kuangpeiling https://bugs.launchpad.net/keystone/+bug/1860252 Bugs closed (1) Bug #1860252 (keystone:Invalid): https://bugs.launchpad.net/keystone/+bug/1860252 ## Milestone Outlook https://releases.openstack.org/ussuri/schedule.html Spec freeze is on the week of 10 Feburary. We have 3 specs proposed for usuri cycle that needs reviews. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

[neutron] Drivers meeting on 24.01 cancelled
by Slawek Kaplonski 23 Jan '20

23 Jan '20

Hi, I am on PTO and I will not have time to chair tomorrow's drivers meeting. Lets cancel it this week. See You all next week on the meeting. Sorry for late info about it. -- Slawek Kaplonski Senior software engineer Red Hat

1 0

Re: [openstack-helm] Core Reviewer Nominations
by Tin Lam 23 Jan '20

23 Jan '20

+1. Thanks for your reviews and contributions to the OSH projects, Gage and Steven. Tin On Mon, Jan 20, 2020 at 7:14 PM Pete Birley < > petebirley+openstack-dev(a)gmail.com> wrote: > >> OpenStack-Helm team, >> >> >> >> Based on their record of quality code review and substantial/meaningful >> code contributions to the openstack-helm project, at last weeks meeting we >> proposed the following individuals as core reviewers for openstack-helm: >> >> >> >> - Gage Hugo >> - Steven Fitzpatrick >> >> >> >> All OpenStack-Helm Core Reviewers are invited to reply with a +1/-1 by >> EOD next Monday (27/1/2020). A lone +1/-1 will apply to both candidates, >> otherwise please spell out votes individually for the candidates. >> >> >> >> Cheers, >> >> >> Pete >> > -- Regards, Tin Lam

2 1

[all] pep8 results for maintenance branches over time
by John Fulton 23 Jan '20

23 Jan '20

What are projects doing about new linters working only with newer deps or even python3 only? For example [1] [2]. Might it be OK to ignore pep8 results on maintenance branches? Thanks, John [1] https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… Ignoring ruamel.yaml: markers 'python_version == "3.4"' don't match your environment ERROR: ansible-lint 4.2.0 has requirement ruamel.yaml<1,>=0.15.34; python_version < "3.7", but you'll have ruamel-yaml 0.13.14 which is incompatible. [2] https://zuul.opendev.org/t/openstack/build/82b01fb8a8c04068a906bf0cb888de58 AttributeError: module 'ruamel.yaml' has no attribute 'YAML' Examining undercloud-debug.yaml of type playbook Traceback (most recent call last): File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/bin/ansible-lint", line 8, in <module> sys.exit(main()) File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/lib/python3.5/site-packages/ansiblelint/__main__.py", line 187, in main matches.extend(runner.run()) File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/lib/python3.5/site-packages/ansiblelint/__init__.py", line 287, in run skip_list=self.skip_list)) File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/lib/python3.5/site-packages/ansiblelint/__init__.py", line 177, in run matches.extend(rule.matchtasks(playbookfile, text)) File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/lib/python3.5/site-packages/ansiblelint/__init__.py", line 87, in matchtasks yaml = ansiblelint.utils.append_skipped_rules(yaml, text, file['type']) File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/lib/python3.5/site-packages/ansiblelint/utils.py", line 596, in append_skipped_rules yaml_skip = _append_skipped_rules(pyyaml_data, file_text, file_type) File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/lib/python3.5/site-packages/ansiblelint/utils.py", line 606, in _append_skipped_rules yaml = ruamel.yaml.YAML() AttributeError: module 'ruamel.yaml' has no attribute 'YAML' Examining undercloud-service-status.yaml of type playbook Traceback (most recent call last): File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/bin/ansible-lint", line 8, in <module> sys.exit(main()) File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/lib/python3.5/site-packages/ansiblelint/__main__.py", line 187, in main matches.extend(runner.run()) File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/lib/python3.5/site-packages/ansiblelint/__init__.py", line 287, in run skip_list=self.skip_list)) File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/lib/python3.5/site-packages/ansiblelint/__init__.py", line 177, in run matches.extend(rule.matchtasks(playbookfile, text)) File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/lib/python3.5/site-packages/ansiblelint/__init__.py", line 87, in matchtasks yaml = ansiblelint.utils.append_skipped_rules(yaml, text, file['type']) File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/lib/python3.5/site-packages/ansiblelint/utils.py", line 596, in append_skipped_rules yaml_skip = _append_skipped_rules(pyyaml_data, file_text, file_type) File "/home/zuul/src/opendev.org/openstack/tripleo-validations/.tox/pep8/lib/python3.5/site-packages/ansiblelint/utils.py", line 606, in _append_skipped_rules yaml = ruamel.yaml.YAML() AttributeError: module 'ruamel.yaml' has no attribute 'YAML' /home/zuul/src/opendev.org/openstack/tripleo-validations ERROR: InvocationError for command /bin/bash tools/ansible-lint.sh (exited with code 1) pep8 finish: run-test after 45.18 seconds pep8 start: run-test-post pep8 finish: run-test-post after 0.00 seconds ___________________________________ summary ____________________________________ ERROR: pep8: commands failed

7 6

Upcoming OSF Event: OpenDev + PTG, June 8-11 in Vancouver
by Ashlee Ferguson 23 Jan '20

23 Jan '20

Join us this June in Vancouver for OpenDev + PTG, and grab your early bird tickets now <https://www.eventbrite.com/e/opendev-ptg-vancouver-2020-tickets-88923270897>! OpenDev + PTG is a new collaborative event organized by the OpenStack Foundation gathering developers, system architects, and operators to address common open source infrastructure challenges. June 8-11, 2020 Vancouver Convention Centre - East Building OpenDev will include discussion oriented sessions around a particular topic to explore a problem within a topic area, share common architectures, and collaborate around potential solutions. This OpenDev will focus specifically on the following Tracks, spanning open source projects, including Airship, Ansible, Ceph, Kata Containers, Kubernetes, OpenStack, StarlingX, and Zuul: Hardware Automation Large-scale Usage of Open Source Infrastructure Software Containers in Production Key Challenges for Open Source in 2020 The conversations will continue into the afternoon with the Project Teams Gathering (PTG) <https://www.openstack.org/ptg>. This is when the morning’s practices will be explored by project teams, SIGs and other workgroups who will have dedicated space to get work done in a productive setting, maximizing the ability of contributors to work through their project objectives in an environment that is focused towards work and productivity. Interested in Sponsoring? Sponsoring these events will help ensure the continued growth and success of open source infrastructure projects. A sponsorship prospectus will be available soon. If your organization is interested in participating and supporting the open infrastructure community, please contact events(a)openstack.org <mailto:events@openstack.org>. P.S. - Stay tuned for more info on OSF’s Q4 event, the Open Infrastructure Summit you know and love! See you in Vancouver! The OpenStack Foundation

1 0

[stestr][tempest] how to conf test suite to get file_name to be pythonlogging instead of stdout
by SCHVENINGER, DOUGLAS P 22 Jan '20

22 Jan '20

When using stestr we are seeing 1. different file_name for logging statement 2. mime type on one test suite run and not the other test suite run 3. test_id on all log statement in one test suite run but missing on some of the log statement from the other test suite run I was wondering if anyone has any input of how to config our internal test suite like tempest to get correct data to show up When we run tempest with stestr the subunit stream is placing all logging data with a test_id and the file_name being pythonlogging. Example sec record 2 below: Record 1 worker-00MùÏ³/àPÈ^'K‡ôoW�@{tempest.api.compute.flavors.test_flavors.FlavorsV2TestJSON.test_list_flavors[id-e36c0eaa-dff5-4082-ad1f-3f9a80aa3f59,smoke] Record 2 worker-0text/plain; charset="utf8"pythonlogging:''P�2020-01-21 19:05:43,639 142 INFO [tempest.lib.common.rest_client] Request (FlavorsV2TestJSON:test_list_flavors): 200 GET https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb… 0.468s 2020-01-21 19:05:43,639 142 DEBUG [tempest.lib.common.rest_client] Request - Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 'X-OpenStack-Nova-API-Version': '2.1', 'X-Auth-Token': '<omitted>'} Body: None Response - Headers: {'date': 'Tue, 21 Jan 2020 19:05:43 GMT', 'content-type': 'application/json', 'content-length': '4244', 'connection': 'close', 'vary': 'X-OpenStack-Nova-API-Version', 'x-content-type-options': 'nosniff', 'strict-transport-security': 'max-age=15724800; includeSubDomains', 'content-security-policy': "script-src 'self'; object-src 'self'", 'x-frame-options': 'DENY', 'x-permitted-cross-domain-policies': 'none', 'x-xss-protection': '1; mode=block', 'openstack-api-version': 'compute 2.1', 'x-openstack-nova-api-version': '2.1', 'x-openstack-request-id': 'req-160e3fc6-d568-457d-9cbd-f6670b652565', 'x-compute-request-id': 'req-160e3fc6-d568-457d-9cbd-f6670b652565', 'status': '200', 'content-location': 'https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…'} Body: b'{"flavors": [{"id": "5f112417-533d-4e33-b9d7-ca8237a29a83", "name": "m1.xlarge", "links": [{"rel": "self", "href": "https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…"}, {"rel": "bookmark", "href": "https://compute-nc.auk51a.cci.att.com/8695795f8370474d9d628b3cdd9f97cb/flav…"}]}, {"id": "877ef018-6134-4d61-ba6b-d40ee58eb6be", "name": "aqa.alt20200121T190526948874", "links": [{"rel": "self", "href": "https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…"}, {"rel": "bookmark", "href": "https://compute-nc.auk51a.cci.att.com/8695795f8370474d9d628b3cdd9f97cb/flav…"}]}, {"id": "910d1836-119b-4ecf-9d47-3ef7e5990fad", "name": "aqa.primary20200121T185150095917", "links": [{"rel": "self", "href": "https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…"}, {"rel": "bookmark", "href": "https://compute-nc.auk51a.cci.att.com/8695795f8370474d9d628b3cdd9f97cb/flav…"}]}, {"id": "bd850da7-a2d8-48e8-bd42-3378abae556a", "name": "aqa.primary20200121T190526948874", "links": [{"rel": "self", "href": "https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…"}, {"rel": "bookmark", "href": "https://compute-nc.auk51a.cci.att.com/8695795f8370474d9d628b3cdd9f97cb/flav…"}]}, {"id": "c6653cba-3cbd-48bd-aa3e-54366bded2b4", "name": "m1.small", "links": [{"rel": "self", "href": "https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…"}, {"rel": "bookmark", "href": "https://compute-nc.auk51a.cci.att.com/8695795f8370474d9d628b3cdd9f97cb/flav…"}]}, {"id": "cdb15fe3-66a6-46cb-ab97-b26cc37b6d7f", "name": "m1.medium", "links": [{"rel": "self", "href": "https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…"}, {"rel": "bookmark", "href": "https://compute-nc.auk51a.cci.att.com/8695795f8370474d9d628b3cdd9f97cb/flav…"}]}, {"id": "dcc5d1ea-d15a-476e-8587-29bd34e36051", "name": "m1.large", "links": [{"rel": "self", "href": "https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…"}, {"rel": "bookmark", "href": "https://compute-nc.auk51a.cci.att.com/8695795f8370474d9d628b3cdd9f97cb/flav…"}]}, {"id": "e43ea269-f785-48f1-a05e-edffae5d5a85", "name": "taas-p1.c2r4d50", "links": [{"rel": "0ËUùÆ³/ðMg^'K‡ôoW�@{tempest.api.compute.flavors.test_flavors.FlavorsV2TestJSON.test_list_flavors[id-e36c0eaa-dff5-4082-ad1f-3f9a80aa3f59,smoke] Record 3 worker-0text/plain; charset="utf8"pythonlogging:''LŸself", "href": "https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…"}, {"rel": "bookmark", "href": "https://compute-nc.auk51a.cci.att.com/8695795f8370474d9d628b3cdd9f97cb/flav…"}]}, {"id": "eef05014-3e5f-4ea5-bbfa-8171c2e2707b", "name": "aqa.alt20200121T185150095917", "links": [{"rel": "self", "href": "https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…"}, {"rel": "bookmark", "href": "https://compute-nc.auk51a.cci.att.com/8695795f8370474d9d628b3cdd9f97cb/flav…"}]}, {"id": "f1a3141db37c48e49bd84e90d1c1369e", "name": "p1.c5r1.0d10s1.0e10", "links": [{"rel": "self", "href": "https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…"}, {"rel": "bookmark", "href": "https://compute-nc.auk51a.cci.att.com/8695795f8370474d9d628b3cdd9f97cb/flav…"}]}, {"id": "f3da4ca8-f8df-44f8-8a06-832bca480234", "name": "m1.tiny", "links": [{"rel": "self", "href": "https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…"}, 2020-01-21 19:05:43,878 142 INFO [tempest.lib.common.rest_client] Request (FlavorsV2TestJSON:test_list_flavors): 200 GET https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb… 0.236s 2020-01-21 19:05:43,878 142 DEBUG [tempest.lib.common.rest_client] Request - Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 'X-OpenStack-Nova-API-Version': '2.1', 'X-Auth-Token': '<omitted>'} Body: None Response - Headers: {'date': 'Tue, 21 Jan 2020 19:05:43 GMT', 'content-type': 'application/json', 'content-length': '581', 'connection': 'close', 'vary': 'X-OpenStack-Nova-API-Version', 'x-content-type-options': 'nosniff', 'strict-transport-security': 'max-age=15724800; includeSubDomains', 'content-security-policy': "script-src 'self'; object-src 'self'", 'x-frame-options': 'DENY', 'x-permitted-cross-domain-policies': 'none', 'x-xss-protection': '1; mode=block', 'openstack-api-version': 'compute 2.1', 'x-openstack-nova-api-version': '2.1', 'x-openstack-request-id': 'req-38380cca-ecaf-4fb5-a768-cc91172ccbff', 'x-compute-request-id': 'req-38380cca-ecaf-4fb5-a768-cc91172ccbff', 'status': '200', 'content-location': 'https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…'} Body: b'{"flavor": {"id": "bd850da7-a2d8-48e8-bd42-3378abae556a", "name": "aqa.primary20200121T190526948874", "ram": 1024, "disk": 5, "swap": "", "OS-FLV-EXT-DATA:ephemeral": 0, "OS-FLV-DISABLED:disabled": false, "vcpus": 1, "os-flavor-access:is_public": true, "rxtx_factor": 1.0, "links": [{"rel": "self", "href": "https://compute-nc.auk51a.cci.att.com/v2.1/8695795f8370474d9d628b3cdd9f97cb…"}, {"rel": "bookmark", "href": "https://compute-nc.auk51a.cci.att.com/8695795f8370474d9d628b3cdd9f97cb/flav…"}]}}' 0£Õ8d³/ƒ@š^'K‡ôoW�@{tempest.api.compute.flavors.test_flavors.FlavorsV2TestJSON.test_list_flavors[id-e36c0eaa-dff5-4082-ad1f-3f9a80aa3f59,smoke] When we run our internal test suite with stestr the subunit stream is placing all logging data sometime with a test_id and the file_name being stdout. Example sec record 2 below: Record 1 process config logging to file_name stdout �'�@�^(�R��worker-0stdout@�2020-01-22 11:24:34.681 24600 INFO aic_aqa_infrastructure_sonobuoy_plugins.host_info.config [-] Config and Logging setup by aic_aqa_infrastructure_sonobuoy_plugins.host_info.config Config data following in DEBUG 0��..�'�B^^(�R�z��worker-0stdoutB82020-01-22 11:24:34.742 24600 INFO aic_aqa_infrastructure_sonobuoy_plugins.common.expected.base [-] Loaded ExpectedData source file: requirements from: /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/host_info/expected/data/requirements.yaml 2020-01-22 11:24:34.744 24600 INFO aic_aqa_infrastructure_sonobuoy_plugins.common.expected.base [-] Loaded ExpectedData source file: site from: /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/host_info/expected/data/site.yaml 0q��'�A@^(�R�'��worker-0stdoutA2020-01-22 11:24:34.819 24600 INFO aic_aqa_infrastructure_sonobuoy_plugins.common.expected.base [-] Loaded ExpectedData source file: default from: /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/host_info/expected/data/default.yaml 0��'�BP^(�S^�worker-0stdoutB*2020-01-22 11:24:35.260 24600 DEBUG aic_aqa_infrastructure_sonobuoy_plugins.common.utils.host_info_utils [-] file mount point /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/tests/functional/data/host with path /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/tests/functional/data/host/etc/rsyslog.d/40-sensage.conf get_host_mount /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/common/utils/host_info_utils.py:18 Record 2 test case exists event 0#l'��/�@�^(�S�#)H@|aic_aqa_infrastructure_sonobuoy_plugins.host_info.tests.network.test_calico_logs.TestCalicoLogs.test_flow_log_file_retentionworker-00�� '�E^(�S�� ________________________________ `worker-0stdoutD�2020-01-22 11:24:35.290 24600 DEBUG aic_aqa_infrastructure_sonobuoy_plugins.common.utils.host_info_utils [-] file mount point /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/tests/functional/data/host with path /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/tests/functional/data/host/etc/hostname get_host_mount /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/common/utils/host_info_utils.py:18 2020-01-22 11:24:35.291 24600 DEBUG aic_aqa_infrastructure_sonobuoy_plugins.common.actuals.commands.base_command [-] Executing command: cat /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/tests/functional/data/host/etc/hostname __init__ /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/common/actuals/commands/base_command.py:31 2020-01-22 11:24:35.298 24600 INFO aic_aqa_infrastructure_sonobuoy_plugins.host_info.tests.test_base [-] Use environment file point /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/tests/functional/data/controller-describe-node.json to describe node. 0�j}��'�D�^(�S��worker-0stdoutD�2020-01-22 11:24:35.342 24600 DEBUG aic_aqa_infrastructure_sonobuoy_plugins.common.utils.host_info_utils [-] file mount point /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/tests/functional/data/host with path /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/tests/functional/data/host/var/log/calico/flowlogs get_host_mount /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/common/utils/host_info_utils.py:18 2020-01-22 11:24:35.343 24600 DEBUG aic_aqa_infrastructure_sonobuoy_plugins.common.utils.host_info_utils [-] file mount point /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/tests/functional/data/host with path /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/tests/functional/data/host/var/log/calico/audit get_host_mount /home/ds6901/aic-aqa-infrastructure-sonobuoy-plugins/aic_aqa_infrastructure_sonobuoy_plugins/common/utils/host_info_utils.py:18 2020-01-22 11:24:35.345 24600 INFO aic_aqa_infrastructure_sonobuoy_plugins.host_info.tests.network.test_calico_logs [-] Class setup logging Record 3 test case in progress with test_id 0ŋ �/�@�^(�Sԗ&@|aic_aqa_infrastructure_sonobuoy_plugins.host_info.tests.network.test_calico_logs.TestCalicoLogs.test_flow_log_file_retentionworker-0 Record 4 log statements from the test case method but no test_id and file_name=stdout 0��Q�'�A�^(�S�a ________________________________ worker-0stdoutA�2020-01-22 11:24:35.350 24600 INFO aic_aqa_infrastructure_sonobuoy_plugins.host_info.tests.network.test_calico_logs [-] Sample log message 1 2020-01-22 11:24:35.358 24600 INFO aic_aqa_infrastructure_sonobuoy_plugins.host_info.tests.network.test_calico_logs [-] Sample log message 2 2020-01-22 11:24:35.359 24600 INFO aic_aqa_infrastructure_sonobuoy_plugins.host_info.tests.network.test_calico_logs [-] Sample log message 3 0�K��/�@�^(�S�n�0@|aic_aqa_infrastructure_sonobuoy_plugins.host_info.tests.network.test_calico_logs.TestCalicoLogs.test_flow_log_file_retentionworker-00N}� Thanks in advance for any help on this. Doug Schveninger Lead Software Engineer douglas.schveninger(a)att.com<mailto:douglas.schveninger@att.com> Office: (314) 450-3311

2 1

[api][sdk][dev][oslo] using uWSGI breaks CORS config
by Radosław Piliszek 22 Jan '20

22 Jan '20

Fellow Devs, as you might have noticed I started taking care of openstack/js-openstack-lib, now under the openstacksdk umbrella [1]. First goal is to modernize the CI to use Zuul v3, current devstack and nodejs, still WIP [2]. As part of the original suite of tests, the unit and functional tests are run from browsers as well as from node. And, as you may know, browsers care about CORS [3]. js-openstack-lib is connecting to various OpenStack APIs (currently limited to keystone, glance, neutron and nova) to act on behalf of the user (just like openstacksdk/client does). oslo.middleware, as used by those APIs, provides a way to configure CORS by setting params in the [cors] group but uWSGI seemingly ignores that completely [4]. I had to switch to mod_wsgi+apache instead of uwsgi+apache to get past that issue. I could not reproduce locally because kolla (thankfully) uses mostly mod_wsgi atm. The issue I see is that uWSGI is proposed as the future and mod_wsgi is termed deprecated. However, this means the future is broken w.r.t. CORS and so any modern web interface with it if not sitting on the exact same host and port (which is usually different between OpenStack APIs and any UI). [1] https://review.opendev.org/701854 [2] https://review.opendev.org/702132 [3] https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS [4] https://github.com/unbit/uwsgi/issues/1550 -yoctozepto

4 8

Re: [Release-job-failures] Release of openstack/tempest for ref refs/tags/23.0.0 failed
by Sean McGinnis 22 Jan '20

22 Jan '20

On 1/22/20 11:01 AM, zuul(a)openstack.org wrote: > Build failed. > > - release-openstack-python https://zuul.opendev.org/t/openstack/build/f56e6adb34c7425e8bda31ab29db4642 : SUCCESS in 3m 55s > - announce-release https://zuul.opendev.org/t/openstack/build/864c651598e74abca8c15a1aedee01c6 : SUCCESS in 4m 39s > - propose-update-constraints https://zuul.opendev.org/t/openstack/build/38926e79572e48c6909abb878df6ce88 : FAILURE in 15m 55s > > _______________________________________________ > Release-job-failures mailing list > Release-job-failures(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures We found there was a memory issue on one of the gitea servers that caused errors while trying to perform a clone. Everything was fine with the release other than proposing raising the upper constraints in openstack/requirements. I have manually proposed the update here: https://review.opendev.org/#/c/703863/ Sean

1 0

[Cyborg][Ironic][Nova][Neutron][TripleO][Cinder] accelerators management
by Arkady.Kanevsky＠dell.com 22 Jan '20

22 Jan '20

Fellow Open Stackers, I have been thinking on how to handle SmartNICs, GPUs, FPGA handling across different projects within OpenStack with Cyborg taking a leading role in it. Cyborg is important project and address accelerator devices that are part of the server and potentially switches and storage. It is address 3 different use cases and users there are all grouped into single project. 1. Application user need to program a portion of the device under management, like GPU, or SmartNIC for that app usage. Having a common way to do it across different device families and across different vendor is very important. And that has to be done every time a VM is deploy that need usage of a device. That is tied with VM scheduling. 2. Administrator need to program the whole device for specific usage. That covers the scenario when device can only support single tenant or single use case. That is done once during OpenStack deployment but may need reprogramming to configure device for different usage. May or may not require reboot of the server. 3. Administrator need to setup device for its use, like burning specific FW on it. This is typically done as part of server life-cycle event. The first 2 cases cover application life cycle of device usage. The last one covers device life cycle independently how it is used. Managing life cycle of devices is Ironic responsibility, One cannot and should not manage lifecycle of server components independently. Managing server devices outside server management violates customer service agreements with server vendors and breaks server support agreements. Nova and Neutron are getting info about all devices and their capabilities from Ironic; that they use for scheduling. We should avoid creating new project for every new component of the server and modify nova and neuron for each new device. (the same will also apply to cinder and manila if smart devices used in its data/control path on a server). Finally we want Cyborg to be able to be used in standalone capacity, say for Kubernetes. Thus, I propose that Cyborg cover use cases 1 & 2, and Ironic would cover use case 3. Thus, move all device Life-cycle code from Cyborg to Ironic. Concentrate Cyborg of fulfilling the first 2 use cases. Simplify integration with Nova and Neutron for using these accelerators to use existing Ironic mechanism for it. Create idempotent calls for use case 1 so Nova and Neutron can use it as part of VM deployment to ensure that devices are programmed for VM under scheduling need. Create idempotent call(s) for use case 2 for TripleO to setup device for single accelerator usage of a node. [Propose similar model for CNI integration.] Let the discussion start! Thanks., Arkady

7 18

[magnum] podman fedora-coreos authorization failed: SSL exception connecting on keystone
by Ionut Biru 22 Jan '20

22 Jan '20

Hello guys, I'm trying to deploy a kubernetes cluster using magnum 9.2 with fedora-coreos-31.20200113.3.1-openstack. Master vm is deployed correctly but the cluster is never deployed since podman returns the following error: Jan 21 21:55:14 k8s-cluster002-mn5qgp6qlmw6-master-0 podman[2433]: Authorization failed: SSL exception connecting to https://api.mydomain.cloud:5000/v3/auth/tokens: HTTPSConnectionPool(host='api.mydomain.cloud', port=5000): Max retries exceeded with url: /v3/auth/tokens (Caused by SSLError(SSLError(185090184, u'[X509] no certificate or crl found (_ssl.c:3063)'),)) I do have a valid letsencrypt certification on that particular domain. curl https://api.mydomain.cloud:5000/v3/auth/tokens {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Unauthorized"}} I was wondering, do you guys seen this issue before? Below is the template. https://paste.xinu.at/OC0Ic/ -- Ionut Biru - https://fleio.com

2 4

Rails Girls Summer of Code
by Amy Marrich 22 Jan '20

22 Jan '20

Hi All, I was contacted about this program to see if OpenStack might be interested in participating and despite the name it is language agnostic. Moe information on the program can be found at Rails Girls Summer of Code, <https://railsgirlssummerofcode.org/about/> I'm willing to help organize our efforts but would need to know level of interest to participate and mentor. Thanks, Amy (spotz) Chair, Diversity and Inclusion WG Chair, User Committee

2 3

[ironic][nova][neutron][cloud-init] Infiniband Support in OpenStack
by Kumari, Madhuri 22 Jan '20

22 Jan '20

Hi, I am trying to deploy a node with infiniband in Ironic without any success. The node has two interfaces, eth0 and ib0. The deployment is successful, node becomes active but is not reachable. I debugged and checked that the issue is with cloud-init. The cloud-init fails to configure the network interfaces on the node complaining that the MAC address of infiniband port(ib0) is not known to the node. Ironic provides a fake MAC address for infiniband ports and cloud-init is supposed to generate the actual MAC address of infiband ports[1]. But it fails[2] before reaching there. I have posted the issue in cloud-init[3] as well. Can someone please help me with this issue? How do we specify "TYPE=InfiniBand" from OpenStack? Currently the type sent is "phy" only. [1] https://github.com/canonical/cloud-init/blob/master/cloudinit/sources/helpe… [2] https://github.com/canonical/cloud-init/blob/master/cloudinit/sources/helpe… [3] https://bugs.launchpad.net/cloud-init/+bug/1857031 Regards, Madhuri

3 5

[nova] block_device_info being introduced to nova.virt.driver.ComputeDriver.rescue
by Lee Yarwood 22 Jan '20

22 Jan '20

Hello all, Just a heads up that as part of my work introducing stable device rescue to Nova the following change will be introducing an additional block_device_info argument to the signature of nova.virt.driver.ComputeDriver.rescue. virt: Provide block_device_info during rescue https://review.opendev.org/#/c/700811/ Any third party drivers implementing instance rescue will need to be updated. Cheers, -- Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76

1 0

Updating Openstack from Pike non-containerised to something current
by Tony Pearce 22 Jan '20

22 Jan '20

I am planning to upgrade my Openstack Pike. Please could I ask some questions about this so I understand better how to proceed? *Background*: - I have Openstack Pike running on 3 nodes (2 x compute and 1 x controller). Storage is provided by a Cinder driver and separate vendor storage array (iSCSI). - I have a bug which is impacting Cinder in Pike which is not present in Queens/Stein. - Since I installed Openstack some years ago, I was not able to update/patch it for a number of reasons. - The Openstack which I installed was from the tripleo.org website and I followed the instructions there. - I have configured LBaaS that was available in Pike by making config changes to .conf files. - I recall reading a few months ago when I started looking into this that I need to update to the latest within the current version (Pike) first, before updating beyond Pike so I am planning for that. *Questions*: 1. do I first need to deconfigure / remove the LBaaS before attempting an upgrade beyond Pike? 2. The tripleo website is a little confusing. I am running Pike and it is not containerised. The upgrade info on tripleo.org mentions upgrades to Pike in a containerised environment. So should I follow the detail for the "Ocata and earlier" release in this case? ref: http://tripleo.org/upgrade/minor_update.html#updating-your-overcloud-ocata-… 3. Do I need to upgrade to each release? ie from Pike > Queens then Queens > Stein etc ? Or can I do this: a) update Pike to the latest in the current Pike release b) Update Pike to Train *What I've gathered so far:* - If I can execute the 'openstack overcloud update' and limit it to the controller node then I can apply this to a cloned environment consisting of 1 x undercloud "director" and 1 x controller but I am unable to stage this for the compute nodes because they are physical bare-metal - the tripleo website guide lists the latest as 'Rocky' but I could see Stein in the yum search. I think I can follow the tripleo guide with a pinch of salt and replace *rocky* with *stein* Thank you *Tony Pearce* | *Senior Network Engineer / Infrastructure Lead**Cinglevue International <https://www.cinglevue.com>* Email: tony.pearce(a)cinglevue.com Web: http://www.cinglevue.com *Australia* 1 Walsh Loop, Joondalup, WA 6027 Australia. Direct: +61 8 6202 0036 | Main: +61 8 6202 0024 Note: This email and all attachments are the sole property of Cinglevue International Pty Ltd. (or any of its subsidiary entities), and the information contained herein must be considered confidential, unless specified otherwise. If you are not the intended recipient, you must not use or forward the information contained in these documents. If you have received this message in error, please delete the email and notify the sender.

2 3

volume local cache
by Fang, Liang A 21 Jan '20

21 Jan '20

Hi Gibi, Dan, Alex and dear Nova cores Nova Spec: https://review.opendev.org/#/c/689070/ Cinder Spec: https://review.opendev.org/#/c/684556/ Regarding the volume local cache spec, after several rounds of discussion in cinder weekly meeting, we continued discussed in cinder virtual mid-cycle ptg yesterday, and now cinder team is close to get agreement, and major ideas are: * Cinder sets “cacheable” property in volume type * Cinder should guarantee “cacheable” is set correctly, that means: should not set with “multiattach”, should not set for a backend that cannot be cached (NFS, RBD) * Os-brick prevents to attach a volume with cache mode that not safe in cloud environment * e.g. prevent write-back cache mode. So that all the operations, like live migration/snapshot/consistent group/volume backup can work as usual. * Nova schedules the VM with “cacheable” volume to servers with cache capability. * If no such available server, just go ahead without cache, but don’t fail it. * Schedule based on flavor (need more design here with Nova expert) Could you please comment on cinder spec if any before cinder team getting this hammered out? Thank you so much. Below is the performance test I did personally, using Optane SSD p4800x 750G as the cache. Setting fio with block size = 4k, iodepth=1 which is typical for latency measurement. The data may be slightly different on different environment, just FYI: In rand read test: [cid:image004.png@01D5D107.23D05610] In rand write test: [cid:image006.png@01D5D107.23D05610] In 70% rand read + 30% rand write mix test: [cid:image009.png@01D5D107.23D05610] Ceph in above chart means the baseline test, as shown in path ① below. Write-Through and Write-Back means open-cas cached, as shown in path②. [cid:image010.png@01D5D0FD.83839680] So even write-through mode, we still have lots of performance gains. Some concerns maybe: * In real world, the cache hit rate may cannot be so high (95% and more). * It depends on how big the cache device is. But normally a fast SSD with x TB size or a persistent memory with 512G size is big enough for hot data cache. * What will happen when backend storage is RDMA * Pure RDMA network link latency would be as low as ~10us. If plus the disk io to the storage system, the final latency would be dozens of microseconds. So it’s not suitable for an fast ssd(itself ~10us) to cache for RDMA volume, but we can use persistent memory (with latency about hundreds of nanosecond) to do the cache. I will do the measurement after Chinese new year. * It’s a pain that ceph cannot be supported * The major concern to mount ceph volume to host OS is the security considerations, right? It is a performance / security tradeoff for operators. In private cloud which OpenStack maybe mostly used, trust host OS would may be not a big problem, anyway, other backends rather than ceph are still doing in this way. I’m not going to change ceph to mount to host OS in this spec, but it’s not difficult for customer to switch to this way, like they customized other things. Regards LiangFang

1 0

[cinder] virtual mid-cycle summary available
by Brian Rosmaita 21 Jan '20

21 Jan '20

Hello Cinderinos, Thanks for a productive discussion today. I've posted a summary on the wiki so we can remember what happened and for the edification of those who didn't attend: https://wiki.openstack.org/wiki/CinderUssuriMidCycleSummary Also, I've posted a mid-cycle survey to get some feedback about the virtual connectivity and the format of today's meeting: https://forms.gle/muR2vMArZ7Eu1iV46 Please take the survey even if you didn't attend. (What I'm hoping to learn from the non-attendees is whether I could've communicated the event better, or whether the content was un-interesting, or what.) We'll be holding Session Two of the mid-cycle in a few weeks, so your feedback will be helpful in planning. cheers, brian PS: If the survey linked above is inaccessible in your country, please let me know and I'll figure something out so I can collect your feedback. The alternative to google forms I used last time was pretty limited in its free version, plus the only people who used it were located in countries where I know google forms are accessible (Europe & USA), so I succumbed to inertia and stuck with google forms.

1 0

[tc] Follow-up on action tems
by Jean-Philippe Evrard 21 Jan '20

21 Jan '20

Hello TC members, Here are a few things that should keep your attention, on top of the usual reviews... - We should start the business opportunities for 2020. Any takers? - We have action items from the last meeting: - ttx to post a summary of large scale sig's meeting on the ML this week. - mnaser to follow up on the static hosting - mnaser to push an update to distill what happened on the ML in terms of stable branch policy - jungleboyj to update the survey report patch - everyone to let the multi-arch SIG ( https://etherpad.openstack.org/p/Multi-arch) know if you have CI resources in different architectures - We have also new action items: - We should update the governance dashboard to include the "ideas" repo. Anyone? - We need to keep tracking on Telemetry status ( http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011586… ). - Our next meeting will host on 6 February. You can provide suggestion on agenda https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee - ttx should report on his investigation on possible bylaws change for an eventual leadership (tc/uc) merge, UC was more or less okay with the idea, which allows to continue forward the investigation. Note: There is no official stance from the TC on this yet. It's just investigation. - We have updated SIGs tags with https://review.opendev.org/#/c/695625/. This will make sure people aware of the actual status. And as mentioned action ttx and ricolin will works on expose that status tag on governance-sigs' page. And finally, some things to keep in mind: - We need to promote the first contact sig to organisations that might need help on getting things achieved in OpenStack - We need to start collecting ideas for the ideas repo. Regards, JP & Rico

1 0

[all][tc] What happened in OpenStack Governance recently
by Jean-Philippe Evrard 21 Jan '20

21 Jan '20

Hello everyone, It's official, the V release will be codenamed Victoria! The TC is now working on declaring its runtimes [A]. The TC has merged a change in its charter, establishing new rules for the future terms [B]. This will give us leeway for elections and term lengths. The cycle goals selection schedule was made clearer, so that we don't add goals to the teams too late in the future [C]. We have selected the 'project specific PTL and contributor guides' as an official goal for Ussuri. I invite you to read the update of Ghanshyam Mann (gmann) to follow what's going on for our Ussuri goals [D]. You should also have a look at the zuul legacy migration [G], as it could eventually be selected as a V goal :) In terms of release naming, we'll start the W naming process soon, because we know that naming things are hard [E]. If you're interested by security policy, you can have a look at Jeremy's patch [F]. In terms of projects: - There is a new official charm, for watcher [H] - js-openstack-lib is now part of the openstacksdk team [I] - there is a new neutron project, ovn-octavia-provider [J] - the ansible-sig got a new repository, ansible-plugin-container- connection [K] - Justin Ferrieu is the PTL for Cloudkitty for the rest of the cycle [L] - sushi-cli is now part of the ironic team [M] Happy new year to our Chinese community! Regards, Jean-Philippe & Rico [A]: https://review.opendev.org/#/c/693743/ [B]: https://review.opendev.org/#/c/699277/ [C]: https://review.opendev.org/#/c/698299/ [D]: http://lists.openstack.org/pipermail/openstack-discuss/2020-January/012019.… [E]: https://review.opendev.org/#/c/702414/ [F]: https://review.opendev.org/#/c/678426/ [G]: https://review.opendev.org/#/c/691278/ [H]: https://review.opendev.org/#/c/702072/ [I]: https://review.opendev.org/#/c/701854/ [J]: https://review.opendev.org/#/c/697095/ [K]: https://review.opendev.org/#/c/696737/ [L]: https://review.opendev.org/#/c/701214/ [M]: https://review.opendev.org/#/c/700914/

1 0

[all][ci] Gate jobs failures because of broken pip
by Takashi Kajinami 21 Jan '20

21 Jan '20

Hi All, I now observe some of the gate jobs are failing[1] because of broken pip[2], and it guess that we need to pin pip to avoid the error atm. [1] https://81b633e2c5fe858f8400-d324a81a71d524d51ede3dc5aee27774.ssl.cf5.rackc… [2] https://github.com/pypa/pip/issues/7217 May I ask for some help to set that pinning ? I couldn't find the correct way to pin pip after several investigation ... Thank you, Takashi -- ---------- Takashi Kajinami Software Maintenance Engineer Customer Experience and Engagement Red Hat e-mail: tkajinam(a)redhat.com

3 2

[tripleo][ironic][ansible][openstack-ansible] Ironic/Baremetal Ansible modules
by Sagi Shnaidman 21 Jan '20

21 Jan '20

Hi, all in the light of finding the new home place for openstack related ansible modules [1] I'd like to discuss the best strategy to create Ironic ansible modules. Existing Ironic modules in Ansible repo don't cover even half of Ironic functionality, don't fit current needs and definitely require an additional work. There are a few topics that require attention and better be solved before modules are written to save additional work. We prepared an etherpad [2] with all these questions and if you have ideas or suggestions on how it should look you're welcome to update it. We'd like to decide the final place for them, name conventions (the most complex one!), what they should look like and how better to implement. Anybody interested in Ansible and baremetal management in Openstack, you're more than welcome to contribute. Thanks [1] https://review.opendev.org/#/c/684740/ [2] https://etherpad.openstack.org/p/ironic-ansible-modules -- Best regards Sagi Shnaidman

9 18

[horizon][cloudkitty][tacker][masakari][congress][karbar][trove] Drop python2.7 and Django1.11 support in horizon plugins
by Akihiro Motoki 21 Jan '20

21 Jan '20

Hi, I am sending this mail to encourage reviews in horizon plugins. - Drop python 2.7 and Django 1.11 - Remove six usage Horizon has dropped python 2.7 support and Django 1.11 support (which is the last version with python 2.7 support). We proposed changes to horizon plugins to catch up with these changes. - Most projects have merged them. Thanks for your cooperation. - There are several pending reviews. https://review.opendev.org/#/q/topic:drop-django111-support+status:open - Django 1.11 drop depends on python 2.7 drop. In case of karbar-dashboard, python 2.7 drop needs to land before it. https://review.opendev.org/#/c/694442/ horizon also has dropped six usage. There are plugins which depends six on horizon requirements. We proposed a series of changes to avoid UT breakages in plugins. Reviews on them are also appreciated. https://review.opendev.org/#/q/topic:remove-six+status:open Thanks, Akihiro Motoki (amotoki)

1 0

[queens][nova] iscsi issue
by Ignazio Cassano 20 Jan '20

20 Jan '20

Hello all we are testing openstack queens cinder driver for Unity iscsi (driver cinder.volume.drivers.dell_emc.unity.Driver). The unity storage is a Unity600 Version 4.5.10.5.001 We are facing an issue when we try to detach volume from a virtual machine with two or more volumes attached (this happens often but not always): The following is reported nova-compute.log: 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server self.connector.disconnect_volume(connection_info['data'], None) 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/os_brick/utils.py", line 137, in trace_logging_wrapper 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", line 274, in inner 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/os_brick/initiator/connectors/iscsi.py", line 848, in disconnect_volume 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server device_info=device_info) 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/os_brick/initiator/connectors/iscsi.py", line 892, in _cleanup_connection 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server path_used, was_multipath) 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/os_brick/initiator/linuxscsi.py", line 271, in remove_connection 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server self.flush_multipath_device(multipath_name) 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/os_brick/initiator/linuxscsi.py", line 329, in flush_multipath_device 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server root_helper=self._root_helper) 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/os_brick/executor.py", line 52, in _execute 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server result = self.__execute(*args, **kwargs) 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/os_brick/privileged/rootwrap.py", line 169, in execute 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server return execute_root(*cmd, **kwargs) 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_privsep/priv_context.py", line 207, in _wrap 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server return self.channel.remote_call(name, args, kwargs) 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_privsep/daemon.py", line 202, in remote_call 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server raise exc_type(*result[2]) 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server ProcessExecutionError: Unexpected error while running command. 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server Command: multipath -f 36006016006e04400d0c4215e3ec55757 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server Exit code: 1 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server Stdout: u'Jan 17 16:04:30 | 36006016006e04400d0c4215e3ec55757p1: map in use\nJan 17 16:04:31 | failed to remove multipath map 36006016006e04400d0c4215e3ec55757\n' 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server Stderr: u'' 2020-01-17 16:05:11.132 6643 ERROR oslo_messaging.rpc.server Best Regards Ignazio

2 2

[magnum][kolla] etcd wal sync duration issue
by Eric K. Miller 20 Jan '20

20 Jan '20

Hi, We are using the following coe cluster template and cluster create commands on an OpenStack Stein installation that installs Magnum 8.2.0 Kolla containers installed by Kolla-Ansible 8.0.1: openstack coe cluster template create \ --image Fedora-AtomicHost-29-20191126.0.x86_64_raw \ --keypair userkey \ --external-network ext-net \ --dns-nameserver 1.1.1.1 \ --master-flavor c5sd.4xlarge \ --flavor m5sd.4xlarge \ --coe kubernetes \ --network-driver flannel \ --volume-driver cinder \ --docker-storage-driver overlay2 \ --docker-volume-size 100 \ --registry-enabled \ --master-lb-enabled \ --floating-ip-disabled \ --fixed-network KubernetesProjectNetwork001 \ --fixed-subnet KubernetesProjectSubnet001 \ --labels kube_tag=v1.15.7,cloud_provider_tag=v1.15.0,heat_container_agent_tag=ste in-dev,master_lb_floating_ip_enabled=true \ k8s-cluster-template-1.15.7-production-private openstack coe cluster create \ --cluster-template k8s-cluster-template-1.15.7-production-private \ --keypair userkey \ --master-count 3 \ --node-count 3 \ k8s-cluster001 The deploy process works perfectly, however, the cluster health status flips between healthy and unhealthy. The unhealthy status indicates that etcd has an issue. When logged into master-0 (out of 3, as configured above), "systemctl status etcd" shows the stdout from etcd, which shows: Jan 11 17:27:36 k8s-cluster001-4effrc2irvjq-master-0.novalocal runc[2725]: 2020-01-11 17:27:36.548453 W | etcdserver: timed out waiting for read index response Jan 11 17:28:02 k8s-cluster001-4effrc2irvjq-master-0.novalocal runc[2725]: 2020-01-11 17:28:02.960977 W | wal: sync duration of 1.696804699s, expected less than 1s Jan 11 17:28:31 k8s-cluster001-4effrc2irvjq-master-0.novalocal runc[2725]: 2020-01-11 17:28:31.292753 W | wal: sync duration of 2.249722223s, expected less than 1s We also see: Jan 11 17:40:39 k8s-cluster001-4effrc2irvjq-master-0.novalocal runc[2725]: 2020-01-11 17:40:39.132459 I | etcdserver/api/v3rpc: grpc: Server.processUnaryRPC failed to write status: stream error: code = DeadlineExceeded desc = "context deadline exceeded" We initially used relatively small flavors, but increased these to something very large to be sure resources were not constrained in any way. "top" reported no CPU nor memory contention on any nodes in either case. Multiple clusters have been deployed, and they all have this issue, including empty clusters that were just deployed. I see a very large number of reports of similar issues with etcd, but discussions lead to disk performance, which can't be the cause here, not only because persistent storage for etcd isn't configured in Magnum, but also the disks are "very" fast in this environment. Looking at "vmstat -D" from within master-0, the number of writes is minimal. Ceilometer logs about 15 to 20 write IOPS for this VM in Gnocchi. Any ideas? We are finalizing procedures to upgrade to Train, so we wanted to be sure that we weren't running into some common issue with Stein that would immediately be solved with Train. If so, we will simply proceed with the upgrade and avoid diagnosing this issue further. Thanks! Eric

4 6

Galera config values
by Albert Braden 20 Jan '20

20 Jan '20

I'm experimenting with Galera in my Rocky openstack-ansible dev cluster, and I'm finding that the default haproxy config values don't seem to work. Finding the correct values is a lot of work. For example, I spent this morning experimenting with different values for "timeout client" in /etc/haproxy/haproxy.cfg. The default is 1m, and with the default set I see this error in /var/log/nova/nova-scheduler.log on the controllers: 2020-01-17 13:54:26.059 443358 ERROR oslo_db.sqlalchemy.engines DBConnectionError: (pymysql.err.OperationalError) (2013, 'Lost connection to MySQL server during query') [SQL: u'SELECT 1'] (Background on this error at: http://sqlalche.me/e/e3q8) There are several timeout values in /etc/haproxy/haproxy.cfg. These are the values we started with: stats timeout 30s timeout http-request 10s timeout queue 1m timeout connect 10s timeout client 1m timeout server 1m timeout check 10s At first I changed them all to 30m. This stopped the "Lost connection" error in nova-scheduler.log. Then, one at a time, I changed them back to the default. When I got to "timeout client" I found that setting it back to 1m caused the errors to start again. I changed it back and forth and found that 4 minutes causes errors, and 6m stops them, so I left it at 6m. These are my active variables: root@us01odc-dev2-ctrl1:/etc/mysql# mysql -e 'show variables;'|grep timeout connect_timeout 20 deadlock_timeout_long 50000000 deadlock_timeout_short 10000 delayed_insert_timeout 300 idle_readonly_transaction_timeout 0 idle_transaction_timeout 0 idle_write_transaction_timeout 0 innodb_flush_log_at_timeout 1 innodb_lock_wait_timeout 50 innodb_rollback_on_timeout OFF interactive_timeout 28800 lock_wait_timeout 86400 net_read_timeout 30 net_write_timeout 60 rpl_semi_sync_master_timeout 10000 rpl_semi_sync_slave_kill_conn_timeout 5 slave_net_timeout 60 thread_pool_idle_timeout 60 wait_timeout 3600 So it looks like the value of "timeout client" in haproxy.cfg needs to match or exceed the value of "wait_timeout" in mysql. Also in nova.conf I see "#connection_recycle_time = 3600" - I need to experiment to see how that value interacts with the timeouts in the other config files. Is this the best way to find the correct config values? It seems like there should be a document that talks about these timeouts and how to set them (or maybe more generally how the different timeout settings in the various config files interact). Does that document exist? If not, maybe I could write one, since I have to figure out the correct values anyway.

4 5

[openstack-helm] Core Reviewer Nominations
by Pete Birley 20 Jan '20

20 Jan '20

OpenStack-Helm team, Based on their record of quality code review and substantial/meaningful code contributions to the openstack-helm project, at last weeks meeting we proposed the following individuals as core reviewers for openstack-helm: - Gage Hugo - Steven Fitzpatrick All OpenStack-Helm Core Reviewers are invited to reply with a +1/-1 by EOD next Monday (27/1/2020). A lone +1/-1 will apply to both candidates, otherwise please spell out votes individually for the candidates. Cheers, Pete

2 1

[neutron] Bug deputy report for week of January 13th
by Brian Haley 20 Jan '20

20 Jan '20

Hi, I was Neutron bug deputy last week. Below is a short summary about reported bugs. -Brian Critical bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1859988 - neutron-tempest-plugin tests fail for stable/queens - bcafarel picked up, related to below bug * https://bugs.launchpad.net/neutron/+bug/1860033 - neutron tempest jobs broken on rocky due to requirements neutron-lib upgrade - many proposed changes, discussion on ML High bugs --------- * https://bugs.launchpad.net/neutron/+bug/1859977 - [OVN] Update of floatingip creates new row in NBDB NAT table - maciej picked up * https://bugs.launchpad.net/neutron/+bug/1860140 - [OVN] Provider driver sends malformed update to Octavia - https://review.opendev.org/#/c/703097 * https://bugs.launchpad.net/neutron/+bug/1860141 - [OVN] Provider driver fails while LB VIP port already created - https://review.opendev.org/#/c/703110 Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/1859832 - L3 HA connectivity to GW port can be broken after reboot of backup node - Issue with MLDv2 packet causing issues with connections - Slawek picked up ownership * https://bugs.launchpad.net/neutron/+bug/1860273 - https://review.opendev.org/#/c/703292/ Low bugs -------- * https://bugs.launchpad.net/neutron/+bug/1859765 - Sgs of device_owner_network port can be update without specifing "device_owner" attr - https://review.opendev.org/#/c/702632/ - discussion in review * https://bugs.launchpad.net/neutron/+bug/1859962 - Sanity checks comparing versions should not use decimal comparison - https://review.opendev.org/#/c/702847/ Wishlist bugs ------------- Invalid bugs ------------ * https://bugs.launchpad.net/neutron/+bug/1859638 - VIP between dvr east-west networks does not work at all - Duplicate of https://bugs.launchpad.net/neutron/+bug/1774459 * https://bugs.launchpad.net/neutron/+bug/1859976 - Removing smart_nic port in openstack will try to delete representor port - os-vif issue Further triage required ----------------------- * https://bugs.launchpad.net/neutron/+bug/1859362 - Neutron accepts arbitrary MTU values for networks - Rodolfo has some questions on the bug * https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1859649 - networking disruption on upgrade from 14.0.0 to 14.0.3 - Rodolfo had question about restart order of services * https://bugs.launchpad.net/neutron/+bug/1859887 - External connectivity broken because of stale FIP rule - Asked for release information, etc * https://bugs.launchpad.net/networking-ovn/+bug/1859965 - networking-ovn's octavia api，how get octavia-api DB use python code? - networking-ovn octavia driver bug? asked for more information

2 1

[release] Python universal wheel support
by Sean McGinnis 20 Jan '20

20 Jan '20

Greetings, We have just merged a change to the release-openstack-python job that changes the wheels we produce to not be universal. For some background - we added an explicit flag of "--universal" to the creation of wheels a while back. For projects that have both Python 2 and 3 support, you want an universal wheel. Not all (probably most) projects did not add this flag to their setup.cfg, so overriding at the release job level was considered a good way to make sure our output was what we wanted at the time. We now have the majority of projects dropping py2 support, so we actually no longer want to create these universal wheels if py2 support has been dropped. That has actually been seen to cause some issues. The downside with this change is that the job is for *all* deliverables we release, including stable releases. So with this change, any new stable branches will no longer get universal wheels if the flag has not been set locally. This was deemed a good tradeoff with the current needs though. The lack of a univeral wheel may just make installation of py2 stable deliverables just slightly slower, but should not cause any real issues. Actions ------ Most likely this won't require any actions on the project team's part. If you have a project that still supports both py2 and py3 and do not have the flag set in setup.cfg, that can be added to still get the universal wheels built. That is done by adding the following: ``` [bdist_wheel] universal = 1 ``` Again, the performance impact is probably very minimal during installation, so this shouldn't be a major concern. If there are any oddities noticed after this change, please bring them up and we can help investigate what is happening. Thanks! Sean

1 0

[Multi-Arch-sig] Meeting this week
by Rico Lin 20 Jan '20

20 Jan '20

Hi all. As reminder, we will host our meeting this week. Tuesday at 0800 UTC in #openstack-meeting-alt and 1500 UTC in #openstack-meeting . Feel free to propose agenda here https://etherpad.openstack.org/p/Multi-Arch-agenda See you all in meeting:) -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0