Skip to content

The mini design of confignetwork support NetworkManager

Yuan Bai edited this page Mar 6, 2019 · 25 revisions

confignetwork framework refine

  1. Make hash for nicdevice, nictypes, nicips, nicnetwork, niccustomscripts
  2. Sort nics device pair based on nicdevice type
  3. If there is invalid nics pair, errorcode is 1
  4. Delete invalid nics device pair based on Error
  5. Check NetworkManager service status, use "networkmanager_active" as global variable,
    1. "networkmanager_active=0" means "using network.service"
    2. "networkmanager_active=1" means "using NetworkManager".
  6. Configure nics framework, the inputs are orderd nic and its device
    For each nic and its device pair:
    1. If install nic is configured, skip to reconfigure it
    2. If there is customscript, then processing custom scripts for nics
    3. For current nic, get its base nic and base nic type
    4. If current nic type is BMC, ignore bmc interfaces
    5. If current nic type is ethernet, configure standalone ethernet nic
    6. If current nic type is bridge:
      1. If brctl works well:
        1. If networkmanager_active=1: create_bridge_interface_nmcli ifname=$nic_dev _brtype=$nic_dev_type _port=$base_nic_dev _pretype=$base_nic_type
        2. If networkmanager_active=0: create_bridge_interface ifname=$nic_dev _brtype=$nic_dev_type _port=$base_nic_dev _pretype=$base_nic_type
    7. If current nic type is VLAN:
      1. Get vlanname and vlanid
      2. If networkmanager_active=1: create_vlan_interface_nmcli ifname=$vlanname vlanid=$vlanid
      3. If networkmanager_active=0: create_vlan_interface ifname=$vlanname vlanid=$vlanid
    8. If current nic type is BOND:
      1. If networkmanager_active=1: create_bond_interface ifname=$nic_dev slave_ports=$base_nic_for_bond slave_type=$base_nic_type
      2. If networkmanager_active=0: create_bond_interface ifname=$nic_dev slave_ports=$base_nic_for_bond slave_type=$base_nic_type
    9. If current nic type is infiniband Or Omnipath, use "configib" to configure IB nics

create BOND interface

  1. create_bond_interface is original interface
  2. create_bond_interface_nmcli is for NetworkManager

create VLAN interface

  1. create_vlan_interface is original interface
  2. create_vlan_interface_nmcli is for NetworkManager

create Bridge interface

  1. create_bridge_interface is original interface
  2. create_bridge_interface_nmcli is for NetworkManager

News

History

  • Oct 22, 2010: xCAT 2.5 released.
  • Apr 30, 2010: xCAT 2.4 is released.
  • Oct 31, 2009: xCAT 2.3 released. xCAT's 10 year anniversary!
  • Apr 16, 2009: xCAT 2.2 released.
  • Oct 31, 2008: xCAT 2.1 released.
  • Sep 12, 2008: Support for xCAT 2 can now be purchased!
  • June 9, 2008: xCAT breaths life into (at the time) the fastest supercomputer on the planet
  • May 30, 2008: xCAT 2.0 for Linux officially released!
  • Oct 31, 2007: IBM open sources xCAT 2.0 to allow collaboration among all of the xCAT users.
  • Oct 31, 1999: xCAT 1.0 is born!
    xCAT started out as a project in IBM developed by Egan Ford. It was quickly adopted by customers and IBM manufacturing sites to rapidly deploy clusters.
Clone this wiki locally