Storage
We have discussed compute instances in Chapter 4. We have seen how to create a new compute instance, using one of the images provided by Oracle or Partners-provided images. Now that we have a compute instance, we will see in this chapter what the Oracle C
- PDF / 1,632,778 Bytes
- 26 Pages / 504 x 720 pts Page_size
- 92 Downloads / 208 Views
Storage We have discussed compute instances in Chapter 4. We have seen how to create a new Compute Instance, using one of the images provided by Oracle or Partner-provided images. Now that we have a Compute Instance, we will see in this chapter what the Oracle Cloud Infrastructure Storage service is, how a Compute Instance uses the boot volume, and how it can use a newly provisioned block volume to store application data. This chapter will also explore the Object Storage service and how we can manage different types of objects stored using this service. Many features are also available to manage the objects in Object Storage service, like lifecycle policy rule, replication, and retention rules.
Block and Boot Volume Since you have your compute, you will need to install your application and have a location to store the data. The Compute Instance will need to have access to persistent, secure, durable, and very performant storage, comparable to your on-premise storage network area (SAN). Also like your SAN, boot and block volume life span is independent of your Compute Instance; you can terminate your Compute Instance and decide to keep the volumes for future use. This cloud service allows you to provision, attach, connect, and move your storage depending on your needs. We describe all these steps. Let’s take the Compute Instance created in Chapter 4, which comes with a boot volume. The boot volume is, first of all, a detachable volume device that contains the image used to boot the instance. By default, the size of the boot volume is 46.6 GB which you can change during the compute provisioning process. We recommend keeping the boot volume for the OS only and not installing any applications or not storing any data on it. Applications and data should reside on dedicated block volumes so that they are completely isolated from the boot volume. We can see a couple of advantages by doing so; first, you will be able to detach the application and data block volume to © Adrian Png and Luc Demanche 2020 A. Png and L. Demanche, Getting Started with Oracle Cloud Free Tier, https://doi.org/10.1007/978-1-4842-6011-1_5
75
Chapter 5
Storage
attach it onto another Compute Instance. This could be useful if you want to move that application and its data to another instance, using a different shape or different processors. Second of all, if you have an issue with your instance and the boot volume is no longer responding, your application and the data are securely stored on the block volume, and you can easily attach the volume to another instance. As you have to install your application on a dedicated volume, you will need to first create the block volume. From the navigation menu, select “Block Storage” and “Block Volumes”, and you will be in the Block Volumes page as you can see in Figure 5-1.
Figure 5-1. Block Volumes page From this page, make sure you are in the right compartment, and click “Create Block Volume”. You will have to provide some information in order to create the block volume as you can see in Figures 5-2 and
Data Loading...
