* I don't think this is the right time to get into performance and scale
discussions; on the implementation side, it would be good for me to
understand how neutron will be able to undeploy resources - for which it
should use a driver which unfortunately has been removed. Are we caching
drivers
More stuff from me.
Salvatore
On 31 July 2013 10:36, Eugene Nikanorov enikano...@mirantis.com wrote:
* I don't think this is the right time to get into performance and scale
discussions; on the implementation side, it would be good for me to
understand how neutron will be able to undeploy
After this discussion I'm thinking about not adding comprehensive handling
for provider removing case at all.
Probably we'll need to document desired workflow and postpone cleanup
feature until use cases are more clear.
I like the idea of leaving resource in ERROR state.
However, If we're not
It is my personal opinion that there is no necessary condition between
'having the possibility of leaving a resource without service provider' and
'API users want to create resources without service providers'.
While being able to change the 'provider' associated with a resource is a
reasonable
Salvatore, thanks for your feedback.
Let me comment on some of your statements
* The possibility Eugene describes in his post - a service provider being
deleted - is probably not a 'regular' use case, but more the consequence of
a potentially error-prone operation.*
Nachi initially raised a
Hi folks,
Recently we've been discussing with Nachi Ueno some specific use case of
deployments with multiple providers for particular advanced service.
What If admin wants to remove certain provider from configuration file?
The following handling was proposed:
1) Before restarting neutron-server
