As Lars mentioned yesterday, the reason for 2.1.4 is to allow time for
some additional project changes (both managerial and technical).
Part of these changes are to split the, currently monolithic,
Heartbeat project into logical components that can be updated/released/
replaced independently of the other pieces.
The current plan is to have 4 pieces (Two of which already exist. All
names are suggestions only).
In order of build sequence, they are:
* heartbeat-core
* heartbeat-stack
* pacemaker
* cluster-extras
Once we've finalized the contents of the different projects, we will
then decide what the packages those projects should produce.
People's thoughts on the details below would be much appreciated.
Andrew
* heartbeat-core (alternate name: cluster-core, lha-core)
This project would contain all the pieces relevant to the operation of
a single node.
Conceptually, the project would include:
- clplumbing (including logging)
- pils
- lrm
- resource agents
- stonith plugins + cli
* heartbeat-stack
This project would contain all the pieces relevant to the clusters
using the heartbeat messaging and membership layers.
Such clusters include all v1 clusters and the vast majority of v2/CRM/
Pacemaker clusters.
The pieces in this project can _optionally_ be replaced with the
OpenAIS messaging and membership layers.
Conceptually, the project would include:
- ccm
- cluster messaging API
- v1 resource manager (haresources)
- quorumd
- dopd
- ipfail
The next two projects are already operational and are presented mostly
for the sake of completeness.
* pacemaker
This project contains all the pieces relevant to the v2/CRM/Pacemaker
cluster resource manager.
Conceptually, the project includes:
- cts
- crm command line tools
- crm (cib, crmd, pengine, tengine, pingd, attrd, OpenAIS plugin)
* cluster-extras (currently known as pygui which isn't the best name)
This project contains high-level management tools and infrastructure.
Conceptually, the project includes:
- mgmtd
- cim
- snmp
- tsa_plugin
- gui (client)
SNMP is currently part of pacemaker but would be moved to live with
the other management pieces
Stonithd would either live in heartbeat-stack or pacemaker depending
on how fencing gets implemented for OpenAIS-based clusters.
Potentially it could also be by itself as a 5th project.
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
