- openstack-discuss - lists.openstack.org

[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

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

17 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

1 0

[sdk][release][requirements] FFE requested for openstacksdk
by Monty Taylor 17 Sep '19

17 Sep '19

Heya, We’d like to cut an 0.35.1 bugfix release as part of train to grab https://review.opendev.org/#/c/680649/ and https://review.opendev.org/#/c/682454/. The first is landed and is in support of the Ironic Nova driver. The second is making its way through the gate right now and is in support of OSC v4. Thanks! Monty

3 4

[zuul3] zuul2 -> zuul3 migration
by Lenny Verkhovsky 17 Sep '19

17 Sep '19

Hi Team, We would like to migrate our Third Party CI[1] from zuul2 to zuul3. We have a lot of Jenkins jobs initially based on infra project-config-example But I guess we need to re write all the jobs now to support ansible. Any guide/example/tips are highly appreciated. [1] https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI [2] https://github.com/openstack-infra/project-config-example/tree/master/jenki… Best Regards Lenny Verkhovsky (aka lennyb) Mellanox Technologies<http://www.mellanox.com/> office: +972 74 712 92 44 fax: +972 74 712 91 11 mobile: +972 54 554 02 33 irc: lennyb

2 2

[requirements] Issues while trying to bump-up ovsdbapp requirement for stable/queens
by Maciej Jozefczyk 17 Sep '19

17 Sep '19

Hello, I'm trying to bump-up ovsdbapp requirement in networking-ovn [0] from 0.8.0 [1] to 0.10.4 [2]. Those two are in the same stable/queens release and we need that change to merge some serious performance improvements to stable/queens. Unfortunately the requirements-check jobs fails on this change [3] with: Requirement for package ovsdbapp : Requirement(package=u'ovsdbapp', location='', specifiers='>=0.10.4', markers=u'', comment=u'# Apache-2.0', extras=frozenset([])) does not match openstack/requirements value : set([Requirement(package='ovsdbapp', location='', specifiers='>=0.8.0', markers='', comment='# Apache-2.0', extras=frozenset([]))]) The only place where >=0.8.0 is set is global-requirements [4]. Do we need to bump up it also there, even the upper-requirements bot proposal [5] has been merged? It is string match? I proposed a change to bump it in global-requirements [6]. Thanks, Maciej [0] https://review.opendev.org/#/c/681562/ [1] https://github.com/openstack/ovsdbapp/releases/tag/0.8.0 [2] https://github.com/openstack/ovsdbapp/releases/tag/0.10.4 [3] https://bb8048f0749367929365-38c02a6f4c2535c3f3f9bfdb5440d261.ssl.cf1.rackc… [4] https://github.com/openstack/requirements/blob/stable/queens/global-require… [5] https://review.opendev.org/#/c/682323 [6] https://review.opendev.org/#/c/682588 -- Best regards, Maciej Józefczyk

2 2

[os-win][requirements] FFE requested for os-win
by Lucian Petrut 17 Sep '19

17 Sep '19

Hi, I’d like to request a FFE for os-win. One important bug fix has missed the train (4.3.1) release, for which reason we’d need to have a subsequent one. The bug in question prevents Nova from starting after host reboots when using the Hyper-V driver on recent Windows Server 2019 builds. Thanks, Lucian Petrut

2 1

[oslo] Stepping down from core reviewer
by ChangBo Guo 17 Sep '19

17 Sep '19

Hi folks, I no longer have the time to contribute to Oslo in a meaningful way in past few months, due to the company internal stuff, and would like to step down from core reviewer. It was an honor to be one of the great team since 4 years ago. I still work on OpenStack, just have no enough time to focus on Oslo. I hope have more time to contribute again in the future :-) All the best! -- ChangBo Guo(gcb)

2 1

[all] stable/ocata gate failure
by Ghanshyam Mann 17 Sep '19

17 Sep '19

