Re: [openstack-dev] [Octavia] [Tempest] Tempest tests using tempest-plugin

[Andrea Frittoli]

All the code that is in tempest-lib is stable interface that can be
consumed safely.
The code in tempest instead does not provide a guaranteed stable interface,
as it was not originally meant for external consumption.
So while you can import it, it may change without warning (i.e. with no new
tempest tag), and break your plugin.

In Mitaka we have an ongoing effort in the QA team to make more parts of
the tempest core framework as stable interfaces.
Service clients, client managers, credentials providers are all part of
this effort.

What part of tempest are you looking to import? If it's something that is
planned to become stable, you could start importing the current code, and
you may have to adapt your plugin code one the interface becomes stable.
And surely you are very welcome to help in the process of turning the part
of tempest you need in your plugin into a stable interface.

andrea

On Fri, Feb 19, 2016 at 10:26 PM Michael Johnson 
wrote:

> I really do not want to see tempest code copied into the Octavia
> repository.  We cannot keep them in sync and maintain the tests that
> way.  It has been a recurring problem with neutron-lbaas that we are
> trying to get back out of[1], so I really do not want to repeat that
> with Octavia.
>
> [1] https://review.openstack.org/#/c/273817/
>
> Michael
>
> On Thu, Feb 18, 2016 at 10:53 PM, Madhusudhan Kandadai
>  wrote:
> > Hi,
> >
> > We are trying to implement tempest tests for Octavia using
> tempest-plugin. I
> > am wondering whether we can import *tempest* common files and use them
> as a
> > base to support Octavia tempest tests rather than copying everything in
> > Octavia tree. I am in favor of importing files directly from tempest to
> > follow tempest structure. If this is not permissible to import from
> tempest
> > directly, do we need to propose any common files in tempest_lib, so we
> can
> > import it from tempest_lib instead? I wanted to check with other for
> > suggestions.
> >
> > Thanks,
> > Madhu
> >
> >
> __
> > 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] [Octavia] [Tempest] Tempest tests using tempest-plugin

[Michael Johnson]

I really do not want to see tempest code copied into the Octavia
repository.  We cannot keep them in sync and maintain the tests that
way.  It has been a recurring problem with neutron-lbaas that we are
trying to get back out of[1], so I really do not want to repeat that
with Octavia.

[1] https://review.openstack.org/#/c/273817/

Michael

On Thu, Feb 18, 2016 at 10:53 PM, Madhusudhan Kandadai
 wrote:
> Hi,
>
> We are trying to implement tempest tests for Octavia using tempest-plugin. I
> am wondering whether we can import *tempest* common files and use them as a
> base to support Octavia tempest tests rather than copying everything in
> Octavia tree. I am in favor of importing files directly from tempest to
> follow tempest structure. If this is not permissible to import from tempest
> directly, do we need to propose any common files in tempest_lib, so we can
> import it from tempest_lib instead? I wanted to check with other for
> suggestions.
>
> Thanks,
> Madhu
>
> __
> 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