On Thu, Apr 17, 2014 at 8:07 PM, Eugene Nikanorov
wrote:
> Hi Zang,
>
> 1.
>> so the tags is totally useless, and I suggest replace tags by provider
>> name/uuid. It is much more straightforward and easier.
> Funny thing is that the goal of flavor framework is directly opposite.
> We need to hide
Hi Zang,
1.
> so the tags is totally useless, and I suggest replace tags by provider
> name/uuid. It is much more straightforward and easier.
Funny thing is that the goal of flavor framework is directly opposite.
We need to hide provider/vendor name. Ssl vpn or ipsec could be implemented
by differ
Hi Eugene:
I have several questions
1. I wonder if tags is really needed. for example, if I want a ipsec
vpn, I'll define a flavor which is directly refer to ipsec provider.
If using current design, almost all users will end up creating flavors
like this:
ipsec tags=[ipsec]
sslvpn tags=[sslvpn]
Hi folks,
In Icehouse there were attempts to apply Provider Framework ('Service Type
Framework') approach to VPN and Firewall services.
Initially Provider Framework was created as a simplistic approach of
allowing user to choose service implementation.
That approach definitely didn't account for p
