xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-06-13 01:40:26 +00:00
Code Issues Releases Wiki Activity

polish based on comments

Browse Source
This commit is contained in:
bybai
2016-01-26 03:43:11 -05:00
parent e9ca72dc5f
commit 65971caaa4
1 changed files with 42 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

67
docs/source/guides/admin-guides/manage_clusters/common/deployment/cfg_network.rst
View File

@ -5,31 +5,43 @@ The ``nics`` table and the ``confignetwork`` script can be used to automatically
To use ``confignetwork``, ``nicips``, ``nictypes``, ``nicnetworks`` and ``nicdevice`` attributes in ``nics`` table should be configured.
``nicdevice`` resolves relationships among physical_nics/BOND/VLAN/BRIDGE.
``nicdevices`` resolves relationships among physical_nics, BOND, VLAN, BRIDGE.
To use the nics table and confignetwork postscript to configure VLAN/BOND/BRIDGE on one or more nodes, here gives an example:
Following example will be used in the whole doc to describe how to use confignetwork postscript.
a. Physical nics are eth2 and eth3
b. Bonding eth2 and eth3 as bond0
c. From bond0, make 2 vlans: bond0.1 and bond0.2
d. Making bridge br1 using bond0.1, making bridge br2 using bond0.2, br1 ip is 10.0.0.1, br2 ip is 20.0.0.1
You should execute these steps:
Define configuration information for the BOND/VLAN/BRIDGE Adapters in the nics table
-------------------------------------------------------------------------------------
Define nic attributes in the nics table
----------------------------------------
There are 3 ways to complete this operation.
#. Using the ``mkdef`` or ``chdef`` commands
a. add nicdevice to define nics relationship ::
a. add nicdevices to define nics relationship ::
chdef cn1 nicdevice.br1=bond0.1 nicdevice.br2=bond0.2 nicdevice.bond0.1=bond0 nicdevice.bond0.2=bond0 nicdevice.bond0="eth2|eth3"
chdef cn1 nicdevices.br1=bond0.1 \
nicdevices.br2=bond0.2 \
nicdevices.bond0.1=bond0 \
nicdevices.bond0.2=bond0 \
nicdevices.bond0="eth2|eth3"
b. add nictypes and nicnetworks ::
chdef cn1 nictypes.eth2=ethernet nictypes.eth3=ethernet nictypes.bond0=bond nictypes.bond0.1=vlan nictypes.bond0.2=vlan nictypes.br1=bridge nictypes.br2=bridge nicips.br1=10.0.0.1 nicips.br2=20.0.0.1 nicnetworks.br1="net10" nicnetworks.br2="net20"
chdef cn1 nictypes.eth2=ethernet \
nictypes.eth3=ethernet \
nictypes.bond0=bond \
nictypes.bond0.1=vlan \
nictypes.bond0.2=vlan \
nictypes.br1=bridge \
nictypes.br2=bridge \
nicips.br1=10.0.0.1 \
nicips.br2=20.0.0.1 \
nicnetworks.br1="net10" \
nicnetworks.br2="net20"
#. Using an xCAT stanza file
@ -40,11 +52,11 @@ There are 3 ways to complete this operation.
objtype=node
arch=x86_64
groups=kvm,vm,all
nicdevice.br1=bond0.1
nicdevice.br2=bond0.2
nicdevice.bond0.1=bond0
nicdevice.bond0.2=bond0
nicdevice.bond0=eth2|eth3
nicdevices.br1=bond0.1
nicdevices.br2=bond0.2
nicdevices.bond0.1=bond0
nicdevices.bond0.2=bond0
nicdevices.bond0=eth2|eth3
nictypes.eth2=ethernet
nictypes.eth3=ethernet
nictypes.bond0=bond
@ -63,16 +75,27 @@ There are 3 ways to complete this operation.
#. Using ``tabedit`` to edit the ``nics`` database table directly
The ``tabedit`` command opens the specified xCAT database table in a vi like editor and allows the user to edit any text and write the changes back to the database table.
The ``tabedit`` command opens the specified xCAT database table in a ``vi`` like editor and allows the user to edit any text and write the changes back to the database table.
*WARNING* Using the ``tabedit`` command is not the recommended method because it is tedious and error prone.
After changing the content of the ``nics`` table, here is the result from ``tabdump nics`` ::
# tabdump nics
#node,nicips,nichostnamesuffixes,nichostnameprefixes,nictypes,niccustomscripts,nicnetworks,nicaliases,nicextraparams,nicdevice,comments,disable
#node,nicips,nichostnamesuffixes,nichostnameprefixes,nictypes,niccustomscripts,nicnetworks,nicaliases,nicextraparams,nicdevices,comments,disable
"cn1","br1!10.0.0.1,br2!20.0.0.1",,,"br1!bridge,eth2!ethernet,eth3!ethernet,bond0.2!vlan,bond0!bond,br2!bridge,bond0.1!vlan",,"br1!net10,br2!net20",,,"br1!bond0.1,bond0!eth2|eth3,bond0.2!bond0,bond0.1!bond0,br2!bond0.2",,
Add network object into the networks table
------------------------------------------
The ``nicnetworks`` attribute only defines the nic that uses the IP address.
Other information about the network should be defined in the ``networks`` table.
Use the ``chdef`` command to add/modify the networks in the ``networks`` table ::
chdef -t network net10 net=10.0.0.0 mask=255.0.0.0 mgtifname=eth0
chdef -t network net20 net=20.0.0.0 mask=255.0.0.0 mgtifname=eth1
Add confignetwork into the node's postscripts list
-----------------------------------------------
@ -80,17 +103,11 @@ Using below command to add confignetwork into the node's postscripts list ::
chdef cn1 -p postscripts=confignetwork
Add network object into the networks table
------------------------------------------
The ``nicnetworks`` attribute only defines the nic that uses the IP address.
Other information about the network should be defined in the ``networks`` table.
During OS deployment on compute node, confignetwork will be run in postscript.
If the compute node has OS, use ``updatenode`` command to run ``confignetwork`` ::
Use the ``tabedit`` command to add/modify the networks in the ``networks`` table ::
#netname,net,mask,mgtifname,gateway,dhcpserver,tftpserver,nameservers,ntpservers,logservers,dynamicrange,staticrange,staticrangeincrement,nodehostname,ddnsdomain,vlanid,domain,comments,disable
"net10","10.0.0.0","255.0.0.0","eth0",,,,,,,,,,,,,,,
"net20","20.0.0.0","255.0.0.0","eth1",,,,,,,,,,,,,,,
updatenode <cn> -P confignetwork