"create-dedicated-vm-host-host-group-placement-constraint-details"
******************************************************************

* Description

* Usage

* Required Parameters

* Optional Parameters

* Global Parameters

* Example using required parameter


Description
===========

Creates a new dedicated virtual machine host in the specified
compartment and the specified availability domain. Dedicated virtual
machine hosts enable you to run your Compute virtual machine (VM)
instances on dedicated servers that are a single tenant and not shared
with other customers. For more information, see Dedicated Virtual
Machine Hosts.


Usage
=====

   oci compute dedicated-vm-host create-dedicated-vm-host-host-group-placement-constraint-details [OPTIONS]


Required Parameters
===================

--availability-domain [text]

The availability domain of the dedicated virtual machine host.

Example:

   Uocm:PHX-AD-1

--compartment-id, -c [text]

The OCID of the compartment.

--dedicated-vm-host-shape [text]

The dedicated virtual machine host shape. The shape determines the
number of CPUs and other resources available for VM instances launched
on the dedicated virtual machine host.

--placement-constraint-details-compute-host-group-id [text]

The OCID of the compute host group. This is only available for
dedicated capacity customers.


Optional Parameters
===================

--defined-tags [complex type]

Defined tags for this resource. Each key is predefined and scoped to a
namespace. For more information, see Resource Tags.

Example:

   {"Operations": {"CostCenter": "42"}}

This is a complex type whose value must be valid JSON. The value can
be provided as a string on the command line or passed in as a file
using the file://path/to/file syntax.

The "--generate-param-json-input" option can be used to generate an
example of the JSON which must be provided. We recommend storing this
example in a file, modifying it as needed and then passing it back in
via the file:// syntax.

--display-name [text]

A user-friendly name. Does not have to be unique, and it’s changeable.
Avoid entering confidential information.

--fault-domain [text]

The fault domain for the dedicated virtual machine host’s assigned
instances. For more information, see Fault Domains. If you do not
specify the fault domain, the system selects one for you. To change
the fault domain for a dedicated virtual machine host, delete it and
create a new dedicated virtual machine host in the preferred fault
domain.

To get a list of fault domains, use the *ListFaultDomains* operation
in the Identity and Access Management Service API.

Example:

   FAULT-DOMAIN-1

--freeform-tags [complex type]

Free-form tags for this resource. Each tag is a simple key-value pair
with no predefined name, type, or namespace. For more information, see
Resource Tags.

Example:

   {"Department": "Finance"}

This is a complex type whose value must be valid JSON. The value can
be provided as a string on the command line or passed in as a file
using the file://path/to/file syntax.

The "--generate-param-json-input" option can be used to generate an
example of the JSON which must be provided. We recommend storing this
example in a file, modifying it as needed and then passing it back in
via the file:// syntax.

--from-json [text]

Provide input to this command as a JSON document from a file using the
file://path-to/file syntax.

The "--generate-full-command-json-input" option can be used to
generate a sample json file to be used with this command option. The
key names are pre-populated and match the command option names
(converted to camelCase format, e.g. compartment-id –> compartmentId),
while the values of the keys need to be populated by the user before
using the sample file as an input to this command. For any command
option that accepts multiple values, the value of the key can be a
JSON array.

Options can still be provided on the command line. If an option exists
in both the JSON document and the command line then the command line
specified value will be used.

For examples on usage of this option, please see our “using CLI with
advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions

--max-wait-seconds [integer]

The maximum time to wait for the resource to reach the lifecycle state
defined by "--wait-for-state". Defaults to 1200 seconds.

--wait-for-state [text]

This operation creates, modifies or deletes a resource that has a
defined lifecycle state. Specify this option to perform the action and
then wait until the resource reaches a given lifecycle state. Multiple
states can be specified, returning on the first state. For example, "
--wait-for-state" SUCCEEDED "--wait-for-state" FAILED would return on
whichever lifecycle state is reached first. If timeout is reached, a
return code of 2 is returned. For any other error, a return code of 1
is returned.

Accepted values are:

   ACTIVE, CREATING, DELETED, DELETING, FAILED, UPDATING

--wait-interval-seconds [integer]

Check every "--wait-interval-seconds" to see whether the resource has
reached the lifecycle state defined by "--wait-for-state". Defaults to
30 seconds.


Global Parameters
=================

Use "oci --help" for help on global parameters.

"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
defaults-file", "--endpoint", "--generate-full-command-json-input", "
--generate-param-json-input", "--help", "--latest-version", "--max-
retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
"--output", "--profile", "--proxy", "--query", "--raw-output", "--
read-timeout", "--realm-specific-endpoint", "--region", "--release-
info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"


Example using required parameter
================================

Copy the following CLI commands into a file named example.sh. Run the
command by typing “bash example.sh” and replacing the example
parameters with your own.

Please note this sample will only work in the POSIX-compliant bash-
like shell. You need to set up the OCI configuration and appropriate
security policies before trying the examples.

       export availability_domain=<substitute-value-of-availability_domain> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/compute/dedicated-vm-host/create-dedicated-vm-host-host-group-placement-constraint-details.html#cmdoption-availability-domain
       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/compute/dedicated-vm-host/create-dedicated-vm-host-host-group-placement-constraint-details.html#cmdoption-compartment-id
       export dedicated_vm_host_shape=<substitute-value-of-dedicated_vm_host_shape> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/compute/dedicated-vm-host/create-dedicated-vm-host-host-group-placement-constraint-details.html#cmdoption-dedicated-vm-host-shape
       export placement_constraint_details_compute_host_group_id=<substitute-value-of-placement_constraint_details_compute_host_group_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/compute/dedicated-vm-host/create-dedicated-vm-host-host-group-placement-constraint-details.html#cmdoption-placement-constraint-details-compute-host-group-id

       oci compute dedicated-vm-host create-dedicated-vm-host-host-group-placement-constraint-details --availability-domain $availability_domain --compartment-id $compartment_id --dedicated-vm-host-shape $dedicated_vm_host_shape --placement-constraint-details-compute-host-group-id $placement_constraint_details_compute_host_group_id
