IT Operations Management (ITOM)
Showing results for 
Search instead for 
Do you mean 

AIRVA: A new way to install the HPE Operations Agent!

HaraldPfaender ‎04-11-2016 04:27 AM - edited ‎04-11-2016 02:17 PM

A software repository is a central location where all kind of software is packaged. You can use it to search, list, download and install packages easily, either via command line or user interface. If you’re using Linux, you should already be familiar with it. RedHat or CentOS Linux, for example, use "yum" as their package manager. Other Linux flavors and even Windows provide similar package repositories and managers. It is obvious that this mechanism simplifies the installation and maintenance of software. The package manager automatically selects the correct version for your platform and also handles the installation of updates.

Wouldn't it be nice to have the HPE Software integrated in this package repository? This would give all the advantages I listed above, i.e., simpler installation and maintenance. And the good news is: There is now a repository solution available for the HPE Operations Agent. It’s part of the new release of the HPE Operations Agent 12.

 p__1_oa_12.png

The HPE Operations Agent 12 is bundled with an installation repository from where you can download, install and upgrade the agent binaries. This repository can be integrated as a 3rd party repository via yum.

What is AIRVA?

AIRVA stand for Agent Installation Repository Virtual Appliance. The HPE Operations Agent 12 ships as an appliance, including agent packages version 11 and version 12. It can be integrated via the yum package repository and includes a puppet automation. The AIRVA provides the same advantages as described above: a central location for Operations Agent binaries. With this, yum will automatically pick the correct Operations Agent files. In case the Operations Agents binaries are updated in the repository, they can be pulled automatically via the yum package manager.

Are you using another package repository or Windows? No problem! There is a script available for use with Linux or Windows. With this you can download and update the Operations Agent automatically.

AIRVA—let's go:

Here are the steps to setup an AIRVA from the vSphere console:

    • Login to vCenter using vSphere client.
    • Click File > Deploy OVF Template. The Deploy OVF Template window opens.
    • Provide the source location to download and install the OVF Package and then click Next.
    • Verify the OVF Template details and click Next.
      p__10a_va_deplo1.png
    • Accept the end user license agreement and click Next.
    • Specify a name and location for the deployed template and click Next.
    • Select a destination storage for the virtual machine files click Next.
  • Provide the network properties details such as Default Gateway, DNS, Interface IP Address and the Netmask and then click Next.
    p__10b_va_deplo2.png
     
  • Click Finish to start the deployment.

That is all. The deployment will start and afterwards your system is ready to go!

 

Verification:

Once the AIRVA is up and running you should see a landing page
https://<system_name or ip>:5480/oarepo/

p__20_LandingPage1.png

If you can see the landing page your system was successfully deployed.

Hint: The landing page is the place where you can start downloading scripts and agent packages.

 

Configuration:

In case you need to change or verify the system setting please use the following link:

https://<system_name or ip>:5480

p__30_airva_config1.png

In addition I would advise you to change the default password after deployment. Please login to the machine as soon as you have provisioned it and change it!

Hint: Looking for the default password -> it is mentioned in the manuals (and I am not repeating it here...)

 

Yum integration:

p__40_landingpage_yum1.png

To integrate AIRVA with the yum package manager you need to:

  • download the yum configuration file and
  • install the HP Keys

Download the yum repo and copy it into the yum repo

p__40_landingpage_yum2.png

# cp /home/harald/Downloads/yum_oa_all.repo /etc/yum.repos.d/

Download the rpm key to allow packages to be installed from the AIRVA:

# cp /home/harald/Downloads/hpPublicKey2048.pub /etc/pki/rpm-gpg/

Update the repo to see the updated packages: # yum update

Loaded plugins: fastestmirror, langpacks oa_11.14                                     | 2.9 kB 00:00:00
oa_12.00                                     | 2.9 kB 00:00:00  
oa_OALIN_00032                               | 2.9 kB 00:00:00  
(1/3): oa_11.14/x86_64/primary_db           | 18 kB 00:00:00  
(2/3): oa_12.00/x86_64/primary_db         | 18 kB 00:00:00  
(3/3): oa_OALIN_00032/x86_64/primary_db     | 17 kB 00:00:00 
 
 

HPE Operations Agent installation:

Now it is time to install the Operations Agent. Please do not forget to accept importing the GPG key during installation.

# yum install HPOvOpsAgt
Dependencies Resolved

=============================================================================================
Package               Arch             Version                Repository           Size
=============================================================================================
Installing:
HPOvOpsAgt             x86_64           12.00.078-1             oa_12.00           904 k
Installing for dependencies:
HPOvAgtLc             x86_64           12.00.078-1             oa_12.00           3.6 M
HPOvBbc               x86_64           12.00.078-1             oa_12.00           3.4 M
HPOvConf               x86_64           12.00.078-1              oa_12.00           2.1 M
HPOvCtrl               x86_64           12.00.078-1             oa_12.00           1.5 M
HPOvDepl               x86_64           12.00.078-1             oa_12.00           2.6 M
HPOvEaAgt             x86_64            12.00.078-1             oa_12.00             17 M
HPOvGlanc             x86_64           12.00.078-1             oa_12.00           3.5 M
HPOvPacc               x86_64           12.00.078-1             oa_12.00           1.5 M
HPOvPerfAgt           x86_64           12.00.078-1             oa_12.00             10 M
HPOvPerfMI             x86_64           12.00.078-1             oa_12.00           6.1
HPOvPerlA             x86_64           5.16.009-1               oa_12.00            13 M
HPOvSecCC             x86_64           12.00.078-1             oa_12.00           5.4
HPOvSecCo             x86_64           12.00.078-1             oa_12.00           4.6
HPOvXpl               x86_64           12.00.078-1             oa_12.00           3.2

Transaction Summary
=============================================================================================
Install 1 Package (+14 Dependent packages)

Total download size: 78 M
Installed size: 236 M
Is this ok [y/d/N]:

Downloading packages:

warning: /var/cache/yum/x86_64/7/oa_12.00/packages/HPOvSecCC.rpm: Header V3 RSA/SHA1 Signature, key ID b564a643: NOKEY

Retrieving key from file:///etc/pki/rpm-gpg/hpPublicKey2048.pub
Importing GPG key 0x5CE2D476:
Userid     : "Hewlett-Packard Company RSA (HP Codesigning Service)"
Fingerprint: 476d adac 9e64 7ee2 7453 f2a3 b070 680a 5ce2 d476
From       : /etc/pki/rpm-gpg/hpPublicKey2048.pub
Is this ok [y/N]:

Afterwards, the HPE Operations Agent is installed.

Hint: In order to have the Agent up and running, it needs to be configured. That means you need to point it to an Operations Manager server (see the next step: Agent configuration).

 

Agent configuration:

In order to allow the HPE Operations Agent communicate with your server you need to activate it. You can activate the agent with the following commands:

# cd /opt/OV/bin/OpC/install
# opcactivate -srv <management_server> -cert_srv <management_server> -f

<management_server> is the FQDN of the Operations Manager server.

 

Puppet integration:

The AIRVA also comes with a puppet integration which I will not cover in this blog. For details, please refer to the manuals.

 

Installation via script:

The installation via script can be used on Windows or Linux. On Linux, I would recommend integrating AIRVA via yum, so I’m going to describe the installation on Windows.

p__50_landingpage_install_via_script.png

Firstly, download the Windows script from the AIRVA landing page.

Second, open a powershell command prompt (as Administrator) and execute the script:

./oarepo.ps1 -i -s <https://hostname:portnumber> -unsec -om <management_server>

p__60_airva_windows_script.png

This will download, install and activate the agent. No need to do anything else. Just wait a few seconds and you should see the agent is installed and configured. The only thing left is to accept the certificate request on your Operations Manager server.

Hint: The installation via script will also activate the agent if you provide the -om <management_server> parameter.

 

Conclusion:

The new AIRVA, which is part of the HPE Operations Agent 12, makes it easy to install, update and maintain agent binaries. Just include AIRVA in your software repository. It is easy and simple. Once set up, your Operations Agent can be kept automatically up-to-date in the same way as all your software. Using Windows or puppet? No problem! Just use the scripts supporting these integrations Very cool!

Try it out now:

 

Feedback:

What do you think about HPE Operations Agent 12? Please share your thoughts and comments!

 

p__100_Discover-2016-LV-blog-banner.jpg

About the Author

HaraldPfaender

Comments
Raymond Meijer
on ‎04-12-2016 01:28 AM

Very nice indeed! Will it be possible to deploy Hotfixes this way as well?

HaraldPfaender
on ‎04-13-2016 01:59 AM

Hello Raymond,

thanks for your comment. With the current version I was not able to deploy the hotfixes.

Kind regards,
Harald

Events
June 6 - 8, 2017
Las Vegas, Nevada
Discover 2017 Las Vegas
Join us for HPE Discover 2017 in Las Vegas. The event will be held at the Venetian | Palazzo from June 6-8, 2017.
Read more
Apr 18, 2017
Houston, TX
HPE Tech Days - 2017
Follow a group of tech bloggers for a new HPE Tech Day, a full day of sessions about how to create a hybrid IT, from hyperconverged to Composable Infr...
Read more
View all
//Add this to "OnDomLoad" event