Hello Everyone, If you have noticed that stable/ocata gate is blocked where 'legacy-tempest-dsvm-neutron-full/-*' job is failing due to the latest Tempest changes. Tempest started the JSON schema strict validation for Volume APIs which caught the failure or you can say Tempest master cannot be used in Ocata testing. More details- https://bugs.launchpad.net/tempest/+bug/1843762 As per the Tempest stable branch testing policy[1], Tempst does not support the stable/ocata (which is EM )in the current development cycle. Current supported stable branches by Tempest are Queens, Rocky, Stein and Train-on-going. We can keep using Tempest master on EM stable/branches as long as it run successfully and if it start failing which is current case of stable/ocata then use Tempest tag to test that EM stable branch. To unblock the stable/ocata gate, I am trying to install the Tempest 20.0.0(compatible version for Ocata) in ocata gate - https://review.opendev.org/#/c/681950/ Fix is not working as of now (it still install Tempest master). I will debug that later (my current priority is for Train feature freeze). [1] https://docs.openstack.org/tempest/latest/stable_branch_support_policy.html -gmann

2 3

[all] Please do not bump openstackdocstheme minimum version if possible
by Thomas Goirand 17 Sep '19

17 Sep '19

Hi, The openstackdocstheme package in Debian is highly modified, because otherwise, building docs just fail. Namely, we have reverted commit d87aaca30f64502b3dd13cc1ddf46beec90fc015 because otherwise, the docs wouldn't build. Rebasing it is *very* annoying. So, it'd be nice if packages didn't depend on the very latest version of openstackdocstheme so we could keep version 1.20.0. I don't think it's that important to depend on the very latest version (please let me know if I'm wrong, and let me know why). Cheers, Thomas Goirand (zigo)

3 3

[kolla] Support Octavia for ubuntu binary on stable/rocky?
by Eddie Yen 17 Sep '19

17 Sep '19

Hi, I'm trying to install Octavia in Rocky release with Ubuntu binary distro. And found that there're no docker images for Ubuntu binary. Then I checked the Kolla dockerfile and found that it will not build the image since it's not support yet. But I found that the Ubuntu Cloud Archive Team has already putted Octavia packages into cloud repository [1]. Since some images built using from this PPA, I think it can support ubuntu binary in Rocky release. I tried put package code into Docker files and build, but it gave me an error message like below: ERROR:kolla.common.utils:octavia-api Failed with status: matched ERROR:kolla.common.utils:octavia-health-manager Failed with status: matched ERROR:kolla.common.utils:octavia-housekeeping Failed with status: matched ERROR:kolla.common.utils:octavia-worker Failed with status: matched So I think there's limit somewhere. How can I release it? Thanks, Eddie. [1] https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/rocky-staging

2 4

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

17 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

3 4

[Neutron][vxlan][nsx-v]
by Ignazio Cassano 16 Sep '19

16 Sep '19

Hello, I have a vmware vcenter installatiom with nsx-v and an openstack installation with kvm and openvswitch. I am looking for a method for realizing a vxlan shared between nsx-v and openvswitch. I know vmware released nsx-t but I prefer to use an opensource solution. Anyone could suggest a solution? Thanks Ignazio

1 0

[dev] [glance] proposal for S3 store driver re-support as galnce_store backend
by Naohiro Sameshima 16 Sep '19

16 Sep '19

Hi all, I know that glance_store had supported S3 backend until version OpenStack Mitaka, and it has already been removed due to lack of maintainers [1][2]. I started refactoring the S3 driver to work with version OpenStack Stein and recently completed it. (e.g. Add Multi Store Support, Using the latest AWS SDK) So, it would be great if glance_store could support the S3 driver again. However, I'm not familiar with the procedure for that. Would it be possible to discuss this? Thanks, Naohiro [1] https://docs.openstack.org/releasenotes/glance/newton.html [2] https://opendev.org/openstack/glance_store/src/branch/master/releasenotes/n…

4 3

[placement] update 19-35
by Chris Dent 16 Sep '19

