Automate MaaS (Metal as a Service) PXE Boot Server Install With Ansible
Vložit
- čas přidán 13. 09. 2024
- Quick Metal as a Service 3.1 server install using ansible playbook. The video covers the following MaaS features.
- Setup using two CLI commands and an ansible playbook
- Configuration of the server via the web interface including subnet, DHCP and image configs
- Deployment of a Ubuntu 22.04 node
- Remote node access
Refs:
Ansible scripts used in the video
github.com/Wor...
Work From Home Tech CZcams Channel
INTRO: / @workfromhometech
Ubuntu Install: • Quick Ubuntu 20.04 Bas...
Bare metal Kubernetes hands on tutorial with MAAS and Juju
• Bare metal Kubernetes ...
PI-HOLE
pi-hole.net/
Hardware
servermonkey.com - Věda a technologie
You can't even imagine how your video and github repository regarding the topic helped me with my work! I've already managed to create 2 PR with some changes included. Great job!
Happy the video was of use. I also so some git repo comments I need to review.
Hey there, do you still use Maas? I am having dhcp issues and was curious if you still use Maas or if you found something better?
I still use it. I am actually working on an updated video coming out soon. I am using it right now with an external DHCP server if you are interested in doing that. As long as the DHCP server you are using supports TFTP and Secondary boot server options it should work.
nice work and a nice video.
Hi..
Very good one.. do we have video on same deployment using terraform
Actually, I would love to use Terraform. I normally work with Ansible, but additional AWS support is increasing the priority of Terraform.
Hello, i am curious if this setup also can boot Windows?
Yes. You can PXE boot Windows, but the image requires more setup work. If you look in the MaaS configuration it even has a section for the Windows license management. I think you will find more info if you go to the MaaS git repo maas.io/docs/how-to-build-a-windows-image
@@workfromhometech Thank you! i will be taking a look at it :)
Been looking for an easy way to do this thank you. I will try the playbook today. I'm not an Ubuntu fan but curious to try Maas.
On another note, blur out your key dude.
I have recently been looking at an easy way to make more images for MAAS.
@@workfromhometech Packer, I think, is the way to go. I need to make Rocky and Debian images and will be looking at Packer with MAAS
@@rickhernandez2114 I agree on using Packer. I have started testing an initial Rocky 8.6 image and will update the playbook for RPMs. Practical advice on the hiding the SSH key, but I knew I was going to reinstall multiple times.
i'm blocking on maas-enlisting-node login. any thing missing?
What OS did you deploy? The user accounts can vary between ubuntu, CentOS, Alpine and root will most likely be disabled.
Congratulations on your work. I don't know if you can help me, but I have difficulty booting PXE. The error message is: "NBP filesize is 0 Bytes. NBP filename is ipxelinux.0. PXE-18: server response timeout ". Thank you
Hello and thanks for the question. Since it sounds like you are getting to the DHCP Boot file options, I ask this question: Would you happen to know if you are using BIOS or UEFI boot mode? Sometimes UEFI and secure boot cause issues.
@@workfromhometech I really appreciate your answer. In fact, I tried both, Legacy Only and UEFI First, existing at Asus X-99-Win / IPMI Bios. The return is similar in both Legacy and UEFI. I am grateful for the hypothesis you suggest, and I will now look at that angle of boot security. I wish you success in your work.
@@cleitonpena4578 There are many points of failure, so I would first isolate the issue to the server or the client first. Then I would try different ones depending on if its the server or client. ISC DHCP and a Nginx web server can replace a PXE boot server. Shoot me a twitter DM and I can attempt more detailed help. Also tcpdump can also occasionally help reveal issues.