[openstack-dev] [tempest][refstack] Data driven testing for tempest

2015-12-22 Thread Marc Koderer
Hi folks, I have a question for the refstack team. Does the idempotent_id has to be unique for a single test? To give more context: the ddt framework [1] will generate multiple similar tests with different data set. In the current implementation it’s something like a for- loop within the test its

Re: [openstack-dev] [vitrage] Gerrit Upgrade 12/16

2015-12-17 Thread Marc Koderer
+1 I am also very confused about the new UI.. but maybe it takes time to get use to it. Regards Marc Am 17.12.2015 um 10:55 schrieb Mohan Kumar : > Eugene: +1 , Old Gerrit page was better than new one . Please fix > > On Thu, Dec 17, 2015 at 2:11 PM, Eugene Nikanorov > wrote: > I'm sorry t

[openstack-dev] [NFV][Telco] Resigning TelcoWG core team

2015-11-03 Thread Marc Koderer
Hello TelcoWG, Due to personal reasons I have to resign my TelcoWG core team membership. I will remove myself from the core reviewer group. Thanks for all the support! Regards Marc __ OpenStack Development Mailing List (no

Re: [openstack-dev] [tempest] Is there a sandbox project how to use tempest test plugin interface?

2015-09-14 Thread Marc Koderer
Am 14.09.2015 um 10:01 schrieb Lajos Katona : > Hi Matthew, > > Finally I made it working, so now I have a dummy plugin. > > Few questions, remarks: > - For me it was little hard to merge my weak knowledge from python packaging > with the documentation for tempest plugins, do you mind if I pus

[openstack-dev] [manila] [third-party][qa]: Tempest plugin concept: 3rd party CI

2015-08-03 Thread Marc Koderer
Hello Manila team, as discussed in the Manila mid-cycle we want to move forward with the tempest plugin porting. The initial patch is already up and ready for review [1]. For more details please see [2]. Please note that 3rd party CI systems may need to be adapted. All tests are currently moved f

Re: [openstack-dev] [Cinder] Implementation of ABC MetaClasses

2015-07-20 Thread Marc Koderer
. I used a script to produce this table [1]. Please let me know if you find a bug :) Regards Marc [1]: http://paste.openstack.org/show/391303/ Am 15.07.2015 um 22:26 schrieb John Griffith : > > > On Wed, Jul 8, 2015 at 12:48 AM, Marc Koderer wrote: > > Am 08.07.2015 um 01:

Re: [openstack-dev] [Cinder] Implementation of ABC MetaClasses

2015-07-07 Thread Marc Koderer
Am 08.07.2015 um 01:37 schrieb Mike Perez : > On 18:38 Jun 22, Marc Koderer wrote: >> >> Am 20.06.2015 um 01:59 schrieb John Griffith : >>> * The BaseVD represents the functionality we require from all drivers. >>> ​Yep >>> ​ >>> * The add

Re: [openstack-dev] [QA][Tempest] Proposing Jordan Pittier for Tempest Core

2015-06-23 Thread Marc Koderer
+1 Am 23.06.2015 um 02:06 schrieb GHANSHYAM MANN : > +1 :) > > On Tue, Jun 23, 2015 at 5:23 AM, Matthew Treinish > wrote: > > > Hi Everyone, > > I'd like to propose we add Jordan Pittier (jordanP) to the tempest core team. > Jordan has been a steady contributor and reviewer on tempest over

Re: [openstack-dev] [Cinder] Implementation of ABC MetaClasses

2015-06-22 Thread Marc Koderer
Am 20.06.2015 um 01:59 schrieb John Griffith : > * The BaseVD represents the functionality we require from all drivers. > ​Yep > ​ > * The additional ABC classes represent features that are not required yet. > * These are represented by classes because some features require a > bundle of method

Re: [openstack-dev] [Cinder] Implementation of ABC MetaClasses

2015-06-22 Thread Marc Koderer
Am 20.06.2015 um 02:34 schrieb Knight, Clinton : > Funny you should mention needing all of the CG methods... > > A VD group (ConsistencyGroupVD) was added to contain the 4 CG methods from > Juno. Then more CG methods were added to VolumeDriver in Kilo, but they > weren’t added to ConsistencyG

[openstack-dev] [Cinder] ABCMeta driver porting

