[chef] Re: Re: Re: Re: Re: Re: Re: Re: Testing and Determining Test Coverage in Cookbooks

["steve ." < >]

Thanks for the tip.  I haven't instrumented this issue yet on the
Vagrant host but I doubt the problem is related to disk I/O on the
host.  It seems like it's related to network I/O on the guest,
actually, as I've seen a similar problem on other hosts (including my
SSD-equipped MacBook ... though I would hope that an iSCSI LUN spread
across some indeterminate number of drive spindles would at least
equal the sequential/random I/O rates of a single SSD!).

Still, I'm not ruling anything out -- I'll add some monitors and take a look.

On Tue, Oct 9, 2012 at 10:56 AM, Ranjib Dey 
<
 >
 wrote:
> you can consider using SSDs on the vagrant hosts, along with
> http://scache.sourceforge.net/ for caching network i/o , we are using these
> two for our CI server, and the results has been decent
>
>
> On Tue, Oct 9, 2012 at 11:20 PM, steve . 
> <
 >
>  wrote:
>>
>> I might investigate this, as one problem we've run into with Vagrant
>> testing is that concurrent VM testing kind of doesn't work.  So we
>> have to test VMs serially (on a physical box).  The I/O is also not
>> that great, so Chef runs are taking several minutes (up to 20!) to
>> finish.  Some of this might be Vagrant's fault but I'm willing to bet
>> it's mostly VirtualBox.
>>
>> Unfortunately, I don't really see anything in the change logs for
>> either project that addresses my issues, which means it's either
>> something tunable or nobody's figured this out yet.
>>
>> Maybe I should just bite the bullet and hop onto the plugin version of
>> Vagrant, get it working with the Vsphere API and use that instead.
>> LXC doesn't help me test on the Windows platforms, after all...
>>
>> On Sun, Oct 7, 2012 at 11:25 PM, Torben Knerr 
>> <
 >
>>  wrote:
>> >
>> > Am 08.10.2012 07:27 schrieb "Peter Donald" 
>> > <
 >:
>> >
>> >
>> >>
>> >> On Mon, Oct 8, 2012 at 4:13 PM, Torben Knerr 
>> >> <
 >
>> >>  wrote:
>> >> > Vagrant works well for me here, but the roundtrip times are naturally
>> >> > longer. I wanted to play with LXC containers instead of using
>> >> > VirtualBox
>> >> > (ideally Re-using my Vagrantfile), but haven't come to testing this
>> >> > yet.
>> >> >
>> >> > Anyone here on the list using LXC containers for testing Chef runs
>> >> > already?
>> >>
>> >> I have yet to do so myself. But I saw the creator of Toft [1] give a
>> >> talk and demonstration of it and it looked really nice.
>> >>
>> >> [1] https://github.com/exceedhl/toft
>> >>
>> >
>> > Nice, looks promising. Now if that would also run on travis-ci, that
>> > would
>> > be super-neat!
>> >
>> > Anyone tried that already?
>> >
>> >> > For testing a complex setup like this I would go for a multivm
>> >> > Vagrantfile
>> >> > and test the real scenario with multiple VMs - otherwise you are
>> >> > testing
>> >> > something that dosen't reflect the real situation.
>> >>
>> >> We do that ...
>> >>
>> >> > Still it would be useful to have something like a special role for
>> >> > development in addition.
>> >>
>> >> except we use a "chef_dev" environment instead of a role
>> >>
>> >>
>> >> --
>> >> Cheers,
>> >>
>> >> Peter Donald
>
>