2. The Quantum project was created to provide a rich and tenant-facing API
for defining network connectivity and addressing in the cloud.
Network
Subnet
Port
3. Flexibility to Choose Different Network Technologies
Open vSwitch
Cisco
Linux Bridge
Nicira NVP
Ryu
NEC OpenFlow
7. • 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.
11. in which tenants also optionally have access to
private per-tenant networks. In addition to seeing
one or more shared networks via the quantum API,
tenants can create additional networks that are
only visible to users of that tenant. When creating
VMs, those VMs can have NICs on any of the shared
networks and/or any of the private networks
belonging to the tenant. This enables the creation
of "multi-tier" topologies using VMs with multiple
NICs. It also supports a model where a VM acting as
a gateway can provide services such as routing, NAT,
or load balancing.
13. This use provides each tenant with one or more
private networks, which connect to the outside
world via a Quantum router. The case where
each tenant gets exactly one network in this
form maps to the same logical topology as the
VlanManager in Nova. Using the Quantum API,
the tenant would only see a network for each
private network assigned to that tenant. The
router object in the API is created and owned by
the cloud admin.
15. A more advanced router scenario in which each tenant
gets at least one router, and potentially has access to the
Quantum API to create additional routers. The tenant can
create their own networks, potentially unlinking those
networks to a router. This model enables tenant-defined
multi-tier applications, with each tier being a separate
network behind the router. Since there are multiple
routers, tenant subnets can be overlapping without
conflicting, since access to external networks all happens
via SNAT or Floating IPs. Each router uplink and floating IP
is allocated from the external network subnet.
16.
17. • 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
18. Network Node Setup
• vi /etc/network/interfaces
auto eth0
iface eth0 inet static
address 10.10.1.2
netmask 255.255.255.0
gateway 10.10.1.254
dns-nameservers 10.10.2.2
###### VMs Networks with OVS in tunnel mode
auto eth1
iface eth1 inet manual
up ifconfig $IFACE 0.0.0.0 up
up ip link set $IFACE promisc on
down ip link set $IFACE promisc off
down ifconfig $IFACE down
############ Public Bridge
auto eth3
iface eth3 inet manual
up ifconfig $IFACE 0.0.0.0 up
up ip link set $IFACE promisc on
down ip link set $IFACE promisc off
down ifconfig $IFACE down
20. Network setup for Compute Nodes
• #vi /etc/network/interfaces
## Management Network
auto eth0
iface eth0 inet static
address 10.10.1.1
netmask 255.255.255.0
gateway 10.10.1.254
dns-nameservers 10.10.2.2
## VMs Networks with OVS in tunnel mode
auto eth1
iface eth1 inet manual
up ifconfig $IFACE 0.0.0.0 up
up ip link set $IFACE promisc on
down ip link set $IFACE promisc off
down ifconfig $IFACE down
21. How to create Quantum Network
• Internal Network
• Internal Subnet
• Router
• External Network
• External Subnet
• Floating IP
