Perl 6 - the future is here, just unevenly distributed

IRC log for #openstack-rally, 2016-06-01

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

All times shown according to UTC.

Time Nick Message
01:06 klindgren_ joined #openstack-rally
01:13 yanyanhu joined #openstack-rally
01:37 psuriset joined #openstack-rally
01:48 ilbot3 joined #openstack-rally
01:48 Topic for #openstack-rally is now ☁ Rally RoadMap: http://goo.gl/JZkmwY ☁ Review Dashboard: http://goo.gl/YuCJfl ☁ IRC logs http://irclog.perlgeek.de/openstack-rally ☁ Key persons to ask:  boris-42, yfried, msdubov, rediskin, andreykurilin, amaretskiy  Ã¢ËœÂ Documentation: https://rally.readthedocs.org/en/latest/ ☁ To publish changes to Rally:  https://rally.readthedocs.org/en/latest/contribute.html
03:33 psuriset joined #openstack-rally
03:40 luzC joined #openstack-rally
04:01 akrzos joined #openstack-rally
05:22 rdas joined #openstack-rally
05:23 abalutoiu joined #openstack-rally
05:31 openstackgerrit Kahou Lei proposed openstack/rally: Expose ssh timeout and interval in vm scenarios  https://review.openstack.org/323666
05:36 openstackgerrit Kahou Lei proposed openstack/rally: Expose ssh timeout and interval in vm scenarios  https://review.openstack.org/323666
05:43 rcernin joined #openstack-rally
06:00 mvk_ joined #openstack-rally
06:16 luzC joined #openstack-rally
07:03 amaretskiy joined #openstack-rally
07:03 luzC joined #openstack-rally
07:03 tesseract joined #openstack-rally
07:26 pcaruana joined #openstack-rally
07:29 arxcruz joined #openstack-rally
07:32 e0ne joined #openstack-rally
07:34 anshul joined #openstack-rally
08:19 ushkalim joined #openstack-rally
08:32 lewo joined #openstack-rally
08:46 openstackgerrit Merged openstack/rally: verify: start and import_results always print uuid  https://review.openstack.org/321381
08:54 arxcruz joined #openstack-rally
08:55 ushkalim joined #openstack-rally
08:57 luzC joined #openstack-rally
09:08 tosky joined #openstack-rally
09:16 Alex_Stef joined #openstack-rally
09:32 mvk joined #openstack-rally
09:32 yingjun joined #openstack-rally
09:54 openstackgerrit Illia Khudoshyn proposed openstack/rally: Use existing users in 'create_and_list_networks'  https://review.openstack.org/320989
10:06 openstackgerrit Illia Khudoshyn proposed openstack/rally: Use existing users in 'create_and_list_networks'  https://review.openstack.org/320989
10:08 bkopilov joined #openstack-rally
10:09 bkopilov joined #openstack-rally
10:28 lezbar joined #openstack-rally
10:30 psuriset joined #openstack-rally
10:48 openstackgerrit Merged openstack/rally: Add cacert_key to _get_auth_info  https://review.openstack.org/323300
11:02 openstackgerrit Illia Khudoshyn proposed openstack/rally: Use existing users in 'create_and_list_networks'  https://review.openstack.org/320989
11:17 Alex_Stef joined #openstack-rally
11:25 stpierre joined #openstack-rally
11:27 dave-mccowan joined #openstack-rally
11:31 yingjun joined #openstack-rally
11:36 openstackgerrit Illia Khudoshyn proposed openstack/rally: [WIP][CI]Use existing users in 'create_and_list_networks'  https://review.openstack.org/320989
11:40 strigazi Hi rally team
11:41 strigazi I think the gate for magnum is ready
11:41 lgreg joined #openstack-rally
11:42 strigazi Is it possible to create a new change to add a rally job with a dependency to https://review.openstack.org/#/c/309546/ ?
11:51 akrzos joined #openstack-rally
11:54 openstackgerrit Spyros Trigazis proposed openstack/rally: [Magnum] Context and scenario for Magnum baymodel  https://review.openstack.org/309546
12:05 MaxPC joined #openstack-rally
12:14 lgreg joined #openstack-rally
12:18 openstackgerrit joined #openstack-rally
12:29 lgreg joined #openstack-rally
12:53 lgreg joined #openstack-rally
13:07 dave-mccowan joined #openstack-rally
13:20 openstackgerrit Roman Vasilets proposed openstack/rally: [WIP] Fix ceilometer bug with required contexts  https://review.openstack.org/323512
13:32 openstackgerrit Illia Khudoshyn proposed openstack/rally: [WIP][CI]Use existing users in 'create_and_list_networks'  https://review.openstack.org/320989
13:48 njohnston joined #openstack-rally
13:51 prithiv joined #openstack-rally
13:53 prithiv anyone facing this error in rally right after deployment http://paste.openstack.org/show/506954/
13:53 stpierre sounds to me like you need to specify {user,project}_domain_name in your deployment credentials
13:54 prithiv like how? i dont remember specifying that explicitly when i used it in my previous deployments.
13:54 prithiv i just created env from existing deployment
13:55 prithiv using rally deployment create —fromenv —name=test
13:55 stpierre like so: https://paste.fedoraproject.org/373356/46478931/
13:56 stpierre --fromenv honors OS_{USER,PROJECT}_DOMAIN_NAME, but it doesn't honor OS_*_DOMAIN_ID, or OS_DEFAULT_DOMAIN_*, which are both valid ways to specify domains
13:56 stpierre OpenStack: because consistency is overrated
13:57 prithiv so can i manually add it to the openrc file and recreate ?
13:57 stpierre i guess. that seems like the long way around -- i'd just describe the deployment in a yaml file like i pasted
13:57 stpierre or you can just manually set and export the OS_*_DOMAIN_NAME env vars
13:57 stpierre and use --fromenv
13:57 stpierre TIMTOWTDI
13:59 psuriset joined #openstack-rally
13:59 prithiv yes. i entered in a file and created deployment with —filename option
13:59 prithiv it worked.
13:59 prithiv thanks
14:00 stpierre np
14:00 openstackgerrit Merged openstack/rally: Expose ssh timeout and interval in vm scenarios  https://review.openstack.org/323666
14:06 zackf joined #openstack-rally
14:07 openstackgerrit OpenStack Proposal Bot proposed openstack/rally: Updated from global requirements  https://review.openstack.org/323924
14:19 openstackgerrit Roman Vasilets proposed openstack/rally: [WIP] Fix ceilometer bug with required contexts  https://review.openstack.org/323512
14:27 diogogmt joined #openstack-rally
14:27 arnoldje joined #openstack-rally
14:36 KevinE joined #openstack-rally
14:49 leoswaldo joined #openstack-rally
14:53 njohnston_ joined #openstack-rally
14:54 openstackgerrit Roman Vasilets proposed openstack/rally: [WIP] Fix ceilometer bug with required contexts  https://review.openstack.org/323512
15:00 openstackgerrit Andrey Kurilin proposed openstack/rally: Introduce Plugins Base classes  https://review.openstack.org/237049
15:00 diogogmt joined #openstack-rally
15:09 asti joined #openstack-rally
15:14 agrebennikov joined #openstack-rally
15:32 permalac joined #openstack-rally
15:37 diogogmt joined #openstack-rally
15:51 openstackgerrit Roman Vasilets proposed openstack/rally: Fix ceilometer bug with required contexts  https://review.openstack.org/323512
15:51 leoswaldo joined #openstack-rally
15:52 openstackgerrit Roman Vasilets proposed openstack/rally: Fix ceilometer bug with required contexts  https://review.openstack.org/323512
15:54 e0ne joined #openstack-rally
16:00 leoswaldo joined #openstack-rally
16:11 leoswaldo joined #openstack-rally
16:14 leoswaldo joined #openstack-rally
16:23 prithiv joined #openstack-rally
16:25 KevinE stpierre: Hey can you help me get my wording down on something? Rally has its tests all upstream for cinder/keystone/neutron/authenticate etc. I want to add a section (what's that even called) and then put some tests in it
16:28 KevinE or to anyone, I suppose that's a pretty simple question
16:28 lgreg joined #openstack-rally
16:31 leoswaldo joined #openstack-rally
16:32 stpierre so you want to add a whole new gate job? e.g., a new file in rally-jobs/ that is run as a separate test at check time?
16:32 stpierre or you just want to add a new scenario to an existing gate job?
16:35 leoswaldo joined #openstack-rally
16:44 KevinE erm I think that's what I'm asking, I am to merge up a whole folder of tests that we made
16:45 KevinE side question what is a blueprint? I have 4 blueprints to point to and idk what they are
16:46 stpierre blueprints are just plans for major new features.
16:46 stpierre usually (depending on the openstack component) there's a blueprint on launchpad, and a spec somewhere else. in rally's case, specs are in doc/specs/
16:47 stpierre so this review partially implements a blueprint, as noted in the commit message: https://review.openstack.org/#/c/317674/
16:47 stpierre if you click on the bp name, it will take you to launchpad and you can see all the reviews that implement that bp
16:48 KevinE Ahh, so assuming this is 1 large commit, it's just 4 lines in my commit message that tie to the 4 blueprints
16:48 stpierre yes
16:48 stpierre i'm still not sure i understand your original question, but if you've got 10 different task files and you just want one file, then you can just concatenate them together and remove the '---' if they're yaml
16:49 KevinE It's a suite of lbaas and l2/l3 tests
16:49 KevinE some json and a couple yaml
16:49 stpierre i guess you'll need to get them all in a common format first
16:50 asti joined #openstack-rally
16:50 KevinE there's a rally vm folder, I want to make a vm_int folder
16:50 stpierre but you can look at the files in rally-jobs/ to get an idea of how to format them
16:50 leoswaldo joined #openstack-rally
16:50 stpierre it's just a top-level dict, keys are scenario names, values are lists of subtasks for that scenario
16:50 KevinE you just lost me
16:50 stpierre the task format
16:51 KevinE Ah, so like Keystone>user-create-and-delete>theStuffInTheJson
16:51 KevinE ?
16:51 stpierre no
16:51 stpierre look at the examples in rally-jobs/
16:56 KevinE okay I looked around. so like the rally-keystone rally-job file has most of the tests in the actual keystone task folder
16:56 KevinE I'm following again I think
16:57 stpierre huh?
16:57 stpierre i'm not
16:57 KevinE stpierre: lol ok I'm looking in the rally-jobs folder. I don't really know what any of it is, just that i can see how the yaml files tie to the specific tests
16:57 stpierre they're all task files
16:57 stpierre let's use https://github.com/openstack/rally/blob/master/rally-jobs/rally.yaml as an example
16:57 stpierre that file describes a single task
16:58 stpierre at the top level, that YAML file describes a dict
16:58 stpierre the keys of that dict are the names of scenarios to be run
16:58 stpierre the values are a list of the configurations with which each scenario will be run
16:58 stpierre most scenarios are run only once, with a single configuration
16:58 stpierre some are run many times, with different configs: https://github.com/openstack/rally/blob/master/rally-jobs/rally.yaml#L390
16:59 KevinE Ah. So I have a folder of scenarios I need to merge.
17:00 stpierre so actual functions that test things?
17:01 stpierre e.g., https://github.com/openstack/rally/blob/master/rally/plugins/openstack/scenarios/neutron/network.py#L28 is a scenario named "NeutronNetworks.create_and_list_networks"
17:01 leoswaldo joined #openstack-rally
17:02 KevinE stpierre: http://pastebin.com/EeYU52bg
17:02 KevinE an example
17:05 KevinE this whole vm_int deal is what I've got
17:08 leoswaldo joined #openstack-rally
17:13 stpierre convert them all to yaml or json, combine them according to the examples in rally-jobs/
17:17 agrebennikov joined #openstack-rally
17:20 KevinE stpierre: why do I not put them in samples/tasks/scenarios/vm_int?
17:25 stpierre oh, you do. sorry, i was using the wrong sense of the word "merge"
17:26 stpierre you want to try to upstream all your stuff, yeah?
17:26 psd joined #openstack-rally
17:26 stpierre then put them in samples/tasks/scenarios/vmperf probably, but yes
17:26 stpierre you'll need both yaml and json versions -- there's a gate check for that
17:53 KevinE stpierre: okay that's an easy conversion haha. Any reason why your suggested name is different from their suggested name of vm_int?
17:55 asti joined #openstack-rally
17:56 stpierre who is "they"?
17:56 stpierre i just went by the name of the scenario
17:57 stpierre "VMPerf.boot_runperf_delete" is provided by the VMPerf plugin, so I'd put it in vmperf. depending on how things are organized it might even go in just vm/
18:03 KevinE stpierre: I actually don't know who they are :) so should all of this just be in one big commit?
18:03 KevinE stpierre: also, it's that folder, along with the plugins it references (assuming they are also new), and what else should I look at that probably needs to be added as well?
18:09 stpierre tasks in rally-jobs/ will need to be added
18:09 stpierre that should be it
18:09 stpierre you should use as many commits as you need
18:09 stpierre or as many as make sense
18:26 e0ne joined #openstack-rally
18:29 openstackgerrit Merged openstack/rally: Updated from global requirements  https://review.openstack.org/323924
18:39 mvk joined #openstack-rally
18:40 asti joined #openstack-rally
18:44 e0ne joined #openstack-rally
18:44 mvk_ joined #openstack-rally
18:48 mvk joined #openstack-rally
18:52 mvk_ joined #openstack-rally
19:20 clenimar joined #openstack-rally
19:20 leoswaldo joined #openstack-rally
19:33 strigazi hi, I have a problem with the gate job for magnum. Can someone help? I asked already on openstack-infra but I didn't get a response
19:34 strigazi it's a gate job to rally for magnum
19:40 e0ne joined #openstack-rally
19:48 e0ne joined #openstack-rally
19:50 pvaneck joined #openstack-rally
19:51 KevinE stpierre: I'm guessing I also have to move these files in rally/plugins/openstack/scenarios/vm_int ?
19:51 stpierre yes
19:52 stpierre and unit tests in tests/unit/plugins/openstack/scenarios/vm_int
19:56 KevinE oh there aren't unit tests..
19:59 stpierre there will need to be before it can be upstreamed
20:01 KevinE Okay I'll look into it, now for the rally-jobs... I see how I can combine all of the yaml files together to make one, but 1) why? What is the purpose of those? and 2) does it go under any of the existing rally-job files or will I make my own?
20:01 stpierre existing
20:01 stpierre the files in rally-jobs/ are each run as a gate job
20:01 stpierre we have, i dunno, a hundred plus scenarios? we don't want 100+ gate jobs. and rally can only run one task file at a time
20:01 stpierre so we write one file per gate job
20:02 KevinE so how do I determine which gate job these go under?
20:03 stpierre what do they test?
20:04 stpierre there are existing VMTasks scenarios in both nova.yaml and rally-neutron.yaml, so i suspect one or the other of those would be appropriate
20:04 stpierre but it depends on what they test
20:04 stpierre you can also just make a best guess and get -1'd until you get it right :)
20:04 dave-mccowan joined #openstack-rally
20:05 _erick0zcr joined #openstack-rally
20:07 _erick0zcr Is there a way to send the profiler data to a file collector instead of using ceilometer?
20:07 KevinE Oh I'm ready for the reviewers to have never seen such a poor commit, but that's just a step in the right direction lol
20:10 leoswaldo joined #openstack-rally
20:31 lgreg joined #openstack-rally
20:44 leoswaldo joined #openstack-rally
21:11 openstackgerrit Chris St. Pierre proposed openstack/rally: Test: Fail jobs if resources are added or removed  https://review.openstack.org/300159
21:51 sshnaidm joined #openstack-rally
22:04 KevinE_ joined #openstack-rally
22:08 akrzos joined #openstack-rally
22:45 asti joined #openstack-rally
23:20 lgreg joined #openstack-rally
23:34 arnoldje joined #openstack-rally
23:47 asti joined #openstack-rally
23:56 afazekas joined #openstack-rally

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