2. Boyan Krosnov
● Chief of Product
● Cloud architect
● "External technology"
● Previously service providers, networks, packet
processing (SDN)
● Algorithms & data structures
2
3. StorPool
● Fast and efficient software-defined storage system
● Used by MSPs, Cloud service providers, Hosting
companies and in private clouds
● Started in 2011 to solve storage for cloud service
providers
● Clean slate design - scale-out, API-controlled,
end-to-end data integrity, CoW
3
4. StorPool
● Most deployments are with KVM
○ some Xen, some VMWare, some Hyper-V
○ some bare metal / dedicated server
● Deep integrations into OpenStack, OpenNebula,
OnApp
● New integration in CloudStack
4
11. Hyper-converged: example
Private cloud for production public-facing application
(high-end VDI)
● Independent racks design. Each rack has…
● Top of rack switches, 2x 25GbE to each node
● 38 compute nodes
● Each with 2x 3.84 TB NVMe SSDs
● 88 TB usable space (3-way replication, checksums,
CoW, safety)
12. Hyper-converged: example
Private cloud for production public-facing application
(high-end VDI)
Strong case for all of
● SDS
● hyper-convergence
● scale-out storage architecture
● low latency and efficient storage software layer
13. Contrast requirements
Best performance I can get at reasonable cost
(private cloud for web/mobile application)
vs.
Good performance and low $/GB for desired performance
level. Market leading, but not too expensive. (service
providers)
vs.
Lowest $/GB (e.g. archival use-case)
18. When hyper-converged
Hyperconverged:
● Green-field
● KVM virtualization
● Building pods / small availability zones
Stand-alone storage system:
● Retrofit
● Other hypervisors: Xen, VMWare, Hyper-V
● Requirements for independence of infrastructure (I don't want an issue
in my KVM environment to affect my VMWare environment)
● Requirement for administrative boundary - e.g. additional storage to
dedicated server via iSCSI
● Building datacenter-scale infrastructure. Cost of high bandwidth
leaf-spine network (3x) justified
19.
20. StorPool-CloudStack
StorPool for CloudStack/KVM
● Uses StorPool native driver in host OS
○ block devices in /dev/storpool/volname are raw disk
images for qemu/KVM
○ data management - e.g. create, delete, clone, resize
snapshot - API calls
● Implements a datastore driver for primary storage
On other hypervisors use their native storage mechanisms -
e.g. VMFS