Abandoned - Two Node Fedora 13 Cluster

From Alteeve Wiki
Jump to navigation Jump to search

Post OS Install

Once the OS is installed, we need to do a couple things;

  1. Setup networking.
  2. Change the default run-level.

Setup Networking

We need to remove NetworkManager, enable network, configure the ifcfg-eth* files and then start the network daemon.

Network Layout

This setup expects you to have three physical network cards connected to three independent networks. To have a common vernacular, lets use this table to describe them:

Network Description Short Name Device Name Suggested Subnet NIC Properties
Internet-Facing Network IFN eth0 192.168.1.0/24 Remaining NIC should be used here.
If using a PXE server, this should be a bootable NIC.
Storage Network SN eth1 10.0.0.0/24 Fastest NIC should be used here.
Back-Channel Network BCN eth2 10.0.1.0/24 NICs with IPMI piggy-back must be used here.
Second-fastest NIC should be used here.

Take note of these concerns when planning which NIC to use on each subnet. These issues are presented in the order that they must be addressed in:

  1. If your nodes have IPMI piggy-backing on a normal NIC, that NIC must be used on BCN subnet. Having your fence device accessible on a subnet that can be remotely accessed can pose a major security risk.
  2. The fastest NIC should be used for your SN subnet. Be sure to know which NICs support the largest jumbo frames when considering this.
  3. If you still have two NICs to choose from, use the fastest remaining NIC for your BCN subnet. This will minimize the time it takes to perform tasks like hot-migration of live virtual machines.
  4. The final NIC should be used for the IFN subnet.

Node IP Addresses

Obviously, the IP addresses you give to your nodes should be ones that suit you best. In this example, the following IP addresses are used:

  Internet-Facing Network (IFN) Storage Network (SN) Back-Channel Network (BCN)
an-node01 192.168.1.71 10.0.0.71 10.0.1.71
an-node02 192.168.1.72 10.0.0.72 10.0.1.72

Remove NetworkManager

Some cluster software will not start with NetworkManager installed. This is because is designed to be a highly-adaptive network system that can accommodate frequent changes in the network. To simplify these network transitions for end-users, a lot of reconfiguration of the network is done behind the scenes.

For workstations, this is wonderful. For clustering, this can be disastrous. Transient network outages are already a risk to a cluster's stability!

So first up, make sure that NetworkManager is completely removed from your system. If you used the kickstart scripts, then it was not installed. Otherwise, run: 

yum remove NetworkManager NetworkManager-gnome NetworkManager-openconnect NetworkManager-openvpn NetworkManager-pptp NetworkManager-vpnc cnetworkmanager knetworkmanager knetworkmanager-openvpn knetworkmanager-pptp knetworkmanager-vpnc libproxy-networkmanager yum-NetworkManager-dispatcher

Setup 'network'

With NetworkManager removed, we now need to configure network.

 

Any questions, feedback, advice, complaints or meanderings are welcome.
Alteeve's Niche! Enterprise Support:
Alteeve Support 		Community Support
© Alteeve's Niche! Inc. 1997-2024   Anvil! "Intelligent Availability®" Platform
legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions.
Retrieved from ‘https://alteeve.com/w/index.php?title=Abandoned_-_Two_Node_Fedora_13_Cluster&oldid=1768’