oci.Database.CloudAutonomousVmCluster
This resource provides the Cloud Autonomous Vm Cluster resource in Oracle Cloud Infrastructure Database service.
Creates an Autonomous Exadata VM cluster in the Oracle cloud. For Exadata Cloud@Customer systems, see CreateAutonomousVmCluster.
Example Usage
using System.Collections.Generic;
using Pulumi;
using Oci = Pulumi.Oci;
return await Deployment.RunAsync(() =>
{
var testCloudAutonomousVmCluster = new Oci.Database.CloudAutonomousVmCluster("testCloudAutonomousVmCluster", new()
{
CloudExadataInfrastructureId = oci_database_cloud_exadata_infrastructure.Test_cloud_exadata_infrastructure.Id,
CompartmentId = @var.Compartment_id,
DisplayName = @var.Cloud_autonomous_vm_cluster_display_name,
SubnetId = oci_core_subnet.Test_subnet.Id,
AutonomousDataStorageSizeInTbs = @var.Cloud_autonomous_vm_cluster_autonomous_data_storage_size_in_tbs,
ClusterTimeZone = @var.Cloud_autonomous_vm_cluster_cluster_time_zone,
ComputeModel = @var.Cloud_autonomous_vm_cluster_compute_model,
CpuCoreCountPerNode = @var.Cloud_autonomous_vm_cluster_cpu_core_count_per_node,
DbServers = @var.Cloud_autonomous_vm_cluster_db_servers,
DefinedTags = @var.Cloud_autonomous_vm_cluster_defined_tags,
Description = @var.Cloud_autonomous_vm_cluster_description,
FreeformTags =
{
{ "Department", "Finance" },
},
LicenseModel = @var.Cloud_autonomous_vm_cluster_license_model,
MaintenanceWindowDetails = new Oci.Database.Inputs.CloudAutonomousVmClusterMaintenanceWindowDetailsArgs
{
CustomActionTimeoutInMins = @var.Cloud_autonomous_vm_cluster_maintenance_window_details_custom_action_timeout_in_mins,
DaysOfWeeks = new[]
{
new Oci.Database.Inputs.CloudAutonomousVmClusterMaintenanceWindowDetailsDaysOfWeekArgs
{
Name = @var.Cloud_autonomous_vm_cluster_maintenance_window_details_days_of_week_name,
},
},
HoursOfDays = @var.Cloud_autonomous_vm_cluster_maintenance_window_details_hours_of_day,
IsCustomActionTimeoutEnabled = @var.Cloud_autonomous_vm_cluster_maintenance_window_details_is_custom_action_timeout_enabled,
IsMonthlyPatchingEnabled = @var.Cloud_autonomous_vm_cluster_maintenance_window_details_is_monthly_patching_enabled,
LeadTimeInWeeks = @var.Cloud_autonomous_vm_cluster_maintenance_window_details_lead_time_in_weeks,
Months = new[]
{
new Oci.Database.Inputs.CloudAutonomousVmClusterMaintenanceWindowDetailsMonthArgs
{
Name = @var.Cloud_autonomous_vm_cluster_maintenance_window_details_months_name,
},
},
PatchingMode = @var.Cloud_autonomous_vm_cluster_maintenance_window_details_patching_mode,
Preference = @var.Cloud_autonomous_vm_cluster_maintenance_window_details_preference,
WeeksOfMonths = @var.Cloud_autonomous_vm_cluster_maintenance_window_details_weeks_of_month,
},
MemoryPerOracleComputeUnitInGbs = @var.Cloud_autonomous_vm_cluster_memory_per_oracle_compute_unit_in_gbs,
NsgIds = @var.Cloud_autonomous_vm_cluster_nsg_ids,
TotalContainerDatabases = @var.Cloud_autonomous_vm_cluster_total_container_databases,
});
});
package main
import (
"github.com/pulumi/pulumi-oci/sdk/go/oci/Database"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := Database.NewCloudAutonomousVmCluster(ctx, "testCloudAutonomousVmCluster", &Database.CloudAutonomousVmClusterArgs{
CloudExadataInfrastructureId: pulumi.Any(oci_database_cloud_exadata_infrastructure.Test_cloud_exadata_infrastructure.Id),
CompartmentId: pulumi.Any(_var.Compartment_id),
DisplayName: pulumi.Any(_var.Cloud_autonomous_vm_cluster_display_name),
SubnetId: pulumi.Any(oci_core_subnet.Test_subnet.Id),
AutonomousDataStorageSizeInTbs: pulumi.Any(_var.Cloud_autonomous_vm_cluster_autonomous_data_storage_size_in_tbs),
ClusterTimeZone: pulumi.Any(_var.Cloud_autonomous_vm_cluster_cluster_time_zone),
ComputeModel: pulumi.Any(_var.Cloud_autonomous_vm_cluster_compute_model),
CpuCoreCountPerNode: pulumi.Any(_var.Cloud_autonomous_vm_cluster_cpu_core_count_per_node),
DbServers: pulumi.Any(_var.Cloud_autonomous_vm_cluster_db_servers),
DefinedTags: pulumi.Any(_var.Cloud_autonomous_vm_cluster_defined_tags),
Description: pulumi.Any(_var.Cloud_autonomous_vm_cluster_description),
FreeformTags: pulumi.AnyMap{
"Department": pulumi.Any("Finance"),
},
LicenseModel: pulumi.Any(_var.Cloud_autonomous_vm_cluster_license_model),
MaintenanceWindowDetails: &database.CloudAutonomousVmClusterMaintenanceWindowDetailsArgs{
CustomActionTimeoutInMins: pulumi.Any(_var.Cloud_autonomous_vm_cluster_maintenance_window_details_custom_action_timeout_in_mins),
DaysOfWeeks: database.CloudAutonomousVmClusterMaintenanceWindowDetailsDaysOfWeekArray{
&database.CloudAutonomousVmClusterMaintenanceWindowDetailsDaysOfWeekArgs{
Name: pulumi.Any(_var.Cloud_autonomous_vm_cluster_maintenance_window_details_days_of_week_name),
},
},
HoursOfDays: pulumi.Any(_var.Cloud_autonomous_vm_cluster_maintenance_window_details_hours_of_day),
IsCustomActionTimeoutEnabled: pulumi.Any(_var.Cloud_autonomous_vm_cluster_maintenance_window_details_is_custom_action_timeout_enabled),
IsMonthlyPatchingEnabled: pulumi.Any(_var.Cloud_autonomous_vm_cluster_maintenance_window_details_is_monthly_patching_enabled),
LeadTimeInWeeks: pulumi.Any(_var.Cloud_autonomous_vm_cluster_maintenance_window_details_lead_time_in_weeks),
Months: database.CloudAutonomousVmClusterMaintenanceWindowDetailsMonthArray{
&database.CloudAutonomousVmClusterMaintenanceWindowDetailsMonthArgs{
Name: pulumi.Any(_var.Cloud_autonomous_vm_cluster_maintenance_window_details_months_name),
},
},
PatchingMode: pulumi.Any(_var.Cloud_autonomous_vm_cluster_maintenance_window_details_patching_mode),
Preference: pulumi.Any(_var.Cloud_autonomous_vm_cluster_maintenance_window_details_preference),
WeeksOfMonths: pulumi.Any(_var.Cloud_autonomous_vm_cluster_maintenance_window_details_weeks_of_month),
},
MemoryPerOracleComputeUnitInGbs: pulumi.Any(_var.Cloud_autonomous_vm_cluster_memory_per_oracle_compute_unit_in_gbs),
NsgIds: pulumi.Any(_var.Cloud_autonomous_vm_cluster_nsg_ids),
TotalContainerDatabases: pulumi.Any(_var.Cloud_autonomous_vm_cluster_total_container_databases),
})
if err != nil {
return err
}
return nil
})
}
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.Database.CloudAutonomousVmCluster;
import com.pulumi.oci.Database.CloudAutonomousVmClusterArgs;
import com.pulumi.oci.Database.inputs.CloudAutonomousVmClusterMaintenanceWindowDetailsArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var testCloudAutonomousVmCluster = new CloudAutonomousVmCluster("testCloudAutonomousVmCluster", CloudAutonomousVmClusterArgs.builder()
.cloudExadataInfrastructureId(oci_database_cloud_exadata_infrastructure.test_cloud_exadata_infrastructure().id())
.compartmentId(var_.compartment_id())
.displayName(var_.cloud_autonomous_vm_cluster_display_name())
.subnetId(oci_core_subnet.test_subnet().id())
.autonomousDataStorageSizeInTbs(var_.cloud_autonomous_vm_cluster_autonomous_data_storage_size_in_tbs())
.clusterTimeZone(var_.cloud_autonomous_vm_cluster_cluster_time_zone())
.computeModel(var_.cloud_autonomous_vm_cluster_compute_model())
.cpuCoreCountPerNode(var_.cloud_autonomous_vm_cluster_cpu_core_count_per_node())
.dbServers(var_.cloud_autonomous_vm_cluster_db_servers())
.definedTags(var_.cloud_autonomous_vm_cluster_defined_tags())
.description(var_.cloud_autonomous_vm_cluster_description())
.freeformTags(Map.of("Department", "Finance"))
.licenseModel(var_.cloud_autonomous_vm_cluster_license_model())
.maintenanceWindowDetails(CloudAutonomousVmClusterMaintenanceWindowDetailsArgs.builder()
.customActionTimeoutInMins(var_.cloud_autonomous_vm_cluster_maintenance_window_details_custom_action_timeout_in_mins())
.daysOfWeeks(CloudAutonomousVmClusterMaintenanceWindowDetailsDaysOfWeekArgs.builder()
.name(var_.cloud_autonomous_vm_cluster_maintenance_window_details_days_of_week_name())
.build())
.hoursOfDays(var_.cloud_autonomous_vm_cluster_maintenance_window_details_hours_of_day())
.isCustomActionTimeoutEnabled(var_.cloud_autonomous_vm_cluster_maintenance_window_details_is_custom_action_timeout_enabled())
.isMonthlyPatchingEnabled(var_.cloud_autonomous_vm_cluster_maintenance_window_details_is_monthly_patching_enabled())
.leadTimeInWeeks(var_.cloud_autonomous_vm_cluster_maintenance_window_details_lead_time_in_weeks())
.months(CloudAutonomousVmClusterMaintenanceWindowDetailsMonthArgs.builder()
.name(var_.cloud_autonomous_vm_cluster_maintenance_window_details_months_name())
.build())
.patchingMode(var_.cloud_autonomous_vm_cluster_maintenance_window_details_patching_mode())
.preference(var_.cloud_autonomous_vm_cluster_maintenance_window_details_preference())
.weeksOfMonths(var_.cloud_autonomous_vm_cluster_maintenance_window_details_weeks_of_month())
.build())
.memoryPerOracleComputeUnitInGbs(var_.cloud_autonomous_vm_cluster_memory_per_oracle_compute_unit_in_gbs())
.nsgIds(var_.cloud_autonomous_vm_cluster_nsg_ids())
.totalContainerDatabases(var_.cloud_autonomous_vm_cluster_total_container_databases())
.build());
}
}
import pulumi
import pulumi_oci as oci
test_cloud_autonomous_vm_cluster = oci.database.CloudAutonomousVmCluster("testCloudAutonomousVmCluster",
cloud_exadata_infrastructure_id=oci_database_cloud_exadata_infrastructure["test_cloud_exadata_infrastructure"]["id"],
compartment_id=var["compartment_id"],
display_name=var["cloud_autonomous_vm_cluster_display_name"],
subnet_id=oci_core_subnet["test_subnet"]["id"],
autonomous_data_storage_size_in_tbs=var["cloud_autonomous_vm_cluster_autonomous_data_storage_size_in_tbs"],
cluster_time_zone=var["cloud_autonomous_vm_cluster_cluster_time_zone"],
compute_model=var["cloud_autonomous_vm_cluster_compute_model"],
cpu_core_count_per_node=var["cloud_autonomous_vm_cluster_cpu_core_count_per_node"],
db_servers=var["cloud_autonomous_vm_cluster_db_servers"],
defined_tags=var["cloud_autonomous_vm_cluster_defined_tags"],
description=var["cloud_autonomous_vm_cluster_description"],
freeform_tags={
"Department": "Finance",
},
license_model=var["cloud_autonomous_vm_cluster_license_model"],
maintenance_window_details=oci.database.CloudAutonomousVmClusterMaintenanceWindowDetailsArgs(
custom_action_timeout_in_mins=var["cloud_autonomous_vm_cluster_maintenance_window_details_custom_action_timeout_in_mins"],
days_of_weeks=[oci.database.CloudAutonomousVmClusterMaintenanceWindowDetailsDaysOfWeekArgs(
name=var["cloud_autonomous_vm_cluster_maintenance_window_details_days_of_week_name"],
)],
hours_of_days=var["cloud_autonomous_vm_cluster_maintenance_window_details_hours_of_day"],
is_custom_action_timeout_enabled=var["cloud_autonomous_vm_cluster_maintenance_window_details_is_custom_action_timeout_enabled"],
is_monthly_patching_enabled=var["cloud_autonomous_vm_cluster_maintenance_window_details_is_monthly_patching_enabled"],
lead_time_in_weeks=var["cloud_autonomous_vm_cluster_maintenance_window_details_lead_time_in_weeks"],
months=[oci.database.CloudAutonomousVmClusterMaintenanceWindowDetailsMonthArgs(
name=var["cloud_autonomous_vm_cluster_maintenance_window_details_months_name"],
)],
patching_mode=var["cloud_autonomous_vm_cluster_maintenance_window_details_patching_mode"],
preference=var["cloud_autonomous_vm_cluster_maintenance_window_details_preference"],
weeks_of_months=var["cloud_autonomous_vm_cluster_maintenance_window_details_weeks_of_month"],
),
memory_per_oracle_compute_unit_in_gbs=var["cloud_autonomous_vm_cluster_memory_per_oracle_compute_unit_in_gbs"],
nsg_ids=var["cloud_autonomous_vm_cluster_nsg_ids"],
total_container_databases=var["cloud_autonomous_vm_cluster_total_container_databases"])
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testCloudAutonomousVmCluster = new oci.database.CloudAutonomousVmCluster("testCloudAutonomousVmCluster", {
cloudExadataInfrastructureId: oci_database_cloud_exadata_infrastructure.test_cloud_exadata_infrastructure.id,
compartmentId: _var.compartment_id,
displayName: _var.cloud_autonomous_vm_cluster_display_name,
subnetId: oci_core_subnet.test_subnet.id,
autonomousDataStorageSizeInTbs: _var.cloud_autonomous_vm_cluster_autonomous_data_storage_size_in_tbs,
clusterTimeZone: _var.cloud_autonomous_vm_cluster_cluster_time_zone,
computeModel: _var.cloud_autonomous_vm_cluster_compute_model,
cpuCoreCountPerNode: _var.cloud_autonomous_vm_cluster_cpu_core_count_per_node,
dbServers: _var.cloud_autonomous_vm_cluster_db_servers,
definedTags: _var.cloud_autonomous_vm_cluster_defined_tags,
description: _var.cloud_autonomous_vm_cluster_description,
freeformTags: {
Department: "Finance",
},
licenseModel: _var.cloud_autonomous_vm_cluster_license_model,
maintenanceWindowDetails: {
customActionTimeoutInMins: _var.cloud_autonomous_vm_cluster_maintenance_window_details_custom_action_timeout_in_mins,
daysOfWeeks: [{
name: _var.cloud_autonomous_vm_cluster_maintenance_window_details_days_of_week_name,
}],
hoursOfDays: _var.cloud_autonomous_vm_cluster_maintenance_window_details_hours_of_day,
isCustomActionTimeoutEnabled: _var.cloud_autonomous_vm_cluster_maintenance_window_details_is_custom_action_timeout_enabled,
isMonthlyPatchingEnabled: _var.cloud_autonomous_vm_cluster_maintenance_window_details_is_monthly_patching_enabled,
leadTimeInWeeks: _var.cloud_autonomous_vm_cluster_maintenance_window_details_lead_time_in_weeks,
months: [{
name: _var.cloud_autonomous_vm_cluster_maintenance_window_details_months_name,
}],
patchingMode: _var.cloud_autonomous_vm_cluster_maintenance_window_details_patching_mode,
preference: _var.cloud_autonomous_vm_cluster_maintenance_window_details_preference,
weeksOfMonths: _var.cloud_autonomous_vm_cluster_maintenance_window_details_weeks_of_month,
},
memoryPerOracleComputeUnitInGbs: _var.cloud_autonomous_vm_cluster_memory_per_oracle_compute_unit_in_gbs,
nsgIds: _var.cloud_autonomous_vm_cluster_nsg_ids,
totalContainerDatabases: _var.cloud_autonomous_vm_cluster_total_container_databases,
});
resources:
testCloudAutonomousVmCluster:
type: oci:Database:CloudAutonomousVmCluster
properties:
#Required
cloudExadataInfrastructureId: ${oci_database_cloud_exadata_infrastructure.test_cloud_exadata_infrastructure.id}
compartmentId: ${var.compartment_id}
displayName: ${var.cloud_autonomous_vm_cluster_display_name}
subnetId: ${oci_core_subnet.test_subnet.id}
#Optional
autonomousDataStorageSizeInTbs: ${var.cloud_autonomous_vm_cluster_autonomous_data_storage_size_in_tbs}
clusterTimeZone: ${var.cloud_autonomous_vm_cluster_cluster_time_zone}
computeModel: ${var.cloud_autonomous_vm_cluster_compute_model}
cpuCoreCountPerNode: ${var.cloud_autonomous_vm_cluster_cpu_core_count_per_node}
dbServers: ${var.cloud_autonomous_vm_cluster_db_servers}
definedTags: ${var.cloud_autonomous_vm_cluster_defined_tags}
description: ${var.cloud_autonomous_vm_cluster_description}
freeformTags:
Department: Finance
licenseModel: ${var.cloud_autonomous_vm_cluster_license_model}
maintenanceWindowDetails:
customActionTimeoutInMins: ${var.cloud_autonomous_vm_cluster_maintenance_window_details_custom_action_timeout_in_mins}
daysOfWeeks:
- name: ${var.cloud_autonomous_vm_cluster_maintenance_window_details_days_of_week_name}
hoursOfDays: ${var.cloud_autonomous_vm_cluster_maintenance_window_details_hours_of_day}
isCustomActionTimeoutEnabled: ${var.cloud_autonomous_vm_cluster_maintenance_window_details_is_custom_action_timeout_enabled}
isMonthlyPatchingEnabled: ${var.cloud_autonomous_vm_cluster_maintenance_window_details_is_monthly_patching_enabled}
leadTimeInWeeks: ${var.cloud_autonomous_vm_cluster_maintenance_window_details_lead_time_in_weeks}
months:
- name: ${var.cloud_autonomous_vm_cluster_maintenance_window_details_months_name}
patchingMode: ${var.cloud_autonomous_vm_cluster_maintenance_window_details_patching_mode}
preference: ${var.cloud_autonomous_vm_cluster_maintenance_window_details_preference}
weeksOfMonths: ${var.cloud_autonomous_vm_cluster_maintenance_window_details_weeks_of_month}
memoryPerOracleComputeUnitInGbs: ${var.cloud_autonomous_vm_cluster_memory_per_oracle_compute_unit_in_gbs}
nsgIds: ${var.cloud_autonomous_vm_cluster_nsg_ids}
totalContainerDatabases: ${var.cloud_autonomous_vm_cluster_total_container_databases}
Create CloudAutonomousVmCluster Resource
new CloudAutonomousVmCluster(name: string, args: CloudAutonomousVmClusterArgs, opts?: CustomResourceOptions);
@overload
def CloudAutonomousVmCluster(resource_name: str,
opts: Optional[ResourceOptions] = None,
autonomous_data_storage_size_in_tbs: Optional[float] = None,
cloud_exadata_infrastructure_id: Optional[str] = None,
cluster_time_zone: Optional[str] = None,
compartment_id: Optional[str] = None,
compute_model: Optional[str] = None,
cpu_core_count_per_node: Optional[int] = None,
db_servers: Optional[Sequence[str]] = None,
defined_tags: Optional[Mapping[str, Any]] = None,
description: Optional[str] = None,
display_name: Optional[str] = None,
freeform_tags: Optional[Mapping[str, Any]] = None,
license_model: Optional[str] = None,
maintenance_window_details: Optional[_database.CloudAutonomousVmClusterMaintenanceWindowDetailsArgs] = None,
memory_per_oracle_compute_unit_in_gbs: Optional[int] = None,
nsg_ids: Optional[Sequence[str]] = None,
subnet_id: Optional[str] = None,
time_updated: Optional[str] = None,
total_container_databases: Optional[int] = None)
@overload
def CloudAutonomousVmCluster(resource_name: str,
args: CloudAutonomousVmClusterArgs,
opts: Optional[ResourceOptions] = None)
func NewCloudAutonomousVmCluster(ctx *Context, name string, args CloudAutonomousVmClusterArgs, opts ...ResourceOption) (*CloudAutonomousVmCluster, error)
public CloudAutonomousVmCluster(string name, CloudAutonomousVmClusterArgs args, CustomResourceOptions? opts = null)
public CloudAutonomousVmCluster(String name, CloudAutonomousVmClusterArgs args)
public CloudAutonomousVmCluster(String name, CloudAutonomousVmClusterArgs args, CustomResourceOptions options)
type: oci:Database:CloudAutonomousVmCluster
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args CloudAutonomousVmClusterArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args CloudAutonomousVmClusterArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args CloudAutonomousVmClusterArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args CloudAutonomousVmClusterArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args CloudAutonomousVmClusterArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
CloudAutonomousVmCluster Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The CloudAutonomousVmCluster resource accepts the following input properties:
- Cloud
Exadata stringInfrastructure Id The OCID of the cloud Exadata infrastructure.
- Compartment
Id string (Updatable) The OCID of the compartment.
- Display
Name string (Updatable) The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.
- Subnet
Id string The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- Autonomous
Data doubleStorage Size In Tbs The data disk group size to be allocated for Autonomous Databases, in TBs.
- Cluster
Time stringZone The time zone to use for the Cloud Autonomous VM cluster. For details, see DB System Time Zones.
- Compute
Model string The compute model of the Cloud Autonomous VM Cluster.
- Cpu
Core intCount Per Node The number of OCPU cores to be enabled per VM cluster node.
- Db
Servers List<string> The list of database servers.
- Dictionary<string, object>
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- Description string
(Updatable) User defined description of the cloud Autonomous VM cluster.
- Dictionary<string, object>
(Updatable) 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"}
- License
Model string (Updatable) The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of
BRING_YOUR_OWN_LICENSE
.- Maintenance
Window CloudDetails Autonomous Vm Cluster Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Memory
Per intOracle Compute Unit In Gbs The amount of memory (in GBs) to be enabled per each OCPU core.
- Nsg
Ids List<string> (Updatable) The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
- Time
Updated string The last date and time that the cloud Autonomous VM cluster was updated.
- Total
Container intDatabases The total number of Autonomous Container Databases that can be created.
- Cloud
Exadata stringInfrastructure Id The OCID of the cloud Exadata infrastructure.
- Compartment
Id string (Updatable) The OCID of the compartment.
- Display
Name string (Updatable) The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.
- Subnet
Id string The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- Autonomous
Data float64Storage Size In Tbs The data disk group size to be allocated for Autonomous Databases, in TBs.
- Cluster
Time stringZone The time zone to use for the Cloud Autonomous VM cluster. For details, see DB System Time Zones.
- Compute
Model string The compute model of the Cloud Autonomous VM Cluster.
- Cpu
Core intCount Per Node The number of OCPU cores to be enabled per VM cluster node.
- Db
Servers []string The list of database servers.
- map[string]interface{}
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- Description string
(Updatable) User defined description of the cloud Autonomous VM cluster.
- map[string]interface{}
(Updatable) 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"}
- License
Model string (Updatable) The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of
BRING_YOUR_OWN_LICENSE
.- Maintenance
Window CloudDetails Autonomous Vm Cluster Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Memory
Per intOracle Compute Unit In Gbs The amount of memory (in GBs) to be enabled per each OCPU core.
- Nsg
Ids []string (Updatable) The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
- Time
Updated string The last date and time that the cloud Autonomous VM cluster was updated.
- Total
Container intDatabases The total number of Autonomous Container Databases that can be created.
- cloud
Exadata StringInfrastructure Id The OCID of the cloud Exadata infrastructure.
- compartment
Id String (Updatable) The OCID of the compartment.
- display
Name String (Updatable) The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.
- subnet
Id String The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- autonomous
Data DoubleStorage Size In Tbs The data disk group size to be allocated for Autonomous Databases, in TBs.
- cluster
Time StringZone The time zone to use for the Cloud Autonomous VM cluster. For details, see DB System Time Zones.
- compute
Model String The compute model of the Cloud Autonomous VM Cluster.
- cpu
Core IntegerCount Per Node The number of OCPU cores to be enabled per VM cluster node.
- db
Servers List<String> The list of database servers.
- Map<String,Object>
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- description String
(Updatable) User defined description of the cloud Autonomous VM cluster.
- Map<String,Object>
(Updatable) 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"}
- license
Model String (Updatable) The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of
BRING_YOUR_OWN_LICENSE
.- maintenance
Window CloudDetails Autonomous Vm Cluster Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per IntegerOracle Compute Unit In Gbs The amount of memory (in GBs) to be enabled per each OCPU core.
- nsg
Ids List<String> (Updatable) The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
- time
Updated String The last date and time that the cloud Autonomous VM cluster was updated.
- total
Container IntegerDatabases The total number of Autonomous Container Databases that can be created.
- cloud
Exadata stringInfrastructure Id The OCID of the cloud Exadata infrastructure.
- compartment
Id string (Updatable) The OCID of the compartment.
- display
Name string (Updatable) The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.
- subnet
Id string The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- autonomous
Data numberStorage Size In Tbs The data disk group size to be allocated for Autonomous Databases, in TBs.
- cluster
Time stringZone The time zone to use for the Cloud Autonomous VM cluster. For details, see DB System Time Zones.
- compute
Model string The compute model of the Cloud Autonomous VM Cluster.
- cpu
Core numberCount Per Node The number of OCPU cores to be enabled per VM cluster node.
- db
Servers string[] The list of database servers.
- {[key: string]: any}
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- description string
(Updatable) User defined description of the cloud Autonomous VM cluster.
- {[key: string]: any}
(Updatable) 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"}
- license
Model string (Updatable) The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of
BRING_YOUR_OWN_LICENSE
.- maintenance
Window CloudDetails Autonomous Vm Cluster Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per numberOracle Compute Unit In Gbs The amount of memory (in GBs) to be enabled per each OCPU core.
- nsg
Ids string[] (Updatable) The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
- time
Updated string The last date and time that the cloud Autonomous VM cluster was updated.
- total
Container numberDatabases The total number of Autonomous Container Databases that can be created.
- cloud_
exadata_ strinfrastructure_ id The OCID of the cloud Exadata infrastructure.
- compartment_
id str (Updatable) The OCID of the compartment.
- display_
name str (Updatable) The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.
- subnet_
id str The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- autonomous_
data_ floatstorage_ size_ in_ tbs The data disk group size to be allocated for Autonomous Databases, in TBs.
- cluster_
time_ strzone The time zone to use for the Cloud Autonomous VM cluster. For details, see DB System Time Zones.
- compute_
model str The compute model of the Cloud Autonomous VM Cluster.
- cpu_
core_ intcount_ per_ node The number of OCPU cores to be enabled per VM cluster node.
- db_
servers Sequence[str] The list of database servers.
- Mapping[str, Any]
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- description str
(Updatable) User defined description of the cloud Autonomous VM cluster.
- Mapping[str, Any]
(Updatable) 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"}
- license_
model str (Updatable) The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of
BRING_YOUR_OWN_LICENSE
.- maintenance_
window_ Clouddetails Autonomous Vm Cluster Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory_
per_ intoracle_ compute_ unit_ in_ gbs The amount of memory (in GBs) to be enabled per each OCPU core.
- nsg_
ids Sequence[str] (Updatable) The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
- time_
updated str The last date and time that the cloud Autonomous VM cluster was updated.
- total_
container_ intdatabases The total number of Autonomous Container Databases that can be created.
- cloud
Exadata StringInfrastructure Id The OCID of the cloud Exadata infrastructure.
- compartment
Id String (Updatable) The OCID of the compartment.
- display
Name String (Updatable) The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.
- subnet
Id String The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- autonomous
Data NumberStorage Size In Tbs The data disk group size to be allocated for Autonomous Databases, in TBs.
- cluster
Time StringZone The time zone to use for the Cloud Autonomous VM cluster. For details, see DB System Time Zones.
- compute
Model String The compute model of the Cloud Autonomous VM Cluster.
- cpu
Core NumberCount Per Node The number of OCPU cores to be enabled per VM cluster node.
- db
Servers List<String> The list of database servers.
- Map<Any>
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- description String
(Updatable) User defined description of the cloud Autonomous VM cluster.
- Map<Any>
(Updatable) 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"}
- license
Model String (Updatable) The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of
BRING_YOUR_OWN_LICENSE
.- maintenance
Window Property MapDetails (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per NumberOracle Compute Unit In Gbs The amount of memory (in GBs) to be enabled per each OCPU core.
- nsg
Ids List<String> (Updatable) The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
- time
Updated String The last date and time that the cloud Autonomous VM cluster was updated.
- total
Container NumberDatabases The total number of Autonomous Container Databases that can be created.
Outputs
All input properties are implicitly available as output properties. Additionally, the CloudAutonomousVmCluster resource produces the following output properties:
- Availability
Domain string The name of the availability domain that the cloud Autonomous VM cluster is located in.
- Available
Autonomous doubleData Storage Size In Tbs The data disk group size available for Autonomous Databases, in TBs.
- Available
Container intDatabases The number of Autonomous Container Databases that can be created with the currently available local storage.
- Available
Cpus double CPU cores available for allocation to Autonomous Databases.
- Cpu
Core intCount The number of CPU cores on the cloud Autonomous VM cluster.
- Data
Storage doubleSize In Gb The total data storage allocated, in gigabytes (GB).
- Data
Storage doubleSize In Tbs The total data storage allocated, in terabytes (TB).
- Db
Node intStorage Size In Gbs The local node storage allocated in GBs.
- Domain string
The domain name for the cloud Autonomous VM cluster.
- Hostname string
The hostname for the cloud Autonomous VM cluster.
- Id string
The provider-assigned unique ID for this managed resource.
- Last
Maintenance stringRun Id The OCID of the last maintenance run.
- Last
Update stringHistory Entry Id The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- Lifecycle
Details string Additional information about the current lifecycle state.
- Maintenance
Windows List<CloudAutonomous Vm Cluster Maintenance Window> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Memory
Size intIn Gbs The memory allocated in GBs.
- Next
Maintenance stringRun Id The OCID of the next maintenance run.
- Node
Count int The number of database servers in the cloud VM cluster.
- Ocpu
Count double The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- Reclaimable
Cpus double CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.
- Shape string
The model name of the Exadata hardware running the cloud Autonomous VM cluster.
- State string
The current state of the cloud Autonomous VM cluster.
- Time
Created string The date and time that the cloud Autonomous VM cluster was created.
- Availability
Domain string The name of the availability domain that the cloud Autonomous VM cluster is located in.
- Available
Autonomous float64Data Storage Size In Tbs The data disk group size available for Autonomous Databases, in TBs.
- Available
Container intDatabases The number of Autonomous Container Databases that can be created with the currently available local storage.
- Available
Cpus float64 CPU cores available for allocation to Autonomous Databases.
- Cpu
Core intCount The number of CPU cores on the cloud Autonomous VM cluster.
- Data
Storage float64Size In Gb The total data storage allocated, in gigabytes (GB).
- Data
Storage float64Size In Tbs The total data storage allocated, in terabytes (TB).
- Db
Node intStorage Size In Gbs The local node storage allocated in GBs.
- Domain string
The domain name for the cloud Autonomous VM cluster.
- Hostname string
The hostname for the cloud Autonomous VM cluster.
- Id string
The provider-assigned unique ID for this managed resource.
- Last
Maintenance stringRun Id The OCID of the last maintenance run.
- Last
Update stringHistory Entry Id The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- Lifecycle
Details string Additional information about the current lifecycle state.
- Maintenance
Windows []CloudAutonomous Vm Cluster Maintenance Window The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Memory
Size intIn Gbs The memory allocated in GBs.
- Next
Maintenance stringRun Id The OCID of the next maintenance run.
- Node
Count int The number of database servers in the cloud VM cluster.
- Ocpu
Count float64 The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- Reclaimable
Cpus float64 CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.
- Shape string
The model name of the Exadata hardware running the cloud Autonomous VM cluster.
- State string
The current state of the cloud Autonomous VM cluster.
- Time
Created string The date and time that the cloud Autonomous VM cluster was created.
- availability
Domain String The name of the availability domain that the cloud Autonomous VM cluster is located in.
- available
Autonomous DoubleData Storage Size In Tbs The data disk group size available for Autonomous Databases, in TBs.
- available
Container IntegerDatabases The number of Autonomous Container Databases that can be created with the currently available local storage.
- available
Cpus Double CPU cores available for allocation to Autonomous Databases.
- cpu
Core IntegerCount The number of CPU cores on the cloud Autonomous VM cluster.
- data
Storage DoubleSize In Gb The total data storage allocated, in gigabytes (GB).
- data
Storage DoubleSize In Tbs The total data storage allocated, in terabytes (TB).
- db
Node IntegerStorage Size In Gbs The local node storage allocated in GBs.
- domain String
The domain name for the cloud Autonomous VM cluster.
- hostname String
The hostname for the cloud Autonomous VM cluster.
- id String
The provider-assigned unique ID for this managed resource.
- last
Maintenance StringRun Id The OCID of the last maintenance run.
- last
Update StringHistory Entry Id The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- lifecycle
Details String Additional information about the current lifecycle state.
- maintenance
Windows List<CloudAutonomous Vm Cluster Maintenance Window> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Size IntegerIn Gbs The memory allocated in GBs.
- next
Maintenance StringRun Id The OCID of the next maintenance run.
- node
Count Integer The number of database servers in the cloud VM cluster.
- ocpu
Count Double The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- reclaimable
Cpus Double CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.
- shape String
The model name of the Exadata hardware running the cloud Autonomous VM cluster.
- state String
The current state of the cloud Autonomous VM cluster.
- time
Created String The date and time that the cloud Autonomous VM cluster was created.
- availability
Domain string The name of the availability domain that the cloud Autonomous VM cluster is located in.
- available
Autonomous numberData Storage Size In Tbs The data disk group size available for Autonomous Databases, in TBs.
- available
Container numberDatabases The number of Autonomous Container Databases that can be created with the currently available local storage.
- available
Cpus number CPU cores available for allocation to Autonomous Databases.
- cpu
Core numberCount The number of CPU cores on the cloud Autonomous VM cluster.
- data
Storage numberSize In Gb The total data storage allocated, in gigabytes (GB).
- data
Storage numberSize In Tbs The total data storage allocated, in terabytes (TB).
- db
Node numberStorage Size In Gbs The local node storage allocated in GBs.
- domain string
The domain name for the cloud Autonomous VM cluster.
- hostname string
The hostname for the cloud Autonomous VM cluster.
- id string
The provider-assigned unique ID for this managed resource.
- last
Maintenance stringRun Id The OCID of the last maintenance run.
- last
Update stringHistory Entry Id The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- lifecycle
Details string Additional information about the current lifecycle state.
- maintenance
Windows CloudAutonomous Vm Cluster Maintenance Window[] The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Size numberIn Gbs The memory allocated in GBs.
- next
Maintenance stringRun Id The OCID of the next maintenance run.
- node
Count number The number of database servers in the cloud VM cluster.
- ocpu
Count number The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- reclaimable
Cpus number CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.
- shape string
The model name of the Exadata hardware running the cloud Autonomous VM cluster.
- state string
The current state of the cloud Autonomous VM cluster.
- time
Created string The date and time that the cloud Autonomous VM cluster was created.
- availability_
domain str The name of the availability domain that the cloud Autonomous VM cluster is located in.
- available_
autonomous_ floatdata_ storage_ size_ in_ tbs The data disk group size available for Autonomous Databases, in TBs.
- available_
container_ intdatabases The number of Autonomous Container Databases that can be created with the currently available local storage.
- available_
cpus float CPU cores available for allocation to Autonomous Databases.
- cpu_
core_ intcount The number of CPU cores on the cloud Autonomous VM cluster.
- data_
storage_ floatsize_ in_ gb The total data storage allocated, in gigabytes (GB).
- data_
storage_ floatsize_ in_ tbs The total data storage allocated, in terabytes (TB).
- db_
node_ intstorage_ size_ in_ gbs The local node storage allocated in GBs.
- domain str
The domain name for the cloud Autonomous VM cluster.
- hostname str
The hostname for the cloud Autonomous VM cluster.
- id str
The provider-assigned unique ID for this managed resource.
- last_
maintenance_ strrun_ id The OCID of the last maintenance run.
- last_
update_ strhistory_ entry_ id The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- lifecycle_
details str Additional information about the current lifecycle state.
- maintenance_
windows CloudAutonomous Vm Cluster Maintenance Window] The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory_
size_ intin_ gbs The memory allocated in GBs.
- next_
maintenance_ strrun_ id The OCID of the next maintenance run.
- node_
count int The number of database servers in the cloud VM cluster.
- ocpu_
count float The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- reclaimable_
cpus float CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.
- shape str
The model name of the Exadata hardware running the cloud Autonomous VM cluster.
- state str
The current state of the cloud Autonomous VM cluster.
- time_
created str The date and time that the cloud Autonomous VM cluster was created.
- availability
Domain String The name of the availability domain that the cloud Autonomous VM cluster is located in.
- available
Autonomous NumberData Storage Size In Tbs The data disk group size available for Autonomous Databases, in TBs.
- available
Container NumberDatabases The number of Autonomous Container Databases that can be created with the currently available local storage.
- available
Cpus Number CPU cores available for allocation to Autonomous Databases.
- cpu
Core NumberCount The number of CPU cores on the cloud Autonomous VM cluster.
- data
Storage NumberSize In Gb The total data storage allocated, in gigabytes (GB).
- data
Storage NumberSize In Tbs The total data storage allocated, in terabytes (TB).
- db
Node NumberStorage Size In Gbs The local node storage allocated in GBs.
- domain String
The domain name for the cloud Autonomous VM cluster.
- hostname String
The hostname for the cloud Autonomous VM cluster.
- id String
The provider-assigned unique ID for this managed resource.
- last
Maintenance StringRun Id The OCID of the last maintenance run.
- last
Update StringHistory Entry Id The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- lifecycle
Details String Additional information about the current lifecycle state.
- maintenance
Windows List<Property Map> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Size NumberIn Gbs The memory allocated in GBs.
- next
Maintenance StringRun Id The OCID of the next maintenance run.
- node
Count Number The number of database servers in the cloud VM cluster.
- ocpu
Count Number The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- reclaimable
Cpus Number CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.
- shape String
The model name of the Exadata hardware running the cloud Autonomous VM cluster.
- state String
The current state of the cloud Autonomous VM cluster.
- time
Created String The date and time that the cloud Autonomous VM cluster was created.
Look up Existing CloudAutonomousVmCluster Resource
Get an existing CloudAutonomousVmCluster resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: CloudAutonomousVmClusterState, opts?: CustomResourceOptions): CloudAutonomousVmCluster
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
autonomous_data_storage_size_in_tbs: Optional[float] = None,
availability_domain: Optional[str] = None,
available_autonomous_data_storage_size_in_tbs: Optional[float] = None,
available_container_databases: Optional[int] = None,
available_cpus: Optional[float] = None,
cloud_exadata_infrastructure_id: Optional[str] = None,
cluster_time_zone: Optional[str] = None,
compartment_id: Optional[str] = None,
compute_model: Optional[str] = None,
cpu_core_count: Optional[int] = None,
cpu_core_count_per_node: Optional[int] = None,
data_storage_size_in_gb: Optional[float] = None,
data_storage_size_in_tbs: Optional[float] = None,
db_node_storage_size_in_gbs: Optional[int] = None,
db_servers: Optional[Sequence[str]] = None,
defined_tags: Optional[Mapping[str, Any]] = None,
description: Optional[str] = None,
display_name: Optional[str] = None,
domain: Optional[str] = None,
freeform_tags: Optional[Mapping[str, Any]] = None,
hostname: Optional[str] = None,
last_maintenance_run_id: Optional[str] = None,
last_update_history_entry_id: Optional[str] = None,
license_model: Optional[str] = None,
lifecycle_details: Optional[str] = None,
maintenance_window_details: Optional[_database.CloudAutonomousVmClusterMaintenanceWindowDetailsArgs] = None,
maintenance_windows: Optional[Sequence[_database.CloudAutonomousVmClusterMaintenanceWindowArgs]] = None,
memory_per_oracle_compute_unit_in_gbs: Optional[int] = None,
memory_size_in_gbs: Optional[int] = None,
next_maintenance_run_id: Optional[str] = None,
node_count: Optional[int] = None,
nsg_ids: Optional[Sequence[str]] = None,
ocpu_count: Optional[float] = None,
reclaimable_cpus: Optional[float] = None,
shape: Optional[str] = None,
state: Optional[str] = None,
subnet_id: Optional[str] = None,
time_created: Optional[str] = None,
time_updated: Optional[str] = None,
total_container_databases: Optional[int] = None) -> CloudAutonomousVmCluster
func GetCloudAutonomousVmCluster(ctx *Context, name string, id IDInput, state *CloudAutonomousVmClusterState, opts ...ResourceOption) (*CloudAutonomousVmCluster, error)
public static CloudAutonomousVmCluster Get(string name, Input<string> id, CloudAutonomousVmClusterState? state, CustomResourceOptions? opts = null)
public static CloudAutonomousVmCluster get(String name, Output<String> id, CloudAutonomousVmClusterState state, CustomResourceOptions options)
Resource lookup is not supported in YAML
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Autonomous
Data doubleStorage Size In Tbs The data disk group size to be allocated for Autonomous Databases, in TBs.
- Availability
Domain string The name of the availability domain that the cloud Autonomous VM cluster is located in.
- Available
Autonomous doubleData Storage Size In Tbs The data disk group size available for Autonomous Databases, in TBs.
- Available
Container intDatabases The number of Autonomous Container Databases that can be created with the currently available local storage.
- Available
Cpus double CPU cores available for allocation to Autonomous Databases.
- Cloud
Exadata stringInfrastructure Id The OCID of the cloud Exadata infrastructure.
- Cluster
Time stringZone The time zone to use for the Cloud Autonomous VM cluster. For details, see DB System Time Zones.
- Compartment
Id string (Updatable) The OCID of the compartment.
- Compute
Model string The compute model of the Cloud Autonomous VM Cluster.
- Cpu
Core intCount The number of CPU cores on the cloud Autonomous VM cluster.
- Cpu
Core intCount Per Node The number of OCPU cores to be enabled per VM cluster node.
- Data
Storage doubleSize In Gb The total data storage allocated, in gigabytes (GB).
- Data
Storage doubleSize In Tbs The total data storage allocated, in terabytes (TB).
- Db
Node intStorage Size In Gbs The local node storage allocated in GBs.
- Db
Servers List<string> The list of database servers.
- Dictionary<string, object>
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- Description string
(Updatable) User defined description of the cloud Autonomous VM cluster.
- Display
Name string (Updatable) The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.
- Domain string
The domain name for the cloud Autonomous VM cluster.
- Dictionary<string, object>
(Updatable) 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"}
- Hostname string
The hostname for the cloud Autonomous VM cluster.
- Last
Maintenance stringRun Id The OCID of the last maintenance run.
- Last
Update stringHistory Entry Id The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- License
Model string (Updatable) The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of
BRING_YOUR_OWN_LICENSE
.- Lifecycle
Details string Additional information about the current lifecycle state.
- Maintenance
Window CloudDetails Autonomous Vm Cluster Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Maintenance
Windows List<CloudAutonomous Vm Cluster Maintenance Window Args> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Memory
Per intOracle Compute Unit In Gbs The amount of memory (in GBs) to be enabled per each OCPU core.
- Memory
Size intIn Gbs The memory allocated in GBs.
- Next
Maintenance stringRun Id The OCID of the next maintenance run.
- Node
Count int The number of database servers in the cloud VM cluster.
- Nsg
Ids List<string> (Updatable) The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
- Ocpu
Count double The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- Reclaimable
Cpus double CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.
- Shape string
The model name of the Exadata hardware running the cloud Autonomous VM cluster.
- State string
The current state of the cloud Autonomous VM cluster.
- Subnet
Id string The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- Time
Created string The date and time that the cloud Autonomous VM cluster was created.
- Time
Updated string The last date and time that the cloud Autonomous VM cluster was updated.
- Total
Container intDatabases The total number of Autonomous Container Databases that can be created.
- Autonomous
Data float64Storage Size In Tbs The data disk group size to be allocated for Autonomous Databases, in TBs.
- Availability
Domain string The name of the availability domain that the cloud Autonomous VM cluster is located in.
- Available
Autonomous float64Data Storage Size In Tbs The data disk group size available for Autonomous Databases, in TBs.
- Available
Container intDatabases The number of Autonomous Container Databases that can be created with the currently available local storage.
- Available
Cpus float64 CPU cores available for allocation to Autonomous Databases.
- Cloud
Exadata stringInfrastructure Id The OCID of the cloud Exadata infrastructure.
- Cluster
Time stringZone The time zone to use for the Cloud Autonomous VM cluster. For details, see DB System Time Zones.
- Compartment
Id string (Updatable) The OCID of the compartment.
- Compute
Model string The compute model of the Cloud Autonomous VM Cluster.
- Cpu
Core intCount The number of CPU cores on the cloud Autonomous VM cluster.
- Cpu
Core intCount Per Node The number of OCPU cores to be enabled per VM cluster node.
- Data
Storage float64Size In Gb The total data storage allocated, in gigabytes (GB).
- Data
Storage float64Size In Tbs The total data storage allocated, in terabytes (TB).
- Db
Node intStorage Size In Gbs The local node storage allocated in GBs.
- Db
Servers []string The list of database servers.
- map[string]interface{}
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- Description string
(Updatable) User defined description of the cloud Autonomous VM cluster.
- Display
Name string (Updatable) The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.
- Domain string
The domain name for the cloud Autonomous VM cluster.
- map[string]interface{}
(Updatable) 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"}
- Hostname string
The hostname for the cloud Autonomous VM cluster.
- Last
Maintenance stringRun Id The OCID of the last maintenance run.
- Last
Update stringHistory Entry Id The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- License
Model string (Updatable) The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of
BRING_YOUR_OWN_LICENSE
.- Lifecycle
Details string Additional information about the current lifecycle state.
- Maintenance
Window CloudDetails Autonomous Vm Cluster Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Maintenance
Windows []CloudAutonomous Vm Cluster Maintenance Window Args The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- Memory
Per intOracle Compute Unit In Gbs The amount of memory (in GBs) to be enabled per each OCPU core.
- Memory
Size intIn Gbs The memory allocated in GBs.
- Next
Maintenance stringRun Id The OCID of the next maintenance run.
- Node
Count int The number of database servers in the cloud VM cluster.
- Nsg
Ids []string (Updatable) The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
- Ocpu
Count float64 The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- Reclaimable
Cpus float64 CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.
- Shape string
The model name of the Exadata hardware running the cloud Autonomous VM cluster.
- State string
The current state of the cloud Autonomous VM cluster.
- Subnet
Id string The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- Time
Created string The date and time that the cloud Autonomous VM cluster was created.
- Time
Updated string The last date and time that the cloud Autonomous VM cluster was updated.
- Total
Container intDatabases The total number of Autonomous Container Databases that can be created.
- autonomous
Data DoubleStorage Size In Tbs The data disk group size to be allocated for Autonomous Databases, in TBs.
- availability
Domain String The name of the availability domain that the cloud Autonomous VM cluster is located in.
- available
Autonomous DoubleData Storage Size In Tbs The data disk group size available for Autonomous Databases, in TBs.
- available
Container IntegerDatabases The number of Autonomous Container Databases that can be created with the currently available local storage.
- available
Cpus Double CPU cores available for allocation to Autonomous Databases.
- cloud
Exadata StringInfrastructure Id The OCID of the cloud Exadata infrastructure.
- cluster
Time StringZone The time zone to use for the Cloud Autonomous VM cluster. For details, see DB System Time Zones.
- compartment
Id String (Updatable) The OCID of the compartment.
- compute
Model String The compute model of the Cloud Autonomous VM Cluster.
- cpu
Core IntegerCount The number of CPU cores on the cloud Autonomous VM cluster.
- cpu
Core IntegerCount Per Node The number of OCPU cores to be enabled per VM cluster node.
- data
Storage DoubleSize In Gb The total data storage allocated, in gigabytes (GB).
- data
Storage DoubleSize In Tbs The total data storage allocated, in terabytes (TB).
- db
Node IntegerStorage Size In Gbs The local node storage allocated in GBs.
- db
Servers List<String> The list of database servers.
- Map<String,Object>
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- description String
(Updatable) User defined description of the cloud Autonomous VM cluster.
- display
Name String (Updatable) The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.
- domain String
The domain name for the cloud Autonomous VM cluster.
- Map<String,Object>
(Updatable) 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"}
- hostname String
The hostname for the cloud Autonomous VM cluster.
- last
Maintenance StringRun Id The OCID of the last maintenance run.
- last
Update StringHistory Entry Id The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- license
Model String (Updatable) The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of
BRING_YOUR_OWN_LICENSE
.- lifecycle
Details String Additional information about the current lifecycle state.
- maintenance
Window CloudDetails Autonomous Vm Cluster Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maintenance
Windows List<CloudAutonomous Vm Cluster Maintenance Window Args> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per IntegerOracle Compute Unit In Gbs The amount of memory (in GBs) to be enabled per each OCPU core.
- memory
Size IntegerIn Gbs The memory allocated in GBs.
- next
Maintenance StringRun Id The OCID of the next maintenance run.
- node
Count Integer The number of database servers in the cloud VM cluster.
- nsg
Ids List<String> (Updatable) The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
- ocpu
Count Double The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- reclaimable
Cpus Double CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.
- shape String
The model name of the Exadata hardware running the cloud Autonomous VM cluster.
- state String
The current state of the cloud Autonomous VM cluster.
- subnet
Id String The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- time
Created String The date and time that the cloud Autonomous VM cluster was created.
- time
Updated String The last date and time that the cloud Autonomous VM cluster was updated.
- total
Container IntegerDatabases The total number of Autonomous Container Databases that can be created.
- autonomous
Data numberStorage Size In Tbs The data disk group size to be allocated for Autonomous Databases, in TBs.
- availability
Domain string The name of the availability domain that the cloud Autonomous VM cluster is located in.
- available
Autonomous numberData Storage Size In Tbs The data disk group size available for Autonomous Databases, in TBs.
- available
Container numberDatabases The number of Autonomous Container Databases that can be created with the currently available local storage.
- available
Cpus number CPU cores available for allocation to Autonomous Databases.
- cloud
Exadata stringInfrastructure Id The OCID of the cloud Exadata infrastructure.
- cluster
Time stringZone The time zone to use for the Cloud Autonomous VM cluster. For details, see DB System Time Zones.
- compartment
Id string (Updatable) The OCID of the compartment.
- compute
Model string The compute model of the Cloud Autonomous VM Cluster.
- cpu
Core numberCount The number of CPU cores on the cloud Autonomous VM cluster.
- cpu
Core numberCount Per Node The number of OCPU cores to be enabled per VM cluster node.
- data
Storage numberSize In Gb The total data storage allocated, in gigabytes (GB).
- data
Storage numberSize In Tbs The total data storage allocated, in terabytes (TB).
- db
Node numberStorage Size In Gbs The local node storage allocated in GBs.
- db
Servers string[] The list of database servers.
- {[key: string]: any}
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- description string
(Updatable) User defined description of the cloud Autonomous VM cluster.
- display
Name string (Updatable) The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.
- domain string
The domain name for the cloud Autonomous VM cluster.
- {[key: string]: any}
(Updatable) 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"}
- hostname string
The hostname for the cloud Autonomous VM cluster.
- last
Maintenance stringRun Id The OCID of the last maintenance run.
- last
Update stringHistory Entry Id The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- license
Model string (Updatable) The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of
BRING_YOUR_OWN_LICENSE
.- lifecycle
Details string Additional information about the current lifecycle state.
- maintenance
Window CloudDetails Autonomous Vm Cluster Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maintenance
Windows CloudAutonomous Vm Cluster Maintenance Window Args[] The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per numberOracle Compute Unit In Gbs The amount of memory (in GBs) to be enabled per each OCPU core.
- memory
Size numberIn Gbs The memory allocated in GBs.
- next
Maintenance stringRun Id The OCID of the next maintenance run.
- node
Count number The number of database servers in the cloud VM cluster.
- nsg
Ids string[] (Updatable) The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
- ocpu
Count number The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- reclaimable
Cpus number CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.
- shape string
The model name of the Exadata hardware running the cloud Autonomous VM cluster.
- state string
The current state of the cloud Autonomous VM cluster.
- subnet
Id string The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- time
Created string The date and time that the cloud Autonomous VM cluster was created.
- time
Updated string The last date and time that the cloud Autonomous VM cluster was updated.
- total
Container numberDatabases The total number of Autonomous Container Databases that can be created.
- autonomous_
data_ floatstorage_ size_ in_ tbs The data disk group size to be allocated for Autonomous Databases, in TBs.
- availability_
domain str The name of the availability domain that the cloud Autonomous VM cluster is located in.
- available_
autonomous_ floatdata_ storage_ size_ in_ tbs The data disk group size available for Autonomous Databases, in TBs.
- available_
container_ intdatabases The number of Autonomous Container Databases that can be created with the currently available local storage.
- available_
cpus float CPU cores available for allocation to Autonomous Databases.
- cloud_
exadata_ strinfrastructure_ id The OCID of the cloud Exadata infrastructure.
- cluster_
time_ strzone The time zone to use for the Cloud Autonomous VM cluster. For details, see DB System Time Zones.
- compartment_
id str (Updatable) The OCID of the compartment.
- compute_
model str The compute model of the Cloud Autonomous VM Cluster.
- cpu_
core_ intcount The number of CPU cores on the cloud Autonomous VM cluster.
- cpu_
core_ intcount_ per_ node The number of OCPU cores to be enabled per VM cluster node.
- data_
storage_ floatsize_ in_ gb The total data storage allocated, in gigabytes (GB).
- data_
storage_ floatsize_ in_ tbs The total data storage allocated, in terabytes (TB).
- db_
node_ intstorage_ size_ in_ gbs The local node storage allocated in GBs.
- db_
servers Sequence[str] The list of database servers.
- Mapping[str, Any]
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- description str
(Updatable) User defined description of the cloud Autonomous VM cluster.
- display_
name str (Updatable) The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.
- domain str
The domain name for the cloud Autonomous VM cluster.
- Mapping[str, Any]
(Updatable) 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"}
- hostname str
The hostname for the cloud Autonomous VM cluster.
- last_
maintenance_ strrun_ id The OCID of the last maintenance run.
- last_
update_ strhistory_ entry_ id The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- license_
model str (Updatable) The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of
BRING_YOUR_OWN_LICENSE
.- lifecycle_
details str Additional information about the current lifecycle state.
- maintenance_
window_ Clouddetails Autonomous Vm Cluster Maintenance Window Details Args (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maintenance_
windows CloudAutonomous Vm Cluster Maintenance Window Args] The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory_
per_ intoracle_ compute_ unit_ in_ gbs The amount of memory (in GBs) to be enabled per each OCPU core.
- memory_
size_ intin_ gbs The memory allocated in GBs.
- next_
maintenance_ strrun_ id The OCID of the next maintenance run.
- node_
count int The number of database servers in the cloud VM cluster.
- nsg_
ids Sequence[str] (Updatable) The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
- ocpu_
count float The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- reclaimable_
cpus float CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.
- shape str
The model name of the Exadata hardware running the cloud Autonomous VM cluster.
- state str
The current state of the cloud Autonomous VM cluster.
- subnet_
id str The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- time_
created str The date and time that the cloud Autonomous VM cluster was created.
- time_
updated str The last date and time that the cloud Autonomous VM cluster was updated.
- total_
container_ intdatabases The total number of Autonomous Container Databases that can be created.
- autonomous
Data NumberStorage Size In Tbs The data disk group size to be allocated for Autonomous Databases, in TBs.
- availability
Domain String The name of the availability domain that the cloud Autonomous VM cluster is located in.
- available
Autonomous NumberData Storage Size In Tbs The data disk group size available for Autonomous Databases, in TBs.
- available
Container NumberDatabases The number of Autonomous Container Databases that can be created with the currently available local storage.
- available
Cpus Number CPU cores available for allocation to Autonomous Databases.
- cloud
Exadata StringInfrastructure Id The OCID of the cloud Exadata infrastructure.
- cluster
Time StringZone The time zone to use for the Cloud Autonomous VM cluster. For details, see DB System Time Zones.
- compartment
Id String (Updatable) The OCID of the compartment.
- compute
Model String The compute model of the Cloud Autonomous VM Cluster.
- cpu
Core NumberCount The number of CPU cores on the cloud Autonomous VM cluster.
- cpu
Core NumberCount Per Node The number of OCPU cores to be enabled per VM cluster node.
- data
Storage NumberSize In Gb The total data storage allocated, in gigabytes (GB).
- data
Storage NumberSize In Tbs The total data storage allocated, in terabytes (TB).
- db
Node NumberStorage Size In Gbs The local node storage allocated in GBs.
- db
Servers List<String> The list of database servers.
- Map<Any>
(Updatable) Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
- description String
(Updatable) User defined description of the cloud Autonomous VM cluster.
- display
Name String (Updatable) The user-friendly name for the cloud Autonomous VM cluster. The name does not need to be unique.
- domain String
The domain name for the cloud Autonomous VM cluster.
- Map<Any>
(Updatable) 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"}
- hostname String
The hostname for the cloud Autonomous VM cluster.
- last
Maintenance StringRun Id The OCID of the last maintenance run.
- last
Update StringHistory Entry Id The OCID of the last maintenance update history. This value is updated when a maintenance update starts.
- license
Model String (Updatable) The Oracle license model that applies to the Oracle Autonomous Database. Bring your own license (BYOL) allows you to apply your current on-premises Oracle software licenses to equivalent, highly automated Oracle PaaS and IaaS services in the cloud. License Included allows you to subscribe to new Oracle Database software licenses and the Database service. Note that when provisioning an Autonomous Database on dedicated Exadata infrastructure, this attribute must be null because the attribute is already set at the Autonomous Exadata Infrastructure level. When using shared Exadata infrastructure, if a value is not specified, the system will supply the value of
BRING_YOUR_OWN_LICENSE
.- lifecycle
Details String Additional information about the current lifecycle state.
- maintenance
Window Property MapDetails (Updatable) The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- maintenance
Windows List<Property Map> The scheduling details for the quarterly maintenance window. Patching and system updates take place during the maintenance window.
- memory
Per NumberOracle Compute Unit In Gbs The amount of memory (in GBs) to be enabled per each OCPU core.
- memory
Size NumberIn Gbs The memory allocated in GBs.
- next
Maintenance StringRun Id The OCID of the next maintenance run.
- node
Count Number The number of database servers in the cloud VM cluster.
- nsg
Ids List<String> (Updatable) The list of OCIDs for the network security groups (NSGs) to which this resource belongs. Setting this to an empty list removes all resources from all NSGs. For more information about NSGs, see Security Rules. NsgIds restrictions:
- A network security group (NSG) is optional for Autonomous Databases with private access. The nsgIds list can be empty.
- ocpu
Count Number The number of CPU cores on the cloud Autonomous VM cluster. Only 1 decimal place is allowed for the fractional part.
- reclaimable
Cpus Number CPU cores that continue to be included in the count of OCPUs available to the Autonomous Container Database even after one of its Autonomous Database is terminated or scaled down. You can release them to the available OCPUs at its parent AVMC level by restarting the Autonomous Container Database.
- shape String
The model name of the Exadata hardware running the cloud Autonomous VM cluster.
- state String
The current state of the cloud Autonomous VM cluster.
- subnet
Id String The OCID of the subnet the cloud Autonomous VM Cluster is associated with.
- time
Created String The date and time that the cloud Autonomous VM cluster was created.
- time
Updated String The last date and time that the cloud Autonomous VM cluster was updated.
- total
Container NumberDatabases The total number of Autonomous Container Databases that can be created.
Supporting Types
CloudAutonomousVmClusterMaintenanceWindow
- Custom
Action intTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- Days
Of List<CloudWeeks Autonomous Vm Cluster Maintenance Window Days Of Week> (Updatable) Days during the week when maintenance should be performed.
- Hours
Of List<int>Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- Is
Custom boolAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- Is
Monthly boolPatching Enabled (Updatable) If true, enables the monthly patching option.
- Lead
Time intIn Weeks (Updatable) Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
List<Cloud
Autonomous Vm Cluster Maintenance Window Month> (Updatable) Months during the year when maintenance should be performed.
- Patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
(Updatable) The maintenance window scheduling preference.
- Weeks
Of List<int>Months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- Custom
Action intTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- Days
Of []CloudWeeks Autonomous Vm Cluster Maintenance Window Days Of Week (Updatable) Days during the week when maintenance should be performed.
- Hours
Of []intDays (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- Is
Custom boolAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- Is
Monthly boolPatching Enabled (Updatable) If true, enables the monthly patching option.
- Lead
Time intIn Weeks (Updatable) Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
[]Cloud
Autonomous Vm Cluster Maintenance Window Month (Updatable) Months during the year when maintenance should be performed.
- Patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Preference string
(Updatable) The maintenance window scheduling preference.
- Weeks
Of []intMonths (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action IntegerTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of List<CloudWeeks Autonomous Vm Cluster Maintenance Window Days Of Week> (Updatable) Days during the week when maintenance should be performed.
- hours
Of List<Integer>Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom BooleanAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled (Updatable) If true, enables the monthly patching option.
- lead
Time IntegerIn Weeks (Updatable) Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
List<Cloud
Autonomous Vm Cluster Maintenance Window Month> (Updatable) Months during the year when maintenance should be performed.
- patching
Mode String (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
(Updatable) The maintenance window scheduling preference.
- weeks
Of List<Integer>Months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action numberTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of CloudWeeks Autonomous Vm Cluster Maintenance Window Days Of Week[] (Updatable) Days during the week when maintenance should be performed.
- hours
Of number[]Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom booleanAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly booleanPatching Enabled (Updatable) If true, enables the monthly patching option.
- lead
Time numberIn Weeks (Updatable) Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
Cloud
Autonomous Vm Cluster Maintenance Window Month[] (Updatable) Months during the year when maintenance should be performed.
- patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference string
(Updatable) The maintenance window scheduling preference.
- weeks
Of number[]Months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom_
action_ inttimeout_ in_ mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days_
of_ Cloudweeks Autonomous Vm Cluster Maintenance Window Days Of Week] (Updatable) Days during the week when maintenance should be performed.
- hours_
of_ Sequence[int]days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is_
custom_ boolaction_ timeout_ enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is_
monthly_ boolpatching_ enabled (Updatable) If true, enables the monthly patching option.
- lead_
time_ intin_ weeks (Updatable) Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
Cloud
Autonomous Vm Cluster Maintenance Window Month] (Updatable) Months during the year when maintenance should be performed.
- patching_
mode str (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference str
(Updatable) The maintenance window scheduling preference.
- weeks_
of_ Sequence[int]months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- custom
Action NumberTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of List<Property Map>Weeks (Updatable) Days during the week when maintenance should be performed.
- hours
Of List<Number>Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom BooleanAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled (Updatable) If true, enables the monthly patching option.
- lead
Time NumberIn Weeks (Updatable) Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months List<Property Map>
(Updatable) Months during the year when maintenance should be performed.
- patching
Mode String (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- preference String
(Updatable) The maintenance window scheduling preference.
- weeks
Of List<Number>Months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
CloudAutonomousVmClusterMaintenanceWindowDaysOfWeek
- Name string
(Updatable) Name of the month of the year.
- Name string
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
- name string
(Updatable) Name of the month of the year.
- name str
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
CloudAutonomousVmClusterMaintenanceWindowDetails
- Preference string
(Updatable) The maintenance window scheduling preference.
- Custom
Action intTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- Days
Of List<CloudWeeks Autonomous Vm Cluster Maintenance Window Details Days Of Week> (Updatable) Days during the week when maintenance should be performed.
- Hours
Of List<int>Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- Is
Custom boolAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- Is
Monthly boolPatching Enabled (Updatable) If true, enables the monthly patching option.
- Lead
Time intIn Weeks (Updatable) Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
List<Cloud
Autonomous Vm Cluster Maintenance Window Details Month> (Updatable) Months during the year when maintenance should be performed.
- Patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Weeks
Of List<int>Months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- Preference string
(Updatable) The maintenance window scheduling preference.
- Custom
Action intTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- Days
Of []CloudWeeks Autonomous Vm Cluster Maintenance Window Details Days Of Week (Updatable) Days during the week when maintenance should be performed.
- Hours
Of []intDays (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- Is
Custom boolAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- Is
Monthly boolPatching Enabled (Updatable) If true, enables the monthly patching option.
- Lead
Time intIn Weeks (Updatable) Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- Months
[]Cloud
Autonomous Vm Cluster Maintenance Window Details Month (Updatable) Months during the year when maintenance should be performed.
- Patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- Weeks
Of []intMonths (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- preference String
(Updatable) The maintenance window scheduling preference.
- custom
Action IntegerTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of List<CloudWeeks Autonomous Vm Cluster Maintenance Window Details Days Of Week> (Updatable) Days during the week when maintenance should be performed.
- hours
Of List<Integer>Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom BooleanAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled (Updatable) If true, enables the monthly patching option.
- lead
Time IntegerIn Weeks (Updatable) Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
List<Cloud
Autonomous Vm Cluster Maintenance Window Details Month> (Updatable) Months during the year when maintenance should be performed.
- patching
Mode String (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- weeks
Of List<Integer>Months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- preference string
(Updatable) The maintenance window scheduling preference.
- custom
Action numberTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of CloudWeeks Autonomous Vm Cluster Maintenance Window Details Days Of Week[] (Updatable) Days during the week when maintenance should be performed.
- hours
Of number[]Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom booleanAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly booleanPatching Enabled (Updatable) If true, enables the monthly patching option.
- lead
Time numberIn Weeks (Updatable) Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
Cloud
Autonomous Vm Cluster Maintenance Window Details Month[] (Updatable) Months during the year when maintenance should be performed.
- patching
Mode string (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- weeks
Of number[]Months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- preference str
(Updatable) The maintenance window scheduling preference.
- custom_
action_ inttimeout_ in_ mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days_
of_ Cloudweeks Autonomous Vm Cluster Maintenance Window Details Days Of Week] (Updatable) Days during the week when maintenance should be performed.
- hours_
of_ Sequence[int]days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is_
custom_ boolaction_ timeout_ enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is_
monthly_ boolpatching_ enabled (Updatable) If true, enables the monthly patching option.
- lead_
time_ intin_ weeks (Updatable) Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months
Cloud
Autonomous Vm Cluster Maintenance Window Details Month] (Updatable) Months during the year when maintenance should be performed.
- patching_
mode str (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- weeks_
of_ Sequence[int]months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
- preference String
(Updatable) The maintenance window scheduling preference.
- custom
Action NumberTimeout In Mins (Updatable) Determines the amount of time the system will wait before the start of each database server patching operation. Custom action timeout is in minutes and valid value is between 15 to 120 (inclusive).
- days
Of List<Property Map>Weeks (Updatable) Days during the week when maintenance should be performed.
- hours
Of List<Number>Days (Updatable) The window of hours during the day when maintenance should be performed. The window is a 4 hour slot. Valid values are
- 0 - represents time slot 0:00 - 3:59 UTC - 4 - represents time slot 4:00 - 7:59 UTC - 8 - represents time slot 8:00 - 11:59 UTC - 12 - represents time slot 12:00 - 15:59 UTC - 16 - represents time slot 16:00 - 19:59 UTC - 20 - represents time slot 20:00 - 23:59 UTC
- is
Custom BooleanAction Timeout Enabled (Updatable) If true, enables the configuration of a custom action timeout (waiting period) between database server patching operations.
- is
Monthly BooleanPatching Enabled (Updatable) If true, enables the monthly patching option.
- lead
Time NumberIn Weeks (Updatable) Lead time window allows user to set a lead time to prepare for a down time. The lead time is in weeks and valid value is between 1 to 4.
- months List<Property Map>
(Updatable) Months during the year when maintenance should be performed.
- patching
Mode String (Updatable) Cloud Exadata infrastructure node patching method, either "ROLLING" or "NONROLLING". Default value is ROLLING.
- weeks
Of List<Number>Months (Updatable) Weeks during the month when maintenance should be performed. Weeks start on the 1st, 8th, 15th, and 22nd days of the month, and have a duration of 7 days. Weeks start and end based on calendar dates, not days of the week. For example, to allow maintenance during the 2nd week of the month (from the 8th day to the 14th day of the month), use the value 2. Maintenance cannot be scheduled for the fifth week of months that contain more than 28 days. Note that this parameter works in conjunction with the daysOfWeek and hoursOfDay parameters to allow you to specify specific days of the week and hours that maintenance will be performed.
CloudAutonomousVmClusterMaintenanceWindowDetailsDaysOfWeek
- Name string
(Updatable) Name of the month of the year.
- Name string
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
- name string
(Updatable) Name of the month of the year.
- name str
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
CloudAutonomousVmClusterMaintenanceWindowDetailsMonth
- Name string
(Updatable) Name of the month of the year.
- Name string
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
- name string
(Updatable) Name of the month of the year.
- name str
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
CloudAutonomousVmClusterMaintenanceWindowMonth
- Name string
(Updatable) Name of the month of the year.
- Name string
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
- name string
(Updatable) Name of the month of the year.
- name str
(Updatable) Name of the month of the year.
- name String
(Updatable) Name of the month of the year.
Import
CloudAutonomousVmClusters can be imported using the id
, e.g.
$ pulumi import oci:Database/cloudAutonomousVmCluster:CloudAutonomousVmCluster test_cloud_autonomous_vm_cluster "id"
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
This Pulumi package is based on the
oci
Terraform Provider.