Re: [Openhpi-devel] Multiple Daemons from one client

[Renier M. <re...@li...>]

On Tue, 2008-08-05 at 12:30 +1200, Luuk Paulussen wrote:
> Hi All,

Hello Luuk

> 
> I've seen a few hints here and there about the ability to connect to
> multiple daemons from one client.  How do you set this up?  Currently
> we do something hacky along the lines of setting the
> OPENHPID_DAEMON_HOST environment variable to the host we want, opening
> a session and then repeating this process for each host we want to
> connect to.  I'm hoping that there is a better way!

This feature hasn't been announced much since it is still in alpha
stage. It lets you configure which domain maps to which openhpi daemon.
Then when you do saHpiSessionOpen(domain_id), the client will contact
the openhpi daemon which corresponds to that doamin. As you can see,
this also changes the way domains are treated currently in OpenHPI and
not just the client's ability to connect only one daemon.

Today it is:
one client -> one daemon -> multiple domains

This feature is looking to enable this:
one client -> 1st daemon -> one domain
           -> 2nd daemon -> one domain
           ...etc.

So that multiple domains are enabled by way of multiple daemons. More on
how to configure this below.

> 
> Also, I'm trying to upgrade our system to openhpi 2.12.0 and am
> noticing debug error messages about loading the client configuration
> file.  Is this a new requirement for clients?  The clients still seem
> to work fine without it.

Yes, the client library works without any client configuration file as
before. So don't worry about the debug message.

> Having a look through the code seems to
> suggest that the client config file should contain things about host,
> domain, port and/or default.

The client configuration file should be at
$sysconfdir/openhpi/openhpiclient.conf

This is an example of what the contents could be:

# Specified default domain. Optional
# If not specified, default domain host is localhost
# and default port is 4743
domain default {
	host = "localhost"
	port = 4743
}

domain 34 {
	host = "hpi43.mydomain.com"
	port = 4744
}

...etc....

If you saHpiSessionOpen(34), your session would be connected to
hpi43.mydomain.com, for example.

	--Renier