If you have custom data you want to keep for your driver, you should create your own database tables to track that information. For example, the reference driver creates its own tables to track its data in ipam* tables.
John On Nov 4, 2015, at 3:46 PM, Shraddha Pandhe <spandhe.openst...@gmail.com<mailto:spandhe.openst...@gmail.com>> wrote: Hi folks, I have a small question/suggestion about IPAM. With IPAM, we are allowing users to have their own IPAM drivers so that they can manage IP allocation. The problem is, the new ipam tables in the database have the same columns as the old tables. So, as a user, if I want to have my own logic for ip allocation, I can't actually get any help from the database. Whereas, if we had an arbitrary json blob in the ipam tables, I could put any useful information/tags there, that can help me for allocation. Does this make sense? e.g. If I want to create multiple allocation pools in a subnet and use them for different purposes, I would need some sort of tag for each allocation pool for identification. Right now, there is no scope for doing something like that. Any thoughts? If there are any other way to solve the problem, please let me know __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
