3. Who am I ?
Midori Oge / ⼤大削 緑 @star76popin
– Chairman of Japan CloudStack Users Group
– Systems Engineer, SolidFire Inc.
4. The world as it is..
Processor speeds and network bandwidth have been able to keep
pace with new workloads requirements
CPUとネットワークは性能向上が進み、新しい要件に対応
Many workloads due to virtualization technology and cloud computing
仮想化/クラウド化によるワークロードの多様化
… How's the STORAGE?
5. The world as it is..
HDD performance had remained almost unchanged
ü increasing OpEx(power, rack space…)
ü proprietary hardware
ü complicated design and operation (RAID sets, manage logical Volume and LUNs…)
ü can't catchup the needs of cloud and unpredictable scaling
ü running many kinds of storages (different solutions for different workloads)
HDD性能は横ばい、I/Oがボトルネックに
ü 運⽤用コストが増⼤大(電⼒力力、設置スペース…)
ü 独⾃自仕様のハードウェア
ü 設計が⼤大変、管理理も複雑(RAID,論論理理ボリューム,LUN)
ü クラウドの柔軟性・拡張性への対応が難しい
ü 複数のストレージが乱⽴立立
6. beginning of the innovation
ü ストレージは2極化の⽅方向に
- Hot/Activeデータは、Flashなどの⾼高速ストレージに
- Cold/Staticデータは、低コストで⼤大容量量を保存可能なストレージに
- HDD SAS Diskは年年々減少していく傾向に
ü Bipolarization of Storage solution
- Hot/Active data for critical applications is stored in Flash storage
- Cold/Static data for backup is stored in cost/capacity optimized storage
- HDD SATA Disk is expected to decrease in these years
Software Defined
ソフトウェアによるきめ細かい制御
Flash prices are reduced
Flashの低価格化
7. Technical trend for cloud computing
ü de-‐‑‒duplication, compression, thin-‐‑‒provisioning
ü multi-‐‑‒tenant
ü scale-‐‑‒out
ü improving availability by data distribution
ü fault detection, self-‐‑‒healing
ü integrated for cloud(CloudStack, OpenStack), API-‐‑‒driven automation
ü 圧縮、重複排除、シンプロビジョニング
ü マルチテナント
ü スケールアウト
ü データ分散による可⽤用性向上
ü 故障検知、⾃自⼰己修復復
ü クラウド連携(CloudStack, OpenStack)、APIによる⾃自動化
8. Storage Types in CloudStack
Primary Storage Secondary Storage
ü for Boot Disks and Data Disks
ü NFS, iSCSI, Fibre Channel, CIFS
(if performance is needed without using HA,
you can choose local storage)
ü Scope: Cluster or Zone
ü for Templates, ISO Images, Snapshots
ü NFS, CIFS Swift/S3(w/NFS)
ü Scope: Zone
What kind of STORAGE do we choose?
9. What type of storage do we choose?
ü Secondary Storage
- using low-‐‑‒cost storage or object storage(e.g., swift)
⽐比較的安価なストレージ、またはオブジェクトストレージ(swiftなど)で構築可能
ü Primary Storage
- Storage performance leads to VM performance(meet the requests of IOPS/Latency)
ストレージの性能がVMの性能に直結(IOPS/Latency要件)
- Lose VM due to Primary Storage fail
Primary Storageがダウンすると、当然VMにもアクセス不不可となる
Need "Guaranteed Performance !!"
10. Guaranteed Performance (QoS)
both MIN and MAX is important in QoS
QoSは、MINとMAXの2つの制御が⼤大事
Form Mixed Workloads
ü MIN
protect the important volume
⼤大事なVolumeを守る
ü MAX
limit the IO of monster VM
モンスターVMなどの影響を排除する
11. Mike
Tutkowski
@mtutkowski
Senior
CloudStack
Developer
–
SolidFire
PMC
Member
-‐
Apache
CloudStack
Guaranteeing
Storage
Performance
in
CloudStack