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 help those of us who do not have an easy way to spin up a ZK cluster at our companies for testing to feel good about vetting a release.
I think that a good first step would be to create something that can actually deploy a configured ZK on top of this cluster, and then deploy some sort of basic test script on machines that executes, eg, pat's smoke test as Flavio pointed out. I will admit to being a bit perplexed as to what the state of the nodes of this cluster look like when you get access to them and what needs to be installed on top of them to actually do this sort of automation. It looks like you can provision the nodes with an OS on them, but beyond that it looks like we may need to create the automation to install java first, then ZK. There's some very bare bones details here: https://github.com/cncf/cluster *For those of you who have internal processes for vetting ZK, if any of you have automation for spinning up new ZK servers in a cloud env hopefully we can use that to start. Does anyone have that? *I think that's where we need to begin. We can then move on to what a good smoke test might look like. Thanks, C On Thu, Jul 7, 2016 at 4:48 PM, Michael Han <h...@cloudera.com> wrote: > 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 JUNQUEIRA <f...@apache.org> > wrote: > > > And thanks for doing this, Camile, this is great. > > > > -Flavio > > On 7 Jul 2016 8:25 p.m., "Flavio P JUNQUEIRA" <f...@apache.org> 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" <cami...@apache.org> > 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 deploying and configuring ZK clusters quickly for stress testing > > that > > >> we could use if we get this access? I'm sure some of you in the > > community > > >> must do some of this internally. > > >> > > >> I would also very much appreciate any volunteers to contribute to > making > > >> better public release validation work, if possible, since it's unclear > > how > > >> much time I personally will be able to dedicate to this effort beyond > > >> getting access to the cluster. > > >> > > >> Thanks, > > >> C > > >> > > > > > > > > > -- > Cheers > Michael. >
