- openstack-discuss - lists.openstack.org

RE: Rabbitmq error report
by Md. Farhad Hasan Khan 14 Sep '19

14 Sep '19

Hi, [root@controller1 ~]# rabbitmqctl list_queues |grep notification notifications.debug 0 notifications.critical 0 notifications.error 0 notifications.info 0 notifications.warn 0 notifications.audit 0 notifications.sample 0 versioned_notifications.error 6 [root@controller1 ~]# From: Md. Farhad Hasan Khan Sent: Thursday, September 12, 2019 3:29 PM To: 'OpenStack Discuss' Subject: Rabbitmq error report Hi, I'm getting this error continuously in rabbitmq log. Though all operation going normal, but slow. Sometimes taking long time to perform operation. Please help me to solve this. rabbitmq version: rabbitmq_server-3.6.16 =ERROR REPORT==== 12-Sep-2019::13:04:55 === Channel error on connection <0.8105.3> (192.168.21.56:60116 -> 192.168.21.11:5672, vhost: '/', user: 'openstack'), channel 1: operation queue.declare caused a channel exception not_found: failed to perform operation on queue 'versioned_notifications.info' in vhost '/' due to timeout =WARNING REPORT==== 12-Sep-2019::13:04:55 === closing AMQP connection <0.8105.3> (192.168.21.56:60116 -> 192.168.21.11:5672 - nova-compute:3493037:e6757c9b-1cdc-43cd-bfd3-dcb58aa4974a, vhost: '/', user: 'openstack'): client unexpectedly closed TCP connection Thanks & B'Rgds, Rony

1 0

[keystone] Keystone Team Update - Week of 9 September 2019
by Colleen Murphy 14 Sep '19

14 Sep '19

# Keystone Team Update - Week of 9 September 2019 ## News ### Feature Freeze Status We have a number of policy changes and one spec implementation still crawling through the gate[1]. Since these have all been reviewed and approved we'll continue to babysit them until they have made it. Federated user attributes[2] and expiring group membership[3] are being deferred until next cycle due to insufficient reviews/incomplete implementation. [1[ https://etherpad.openstack.org/p/keystone-train-feature-freeze-todo [2] https://review.opendev.org/#/q/topic:bp/support-federated-attr [3] https://review.opendev.org/#/q/topic:bug/1809116 ## Office Hours When there are topics to cover, the keystone team holds office hours on Tuesdays at 17:00 UTC. The topic for next week's office hour will be: bug triage and prioritizing bugs for RC. The location for next week's office hour will be: https://meet.jit.si/keystone-office-hours Add topics you would like to see covered during office hours to the etherpad: https://etherpad.openstack.org/p/keystone-office-hours-topics ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 41 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 51 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ### Priority Reviews https://etherpad.openstack.org/p/keystone-train-feature-freeze-todo ## Bugs This week we opened 5 new bugs and closed 7. Bugs opened (5) Bug #1843609 (keystone:High) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1843609 Bug #1843464 (keystone:Medium) opened by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1843464 Bug #1843925 (keystone:Undecided) opened by Ben Nemec https://bugs.launchpad.net/keystone/+bug/1843925 Bug #1843903 (python-keystoneclient:Undecided) opened by Andrew Berezovskiy https://bugs.launchpad.net/python-keystoneclient/+bug/1843903 Bug #1843931 (oslo.policy:Medium) opened by Ben Nemec https://bugs.launchpad.net/oslo.policy/+bug/1843931 Bugs closed (1) Bug #1843903 (python-keystoneclient:Undecided) https://bugs.launchpad.net/python-keystoneclient/+bug/1843903 Bugs fixed (6) Bug #1750669 (keystone:High) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1750669 Bug #1805368 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1805368 Bug #1805371 (keystone:Medium) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1805371 Bug #1818846 (keystone:Low) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1818846 Bug #1818850 (keystone:Low) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1818850 Bug #1805409 (keystone:Wishlist) fixed by Vishakha Agarwal https://bugs.launchpad.net/keystone/+bug/1805409 ## Milestone Outlook https://releases.openstack.org/train/schedule.html We're now past feature freeze and entering the RC period. Development focus should be on fixing bugs and helping to stabilize CI. RC1 will be cut in 2 weeks. We're also at requirements freeze, which means no new dependencies can be added and versions can't be changed. We're also at soft string freeze, so be mindful of checking that changes are not modifying strings. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

Execute a script on every object upload event (Swift+aodh)
by Anmar Salih 13 Sep '19

13 Sep '19

Hey all, Need help to configure swift and aodh. The idea is to trigger aodh alarm on very object upload event on swift. Once the alarm triggered, a small script should be executed. So the sequence of operations should be like this: 1- Object just uploaded to swift container 2- Alarm triggered by aodh 3- Once alarm triggered , execute python script. I am using Devstack Stein release installed on virtual box. Best regards. Anmar Salih

2 1

[all][PTL] Call for Cycle Highlights for Train
by Kendall Nelson 13 Sep '19

13 Sep '19

Hello Everyone! As you may or may not have read last week in the release update from Sean, its time to call out 'cycle-highlights' in your deliverables! As PTLs, you probably get many pings towards the end of every release cycle by various parties (marketing, management, journalists, etc) asking for highlights of what is new and what significant changes are coming in the new release. By putting them all in the same place it makes them easy to reference because they get compiled into a pretty website like this from Rocky[1] or this one for Stein[2]. We don't need a fully fledged marketing message, just a few highlights (3-4 ideally), from each project team. *The deadline for cycle highlights is the end of the R-5 week [3] on Sept 13th.* How To Reminder: ------------------------- Simply add them to the deliverables/train/$PROJECT.yaml in the openstack/releases repo similar to this: cycle-highlights: - Introduced new service to use unused host to mine bitcoin. The formatting options for this tag are the same as what you are probably used to with Reno release notes. Also, you can check on the formatting of the output by either running locally: tox -e docs And then checking the resulting doc/build/html/train/highlights.html file or the output of the build-openstack-sphinx-docs job under html/train/ highlights.html. Thanks :) -Kendall Nelson (diablo_rojo) [1] https://releases.openstack.org/rocky/highlights.html [2] https://releases.openstack.org/stein/highlights.html [3] https://releases.openstack.org/train/schedule.html <https://releases.openstack.org/train/schedule.html#t-cycle-highlights>

1 2

Re: [Release-job-failures] release-post job for openstack/releases for ref refs/heads/master failed
by Sean McGinnis 13 Sep '19

13 Sep '19

On Fri, Sep 13, 2019 at 04:07:54PM +0000, zuul(a)openstack.org wrote: > Build failed. > > - tag-releases https://zuul.opendev.org/t/openstack/build/c95672e425294127821c55ddf1176218 : RETRY_LIMIT in 1m 18s > - publish-tox-docs-static https://zuul.opendev.org/t/openstack/build/None : SKIPPED > > _______________________________________________ > Release-job-failures mailing list > Release-job-failures(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures Just to make sure there is a record of it - this was a temporary infrastructure sync issue that was quickly resolved. The job was reenqueued and everything completed fine. Looks like everything is now good and no further action is needed, but of course if anything odd is seen related to this, please let us know. Sean

1 0

