Re: [openstack-dev] [Designate] Tempest Tests - in-repo or separate

2016-04-05 Thread Matthew Treinish 
On Tue, Apr 05, 2016 at 01:37:21PM +0100, Kiall Mac Innes wrote:
> Agreed on a separate repo.
> 
> I'm honestly a little unsure how in-service-repo would ever work long
> term, given that tempest's requirements will match master, and may
> not be compatible with N releases ago's $service requirements..
> 
> Thoughts on how that might work, or is it just that no service has had
> an in-repo plugin for long enough to hit this yet?

So this has come up, the plugin interface has been around for a little over a
cycle so some projects have crossed a release boundary already. Although, most
projects don't seem to worry about this and either don't run the plugin on
stable or just haven't thought about it yet. The solution I've been working with
for ironic is to install the project from master inside the tempest tox venv.
I've got a patch up to add the machinery to devstack-gate to enable this:

https://review.openstack.org/297446

But, I agree having the plugin be a separate python package makes this much
easier.

-Matt Treinish

> 
> On 04/04/16 17:16, Andrea Frittoli wrote:
> > I look forward to the first (as far as I know) tempest plugin for a
> > service in its own repo! :)
> >
> >
> > On Mon, Apr 4, 2016 at 4:49 PM Hayes, Graham  > > wrote:
> >
> > On 04/04/2016 16:36, Jordan Pittier wrote:
> > >
> > > On Mon, Apr 4, 2016 at 5:01 PM, Hayes, Graham
> > 
> > > >> wrote:
> > >
> > > As we have started to move to a tempest plugin for our
> > functional test
> > > suite, we have 2 choices about where it lives.
> > >
> > > 1 - In repo (as we have [0] currently)
> > > 2 - In a repo of its own (something like
> > openstack/designate-tempest)
> > >
> > > There are several advantages to a separate repo:
> > >
> > > * It will force us to make API changes compatable
> > > * * This could cause us to be slower at merging changes [1]
> > > * It allows us to be branchless (like tempest is)
> > > * It can be its own installable package, and a (much)
> > shorter list
> > > of requirements.
> > >
> > > I am not a Designate contributor, but as a Tempest contributor we
> > > recommend to use a separate repo. See
> > >
> > 
> > http://docs.openstack.org/developer/tempest/plugin.html#standalone-plugin-vs-in-repo-plugin
> > > for more details.
> >
> > Yeap - that was one of the reasons I will leaning towards the separate
> > repo. The only thing stopping us was that I cannot see any other
> > project
> > who does it [2]
> >
> > We just had a quick discussion in IRC[3] and we are going to go with
> > the separate repo anyway.
> >
> > 2 -
> > 
> > http://codesearch.openstack.org/?q=%5Etempest=nope=setup.cfg=
> > 3 -
> > 
> > http://eavesdrop.openstack.org/irclogs/%23openstack-dns/%23openstack-dns.2016-04-04.log.html#t2016-04-04T15:05:38
> >
> >
> > > If everyone is OK with a separate repo, I will go ahead and
> > start the
> > > creation process.
> > >
> > > Thanks
> > >
> > > - Graham
> > >
> > >
> > > 0 - https://review.openstack.org/283511
> > > 1 -
> > >   
> >  
> > http://docs.openstack.org/developer/tempest/HACKING.html#branchless-tempest-considerations
> > >
> > >   
> >  
> > __
> > > OpenStack Development Mailing List (not for usage questions)
> > > Unsubscribe:
> > >   
> >  openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > 
> > >   
> >  
> > >   
> >  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> > >
> >
> >
> > 
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > 
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:

Re: [openstack-dev] [Designate] Tempest Tests - in-repo or separate

2016-04-05 Thread Kiall Mac Innes 
Agreed on a separate repo.

I'm honestly a little unsure how in-service-repo would ever work long
term, given that tempest's requirements will match master, and may
not be compatible with N releases ago's $service requirements..

Thoughts on how that might work, or is it just that no service has had
an in-repo plugin for long enough to hit this yet?

Thanks,
Kiall

On 04/04/16 17:16, Andrea Frittoli wrote:
> I look forward to the first (as far as I know) tempest plugin for a
> service in its own repo! :)
>
>
> On Mon, Apr 4, 2016 at 4:49 PM Hayes, Graham  > wrote:
>
> On 04/04/2016 16:36, Jordan Pittier wrote:
> >
> > On Mon, Apr 4, 2016 at 5:01 PM, Hayes, Graham
> 
> > >> wrote:
> >
> > As we have started to move to a tempest plugin for our
> functional test
> > suite, we have 2 choices about where it lives.
> >
> > 1 - In repo (as we have [0] currently)
> > 2 - In a repo of its own (something like
> openstack/designate-tempest)
> >
> > There are several advantages to a separate repo:
> >
> > * It will force us to make API changes compatable
> > * * This could cause us to be slower at merging changes [1]
> > * It allows us to be branchless (like tempest is)
> > * It can be its own installable package, and a (much)
> shorter list
> > of requirements.
> >
> > I am not a Designate contributor, but as a Tempest contributor we
> > recommend to use a separate repo. See
> >
> 
> http://docs.openstack.org/developer/tempest/plugin.html#standalone-plugin-vs-in-repo-plugin
> > for more details.
>
> Yeap - that was one of the reasons I will leaning towards the separate
> repo. The only thing stopping us was that I cannot see any other
> project
> who does it [2]
>
> We just had a quick discussion in IRC[3] and we are going to go with
> the separate repo anyway.
>
> 2 -
> 
> http://codesearch.openstack.org/?q=%5Etempest=nope=setup.cfg=
> 3 -
> 
> http://eavesdrop.openstack.org/irclogs/%23openstack-dns/%23openstack-dns.2016-04-04.log.html#t2016-04-04T15:05:38
>
>
> > If everyone is OK with a separate repo, I will go ahead and
> start the
> > creation process.
> >
> > Thanks
> >
> > - Graham
> >
> >
> > 0 - https://review.openstack.org/283511
> > 1 -
> >   
>  
> http://docs.openstack.org/developer/tempest/HACKING.html#branchless-tempest-considerations
> >
> >   
>  
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> >   
>  openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 
> >   
>  
> >   
>  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Designate] Tempest Tests - in-repo or separate

2016-04-04 Thread Andrea Frittoli 
I look forward to the first (as far as I know) tempest plugin for a service
in its own repo! :)


On Mon, Apr 4, 2016 at 4:49 PM Hayes, Graham  wrote:

> On 04/04/2016 16:36, Jordan Pittier wrote:
> >
> > On Mon, Apr 4, 2016 at 5:01 PM, Hayes, Graham  > > wrote:
> >
> > As we have started to move to a tempest plugin for our functional
> test
> > suite, we have 2 choices about where it lives.
> >
> > 1 - In repo (as we have [0] currently)
> > 2 - In a repo of its own (something like openstack/designate-tempest)
> >
> > There are several advantages to a separate repo:
> >
> > * It will force us to make API changes compatable
> > * * This could cause us to be slower at merging changes [1]
> > * It allows us to be branchless (like tempest is)
> > * It can be its own installable package, and a (much) shorter list
> > of requirements.
> >
> > I am not a Designate contributor, but as a Tempest contributor we
> > recommend to use a separate repo. See
> >
> http://docs.openstack.org/developer/tempest/plugin.html#standalone-plugin-vs-in-repo-plugin
> > for more details.
>
> Yeap - that was one of the reasons I will leaning towards the separate
> repo. The only thing stopping us was that I cannot see any other project
> who does it [2]
>
> We just had a quick discussion in IRC[3] and we are going to go with
> the separate repo anyway.
>
> 2 -
> http://codesearch.openstack.org/?q=%5Etempest=nope=setup.cfg=
> 3 -
>
> http://eavesdrop.openstack.org/irclogs/%23openstack-dns/%23openstack-dns.2016-04-04.log.html#t2016-04-04T15:05:38
>
>
> > If everyone is OK with a separate repo, I will go ahead and start the
> > creation process.
> >
> > Thanks
> >
> > - Graham
> >
> >
> > 0 - https://review.openstack.org/283511
> > 1 -
> >
> http://docs.openstack.org/developer/tempest/HACKING.html#branchless-tempest-considerations
> >
> >
>  __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > <
> http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Designate] Tempest Tests - in-repo or separate

2016-04-04 Thread Hayes, Graham 
On 04/04/2016 16:36, Jordan Pittier wrote:
>
> On Mon, Apr 4, 2016 at 5:01 PM, Hayes, Graham  > wrote:
>
> As we have started to move to a tempest plugin for our functional test
> suite, we have 2 choices about where it lives.
>
> 1 - In repo (as we have [0] currently)
> 2 - In a repo of its own (something like openstack/designate-tempest)
>
> There are several advantages to a separate repo:
>
> * It will force us to make API changes compatable
> * * This could cause us to be slower at merging changes [1]
> * It allows us to be branchless (like tempest is)
> * It can be its own installable package, and a (much) shorter list
> of requirements.
>
> I am not a Designate contributor, but as a Tempest contributor we
> recommend to use a separate repo. See
> http://docs.openstack.org/developer/tempest/plugin.html#standalone-plugin-vs-in-repo-plugin
> for more details.

Yeap - that was one of the reasons I will leaning towards the separate
repo. The only thing stopping us was that I cannot see any other project
who does it [2]

We just had a quick discussion in IRC[3] and we are going to go with
the separate repo anyway.

2 - 
http://codesearch.openstack.org/?q=%5Etempest=nope=setup.cfg=
3 - 
http://eavesdrop.openstack.org/irclogs/%23openstack-dns/%23openstack-dns.2016-04-04.log.html#t2016-04-04T15:05:38


> If everyone is OK with a separate repo, I will go ahead and start the
> creation process.
>
> Thanks
>
> - Graham
>
>
> 0 - https://review.openstack.org/283511
> 1 -
> 
> http://docs.openstack.org/developer/tempest/HACKING.html#branchless-tempest-considerations
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Designate] Tempest Tests - in-repo or separate

2016-04-04 Thread Jordan Pittier 
On Mon, Apr 4, 2016 at 5:01 PM, Hayes, Graham  wrote:

> As we have started to move to a tempest plugin for our functional test
> suite, we have 2 choices about where it lives.
>
> 1 - In repo (as we have [0] currently)
> 2 - In a repo of its own (something like openstack/designate-tempest)
>
> There are several advantages to a separate repo:
>
> * It will force us to make API changes compatable
> * * This could cause us to be slower at merging changes [1]
> * It allows us to be branchless (like tempest is)
> * It can be its own installable package, and a (much) shorter list
>of requirements.
>
>
I am not a Designate contributor, but as a Tempest contributor we recommend
to use a separate repo. See
http://docs.openstack.org/developer/tempest/plugin.html#standalone-plugin-vs-in-repo-plugin
for more details.

If everyone is OK with a separate repo, I will go ahead and start the
> creation process.
>
> Thanks
>
> - Graham
>
>
> 0 - https://review.openstack.org/283511
> 1 -
>
> http://docs.openstack.org/developer/tempest/HACKING.html#branchless-tempest-considerations
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Designate] Tempest Tests - in-repo or separate

2016-04-04 Thread Hayes, Graham 
As we have started to move to a tempest plugin for our functional test
suite, we have 2 choices about where it lives.

1 - In repo (as we have [0] currently)
2 - In a repo of its own (something like openstack/designate-tempest)

There are several advantages to a separate repo:

* It will force us to make API changes compatable
* * This could cause us to be slower at merging changes [1]
* It allows us to be branchless (like tempest is)
* It can be its own installable package, and a (much) shorter list
   of requirements.

If everyone is OK with a separate repo, I will go ahead and start the
creation process.

Thanks

- Graham


0 - https://review.openstack.org/283511
1 - 
http://docs.openstack.org/developer/tempest/HACKING.html#branchless-tempest-considerations

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev