[
https://issues.apache.org/jira/browse/BIGTOP-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334373#comment-14334373
]
Konstantin Boudnik commented on BIGTOP-1702:
--------------------------------------------
Let's change the name of the JIRA then ;)
Also, I still fail to see how it is different from current deployment using our
Puppet stuff? I am sorry - I am pretty dense around vagrant. I am still
struggling to understand if this is an orchestration or just a trimming around
the edges of current deployment mechanism?
If it is an orchestration: what if an installation fails for some components?
Would it be possible to test and/or get auto-corrected? Where we'd store the
topology descriptions and inter-components relations?
> Bare Metal vagrant Provider: The final frontier one click BigTop
> provisioning.
> -------------------------------------------------------------------------------
>
> Key: BIGTOP-1702
> URL: https://issues.apache.org/jira/browse/BIGTOP-1702
> Project: Bigtop
> Issue Type: Bug
> Components: deployment
> Reporter: jay vyas
>
> Okay folks, I just saw https://github.com/tknerr/vagrant-managed-servers.
> Currently, we are doing a lot of maintenance of wiki pages like this:
> https://cwiki.apache.org/confluence/display/BIGTOP/How+to+install+BigTop+0.7.0+hadoop+on+CentOS+with+puppet
> Well, why don't we just deploy w/ vagrant ? Then anyone can spin up a
> vagrant cluster using our existing VM deployers.
> I can look into it and see if it works.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
