- openstack-discuss - lists.openstack.org

[horizon] horizon-integration-tests job is broken
by Ivan Kolodyazhny 01 Sep '20

01 Sep '20

Hi team, Please, do not trigger recheck if horizon-integration-tests failed like [1]: ______________ TestDashboardHelp.test_dashboard_help_redirection _______________ 'NoneType' object is not iterable While I'm trying to figure out what is happening there [2], any help with troubleshooting is welcome. [1] https://51bb980dc10c72928109-9873e0e5415ff38d9f1a5cc3b1681b19.ssl.cf1.rackc… [2] https://review.opendev.org/#/c/749011 Regards, Ivan Kolodyazhny, http://blog.e0ne.info/

1 1

[ops] Restructuring OSOPS tools
by Sean McGinnis 31 Aug '20

31 Aug '20

Hello everyone, We recently expanded the scope of the Ops Docs SIG to also include any ops tooling. I think it's now time to move on to the next step of actually getting some of the old tooling in place and organized how we want it. We have several semi-abandoned repos from back when there was more work being done on ops tooling. During the great rebranding, those all were moved under the x/ namespace: https://opendev.org/x/?tab=&sort=recentupdate&q=osops Since these are now owned by an official SIG, we can move this content back under the openstack/ namespace. That should help increase visibility somewhat, and make things look a little more official. It will also allow contributors to tooling to get recognition for contributing to an import part of the OpenStack ecosystem. I do think it's can be a little more difficult to find things spread out over several repos though. For simplicity with finding tooling, as well as watching for reviews and helping with overall maintenance, I would like to move all of these under a common openstack/osops. Under that repo, we can then have a folder structure with tools/logging, tools/monitoring, etc. Then with everything in one place, we can have docs published in one place that helps find everything and easily links between tools. We can also capture some metadata about the tools, and use that to reflect their state in those docs. Please let me know if there are any objects to this plan. Otherwise, I will start cleaning things up and getting it staged in a new repo to be imported as an official repo owned by the SIG. Thanks! Sean

3 2

[TripleO][Ussuri] image prepare, cannot download containers image prepare recently
by Ruslanas Gžibovskis 31 Aug '20

31 Aug '20

Hi all, I have noticed, that recently my undercloud is not able to download images [0]. I have provided newly generated containers-prepare-parameter.yaml and outputs from container image prepare providing --verbose and later beginning of --debug (in the end) [0] were there any changes? As "openstack tripleo container image prepare default --output-env-file containers-prepare-parameter.yaml --local-push-destination" have prepared a bit different file, compared what was previously: NEW # namespace: docker.io/tripleou VS namespace: docker.io/tripleomaster # OLD [0] - http://paste.openstack.org/show/rBCNAQJBEe9y7CKyi9aG/ -- Ruslanas Gžibovskis +370 6030 7030

2 1

[neutron] Team meeting - Tuesday 01.09.2020
by Slawek Kaplonski 31 Aug '20

31 Aug '20

Hi, I will be on PTO on Tuesday and I will not be able to run our team meeting. So lets cancel it this week and see You all on meeting next week. For this week there are 3 important things from me: * please check doodle: https://doodle.com/poll/2ppmnua2nuva5nyp and put there time slots which works the best for You for the PTG in October - please do that this week as next week I need to book some slots for us, * as we are close to the Victoria-3 milestone (next week) which is also feature freeze week, please focus now on reviewin patches for BPs targeted for this cycle: https://wiki.openstack.org/wiki/Network/Meetings#Blueprints * There is new bug deputy role starting this week. Please check new schedule at https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy and let me know if it don't works for You. That's all from me for this week. See You all online :) -- Slawek Kaplonski Principal software engineer Red Hat

1 0

[tc] weekly update
by Mohammed Naser 31 Aug '20

31 Aug '20

Hi everyone, Here’s an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. We've also included a few references to some important mailing list threads that you should check out. # Patches ## Open Reviews - Move ansible-role-XXX-hsm projects to Barbican team https://review.opendev.org/748027 - Retire the devstack-plugin-zmq project https://review.opendev.org/748731 - Retire devstack-plugin-pika project https://review.opendev.org/748730 - Add openstack-ansible/os_senlin role https://review.opendev.org/748677 - Drop all exceptions for legacy validation https://review.opendev.org/745403 - Add openstack-helm-releases to openstack-helm https://review.opendev.org/748302 - Add assert:supports-standalone. https://review.opendev.org/722399 ## Project Updates - Add etcd3gw to Oslo https://review.opendev.org/747188 ## General Changes - Update and simplify comparison of working groups https://review.opendev.org/746763 - Move towards dual office hours in diff TZ https://review.opendev.org/746167 ## Abandoned Changes - Drop requirement of 1/3 positive TC votes to land https://review.opendev.org/746711 - Move towards single office hour https://review.opendev.org/745200 # Email Threads - vPTG October 2020 Signup: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016497.h… Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

Setuptools 48 and Devstack Failures
by Clark Boylan 31 Aug '20

31 Aug '20

Hello, Setuptools has made a new version 48 release. This appears to be causing problems for devstack because `pip install -e $PACKAGE_PATH` installs commands to /usr/bin and not /usr/local/bin on Ubuntu as it did in the past. `pip install $PACKAGE_PATH` continues to install to /usr/local/bin as expected. Devstack is failing because keystone-manage cannot currently be found at the specific /usr/local/bin/ path. Potential workarounds for this include not using `pip install -e` or relying on $PATH to find the commands rather than specifying rooted paths to them. I'll defer to the QA team on how they want to address this. While we can have devstack install an older setuptools version as well, generally this is not considered to be a good idea because anyone doing pip installs outside of devstack may get the newer behavior. It is actually important for us to try and keep up with setuptools changes as a result. Fungi indicated that setuptools expected this to be a bumpy upgrade. I'm not sure if they would consider `pip install -e` and `pip install` installing to different paths as a bug, and if they did which behavior is correct. It would probably be a good idea to file a bug upstream if we debug this further. Clark

5 6

[octavia] usage of SELECT .. FOR UPDATE
by Mohammed Naser 30 Aug '20

30 Aug '20

Hi everyone, We're being particularly hit hard across different deployments where Octavia has several SELECT .. FOR UPDATE queries which are causing load balancers to fail to provision properly. - spare_pools: This usually hits on rolling restarts of o-housekeeping as they all seem to try to capture a lock -- https://github.com/openstack/octavia/blob/73fbc05386b512aa1dd86a0ed6e8455cc… - quota: This hits when provisioning a lot of load balancers in parallel. For example in cases when using Heat -- https://github.com/openstack/octavia/blob/bf3d5372b9fc670ecd08339fa989c9b73… These hurt quite a lot in a busy deployment and result in a poor user experience unfortunately. We're trying to off-load Octavia to it's own database server but that is more of a "throw power at the problem" solution. I can imagine that we can probably likely look into a better/cleaner alternative that avoids this entirely? I'm happy to try and push for some of this work on our side. Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

2 1

Openstack zun ui
by mahdi abbasi 30 Aug '20

30 Aug '20

Hi, I want install zun ui, first i installed horizon with package and then install zun ui with pip and then python horizon_path/manage.py collectstatic But i receive error in httpd finaly. Error: ImportError: No module named zun_ui Please help me Best Regards Mahdi

2 4

[all] READMEs of zuul roles not rendered properly - missing content
by Martin Kopec 30 Aug '20

30 Aug '20

Hello everyone, I've noticed that READMEs of zuul roles within openstack projects are not rendered properly on opendev.org - ".. zuul:rolevar::" syntax seems to be the problem. Although it's rendered well on github.com, see f.e. [1] [2]. I wonder if there were some changes in the supported README syntax. Also the ".. zuul:rolevar::" syntax throws errors on online rst formatters I was testing on, however, it's rendered fine by md online formatters - maybe opendev.org is more rst strict in case of .rst files than github? Any ideas? [1] https://opendev.org/openstack/tempest/src/branch/master/roles/run-tempest [2] https://github.com/openstack/tempest/tree/master/roles/run-tempest Thanks, -- Martin Kopec Quality Engineer Red Hat EMEA <https://www.redhat.com> <https://red.ht/sig>

4 4

[tc][telemetry][gnocchi] The future of Gnocchi in OpenStack
by Adrian Turjak 28 Aug '20

