[
https://issues.apache.org/jira/browse/BIGTOP-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461010#comment-13461010
]
Bruno Mahé commented on BIGTOP-710:
-----------------------------------
Anatoli> It could, but I would not go there.
Building a robust open cluster manager has a much larger scope than building
something solving Apache Bigtop issues of today. Before trying to solve
everyone's problem, I would rather try to solve Apache Bigtop's first. We can
always expand later on.
Which brings me to the point that this ticket try to state a solution to a
problem not yet defined.
We all know and talked about wanting some sort of orchestration layer to help
us managing our VMs and test nodes (see BIGTOP-635 for instance) but we
probably all have something different in mind. This may create some confusion
later when implementations starts to appears but not matching everyone's
expectations.
So maybe we should spend some time first defining the use cases and
requirements?
> Create a higher level orchestration deployment framework
> --------------------------------------------------------
>
> Key: BIGTOP-710
> URL: https://issues.apache.org/jira/browse/BIGTOP-710
> Project: Bigtop
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Labels: orchestration
> Fix For: 0.5.0
>
>
> It would be very nice to start using our puppet code as a basis for a higher
> level orchestration framework capable of driving a true distributed
> multi-node deployment of Bigtop components. Puppet code is great at stamping
> out a predictable single node deployments, but we have to extend it with a
> DSL aimed at solving higher level orchestration.
> This JIRA is meant to be a central information radiator for collecting ideas
> on how to approach this (what DSL to use, how to structure communication
> between agents and fact sharing, etc).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
