<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;color:rgb(0,0,0)"><p class="gmail-MsoPlainText">Yea, agree with dims. </p>
<p class="gmail-MsoPlainText">Sampath ,<span></span></p>
<p class="gmail-MsoPlainText">Thanks for taking over this, it is really great help. Please
update the current spec with approaches you have. Timur help will be great if
he show up sometime.</p>
<p class="gmail-MsoPlainText">Also we will add destructive testing as one of weekly
meeting agenda and make sure you will get all help & required attention
from QA team. </p>
<p class="gmail-MsoPlainText">-gmann</p></div><div class="gmail_extra">
<br><div class="gmail_quote">On Fri, Feb 24, 2017 at 7:26 AM, Davanum Srinivas <span dir="ltr"><<a href="mailto:davanum@gmail.com" target="_blank">davanum@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sampath,<br>
<br>
I am not sure if you will hear back from Timur soon as he may not be<br>
working on this stuff anymore (in Mirantis). So i'd recommend picking<br>
up the work if you don't hear from him soon.<br>
<br>
Thanks,<br>
Dims<br>
<br>
On Thu, Feb 23, 2017 at 3:41 PM, Sam P <<a href="mailto:sam47priya@gmail.com">sam47priya@gmail.com</a>> wrote:<br>
> Hi Timur,<br>
><br>
> The current status of this work is,<br>
> 1) The QA user story for destructive testing of OpenStack cloud [1] is merged .<br>
> 2) The spec for a new framework which will focus on HA/failover and<br>
> destructive testing [2] has no update since Nov 30 2016.<br>
> 3) The commit for the new repository [3] has abandoned due to no<br>
> update after Nov 29 2016.<br>
><br>
> Currently, I am working on 3rd party destructive/HA testing CI for<br>
> Masakari[4] and very much interested in this work.<br>
> I will keep working on [1] with PWG.<br>
> Please let me know your plans for [2], and [3].<br>
> If it is difficult for you to continue, I would love to continue your<br>
> work on [2], and [3].<br>
><br>
> [1] <a href="https://review.openstack.org/#/c/396142" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/396142</a><br>
> [2] <a href="https://review.openstack.org/#/c/399618" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/399618</a><br>
> [3] <a href="https://review.openstack.org/#/c/374667" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/374667</a><br>
> [4] <a href="https://wiki.openstack.org/wiki/Masakari" rel="noreferrer" target="_blank">https://wiki.openstack.org/<wbr>wiki/Masakari</a><br>
> --- Regards,<br>
> Sampath<br>
><br>
><br>
><br>
> On Mon, Nov 28, 2016 at 6:37 AM, Timur Nurlygayanov<br>
> <<a href="mailto:tnurlygayanov@mirantis.com">tnurlygayanov@mirantis.com</a>> wrote:<br>
>> Hi team,<br>
>><br>
>> here is a short update:<br>
>><br>
>> 1) The QA user story for destructive testing of OpenStack cloud is on review<br>
>> [1].<br>
>> 2) The spec for a new framework which will focus on HA/failover and<br>
>> destructive testing is no review [2].<br>
>> 3) The commit for the new repository is on review [3] as well.<br>
>><br>
>> [1] <a href="https://review.openstack.org/#/c/396142" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/396142</a><br>
>> [2] <a href="https://review.openstack.org/#/c/399618" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/399618</a><br>
>> [3] <a href="https://review.openstack.org/#/c/374667" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/374667</a><br>
>><br>
>><br>
>> On Fri, Oct 14, 2016 at 3:47 AM, Ghanshyam Mann<br>
>> <<a href="mailto:ghanshyam.mann@nectechnologies.in">ghanshyam.mann@<wbr>nectechnologies.in</a>> wrote:<br>
>>><br>
>>> I like os-faults library which can provide the abstraction over different<br>
>>> destructive actions like reboot/poweroff node etc.<br>
>>><br>
>>><br>
>>><br>
>>> But not much clear about Stepler that what all tests it will contain.<br>
>>> Tempest do have scenario tests which can hit the production env with<br>
>>> significant way of testing scenario.<br>
>>><br>
>>> It can cover the end user scenario also which involves the interaction of<br>
>>> public OpenStack APIs and always in enhancement state by adding more and<br>
>>> more scenario tests.<br>
>>><br>
>>><br>
>>><br>
>>> Few query over Stepler as separate project:<br>
>>><br>
>>> 1. Is Stepler will cover only tests which hits the node level<br>
>>> action(reboot, HA etc)?<br>
>>><br>
>>> 2. This should not mix the scenario tests which are in Tempest scope<br>
>>> because that can make confusion for developers (where to add scenario tests)<br>
>>> as well as for tester(from where to run what scenario tests).<br>
>>><br>
>>> 3. How we make sure those tests run fine or at least run while<br>
>>> adding.<br>
>>><br>
>>> a. I think devstack enhancement for multi-node etc can do this as<br>
>>> mentioned by you also.<br>
>>><br>
>>> b. If so then why not adding those tests in Tempest only using<br>
>>> os-faults lib ?<br>
>>><br>
>>><br>
>>><br>
>>> Overall I feel os-faults as lib is really nice idea but tests scope can<br>
>>> go in Tempest under HW_scenario (or something else) till it does not break<br>
>>> basic principle of Tempest.<br>
>>><br>
>>><br>
>>><br>
>>> Thanks<br>
>>><br>
>>> gmann<br>
>>><br>
>>><br>
>>><br>
>>> From: Timur Nurlygayanov [mailto:<a href="mailto:tnurlygayanov@mirantis.com">tnurlygayanov@<wbr>mirantis.com</a>]<br>
>>> Sent: 06 October 2016 20:09<br>
>>> To: OpenStack Development Mailing List (not for usage questions)<br>
>>> <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
>>> Subject: Re: [openstack-dev] [QA] The end-user test suite for OpenStack<br>
>>> clusters<br>
>>><br>
>>><br>
>>><br>
>>> Ken, it is a good idea!<br>
>>><br>
>>><br>
>>><br>
>>> The plan is to develop os-faults as a library which will be able<br>
>>><br>
>>> to manage cluster nodes and OpenStack services on these nodes.<br>
>>><br>
>>> It is a good idea to add some Tempest tests which will use<br>
>>><br>
>>> os-faults library as well for some API tests.<br>
>>><br>
>>><br>
>>><br>
>>> The Stepler framework [1] will use os-faults to perform all destructive<br>
>>><br>
>>> actions in the clouds (the reboot of nodes, restart of OpenStack services,<br>
>>><br>
>>> enable/disable network interfaces or some firewall rules and etc).<br>
>>><br>
>>><br>
>>><br>
>>> We need to get +1 from you in [1] to create the repository with<br>
>>><br>
>>> advanced end-user scenario tests.<br>
>>><br>
>>><br>
>>><br>
>>> Thank you!<br>
>>><br>
>>><br>
>>><br>
>>> [1] <a href="https://review.openstack.org/#/c/374667/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/374667/</a><br>
>>><br>
>>><br>
>>><br>
>>> On Tue, Oct 4, 2016 at 8:53 PM, Yaroslav Lobankov <<a href="mailto:ylobankov@mirantis.com">ylobankov@mirantis.com</a>><br>
>>> wrote:<br>
>>><br>
>>> Hi Ken,<br>
>>><br>
>>><br>
>>><br>
>>> OS-Faults doesn't have any scenarios in the tree yet (the project is two<br>
>>> months old), but you can find some examples of the use in the<br>
>>> os-faults/examples directory.<br>
>>><br>
>>><br>
>>><br>
>>> Regards,<br>
>>><br>
>>> Yaroslav Lobankov.<br>
>>><br>
>>><br>
>>><br>
>>> On Tue, Oct 4, 2016 at 8:02 PM, Ken'ichi Ohmichi <<a href="mailto:ken1ohmichi@gmail.com">ken1ohmichi@gmail.com</a>><br>
>>> wrote:<br>
>>><br>
>>> Hi Timur,<br>
>>><br>
>>> Thanks for your explanation.<br>
>>><br>
>>><br>
>>> 2016-09-29 6:22 GMT-07:00 Timur Nurlygayanov <<a href="mailto:tnurlygayanov@mirantis.com">tnurlygayanov@mirantis.com</a>>:<br>
>>> ><br>
>>> >> I am guessing the above "restart nodes" is for verifying each<br>
>>> >> OpenStack service restarts successfully, right?<br>
>>> ><br>
>>> > Yes, this is right. And we also will check that HA logic for these<br>
>>> > services works correctly (for example, rescheduling of L3 Neutron<br>
>>> > agents for networks).<br>
>>> ><br>
>>> >> But these service scripts are provided by distributors, and Devstack<br>
>>> >> itself doesn't contain service scripts IIUC.<br>
>>> >> So I'd like to know how to verify it on Devstack clouds.<br>
>>> ><br>
>>> > Yes, DevStack doesn't support many scenarios which are actual<br>
>>> > and should be supported on the production clouds.<br>
>>> > It will be not possible to run all advanced test scenarios for DevStack<br>
>>> > clouds,<br>
>>> > just because DevStack can't deploy OpenStack cloud with 3 controllers<br>
>>> > now (so, probably it will be possible in the future).<br>
>>> ><br>
>>> > Of course, some advanced scenarios will support DevStack clouds,<br>
>>> > for example, some test scenarios which are based on customer-found<br>
>>> > issues from the real production clouds, like upload of the large images<br>
>>> > (100+ Gb)<br>
>>> > to Glance with Swift backend. Such cases are important for verification<br>
>>> > of<br>
>>> > pre-production environments, but not very important for CI gate jobs.<br>
>>> ><br>
>>> > It is also important to note that in these advanced cases we are<br>
>>> > targeting<br>
>>> > to check not only the logic of Python code, but also the correct<br>
>>> > configuration<br>
>>> > of all OpenStack components on some pre-production OpenStack clusters.<br>
>>><br>
>>> I guessed some part of os-faults can be moved to Tempest if os-faults<br>
>>> contains API tests for enabling/disabling OpenStack services.<br>
>>> Then, os-faults would be able to concentrate on more destructive tests<br>
>>> like rebooting physical nodes, etc.<br>
>>> However, I could not find any actual scenarios on current os-faults<br>
>>> (<a href="https://github.com/openstack/os-faults" rel="noreferrer" target="_blank">https://github.com/openstack/<wbr>os-faults</a>).<br>
>>> That seems to just contain some abstraction layers and unit tests. Can<br>
>>> we see actual test scenarios of os-faults ?<br>
>>> Maybe I missed something.<br>
>>><br>
>>> Thanks<br>
>>> Ken Ohmichi<br>
>>><br>
>>><br>
>>> ______________________________<wbr>______________________________<wbr>______________<br>
>>> OpenStack Development Mailing List (not for usage questions)<br>
>>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> ______________________________<wbr>______________________________<wbr>______________<br>
>>> OpenStack Development Mailing List (not for usage questions)<br>
>>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>><br>
>>><br>
>>><br>
>>> Timur,<br>
>>><br>
>>> Senior QA Manager<br>
>>><br>
>>> OpenStack Projects<br>
>>><br>
>>> Mirantis Inc<br>
>>><br>
>>><br>
>>> ______________________________<wbr>______________________________<wbr>______________<br>
>>> OpenStack Development Mailing List (not for usage questions)<br>
>>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
>>><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Timur,<br>
>> QA Manager<br>
>> OpenStack Projects<br>
>> Mirantis Inc<br>
>><br>
>> ______________________________<wbr>______________________________<wbr>______________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
>><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
Davanum Srinivas :: <a href="https://twitter.com/dims" rel="noreferrer" target="_blank">https://twitter.com/dims</a><br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</font></span></blockquote></div><br></div></div>