Re: ZooKeeper release validation cluster access

An update: I have the OK to get access to this cluster for the ZK project. I've put in the application and will start looking to figure out next steps once it's approved On Tue, Jul 12, 2016 at 12:43 AM, Raúl Gutiérrez Segalés < r...@itevenworks.net> wrote: > A bit late, but fwiw this was the 20

Re: ZooKeeper release validation cluster access

A bit late, but fwiw this was the 2015 flavor of my (personal) validation process: http://itevenworks.net/zk-releases -rgs On Jul 8, 2016 11:18 AM, "Michael Han" wrote: > Sure, I will post an early version next week. > > On Fri, Jul 8, 2016 at 10:55 AM, Camille Fournier > wrote: > > > That's g

Re: ZooKeeper release validation cluster access

Sure, I will post an early version next week. On Fri, Jul 8, 2016 at 10:55 AM, Camille Fournier wrote: > That's great Michael do you think you could share any of your work on > github to get us started? > On Jul 8, 2016 1:41 PM, "Michael Han" wrote: > > > Regarding ZK deployment automation, I a

Re: ZooKeeper release validation cluster access

That's great Michael do you think you could share any of your work on github to get us started? On Jul 8, 2016 1:41 PM, "Michael Han" wrote: > Regarding ZK deployment automation, I am building an automation that is > very similar to the requirement here - the motivation is to save me > sometime o

Re: ZooKeeper release validation cluster access

Regarding ZK deployment automation, I am building an automation that is very similar to the requirement here - the motivation is to save me sometime on validation / regression test of ZOOKEEPER-1045 and I could see same automation being used to validate a release as well. It might not be ready for

Re: ZooKeeper release validation cluster access

We could consider using vagrant and something like ducktape (for Kafka): https://cwiki.apache.org/confluence/display/KAFKA/tutorial+-+set+up+and+run+Kafka+system+tests+with+ducktape As

Re: ZooKeeper release validation cluster access

These are all good questions. My ultimate hope here is that we can actually get something set up so that for each release we want to do, we can easily run a standard smoke test on this cluster, and potentially leave the cluster available for a few days for additional testing by the community, to h

Re: ZooKeeper release validation cluster access

I'll help validating the release on our internal cluster using zk-smoke and manual testing. Do we have a standard protocol on what should be validated and how? Also do we perform integration tests (e.g. with HBase / Kafka) as part of release validation? On Thu, Jul 7, 2016 at 12:25 PM, Flavio P J

Re: ZooKeeper release validation cluster access

Hi, Camille, We (twitter) are definitely interested in helping. We would need to test this release anyway for our own sake. However, we have very limited OSS experience so please guide us along the way. So what’s the next step? > On Jul 7, 2016, at 11:04 AM, Camille Fournier wrote: > > So I'm

Re: ZooKeeper release validation cluster access

And thanks for doing this, Camile, this is great. -Flavio On 7 Jul 2016 8:25 p.m., "Flavio P JUNQUEIRA" wrote: > Perhaps start from phunt's smoke test? > > https://github.com/phunt/zk-smoketest > > -Flavio > On 7 Jul 2016 7:04 p.m., "Camille Fournier" wrote: > >> So I'm working with the CNCF to

Re: ZooKeeper release validation cluster access

Perhaps start from phunt's smoke test? https://github.com/phunt/zk-smoketest -Flavio On 7 Jul 2016 7:04 p.m., "Camille Fournier" wrote: > So I'm working with the CNCF to see about getting cluster access to spin up > ZK clusters for release validation. I was wondering if anyone has scripts > for