Year(s) past, Renier has proposed a new scheme to handle Multiple Domains.
I have been having problems searching sourceforge openhpi-devel discussion
group the last few weeks, so I would like to revisit the new proposal with
the group to get everyone on the same page, to ensure that I understand the
new design correctly prior to checking in the new implementation.
(A)Proposed Design:
(A1) Proposed design overview
Client Application <--> openhpi Client Library/openhpiclient_conf |
(domain 0) <--> openhpi Daemon/openhpi_conf/Plugin <--> Target
| (domain 1) <--> openhpi Daemon/openhpi_conf/Plugin
| (domain 2) <--> openhpi Daemon/openhpi_conf/Plugin
| ......
| ......
| (domain n) <--> openhpi Daemon/openhpi_conf/Plugin
(A2) Proposed design has the following attributes:
(A2.1) Domains are defined in the newly introduced openhpiclient.conf file.
#domain 1 {
# host = my_domain1_host;
# port = my_domain1_port;
#}
#domain 2 {
# host = my_domain2_host;
# port = my_domain2_port;
#}
(A2.2) Domains; peers, parents; are managed at Client Application level
(A2.3) Each openhpi Daemon has only one domain, the default domain. There
is *no* domain stanza in the (old) openhpi.conf file
(A2.4) openhpi non-daemon mode will *no longer* works similarly to daemon
mode.
(B) Current Design (in sourceforge)
(B1) Current design overview
Client Application <--> openhpi Client Library <--> openhpi
Daemon/openhpi_conf/Plugin | (domain 0) <--> Target machine
| (domain 1)
| (domain 2)
| ...
| ...
| (domain n)
(B2) Current design has the following attributes
(B2.1) Domains are defined in file openhpi.conf (optional) domain
stanzas .
#domain 1 {
# # Required if peer_of is not used..
# entity_pattern = "{SYSTEM_CHASSIS,1}*{SBC_BLADE,.}"
# tag = "Blades on first chassis" # Optional
# ai_timeout = 0 # Optional. -1 means BLOCK. 0 is the
default.
# ai_readonly = 1 # Optional. 1 means yes (default), 0 means
no.
#}
#domain 2 {
# entity_pattern = "*{SBC_BLADE,.}{FAN,.}"
# tag = "All Blade Fans" # Optional
# child_of = 1 # Optional. 0 means the default domain.
#}
(B2.2) Domains; peers, parents; are managed within openhpi by values of
entity_pattern and child_of.
(B2.3) openhpi daemon has more than one domains within it
(B2.4) openhpi daemon propagates events to peer/parent domains by values of
entity_pattern and child_of
(B2.5) Even though openhpi non-daemon is not supported, non-daemon mode
works similarly to daemon mode
Regards,
--------------------------------------------------------------------------------------------
P. D. Phan
IBM Austin
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
