open source vs. open standards by sage weil
TRANSCRIPT
STANDARDS ARE IMPORTANT
Standards like these allow interoperability and vendor-neutrality into today's data center
Fibre Channel, iSCSINFS, SMB
STANDARDS ARE IMPORTANT
Standards like these allow interoperability and vendor-neutrality into today's data center
Fibre Channel, iSCSINFS, SMB
BIG WIN FOR USERS
STANDARDS ARE IMPORTANT
Standards like these allow interoperability and vendor-neutrality into today's data center
Fibre Channel, iSCSINFS, SMB
BIG WIN FOR USERS
BIG WIN FOR APPLIANCE
VENDORS
STANDARDS ARE IMPORTANT
Standards like these allow interoperability and vendor-neutrality into today's data center
Fibre Channel, iSCSINFS, SMB
BIG WIN FOR USERS
BIG WIN FOR APPLIANCE
VENDORS
BIG WIN FOR OPEN SOURCE
STANDARDS BODIES
Should we engage directly in standards bodies?And how should we engage?
There are many organizations to choose from.IETF, SNIA, INCITS (T10, T11, etc.)
BIG PICTURE
What architectures will we be using in 5-10 years?Which ones are the most successful today?
BIG PICTURE
What architectures will we be using in 5-10 years?Which ones are the most successful today?
BIG PICTURE
What architectures will we be using in 5-10 years?Which ones are the most successful today?
Google Amazon Web Services
BIG PICTURE
What architectures will we be using in 5-10 years?Which ones are the most successful today?
Google Amazon Web Services
Can we make a similar leap with a standards-based approach?
QEMU/KVM BLOCK DEVICES
Open source virtual block devices can be built with less friction than standards-based interfaces.
New problems can be solved more efficiently and the API can be evolved over time.
QEMU/KVM BLOCK DEVICES
Open source virtual block devices can be built with less friction than standards-based interfaces.
New problems can be solved more efficiently and the API can be evolved over time.
STANDARDS CAN RESTRICT US
The use of standard protocols often makes:
Simple problems harder for
developers to solve.
Solutions slower and more expensive.
EXAMPLE 1: SCSIHost-attached drive with SCSI.
DEVICE
VOLATILE CACHE (RAM)
DURABLE STORE (PLATTER)
LINK
EXAMPLE 1: SCSIHost-attached drive with SCSI.
DEVICE
VOLATILE CACHE (RAM)
DURABLE STORE (PLATTER)
LINK
WRITE
EXAMPLE 1: SCSIHost-attached drive with SCSI.
DEVICE
VOLATILE CACHE (RAM)
DURABLE STORE (PLATTER)
LINK
WRITE
EXAMPLE 1: SCSIHost-attached drive with SCSI.
DEVICE
VOLATILE CACHE (RAM)
DURABLE STORE (PLATTER)
LINK
WRITE
EXAMPLE 1: SCSIHost-attached drive with SCSI.
DEVICE
VOLATILE CACHE (RAM)
DURABLE STORE (PLATTER)
LINK
FLUSH
EXAMPLE 1: SCSINetwork-attached drive with iSCSI or FC.
DEVICE
VOLATILE CACHE (RAM)
DURABLE STORE (PLATTER)
MULTIPATH LINKS
EXAMPLE 1: SCSINetwork-attached drive with iSCSI or FC.
DEVICE
VOLATILE CACHE (RAM)
DURABLE STORE (PLATTER)
MULTIPATH LINKS
WRITE
EXAMPLE 1: SCSINetwork-attached drive with iSCSI or FC.
DEVICE
VOLATILE CACHE (RAM)
DURABLE STORE (PLATTER)
MULTIPATH LINKS
WRITE
EXAMPLE 1: SCSINetwork-attached drive with iSCSI or FC.
DEVICE
VOLATILE CACHE (RAM)
DURABLE STORE (PLATTER)
MULTIPATH LINKS
FLUSH
EXAMPLE 1: SCSIThe real world (where failures happen).
LINK LINK
NON-VOLATILE CACHENON-VOLATILE CACHE
EXAMPLE 1: SCSIThe real world (where failures happen).
LINK LINK
NON-VOLATILE CACHENON-VOLATILE CACHE
WRITE
EXAMPLE 1: SCSIThe real world (where failures happen).
LINK LINK
NON-VOLATILE CACHENON-VOLATILE CACHE
WRITE
EXAMPLE 1: SCSIThe real world (where failures happen).
LINK LINK
NON-VOLATILE CACHENON-VOLATILE CACHE
EXAMPLE 1: SCSIThe real world (where reliable things are expensive).
LINK LINK
NON-VOLATILE CACHENON-VOLATILE CACHE
EXAMPLE 3: PANFS
A modern proprietary distributed file system
● Sane client/cluster protocol● Cache coherency● Scale-out data and metadata● Innovative hardware model
EXAMPLE 3: PANFS
PanFS's Linux kernel client was impractical to maintain.
● It's hard to maintain a closed source clientout of tree.
● It's hard to upstream an open sourceclient without an open source server.
EXAMPLE 3: PANFS
PanFS's Linux kernel client was impractical to maintain.
● It's hard to maintain a closed source clientout of tree.
● It's hard to upstream an open sourceclient without an open source server.
OPEN SOURCE ARCHITECTURES AVOID THIS PROBLEM.
OPEN SOURCE IS AN ADVANTAGE
Closed source vendors need these standards, but they can slow (or even prevent) innovation—be careful.
For open platforms, clients can be freely integrated, tested, and deploy without friction, and still provide interoperability and vendor neutrality.
OPEN SOURCE IS AN OPPORTUNITY
Open source architectures can develop at a faster pace due to lower ecosystem friction.
We should focus on APIs instead of protocol standards, and how they should evolve for future environments.
When open source dominates the environment, traditional vendors can play by our rules: running code, open source software, open collaboration.