- Joined
- Nov 12, 2015
- Messages
- 1,471
Loyal FreeNAS users,
After many long nights, too much caffeine, and 4 (count’em) RC’s we are pleased to announce that FreeNAS 11.0 is now available!
This release brings the underlying FreeNAS OS up to FreeBSD 11-STABLE, and with it some performance improvements, newer hardware compatibility and more. On the FreeNAS side we’ve now added the ability to run VMs through bhyve (BSD hypervisor), support for hosting S3 object-stores, an early look at our work-in-progress Angular UI, and the initial API / CLI versions of iocage jail management. In addition there have been a number of behind the scenes improvements, such as migrating to python3, which will allow us to quickly iterate upon the 11.X series, adding new features as we go.
Users who are ready to upgrade can do so today by switching to the 11-STABLE train from their user-interface, while those who want to start fresh can grab ISO’s at the usual download locations.
Thanks for your patience and loyal FreeNAS use! As usual, let us know if you run into any issues on our bug tracker.
After many long nights, too much caffeine, and 4 (count’em) RC’s we are pleased to announce that FreeNAS 11.0 is now available!
This release brings the underlying FreeNAS OS up to FreeBSD 11-STABLE, and with it some performance improvements, newer hardware compatibility and more. On the FreeNAS side we’ve now added the ability to run VMs through bhyve (BSD hypervisor), support for hosting S3 object-stores, an early look at our work-in-progress Angular UI, and the initial API / CLI versions of iocage jail management. In addition there have been a number of behind the scenes improvements, such as migrating to python3, which will allow us to quickly iterate upon the 11.X series, adding new features as we go.
Users who are ready to upgrade can do so today by switching to the 11-STABLE train from their user-interface, while those who want to start fresh can grab ISO’s at the usual download locations.
Thanks for your patience and loyal FreeNAS use! As usual, let us know if you run into any issues on our bug tracker.
Last edited by a moderator: