baserock/baserock/definitions.git - gitlab.com: baserock/definitions.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fix Mason deployments for non-openstack-testing Mason	Pedro Alvarez	2014-11-19	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In mason.configure: It's not needed to create a separate os.conf file at this point. In this file we were puting OpenStack credentials used to create an os.conf file with Ansible. This file was only created when TEST_INFRASTRUCTURE_TYPE was 'openstack', and Ansible was expecting it always. This patch moves the OpenStack credentials to mason.conf, so Ansible only have to read the variables from one file. In mason.sh: The script was always loading /etc/os.conf. This file is only created when TEST_INFRASTRUCTURE_TYPE is 'openstack'. This patch checks that the file exists before loading it. In mason.conf template for Ansible. OPENSTACK_NETWORK_ID is only present when TEST_INFRASTRUCTURE_TYPE is 'openstack'. This patch adds a conditon in the template to skip this value if it doesn't exist.
*	Check Mason variables after installing Mason files	Pedro Alvarez	2014-11-19	1	-30/+28
\| \| \| \| \|	This way, if the Mason system that is being deployed is generic, it will contain the files needed to setup and run Mason.
*	Allow mason.configure to be enabled without requiring configuration	Sam Thursfield	2014-10-27	1	-19/+29
\| \| \| \| \| \|	If none of the MASON_ options are set then mason.configure will now do nothing, instead of raising an error. This is needed because mason.configure is enabled by default in the build-system.
*	Stop mason.service starting before mason-setup.service has completed	Adam Coldrick	2014-10-27	1	-1/+0
\|
*	Use Ansible to generate config for OpenStack	Adam Coldrick	2014-10-27	1	-0/+16
\|
*	Make mason.conf contain everything it needs to	Adam Coldrick	2014-10-27	1	-0/+4
\| \| \| \| \| \| \|	This adds TEST_INFRASTRUCTURE_TYPE and OPENSTACK_NETWORK_ID to mason.conf, as well as ending the confusion of using both MASON_TEST_HOST and TEST_VM_HOST_SSH_URL to mean the same thing in different places.
*	Fix another issue with deployment of configured Masons.	Sam Thursfield	2014-09-30	1	-1/+1
\| \| \| \| \|	Reviewed-By: Daniel Silverstone <daniel.silverstone@codethink.co.uk> Reviewed-By: Paul Sherwood <paul.sherwood@codethink.co.uk>
*	Fix deploying a non-generic Mason	Sam Thursfield	2014-09-30	1	-3/+2
\| \| \| \| \| \| \| \|	Fixed DISTBUILD_GENERIC check in distbuild.configure, and TROVE_ADMIN_NAME check in mason.configure Reviewed-By: Pedro Alvarez <pedro.alvarez@codethink.co.uk> Reviewed-By: Paul Sherwood <paul.sherwood@codethink.co.uk>
*	Update mason.configure to use Ansible	Pedro Alvarez	2014-09-17	1	-25/+32
\|
*	Move Mason out from /root	Pedro Alvarez	2014-09-17	1	-3/+6
\| \| \| \| \| \|	- Move the configuration file to /etc/mason.conf - Move the scripts to /usr/lib/mason/ - Mason will store the report in /var/mason/report.html
*	Allow the deployment of generic Mason instances	Pedro Alvarez	2014-09-17	1	-20/+36
\|
*	Deploy Masons to use source on upstream troves	Richard Maw	2014-08-28	1	-5/+5
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The per-mason trove only needs to worry about being an artifact cache, so we can prevent it populating itself from the upstream trove by making it use the SSH protocol for fetching sources, and not registering its ssh key with the upstream trove. The MASON_UPSTREAM_TROVE_ADDRESS option has been removed, as this is now the TROVE_HOST. The distbuild network is now configured to use the upstream trove for sources, and the local trove for artifacts, with the ARTIFACT_CACHE_SERVER option. mason.configure now uses ARTIFACT_CACHE_SERVER to tell deploy commands which server to fetch artifacts from.
*	Ensure .log files are served with mime-type of text/plain.	Michael Drake	2014-08-07	1	-0/+9
\| \| \| \|	Stops the server offering logs for download, instead of displaying them.
*	Fix web server root directory creation.	Michael Drake	2014-08-07	1	-1/+1
\|
*	Add Mason scripts on top of distbuild system	Michael Drake	2014-08-06	1	-0/+92
	The distbuild system can be configured to act as a CI controller. Providing appropriate config makes it copy all the scripts and systemd units out of the mason directory onto the target, such that it will start building and testing the configured cluster morphology on boot.