HPE GreenLake for Private Cloud Business Edition at Equinix

1. Service overview

  • 1.1. HPE GreenLake for Private Cloud Business Edition at Equinix (the “Service”) is an extension of the infrastructure-as-a-service—offered on the HPE GreenLake edge-to-cloud platform (the “platform”). It provides a self-managed private cloud solution deployed at Equinix colocation facilities with a unified web interface to simplify VM to infrastructure management.

  • 1.2. The Service includes the hardware (HPE ProLiant Servers, HPE Alletra Storage, optional rack and switches, software-as-a-service (Alletra Software & Support SaaS, Private Cloud Business Edition-Management Console) and hardware support.

  • 1.3. As an extension to the HPE GreenLake for Private Cloud Business Edition service description, this document describes modifications to the services and features provided under the HPE GreenLake for Private Cloud Business Edition service description.
  • 2. Core service features

    • 2.1. The core features associated with the Service are the same as the core service features associated with HPE GreenLake for Private Cloud Business Edition
  • 3. Optional service features

    3.1. HPE GreenLake for Private Cloud Business Edition at Equinix


    • 3.1.1. This service option allows the underlying hardware to be deployed within an Equinix colocation facility.

    3.2. HPE GreenLake for Private Cloud Business Edition at Equinix features

    • 3.2.1.1. Selection of a colocation facility across the globe which eliminates the need for a user’s own facilities, IT capital outlay, and additional IT human resources.
    • 3.2.1.2. Single, intuitive cloud-based user interface to manage data center and colocation deployed Systems.
    • 3.2.1.3. Simplified ordering process as the rack, PDU, and top of rack switch decisions are predetermined.
    • 3.2.1.4. One support and billing experience and contact from HPE.
    • 3.2.1.5. Optimized sustainability, security, and resiliency through state-of-the-art hosting facilities delivered by the colocation provider.
    • 3.2.1.6. Low latency, high bandwidth connections to major CSPs.
  • 4. Features requiring Customer selection

    4.1. City location associated with a colocation facility

    • 4.1.1. Selection of a city will automatically select the top of rack switch, the rack, and PDU options

    4.2. Workload Requirements

    • 4.2.1. All Flash
    • Backed by Business Critical storage (applications not in scope)
    • Wide range for performance expectations from 2GB10GB/sec
    • Advanced site replication desired, with some tolerance for failover time
    • 4.2.2. Hybrid Flash
    • Backed by General Purpose storage (applications not in scope)
    • Wide range of performance expectations from 0.3GB2GB/sec
    • 4.2.3. Available Tiers
    • Performance
      • Delivers the most performance within a chosen data availability level.
    • Balanced
      • Delivers a balance of performance and capacity scaling within a chosen data availability level.
    • Value
      • Delivers the most cost optimized performance level within a chosen data availability level.
    • 4.2.4. Units of Measure of Commitment
    • Block Storage
    • CPU
    • Memory

    4.3. Internet connectivity and Firewall selection

    • 4.3.1. Selection of the internet type and speed and the firewall termination to the Equinix facility Optional add-on features

    4.4 The following are add-on features that may be configurable as part of the Service.

    • HPE Defective Media Retention (DMR)
    • HPE Comprehensive Defective Media Retention (CDMR)
  • 5. Support

    5.1. HPE Tech Care Service Essential service level support is included as part of the Service.


    5.2. Deployment services for the initial setup of PCBE within the chosen colocation facility.

  • 6. Exclusions

    6.1. Customers are responsible for procuring any 3rd party software licenses required for the Service e.g., VMware vSphere licenses, as the Service does not include any 3rd party software licenses.


    6.2. Racks, PDUs, and switches:

    • 6.2.1. The switch, rack, and PDU decisions for the colocation option are pre-determined
      • 6.2.1.1. The switches will be included as the standard switches available with the Private Cloud Business Edition solution.
      • 6.2.1.2. The rack and required PDUs will be included.

    6.3. When ordering for delivery to multiple locations, a separate purchase order is required for each location.

  • 7. Customer responsibilities

    7.1. Shared responsibility model

Customer

HPE

Responsible for the connectivity to the platform, the administration, and the management of the data/objects

Responsible for the setup and functionality of the infrastructure providing the Service

Internet connectivity, Firewall, and Virtual connections (VC) to the Equinix fabric

Installation & activation of devices

Maintain connectivity to the platform

Customer orientation

Volume Creation and administration

Access to software, firmware, and documentation updates

Data resilience and remote replication

H Support for Equinix based PCBE hardware

Data backup

Proactive support and operational guidance through the platform

Applying recommended software updates & security patches

Operational Insights and Dashboard through the platform

Data Monitoring

Proactive capacity planning


Initiating the order of additional capacity beyond total available capacity

Proactive incident alerting through the platform


Communicate security incident & remediation through the platform


Test volume Creation during installation


Maintain the Systems located at Equinix

Optional addons services may be available from Equinix


7.2. Systems and data

  • Procuring required software
  • Unless included as part of the Systems, the Customer is responsible for purchasing and installing the OS, virtualization software, and related software licenses and support.
  • Enabling installation
  • The Customer acknowledges that they must take the necessary steps to enable installation (including platform connectivity) within 30 calendar days from receipt of the Systems.
  • 8. Service Level Objectives

    The Customer can choose from the following service level objectives (“SLO”):


    8.1. Performance Optimized Tier

    Service for I/O intensive, very-low latency workloads, and bandwidth intensive applications at a given availability level. Most common for SAP HANA, Oracle, Microsoft SQL Server, and IBM DB2 based applications.


    8.2. Balanced Optimized Tier

    Service designed to balance scalable capacity requirements with I/O sensitive, very-low latency workloads at a given availability level.


    8.3. Value Optimized Tier

    Service optimized for cost for I/O sensitive, very-low latency workloads at a given availability level.


SLO

All Flash

Hybrid Flash

Performance Tier

Up to 400K IOPS (read)

Up to 120K IOPS (read)


Up to 200K IOPS (mixed)

Up to 120K IOPS (mixed)


Up to 9GB/s & 3GB/s (read & write)

Up to 5.0GB/s & 2.0GB/s (read & write)

Balanced Tier

Up to 200K IOPS (read)

Up to 65K IOPS (read)


Up to 100K IOPS (mixed)

Up to 60K IOPS (mixed)


Up to 2GB/s & 2GB/s (read & write)

Up to 1.9GB/s & 1.0GB/s (read & write)

Value Tier

Up to 150K IOPS (read)

Up to 20K IOPS (read)


Up to 75K IOPS (mixed)

Up to 15K IOPS (mixed)


Up to 4GB/s & 1GB/s (read & write)

Up to 1.0GB/s & 0.3GB/s (read & write)

The performance service level objective includes standard data operations (i.e. UI, Intelligent Autonomous Storage, garbage collection). Event-based data operations (replication, snapshots, hw upgrade, etc.) are excluded.

The underlying device Infrastructure deployed is designed to deliver the stated total IOPS under 1ms latency for the specified workload: Read IOPS: 100%, 8k.

Mixed IOPS: 50% read, 50% write, 8k.

Throughput: 256k sequential

  • 10. Service Level Agreement Customer responsibilities

    HPE’s availability commitment applies separately to each account using the Service. Data availability service-level agreement conditions:


    10.1. Customer responsibilities

    • Connectivity to the platform, including Data Services Cloud Console and HPE Infosight; outages that happen while the device is not connected and sending data back to HPE will not qualify for this service-level agreement.
    • Applying all HPE critical and recommended software updates (patches) within 10 days and HPE Alletra OS releases within 30 days of notification.
    • Remediating any technical issues related to HPE GreenLake for Block Storage on-premises equipment or other customer equipment that HPE has proactively raised within 30 days.

    10.2. In the event of an unplanned qualifying outage:

    • If not proactively identified by HPE, the customer must open a support case with HPE within seven days.
    • In the event that HPE is not able to determine the root cause of an outage due to missing information (log entries) or failure to recover equipment, parts, components, or other devices that are required to establish the root cause (outside of the equipment within the colo facility), the associated unplanned outage may not qualify for remediation under this service-level agreement.
  • 11. Applicable Terms and Conditions

Terms

Links

Data Privacy and Security Agreement

Data processing & security measures

N/A

Sub-processor list

N/A

HPE aaS Terms for Customers (unless otherwise stated in the Change Order Form)

Recommended for you