September 2019 - openstack-discuss

Long, Slow Zuul Queues and Why They Happen
by Clark Boylan 23 Sep '19

23 Sep '19

Hello, We've been fielding a fair bit of questions and suggestions around Zuul's long change (and job) queues over the last week or so. As a result I tried to put a quick FAQ type document [0] on how we schedule jobs, why we schedule that way, and how we can improve the long queues. Hoping that gives us all a better understanding of why were are in the current situation and ideas on how we can help to improve things. [0] https://docs.openstack.org/infra/manual/testing.html#why-are-jobs-for-chang… Thanks, Clark

3 4

[neutron][drivers][ironic] FFE request - Use openstacksdk for ironic notifiers
by Riccardo Pittau 23 Sep '19

23 Sep '19

Hello fellow openstackers, I'd like to open an FFE request to convert the ironic events notifier from the current ironicclient to openstacksdk with the change https://review.opendev.org/682040 This requires also a bump of the versions of mock and openstacksdk in lower-constraints, included in the CR. The change has been tested in a devstack environment and passes the zuul checks. Thank you! Riccardo Pittau rpittau||elfosardo

4 5

[goals][IPv6-Only Deployments and Testing] Week R-3 Update
by Ghanshyam Mann 23 Sep '19

23 Sep '19

Hello Everyone, Below is the latest updated on IPv6 goal. All the projects have the ipv6 job patch proposed now. Next step is to review then as per mentioned guidelines below or help in debugging the failure. I saw tests are failing for the few projects which need debugging and help from the project team. Summary: The projects still need to prepare the IPv6 job: * None The projects waiting for IPv6 job patch to merge: If patch is failing, help me to debug that otherwise review and merge. * Barbican * Blazar * Cyborg * Tricircle * Vitrage * Zaqar * Glance * Monasca * Neutron * Qinling * Sahara * Searchlight * Senlin * Tacker * Ec2-Api * Freezer * Heat * Ironic * Karbor * Kuryr * Magnum * Masakari * Mistral * Murano * Octavia (johnsom is working on this and will take over the base patch) The projects have merged the IPv6 jobs: * Designate * Murano * Trove * Cloudkitty * Congress * Horizon * Keystone * Nova * Placement * Solum * Telemetry * Watcher * Zun * Cinder * Manila * Swift The projects do not need the IPv6 job (CLI, lib, deployment projects etc ): I have marked the tasks for below project as invalid. * Adjutant * Documentation * I18n * Infrastructure * Kolla * Loci * Openstack Charms * Openstack-Chef * Openstack-Helm * Openstackansible * Openstackclient * Openstacksdk * Oslo * Packaging-Rpm * Powervmstackers * Puppet Openstack * Rally * Release Management * Requirements * Storlets * Tripleo * Winstackers Storyboard: ========= - https://storyboard.openstack.org/#!/story/2005477 IPv6 missing support found: ===================== 1. https://review.opendev.org/#/c/673397/ 2. https://review.opendev.org/#/c/673449/ 3. https://review.opendev.org/#/c/677524/ There are few more but need to be tracked. How you can help: ============== - Each project needs to look for and review the ipv6 job patch. - Verify it works fine on ipv6 and no ipv4 used in conf etc - Any other specific scenario needs to be added as part of project IPv6 verification. - Help on debugging and fix the bug in IPv6 job is failing. Everything related to this goal can be found under this topic: Topic: https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(stat… How to define and run new IPv6 Job on project side: ======================================= - I prepared a wiki page to describe this section - https://wiki.openstack.org/wiki/Goal-IPv6-only-deployments-and-testing Review suggestion: ============== - Main goal of these jobs will be whether your service is able to listen on IPv6 and can communicate to any other services either OpenStack or DB or rabbitmq etc on IPv6 or not. So check your proposed job with that point of view. If anything missing, comment on patch. - One example was - I missed to configure novnc address to IPv6- https://review.opendev.org/#/c/672493/ - base script as part of 'devstack-tempest-ipv6' will do basic checks for endpoints on IPv6 and some devstack var setting. But if your project needs more specific verification then it can be added in project side job as post-run playbooks as described in wiki page[1]. [1] https://wiki.openstack.org/wiki/Goal-IPv6-only-deployments-and-testing

1 0

[neutron] bug deputy report (the week of 2019-09-16)
by Takashi Yamamoto 23 Sep '19

23 Sep '19

here's the list of what we got reported in the week. features (nova bp follow-up) https://bugs.launchpad.net/neutron/+bug/1844131 Boot a VM with an unaddressed port High https://bugs.launchpad.net/neutron/+bug/1844168 [L3] TooManyExternalNetworks: More than one external network exists. A proposed fix: https://review.opendev.org/#/c/682418/ Medium https://bugs.launchpad.net/neutron/+bug/1844124 Not possible to change fixed-ips if port is on routed provider network A proposed fix: https://review.opendev.org/#/c/682489/ https://bugs.launchpad.net/neutron/+bug/1844516 [neutron-tempest-plugin] SSH timeout exceptions when executing remote commands A proposed fix: https://review.opendev.org/#/c/682864/ https://bugs.launchpad.net/neutron/+bug/1844688 "radvd" daemon does not work by default in some containers A proposed fix: https://review.opendev.org/#/c/683207/ Low https://bugs.launchpad.net/neutron/+bug/1844171 Configuration parameter missing at "Configure the layer-3 agent" A merged fix: https://review.opendev.org/#/c/682645/ https://bugs.launchpad.net/neutron/+bug/1844607 log error when create neutron port with wrong subnet A proposed fix: https://review.opendev.org/#/c/683273/ Incomplete https://bugs.launchpad.net/neutron/+bug/1844123 Unable to trigger IPv6 Prefix Delegation https://bugs.launchpad.net/neutron/+bug/1844595 openstackNova(Rocky)--chinese incorrect codes for db character error https://bugs.launchpad.net/neutron/+bug/1844915 Duplicate packets with two networks connected by router Invalid https://bugs.launchpad.net/neutron/+bug/1844097 Redundant ipv6 address(SLAAC/DHCPv6 stateless) created for port It was an intended behavior and the rationale was explained to the submitter.

1 0

zun-ui 4.0.0.0rc1 (train)
by no-reply＠openstack.org 23 Sep '19

23 Sep '19

Hello everyone, A new release candidate for zun-ui for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/zun-ui/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/zun-ui/log/?h=stable/train Release notes for zun-ui can be found at: https://docs.openstack.org/releasenotes/zun-ui/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/zun-ui/+bugs and tag it *train-rc-potential* to bring it to the zun-ui release crew's attention.

1 0

kuryr-libnetwork 4.0.0.0rc1 (train)
by no-reply＠openstack.org 23 Sep '19

23 Sep '19

Hello everyone, A new release candidate for kuryr-libnetwork for the end of the Train cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/kuryr-libnetwork/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Train release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/train release branch at: https://opendev.org/openstack/kuryr-libnetwork/log/?h=stable/train Release notes for kuryr-libnetwork can be found at: https://docs.openstack.org/releasenotes/kuryr-libnetwork/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/kuryr-libnetwork/+bugs and tag it *train-rc-potential* to bring it to the kuryr-libnetwork release crew's attention.

1 0

Outreachy Application Deadline - Call for mentors and projects
by Samuel de Medeiros Queiroz 21 Sep '19

21 Sep '19

