Open Stack

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 different vendors and we don't want to expose vendor or provider name.
Instead, we may expose the type or other capabilities. It may be a
coincidence the names 'sslvpn' and 'ipsec' map to both types of vpn and the
provider names,
but there are plenty of other cases (for other services) where additional
parameters are needed.

2.
> I don't know why give user the ability to name the provider, and the name
is totally
> nonsense, it hasn't been referred anywhere.
A user isn't given an ability to name providers. Only deployer/cloud admin
has a right to do that.
Right now, when service implementation is chosen by the user directly by
specifying the provider he/she wants, provider name is returned when you
list providers.
It is also used in REST call dispatching.

We definitely will not expose anything like driver aliases to the user as
it is a particular implementation detail.

Thanks,
Eugene.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140417/2005b5c1/attachment.html>