summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichelle Au <msau@google.com>2017-03-30 13:04:34 -0700
committerMichelle Au <msau@google.com>2017-03-30 13:04:34 -0700
commitcee4bca172d77a8d203d56887efaf3d757f23eba (patch)
tree1da28564774b19d11939e2adffbae16d5bcb2332
parent4893f8f94272db2d970638a6133f7ebe5327ab3f (diff)
Clarify that block access can be considered as a separate feature.
-rw-r--r--contributors/design-proposals/local-storage-overview.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/contributors/design-proposals/local-storage-overview.md b/contributors/design-proposals/local-storage-overview.md
index b8fd489c..431c3678 100644
--- a/contributors/design-proposals/local-storage-overview.md
+++ b/contributors/design-proposals/local-storage-overview.md
@@ -468,6 +468,7 @@ Since local PVs are only accessible from specific nodes, a new PV-node associati
```
### Bob manages a specialized application that needs access to Block level storage
+Note: Block access will be considered as a separate feature because it can work for both remote and local storage. The examples here are a suggestion on how such a feature can be applied to this local storage model, but is subject to change based on the final design for block access.
1. The cluster that Bob uses has nodes that contain raw block devices that have not been formatted yet.
2. The same addon DaemonSet can discover block devices in the same directory as the filesystem mount points and creates corresponding PVs for them with a new `volumeType = block` field. This field indicates the original volume type upon PV creation.