[release][freezer][karbor][kuryr][magnum][manila][monasca][neutron][senlin][tacker][winstackers] Missing releases for some deliverables
by Thierry Carrez 13 Sep '19

13 Sep '19

Hi everyone, Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the Train cycle: - freezer and freezer-web-ui - karbor and karbor-dashboard - kuryr-kubernetes - magnum-ui - manila-ui - monasca-agent, monasca-api, monasca-ceilometer, monasca-events-api, monasca-log-api, monasca-notification, monasca-persister and monasca-transform - networking-hyperv - neutron-fwaas-dashboard and neutron-vpnaas-dashboard - senlin-dashboard - tacker-horizon Those should be released ASAP, and in all cases before September 26th, so that we have a release to include in the final Train release. Thanks in advance, -- Thierry Carrez (ttx)

3 2

[release] Release countdown for week R-4, September 16-20
by Sean McGinnis 13 Sep '19

13 Sep '19

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the Train deliverables can be proposed, well ahead of the final Train release date. General Information ------------------- We are still finishing up processing a few release requests, but the Train release requirements are now frozen. If new library releases are needed to fix release-critical bugs in Train, you must request a Feature Freeze Exception (FFE) from the requirements team before we can do a new release to avoid having something released in Train that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] FFE requested for $PROJECT_LIB Include justification/reasoning for why a FFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By September 26 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions --------- stable/train branches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for Train changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed Train cycle-highlights yet, you are already late to the party. Please see http://lists.openstack.org/pipermail/openstack-discuss/2019-September/00913… for details. Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 26 (R-3 week) Final RC deadline: October 10 (R-1 week) Final Train release: October 16 Forum+PTG at Shanghai summit: November 4

1 0

[goal][python3] Train unit tests weekly update (goal-0)
by Corey Bryant 13 Sep '19

13 Sep '19

This is the goal-0 weekly update for the "Update Python 3 test runtimes for Train" goal [1]. Today is the final day for completion of Train community goals [2]. == How can you help? == If your project has failing tests please take a look and help fix. Python 3.7 unit tests will be self-testing in Zuul. Failing patches: https://review.openstack.org/#/q/topic:python3-train +status:open+(+label:Verified-1+OR+label:Verified-2+) If your project has patches with successful tests please help get them merged. Open patches needing reviews: https://review.openstack.org/#/q/topic:python3 -train+is:open Patch automation scripts needing review: https://review.opendev.org/#/c/666934 == Ongoing Work == We're down to 3 projects with failing tests, and 2 projects with successful tests. Barbican and PowerVM are actively working on getting patches landed. I've not been successful in making contact with the Freezer PTL. Thank you to all who have contributed their time and fixes to enable patches to land! == Completed Work == All patches have been submitted to all applicable projects for this goal. Merged patches: https://review.openstack.org/#/q/topic:python3-train +is:merged == What's the Goal? == To ensure (in the Train cycle) that all official OpenStack repositories with Python 3 unit tests are exclusively using the 'openstack-python3-train-jobs' Zuul template or one of its variants (e.g. 'openstack-python3-train-jobs-neutron') to run unit tests, and that tests are passing. This will ensure that all official projects are running py36 and py37 unit tests in Train. For complete details please see [1]. == Reference Material == [1] Goal description: https://governance.openstack.org/tc/goals/train/ python3-updates.html [2] Train release schedule: https://releases.openstack.org/train /schedule.html (see R-5 for "Train Community Goals Completed") Storyboard: https://storyboard.openstack.org/#!/story/2005924 Porting to Python 3.7: https://docs.python.org/3/whatsnew/3.7.html#porting-to-python-3-7 Python Update Process: https://opendev.org/openstack/governance/src/branch/master/resolutions/2018… Train runtimes: https://opendev.org/openstack/governance/src/branch/master/reference/runtim… train.rst Thanks, Corey

1 0

[tc][uc][meta-sig] How to help SIGs to have a better life? (Needs feedback for SIGs guideline)
by Rico Lin 13 Sep '19

13 Sep '19

