I've spent some time thinking about this, and I have a clarification.
I don't like the use of the word 'deployment', because it's not exact
enough for me. Future plans for the tuskar-ui include management of the
undercloud as well, and at that point, 'deployment role' becomes vague, as
it could
I thought we were avoiding using overcloud and undercloud within the UI?
-J
On 01/28/2014 03:04 AM, Tzu-Mainn Chen wrote:
I've spent some time thinking about this, and I have a clarification.
I don't like the use of the word 'deployment', because it's not exact
enough for me. Future plans
Yep, although the reason why - that no end-user will know what these terms mean
-
has never been entirely convincing to me. But even if we don't use the word
'overcloud', I think we should use *something*. Deployment is just so vague
that without some context, it could refer to anything.
As a
On Tue, 2014-01-28 at 10:02 -0500, Tzu-Mainn Chen wrote:
Yep, although the reason why - that no end-user will know what these terms
mean -
has never been entirely convincing to me.
Well, tenants would never see any of the Tuskar UI, so I don't think we
need worry about them. And if a deployer
On 01/28/2014 11:42 AM, Jay Pipes wrote:
On Tue, 2014-01-28 at 10:02 -0500, Tzu-Mainn Chen wrote:
Yep, although the reason why - that no end-user will know what these terms mean
-
has never been entirely convincing to me.
Well, tenants would never see any of the Tuskar UI, so I don't think
Based on this thread which didn't seem to get clear outcome, I have one
last suggestion:
* Deployment Role
It looks that it might satisfy participants of this discussion. When I
internally talked to people it got the best reactions from already
suggested terms.
Depending on your reactions
I'd argue that we should call it 'overcloud role' - at least from the modeling
point of view - since the tuskar-api calls a deployment an overcloud.
But I like the general direction of the term-renaming!
Mainn
- Original Message -
Based on this thread which didn't seem to get clear
On 2014/22/01 19:46, Tzu-Mainn Chen wrote:
- Original Message -
Oh dear user... :)
I'll step a little bit back. We need to agree if we want to name
concepts one way in the background and other way in the UI for user (did
we already agree on this point?). We all know pros and cons.
On 22 January 2014 12:05, Liz Blanchard lsure...@redhat.com wrote:
How about Instance Type? I’m looking at page 10 of the latest wireframes [1]
and I see we are using the terms “Resource”, “Node”, and “Instance” to labels
certain items. I’m pretty sure Node and Instance are different, but
On 23 January 2014 21:39, Jaromir Coufal jcou...@redhat.com wrote:
On 2014/22/01 19:46, Tzu-Mainn Chen wrote:
So... For now, the attributes are:
- Name
- Description
- Image (Image was discussed on the level of a Role, not Node Profile)
- Node Profile(s)
Future:
+ Service Specific
- Original Message -
On 23 January 2014 21:39, Jaromir Coufal jcou...@redhat.com wrote:
On 2014/22/01 19:46, Tzu-Mainn Chen wrote:
So... For now, the attributes are:
- Name
- Description
- Image (Image was discussed on the level of a Role, not Node Profile)
- Node
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we specify that we want an Overcloud with 1
Controller
and 3 Compute, Heat will create a Stack that contains 1 Controller and 3
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we specify that we want an Overcloud with 1
Controller
and 3 Compute, Heat will create a Stack that contains 1 Controller and 3
On 2014/22/01 10:00, Jaromir Coufal wrote:
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we specify that we want an Overcloud
with 1 Controller
and 3 Compute, Heat will create
Hello, Jaromir
On Wed, Jan 22, 2014 at 4:09 PM, Jaromir Coufal jcou...@redhat.com wrote:
I am leaning towards Role. We can be more specific with adding some extra
word, e.g.:
* Node Role
We use this term a lot internally for the very similar purpose, so it looks
reasonable to me.
Just my
That's a fair question; I'd argue that it *should* be resources. When we
update an overcloud deployment, it'll create additional resources.
Mainn
- Original Message -
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
- Original Message -
On 2014/22/01 10:00, Jaromir Coufal wrote:
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we specify that we want an Overcloud
with 1
On 2014/22/01 10:00, Jaromir Coufal wrote:
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we specify that we want an Overcloud
with 1 Controller
and 3
On 22/01/14 14:31, Tzu-Mainn Chen wrote:
On 2014/22/01 10:00, Jaromir Coufal wrote:
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we specify that we want an Overcloud
with 1
On Jan 22, 2014, at 4:02 AM, Jaromir Coufal jcou...@redhat.com wrote:
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we specify that we want an Overcloud with 1
On Jan 22, 2014, at 9:52 AM, Dougal Matthews dou...@redhat.com wrote:
On 22/01/14 14:31, Tzu-Mainn Chen wrote:
On 2014/22/01 10:00, Jaromir Coufal wrote:
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
On Jan 22, 2014, at 7:09 AM, Jaromir Coufal jcou...@redhat.com wrote:
On 2014/22/01 10:00, Jaromir Coufal wrote:
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we
On Jan 22, 2014, at 7:09 AM, Jaromir Coufal jcou...@redhat.com wrote:
On 2014/22/01 10:00, Jaromir Coufal wrote:
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e.,
On Jan 22, 2014, at 4:02 AM, Jaromir Coufal jcou...@redhat.com wrote:
On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
Hiya - Resource is actually a Heat term that corresponds to what we're
deploying within
the Overcloud Stack - i.e., if we specify that we want an Overcloud with 1
Oh dear user... :)
I'll step a little bit back. We need to agree if we want to name
concepts one way in the background and other way in the UI for user (did
we already agree on this point?). We all know pros and cons. And I will
still fight for users to get global infrastructure terminology
On Jan 22, 2014, at 10:53 AM, Jaromir Coufal jcou...@redhat.com wrote:
Oh dear user... :)
I'll step a little bit back. We need to agree if we want to name concepts one
way in the background and other way in the UI for user (did we already agree
on this point?). We all know pros and cons.
- Original Message -
Oh dear user... :)
I'll step a little bit back. We need to agree if we want to name
concepts one way in the background and other way in the UI for user (did
we already agree on this point?). We all know pros and cons. And I will
still fight for users to get
Thanks for starting this! Comments in-line:
Hi folks,
when I was getting feedback on wireframes and we talked about Roles,
there were various objections and not much suggestions. I would love to
call for action and think a bit about the term for concept currently
known as Role (= Resource
On 21/01/14 14:19, Jaromir Coufal wrote:
when I was getting feedback on wireframes and we talked about Roles,
there were various objections and not much suggestions. I would love to
call for action and think a bit about the term for concept currently
known as Role (= Resource Category).
This
On Jan 21, 2014, at 9:40 AM, Dougal Matthews dou...@redhat.com wrote:
On 21/01/14 14:19, Jaromir Coufal wrote:
when I was getting feedback on wireframes and we talked about Roles,
there were various objections and not much suggestions. I would love to
call for action and think a bit about
On Jan 21, 2014, at 9:40 AM, Dougal Matthews dou...@redhat.com wrote:
On 21/01/14 14:19, Jaromir Coufal wrote:
when I was getting feedback on wireframes and we talked about Roles,
there were various objections and not much suggestions. I would love to
call for action and think a bit
31 matches
Mail list logo
