RFC: Renaming
Jirka Tomasek
jtomasek at redhat.com
Thu Jan 17 14:55:29 UTC 2013
Hi,
On 01/17/2013 03:04 PM, Jiří Stránský wrote:
>>
>> Image Template -> Component Outline
>> Deployable -> AppForm Blueprint
>> Deployment -> AppForm
>> Pool Family/Environment-> Cloud Environment
>> Pool -> Resource Zone
>> Provider -> Cloud Provider
>>
>
> In terms of API - should we make it backwards compatible when the
> switch happens?
>
> My 2 cents would be that we shouldn't, since we concluded in the API
> versioning discussions that we don't want one Conductor instance to
> provide multiple versions of API. And I think only API clients to date
> are CLI and WM, which are still under construction and could be
> updated quite easily I think.
>
> If the renaming happens soon enough, we can release first generally
> usable version of CLI with the new names. (And WM probably doesn't
> care about Conductor names at all, because they have their own
> dictionary I think, so Conductor names are hidden from users?)
We are currently in discussion about whether to use the specific
provider names or one converged winged monkey term set. These are just a
matter of translation strings anyway, so name changes in Conductor are
not a big deal for Winged Monkey.
>
> J.
Jirka
More information about the aeolus-devel
mailing list