I should have been more clear. I’m happy for you to use any of my work to write a tutorial, it sounds like you are aiming for a CLI based approach and that does make more sense. I was just asking if you already know of any remote control hubs so I can look into getting one.
(I’m also OK to reformat what I have into markup and put it up here if you feel that is useful)
Ah sorry, yes I misunderstood you. I have been looking at uhubctl which we were thinking we could wrap with a REST API and then use the webhook driver: https://github.com/mvp/uhubctl
There they have a list of supported hubs, I have looked for a few of them on amazon etc but haven’t tried anything. For RPIs, I think the most important thing is to pay attention to the total power output + power output per port (2.4A needed I think?).
Hi Giles that is amazing! I was going to do something similar but life with kids keeps me from that kind of pace ;).
Let’s get a repo going where we can all contribute to make it better - both code for the service and guides. When we think it’s good enough we can make some noise about it, I’m sure a lot of k8s cluster builders will enjoy it.
@gilesknap - what can I say? I’m stunned at how quickly you churned that out. I took a look through the docs and the code and I’m really impressed that you made it pluggable which means it should be usable by almost everybody. Love the config idea too, wanted to do that myself :).
With this, and the guide for RPI booting from MAAS, I think it should be relatively simple to throw together a tutorial. I would really like to host it on maas.io/tutorials.
Seems like after many years we have an end-to-end solution for running an RPI cluster together with MAAS!
Hi @gilesknap and @anton5mith , thank you for your work on this. I am really interested by testing your tutorial, I may give you some feedback on it. I am new to MAAS but I would like to try to use MAAS to provision a cluster or RPi 4.
It would be the first step in my homelab project. My plan is to start playing with Juju, Kubernetes and the Charm operators.
The only thing I need now is to find some RPi4 … I hope this global shortage will not continue for too long
Giles and I have been working hard on a tutorial - it took a pause while I’m on vacation this week, but I hope it will be out soon (warts and all). I’ll announce it here in the MAAS discourse forum when it’s ready
Great, yes the “maas in 30 minutes” tutorial is designed to get you up and running with MAAS as fast as possible.
However, using multipass for the bare metal kubernetes tutorial might give you problems because of nested VMs. The bm k8s tutorial assumes you’re running on a bare metal machine, because it uses LXD VMs to 1) setup some simulated bare metal machines then 2) Juju will try to create more LXD VMs inside those VMs for ceph-mon -> at that point it might fail because you have 3 layers of VMs if you count multipass.
Or, perhaps you can put ceph-mon directly onto machines 0,1,2 without LXD, haven’t tried it.
In any case, the only thing I think stopping you from running things in multipass is the presence of those 3rd level ceph-mon LXD VMs. If you manage to get something working, let me know.
I am trying to get this to work without custom-patching MAAS and using the RPI built-in network bootloader.
So far I’ve managed to get it to pickup an IP address and attempt provisioning by creating this DHCP Snippet with the RPI dhcp/pxe magic numbers: [Source]
This picks up the TFTP server, but now I get “File not found” and “Firmware not found”
I think its looking for “start.elf” and “fixup.dat”
EDIT: Upon further inspection, looks like we need to supply bootcode.bin over tftp and then will try finding start.elf/kernal first in a serial subfolder than the root folder on the tftpboot directory? [Source]