OCI Autoscaling
Metric-based or scheduled rules that resize an instance pool.
- Provider
- oci
- Kind
- Virtual machine
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| coolDownSeconds | integer | — | no | 300 | inherited |
| diskEncryption | boolean | — | no | — | inherited |
| evaluationPeriods | integer | — | no | 3 | inherited |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| memoryGib | integer | — | no | — | inherited |
| metric | enum | cpu-utilization | memory-utilization | no | — | inherited |
| os | enum | linux | windows | aix | ibm-i | no | linux | inherited |
| policyType | enum | metric-based | schedule-based | no | — | inherited |
| publicIp | boolean | — | no | — | inherited |
| sizeVcpu | integer | — | no | — | inherited |
| zoneRedundant | boolean | — | no | — | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
stateful-node-without-zone-redundancy
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "compute-autoscaling", component: "oci-compute-autoscaling" }Auto Scalingalibaba-auto-scalingElastic Compute Servicealibaba-ecsEdge Node Servicealibaba-ensSimple Application Serveralibaba-simple-application-serverAmazon EC2aws-ec2Amazon EC2 Auto Scalingaws-ec2-auto-scalingAmazon EC2 Dedicated Hostsaws-ec2-dedicated-hostAmazon Elastic VMware Serviceaws-evsAmazon Lightsailaws-lightsailAWS Nitro Enclavesaws-nitro-enclaveAzure BareMetal Infrastructureazure-baremetal-infrastructureAzure Compute Fleetazure-compute-fleetAzure Dedicated Hostazure-dedicated-hostAzure Data Science Virtual Machineazure-dsvmNutanix Cloud Clusters on Azureazure-nutanix-cloud-clustersAzure Virtual Machinesazure-virtual-machineAzure Virtual Machine Scale Setsazure-vm-scale-setAzure VMware Solutionazure-vmware-solutionCrusoe Cloud VMcrusoeFirecrackerfirecrackerMicrosoft Hyper-Vhyper-vKubeVirtkubevirtLambda Cloud instancelambda-labsKVM with libvirtlibvirtNebius AI Cloud VMnebiusNutanix AHVnutanix-ahvOpenStack Novaopenstack-novaoVirtovirtProxmox VEproxmoxRunpod PodrunpodVast.ai instancevast-aiGeneric virtual machinevirtual-machineVMware vSpherevsphereXCP-ngxcp-ngXenServerxenserverDigitalOcean Bare Metal GPUsdigitalocean-bare-metal-gpuDropletsdigitalocean-dropletDroplet Autoscale Pooldigitalocean-droplet-autoscaleBare Metal Solutiongoogle-bare-metal-solutionCloud TPUgoogle-cloud-tpu
and 20 more → Virtual machine page# yaml-language-server: $schema=../../schema/component.schema.json # OCI autoscaling configuration for an instance pool: metric-based or schedule-based rules that # resize the pool ("Autoscaling"). That page evaluates Monitoring metrics aggregated into # one-minute periods and needs three consecutive periods over the threshold to act; the cooldown # between scaling actions is 300 seconds, which is both the default and the minimum. schemaVersion: "1" type: "component" id: "oci-compute-autoscaling" kind: "virtual-machine" provider: "oci" docs: "https://docs.oracle.com/en-us/iaas/Content/Compute/Tasks/autoscalinginstancepools.htm" defaults: managed: true properties: policyType: type: "enum" values: ["metric-based", "schedule-based"] metric: type: "enum" values: ["cpu-utilization", "memory-utilization"] coolDownSeconds: type: "integer" default: 300 evaluationPeriods: type: "integer" default: 3