a3de34dbc7
Now Trove doesn't support to specify keypair when creating the db instance, the ssh key is injected into the guest agent image at the build time, which makes it very hard to manage. This patch adds a config option `nova_keypair` that is used as keypair name when creating db instance. The old way of the image building will be changed in the subsequent patches. Change-Id: I41d4e41fc4bc413cdd48b8d761429b0204481932 Story: #2005429 Task: #30462
14 lines
823 B
YAML
14 lines
823 B
YAML
features:
|
|
- Added a new config option ``nova_keypair`` to specify an existing Nova
|
|
keypair name for the database instance creation, the cloud administrator is
|
|
responsible for the keypair management and configuration. It's recommended
|
|
to create Trove database instance in the admin project for security
|
|
reasons, so only the cloud administrator who has the private key can access
|
|
the database instance. With the keypair support, ssh keys are no longer
|
|
injected into Trove guest agent image at build time.
|
|
upgrade:
|
|
- Cloud administrator needs to create a Nova keypair and specify the keypair
|
|
name for config option ``nova_keypair``, the private key is used to ssh
|
|
into new database instances created. The previous private key is also
|
|
needed to ssh into the existing database instances.
|