NvIPAM basic refactoring done

NvIPAM
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.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s