Neutron Configuration

Neutron Configuration:

Deploying OpenStack neutron(with 3 nodes) as explained in previous post OpenStack Neutron Architecture

1. Requirements: 
Considering its as management network as 10.30.10.0/24.

Controller Node: Controller node contains all OpenStack API services. It requires one NIC card.
        NIC-1(eth0) : Connected with management network. (IP-10.30.10.3)

Network Node: Network node contains DHCP server and virtual routing. It requires 3 NIC cards.
        NIC-1(eth0) : Connected to management network.(IP-10.30.10.4)
        NIC-2(eth1) : Connected to VM internal network. (No ip address is assigned)
        NIC-3(eth2) : Connected to VM external network. (No ip address is assigned)

Compute Node: Network node contains compute service and neutron plugin. It requires 2 NIC cards.
        NIC-1(eth0) : Connected to management network.(IP-10.30.10.5)
        NIC-2(eth1) : Connected to VM internal network. (No ip address is assigned)

OpenStack Neutron architecture

OpenStack Networking - Neutron (formally Quantum).
 
Neutron:
Neutron is an OpenStack project to provide "networking as a service" between interface devices. It enables operators to leverage different networking technologies to power their cloud networking.

Neutron supports each tenant having multiple private networks, and allows tenants to choose their own IP addressing scheme (even if those IP addresses overlap with those that other tenants use).

Network Architecture:
This is basic network architecture, you can add more compute nodes.

Management network. Used for internal communication between OpenStack Components.
Internal network. Used for VM data communication within the cloud deployment.
External network. Used to provide VMs with Internet access.

Controller Node: Controller node contains all OpenStack API services.
Network Node: Network node contains DHCP server and virtual routing.
Compute Node: Network node contains compute service and neutron plugin.