summaryrefslogtreecommitdiff
path: root/trove.configure
Commit message (Collapse)AuthorAgeFilesLines
* trove.configure: Make UPSTREAM_TROVE optionalPedro Alvarez2014-09-171-7/+1
|
* Allow changing upstream trove fetch protocol at configure timeMichael Drake2014-08-051-1/+3
|
* New trove.configurePedro Alvarez2014-07-141-202/+84
|
* Update commentRichard Ipsum2014-06-171-2/+0
| | | | We don't use UPSTREAM_TROVE_USER or UPSTREAM_TROVE_EMAIL
* Allow TROVE_HOSTNAME to be set separately from TROVE_IDLars Wirzenius2014-05-291-1/+7
|
* Stop setting system hostname to TROVE_IDLars Wirzenius2014-05-291-3/+0
| | | | | | | | | | We have hostname.configure already for setting the hostname, and nothing in Trove (gitano, LC, etc) should care about the hostname. They might care about the external name (i.e., TROVE_HOSTNAME), but that's entirely orthogonal to the system hostname. And some systems shouldn't have their system hostname set to TROVE_ID. For example, git.baserock.org's TROVE_ID is baserock, but the system hostname shouldn't be that (it's currently firehose1).
* Create the minion configuration in trove.configurePedro Alvarez2014-05-211-0/+11
| | | | | Minions load its configuration from /etc/lorry-controller/minion.conf and the file wasn't been generated at deploy time.
* Make Trove deployment handle new Lorry ControllerLars Wirzenius2014-04-231-0/+35
| | | | | | | | | | | | | | Add install-files to the list of configuration extensions, on general principles. It costs nothing to have it, and is a nice way to install, say, ssh keys. In trove.configure, support the optional LORRY_CONTROLLER_MINIONS configuration key to decide how many Lorry Controller MINION instances may run at the same time. It has a default in case it is not set. Create /etc/lorry-controller/webapp.conf. This needs to have some information from the deployment, so it can't be just installed by the Lorry Controller chunk.
* Make trove.configure perform required substitutionsbaserock/adamcoldrick/binary-delivery-v4-rebaseAdam Coldrick2014-03-271-1/+11
| | | | | | Since we added releases-repo-migration.sh and a systemd unit to call it, and both of these need to know the Trove ID, add them to the command that performs substitutions in trove.configure.
* Revert "trove: Allow TROVE_HOSTNAME different to TROVE_ID"Sam Thursfield2014-03-171-11/+4
| | | | | | | This reverts commit 3e73cebdb2ef8df99f416696d040e797b856cd24. This patch was accidentally pushed without review as part of the previous branch.
* trove: Allow TROVE_HOSTNAME different to TROVE_IDSam Thursfield2014-03-141-4/+11
| | | | | This is necessary for git.baserock.org, whose TROVE_PREFIX and TROVE_ID is 'baserock' but whose hostname certainly isn't.
* trove: Do subsitutions in /etc at deploy-time, not at first bootSam Thursfield2014-03-111-10/+32
| | | | | | | | | This makes it easier to merge changes between /etc when doing upgrades. Lorry and Mason config goes into local-config.git, not in /etc, so this still needs to be done at first boot when we can run Gitano commands on the target. For this reason the /etc/trove-setup.sed file is still stored in the resulting system.
* trove: Allow multiple configuration placeholders on one lineSam Thursfield2014-03-061-9/+9
| | | | | | | | The generated /etc/trove-setup.sed script, used to set up site configuration for a deployed Trove on first-boot by trove-early-setup, did not specify the 'g' (global) flag which meant that lines with more than one occurance of a placeholder such as ##TROVE_HOST## were not set correctly.
* trove: Make dependency graph of trove-early-setup.service clearerSam Thursfield2014-03-031-0/+6
| | | | | | It's hard to spot the 'reboot' command at the bottom of the list of commands and it's a non-standard thing to do. This change should make it more obvious what goes on during Trove first boot.
* trove: Don't keep trove-early-setup systemd unit in /varSam Thursfield2014-03-031-7/+16
| | | | | | If /var is a subvolume then we cannot access it until local-fs.target has completed, and certainly we can't expect it to be around when systemd is deciding what units to execute.
* trove: Avoid running trove-early-setup on upgradesSam Thursfield2014-03-031-3/+11
| | | | The trove-early-setup configuration tool is for initial deployment only.
* Add troveRichard Ipsum2013-12-171-0/+168