16 Sep '19

HTML: https://anticdent.org/placement-update-19-36.html Here's placement update 19-36. There won't be one next week, I will be away. Because of my forthcoming "less time available for OpenStack" I will also be stopping these updates at some point in the next month or so so I can focus the limited time I will have on reviewing and coding. There will be at least one more. # Most Important The big news this week is that after returning from a trip (that meant he was away during the nomination period) Tetsuro has stepped up to be the PTL for placement in Ussuri. Thanks very much to him for taking this up, I'm sure he will be excellent. We need to work on useful documentation for the features developed this cycle. I've also made a [now worklist](https://storyboard.openstack.org/#!/worklist/754) in StoryBoard to draw attention to placement project stories that are relevant to the next few weeks, making it easier to ignore those that are not relevant now, but may be later. # Stories/Bugs (Numbers in () are the change since the last pupdate.) There are 23 (-1) stories in [the placement group](https://storyboard.openstack.org/#!/project_group/placement). 0 (0) are [untagged](https://storyboard.openstack.org/#!/worklist/580). 5 (0) are [bugs](https://storyboard.openstack.org/#!/worklist/574). 4 (0) are [cleanups](https://storyboard.openstack.org/#!/worklist/575). 10 (-1) are [rfes](https://storyboard.openstack.org/#!/worklist/594). 5 (1) are [docs](https://storyboard.openstack.org/#!/worklist/637). If you're interested in helping out with placement, those stories are good places to look. * Placement related nova [bugs not yet in progress](https://goo.gl/TgiPXb) on launchpad: 17 (0). * Placement related nova [in progress bugs](https://goo.gl/vzGGDQ) on launchpad: 6 (0). # osc-placement * <https://review.opendev.org/666542> Add support for multiple member_of. There's been some useful discussion about how to achieve this, and a consensus has emerged on how to get the best results. # Main Themes ## Consumer Types Adding a type to consumers will allow them to be grouped for various purposes, including quota accounting. * <https://review.opendev.org/#/q/topic:bp/support-consumer-types> This has some good comments on it from melwitt. I'm going to be away next week, so if someone else would like to address them that would be great. If it is deemed fit to merge, we should, despite feature freeze passing, since we haven't had much churn lately. If it doesn't make it in Train, that's fine too. The goal is to have it ready for Nova in Ussuri as early as possible. ## Cleanup Cleanup is an overarching theme related to improving documentation, performance and the maintainability of the code. The changes we are making this cycle are fairly complex to use and are fairly complex to write, so it is good that we're going to have plenty of time to clean and clarify all these things. Performance related explorations continue: * <https://review.opendev.org/#/c/679385/> Refactor initialization of research context. This puts the code that might cause an exit earlier in the process so we can avoid useless work. One outcome of the performance work needs to be something like a _Deployment Considerations_ document to help people choose how to tweak their placement deployment to match their needs. The simple answer is use more web servers and more database servers, but that's often very wasteful. * <https://review.opendev.org/#/q/owner:"Chris+Dent+%253Ccdent%2540anticdent.org%253E"+topic:build-pdf-docs> These are the patches for meeting the build pdf docs goal for the various placement projects. # Other Placement Miscellaneous changes can be found in [the usual place](https://review.opendev.org/#/q/project:openstack/placement+status:op…. There are three [os-traits changes](https://review.opendev.org/#/q/project:openstack/os-traits+status:… being discussed. And two [os-resource-classes changes](https://review.opendev.org/#/q/project:openstack/os-resource-class…. The latter are docs-related. # Other Service Users New reviews are added to the end of the list. Reviews that haven't had attention in a long time (boo!) or have merged or approved (yay!) are removed. * <https://review.opendev.org/662229> helm: add placement chart * <https://review.opendev.org/670112> Nova: WIP: Add a placement audit command * <https://review.opendev.org/670696> tempest: Add placement API methods for testing routed provider nets * <https://review.opendev.org/#/q/topic:bp/cross-cell-resize> Nova: cross cell resize * <https://review.opendev.org/674524> Nova: Scheduler translate properties to traits * <https://review.opendev.org/623558> Nova: single pass instance info fetch in host manager * <https://review.opendev.org/#/q/topic:bp/provider-config-file> Nova: using provider config file for custom resource providers * <https://review.opendev.org/681955> Nova: clean up some lingering placement stuff * <https://review.opendev.org/664867> OSA: Add nova placement to placement migration * <https://review.opendev.org/681343> Charms: Disable nova placement API in Train * <https://review.opendev.org/#/q/topic:bug/1841481> Nova: stop using @safe_connect in report client # End 🐈 -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent

