In this BSD Now episode, hosts Allan Jude and Kris Moore interview Sean Chittenden of Groupon. They discuss the ways ZFS has saved his data, in addition to Groupon’s recent switch to FreeBSD. Hit play below to tune in:
This article by Josh Paetzel informs users on implementing FreeNAS in a virtualized environment.
FreeNAS is the world’s most popular open source storage OS, and one of the more popular questions I get asked is, “How do I run FreeNAS as a VM?” Due to the number of caveats required to answer that question, I would typically short-circuit the conversation by recommending against it, or only recommend it for test environments since the prerequisite knowledge required to “do it right” can’t be passed on quickly. Somehow over time, this message morphed into a general consensus that “you cannot (or shouldn’t) virtualize FreeNAS at all under any circumstances”, which wasn’t my intention. So, I’m here to set the record straight once and for all: You absolutely can virtualize FreeNAS.
Whether you are test driving the functionality of FreeNAS, testing an upgrade for compatibility in your environment, or you want to insulate your FreeNAS system from hardware faults, virtualization can provide many well understood benefits. That said, while FreeNAS can and will run as a virtual machine, it’s definitely not ideal for every use case. If you do choose to run FreeNAS under virtualization, there are some caveats and precautions that must be considered and implemented. In this post I’ll describe what they are so that you can make well-informed choices.
Before we get started though, I should probably start with a disclaimer…
If best practices and recommendations for running FreeNAS under virtualization are followed, FreeNAS and virtualization can be smooth sailing. However, failure to adhere to the recommendations and best practices below can result in catastrophic loss of your ZFS pool (and/or data) without warning. Please read through them and take heed.
Sean Chittenden speaks about Groupon’s use of FreeBSD during BayLISA June 2015.
Groupon is making use of FreeBSD for its databases. In this talk, the following will be covered:
Why Groupon made the switch
What have been some of the benefits
What performance impacts have been observed
What did it take to begin supporting FreeBSD for production use
What have been some of the benefits
What were some of the challenges that were encountered from the
Interesting work happening in FreeBSD that is relevant to the future
This short tutorial will show you how to get Sonarr set up on FreeBSD.
Installing Sonarr on FreeBSD isn’t hard, but does require several commands. If you aren’t familiar with Unix or Linux, this guide should hopefully be enough to get you up and running. This guide was tested under FreeBSD 10.1-RELEASE.
If you want to do this safely, install and run it inside a FreeBSD jail.
mv /usr/local/etc/pkg.conf /usr/local/etc/pkg.conf.backup pkg install mono mediainfo sqlite3 cd fetch http://download.sonarr.tv/v2/master/mono/NzbDrone.master.tar.gz tar -xzvf NzbDrone.master.tar.gz ee /etc/rc.d/run_drone
At this point you have a text editor open. Copy and the paste the following line into the editor:
/usr/local/bin/mono /root/NzbDrone/NzbDrone.exe --nobrowser &
- Hit Esc, Enter, Enter to leave editor and save changes.
chmod 555 /etc/rc.d/run_drone
At this point Sonarr is installed, and we have it set to start on boot. You can execute run_drone, reboot the system or restart the jail if installed into one.
If you are wondering what is going on in the commands, here’s a brief rundown. FreeNAS 9.2 may have an older version of pkg installed. By moving the configuration file, it will heal itself and just work™, although this should not be necessary on newer versions of FreeBSD. Then we install mono, mediainfo, sqlite3 and all their required dependencies, including perl. Next up is Sonarr itself. Grab the files and extract, simple enough. Lastly we need to get Sonarr launching at boot, so we make a small script in rc.d which gets run at boot.
Unix experts will see that this is very hacky and insecure, especially as everything is running as root and listening on all IPs by default, so it’s a really good idea to put this inside a jail.
This tutorial by user Kenno shows us how to get PostgreSQL server set up on Raspberry Pi from FreeBSD port.
Before I wrote this blog post, I had thought there was no binary package for PostgreSQL server for FreeBSD 11 running on Raspberry Pi. Hmm… how wrong I was! I just wasted the whole night compiling Postgres from source. DOH!
Anyhow, here’s the step I took to do it. If you’re familiar with FreeBSD, there’s nothing new here. But, I only use FreeBSD once in awhile, and so I tend to forget a lot what I do.cd /usr/ports/databases/postgresql94-server make config make install clean
After a very long time of waiting, I was presented with the following message:To initialize the database, run /usr/local/etc/rc.d/postgresql initdb You can then start PostgreSQL by running: /usr/local/etc/rc.d/postgresql start For postmaster settings, see ~pgsql/data/postgresql.conf NB. FreeBSD's PostgreSQL port logs to syslog by default See ~pgsql/data/postgresql.conf for more info ====================================================================== To run PostgreSQL at startup, add 'postgresql_enable="YES"' to /etc/rc.conf
Let’s initialize the database:
During the last Bay Area FreeBSD User Group meeting, Michael Berman of TidalScale gave a presentation on building a distributed hypervisor. The talk was held at Citrix Startup Accelerator. Click play below to tune in:
BAFUG June 2015 – https://www.youtube.com/watch?v=f-ug6B6ycng
Xin Li has just been appointed as the new Security Officer as part of the FreeBSD Core Team. Congratulations sir! We also send our best wishes to Dag-Erling and his family.
Dear all, With immediate effect, the FreeBSD Core team has appointed Xin Li as the new Security Officer. Congratulations Xin! The previous Security Officer, Dag-Erling Smørgrav has unfortunately been unable to continue in the role due to his family circumstances. As is usual, he proposed his successor when he tendered his resignation to Core. Xin was formerly the Deputy Security Officer and Core was glad to confirm his appointment. Core wishes to thank Dag-Erling for his valuable contributions during his time as Security Officer and wishes him every future success. Traditionally the hand-over of the Security Officer role has been announced by the departing Security Officer. Unfortunately Dag-Erling has not been able to do that, so in this instance I have been requested to make the announcement in his stead. Matthew -- FreeBSD Core Team Secretary core-secretary at FreeBSD.org
Last week the FreeBSD project released an errata notice for the sendmail service. While the notice itself covers all the technical details, what has essentially happened is OpenSSL and related software have begun rejecting 512-bit and lower DH parameters. This change protects services against the OpenSSL “Logjam” vulnerability and will hopefully make us all a little safer.
The bad news is that sendmail, as it is shipped with FreeBSD, does not make the grade when it comes to the security restrictions. As a result, FreeBSD systems which have been recently upgraded with security patches may no longer be able to send e-mail messages through the sendmail service. Administrators may notice they are no longer receiving status reports via e-mail or local users may not be able to send out mail messages.
The good news is there is an easy fix, we simply need to generate a new DH parameter file on our FreeBSD system and restart the mail service. This can be accomplished with just a few commands from the shell. In a terminal, as the root user, run the following commands:
openssl dhparam -out dh.param 2048
The above commands will create a new DH parameter file with a 2048-bit key and restart the sendmail service. At this point the sendmail service should resume working. Some people have reported on the FreeBSD forums that they also had to reboot their computer after applying the above fix.
This article compares FreeNAS with NextentaStor Community. They are both storage operating systems, FreeNAS being based on FreeBSD.
High Level Comparison
FreeNAS and NexentaStor Community are Storage Operating Systems that support many of the same features like CIFS, SMB, NFS, and iSCSI protocols. Each system works with OpenZFS (v5000) with feature flags, most virtualization platforms, and have support, training and certification available.
NexentaStor Community Edition
Alex Aizman and Dmitry Ysupov created the Nexenta OS project after Sun Microsystems released the bulk of its Solaris operating system under free software licenses as OpenSolaris. NexentaStor is derived from the former Nexenta OS and based on the illumos operating system, utilizing OpenZFS as an underlying filesystem. The software delivers unified file and block storage services to consumers. NexentaStor Community edition is free up to 18TB of raw storage and does not include all the features of the professional version.
In this BSD Now episode, hosts Kris Moore and Allan Jude interview Marc Espie regarding adding additional security measures to dpb, OpenBSD’s package building tool. Hit play below to tuen in: