Monday, 2019-03-18

*** slaweq_ has joined #openstack-meeting-alt00:11
*** slaweq_ has quit IRC00:24
*** dave-mccowan has joined #openstack-meeting-alt00:29
*** dave-mccowan has quit IRC00:31
*** jamesmcarthur has joined #openstack-meeting-alt00:58
*** slaweq_ has joined #openstack-meeting-alt01:11
*** slaweq_ has quit IRC01:24
*** lbragstad has joined #openstack-meeting-alt01:40
*** jamesmcarthur has quit IRC01:45
*** jamesmcarthur has joined #openstack-meeting-alt01:55
*** jamesmcarthur has quit IRC02:06
*** jamesmcarthur_ has joined #openstack-meeting-alt02:06
*** slaweq_ has joined #openstack-meeting-alt02:11
*** lbragstad has quit IRC02:17
*** irclogbot_1 has quit IRC02:23
*** slaweq_ has quit IRC02:24
*** edleafe has quit IRC02:27
*** jamesmcarthur_ has quit IRC02:59
*** slaweq_ has joined #openstack-meeting-alt03:11
*** hongbin has joined #openstack-meeting-alt03:12
*** hongbin has quit IRC03:21
*** slaweq_ has quit IRC03:25
*** whoami-rajat has joined #openstack-meeting-alt03:46
*** ttsiouts has quit IRC03:52
*** janki has joined #openstack-meeting-alt04:05
*** slaweq_ has joined #openstack-meeting-alt04:14
*** slaweq_ has quit IRC04:24
*** chhagarw has joined #openstack-meeting-alt04:45
*** slaweq_ has joined #openstack-meeting-alt05:16
*** absubram has joined #openstack-meeting-alt05:23
*** slaweq_ has quit IRC05:24
*** absubram_ has joined #openstack-meeting-alt05:27
*** absubram has quit IRC05:28
*** absubram_ is now known as absubram05:28
*** rcernin has quit IRC05:43
*** vishalmanchanda has joined #openstack-meeting-alt05:47
*** rcernin has joined #openstack-meeting-alt05:59
*** jbadiapa has joined #openstack-meeting-alt06:06
*** slaweq_ has joined #openstack-meeting-alt06:11
*** slaweq_ has quit IRC06:24
*** e0ne has joined #openstack-meeting-alt06:40
*** absubram has quit IRC06:45
*** brault has joined #openstack-meeting-alt06:46
*** brault has quit IRC06:55
*** e0ne has quit IRC07:02
*** kopecmartin|off is now known as kopecmartin07:03
*** jtomasek has joined #openstack-meeting-alt07:12
*** slaweq_ has joined #openstack-meeting-alt07:13
*** apetrich has joined #openstack-meeting-alt07:38
*** yamamoto has quit IRC08:04
*** yamamoto has joined #openstack-meeting-alt08:05
*** ttsiouts has joined #openstack-meeting-alt08:06
*** yamamoto has quit IRC08:06
*** ccamacho has joined #openstack-meeting-alt08:19
*** sridharg has joined #openstack-meeting-alt08:20
*** priteau has joined #openstack-meeting-alt08:26
*** lennyb has joined #openstack-meeting-alt08:34
*** tssurya has joined #openstack-meeting-alt08:36
*** brault has joined #openstack-meeting-alt09:03
*** brault has quit IRC09:09
*** jrbalderrama has joined #openstack-meeting-alt09:14
*** rfolco has joined #openstack-meeting-alt09:34
*** yamamoto has joined #openstack-meeting-alt10:22
*** yamamoto has quit IRC10:22
*** e0ne has joined #openstack-meeting-alt10:28
*** yamamoto has joined #openstack-meeting-alt10:28
*** masahito has quit IRC10:30
*** jbadiapa has quit IRC10:44
*** slaweq_ is now known as slaweq11:14
*** ttsiouts has quit IRC11:21
*** rcernin has quit IRC11:46
*** ttsiouts has joined #openstack-meeting-alt11:47
*** raildo has joined #openstack-meeting-alt11:52
*** edleafe has joined #openstack-meeting-alt12:21
*** markvoelker has quit IRC12:22
*** yamamoto has quit IRC12:30
*** whoami-rajat has quit IRC12:35
*** e0ne has quit IRC12:51
*** e0ne has joined #openstack-meeting-alt12:52
*** yamamoto has joined #openstack-meeting-alt12:55
*** jtomasek_ has joined #openstack-meeting-alt13:02
*** jtomasek has quit IRC13:03
*** jtomasek_ has quit IRC13:05
*** jtomasek has joined #openstack-meeting-alt13:05
*** whoami-rajat has joined #openstack-meeting-alt13:08
*** dave-mccowan has joined #openstack-meeting-alt13:09
*** dave-mccowan has quit IRC13:15
*** lbragstad has joined #openstack-meeting-alt13:18
*** lseki has joined #openstack-meeting-alt13:27
*** ttsiouts has quit IRC13:36
*** alex_xu has joined #openstack-meeting-alt13:40
*** ttsiouts has joined #openstack-meeting-alt13:41
*** absubram has joined #openstack-meeting-alt13:41
*** ttsiouts_ has joined #openstack-meeting-alt13:42
*** absubram_ has joined #openstack-meeting-alt13:42
*** absubram has quit IRC13:45
*** absubram_ is now known as absubram13:45
*** ttsiouts has quit IRC13:46
*** cdent has joined #openstack-meeting-alt13:52
*** tetsuro has joined #openstack-meeting-alt13:57
*** e0ne has quit IRC13:58
*** mriedem has joined #openstack-meeting-alt13:58
*** takashin has joined #openstack-meeting-alt13:59
* cdent glances at efried 14:00
efried#startmeeting nova-scheduler14:00
openstackMeeting started Mon Mar 18 14:00:44 2019 UTC and is due to finish in 60 minutes.  The chair is efried. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova-scheduler)"14:00
openstackThe meeting name has been set to 'nova_scheduler'14:00
cdent\o/14:00
takashino/14:00
efriedwhat, I was like 45 seconds late14:00
alex_xu\o14:00
efriedChanging over the laundry. Thought I was going to bleed into the next minute, but I made it.14:01
cdentthat was a glance not a glare14:01
* bauzas sits at the back14:01
tetsuroo/14:01
efried#link Agenda https://wiki.openstack.org/wiki/Meetings/NovaScheduler#Agenda_for_next_meeting14:01
efried#topic last meeting14:01
efried#link last minutes http://eavesdrop.openstack.org/meetings/nova_scheduler/2019/nova_scheduler.2019-03-11-14.00.html14:01
*** openstack changes topic to "last meeting (Meeting topic: nova-scheduler)"14:01
efried#link DRY/clean up placement objects phase 2 https://review.openstack.org/#/q/topic:cd/de-list-phase2+(status:open+OR+status:merged)14:01
efried^ merged \o/14:01
efriedother ol bidniss?14:02
edleafew00t!14:02
* efried apologizes to non-English speakers14:02
efriedAny other old business?14:02
efried#topic specs and review14:02
efried#link latest pupdate http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003865.html14:02
*** openstack changes topic to "specs and review (Meeting topic: nova-scheduler)"14:02
efried#link negative aggregate membership https://review.openstack.org/#/q/topic:bp/negative-aggregate-membership14:03
efried^ Minimal additional work to make ready for Train14:03
* alex_xu is googling14:03
efriedFolks could render opinions on:14:04
efried#link getting rid of backslash continuations https://review.openstack.org/#/c/641497/14:04
mriedemo/14:04
efriedand whether14:04
efried#link using ``code`` role in section titles http://logs.openstack.org/04/641404/5/check/openstack-tox-docs/1d2faee/html/placement-api-microversion-history.html14:04
efriedis still ugly/shouting14:04
efriedIt appears to be bad on mac, fine on linux/windows.14:04
edleafeAs the pep8 document clearly states, readability trumps absolute adherence to the guidelines14:04
mriedemi don't love http://logs.openstack.org/04/641404/5/check/openstack-tox-docs/1d2faee/html/placement-api-microversion-history.html but it's better than it was originally14:05
*** dtrainor has joined #openstack-meeting-alt14:05
*** e0ne has joined #openstack-meeting-alt14:05
efriedmriedem: So IYO, go with it or trash it?14:05
mriedemi don't have a real strong opinion on this14:06
efriedight14:06
efriedMaybe finucannot has one.14:06
cdentlet's do whatever finucannot wants14:06
efriedbut I don't think he's around atm14:06
bauzashe's on holiday today14:06
mriedemheh i'm sure he has a bias since he added that to the docs theme tooling14:06
cdentmy passport says I should be on holiday today too14:06
bauzas(Irish people have some times after a beer day, that's it)14:07
efriedoh, is it a "bank holiday"?14:07
cdenton the island of ireland, yes14:07
efriedAny other reviews to discuss?14:08
efriedWhat about bps/specs lined up for Train?14:08
cdentI have some doc changes that landed this morning/last night14:08
cdentand are needed before we cut the rc14:08
efriedlanded meaning proposed?14:08
efriedPlease link, I will review soonest.14:09
*** carlos_silva has joined #openstack-meeting-alt14:09
cdent(yes, as in landed on gerrit... ) there's still 1 or 1.5 big things left to do on the docs for rc front: upgrade from nova docs, and releasenotes review and prelude creation14:09
cdent#link from-pypi install: https://review.openstack.org/#/c/643938/14:10
cdent#link restructure install: https://review.openstack.org/#/c/643919/14:10
cdent#link database singularity fix: https://review.openstack.org/#/c/643915/14:10
cdent#link cleaner usage docs: https://review.openstack.org/#/c/643913/14:10
efriedack14:11
edleafecdent: will review those soon14:11
cdentdo we have any volunteers for the upgrade from nova docs? It needs to be available for review by wednesday at the latest14:11
efriedI wouldn't know what that looks like I'm afraid. Can we tap like a lyarwood or a tonyb?14:12
cdentwhy would they be good choices?14:12
efriedDon't they know how to upgrade things?14:12
efriedor, like, install things?14:12
efriedSee, I don't even know who *knows* how to do that shit.14:13
efriedI'm clearly a terrible choice.14:13
mriedemwouldn't that doc, at the very least, essentially be a walk through of the steps in the grenade patch?14:13
cdentthe issue isn't the way to normally do an upgrade, but rather the way in which upgrades are different14:13
cdentmriedem: yes, that's the plan, as stated on the pupdate14:13
cdentIf nobody wants to volunteer I can do it, but I didn't want to clobber any toes that were already started14:13
cdentalso by having me do it, that means there's an added "why can't he type!?" review burden14:14
mriedemdoesn't matter to me, if you can't get to it i can put words to https://github.com/openstack-dev/grenade/blob/master/projects/60_nova/from-rocky/upgrade-nova14:14
mriedemsince we both worked on it14:14
mriedemit won't be pretty but anything is better than nothing14:14
cdentI think given that you (mriedem) are probably in some criitical nova paths, I'll take it14:15
mriedemheh, i'm trying not to be, but ok14:15
cdent#action cdent nova-to-placement upgrade doc14:15
efriedSpec-wise, I wanted to mention this as an early warning: I haven't started yet, but I plan to scribble down something to enable inter-provider affinity for various cases like NUMA and similar. We've brainstormed a few ideas on this at the past several PTGs but never really landed on anything (or, to my knowledge, written anything down).14:15
efriedPerhaps as a lead-in, I should start an etherpad to gather ideas first.14:16
cdentWhile I think that's worth thinking/talking about, I would be put it pretty far behind getting nova using shared and nested more than it currently does14:16
cdentI think there are plenty of non-affinity-using use cases that are not yet filled14:17
cdentwhich is not to stymie any writing down. Definitely write down.14:17
mriedemspeaking of docs, i guess i'll be writing something up about https://review.openstack.org/#/c/538498/ in the nova reference docs14:17
efried#link inter-provider affinity brainstorm etherpad https://etherpad.openstack.org/p/placement-inter-provider-affinity14:18
efriedmriedem: Can't you get aspiers to do it?14:18
efriedI mean, we already suckered him into finishing the patch14:18
mriedemhe's been poked a few times so i think he's probably ignoring it14:18
efriedAnd he did such an excellent job...14:18
efriedokay.14:19
mriedemso i'll just puke up some words14:19
mriedemhe's also busy backporting this sev stuff for suse...14:19
efriedokay14:20
efried#action mriedem to document compute driver capability traits per https://review.openstack.org/#/c/538498/14:20
efriedanything else review/spec wise?14:20
efried#topic bugs14:20
efried#link Placement bugs (launchpad) https://bugs.launchpad.net/nova/+bugs?field.tag=placement14:20
efried#link Placement storyboard https://storyboard.openstack.org/#!/project_group/placement14:20
*** openstack changes topic to "bugs (Meeting topic: nova-scheduler)"14:20
cdentonce RC is done and the dust settles, I intend to write up a refreshed spec on shared disk (after I do some learning)14:21
efriedany bugs to mention? In particular, things we want in Stein?14:21
efriedcdent: lmk if you want help with that.14:21
cdentwhen I checked friday there wasn't anything critical bugwise, except for the already mentioned docs14:21
cdentI'll do another review of that either later today or tomorrow morning14:21
bauzasthat reminds me one question14:21
cdentbut the impression that I had was that except for docs we are releasable14:21
efriedcool14:22
bauzaswhat would we our backport policy once we cut RC1 ?14:22
bauzasfor bugfixes14:22
mriedemsame as always14:22
mriedemright?14:22
mriedemwhy change it14:22
efriedI'm a little curious whether we backport bugfixes into nova-placement14:22
cdentyeah, what were you thinking bauzas ?14:22
bauzasshould we have backports to Stein and older against both placement and nova repos ?14:22
efriedyeah, that14:22
bauzasokay I'm cool14:22
cdentsecurity fixes only to nova, I'd say14:23
efriedI agree14:23
cdentbecause it's not supposed to be a "real" thing14:23
bauzascdent: actually, it's a question to the placement team, would you follow the stable policy ?14:23
efriedEncourage people to move.14:23
cdentbauzas: for now, yes14:23
bauzasif you follow the stable policy, all bugfixes, not only security ones, are candidates for backports14:24
cdentI think there is scope to talk (some ways in the future) about getting off the standard release cycle but that's not something to do any time soon14:24
cdentbauzas: yes, but nova isn't placement, so it doesn't matter14:24
cdenthow14:24
cdentever14:24
bauzasI don't get the answer14:24
cdentIf we want to go back to rocky then yes, we would need to go back to nova14:24
bauzasif someone proposes a change against stable/nova, I guess we will accept it14:24
cdenti'm crossing my fingers that that won't be necessary14:25
mriedemlet's deal with the hypothetical when it actually comes up14:25
cdentyes14:25
edleafemriedem: I was just typing something similar14:25
mriedemi don't notice a lot of critical placement bugs right now14:25
bauzaswell, we'll branch with RC1, but sure, let's not rathole on it14:25
cdentwe've been really lucky so far, so let's hope it continues14:25
edleafes/lucky/skilled14:25
edleafe:)14:25
mriedemwe've had some stuff that needed to go to both like that one postgres fix14:26
mriedemfor the consumers migration14:26
mriedembut those are fairly obvious14:26
efriedBacktracking again, one more spec-ish thing to bring up.14:26
efried#link Nova scheduler using openstacksdk instead of direct ksa to talk to placement https://review.openstack.org/64366414:26
efriedWondering if this needs a bp and/or spec.14:26
efriedperhaps for the broader goal of using sdk for all our talk-to-services14:27
mriedema broader change to the sdk yes would be a bp at least imo14:27
mriedemswapping the scheduler client stuff for sdk seems like not a huge win to me since the scheduler client is already just using ksa14:27
mriedemgetting rid of cinderclient/neutronclient/glanceclient are much bigger deals14:28
*** hongbin has joined #openstack-meeting-alt14:28
efriedoh, for sure, the only win is proving that the tweaks made in sdk work.14:28
efriedand establishing the framework in nova14:28
mriedemsounds like ptg fodder to me14:28
efriedwhich, with the sdk tweaks, turns out to be fairly simple.14:28
efriedk, I think I added it to the ptg etherpad already14:29
mriedemyou'll just have to work on your sales pitch14:29
cdentwear a tie14:29
efriedI'll just have mordred walk in14:29
efriedwhereupon the Harlem Gospel Choir will burst into song14:30
efriedmoving on14:30
* bauzas won't do any "walks into a bar" jokes14:30
efried#topic opens14:30
efriedOn the agenda:14:30
efriedShould we further split objects/resource_provider.py? How?14:30
*** openstack changes topic to "opens (Meeting topic: nova-scheduler)"14:30
*** jrbalderrama has quit IRC14:30
efriedThis came up because cdent put up a patch to reorder the remaining 2KLOC of objects/resource_provider.py14:30
efriedand I poo-pooed it14:31
cdentand we all ran screaming14:31
efriedand said I wanted to instead/first split resource_provider.py into (yet) smaller chunks14:31
efriedThe only obvious way to do this is to sub-module it based on what things you're mucking with on the resource provider.14:31
cdentanother is db/not-db14:32
efriedSo we have a module for Trait, where you mess with actual traits; but there would be a resource_provider.traits where you would mess with a resource provider's traits.14:32
cdentbut that's probably more invasive14:32
edleafeI really don't like the idea of sub modules14:32
efriedI talked to edleafe last week about this, and he really didn't like the idea of sub modules.14:32
edleafeRPs are big, complex things. It stands to reason that the code to describe them would be large.14:33
efriedhow do others feel? Is 2KLOC small enough to not be worth the potential confusion of sub-module namespaces?14:33
efriedalso keeping in mind that resource_providers.py could grow14:33
efriedunless tetsuro keeps trimming it down, which is ++14:33
cdentMy attitude is perhaps clear: I think long modules are bad news and that efforts to split them up seems to always lead to non-size related cleanups and bug fixes, so my preference would be that we consider size a bug, and fix things as possible14:34
efried#link -74LOC in resource_provider.py https://review.openstack.org/#/c/643729/14:34
*** yamamoto has quit IRC14:34
edleafeTraits only apply to RPs. So where do we draw the line between objects.resource_provider.traits and objects.traits?14:34
cdentnot because size is _literally_ a bug, but it is a good excuse14:34
efriededleafe: that's an easy one: objects.trait is for creating, deleting, and listing traits14:35
efriededleafe: resource_provider.traits is for changing what traits are on a resource provider.14:35
edleafeIt really feels like an artificial split because of an aversion to a large module14:35
cdentefried: you started a placement-related ptg etherpad at some point yes? put "refactoring goals and constraints" on there, perhaps?14:36
efriedI didn't14:36
cdentwhat am I remember then?14:36
efriedI asked whether you did14:36
cdentalright14:36
efriedin the middle of the night or on a weekend or something14:36
cdent#action cdent make a ptg etherpad with refactoring goals and constraints on it14:36
cdent(amongst other things)14:37
edleafeI would much prefer to reorder resource_provider.py to group all the trait-related methods together14:37
*** yamamoto has joined #openstack-meeting-alt14:37
efrieddon't forget to add it to https://wiki.openstack.org/wiki/PTG/Train/Etherpads -- it seems like other teams have forgotten this.14:37
efriededleafe: it's already in that order14:37
efriedwhich is another thing.14:37
cdentwe already moved some trait stuff out of rp,14:37
edleafeThen I don't have a problem with it14:37
cdentand kept the rp related stuff (for setting) in rp14:37
efriedI don't like the idea of reordering to class->public->private->alpha14:37
efriedI prefer keeping related stuff together.14:38
efried(like, in a module, but failing that...)14:38
edleafevim is really fast at searching :)14:38
efriedSure, so are real IDEs14:38
cdentThe idea beyond that mode is that you don't have to have subjective debates (as we already have over what is "related" to something else)14:38
efriedbut it's nice to be able to see both methods on the same screen.14:38
cdentit's the same reason for stick to pep814:38
cdentthey aren't good rules14:38
cdentbut they are easy to calculate rules14:38
cdentif we try a little bit harder, we can paint both of these sheds before the end of the hour14:39
cdentor we could talk about something else14:39
efriedyeah, let's move on.14:39
efriedWe have been carrying these three until we had a new PTL:14:39
efried(From last last last last week) Format of this meeting - new PTL to query ML14:39
efried(From last last last last week) Placement team logistics at PTG - new PTL to query ML14:39
efried#link post-extraction plans for placement specs/bps/stories http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003102.html14:39
cdent(I'd enjoy seeing a refactoring and code structure ml discussion, btw)14:40
efriedwow, I don't think I would enjoy that.14:40
efriedthat would go off into the weeds right quikck.14:40
cdentyeah, gist is: specs in placement repo itself, bps as stories in storyboard, but I'm going to formalize that after the RC14:40
cdent(sure it would, which is why email is a better place, it's async)14:41
edleafe+1 to specs in the placement repo14:41
*** e0ne has quit IRC14:41
efriedYeah, I don't think that one is too controversial, we seemed to reach consensus fairly easily14:42
efriedcdent: Would you like to open the discussion of fate of this meeting and/or PTG logistics here prior to asking ml?14:42
*** e0ne has joined #openstack-meeting-alt14:42
*** sridharg has quit IRC14:42
*** yamamoto has quit IRC14:42
cdentI think we have insufficient people participating here right now for any decisions made here, now, to stick. So I've got nothing on that, but if people have things to say, go for it14:43
efriedyeah, just thought a quick brainstorm14:44
cdentIf we make an RC and the world doesn't explode, I'll take core of that stuff soon after that14:44
cdentcare14:44
cdentbut speaking of core14:44
cdentI'm going to port the nova-cores to placement, but would prefer to only port those that are actually interested14:45
cdenta plan, which I'd like people here to verify or dismiss is: post to the ml asking for positive assent to be added to placement-code. That allows people who don't care or aren't paying attention to be dropped without effort14:45
cdentThoughts?14:46
mriedem+14:46
mriedemfwiw nova-core itself needs to be trimmed14:46
bauzasthat's fair14:46
efried++ cdent14:46
cdentI'm not expecting there to be anyone who wants to participate but shouldn't, but if that comes up we'll cross that bridge14:47
edleafeAnd, of course, anyone who later decides to become active would be welcomed back14:48
cdentdamn, was hoping to be able to shun14:48
cdentI got nothing else14:50
efriedanybody anything else for opens?14:51
efriedalright, thanks all o/14:52
efried#endmeeting14:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:52
openstackMeeting ended Mon Mar 18 14:52:42 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2019/nova_scheduler.2019-03-18-14.00.html14:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2019/nova_scheduler.2019-03-18-14.00.txt14:52
cdentthanks efried14:52
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2019/nova_scheduler.2019-03-18-14.00.log.html14:52
*** mriedem has left #openstack-meeting-alt14:52
*** e0ne has quit IRC14:53
*** takashin has left #openstack-meeting-alt14:53
*** tetsuro has quit IRC14:54
*** e0ne has joined #openstack-meeting-alt14:55
*** liuyulong has joined #openstack-meeting-alt14:57
*** jamesmcarthur has joined #openstack-meeting-alt15:02
*** e0ne has quit IRC15:05
*** e0ne has joined #openstack-meeting-alt15:20
*** janki has quit IRC15:26
*** absubram has quit IRC15:29
*** absubram has joined #openstack-meeting-alt15:29
*** yamamoto has joined #openstack-meeting-alt15:34
*** yamamoto has quit IRC15:42
*** ttsiouts_ has quit IRC16:05
*** ttsiouts has joined #openstack-meeting-alt16:13
*** e0ne has quit IRC16:14
*** e0ne has joined #openstack-meeting-alt16:19
*** jrbalderrama has joined #openstack-meeting-alt16:19
*** cdent has left #openstack-meeting-alt16:26
*** diablo_rojo has joined #openstack-meeting-alt16:33
*** tssurya has quit IRC16:44
*** iyamahat has quit IRC16:45
*** brault has joined #openstack-meeting-alt16:45
*** brault has quit IRC16:50
*** ttsiouts has quit IRC16:57
*** iyamahat has joined #openstack-meeting-alt17:03
*** jgrosso has joined #openstack-meeting-alt17:13
*** e0ne has quit IRC17:14
*** yamahata has joined #openstack-meeting-alt17:20
*** kopecmartin is now known as kopecmartin|off17:22
*** jamesmcarthur has quit IRC17:38
*** jamesmcarthur has joined #openstack-meeting-alt17:39
*** yamamoto has joined #openstack-meeting-alt17:53
*** gyee has joined #openstack-meeting-alt17:58
*** jtomasek has quit IRC18:18
*** jtomasek has joined #openstack-meeting-alt18:18
*** jrbalderrama has quit IRC18:33
*** jamesmcarthur has quit IRC18:41
*** jamesmcarthur has joined #openstack-meeting-alt18:56
*** jamesmcarthur has quit IRC19:00
*** dave-mccowan has joined #openstack-meeting-alt19:05
*** chhagarw has quit IRC19:06
*** jamesmcarthur has joined #openstack-meeting-alt19:18
*** jamesmcarthur has quit IRC19:19
*** igordc has joined #openstack-meeting-alt19:22
*** jamesmcarthur has joined #openstack-meeting-alt19:23
*** whoami-rajat has quit IRC19:55
*** jamesmcarthur has quit IRC20:00
*** jamesmcarthur has joined #openstack-meeting-alt20:09
*** jamesmcarthur has quit IRC20:10
*** jamesmcarthur has joined #openstack-meeting-alt20:10
*** irclogbot_1 has joined #openstack-meeting-alt20:13
*** dklyle has quit IRC20:14
*** dklyle has joined #openstack-meeting-alt20:18
*** irclogbot_1 has quit IRC20:25
*** irclogbot_1 has joined #openstack-meeting-alt20:28
*** e0ne has joined #openstack-meeting-alt20:28
*** jgrosso has quit IRC20:30
*** dave-mccowan has quit IRC20:39
*** e0ne has quit IRC20:41
*** dave-mccowan has joined #openstack-meeting-alt20:45
*** igordc has quit IRC20:49
*** igordc has joined #openstack-meeting-alt20:54
*** priteau has quit IRC21:12
*** irclogbot_1 has quit IRC21:26
*** irclogbot_1 has joined #openstack-meeting-alt21:29
*** raildo has quit IRC21:48
*** rfolco has quit IRC22:04
*** jtomasek has quit IRC22:05
*** vishalmanchanda has quit IRC22:05
*** igordc has quit IRC22:36
*** igordc has joined #openstack-meeting-alt22:40
*** rcernin has joined #openstack-meeting-alt23:04
*** carlos_silva has quit IRC23:08
*** hongbin has quit IRC23:19
*** jamesmcarthur has quit IRC23:51

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