Last week, I was able to exercise juju/puppet deployment and smoke-tests on a few 1.2.1 components (Hadoop/HBase/Spark/Zookeeper). Results are here (Oct 25) for AWS and local deployments on ubuntu 16.04/x86_64:
http://bigtop.charm.qa/ +1 from me. Thanks! -Kevin On Tue, Oct 31, 2017 at 12:26 PM, Olaf Flebbe <[email protected]> wrote: > Hi > > I had only limited testing: But LGTM +1 (did some provisioner tests with > centos7) > > Olaf > > > > > Am 31.10.2017 um 16:46 schrieb MrAsanjar . <[email protected]>: > > > > My team have done limited testing on some of the key components (i.e. > > Hadoop and Spark).. looks good > > +1 > > > > On Sun, Oct 29, 2017 at 12:15 AM, Evans Ye <[email protected]> wrote: > > > >> Hey amir what’s the plan on your side? > >> We better have a schedule for testing so that we can setup another vote. > >> > >> Kevin Monroe <[email protected]>於 2017年10月26日 週四，上午1:20寫道： > >> > >>> Let me fire off another thread on this so we don't clutter the vote :) > >>> > >>> On Wed, Oct 25, 2017 at 12:07 PM, Evans Ye <[email protected]> wrote: > >>> > >>>> Surly that's doable. > >>>> I can recall that in 1.2.0 Roman was releasing ppc and arm repos with > >> non > >>>> arch dependent packages built on x86 64. For those arch dependent > >>> packages, > >>>> that can be built separately. > >>>> How do you think? > >>>> > >>>> Kevin Monroe <[email protected]>於 2017年10月26日 週四，上午12:05寫道： > >>>> > >>>>> Hey Evans, my intel tests are looking great so far. Since Amir > >>> mentioned > >>>>> ppc64le, I was curious if you had an ETA for the 1.2.1/ppc64le > >>>> convenience > >>>>> repo. I understand this won't block the release, but I'd be happy to > >>> run > >>>>> some tests on that arch if/when the repo becomes available. > >>>>> > >>>>> On Wed, Oct 25, 2017 at 9:06 AM, Evans Ye <[email protected]> > >> wrote: > >>>>> > >>>>>> That's great! The original deadline is October 29th, 2017 at noon > >>> PDT. > >>>>>> We can reset that based on your timeline for conducting the > >> testing. > >>>>>> > >>>>>> > >>>>>> > >>>>>> 2017-10-25 4:35 GMT+08:00 MrAsanjar . <[email protected]>: > >>>>>> > >>>>>>> when is the deadline?! I would like to get my team verify Bigtop > >> on > >>>>>> ppc64le > >>>>>>> platform, however it wpn't be possible till next week, due to few > >>>> other > >>>>>>> commitments. > >>>>>>> > >>>>>>> On Tue, Oct 24, 2017 at 9:12 AM, Evans Ye <[email protected]> > >>>> wrote: > >>>>>>> > >>>>>>>> This is the vote for release 1.2.1 of Apache Bigtop. > >>>>>>>> > >>>>>>>> It fixes the following issues: > >>>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa > >> ? > >>>>>>>> version=12340373&projectId=12311420 > >>>>>>>> > >>>>>>>> The vote will be going for at least 120 hours and will be > >> closed > >>> on > >>>>>>> Sunday, > >>>>>>>> October 29th, 2017 at noon PDT. Please download, test and vote > >>>> with > >>>>>>>> > >>>>>>>> [ ] +1, accept RC2 as the official 1.2.1 release of Apache > >> Bigtop > >>>>>>>> [ ] +0, I don't care either way, > >>>>>>>> [ ] -1, do not accept RC2 as the official 1.2.1 release of > >> Apache > >>>>>> Bigtop, > >>>>>>>> because... > >>>>>>>> > >>>>>>>> Source and binary files: > >>>>>>>> https://dist.apache.org/repos/ > >>>> dist/dev/bigtop/bigtop-1.2.1- > >>>>>> RC2/ > >>>>>>>> > >>>>>>>> Maven staging repo: > >>>>>>>> https://repository.apache.org/content/repositories/ > >>>>>> orgapachebigtop-1016 > >>>>>>>> > >>>>>>>> The git tag to be voted upon is release-1.2.1-RC2 > >>>>>>>> > >>>>>>>> Bigtop's KEYS file containing PGP keys we use to sign the > >>> release: > >>>>>>>> https://dist.apache.org/repos/dist/release/bigtop/KEYS > >>>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > >
