I can define static IP configured systems like this:
cobbler system add --name=vera --hostname=vera.domainname --profile='centos-53-i386-puppet' \ --static=true --gateway=1.2.1.254 --subnet=255.255.128.0 --ip=1,2.5.27 --mac=00:0C:F1:f1:f1:f1 \ --name-servers='1.2.0.20 1.2.0.10' --name-servers-search='domainname'
but that's a lot of typing :) anyway to inherit these (say from the profile)?
I know, this is what DHCP is for :) but I need the values hardcoded into the machines after they're built.
Tried setting 'default_name_servers' in cobbler/settings and it seemed to be a null-op; certainly had no effect on existing systems, even if I re-created their definitions.
Am I missing something? Thanks!
Dick Davies wrote:
I can define static IP configured systems like this:
cobbler system add --name=vera --hostname=vera.domainname --profile='centos-53-i386-puppet' \ --static=true --gateway=1.2.1.254 --subnet=255.255.128.0 --ip=1,2.5.27 --mac=00:0C:F1:f1:f1:f1 \ --name-servers='1.2.0.20 1.2.0.10' --name-servers-search='domainname'
but that's a lot of typing :) anyway to inherit these (say from the profile)?
I know, this is what DHCP is for :) but I need the values hardcoded into the machines after they're built.
Tried setting 'default_name_servers' in cobbler/settings and it seemed to be a null-op; certainly had no effect on existing systems, even if I re-created their definitions.
Am I missing something? Thanks! _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
You just asked this on IRC, so now I have to answer twice :)
Presently no. With the completion of network objects it will be possible to just say that an interface lives on a network, in which case, yes.
Default name servers works via the network snippets and is applied at install time, it is not something you should see in Cobbler Web, for instance.
--Michael
On Thu, May 21, 2009 at 8:12 AM, Dick Davies rasputnik@hellooperator.net wrote:
I can define static IP configured systems like this:
cobbler system add --name=vera --hostname=vera.domainname --profile='centos-53-i386-puppet' \ --static=true --gateway=1.2.1.254 --subnet=255.255.128.0 --ip=1,2.5.27 --mac=00:0C:F1:f1:f1:f1 \ --name-servers='1.2.0.20 1.2.0.10' --name-servers-search='domainname'
but that's a lot of typing :) anyway to inherit these (say from the profile)?
I know, this is what DHCP is for :) but I need the values hardcoded into the machines after they're built.
Tried setting 'default_name_servers' in cobbler/settings and it seemed to be a null-op; certainly had no effect on existing systems, even if I re-created their definitions.
Am I missing something? Thanks!
We have the same problem and get around it by putting the dns servers in /etc/cobbler/dhcp.template. You need to statically define the subnets via the normal isc dhcpd methods for each network. Anaconda (network-manager actually) will pick them up and write them out to resolve.conf during the intstall. Then everything works as expected. Its pretty simple once you wrap your head around it.
Ah, that explains it then; this is a 'manage_dhcp : 0' setup. Thanks!
On Thu, May 21, 2009 at 5:51 PM, Jeff Schroeder jeffschroed@gmail.com wrote:
On Thu, May 21, 2009 at 8:12 AM, Dick Davies rasputnik@hellooperator.net wrote:
I can define static IP configured systems like this:
cobbler system add --name=vera --hostname=vera.domainname --profile='centos-53-i386-puppet' \ --static=true --gateway=1.2.1.254 --subnet=255.255.128.0 --ip=1,2.5.27 --mac=00:0C:F1:f1:f1:f1 \ --name-servers='1.2.0.20 1.2.0.10' --name-servers-search='domainname'
but that's a lot of typing :) anyway to inherit these (say from the profile)?
I know, this is what DHCP is for :) but I need the values hardcoded into the machines after they're built.
Tried setting 'default_name_servers' in cobbler/settings and it seemed to be a null-op; certainly had no effect on existing systems, even if I re-created their definitions.
Am I missing something? Thanks!
We have the same problem and get around it by putting the dns servers in /etc/cobbler/dhcp.template. You need to statically define the subnets via the normal isc dhcpd methods for each network. Anaconda (network-manager actually) will pick them up and write them out to resolve.conf during the intstall. Then everything works as expected. Its pretty simple once you wrap your head around it.
-- Jeff Schroeder
Don't drink and derive, alcohol and analysis don't mix. http://www.digitalprognosis.com _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
Dick Davies wrote:
Ah, that explains it then; this is a 'manage_dhcp : 0' setup. Thanks!
It actually does not explain it.
The name_servers setting is applied by the snippets you will see in such files at /var/lib/cobbler/kickstarts/sample*.ks. If you have the network config settings there, they will be applied to your local system upon kickstart. The value in settings is used when this is /not/ specified, such that you do not have to enter it in for all systems. It is the /default/ value for this per-system setting.
If you are using your own kickstarts, they will not have this snippet by default and you'll have to go in and fix that.
Manage DHCP simply handles DHCP reservations. It has no bearing on this setting.
On Thu, May 21, 2009 at 5:51 PM, Jeff Schroeder jeffschroed@gmail.com wrote:
On Thu, May 21, 2009 at 8:12 AM, Dick Davies rasputnik@hellooperator.net wrote:
I can define static IP configured systems like this:
cobbler system add --name=vera --hostname=vera.domainname --profile='centos-53-i386-puppet' \ --static=true --gateway=1.2.1.254 --subnet=255.255.128.0 --ip=1,2.5.27 --mac=00:0C:F1:f1:f1:f1 \ --name-servers='1.2.0.20 1.2.0.10' --name-servers-search='domainname'
but that's a lot of typing :) anyway to inherit these (say from the profile)?
I know, this is what DHCP is for :) but I need the values hardcoded into the machines after they're built.
Tried setting 'default_name_servers' in cobbler/settings and it seemed to be a null-op; certainly had no effect on existing systems, even if I re-created their definitions.
Am I missing something? Thanks!
We have the same problem and get around it by putting the dns servers in /etc/cobbler/dhcp.template. You need to statically define the subnets via the normal isc dhcpd methods for each network. Anaconda (network-manager actually) will pick them up and write them out to resolve.conf during the intstall. Then everything works as expected. Its pretty simple once you wrap your head around it.
-- Jeff Schroeder
Don't drink and derive, alcohol and analysis don't mix. http://www.digitalprognosis.com _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
On Fri, May 22, 2009 at 2:27 PM, Michael DeHaan mdehaan@redhat.com wrote:
Dick Davies wrote:
Ah, that explains it then; this is a 'manage_dhcp : 0' setup. Thanks!
It actually does not explain it.
The name_servers setting is applied by the snippets you will see in such files at /var/lib/cobbler/kickstarts/sample*.ks. If you have the network config settings there, they will be applied to your local system upon kickstart. The value in settings is used when this is /not/ specified, such that you do not have to enter it in for all systems. It is the /default/ value for this per-system setting.
If you are using your own kickstarts, they will not have this snippet by default and you'll have to go in and fix that.
no, I'm using a copied sample.ks (with a few tweaks to add puppet in).
Can you give me a 'cobbler system add' command you'd expect to add this in? I'm presuming I'd need at least --static=1 in there somewhere.
Thanks again.
(incidentally, the manpage implies --static doesn't need any arguments, in my experience that's not true. Where can I file bugs/send patches? )
Dick Davies wrote:
On Fri, May 22, 2009 at 2:27 PM, Michael DeHaan mdehaan@redhat.com wrote:
Dick Davies wrote:
Ah, that explains it then; this is a 'manage_dhcp : 0' setup. Thanks!
It actually does not explain it.
The name_servers setting is applied by the snippets you will see in such files at /var/lib/cobbler/kickstarts/sample*.ks. If you have the network config settings there, they will be applied to your local system upon kickstart. The value in settings is used when this is /not/ specified, such that you do not have to enter it in for all systems. It is the /default/ value for this per-system setting.
If you are using your own kickstarts, they will not have this snippet by default and you'll have to go in and fix that.
no, I'm using a copied sample.ks (with a few tweaks to add puppet in).
Can you give me a 'cobbler system add' command you'd expect to add this in? I'm presuming I'd need at least --static=1 in there somewhere.
cobbler system add --name=foo --mac=AA:BB:CC:DD:EE:FF --static=1 --ip=<ip> --gateway=<gateway> --name-servers="<ip1> <ip2>" [etc]
Thanks again.
(incidentally, the manpage implies --static doesn't need any arguments, in my experience that's not true. Where can I file bugs/send patches? )
Correct. There'd be no nice way to unstatic it if there wasn't an argument.
Patches to the manpage (cobbler.pod) file can go to cobbler-devel@lists.fedorahosted.org
Bugs go to fedorahosted.org/cobbler
cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
cobbler@lists.fedorahosted.org