I think the option 1) is a better choice. Since:
1. The api and agent talk through RPC. So it is unnecessarily to have both
the api and agent service on the same node. Separate composable service is
more appropriate here.
2. In the l2gw_plugin.ini file, it suggests that the service_provider could
On Thu, 2017-04-06 at 13:07 +0200, Ricardo Noriega De Soto wrote:
> Hi owls!
>
> This is something that I've been discussing in the IRC channel but
> still I
> think we should define a consistent way of integrating services which
> support different backends. In this case, I'm refering to BGPVPN
I think the answer here should be if we want to define environment files
as a whole
“With all the information required to deploy something functional” or
composing them like
a LEGO (which might not work separately).
I don't have a strong opinion about it, but I'm inclined to use them as
Hi owls!
This is something that I've been discussing in the IRC channel but still I
think we should define a consistent way of integrating services which
support different backends. In this case, I'm refering to BGPVPN and L2GW
Neutron services, but it could be applied to any other type of
