Managing private cloud providers

Last updated 28 November, 2018

About private cloud providers

A cloud service provider makes cloud services available for deploying virtual machines.

In HPE OneSphere, you can connect to the following private cloud providers:

  • VMware vCenter/ESXi

  • KVM 

A HPE OneSphere private cloud provider is used for the initial connection between HPE OneSphere and your VMware ESXi or KVM environment.

A provider contains a region and one or more zones.

  • A region describes the geographic location of the data center or server in which the HPE OneSphere virtual machine is deployed.

  • A zone is a specific VMware vCenter datacenter or set of KVM servers.

Connecting, or adding, a private cloud provider allows you to:

  • Create, view, update, and delete infrastructure (virtual machines, storage, and networking).

  • Automatically import VMware templates and KVM images to the Catalog.

  • Collect resource usage data for display on the Providers screen.

  • (VMware ESXi only) Collect cost data for display on the Insights screen.

About resource usage in private cloud providers

When managing a hybrid cloud, you will want to understand and manage the utilization of your cloud resources.

HPE OneSphere provides you with cloud analytics, which is information about your hybrid cloud consumption. Cloud analytics tell you who is using how much of which services.

Understanding resource usage from the Providers screen

On the Providers screen, under Private Zones, you can select a private cloud provider to see utilization and performance information about virtual machine deployments and hosts.

  • Click on your private cloud provider name to see scores for the virtual machine hosts in the provider.

  • After selecting the private cloud provider, view details about the score.

Each graph shows a score from 0 to 1000, where 1000 is the highest score. The score is an abstract value that represents the relative state of the virtual machine deployment. Clicking an individual category in the bar graph displays details specific to each category. Click the information icon  to display more information about the Rating Breakdown.

NOTE:

Resource usage metrics for private cloud providers can take up to an hour to appear.

  • Rating

    Overall score computed from the Availability, Utilization, and Performance scores. The score is weighted as follows:

    • Availability: 50%

    • Utilization: 30%

    • Performance: 20%

  • Availability

    Score computed from the proportion of time that the virtual machine or host is available for use.

  • Utilization

    The score is measured against the target utilization rate of 75%. A high score means you are using a large percentage of the target utilization.

    • Private cloud: Number of CPU cores used out of the total number of cores, the amount of RAM used, and the amount of storage used.

  • Performance

    For private clouds, the score computed from the number of network errors divided by the total number of packets sent, and the number of dropped packets divided by the total number of packets sent.

Adding a zone to your private cloud provider

Use the following procedure to add a zone in HPE OneSphere to connect to your existing private VMware ESXi or KVM environment. You can then deploy virtual machines from HPE OneSphere to a VMware vCenter cluster or KVM hypervisor(s) in a specified region.

You use the HPE OneSphere Connect application to create a zone to connect to your VMware or KVM environment for the first time. You use the same application to add additional zones to your private cloud environment.

Prerequisites

The administrator configured a VMware vCenter or KVM environment for use with HPE OneSphere.

For detailed configuration and prerequisites information, see Network configuration for HPE OneSphere Connect, Network configuration for KVM servers, and the HPE OneSphere Support Matrix.

Procedure
  1. Launch the HPE OneSphere URL in a supported web browser.

    The HPE OneSphere URL and login information is provided in an email sent by Hewlett Packard Enterprise after your account has been created. If you do not have this information, contact your Hewlett Packard Enterprise representative.

  2. Enter the administrator username provided by Hewlett Packard Enterprise to log in to your HPE OneSphere account. For more information, see Setting up your account and managing users.
  3. From the HPE OneSphere main menu, select Providers.
  4. From the Providers screen, select Private Zones.
  5. From the Private Zones screen, click the green plus icon.
  6. Click the following option on the Create Zone panel.

    Create from existing Virtualized Environment

    Connect existing VMware clusters or KVM servers that are already in use outside of HPE OneSphere.

  7. Click Download Connect for Windows or Download Connect for Mac.
  8. Save the HPE OneSphere Connect file for Windows (HPE-OneSphere-Connect-1.0.0-(x)-win.zip) or Mac OS X (HPE-OneSphere-Connect-1.0.0-(x)-mac.zip). The size of the zip file is approximately 32 MB.
  9. After saving the HPE OneSphere Connect file, you can use it to connect to your VMware vSphere private cloud or connect to your KVM private cloud.

Using HPE OneSphere Connect to add a new zone in your VMware vSphere private cloud

Use the following procedure to add a new zone in your VMware vCenter ESXi environment.

Prerequisites
  • An account on the HPE OneSphere portal with administrator privileged access

  • The administrator:

    • Added a private cloud zone from the Create Zone screen in the HPE OneSphere web portal

    • Downloaded the HPE OneSphere Connect .zip file from the Create Zone screen in the HPE OneSphere portal, and extracted the .exe or .app file

    • Deleted any existing VMware private cloud zones that are using Nova networking. Upgrading a VMware zone from Nova networking to Neutron networking is not supported.
Procedure
  1. Launch the HPE OneSphere Connect .exe or .app file.

    HPE OneSphere Connect is downloaded from the HPE OneSphere Create Zone screen.

  2. Click Get Started.
  3. In HPE OneSphere Account, enter the HPE OneSphere portal URL provided by Hewlett Packard Enterprise, then click Continue.

    Example: https://[your-account].hpeonesphere.com

  4. Sign in using the username and password for your HPE OneSphere Account.
  5. On the Infrastructure Location in HPE OneSphere screen:
    1. Click the Region drop-down list and select an existing region.
    2. Click the Type of Zone drop-down list and select the zone type.
    3. Click the Private Zone drop-down list and select the existing zone.

    Or, create a new region by selecting Create New Region, then enter the following details.

    1. Enter a name for the region where your VMware environment is located, for example, US-Denver.

      NOTE:

      The region name cannot contain spaces, and it cannot contain more than 18 characters.

    2. Drag the dot on the map to the approximate location of your private cloud.
    3. Click the Type of Zone drop-down list and select the zone type, such as vCenter.
    4. Enter a name for the name of the zone, for example, ESXi-US-Zone.

      NOTE:

      The zone name cannot contain underscores and spaces, and it cannot contain more than 18 characters.

  6. Click Continue.
  7. On the vCenter Sign-In screen, enter the vCenter hostname or IP address and the vCenter login credentials for the account that manages your VMware ESXi private cloud platform. If you plan to connect multiple datacenters, then specify datacenter Administrator credentials. 

    See Required permissions for VMware vSphere user accounts and ensure that the vCenter administrator or datacenter administrator account is assigned the required permissions.

    NOTE:

    Ensure that the vCenter cluster is created outside of a folder in vSphere. If the cluster is already created inside of a folder, move the cluster outside of the folder before enabling the cluster. (You enable the cluster after connecting it to HPE OneSphere.)

    HPE OneSphere currently supports connecting to a vCenter Server that is configured with port 443 only.

  8. Click Sign In.
  9. On the vCenter VM Location screen, enter a name for the HPE OneSphere Controller virtual machine instance to be deployed, and select the cluster, shared datastore, and network where the virtual machine instance will be deployed.

    Hewlett Packard Enterprise recommends connecting the HPE OneSphere Controller virtual machine to a VMware vSphere Distributed Switch (VDS)-based portgroup network that has connectivity to the Internet and the vCenter server, and is isolated from the portgroup network used for deployment of virtual machines. This virtual machine establishes a secure https communication channel between your vCenter private cloud platform and the HPE OneSphere cloud management service.

  10. On the vCenter vSphere Data Network screen, select vSphere Distributed Switch from the drop-down list and select the vSphere Distributed Switch that is connected to all hosts within a vCenter datacenter. The port groups on the selected VDS are imported as networks in HPE OneSphere and will be used for VM deployments. 

    NOTE:

    HPE OneSphere Connect lists all the vSphere Distributed Switches available in the vCenter. Log in to vCenter and note the name of the VDS for the specified datacenter before selecting it on the vCenter VM Location screen.

  11. Click Continue.
  12. On the HPE OneSphere Controller screen, configure the network settings of the virtual machine so that the virtual machine in the vCenter can communicate with HPE OneSphere.
    1. Click the IP address assignment drop-down list and select the IP address assignment type (DHCP or Static) depending on your requirements. If you select Static, enter the network details including IP address, Subnet mask, Gateway, and DNS server.
    2. Enter a proxy to establish a connection between the vCenter and HPE OneSphere. (Do not enter the system proxy, which is configured from your local Windows client PC to other networks.)
  13. Click Continue.
  14. On the HPE Private Cloud Infrastructure Connection Summary screen, review the connection details.
    1. To change any information, click Back (green return icon at the top left corner) of the Summary screen and edit the information before connecting.
    2. If the displayed information on the Summary screen is correct, click Connect.

      NOTE:

      Do not close the Connect screen during this operation.

