Date: Fri, 31 Jul 2015 10:59:04 -0400 From: Allan Jude <allanjude@freebsd.org> To: Kai Gallasch <k@free.de> Cc: freebsd-jail@freebsd.org Subject: Re: sysutils/iocage in a NAS environment Message-ID: <55BB8D38.5000500@freebsd.org> In-Reply-To: <55BB8BE1.8050808@free.de> References: <55BB4CC5.2050004@free.de> <55BB84AF.5040808@freebsd.org> <55BB8BE1.8050808@free.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --k6OSAPqIPvs9WdiQE9jc6w2b4Bjp35j95 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2015-07-31 10:53, Kai Gallasch wrote: >=20 >=20 > On 31.07.2015 16:22 Allan Jude wrote: >> On 2015-07-31 06:24, Kai Gallasch wrote: >>> >>> Hi. >>> >>> Just read that FreeNAS 10 is going to use sysutils/iocage for managin= g >>> local jails on the NAS. That is great news and it will give iocage mo= re >>> publicity and a wider user base! >>> >>> I am currently testing a FreeNAS 9 as a NAS for my FreeBSD servers. E= ach >>> (FreeBSD 10) server is running between 10-50 iocage jails. >>> >>> iocage's documentation states that each iocage installation needs a >>> zpool to run on. >>> >>> So the only way I see to use a NAS for iocage deployment would be to >>> make use of iSCSI (block based) mounts. The NAS would offer an iscsi >>> target to the jailhost. When mounted, it just shows up as a block bas= ed >>> LUN. You then could create a zpool on this LUN and use this zpool for= >>> iocage. (Each time the jailhost starts up, the iSCSI mount + zpool >>> import would have to happen automatically) >>> >>> Does this approach make any sense when both performance or stability = are >>> needed? >>> >>> Is it generally adviseable to use zpools on iSCSI targets, because th= ey >>> are basically iSCSI exported zvols running on top of another zpool? >>> >>> Regards, >>> Kai. >>> >> >> If FreeBSD 9 is your NAS, why are the disks remote? >> >> Normally, you'd run iocage on the NAS (the machine with the physical >> disks in it) and have direct access to the zpool. >=20 > I understand that this would result in the best performance, but how am= > I to run FreeBSD 10 or 11 jails on this NAS appliance that is plain > FreeBSD9 ? >=20 > The current state is (as I wrote), that I manage several jail hosts in = a > rack, which are just running jails using the iocage tool. >=20 > What I want to achieve with FreeNAS is to have the jail data centralize= d > on the NAS and the jail hosts just "mounting" the jail data and running= > the jails. The benefit would be that if one server dies or needs to be > completely rebuild, I just remount the jails on another active server, > without much service interruption. >=20 > In my experience when running a bunch of jail hosts with local jail > data, much time and effort is wasted moving data around if you want to > change hardware or have failed hardware, etc. >=20 > K. >=20 Ok, I understand your use case better now. iSCSI (or geom gate) to share the block device looks to be your only options if you want to use iocage which depends on ZFS. You could use a different jail management tool that doesn't depend on ZFS, and then use NFS or something, but then it is harder to trigger snapshots etc, since you'd have to do that via the remote NAS. If this was the only use case for the NAS, you might consider exposing the raw disks via iSCSI and creating the zpools (and the redundancy) inside the jail hosts. This would avoid the zpool on iscsi on zvol complexity. Of course this is harder to conceptualize, especially if you want to 'pool' storage for maximum utilization. --=20 Allan Jude --k6OSAPqIPvs9WdiQE9jc6w2b4Bjp35j95 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJVu409AAoJEBmVNT4SmAt+N5AP/0i2frQI4Z9CHRw5m2LsjEZ3 +BcxXvPbR0W9xqgfRQ4jH6m0WUJhZS381TjIBgplEaVkaqLqsC2AreGF5dtdIf7L DYxsQK519UHoI8qQcpC84QxbTEoUxmnfSNPSBOQYlcnD01fpJcmoyOv9vY7SHxzu OaWk9tp4fc8L2cOHT1wATUsYfRYy8tGrKAFZPbe0x702VL0pn7AKJ5ui264UCa0v u4+yTGwOyUNcW+9CNCMtsuOA1bB8XUNOkhlO4Ul4gutTNjgi+eCGJRnab6FkWfTl TUstYPhQNZrHPIJ3njY9s2Xb1/PWasnveV8N7j1baG8ybF5i7ZjRWjD4hcLpmG1c BHSB+fMmpG2gbb0xo5mrTdW9rvxdtDeOz5BmsU+JzBIEnZH1dyyJ058jy+Ed92H1 iFBsCajE7m7aez554BzSnvmI51N3ecdZwcvTcV5Pm3hqN20gs5CSuqMGgGikDqWP 2iPJCzdTyVgKid1NNKYL0LlkV/RBwUVAaxR8lIjxNzFlR4LIEsBZn+aRE8oM1QGj a+WL1K97OBhfpO9WS3qCINjVNinXV/6/EtCdJwkIoAXG12apwF5kI9/MYjr0XDfF i8tJkOVTzUAmlwLqD/2frvGD+T1pvhvxLh6VzL5llesYvahTyJz3LMVJTJwvNb18 R3948iuGta10pFJkeZoU =kifu -----END PGP SIGNATURE----- --k6OSAPqIPvs9WdiQE9jc6w2b4Bjp35j95--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55BB8D38.5000500>