The header encourages us to introduce ourselves, but the thread for that is closed ;-/
OK, so I introduce myself this way, nobody is forced to read it.
49 year old system administrator, mostly CentOS 5-8 (earlier also RHEL), private laptop Fedora 31 KDE.
Living in Finland, wife, 3 kids + 2 dogs.
At the moment unemployed, so lot of time to try out new things
Previous experiences with deployment tools:
Used RHN Satellite long ago (RHEL 5 based?)
At work recent years, mostly self-made scripts and later Ansible.
Very limited experience with Vagrant/Chef.
My infra / data center
I have in my garage some decommissioned blade servers (all of them Centos 7 with KVM), and a ProCurve Switch.
On those I run a couple of VMs with stuff for the family, like a fileserver and mediaserver (serviio); a DHCP server because the Zyxel ADSL gateway every few days got stuck (clients not getting and IP address), some web server (playground) for my wife, … all kind of stuff.
A job I applied to listed foreman as prerequisite, so I thought I try it out a bit.
What I have managed to do so far:
- installed one foreman server… and next day a foremen/katello server
(foreman 2.0 and katello 3.15, I guess).
- provides PXE kickstart booting via tftp and vsftp
- DHCP and DNS at the moment still use “old, own VMs”, edit files manually
( to do: make foreman do that with a proxy?)
- customized some of the kickstart/paritioning templates a bit
- connected one of the three blade servers as libvirt provider
- created on 1-2 VMs using all above.
(needed several attempts, sda vs. vda, another installation failed with an exception I don’t understand, …)
So on the long run my goal is to rebuild some of the VMs I had installed semi-automatically (kickstart, some scripting, plus some handful of basic stuff interactively (ifcfg, aliases, ssh keys, …) with foreman.
Why I am here:
I have created the computing resource for one of the blades; but when I want to create a new host, it still forces me to create a network with a MAC address?
The first VM I installed, I created it in virt-manager, then paused the boot to create it in foreman and enter the Mac address I got from the virt-manager gui.
So my question was, can’t foreman do the creation of the VM on the hypervisor itself?
Didn’t find anything with a Google search, so I thought I try this forum.
Used the search function to find is there any threads about my problem. Didn’t find any.
So I thought, I ask about it… first introducing myself.
Meanwhile… I have found the answer
==> Compute resources needs to be set up properly…
I had seen the “Compute profiles”, so I thought all is well. Looking at them again, I noticed one has to select a Compute resource for each profile. And after I had done that, now I can in the Create host dialog I can choose a profile, and now it allows the creation without that I have to specify a Mac address manually. Cool!
Well now the VM starts installing; but clicking on virt-manager it says “Viewer was disconnected”.
But starting a virt-viewer from the hypervisors commandline, it works…
(might be because my virt-manager connects as me but foreman connects as root …???).
And the installation fails again, because it can’t find sda. (by default I use virtio disk devices, which appear inside as /dev/vda/ , but the kickstart defaults to sda… need to figure out how to pass in that
“dev” parameter (( dev = host_param(‘part_device’) || ‘sda’ )).
Time do to more troubleshooting.
As said: Hello everybody!
Greetings from beautiful Finland!