There are lots of wrong and right articles in internet, when you try to execute Hands-on Labs by yourself, there is chance that you could get drifted away or get severely confused, We strictly adhere to Official Oracle Cloud Documentation, offering you reliable and precise information without personal interpretations. This means you can trust our content 100% Genuine.
Prerequisites
Before you Start the Lab kindly ensure you have the following:
- An active OCI account.
- and your Account user has, necessary IAM policies to create and manage networking components and Resources.
Lab Task :
In this Lab is about moving Resources in One Compartment to another using (OCI) web console.
Lab Task Flow
Task 1: Identifying Compartment and getting Reources within it
There are four main types of resources that we can build in any Cloud
- Compute instances
- Databases
- Storage
- Networking Resources
Follow below Guided Hand-on Lab Link to perform Corresponding Operations.
Task 2: Moving a Single Resource Between Compartments
Task 3: Moving Multiple Resources Between Compartments
- (OCI doc.) Steps to move Multiple Resources Between Compartments using (OCI) CLI
This Option is Not Possible using (OCI) web console, this can be Done only with (OCI) CLI and this topic will be explained when we see series of Lab Task using (OCI) CLI.
Task 4: Moving Other Resources
Follow below Guided Hand-on Lab Link to perform Corresponding Operations.
- Move a VCN & Subnet to a Different Compartment.
- Move an instance to a different compartment.
- Move a custom image to a different compartment.
- Move an instance configuration to a different compartment.
- Move an instance pool to a different compartment.
- Move an autoscaling configuration to a different compartment.
- Move a cluster network to a different compartment.
- Move a dedicated virtual machine host to a different compartment.
Required concept knowledge
Moving Resources to a Different Compartment
- Most resources can be moved after they are created. There are a few resources that you can't move from one compartment to another. Also, you can't move certain resources from a security zone to a compartment that's not in the same security zone, because it might be less secure.
- Some resources have attached resource dependencies and some don't. Not all attached dependencies behave the same way when the parent resource moves, for some resources, the attached dependencies move with the parent resource to the new compartment.The parent resource moves immediately, but in some cases attached dependencies move asynchronously and are not visible in the new compartment until the move is complete. for other resources, the attached resource dependencies do not move to the new compartment, You can move these attached resources independently.
- After you move the resource to the new compartment, the policies that govern the new compartment apply immediately and affect access to the resource. Depending on the structure of your compartment organization, metering, billing, and alarms can also be affected.
- See the service documentation for individual resources to familiarize yourself with the behavior of each resource and its attachments.
Reference
Stay tuned for more posts on managing your OCI resources effectively! Happy cloud computing!