The page navigates to Connecting all the bits for your HPE Private Cloud. The progress bar provides the percentage of time taken to establish a connection between vCenter and HPE OneSphere.

If any errors occur during this onboarding process, see the log file for more information. In Windows, the HPE OneSphere Connect log file is located in C:\Users\<windowsLoginusername>\hpeConnect. In macOS, the log file is located in %userprofile%\HPEconnect\HPEconnect.log.

After a successful connection, You're all set! screen appears. Click Take me there to proceed to the HPE OneSphere application log in screen; otherwise, click Connect another environment to establish a new connection.

Using HPE OneSphere Connect to add a new zone in your KVM private cloud 

Use the following procedure to connect HPE OneSphere to an existing KVM environment.

Prerequisites
  • An account on the HPE OneSphere portal with administrator privileged access

  • The administrator:

    • Added a private cloud zone from the Create Zone screen in the HPE OneSphere web portal

    • Downloaded the HPE OneSphere Connect .zip file from the Create Zone screen in the HPE OneSphere portal, and extracted the .exe or .app file.

Procedure
  1. Launch the HPE OneSphere Connect .exe or .app file.

    HPE OneSphere Connect is downloaded from the HPE OneSphere Create Zone.

  2. Click Get Started.
  3. In HPE OneSphere Account, enter the HPE OneSphere portal URL provided by Hewlett Packard Enterprise, then click Continue.

    Example: your-account.hpeonesphere.com

  4. Sign in using the administrator username and password for your HPE OneSphere Account.
  5. On the Infrastructure Location in HPE OneSphere screen, click the Region drop-down list and create a new region by selecting Create New Region, or enter an existing region. Enter the following details.
    1. Enter a name for the region where your KVM hypervisor is located, for example, US-Denver.
    2. Drag the dot on the map to the approximate location of your private cloud.
    3. Click the Type of Zone drop-down list and select the zone type, such as KVM.
    4. Enter a name for the name of the zone, for example, KVM-US-Zone.
    5. Click Continue.
  6. On the KVM Sign-In screen, enter the following details.
    1. Enter the KVM hostname or IP address and the KVM login credentials for the account that manages your KVM private cloud platform.
    2. Enter the proxy details to establish a connection between the KVM hypervisor and HPE OneSphere 

      NOTE:

      Do not enter the system proxy, which is configured from your local Windows client PC to other networks.

  7. Click Sign In.
  8. On the HPE Private Cloud Infrastructure Connection Summary screen, review the connection details.
    1. To change any information, click Back (green return icon at the top left corner) of the Summary screen and edit the information before connecting.
    2. If the displayed information on the Summary screen is correct, click Connect 

      NOTE:

      Do not close the Connect screen during this operation.

The page navigates to Connecting all the bits for your HPE Private Cloud. The progress bar provides the percentage of time taken to establish a connection between KVM hypservisor and HPE OneSphere.

If any errors occur during this onboarding process, see the log file for more information. In Windows, the HPE OneSphere Connect log file is located in C:\Users\<windowsLoginusername>\hpeConnect. In macOS, the log file is located in %userprofile%\HPEconnect\HPEconnect.log.

After a successful connection, You're all set! screen appears. Click Take me there to proceed to the HPE OneSphere application log in screen; otherwise, click Connect another environment to establish a new connection.

Updating, connecting, and deleting a private zone

From the Update Zone screen, you can change, configure, or delete your private zone.

Prerequisites

The administrator ran HPE OneSphere Connect to connect or create a zone.