28 Aug '20

Hey OpenStackers, We're currently in the process of discussing what to do with OpenStack's reliance on Gnocchi, and at present it is looking like we are most likely to just fork it back under a new name (currently Farfalle to stick with the pasta theme). The discussion is mostly happening here: https://review.opendev.org/#/c/744592/ But for those running Gnocchi in prod, this is likely something you may want to know about and we'd like to hear from you. A bit of history: Gnocchi started off as a new backend for Ceilometer in OpenStack, and eventually become the defacto API for telemetry samples when that was removed from Ceilometer (as backed by MongoDB). Gnocchi was eventually spun off outside of OpenStack, but still essentially remained our API for telemetry despite not being an official part of OpenStack anymore. Since then the development around it seems to have stalled, with pull requests left unreviewed, CI broken, and even the domain for the docs lapsing once. They have essentially said the project is unmaintained themselves: https://github.com/gnocchixyz/gnocchi/issues/1049 Given that OpenStack telemetry relies on it, we needed to decide what to do. We tried talking to the devs which spun it off outside of OpenStack, but they seem disinclined to interact with the OpenStack community, or move the project back to our infra/governance despite OpenStack looking like the only consumers of Gnocchi as a project. We want to find a solution, and the feeling is that they don't. So we've opted to fork it back and now the discussion is how to approach that fork. The OpenStack community doesn't want to maintain a time series database, but our telemetry API is part of it. We are putting it under non-OpenStack namespace to start, but we need to decide what the long term place for it should be. Do we want to make it an official project again? Do we keep it just as an API and drop the time series DB part for another DB? Do we build a new API back into Ceilometer and switch to a different backend like InfluxDB? We don't know yet, and we want some input from people who use the service so we can hopefully work with OpenStack telemetry as a whole and figure out what the long term picture is. If Gnocchi matters to you at all, or you use it, we want to hear from you. Cheers, Adrian Turjak

3 3

[release] Release countdown for week R-6 Aug 31 - Sept 4
by Sean McGinnis 28 Aug '20

28 Aug '20

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on September 3. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/victoria branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (Sept 10) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, Sept 10. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/victoria branches, this would be a good point for teams to review membership in their victoria-stable-maint groups. Once the stable/victoria branches are cut for a repo, the ability to approve any necessary backports into those branches for Victoria will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: September 3 (R-6 week) Client library freeze: September 10 (R-5 week) Victoria-3 milestone: September 10 (R-5 week) Cycle Highlights Due: September 10 (R-5 week) Victoria release: October 14

1 0

[all][goals] Switch legacy Zuul jobs to native - update #3
by Luigi Toscano 28 Aug '20

28 Aug '20

Hi, it's time for another status report on this goal. A lot of reviews have been merged in the past 10 days, and several projects are not on the list anymore. This is a very good news, but we still have some work to complete. Please keep pushing! Status ====== The number of the project with legacy jobs is now limited, so I'm going to explain the status in more details for each of them. The links to the patches can be found in the etherpad [3] (see below for the links). cinder ------ There is just one test left, and it is definitely tricky, because it implements a cycle of "change tempest configuration"/"run tempest"/"repeat", which is not the usual pattern. In the worst case I will "port" by adding a simple bash wrapper, but I'd like to have a clean ansible solution. designate --------- A patch for the only legacy job is under review after some forth and back, but there are some open questions. heat ------ Only one legacy job left, the heat cores are aware of it. infra ----- Only one devstack-gate job in the os-loganalyze repository, which should be probably retired. There are 2 other legacy jobs, but not devstack-gate, so less urgent. ironic ------ There has been an open review with the full port of the last legacy job, but it is failing. As it is has been failing even before the porting, the patch could be probably merged as it is. karbor ------ A patch for the only legacy job is under review, but it still has some issues. manila ------ There is only one legacy-base job (not devstack-gate), so less urgent, but there is a patch for it. monasca ------- One job in the monasca-transform repository, which is most likely due for a retirement. There are 3 legacy (non devstack-gate) jobs in other repositories. murano ------ There are two legacy jobs left. I'm not sure whether murano-apps-refstackclient-unittest is still needed. murano-dashboard-sanity-check is a bit tricky, the tests still use nose and the corresponding code in horizon has seen several changes. neutron ------- There are three types of legacy jobs: * all jobs in networking-midonet, whose retirement is under discussion, but the final decision is not clear, so a porting may be needed anyway: * two grenade jobs are being worked on; * the remaining legacy job could be maybe dropped. nova ---- The team is trying to port the two legacy job left with some refactoring, but it may require some effort yet. oslo ---- Only one legacy job left, but it is part of the soon-to-be-retired devstack-plugin-zmq repository. senlin ------ A patch for the only legacy job has been proposed and it is working, needs reviews. trove ----- The trove-grenade job should be ported, but on the other hand, trove has no grenade plugin. At this point it is unlikely to be implemented before Victoria, so maybe the job can be dropped for now. zaqar ----- A few patches have been proposed and working. One of them is failing (python-zaqarclient) but it does a bit more than a simple porting, so it may be simply changed to do exactly what the old job was doing (input needed). References ========== [1] the goal: https://governance.openstack.org/tc/goals/selected/victoria/native-zuulv3-j… [2] the up-to-date Zuul v3 porting guide: https://docs.openstack.org/project-team-guide/zuulv3.html [3] the etherpad which tracks the current status: https://etherpad.opendev.org/p/goal-victoria-native-zuulv3-migration [4] the previous reports: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016058.html http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016561.h… Ciao -- Luigi

1 0

[neutron][gate] verbose q-svc log files and e-r indexing
by melanie witt 28 Aug '20

28 Aug '20

Hi all, Recently we've noticed elastic search indexing is behind 115 hours [1] and we looked for abnormally large log files being generated in the gate. We found that the q-svc log is very large, one example being 71.6M [2]. There is a lot of Time-Cost profiling output in the log, like this: Aug 17 14:22:23.210076 ubuntu-bionic-ovh-bhs1-0019298855 neutron-server[5168]: DEBUG neutron_lib.utils.helpers [req-75719db1-4abf-4500-bb0a-6d24e82cd4fd req-d88e7052-7da9-4bc9-8b35-5730ae76dcad service neutron] Time-cost: call 48e628cc-8c3a-408d-a36f-b219524480e0 function apply_funcs start {{(pid=5554) wrapper /usr/local/lib/python3.6/dist-packages/neutron_lib/utils/helpers.py:218}} We saw that there was a recent-ish change to remove some of the profiling output [3] but it was only for the get_objects method. Looking at the total number of lines in the file vs the number of lines without apply_funcs Time-Cost output: $ wc -l screen-q-svc.txt 186387 screen-q-svc.txt $ grep -v "function apply_funcs" screen-q-svc.txt|wc -l 102593 Would it be possible to remove this profiling output from the gate log to give elastic search indexing a better chance at keeping up? Or is there something else I've missed that could be made less verbose in the logging? Thanks for your help. Cheers, -melanie [1] http://status.openstack.org/elastic-recheck [2] https://b6ba3b9af8fd7de57099-18aa39cea11f738aa67ebd6bc9fb5e4c.ssl.cf2.rackc… [3] https://review.opendev.org/741540

3 5

[all][tc][policy] Progress report of consistent and secure default policies pop-up team
by Ghanshyam Mann 28 Aug '20

28 Aug '20

