Compute Cloud@Customer introduces new features
- Services: Compute Cloud@Customer
- Release Date: January 15, 2025
A new release of Compute Cloud@Customer is now available with the following new features:
- Updated Platform Images
-
You can create instances with the following new platform images.
- New Marketplace Images
-
You can request access to the following Marketplace images that are tested and approved for use on Compute Cloud@Customer:
-
Oracle Weblogic Server Enterprise Edition UCM
This image provides binaries of the Oracle WebLogic Server and the Java Development Toolkit along with the entitlement to create Oracle WebLogic Server domains in your Compute Cloud@Customer instances.
-
Oracle WebLogic Suite UCM
Quickly create instances that contain the key components needed to develop, test, and deploy Java EE applications in Oracle WebLogic Server or Oracle Forms applications.
For more information, see Marketplace Images.
-
- New Policy Requirement
- There is a new policy that you need to create in your OCI tenancy. The new policy allows a user to initiate a registration process that enables the infrastructure to communicate with your OCI tenancy. See Policy 4 in Add Required Policies
- New Port Needed for Instance Console Connections
-
The Console Connection feature needs access to port 1443. Previously, port 443 was used. See Network Port and Protocol Matrix.
- Uplink Reference Topologies
-
The integration of a Compute Cloud@Customer into the data center network can be challenging due to existing configurations, local requirements, and standard practices. There are various ways to configure the uplinks, and Oracle provides assistance in advance. The documentation provides examples of commonly used topologies, with switch configuration examples to guide network administrators in mapping their specific setup. See Reference Topologies.
- Kubernetes Engine
-
The following new features are added for Kubernetes Engine (OKE):
-
Node Doctor: The Node Doctor utility helps you troubleshoot a cluster worker node that's not Active or Running. Node Doctor can identify potential problem areas and provide information to help you address those problem areas. The utility can collect node system information into a support bundle to enable you to get help from Oracle Support. See Using Node Doctor to Troubleshoot Worker Node Issues.
-
Node cycling: By default when you update a node pool, only new nodes that are added during this update or that are added later receive the updates. Node cycling enables you to replace existing nodes with new nodes that use updated settings. Node cycling performs an in-place update of all existing nodes in the node pool to the latest specified configuration. New nodes are created, workloads moved onto them from existing nodes, current node pool updates applied, and the original nodes terminated. See Node Cycling an OKE Node Pool.
-
Node labels: A node label is a key/value pair that enables you to target pods for scheduling on specific nodes or groups of nodes. See the OCI CLI procedure in Creating an OKE Worker Node Pool.
-
Persistent storage: New ability to create high performance block volume storage and create file system storage by using the CSI (Container Storage Interface) plugin. See Adding Storage for Containerized Applications.
-
- SR-IOV Support
-
Single root I/O virtualization (SR-IOV) technology enables virtual machines to achieve low latency and high throughput simultaneously on 1 or more physical links. This technology is ideal for low-latency workloads such as video streaming, real-time applications, and large or clustered databases. Hardware-assisted (SR-IOV) networking uses the VFIO driver framework. Note that instances configured with SR-IOV can't be live migrated. See Configuring SR-IOV for Virtual Networking.
- Dynamic Routing Gateways Limit Increase
-
As of this release, the limits for Dynamic Routing Gateways (DRG) have increased to 32 total DRGs, with up to 16 SR-IOV DRGs.
- Flex Network Limit Increase
-
As of this release, the maximum number of flex networks per port is now 8 with a maximum of 32 flex networks per rack. This change allows up to 32 end-customers to be hosted with the HSP (Hosting Service Provider) use case.
The following restrictions apply:
-
The relationship between flex networks and DRGs is 1:1.
-
A flex network can't share a DRG with another flex network.
-
A flex network can't share a DRG with one or more direct attach Exadata networks.
When upgrading to this release, if you have existing flex or Exadata networks that share a DRG with other flex networks for Exadata direct connect, they can no longer share a DRG. Each flex network must have its own DRG.
-