In process of making NICs seperate data structures in cobbler, which requires seperate accessors

and templating.  This is all to allow multiple NICs in koan.  Stil needs changes in sync
code and possibly other places.

1 files changed, 18 insertions, 0 deletions

diff --git a/docs/cobbler.pod b/docs/cobbler.pod
index 8326987..0962278 100644
--- a/docs/cobbler.pod
+++ b/docs/cobbler.pod
@@ -204,6 +204,8 @@ already looks like a mac address, this is inferred from the system name and does
 
 MAC addresses have the format AA:BB:CC:DD:EE:FF.
 
+If you would like to specify additional MACs, use --mac0=x, --mac1=y and so on.
+
 =item ip
 
 If cobbler is configured to generate a DHCP configuratition (see advanced section), use this
@@ -214,6 +216,8 @@ 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.
+
 =item hostname
 
 If using the DHCP configuration feature (see advanced section) with dnsmasq, use this to define a hostname for the system to
@@ -222,6 +226,18 @@ basically ignored.
 
 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
+information inside of cobbler.  These variables are not used internally by cobbler, but are
+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 --kickstart
 
 (optional) While it is recommended that the --kickstart parameter is only used within for the "profile add" command, there are scenarios when an install base switching to cobbler may have kickstarts created on a per-system basis (one kickstart for each system, nothing shared) and may not want to immediately make use of the cobbler templating system.  This allows specifing a kickstart for use on a per-system basis.  Creation of a parent profile is still required.  If the kickstart is a filesystem location, it will still be treated as a cobbler template.
@@ -237,6 +253,8 @@ 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.
+
 =end
 
 =head2 ADDING A REPOSITORY TO MIRROR