January 2019 - openstack-discuss - lists.openstack.org

Denver Summit CFP Closing Tomorrow
by Ashlee Ferguson 23 Jan '19

23 Jan '19

Hi everyone, The CFP closes in less than 48 hours, so make sure to submit your presentations, panels, and workshops <https://www.openstack.org/summit/denver-2019/call-for-presentations> for the Denver Open Infrastructure Summit before tomorrow, January 23 at 11:59pm PT (January 24 at 7:59am UTC). SUBMIT YOUR PRESENTATION <https://www.openstack.org/summit/denver-2019/call-for-presentations> Tracks: AI, Machine Learning & HPC CI/CD Container Infrastructure Edge Computing Hands-on Workshops Open Development (formerly Open Source Community) Open Infrastructure Basics Private & Hybrid Cloud Public Cloud Security - NEW! Telecom & NFV Full track descriptions <https://www.openstack.org/summit/denver-2019/summit-categories> For tips on your submissions, check out these articles for some advice from the Summit Programming Committees— http://superuser.openstack.org/articles/tips-for-the-open-infrastructure-su… http://superuser.openstack.org/articles/tips-open-development-track-denver-… http://superuser.openstack.org/articles/tips-for-talks-on-the-public-cloud-… Denver Summit registration <https://openinfrasummitandptgdenver.eventbrite.com/> and sponsor sales are currently open. Learn more <https://www.openstack.org/summit/denver-2019> Please email speakersupport(a)openstack.org <mailto:speakersupport@openstack.org> with any questions or feedback. Cheers, Ashlee Ashlee Ferguson OpenStack Foundation ashlee(a)openstack.org

1 0

[tripleo][openstack-ansible] collaboration on os_tempest role update VII - Jan 22, 2019
by Chandan kumar 23 Jan '19

23 Jan '19

Hello, Here is the seventh update (Jan 15 to Jan 22, 2019) on collaboration on os_tempest[1] role between TripleO and OpenStack-Ansible projects. Things got merged: os_tempest: * Add support for aarch64 images - https://review.openstack.org/#/c/620032/ * Configuration drives don't appear to work on aarch64+kvm - https://review.openstack.org/#/c/626592/ * Fix tempest workspace path - https://review.openstack.org/#/c/628182/ * Add libselinux-python package for Red Hat distro - https://review.openstack.org/#/c/631203/ * Use usr/local/share/ansible/roles for data_files - https://review.openstack.org/#/c/630917/ * Use tempest_domain_name var for setting domain - https://review.openstack.org/#/c/630957/ * Rename tempest_public_net_physical_{type to name} - https://review.openstack.org/#/c/631183/ * Add tempest_interface_name var for setting interface - https://review.openstack.org/#/c/630942/ ansible-config_template * Use usr/share/ansible/plugins for data_files - https://review.openstack.org/631214 ansible-role-python_venv_build * Use usr/local/share/ansible/roles for data_files - https://review.openstack.org/#/c/631777/ openstack-ansible-tests * Setup clouds.yaml on tempest node - https://review.openstack.org/631794 Tripleo-spec * New spec for stein: os_tempest tripleo integration - https://review.openstack.org/630654 Summary: * We have cleaned up os_tempest cloudname and network related vars, fixed tempest workspace upgrade issue and os_tempest got support of aarch64 images and nova Configuration drives. * Tripleo os_tempest spec published: https://specs.openstack.org/openstack/tripleo-specs/specs/stein/ostempest-t… Things in Progress: os_tempest * Always generate stackviz irrespective of tests pass or fail - https://review.openstack.org/631967 * Add telemetry distro plugin install for aodh - https://review.openstack.org/632125 * Added tempest.conf for heat_plugin - https://review.openstack.org/632021 * Use the correct heat tests - https://review.openstack.org/630695 * Use tempest_cloud_name in tempestconf - https://review.openstack.org/631708 * Adds tempest run command with --test-list option - https://review.openstack.org/631351 os_tempest integration with Tripleo * Added requirements for integrating os_tempest role - https://review.openstack.org/628421 * Run tempest using os_tempest role in standalone job - https://review.openstack.org/627500 * Use os_tempest for running tempest on standalone - https://review.openstack.org/628415 Upcoming week: * We are able to run tempest in Triplo CI standalone test results are here: http://logs.openstack.org/00/627500/65/check/tripleo-ci-centos-7-standalone… * We will try to finish os_tempest integration with tripleo and heat support in os_tempest. Thanks to odyssey4me, cloudnull, jrosser (a lot of help on different patches), Panda and Sagi from Tripleo CI team pabelanger and dmsimard on figuring out os_tempest dependencies, action_plugins and nested ansible. Here is the 6th update [2]. Have queries, Feel free to ping us on #tripleo or #openstack-ansible channel. Links: [1.] http://git.openstack.org/cgit/openstack/openstack-ansible-os_tempest [2.] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001730.… Thanks, Chandan Kumar

