Re: [openstack-dev] [QA] [ptg] Team photo

2017-02-22 Thread Yaroslav Lobankov
+1

Regards,
Yaroslav Lobankov.

On Wed, Feb 22, 2017 at 8:14 AM, <zhu.fang...@zte.com.cn> wrote:

> Who can kindly send me a photo as an mail attachment? I am curious about
> it but I can't open the link ^-^
>
>
> Original Mail
> *Sender: * <andrea.fritt...@gmail.com>;
> *To: * <openstack-dev@lists.openstack.org>;
> *Date: *2017/02/22 11:40
> *Subject: **[openstack-dev] [QA] [ptg] Team photo*
>
>
> Here are our team photos: https://www.dropbox.com/home/
> Public/PTG%20Atlanta%20QA%20Team
>
> andrea
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] The end-user test suite for OpenStack clusters

2016-10-04 Thread Yaroslav Lobankov
Hi Ken,

OS-Faults doesn't have any scenarios in the tree yet (the project is two
months old), but you can find some examples of the use in the
os-faults/examples directory.

Regards,
Yaroslav Lobankov.

On Tue, Oct 4, 2016 at 8:02 PM, Ken'ichi Ohmichi <ken1ohmi...@gmail.com>
wrote:

> Hi Timur,
>
> Thanks for your explanation.
>
> 2016-09-29 6:22 GMT-07:00 Timur Nurlygayanov <tnurlygaya...@mirantis.com>:
> >
> >> I am guessing the above "restart nodes" is for verifying each
> >> OpenStack service restarts successfully, right?
> >
> > Yes, this is right. And we also will check that HA logic for these
> > services works correctly (for example, rescheduling of L3 Neutron
> > agents for networks).
> >
> >> But these service scripts are provided by distributors, and Devstack
> >> itself doesn't contain service scripts IIUC.
> >> So I'd like to know how to verify it on Devstack clouds.
> >
> > Yes, DevStack doesn't support many scenarios which are actual
> > and should be supported on the production clouds.
> > It will be not possible to run all advanced test scenarios for DevStack
> > clouds,
> > just because DevStack can't deploy OpenStack cloud with 3 controllers
> > now (so, probably it will be possible in the future).
> >
> > Of course, some advanced scenarios will support DevStack clouds,
> > for example, some test scenarios which are based on customer-found
> > issues from the real production clouds, like upload of the large images
> > (100+ Gb)
> > to Glance with Swift backend. Such cases are important for verification
> of
> > pre-production environments, but not very important for CI gate jobs.
> >
> > It is also important to note that in these advanced cases we are
> targeting
> > to check not only the logic of Python code, but also the correct
> > configuration
> > of all OpenStack components on some pre-production OpenStack clusters.
>
> I guessed some part of os-faults can be moved to Tempest if os-faults
> contains API tests for enabling/disabling OpenStack services.
> Then, os-faults would be able to concentrate on more destructive tests
> like rebooting physical nodes, etc.
> However, I could not find any actual scenarios on current os-faults
> (https://github.com/openstack/os-faults).
> That seems to just contain some abstraction layers and unit tests. Can
> we see actual test scenarios of os-faults ?
> Maybe I missed something.
>
> Thanks
> Ken Ohmichi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [qa] [Tempest] Abondoned old code reviews

2016-05-31 Thread Yaroslav Lobankov
+1! But I think we can leave patches created in 2016 and abandon others.

Regards,
Yaroslav Lobankov.

On Mon, May 30, 2016 at 8:20 PM, Ken'ichi Ohmichi <ken1ohmi...@gmail.com>
wrote:

> Hi,
>
> There are many patches which are not updated in Tempest review queue
> even if having gotten negative feedback from reviewers or jenkins.
> Nova team is abandoning such patches like [1].
> I feel it would be nice to abandone such patches which are not updated
> since the end of 2015.
> Any thoughts?
>
> [1]:
> http://lists.openstack.org/pipermail/openstack-dev/2016-May/096112.html
>
> Thanks
> Ken Ohmichi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] Not running for PTL

2016-03-13 Thread Yaroslav Lobankov
Thanks, Matt, for your great work for 2 years! These years have been very
productive for the QA program. It has been a pleasure working under your
leadership! :)

Regards,
Yaroslav Lobankov.

On Sun, Mar 13, 2016 at 8:51 AM, Masayuki Igawa <masayuki.ig...@gmail.com>
wrote:

> From: Matthew Treinish <mtrein...@kortar.org>
> Subject: [openstack-dev] [QA] Not running for PTL
> Date: Fri, 11 Mar 2016 14:34:10 -0500
>
> > Hi everyone,
> >
> > I'm writing this to announce that I am not running for QA PTL this
> cycle. I've
> > been the QA PTL for the past 4 cycles and I think it's time for another
> person
> > to take over the role. I think during the past 4 cycles the QA community
> has
> > grown greatly and become a much larger and stronger community compared
> to when
> > I first took on the position in the Juno cycle.
> >
> > I strongly believe in the diversity of leadership and ideas, and I don't
> want
> > the community to grow stagnant because it becomes synonymous with just
> my voice.
> > Being a PTL is not the same as being an autocrat and I think it's time
> for
> > another person to step up and take over the QA PTL spot.
> >
> > That being said, I'm not planning on going anywhere or leaving the
> project. I
> > fully intend to continue working and being heavily involved with the QA
> program,
> > as I have for been the past 2 years. (although maybe with a bit more
> free time
> > now)
>
> Thank you very very very much for your really great work! And I hope you
> still
> continue to deeply involved with the QA program for the better OpenStack
> quality,
> too :)
>
> Best Regards,
> -- Masayuki Igawa(IRC: masayukig)
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] No meetings for the next 2 weeks

2015-12-17 Thread Yaroslav Lobankov
Hi Matt,

Unfortunately, I had no chance to participate in the latest meeting. It is
very helpful information. Thanks!

Regards,
Yaroslav Lobankov.

On Fri, Dec 18, 2015 at 12:06 AM, Matthew Treinish <mtrein...@kortar.org>
wrote:

>
> Hi Everyone,
>
> As we discussed during today's QA meeting we'll not be holding the weekly
> QA
> meeting for the next 2 weeks. Most people will be on vacation anyway, so
> this
> likely isn't a big surprise.
>
> The next meeting will be on Jan. 7th at 0900 UTC.
>
> Thanks,
>
> Matt Treinish
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA][Tempest] Use tempest-config for tempest-cli-improvements

2015-11-26 Thread Yaroslav Lobankov
Hello everyone,

Yes, I am working on this now. We have some success already, but there is a
lot of work to do. Of course, some things don't work ideally. For example,
in [2] from the previous letter we have not 24 skipped tests, actually much
more. So we have a bug somewhere :)

Regards,
Yaroslav Lobankov.

On Thu, Nov 26, 2015 at 3:59 PM, Andrey Kurilin <akuri...@mirantis.com>
wrote:

> Hi!
> Boris P. and I tried to push a spec[1] for automation tempest config
> generator, but we did not succeed to merge it. Imo, qa-team doesn't want to
> have such tool:(
>
> >However, there is a big concern:
> >If the script contain a bug and creates the configuration which makes
> >most tests skipped, we cannot do enough tests on the gate.
> >Tempest contains 1432 tests and difficult to detect which tests are
> >skipped as unexpected.
>
> Yaroslav Lobankov is working on improvement for tempest config generator
> in Rally. Last time when we launch full tempest run[2], we got 1154 success
> tests and only 24 skipped. Also, there is a patch, which adds x-fail
> mechanism(it based on subunit-filter): you can transmit a file with test
> names + reasons and rally will modify results.
>
> [1] - https://review.openstack.org/#/c/94473/
>
> [2] -
> http://logs.openstack.org/49/242849/8/check/gate-rally-dsvm-verify/e91992e/rally-verify/7_verify_results_--html.html.gz
>
> On Thu, Nov 26, 2015 at 1:52 PM, Ken'ichi Ohmichi <ken1ohmi...@gmail.com>
> wrote:
>
>> Hi Daniel,
>>
>> Thanks for pointing this up.
>>
>> 2015-11-25 1:40 GMT+09:00 Daniel Mellado <daniel.mellado...@ieee.org>:
>> > Hi All,
>> >
>> > As you might already know, within Red Hat's tempest fork, we do have one
>> > tempest configuration script which was built in the past by David Kranz
>> [1]
>> > and that's been actively used in our CI system. Regarding this topic,
>> I'm
>> > aware that quite some effort has been done in the past [2] and I would
>> like
>> > to complete the implementation of this blueprint/spec.
>> >
>> > My plan would be to have this script under the /tempest/cmd or
>> > /tempest/tools folder from tempest so it can be used to configure not
>> the
>> > tempest gate but any cloud we'd like to run tempest against.
>> >
>> > Adding the configuration script was discussed briefly at the Mitaka
>> summit
>> > in the QA Priorities meting [3]. I propose we use the existing etherpad
>> to
>> > continue the discussion around and tracking of implementing "tempest
>> > config-create" using the downstream config script as a starting point.
>> [4]
>> >
>> > If you have any questions, comments or opinion, please let me know.
>>
>> This topic have happened several times, and I also felt this kind of
>> tool was very useful for Tempest users, because Tempest contains 296
>> options($ grep cfg * -R | grep Opt | wc -l) now and it is difficult to
>> set the configuration up.
>> However, there is a big concern:
>> If the script contain a bug and creates the configuration which makes
>> most tests skipped, we cannot do enough tests on the gate.
>> Tempest contains 1432 tests and difficult to detect which tests are
>> skipped as unexpected.
>> Actually we faced unexpected skipped tests on the gate before due to
>> some bug, then the problem has been fixed.
>> But I can imagine this kind of problem happens after implementing this
>> kind of script.
>>
>> So now I am feeling Tempest users need to know what cloud they want to
>> test with Tempest, and need to know what tests run with Tempest.
>> Testers need to know what test target/items they are testing basically.
>>
>> Thanks
>> Ken Ohmichi
>>
>> ---
>>
>> > ---
>> > [1]
>> >
>> https://github.com/redhat-openstack/tempest/blob/master/tools/config_tempest.py
>> > [2]
>> https://blueprints.launchpad.net/tempest/+spec/tempest-config-generator
>> > [3] https://etherpad.openstack.org/p/mitaka-qa-priorities
>> > [4] https://etherpad.openstack.org/p/tempest-cli-improvements
>> >
>> >
>> https://github.com/openstack/qa-specs/blob/master/specs/tempest/tempest-cli-improvements.rst
>> >
>> >
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/opens

[openstack-dev] [qa] Tempest bug triage questions

2015-06-22 Thread Yaroslav Lobankov
Hello everyone,

I have some questions about the bug triage procedure for Tempest:

1. Some bugs in Tempest have status Fix committed. Should we move
statuses of these bugs to Fix released?

2. Many bugs have statuses In progress, but patches for these bugs have
-1 from someone (or their workflow is -1)
and it looks like these patches are abandoned, while statuses of such
patches are Review in progress.
What should we do with such bugs?

3. What should we do with bugs like this [1]? It says that
TimeoutException occurred,
but the log of the test is unavailable
by the link already. I don't know how to reproduce the issue, besides
the log of the test is unavailable. What should I do with this bug?

Thank you!

[1] https://bugs.launchpad.net/tempest/+bug/1322011

Regards,
Yaroslav Lobankov.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [qa] Need volunteers for tempest bug triage

2015-05-30 Thread Yaroslav Lobankov
Hi everyone,

Is it possible for other people (not only core reviewers) to participate in
bug triage? I would like to help in doing this.

Regards,
Yaroslav Lobankov.

On Fri, May 29, 2015 at 11:44 PM, David Kranz dkr...@redhat.com wrote:

 The rotation has gotten a bit thin, and the untriaged bug count growing,
 with no one signing up for this past week:

 https://etherpad.openstack.org/p/qa-bug-triage-rotation

 It would help if every core reviewer could be doing this every other
 month. Getting some more sign ups would be very helpful!

  -David

 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] Question about Heat Tempest tests

2015-05-15 Thread Yaroslav Lobankov
Forgot to provide the link to the test results :)
http://logs.openstack.org/71/182971/1/gate/gate-tempest-dsvm-heat/241e473/logs/testr_results.html.gz

Regards,
Yaroslav Lobankov.

On Fri, May 15, 2015 at 4:30 PM, Yaroslav Lobankov yloban...@mirantis.com
wrote:

 Angus,

 If you take a look at the tempest check job check-tempest-dsvm-heat for
 the patch https://review.openstack.org/#/c/182971/, you will see that all
 tests are skipped there. I have not found any job anywhere that runs
 these tests.

 Regards,
 Yaroslav Lobankov.

 On Fri, May 15, 2015 at 2:16 AM, Angus Salkeld asalk...@mirantis.com
 wrote:

 On Fri, May 15, 2015 at 1:53 AM, Yaroslav Lobankov 
 yloban...@mirantis.com wrote:

 Hello everyone,

 I have a question about Heat Tempest tests. Is there any dsvm job that
 runs these tests? At first glance no dsvm job runs them.


 We are using in tree functional tests now:
 https://github.com/openstack/heat/tree/master/heat_integrationtests

 And heat has a tempest check job too (for the API tests):
 check-tempest-dsvm-heat
 for example: https://review.openstack.org/#/c/182971/

 -Angus

 Thank you!

 Regards,
 Yaroslav Lobankov.


 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] Question about Heat Tempest tests

2015-05-15 Thread Yaroslav Lobankov
Angus,

If you take a look at the tempest check job check-tempest-dsvm-heat for
the patch https://review.openstack.org/#/c/182971/, you will see that all
tests are skipped there. I have not found any job anywhere that runs these
tests.

Regards,
Yaroslav Lobankov.

On Fri, May 15, 2015 at 2:16 AM, Angus Salkeld asalk...@mirantis.com
wrote:

 On Fri, May 15, 2015 at 1:53 AM, Yaroslav Lobankov yloban...@mirantis.com
  wrote:

 Hello everyone,

 I have a question about Heat Tempest tests. Is there any dsvm job that
 runs these tests? At first glance no dsvm job runs them.


 We are using in tree functional tests now:
 https://github.com/openstack/heat/tree/master/heat_integrationtests

 And heat has a tempest check job too (for the API tests):
 check-tempest-dsvm-heat
 for example: https://review.openstack.org/#/c/182971/

 -Angus

 Thank you!

 Regards,
 Yaroslav Lobankov.

 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [QA] Question about Heat Tempest tests

2015-05-14 Thread Yaroslav Lobankov
Hello everyone,

I have a question about Heat Tempest tests. Is there any dsvm job that runs
these tests? At first glance no dsvm job runs them.

Thank you!

Regards,
Yaroslav Lobankov.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] Question about tempest API tests that establish SSH connection to instances

2015-04-28 Thread Yaroslav Lobankov
Guys, thank you for answers!

Then I have one more question :) How do scenario tests (that establish SSH
connection to instances) work?

Regards,
Yaroslav Lobankov.

On Tue, Apr 28, 2015 at 12:27 PM, Lanoux, Joseph joseph.lan...@hp.com
wrote:

  Hi,



 Actually, ssh connection is not yet implemented in Tempest. We’re
 currently working on it [1].



 Joseph



 [1]
 https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/ssh-auth-strategy,n,z





 *From:* Salvatore Orlando [mailto:sorla...@nicira.com]
 *Sent:* 28 April 2015 10:16
 *To:* OpenStack Development Mailing List (not for usage questions)
 *Subject:* Re: [openstack-dev] [QA] Question about tempest API tests that
 establish SSH connection to instances



 At a first glance it seems run_ssh is disabled in gate tests [1]. I could
 not find any nova job where it is enabled.

 These tests are therefore skipped. For what is worth they might be broken
 now. Sharing a traceback or filing a bug might help.



 Salvatore



 [1]
 http://logs.openstack.org/81/159481/2/check/check-tempest-dsvm-neutron-full/85e039c/logs/testr_results.html.gz



 On 28 April 2015 at 10:26, Yaroslav Lobankov yloban...@mirantis.com
 wrote:

  Hi everyone,



 I have a question about tempest tests that are related to instance
 validation. Some of these tests are




 tempest.api.compute.servers.test_create_server.ServersTestJSON.test_host_name_is_same_as_server_name[gate,id-ac1ad47f-984b-4441-9274-c9079b7a0666]


 tempest.api.compute.servers.test_create_server.ServersTestJSON.test_verify_created_server_vcpus[gate,id-cbc0f52f-05aa-492b-bdc1-84b575ca294b]


 tempest.api.compute.servers.test_create_server.ServersTestManualDisk.test_host_name_is_same_as_server_name[gate,id-ac1ad47f-984b-4441-9274-c9079b7a0666]


 tempest.api.compute.servers.test_create_server.ServersTestManualDisk.test_verify_created_server_vcpus[gate,id-cbc0f52f-05aa-492b-bdc1-84b575ca294b]



 To enable these tests I should set the config option run_ssh to True.
 When I set the option to true and ran the tests, all the tests failed. It
 looks like ssh code in API tests doesn't work.

 Maybe I am wrong. The question is the following: which of tempest jobs
 runs these tests?  Maybe I have tempest misconfiguration.



 Regards,

 Yaroslav Lobankov.


 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [QA] Question about tempest API tests that establish SSH connection to instances

2015-04-28 Thread Yaroslav Lobankov
Hi everyone,

I have a question about tempest tests that are related to instance
validation. Some of these tests are

tempest.api.compute.servers.test_create_server.ServersTestJSON.test_host_name_is_same_as_server_name[gate,id-ac1ad47f-984b-4441-9274-c9079b7a0666]
tempest.api.compute.servers.test_create_server.ServersTestJSON.test_verify_created_server_vcpus[gate,id-cbc0f52f-05aa-492b-bdc1-84b575ca294b]
tempest.api.compute.servers.test_create_server.ServersTestManualDisk.test_host_name_is_same_as_server_name[gate,id-ac1ad47f-984b-4441-9274-c9079b7a0666]
tempest.api.compute.servers.test_create_server.ServersTestManualDisk.test_verify_created_server_vcpus[gate,id-cbc0f52f-05aa-492b-bdc1-84b575ca294b]

To enable these tests I should set the config option run_ssh to True.
When I set the option to true and ran the tests, all the tests failed. It
looks like ssh code in API tests doesn't work.
Maybe I am wrong. The question is the following: which of tempest jobs runs
these tests?  Maybe I have tempest misconfiguration.

Regards,
Yaroslav Lobankov.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] Question about tempest API tests that establish SSH connection to instances

2015-04-28 Thread Yaroslav Lobankov
Matt, thank you for the answer!

Regards,
Yaroslav Lobankov.

On Tue, Apr 28, 2015 at 6:00 PM, Matthew Treinish mtrein...@kortar.org
wrote:

 On Tue, Apr 28, 2015 at 02:21:27PM +0300, Yaroslav Lobankov wrote:
  Guys, thank you for answers!
 
  Then I have one more question :) How do scenario tests (that establish
 SSH
  connection to instances) work?
 

 So the scenario tests don't use the run_ssh flag, they just ssh in to
 servers
 when they need to regardless of the value of that config option. (as do any
 tests which are currently using ssh in the gate)

 That's actually part of what the BP that Joseph pointed out is trying to
 address. The run_ssh option is currently kind of a mess, it's not globally
 respected, and things that do rely on it are probably broken, because as
 Salvatore said we skip those in the gate.

 Reading the spec for that BP will provide some good background here:

 http://specs.openstack.org/openstack/qa-specs/specs/ssh-auth-strategy.html

 -Matt Treinish

 
  On Tue, Apr 28, 2015 at 12:27 PM, Lanoux, Joseph joseph.lan...@hp.com
  wrote:
 
Hi,
  
  
  
   Actually, ssh connection is not yet implemented in Tempest. We’re
   currently working on it [1].
  
  
  
   Joseph
  
  
  
   [1]
  
 https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/ssh-auth-strategy,n,z
  
  
  
  
  
   *From:* Salvatore Orlando [mailto:sorla...@nicira.com]
   *Sent:* 28 April 2015 10:16
   *To:* OpenStack Development Mailing List (not for usage questions)
   *Subject:* Re: [openstack-dev] [QA] Question about tempest API tests
 that
   establish SSH connection to instances
  
  
  
   At a first glance it seems run_ssh is disabled in gate tests [1]. I
 could
   not find any nova job where it is enabled.
  
   These tests are therefore skipped. For what is worth they might be
 broken
   now. Sharing a traceback or filing a bug might help.
  
  
  
   Salvatore
  
  
  
   [1]
  
 http://logs.openstack.org/81/159481/2/check/check-tempest-dsvm-neutron-full/85e039c/logs/testr_results.html.gz
  
  
  
   On 28 April 2015 at 10:26, Yaroslav Lobankov yloban...@mirantis.com
   wrote:
  
Hi everyone,
  
  
  
   I have a question about tempest tests that are related to instance
   validation. Some of these tests are
  
  
  
  
  
 tempest.api.compute.servers.test_create_server.ServersTestJSON.test_host_name_is_same_as_server_name[gate,id-ac1ad47f-984b-4441-9274-c9079b7a0666]
  
  
  
 tempest.api.compute.servers.test_create_server.ServersTestJSON.test_verify_created_server_vcpus[gate,id-cbc0f52f-05aa-492b-bdc1-84b575ca294b]
  
  
  
 tempest.api.compute.servers.test_create_server.ServersTestManualDisk.test_host_name_is_same_as_server_name[gate,id-ac1ad47f-984b-4441-9274-c9079b7a0666]
  
  
  
 tempest.api.compute.servers.test_create_server.ServersTestManualDisk.test_verify_created_server_vcpus[gate,id-cbc0f52f-05aa-492b-bdc1-84b575ca294b]
  
  
  
   To enable these tests I should set the config option run_ssh to True.
   When I set the option to true and ran the tests, all the tests failed.
 It
   looks like ssh code in API tests doesn't work.
  
   Maybe I am wrong. The question is the following: which of tempest jobs
   runs these tests?  Maybe I have tempest misconfiguration.
  
  
  
   Regards,
  
   Yaroslav Lobankov.
  
  
  
 __
   OpenStack Development Mailing List (not for usage questions)
   Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
   http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
  
  
  
  
 __
   OpenStack Development Mailing List (not for usage questions)
   Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
   http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
  
  

 
 __
  OpenStack Development Mailing List (not for usage questions)
  Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] Question about EC2 Tempest tests

2015-02-12 Thread Yaroslav Lobankov
Joe, thank you for the note!

Regards,
Yaroslav Lobankov.

On Thu, Feb 12, 2015 at 2:43 AM, Joe Gordon joe.gord...@gmail.com wrote:



 On Wed, Feb 11, 2015 at 3:58 AM, Alexandre Levine 
 alev...@cloudscaling.com wrote:

  Yaroslav,

 The bug:
 https://bugs.launchpad.net/nova/+bug/1410622

 And the review:
 https://review.openstack.org/#/c/152112/

 It's recently fixed.


 Note, AFAIK this has not been backported to stable/juno or stable/icehouse
 so running trunk EC2 tempest tests against stable/juno nova is still not
 working.

 In fact to unwedge stable branches we turned these tests off:
 https://review.openstack.org/#/c/154575/


 Best regards,
   Alex Levine


 On 2/11/15 2:23 PM, Yaroslav Lobankov wrote:

 Hello everyone,

  I have some question about EC2 Tempest tests. When I run these tests, I
 regularly have the same error for all tests:

  EC2ResponseError: EC2ResponseError: 400 Bad Request
 ?xml version=1.0?
 ResponseErrorsErrorCodeAuthFailure/CodeMessageSignature not
 provided/Message/Error/Errors

  My environment is OpenStack (the Juno release) deployed by Fuel 6.0.
 Tempest is from master branch.

  I found that the issue was related to boto (Tempest installs it into
 virtual environment as a dependency). The last available release of boto is
 2.36.0.
 When this version of boto is installed, EC2 tests don't work. But if I
 install boto 2.34.0 instead of 2.36.0, all EC2 tests will have success.

  Any thoughts?

  Regards,
 Yaroslav Lobankov.


 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: 
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [QA] Question about EC2 Tempest tests

