Oracle Could Infrastructure Compute is a web service that provides bare metal and virtual machine (VM) compute capacity that delivers performance, flexibility, and control without compromise. It's powered by Oracle’s next generation internet-scale infrastructure service and is designed to help modern enterprises do more while paying less when developing and running their most demanding applications and workloads in the cloud.
Compute enables you to provision compute capacity in minutes through an easy-to-use web console. The bare metal compute instance, once provisioned, provides you access to the host. This gives you the flexibility, control, and performance without compromise needed for your most demanding applications and workloads, all while paying only for what you use.
Oracle Cloud Infrastructure is hosted in regions, each of which contain at least three availability domains. A region is simply a geographic area, such as “Germany” or “US West.” An availability domain is an isolated, fault-tolerant set of resources consisting of at least one data center. Availability domains don't share infrastructure such as a building, power, or cooling. A failure in one availability domain is unlikely to impact the availability of other availability domains.
A fault domain is a grouping of hardware and infrastructure within an availability domain. Fault domains let you distribute your instances so they're not on the same physical hardware within a single availability domain, thereby introducing another layer of fault tolerance. Each availability domain contains three fault domains. A hardware failure or maintenance on Compute hardware that affects one fault domain doesn't affect instances in other fault domains.
Oracle Cloud Infrastructure Compute offers the choice, flexibility, control, and performance that your applications and workloads need. You can provision compute instances in minutes through an easy-to-use web console or through an API. Oracle Cloud Infrastructure provides bare metal, virtual machine (VM), and GPU instances:
Compute instances, regardless of shape or size, launch within minutes from the time that you provision them from the Oracle Cloud Infrastructure Console or issue the LaunchInstanceRequest API command.
You can remotely connect to your instance by using the industry standard secure shell (SSH) protocol with a public-private key pair for authentication for Linux instances. For Windows instances, you can use the Remote Desktop Protocol (RDP) client with a username and password.
Yes. You can run a custom startup script as part of the provisioning workflow by including it in the user_data key/value pair of the metadata attribute in the LaunchInstanceDetails object. For more information, see the LaunchInstanceDetails API documentation.
Yes. You can stop your instance without deleting it. The Compute service supports the following actions for an instance:
For billing information, see How am I billed for instances?
Customers can consume Oracle Cloud Infrastructure resources without any upfront commitment and pay only for what they use by creating an account at shop.oracle.com. Alternatively, existing customers can contact their sales representative to enable an existing pool of credits, or purchase a new pool, to consume Oracle Cloud Infrastructure resources based on published metered rates.
Oracle Cloud Infrastructure provides you with flexibility, access, and control over your compute instances. You can use a variety of monitoring tools, such as Microsoft SysInternals (sysmon, diskmon, process monitor) and Linux monitoring tools (sysstats, vmstate, iostate), or enterprise management tools such as Oracle Enterprise Manager, to monitor the health of your compute instances. For more information, see the Oracle Enterprise Manager documentation.
You can access Oracle Cloud Infrastructure Compute via the Oracle Cloud Infrastructure Console, REST API, or SDKs. Oracle customers can consume all resources with no upfront commitment and pay only for what they use by creating an account at shop.oracle.com. Alternatively, customers can contact their sales representative to enable an existing pool of credits, or purchase a new pool, and start consuming Oracle Cloud Infrastructure resources based on published metered rates.
After your account is provisioned, see the Getting Started Guide in the service documentation for more information. We have provided a tutorial guiding you through the steps to launch your first instance.
Oracle Cloud Infrastructure will continue to support customers running prior-generation compute instances. However, as we continue to release new instances types, we encourage customers to use the latest offerings to ensure the best performance and pricing. To review prior-generation instances and upgrade recommendations, see the following list.
Bare Metal High I/O (BM.HighIO1.36)
For customers using the BM.HighIO bare metal shape, we recommend upgrading to X7-based Dense I/O virtual machine instances. The X7-based VM.DenseIO2.16 shape offers the newer Intel Skylake processor, including 16 OCPUs, 240 GB of RAM, and 12.8 TB of NVMe storage at a lower price. Additionally, the X7-based VM.DenseIO2.16 shape offers higher network bandwidth. For details, see Compute Shapes in the service documentation. Customers with CPU-intensive workloads can also opt for a higher-CPU offering with the VM.DenseIO2.24 shape, which includes 24 OCPUs, 320 GB of RAM, and 25.6 TB of NVMe storage.
| Instance Type | Service Includes per Month | Recommended Upgrade Option |
|---|---|---|
| High I/O | BM.HighIO1.36 OCPU: 36 Memory: 512 GB Local Disk: 12.8 TB NVMe SSD Network Bandwidth: 10 Gbps Additional Storage: Up to 1 PB of remote Block Volumes |
X7-Based VM.DenseIO2.16 OCPU: 16 Memory: 240 GB Local Disk: 12.8 TB NVMe SSD Network Bandwidth: 16.4 Gbps Additional Storage: Up to 1 PB of remote Block Volumes |
"X5" Series Compute Instance Shapes
| SKU Type | "X5" Compute Instance Shape | Recommended Alternatives |
|---|---|---|
| Bare Metal Standard – "X5" | BM.Standard1.36 OCPU: 36 Memory: 256 GB Network Bandwidth: 10 Gbps |
X7-based BM.Standard2.52 OCPU: 52 Memory: 768 GB Network Bandwidth: 2x25 Gbps AMD-based BM.Standard.E2.64 OCPU: 64 Memory: 512 GB Network Bandwidth: 2x25 Gbps X7-based VM.Standard2.24 OCPU: 24 Memory: 320 GB Network Bandwidth: 24.6 Gbps |
| Bare Metal Dense I/O – "X5" | BM.DenseIO1.36 OCPU: 36 Memory: 512 GB Local Disk: 28.8 TB NVMe SSD Network Bandwidth: 10 Gbps |
X7-based BM.DenseIO2.52 OCPU: 52 Memory: 768 GB Local Disk: 51.2 TB NVMe SSD Network Bandwidth: 2x25 Gbps X7-based VM.DenseIO2.24 OCPU: 24 Memory: 320 GB Local Disk: 25.6 TB NVMe SSD Network Bandwidth: 24.6 Gbps |
| Virtual Machine Standard – "X5" | VM.Standard1.1 OCPU: 1 Memory: 7 GB Network Bandwidth: Up to 600 Mbps |
X7-based VM.Standard2.1 OCPU: 1 Memory: 15 GB Network Bandwidth: 1 Gbps AMD-based VM.Standard.E2.1 OCPU: 1 Memory: 8 GB Network Bandwidth: 0.7 Gbps |
| Virtual Machine Standard – "X5" | VM.Standard1.2 OCPU: 2 Memory: 14 GB Network Bandwidth: Up to 1.2 Gbps |
X7-based VM.Standard2.2 OCPU: 2 Memory: 30 GB Network Bandwidth: 2 Gbps AMD-based VM.Standard.E2.2 OCPU: 2 Memory: 16 GB Network Bandwidth: 1.4 Gbps |
| Virtual Machine Standard – "X5" | VM.Standard1.4 OCPU: 4 Memory: 28 GB Network Bandwidth: 1.2 Gbps |
X7-based VM.Standard2.4 OCPU: 4 Memory: 60 GB Network Bandwidth: 4.1 Gbps AMD-based VM.Standard.E2.4 OCPU: 4 Memory: 32 GB Network Bandwidth: 2.8 Gbps |
| Virtual Machine Standard – "X5" | VM.Standard1.8 OCPU: 8 Memory: 56 GB Network Bandwidth: 2.4 Gbps |
X7-based VM.Standard2.8 OCPU: 8 Memory: 120 GB Network Bandwidth: 8.2 Gbps AMD-based VM.Standard.E2.8 OCPU: 8 Memory: 64 GB Network Bandwidth: 5.6 Gbps |
| Virtual Machine Standard – "X5" | VM.Standard1.16 OCPU: 16 Memory: 112 GB Network Bandwidth: 4.8 Gbps |
X7-based VM.Standard2.16 OCPU: 16 Memory: 240 GB Network Bandwidth: 16.4 Gbps |
| Virtual Machine Dense I/O – "X5" | VM.DenseIO1.4 OCPU: 4 Memory: 60 GB Local Storage: 3.2 TB NVMe SSD Network Bandwidth: 1.2 Gbps |
X7-based VM.DenseIO2.8 OCPU: 8 Memory: 120 GB Local Storage: 6.4 TB NVMe SSD Network Bandwidth: 8.2 Gbps |
| Virtual Machine Dense I/O – "X5" | VM.DenseIO1.8 OCPU: 8 Memory: 120 GB Local Storage: 6.4 TB NVMe SSD Network Bandwidth: 2.4 Gbps |
X7-based VM.DenseIO2.8 OCPU: 8 Memory: 120 GB Local Storage: 6.4 TB NVMe SSD Network Bandwidth: 8.2 Gbps |
| Virtual Machine Dense I/O – "X5" | VM.DenseIO1.16 OCPU: 16 Memory: 240 GB Local Storage: 12.8 TB NVMe SSD Network Bandwidth: 4.8 Gbps |
X7-based VM.DenseIO2.16 OCPU: 16 Memory: 240 GB Local Storage: 12.8 TB NVMe SSD Network Bandwidth: 16.4 Gbps |
Billing depends on the shape that you used to create the instance, and the status of the instance.
| Instance Type | Billing Metric | Billing Stops When Instance Status Is |
|---|---|---|
| Standard | OCPU per hour | Stopped |
| Standard flex | OCPU per hour and GB per hour | Stopped |
| Dense I/O | OCPU per hour | Terminated |
| GPU | GPU per hour | Terminated |
| HPC | OCPU per hour | Terminated |
Refer to the Compute Pricing page for more information. For information about dedicated virtual machine hosts and Microsoft Windows Server images and how they are billed when they are stopped, see the sections about Microsoft Windows Server OS and Dedicated Virtual Machine Hosts in this FAQ.
Oracle Cloud Infrastructure Compute's autoscaling capability enables you to automatically scale Compute instances for a workload in response to changing performance metrics, instead of manually calling the Compute APIs or using a Terraform script. A guided Console experience and autoscaling APIs help you create autoscaling policies that automatically launch or terminate instances based on metrics emitted by instances in instance pools. As load increases, new instances are dynamically provisioned. And as load decreases, instances are automatically removed.
This capability is available at no additional cost for virtual machine (VM) instances in commercial regions.
Autoscaling acts on instance pools and relies on performance metrics that are collected by the Oracle Cloud Infrastructure Monitoring service. Instance pools allow you to group VM instances together and keep all VM instances in your pool healthy and running. Monitoring lets you capture average CPU and memory utilization metrics from instances in your instance pools.
With autoscaling, you configure thresholds on the aggregate metrics that Monitoring captures from instances in your instance pool. Autoscaling events are triggered when the thresholds are met or exceeded based on your autoscaling policy and rules. Autoscaling responds to a trigger by adding or removing instances from your instance pools. Autoscaling works by changing the size of your instance pool: instance pools are self-managing and will terminate or launch new instances until the pool reaches the target size.
You need to first launch an instance pool using an initial size, and then define an autoscaling configuration for the instance pool. When you define an autoscaling configuration, it sets up Monitoring such that metrics can start flowing from your instances into Monitoring. Monitoring then averages the metrics and sends back the averaged metrics to autoscaling, which triggers events and starts scaling based on the thresholds you set.
An autoscaling configuration defines the information that is needed to configure autoscaling for an instance pool. It contains an autoscaling policy with scaling rules. It also defines a cooldown period between scaling events.
Each instance pool can have one autoscaling configuration.
An autoscaling policy defines the minimum and the maximum number of instances to scale to and the initial size of the instance pool. It also defines the autoscaling policy type. Each autoscaling policy also contains two autoscaling rules, one rule for scaling in and another rule for scaling out.
You can apply the following types of autoscaling to an instance pool:
Autoscaling is supported for virtual machine (VM) and bare metal instance pools that use Standard, DenseIO, and GPU shapes.
An autoscaling rule defines which metric to use for scaling and the thresholds for scaling in and out. You choose a single metric that is used for both the scale-in rule and the scale-out rule. You also define the number of instances to add or remove with each scaling action.
Autoscaling supports the CPU utilization and memory utilization metrics.
You can add or remove instances in increments of one, up to the maximum instance pool size of 50.
You can scale in and scale out within minutes. You can also control how frequently autoscaling is triggered by adjusting a cooldown period that defines how long to wait between autoscaling actions.
A cooldown period is the minimum amount of time that autoscaling waits before taking another scaling action. It lets the instance pool stabilize at the updated level. The cooldown period starts after the instance pool reaches the target size from the previous scaling event. The minimum cooldown period is five minutes.
Instance pools monitor the life cycle state of instances. If the number of instances in the running or launching state is below the instance pool size, the instance pool creates more instances. If the number of instances in the running or launching state is less than the target size, the instance pool creates more instances.
There are no service limits associated directly with autoscaling. However, instances that are created with autoscaling actions count against your Compute instance limits. When you reach your Compute instance limits, autoscaling is unable to add more instances to your instance pools. See the Service Limits documentation for the default limits for each instance type and instructions on how to request a service limit increase.
You can attach a load balancer working set OCID to your instance pool. After you do this, every time an instance is added to the instance pool, its IP address is also added to the backend set. When the instance reaches a healthy state (the instance is listening on the configured port number), incoming traffic is automatically routed to the new instance. Similarly, every time an instance is removed, the IP address is also removed from the backend set. When removing instances from the load balancer working set, autoscaling waits two minutes before terminating the instance. The two minute delay allows the Load Balancing service to drain connections on the IP address for the instance before the instance is terminated. Any connections that are still active after two minutes are terminated when the instance is shut down.
If the instance configuration was based on an Oracle-provided image released after November 18, 2018, the OracleCloudAgent that emits metrics and works with Monitoring and autoscaling is already installed. You can also manually build, install, and then enable the agent for your custom images.
We support all VM instance shapes including VM.Standard1, VM.DenseIO1, VM.Standard2, VM.DenseIO2, VM.Standard2.E2, VM.GPU2, and VM.GPU3.
Currently, we support only AMD shapes.
| Virtual Machine Compute | Bare Metal Compute |
|---|---|
| VM.Standard.E4.Flex | BM.DenseIO.E4.128 |
| VM.Standard.E3.Flex | BM.Standard.E4.128 |
| BM.Standard.E3.128 |
Enabling confidential computing doesn’t incur any extra costs on top of compute instance pricing.
Currently, we support creating only new confidential VM instances.
Bare metal instances are on-demand, bare metal compute resources in the cloud. Unlike virtual machine (VM) instances, bare metal instances are entire physical hosts dedicated to a single customer's use with no hypervisor or Oracle applied software installed. You have full control of the bare metal host's resources, which gives you flexibility, control, and performance without compromise. Bare metal compute instances are ideal for your most demanding applications and workloads.
Oracle Cloud Infrastructure Compute offers a variety of instance types. Each instance type provides a different hardware configuration to support a variety of applications and workloads.
See the Service Limits help documentation for the default limits for each instance type and instructions on how to request a service limit increase. We are happy to increase the limits for your account as needed.
Currently, Oracle Cloud Infrastructure doesn't provide built-in capability to migrate a bare metal instance to a different bare metal instance type or virtual machine (VM) shape. However, you can perform the migration manually by launching a new compute instance from a boot image that you created (by using the Create Image feature) and subsequently attaching your block volumes to the new instance. If you have data persisted locally, you must copy or replicate the local data manually to the new instance. You can also mitigate changing the shape or scaling for an instance via boot volumes. When you terminate an instance, you can keep its boot volume and launch a new instance with a different shape by using the boot volume that you kept from the original instance.
Yes. Bare metal instances are dedicated physical hosts with no hypervisor installed on them. You have access to the host and can install your own type 2 hypervisor (hosted hypervisor) such as KVM or VirtualBox to run any version of OS supported by the hypervisors, subject to your existing licensing terms.
Oracle Cloud Infrastructure Compute dedicated virtual machine hosts enable you to run VM compute instances on a physical server that is dedicated to your Oracle Cloud Infrastructure tenancy. No VMs from any other tenancy or Oracle customer will run on this dedicated host. You can then set an optional parameter when launching a VM compute instance to place it on your Dedicated Virtual Machine Host. These dedicated hosts are "single tenant" - i.e., dedicated exclusively to your tenancy. VM characteristics, such as number of OCPUs and amount of memory, and performance are the same as when running on regular shared hardware in Oracle Cloud Infrastructure.
Oracle Cloud Infrastructure Compute DVH is currently offered in a DVH.Standard2.52 shape. This shape allows you to launch any VM.Standard2 instance on the DVH. New DVH shapes will be added over time.
You are charged for the dedicated virtual machine host when it is in the running state. You are not charged for the individual compute VM instances launched on the host, however, you will still be charged per OCPU hour for a Windows Server license when you run a VM instance using a Windows Server image. Billing stops when you terminate the dedicated host. For the DVH.Standard2.52 host, you are charged for a 52 OCPU BM.Standard2.52 instance once the dedicated virtual machine host starts running. On your bill, you will see a charge for 52 OCPUs under "Oracle Cloud Infrastructure Compute Bare Metal Standard - X7". You can at maximum use 48 OCPUs for running your VMs in a DVH.Standard2.52.
The only supported actions with a dedicated virtual machine host are to launch, move compartments and terminate. However, you are not allowed to terminate the dedicated virtual machine host if there are VM instances still running on it. You are required to terminate all VM instances before you can terminate the dedicated virtual machine host.
Oracle Cloud Infrastructure compute instances running Oracle Linux come included with Oracle Ksplice. Ksplice is an OS-management technology that lets you update important kernel and user-space security components without requiring a reboot.
For more information about downloading patches to your OS instance, see Oracle Ksplice.
Yes. You can create a custom image of your boot disk as a backup or use it as a mechanism to package your preconfigured OS image and use it to launch new compute instances. This is particularly useful when you need to create multiple compute instances with similar configurations. The custom image is instance-type and shape agnostic; it can be used to launch any instance types or shapes: bare metal or virtual machine instances.
After you initiate image creation, the system stops your compute instance to ensure a consistent boot disk image. The time it takes for the image creation process depends on the size of the boot disk. After the image creation is complete, the compute instance automatically restarts. For applications and services that don't automatically start when the instance reboots, you're expected to restart them manually.
On April 25, 2020, Oracle Cloud Infrastructure changed the pricing of Windows licenses to $0.092 per OCPU/hr. The new price is consistent with Windows pricing across cloud providers. Oracle Cloud Infrastructure sets the price of third-party software licenses based on the cost of licenses from the third-party software provider.
Microsoft Windows Server is available as an Oracle-provided platform image and is also supported for custom image import. The following versions and editions of Microsoft Windows Server are supported:
Platform images are available in the English language. Refer to the documentation about platform images and windows BYOI.
The cost of a Microsoft Windows Server license is an additional cost, on top of the underlying compute instance price. Billing depends on the status and shape of the instance. The Windows Server license charge starts when the instance is in the "running" state and ends when you terminate the instance.
For Standard VM and bare metal instances, when the instance is in a "stopped" state, billing pauses for both the compute instance cost and the Microsoft Windows Server operating system license cost.
For most Dense I/O, GPU, and HPC shapes, billing continues for both the compute instance and the Windows Server license when the instance is stopped because the attached GPU and NVMe local storage resources are preserved. To halt billing, you must terminate the instance. For shapes in the VM.GPU.GU1 series (also named the VM.GPU.A10 series), billing is paused for stopped instances.
You can get more information about Microsoft Windows Server pricing from the Compute Pricing page.
Oracle Cloud Infrastructure enables automatic updates on Microsoft Windows Server and uses the default settings for applying Windows patches. You need to update your VCN security list to enable egress traffic for port 80 (http) and port 443 (https) to install patches from Microsoft Windows Update Servers.
Yes. You can create a custom image of your Windows Server instance and use it to launch a new compute instance. We support the creation of "generalized" images (used to create a template or golden image) and "specialized" images (used as backup) for your Windows instance. For more information about these image types, see Creating Windows Custom Images help documentation.
Yes. You can bring your own license (BYOL) for Microsoft Windows Server on a dedicated bare metal or dedicated virtual machine host, subject to the Microsoft Product Terms. You are responsible for managing your own licenses to maintain compliance with Microsoft licensing terms. For more information, see Licensing Options for Microsoft Windows.
The following table shows the BYOL requirements for Microsoft licenses on Oracle Cloud Infrastructure.
| Microsoft License | Bare Metal Machines and Dedicated Virtual Machine Hosts | Virtual Machines (Multi-Tenant Shared Host) |
|---|---|---|
| Windows Server | BYOL on a bare metal dedicated host is only eligible when using a KVM hypervisor. BYOL is not eligible for Microsoft Windows Server using Oracle-provided images or when importing your own Microsoft Windows Server image. | Not eligible. Shared hosts must use Oracle-provided images that include the Microsoft license. |
| SQL Server Subject to the Microsoft Product Terms |
Eligible. You must have License Mobility through Software Assurance. |
Eligible. You must have License Mobility through Software Assurance. |
| Visual Studio (MSDN) | Eligible. Non-production use only. |
Eligible. Non-production use only. |
| Microsoft 365 Apps for enterprise (Office 365 ProPlus) and Office Professional Plus | Eligible | Not eligible. |
| Microsoft Office | No* | No |
| Windows 7, Windows 8, and Windows 10 | Eligible. You must have an Enterprise Agreement license with Software Assurance or a Windows Virtual Desktop Access (VDA) license. |
Not eligible. |
| Other Microsoft applications | Eligible. Subject to the Microsoft Product Terms. |
Eligible. You must have License Mobility through Software Assurance. |
Application licenses such as SQL Server or System Center require License Mobility through Software Assurance when running on Oracle Cloud Infrastructure VM instances. License Mobility is not used for Microsoft Office, Windows clients, or Windows Server BYOL. Review the Microsoft Product Terms to validate which applications support License Mobility.
Direct questions about your licensing rights to Microsoft or your Microsoft reseller.
No. You must bring your own Microsoft Windows image if you bring your Microsoft Windows Server license on a dedicated Bare Metal Machine and Dedicated Virtual Machine Hosts host only. BYOL of Microsoft Windows Server license is not permitted for Virtual Machines on a multi-tenant host.
Oracle Support provides limited assistance for Microsoft Windows Server operating systems running on Oracle Cloud Infrastructure and for SQL Server images provided by Oracle Cloud Marketplace. For product issues, work directly with Microsoft Support. You can get more information about support options for Microsoft software.
We provide images with a variety of Linux distributions such as Oracle Linux, CentOS, and Ubuntu, as well as Microsoft Windows Server. For a complete list and more details, see Oracle-Provided Images help documentation. We support Oracle Linux OSs with Oracle Linux Premier Support included at no additional charge with Oracle Cloud Infrastructure.
You can launch any of the supported OSs on any Oracle Cloud Infrastructure Compute bare metal or virtual machine compute instance shape. You can see a list of all available shapes on the Compute Pricing page.
Yes. Oracle Cloud Infrastructure Compute supports bringing your own OS image. For more information, see Bring Your Own Image help documentation.
Oracle Cloud VMware Solution is based on VMware Cloud Foundation and provides a fully supported, customizable cloud environment for VMware deployments and migrations. The solution delivers a full-stack software-defined data center (SDDC), including VMware vCenter, ESXi, NSX, and vSAN. Specific use cases targeted by Oracle Cloud VMware Solution include; datacenter and application migration, hybrid extension, on-demand capacity, and disaster recovery.
Oracle Cloud VMware Solution is currently available in all OCI regions.
Oracle Cloud VMware Solution is not a ‘managed service’. Instead it is ‘customer managed’ and provides customers full administrative access and control. Customers control and manage VMware operations and updates.
Oracle Cloud VMware Solution supports VMware cluster deployments up to the current VMware limit of 64 instances for multi-host SDDC deployments. Additional host instances can be added at any time up to the maximum supported in the customer's tenancy based on OCI service limits. Note: The customer will use VMware software and tooling to define additional clusters within vCenter Server. The Oracle Cloud VMware Solution SDDC can contain more than 64 hosts, but each cluster has a current maximum of 64 based on VMware limits.
Oracle Cloud VMware Solution supports a single ESXi host SDDC for a Single Node SDDC or a minimum of 3 ESXi hosts for multi-host SDDC.
Oracle provides Tier 1, Tier 2, and Tier 3 customer support for all support related issues.
Oracle provides support for core VMware VCF components (vSphere, vCenter, vSAN, NSX) which we license and deploy.
Oracle Cloud VMware Solution provides support for provisioning vSphere 6.5, 6.7, and 7.0 while these versions are in the General Support Phase from VMware, as defined by the VMware Lifecycle Policy.
Oracle will provide commercially reasonable support for provisioning of vSphere 6.5 and 6.7 environments after they end General Support from VMware (October 15, 2022) and enter the Technical Guidance Phase. Oracle Cloud VMware Solution shape support will be limited to the shapes supported at the end of General Support. New Oracle Cloud VMware Solution shapes introduced after October 15, 2022, will not be enabled for 6.5 or 6.7. Customers will no longer be able to provision using 6.5 or 6.7 for existing shapes after December 13, 2022.
Additional VMware product suites are expected to function as advertised on Oracle Cloud VMware Solution based on VMware compatibility matrix.
No, the customer or their operating partner is responsible for all VMware configuration, patching, operations, and application deployment.
Single Node SDDC is limited to a global maximum of 10 across tenancies and regions.
You can use HCX to migrate workloads to production 3-node SDDC or using your preferred method of migrating the workload from one SDDC to the other.
Please refer to the Service Descriptions (PDF) for details.
Please refer to the Service Descriptions (PDF) for details.
High availability (HA) configuration works only in multi-host cluster (3 or more hosts). All other features that work with a multi-host will work with a Single Host.
BYOL VMware license model is not supported for core Oracle Cloud VMware Solution components; vSphere/NSX/vSAN. This is the VMware standard across all public cloud offerings.
Oracle Cloud VMware Solution supports a minimum subscription term of eight hours using the hourly subscription option.
No, the Oracle Cloud VMware Solution product is billed via a single SKU per host in the customers usage reports and include both infrastructure and VMware license access.
Yes. Oracle Cloud VMware Solution can easily be connected to other Oracle Cloud Infrastructure and service offerings such as Oracle Database as a Service.
Yes. Customers should observe VMware's guidance and recommendations for the monitoring tools in question.
Standard Oracle Cloud telemetry is not available as no agent is installed in the ESXi bare metal instance. However, customers can get compute and network telemetry from VMware directly in ESXi, vCenter and NSX-T administrative interfaces, or via the APIs provided as part of these offerings.
The licensing policy for Oracle software, including Oracle Database, running on virtualized environments has not changed. Customers that deploy Oracle software on Oracle Cloud VMware Solution are subject to the Oracle’s existing server/hardware partitioning policy. For more detail on Oracle’s Partitioning Policy, see the following resource: Server/Hardware Partitioning (PDF).
Customers need to buy the licenses for attached services such as VMware Site Recovery Manager (SRM), Horizon VDI, vRealize Suites, and Tanzu from VMware.
When the host is in the reserved capacity, the billing is based on reserved capacity SKU pricing. Once the host is provisioned from reserved capacity through Oracle Cloud VMware Solution, the host will switch to using Oracle Cloud VMware Solution SKU pricing based on the selected commit interval. If the host is deleted before the end of the commit period, then the host will continue to be billed for the duration of the commitment. Hosts in the reserved capacity pool (not active) are billed independently of Oracle Cloud VMware Solution commit billing.
Refer to Capacity Reservations for details on reserved capacity and usage.
We will continue to have X7 capacity in the existing regions (as of March 2022) and will enable customers to consume Oracle Cloud VMware Solution on X7 for their commit periods.
Please see this cost estimator and navigate to the “Services” tab, select the “Native VMware” option in the “Select Category” drop-down menu, and load “Oracle Cloud VMware Solution.”
Oracle Cloud VMware Solution supports an automated, guided workflow along with some manual steps to upgrade to VMware vSphere version 7 from older versions. It automates updating an SDDC, providing a downloadable link for binaries and licenses, performing a rolling upgrade of the host to bring it to the latest version. Please refer to Oracle Cloud VMware Solution documentation for detailed step-by-step instructions.
Once an SDDC upgrade is complete, the Details page provides you with links for VMware Cloud Foundation bundle binaries and licenses. The downloadable links are preauthenticated read-only object storage bucket URLs pointing to the vCenter component bundle and the NSX-T Data Center bundle.
If you need assistance with binaries or licenses, please submit a ticket at My Oracle Support.
Once an SDDC upgrade is complete, from the list of ESXi hosts to be upgraded, select each host and upgrade to the latest version. The new host created will be with the existing host’s configuration. Once the workloads are migrated from the old host to the new ESXi host, old ESXi hosts need to be deleted. The new ESXi host will be billed hourly, and there is no minimum eight-hour charge on this host, unlike the regular hourly SKU. Any term commitments assigned to the old host are moved to the new host when the old host is deleted and have the same terms as the original commitment.
There will be a notification that the old hosts need to be deleted, and the new hosts will be billed hourly until the old hosts are deleted.
Yes. From the Create Compute Instance wizard, you can launch prebuilt Oracle enterprise images and solutions that are enabled for Oracle Cloud Infrastructure.
Depending on the Oracle application, there are 30-day evaluation trial terms. At the end of the trial term, a license is required to continue use. Any trial information is detailed in the preinstallation notes in the image selection.
Oracle Cloud Infrastructure provides the following storage options to support different use cases:
Local NVMe SSDs provide very high performance storage and are ideal for the most demanding workloads. For more information about NVMe SSD performance, see the product specification.
After you terminate your compute instance, you have the option to keep its boot volume for later reuse. If you choose not to keep the boot volume, it's deallocated and wiped out. Local NVMe storage for storage-optimized instances is wiped out and deallocated. Any data in the block volumes attached to the instance persists and remains available for later use.
Before terminating the instance, you can create a custom image of the boot disk and use the custom image to launch new instances at a later time.
All third-party images are accessible in the Oracle Cloud Infrastructure Console via the embedded Marketplace. Choose the partner image that you want to launch, and you are guided through the Launch Instance process.
After the partner image is installed, any product issues related to the image are addressed by the partner. For support issues related to installing images, submit a ticket in My Oracle Support.
Oracle Cloud Infrastructure Compute VMs offer smaller compute shapes than bare metal instances. VMs use the same cloud-optimized hardware and networking infrastructure as bare metal instances to deliver compute shape flexibility and performance for your changing application needs.
Oracle Cloud Infrastructure Compute offers flexible VM instances where you can configure the memory and CPU of your instance to meet the varying needs of the applications that you build. Standard E3 based flexible VM instances support between 1 and 64 cores and between 1 and 64 GB RAM per core (up to a maximum of 1024 GB).
You can also choose fixed shapes with a range of options including Intel and AMD processors, NVMe local SSD storage, and GPUs. For details, see the Compute Shapes page.
See the Service Limits help documentation for the default limits and instructions on how to request a service limit increase. We are happy to increase the limits for your account as needed.
Each VM shape has a different number of processor cores, amount of memory, and disk configuration, so you can easily select a size that matches the needs of your application.
There are three types of VM shapes.
You can use the compute Console, API or CLI to change the shape of a VM after it's created. You can choose any VM shape that is compatible with the existing operating system image. The shape change will require a reboot but will preserve all instance properties. See the technical documentation for more information about how to change the shape of an instance.
You can also migrate your VM manually by launching a new compute instance from a boot image that you created (by using the Create Image feature) and subsequently attaching your block volumes to the new instance. If you have data persisted locally, you must copy or replicate the local data manually to the new instance.
Oracle Cloud Infrastructure provides several options for sending feedback or getting support from the community and from Oracle. You can find vibrant and active community support in the Oracle Forum and regular updates via the Oracle Cloud Infrastructure Blog.
You can also get support for debugging and troubleshooting by submitting a service request via My Oracle Support.