[openstack-dev] [Openstack-operators] Destructive / HA / fail-over scenarios

Hi OpenStack developers and operators, we are going to create the test suite for destructive testing of OpenStack clouds. We want to hear your feedback and ideas about possible destructive and failover scenarios which we need to check. Which scenarios we need to check if we want to make sure

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

faults as lib is really nice idea but tests scope can > go in Tempest under HW_scenario (or something else) till it does not break > basic principle of Tempest. > > > > Thanks > > gmann > > > > *From:* Timur Nurlygayanov [mailto:tnurlygaya...@mirantis.com] >

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

ts/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

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

t; > Thanks for picking this up, that is interesting for me. > > 2016-09-22 5:58 GMT-07:00 Timur Nurlygayanov <tnurlygaya...@mirantis.com>: > > > > we have an idea to create the test suite with destructive/HA and advanced > > end-user scenarios for the OpenStack

Re: [openstack-dev] [QA][infra][all] Measuring code coverage in integration tests

Hi milan, we have measured the test coverage for OpenStack components with coverage.py tool [1]. It is very easy tool and it allows measure the coverage by lines of code and etc. (several metrics are available). [1] https://coverage.readthedocs.io/en/coverage-4.2/ On Tue, Sep 27, 2016 at 1:06

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

Hi team, we have an idea to create the test suite with destructive/HA and advanced end-user scenarios for the OpenStack clusters. This test suite will contains advanced scenario integration tests for OpenStack clusters to make sure that the cluster is ready for the production. The test cases

Re: [openstack-dev] [Fuel] new branch stable/2.9 for fuel-devops

Good news :) Thank you! On Tue, Jan 12, 2016 at 2:28 PM, Dennis Dmitriev wrote: > + mos-dev & mos-qa > > 12.01.2016 13:26, Dennis Dmitriev пишет: > > Hi all! > > > > Framework QA team is going to merge a lot of changes to the > > fuel-devops repository [0] , to

Re: [openstack-dev] [Fuel] [QA] [Tests] MOS integration tests in SWARM test suite

and? > > > Best regards, > Boris Pavlovic > > On Mon, Dec 7, 2015 at 6:09 AM, Timur Nurlygayanov < > tnurlygaya...@mirantis.com> wrote: > >> Hi Fuel team, >> >> we have a lot of automated integration tests for OpenStack verification >> and we wan

[openstack-dev] [Fuel] [QA] [Tests] MOS integration tests in SWARM test suite

Hi Fuel team, we have a lot of automated integration tests for OpenStack verification and we want to add execution of these tests to Fuel SWARM test suite (to run these tests on daily basis and on per commit basis). We used our own bash scripts to deploy OpenStack environments with Fuel before,

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

Hi Andrey, As far as I remember from the last usage of fuel master node, there was > Centos + py26 installation. Python 2.6 is old enough and sometimes it is > hard to launch some application on fuel node without docker (image with > py27/py3). Are you planning to provide py27 at least or my note

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

Hi team, I think it too late to make such significant changes for MOS 8.0 now, but I'm ok with the idea to remove docker containers in the future releases if our dev team want to do this. Any way, before we will do this, we need to plan how we will perform updates between different releases with

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

d, but switching from docker to plain is much > > simpler. > > > > > > > > > > Vladimir Kozhukalov > > > > On Fri, Nov 20, 2015 at 6:47 PM, Bogdan Dobrelya <bdobre...@mirantis.com > > <mailto:bdobre...@mirantis.com>> wrote: > > > > On 2

[openstack-dev] [Horizon] [Nova] [Cinder] Need to add selection of availability zone for new volume

Hi OpenStack dev team, we found issue [1] in Horizon (probably, in Nova API too), which blocks the ability to boot VMs with option Instance Boot Source = Boot from image (creates new volume) in case when we have several Availability Zones in Nova and Cinder - it will fail with error Failure

Re: [openstack-dev] [Sahara] [QA] [tests coverage] Can we add CI job to control the unit tests coverage?

by unit tests or not. But I am not sure that this gate should be voting (if I understand you correct), because new patch may not be just a new code, committer may delete something or fix typos in docsting, etc. On Thu, Jul 2, 2015 at 8:15 PM, Timur Nurlygayanov tnurlygaya...@mirantis.com wrote

Re: [openstack-dev] [puppet] [Nova] Do we really need to use rabbit_ha_queues parameter?

I have reviewed the git history and looks like we can just fix unit tests for puppet manifests. I'm going to do this. On Fri, Jul 3, 2015 at 1:03 PM, Timur Nurlygayanov tnurlygaya...@mirantis.com wrote: Hi all, I have updated puppet manifests for all OpenStack components to fix the logic

[openstack-dev] [puppet] [Nova] Do we really need to use rabbit_ha_queues parameter?

Hi all, I have updated puppet manifests for all OpenStack components to fix the logic of configuration of rabbit_ha_queues parameter [1] but Nova puppet unit tests failed because these tests expect that we will use rabbit_ha_queues=True for one-controller-node installations [2], [3]. Do we have

[openstack-dev] [Sahara] [QA] [tests coverage] Can we add CI job to control the unit tests coverage?

Hi all, I suggest to add CI job which will check the unit tests coverage for Sahara repository and will set -1 for commits with new code and without unit tests (if we have some degradation of tests coverage). This job successfully works for Rally project and it helps to organize the right code

[openstack-dev] [Sahara] [QA] [tests coverage] Can we add CI job to control the unit tests coverage?

Hi all, I suggest to add CI job which will check the unit tests coverage for Sahara repository and will set -1 for commits with new code and without unit tests (if we have some degradation of tests coverage). This job successfully works for Rally project and it helps to organize the right code

[openstack-dev] [Murano] [QA] [tests coverage] Can we add CI job to control the unit tests coverage?

Hi all, I suggest to add CI job which will check the unit tests coverage for Murano repository and will set -1 for commits with new code and without unit tests (if we have some degradation of tests coverage). This job successfully works for Rally project and it helps to organize the right code

Re: [openstack-dev] [Sahara] [QA] [tests coverage] Can we add CI job to control the unit tests coverage?

that contains mostly deployment code fully tested by integration tests we'll have ~70% unit tests coverage. Thanks. On Thu, Jul 2, 2015 at 8:55 PM, Timur Nurlygayanov tnurlygaya...@mirantis.com wrote: Hi all, I suggest to add CI job which will check the unit tests coverage for Sahara repository

[openstack-dev] [Horizon] [tests] [dsvm] Tests failed because of timeout during the images upload

Hi team, I investigated the latest failed Horizon integration dsvm jobs [1] and found that many of them failed because of timeouts during the upload of image (in function 'create_image' [2]), on step '_wait_till_spinner_disappears' [3], where we wait while 'div.*modal-backdrop*' will disappear.

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

Hi Doug, I suggest to use some version for neutron-*aas plugins, probably, 1.0.0 just to have one pattern for all components. If we will not use numbers for the first releases (or release candidates) it will be hard to understand what the version it is. What do you think about it? Thank you! On

Re: [openstack-dev] [fuel] [HA] How long we need to wait for cloud recovery after some destructive scenarios?

#HA_Intro_and_Concepts On Wed, Jun 3, 2015 at 1:06 PM, Timur Nurlygayanov tnurlygaya...@mirantis.com wrote: Looks like I forgot to add the link to [1] in the first email: [1] https://github.com/stackforge/haos On Wed, Jun 3, 2015 at 12:50 PM, Timur Nurlygayanov tnurlygaya...@mirantis.com

[openstack-dev] [fuel] [HA] How long we need to wait for cloud recovery after some destructive scenarios?

Hi team, I'm working on HA / destructive / recovery automated tests [1] for OpenStack clouds and I want to get some expectations from users, operators and developers for the speed of OpenStack recovery after some destructive actions. For example, how long cluster should be unavailable if one of

Re: [openstack-dev] [fuel] [HA] How long we need to wait for cloud recovery after some destructive scenarios?

Looks like I forgot to add the link to [1] in the first email: [1] https://github.com/stackforge/haos On Wed, Jun 3, 2015 at 12:50 PM, Timur Nurlygayanov tnurlygaya...@mirantis.com wrote: Hi team, I'm working on HA / destructive / recovery automated tests [1] for OpenStack clouds and I

Re: [openstack-dev] [qa] SafeConfigParser.write duplicates defaults: bug or feature?

Hi David, it looks like a bug for me (as a user) just because I don't want to get 'dirty' config in the result. And looks like it should be easy to fix, we can just verify parameters from DEFAULT section and add them to the specific section only if we need to set another value for this parameter.

Re: [openstack-dev] [Openstack-operators] [all][qa][gabbi][rally][tempest] Extend rally verfiy to unify work with Gabbi, Tempest and all in-tree functional tests

Hi, I like this idea, we use Rally for OpenStack clouds verification at scale and it is the real issue - how to run all functional tests from each project with the one script. If Rally will do this, I will use Rally to run these tests. Thank you! On Mon, Mar 9, 2015 at 6:04 PM, Chris Dent

