Perl 6 - the future is here, just unevenly distributed

IRC log for #openstack-rally, 2015-03-29

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

All times shown according to UTC.

Time Nick Message
00:05 openstackgerrit Boris Pavlovic proposed stackforge/rally: Finish support of benchmarking with existing users  https://review.openstack.org/168524
00:05 openstackgerrit Boris Pavlovic proposed stackforge/rally: Fix rally show commands when we have existing users in deployment  https://review.openstack.org/168636
01:07 baker joined #openstack-rally
01:17 dspano joined #openstack-rally
01:18 openstackgerrit Boris Pavlovic proposed stackforge/rally: Finish support of benchmarking with existing users  https://review.openstack.org/168524
03:36 PerfBeing joined #openstack-rally
04:30 PerfBeing joined #openstack-rally
04:55 tfreger joined #openstack-rally
05:57 SivaSubramaniam joined #openstack-rally
05:57 SivaSubramaniam Hello!
05:58 SivaSubramaniam I am new here and would like to start contributing to the rally project.
05:59 yfried|afk joined #openstack-rally
06:03 yfried joined #openstack-rally
06:58 exploreshaifali joined #openstack-rally
07:15 PerfBeing joined #openstack-rally
07:17 nmagnezi joined #openstack-rally
07:27 openstackgerrit Nir Magnezi proposed stackforge/rally: Adds multi network and IPv6 support for scenarios  https://review.openstack.org/154885
07:44 PerfBeing joined #openstack-rally
07:47 openstackgerrit Nir Magnezi proposed stackforge/rally: Adds multi network and IPv6 support for scenarios  https://review.openstack.org/154885
07:52 yfried nmagnezi: don't forget to set topic for your patches
08:00 nmagnezi yfried, will do
08:01 nmagnezi yfried, i need to change it every time.. no idea how to keep it when i send a new patchset ( -t flag did not work)
08:08 yfried nmagnezi: maybe ask on #openstack-infra?
08:11 openstackgerrit Nir Magnezi proposed stackforge/rally: Adds multi network and IPv6 support for scenarios  https://review.openstack.org/154885
08:20 PerfBeing joined #openstack-rally
08:49 openstackgerrit pradeep proposed stackforge/rally: Add nova pause_and_unpause scenario  https://review.openstack.org/168681
09:21 siva_subramaniam joined #openstack-rally
09:22 siva_subramaniam submitted the blueprint https://blueprints.launchpad.net/rally/+spec/pause-unpause-resume
09:22 siva_subramaniam can someone help me how to proceed from here?
09:22 siva_subramaniam i am new to openstack contribution.
09:25 siva_subramaniam @boris-42 Hi Boris!
09:34 * yfried looking at siva_subramaniam's link
09:35 yfried siva_subramaniam: I don't understand the scope of this bp
09:35 yfried siva_subramaniam: if you mean to add tests for pause/resume VM
09:35 yfried siva_subramaniam: then you don't need a bp for that
09:35 siva_subramaniam yes to add pause/unpause scenarios and also resume.
09:35 siva_subramaniam oh ok i can directly check-in for review?
09:36 yfried siva_subramaniam: if it's a few small patches, then yes
09:36 siva_subramaniam ok. thanks :) and what is the scope of a blueprint. is there some minimum number of lines or like that?
09:38 yfried siva_subramaniam: I meant that I didn't understand if your bp is referring to some tests on server status, or do you have some pause/unpause tests to something else or even to the rally project
09:38 yfried siva_subramaniam: maybe "scope" was the wrong word
09:39 yfried siva_subramaniam: https://github.com/openstack/tempest/blob/master/tempest/scenario/test_network_advanced_server_ops.py
09:39 yfried siva_subramaniam: ^ is this what you had in mind?
09:40 siva_subramaniam yes exactly, i want to add these missing functionality like pause/unpause, resume server tests in rally.
09:40 yfried siva_subramaniam: did you know that you can execute tempest tests via rally like any other rally scenarios?
09:41 siva_subramaniam yes . i am aware of that. however, running the  tempest tests in rally does not give me the atomic operation times, is that right?
09:42 yfried siva_subramaniam: that's the main problem
09:42 yfried siva_subramaniam: so seems to me you want to extend NovaScenario.utils to support pause/unpause. good luck
09:43 siva_subramaniam yes. thanks a lot for the help.!! i will proceed without the blueprint!
09:46 yfried siva_subramaniam: bp is for tracking changes in rally itself. just extending rally scenarios shouldn't require too much tracking. esp if it's a single patch
09:47 yfried siva_subramaniam: if you have multiple related patches, I suggest setting a common topic via gerrit so reviewers can see all of them.
10:01 siva_subramaniam okay!
10:07 openstackgerrit Nir Magnezi proposed stackforge/rally: Modifies VMScenario._run_command function, to handle single bash cmd  https://review.openstack.org/154825
10:34 rook__ joined #openstack-rally
11:05 openstackgerrit Nir Magnezi proposed stackforge/rally: Modifies VMScenario._run_command function, to handle single bash cmd  https://review.openstack.org/154825
11:11 openstackgerrit Nir Magnezi proposed stackforge/rally: Adds multi network and IPv6 support for scenarios  https://review.openstack.org/154885
11:31 openstackgerrit Siva Subramaniam proposed stackforge/rally: Nova utils: Added pause, unpause, resume tests  https://review.openstack.org/168689
11:31 psd joined #openstack-rally
11:35 siva-subramaniam joined #openstack-rally
11:37 openstackgerrit Yair Fried proposed stackforge/rally: Fixes Tempest.__move_contents_to_subdir to abspath  https://review.openstack.org/168690
11:39 openstackgerrit Yair Fried proposed stackforge/rally: Fixes Tempest path update to use abspath  https://review.openstack.org/168690
11:39 yfried siva-subramaniam: what did you have in mind?
11:39 siva-subramaniam yfried: I have posted my first patch, can you review this? https://review.openstack.org/#/c/168689/
11:40 yfried siva-subramaniam: sure. I usually wait for the jenkins CI to post review, but I'll take a look now
11:41 siva-subramaniam okay great. thanks.
11:55 yfried siva-subramaniam: review done
11:58 siva-subramaniam yfried: that was fast, thanks!
12:25 yfried siva-subramaniam: small patches are quick and easy to review
12:25 yfried siva-subramaniam: keep that in mind
12:29 siva-subramaniam yfried: ok i saw your review, good suggestion. so i will create a server action in nova utils like the one you mentioned in the review.
12:30 siva-subramaniam yfried: the end goal would be a scenario which will take the list of lifecycle operations from the args.  It will boot a server and then execute all of them one by one.
12:32 boris-42 yfried: siva-subramaniam hi guys=)
12:33 siva-subramaniam boris-42: hello boris!
12:33 boris-42 siva-subramaniam: so writing most of scenarios doesn't require any bp
12:34 boris-42 siva-subramaniam: btw did you see boot_and_bounce_server ?
12:35 siva-subramaniam boris-42: yes i did see that.
12:36 boris-42 yfried: btw usually we have N methods
12:36 siva-subramaniam boris-42: using that method is a good idea, but it requires additional scenarios to be written for each lifecycle operation(stop_start, rescue_unrescue, etc)
12:36 boris-42 yfried: for each action
12:36 boris-42 siva-subramaniam: hm?
12:36 boris-42 siva-subramaniam: why?
12:37 siva-subramaniam boris-42: so it requires a scenario name as an action, am i correct?
12:38 siva-subramaniam boris-42: it calls a bind_actions method which maps to the scenarios.
12:38 openstackgerrit Nir Magnezi proposed stackforge/rally: Modifies _boot_server() to handle instances with multiple networks  https://review.openstack.org/154833
12:41 siva-subramaniam boris-42: What I am thinking is i will create one scenario which will take args from the user, for eg. ["pause", "unpause", "suspend", "resume"] and then execute that scenario in that order.
12:41 boris-42 siva-subramaniam: it is exactly what does boot_and_bounce_server
12:42 boris-42 siva-subramaniam: it runs what you speicify in order that you speicify
12:45 siva-subramaniam boris-42: ok, what is the scenario that i am proposing is an extension of boot and bounce server, but it will need only two methods, one in nova.utils and one in nova.servers
12:46 boris-42 siva-subramaniam: so seems like misleading why not just extend boot_and_bounce_server to support unpause-pause?
12:46 siva-subramaniam boris-42: in the case of boot_and_bounce server method, if we need to add more functionality, like in my case, pause and unpause instance, i need to write two methods in nova.utils, one scenario method (pause_unpause_server) in nova.servers
12:47 boris-42 siva-subramaniam: yep
12:48 boris-42 siva-subramaniam: actually you need to change this https://github.com/stackforge/rally/blob/master/rally/benchmark/scenarios/nova/servers.py#L243-L253
12:51 boris-42 siva-subramaniam: so rescue-unrescue is a sample how to do the things
12:54 siva-subramaniam boris-42: yes i have checked that. my only doubt is why are we not having a single method for lifecycle operations, like def _server_action(server, action) , in nova_utils? this will reduce a lot of duplications. I am just curious :)
12:55 boris-42 siva-subramaniam: you mean thing that yfried proposed?
12:56 siva-subramaniam boris-42: yes, i got the idea from that review.  We can achieve all the lifecycle operations in just 2 methods going by that logic.
12:57 boris-42 siva-subramaniam: yep that thing is reasonable
12:57 boris-42 siva-subramaniam: but I would like to dicuss it with the reset team
12:57 boris-42 rest*
12:57 boris-42 siva-subramaniam: I mean if we chose that direction we should refactor a lot of code=)
12:58 siva-subramaniam boris-42: yes, i can help if you want to do that.
12:59 boris-42 siva-subramaniam: that will be great, but let's discuss this on Monday
12:59 boris-42 siva-subramaniam: when the rest team will be online as well
12:59 boris-42 siva-subramaniam: you can do your part of work in new style
12:59 boris-42 siva-subramaniam: so we will have sample*
13:00 boris-42 for dicussion
13:00 siva-subramaniam boris-42: sure i will start that! what time you guys will be online on monday?
13:00 boris-42 siva-subramaniam: at this time 100% =)
13:00 boris-42 siva-subramaniam: so it's 4p.m. for us
13:01 siva-subramaniam boris-42: great! 6.30 pm here, sounds good to me :)
13:05 boris-42 siva-subramaniam: yep=)
13:07 yingjun joined #openstack-rally
13:09 anshul joined #openstack-rally
13:20 boris-42 yingjun: ping
13:20 jjmb joined #openstack-rally
13:22 yingjun boris-42: pong
13:25 boris-42 yingjun: I finished that case with supporting benchmarking with existing users
13:25 boris-42 yingjun: I think you should be interested in this case?
13:26 yingjun boris-42, nice, i’ll try that tomorrow
13:26 boris-42 yingjun: so here is the patch https://review.openstack.org/#/c/168524/
13:27 boris-42 yingjun: it's not yet merged
13:27 boris-42 just finished it yestarday=)
13:29 yingjun :), will try and review
13:32 boris-42 yingjun: great thnaks
13:32 boris-42 yingjun: it's one of the most wanted features lol=)
13:34 yingjun boris-42, ya, btw, found that you have a presentation in Vancouver summit, really cool, and i’ll be there
13:36 boris-42 yingjun: nice
13:36 boris-42 yingjun: we need to drink some beer =)
13:37 yingjun boris-42, yep, look forward for that
13:37 exploreshaifali joined #openstack-rally
13:57 openstackgerrit Nir Magnezi proposed stackforge/rally: Adds dual-stack (IPv4 and IPv6) support for scenarios  https://review.openstack.org/154885
14:07 openstackgerrit Wataru Takase proposed stackforge/rally: Add list servers scenario for EC2 API  https://review.openstack.org/156228
14:07 yingjun joined #openstack-rally
14:19 baker joined #openstack-rally
14:23 yingjun joined #openstack-rally
14:28 openstackgerrit Nir Magnezi proposed stackforge/rally: Adds dual-stack (IPv4 and IPv6) support for scenarios  https://review.openstack.org/154885
14:48 baker joined #openstack-rally
15:33 dpaterson joined #openstack-rally
15:47 openstackgerrit pradeep proposed stackforge/rally: Add nova pause_and_unpause scenario  https://review.openstack.org/168719
16:47 exploreshaifali joined #openstack-rally
16:48 e0ne joined #openstack-rally
16:56 yingjun joined #openstack-rally
17:04 panbalag joined #openstack-rally
17:13 nmagnezi joined #openstack-rally
17:20 e0ne joined #openstack-rally
17:27 e0ne joined #openstack-rally
17:39 e0ne joined #openstack-rally
17:57 PerfBeing joined #openstack-rally
18:08 yingjun joined #openstack-rally
18:10 baker joined #openstack-rally
18:37 panbalag joined #openstack-rally
18:38 panbalag joined #openstack-rally
18:46 e0ne joined #openstack-rally
18:55 e0ne joined #openstack-rally
19:06 baker joined #openstack-rally
19:23 yingjun joined #openstack-rally
19:33 e0ne joined #openstack-rally
19:39 e0ne joined #openstack-rally
19:41 exploreshaifali joined #openstack-rally
19:45 e0ne joined #openstack-rally
20:11 e0ne joined #openstack-rally
20:20 baker_ joined #openstack-rally
20:26 e0ne joined #openstack-rally
20:32 e0ne joined #openstack-rally
20:40 yingjun joined #openstack-rally
21:01 PerfBeing joined #openstack-rally
21:43 yingjun joined #openstack-rally
22:19 openstackgerrit Boris Pavlovic proposed stackforge/rally: Finish support of benchmarking with existing users  https://review.openstack.org/168524
22:19 openstackgerrit Boris Pavlovic proposed stackforge/rally: Fix rally show commands when we have existing users in deployment  https://review.openstack.org/168636
22:45 rook__ joined #openstack-rally
22:55 yingjun joined #openstack-rally
22:57 openstackgerrit Nir Magnezi proposed stackforge/rally: Adds dual-stack (IPv4 and IPv6) support for scenarios  https://review.openstack.org/154885
23:14 baker joined #openstack-rally
23:25 openstackgerrit Nir Magnezi proposed stackforge/rally: Modifies _boot_server() to handle instances with multiple networks  https://review.openstack.org/154833
23:40 rook__ joined #openstack-rally
23:46 mwagner_lap joined #openstack-rally

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