Thursday, 2017-07-13

*** dave-mccowan has joined #openstack-rally00:09
*** LindaWang has joined #openstack-rally00:44
openstackgerritBoris Pavlovic proposed openstack/rally master: WIP: Add server console log to scenario output data  https://review.openstack.org/48315001:32
openstackgerritBoris Pavlovic proposed openstack/rally master: WIP: Add server console log to scenario output data  https://review.openstack.org/48315001:37
*** psuriset has quit IRC01:42
*** ilbot3 has quit IRC01:45
a8K8U1LOP[From Gitter] geyao0619 : Hi, I failed the 'gate-rally-dsvm-rally-heat’ for jenkins.01:48
a8K8U1LOP[From Gitter] geyao0619 : I got ‘HTTPNotFound’. just wondering if‘recheck’ will solve it?http://logs.openstack.org/94/476694/9/check/gate-rally-dsvm-rally-heat/6f52057/rally-plot/results.html.gz#/HeatStacks.create_stack_and_scale-2/failures01:48
*** ilbot3 has joined #openstack-rally01:49
*** itlinux has joined #openstack-rally02:10
LindaWangHi guys02:31
LindaWangWhen I run "rally verify configure-verifier" in rally 0.9.102:32
LindaWangthe param lock_path is missing in tempest.conf02:34
LindaWangCause there is no dir named .rally/verification/tempest/data/lock_files_uuid any more.02:34
LindaWangSo I am wondering what the param is for.02:35
LindaWang2 tests (tempest.api.compute.test_quotas.QuotasTestJSON.test_get_default_quotas[id-9bfecac7-b966-4f47-913f-1a9e2c12134a]02:35
LindaWangtempest.api.compute.test_quotas.QuotasTestJSON.test_get_quotas[id-f1ef0a97-dbbb-4cca-adc5-c9fbc4f76107]) failed due to this issue02:35
LindaWangAnybody would like to help? Thanks02:36
openstackgerritMerged openstack/rally master: [Install] Fix postgresql installation  https://review.openstack.org/48199802:36
openstackgerritchenhb proposed openstack/rally master: Fix an issue of database migration  https://review.openstack.org/48316302:49
*** aojea has joined #openstack-rally02:53
*** aojea has quit IRC02:58
a8K8U1LOP[From Gitter] zhangzhihui1 : in my tempest.conf02:58
a8K8U1LOP[From Gitter] zhangzhihui1 : [oslo_concurrency]02:58
a8K8U1LOP[From Gitter] zhangzhihui1 : lock_path = /root/.rally/verification/verifier-0a571769-31d4-4ab9-ab28-34c88b9ac4c2/for-deployment-0052293e-7103-4bcb-8147-a97960e50c50/lock_files02:58
a8K8U1LOP[From Gitter] zhangzhihui1 : 'lock_files' is a dir.02:59
*** chhavi has joined #openstack-rally03:02
openstackgerritchenhb proposed openstack/rally master: Fix an issue of database migration  https://review.openstack.org/48316303:17
*** dave-mccowan has quit IRC03:24
*** psuriset has joined #openstack-rally03:52
LindaWangzhangzhihui1 Which version of rally do you use?04:00
LindaWanga8K8U1LOP: zhangzhihui1 When I run tests in rally 0.8.1, the dir lock_files is there and the param lock_path is right04:02
LindaWang zhangzhihui1 The issue is only for rally 0.9.104:03
a8K8U1LOP[From Gitter] zhangzhihui1 : @ LindaWang  # rally version04:50
a8K8U1LOP[From Gitter] zhangzhihui1 : 0.9.1~dev28004:50
*** anshul has joined #openstack-rally04:59
*** aojea has joined #openstack-rally05:28
*** psuriset has quit IRC05:30
*** rcernin has joined #openstack-rally05:40
openstackgerritchenhb proposed openstack/rally master: Fix an issue of database migration  https://review.openstack.org/48316305:46
*** psuriset has joined #openstack-rally05:47
*** aojea has quit IRC05:53
*** lpetrut has joined #openstack-rally06:06
*** psuriset has quit IRC06:48
*** pcaruana has joined #openstack-rally06:52
*** tesseract has joined #openstack-rally06:56
*** psuriset has joined #openstack-rally07:01
*** lpetrut has quit IRC07:07
LindaWang zhangzhihui1 I doubt if the way I installed rally was wrong.07:14
LindaWangzhangzhihui1 I did not use the install_rally.sh to install07:16
*** aojea has joined #openstack-rally07:17
LindaWangzhangzhihui1 What I use is these lines below:07:19
LindaWang    mkdir -p /etc/rally && \07:19
LindaWang    printf "[database]\nconnection = 'sqlite:////var/lib/rally/database/rally.sqlite'" > /etc/rally/rally.conf && \07:19
LindaWang    mkdir -p /var/lib/rally/database && rally-manage db create07:19
LindaWangzhangzhihui1 Do you know if it is right?07:20
*** alexchadin has joined #openstack-rally07:25
LindaWangzhangzhihui1 Or, could you help test rally 0.9.1 locally? I see your rally version is master.07:27
openstackgerritsudhir agarwal proposed openstack/rally master: Replaces uuid.uuid4 with uuidutils.generate_uuid()  https://review.openstack.org/48323907:29
a8K8U1LOP[From Gitter] zhangzhihui1 : do you want to let me to run tempest.api.compute.test_quotas.QuotasTestJSON.test_get_default_quotas?07:32
*** lpetrut has joined #openstack-rally07:34
LindaWangNo, after deployment, just run "rally verify configrue-verifier"07:34
LindaWangTo check is the dir .rally/verification/tempest/data/lock_files_uuid exists07:35
LindaWangSo also check if the param lock_path in tempest.conf has been configured correctly.07:35
*** jose_lausuch has joined #openstack-rally07:37
*** psuriset has quit IRC07:38
*** lpetrut has quit IRC07:43
*** itlinux has quit IRC07:47
openstackgerritAndrey Kurilin proposed openstack/rally master: [ci] Turn off glance scenarios  https://review.openstack.org/48324707:49
a8K8U1LOP[From Gitter] zhangzhihui1 : ok07:54
a8K8U1LOP[From Gitter] zhangzhihui1 : .rally/verification/tempest/data/lock_files_uuid: No such file or directory, but test is success07:55
a8K8U1LOP[From Gitter] zhangzhihui1 : lock_path = /root/.rally/verification/verifier-0a571769-31d4-4ab9-ab28-34c88b9ac4c2/for-deployment-804455f2-9fec-497c-a840-72186052cb94/lock_files07:55
a8K8U1LOP[From Gitter] zhangzhihui1 :  tempest.api.compute.test_quotas.QuotasTestJSON.test_get_quotas ... success [2.223s]07:56
LindaWangThen, could you help check if the way I insatlled rally is correct?07:57
a8K8U1LOP[From Gitter] zhangzhihui1 : and i don't know if the way you installed rally is right. we can ask @andreykurilin07:59
LindaWangzhangzhihui1 Fine. Thanks07:59
LindaWangandreykurilin:  Could you help check the way I installed rally is right? I did not user install_rally.sh08:05
LindaWangandreykurilin:08:06
LindaWangmkdir -p /etc/rally && \08:06
LindaWangprintf "[database]\nconnection = 'sqlite:////var/lib/rally/database/rally.sqlite'" > /etc/rally/rally.conf && \08:06
LindaWangmkdir -p /var/lib/rally/database && rally-manage db create08:06
*** serlex has joined #openstack-rally08:18
*** alexchadin has quit IRC08:29
LindaWangzhangzhihui1 There is  no such dir in my system: /root/.rally/verification/verifier-uuid/for-deployment-uuid/lock_files08:32
LindaWangzhangzhihui1 Actually there is no dir named lock_files anywhere.08:32
a8K8U1LOP[From Gitter] zhangzhihui1 : when run tests, the dir will be created08:34
LindaWangI thought it was created by the cli "rally verify configrue-verifier"08:35
LindaWangBut why it failed to run tempest.api.compute.test_quotas.QuotasTestJSON.test_get_default_quotas, complaining that: oslo_config.cfg.RequiredError: value required for option lock_path in group [DEFAULT]08:38
*** e0ne has joined #openstack-rally08:38
a8K8U1LOP[From Gitter] andreykurilin : @geyao0619 hi! sorry, several other OpenStack projects broke our gates. We are trying to localize problems now.08:40
a8K8U1LOP[From Gitter] andreykurilin : @LindaWang, @zhangzhihui1 : hi!08:42
LindaWangHi andreykurilin08:43
a8K8U1LOP[From Gitter] zhangzhihui1 : Actually we can set lock_path by ourself, if without setting lock_path, rally will auto create.08:43
a8K8U1LOP[From Gitter] andreykurilin : rally can be installed manually and by the helper script. it doesnt metter for rally code itself08:43
a8K8U1LOP[From Gitter] andreykurilin : about lock_path: it is the same as image and some other options. Rally creates the directory right before running actual verification08:44
a8K8U1LOP[From Gitter] andreykurilin : can you share an error of failed test?08:44
LindaWangandreykurilin: http://paste.openstack.org/raw/615232/08:48
*** ushkalim has joined #openstack-rally08:55
*** alexchadin has joined #openstack-rally08:58
openstackgerritchenhb proposed openstack/rally master: Print the messages what can be traced back to real address  https://review.openstack.org/48327109:02
*** oanufrii has joined #openstack-rally09:03
a8K8U1LOP[From Gitter] andreykurilin : @LindaWang: do you use the latest tempest?09:09
LindaWangandreykurilin: tempest 14.0.009:09
LindaWangrally 0.9.109:10
a8K8U1LOP[From Gitter] andreykurilin : ok, it looks like tempest team changed the location of the options in 15+ and our code sets the option in new way. Can you check that you have oslo_concurrency section with lock_path variable in the config?09:11
*** tosky has joined #openstack-rally09:12
a8K8U1LOP[From Gitter] andreykurilin : Folks: our gates should be unblocked right after https://review.openstack.org/48324709:13
LindaWanga8K8U1LOP: andreykurilin: the var lock_path in  session oslo_concurrency is in tempest.conf09:20
*** a8K8U1LOP has quit IRC09:20
*** rallydev-bot has joined #openstack-rally09:21
rallydev-bot[From Gitter] andreykurilin : In this case, I have to solutions: use tempest 15+ :) propose a patch, which will set an old variable too here - https://github.com/openstack/rally/blob/master/rally/plugins/openstack/verification/tempest/context.py#L69-L7009:22
LindaWangandreykurilin: The reason we Functest team uses tempest 14.0.0 is that the upper stream openstack Ocata recommends that version09:26
LindaWangandreykurilin: https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt?h=stable/ocata09:26
*** mvk has quit IRC09:28
rallydev-bot[From Gitter] andreykurilin : LindaWang: can you update propose a patch to rally for setting the right option?09:36
LindaWangandreykurilin: I have no idea how rally handles that option with different versions of tempest?09:39
rallydev-bot[From Gitter] andreykurilin : I think any version of tempest will no fail if additional options,which are not used, will be specified09:40
rallydev-bot[From Gitter] andreykurilin : so we can specify two options09:40
rallydev-bot[From Gitter] andreykurilin : old one and new one09:40
rallydev-bot[From Gitter] andreykurilin : and everything should work09:40
LindaWangSo could you help with that when you are available? I'd really appreciate it.09:50
*** mvk has joined #openstack-rally09:55
*** alexchadin has quit IRC10:06
rallydev-bot[From Gitter] chenhb-zte : @andreykurilin yup, saw the patch,  expect  gates will be right.10:18
rallydev-bot[From Gitter] andreykurilin : LindaWang: I'm available now and ready to help you to make a patch to rally :)10:20
LindaWangandreykurilin:  Thanks10:20
openstackgerritMerged openstack/rally master: [ci] Turn off glance scenarios  https://review.openstack.org/48324710:21
LindaWangandreykurilin:  A quick question: Is the var floating_network_name in tempest.conf supported by rally 0.9.1+?10:24
rallydev-bot[From Gitter] zhangzhihui1 : @andreykurilin  https://review.openstack.org/#/c/433013/ give us some advice10:26
rallydev-bot[From Gitter] MaXinjian : @andreykurilin  https://review.openstack.org/#/c/421088/  I have beem stuck on this case for a long time...10:28
rallydev-bot[From Gitter] andreykurilin : LndaWang: yes. if rally finds a public network while config generation, it puts it into the config as floating_network_name10:28
rallydev-bot[From Gitter] andreykurilin : @MaXinjian  @zhangzhihui1 sorry for the delay, we spent time trying to fix our CI. will comment these patches today10:29
LindaWangandreykurilin:  Is the var floating_network_name also influenced by tempest version?10:29
*** yamamoto has quit IRC10:31
rallydev-bot[From Gitter] andreykurilin : I do not think so10:31
LindaWangandreykurilin: ok10:34
*** mvk has quit IRC10:34
LindaWangandreykurilin:  Is floating_network_name exactly the name of public_network_id in tempest.conf?10:35
LindaWangandreykurilin:  I find in some certain SUTs, public_network_id exists which floating_network_name is missing in rally 0.9.110:36
rallydev-bot[From Gitter] andreykurilin : hm10:36
rallydev-bot[From Gitter] andreykurilin : do you have any public networks there?10:36
LindaWangandreykurilin:  yes,10:37
rallydev-bot[From Gitter] andreykurilin : so rally lists all networks via neutron, then filter them by active status and external router10:37
LindaWangandreykurilin: Cause public_network_id is configured correctly10:37
rallydev-bot[From Gitter] andreykurilin : if such networks are available, rally takes the first one, puts its id to public_network_id and its name into floating_network_name10:38
rallydev-bot[From Gitter] andreykurilin : if public_network_id is correct, the floating_network_name should be configured too. they use the same if check for setting10:39
LindaWangOk, I will check that later.10:40
LindaWangandreykurilin: Do you still remember the issue about admin role when running rally?10:41
LindaWangandreykurilin:  I sent you one email 4 days ago.10:41
rallydev-bot[From Gitter] andreykurilin : wow, sorry, It looks like I forgot to send a reply10:42
LindaWangandreykurilin:  Talk to you later. A conference offline to join now.10:45
*** lpetrut has joined #openstack-rally10:45
LindaWangandreykurilin:  I am wondering if the SUT has strict limit about resource management, and only the user with admin role can be allowed to take actions10:46
LindaWangandreykurilin: Then how can I run rally on the SUT?10:47
rallydev-bot[From Gitter] andreykurilin : first of all, it sounds really weird. I mean it is a hard to understand such decision(restriction). the seconde question: I do not know what is SUT, so please explain :)10:48
rallydev-bot[From Gitter] andreykurilin : In general I see two options10:48
rallydev-bot[From Gitter] andreykurilin : 1) you can use roles context, which allows to assign any role to new users. 2)  use existing users with the right roles10:49
rallydev-bot[From Gitter] andreykurilin : BUT, as far as I know, the error which you have ususally raises when the member role is not proper configured in the cloud10:49
*** mvk has joined #openstack-rally10:50
rallydev-bot[From Gitter] andreykurilin : to check this, you should try to create a new project, a new user in it and assign a member role (this step is quite important). then try to perform actions from this user10:50
*** jkilpatr has quit IRC11:01
*** aojea has quit IRC11:04
*** aojea has joined #openstack-rally11:06
*** aojea has quit IRC11:09
*** yamamoto has joined #openstack-rally11:13
*** mvk has quit IRC11:13
*** yamamoto has quit IRC11:18
*** yamamoto has joined #openstack-rally11:21
*** mvk has joined #openstack-rally11:26
*** yamamoto has quit IRC11:26
*** psuriset has joined #openstack-rally11:27
*** yamamoto has joined #openstack-rally11:36
*** e0ne_ has joined #openstack-rally11:37
*** lpetrut_ has joined #openstack-rally11:38
*** e0ne has quit IRC11:39
*** jkilpatr has joined #openstack-rally11:39
*** yamamoto has quit IRC11:40
*** lpetrut has quit IRC11:41
*** yamamoto has joined #openstack-rally11:50
*** yamamoto has quit IRC11:54
openstackgerritbhavani proposed openstack/rally master: Add a hacking rule for string interpolation at logging  https://review.openstack.org/48331411:57
*** dave-mccowan has joined #openstack-rally12:01
*** reveller has quit IRC12:12
*** yamamoto has joined #openstack-rally12:17
openstackgerritAndrey Kurilin proposed openstack/rally master: [cli] "rally task list" improvements  https://review.openstack.org/48247312:21
openstackgerritbhavani proposed openstack/rally master: Handle log message interpolation by the logger in common/  https://review.openstack.org/48331412:28
*** alexchadin has joined #openstack-rally12:48
*** catintheroof has joined #openstack-rally12:56
*** deep-book-gk_ has joined #openstack-rally13:00
*** deep-book-gk_ has left #openstack-rally13:01
*** reveller has joined #openstack-rally13:07
*** alexchadin has quit IRC13:09
*** LindaWang has quit IRC13:13
*** LindaWang has joined #openstack-rally13:14
LindaWang\13:18
*** aojea has joined #openstack-rally13:24
*** LindaWang has quit IRC13:25
*** aojea has quit IRC13:25
*** aojea has joined #openstack-rally13:25
openstackgerritAndrey Kurilin proposed openstack/rally master: [cli] "rally task list" improvements  https://review.openstack.org/48247313:39
*** jkilpatr has quit IRC13:42
*** jkilpatr has joined #openstack-rally13:47
*** LindaWang has joined #openstack-rally14:07
*** e0ne_ has quit IRC14:16
*** aarefiev is now known as aarefiev_afk14:21
*** itlinux_ has joined #openstack-rally14:22
*** e0ne has joined #openstack-rally14:24
*** LindaWang has quit IRC14:31
*** LindaWang has joined #openstack-rally14:31
openstackgerritAndrey Kurilin proposed openstack/rally master: Remove existing_users context  https://review.openstack.org/45881014:31
*** jose_lausuch has quit IRC14:34
LindaWangandreykurilin:  The SUT I am testing is one oommercial version of Openstack.14:35
LindaWangandreykurilin: The SUT I am testing is one commercial version of Openstack.14:36
LindaWangandreykurilin:  1) Where is the roles context that can be used?14:36
rallydev-bot[From Gitter] andreykurilin : Are you sure that regular user which cannot do anything is an expected behaviuor of that cloud?14:37
LindaWangYes, I am sure. The new user with admin role can be allowed to take actions in that SUT14:41
*** itlinux_ has quit IRC14:42
rallydev-bot[From Gitter] andreykurilin : I'm not talking about a new user with admin role.  It is logical that a user with admin role can do anything :) I wonder just about regular users. Normally, new user without any roles cannot perform any action is the cloud (like in your case) and after applying the magic role member the new user obtains enough rights for doing something in the cloud14:43
rallydev-bot[From Gitter] andreykurilin : ok, if you think that your case is not a bug, but a feature, I'm ok too :)14:44
*** serlex has quit IRC14:44
rallydev-bot[From Gitter] andreykurilin : so let's talk who we can interact with such case14:45
LindaWangWhat I mean is that the new user without admin role can not be allowed to do anything14:45
rallydev-bot[From Gitter] andreykurilin : ok14:45
*** anshul has quit IRC14:47
rallydev-bot[From Gitter] andreykurilin : solution #1: rally can create new users for workload or use existing users. In this case you just need to create several test users with enough rights to perform actions in the cloud and specify that users in rally deployment config.14:47
rallydev-bot[From Gitter] andreykurilin : An example:  https://github.com/openstack/rally/blob/master/samples/deployments/existing-with-predefined-users.json#L13-L23 (note: if you use keystone v3, specify users with using keystone v3 terms)14:48
rallydev-bot[From Gitter] andreykurilin : solution #2 : use roles context. In this case rally will create users and then apply specified roles for you14:49
rallydev-bot[From Gitter] andreykurilin : https://rally.readthedocs.io/en/latest/plugins/plugin_reference.html#roles-context14:49
rallydev-bot[From Gitter] andreykurilin : An example: https://github.com/openstack/rally/blob/master/samples/tasks/contexts/roles.json#L1714:49
rallydev-bot[From Gitter] andreykurilin : NOTE: the first solution will work for all rally scenarios and context. The second solution can led to some issues at validation step14:50
LindaWangActually I use only on user(admin) in the creds when I created rally deployment14:50
LindaWangActually I use only one user(admin) in the creds when I created rally deployment14:50
rallydev-bot[From Gitter] andreykurilin : yes. specifing just one user(admin) is a case when rally creates new users for workload14:52
LindaWangI think the user named admin is only for creating the rally deployment.14:54
LindaWangWhen it comes to different tests, new different users will be created then.14:55
rallydev-bot[From Gitter] andreykurilin : yes14:55
*** ushkalim has quit IRC14:56
LindaWangFor solution 1, the additional added users in the file existing-with-predefined-users.json, will be used when running all scenarios? If so, there will be no new users created, right?14:58
rallydev-bot[From Gitter] andreykurilin : yes14:58
LindaWangSo in my case here, i have to assign admin role to these users beforehand?14:59
rallydev-bot[From Gitter] andreykurilin : yup14:59
LindaWangHow to guarantee the number of additional added users in the file existing-with-predefined-users.json is enough for all these tests?15:00
*** e0ne has quit IRC15:01
rallydev-bot[From Gitter] andreykurilin : LindaWang: ok. so rally takes a random user from the list. If it will be just one users, all scenarios and all iterations will be executed from it. If you have more  users, the usage will be fuzzy. But again, even one user will be enough. NOTE: you need to remove "users" context section from the task config in such case. If "users" sections is present there, rally eng15:02
rallydev-botine will force to create new users15:02
LindaWangNow I prefer to solution 215:04
rallydev-bot[From Gitter] andreykurilin : heh15:04
LindaWangBut I have no idea when I run these command: http://paste.openstack.org/raw/615280/15:05
rallydev-bot[From Gitter] andreykurilin : you need to modify /home/opnfv/repos/functest/functest/opnfv_tests/openstack/rally/task.yaml15:06
LindaWangHow can I configure the roles.json file?15:06
*** serlex has joined #openstack-rally15:06
LindaWanghttps://github.com/opnfv/functest/blob/master/functest/opnfv_tests/openstack/rally/task.yaml15:06
LindaWangNo roles can be configured in this file.15:07
*** serlex has left #openstack-rally15:07
rallydev-bot[From Gitter] andreykurilin : Actually, it would be much easier to you to return to solution #115:08
LindaWangWell, fine :)15:09
*** e0ne has joined #openstack-rally15:09
rallydev-bot[From Gitter] andreykurilin : Each of workload(scenario) can require theoretically different roles, so the roles context should be specified for each workload separately. Based on the fact that your task config is splitted accross a lot of files (see https://github.com/opnfv/functest/tree/master/functest/opnfv_tests/openstack/rally/scenario), it will take much time15:09
LindaWangI am just wondering how to realize solution #2 in functest15:09
rallydev-bot[From Gitter] andreykurilin : you will need to add roles context like in example to each of context sections here - https://github.com/opnfv/functest/blob/master/functest/opnfv_tests/openstack/rally/scenario/opnfv-authenticate.yaml#L3-L415:10
rallydev-bot[From Gitter] andreykurilin : and to other files15:10
rallydev-bot[From Gitter] andreykurilin : As you can see, you task config uses macros and it supports existing users. It means that in case of solution #1, you will need just to create new users transmit them into rally deployment and transmit into task a argument to use existing users15:12
LindaWangWhat is the purpose of the var tmpl_dir and sup_dir? ('tmpl_dir': '/home/opnfv/repos/functest/functest/opnfv_tests/openstack/rally/scenario/templates', 'sup_dir': '/home/opnfv/repos/functest/functest/opnfv_tests/openstack/rally/scenario/support')15:12
rallydev-bot[From Gitter] andreykurilin : I do not know what is it)15:13
LindaWanghttps://github.com/opnfv/functest/tree/master/functest/opnfv_tests/openstack/rally/scenario/templates15:13
rallydev-bot[From Gitter] andreykurilin : I think it is templates for heat15:14
LindaWangI thought these 2 params (tmpl_dir and sup_dir) were required by rally15:14
rallydev-bot[From Gitter] andreykurilin : possibly, these parameters are required by you script, but not rally itself15:19
*** yingjun has joined #openstack-rally15:20
*** jkilpatr has quit IRC15:23
*** rcernin has quit IRC15:27
LindaWangDo you mean these two lines should be removed for solution #1 https://github.com/opnfv/functest/blob/master/functest/opnfv_tests/openstack/rally/scenario/opnfv-authenticate.yaml#L3-L415:27
rallydev-bot[From Gitter] andreykurilin : no15:28
LindaWangRemove the session of context for all scenario?15:28
rallydev-bot[From Gitter] andreykurilin : let me try to explain in another way15:28
LindaWangThanks, I just can not understand this sentence: you need to remove "users" context section from the task config in such case. If "users" sections is present there, rally engine will force to create new users15:29
rallydev-bot[From Gitter] andreykurilin : an example of rally task which should launch two scenarios - http://xsnippet.org/362640/15:32
rallydev-bot[From Gitter] andreykurilin : both of scenarios has context section with specified users ctx15:33
rallydev-bot[From Gitter] andreykurilin : if you launch that scenario, rally will not even look at existance of real users in deployment config, the new users will be created, because it is specified in the json15:34
LindaWangYEP15:34
rallydev-bot[From Gitter] andreykurilin : "users": {"tenants": 2, "users_per_tenant": 2} means that user asks rally to create 2 tenants with 2 users in it, so rally will do it for you.15:35
rallydev-bot[From Gitter] andreykurilin : an another example - http://xsnippet.org/362641/15:35
rallydev-bot[From Gitter] andreykurilin : the first workload is not changed15:35
rallydev-bot[From Gitter] andreykurilin : rally will again ignore "users" section of deployment config and create new users15:36
rallydev-bot[From Gitter] andreykurilin : BUT the config for the second workload is changed15:36
rallydev-bot[From Gitter] andreykurilin : there is no users context15:36
rallydev-bot[From Gitter] andreykurilin : in this case rally will check a deployment and if "users" are there, they will be used for workload. If not -> the new ones will be created15:37
LindaWangSo my question is how to modify this file https://github.com/opnfv/functest/blob/master/functest/opnfv_tests/openstack/rally/scenario/opnfv-authenticate.yaml#L3-L4 to avoid new user created by rally?15:38
*** pcaruana has quit IRC15:38
rallydev-bot[From Gitter] andreykurilin : as from the previous example, it is become obvious that each workload have separated contexts, so you need(do not do it before reading the next my message) to remove all contexts sections - https://github.com/opnfv/functest/blob/master/functest/opnfv_tests/openstack/rally/scenario/opnfv-authenticate.yaml#L3-L4 and https://github.com/opnfv/functest/blob/master/functest15:40
rallydev-bot/opnfv_tests/openstack/rally/scenario/opnfv-authenticate.yaml#L14-L15 and15:40
rallydev-bot[From Gitter] andreykurilin : so on15:40
rallydev-bot[From Gitter] andreykurilin : Here is another thing that you should know about rally -> task configs are not just regular JSON/YAML files, they are actually jinja2 templates, which allows to optimize some things, split one big task config into separate files, add if...else blocks, etc15:41
rallydev-bot[From Gitter] andreykurilin : the author of https://github.com/opnfv/functest/tree/master/functest/opnfv_tests/openstack/rally knew it and make the task config configurable. A lot of things can be configured there. And one of those things - where to add users context to all workloads or not15:42
LindaWangOk, got it. For authenticate sceanrio, remove all contexts sections in opnfv-authenticate.yaml, right?15:43
rallydev-bot[From Gitter] andreykurilin : so you do not need to remove anything, you just need to transmit the right argument into the task, so existing users will be used15:43
rallydev-bot[From Gitter] andreykurilin : It looks like you need just to transmit "use_existing_users" into task-args here - http://paste.openstack.org/raw/615280/15:44
LindaWangok, I will try that15:45
LindaWangThanks for your detailed explanation and patience. :)15:47
openstackgerritAndrey Kurilin proposed openstack/rally master: [wip][cli] "rally task list" improvements  https://review.openstack.org/48247315:52
LindaWangI will try to update the patch about lock_path, if we have to use tempest 14.0.015:55
*** e0ne has quit IRC15:55
*** aojea has quit IRC15:55
*** aojea has joined #openstack-rally16:02
*** LindaWang has quit IRC16:04
*** LindaWang has joined #openstack-rally16:04
*** LindaWang has quit IRC16:06
*** aojea has quit IRC16:07
*** aojea has joined #openstack-rally16:12
*** aojea has quit IRC16:16
*** tesseract has quit IRC16:19
*** aojea has joined #openstack-rally16:21
*** aojea has quit IRC16:25
*** aojea has joined #openstack-rally16:30
*** aojea has quit IRC16:36
*** aojea has joined #openstack-rally16:39
*** lpetrut_ has quit IRC16:42
*** aojea has quit IRC16:44
*** itlinux has joined #openstack-rally16:45
*** aojea has joined #openstack-rally16:48
*** aojea has quit IRC16:52
*** aojea has joined #openstack-rally16:57
*** aojea has quit IRC17:02
*** oanufrii has quit IRC17:02
*** aojea has joined #openstack-rally17:06
*** e0ne has joined #openstack-rally17:09
*** aojea has quit IRC17:10
*** aojea has joined #openstack-rally17:15
*** jkilpatr has joined #openstack-rally17:18
*** aojea has quit IRC17:20
*** aojea has joined #openstack-rally17:24
*** jkilpatr has quit IRC17:26
*** harlowja has quit IRC17:27
*** aojea has quit IRC17:29
*** yingjun has quit IRC17:29
*** tosky has quit IRC17:34
*** mvk has quit IRC18:01
*** jkilpatr has joined #openstack-rally18:16
*** e0ne has quit IRC18:16
*** mvk has joined #openstack-rally18:35
*** pcaruana has joined #openstack-rally18:38
*** harlowja has joined #openstack-rally18:54
*** chandankumar has quit IRC19:00
*** tosky has joined #openstack-rally19:06
*** chhavi has quit IRC19:38
*** pcaruana has quit IRC19:52
*** harlowja has quit IRC20:19
*** lpetrut_ has joined #openstack-rally20:21
*** harlowja has joined #openstack-rally20:22
*** aojea has joined #openstack-rally20:35
*** aojea has quit IRC20:41
*** lpetrut_ has quit IRC22:06
*** dpaterson has quit IRC22:17
*** dpaterson has joined #openstack-rally22:20
*** itlinux has quit IRC22:58
*** tosky has quit IRC23:00
*** catintheroof has quit IRC23:03
*** aojea has joined #openstack-rally23:28
*** aojea has quit IRC23:33
*** aojea has joined #openstack-rally23:37
*** aojea has quit IRC23:41
*** aojea has joined #openstack-rally23:46
*** aojea has quit IRC23:51
*** itlinux has joined #openstack-rally23:56

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!