Hiya, I'm kind of new to cobbler, so apologies if any of what I'm going to ask is dumb. Questions:
1. Are the manual pages that get loaded the definitive reference for the available cobbler commands?
2. The configuration I'm having to use (VirtualBox running Centos 5.5 cobbler server and VB-hosted "clients") is currently using client servers with eth0 assigned for "management" purposes and eth1 for "system". Now I can easily setup eth1 IP addresses, nameservers etc easily with the Web interface (which is really quite good) but I've want to automate the VB machine generation and cobbler setup - so I need to be able to generate my eth1 configuration from the command line. Are there any decent references on how to do this? (the alternative is for me to try and reverse-engineer the web interface, but I'd prefer not to have to do this). From what I've seen it kind of looks like I need to do a "cobbler system add ..." to setup the basic system and then use "cobbler system edit ..." to add in all the extras that I want.
3. Anyone know why the Debian configuration has been disabled? Presumably this is a work-in-progress? ;)
Thanks, Bob.
On Wed, 19 Jan 2011 11:53:39 +0000, Robert Cross r_l_cross@dechro.co.uk wrote:
Hiya, I'm kind of new to cobbler, so apologies if any of what I'm going to ask is dumb. Questions:
- Are the manual pages that get loaded the definitive reference for the
available cobbler commands?
We try to keep it as up to date as possible. It should be pretty definitive. Let us know if you find things that are not there though.
- The configuration I'm having to use (VirtualBox running Centos 5.5
cobbler server and VB-hosted "clients") is currently using client servers with eth0 assigned for "management" purposes and eth1 for "system". Now I can easily setup eth1 IP addresses, nameservers etc easily with the Web interface (which is really quite good) but I've want to automate the VB machine generation and cobbler setup - so I need to be able to generate my eth1 configuration from the command line. Are there any decent references on how to do this? (the alternative is for me to try and reverse-engineer the web interface, but I'd prefer not to have to do this). From what I've seen it kind of looks like I need to do a "cobbler system add ..." to setup the basic system and then use "cobbler system edit ..." to add in all the extras that I want.
To add additional interfaces you just specify them on the command line with the '--interface' flag. When you add a new system and specify interface properties without specifying an interface, it is assumed you mean eth0. So whatever ip address you specified on 'system add' will be for eth0. To add information for eth1, you would so something like the following.
# cobbler system edit --name foo --interface eth1 --ip 192.168.1.2 --subnet 255.255.255.0
This should give you a second interface, eth1, with the appropriate properties set. The default networking snippets handle this quite well and will lay down the configurations properly.
- Anyone know why the Debian configuration has been disabled?
Presumably this is a work-in-progress? ;)
When we released cobbler 2.0, there was a significant amount of change in the code that imports distributions. Unfortunately, there was no one around to test Debian or Ubuntu for this at the time. So, the import support was removed. You can still boot Debian, but you must add the distro manually and figure out a lot of things to get it right. However, we now have Debian and Ubuntu support in the master branch of git, so it should be making a return soonish.
cobbler@lists.fedorahosted.org