Differences

This shows you the differences between two versions of the page.

--- ipv6_opnfv_project:create_networks [2015/10/16 06:29]
Bin Hu
+++ ipv6_opnfv_project:create_networks [2015/12/30 08:40] (current)
Sridhar Gaddam
@@ Line 1: / Line 1: @@
-===== Step 5: Creating Networks and Subnets =====
+===== Step 4: Creating Networks and Subnets =====
 OPNFV POC OpenStack Setup Instructions.
@@ Line 6: / Line 6: @@
 Steps to be executed on the snsj113 (IP: 198.59.156.113) machine (''refer to [[http://spirent.app.box.com/notes/37713582266?s=tgm98glcerw9zlcdy6pclavjlorgop4v|the details of lab environment]]'').
-. Login as odl user and change directory to devstack.
+. Login as odl user and source the credentials.
    cd ~/devstack
+   odl@opnfv-openstack-ubuntu:~/devstack$ source openrc admin demo
+. Clone the opnfv_os_ipv6_poc repo.
-. Source the credentials.
+   git clone https://github.com/sridhargaddam/opnfv_os_ipv6_poc.git /opt/stack/opnfv_os_ipv6_poc
-   odl@opnfv-openstack-ubuntu:~/devstack$ source openrc admin demo
 . We want to manually create networks/subnets that will help us to achieve the POC, so we have used the flag, ''NEUTRON_CREATE_INITIAL_NETWORKS=False'' in ''local.conf'' file. When this flag is set to False, devstack does not create any networks/subnets during the setup phase.
@@ Line 18: / Line 18: @@
 . On snsj113 machine, eth1 provides external/public connectivity (both IPv4 and IPv6). So let us add this interface to br-ex and move the IP address (including the default route) from eth1 to br-ex.
-''Note: This can be automated in /etc/network/interfaces. This file /etc/network/interfaces is already configured in host snsj113 to achieve this.''
+''Note: This can be automated in /etc/network/interfaces. ''
-   sudo ovs-vsctl del-port br-ex eth1 && sudo ip addr del 198.59.156.113/24 dev br-ex && sudo ifconfig eth1 up &&  sudo ip addr add 198.59.156.113/24 dev eth1 && sudo ifconfig br-ex up && sudo ip route del default via 198.59.156.1 dev eth1 && sudo ip route add default via 198.59.156.1 dev br-ex
+   sudo ip addr del 198.59.156.113/24 dev eth1 && sudo ovs-vsctl add-port br-ex eth1 && sudo ifconfig eth1 up &&  sudo ip addr add 198.59.156.113/24 dev br-ex && sudo ifconfig br-ex up && sudo ip route add default via 198.59.156.1 dev br-ex
 # Verify that br-ex now has the IPaddress 198.59.156.113/24 and the default route is on br-ex
@@ Line 43: / Line 43: @@
    neutron router-create ipv4-router
-   # Create an external network/subnet using the appropriate values based on the data-center physical network setup.
+# Create an external network/subnet using the appropriate values based on the data-center physical network setup.
    neutron net-create --router:external ext-net
    neutron subnet-create --disable-dhcp --allocation-pool start=198.59.156.251,end=198.59.156.254 --gateway 198.59.156.1 ext-net 198.59.156.0/24
-   # Associate the ext-net to the neutron router.
+# Associate the ext-net to the neutron router.
    neutron router-gateway-set ipv4-router ext-net
-   # Create an internal/tenant ipv4 network.
+# Create an internal/tenant ipv4 network.
    neutron net-create ipv4-int-network1
-   # Create an IPv4 subnet in the internal network.
+# Create an IPv4 subnet in the internal network.
    neutron subnet-create --name ipv4-int-subnet1 --dns-nameserver 8.8.8.8 ipv4-int-network1 20.0.0.0/24
-   # Associate the ipv4 internal subnet to a neutron router.
+# Associate the ipv4 internal subnet to a neutron router.
    neutron router-interface-add ipv4-router ipv4-int-subnet1
-   # Create a second neutron router where we want to "manually spawn a radvd daemon" to simulate external IPv6 router.
+# Create a second neutron router where we want to "manually spawn a radvd daemon" to simulate external IPv6 router.
    neutron router-create ipv6-router
-   # Associate the ext-net to the ipv6-router.
+# Associate the ext-net to the ipv6-router.
    neutron router-gateway-set ipv6-router ext-net
-   # Create a second internal/tenant ipv4 network.
+# Create a second internal/tenant ipv4 network.
    neutron net-create ipv4-int-network2
-   # Create an IPv4 subnet for the ipv6-router internal network.
+# Create an IPv4 subnet for the ipv6-router internal network.
    neutron subnet-create --name ipv4-int-subnet2 --dns-nameserver 8.8.8.8 ipv4-int-network2 10.0.0.0/24
-   # Associate the ipv4 internal subnet2 to ipv6-router.
+# Associate the ipv4 internal subnet2 to ipv6-router.
    neutron router-interface-add ipv6-router ipv4-int-subnet2
-. Download ''fedora20'' image which would be used as vRouter.
+. Download ''fedora22'' image which would be used as vRouter.
-   glance image-create --name 'Fedora20' --disk-format qcow2 --container-format bare --is-public true --copy-from http://cloud.fedoraproject.org/fedora-20.x86_64.qcow2
+   glance image-create --name 'Fedora22' --disk-format qcow2 --container-format bare --is-public true --copy-from https://download.fedoraproject.org/pub/fedora/linux/releases/22/Cloud/x86_64/Images/Fedora-Cloud-Base-22-20150521.x86_64.qcow2
 . Create a keypair.
@@ Line 82: / Line 92: @@
    nova keypair-add vRouterKey > ~/vRouterKey
-. Copy the contents of the following url to ''metadata.txt'' (i.e., metadata which enables IPv6 router functionality inside vRouter)
+. Create some Neutron ports that would be used for vRouter and the two VMs.
-   http://fpaste.org/276989/39903414/
+   neutron port-create --name eth0-vRouter --mac-address fa:16:3e:11:11:11 ipv4-int-network2
+   neutron port-create --name eth1-vRouter --mac-address fa:16:3e:22:22:22 ipv4-int-network1
+   neutron port-create --name eth0-VM1 --mac-address fa:16:3e:33:33:33 ipv4-int-network1
+   neutron port-create --name eth0-VM2 --mac-address fa:16:3e:44:44:44 ipv4-int-network1
+. Boot the vRouter using ''Fedora22'' image on the Compute node (hostname: opnfv-odl-ubuntu)
-. Boot the vRouter using ''Fedora20'' image on the Compute node (hostname: opnfv-odl-ubuntu)
+   nova boot --image Fedora22 --flavor m1.small --user-data /opt/stack/opnfv_os_ipv6_poc/metadata.txt --availability-zone nova:opnfv-odl-ubuntu --nic port-id=$(neutron port-list | grep -w eth0-vRouter | awk '{print $2}') --nic port-id=$(neutron port-list | grep -w eth1-vRouter | awk '{print $2}') --key-name vRouterKey vRouter
-   nova boot --image Fedora20 --flavor m1.small --user-data=./metadata.txt --availability-zone nova:opnfv-odl-ubuntu --nic net-id=$(neutron net-list | grep -w ipv4-int-subnet2 | awk '{print $2}') --nic net-id=(neutron net-list | grep -w ipv4-int-subnet1 | awk '{print $2}') --key-name vRouterKey vRouter
+. Verify that vRouter boots up successfully and the ssh keys are properly injected.
-. Verify that Fedora20 image boots up successfully and the ssh keys are properly injected.
 ''Note: It may take few minutes for the necessary packages to get installed and ssh keys to be injected.''
@@ Line 97: / Line 110: @@
    nova console-log vRouter
-   Sample output:
+# Sample output:
    [  762.884523] cloud-init[871]: ec2: #############################################################
    [  762.909634] cloud-init[871]: ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
@@ Line 108: / Line 122: @@
 ''Note: VM1 is created on Control+Network node (i.e., opnfv-openstack-ubuntu)''
-    nova boot --image cirros-0.3.4-x86_64-uec --flavor m1.tiny --nic net-id=(neutron net-list | grep -w ipv4-int-network1 | awk '{print $2}') --availability-zone nova:opnfv-openstack-ubuntu --key-name vRouterKey VM1
+    nova boot --image cirros-0.3.4-x86_64-uec --flavor m1.tiny --nic port-id=$(neutron port-list | grep -w eth0-VM1 | awk '{print $2}') --availability-zone nova:opnfv-openstack-ubuntu --key-name vRouterKey --user-data /opt/stack/opnfv_os_ipv6_poc/set_mtu.sh VM1
-''Note: VM2 is created on Compute node (i.e., opnfv-openstack-ubuntu)''
+''Note: VM2 is created on Compute node (i.e., opnfv-odl-ubuntu). We will have to configure appropriate mtu on the VM iface by taking into account the tunneling overhead and any physical switch requirements. If so, push the mtu to the VM either using dhcp options or via meta-data. ''
-    nova boot --image cirros-0.3.4-x86_64-uec --flavor m1.tiny --nic net-id=(neutron net-list | grep -w ipv4-int-network1 | awk '{print $2}') --availability-zone nova:opnfv-odl-ubuntu --key-name vRouterKey VM2
+    nova boot --image cirros-0.3.4-x86_64-uec --flavor m1.tiny --nic port-id=$(neutron port-list | grep -w eth0-VM2 | awk '{print $2}') --availability-zone nova:opnfv-odl-ubuntu --key-name vRouterKey --user-data /opt/stack/opnfv_os_ipv6_poc/set_mtu.sh VM2
 . Confirm that both the VMs are successfully booted.
@@ Line 123: / Line 137: @@
     sudo ip netns exec qrouter-$(neutron router-list | grep -w ipv6-router | awk '{print $2}') bash
-    # On successful execution of the above command, you will be in the router namespace.
-Copy the following contents to a file ''/tmp/br-ex.radvd.conf''
+# On successful execution of the above command, you will be in the router namespace.\\
+# Configure the IPv6 address on the <qr-xxx> iface.
-    interface qr-0878306e-2b
+    export router_interface=$(ip a s | grep -w "global qr-*" | awk '{print $7}')
-    {
+    ip -6 addr add 2001:db8:0:1::1 dev $router_interface
-       AdvSendAdvert on;
-       MinRtrAdvInterval 3;
-       MaxRtrAdvInterval 10;
-       prefix 2001:db8:0:1::/64
-       {
-	  AdvOnLink on;
-	  AdvAutonomous on;
-       };
-    };
-Configure the IPv6 address on the <qr-xxx> iface.
+# Update the sample radvd.conf file with the $router_interface and spawn ''radvd'' daemon inside the namespace to simulate an external IPv6 router.
-    ip -6 addr add 2001:db8:0:1::1 dev <qr-xxx>
+    cp /opt/stack/opnfv_os_ipv6_poc/scenario2/radvd.conf /tmp/radvd.$router_interface.conf
+    sed -i 's/$router_interface/'$router_interface'/g' /tmp/radvd.$router_interface.conf
+    $radvd -C /tmp/radvd.$router_interface.conf -p /tmp/br-ex.pid.radvd -m syslog
-Spawn a ''radvd'' daemon to simulate an external router.
+Configure the downstream route pointing to the eth0 iface of vRouter.
+    ip -6 route add 2001:db8:0:2::/64 via 2001:db8:0:1:f816:3eff:fe11:1111
-    $radvd -C /tmp/br-ex.radvd.conf -p /tmp/br-ex.pid.radvd -m syslog
+    Note: The routing table should now look something similar to shown below.
+    ip -6 route show
+:db8:0:1::1 dev qr-42968b9e-62  proto kernel  metric 256
+:db8:0:1::/64 dev qr-42968b9e-62  proto kernel  metric 256  expires 86384sec
+:db8:0:2::/64 via 2001:db8:0:1:f816:3eff:fe11:1111 dev qr-42968b9e-62  proto ra  metric 1024  expires 29sec
+    fe80::/64 dev qg-3736e0c7-7c  proto kernel  metric 256
+    fe80::/64 dev qr-42968b9e-62  proto kernel  metric 256
-You will also have to add an ipv6 route which points to the ''eth0'' interface of vRouter. This is necessary for the ipv6 router to know that ''2001:db8:0:2::/64'' is reachable via the ''eth0'' interface of vRouter.
+Now, let us ssh to one of the VMs (say VM1) to confirm that it has successfully configured the IPv6 address using SLAAC with prefix from vRouter.
-    ip -6 route add 2001:db8:0:2::/64 via <LLA-of-eth0-iface-on-vRouter> dev <qr-iface>
-Verify that the route is properly added.
-    ip -6 route show
-Now, let us ssh to one of the VMs (say VM1) to confirm that it has successfully configured the IPv6 address using SLAAC with prefix from vRouter. ''Note: Get the IPv4 address associated to VM1. This can be inferred from nova list command.
+''Note: Get the IPv4 address associated to VM1. This can be inferred from nova list command.''
     ssh -i /home/odl/vRouterKey cirros@<VM1-ipv4-address>
 If everything goes well, ssh will be successful and you will be logged into VM1. Run some commands to verify that IPv6 addresses are configured on ''eth0'' interface.
@@ Line 173: / Line 180: @@
     exit
+The Network Topology of this setup would be as follows.
+{{:ipv6_opnfv_project:setup-os_odl.png}}
+[[http://199.188.118.108:8181/index.htm| ODL DLUX UI]] would display the two nodes as shown below.
+{{:ipv6_opnfv_project:odl-dlux_ipv6_poc.png}}

Wiki

User Tools

Site Tools

Differences

Page Tools