06-Neutron.pptx

Neutron- Networking ServiceXuan Luo16 October 2014Neutron in OpenStack Conceptual ArchitectureNeutron OverviewNetwork as a ServiceAllow tenants to control their own private networksIsolatedRich topologiesChoose their own IP addressing scheme, even if those IP addresses overlap with those used by other tenantsOpen APIs for operating logical networksTechnology agnostic. Separate logical operations and backend provisionsBackend technologies are provisioned/configured by plugins/driversModular designAPI specifies service, vendor provides its implementationExtensions for vendor-specific featuresAdvance services supportLoad balancing, VPN, FirewallSupport emerging network technologySDN/OpenFlow-based networkOverlay tunneling (VXLAN, NVGRE, STT, …)Neutron Deployment Use CasesPer-tenant Routers with Private NetworksTenant-AVMTenant-AVMTenant-AVM3Tenant-AVM4Tenant-CVMTenant-CVMTenant-A Private Net-/24Tenant-A Private Net-/24Tenant-C Private Net/24Tenant-C RouterTenant-A RouterExternal Net/2Physical RouterWork Flow of NeutronTenant-A Private Net-1Create a network. Network is an isolated L2 segment, analogous to VLAN in the physical networking world.Work Flow of NeutronTenant-A Private Net-/24Create a subnet and assign it with the network. Subnet is a block of v4 or v6 IP addresses and serves as an address pool from which OpenStack can assign IP addresses to VMs. Subnet must be associated with a network.Multiple subnet can be associated with one network.Work Flow of NeutronTenant-A Private Net-/24Create a port on the network.Port is a connection point for attaching a single device, such as the NIC of a virtual server, to a virtual network. Also describes the associated network configuration, such as the MAC and IP addresses to be used on that port.Work Flow of NeutronTenant-AVMTenant-A Private Net-/24After the port is created, VM can be attached to the port. Then the MAC and IP address are injected into VM. This IP address is also called fixed IP.Work Flow of NeutronTenant-AVM