Justin Santa Barbara e711cbf912 GCE/AWS: Spread PetSet volume creation across zones ...

Long term we plan on integrating this into the scheduler, but in the
short term we use the volume name to place it onto a zone.

We hash the volume name so we don't bias to the first few zones.

If the volume name "looks like" a PetSet volume name (ending with
-<number>) then we use the number as an offset.  In that case we hash
the base name.

Fixes #27256

2016-06-17 23:27:31 -04:00

..

options

Reduce volume controller sync period

2016-05-30 09:59:31 +02:00

binder_test.go

Add label selector to match criteria for claims to volumes

2016-05-30 12:11:12 -04:00

controller_base.go

Rework PV controller to use util/goroutinemap

2016-06-09 13:49:04 +02:00

controller_test.go

Merge pull request #25865 from jsafrane/devel/pv-convert-from-12

2016-06-03 23:27:13 -07:00

controller.go

GCE/AWS: Spread PetSet volume creation across zones

2016-06-17 23:27:31 -04:00

delete_test.go

Big move and rename

2016-05-18 10:06:51 +02:00

framework_test.go

Introduce new kubelet volume manager

2016-06-15 09:34:08 -07:00

index_test.go

Add label selector to match criteria for claims to volumes

2016-05-30 12:11:12 -04:00

index.go

Fix typo and linewrap comments in PV controller

2016-06-02 15:50:07 -04:00

OWNERS

Move blunderbuss assignees into tree

2016-03-02 20:46:32 -05:00

provision_test.go

Generate shorter provisioned PV names.

2016-05-18 10:06:51 +02:00

recycle_test.go

Big move and rename

2016-05-18 10:06:51 +02:00

volume_host.go

Introduce new kubelet volume manager

2016-06-15 09:34:08 -07:00