summaryrefslogtreecommitdiffstats
path: root/tox.ini
AgeCommit message (Collapse)AuthorFilesLines
2017-07-07Add in roles data validationAlex Schultz1-0/+9
With the merging of Iad3e9b215c6f21ba761c8360bb7ed531e34520e6 the roles_data.yaml should be generated with tripleoclient rather than edited. This change adds in a pep8 task to verify that the appropriate role files in roles/ have been modified to match how our default roles_data.yaml is constructed. Additionally this change adds a new tox target called 'genrolesdata' that will all you to automatically generate roles_data.yaml and roles_data_undercloud.yaml Change-Id: I5eb15443a131a122d1a4abf6fc15a3ac3e15941b Related-Blueprint: example-custom-role-environments
2017-06-12Support config dir for env generator input filesBen Nemec1-1/+1
We're not going to want to list every single sample environment in a single file, so let's also take a directory and just read every yaml file in it. This commit adds support for that as well as some initial environments to demonstrate its use. Change-Id: If2c608f2a61fc5e16784ab594d23f1fa335e1d3c
2017-06-12Sample environment generatorBen Nemec1-0/+10
This is a tool to automate the generation of our sample environment files. It takes a yaml file as input, and based on the environments defined in that file generates a number of sample environment files from the parameters in the Heat templates. A tox genconfig target is added that mirrors how the other OpenStack services generate their sample config files. A description of the available options for the input file is provided in a README file in the sample-env-generator directory. In this commit only a single sample config is provided as a basic example of how the tool works, but subsequent commits will add more generated sample configs. Change-Id: I855f33a61bba5337d844555a7c41b633b3327f7a bp: environment-generator
2017-05-17Use upper-constraints for toxAlex Schultz1-0/+1
Use the openstack upper-constraints when running tox. Change-Id: I9eef36eec749beec0effdb2309fe2ceb9bc557f8 Related-Bug: #1691511
2017-02-01Validate that endpoint_map.yaml is up to date in the gateZane Bitter1-0/+1
Change-Id: I72aa48c72c825151739cb478c58e9a6c841c9130
2017-01-13Add ReNo supportEmilien Macchi1-0/+3
Add ReNo support to manage release notes. http://docs.openstack.org/developer/reno/ Change-Id: Ie5154d909e616e4e7e813052f9c121d6ac5b0875
2016-11-30Make pep8 task run template generationDan Prince1-2/+4
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-30Add local template generation tox taskDan Prince1-0/+3
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-02-11Rename tox env to pep8Ben Nemec1-1/+1
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-01-20Rename validate tox env to lintersBen Nemec1-2/+2
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
2015-09-15Add YAML sanity checkBen Nemec1-0/+3
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
2013-10-22Add release configuration.Chris Jones1-0/+11
We can now release through openstack.org infrastructure. Change-Id: I6dff6ae4a97db15bdc4ce419e46e9a125bec277c