2 1

[neutron] [neutron-lib] Change of in neutron-lib lead
by Miguel Lavalle 16 Sep '19

16 Sep '19

Dear Neutrinos, Many of you might have heard the Russel Boden's employer is changing his focus. As a consequence, Boden won't be able to continue leading our neutron-lib efforts. We want to thank you for the great job he has done over many cycles in advancing this sub-project. We are also looking for a volunteer to lead neutron-lib. Boden put together an etherpad with what needs to be done in the near future: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list Regards Miguel

2 1

Open Infrastructure Summit Shanghai: Forum Submissions Open
by Jimmy McArthur 16 Sep '19

16 Sep '19

Hello Everyone! We are now accepting Forum [1] submissions for the 2019 Open Infrastructure Summit in Shanghai [2]. Please submit your ideas through the Summit CFP tool [3] through September20th. Don't forget to put your brainstorming etherpad up on the Shanghai Forum page [4]. This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. Keep in mind, Forum submissions are for discussions, not presentations. The timeline for submissions is as follows: Sep 4th | Formal topic submission tool opens: https://cfp.openstack.org. Sep 20th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. Sep 30th | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. Oct 7th | Scheduling committee final meeting Oct 14th | Forum schedule final Nov 4-6| Forum Time! If you have questions or concerns, please reach out to speakersupport(a)openstack.org <mailto:speakersupport@openstack.org>. Cheers, Jimmy [1] https://wiki.openstack.org/wiki/Forum [2] https://www.openstack.org/summit/shanghai-2019/ [3] https://cfp.openstack.org [4] https://wiki.openstack.org/wiki/Forum/Shanghai2019

1 1

[charms] no irc meeting today
by James Page 16 Sep '19

16 Sep '19

Hi Team Due to travel + events for most of the team there will be no Charms IRC meeting today. Cheers James

1 0

[cloudkitty] 13/09 meeting summary
by Luka Peschke 16 Sep '19

16 Sep '19

Hi everyone, This is the recap of the cloudkitty team IRC meeting that happened on 13/09. The logs can be found at [1]. All features patches we wanted to integrate have been merged for the feature freeze dealine. An experimental v2 storage driver for Elasticsearch has also been merged. Concerning the community goals: python3-first has been implemented early, however we're late for PDF docs generation, as we've got several issues when trying to generate PDF documentation, especially with tabs. A patch for cloudkitty has been proposed today [2]. Patches for the client and specs repos are to be done. They're our current top priority. From now on, the IRC meeting will be held twice every month, on the first and third monday at 14h UTC. This means that the next meeting will happen on october 7th. We plan to send a recap to this mailing list for each meeting. For the U cycle, we'd like to use storyboard a lot more. For now, it's been used for features and major bugs only, but we'll use it for every non-trivial patch from now on. Our temporary roadmap for U is the following: * Design and implement a new rating module. * Support time-based grouping in the /v2/summary endpoint. This would allow to easily create charts with cloudkitty's API. * [To be discussed] Stop differenciating "groupby" and "metadata" attributes, as these seem to be confusing for admins. * Port as many v1 API endpoints as possible to v2. Best regards, Luka Peschke (peschk_l) [1] http://eavesdrop.openstack.org/meetings/cloudkitty/2019/cloudkitty.2019-09-… [2] https://review.opendev.org/#/c/682364/

