Before I started this project I had various hosts setup at various providers as well as at home.
These handled varied services including:
Jenkins for performing CI builds of all of my opensource projects with separate build servers for amd64, arm7 & arm8 cpu architectures
Sonatype Nexus for managing build artifacts
Geoserver handling dynamic mapping for my mapping site
PostgreSQL instances for various online & offline databases
Live feeds from Network Rail, National Rail Enquiries (Rail Delivery Group), USGS (United States Geological Survey) and others
Archiving the live feeds
Now with one of the providers removing support & soon the actual nodes for some of their server types which hosts Jenkins, Nexus, Geoserver & the amd64/arm8 build severs I needed to find suitable replacements.
At home I already had a large collection of Raspberry PI’s some dating from 2012 so I had a reasonable collection of machines for adding to the cluster so all I needed was to add a shared filesystem, support for AMD64 builds & racking to house it all – previously I had some in cases, others without & it was a mess…
In recent months I’ve been setting up a new cluster at home to replace some of the hosts I have in the cloud. This has become more important as one of the hosts I use is removing support some of the types of server that I use with the aim of removing them completely later in the year. Unfortunately there are currently no other providers out there that provide similar servers are a similar price so I took the decision to migrate some of the services which don’t need to be external back in-house.
So this is the beginning of a series of articles on that migration process including setting up the various nodes in the cluster, how they are managed & how they are racked so that they don’t take up much space.
At Christmas I treated myself to a new machine, a BBC Master 128. It’s that new that it was manufactured somewhere between 1986 and 1993 – if you are into retro-computing you know what this is like.
Anyhow, this machine is in very good condition. It’s been refurbished with new capacitors in the power supply (something you must check on the BBC’s as they can go bang if you aren’t careful).
It also came with a GoTek USB floppy emulator. This is a device that connects to the BBC (and others like the Amiga) as if they were a real floppy drive but instead of a disk it uses a standard USB stick which can contain images of the original disks. So many you could probably have a copy of every bit of software for the BBC micro ever produced on floppy on one stick!
Now this is perfectly fine if you have your software collection on it & rarely add anything but if you are doing any development and need to regularly add or update disks it’s a pain as you have to unplug the USB stick, put it in to your main development box, mount it, copy a 200K file (thats the capacity of a standard BBC DFS 40 track disk!), unmount it then plug it back into the drive.
You can tell it’s tedious and if regularly done could cause additional wear & tear to the contacts!
So to make this far easier I took a Raspberry PI Zero W and used it as the flash drive. In the above picture you can see a white USB cable in the GoTek, thats got the Zero on the other end of it.
If I needed to add or update a disk I can simply use SCP to copy the file to the pi and the GoTek then sees the new disk, I select it & the BBC can read it. From upload to opening it on the BBC can literally be a few seconds.
This is a good article so I’m not going to repeat it here except you don’t need to do all of them & there’s a few errors in that article which I will repeat here:
Step 4 is not needed if you used a minimal Raspbian image – i.e. no need to use the full desktop one, use the lite image as the base.
For step 6 use the GoTek as the power source not the TV as used in the article & yes for now it is being powered solely by the drive it’s being used on.
You can ignore Step 9 as we won’t be using multimedia – you could use a bbc disk image here instead
Step 10 has the errors. Here it mentions gmassstorage this is wrong & I think it’s the formatting on the site that’s broken it. Replace all references to that with g_mass_storage not the _’s, some CMS’s use _ to say underline which you can see on that page.
Steps 11 & 12 are optional – I did them but don’t use them
That’s effectively it, except a comment about powering the PI (which is in step 6 of that article).
Now I am using the GoTek to power the Pi – so there’s just a single USB cable from the GoTek to the usb port on the PI (not the PWR IN). This is fine as my GoTek has it’s own power supply.
However if you were to use an external supply for the PI, then you must cut the red wire inside the micro USB cable else you’ll feed additional power from the PI to the GoTek as well as the PI suddenly having two 5V supplies feeding it – which will cause damage to both devices!