I found that knowing about the variable @@server@@ is very useful.  I can create yum.repos configuration files at the time of build that point to the cobbler server that you build from…  Are these documented anywhere?  I would like to know what other variables cobbler uses that I could also use.

 

For example one problem I am currently trying to solve is to define the variable in the kickstart file for the network device.  Sometimes I use eth0 sometimes eth1.   When I use koan for my rebuilds this needs to be set to the interface that koan used to connect to the cobbler server..  Currently I use ksmeta to define $iface in a profile for this and then pass that into the ks file, but  I wonder if there is a magic cobbler variable that already sets this.

 

# Network information

network --bootproto=dhcp --device=${iface} --onboot=on

 

Thanks,

 

Jolynn

 

From: cobbler-bounces@lists.fedorahosted.org [mailto:cobbler-bounces@lists.fedorahosted.org] On Behalf Of Vreman, Peter - Acision
Sent: Wednesday, November 19, 2008 5:23 AM
To: cobbler@lists.fedorahosted.org
Subject: cobbler_server environment snippet

 

Might it be a good idea to include by default a snippet that sets the COBBLER_SERVER environment?

Below is the snippet post_cobbler_env that I’m now using:

 

echo "export COBBLER_SERVER=@@server@@" > /etc/profile.d/cobbler.sh

echo "setenv COBBLER_SERVER @@server@@" > /etc/profile.d/cobbler.csh

 

Regards,

Peter


This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.



This e-mail and its attachments are intended only for the individual or entity to whom it is addressed and may contain information that is confidential, privileged, inside information, or subject to other restrictions on use or disclosure. Any unauthorized use, dissemination or copying of this transmission or the information in it is prohibited and may be unlawful. If you have received this transmission in error, please notify the sender immediately by return e-mail, and permanently delete or destroy this e-mail, any attachments, and all copies (digital or paper). Unless expressly stated in this e-mail, nothing in this message should be construed as a digital or electronic signature.