Tuesday, 2019-08-27

*** markvoelker has joined #openstack-meeting-alt00:10
*** markvoelker has quit IRC00:15
*** gyee has quit IRC00:18
*** hongbin has joined #openstack-meeting-alt00:37
*** slaweq has joined #openstack-meeting-alt01:11
*** lseki has quit IRC01:12
*** rcernin has quit IRC01:13
*** slaweq has quit IRC01:16
*** bhavikdbavishi has joined #openstack-meeting-alt01:31
*** bhavikdbavishi1 has joined #openstack-meeting-alt01:35
*** bhavikdbavishi has quit IRC01:35
*** bhavikdbavishi1 is now known as bhavikdbavishi01:35
*** apetrich has quit IRC02:10
*** slaweq has joined #openstack-meeting-alt02:11
*** rcernin has joined #openstack-meeting-alt02:13
*** slaweq has quit IRC02:16
*** markvoelker has joined #openstack-meeting-alt03:10
*** markvoelker has quit IRC03:15
*** jtomasek has quit IRC04:00
*** rfolco has quit IRC04:03
*** markvoelker has joined #openstack-meeting-alt04:10
*** slaweq has joined #openstack-meeting-alt04:11
*** hongbin has quit IRC04:13
*** markvoelker has quit IRC04:15
*** slaweq has quit IRC04:16
*** dave-mccowan has quit IRC04:36
*** jtomasek has joined #openstack-meeting-alt04:44
*** macz has joined #openstack-meeting-alt04:58
*** macz has quit IRC05:03
*** sridharg has joined #openstack-meeting-alt05:10
*** sridharg has quit IRC05:10
*** markvoelker has joined #openstack-meeting-alt05:10
*** sridharg has joined #openstack-meeting-alt05:11
*** slaweq has joined #openstack-meeting-alt05:11
*** markvoelker has quit IRC05:15
*** slaweq has quit IRC05:16
*** links has joined #openstack-meeting-alt05:52
*** ccamacho has quit IRC05:52
*** lpetrut has joined #openstack-meeting-alt06:02
*** e0ne has joined #openstack-meeting-alt06:06
*** macz has joined #openstack-meeting-alt06:11
*** e0ne has quit IRC06:11
*** slaweq has joined #openstack-meeting-alt06:11
*** macz has quit IRC06:15
*** slaweq has quit IRC06:15
*** brault has joined #openstack-meeting-alt06:38
*** macz has joined #openstack-meeting-alt06:39
*** macz has quit IRC06:44
*** markvoelker has joined #openstack-meeting-alt07:06
*** slaweq has joined #openstack-meeting-alt07:11
*** _pewp_ has quit IRC07:12
*** _pewp_ has joined #openstack-meeting-alt07:13
*** markvoelker has quit IRC07:15
*** slaweq has quit IRC07:15
*** macz has joined #openstack-meeting-alt07:17
*** macz has quit IRC07:22
*** markvoelker has joined #openstack-meeting-alt07:35
*** rcernin has quit IRC07:40
*** markvoelker has quit IRC07:40
*** slaweq has joined #openstack-meeting-alt07:52
*** panda has quit IRC08:02
*** panda has joined #openstack-meeting-alt08:02
*** tetsuro has joined #openstack-meeting-alt08:21
*** apetrich has joined #openstack-meeting-alt08:22
*** masahito has joined #openstack-meeting-alt08:34
*** markvoelker has joined #openstack-meeting-alt08:40
*** markvoelker has quit IRC08:45
*** ccamacho has joined #openstack-meeting-alt08:47
*** priteau has joined #openstack-meeting-alt08:50
*** derekh has joined #openstack-meeting-alt08:50
*** masahito has quit IRC08:51
*** masahito has joined #openstack-meeting-alt08:51
*** slaweq has quit IRC08:53
*** macz has joined #openstack-meeting-alt08:53
*** bobmel has quit IRC08:54
*** macz has quit IRC08:58
priteau#startmeeting blazar08:59
openstackMeeting started Tue Aug 27 08:59:53 2019 UTC and is due to finish in 60 minutes.  The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot.08:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:59
*** openstack changes topic to " (Meeting topic: blazar)"08:59
openstackThe meeting name has been set to 'blazar'08:59
priteau#topic Roll call09:00
*** openstack changes topic to "Roll call (Meeting topic: blazar)"09:00
masahitoo/09:01
priteauHi masahito09:01
priteautetsuro: Are you here too?09:03
tetsuroo/09:03
priteauHi tetsuro09:04
tetsuroHi09:04
priteauAgenda for today09:04
priteau* Client release09:04
priteau* Change of blazar-dashboard release model09:04
priteau* Code review priorities09:04
priteau* AOB09:04
priteau#topic Client release09:04
*** openstack changes topic to "Client release (Meeting topic: blazar)"09:04
priteau#info python-blazarclient 2.2.0 was released last week09:04
priteau#link https://pypi.org/project/python-blazarclient/09:04
priteau#action Write floating IP reservation docs09:05
priteauThere are also some client patches pending review, if we want to include them in Train we need to release the client again before Sep 09 - Sep 1309:06
priteauAlthough none of them are ready: https://review.opendev.org/#/q/project:openstack/python-blazarclient+is:open09:07
priteauThe switch to stestr is not critical and if we merge it I would like to synchronize it with all the other blazar repos09:08
priteau#topic Change of blazar-dashboard release model09:09
*** openstack changes topic to "Change of blazar-dashboard release model (Meeting topic: blazar)"09:09
priteauWe got an answer from Thierry about the change of release model: https://review.opendev.org/#/c/675471/09:09
priteauHe said: "It is possible to move back to cycle-with-intermediary.... However if you are likely to do that, I would rather stay on cycle-with-intermediary and just do one release this cycle. Just remember to do it before the RC1 deadline !"09:09
*** slaweq has joined #openstack-meeting-alt09:10
priteauBecause we're not sure we will have enough activity on blazar-dashboard to release multiple times per cycle, I propose that we mov to cycle-with-rc for Train and keep using this model until we get enough activity to go back to cycle-with-intermediary09:11
priteauAny thoughts / objections?09:11
masahitono objections from my side09:11
tetsurono objections09:12
priteauSo we will need to create an RC1 for blazar-dashboard soon. I would like to see if I can add some floating IP support easily.09:13
priteau#topic Code review priorities09:14
*** openstack changes topic to "Code review priorities (Meeting topic: blazar)"09:14
*** slaweq has quit IRC09:14
priteautetsuro: I see that you submitted a query optimization patch earlier, I will look as soon as possible.09:15
priteauThanks for doing this.09:15
ttxpriteau: re : RC1 you have a few more weeks for it09:15
priteauttx: About a month, it will come quicly!09:16
priteauquickly09:16
tetsuroThat is after https://review.opendev.org/#/c/672994/3 and less controversial09:16
ttxbetween now and then you could request a beta-1 if you want to exercise the process, after the release model change09:16
priteauttx: Thanks for letting us know09:16
ttxOne benefit of the cycle-with-rc process is that it lets you have a number of pre-release opportunities (betas)09:17
priteaumasahito: Could you please take a look at https://review.opendev.org/#/c/671312/ and +2 if it looks good to you?09:17
ttxthen switch to RCs when you are in "releasable" state09:17
ttxwe just automatically take the latest RC available to make it as "the release" at the end of the cycle09:18
*** slaweq has joined #openstack-meeting-alt09:20
priteauThanks masahito09:21
priteauOther patch series going on:09:24
priteau* network reservation: Jake will update his specs patch (I've left comments), we can already comment on the code: https://review.opendev.org/#/c/668749/09:25
*** slaweq has quit IRC09:25
priteau* floating IP reservation update: https://review.opendev.org/#/c/672763/09:25
priteaumasahito: what were your thoughts on ^^^09:25
masahitoI'll check it.09:28
masahitoDo you plan to release all network reservation feature in T?09:29
priteauIf possible, yes. But at least completing floating IP reservation is essential since we promised it for T09:29
masahitookay. I'll review floating ip patch first09:30
priteauThank you09:31
priteauAny other patch to mention particularly?09:33
tetsuroThe series starting from https://review.opendev.org/#/c/637140/15 is also ready for reviewing09:36
priteauThanks for the reminder09:37
priteau#topic AOB09:38
*** openstack changes topic to "AOB (Meeting topic: blazar)"09:38
priteauPTL election season is coming up again09:39
priteauThe nomination period officially begins Aug 27, 2019 23:45 UTC.09:39
priteauwhich is later today!09:39
priteauIs anyone planning to self-nominate?09:40
priteauI will submit my nomination if no one else wants to ;-)09:42
masahito+1 to your nomination :-)09:43
tetsuro+1. thank you!09:44
priteauThanks for your support :-)09:45
priteauAnything else to discuss today?09:45
priteaumasahito: I noticed that Gerrit still shows your old email address09:47
masahitosorry, I haven't changed it yet.09:48
priteauPlease do so you can receive notifications when we add you as reviewer09:49
priteauI think that's all for today, let's end here09:51
priteauThanks both for joining09:51
priteau#endmeeting09:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:51
openstackMeeting ended Tue Aug 27 09:51:18 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-08-27-08.59.html09:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-08-27-08.59.txt09:51
openstackLog:            http://eavesdrop.openstack.org/meetings/blazar/2019/blazar.2019-08-27-08.59.log.html09:51
masahitoThanks09:53
*** apetrich has quit IRC09:55
*** bobmel has joined #openstack-meeting-alt09:59
*** apetrich has joined #openstack-meeting-alt10:00
*** e0ne has joined #openstack-meeting-alt10:11
*** masahito has quit IRC10:18
*** macz has joined #openstack-meeting-alt10:19
*** macz has quit IRC10:24
*** e0ne has quit IRC10:26
*** e0ne has joined #openstack-meeting-alt10:28
*** e0ne has quit IRC10:32
*** tetsuro has quit IRC10:34
*** macz has joined #openstack-meeting-alt10:40
*** macz has quit IRC10:45
*** slaweq has joined #openstack-meeting-alt10:55
*** macz has joined #openstack-meeting-alt11:01
*** carloss has joined #openstack-meeting-alt11:03
*** macz has quit IRC11:06
*** tesseract has joined #openstack-meeting-alt11:11
*** macz has joined #openstack-meeting-alt11:22
*** macz has quit IRC11:27
*** slaweq has quit IRC11:31
*** slaweq has joined #openstack-meeting-alt11:33
*** dave-mccowan has joined #openstack-meeting-alt11:35
*** slaweq has quit IRC11:41
*** slaweq has joined #openstack-meeting-alt11:52
*** slaweq has quit IRC11:57
*** markvoelker has joined #openstack-meeting-alt12:10
*** slaweq has joined #openstack-meeting-alt12:12
*** slaweq has quit IRC12:17
*** links has quit IRC12:20
*** rfolco has joined #openstack-meeting-alt12:22
*** bobmel has quit IRC12:30
*** bobmel has joined #openstack-meeting-alt12:30
*** bobmel has quit IRC12:30
*** links has joined #openstack-meeting-alt12:35
*** bobmel has joined #openstack-meeting-alt12:36
*** slaweq has joined #openstack-meeting-alt12:40
*** priteau has quit IRC12:44
*** jraju__ has joined #openstack-meeting-alt12:58
*** links has quit IRC12:59
*** bobmel has quit IRC13:00
*** jcoufal has joined #openstack-meeting-alt13:00
*** bobmel has joined #openstack-meeting-alt13:00
*** slaweq has quit IRC13:04
*** macz has joined #openstack-meeting-alt13:10
*** macz has quit IRC13:15
*** bhavikdbavishi has quit IRC13:29
*** bhavikdbavishi has joined #openstack-meeting-alt13:29
*** dklyle has quit IRC13:38
*** david-lyle has joined #openstack-meeting-alt13:38
*** priteau has joined #openstack-meeting-alt13:44
*** macz has joined #openstack-meeting-alt13:48
*** macz has quit IRC13:52
*** e0ne has joined #openstack-meeting-alt13:54
*** jcoufal_ has joined #openstack-meeting-alt14:02
*** lseki has joined #openstack-meeting-alt14:02
*** liuyulong has joined #openstack-meeting-alt14:05
*** jcoufal has quit IRC14:05
*** priteau has quit IRC14:39
*** lpetrut has quit IRC14:44
*** gagehugo has joined #openstack-meeting-alt14:51
*** david-lyle has quit IRC15:01
*** david-lyle has joined #openstack-meeting-alt15:01
*** sridharg has quit IRC15:02
*** jamesmcarthur has joined #openstack-meeting-alt15:05
*** ccamacho has quit IRC15:23
*** gyee has joined #openstack-meeting-alt15:37
*** macz has joined #openstack-meeting-alt15:42
*** vishakha has joined #openstack-meeting-alt15:50
*** brault has quit IRC15:50
*** e0ne has quit IRC15:52
kmalloc#startmeeting keystone16:01
openstackMeeting started Tue Aug 27 16:01:07 2019 UTC and is due to finish in 60 minutes.  The chair is kmalloc. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: keystone)"16:01
openstackThe meeting name has been set to 'keystone'16:01
gagehugoo/16:01
bnemeco/16:01
kmalloci'll give a couple minutes for people to arrive.16:01
kmallocit is probably going to be a short meeting.16:02
vishakhao/16:02
kmallocor short on planned agenda at least16:02
lbragstado/16:02
knikollao/16:03
kmallocok16:07
kmalloclets get started16:07
kmalloc#topic Request for Review16:07
*** openstack changes topic to "Request for Review (Meeting topic: keystone)"16:07
kmallocKSM v2 removals16:07
kmallocgagehugo: o/16:08
gagehugoo/ that's me16:08
kmalloc#link https://review.opendev.org/#/c/678386/16:08
kmalloc#link https://review.opendev.org/#/c/669706/16:08
gagehugothose two for now16:08
kmallocthe other links?16:08
kmallochttps://review.opendev.org/#/c/677585/ and  https://review.opendev.org/#/q/status:open+project:openstack/keystone+branch:master+topic:bug/1805409 ?16:08
gagehugoI mean for ksmv216:08
gagehugoidk about the other links16:09
vishakha0/16:09
kmallocin short we're working to remove the v2 support from keystonemiddleware, gagehugo has been working on getting things passing16:09
kmallocand looks like vishakha is too :)16:09
vishakhalink https://review.opendev.org/#/c/677585/ , this is colleen's patch for client support app creds. open for review16:10
kmallocvishakha: ahhh16:10
kmallocthere we go16:10
vishakhaif its good to go we can propose build of keystomeclient  so that it is available for openstackclient16:10
kmallocanyway, keystonemiddleware dropping v2 support will ease up the codebase for further cleanup16:10
kmallocask gagehugo questions16:10
kmalloc#link https://review.opendev.org/#/c/677585/16:11
kmallocneeds eyes, it's app-cred related16:11
vishakhathanks kmalloc16:11
kmallocwhile cmurphy is on vacation, please feel free to review/comment/approve, etc16:11
gagehugovishakha thanks16:12
kmallocif you have questions both vishakha and I are available to help :)16:12
kmallocand finally16:12
kmalloc#link https://review.opendev.org/#/q/status:open+project:openstack/keystone+branch:master+topic:bug/180540916:12
kmalloclots of policy related work, help to get them passing gate and get these landed would be appreciated16:12
vishakhathis is few left in policy API in system scopes16:12
* kmalloc nods.16:12
kmallocvishakha: want to continue with the other changes you have in flight?16:13
* kmalloc noticed more review requests by vishakha on the agenda :)16:13
vishakhaThats all for policy and association API16:13
kmallocbut there is also oauthlib and pdf docs.16:14
knikollai did review a whole bunch yesterday, will be happy to keep reviewing16:14
vishakhathanks kmalloc knikolla16:14
kmallocyay knikolla reviews!16:14
vishakhafor oauthlib I can many test cases failing but I am still digging the reason of failure16:15
* kmalloc nods.16:15
vishakhaHelp will be appreciated :)16:16
kmalloclooks like an unfortunate case of the lib changed pretty drastically in weird ways.16:16
kmallocs/weird/subtle16:16
vishakhaAlso for the pdf docs we came across with the errors none of the other project ran into. Also asked the docs team to look inti16:17
* kmalloc nods.16:17
vishakhas/inti/into16:17
kmallocthat is a bit weird of an error16:17
vishakhakmalloc: yes it is16:18
vishakhathat's it from my side16:20
kmallocok i think we're on for lbragstad16:20
kmalloclbragstad: o/16:20
lbragstado;16:20
lbragstado/16:20
gyeevishakha, what's the weird error. Out of memory?16:21
lbragstadok - so cmurphy|afk kmalloc and i were looking at the test run times for unit tests16:21
gyeeI know others had hit that error recently, especially with large docs16:21
lbragstadand the obvious culprit for increased run times is all the protection testing we've been doing16:21
kmallocgyee: matrix file missing.16:22
lbragstadi wanted to throw this on the agenda so that we could discuss additional ideas for how to keep testing policy but in ways that don't take forever or spool out of control16:22
vishakhagyee:  https://zuul.opendev.org/t/openstack/build/ec6d51585a3c4b31b42aebe928c73e35/log/job-output.txt#539516:22
gyeek, that's different one then16:22
*** jamesmcarthur has quit IRC16:22
lbragstadinitially - we were thinking that reusing some of the common resources would help out - and it certainly would16:23
*** david-lyle is now known as dklyle16:23
lbragstadbut we're ultimately making a lot of API requests, period16:23
kmalloci'm sure that re-using fernet / cred repos would help a lot16:23
kmallocthat is both random/urandom and filesystem access16:24
lbragstadand some of the bootstrap resources - but the testresources work has kinda hit a wall16:24
lbragstad(i'm also not convinced its possible to do what we want with testresources)16:24
lbragstadintegrating that into our tests has been painful16:24
lbragstadbut that's the recommended approach over using native structures like setUpClass or setUpModule16:25
lbragstadi'm wondering how people feel about graduating the protection tests to formal functional tests...16:25
kmalloci'd be ok with that16:26
gagehugosame16:26
kmallochowever, i don't think it's going to reduce local testing load16:26
lbragstadi haven't planned things out in detail yet16:26
kmallocbecause we're going to need to run these locally as well as unit tests16:26
lbragstadyeah - we'd definitely keep gating on them16:27
kmallocwe might be able to at least isolate the protection tests into testresources16:27
kmallocesp. if we're putting them into their own test-run16:27
lbragstadbut they wouldn't be invoked by ``tox -re py37``16:27
*** jamesmcarthur has joined #openstack-meeting-alt16:27
kmallocbecause we have less concern about API correctness and more of policy behavior16:27
lbragstadinstead, we could exercise that suite using something like ``tox -e functional`` or ``tox -e protection``16:27
gyeewe can't mock the target part?16:27
kmalloci'd opt for -e protection, and i would opt for trying to use testresources or similar in the protection-only tests16:28
kmallocwe can re-merge them to -epy37 if we want later or keep them isolated16:28
lbragstadsure - i think we should still vet that16:28
kmallocwe are going to have to rebuild a chunk of them in either case.16:28
kmallocsince -eprotection isn't going to be fast16:28
lbragstadbut this would allow us to slim down the unit test times while we figure out what the deal is with testresources16:29
kmallocbut it's not trying to retrofit our entire test suite16:29
kmallocin one go.16:29
kmallockeep in mind it will only add concurrency to gating, it wont, in fact fix test runtimes overall or resource consumption16:29
kmallocunless we also do testresources or more streamlined setup work16:30
kmallocsomehow16:30
lbragstadat this point - i'd be happy if we could get testresources to handle bootstrap16:30
lbragstadand share those resources16:30
lbragstadif we can get that done, i'd say we can take the next step and look at other optimizations in how we set things up16:30
lbragstador we look at that now if testresources doesn't actually work for what we're trying to do with it16:31
kmalloc++16:31
* lbragstad thought it was going to be more straight forward to integrate that into keystone's protection tests16:31
kmallocwe might need to really just isolate and build a new core test structure up that does testresources from the get go16:32
kmallocit's a big chunk of work, but might be easier than retrofitting it into the current mess16:32
kmallocand history16:32
lbragstadyeah...16:32
lbragstadkinda damned if you do and damned if you don't...16:32
*** slaweq has joined #openstack-meeting-alt16:33
kmallocyup16:33
kmalloc*shrug*16:33
lbragstadeither way it's going to be a huge refactor16:33
*** liuyulong has quit IRC16:33
lbragstadunfortunately16:33
kmallocanything else?16:34
lbragstaddo we have general consensus on the approach?16:34
lbragstaddoes anyone see red flags with this?16:34
kmallocanyone want to volunteer (gyee ?) to toss some help over to lbragstad ?16:34
kmalloci don't see any red flags besides "it's a lot of work"16:34
kmallocand that is expected16:34
lbragstadagain - i'd just be happy to get things isolated this release16:34
lbragstadwe can have another gate job that exercises protection testing - running it in parallel with our existing unit tests16:35
lbragstad(which might help gate run times)16:35
kmallocwhich is at least a start16:35
lbragstadbut we're also not forcing people to testing thousands of protection tests if they're not modifying the api layer or policies directly16:35
gyeekmalloc, sure, yeah, it'll be a lot of work16:35
kmallocok16:36
kmallocmoving on, resource options (this is me/cmurphy)16:36
lbragstadthanks kmalloc and gyee16:36
kmallocsome code is posted to add resource options to roles and projects (+domains)16:36
kmalloc#link https://review.opendev.org/#/c/678322/16:36
kmalloccore addition of code16:36
kmalloc#link https://review.opendev.org/#/c/666739/16:36
kmallocimmutable option16:36
kmalloc#link https://review.opendev.org/#/c/678379/16:37
kmalloctempest change to disable a test16:37
kmalloc#link https://review.opendev.org/#/c/678380/16:37
kmalloctempest change to re-enable and fix the test16:37
kmalloceyes would be welcome16:37
kmallocsome tests are not 100% done16:37
kmallocand i know there are some issues with gate passing, that is related to LDAP and tempest tests16:37
kmalloci should have these fixed shortly16:37
kmallocbut, please review general approach16:37
kmallocdue to some complexity with the ORM, we opted to just create new tables for project_options and role_options16:38
kmalloca couple key things, an immutable project cannot have tags created/updated/deleted on it as well as cannot be updated or deletedc16:38
kmallocimmutable works similar to chattr command, you can change immutable options and other options in one go, but you may not, for example16:39
kmallocchange the project name and the immutable option at the same time16:39
kmallocthere is not a lot else to say here, feel free to reach out to me if you have questions16:39
kmallocfinal topic:16:40
kmalloc#topic meeting 2019-09-316:40
*** openstack changes topic to "meeting 2019-09-3 (Meeting topic: keystone)"16:40
kmallocUnless someone has a critical need, I am planning on skipping the meeting (for everyone). The day before is labor day (US Holiday), this will give us a bit more heads-down time to just keep plugging on items16:41
kmallocs/skipping/cancelling16:41
kmalloci wont send the cancel email until friday16:41
kmallocplease let me know if you have a critical item for the next meeting between now and friday16:42
kmalloc#topic open discussion16:42
*** openstack changes topic to "open discussion (Meeting topic: keystone)"16:42
kmallocanyone have anything else?16:42
* gagehugo does not16:42
*** amotoki is now known as amotoki_16:42
kmallocok16:43
kmalloc#endmeeting16:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:43
openstackMeeting ended Tue Aug 27 16:43:29 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-08-27-16.01.html16:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-08-27-16.01.txt16:43
kmallocthanks for joining us16:43
lbragstadthanks all16:43
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-08-27-16.01.log.html16:43
*** jamesmcarthur has quit IRC16:47
*** e0ne has joined #openstack-meeting-alt17:01
*** diablo_rojo has joined #openstack-meeting-alt17:02
*** derekh has quit IRC17:02
*** brault has joined #openstack-meeting-alt17:23
*** slaweq has quit IRC17:27
*** jamesmcarthur has joined #openstack-meeting-alt17:27
*** slaweq has joined #openstack-meeting-alt17:28
*** tesseract has quit IRC17:30
*** slaweq has quit IRC17:33
*** e0ne has quit IRC17:49
*** jamesmcarthur has quit IRC17:52
*** bhavikdbavishi has quit IRC17:52
*** bhavikdbavishi has joined #openstack-meeting-alt17:54
*** jcoufal_ has quit IRC17:55
*** jcoufal has joined #openstack-meeting-alt17:59
*** diablo_rojo has quit IRC18:03
*** bhavikdbavishi has quit IRC18:13
*** jcoufal_ has joined #openstack-meeting-alt18:29
*** jcoufal has quit IRC18:32
*** e0ne has joined #openstack-meeting-alt18:51
*** jamesmcarthur has joined #openstack-meeting-alt19:03
*** markvoelker has quit IRC19:07
*** markvoelker has joined #openstack-meeting-alt19:08
*** e0ne has quit IRC19:19
*** vishakha has quit IRC19:58
*** jraju__ has quit IRC20:10
*** jcoufal has joined #openstack-meeting-alt20:17
*** ijw has joined #openstack-meeting-alt20:19
*** jcoufal_ has quit IRC20:20
*** wxy-xiyuan has quit IRC20:45
*** jcoufal has quit IRC20:46
*** jamesmcarthur has quit IRC20:46
*** brault has quit IRC20:48
*** lpetrut has joined #openstack-meeting-alt20:50
*** lpetrut has quit IRC20:51
*** lpetrut has joined #openstack-meeting-alt20:51
*** ijw has quit IRC20:57
*** lpetrut has quit IRC20:58
*** ijw has joined #openstack-meeting-alt20:59
*** ijw has quit IRC21:03
*** markvoelker has quit IRC21:19
*** jtomasek has quit IRC21:29
*** ijw has joined #openstack-meeting-alt21:34
*** ijw has quit IRC21:37
*** ijw has joined #openstack-meeting-alt21:37
*** baojg has quit IRC21:47
*** baojg has joined #openstack-meeting-alt21:47
*** rcernin has joined #openstack-meeting-alt22:15
*** markvoelker has joined #openstack-meeting-alt22:15
*** markvoelker has quit IRC22:20
*** brault has joined #openstack-meeting-alt22:49
*** brault has quit IRC22:53
*** carloss has quit IRC23:06
*** markvoelker has joined #openstack-meeting-alt23:15
*** markvoelker has quit IRC23:20
*** macz has quit IRC23:36
*** markvoelker has joined #openstack-meeting-alt23:55

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