Hi everyone! Outreachy <https://www.outreachy.org/> helps people from underrepresented groups get involved in free and open source software by matching interns with established mentors in the upstream communities. OpenStack is a participating organization in the Outreachy Dec 2019 to Mar 2020 round. If you're interested to be a mentor, please register as a mentor in the Outreachy website and publish your project ideas. According to this round's schedule <https://www.outreachy.org/docs/applicant/#outreachy-schedule>, the initial application is due next week: - *Sept. 24, 2019 at 4pm UTC Initial application deadline * - *Nov. 5, 2019 at 4pm UTC Final application deadline* It is important to get projects submitted *as soon as possible* so that applicants can sign up before the *Sept. 24 deadline*. Once signed up, they will have between *Oct. 1, 2019 to Nov. 5, 2019 to contribute to the projects*. If you have any questions about becoming a mentor or want to sponsor an intern, please contact me (samueldmq(a)gmail.com) or Mahati Chamarthy ( mahati.chamarthy(a)gmail.com). Thank you, Samuel de Medeiros Queiroz

3 2

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

20 Sep '19

# Keystone Team Update - Week of 16 September 2019 ## News ### RC1 Status Even after discovering some gaps in our policy migrations we managed to quickly cover them and are on track to close all our RC1-targeted bugs[1] on time! [1] https://launchpad.net/keystone/+milestone/train-rc1 ## Office Hours When there are topics to cover, the keystone team holds office hours on Tuesdays at 17:00 UTC. No office hours next week due to lack of topics. 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 32 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 58 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ## Milestone Outlook https://releases.openstack.org/train/schedule.html We're on target to release RC1 next week. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

[ironic] Tips on testing custom hardware manager?
by Jason Anderson 20 Sep '19

20 Sep '19

Hi all, I am hoping to get some tips on how to test out a custom hardware manager. One of my colleagues is working on a project that involves implementing a custom in-band cleaning step, which we are implementing by creating our own ramdisk image that includes an extra library, which is necessary for the clean step. We already have created the image and ensured it has IPA installed and that all seems to work fine (in that, it executes on the node and we see our code running--and failing!) The issue we are having is that we encounter some issues in our fully integrated environment (such as the provisioning network having different networking rules) and replicating this environment in some local development context is very difficult. Right now our workflow is really onerous as a result: my colleague has to rebuild the ramdisk image, re-upload it to Glance, update the test Ironic node to reference that image, then perform a rebuild. One cycle of this takes a while as you can imagine. I was wondering: is it possible to somehow interrupt or give a larger window for some interactive debugging? The amount of time we have to run some quick tests/debugging is small because the deploy will time out and cancel itself or it will proceed and fail. Thusfar I haven't found any documentation or written experience on this admittedly niche task. Perhaps somebody has already gone down this road and can advise on some tips? It would be much appreciated! Cheers, -- Jason Anderson Chameleon DevOps Lead Consortium for Advanced Science and Engineering, The University of Chicago Mathematics & Computer Science Division, Argonne National Laboratory

2 2

[i18n][tc] The future of I18n
by Thierry Carrez 20 Sep '19

20 Sep '19

Hi! The I18n project team had no PTL candidates for Ussuri, so the TC needs to decide what to do with it. It just happens that Ian kindly volunteered to be an election official, and therefore could not technically run for I18n PTL. So if Ian is still up for taking it, we could just go and appoint him. That said, I18n evolved a lot, to the point where it might fit the SIG profile better than the project team profile. As a reminder, project teams are responsible for producing OpenStack-the-software, and since they are all integral in the production of the software that we want to release on a time-based schedule, they come with a number of mandatory tasks (like designating a PTL every 6 months). SIGs (special interest groups) are OpenStack teams that work on a mission that is not directly producing a piece of the OpenStack release. SIG members are bound by their mission, rather than by a specific OpenStack release deliverable. There is no mandatory task, as it is OK if the group goes dormant for a while. The I18n team regroups translators, with an interest of making OpenStack (in general, not just the software) more accessible to non-English speakers. They currently try to translate the OpenStack user survey, the Horizon dashboard messages, and key documentation. It could still continue as a project team (since it still produces Horizon translations), but I'd argue that at this point it is not what defines them. The fact that they are translators is what defines them, which IMHO makes them fit the SIG profile better than the project team profile. They can totally continue proposing translation files for Horizon as a I18n SIG, so there would be no technical difference. Just less mandatory tasks for the team. Thoughts ? -- Thierry Carrez (ttx)

4 4

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

20 Sep '19

On Fri, Sep 20, 2019 at 04:46:49PM +0000, zuul(a)openstack.org wrote: > Build failed. > > - tag-releases https://zuul.opendev.org/t/openstack/build/9413e62eae174733a7f577c6090c3059 : TIMED_OUT in 30m 56s > - publish-tox-docs-static https://zuul.opendev.org/t/openstack/build/None : SKIPPED > The tagging job failed here because I tried to include too many new branch creation requests in one patch. This job will be reenqueued so the processing runs again. The automation is smart enough to skip over the ones that have already been branched, so it should be able to just pick up where it left off. This was half way through processing the python-designateclient branching. The branch was created, and one of the two automatic stable patches were submitted before the job was killed. I have manually submitted the one that was missed here: https://review.opendev.org/#/c/683592/ Sean

1 0

[RelMgmt] Moving release team meeting for the week of Sept 23
by Sean McGinnis 20 Sep '19

20 Sep '19

Hey everyone, Due to travel conflicts next week, rather than cancelling the weekly meeting during the RC week we will be moving it to Friday at 15:00 UTC. This is a one time change of the meeting time. Afterwards we will return to our normal schedule of Thursday, 16:00 UTC. Let me know if there are any questions or concerns. Sean

1 0

A reminder about our upstream backport policy
by Matt Riedemann 20 Sep '19

20 Sep '19

I have noticed several stable/rocky-only docs fixes proposed lately across several projects and when I review them I find that what is being fixed is still broken on master and stable/stein, meaning once someone upgrades from rocky to stein or train they are just going to have to re-fix that same issue. All of the developers are from the same vendor who is targeting a rocky-based release, and while it's great that they put an emphasis on using the upstream docs for product code and work on fixing those docs upstream, we do have backport processes in place for working on stable branches, in this case specifically: https://docs.openstack.org/project-team-guide/stable-branches.html#processes So let's please follow the upstream process so we don't have to continue to fix the same things each release because backports weren't done properly the first time. -- Thanks, Matt

1 0

[sahara] Sahara meeting frequency change
by Jeremy Freudberg 20 Sep '19

20 Sep '19

For any interested parties not already aware, the Sahara meeting now takes place every two weeks instead of every week. The next meeting will take place October 3, 2019. More information and the latest ICS file reflecting this change are found here: http://eavesdrop.openstack.org/#OpenStack_Data_Processing_(Sahara)_Team_Mee… Thanks, Jeremy

1 0

[ops] Shanghai Forum / Ops Day sessions
by Erik McCormick 20 Sep '19

20 Sep '19

Greetings! We are coming up on the Shanghai Summit and need to plan out a few sessions for forum submissions (yeah I know, late as always). We are also trying to see if there's enough traction to do an Ops day on Thursday after the summit. This is a bit freeform, but if there are enough attendees interested, we can make it happen. Please visit the following etherpad and suggest topics for both. +1 those you like the most. We will submit the forum sessions on Friday so there's not a lot of time for that part. Things for the Ops day can go on being entered until that day. https://etherpad.openstack.org/p/PVG-OPS-Forum-Brainstorming Thanks, Erik

1 1

RE: [cinder][FFE] Feature Freeze Exceptions
by Ryan.Liang＠dell.com 20 Sep '19

20 Sep '19

