Re: [MirageOS-devel] blobs.openmirage.org is down

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

On 27 Jul 2015, at 11:42, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
> 
> On 26 Jul 2015, at 16:28, Amir Chaudhry <amc79@xxxxxxxxx> wrote:
>> 
>> Hi folks,
>> 
>> David reported that the blobs site was down a few days ago [1].  Could 
>> whoever has access please check it out and report back? (either here or on 
>> the issue).
>> 
>> [1] https://github.com/mirage/mirage-www/issues/375
> 
> I'm on it -- the VM at Rackspace had both rebooted and the Docker volume had 
> run out of disk space since we don't garbage collect the is-mirage-broken 
> cron job volumes.  I've installed a cron job to reap intermediate containers 
> now, which should alleviate the situation.
> 
> In the longer term, I'm looking into moving the Docker cron jobs into a more 
> dedicated infrastructure, instead of repurposing the ARM build VM.  I'll 
> update the bug report to reflect this and leave it open.

Incidentally, I was looking at the other problem of is-mirage-broken being out 
of date on the live website:

https://github.com/mirage/mirage-www/issues/374

Rather than fixing this directly, I'm taking the opportunity to rearchitect the 
website to use Irmin, since Thomas has largely got this working now.  The new 
model will involve the website cloning all of its data sources at unikernel 
compile time:

- the templates from mirage/mirage-www.git
- the Markdown from mirage/mirage-www.wiki.git
- the is-mirage-broken data from mirage/is-mirage-broken.git
- the changelog from the (as yet uncreated) mirage/megamirage.wiki.git (which 
aggregates all the repositories)

This way, asynchronous jobs can update their relevant repositories, and the 
Mirage website just glues them together via Irmin queries.  One thing missing 
is a connector between the static website generation and Irmin, which I'm 
hopeful we can derive from Thomas Leonard and David Sheets' recent work.  In 
particular, I would love to hook up the website with live updates whenever 
anything is pushed to the various data sources, which involves grabbing the 
relevant Cuekeeper code.

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel