"create"
********

* Description

* Usage

* Required Parameters

* Optional Parameters

* Global Parameters

* Example using required parameter


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

Create a Database Infrastructure using the specified details.


Usage
=====

   oci datacc infrastructure create [OPTIONS]


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

--compartment-id, -c [text]

The OCID of the compartment.

--control-plane-server1 [text]

The IP address for the first control plane server.

--control-plane-server2 [text]

The IP address for the second control plane server.

--display-name [text]

The user-friendly name for the Database Infrastructure. The name does
not need to be unique.

--dns-servers [complex type]

The list of DNS server IP addresses. Maximum of 3 allowed. 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.

--gateway [text]

The gateway for the control plane network.

--netmask [text]

The netmask for the control plane network.

--ntp-servers [complex type]

The list of NTP server IP addresses. Maximum of 3 allowed. 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.

--shape [text]

The shape of the Database Infrastructure. The shape determines the
amount of CPU, storage, and memory resources allocated to the
instance.

Accepted values are:

   EIGHTEEN_SSDS, SIX_SSDS, TWELVE_SSDS, TWENTY_FOUR_SSDS

--system-model [text]

Database Infrastructure System Model specification. The system model
determines the model of the Database Infrastructure hardware to be
used.

Accepted values are:

   X10_HA_512, X11_HA_768, X8_HA_384


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

--acfs-size-in-gbs [text]

The amount of storage (in GB) in the DATA disk group that is reserved
for creating local storage for VM Clusters and application VMs.

--admin-networkcidr [text]

The CIDR block for the system network. The system network is a private
network in Database Infrastructure and is not connected to your
corporate network. The system network is used for storage (ASM)
traffic, high-performance interconnect traffic and administration of
infrastructure components.

--backup-bond-iface [text]

The network bonding interface for backup network for the Database
Infrastructure.

Accepted values are:

   BTBOND1, BTBOND2, BTBOND3, BTBOND4, BTBOND5, BTBOND6

--backup-bond-mode [text]

The network bonding mode for Backup networks for the Database
Infrastructure.

Accepted values are:

   ACTIVE_BACKUP, LACP

--client-bond-iface [text]

The network bonding interface for client network for the Database
Infrastructure.

Accepted values are:

   BTBOND1, BTBOND2, BTBOND3, BTBOND4, BTBOND5, BTBOND6

--client-bond-mode [text]

The network bonding mode for Client networks for the Database
Infrastructure.

Accepted values are:

   ACTIVE_BACKUP, LACP

--contacts [complex type]

The list of contacts for the Database Infrastructure.

This option is a JSON list with items of type InfrastructureContact.
For documentation on InfrastructureContact please see our API
reference: https://docs.oracle.com/en-
us/iaas/api/#/en/baseinfra/20251101/datatypes/InfrastructureContact.
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.

--corporate-proxy [text]

The corporate network proxy for access to the control plane network.
Oracle recommends using an HTTPS proxy when possible for enhanced
security.

--cps-bond-iface [text]

The network bonding interface for CPS network for the Database
Infrastructure.

Accepted values are:

   BTBOND1, BTBOND2, BTBOND3, BTBOND4, BTBOND5, BTBOND6

--cps-bond-mode [text]

The network bonding mode for CPS networks for the Database
Infrastructure.

Accepted values are:

   ACTIVE_BACKUP, LACP

--data-disk-percentage [integer]

Percentage of disk space assigned for DATA disk group. Remaining disk
space will get assiged to RECO disk group

--defined-tags [complex type]

Defined tags for this resource. Each key is predefined and scoped to a
namespace. Example: *{“foo-namespace”: {“bar-key”: “value”}}* 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.

--description [text]

Database Infrastructure description.

--freeform-tags [complex type]

Simple key-value pair that is applied without any predefined name,
type or scope. This tag option exists for cross-compatibility only.
Example: *{“bar-key”: “value”}* 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

--maintenance-window [complex type]

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.

--max-wait-seconds [integer]

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

--vlan-id [text]

The CPS network VLAN ID.

--wait-for-state [text]

This operation asynchronously creates, modifies or deletes a resource
and uses a work request to track the progress of the operation.
Specify this option to perform the action and then wait until the work
request reaches a certain state. Multiple states can be specified,
returning on the first state. For example, "--wait-for-state" ACCEPTED
"--wait-for-state" WAITING 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:

   ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, SUCCEEDED, WAITING

--wait-interval-seconds [integer]

Check every "--wait-interval-seconds" to see whether the work request
has reached the 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", "--enable-dual-stack", "--enable-propagation", "--
endpoint", "--federation-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 and paste the following example into a JSON file, replacing the
example parameters with your own.

       oci datacc infrastructure create --generate-param-json-input dns-servers > dns-servers.json
       oci datacc infrastructure create --generate-param-json-input ntp-servers > ntp-servers.json

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 compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/datacc/infrastructure/create.html#cmdoption-compartment-id
       export control_plane_server1=<substitute-value-of-control_plane_server1> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/datacc/infrastructure/create.html#cmdoption-control-plane-server1
       export control_plane_server2=<substitute-value-of-control_plane_server2> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/datacc/infrastructure/create.html#cmdoption-control-plane-server2
       export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/datacc/infrastructure/create.html#cmdoption-display-name
       export gateway=<substitute-value-of-gateway> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/datacc/infrastructure/create.html#cmdoption-gateway
       export netmask=<substitute-value-of-netmask> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/datacc/infrastructure/create.html#cmdoption-netmask
       export shape=<substitute-value-of-shape> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/datacc/infrastructure/create.html#cmdoption-shape
       export system_model=<substitute-value-of-system_model> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/datacc/infrastructure/create.html#cmdoption-system-model

       oci datacc infrastructure create --compartment-id $compartment_id --control-plane-server1 $control_plane_server1 --control-plane-server2 $control_plane_server2 --display-name $display_name --dns-servers file://dns-servers.json --gateway $gateway --netmask $netmask --ntp-servers file://ntp-servers.json --shape $shape --system-model $system_model