Sorry. Sending to the mailing list. Hi, I’d like to request FFE for the following Cinder Unity driver review: Unity: Add replication support. https://review.opendev.org/#/c/633451/ This change is limited to our Unity driver. Thanks, -Ryan From: Sean McGinnis <sean.mcginnis(a)gmail.com> Sent: Friday, September 20, 2019 9:02 PM To: Liang, Ryan Cc: Jay Bryant; Sun, Hao; Karthik, Rajini Subject: Re: [cinder][FFE] Feature Freeze Exceptions [EXTERNAL EMAIL] Hey Ryan, I think that should be fine, but you need to post this to the mailing list, not directly to Jay. Sean On Fri, Sep 20, 2019 at 1:13 AM <Ryan.Liang(a)dell.com<mailto:Ryan.Liang@dell.com>> wrote: Hi Jay and Sean, I’d like to request FFE for the following Cinder Unity driver review: Unity: Add replication support. https://review.opendev.org/#/c/633451/ This change is limited to our Unity driver. Thanks, -Ryan

1 0

[kolla] Kayobe Train planning meeting
by Mark Goddard 20 Sep '19

20 Sep '19

Hi, Just as the rest of the world is wrapping up the Train release, we find ourselves having just released Stein and starting on Train development. Given the timing of CentOS 8 which we intend to support in the kolla Train release, we have some time to do some feature development in kayobe. I've set up a Doodle poll [1] with two hour slots next week to plan the next release. [1] https://doodle.com/poll/y7fakbhbkfx5hqyk Cheers, Mark

1 2

[openstack-dev][cinder] question on cinder-volume A/A configuration
by Chen CH Ji 20 Sep '19

20 Sep '19

3 2

[oslo] run outlasted interval
by Ignazio Cassano 20 Sep '19

20 Sep '19

Hello, I have an openstack queens installation on centos 7 and starting from last night I got some warnings in several service: nova conductor reports: 2019-09-19 17:37:54.091 161110 WARNING oslo.service.loopingcall [-] Function 'nova.servicegroup.drivers.db.DbDriver._report_state' run outlasted interval by 29.88 sec 2019-09-19 17:37:54.092 161108 WARNING oslo.service.loopingcall [-] Function 'nova.servicegroup.drivers.db.DbDriver._report_state' run outlasted interval by 29.88 sec 2019-09-19 17:37:54.093 161118 WARNING oslo.service.loopingcall [-] Function 'nova.servicegroup.drivers.db.DbDriver._report_state' run outlasted interval by 29.88 sec 2019-09-19 17:37:54.095 161116 WARNING oslo.service.loopingcall [-] Function 'nova.servicegroup.drivers.db.DbDriver._report_state' run outlasted interval by 29.88 sec 2019-09-19 17:37:54.096 161109 WARNING oslo.service.loopingcall [-] Function 'nova.servicegroup.drivers.db.DbDriver._report_state' run outlasted interval by 29.88 sec 2019-09-19 17:37:54.097 161107 WARNING oslo.service.loopingcall [-] Function 'nova.servicegroup.drivers.db.DbDriver._report_state' run outlasted interval by 29.88 sec openvswitch agent reports: 019-09-19 17:16:14.499 26115 WARNING oslo.service.loopingcall [-] Function 'neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent.OVSNeutronAgent._report_state' run outlasted interval by 3.57 sec 2019-09-19 17:23:44.200 26115 WARNING oslo.service.loopingcall [-] Function 'neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent.OVSNeutronAgent._report_state' run outlasted interval by 29.71 sec 2019-09-19 17:37:54.077 26115 WARNING oslo.service.loopingcall [-] Function 'neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent.OVSNeutronAgent._report_state' run outlasted interval by 9.91 sec Please, anyone could help me ? Regards Ignazio

3 5

[tacker] Feature Freeze Exception Request - Add VNF packages support
by Patil, Tushar 19 Sep '19

19 Sep '19

Hi Dharmendra and all Core reviewers In train cycle ,we are committed to implement spec “VNF packages support for VNF onboarding” [1]. All patches [2] are uploaded on the gerrit and code review is in progress but as we have dependency on tosca-parser library, patches are not yet merged. Now, tosca-parser library new version 1.6.0. is released but we are waiting for patch [3] to merge which will update the constraints of tosca-parser to 1.6.0 in requirements project. Once that happens, we will make changes to the tacker patch [4] to update the lower constraints of tosca-parser to 1.6.0 which will run all functional and unit tests added for this feature successfully on the CI job. I would like to request feature freeze exception for “VNF packages support for VNF onboarding” [1]. We will make sure all the review comments on the patches will be fixed promptly so that we can merge them as soon as possible. [1] : https://review.opendev.org/#/c/582930/ [2] : https://review.opendev.org/#/q/topic:bp/tosca-csar-mgmt-driver+(status:open… [3] : https://review.opendev.org/#/c/681819/ [4]: https://review.opendev.org/#/c/675600/ Thanks, tpatil Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.

2 2

[tripleo][ci] gate jobs killed / reset
by Wesley Hayutin 19 Sep '19

19 Sep '19

Greetings, The zuul jobs in the TripleO gate queue were put out of their misery approximately at 20:14 UTC Sept 17 2019. The TripleO jobs were timing out [1] and causing the gate queue to be delayed about 24 hours [2]. We are hoping a revert [3] will restore TripleO jobs back to their usual run times. Please hold off on any rechecks or workflowing patches until [3] is merged and the status on #tripleo is no longer "RED" We appreciate your patience while we work through this issue, the jobs that were in the gate will be restored once we have confirmed and verified the solution. Thank you [1] https://bugs.launchpad.net/tripleo/+bug/1844446 [2] http://dashboard-ci.tripleo.org/d/YRJtmtNWk/cockpit?orgId=1&fullscreen&pane… [3] https://review.opendev.org/#/c/682729/

2 4

[release] Release countdown for week R-3, September 23-27
by Sean McGinnis 19 Sep '19

19 Sep '19

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, September 26th. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/train branch will be cut. This branch will track the Train release. Once stable/train has been created, master will will be ready to switch to Ussuri development. While master will no longer be feature-frozen, please prioritize any work necessary for completing Train plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/train branch before a new release candidate can be proposed. Actions --------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from master. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/train branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from master (which will technically then be Ussuri) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any Train release so far. 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

[tripleo] TripleO CI Summary: Sprint 36
by Rafael Folco 19 Sep '19

19 Sep '19

Greetings, The TripleO CI team has just completed Sprint 36 / Unified Sprint 15 (Aug 29 thru Sep 18). The following is a summary of completed work during this sprint cycle: - Addressed issues for scenario{001,002} jobs for RHEL8 in the periodic pipeline. RHEL 8 scen003, scen004 have CIX issues and are being worked on by the ruck/rovers. - Merged multi-arch container tagging support and implemented changes in the promoter code to push manifests with annotated metadata for architecture in addition to the arch tagged containers strategy. - Implemented the provisioning and staging promoter setup to an RDO job for testing changes in the promoter server. Next sprint will close-out the tests for the staging promotion workflow. The planned work for the next sprint [1] are: - Complete the manifest implementation with a test strategy for not breaking promotion workflow. - Design and implement tests for verifying a full promotion workflow running on the staging environment. - Design CI jobs in zuul to build and run tests against ceph-ansible and podman pull requests in github. - Train release branching preparation work. - Prepare CentOS8 node for upcoming distro release support across TripleO CI jobs. The Ruck and Rover for this sprint are Arx Cruz (arxcruz) and Sorin Sbarnea (zbr). 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 are being tracked in etherpad [2]. Thanks, rfolco [1] https://tree.taiga.io/project/tripleo-ci-board/taskboard/unified-sprint-16 [2] https://etherpad.openstack.org/p/ruckroversprint16

1 0

[all][release] Proposed release schedule for Ussuri
by Sean McGinnis 19 Sep '19

