On 30 May 2017, at 08:31, Yaniv Kaul <ykaul@redhat.com> wrote: =20 =20 =20 On Mon, May 29, 2017 at 2:25 PM, Andy Gibbs <andyg1001@hotmail.co.uk = <mailto:andyg1001@hotmail.co.uk>> wrote: On 29 May 2017 08:22, Sandro Bonazzola wrote:
Hi, so if I understood correctly, you're trying to work on a single = host deployment right? Or are you just trying to replace the bare metal all-in-one 3.6 in a = context with more hosts? If this is the case, can you share your use case? I'm asking because = for single host installations there are other solutions that may fit = better than oVirt, like virt-manager or kimchi = (https://github.com/kimchi-project/kimchi = <https://github.com/kimchi-project/kimchi>) =20 Sandro, thank you for your reply. =20 I hadn't heard about kimchi before. Virt-manager had been discounted = as the user interface is not really friendly enough for non-technical =
=20 I would say that the primary use-case is this: We want a server which = individual employees can log into (using their active directory logins), = access company-wide "public" VMs or create their own private VMs for =
f this is fixed in 4.1, but our work-around is to have a dummy VM =
--Apple-Mail=_6B48C156-A9B7-4D11-9AC3-D96A130B085A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 people, which is important for us. The simple web interface with oVirt, = however, is excellent in this regard. their own use (if permitted). Users should be able to start and stop = the "public" VMs but not be able to edit or delete them. They should = only have full control over the VMs that they create for themselves. = And very importantly, it should be possible to say which users have the = ability to create their own VMs. Nice to have would be the ability for = users to be able to share their VMs with other users. Really nice to = have would be a way of detecting whether VMs are in use by someone else = before opening a console and stealing it away from the current user! = (Actually, case in point, the user web interface for oVirt 3.6 always = starts a console for a VM when the user logs in, if it is the only one = running on the server and which the user has access to. I don't know i that always runs and displays a graphic with helpful text for any that = see it! Bit of a nuisance, but not too bad. We never found a way to = disable this behaviour.)
=20 This sounds like a bug to me, if guest agent is installed and running = on the guest. I'd appreciate if you could open a bug with all relevant details.
=20 =20 We started off some years ago with a server running oVirt 3.4, now = running 3.6, with the all-in-one plugin and had good success with this. = The hosted engine for oVirt 4.1 seemed to be the recommended "upgrade =
=20 Ultimately once this first server is set up we will want to convert =
nothing to do with agent but rather the =E2=80=9Cconnect = automatically=E2=80=9D checkbox per user. Just uncheck it for the user. You may also check out https://github.com/oVirt/ovirt-web-ui for a = modern simplified user portal. It=E2=80=99s not fully complete, it=E2=80=99= s missing this =E2=80=9Cconnect automatically=E2=80=9D functionality, so = it=E2=80=99s perfect for you:) Thanks, michal path" -- although we did also start with entirely new server hardware. the old server hardware to a second node so that we can balance the load = (we have a number of very resource-hungry VMs). This would be our = secondary use-case. More nodes may follow in future. However, we don't = see the particular need to have VMs that migrate from node to node, and = each node will most likely have its own storage domains for the VMs that = run on it. But to have one central web interface for managing the whole = lot is a huge advantage.
=20 Coming then to the storage issue that comes up in my original post, we = are trying to install this first server platform, keeping the node, the = hosted engine, and the storage all on one physical machine. We don't = (currently) want to set up a separate storage server, and don't really = see the benefit of doing so. Since my first email, I've actually = succeeded in getting the engine to recognise the node's storage paths. = However, I'm not sure it really is the right way. The solution I found = was to create a third path, /srv/ovirt/engine, in addition to the data = and iso paths. The engine gets installed to /srv/ovirt/engine and then = once the engine is started up, I create a new data domain at = node:/srv/ovirt/data. This then adds the new path as the master data = domain, and then after thinking a bit to itself, suddenly the = hosted_storage data domain appears, and after a bit more thinking, = everything seems to get properly registered and works. I can then also = create the ISO storag e domain. =20 Does this seem like a viable solution, or have I achieved something = "illegal"? =20 Sounds a bit of a hack, but I don't see a good reason why it wouldn't = work - perhaps firewalling issues. Certainly not a common or tested = scenario. =20 =20 I am still not having much luck with my other problem(s) to do with = restarting the server: it still hangs on shutdown and it still takes a = very long time (about ten minutes) after the node starts for the engine = to start. Any help on this would be much appreciated. =20 Logs would be appreciated - engine.log, server.log, perhaps journal = entries. Perhaps there's race between NFS and Engine services? Y. =20 =20 Thanks Andy _______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users = <http://lists.ovirt.org/mailman/listinfo/users> =20 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_6B48C156-A9B7-4D11-9AC3-D96A130B085A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div = class=3D"">On 30 May 2017, at 08:31, Yaniv Kaul <<a = href=3D"mailto:ykaul@redhat.com" class=3D"">ykaul@redhat.com</a>> = wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div = dir=3D"ltr" class=3D""><br class=3D""><div class=3D"gmail_extra"><br = class=3D""><div class=3D"gmail_quote">On Mon, May 29, 2017 at 2:25 PM, = Andy Gibbs <span dir=3D"ltr" class=3D""><<a = href=3D"mailto:andyg1001@hotmail.co.uk" target=3D"_blank" = class=3D"">andyg1001@hotmail.co.uk</a>></span> wrote:<br = class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 = .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On 29 = May 2017 08:22, Sandro Bonazzola wrote:<br class=3D""> > Hi, so if I understood correctly, you're trying to work on a single = host<br class=3D""> > deployment right?<br class=3D""> > Or are you just trying to replace the bare metal all-in-one 3.6 in = a context<br class=3D""> > with more hosts?<br class=3D""> > If this is the case, can you share your use case? I'm asking = because for<br class=3D""> > single host installations there are other solutions that may fit = better than<br class=3D""> > oVirt, like virt-manager or kimchi (<a = href=3D"https://github.com/kimchi-project/kimchi" rel=3D"noreferrer" = target=3D"_blank" class=3D"">https://github.com/kimchi-<wbr = class=3D"">project/kimchi</a>)<br class=3D""> <br class=3D""> </span>Sandro, thank you for your reply.<br class=3D""> <br class=3D""> I hadn't heard about kimchi before. Virt-manager had been = discounted as the user interface is not really friendly enough for = non-technical people, which is important for us. The simple web = interface with oVirt, however, is excellent in this regard.<br class=3D"">= <br class=3D""> I would say that the primary use-case is this: We want a server which = individual employees can log into (using their active directory logins), = access company-wide "public" VMs or create their own private VMs for = their own use (if permitted). Users should be able to start and = stop the "public" VMs but not be able to edit or delete them. They = should only have full control over the VMs that they create for = themselves. And very importantly, it should be possible to say = which users have the ability to create their own VMs. Nice to have = would be the ability for users to be able to share their VMs with other = users. Really nice to have would be a way of detecting whether VMs = are in use by someone else before opening a console and stealing it away = from the current user! (Actually, case in point, the user web = interface for oVirt 3.6 always starts a console for a VM when the user = logs in, if it is the only one running on the server and which the user = has access to. I don't know i<br class=3D""> f this is fixed in 4.1, but our work-around is to have a dummy VM = that always runs and displays a graphic with helpful text for any that = see it! Bit of a nuisance, but not too bad. We never found a = way to disable this behaviour.)<br class=3D""></blockquote><div = class=3D""><br class=3D""></div><div class=3D"">This sounds like a bug = to me, if guest agent is installed and running on the guest.</div><div = class=3D"">I'd appreciate if you could open a bug with all relevant = details.</div></div></div></div></div></blockquote><div><br = class=3D""></div>nothing to do with agent but rather the =E2=80=9Cconnect = automatically=E2=80=9D checkbox per user. Just uncheck it for the = user.</div><div>You may also check out <a = href=3D"https://github.com/oVirt/ovirt-web-ui" = class=3D"">https://github.com/oVirt/ovirt-web-ui</a> for a modern = simplified user portal. It=E2=80=99s not fully complete, it=E2=80=99s = missing this =E2=80=9Cconnect automatically=E2=80=9D functionality, so = it=E2=80=99s perfect for you:)</div><div><br = class=3D""></div><div>Thanks,</div><div>michal</div><div><br = class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div = dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div = class=3D"gmail_quote"><div class=3D""><br class=3D""></div><blockquote = class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc = solid;padding-left:1ex"> <br class=3D""> We started off some years ago with a server running oVirt 3.4, now = running 3.6, with the all-in-one plugin and had good success with = this. The hosted engine for oVirt 4.1 seemed to be the recommended = "upgrade path" -- although we did also start with entirely new server = hardware.<br class=3D""> <br class=3D""> Ultimately once this first server is set up we will want to convert the = old server hardware to a second node so that we can balance the load (we = have a number of very resource-hungry VMs). This would be our = secondary use-case. More nodes may follow in future. = However, we don't see the particular need to have VMs that migrate from = node to node, and each node will most likely have its own storage = domains for the VMs that run on it. But to have one central web = interface for managing the whole lot is a huge advantage.<br class=3D""> <br class=3D""> Coming then to the storage issue that comes up in my original post, we = are trying to install this first server platform, keeping the node, the = hosted engine, and the storage all on one physical machine. We = don't (currently) want to set up a separate storage server, and don't = really see the benefit of doing so. Since my first email, I've = actually succeeded in getting the engine to recognise the node's storage = paths. However, I'm not sure it really is the right way. The = solution I found was to create a third path, /srv/ovirt/engine, in = addition to the data and iso paths. The engine gets installed to = /srv/ovirt/engine and then once the engine is started up, I create a new = data domain at node:/srv/ovirt/data. This then adds the new path = as the master data domain, and then after thinking a bit to itself, = suddenly the hosted_storage data domain appears, and after a bit more = thinking, everything seems to get properly registered and works. I = can then also create the ISO storag<br class=3D""> e domain.<br class=3D""> <br class=3D""> Does this seem like a viable solution, or have I achieved something = "illegal"?<br class=3D""></blockquote><div class=3D""><br = class=3D""></div><div class=3D"">Sounds a bit of a hack, but I don't see = a good reason why it wouldn't work - perhaps firewalling issues. = Certainly not a common or tested scenario.</div><div = class=3D""> </div><blockquote class=3D"gmail_quote" style=3D"margin:0= 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br class=3D""> I am still not having much luck with my other problem(s) to do with = restarting the server: it still hangs on shutdown and it still takes a = very long time (about ten minutes) after the node starts for the engine = to start. Any help on this would be much appreciated.<br = class=3D""></blockquote><div class=3D""><br class=3D""></div><div = class=3D"">Logs would be appreciated - engine.log, server.log, perhaps = journal entries. Perhaps there's race between NFS and Engine = services?</div><div class=3D"">Y.</div><div = class=3D""> </div><blockquote class=3D"gmail_quote" style=3D"margin:0= 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br class=3D""> Thanks<br class=3D""> <div class=3D"HOEnZb"><div class=3D"h5">Andy<br class=3D""> ______________________________<wbr class=3D"">_________________<br = class=3D""> Users mailing list<br class=3D""> <a href=3D"mailto:Users@ovirt.org" class=3D"">Users@ovirt.org</a><br = class=3D""> <a href=3D"http://lists.ovirt.org/mailman/listinfo/users" = rel=3D"noreferrer" target=3D"_blank" = class=3D"">http://lists.ovirt.org/<wbr = class=3D"">mailman/listinfo/users</a><br class=3D""> </div></div></blockquote></div><br class=3D""></div></div> _______________________________________________<br class=3D"">Users = mailing list<br class=3D""><a href=3D"mailto:Users@ovirt.org" = class=3D"">Users@ovirt.org</a><br = class=3D"">http://lists.ovirt.org/mailman/listinfo/users<br = class=3D""></div></blockquote></div><br class=3D""></body></html>= --Apple-Mail=_6B48C156-A9B7-4D11-9AC3-D96A130B085A--