On Wed, 26 Jul 2017 15:58:30 +0100 Mark Shuttleworth <m...@ubuntu.com> wrote:
> On 26/07/17 15:51, Felipe Reyes wrote: > > Some users run the controller in fairly big bare metal machines > > (e.g. 128G of RAM, I've seen even bigger controllers) and it won't > > be easy for them to have an extra machine to setup a new controller > > and run model migration, if their controller is HA then 3 spare > > machines are needed, this is hard to justify. > > Could LXD solve that problem? > > Seems like having A/B containers in each of those machines would be > fine. The total amount of work isn't growing, it's just shifting from > one codebase to the next. > > So, the three machines each get two containers, the Juju controller is > spread across three A controllers, the new one goes into the B > controllers, and migration essentially takes place on the same > hardware. Sounds like a good option, specially since this may open the door to have faster rollbacks, something we achieve today using VM snapshots and/or "juju backups". We just need to be careful to not assume the machine will have enough resources to have both containers (jujud and mongod in them specifically) running at the same time. -- Felipe Reyes Software Sustaining Engineer @ Canonical # Launchpad: ~freyes | IRC: freyes -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