19 Sep '19

Hey everyone, Now that we have a date for the next event [0], it might be a good time to finalize the release cycle schedule for the Ussuri release. I have put up a proposal for the schedule here: https://review.opendev.org/#/c/679822/ Please take a look and give any feedback if you see any issues with where the milestone dates align with any major holidays or other external factors that we should consider. For your viewing convenience, here is the rendered output from the docs job: https://openstack.fortnebula.com:13808/v1/AUTH_e8fd161dc34c421a979a9e6421f8… Thanks! Sean [0] http://lists.openstack.org/pipermail/foundation/2019-September/002794.html

1 0

[Security] Security SIG Newsletter
by Gage Hugo 19 Sep '19

19 Sep '19

Past couple weeks were a bit slow, but this week has some updates! #Date: 19 Sept 2019 - Security SIG Meeting Info: http://eavesdrop.openstack.org/#Security_SIG_meeting - Weekly on Thursday at 1500 UTC in #openstack-meeting - Agenda: https://etherpad.openstack.org/p/security-agenda - https://security.openstack.org/ - https://wiki.openstack.org/wiki/Security-SIG #Meeting Notes - Summary: http://eavesdrop.openstack.org/meetings/security/2019/security.2019-09-19-1… - Discussed the recently public big here: https://bugs.launchpad.net/horizon/+bug/1842930 - Current path forward is to clear up documentation to warn about this and provide info about caching settings. - nickthetait is currently working on https://bugs.launchpad.net/ossp-security-documentation/+bug/1703353 - Will create a page describing the usage and functionality of the audit middleware & CADF notifications #VMT Reports - A full list of publicly marked security issues can be found here: https://bugs.launchpad.net/ossa/ - Deleted user still can delete volumes in Horizon: https://bugs.launchpad.net/horizon/+bug/1842930

1 0

[cinder][FFE] Feature Freeze Exceptions
by Rajat Dhasmana 19 Sep '19

19 Sep '19

Hi, I would like to request FFE for the following cinder feature : - Untyped to Default Volume Type: https://review.opendev.org/#/c/639180 <https://review.opendev.org/#/c/639180/39> Thanks and Regards Rajat Dhasmana

2 3

[ironic] FFE: PXE boot retry
by Dmitry Tantsur 19 Sep '19

19 Sep '19

Hi folks, I would like to ask a late FFE for https://storyboard.openstack.org/#!/story/2005167 - retry PXE boot on timeout. Random PXE failures have long been haunting both our consumers and our CI. This change may be a big relief for everyone. Since we're very late in the cycle, and the change is on the critical path, I'm making it off by default (except for the CI) with the intend to reconsider it in Ussuri. The patch https://review.opendev.org/#/c/683127/ has been tested locally, I will finish unit tests and a release note tomorrow (CEST) morning. Please let me know if you have any concerns or questions. Dmitry

3 3

[release][ironic] Some Ironic deliverables might need a refresh before final Train release
by Thierry Carrez 19 Sep '19

19 Sep '19

Hi everyone, Quick reminder that for deliverables following the cycle-with-intermediary model, the release team will use the latest train release available on release week. The following deliverables have done a train release, but it was not refreshed in the last two months: - bifrost (last released on 2019-06-06) - ironic-inspector (last released on 2019-07-09) - ironic-python-agent (last released on 2019-07-09) - ironic (last released on 2019-06-21) You should consider making a new one very soon, so that we don't use an outdated version for the final release. Thanks in advance, -- Thierry Carrez (ttx)

2 2

[tc] new chair
by Mohammed Naser 19 Sep '19

19 Sep '19

Hi everyone, With the new TC roster, JP and I both volunteered to be chairs of the TC which resulted in a CIVS vote between the TC, where the outcome was that JP won: http://lists.openstack.org/pipermail/openstack-discuss/2019-September/00948… Thanks for letting me serve for the past 6 months. Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

3 2

[horizon] FFE request for allow-users-change-expired-password
by Radomir Dopieralski 19 Sep '19

19 Sep '19

Hello everyone, I would like to request a feature freeze exception for Horizon for the allow-users-change-expired-password blueprint. The blueprint consists of three patches, of which one, implementing the actual password change form, is already merged, and the other two, implementing the redirect to that form when the password is expired, and adding documentation and release notes, have been already tested, reviewed and accepted (but can't be merged due to the freeze). Thank you, -- Radomir Dopieralski

3 2

[Tacker] {TOSCA] Regarding attaching persistent volume to a VDU in Tosca Template
by Nehal Bansal 19 Sep '19

19 Sep '19

Hi, I want to keep a backup of the data that my VNF creates. For this, I wanted to create a persistent volume such that if a VNF gets deleted and a new one gets launched, it can access the data created by the previous VNF. Is there a way to do this? Thanks. Nehal

2 1

[mistral] cron triggers execution fails on identity:validate_token with non-admin users
by Francois Scheurer 19 Sep '19

19 Sep '19

Dear All We are using Mistral 7.0.1.1 with Openstack Rocky. (with federated users) We can create and execute a workflow via horizon, but cron triggers always fail with this error: { "result": "The action raised an exception [ action_ex_id=ef878c48-d0ad-4564-9b7e-a06f07a70ded, action_cls='<class 'mistral.actions.action_factory.NovaAction'>', attributes='{u'client_method_name': u'servers.find'}', params='{ u'action_region': u'ch-zh1', u'name': u'42724489-1912-44d1-9a59-6c7a4bebebfa' }' ] \n NovaAction.servers.find failed: You are not authorized to perform the requested action: identity:validate_token. (HTTP 403) (Request-ID: req-ec1aea36-c198-4307-bf01-58aca74fad33) " } Adding the role *admin* or *service* to the user logged in horizon is "fixing" the issue, I mean that the cron trigger then works as expected, but it would be obviously a bad idea to do this for all normal users ;-) So my question: is it a config problem on our side ? is it a known bug? or is it a feature in the sense that cron triggers are for normal users? After digging in the keystone debug logs (see at the end below), I found that RBAC check identity:validate_token an deny the authorization. But according to the policy.json (in keystone and in horizon), rule:owner should be enough to grant it...: "identity:validate_token": "rule:service_admin_or_owner", "service_admin_or_owner": "rule:service_or_admin or rule:owner", "service_or_admin": "rule:admin_required or rule:service_role", "service_role": "role:service", "owner": "user_id:%(user_id)s or user_id:%(target.token.user_id)s", Thank you in advance for your help. Best Regards Francois Scheurer Keystone logs: 2019-09-05 09:38:00.902 29 DEBUG keystone.policy.backends.rules [req-1a276b9d-8276-4ec3-b516-f51f86cd1df6 fsc fscproject - testdom testdom] enforce identity:validate_token: { 'service_project_id':None, 'service_user_id':None, 'service_user_domain_id':None, 'service_project_domain_id':None, 'trustor_id':None, 'user_domain_id':u'testdom', 'domain_id':None, 'trust_id':u'mytrustid', 'project_domain_id':u'testdom', 'service_roles':[], 'group_ids':[], 'user_id':u'fsc', 'roles':[ u'_member_', u'creator', u'reader', u'heat_stack_owner', u'member', u'load-balancer_member'], 'system_scope':None, 'trustee_id':None, 'domain_name':None, 'is_admin_project':True, 'token':<TokenModel (audit_id=0LAsW_0dQMWXh2cTZTLcWA, audit_chain_id=[u'0LAsW_0dQMWXh2cTZTLcWA']) at 0x7f208f4a3bd0>, 'project_id':u'fscproject' } enforce /var/lib/kolla/venv/local/lib/python2.7/site-packages/keystone/policy/backends/rules.py:33 2019-09-05 09:38:00.920 29 WARNING keystone.common.wsgi [req-1a276b9d-8276-4ec3-b516-f51f86cd1df6 fsc fscproject - testdom testdom] You are not authorized to perform the requested action: identity:validate_token.: *ForbiddenAction: You are not authorized to perform the requested action: identity:validate_token.* -- EveryWare AG François Scheurer Senior Systems Engineer Zurlindenstrasse 52a CH-8003 Zürich tel: +41 44 466 60 00 fax: +41 44 466 60 10 mail: francois.scheurer(a)everyware.ch web: http://www.everyware.ch

3 5

[tc] Results of the two TC CIVS polls
by Graham Hayes 19 Sep '19

19 Sep '19

Hi All, We had two votes running for the TC - V->Z naming, and the TC Chair. The results are as follows: Release Naming: 1. Tied: Do not change current model of geographic names - No review Name releases after major cities - https://review.opendev.org/#/c/677745/ 3. Name releases after the ICAO alphabet - https://review.opendev.org/#/c/677746/ Full results: https://civs.cs.cornell.edu/cgi-bin/results.pl?num_winners=1&id=E_0a9abdade… TC Chair: 1. JP Evrard - https://review.opendev.org/#/c/681285/ 2. Mohammed Naser - https://review.opendev.org/#/c/680414/ Full results: https://civs.cs.cornell.edu/cgi-bin/results.pl?num_winners=1&id=E_e6963bddd… Thanks all for taking the time to vote, and for the candidates and people who put forward the options for the naming poll. Thanks, Graham

3 4

[horizon] exception for the allow-users-change-expired-password blueprint
by Radomir Dopieralski 19 Sep '19

19 Sep '19

Hello y'all, I would like to ask for an FEE for the allow-users-change-expired-password blueprint ( https://blueprints.launchpad.net/horizon/+spec/allow-users-change-expired-p…). The feature is important for users, and the code is reviewed and ready to merge. There are three patches, of which one, containing the form itself, is already merged, one contains the redirect on login failure, and one contains the documentation: https://review.opendev.org/#/c/672315/ https://review.opendev.org/#/c/676167/ Thank you, -- Radomir Dopieralski

1 1

[neutron]IPv6 Prefix Delegation could not be activated in newest version Neutron
by Shuai Zhao 18 Sep '19

18 Sep '19

Hi All, I'm working on validate the IPv6 PD in newest Neutron. What I want is to offer the Global Unified address to the VM and I find PD is the good solutions for me. I follow the guide *https://docs.openstack.org/neutron/latest/admin/config-ipv6.html <https://docs.openstack.org/neutron/latest/admin/config-ipv6.html> *to setup PD and dibbler-server and devstack, but I find I could not to trigger the PD process. *The Dibbler server print nothing when attach the Subnet to router has external gateway.* All procedure has recorded to the bug: https://bugs.launchpad.net/neutron/+bug/1844123. Thanks for your action and help in advance!

1 1

Nova causes MySQL timeouts
by Albert Braden 18 Sep '19

18 Sep '19

It looks like nova is keeping mysql connections open until they time out. How are others responding to this issue? Do you just ignore the mysql errors, or is it possible to change configuration so that nova closes and reopens connections before they time out? Or is there a way to stop mysql from logging these aborted connections without hiding real issues? Aborted connection 10726 to db: 'nova' user: 'nova' host: 'asdf' (Got timeout reading communication packets)

9 14

[cinder][FFE] Feature Freeze Exceptions agreed to in Weekly Meeting ....
by Jay Bryant 18 Sep '19

18 Sep '19

All, In our weekly meeting we discussed patches that required an FFE and decided to approve them there. This note is just to document that the FFE's were approved. The patches: * https://review.opendev.org/#/c/668825/(ZhengMa) - Leverage hw accelerator in image compression * https://review.opendev.org/#/c/673013 PowerMax Driver - Volume & Snapshot Metadata * https://review.opendev.org/#/c/677945/3Par -- Add Peer Persistence Support Please let us know if there are any concerns with these planned FFEs. Thanks! Jay (irc: jungleboyj)

1 0

[i18n][mogan][neutron][swift][tc][valet] Cleaning up IRC logging for defunct channels
by Jeremy Stanley 18 Sep '19

18 Sep '19

Freenode imposes a hard limit of 120 simultaneously joined channels for any single account. We've once again reached that limit with our channel-logging meetbot. As a quick measure, I've proposed a bit of cleanup: https://review.opendev.org/682500 Analysis of IRC channel logs indicates the following have seen 5 or fewer non-bot comments posted in the past 12 months and are likely of no value to continue logging: 5 #openstack-vpnaas 2 #swift3 2 #openstack-ko 1 #openstack-deployment 1 #midonet 0 #openstack-valet 0 #openstack-swg 0 #openstack-mogan Please let me know either here on the ML or with a comment on the review linked above if you have a reason to continue logging any of these channels. I'd like to merge it later this week if possible. Thanks! -- Jeremy Stanley

5 8

Re: [zuul3] zuul2 -> zuul3 migration
by Aditi Dukle1 18 Sep '19

18 Sep '19

Hi Lenny, Even I am working on zuulv2 to v3 migration for IBM PowerKVM - https://wiki.openstack.org/wiki/ThirdPartySystems/IBMPowerKVMCI and so far we have setup a test VM wherein we have installed zuulv3 and Nodepool version: 3.7.2 and have migrated 4 of our jenkins jobs to ansible to work with zuulv3. Zuulv3 doesn't have much info online apart from the official documentation but I found the following blogs quite useful while doing the migration: https://zuul-ci.org/docs/zuul/admin/quick-start.html - This is a very good installation tutorial to get a hang of zuulv3 that needs a single VM and it installs different components in docker containers. I started with this which helped me to understand how different components are configured. Also, the following articles are good read. 1. https://www.softwarefactory-project.io/cicd-workflow-offered-by-zuulnodepoo… 2. https://www.softwarefactory-project.io/zuul-hands-on-part-2-your-first-gate… 3. https://www.softwarefactory-project.io/zuul-hands-on-part-3-use-the-zuul-jo… Openstack has migrated to zuulv3, so you can also check out their project configuration here - https://opendev.org/openstack/project-config I am planning to write my experience of migration in a blog which I will let you know once complete. Let me know if you got any doubts while setting up zuulv3 Thanks and Regards, Aditi Dukle

1 0

regarding rabbitmq suspicious processes.
by Navid Bin Sakhawat 18 Sep '19

18 Sep '19

