On Tue, Mar 15, 2016 at 09:04:48AM -0400, Jeff Darcy wrote: > > Yes, Right now we get the machine from duffy instantly. If it is not > > instant, > > it means no machines are in ready state and we will have to wait few more > > minutes (~5 minutes) to get them. > > If machines are available to be allocated instantly, does that mean they're > being re-used across allocations? Or are there just so many extra machines > in the pool that there's time to re-provision in the background before they > get re-used again?
Yes, indeed. Once a test has been run and the machine is released back to Duffy, it will get cleanly installed. Last time the CentOS team explained about their community CI, they had ~250 physical machines for testing available. Details are in their wiki: https://wiki.centos.org/QaWiki/PubHardware > > But I think vagrant is very useful anywhere else (in non CentOS CI infra). > > But I wasn't sure *in* CentOS CI, since the machines required for distaf are > > available via duffy. So I wasn't sure where vagrant would fit in. > > > > But if the plan is to run the existing regression tests by spawning vms > > inside the machines provided by duffy, then I think it can be done. Although > > someone will have to try that out see if it provides any advantage. > > I think the advantages would be two-fold. > > (a) The environment within a vagrant box is one we can control more than > might be possible within duffy. > > (b) It's an environment that we can replicate with certainty in other > host environments where duffy doesn't exist. (c) it would be possible to run tests on non-CentOS distributions We can place the Vagrant box files/images/whatever on artifacts.ci.centos.org so that all systems in the CI have local access to them. Let me know if you want me to get that done and someone else can then configure a Jenkins job to run tests in Vagrant. It'll basically need scripts like these: https://github.com/gluster/glusterfs-patch-acceptance-tests/tree/master/centos-ci/libgfapi-python Niels
signature.asc
Description: PGP signature
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel