You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by ha...@apache.org on 2014/01/23 18:05:34 UTC
git commit: Add a section to describe VNIs allocation matter
Updated Branches:
refs/heads/master ef9c1de5f -> c9b8bc088
Add a section to describe VNIs allocation matter
Add a description that explain a physical interface name can be used for
traffic label.
Update screen shots to catch up new UI visual appearance.
Update Linux distribution list to include CentOS 6.5
Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/commit/c9b8bc08
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/tree/c9b8bc08
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs/diff/c9b8bc08
Branch: refs/heads/master
Commit: c9b8bc0884e9e1166046bfdd1354a991d39d7d71
Parents: ef9c1de
Author: ynojima <ma...@ynojima.net>
Authored: Tue Jan 21 18:07:29 2014 -0700
Committer: Toshiaki Hatano <ha...@haeena.net>
Committed: Fri Jan 24 01:05:46 2014 +0900
----------------------------------------------------------------------
vxlan/en-US/images/vxlan-physicalnetwork.png | Bin 0 -> 68376 bytes
vxlan/en-US/images/vxlan-trafficlabel.png | Bin 72542 -> 61473 bytes
vxlan/en-US/images/vxlan-vniconfig.png | Bin 0 -> 18161 bytes
vxlan/en-US/plugin-vxlan-config-hypervisor.xml | 72 ++++++++++++--------
vxlan/en-US/plugin-vxlan-config-management.xml | 25 ++++++-
vxlan/en-US/plugin-vxlan-requirements.xml | 6 ++
vxlan/en-US/plugin-vxlan-revision-history.xml | 13 ++++
7 files changed, 86 insertions(+), 30 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/c9b8bc08/vxlan/en-US/images/vxlan-physicalnetwork.png
----------------------------------------------------------------------
diff --git a/vxlan/en-US/images/vxlan-physicalnetwork.png b/vxlan/en-US/images/vxlan-physicalnetwork.png
index e69de29..eb06fcd 100644
Binary files a/vxlan/en-US/images/vxlan-physicalnetwork.png and b/vxlan/en-US/images/vxlan-physicalnetwork.png differ
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/c9b8bc08/vxlan/en-US/images/vxlan-trafficlabel.png
----------------------------------------------------------------------
diff --git a/vxlan/en-US/images/vxlan-trafficlabel.png b/vxlan/en-US/images/vxlan-trafficlabel.png
index 956d5f4..916e944 100644
Binary files a/vxlan/en-US/images/vxlan-trafficlabel.png and b/vxlan/en-US/images/vxlan-trafficlabel.png differ
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/c9b8bc08/vxlan/en-US/images/vxlan-vniconfig.png
----------------------------------------------------------------------
diff --git a/vxlan/en-US/images/vxlan-vniconfig.png b/vxlan/en-US/images/vxlan-vniconfig.png
new file mode 100644
index 0000000..c7372a0
Binary files /dev/null and b/vxlan/en-US/images/vxlan-vniconfig.png differ
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/c9b8bc08/vxlan/en-US/plugin-vxlan-config-hypervisor.xml
----------------------------------------------------------------------
diff --git a/vxlan/en-US/plugin-vxlan-config-hypervisor.xml b/vxlan/en-US/plugin-vxlan-config-hypervisor.xml
index 2c5e138..d441c8b 100644
--- a/vxlan/en-US/plugin-vxlan-config-hypervisor.xml
+++ b/vxlan/en-US/plugin-vxlan-config-hypervisor.xml
@@ -24,19 +24,24 @@
<title>Configure hypervisor</title>
<section id="plugin-vxlan-config-hypervisor-kvm">
<title>Configure hypervisor: KVM</title>
- <para>In addition to "KVM Hypervisor Host Installation" in "&PRODUCT; Installation Guide", you have to configure the following item on the host.</para>
- <section id="plugin-vxlan-config-hypervisor-kvm-ip">
+ <para>
+ In addition to "KVM Hypervisor Host Installation" in "&PRODUCT; Installation Guide", you have to configure the following item on the host.
+ </para>
+ <section id="plugin-vxlan-config-hypervisor-kvm-bridge">
<title>Create bridge interface with IPv4 address</title>
<para>
This plugin requires an IPv4 address on the KVM host to terminate and originate VXLAN traffic.
- The address should be assinged to bridge interface created for the instances' private network.
+ The address should be assinged to a physical interface or a bridge interface bound to a physical interface.
Both a private address or a public address are fine for the purpose.
It is not required to be in the same subnet for all hypervisors in a zone, but they should be able to reach each other via IP multicast with UDP/8472 port.
+ A name of a physical interface or a name of a bridge interface bound to a physical interface can be used as a traffic label.
+ Physical interface name fits for almost all cases, but if physical interface name differs per host, you may use a bridge to set a same name.
+ If you would like to use a bridge name as a traffic label, you may create a bridge in this way.
</para>
<para>
Let <parameter>cloudbr1</parameter> be the bridge interface for the instances' private network.
</para>
- <section id="plugin-vxlan-config-hypervisor-kvm-centos">
+ <section id="plugin-vxlan-config-hypervisor-kvm-bridge-rhel">
<title>Configure in RHEL or CentOS</title>
<para>
When you configured the <parameter>cloudbr1</parameter> interface as below,
@@ -66,29 +71,9 @@ IPV6_AUTOCONF=no
DELAY=5
STP=yes
</programlisting>
- <para>
- RHEL and CentOS use iptables for firewalling the system, you can open extra ports by executing the following iptable commands:
- </para>
- <programlisting language="Bash">$ sudo iptables -I INPUT -p udp -m udp --dport 8472 -j ACCEPT
- </programlisting>
- <para>
- These iptable settings are not persistent accross reboots, we have to save them first.
- </para>
- <programlisting language="Bash">$ sudo iptables-save > /etc/sysconfig/iptables
- </programlisting>
- <para>
- With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly.
- </para>
- <programlisting language="Bash">$ sudo service network restart
-$ sudo reboot
- </programlisting>
- <warning>
- <para>
- 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!
- </para>
- </warning>
+
</section>
- <section id="plugin-vxlan-config-hypervisor-kvm-ubuntu">
+ <section id="plugin-vxlan-config-hypervisor-kvm-bridge-ubuntu">
<title>Configure in Ubuntu</title>
<para>
When you configured <parameter>cloudbr1</parameter> as below,
@@ -156,6 +141,39 @@ iface cloudbr1 inet static
bridge_stp off
bridge_maxwait 1
</programlisting>
+ </section>
+ </section>
+ <section id="plugin-vxlan-config-hypervisor-kvm-iptables">
+ <title>Configure iptables to pass XVLAN packets</title>
+ <para>
+ Since VXLAN uses UDP packet to forward encapsulated the L2 frames, UDP/8472 port must be opened.
+ </para>
+ <section id="plugin-vxlan-config-hypervisor-kvm-iptables-rhel">
+ <title>Configure in RHEL or CentOS</title>
+ <para>
+ RHEL and CentOS use iptables for firewalling the system, you can open extra ports by executing the following iptable commands:
+ </para>
+ <programlisting language="Bash">$ sudo iptables -I INPUT -p udp -m udp --dport 8472 -j ACCEPT
+ </programlisting>
+ <para>
+ These iptable settings are not persistent accross reboots, we have to save them first.
+ </para>
+ <programlisting language="Bash">$ sudo iptables-save > /etc/sysconfig/iptables
+ </programlisting>
+ <para>
+ With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly.
+ </para>
+ <programlisting language="Bash">$ sudo service network restart
+ $ sudo reboot
+ </programlisting>
+ <warning>
+ <para>
+ 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!
+ </para>
+ </warning>
+ </section>
+ <section id="plugin-vxlan-config-hypervisor-kvm-iptables-ubuntu">
+ <title>Configure in Ubuntu</title>
<para>
The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is a Python wrapper around iptables.
</para>
@@ -180,7 +198,7 @@ $ sudo reboot
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!
</para>
</warning>
- </section>
+ </section>
</section>
</section>
</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/c9b8bc08/vxlan/en-US/plugin-vxlan-config-management.xml
----------------------------------------------------------------------
diff --git a/vxlan/en-US/plugin-vxlan-config-management.xml b/vxlan/en-US/plugin-vxlan-config-management.xml
index 21f5461..d8ba907 100644
--- a/vxlan/en-US/plugin-vxlan-config-management.xml
+++ b/vxlan/en-US/plugin-vxlan-config-management.xml
@@ -27,7 +27,7 @@
It is not required to add a network element nor to reconfigure the network offering.
The only thing you have to do is configure the physical network to use VXLAN as the isolation method for Guest Network.
</para>
- <section id="plugin-vxlan-config-management-zone">
+ <section id="plugin-vxlan-config-management-physical-network">
<title>Configure the physical network</title>
<mediaobject>
<imageobject>
@@ -50,8 +50,27 @@
</textobject>
</mediaobject>
<para>
- Guest Network traffic label should be name of the bridge interface and the bridge interface should have an IPv4 address.
- See <xref linkend="plugin-vxlan-config-hypervisor-kvm-ip"/> for details.
+ Guest Network traffic label should be the name of the physical interface or the name of the bridge interface and the bridge interface and they should have an IPv4 address.
+ See <xref linkend="plugin-vxlan-config-hypervisor-kvm-bridge"/> for details.
</para>
</section>
+ <section id="plugin-vxlan-config-management-guest-traffic">
+ <title>Configure the guest traffic</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="./images/vxlan-vniconfig.png"/>
+ </imageobject>
+ <textobject>
+ <phrase>vxlan-vniconfig.png: VNI configuration</phrase>
+ </textobject>
+ </mediaobject>
+ <para>
+ Specify a range of VNIs you would like to use for carrying guest network traffic.
+ </para>
+ <warning>
+ <para>
+ VNI must be unique per zone and no duplicate VNIs can exist in the zone. Exercise care when designing your VNI allocation policy.
+ </para>
+ </warning>
+ </section>
</section>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/c9b8bc08/vxlan/en-US/plugin-vxlan-requirements.xml
----------------------------------------------------------------------
diff --git a/vxlan/en-US/plugin-vxlan-requirements.xml b/vxlan/en-US/plugin-vxlan-requirements.xml
index c2e04a6..129e46a 100644
--- a/vxlan/en-US/plugin-vxlan-requirements.xml
+++ b/vxlan/en-US/plugin-vxlan-requirements.xml
@@ -89,6 +89,12 @@
<entry>3.9.10 (2013/07/23)</entry>
<entry>Latest kernel packages are available in "update" repository.</entry>
</row>
+ <row>
+ <entry>CentOS</entry>
+ <entry>>= 6.5</entry>
+ <entry>2.6.32-431.3.1.el6.x86_64 (2014/01/21)</entry>
+ <entry></entry>
+ </row>
</tbody>
</tgroup>
</table>
http://git-wip-us.apache.org/repos/asf/cloudstack-docs/blob/c9b8bc08/vxlan/en-US/plugin-vxlan-revision-history.xml
----------------------------------------------------------------------
diff --git a/vxlan/en-US/plugin-vxlan-revision-history.xml b/vxlan/en-US/plugin-vxlan-revision-history.xml
index ec04d11..7c45a54 100644
--- a/vxlan/en-US/plugin-vxlan-revision-history.xml
+++ b/vxlan/en-US/plugin-vxlan-revision-history.xml
@@ -27,6 +27,19 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>0-2</revnumber>
+ <date>January 21 2014</date>
+ <author>
+ <firstname>Yoshikazu</firstname>
+ <surname>Nojima</surname>
+ <email/>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Add a section to describe VNI allocation matter. Add a description that explain a physical interface name can be used for traffic label.</member>
+ </simplelist>
+ </revdescription>
+ </revision> <revision>
<revnumber>0-1</revnumber>
<date>October 3 2013</date>
<author>