User Tools

Site Tools


ipv6_opnfv_project:metadata_structure

Differences

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

Link to this comparison view

Next revision
Previous revision
ipv6_opnfv_project:metadata_structure [2015/07/17 04:32]
Bin Hu created
ipv6_opnfv_project:metadata_structure [2015/09/04 08:12] (current)
Sridhar Gaddam [Greenfield approach with Cloudinit]
Line 46: Line 46:
  
 9. The VM booted in above step would have two interfaces (say eth0 and eth1) and would have IP addresses assigned from the respective subnets. ​ 9. The VM booted in above step would have two interfaces (say eth0 and eth1) and would have IP addresses assigned from the respective subnets. ​
 +
 +==== Greenfield approach with Cloudinit ====
 +
 + #​cloud-config
 + bootcmd:
 +   - /​usr/​sbin/​ifdown eth0
 +   - /​usr/​sbin/​ifup eth0
 +   - /​usr/​sbin/​ifdown eth1
 +   - /​usr/​sbin/​ifup eth1
 +   - setenforce 0
 +   - /​sbin/​sysctl -w net.ipv6.conf.all.forwarding=1
 +   - /​sbin/​sysctl -w net.ipv6.conf.eth0.accept_ra=2
 +   - /​sbin/​sysctl -w net.ipv6.conf.eth0.accept_ra_defrtr=1
 +   - /​sbin/​sysctl -w net.ipv6.conf.eth0.router_solicitations=1
 + packages:
 +   - radvd
 + runcmd:
 +   - /​usr/​sbin/​ifdown eth1
 +   - /​usr/​sbin/​ifup eth1
 +   - /​usr/​bin/​systemctl disable NetworkManager
 +   - /​usr/​bin/​systemctl start radvd
 +   - echo '​complete'​ >> /​tmp/​cloud-config.log
 + write_files:​
 + - content: |
 +      ​TYPE="​Ethernet"​
 +      ​BOOTPROTO="​dhcp"​
 +      ​DEFROUTE="​yes"​
 +      ​PEERDNS="​yes"​
 +      ​PEERROUTES="​yes"​
 +      ​IPV4_FAILURE_FATAL="​no"​
 +      ​IPV6INIT="​yes"​
 +      ​IPV6_AUTOCONF="​yes"​
 +      ​IPV6_DEFROUTE="​yes"​
 +      ​IPV6_PEERROUTES="​yes"​
 +      ​IPV6_PEERDNS="​yes"​
 +      ​IPV6_FAILURE_FATAL="​no"​
 +      ​NAME="​eth0"​
 +      ​DEVICE="​eth0"​
 +      ​ONBOOT="​yes"​
 +    path: /​etc/​sysconfig/​network-scripts/​ifcfg-eth0
 +    ​permissions:​ '​0755'​
 +    ​owner:​ root:root
 + - content: |
 +      ​TYPE="​Ethernet"​
 +      ​BOOTPROTO=static
 +      ​IPV6INIT=yes
 +      ​IPV6ADDR="​2001:​db8:​0:​2::​1/​64"​
 +      ​NAME=eth1
 +      ​DEVICE=eth1
 +      ​ONBOOT=yes
 +      ​NM_CONTROLLED=no
 +    path: /​etc/​sysconfig/​network-scripts/​ifcfg-eth1
 +    ​permissions:​ '​0755'​
 +    ​owner:​ root:root
 + - content: |
 +      ​interface eth1
 +      {
 + AdvSendAdvert on;
 + MinRtrAdvInterval 3;
 + MaxRtrAdvInterval 10;
 + AdvHomeAgentFlag off;
 + AdvManagedFlag on;
 + AdvOtherConfigFlag on;
 + prefix 2001:​db8:​0:​2::/​64
 + {
 +     AdvOnLink on;
 +     ### On link tells the host that the default router is on the same "​link"​ as it is
 +     AdvAutonomous on;
 +     AdvRouterAddr off;
 + };
 +      };
 +    path: /​etc/​radvd.conf
 +    ​permissions:​ '​0644'​
 +    ​owner:​ root:root
 + - content: |
 +      ​IPV6FORWARDING=yes
 +    path: /​etc/​sysconfig/​network
 +    ​permissions:​ '​0644'​
 +    ​owner:​ root:root
 +==== Brownfield approach with Meta Data Structure ====
 +
 +This will be more suitable for OPNFV 6-server POD usage with Jenkins Integration. As pointed by Iben Rodriguez of Spirent, most enterprise prefer to work with existing DC resources and hence Carriers need to support Brownfield vRouter in VM within existing DC resources.
 +
 +Now we have  an IP6VM (meaning a VM with two IPv6 Interfaces) ​ and we need to downlaod and install Quagga base package(with just IPv6 add-on) to invoke and use it as a   ​VRouter,​ rather than the OVS based in Hypervisor for switching and forwarding as usually done in OpenStack Neutron.Functionally the VM approach may have performance issues but lets deal with that latter as this gives better isolation and modularity for scaling.
  
  
ipv6_opnfv_project/metadata_structure.1437107565.txt.gz ยท Last modified: 2015/07/17 04:32 by Bin Hu