[
https://issues.apache.org/jira/browse/KUDU-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke updated KUDU-623:
-----------------------------
Target Version/s: (was: Public beta)
> Evaluate automated deploy+tests on EC2 or Cloudstack
> ----------------------------------------------------
>
> Key: KUDU-623
> URL: https://issues.apache.org/jira/browse/KUDU-623
> Project: Kudu
> Issue Type: Task
> Components: test
> Affects Versions: Public beta
> Reporter: Todd Lipcon
> Priority: Trivial
>
> Currently, we have a 7-node cluster internally mostly running ITBLL. This
> cluster does double duty of testing master and occasionally testing in-flight
> patches prior to commit. When we're in the latter mode, we don't always have
> good coverage of our current master. We also have a 10 nodes cluster that
> runs YCSB every 3 hours.
> We should invest some time in building an easy (i.e anyone can do it by
> following directions) deploy+test infrastructure based on amazon or
> cloudstack. We can probably use cheap instances, since we're mostly concerned
> with correctness and not performance. Ideally, once we have such a thing, we
> could have some policy like starting a new cluster every 2 days, and running
> each cluster for 7 days. Once a week we could start a cluster which we will
> let run for a month or something to get better longevity.
> The overall goal is to hit multiple points in the recency/longevity trade-off
> while also keeping costs manageable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
