2a5baa5979
We have yet Nova for SSH keys management, when deploying a standalone cloud. Allow Octavia deployments for such a case as well. Jinja2 rendering of the octavia service template provides that functionality by relying on a new role tag 'standalone'. Change-Id: I69f3623646ec5b65109e0a4f0c16139018da9282 Closes-bug: #1806113 Co-Authored-By: Harald Jensas <hjensas@redhat.com> Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
9 lines
385 B
YAML
9 lines
385 B
YAML
---
|
|
other:
|
|
- |
|
|
Octavia may be deployed for a standalone cloud, which has yet Nova services
|
|
available for Amphorae SSH keys management. For that case, the parameter
|
|
``OctaviaAmphoraSshKeyFile`` must be defined by a user.
|
|
Otherwise, it takes an empty value by usual for overcloud deployments
|
|
meanings and Nova will be used to create a key-pair for Octavia instead.
|