Turbo Tip: Adding Nutanix Targets

Document created by anson.mccook Expert on Dec 3, 2015Last modified by fran.schwarzmann on Aug 15, 2016
Version 4Show Document
  • View in full screen mode

5.3 introduces support for Nutanix  platforms where the Operations Manager supply chain treats the Nutanix Storage Pool as a disk array. In addition, Operations Manager discovers the hypervisors running on the Nutanix platform, and adds them to the supply chain for analysis and control.

 

There are two modes for Nutanix support in Operations Manager:

  • Stand-Alone
    In this mode, the platform uses Nutanix Acropolis to collect compute information

 

  • Generic Hypervisor
    In this mode, the platform uses 3rd-Party hypervisors to collect compute information and connect to the Nutanix Controller for additional storage information. For example, in this mode your platform could use VMware vSphere or Microsoft Hyper-V hypervisors. This mode requires the Supply Control Module to be licensed.

 

Generic Mode (Nutanix with VMware/Hyper-V)

If you are running in "Generic Mode" then you can simply add your Nutanix controller by navigating to Target Configuration > Storage > Nutanix

After a "Rediscovery," the platform will treat Nutanix as a disk array and populate in the Inventory view as such. Additionally, Operations Manager considers utilization of "HotStorage" (server-attached flash) to calculate VM placement that uses server flash efficiently and with assured performance. In addition, Operations Manager can recommend actions to scale flash capacity up or down by adding more hosts to the cluster, or more flash drives to the hosts.

 

 

Stand-Alone Mode (Nutanix with Acropolis)

Download the Operations Manager qcow2 file for Acropolis here: Download VMTurbo

Use the Acropolis Image Service to deploy VMTurbo. The following document outlines how to deploy a qcow2 file using the Image Service.

Acropolis Image Service

 

Follow the instructions below if you are running Acropolis.

 

The assumed Nutanix hypervisor is either vSphere or Hyper-V. For those using Acropolis, a small modification needs to be made to the targets configuration file. This tells VMTurbo that Nutanix is operating in "standalone mode" - meaning, you are running on Acropolis and all performance information should be pulled in through the Prism APIs.

 

1) Add the Nutanix target(s) to the user interface – use the IP of a controller VM. Go to the Admin Tab > Workflows > Target Configuration > Add > Storage > Nutanix

2) SSH into the VMTurbo appliance – credentials are root/vmturbo

3) Take a backup of the targets file

 

cp /srv/tomcat/data/config/disc.config.topology /srv/tomcat/data/config/disc.config.topology.old

 

4) Find target in targets file that says “NutanixTarget” in the “xsi:type” :

 

vi /srv/tomcat/data/config/disc.config.topology

 

<targets xsi:type="nutanix:NutanixTarget" uuid="_pRSdsFheEeWgpfmffIwmXw" name="VMTTarget_10.10.64.88" displayName="10.10.64.88" nameOrAddress="10.10.64.88" timeout="30000" template="_2kieMIMcEeCC5PhGZd6dJj"

lastValidationStatus="Validated" lastValidationDescription="Validated" lastValidationTime="2015-09-11T08:25:22.590+0000">

<credentials xsi:type="Mediation:UsernamePassword" uuid="_pRSdsVheEeWgpfmffIwmXw" derived="false" username="admin1" password=“xxxx" encrypted="true"/>

</targets>

 

5) Edit the “template” field of this target, and change the last character of that string to be “i” instead of “j”:

 

<targets xsi:type="nutanix:NutanixTarget" uuid="_pRSdsFheEeWgpfmffIwmXw" name="VMTTarget_10.10.64.88" displayName="10.10.64.88" nameOrAddress=“10.10.64.88" timeout="30000" template="_2kieMIMcEeCC5PhGZd6dJi"

lastValidationStatus="Validated" lastValidationDescription="Validated" lastValidationTime="2015-09-11T08:25:22.590+0000">

<credentials xsi:type="Mediation:UsernamePassword" uuid="_pRSdsVheEeWgpfmffIwmXw" derived="false" username="admin1" password=“xxxx" encrypted="true"/>

</targets>

 

This changes the probe used from “Nutanix” to “NutanixProbe Standalone"

 

6) Now, restart tomcat to re-read this file:

 

service tomcat restart

 

7) You should now be able to see the Nutanix infrastructure:

1 person found this helpful

Attachments

    Outcomes