• This is a "shared" network, meaning it is visible to all tenants via the Quantum API. Tenant VMs have a single NIC, and receive a fixed IP address from the subnet(s) associated with that network. This essentially maps to the FlatManager and FlatDHCPManager models provided by Nova. Floating IPs are not supported.
Use Case: Multiple Flat Network
• This use case is very similar to the above Single Flat Network use case, except that tenants see multiple shared networks
Use Case: Mixed Flat and Private Network
in which tenants also optionally have access toprivate per-tenant networks. In addition to seeingone or more shared networks via the quantum API,tenants can create additional networks that areonly visible to users of that tenant. When creatingVMs, those VMs can have NICs on any of the sharednetworks and/or any of the private networksbelonging to the tenant. This enables the creationof "multi-tier" topologies using VMs with multipleNICs. It also supports a model where a VM acting asa gateway can provide services such as routing, NAT,or load balancing.
Provider Router with Private Networks
This use provides each tenant with one or moreprivate networks, which connect to the outsideworld via a Quantum router. The case whereeach tenant gets exactly one network in thisform maps to the same logical topology as theVlanManager in Nova. Using the Quantum API,the tenant would only see a network for eachprivate network assigned to that tenant. Therouter object in the API is created and owned bythe cloud admin.
Per-tenant Routers with Private Networks
A more advanced router scenario in which each tenantgets at least one router, and potentially has access to theQuantum API to create additional routers. The tenant cancreate their own networks, potentially unlinking thosenetworks to a router. This model enables tenant-definedmulti-tier applications, with each tier being a separatenetwork behind the router. Since there are multiplerouters, tenant subnets can be overlapping withoutconflicting, since access to external networks all happensvia SNAT or Floating IPs. Each router uplink and floating IPis allocated from the external network subnet.
• 3 Servers Server 1 = > running network controller and nova-compute Server 2 = > running nova-compute, Cinder, rabbit-mq, mysql, keystone, glance, swift Server 3 = > running nova-compute• All servers are having 4 lan card, eth0 is connected to public switch and rest are connected to private switch. eth3 of Server 1 is also connected to public switch for br-ex. all node eth2 is for br-int• 10.10.x.x is for public access• 172.24.0.x is for private network• 172.24.x.x is reserved for tenant Network
Network Node Setup• vi /etc/network/interfacesauto eth0iface eth0 inet staticaddress 10.10.1.2netmask 255.255.255.0gateway 10.10.1.254dns-nameservers 10.10.2.2###### VMs Networks with OVS in tunnel modeauto eth1iface eth1 inet manualup ifconfig $IFACE 0.0.0.0 upup ip link set $IFACE promisc ondown ip link set $IFACE promisc offdown ifconfig $IFACE down############ Public Bridgeauto eth3iface eth3 inet manualup ifconfig $IFACE 0.0.0.0 upup ip link set $IFACE promisc ondown ip link set $IFACE promisc offdown ifconfig $IFACE down
Network setup for Compute Nodes• #vi /etc/network/interfaces## Management Networkauto eth0iface eth0 inet staticaddress 10.10.1.1netmask 255.255.255.0gateway 10.10.1.254dns-nameservers 10.10.2.2## VMs Networks with OVS in tunnel modeauto eth1iface eth1 inet manualup ifconfig $IFACE 0.0.0.0 upup ip link set $IFACE promisc ondown ip link set $IFACE promisc offdown ifconfig $IFACE down
How to create Quantum Network• Internal Network• Internal Subnet• Router• External Network• External Subnet• Floating IP