Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of andrew.purtell@gmail.com
 designates 209.85.210.41 as permitted sender)
References: <op.we43n5x9mrx7t6@localhost.localdomain>
In-Reply-To: <op.we43n5x9mrx7t6@localhost.localdomain>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <1F1CCA0F-51CA-4B42-81C3-C848AC493B04@gmail.com>
Cc: "user@hbase.apache.org" <user@hbase.apache.org>
From: Andrew Purtell <andrew.purtell@gmail.com>
Subject: Re: Deployment Best Practices
Date: Wed, 30 May 2012 14:52:02 -0700
To: "user@hbase.apache.org" <user@hbase.apache.org>

We package into RPMs and manage configuration with Puppet.=20

Have a look at Apache Bigtop (incubating) for RPM and DEB package build harn=
ess and integration/smoke tests. It's a promising project.=20

You can also Google around for presentations on this topic by Arvind at Stum=
bleUpon. He talks about how they use tarballs for deploy and Puppet for conf=
iguration management and Fabric for coordination.=20

I'd say RPM package management and Puppet configuration management is common=
, maybe most common, but that last bit is just a guess.=20

Hope that helps,

     - Any

On May 30, 2012, at 2:08 PM, "Peter Naudus" <pnaudus@dataraker.com> wrote:

> Hello All,
>=20
> Is there a "community standard" / "best" way to deploy HBase to a cluster?=
 We're in the process of setting up a ~15 node cluster and I'm curious how y=
ou all go about your deployments. Do you package the code into an RPM, place=
 it into a central YUM repository, and then drive the install via Puppet? Or=
 do you rsync the code and use shell scripts? Or all the above?
>=20
> Thanks so much for your input!
>=20
> ~ Peter