Hello Everyone, This is a regular update on progress in 'Consistent and Secure Default Policies Popup Team'. We will try to make it a monthly report form now onwards. Progress so far: ============ * Popup team meet twice in a month and discuss and work on progress and pre-work to do. - https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… * Pre-work to provide a smooth migration path to the new policy <here we will add any pre-work we need to do before more project start moving towards new policy> ** Migrate Default Policy Format from JSON to YAML - This involves oslo side + each project side works. - oslo side work to provide tool and utils method are merged (one patch is in gate). - The new tool 'oslopolicy-convert-json-to-yaml' is available now to convert your existing JSON formatted policy file to YAML formatted in a backward-compatible way. - I have started to do it in Nova (need to update the patch though) to give example work for other projects: https://review.opendev.org/#/c/748059/ - all work is tracked here: https://review.opendev.org/#/q/topic:bp/policy-json-to-yaml+(status:open+OR… ** Improving documentation about target resources (oslo.policy) - https://bugs.launchpad.net/oslo.policy/+bug/1886857 - raildo pushed the patch which is under review: https://review.opendev.org/#/c/743318/ * Team Progress: (list of a team interested or have volunteer to work) ** Keystone (COMPLETED; use as a reference) ** Nova (COMPLETED; use as a reference) - All APIs except deprecated APIs were done in the Ussuri cycle and deprecated APIs also done now. ** Cyborg (in-progress) - Spec is merged, code under review. ** Barbican (not started) ** Neutron (not started) ** Cinder (not started) ** Manila (not started) Why This Is Important ================= (I have copied it from Colleen email which is nicely written) Separating system, domain, and project-scope APIs and providing meaningful default roles is critical to facilitating secure cloud deployments and to fulfilling OpenStack's vision as a fully self-service infrastructure provider[1]. Until all projects have completed this policy migration, the "reader" role that exists in keystone is dangerously misleading, and the `[oslo_policy]/enforce_scope` option has limited usefulness as long as projects lack uniformity in how an administrator can use scoped APIs. How You Can Help ================ Contributor: - You can help by starting the work in your (or any other you would like to help) project and attend popup team meeting in case of any question, review request etc. Cloud operator: - Please help review the proposed policy rule changes to sanity-check the new scope and role defaults. - Migrate your JSON formatted policy file to YAML JSON formatted file can be problematic in the various way as described here[2]. You can use 'oslopolicy-convert-json-to-yaml' tool [3] to convert your existing JSON formatted policy file to YAML formatted in a backward-compatible way. [1] https://governance.openstack.org/tc/reference/technical-vision.html#self-se… [2] https://specs.openstack.org/openstack/oslo-specs/specs/victoria/policy-json… [3] https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-t… -gmann & raildo

1 0

Horizon installation problem
by mahdi abbasi 28 Aug '20

28 Aug '20

Hi openstack development team, When i want install horizon with pip3 i recieve and error: Could not satisfy constraints for horizon: installation from path or url cannot be constrained to a version. Please help me Best regards Mahdi

2 1

[Kolla] re-create container
by Tony Liu 28 Aug '20

28 Aug '20

Hi, Is Kolla container created by playbook only or there is something like docker-compose to re-create container in case it's deleted after initial deployment? Thanks! Tony

2 1

[tc] office hours update
by Mohammed Naser 28 Aug '20

28 Aug '20

Hi everyone, In order to be able to have more folks available during office hours, we have the following newly available times once this patch lands: https://review.opendev.org/746167 * 01:00 UTC on Tuesdays: http://www.timeanddate.com/worldclock/fixedtime.html?hour=01&min=00&sec=0 * 15:00 UTC on Wednesdays: http://www.timeanddate.com/worldclock/fixedtime.html?hour=15&min=00&sec=0 We look forward to seeing our community present at those office hours with anything they have. Thank you, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[kuryr] vPTG October 2020
by Michał Dulko 28 Aug '20

28 Aug '20

Hello all, There's a vPTG October 2020 project signup process going on and I'd like to ask if you want me to reserve an hour or two there for a sync up on the priorities and plans of various parts of the team. Thanks, Michał

1 1

[Heat] Reg Creation of resource based on another resource attribute value
by NANTHINI A A 27 Aug '20

27 Aug '20

Hi Team , I want to create the openstack subnet resource based on the openstack network resource's attribute STATUS value. i.e Create neutron subnet only when the neutron network status is ACTIVE . I can see currently the support of get_Attr function is not there in conditions section .Also the depends_on function accepts input as resource ids only .I cant pass a condition there . Is there any other way to implement the same .Please suggest . Thanks, A.Nanthini

2 1

per user quota not applign in openstack train
by its-openstack＠zohocorp.com 27 Aug '20

27 Aug '20

Dear openstack, We are facing a peculiar issue with regards to users quota of resources. e.g: +------------------------------------------------------------------------------------------------------+ | project | user | instance quota | no: of instance created | | -----------|------------|-----------------------------------|------------------------------------------| | tes | - | 10 | - | | test | user1 | 2 | 2 | | test | user2 | 2 | error "quota over" | | test | user3 | 3 | only 1 instance allowed | | test | user4 | no user quota defined | able to create 10 instance| +-------------------------------------------------------------------------------------------------------+ As you see from mentioned table. when user1,user2, has instance quota of 2 and when user1 has created 2 instance, user2 unable to create instance. but user3 able to create only 1 more instance, user 4 has no quota applied so project quota 10 will be applied and he can create 10 instance. the quota is applied to each user but not tracked for each user, so this defeats the purpose of per user quota. Please help us with resolving this issue. Regards, sysadmin team

3 2

[kolla] Focal upgrade
by Mark Goddard 27 Aug '20

27 Aug '20

Hi, For the Victoria release we will be moving our Ubuntu support from Bionic 18.04 to the Focal 20.04 LTS release. This applies to both the base container image and host OS. We would like to request feedback from any Ubuntu users about how they typically deal with a distro upgrade like this. I would assume that the following workflow would be used: 1. start with a Ussuri release on Bionic 2. distro upgrade to Focal 3. OpenStack upgrade to Victoria However, that would imply that it would not be possible to make any more changes to the Ussuri deploy after the Focal upgrade, since Kolla Ansible Ussuri release does not support Focal (it is blocked by prechecks). An alternative approach is: 1. start with a Ussuri release on Bionic 2. OpenStack upgrade to Victoria 3. distro upgrade to Focal This implies that Victoria must support both Bionic and Focal as a host OS, which it currently does. This flow matches more closely what we are currently testing in CI (steps 1 and 2 only). In both cases, Victoria container images are based on Focal. Feedback on this would be appreciated. Thanks, Mark

2 1

Do you want to render ANSI in Zuul console?
by Sorin Sbarnea 27 Aug '20

27 Aug '20

At this moment Zuul web interfaces displays output of commands as raw, so any ANSI terminal output will display ugly artifacts. I tried enabling ANSI about half a year ago but even after providing two different implementations, I was not able to popularize it enough. As this is a UX related feature, I think would like more appropriate to ask for feedback from openstack-discuss, likely the biggest consumer of zuul web interface. Please comment/+/- on review below even if you are not a zuul core. At least it should show if this is a desired feature to have or not: https://review.opendev.org/#/c/739444/ ✅ This review also includes a screenshot that shows how the rendering looks (an alternative for using the sitepreview) Thanks Sorin Sbarnea

3 5

[neutron] Drivers meeting 28.08.2020 cancelled
by Slawek Kaplonski 27 Aug '20

27 Aug '20

Hi, There is no any new RFEs in the agenda for tomorrow's drivers team meeting so lets cancel it and see You all next week. Have a great weekend. -- Slawek Kaplonski Principal software engineer Red Hat

1 0

[tc] Monthly meeting
by Mohammed Naser 27 Aug '20

27 Aug '20

Hi everyone, Our monthly TC meeting is scheduled for next Thursday, September 3rd, at 1400 UTC. If you would like to add topics for discussion, please go to https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and fill out your suggestions by Wednesday, September 2nd, at 1900 UTC. Thank you, Regards, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[all] Wallaby Release Schedule
by Sean McGinnis 27 Aug '20

27 Aug '20

Hey everyone, We have officially published the schedule for the Wallaby development cycle. That can now be found on the release.openstack.org site here: https://releases.openstack.org/wallaby/schedule.html PTLs, feel free to propose any updates if there are important project-specific deadlines you would like to include on the schedule. Just ping me if you need any examples of how that is done. Thanks! Sean

2 2

[neutron][ovn] OVN Performance
by Apsey, Christopher 27 Aug '20

27 Aug '20

All, I know that OVN is going to become the default neutron backend at some point and displace linuxbridge as the default configuration option in the docs, but we have noticed a pretty significant performance disparity between OVN and linuxbridge on identical hardware over the past year or so in a few different environments[1]. I know that example is unscientific, but similar results have been borne out in many different scenarios from what we have observed. There are three main problems from what we see: 1. OVN does not handle large concurrent requests as well as linuxbridge. Additionally, linuxbridge concurrent capacity grows (not linearly, but grows nonetheless) by adding additional neutron API endpoints and RPC agents. OVN does not really horizontally scale by adding additional API endpoints, from what we have observed. 2. OVN gets significantly slower as load on the system grows. We have observed a soft cap of about 2000-2500 instances in a given deployment before ovn-backed neutron stops responding altogether to nova requests (even for booting a single instance). We have observed linuxbridge get to 5000+ instances before it starts to struggle on the same hardware (and we think that linuxbridge can go further with improved provider network design in that particular case). 3. Once the southbound database process hits 100% CPU usage on the leader in the ovn cluster, it’s game over (probably causes 1+2) It's entirely possible that we just don’t understand OVN well enough to tune it [2][3][4], but then the question becomes how do we get that tuning knowledge into the docs so people don’t scratch their heads when their cool new OVN deployment scales 40% as well as their ancient linuxbridge-based one? If it is ‘known’ that OVN has some scaling challenges, is there a plan to fix it, and what is the best way to contribute to doing so? We have observed similar results on Ubuntu 18.04/20.04 and CentOS 7/8 on Stein, Train, and Ussuri. [1] https://pastebin.com/kyyURTJm [2] https://github.com/GeorgiaCyber/kinetic/tree/master/formulas/ovsdb [3] https://github.com/GeorgiaCyber/kinetic/tree/master/formulas/neutron [4] https://github.com/GeorgiaCyber/kinetic/tree/master/formulas/compute Chris Apsey GEORGIA CYBER CENTER

3 5

Re: [cyborg] Temporary treatment plan for the 3rd-party driver
by yumeng bao 27 Aug '20

27 Aug '20

Brin, thanks for bringing this up! > Hi all： > This release we want to introduce some 3rd party drivers (e.g. Intel QAT, Inspur FPGA, and Inspur SSD etc.) in Cyborg, and we discussed the handling of 3rd-party driver CI in Cyborg IRC meeting [1]. > Due to the lack of CI test environment supported by hardware, we reached a temporary solution in two ways, as follows: > 1. Provide a CI environment and provide a tempest test for Cyborg, this method is recommended; > 2. If there is no CI environment, please provide the test results of this driver in the master branch or in the designated branch, which should be as complete as possible, sent to the Cyborg team, or pasted in the implementation of the commit. Providing test result can be our option. The test result can be part of the driver documentation[0] as this is public to users. And from my understanding, the test result should work as the role of tempest case and clarify at least: necessary configuration,test operations and test results. [0] https://docs.openstack.org/cyborg/latest/reference/support-matrix.html#driv… > [1] http://eavesdrop.openstack.org/meetings/openstack_cyborg/2020/openstack_cyb… Regards， Yumeng

4 4

DB Prune
by Szabo, Istvan (Agoda) 27 Aug '20

27 Aug '20

Hi, We have a cluster where the user continuously spawn and delete servers which makes the db even in compressed state 1.1GB. I'm sure it has a huge amount of trash because this is a cicd environment and the prod just uses 75MB. How is it possible to cleanup the db on a safe way, what should be the steps? Best regards, Istvan ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

3 4

[ironic] next Victoria meetup
by Riccardo Pittau 27 Aug '20

27 Aug '20

Hello everyone! The time for the next Ironic virtual meetup is close! It will be an opportunity to review what has been done in the last months, exchange ideas and plan for the time before the upcoming victoria release, with an eye towards the future. We're aiming to have the virtual meetup the first week of September (Monday August 31 - Friday September 4) and split it in two days, with one two-hours slot per day. Please vote for your best time slots here: https://doodle.com/poll/pi4x3kuxamf4nnpu We're planning to leave the vote open at least for the entire week until Friday August 21, so to have enough time to announce the final slots and planning early next week. Thanks! A si biri Riccardo

1 2

Re: [openstack-community] Error add member to pool ( OCTAVIA ) when using SSL to verify
by Amy Marrich 26 Aug '20

26 Aug '20

