Hi,
We are trying to use corosync to bridge communication across two or more
ATCA chassis. We do not want to run the corosync daemon on all the
blades of the ATCA chassis, but we would need the applications running
on all the cards to be able to talk to the centralized corosync deamon
-- for example to use the cpg service.
The existing architecture of corosync does not seem to support the above
mentioned use case as it assumes that the corosync daemon is running on
all the cards and the client and server are located on the same
node/card. This restriction arises mainly due to use of unix domain
sockets.
Can we achieve the above use case if the underlying IPC is changed to
TCP instead of unix sockets? What other issues do we need to address to
have this working?
Regards,
Shridhar
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
