April 2019 - openstack-discuss - lists.openstack.org

[openstack-ansible] Retirement of unused OpenStack Ansible roles
by Guilherme Steinmüller 20 May '19

20 May '19

Hello all, We have been discussing about some of our roles that are not maintained for a while, some of them are not even integrated with our main repository. In order to the team to focus on performance and stability of the roles that has been actively used, we are discussing about retiring the unused ones. The roles are the following: openstack-ansible-os_monasca openstack-ansible-os_monasca-agent openstack-ansible-os_zaqar openstack-ansible-os_watcher openstack-ansible-os_almanach openstack-ansible-os_molteniron openstack-ansible-os_searchlight We would love to help if someone wants to pick one or some of them to keep our variety of roles. If we don't hear back, we'll retire those roles out of OpenStack Ansible. Thank you Guilherme Steinmüller

6 11

OpenStack User Survey 2019
by Jimmy Mcarthur 16 May '19

16 May '19

It's time for the OpenStack User Survey <https://www.openstack.org/user-survey> [1]! In an effort to create less work for our community, in 2018 we moved to an annual, rather than a bi-annual report. If you run an OpenStack deployment, now is the time to share details about how you run the software and your thoughts on ways that the community can improve the software. Your feedback matters and it's shared directly with the PTLs and community leaders that work to build OpenStack! We had some good community feedback on the last survey and ended up with only minor updates from 2018. Below you can see a list of changes that we've incorporated: * "Which new/emerging technologies are you interested in using or seeing integrated with OpenStack?" o Added options for "AI/ML" and "5G" * Deleted the question "Are you interested in helping our interoperability efforts by using RefStack to test your cloud capabilities?" * "Which tools are you using to deploy / manage this cluster?" o Added the word "manage" to the question as tools can be used for both o Add "TripleO" and "Container-based orchestration" as options o Created a new "Please specify" if "Other tools" is chosen * "Which container orchestration or Platform-as-a-Service (PaaS) tools are you using to manage applications on this OpenStack deployment?" o Added "container orchestration or " to question * "Which OpenStack Network (Neutron) drivers are you using?" o Add Calico as an answer * "Which compatibility APIs does this deployment support?" o Added the option "This deployment doesn't use compatibility APIs" * Please note: This year, we will not be including the hardware and software vendor questions in the report or analytics dashboard due to the potential for the data to be misinterpreted. * *In addition to the question modifications above, we reached out to PTLs to ask for their feedback and guidance on the project specific questions of the survey. We've modified or added those questions as noted below: *Keystone* This will be a question where respondents can rank their choices and will follow their existing question: * Which of the following initiatives would be most beneficial for your deployment? You can rank items by priority with items at the top being most important and items at the bottom being least important. o Improved performance o Better support for synchronizing multiple keystone regions o Read-only RBAC roles o More flexible federated mappings o Improved fine-grained access control o Better support for domain administrators o Improved usability of keystone outside of an OpenStack environment Glance Changed existing question to: * "Multi back-ends feature will stay Experimental in Stein release. How badly this affect your deployment plans? Any details how you’re planning to use it would be helpful.” *Ironic* Changed existing question to: * "What would you find most useful if it was part of Ironic?" *Swift* Changed existing question to: * What features of Swift are you currently using (or have plans to use in the next 12 months)? (select all that apply o S3 compatibility o Dynamic Large Objects o Static Large Objects o Temporary URLs o Data-at-rest encryption o Multiple storage policies o Multi-region clusters o Explicit data placement (composite rings) o Container sync o Static websites or CORS o Symlinks o Quotas o Object versioning If you have further questions, concerns, please let us know. Cheers, Jimmy and Allison [1] https://www.openstack.org/user-survey

7 14

[PTL][SIG][WG] PTG Team Photos
by Kendall Nelson 15 May '19

15 May '19

Hello! If your team is attending the PTG and is interested in having a team photo taken, here is the signup[1]! There are slots Thursday and Friday from 10:00 AM to 4:30 PM. The location is TBD but will likely be close to where registration will be. I'll send an email out the day before with a reminder of your time slot and an exact location. -Kendall (diablo_rojo) [1] https://docs.google.com/spreadsheets/d/1DgsRHVWW2YLv7ewfX0M21zWJRf4wUfPG4ff…

5 10

[devstack][stein][masakari]Using Masakari in multihost devstack stein setup
by Sanjay K 13 May '19

13 May '19

Hi all, I have been trying to setup Masakari in a 3 node setup - 1 controller + 2 computes with minimal openstack services installed using devstack stable/stein version. All these 3 nodes are Ubuntu 16.04 VMs. I have included Masakari plugin in controller's local.conf file and included masakari-monitor in both compute node's local.conf file. I want to test out VM/process failure in my test environment. To do so, when I kill one of the qemu process created for one instance (cirros 256 flavor VMs) on one of the compute with root user login, I did not see any notification under my horizon/instance-ha section for this (I have already created Segments, Hosts under instance-ha in horizon). Also the killed process is not restarted by Masakari. I have asked the same question in openstack forum, but not got a single response. masakari-notification-on-process-failure <https://ask.openstack.org/en/question/121490/masakari-notification-on-proce…> Whether any additional services related to Masakari need to be configured on compute hosts to detect failures since I did not find exactly the documentation related inside devstack for this. Please let me know if I am missing anything my set up. Any helps and pointers are most appreciated. thank you for your reply. best regards

2 4

[placement][nova][ptg] resource provider affinity
by Chris Dent 09 May '19

09 May '19

Spec: https://review.openstack.org/650476 >From the commit message: To support NUMA and similar concepts, this proposes the ability to request resources from different providers nested under a common subtree (below the root provider). There's much in the feature described by the spec and the surrounding context that is frequently a source of contention in the placement group, so working through this spec is probably going to require some robust discussion. Doing most of that before the PTG will help make sure we're not going in circles in person.k Some of the areas of potential contention: * Adequate for limited but maybe not all use case solutions * Strict trait constructionism * Evolving the complexity of placement solely for the satisfaction of hardware representation in Nova * Inventory-less resource providers * Developing new features in placement before existing features are fully used in client services * Others? I list this not because they are deal breakers or the only thing that matters, but because they have presented stumbling blocks in the past and we may as well work to address them (or make an agreement to punt them until later) otherwise there will be lingering dread. And, beyond all that squishy stuff, there is the necessary discussion over the solution described in the spec. There are several alternatives listed in the spec, and a few more in the comments. We'd like to figure out the best solution that can actually be done in a reasonable amount of time, not the best solution in the absolute. Discuss! -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

10 37

[nova] Stein regressions
by Matt Riedemann 08 May '19

08 May '19

Hey cool cats, I know we just released Stein last week so what better time to write an email about a bunch of Stein regressions?! I wanted to dump this in the list so (a) I don't lose track of them all and (b) other people are aware and get involved. In no particular order: 1. https://bugs.launchpad.net/nova/+bug/1822801 There is a patch being worked: https://review.openstack.org/#/c/649345/ The workaround for this would be to disable the _heal_instance_info_cache periodic in nova-compute services that manage baremetal nodes by setting the heal_instance_info_cache_interval value to 0. 2. https://bugs.launchpad.net/nova/+bug/1824435 We have a re-create scenario for this in devstack (noted in the bug report). I've been unable to recreate in a functional test, possibly because of how sqlite deals with NULL values in unique constraints differently from mysql. I would have thought this regression test [1] would have hit it but it didn't. There are some options for fixing this, some more hacky than others, e.g.: https://review.openstack.org/#/c/653065/ Need some input from others on fixing that bug in maybe a less hacky way. 3. https://bugs.launchpad.net/nova/+bug/1825034 I found this when writing [1] to try and recreate the previous bug 1824435. I have a series up for this starting with a recreate patch [1]. The fix on top is one of a few options I detailed in the bug report. It's not pretty but it works. The workaround for this would be to archive deleted records but you'd have to do that after each run of the online data migration which is not great. 4. https://bugs.launchpad.net/nova/+bug/1825020 I just triaged this a couple of hours ago. I plan on writing a functional regression recreate test since the recreate scenario seems pretty easy - try to resize a volume-backed server where the new flavor has a smaller disk than the old flavor. The fix should also be relatively straight-forward. -- Once we get fixes landed and backported to stable/stein for these bugs we should do a patch release ASAP. [1] https://review.openstack.org/#/c/653098/ -- Thanks, Matt

1 2

[oslo][oslo-messaging][nova] Stein nova-api AMQP issue running under uWSGI
by iain.macdonnell＠oracle.com 08 May '19

08 May '19

Is anyone running Stein nova-api under uWSGI? I'm trying to do this, in exactly the same way as I did with Rocky, but encountering a new problem... The symptom is intermittent failure of API operations that involve RPC calls - notably getting the noVNC console URL for an instance. The nova-api log shows RPC timeouts and "connection reset by peer" for AMQP. I've ruled out environmental issues, as a Rocky installation on the same hosts works fine. With oslo debug enabled, I see that the first API call causes a AMQP connections to be established, and the RPC call gets its reply, and all is well... but there are no heartbeats logged after that. 3 minutes later, rabbitmq-server reports that it has received no heartbeats, and drops the connection. On a subsequent API call (but not before), nova-api logging "connection reset by peer" and the RPC call times out. With the Rocky code, once the first API call causes the AMQP connections to be established, regular heartbeats start happening, the connections are maintained, and subsequent API calls work as expected. It seems like a lockup in a thread that's supposed to maintain the AMQP connection, or something. I tried to use SIGUSR2 to trigger guru meditation, but it seems that uWSGI has its own interpretation of SIGUSR2, so nova-api never sees it (anyone know a way around this?). Running nova-api as a standalone service, instead of under uWSGI, the problem does not occur (I see the heartbeats, and everything works fine). I've tried updating oslo-messaging (and python-amqp) on a Rocky installation to the Stein version, but the problem does not reproduce. Ideas? ~iain

8 18

[octavia][taskflow] Adaption of persistence/jobboard (taskflow expert review needed)
by Anna Taraday 08 May '19

08 May '19

Hello everyone! I was looking at the topic of usage taskflow persistence and jobboard in Octavia [1]. I created a simple PoC to check what should be done to enable this functionality [2] . >From what I see, taskflow expects that data, which will be stored in persitence backend/jobboard backend, is a dict or an object easily converted to dicts [3] (error [3.1]) Also functions that creates flow should be importable [4] (error [4.1]). These two points lead to refactor required for Octavia to enable taskflow persistence and jobboard: 1) Convert data which is passed between flows in dicts, at this moment it is db objects with links to other db objects. 2) Create importable flow functions. As far as I see the only OpenStack project which adapted taskflow persistence is poppy [5] I'm looking for taskflow expect to take a look at all this and give some comments - whether I am correct or missing something. Thank you for your time in advance! [1] - https://storyboard.openstack.org/#!/story/2005072 [2] - https://review.openstack.org/#/c/647406 [3] - https://github.com/openstack/taskflow/blob/master/taskflow/persistence/back… [3.1] - http://paste.openstack.org/show/749530/ [4] - https://docs.openstack.org/taskflow/latest/_modules/taskflow/engines/helper… [4.1] - http://paste.openstack.org/show/749527/ [5] - https://github.com/openstack/poppy -- Regards, Ann Taraday Mirantis, Inc

2 3

[kolla] Virtual PTG scheduling poll
by Mark Goddard 07 May '19

07 May '19

Hi, Since most of the Kolla team aren't attending the PTG, we've agreed to hold a virtual PTG. We agreed to start with two 4 hour sessions. We can finish early or schedule another session, depending on how we progress. We'll use some video conferencing software TBD. I've created a Doodle poll here [2], please fill it in if you hope to attend. Times are in UTC. Please continue to fill out the planning Etherpad [1]. Thanks, Mark [1] https://etherpad.openstack.org/p/kolla-train-ptg [2] https://doodle.com/poll/adk2smds76d8db4u

1 2

[blazar] Scheduling a new Blazar IRC meeting for the Americas
by Pierre Riteau 06 May '19

06 May '19

Hello, Contributors to the Blazar project are currently mostly from Europe or Asia. Our weekly IRC meeting at 0900 UTC is a good match for this group. To foster more contributions, I would like to schedule another IRC meeting in the morning for American timezones, probably every two weeks to start with. I am thinking of proposing 1600 UTC on either Monday, Tuesday, or Thursday, which doesn't appear to conflict with closely related projects (Nova, Placement, Ironic). If there is anyone who would like to join but cannot make this time, or has a preference on which day, please let me know. I will wait for a few days before requesting a meeting slot. Thanks, Pierre

1 1