Adding the OpenStack discuss list. Amy (spotz) > On Aug 24, 2020, at 11:14 PM, Vinh Nguyen Duc <vinhducnguyen1708(a)gmail.com> wrote: > > > Dear Openstack community, > > My name is Duc Vinh, I am newer in Openstack > I am deploy Openstack Ussuri on Centos8 , I am using three nodes controller with High Availability topology and using HAproxy to verify cert for connect HTTPS, > I have trouble with project Octavia, I cannot add member in a pool after created Loadbalancer, listener, pool ( everything is fine). > Here is my log and configuration file: > > LOGS: > > 2020-08-25 10:55:42.872 226250 DEBUG octavia.network.drivers.neutron.base [req-57c5b37c-e50f-4d50-b535-b0a3d19db1d5 - 8259463ce052437396afa845933afe4b - default default] Neutron extension security-group found enabled _check_extension_enabled /usr/lib/python3.6/site-packages/octavia/network/drivers/neutron/base.py:66 > 2020-08-25 10:55:42.892 226250 DEBUG octavia.network.drivers.neutron.base [req-57c5b37c-e50f-4d50-b535-b0a3d19db1d5 - 8259463ce052437396afa845933afe4b - default default] Neutron extension dns-integration is not enabled _check_extension_enabled /usr/lib/python3.6/site-packages/octavia/network/drivers/neutron/base.py:70 > 2020-08-25 10:55:42.911 226250 DEBUG octavia.network.drivers.neutron.base [req-57c5b37c-e50f-4d50-b535-b0a3d19db1d5 - 8259463ce052437396afa845933afe4b - default default] Neutron extension qos found enabled _check_extension_enabled /usr/lib/python3.6/site-packages/octavia/network/drivers/neutron/base.py:66 > 2020-08-25 10:55:42.933 226250 DEBUG octavia.network.drivers.neutron.base [req-57c5b37c-e50f-4d50-b535-b0a3d19db1d5 - 8259463ce052437396afa845933afe4b - default default] Neutron extension allowed-address-pairs found enabled _check_extension_enabled /usr/lib/python3.6/site-packages/octavia/network/drivers/neutron/base.py:66 > 2020-08-25 10:55:43.068 226250 WARNING keystoneauth.identity.generic.base [req-57c5b37c-e50f-4d50-b535-b0a3d19db1d5 - 8259463ce052437396afa845933afe4b - default default] Failed to discover available identity versions when contacting https://192.168.10.150:5000. Attempting to parse version from URL.: keystoneauth1.exceptions.connection.SSLError: SSL exception connecting to https://192.168.10.150:5000: HTTPSConnectionPool(host='192.168.10.150', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897)'),)) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base [req-57c5b37c-e50f-4d50-b535-b0a3d19db1d5 - 8259463ce052437396afa845933afe4b - default default] Error retrieving subnet (subnet id: 035f3183-f469-415f-b536-b4a81364e814.: keystoneauth1.exceptions.discovery.DiscoveryFailure: Could not find versioned identity endpoints when attempting to authenticate. Please check that your auth_url is correct. SSL exception connecting to https://192.168.10.150:5000: HTTPSConnectionPool(host='192.168.10.150', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897)'),)) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base Traceback (most recent call last): > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 600, in urlopen > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base chunked=chunked) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 343, in _make_request > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base self._validate_conn(conn) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 839, in _validate_conn > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base conn.connect() > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 344, in connect > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base ssl_context=context) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/urllib3/util/ssl_.py", line 367, in ssl_wrap_socket > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base return context.wrap_socket(sock) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib64/python3.6/ssl.py", line 365, in wrap_socket > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base _context=self, _session=session) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib64/python3.6/ssl.py", line 776, in __init__ > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base self.do_handshake() > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib64/python3.6/ssl.py", line 1036, in do_handshake > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base self._sslobj.do_handshake() > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib64/python3.6/ssl.py", line 648, in do_handshake > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base self._sslobj.do_handshake() > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base During handling of the above exception, another exception occurred: > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base Traceback (most recent call last): > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/requests/adapters.py", line 449, in send > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base timeout=timeout > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 638, in urlopen > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base _stacktrace=sys.exc_info()[2]) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/urllib3/util/retry.py", line 399, in increment > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base raise MaxRetryError(_pool, url, error or ResponseError(cause)) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='192.168.10.150', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897)'),)) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base During handling of the above exception, another exception occurred: > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base Traceback (most recent call last): > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/session.py", line 1004, in _send_request > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base resp = self.session.request(method, url, **kwargs) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/requests/sessions.py", line 533, in request > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base resp = self.send(prep, **send_kwargs) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/requests/sessions.py", line 646, in send > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base r = adapter.send(request, **kwargs) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/requests/adapters.py", line 514, in send > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base raise SSLError(e, request=request) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base requests.exceptions.SSLError: HTTPSConnectionPool(host='192.168.10.150', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897)'),)) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base During handling of the above exception, another exception occurred: > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base Traceback (most recent call last): > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/identity/generic/base.py", line 138, in _do_create_plugin > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base authenticated=False) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/identity/base.py", line 610, in get_discovery > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base authenticated=authenticated) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/discover.py", line 1452, in get_discovery > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base disc = Discover(session, url, authenticated=authenticated) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/discover.py", line 536, in __init__ > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base authenticated=authenticated) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/discover.py", line 102, in get_version_data > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base resp = session.get(url, headers=headers, authenticated=authenticated) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/session.py", line 1123, in get > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base return self.request(url, 'GET', **kwargs) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/session.py", line 913, in request > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base resp = send(**kwargs) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/session.py", line 1008, in _send_request > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base raise exceptions.SSLError(msg) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base keystoneauth1.exceptions.connection.SSLError: SSL exception connecting to https://192.168.10.150:5000: HTTPSConnectionPool(host='192.168.10.150', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897)'),)) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base During handling of the above exception, another exception occurred: > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base Traceback (most recent call last): > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/octavia/network/drivers/neutron/base.py", line 193, in _get_resource > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base resource_type)(resource_id) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/neutronclient/v2_0/client.py", line 869, in show_subnet > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base return self.get(self.subnet_path % (subnet), params=_params) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/neutronclient/v2_0/client.py", line 354, in get > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base headers=headers, params=params) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/neutronclient/v2_0/client.py", line 331, in retry_request > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base headers=headers, params=params) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/neutronclient/v2_0/client.py", line 282, in do_request > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base headers=headers) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/neutronclient/client.py", line 339, in do_request > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base self._check_uri_length(url) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/neutronclient/client.py", line 332, in _check_uri_length > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base uri_len = len(self.endpoint_url) + len(url) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/neutronclient/client.py", line 346, in endpoint_url > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base return self.get_endpoint() > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/adapter.py", line 282, in get_endpoint > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base return self.session.get_endpoint(auth or self.auth, **kwargs) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/session.py", line 1225, in get_endpoint > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base return auth.get_endpoint(self, **kwargs) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/identity/base.py", line 380, in get_endpoint > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base allow_version_hack=allow_version_hack, **kwargs) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/identity/base.py", line 271, in get_endpoint_data > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base service_catalog = self.get_access(session).service_catalog > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/identity/base.py", line 134, in get_access > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base self.auth_ref = self.get_auth_ref(session) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/identity/generic/base.py", line 206, in get_auth_ref > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base self._plugin = self._do_create_plugin(session) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base File "/usr/lib/python3.6/site-packages/keystoneauth1/identity/generic/base.py", line 161, in _do_create_plugin > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base 'auth_url is correct. %s' % e) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base keystoneauth1.exceptions.discovery.DiscoveryFailure: Could not find versioned identity endpoints when attempting to authenticate. Please check that your auth_url is correct. SSL exception connecting to https://192.168.10.150:5000: HTTPSConnectionPool(host='192.168.10.150', port=5000): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897)'),)) > 2020-08-25 10:55:43.070 226250 ERROR octavia.network.drivers.neutron.base > 2020-08-25 10:55:43.074 226250 DEBUG wsme.api [req-57c5b37c-e50f-4d50-b535-b0a3d19db1d5 - 8259463ce052437396afa845933afe4b - default default] Client-side error: Subnet 035f3183-f469-415f-b536-b4a81364e814 not found. format_exception /usr/lib/python3.6/site-packages/wsme/api.py:222 > 2020-08-25 10:55:43.076 226250 DEBUG octavia.common.keystone [req-57c5b37c-e50f-4d50-b535-b0a3d19db1d5 - 8259463ce052437396afa845933afe4b - default default] Request path is / and it does not require keystone authentication process_request /usr/lib/python3.6/site-packages/octavia/common/keystone.py:77 > 2020-08-25 10:55:43.080 226250 DEBUG octavia.common.keystone [req-5091d326-0cb4-4ae1-bf4b-9ef6b9313dca - - - - -] Request path is / and it does not require keystone authentication process_request /usr/lib/python3.6/site-packages/octavia/common/keystone.py:77 > > Configuration: > [root@controller01 ~]# cat /etc/octavia/octavia.conf > [DEFAULT] > > log_dir = /var/log/octavia > debug = True > transport_url = rabbit://openstack:4ychZAT5VrWlk6KFfgAmpXvGdzfdV8hEpIgOLhyF@192.168.10.178:5672,openstack:4ychZAT5VrWlk6KFfgAmpXvGdzfdV8hEpIgOLhyF@192.168.10.179:5672,openstack:4ychZAT5VrWlk6KFfgAmpXvGdzfdV8hEpIgOLhyF@192.168.10.28:5672 > > [api_settings] > api_base_uri = https://192.168.10.150:9876 > bind_host = 192.168.10.178 > bind_port = 9876 > auth_strategy = keystone > healthcheck_enabled = True > allow_tls_terminated_listeners = True > > [database] > connection = mysql+pymysql://octavia:FUkbii8AY4G6H9LxbJ2RRlOzHN61X8PI8FrMcuXQ@192.168.10.150/octavia > max_retries = -1 > > [health_manager] > bind_port = 5555 > bind_ip = 192.168.10.178 > controller_ip_port_list = 192.168.10.178:5555, 192.168.10.179:5555, 192.168.10.28:5555 > heartbeat_key = insecure > > [keystone_authtoken] > service_token_roles_required = True > www_authenticate_uri = https://192.168.10.150:5000 > auth_url = https://192.168.10.150:5000 > region_name = Hanoi > memcached_servers = 192.168.10.178:11211,192.168.10.179:11211,192.168.10.28:11211 > auth_type = password > project_domain_name = Default > user_domain_name = Default > project_name = service > username = octavia > password = esGn3rN3iJOAD2HXmqznFPI9oAY2wQNDWYwqJaCH > cafile = /etc/ssl/private/haproxy.pem > insecure = false > > > [certificates] > cert_generator = local_cert_generator > #server_certs_key_passphrase = insecure-key-do-not-use-this-key > ca_private_key_passphrase = esGn3rN3iJOAD2HXmqznFPI9oAY2wQNDWYwqJaCH > ca_private_key = /etc/octavia/certs/server_ca.key.pem > ca_certificate = /etc/octavia/certs/server_ca.cert.pem > region_name = Hanoi > ca_certificates_file = /etc/ssl/private/haproxy.pem > endpoint_type = internal > > [networking] > #allow_vip_network_id = True > #allow_vip_subnet_id = True > #allow_vip_port_id = True > > [haproxy_amphora] > #bind_port = 9443 > server_ca = /etc/octavia/certs/server_ca.cert.pem > client_cert = /etc/octavia/certs/client.cert-and-key.pem > base_path = /var/lib/octavia > base_cert_dir = /var/lib/octavia/certs > connection_max_retries = 1500 > connection_retry_interval = 1 > > [controller_worker] > amp_image_tag = amphora > amp_ssh_key_name = octavia > amp_secgroup_list = 80f44b73-dc9f-48aa-a0b8-8b78e5c6585c > amp_boot_network_list = 04425cb2-5963-48f5-a229-b89b7c6036bd > amp_flavor_id = 200 > network_driver = allowed_address_pairs_driver > compute_driver = compute_nova_driver > amphora_driver = amphora_haproxy_rest_driver > client_ca = /etc/octavia/certs/client_ca.cert.pem > loadbalancer_topology = SINGLE > amp_active_retries = 9999 > > [task_flow] > [oslo_messaging] > topic = octavia_prov > rpc_thread_pool_size = 2 > > [house_keeping] > [amphora_agent] > [keepalived_vrrp] > > [service_auth] > auth_url = https://192.168.10.150:5000 > auth_type = password > project_domain_name = default > user_domain_name = default > project_name = admin > username = admin > password = F35sXAYW5qDlMGfQbhmexIx12DqrQdpw6ixAseTd > cafile = /etc/ssl/private/haproxy.pem > region_name = Hanoi > memcached_servers = 192.168.10.178:11211,192.168.10.179:11211,192.168.10.28:11211 > #insecure = true > > > [glance] > ca_certificates_file = /etc/ssl/private/haproxy.pem > region_name = Hanoi > endpoint_type = internal > insecure = false > > [neutron] > ca_certificates_file = /etc/ssl/private/haproxy.pem > region_name = Hanoi > endpoint_type = internal > insecure = false > > [cinder] > ca_certificates_file = /etc/ssl/private/haproxy.pem > region_name = Hanoi > endpoint_type = internal > insecure = false > > [nova] > ca_certificates_file = /etc/ssl/private/haproxy.pem > region_name = Hanoi > endpoint_type = internal > insecure = false > > [oslo_policy] > #policy_file = /etc/octavia/policy.json > > [oslo_messaging_notifications] > transport_url = rabbit://openstack:4ychZAT5VrWlk6KFfgAmpXvGdzfdV8hEpIgOLhyF@192.168.10.178:5672,openstack:4ychZAT5VrWlk6KFfgAmpXvGdzfdV8hEpIgOLhyF@192.168.10.179:5672,openstack:4ychZAT5VrWlk6KFfgAmpXvGdzfdV8hEpIgOLhyF@192.168.10.28:5672 > > _______________________________________________ > Community mailing list > Community(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/community

