Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 3 Aug 2012 06:06:03 +0000 (UTC)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <83595947.8993.1343973963925.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <2046828916.1532.1341363652957.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (MAPREDUCE-4393) PaaS on YARN: an YARN application
 to demonstrate that YARN can be used as a PaaS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arun C Murthy updated MAPREDUCE-4393:
-------------------------------------

    Status: Open  (was: Patch Available)

Jaigak - I spent some more thinking about this in light of MAPREDUCE-4495.

Unfortunately, it seems that we are running the risk of turning YARN into an 'umbrella' project by accepting applications built on top of YARN into the project itself...

Essentially, as folks like Chris Mattman have pointed out in MAPREDUCE-4495, the PaaS prototype is better off being a standalone project in Apache Incubator since the Apache Software Foundation frowns upon one 'umbrella' project housing several smaller projects i.e. YARN vis-a-vis PaaS, Workflow AM etc.

If you are interested, I'm more than happy to help you through the Apache Incubator process and we collaborate via the Incubator. Do you mind doing that? Thanks!
                
> PaaS on YARN: an YARN application to demonstrate that YARN can be used as a PaaS
> --------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4393
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4393
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>          Components: examples
>    Affects Versions: 0.23.1
>            Reporter: Jaigak Song
>            Assignee: Jaigak Song
>             Fix For: 3.0.0
>
>         Attachments: HADOOPasPAAS_Architecture.pdf, MAPREDUCE-4393.patch, MAPREDUCE-4393.patch, MAPREDUCE-4393.patch, MAPREDUCE4393.patch, MAPREDUCE4393.patch
>
>   Original Estimate: 336h
>          Time Spent: 336h
>  Remaining Estimate: 0h
>
> This application is to demonstrate that YARN can be used for non-mapreduce applications. As Hadoop has already been adopted and deployed widely and its deployment in future will be highly increased, we thought that it's a good potential to be used as PaaS.  
> I have implemented a proof of concept to demonstrate that YARN can be used as a PaaS (Platform as a Service). I have done a gap analysis against VMware's Cloud Foundry and tried to achieve as many PaaS functionalities as possible on YARN.
> I'd like to check in this POC as a YARN example application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira