Make it possible to provide additional workspace mount

[ghost]

Some customer use cases imply mounting host directories in workspace container. Currently it is impossible both on user and admin level.

It should be possible for an installation admin to provide host paths to be mounted in workspace containers that start on a machine node.

[ghost]

@bmicklea please comment on urgency and motivation for this issue.

[MuhamadSherif]

Hi @eivantsov , yes I have the same issue since my product needs to mount to a NAS server, and after some search I found it's impossible to do that directly from the container and I need to mount the host to the NAS server first then to mount container to host.
but unfortunately I cannot do that using codenvy.

[TylerJewell]

@eivantsov - I am starting to see variations of this come up from different customers. You said specifically that an admin would need to identify the host paths. Maybe it would be better to have two modes:
1: Admin defined, where admin must define list of all host paths available, or:
2: User defined, where the user can provide any set of host paths they would like.

How would a user who is authoring a workspace recipe know about, and be able to use these mounts? Would they just magically work inside the workspace, or would we display something to the user, perhaps at the top of their terminal when it opens? Something like, "# Workspace has added host mounts for x, y, and z"

[ghost]

@TylerJewell as Codenvy On Prem admin I will not let any user mount any path - that's for sure. It's a huge risk of bringing the entire system down. A user can mount some critical Unix paths and mess up with files.

It should be admin who defines mount paths and mode (read only?).

Just my 2 cents.

[TylerJewell]

Yes, absolutely agree -it would be an admin selection only, and it would come with a lot of risk factors.

[ghost]

@tolusha is taking care of it in this issue - #499

[bmicklea]

Closing this as a duplicate of #499