Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <9212259.464031285776994103.JavaMail.jira@thor>
Date: Wed, 29 Sep 2010 12:16:34 -0400 (EDT)
From: "Konstantin Boudnik (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Created: (HADOOP-6980) Add abstraction layer to isolate
 cluster deployment mechanisms
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Add abstraction layer to isolate cluster deployment mechanisms
--------------------------------------------------------------

                 Key: HADOOP-6980
                 URL: https://issues.apache.org/jira/browse/HADOOP-6980
             Project: Hadoop Common
          Issue Type: Improvement
          Components: test
    Affects Versions: 0.22.0
            Reporter: Konstantin Boudnik


Certain types of system tests might require to perform a fresh deployment of a test cluster (e.g. upgrade tests, and similar).
This can be achieved by having an external way of deploying clusters and then running the tests. However, this won't work if re-deployment is needed in a middle of such test execution. In this case, Herriot needs to be able to explicitly call a deployment mechanism to carry on the process.

However, there are many possible ways of implementing cluster deployment and Herriot couldn't possibly be aware about all of them nor should be able to satisfy all their different interfaces. Thus an abstract interface should isolate plug-gable concrete implementations.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.