Skip to main content

Oracle Cloud Compute Common Terms and Usage

Oracle Cloud Compute Common Terms and Usage


Oracle Cloud Compute offers a range of compute services and features for deploying and managing virtual machines and containers. Here are some key compute terms and their usage in Oracle Cloud:

Compute Instance: A compute instance is a virtual machine (VM) running in Oracle Cloud. Instances can be used for a wide range of workloads, including applications, databases, and web servers.

Availability Domain (AD): An availability domain is a physically separate data center within an Oracle Cloud region. Oracle Cloud regions consist of multiple availability domains to provide redundancy and high availability.

Virtual Machine (VM): A virtual machine is a software emulation of a physical computer, running an operating system and applications. Oracle Cloud offers various VM shapes (sizes) with different CPU and memory configurations to meet different performance needs.

Instance Shapes: Oracle Cloud provides a variety of instance shapes, each with specific CPU, memory, and network performance characteristics. Users can choose the appropriate shape based on their workload requirements.

Images: Images are pre-configured templates for creating instances. Oracle offers a range of standard images, including Oracle Linux, CentOS, Windows, and more. Users can also create custom images.

Orchestration: Oracle Cloud Compute allows you to create and manage instances using orchestration tools like Terraform and Oracle Cloud Infrastructure Resource Manager.

Instance Lifecycle: You can manage the lifecycle of instances, including provisioning, starting, stopping, restarting, and terminating (deleting) instances.

Load Balancers: Oracle Cloud provides load balancers to distribute incoming network traffic across multiple compute instances, ensuring high availability and scalability of applications.

Autonomous Database: Oracle Cloud offers Autonomous Database services, which are fully managed, self-driving databases designed for high performance, availability, and security.

Container Engine for Kubernetes (OKE): Oracle Cloud Container Engine for Kubernetes is a managed Kubernetes service that allows you to deploy, manage, and scale containerized applications using Kubernetes.

Bare Metal Compute: Oracle Cloud offers bare metal compute instances that provide direct access to physical hardware. These instances are suitable for high-performance workloads.

GPU Instances: Some Oracle Cloud instance shapes come with GPU (Graphics Processing Unit) options, which are suitable for AI/ML workloads and other GPU-intensive tasks.

Instance Console Connection: You can access the console of a running instance for troubleshooting and management tasks. Console connections are available for both Windows and Linux instances.

Instance Metadata: Instances can retrieve metadata about themselves using instance metadata. This can be useful for scripting and automation.

Instance Storage: Instances in Oracle Cloud come with local storage for temporary data. Additionally, you can attach block volumes or use file storage for persistent data.

Custom Images: You can create custom images from your running instances or imported images, allowing you to capture a snapshot of your VM's configuration and use it to create new instances.

Instance Networking: You can configure network-related settings for your instances, including assigning public and private IP addresses, configuring security groups, and defining network security rules.

Instance Scaling: Oracle Cloud provides tools for automatically scaling instances based on workload demand, such as Auto Scaling and Instance Pools.

These are some of the key compute terms and their usage in Oracle Cloud. Oracle Cloud Compute services offer flexibility, scalability, and control for deploying and managing virtual machines and containers to meet a wide range of computing needs.





If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more