March 2019 - openstack-discuss - lists.openstack.org

designate-dashboard 8.0.0.0rc1 (stein)
by no-reply＠openstack.org 19 Mar '19

19 Mar '19

Hello everyone, A new release candidate for designate-dashboard for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/designate-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/designate-dashboard/log/?h=stable/… Release notes for designate-dashboard can be found at: https://docs.openstack.org/releasenotes/designate-dashboard/

1 0

[all][elections] Project Team Lead Election Conclusion and Results
by Kendall Nelson 19 Mar '19

19 Mar '19

Hello Everyone! Thank you to the electorate, to all those who voted and to all candidates who put their name forward for Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability thank you to all those who make this process possible. Now for the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Ec2 Api : Andrey Pavlov * Sahara : Jeremy Freudberg * Vitrage : Ifat Afek * Solum : Rong Zhu * Freezer : geng chc2 * Glance : Erno Kuvaja * Senlin : XueFeng Liu * Barbican : Douglas Mendizábal * Cinder : Jay Bryant * Placement : Chris Dent * Loci : Chris Hoge * OpenStack Helm : Pete Birley * Requirements : Matthew Thode * Qinling : Lingxian Kong * Trove : Lingxian Kong * Cyborg : Sundar Nadathur * Ironic : Julia Kreger * OpenStackAnsible : Mohammed Naser * OpenStack Charms : James Page * Storlets : Kota Tsuyuzaki * Puppet OpenStack : Zhong Shengping * Kuryr : Daniel Mellado * Quality Assurance : Ghanshyam Mann * Tripleo : Alex Schultz * Chef OpenStack : Jens Harbott * Cloudkitty : Luka Peschke * Tacker : dharmendra kushwaha * Designate : Graham Hayes * Kolla : Mark Goddard * Masakari : Sampath Priyankara * Swift : Tim Burke * Watcher : canwei li * Neutron : Miguel Lavalle * Karbor : Pengju Jiao * Heat : Rico Lin * Keystone : Colleen Murphy * OpenStackClient : Dean Troyer * Oslo : Ben Nemec * Documentation : Stephen Finucane * Rally : Andrey Kurilin * Monasca : Witek Bedyk * Horizon : Ivan Kolodyazhny * Murano : Rong Zhu * Tricircle : baisen song * Searchlight : Trinh Nguyen * OpenStackSDK : Monty Taylor * Nova : Eric Fried * Release Management : Tony Breeds * Congress : Eric Kao * I18n : Ian Y. Choi * Manila : Thomas Barron * Mistral : Renat Akhmerov * Zun : Feng Shengqin * Winstackers : Claudiu Belu * Octavia : Adam Harwell * Magnum : Feilong Wang * Adjutant : Adrian Turjak * Infrastructure : Clark Boylan * Packaging Rpm : Thomas Bechtold * Blazar : Pierre Riteau Elections: * OpenStack_Charms: https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_ca2c11f0f83ce84d * Nova: https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_b03df704c3012e18 Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all involved in the PTL election process, -Kendall Nelson(diablo_rojo)

1 0

[tripleo][openstack-ansible][kolla-ansible] Packaging Ansible role and action_plugin for consuming outside OpenStack easily
by Chandan kumar 19 Mar '19

19 Mar '19

Hello, >From last few months, we have started using openstack-ansible-os_tempest role developed under openstack-ansible project in TripleO for running tempest os_tempest[1] role depends on ansible-role-python_venv_build[2] role and ansible-config_template[3] action plugin. In order to install these dependencies with os_tempest, we have changed the setup.cfg [data_files] section based on tripleo-quickstart setup.py file https://github.com/openstack/tripleo-quickstart/blob/master/setup.cfg#L27 [files] data_files = usr/local/share/tripleo-quickstart/roles = roles/* for python_venv_build and ansible-config_template, we tweaked role_path and action_plugin in ansible.cfg https://github.com/openstack/tripleo-quickstart/blob/master/ansible.cfg#L16 It is working fine. Later on, we started checking other roles and action plugins available on openstack ecosystem in order to make user experience easier, we found that ansible-role-tripleo-modify-image dumps it's files in share/ansible/roles/tripleo-modify-image/ directory [ https://github.com/openstack/ansible-role-tripleo-modify-image/blob/master/…] and kolla-ansible is dumping all stuff at share/kolla-ansible/ansible [https://github.com/openstack/kolla-ansible/blob/master/setup.cfg#L27] and ceph-ansible can copied the config_template action_plugin to their own repo https://github.com/ceph/ceph-ansible/blob/master/plugins/actions/config_tem… so that end-user can just clone the role & action_plugin and just do python setup.py install In all above case, these are using python packaging format. Currently ansible looks for roles and plugins by default at following different places from https://github.com/ansible/ansible/blob/devel/lib/ansible/config/base.yml action_plugins: ~/.ansible/plugins/action:/usr/share/ansible/plugins/action roles_path: default: ~/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles By seeing that, we thought use to introduce requirements.yaml file to keep the ansible role requirements and then use ansible-galaxy install -r requirments.yaml it will install both the dependencies to ~/.ansible/roles directory but it will not load config_template action plugins and for enduser, we explicitly export the ANSIBLE_ACTION_PLUGINS to ~/.ansible/roles/config_template which is too much for an end user. Patch example: https://review.openstack.org/#/q/topic:ostempest_packaging+(status:open+OR+… For end user, we are looking for solution something like that or may be something better: git clone <os_tempest> then ansible-galaxy install or python setup.py install and we are done to run the playbook. But as you see above, different projects uses different ways of packaging the role and action plugins. Do we have defined standard around packaging ansible roles and ansible modules in OpenStack so that it will be easily consumable so that ansible can easily find the role and action_plugins? Like in terms of where to keep ansible role & action plugin while using setup.cfg or any other format. Thanks for reading, Links: [1.] https://github.com/openstack/openstack-ansible-os_tempest/ [2.] https://github.com/openstack/ansible-role-python_venv_build [3.] https://github.com/openstack/ansible-config_template Thanks, Chandan Kumar

