Skip to main content

Oracle Cloud OS Management Service: Simplifying and Streamlining OS Management on OCI Compute

Oracle Cloud OS Management Service: Simplifying and Streamlining OS Management on OCI Compute




The Oracle Cloud OS Management Service is a powerful tool designed to streamline the management of operating systems (OS) on virtual machines in Oracle Cloud Infrastructure (OCI). This service provides administrators with the ability to automate tasks related to OS updates, patching, configuration, and monitoring. In this article, we will delve into the features, benefits, and step-by-step guide to setting up the Oracle Cloud OS Management Service.

Features and Benefits:


Automated OS Updates: The service automates the process of applying updates, security patches, and bug fixes to your VM instances.
Centralized Management: Administrators can manage OS updates and patches across multiple VM instances from a single, centralized location.
Configurable Policies: Define policies to control when and how updates are applied to VM instances.
Security Enhancement: Keep your VM instances up to date with the latest security patches to mitigate vulnerabilities.
Consistency: Ensure that all VM instances are running the same patched and up-to-date OS version.
Patch Rollback: If a patch causes issues, easily roll back to a previous state using the service.
Compliance Monitoring: Monitor the compliance of VM instances with defined patching policies.
Reporting: Detailed reports provide insights into the status of OS updates and patching across your environment.

Note:OS Management will not work for Always free instances

Setting Up Oracle Cloud OS Management Service:

 Prerequisites:

An active Oracle Cloud Infrastructure (OCI) account.
Virtual Machine instances running on OCI.


1) Create a dynamic group that will be used select all the instances from a compartment


Follow below screenshot to create dynamic group.






I am going to create a dynamic group to allow any instances in a compartment "gold1_compartment"

For this I will capture the compartment OCID .




2) Edit the policy statement-For an instance to be registered with the OS Management service, you must create policies that allow instances to use OS Management.

I have created a new policy with below rules in root compartment

Allow Service osms to read instances in tenancy
Allow dynamic-group LINUX_OS_GRP to read instance-family in compartment gold1_compartment
Allow dynamic-group LINUX_OS_GRP to use osms-managed-instances in compartment gold1_compartment




3) Now to to Compute instance in respective compartment and enable the OS management.





4) On the Instance resource go to the OS management tab to view all the specific bug, patches, updates available.


Run below to validate if agent is installed.

sudo yum info oracle-cloud-agent

Or install using

sudo yum install -y oracle-cloud-agent


Run below validate agent running status

[root@ ~]# sudo systemctl status oracle-cloud-agent
● oracle-cloud-agent.service - Oracle Cloud Infrastructure agent for management and monitoring
   Loaded: loaded (/etc/systemd/system/oracle-cloud-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2023-08-24 16:40:59 GMT; 2min 0s ago
     Docs: https://docs.cloud.oracle.com/iaas/
 Main PID: 2153 (agent)
    Tasks: 70 (limit: 5418)
   Memory: 212.2M
   CGroup: /system.slice/oracle-cloud-agent.service
           ├─2153 /usr/libexec/oracle-cloud-agent/agent
           ├─2277 /usr/libexec/oracle-cloud-agent/plugins/gomon/gomon
           ├─2378 /usr/libexec/oracle-cloud-agent/plugins/oci-managementagent/oci-managementagent
           ├─2409 /usr/libexec/oracle-cloud-agent/plugins/oci-wlp/oci-wlp
           ├─2461 /bin/bash 230727.1916/bin/oracle.polaris.oca.main -Xmx128m -Dpolyglot.engine.AllowExperimentalOptions=true -Dpo>
           └─2463 /var/lib/oracle-cloud-agent/plugins/oci-managementagent/polaris/jdk1.8.0_381-b09/bin/java -Djava.security.egd=f>



5) Now  we can see the Available OS updates from OS management on console for the instance.







6) If we check at the server level and use the standard method to update OS. We can seen message saying it is receiving updates by OSMS agent.

But still if we want we can use the OS management tools to patch and update.



7)  Now what if we update from OS level updates.


yum update -y 

Now after the update we can review OS management console and it will mark all as update no available updates as it was already installed using yum utility.




So we can use both method to update our OS. So it is based on your needs and convenience. OS management will help you to patch group of OS system as needed and required at the same time. It can be achieved by creating Managed Instance Groups.





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

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...
Post a Comment
Read more