29 Commits

Author SHA1 Message Date
Mohammed Naser
7a96aa311e Prepare for official Queens release
Prepare the metadata for the official Queens release.

Change-Id: Ie82bb7b21ea9dffff6e21696623d78306fa9d18a
2018-02-19 12:44:29 -05:00
Emilien Macchi
1bf85b5748 Prepare for Queens Milestone 3
Prepare the metadata configuration for the third Queens milestone.

Change-Id: I760f0cedf5e949f15b38cda766d0d5cff936f45d
2018-01-16 15:56:49 -08:00
Alex Schultz
326f473a20 Prepare for Queens Milestone 2
Prepare the metadata configuration for the second Queens milestone.

Change-Id: I04359bef39be5e98a1e662b9fac93b4e01827c88
2017-11-28 16:19:49 -07:00
Alex Schultz
e5528e7ca4 Prepare for Queens Milestone 1
Prepare the metadata configuration for the first Queens milestone.

Depends-On: Id68ee1b443a4172d0c1d6d58a04908c52a566623
Change-Id: I16cb1a10c88ea033b0b27cd9ff5363676daf918e
2017-10-18 01:55:44 +00:00
Alex Schultz
7e87071cad Update versions for Queens cycle
Since we've cut the release for pike, we need to open master up
with Queens version information.

Change-Id: I6e8f178b2ad11ebf09120c2df2abd9735900dc7f
2017-08-24 13:08:39 -06:00
Alex Schultz
915c8f7ac5 Prepare for official Pike release
Prepare the metadata and release note configuration for the
official Pike release.

Change-Id: I1a9eb84422ada438e00348de37b5cfebc034d970
2017-08-21 16:01:14 -06:00
Alex Schultz
88765f143c Bump modules to next minor with -dev
After releasing Pike M3, we need to bump the metadata version
information for the next release with a -dev.

Change-Id: I2252bf5f5f41d70d9078a39196000219a01919f1
2017-08-04 13:39:11 -06:00
Alex Schultz
fe32e6c9ce Drop -dev version for Pike M3
Prepare version metadata for Pike M3

Change-Id: I5991f9c0f5e36d94d83c44366a3ca6e4b1f3f823
2017-07-25 08:15:42 -06:00
Alex Schultz
be53101921 Bump version for Pike M3 Dev
Pike M2 has been released. Prepare version numbers for M3.

Change-Id: Ia21b07b01d445cfd7b5a78bc7bc2208426853f85
2017-06-08 15:34:30 -06:00
Alex Schultz
9697f99915 Drop -dev in preparation for Pike M2
We're coming up on the Pike M2 release and we need to prepare the
metadata.json and reno configuration for the release.

Change-Id: Ib2c65d09100ab1ead52edf7c0f93126fb6c01c2a
2017-06-01 08:55:37 -06:00
Alex Schultz
e5bc71f020 Bump modules to next minor with -dev
After releasing Pike M1, we need to bump the metadata version
information for the next release with a -dev.

Change-Id: I7ed9782f9598ed1b427102aaf7ea2062168a04de
2017-04-21 17:24:47 -06:00
Alex Schultz
3aff1adcb7 Drop -dev for release prep
Removing the -dev from the version to prepare for Pike M1

Change-Id: I872fadcf46add2b068fd6e106345db9f63e1c998
2017-04-05 10:46:39 -06:00
Alex Schultz
f739d83348 Prepare Pike metadata
Bump metadata.json and reno configs for Pike

Change-Id: I1401e91d049e2484c57fb1fc259b1aaa489ca1c8
2017-03-07 15:35:22 -07:00
Thomas Herve
4a5a1fd46d Allow deployment of Zaqar WSGI with Apache
Change-Id: If91894176abdfae2820c2e13723c87f5ef8fb153
2017-02-22 13:13:12 -05:00
Alex Schultz
371d810300 Prepare ocata-rc1 release
Bump metadata.json and reno configs for ocata-rc1 release

Change-Id: Ifd7c185c0126e4320599075e9855827e62c5f712
2017-02-03 16:24:44 -07:00
Alex Schultz
de88098ee5 Prepare 10.2.1 release
We missed the metadata.json updates for the ocata-3 release
so we need to include them in a new release.

Change-Id: I5bb8a1fe8d85b023ec35a75e2f413e4209076e93
2017-01-26 13:24:24 -07:00
Alex Schultz
be984e4577 Prepare 10.1.0 release
The second release for Ocata.

Change-Id: Ib5222f2c1b8c051dd1a743c3260620058b2a1db0
2016-12-09 09:35:47 -07:00
Alex Schultz
1a22c9e3ed Prepare 10.0.0 release
First release of Ocata.

