On 11/11/2011 06:48 PM, Angus Thomas wrote:
There's been a lot of discussion recently about the best way to
name the
components that our users interact with.
We have sought to arrive at a set of names with which are:
- Descriptive and intuitive
- Internally consistent
- Consistent with the names used by similar applications which users
might be familiar with
Given that we'll need to update the code to reflect the new names, along
with the related documentation etc., there's a great deal to be said for
actually settling on a set of names.
So, here's the list:
Image template -> Component Outline
Assembly -> Component Blueprint
Deployable -> Application Blueprint
Deployment -> Application
Pool Family/Environment -> Cloud
Pool -> Cloud Resource Zone
User Defined Realm -> Cloud Resource Cluster
Provider -> Cloud Resource Provider
Hardware Profile -> Cloud Resource Profile
Angus
Hi,
my 2 cents: much more confusing than current naming. Most confusing are:
Application - as a user I would expect real application (=program) under
this naming
Cloud - I would expect cloud provider
Cloud Resource Zone - sounds like a provider realm to me
Component Outline - 'component' is very abstract (confusing), I wouldn't
have an idea what to imagine under this name. 'Template' is clear.
Jan