create
******


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

Creates a new volume group in the specified compartment. A volume
group can have at most 20 block volumes. A volume group is a
collection of volumes and may be created from a list of volumes,
cloning an existing volume group or by restoring a volume group
backup. You may optionally specify a *display name* for the volume
group, which is simply a friendly name or description. It does not
have to be unique, and you can change it. Avoid entering confidential
information.


Usage
=====

   oci bv volume-group create [OPTIONS]


Options
=======


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

The Availability Domain of the volume group. [required]


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

The OCID of the compartment that contains the volume group. [required]


--source-details [complex type]
-------------------------------

Specifies the volume group source details for a new volume group. The
volume source is either another a list of volume ids in the same
Availability Domain, another volume group or a volume group backup.
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.

   [required]


--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 for the volume group. Does not have to be unique,
and it's changeable.


--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.


--wait-for-state [PROVISIONING|AVAILABLE|TERMINATING|TERMINATED|FAULTY]
-----------------------------------------------------------------------

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.
