I agree, we should amend it to not run pluggable IPAM as the default for now.
When we decide to make it the default, the migration scripts will be needed.
John
On 5/5/15, 1:47 PM, Salvatore Orlando
sorla...@nicira.commailto:sorla...@nicira.com wrote:
Patch #153236 is introducing pluggable
On Tue, May 5, 2015 at 11:47 AM, Salvatore Orlando sorla...@nicira.com wrote:
I suggest to not enable it by default, and then consider in L-3 whether we
should do this switch.
I agree. At the least, the switch should be decoupled from that
patch. I think decoupling them before merging the
Ok, sounds good to me.
I'll switch #153236 to built-in IPAM implementation by default, and pay
additional attention on testing pluggable IPAM routines in this case.
- Pavel
On 06.05.2015 16:50, John Belamaric wrote:
I agree, we should amend it to not run pluggable IPAM as the default for
now.
Patch #153236 is introducing pluggable IPAM in the db base plugin class,
and default to it at the same time, I believe.
If the consensus is to default to IPAM driver then in order to satisfy
grenade requirements those migrations scripts should be run. There should
actually be a single script to
Hi,
During fixing failures in db_base_plugin_v2.py with new IPAM[1] I faced
to check-grenade-dsvm-neutron failures[2].
check-grenade-dsvm-neutron installs stable/kilo, creates
networks/subnets and upgrades to patched master.
So it validates that migrations passes fine and installation is works
