July 2019 - openstack-discuss - lists.openstack.org

[keystone] Virtual Midcycle Planning
by Colleen Murphy 08 Jul '19

08 Jul '19

Hi team, As discussed in today's meeting, we will be having a virtual midcycle some time around milestone 2. We'll do two days with one three-hour session (with breaks) each day. We will do this over a video conference session, details of how to join will follow closer to the event. I've started a brainstorming etherpad: https://etherpad.openstack.org/p/keystone-train-midcycle-topics Please add discussion topics or hacking ideas to the etherpad and I will try to sort them. We need to decide on when exactly to hold the midcycle. I've created a doodle poll: https://doodle.com/poll/wr7ct4uhpw82sysg Please select times and days that you're available and then we'll try to schedule two back-to-back days (or at least two days in the same week) for the midcycle. Let me know if you have any questions or concerns. Colleen

1 1

[oslo] oslo.config /castellan poster review
by Moises Guimaraes de Medeiros 08 Jul '19

08 Jul '19

Hi, This week I'll be presenting a poster about oslo.config's castellan driver at EuroPython. I'd like to ask y'all interested in the subject to take a look at my poster. I'm planning to print it this Tuesday and I still have some spare space to fit a bit more. The latest version is available at: https://ep2019.europython.eu/media/conference/slides/m7RV4BB-protecting-sec… Thanks a lot! -- Moisés Guimarães Software Engineer Red Hat <https://www.redhat.com> <https://red.ht/sig>

4 3

[docs] Retire openstack/docs-specs
by Stephen Finucane 08 Jul '19

08 Jul '19

Hey, I'm proposing retiring docs-specs [1][2]. This hasn't been used in some time since most of our documentation now lives in individual project repositories and any work that would span these multiple projects would likely exist as a community goal, documented in those relevant repositories. I do not intend for the existing content to be removed - it simply won't be possible to add new specs. Let me know if anyone has a reason not to do this. If not, we'll get a move on with this next week. Stephen [1] https://opendev.org/openstack/docs-specs [2] https://review.opendev.org/#/c/668853/

2 1

[neutron] Bug deputy report (week starting on 2019-07-01)
by Bernard Cafarelli 08 Jul '19

08 Jul '19

Hi Neutrinos, time for a new cycle of bug deputy rotation, which means I was on duty last week, checking bugs up to 1835663 included Quite a few bugs in that list worth a read and further discussion: * port status changing to UP when changing the network name (and possible fallout on DHCP issues) * API currently allowing to set gateway outside of the subnet * How to handle external dependencies recommended version bumps (pyroute bump in queens fixing a memory leak) * possible issue in IPv6 address renewal since we started cleaning the dnsmasq leases file Critical: * Wrong endpoints config with configure_auth_token_middleware - https://bugs.launchpad.net/bugs/1834849 Removal of devstack deprecated option broke designate scenario job Fix merged: https://review.opendev.org/668447 High: * [Queens] Memory leak in pyroute2 0.4.21 - https://bugs.launchpad.net/neutron/+bug/1835044 we need a newer pyroute version Patches on requirements with DNM neutron one for testing in progress: https://review.opendev.org/668676 and https://review.opendev.org/668677 openstack-discuss thread: http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007545.html * Bulk-created ports ignore binding_host_id property - https://bugs.launchpad.net/neutron/+bug/1835209 Issue on bulk port creation work Fix in progress: https://review.opendev.org/#/c/665516/ * flood flow in br-tun table22 incorrect - https://bugs.launchpad.net/neutron/+bug/1835163 Linked to https://bugs.launchpad.net/neutron/+bug/1834979 (see below), this can cause hard to trace l2pop and dhcp issues No owner Medium: * Add ipam.utils.check_gateway_invalid_in_subnet unit tests - https://bugs.launchpad.net/neutron/+bug/1835448 Shows proper usage after bug https://bugs.launchpad.net/neutron/+bug/1835344 (see in Opinion section) Review in progress: https://review.opendev.org/669210 * Port status becomes active after updating network/subnet - https://bugs.launchpad.net/neutron/+bug/1834979 The port of a turned off VM will show as UP after a network modification (reproducer with network name) No owner * Some L3 RPCs are time-consuming especially get_routers - https://bugs.launchpad.net/neutron/+bug/1835663 Probably worth discussing in performance meeting? Incomplete: * Restart dhcp-agent cause IPv6 vm can't renew IP address, will lost minutes or hours - https://bugs.launchpad.net/neutron/+bug/1835484 Cleaning IPv6 addresses from dnsmasq leases file ( https://bugs.launchpad.net/neutron/+bug/1722126) apparently causes VM to loose its address on renewal Waiting for detailed logs, but if ipv6 experts can chime in Opinion: * neutron doesn't check the validity of gateway_ip as a subnet had been created - https://bugs.launchpad.net/neutron/+bug/1835344 How to handle gateway IP outside of the subnet? Discussion in the bug and related review: https://review.opendev.org/669030 Duplicate: * QoS plugin slows down get_ports operation - https://bugs.launchpad.net/neutron/+bug/1835369 Was filled close to https://bugs.launchpad.net/bugs/1834484 Regards, -- Bernard Cafarelli

1 1

[TripleO] Using TripleO standalone with ML2/OVS
by Slawek Kaplonski 08 Jul '19

08 Jul '19

Hi, I was trying to use TripleO standalone for development work in the way how Emilien described it in [1] and indeed it works quite well. Thx Emilien. But now, I’m trying to find out the way how to deploy it with Neutron using ML2/OVS instead of default in TripleO ML2/OVN. And I still don’t know how to do it :/ I know it’s my fault but maybe someone can help me with this and tell me what exactly options I should change there to deploy it with other Neutron backend? Thx in advance for any help. [1] https://my1.fr/blog/developer-workflow-with-tripleo/ — Slawek Kaplonski Senior software engineer Red Hat

3 2

[ops] [nova] [placement] Mismatch between allocations and instances
by Massimo Sgaravatto 08 Jul '19

08 Jul '19

I tried to check the allocations on each compute node of a Ocata cloud, using the command: curl -s ${PLACEMENT_ENDPOINT}/resource_providers/${UUID}/allocations -H "x-auth-token: $TOKEN" | python -m json.tool I found that, on a few compute nodes, there are some instances for which there is not a corresponding allocation. On another Rocky cloud, we had the opposite problem: there were allocations also for some instances that didn't exist anymore. And this caused problems since we were not able to use all the resources of the relevant compute nodes: we had to manually remove the fwrong" allocations to fix the problem ... I wonder why/how this problem can happen ... And how can we fix the issue ? Should we manually add the missing allocations / manually remove the wrong ones ? Thanks, Massimo

3 3

[qa][ptg][nova][cinder][keystone][neutron][glance][swift][placement] How to make integrated-gate testing (tempest-full) more stable and fast
by Ghanshyam Mann 07 Jul '19

07 Jul '19

Current integrated-gate jobs (tempest-full) is not so stable for various bugs specially timeout. We tried to improve it via filtering the slow tests in the separate tempest-slow job but the situation has not been improved much. We talked about the Ideas to make it more stable and fast for projects especially when failure is not related to each project. We are planning to split the integrated-gate template (only tempest-full job as first step) per related services. Idea: - Run only dependent service tests on project gate. - Tempest gate will keep running all the services tests as the integrated gate at a centeralized place without any change in the current job. - Each project can run the below mentioned template. - All below template will be defined and maintained by QA team. I would like to know each 6 services which run integrated-gate jobs 1."Integrated-gate-networking" (job to run on neutron gate) Tests to run in this template: neutron APIs , nova APIs, keystone APIs ? All scenario currently running in tempest-full in the same way ( means non-slow and in serial) Improvement for neutron gate: exlcude the cinder API tests, glance API tests, swift API tests, 2."Integrated-gate-storage" (job to run on cinder gate, glance gate) Tests to run in this template: Cinder APIs , Glance APIs, Swift APIs, Nova APIs and All scenario currently running in tempest-full in the same way ( means non-slow and in serial) Improvement for cinder, glance gate: excluded the neutron APIs tests, Keystone APIs tests 3. "Integrated-gate-object-storage" (job to run on swift gate) Tests to run in this template: Cinder APIs , Glance APIs, Swift APIs and All scenario currently running in tempest-full in the same way ( means non-slow and in serial) Improvement for swift gate: excluded the neutron APIs tests, - Keystone APIs tests, - Nova APIs tests. Note: swift does not run integrated-gate as of now. 4. "Integrated-gate-compute" (job to run on Nova gate) tests to run is : Nova APIs, Cinder APIs , Glance APIs ?, neutron APIs and All scenario currently running in tempest-full in same way ( means non-slow and in serial) Improvement for Nova gate: excluded the swift APIs tests(not running in current job but in future, it might), Keystone API tests. 5. "Integrated-gate-identity" (job to run on keystone gate) Tests to run is : all as all project use keystone, we might need to run all tests as it is running in integrated-gate. But does keystone is being unsed differently by all services? if no then, is it enough to run only single service tests say Nova or neutron ? 6. "Integrated-gate-placement" (job to run on placement gate) Tests to run in this template: Nova APIs tests, Neutron APIs tests + scenario tests + any new service depends on placement APIs Improvement for placement gate: excluded the glance APIs tests, cinder APIs tests, swift APIs tests, keystone APIs tests Thoughts on this approach? The important point is we must not lose the coverage of integrated testing per project. So I would like to get each project view if we are missing any dependency (proposed tests removal) in above proposed templates. - https://etherpad.openstack.org/p/qa-train-ptg -gmann

