Re: [openstack-dev] [Tuskar] Tuskar Names Clarification Unification

2013-09-17 Thread Tomas Sedovic

On 09/17/2013 04:17 AM, Jaromir Coufal wrote:


On 2013/16/09 15:11, Tomas Sedovic wrote:

On 09/16/2013 05:50 PM, Jaromir Coufal wrote:

Hi,

after few days of gathering information, it looks that no more new ideas
appear there, so let's take the last round of voting for names which you
prefer. It's important for us to get on the same page.

https://etherpad.openstack.org/tuskar-naming

Thanks guys
-- Jarda


Thanks Jarda,

I was thinking we could do the voting during the weekly IRC meeting
(the bot has some cool voting capabilities).

Unfortunately, I've fallen ill and chances are I won't be able to
drive the meeting. If you folks want to self-organise and start the
vote, you have my blessing.

Otherwise, shall we do it on the IRC meeting after that?

T.

Sure Thomas, thanks for following the thread. We can try to
self-organize there, I might try to run it, just can you point me to bot
commands?

Get well soon


Thanks.

Here's the manual:

http://meetbot.debian.net/Manual.html

The most important commands are:

#startmeeting tuskar

#topic an item from the agenda

#info an item to be listed in the meeting minutes

#agreed whatever the people agreed to do

#action nick an action the person is supposed to take

#endmeeting

If you scroll to the last section of the Heat meeting page, they have 
some instructions on running the meetings:


https://wiki.openstack.org/wiki/Meetings/HeatAgenda



-- Jarda

[snip]



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Tuskar] Tuskar Names Clarification Unification

2013-09-17 Thread Tomas Sedovic

On 09/17/2013 04:53 AM, Mike Spreitzer wrote:


  From: Jaromir Coufal jcou...@redhat.com
  To: openstack-dev@lists.openstack.org,
  Date: 09/16/2013 11:51 AM
  Subject: Re: [openstack-dev] [Tuskar] Tuskar Names Clarification 
Unification
 
  Hi,
 
  after few days of gathering information, it looks that no more new
  ideas appear there, so let's take the last round of voting for names
  which you prefer. It's important for us to get on the same page.

I am concerned that the proposals around the term 'rack' do not
recognize that there might be more than one layer in the organization.

Is it more important to get appropriately abstract and generic terms, or
is the desire to match common concrete terms?



So our thinking here is to work with a grouping of nodes in the same 
physical location, the same subnet and ideally the same hardware 
configuration.


This can be a physical rack, or what I believe you call a chassis (a 
group of servers inside the rack).


Regarding layers, I see two physical layers in play: a rack and a 
chassis. Could there be more?


The idea right now is that the Tuskar admins would choose their 
preferred granularity and just work on that level.


Do you think that's not sufficient?

T.


Regards,
Mike


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Tuskar] Tuskar Names Clarification Unification

2013-09-16 Thread Jaromir Coufal

Hi,

after few days of gathering information, it looks that no more new ideas 
appear there, so let's take the last round of voting for names which you 
prefer. It's important for us to get on the same page.


https://etherpad.openstack.org/tuskar-naming

Thanks guys
-- Jarda


On 2013/12/09 11:20, Jaromir Coufal wrote:

Hello everybody,

I just started and etherped with various names of concepts in Tuskar. 
It is important to get all of us on the same page, so the usage and 
discussions around Tuskar concepts are clear and easy to use (also for 
users, not just contributors!).


https://etherpad.openstack.org/tuskar-naming

Keep in mind, that we will use these names in API, CLI and UI as well, 
so they should be as descriptive as possible and not very long or 
difficult though.


Etherpad is not the best tool for mark up, but I did my best. Each 
concept which needs name is bold and is followed with bunch of bullets 
- description, suggestion of names, plus discussion under each 
suggestion, why yes or not.


Name suggestions are in underlined italic font.

Feel free to add  update  discuss anything in the document, because 
I might have forgotten bunch of stuff.


Thank you all and follow the etherpad :)
-- Jarda




___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Tuskar] Tuskar Names Clarification Unification

2013-09-16 Thread Tomas Sedovic

On 09/16/2013 05:50 PM, Jaromir Coufal wrote:

Hi,

after few days of gathering information, it looks that no more new ideas
appear there, so let's take the last round of voting for names which you
prefer. It's important for us to get on the same page.

https://etherpad.openstack.org/tuskar-naming

Thanks guys
-- Jarda


Thanks Jarda,

I was thinking we could do the voting during the weekly IRC meeting (the 
bot has some cool voting capabilities).


Unfortunately, I've fallen ill and chances are I won't be able to drive 
the meeting. If you folks want to self-organise and start the vote, you 
have my blessing.


Otherwise, shall we do it on the IRC meeting after that?

T.




On 2013/12/09 11:20, Jaromir Coufal wrote:

Hello everybody,

I just started and etherped with various names of concepts in Tuskar.
It is important to get all of us on the same page, so the usage and
discussions around Tuskar concepts are clear and easy to use (also for
users, not just contributors!).

https://etherpad.openstack.org/tuskar-naming

Keep in mind, that we will use these names in API, CLI and UI as well,
so they should be as descriptive as possible and not very long or
difficult though.

Etherpad is not the best tool for mark up, but I did my best. Each
concept which needs name is bold and is followed with bunch of bullets
- description, suggestion of names, plus discussion under each
suggestion, why yes or not.

Name suggestions are in underlined italic font.

Feel free to add  update  discuss anything in the document, because
I might have forgotten bunch of stuff.

Thank you all and follow the etherpad :)
-- Jarda




___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Tuskar] Tuskar Names Clarification Unification

2013-09-16 Thread Mike Spreitzer
 From: Jaromir Coufal jcou...@redhat.com
 To: openstack-dev@lists.openstack.org, 
 Date: 09/16/2013 11:51 AM
 Subject: Re: [openstack-dev] [Tuskar] Tuskar Names Clarification  
Unification
 
 Hi,
 
 after few days of gathering information, it looks that no more new 
 ideas appear there, so let's take the last round of voting for names
 which you prefer. It's important for us to get on the same page.

I am concerned that the proposals around the term 'rack' do not recognize 
that there might be more than one layer in the organization.

Is it more important to get appropriately abstract and generic terms, or 
is the desire to match common concrete terms?

Regards,
Mike___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [Tuskar] Tuskar Names Clarification Unification

2013-09-12 Thread Jaromir Coufal

Hello everybody,

I just started and etherped with various names of concepts in Tuskar. It 
is important to get all of us on the same page, so the usage and 
discussions around Tuskar concepts are clear and easy to use (also for 
users, not just contributors!).


https://etherpad.openstack.org/tuskar-naming

Keep in mind, that we will use these names in API, CLI and UI as well, 
so they should be as descriptive as possible and not very long or 
difficult though.


Etherpad is not the best tool for mark up, but I did my best. Each 
concept which needs name is bold and is followed with bunch of bullets - 
description, suggestion of names, plus discussion under each suggestion, 
why yes or not.


Name suggestions are in underlined italic font.

Feel free to add  update  discuss anything in the document, because I 
might have forgotten bunch of stuff.


Thank you all and follow the etherpad :)
-- Jarda


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev