Hi,
On Thu, December 8, 2016 11:15 am, Mark Steckel wrote:
>
> ----- Derek Atkins <derek(a)ihtfp.com> wrote:
>> Hi,
>>
>> Mark Steckel <mjs(a)fix.net> writes:
>>
>> > Am I missing and or just misunderstanding something here?
>> >
>> > Oh, and does ip_forwarding need to be set in the kernel? (ie
>> > net.ipv4.ip_forward=1)
>>
>> If you expect the host to act as the router for your /29, then yes, it
>> would need to forward packets. You will also need to set up the
>> firewall on the host to properly forward packets through.
>>
>> It honestly might be easier for you to get an actual router instead of
>> trying to force your host to act as both host+router. I suspect the
>> hosted-engine --deploy script wouldn't really know how to properly
>> handle the host as a router so it might either break that configuration
>> or at least not know how to set it up.
>
> Agreed. Unfortunately, the hosting company (Hetzner) providing the server
> requires the /29 to be on the host.
>
> Googling "ovirt Hetzner" shows that a number of people have attempted
this
> at Hetzner and have run into various problems. Here is one of the more
> relevant examples:
>
>
http://lists.ovirt.org/pipermail/users/2014-January/019785.html
> (check out the first link)
>
http://lists.ovirt.org/pipermail/users/2014-February/020913.html
>
> So it seems this is doable, but needs a bit more finesse than I've used so
> far.
Yeah, I suspect you will need to set up your engine NOT using the
appliance, but instead install CentOS and then the engine inside the VM.
This will give you more direct access to the engine VM, and should give
you the opportunity to set up the bridge routing during the process.
Makes sense, at least in concept.
But are you suggesting that I manually set up the vm for the engine (ie not use
"hosted-engine --deploy") and then manually run engine setup from w/i the vm?
> Mark
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com
www.ihtfp.com
Computer and Internet Security Consultant