Timur, I have reviewed these specs, looks very promising. I want to participate in > implementation.
Nice! cause there will be a lot of work Best regards, Boris Pavlovic On Tue, Oct 28, 2014 at 1:14 AM, Timur Nurlygayanov < tnurlygaya...@mirantis.com> wrote: > Thank you, Rocky! > > I have reviewed these specs, looks very promising. I want to participate > in implementation. > > On Sat, Oct 25, 2014 at 3:49 AM, Rochelle.RochelleGrober < > rochelle.gro...@huawei.com> wrote: > >> Hi, Timur. >> >> >> >> Check out [1]. Boris Pavlovic has been working towards what you want >> for more than a full release cycle. There are still major issues to be >> conquered, but having something that gets us part of the way there and can >> identify what can’t be determined so that the humans have only a subset to >> work out would be a great first step. >> >> >> >> There are also other reviews out there that need to come together to >> really make this work. And projects that would be the better for it >> (Refstack and Rally). These are [2] allowing Tempest tests to run as >> non-admin, [3] making Tempest pluggable, [4] refactoring the client manager >> to be more flexible. >> >> >> >> I think some others may have merged already. The bottom line is to >> refactor tempest such that there is a test server with the necessary tools >> and components to make it work, and a tempest lib such that writing tests >> can benefit from common procedures. >> >> >> >> Enjoy the reading. >> >> >> >> --Rocky >> >> >> >> >> >> [1] https://review.openstack.org/#/c/94473/ >> >> [2] https://review.openstack.org/#/c/86967/ >> >> [3] https://review.openstack.org/#/c/89322/ >> >> [4] https://review.openstack.org/#/c/92804/ >> >> >> >> >> >> *From:* Timur Nurlygayanov [mailto:tnurlygaya...@mirantis.com] >> *Sent:* Friday, October 24, 2014 4:05 AM >> *To:* OpenStack Development Mailing List >> *Subject:* [openstack-dev] [tempest] [devstack] Generic scripts for >> Tempest configuration >> >> >> >> Hi all, >> >> we are using Tempest tests to verify every changes in different OpenStack >> components and we have scripts in devstack, which allow to configure >> Tempest. >> >> We want to use Tempest tests to verify different clouds, not only >> installed with devstack and to do this we need to configure Tempest >> manually (or with some no-generic scripts, which allow to configure tempest >> for specific lab configuration). >> >> Looks like we can improve these scripts for configuration of the Tempest, >> which we have in devstack repository now and create generic scripts for >> Tempest, which can be used by devstack scripts or manually, to configure >> Tempest for any private/public OpenStack clouds. These scripts should allow >> to easily configure Tempest: user should provide only Keystone endpoint and >> logins/passwords, other parameters can be optional and can be configured >> automatically. >> >> >> >> The idea is to have the generic scripts, which will allow to easily >> configure Tempest from-the-box, without deep inspection of lab >> configuration (but with the ability to change optional parameters too, if >> it is required). >> >> >> -- >> >> >> >> Timur, >> >> Senior QA Engineer >> >> OpenStack Projects >> >> Mirantis Inc >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > > -- > > Timur, > Senior QA Engineer > OpenStack Projects > Mirantis Inc > > _______________________________________________ > 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