February 2020 - openstack-discuss

[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 03 Feb '20

03 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 02 Feb '20

02 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 02 Feb '20

02 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