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

FusionCloud 6.3.0 Solution Description 05

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).
Ultra-high I/O (SSD-type) ECSs

Ultra-high I/O (SSD-type) ECSs

Application Scenarios

Ultra-high I/O ECSs use high-performance local NVMe SSDs as data disks to provide high storage input/output operations per second (IOPS) and low read/write latency. The ratio of memory to vCPU is 8:1, excepting the ECSs with 60 vCPUs. You can create such ECSs with high-performance NVMe SSDs attached on the management console.

Ultra-high I/O ECSs can be used for high-performance relational databases, NoSQL databases (such as Cassandra and MongoDB), and ElasticSearch search.

Notes

  • Ultra-high I/O ECSs support KVM virtualization only, but do not support flavor change, cold migration, live migration, HA, or cloning.
  • Ultra-high I/O ECSs cannot be used in a converged deployment scenario. A converged deployment means that FusionStorage is deployed on compute nodes.
  • After an ultra-high I/O ECS is deleted, the data on the local NVMe SSD is automatically deleted. Back up the data before deleting it.
  • Local NVMe SSDs are not hot-swappable. To replace them, power off the physical server first.
  • Local NVMe SSDs can only be used as data disks. Their reliability depends on the reliability of physical servers and hard disks, which are SPOF-prone. Therefore, you are advised to configure data redundancy at the application layer to ensure data availability. Use EVS disks to store data that needs to be retained for long periods of time.
  • A physical server supports local NVMe SSDs that are of the same type and capacity only. It does not support mixed configuration.
  • In the Region Type I scenario, ultra-high I/O ECSs cannot be created at the cascading layer.
  • Ultra-high I/O ECSs support the following OSs:
    • EulerOS 2.2
    • CentOS 7.2 64bit
    • Ubuntu Server 14.00-14.05
    • Ubuntu Server 16.04
    • Redhat 6.5 64bit
    • Windows Server 2008 R2
    • Windows Server 2012 R2 64bit (Standard Edition/Datacenter Edition)
NOTE:

You are advised to use EulerOS 2.2 or Ubuntu Server 16.04 for optimal performance.

  • If an ultra-high I/O ECS is created using a private image, make sure that the NVMe driver has been installed during the private image creation. If not, install the driver after the ultra-high I/O ECS is created.

Flavors

Table 16-7 Flavors of ultra-high I/O ECSs

Type

vCPU (U)

Memory (GB)

Flavor Name

Local SSD flavor (for reference)

Disk Type

Maximum IOPS for Random 4 KB Read

Ultra-high I/O ECSs

8

64

i3.2xlarge.8

1 x 1600GB NVMe SSD

NVMe_SSD

750000

16

128

i3.4xlarge.8

2 x 1600GB NVMe SSD

NVMe_SSD

1500000

32

256

i3.8xlarge.8

4 x 1600GB NVMe SSD

NVMe_SSD

3000000

48

384

i3.12xlarge.8

6 x 1600GB NVMe SSD

NVMe_SSD

4500000

60

512

i3.15xlarge.8

7 x 1600GB NVMe SSD

NVMe_SSD

5250000

NOTE:

Configure the capacity and number of local SSDs based on server hardware configuration.

Translation
Download
Updated: 2019-04-23

Document ID: EDOC1100026685

Views: 153174

Downloads: 262

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