Hi,
On Mon, November 21, 2016 4:21 pm, Mark Steckel wrote:
----- Derek Atkins <derek(a)ihtfp.com> wrote:
> Hi,
>
> Mark Steckel <mjs(a)fix.net> writes:
>
> > Thanks all who have responded so far.
> >
> > Advice so far seems to be:
> > * Use 'screen' when deploying. Easy
> > * Don't use/disable Network-Manager. Easy
> > * Preconfigure the ovirtmgmt bridge. I've got questions...
> >
> > The server has a public /32 as the primary IP, and a public /29 which
> > will be used for the VMs.
> >
> > Besides creating the ovirtmgmt bridge is there anything specific for
> > how I should configure it?
>
> My recommendation is that you just set up non-NM-controlled static
> network using your public /32. Then the hosted-engine --deploy process
> should take that config and apply it to ovirtmgmt bridge. At least,
> that's what happened for me when I did it. I don't think you need to
> set up the ovirtmgmt bridge manually.
This is what I initially did and then lost Internet access when the /32
was migrated to the ovirtmgmt bridge.
I then used KVM console access to access the box, but it could no longer
access it's public gateway. It was at this point then I surmised that
something was amiss.
Hmm. That's odd. "If worked for me"..
What did your /etc/sysconfig/network-scripts/ifcfg-<dev> file look like?
(And what does the ifcfg-ovirtmgmt file look like)?
>
> As for the /29 -- don't worry about it now, that would be a routing
> issue you can apply later. Is it the same network as the /32? Or is it
> a different network?
Different.
I assume both networks are available on your host interface?
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com
www.ihtfp.com
Computer and Internet Security Consultant