Subnet Pools and Pluggable IPAM

1 | © 2013 Infoblox Inc. All Rights Reserved. 1

Subnet Pools and Pluggable IPAMLiberty Design Summit

May 20th 2015

Carl Baldwin, Neutron Development, HPJohn Belamaric, Senior Architect, Infoblox

John Voss, Senior Product Manager, Infoblox


• No VM connectivity without a valid IP assigned • Duplicate subnets/IPs in shared or routable space are disastrous

2 Especially relevant when using provider networks• Allocation of subnets for large scale deployments can be difficult and

time consuming2 Especially for Tenants using non-overlapping addresses2 Errors in address planning and quota allocation are difficult to reverse

• Users have multiple/heterogeneous environments2 Track IPs/subnets across multiple clusters2 Reclaim IPs/subnets that are no longer in use

Why is IPAM important for Neutron?


• Dynamic Subnet Allocation2 Enables definition of per-tenant and shared pools of subnets2 Delivered in Kilo

• Pluggable IPAM2 Enables integration of home grown or 3rd party IPAM systems2 Enables centralized management of addressing across the cloud and

organization2 On track for delivery in Liberty

IPAM Enhancements for Neutron


• What was introduced in Kilo?2 Subnet Pool - Range of addresses from which subnets may be allocated- May be exclusive to a tenant or shared- Enforces a quota for shared pools- Simplifies centralized management of subnet allocations to tenants- Example: 10.0.0.0/16 from which smaller subnets (/20, /23, /24, etc.) are allocated

• How does it work?2 Pools can be managed via the API or neutron client2 Optionally specify a pool when allocating a subnet- Leave out the CIDR and just pass a prefix length (or use the default prefix length)- Specify a CIDR if you want, as long as it fits in the pool without overlap

Subnet Allocation


Creating a Subnet Pool


Allocate a Subnet From a Pool


Allocate a Specific Subnet


Update the Pool


First-fit when multiple prefixes


• Kilo and earlier IPAM is embedded in Neutron• In Liberty, IPAM services will have a driver-based architecture

2 Allocation of subnets, fixed and floating IPs handled via IPAM driver2 Optionally enabled - by default “built-in” IPAM will be used2 Reference driver has no user-facing differences

• Enables alternate drivers2 Local drivers with alternate allocation strategies2 Third-party drivers to interface with external IPAM2 Custom-built drivers to interface with home grown IPAM systems

Pluggable IPAM


Pluggable IPAM


• Address scopes become first-class objects2 Created and managed via the API2 Routers will not route between them without NAT or (maybe) an override2 Associate an RD and RT for BGP advertising (and/or VPN ID)

• Per subnet-pool IPAM driver configurations2 Enables different drivers for different pools2 Track private spaces locally and reserve external IPAM for routable space

Future Possibilities

Subnet Pools and Pluggable IPAM

Software

Transcript of Subnet Pools and Pluggable IPAM