Upgrade smoke-tests to use 'overlay' storage and Ubuntu 15.04

[bboreham]

The 'overlay' driver is claimed to be the best choice right now, but requires Linux kernel 3.18.

You can feel the difference - using vfs (which our Vagrant set-up did because it didn't install the extra bits for aufs) the machine would bog down when tests were running, but with overlay you rarely notice this.

I will post some timings to illustrate the difference soon.

[tomwilkie]

We should do the same for circle runs. Needs updates to gce.sh and a new
template generating.

On Monday, 13 July 2015, Bryan Boreham [email protected] wrote:

The 'overlay' driver is the fastest available right now, but requires
Linux kernel 3.18.

I will post some timings to illustrate the difference soon.

You can view, comment on, or merge this pull request online at:

#1125
Commit Summary

• Upgrade to Ubuntu 15.04
• Tell Docker to use 'overlay' storage driver

File Changes

• M test/Vagrantfile
  https://github.com/weaveworks/weave/pull/1125/files#diff-0 (15)

Patch Links:

• https://github.com/weaveworks/weave/pull/1125.patch
• https://github.com/weaveworks/weave/pull/1125.diff

—
Reply to this email directly or view it on GitHub
#1125.

[rade]

it's less important for circle since that at least uses aufs.

[bboreham]

Sample timings for make run-smoketests, after all images have been pre-downloaded:

Driver	Run 1	Run 2
VFS (current)	23m47s	16m32s
AUFS	8m45s	5m48s
Overlay	6m19s	6m33s

Not sure if this is conclusive between AUFS and Overlay. Maybe the 8-minute one was an outlier.

[errordeveloper]

LGTM

[2opremio]

This change breaks the smoke-tests (in my local installation at least).

Using current master (907de67), after getting excited about the performance benefits of this PR and recreating the test VMs:

weave/test $ ./setup.sh
Copying weave images, scripts, and certificates to hosts, and
prefetch test images
Post http://192.168.48.11:2375/v1.19/images/load: dial tcp 192.168.48.11:2375: i/o timeout. Are you trying to connect to a TLS-enabled daemon without TLS?

It seems like 192.168.48.11:2375 cannot be accessed externally anymore when switching to ubuntu 15.

From my host:

$ docker -H tcp://192.168.48.11:2375 ps
Cannot connect to the Docker daemon. Is 'docker -d' running on this host?`

From my vagrant dev machine:

 $ docker -H tcp://192.168.48.11:2375 ps
 Get http://192.168.48.11:2375/v1.19/containers/json: dial tcp 192.168.48.11:2375: i/o timeout. Are you trying to connect to a TLS-enabled daemon without TLS?

Reverting to 499d65e and recreating the VMs fixes it

[bboreham]

Sorry, there's a fix in 6d17fe5