- openstack-discuss - lists.openstack.org

[manila] Manila Drivers and CI Status
by Douglas 04 Feb '20

04 Feb '20

Hi all, In the past months we have been analyzing drivers that are not reporting any status on patches submitted to the master branch of the openstack/manila repository [1]. We would like to request to driver maintainers to pay attention on the following warnings: 1. CI's that are not running and qualifying changes on master branch will be marked as `Not Qualified` on Manila's wiki page [2]. This annotation should help clarify to deployers/operators what drivers have been tested. A link to this will be created within Manila's administrator and user documentation [3]. 2. Python runtimes for Train and Ussuri cycles have been published by the OpenStack TC and we expect vendor CIs to adhere to these [4][5]. That said, no CIs should be running master (Ussuri) with python < 3.6. 3. If your CI system, and recheck trigger are missing from the Third Party CI wiki page [6], please add it. As has been the norm, no vendor driver changes will be allowed to merge without Third Party CI assuring us that the change has been tested for regressions. If you have any questions/concerns regarding CI and testing your drivers, please reach out to us here (openstack-discuss(a)lists.openstack.org) or on #openstack-manila [1] https://docs.google.com/spreadsheets/d/1dBSCqtQKoyFMX6oWTahhP9Z133NRFW3ynez… [2] https://wiki.openstack.org/wiki/Manila [3] https://docs.openstack.org/manila/latest/index.html [4] https://governance.openstack.org/tc/reference/runtimes/train.html [5] https://governance.openstack.org/tc/reference/runtimes/ussuri.html [6] https://wiki.openstack.org/wiki/ThirdPartySystems Thanks! Douglas Viroel (dviroel)

1 0

Re: Migration to Openstack from Proxmox
by Erik McCormick 04 Feb '20

04 Feb '20

+list again :) On Tue, Feb 4, 2020, 8:46 AM <jmacer(a)42iso.com> wrote: > Thanks for the reply. > > So if I understand you, swift is not an acceptable storage solution to > couple with OpenStack? I also think that I missed something in your first > paragraph "whereas you may be used concept being native in Proxmox." Are > you talking about how Proxmox has the local storage on the server AND the > NFS storage? > Swift is an Openstack project so sure it's good to use with Openstack or even on it's own. It is Object Storage (like AWS S3). If you want volumes you'll want some other system like Ceph, some NFS server, etc. Proxmox is capable of deploying Ceph and that's what I was referring to. > All of our VM's are the standard VM. We do have a few "templates" but > those are not really anything special. I do have quite a few images > pre-built, so that is my biggest concern with a migration. > You can easily import those images into Glance (Openstack image service);and then launch instances using them. > I know, just from looking at the docs/videos out there that OpenStack is > definitely more akin to AWS than it is ProxMox, but would you say it is > worth it from a manage a multi-location hardware environment to switch to > OpenStack from proxmox? > This is mainly a matter of your use case. Openstack is complex; more complex than Proxmox by quite a bit. It is also extremely powerful and has many projects to provide lots of cloudy services. Many of those services are analogous to ones found in AWS and other public clouds. It is well suited to orchestrate large numbers of instances, volumes, networks, etc. across many hypervisors, Proxmox, as far as I recall, is more of a straight virtualization platform. I also recall it being fairly simple and reliable. If it meets your needs, don't complicate your life. You may want to sign up for a trial at an Openstack-based public cloud provider to get familiar with the functionality before committing to building your own. You can find a list here: https://www.openstack.org/passport/ Cheers, Erik Thanks! > > > Jason > > -------- Original Message -------- > Subject: Re: Migration to Openstack from Proxmox > Date: 2020-02-04 07:33 > From: Erik McCormick <emccormick(a)cirrusseven.com> > To: jmacer(a)42iso.com > > > > > On Mon, Feb 3, 2020, 3:28 PM <jmacer(a)42iso.com> wrote: > > We currently are using proxmox for a envrionment management, and while we > were looking at DFS options we came across openstack, and we've decided to > start looking at it as a replacement for proxmox. Has anyone made this > migration before? > > > Keep on mind that you're still going to need a storage system like Ceph > separate from Openstack whereas you may be used concept being native in > Proxmox. > > Besides that, migration is pretty straightforward. I assume you're already > running on KVM, so you should be able to snapshot and import your current > instances, volumes, etc. > > > > Currently we're running a few Windows Server 12/16/19 virtual machines, > but mostly centOS7 virtual machines, however what we are developing are > micro-services that ideally would be deployed using k8s. > > Openstack and k8s are great together. Check out the Openstack Magnum > project, cloudprovider-openstack, and if you're trying to so multiattach > persistent volumes, Manila. > > > Does anyone have any experience migrating between the two, or any other > recommendation when considering openstack? > > Follow one of the install guides on docs.openstack.org to do a manual > install so you get familiar with all the bits and bobs under the hood. > After that, pick a deployment project to create your production cluster. > Kolla-ansible, Openstack-ansible, Triple-O, and Juju are some popular ones. > > Cheers, > Erik > > > > >

