diff options
| author | Xingcai Zhang <zhangxingcai@ghostcloud.cn> | 2017-11-04 23:30:58 +0800 |
|---|---|---|
| committer | Xingcai Zhang <zhangxingcai@ghostcloud.cn> | 2017-11-04 23:30:58 +0800 |
| commit | d8942f32f68aaa359a649f33be1bc378626de516 (patch) | |
| tree | 5b71939027434993acddba03cf89706483c667ad | |
| parent | be6c11c89b2c5a2a58ed2157f219e3dac4700873 (diff) | |
fix typo words to implementation
| -rw-r--r-- | contributors/design-proposals/storage/raw-block-pv.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/contributors/design-proposals/storage/raw-block-pv.md b/contributors/design-proposals/storage/raw-block-pv.md index d4132c78..6ac48d1e 100644 --- a/contributors/design-proposals/storage/raw-block-pv.md +++ b/contributors/design-proposals/storage/raw-block-pv.md @@ -539,12 +539,12 @@ It is important the values that are passed to the container runtimes are valid a The accessModes would be passed as part of the options array and would need validate against the specific runtime engine. Since rkt doesn't use the CRI, the config values would need to be passed in the legacy method. -Note: the container runtime doesn't require a privileged pod to enable the device as RWX (RMW), but still requires privileges to mount as is consistent with the filesystem implemenatation today. +Note: the container runtime doesn't require a privileged pod to enable the device as RWX (RMW), but still requires privileges to mount as is consistent with the filesystem implementation today. The runtime option would be placed in the DeviceInfo as such: devices = append(devices, kubecontainer.DeviceInfo{PathOnHost: path, PathInContainer: path, Permissions: "XXX"}) -The implemenation plan would be to rename the current makeDevices to makeGPUDevices and create a separate function to add the raw block devices to the option array to be passed to the container runtime. This would iterate on the paths passed in for the pod/container. +The implementation plan would be to rename the current makeDevices to makeGPUDevices and create a separate function to add the raw block devices to the option array to be passed to the container runtime. This would iterate on the paths passed in for the pod/container. Since the future of this in Kubernetes for GPUs and other plug-able devices is migrating to a device plugin architecture, there are still differentiating components of storage that are enough to not to enforce alignment to their convention. Two factors when |