Hi, I believe this message should have reached the BTS, so I'm forwarding it to the relevant bug.
My take on this: it's ok to add a "Should-Start: corosync" in the sheepdog init script. It will work regardless if we're using corosync or not (in other words: it can't hurt...). If I hear nothing form the current maintainer of Sheepdog, I'll do that. Thomas Goirand (zigo) -------- Original Message -------- Subject: Re: [PKG-Openstack-devel] Bug#759216: sheepdog: Init script missing corosync dependency Date: Mon, 25 Aug 2014 14:32:40 +0200 From: Valerio Pachera <[email protected]> Reply-To: Tracking bugs and development for OpenStack <[email protected]> To: Tracking bugs and development for OpenStack <[email protected]> Hi, I think this assumption is wrong. Sheepdog can use different cluster managers. Corosync has proven to be problematic in some situation and it doesn't support anyway more than 10 nodes. I strongly recommend to build sheepdog package so it supports also zookeeper. (If Im not worng, the package already use --enable-zookeper, but please check it). Zookeeper configuration is not more difficult than corosync, supports way more nodes, it doesn't need to be run on each node. Because we can't know what cluster manager the user is going to be using, I think it's better not to start nor require corosync as dependency. Valerio. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
