As IT moves towards virtualization, cloud and hybrid environments, containers, agile developments, etc. Automation and orchestration tools are gaining popularity to build and deliver environments faster and efficiently.
In this post, I want to show how Oracle Enterprise Manager (EM) interacts with 3rd party tools and how this can be used to integrate EM’s functionality with DevOps tools like Ansible or Terraform for configuration management and automation.
Oracle Enterprise Manager (EM) offers a complete tool-set for monitoring, provisioning, upgrade and patching, consolidation, compliance, DBaaS, etc., for the Oracle Database. Oracle Enterprise Manager makes use of Plug-ins and managements packs in order to discover, monitor and manage targets. EM’s functionality can be further extended with connectors and the EM’s extensibility framework in order to interact with 3rd party tools.
You can interact with Oracle Enterprise Manager (EM) in several ways:
- Oracle Enterprise Manager Console
- Oracle Enterprise Manager Command Line Interface (EMCLI)
- Management Repository Views
- Web Service REST APIs
- Executing SQL via REST APIs (13.4 only)
We can leverage all the EMCLI commands and REST API’s that Oracle EM exposes with tools like Ansible or Terraform for a complete automation and orchestration solution.
One of the requirements for Oracle EM to monitor and manage a target is to deploy an Oracle Management Agent (OMA) to the machine hosting the target. Many organizations use DevOps tools to deploy virtual machines in an automated fashion. We can integrate the Oracle EM’s agent deployment process with these tools. This helps to drive consistency and reduces the efforts and time that administrators spend deploying Oracle Management Agents.
Let’s deploy an OMA to a Linux host using Ansible and Oracle’s EMCLI interface.
First of all, I need to download and install Ansible in a test server. My test server is a small virtual machine running Oracle Linux 7.
[root@ansible-s02 ~]# yum install -y ansible
Loaded plugins: langpacks, ulninfo
ol7_UEKR5 | 2.8 kB 00:00
ol7_addons | 2.8 kB 00:00
ol7_developer | 2.8 kB 00:00
ol7_developer_EPEL | 3.4 kB 00:00
ol7_ksplice | 2.8 kB 00:00
ol7_latest | 3.4 kB 00:00
ol7_oci_included | 2.9 kB 00:00
ol7_optional_latest | 2.8 kB 00:00
ol7_software_collections | 2.8 kB 00:00
(1/19): ol7_UEKR5/x86_64/updateinfo | 64 kB 00:00
(2/19): ol7_developer/x86_64/primary_db | 544 kB 00:00
(3/19): ol7_developer_EPEL/x86_64/group_gz | 87 kB 00:00
(4/19): ol7_developer_EPEL/x86_64/updateinfo | 6.3 kB 00:00
(5/19): ol7_addons/x86_64/updateinfo | 91 kB 00:00
(6/19): ol7_ksplice/updateinfo | 5.3 kB 00:00
(7/19): ol7_addons/x86_64/primary_db | 153 kB 00:00
(8/19): ol7_latest/x86_64/group_gz | 134 kB 00:00
(9/19): ol7_ksplice/primary_db | 964 kB 00:00
(10/19): ol7_latest/x86_64/updateinfo | 2.9 MB 00:00
(11/19): ol7_developer/x86_64/updateinfo | 7.2 kB 00:00
(12/19): ol7_UEKR5/x86_64/primary_db | 6.9 MB 00:00
(13/19): ol7_oci_included/x86_64/primary_db | 211 kB 00:00
(14/19): ol7_optional_latest/x86_64/updateinfo | 1.0 MB 00:00
(15/19): ol7_software_collections/x86_64/updateinfo | 8.7 kB 00:00
(16/19): ol7_software_collections/x86_64/primary_db | 4.9 MB 00:00
(17/19): ol7_developer_EPEL/x86_64/primary_db | 12 MB 00:00
(18/19): ol7_latest/x86_64/primary_db | 24 MB 00:00
(19/19): ol7_optional_latest/x86_64/primary_db | 4.7 MB 00:00
...
Installed:
ansible.noarch 0:2.8.4-1.0.1.el7
Dependency Installed:
python-httplib2.noarch 0:0.9.2-0.1.el7
python-paramiko.noarch 0:2.1.1-9.el7
python2-jmespath.noarch 0:0.9.4-1.el7
python3.x86_64 0:3.6.8-13.0.1.el7
python3-libs.x86_64 0:3.6.8-13.0.1.el7
python3-pip.noarch 0:9.0.3-7.el7_8
python3-setuptools.noarch 0:39.2.0-10.el7
sshpass.x86_64 0:1.06-1.el7
Complete!Ansible is now installed in the test machine. The Ansible installion will create a directory under “/etc” that contains the configuration, host inventory and roles.
[root@ansible-s02 ~]# cd /etc/ansible/
[root@ansible-s02 ansible]# ls
ansible.cfg hosts roles
Our next step is to edit the host inventory file and add both, our Oracle EM server and the machine where we want to deploy the OMA into. This will look similar to my configuration file below.
# This is the default ansible 'hosts' file.
#
# It should live in /etc/ansible/hosts
#
# - Comments begin with the '#' character
# - Blank lines are ignored
# - Groups of hosts are delimited by [header] elements
# - You can enter hostnames or ip addresses
# - A hostname/ip can be a member of multiple groups
# Ex 1: Ungrouped hosts, specify before any group headers.
## green.example.com
## blue.example.com
## 192.168.100.1
## 192.168.100.10
# Ex 2: A collection of hosts belonging to the 'webservers' group
## [webservers]
## alpha.example.org
## beta.example.org
## 192.168.1.100
## 192.168.1.110
# If you have multiple hosts following a pattern you can specify
# them like this:
## www[001:006].example.com
# Ex 3: A collection of database servers in the 'dbservers' group
## [dbservers]
##
## db01.intranet.mydomain.net
## db02.intranet.mydomain.net
## 10.25.1.56
## 10.25.1.57
# Here's another example of host ranges, this time there are no
# leading 0s:
## db-[99:101]-node.example.com
[local]
127.0.0.1
[emserver]
10.0.0.28
[emtarget]
10.0.0.11I also configured a password-less SSH connectivity between the Ansible test machine and both, the EM’s server and the server where I want to deploy the OMA into. After this, I’m going to verify the connectivity from Ansible to both servers.
[root@ansible-s02 ansible]# ansible emserver -m ping -u oracle
[WARNING]: Platform linux on host 10.0.0.28 is using the discovered Python
interpreter at /usr/bin/python, but future installation of another Python
interpreter could change this. See https://docs.ansible.com/ansible/2.8/referen
ce_appendices/interpreter_discovery.html for more information.
10.0.0.28 | SUCCESS => {
"ansible_facts": {
"discovered_interpreter_python": "/usr/bin/python"
},
"changed": false,
"ping": "pong"
}
[root@ansible-s02 ansible]# ansible emtarget -m ping -u oracle
[WARNING]: Platform linux on host 10.0.0.11 is using the discovered Python
interpreter at /usr/bin/python, but future installation of another Python
interpreter could change this. See https://docs.ansible.com/ansible/2.8/referen
ce_appendices/interpreter_discovery.html for more information.
10.0.0.11 | SUCCESS => {
"ansible_facts": {
"discovered_interpreter_python": "/usr/bin/python"
},
"changed": false,
"ping": "pong"
}
I see the SUCCESS flag on both of them. Now is time to develop my .yml file with all the necessary steps to deploy the OMA to the host.
Let’s pause for a minute and review all the available options to deploy an OMA to servers. The list below show’s these options:
- Oracle Enterprise Manager Console
- Oracle Enterprise Manager Command Line Interface (EMCLI)
- Silent Mode
- Using the AgentPull script
- Using the agentDeploy script
- Using the RPM file
I decided to use EMCLI to deploy the OMA to a host in this example. The .yml file to deploy the OMA looks like:
- hosts: emtarget
vars:
emagent_port: 3874
emagent_base: /u01/app/oracle/product/agent134c
tasks:
- name: check emagent port
wait_for: port={{ emagent_port }} state=stopped timeout=1
- name: creating base directory
file: path={{ emagent_base }} state=directory owner="oracle" group="oinstall"
tags: install
- hosts: emserver
vars:
emagent_port: 3874
emagent_base: /u01/app/oracle/product/agent134c
emagent_hostname: emtarget.oracle.com
emagent_platform_id: 226
tasks:
- name: execute emcli
command: "/u01/app/oracle/product/omshome/bin/emcli submit_add_host -host_names={{ emagent_hostname }} -platform={{ emagent_platform_id }} -installation_base_directory={{ emagent_base }} -credential_name=\"HOST_ORACLE\" -port={{ emagent_port }} -wait_for_completion"
register: result
- name: show results
debug:
var: result.stdoutNow is time to execute our Ansible Playbook.
[root@ansible-s02 ansible]# ansible-playbook emcli_deploy_agent.yml -u oracle
PLAY [emtarget] *************************************************************************************************************************************************************************************************************************************************************************************************************
TASK [Gathering Facts] ******************************************************************************************************************************************************************************************************************************************************************************************************
ok: [10.0.0.11]
TASK [check emagent port] ***************************************************************************************************************************************************************************************************************************************************************************************************
ok: [10.0.0.11]
TASK [creating base directory] **********************************************************************************************************************************************************************************************************************************************************************************************
ok: [10.0.0.11]
PLAY [emserver] *************************************************************************************************************************************************************************************************************************************************************************************************************
TASK [Gathering Facts] ******************************************************************************************************************************************************************************************************************************************************************************************************
ok: [10.0.0.28]
TASK [execute emcli] ********************************************************************************************************************************************************************************************************************************************************************************************************
changed: [10.0.0.28]
TASK [show results] *********************************************************************************************************************************************************************************************************************************************************************************************************
ok: [10.0.0.28] => {
"result.stdout": "Session Name : ADD_HOST_SYSMAN_Jun_26_2020_11:54:55_AM_EDT\nOverAll Status : Agent Deployment Succeeded\n\nHost Platform Name Initialization Remote Prerequisite Agent Deployment Error\nemtarget.oracle.com Linux x86-64 Succeeded Succeeded Succeeded "
}
PLAY RECAP ******************************************************************************************************************************************************************************************************************************************************************************************************************
10.0.0.11 : ok=3 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
10.0.0.28 : ok=3 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0Now let’s verify our agent deployment. I’m going to login to the Oracle Enterprise Manager Console and I should be able to see the details of the deployment.
Here you go! The OMA was successfully deployed to my target host. I now need to manually execute the “root.sh” script, this because I didn’t specify a privileged credential during the deployment.
Hope this helps to demonstrate the flexibility of Oracle’s EM and also as an example on how to integrate it’s functionality with DevOps tools like Ansible. This is not by any means the best way to deploy an agent for your particular environment but rather an example of how to integrate EM with Ansible.
Thanks,
Alfredo