b29b7a6f3c
At the moment we do generate SSH keypairs for octavia with pre-defined options for backwards compatability. In the meanwhile it might not make much sense for new deployments, though there's no clear way to overrride these options.] With that we implement a bunch of new variables that allows to tune properties for the SSH key to be used. Change-Id: I5c4c20e7375b2471cc47ac628e007d6297bdeb7e (cherry picked from commit f976e5fd281f28fecb4e5f7d2be3e8c9769adceb)
17 lines
773 B
YAML
17 lines
773 B
YAML
---
|
|
|
|
features:
|
|
- |
|
|
Added variables to better control SSH keypair generation for Octavia:
|
|
|
|
* ``octavia_ssh_key_manage`` (True): Enables an Octavia role to generate
|
|
and manage SSH keypair to be used for Amphoras.
|
|
* ``octavia_resources_deploy_host`` (localhost): The host on which SSH key will be
|
|
created.
|
|
* ``octavia_ssh_key_dir`` (${HOME}/.ssh): Directory under which keypair
|
|
will be created on the ``octavia_resources_deploy_host``
|
|
* ``octavia_ssh_key_comment`` (Generated-by-Nova): Comment for the keypair.
|
|
* ``octavia_ssh_key_format`` (ssh): Format for the stored private key
|
|
* ``octavia_ssh_key_type`` (rsa): Type of the SSH keypair generated
|
|
* ``octavia_ssh_key_size`` (2048): Private key length.
|