Support matrix

Last updated 10 December, 2018

Overview

The HPE OneSphere support matrix outlines the solution-level software and hardware and component-level firmware versions qualified to run with HPE OneSphere. Hewlett Packard Enterprise recommends running HPE OneSphere with the software, hardware, and firmware versions listed in this document. Upgrades beyond the versions in this document, except where explicitly stated, may cause unexpected behavior and result in an unsupported configuration.

For customers skilled in maintaining and upgrading the components of their solution, Hewlett Packard Enterprise recommends following this matrix. For customers who prefer Hewlett Packard Enterprise to perform updates and upgrades for their solution, Hewlett Packard Enterprise Pointnext Services offers a range of services to help maintain your solution. See www.hpe.com/Pointnext 

IMPORTANT:

To remain in support compliance, Hewlett Packard Enterprise recommends updating your system to the software, hardware, and firmware versions in this guide before connecting HPE OneSphere to your environment.

For more information, see Network configuration for HPE OneSphere Connect.

Browsers

The following browsers are supported to access the HPE OneSphere management service user interface. 

NOTE:

Hewlett Packard Enterprise recommends using Google Chrome with HPE OneSphere.

See the HPE OneSphere Release Notes for issues with other supported browsers.

Browser Version Notes

Google Chrome

62 or higher

Supported; recommended

Internet Explorer

11 or higher

Supported, but some features may not work as expected in this release

Mozilla Firefox

57.0.3 or higher

Supported, but some features may not work as expected in this release

Apple Safari

Most recent version

Supported, but some features may not work as expected in this release

Operating systems for HPE OneSphere Connect

The following operating systems are supported by the HPE OneSphere Connect application.

For more information, see Network configuration for HPE OneSphere Connect.

OS Version
Microsoft Windows Windows 7
  Windows 8
  Windows 10
  Windows Server 2012 R2
  Windows Server 2016
Apple Mac OS X 10.11 (El Capitan)
  macOS 10.12 (Sierra)
  macOS 10.13 (High Sierra)

Private cloud hardware and firmware

HPE OneSphere supports connecting HPE OneSphere to:

Supported hardware in an existing VMware environment Notes

HPE hardware support and HPE OneSphere software support is available for any HPE server* running a supported version of VMware ESXi.

HPE OneSphere software support is available when HPE OneSphere is connected to non-HPE servers running a supported version of VMware ESXi.

*HPE Synergy and HPE ProLiant Gen9 and Gen10 servers running ESXi 6.5 U1 require HPE Service Pack for ProLiant (SPP) October 2017 (SPP 2017.10.x) or higher.

Supported hardware in an existing KVM server Notes

HPE hardware support and HPE OneSphere software support is available for any HPE server running a supported operating system and kernel release.

HPE OneSphere software support is available when HPE OneSphere is connected to non-HPE servers running a supported version of KVM.

VMware vCenter and ESXi versions

Component Supported versions (including patch releases)
VMware vCenter

6.5 U1

6.5

6.0

5.5

VMware ESXi

6.5 U1

6.5

6.0

5.5

VMware vCenter environment

Before you connect HPE OneSphere with your on-premises VMware vCenter environment using HPE OneSphere Connect, verify that your private cloud environment is configured as follows.

  • A VMware vCenter environment is available to connect to HPE OneSphere.

  • One or more vSphere clusters is located in the vCenter environment.

  • vSphere clusters are configured for Distributed Resource Scheduler (DRS) with the Fully Automated option.

  • vSphere Distributed Switch (vDS)-based networking is configured for the vSphere clusters. Connect the vDS to all hosts in datacenters managed by HPE OneSphere. Create one HPE OneSphere private zone for each datacenter in the vCenter.

    NOTE:

    A vSphere environment configured with vDS is strongly recommended. However, a hybrid vDS and vSphere Standard Switch (vSS) configuration is also supported. In a hybrid configuration, VM networking for VM deployments is configured on vDS. The network segment configuration for the HPE OneSphere Controller and VMkernel services (for example management and vMotion) and other networks can be configured on vDS or vSS.

  • Outbound HTTPS network access is configured in the cluster for communication with the HPE OneSphere management service.

  • NTP lookup (*.centos.pool.ntp.org) and time synchronization are available over the internet connection through the configured proxy server.

For information about creating the initial private cloud provider and running HPE OneSphere Connect, see Connecting to HPE OneSphere for the first time.

VMware vSphere ESXi cluster

vCenter cluster Requirement

Nodes per cluster

2 to 64

3 to 64 for vSAN cluster

vCPU

8 (minimum)

Memory

32 GB (minimum)

Shared datastore

100 GB (minimum)

DRS (Fully automated)

Enabled

HA

Enabled (optional)

VMware vSphere/ESXi networks

Network name Notes
HPE OneSphere Mgmt Must have outbound HTTPS connectivity to HPE OneSphere management service and connectivity to the vCenter Server.
Tenant networks (Provider) These networks map to the existing physical networks in the data center. Each network can be shared by multiple projects (tenants) and carry tenant's virtual machines traffic.

VMware vSphere/ESXi storage

Component Supported version
ESXi storage

Any VMware storage backend that is supported in the supported version of ESXi that provides shared storage to the cluster.

NOTE:

Local datastores are not supported for hosting VMware templates.

KVM versions 

Distribution OS version x86 instruction set version

CentOS

7.3 (recommended)

7.2

64-bit (x86_64)

Red Hat Enterprise Linux (RHEL)

7.3 (recommended)

7.2

64-bit (x86_64)

Ubuntu

16.04

64-bit (x86_64)

KVM servers 

KVM server component/feature Requirement Notes

Hostname

Unique

 

Storage

Local or Ceph (block) storage

See KVM storage

System clock

Synchronized with a public cloud-based NTP server

See Network configuration for KVM servers for NTP configuration steps.

Virtualization

Enabled

Check BIOS settings (Intel VT)

KVM networks 

For detailed KVM networking configuration steps, see Network configuration for KVM servers.

NOTE:

OpenStack virtual routing is not supported.

KVM networking component Requirement Notes

Interfaces

Two or more physical network interfaces (NICs) clubbed as bond0

NICs carry both management and production traffic. Alternatively, you can configure one dedicated interface for management connectivity.

HTTPS

Outbound HTTPS (port 443) access

 

OpenStack Provider networks

Use OpenStack Neutron API

HPE OneSphere supports using OpenStack Provider networks for deploying virtual machine instances to existing KVM servers in a private cloud.*

VLAN sub-interfaces on the physical interface/bond

VLAN-based virtual machine traffic

Used to route traffic for the VLAN-based Provider networks. Ensure that the VLAN is trunked on the switch where the KVM server is connected for all VLAN IDs that you plan to supply to OpenStack Neutron.

Management VLAN

Ensure this VLAN allows outbound HTTPS access for the host agent to communicate with HPE OneSphere.

* Create Provider networks and attach them to a project using the OpenStack Neutron API. You can then select a Provider network from a list of pre-created networks when you deploy a virtual machine from HPE OneSphere. Provider networks cannot be edited in HPE OneSphere.

KVM storage 

Supported storage type Requirement

Local storage

Each KVM hypervisor is configured with local storage that is sufficient to host virtual machines that will run on that server

One server is configured with sufficient additional storage to host one or more images used for virtual machine provisioning

Block storage

Integrated with Ceph (SUSE Enterprise Storage 5). 

See Configuring Ceph storage, SUSE Enterprise Storage 5 Deployment Guide, and HPE best practices for deploying SUSE Enterprise Storage on HPE Synergy.

OpenStack client 

OpenStack client version Supported version and notes

HPE OneSphere supports the installation of the version of the OpenStack client CLIs that is distributed with the supported versions of RHEL, CentOS, and Ubuntu.

See Installing OpenStack CLI clients for HPE OneSphere

Python

Version 2.7

novaclient Python API

Version 7.0.0

Public cloud provider accounts

HPE OneSphere supports Amazon Web Services (AWS) and Microsoft Azure as public cloud providers.

Provider Account type
AWS AWS organization accounts (Master/payer account and member accounts)
AWS Non-organization account (Standalone account)
Azure Enterprise Agreement account
Azure Subscription

For more information about public cloud provider accounts, see Managing Amazon Web Services public providers and Managing Azure public providers.

Scale limitations

Resource Maximum number supported

Total of Amazon Web Services (AWS) regions, VMware ESXi private zones, and KVM private zones

10

Project quotas

Projects

50

In a single project

Default values:**

10 deployments

20 cores

51200 MB RAM

200 GB storage

VMware vCenter environments

VMware vCenter clusters per data center

10

ESXi hosts per vCenter cluster

10

ESXi hosts per vCenter data center

50

Virtual machine instances deployed to a vCenter

700

Port groups in a vNetwork Distributed Switch (VDS)

50

VDS for production networks

1*

Subnet for production networks

1

KVM environments

KVM servers per zone

10

Virtual machine instances deployed to a KVM server

40

AWS providers

Storage volumes connected to a virtual machine deployed to AWS

1

Size of a storage volume connected to a virtual machine deployed to AWS

1 GB (minimum) to 1 TB (maximum)

* Port groups that are created on this vNetwork Distributed Switch are available for HPE OneSphere VM deployments. IP addresses can be configured only to networks (port groups) belonging to this configured VDS.

**Contact HPE Support to increase the default quota limits for a given project.

Required permissions for VMware vSphere user accounts

The following user permissions are required in VMware vSphere to connect to the HPE OneSphere management service.

  • Datastore

    • Allocate space

    • Browser datastore

    • Low level file operation

    • Remove file

  • Extension

    • Register extension

  • Folder

    • Create folder

  • Host

    • Configuration

      • Maintenance

      • Network configuration

      • Storage partition configuration

  • Network

    • Assign network

  • Resource

    • Assign virtual machine to resource pool

    • Migrate powered off virtual machine

    • Migrate powered on virtual machine

  • Virtual machine

    • Configuration

      • Add existing disk

      • Add new disk

      • Add or remove device

      • Advanced

      • Change CPU count

      • Configure managedBy

      • Disk change tracking

      • Host USB device

      • Memory

      • Modify device settings

      • Raw device

      • Remove disk

      • Rename

      • Set annotation

      • Settings

      • Swapfile placement

    • Guest operations

      • Guest operation alias modification

      • Guest operation alias query

      • Guest operation modifications

      • Guest operation program execution

      • Guest operation queries

    • Interaction

      • Configure CD media

      • Power off/on

      • Reset

      • Suspend

    • Inventory

      • Create from existing

      • Create new

      • Move

      • Remove

      • Unregister

    • Provisioning

      • Clone virtual machine

      • Customize

      • Deploy template

      • Mark as template

    • Snapshot management

      • Create snapshot

      • Remove snapshot

  • Sessions

    • Validate session

    • View and stop sessions

  • vAPP

    • Import/export

Additional permission requirements

If the permissions mentioned in Required permissions for VMware vSphere user accounts are given only to the appropriate datacenter, rather than the entire vCenter, then the user will need additional permissions on the vCenter root folder. The following permissions must be given to the user on the vCenter level. When creating this additional role, copy the pre-existing "Read-only" role and add the following permissions. When assigning these permissions, verify that Propagate to Child Objects is selected.


  • Profile-driven storage


    • Profile-driven storage view


  • Sessions


    • Validate session


    • View and stop sessions


  • Storage views


    • View