Learning neutron by debugging openstack neutron client

1: install neutron server on a node named neutron-server
    $apt-get install neutron-server neutron-plugin-ml2 python-neutronclient

2:install neutron Networking on a node named neutron
    $apt-get install neutron-plugin-ml2 neutron-plugin-openvswitch-agent \
neutron-l3-agent neutron-dhcp-agent neutron-metadata-agent

3: clone neutron client repo
https://review.openstack.org/p/openstack/python-neutronclient.git

4: create a virtual env
    $cd ~$NEUTRON_CLIENT_HOME && virtalenv .venv
    $. ./.venv/bin/activate

5: pip install -r requirements.txt   test-requirements.txt

6:Run neutron client from command line
   $export export PYTHONPATH=$PYTHONPATH:.
   $$SWIFT_HOME/bin/neutron ext-list

7:Run neutron client from IDE
  
   Pycharm setup

• set project interpreter as $NEUTRON_CLIENT_HOME/.venv/
• import neutron client source code into pycharm project
• Run/edit Configuration/

• keystone environment setup
  
    

Note:

• neutron-server and enutron-client ip and host name entries should be appended to /etc/hosts on neutron client node

Every network created in Neutron, whether created by an administrator or tenant, hasprovider attributes that describe it. Attributes that describe a network include the network's type (such as flat, vlan, gre, vxlan, or local), the physical network interface that the traffic will traverse, and the segmentation ID of the network. The difference between a provider and tenant network is in who or what sets these attributes and how they are managed within OpenStack

Linux brideg driver doesn't support GRE and dvr


In the Juno release of OpenStack, the Neutron community introduced two methods of attaining high availability in routing in a reference implementation. This chapter focuses on a method that uses Virtual Routing Redundancy Protocol, also known as VRRP, to implement redundancy between two or more Neutron routers. High availability usingdistributed virtual routers, otherwise known as DVR,


VRRP utilizes a virtual router identifier, or VRID, within a subnet and exchanges VRRP protocol messages with other routers with the same VRID using multicast to determine the master router. The VRID is 8 bits in length, and the valid range is 1 to 255. As each tenant uses a single administrative network for VRRP communication between routers, tenants are limited to only 255 HA virtual routers.