Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 31 Jul 2015 10:22:39 -0400
From:      Allan Jude <allanjude@freebsd.org>
To:        freebsd-jail@freebsd.org
Subject:   Re: sysutils/iocage in a NAS environment
Message-ID:  <55BB84AF.5040808@freebsd.org>
In-Reply-To: <55BB4CC5.2050004@free.de>
References:  <55BB4CC5.2050004@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)
--sphNnMCWB2fa62iGji3SvGQDq7QaDJJs7
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 2015-07-31 06:24, Kai Gallasch wrote:
>=20
> Hi.
>=20
> Just read that FreeNAS 10 is going to use sysutils/iocage for managing
> local jails on the NAS. That is great news and it will give iocage more=

> publicity and a wider user base!
>=20
> I am currently testing a FreeNAS 9 as a NAS for my FreeBSD servers. Eac=
h
> (FreeBSD 10) server is running between 10-50 iocage jails.
>=20
> iocage's documentation states that each iocage installation needs a
> zpool to run on.
>=20
> 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 based=

> 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)
>=20
> Does this approach make any sense when both performance or stability ar=
e
> needed?
>=20
> Is it generally adviseable to use zpools on iSCSI targets, because they=

> are basically iSCSI exported zvols running on top of another zpool?
>=20
> Regards,
> Kai.
>=20

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
Allan Jude


--sphNnMCWB2fa62iGji3SvGQDq7QaDJJs7
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)

iQIcBAEBAgAGBQJVu4S7AAoJEBmVNT4SmAt+7LIP/j5S4CuAVnmj/qSkCrW77yHY
0Cwbce/S97piKuVbJc0VTQupNeRnXIRGX/GL3vXDPDmh6xbjCuU/OMumXleE+bv6
SJ3jsL7+7JFeTUWGJVcqLTKK0ZL3NFsZ9U9MIkCY46WGvQzK8I9S67aqFvKdEi7a
tW2PIvqxo9qg1fS/cRTC9JWcZT0gPX6/qBKD3Ocvw97J1RJQoV/hNPIUprGDe2kC
hmSrXZ3k5Q9fmBPs/smdL9ctRP9Ib7oPX/b8XY57sEclv9mbdBLixBWIbuYYsqZH
b2kv12y17ObtAVJTeGn4WfexF77zm15UEJMQSG0vWgFf+RJvWbnvJWsv6GwJqfFq
26Gv1KsUSDexJebg2F/dEDkcpEKXxL4Fq5TQ1QhpCqb9X5nkgK9EH1ahIcmXzqOt
0btkFt5/62JR2FZOA5y+aBtI/1VvOPWYZkJ7uJ7ZFd7tKZARATsQwvlFwNJ3es7i
6mJDhcttA0R2zYuxM2ne2BZC/0lYfIB+/N5DuIlhOMELgBtW1GZthL2dcjXuyXXY
RcoZ5+em/djF9DRg7GcPpbGmrmcPqV574fx0I8IrJVhXKqFcmSfppMjNh3SH1ps5
YX5jscJ87NsjPHe8ffJ3kgL/GlBvNhk0kEDiKixcYLU2M9tXTRz8lLPWb3r2kZeE
gPv6P8PmqRvHDxxNTEAp
=sbPk
-----END PGP SIGNATURE-----

--sphNnMCWB2fa62iGji3SvGQDq7QaDJJs7--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55BB84AF.5040808>