Re: [openstack-dev] [Murano] [QA] Automated tests for all Murano applications

it makes sense just to use it in gates and avoid implementing anything else? 1. https://review.openstack.org/#/c/137650/ 2. https://review.openstack.org/#/c/137661/ Best regards, Boris Pavlovic On Tue, Feb 24, 2015 at 12:18 PM, Timur Nurlygayanov tnurlygaya...@mirantis.com wrote: Hi all

Re: [openstack-dev] [QA] Prototype of the script for Tempest auto-configuration

Hi, *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

Re: [openstack-dev] [qa] What does it mean when a network's admin_state_up = false?

Hi Danny, I know that if we will set admin_state_up= false we will disable DHCP service for this network and new VMs will not get network settings by DHCP. On Wed, Dec 31, 2014 at 2:41 AM, Danny Choi (dannchoi) dannc...@cisco.com wrote: Hi, I have a VM with an interface attached to network

Re: [openstack-dev] [Murano] Murano Agent

Hi, murano python client allows to work with Murano API from the console interface (instead of Web UI). To install Murano python client on Ubuntu you can execute the following commands: apt-get update apt-get install python-pip pip install -U pip setuptools pip install python-muranoclient On

Re: [openstack-dev] [qa] Fail to launch VM due to maximum number of ports exceeded

Hi Danny, what about the global ports count and quotas? On Sun, Dec 21, 2014 at 1:32 AM, Danny Choi (dannchoi) dannc...@cisco.com wrote: Hi, The default quota for port is 50. +--++-+ localadmin@qa4:~/devstack$ neutron

Re: [openstack-dev] tempest - object_storage

Hi Anton, it depends on the storage service which you use on this lab. Tempest tests can fail, for example, if the configuration or your object storage has some customizations. Also you can change the tempest configuration to adapt tempest tests for your environment. On my test OpenStack

Re: [openstack-dev] [Murano] Cannot find murano.conf

Hi, looks like this is issues with the installation of Murano requirements with the pip. To fix them I suggest to do the following: *pip install pip -Upip install setuptools -U* and after this try to install Murano requirements again. On Wed, Dec 10, 2014 at 10:46 AM,

Re: [openstack-dev] [Murano] Oslo.messaging error

Hi Raghavendra Lad, looks like Murano services can't connect ot the RabbitMQ server. Could you please share the configuration parameters for RabbitMQ from ./etc/murano/murano.conf ? On Wed, Dec 10, 2014 at 10:55 AM, raghavendra@accenture.com wrote: HI Team, I am installing Murano

Re: [openstack-dev] [qa] How to perform VMs live migration?

Hi Danny, probably information on the following pages can help: http://docs.openstack.org/admin-guide-cloud/content/section_configuring-compute-migrations.html http://kimizhang.wordpress.com/2013/08/26/openstack-vm-live-migration/

Re: [openstack-dev] [QA][Tempest] Gap analysis for using Tempest in production environments

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

Re: [openstack-dev] [tempest] [devstack] Generic scripts for Tempest configuration

://review.openstack.org/#/c/94473/ [2] https://review.openstack.org/#/c/86967/ [3] https://review.openstack.org/#/c/89322/ [4] https://review.openstack.org/#/c/92804/ *From:* Timur Nurlygayanov [mailto:tnurlygaya...@mirantis.com] *Sent:* Friday, October 24, 2014 4:05 AM *To:* OpenStack Development

[openstack-dev] [tempest] [devstack] Generic scripts for Tempest configuration

Hi all, we are using Tempest tests to verify every changes in different OpenStack components and we have scripts in devstack, which allow to configure Tempest. We want to use Tempest tests to verify different clouds, not only installed with devstack and to do this we need to configure Tempest

Re: [openstack-dev] [tempest] [devstack] Generic scripts for Tempest configuration

Yes, got it. I will review this spec. Thank you! On Fri, Oct 24, 2014 at 3:29 PM, Andrey Kurilin akuri...@mirantis.com wrote: Hi Timur! https://review.openstack.org/#/c/94473/ - this is what you need:) On Fri, Oct 24, 2014 at 2:05 PM, Timur Nurlygayanov tnurlygaya...@mirantis.com wrote

Re: [openstack-dev] [Openstack] Glance on swift problem

(it is then in one big object). --- Best regards Sławek Kapłoński sla...@kaplonski.pl Dnia wtorek, 30 września 2014 22:28:11 Timur Nurlygayanov pisze: Hi Slawek, we faced the same error and this is issue with Swift. We can see 100% disk usage on the Swift node during the file upload

[openstack-dev] [Ceph] Why performance of benchmarks with small blocks is extremely small?

Hello all, I installed OpenStack with Glance + Ceph OSD with replication factor 2 and now I can see the write operations are extremly slow. For example, I can see only 0.04 MB/s write speed when I run rados bench with 512b blocks: rados bench -p test 60 write --no-cleanup -t 1 -b 512

Re: [openstack-dev] [Murano] Changes in networking part of Murano

Hi, what if we will add drop down list with the list of all routers which are available in the specific tenant and user will have the ability to select the router during the application configuration? (like now user can select, for example, availability zone or keypair). Regards, Timur On Thu,

Re: [openstack-dev] Rally scenario Issue

Hi Ajay, looks like you need to use NeutronContext feature to configure Neutron Networks during the benchmarks execution. We now working on merge of two different comits with NeutronContext implementation: https://review.openstack.org/#/c/96300 and https://review.openstack.org/#/c/103306 could

[openstack-dev] [Fuel] Issues with hardcoded versions of requirements in specs of packages

Hi team, Today I started to build Fuel ISO from the master branch and with packages with code from the master branches, and have found strange errors: http://jenkins-product.srt.mirantis.net:8080/view/custom_iso/job/custom_master_iso/77/console Looks like we have hardcoded versions of all

Re: [openstack-dev] [Fuel] Issues with hardcoded versions of requirements in specs of packages

with dependencies before this. Thank you. On Mon, Aug 25, 2014 at 6:21 PM, Timur Nurlygayanov tnurlygaya...@mirantis.com wrote: Hi team, Today I started to build Fuel ISO from the master branch and with packages with code from the master branches, and have found strange errors: http://jenkins

Re: [openstack-dev] [Fuel] Issues with hardcoded versions of requirements in specs of packages

Commit with fast fix was submitted: https://review.openstack.org/#/c/116667/ Need review :) I will try to build image with this commit and will send my comments with my results. On Mon, Aug 25, 2014 at 7:55 PM, Timur Nurlygayanov tnurlygaya...@mirantis.com wrote: When I started the build

Re: [openstack-dev] [Murano] Nominations to Murano core

+1, they make really important work! Serg and Steve, congratulations! On Thu, Jun 26, 2014 at 3:29 PM, Stan Lagun sla...@mirantis.com wrote: +1 for both (or should I say +2?) Sincerely yours, Stan Lagun Principal Software Engineer @ Mirantis sla...@mirantis.com On Thu, Jun 26, 2014

[openstack-dev] [Mistral] Integration tests discussion

Hi team, Tomorrow we discussed integration tests for Mistral and looks like we have many ideas how we can improve them and what we also want to test. The ideas were described in this etherpad: https://etherpad.openstack.org/p/MistralNewTestsDesign Please, fill free to add your ideas about our

[openstack-dev] [Mistral] Mistral weekly meeting - meeting minutes

Hi team, Thank you all for participating in Mistral weekly meeting today, meeting minutes are available by the following links: Minutes: http://eavesdrop.openstack.org/meetings/mistral_weekly_meeting/2014/mistral_weekly_meeting.2014-06-09-15.59.html Minutes (text):

Re: [openstack-dev] [Murano] [meetings] Murano bug scrub

, Jun 2, 2014 at 10:13 PM, Timur Nurlygayanov tnurlygaya...@mirantis.com wrote: Thanks for today's bug scrub meeting! The meeting minutes are available by the following links: Minutes: http://eavesdrop.openstack.org/meetings/murano_bug_scrub/2014/murano_bug_scrub.2014-06-02-17.02.html

[openstack-dev] [Mistral] Meeting minutes

Hi all, Thanks to all participants for visiting the Mistral meeting in #openstack-meeting today! The meeting minutes can be found by the following links: Minutes: http://eavesdrop.openstack.org/meetings/mistral_meeting/2014/mistral_meeting.2014-06-02-16.00.html Minutes (text):

Re: [openstack-dev] [Murano] [meetings] Murano bug scrub

/murano_bug_scrub.2014-06-02-17.02.txt Log: http://eavesdrop.openstack.org/meetings/murano_bug_scrub/2014/murano_bug_scrub.2014-06-02-17.02.log.html We plan to continue our meeting 4 June, at 4:00 - 6:00 PM UTC, in *#murano* IRC. You are welcome! On Tue, May 27, 2014 at 2:41 PM, Timur Nurlygayanov

[openstack-dev] [Murano] Murano API improvements

Hi all, We need to rewrite Murano API on new API framework and we have the commit: https://review.openstack.org/#/c/60787 (*Sergey*, sorry, but -1 from me, need to fix small isses) Also, today I created blueprint: https://blueprints.launchpad.net/murano/+spec/murano-api-workers this feature

[openstack-dev] [Murano] [meetings] Murano bug scrub

Hi all, We want to schedule the bug scrub meeting for Murano project to 06/02/14 (June 2), at 1700 UTC. On this meeting we will discuss all new bugs, which we plan to fix in juno-1 release cycle. All actual descriptions of Murano bugs are available here: https://bugs.launchpad.net/murano If you

Re: [openstack-dev] [murano] Proposal to add Ruslan Kamaldinov to murano-core team

+1 Ruslan, congratulations! On Fri, Apr 18, 2014 at 1:41 PM, Timur Sufiev tsuf...@mirantis.com wrote: Ruslan, welcome to the Murano core team :)! On Thu, Apr 17, 2014 at 7:32 PM, Anastasia Kuznetsova akuznets...@mirantis.com wrote: +1 On Thu, Apr 17, 2014 at 7:11 PM, Stan Lagun

[openstack-dev] [murano] Murano bug scrub 04/23/14

Hi all, We have many new bugs in Murano and I suggest to conduct the meeting and discuss all bugs, assign these bugs to developers and set the mailstones. Let's schedule this meeting on 04/23/14, at 16:00 UTC, im #murano IRC. Thank you! -- Timur, QA Engineer OpenStack Projects Mirantis Inc

[openstack-dev] [fuel-dev] [Fuel] Issues about OSTF tests

Hi Fuel team, I have a questions about the OSTF tests for next release 5.0. In this release we plan to include Murano 0.5, which will have significant architecture changes and it will require significant changes in OSTF tests for Murano. For example, we will not support all services, which

[openstack-dev] [Murano] Code review

Hi Murano team, can we review this commit asap: https://bugs.launchpad.net/murano/+bug/1291968? This is fix for the critical issue in release 0.5: #1291968https://bugs.launchpad.net/murano/+bug/1291968 . Thanks! -- Timur, QA Engineer OpenStack Projects Mirantis Inc

Re: [openstack-dev] Separating our Murano PL core in own package

Hi Serg, This idea sounds good, I suggest to use name 'murano.engine.murano_pl' (not just common name like 'language' or 'dsl', but name, which will be based on 'MuranoPL') Do we plan to support the ability to define different languages for Murano Engine? Thank you! On Sun, Mar 23, 2014 at

Re: [openstack-dev] [openstack][Mistral] Adding new core reviewers

+1 from me. Also, in the future, we can join Kirill Izotov to the core team too. On Wed, Mar 19, 2014 at 9:46 PM, Manas Kelshikar ma...@stackstorm.comwrote: +1 On Wed, Mar 19, 2014 at 5:33 AM, Stan Lagun sla...@mirantis.com wrote: +1 for both On Wed, Mar 19, 2014 at 3:35 PM, Renat

[openstack-dev] [Murano] Need to fix issues with OpenStack Global Requirements

Hi team, We have some issues with the requirements for different Murano components: linkhttps://docs.google.com/a/mirantis.com/spreadsheet/pub?key=0Aiup6hoNUUUedGt3cnJIMHAxbTlHdlFDZGhxLS1yRXcoutput=html I suggest to discuss these issues in etherpad:

Re: [openstack-dev] [Mistral] Understanding parameters for tasks and actions

Hi Renat, for me just unclear the following syntacsis: $.image_id what is $ in this case? It will be more clear if we can replace $ to something - any instance with readable name, like global.image_id or context.image_id. looks like $ can be the different in different name spaces. it will be

[openstack-dev] [Mistral] [pylint] Mistral Repository: pylint errors

Hi Mistral team, We have the following critical errors in Mistral repositoryhttps://github.com/stackforge/mistral, whose I suggest to fix: Code E1101 http://pylint-messages.wikidot.com/messages:e1001, occurrences: 231 Code E1002 http://pylint-messages.wikidot.com/messages:e1002, occurrences: 9

[openstack-dev] [Murano] Meeting Minutes 2013-09-23

Hello, Below, you can see the meeting minutes from today's Murano meeting. Minutes: http://eavesdrop.openstack.org/meetings/murano/2013/murano.2013-09-23-15.04.html Minutes (text): http://eavesdrop.openstack.org/meetings/murano/2013/murano.2013-09-23-15.04.txt Log: