Adding Kimchi to oVirt node perhaps may be the easiest option. It can be
pretty useful for many situations and doesn't need such thing like
mounting NFS in localhost.
It is not nice to not have a All-in-One stable solution anymore as this
can help with its adoption for later growth.
oVirt-Cockpit looks nice and intresting.
Fernando
On 05/09/2016 05:18, Barak Korren wrote:
On 4 September 2016 at 23:45, zero four <zfnoc...@gmail.com> wrote:
...
I understand and acknowledge that oVirt is not targeted towards homelab
setups, or at least small homelab setups. However I believe that having a
solid configuration for such use cases would be a benefit to the project as
a whole.
As others have already mentioned, using the full oVirt with engine in
a single host scenario can work, but is not currently actively
maintained or tested.
There are other options originating from the oVirt community however.
One notable option is to use the Cockpit-oVirt plugin [1] which can
use VDSM to manage VMs on a single host.
Another option is to use the Kimchi project [2] for which discussion
for making it an oVirt project had taken part in the past [3]. It
seems that also some work for inclusion in oVirt node was also planned
at some point [4].
[1]: http://www.ovirt.org/develop/release-management/features/cockpit/
[2]: https://github.com/kimchi-project/kimchi
[3]: http://lists.ovirt.org/pipermail/board/2013-July/000921.html
[4]: http://www.ovirt.org/develop/release-management/features/node/kimchiplugin/
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
