Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4BEB410A7F for ; Thu, 18 Dec 2014 18:11:14 +0000 (UTC) Received: (qmail 35279 invoked by uid 500); 18 Dec 2014 18:11:13 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 35126 invoked by uid 500); 18 Dec 2014 18:11:13 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 34884 invoked by uid 99); 18 Dec 2014 18:11:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Dec 2014 18:11:13 +0000 Date: Thu, 18 Dec 2014 18:11:13 +0000 (UTC) From: "Dima Spivak (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-12721) Extend hbase_docker to handle more useful use cases MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Dima Spivak created HBASE-12721: ----------------------------------- Summary: Extend hbase_docker to handle more useful use cases Key: HBASE-12721 URL: https://issues.apache.org/jira/browse/HBASE-12721 Project: HBase Issue Type: New Feature Reporter: Dima Spivak Assignee: Dima Spivak Some simple work on using HBase with Docker was committed into /dev-support as "hbase_docker;" all this did was stand up a standalone cluster from source and start a shell. Now seems like a good time to extend this to be useful for applications that could actual benefit the community, especially around testing. Some ideas: - Integration testing would be much more accessible if people could stand up distributed HBase clusters on a single host machine in a couple minutes and run our awesome hbase-it suite against it. - Binary compatibility testing of an HBase client is easiest when standing up an HBase cluster can be done once and then different client source/binary permutations run against it. - Upgrade testing, and especially rolling upgrade testing, doesn't have any upstream automation on build.apache.org, in part because it's a pain to set up x-node clusters on Apache infrastructure. This proposal, whether it stays under /dev-support or moves out into it's own top-level module ("hbase-docker" would conveniently fit the existing schema :-)), strives to create a simple framework for deploying "distributed," multi-container Apache HBase clusters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)