3 minute read

Customer responsibilities

TABLE 1. Service component highlights (continued)

Component Delivery specifications

Advertisement

Consumption billing HPE GreenLake for ML Ops pricing is made up of a recurring price for reserved capacity, plus monthly charges for any usage over the reserved capacity.

The customer agrees to a reserved capacity at a certain price. The minimum reserved capacity for HPE GreenLake for ML Ops, for both configurations, is 50%. If the customer consumes at or below the reserved capacity, the monthly bill does not change month to month. Monthly charges over the reserved capacity are calculated based upon the following 4 meters: • Storage: GB average usage per hour • CPU cores: Usage by minute • V100 GPU: Usage by minute • T4 GPU: Usage by minute

Pricing is based on a rate card. The higher the reserved capacity, the lower the unit price for the 4 meters. To retain a consistent rate and consistent monthly reserve payment, every month will be set to have the same number of days, 30.477, based on the average number of days in a month over the year (365.25/12 = 30.477). Compute is measured and billed to the nearest minute (per month). Storage is measured and billed to the nearest hour (per month). The 4-year contract is paid monthly. If the customer uses more than their reserved monthly capacity, they pay for that extra consumption across the meters where they exceeded the reserve. The rate at which they pay is the unit price at the reserved amount.

How usage is metered For compute, the HPE metering tool calls an OS level API that returns CPU ticks every minute. CPU ticks indicate the CPU is in use. If the CPU returns a usage rate of 5% during the minute, we regard that CPU as in use, and bill for that minute at the agreed hourly rate. The first 5% is intended to cover low-level system jobs not initiated by the user and not counted as HPE GreenLake usage. For storage, HPE uses HPE Ezmeral technology to check at the beginning of the hour and the end of the hour what the storage consumption is for the particular drive or volume, and then it calculates the average. For example, if the meter shows 50% used at the beginning of the hour and 100% at the end of the hour, HPE bills on 75%. HPE does not charge for ephemeral storage; this is reported but not charged.

Consumption analytics Via the HPE GreenLake Central portal, HPE GreenLake for ML Ops customers have access to HPE Consumption Analytics. HPE Consumption Analytics provides detailed reports, views, and analytics to help customers manage consumption and help maximize investments across public cloud and hybrid cloud infrastructure. Included are interactive charts, drag-and-drop features, data mapping, monitoring, and powerful insights. The HPE GreenLake for ML Ops monthly charge report displays actual usage compared to reserved usage.

Ordering and pricing • U.S. prices are published for a sample set of reserve levels on the HPE GreenLake for ML Ops webpage. • Contact HPE sales for a quote in your country. • HPE GreenLake for ML Ops shall be available for sale in 21 countries.

Governance HPE GreenLake for ML Ops includes an assigned account team (AAT) that works closely with the customer to understand their business and IT objectives, with the goal to help ensure these needs are met. The AAT is the customer’s advocate and technical focal point for ongoing support of the IT environment. The AAT works with the customer to develop and routinely review a mutually agreed account support plan.

The customer responsibilities include, but are not limited to, the following:

The customer will:

• Provide an internet connection necessary for HPE GreenLake Central service

• Provide a location suitable for delivery of the service, public (guest) internet access for the HPE delivery consultants, and any network connections required

• Allow HPE all reasonably necessary access to all locations where delivery service is to be performed

• Assign a project sponsor, project manager, and other personnel, as appropriate, to work with HPE throughout the project’s lifecycle

This article is from: