[Users] Is it possible to run the node and engine on the same box?

[Livnat Peer]

On 19/02/12 19:21, Brent Bolin wrote:
> On Sun, Feb 19, 2012 at 10:10 AM, Doron Fediuck <dfediuck at redhat.com> wrote:
>> On 19/02/12 15:33, Brent Bolin wrote:
>>> Assume if it was possible fedora 16 with the additional repos would be
>>> suggested.
>>
>> Hi Brent,
>> ovirt-node is read-only by nature (with the exception of some configurations).
>> This means you cannot simply install rpm's on it. Instead both vdsm and the
>> engine core needs to be pre-built on the node. This is not trivial, as the
>> engine core requires many packages.
>>
>> If we assume you're using standard Fedora to be able to install rpm's, then
>> we come to the next set of issues; co-hosting engine core with vdsm. There
>> are things that need to be taken care of such as-
>> - Adding the same host as a new host into the engine will cause reboot, which
>> is not a good thing to do to the engine core during the installation process
>> of the host..

We are adding a flag (host property) to avoid host reboot at the end of
host installation.
This will be available soon and we are thinking to expose it only
through the API (not in the UI).


>> - Fencing.... the co-hosted machine should not be fenced under any circumstances,
>> in order to protect the engine core.
>> - Networking... networking changes may impact the engine core as well. So here again
>> we need to be careful.
>>
>> To conclude,
>> it is possible to create a co-hosted machine used both by vdsm and engine-core.
>> However, we need to verify the machine is not being rebooted. There are thoughts
>> and maybe some work on achieving it, but it will take some time.
>> --
>>
>> /d
>>
>> “Funny,” he intoned funereally, “how just when you think life can't possibly get any worse it suddenly does.” --Douglas Adams, The Hitchhiker's Guide to the Galaxy
> 
> Thanks for your reply.
> 
> I've used XEN, ESX and now i'm focusing on KVM because that's where I
> think the technology is going.  Very interested in the GUI management
> and not having to use windows for the engine database(ESX) or windows
> client(vSphere).
> 
> The ovirt node ISO is still pretty buggy from what I've seen.  stdout
> errors and the install just not working without more then one attempt.
>  Even tried breaking in as root to install ovirt engine repos without
> success.  Getting some odd errors when trying to set the root password
> to a known value.
> 
> Any way I was able to install ovirt engine and vdsm by looking at the
> install guides using fedora 16 x86_64 DVD ISO.  Doing a minimal
> install.
> 
> Was able to bring up the mgmt UI.  Saw exactly what your talking about
> requiring a reboot when adding a node host.  Wasn't sure if that's the
> way it's suppose to work or not.  Kinda like the surgeon working on
> his own hands!.  Don't think the node registration fully installed
> itself because it re-booty up'ed itself.
> 
> Networking isn't very clear if the above was tried.  Example: using
> loopback 127.0.0.1 as the host node address.  Not sure if the node
> host has to be reachable via a bridged network etc... .
> 
> Thought it was worth the question because I'd like to know.
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users