| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
| |
This allows downstream troves that only need to access publically
available content to be able to operate without configuring
ssh keys on the upstream trove.
|
| |
|
