A Subnet will define a range of IP Addresses that it manages for reservations. A Pool is a container for one or more Subnets.
Users will be able to create Pools & Subnets through the API.
The next pass will incorporate extensibility features and flush out Consul integration. As such the plan of record is to implement all of the API end points and their associated data models in a first pass while following up with specific business logic to implement the initial lease allocation and reservation process. To that end we are thinking of IPAM as more of a resource allocation service with a strong API & flexible data model while providing less out of the box integration with network services like DHCP & DNS or concerns such as routing topologies.Ĭurrently IPAM development is driving towards providing the initial technology for it’s REST API and underlying data model. A flexible solution providing extensible configuration, reservation, and auditing of IP resources will provide a capability to more easily integrate with different operational designs. IPAM intends to fill a gap around dynamic configuration of resources in datacenter management workflows.
