YunoHost might be the spiritual successor to Microsoft Small Business Server.

Microsoft Small Business Server (SBS) was the product everyone needed in the early 2000’s and earlier. It was their “Business in a box” offering that provided every service a small business (under 50 users) could want. Email, Calendar, File Sharing, Directory Services, DNS, DHCP, Webhosting. It was truly the go-to deployment for most companies.

I administered 3 different versions of SBS, and did a fresh deployment of 1 before Microsoft killed it off for their new hybrid-cloud solution of Microsoft Server Essentials paired with Office 365.

To be clear, SBS was not a perfect product, but in my experience, was a fine, affordable, one-time expense solution that worked for a great number of companies in my area.

So, the SBS pitch thesis went something like this, “I can give you the ability to login anywhere in your office, have professional email using your .com name, share files between computers, and all of this for a low entry cost of (WhateverTheBoxCosts) Dollars.

Easy to sell, you either want the stuff, or you don’t.

The Microsoft Essentials Pitch now goes something like “I can give you the ability to log in anywhere in your office, and share files between your computers for a low entry cost of (WhateverTheBoxCosts) Dollars, and if you want professional email and cloud storage and it’s between 8 and 15 dollars per month, per user, forever.

Less appealing right? You have a significant upfront cost, and then now I have also baked in overhead forever, that only swells as your company grows.

Enter YunoHost

YunoHost describes itself as “a server operating system aiming to make self-hosting accessible to as many people as possible, without taking away from the quality and reliability of the software.”

In practice, at least for my use case, YunoHost was an incredibly easy to deploy, rock solid Email, cloud storage, and web hosting platform. In fact you’re reading on a YunoHost box right now!

Deployment is very easy, they have well written guides for deploying on hobbyist platforms like Raspberry Pi, Certain ARM boards or business class Debian linux servers.

Installing on a Debian VPS can be as easy as 1 command, and then filling in forms as prompted.

curl https://install.yunohost.org | bash

That’s it, really. This platform is dead simple to deploy and would be easy to manage as any other Debian based appliance. This is the new business in a box. It supports SSO via LDAP, IMAP mail, two web mail clients, DokuWiki, NextCloud, XMPP based chat services, WordPress.

This is a platform I would like to see more clients use, here’s the pitch.

“I can give you the ability to log in using 1 set of credentials (directory services), regardless of what computer or device you’re at. You can have as many professional email addresses and users as you have storage for, cloud storage under the same limitation, group messaging, and total control of your data, all for the price of the hardware it runs on.”

Compelling, right?

Moving to XCP-ng in my lab, possibly the datacenter.

I’d like to start with the preface; I have been a Hyper-V advocate/evangelist since 2008R2. In my main job, all of our infrastructure runs on Hyper-V server 2016, we’re a full Microsoft stack house, IIS, SQL Server, AD the whole whack. I have been drinking the windows koolaid since I started my IT career. Until very recently it had been my experience that open-source did great on the web, and that’s where it stayed for me, my clients, and my company.

In my testing/toying with XCP-ng, I am finding it very difficult to make a strong case for choosing Hyper-V over XCP-ng. In some ways they have feature parity, in others I’m finding XCP-ng to be superior.

How did we get here?

It started with a video from Lawrence Systems / PC Pickup. From my understanding, they are an IT consultancy in the Detroit area and their technical skillset focuses strongly on open source deployments for core infrastructure (think pfSense, freenas, etc.).

Unsurprisingly they have several videos and tutorials evangelizing XCP-ng and made a compelling enough case for me to deploy it on my homelab blow-up/tear-down/testing cluster.

First Impressions

Simple Installer

Unlike some linux based installers, XCP-ng has a very minimal, easy to understand and well documented install process. For me it was a matter of pushing enter a few times and letting it do it’s thing.

Lower OS Overhead

This, honestly was expected but because XCP-ng is linux based the core os runs very lean. Hyper-V suggests a minimum of 4GB RAM for the host, and then whatever else you’d want to allocate for the guests. XCP-ng suggests a minimum of 2GB per host, but in my uses I’ve never seen it use more than 700mb.

Management Options

In Hyper-V you basically need a Windows 10 client with RSAT tools and joined to the same domain as your host to manage your hosts remotely. I understand that it is technically possible to do this without joining a domain but it’s not practically sound or really scaleable.

With XCP-ng I was able to manage the hosts individually or together in a single interface using a tool that is packaged with the hyper visor called “XCP-ng Center” similar to Citrix’s Xen Center. This tool allows for individual user logins, per host, independent of your local machines credentials.

Additionally you can install a wonderful open source tool from the maintainers of XCP-ng called Xen Orchestra. You can either try the paid, pre compiled appliance by running a few shell commands on a XCP-ng host of your choice, downloading it and importing it via XCP-ng Center, or compiling it from source on your own for a Libre experience. Deploying XO is really where a XCP-ng deployment starts to shine, you can think of it as a similar appliance like the Unifi Controller software, it allows for centralized, web based management of all of your hosts, and a ton more features for your private cloud like user-based resource allocation, allowing users to self service deploy VMs on your hosts without IT intervention.

Storage Flexibility

Initially I deployed it using local SR’s. After I got comfortable using XenMotion and some of the other features, I wanted to start using XCP-ng’s version of clustering, “pooling”. To do this you need shared storage between all of your hosts, and this is where another very delightful discovery was made for me.

XCP-ng supports using SMB shares as SR’s for VDIs. I.E. You can use any typical SMB fileserver as shared storage between hosts. I understand that there are much more performant file systems for this, but the availability of this feature makes XCP-ng almost a no-brainer for home labbers. Of course XCP-ng supports NFS and ISCSI for shared storage like you’d expect to for an actual production environment.

Final Thoughts

I think in short, XCP-ng has really changed the way I look at my current virtualization deployments, and moving forward with smaller clients I think I’m going to run XCP-ng instead of hyper-v purely for the web management availability and lower overhead.

I want to deploy it on my core setup here at work, but we already have existing infrastructure to support Hyper-V and I can’t really validate making a change for change’s sake…yet.

A Mullet Deployment

Windows in the front, Linux in the back.

I’ve been working on a pretty interesting environment and I thought you guys might like to hear about it, I would also love to hear what you have to think in the comments! I’m contracting with a non-profit charity organization that is just getting started. Currently there are three users including the founder, they each have their own personal laptops 2 of them running Windows 7 and one of them running Windows 8.1 . They have the pretty standard office needs and they contacted me from a referral to see what I could do for them on their budget (which is tight).

After meeting with the founder already we hit our first snag, she’s very cloudphobic, borderline fanatical about the fact that she want’s to control all of the organizations data in house. That struck me as odd, but hey, every office is different right? Our only other challenges are that the budget really does not allow for nice hardware, and they are still pending for 501c status. What that translates to is we are going to have a hard time getting equipment.

From the discovery meeting I learned that this organization requires:

  • Active Directory
  • Network storage
  • Business class email and calendar
  • VPN access
  • Web server
  • WordPress website

I also learned that our challenges are:

  • We do not have 501c status yet (this could take months) which means we do not benefit from companies non-profit pricing schedules, and it will be harder to receive donated equipment.
  • The founder requires that everything is stored locally, she wants nothing in the cloud.

We couldn’t use Microsoft Server 2012 Essentials because of the email requirement and we certainly could not afford full Server 2012 and Exchange. I ended up going with Zentyal 3.3 which is a linux based small business server that gives *close enough* products that I thought would be a good fit considering all of our needs versus all of our challenges. (Added bonus, it’s free!) I purchased a HP ProLiant G7 N54L MicroServer an additional 500gb HDD and 4 GB of RAM. Which put us around $500 total for costs of server hardware. For networking I just went with the router/built it switch that the ISP provided.

Surprisingly It all went pretty well.

Everything was very simple to set up, it reminded me of Small Business 2008 is a lot of ways, the Zentyal GUI just walks you through it all and the entire build out took me maybe 4 hours of billable time. The only custom thing I had to do was install wordpress, which is a simple thing to do on linux, but this required me to change the management interface to listen on port 444 instead of 443. The entire build cost the client just under $3000.00 included the website I built out for them.

So what’s the catch?

Zentyal is not all there, yet. The domain acts like a Server 2000 domain, which is not necessarily a bad thing but if you get into a situation where you need to scale up, or add a windows server it could become a problem. OpenChange is still being proven and I’m genuinely un-sure of how it will perform over the long haul, Outlook 2010 seemed to think it was an exchange server so I have high hopes! Samba4 is not a Windows file server which could limit our ability to use Windows native network applications (Access, Quickbooks, Etc.). There is also the obvious red flags, the primary web server is also the primary domain controller, and mail server. All of the eggs are in one basket with no redundancy, maybe as funding increases and they receive their 501c we can revisit this project.

How would you have handled it?

I would love to hear about some other approaches from other geeks. What would you have changed? Would you have taken this project at all?

Who am I?

Hi there. My friends call me Jay! I’m nearly 30 and I work in IT.

I’m a technical leader and project manager with experience in data driven companies. I have worked both as a system administrator and software developer, and have several mobile and web applications in production today. 

Until recently I owned and operated my own consultancy where I served as the technical decision maker / adviser for several small businesses throughout the Frankfort area. My businesses main focus was web development and customized workflow solutions.

Lately I serve as Technical Director for my wife’s mixed media/graphic design company, and IT Director for a major transportation company.