The next few topics explain the benefits of migrating your existing Oracle Developer Cloud Service (DevCS) instance from Oracle Cloud Infrastructure Classic (OCI Classic) to Oracle Cloud Infrastructure (OCI), and provide an overview of the migration process.
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. A region supports either the Oracle Cloud Infrastructure Classic or Oracle Cloud Infrastructure platform.
Oracle Cloud Infrastructure is Oracle's more modern infrastructure platform that's based on the latest cloud technologies and standards. It typically provides better performance than Oracle Cloud Infrastructure Classic. Oracle Cloud Infrastructure also has more predictable pricing and lower costs in terms of Oracle Compute Units (OCPUs) per hour. Most importantly, 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 in Oracle Cloud Infrastructure when you migrate your cloud resources from Oracle Cloud Infrastructure Classic:
- Organize cloud resources into a hierarchy of logical compartments.
- Create fine-grained access policies for each compartment.
About the Migration Scope
Before you migrate your existing DevCS instance to OCI, ensure that the service instance meets the prerequisites for the migration.
You need a DevCS instance in the OCI region set up with a dedicated OCI compartment and a bucket. This guide includes procedures that describe how to create the target DevCS instance, and how to set up a compartment and a bucket, but doesn't include detailed procedures on the configuration of basic OCI security, network, and storage resources that might be required to support your instance. Instead, this guide provides references to the OCI documentation as appropriate.
Using the Export/Import Data feature of a project, you can automate the migration of some of the project's artifacts of the source DevCS instance to the project of the target DevCS instance. The artifacts that aren't migrated must be manually re-created other artifacts in the target DevCS instance project. This guide includes detailed procedures on how to migrate such artifacts.
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 the Migration Task Flow
At a high level, the migration process is composed of these tasks:
|Task||Time Required||More Information|
|Create the target DevCS instance||30 minutes||Create the Target DevCS Instance in the OCI Region|
|Set up the OCI connections in the target DevCS instance||15 minutes||Set Up the OCI Connections on the Target Oracle Cloud Account|
|Set up OCI Object Storage bucket or OCI Object Storage Classic container||10 minutes||Set Up an OCI Object Storage Bucket or an OCI Object Storage Classic Container|
|Migrate VMs and VM templates from the source DevCS instance to the target DevCS instance||Few minutes for each Build VM template and Build VM||Migrate VMs|
|Export a project's data in the source DevCS instance to an OCI bucket or an OCI Object Storage Classic container||15 minutes||Export Project Data From the Source DevCS Instance|
|Create a project with exported project's data in the target DevCS instance.||10 minutes||Create a Project With an Exported Project's Data in the Target DevCS Instance|
|Migrate the artifacts that weren't exported from the source DevCS project to the target DevCS project.||1 - 1.5 hours for all artifacts of a project||Migrate Other Artifacts and Data|
|Clean up the source DevCS instance||20 minutes||Clean Up Resources in Oracle Cloud Infrastructure Classic|