06f056f606
Keypair can now be added during Cluster create command. This allows Clusters to be created from the same ClusterTemplate but have different keypair values when created. If not specified on create then the value from the ClusterTemplate will be used. Adds keypair_id to Cluster object and uses of keypair_id will use the value from Cluster instead of ClusterTemplate. Added release note for new features in magnum and magnum CLI. Change-Id: I177a5aa06f881156944a9f74c9ccc3cd2abac492 Implements: blueprint keypair-override-on-create
18 lines
639 B
YAML
18 lines
639 B
YAML
---
|
|
prelude: >
|
|
Magnum's keypair-override-on-create blueprint [1]
|
|
allows for optional keypair value in ClusterTemplates
|
|
and the ability to specify a keypair value during
|
|
cluster creation.
|
|
features:
|
|
- Added parameter in cluster-create to specify the
|
|
keypair. If keypair is not provided, the default
|
|
value from the matching ClusterTemplate will be used.
|
|
- Keypair is now optional for ClusterTemplate, in order
|
|
to allow Clusters to use keypairs separate from their
|
|
parent ClusterTemplate.
|
|
deprecations:
|
|
- --keypair-id parameter in magnum CLI
|
|
cluster-template-create has been renamed to
|
|
--keypair.
|