NvIPAM Ansible Playbook

Man I love it when a play starts to come together. cropped-nvipam-1.png

First off, the refactoring is done.  Oh yeah.

Plus an Ansible playbook to prepare and setup NvIPAM on a basic CentOS virtual machine is now working.  The playbook installs and configures the following

  1. Installs the basic OS requirements
  2. Installs and configures Postgresql
  3. Installs and configures PowerDNS authoritative and recursor servers
  4. Installs and configures Python virutal environment
  5. Installs and configures NGINX
  6. Setups uWSGI
  7. And installs the application

And if that isn’t enough, I dumped the Swagger into a Postman file to help with continuing development agains vRealize Orchestrator (and other CMS).

The current install script is available at NvIPAM setup

The next step is to start tinkering with the vRA IPAM SDK.

NvIPAM basic refactoring done

Virtualization aware IPAM

I’ve spent the last few days refactoring the project.  The main reason for refactoring was accessing the PowerDns database.  The previous version was attempting to use two databases.  One for IPAM/CMDB and second remote one for PowerDns.  This was causing all sorts of issues.

The new model has a single shared database, containing all the tables. PowerDns tables are created manually by importing the schema from their site.  The other tables are created using flask-migrate.

My next step after adding the few remaining DNS routes is to move it up to my CentOS machine and front end the whole thing with Gunicorn or some other WSGI using Ansible.

Stay tuned.

NvIPAM plans

Project goals

NvIPAM is an IPAM solution specifically targeting VMware vRealize Automation (vRA) deployments.

During on project I had a customer with multiple networks using the same Network Profile.  The profile had several IP ranges managed by an external IPAM solution.  When the customer would request the machine at network would be assigned, but it would be assigned an IP address from the wrong pool.  The logical workaround was to have a unique network pool per network.

I think the main issue with legacy IPAM solutions is they don’t understand Virtual Networks. Most that I’ve worked with are based on VLAN’s.

NvIPAM’s network schema includes the network-id, network name, datacenter and cluster.  The intent is to use the Event Broker payload to determine the network, then grab an IP address from the pool (or pools) associated with that network.

The beta version provides the following features;

  • NSX / vSphere network keys
  • Pools bound to the network (The network JSON includes associated networks)
  • Tags for Networks and Pools
  • Basic CMDB
  • PowerDNS A/PTR record management
  • Swagger API provided by flask_restplus
  • API ONLY – No UI other than Swagger
  • Ansible playbooks to install and configure base packages
  • Postgresql database
  • PowerShell scripts to capture vSphere network information (includes NSX logical wires)

The beta version includes a basic CMDB, and DNS through PowerDNS.

Stay tuned