Good questions: Q) how do you think the charms will be contributed? A) We are planing to move all charms to github, that will make the contribution process much easier. Goal is to mirror bigtop contribution process.
Q) How they are going to be maintained, by whom, etc. A) we in canonical will maintain all contributed charms as a committer to the project. However we will strongly recommend more community members to join contributor and committer ranks, as any other open source project. Q) How the interaction between Bigtop-proper and the Juju charms store (?!) would be formed? A) Charmstore is getting remapped, meanwhile we could provide tools to sync bigtop<->Charmstore On Thu, May 14, 2015 at 6:35 PM, Konstantin Boudnik <[email protected]> wrote: > Thanks Amir. > > So, how do you think the charms will be contributed? How they are going to > be > maintained, by whom, etc. How the interaction between Bigtop-proper and the > Juju charms store (?!) would be formed? I do not expect you to have ready > answers for all these questions, but I'd love to have a discussion around > these points: I am sure we'll be seeing more situations like that in the > future. > > From Bigtop standpoint of view, something like this will probably belong > to a > contrib/ project, although we don't have such concept yet. > > Thanks in advance, > Cos > > On Fri, May 08, 2015 at 01:01PM, MrAsanjar . wrote: > > Hi Konstantin, > > Sorry for a late reply, I was on a long overdue vacation in sunny Malta > :) > > *The vision is to build a big-data solution ecosystem where it allows > > community collaboration in design and development of * > > > > > > > > *publicly available big-data solutions, regarless of the deployment > > mechanism.Regarding Juju, I envision its deployment model not only will > > co-exist but also will compliment other style of deployment/management > > mechanisms ( ), as it has done with ClouderaManager CH5.3 > > https://jujucharms.com/u/bigdata-dev/cdh5-cm/trusty/13 > > <https://jujucharms.com/u/bigdata-dev/cdh5-cm/trusty/13>. * > > > > > > > > *While Juju is written in Python, its charms can be written in any > > language. You can write them in Python, Bash, Puppet (i.e. bigtop > > deployment)and Chef scripts. * > > *I will be glad to provide any other information and answer questions.* > > > > On Fri, Apr 24, 2015 at 9:58 PM, Konstantin Boudnik <[email protected]> > wrote: > > > > > Hello Amir. > > > > > > Thanks a lot for reaching out to the Bigtop community! It be great to > have > > > these hosted here as well as get some help to maintain them in the > future. > > > > > > Could you please share with us a little bit more details on how you > > > envision > > > it would work and how it might co-exist or compliment our in-house > Puppet > > > deployment mechanism? > > > > > > Thanks in advance! > > > Cos > > > > > > On Sun, Apr 19, 2015 at 11:17AM, MrAsanjar . wrote: > > > > To whom it may concern, > > > > My name is Amir Sanjar, Big Data Solution Development Lead at > Canonical. > > > My > > > > team has been developing various Big Data solutions built on top of > > > Apache > > > > Hadoop, Hortonworks, and Cloudera distributions (i.e > > > > https://jujucharms.com/big-data). We would like to contribute these > and > > > > future solutions to the Apache BigTop community. I wish to propose > > > creating > > > > a BigTop Solution project to house all big data solutions regardless > of > > > > orchestration tool (i.e. Juju, Ambari, Chef, ClouderaManager, puppet, > > > ...), > > > > any suggestions ? > > > >
