[PATCH 01/11] Import distbuild configuration files into definitions.git

Rob Taylor rob.taylor at codethink.co.uk
Tue Mar 18 16:41:28 GMT 2014

On 18/03/14 16:24, Sam Thursfield wrote:


> I realise now that this deploy-time setup of directories is flawed.
> In a later patch I add an example cluster morphology with this
> configuration line:
>      FSTAB_SRC: LABEL=src /srv/distbuild auto defaults,rw,noatime 0 2
> That's a hint at how we've been deploying distbuild machines internally:
> we've mounted a physical disk at /srv/distbuild, so the build uses a
> hard disk storage rather than NFS (which is pretty much essential. I
> should probably mention this in the example cluster morphology).
> This means that it's futile creating the directories in /srv at
> deploy-time, and expecting them to be there on first boot: we'll have
> just mounted an empty disk over the top instead, so the
> morph-cache-server unit above will fail to start.
> Does anyone have a preferred way to solve this? I believe having the
> cache server or its unit file create the /srv/distbuild/artifacts
> directory if it is missing, rather than expecting it to have been
> created at deploy-time.

Given this is application specific workspace, I'd have the distbuild 
worker itself populate it if it needs populating.


More information about the baserock-dev mailing list