8 Commits

Author SHA1 Message Date
Zane Bitter
5e0a7eee8f Validate that endpoint_map.yaml is up to date in the gate
Change-Id: I72aa48c72c825151739cb478c58e9a6c841c9130
2017-02-01 16:06:20 -05:00
Emilien Macchi
5efee26c97 Add ReNo support
Add ReNo support to manage release notes.
http://docs.openstack.org/developer/reno/

Change-Id: Ie5154d909e616e4e7e813052f9c121d6ac5b0875
2017-01-13 14:35:27 -05:00
Dan Prince
b56e666dd5 Make pep8 task run template generation
This patch updates the pep8 task (which is executed in CI) so
that it generates templates locally. This will give us extra
CI coverage to ensure our generated templates produce valid
YAML.

Change-Id: I2287802d44c0ebe404d3fce30f04efcc3c6ab27f
2016-11-30 21:14:52 -05:00
Dan Prince
4b5b24462b Add local template generation tox task
This patch adds a local version of our template processing
routine so that developers can more quickly view the templates
that are actually getting generated. I've noticed multiple developers
now do a full deployment with 'overcloud deploy' only to download
the swift container with the generated templates. This simple task
avoids that step by allowing developers to generate it locally.

It also aims to preserve the ability to use t-h-t templates directly
with Heat (instead of going through Mistral) should users wish to do that.
The new undercloud heat installer requires the ability to generate
templates without requiring Mistral and Swift to do so.

Ideally the Mistral API workflow would use this same code
so perhaps in the future we might modify that routine to:

 -download swift tarball containing the templates
 -run this local routine that lives in t-h-t
 -re-upload the tarball of templates to the swift container

Change-Id: Ie664c9c5f455b7320a58a26f35bc403355408d9b
2016-11-30 16:02:44 -05:00
Ben Nemec
63df8f1a01 Rename tox env to pep8
It turns out the linters rename was a bit premature[1].  Use the
current standard pep8 name so we don't need custom jobs in the
gate to run this test on proposed changes.

Change-Id: I5226d4c5e3d4095d76cba24fcf27f87c59730587
1: http://lists.openstack.org/pipermail/openstack-dev/2016-February/086268.html
2016-02-11 12:29:36 -06:00
Ben Nemec
e97fdbe639 Rename validate tox env to linters
This is the new blessed naming scheme for lint-type jobs such as
pep8 or the yaml validation job we have in this project.  Doing
this rename will allow us to use standard infra job templates
to run validation on proposed changes.

Change-Id: I0a4c4372429a08e0babb4d323f2b027f1d95f3d7
2016-01-20 15:33:23 -06:00
Ben Nemec
607804f242 Add YAML sanity check
Adds a "validate" tox env for basic sanity checking of templates.
Currently it just validates that all of the .yaml files are in fact
valid YAML.  In the future we might want to add more, but this
seemed like a reasonable start.

Change-Id: I8091bbad0003b150e23dae5de4f465053c982229
2015-09-15 15:31:43 -05:00
Chris Jones
80da8e3968 Add release configuration.
We can now release through openstack.org infrastructure.

Change-Id: I6dff6ae4a97db15bdc4ce419e46e9a125bec277c
2013-10-22 17:49:35 +01:00