Cisco HyperFlex

Note:

After reviewing telemetry data and conducting interviews with customers to determine use of this capability, this target was deemed appropriate to deprecate. If you replaced this technology with something that is currently not supported, submit an idea at the Cloud Management and AIOps Idea Portal. The last Turbonomic version that will contain this target is 8.15.0.

Cisco HyperFlex provides a hyperconverged platform that combines the networking and compute power of UCS with the storage capabilities of the HyperFlex HX Data Platform.

With the additional and refined storage information provided by HyperFlex, Turbonomic narrows the Desired State and recommends actions using the joint compute and storage information, gaining valuable insight into the interconnected nature of your environment.

For Turbonomic to make the most informed decisions, you must also add the compute nodes and any associated hypervisors. HyperFlex environments typically include:

  • Converged (HX) Nodes

    A combination of the cluster's storage devices into a single multi-tiered, object-based datastore.

  • Compute Nodes

    Cisco B or C series servers that make up the compute resources of the cluster, and are typically managed by a hypervisor.

  • Controller VMs

    Each HyperFlex node includes a Controller VM that intercepts and handles all the I/O from associated virtual machines. Turbonomic will not recommend actions for these VMs.

Prerequisites

  • Cisco HyperFlex 3.5

  • A service account on the controller VM that Turbonomic can use to connect to the HyperFlex environment

Adding HyperFlex targets

  1. Click Settings > Target Configuration.

  2. Click New Target > Hyperconverged.

  3. Select Cisco HyperFlex.

  4. Configure the following settings:

    • Address

      The name or IP address of the HyperFlex controller VM. If a port is appended to the IP address, it must be a secure (HTTPS) port.

    • Username/Password

      Credentials for a user account Turbonomic will use to connect to the controller VM.

      To specify a root user for the target, give the name as local/root. Note that earlier versions of Turbonomic accepted a username of root. If an existing HyperFlex target fails to validate after you have upgraded Turbonomic, then check to make sure the username for a root account is properly set to local/root.

      If you use vSphere SSO for authentication to the HyperFlex target, you must prepend your username with vc-. For example, if your username is Administrator@vsphere.local, you would enter it as vc-Administrator@vsphere.local.

    • Port Number

      Port Number Turbonomic will use to connect to the controller VM.

Entity mapping

After validating your targets, Turbonomic updates the supply chain with the entities that it discovered. The following table describes the entity mapping between the target and Turbonomic.

HyperFlex Turbonomic
Volume Storage
HX Cluster Disk Array

HyperFlex targets add Disk Array entities to the supply chain, and receive more granular information from the compute resources in your environment.

Monitored resources

Turbonomic monitors the following resources:

  • Storage

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

    • Storage provisioned

      Storage provisioned is the utilization of the entity's capacity, including overprovisioning.

    • Storage access (IOPS)

      Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

      Note:

      When it generates actions, Turbonomic does not consider IOPS throttling that it discovers on storage entities. Analysis uses the IOPS it discovers on Logical Pool or Disk Array entities.

    • Latency

      Latency is the measurement of storage latency.

  • Disk Array

    • Storage amount

      Storage amount is the measurement of storage capacity that is in use.

    • Storage provisioned

      Storage provisioned is the utilization of the entity's capacity, including overprovisioning.

    • Storage access (IOPS)

      Storage access, also known as IOPS, is the per-second measurement of read and write access operations on a storage entity.

    • Latency

      Latency is the measurement of storage latency.

Actions

Turbonomic supports the following actions:

  • Storage

    • Move

      This action can only be executed outside Turbonomic.

    • Provision

      This action can only be executed outside Turbonomic.

    • Resize Up

      This action can only be executed outside Turbonomic.

  • Disk Array

    • Provision

      This action can only be executed outside Turbonomic.

    • Suspend

      This action can only be executed outside Turbonomic.

    • Resize Up

      This action can only be executed outside Turbonomic.

Note:
For this target, Turbonomic discovers the HX Cluster as a Disk Array. When you see a provision action on this entity, you should determine which of the following is most relevant, based on your environment:
  • Add disks to converged nodes

  • Add a new converged node

  • Add a new HX Cluster