Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-28 Thread Matthew Treinish
On Fri, Aug 22, 2014 at 11:26:25AM -0400, Matthew Treinish wrote:
 On Fri, Aug 15, 2014 at 03:14:21PM -0400, Matthew Treinish wrote:
  Hi Everyone,
  
  So as part of splitting out common functionality from tempest into a 
  library [1]
  we need to create a new repository. Which means we have the fun task of 
  coming
  up with something to name it. I'm personally thought we should call it:
  
   - mesocyclone
  
  Which has the advantage of being a cloud/weather thing, and the name sort of
  fits because it's a precursor to a tornado. Also, it's an available 
  namespace on
  both launchpad and pypi. But there has been expressed concern that both it 
  is a
  bit on the long side (which might have 80 char line length implications) and
  it's unclear from the name what it does. 
  
  During the last QA meeting some alternatives were also brought up:
  
   - tempest-lib / lib-tempest
   - tsepmet
   - blackstorm
   - calm
   - tempit
   - integration-test-lib
  
  (although I'm not entirely sure I remember which ones were serious 
  suggestions
  or just jokes)
  
  So as a first step I figured that I'd bring it up on the ML to see if 
  anyone had
  any other suggestions. (or maybe get a consensus around one choice) I'll 
  take
  the list, check if the namespaces are available, and make a survey so that
  everyone can vote and hopefully we'll have a clear choice for a name from 
  that.
  
 
 Since the consensus was for renaming tempest and making tempest the library 
 name,
 which wasn't really feasible, I opened up a survey to poll everyone on the 
 which
 name to use:
 
 https://www.surveymonkey.com/s/RLLZRGJ
 
 The choices were taken from the initial list I posted and from the suggestions
 which people posted based on the availability of the names.
 
 I'll keep it open for about a week, or until a clear favorite emerges.
 

So I just closed the survey because one name had a commanding lead and in the
past 48hrs there was only 1 vote. The winner is tempest-lib, with 13 of 33
votes. The results from the survey are:

tempest-lib: 13
lib-tempest: 2
libtempest: 4
mesocyclone: 4
blackstorm: 4
caliban: 2
tempit: 3
pocovento: 1

-Matt Treinish


pgpW9eXHCkKfw.pgp
Description: PGP signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-22 Thread Matthew Treinish
On Fri, Aug 15, 2014 at 03:14:21PM -0400, Matthew Treinish wrote:
 Hi Everyone,
 
 So as part of splitting out common functionality from tempest into a library 
 [1]
 we need to create a new repository. Which means we have the fun task of coming
 up with something to name it. I'm personally thought we should call it:
 
  - mesocyclone
 
 Which has the advantage of being a cloud/weather thing, and the name sort of
 fits because it's a precursor to a tornado. Also, it's an available namespace 
 on
 both launchpad and pypi. But there has been expressed concern that both it is 
 a
 bit on the long side (which might have 80 char line length implications) and
 it's unclear from the name what it does. 
 
 During the last QA meeting some alternatives were also brought up:
 
  - tempest-lib / lib-tempest
  - tsepmet
  - blackstorm
  - calm
  - tempit
  - integration-test-lib
 
 (although I'm not entirely sure I remember which ones were serious suggestions
 or just jokes)
 
 So as a first step I figured that I'd bring it up on the ML to see if anyone 
 had
 any other suggestions. (or maybe get a consensus around one choice) I'll take
 the list, check if the namespaces are available, and make a survey so that
 everyone can vote and hopefully we'll have a clear choice for a name from 
 that.
 

Since the consensus was for renaming tempest and making tempest the library 
name,
which wasn't really feasible, I opened up a survey to poll everyone on the which
name to use:

https://www.surveymonkey.com/s/RLLZRGJ

The choices were taken from the initial list I posted and from the suggestions
which people posted based on the availability of the names.

I'll keep it open for about a week, or until a clear favorite emerges.

-Matt Treinish



pgpqTJ5e2Nca1.pgp
Description: PGP signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-20 Thread David Kranz

On 08/18/2014 04:57 PM, Matthew Treinish wrote:

On Sat, Aug 16, 2014 at 06:27:19PM +0200, Marc Koderer wrote:

Hi all,

Am 15.08.2014 um 23:31 schrieb Jay Pipes jaypi...@gmail.com:

I suggest that tempest should be the name of the import'able library, and that the integration 
tests themselves should be what is pulled out of the current Tempest repository, into their own repo called 
openstack-integration-tests or os-integration-tests.

why not keeping it simple:

tempest: importable test library
tempest-tests: all the test cases

Simple, obvious and clear ;)


While I agree that I like how this looks, and that it keeps things simple, I
don't think it's too feasible. The problem is the tempest namespace is already
kind of large and established. The libification effort, while reducing some of
that, doesn't eliminate it completely. So what this ends meaning is that we'll
have to do a rename for a large project in order to split certain functionality
out into a smaller library. Which really doesn't seem like the best way to do
it, because a rename is a considerable effort.

Another wrinkle to consider is that the tempest namespace on pypi is already in
use: https://pypi.python.org/pypi/Tempest so if we wanted to publish the library
as tempest we'd need to figure out what to do about that.

-Matt Treinish
Yes, I agree. Tempest is also used by Refstack, Rally, and I'm sure many 
other parts of our ecosystem. I would vote for tempest-lib as the 
library and keeping tempest to mean the same thing in the ecosystem as 
it does at present. I would also not be opposed to a different name than 
tempest-lib if it were related to its function.


 -David



___
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] [QA] Picking a Name for the Tempest Library

2014-08-18 Thread Christopher Yeoh
On Sat, 16 Aug 2014 18:27:19 +0200
Marc Koderer m...@koderer.com wrote:

 Hi all,
 
 Am 15.08.2014 um 23:31 schrieb Jay Pipes jaypi...@gmail.com:
  
  I suggest that tempest should be the name of the import'able
  library, and that the integration tests themselves should be what
  is pulled out of the current Tempest repository, into their own
  repo called openstack-integration-tests or os-integration-tests“.
 
 why not keeping it simple:
 
 tempest: importable test library
 tempest-tests: all the test cases
 
 Simple, obvious and clear ;)

+1

Chris

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


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-18 Thread Matthew Treinish
On Sat, Aug 16, 2014 at 06:27:19PM +0200, Marc Koderer wrote:
 Hi all,
 
 Am 15.08.2014 um 23:31 schrieb Jay Pipes jaypi...@gmail.com:
  
  I suggest that tempest should be the name of the import'able library, and 
  that the integration tests themselves should be what is pulled out of the 
  current Tempest repository, into their own repo called 
  openstack-integration-tests or os-integration-tests“.
 
 why not keeping it simple:
 
 tempest: importable test library
 tempest-tests: all the test cases
 
 Simple, obvious and clear ;)
 

While I agree that I like how this looks, and that it keeps things simple, I
don't think it's too feasible. The problem is the tempest namespace is already
kind of large and established. The libification effort, while reducing some of
that, doesn't eliminate it completely. So what this ends meaning is that we'll
have to do a rename for a large project in order to split certain functionality
out into a smaller library. Which really doesn't seem like the best way to do
it, because a rename is a considerable effort.

Another wrinkle to consider is that the tempest namespace on pypi is already in
use: https://pypi.python.org/pypi/Tempest so if we wanted to publish the library
as tempest we'd need to figure out what to do about that.

-Matt Treinish


pgpvUChCvCCKH.pgp
Description: PGP signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-17 Thread GHANSHYAM MANN
On Sun, Aug 17, 2014 at 1:27 AM, Marc Koderer m...@koderer.com wrote:

 Hi all,

 Am 15.08.2014 um 23:31 schrieb Jay Pipes jaypi...@gmail.com:
 
  I suggest that tempest should be the name of the import'able library,
 and that the integration tests themselves should be what is pulled out of
 the current Tempest repository, into their own repo called
 openstack-integration-tests or os-integration-tests“.

 why not keeping it simple:

 tempest: importable test library
 tempest-tests: all the test cases

 Simple, obvious and clear ;)


++. And for more clarity- importable test library could name
as tempest-lib



 Regards
 Marc

  Best,
  -jay
 
 
  ___
  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




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


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-17 Thread Ken'ichi Ohmichi
2014-08-17 1:27 GMT+09:00 Marc Koderer m...@koderer.com:
 Hi all,

 Am 15.08.2014 um 23:31 schrieb Jay Pipes jaypi...@gmail.com:

 I suggest that tempest should be the name of the import'able library, and 
 that the integration tests themselves should be what is pulled out of the 
 current Tempest repository, into their own repo called 
 openstack-integration-tests or os-integration-tests“.

 why not keeping it simple:

 tempest: importable test library
 tempest-tests: all the test cases

 Simple, obvious and clear ;)

+1 :-)

Thanks
Ken'ichi Ohmichi

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


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-16 Thread Chris Dent

On Fri, 15 Aug 2014, Jay Pipes wrote:

