Tuesday, 2015-06-23

*** mahito has quit IRC00:00
*** mahito has joined #openstack-rally00:00
*** frayedknot has quit IRC00:26
*** dmorita has joined #openstack-rally00:28
*** echoingumesh has quit IRC00:49
*** echoingumesh has joined #openstack-rally00:50
*** nihilifer has quit IRC00:51
*** yingjun has joined #openstack-rally00:52
*** echoingumesh has quit IRC00:54
*** georgem1 has joined #openstack-rally01:36
*** yingjun has quit IRC02:25
*** yingjun has joined #openstack-rally02:30
*** yingjun has quit IRC02:49
*** rushiagr_away is now known as rushiagr02:53
*** yingjun has joined #openstack-rally02:56
*** arxcruz has quit IRC03:02
*** rushiagr is now known as rushiagr_away03:32
*** harlowja has quit IRC03:43
*** yingjun has quit IRC03:44
*** coolsvap|away is now known as coolsvap03:47
*** yingjun has joined #openstack-rally03:48
*** yingjun has quit IRC03:56
*** georgem1 has quit IRC03:59
*** kiran-r has joined #openstack-rally04:01
kun_huangboris-42: any blueprints or spec on report series patches (https://review.openstack.org/#/c/159458/)?04:02
*** rushiagr_away is now known as rushiagr04:11
*** rushiagr is now known as rushiagr_away04:14
*** rushiagr_away is now known as rushiagr04:15
*** PrashantS has joined #openstack-rally04:16
*** rdas has joined #openstack-rally04:33
*** zerda has joined #openstack-rally04:33
*** tfreger has joined #openstack-rally04:34
*** yfried__ has quit IRC04:48
*** PrashantS has quit IRC04:52
*** PrashantS has joined #openstack-rally04:53
*** PrashantS has quit IRC04:58
*** PrashantS has joined #openstack-rally05:01
*** boris-42 has quit IRC05:12
*** PrashantS has quit IRC05:15
*** PrashantS has joined #openstack-rally05:15
*** yingjun has joined #openstack-rally05:16
*** PrashantS has quit IRC05:20
*** agarciam has joined #openstack-rally05:42
*** yfried__ has joined #openstack-rally05:52
*** exploreshaifali has joined #openstack-rally06:02
*** yingjun has quit IRC06:04
*** yingjun has joined #openstack-rally06:19
*** igormarnat is now known as imarnat06:39
*** rushiagr is now known as rushiagr_away06:42
*** exploreshaifali has quit IRC06:43
*** yfried__ has quit IRC07:01
openstackgerritKiran proposed openstack/rally: Add ability to create pool in Neutron context  https://review.openstack.org/19343207:02
*** tfreger has quit IRC07:04
*** tfreger has joined #openstack-rally07:04
*** yfried__ has joined #openstack-rally07:06
*** imarnat is now known as igormarnat07:20
openstackgerritKiran proposed openstack/rally: Add Neutron LoadBalancer v1 create and list vips  https://review.openstack.org/19352707:26
*** neeti has joined #openstack-rally07:29
*** boris-42 has joined #openstack-rally07:32
*** arxcruz has joined #openstack-rally07:35
boris-42kun_huang: no07:41
*** akuznetsova__ is now known as akuznetsova07:48
*** anshul has joined #openstack-rally07:50
*** kiran-r has quit IRC07:57
*** amaretskiy has joined #openstack-rally08:03
*** karimb has joined #openstack-rally08:04
*** yingjun has quit IRC08:15
*** fhubik has joined #openstack-rally08:16
openstackgerritPavel Boldin proposed openstack/rally: unit-tests: fix mock check error messages  https://review.openstack.org/19440308:22
openstackgerritKun Huang proposed openstack/rally: Optimize task table order  https://review.openstack.org/19453708:25
*** yingjun has joined #openstack-rally08:25
*** fhubik is now known as fhubik_afk08:26
openstackgerritKun Huang proposed openstack/rally: Optimize task table order  https://review.openstack.org/19453708:27
*** e0ne has joined #openstack-rally08:32
*** fhubik_afk is now known as fhubik08:35
*** e0ne is now known as e0ne_08:38
*** yfried__ is now known as yfried|afk08:43
*** e0ne_ has quit IRC08:44
*** igormarnat is now known as imarnat08:47
*** e0ne has joined #openstack-rally08:48
*** yfried|afk is now known as yfried__08:49
openstackgerritLi Yingjun proposed openstack/rally: Support validate parameter list for restricted_parameters  https://review.openstack.org/19455208:50
openstackgerritPavel Boldin proposed openstack/rally: unit-tests: fix mock check error messages  https://review.openstack.org/19440308:52
*** aix has quit IRC08:53
openstackgerritIvan Kolodyazhny proposed openstack/rally: WIP. DO NOT MERGE!!!! Switch Cinder scenarios to APIv2  https://review.openstack.org/19368508:56
*** cdent has joined #openstack-rally08:58
*** e0ne is now known as e0ne_09:06
*** aix has joined #openstack-rally09:07
*** tfreger has quit IRC09:07
*** yfried__ is now known as yfried|afk09:11
*** e0ne_ has quit IRC09:11
*** yfried|afk is now known as yfried__09:11
*** yfried has joined #openstack-rally09:15
*** e0ne has joined #openstack-rally09:15
*** fhubik is now known as fhubik_afk09:17
openstackgerritKairat Kushaev proposed openstack/rally: [Heat] create-snapshot-restore-delete stack scenario  https://review.openstack.org/17903709:17
*** imarnat is now known as igormarnat09:19
*** yfried__ has quit IRC09:19
*** fhubik_afk is now known as fhubik09:20
*** igormarnat is now known as imarnat09:24
*** dmorita has quit IRC09:27
*** fhubik is now known as fhubik_afk09:30
*** tosky has joined #openstack-rally09:30
*** yingjun has quit IRC09:35
*** nihilifer_ has joined #openstack-rally09:40
*** fhubik_afk is now known as fhubik09:42
*** nihilifer_ has quit IRC09:46
*** nihilifer has joined #openstack-rally09:47
*** nihilifer_ has joined #openstack-rally09:50
*** nihilifer has quit IRC09:54
openstackgerritMerged openstack/rally: Fix sqlite file permission for system-wide install  https://review.openstack.org/19203409:59
*** nihilifer_ has quit IRC10:00
openstackgerritMerged openstack/rally: Add specs in doc/README.rst file  https://review.openstack.org/19437910:01
*** tfreger has joined #openstack-rally10:07
*** e0ne is now known as e0ne_10:10
*** e0ne_ has quit IRC10:20
*** yfried is now known as yfried|afk10:24
*** yfried|afk is now known as yfried10:34
*** mahito has quit IRC10:37
openstackgerritMerged openstack/rally: Keystone get_entities scenario backwards compat  https://review.openstack.org/19415110:49
*** yfried is now known as yfried|afk10:54
*** coolsvap is now known as coolsvap|away10:55
*** yfried|afk is now known as yfried10:56
*** fhubik is now known as fhubik_afk11:02
*** yfried is now known as yfried|afk11:09
*** e0ne has joined #openstack-rally11:09
*** yfried|afk is now known as yfried11:15
*** aix has quit IRC11:15
*** imarnat is now known as igormarnat11:24
*** aix has joined #openstack-rally11:28
*** stpierre has joined #openstack-rally11:32
*** e0ne is now known as e0ne_11:36
*** kiran-r has joined #openstack-rally11:38
*** igormarnat is now known as imarnat11:40
*** tfreger1 has joined #openstack-rally11:45
*** e0ne_ has quit IRC11:46
*** tfreger has quit IRC11:48
*** rvasilets has left #openstack-rally12:02
*** imarnat is now known as igormarnat12:06
*** tfreger1 has quit IRC12:06
*** fhubik_afk is now known as fhubik12:06
*** igormarnat is now known as imarnat12:09
*** neeti has quit IRC12:09
*** imarnat is now known as igormarnat12:12
*** igormarnat is now known as imarnat12:14
*** frayedknot has joined #openstack-rally12:16
*** imarnat is now known as igormarnat12:18
*** tfreger has joined #openstack-rally12:21
*** kiran-r has quit IRC12:24
*** MaxPC has joined #openstack-rally12:29
*** zerda has quit IRC12:30
*** aix has quit IRC12:31
*** yfried is now known as yfried|afk12:33
*** yfried|afk is now known as yfried12:34
*** fhubik is now known as fhubik_afk12:37
*** fhubik_afk is now known as fhubik12:37
*** e0ne has joined #openstack-rally12:37
*** igormarnat is now known as imarnat12:40
*** boris-42 has quit IRC12:42
*** mwagner_afk has joined #openstack-rally12:43
*** imarnat is now known as igormarnat12:46
*** aix has joined #openstack-rally12:47
*** coolsvap|away is now known as coolsvap12:51
*** georgem1 has joined #openstack-rally12:54
*** igormarnat is now known as imarnat12:56
*** imarnat is now known as igormarnat12:58
*** igormarnat is now known as imarnat12:58
*** coolsvap is now known as coolsvap|away13:01
kairat_kushaevstpierre: I really confused why do you need such attribute=)13:01
kairat_kushaevstpierre: I am also thinking about delta attribute13:02
kairat_kushaevstpierre: Why do we need it if we want to test change in scaling policy13:02
stpierrebecause we need to know that the scaling operation has completed13:03
*** tfreger has quit IRC13:07
*** rdas has quit IRC13:08
*** coolsvap|away is now known as coolsvap13:08
*** openstack has quit IRC13:17
*** openstack has joined #openstack-rally13:19
*** agarciam has quit IRC13:20
*** agarciam has joined #openstack-rally13:22
kairat_kushaevstpierre: So you can hard-code delta in scenario13:26
stpierreit needs to be configurable, because different scaling policies will result in different deltas13:26
kairat_kushaevstpierre: but changing delta also will require change in scaling adjustment13:27
kairat_kushaevotherwise the scenario will never end13:27
stpierrethe delta needs to reflect the scaling_adjustment in the ScalingPolicy object13:27
stpierreso yes, if you change the scaling_adjustment in a Heat template to 5, but keep the delta at 1, then the benchmark will time out13:27
stpierreerr, other way around, sorry13:28
stpierreif you change scaling_adjustment to 1 but keep delta=5, then it will timeout13:28
kairat_kushaevyep13:28
stpierreand that's okay; the end user needs to configure things sanely.13:28
stpierreif there was a way to discover this automatically short of reinventing the HOT parser, i'd do it, but AFAICT there isn't13:28
kairat_kushaevyou can define scaling adjustment as input parameter13:29
*** aix has quit IRC13:29
stpierrethat's precisely what the delta is13:30
kairat_kushaevbut I see that it is hard-coded now=)13:30
kairat_kushaevit is not calculated based on delta13:30
stpierrethe only difference is that scaling_adjustment can be a percentage; delta needs to be an absolute number, to avoid possible math errors. (e.g., i don't want rally to round up when Heat rounds down)13:30
kairat_kushaevyep, it is reasonable13:31
kairat_kushaevin addition setiing up scale_adjustment as input will allow to avoid redundant scaling policy in your template)13:32
kairat_kushaevyou will need only 1 policy in this case13:32
stpierrethe goal here is not to provide one Heat template to rule them all, though13:33
stpierrethe end user should be able to supply their own template if they wish, and they should not have to go out of their way to structure it explicitly for Rally13:33
stpierrethis scenario should be able to be used with any Heat template that contains a ScalingPolicy.13:34
stpierreright now, it can. you're proposing to make it so that the scenario can only be used with a Heat template that contains a ScalingPolicy whose scaling_adjustment is derived from a template parameter, but that's an unnecessary constraint13:35
stpierreif we're willing to constrain the user we can do lots of things differently -- for instance, we could require a specific scaling webhook URL key -- but i don't think it's reasonable to constrain the user thusly. let them use HOT however they feel fit, and make Rally work with that -- not require them to write a template to our arbitrary specifications13:36
kairat_kushaevstpierre: I think that the main idea of rally is quite the different13:41
kairat_kushaevas a user I would like to deal with rally parameters only13:41
kairat_kushaevthe bad thing here is that I need to know the realisation of the test13:42
kairat_kushaevand I cannot modify rally scenario parameters without updating a template13:42
*** aix has joined #openstack-rally13:42
stpierreif you want to do more advanced benchmarking than what is provided in the scenario then yes, you do need to have some familiarity with the subsystems that are being benchmarked.13:42
stpierres/provided in the scenario/provided in the samples/13:42
*** fhubik_afk is now known as fhubik13:43
stpierreremember, what we're providing are just samples. they're not intended to be exhaustive or complete or all the rally you'll ever need13:43
stpierrethey're a starting point.13:43
stpierreif you want to do fancy benchmarking of nova instances with VMTasks, you'd better familiarize yourself with bash, JSON, and floating IP pools. you'll have to write scripts. that's okay -- good, even.13:44
stpierrethis follows one of the points of the Unix philosophy: be liberal in what you accept (and conservative in what you produce, although that doesn't really apply here). we should let the end user provide literally any Heat template, and work with that -- not require some constrained subset of HOT.13:44
*** coolsvap is now known as coolsvap|away13:46
kairat_kushaevstpierre: Should the rally scenario work with different parameters without any updates in normal case?13:47
stpierrenot when the scenario references external files (i.e., Heat and VMTasks scenarios)13:48
*** yfried is now known as yfried|afk13:48
stpierreif i run VMTasks.boot_runcommand_delete and change the 'script' argument, I'd better also make sure that the script i've referenced exists. conversely, if i change the script that it's running, i may need to make changes to the scenario description (for example, changing the interpreter to bash instead of sh, or using a more full-featured image than cirros)13:50
*** tosky has quit IRC13:51
*** yfried|afk is now known as yfried13:53
stpierrethat happens in other places, too: if you change volume_type to True for CinderVolumes.create_snapshot_and_attach_volume, then you need to make sure that at least one volume type has been created in Cinder.13:54
kairat_kushaevyou can completely follow the unix-way when you will introduce the input parameter in the template13:57
*** cdent has quit IRC13:58
*** cdent has joined #openstack-rally13:58
kairat_kushaevwill it be complex to introduce this parameter in the template?13:58
stpierreno, but it unnecessarily constrains the end user.13:58
kairat_kushaevwe already require some output key for them in the scenario13:58
kairat_kushaevbut it also will be easier for them to test with rally later13:59
stpierreunless they want to write their own template13:59
stpierrethen it will be harder13:59
stpierreyour suggestion optimizes for the case of someone who doesn't know (or want to know) how to modify a simple Heat template, but who wants to test different scaling policies. (I do not think this person exists.) mine optimizes for the case of someone who wants to test arbitrary scaling policies in arbitrary templates, without imposing additional artificial constraints on the HOT they can write14:00
kairat_kushaevif somebody is familiar with templates will it be hard for them to introduce input parameter>14:01
kairat_kushaevmy proposal is just to make testing easier14:01
*** imarnat is now known as igormarnat14:02
stpierrebut it doesn't -- it makes testing easier in one very narrow case. in other cases -- say i have an existing Heat template that i want to benchmark -- it makes it harder. now i have to parameterize that template so that it works with Rally's magic14:02
stpierreinstead of telling Rally about my template, Rally tells me about artificial constrains my template must satisfy14:03
*** igormarnat is now known as imarnat14:07
kairat_kushaevstpierre: What do you think about this simplification14:15
*** fhubik is now known as fhubik_afk14:16
kairat_kushaev1. When stack is scaling it should be IN_PROGRESS14:16
kairat_kushaev 2. When scaling has finished then it should be in COMPLETE state14:16
kairat_kushaevSo perhaps it will be much easier first to wait untill stack become IN_PROGRESS14:17
stpierreif that's the case, then i'm happy to use that instead of checking for the size of the stack14:17
kairat_kushaevyou can check it on your env14:17
*** karimb has quit IRC14:17
kairat_kushaevit should work14:17
kairat_kushaevand finally it should in COMPLETE state again when autoscaling has finished14:18
stpierrethe problem is that we can't wait for the stack to become IN_PROGRESS first, because on an installation with low load the webhook POST is very nearly synchronous -- that is, the scaling operation is complete by the time the POST returns14:18
stpierreso i'm not sure how we'll tell the difference between a stack that has finished scaling, and one that hasn't started14:19
kairat_kushaevThe one possibility is to track if stack was updated or not14:20
kairat_kushaevif yes then is has been scaled14:20
kairat_kushaevotherwise it was not14:21
kairat_kushaevAFAIK you can just wait for stack to be UPDATE_COMPLETE14:21
kairat_kushaevIt should mean that the stack scale finished14:21
stpierreokay, i'll look into that today14:21
*** karimb has joined #openstack-rally14:24
*** imarnat is now known as igormarnat14:29
*** nihilifer has joined #openstack-rally14:31
*** fhubik_afk is now known as fhubik14:33
*** igormarnat is now known as imarnat14:33
*** yeungp has joined #openstack-rally14:43
*** e0ne is now known as e0ne_14:44
*** anshul has quit IRC14:44
*** e0ne_ is now known as e0ne14:49
*** tosky has joined #openstack-rally14:50
*** kiran-r has joined #openstack-rally14:51
openstackgerritAndrey Kurilin proposed openstack/rally: Try catch everything while running scenarios  https://review.openstack.org/19469014:55
stpierrekairat_kushaev: in Juno, the stack status doesn't change for scaling operations :(14:57
stpierreturns out that kilo heat is wildly less shitty than juno heat14:59
*** kiran-r has quit IRC15:02
*** frayedknot has quit IRC15:02
*** frayedknot has joined #openstack-rally15:04
kairat_kushaevstpierre: or kilo heat is much greater then juno heat=)15:06
*** fhubik is now known as fhubik_afk15:07
stpierreis the glass half full or half empty?15:07
kairat_kushaevstpierre: that's bad(15:07
kairat_kushaevstpierre: BTW are you going to support last 2 cycles in rally?15:08
*** fhubik_afk is now known as fhubik15:08
kairat_kushaevbecause we can stay it as it is right now but need to improve in the future15:08
stpierreafaik there's no official stance on that, but i think we need to do our best to support currently supported OpenStack15:08
stpierreyeah, we can improve the hell out of this when all we need to support is Kilo15:09
stpierrein kilo we can access alarm urls without output keys, too -- just get them directly from the scalingpolicy attributes15:09
*** arxcruz has quit IRC15:10
*** psd has joined #openstack-rally15:10
kairat_kushaevOk, let's move on untill next cycle15:11
stpierrelet me add a todo to this so we remember15:11
kairat_kushaevok,15:11
kairat_kushaevOne small remark also15:11
kairat_kushaevWe need to ensure also that the stack is not in FAILED state15:12
stpierre_create_stack() does that. or do you mean after the scaling operation?15:13
kairat_kushaevyep15:13
stpierreok15:13
kairat_kushaevotherwise it is possible that nnum of instances increased but some of them failed and the whole stack is failed15:13
kairat_kushaevso it should be complete after resizing15:14
*** fhubik has quit IRC15:23
*** kiran-r has joined #openstack-rally15:23
openstackgerritChris St. Pierre proposed openstack/rally: Add Heat scenario to test scaling policies  https://review.openstack.org/17843615:27
*** yfried has quit IRC15:32
*** kkuznetsova has quit IRC15:33
*** kiranr has joined #openstack-rally15:36
*** agarciam has quit IRC15:37
*** kiran-r has quit IRC15:40
*** e0ne is now known as e0ne_15:46
*** PrashantS has joined #openstack-rally15:46
*** e0ne_ is now known as e0ne15:47
*** cdent has quit IRC15:49
*** cdent has joined #openstack-rally15:49
*** frayedknot has quit IRC15:58
*** frayedknot has joined #openstack-rally16:00
*** yfried has joined #openstack-rally16:05
*** nihilifer has quit IRC16:13
openstackgerritRoman Vasilets proposed openstack/rally: Add Ironic create_and_list_node and create_node scenario  https://review.openstack.org/18606416:14
*** redixin has joined #openstack-rally16:16
openstackgerritKairat Kushaev proposed openstack/rally: [Heat] create-snapshot-restore-delete stack scenario  https://review.openstack.org/17903716:16
*** yfried has quit IRC16:24
*** yfried has joined #openstack-rally16:28
*** _kiran_ has joined #openstack-rally16:28
*** imarnat is now known as igormarnat16:28
*** e0ne has quit IRC16:29
*** kiranr has quit IRC16:32
*** _kiran_ has quit IRC16:36
*** _kiran_ has joined #openstack-rally16:36
*** davideagnello has quit IRC16:43
*** kiranr has joined #openstack-rally16:43
*** davideagnello has joined #openstack-rally16:44
*** _kiran_ has quit IRC16:47
*** igormarnat is now known as imarnat16:48
*** yfried has quit IRC16:53
*** karimb has quit IRC16:56
*** cdent has left #openstack-rally16:57
*** dontalton has joined #openstack-rally17:01
openstackgerritAlexander Maretskiy proposed openstack/rally: [Reports] Add class for merging data stream  https://review.openstack.org/19474517:04
openstackgerritAlexander Maretskiy proposed openstack/rally: [Reports] Add class for merging data stream  https://review.openstack.org/19474517:05
*** amaretskiy has quit IRC17:11
*** kiranr has quit IRC17:19
openstackgerritPavel Boldin proposed openstack/rally: unit-tests: fix mock check  https://review.openstack.org/19440317:22
*** yfried has joined #openstack-rally17:26
*** harlowja has joined #openstack-rally17:26
openstackgerritPavel Boldin proposed openstack/rally: unit-tests: fix mock check errors messages  https://review.openstack.org/19440317:29
openstackgerritPavel Boldin proposed openstack/rally: unit-tests: inception: add mock check unit-tests  https://review.openstack.org/19475417:29
*** psd has quit IRC17:57
*** mwagner_afk has quit IRC18:02
*** e0ne has joined #openstack-rally18:08
*** tosky has quit IRC18:11
*** imarnat is now known as igormarnat18:17
*** e0ne is now known as e0ne_18:27
*** e0ne_ has quit IRC18:32
*** echoingumesh has joined #openstack-rally18:35
*** e0ne has joined #openstack-rally18:41
*** aix has quit IRC18:42
*** nihilifer has joined #openstack-rally18:52
*** tfreger has joined #openstack-rally18:56
*** marcoceppi has quit IRC19:13
*** openstackgerrit has quit IRC19:21
*** openstackgerrit has joined #openstack-rally19:22
*** tfreger has quit IRC19:40
*** aix has joined #openstack-rally19:43
*** marcoceppi has joined #openstack-rally19:43
*** marcoceppi has quit IRC19:49
*** marcoceppi has joined #openstack-rally20:00
*** marcoceppi has joined #openstack-rally20:00
*** e0ne is now known as e0ne_20:05
*** e0ne_ is now known as e0ne20:05
*** tosky has joined #openstack-rally20:07
*** marcoceppi has quit IRC20:07
*** MaxPC has quit IRC20:16
*** marcoceppi has joined #openstack-rally20:19
*** marcoceppi has joined #openstack-rally20:19
*** dontalton has quit IRC20:32
*** dontalton has joined #openstack-rally20:33
*** Prashan__ has joined #openstack-rally20:42
*** PrashantS has quit IRC20:44
*** georgem1 has quit IRC20:45
*** frayedknot has quit IRC20:51
*** stpierre has quit IRC20:54
*** Prashan__ has quit IRC21:02
*** PrashantS has joined #openstack-rally21:02
*** gubouvier has joined #openstack-rally21:09
gubouvierHi guys, quick question: Is it normal, when I run a scenario on an existing tenant/user, that rally will cleanup everything after his tests, not only what it created ?21:12
gubouvierexample, I'm running NeutronNetworks.create_and_delete_networks, at the end, Rally will delete all the network of the tenant, not only his tests21:12
*** jaredroh_ has joined #openstack-rally21:18
*** karimb has joined #openstack-rally21:18
jaredroheI have a question:  Is it possible to have an __init__ method() in my scenario test that I want to benchmark with rally?  If I include a very simple __init__() method with only the keyword pass in the method body, I receive the following error:21:21
jaredrohe"TypeError: __init__() got an unexpected keyword argument 'admin_clients'"21:22
jaredroheIf I remove the __init__() method, rally benchmarks my script just fine21:23
*** stpierre has joined #openstack-rally21:27
*** e0ne is now known as e0ne_21:28
*** e0ne_ has quit IRC21:29
*** e0ne has joined #openstack-rally21:34
*** anshul has joined #openstack-rally21:36
*** stpierre has quit IRC21:39
*** stpierre has joined #openstack-rally21:39
*** e0ne is now known as e0ne_21:42
*** e0ne_ is now known as e0ne21:45
*** e0ne has quit IRC21:55
*** gubouvier has quit IRC22:01
*** karimb has quit IRC22:06
*** lutostag has quit IRC22:16
*** dontalton2 has joined #openstack-rally22:19
openstackgerritOmar Khalid proposed openstack/rally: Boot public images and test connectivity  https://review.openstack.org/19484622:28
*** masa_ has joined #openstack-rally22:49
*** masa_ has quit IRC22:51
*** PrashantS has quit IRC22:52
*** PrashantS has joined #openstack-rally22:52
*** PrashantS has quit IRC22:57
*** masa_ has joined #openstack-rally23:02
*** masa_ has quit IRC23:13
*** redixin has quit IRC23:15
*** dontalton2 has quit IRC23:16
*** dontalton has quit IRC23:16
*** anshul has quit IRC23:20
*** BitSmith has joined #openstack-rally23:22
*** stpierre has quit IRC23:29
*** masa_ has joined #openstack-rally23:33
*** masa_ has quit IRC23:34
*** masa_ has joined #openstack-rally23:34
*** masa_ has left #openstack-rally23:37
*** masa_ has joined #openstack-rally23:37
*** tosky has quit IRC23:43
*** masa_ has quit IRC23:56
*** masa_ has joined #openstack-rally23:57

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