[Users] Post-Install Engine VM Changes Feasible?

[Joshua Dotson]

Hi,

I'm in the process of installing 3.4 RC(2?) on Fedora 19.  I'm using hosted
engine, introspective GlusterFS+keepalived+NFS ala [1], across six nodes.

I have a layered networking topology ((V)LANs for public, internal,
storage, compute and ipmi).  I am comfortable doing the bridging for each
interface myself via /etc/sysconfig/network-scripts/ifcfg-*.

Here's my desired topology:
http://www.asciiflow.com/#Draw6325992559863447154

Here's my keepalived setup:
https://gist.github.com/josh-at-knoesis/98618a16418101225726

I'm writing a lot of documentation of the many steps I'm taking.  I hope to
eventually release a distributed introspective all-in-one (including
distributed storage) guide.

Looking at vm.conf.in, it looks like I'd by default end up with one
interface on my engine, probably on my internal VLAN, as that's where I'd
like the control traffic to flow.  I definitely could do NAT, but I'd be
most happy to see the engine have a presence on all of the LANs, if for no
other reason than because I want to send backups directly over the storage
VLAN.

I'll cut to it:  I believe I could successfully alter the vdsm template (
vm.conf.in) to give me the extra interfaces I require.  It hit me, however,
that I could just take the defaults for the initial install.  Later, I
think I'll be able to come back with virsh and make my changes to the
gracefully disabled VM.  Is this true?

[1] http://www.andrewklau.com/ovirt-hosted-engine-with-3-4-0-nightly/

Thanks,
Joshua
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140315/e43477e7/attachment-0001.html>