- different Flavors for control, compute and storage nodes
- for devtest use, they default to 'baremetal', so nothing
changes
- for Tuskar, there is a possibility to have them different for
every role
Change-Id: I8c1b80f55a91c7a7fd5e560ccdb8da82ec374084
Type: String
Default: "guest"
NoEcho: true
+ OvercloudBlockStorageFlavor:
+ Default: baremetal
+ Description: Flavor for block storage nodes to request when deploying.
+ Type: String
Resources:
BlockStorageAccessPolicy:
Type: OS::Heat::AccessPolicy
Properties:
image:
{Ref: BlockStorageImage}
- flavor: {Ref: Flavor}
+ flavor: {Ref: OvercloudBlockStorageFlavor}
key_name: {Ref: KeyName}
Metadata:
os-collect-config:
Description: Name of an existing EC2 KeyPair to enable SSH access to the instances
Type: String
Default: default
- Flavor:
+ OvercloudComputeFlavor:
Description: Use this flavor
Type: String
Default: baremetal
{Ref: NovaImage}
image_update_policy:
Ref: ImageUpdatePolicy
- flavor: {Ref: Flavor}
+ flavor: {Ref: OvercloudComputeFlavor}
key_name: {Ref: KeyName}
Metadata:
os-collect-config:
Description: The password for the cinder service account, used by cinder-api.
Type: String
NoEcho: true
- Flavor:
+ OvercloudControlFlavor:
Default: baremetal
- Description: Flavor to request when deploying.
+ Description: Flavor for control nodes to request when deploying.
+ Type: String
+ OvercloudComputeFlavor:
+ Default: baremetal
+ Description: Flavor for compute nodes to request when deploying.
Type: String
GlancePassword:
Default: unset
image_update_policy:
Ref: ImageUpdatePolicy
flavor:
- Ref: Flavor
+ Ref: OvercloudControlFlavor
key_name:
Ref: KeyName
Metadata: