Open Stack Neutron Packet Flow between VM’s

0
1805

host-view

 

Networking integrates with OpenStack components in a number of ways:

  • Networking relies on the Identity service (keystone) for the authentication and authorization of all API   requests.
  • As part of creating a VM, the nova-compute service communicates with the Networking API to plug each virtual NIC on the VM into   a particular network.
  • The dashboard (horizon) integrates with the Networking API, enabling administrators and tenant users to create and manage network services through a web-based GUI.

VM1 <–> VM2

  • Packet gets initiated from vNic0 of the Nova instance of customer
  • vNic0 is connected to to the ovs bridge ( br-int)
  • br-int forwards packet to br-tun and br-tun adds header to the packet and sends to compute node 02 over GRE tunnel
  • Compute Node 02 (br-tun recieves the packet and remove the header and forwards to br-int )
  • br-int would send it vNic0 0f vm-02

VM1 <–> Network Node –> Internet

  • Packet gets initiated from vNic0 of the Nova instance of customer
  • vNic0 is connected to to the ovs bridge ( br-int)
  • br-int forwards packet to br-tun and br-tun adds header to the packet and sends to Network node over GRE tunnel
  • Network Node (br-tun recieves the packet and remove the header and forwards to br-int )
  • The packet is forwarded to qrouter namespace > br-ex and then goes to eth1 public interface and then to internet

LEAVE A REPLY

Please enter your comment!
Please enter your name here