Tuesday, 2015-11-24

*** boris-42 has joined #openstack-performance00:09
*** mdorman has quit IRC00:25
*** dims has joined #openstack-performance02:40
*** harshs has quit IRC03:08
*** dims has quit IRC03:17
*** dims has joined #openstack-performance03:22
*** dims has quit IRC03:35
*** mageshgv has joined #openstack-performance04:53
*** harlowja_at_home has joined #openstack-performance05:48
*** pasquier-s has quit IRC06:13
*** pasquier-s has joined #openstack-performance06:14
*** boris-42 has quit IRC06:48
*** arnoldje has quit IRC07:15
*** harlowja_at_home has quit IRC07:23
*** amaretskiy has joined #openstack-performance09:08
johnthetubaguycurious about the local-conductor vs remote-conductor debate, upgrade is what is forcing us to change to remote-conductor09:45
johnthetubaguythe load would otherwise be on the compute nodes, so its not all bad, more CPU on there, if you want to load on the compute nodes, run a conductor on them all09:46
johnthetubaguyusing pymysql should help a lot with reducing the number of conductors required09:46
DinaBelovajohnthetubaguy - yeah, that's why we're trying to understand what's going on with the issue seen on the GoDaddy's cloud :)09:59
johnthetubaguyDinaBelova: yeah, agreed, I am certainly interested10:56
*** dims has joined #openstack-performance11:06
DinaBelovawell, in fact I'll agree with SpamapS - on the dev env (like devstack or whatever) where metadata service is running as a part of nova-api, not the separated service nova-api-metadata on computes, metadata load I'm giving from the looped calls to the metadata service from the instances running is mostly affecting nova-api service itself rather then conductor. Afair klindgren_ mentioned they have about 32k metadata related calls in 1511:57
DinaBelova mins (both nova-api-metadata and nova-ec2-metadata). That gives ~35 requests per second. Of course they have 3 servers and about 60 total workers, that will be crazy enough on my VM with 2 cores :) So I have 2 nova-conductor workers and 2 nova-api (combined with nova-api-metadata). And if I'm having about ~30 VMs running with ~8-10 nova-api-metadata calls from them and (!!!) turned off metadata cache, I have ~90-100% CPU (from 200%11:57
DinaBelova total) eaten by nova-api :) Nova-conductor is giving from 10% to 20% :) So it looks like I won't be able to reproduce exactly the same situation on my env, sadly.11:57
DinaBelovaand all metadata requests to the conductor are quite fast, so I do not see too long ones like klindgren_ was seeing11:58
*** mageshgv has quit IRC12:03
DinaBelovararely conductor has spikes up to 30-35 - but that looks like something sporadic12:15
*** markvoelker has quit IRC13:35
*** markvoelker has joined #openstack-performance13:53
*** msemenov has joined #openstack-performance14:18
*** rvasilets___ has joined #openstack-performance14:21
*** regXboi has joined #openstack-performance14:23
*** zz_dimtruck is now known as dimtruck14:25
*** mriedem_away is now known as mriedem14:33
mriedemwe have a large ops job in the gate,14:54
mriedembut i don't think it's running the metadata service,14:55
mriedemand the tests are just booting up a bunch of servers and then waiting for them to be deleted (does that 3 times)14:55
DinaBelovamriedem - so nova-api-metadata is turned off fully14:55
DinaBelova?14:55
mriedemyeah http://logs.openstack.org/98/242698/10/check/gate-tempest-dsvm-large-ops/7ceded9/logs/14:56
DinaBelovaneither running as a part of nova-api or separately14:56
DinaBelovaok14:56
mriedemwe only run the nova metadata service in the postgres job http://logs.openstack.org/98/242698/10/check/gate-tempest-dsvm-postgres-full/eee7c06/logs/14:56
DinaBelovayeah, got it14:56
mriedemnot related to postgres, it was just another config to add that wrinkle14:56
DinaBelova#startmeeting Performance Team15:00
openstackMeeting started Tue Nov 24 15:00:15 2015 UTC and is due to finish in 60 minutes.  The chair is DinaBelova. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
openstackThe meeting name has been set to 'performance_team'15:00
DinaBelovahello folks o/15:00
mriedemo/15:00
bauzas\o15:00
DinaBelovatodays agenda located here15:00
DinaBelova#link https://wiki.openstack.org/wiki/Meetings/Performance#Agenda_for_next_meeting15:00
*** redixin has joined #openstack-performance15:00
*** Augie has joined #openstack-performance15:01
DinaBelovalet's wait for few more moments for others to come :)15:01
kun_huango/15:01
* regXboi stumbles in and finds a corner to fall asleep in15:01
andreykurilinhi Dina15:01
*** boris-42 has joined #openstack-performance15:01
Augiehello Dina15:02
DinaBelovahello folks!15:02
*** temujin_ has joined #openstack-performance15:02
DinaBelovaso let's start with action items :)15:02
DinaBelova#topic Action Items15:02
DinaBelovalast time we had several ones15:02
temujin_hi all15:02
DinaBelova#link http://eavesdrop.openstack.org/meetings/performance_team/2015/performance_team.2015-11-17-15.00.html15:03
boris-42hi15:03
DinaBelovatemujin_, boris-42  o/15:03
DinaBelovalet's start with boris-42 action item - update osprofiler spec to fit Mitaka cycle15:03
DinaBelovathat was done :)15:03
DinaBelovaboris-42 - please send the link here :)15:03
*** temujin_ is now known as oanufriev__15:03
regXboiDinaBelova, boris-42: do we expect another respin?15:04
andreykurilin#link https://review.openstack.org/#/c/103825/15:04
DinaBelovaandreykurilin - ah, thanks - I was looking for it15:04
*** rohanion has joined #openstack-performance15:04
*** rohanion is now known as rohanion_15:04
*** rohanion has joined #openstack-performance15:05
*** rohanion has left #openstack-performance15:05
DinaBelovaregXboi - do you mean new era of osprofiler? :)15:05
DinaBelovaor what?15:05
rvasilets___hi15:05
boris-42regXboi: some kind of that=)15:06
DinaBelovarvasilets___ o/15:06
* regXboi added an ask for the next respin of 10382515:06
* regXboi just wondering if it has a chance of being added15:06
DinaBelovaregXboi - I believe yes15:06
DinaBelovalast time this spec was active there were lots of +es there15:06
DinaBelovamost of the comments were regarding spelling, tc15:07
DinaBelovaetc*15:07
regXboiok, let me try again - I added a comment to PS7 of 103825 asking for an additional future to be added to the spec15:07
regXboiI want to know if that will be added to PS8 or if I have to look at spinning a new patch set to modify this if it merges15:07
DinaBelovaregXboi - sadly don't know. boris-42 ?15:08
*** dims_ has joined #openstack-performance15:08
* regXboi waves at dims_15:09
*** dims has quit IRC15:09
dims_hi regXboi15:09
DinaBelovaregXboi - well, I don't know still. Need closer look on current PS to undertsand if that info was added15:09
regXboiDinaBelova: no worries, we can move on15:10
DinaBelovaok, cool15:10
DinaBelovaone more action item regarding this etherpad15:10
DinaBelova#link https://etherpad.openstack.org/p/rally_scenarios_list15:10
DinaBelovasome info from IBM folks appeared here :)15:10
DinaBelovacool :)15:10
DinaBelovaalthough still want to see it updated by yahoo for instance (pink harlowja_ )15:11
DinaBelovaping*15:11
DinaBelovaalso I'll ping some Intel folks for them to fill this etherpad as well15:11
DinaBelovabut we see the progress has started15:11
DinaBelovaand then several items on me15:11
DinaBelovathe first one about writing the email to openstack-operators mailing list about various ratios15:12
DinaBelova#link http://lists.openstack.org/pipermail/openstack-operators/2015-November/008846.html15:12
DinaBelovaI pinged Kristian from ATT - he was not able to meet yet with ATT performance group to find out feedback on rally15:12
DinaBelovakun_huang - and I loved the video you've shared last time very much15:13
DinaBelovaI believe eventually we need performance benchmarking like that automated in gates15:13
DinaBelovafor various projects15:13
DinaBelova#link https://www.youtube.com/watch?v=a0qlsH1hoKs15:13
DinaBelovafor folks who did not see it yet ^^15:13
DinaBelovait's about neutron performance benchmarking from commit to commit15:14
kun_huangDinaBelova: +1, Kevid did a good job with rally15:14
DinaBelovakun_huang indeed15:14
DinaBelovaso that's it with action items from last time15:14
DinaBelovalet's move forward I guess now :)15:14
DinaBelovaany objectives?15:14
DinaBelovak15:15
DinaBelova#topic Team Work Items15:15
DinaBelovaharlowja_ has proposed really interesting idea during last week15:15
DinaBelovahe proposed to collect list of work items for performance team15:15
DinaBelovathat new comers (or members) can pick from15:15
DinaBelovaI've added section https://etherpad.openstack.org/p/perf-zoom-zoom15:16
DinaBelova#link https://etherpad.openstack.org/p/perf-zoom-zoom15:16
*** mdorman has joined #openstack-performance15:16
DinaBelovacalled "Work Items to grab"15:16
DinaBelovaand added two osprofiler specs to work on there15:16
DinaBelovaand I'm kindly encouraging people to add bugs, issues, investigations to be done, tests to be run here15:17
DinaBelovaI believe I'll need to send the email to openstack-operators mailing list about it as well15:17
DinaBelovaregXboi, Augie, mriedem - so if you have anything hot to take a look on - please put your thoughts there15:18
*** markvoelker has quit IRC15:18
*** markvoelker has joined #openstack-performance15:18
DinaBelova#action DinaBelova write an email about work items to the openstack-dev and openstack-operators15:18
AugieDina - OK, will do15:18
DinaBelovaAugie - thanks :)15:18
regXboiack15:18
mriedemyeah, need ML, can't keep track of the bazillion etherpads15:19
DinaBelovamriedem for sure :)15:19
DinaBelovawill do15:19
DinaBelovaI really hope that list of concrete items to work on can attract more people here15:19
DinaBelovaand some hands that can work on specific points15:19
DinaBelovanot something abstract like 'some' testing or whatever15:20
DinaBelovaany questions regarding this topic?15:20
*** Nikolay_St has joined #openstack-performance15:20
DinaBelovaok15:20
DinaBelovaso let's move forward (although today I feel like I'm having mostly monologue :))15:21
DinaBelova#topic Nova-conductor performance issues15:21
DinaBelovahot topic :)15:21
DinaBelovaok, so about latest news15:21
DinaBelovaI've tried to reproduce this issue on my dev env - sadly, that try was not very successful :(15:22
mriedemso one idea is running the n-api-meta service in the large ops job in the gate15:22
*** arnoldje has joined #openstack-performance15:22
DinaBelovaIn fact my nova-api service (containing nova-api-metadata inside) started eating CPU much faster than conductor15:22
mriedemthat job uses the nova fake virt driver though, so i'm not sure if some extra plumbing would be needed there to tickle it15:23
DinaBelovamriedem - I believe that will be useful15:23
DinaBelovain case of fake driver - yeah, I believe it'll be needed15:23
DinaBelovamriedem - I'll take a look on this faking as well on my env first of all15:23
DinaBelovaand then let's see if that will be more or less easy or not15:24
DinaBelovadon't think in fact :(15:24
mriedemwasn't SpamapS or someone talking about the nova fake virt driver yesterday?15:24
DinaBelovamriedem - yep, we were talking about this15:24
DinaBelovabut we have feeling it won't be very easy15:25
mriedemfwiw, adding n-api-meta to a large ops type config should be easy enough, would be a separate job maybe15:25
DinaBelovamriedem -ack15:25
mriedemi could poke on testing that out with a devstack-gate change, or talk to sdague about it15:25
DinaBelovamriedem - that will be super-nice15:25
mriedemi'll add a todo15:25
DinaBelovamriedem thanks15:26
DinaBelova#action mriedem testing that out with a devstack-gate  n-api-meta to a large ops type config change, or talk to sdague about it15:26
DinaBelovafyi right now I'm testing profiling periodical task15:27
DinaBelovafor conductor15:27
DinaBelovaon my env - if it works ok, I'll ask klindgren_ to run it as well15:27
DinaBelovaI guess that will add some info here as well (as right now I see much more load on the nova-metadata-api than on the conductor itself)15:27
DinaBelovaso probably something else is happening on their cloud we just don't know about15:28
DinaBelovaok, any additional ideas for me on what to look at here?15:28
DinaBelovak, let's move forward15:29
DinaBelova#topic OSProfiler weekly update15:29
DinaBelovaok, so about profiler - we have new version of the spec proposed by boris-42 - thanks :)15:30
DinaBelovaand currently the most interesting chain on review is https://review.openstack.org/#/c/247005/15:30
boris-42DinaBelova: heh that one is big15:31
DinaBelova:D15:31
boris-42DinaBelova: maybe we should split it to 2 patches15:31
DinaBelovaboris-42 - yep, possibly15:31
boris-42DinaBelova: one that adds strucutre of drivers15:31
boris-42DinaBelova: another that implements ceilometer on it15:31
boris-42DinaBelova: it will be simpler to review this to logical piece15:32
DinaBelovaI want to finish first my debug of what's going wrong with the adding osprofiler timestamps to the notifications15:32
DinaBelovaand then I can do that, yep15:32
DinaBelovathanks15:32
DinaBelova#action DinaBelova split https://review.openstack.org/#/c/247005/ to two commits: adding drivers structure and adding ceilometer driver15:32
DinaBelovaanyway I encourage everyone here to review what's currently available15:33
DinaBelovakun_huang, harlowja_, SpamapS  - you're welcome :)15:33
DinaBelovaand, as said, there are two more specs to work on15:34
DinaBelovathey're listed here https://etherpad.openstack.org/p/perf-zoom-zoom15:34
DinaBelovaand they still do not have any assignee :)15:34
DinaBelovaso please try working through them :)15:34
DinaBelovaany questions / ideas regarding osprofiler?15:35
DinaBelovaboris-42?15:35
boris-42DinaBelova: reading15:35
boris-42DinaBelova: no question about osprofiler=)15:35
DinaBelova:D for you I've prepared option 'ideas'15:36
DinaBelova:D15:36
DinaBelovaok, cool :)15:36
DinaBelovaToday we're having super-fast meeting :)15:36
DinaBelova#topic Open Discussion15:36
DinaBelovahere I just wanted to share the recent news with you, folks15:37
DinaBelovacurrently performance team inside Mirantis is working on various researches15:37
DinaBelovacurrently mostly around components like DB, MQ, Ceph, etc.15:37
DinaBelovaand we're preparing the testing plans to be shared with you, guys15:38
DinaBelovaI hope they will be available before the end of week15:38
DinaBelovaand then I'll kindly ask you folks to give some feedback on what else and how can be tested here15:38
DinaBelovaI'll ping kun_huang, harlowja_, SpamapS, mriedem, Augie, klindgren_ and others here and will write an email about that as well15:39
DinaBelovayour feedback will be essential - if any, we can add your items / test cases to the testing as well15:40
DinaBelovak, any other topics, ideas or issues to be discussed?15:40
DinaBelovaI'm feeling like I was disconnected and talking with myself for a while :)15:41
AugieDina - that's great on the testing plans...  Do you expect to use an environment withing Mirantis for the testing?15:41
Augiewithing = within15:41
DinaBelovaAugie - yep, currently we're having not very big lab available15:41
DinaBelovahoping to grab ~500 compute nodes close to the New Year15:42
DinaBelovabut this env will be Mirantis-available now15:42
Augieany thoughts on potential use of that Intel/Rackspace environment?15:42
*** Kristian__ has joined #openstack-performance15:43
DinaBelovaAugie - in terms of Mirantis and Intel coop we're planning to use it, but right now we are not using their super-big envs :)15:44
DinaBelovaso yep, it's planned15:44
Kristian__dina- here's latest Agile use case/feedback from my Rally development team@ t. being use case: as a test developer/executioner I want Rally to ramp up threads/users gradually over a configurable time period until reaching a target load so that tests with large loads a) do not have a sudden load impact on systems and b) a test can gradually increase until a breakpoint is found, instead of having to run subsequent tes15:44
AugieDina - ok15:44
DinaBelovaKristian__ o/15:44
DinaBelovaboris-42 ^^ please take a look and comment :)15:45
Kristian__finding breakpoints in OS deployment are crucial to us15:45
DinaBelovaKristian__ - so you want something like growing load pattern tests - am I right?15:45
Kristian__yes, so to paraphrase a bit- if rally detects load is too large at first, test can scale back at smaller load intervals then grow to higher load patterns until max load/errors based on SLA start forming15:47
DinaBelovaboris-42, are you around?15:47
andreykurilinKristian__: we have something like this in rally roadmap15:48
Kristian__so can stay for a bit, Boris knows how to reach me....i've got an open door for him15:48
DinaBelovaandreykurilin, a-ha, can you share the estimates on when this integration is planned?15:48
Kristian__ok.  @andreykurilin - which version is this expected in?15:48
andreykurilinI can give you any estimations. As far as I know, there are no activities on this type of runner. Let's move this topic for next meeting15:49
andreykurilin*I can't15:49
DinaBelovaandreykurilin, ack15:50
DinaBelova#acion andreykurilin find out the estimates on when growing load pattern tests runner will be available in Rally15:50
DinaBelovaok, so it looks like we're done here15:51
andreykurilin#action andreykurilin find out the estimates on when growing load pattern tests runner will be available in Rally15:51
DinaBelova:D15:51
DinaBelovaok, so two action items on you :)15:51
DinaBelovaanything else to be discussed?15:51
andreykurilinno, your action item doesn't have char "t"15:51
andreykurilin:)15:51
DinaBelovaah :)15:51
DinaBelovayou're right :)15:51
DinaBelovaok, so I guess that's it for today15:52
DinaBelovathanks everyone for coming and taking part :)15:52
mriedemthanks15:52
DinaBelova#endmeeting15:52
openstackMeeting ended Tue Nov 24 15:52:18 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/performance_team/2015/performance_team.2015-11-24-15.00.html15:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/performance_team/2015/performance_team.2015-11-24-15.00.txt15:52
openstackLog:            http://eavesdrop.openstack.org/meetings/performance_team/2015/performance_team.2015-11-24-15.00.log.html15:52
Kristian__ty @DinaBelova and  @andreykurilin15:52
*** Kristian__ has quit IRC15:52
*** rohanion_ has quit IRC15:53
*** Augie has quit IRC15:53
*** tdurakov has joined #openstack-performance15:55
klindgren_doh - earl meeting15:56
klindgren_early*15:56
*** rfolco_ has joined #openstack-performance16:03
*** tdurakov has quit IRC16:03
DinaBelova:D16:06
DinaBelovaI guess we need revote on moving it to one hour later :)16:06
DinaBelovato make it more US friendly :)16:06
DinaBelovaklindgren_ and harlowja_ I guess will be happy :)16:06
klindgren_it wasn't in my schedule is all - but I normally start work around this time so +1 hour would rock :-D16:13
kun_huangDinaBelova: is it possible to organize a team like openstack-security?16:21
DinaBelovakun_huang - do you mean official openstack team working on performance issues?16:24
*** harshs has joined #openstack-performance16:24
kun_huangDinaBelova: yep16:25
DinaBelovaI've spoken about it with Thierry - he told, that we need to start with non-official working group like API working group for instance - so in fact it is what's we are now - https://wiki.openstack.org/wiki/Category:Working_Groups - here you can see Performance Team as well16:26
DinaBelovaand then after some work16:26
DinaBelovaand results16:26
DinaBelovateam may become acknowledged by the TC16:27
DinaBelovakun_huang ^^16:27
DinaBelovaso we need to continue working and collect results of our work :) once there will be some of them, we can become acknowledged by the TC and become official OpenStack team16:27
boris-42DinaBelova: load growing runner will be soon16:29
DinaBelovaboris-42 - wow, cool :)16:29
DinaBelovais it scheduled for some of rally releases?16:29
boris-42DinaBelova: https://review.openstack.org/#/c/234195/16:29
boris-42DinaBelova: something like this16:29
boris-42DinaBelova: nope it is not scheduled=)16:29
DinaBelova:) yeah, once it'll be merged - yep? :)16:29
boris-42DinaBelova: but it won't be based on SLAs16:29
boris-42DinaBelova: that thing that is asked by Kristian will be later16:30
*** dims_ has quit IRC16:30
DinaBelovaok, cool16:30
boris-42DinaBelova: but I have some thoughts16:31
boris-42DinaBelova: in any case it's not the most high priority for me now16:31
DinaBelovaack, gotcha16:32
* notmorgan is curious why the meetings happen in this channel instead of -meeting channels?16:42
DinaBelovanotmorgan - we used the same practice Large Deploymetns team is using - they are having meetings on #openstack-operators channel simply because there are too many meetings already on the *-meeting chanels and that will b really hard to find the timeslot good both for the channels and people. in fact right now any official openstack irc channel can be used for meetings if meetbot is monitoring it16:45
*** tdurakov has joined #openstack-performance16:45
*** dims has joined #openstack-performance16:46
notmorganright. just the -meeting channels tend to have more eyes and often have more people involved than the more isolated local channels16:47
* notmorgan also has stopped lurking the the -meeting channels anyway, but...16:47
notmorganthat is aside16:47
notmorganjust was curious16:47
DinaBelovanotmorgan - yeah, official channels have more eyes on them definitely... but timeslots available for both european, chinese and US timezones are very busy there :)16:48
DinaBelovaalthough even ours is late for Asia16:49
*** dims has quit IRC17:18
*** dims_ has joined #openstack-performance17:18
*** regXboi has quit IRC17:19
*** tdurakov has quit IRC17:23
*** harshs has quit IRC17:26
*** amaretskiy has quit IRC17:42
harlowja_DinaBelova hi!17:51
harlowja_lol17:51
DinaBelovaharlowja_, morning sir :)17:51
harlowja_i sorta slept in, oops, was working late on/messing around with https://review.openstack.org/#/c/244376/ :-P17:52
harlowja_DinaBelova morning lady!17:52
harlowja_actually i don't think its morning, ha17:52
DinaBelova:D17:52
DinaBelova9PM here :)17:52
harlowja_boris-42 what u doing17:52
harlowja_DinaBelova evening lady!17:52
harlowja_lol17:52
harlowja_there fixed it :-P17:52
DinaBelovaharlowja_ lol17:52
harlowja_:)17:54
harlowja_+1 DinaBelova  looks like a useful meeting, sorry i sorta slept past it :-/17:55
harlowja_ "Work Items to grab"  + 217:55
harlowja_next meeting, i guess after US thanksgiving perhaps I can not sleep in and talk about how to create a place for sharing rally results17:55
harlowja_boris-42 will make the site for us, and we can find a place to host it and get people to easily upload rally results (hopefully frequently...)17:56
DinaBelova:D17:57
harlowja_right boris-42 ???!!?? :-P17:57
*** rvasilets___ has quit IRC17:59
boris-42harlowja_: =))))18:04
harlowja_;)18:05
harlowja_that means yes boris-4218:05
harlowja_DinaBelova so we have a site-designer now, lol18:05
DinaBelovaharlowja_ - you need to be the sales person, what the hell are you doing among devs? :)18:06
harlowja_lol18:06
harlowja_someone has to write all these libraries :-P18:06
harlowja_*these oslo/other libraries18:06
harlowja_boris-42 does rally produce output in a parseable format, like json or a zip file or something that people can upload18:08
harlowja_i'm assuming yes18:08
harlowja_but just want to check18:08
harlowja_(i should really get around to messing more around with rally)18:08
boris-42harlowja_: yep it produces results in raw json18:10
harlowja_ok, many json files or just one?18:10
* harlowja_ just thinking of a simple archive format people could upload 18:10
*** mriedem has quit IRC18:17
*** mriedem has joined #openstack-performance18:21
*** harshs has joined #openstack-performance18:30
*** tdurakov has joined #openstack-performance18:38
*** tdurakov has quit IRC19:09
*** tdurakov has joined #openstack-performance19:10
*** regXboi has joined #openstack-performance19:46
*** dims has joined #openstack-performance19:53
*** dims_ has quit IRC19:56
*** arnoldje has quit IRC19:57
*** rfolco_ has quit IRC20:00
*** arnoldje has joined #openstack-performance20:14
harlowja_boris-42 is https://review.openstack.org/#/c/103825 basically asking for oslo to take in osprofiler?20:17
harlowja_lots of other stuff there, but is it primiarily oslo adopt it?20:17
harlowja_i get the how it works stuff, so just wondering :-P20:18
dimsharlowja_ : does it say what we need to do in Oslo?20:22
harlowja_dims no, but i know boris-42 has been told to go put that spec in like 25 places20:22
harlowja_and its in oslo-specs now20:22
harlowja_so i'm just wondering20:22
* harlowja_ personally has no issue doing that, if thats the desire20:23
* harlowja_ would rather not have boris-42 need to move that spec for the 26th time because people can't commit to things...20:27
dimsharlowja_ y i was just looking for what to do :)20:27
harlowja_dims partially me to ;)20:28
harlowja_its a nice overview of it all so thats cool :-P20:28
harlowja_would be a nice sphinx doc  page if its not already20:28
harlowja_https://github.com/openstack/osprofiler/blob/master/README.rst is a little hairy (to much info) imho20:29
mriedemdoes anyone here care about the performance of nova's unshelve operation? https://review.openstack.org/#/c/135387/20:51
*** redixin has quit IRC21:17
*** regXboi has quit IRC21:25
*** badari has joined #openstack-performance21:26
*** redixin has joined #openstack-performance21:30
*** tdurakov has quit IRC21:35
*** arnoldje has quit IRC21:36
*** dims has quit IRC21:37
*** dims has joined #openstack-performance21:38
*** dimtruck is now known as zz_dimtruck21:48
*** boris-42 has quit IRC21:48
*** moravec has joined #openstack-performance21:50
*** arnoldje has joined #openstack-performance22:03
*** mriedem has quit IRC22:38
*** redixin has quit IRC23:02
*** harshs has quit IRC23:03
*** redixin has joined #openstack-performance23:05
*** harshs has joined #openstack-performance23:08
*** boris-42 has joined #openstack-performance23:10
boris-42harlowja_: for now it is single json23:12
harlowja_boris-42 k23:12
boris-42harlowja_: in future it may be many files with crapy organization23:12
harlowja_lol23:12
harlowja_k23:12
*** dims_ has joined #openstack-performance23:28
*** redixin has quit IRC23:29
*** dims has quit IRC23:29

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