If hibench can run as a gradle task that would be far more useful to the typical audience IMO and less technical debt to carry
.....I think the amount of boilerplate for a package only is justified if it's a distributed component. > On Jan 26, 2016, at 11:03 PM, RJ Nowling <rnowl...@gmail.com> wrote: > > My personal view would be to start with adding packages. Then send an > email to the dev@ list to open a separate discussion. > >> On Tue, Jan 26, 2016 at 9:45 PM, Cheng, Hao <hao.ch...@intel.com> wrote: >> >> Which way does the community prefer? Just for packaging or the put entire >> project into bigtop? >> >> -----Original Message----- >> From: RJ Nowling [mailto:rnowl...@gmail.com] >> Sent: Wednesday, January 27, 2016 11:24 AM >> To: dev@bigtop.apache.org >> Subject: Re: HiBench as part of Bigtop >> >> A few of us have been working on BigPetStore, a family of example >> applications (blueprints). We've also been working on data generators to >> create relatively complex fake data for those demo apps. >> >>> On Tue, Jan 26, 2016 at 9:10 PM, Cheng, Hao <hao.ch...@intel.com> wrote: >>> >>> Hi RJ, >>> >>> Currently, we are targeting packaging the HiBench in Bigtop; but is >>> there any other subproject entirely be part of BigTop? >>> >>> Thanks, >>> Hao >>> >>> -----Original Message----- >>> From: RJ Nowling [mailto:rnowl...@gmail.com] >>> Sent: Wednesday, January 27, 2016 11:04 AM >>> To: dev@bigtop.apache.org >>> Subject: Re: HiBench as part of Bigtop >>> >>> Hi Hao, >>> >>> Are you interested in just packaging HiBench in Bigtop or contributing >>> the entire project to Bigtop? >>> >>> Is there someone who would be willing to take responsibility for >>> maintenance? >>> >>> We generally like to find a maintainer for each package and add them >>> to our maintainers list. This way we know who to contact if a build >>> fails and blocks a release. If there is no maintainer (and the build >>> has problems), we use that as grounds for removing the package from >> Bigtop. >>> >>> Thanks! >>> RJ >>> >>> >>>> On Tue, Jan 26, 2016 at 1:15 AM, Cheng, Hao <hao.ch...@intel.com> wrote: >>>> >>>> Thank you Cos for the reply, we will take a look at YCSB. :) >>>> >>>> Hao >>>> >>>> -----Original Message----- >>>> From: Konstantin Boudnik [mailto:c...@apache.org] >>>> Sent: Tuesday, January 26, 2016 2:33 PM >>>> To: dev@bigtop.apache.org >>>> Subject: Re: HiBench as part of Bigtop >>>> >>>> Hi Hao. >>>> >>>> Thanks for your interest in the project and for considering us as >>>> the new home for this benchmarking tool! We already have YCSB as the >>>> part of stack, but clearly the more the merrier ;) >>>> >>>> A quick look at the source code shows that HiBench is already >>>> licensed under ASL2, so the rest of it should be just a SMOP ;) As >>>> you know, we do package all our components for both deb and rpm >>>> package managers, deployment code, as well as do have requirements >>>> for package and integration testing. I think the good starting point >>>> would be to take a look at YCSB >>>> >>>> bigtop-packages/src/*/ycsb/ >>>> bigtop-deploy/puppet/modules/ycsb/ >>>> >>>> and/or other components in the stack. This link >>>> >>>> https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute >>>> >>>> should also be helpful to understand the process of contributing >>>> into the project. And you already found dev@ list, so you'll set ;) >>>> >>>> I wonder how others in the community see this? >>>> Cos >>>> >>>>> On Tue, Jan 26, 2016 at 05:37AM, Cheng, Hao wrote: >>>>> Dear BigTop Devs, >>>>> >>>>> I am from Intel Big Data Technology team, and we are the owner of >>>>> HiBench, an open source benchmark suite for Hadoop / Spark >>>>> ecosystem; as widely used, more and more trivial requirements from >>>>> HiBench users, due to the limited resources, particularly the ease >>>>> of deployment, we are exploring the possibility of getting the >>>>> code >>> into BigTop. >>>>> >>>>> HiBench code can be found at: >>>>> https://github.com/intel-hadoop/HiBench >>>>> >>>>> Looking forward to your reply. >>>>> >>>>> Regards, >>>>> Hao >>
