[Spacewalk-list] Spacewalk-> cobbler define ks-server IP?

[Samuel_Suter at mcafee.com]

Jonathan

You should be able to control this via the server setting in /etc/cobbler/settings.

Remember that any change in the cobbler settings file requires a restart of the cobblerd service (and possibly a sync thereafter) to take full effect.

If you need more logic you can start playing with the templates in /etc/cobbler/pxe.

For example, if you need different IP addresses for different hosts, you could start using extra attributes in the system definition and query those in these PXE templates.

Regards

Samuel

________________________________________
From: spacewalk-list-bounces at redhat.com [spacewalk-list-bounces at redhat.com] on behalf of Jonathan Hoser [jonathan.hoser at helmholtz-muenchen.de]
Sent: 22 June 2014 10:50
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Spacewalk-> cobbler define ks-server IP?

Dear all,

I'm have once again come up with a problem, that I currently don't know
how to tackle:

We are reorganising our internal network, and thus have two subnets,
that do not know of each other (yet) (long story, routing, backbone
config,...).

And I'd like to initiate a number of servers in the new subnet,
of course installing from spacewalk.

The interface itself is not an issue, my spacewalk server does have an
interface configured for the new subnet,
it can ping/connect to whatever I need to.

HOWEVER.... when I do the PXE netboot,
the new installations will get all the initial kernel/boot/blah stuff
just all right, and
 then fail to get the kickstart file.

It took my a while, but I finally found out that cobbler is having fun here:
In the cobbler config, we only specify a spacewalk-/server-name String -
which gets converted by cobbler to the IP address
in question.
And stays the same, as long as cobbler daemon is up and running.
Once the DNS record changes, and cobblerd is restarted, and a cobbler
sync is executed,
all kickstarts-records in the tftpserver will show up with the
new/different IP.

But - that doesn't help me too much, since I still have a couple of
machines on the old subnet,
which are of course complainging about loosing connection to spacewalk.

So, do any of you know how to tell cobbler which IP to write into the
PXE files?

append initrd=[...] ks=http://[IP I want to tell cobbler to
use]/cblr/svc/op/ks/system/[SYSNAME from cobbler db]

And it is no good replacing them (semi-) manually, since these files
will get rewritten once in a while by cobbler...

So, if any of you would have a pointer for me (other than wait for the
subnets to merge/the routing to fully work)
I'd greatly appreciate your efforts!

With best regards
-Jonathan


--
Jonathan Hoser, M.Sc.
Institute of Bioinformatics and System Biology

WWW: http://mips.helmholtz-muenchen.de


Helmholtz Zentrum München
Deutsches Forschungszentrum für Gesundheit und Umwelt (GmbH)
Ingolstädter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir´in Bärbel Brumme-Bothe
Geschäftsführer: Prof. Dr. Günther Wess, Dr. Nikolaus Blum, Dr. Alfons Enhsen
Registergericht: Amtsgericht München HRB 6466
USt-IdNr: DE 129521671

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list