Click here to load reader

Mike Tutkowski · PDF file 2017-12-14 · SOLIDFIRE . [email protected]: [email protected] sudo fdtsk -I Disk /dev/sda: 107.4 GB, 1073741824ee bytes 255 heads, 63

  • View
    2

  • Download
    0

Embed Size (px)

Text of Mike Tutkowski · PDF file 2017-12-14 · SOLIDFIRE . [email protected]:...

  • Mike Tutkowski - CloudStack software engineer; CloudStack PMC member

    - Focused on CloudStack's storage component

    SolidFire (http://solidfire.com) - Based out of Boulder, CO, USA

    - Develop a clustered, scale-out SAN technology (using industry-standard hardware)

    - Built from the ground up to support guaranteed Quality of Service (QoS) on a per-volume (logical unit) basis (min, max, and burst IOPS per volume)

    - All-flash architecture (no spinning disks)

    - Leverage compression, de-duplication, and thin provisioning (all inline) on a 4-KB block boundary across the entire cluster to drive down cost/GB to be on par with traditional disk-based SANs

    - Rest-like API to enable automation of all aspects of the SAN

  • Robust Support for Hypervisor Snapshots and

    Volume Snapshots

  • Hypervisor Snapshots

    ●Hypervisor snapshots are delta files created in the storage

    repository (for XenServer) or datastore (for ESXi) of the VDI (VHD

    file for XenServer/VMDK file for ESXi) that they are a snapshot of.

    ●CloudStack and the SolidFire plug-in support hypervisor snapshots

    through a property of a Compute or Disk Offering called Hypervisor

    Snapshot Reserve.

  • Volume Snapshots (also known as Backups)

    Volume snapshots have been traditionally stored as backups on

    secondary storage.

    ●CloudStack and the SolidFire plug-in support taking volume

    snapshots that exist on the SolidFire SAN instead of on secondary

    storage (i.e. not a backup).