No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

SmartMulti-Tenant Feature Guide for Block

OceanStor V5 Series V500R007

This document is applicable to OceanStor 5110 V5, 5110F V5, 5300 V5, 5300F V5, 5500 V5, 5500F V5, 5600 V5, 5600F V5, 5800 V5, 5800F V5, 6800 V5, 6800F V5, 18500 V5, 18500F V5, 18800 V5, and 18800F V5. This document describes the implementation principles and application scenarios of the SmartMulti-Tenant feature. Also, it explains how to configure and manage SmartMulti-Tenant.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Application Scenarios

Application Scenarios

SmartMulti-Tenant enables users to implement flexible, easy-to-manage, and cost-effective storage sharing among multiple tenants in a storage infrastructure where various protocols are employed. By using this feature, tenants can customize their performance tuning policies and data protection settings, meeting their diversified service requirements.

Offering Differentiated Performance Levels to Different Users

In order to reduce costs, some users will not build their dedicated storage systems, but use the SmartMulti-Tenant feature to centrally run their storage applications. This lowers the total cost of ownership (TCO) and ensures the application continuity. However, applications of different types and characteristics bring about contention for storage resources. How to fully utilize existing storage resources to meet the unique requirement of every user becomes a challenge to address.

The SmartMulti-Tenant feature provides customized services for tenants of different levels in a single storage system. These tenants can create their own SmartQoS and SmartPartition policies to properly utilize storage resources. The service requirements of high-level tenants are prioritized.

For example, a storage resource provider is providing storage resources for subscribers of five levels, as shown in Table 1-3.

Table 1-3 Subscriber characteristics

Subscriber

Service Type

QoS Requirement

Subscriber A (diamond subscriber)

Mission-critical applications, sensitive to latency

Highest

Subscriber B (platinum subscriber)

Online transaction processing (OLTP) and enterprise resource planning (ERP) applications

High

Subscriber C (gold subscriber)

Mainstream business applications, having demanding write requirements

Comparatively high

Subscriber D (silver subscriber)

Decision support, data warehouse, messaging and collaboration applications, and so on

Medium

Subscriber E (bronze subscriber)

Archiving, paperwork, printing, and so on

Low

These subscribers have different service priorities, so the storage resource provider can create tenants for them and configure the following settings for the tenants and their vStores:
  • Allocate storage resources to each vStore based on the tenant's level and service requirements.
  • Set the maximum IOPS and bandwidth for each tenant.
  • Set a SmartPartition policy for each tenant to meet their service requirements and ensure the QoS of high-level tenants.

Table 1-4 lists the detailed service policies that the storage resource provider can set for tenants.

Table 1-4 Service policies set for subscribers

Subscriber

Storage Configuration Policy

QoS Requirement

Subscriber A (diamond subscriber)

  • I/O priority: high
  • Initial capacity allocation policy: Allocate from the high performance layer first
  • SmartQoS policy: Limit the maximum bandwidth consumption (for example: to 50 MB/s) of the other services of subscriber A during peak hours.
  • SmartPartition policy: Create SmartPartition 1 for subscriber A. Set read and write cache sizes for SmartPartition 1 (for example, set the read cache size to 20 GB and write cache size to 15 GB).

Subscriber B (platinum subscriber)

  • I/O priority: high
  • Initial capacity allocation policy: Allocate from the high performance layer first
  • SmartQoS policy: Limit the maximum bandwidth consumption (for example: to 50 MB/s) of the other services of subscriber B during peak hours.
  • SmartPartition policy: Create SmartPartition 2 for subscriber B. Set read and write cache sizes for SmartPartition 2 (for example, set the read cache size to 15 GB and write cache size to 10 GB).

Subscriber C (gold subscriber)

  • I/O priority: medium
  • Initial capacity allocation policy: Allocate from the performance layer first
  • SmartQoS policy: none.
  • SmartPartition policy: Create SmartPartition 3 for subscriber C. Set read and write cache sizes for SmartPartition 3 (for example, set the read cache size to 15 GB and write cache size to 10 GB).

Subscriber D (silver subscriber)

  • I/O priority: medium
  • Initial capacity allocation policy: Allocate from the capacity layer first
  • SmartQoS policy: none.
  • SmartPartition policy: Create SmartPartition 4 for subscriber D. Set read and write cache sizes for SmartPartition 4 (for example, set the read cache size to 10 GB and write cache size to 8 GB).

Subscriber E (bronze subscriber)

  • I/O priority: low
  • Initial capacity allocation policy: Allocate from the capacity layer first
  • SmartQoS policy: none.
  • SmartPartition policy: none.

Figure 1-3 illustrates the resource allocation results in an intuitive manner.

Figure 1-3 Service performance control results of tenants

Safeguarding Mission-Critical Applications

Advanced data protection technologies such as snapshot and remote replication are provided for tenants to protect their local and remote data and configurations. These technologies help tenants fast retrieve data if it was non-physically damaged, such as being deleted, overwritten, or infected by virus.

Table 1-5 lists the data protection policies that can be provided for the subscribers based on their levels and service requirements.

Table 1-5 Data protection policies of subscribers

Subscriber

Data Protection Policy

Subscriber A (diamond subscriber)

Snapshot + remote replication

Subscriber B (platinum subscriber)

Snapshot + remote replication

Subscriber C (gold subscriber)

Snapshot

Subscriber D (silver subscriber)

None

Subscriber E (bronze subscriber)

None

Translation
Download
Updated: 2019-07-11

Document ID: EDOC1000181478

Views: 32412

Downloads: 196

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next