21–30 of 32 posts
Earlier quoted context omitted.
Many organizations use RHEL, and individual workers cannot just spin up Ubuntu for their bank database servers.
I guess we should all give up and only use what RHEL provides to us, then, since it is the only universally available distribution.
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?
Over time, as each distro catches up with the same patches/kernel version/etc choices ubuntu made, this problem will go away. For now, however, LXD means Ubuntu as the host os.
[1] https://www.youtube.com/playlist?list=PLzSGDpUWtiotngRgVqpa8...
[2] https://www.youtube.com/watch?v=sp_Re8Mx9xk#t=1h8m15s
Earlier quoted context omitted.
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.
>>That article is almost a year old now. 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 h…
Earlier quoted context omitted.
>>That article is almost a year old now. 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 h…
I used lxc containers with ubuntu 12.04 on a Debian host ;-)
Edit: Or you did, and you figured out how to replicate all the needed changes back to Deb.
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.
a cache drive is l2arc. Brendan Gregg's post[0] explains it well, but the TLDR is that l2arc is very much like an l2 cache in a cpu. Recent and relevant items are held on a fast drive in case it will be needed in the near future. It is really an L2 cache: L1 is called ARC and is held in dram. If I recall correctly, the extra indexes and tags mean l2arc requires more memory to work efficiently. [0]: https://blogs.orac…
I don't think the author of this post really understands ZFS. Is that a 4 disk mirror? You'd be much faster using a raid10 there. ZFS 'cache' devices are't for write cache either, you'd want a log device for write perf reasons if that's your constraint... Even then it's unlikely to make a difference on a workstation workload with 16GB of memory..
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
LXD looks sweet, and seem to have many advantages over Docker. The only issue I got with it is the network settings where I miss a configuration that let me isolate the containers from the LAN, while still giving them Internet access.
Maybe something went wrong with your install?