create
******


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

Creates a new mount target in the specified compartment and subnet.
You can associate a file system with a mount target only when they
exist in the same availability domain. Instances can connect to mount
targets in another availablity domain, but you might see higher
latency than with instances in the same availability domain as the
mount target.

Mount targets have one or more private IP addresses that you can
provide as the host portion of remote target parameters in client
mount commands. These private IP addresses are listed in the
privateIpIds property of the mount target and are highly available.
Mount targets also consume additional IP addresses in their subnet. Do
not use /30 or smaller subnets for mount target creation because they
do not have sufficient available IP addresses. Allow at least three IP
addresses for each mount target.

For information about access control and compartments, see Overview of
the IAM Service.

For information about availability domains, see Regions and
Availability Domains. To get a list of availability domains, use the
*ListAvailabilityDomains* operation in the Identity and Access
Management Service API.

All Oracle Cloud Infrastructure Services resources, including mount
targets, get an Oracle-assigned, unique ID called an Oracle Cloud
Identifier (OCID).  When you create a resource, you can find its OCID
in the response. You can also retrieve a resource's OCID by using a
List API operation on that resource type, or by viewing the resource
in the Console.


Usage
=====

   oci fs mount-target create [OPTIONS]


Options
=======


--availability-domain [text]
----------------------------

The availability domain in which to create the mount target.

Example: *Uocm:PHX-AD-1* [required]


--compartment-id, -c [text]
---------------------------

The OCID of the compartment in which to create the mount target.
[required]


--subnet-id [text]
------------------

The OCID of the subnet in which to create the mount target. [required]


--display-name [text]
---------------------

A user-friendly name. It does not have to be unique, and it is
changeable. Avoid entering confidential information.

Example: *My mount target*


--hostname-label [text]
-----------------------

The hostname for the mount target's IP address, used for DNS
resolution. The value is the hostname portion of the private IP
address's fully qualified domain name (FQDN). For example, *files-1*
in the FQDN *files-1.subnet123.vcn1.oraclevcn.com*. Must be unique
across all VNICs in the subnet and comply with RFC 952 and RFC 1123.

For more information, see DNS in Your Virtual Cloud Network.

Example: *files-1*


--ip-address [text]
-------------------

A private IP address of your choice. Must be an available IP address
within the subnet's CIDR. If you don't specify a value, Oracle
automatically assigns a private IP address from the subnet.

Example: *10.0.3.3*


--wait-for-state [CREATING|ACTIVE|DELETING|DELETED|FAILED]
----------------------------------------------------------

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.


--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-interval-seconds [integer]
---------------------------------

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


--from-json [text]
------------------

Provide input to this command as a JSON document from a file.

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


-?, -h, --help
--------------

Show this message and exit.