2015-02-11 Thread Yaroslav Lobankov
Hello everyone,

I have some question about EC2 Tempest tests. When I run these tests, I
regularly have the same error for all tests:

EC2ResponseError: EC2ResponseError: 400 Bad Request
?xml version=1.0?
ResponseErrorsErrorCodeAuthFailure/CodeMessageSignature not
provided/Message/Error/Errors

My environment is OpenStack (the Juno release) deployed by Fuel 6.0.
Tempest is from master branch.

I found that the issue was related to boto (Tempest installs it into
virtual environment as a dependency). The last available release of boto is
2.36.0.
When this version of boto is installed, EC2 tests don't work. But if I
install boto 2.34.0 instead of 2.36.0, all EC2 tests will have success.

Any thoughts?

Regards,
Yaroslav Lobankov.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [QA] Question about EC2 Tempest tests

2015-02-11 Thread Yaroslav Lobankov
Thanks, Alexandre!

Regards,
Yaroslav Lobankov.

On Wed, Feb 11, 2015 at 2:58 PM, Alexandre Levine alev...@cloudscaling.com
wrote:

  Yaroslav,

 The bug:
 https://bugs.launchpad.net/nova/+bug/1410622

 And the review:
 https://review.openstack.org/#/c/152112/

 It's recently fixed.

 Best regards,
   Alex Levine


 On 2/11/15 2:23 PM, Yaroslav Lobankov wrote:

 Hello everyone,

  I have some question about EC2 Tempest tests. When I run these tests, I
 regularly have the same error for all tests:

  EC2ResponseError: EC2ResponseError: 400 Bad Request
 ?xml version=1.0?
 ResponseErrorsErrorCodeAuthFailure/CodeMessageSignature not
 provided/Message/Error/Errors

  My environment is OpenStack (the Juno release) deployed by Fuel 6.0.
 Tempest is from master branch.

  I found that the issue was related to boto (Tempest installs it into
 virtual environment as a dependency). The last available release of boto is
 2.36.0.
 When this version of boto is installed, EC2 tests don't work. But if I
 install boto 2.34.0 instead of 2.36.0, all EC2 tests will have success.

  Any thoughts?

  Regards,
 Yaroslav Lobankov.


 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: 
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [Sahara] Sahara testing for Juno

2014-10-15 Thread Yaroslav Lobankov
Hello everyone,

I have been testing Sahara for two weeks and would like to share some
results with you [1].
While testing I used new images built for the Juno release of Sahara.

Images for Vanilla plugin are available here [2].
Images for HDP plugin are available here [3].
Image for Spark plugin is available here [4].
Unfortunately, for now there are no links in the Sahara documentation to
download images for CDH plugin.

A bunch of integration tests for Sahara you can find here [5].

[1]
https://docs.google.com/a/mirantis.com/spreadsheets/d/1F_Rti8UP5Avv8w_W8cf-5vkzosBdSzS8pn6Si_sjifw/edit#gid=0
[2]
http://docs.openstack.org/developer/sahara/userdoc/vanilla_plugin.html#vanilla-plugin
[3]
http://docs.openstack.org/developer/sahara/userdoc/hdp_plugin.html#images
[4]
http://docs.openstack.org/developer/sahara/userdoc/spark_plugin.html#images
[5] https://github.com/ylobankov/sahara_integration_tests

Regards,
Yaroslav Lobankov
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev