Re: Config help? .. Cobbler 1.2.9
by Dylan Swift
Hi Frank,
I'll put some comments inline...
On 11 June 2010 11:46, Frank <support(a)server-1.com> wrote:
> The netmask in in this case actually "255.255.255.192".
so that means a maximum of 63 addresses available.
> With the below SAMPLE IP (fake IP) 212.44.88.10, if that would be my
> Cobbler server IP, would then the below "dhcpd.conf" configured okay?
>
> Specific questions:
>
> "option domain-name-servers" --> Would I add all the IP rangers I
> have? Separated with comma? For example:
> 212.44.88.1 212.44.88.63, 212.48.77.1 212.48.77.255;
>
> "option domain-name-servers" --> Can this be an IP that works for all servers?
This is a list of IP addresses that the dhcp clients will configure as
DNS servers (ie should end up as 'nameserver a.b.c.d' entries in
/etc/resolv.conf)
> # ******************************************************************
> # Cobbler managed dhcpd.conf file
> # generated from cobbler dhcp.conf template (Thu Jun 10 14:30:41 2010)
> # ******************************************************************
>
> ddns-update-style interim;
>
> allow booting;
> allow bootp;
> omapi-port 647;
>
> ignore client-updates;
> set vendorclass = option vendor-class-identifier;
>
> subnet 212.44.88.10 netmask 255.255.255.192 {
I think you mean subnet 212.44.88.0 netmask 255.255.255.192 {
> option routers 212.44.88.10;
ok, your cobbler box is the router, or gateway to the rest of the network
> option subnet-mask 255.255.255.192;
> option domain-name-servers 212.33.44.55;
your dns server for the dhcp clients will be at 212.33.44.55
> option domain-name "newdomain123.net";
the suffix of your dns domain is newdomain123.net. This should appear
in the /etc/resolv.conf file as an entry 'search newdomain123.net'
> range dynamic-bootp 212.44.88.1 212.44.88.63;
this range will overlap your cobbler server. I'm not certain if the
dhcp daemon is intelligent enough to avoid 212.44.88.10 or if it will
potentially offer it to a client. I would change this to '212.44.88.11
212.44.88.63'.
I would personally consider moving the cobbler server to IP address
212.44.88.1 and make the range '212.44.88.2 212.44.88.63'
> filename "/tftpboot/pxelinux.0";
> default-lease-time 21600;
> max-lease-time 43200;
> next-server 212.44.88.10;
the cobbler server is also running the tftp service.
> }
Regards
Dylan
13 years, 10 months
Re: Config help? .. Cobbler 1.2.9
by Dylan Swift
On 12 June 2010 22:46, Frank <support(a)server-1.com> wrote:
> Dear All:
>
> After two days pause ... here one more setup question:
I just got back on my laptop and was reading the thread from the last
2 days when this appeared!
> I edited
> /etc/dhcpd.conf
> the way you see below under (#1).
> But when I click onto "Sync" in Cobbler_Web, it gets reset to the
> default (I believe that's the default) -- see (#2). Why is this?
You probably have 'manage_dhcp: 1' in your cobbler settings file
/etc/cobbler/settings.
This parameter tells cobbler to rebuild the dhcpd.conf file using
/etc/cobbler/dhcp.template.
I would suggest that this is the best way to use dhcp with cobbler as
it allows all the PXE options you can set in the cobbler web interface
/ command line to be passed into the dhcp server correctly. If you
really want to manage /etc/dhcpd.conf yourself then set 'manage_dhcp:
0' in the /etc/cobbler/settings file, restart cobbler and then update
the dhcpd.conf file. Finally restart the dhcpd server.
> Thanks!
> Frank
Your welcome.
Dylan
13 years, 10 months
Re: Config help? .. Cobbler 1.2.9
by Frank
Hello Ron:
I much appreciate your efforts to help! Thank you.
You wrote:
>Are you planning on running a separate (private) network for your cobbler
>installs? or just going to use one subnet with DHCP offered from cobbler
>with TFTP?
Can't answer this question as I am not understanding what each option
means in practical terms.
I have (so far) four blocks of IPs, in different subnets ... all
servers in one rack only. Not sure what makes most sense for me. But
again, my objective/need is: (a) most important, *remotely*
re-installing Linux OS (mostly CentOS versions) to servers in my
rack, and (b) installing Linux OS on new servers that get added to
the rack.
The "dhcpd.conf" file is on my Fedora 8 VPS Cobbler server at:
/etc/dhcpd.conf
"pxelinux.0" is at:
/tftpboot/pxelinux.0
(and I see there is another one at:
/usr/lib/syslinux/pxelinux.0 )
The netmask in in this case actually "255.255.255.192".
With the below SAMPLE IP (fake IP) 212.44.88.10, if that would be my
Cobbler server IP, would then the below "dhcpd.conf" configured okay?
Specific questions:
"option domain-name-servers" --> Would I add all the IP rangers I
have? Separated with comma? For example:
212.44.88.1 212.44.88.63, 212.48.77.1 212.48.77.255;
"option domain-name-servers" --> Can this be an IP that works for all servers?
# ******************************************************************
# Cobbler managed dhcpd.conf file
# generated from cobbler dhcp.conf template (Thu Jun 10 14:30:41 2010)
# ******************************************************************
ddns-update-style interim;
allow booting;
allow bootp;
omapi-port 647;
ignore client-updates;
set vendorclass = option vendor-class-identifier;
subnet 212.44.88.10 netmask 255.255.255.192 {
option routers 212.44.88.10;
option subnet-mask 255.255.255.192;
option domain-name-servers 212.33.44.55;
option domain-name "newdomain123.net";
range dynamic-bootp 212.44.88.1 212.44.88.63;
filename "/tftpboot/pxelinux.0";
default-lease-time 21600;
max-lease-time 43200;
next-server 212.44.88.10;
}
# group for Cobbler DHCP tag: default
(...)
**************************
If the settings above are correct -- or after they are corrected,
what is the next step?
Hope all these questions do not bother you too much.
Best wishes,
Frank
13 years, 10 months
Re: Config help? .. Cobbler 1.2.9
by Frank
Hi Ronald!
Thanks for your response.
To clarify -- I was only saying that *I* do not know what the next
step is, not that there is a problem with the Cobbler install. I
simply do not know what to do now, after I did the import of CentOS
distributions .... I think the next step would be the same, whatever
distribution I would want to install on any server. Maybe it is so
obvious to you that you can't see why I have a problem at this point.
Thanks,
Frank
.........
cobbler check
The following potential problems were detected:
#0: One or more kickstart templates references default password
'cobbler' and should be changed for security reasons: /etc/cobbler
/sample.ks, /etc/cobbler/legacy.ks, /etc/cobbler/sample_end.ks
.........
# cobbler report
distro : CentOS48-32-bit-i386
breed : redhat
os version : rhel4
architecture : i386
initrd :
/var/www/cobbler/ks_mirror/CentOS48-32-bit/images/pxeboot/initrd.img
kernel :
/var/www/cobbler/ks_mirror/CentOS48-32-bit/images/pxeboot/vmlinuz
kernel options : {}
post kernel options : {}
ks metadata : {'tree':
'http://@@http_server@@/cblr/links/CentOS48-32-bit-i386'}
owners : ['admin']
distro : CentOS48-32-bit-xen-i386
breed : redhat
os version : rhel4
architecture : i386
initrd :
/var/www/cobbler/ks_mirror/CentOS48-32-bit/images/xen/initrd.img
kernel :
/var/www/cobbler/ks_mirror/CentOS48-32-bit/images/xen/vmlinuz
kernel options : {}
post kernel options : {}
ks metadata : {'tree':
'http://@@http_server@@/cblr/links/CentOS48-32-bit-xen-i386'}
owners : ['admin']
distro : CentOS48-64-bit-x86_64
breed : redhat
os version : rhel4
architecture : x86_64
initrd :
/var/www/cobbler/ks_mirror/CentOS48-64-bit/images/pxeboot/initrd.img
kernel :
/var/www/cobbler/ks_mirror/CentOS48-64-bit/images/pxeboot/vmlinuz
kernel options : {}
post kernel options : {}
ks metadata : {'tree':
'http://@@http_server@@/cblr/links/CentOS48-64-bit-x86_64'}
owners : ['admin']
distro : CentOS48-64-bit-xen-x86_64
breed : redhat
os version : rhel4
architecture : x86_64
initrd :
/var/www/cobbler/ks_mirror/CentOS48-64-bit/images/xen/initrd.img
kernel :
/var/www/cobbler/ks_mirror/CentOS48-64-bit/images/xen/vmlinuz
kernel options : {}
post kernel options : {}
ks metadata : {'tree':
'http://@@http_server@@/cblr/links/CentOS48-64-bit-xen-x86_64'}
owners : ['admin']
distro : CentOS54-32-bit-i386
breed : redhat
os version : rhel5
architecture : i386
initrd :
/var/www/cobbler/ks_mirror/CentOS54-32-bit/images/pxeboot/initrd.img
kernel :
/var/www/cobbler/ks_mirror/CentOS54-32-bit/images/pxeboot/vmlinuz
kernel options : {}
post kernel options : {}
ks metadata : {'tree':
'http://@@http_server@@/cblr/links/CentOS54-32-bit-i386'}
owners : ['admin']
distro : CentOS54-32-bit-xen-i386
breed : redhat
os version : rhel5
architecture : i386
initrd :
/var/www/cobbler/ks_mirror/CentOS54-32-bit/images/xen/initrd.img
kernel :
/var/www/cobbler/ks_mirror/CentOS54-32-bit/images/xen/vmlinuz
kernel options : {}
post kernel options : {}
ks metadata : {'tree':
'http://@@http_server@@/cblr/links/CentOS54-32-bit-xen-i386'}
owners : ['admin']
distro : CentOS54-64-bit-x86_64
breed : redhat
os version : rhel5
architecture : x86_64
initrd :
/var/www/cobbler/ks_mirror/CentOS54-64-bit/images/pxeboot/initrd.img
kernel :
/var/www/cobbler/ks_mirror/CentOS54-64-bit/images/pxeboot/vmlinuz
kernel options : {}
post kernel options : {}
ks metadata : {'tree':
'http://@@http_server@@/cblr/links/CentOS54-64-bit-x86_64'}
owners : ['admin']
distro : CentOS54-64-bit-xen-x86_64
breed : redhat
os version : rhel5
architecture : x86_64
initrd :
/var/www/cobbler/ks_mirror/CentOS54-64-bit/images/xen/initrd.img
kernel :
/var/www/cobbler/ks_mirror/CentOS54-64-bit/images/xen/vmlinuz
kernel options : {}
post kernel options : {}
ks metadata : {'tree':
'http://@@http_server@@/cblr/links/CentOS54-64-bit-xen-x86_64'}
owners : ['admin']
profile : CentOS48-32-bit-i386
distro : CentOS48-32-bit-i386
dhcp tag : default
kernel options : {}
post kernel options : {}
kickstart : /etc/cobbler/legacy.ks
ks metadata : {}
owners : ['admin']
repos : []
server : <<inherit>>
virt bridge : xenbr0
virt cpus : 1
virt file size : 5
virt path :
virt ram : 512
virt type : qemu
profile : CentOS48-32-bit-xen-i386
distro : CentOS48-32-bit-xen-i386
dhcp tag : default
kernel options : {}
post kernel options : {}
kickstart : /etc/cobbler/legacy.ks
ks metadata : {}
owners : ['admin']
repos : []
server : <<inherit>>
virt bridge : xenbr0
virt cpus : 1
virt file size : 5
virt path :
virt ram : 512
virt type : xenpv
profile : CentOS48-64-bit-x86_64
distro : CentOS48-64-bit-x86_64
dhcp tag : default
kernel options : {}
post kernel options : {}
kickstart : /etc/cobbler/legacy.ks
ks metadata : {}
owners : ['admin']
repos : []
server : <<inherit>>
virt bridge : xenbr0
virt cpus : 1
virt file size : 5
virt path :
virt ram : 512
virt type : qemu
profile : CentOS48-64-bit-xen-x86_64
distro : CentOS48-64-bit-xen-x86_64
dhcp tag : default
kernel options : {}
post kernel options : {}
kickstart : /etc/cobbler/legacy.ks
ks metadata : {}
owners : ['admin']
repos : []
server : <<inherit>>
virt bridge : xenbr0
virt cpus : 1
virt file size : 5
virt path :
virt ram : 512
virt type : xenpv
profile : CentOS54-32-bit-i386
distro : CentOS54-32-bit-i386
dhcp tag : default
kernel options : {}
post kernel options : {}
kickstart : /etc/cobbler/sample.ks
ks metadata : {}
owners : ['admin']
repos : []
server : <<inherit>>
virt bridge : xenbr0
virt cpus : 1
virt file size : 5
virt path :
virt ram : 512
virt type : qemu
profile : CentOS54-32-bit-xen-i386
distro : CentOS54-32-bit-xen-i386
dhcp tag : default
kernel options : {}
post kernel options : {}
kickstart : /etc/cobbler/sample.ks
ks metadata : {}
owners : ['admin']
repos : []
server : <<inherit>>
virt bridge : xenbr0
virt cpus : 1
virt file size : 5
virt path :
virt ram : 512
virt type : xenpv
profile : CentOS54-64-bit-x86_64
distro : CentOS54-64-bit-x86_64
dhcp tag : default
kernel options : {}
post kernel options : {}
kickstart : /etc/cobbler/sample.ks
ks metadata : {}
owners : ['admin']
repos : []
server : <<inherit>>
virt bridge : xenbr0
virt cpus : 1
virt file size : 5
virt path :
virt ram : 512
virt type : qemu
profile : CentOS54-64-bit-xen-x86_64
distro : CentOS54-64-bit-xen-x86_64
dhcp tag : default
kernel options : {}
post kernel options : {}
kickstart : /etc/cobbler/sample.ks
ks metadata : {}
owners : ['admin']
repos : []
server : <<inherit>>
virt bridge : xenbr0
virt cpus : 1
virt file size : 5
virt path :
virt ram : 512
virt type : xenpv
>Frank,
>
>Sounds like you might be missing the TFTP portion, you will need
>this for servers to PXE boot from and install Centos.
>Have not done anything with Centos, but we have an extensive Cobbler
>setup here that handles the PXE and VM (quem) installation of Fedora
>8 - Fedora 13.
>
>How did you import the Centos distros into cobbler? Also what does
>'cobbler check' and 'cobbler report' show?
>
>-Ron
--
--------------------------------------
RESELLER SHARKS
http://reseller-sharks.com
Support Request: http://reseller-sharks.com/supportrequest.html
Accounting: https://basicnetworks.net/accounts/
13 years, 11 months
Config help? .. Cobbler 1.2.9
by Frank
Dear All:
Is there anyone out there who can help me. I will be happy to pay for
your help.
What I have done so far:
- installed Fedora 8 as a Virtuozzo VPS server (because I do not want
to dedicated an entire physical server just for Cobbler, and could
not get a CentOS VPS to work with Cobbler, because of SWAP file
problem there ... so I use an older Fedora version)
- installed Cobbler 1.2.9, using "yum" method for install .. worked fine
- created/imported 4 different CentOS distributions (4.8 and 5.4, 32-
and 64-bit versions), which I would like to use to REMOTELY set up
others physical servers in the same rack, or to REMOTELY reinstall
CentOS on these servers, when needed ... these distributions show up
fine in the Web interface of Cobbler
But from here on I am really lost. I tried to understand what the
next step should be, but don't, and am not at all sure what to
configure and how.
Again, my objective is to use Cobber on this VPS (that is, the VPS is
only there as installer server) to set up new physical servers, and
to reinstall Linux distributions (mostly CentOS) when needed on other
servers in the same rack. I can reboot each server using a device
that interrupts the power supply.
You can reach me at: support AT server-1.com
Best,
Frank
13 years, 11 months
Docs on build_report_email.template???
by Jeremy Hansen
I'd like to use the reporting feature in cobbler. Is there any documentation for build_report_email.template? There's some information I would like to include that isn't present in the default template. I'm looking for information such as disk, mount info and link status info. How can I include this?
Thanks
-jeremy
13 years, 11 months
Setting the right boot nic
by Thomas S Hatch
I suppose I am missing something simple again... When I install a vm of
rhel 5 which has multimple nics with koan, the install holds and asks which
interface to dhcp preparatory to retrieving the kickstart file. How am I to
go about making it always use say, eth0?
-Tom Hatch
13 years, 11 months
Automatically start domus after installation
by Joerg.Hollmann@t-systems.com
Hi,
maybe somebody can help me. I'm installing 2 xenfv domu with Red Hat
Enterprise Linux 5.5 using following command line
koan --server=ip-cobbler-server --virt --system=sysname
Cobbler and Koan both have version 2.0.4. Everything works fine. The xen
instances boots over pxe and Red Hat Linux is installed succesfully but
after the installation the guest systems are not started. The status
field in virt-manager shows "Shutoff". Choosing "Run" in virt-manager
starts the machines. Is there a way to configure the automatically start
of the freshly installed xen instances?
Regards Joerg
13 years, 11 months