Add comments & misc review fixes

Lots of comments describing the heuristics, how it fits together and the
limitations.

In particular, we can't guarantee correct volume placement if the set of
zones is changing between allocating volumes.
This commit is contained in:
Justin Santa Barbara
2016-06-21 15:22:16 -04:00
parent 9c2566572d
commit dd94997619
4 changed files with 34 additions and 3 deletions

View File

@@ -49,7 +49,7 @@ type VolumeOptions struct {
// PV.Name of the appropriate PersistentVolume. Used to generate cloud
// volume name.
PVName string
// PVC.Name of the PersistentVolumeClaim, if we are auto-provisioning.
// PVC.Name of the PersistentVolumeClaim; only set during dynamic provisioning.
PVCName string
// Unique name of Kubernetes cluster.
ClusterName string