FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora/Linux Management Tools

 
 
LinkBack Thread Tools
 
Old 07-01-2008, 11:49 AM
Tom Brown
 
Default cobbler-1.0.1-2 - build problem using koan

OK. Something is definitely missing here. Notice how
(http://www.redhat.com/magazine/024oct06/features/kickstart/) GRUB
contains options for setting the IP address, netmask, and gateway for
the system you intend to boot. These arguments are /*not*/ set in
/your/ grub configuration. As to why they are not, either you didn't
specify them during your cobbler system provisioning OR there is some
kind of a bug in koan's 'reprovision' logic. Likely the former.
Please double check that you specified


cobbler .... --ip=X --subnet=Y --gateway=Z ...

in your provision command.



# cobbler system report --name=xxxxxx
system : xxxxxx
profile : RHEL4-u5-i386-prd
kernel options : {}
kickstart : <<inherit>>
ks metadata : {'nameserver': '10.xxx.xxx.117'}
netboot enabled? : True
owners : ['admin']
server : <<inherit>>
virt cpus : <<inherit>>
virt file size : <<inherit>>
virt path : <<inherit>>
virt ram : <<inherit>>
virt type : <<inherit>>
interface : intf0
mac address : 00:13:72:69:95:7E
ip address : 10.xxx.xxx.19
hostname : xxxxxx
gateway : 10.xxx.xxx.253
subnet : 255.255.254.0
virt bridge :
dhcp tag :

that seems fine to me?

and the koan version on the client

# rpm -qa | grep koan
koan-1.0.0-1.el4

thanks for any further info


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 11:51 AM
Adam Rosenwald
 
Default cobbler-1.0.1-2 - build problem using koan

Tom Brown wrote:


Please explain how your home brew system talks to booting systems.
When your provisioned systems boot, how do they communicate with the
server hosting the kickstart files?
As I understand it, at network boot time, they need to have IP
addresses, netmasks assigned to them. PXE starts by the NIC(s)
broadcasting its MAC address. Some daemon on the LAN segment
(typically dhcp) will respond to the broadcast by assigning the NIC
an IP address and subnet mask.


Unless you have an ability to assign IPs/netmasks to NICs through
BIOS (which I've never seen and which would be a pain to do for a
'lot' of servers) or have some other mechanism (i.e. other than DHCP)
which assigns IPs/netmasks by responding to MAC broadcasts, you will
have to use DHCP somewhere during a network install.




i will try and explain as best i can as i did not write the system -
but basically what i believes happens is that a minimal boot kernel
boots that is generated on the client machines before a reboot is
issued. Within this boot kernel is the network info that allows the
box to have network info before it then downloads its kickstart file
etc. This is how i thought koan worked as i can rebuild machines using
a different cobbler server and in a different network that the cobbler
server knows nothing about, i mean it knows nothing about these other
networks from a DHCP point of view.


I can of course see why my goal will not work on a bare metal system
but i thought that on a system that has a running OS koan could be
used to rebuild it to the profile as per assigned by the cobbler
server. When rebuilds occur using koan i did not think DHCP or PXE
came into it.


thanks
I understand now. I haven't used GRUB before to pass anaconda options
when attempting to perform network installs. Clearly we both now
understand the problem and solution.


-A.


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools



_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 11:54 AM
Tom Brown
 
Default cobbler-1.0.1-2 - build problem using koan

I understand now. I haven't used GRUB before to pass anaconda options
when attempting to perform network installs. Clearly we both now
understand the problem and solution.




also

http://www.nabble.com/koan-1.0.0-is-ignoring-kernel-options-td17702492.html

/ME investigating

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 12:04 PM
Adam Rosenwald
 
Default cobbler-1.0.1-2 - build problem using koan

Tom Brown wrote:


OK.* Something is definitely missing here.*
Notice how
(http://www.redhat.com/magazine/024oct06/features/kickstart/) GRUB
contains options for setting the IP address, netmask, and gateway for
the system you intend to boot.* These arguments are /*not*/ set in
/your/ grub configuration.* As to why they are not, either you didn't
specify them during your cobbler system provisioning OR there is some
kind of a bug in koan's 'reprovision' logic.* Likely the former.*
Please double check that you specified




cobbler .... --ip=X --subnet=Y --gateway=Z ...




in your provision command.







# cobbler system report --name=xxxxxx


system********** : xxxxxx


profile********* : RHEL4-u5-i386-prd


kernel options** : {}


kickstart******* : <<inherit>>


ks metadata***** : {'nameserver': '10.xxx.xxx.117'}


netboot enabled? : True


owners********** : ['admin']


server********** : <<inherit>>


virt cpus******* : <<inherit>>


virt file size** : <<inherit>>


virt path******* : <<inherit>>


virt ram******** : <<inherit>>


virt type******* : <<inherit>>


interface******* : intf0


*mac address*** : 00:13:72:69:95:7E


*ip address**** : 10.xxx.xxx.19


*hostname****** : xxxxxx


*gateway******* : 10.xxx.xxx.253


*subnet******** : 255.255.254.0


*virt bridge*** :


*dhcp tag****** :




that seems fine to me?




and the koan version on the client




# rpm -qa | grep koan


koan-1.0.0-1.el4




thanks for any further info



OK... good.* If you could try to do so, please reprovision your system
with the following amendment:


cobbler ... --kopts='ip=10.xxx.xxx.19 netmask=255.255.254.0
gateway=10.xxx.xxx.253 dns=10.xxx.xxx.117' ...

Resync and see if the new grub file installed after koaning looks the
part.



-A.





_______________________________________________


et-mgmt-tools mailing list


et-mgmt-tools@redhat.com


https://www.redhat.com/mailman/listinfo/et-mgmt-tools









_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 12:17 PM
Adam Rosenwald
 
Default cobbler-1.0.1-2 - build problem using koan

Adam Rosenwald wrote:



Tom Brown wrote:


OK.* Something is definitely missing here.*
Notice how
(http://www.redhat.com/magazine/024oct06/features/kickstart/)
GRUB
contains options for setting the IP address, netmask, and gateway for
the system you intend to boot.* These arguments are /*not*/ set in
/your/ grub configuration.* As to why they are not, either you didn't
specify them during your cobbler system provisioning OR there is some
kind of a bug in koan's 'reprovision' logic.* Likely the former.*
Please double check that you specified



cobbler .... --ip=X --subnet=Y --gateway=Z ...



in your provision command.






# cobbler system report --name=xxxxxx

system********** : xxxxxx

profile********* : RHEL4-u5-i386-prd

kernel options** : {}

kickstart******* : <<inherit>>

ks metadata***** : {'nameserver': '10.xxx.xxx.117'}

netboot enabled? : True

owners********** : ['admin']

server********** : <<inherit>>

virt cpus******* : <<inherit>>

virt file size** : <<inherit>>

virt path******* : <<inherit>>

virt ram******** : <<inherit>>

virt type******* : <<inherit>>

interface******* : intf0

*mac address*** : 00:13:72:69:95:7E

*ip address**** : 10.xxx.xxx.19

*hostname****** : xxxxxx

*gateway******* : 10.xxx.xxx.253

*subnet******** : 255.255.254.0

*virt bridge*** :

*dhcp tag****** :



that seems fine to me?



and the koan version on the client



# rpm -qa | grep koan

koan-1.0.0-1.el4



thanks for any further info


OK... good.* If you could try to do so, please reprovision your system
with the following amendment:


cobbler ... --kopts='ip=10.xxx.xxx.19 netmask=255.255.254.0
gateway=10.xxx.xxx.253 dns=10.xxx.xxx.117' ...

Resync and see if the new grub file installed after koaning looks the
part.



-A.


Sorry.* You could have also overridden the kernel options in koan
itself:


koan ... --kopts='ip=10.xxx.xxx.19 netmask=255.255.254.0
gateway=10.xxx.xxx.253 dns=10.xxx.xxx.117'

Basically koan doesn't make use of the cobbler's own --ip, --gateway,
--subnet variables when interfacing with grubby to create the grub
config file; rather it only makes use of --kopts.* This is
rather nonintuitive, and it's difficult for me to think of a situation
where one is attempting to reprovision (via koan --replace-self) a
system, yet not want import those cobbler dictionary values (ip,
subnet, etc.) into grub kernel arguments.



Then, there is the problem of precedence: do --ip, --subnet, etc.
override --kopts='ip=... netmask=...' if both are declared?* Or vice
versa?* This is a policy decision which Michael shouldn't have to worry
about enforcing.* Rather, it may be more relevant to update the cobbler
wiki under 'koan replace-self procedure'.



-A.






_______________________________________________

et-mgmt-tools mailing list

et-mgmt-tools@redhat.com

https://www.redhat.com/mailman/listinfo/et-mgmt-tools












_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 12:49 PM
Tom Brown
 
Default cobbler-1.0.1-2 - build problem using koan

Sorry. You could have also overridden the kernel options in koan itself:

* koan ... --kopts='ip=10.xxx.xxx.19 netmask=255.255.254.0
gateway=10.xxx.xxx.253 dns=10.xxx.xxx.117'

Basically koan doesn't make use of the cobbler's own --ip, --gateway,
--subnet variables when interfacing with grubby to create the grub
config file; rather it /only/ makes use of --kopts. This is rather
nonintuitive, and it's difficult for me to think of a situation where
one is attempting to reprovision (via koan --replace-self) a system,
yet not want import those cobbler dictionary values (ip, subnet, etc.)
into grub kernel arguments.


Then, there is the problem of precedence: do --ip, --subnet, etc.
override --kopts='ip=... netmask=...' if both are declared? Or vice
versa? This is a policy decision which Michael shouldn't have to
worry about enforcing. Rather, it may be more relevant to update the
cobbler wiki under 'koan replace-self procedure'.





OK to confirm in my own mind

You need to add network info to both the cobbler variables and also
ksmeta variables at system configuration time in order to get the
replace-self to work correctly?


thanks


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 01:04 PM
Adam Rosenwald
 
Default cobbler-1.0.1-2 - build problem using koan

Tom Brown wrote:


Sorry.* You could have also overridden the
kernel options in koan itself:




*** * koan ... --kopts='ip=10.xxx.xxx.19 netmask=255.255.254.0


***** gateway=10.xxx.xxx.253 dns=10.xxx.xxx.117'




Basically koan doesn't make use of the cobbler's own --ip, --gateway,
--subnet variables when interfacing with grubby to create the grub
config file; rather it /only/ makes use of --kopts.* This is rather
nonintuitive, and it's difficult for me to think of a situation where
one is attempting to reprovision (via koan --replace-self) a system,
yet not want import those cobbler dictionary values (ip, subnet, etc.)
into grub kernel arguments.




Then, there is the problem of precedence: do --ip, --subnet, etc.
override --kopts='ip=... netmask=...' if both are declared?* Or vice
versa?* This is a policy decision which Michael shouldn't have to worry
about enforcing.* Rather, it may be more relevant to update the cobbler
wiki under 'koan replace-self procedure'.









OK to confirm in my own mind




You need to add network info to both the cobbler variables and also
ksmeta variables at system configuration time in order to get the
replace-self to work correctly?



No.* You need to do specify the kopts variables on either the cobbler
end or the koan end.


cobbler ... --kopts='<kernel args>'



or


koan ... --kopts='<kernel args>'

FYI,



-A.



thanks






_______________________________________________


et-mgmt-tools mailing list


et-mgmt-tools@redhat.com


https://www.redhat.com/mailman/listinfo/et-mgmt-tools









_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 01:12 PM
Tom Brown
 
Default cobbler-1.0.1-2 - build problem using koan

No. You need to do specify the kopts variables on either the cobbler
end or the koan end.


* cobbler ... --kopts='<kernel args>'

or

* koan ... --kopts='<kernel args>'

FYI,



yes - i wrote ksmeta but meant kopts - my bad there, now i have more of
a scripting question


To add a system i have a script that i pass some args to and it looks
like this


cobbler system add --name=$1 --mac=$2 --hostname=$1 --ip=$3 --subnet=$4
--gateway=$5 --ksmeta="nameserver=10.xxx.xxx.117" --profile=$6


works fine and by 'scraping' that info from machines currently running i
can automate the process of adding systems.


A typical use of this script i call 'buildbox' would be

buildbox xxxxxx 00:13:72:69:95:7E 10.xxx.xxx.19 255.255.254.0
10.xxx.xxx.253 RHEL4-u5-i386-prd


This works like a charm and adds machines - however when i add the
following...


cobbler system add --name=$1 --mac=$2 --hostname=$1 --ip=$3 --subnet=$4
--gateway=$5 --ksmeta="nameserver=10.168.86.117" --profile=$6
--kopts='ip=$3 netmask=$4 gateway=$5 dns=10.xxx.xxx.117'


the 'ksopts' bits just end up as $3, $4 etc and not their actual value -

Can anyone offer me a hint here

thanks


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 01:17 PM
Adam Rosenwald
 
Default cobbler-1.0.1-2 - build problem using koan

Try double quotes instead of single quotes.

Tom Brown wrote:


No. You need to do specify the kopts variables on either the cobbler
end or the koan end.


* cobbler ... --kopts='<kernel args>'

or

* koan ... --kopts='<kernel args>'

FYI,



yes - i wrote ksmeta but meant kopts - my bad there, now i have more
of a scripting question


To add a system i have a script that i pass some args to and it looks
like this


cobbler system add --name=$1 --mac=$2 --hostname=$1 --ip=$3
--subnet=$4 --gateway=$5 --ksmeta="nameserver=10.xxx.xxx.117"
--profile=$6


works fine and by 'scraping' that info from machines currently running
i can automate the process of adding systems.


A typical use of this script i call 'buildbox' would be

buildbox xxxxxx 00:13:72:69:95:7E 10.xxx.xxx.19 255.255.254.0
10.xxx.xxx.253 RHEL4-u5-i386-prd


This works like a charm and adds machines - however when i add the
following...


cobbler system add --name=$1 --mac=$2 --hostname=$1 --ip=$3
--subnet=$4 --gateway=$5 --ksmeta="nameserver=10.168.86.117"
--profile=$6 --kopts='ip=$3 netmask=$4 gateway=$5 dns=10.xxx.xxx.117'


the 'ksopts' bits just end up as $3, $4 etc and not their actual value -

Can anyone offer me a hint here

thanks


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools



_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 01:28 PM
Tom Brown
 
Default cobbler-1.0.1-2 - build problem using koan

Try double quotes instead of single quotes.



looks like we have a winner! thanks - also my boxes are now rebuilding
using koan and no DHCP ir PXE in sight


personally a feature request for koan would be to inherit these values
but adding them on the end of my script also works it just seems a bit
excessive.


thanks


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 

Thread Tools




All times are GMT. The time now is 07:13 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org