On 08/02/2012 08:52 PM, Eric Windisch wrote: >> >> What do you mean by "membership services"? > See the email today from Yun Mao. This is a proposal to have a pluggable > framework for integration services that maintain memberships. This was > originally desiged to replace the MySQL heartbeats in Nova, although there > will be a mysql-heartbeat backend by default as a drop-in replacement. There > is a zookeeper backend in the works, and we've discussed the possibility of > building a backend that can poll RabbitMQ's list_consumers.
Ah, yes. I've urged the team to use the term ServiceGroup instead of the Zookeeper "membership" terminology -- as membership has other connotations in Glance and Nova -- for instance, membership in a project/tenant really has nothing to do with the concept of service groups that can monitor response/hearbeat of service daemons. Best, -jay > This is useful for more than just Nova's heartbeats, however. This will > largely supplant the requirement for the matchmaker to build these backends > in itself, which had been my original plan (the matchmaker is already in > openstack-common). As such, it had already been my intent to have a > MySQL-backed matchmaker. The only thing new is that someone has actually > written the code. > > In the first pass, the intention is to leave the matchmaker in and introduce > the membership modules. Then, the matchmaker would either use the new > membership modules as a backend, or even replaced entirely. > > Regards, > Eric Windisch > > > _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
