[
https://issues.apache.org/jira/browse/BIGTOP-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021050#comment-14021050
]
jay vyas commented on BIGTOP-1329:
----------------------------------
Although vagrant supports others (VMWare, KVM, ...) im okay, if we just start
with a *docker recipe*, and leave the VM part out of it.
We can thus fold this in as part of the docker infrastructure that roman is
building in BIGTOP-1154/BIGTOP-1323 similar to what roman is working on
> Leverage bigtop to build a patch deployment tester for hadoop.
> --------------------------------------------------------------
>
> Key: BIGTOP-1329
> URL: https://issues.apache.org/jira/browse/BIGTOP-1329
> Project: Bigtop
> Issue Type: Wish
> Components: VM
> Affects Versions: backlog
> Reporter: jay vyas
> Priority: Minor
>
> YARN-1964 demonstrates that testing patches in hadoop is not just about unit
> testing anymore : End to end testing is increasingly valuable.
> Lets create a vagrant recipe in bigtop which
> 1) Pulls a jira patch down
> 2) Builds hadoop from scratch and
> 3) Packages it in a local repo, in a VM.
> 4) Runs a smoke test on the patch.
> This essentially would validate that (1) bigtop hadoop packaging is
> up-to-date with the code on hadoop head (2) Give the hadoop community a solid
> utility for end-to-end testing of YARN apps.
> This jira will be a significant undertaking, and we will work some on the
> idea during the BigTop Meetup today.
> Lets start by diagraming the process for end-to-end testing of a hadoop patch
> using bigtop-rpms, and ensuring that its actually feasible.
--
This message was sent by Atlassian JIRA
(v6.2#6252)