I suggest that tempest should be the name of the import'able library, and 
that the integration tests themselves should be what is pulled out of the 
current Tempest repository, into their own repo called 
openstack-integration-tests or os-integration-tests.


This idea is best, but if a new name is required, tempit is good because it
is a) short b) might subconsciously remind people that testing ought to
be fast(-ish).

--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent

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


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-16 Thread Adam Lawson
I like tempest-lib personally. Especially for those just starting out and
getting their feet wet.
On Aug 16, 2014 5:36 AM, Chris Dent chd...@redhat.com wrote:

 On Fri, 15 Aug 2014, Jay Pipes wrote:

  I suggest that tempest should be the name of the import'able library,
 and that the integration tests themselves should be what is pulled out of
 the current Tempest repository, into their own repo called
 openstack-integration-tests or os-integration-tests.


 This idea is best, but if a new name is required, tempit is good because it
 is a) short b) might subconsciously remind people that testing ought to
 be fast(-ish).

 --
 Chris Dent tw:@anticdent freenode:cdent
 https://tank.peermore.com/tanks/cdent

 ___
 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] [QA] Picking a Name for the Tempest Library

2014-08-16 Thread Marc Koderer
Hi all,

Am 15.08.2014 um 23:31 schrieb Jay Pipes jaypi...@gmail.com:
 
 I suggest that tempest should be the name of the import'able library, and 
 that the integration tests themselves should be what is pulled out of the 
 current Tempest repository, into their own repo called 
 openstack-integration-tests or os-integration-tests“.

why not keeping it simple:

tempest: importable test library
tempest-tests: all the test cases

Simple, obvious and clear ;)

Regards
Marc

 Best,
 -jay
 
 
 ___
 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] [QA] Picking a Name for the Tempest Library

2014-08-16 Thread Jay Pipes

On 08/16/2014 12:27 PM, Marc Koderer wrote:

Hi all,

Am 15.08.2014 um 23:31 schrieb Jay Pipes jaypi...@gmail.com:


I suggest that tempest should be the name of the import'able library, and that the 
integration tests themselves should be what is pulled out of the current Tempest repository, into their 
own repo called openstack-integration-tests or os-integration-tests“.


why not keeping it simple:

tempest: importable test library
tempest-tests: all the test cases

Simple, obvious and clear ;)


++


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


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-15 Thread Drew Fisher

What about 'teapot' (as in the idiom 'tempest in a teapot'[1])

-Drew

[1] http://en.wikipedia.org/wiki/Tempest_in_a_teapot


On 08/15/2014 01:14 PM, Matthew Treinish wrote:

Hi Everyone,

So as part of splitting out common functionality from tempest into a library [1]
we need to create a new repository. Which means we have the fun task of coming
up with something to name it. I'm personally thought we should call it:

  - mesocyclone

Which has the advantage of being a cloud/weather thing, and the name sort of
fits because it's a precursor to a tornado. Also, it's an available namespace on
both launchpad and pypi. But there has been expressed concern that both it is a
bit on the long side (which might have 80 char line length implications) and
it's unclear from the name what it does.

During the last QA meeting some alternatives were also brought up:

  - tempest-lib / lib-tempest
  - tsepmet
  - blackstorm
  - calm
  - tempit
  - integration-test-lib

(although I'm not entirely sure I remember which ones were serious suggestions
or just jokes)

So as a first step I figured that I'd bring it up on the ML to see if anyone had
any other suggestions. (or maybe get a consensus around one choice) I'll take
the list, check if the namespaces are available, and make a survey so that
everyone can vote and hopefully we'll have a clear choice for a name from that.

-Matt Treinish

[1] http://specs.openstack.org/openstack/qa-specs/specs/tempest-library.html



___
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] [QA] Picking a Name for the Tempest Library

2014-08-15 Thread Russell Bryant
On 08/15/2014 03:26 PM, Drew Fisher wrote:
 What about 'teapot' (as in the idiom 'tempest in a teapot'[1])
 
 -Drew
 
 [1] http://en.wikipedia.org/wiki/Tempest_in_a_teapot

Though in this case it'd be teacup in tempest, I think?

There's also a TCup project [1] that uses tempest.  So, you have teapot
in tempest in tcup ... and that just gets confusing.  :-)

[1] https://wiki.openstack.org/wiki/RefStack/TCup

-- 
Russell Bryant

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


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-15 Thread Valeriy Ponomaryov
OpenTest is a library for integrational and functional testing of
OpenStack cloud technology.

Sounds?


On Fri, Aug 15, 2014 at 10:48 PM, Russell Bryant rbry...@redhat.com wrote:

 On 08/15/2014 03:26 PM, Drew Fisher wrote:
  What about 'teapot' (as in the idiom 'tempest in a teapot'[1])
 
  -Drew
 
  [1] http://en.wikipedia.org/wiki/Tempest_in_a_teapot

 Though in this case it'd be teacup in tempest, I think?

 There's also a TCup project [1] that uses tempest.  So, you have teapot
 in tempest in tcup ... and that just gets confusing.  :-)

 [1] https://wiki.openstack.org/wiki/RefStack/TCup

 --
 Russell Bryant

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




-- 
Kind Regards
Valeriy Ponomaryov
QA Engineer,
Mirantis, Kharkiv, Ukraine
www.mirantis.com
vponomar...@mirantis.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-15 Thread Jay Pipes

On 08/15/2014 03:14 PM, Matthew Treinish wrote:

Hi Everyone,

So as part of splitting out common functionality from tempest into a library [1]
we need to create a new repository. Which means we have the fun task of coming
up with something to name it. I'm personally thought we should call it:

  - mesocyclone

Which has the advantage of being a cloud/weather thing, and the name sort of
fits because it's a precursor to a tornado. Also, it's an available namespace on
both launchpad and pypi. But there has been expressed concern that both it is a
bit on the long side (which might have 80 char line length implications) and
it's unclear from the name what it does.

During the last QA meeting some alternatives were also brought up:

  - tempest-lib / lib-tempest
  - tsepmet
  - blackstorm
  - calm
  - tempit
  - integration-test-lib

(although I'm not entirely sure I remember which ones were serious suggestions
or just jokes)

So as a first step I figured that I'd bring it up on the ML to see if anyone had
any other suggestions. (or maybe get a consensus around one choice) I'll take
the list, check if the namespaces are available, and make a survey so that
everyone can vote and hopefully we'll have a clear choice for a name from that.


I suggest that tempest should be the name of the import'able library, 
and that the integration tests themselves should be what is pulled out 
of the current Tempest repository, into their own repo called 
openstack-integration-tests or os-integration-tests.


Best,
-jay


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


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-15 Thread Russell Bryant


 On Aug 15, 2014, at 5:39 PM, Jay Pipes jaypi...@gmail.com wrote:
 
 On 08/15/2014 03:14 PM, Matthew Treinish wrote:
 Hi Everyone,
 
 So as part of splitting out common functionality from tempest into a library 
 [1]
 we need to create a new repository. Which means we have the fun task of 
 coming
 up with something to name it. I'm personally thought we should call it:
 
  - mesocyclone
 
 Which has the advantage of being a cloud/weather thing, and the name sort of
 fits because it's a precursor to a tornado. Also, it's an available 
 namespace on
 both launchpad and pypi. But there has been expressed concern that both it 
 is a
 bit on the long side (which might have 80 char line length implications) and
 it's unclear from the name what it does.
 
 During the last QA meeting some alternatives were also brought up:
 
  - tempest-lib / lib-tempest
  - tsepmet
  - blackstorm
  - calm
  - tempit
  - integration-test-lib
 
 (although I'm not entirely sure I remember which ones were serious 
 suggestions
 or just jokes)
 
 So as a first step I figured that I'd bring it up on the ML to see if anyone 
 had
 any other suggestions. (or maybe get a consensus around one choice) I'll take
 the list, check if the namespaces are available, and make a survey so that
 everyone can vote and hopefully we'll have a clear choice for a name from 
 that.
 
 I suggest that tempest should be the name of the import'able library, and 
 that the integration tests themselves should be what is pulled out of the 
 current Tempest repository, into their own repo called 
 openstack-integration-tests or os-integration-tests.

Ooh, I like that idea!  +1

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


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-15 Thread Dean Troyer
On Fri, Aug 15, 2014 at 4:31 PM, Jay Pipes jaypi...@gmail.com wrote:

 current Tempest repository, into their own repo called
 openstack-integration-tests or os-integration-tests.


I see what you did there...

+1 anyway

dt

Dean Troyer
dtro...@gmail.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-15 Thread Jeremy Stanley
On 2014-08-15 15:14:21 -0400 (-0400), Matthew Treinish wrote:
[...]
 So as a first step I figured that I'd bring it up on the ML to see
 if anyone had any other suggestions.
[...]

Twas a clever quibble. Here, a garment for it:

http://en.wikipedia.org/wiki/The_Tempest#Characters

Now I will believe that there are unicorns!
-- 
Jeremy Stanley

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