1 0

[goals][Drop Python 2.7 Support] Week R-15 2nd Update (# 2 weeks left to complete)
by Ghanshyam Mann 04 Feb '20

04 Feb '20

Hello Everyone, Below is the progress on "Drop Python 2.7 Support" at end of R-15 week. Schedule: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html#sc… Highlights: ======== * 2 weeks left to finish the work. * QA tooling: ** Tempest is dropping py3.5[1]. Tempest plugins can drop py3.5 now if they still support it. ** Updating tox with basepython python3 [2]. ** Pining stable/rocky testing with 23.0.0[3]. ** Updating neutron-tempest-plugins rocky jobs to run with py3 on master and py2 on stable/rocky gate. ** Ironic-tempest-plugin jobs are failing on uploading image on glance. Debugging in progress. * zipp failure fix on py3.5 job is merged. * 5 services listed below still not merged the patches, 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 * ec2-api * Karbor * Masakari * 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. * Most of the tempest plugins and python client patches are good to merge. * 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://review.opendev.org/#/c/704840/ [2] https://review.opendev.org/#/c/704688/ [3] https://review.opendev.org/#/c/705098/ -gmann

1 1

Migration to Openstack from Proxmox
by jmacer＠42iso.com 04 Feb '20

04 Feb '20

We currently are using proxmox for a envrionment management, and while we were looking at DFS options we came across openstack, and we've decided to start looking at it as a replacement for proxmox. Has anyone made this migration before? Currently we're running a few Windows Server 12/16/19 virtual machines, but mostly centOS7 virtual machines, however what we are developing are micro-services that ideally would be deployed using k8s. Does anyone have any experience migrating between the two, or any other recommendation when considering openstack?

2 1

[nova] noVNC console with password authentication
by Brin Zhang(张百林) 04 Feb '20

04 Feb '20

Hi all: About https://review.opendev.org/#/c/623120/ SPEC, there are two different perspectives, one from Alex and one from SPEC author Jingyu. 1. @Jingyu’s point is add“vnc_password”to the instance’s metadata,“vnc_password”is only provided for libvirtd support. As described in SPEC, the“vnc_password”parameter is populated when the instance generates XML, and when show server details that pop the “vnc_password”from nova api to ensure its security. That we can refer to the implementation of "adminPass" to understand this method. Its advantage is that it will not break the current nova api, you only need to store“vnc_password”in the instance's metadata. The disadvantage is that“vnc_password”is in the metadata but the user cannot get it. In addition, after we are evacuate/rebuild a server that we should reset it’s“vnc_password”, or take out "vnc_password" from the original instance and write into the new instance during evacuate/rebuild. 2. @Alex’s suggestion is change the Create Console API, add“vnc_password”as a new request optional parameter to the request body, that when we request create the remote console, if the“vnc_password”is not None we will reset the server’s vnc passwd, if“vnc_password”is None, that it will use the novnc password set last time you opened the console. The advantage is that it is more simple and convenient than storing "vnc_password" in metadata. When evacuate/rebuild, there is no need to consider the problem of "vnc_password" storage, but when we first open the console, we need to set it in the request body the value of "vnc_password". The disadvantage is that you need to add a new microversion to support this feature, which will break the current nova API (Create Console API). In addition, from the working principle of the RFB protocol, nova does not care about the "vnc_password" parameter passed in to obtain the Console URL. The verification of the vnc password is the job of the vnc server maintained by libvirtd. We look forward to completing it before the SPEC freeze, and hope to get more feedback, especially from the nova core team. SPEC link: https://review.opendev.org/#/c/623120/ brinzhang

1 0

[kuryr] Deprecation of Ingress support and namespace isolation
by Michał Dulko 04 Feb '20

04 Feb '20

Hi, I've decided to put up a patch [1] deprecating the aforementioned features. It's motivated by the fact that there are better ways to do both: * Ingress can be done by another controller or through cloud provider. * Namespace isolation can be achieved through network policies. Both alternative ways are way better tested and there's nobody maintaining the deprecated features. I'm open to keep them if someone using them steps up. With the fact that Kuryr seems to be tied more with Kubernetes releases than with OpenStack ones and given there will be no objections, we might start removing the code in the Ussuri timeframe. [1] https://review.opendev.org/#/c/703420/ Thanks, Michał

2 1

RDO OpenStack Repo for CentOS 8
by Pradeep Antil 04 Feb '20

04 Feb '20

Hi Folks, I am trying to deploy single node openstack on CentOS 8 using packstack, but it seems like CentOS 8 packages are not updated in repo. Has anyone tried this before on centos 8 , if yes what repository should I use ? [root@xxxxx~]# dnf install -y https://www.rdoproject.org/repos/rdo-release.rpm Last metadata expiration check: 0:02:17 ago on Tue 04 Feb 2020 03:07:49 AM EST. rdo-release.rpm 936 B/s | 6.4 kB 00:07 Dependencies resolved. ============================================================================================================================== Package Architecture Version Repository Size ============================================================================================================================== Installing: rdo-release noarch stein-3 @commandline 6.4 k Transaction Summary ============================================================================================================================== Install 1 Package Total size: 6.4 k Installed size: 3.1 k Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : rdo-release-stein-3.noarch 1/1 Verifying : rdo-release-stein-3.noarch 1/1 Installed: rdo-release-stein-3.noarch Complete! [root@xxxx ~]# [root@xxxx ~]# [root@xxxx ~]# dnf install -y openstack-packstack RDO CentOS-7 - QEMU EV 42 kB/s | 35 kB 00:00 OpenStack Stein Repository 1.3 MB/s | 4.1 MB 00:03 Last metadata expiration check: 0:00:01 ago on Tue 04 Feb 2020 03:12:15 AM EST. Error: Problem: cannot install the best candidate for the job - nothing provides python-netifaces needed by openstack-packstack-1:14.0.0-1.el7.noarch - nothing provides PyYAML needed by openstack-packstack-1:14.0.0-1.el7.noarch - nothing provides python-docutils needed by openstack-packstack-1:14.0.0-1.el7.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [root@xxxxx ~]# -- Best Regards Pradeep Kumar

2 1

[cinder][ci] Cinder drivers being Unsupported and General CI Status ...
by Jay Bryant 04 Feb '20

04 Feb '20

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 jsbryant(a)electronicjungle.net IRC: jungleboyj

7 8

[oslo] drop 2.7 support - track releases
by Herve Beraud 04 Feb '20

04 Feb '20

Hello, FYI you can track the dropping of py2.7 support in oslo by using: https://review.opendev.org/#/q/topic:oslo_drop_py2_support+(status:open+OR+… Topic: oslo_drop_py2_support We release a major version each time an oslo projects drop the py2.7 support. -- Hervé Beraud Senior Software Engineer Red Hat - Openstack Oslo irc: hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

2 3

[security] No Security SIG Meeting - Feb 06th
by Gage Hugo 03 Feb '20

03 Feb '20

The Security SIG won't be meeting this Thursday, Feb 06th, we will be back next week. For any questions please feel free to ask in #openstack-security. Thanks

1 0

[security] Security SIG Newsletter - Jan 2020
by Gage Hugo 03 Feb '20

03 Feb '20

Hope everyone's 2020 is going good so far, here's the list of updates from the Security SIG. Overall Jan was a pretty quiet month, only have a few update items. #Month Jan 2020 - Security SIG Meeting Info: http://eavesdrop.openstack.org/#Security_SIG_meeting - Weekly on Thursday at 1500 UTC in #openstack-meeting - Agenda: https://etherpad.openstack.org/p/security-agenda - https://security.openstack.org/ - https://wiki.openstack.org/wiki/Security-SIG #Updates - https://review.opendev.org/#/c/678426/ - Update to vmt policy, currently up for formal TC review - https://bugs.launchpad.net/nova/+bug/1492140 - Updates to stable branches - https://bugs.launchpad.net/neutron/+bug/1732067 - Backports to stable branches may require a configuration change #VMT Reports - A full list of publicly marked security issues can be found here: https://bugs.launchpad.net/ossa/

1 0

[Ansible] European Ansible Cntributors Summit
by Amy Marrich 03 Feb '20

03 Feb '20

This was shared on the OpenStack-Ansible channel this morning and I wanted to share with everyone using Ansible who might be interested in attending. https://groups.google.com/forum/#!topic/ansible-outreach/sLte90d5hdc Thanks, Amy (spotz)

1 0

[neutron] Bug Deputy Report Jan. 27 - Feb. 3
by Ryan Tidwell 03 Feb '20

03 Feb '20

Here's this week's bug report for neutron: https://bugs.launchpad.net/neutron/+bug/1861269 Functional tests failing due to failure with getting datapath ID from ovs Fix merged to master, backports in progress https://review.opendev.org/705401 https://review.opendev.org/705400 https://review.opendev.org/705399 https://review.opendev.org/705398 https://bugs.launchpad.net/neutron/+bug/1861442 QOS minimum bandwidth rejection of non-physnet network and updates should be driver specific This was discussed in the drivers meeting. The short-term plan is move where validation is done, then there is likely an RFE to tackle once this fixed. https://bugs.launchpad.net/neutron/+bug/1861496 All ports of server instance are open even no security group does allow this This one is worth a look as it involves security groups potentially not filtering things as expressed by the user. I asked a follow-up question in launchpad, others should chime in. https://bugs.launchpad.net/neutron/+bug/1861502 [OVN] Mechanism driver - failing to recreate floating IP Some errors related to the OVN ML2 driver are being observed in the gate "TypeError: create_floatingip() missing 1 required positional argument: 'floatingip'" https://bugs.launchpad.net/neutron/+bug/1861670 AttributeError: 'NetworkConnectivityTest' object has no attribute 'safe_client' Fix proposed - https://review.opendev.org/#/c/705413/ https://bugs.launchpad.net/neutron/+bug/1861674 Gateway which is not in subnet CIDR is unsupported in ha router This could use some follow-up by the team for clarification Some OVN scheduler-related issues: [OVN] GW rescheduling mechanism is triggered on every Chassis updated unnecessarily https://bugs.launchpad.net/bugs/1861510 Some PoC code up for review - https://review.opendev.org/#/c/705331/ https://bugs.launchpad.net/bugs/1861509 [OVN] GW rescheduling logic is broken RFE's: https://bugs.launchpad.net/neutron/+bug/1861032 Add support for configuring dnsmasq with multiple IPv6 addresses in same subnet on same port https://bugs.launchpad.net/neutron/+bug/1861529 A port's network should be changable -Ryan

1 0

Re: [magnum] Help / Pointers on mirroring https://opendev.org/starlingx in github.com for CNCF certification of starlingx
by Roman Gorshunov 03 Feb '20

03 Feb '20

Hello Bin, Yes, that's correct. When you are connecting to the GitHub, your username should be git. GitHub recognizes you by your SSH key [0]. Example: [roman@pc ~]$ ssh git(a)github.com PTY allocation request failed on channel 0 Hi gorshunovr! You've successfully authenticated, but GitHub does not provide shell access. Connection to github.com closed. [roman@pc ~]$ As you may see, GitHub has recognized me as 'gorshunovr', despite I was using 'git' as a username for SSH. [0] https://help.github.com/en/github/authenticating-to-github/testing-your-ssh… Please, use mailing list for the communication, not direct e-mail. Thank you. Best regards, -- Roman Gorshunov On Mon, Feb 3, 2020 at 3:53 PM Qian, Bin <Bin.Qian(a)windriver.com> wrote: > > Hi Roman, > > Thank you for the information about GitHub mirroring. > Based on the info below, I think what we want to do is to: > 1. create a GitHub account, which has the privilege to commit to our repos, > 2. with the account, create ssh key on zuul server and upload the ssh key to GitHub > 3. use zuul tool [3] to create zuul job secret, embed it to the upload job in zuul.yaml > 4. add the upload job a post job > > But I am not very sure about the step 1, as in the reference [4] below, it states, > "For GitHub, the user parameter is git, not your personal username." > > Would you please let me know if my steps above is correct? > > Thanks, > > Bin > > ________________________________ > From: Waines, Greg > Sent: Thursday, January 30, 2020 10:21 AM > To: Qian, Bin > Cc: Eslimi, Dariush; Khalil, Ghada > Subject: FW: [magnum] Help / Pointers on mirroring https://opendev.org/starlingx in github.com for CNCF certification of starlingx > > fyi > > > > From: Roman Gorshunov <paye600(a)gmail.com> > Date: Thursday, January 30, 2020 at 11:38 AM > To: "openstack-discuss(a)lists.openstack.org" <openstack-discuss(a)lists.openstack.org> > Subject: Re: [magnum] Help / Pointers on mirroring https://opendev.org/starlingx in github.com for CNCF certification of starlingx > > > > Hello Greg, > > > > - Create a GitHub account for the starlingx, you will have URL on > > GitHub like [0]. You may try to contact GitHub admins and ask to > > release starlingx name, as it seems to be unused. > > - Then create SSH key and upload onto GitHub for that account in > > GitHub interface > > - Create empty repositories under [1] to match your existing > > repositories names here [2] > > - Encrypt SSH private key as described here [3] or here [4] using this tool [5] > > - Create patch to all your projects under [2] to '/.zuul.yaml' file, > > similar to what is listed here [6] > > - Change job name shown on line 407 via URL above, description (line > > 409), git_mirror_repository variable (line 411), secret name (line 414 > > and 418), and SSH key starting from line 424 to 463, to match your > > project's name, repo path on GitHub, and SSH key > > - Submit changes to Gerrit with patches for all your project and get > > them merged. If all goes good, the next change merged would trigger > > your repositories to be synced to GitHub. Status could be seen here > > [7] - search for your newly created job manes, they should be nested > > under "upload-git-mirrorMirrors a tested project repository to a > > remote git server." > > > > Hope it helps. > > > > [0] https://github.com/starlingxxxx > > [1] https://github.com/starlingxxxx/... > > [2] https://opendev.org/starlingx/... > > [3] https://docs.openstack.org/infra/manual/zuulv3.html#secret-variables > > [4] https://docs.openstack.org/infra/manual/creators.html#mirroring-projects-to… > > [5] https://opendev.org/zuul/zuul/src/branch/master/tools/encrypt_secret.py > > [6] https://opendev.org/airship/deckhand/src/commit/51dcea4fa12b0bcce65c381c286… > > [7] https://zuul.openstack.org/jobs > > > > Sample content of your addition (patch) to your '/.zuul.yaml' files: > > =================================================== > > - job: > > name: starlingx-compile-upload-git-mirror > > parent: upload-git-mirror > > description: Mirrors starlingx/compile to starlingxxxx/compile > > vars: > > git_mirror_repository: starlingxxxx/compile > > secrets: > > - name: git_mirror_credentials > > secret: starlingx-compile-github-secret > > pass-to-parent: true > > > > - secret: > > name: starlingx-compile-github-secret > > data: > > user: git > > host: github.com > > host_key: github.com ssh-rsa > > AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ== > > ssh_key: !encrypted/pkcs1-oaep > > - <here goes encrypted SSH private key> > > =================================================== > > > > Best regards, > > -- > > Roman Gorshunov > > > >

2 1

[qa] Proposing Radosław Piliszek to devstack core
by Ghanshyam Mann 03 Feb '20

03 Feb '20

Hello Everyone, Radosław Piliszek (yoctozepto) has been doing nice work in devstack from code as well as review perspective. He has been helping for many bugs fixes nowadays and having him as Core will help us to speed up the things. I would like to propose him for Devstack Core. You can vote/feedback on this email. If no objection by end of this week, I will add him to the list. -gmann

4 4

[Watcher] confused about meeting schedule
by info＠dantalion.nl 03 Feb '20

03 Feb '20

Hello everyone, The documentation for Watcher states that meetings will be held on a bi-weekly basis on odd-weeks, however, last meeting was held on the 8th of January which is not an odd-week. Today I was expecting a meeting as the meetings are held bi-weekly and the last one was held on the 8th of January, however, there was none. Can someone clarify when the next meeting will be held and the subsequent one after that? If these are on even weeks we should also update Watcher's documentation. Kind regards, Corne lukken

3 4

[openstack-dev][kuryr] How to add new worker node
by VeeraReddy 03 Feb '20

03 Feb '20

Hi , I successfully install kuryr-kubernetes using below linkhttps://docs.openstack.org/kuryr-kubernetes/latest/installation/devstac… How to add a new external worker node to existing controller node. Regards, Veera.

2 1

Kayobe Openstack deployment
by Tony Pearce 03 Feb '20

03 Feb '20

Hi all - I wanted to ask if there was such a reference architecture / step-by-step deployment guide for Openstack / Kayobe that I could follow to get a better understanding of the components and how to go about deploying it? The documentation is not that great so I'm hitting various issues when trying to follow what is there on the Openstack site. There's a lot of technical things like information on variables - which is fantastic, but there's no context about them. For example, the architecture page is pretty small, when you get further on in the guide it's difficult to contextually link detail back to the architecture. I tried to do the all-in-one deployment as well as the "universe from nothing approach" but hit some issues there as well. Plus it's kind of like trying to learn how to drive a bus by riding a micro-scooter :) Also, the "report bug" bug link on the top of all the pages is going to an error "page does not exist" - not sure that had been realised yet. Regards, *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

[kolla] ujson issue affected to few containers.
by Eddie Yen 02 Feb '20

02 Feb '20

Hi everyone, I'm not sure it should be bug report or not. So I email out about this issue. In these days, I found the Rocky source deployment always failed at Ceilometer bootstrapping. Then I found it failed at ceilometer-upgrade. So I tried to looking at ceilometer-upgrade.log and the error shows it failed to import ujson. https://pastebin.com/nGqsM0uf Then I googled it and found this issue is already happened and released fixes. https://github.com/esnme/ultrajson/issues/346 But it seems like the container still using the questionable one, even today (Jan 30 UTC+8). And this not only affected to Ceilometer, but may also Gnocchi. I think we have to patch it, but not sure about the workaround. Does anyone have good idea? Many thanks, Eddie.

3 9

[horizon] [keystone] Re: [User-committee] Help
by Amy Marrich 01 Feb '20

01 Feb '20

Pradeep, I am sending this to the OpenStack discuss mailing list where you might be able to receive more help. I have tagged both the Horizon and Keystone teams as the error seems to be from Horizon and concerning Keystone. In order to provide more assistance, information as to what you were doing at the time will be needed. Please confirm this is OpenStack Rocky on CentOS and how you installed, from scratch, TripleO, OpenStack-Ansible, etc. Thanks, Amy (spotz) > On Feb 1, 2020, at 7:11 AM, pradeep pal <pspal83(a)hotmail.com> wrote: > > > Rocky+Centos 7.7 64bit, > > 2020-02-01 18:26:38.063938 ArgsAlreadyParsedError: arguments already parsed: cannot register CLI option > 2020-02-01 18:26:38.549453 mod_wsgi (pid=82228): Target WSGI script '/usr/bin/keystone-wsgi-public' cannot be loaded as Python module. > 2020-02-01 18:26:38.549516 mod_wsgi (pid=82228): Exception occurred processing WSGI script '/usr/bin/keystone-wsgi-public'. > 2020-02-01 18:26:38.549558 Traceback (most recent call last): > 2020-02-01 18:26:38.549600 File "/usr/bin/keystone-wsgi-public", line 54, in <module> > 2020-02-01 18:26:38.549666 application = initialize_public_application() > 2020-02-01 18:26:38.549695 File "/usr/lib/python2.7/site-packages/keystone/server/wsgi.py", line 24, in initialize_public_application > 2020-02-01 18:26:38.549763 name='public', config_files=flask_core._get_config_files()) > 2020-02-01 18:26:38.549799 File "/usr/lib/python2.7/site-packages/keystone/server/flask/core.py", line 149, in initialize_application > 2020-02-01 18:26:38.549862 keystone.server.configure(config_files=config_files) > 2020-02-01 18:26:38.549897 File "/usr/lib/python2.7/site-packages/keystone/server/__init__.py", line 28, in configure > 2020-02-01 18:26:38.549958 keystone.conf.configure() > 2020-02-01 18:26:38.549988 File "/usr/lib/python2.7/site-packages/keystone/conf/__init__.py", line 125, in configure > 2020-02-01 18:26:38.550040 help='Do not monkey-patch threading system modules.')) > 2020-02-01 18:26:38.550084 File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2501, in __inner > 2020-02-01 18:26:38.550137 result = f(self, *args, **kwargs) > 2020-02-01 18:26:38.550164 File "/usr/lib/python2.7/site-packages/oslo_config/cfg.py", line 2776, in register_cli_opt > 2020-02-01 18:26:38.550225 raise ArgsAlreadyParsedError("cannot register CLI option") > 2020-02-01 18:26:38.550276 ArgsAlreadyParsedError: arguments already parsed: cannot register CLI option > > > > > _______________________________________________ > User-committee mailing list > User-committee(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee

2 1

[nova] I would like to add another option for cross_az_attach
by Kim KS 01 Feb '20

01 Feb '20

Hello all, In nova with setting [cinder]/ cross_az_attach option to false, nova creates instance and volume in same AZ. but some of usecase (in my case), we need to attach new volume in different AZ to the instance. so I need two options. one is for nova block device mapping and attaching volume and another is for attaching volume in specified AZ. [cinder] cross_az_attach = False enable_az_attach_list = AZ1,AZ2 how do you all think of it? Best, Kiseok

4 4

[cinder] last call for ussuri spec comments
by Brian Rosmaita 01 Feb '20

01 Feb '20

The following specs have two +2s. I believe that all expressed concerns have been addressed. I intend to merge them at 22:00 UTC today unless a serious issue is raised before then. https://review.opendev.org/#/c/684556/ - support volume-local-cache https://review.opendev.org/#/c/700977 - add backup id to volume metadata cheers, brian

3 3

"encoding error when doing console log show" in Rocky
by Albert Braden 31 Jan '20

31 Jan '20

We're running openstack-ansible Rocky and seeing the "encoding error when doing console log show." I see here that there is a patch: https://bugs.launchpad.net/python-openstackclient/+bug/1747862 How can I apply this patch to our Rocky install? Do I need to just copy the file over the existing /usr/lib/python2.7/dist-packages/openstackclient/compute/v2/console.py on controllers and hypervisors? Or is there a better way?

2 13

[tripleo] no rechecks
by Wesley Hayutin 31 Jan '20

31 Jan '20

Greetings, Hey folks we need a few patches to land before it's safe to blindly recheck. A few minor patches need to land before you can expect to get +1 from zuul in a lot of cases. We appreciate your patience while we resolve the issues. Thanks * TRIPLEO GATES ARE BROKEN* * need two patches to fix - * https://review.opendev.org/#/c/705051/ - * https://review.opendev.org/#/c/704885/ - * Also need - * https://review.rdoproject.org/r/#/c/24754/

1 1

[all][requirements][qa] zipp failing py3.5 again
by Radosław Piliszek 31 Jan '20

31 Jan '20

Folks, we are running circles here. [1] merged breaking zipp again for py3.5 The script which generates these proposals needs to learn python version constraints. Reproposed [2]. [1] https://review.opendev.org/705128 [2] https://review.opendev.org/705184 -yoctozepto

3 4

[ironic] An approach to removing WSME
by Steve Baker 31 Jan '20

31 Jan '20

I've put together a set of changes for removing WSME which involves copying just enough of it into ironic, and I think we need to have the conversation about whether this approach is desirable :) This git branch[1] finishes with WSME removed and existing tests passing. Here are some stats about lines of code (not including unit tests, calculated with cloc): 4500 wsme/wsme 6000 ironic/ironic/api master 7000 ironic/ironic/api story/1651346 In words, we need 1000 out of 4500 lines of WSME source in order to support 6000 lines of ironic specific API code. Switching to a replacement for WSME would likely touch a good proportion of that 6000 lines of ironic specific API code. If we eventually replace it with a new library I think it would be easier if the thing being replaced is inside the ironic source tree to allow for a gradual transition. So this approach could be an end in itself, or it could be a step towards the final goal. My strategy for copying in code was to pull in chunks of required logic while removing some unused features (like request pass-through and date & time type serialization). I also replaced py2/3 patterns with pure py3. There is likely further things which can be removed or refactored for simplicity, but what exists currently works. If there is enough positive feedback for this approach I'll start on unit test coverage for the new code. [1] https://review.opendev.org/#/q/topic:story/1651346

3 2

[oslo] AFK this week
by Ben Nemec 31 Jan '20

31 Jan '20

I am going to be out most or all of this week. If someone wants to run the meeting on Monday then feel free to have it without me again. I may not be back right away next week either. A lot of stuff is still to be determined at this point. -Ben

1 1

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

31 Jan '20

# Keystone Team Update - Week of 27 January 2020 ## News ### 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 [1] [1] 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 19 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 26 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ### Priority Reviews * Ussuri Roadmap Stories - Groups in keystone SAML assertion https://tree.taiga.io/project/keystone-ussuri-roadmap/us/33 https://review.opendev.org/#/c/588211/ Add openstack_groups to assertion - Add support for modifying resource options to CLI tool https://tree.taiga.io/project/keystone-ussuri-roadmap/us/53 https://review.opendev.org/#/c/697444/ Adding options to user cli * Community Goals https://review.opendev.org/#/c/699119/ [ussuri][goal] Drop python 2.7 support and testing python-keystoneclient * Special Requests https://review.opendev.org/#/c/703578/ Updating tox -e all-plugin command https://review.opendev.org/#/c/704736/ Remove six usage ## Bugs This week we opened 4 new bugs and closed 4. Bugs opened (4) 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 Bug #1861264 (keystone:Undecided): Help information should be returned when executing 'placement-status' alone - Opened by Eric Xie https://bugs.launchpad.net/keystone/+bug/1861264 Bug #1861279 (keystone:Undecided): incomplete instruction in "Install and configure" in keystone in https://docs.openstack.org/keystone/train/install/keystone-install-rdo.html - Opened by Arie Maron https://bugs.launchpad.net/keystone/+bug/1861279 Bugs closed (4) Bug #1860252 (keystone:Undecided) https://bugs.launchpad.net/keystone/+bug/1860252 Bug #1861264 (keystone:Undecided) https://bugs.launchpad.net/keystone/+bug/1861264 Bug #1856904 (keystone:Undecided): CADF Notifications are missing user name in initiator object - Fixed by Gage Hugo https://bugs.launchpad.net/keystone/+bug/1856904 Bug #1858012 (keystone:Undecided): List role assignments by role ID may leak extra system assignments outside of filter - Fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1858012 ## Milestone Outlook https://releases.openstack.org/ussuri/schedule.html Milestone 2 is in two weeks, which means spec freeze is coming up followed closely by feature proposal freeze. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

[cinder][nova] Migrating servers' root block devices from a cinder backend to another
by Jean-Philippe Méthot 30 Jan '20

30 Jan '20

Hi, We have a several hundred VMs which were built on cinder block devices as root drives which use a SAN backend. Now we want to change their backend from the SAN to Ceph. We can shutdown the VMs but we will not destroy them. I am aware that there is a cinder migrate volume command to change a volume’s backend, but it requires that the volume be completely detached. Forcing a detached state on that volume does let the volume migration take place, but the volume’s path in Nova block_device_mapping doesn’t update, for obvious reasons. So, I am considering forcing the volumes to a detached status in Cinder and then manually updating the nova db block_device_mapping entry for each volume so that the VM can boot back up afterwards. However, before I start toying with the database and accidentally break stuff, has anyone else ever done something similar? Got any tips or hints on how best to proceed? Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc.

7 10

[openstack-ansible][ansible-sig][tripleo] Openstack Ansible modules - update on progress, new meeting time
by Sagi Shnaidman 30 Jan '20

30 Jan '20

Hi, all because no people have been available in the meeting, I'll write a quick summary in ML. Agenda and progress are tracked here as usual: https://etherpad.openstack.org/p/openstack-ansible-modules 1. Because people had overlapping meetings I've created a poll for better meeting time. I think we can switch now to the bi-weekly meeting if no objections to it. The poll is here: https://xoyondo.com/dp/ITMGRZSvaZaONcz 2. We have the same coverage as we had in Ansible repository, so now we can start to improve our testing. It should include a matrix with various ansible versions and openstacksdk versions. We had already some issues with versions mismatch [1] Also we should start to do a better module design. 3. In case of critical patches to 2.9 and when openstack modules will be removed from Ansible repo, please submit patches directly to the 2.9-stable branch of Ansible. Confirmed that with Ansible folks. 4. The CI job in Ansible repository now is failing with a message about moving modules. I hope it won't block from 2.9 patches to land but will do more checking. But at least we've got attention to the fact modules are moving. 5. Jobs for pushing collections to ansible-galaxy are in progress and please review patches in the repo in your time: [1] https://review.opendev.org/705054 [2] https://review.opendev.org/#/q/project:openstack/ansible-collections-openst… -- Best regards Sagi Shnaidman

1 0

[ops] Federated Identity Management survey
by Colleen Murphy 30 Jan '20

30 Jan '20

Hello operators, A researcher from the University of Kent who was influential in the design of keystone's federation implementation has asked the keystone team to gauge adoption of federated identity management in OpenStack deployments. This is something we've neglected to track well in the last few OpenStack user surveys, so I'd like to ask OpenStack operators to please take a few minutes to complete the following survey about your usage of identity federation in your OpenStack deployment (even if you don't use federation): https://uok.typeform.com/to/KuRY0q The results of this survey will benefit not only university research but also the keystone team as it will help us understand where to focus our efforts. Your participation is greatly appreciated. Thanks for your time, Colleen (cmurphy)

1 3

[neutron][drivers team] Proposing Nate Johnston as drivers team member
by Slawek Kaplonski 30 Jan '20

30 Jan '20

Hi Neutrinos, I would like to propose Nate Johnston to be part of Neutron drivers team. Since long time Nate is very active Neutron's core reviewer. He is also actively participating in our Neutron drivers team meetings and he shown there that he has big experience and knowledge about Neutron, Neutron stadium projects as well as whole OpenStack. I think that he really deservers to be part of this team and that he will be great addition it. I will wait for Your feedback for 1 week and if there will be no any votes agains, I will add Nate to drivers team in next week. -- Slawek Kaplonski Senior software engineer Red Hat

5 5

[nova] API updates week 20-5
by Ghanshyam Mann 30 Jan '20

30 Jan '20

Hello Everyone, Please find the Nova API updates of this week. Please add if I missed any BPs/API related work. API Related BP : ============ COMPLETED: 1. Add image-precache-support spec: - https://blueprints.launchpad.net/nova/+spec/image-precache-support Code Ready for Review: ------------------------------ 1. Nova API policy improvement - Topic: https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh+(status:ope… - Weekly Progress: First set is merged and 4 APIs policy are ready to review. I will push more changes in this week. - Review guide over ML - http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008504.h… Specs are merged and code in-progress: ------------------------------ ------------------ 1. Non-Admin user can filter their instance by availability zone: - Topic: https://review.opendev.org/#/q/topic:bp/non-admin-filter-instance-by-az+(st… - Weekly Progress: Spec is just merged. 2. Boot from volume instance rescue - Topic: https://review.opendev.org/#/q/topic:bp/virt-bfv-instance-rescue+(status:op… - Weekly Progress: Code is in progress. WIP as of now. Spec Ready for Review or Action from Author: --------------------------------------------------------- 1. Support specifying vnic_type to boot a server -Spec: https://review.opendev.org/#/c/672400/ - Weekly Progress: As discussed in spec, this is something can be done via heat or other automation instead of doing it in nova. 2. Add action event fault details -Spec: https://review.opendev.org/#/c/699669/ - Weekly Progress: This seems good to go, it has two +2. 3. Allow specify user to reset password -Spec: https://review.opendev.org/#/c/682302/5 - Weekly Progress: One +2 on this but other are disagree on this idea. More discussion on review. 4. Support re-configure deleted_on_termination in server -Spec: https://review.openstack.org/#/c/580336/ - Weekly Progress: This is old spec and there is no consensus on this till now. Others: 1. None Bugs: ==== I will track the bug data from next report. NOTE- There might be some bug which is not tagged as 'api' or 'api-ref', those are not in the above list. Tag such bugs so that we can keep our eyes. -gmann

1 0

[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