OpenVZ storage

[drrighteous]

One of the benefits I saw in PVE was it's built in support for NFS storage volumes by default without having to modify underline configs. However, upon creating several OpenVZ containers in great hast I only realized after the fact that the web interface didn't seem to ask me where the storage should be for their filesystems.

While I do get that a VZ container isn't a fully virtualized environment like KVM, I am a little disappointed in the lack of configuribility to store said files on my NAS. I use my NAS because I don't have to limit my files and because its a RAIDed, many spindle environment. Is there a solution and can it be part of the web interface?

--David

 

[tom]

One of the benefits I saw in PVE was it's built in support for NFS storage volumes by default without having to modify underline configs. However, upon creating several OpenVZ containers in great hast I only realized after the fact that the web interface didn't seem to ask me where the storage should be for their filesystems.

While I do get that a VZ container isn't a fully virtualized environment like KVM, I am a little disappointed in the lack of configuribility to store said files on my NAS. I use my NAS because I don't have to limit my files and because its a RAIDed, many spindle environment. Is there a solution and can it be part of the web interface?

--David

OpenVZ does not support multiple storages.

I suggest you mount NFS via fstab on your host and do bind mounts into your containers.

see http://wiki.openvz.org/Bind_mounts

 

[drrighteous]

Thank you for the link. I do think however that it would be a very good offering of PVE to provide a web interface driven config option to select a NFS point to mount for the primary VZ storage. I have no personal problem configuring a fstab automount, however considering how well you've done with the rest of the interface, I thought it would be an excellent extension to your OpenVZ support.

--David

 

[tom]

Thank you for the link. I do think however that it would be a very good offering of PVE to provide a web interface driven config option to select a NFS point to mount for the primary VZ storage. I have no personal problem configuring a fstab automount, however considering how well you've done with the rest of the interface, I thought it would be an excellent extension to your OpenVZ support.

--David

the openVZ team does not support multiple storage types - and they have no real interest to implement it together with us. so if we go for this we are quite alone. therefore it makes no sense for us in the current stage.

 

[drrighteous]

No no, not suggesting you create an interface for multiple, merely one to configure the primary/only. AKA to do the same thing you suggested I do in fstab, only via the web interface.

--David

 

[tom]

No no, not suggesting you create an interface for multiple, merely one to configure the primary/only. AKA to do the same thing you suggested I do in fstab, only via the web interface.

--David

I see no real benefit on this. we want to keep the web interface clean and I assume this function would be used by only 0.01 % of our users, and only one time.

 

[SamTzu]

I can understand Tom's view point. (Although I think he's wrong about the 0.01%.) Going above OpenVZ groups head might not be smart and would certainly set us apart. But it looks like most of the Admin's I know are looking way's how to use cheap NAS storage in their virtualisation need's. (AoE solutions are most sought after.) And besides, It looks to me like OpenVZ is slowly dying from the lack of support. Maybe this would be the kind of support they are looking for.