Hi! We are getting below status from rabbitmq. [root@controller1 ~]# rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().' 2019-09-18 18 <callto:2019-09-18 18>:08:55 There are 12374 processes. 2019-09-18 18 <callto:2019-09-18 18>:08:55 Investigated 2 processes this round, 5000ms to go. 2019-09-18 18 <callto:2019-09-18 18>:08:56 Investigated 2 processes this round, 4500ms to go. 2019-09-18 18 <callto:2019-09-18 18>:08:56 Investigated 2 processes this round, 4000ms to go. 2019-09-18 18 <callto:2019-09-18 18>:08:57 Investigated 2 processes this round, 3500ms to go. 2019-09-18 18 <callto:2019-09-18 18>:08:57 Investigated 2 processes this round, 3000ms to go. 2019-09-18 18 <callto:2019-09-18 18>:08:58 Investigated 2 processes this round, 2500ms to go. 2019-09-18 18 <callto:2019-09-18 18>:08:58 Investigated 2 processes this round, 2000ms to go. 2019-09-18 18 <callto:2019-09-18 18>:08:59 Investigated 2 processes this round, 1500ms to go. 2019-09-18 18 <callto:2019-09-18 18>:08:59 Investigated 2 processes this round, 1000ms to go. 2019-09-18 18 <callto:2019-09-18 18>:09:00 Investigated 2 processes this round, 500ms to go. 2019-09-18 18 <callto:2019-09-18 18>:09:00 Found 2 suspicious processes. 2019-09-18 18 <callto:2019-09-18 18>:09:00 [{pid,<10698.8499.10 <callto:10698.8499.10>>}, {registered_name,[]}, {current_stacktrace, [{timer,sleep,1,[{file,"timer.erl"},{line,153}]}, {rabbit_amqqueue,'-with/4-fun-0-',5, [{file,"src/rabbit_amqqueue.erl"},{line,469}]}, {rabbit_channel,handle_method,3, [{file,"src/rabbit_channel.erl"},{line,1323}]}, {rabbit_channel,handle_cast,2, [{file,"src/rabbit_channel.erl"},{line,470}]}, {gen_server2,handle_msg,2, [{file,"src/gen_server2.erl"},{line,1050}]}, {proc_lib,init_p_do_apply,3, [{file,"proc_lib.erl"},{line,247}]}]}, {initial_call,{proc_lib,init_p,5}}, {message_queue_len,2}, {links,[<10698.8496.10 <callto:10698.8496.10>>]}, {monitors, [{process,<10876.617.0>}, {process,<10698.3225.0 <callto:10698.3225.0>>}, {process,<10877.3228.0 <callto:10877.3228.0>>}]}, {monitored_by, [<10698.3225.0 <callto:10698.3225.0> >,<10877.293.0>,<10876.293.0>, <10698.8491.10 <callto:10698.8491.10>>,< 10698.21564.0 <callto:10698.21564.0>>,<10698.8670.0 <callto:10698.8670.0> >]}, {heap_size,4185}] 2019-09-18 18 <callto:2019-09-18 18>:09:00 [{pid,<10698.8521.10 <callto:10698.8521.10>>}, {registered_name,[]}, {current_stacktrace, [{timer,sleep,1,[{file,"timer.erl"},{line,153}]}, {rabbit_amqqueue,'-with/4-fun-0-',5, [{file,"src/rabbit_amqqueue.erl"},{line,469}]}, {rabbit_channel,handle_method,3, [{file,"src/rabbit_channel.erl"},{line,1323}]}, {rabbit_channel,handle_cast,2, [{file,"src/rabbit_channel.erl"},{line,470}]}, {gen_server2,handle_msg,2, [{file,"src/gen_server2.erl"},{line,1050}]}, {proc_lib,init_p_do_apply,3, [{file,"proc_lib.erl"},{line,247}]}]}, {initial_call,{proc_lib,init_p,5}}, {message_queue_len,2}, {links,[<10698.8518.10 <callto:10698.8518.10>>]}, {monitors, [{process,<10698.3225.0 <callto:10698.3225.0>>}, {process,<10876.617.0>}, {process,<10877.3228.0 <callto:10877.3228.0>>}]}, {monitored_by, [<10698.8513.10 <callto:10698.8513.10>>,< 10698.3225.0 <callto:10698.3225.0>>,<10877.293.0>, <10876.293.0>,<10698.8670.0 <callto:10698.8670.0> >,<10698.21564.0 <callto:10698.21564.0>>]}, {heap_size,4185}] Regards, *Navid Bin Sakhawat* Former Manager IT E.G Salary Ltd Mobile +880161559955 *5th Floor BGMEA Complex, Kawran Bazar, Dhaka. * *Former Engineer NOC* Mos 5 Tel Ltd. Plot-59, 61, Lotus Kamal Tower-2, Level-11, Gulshan-1, Dhaka-1212. *www.mos5tel.com <http://www.mos5tel.com>*

1 0

[goals][IPv6-Only Deployments and Testing] Week R-4 Update
by Ghanshyam Mann 18 Sep '19

18 Sep '19

Hello Everyone, Below is the progress on Ipv6 goal during R6 week. I started the legacy job for IPv6 deployment with duplicating the run.yaml which is the only best way to do. Summary: The projects still need to prepare the IPv6 job: * Ec2-Api * Freezer * Heat * Ironic * Karbor * Kolla * Kuryr * Magnum * Manila * Masakari * Mistral * Murano * Octavia * Swift The projects waiting for IPv6 job patch to merge: If patch is failing, help me to debug that otherwise review and merge. * Barbican * Blazar * Cyborg * Tricircle * Vitrage * Zaqar * Cinder * Glance * Monasca * Neutron * Qinling * Quality Assurance * Sahara * Searchlight * Senlin * Tacker The projects have merged the IPv6 jobs: * Designate * Murano * Trove * Cloudkitty * Congress * Horizon * Keystone * Nova * Placement * Solum * Telemetry * Watcher * Zun The projects do not need the IPv6 job (CLI, lib, deployment projects etc ): If anything I missed and IPv6 job need, please reply otherwise I will mark their task in storyboard as invalid. * Adjutant * Documentation * I18n * Infrastructure * Loci * Openstack Charms * Openstack-Chef * Openstack-Helm * Openstackansible * Openstackclient * Openstacksdk * Oslo * Packaging-Rpm * Powervmstackers * Puppet Openstack * Rally * Release Management * Requirements * Storlets * Tripleo * Winstackers Storyboard: ========= - https://storyboard.openstack.org/#!/story/2005477 IPv6 missing support found: ===================== 1. https://review.opendev.org/#/c/673397/ 2. https://review.opendev.org/#/c/673449/ 3. https://review.opendev.org/#/c/677524/ How you can help: ============== - Each project needs to look for and review the ipv6 job patch. - Verify it works fine on ipv6 and no ipv4 used in conf etc - Any other specific scenario needs to be added as part of project IPv6 verification. - Help on debugging and fix the bug in IPv6 job is failing. Everything related to this goal can be found under this topic: Topic: https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(stat… How to define and run new IPv6 Job on project side: ======================================= - I prepared a wiki page to describe this section - https://wiki.openstack.org/wiki/Goal-IPv6-only-deployments-and-testing Review suggestion: ============== - Main goal of these jobs will be whether your service is able to listen on IPv6 and can communicate to any other services either OpenStack or DB or rabbitmq etc on IPv6 or not. So check your proposed job with that point of view. If anything missing, comment on patch. - One example was - I missed to configure novnc address to IPv6- https://review.opendev.org/#/c/672493/ - base script as part of 'devstack-tempest-ipv6' will do basic checks for endpoints on IPv6 and some devstack var setting. But if your project needs more specific verification then it can be added in project side job as post-run playbooks as described in wiki page[1]. [1] https://wiki.openstack.org/wiki/Goal-IPv6-only-deployments-and-testing -gmann

7 15

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

18 Sep '19

