| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Avoid scanning SSH host key of UPSTREAM_TROVE unless necessarysam/fix-init-behind-proxy | Sam Thursfield | 2014-11-17 | 1 | -7/+12 |
| | | | | | | | | | | | | | I've seen trove-setup.service fail in the case that the Trove is behind a proxy that blocks SSH traffic due to `ssh-keyscan` returning an error. We only need to scan the SSH host key of UPSTREAM_TROVE if we're going to be using SSH to acess it, so we can work around this issue. This pulls in the 'sshknownhosts' Ansible module from commit 80f31fa8a5d3751b4e3e19123164c3ea97f262dd of <https://github.com/bfmartin/ansible-sshknownhosts>. The module seems small enough that we don't need to mess with a submodules to include it. | ||||
| * | Allow the configuration of troves without UPSTREAM_TROVE | Pedro Alvarez | 2014-09-17 | 1 | -1/+4 |
| | | | | | | | | Now UPSTREAM_TROVE is not mandatory to configure a Trove, and if the value is not set, then the configuration of the lorry controller (lorry-controller.conf) won't include any configuration for an upstream Trove. | ||||
| * | Add Ansible scripts | Pedro Alvarez | 2014-07-14 | 1 | -0/+7 |
 |
index : baserock/baserock/trove-setup.git | |
| Trove configuration manager |
| summaryrefslogtreecommitdiff |