On Fri, Dec 14, 2012 at 7:34 AM, Andrei Savu <[email protected]> wrote: > Hi guys, > > There is no secret that at Axemblr we are using Apache Whirr for > provisioning and initial basic cluster configuration for Hadoop. As soon as > the machines are running we configure Hadoop by leveraging APIs from > existing tools like Cloudera Manager or Ambari. > > All the orchestration needed to make this happen is not trivial if you want > the final system to be predictable, robust, restartable and easy to inspect > while running. > > A few months ago we've realised that we need to re-work the machine > provisioning layer from Whirr and build a system that has the following > features
This looks really interesting and I can see how it can be very useful for things like buildouts of classes of virtual nodes. The question I have is this -- once you're done with automating the base-line provisioning, what's your involvement with higher-level orchestration? It seems that one way for you to handle this is to hand off to the existing cluster orchestrators like CM and Ambari. This is fine, but I'm more interested in how extensible your architecture is. So here's my favorite use case -- suppose I need to stand up a Zookeeper cluster from Zookeper RPM packages from the Bigtop distribution. Could you, please, walk me through each step? The more detailed the better! Thanks, Roman.