1 0

[requirements] [ironic] Bumping test-requirements on stable/train for the PDF goal?
by Dmitry Tantsur 16 Sep '19

16 Sep '19

Hi all, we (ironic) have a few deliverables that got the PDF goal fulfilled after stable/train was branched. Is it reasonable to still pursue the goal on stable/train even if it requires raising the openstackdoctheme requirement? An example is https://review.opendev.org/#/c/682274/ Thanks, Dmitry

2 1

[neutron] DevStack with IPv6
by Lucio Seki 16 Sep '19

16 Sep '19

Hi folks, I'm having troubles to ping6 a VM running over DevStack from its hypervisor. Could you please help me troubleshooting it? I deployed DevStack with NEUTRON_CREATE_INITIAL_NETWORKS=False, and manually created the networks, subnets and router. Following is my router: $ openstack router show router1 -c external_gateway_info -c interfaces_info +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | external_gateway_info | {"network_id": "b87048ed-1be9-4f31-8d7e-fe74921aeec4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "28a00bc3-b30b-456f-b26a-44b50d37183f", "ip_address": "10.2.0.199"}, {"subnet_id": "a9729beb-b297-4fec-8ec3-7703f7f6f4bc", "ip_address": "fd12:67:1::3c"}]} | | interfaces_info | [{"subnet_id": "081e8508-4ceb-4aaf-bf91-36a1e22a768c", "ip_address": "fd12:67:1:1::1", "port_id": "75391abd-8ac8-41f8-acf8-3dfaf2a6b08f"}] | +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ I'm trying to ping6 the following VM: $ openstack server list +--------------------------------------+---------+--------+------------------------------------------+--------+--------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+---------+--------+------------------------------------------+--------+--------+ | 938854d0-80e9-45b2-bc29-8fe7651ffa93 | manila1 | ACTIVE | private1=fd12:67:1:1:f816:3eff:fe0e:17c3 | manila | manila | +--------------------------------------+---------+--------+------------------------------------------+--------+--------+ I intend to reach it via br-ex interface of the hypervisor: $ ip a show dev br-ex 9: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 0e:82:a1:ba:77:4c brd ff:ff:ff:ff:ff:ff inet6 fd12:67:1::1/64 scope global valid_lft forever preferred_lft forever inet6 fe80::c82:a1ff:feba:774c/64 scope link valid_lft forever preferred_lft forever The hypervisor has the following routes: $ ip -6 route fd12:67:1:1::/64 via fd12:67:1::3c dev br-ex metric 1024 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev br-ex proto kernel metric 256 pref medium fe80::/64 dev br-int proto kernel metric 256 pref medium fe80::/64 dev tapa5cf4799-9f proto kernel metric 256 pref medium And within the VM has the following routes: root@ubuntu:~# ip -6 route root@ubuntu:~# ip -6 route fd12:67:1::/64 via fd12:67:1:1::1 dev ens3 metric 1024 pref medium fd12:67:1:1::/64 dev ens3 proto kernel metric 256 expires 86360sec pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium default via fe80::f816:3eff:feb3:bd56 dev ens3 proto ra metric 1024 expires 260sec hoplimit 64 pref medium Though the ping6 from VM to hypervisor doesn't work: root@ubuntu:~# ping6 fd12:67:1::1 -c4 PING fd12:67:1::1 (fd12:67:1::1): 56 data bytes --- fd12:67:1::1 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss I'm able to tcpdump inside the router1 netns and see that request packet is passing there, but can't see any reply packets: $ sudo ip netns exec qrouter-5172472c-bbe7-4907-832a-e2239c8badb4 tcpdump -l -i any icmp6 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 21:29:29.351358 IP6 fd12:67:1:1:f816:3eff:fe0e:17c3 > fd12:67:1::1: ICMP6, echo request, seq 0, length 64 21:29:30.033316 IP6 fe80::f816:3eff:feb3:bd56 > fe80::f816:3eff:fe0e:17c3: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe0e:17c3, length 32 21:29:30.035807 IP6 fe80::f816:3eff:fe0e:17c3 > fe80::f816:3eff:feb3:bd56: ICMP6, neighbor advertisement, tgt is fe80::f816:3eff:fe0e:17c3, length 24 21:29:30.353646 IP6 fd12:67:1:1:f816:3eff:fe0e:17c3 > fd12:67:1::1: ICMP6, echo request, seq 1, length 64 21:29:31.355410 IP6 fd12:67:1:1:f816:3eff:fe0e:17c3 > fd12:67:1::1: ICMP6, echo request, seq 2, length 64 21:29:32.357239 IP6 fd12:67:1:1:f816:3eff:fe0e:17c3 > fd12:67:1::1: ICMP6, echo request, seq 3, length 64 The same happens from hypervisor to VM. I only acan see the request packets, but no reply packets. Thanks in advance, Lucio Seki

