+1 As long as we're not changing API names which would break backward
compatibility, I think having clear, intuitive and consistent names and
terminology in CloudStack UI and documentation for resources is a good idea and
will be greatly improve and polish CloudStack.
Historically, the word VM
Giles, the principle of what you are saying seems good but I have a few remarks;
1. Consistency should not become a goal. Clarity is and if context
might give rise to a different understanding of the same work
consistency is detrimental to understanding
2. Metaphor is an important aspect in system
Background
Recently, I have been looking at a number of issues relating to the "first
use" / "first impression" use of cloudstack. What to people think of
Cloudstack as a new user? What is peoples perception of Cloudstack as a new
user ? How easy is it for people to understand cloudstack & its
