Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 2 Jun 2016 01:35:59 +0000 (UTC)
From: "Dima Spivak (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12762646.1418926212000.10200.1464831359823@Atlassian.JIRA>
In-Reply-To: <JIRA.12762646.1418926212000@Atlassian.JIRA>
References: <JIRA.12762646.1418926212000@Atlassian.JIRA> <JIRA.12762646.1418926212552@arcas>
Subject: [jira] [Updated] (HBASE-12721) Create Docker container cluster
 infrastructure to enable better testing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 02 Jun 2016 01:36:01 -0000


     [ https://issues.apache.org/jira/browse/HBASE-12721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dima Spivak updated HBASE-12721:
--------------------------------
    Summary: Create Docker container cluster infrastructure to enable better testing  (was: Extend hbase_docker to handle more useful use cases)

> Create Docker container cluster infrastructure to enable better testing
> -----------------------------------------------------------------------
>
>                 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)