[Ovirt-devel] Ovirt Host Tasks

[Simo Sorce]

On Mon, 2008-03-17 at 12:35 -0400, Hugh O. Brock wrote:
> There is another interesting possibility we might want to look at in
> the
> medium term. We are actively working on ways to use amqp as part of
> our infrastructure. If a machine has an identity via a keytab and an
> IP address via DHCP, I imagine it's possible to retrieve the remaining
> necessary config information by sending a message to a known alias?
> This relieves the oVirt host of having to know the precise address of
> the management server. Something to think about at least.

Both IPA and AMQP is in need of various auto-discovery features and they
will involve using DNS SRV records. I think a service record that holds
the address(es) of the manager should be used.

The only gotcha about using DNS is that you must either know which
domain you have to bind to, or have another way to provide that.
Assuming that DHCP will ship the base default domain (where IPA stores
the _kerberos SRV record and I assume O-Virt may store something
similar) it may all just work.

But this would be quite static (and all clients would point to one
single Manager for the full IPA Realm), I assume big organizations may
want to have multiple instances (reliability, fault-tolerance) in
different locations on the network, so perhaps supporting the full
auto-discovery we are going to implement in IPA/AMQP will probably make
sense.

Discussion on the details of auto-discovery is open if anyone wants to
chime in, as we are still deciding how to exactly implement it in terms
of protocols and conventions.

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York