2 1

murano 7.0.0.0rc1 (stein)
by no-reply＠openstack.org 19 Mar '19

19 Mar '19

Hello everyone, A new release candidate for murano for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/murano/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/murano/log/?h=stable/stein Release notes for murano can be found at: https://docs.openstack.org/releasenotes/murano/

1 0

murano-dashboard 7.0.0.0rc1 (stein)
by no-reply＠openstack.org 19 Mar '19

19 Mar '19

Hello everyone, A new release candidate for murano-dashboard for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/murano-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/murano-dashboard/log/?h=stable/ste… Release notes for murano-dashboard can be found at: https://docs.openstack.org/releasenotes/murano-dashboard/

1 0

[all][tc][goals] train cycle goals discussion
by Mohammed Naser 19 Mar '19

19 Mar '19

Hi everyone, I'd like us to schedule an ad-hoc meeting to discuss the cycle goals in order to give enough time for developers to plan out their PTG. We would love to have community members as well as potential goal champions available to discuss, we'll be discussing these two reviews: https://review.openstack.org/#/c/639010/ https://review.openstack.org/#/c/639376/ We've setup a Framedate poll to pick one of the upcoming office hours to discuss this, please include your name so we can pick a time that works best. https://framadate.org/1Q5i7gqQsZDH9dBQ Thank you. Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

2 3

[scientific-sig] IRC meeting today 2100 UTC (in 2.5 hours): Nomad (Hashicorp) GPU cluster
by Blair Bethwaite 19 Mar '19

19 Mar '19

Hi all, Today we've got Joe Topjian from Cybera coming along to share some details on a PoC he's been working on recently, using Hashicorp's Nomad as a container based workload manager to support datascience and ML workloads (IIUC). Cheers, b1airo

1 0

DNS for instances
by Grant Morley 19 Mar '19

19 Mar '19

Hi all, I am having a bit of an issue with DNS for instances. We are wanting to update our DNS servers that all instances use. I have tested this by using google's nameservers for now and set both of our subnets to use "8.8.8.8 & 8.8.4.4", I have also changed the "dhcp_agent.ini" on our Neutron nodes to have: dnsmasq_dns_servers = 8.8.8.8, 8.8.4.4 I have restarted the dhcp agents on both nodes, however whenever a new instance is launched, it is still using the old DNS server setup. Is there anything else I need to do or anything I have missed to make sure instances use the updated DNS servers? Many thanks, Grant -- Grant Morley Cloud Lead Absolute DevOps Ltd Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP www.absolutedevops.io <http://www.absolutedevops.io/> grant(a)absolutedevops.io <mailto:grant@absolutedevops.io> 0845 874 0580

1 1

[ops] ops meetups team meeting 2019-3-19
by Chris Morgan 19 Mar '19

19 Mar '19

meeting minutes from today's meeting openstack> Meeting ended Tue Mar 19 14:58:06 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 10:58 AM Minutes: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… 10:58 AM Minutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… 10:58 AM O<•openstack> Log: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_tea… meetings are held weekly at 10am EST on #openstack-operators Chris -- Chris Morgan <mihalis68(a)gmail.com>

1 0

[release] Release countdown for week R-3, March 18-22
by Sean McGinnis 19 Mar '19

19 Mar '19

Another busy week. We are getting to the end of the Stein release cycle, so please read through for important actions needed as we prepare for wrapping things up. Development Focus ----------------- The Release Candidate (RC) deadline is this Thursday, the 21st. Work should be focused on any release-critical bugs and wrapping up and finalizing feature work. General Information ------------------- All cycle-with-rc and cycle-with-intermediary projects should cut their stable/stein branch by the end of the week. This branch will track the Stein release. Once stable/stein has been created, master will will be ready to switch to Train development. While master will no longer be frozen, please prioritize any work necessary for completing Stein plans. Please also keep in mind there will be stein patches competing with any new Train work to make it through the gate. Changes can be merged into stable/stein as needed if deemed necessary for an RC2. Once Stein is released, stable/stein will also be ready for any stable point releases. Whether fixing something for another RC, or in preparation of a future stable release, fixes must be merged to master first, then backported to stable/stein. 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/stein 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 Train) to this stable branch for any additional RCs before the final release. There have been a few teams that have added cycle-highlights so far. Please get those added to help in communicating Stein updates. We would like to have all of those by the RC1 deadline to give marketing time to compile them and come up with that messaging. http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003597.ht… Finally, any cycle-with-intermediary projects that have not done a release lately - we will need to use the last release point as the branching point for stable/stein unless you specify an updated one. Please make sure the stable branch will have everything you would like included to avoid needing to backport already merged changes. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 21 Final RC deadline: April 1 Final Stein release: April 10 -- Sean McGinnis (smcginnis)

2 2