November 2019 - openstack-discuss

[mitaka][keystone] Authentication over keycloak server possible?
by Michael Stang 02 Dec '19

02 Dec '19

Hi, we have an OpenStack Mitaka installation running (yes I know it's pretty old ;-) ) at our lab and would like to use the keycloak-server from the central IT for authentication. So I would like to know if it is already possible in mitaka to use this external keycloak server or if this only possible in a later OpenStack version? Maybe anyone know and if yes is there any documentation how to do it? Was searching for it but found not much about it by now... Thanks :) Kind regards Michael Michael Stang Laboringenieur, Dipl. Inf. (FH) Duale Hochschule Baden-Württemberg Mannheim Baden-Wuerttemberg Cooperative State University Mannheim ZeMath Zentrum für mathematisch-naturwissenschaftliches Basiswissen Fachbereich Informatik, Fakultät Technik Coblitzallee 1-9 68163 Mannheim michael.stang(a)dhbw-mannheim.de mailto:michael.stang@dhbw-mannheim.de http://www.mannheim.dhbw.de http://www.dhbw-mannheim.de/

2 2

[all] Nominations for the "V" release name
by Sean McGinnis 02 Dec '19

02 Dec '19

Hey everyone, There is ongoing discussion about changing our release naming process, but for the time being we are going to stick with what we have been doing. That means it's time to start thinking about the "V" release name! The next developer event will take place in Vancouver, BC. The geographic location for this release will be things starting with "V" in the British Columbia province. The nomination period is now open. Please add suitable names to https://wiki.openstack.org/wiki/Release_Naming/V_Proposals. We will accept nominations until December 6, 2019 23:59:59 UTC. A recap of our current naming rules: * Each release name must start with the letter of the ISO basic Latin alphabet following the initial letter of the previous release, starting with the initial release of "Austin". After "Z", the next name should start with "A" again. * The name must be composed only of the 26 characters of the ISO basic Latin alphabet. Names which can be transliterated into this character set are also acceptable. * The name must refer to the physical or human geography of the region encompassing the location of the OpenStack design summit for the corresponding release. The exact boundaries of the geographic region under consideration must be declared before the opening of nominations, as part of the initiation of the selection process. * The name must be a single word with a maximum of 10 characters. Words that describe the feature should not be included, so "Foo City" or "Foo Peak" would both be eligible as "Foo". Names which do not meet these criteria but otherwise sound really cool should be added to a separate section of the wiki page and the TC may make an exception for one or more of them to be considered in the Condorcet poll. The naming official is responsible for presenting the list of exceptional names for consideration to the TC before the poll opens. Additional information about the release naming process can be found here: https://governance.openstack.org/tc/reference/release-naming.html Looking forward to having a name for our next release! Sean

4 7

[neutron] Including networking-ovn-core team into neutron-core
by Slawek Kaplonski 02 Dec '19

02 Dec '19

Hi neutrinos, We recently merged spec [1] and now we are starting to moving networking-ovn code to be in neutron tree. Blueprint to track progress of this is on [2]. As a consequence of this merge of code, I think that we need to also include networking-ovn-core team into neutron-core to give people who are cores on networking-ovn today ability to merge ovn related patches in neutron after this migration will be done. Of course current networking-ovn cores should only approve patches related to ovn driver, and not approve patches related to different areas of neutron code. So if there will be no objections for that until the end of this week, I will include networking-ovn-core group in neutron-core. [1] https://review.opendev.org/#/c/658414/ [2] https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge — Slawek Kaplonski Senior software engineer Red Hat

2 2

[Usage][Designate] Salve Bind servers
by Steven Relf 02 Dec '19

02 Dec '19

Hi list.... I'm looking at making use of Designate, and have so farmanaged to get designate configured and working against a single bind9 server. The issue I'm having, and this could be due to notunderstanding bind config well, is how do I configure other bind servers to beslaves of the server used by designate. I keep running into an issue where theslave doesn’t want to do a transfer and errors with "received notify forzone 'domain': not authoritative" I'm assuming this has something to do with the slave notknowing about the zone. So the question, do I have to have all my bind servershooked upto designate, and managed with a mdns service, or am I missingsomething obvious. Rgds Steve. The future has already arrived. It's just not evenlydistributed yet - William Gibson

2 1

[Magnum] Virtual PTG planning
by Feilong Wang 02 Dec '19

02 Dec '19

Hi team, As we discussed on last weekly team meeting, we'd like to have a virtual PTG before the Xmas holiday to plan our work for the U release. The general idea is extending our current weekly meeting time from 1 hour to 2 hours and having 2 sessions with total 4 hours. My current proposal is as below, please reply if you have question or comments. Thanks. Pre discussion/Ideas collection: 20th Nov 9:00AM-10:00AM UTC 1st Session: 27th Nov 9:00AM-11:00AM UTC 2nd Session: 4th Dec 9:00AM-11:00AM UTC -- Cheers & Best regards, Feilong Wang (王飞龙) Head of R&D Catalyst Cloud - Cloud Native New Zealand -------------------------------------------------------------------------- Tel: +64-48032246 Email: flwang(a)catalyst.net.nz Level 6, Catalyst House, 150 Willis Street, Wellington --------------------------------------------------------------------------

3 4

Openstack - Rocky Install
by doug schmidt 01 Dec '19

01 Dec '19

Hi, I'm having an issue with httpd not starting on my install. I have installed rocky on a windows 10 laptop with virtualbox and centos 7 guests. So far I have 2 controllers and 3 compute nodes. I have followed the install docs for rocky. https://docs.openstack.org/install-guide/openstack-services.html#minimal-de… Minimal services have been installed and configured.keystone, glance, nova, neutron are configured and running. I followed the install for horizon dashboard, and that is where I'm getting httpd.service failing. I have gone over the configuration a few times, but I can not find what the issue is. Any ideas of where to look or what to fix? Thanks for any help with this ------------------------ [root@openstack-cntr1 ~]# systemctl | egrep -i 'openstack|neutron|httpd' ● httpd.service loaded failed failed The Apache HTTP Server neutron-dhcp-agent.service loaded active running OpenStack Neutron DHCP Agent neutron-linuxbridge-agent.service loaded active running OpenStack Neutron Linux Bridge Agent neutron-metadata-agent.service loaded active running OpenStack Neutron Metadata Agent neutron-server.service loaded active running OpenStack Neutron Server openstack-glance-api.service loaded active running OpenStack Image Service (code-named Glance) API server openstack-glance-registry.service loaded active running OpenStack Image Service (code-named Glance) Registry server openstack-nova-api.service loaded active running OpenStack Nova API Server openstack-nova-conductor.service loaded active running OpenStack Nova Conductor Server openstack-nova-consoleauth.service loaded active running OpenStack Nova VNC console auth Server openstack-nova-novncproxy.service loaded active running OpenStack Nova NoVNC Proxy Server openstack-nova-scheduler.service loaded active running OpenStack Nova Scheduler Server [root@openstack-cntr1 ~]# systemctl start httpd.service Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. [root@openstack-cntr1 ~]# systemctl status httpd.service ● httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/httpd.service.d └─openstack-dashboard.conf Active: failed (Result: exit-code) since Sat 2019-11-30 09:45:46 EST; 15s ago Docs: man:httpd(8) man:apachectl(8) Process: 12855 ExecStartPre=/usr/bin/python /usr/share/openstack-dashboard/manage.py collectstatic --noinput --clear -v0 (code=exited, status=1/FAILURE) Nov 30 09:45:46 openstack-cntr1 python[12855]: File "/usr/share/openstack-dashboard/openstack_dashboard/settings.py", line 376, in <module> Nov 30 09:45:46 openstack-cntr1 python[12855]: from local.local_settings import * # noqa: F403,H303 Nov 30 09:45:46 openstack-cntr1 python[12855]: File "/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py", line 399 Nov 30 09:45:46 openstack-cntr1 python[12855]: 'supported_vnic_types': ['*'], Nov 30 09:45:46 openstack-cntr1 python[12855]: ^ Nov 30 09:45:46 openstack-cntr1 python[12855]: IndentationError: unexpected indent Nov 30 09:45:46 openstack-cntr1 systemd[1]: httpd.service: control process exited, code=exited status=1 Nov 30 09:45:46 openstack-cntr1 systemd[1]: Failed to start The Apache HTTP Server. Nov 30 09:45:46 openstack-cntr1 systemd[1]: Unit httpd.service entered failed state. Nov 30 09:45:46 openstack-cntr1 systemd[1]: httpd.service failed. [root@openstack-cntr1 ~]#

3 2

[requirements][stable] Capping requirements in stable branches
by Akihiro Motoki 30 Nov '19

30 Nov '19

Hi, I have a question on version capping in requirements files in stable branches. When some newer version of dependent library does not work with my project, do we accept a patch to add version capping of the library in stable branches? For example, the horizon team received a patch to novaclient to <16 [1]. novaclient 16.0.0 was released after Train release, so there is no surprise that we don't have the version cap novaclient<16 in Train release. My understanding is that we don't usually cap versions of libraries after the release, but I am sending this mail to check our general guideline. Thanks, Akihiro Motoki (irc: amotoki) [1] https://review.opendev.org/#/c/693000/

4 6

[neutron] security group api slow at scale
by Erik Olof Gunnar Andersson 30 Nov '19

30 Nov '19

I was wondering if there has been any work since Rocky to improve the performance of CRUD operations for security groups. When you have many thousands of rules the performance of simple operations gets exponentially slower. It got a little better after we applied the patches from this bug. https://bugs.launchpad.net/neutron/+bug/1810563 But in one of our environments getting security group rule lists, even when there are only 6-8 rules in that group takes almost 60 seconds. Best Regards, Erik Olof Gunnar Andersson

1 0

[horizon][stein] issue
by Ignazio Cassano 29 Nov '19

29 Nov '19

Hello, I just installed stein on centos 7 and when I have a log of instances clicking "next" on horizon the following messages appears in httpd error log (please help me): [Fri Nov 29 10:52:47.306231 2019] [:error] [pid 27395] INFO openstack_auth.forms Login successful for user "admin" using domain "default", remote address 10.102.184.193. [Fri Nov 29 10:53:04.594482 2019] [:error] [pid 27395] ERROR django.request Internal Server Error: /dashboard/project/instances/ [Fri Nov 29 10:53:04.594503 2019] [:error] [pid 27395] Traceback (most recent call last): [Fri Nov 29 10:53:04.594507 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/django/core/handlers/exception.py", line 41, in inner [Fri Nov 29 10:53:04.594510 2019] [:error] [pid 27395] response = get_response(request) [Fri Nov 29 10:53:04.594513 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 187, in _get_response [Fri Nov 29 10:53:04.594515 2019] [:error] [pid 27395] response = self.process_exception_by_middleware(e, request) [Fri Nov 29 10:53:04.594518 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 185, in _get_response [Fri Nov 29 10:53:04.594521 2019] [:error] [pid 27395] response = wrapped_callback(request, *callback_args, **callback_kwargs) [Fri Nov 29 10:53:04.594523 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 36, in dec [Fri Nov 29 10:53:04.594526 2019] [:error] [pid 27395] return view_func(request, *args, **kwargs) [Fri Nov 29 10:53:04.594538 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 52, in dec [Fri Nov 29 10:53:04.594561 2019] [:error] [pid 27395] return view_func(request, *args, **kwargs) [Fri Nov 29 10:53:04.594563 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 36, in dec [Fri Nov 29 10:53:04.594566 2019] [:error] [pid 27395] return view_func(request, *args, **kwargs) [Fri Nov 29 10:53:04.594568 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 113, in dec [Fri Nov 29 10:53:04.594586 2019] [:error] [pid 27395] return view_func(request, *args, **kwargs) [Fri Nov 29 10:53:04.594589 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/horizon/decorators.py", line 84, in dec [Fri Nov 29 10:53:04.594591 2019] [:error] [pid 27395] return view_func(request, *args, **kwargs) [Fri Nov 29 10:53:04.594594 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 68, in view [Fri Nov 29 10:53:04.594597 2019] [:error] [pid 27395] return self.dispatch(request, *args, **kwargs) [Fri Nov 29 10:53:04.594600 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 88, in dispatch [Fri Nov 29 10:53:04.594603 2019] [:error] [pid 27395] return handler(request, *args, **kwargs) [Fri Nov 29 10:53:04.594605 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/horizon/tables/views.py", line 223, in get [Fri Nov 29 10:53:04.594608 2019] [:error] [pid 27395] handled = self.construct_tables() [Fri Nov 29 10:53:04.594611 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/horizon/tables/views.py", line 214, in construct_tables [Fri Nov 29 10:53:04.594613 2019] [:error] [pid 27395] handled = self.handle_table(table) [Fri Nov 29 10:53:04.594616 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/horizon/tables/views.py", line 123, in handle_table [Fri Nov 29 10:53:04.594638 2019] [:error] [pid 27395] File "/usr/lib/python2.7/site-packages/horizon/tables/views.py", line 252, in _get_data_dict [Fri Nov 29 10:53:04.594641 2019] [:error] [pid 27395] self._data = {self.table_class._meta.name: self.get_data()} [Fri Nov 29 10:53:04.594644 2019] [:error] [pid 27395] File "/usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/instances/views.py", line 186, in get_data [Fri Nov 29 10:53:04.594661 2019] [:error] [pid 27395] boot_volume.volume_image_metadata['image_id'] in [Fri Nov 29 10:53:04.594664 2019] [:error] [pid 27395] KeyError: 'image_id

2 3

[horizon][stein]
by Ignazio Cassano 29 Nov '19

29 Nov '19

Hello, I just installed stein on centos 7 and when I have a log of instances clicking "next" on horizon the following images appears. Please help me [image: image.png]

1 0

[zun][zun-ui][horizon] Request code review for a breaking fix
by Hongbin Lu 29 Nov '19

29 Nov '19

Hi Horizon folks, We have an issue that needs to be fixed at horizon side. Please check this bug: https://bugs.launchpad.net/zun-ui/+bug/1847889 We propose a fix on Horizon but the patch hasn't been moved forward for a while. Would I ask for a code review for the patch https://review.opendev.org/#/c/688290/ ? Without the fix, our horizon plugin couldn't work correctly. Best regards, Hongbin

2 2

[stein] [manila-ui] error
by Ignazio Cassano 29 Nov '19

29 Nov '19

Hello, I just installed openstack stein on centos. Manila works fine my command line but when I click "share" in the dashboard the following error appears: Environment: Request Method: GET Request URL: http://10.102.184.190/dashboard/project/shares/ Django Version: 1.11.20 Python Version: 2.7.5 Installed Applications: ['openstack_dashboard.dashboards.project', 'neutron_lbaas_dashboard', 'heat_dashboard', 'openstack_dashboard.dashboards.admin', 'openstack_dashboard.dashboards.identity', 'openstack_dashboard.dashboards.settings', 'dashboards', 'openstack_dashboard', 'django.contrib.contenttypes', 'django.contrib.auth', 'django.contrib.sessions', 'django.contrib.messages', 'django.contrib.staticfiles', 'django.contrib.humanize', 'django_pyscss', 'debreach', 'openstack_dashboard.django_pyscss_fix', 'compressor', 'horizon', 'openstack_auth'] Installed Middleware: ('openstack_auth.middleware.OpenstackAuthMonkeyPatchMiddleware', 'debreach.middleware.RandomCommentMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'horizon.middleware.OperationLogMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'horizon.middleware.HorizonMiddleware', 'horizon.themes.ThemeMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'openstack_dashboard.contrib.developer.profiler.middleware.ProfilerClientMiddleware', 'openstack_dashboard.contrib.developer.profiler.middleware.ProfilerMiddleware') Traceback: File "/usr/lib/python2.7/site-packages/django/core/handlers/exception.py" in inner 41. response = get_response(request) File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py" in _get_response 187. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py" in _get_response 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/site-packages/horizon/decorators.py" in dec 36. return view_func(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/horizon/decorators.py" in dec 52. return view_func(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/horizon/decorators.py" in dec 36. return view_func(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/horizon/decorators.py" in dec 113. return view_func(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/horizon/decorators.py" in dec 84. return view_func(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py" in view 68. return self.dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py" in dispatch 88. return handler(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/horizon/tables/views.py" in get 223. handled = self.construct_tables() File "/usr/lib/python2.7/site-packages/horizon/tables/views.py" in construct_tables 214. handled = self.handle_table(table) File "/usr/lib/python2.7/site-packages/horizon/tables/views.py" in handle_table 123. data = self._get_data_dict() File "/usr/lib/python2.7/site-packages/horizon/tables/views.py" in _get_data_dict 43. data.extend(func()) File "/usr/lib/python2.7/site-packages/horizon/utils/memoized.py" in wrapped 109. value = cache[key] = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/manila_ui/dashboards/project/shares/views.py" in get_shares_data 57. share_nets = manila.share_network_list(self.request) File "/usr/lib/python2.7/site-packages/manila_ui/api/manila.py" in share_network_list 280. return manilaclient(request).share_networks.list(detailed=detailed, Exception Type: AttributeError at /project/shares/ Exception Value: 'NoneType' object has no attribute 'share_networks' Anyone can help, please ? Ignazio

1 0

Re: [nova] There is no screen for UEFI instance from console
by YuChengDe 29 Nov '19

29 Nov '19

Hi Marcin Thanks~ I cloud not find uefi mode cloud image in ubuntu bionic. Instead, use the image bionic-server-cloudimg-amd64.img with metadata "hw_firmware_type: uefi" https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64… However, console shows no screen. Besides, neither creating a CentOS image with console available isn't work. GRUB_CMDLINE_LINUX = "... console=tty0 console=ttyS0,115200n8" Cloud you please provide some suggestions how to implement console input/output with uefi mode os. My appreciation~ Hi. After launch an UEFI mode instance in OpenStack, the console screen show the message “Guest has no initialized the displayed (yet) " Engage your help, many thanks Base on ubuntu cloud image, listed as below https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64… // // Please check with bionic image. // // On arm64 xenial image was unable to initialize graphics for uefi hosts. -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德产品开发部邮箱(Email): yu.chengde(a)99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net

1 0

Neutron sfc not working in openstack stein
by Brijesh 29 Nov '19

29 Nov '19

Hi I have installed openstack stein using Kolla Ansible along with neutron sfc. Everything is working fine apart from SFC. I have compared all the configuration related to sfc and it seems fine with me. I was trying to create a SFC with following flow: VM1 --> VM2 --> VM3 When i am pinging from vm1 to vm3 without SFC creation everything is working fine. But when i try to ping after SFC i am not able to ping. I cann't see packet on vm2 (using tcpdump) on any interface after sfc. I tried to see packet drop on br-int and br-tun using openflow rule but i cannot see any packet drop on that also. I have one controller and one compute, so all instances are on same host. All vm have 2 port of same network one is ingress and one egress. vm1 has port as p11 and p12 vm2 has port as p13 and p14 vm3 has port as p15 and p16 10.0.0.174 (vm3 ip) openstack server list +--------------------------------------+------+--------+---------------------------------+--------+----------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+------+--------+---------------------------------+--------+----------+ | ea663fee-c0c4-479d-8d33-42014bd633af | x3 | ACTIVE | demo-net=10.0.0.174, 10.0.0.76 | xenial | m1.small | | 11203289-e008-4a71-adee-51c69546a18c | x2 | ACTIVE | demo-net=10.0.0.187, 10.0.0.126 | xenial | m1.small | | 1699e74c-706b-42b8-b340-7f7077b062d6 | x1 | ACTIVE | demo-net=10.0.0.122, 10.0.0.42 | xenial | m1.small | +--------------------------------------+------+--------+---------------------------------+--------+----------+ openstack port list |grep p1 | 1391dea1-32bc-42d8-aafa-d66f9003a816 | p13 | fa:16:3e:0b:08:7d | ip_address='10.0.0.187', subnet_id='949b8df3-9832-42fb-86c1-0483f57d31d8' | ACTIVE | | 3f6e9791-940a-4466-b085-521a65511bbb | p16 | fa:16:3e:85:54:ef | ip_address='10.0.0.76', subnet_id='949b8df3-9832-42fb-86c1-0483f57d31d8' | ACTIVE | | 6955e1b1-4fcf-4998-8791-4a49ed298dc5 | p14 | fa:16:3e:4d:4e:31 | ip_address='10.0.0.126', subnet_id='949b8df3-9832-42fb-86c1-0483f57d31d8' | ACTIVE | | a51175db-6272-4748-a6e6-3af719a33b86 | p12 | fa:16:3e:6a:da:60 | ip_address='10.0.0.42', subnet_id='949b8df3-9832-42fb-86c1-0483f57d31d8' | ACTIVE | | dad20742-67e4-47c7-a759-8025f042df45 | p15 | fa:16:3e:96:eb:f8 | ip_address='10.0.0.174', subnet_id='949b8df3-9832-42fb-86c1-0483f57d31d8' | ACTIVE | | db8b775f-363a-4a61-88f4-5db1b42a7681 | p11 | fa:16:3e:b6:a9:0e | ip_address='10.0.0.122', subnet_id='949b8df3-9832-42fb-86c1-0483f57d31d8' | ACTIVE | openstack sfc flow classifier list +--------------------------------------+------+-----------------------------------------------------------------+ | ID | Name | Summary | +--------------------------------------+------+-----------------------------------------------------------------+ | 20a58a64-8339-493f-8418-922c756c2b91 | FC11 | protocol: any, | | | | source[port]: any[any:any], | | | | destination[port]: 10.0.0.174/32[any:any], | | | | neutron_source_port: db8b775f-363a-4a61-88f4-5db1b42a7681, | | | | neutron_destination_port: dad20742-67e4-47c7-a759-8025f042df45, | | | | l7_parameters: {} | +--------------------------------------+------+-----------------------------------------------------------------+ openstack sfc port chain list +--------------------------------------+------+-----------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+------------------------------------------------+----------+ | ID | Name | Port Pair Groups | Flow Classifiers | Chain Parameters | Chain ID | +--------------------------------------+------+-----------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+------------------------------------------------+----------+ | f342d2cc-dbfe-4832-9e7c-b22cc9629891 | PC11 | [u'080395fa-21fe-4d5b-b9c2-9f196e93ac98', u'89110fed-59cd-4ac8-ac45-8ce954fa99c0', u'd16b65a4-4a23-4b38-a937-a57a7058eee0'] | [u'20a58a64-8339-493f-8418-922c756c2b91'] | {u'symmetric': False, u'correlation': u'mpls'} | 1 | +--------------------------------------+------+-----------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+------------------------------------- openstack sfc port pair group list +--------------------------------------+-------+-------------------------------------------+---------------------------------------------------------------------------------------------+-------------+ | ID | Name | Port Pair | Port Pair Group Parameters | Tap Enabled | +--------------------------------------+-------+-------------------------------------------+---------------------------------------------------------------------------------------------+-------------+ | 080395fa-21fe-4d5b-b9c2-9f196e93ac98 | PPG11 | [u'10f9e355-3680-4dca-809f-7628bbbebd7f'] | {u'lb_fields': [], u'ppg_n_tuple_mapping': {u'ingress_n_tuple': {}, u'egress_n_tuple': {}}} | False | | 89110fed-59cd-4ac8-ac45-8ce954fa99c0 | PPG12 | [u'22af2ffa-72d1-477c-9b68-2582cca22f79'] | {u'lb_fields': [], u'ppg_n_tuple_mapping': {u'ingress_n_tuple': {}, u'egress_n_tuple': {}}} | False | | d16b65a4-4a23-4b38-a937-a57a7058eee0 | PPG13 | [u'cf8d263e-abab-499a-b82b-b290e85b2831'] | {u'lb_fields': [], u'ppg_n_tuple_mapping': {u'ingress_n_tuple': {}, u'egress_n_tuple': {}}} | False | +--------------------------------------+-------+-------------------------------------------+----------------------------------- Please help. If anyone can. Launchpad Bug #1854327. Thanks and Regards Brijesh DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

1 0

Re: [keystone][nova][barbican][neutron][cinder][tc][policy] Proposal for policy popup team⁩
by yumeng bao 29 Nov '19

29 Nov '19

>> Please nominate Yumeng Bao (yumeng_bao(a)yahoo.com) as the liaison with >> Cyborg team. She will contribute the spec. We have informed Howard of >> this. > Thanks Sundar, I have replaced Howard with Yumeng as the liaison for cyborg. > (Side note - the wiki can be edited by anyone, and I am tracking changes in it, so anyone may feel free to change their project liaison or add or remove team members and I will be notified of the change.) > Colleen Thanks Colleen for the update and the note reminder ! I will update the cyborg team progress on wiki paget later. Regards, Yumeng

1 0

[nova][api]
by Surya Seetharaman 28 Nov '19

28 Nov '19

Hello everyone, We came across this bug [1] in nova recently and wanted to know what people think is the best (relatively) way to fix this. In the past, the project id validation was added as a best effort to prevent users from being able to enter random values into the database. When this validation is used from the os flavor set/unset admin apis [2], there are chances that keystone returns a 403 which gets silently ignored by nova [3] allowing the user to enter the provided project_id/name without validation or warning or remove an existing flavor-project mapping. There were a couple of options discussed on IRC [4] to fix this behaviour out of which the practically reasonable ones are: 1) close the bug as invalid - tweak your config (we could add docs, idk if that would be found or help) to do what you need to avoid the 403 from keystone 2) change the 403 case as an error and raise it back to the compute api caller - maybe enough time has passed to not worry about backward compat with the old non-validating behavior Option 2 seems better than option 1 for most of us, however what we cannot agree upon is if this change should be accompanied by a microversion bump or not. [1] https://bugs.launchpad.net/nova/+bug/1854053 [2] https://github.com/openstack/nova/blob/fd67f69cfdaf04620f2e8a5f1fbf57370969… [3] https://github.com/openstack/nova/blob/d621914442855ce67ce0b99003f7e69e8ee5… [4] http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.… Cheers, Surya.

5 9

[Tacker] [Mistral] [Network Service] Regarding parameters to Network Service
by Nehal Bansal 28 Nov '19

28 Nov '19

Hi, Is there a way to pass parameters from Network Service Descriptor to the VNF Descriptor using a parameter file? Kindly advise as it would be of great help. Thank you. Regards, Nehal

1 0

[nova] There is no screen for UEFI instance from console display
by yu.chengde＠99cloud.net 28 Nov '19

28 Nov '19

Hi. After launch an UEFI mode instance in OpenStack, the console screen show the message “Guest has no initialized the displayed (yet) " Engage your help, many thanks Base on ubuntu cloud image, listed as below https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64… <https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64…>

2 1

[nova][neutron][cyborg] Bandwidth (and accel) providers are broken if CONF.host is set
by Eric Fried 28 Nov '19

28 Nov '19

Hi all. Sean mentioned a "downstream bug" in IRC today [1], which we discussed a little bit, but without gibi; and then Matt and I discussed it more later [2], but without gibi *or* Sean. Since I don't know if there's a bug report I can comment on, I wanted to summarize here for now so I don't forget. The Problem =========== Neutron needs to know the compute node resource provider on which to hang the child providers for QoS bandwidth. Today it assumes CONF.host is the name of that provider. That's wrong. The name of the provider is `hypervisor_hostname`, which for libvirt [3] happens to match the *default* value of CONF.host [4]. Per the bug Sean describes, if you override CONF.host, neutron won't find the compute node provider, and things break. The problem will be the same for any non-nova wishing to discover the compute node RP -- e.g. cyborg for purposes of creating child providers for accelerators. The Right Solution ================== Neutron (and any $service) should look up the compute node provider by its UUID. That's returned by the /os-hypervisors APIs after microversion 2.53, e.g. [5], but, Catch-22, you can currently only filter those results on hypervisor_hostname. So you would have to e.g. GET /os-hypervisors/detail and then walk the list looking for service.host matching CONF.host. That's way heavy for your CERNs. So the proposal moving forward is to add (in a new microversion) a ?service_host=XXX qparam to those APIs to let you filter down to just the one entry for your CONF.host. The UUID of that entry will also be the UUID of the compute node resource provider. (At that point you don't even need to ask Placement for that provider; you can just use that UUID directly in the APIs that create the child providers. Yay, you got your extra API call back.) Now, that's not backportable, and this problem exists in stable releases (at least those that support QoS bandwidth). So we should totally do it, but we also need... The Backportable Solution ========================= Neutron should use `gethostname()` rather than CONF.host to discover the compute node resource provider. I don't consider this a viable permanent solution because it is tightly coupled to knowing that hypervisor_hostname == `gethostname()`, which happens to be true for libvirt, but not necessarily for other drivers. We can get away with it for stable because we happen to know that we're only supporting QoS bandwidth via Placement for libvirt. Upgrade Concerns ================ Matt and I didn't nail down whether neutron and compute are allowed to be at different versions on a given host, or what those are allowed to be. But things should be sane if neutron (or any $service) logics like this in >=ussuri: if new_nova_microversion_available: do_the_os_hypervisors_thing() elif using_new_non_libvirt_feature: raise YouCantDoThisWithOldNova() else: do_the_gethostname_thing() Action Summary ============== If the above sounds reasonable, it would entail the following actions: - Neutron(/Cyborg?): backportable patch to s/CONF.host/socket.gethostname()/ - Nova: GET /os-hypervisors*?service_host=X in a new microversion. - Neutron/Cyborg: master-only patch to do the logic described in `Upgrade Concerns`_ (though for now without the `elif` branch). Thanks, efried [1] http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.… [2] http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.… [3] https://opendev.org/openstack/nova/src/commit/1cd5563f2dd2b218db2422397c8aa… [4] https://opendev.org/openstack/nova/src/commit/1cd5563f2dd2b218db2422397c8aa… [5] https://docs.openstack.org/api-ref/compute/?expanded=list-hypervisors-detai…

6 19

Re: [lists.openstack.org代发][nova][ptg] Support re-configure deleted_on_termination in server
by Brin Zhang(张百林) 28 Nov '19

28 Nov '19

Hi Sylvain, Matthew: https://review.opendev.org/#/c/693828/ Here is the PoC code, please review this change, thanks. Sylvain Bauza [mailto:sbauza@redhat.com] Items: [lists.openstack.org代发][nova][ptg] Support re-configure deleted_on_termination in server Spec is https://review.opendev.org/#/c/580336/ Most people seem to think this makes sense but realize there are already other ways to do this (snapshot) and therefore it's not totally necessary. The agreement in the room was to post the code up for the change, as this will help sell people on it if it's trivial enough and document the use case (i.e. are there scenarios where this would make life 10x easier?)

1 0

[kolla] kolla-ceph future
by Michał Nasiadka 28 Nov '19

28 Nov '19

Hello, Ceph deployment functionality in Kolla-Ansible has been deprecated in Train (https://review.opendev.org/#/c/669214/1) Given the fact that Ceph deployment was (and is) important functionality in Kolla-Ansible - I’d like to propose following steps: 1) Improve external Ceph functionality in Kolla-Ansible (configurable keyrings, users, improved documentation) - in progress now 2) Replace current kolla-ceph CI jobs with an equivalent using ceph-ansible (and possibly ceph orchestrator after Octopus is out around March 2020) 3) Remove kolla-ceph functionality in Ussuri release from Kolla-Ansible code base - or (if there are volunteers) extract it as a separate repository with a separate set of maintainers/core team. 4) (OPTIONAL) Find a volunteer to work on ceph-ansible/ceph-orchestrator existing deployment takeover functionality for ceph-kolla (current core team has no spare cycles to work on that) Essentially this mail is a call for volunteers for 3) - if there is somebody that is interested in picking up the code and maintaining it - please speak up. If there are none - we will start preparing for removing the code in 2020. Thank you for your understanding in this not easy decision. Kind regards, Michal Nasiadka

1 0

[olso][pbr][i18n] Using setup.cfg [files] data_files to install localization files
by info＠dantalion.nl 28 Nov '19

28 Nov '19

Hello everyone :), I was wondering what the preferred method to install localization files is. I can think of some probably solutions such as: 1: Including the locale files as part of a package for the target systems package manager (pacman, yum, apt, etc). 2: adding the locale files to the [files] directive in setup.cfg: I hope someone can answer my question. Kind regards, Corne Lukken

3 5

Re: [keystone][nova][barbican][neutron][cinder][tc][policy] Proposal for policy popup team⁩
by yumeng bao 28 Nov '19

28 Nov '19

>> Please nominate Yumeng Bao (yumeng_bao(a)yahoo.com) as the liaison with >> Cyborg team. She will contribute the spec. We have informed Howard of >> this. > Thanks Sundar, I have replaced Howard with Yumeng as the liaison for cyborg. > (Side note - the wiki can be edited by anyone, and I am tracking changes in it, so anyone may feel free to change their project liaison or add or remove team members and I will be notified of the change.) > Colleen Thanks Colleen for the update and the note reminder ! I will update the cyborg team progress on wiki paget later. Regards, Yumeng

1 0

[meta][K8s][API][Extended Maintenance][Operation Docs] Change SIG to Advisory status
by Rico Lin 28 Nov '19

28 Nov '19

Dear SIG members and chairs To follow the discussion in Meta SIG PTG room [1]. I would like to propose to change the following SIGs to Advisory status [2] to represent the SIG stays around for provide help, make sure everything stays working and provide advice when needed. - K8s SIG - API SIG - Extended Maintenance SIG - Operation Docs SIG If you think your SIG should not belong to `advisory` statue. Please advise from the following statuses: - active: SIG reaches out for discussion and event, have plans for the current cycle, host meetings or send ML out regularly. - forming: SIG still setting up. - advisory: SIG stays around for help, make sure everything stays working and provide advice when needed. - complete: SIG completes its mission. If that sounds correct, I need at least one chair from each SIG +1 on [2], so we can make sure it's what SIGs agreed on. [1] https://etherpad.openstack.org/p/PVG-meta-sig [2] https://review.opendev.org/#/c/695625/ -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

3 4

[meta-sig] Add Thierry Carrez to core reviewer
by Rico Lin 28 Nov '19

28 Nov '19

I would like to propose adding Thierry to core reviewer for governance-sigs I don't think anyone will doubt his knowledge of maintaining governance-sigs repo. He will be able to do core review on all patches. To create SIG patch, it will require both UC and TC to give their blessing. That means besides Amy's +2, we only need Thierry or mine +2 to approve the workflow. Let me know what you think if you have other thoughts, otherwise, I will add him in core think week. -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

2 2