723db1317c
Currently all the OS::Nova::Server resource created don't pass any user-data. It's possible to pass user-data as well as using heat SoftwareConfig/SoftwareDeployment resources, and this can be useful when you have simple "first boot" tasks which are possible either via cloud-init, or via simple run-once scripts. This enables passing such data by implementing a new provider resource OS::TripleO::NodeUserData, which defaults to passing an empty mime archive (thus it's a no-op). An example of non no-op usage is also provided. Change-Id: Id0caba69768630e3a10439ba1fc2547a609c0cfe
22 lines
1.2 KiB
YAML
22 lines
1.2 KiB
YAML
resource_registry:
|
|
OS::TripleO::BlockStorage: puppet/cinder-storage-puppet.yaml
|
|
OS::TripleO::Compute: puppet/compute-puppet.yaml
|
|
OS::TripleO::SoftwareDeployment: OS::Heat::StructuredDeployment
|
|
OS::TripleO::Controller: puppet/controller-puppet.yaml
|
|
OS::TripleO::ObjectStorage: puppet/swift-storage-puppet.yaml
|
|
OS::TripleO::Net::SoftwareConfig: net-config-bridge.yaml
|
|
OS::TripleO::CephStorage: puppet/ceph-storage-puppet.yaml
|
|
OS::TripleO::ControllerPostDeployment: puppet/controller-post-puppet.yaml
|
|
OS::TripleO::ComputePostDeployment: puppet/compute-post-puppet.yaml
|
|
OS::TripleO::ObjectStoragePostDeployment: puppet/swift-storage-post.yaml
|
|
OS::TripleO::BlockStoragePostDeployment: puppet/cinder-storage-post.yaml
|
|
OS::TripleO::CephStoragePostDeployment: puppet/ceph-storage-post-puppet.yaml
|
|
OS::TripleO::SwiftDevicesAndProxy::SoftwareConfig: puppet/swift-devices-and-proxy-config.yaml
|
|
OS::TripleO::CephClusterConfig::SoftwareConfig: puppet/ceph-cluster-config.yaml
|
|
OS::TripleO::AllNodes::SoftwareConfig: puppet/all-nodes-config.yaml
|
|
OS::TripleO::BootstrapNode::SoftwareConfig: puppet/bootstrap-config.yaml
|
|
OS::TripleO::NodeUserData: firstboot/userdata_default.yaml
|
|
|
|
parameter_defaults:
|
|
EnablePackageInstall: false
|