2 1

[Trove] State of the Trove service tenant deployment model
by Michael Richardson 23 Jan '19

23 Jan '19

Hi all, Is anyone aware of the current state of the "service tenant" deployment model for Trove, and whether it is a viable option; or whether the historical method of customer tenants/projects are still the recommended approach? Any and all comments/thoughts/gotchas would be most appreciated! Cheers, Michael

3 6

Fwd: [OpenStack Foundation] 2019 Individual Director election and Bylaws amendment results
by Chris Morgan 23 Jan '19

23 Jan '19

Congrats to the new openstack foundation directors! Just FYI the following went to the foundation mailing list. Chris From: Jonathan Bryce <jonathan(a)openstack.org> Date: Fri, Jan 18, 2019, 12:42 Subject: [OpenStack Foundation] 2019 Individual Director election and Bylaws amendment results To: <foundation(a)lists.openstack.org> Hello everyone, The 2019 election of Individual Directors has closed. Results are available at the following link: https://www.bigpulse.com/pollresults?code=1336400LYwRuQQZqR72BJRpKJYV The Bylaws amendments have now been passed by the Individual Member class. The elected and appointed directors will be seated at the Board meeting at the end of January. Congratulations to our new and returning directors. We actually had the highest number of voters for any of our elections participate this year, so thank you to everyone for joining in the process. Jonathan 210-317-2438 Individual Directors ----------------------------------------- Tim Bell ChangBo Guo Sean McGinnis Prakash Ramchandran Allison Randal Egle Sigler Monty Taylor Shane Wang Platinum Directors ----------------------------------------- Alan Clark Ruan He Anni Lai Mark McLoughlin Chris Price Imad Sousou Brian Stein Ryan Van Wyk Gold Directors ----------------------------------------- Mark Baker Johan Christenson Robert Esker Clemens Hardewig Arkady Kanevsky JunWei Liu Vijoy Pandey Joseph Wang _______________________________________________ Foundation mailing list Foundation(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation -- Chris Morgan <mihalis68(a)gmail.com>

2 1

About gitignore policy.
by Natal Ngétal 23 Jan '19

23 Jan '19

Hi everyone, I would to have more information about the .gitignore file policy. First I have made a patch to ignore backup files from vim editor. The patches was refused because that doesn't respect the OpenStack policy: https://review.openstack.org/#/c/631790/ https://review.openstack.org/#/c/631789/ The policy is available in a cookiecutter template repository: https://git.openstack.org/cgit/openstack-dev/cookiecutter/tree/%7b%7bcookie… Then I have started to make patch, to align OpenStack projects with this policy: https://review.openstack.org/#/c/632086/ In nova project the patch was refused, the first reason was we have already talk about this subject. The second reason was this policy is only for the new projects. Oslo is not a new project and is follow this policy. I know is not a priority subject, but I just want understand. For me a policy must be followed by all projects, to harmonize all, but maybe I wrong. For example, in this case, I would to know what is the rules? The new projects must follow the policy but not the old ones? In this case, what the rules for old projects and can we defined also an policy for it? Thanks in advance for your help. My best regards

4 4

[qa] dynamic credentials with the tempest swift client
by Udi Kalifon 23 Jan '19

23 Jan '19

Hello. I am developing GUI tests (Selenium) for the openstack director. I am now trying to make use of tempest Swift client in one of the tests which needs to fetch a file from the tripleo plans. I added this code in our base class to access the client: class GUITestCase(test.BaseTestCase): credentials = ('admin', 'primary') @classmethod def setup_clients(cls): super(GUITestCase, cls).setup_clients() # Clients for Swift cls.account_client = cls.os_admin.account_client cls.container_client = cls.os_admin.container_client cls.object_client = cls.os_admin.object_client I then try to list the objects in the "overcloud" container, which is where the default plans are found: class TestSwift(GUITestCase): def test_swift(self): (resp, body) = self.container_client.list_container_objects( "overcloud") print resp print body It returns a "not found" error. I'm pretty sure that the reason for it not finding the container (which is definitely there) is that it creates a project and a user for itself, and uses those credentials for its interactions with the undercloud. I can see the POST calls in tempest.log that show that it's creating itself the dynamic credentials: INFO tempest.lib.common.rest_client [req-54a... ] Request (TestSwift:setUpClass): 201 POST http://192.168.24.3:35357/v3/projects 0.365s INFO tempest.lib.common.rest_client [req-d3f... ] Request (TestSwift:setUpClass): 201 POST http://192.168.24.3:35357/v3/users 0.493s INFO tempest.lib.common.rest_client [req-480... ] Request (TestSwift:setUpClass): 200 GET http://192.168.24.3:35357/v3/roles 0.297s INFO tempest.lib.common.rest_client [req-e0a... ] Request (TestSwift:setUpClass): 204 PUT http://192.168.24.3:35357/v3/projects/9e1e6b33dcbd4aebb546c56a7258d5e0/user… 0.270s INFO tempest.lib.common.dynamic_creds [-] *Acquired dynamic creds:* credentials: Credentials: {'username': u'tempest-TestSwift-1494291785', 'project_name': u'tempest-TestSwift-1494291785', 'project_domain_id': u'default', 'user_domain_id': u'default', 'tenant_id': u'9e1e6b33dcbd4aebb546c56a7258d5e0', 'user_domain_name': u'Default', 'domain_name': u'Default', 'tenant_name': u'tempest-TestSwift-1494291785', 'user_id': u'cc715537a0c048b7a8692a0c8304b94d', 'project_id': u'9e1e6b33dcbd4aebb546c56a7258d5e0', 'domain_id': u'default', 'project_domain_name': u'Default'}, Network: None, Subnet: None, Router: None So I'm looking for a way to utilize the client without it automatically creating itself dynamic credentials; it has to use the already-existing admin credentials on the admin project in order to see the container with the plans. What's the right way to do that, please? Thanks a lot in advance! Regards, Udi Kalifon; Senior QE; RHOS-UI Automation

3 4

[oslo] Meetings next two weeks
by Ben Nemec 23 Jan '19

23 Jan '19

I had some last-minute travel come up for next week (the 28th-1st) which means I may have spotty availability. I'm not sure if I'll be able to run the meeting on Monday. I guess you can watch for courtesy pings and if they don't happen then chances are I couldn't. :-) The next week (4th-8th) I'm on vacation so I definitely won't be around. Unless someone else wants to run the meeting that one will not happen for sure. -Ben

1 0

UC Election - Looking for Election Officials
by Matt Van Winkle 23 Jan '19

23 Jan '19

Hey Stackers, We are getting ready for the Winter UC election and we need to have at least two Election Officials. I was wondering if you would like to help us on that process. You can find all the details of the election at *https://governance.openstack.org/uc/reference/uc-election-feb2019.html <https://governance.openstack.org/uc/reference/uc-election-feb2019.html>*. I do want to point out to those who are new that Election Officials are unable to run in the election itself but can of course vote. The election dates will be: January 21 - February 03, 05:59 UTC: Open candidacy for UC positions February 04 - February 10, 11:59 UTC: UC elections (voting) Please, reach out to any of the current UC members or simple reply to this email if you can help us in this community process. Thanks, OpenStack User Committee Amy, Leong, Matt, Melvin, and Joseph

4 4

[Release-job-failures][puppet] Release of openstack/puppet-aodh failed
by Jean-Philippe Evrard 22 Jan '19

22 Jan '19

Hello, puppet-aodh failed [3] to release due to an issue in the upload- puppetforge role, for a permission issue [0]. Maybe a privilege escalation is required in [1], or a deeper analysis needs to be done. The role was changed 5 days ago [2], so I am not sure this code had the chance to be tested in post release pipelines. Could someone have a look, please? Thank you in advance. Jean-Philippe Evrard (evrardjp) [0]: http://logs.openstack.org/61/617ffad84b633618490ca1023f8a31d9694b31a9/relea… [1]: http://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/upload-p… [2]: https://github.com/openstack-infra/zuul-jobs/commit/fd8ffc6711d6481e2fcd40d… [3]: http://lists.openstack.org/pipermail/release-job-failures/2019-January/0010…

2 2

[nova][ops] Problems disabling notifications on state changes
by Massimo Sgaravatto 22 Jan '19

22 Jan '19

I am disabling ceilometer on my OpenStack Ocata cloud. As fas as I understand, besides stopping the ceilometer services, I can also apply the following changes to nova.conf on the compute nodes: instance_usage_audit = True --> false notify_on_state_change = vm_and_task_state --> None I have a problem with the latter change: # grep ^notify_on_state_change /etc/nova/nova.conf notify_on_state_change=None but in the nova log: 2019-01-21 08:31:48.246 6349 ERROR nova ConfigFileValueError: Value for option notify_on_state_change is not valid: Valid values are [None, vm_state, vm_and_task_state], but found 'None' I have also tried setting notify_on_state_change=<None> but it complains that it is not a valid value I can simply comment that line, but I am afraid there is a problem somewhere Thanks, Massimo

2 2