About Migrating to Oracle Cloud Infrastructure

Why Migrate to Oracle Cloud Infrastructure

Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions. You can gain several advantages by doing so.

In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations. Certain regions support the Oracle Cloud Infrastructure platform.

Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards. It provides more consistent performance and better features at lower costs. Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features. See Data Regions for Platform and Infrastructure Services.

You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure:

Organize cloud resources into a hierarchy of logical compartments.
Create fine-grained access policies for each compartment.

Oracle WebLogic Server for OCI allows you to quickly provision a WebLogic domain in Oracle Cloud Infrastructure and at the same time provides you the flexibility to customize your WebLogic domain. It also offers the following advantages over Oracle Java Cloud Service:

Supports WebLogic Server major release versions after 12.2.1.4.0.
Offers flexibility to add or remove patches.
Allows managing the operating system or domain after provisioning, without any restrictions.
Allows choosing any supported method to backup, scale, or patch a domain.
Allows full customization of the Oracle-managed load balancer.
Supports cloning instances.
Includes optional autoscaling feature.
Supports a documented disaster recovery process.
Allows WebLogic Server domains without Java Required Files (JRF).
Integrates with multiple Oracle Cloud Infrastructure services to monitor, trace, deploy, scale and autoscale your WebLogic domain, and other Oracle Cloud Infrastructure services to manage and patch your WebLogic domain resources.
Offers the option to pay per OCPU/Hour for Oracle WebLogic Server for OCI images with the entitlement to install any Oracle WebLogic Server version.

To learn more, see Upgrade Your Classic Services to Oracle Cloud Infrastructure.

About the Migration Scope

Before you migrate your Oracle Application Container Cloud Service applications to Oracle Cloud Infrastructure Container Engine for Kubernetes, consider the scope and constraints of this process.

Oracle doesn't support the migration of applications that meet any of these conditions:

The application is configured to use Oracle Identity Cloud Service for authentication.
The application uses the cache service.

Most applications also connect to and use other Oracle Cloud services. You can migrate your application to Oracle Cloud Infrastructure Container Engine for Kubernetes and keep the connectivity to other Oracle Cloud services in Oracle Cloud Infrastructure Classic or migrate the other services to Oracle Cloud Infrastructure. This guide doesn't include the detailed procedure for migrating these services from Oracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure.

You must consider that after the migration process the application URL will change.

Compare Oracle Cloud Infrastructure to Classic

Get familiar with basic Oracle Cloud Infrastructure security, network, and storage concepts, and their equivalent concepts in Oracle Cloud Infrastructure Classic.

Cloud resources in Oracle Cloud Infrastructure are created in logical compartments. You also create fine-grained policies to control access to the resources within a compartment.

You create instances within an Oracle Cloud Infrastructure region. You also specify an availability domain (AD), if supported in the selected region. Oracle Cloud Infrastructure Classic does not use availability domains.

A virtual cloud network (VCN) is comprised of one or more subnets, and an instance is assigned to a specific subnet. In Oracle Cloud Infrastructure Classic, you assign instances to IP networks or the shared network. Typically, you create one subnet for the shared network, and create a separate subnet for each IP network in Oracle Cloud Infrastructure Classic. Note that unlike Oracle Cloud Infrastructure Classic, Oracle Cloud Infrastructure does not allow you to reserve IP addresses for platform services.

A subnet's security lists permit and block traffic to and from specific IP addresses and ports. In Oracle Cloud Infrastructure Classic, an instance's access rules provide similar capabilities, although security lists are configured at the subnet level.

Instances can communicate with resources outside of Oracle Cloud by using Oracle Cloud Infrastructure FastConnect, which provides a fast, dedicated connection to your on-premises network. This service is equivalent to Oracle Cloud Infrastructure FastConnect Classic. Alternatively, use IPSec VPN in Oracle Cloud Infrastructure as a replacement for VPN as a Service (VPNaaS) or Corente in Oracle Cloud Infrastructure Classic.

A bucket in Oracle Cloud Infrastructure Object Storage can be used to store files and share them with multiple instances. A user's generated authentication token (auth token) is required to access the bucket. Oracle Cloud Infrastructure Object Storage Classic provides the same service in Oracle Cloud Infrastructure Classic, but does not use auth tokens.

To learn more, see Key Concepts and Terminology in the Oracle Cloud Infrastructure documentation.

About Oracle Cloud Infrastructure Container Engine for Kubernetes

Oracle Cloud Infrastructure Container Engine for Kubernetes is a fully-managed, scalable, and highly available service that you can use to deploy your containerized applications to the cloud.

You can use Oracle Cloud Infrastructure Container Engine for Kubernetes when your development team wants to reliably build, deploy, and manage cloud-native applications. You specify the compute resources that your applications require, and Oracle Cloud Infrastructure Container Engine for Kubernetes provisions them on Oracle Cloud Infrastructure in an existing tenancy.

A Kubernetes cluster is a group of nodes. The nodes are the machines running applications. Each node can be a physical machine or a virtual machine. The node's capacity (its number of CPUs and amount of memory) is defined when the node is created. A cluster can be organized into namespaces, to divide the cluster's resources between multiple uses.

To learn more about Oracle Cloud Infrastructure Container Engine for Kubernetes, see Overview of Container Engine for Kubernetes.

About Oracle Cloud Infrastructure Users and Groups

Use the Identity and Access Management (IAM) system in Oracle Cloud Infrastructure to manage users, groups, and policies.

A policy is a document that specifies who can access which Oracle Cloud Infrastructure resources that your company has, and how. To migrate your Oracle Application Container Cloud Service applications to Oracle Cloud Infrastructure you must define the policies required to perform operations on Oracle Cloud Infrastructure Container Engine for Kubernetes clusters and on the Oracle Cloud Infrastructure Registry repositories . See Policy Configuration for Cluster Creation and Deployment and Policies to Control Repository Access.

About the Migration Task Flow

Understand the process of migrating your existing Oracle Application Container Cloud Service applications to Oracle Cloud Infrastructure Container Engine for Kubernetes.

The following diagram shows the process of deploying an Oracle Application Container Cloud Service application to Oracle Cloud Infrastructure Container Engine for Kubernetes.

Description of accs_migration_overview.png follows

Description of the illustration accs_migration_overview.png

The migration process includes the following tasks:

Create the Kubernetes cluster. Create the cluster in Oracle Cloud Infrastructure Container Engine for Kubernetes.
Configure kubectl. Download the kubeconfig file to have access to the cluster by using kubectl.
Create a Docker image. Create the Dockerfile from a template depending on the runtime of your application.
Push the Docker image to Oracle Cloud Infrastructure Registry
Create the Kubernetes configuration. Set up the deployment.yaml, services.yaml, and env.properties files, including the configuration of the registry and SSL secrets.
Deploy your application to the Kubernetes cluster.