Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 25 May 2011 22:05:48 +0000 (UTC)
From: "Eric Yang (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <123147266.43383.1306361148560.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HADOOP-6255) Create an rpm integration project
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/HADOOP-6255?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang updated HADOOP-6255:
------------------------------

    Attachment: HADOOP-6255-common-trunk-8.patch

hadoop-setup-single-node.sh utilize hadoop-setup-conf.sh to generate config=
uration.  haddop-setup-conf.sh is a utility for admin to generate config in=
 cwd, and admin can push out config files to remote nodes with admin's own =
utilities like rsync or scp.  However, the single-node setup was meant to s=
etup automatically with minimal config.  It is nicer to have config file ge=
nerated to HADOOP_CONF_DIR without storing a copy in cwd when hadoop-setup-=
single-node.sh invokes hadoop-setup-conf.sh. =20

The patch is revised to avoid writing to cwd, if automatic setup is choosen=
.

> Create an rpm integration project
> ---------------------------------
>
>                 Key: HADOOP-6255
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6255
>             Project: Hadoop Common
>          Issue Type: New Feature
>    Affects Versions: 0.20.203.0
>            Reporter: Owen O'Malley
>            Assignee: Eric Yang
>             Fix For: 0.20.203.0
>
>         Attachments: HADOOP-6255-branch-0.20-security-1.patch, HADOOP-625=
5-branch-0.20-security-10.patch, HADOOP-6255-branch-0.20-security-11.patch,=
 HADOOP-6255-branch-0.20-security-2.patch, HADOOP-6255-branch-0.20-security=
-3.patch, HADOOP-6255-branch-0.20-security-4.patch, HADOOP-6255-branch-0.20=
-security-5.patch, HADOOP-6255-branch-0.20-security-6.patch, HADOOP-6255-br=
anch-0.20-security-7.patch, HADOOP-6255-branch-0.20-security-8.patch, HADOO=
P-6255-branch-0.20-security-9.patch, HADOOP-6255-branch-0.20-security.patch=
, HADOOP-6255-common-trunk-1.patch, HADOOP-6255-common-trunk-2.patch, HADOO=
P-6255-common-trunk-4.patch, HADOOP-6255-common-trunk-5.patch, HADOOP-6255-=
common-trunk-6.patch, HADOOP-6255-common-trunk-7.patch, HADOOP-6255-common-=
trunk-8.patch, HADOOP-6255-common-trunk.patch, HADOOP-6255-hdfs-trunk-1.pat=
ch, HADOOP-6255-hdfs-trunk.patch, HADOOP-6255-mapred-trunk-1.patch, HADOOP-=
6255-mapred-trunk-2.patch, HADOOP-6255-mapred-trunk.patch, HADOOP-6255.patc=
h, deployment.pdf, deployment.tex
>
>
> We should be able to create RPMs for Hadoop releases.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira