Getting back to basics

It's been a little while since I have been able to write a post up here thanks to finding a new job and just generally being busy.

Unfortunately I had another NAS fail this week, it was my mum's old computer repurposed into a Nas because it had 6 SATA II ports so easy to cram 6TB of storage on it for storing virtual machines. Though it's age finally started to catch up with it after another nearly full year since mum retired it to me it ended up not failing completely but it was rebooting and blue screening every few minutes. It's unfortunante but it did encourage a good network refresh.

So first things first was stripping the failed machine and dropping the disks into one of the hypervisors that had enough SATA ports and thus was born the Nasevisor XD

Here is a couple of pics from that adventure.

Unfortunantly all my current hypervisors are just old PC's built with stuff off hand and a couple of old laptops that have decent procs and 16GB ram but they get the job done until I can afford to buy something way more professional.

But all the hypervisors have been reinstalled and are running Windows server core 2016 with Hyper-V and the primary reason I went back to Hyper-V is simply Windows domain management makes life nice and easy and under bench testing I don't really notice much difference between server core and xenserver as far as overhead goes.

Goals for this refresh is really to put in place a really solid devops environment with full orchestration and DSC (Desired State Configuration) and to start working alot more with unikernels for services because I think that will be fun and really kick my container focus to the next level in the forever hunt for performance.

That said there is also another reason I want to start working with unikernels and that's really just to learn more about how kernels interact with hardware, I mean I understand how it all works but I have never written a driver or kernel module in any language so I think it will be a great experience to do that.

My first unikernel goal is to write my Eve online discord bot in C++ (currently in C# ofc :P) and run it in a unikernel and build up orchestration for that so if the bot ever enters a failed state (I.e throws an exception) the unikernel is able to destroy itself and a new one to be scheduled in its place all of course stirring stack traces some place they are easy to get at perhaps a DB to start off with.

The second goal I have is to write a driver for includeOS (current weapon of choice in the unikernel space) for the Hyper-V network interface as at the moment there isn't one and the network driver that comes with includeOS doesent appear to be working with the gen1 or gen2 NICs.

From there who knows.

I have run into a few minor road blocks though, the first one is my CI (Jenkins) for obviously doing CI/CD but it will also play a role in orchestration at this stage, I originally intended to go with Jetbrains Teamcity but the free version only allows for 20 build configs and I'm expecting a few more than that with back of the napkin maths and Teamcity is out of my price range for the next steps up at this stage.
So I went back to Jenkins because open source for the win but I'm currently having a huge issue getting the Jenkins master to configure windows slaves with DCOM due to some arguments Jenkins and windows has had they just aren't being friendly at the moment lol, so once I get that issue sorted out I'll be able to dive right in and really get the ball rolling on some cool projects that I want to make some YouTube videos for and really just get back into the fun stuff instead of nursing a bug or two that have been about for years.

Slightly off topic before I close this post out, I'm also playing eve online again a crap ton so hopefully here soon I'll be able to knock out some cool solo/fleet PvP vids for those who are interested in mixing it up a bit with some gaming :D

Well I think that about wraps up this post stay tuned for more posts on all the things it should be fun :D