Open Stack

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 <graham.hayes at hpe.com
> <mailto:graham.hayes at hpe.com>> wrote:
>
>     On 04/04/2016 16:36, Jordan Pittier wrote:
>     >
>     > On Mon, Apr 4, 2016 at 5:01 PM, Hayes, Graham
>     <graham.hayes at hpe.com <mailto:graham.hayes at hpe.com>
>     > <mailto:graham.hayes at hpe.com <mailto:graham.hayes at hpe.com>>> 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&i=nope&files=setup.cfg&repos=
>     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-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     >   
>      <http://OpenStack-dev-request@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-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160405/e2cc18ab/attachment.html>