|
| From: | Dave Crossland |
| Subject: | Re: [Userops] Why is it hard to move from one machine to another? An analysis. |
| Date: | Fri, 10 Apr 2015 11:03:08 -0400 |
On Apr 9, 2015 6:18 PM, "Dave Crossland" <address@hidden> wrote:
> On 9 April 2015 at 11:58, Bob Mottram <address@hidden> wrote:
>> Maybe Docker and containers are the way to go, but I have some concerns.
>> Installing initially from a Dockerfile, or equivalent, might be ok but there
>> is then the problem of keeping the container up to date with security
>> patches, application upgrades and wotnot.
>
> I think this is bare-metal mindset. You don't update the container; you create a new one, and you throw throw the old one away after its no longer in use.
That's great when the container is free of state, but it can't be
turtles all the way down. The state needs to be somewhere and if it's
in a container, that container can't be just rebuilt unless the
container itself is stateless and the state is mounted in like the
Sandstorm /var.
Mounted? This sounds to me like bare metal mindset :)
Post containerisation, state lives in an object store that has redundancy, so if you tear down a store node it doesn't effect the integrity of the store.
Even if you run a server system with a primary host for yourself and your immediate family, you need a second[ary] off-site backup host to mitigate fire risk.
This could be done with a mountable healing filesystem, of course, but it's probably more like:
$ git annex initremote cloud \
type=S3 encryption=none port=80 \ host=your.libre.s3.api.compatible.storage.cloud.net
| [Prev in Thread] | Current Thread | [Next in Thread] |