2.12.6.3. hammer compute-profile values create
コンピュートプロファイルの値セットを作成します。
Usage: hammer compute-profile values create [OPTIONS] Options: --compute-attributes COMPUTE_ATTRS Compute resource attributes Comma-separated list of key=value. JSON is acceptable and preferred way for complex parameters --compute-profile COMPUTE_PROFILE_NAME Compute profile name --compute-profile-id COMPUTE_PROFILE_ID --compute-resource COMPUTE_RESOURCE_NAME Compute resource name --compute-resource-id COMPUTE_RESOURCE_ID --interface INTERFACE Interface parameters, should be comma separated list of values Comma-separated list of key=value. JSON is acceptable and preferred way for complex parameters Can be specified multiple times. --location LOCATION_NAME Location name --location-id LOCATION_ID --location-title LOCATION_TITLE Location title --organization ORGANIZATION_NAME Organization name --organization-id ORGANIZATION_ID Organization ID --organization-title ORGANIZATION_TITLE Organization title --volume VOLUME Volume parameters, should be comma separated list of values Comma-separated list of key=value. JSON is acceptable and preferred way for complex parameters Can be specified multiple times. -h, --help Print help Provider specific options: NOTE: Bold attributes are required. EC2: --volume: --interface: --compute-attributes: availability_zone flavor_id groups security_group_ids managed_ip GCE: --volume: size_gb Volume size in GB, integer value --interface: --compute-attributes: machine_type network associate_external_ip Libvirt: --volume: pool_name One of available storage pools capacity String value, e.g. 10G allocation Initial allocation, e.g. 0G format_type Possible values: raw, qcow2 --interface: compute_type Possible values: bridge, network compute_bridge Name of interface according to type compute_model Possible values: virtio, rtl8139, ne2k_pci, pcnet, e1000 compute_network Libvirt instance network, e.g. default --compute-attributes: cpus Number of CPUs memory String, amount of memory, value in bytes cpu_mode Possible values: default, host-model, host-passthrough OpenStack: --volume: --interface: --compute-attributes: availability_zone boot_from_volume flavor_ref image_ref tenant_id security_groups network oVirt: --volume: size_gb Volume size in GB, integer value storage_domain ID or name of storage domain bootable Boolean, set 1 for bootable, only one volume can be bootable preallocate Boolean, set 1 to preallocate wipe_after_delete Boolean, set 1 to wipe disk after delete interface Disk interface name, must be ide, virto or virto_scsi --interface: compute_name Compute name, e.g. eth0 compute_network Select one of available networks for a cluster, must be an ID compute_interface Interface type --compute-attributes: cluster ID of cluster to use template Hardware profile to use cores Integer value, number of cores sockets Integer value, number of sockets memory Amount of memory, integer value in bytes Rackspace: --volume: --interface: --compute-attributes: flavor_id VMware: --volume: name storage_pod Storage Pod ID from VMware datastore Datastore ID from VMware mode persistent/independent_persistent/independent_nonpersistent size_gb Integer number, volume size in GB thin true/false eager_zero true/false controller_key Associated SCSI controller key --interface: compute_type Type of the network adapter, for example one of: VirtualVmxnet3 VirtualE1000 See documentation center for your version of vSphere to find more details about available adapter types: https://www.vmware.com/support/pubs/ compute_network Network ID from VMware --compute-attributes: cluster Cluster ID from VMware corespersocket Number of cores per socket (applicable to hardware versions < 10 only) cpus CPU count memory_mb Integer number, amount of memory in MB path Path to folder resource_pool Resource Pool ID from VMware firmware automatic/bios/efi guest_id Guest OS ID form VMware hardware_version Hardware version ID from VMware memoryHotAddEnabled Must be a 1 or 0, lets you add CPU resources while the machine is on cpuHotAddEnabled Must be a 1 or 0, lets you add memory resources while the machine is on add_cdrom Must be a 1 or 0, Add a CD-ROM drive to the virtual machine annotation Annotation Notes scsi_controllers List with SCSI controllers definitions type - ID of the controller from VMware key - Key of the controller (e.g. 1000) AzureRM: --volume: --interface: compute_network Select one of available Azure Subnets, must be an ID compute_public_ip Public IP (None, Static, Dynamic) compute_private_ip Static Private IP (expressed as true or false) --compute-attributes: resource_group Existing Azure Resource Group of user vm_size VM Size, eg. Standard_A0 etc. username The Admin username password The Admin password platform OS type eg. Linux ssh_key_data SSH key for passwordless authentication os_disk_caching OS disk caching premium_os_disk Premium OS Disk, Boolean as 0 or 1 script_command Custom Script Command script_uris Comma seperated file URIs
Usage:
hammer compute-profile values create [OPTIONS]
Options:
--compute-attributes COMPUTE_ATTRS Compute resource attributes
Comma-separated list of key=value.
JSON is acceptable and preferred way for complex parameters
--compute-profile COMPUTE_PROFILE_NAME Compute profile name
--compute-profile-id COMPUTE_PROFILE_ID
--compute-resource COMPUTE_RESOURCE_NAME Compute resource name
--compute-resource-id COMPUTE_RESOURCE_ID
--interface INTERFACE Interface parameters, should be comma separated list of values
Comma-separated list of key=value.
JSON is acceptable and preferred way for complex parameters
Can be specified multiple times.
--location LOCATION_NAME Location name
--location-id LOCATION_ID
--location-title LOCATION_TITLE Location title
--organization ORGANIZATION_NAME Organization name
--organization-id ORGANIZATION_ID Organization ID
--organization-title ORGANIZATION_TITLE Organization title
--volume VOLUME Volume parameters, should be comma separated list of values
Comma-separated list of key=value.
JSON is acceptable and preferred way for complex parameters
Can be specified multiple times.
-h, --help Print help
Provider specific options:
NOTE: Bold attributes are required.
EC2:
--volume:
--interface:
--compute-attributes:
availability_zone
flavor_id
groups
security_group_ids
managed_ip
GCE:
--volume:
size_gb Volume size in GB, integer value
--interface:
--compute-attributes:
machine_type
network
associate_external_ip
Libvirt:
--volume:
pool_name One of available storage pools
capacity String value, e.g. 10G
allocation
Initial allocation, e.g. 0G
format_type Possible values: raw, qcow2
--interface:
compute_type Possible values: bridge, network
compute_bridge Name of interface according to type
compute_model Possible values: virtio, rtl8139, ne2k_pci, pcnet, e1000
compute_network
Libvirt instance network, e.g. default
--compute-attributes:
cpus Number of CPUs
memory String, amount of memory, value in bytes
cpu_mode Possible values: default, host-model, host-passthrough
OpenStack:
--volume:
--interface:
--compute-attributes:
availability_zone
boot_from_volume
flavor_ref
image_ref
tenant_id
security_groups
network
oVirt:
--volume:
size_gb Volume size in GB, integer value
storage_domain ID or name of storage domain
bootable Boolean, set 1 for bootable, only one volume can be bootable
preallocate Boolean, set 1 to preallocate
wipe_after_delete Boolean, set 1 to wipe disk after delete
interface Disk interface name, must be ide, virto or virto_scsi
--interface:
compute_name Compute name, e.g. eth0
compute_network Select one of available networks for a cluster, must be an ID
compute_interface Interface type
--compute-attributes:
cluster ID of cluster to use
template Hardware profile to use
cores Integer value, number of cores
sockets Integer value, number of sockets
memory Amount of memory, integer value in bytes
Rackspace:
--volume:
--interface:
--compute-attributes:
flavor_id
VMware:
--volume:
name
storage_pod Storage Pod ID from VMware
datastore Datastore ID from VMware
mode persistent/independent_persistent/independent_nonpersistent
size_gb Integer number, volume size in GB
thin true/false
eager_zero true/false
controller_key Associated SCSI controller key
--interface:
compute_type Type of the network adapter, for example one of:
VirtualVmxnet3
VirtualE1000
See documentation center for your version of vSphere to find more details about available adapter types:
https://www.vmware.com/support/pubs/
compute_network Network ID from VMware
--compute-attributes:
cluster Cluster ID from VMware
corespersocket Number of cores per socket (applicable to hardware versions < 10 only)
cpus CPU count
memory_mb Integer number, amount of memory in MB
path Path to folder
resource_pool Resource Pool ID from VMware
firmware automatic/bios/efi
guest_id Guest OS ID form VMware
hardware_version Hardware version ID from VMware
memoryHotAddEnabled Must be a 1 or 0, lets you add CPU resources while the machine is on
cpuHotAddEnabled Must be a 1 or 0, lets you add memory resources while the machine is on
add_cdrom Must be a 1 or 0, Add a CD-ROM drive to the virtual machine
annotation Annotation Notes
scsi_controllers List with SCSI controllers definitions
type - ID of the controller from VMware
key - Key of the controller (e.g. 1000)
AzureRM:
--volume:
--interface:
compute_network Select one of available Azure Subnets, must be an ID
compute_public_ip Public IP (None, Static, Dynamic)
compute_private_ip Static Private IP (expressed as true or false)
--compute-attributes:
resource_group Existing Azure Resource Group of user
vm_size VM Size, eg. Standard_A0 etc.
username The Admin username
password The Admin password
platform OS type eg. Linux
ssh_key_data SSH key for passwordless authentication
os_disk_caching OS disk caching
premium_os_disk Premium OS Disk, Boolean as 0 or 1
script_command Custom Script Command
script_uris Comma seperated file URIs