As a Singly Locker owner, I want new features and bug fixes in my Locker

WIP!!!

For Singly hosted locker, it's desirable to have lockers always up to date with the latest stable version of the code. In order to enable this, there must be a simple, repeatable, manner in which the code can be updated in the hosted environment. Some high-level (a)spec(t)s of this:

• All code for lockers on a given lxc box should run from the same code (i.e. it should be mounted into lxc containers from the same place on the file system)
• To begin with, the update process will be manual: 'shutdown', 'git pull, 'startup'
• To support this the locker itself wil need to clean up of its "mutable data" into
  • owner data (/Me, data from connectors, etc)
  • locker config (/Config, apikeys.json, config.json)
    • per env
    • per inst
  • For now, let's KISS and combine the per-env and per-inst stuff into one, /Config

First Steps

The proposed solution is simply to:

• update the locker code to support /Config
  • update lockerbox to cp template config files into the /Config dir
• create simple 'lxc-stop all' and 'lxc-start all' scripts
• update mounts:
  • bind mount /var/locker
  • mount /var/Locker/Me separately for each locker (probably makes replication easier!)

Stakeholders

• Forrest
• Temas

Dependancies

• Hosting /Me Storage