RFC - API: Update of Provider Type

Richard Su rwsu at redhat.com
Thu Jan 10 01:51:41 UTC 2013


On 01/08/2013 08:01 AM, Petr Blaho wrote:
> Hi all,
>
> after some good points during sprint planning session
> I want to know every opinion about wether implement update action
> for Provider Type resource or not.
>
> The point is that updating Provider Type will mean changing of dependent
> Providers too. We cannot predict how will API users modify Provider
> Type. Change of Credential Definitions for that Provider Type could mean
> that all Providers of that Provider Type should be modified/recreated.
> And that is a problem.
>
> To make a better idea why user should use Provider Type API imagine
> a company with proprietary solution for managing VMs. They have
> Deltacloud Driver for their solution and they need to tell Conductor
> that Deltacloud has this Provider Type and how to work with it (which
> Credential Definitions it has ...)
>
> So, do you see a reason why build update action for Provider Type and
> which issues should be addressed w/r/t modifying Provider Type -
> Providers associations? Or should I work on other things and save time
> implementing feature which probably will have no use at all?
>
> IMHO I cannot imagine scenario where user needs to modify Provider Type
> but maybe I am wrong.
>
> --
> Petr Blaho, pblaho at redhat.com
> Software Engineer, CloudForms

Credential definition changes are probably infrequent. So yeah, I think 
updates are a low priority. We should focus on other areas and come back 
to this once other pieces of the API are done.


More information about the aeolus-devel mailing list