Ok. If don't have more or less working solution by the beginning of next
week, let's start a second track to consume ML2 part only as a mitigation
plan.
On Tue, Jun 17, 2014 at 2:29 AM, Dmitry Borodaenko wrote:
> Correction/clarification: call tomorrow is about
> multiple-cluster-networks, and
Correction/clarification: call tomorrow is about
multiple-cluster-networks, and it was a bad idea on my part to try to
hijack that with neutron-ml2 discussion. Lets not do that and continue
discussing the blueprint spec in gerrit, and hopefully by Thursday
Andrew will have enough code out there to
Mike,
We discussed this in our team syncup meeting earlier today. The
agreement was that HA is the biggest risk with the current approach.
However, keeping our current state of divergence from upstream (and
even exagerrating it further) leaves us with a huge technical debt, so
the tradeoff between
Fuelers, Andrew,
I've talked to Sergey V. today about ML2 support in Fuel. Our current
approach [1] is to port upstream puppet module for Neutron which has
support of ML2, however our Neutron module is significantly diverged from
upstream one (at least for Neutron HA deployment capabilities), as fa
