37 lines
1.8 KiB
JSON
37 lines
1.8 KiB
JSON
{
|
|
"namespace": "OS::Compute::InstanceData",
|
|
"display_name": "Instance Config Data",
|
|
"description": "Instances can perform self-configuration based on data made available to the running instance. These properties affect instance configuration.",
|
|
"visibility": "public",
|
|
"protected": true,
|
|
"resource_type_associations": [
|
|
{
|
|
"name": "OS::Glance::Image"
|
|
},
|
|
{
|
|
"name": "OS::Cinder::Volume",
|
|
"properties_target": "image"
|
|
}
|
|
],
|
|
"properties": {
|
|
"img_config_drive": {
|
|
"title": "Config Drive",
|
|
"description": "This property specifies whether or not Nova should use a config drive when booting the image. Mandatory means that Nova will always use a config drive when booting the image. OpenStack can be configured to write metadata to a special configuration drive that will be attached to the instance when it boots. The instance can retrieve any information from the config drive. One use case for the config drive is to pass network configuration information to the instance. See also: http://docs.openstack.org/user-guide/content/config-drive.html",
|
|
"type": "string",
|
|
"enum": [
|
|
"optional",
|
|
"mandatory"
|
|
]
|
|
},
|
|
"os_require_quiesce": {
|
|
"title": "Require Quiescent File system",
|
|
"description": "This property specifies whether or not the filesystem must be quiesced during snapshot processing. For volume backed and image backed snapshots, yes means that snapshotting is aborted when quiescing fails, whereas, no means quiescing will be skipped and snapshot processing will continue after the quiesce failure.",
|
|
"type": "string",
|
|
"enum": [
|
|
"yes",
|
|
"no"
|
|
]
|
|
}
|
|
}
|
|
}
|