3 2

[Diversity] Diversity & Inclusion WG Meeting 8/31 - Removing Divisive Language
by Amy Marrich 26 Aug '20

26 Aug '20

The Diversity & Inclusion WG has taken on the task from this week's Board meeting to assist with the development of the OSF's stance on the removal of Divisive Language within the OSF projects. The WG invites members of all OSF projects to participate in this effort and to join us at our next meeting Monday, August 31, at 17:00 UTC which will be held at https://meetpad.opendev.org/osf-diversity-and-inclusion. <https://meetpad.opendev.org/osf-diversity-and-inclusion> The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. If you have any questions please let me and the team know here, on #openstack-diversity on IRC, or you can email me directly. Thanks, Amy Marrich (spotz)

1 0

openstack-discuss
by ARUNKUMAR PALANISAMY 26 Aug '20

26 Aug '20

Hello Team, My name is ARUNKUMAR PALANISAMY, As part of our project requirement, we are evaluating trove components and need your support for experimental datastore Image for testing cluster. (Redis, Cassandra, MongoDB, Couchbase) 1.) We are running devstack enviorment with Victoria Openstack release and with this image (trove-master-guest-ubuntu-bionic-dev.qcow2<https://tarballs.opendev.org/openstack/trove/images/trove-master-guest-ubun…>), we are able to deploy mysql instance and and getting below error while creating mongoDB instances. "ModuleNotFoundError: No module named 'trove.guestagent.datastore.experimental' " 2.) While tried creating mongoDB image with diskimage-builder<https://opendev.org/openstack/diskimage-builder> tool, but we are getting "Block device " element error. Regards, Arunkumar Palanisamy =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

1 0

Re: [tc][masakari] Project aliveness (was: [masakari] Meetings)
by Jegor van Opdorp 26 Aug '20

26 Aug '20

We're also using masakari and willing to help maintain it! ________________________________ From: Mark Goddard <mark(a)stackhpc.com> Sent: Monday, August 17, 2020 12:12 PM To: Jegor van Opdorp <jegor(a)greenedge.cloud> Subject: Fwd: [tc][masakari] Project aliveness (was: [masakari] Meetings) ---------- Forwarded message --------- From: Radosław Piliszek <radoslaw.piliszek(a)gmail.com> Date: Fri, 14 Aug 2020 at 08:53 Subject: [tc][masakari] Project aliveness (was: [masakari] Meetings) To: openstack-discuss <openstack-discuss(a)lists.openstack.org> Cc: Sampath Priyankara (samP) <sam47priya(a)gmail.com>, Tushar Patil (tpatil) <tushar.vitthal.patil(a)gmail.com> Hi, it's been a month since I wrote the original (quoted) email, so I retry it with CC to the PTL and a recently (this year) active core. I see there have been no meetings and neither Masakari IRC channel nor review queues have been getting much attention during that time period. I am, therefore, offering my help to maintain the project. Regarding the original topic, I would opt for running Masakari meetings during the time I proposed so that interested parties could join and I know there is at least some interest based on recent IRC activity (i.e. there exist people who want to use and discuss Masakari - apart from me that is :-) ). -yoctozepto On Mon, Jul 13, 2020 at 9:53 PM Radosław Piliszek <radoslaw.piliszek(a)gmail.com> wrote: > > Hello Fellow cloud-HA-seekers, > > I wanted to attend Masakari meetings but I found the current schedule unfit. > Is there a chance to change the schedule? The day is fine but a shift > by +3 hours would be nice. > > Anyhow, I wanted to discuss [1]. I've already proposed a change > implementing it and looking forward to positive reviews. :-) That > said, please reply on the change directly, or mail me or catch me on > IRC, whichever option sounds best to you. > > [1] https://blueprints.launchpad.net/masakari/+spec/customisable-ha-enabled-ins… > > -yoctozepto

6 13

[kolla] Kayobe config walkthrough docs call
by Mark Goddard 26 Aug '20

26 Aug '20

Hi, In today's kolla IRC meeting we proposed to have a meeting to discuss the long awaited Kayobe configuration walkthrough documentation. We'll try to agree on an approach, and get people signed up for writing parts or all of it. The proposed meeting time is tomorrow (27th August) at 15:00 - 16:00 UTC, the same slot as the Kolla Klub (which is still on summer break). Please reply if you would like to attend but cannot make this slot. Google meet link: https://meet.google.com/xfg-ieza-qrz Regards, Mark

1 0

[monasca] Retire monasca-analytics repository
by Witek Bedyk 26 Aug '20

26 Aug '20

Hello, this message is to announce the retirement of openstack/monasca-analytics repository. The project will not accept any new patches. It will follow the process described in Project Team Guide [1]. Please reply to this message until Sept. 7 if you would like to take over the development and maintenance of this repository. Thanks Witek [1] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-re…

1 0

[releases] Dropping my releases core/release-manager hat
by Jean-Philippe Evrard 26 Aug '20

26 Aug '20

Hello folks, I am sad to announce that, while super motivated to keep helping the team, I cannot reliably and consistantly do my duties of core in the releases team, due to my current duties at work. It's been a while I haven't significantly helped the release team, and the team deserve all the transparency and clarity it can get about its contributors. It's time for me to step down. It's been a pleasure to help the team while it lasted. If you are looking for a team to get involved in OpenStack, make no mistake, the release team is awesome. Thank you everyone in the team, you were all amazing and so welcoming :) Regards, Jean-Philippe Evrard (evrardjp)

3 2

nova config vCenter and creating instance failed
by Ankele zhang 26 Aug '20

26 Aug '20

Hi all I have config vCenter in my nova.conf, cinder.conf and glance-api.conf. First of all, I can create VM inner vSphere successfully and I can create VM inner OpenStack without vCenter configuration successfully. Now I config vCenter driver in nova, cinder and glance. Creating images and volumes successfully, but when I create VM instance, I got the error message "Build of instance e3e8e049-98fc-486e-95c7-e17ec0e22e59 aborted: 主机配置过程中出错。" , in english is "Build of instance e3e8e049-98fc-486e-95c7-e17ec0e22e59 aborted: an error occurred during host configuration". And error in vCSA client is just "主机配置过程中出错" while creating vm. Environment: OpenStack(Rocky), vSphere(6.7), storage(iSCSI),network(OVS vlan),vCenter is VMware-VIM-all-6.7.0-16046470.iso installed in windows2012 server. I don't know where did my configuration error in OpenStack or something error in my vSphere. nova.conf: [default] ... compute_driver = vmwareapi.VMwareVCDriver [vmware] host_ip = 192.168.3.115 host_username = administrator(a)vsphere.local host_password = Zl@123456 cluster_name = mycluster datastore_regex = Datastore_iscsi insecure = True vlan_interface = vmnic0 integration_bridge = br-int api_retry_count = 10 cinder.conf: [DEFAULT] enabled_backends = vmware default_volume_type = vmware [vmware] volume_driver = cinder.volume.drivers.vmware.vmdk.VMwareVcVmdkDriver vmware_host_ip=192.168.3.115 vmware_host_password=Zl@123456 vmware_host_username=administrator(a)vsphere.local vmware_wsdl_location=https://192.168.3.115/sdk/vimService.wsdl vmware_volume_folder= openstack_volume vmware_datastore_regex = Datastore_iscsi vmware_insecure = True vmware_host_version = 6.7 glance-api.conf: [default] ... known_stores = vmware default_store = vmware [glance_store] filesystem_store_datadir = /tri_fs/images/ stores = files,http,vmware default_store = vsphere vmware_server_host = 192.168.3.115 vmware_server_username = administrator(a)vsphere.local vmware_server_password = Zl@123456 vmware_datastore_name = Datastore_iscsi vmware_datacenter_path = Datacenter vmware_datastores = Datacenter:Datastore_iscsi vmware_task_poll_interval = 5 vmware_store_image_dir = /openstack_glance vmware_api_insecure = True I hope you can help me. Thank you very much!

1 0

[largescale-sig] Next meeting: August 26, 8utc
by Thierry Carrez 26 Aug '20

26 Aug '20

Hi everyone, Our next meeting will be a EU-APAC-friendly meeting, on Wednesday, August 26 at 8 UTC[1] in the #openstack-meeting-3 channel on IRC: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200826T08 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting A reminder of the TODOs we had from last meeting, in case you have time to make progress on them: - amorin to add some meat to the wiki page before we push the Nova doc patch further - all to describe briefly how you solved metrics/billing in your deployment in https://etherpad.openstack.org/p/large-scale-sig-documentation Talk to you all on Wednesday, -- Thierry Carrez

1 1

[horizon] default create_volume setting can't be changed
by Eugen Block 26 Aug '20

26 Aug '20

Hi *, we recently upgraded from Ocata to Train and I'm struggling with a specific setting: I believe since Pike version the default for "create_volume" changed to "true" when launching instances from Horizon dashboard. I would like to change that to "false" and set it in our custom /srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.d/_100_local_settings.py: LAUNCH_INSTANCE_DEFAULTS = { 'config_drive': False, 'create_volume': False, 'hide_create_volume': False, 'disable_image': False, 'disable_instance_snapshot': False, 'disable_volume': False, 'disable_volume_snapshot': False, 'enable_scheduler_hints': True, } Other configs from this file work as expected, so that custom file can't be the reason. After apache and memcached restart nothing changes, the default is still "true". Can anyone shed some light, please? I haven't tried other configs yet so I can't tell if more options are affected. Thanks! Eugen

2 3

[nova] Add 'accel_uuids' parameter to rebuild() function of the virt driver
by Brin Zhang(张百林) 26 Aug '20

26 Aug '20

Hi all. In Ussuri release we were completed the nova-cyborg-interaction feature, but there are some operations of instance were blocked [1], we will support evacuate/rebuild [2] and/or shelve/unshelve [2] instance with accelerator in Victoria release. In [2] we will add 'accel_uuids' parameter to the rebuild() method of virt driver and Ironic driver, in virt/driver [4] we are not implemented the rebuild() method, and the 'accel_uuids' will be ignored in virt/ironic/driver. [1] https://docs.openstack.org/api-guide/compute/accelerator-support.html [2] Cyborg evacuate/rebuild support https://review.opendev.org/#/c/715326 [3] Cyborg shelve/unshelve support https://review.opendev.org/#/c/729563 [4] https://github.com/openstack/nova/blob/master/nova/virt/driver.py#L285 [5] https://github.com/openstack/nova/blob/master/nova/virt/ironic/driver.py#L1… brinzhang

1 0

[tripleo] no recheck please
by Emilien Macchi 25 Aug '20

25 Aug '20

We're hitting the docker rate limits very badly right now and while our mitigation patch will land [1], please refrain from approving or recheck patches for now. I've cleared the gate and I'll take care of re-adding these patches into the gate when things will be stable again. [1] https://review.opendev.org/#/c/746993 Thanks for your understanding and your patience! -- Emilien Macchi

1 1

[tripleo] TripleO CI Summary: Unified Sprint 31
by Rafael Folco 25 Aug '20

25 Aug '20

Greetings, The TripleO CI team has just completed **Unified Sprint 31** (July 31 thru Aug 20). The following is a summary of completed work during this sprint cycle*: - Continued building internal component and integration pipelines for rhos-16.2. - Added more jobs to the component and integration pipelines. - Completed promoter code and test scenarios to run on CentOS8/Python3. - Continued merging changes to switch to the new configuration engine in promoter code. - Merged all patches for CentOS-7 -> CentOS-8 stable/train upstream migration. - Design improvements to Tempest scenario manager are under review. - Python3 support on diskimage-builder and buildimage role in tripleo-ci repo is under review. - Ruck/Rover recorded notes [1]. The planned work for the next sprint extends the work started in the previous sprint and focuses on the following: - Downstream OSP 16.2 pipeline. - Next-gen promoter changes (new configuration engine). - Dependency pipeline design to early detect breakages in the OS. - New container naming prefix on Victoria/Master onwards. The Ruck and Rover for this sprint are Arx Cruz (arxcruz) and Amol Kahat (akahat). 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 hackmd [2]. Thanks, rfolco *TripleO-CI team is now using an internal JIRA instance to track sprint work [1] https://hackmd.io/QnprH9-yRTi6uWlEfaahoQ [2] https://hackmd.io/FUalpr55TJuy28QLp2tLng -- Folco

1 0

[OSSA-2020-006] Nova: Live migration fails to update persistent domain XML (CVE-2020-17376)
by Jeremy Stanley 25 Aug '20

25 Aug '20

=================================================================== OSSA-2020-006: Live migration fails to update persistent domain XML =================================================================== :Date: August 25, 2020 :CVE: CVE-2020-17376 Affects ~~~~~~~ - Nova: <19.3.1, >=20.0.0 <20.3.1, ==21.0.0 Description ~~~~~~~~~~~ Tadayoshi Hosoya (NEC) and Lee Yarwood (Red Hat) reported a vulnerability in Nova live migration. By performing a soft reboot of an instance which has previously undergone live migration, a user may gain access to destination host devices that share the same paths as host devices previously referenced by the virtual machine on the source. This can include block devices that map to different Cinder volumes on the destination than the source. The risk is increased significantly in non-default configurations allowing untrusted users to initiate live migrations, so administrators may consider temporarily disabling this in policy if they cannot upgrade immediately. This only impacts deployments where users are allowed to perform soft reboots of server instances; it is recommended to disable soft reboots in policy (only allowing hard reboots) until the fix can be applied. Patches ~~~~~~~ - https://review.opendev.org/747978 (Pike) - https://review.opendev.org/747976 (Queens) - https://review.opendev.org/747975 (Rocky) - https://review.opendev.org/747974 (Stein) - https://review.opendev.org/747973 (Train) - https://review.opendev.org/747972 (Ussuri) - https://review.opendev.org/747969 (Victoria) Credits ~~~~~~~ - Tadayoshi Hosoya from NEC (CVE-2020-17376) - Lee Yarwood from Red Hat (CVE-2020-17376) References ~~~~~~~~~~ - https://launchpad.net/bugs/1890501 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-17376 Notes ~~~~~ - The stable/rocky, stable/queens, and stable/pike branches are under extended maintenance and will receive no new point releases, but patches for them are provided as a courtesy. -- Jeremy Stanley OpenStack Vulnerability Management Team

1 0

Re: Openstack with Nginx Support (HARISH KUMAR Ivaturi)
by prakash RAMCHANDRAN 25 Aug '20

25 Aug '20

Harish, Note Horizon dashboard is based on Django framework over Apache. Thus logically it should work if you deploy Django over Nginx and please refer to link getting Django and once you have that rest should work as the Model, View, Controller (MVC) take care of addressing the rest. I have not seen any Ngnix deployment of Open stack, but a single domain Open stack Controller should be possible to deploy with Nginx. You can also reach out to Ngnix or F5 team to help you out, as this is a good exercise for leveraging capability of Nginix for OpenSrack https://uwsgi-docs.readthedocs.io/en/latest/tutorials/Django_and_nginx.html ThanksPrakash ---------------------------------------------------------------------- Message: 1 Date: Tue, 25 Aug 2020 14:30:27 +0200 From: HARISH KUMAR Ivaturi <harishkumarivaturi(a)gmail.com> To: openstack-discuss(a)lists.openstack.org Subject: Openstack with Nginx Support Message-ID: <CAGmfrByFq8++y6T6sBvKmCjb+T9MGhkua0WP6ZYOVb0gkCTXRA(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi I am Harish Kumar, Master Student at BTH, Karlskrona, Sweden. I am working on my Master thesis at BTH and my thesis topic is Performance evaluation of OpenStack with HTTP/3. I have successfully built curl and nginx with HTTP/3 support and I am performing some commands using curl for generating tokens so i could access the services of OpenStack. OpenStack relies with the Apache web server and I could not get any results using Nginx HTTP/3 . I would like to ask if there is any official documentation on OpenStack relying with Nginx?, I have searched in the internet reg. this info but could not get any, I would like to use nginx instead of apache web server , so I could get some results by performing curl and commands and nginx web server (with http/3 support). Please let me know and if there is any content please share with me. I hope you have understood this. It would be helpful for my Master Thesis. BR Harish Kumar

1 0

[tc] weekly update
by Mohammed Naser 25 Aug '20

25 Aug '20

Hi everyone, Here’s an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. We've also included a few references to some important mailing list threads that you should check out. # Patches ## Open Reviews - Add assert:supports-standalone https://review.opendev.org/722399 - Add etcd3gw to Oslo https://review.opendev.org/747188 - Update and simplify comparison of working groups https://review.opendev.org/746763 - Drop requirement of 1/3 positive TC votes to land https://review.opendev.org/746711 - Resolution to define distributed leadership for projects https://review.opendev.org/744995 - Move towards dual office hours in diff TZ https://review.opendev.org/746167 - Create starter-kit:kubernetes-in-virt tag https://review.opendev.org/736369 - Drop all exceptions for legacy validation https://review.opendev.org/745403 - Move towards single office hour https://review.opendev.org/745200 ## General Changes - Fix names inside check-review-status https://review.opendev.org/745913 # Email Threads - Zuul Native Jobs Goal Update #2: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016561.h… - Masakari Project Aliveness: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016520.h… - vPTG October 2020 Signup: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016497.h… - OpenStack Client vs python-*clients: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016409.h… Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[monasca] Deprecate monasca-transform repository
by Witek Bedyk 25 Aug '20

25 Aug '20

Hello, this message is to announce the deprecation of openstack/monasca-transform repository. The project will not accept new development on master branch but accept fixes on stable branches. It will follow the process described in Project Team Guide [1]. Please reply to this message until Sept. 7 if you would like to take over the development and maintenance of this repository. Thanks Witek [1] https://docs.openstack.org/project-team-guide/repository.html#deprecating-a…

1 0

Openstack with Nginx Support
by HARISH KUMAR Ivaturi 25 Aug '20

25 Aug '20

Hi I am Harish Kumar, Master Student at BTH, Karlskrona, Sweden. I am working on my Master thesis at BTH and my thesis topic is Performance evaluation of OpenStack with HTTP/3. I have successfully built curl and nginx with HTTP/3 support and I am performing some commands using curl for generating tokens so i could access the services of OpenStack. OpenStack relies with the Apache web server and I could not get any results using Nginx HTTP/3 . I would like to ask if there is any official documentation on OpenStack relying with Nginx?, I have searched in the internet reg. this info but could not get any, I would like to use nginx instead of apache web server , so I could get some results by performing curl and commands and nginx web server (with http/3 support). Please let me know and if there is any content please share with me. I hope you have understood this. It would be helpful for my Master Thesis. BR Harish Kumar

1 0

[ironic] RFC: deprecate the iSCSI deploy interface?
by Dmitry Tantsur 25 Aug '20

25 Aug '20

Hi all, Side note for those lacking context: this proposal concerns deprecating one of the ironic deploy interfaces detailed in https://docs.openstack.org/ironic/latest/admin/interfaces/deploy.html. It does not affect the boot-from-iSCSI feature. I would like to propose deprecating and removing the 'iscsi' deploy interface over the course of the next 2 cycles. The reasons are: 1) The iSCSI deploy is a source of occasional cryptic bugs when a target cannot be discovered or mounted properly. 2) Its security is questionable: I don't think we even use authentication. 3) Operators confusion: right now we default to the iSCSI deploy but pretty much direct everyone who cares about scalability or security to the 'direct' deploy. 4) Cost of maintenance: our feature set is growing, our team - not so much. iscsi_deploy.py is 800 lines of code that can be removed, and some dependencies that can be dropped as well. As far as I can remember, we've kept the iSCSI deploy for two reasons: 1) The direct deploy used to require Glance with Swift backend. The recently added [agent]image_download_source option allows caching and serving images via the ironic's HTTP server, eliminating this problem. I guess we'll have to switch to 'http' by default for this option to keep the out-of-box experience. 2) Memory footprint of the direct deploy. With the raw images streaming we no longer have to cache the downloaded images in the agent memory, removing this problem as well (I'm not even sure how much of a problem it is in 2020, even my phone has 4GiB of RAM). If this proposal is accepted, I suggest to execute it as follows: Victoria release: 1) Put an early deprecation warning in the release notes. 2) Announce the future change of the default value for [agent]image_download_source. W release: 3) Change [agent]image_download_source to 'http' by default. 4) Remove iscsi from the default enabled_deploy_interfaces and move it to the back of the supported list (effectively making direct deploy the default). X release: 5) Remove the iscsi deploy code from both ironic and IPA. Thoughts, opinions, suggestions? Dmitry

6 11

[cliff] [dev] Cliff auto completion not working inside interactive mode
by sandeep 25 Aug '20

25 Aug '20

Hi Team, In my system, I am trying auto completion for my CLI application. CLIFF version - cliff==3.4.0 Auto complete works fine on bash prompt. But inside the interactive shell, auto complete does not work. Below is the output for the help command inside the interactive shell. (appcli) help Miscellaneous help topics: ========================== help Application commands (type help <topic>): ========================================= complete snapshot list reports service restart service-object-type app2 service restart service-object-type app3 service restart service-object-type app4 service show state service-object-type app1 service show state service-object-type app2 service show state service-object-type app3 service show state service-object-type app4 swm rollback node swm cancel sw-update swm downgrade node swm list sw-info swm show sw-info swm start sw-update file swm start sw-downgrade help Now, if I type swm and press tab, it lists all the sub commands under it. (appcli) swm cancel sw-update list sw-info start sw-update file downgrade node rollback node show sw-info start sw-downgrade But if i type, (appcli) swm s<tab> gives below output, (appcli) swm "s It stops at this point and further pressing tab does not autocomplete. Could you please let me know what could be the problem? Is this a known issue? or Am i missing something? Thanks, Sandeep

1 0

Scaling control nodes
by Benjamin Zapiec 25 Aug '20

25 Aug '20

Hello everyone, while trying openstack i referred to the red hat installation documentation which is okay but lead to one question. It looks like there is no problem in scaling compute nodes if you run out of resources. But scaling the controller nodes is not supported by red hat. Since I'm using the official tripleo openstack version and not the red hat version i was wondering if this is not supported by the openstack project. Having in mind that red hat doesn't support this i was looking for something that tells me that it is supported (or not) by the tripleo openstack project. But i didn't found anything explicit. So may you tell me if it is possible to scale up Controller Nodes? And if not which component is not scalable by tripleo? Is it possible to create an controller profile that is scalable? Best regards -- Benjamin Zapiec <benjamin.zapiec(a)gonicus.de> (System Engineer) * GONICUS GmbH * Moehnestrasse 55 (Kaiserhaus) * D-59755 Arnsberg * Tel.: +49 2932 916-0 * Fax: +49 2932 916-245 * http://www.GONICUS.de * Sitz der Gesellschaft: Moehnestrasse 55 * D-59755 Arnsberg * Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder * Vorsitzender des Beirats: Juergen Michels * Amtsgericht Arnsberg * HRB 1968 Wir erfüllen unsere Informationspflichten zum Datenschutz gem. der Artikel 13 und 14 DS-GVO durch Veröffentlichung auf unserer Internetseite unter: https://www.gonicus.de/datenschutz oder durch Zusendung auf Ihre formlose Anfrage.

1 0