Update documentation and add blog #607
Conversation
kerneltime
force-pushed
the
our2centblog.kerneltime
branch
2 times, most recently
from
46a5adf
to
5a0bc92
Compare
|
|
||
| Thanks to [Bruno Moura's](https://github.com/brunotm) excellent [work](https://github.com/vmware/docker-volume-vsphere/pull/597), Docker volume plugin for vSphere now supports selection of file system format when creating a new docker volume. | ||
|
|
||
| Ability to set a volume [read-only](https://github.com/vmware/docker-volume-vsphere/issues/274) is now supported by the plugin. The [admin cli](https://vmware.github.io/docker-volume-vsphere/user-guide/admin-cli/#set) allows the admin to set a volume to be read only. |
There was a problem hiding this comment.
Admin cli can be used to set to read-write also, both modes are supported. Allowing the user to temporarily make a volume as read-write, make changes and then set to read-write allowing multiple containers in the same VM to use the same volume contents - containers don't need to build all their libs into the docker image. 1. Create a volume, attach to a container (default is read-write).
2. Master the volume with libraries commonly used by the target application (or a cluster of apps that form a docker app bundle).
3. Use admin CLI to flip the access attribute to read-only.
4. Make those libraries available to the containers in the app bundle and they can all share the same libraries.
The container images themselves can be smaller as they share the libs and possibly binaries from read-only volumes. Allows distributing ready to use "app volumes" that containers can use.
There was a problem hiding this comment.
What you describe should be part of the user guide not the announcement
There was a problem hiding this comment.
Agree, just saying somewhere we should say how these features can get leveraged beyond just create/attach/detach/delete volumes.
There was a problem hiding this comment.
I agree with the both of you, but I think Govindan's text should go in Readme or doc in the same PR
kerneltime
force-pushed
the
our2centblog.kerneltime
branch
from
5a0bc92
to
14b2727
Compare
| @@ -0,0 +1,15 @@ | |||
| # New Release | |||
| We continue our montly release cycle with our [September release](https://github.com/vmware/docker-volume-vsphere/releases/tag/0.7) | |||
| # External Blog entries | ||
|
|
||
| - Cormac Hogan - [Docker Volume Driver for vSphere using policies on VSAN](http://cormachogan.com/2016/09/26/docker-volume-driver-vsphere-using-policies-vsan-short-video/) | ||
| - William Lam - [Getting Started with Tech Preview of Docker Volume Driver for vSphere - updated](http://www.virtuallyghetto.com/2016/05/getting-started-with-tech-preview-of-docker-volume-driver-for-vsphere.html) |
There was a problem hiding this comment.
There are more;
http://cormachogan.com/2016/06/01/docker-volume-driver-vsphere/
http://cormachogan.com/2016/06/03/docker-volume-driver-vsphere-short-video/
http://cormachogan.com/2016/06/09/docker-volume-driver-vsphere-virtual-san-vsan/
http://cormachogan.com/2016/07/29/using-vsphere-docker-volume-driver-run-project-harbor-vsan/
(New) http://cormachogan.com/2016/10/06/nice-enhancements-docker-volume-driver-vsphere-v0-7/
It may makes sense to categorize them in Intro, Advanced etc
There was a problem hiding this comment.
| # New Release | ||
| We continue our montly release cycle with our [September release](https://github.com/vmware/docker-volume-vsphere/releases/tag/0.7) | ||
|
|
||
| Thanks to [Bruno Moura's](https://github.com/brunotm) excellent [work](https://github.com/vmware/docker-volume-vsphere/pull/597), Docker volume plugin for vSphere now supports selection of file system format when creating a new docker volume. |
There was a problem hiding this comment.
nit: drop "excellent" please - the work is indeed excellent but IMO not needed for the announcement
|
|
||
| Thanks to [Bruno Moura's](https://github.com/brunotm) excellent [work](https://github.com/vmware/docker-volume-vsphere/pull/597), Docker volume plugin for vSphere now supports selection of file system format when creating a new docker volume. | ||
|
|
||
| Ability to set a volume [read-only](https://github.com/vmware/docker-volume-vsphere/issues/274) is now supported by the plugin. The [admin cli](https://vmware.github.io/docker-volume-vsphere/user-guide/admin-cli/#set) allows the admin to set a volume to be read only. |
There was a problem hiding this comment.
I agree with the both of you, but I think Govindan's text should go in Readme or doc in the same PR
|
@kerneltime - any update for this one ? |
not code/issues for public consumption. Also, fix the documentation part of #583
kerneltime
force-pushed
the
our2centblog.kerneltime
branch
from
14b2727
to
d1419ab
Compare
|
updated |
We need to curate external links of interest and post content that is
not code/issues for public consumption.
Also, fix the documentation part of #583