oci-cli 3.66.1__py3-none-any.whl → 3.67.0__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-collection/create-guest-os.txt

@@ -0,0 +1,180 @@
+"create-guest-os"
+*****************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Creates a new Exadata Fleet Update Collection.
+
+
+Usage
+=====
+
+   oci fleet-software-update fsu-collection create-guest-os [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+The OCID of the Compartment.
+
+--service-type [text]
+
+Exadata service type for the target resource members.
+
+Accepted values are:
+
+   EXACC, EXACS
+
+--source-major-version [text]
+
+Major version of Exadata Image (Guest OS) release for Exadata VM
+Cluster targets to be included in the Exadata Fleet Update Collection.
+Only Exadata VM Clusters whose ‘systemVersion’ is related to the major
+version will be added to the Exadata Fleet Update Collection. For more
+details, refer to Oracle document 2075007.1
+
+Accepted values are:
+
+   EXA_OL_5, EXA_OL_6, EXA_OL_7, EXA_OL_8
+
+
+Optional Parameters
+===================
+
+--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.
+
+--display-name [text]
+
+The user-friendly name for the Exadata Fleet Update Collection.
+
+--fleet-discovery [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.
+
+--freeform-tags [complex type]
+
+Simple key-value pair that is applied without any predefined name,
+type or scope. 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
+
+--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.
+
+--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"
+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:
+
+   ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, NEEDS_ATTENTION, 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", "--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 compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-software-update/fsu-collection/create-guest-os.html#cmdoption-compartment-id
+       export service_type=<substitute-value-of-service_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-software-update/fsu-collection/create-guest-os.html#cmdoption-service-type
+       export source_major_version=<substitute-value-of-source_major_version> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-software-update/fsu-collection/create-guest-os.html#cmdoption-source-major-version
+
+       oci fleet-software-update fsu-collection create-guest-os --compartment-id $compartment_id --service-type $service_type --source-major-version $source_major_version

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-collection/create.txt

@@ -31,7 +31,7 @@ Required Parameters
 
 --compartment-id, -c [text]
 
-Compartment Identifier
+The OCID of the Compartment.
 
 --service-type [text]
 
@@ -44,11 +44,14 @@ Accepted values are:
 --type [text]
 
 Collection type. DB: Only Database entity type resources allowed. GI:
-CloudVMCluster and VMCluster entity type resources allowed.
+CloudVMCluster and VMCluster entity type resources allowed. GUEST_OS:
+CloudVmCluster and VmCluster entity type resources are allowed.
+EXADB_STACK: CloudVmCluster and VmCluster entity type resources are
+allowed.
 
 Accepted values are:
 
-   DB, GI
+   DB, EXADB_STACK, GI, GUEST_OS
 
 
 Optional Parameters
@@ -69,7 +72,7 @@ via the file:// syntax.
 
 --display-name [text]
 
-Exadata Fleet Update Collection Identifier.
+The user-friendly name for the Exadata Fleet Update Collection.
 
 --freeform-tags [complex type]
 

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-collection/update.txt

@@ -52,7 +52,7 @@ via the file:// syntax.
 
 --display-name [text]
 
-Exadata Fleet Update Collection display name.
+The user-friendly name for the Exadata Fleet Update Collection.
 
 --force
 

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-collection-summary/list.txt

@@ -117,7 +117,7 @@ A filter to return only resources whose type matches the given type.
 
 Accepted values are:
 
-   DB, GI
+   DB, EXADB_STACK, GI, GUEST_OS
 
 
 Global Parameters

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-collection.txt

@@ -19,8 +19,12 @@ Available Commands
 
 * create-db
 
+* create-exadb-stack
+
 * create-gi
 
+* create-guest-os
+
 * delete
 
 * delete-fsu-collection-target

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-cycle/clone.txt

@@ -73,11 +73,11 @@ via the file:// syntax.
 
 --compartment-id, -c [text]
 
-Compartment Identifier.
+The OCID of the Compartment.
 
 --display-name [text]
 
-Exadata Fleet Update Cycle display name.
+The user-friendly name for the Exadata Fleet Update Cycle.
 
 --from-json [text]
 
@@ -103,9 +103,10 @@ nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
 
 --fsu-collection-id [text]
 
-OCID identifier for the Collection ID the Exadata Fleet Update Cycle
-will be assigned to. If not specified, it will be assigned to the same
-Collection as the source Exadata Fleet Update Cycle.
+The OCID of the Exadata Fleet Update Collection which will be updated
+by the Exadata Fleet Update Cycle being created. If not specified, the
+cloned Exadata Fleet Update Cycle will be assigned to the same Exadata
+Fleet Update Collection as the source Exadata Fleet Update Cycle.
 
 --max-wait-seconds [integer]
 

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-cycle/create-fsu-cycle-create-upgrade-fsu-cycle.txt

@@ -31,12 +31,12 @@ Required Parameters
 
 --compartment-id, -c [text]
 
-Compartment Identifier.
+The OCID of the Compartment.
 
 --fsu-collection-id [text]
 
-OCID identifier for the Collection ID the Exadata Fleet Update Cycle
-will be assigned to.
+The OCID of the Exadata Fleet Update Collection which will be updated
+by the Exadata Fleet Update Cycle being created.
 
 --goal-version-details [complex type]
 
@@ -101,7 +101,7 @@ via the file:// syntax.
 
 --display-name [text]
 
-Exadata Fleet Update Cycle display name.
+The user-friendly name for the Exadata Fleet Update Cycle.
 
 --freeform-tags [complex type]
 

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-cycle/create-patch.txt

@@ -31,12 +31,12 @@ Required Parameters
 
 --compartment-id, -c [text]
 
-Compartment Identifier.
+The OCID of the Compartment.
 
 --fsu-collection-id [text]
 
-OCID identifier for the Collection ID the Exadata Fleet Update Cycle
-will be assigned to.
+The OCID of the Exadata Fleet Update Collection which will be updated
+by the Exadata Fleet Update Cycle being created.
 
 --goal-version-details [complex type]
 
@@ -101,7 +101,7 @@ via the file:// syntax.
 
 --display-name [text]
 
-Exadata Fleet Update Cycle display name.
+The user-friendly name for the Exadata Fleet Update Cycle.
 
 --freeform-tags [complex type]
 
@@ -140,9 +140,11 @@ nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
 
 --is-ignore-missing-patches [complex type]
 
-List of patch IDs to ignore. 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.
+List of identifiers of patches to ignore. This attribute will be
+ignored for Exadata Image (Guest OS) maintenance update. 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
@@ -151,14 +153,14 @@ via the file:// syntax.
 
 --is-ignore-patches [boolean]
 
-Ignore all patches between the source and target homes during
-patching.
+Ignore patch conflicts or missing patches between the source and goal
+homes. This attribute will be ignored for Exadata Image (Guest OS)
+maintenance update.
 
 --is-keep-placement [boolean]
 
-Ensure that services of administrator-managed Oracle RAC or Oracle RAC
-One databases are running on the same instances before and after the
-move operation.
+Ensure that database services are online on the same VMs before and
+after the maintenance update.
 
 --max-drain-timeout-in-sec [integer]
 

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-cycle/create.txt

@@ -31,12 +31,12 @@ Required Parameters
 
 --compartment-id, -c [text]
 
-Compartment Identifier.
+The OCID of the Compartment.
 
 --fsu-collection-id [text]
 
-OCID identifier for the Collection ID the Exadata Fleet Update Cycle
-will be assigned to.
+The OCID of the Exadata Fleet Update Collection which will be updated
+by the Exadata Fleet Update Cycle being created.
 
 --goal-version-details [complex type]
 
@@ -109,7 +109,7 @@ via the file:// syntax.
 
 --display-name [text]
 
-Exadata Fleet Update Cycle display name.
+The user-friendly name for the Exadata Fleet Update Cycle.
 
 --freeform-tags [complex type]
 

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-cycle/update-fsu-cycle-exadb-stack-fsu-goal-version-details.txt

@@ -0,0 +1,230 @@
+"update-fsu-cycle-exadb-stack-fsu-goal-version-details"
+*******************************************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Updates the Exadata Fleet Update Cycle identified by the ID.
+
+
+Usage
+=====
+
+   oci fleet-software-update fsu-cycle update-fsu-cycle-exadb-stack-fsu-goal-version-details [OPTIONS]
+
+
+Required Parameters
+===================
+
+--fsu-cycle-id [text]
+
+Unique Exadata Fleet Update Cycle identifier.
+
+--goal-version-details-components [complex type]
+
+Details of goal versions for components in an Exadata software stack.
+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.
+
+
+Optional Parameters
+===================
+
+--batching-strategy [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.
+
+--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.
+
+--diagnostics-collection [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.
+
+--display-name [text]
+
+Exadata Fleet Update Cycle display name.
+
+--force
+
+Perform update without prompting for confirmation.
+
+--freeform-tags [complex type]
+
+Simple key-value pair that is applied without any predefined name,
+type or scope. 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
+
+--goal-version-details-home-policy [text]
+
+Goal home policy to use when Staging the Goal Version during patching.
+CREATE_NEW: Create a new DBHome (for Database Collections) for the
+specified image or version. USE_EXISTING: All database targets in the
+same VMCluster or CloudVmCluster will be moved to a shared database
+home.   If an existing home for the selected image or version is not
+found in the VM Cluster for a target database, then a new home will be
+created.   If more than one existing home for the selected image is
+found, then the home with the least number of databases will be used.
+If multiple homes have the least number of databases, then a home will
+be selected at random.
+
+Accepted values are:
+
+   CREATE_NEW, USE_EXISTING
+
+--goal-version-details-new-home-prefix [text]
+
+Prefix name used for new DB home resources created as part of the
+Stage Action. Format: <specified_prefix>_<timestamp> If not specified,
+a default OCI DB home resource will be generated for the new DB home
+resources created.
+
+--if-match [text]
+
+For optimistic concurrency control. In the PUT or DELETE call for a
+resource, set the *if-match* parameter to the value of the etag from a
+previous GET or POST response for that resource. The resource will be
+updated or deleted only if the etag you provide matches the resource’s
+current etag value.
+
+--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.
+
+--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"
+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:
+
+   ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, NEEDS_ATTENTION, 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", "--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 fleet-software-update fsu-cycle create --generate-param-json-input goal-version-details > goal-version-details.json
+
+       oci fleet-software-update fsu-cycle update-fsu-cycle-exadb-stack-fsu-goal-version-details --generate-param-json-input goal-version-details-components > goal-version-details-components.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/fleet-software-update/fsu-collection/create.html#cmdoption-compartment-id
+       export service_type=<substitute-value-of-service_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-software-update/fsu-collection/create.html#cmdoption-service-type
+       export type=<substitute-value-of-type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-software-update/fsu-collection/create.html#cmdoption-type
+
+       fsu_collection_id=$(oci fleet-software-update fsu-collection create --compartment-id $compartment_id --service-type $service_type --type $type --query data.id --raw-output)
+
+       fsu_cycle_id=$(oci fleet-software-update fsu-cycle create --compartment-id $compartment_id --fsu-collection-id $fsu_collection_id --goal-version-details file://goal-version-details.json --type $type --query data.id --raw-output)
+
+       oci fleet-software-update fsu-cycle update-fsu-cycle-exadb-stack-fsu-goal-version-details --fsu-cycle-id $fsu_cycle_id --goal-version-details-components file://goal-version-details-components.json

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-cycle/update-patch.txt

@@ -140,11 +140,11 @@ current etag value.
 
 --is-ignore-missing-patches [complex type]
 
-List of patch IDs to ignore. An empty array removes the previously
-stored patch IDs in the Maintenance Cycle properties. 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.
+List of identifiers of patches to ignore. Specify an empty array to
+unset the field. This attribute will be ignored for Exadata Image
+(Guest OS) maintenance update. 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
@@ -153,14 +153,14 @@ via the file:// syntax.
 
 --is-ignore-patches [boolean]
 
-Ignore all patches between the source and target homes during
-patching.
+Ignore patch conflicts or missing patches between the source and goal
+homes. This attribute will be ignored for Exadata Image (Guest OS)
+maintenance update.
 
 --is-keep-placement [boolean]
 
-Ensure that services of administrator-managed Oracle RAC or Oracle RAC
-One databases are running on the same instances before and after the
-move operation.
+Ensure that database services are online on the same VMs before and
+after the maintenance update.
 
 --max-wait-seconds [integer]
 

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-cycle-summary/list.txt

@@ -49,7 +49,7 @@ given type.
 
 Accepted values are:
 
-   DB, GI
+   DB, EXADB_STACK, GI, GUEST_OS
 
 --display-name [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-cycle.txt

@@ -29,6 +29,8 @@ Available Commands
 
 * update-fifty-batch
 
+* update-fsu-cycle-exadb-stack-fsu-goal-version-details
+
 * update-fsu-cycle-update-upgrade-fsu-cycle
 
 * update-image-id-target