Hi Benoit,
Our environment is pretty locked down when it comes to upgrades at the Ubuntu
server level. We don't upgrade often (mainly for security-related stuff).
That said, in the event of a mandatory reboot, we take a VM snapshot then take
a small downtime. Since Ubuntu 16 (re)boots so
Hi Ron,
sounds like a good way to manage it. Thanks
How do you handle your Ubuntu 16.04 upgrade / kernel update ? I case of a
mandatory reboot, your LXD containers will have a downtime but maybe not a
problem in your situation?
Regarding ceph, gluster and drdb, the main concern is about
We do it slightly differently. We run LXD containers on Ubuntu 16.04 Virtual
Machines (inside a virtualized infrastructure). Each physical server has
redundant network links to highly-available storage. Thus, we don't have to
migrate containers between LXD servers; instead we migrate the
On 11/03/2016 08:41 AM, Geaaru wrote:
Hi guys,
is there any milestone for develop a vagrant-lxd plugin ?
I think that could be important to improve lxd project visibility to
permit use of Vagrant with LXD technology.
Thanks in advance.
question done before here, check this [1], some to
ZFS is not a distributed filesystem.
So the only way to do what you want is to use DRBD, and ZFS on top of
it.
Tomasz Chmielewski
https://lxadm.com
On 2016-11-03 22:42, Benoit GEORGELIN - Association Web4all wrote:
Thanks, looks like nobody use LXD in a cluster
Cordialement,
Benoît
Hi guys,
is there any milestone for develop a vagrant-lxd plugin ?
I think that could be important to improve lxd project visibility to
permit use of Vagrant with LXD technology.
Thanks in advance.
G.
___
lxc-users mailing list
