RE: [Users] Remote storage and migration
Hello, list. I've been using OpenVZ since last year. Now I'd like to configure the cluster I've been using to use remote storage, so that migrations do not require to copy the container's filesystem. Reading the wiki and the forum, I've learned that NFS is not recommended, but I don't know why. iSCSI has been suggested as a way to go, although no success story supported the suggestion. Finally, somebody said that he was using GFS without problems, but one of the OpenVZ developers said (at that time) that GFS was not recommended due to stability issuess. I've been told that remote storage with OpenVZ is not a well-known area, but I have to ask anyway, so as to leverage in previous experiences. Any information is welcome, even more the problems that were found with each approach, so that I know were to go and were not to. I am also interested to make openvz more flexible. The new proxmox release will have a very flexible storage model which supports iscsi/nfs/lvm, but it is currently KVM only, because openvz lacks that feature. I am especially interested in mounting devices (lvm) as container root, something like # mount -t ext3 /dev/xzy /var/lib/vz/private/777 Looking at the source (vzctl/src/fs_simfs.c vz_mount) it seem to be easy to implement. If ROOT is a device we use 'ext3' instead of 'simfs'. But I have no idea how this interacts with the rest of the openvz code? Does quotas work that way? Or would it be better to use an additional configuration option to specify the root device: ROOTDEV=/dev/xzy ROOT=... PRIVATE=... We then simply mount ROOTDEV first, then use simfs as usual? I can write that code if some of the OpenVZ developers give me some hints. - Dietmar ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
AW: [Users] Remote storage and migration
Hi, I am also interested to make openvz more flexible. The new proxmox release will have a very flexible storage model which supports iscsi/nfs/lvm, but it is currently KVM only, because openvz lacks that feature. I am especially interested in mounting devices (lvm) as container root, something like # mount -t ext3 /dev/xzy /var/lib/vz/private/777 see here: http://www.atombot.de/blog/2008/12/09/openvz-premount-und-postmount-unte r-linux/ (unfortunately german) You can use the script /etc/vz/conf/vps.mount for this purpose. This can mnount the FS as requested. We then simply mount ROOTDEV first, then use simfs as usual? Like this ... (me not a developer ..) Regards, Robert ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] Re: Enabling hardware access in VPS
Vidhya Nagarajan пишет: I don't see this file. I only find /etc/vz/conf/$VEID.conf. You should create /etc/vz/conf/$VEID.mount file for this. Please look on my sample conf: mysrv # cat /etc/vz/conf/114133.mount --- #!/bin/bash . /etc/vz/vz.conf mount -n -o bind /mnt/data $VE_ROOT/mnt/data --- no umount script is needed. You could refer to http://forum.openvz.org/index.php?t=msggoto=12027; for more details. This way describe how to mount a folder from HN to VE. But I don't know does this solution help you with your /proc/diskstats file. Can someone please help me figure this out! Thanks, Vidhya On Fri, Jul 31, 2009 at 3:34 PM, Suno Ano suno@sunoano.org mailto:suno@sunoano.org wrote: Vidhya How can the /proc/diskstats file be made available to a VPS? I would try with the mount/umount scripts i.e. those are executed when a VE gets mounted/umounted - /etc/vz/conf/$VEID.mount - /etc/vz/conf/$VEID.umount -- Best wishes, Sergej Kandyla http://paix.org.ua ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
[Users] sharing files + locking through mount --bind ?!
Hi, I'm working on a setup with OpenLDAP, Samba, and NFS. For the users I want to use NFS for their home directories, and then they would authenticate against LDAP on the fileserver VE (OpenVZ), which also offers samba. Files inside that VE are mounted with --bind from the host system. I just thought about the option of not using samba mounting on the desktops, but using mount --bind to show the file shares on the server inside their (NFS mounted) home directories. I wondered how things are when it comes to locking. I assume that there's no locking of files, when some users would be opening the same file at the same time, but I'm not sure about that. Is there any filelocking with the mount --bind option in OpenVZ ? Where do I find more information on this ? TIA ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