7 11

how to install masakari on centos 7
by Vu Tan 07 Jul '19

07 Jul '19

Hi, I would like to use Masakari and I'm having trouble finding a step by step or other documentation to get started with. Which part should be installed on controller, which is should be on compute, and what is the prerequisite to install masakari, I have installed corosync and pacemaker on compute and controller nodes, , what else do I need to do ? step I have done so far: - installed corosync/pacemaker - install masakari on compute node on this github repo: https://github.com/openstack/masakari - add masakari in to mariadb here is my configuration file of masakari.conf, do you mind to take a look at it, if I have misconfigured anything? [DEFAULT] enabled_apis = masakari_api # Enable to specify listening IP other than default masakari_api_listen = controller # Enable to specify port other than default masakari_api_listen_port = 15868 debug = False auth_strategy=keystone [wsgi] # The paste configuration file path api_paste_config = /etc/masakari/api-paste.ini [keystone_authtoken] www_authenticate_uri = http://controller:5000 auth_url = http://controller:5000 auth_type = password project_domain_id = default user_domain_id = default project_name = service username = masakari password = P@ssword [database] connection = mysql+pymysql://masakari:P@ssword@controller/masakari

1 0

[masakari] Run masakari-hostmonitor into Docker container
by gaetan.trellu＠incloudus.com 06 Jul '19

06 Jul '19

Hi, I'm integrating Masakari into Kolla and Kolla Ansible projects but I'm facing an issue related to masakari-hostmonitor. Based on masakari-monitors code[1], "systemctl status" command is used to check if pacemaker, pacemaker-remote and corosync are running. Having systemd running into Docker container is not the best solution. Does any of you has been able to run masakari-monitor into Docker container ? Thanks for your help. Gaëtan - [1] https://github.com/openstack/masakari-monitors/blob/26d558333d9731ca06da09b…

3 2

[neutron][requirements] Pyroute2 stable/queens upper version (0.4.21) has a memory leak
by Rodolfo Alonso 06 Jul '19

06 Jul '19

Hello folks: As reported in [1], we have found a memory leak in Pyroute stable/queens upper version (0.4.21). This memory leak is reproducible both with Python 2.7 and Python 3.6 (I didn't test 3.5 or 3.7). The script used is [2]. Using "pmap" to read the process memory map (specifically the "total" value), we can see an increase of several MB per minute. This problem is not present in version 0.5.2 (stable/rocky upper-requirements) I know that in stable releases, the policy established [3] is only to modify those external libraries in case of security related issues. This is not exactly a security breach but can tear down a server along the time. I submitted a patch to bump the version in stable/queens [4] and another one to test this change in the Neutron CI [5]. Is it possible to merge [4]? Regards. [1] https://bugs.launchpad.net/neutron/+bug/1835044 [2] http://paste.openstack.org/show/753759/ [3] https://docs.openstack.org/project-team-guide/stable-branches.html [4] https://review.opendev.org/#/c/668676/ [5] https://review.opendev.org/#/c/668677/

2 1