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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Install opengrok.baserock.org	Pedro Alvarez	2016-04-18	1	-0/+1
\| \| \| \| \| \| \| \|	Using baserock-export scripts, OpenGrok sytem will export all the sources needed for a Baserock minimal system and will use them. Change-Id: Ia1e5196b15d6bb8af005f0ea8cf317182db51134
*	baserock_database: Update on top of Fedora 23, redeploy	Sam Thursfield	2016-02-19	1	-1/+1
\| \| \| \|	Change-Id: I9a25d9aad540c291aaea45f00e38065981ff3f50
*	baserock_mail: Update on top of Fedora 23, redeploy	Sam Thursfield	2016-02-19	1	-1/+1
\| \| \| \| \| \| \| \|	The instance-config.yml script was failing to create a valid EXIM config against the default /etc/exim.conf in Fedora 23, this is fixed now. The regexp configuration approach is rather fragile. Change-Id: Id1b4e3a854cb579ee58c1c4f7674415c6e8c096a
*	baserock_openid_provider: Update on top of Fedora 23, and without Packer	Sam Thursfield	2016-02-19	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This means we no longer use Packer for anything, which is good. The switch from Django 1.7 to Django 1.9 caused some problems in the openid_provider module. Upstream for that module is here: https://bitbucket.org/romke/django_openid_provider/ At the time of writing there was no fix upstream for these issues, it would be good to submit them. We have other unsubmitted changes against that upstream in our openid_provider code. One issue was use of import_module (which is now available from importlib, doesn't need to be imported from django.utils any more). Another is use of WSGIRequest.REQUEST, which is deprecated since Django 1.7 and removed in Django 1.9. We now need to use .POST or .GET to get that info. Change-Id: I60793aaf0d84d81b89ff59efbe08240d99b7973f
*	Remove some dead systems from the inventory	Sam Thursfield	2016-02-18	1	-2/+0
\| \| \| \|	Change-Id: I404d337a93a1f986a4613f450dcbafc67af7df9a
*	baserock_storyboard: Upgrade to latest and use Ansible for deployment	Pedro Alvarez	2016-01-22	1	-1/+1
\| \| \| \|	Change-Id: If4578c0d97aa2aee1a1a7e57bb7e2c42917ba077
*	Added new 'webserver' host	Gary Perkins	2015-12-03	1	-0/+1
\|
*	Add simple mail relay instance	Sam Thursfield	2015-03-26	1	-0/+1
\| \| \| \| \| \|	This is a Fedora Cloud 21 instance running exim4, for the moment. Change-Id: I6298a134bb474c65dd57a1bda87469dc3cd88441
*	Use unqualified hostnames for Ansible 'hosts'	Sam Thursfield	2015-03-17	1	-12/+11
\| \| \| \| \| \| \|	This makes the deployment scripts a bit more generic. Now, if I want to deploy 'gerrit.example.com', I don't need to fix all the places that say 'hosts: gerrit.baserock.org' to say 'hosts: gerrit.example.com' instead.
*	Make 'hosts' a symlink to baserock_hosts	Sam Thursfield	2015-03-17	1	-0/+40
	The idea is to make it easier for people to fork infrastructure.git and use it for their own infrastructure. They'll need to totally change 'hosts' to point to their own systems, and this would lead to merge conflicts every time they tried to pull in 'master' of infrastructure.git.