Monday, 2018-08-13

*** slaweq has joined #openstack-meeting-alt01:11
*** slaweq has quit IRC01:16
*** tetsuro has joined #openstack-meeting-alt01:49
*** hongbin has joined #openstack-meeting-alt02:19
*** efried1 has joined #openstack-meeting-alt02:26
*** efried has quit IRC02:28
*** efried1 is now known as efried02:28
*** slaweq has joined #openstack-meeting-alt03:11
*** cloudrancher has quit IRC03:11
*** cloudrancher has joined #openstack-meeting-alt03:11
*** slaweq has quit IRC03:15
*** tetsuro has quit IRC03:26
*** redrobot has quit IRC03:55
*** dklyle has joined #openstack-meeting-alt04:23
*** adrian_otto has joined #openstack-meeting-alt04:26
*** dave-mccowan has quit IRC04:28
*** adrian_otto has quit IRC04:38
*** dklyle has quit IRC04:38
*** rcernin has quit IRC04:54
*** rcernin has joined #openstack-meeting-alt04:54
*** browny has joined #openstack-meeting-alt05:06
*** hongbin has quit IRC05:20
*** kopecmartin has joined #openstack-meeting-alt05:47
*** janki has joined #openstack-meeting-alt05:59
*** dpawlik has joined #openstack-meeting-alt06:00
*** ircuser-1 has joined #openstack-meeting-alt06:02
*** dpawlik has quit IRC06:05
*** slaweq has joined #openstack-meeting-alt06:11
*** dpawlik has joined #openstack-meeting-alt06:12
*** slaweq has quit IRC06:15
*** alexchadin has joined #openstack-meeting-alt06:33
*** slaweq has joined #openstack-meeting-alt06:37
*** rcernin has quit IRC07:03
*** apetrich has joined #openstack-meeting-alt07:04
*** arne_wiebalck has joined #openstack-meeting-alt07:14
*** alexchadin has quit IRC07:31
*** alexchadin has joined #openstack-meeting-alt07:35
*** ccamacho has joined #openstack-meeting-alt07:40
*** slaweq_ has joined #openstack-meeting-alt07:57
*** slaweq has quit IRC07:59
*** e0ne has joined #openstack-meeting-alt08:20
*** tssurya has joined #openstack-meeting-alt08:34
*** derekh has joined #openstack-meeting-alt08:36
*** alexchadin has quit IRC08:41
*** alexchadin has joined #openstack-meeting-alt08:43
*** giblet_off is now known as gibi08:55
*** GeraldK has joined #openstack-meeting-alt09:00
*** slaweq_ is now known as slaweq09:05
*** alexchadin has quit IRC09:12
*** liuyulong has joined #openstack-meeting-alt09:18
*** ccamacho has quit IRC09:21
*** alexchadin has joined #openstack-meeting-alt09:33
*** ccamacho has joined #openstack-meeting-alt09:39
*** apetrich has quit IRC09:47
*** GeraldK has quit IRC09:51
*** panda is now known as panda|ruck10:15
*** ccamacho has quit IRC10:31
*** ccamacho has joined #openstack-meeting-alt10:32
*** numans has joined #openstack-meeting-alt10:41
*** gouthamr has quit IRC10:44
*** alexchadin has quit IRC10:53
*** sambetts_ is now known as sambetts11:00
*** alexchadin has joined #openstack-meeting-alt11:03
*** sambetts is now known as sambetts|afk11:04
*** slaweq_ has joined #openstack-meeting-alt11:06
*** slaweq has quit IRC11:06
*** alexchadin has quit IRC11:17
*** alexchadin has joined #openstack-meeting-alt11:20
*** slagle has joined #openstack-meeting-alt11:22
*** panda|ruck is now known as panda|ruck|lunch11:23
*** alexchadin has quit IRC11:36
*** alexchadin has joined #openstack-meeting-alt11:38
*** erlon has joined #openstack-meeting-alt11:39
*** erlon has quit IRC11:44
*** sambetts|afk is now known as sambetts11:45
*** alexchadin has quit IRC11:53
*** raildo has joined #openstack-meeting-alt11:59
*** panda|ruck|lunch is now known as panda|ruck12:02
*** markstur has joined #openstack-meeting-alt12:12
*** markstur has quit IRC12:13
*** liuyulong has quit IRC12:14
*** erlon has joined #openstack-meeting-alt12:27
*** jcoufal has joined #openstack-meeting-alt12:30
*** apetrich has joined #openstack-meeting-alt12:31
*** markstur has joined #openstack-meeting-alt12:34
*** markstur has quit IRC12:38
*** jcoufal has quit IRC12:41
*** jcoufal has joined #openstack-meeting-alt12:42
*** redrobot has joined #openstack-meeting-alt12:51
*** dustins has joined #openstack-meeting-alt12:53
*** jroll has quit IRC12:59
*** jroll has joined #openstack-meeting-alt13:00
*** dtrainor has joined #openstack-meeting-alt13:01
*** markstur has joined #openstack-meeting-alt13:01
*** cloudrancher has quit IRC13:03
*** cloudrancher has joined #openstack-meeting-alt13:04
*** alexchadin has joined #openstack-meeting-alt13:12
*** SteelyDan is now known as dansmith13:25
*** jaypipes has joined #openstack-meeting-alt13:26
*** alex_xu has joined #openstack-meeting-alt13:47
*** takashin has joined #openstack-meeting-alt13:51
*** cdent has joined #openstack-meeting-alt13:51
*** pbourke has quit IRC13:52
*** pbourke has joined #openstack-meeting-alt13:53
*** tetsuro__ has joined #openstack-meeting-alt13:59
* cdent tries to wake up14:00
efried#startmeeting nova_scheduler14:00
openstackMeeting started Mon Aug 13 14:00:18 2018 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
takashino/14:00
* efried waves smelling salts at cdent14:00
alex_xuo/14:00
tssuryao/14:00
tetsuro__o/14:00
efried#link Agenda https://wiki.openstack.org/wiki/Meetings/NovaScheduler#Agenda_for_next_meeting14:01
efriedjaypipes said he wouldn't make it today. So I gave him all the reviews.14:01
edleafe\o14:01
efried#topic last meeting14:02
efried#link last minutes: http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-08-06-14.00.html14:02
efriedAny old business to discuss that's not elsewhere on the agenda?14:02
*** openstack changes topic to "last meeting (Meeting topic: nova_scheduler)"14:02
gibio/14:02
*** tetsuro__ has quit IRC14:02
*** tetsuro has joined #openstack-meeting-alt14:03
efried#topic specs and review14:03
efried#link latest pupdate: http://lists.openstack.org/pipermail/openstack-dev/2018-August/132852.html14:03
efriedNobody picked this up last week. I feel the loss... maybe even enough to pick it up next week. We shall see.14:03
*** openstack changes topic to "specs and review (Meeting topic: nova_scheduler)"14:03
efried#link reshaper series: https://review.openstack.org/#/q/topic:bp/reshape-provider-tree+status:open14:05
efriedStein is open, so let's get this merged ASAP.14:05
efriedI believe jaypipes and gibi are on the hook here. Other eyeballs from those who were involved in the planning stages and haven't looked lately (dansmith mriedem bauzas edleafe) would be appreciated.14:05
efried#link Gigantor SQL split and debug logging: https://review.openstack.org/#/c/590041/14:06
efriedThis has undergone rudimentary scale/perf testing and has so far been shown not to be significantly slower than the original (yay)14:06
efriedNeeds scrutiny wrt content and abundance of log messages, please review.14:06
jaypipeshey, I'm here now...14:07
cdentwhen I left on friday review had identified some edge cases. did those bugs get additional test coverage14:07
jaypipesthought I'd have to miss the meeting, but was able to catch a bit.14:07
alex_xuefried: where can see the perf testing result?14:08
efriedcdent: There was a logic bug with multiple forbidden traits: the new algo was using ^ instead of -. A patch to expose the bug was merged and the code has been fixed.14:08
efried#link Test case for multiple forbidden traits https://review.openstack.org/#/c/591070/14:08
efriedalex_xu: There are numbers in some of the patches, stand by...14:09
cdentI wonder if we can programmatically figure out (perhaps just with coverage?) that we're getting the corners14:09
jaypipesalex_xu: short version: not doing nested means performance is much better.14:10
efriedalex_xu: https://review.openstack.org/#/c/590041/ see around PS414:10
*** bnemec-pto is now known as bnemec14:10
alex_xujaypipes: ah...right14:10
efriedalex_xu: Oh, jaypipes is talking about something different. Stand by...14:10
alex_xuefried: thanks, checking14:10
efriedalex_xu: https://review.openstack.org/#/c/590388/ around PS3 commentary there's an eavesdrop link.14:11
efriedalex_xu: There's a topic in open discussion to talk more about scale/perf in general.14:11
alex_xuefried: got it, thanks14:12
efriedThose two patches ^ ought to be backported to rocky once we're past the (bizarre and arbitrary) RC/release phase.14:12
efriedPlanning/Doing support in nova/report client for:14:13
efried#link consumer generation handling (gibi): https://review.openstack.org/#/c/583667/14:13
efriedStill WIP (code almost done, gibi is splitting into multiple patches)14:13
gibithere will be questionable api behaviors there14:14
efriedgibi: Nova API or placement API?14:14
gibiwhen the report client gets consumer conflict it retries but at some point it can run out of retry and needs to fail14:14
gibiefried: nova API14:14
gibiI will write up a list of question in a mail14:14
efriedyes, I imagine that will look like the non-retry failure would have looked before, right?14:14
efriedthat's what I would expect anyway14:15
gibiefried: we don't handle today when a PUT allocations (that used to delete allocation) fails14:15
gibiefried: and many other failure cases14:15
efried"handle" in what sense? You mean today we let the exception bubble up through the resource tracker, where it gets ignored?14:16
gibiefried: there are plenty of TODO in the above patch in the func test detailing them14:16
gibiefried: today we are silent in most cases14:16
efriedyup14:16
gibiefried: or go to error in some migration cases like revert_resize14:16
gibiefried: but revert_resize fails then the the end user might want to retry14:16
*** markstur has quit IRC14:16
gibianyhow plenty of edges I have to list and ask for oppinion14:17
efriedThis is great to have you digging and auditing and finding these holes. Pepper the code with TODOs. Call out behavioral changes in commit messages. Do the ML thing.14:18
gibiefried: will do14:18
efriedThanks gibi14:18
cdentyeah, even if we don't fix everything now, todo-ing what you notice is +many14:18
efriednested and shared providers for initial allocations14:19
efriednested and shared providers when modifying migration (and other?) allocations14:19
efriedgibi, has your work above expanded to cover any of ^^ this stuff?14:19
gibiefried: unfortunately no14:19
efriedokay.14:19
gibitetsuro started with nested here https://review.openstack.org/#/c/58567214:20
gibithere are two set of functional test cases above it14:20
gibione for initial and one for move14:20
efriedoh, nice.14:20
tetsurowill rebase it once gibi's one is split.14:20
efriedYeah, I have those on my radar but haven't looked at them recently. But let me add them to the agenda so I don't forget (again) next week...14:21
gibiyeah, I have to move forward as lot of good work depend on the 1.28 patch now14:21
efried#link nested and shared providers for initial & migration (and other?) allocations, series starting at: https://review.openstack.org/#/c/58567214:22
efriedOkay, any other reviews to discuss? Or specs?14:23
*** markstur has joined #openstack-meeting-alt14:23
*** janki has quit IRC14:24
efriedOh, there's a spec I didn't put on the agenda but I'd like to mention.14:24
efriedDisclaimer: I haven't read it yet.14:24
efried#link Placement model for PCI devices https://review.openstack.org/#/c/591037/14:24
*** janki has joined #openstack-meeting-alt14:24
cdentI glanced at that, it's basically a dup of your powervm spec14:25
efriedThis is a next step on the road to the "generic device management" via placement.14:25
efriedokay, that was essentially what kosamara said he was going to do.14:25
efriedFor reference, cdent is referring to:14:26
efried#link nova-powervm spec for generic device passthrough via placement: https://review.openstack.org/#/c/579359/14:26
efriedAnything else for specs/reviews?14:27
efried#topic bugs14:27
efried#link placement bugs: https://bugs.launchpad.net/nova/+bugs?field.tag=placement&orderby=-id14:27
*** openstack changes topic to "bugs (Meeting topic: nova_scheduler)"14:27
*** markstur has quit IRC14:27
cdentI added a new one over the weekend14:28
cdenthttps://bugs.launchpad.net/nova/+bug/178670314:28
openstackLaunchpad bug 1786703 in OpenStack Compute (nova) "Placement duplicate aggregate uuid handling during concurrent aggregate create insufficiently robust" [Medium,New]14:28
cdentoops14:28
cdent#link https://bugs.launchpad.net/nova/+bug/178670314:28
cdentnot sure if it an postgres problem, an oslo_db problem or a placement problem14:28
efriedneat14:29
*** markstur has joined #openstack-meeting-alt14:29
cdentthat was my reaction too14:29
*** alexchadin has quit IRC14:30
efriedI can almost see that happening IRL.14:30
cdentin a kinda "oh lookie, I made it broked!!!"14:30
*** alexchadin has joined #openstack-meeting-alt14:30
efriedOkay, any other bug topics?14:30
jaypipesefried: ack, thx for the prod on that GDM-ish spec.14:31
jaypipeswill review later.14:31
efried#topic opens14:31
efriedWhere do we want to be on that extraction thing?14:31
efriedcdent, assume this is your microphone14:31
*** openstack changes topic to "opens (Meeting topic: nova_scheduler)"14:31
cdentit's just a reminder/open question. stein is open but we have a fair chunk of code pending14:32
cdentso we can't go _now_ but do we want to go _soon_?14:32
cdentor are we going to delay even more?14:32
efriedcdent: There's an etherpad somewhere that lists the pending steps before we can pull the trigger, right?14:33
cdentthere are several etherpads that had that kind of stuff on them, but I'm not sure we made such a list?14:33
cdentor maybe you're remembering something I've forgotten14:34
efriedumm14:34
*** markstur has quit IRC14:34
cdentI'm not very good at remember things on etherpads because they are impossible to find14:34
efried#action cdent to find/make an etherpad (or other doc) with a burndown of remaining work items for extraction14:34
efried?14:34
efriedThis will be useful when we get to that agenda item in denver.14:35
cdentso, actually, no. I don't want this to be solely on me, essentially because there are many factors that I don't care about. If it was just on me we would have done it long ago.14:35
cdentbut14:35
*** markstur has joined #openstack-meeting-alt14:35
*** markstur has quit IRC14:35
efried#undo14:35
efried:)14:35
openstackRemoving item from minutes: #action cdent to find/make an etherpad (or other doc) with a burndown of remaining work items for extraction14:35
cdentI can start an etherpad of some kind that reflects the several times I've written all this up in a blog post or on a ptg planning etherpad14:36
efriedany single point of reference would be great.14:36
cdentbut the root of my question/agenda item is more a query about our combined fortitude and commitment to doing it14:37
efriedI for one am very much supportive of extraction, but definitely don't have my head wrapped around what else needs to be done around it.14:37
cdenthave you (re)read my several blog posts and emails on the topic?14:37
cdentwould assembling those links somewhere be a useful starting point?14:38
jaypipescdent: didn't you have a blog post on extraction (a followup post to your original one)?14:38
efriedI read them when they come out (assuming I'm linked on them) but don't go back and reread them later unless prompted.14:38
cdentjaypipes: yes14:38
cdent#link placement extraction 2: https://anticdent.org/placement-extraction-2.html14:38
jaypipesdanke14:39
cdentseveral of the things listed there are done14:39
efriedOne one hand, yes, such a collection of links would be useful; but on the other, I don't want to daunted by a massive volume of reading if much of it is obsolete (already completed).14:39
cdentbut again: the technical barriers are not my major concern at this point14:39
cdentin fact not even really my minor concern14:39
*** vgreen has joined #openstack-meeting-alt14:40
jaypipescdent: the intestinal fortitude of the nova core team to allow the complete segregation of the placement service from nova itself is your primary question/concern.14:40
cdentYes, jaypipes. At some point we're going to fork, and I'd like that to be a comfortable thing to do, if at all possible.14:40
jaypipesack14:41
efriedWell, knowing which work items are mandatory and which are optional; knowing if any need to be done in a particular order; maybe even having some sense of how big each item is; getting names next to some of them...14:41
efriedAll of that would be useful to break down barriers14:41
jaypipescdent: I think one thing that might make that process easier is having a placementclient library that can be easily imported into nova and replace much of the code currently in scheduler/client/report.py14:42
cdentefried: are you asking me to do something, or are you just listing things that may need to be done?14:42
jaypipescdent: I think efried is pining for the list, that's all :)14:42
cdentjaypipes: I don't see what the report client has to do with placement the api service being in its own repo?14:42
efriedcdent: I'm describing a thing (burndown etherpad or similar) that I think would be useful. I think you're the best person to compose it, at least initially, at least in skeletal form.14:43
cdentk14:43
jaypipescdent: because having a separate client library indicates the maturity of the API service for which the client library provides an interface.14:43
efriedI agree this has nothing to do with a client library, which is a topic all of its own, and a contentious one. The mordred faction would likely argue that we shouldn't have a placementclient lib at all, ever.14:44
mordredaroo?14:44
mordredyup14:44
mordredI would strongly argue that14:44
efriedThe report client does stuff that's nova-specific. The vast majority of it wouldn't be appropriate for a generic lib.14:44
cdentthe api service is as mature (or at least temporarily static) as we declare it to be. I agree that if we are going to do this move we should freeze the placement api14:44
jaypipescdent: put another way: the fact that the reportclient is its own bastardized client library to placement is an indicator to nova core contributors that the placement API service is not yet fully distinguishable from nova itself.14:44
efriedoh, I disagree with this ^14:45
jaypipesmordred: oh, fello.14:45
jaypipeshello...14:45
mordredor fello14:45
cdentjaypipes: I agree with efried disagreeing14:45
cdent:)14:45
mordredbut yeah - we should be deleting python-*client libraries, not making new ones14:45
jaypipesmordred: are openstacksdk pieces separately importable into a service?14:46
mordredyes14:46
jaypipeswithout bringing in the entire collection of other clients?14:46
mordredsdk does not touch other clients14:47
mordredas should nothing14:47
mordredsince they make everything harder14:47
cdentI suspect that "placementclient" lib ought to be more to do with things like ProviderTree than with api calls. But I still think that "client stuff" is orthogonal from maturity and repo separation14:47
jaypipesok, so since there is a placement openstacksdk client plugin, we should be able to import that without having to import any other client plugin? is that correct?14:47
jaypipesmordred: ^14:48
mordredwell, there is no such thing as openstacksdk plugins - but placement is more than welcome to put as much placement support in sdk as desired, and we can make some people core on that area if needed14:48
efriedis that a wrapper around a ksa adapter to the placement API?14:48
mordredand I'd be more than happy to work with y'all on figuring out the right/easiest way to make the progress you need to make14:49
jaypipesmordred: right now, we have a straight requests+ksa raw HTTP client embedded in the scheduler/client/report.py module. what I'm looking for is the ability to do: from openstacksdk import placement as place_client (or something like that)14:49
mordredyup. that would basically just work today14:49
efriedjaypipes: And then place_client.what()?14:49
jaypipesefried: place_client.get_providers(), blah blah...14:50
efried.get() .put() .post() .delete() ?14:50
mordredconn = openstack.connect() ; conn.placement.get('/some/placement/path')14:50
*** ccamacho has quit IRC14:50
mordredno patches needed14:50
jaypipesmordred: cool. maybe I can sit down with you in Denver and learn more about that.14:50
efriedbingo, there's the disconnect (so to speak). jaypipes is asking for .get_providers() etc. - basically method wrappers around particular URIs.14:50
mordredBUT - if you want to add more smarter things, we can add those methods to the proxy/adapter object that gets attached to conn as placement14:50
mordredjaypipes: would LOVE to do that14:50
mordredefried: yup - we can add one of those really easily14:51
efriedOkay.14:51
efriedThat's neat.14:51
efriedBut14:51
mordredand then I've been meaning to circle back around with efried about getting nova to use sdk instead of python-*client or raw ksa anyway14:51
efriedStill orthogonal to the where the placement API itself sprouts from.14:51
mordredso - yay denver!14:51
efriedmordred: Would you be able to hang out in the nova room for that topic if we had it on the agenda/14:51
efried?14:51
mordredefried: absolutely14:52
cdentwe running out of time14:52
* efried adds to etherpad14:52
efriedYeah, so back to placement API extraction itself. cdent, do you "volunteer" to take an action to create a master burndown list of action items toward extraction?14:53
jaypipesefried: to repeat... cdent's concern is not actually with that list of things.14:53
jaypipesefried: his concern is a metaphysical one.14:53
jaypipesefried: and no amount of list-making will answer those concerns.14:54
efried#link Stein PTG etherpad https://etherpad.openstack.org/p/nova-ptg-stein14:54
cdentvolunteer is a bit strong, but yes I will create that list, and yes, jay is right that I'm concerned about metaphysics, but we presumably need the list anyway14:54
efriedmordred: ^ very bottom14:54
efriedcdent: Right, because we don't need to waste time with the first wave of objections ("well, what about X, what about Y, ...")14:54
efriedbecause we already have X and Y listed with a plan to address.14:55
efriedokay, moving on, 5 minutes left.14:55
efriedPlacement scale/perf testing in the gate (cdent)14:55
efried#link github repo to set up a bunch of providers: https://github.com/cdent/placeload14:55
efried#link A start on adding some kind of perf reporting to the gate: https://review.openstack.org/#/c/591367/14:55
efriedThis is to follow on with earlier mentions of cdent having experimented with some scale testing14:56
jaypipesand I was trying (terribly, apparently) to explain that one source of tension that nova core contributors have w.r.t. a placement extraction is the continued belief that nova == placement in so much as there is as yet no real consumer of placement outside of nova. it's a chicken and egg problem in a lot of ways, but the mess of the reportclient's calling into the placement service (and the very nova-centrism of that reportclient) makes14:56
jaypipesit *seem* like nova == placement for all intents and purposes.14:56
efriedHe identified some serious bottlenecks, which have since been fixed.14:56
cdentneutron and blazar have significant bits of code in-progress14:56
efriedBut it would be neat if this kind of testing could be more regular14:56
cdentso yeah, perf scale stuff14:56
cdentI've started:14:56
cdent#link perf info in the gate: https://review.openstack.org/#/c/591367/14:56
*** ccamacho has joined #openstack-meeting-alt14:56
cdentdoesn't work yet14:56
cdentbut will allow the nova-next job to report a simple timing info each run (adding only seconds to the job run time)14:57
jaypipesnice, good work cdent.14:57
cdentI put it on nova-next because that one uses the optional placement db14:57
efriedjaypipes: Even if nova == placement for all intents and purposes, that's *no* reason to avoid extracting it. We have a demonstrated imbalance of codebase to reviewers/developers. Extracting pieces into their own components where feasible is a good way to combat that. And placement is a significant piece with some pretty clear borders that's ripe for such a move.14:59
cdentwith time it could become a bit more exciting, but at the moment I'm trying to make it as dumb as possible14:59
efriedAs I mentioned earlier, that's way better than what we had before, which is nothing.15:00
jaypipesefried: again, I'm trying to tell you what the perceptions are.15:00
efriedOkay, we're out of time.15:00
efriedjaypipes: Would love to continue the discussion in -placement15:00
*** kopecmartin has quit IRC15:00
efried#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Mon Aug 13 15:00:27 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-08-13-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-08-13-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-08-13-14.00.log.html15:00
*** takashin has left #openstack-meeting-alt15:01
*** hongbin has joined #openstack-meeting-alt15:01
*** alexchadin has quit IRC15:04
*** tetsuro has quit IRC15:05
*** kopecmartin has joined #openstack-meeting-alt15:15
*** janki has quit IRC15:19
*** gouthamr has joined #openstack-meeting-alt15:54
*** e0ne has quit IRC16:03
*** markstur has joined #openstack-meeting-alt16:03
*** dtrainor_ has joined #openstack-meeting-alt16:08
*** markstur has quit IRC16:08
*** dtrainor has quit IRC16:09
*** dklyle has joined #openstack-meeting-alt16:10
*** slaweq_ has quit IRC16:15
*** kopecmartin has quit IRC16:20
*** markstur has joined #openstack-meeting-alt16:21
*** gyee has joined #openstack-meeting-alt16:23
*** sambetts is now known as sambetts|afk16:26
*** markstur has quit IRC16:26
*** namnh has joined #openstack-meeting-alt16:26
*** e0ne has joined #openstack-meeting-alt16:28
*** ccamacho has quit IRC16:31
*** slaweq_ has joined #openstack-meeting-alt16:31
*** markstur has joined #openstack-meeting-alt16:33
*** slaweq_ has quit IRC16:36
*** markstur has quit IRC16:37
*** markstur has joined #openstack-meeting-alt16:45
*** markstur has quit IRC16:50
*** markstur has joined #openstack-meeting-alt16:51
*** slaweq_ has joined #openstack-meeting-alt16:52
*** markstur has quit IRC16:55
*** markstur has joined #openstack-meeting-alt16:55
*** slaweq_ has quit IRC16:57
*** derekh has quit IRC17:01
*** e0ne has quit IRC17:01
*** namnh has quit IRC17:09
*** slaweq_ has joined #openstack-meeting-alt17:11
*** yamahata has quit IRC17:11
*** namnh has joined #openstack-meeting-alt17:14
*** slaweq_ has quit IRC17:15
*** namnh has quit IRC17:22
*** slaweq_ has joined #openstack-meeting-alt17:32
*** tssurya has quit IRC17:36
*** slaweq_ has quit IRC17:37
*** ianychoi_ has joined #openstack-meeting-alt17:38
*** isq has joined #openstack-meeting-alt17:40
*** isq_ has quit IRC17:40
*** ianychoi has quit IRC17:41
*** stephenfin_ has quit IRC17:42
*** stephenfin has joined #openstack-meeting-alt17:45
*** yamahata has joined #openstack-meeting-alt17:47
*** markstur has quit IRC17:59
*** markstur has joined #openstack-meeting-alt18:05
*** markstur has quit IRC18:10
*** slaweq_ has joined #openstack-meeting-alt18:11
*** markstur has joined #openstack-meeting-alt18:11
*** slaweq_ has quit IRC18:15
*** markstur has quit IRC18:17
*** cloudrancher has quit IRC18:20
*** cloudrancher has joined #openstack-meeting-alt18:20
*** e0ne has joined #openstack-meeting-alt18:30
*** slaweq_ has joined #openstack-meeting-alt18:32
*** slaweq_ has quit IRC18:37
*** namnh has joined #openstack-meeting-alt18:37
*** tssurya has joined #openstack-meeting-alt18:39
*** namnh has quit IRC18:42
*** slaweq_ has joined #openstack-meeting-alt18:53
*** slaweq_ has quit IRC18:57
*** raildo_ has joined #openstack-meeting-alt18:59
*** raildo has quit IRC19:00
*** rmascena__ has joined #openstack-meeting-alt19:06
*** rmascena__ is now known as raildo19:06
*** raildo_ has quit IRC19:08
*** ameade_ has joined #openstack-meeting-alt19:18
*** mgagne_ has joined #openstack-meeting-alt19:24
*** knikolla has quit IRC19:25
*** ameade has quit IRC19:25
*** serverascode_ has quit IRC19:25
*** jgrassler has quit IRC19:25
*** mgagne has quit IRC19:25
*** ameade_ is now known as ameade19:25
*** purplerbot has quit IRC19:27
*** amotoki has quit IRC19:27
*** knikolla has joined #openstack-meeting-alt19:28
*** dustins has quit IRC19:29
*** amotoki has joined #openstack-meeting-alt19:30
*** raildo has quit IRC19:30
*** raildo has joined #openstack-meeting-alt19:31
*** slaweq_ has joined #openstack-meeting-alt19:32
*** slaweq_ has quit IRC19:36
*** apetrich has quit IRC19:41
*** e0ne has quit IRC19:52
*** efried has quit IRC19:58
*** tssurya has quit IRC20:07
*** slaweq_ has joined #openstack-meeting-alt20:11
*** cloudrancher has quit IRC20:12
*** cloudrancher has joined #openstack-meeting-alt20:13
*** efried has joined #openstack-meeting-alt20:13
*** vgreen has quit IRC20:15
*** slaweq_ has quit IRC20:16
*** e0ne has joined #openstack-meeting-alt20:18
*** purplerbot has joined #openstack-meeting-alt20:25
*** raildo has quit IRC20:28
*** slaweq_ has joined #openstack-meeting-alt20:32
*** e0ne has quit IRC20:33
*** apetrich has joined #openstack-meeting-alt20:34
*** jcoufal has quit IRC20:34
*** slaweq_ has quit IRC20:36
*** erlon has quit IRC20:45
*** cloudrancher has quit IRC20:46
*** cloudrancher has joined #openstack-meeting-alt20:49
*** slaweq_ has joined #openstack-meeting-alt20:53
*** dtrainor_ has quit IRC20:54
*** dtrainor has joined #openstack-meeting-alt20:55
*** slaweq_ has quit IRC20:57
*** apetrich has quit IRC20:59
*** cdent has left #openstack-meeting-alt21:05
*** erlon has joined #openstack-meeting-alt21:05
*** slaweq_ has joined #openstack-meeting-alt21:11
*** slaweq_ has quit IRC21:16
*** haleyb is now known as haleyb|away21:20
*** cloudrancher has quit IRC21:25
*** cloudrancher has joined #openstack-meeting-alt21:25
*** slagle has quit IRC21:26
*** slaweq_ has joined #openstack-meeting-alt21:33
*** slaweq_ has quit IRC21:43
*** e0ne has joined #openstack-meeting-alt21:50
*** hongbin has quit IRC21:54
*** e0ne has quit IRC21:56
*** slaweq_ has joined #openstack-meeting-alt22:00
*** erlon has quit IRC22:00
*** rcernin has joined #openstack-meeting-alt22:01
*** slaweq_ has quit IRC22:04
*** slaweq_ has joined #openstack-meeting-alt22:11
*** slaweq_ has quit IRC22:16
*** namnh has joined #openstack-meeting-alt22:38
*** namnh has quit IRC22:44
*** slaweq_ has joined #openstack-meeting-alt22:53
*** slaweq_ has quit IRC22:58
*** slaweq_ has joined #openstack-meeting-alt23:11
*** slaweq_ has quit IRC23:15
*** tpsilva has quit IRC23:28
*** cloudrancher has quit IRC23:33
*** cloudrancher has joined #openstack-meeting-alt23:35
*** namnh has joined #openstack-meeting-alt23:51
*** slaweq_ has joined #openstack-meeting-alt23:53
*** slaweq_ has quit IRC23:57

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