StorPool Distributed Storage - Embracing Software Defined
22
Embracing Software Defined: From Theory to Practice
-
Upload
boyan-ivanov -
Category
Software
-
view
78 -
download
0
Transcript of StorPool Distributed Storage - Embracing Software Defined
Embracing Software Defined:
From Theory to Practice
Image by theaucitron
Software-defined – why, what, how
…and not “marketing-defined”
A few words about me
Tried programming at the age of 10
First ventures at the same age (and the
latter stuck)
Experience in both Enterprise and start-up
worlds
2 “formal start-ups” prior StorPool
StorPool – distributed storage software
Boyan Ivanov
CEO & co-founder StorPool Storage
@bhivanov
“Software Is Eating The World”
Then Now
Image by Erik (HASH) Hersman
Image by Michael Casey
Image by Alfred
Image by Remko van Dokkum
Image by Kārlis Dambrāns
Image by Alfred
“Software Is Eating The World” – Indeed.
Image by Marcin Wichary
Image by George Redgrave
Image by Jeff Geerling
Image by John Karakatsanis
Then Now
“Software Is Eating The World” – Indeed. True.
Image by Bob Mical
Image by derfian
Software
+
Leonardo Rizzi Image by Bob Mical
Then Now
Infrastructure is not going away…
…but it’s becoming “software defined”
Image by is van Zuijlekom
Cloud = hardware + software
Practice: What Software Defined Is
A way to achieve: Scale & agility Simplicity Cost optimization (TCO)
In practice Software defined technologies are sensitive to hardware, configurations, firmware versions, etc.
COTS hardware. Nothing special, still selected for the task: x86 servers, standard NICs, HBAs, HDDs,
SSDs. That’s all. Must provide the full functionality with just software not depend on an external specialized
system
Practice: What Software Defined Is NOT
Some vendors are doing marketing disinformation. Reality: x86 server is as good as a specialized
appliance Ethernet is as good as FC; SATA is as good as
SAS
Silver bullet
“Orchestration”, “storage virtualization”, etc. - if you need another layer of legacy technology underneath – NOT SD
Software-managed is not Software-defined. Connecting your appliance to OpenStack,
doesn’t make it “software-defined”
Image by el cajon yacht club
Tools used depend on the task
Practice: Why Software Defined?
Better Technology.(scalability, flexibility, performance, reliability)
Image by Dean Johnson
Practice: Why Software Defined?
Simplicity. All the way.
Image by Dennis Skley
Practice: Why Software Defined?
Cost reduction. TCO.
Image by 401(K) 2012
Practice: Hardware (HW) - Design
Standard, cheap, commodity HW
Redundancy on system level
The “converged” concept:
All intelligence and functionality in software (SW)
Unified building blocks
Practice: Hardware (HW) - Price
“White box” server$6-8k
“Branded” server
$15-20k
VS.
OEM
SSD (1.6TB)$1.2k
“Branded” SSD
$3.4k
VS.
Modern server: 16-36 cores; 256GB+ RAM
5 - 15%
Practice: Hardware (HW) - Efficiency
Take 5-15% of these resources – make SAN irrelevant
Practice: convergence / hyper-convergence
Efficiency and TCO reduction
Compute, network and storage become one
Standardization and simplicity
OS
Virtualization
Cloud Management
Economical at up to several racks
App1
App2
App3
VM <$250 (2GB RAM, 1 vCPU, 30GB storage)
Storage
Practice: rack-level architecture
When doing infrastructure on a rack level
Additional efficiencies over converged/hyper-converged
There are some counter-intuitive choices – more expensive CPUs, bigger SSDs, etc.
Image by Robert
Practice: data-center level architecture
Applicable if you are operating your own datacenters
Additional savings over the lifetime
Software defined is the Future
ScalableSimple (all the way)
Economical
A, B, C
© 2015 StorPool. All rights reserved.
Boyan Ivanov
CEO, StorPool
Storage
www.storpool.com
@storpool
Thank you