Hi all, The question I would like to ask is, what else we can do here to help SIGs to have a better life? What can we do from here? And is there any feedback regarding on experience of participate a SIG or chairing one? For some work in progress (or completed) actions: I'm working on a guideline for SIGs ( https://etherpad.openstack.org/p/SIGs-guideline ) because I believe it might provide some value for SIGs, especially new-formed SIGs. Please kindly provide your feedback on it. Will send a patch to update current document under governance-sigs once we got good enough confident on it. On the other hand, the reason I start this work is because we're thinking `How to help SIGs to have a better life?` There're some actions I can think of and the most easier answers are to get SIGs status, update guidelines and explain why we need SIG in general. So actions: I'm working on SIG guideline ( https://etherpad.openstack.org/p/SIGs-guideline ) and document `Comparison of Official Group Structures` ( https://review.opendev.org/#/c/668093/ ). Also, reach out to SIGs earlier this year to collect help most needed information for SIGs and WGs ( https://etherpad.openstack.org/p/DEN-help-most-needed-for-sigs-and-wgs ) Also, I know Belmiro Moreira (UC member) has reached out to SIGs too, so there are some up to date information. I will try to put all the above information together for share. And now, back to the question, what can we do from here? Or is there any other feedback? Before I start to disturb everyone with crazy ideas in my mind, would like to hear feedback from all of you. Finally, feedback on SIG guideline is desired. Thanks! -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

2 1

[openstack-dev] [neutron] Cancelling Neutron Drivers meeting on September 13th
by Miguel Lavalle 12 Sep '19

12 Sep '19

Dear Neutrinos, We don't have RFEs ready to be discussed during this week's drivers meeting. As a consequence, let's skip it. However, last week we discussed https://bugs.launchpad.net/neutron/+bug/1837847 and asked the submitter to write a spec, which he did: https://review.opendev.org/#/c/680990/. Please review it and let's be ready to go back the this RFE during the meeting on the 20th Best regards Miguel

1 0

Re: [nova] Deprecating the XenAPI driver
by James Benson 12 Sep '19

12 Sep '19

Matt, I am currently working on trying to deploy Xen OpenStack. Currently I have been trying to get it working on Rocky with Xen6.0 and will code fix for Stein/Train as well if possible. Trying to get a working solution with Rocky then will patch up the line. I have reached out to the last person who submitted a bug fix in Xen (with no response), but I am actively trying to get this working. Unfortunately it is a one-man job, so it is taking a lot of time. Currently facing issues with Nova and Neutron. James

3 2

Re: [Openstack-stable-maint] Stable check of openstack/swift for ref refs/heads/stable/pike failed
by Tim Burke 12 Sep '19

12 Sep '19

Wrote up https://bugs.launchpad.net/swift/+bug/1843816 to describe the issue; tl;dr is that python's http.client/httplib got more picky about sending only RFC-compliant HTTP requests, but Swift's proxy was happy to accept non-compliant query strings and try to forward them on to backend servers. Fix for master is up at https://review.opendev.org/#/c/681875/, and a backport for pike is up at https://review.opendev.org/#/c/681879/. Once I see passing checks there, I'll propose backports for everyone in between, plus ocata. Tim On Wed, 2019-09-11 at 06:43 +0000, A mailing list for the OpenStack Stable Branch test reports. wrote: > Build failed. > > - build-openstack-sphinx-docs > https://zuul.opendev.org/t/openstack/build/d7030406f5224d78baebbe5dbe80b4d5 > : SUCCESS in 6m 39s > - openstack-tox-py27 > https://zuul.opendev.org/t/openstack/build/a4ee29fb61684505995fda21718fcd89 > : FAILURE in 7m 15s > > _______________________________________________ > Openstack-stable-maint mailing list > Openstack-stable-maint(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint

1 0

[oslo][release][requirements] FFE request for oslo.policy, privsep, and service
by Ben Nemec 12 Sep '19

12 Sep '19

Hi, As discussed in the release meeting today, I'm requesting an FFE for oslo.policy, oslo.privsep, and oslo.service. The latter two are only release notes for things that landed late in the cycle, and oslo.policy is a small bugfix in sample policy generation. These should all be backportable if necessary, but for convenience we'd like to get them out now. Thanks. -Ben

2 1

[openstack-ansible] office hours update
by Mohammed Naser 12 Sep '19

12 Sep '19

Hi everyone, Here’s the update of what happened in this week’s OpenStack Ansible Office Hours. We finished installing the Python3 for ansible-runtime virtual environment. We discussed how Centos 7.7 wasn’t out yet but we want to move to Python 3 so we’ll start using the CR repository. The placement extract and upgrade jobs are in progress. We clarified the whole definition around freezing a milestone and features and what it implies. The roles for Train milestones were frozen. We’ll wait for Python3, placement and bind-to-mgmt before proposing the milestone. Galera is still having issues and we’re having trouble understanding and fixing them but it has something to do with listening to localhost. We tested Ansible 2.9 and are trying to figure out if we want to use it for Train. We’re having issues with bumping up os-vif for Stein because they seem to be only for testing according to OpenStack Requirements. We talked about maybe using the in-repository local constraints or creating a tag, but we don’t think they can be bumped. It seems later that it was clarified that we can do that, and os-vif made a new release today so we can check it out. Finally, we discussed a journal logging error on Stein. There’s a case of python-systemd missing for logging. Thanks! Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0

[tc] TC Chair Nominations - closing soon
by Graham Hayes 12 Sep '19

12 Sep '19

Hello all new and returning TC members! Welcome (back) to the TC. We now have to do some of the standard post election paperwork / processes. One of the first things we need to do is elect a chair for this cycle! We currently have 2 nominations, and nominations will remain open until 23:59 UTC tomorrow 12-Sept-2019. At that point, we will start a CIVS election for the chair, and select them. To nominate yourself, just add a review to the governance repo like so : [1][2]. If you are interested in the chair, please do consider running - It is open to everyone, new and less new on the TC, and the job has been documented by previous chairs and TC members [3] If you have any questions - reply to this mail, ask in the #openstack-tc IRC room, reply to me and I will see who I can put you in contact with, who may know, or ping mnaser, who is the current chair. I propose the following timeline: Nominations Close: 2019-09-12 @ 23:59 UTC. Election created: Morning (EU timezone) of 13 Sept Election finish: Evening (EU timezone) of 18 Sept or when all TC members have voted. Thanks all, and please reach out with any questions! - Graham 1 - https://review.opendev.org/#/c/681285/2/reference/members.yaml 2 - https://review.opendev.org/#/c/680414/2/reference/members.yaml 3 - https://opendev.org/openstack/governance/src/branch/master/CHAIR.rst

2 1

Rabbitmq error report
by Md. Farhad Hasan Khan 12 Sep '19

12 Sep '19

Hi, I'm getting this error continuously in rabbitmq log. Though all operation going normal, but slow. Sometimes taking long time to perform operation. Please help me to solve this. rabbitmq version: rabbitmq_server-3.6.16 =ERROR REPORT==== 12-Sep-2019::13:04:55 === Channel error on connection <0.8105.3> (192.168.21.56:60116 -> 192.168.21.11:5672, vhost: '/', user: 'openstack'), channel 1: operation queue.declare caused a channel exception not_found: failed to perform operation on queue 'versioned_notifications.info' in vhost '/' due to timeout =WARNING REPORT==== 12-Sep-2019::13:04:55 === closing AMQP connection <0.8105.3> (192.168.21.56:60116 -> 192.168.21.11:5672 - nova-compute:3493037:e6757c9b-1cdc-43cd-bfd3-dcb58aa4974a, vhost: '/', user: 'openstack'): client unexpectedly closed TCP connection Thanks & B'Rgds, Rony

1 0

[ceph][nova][DR] Openstack DR Setup
by Premdeep S 12 Sep '19

12 Sep '19

Hi Team, We are looking to build a DR infrastructure. Our existing DC setup consists of multiple node Controller, Compute and Ceph nodes as the storage backend. We are using ubuntu 18.04 and Rocky version. Can someone please share any document or guide us on how we can build a DR infra for the existing DC? 1. Do we need to have the storage shared across (Ceph)? 2. What are the dependencies? 3. Is there a guide for the same Thanks Prem

1 1

[qa] forum sessions brainstorming
by Masayuki Igawa 11 Sep '19

11 Sep '19

Hi All, I have created the below etherpad[0] to collect the forum ideas related to QA for Shanghai Summit. Please write up your ideas with your IRC name on the etherpad. [0] https://etherpad.openstack.org/p/PVG-forum-qa-brainstorming -- Masayuki

1 0

[self-healing][autohealing][PTG][Forum] brainstorming etherpads for Shanghai
by Eric K 11 Sep '19

11 Sep '19

Hello healers, The brainstorming etherpads for Self-healing Forum and PTG sessions are up: https://etherpad.openstack.org/p/SHA-self-healing-SIG Please add your topics there. Looking forward to productive discussions in Shanghai!

1 0

How to boot 2 VMs in openstack on same subnet?
by Paul Belanger 11 Sep '19

11 Sep '19

Greetings, We use a few openstack public clouds for testing in the ansible project, specifically using nodepool. We have a use case, where we need to boot 2 VMs on the same public subnet for testing reasons. However, the majority of the clouds we are using, do not have a single subnet for their entire public IP range. Up until now, we boot the 2 VMs, then hope they land on the same subnet, but this isn't really efficient. Basically looking to see if there is a better way to handle this either via openstacksdk or some other configuration we need cloud side. Also note, we'd like to do this with public provider network (which we don't have control over) and avoid using private network for now. Paul

3 3

Re: [rpm-packaging] Proposing new core member
by Nicolas Bock 11 Sep '19

11 Sep '19

On 9/11/19 6:48 AM, Thomas Bechtold wrote: > Hi, > > I would like to nominate Ralf Haferkamp for rpm-packaging core. > Ralf has be active in doing very valuable reviews since some time so I > feel he would be a great addition to the team. > > Please give your +1/-1 in the next days. +1 > Cheers, > > Tom > >

1 0

[rpm-packaging] Proposing new core member
by Thomas Bechtold 11 Sep '19

11 Sep '19

Hi, I would like to nominate Ralf Haferkamp for rpm-packaging core. Ralf has be active in doing very valuable reviews since some time so I feel he would be a great addition to the team. Please give your +1/-1 in the next days. Cheers, Tom

2 1

[sahara] Cancelling Sahara meeting September 12
by Jeremy Freudberg 11 Sep '19

11 Sep '19

Hi all, There will be no Sahara meeting 2019-09-12, the reason being that Luigi is not around and there is not much to discuss anyway. Holler if you need anything. Thanks, Jeremy

1 0

Re: [Horizon] Paging and Angular...
by Marek Lyčka 11 Sep '19

11 Sep '19

Hi, > we need people familiar with Angular and Horizon's ways of using Angular (which seem to be very > non-standard) that would be willing to write and review code. Unfortunately the people who originally > introduced Angular in Horizon and designed how it is used are no longer interested in contributing, > and there don't seem to be any new people able to handle this. I've been working with Horizon's Angular for quite some time and don't mind keeping at it, but it's useless unless I can get my code merged, hence my original message. As far as attracting new developers goes, I think that removing some barriers to entry couldn't hurt - seeing commits simply lost to time being one of them. I can see it as being fairly demoralizing. > Personally, I think that a better long-time strategy would be to remove all > Angular-based views from Horizon, and focus on maintaining one language and one set of tools. Removing AngularJS wouldn't remove JavaScript from horizon. We'd still be left with a home-brewish framework (which is buggy as is). I don't think removing js completely is realistic either: we'd lose functionality and worsen user experience. I think that keeping Angular is the better alternative: 1) A lot of work has already been put into Angularization, solving many problems 2) Unlike legacy js, Angular code is covered by automated tests 3) Arguably, improvments are, on average, easier to add to Angular than pure js implementations Whatever reservations there may be about the current implementation can be identified and addressed, but all in all, I think removing it at this point would be counterproductive. M. čt 5. 9. 2019 v 14:28 odesílatel Radomir Dopieralski <openstack(a)sheep.art.pl> napsal: > Both of your questions have one answer: we need people familiar with > Angular and Horizon's ways of using Angular (which seem to be very > non-standard) that would be willing to write and review code. Unfortunately > the people who originally introduced Angular in Horizon and designed how it > is used are no longer interested in contributing, and there don't seem to > be any new people able to handle this. Personally, I think that a better > long-time strategy would be to remove all Angular-based views from Horizon, > and focus on maintaining one language and one set of tools. > > On Thu, Sep 5, 2019 at 1:52 PM Marek Lyčka <marek.lycka(a)ultimum.io> wrote: > >> Hi all, >> >> I took apart the Horizon paging mechanism while working on [1] and have a >> few of findings: >> >> - Paging is unimplemented/turned off for many (if not most) panels, not >> just Routers and Networks >> - Currently, single page data loads could potentially bump up against API >> hard limits >> - Sorting is also broken in places where paging is enabled (Old >> images...), see [2] >> - The Networks table loads data via three API calls due to neutron API >> limitations, which makes the marker based mechanism unusable >> - There is at least one more minor bug which breaks pagination, there may >> be more >> >> While some of these things may be fixable in different hacky and/or >> inefficient ways, >> we already have Angular implementations which fix many of them and make >> improving >> and fixing the rest easier. >> >> Since Angular ports would help with other unrelated issues as well and >> allow us to >> start deprecating old code, I was wondering two things: >> >> 1) What would it take to increase the priority of Angularization in >> general? >> 2) Can the Code Review process be modified/improved to increase the >> chance for >> Angularization changes to be code reviewed and merged if they do >> happen? >> My previous attempts in this area have failed because of lack of code >> reviewers... >> >> Since full Angularization is still the goal for Horizon as far as I know, >> I'd rather >> spend time doing that than hacking solutions to different problems in >> legacy code >> which is slated deprecation. >> >> Best Regards, >> Marek >> >> [1] https://bugs.launchpad.net/horizon/+bug/1746184 >> [2] https://bugs.launchpad.net/horizon/+bug/1782732 >> >> -- >> Marek Lyčka >> Linux Developer >> >> Ultimum Technologies s.r.o. >> Na Poříčí 1047/26, 11000 Praha 1 >> Czech Republic >> >> marek.lycka(a)ultimum.io <stanislav.ulrych(a)ultimum.io> >> *https://ultimum.io <https://ultimum.io/>* >> > -- Marek Lyčka Linux Developer Ultimum Technologies s.r.o. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic marek.lycka(a)ultimum.io <stanislav.ulrych(a)ultimum.io> *https://ultimum.io <https://ultimum.io/>*

3 3

RE: [winstackers][powervmstackers][tc] removing winstackers and PowerVMStackers from TC governance
by Lucian Petrut 11 Sep '19

11 Sep '19

Hi, I had a chat with my team and we think it would be best if we could keep Winstackers as a separate team. This is mostly because of the associated projects, which are essential for the Windows – Openstack integration effort. Other teams may not be interested in adopting those projects, which would be required if we chose the SIG route. Despite missing this election, I can assure you that we’re quite active in this endeavor. I’m willing to take the PTL role, offloading this task from Claudiu, whose time was quite limited recently. Regards, Lucian Petrut Cloudbase Solutions ________________________________________ From: Mohammed Naser [mnaser(a)vexxhost.com] Sent: Monday, September 09, 2019 3:05 PM To: Thierry Carrez Cc: OpenStack Discuss Subject: Re: [winstackers][powervmstackers][tc] removing winstackers and PowerVMStackers from TC governance On Fri, Sep 6, 2019 at 5:10 AM Thierry Carrez <thierry(a)openstack.org> wrote: > > Divya K Konoor wrote: > > Missing the deadline for a PTL nomination cannot be the reason for > > removing governance. > > I agree with that, but missing the deadline twice in a row is certainly > a sign of some disconnect with the rest of the OpenStack community. > Project teams require a minimal amount of reactivity and presence, so it > is fair to question whether PowerVMStackers should continue as a project > team in the future. > > > PowerVMStackers continue to be an active project > > and would want to be continued to be governed under OpenStack. For PTL, > > an eligible candidate can still be appointed . > > There is another option, to stay under OpenStack governance but without > the constraints of a full project team: PowerVMStackers could be made an > OpenStack SIG. > > I already proposed that 6 months ago (last time there was no PTL nominee > for the team), on the grounds that interest in PowerVM was clearly a > special interest, and a SIG might be a better way to regroup people > interested in supporting PowerVM in OpenStack. > > The objection back then was that PowerVMStackers maintained a number of > PowerVM-related code, plugins and drivers that should ideally be adopted > by their consuming project teams (nova, neutron, ceilometer), and that > making it a SIG would endanger that adoption process. > > I still think it makes sense to consider PowerVMStackers as a Special > Interest Group. As long as the PowerVM-related code is not adopted by > the consuming projects, it is arguably a special interest, and not a > completely-integrated part of OpenStack components. > > The only difference in being a SIG (compared to being a project team) > would be to reduce the amount of mandatory tasks (like designating a PTL > every 6 months). You would still be able to own repositories, get room > at OpenStack events, vote on TC election... > > It would seem to be the best solution in your case. I echo all of this and I think at this point, it's better for the deliverables to be within a SIG. > -- > Thierry Carrez (ttx) > -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0

[sigs][publiccloud][publiccloud-wg][publiccloud-sig] Bi-weekly meeting for the Public Cloud SIG tomorrow
by Tobias Rydberg 11 Sep '19

11 Sep '19

Hi all, It is time for a new meeting for the Public Cloud SIG! Would love to see as many of you there as possible! Topics for the meeting includes Shanghai Forum topics and moving forward on the billing initiative. Time and place: Tomorrow, 12th September at 1400 UTC in #openstack-publiccloud! Agenda can be found at https://etherpad.openstack.org/p/publiccloud-sig Feel free to add topics to the agenda! Cheers, Tobias -- Tobias Rydberg Senior Developer Twitter & IRC: tobberydberg www.citynetwork.eu | www.citycloud.com INNOVATION THROUGH OPEN IT INFRASTRUCTURE ISO 9001, 14001, 27001, 27015 & 27018 CERTIFIED

1 0

[masakari]
by Liam Young 11 Sep '19

11 Sep '19

Hi, I have a patch up for masakari and another for masakari-monitors: https://review.opendev.org/#/c/647756/ https://review.opendev.org/#/c/675734/ If any of the masakari devs have cycles I'd really love to get them landed. Thanks Liam

1 0

[scientific-sig] No IRC meeting today
by Stig Telfer 11 Sep '19

11 Sep '19

Hi all - Apologies, there will not be a Scientific SIG IRC meeting today, due to chair availability. Cheers, Stig

1 0

[all] [tc] [ptls] PDF Goal Update
by Alexandra Settle 11 Sep '19

11 Sep '19

Hi all, According to the Train schedule, this week is the week of "Train Community Goals completed" [1]. In the last few weeks, we've been working hard on the goal to enable PDF support in the project docs. We have successfully completed... 1. Creating a workable solution [2] 2. Communicating this solution via ML [3] As far as the success of the goal is, that has to be measured by the individual teams. But it looks like we're all going really well at implementing the new changes [4]. Thanks to everyone who has jumped in from across the board to make this a success! I wanted to touch base with the teams and gather a status update from the PTLs or project liaisons on where they are at, what questions they may have, and how we (the docs team and TC) can help. Over the next week I will reach out to each team and gather a status update of sorts. Thanks, Alex -- Alexandra Settle <a.settle(a)outlook.com> IRC: asettle [1] https://releases.openstack.org/train/schedule.html#t-goals-complete [2] https://etherpad.openstack.org/p/train-pdf-support-goal [3] http://lists.openstack.org/pipermail/openstack-discuss/2019-August/ 008503.html (amongst others) [4] https://review.opendev.org/#/q/topic:build-pdf-docs

1 0

[nova][glance][entropy][database] update glance metadata for nova instance
by Jordan Ansell 11 Sep '19

11 Sep '19

Hi Openstack Discuss, I have an issue with nova not synchronizing changes between a glance image and it's local image meta information in nova. I have updated a glance image with the property "hw_rng_model=virtio", and that successfully passes that to new instances created using the updated image. However existing instances do not receive this new property. I have located the image metadata within the nova database, in the **instance_system_metadata** table, and can see it's not updated for the existing instances, and only adding the relevant rows for instances that are created when that property is present. The key being "image_hw_rng_model" and "virtio" being the value. Is there a way to tell nova to update the table for existing instances, and synchronizing the two databases? Or is this the kind of thing that would need to be done *shudder* manually...? If so, are there any experts out there who can point me to some documentation on doing this correctly before I go butcher a couple of dummy nova database? Regards, Jordan

3 4

[Watcher] team meeting at 08:00 UTC today
by li.canwei2＠zte.com.cn 10 Sep '19

10 Sep '19

Hi team, Watcher team will have a meeting at 08:00 UTC today in the #openstack-meeting-alt channel. The agenda is available on https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda feel free to add any additional items. Thanks! Canwei Li

1 0

[nova][keystone][neutron][kuryr][requirements] breaking tests with new library versions
by Matthew Thode 10 Sep '19

10 Sep '19

NOVA: lxml===4.4.1 nova tests fail https://bugs.launchpad.net/nova/+bug/1838666 websockify===0.9.0 tempest test failing KEYSTONE: oauthlib===3.1.0 keystone https://bugs.launchpad.net/keystone/+bug/1839393 NEUTRON: tenacity===5.1.1 https://2c976b5e9e9a7bed9985-82d79a041e998664bd1d0bc4b6e78332.ssl.cf2.rackc… this could be caused by pytest===5.1.0 as well KURYR: kubernetes===10.0.1 openshift PINS this, only kuryr-tempest-plugin deps on it https://review.opendev.org/665352 MISC: tornado===5.1.1 salt is cauing this, no eta on fix (same as the last year) stestr===2.5.0 needs merged https://github.com/mtreinish/stestr/pull/265 jsonschema===3.0.2 see https://review.opendev.org/649789 I'm trying to get this in place as we are getting closer to the requirements freeze (sept 9th-13th). Any help clearing up these bugs would be appreciated. -- Matthew Thode

7 18

[tc] monthly meeting summary
by Mohammed Naser 10 Sep '19

10 Sep '19

Hi everyone, The TC held it’s monthly meeting on the 5th of September 2019 and this email provides a summary of that meeting. We contacted Alan to mention that TC will have some presence at the Shanghai leadership meeting alongside other OSF projects on November 3rd, so the day before the summit. Rico is currently working on an etherpad to update SIG guidelines to simplify the process for new SIGs. Once the draft version is done, they will ask SIG chairs to join in the editing part. We still have to contact interested parties for a new ‘large scale’ SIG so we will follow up again on that action item in the next meeting. Graham is currently in the process of testing the code in order to make the proposal bot for propose project-template patches for specific releases. We’re working on adding some forum sessions ideas for the TC and we’ve got volunteers in the forum selection committee. Thierry finished making goal selection a two-step process and it's been merged. There are a few projects that lacked a PTL elected, we’ve discussed the following points for each: - Cyborg: Sundar self-nominated but only on the mailing list, therefore we will appoint them. - Designate: The developers who have expressed interest didn’t have commits, so Graham will sync with both of them to see how if can make it work. - OpenstackSDK: Monty might have missed the notice since they were traveling so Thierry will reach out to him to see if they want to take it again or has suggestions. - I18n: Ian Y. Choi expressed interest but couldn’t run because they were an election official. - {PowerVM,Win}stackers: The code and review activity was quiet and they missed election twice in a row so we proposed to remove them from project teams list and if they want to continue they can as a SIG. - Placement: we are trying to find someone to volunteer by reaching out to Placement and Nova team. We started discussing a change in the process for release names and the rest of that discussion carried over into office hours. I hope that I covered most of what we discussed, for the full meeting logs, you can find them here: http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-09-05-14.00.log.html Thanks! Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0

Invite Oleg Ovcharuk to join the Mistral Core Team
by András Kövi 10 Sep '19

10 Sep '19

I would like to invite Oleg Ovcharuk <vgvoleg(a)gmail.com> to join the Mistral Core Team. Oleg has been a very active and enthusiastic contributor to the project. He has definitely earned his way into our community. Thank you, Andras

4 4

[tc] weekly update
by Mohammed Naser 10 Sep '19

10 Sep '19

Hi everyone, Here’s the update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. # New Projects - os_murano (under openstack-ansible) # General Changes - We made a few improvements while reviewing the separation of goal definition from goal selection: https://review.opendev.org/#/c/677938/ Thanks! Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0

[charms] Retiring charm-neutron-api-genericswitch
by Corey Bryant 10 Sep '19

10 Sep '19

Hi All, I'm going to retire charm-neutron-api-genericswitch today as it is currently not maintained. I've already discussed and received approval to do so from the original author and the current charms PTL, so this serves as a more broad announcement. Thanks, Corey

1 0

[Horizon] Help making custom theme
by Amy Marrich 10 Sep '19

10 Sep '19

For the Grace Hopper Conference's Open Source Day we're doing a Horizon based workshop for OpenStack (running Devstack Pike). The end goal is to have the attendee teams create their own OpenStack theme supporting a humanitarian effort of their choice in a few hours. I've tried modifying the material theme thinking it would be the easiest route to go but that might not be the best way to go about this.:) I've been getting some assistance from e0ne in the Horizon channel and my logo now shows up on the login page, and I had already gotten the SITE_BRAND attributes and the theme itself to show up after changing the local_settings.py. If anyone has some tips or a tutorial somewhere it would be greatly appreciated and I will gladly put together a tutorial for the repo when done. Thanks! Amy (spotz)

3 6

[release][cyborg] os-acc status
by Thierry Carrez 10 Sep '19

10 Sep '19

Hi Cyborgs, One of your deliverables is the os-acc library. It has seen no change over this development cycle and therefore was not released at all in train. We have several options for this library now: 1- It's still very much alive and desired and just has exceptionally not seen much activity during this cycle. We should just cut a stable/train branch from the last release available (0.2.0) and continue in ussuri. 2- It's a valuable library, it just changes extremely rarely. We should make it independent from the release cycle and have it release at its own rhythm. 3- Development has stopped on this, and the library is not useful right now. We should retire this deliverable so that we do not build wrong expectations for our users. Please let us know which option fits the current status of os-acc. -- Thierry Carrez (ttx)

3 4

[placement][ptl][tc] Call for Placement PTL position
by Ghanshyam Mann 10 Sep '19

10 Sep '19

Hello Everyone, With Ussuri Cycle PTL election completed, we left with Placement project as leaderless[1]. In today TC meeting[2], we discussed the few possibilities and decided to reach out to the eligible candidates to serve the PTL position. We would like to know if anyone from Placement core team, Nova core team or PTL (as placement main consumer) of any other interested/related developer is interested to take the PTL position? [1] https://governance.openstack.org/election/results/ussuri/ptl.html [2] http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-09-05-14.00.log.htm… -TC (gmann)

5 8

OSA upgrading Xenial Queens to Bionic Rocky
by Grant Morley 10 Sep '19

10 Sep '19

Hi all, I was wondering if there was a guide for upgrading OpenStack Ansible from Ubuntu 16.04 Queens to Ubuntu 18.04 Rocky? I remember a long time ago there was an etherpad set up for upgrading from 14.04 -> 16.04 but I can't seem to find anything similar for going to 18.04. Annoyingly as we don't have lots of hardware, we are going to have to upgrade in place. If there are any guides that would be much appreciated. Many thanks. -- Grant Morley Cloud Lead, Civo Ltd www.civo.com <https://www.civo.com/>| Signup for an account! <https://www.civo.com/signup>

2 1

[neutron][vmware][vsphere] integration
by Ionut Biru 10 Sep '19

10 Sep '19

Hello guys, I'm trying to integrate openstack stein with an already running vmware vsphere cluster. All the documentation that I found explain how do it with distributed switches or port groups but currently in my setup, vmware is using Standard Network. Openstack Stein was deployed using OSA , neutron was configured using ovs and i configured the integrated_bridge to br-int. I tried first to deployed using linux-bridge but when I tried to deployed an instance, neutron returned that only ovs or dvs method is supported. Now when ovs when I'm deploying an instance with network, nova returns an error message: 2019-09-10 10:15:19.010 22443 ERROR nova.compute.manager [instance: d8d1cbb8-5c1c-4b98-9739-bea0668cfaa5] VimFaultException: An error occurred during host configuration. 2019-09-10 10:15:19.010 22443 ERROR nova.compute.manager [instance: d8d1cbb8-5c1c-4b98-9739-bea0668cfaa5] Faults: ['PlatformConfigFault'] How do you guys integrate neutron with vmware vsphere with standard network? Is there a driver that I need to use? -- Ionut Biru - https://fleio.com

1 0

Thank you Stackers for five amazing years!
by Chris Hoge 10 Sep '19

10 Sep '19

Hi everyone, After more than nine years working in cloud computing and on OpenStack, I've decided that it is time for a change and will be moving on from the OpenStack Foundation. For the last five years I've had the honor of helping to support this vibrant community, and I'm going to deeply miss being a part of it. OpenStack has been a central part of my life for so long that it's hard to imagine a work life without it. I'm proud to have helped in some small way to create a lasting project and community that has, and will continue to, transform how infrastructure is managed. September 12 will officially be my last day with the OpenStack Foundation. As I make the move away from my responsibilities, I'll be working with community members to help ensure continuity of my efforts. Thank you to everyone for building such an incredible community filled with talented, smart, funny, and kind people. You've built something special here, and we're all better for it. I'll still be involved with open source. If you ever want to get in touch, be it with questions about work I've been involved with or to talk about some exciting new tech or to just catch up over a tasty meal, I'm just a message away in all the usual places. Sincerely, Chris chris(a)hogepodge.com Twitter/IRC/everywhere else: @hogepodge

10 9

[keystone] cannot use 'openstack trust list' without admin role
by Francois Scheurer 10 Sep '19

10 Sep '19

Dear Keystone Experts, I have an issue with the openstack client in stage (using Rocky), using a user 'fsc' without 'admin' role and with password auth. 'openstack trust create/show' works. 'openstack trust list' is denied. But keystone policy.json says: "identity:create_trust": "user_id:%(trust.trustor_user_id)s", "identity:list_trusts": "", "identity:list_roles_for_trust": "", "identity:get_role_for_trust": "", "identity:delete_trust": "", "identity:get_trust": "", So "openstack list trusts" is always allowed. In keystone log (I replaced the uid's by names in the ouput below) I see that 'identity:list_trusts()' was actually granted but just after that a_*admin_required()*_ is getting checked and fails... I wonder why... There is also a flag*is_admin_project=True* in the rbac creds for some reason... Any clue? Many thanks in advance! Cheers Francois #openstack --os-cloud stage-fsc trust create --project fscproject --role creator fsc fsc #=> fail because of the names and policy rules, but using uid's it works openstack --os-cloud stage-fsc trust create --project aeac4b07d8b144178c43c65f29fa9dac --role 085180eeaf354426b01908cca8e82792 3e9b1a4fe95048a3b98fb5abebd44f6c 3e9b1a4fe95048a3b98fb5abebd44f6c +--------------------+----------------------------------+ | Field | Value | +--------------------+----------------------------------+ | deleted_at | None | | expires_at | None | | id | e74bcdf125e049c69c2e0ab1b182df5b | | impersonation | False | | project_id | fscproject | | redelegation_count | 0 | | remaining_uses | None | | roles | creator | | trustee_user_id | fsc | | trustor_user_id | fsc | +--------------------+----------------------------------+ openstack --os-cloud stage-fsc trust show e74bcdf125e049c69c2e0ab1b182df5b +--------------------+----------------------------------+ | Field | Value | +--------------------+----------------------------------+ | deleted_at | None | | expires_at | None | | id | e74bcdf125e049c69c2e0ab1b182df5b | | impersonation | False | | project_id | fscproject | | redelegation_count | 0 | | remaining_uses | None | | roles | creator | | trustee_user_id | fsc | | trustor_user_id | fsc | +--------------------+----------------------------------+ #this fails: openstack --os-cloud stage-fsc trust list *You are not authorized to perform the requested action: admin_required. (HTTP 403)*

3 3

[ironic] Ironic tempest jobs hitting retry_limit failures
by Clark Boylan 09 Sep '19

09 Sep '19

Hello Ironic, We've noticed that your tempest jobs have been hitting retry_limit failure recently. What this means is we attempted to run the job 3 times but each time the job failed due to "network" problems and Zuul eventually gave up. On further investigation I found that this is happening because the ironic tempest jobs are filling the root disk on rackspace nodes (which have a smaller root / + ephemeral drive mounted at /opt) with libvirt qcow2 images. This seems to cause ansible to fail to operate because it needs to write to /tmp and it thinks there is a "network" error. I've thrown my investigation into a bug for you [0]. It would be great if you could take a look at this as we are effectively spinning our wheels for about 9 hours every time this happens. I did hold the node I used to investigate. If you'd like to dig in yourselves just ask the infra team for access to nodepool node ubuntu-bionic-rax-ord-0011007873. Finally, to help debug these issues in the future I've started adding a cleanup-run playbook [1] which should give us network and disk info (can be expanded if necessary too) for every job when it is done running. Even if the disk is full. [0] https://storyboard.openstack.org/#!/story/2006520 [1] https://review.opendev.org/#/c/681100/ Clark

1 0

[devstack][qa][python3] "also install the Python 2 dev library" - still needed?
by Peter Penchev 09 Sep '19

09 Sep '19

Hi, When devstack's `setup_dev_lib` function is invoked and USE_PYTHON3 has been specified, this function tries to also install the development library for Python 2.x, I guess just in case some package has not declared proper Python 3 support or something. It then proceeds to install the Python 3 version of the library and all its dependencies. Unfortunately there is a problem with that, and specifically with script files installed in the system's executable files directory, e.g. /usr/local/bin. The problem appears when some Python library has already been installed for Python 3 (and has installed its script files), but is now installed for Python 2 (overwriting the script files) and is then not forcefully reinstalled for Python 3, since it is already present. Thus, the script files are last modified by the Python 2 library installation and they have a hashbang line saying `python2.x` - so if something then tries to execute them, they will run and use modules and libraries for Python 2 only. We experienced this problem when running the cinderlib tests from Cinder's `playbooks/cinderlib-run.yaml` file - it finds a unit2 executable (installed by the unittest2 library) and runs it, hoping that unit2 will be able to discover and collect the cinderlib tests and load the cinderlib modules. However, since unittest2 has last been installed as a Python 2 library, unit2 runs with Python 2 and fails to locate the cinderlib modules. (Yes, we know that there are other ways to run the cinderlib tests; this message is about the problem exposed by this way of running them) The obvious solution would be to instruct the Python 2 pip to not install script (or other shared) files at all; unfortunately, https://github.com/pypa/pip/issues/3980 ("Option to exclude scripts on install"), detailing a very similar use case ("need it installed for Python 2, but want to use it with Python 3") has been open for almost exactly three years now with no progress. I wonder if I could try to help, but even if this issue is resolved, there will be some time before OpenStack can actually depend on a recent enough version of pip. A horrible workaround would be to find the binary directory before installing the Python 2 library (using something like `pip3.7 show somepackage` and then running some heuristics on the "Location" field), tar'ing it up and then restoring it... but I don't know if I even want to think about this. Another possible way forward would be to consider whether we still want the Python 2 libraries installed - is OpenStack's Python 3 transition reached a far enough stage to assume that any projects that still require Python 2 *and* fail to declare their Python 2 dependencies properly are buggy? To be honest, this seems the most reasonable path for me - drop the "also install the Python 2 libs" code and see what happens. I could try to make this change in a couple of test runs in our third-party Cinder CI system and see if something breaks. Here is a breakdown of what happens, with links to the log of the StorPool third-party CI system for Cinder: https://spfactory.storpool.com/logs/80/639180/35/check/cinder-storpool-temp… `stack.sh` invokes `pip_install` for `os-testr` https://spfactory.storpool.com/logs/80/639180/35/check/cinder-storpool-temp… `pip_install` sees that we want a Python 3 installation and invokes `pip3.7` to install os-testr. https://spfactory.storpool.com/logs/80/639180/35/check/cinder-storpool-temp… `pip3.7` wants to install `unittest2` https://spfactory.storpool.com/logs/80/639180/35/check/cinder-storpool-temp… `pip3.7` has installed `unittest2` - now `/usr/local/bin/unit2` has a hashbang line saying `python3.7` Now this is where it gets, uhm, interesting: https://spfactory.storpool.com/logs/80/639180/35/check/cinder-storpool-temp… `setup_dev_lib` is invoked for `os-brick` https://spfactory.storpool.com/logs/80/639180/35/check/cinder-storpool-temp… `setup_dev_lib`, seeing that we really want a Python 3 installation, decides to install `os-brick` for Python 2 just in case. https://spfactory.storpool.com/logs/80/639180/35/check/cinder-storpool-temp… `pip2.7` is invoked to install `os-brick` and its dependencies. https://spfactory.storpool.com/logs/80/639180/35/check/cinder-storpool-temp… `pip2.7` decides it wants to install `unittest2`, too. https://spfactory.storpool.com/logs/80/639180/35/check/cinder-storpool-temp… `pip2.7` has installed `unittest2`, and now `/usr/local/bin/unit2` has a hasbang line saying `python2.7` https://spfactory.storpool.com/logs/80/639180/35/check/cinder-storpool-temp… `setup_dev_lib` turns the Python 3 flag back on. https://spfactory.storpool.com/logs/80/639180/35/check/cinder-storpool-temp… `pip3.7` is invoked to install `os-brick` https://spfactory.storpool.com/logs/80/639180/35/check/cinder-storpool-temp… `pip3.7` decides (correctly) that it has already installed `unittest2`, so (only partially correctly) it does not need to install it again. Thus `/usr/local/bin/unit2` is left with a hashbang line saying `python2.7`. Thanks for reading this far, I guess :) G'luck, Peter

4 5

Bug Deputy September 2 - September 9
by Nate Johnston 09 Sep '19

09 Sep '19

Neutrinos, Here is the bug deputy report for this past week. It was an exciting week of CI problems; thanks to everyone who pitched in to get us past those thorny issues. I would call out specifically the two bugs rated as High that have no assignee yet; they are both gate related - one for Neutron, and the other affecting the Patrole project. There is also one bug left Untriaged because I was unable to validate the bug; I would appreciate a triaging look if you can. Thanks! Nate ---- Critical - https://bugs.launchpad.net/bugs/1842482 "test_get_devices_info_veth_different_namespaces" fails because veth1_1 interface has a link device in the same namespace Status: Fix Committed (slaweq) https://review.opendev.org/680001 - https://bugs.launchpad.net/bugs/1842517 neutron-sanity-check command fails if netdev datapath is used Status: In Progress (deepak.tiwari) No change registered in LP bug - https://bugs.launchpad.net/bugs/1842657 Job networking-ovn-tempest-dsvm-ovs-release is failing 100% times Status: Fix Committed (maciej.josefczyk) https://review.opendev.org/661065 - https://bugs.launchpad.net/bugs/1842659 Funtional tests of start and restart services failing 100% times Status: Fix Committed (slaweq) https://review.opendev.org/680001 High - https://bugs.launchpad.net/bugs/1843285 Trunk scenario test test_subport_connectivity failing with iptables_hybrid fw driver Status: Unassigned - https://bugs.launchpad.net/bugs/1842666 Bulk port creation with supplied security group also adds default security group Status: In Progress (njohnston) https://review.opendev.org/679852 - https://bugs.launchpad.net/bugs/1843025 FWaaS v2 fails to add ICMPv6 rules via horizon Status: In Progress (haleyb) https://review.opendev.org/680753 - https://bugs.launchpad.net/bugs/1843282 Rally CI not working since jsonschema version bump Status: Fix Committed (ralonsoh) https://review.opendev.org/681001 - https://bugs.launchpad.net/bugs/1843290 Remove network flavor profile fails Status: Unassigned Note: Currently breaking the gate for the Patrole project Medium - https://bugs.launchpad.net/bugs/1842327 Report in logs when FIP associate and disassociate Status: In progress (ralonsoh) https://review.opendev.org/680976 Low - https://bugs.launchpad.net/bugs/1842934 multicast scenario test failing when guest image don't have python3 installed Status: In Progress (slaweq) https://review.opendev.org/680428 - https://bugs.launchpad.net/bugs/1842937 Some ports assigned to routers don't have the correspondent routerport register Status: In Progress (ralonsoh) No change registered in LP bug - https://bugs.launchpad.net/bugs/1843269 Nova notifier called even if set to False Status: In Progress (haleyb) https://review.opendev.org/681016 RFE - https://bugs.launchpad.net/bugs/1843218 allow to create record on default zone from tenants Untriaged - https://bugs.launchpad.net/bugs/1843211 network-ip-availabilities' result is not correct when the subnet has no allocation-pool Status: Unassigned

1 1

[edge] Edge whitepaper and tutorial authors needed
by Ildiko Vancsa 09 Sep '19

09 Sep '19

Hi, I’m reaching out to point you to two mail threads on the edge-computing mailing list. The edge working group is looking into writing up a second whitepaper with a few detailed use cases and information about the reference architecture work the group has been doing. If you are interested in this work please __reach out to me or check out this mail thread__: http://lists.openstack.org/pipermail/edge-computing/2019-September/000632.h… The other work item is writing up edge tutorials about frameworks to a German magazine. __This is a short deadline activity, please reach out to me if you are interested in participating.__ For further information please see this mail thread: http://lists.openstack.org/pipermail/edge-computing/2019-September/000633.h… Please let me know if you have questions to any of the above. Thanks, Ildikó

1 0

[nova] Offline Installation of Openstack
by Premdeep S 09 Sep '19

09 Sep '19

Hi Team, Requesting your help on below. We have a requirement to setup Openstack in an isolated infra. We will not be provided with Internet. How can we set it up? 1. Can we have a local repository (Rocky, Universal, etc)created? If so how do we manage it? 2. We have noticed lot of package dependencies while setting up Openstack Infra, so will creating a local repository help in an implementation when we do not have an internet. What is the success rate? Thanks Prem

2 2

[manila][ops] Shanghai Forum - Manila Topic Planning
by Tom Barron 09 Sep '19

09 Sep '19

As mentioned several times in the Manila Community Meeting, we have posted an etherpad to brainstorm and gauge interest in topics for the Forum at the upcoming OpenInfra Summit in Shanghai. The point of the Forum sesssions is to get feedback from operators and users on things that need fixing, improvements and enhancements, and more generally about the strategic direction for Manila. So please take a look and update this etherpad with topic ideas and indicate your interest in topics already present if you have an interest in Manila. It doesn't matter whether you contribute to the project or not, or whether you will yourself be attending the Forum: https://etherpad.openstack.org/p/manila-shanghai-forum-brainstorming We will review this etherpad in our community meeting at 1500 UTC on 19 September in #openstack-meeting-alt on Freenode, one day before the Forum proposal deadline. Please feel free to join that meeting to discuss, and in any case please add to the brainstorming deadline before then. Cheers, -- Tom Barron

1 0

[keystone] Pre-feature-freeze update
by Colleen Murphy 09 Sep '19

09 Sep '19

I won't be writing a team report since I'm still figuring out which way is up after a week in the desert, but with feature freeze next week I wanted to give a status update on all the in-flight work that is due next week: * System Scope and Default Roles All documented scope[1] and role[2] migrations are in progress. Some are closer to done than others. Since enforce_scope cannot be set to true in keystone.conf until all of them are completed, and since leaving deprecation warnings in the logs for more than two cycles is a very undesirable operator experience, it's essential we complete these by next week. * Application Credential Access Rules This implementation[3] for keystone has been completed for months but the last few patches in the stack are lacking reviews. Client support has been proposed but with the final client release happening next week we will likely not land it until next cycle. * Resource Options and Immutable Resources Resource options[4] and immutable resources[5] are intertwined and the finishing touches are still being applied. Hope to have this completed early next week. * Federated Attributes for Users Support for federated attributes for users[6] is passing CI but needs reviews, it's unclear to me how much has changed since those patches were originally proposed two years ago so it's unfortunate that we're only left with a week to look at them. * Expiring Group Membership There is only a partial implementation proposed for expiring group membership[7] and neither patch is passing CI. This seems to have effectively missed the feature proposal freeze deadline which was a few weeks ago and will not likely make it in this cycle. * CI After skimming the meeting logs I saw the unit test timeout problem was discussed and a temporary workaround was proposed[8]. This sounded like a great idea but it seems that no one implemented it, so I did[9]. Unfortunately this will conflict with all the system-scope/default-roles patches in flight. With how many changes need to go in and how slow it will be with all of them needing to be rechecked and continually making the problem even worse, I propose we go ahead and merge the workaround ASAP and update all the in-flight changes to move the protection tests to the new location. It also appears that the non-voting federation CI broke recently, this will hopefully be fixed by updating the opensuse nodeset[10]. [1] https://bugs.launchpad.net/keystone/+bugs?field.tag=system-scope [2] https://bugs.launchpad.net/keystone/+bugs?field.tag=default-roles [3] https://review.opendev.org/#/q/topic:bp/whitelist-extension-for-app-creds [4] https://review.opendev.org/678322 [5] https://review.opendev.org/#/q/topic:immutable-resources [6] https://review.opendev.org/#/q/topic:bp/support-federated-attr [7] https://review.opendev.org/#/q/topic:bug/1809116 [8] http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-08-27-1… [9]https://review.opendev.org/680788 [10] https://review.opendev.org/680799 Colleen

2 2