Hello, > You seem to be missing the point. The alternative to Angular is not JQuery, it's a proper implementation on the server-side, > both in the APIs (for pagination and filtering) and Horizon itself. Slapping JavaScript on top of it, whether it's Angular or > JQuery, won't improve the situation. No, I understand what you're saying, I just don't think it's very realistic. Exclusively using server side templating has some issues in terms of usability and performance which might not have satisfactory solutions. For example: - Any interaction causes a roundtrip to the web server and the backend API, which reduces performance, especially with large data sets. - In some cases, datasets are composed of multiple API calls with disjunct results (see Networks [1] for an example). Paging and sorting over these datasets requires for them to be reconstructed on the webserver for every paging or sorting request and that means a full data load. For any at least somewhat sizeable datasets, this creates performance issues. - UI loses reactivity. Interfield interactions, for example, are basically impossible because of web server centered re-rendering, which reduces user comfort and usability. Moving logic to the client using JavaScript does improve the situation: - Data can be loaded in chunks asynchronously in the background without impeding the rest of Horizon - Cached data can be operated on (paged, sorted...) without additional requests to the web server and backend - Data can be shared between different horizon elements without the need for a reload - e.g. loaded networks can be used in the network index table, the Launch instance dialog and Network Topology all without loading it separately for each. Additionally, JavaScript also allows for more advanced tools, such as the Network Topology views (admittedly, they also require a fair amount of work). These are just some examples to illustrate the point. I'm sure other use cases could be found. [1] https://github.com/openstack/horizon/blob/fa804370b11519fc261f73fa90177368f… po 16. 9. 2019 v 10:43 odesílatel Radomir Dopieralski < openstack(a)sheep.art.pl> napsal: > You seem to be missing the point. The alternative to Angular is not > JQuery, it's a proper implementation on the server-side, both in the APIs > (for pagination and filtering) and Horizon itself. Slapping JavaScript on > top of it, whether it's Angular or JQuery, won't improve the situation. > > On Wed, Sep 11, 2019 at 5:21 PM Marek Lyčka <marek.lycka(a)ultimum.io> > wrote: > >> Hi all, >> >> > We can't review your patches, because we don't understand them. For the >> patches to be merged, we >> > need more than one person, so that they can review each other's patches. >> >> Well, yes. That's what I'm trying to address. Even if another person >> appeared to review >> javascript code, it wouldn't change anything unless he had +2 and +W >> rights though. And even then, >> it wouldn't be enough, because two +2 are currently expected for the CR >> process to go ahead. >> >> > JavaScript is fine. We all know how to write and how to review >> JavaScript code, and there doesn't >> > have to be much of it — Horizon is not the kind of tool that has to bee >> all shiny and animated. It's a tool >> > for getting work done. >> >> This isn't about being shiny and animated though. This is about basic >> functionality, usability and performance. >> I did some stress testing with large datasets [1], and the >> non-angularized versions of basic functionality like >> sorting, paging and filtering in table panels are either non-existent, >> not working at all or basically unusable >> (for a multitude of reasons). >> >> Removing them would force reimplementations in pure JQuery and I strongly >> suspect that those >> implementations would be much messier and cost a considerable amount of >> time and effort. >> >> >AngularJS is a problem, because you can't tell what the code does just >> by looking >> >at the code, and so you can neither review nor fix it. >> >> This is clearly a matter of opinion. I find Angular code easier to deal >> with than JQuery spaghetti. >> >> > There has been a lot of work put into mixing Horizon with Angular, but >> I disagree that it has solved problems, >> > and in fact it has introduced a lot of regressions. >> >> I'm not saying the NG implementations are perfect, but they mostly work >> where it counts and can be improved >> where they do not. >> >> > Just to take a simple example, the translations are currently broken >> for en.AU and en.GB languages, >> > and date display is not localized. And nobody cares. >> >> It's difficult for me to judge which features are broken in NG and how >> much interest there is in having them >> fixed, but they can be fixed once reported. What I can say for sure is >> that I keep hitting this issue >> because of actual feature requests from actual users. See [2] for an >> example. I'm not sure implementing >> that in pure JQuery would be nearly as simple as it was in Angular. >> >> > We had automated tests before Angular. There weren't many of them, >> because we also didn't have much >> > JavaScript code. If I remember correctly, those tests were ripped out >> during the Angularization. >> >> Fair enough. >> >> > Arguably, improvements are, on average, impossible to add to Angular >> >> I disagree. Yes, pure JQuery is probably easier when dealing with very >> simple things, but once feature >> complexity increases beyond the basics, you'll very quickly find the >> features offered by the framework >> relevant - things like MVC decoupling, browser-side templating, reusable >> components, functionality injection etc. >> Again, see [2] for an example. >> >> On a side note, some horizon plugins (such as octavia-dashboard) use >> Angular extensively. Removing it >> would at the very least break them. >> >> Whatever the community decision is though, I feel like it needs to be >> made so that related issues >> can be addressed with a reasonable expectation of being reviewed and >> merged. >> >> [1] Networks, Roles and Images in the low thousands >> [2] https://review.opendev.org/#/c/618173/ >> >> pá 6. 9. 2019 v 18:44 odesílatel Dale Bewley <dale(a)bewley.net> napsal: >> >>> As an uninformed user I would just like to say Horizon is seen _as_ >>> Openstack to new users and I appreciate ever effort to improve it. >>> >>> Without discounting past work, the Horizon experience leaves much to be >>> desired and it colors the perspective on the entire platform. >>> >>> On Fri, Sep 6, 2019 at 05:01 Radomir Dopieralski <openstack(a)sheep.art.pl> >>> wrote: >>> >>>> >>>> >>>> On Fri, Sep 6, 2019 at 11:33 AM Marek Lyčka <marek.lycka(a)ultimum.io> >>>> wrote: >>>> >>>>> 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. >>>>> >>>> >>>> We can't review your patches, because we don't understand them. For the >>>> patches to be merged, we >>>> need more than one person, so that they can review each other's patches. >>>> >>>> >>>>> > 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. >>>>> >>>> >>>> JavaScript is fine. We all know how to write and how to review >>>> JavaScript code, and there doesn't >>>> have to be much of it — Horizon is not the kind of tool that has to bee >>>> all shiny and animated. It's a tool >>>> for getting work done. AngularJS is a problem, because you can't tell >>>> what the code does just by looking >>>> at the code, and so you can neither review nor fix it. >>>> >>>> There has been a lot of work put into mixing Horizon with Angular, but >>>> I disagree that it has solved problems, >>>> and in fact it has introduced a lot of regressions. Just to take a >>>> simple example, the translations are currently >>>> broken for en.AU and en.GB languages, and date display is not >>>> localized. And nobody cares. >>>> >>>> We had automated tests before Angular. There weren't many of them, >>>> because we also didn't have much JavaScript code. >>>> If I remember correctly, those tests were ripped out during the >>>> Angularization. >>>> >>>> Arguably, improvements are, on average, impossible to add to Angular, >>>> because the code makes no sense on its own. >>>> >>>> >>>> >> >> -- >> 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/>*

2 1

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

17 Sep '19

Hi everyone, Here’s the update of what happened in this week’s OpenStack Ansible Office Hours. The upgrade jobs are going well and passing. CentOD is taking longer but we can reduce the time it takes if we skip tempest tests after Stein deployment (by changing the order of passed arguments to the ansible-playbook). Milestone was updated but we’re waiting on the Keystone bug to get resolved before merging it. We’ll have to work on Tempest in order to get that fixed with the proper testing. For Swift, we talked about editing our job templates to remove testing as we transition to Python 3. We’ll propose a patch and a revert at the same time to not forget about fixing it later. Neutron and Calico are having problems with Python3 and we discussed going through distro variables to make sure Ubuntu is using Python3 everywhere. Bind-to-mgmt needs a little more work until we can land it. We need to cut back on variables because right now there are too many. We also want to add a global variable in each role corresponding to the mgmt-addr. We think we’re getting closer to knowing what is breaking with CentOS 7.7. As for Galera, we abandoned the patch and replaced the bind addrs but we still need to figure out why it’s still breaking on the integrated repository. 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

2 1

[all][interop][cinder][qa] API changes with/without microversion and Tempest verification of API interoperability
by Ghanshyam Mann 17 Sep '19

17 Sep '19

Hello Everyone, As per discussion over ML, Tempest started the JSON schema strict validation for Volume APIs response [1]. Because it may affect the interop certification, it was explained to the Interop team as well as in the Board of Director meeting[2]. In Train, Tempest started implementing the validation and found an API change where the new field was added in API response without versioning[3] (Cinder has API microversion mechanism). IMO, that was not the correct way to change the API and as per API-WG guidelines[4] any field added/modified/removed in API should be with microverison(means old versions/user should not be affected by that change) and must for API interoperability. With JSON schema validation, Tempest verifies the API interoperability recommended behaviour by API-WG. But as per IRC conversion with cinder team, we have different opinion on API interoperability and how API should be changed under microversion mechanism. I would like to have a conclusion on this so that Tempest can verify or leave the Volume API for strict validation. [1] http://lists.openstack.org/pipermail/openstack-discuss/2018-November/000358… [2] - http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003652.ht… - http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003655.ht… [3] https://bugs.launchpad.net/tempest/+bug/1843762 https://review.opendev.org/#/c/439461/ [4] https://specs.openstack.org/openstack/api-wg/guidelines/api_interoperabilit… -gmann

8 21

[goals][IPv6-Only Deployments and Testing] Week R-4 Update-2
by Ghanshyam Mann 17 Sep '19

17 Sep '19

Hello Everyone, Below is the latest updated on IPv6 goal. All the projects have the patch proposed now. Next step is to review then as per mentioned guidelines below or help in debugging the failure if any. Summary: The projects still need to prepare the IPv6 job: * None The projects waiting for IPv6 job patch to merge: If patch is failing, help me to debug that otherwise review and merge. * Barbican * Blazar * Cyborg * Tricircle * Vitrage * Zaqar * Cinder * Glance * Monasca * Neutron * Qinling * Sahara * Searchlight * Senlin * Tacker * Ec2-Api * Freezer * Heat * Ironic * Karbor * Kuryr * Magnum * Manila * Masakari * Mistral * Murano * Octavia (johnsom is working on this and will take over the base patch) * Swift The projects have merged the IPv6 jobs: * Designate * Murano * Trove * Cloudkitty * Congress * Horizon * Keystone * Nova * Placement * Solum * Telemetry * Watcher * Zun The projects do not need the IPv6 job (CLI, lib, deployment projects etc ): I have marked the tasks for below project as invalid. * Adjutant * Documentation * I18n * Infrastructure * Kolla * Loci * Openstack Charms * Openstack-Chef * Openstack-Helm * Openstackansible * Openstackclient * Openstacksdk * Oslo * Packaging-Rpm * Powervmstackers * Puppet Openstack * Rally * Release Management * Requirements * Storlets * Tripleo * Winstackers Storyboard: ========= - https://storyboard.openstack.org/#!/story/2005477 IPv6 missing support found: ===================== 1. https://review.opendev.org/#/c/673397/ 2. https://review.opendev.org/#/c/673449/ 3. https://review.opendev.org/#/c/677524/ How you can help: ============== - Each project needs to look for and review the ipv6 job patch. - Verify it works fine on ipv6 and no ipv4 used in conf etc - Any other specific scenario needs to be added as part of project IPv6 verification. - Help on debugging and fix the bug in IPv6 job is failing. Everything related to this goal can be found under this topic: Topic: https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(stat… How to define and run new IPv6 Job on project side: ======================================= - I prepared a wiki page to describe this section - https://wiki.openstack.org/wiki/Goal-IPv6-only-deployments-and-testing Review suggestion: ============== - Main goal of these jobs will be whether your service is able to listen on IPv6 and can communicate to any other services either OpenStack or DB or rabbitmq etc on IPv6 or not. So check your proposed job with that point of view. If anything missing, comment on patch. - One example was - I missed to configure novnc address to IPv6- https://review.opendev.org/#/c/672493/ - base script as part of 'devstack-tempest-ipv6' will do basic checks for endpoints on IPv6 and some devstack var setting. But if your project needs more specific verification then it can be added in project side job as post-run playbooks as described in wiki page[1]. [1] https://wiki.openstack.org/wiki/Goal-IPv6-only-deployments-and-testing

1 0

[PTLs] [TC] OpenStack User Survey - PTL & TC Feedback
by Jimmy McArthur 17 Sep '19

17 Sep '19

Hi everyone - It's that time again where we share the project specific feedback from the user survey directly with you, the community There are two CSVs, one with all of the feedback[1] and another with a question key[2] so you have some context for the answers. The data in these spreadsheets is 100% anonymized and contains NO information around the actual deployments. These are simply answers to the project-specific and TC questions that were added to the end of the survey. If you are a PTL or TC member and would like specific/expanded information around a particular comment, please contact allison(a)openstack.org or jimmy(a)openstack.org. We will do our best to accommodate, provided it doesn't violate the privacy of the submitter. Please let me know if you have questions/concerns. Cheers, Jimmy [1] 2019 User Survey Data - Deployment PTL Comments.csv [2] 2019 User Survey Data - PTL Answer Key.csv

1 0

[magnum] New weekly meeting time
by feilong 17 Sep '19

17 Sep '19

Hi team, As we discussed on IRC, the new Magnum weekly meeting time will be each Wednesday 9:00AM UTC on #openstack-containers channel. -- Cheers & Best regards, Feilong Wang (王飞龙) ------------------------------------------------------ Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang(a)catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington ------------------------------------------------------

1 0

[kolla] State of ppc64le support
by Marcin Juszkiewicz 17 Sep '19

17 Sep '19

About 2.5 years ago I added AArch64 (64-bit ARM) architecture support to Kolla project. Side effect of that work was adding ppc64le (64-bit Power, Little Endian) support. Time passed, from time to time someone jumped to the irc channel and said that they use it. No one in core team spent much time on supporting it as it was outside of our interest. >From time to time I was reserving Power machine in Red Hat to do build and check how we are with ppc64le support. This week I did that again. >From 3 distributions we target only Debian/source combo was buildable. CentOS builds lack 'rabbitmq' 3.7.10 (we use external repo) and 'gnocchi' binary images are not buildable due to lack of some packages (issue already reported to CentOS by TripleO team). Ubuntu builds lack MariaDB 10.3 because upstream repo is broken. Packages index is provided for 'ppc64le' but no packages so we get 404 errors. Due to all those issues and fact that there are no users of ppc64le Kolla containers I want to drop support for it in this cycle. Any objections?

4 6

[ansible-sig] weekly meeting summary
by Mohammed Naser 17 Sep '19

17 Sep '19

Hi everyone, On Friday, September 13th we had our first ever openstack-ansible-sig meeting and here’s a summary of what we talked about. The goal of this group would be to collaborate on points that will lower the tech-debt of all our projects. We think there are a few things we can work on like spanning roles, modules, plugins, patterns, etc. We mentioned wanting to work on the os-tempest role, the config-template, the connection plugin or mitogen if we can extract only the connection stacking parts. We’ll start working on the connection plugins and try to upstream when it’s ready. owalsh has been working on the docker plugin, so he should have his docker bits in a repository soon so we can push them into the forked connection plugin. We discussed getting Kolla into working on tempest things alongside OSA and TripleO in order to make it better. We’ll also start working on the Ansible RFE regarding connection plugins.. Thanks for tuning in! 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] weekly update
by Mohammed Naser 17 Sep '19

17 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 - charm-cinder-purestorage (under charm-cinder) # Retired projects - networking-generic-switch-tempest-plugin (under ironic) # General changes - Date changes, role resets and member additions to the OpenStack Governance member list: https://review.opendev.org/#/c/680356/ - Changes in the OpenStack Governance house-rules. TC members will be able to approve fast-tracked changes: https://review.opendev.org/#/c/678212/ - Update elections results: https://review.opendev.org/#/c/680507/ 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