oraclecloud-core-workflow-a

# OCI Compute — Launch, Manage & Scale ## Overview Provision and manage OCI compute instances using the Python SDK. Compute is the entry point for most OCI workloads, but "out of host capacity" errors, shape selection confusion (Flex vs Standard, AMD vs ARM vs Intel), and boot volume management make it harder than AWS EC2. This skill covers shape selection, launch with capacity retry across availability domains, instance lifecycle actions, and boot volume management. **Purpose:** Launch reliable compute instances with retry logic that survives capacity shortages. ## Prerequisites - **OCI Python SDK** — `pip install oci` - **Config file** at `~/.oci/config` with fields: `user`, `fingerprint`, `tenancy`, `region`, `key_file` - **IAM policy** — `Allow group Developers to manage instances in compartment <name>` - **Python 3.8+** - A VCN with at least one subnet (see `oraclecloud-core-workflow-b`) ## Instructions ### Step 1: Understand Shape Options | Shape | Arch | Flex? | OCPUs | Use Case | |-------|------|-------|-------|----------| | VM.Standard.A1.Flex | ARM (Ampere) | Yes | 1-80 | Always Free eligible, best price/perf | | VM.Standard.E5.Flex | AMD | Yes | 1-94 | General purpose, broadest availability | | VM.Standard3.Flex | Intel | Yes | 1-32 | Intel-specific workloads | | VM.Standard.E4.Flex | AMD | Yes | 1-64 | Previous gen, still available | **Key rule:** Always use Flex shapes. They let you set exact OCPU and memory. Standard (non-Flex) shapes have fixed sizes a...