Before deleting an ESXi private zone, the administrator disabled all VMware clusters in the zone.

Procedure
  1. From the HPE OneSphere main menu, select Providers.
  2. From the Providers screen, select Private Zones.
  3. From the Private Zones screen, select the name of the zone you want to update.
  4. Select the Update Zone link.
  5. Update the zone by performing one or more of the following steps.

    For VMware ESXi

    1. Connect or disable the connection to clusters in the zone.

      To enable all clusters in the zone, enable the Connect All Available Clusters slider button.

      To enable specific clusters in the zone, enable the specific cluster slider button.

    2. Enable the Customize Cost Model slider button.

      Replace one or more default values (shown in gray) with the costs for your environment. If you do not customize the cost model, costs are calculated based on the values in a Small sample HPE Synergy Bill of Materials (BOM) configuration.

      You can change Annual Fixed Cost, vCPU (per core rate/hour), Memory (per GB rate/hour), and Disk (per GB rate/hour).

    For KVM

    1. From Server Connection, connect or disable the connection to the available servers in the zone.

      To enable all servers in the zone, enable the Connect All Available Servers slider button.

      To enable specific servers in the zone, enable the specific server slider button.

    2. From Enable services, select a server to authorize the service.

      Select the server from the drop-down list on which to enable the Image library registry for storing images.

      Select the server on which to enable the Block storage role.

      NOTE:

      By default, Ceph (block storage) is enabled for KVM servers.

      See Configuring Ceph storage.

  6. Click Update Zone.
  7. To delete the zone, click the trash icon , then confirm the deletion by clicking Yes, Delete Zone.

    IMPORTANT:

    Deleting a zone is not reversible.

    This action deletes the zone from the HPE OneSphere portal; virtual machines and data in the KVM or VMware vCenter environment are not deleted. However, if you subsequently connect to the same server or cluster to HPE OneSphere again, the existing virtual machines are not discovered and are not displayed in the HPE OneSphere portal.

    After deleting a zone, manual cleanup is required.

    • In VMware vCenter, remove the HPE OneSphere Controller appliance.

    • In a KVM environment, remove the components from KVM-enabled nodes.

Disabling KVM servers

HPE OneSphere allows you to disable a KVM server that has been enabled in HPE OneSphere.

Disabling a KVM server does not delete any virtual machines or data. The virtual machines running on that KVM server are removed from HPE OneSphere. If you subsequently re-enable the KVM server, the existing virtual machines are not discovered and are not displayed in the HPE OneSphere portal.

There are three different ways to disable the server based on your environment.

Disabling a server without any role

Navigate to the Provider > Private Zones > Update Zone screen. Under Server Connections, disable the slider button for the KVM server you want to disable. Once the server is disabled, log in to the disabled server and remove the disabled server.

Disabling a server with the ImageLibrary role enabled

The following will occur:

  • Images will no longer be available for VM provisioning

  • New VM deployments will be disabled until you assign the ImageLibrary role to a new

    KVM server

  • Any VMs created using snapshots from the Image Library will experience issues

  • Stale entries of the images on the disabled server will be listed in the HPE OneSphere Catalog page

Prerequisites

The administrator:

  • Connected HPE OneSphere to a KVM private cloud

  • Enabled the server from the HPE OneSphere Private Zones > Update Zone screen

Procedure
  1. Log in to any Ubuntu machine where the OpenStack client is installed.
  2. Get and export the environment variables. Export the environment variables under the os-rc section.
    <Portal URL>/rest/zone/<zoneid>/os-endpoints

    Example:

    https://kvm.test.net/rest/zones/24ed0c36-95b2-4da5-a721-5333927ef852/os-endpoints

    Output similar to the following will appear.

    Status: 200
    {
      "os-endpoints": [
        "https://kvm-zone-ncs.test.net/nova",
        "https://kvm-zone-ncs.test.net/neutron",
        "http://xxx.xx.xx.xxx:9292",
        "https://kvm-zone-ncs.test.net/cinder",
        "https://ncsqekvm-du.test.net/keystone"
      ],
      "os-rc": [
        "export OS_AUTH_URL=https://kvm-zone-ncs.test.net/keystone/v3",
        "export OS_IDENTITY_API_VERSION=3",
        "export OS_REGION_NAME=kvm-zone-ncs",
        "export OS_USERNAME=<username>",
        "export OS_PASSWORD=<password>",
        "export OS_PROJECT_NAME=service",
        "export OS_PROJECT_DOMAIN_ID=${OS_PROJECT_DOMAIN_ID:-'default'}",
        "export OS_USER_DOMAIN_ID=default"
      ]
    }
    
  3. Delete each image from the catalog.
    glance image-delete <id or name>
  4. Log in to the HPE OneSphere portal.
  5. Navigate to the Provider > Private Zones > Update Zone screen. Under Server Connections, disable the slider button for the KVM server you want to disable.
  6. Log in to the disabled server and remove the disabled server from the private zone.

Disabling HA enabled KVM servers

IMPORTANT: If high availability is enabled for your KVM server with the ImageLibrary role, you must remove images from the shared storage before disabling the last server. This will remove stale entries of the images from the Catalog screen.
Prerequisites

The administrator:

  • Connected HPE OneSphere to a KVM private cloud.

  • Enabled the server from the HPE OneSphere Private Zones > Update Zone screen

Procedure
  1. On all HA servers except the last server:
    1. Log in to the HPE OneSphere portal.
    2. Navigate to the Provider > Private Zones > Update Zone screen. Under Server Connections, disable the slider button for the KVM server you want to disable.
    3. Log in to the disabled server and remove the disabled server from the private zone.
  2. On the last server:
    1. Check to see if there are images in your image catalog using the OpenStack Glance client.
      glance image-list
    2. (Optional) If there are images in the catalog, then back up each image into a temporary location.
      glance image-download --file
    3. Delete each image from the catalog.
      glance image-delete <id or name>
    4. Log in to the HPE OneSphere portal.
    5. Navigate to the Provider > Private Zones > Update Zone screen. Under Server Connections, disable the slider button for the last server.
    6. Log in to the last server and remove the disabled server from the private zone.

Removing a disabled KVM server from a KVM private zone 

After disabling a KVM server, you can remove it from your HPE OneSphere KVM private zone. 

NOTE:

Any workloads running on this server are not affected.

Prerequisites
Procedure
  1. Find the name of the host agent running on the KVM server.
    1. For RedHat-based distributions:
      sudo rpm -qa | grep pf9-hostagent
      sudo rpm -qa | grep pf9-comms
      sudo rpm -qa | grep pf9-muster
    2. For Ubuntu:
      sudo dpkg -l | grep pf9-hostagent
      sudo dpkg -l | grep pf9-comms
      sudo dpkg -l | grep pf9-muster
  2. Uninstall the host agent and its dependencies.
    1. For RedHat-based distributions:
      sudo yum -y erase <pf9-agent-names-you-previously-grepped>
    2. For Ubuntu:
      sudo apt-get purge <pf9-agent-names-you-previously-grepped>

    These commands uninstall the host agent, along with any dependencies it installed on the server, such as OpenStack nova drivers, image library components, and so on.

  3. Terminate the pf9-sidekick.js process, if present.

    The pf9-sidekick.js process is used as an emergency rescue mechanism for failed upgrades where the host agent may have stopped functioning properly. This process is not automatically terminated after the host agent software is removed.

    Use the ps -C command to find the correct process ID, and if it exists, use kill to terminate it.

    The following example works for both RedHat and Ubuntu distributions:

    > sudo ps -C pf9-sidekick.js
    PID TTY TIME CMD
    1344 ? 00:02:16 pf9-sidekick.js
    > sudo kill 1344
  4. Remove the following directories.
    > rm -rf /var/log/pf9
    > rm -rf /etc/pf9

Validating and updating VMware vCenter credentials stored in the HPE OneSphere Controller

After you update the credentials for the VMware vCenter connected to HPE OneSphere, you must update the credentials for the vCenter in the HPE OneSphere Controller appliance that is deployed by HPE OneSphere in the vCenter.

The HPE OneSphere Controller appliance must contain the correct vCenter credentials in order for HPE OneSphere to communicate with the vCenter.

Procedure
  1. Log in to HPE OneSphere Controller running in the VMware vCenter connected to HPE OneSphere.
  2. Execute the update_credentials CLI utility.

    The HPE OneSphere Controller is deployed with a CLI utility that allows you to re-authenticate the HPE OneSphere Controller appliance with vCenter.

    1. (Optional) View the help for the CLI utility.
      update_credentials --help
    2. Validate the credentials for the vCenter in the HPE OneSphere Controller.
      update_credentials -i <vcenter ip address or hostname> 
      -u <vcenter username> [-p <vcenter password>] -V
      
      # If password option is not specified while invoking the command
      # you will be prompted to provide it later as password protected field
       NOTE:

      If the vCenter user name or password contains special characters, enclose the text in single quotes ('passw@$rd'). Single quotes (') and double quotes (") are not supported in the password.

    3. Update the credentials for the vCenter in the HPE OneSphere Controller.
      update_credentials -i <vcenter ip address or hostname> 
      -u <vcenter username> [-p <vcenter password>]

Viewing ESXi cluster and hosts summary for vCenter zones 

You can view details about clusters in your ESXi private zone including CPU usage, memory usage, a list of datastores, and a list of ESXi hosts in each cluster. You can also view details about each ESXi host in a cluster, including resource usage through a graphical presentation.

Procedure
  1. From the HPE OneSphere main menu, select Providers.
  2. On the Providers screen, select Private Zones.
  3. On the Private Zones screen, click the ESXi zone for which you want to view details.
  4. From the selected ESXi zone screen, click Clusters next to the cluster icon.
  5. From the Clusters screen, click the cluster name for which you want to view cluster details and resource usage metrics (performance and configuration parameters) of the deployed cluster.

    NOTE:

    If vCenter Administrator credentials were specified in HPE Connect when connecting HPE OneSphere to this private zone, then all clusters that belong to all datacenters in the vCenter are displayed. If datacenter Administrator credentials were specified, then only the clusters in that datacenter are displayed.

    If you enable a cluster by clicking Update Zone, you must select the cluster to enable that is associated with the vSphere Distributed Switch (VDS) specified in HPE OneSphere Connect. If you enable other datacenter clusters, then virtual machine deployment will fail in those clusters.

  6. From the selected ESXi zone screen, click Datastores next to the datastores icon.
  7. From the Datastores screen, click the datastore name to view the name of the zone, region, and the list of the clusters associated with the selected datastore. You can also view the amount of allocated storage space and the used storage space.
  8. From the selected ESXi zone screen, click Physical Servers next to the physical server icon.
  9. From the Physical Servers screen, click the name of the physical server (IP address or FQDN) to view the CPU and memory usage of the physical server and other details, including the name of the zone, region, and cluster associated with the physical server, and the total number of datastores along with their names.

Viewing servers summary for KVM zones 

You can view details about each KVM server in your KVM private zone, including operating system name and version, CPU usage, memory usage, and lists of datastores (LVM volumes) on the server. You can also view resource usage associated with the KVM server through graphical presentation.

Procedure
  1. From the HPE OneSphere main menu, select Providers.
  2. On the Providers screen, select Private Zones.
  3. On the Private Zones screen, click the KVM zone containing the server for which you want to view details.
  4. From the resulting screen, click Servers next to the cluster icon.
  5. From the Servers screen, select the server to view the server details and the resource usage metrics of the deployed server.

The Server Details screen displays the name of zone, region, CPU and memory usage, the name of operating system and its version, and the list of LVM volumes created on the server.

Viewing ESXi hosts summary for an existing vCenter private zone 

Existing VMware private zones that were previously connected do not have additional information about physical servers that are now part of each cluster deployed by default.

To enable viewing details about physical servers that are part of clusters, use the HPE OneSphere API as described below.

Procedure
  1. Log in to the HPE OneSphere portal to get an authorization token from the API.

    See Accessing the HPE OneSphere REST API interactive documentation for the procedure to access the HPE OneSphere REST API from the HPE OneSphere portal.

  2. Using the HPE OneSphere API, get the authorization token.
    Method : POST  
    URL: https://<customer-account>/rest/session
    Body : {
      "password": "string",
      "userName": "string"
    }
  3. Using the HPE OneSphere API, retrieve the list of zones and get the ZONE_ID for the existing vCenter zone.
    Method : GET
    URL: https://<customer-account>/rest/zones
  4. Log in to the HPE OneSphere Controller VM. If you are unable to log in, contact HPE Support.
    1. Create a directory named /opt/hpe.
      # mkdir -p /opt/hpe
      # cd /opt/hpe
    2. Export the token in the environment variable. (This is the session token generated in step 2.)
      # export HPE_OS_TOKEN=<TOKEN>
    3. Download the extension helper script.
      curl -X GET -H "Authorization: $HPE_OS_TOKEN" -H "Content-Type: application/json" 
      -x http://<proxy-server>:<proxy-port> 
      https://<customer_account_name>/rest/zones/<ZONE_ID>/node-recipes/extension-script-helper.sh 
      -o extension-script-helper.sh
      
    4. Give permission and execute the script.
      # chmod +x extension-script-helper.sh
      # ./extension-script-helper.sh -u https://<customer_account_name> 
      -z <ZONE_ID> -p http://<proxy-server>:<proxy-port> 
      -s fetch_cluster_inventory.py
  5. Check the log file at /var/log/hpe_extension_update.log for status.

You can now view details about your physical servers (hosts) in an ESXi zone from the Private Zones screen.

Viewing resource usage in private cloud providers

View scores for provider availability, utilization, and performance for private cloud providers from the HPE OneSphereProviders screen.

For detailed information, see About resource usage.

Procedure
  1. From the HPE OneSphere main menu, select Providers.
  2. Select Private Zones.
  3. Select the private provider zone you want to view.
    1. Click the graph to see the overall rating, and the utilization, availability, and performance scores.
    2. Click the individual categories for details specific to each category.

    Scores range from 0 to 1000, where 1000 is a perfect score. The score is an abstract value that represents the relative state.

    You can click the information icon  to see a detailed explanation of the Rating Breakdown.

    NOTE:

    It may take up to an hour for resource metrics to appear.

  4. To see details about a cluster in a private zone, go back to the Providers screen, and select a private zone.
    1. Select a cluster.
    2. Click the tabs above the graph to see the overall rating, and the utilization, availability, and performance scores for the cluster. You can also view the detailed cluster metadata for the selected zone. See Viewing cluster summary.

VMware vSphere storage metrics 

The following VMware storage metrics are collected by HPE OneSphere and can be viewed in VMware vSphere. These metrics are collected for vSAN and non-vSAN (VMFS, NFS, and virtual volumes) datastores.

Capacity metrics

Capacity metrics provide information about the cluster usage for vSAN and non-vSAN datastores.

Metric

Description

total_capacity

Total storage capacity of a datastore.

available_capacity

Available storage capacity of a datastore.

used_capacity_percentage

Percentage of the used storage capacity of a datastore.

Datastore health metrics

Health metrics provide information about the vSAN and non-vSAN data center status.

Metric

Description

datastore_used_capacity_percentage

Percentage of the used datastore capacity.

datastore_available_capacity

Available storage capacity of a given data center.

datastore_total_capacity

Provides the capacity of the entire datastore (both vSAN and non-vSAN).

SAN metrics

HPE OneSphere displays vSAN metrics when the version of vSAN SDK is 6.6.1. If the SDK version is lower or higher, HPE OneSphere may not generate these metrics.

Metric

Description

vsan_version

Version number of the vSAN cluster.

host_service_enabled

Enabled host service. The value must be set as true.

vsan_storage_service_connectivity

Host name which lacks the connectivity between vSAN service and vSAN service in the vCenter.

vSAN health metrics

Health metrics provide information about vSAN host status.

Metric

Description

vsan_overall_host_disk_health

Status of overall disks operational health of the ESXi host in vSAN cluster.

vsan._overall_cluster_health

Status of overall cluster operational health of the vSAN cluster.

vSAN diskgroup metrics

The health status of the diskgroup.

Metric

Description

vsan_overall_disk_group_mount

Functional status of the disk group health for vSAN cluster.