5 12

[openstack-dev] [neutron]IPv6 Prefix Delegation could not activated in newest version Neutron
by Shuai Zhao 16 Sep '19

16 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 0

[neutron] Bug deputy report week of September 9th
by Miguel Lavalle 15 Sep '19

15 Sep '19

Hi, I was the bug deputy for the week of September 9th. Here's the list of what we got reported: Critical: - https://bugs.launchpad.net/neutron/+bug/1843413 neutron-tempest-iptables_hybrid-fedora job is failing with RETRY_LIMIT constantly Status: Assigned to slaweq. Job was made non-voting temporarily while bug is fixed High: - https://bugs.launchpad.net/neutron/+bug/1843478 Mitigate frequent fixtures._fixtures.timeout.TimeoutException in UTs and FTs Status: Assigned to ralonsoh: Proposed fix: https://review.opendev.org/#/c/681432/ Medium: - https://bugs.launchpad.net/neutron/+bug/1843418 Functional tests shouldn't fail if kill command will have "no such process" during cleanup Status: Assigned to ralonsoh. Proposed fix: https://review.opendev.org/#/c/681671/ - https://bugs.launchpad.net/neutron/+bug/1843425 br-int lose flows ephemerally due to unnecessary flow operation Status: In progress. Proposed fix: https://review.opendev.org/#/c/681462/ - https://bugs.launchpad.net/neutron/+bug/1843428 List port by mac address is case sensitive Status: Fix in progress. Proposed fix: https://review.opendev.org/#/c/681390 - https://bugs.launchpad.net/neutron/+bug/1843446 Implement "kill" operation using python method os.kill() Status: Assigned to ralonsoh: Proposed fix: https://review.opendev.org/#/c/681671/ - https://bugs.launchpad.net/neutron/+bug/1843870 ovsdb monitor ignores modified ports Status: proposed fix: https://review.opendev.org/#/c/681984 - https://bugs.launchpad.net/neutron/+bug/1843889 Windows: IPv6 tunnel endpoints Status: proposed fix: https://review.opendev.org/#/c/682031 Incomplete: - https://bugs.launchpad.net/neutron/+bug/1843359 The iptables rules are covered when add a port from the FW group Status: requested more data from submitter - https://bugs.launchpad.net/neutron/+bug/1843801 metadata-proxy process stops listening on port 80 Status: Incomplete. Submitter was directed to use haproxy >= 1.8.15 Invalid: - https://bugs.launchpad.net/neutron/+bug/1843379 Tagging is not work for tags of QoS Policy Status: submitter was using invalid resource for the request RFE: - https://bugs.launchpad.net/neutron/+bug/1843165 RFE: Adding support for direct ports with qos in ovs Status: Under discussion with submitter - https://bugs.launchpad.net/neutron/+bug/1843924 [RFE] Create optional bulk resource_extend Status: Under discussion with submitter

1 0