Since its inception, Project-Fifo has run exclusively on Illumos based operating systems. At first Smartos, and later OmniOS and Oracle Solaris. Today we are happy to announce the immediate availability of release 0.9.3 and with it FreeBSD support.
FreeBSD and Illumos have always seemed to be good friends rather than competitors in the operating system landscape. Not only do you rarely hear something bad said about the other from the communities, but there is a healthy level of respect and cross-pollination going on. BSD Jails inspired Zones; Crossbow inspired VNet, there is now DTrace, kstat and ZFS on BSD, and bhyve on SmartOS.
It is refreshing to see such cooperation in an otherwise extremely competitive field. This fantastic attitude inspires us. We are no Kernel engineers or distribution maintainers, but we know a bit about cloud management.
So in this spirit, we started making a clone of vmadm, a tool we learned to love on SmartOS, for FreeBSD. It is not done or perfect yet, but we are very proud of the progress and the excellent feedback and contributions to it we have already gotten.
However, that is not all, with vmadm on FreeBSD fifo, our cloud management system now works in combined environments letting users mix and match hypervisors and run FreeBSD jails along with SmartOS zones. In a way bringing two friends together.
As usual, we published the release notes (with over 100 related tickets!) as well as the update manual as part of our documentation.
We will release an all in one dataset later this week.
Just setup a production cloud on 0.9.2, great work, looking forward to upgrading to this.
Glad to hear that! I hope 0.9.3 treats you as good as 0.9.2 did :). Wehn you upgrade, 0.9.3 (finally) switches to a new dataset images, make sure to look at the upgrade section in the docs.
Noticed that the documentation seems to be using an older dataset (20170216T015949Z) while 0.9.2 supported 20170330T015208Z and the chunter setup file lists 20170706T001501Z. Any specific reason not to use the newer dataset?
Hi,
thanks for catching that. There was no reason to it, simply an oversight on my part – brain like a sieve and all that ;). Updated the docs! Thanks again.