Releases

Releases Summary

Module Version

OpenStack Version Codename

Community Supported

2.y.z

Grizzly

no - EOL (2014-03-29)

3.y.z

Havana

no - EOL (2014-09-30)

4.y.z

Icehouse

no - EOL (2015-07-02)

5.z.y

Juno

no - EOL (2015-12-07)

6.z.y

Kilo

no - EOL (2016-05-02)

7.z.y

Liberty

no - EOL (2016-11-17)

8.z.y

Mitaka

no - EOL (2017-04-10)

9.z.y

Newton

no - EOL (2017-10-11)

10.z.y

Ocata

yes - EOL (2017-02-26)

11.z.y

Pike

yes - EOL (2017-08-30)

12.z.y

Queens

yes - EOL (2018-02-28)

13.z.y

Rocky

yes - EOL (2018-08-30)

14.z.y

Stein

yes - EOL (2019-04-10)

15.z.y

Train

yes

16.z.y

Ussuri

yes

17.z.y

Victoria

yes (current master)

Puppetlabs releases

How to release Puppet modules

Note

puppet-ceph should be done separately because the branches track ceph releases and not openstack releases.

Note

puppet-pacemaker should also be done seperately because it is an independent release

Once the release is done, you can see the tarballs here: https://tarballs.openstack.org

If a new branch has been created, some tasks need to be done:

  • Branch openstack/puppet-openstack-integration and openstack/puppet-openstack_spec_helper http://docs.openstack.org/infra/manual/drivers.html#create-stable-branch

  • Update openstack/puppet-openstack_spec_helper and update CI scripts to checkout stable, also rake_tasks.rb and beaker_spec_helper.rb to checkout the new branch, .gitreview file and release notes to have a page for the stable release, looking for notes in the stable branch. Note: the patch has to be done in stable/pike. Example: https://review.opendev.org/#/c/497403/

  • For all modules and openstack/puppet-openstack-integration, Puppetfile + Gemfile to use the new branch, also update .gitreview. Note: example patches patch has to be done in stable/pike. Example: https://review.opendev.org/#/q/topic:switch-to-pike

  • Update this documentation