Thank Steven for your answers. What do you mean by "cluster engine" ? Will you qualify Pacemarker as a "cluster engine" ? If I understand you, OpenAIS can not be used as a standalone library. Any corosync process(es) should run in order to use OpenAIS ? I have quickly seen some patch for a quorum_vote C function/file. Is a cluster is running after a quorum vote ?
Sorry for all these questions, but I haven't seen any documentation about corosync and its architecture. As I am interested by cluster issue I try to understand your project because it seems to be the last hope to have a decent cluster, as FailSafe has no more support, and heartbeat (v1 and v2) does not match with my opinion of a cluster manager for non aware HA applications. I haven't try the latest Red Hat Cluster, but the earlier version was not enought advanced for me. Thank in advance for your lights. Regards, -Rv Steven Dake a écrit : > Corosync is a cluster engine which uses plugins (called service engines) > and provides services to the plugin users. > > OpenAIS is designed now as plugins to the corosync cluster engine. > OpenAIS now consists of service engine plugins as well as libraries the > user links with that connects to those service engines. > > I hope that clears up the architecture a bit. > > Regards > -steve > > -- Hervé GAUTIER _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
