Open Stack

We have a CI for Cinder drivers. Currently we use 1 instance for the master
and 1 instance for each slave(we test one driver on each slave). The
configuration is the following:

Master: 2VCPUs + 8GB RAM
Slaves: 2VCPUs + 12GB RAM
Network: 4Mb Download + 4Mb Upload

Our jobs usually take 1:20h to run, but that is because of the network. In
our setup we virtualize all hosts using VMWare, which is very handy as we
can save an snapshot and trigger a revert after the job is complete also,
if you have FC drivers, VMWare will save a lot of pain with it PCI
passthrought. We have an step by step to configure the env with VMWare and
Cinder drivers, if you need we can make it available.


On Thu, Oct 30, 2014 at 1:24 PM, Jeremy Stanley <fungi at yuggoth.org> wrote:

> On 2014-10-30 20:28:17 +0530 (+0530), Amit Das wrote:
> > This is exactly what we intend to do. Wanted to know if there is
> > anything else that we should know before placing the requests.
>
> In that case, if you're wanting to do devstack-gate based jobs we
> use instances with 8 VCPUs and 8 GB RAM. A typical tempest-full run
> takes somewhere in the vicinity of an hour to complete depending on
> what configuration options have been selected. Due to the inability
> to cleanly re-run DevStack or to trust that proposed changes haven't
> destroyed the usability of the worker instance, we recycle and
> replace them with fresh instances for each job.
> --
> Jeremy Stanley
>
> _______________________________________________
> OpenStack-Infra mailing list
> OpenStack-Infra at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20141031/b04fc87b/attachment.html>