Roadmap: https://github.com/cobbler/cobbler/wiki/Roadmap Meeting Room: https://meet.opensuse.org/cobbler
It will make the DHCP server configuration basically static and at least ipxe/grub-wise there will be no more point in actually syncing the configuration files to the TFTP root
In theory it is already implemented. Because even though we need to files not in the TFTP Root, we then need them on the webserver root to be accessible.
Well but that we could serve in theory with out own webserver.
Thus no need to copy kernel & initrd around all the time then.
This would be neat indeed then.
Serving kernel and initrd by internal server is not necessary since Cobbler only need to serve the proper config with proper links
Yes but how do we generate that links? Since currently Cobbler knows the paths to the Kernel & Initrd I think just serving that file would be best instead of putting additonal logic into accepting more path possibilities. Also then it is under Cobbler control and we don't need to support addtional setups. I mean I can understand your reasoning but so far I don't see the "big" advantage in it compared to mine.
That's how I do it now
I've just prepended the address of the server to initrd and kernel
And Grub fetches them over http
The only missing part is ipxe-like templating for Grub
UEFI HTTP booting (pure http, not the kind that uses ipxe chainloading) requires updates to the dhcp.conf file in order for the httpboot client to find the boot files from a web URL. In my former job, i had to hack my way through figure most of it out. It would be nice if official directions can be given (or maybe the dhcp.template file could include a section for http booting by default). Unfortunately, i didnt finish the implementation and am no longer in that role. It would be nice for my replacement to have a good doc though. Thoughts?
For reference, i made heavy use of this doc: https://documentation.suse.com/sles/15-SP2/html/SLES-all/cha-deployment-prep-uefi-httpboot.html
But HTTPClients
And yes, filename https://...
That's not a big deal
AFAIR I still have the HTTPBoot config for Grub lying around
Since the default template is still have to be edited, maybe the RTD article is good enough
I'm facing an annoying situation on cobbler, I've defined a bunch of systems using the same procedure, and now, ones work and others not. The only difference that I saw is this:
I'm trying to remove it via web dashboard, but after resync the cobbler status this conf is persistent and reappers again
any clue on what is the possible missconfiguration?
thanks in advance
(i'm not sure if this parameter is inherited from the profile or other object on cobbler)
after one restart:
cobbler.cexceptions.CX: "Error with distro rocky-8.4-minimal-x86_64 - kernel '/var/www/cobbler/distro_mirror/rocky-8.4-minimal-x86_64/images/pxeboot/vmlinuz' not found"
????/
this disapeared without modifying anything'
Also please don't put files inside the Cobbler managed directories.
Regarding the webUI Situation: Can't help there for now since the old UI is gone and the new is a WIP...
also, Im facing some issues trying to pass files with the partitioning definition using snippets
but this I don't know if its related directly with cobbler or the kickstart against rocky8
@SchoolGuy, looking at the cobbler-web github I see '[root@localhost local]# npm install
npm WARN saveError ENOENT: no such file or directory, open '/usr/local/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/usr/local/package.json'
so... what syntax did you use for the npm init? I know I need to run that to create the package.json file but no clue what you used. What is in your package.json?
npm WARN saveError ENOENT: no such file or directory, open '/usr/local/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/usr/local/package.json'
so... what syntax did you use for the npm init? I know I need to run that to create the package.json file but no clue what you used. What is in your package.json?
@InterceptorF: We are using Angular and thus you need the Angular CLI available. The
package.json however should be just a normal npm file. I am using npm on a regular basis with that file. The project is kind of very very early but I am working on implementing the XMLRPC API currently: cobbler/cobbler-web#14
9d0cd7d2: Tat sounds like a lot of trouble. Sorry to hear that Cobbler broke. Do you have an idea what broke it? Maybe a package upgrade or a custom script?
1 reply
not a problem at all, I had all the configs tracked on a git repo, so it was quite easy to recover the environment