Hi Timur, 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 [2] to the event > description [1], it will help to find the correct link from mobile devices. Actually, I don't have the permission to add/change the description on the sched.org. I think Matthew(mtreinish) can do it. Thanks. On Sat, Nov 1, 2014 at 6:21 PM, Timur Nurlygayanov <[email protected]> wrote: > Hello, > > 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 > etherpad): > > https://review.openstack.org/#/c/86967/ > > https://review.openstack.org/#/c/89322/ > > https://review.openstack.org/#/c/92804/ > > 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 [2] to the event > description [1], it will help to > find the correct link from mobile devices. > > Thank you! > > > On Fri, Oct 31, 2014 at 4:23 AM, Masayuki Igawa <[email protected]> > wrote: >> >> Hi everyone, >> >> I'd like to advertise the session[1] 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[2] 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. >> >> [1] >> http://kilodesignsummit.sched.org/event/6d91b3205804c930c2a067b23e7aab76#.VErHcH96c-U >> [2] >> https://etherpad.openstack.org/p/kilo-summit-gap-analysis-tempest-in-production >> >> Thanks, >> -- >> Masayuki Igawa >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > -- > > Timur, > Senior QA Engineer > OpenStack Projects > Mirantis Inc > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Masayuki Igawa _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
