- openstack-discuss - lists.openstack.org

sahara-plugin-spark 1.0.0.0rc1 (stein)
by no-reply＠openstack.org 20 Mar '19

20 Mar '19

Hello everyone, A new release candidate for sahara-plugin-spark for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-plugin-spark/ 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/sahara-plugin-spark/log/?h=stable/… Release notes for sahara-plugin-spark can be found at: https://docs.openstack.org/releasenotes/sahara-plugin-spark/

1 0

sahara-plugin-vanilla 1.0.0.0rc1 (stein)
by no-reply＠openstack.org 20 Mar '19

20 Mar '19

Hello everyone, A new release candidate for sahara-plugin-vanilla for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-plugin-vanilla/ 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/sahara-plugin-vanilla/log/?h=stabl… Release notes for sahara-plugin-vanilla can be found at: https://docs.openstack.org/releasenotes/sahara-plugin-vanilla/

1 0

solum 6.0.0.0rc1 (stein)
by no-reply＠openstack.org 20 Mar '19

20 Mar '19

Hello everyone, A new release candidate for solum for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/solum/ 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/solum/log/?h=stable/stein Release notes for solum can be found at: https://docs.openstack.org/releasenotes/solum/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/solum and tag it *stein-rc-potential* to bring it to the solum release crew's attention.

1 0

sahara-plugin-mapr 1.0.0.0rc1 (stein)
by no-reply＠openstack.org 20 Mar '19

20 Mar '19

Hello everyone, A new release candidate for sahara-plugin-mapr for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-plugin-mapr/ 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/sahara-plugin-mapr/log/?h=stable/s… Release notes for sahara-plugin-mapr can be found at: https://docs.openstack.org/releasenotes/sahara-plugin-mapr/

1 0

neutron-lbaas-dashboard 6.0.0.0rc1 (stein)
by no-reply＠openstack.org 20 Mar '19

20 Mar '19

Hello everyone, A new release candidate for neutron-lbaas-dashboard for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron-lbaas-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/neutron-lbaas-dashboard/log/?h=sta… Release notes for neutron-lbaas-dashboard can be found at: https://docs.openstack.org/releasenotes/neutron-lbaas-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://storyboard.openstack.org/#!/project/907 and tag it *stein-rc-potential* to bring it to the neutron-lbaas-dashboard release crew's attention.

1 0

sahara-image-elements 10.0.0.0rc1 (stein)
by no-reply＠openstack.org 20 Mar '19

20 Mar '19

Hello everyone, A new release candidate for sahara-image-elements for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-image-elements/ 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/sahara-image-elements/log/?h=stabl… Release notes for sahara-image-elements can be found at: https://docs.openstack.org/releasenotes/sahara-image-elements/

1 0

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

20 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 20 Mar '19

20 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