diff --git a/docs/en-US/hypervisor-host-install-firewall.xml b/docs/en-US/hypervisor-host-install-firewall.xml new file mode 100644 index 00000000000..9efca5ed43b --- /dev/null +++ b/docs/en-US/hypervisor-host-install-firewall.xml @@ -0,0 +1,52 @@ + + +%BOOK_ENTITIES; +]> + + + +
+ Configuring the firewall + The hypervisor needs to be able to communicate with other hypervisors and the management server needs to be able to reach the hypervisor. + In order to do so we have to open the following TCP ports (if you are using a firewall): + + 22 (SSH) + 1798 + 16509 (libvirt) + 5900 - 6100 (VNC consoles) + 49152 - 49216 (libvirt live migration) + + It depends on the firewall you are using how to open these ports. Below you'll find examples how to open these ports in RHEL/CentOS and Ubuntu. +
+ Open ports in RHEL/CentOS + TODO: How to open ports +
+
+ Open ports in Ubuntu + The default firewall under Ubuntu is UFW (Uncomplicated FireWall), although not enabled. + To open the required ports, execute the following commands: + ufw allow proto tcp from any to any port 22 + ufw allow proto tcp from any to any port 1798 + ufw allow proto tcp from any to any port 16509 + ufw allow proto tcp from any to any port 5900:6100 + ufw allow proto tcp from any to any port 49152:492160 + By default UFW is not enabled on Ubuntu. Executing these commands with the firewall disabled does not enable the firewall. +
+
\ No newline at end of file diff --git a/docs/en-US/hypervisor-host-install-flow.xml b/docs/en-US/hypervisor-host-install-flow.xml index 5badfde8888..af1daa744e3 100644 --- a/docs/en-US/hypervisor-host-install-flow.xml +++ b/docs/en-US/hypervisor-host-install-flow.xml @@ -28,4 +28,6 @@ + + \ No newline at end of file diff --git a/docs/en-US/hypervisor-host-install-network.xml b/docs/en-US/hypervisor-host-install-network.xml new file mode 100644 index 00000000000..e4f668e0c4b --- /dev/null +++ b/docs/en-US/hypervisor-host-install-network.xml @@ -0,0 +1,151 @@ + + +%BOOK_ENTITIES; +]> + + + +
+ Configure the network bridges + This is a very important section, please make sure you read this thoroughly. + In order to forward traffic to your instances you will need at least two bridges: public and private. + By default these bridges are called cloudbr0 and cloudbr1, but you do have to make sure they are available on each hypervisor. +
+ Network example + There are many ways to configure your network. In the Basic networking mode you should have two (V)LAN's, one for your private network and one for the public network. + The hypervisor has one NIC (eth0) with three VLAN's: + + VLAN 100 for management of the hypervisor + VLAN 200 for public network of the instances (cloudbr0) + VLAN 300 for private network of the instances (cloudbr1) + + On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with the gateway 192.168.42.1 +
+
+ Configuring the network bridges + It depends on the distribution you are using how to configure these, below you'll find examples for RHEL/CentOS and Ubuntu. + The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this section. This should be used as a guideline only. The exact configuration will depend on your network layout. +
+ Configure in RHEL or CentOS + The required packages were installed when libvirt was installed, we can proceed to configuring the network. + First we configure eth0 + vi /etc/sysconfig/network-scripts/ifcfg-eth0 + Make sure it looks similair to: + + We now have to configure the three VLAN interfaces: + vi /etc/sysconfig/network-scripts/ifcfg-eth0.100 + + vi /etc/sysconfig/network-scripts/ifcfg-eth0.200 + + vi /etc/sysconfig/network-scripts/ifcfg-eth0.300 + + Now we have the VLAN interfaces configured we can add the bridges on top of them. + vi /etc/sysconfig/network-scripts/ifcfg-cloudbr0 + Now we just configure it is a plain bridge without an IP-Adress + + We do the same for cloudbr1 + vi /etc/sysconfig/network-scripts/ifcfg-cloudbr1 + + With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly. + Make sure you have an alternative way like IPMI or ILO to reach the machine in case you made a configuration error and the network stops functioning! +
+
+ Configure in Ubuntu + All the required packages were installed when you installed libvirt, so we only have to configure the network. + vi /etc/network/interfaces + Modify the interfaces file to look like this: + + With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly. + Make sure you have an alternative way like IPMI or ILO to reach the machine in case you made a configuration error and the network stops functioning! +
+
+
\ No newline at end of file