Persistent disks proposal

A stake in the ground ... something to evolve into a working implementation.
I just verified with the GCE and AWS APIs.  1 GB is their smallest option.


----- Original Message -----
From: "N. Harrison Ripps" <notifications@github.com>
To: "smarterclayton/kubernetes" <kubernetes@noreply.github.com>
Cc: "Mark Turansky" <mturansk@redhat.com>
Sent: Tuesday, November 25, 2014 9:12:01 AM
Subject: Re: [kubernetes] Persistent disks proposal (#1)

> +
> +    // Unique name of the PD resource. Used to identify the disk in a cloud provider
> +    // Optional.  New volumes are created if an existing one is not specified
> +    PDName      string
> +    
> +	// Required: Filesystem type to mount.
> +	// Must be a filesystem type supported by the host operating system.
> +	// Ex. "ext4", "xfs", "ntfs"
> +    FSType      string
> +    
> +	// Optional: Partition on the disk to mount.
> +	// If omitted, kubelet will attempt to mount the device name.
> +	// Ex. For /dev/sda1, this field is "1", for /dev/sda, this field is 0 or empty.
> +    Partition   int
> +    
> +    // the requested disk size in gb

Would it be useful to break out the order of magnitude (GB) as another variable? I can imagine private cloud use cases where smaller (<1GB) storage denominations might be desirable.

---
Reply to this email directly or view it on GitHub:
https://github.com/smarterclayton/kubernetes/pull/1/files#r20864314