Perl 6 - the future is here, just unevenly distributed

IRC log for #openstack-rally, 2017-07-13

| Channels | #openstack-rally index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:09 dave-mccowan joined #openstack-rally
00:44 LindaWang joined #openstack-rally
01:32 openstackgerrit Boris Pavlovic proposed openstack/rally master: WIP: Add server console log to scenario output data  https://review.openstack.org/483150
01:37 openstackgerrit Boris Pavlovic proposed openstack/rally master: WIP: Add server console log to scenario output data  https://review.openstack.org/483150
01:49 ilbot3 joined #openstack-rally
01:49 Topic for #openstack-rally is now Gitter https://gitter.im/rally-dev/Lobby ☁ Review board: https://goo.gl/iYw2m0 ☁ Rally RoadMap: http://goo.gl/JZkmwY ☁ IRC logs http://irclog.perlgeek.de/openstack-rally ☁ Key persons to ask:  andreykurilin, boris-42, amaretskiy, rvasilets, stpierre  â˜ Documentation: https://rally.readthedocs.org/en/latest/ ☁ To publish changes to Rally:
02:10 itlinux joined #openstack-rally
02:31 LindaWang Hi guys
02:32 LindaWang When I run "rally verify configure-verifier" in rally 0.9.1
02:34 LindaWang the param lock_path is missing in tempest.conf
02:34 LindaWang Cause there is no dir named .rally/verification/tempest/data/lock_files_uuid any more.
02:35 LindaWang So I am wondering what the param is for.
02:35 LindaWang 2 tests (tempest.api.compute.test_quotas.QuotasTestJSON.test_get_default_quotas[id-9bfecac7-b966-4f47-913f-1a9e2c12134a]
02:35 LindaWang tempest.api.compute.test_quotas.QuotasTestJSON.test_get_quotas[id-f1ef0a97-dbbb-4cca-adc5-c9fbc4f76107]) failed due to this issue
02:36 LindaWang Anybody would like to help? Thanks
02:36 openstackgerrit Merged openstack/rally master: [Install] Fix postgresql installation  https://review.openstack.org/481998
02:49 openstackgerrit chenhb proposed openstack/rally master: Fix an issue of database migration  https://review.openstack.org/483163
02:53 aojea joined #openstack-rally
02:58 a8K8U1LOP [From Gitter] zhangzhihui1 : in my tempest.conf
02: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_files
02:59 a8K8U1LOP [From Gitter] zhangzhihui1 : 'lock_files' is a dir.
03:02 chhavi joined #openstack-rally
03:17 openstackgerrit chenhb proposed openstack/rally master: Fix an issue of database migration  https://review.openstack.org/483163
03:52 psuriset joined #openstack-rally
04:00 LindaWang zhangzhihui1 Which version of rally do you use?
04:02 LindaWang a8K8U1LOP: zhangzhihui1 When I run tests in rally 0.8.1, the dir lock_files is there and the param lock_path is right
04:03 LindaWang zhangzhihui1 The issue is only for rally 0.9.1
04:50 a8K8U1LOP [From Gitter] zhangzhihui1 : @ LindaWang  # rally version
04:50 a8K8U1LOP [From Gitter] zhangzhihui1 : 0.9.1~dev280
04:59 anshul joined #openstack-rally
05:28 aojea joined #openstack-rally
05:40 rcernin joined #openstack-rally
05:46 openstackgerrit chenhb proposed openstack/rally master: Fix an issue of database migration  https://review.openstack.org/483163
05:47 psuriset joined #openstack-rally
06:06 lpetrut joined #openstack-rally
06:52 pcaruana joined #openstack-rally
06:56 tesseract joined #openstack-rally
07:01 psuriset joined #openstack-rally
07:14 LindaWang zhangzhihui1 I doubt if the way I installed rally was wrong.
07:16 LindaWang zhangzhihui1 I did not use the install_rally.sh to install
07:17 aojea joined #openstack-rally
07:19 LindaWang zhangzhihui1 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 create
07:20 LindaWang zhangzhihui1 Do you know if it is right?
07:25 alexchadin joined #openstack-rally
07:27 LindaWang zhangzhihui1 Or, could you help test rally 0.9.1 locally? I see your rally version is master.
07:29 openstackgerrit sudhir agarwal proposed openstack/rally master: Replaces uuid.uuid4 with uuidutils.generate_uuid()  https://review.openstack.org/483239
07:32 a8K8U1LOP [From Gitter] zhangzhihui1 : do you want to let me to run tempest.api.compute.test_quotas.QuotasTestJSON.test_get_default_quotas?
07:34 lpetrut joined #openstack-rally
07:34 LindaWang No, after deployment, just run "rally verify configrue-verifier"
07:35 LindaWang To check is the dir .rally/verification/tempest/data/lock_files_uuid exists
07:35 LindaWang So also check if the param lock_path in tempest.conf has been configured correctly.
07:37 jose_lausuch joined #openstack-rally
07:49 openstackgerrit Andrey Kurilin proposed openstack/rally master: [ci] Turn off glance scenarios  https://review.openstack.org/483247
07:54 a8K8U1LOP [From Gitter] zhangzhihui1 : ok
07:55 a8K8U1LOP [From Gitter] zhangzhihui1 : .rally/verification/tempest/data/lock_files_uuid: No such file or directory, but test is success
07:55 a8K8U1LOP [From Gitter] zhangzhihui1 : lock_path = /root/.rally/verification/verifier-0a571769-31d4-4ab9-ab28-34c88b9ac4c2/for-deployment-804455f2-9fec-497c-a840-72186052cb94/lock_files
07:56 a8K8U1LOP [From Gitter] zhangzhihui1 :  tempest.api.compute.test_quotas.QuotasTestJSON.test_get_quotas ... success [2.223s]
07:57 LindaWang Then, could you help check if the way I insatlled rally is correct?
07:59 a8K8U1LOP [From Gitter] zhangzhihui1 : and i don't know if the way you installed rally is right. we can ask @andreykurilin
07:59 LindaWang zhangzhihui1 Fine. Thanks
08:05 LindaWang andreykurilin:  Could you help check the way I installed rally is right? I did not user install_rally.sh
08:06 LindaWang andreykurilin:
08:06 LindaWang mkdir -p /etc/rally && \
08:06 LindaWang printf "[database]\nconnection = 'sqlite:////var/lib/rally/database/rally.sqlite'" > /etc/rally/rally.conf && \
08:06 LindaWang mkdir -p /var/lib/rally/database && rally-manage db create
08:18 serlex joined #openstack-rally
08:32 LindaWang zhangzhihui1 There is  no such dir in my system: /root/.rally/verification/verifier-uuid/for-deployment-uuid/lock_files
08:32 LindaWang zhangzhihui1 Actually there is no dir named lock_files anywhere.
08:34 a8K8U1LOP [From Gitter] zhangzhihui1 : when run tests, the dir will be created
08:35 LindaWang I thought it was created by the cli "rally verify configrue-verifier"
08:38 LindaWang But 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 joined #openstack-rally
08:40 a8K8U1LOP [From Gitter] andreykurilin : @geyao0619 hi! sorry, several other OpenStack projects broke our gates. We are trying to localize problems now.
08:42 a8K8U1LOP [From Gitter] andreykurilin : @LindaWang, @zhangzhihui1 : hi!
08:43 LindaWang Hi andreykurilin
08: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 itself
08:44 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 verification
08:44 a8K8U1LOP [From Gitter] andreykurilin : can you share an error of failed test?
08:48 LindaWang andreykurilin: http://paste.openstack.org/raw/615232/
08:55 ushkalim joined #openstack-rally
08:58 alexchadin joined #openstack-rally
09:02 openstackgerrit chenhb proposed openstack/rally master: Print the messages what can be traced back to real address  https://review.openstack.org/483271
09:03 oanufrii joined #openstack-rally
09:09 a8K8U1LOP [From Gitter] andreykurilin : @LindaWang: do you use the latest tempest?
09:09 LindaWang andreykurilin: tempest 14.0.0
09:10 LindaWang rally 0.9.1
09:11 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:12 tosky joined #openstack-rally
09:13 a8K8U1LOP [From Gitter] andreykurilin : Folks: our gates should be unblocked right after https://review.openstack.org/483247
09:20 LindaWang a8K8U1LOP: andreykurilin: the var lock_path in  session oslo_concurrency is in tempest.conf
09:21 rallydev-bot joined #openstack-rally
09:22 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-L70
09:26 LindaWang andreykurilin: The reason we Functest team uses tempest 14.0.0 is that the upper stream openstack Ocata recommends that version
09:26 LindaWang andreykurilin: https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt?h=stable/ocata
09:36 rallydev-bot [From Gitter] andreykurilin : LindaWang: can you update propose a patch to rally for setting the right option?
09:39 LindaWang andreykurilin: I have no idea how rally handles that option with different versions of tempest?
09:40 rallydev-bot [From Gitter] andreykurilin : I think any version of tempest will no fail if additional options,which are not used, will be specified
09:40 rallydev-bot [From Gitter] andreykurilin : so we can specify two options
09:40 rallydev-bot [From Gitter] andreykurilin : old one and new one
09:40 rallydev-bot [From Gitter] andreykurilin : and everything should work
09:50 LindaWang So could you help with that when you are available? I'd really appreciate it.
09:55 mvk joined #openstack-rally
10:18 rallydev-bot [From Gitter] chenhb-zte : @andreykurilin yup, saw the patch,  expect  gates will be right.
10:20 rallydev-bot [From Gitter] andreykurilin : LindaWang: I'm available now and ready to help you to make a patch to rally :)
10:20 LindaWang andreykurilin:  Thanks
10:21 openstackgerrit Merged openstack/rally master: [ci] Turn off glance scenarios  https://review.openstack.org/483247
10:24 LindaWang andreykurilin:  A quick question: Is the var floating_network_name in tempest.conf supported by rally 0.9.1+?
10:26 rallydev-bot [From Gitter] zhangzhihui1 : @andreykurilin  https://review.openstack.org/#/c/433013/ give us some advice
10:28 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_name
10:29 rallydev-bot [From Gitter] andreykurilin : @MaXinjian  @zhangzhihui1 sorry for the delay, we spent time trying to fix our CI. will comment these patches today
10:29 LindaWang andreykurilin:  Is the var floating_network_name also influenced by tempest version?
10:31 rallydev-bot [From Gitter] andreykurilin : I do not think so
10:34 LindaWang andreykurilin: ok
10:35 LindaWang andreykurilin:  Is floating_network_name exactly the name of public_network_id in tempest.conf?
10:36 LindaWang andreykurilin:  I find in some certain SUTs, public_network_id exists which floating_network_name is missing in rally 0.9.1
10:36 rallydev-bot [From Gitter] andreykurilin : hm
10:36 rallydev-bot [From Gitter] andreykurilin : do you have any public networks there?
10:37 LindaWang andreykurilin:  yes,
10:37 rallydev-bot [From Gitter] andreykurilin : so rally lists all networks via neutron, then filter them by active status and external router
10:37 LindaWang andreykurilin: Cause public_network_id is configured correctly
10:38 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_name
10:39 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 setting
10:40 LindaWang Ok, I will check that later.
10:41 LindaWang andreykurilin: Do you still remember the issue about admin role when running rally?
10:41 LindaWang andreykurilin:  I sent you one email 4 days ago.
10:42 rallydev-bot [From Gitter] andreykurilin : wow, sorry, It looks like I forgot to send a reply
10:45 LindaWang andreykurilin:  Talk to you later. A conference offline to join now.
10:45 lpetrut joined #openstack-rally
10:46 LindaWang andreykurilin:  I am wondering if the SUT has strict limit about resource management, and only the user with admin role can be allowed to take actions
10:47 LindaWang andreykurilin: Then how can I run rally on the SUT?
10:48 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 options
10:49 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 roles
10: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 cloud
10:50 mvk joined #openstack-rally
10: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 user
11:06 aojea joined #openstack-rally
11:13 yamamoto joined #openstack-rally
11:21 yamamoto joined #openstack-rally
11:26 mvk joined #openstack-rally
11:27 psuriset joined #openstack-rally
11:36 yamamoto joined #openstack-rally
11:37 e0ne_ joined #openstack-rally
11:38 lpetrut_ joined #openstack-rally
11:39 jkilpatr joined #openstack-rally
11:50 yamamoto joined #openstack-rally
11:57 openstackgerrit bhavani proposed openstack/rally master: Add a hacking rule for string interpolation at logging  https://review.openstack.org/483314
12:01 dave-mccowan joined #openstack-rally
12:17 yamamoto joined #openstack-rally
12:21 openstackgerrit Andrey Kurilin proposed openstack/rally master: [cli] "rally task list" improvements  https://review.openstack.org/482473
12:28 openstackgerrit bhavani proposed openstack/rally master: Handle log message interpolation by the logger in common/  https://review.openstack.org/483314
12:48 alexchadin joined #openstack-rally
12:56 catintheroof joined #openstack-rally
13:00 deep-book-gk_ joined #openstack-rally
13:01 deep-book-gk_ left #openstack-rally
13:07 reveller joined #openstack-rally
13:14 LindaWang joined #openstack-rally
13:18 LindaWang \
13:24 aojea joined #openstack-rally
13:25 aojea joined #openstack-rally
13:39 openstackgerrit Andrey Kurilin proposed openstack/rally master: [cli] "rally task list" improvements  https://review.openstack.org/482473
13:47 jkilpatr joined #openstack-rally
14:07 LindaWang joined #openstack-rally
14:22 itlinux_ joined #openstack-rally
14:24 e0ne joined #openstack-rally
14:31 LindaWang joined #openstack-rally
14:31 openstackgerrit Andrey Kurilin proposed openstack/rally master: Remove existing_users context  https://review.openstack.org/458810
14:35 LindaWang andreykurilin:  The SUT I am testing is one oommercial version of Openstack.
14:36 LindaWang andreykurilin: The SUT I am testing is one commercial version of Openstack.
14:36 LindaWang andreykurilin:  1) Where is the roles context that can be used?
14:37 rallydev-bot [From Gitter] andreykurilin : Are you sure that regular user which cannot do anything is an expected behaviuor of that cloud?
14:41 LindaWang Yes, I am sure. The new user with admin role can be allowed to take actions in that SUT
14:43 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 cloud
14:44 rallydev-bot [From Gitter] andreykurilin : ok, if you think that your case is not a bug, but a feature, I'm ok too :)
14:45 rallydev-bot [From Gitter] andreykurilin : so let's talk who we can interact with such case
14:45 LindaWang What I mean is that the new user without admin role can not be allowed to do anything
14:45 rallydev-bot [From Gitter] andreykurilin : ok
14: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:48 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:49 rallydev-bot [From Gitter] andreykurilin : solution #2 : use roles context. In this case rally will create users and then apply specified roles for you
14:49 rallydev-bot [From Gitter] andreykurilin : https://rally.readthedocs.io/en/latest/plugins/plugin_reference.html#roles-context
14:49 rallydev-bot [From Gitter] andreykurilin : An example: https://github.com/openstack/rally/blob/master/samples/tasks/contexts/roles.json#L17
14:50 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 step
14:50 LindaWang Actually I use only on user(admin) in the creds when I created rally deployment
14:50 LindaWang Actually I use only one user(admin) in the creds when I created rally deployment
14:52 rallydev-bot [From Gitter] andreykurilin : yes. specifing just one user(admin) is a case when rally creates new users for workload
14:54 LindaWang I think the user named admin is only for creating the rally deployment.
14:55 LindaWang When it comes to different tests, new different users will be created then.
14:55 rallydev-bot [From Gitter] andreykurilin : yes
14:58 LindaWang For 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 : yes
14:59 LindaWang So in my case here, i have to assign admin role to these users beforehand?
14:59 rallydev-bot [From Gitter] andreykurilin : yup
15:00 LindaWang How to guarantee the number of additional added users in the file existing-with-predefined-users.json is enough for all these tests?
15:02 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 eng
15:02 rallydev-bot ine will force to create new users
15:04 LindaWang Now I prefer to solution 2
15:04 rallydev-bot [From Gitter] andreykurilin : heh
15:05 LindaWang But I have no idea when I run these command: http://paste.openstack.org/raw/615280/
15:06 rallydev-bot [From Gitter] andreykurilin : you need to modify /home/opnfv/repos/functest/functest/opnfv_tests/openstack/rally/task.yaml
15:06 LindaWang How can I configure the roles.json file?
15:06 serlex joined #openstack-rally
15:06 LindaWang https://github.com/opnfv/functest/blob/master/functest/opnfv_tests/openstack/rally/task.yaml
15:07 LindaWang No roles can be configured in this file.
15:07 serlex left #openstack-rally
15:08 rallydev-bot [From Gitter] andreykurilin : Actually, it would be much easier to you to return to solution #1
15:09 LindaWang Well, fine :)
15:09 e0ne joined #openstack-rally
15: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 time
15:09 LindaWang I am just wondering how to realize solution #2 in functest
15:10 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-L4
15:10 rallydev-bot [From Gitter] andreykurilin : and to other files
15:12 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 users
15:12 LindaWang What 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:13 rallydev-bot [From Gitter] andreykurilin : I do not know what is it)
15:13 LindaWang https://github.com/opnfv/functest/tree/master/functest/opnfv_tests/openstack/rally/scenario/templates
15:14 rallydev-bot [From Gitter] andreykurilin : I think it is templates for heat
15:14 LindaWang I thought these 2 params (tmpl_dir and sup_dir) were required by rally
15:19 rallydev-bot [From Gitter] andreykurilin : possibly, these parameters are required by you script, but not rally itself
15:20 yingjun joined #openstack-rally
15:27 LindaWang Do 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-L4
15:28 rallydev-bot [From Gitter] andreykurilin : no
15:28 LindaWang Remove the session of context for all scenario?
15:28 rallydev-bot [From Gitter] andreykurilin : let me try to explain in another way
15:29 LindaWang Thanks, 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 users
15:32 rallydev-bot [From Gitter] andreykurilin : an example of rally task which should launch two scenarios - http://xsnippet.org/362640/
15:33 rallydev-bot [From Gitter] andreykurilin : both of scenarios has context section with specified users ctx
15:34 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 json
15:34 LindaWang YEP
15:35 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 changed
15:36 rallydev-bot [From Gitter] andreykurilin : rally will again ignore "users" section of deployment config and create new users
15:36 rallydev-bot [From Gitter] andreykurilin : BUT the config for the second workload is changed
15:36 rallydev-bot [From Gitter] andreykurilin : there is no users context
15:37 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 created
15:38 LindaWang So 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:40 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/functest
15:40 rallydev-bot /opnfv_tests/openstack/rally/scenario/opnfv-authenticate.yaml#L14-L15 and
15:40 rallydev-bot [From Gitter] andreykurilin : so on
15:41 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, etc
15:42 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 not
15:43 LindaWang Ok, 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 used
15:44 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:45 LindaWang ok, I will try that
15:47 LindaWang Thanks for your detailed explanation and patience. :)
15:52 openstackgerrit Andrey Kurilin proposed openstack/rally master: [wip][cli] "rally task list" improvements  https://review.openstack.org/482473
15:55 LindaWang I will try to update the patch about lock_path, if we have to use tempest 14.0.0
16:02 aojea joined #openstack-rally
16:04 LindaWang joined #openstack-rally
16:12 aojea joined #openstack-rally
16:21 aojea joined #openstack-rally
16:30 aojea joined #openstack-rally
16:39 aojea joined #openstack-rally
16:45 itlinux joined #openstack-rally
16:48 aojea joined #openstack-rally
16:57 aojea joined #openstack-rally
17:06 aojea joined #openstack-rally
17:09 e0ne joined #openstack-rally
17:15 aojea joined #openstack-rally
17:18 jkilpatr joined #openstack-rally
17:24 aojea joined #openstack-rally
18:16 jkilpatr joined #openstack-rally
18:35 mvk joined #openstack-rally
18:38 pcaruana joined #openstack-rally
18:54 harlowja joined #openstack-rally
19:06 tosky joined #openstack-rally
20:21 lpetrut_ joined #openstack-rally
20:22 harlowja joined #openstack-rally
20:35 aojea joined #openstack-rally
22:20 dpaterson joined #openstack-rally
23:28 aojea joined #openstack-rally
23:37 aojea joined #openstack-rally
23:46 aojea joined #openstack-rally
23:56 itlinux joined #openstack-rally

| Channels | #openstack-rally index | Today | | Search | Google Search | Plain-Text | summary