Wednesday, 2016-05-18

*** vilobhmm11 has joined #openstack-meeting-cp00:00
*** beekhof has quit IRC00:14
*** ninag has joined #openstack-meeting-cp00:14
*** ninag has quit IRC00:21
*** piet has quit IRC00:27
*** piet has joined #openstack-meeting-cp00:32
*** aliadil has joined #openstack-meeting-cp00:43
*** piet has quit IRC00:55
*** aliadil has quit IRC01:01
*** exedore6 has joined #openstack-meeting-cp01:17
*** exedore6 has quit IRC01:29
*** exedore6 has joined #openstack-meeting-cp01:29
*** exedore6 has left #openstack-meeting-cp01:34
*** ninag has joined #openstack-meeting-cp02:00
*** ninag has quit IRC02:05
*** sdake has quit IRC02:06
*** tyr_ has joined #openstack-meeting-cp02:07
*** tyr_ has quit IRC02:11
*** sdake has joined #openstack-meeting-cp02:12
*** sdake has quit IRC02:22
*** sdake has joined #openstack-meeting-cp03:09
*** sdake_ has joined #openstack-meeting-cp03:37
*** sdake has quit IRC03:40
*** piet has joined #openstack-meeting-cp03:53
*** tyr_ has joined #openstack-meeting-cp03:56
*** sdake_ has quit IRC03:58
*** tyr_ has quit IRC04:00
*** sdake has joined #openstack-meeting-cp04:09
*** samueldmq has quit IRC04:43
*** piet has quit IRC04:44
*** samueldmq has joined #openstack-meeting-cp04:46
*** flwang1 has quit IRC04:58
*** piet has joined #openstack-meeting-cp04:59
*** piet has quit IRC05:12
*** ericksonsantos has quit IRC05:12
*** ericksonsantos has joined #openstack-meeting-cp05:13
*** sdake has quit IRC05:26
*** amrith is now known as _amrith_05:34
*** tyr_ has joined #openstack-meeting-cp05:44
*** tyr_ has quit IRC05:48
*** david-lyle has quit IRC06:05
*** _amrith_ is now known as amrith06:09
*** beekhof has joined #openstack-meeting-cp06:50
*** belmoreira has joined #openstack-meeting-cp07:02
*** vilobhmm11 has quit IRC07:08
*** tyr_ has joined #openstack-meeting-cp07:31
*** tyr_ has quit IRC07:35
*** david-lyle has joined #openstack-meeting-cp07:57
*** soren_ has joined #openstack-meeting-cp08:43
*** lbragstad_ has joined #openstack-meeting-cp08:44
*** breton_ has joined #openstack-meeting-cp08:45
*** sigmavirus24_awa has quit IRC08:45
*** cFouts has quit IRC08:45
*** soren has quit IRC08:45
*** homerp has quit IRC08:45
*** ameade has quit IRC08:45
*** tpeoples has quit IRC08:45
*** melwitt has quit IRC08:45
*** odyssey4me has quit IRC08:45
*** breton has quit IRC08:45
*** lbragstad has quit IRC08:45
*** melwitt has joined #openstack-meeting-cp08:45
*** melwitt is now known as Guest3726408:46
*** soren_ is now known as soren08:46
*** odyssey4me has joined #openstack-meeting-cp08:46
*** sigmavirus24_awa has joined #openstack-meeting-cp08:48
*** ildikov has quit IRC08:48
*** homerp has joined #openstack-meeting-cp08:48
*** gnarld_ has joined #openstack-meeting-cp08:49
*** tpeoples has joined #openstack-meeting-cp08:52
*** ildikov has joined #openstack-meeting-cp08:55
*** ameade has joined #openstack-meeting-cp08:55
*** tyr_ has joined #openstack-meeting-cp09:20
*** tyr_ has quit IRC09:24
*** aimeeu has quit IRC09:33
*** aimeeu has joined #openstack-meeting-cp09:36
*** markvoelker has joined #openstack-meeting-cp09:56
*** sdague has joined #openstack-meeting-cp10:01
*** markvoelker has quit IRC10:02
*** tyr_ has joined #openstack-meeting-cp11:08
*** tyr_ has quit IRC11:13
*** coolsvap has joined #openstack-meeting-cp11:16
*** ninag has joined #openstack-meeting-cp11:51
*** ninag has quit IRC11:57
*** promethe1nfire has joined #openstack-meeting-cp11:59
dims_#startmeeting requirements12:00
openstackMeeting started Wed May 18 12:00:27 2016 UTC and is due to finish in 60 minutes.  The chair is dims_. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: requirements)"12:00
openstackThe meeting name has been set to 'requirements'12:00
ttxo/12:00
dims_hey ttx12:00
promethe1nfirehi12:01
tonybo/12:01
coolsvapo?12:01
coolsvapo/12:01
*** beisner has joined #openstack-meeting-cp12:01
*** dirk has joined #openstack-meeting-cp12:01
dirkHey12:02
promethe1nfiretonyb: what time is it for you?12:02
amrith./12:02
dims_tonyb : i don't see you on our new channel. #openstack-requirements12:02
amrithsorry, am a bit late12:02
tonyb2200ish12:02
tonybdims_: I did not12:02
* tonyb adds it to his IRC config12:02
ttxohhh new channel. shiny12:02
dhellmanno/12:02
*** number80 has joined #openstack-meeting-cp12:02
*** GheRivero has joined #openstack-meeting-cp12:02
GheRiveroo/12:03
dims_welcome everyone to the new team!12:03
dims_#topic : is this day/time ok for you?12:03
*** openstack changes topic to ": is this day/time ok for you? (Meeting topic: requirements)"12:03
dims_i know we lost lifeless as it's midnight12:04
dims_tonyb : would you like us to move one hour earlier?12:04
*** mugsie has joined #openstack-meeting-cp12:04
promethe1nfireit's 7AM here12:04
ttxday/time perfect for me12:04
tonybdims_: that would be nice but only if it isn't terrible for the people just starting for the day12:04
dims_tonyb : ok, will keep that in mind12:05
dims_promethe1nfire : ack.12:05
ttxI think one hour earlier would make it difficult for promethe1nfire, and one hour later difficult for tonyb12:05
dims_ttx : right, let's leave it at this time12:05
promethe1nfireI think we have a people from each region12:05
tonybyeah12:05
promethe1nfireya12:05
mugsiedims_: got a ping to join here?12:05
tonybI think leave it as it is while we bootstrap and then reevaluate in a couple of months12:06
dims_#topic reviews with immediate attention12:06
GheRiveroIt's ok to me.. but not today. I'm out of the office now, but can do almost any hour. I'm a night person12:06
*** openstack changes topic to "reviews with immediate attention (Meeting topic: requirements)"12:06
dims_https://review.openstack.org/#/q/status:open+project:%255E.*requirements.*+branch:master,n,z12:06
dims_GheRivero : ack12:06
dims_tonyb : ack12:06
dims_mugsie : not sure if you were interested in the team meeting. hence the ping12:06
promethe1nfireif it was 6 hours earlier that'd be fine12:06
dims_Looks like we made excellent progress the last few days12:07
promethe1nfireI'm also a night person12:07
dims_with reviews12:07
dirkyeah12:07
dirkwe're down to less than one page12:07
dirkawesome!12:07
dims_the only hiccup we had was with python-kafka. we had to revert for monasca12:07
dims_#link https://review.openstack.org/#/c/316259/12:07
dims_Though they are not subject to requirements process12:08
GheRiveroIs there a gerrit topic for priority reviews?12:08
dims_their jobs seemed to use the versions in g-r/u-c12:08
dims_GheRivero : no, we don't have one yet12:08
dims_any questions on the kafka revert?12:09
* dims_ lets folks look at the comments in review12:09
dirkdims_: is there a general guideline for that? I mean the revert broke some other project right?12:10
dims_dirk : ideally we would say no to revert. since oslo.messaging had not yet started using code depending on the new version, it was technically feasible to revert back12:11
dhellmanndims_ : I don't think the test system differentiates between projects following requirements and not when it forces the use of the constraints file12:12
dhellmannis someone working on fixing monasca?12:12
*** sigmavirus24_awa is now known as sigmavirus2412:12
dims_dhellmann : Joe Keen and Roland Hochmuth (not sure what their IRC nicks are)12:13
tonybdhellmann: I think they're waiting for anumber of kafka issues to be closed before they do that work.12:13
* sigmavirus24 apologizes for being late12:13
dims_hey sigmavirus2412:13
dhellmanndims_, tonyb : ok, as long as it's not being ignored12:13
promethe1nfiresigmavirus24: you up early too :P12:14
tonybdhellmann: yup12:14
dims_dhellmann : when oslo.messaging folks are ready with newer kafka, monasca should not have a say, unless they are subject to the g-r process by then12:14
sigmavirus24promethe1nfire: that I am12:14
dims_So this monasca not being in g-r but wanting revert promoted me to post this email12:14
dims_#link http://markmail.org/message/kb6jlhiuhmxea45412:14
* dims_ lets folks click on the link12:15
*** apevec has joined #openstack-meeting-cp12:15
* tonyb had flagged that for reading tomorrow;P12:16
dhellmannin principle I agree, but if the way we run tests forces folks to use the updates even when they aren't syncing then we need to be aware of that12:16
* dirk clicked it12:16
* coolsvap saw that just before the meeting12:16
dhellmannbecause it doesn't sound like syncing requirements would have helped monasca here?12:16
promethe1nfirethat looks like what's been discussed12:16
dims_dhellmann : it would have given them a heads up when the g-r change merged12:17
dims_as the bot proposes a review in their project12:17
dims_coolsvap : y, giving background on what prompted that email12:17
dhellmanndims_ : that's true. it still would have broken their jobs, but at least there would have been some sort of notice of what changed12:17
dims_right, and they would have the right to ask for a immediate revert12:18
dhellmannsure12:18
coolsvapdims_, ack12:18
dhellmannit would be good to get them off of the fence, and either start participating in g-r or stop using the constraints in their jobs (if that's even possible)12:18
dims_yep, in general we need to push people more to understand requirements process better. another example - https://review.openstack.org/#/c/313835/12:19
tonybdhellmann: it isnt possible in a dsvm job12:19
dims_Steven Hardy was asking about instack-*12:19
dhellmanntonyb : that's what I was afraid of12:19
tonybdhellmann: we made it mandatory at some point12:19
dims_needing some packages that we were trying to remove12:19
dhellmanntonyb : it's really the only way to ensure it's going to work12:20
tonybdhellmann: Yeah.  I'm sure it seemed like a good idea at the time12:21
dims_#topic - sniff test matrix12:21
*** openstack changes topic to "- sniff test matrix (Meeting topic: requirements)"12:21
dims_we have a bunch of jobs in the requirements reviews themselves12:22
dirkdims_: I'm not sure I understand teh concerns in that review so far12:22
dims_dirk : instack-* is welcome to maintain any package versions they want they should not dictate what's in g-r12:22
dims_and i maintain a set of sniff tests - https://review.openstack.org/#/q/status:open+branch:master+topic:dims/test/constraints12:23
dims_dirk and i have been diligently checking failures in these tests before letting in the nightly proposed updates to u-c12:23
dirkdims_: right.. lets talk about that some other time12:23
dims_does anyone want another project added to my sniff test?12:24
dirksounds like monasca wants to be on that list :)12:24
dims_dirk : LOL, if they get into g-r/u-c/projects.txt then yes :)12:24
tonybdims_: keystone, glance, swift12:25
mugsiedims_: designate, if possible?12:25
tonybdims_: with what you have and those you'll be covering >55% of all the items in g-r12:25
dims_mugsie tonyb : if you can add the reviews like the ones i have then that would be great - they key is the topic "dims/test/constraints" as i have a cron job that maintains these reviews once they are created - https://gist.github.com/dims/094ac0e8d8bd8c4a096b6b391157aef512:26
dims_tonyb : right12:26
dims_#topic - release process updates that affect requirements12:27
*** openstack changes topic to "- release process updates that affect requirements (Meeting topic: requirements)"12:27
dims_dhellmann : any thoughts/plans here?12:27
* tonyb will review the gist and then add the required jobs ;P12:27
dirkdims_: painful projects are probably sahara, ceilometer, magnum12:27
dims_#action tonybwill review the gist and then add the required jobs12:27
dirkthey integrate a lot of dependencies and from my experience break often due to inter-project dependency issues12:27
dims_dirk : i tend to add one when i break them once :)12:27
tonybA releated topic is runing $projects unit tests in u-c changes12:28
dirkit seems ceilometer got broken so often that they opted out already ;)12:28
dims_dirk : i don't want to get started on telemetry team :)12:28
tonybIIRC there was some interest in that at the summit and the issue was "which" tests.12:28
dirkdims_: ;)12:28
dirktonyb: good point..12:29
dims_tonyb : can you please add TODO(s) in https://etherpad.openstack.org/p/requirements-tasks ?12:29
tonyb(that's how I know the project set that covers 55% of g-r)12:29
promethe1nfiretonyb: ya, I thought it was a good idea, should we just pick some and see what still breaks?12:29
tonybbetter coverage is hard to get as we have lots of leaf items :(12:29
dhellmanndims_ : we've merged the patch to automatically submit constraint updates when needed. I just submitted another to give all of those reviews a consistent topic of "new-release"12:30
dims_tonyb : my sniff wip reviews run the unit tests too12:30
tonybpromethe1nfire: Well we need to do some infra work first which will be mildly cumbersome12:30
promethe1nfireah, ya12:30
dhellmanndims_ : those are the only release changes I can think of, unless you had something else in mind?12:30
dims_dhellmann : nice thanks!12:30
tonybdims_: Sure this was aimed at offical gateing12:30
dims_tonyb : ack12:31
dims_who wants to help tonyb ? :)12:31
tonybdims_: we need to decide if it's a good idea ;P12:31
tonybdims_: Sean was against it at the time12:31
dims_tonyb : we don't want to add *all* projects, we need a good representation or we would never land anything12:32
*** IgorYozhikov has joined #openstack-meeting-cp12:32
dims_guessing that was sdague 's concern as well?12:32
promethe1nfireprojects that have good coverage would be nice, or ones that use more esoteric things12:32
tonybdims_: sure.  We'd need to have a *very* good reasin for adding projects to the list if it was gateing12:32
tonybdims_: Yeah I think that was the crux of it.12:33
dims_ok switching topics12:33
dims_#topic TODO(s) from our backlog - https://etherpad.openstack.org/p/requirements-tasks12:33
*** openstack changes topic to "TODO(s) from our backlog - https://etherpad.openstack.org/p/requirements-tasks (Meeting topic: requirements)"12:33
dhellmannwe should probably leave out projets that use the more obscure requirements, since they're likely to be the teams proposing changes in the first place12:33
dims_dhellmann : ++12:34
dims_anyone interested in picking up something to work on?12:34
tonybdims_: It seems a few poeple are working on the cruft problem12:34
dims_tonyb : right, almost done i think12:35
promethe1nfiredhellmann: right, I was speaking of more esoteric usage, not the requirements themselves12:35
dims_under "proactive tasks" we unblocked the keystone team to experiement with packages that work under python3 for LDAP12:35
tonybdims_: probably :)12:35
promethe1nfiredims_: for both libraries :|12:36
dims_promethe1nfire : you mean they have 2 sets of possible things to use?12:36
sigmavirus24So other than those dim/test/constraints reviews, how can we improve test coverage?12:37
sigmavirus24Is that the only axis we're measuring test coverage on?12:37
dims_sigmavirus24 : the oslo team has a set of periodic jobs to test several projects with oslo.* from master repos12:37
*** promethe1nfire is now known as prometheanfire12:38
dims_sigmavirus24 : that's about it12:38
dirkdims_: how ot find those jobs?12:38
prometheanfiredims_: keystone has pyldap and python-ldap both supporting python312:38
dims_dirk : https://etherpad.openstack.org/p/dims-periodic-jobs12:38
*** anteaya has joined #openstack-meeting-cp12:38
dirkdims_: great!12:39
prometheanfirethey added pyldap a couple of days ago and just requested a bump of python-ldap yesterday12:39
dims_prometheanfire : by m1/m2, we should make sure they use one set12:39
prometheanfireya, it needs to be tracked12:39
dims_they are still experimenting i think12:39
prometheanfireI can bug stanek and dolphm12:39
dims_stevemar : bknudson : dolphm : ^^12:39
dims_:)12:39
prometheanfire:D12:39
dims_prometheanfire : agree12:39
dims_#topic - daily reviews12:40
*** openstack changes topic to "- daily reviews (Meeting topic: requirements)"12:40
dims_around this time every day, starting about 7 AM my time (we started the meeting at 8 AM my time), me and dirk and others have been trading comments on reviews as well as on IRC12:40
dims_is anyone else available to join us?12:41
dims_this way, we push a bunch of things out, then see if anything fails by end of day, then start again next day with a fresh slate12:41
coolsvap+1 although its almost eod for me, but i can join for couple of hours12:41
dims_coolsvap : nice!12:41
dirkI actually put it on my morning routine (which is like 4-5 hours before dims_ ;) )12:41
prometheanfireI'd be available to do that at 10 or 11 your time12:41
tonybdims_: I can check in at the start of my day which would be toward the end of yours but no overlap with the others12:42
dims_tonyb : ack. i am usually still around when you begin your day :)12:42
dirkdims_: one of the action items is to publish the information that people should come and ping in openstack-requirements channel for issues..12:42
sigmavirus24dims_: It's 7am for me, but I can join later12:42
IgorYozhikovI can try to review from 12 gmt+312:42
dims_sigmavirus24 : awesome12:42
prometheanfiredirk: +112:42
dims_IgorYozhikov : ack. cool12:42
dims_dirk : action to send an email to the ML tomorrow about the channel?12:43
tonybI can add the channel to IRC wiki page, dims do you want to email the list?12:43
dirkI can take that action12:43
dirkbut I think a more permant place is better12:43
dims_dirk : thanks!12:43
dirkI just don't know where.. somewhere on elastic check pages or so?12:43
prometheanfireradme?12:43
prometheanfirereadme12:43
dirk"we noticed that g-r broke your fancy project. please come to irc and tell us about it"12:44
dims_dirk : +112:44
dirkdoes anyone have a good place to put that information?12:44
prometheanfireah, right12:44
dirkhttps://wiki.openstack.org/wiki/Requirements might be a good candidate for refreshment12:45
dims_#topic - adding folks to team roster12:45
*** openstack changes topic to "- adding folks to team roster (Meeting topic: requirements)"12:45
dims_ttx, dhellmann - thoughts here?12:45
prometheanfiretonyb wanted to be ptl, was practicaly begging for it12:46
dims_since we officially started today, probably check back in a month on reviews, engagement and figure out who we can add?12:46
dhellmannprometheanfire : that's how I remember it, too12:46
dims_all hail tonyb :)12:46
tonybprometheanfire: uuuuummmm that's not how I remember it12:46
dhellmanndims_ : yeah, let's run as a team for a few weeks and see how it goes12:46
dhellmanntonyb : you might not have been in the room at that point ;-)12:46
ttxyes, we should definitely revisit core once we know who is sticking12:46
dims_:)12:46
prometheanfiretonyb: you're welcome, and I'm sorry12:46
* dims_ leaves "when" on ttx and dhellmann 's hands12:47
dims_#topic open discussion12:47
*** openstack changes topic to "open discussion (Meeting topic: requirements)"12:47
dims_So was the info in the etherpad enough?12:47
dims_do folks have an idea of what we need to do here? :)12:47
dhellmannI want to reiterate my thanks for all of you joining the team. It's good to see this work have some dedicated folks looking at it.12:47
dims_++ dhellmann !12:48
prometheanfireI think so12:48
dhellmannAnd thank you dims, for taking the lead in organizing the meeting and the todo list and everything else.12:48
*** amrith is now known as _amrith_12:48
tonybdhellmann: Thanks for picking a scary title to get us in a room :)12:48
dims_my pleasure dhellmann12:48
prometheanfireheh, ya12:48
dims_LOL12:48
dhellmanntonyb : yeah, I'll have to be more careful at future summits or folks won't come to my sessions :-)12:49
tonybdhellmann: :)12:49
prometheanfireyou only get to use that once in 2-4 summits12:49
dims_one another ML thread i'd like to bring to everyone's attention is from IgorYozhikov : http://markmail.org/message/awlpe5huktysxslj12:49
tonybSo if this is a happening thing I'll make a calendar entry (probably in #openstack-meeting)12:49
tonybsound good?12:49
dims_tonyb : please go ahead to do the calendar entry12:50
sigmavirus24Thanks tonyb12:50
dims_tonyb : please add yourself as chair for now12:50
* sigmavirus24 snickers12:50
IgorYozhikovdims_, I believe that we already discussed it or new questions appears?12:50
dims_IgorYozhikov : want to be sure more folks read that thread12:50
* dhellmann has to drop off early12:50
dims_thanks dhellmann12:51
IgorYozhikovdims_, i c, thanx12:51
* sigmavirus24 was snickering about tonyb being the chair12:51
tonybdims_: ;P12:51
sigmavirus24bye dhellmann12:51
prometheanfiresigmavirus24: will you be a stool?12:51
dims_yew!12:51
sigmavirus24prometheanfire: as long as I'm the useful kind and not the smelly kind12:51
prometheanfiresigmavirus24: dunno, some days you do kinda have an 'air' about you12:53
coolsvapthanks dims for arranging the meeting!12:53
dirkdims_: one action item from that thread imho is to review those cases where requirements and uc diverge significantly if that is still correct12:53
dirkso does anyone want to help revive https://wiki.openstack.org/wiki/Requirements ?12:54
prometheanfiredirk: you mean if there's a big diff in versions?12:54
dirkit is currently marked as deprecation12:54
dirkprometheanfire: yep12:54
dirkprometheanfire: either that, or just by git commit messages (like e.g. uc got updated in 2016 but lower bounds last time in 2014 or so)12:54
prometheanfirenot a problem for me, luckilly12:54
coolsvapdirk, yes we need to update the page12:54
*** ninag has joined #openstack-meeting-cp12:55
dims_so folks feel free to self-organize :) we can go back to our channel12:55
dims_thanks everyone12:55
coolsvapcan we open an etherpad to first to finalize the content12:55
prometheanfirecya12:55
coolsvapthanks dims12:55
dims_#endmeeting12:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:55
openstackMeeting ended Wed May 18 12:55:37 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/requirements/2016/requirements.2016-05-18-12.00.html12:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/requirements/2016/requirements.2016-05-18-12.00.txt12:55
openstackLog:            http://eavesdrop.openstack.org/meetings/requirements/2016/requirements.2016-05-18-12.00.log.html12:55
ttxdims_: are you going to file the irc-meetings request for that ?12:55
sigmavirus24dirk: so I think lower bounds aren't meant to change based on the MUST READ portions of the etherpad12:55
dims_ttx : tonyb will do that12:56
ttxok12:56
ttxthanks for kicking that one12:56
prometheanfirelol12:56
*** prometheanfire has left #openstack-meeting-cp12:56
*** tyr_ has joined #openstack-meeting-cp12:56
dirkdims_: tonyb : so next week same day same time?12:58
dims_dirk : tonyb : yep, sounds good12:58
tonybdirk: yup but different channel12:58
tonybttx, https://review.openstack.org/31804313:00
coolsvaptonyb, sorry for -113:01
tonybcoolsvap: why?13:01
coolsvapagenda_url: https://wiki.openstack.org/wiki/Meetings/Nova13:01
*** tyr_ has quit IRC13:01
tonybcoolsvap: Gah!  now you know which file I copied ;P13:02
tonybcoolsvap: fixed13:02
tonybcoolsvap: thanks13:02
coolsvaptonyb, :)13:02
*** lbragstad_ is now known as lbragstad13:39
*** aliadil has joined #openstack-meeting-cp13:41
*** diablo_rojo has joined #openstack-meeting-cp13:49
*** ninag has quit IRC14:02
*** apevec has left #openstack-meeting-cp14:03
*** ninag has joined #openstack-meeting-cp14:04
*** ninag has quit IRC14:09
*** ninag has joined #openstack-meeting-cp14:12
*** sdake has joined #openstack-meeting-cp14:14
*** tyr_ has joined #openstack-meeting-cp14:23
*** sdake has quit IRC14:26
*** sdake has joined #openstack-meeting-cp14:27
*** ninag has quit IRC14:32
*** ninag has joined #openstack-meeting-cp14:33
*** ninag has quit IRC14:37
*** sdake_ has joined #openstack-meeting-cp14:42
*** sdake has quit IRC14:43
*** xyang1 has joined #openstack-meeting-cp14:52
*** coolsvap has quit IRC14:53
*** _amrith_ is now known as amrith14:53
*** coolsvap has joined #openstack-meeting-cp14:54
*** diablo_rojo has quit IRC14:59
*** diablo_rojo has joined #openstack-meeting-cp15:09
*** ninag has joined #openstack-meeting-cp15:10
*** ninag has quit IRC15:14
*** ninag has joined #openstack-meeting-cp15:18
*** ninag has quit IRC15:21
*** ninag has joined #openstack-meeting-cp15:21
*** itisha has joined #openstack-meeting-cp15:26
*** belmoreira has quit IRC15:32
*** ninag has quit IRC15:43
*** ninag has joined #openstack-meeting-cp15:54
*** Rockyg has joined #openstack-meeting-cp15:55
*** diablo_rojo has quit IRC15:56
*** ninag has quit IRC15:58
*** ninag has joined #openstack-meeting-cp15:58
*** diablo_rojo1 has joined #openstack-meeting-cp16:01
*** diablo_rojo1 is now known as diablo_rojo16:02
*** gnarld_ is now known as cFouts16:02
*** ninag has quit IRC16:04
*** ninag has joined #openstack-meeting-cp16:04
*** ninag has quit IRC16:09
*** ninag has joined #openstack-meeting-cp16:10
*** ninag has quit IRC16:15
*** anteaya has quit IRC16:21
*** ninag has joined #openstack-meeting-cp16:27
*** sdake_ has quit IRC16:31
*** sdake has joined #openstack-meeting-cp16:31
*** ninag has quit IRC16:34
*** ninag has joined #openstack-meeting-cp16:34
*** ninag has quit IRC16:40
*** amrith is now known as _amrith_16:45
*** ninag has joined #openstack-meeting-cp16:47
*** vilobhmm11 has joined #openstack-meeting-cp16:48
*** Guest37264 is now known as melwitt16:51
*** ninag has quit IRC16:52
*** ninag has joined #openstack-meeting-cp16:52
*** ninag has quit IRC16:52
*** ninag has joined #openstack-meeting-cp16:53
*** ninag has quit IRC16:55
*** ninag has joined #openstack-meeting-cp16:55
*** ninag has quit IRC17:00
*** ninag has joined #openstack-meeting-cp17:02
*** ninag has quit IRC17:11
*** ninag has joined #openstack-meeting-cp17:15
*** ninag_ has joined #openstack-meeting-cp17:16
*** Rockyg has quit IRC17:17
*** diablo_rojo has quit IRC17:17
*** ninag has quit IRC17:20
*** ninag_ has quit IRC17:20
*** _amrith_ is now known as amrith17:32
*** ninag has joined #openstack-meeting-cp17:40
*** ninag has quit IRC17:45
*** ninag has joined #openstack-meeting-cp17:46
*** piet has joined #openstack-meeting-cp17:51
*** vilobhmm111 has joined #openstack-meeting-cp18:01
*** vilobhmm11 has quit IRC18:04
*** coolsvap has quit IRC18:20
*** hemna is now known as hemnafk18:21
*** sdake_ has joined #openstack-meeting-cp18:31
*** sdake has quit IRC18:33
*** rockyg has joined #openstack-meeting-cp18:44
*** anteaya has joined #openstack-meeting-cp18:47
*** flwang1 has joined #openstack-meeting-cp18:54
*** anteaya has quit IRC18:57
*** piet has quit IRC19:05
*** piet has joined #openstack-meeting-cp19:06
*** diablo_rojo has joined #openstack-meeting-cp19:08
*** kbyrne has quit IRC19:16
*** flwang1 has quit IRC19:18
*** kbyrne has joined #openstack-meeting-cp19:20
*** piet has quit IRC19:21
*** sdake_ has quit IRC19:23
*** flwang1 has joined #openstack-meeting-cp19:26
*** piet has joined #openstack-meeting-cp19:28
*** diablo_rojo has quit IRC19:28
*** ninag has quit IRC19:41
*** ninag has joined #openstack-meeting-cp19:45
*** sdake has joined #openstack-meeting-cp19:48
*** flwang1 has quit IRC19:58
*** diablo_rojo has joined #openstack-meeting-cp20:04
*** vilobhmm11 has joined #openstack-meeting-cp20:06
*** vilobhmm111 has quit IRC20:06
*** ninag has quit IRC20:21
*** vilobhmm111 has joined #openstack-meeting-cp20:22
*** vilobhmm11 has quit IRC20:25
*** ninag has joined #openstack-meeting-cp20:27
*** vilobhmm111 has quit IRC20:50
*** ninag has quit IRC21:01
*** piet has quit IRC21:11
*** ninag has joined #openstack-meeting-cp21:15
*** piet has joined #openstack-meeting-cp21:32
*** aliadil has quit IRC21:32
*** diablo_rojo has quit IRC21:33
*** rockyg has quit IRC21:35
*** flwang1 has joined #openstack-meeting-cp21:35
*** markvoelker has joined #openstack-meeting-cp21:51
*** markvoelker has quit IRC21:52
*** markvoelker has joined #openstack-meeting-cp21:53
*** piet has quit IRC21:57
*** anteaya has joined #openstack-meeting-cp22:14
*** harlowja has quit IRC22:22
*** itisha has quit IRC22:29
*** ninag has quit IRC22:45
*** ninag has joined #openstack-meeting-cp22:45
*** ninag has quit IRC22:50
*** tyr_ has quit IRC22:58
*** harlowja has joined #openstack-meeting-cp23:00
*** anteaya has quit IRC23:01
*** markvoelker_ has joined #openstack-meeting-cp23:05
*** markvoelker_ has quit IRC23:05
*** markvoelker_ has joined #openstack-meeting-cp23:06
*** markvoelker has quit IRC23:09
*** sdague has quit IRC23:14
*** xyang1 has quit IRC23:19
*** diablo_rojo has joined #openstack-meeting-cp23:27
*** markvoelker has joined #openstack-meeting-cp23:53
*** markvoelker_ has quit IRC23:56

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