[openstack-dev] [QA][Tempest] Gap analysis for using Tempest in production environments
masayuki.igawa at gmail.com
Sat Nov 1 14:18:01 UTC 2014
Thank you for your reply and adding interesting topics! I'll look at it.
> By the way, could you please add the link to etherpad  to the event description , it will help to find the correct link from mobile devices.
Actually, I don't have the permission to add/change the description on
I think Matthew(mtreinish) can do it.
On Sat, Nov 1, 2014 at 6:21 PM, Timur Nurlygayanov
<tnurlygayanov at mirantis.com> wrote:
> it is the really important design session, because we need to break the ice
> and implement several good ideas, which we have.
> The first one is https://review.openstack.org/#/c/94473, we have the
> blueprint for this spec
> and one commit https://review.openstack.org/#/c/75425 in Abandoned state.
> Can we continue
> to work on this commit or we need to redesign it and make new commits?
> The other specs which we also can discuss on this design session (added to
> and again, we need to update them, review and merge (if we want to see them
> in Tempest).
> We are using Tempest tests for verification of different OpenStack clouds
> and we really have
> issues with many custom configuration files and additional scripts, which
> allow to configure
> OpenStack before the tests. I like the idea, which Boris and Andrey
> described in https://review.openstack.org/#/c/94473
> and I want to participate in implementation of this feature and use it to
> automate OpenStack clouds
> verification on many projects. I hope we will discuss this spec on the
> design session and will update
> and merge it soon.
> By the way, could you please add the link to etherpad  to the event
> description , it will help to
> find the correct link from mobile devices.
> Thank you!
> On Fri, Oct 31, 2014 at 4:23 AM, Masayuki Igawa <masayuki.igawa at gmail.com>
>> Hi everyone,
>> I'd like to advertise the session and gather ideas before we will
>> start the session to make it more productive.
>> So please put your ideas for this topic on the pad if you have ideas.
>> I think the goal of this session is to make decisions what we should
>> do or not in Kilo development cycle for filling the gap. And that will
>> be an input to make blurprints.
>> Masayuki Igawa
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
> Senior QA Engineer
> OpenStack Projects
> Mirantis Inc
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev