[
https://issues.apache.org/jira/browse/BIGTOP-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333763#comment-14333763
]
Konstantin Boudnik commented on BIGTOP-1702:
--------------------------------------------
Interesting... Is it it similar to Ubuntu Juju? Also, do you know if it solves
topology/orchestration/testing requirements?
Perhaps it would make sense to discuss this on user@ list first before doing
the work, adding support for a new framework, and/or locking us in a certain
ssh-controlling system.
Besides, I don't see how this works for bare-metal? I clearly says
bq. servers for which you have SSH access but no control over their lifecycle
which evidently requires an OS being provisioned. For baremetal you'd need to
support IMPI standard, like Foreman/MAAS do.
> 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)
