Hi Andrew,
In the medium term I think that might be easier and more scalable -
oVirt should allow you to not have to deal with libvirt "plumbing".
Re-reading your original e-mail, I only now understand that you're using
the default network to setup NAT, and that you weren't adding iptables
rules
Lior,
The main purpose of this is for testing. Medium-term, my plan is to spin
up another VLAN and routable private subnet with DHCP to trunk our
virtualization hosts onto. That requires more people to get involved to
get the testing environment in place. I suppose I can spin up a DHCP
server
Hi Andrew,
On 17/12/14 22:39, Andrew Wagner wrote:
> All,
>
> I'm testing out oVirt for one of our projects that wants to try an
> all-in-one setup before going to a larger deployment. For their testing,
> they want to use the default NAT'd network from libvirtd on the host.
>
> I've install oVi
All,
I'm testing out oVirt for one of our projects that wants to try an
all-in-one setup before going to a larger deployment. For their testing,
they want to use the default NAT'd network from libvirtd on the host.
I've install oVirt, installed the extnet hook, enabled IP forwarding in
sysct
4 matches
Mail list logo