December 2019 - openstack-discuss

[stein][manila-ui] error
by Ignazio Cassano 02 Dec '19

02 Dec '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 ?

3 7

[cinder] Anastasiya accepted for Outreachy
by Sofia Enriquez 02 Dec '19

02 Dec '19

Hi Cinder team, I'd like to announce that Anastasiya will be working with us improving the Tempest coverage this round. The internship schedule starts on Dec. 3, 2019, to March 3, 2020. Feel free to reach her on IRC *as anastzhyr* if something comes up. On the other hand, If you have any suggestions for tempest test scenarios or possible ideas, please let me know. Regards, Sofi -- L. Sofía Enriquez she/her Associate Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

6 7

"Transible" - convert your current cloud state to Ansible playbooks
by Sagi Shnaidman 02 Dec '19

02 Dec '19

Hi, all I'd like to present you a new tool I wrote recently, although it's under heavy development, but it can be already used and can be helpful in some of your DevOps/CloudOps tasks. I'd appreciate any feedback on it and any contributions of course :) Transible [1] (TRansformANSIBLE) - converts existing cloud state to ansible playbooks. It's a tool that takes your current cloud resources and represents them as Ansible playbooks. Running these playbooks you *ideally* will get no "changed" tasks and the same cloud configuration. Currently, it works with Openstack servers, security rules, security groups, images, volumes, servers, routers, networks, subnets, users, domains and projects which your cloud includes and defines their config as tasks in Ansible playbooks that are ready for deployment. By running these playbooks you actually can deploy or redeploy your current cloud. What are the possible use cases? 1. Freezing cloud config for further IaaC management If you have a ton of deployed resources and lost your tracking, better to start to manage them according to Infrastructure as Code principles. Creating a configuration of everything you have now allows you to change, delete, add things now via code. 2. Keeping current cloud configuration Sometimes it's required to have a "snapshot" of mandatory resources on the cloud and keep them the same no matter what happens in the cloud, like heavy testing for example. Running these playbooks will ensure you have all you need in the cloud in the required configuration. 3. Moving current infrastructure to another tenant, cloud, provider, whatever If you move to another provider but want to keep all you need and as it's configured right now, you can create playbooks with Transible and use them in the new cloud or provider. 4. In the future, I plan to add translation from one cloud configuration to another and it may help with releasing from vendor lock. Of course, because of various clouds' differences, it'll be limited. Can you come up with more? More details about the tool and how it can be configured for various use cases you can read in my longer articles on Medium [2] or Dev.to [3]. I'd appreciate your feedback here or in issues of Transible project. [4] Thanks [1] https://github.com/sshnaidm/transible [2] https://medium.com/@einarum/https-medium-com-einarum-transible-represents-c… [3] https://dev.to/sshnaidm/transible-represents-cloud-configuration-as-ansible… [4] https://github.com/sshnaidm/transible/issues -- Best regards Sagi Shnaidman

1 0

[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

Open Infrastructure Summit and PTG Shanghai - edge recap
by Ildiko Vancsa 02 Dec '19

02 Dec '19

Hi, I wrote up a quick summary about edge activities at the Open Infrastructure Summit and PTG in Shanghai to give a brief summary to people who were there and to catch up those who couldn’t attend this time. You can access the content here: http://lists.openstack.org/pipermail/edge-computing/2019-December/000664.ht… Please let me know if you have any questions or comments. Thanks, Ildikó (IRC: ildikov on Freenode)

1 0

[magnum][stein] error
by Ignazio Cassano 02 Dec '19

02 Dec '19

Hello, I've juste installed magnum on centos 7 stein, when magnu-api starts it does not log under /var/log/magnum but under /var/log/messages and it reports the following error: magnum-api: error: [Errno 32] Broken pipe Please , help me on this thread. Regards Ignazio

1 0

[charms] IRC meetings and the holiday season
by Frode Nordahl 02 Dec '19

02 Dec '19

Hello all, We are entering the holiday season, and as such we will stop our IRC meeting activity until we enter the next year. The next meeting will be held Monday January 13th 2020. I want to use this opportunity to say thank you to all activity and contributions to the charms project this year, and I look forward to what the next year might bring. Cheers! -- Frode Nordahl

1 0

[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

[blazar] IRC meetings cancelled this week
by Pierre Riteau 02 Dec '19

02 Dec '19

Hello, Due to travel, both Blazar IRC meetings are cancelled this week. Cheers, Pierre

1 0