Even so cblr is set as an alias, should I not expect to have m2067 (the system created using cobbler) sitting in the directory structure at /var/www/cobbler/svc/op/ks/system/m2067 which is referenced in
ks=http://172.17.11.1/cblr/svc/op/ks/system/m2067 ?
I used
cobbler system add --name=m2067 etc ....
But the file is not in that place.
Also: I expected /etc/dhcpd.conf to have been modified to reflect the adding of the system. But there have been no changes.
cobbler report sytem shows
systems: ========== Name : m2067 Comment : Gateway : Hostname : Image : Kernel Options : {} Kernel Options (Post Install) : {} Kickstart : <<inherit>> Kickstart Metadata : {} Management Classes : [] Name Servers : [] Name Servers Search Path : [] Netboot Enabled : True Owners : ['admin'] Power Management Address : Power ID : Power Password : Power Management Type : ipmitool Power Username : Profile : cordelia Red Hat Management Key : <<inherit>> Red Hat Management Server : <<inherit>> Server Override : <<inherit>> Template Files : {} Virt Auto Boot : <<inherit>> Virt CPUs : <<inherit>> Virt File Size(GB) : <<inherit>> Virt Path : <<inherit>> Virt RAM (MB) : <<inherit>> Virt Type : <<inherit>> Interface ===== : eth1 Bonding Mode : Bonding Master : Bonding Opts : DHCP Tag : DNS Name : IP Address : 172.18.11.3 MAC Address : 00:15:17:00:32:48 Static : True Static Routes : [] Subnet : 172.18.0.0 Virt Bridge : Interface ===== : eth0 Bonding Mode : Bonding Master : Bonding Opts : DHCP Tag : DNS Name : IP Address : 172.17.11.3 MAC Address : 00:E0:81:5B:0F:2B Static : True Static Routes : [] Subnet : 172.17.0.0 Virt Bridge :
yacketrj at potsdam.edu wrote:
On 5/18/2010 10:12 AM, Lydia Heck wrote:
I downloaded and installed cobbler and configured it.
Then I started to setup an install server, adding a distro, some profiles and one system.
All looked most straightforward. However, when I looked into the file created for the system in /tftp/pxelinux.cfg I got
default linux prompt 0 timeout 1 label linux kernel /images/SL54-x86_64/vmlinuz ipappend 2 append initrd=/images/SL54-x86_64/initrd.img ksdevice=bootif
lang=kssendmac text ks=http://172.17.11.1/cblr/svc/op/ks/system/m2067
However, try as I might I cannot find
cblr/svc/op/ks/system/m2067 anywhere on my server system
/cblr is a alias setup in cobbler.conf :
AliasMatch ^/cblr(.*)?$ "/var/www/cobbler$1" ....
<Directory "/var/www/cobbler/svc/"> SetHandler mod_python PythonHandler services PythonDebug on PythonPath "sys.path + ['/var/www/cobbler/svc/']" </Directory>
Any idea?
------------------------------------------ Dr E L Heck
University of Durham Institute for Computational Cosmology Ogden Centre Department of Physics South Road
DURHAM, DH1 3LE United Kingdom
e-mail: lydia.heck@durham.ac.uk
Tel.: + 44 191 - 334 3628 Fax.: + 44 191 - 334 3645 ___________________________________________
On 5/18/2010 1:59 PM, Lydia Heck wrote:
Even so cblr is set as an alias, should I not expect to have m2067 (the system created using cobbler) sitting in the directory structure at /var/www/cobbler/svc/op/ks/system/m2067 which is referenced in
ks=http://172.17.11.1/cblr/svc/op/ks/system/m2067 ?
I used
cobbler system add --name=m2067 etc ....
But the file is not in that place.
Also: I expected /etc/dhcpd.conf to have been modified to reflect the adding of the system. But there have been no changes.
cobbler report sytem shows
systems:
Name : m2067 Comment : Gateway : Hostname : Image : Kernel Options : {} Kernel Options (Post Install) : {} Kickstart :<<inherit>> Kickstart Metadata : {} Management Classes : [] Name Servers : [] Name Servers Search Path : [] Netboot Enabled : True Owners : ['admin'] Power Management Address : Power ID : Power Password : Power Management Type : ipmitool Power Username : Profile : cordelia Red Hat Management Key :<<inherit>> Red Hat Management Server :<<inherit>> Server Override :<<inherit>> Template Files : {} Virt Auto Boot :<<inherit>> Virt CPUs :<<inherit>> Virt File Size(GB) :<<inherit>> Virt Path :<<inherit>> Virt RAM (MB) :<<inherit>> Virt Type :<<inherit>> Interface ===== : eth1 Bonding Mode : Bonding Master : Bonding Opts : DHCP Tag : DNS Name : IP Address : 172.18.11.3 MAC Address : 00:15:17:00:32:48 Static : True Static Routes : [] Subnet : 172.18.0.0 Virt Bridge : Interface ===== : eth0 Bonding Mode : Bonding Master : Bonding Opts : DHCP Tag : DNS Name : IP Address : 172.17.11.3 MAC Address : 00:E0:81:5B:0F:2B Static : True Static Routes : [] Subnet : 172.17.0.0 Virt Bridge :
yacketrj at potsdam.edu wrote:
On 5/18/2010 10:12 AM, Lydia Heck wrote:
I downloaded and installed cobbler and configured it.
Then I started to setup an install server, adding a distro, some profiles and one system.
All looked most straightforward. However, when I looked into the file created for the system in /tftp/pxelinux.cfg I got
default linux prompt 0 timeout 1 label linux kernel /images/SL54-x86_64/vmlinuz ipappend 2 append initrd=/images/SL54-x86_64/initrd.img ksdevice=bootif
lang=kssendmac text ks=http://172.17.11.1/cblr/svc/op/ks/system/m2067
However, try as I might I cannot find
cblr/svc/op/ks/system/m2067 anywhere on my server system
/cblr is a alias setup in cobbler.conf :
AliasMatch ^/cblr(.*)?$ "/var/www/cobbler$1" ....
<Directory "/var/www/cobbler/svc/"> SetHandler mod_python PythonHandler services PythonDebug on PythonPath "sys.path + ['/var/www/cobbler/svc/']"
</Directory>
Any idea?
Dr E L Heck
University of Durham Institute for Computational Cosmology Ogden Centre Department of Physics South Road
DURHAM, DH1 3LE United Kingdom
e-mail: lydia.heck@durham.ac.uk
Tel.: + 44 191 - 334 3628 Fax.: + 44 191 - 334 3645 ___________________________________________ _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Not a cobbler expert, but looking in the /var/www/cobbler/svc directory shows a python file which is used to handle the html request. Need to defer to someone who has python knowledge to explain how that script takes the url you mention and builds what it needs etc.
Excerpts from Lydia Heck's message of Tue May 18 13:59:28 -0400 2010:
Even so cblr is set as an alias, should I not expect to have m2067 (the system created using cobbler) sitting in the directory structure at /var/www/cobbler/svc/op/ks/system/m2067 which is referenced in
I believe it did this at one point, but then we moved to mod_python (and now we are moving to mod_wsgi) to do that templating on the fly. You will find the kickstart template that generates into the kickstart in /var/lib/cobbler/kickstarts. Which template is used shuld be set in the cordelia profile.
Cobbler does this so it can dynamically generate the template at request time. This leads to cobbler having the ability to do some very neat things. The templating generation tends to be pretty fast as well.
I used
cobbler system add --name=m2067 etc ....
But the file is not in that place.
Also: I expected /etc/dhcpd.conf to have been modified to reflect the adding of the system. But there have been no changes.
Have you run 'cobbler sync' after adding the system? The dhcp template is generated at sync time due to the amount of times it takes to restart the dhcp server.
cobbler@lists.fedorahosted.org