Change-Id: I3e9f810fce65ede07a52d01a7cf4f3f684c064c3
2016-11-14 16:41:13 -07:00
ZhongShengping
de627fd745 Add requirements in metadata.json file
Change-Id: I2e297e7479319052f47a2322e77cbc964f03601f
2016-11-03 10:05:29 +08:00
Alex Schultz
c34d1b6642 Puppet OpenStack Newton RC2
9.4.0 will be our RC2.

Change-Id: I9d422faf4ef68b22e2be1b51ce184c92509c4065
2016-09-26 07:33:20 -06:00
Emilien Macchi
9539153497 Prepare 9.3.0 (newton rc1)
Preparing Newton rc1 release.

Change-Id: Ia234053e1963a1e985c5aebfc425261f019042e4
2016-09-16 11:42:33 -04:00
Emilien Macchi
1b127300d7 Prepare 9.2.0 (newton b3)
Preparing Newton b3 release.

Change-Id: Ia9877b185ef582a3b6f1841589d5f833f46641e6
2016-08-26 09:57:14 -04:00
Emilien Macchi
8ea7a5c931 Prepare 9.1.0 (newton-2)
Prepare the second milestone of Newton cycle.

Change-Id: I7a6fb470fbb21e5f9846bbdc73f093d6610f9da5
2016-07-07 09:10:32 -04:00
Iury Gregory Melo Ferreira
cca253d8ed Add xenial to metadata
Change-Id: I2cd58c47920631836c416835b2bcd0313d0a9b83
2016-06-29 23:13:00 -03:00
Emilien Macchi
79a80f9583 Prepare 9.0.0 release
First release of Newton.

Change-Id: I562f8380a78412848bebbe7be987196933308ccb
2016-06-03 10:08:48 -04:00
Emilien Macchi
b2b1be1de8 Release 8.0.0
* Update CHANGELOG with release notes URL.
* Update README with new release number & name.
* Update metadata.json with new tag & dependencies.
* Add release note prelude for Mitaka.
* Update Reno release note to drop prelude.
* Improve release note landing page.

Change-Id: I55cb70b74940eeed95e911b4df24f8320f57fe6d
2016-03-23 16:08:03 -04:00
Dan Prince
fa9218c4cd Reflect provider change in puppet-openstacklib
With the creation of the new openstack_config provider, some
essing
that was done in zaqar_config has been centralized in
openstack_config.

Impacted methods are :

  * section
  * setting
  * separator

Also, this commit adds the fact that, when passing a specific string
(ensure_absent_val) the provider will behave as if ensure => absent
was
specified. '<SERVICE DEFAULT>' is the default value for
ensure_absent_val.

The use case is the following :

zaqar_config { 'DEFAULT/foo' : value => 'bar' } # will work as
l

zaqar_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>' } #
 mean absent

That means that all the current :

if $myvar {
  zaqar_config { 'DEFAULT/foo' : value => $myvar }
} else {
  zaqar_config { 'DEFAULT/foo' : ensure => absent }
}

can be removed in favor of :

zaqar_config { 'DEFAULT/foo' : value => $myvar }

If for any reason '<SERVICE DEFAULT>' turns out to be a valid value
for a specific parameter. One could by pass that doing the following

zaqar_config { 'DEFAULT/foo' : value => '<SERVICE DEFAULT>',
 ensure_absent_val => 'foo' }

Change-Id: Iaaf2e5755080ef32d7d585465aaea6fd408d0ece
2016-02-11 20:10:48 -05:00
Gael Chamoulaud
8132ef1c11 metadata: Switch to OpenStack namespace and bump to Kilo
This patch fixes the puppet forge namespace, and bump min dependency to Kilo
https://wiki.openstack.org/wiki/Puppet/releases.

Change-Id: I2640446d5dfd6bea6e43a52e016a813ef78a105f
Signed-off-by: Gael Chamoulaud <gchamoul@redhat.com>
2015-11-12 14:29:05 +01:00
Richard Raseley
33c0956a92 puppet-zaqar: Initial commit
This is the initial commit for puppet-zaqar.
It has been automatically generated using cookiecutter[1] and msync[2]

[1] https://github.com/openstack/puppet-openstack-cookiecutter
[2] https://github.com/openstack/puppet-modulesync-configs

Change-Id: Iaca8f89dd22320ec0e08bfb8ec9b5912ad68c9fb
Co-Authored-By: yguenane@redhat.com
2015-08-25 09:59:38 -07:00