2015-04-30 Thread Marc Koderer
Dear cinder driver maintainers, the abc driver porting bp got merged [1] and with this we need to refactor all cinder driver classes slightly. I hope we will manage to deprecate the usage of driver.VolumeDriver during Liberty. The porting should be very trivial (~ 2 LOC) in the most cases (see [2]

Re: [openstack-dev] [Manila] Two nominations for Manila Core Reviewer Team

2015-04-24 Thread Marc Koderer
[+1, +1] Am 24.04.2015 um 06:42 schrieb Ramana Raja : > +1 to both. > > - Original Message - > From: "Ben Swartzlander" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Wednesday, April 22, 2015 11:53:15 PM > Subject: [openstack-dev] [Manila] Two nominat

Re: [openstack-dev] [Openstack-operators] [Telco][NFV][infra] Review process of TelcoWG use cases

2015-02-17 Thread Marc Koderer
. Regards Marc [1]: https://review.openstack.org/#/c/155248/ [2]: https://wiki.openstack.org/wiki/How_To_Contribute Am 06.02.2015 um 12:11 schrieb Marc Koderer : > Hello everyone, > > we are currently facing the issue that we don’t know how to proceed with > our telco WG use case

[openstack-dev] [Telco][NFV][infra] Review process of TelcoWG use cases

2015-02-06 Thread Marc Koderer
Hello everyone, we are currently facing the issue that we don’t know how to proceed with our telco WG use cases. There are many of them already defined but the reviews via Etherpad doesn’t seem to work. I suggest to do a review on them with the usual OpenStack tooling. Therefore I uploaded one of

Re: [openstack-dev] [Telco][NFV] Meeting facilitator for January 28th

2015-01-27 Thread Marc Koderer
Hi Steve, I can host it. Regards Marc Am 27.01.2015 um 08:40 schrieb Steve Gordon : > Hi all, > > As mentioned in the notes from last week's meeting I am going to be in > transit during our 1400 UTC meeting this Wednesday (28th) [1]. Is anyone else > willing and able to facilitate in my abse

Re: [openstack-dev] [nova][NFV][qa][Telco] Testing NUMA, CPU pinning and large pages

2015-01-12 Thread Marc Koderer
Hi Vladik, I added the [Telco] tag. see below.. Am 12.01.2015 um 03:02 schrieb Vladik Romanovsky : > Hi everyone, > > Following Steve Gordon's email [1], regarding CI for NUMA, SR-IOV, and other > features, I'd like to start a discussion about the NUMA testing in particular. > > Recently we

Re: [openstack-dev] [Manila] Manila project use-cases

2014-12-02 Thread Marc Koderer
e not implemented. > 6) Implemented. > 7) Not implemented yet. > 8) No "cloning", but we have snapshot-approach as for volumes in cinder. Regards Marc > > Regards, > Valeriy Ponomaryov > Mirantis > > On Tue, Dec 2, 2014 at 4:22 PM, Marc Koderer wrote: > He

[openstack-dev] [Manila] Manila project use-cases

2014-12-02 Thread Marc Koderer
Hello Manila Team, We identified use cases for Manila during an internal workshop with our operators. I would like to share them with you and update the wiki [1] since it seems to be outdated. Before that I would like to gather feedback and you might help me with identifying things that aren’t im

Re: [openstack-dev] [QA][Tempest] Proposing Ghanshyam Mann for Tempest Core

2014-11-25 Thread Marc Koderer
+1 Am 22.11.2014 um 15:51 schrieb Andrea Frittoli : > +1 > > On 21 Nov 2014 18:25, "Ken1 Ohmichi" wrote: > +1 :-) > > Sent from my iPod > > On 2014/11/22, at 7:56, Christopher Yeoh wrote: > > > +1 > > > > Sent from my iPad > > > >> On 22 Nov 2014, at 4:56 am, Matthew Treinish wrote: > >> >

Re: [openstack-dev] [Telco] [NFV] [Heat] Telco Orchestration

2014-11-25 Thread Marc Koderer
Hi Angus, Am 25.11.2014 um 12:48 schrieb Angus Salkeld : > On Tue, Nov 25, 2014 at 7:27 PM, Marc Koderer wrote: > Hi all, > > as discussed during our summit sessions we would like to expand the scope > of the Telco WG (aka OpenStack NFV group) and start working > on the o

[openstack-dev] [Telco] [NFV] [Heat] Telco Orchestration

2014-11-25 Thread Marc Koderer
Hi all, as discussed during our summit sessions we would like to expand the scope of the Telco WG (aka OpenStack NFV group) and start working on the orchestration topic (ETSI MANO). Therefore we started with an etherpad [1] to collect ideas, use-cases and requirements. Goal is to discuss this d

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 : > > 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