From 8ffb261c99f38eb88c8fa34d7c4a707e68be5ef9 Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Mon, 19 Nov 2007 15:55:17 -0500 Subject: All cobbler objects are now stubbed in as CLI modules, still needs testing. Next step is to add the CLI functions that are not object-manipulation based. These will be much shorter. --- docs/cobbler.pod | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) (limited to 'docs/cobbler.pod') diff --git a/docs/cobbler.pod b/docs/cobbler.pod index d99fdab..787e539 100644 --- a/docs/cobbler.pod +++ b/docs/cobbler.pod @@ -209,8 +209,6 @@ Specifying a mac address via --mac allows the system object to boot via PXE. If MAC addresses have the format AA:BB:CC:DD:EE:FF. -If you would like to specify additional interfaces, use --mac0=x, --mac1=y and so on. Interfaces 0 through 7 are supported. - =item ip If cobbler is configured to generate a DHCP configuratition (see advanced section), use this @@ -220,8 +218,6 @@ Example: ---ip=192.168.1.50 Note for Itanium users: this setting is always required for IA64 regardless of whether DHCP management is enabled. -If you would like to specify additional IPs, use --ip0=x, --ip1=y and so on. - If DHCP management is disabled, setting this parameter may still be useful for record keeping, and it is also available in all kickstart templates, so it can be easily used for static IP configuration within kickstarts. =item hostname @@ -230,8 +226,6 @@ If using the DHCP configuration feature (see advanced section) with dnsmasq, use Example: --hostname=mycomputer.example.com -If you would like to specify additional hostnames, use --hostname0=x, --hostname1=y and so on. - =item --gateway and --subnet If you are using static IP configurations, you may find it useful to store gateway and subnet @@ -239,9 +233,6 @@ information inside of cobbler. These variables are not used internally by cobbl made available in cobbler templates, which are described later in this document and on the Wiki. For DHCP configurations, these parameters should be left blank. -To describe gateway and subnet information for multiple intefaces, use --gateway0=x, --gateway1=y -and so on. Subnets work the same way. - =item --virt-bridge (Virt-only) While --virt-bridge is present in the profile object (see above), here it works on an interface by interface basis. For instance it would be possible to have --virt-bridge0=xenbr0 and --virt-bridge1=xenbr1. If not specified in cobbler for each interface, koan will use the value as specified in the profile for each interface, which may not always be what is intended, but will be sufficient in most cases. @@ -261,10 +252,21 @@ If you are setting up a PXE environment with multiple subnets/gateways, and are By default, the dhcp tag for all systems is "default" and means that in the DHCP template files the systems will expand out where $insert_cobbler_systems_definitions is found in the DHCP template. However, you may want certain systems to expand out in other places in the file. Setting --dhcp-tag=subnet2 for instance, will cause that system to expand out where $insert_cobbler_system_definitions_subnet2 is found, allowing you to insert directives to specify different subnets (or other parameters) before the DHCP configuration entries for those particular systems. -If your system has multiple network interfaces, use --dhcp-tag0=x, --dhcp-tag1=y and so on. - This is described further on the Cobbler Wiki. +=item --interface + +By default flags like --ip, --mac, --dhcp-tag, --gateway, --subnet, and --virt-bridge operation on the first network +interface defined for a system. Additional interfaces can be specified (0 through 7) for use with the edit command. + +Example: + +cobbler system edit --name=foo --ip=192.168.1.50 --mac=AA:BB:CC:DD:EE:A0 +cobbler system edit --name=foo --interface=2 --ip=192.168.1.51 --mac=AA:BB:CC:DD:EE:A1 +cobbler system report foo + +NOTE: Additional interfaces can presently only be deleted via the web interface. + =end =head2 ADDING A REPOSITORY TO MIRROR -- cgit