1. Proposed title of this feature request

IPAM for Baremetal networking

2. What is the nature and description of the request?

Currently when deploying BM asset with metal3, there are 3 ways to provision networking:

• using 3rd party dhcp solution

• spec.preprovisioningNetworkDataName - nmstate format static network injection for inspection and deployment 

• cloud-init - spec.networkData.name - json format static network injection for deployed OS network

This request is to unify all 3 methods into a single solution that can dynamically allocate an IP to a baremetal host at each state of it's lifecycle

OpenStack neutron provides an equivalent of this capabilities for OpenStack Ironic use case 

3. Why does the customer need this? (List the business requirements here)

Statically assigning the IPs to a large fleet of BM nodes is unfeasible. Also variety methods use today (json, nmstate yaml, dhcp) adds to operational overhead and complexity.

4. List any affected packages or components.