Hi, this might be documented somewhere but I cannot find it. In what way does ovirt rely on vdsm:kvm being 36:36? Or can I just change the uid:gid everywhere and be golden? I need to change the uid:gid of vdsm:kvm to a value >1024. It has something to do with the setup of the diskstore I am supposed to use for this setup. The diskstore is a Synology which has all kinds of strange implications on the setup. Cheers, Stefan
This is a multi-part message in MIME format. --------------010203040307060507000405 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Should have send it the the ML: On 22-9-2014 16:27, Stefan Wendler wrote:
Hi,
this might be documented somewhere but I cannot find it.
In what way does ovirt rely on vdsm:kvm being 36:36? Or can I just change the uid:gid everywhere and be golden?
I need to change the uid:gid of vdsm:kvm to a value >1024. It has something to do with the setup of the diskstore I am supposed to use for this setup. The diskstore is a Synology which has all kinds of strange implications on the setup.
I use a Synology (DS211j and now DS214play) at home and have my storage for oVirt on it and no problems with 36:36. I think I modified /etc/exports after creating it so that it keeps the 36:36 permissions. /volume1/nfs/data 192.168.x.x/24(rw,async,no_wdelay,root_squash,insecure_locks,sec=sys,anonuid=36,anongid=36) Joop --------------010203040307060507000405 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-text-plain" wrap="true" graphical-quote="true" style="font-family: -moz-fixed; font-size: 14px;" lang="x-western"> <pre wrap="">Should have send it the the ML: On 22-9-2014 16:27, Stefan Wendler wrote: </pre> <blockquote type="cite" style="color: #000000;"> <pre wrap="">Hi, this might be documented somewhere but I cannot find it. In what way does ovirt rely on vdsm:kvm being 36:36? Or can I just change the uid:gid everywhere and be golden? I need to change the uid:gid of vdsm:kvm to a value >1024. It has something to do with the setup of the diskstore I am supposed to use for this setup. The diskstore is a Synology which has all kinds of strange implications on the setup. </pre> </blockquote> <pre wrap="">I use a Synology (DS211j and now DS214play) at home and have my storage for oVirt on it and no problems with 36:36. I think I modified /etc/exports after creating it so that it keeps the 36:36 permissions. /volume1/nfs/data 192.168.x.x/24(rw,async,no_wdelay,root_squash,insecure_locks,sec=sys,anonuid=36,anongid=36) Joop </pre> </div> <br> </body> </html> --------------010203040307060507000405--
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --c16hSnjeI5RwlMV3MxaBI3LiNudQxHUp3 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 09/23/2014 09:29, noc wrote:
Should have send it the the ML: =20 On 22-9-2014 16:27, Stefan Wendler wrote: =20
Hi,
this might be documented somewhere but I cannot find it.
In what way does ovirt rely on vdsm:kvm being 36:36? Or can I just change the uid:gid everywhere and be golden?
I need to change the uid:gid of vdsm:kvm to a value >1024. It has something to do with the setup of the diskstore I am supposed to use f= or this setup. The diskstore is a Synology which has all kinds of strange=
implications on the setup.
I use a Synology (DS211j and now DS214play) at home and have my storage=
for oVirt on it and no problems with 36:36. I think I modified /etc/exports after creating it so that it keeps the 36:36 permissions. /volume1/nfs/data =20 192.168.x.x/24(rw,async,no_wdelay,root_squash,insecure_locks,sec=3Dsys,= anonuid=3D36,anongid=3D36) =20 Joop =20
Hey, thanks for the answer. This definitely helped knowing somebody uses a Syno box with ovirt. After fiddling around for some hours I think I have this working now. But especially the nfs and the permission parts are really really fragile. One wrong click and everything goes to hell. And as I have figured out this wont always happen instantaneously. But sometimes only after a reboot. I personally cannot recommend |ynology as a Diskstore for ovirt and don't feel too comfortable with this solution. I personally favour a FreeBSD box with decent zfs support. Cheers, Stefan --c16hSnjeI5RwlMV3MxaBI3LiNudQxHUp3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlQhffcACgkQ01vvrYDXSqvm/wCggSITLqDXoDNKpDvSNqEFbI71 aYEAn1SzMadsoc4bQ04Q1G0RFULXrcAI =yz8w -----END PGP SIGNATURE----- --c16hSnjeI5RwlMV3MxaBI3LiNudQxHUp3--
participants (2)
-
noc -
Stefan Wendler