11–20 of 32 posts
LXD is great. It lowers significantly the mental burden of running something in containers because they behave essentially like a VM. That being said LXD and juju are very Ubuntu things. LXD needs wide adoption for it to be attractive as a serious workload.
Earlier quoted context omitted.
Yeah.. it is a subtle difference between zpool create home mirror a b c d cache e and zpool create home mirror a b mirror c d cache e
Could you elaborate on the semantics of "cache"? I do understand the mirror keyword, but I know next to nothing about ZFS and don't really get what "cache" means, considering bouth your and OPs comment.
If I recall correctly, the extra indexes and tags mean l2arc requires more memory to work efficiently.
LXD is great. It lowers significantly the mental burden of running something in containers because they behave essentially like a VM. That being said LXD and juju are very Ubuntu things. LXD needs wide adoption for it to be attractive as a serious workload.
If you like LXD, why can't you just use it and not care whether Redhat is using it?
LXD is great. It lowers significantly the mental burden of running something in containers because they behave essentially like a VM. That being said LXD and juju are very Ubuntu things. LXD needs wide adoption for it to be attractive as a serious workload.
There are LXD images for Ubuntu, CentOS, Gentoo, Plamo, and other Linux operating systems. So you can really boot most any Linux as you would a VM. Between that and it's use as a hypervisor in OpenStack it gets flexed pretty heavily. Though I agree, more people should be using it!
https://www.flockport.com/lxc-and-lxd-support-across-distrib...
LXD is more often associated with a VPS style container, versus docker style containers. So, at the moment, it does have a distinctly "only runs right on Ubuntu" feel.
Earlier quoted context omitted.
Could you elaborate on the semantics of "cache"? I do understand the mirror keyword, but I know next to nothing about ZFS and don't really get what "cache" means, considering bouth your and OPs comment.
You can use a fast disk like an SSD as a 2nd level cache device after ram. So reads will first check the main ram cache first, then the ssd cache disk before finally hitting the underlying storage.
https://svnweb.freebsd.org/base/head/sys/cddl/contrib/openso...
Earlier quoted context omitted.
If you like LXD, why can't you just use it and not care whether Redhat is using it?
Many organizations use RHEL, and individual workers cannot just spin up Ubuntu for their bank database servers.
Earlier quoted context omitted.
There are LXD images for Ubuntu, CentOS, Gentoo, Plamo, and other Linux operating systems. So you can really boot most any Linux as you would a VM. Between that and it's use as a hypervisor in OpenStack it gets flexed pretty heavily. Though I agree, more people should be using it!
Lxc itself is a bit hobbled on distros other than Ubuntu if you want unprivileged containers or containers running systemd based distros. https://www.flockport.com/lxc-and-lxd-support-across-distrib... LXD is more often associated with a VPS style container, versus docker style containers. So, at the moment, it does have a distinctly "only runs right on Ubuntu" feel.
As for your last comment, yeah these are system containers - lighterweight virtual machines and not docker containers. They're meant to replicate and entire machine, with an init, more attuned to a VPS/VM and not an application container.
Seeing how much it's used there, I wish ZFS would land in linux(-next/-staging) already :-).
Earlier quoted context omitted.
Lxc itself is a bit hobbled on distros other than Ubuntu if you want unprivileged containers or containers running systemd based distros. https://www.flockport.com/lxc-and-lxd-support-across-distrib... LXD is more often associated with a VPS style container, versus docker style containers. So, at the moment, it does have a distinctly "only runs right on Ubuntu" feel.
That article is almost a year old now. Considering Wily and Xenial are systemd based I'm going to assume the LXD/LXC folks have figured this out. As for your last comment, yeah these are system containers - lighterweight virtual machines and not docker containers. They're meant to replicate and entire machine, with an init, more attuned to a VPS/VM and not an application container.
Not much has changed, at least as far as running LXC/LXD using something other than Ubuntu as the host os. Not LXC's fault exactly, just the underlying set of requirements, kernel/systemd/etc patches, assuming you want the unpriv containers and systemd based containers to run.
Technically, you could find and apply all of those to Debian, Redhat, whatever, and use them as the host OS, but it wouldn't be a trivial effort.