Open Stack

On 01/26/2015 09:39 AM, Timur Nurlygayanov wrote:
> Hi,
Sorry for the late reply. Was on vacation.
>
> *Yaroslav*,thank you for raising the question, I realy like this 
> feature, I discussed this script with several people during the 
> OpenStack summit in Paris and heard many the same things - we need to 
> have something like this to execute tempest tests automatically for 
> validation of different production and test OpenStack clouds - it is 
> real pain to create our own separate scripts for each project / team 
> which will configure Tempest for some specific configurations / 
> installations, because tempest configuration file can be changed and 
> we will need to update our scripts.
>
> We need to discuss, first of all, what we need to change in this 
> script before this script will be merged.
> As I can see, the spec description [1] not fully meet the current 
> implementation [2] and the spec looks really general - probably we can 
> describe separate 'simple' spec for this script and just abandon the 
> current spec or update the spec to sync spec and this script?
Good idea.
>
> *David*, we found many issues with the current version of script, many 
> tempest tests failed for our custom OpenStack configurations (for 
> example, with and without Swift or Ceph) and we have our own scripts 
> which already can solve the problem. Can we join you and edit the 
> patch together? (or we can describe our ideas in the comments for the 
> patch).
I welcome edits to this patch.

  -David
>
> Also, looks like we need review from Tempest core team - they can 
> write more valuable comments and suggest some cool ideas for the 
> implementation.
>
> [1] https://review.openstack.org/#/c/94473
> [2] https://review.openstack.org/#/c/133245
>
>
> On Fri, Jan 23, 2015 at 7:12 PM, Yaroslav Lobankov 
> <ylobankov at mirantis.com <mailto:ylobankov at mirantis.com>> wrote:
>
>     Hello everyone,
>
>     I would like to discuss the following patch [1] for Tempest. I
>     think that such feature
>     as auto-configuration of Tempest would be very useful for many
>     engineers and users.
>     I have recently tried to use the script from [1]. I rebased the
>     patch on master and ran the script.
>     The script was finished without any errors and the tempest.conf
>     was generated! Of course,
>     this patch needs a lot of work, but the idea looks very cool!
>
>     Also I would like to thank David Kranz for his working on initial
>     version of the script.
>
>     Any thoughts?
>
>     [1] https://review.openstack.org/#/c/133245
>
>     Regards,
>     Yaroslav Lobankov.
>
>     __________________________________________________________________________
>     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
>
>
>
>
> -- 
>
> Timur,
> Senior QA Engineer
> OpenStack Projects
> Mirantis Inc

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