Tuesday, 2014-06-10

*** seizadi has quit IRC00:06
*** hurgleburgler has quit IRC00:19
*** nedbat_ has quit IRC00:19
*** nedbat has joined #openstack-meeting-300:20
*** tomoe_ has quit IRC00:27
*** eguz has quit IRC00:28
*** jaypipes has quit IRC00:32
*** chuckC has quit IRC00:37
*** banix has joined #openstack-meeting-300:41
*** nedbat has quit IRC00:46
*** nedbat has joined #openstack-meeting-300:46
*** cjellick has quit IRC00:47
*** cjellick has joined #openstack-meeting-300:47
*** chuckC has joined #openstack-meeting-300:50
*** nedbat has quit IRC00:50
*** cjellick has quit IRC00:51
*** yamahata has quit IRC00:52
*** nedbat has joined #openstack-meeting-300:56
*** nedbat has quit IRC00:56
*** seizadi has joined #openstack-meeting-301:01
*** rm_work is now known as rm_work|away01:07
*** rgbkrk has joined #openstack-meeting-301:09
*** flaviof is now known as flaviof_zzz01:20
*** seizadi has quit IRC01:24
*** rgbkrk_ has joined #openstack-meeting-301:25
*** devlaps has quit IRC01:26
*** davlaps has quit IRC01:26
*** rgbkrk has quit IRC01:28
*** nedbat has joined #openstack-meeting-301:31
*** nati_uen_ has quit IRC01:36
*** yamahata has joined #openstack-meeting-301:37
*** igordcard has quit IRC01:41
*** rgbkrk has joined #openstack-meeting-301:52
*** rgbkrk_ has quit IRC01:53
*** seizadi has joined #openstack-meeting-301:58
*** thomasem has joined #openstack-meeting-301:59
*** thomasem has quit IRC02:03
*** tomoe_ has joined #openstack-meeting-302:19
*** sankarshan is now known as sankarshan_away02:20
*** nati_ueno has joined #openstack-meeting-302:23
*** seizadi has quit IRC02:30
*** nedbat has quit IRC02:59
*** rgbkrk has quit IRC03:08
*** rgbkrk has joined #openstack-meeting-303:09
*** nati_ueno has quit IRC03:10
*** david-lyle has joined #openstack-meeting-303:11
*** rgbkrk has quit IRC03:18
*** rgbkrk has joined #openstack-meeting-303:18
*** sankarshan_away is now known as sankarshan03:24
*** rgbkrk has quit IRC03:30
*** rgbkrk_ has joined #openstack-meeting-303:30
*** rgbkrk_ has quit IRC03:36
*** thomasem has joined #openstack-meeting-303:36
*** rgbkrk has joined #openstack-meeting-303:37
*** thomasem has quit IRC03:38
*** thomasem has joined #openstack-meeting-303:39
*** gcb has joined #openstack-meeting-303:41
*** thomasem_ has joined #openstack-meeting-303:47
*** thomasem has quit IRC03:47
*** thomasem_ has quit IRC03:51
*** eghobo has joined #openstack-meeting-303:55
*** eghobo has quit IRC03:55
*** eghobo has joined #openstack-meeting-303:56
*** coolsvap|afk is now known as coolsvap03:57
*** yamamoto_ has joined #openstack-meeting-304:01
*** MarkAtwood has joined #openstack-meeting-304:02
*** rgbkrk has quit IRC04:06
*** dlenrow has quit IRC04:14
*** lenrow has joined #openstack-meeting-304:15
*** lcheng has joined #openstack-meeting-304:21
*** nelsnels_ has quit IRC04:22
*** yisun has joined #openstack-meeting-304:26
*** seizadi has joined #openstack-meeting-304:26
*** seizadi has quit IRC04:26
*** seizadi has joined #openstack-meeting-304:27
*** david-lyle has quit IRC04:33
*** seizadi has joined #openstack-meeting-304:35
*** eghobo has quit IRC04:36
*** catheri5 has joined #openstack-meeting-304:43
*** catheri5 has left #openstack-meeting-304:44
*** banix has quit IRC04:46
*** eghobo has joined #openstack-meeting-304:50
*** eghobo has quit IRC04:54
*** eghobo has joined #openstack-meeting-304:54
*** bobmel has joined #openstack-meeting-305:06
*** garyduan has joined #openstack-meeting-305:10
*** gcb has quit IRC05:14
*** gyee has quit IRC05:38
*** eguz has joined #openstack-meeting-305:50
*** eghobo has quit IRC05:50
*** seizadi has quit IRC05:57
*** jtomasek has joined #openstack-meeting-305:57
*** yisun has left #openstack-meeting-306:17
*** jamie_h has joined #openstack-meeting-306:26
*** jtomasek has quit IRC06:31
*** yamamoto_ has quit IRC06:35
*** eguz has quit IRC06:41
*** jtomasek has joined #openstack-meeting-306:48
*** seizadi has joined #openstack-meeting-306:54
*** mrunge has joined #openstack-meeting-306:58
*** seizadi has quit IRC06:58
*** jcoufal has joined #openstack-meeting-306:59
*** armax has quit IRC07:01
*** devlaps has joined #openstack-meeting-307:07
*** devlaps has quit IRC07:07
*** ttrifonov_zZzz is now known as ttrifonov07:13
*** mwagner_lap has quit IRC07:34
*** mrunge has quit IRC07:35
*** mwagner_lap has joined #openstack-meeting-307:36
*** enykeev has joined #openstack-meeting-307:45
*** bobmel has quit IRC07:47
*** gcb has joined #openstack-meeting-308:08
*** mrunge has joined #openstack-meeting-308:19
*** safchain has joined #openstack-meeting-308:20
*** jcoufal has quit IRC08:55
*** jcoufal has joined #openstack-meeting-308:56
*** nedbat has joined #openstack-meeting-309:17
*** tomoe_ has quit IRC09:19
*** nacim has joined #openstack-meeting-309:35
*** sankarshan is now known as sankarshan_away09:52
*** gcb has quit IRC10:04
*** MaxV has joined #openstack-meeting-310:16
*** gcb has joined #openstack-meeting-310:16
*** igordcard has joined #openstack-meeting-310:16
*** jamie_h has quit IRC10:17
*** jamie_h has joined #openstack-meeting-310:18
*** mrunge has quit IRC10:24
*** jamie_h_ has joined #openstack-meeting-310:29
*** mrunge has joined #openstack-meeting-310:29
*** jamie_h has quit IRC10:32
*** MaxV has quit IRC10:41
*** enykeev has quit IRC11:00
*** enykeev has joined #openstack-meeting-311:04
*** coolsvap is now known as coolsvap|afk11:04
*** MaxV has joined #openstack-meeting-311:05
*** alexpilotti has joined #openstack-meeting-311:29
*** yamahata has quit IRC11:32
*** tomoe_ has joined #openstack-meeting-311:41
*** gcb has quit IRC11:47
*** nedbat has quit IRC11:48
*** Youcef_ has joined #openstack-meeting-311:53
*** Youcef has quit IRC11:56
*** ttrifonov is now known as ttrifonov_zZzz11:56
*** ttrifonov_zZzz is now known as ttrifonov11:56
*** nedbat has joined #openstack-meeting-312:01
*** nedbat has quit IRC12:03
*** xuhanp has joined #openstack-meeting-312:23
*** mwagner_lap has quit IRC12:26
*** dhellmann has quit IRC12:28
*** mrunge has quit IRC12:32
*** HenryG has quit IRC12:53
*** alexpilotti_ has joined #openstack-meeting-312:53
*** alexpilotti has quit IRC12:54
*** alexpilotti_ is now known as alexpilotti12:54
*** jpich has joined #openstack-meeting-312:55
*** lblanchard has joined #openstack-meeting-313:03
*** yamahata has joined #openstack-meeting-313:05
*** seizadi has joined #openstack-meeting-313:06
*** amotoki_ has joined #openstack-meeting-313:06
*** julim has joined #openstack-meeting-313:06
*** mfer has joined #openstack-meeting-313:16
*** alexpilotti_ has joined #openstack-meeting-313:21
*** alexpilotti has quit IRC13:22
*** alexpilotti_ is now known as alexpilotti13:22
*** thomasem has joined #openstack-meeting-313:28
*** banix has joined #openstack-meeting-313:33
*** nedbat has joined #openstack-meeting-313:34
*** devlaps has joined #openstack-meeting-313:34
*** devlaps1 has joined #openstack-meeting-313:34
*** jackib has joined #openstack-meeting-313:35
*** peristeri has joined #openstack-meeting-313:35
*** seizadi has quit IRC13:36
*** jackib has quit IRC13:48
*** haleyb has quit IRC13:50
*** seizadi has joined #openstack-meeting-313:53
*** haleyb has joined #openstack-meeting-313:54
*** jcoufal has quit IRC14:03
*** flaviof_zzz is now known as flaviof14:20
*** dhellmann has joined #openstack-meeting-314:20
*** sankarshan_away is now known as sankarshan14:21
*** mwagner_lap has joined #openstack-meeting-314:25
*** seizadi has quit IRC14:32
*** vinay_yadhav has joined #openstack-meeting-314:34
*** vinay_yadhav has quit IRC14:34
*** jaypipes has joined #openstack-meeting-314:37
*** jaypipes has quit IRC14:39
*** jaypipes has joined #openstack-meeting-314:39
*** jaypipes has quit IRC14:41
*** jaypipes has joined #openstack-meeting-314:41
*** nelsnelson has joined #openstack-meeting-314:42
*** jaypipes has quit IRC14:44
*** jaypipes has joined #openstack-meeting-314:45
*** s1rp has joined #openstack-meeting-314:45
*** seizadi has joined #openstack-meeting-314:56
*** sgordon has joined #openstack-meeting-314:57
*** apmelton has joined #openstack-meeting-314:57
*** otherwiseguy has joined #openstack-meeting-314:57
*** vladikr has joined #openstack-meeting-314:57
*** cjellick has joined #openstack-meeting-314:57
*** cjellick has quit IRC14:57
*** cjellick has joined #openstack-meeting-314:58
*** lparth has joined #openstack-meeting-314:58
*** sew has joined #openstack-meeting-314:58
*** danpb has joined #openstack-meeting-315:00
danpb#startmeeting libvirt15:00
openstackMeeting started Tue Jun 10 15:00:33 2014 UTC and is due to finish in 60 minutes.  The chair is danpb. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: libvirt)"15:00
openstackThe meeting name has been set to 'libvirt'15:00
thomasemo/15:01
danpbwell we have no agenda items today...15:01
vladikro/15:01
apmeltono/15:01
danpbsomeone add some items if they want to talk about anything...15:01
*** chris_hunt has joined #openstack-meeting-315:01
danpb(  https://etherpad.openstack.org/p/nova-libvirt-meeting-agenda )15:01
*** jcoufal has joined #openstack-meeting-315:01
*** ndipanov has joined #openstack-meeting-315:02
ndipanovo/15:02
sewo/15:02
sgordonO/15:02
lpartho/15:02
*** jcoufal has quit IRC15:02
*** seizadi has quit IRC15:02
*** jcoufal has joined #openstack-meeting-315:03
danpb#topic open discussion15:03
*** openstack changes topic to "open discussion (Meeting topic: libvirt)"15:03
*** absubram has joined #openstack-meeting-315:03
danpbsince there are no formal  agenda items, speak now if you want to mention anything...otherwise this'll be a short meeting :-)15:04
thomasemdanpb: sew just added one about nested Docker support in Libvirt LXC containers15:04
*** HenryG has joined #openstack-meeting-315:04
sewreally just curious if anyone has been able to get nested docker to run inside libvirt lxc containers?15:04
s1rpo/15:04
danpbi've never tried it myself15:05
danpbnested containers is getting into the uncharted waters in general though15:05
sewthere seem to be cgroup differences between lxc and libvirt_lxc which cause docker layering features to fail15:06
apmeltondocker does some mounting inside of the containers it builds right?15:06
*** jtomasek has quit IRC15:06
apmeltonif we're revoking mount capability inside libvirt-lxc containers, that won't work15:07
danpbif you can get it working on lxc but not libvirt-lxc then do file bugs against libvirt - probably best to try it in plain libvirt rather than under nova15:07
s1rpapmelton: cap_sys_admin isn't dropped at least for libvirt, but for docker it is15:08
sewi do see where mknod is dropped tho:  http://libvirt.org/git/?p=libvirt.git;a=blob;f=src/lxc/lxc_container.c;h=fd8ab167f8945d33ba6f82e6f0aed84814fa98c0;hb=HEAD#l174615:08
apmeltonah yes, that's what I was thinking of15:09
sewmy testing with nested docker was done with just libvirt-1.2.315:09
sewi commented out those dropped caps, but was still unable to make docker layer images successfully15:10
vladikrdanpb, I was playing a bit with libosinfo recently, and curious what was your vision of it to be used with image properties? should everything be validated against it?15:10
sewthe only other differences i noticed were with regard to cgroup layouts15:10
danpbvladikr: so my view is that in glance we should set   os_id=<libosinfo OS identifier> and then Nova libvirt driver should use that to lookup preferred hardware models15:11
danpbvladikr: ie so it'd use virtio net for linux, e1000 for bsd or whatever libosinfo says for preferred nic15:11
danpbso it would avoid needing to set things like hw_nic_model and other similar bits in common case15:12
vladikrI see, thanks15:13
apmeltonso danpb, about the spec for user namespaces, I guess I need to get mikal to revoke his -2 on it so it can actually get approved15:14
danpbyep, guess he's missed our followup comment15:15
danpbnothing will get approved this weekend regardless though until Juno-1 is out15:15
*** jcoufal has quit IRC15:15
apmeltonyup15:15
apmeltona couple of my other patches we're pushed to J215:15
danpbok, so i guess we can finish the meeting and get back to regular work15:17
danpb#endmeeting15:17
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:17
openstackMeeting ended Tue Jun 10 15:17:36 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:17
openstackMinutes:        http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-06-10-15.00.html15:17
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-06-10-15.00.txt15:17
openstackLog:            http://eavesdrop.openstack.org/meetings/libvirt/2014/libvirt.2014-06-10-15.00.log.html15:17
*** lparth has left #openstack-meeting-315:17
*** sarob has joined #openstack-meeting-315:17
thomasemtake it easy!15:19
*** chris_hunt has left #openstack-meeting-315:22
*** jcoufal has joined #openstack-meeting-315:24
*** apmelton has left #openstack-meeting-315:25
*** xuhanp has quit IRC15:25
*** sew has left #openstack-meeting-315:25
*** vladikr has left #openstack-meeting-315:28
*** hurgleburgler has joined #openstack-meeting-315:31
*** sgordon has left #openstack-meeting-315:37
*** nacim has quit IRC15:43
*** tsufiev has joined #openstack-meeting-315:53
*** nedbat_ has joined #openstack-meeting-315:54
*** ericpeterson has joined #openstack-meeting-315:55
*** doug-fish has joined #openstack-meeting-315:55
*** tzumainn has joined #openstack-meeting-315:58
*** nedbat has quit IRC15:58
*** rdopieralski has joined #openstack-meeting-315:59
*** julim has quit IRC15:59
jpich#startmeeting Horizon16:00
openstackMeeting started Tue Jun 10 16:00:24 2014 UTC and is due to finish in 60 minutes.  The chair is jpich. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Horizon)"16:00
openstackThe meeting name has been set to 'horizon'16:00
jpichHi everyone16:00
rdopieralskihi16:00
jpichOur esteemed PTL is away so I'll be chairing the meeting this time around16:00
absubramhi16:00
hurgleburglerHi16:01
tsufievhi16:01
tzumainnhiya!16:01
*** danpb has left #openstack-meeting-316:01
ericpetersonhi16:01
*** terryw has joined #openstack-meeting-316:01
*** coolsvap|afk is now known as coolsvap16:01
*** nlahouti__ has joined #openstack-meeting-316:01
*** MaxV has quit IRC16:01
*** otherwiseguy has quit IRC16:01
jpich#link https://wiki.openstack.org/wiki/Meetings/Horizon16:01
jcoufalo/16:02
devlapso/16:02
jpichA short agenda this time around but I'm sure we'll manage to make the meeting last the full hour anyway :-)16:02
jpich#topic Juno Milestone 116:02
*** openstack changes topic to "Juno Milestone 1 (Meeting topic: Horizon)"16:02
jpich#link https://launchpad.net/horizon/+milestone/juno-116:02
*** julim has joined #openstack-meeting-316:02
jpichThe first milestone for Juno should be cut tomorrow so anything that's not approved or about to be has been moved to Juno-2 by now (if I made a mistake feel free to go ahead and correct it though)16:03
*** pballand has joined #openstack-meeting-316:04
jpichAnd speaking of Juno 2...16:04
*** emagana has quit IRC16:04
jpich#link https://launchpad.net/horizon/+milestone/juno-216:04
jpichThere's a huuuuuge list of blueprints there already16:04
jpichbut luckily a lot already have code up for review16:04
jpichIt'd be cool if people could consider reviewing the patches for a blueprint or two in their review rounds so we can start munching through the list16:05
jpichLots of people wait for Feature Freeze Proposal to propose their blueprints and miss the release because there's not enough time to review them all16:05
jpichSo let's try to merge blueprints early while we have a chance :) Thanks everyone. Review help is really greatly greatly appreciated always16:05
lblanchardo/16:05
jpichFYI according to https://wiki.openstack.org/wiki/Juno_Release_Schedule Juno-2 will likely be cut around July 22nd-24th16:06
*** otherwiseguy has joined #openstack-meeting-316:06
jpichAny related questions?16:06
nlahouti__jpich: how can the deleivery status be changed?16:07
jpichnlahouti__: Do you mean the status for a blueprint?16:07
*** gary-smith has joined #openstack-meeting-316:08
nlahouti__jpich: yes. mine shows unknown but it should be in 'needs code review'16:08
jpichnlahouti__: Oh! Do you have a link?16:08
*** jgravel has joined #openstack-meeting-316:08
jpichThe assignee should be able to do that16:08
jpichand members of the core team, and normally Gerrit does it automatically but sometimes it doesn't work...16:08
*** rhagarty_ has joined #openstack-meeting-316:09
nlahouti__jpich: sure. here it is:https://blueprints.launchpad.net/horizon/+spec/horizon-cisco-dfa-support16:09
tzumainnmight be because it's still in drafting state?16:09
jpichnlahouti__: Ok, as the assignee you should be able to change the implementation status? Can you give it a shot to see if it works?16:09
nlahouti__tzumainn: and what does it mean?16:09
*** emagana has joined #openstack-meeting-316:10
tzumainnlol, no idea, that just looked different to me : )16:10
*** terryw has quit IRC16:10
nlahouti__jpich: sure will try that.16:10
tzumainnor does it need to be approved?16:10
jpichDunno, Gerrit did add the usual "Addressed by" comments16:11
nlahouti__tzumainn: I don't know either, but it needs to be approved.16:11
jpichnlahouti__: I updated the status for now16:11
nlahouti__jpich: Thanks a lot.16:12
jpichNo problems!16:12
jpichAny other questions about milestones?16:12
*** clu_ has joined #openstack-meeting-316:12
jpich#topic How to vote for names16:13
*** openstack changes topic to "How to vote for names (Meeting topic: Horizon)"16:13
jpich#link https://etherpad.openstack.org/p/horizon-name-proposals16:13
jpichWho proposed this topic?16:13
rdopieralskime16:13
rdopieralskiso now that we have a list of names to choose from16:14
jpichCool! Consider putting your name besides the topic in the agenda :-)16:14
rdopieralskiwe should decide how to vote for them16:14
rdopieralskiyes, sorry, I forgot16:14
rdopieralskidoes anybody have their favorite poll service?16:14
rdopieralskior is there something official?16:15
clu_surkeymonkey16:15
jpichI think we've used Launchpad polls for very simple polls like that in the past16:15
jpichlike release names?16:15
* rdopieralski looks at launchpad16:15
jpichI'd recommend that 2-3 who've been involved with the work so far get together and reduce the list to 4-6 names though16:15
jpichsome of the names look a little like they were proposed by people who don't understand what part of the split we were talking about16:16
rdopieralskiI suppose the conflicting names are out right away16:16
jpichYup16:16
rdopieralskijpich: do you know how to set up a poll on launchpad?16:16
jpichThe kind folks on #openstack-infra can probably provide assistance for setting up the poll, I'm not quite sure where it is either16:16
tzumainnactually, can we address that a bit?16:16
*** jackib has joined #openstack-meeting-316:16
tzumainnbecause I know there was an option to keep horizon as horizon, and rename the dashboard instead16:17
*** crobertsrh has joined #openstack-meeting-316:17
rdopieralskitzumainn: but nobody wanted to discuss the technical details of that16:17
tzumainnwhich I was gently reminded doesn't work with the proposal to split16:17
doug-fishsorry about that - I suggested it without realizing the full impact16:17
doug-fishI think there are other reasonable options that are less troublesome16:17
rdopieralskidoug-fish: can you elaborate?16:18
jpichThere was a strong argument at some point that to everyone except the folks working on the codebase (us), "horizon" means what we call "openstack_dashboard"16:18
tzumainnjust to check then - the two benefits of naming the dashboard 'horizon' is that we reduce the impact on a bunch of infrastructure, and what jpich just said?16:18
rdopieralskitzumainn: pretty much, yes16:19
*** mxu has joined #openstack-meeting-316:20
tzumainnfair enough, I can buy that - I just remember when the naming of the tuskar ui came up, people eventually agreed that the simple solution would be the best - tripleo-ui - but that seems inconsistent with what we're doing here16:20
doug-fishI think using the horizon name to mean the actual dashboard impl and horizon_lib to mean the library is quite clear16:20
*** jaypipes has quit IRC16:20
tzumainnbut people are right, 'horizon' is established, so I don't really care that much16:20
ericpetersonsome things are also wierd.... when someone says "this is built upon horizon".....  that becomes vaugue16:20
doug-fishI'm sure that there will be other reasonable options we can vote for as well16:20
rdopieralskidoug-fish: I don't that things that have actual technical impact should be voted upon -- it usually ends up with bikeshedding16:22
jpichericpeterson: Hopefully the split/renaming will help to clarify though this may be a good argument against having "horizon" + "horizon_lib" :)16:22
clu_ericpeterson - http://docs.openstack.org/developer/horizon/topics/tutorial.html will have to change :)16:22
ericpetersonI think the confusion will be cleared up in time, it's not a huge deal16:22
doug-fishI think I'm getting confused right now16:22
rdopieralskiclu_: can you add it to https://etherpad.openstack.org/p/horizon-split-plan please?16:22
clu_rdopieralski: sure thing :)16:23
rdopieralskianother thing is how the voting shuld be done16:23
rdopieralskidoes everybody get just one vote?16:23
rdopieralskior can we pick the best, say, three?16:23
rdopieralski(it depends on what launchpad offers, of course)16:24
jpichI'd say to keep it to one to keep it simple. My question would be "who is everybody"? :-)16:24
ericpetersonit kinda depends upon how robust our voting tool might be?16:24
rdopieralskianybody who stumbles upon it :)16:24
tzumainnlol16:24
jpichrdopieralski: I think launchpad only offers "vote for the best" but if you/folks are keen on weighted voting we could maybe reuse the condorcet thingie we used for elections16:24
rdopieralskijpich: In the worst case I will just set up a wiki page, and ask people to add X-es16:24
*** jackib has quit IRC16:25
tsufievrdopieralski, i'd limit voters to the people who contributed to horizon codebase16:25
jpichrdopieralski: haha, as long as they add their nick too for tracking why not16:25
jpichtsufiev: This also affects people who build on top of us though16:25
ericpetersoncan I switch doug-fish's votes then?  ;)16:25
jpichand they are the folks that made good points like what "horizon" means to people who are not actually working on the codebase16:25
tsufievjpich, agree, didn't think of it16:25
rdopieralskitsufiev: who is going to prepare the list of such people then?16:26
doug-fishericpeterson:  only if you can figure out all of my pseudonyms!16:26
rdopieralskiericpeterson: wiki has history16:26
rdopieralskiericpeterson: which can be checked16:26
tsufievrdopieralski, afaik, the invitation to the voting for horizon PTL was sent only to contributors16:26
rdopieralskiericpeterson: also, I don't think this is such a big and important thing that anybody would cheat16:26
doug-fishagreed16:27
ericpetersonyeah, I was teasing a bit :D16:27
rdopieralskitsufiev: ok, I will ask at -infra about it too16:27
jpichI think on Launchpad folks get only one vote per LP account16:27
*** santib has joined #openstack-meeting-316:27
jpichrdopieralski: Are you happy enough you have the next steps for the name change voting?16:29
rdopieralskijpich: yes, thank you16:29
jpichCool!16:30
jpich#topic Open Discussion16:30
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"16:30
* rdopieralski is extremely happy16:30
tzumainnI have a question about common dashboard code16:30
jpichrdopieralski: I am utterly delighted to hear this16:30
tzumainnI started a thread about it on openstack-dev, got a few responses, and then had a question using concrete examples - http://lists.openstack.org/pipermail/openstack-dev/2014-June/036998.html16:30
tzumainnso I was curious if people had opinions : )16:30
tzumainnor should I just submit a patch and let people opine in that fashion?16:32
doug-fishtzumainn: its hard for me to ask this right while we are changing names ... but are you saying there are openstack_dashboard pieces that you use as building blocks?16:32
*** jaypipes has joined #openstack-meeting-316:32
jpichtzumainn: The way admin and project tables extend each other's tables probably could use some refactoring,yeah... though I don't have specific opinion as to the best way would be to go about this at this point16:32
ericpetersonyeah, there is a common pattern I think for taking something from openstack_dashboard.... and doing a slightly modified copy of that16:33
tzumainndoug-fish, yes, exactly - well, there are openstack_dashboard dashboard pieces that tripleo-ui extends, which feels peculiar16:33
tzumainnericpeterson, is there a canonical pattern I should duplicate?16:33
doug-fishdoesn't that mean that openstack_dashboard itself is part of the toolkit then?16:33
ericpetersonnot that I can think of.....   I have seen the same problem / situation16:33
*** seizadi has joined #openstack-meeting-316:34
tzumainnso david-lyle mentioned that creating openstack_dashboard/common seemed reasonable to him16:34
*** kashyap has joined #openstack-meeting-316:34
ericpetersonit's kind of like the common toolkit, then common openstack type things.... then the openstack_dashboard or tuskar ui etc16:34
tzumainnyeah, that would be excellent, but I'm not clear as to the extent that things would end up in the common toolkit16:35
*** seizadi1 has joined #openstack-meeting-316:35
*** seizadi has quit IRC16:35
mxuHi jpich: we have this BP https://blueprints.launchpad.net/horizon/+spec/horizon-cisco-dfa-support for quite a while and code patch @ https://review.openstack.org/#/c/83863/, which got some review comments. How can close the reviews and have the BPs approved?16:35
doug-fishtzumainn:  your usage makes me wonder why we are working so hard to split the components.  I know other people who want to consume dashboard panels and make only small modificaitons to them16:35
ericpetersonI think eventually the openstack_dashboard (level 3)  would be an empty file :o16:35
tzumainner, "should" end up - which is what my email asks, so just wondering if people had opinions before I just went ahead and tried something16:35
doug-fishmaybe we should treat every panel as a potential extension point16:35
tzumainnericpeterson, yeah, that was my fear as well16:35
*** pgpus has joined #openstack-meeting-316:36
*** markmcclain has joined #openstack-meeting-316:36
tsufievit code at level 2 is so common, shouldn't it be moved to level 1?16:36
tzumainndoug-fish, so in that sense, openstack_dashboard dashboard code in project and admin is both the "openstack ui" and the intended point of extension?16:36
tsufiev*if16:36
jpichtzumainn, doug-fish: There was a somewhat related blueprint proposed by Cody Sommerville after the Portland summit but I'm struggling to find it back atm, maybe someone else will have better luck16:36
rdopieralskiI have one more question about the voting16:36
doug-fishtzumainn yes16:36
rdopieralskiI need a list of e-mails of peole who are to vote -- what do you think guys would be the best way to complete it?16:37
rdopieralskijust go over the patches from the last year?16:37
ericpetersonrdopieralski: I would see if the infra group has list of contributors???16:37
ericpetersonsame as PTL votes maybe???16:38
ericpetersonwould it make sense to limit to only recent contributors???16:38
tzumainnjpich, thanks, I'll poke around a bit16:38
*** igordcard has quit IRC16:39
rdopieralskiericpeterson: they don't16:39
jpichmxu: Sorry about this, the review queue is quite large at the moment so we're behind. It'd be great to get input on the blueprint from folks more familiar with Neutron like maybe amotoki? I haven't had a chance to look at it yet, I'll try next week if no one's approved the bp yet16:39
jpichrdopieralski: So we're going only with horizon contributors then?16:39
doug-fishhttps://blueprints.launchpad.net/horizon/+spec/building-on-openstack-dashboard16:39
rdopieralskijpich: I'm open to suggestions, but I need a list of e-mails16:40
doug-fishjpich, is that the one you were thinking of? ^16:40
rdopieralskijpich: it's the easiest to get the horizon contributors at this moment16:40
amotoki_mxu: jpich: I totally forgot the horizon meeting time :-(16:40
jpichdoug-fish: That one! Thanks :D16:40
gary-smithgit shortlog -s -e    shows emails of contributor16:40
rdopieralskigary-smith: thank you!16:41
gary-smithcan be limited by time range16:41
*** emaganap has joined #openstack-meeting-316:41
amotoki_mxu: is neutron side patch of DFA merged?16:41
nlahouti__amotoki: not yet.16:42
amotoki_mxu: As we discussed in the previous meetings, we can approve the bp but the code can't be merged before merging the corresponding dependent feature.16:42
jpichrdopieralski: I think the actual query they use for generating the voters list are on the wiki on one of the governance pages16:42
mxujpich:  thanks for offering to review it!  we actually talked to amotoki at the summit and thru many emails. We are getting close to juno-2 cutoff time so really would like to close this16:42
jpichamotoki_, mxu: Oh is this the same as last week? As amotoki said, if the Neutron isn't merged the code cannot merge in Horizon16:43
*** emagana has quit IRC16:43
amotoki_jpich: mxu: i think so.16:43
jpichmxu: Note that I'm only talking about trying to understand the bp, not the code :-) Blueprint draft/approval statuses are not used all that much in horizon either way, is my impression...16:43
rdopieralskijpich: I will look for it, and if I don't find it, I will use git16:43
jpichrdopieralski: Yup it was a git query16:44
rdopieralskiah16:44
mxuamotoki:  our BP for neutron has been approved. nlahouti is going to post hist code for MD very soon. Can you please approve this Horizon BP?  We are just asking for approving the BP, not merging the code. We will merge it after we merge our neutron code. Hope this makes it clear.16:44
jpichrdopieralski: If it's a launchpad poll maybe we can use the umbrella openstack project as the allowed voter list? At least it'd be a bit larger than horizon's though I don't know who's included in that either16:45
* jpich starting to warm up again to the wiki page vote lol16:45
rdopieralskijpich: no, it's civs16:45
rdopieralskijpich: it lets you rank all entries by preference, by the way16:45
jpichOk, so people will get an email about it. I think it's fair enough to only send the email to recentish contributors rather than everyone ever16:46
jpichrdopieralski: Yeah, it's used for the people elections16:46
rdopieralskijpich: for launchpad, you need to be the group admin to start a poll16:46
rdopieralskijpich: and the groups are hopelessly out of sync with "reality"16:46
* jpich fails to open a poll16:46
jpichI see16:46
rdopieralskiso either civs or something like survemonkey16:46
rdopieralskibut I would hate to force people to signup to commercial services16:47
jpichrdopieralski: That's the link I was thinking about fwiw https://wiki.openstack.org/wiki/Election_Officiating_Guidelines#Generate_a_list_of_voters16:47
*** lblanchard has quit IRC16:48
*** mwagner_lap has quit IRC16:48
jpichmxu: Thanks for the clarification!16:48
amotoki_I would like to ask who approves blueprints. AFAIK in horizon PTL approves almost all blueprints.16:48
rdopieralskithat gives 213 addresses16:48
tzumainnout of curiosity, would an etherpad be really so terrible for voting?  or would we be expecting massive voter fraud. . . ?16:48
rdopieralskiI think it may be enough16:48
gary-smithetherpad seems like the simplest approach16:49
jpichmxu: Also please add a link in the blueprint to the dependent neutron patches so reviewers can check the statuses16:49
rdopieralskitzumainn: I was thinking about doing it on the etherpad initially, until *someone* completely derailed the name collecting16:49
mxujpich, amotoki: how can we make progress with the BP approval? It has been there for a long time.16:49
tzumainnlol, my bad16:49
rdopieralskitzumainn: then I began to have doubts about the ability of people to follow guidelines16:49
tzumainnI shall wash my neck and wait16:49
mxujpich:  will add the link soon.16:49
tzumainnI would think if you started a new etherpad with a culled list of names, send out an email saying that the time for option gathering is over, please just +1 one of the available options - that may work?16:50
ericpetersonrdopieralski : I think if we have the email list, surveymonkey or whatever would likely work... the more I think about it16:50
jpichamotoki: I think anyone in core can and should do it16:50
rdopieralskiericpeterson: it requires you to sign up16:51
rdopieralskiericpeterson: and civs is proven16:51
jpichamotoki: But we haven't so the PTL has had to pick up the slack. As long as it seems to fit I don't see a problem with approving16:51
*** thinrichs has joined #openstack-meeting-316:51
jpichI wouldn't be too keen on using etherpad for a vote but maybe I just lack faith in humanity :)16:51
amotoki_AFAIK we haven't discussed the concrete blueprint approval process so far...     I believe bleurprint approval by core team works, but it is better to be discussed in the meeting.16:51
doug-fishI promise to behave better if we use the etherpad again16:52
tzumainnjpich, no, I promise I won't commit etherpad fraud this time, unlike the previous million times16:52
gary-smithif we put our email addresses next to our vote in etherpad, it would avoid fraud16:52
gary-smiththose addresses could be filtered against the list from git16:53
tzumainnI mean, people were fairly well behaved when voting for summit sessions, right?16:53
rdopieralskiI think it would just be enough to put an * next to the names you like16:54
gary-smithoh wait, unless doug-fish changes everyone's votes. forgot about that16:54
jpichamotoki: I think spreading the load on more people is good, especially if a core is interested in helping to drive a particular blueprint. Looking at https://wiki.openstack.org/wiki/Blueprints#Blueprint_Review_Criteria any core should be equipped to do that... but I get your point, maybe we should discuss it first on list or in a meeting when the PTL is back16:54
absubram+116:54
amotoki_jpich: totally agree.16:54
tzumainnrdopieralski, I'd be fine with that16:55
*** jcoufal has quit IRC16:55
doug-fishgary-smith:  oh its not that I'm dishonest.  I just don't follow guidelines.  ericpeterson is the one you need to look out for.16:55
absubramamotoki_: not sure if you had time to read through the comments I posted in response to your review comments.. https://review.openstack.org/#/c/90093/ I tried the nice idea you suggested.. but I don't see a way without changing the test/settings.py..16:55
jpichtzumainn: I'd hope to make the poll wider known than the summit sessions vote, more people == more chances stupid16:55
ericpetersonI'm trying to find the conversion between *'s and +1's16:55
absubramamotoki_: I'm still trying to see if it is doable though.. marked it as WIP for now16:56
*** emaganap has quit IRC16:56
absubrambut please do let me know your thoughts on my comments.. whenever you are able to get a chance16:56
absubramthanks!16:56
jpichrdopieralski: civs + 1 year list of horizon contributors seems fair enough to me so that we can actually vote rather than have a vote on how to vote :-) I'll leave it in your good hands though!16:56
mxujpich, amotoki:  really appreciate it if you can have the discussions (on core folks help approving the BPs) soon as we missed the juno-1 already and time is flying16:57
*** emagana has joined #openstack-meeting-316:57
* jpich proposes averaging etherpad + wiki + LP polls results on which tool to use to vote16:57
tzumainnlol16:58
*** pgpus has quit IRC16:58
jpichmxu: Sure, but this isn't actually blocking your work, or am I missing something?16:58
amotoki_mxu: it seems your blueprint fits to Juno-2 only when considering horizon side. I think it totally depends on neutron whether it actually lands in juno-2 :-)16:59
jpichAgreed with amotoki16:59
jpichI had another exciting topic down my sleeve but it looks like it'll have to wait until next week ;) It's about time to wrap up17:00
mxujpich: again,  we are asking for BP approve so we see the agreement  from the community on our design. Our MD code will be posted for review soon.17:00
jpichThanks everyone!17:00
doug-fishwell done on filling the hour!17:00
tzumainnthanks all!17:00
jpichmxu: Ok, fair enough17:00
jpichdoug-fish: toldya17:00
jpich#endmeeting17:00
*** s3wong has joined #openstack-meeting-317:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
*** kudva has joined #openstack-meeting-317:00
openstackMeeting ended Tue Jun 10 17:00:26 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-06-10-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-06-10-16.00.txt17:00
*** ericpeterson has left #openstack-meeting-317:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-06-10-16.00.log.html17:00
*** doug-fish has left #openstack-meeting-317:00
*** tsufiev has left #openstack-meeting-317:00
*** tzumainn has left #openstack-meeting-317:00
amotoki_thanks all.17:01
thinrichsAnyone here for Congress?17:01
absubramthanks17:01
pballandyo17:01
*** gary-smith has left #openstack-meeting-317:01
sarobyup17:01
banixhi17:01
kudvahey17:01
thinrichsHi all17:01
thinrichs#startmeeting CongressTeamMeeting17:01
openstackMeeting started Tue Jun 10 17:01:38 2014 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"17:01
openstackThe meeting name has been set to 'congressteammeeting'17:01
thinrichsSo let’s start with action items from last week.17:01
thinrichskudva: how are the builtins progressing?17:02
*** jgravel has left #openstack-meeting-317:02
kudvaI completed the basic builtin with many rounds of comments from Tim17:03
*** julim has quit IRC17:03
thinrichsAnd it was merged!17:03
kudvasending  link in a minute17:03
kudvaThanks a lot!17:03
banixgreat17:04
kudvahttps://review.openstack.org/#/c/97673/17:04
kudvaSo there were more comments, especially17:04
*** jpich has quit IRC17:04
kudvaone cool thing I learned about python (storing a function in a class), and then calling it via code(*arglist): thanks Tim :)17:04
*** nlahouti__ has quit IRC17:05
kudvaBut I messed up some rebasing and so we are missing some commits in the full patch set17:05
thinrichsPython can be fun!17:05
kudvaNow the next step is to17:05
*** rajdeep has joined #openstack-meeting-317:05
*** absubram has quit IRC17:05
kudvatake a real use case where I can apply builtin17:05
rajdeephi guys17:05
kudvaI was hoping sjcazzoll would be here. the host evacuation example would be a good one (but I have others in mind as well)17:05
thinrichshi rajdeep17:06
thinrichssjcazzoll sends his regrets.17:06
kudvawhere one can combine predicates such as x > 10 (where 10 may be the number of alerts from a host)17:06
*** hurgleburgler has left #openstack-meeting-317:06
thinrichsrajdeep: we just started hearing about kudva’s progress on builtins.17:06
kudvawith other predicates17:06
rajdeepok..17:06
kudvahi rajdeep17:06
rajdeephi kudva17:07
kudvaSo my next items:17:07
kudva1. hook builtin to runtime.py17:07
thinrichskudva: sjcazzoll’s use case may very well need the builtins.  Builtins are definitely important in practice.17:07
kudva2. an example such as host evactuation with builtins (have to think if we need ceilometer integration). will craft an example17:08
*** jackib has joined #openstack-meeting-317:09
thinrichsSounds good.  I was looking into (1) today, since it requires knowledge deep into the policy engine.17:09
thinrichsI’ll let you know what I figure out.17:09
kudvaI need a bit of tutorail on runtime.py17:09
kudvaif that is possible17:09
thinrichsMay require a phone call.17:10
kudvaMainly want a quick overview of the four classes there.17:10
kudvaokay17:10
thinrichsLet me know if that’s useful for you.17:10
thinrichsLet’s move on to rajdeep.17:10
kudvaYes, it would be. Perhaps the whole team may be interested17:10
thinrichsrajdeep: how did the data source docs go?17:10
rajdeepi have added details for nova17:11
banixa hangout meeting may be useful17:11
rajdeepand got feedback from sergio17:11
thinrichskudva: I’m guessing that’s something people will only want to understand if they want to modify the policy engine.17:11
kudvaokay, I am interested for sure17:11
thinrichsAnyone who wants an overview: email me: thinrichs@vmware.com17:12
thinrichsrajdeep: sorry for the interruption.  please continue17:12
rajdeepsergio's use case needs host status which is not available in Nova17:12
rajdeeplooks like we will need to build driver for ceilometer to get that data17:13
thinrichsIt just doesn’t exist in Nova, or the driver we have doesn’t extract it?17:13
*** skn_ has joined #openstack-meeting-317:13
rajdeepit doesn't exist in nova17:13
kudvaWe can either get host status from ceilometer or monitor nova notifications17:13
kudvafor host17:13
rajdeepi checked the json returned17:13
kudvaCeilometer actually gets the host status from nova "compute-metrics-update" notifications17:14
pballandso does nova expose it on the message bus but not in REST?17:14
rajdeeplooks like17:14
skn_Oh, finally I got into this room17:14
rajdeepit exposes in message bus17:14
rajdeepshould driver be looking for message bus notifications as well?17:14
kudvaceilometer just picks up the nova notifications for host. We can get this from the notification bus or ceilometer api17:15
pballandrajdeep: that is reasonable, but how would it bootstrap initial state?17:15
banixideally the monitoring engine should do that17:15
*** seizadi1 has quit IRC17:15
thinrichscloudtoad has been working on adding the ability to listen on the usual OS message bus.17:15
pballandbanix: what do you mean by monitoring engine?  ceilometer?17:15
banixpballand: yes17:15
kudvapballand: what do you mean by bootstrap initial state?17:15
rajdeepi guess writing ceilometer driver would be cleaner design17:16
pballandkudva: if all you get are updates, what is the initial state (when congress starts after nova has been running)17:16
rajdeepso that we stick to REST17:16
thinrichsrajdeep: agreed that having a driver for ceilometer would be cleaner.17:16
rajdeepwhat do you guys think17:16
kudvapballand: ceilometer will give you a snapshot of the current situation of the metric, which it gets from notifications usually17:17
banixrajdeep: agree17:17
kudvarajdeep: agree17:17
rajdeepanother problem is the ceilometer metrics are very closely tied to kvm17:17
pballandlong term, the message bus is a more efficient means of receiving updates - but sticking with REST initially simplifies the design17:17
skn_Does ceilometer maintain the current state of the hosts?17:17
pballandrajdeep: that sounds like a blueprint for ceilometer to handle :)17:18
rajdeepe.g host status doesn't make sense if we use vCenter behind nova17:18
rajdeepskn_ : i think so it does17:18
pballandrajdeep: wouldn’t ceilometer handle that?17:18
*** HenryG has quit IRC17:19
skn_rajdeep: I meant, all vhosts, not just kvm17:19
thinrichsrajdeep: the policy engine needs to trust the data it’s given from components.  If the user doesn’t like that data, it should be reflected in the policy.17:19
skn_banix: hi, did you see my reply to your email?17:20
*** HenryG has joined #openstack-meeting-317:20
banixskn_: hi; yes17:20
*** jackib has quit IRC17:20
*** otherwiseguy has quit IRC17:20
thinrichsPerhaps this is a good transition to the use case action item.17:20
kudvaSo take an example: if I have a ceilometer plugin that monitors number of fan alerts (or some other hardware alerts), and ceilometer puts it onto notification for the collector to pick up.  How does vcenter fit into this?17:20
*** rajdeep-1 has joined #openstack-meeting-317:20
banixskn_: will respond; sorry for delay17:20
skn_banix: great, may be we can catch up on some of that at a later time this week17:21
*** rhagarty_ has quit IRC17:21
banixskn_: sounds good17:21
rajdeep-1sorry got disconnected17:21
thinrichsWe had talked about adding a list of data sources for each of the use cases.17:21
*** rhagarty has joined #openstack-meeting-317:21
thinrichsWe had also talked about solicting feedback on them.17:21
thinrichs#link https://docs.google.com/document/d/1ExDmT06vDZjzOPePYBqojMRfXodvsk0R8nRkX-zrkSw/edit#17:21
thinrichsI see there’s been a bunch of editing.17:22
thinrichssarob, skn_: want to report?17:22
skn_I was mostly looking at the specs and other docs17:22
*** rajdeep has quit IRC17:22
skn_I have some comments, not sure how to put them in17:23
*** rdopieralski has left #openstack-meeting-317:23
thinrichsHow about the usual gdoc comments?17:23
skn_thinrichs: specs that you wrote up17:23
skn_Is there a gdoc for comments?17:23
sarobi gots very typy17:23
thinrichssarob: :)17:24
sarobhmm, looking for the gdoc link17:24
sarob#link https://docs.google.com/document/d/1ExDmT06vDZjzOPePYBqojMRfXodvsk0R8nRkX-zrkSw/edit#heading=h.fbota2qx0jad17:24
thinrichsskn_: I meant go into the google doc, highlight some text you want to comment on, and (right?) click to choose to leave a comment.17:24
thinrichssarob has entered several comments on the use case doc linked above.17:25
sarobi pointed msteel and mestery at it17:25
*** markmcclain has quit IRC17:25
* mestery got it, it's on his reading list. :)17:25
sarob;)17:25
banixmestery: always alert :)17:26
mesterybanix: It's easy when it calls my name out :)17:26
sarobboth have postively replied that they are looking at17:26
thinrichssarob: great!17:26
skn_thinrichs: I meant the congress’ nova-like specs17:26
thinrichsskn_: oh—I’d leave a comment in gerritt.17:26
sarobisnt the user stories to turn into specs into blueprints?17:27
sarobjust sayin17:27
skn_sarob: are we planning to merge the specs that tthinrichs wrote up with the user stories17:27
*** nedbat has joined #openstack-meeting-317:27
sarobroger roger17:28
banixblueprint if need to track with milestones, etc17:28
thinrichsCan someone explain the diff between a nova-spec and a blueprint?17:28
*** emaganap has joined #openstack-meeting-317:28
thinrichsOther than they live in different places w/ diff formats.17:29
kudvathinrichs: can we take the host evacuation example or one use case and deep dive for that, so we can see the difference17:29
banixi think the spec is better for keeping track of reviews and updating while blueprint has other features such as milestones17:29
*** emaganap has quit IRC17:29
*** markmcclain has joined #openstack-meeting-317:29
banixso the need to kinf of use both until something better with all features is available17:29
*** nedbat_ has quit IRC17:30
*** carl_baldwin has joined #openstack-meeting-317:30
pballandkudva: +117:31
pballandI agree it would be helpful to take one story all the way thorugh17:31
pballandthrough17:31
*** emagana has quit IRC17:31
*** emagana has joined #openstack-meeting-317:31
skn_thinrichs: for data sources, can we also get some from other policy project, e.g. neutro GBP?17:31
pballandshall we start with host evacuation?17:31
kudvarajdeep, pballand: since have a few people interested in host evacuation (including sjcazzoll), I second that.17:32
kudvafor one deep dive. We can have more than one (say neutron GBP example)17:32
thinrichsskn_: get some what?17:32
skn_data sources from other “policy” projects, in addition to the core OS components like nova?17:33
rajdeep-1skn_ : we could write a driver for neutro GBP17:33
thinrichsskn_: I don’t think the other policy projects are writing the same kinds of drivers we are to import data.17:33
rajdeep-1but it is not prioritized17:33
rajdeep-1looks like exploring a driver for ceilometer would make sense17:34
thinrichsBut as rajdeep-1 says we could write drivers for any collection of APIs.17:34
skn_rajdeep-1: one idea we discussed earlier was to work with the other policy projects too, to enforce things.17:34
thinrichsIn terms of writing new drivers we want to prioritize based on use-case prioritization.  Which is why it’s important to know which use cases utilize which data sources.17:35
rajdeep-1sure thinrichs : what do you suggest17:35
kudvarajdeep-1: I can work with you on the ceilometer driver if we decide to pursue it. Would like to understand better how the drivers are implemented.17:35
skn_For use case prioritization, we should probably take one from each categories of use cases17:35
rajdeep-1kudva : that is great17:36
pballandI think thinrichs is saying that we need more clarity of the required data for each use case17:36
pballandhaving that would help drive data source development17:37
*** amotoki_ has quit IRC17:37
skn_Let’s start a deep dive on something then17:37
skn_it’ll help us understand better17:38
thinrichsOnce we have data source drivers needed for a use case, we just write the policy for that use case.17:38
thinrichsSo there’s (hopefully) no development to do once we have the data source drivers in place.17:38
thinrichsPerhaps we should add our basic example to the use case doc, along with the data sources needed, and the policy so that we can all see what technical info we need.17:38
thinrichsI’ll volunteer to do that.17:38
banixthinrichs: that’s a good idea17:39
pballandso for the evacuation use case, what data sources do people envision the policy referencing?17:39
thinrichs#action thinrichs will add private/public network example to use case doc17:39
skn_thinrichs: how does the action happen, if its needed? Data sources is one way from the drivers to the Congress, sounds like17:39
thinrichsskn_: we’re working on monitoring first.  Then we’ll work on enforcement (adding actions).  I imagine we can talk about just monitoring for almost all of our use cases.17:40
kudvapballand: not sure what sjcazzoll had in mind. But in general, the host will be evacuated if there are a high number of failures on the host. So a ceilometer plugin on the host or nova notification from the hosts are picked up by ceilometer.17:41
kudvaSo, we need to get some data from ceilometer on this to say if it's time to evacuate.17:41
kudvawe may have a threshold on a policy: host_owner, and faults> x and any other conditions17:41
skn_thinrichs: but most of the use cases make sense only if we have some action, right?17:41
pballandpossible evacuation sources that come to mind: nova:host->vm bindings, ceilometer: metrics on hosts and networks17:41
thinrichsskn_: Let’s put it this way.  The action mechanism we’ll use is independent of the use cases.  So once we get it in, we can execute actions.17:42
skn_thinrichs: Agreed17:42
pballandmonitoring is a precursor to actions - the first way to “execution” actions is “tell the admin to fix it"17:42
kudvapballand: what do you mean by>? host->vm bindings, and metrics on hosts and networks?17:43
thinrichsBut until we have monitoring in place, we can’t be executing actinos.  So the use cases aren’t driving those features.17:43
thinrichsThe use cases are only driving the development of data sources.17:43
pballandkudva: sorry I’m not being clear - I mean we need host:vm bindings, and that would come from nova, and we also need additional metrics that would likely come form ceilometer17:44
skn_thinrichs: OK, got iit.  The priority now is to have data source developments, e.g. via drivers17:44
kudvapballand: got it17:44
thinrichsskn_: Use cases/stories are important for 2 reasons: to drive technical development and to help explain why the project is useful to people.17:45
skn_I can work on the data sources in the security use cases that I’ve added17:45
thinrichsFor technical development, the use cases are only helping prioritize data source development.17:45
thinrichsBut independently we need to push on policy engine/action execution development17:45
thinrichsskn_: great!17:45
thinrichsskn_: rajdeep is the expert on datasource driver development.17:46
thinrichsSpeaking of which I’m making progress on integration of datasources, policy engine, and DSE.17:46
thinrichsAnd there are a number of small changes to the datasource drivers we have.17:46
skn_I meant, I can start with putting the info on doc and then take it from there17:47
banixthinrichs: link? if the code is out there17:47
thinrichsskn_: got it.17:47
thinrichsStarting at:17:47
thinrichshttps://review.openstack.org/#/c/95965/717:47
thinrichsEnding at:17:47
thinrichshttps://review.openstack.org/#/c/96978/17:47
skn_Rajdeep: I can take some help in understanding what all data sources do we already have (or in plan) for Congress17:47
thinrichsThe very last change in the series is unfinished (and the commit msg says so).  Don’t bother reviewing that one yet.17:48
banixthinrichs: thanks17:48
thinrichsBut the others are ready for review.17:48
rajdeep-1sure skn_17:48
rajdeep-1currently nova and neutron drivers are implemented17:48
thinrichsI’ll go through and add reviewers for the ones who I know.17:48
rajdeep-1https://github.com/stackforge/congress/tree/master/congress/datasources17:49
skn_rajdeep: oh ok. thanks.17:49
kudvarajdeep-1: how do you plan to start ceiometer integration17:49
thinrichsI know pballand is swamped.  So if everybody could pitch in and do some reviewing, that would help.17:49
skn_isn’t dereck@plexxi doing something along this line?17:49
banixthinrichs: will do17:50
skn_thinrichs: sure17:50
thinrichsskn_: cloudtoad isn’t doing this kind of integration.  I talked to him yesterday.17:50
rajdeep-1kudva : i will look at what ceilometer has and come up with a design doc17:50
skn_thinrichs: I see17:50
kudvarajdeep-1: okay let me know, thanks17:51
skn_OK, so looks like two actions on me, 1. review data source code, and 2. add some data sources needed for the security use cases17:52
thinrichsskn_: yes—thankyou!17:52
skn_thinrichs: feel free to put these in actions17:52
thinrichs#action skn_ will add data sources to the use case doc17:53
pballandskn_: just to be clear, by 2) - do you mean update the use case doc, or or actually work on the data sources?17:53
skn_update the doc17:53
skn_we have to first get that done17:53
thinrichs#action skn_, banix, (and others who have time) will review thinrichs code changes17:53
thinrichsTime check: 5 mins left.17:54
thinrichsOpen discussion17:54
skn_any plans on the blueprint?17:54
thinrichsWe had talked about working thru host evac from Story to spec and blueprint.17:55
*** rm_work|away is now known as rm_work17:55
thinrichsAnyone want to work on that?17:55
skn_thinrichs: Is it per use cases? I thought we are going to put in multiple of them together17:56
thinrichsLooking into whether we can post blueprints.  Anyone know how we can add Congress as a blueprint project?17:57
skn_sarob: are you there?17:57
sarobhere17:57
thinrichssarob: do you know how we get Congress added as a project when creating a new blueprint?17:58
skn_sarob: Any ideas on how to add congress as a blueprint project?17:58
sarobvery17:58
thinrichssarob:???17:58
sarobyou mean incubated right?17:58
sarobim working on incubating training-guides as well17:59
sarobso i gots the skinny17:59
pballanddoes Congress need to be inclubated before it can be listed as a project for blueprints?17:59
sarobnope17:59
*** seizadi has joined #openstack-meeting-317:59
skn_ok, then we start with blueprints and then work on getting it incubated, right?17:59
sarobgeneral practice now is repo spec patches then blueprints17:59
pballandI’ll volunteer to research how to get congress listed as a project when creating blueproints18:00
sarobwe following that so good and good18:00
sarobah, create a launchpad project?18:00
skn_pballand: thanks18:00
sarobi can do that for you18:00
sarobwith you18:00
pballandsarob: ah - sweet!18:00
thinrichs#action sarob will add Congress as a launchpad project18:00
thinrichsAnd we’re out of time.18:00
thinrichsThanks all!  Follow up on the ML if need be.18:01
sarobdone18:01
skn_Bye guys18:01
thinrichssarob: sweet!18:01
banixbye18:01
*** kudva has quit IRC18:01
thinrichs#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
saroblater18:01
openstackMeeting ended Tue Jun 10 18:01:21 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-06-10-17.01.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-06-10-17.01.txt18:01
rajdeep-1bye18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-06-10-17.01.log.html18:01
*** skn_ has left #openstack-meeting-318:01
*** rajdeep-1 has quit IRC18:01
*** emagana has quit IRC18:02
*** emagana has joined #openstack-meeting-318:03
*** jaypipes has quit IRC18:03
*** emagana has quit IRC18:08
*** emagana has joined #openstack-meeting-318:08
*** mrunge has joined #openstack-meeting-318:11
*** seizadi has quit IRC18:14
*** mrunge has quit IRC18:15
*** seizadi has joined #openstack-meeting-318:15
*** thinrichs has quit IRC18:16
*** coolsvap is now known as coolsvap|afk18:17
*** dlenrow has joined #openstack-meeting-318:17
*** lenrow has quit IRC18:20
*** safchain has quit IRC18:29
*** gduan has joined #openstack-meeting-318:30
*** garyduan has quit IRC18:31
*** emagana has quit IRC18:34
*** nati_ueno has joined #openstack-meeting-318:35
*** emagana has joined #openstack-meeting-318:37
*** gduan has quit IRC18:41
*** garyduan has joined #openstack-meeting-318:42
*** igordcard has joined #openstack-meeting-318:43
*** nedbat has quit IRC18:44
*** nedbat has joined #openstack-meeting-318:44
*** catherine_d has joined #openstack-meeting-318:45
*** catherine_d has left #openstack-meeting-318:45
*** seizadi has quit IRC18:45
*** seizadi has joined #openstack-meeting-318:45
*** nedbat_ has joined #openstack-meeting-318:46
*** nedbat_ has quit IRC18:46
*** nedbat_ has joined #openstack-meeting-318:46
*** nedbat has quit IRC18:49
*** pballand has quit IRC18:50
*** markmcclain has quit IRC18:56
*** Alex_Gaynor has joined #openstack-meeting-318:57
*** nati_ueno has quit IRC18:57
*** gduan has joined #openstack-meeting-318:59
*** garyduan has quit IRC19:00
briancurtin#startmeeting python-openstacksdk19:01
openstackMeeting started Tue Jun 10 19:01:08 2014 UTC and is due to finish in 60 minutes.  The chair is briancurtin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:01
openstackThe meeting name has been set to 'python_openstacksdk'19:01
*** jamielennox has joined #openstack-meeting-319:01
*** terrylhowe has joined #openstack-meeting-319:01
briancurtin#info agenda at https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK#Agenda_for_2014-06-10_1900_UTC19:02
briancurtinIf you're here for the python-openstacksdk meeting, say hi19:02
briancurtinBrian Curtin, Rackspace19:02
Alex_GaynorAlex Gaynor, Rackspace19:02
terrylhoweTerry Howe, HP19:02
edleafeEd Leafe, Rackspace19:03
jamielennoxJamie Lennox, Red Hat19:03
jamielennoxhi19:03
*** garyduan has joined #openstack-meeting-319:03
Alex_Gaynorjamielennox: isn't it like midnight for you? That's dedication!19:03
*** gduan has quit IRC19:03
jamielennoxAlex_Gaynor: 5am, and 2nd of the day19:04
briancurtin#topic https://review.openstack.org/#/c/98917/ - Important auth fixes19:04
*** openstack changes topic to "https://review.openstack.org/#/c/98917/ - Important auth fixes (Meeting topic: python-openstacksdk)"19:04
briancurtinso that review is the root of a few of the example changes, so i figure start with that. it's fairly small, only i've reviewed it though19:04
jamielennoxterrylhowe: do yoy have a need for passing **kwargs through on get_token?19:06
jamielennox#link https://review.openstack.org/#/c/98917/1/openstack/auth/identity/base.py19:06
Alex_GaynorJust did a quick review, it looks fine to me, besides the comment I left.19:06
Alex_GaynorIf someone replies to that I'm sure we can have that merged before the meeting ends19:07
*** sarob has quit IRC19:07
terrylhowejamielennox: I don’t have a need right now, but figured there might be a possibliity the transport would need it19:07
*** emaganap has joined #openstack-meeting-319:07
jamielennoxif so then no problem, i'm pretty sure i didn't pass kwargs through there on purpose but if you've come across a case then i'm happy to go with it19:07
jamielennoxok, can i recommend being really careful passing **kwargs around like that because it can become a real pain to maintain compatability in the future19:08
Alex_Gaynor==jamielennox19:09
*** nati_ueno has joined #openstack-meeting-319:09
terrylhowethat is fine, looking at session right now, and it doesn’t pass in kwargs at the moment19:10
*** emagana has quit IRC19:10
jamielennoxin the ksc case most of using **kwargs was just a sink that would ignore params it didn't understand yet19:11
terrylhoweI’d be okay with removing kwargs from those guys if everyone feels that is best19:12
briancurtinyeah, that sounds best19:12
*** emagana has joined #openstack-meeting-319:12
jamielennoxterrylhowe: ++19:12
jamielennoxeasy to add back if a case ever comes up19:13
terrylhowecool19:13
briancurtinyep. seems like a better idea to know for sure that we need them, so +119:13
briancurtin#action Terry will remove the kwargs, should be good to go at that point19:14
briancurtin#topic https://review.openstack.org/#/c/97829/ - Example code reorg and auth examples19:14
*** openstack changes topic to "https://review.openstack.org/#/c/97829/ - Example code reorg and auth examples (Meeting topic: python-openstacksdk)"19:14
briancurtinhmm, Dean isn't here - he -2'ed this one19:14
terrylhowewell, he -2ed the previous patch19:15
terrylhoweI think I’ve addressed his concerns19:15
*** emaganap has quit IRC19:15
briancurtini think so as well, just wondered if he was around to take a look yet19:16
jamielennoxi'm good with that one19:17
briancurtinEd brings up a good point about where the examples are aimed at, but i put that as an item to talk about generally at the end19:19
briancurtinother than that, i think this is probably good to move on, and Dean can chime in whenever19:19
briancurtin#topic https://review.openstack.org/#/c/98524/ - Example session command19:19
*** openstack changes topic to "https://review.openstack.org/#/c/98524/ - Example session command (Meeting topic: python-openstacksdk)"19:19
briancurtinAt the top of it all, this change is now much more slimmed down as things have moved into those other reviews. i +2ed this latest set19:20
jamielennox+2 as well19:22
*** amotoki has quit IRC19:22
briancurtin#topic: identifying example audiences19:25
*** openstack changes topic to ": identifying example audiences (Meeting topic: python-openstacksdk)"19:25
terrylhoweI kind of like the super simple examples and allow the devs to jump in try out whatever they like19:26
terrylhoweI just want to create something and see it work in some basic way19:27
*** sarob has joined #openstack-meeting-319:27
terrylhoweedleafe: and perhaps Dean feel differently19:27
briancurtinedleafe: is there anything at the moment we should change?19:27
Alex_GaynorRight now I've just been treating examples as "for internal consumption" not for any sort of end users19:27
edleafeYeah, what Alex said19:28
briancurtinin general I kind of like when an example gives somewhat of a 'user story', but i dont know if we're at the point now where we have many user stories besides internal devs19:28
edleafeI don't really see the benefit of example code for internal devs19:28
edleafeBDD, anyone?  ;-)19:28
edleafeWe're writing a tool to make devs' lives simpler and easier19:29
edleafeIf I came in cold and saw a bunch of examples that dove deep into the internals, I'd figure that this wasn't the sort of SDK I needed.19:30
jamielennoxi think the examples reflect the deep internals because that's really all we have at the moment19:30
edleafeThen why are we spending time on them instead of getting closer to an MVP?19:31
jamielennoxas we get higher level we obviously add those examples but i don't see a problem with examples for like the session object because the intent is not to hide that from people19:31
*** Sukhdev has joined #openstack-meeting-319:31
*** santib has left #openstack-meeting-319:31
briancurtinedleafe: i dont think we're going to end up with one directory containing all levels of example code, from internals to "i want to use swift"19:31
Alex_GaynorEventually I would expect that the examples for end users would be in the docs/ directory :-)19:32
briancurtinyep. this is just another thing that will grow to fit the needs as this continues on. maybe this dir eventually becomes /internals/examples, who knows19:33
edleafejamielennox: I don't think you should hide it, but if your examples feature it, that's what users will think is the way to use the SDK19:33
terrylhowewell, examples are for SDK devs or SDK users?19:34
edleafebriancurtin: why do internal devs need examples??19:34
briancurtinso they can write code?19:34
briancurtinso they can build thigns?19:34
briancurtinwhat are we hired for?19:34
*** jtomasek has joined #openstack-meeting-319:34
jamielennoxedleafe: because at some point i expect the various services to start chipping in there own features, so there is a need for them to understand how the library works19:35
briancurtinif i want to know how to quickly setup a session but my goal is like 10 things away from dealing with session stuff, i might just want a quick piece of code to show me so i can get on with my job19:35
edleafeI always thought that's what the code itself, including tests, was supposed to do19:35
jamielennoxnot being argumentative, i think the examples will grow until the point where we need to figure them out, but there is reason for both19:36
Alex_GaynorI suspect some of this will go away as we have examples of how to add a service, but without the examples how would the first person know how to add (say) swift suport?19:36
Alex_GaynorI hope these can eventually just be replaced with the code itself.19:36
Alex_GaynorBut there's a chicken/egg thing I think19:36
edleafeAlex_Gaynor: that's a code smell to me19:36
terrylhoweThis has been a very confusing discussion19:39
*** Sukhdev has quit IRC19:40
briancurtinso we're making a bunch of code and people need to know how to use it: examples seem fine to me19:40
*** emagana has quit IRC19:41
edleafeMy only concern is that, based on experience, if you have example code, newcomers to the SDK will look at those and pattern their work on that19:41
briancurtinso we should identify what the examples are aimed at19:41
*** emagana has joined #openstack-meeting-319:41
edleafeBut if no one else feels that that could be an issue, so be it19:41
*** sarob has quit IRC19:42
terrylhoweedleafe: that is definitely true19:42
*** emagana has quit IRC19:42
briancurtini don't think we're going to put this current example on the rackspace site and have our customers building things like this - it's going to live in the repo for us in this meeting19:42
*** emagana has joined #openstack-meeting-319:43
*** peristeri has quit IRC19:44
*** peristeri has joined #openstack-meeting-319:46
*** nedbat_ has quit IRC19:46
*** nedbat has joined #openstack-meeting-319:47
*** nedbat has quit IRC19:47
briancurtini think this is just a bridge we'll cross when we get to it. for now we just document and examplement (that's a new word) what we have and enable people to build on what's available19:47
*** nedbat has joined #openstack-meeting-319:47
terrylhowesounds good to me19:48
jamielennox+119:48
briancurtin#topic building out resouces19:48
*** openstack changes topic to "building out resouces (Meeting topic: python-openstacksdk)"19:48
briancurtini was at two conferences and in transit to and from russia for a while, so i haven't really hacked on much, so i have nothing to add here...but does anyone else?19:49
terrylhoweI’ve done a little work on a glance image resource, it needs lots more19:49
terrylhoweI should have something rough sometime this week19:50
briancurtincool. i'm going to start poking around as well, likely swift19:51
briancurtin4 min left, anything else to add?19:56
Alex_GaynorSeems like no, thanks everybody!19:57
* Alex_Gaynor -> lunch19:57
*** Alex_Gaynor has left #openstack-meeting-319:57
edleafec ya!19:58
briancurtin#action Terry working on Glance resource, Brian on Swift19:58
briancurtinthanks all19:58
*** devlaps has quit IRC19:59
*** devlaps1 has quit IRC19:59
briancurtin#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:59
openstackMeeting ended Tue Jun 10 19:59:25 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-06-10-19.01.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-06-10-19.01.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-06-10-19.01.log.html19:59
*** devlaps has joined #openstack-meeting-320:00
*** jaypipes has joined #openstack-meeting-320:00
*** pballand has joined #openstack-meeting-320:02
*** markmcclain has joined #openstack-meeting-320:02
*** terrylhowe has left #openstack-meeting-320:07
*** nati_ueno has quit IRC20:11
*** mxu has quit IRC20:13
*** crobertsrh has left #openstack-meeting-320:15
*** nati_ueno has joined #openstack-meeting-320:19
*** peristeri has quit IRC20:20
*** jamie_h has joined #openstack-meeting-320:23
*** jamie_h_ has quit IRC20:25
*** seizadi has quit IRC20:31
*** jrist has quit IRC20:33
*** dachary has quit IRC20:33
*** ryanpetrello has quit IRC20:33
*** Sukhdev has joined #openstack-meeting-320:33
*** jrist has joined #openstack-meeting-320:33
*** ryanpetrello has joined #openstack-meeting-320:33
*** dachary has joined #openstack-meeting-320:34
*** s3wong_ has joined #openstack-meeting-320:37
*** sarob has joined #openstack-meeting-320:38
*** peristeri has joined #openstack-meeting-320:39
*** dhellmann_ has joined #openstack-meeting-320:41
*** sarob has quit IRC20:43
*** peristeri has quit IRC20:44
*** HenryG has quit IRC20:45
*** peristeri has joined #openstack-meeting-320:45
*** devlaps1 has joined #openstack-meeting-320:45
*** dhellmann_ has quit IRC20:48
*** dhellmann_ has joined #openstack-meeting-320:48
*** mrunge has joined #openstack-meeting-320:48
*** seizadi has joined #openstack-meeting-320:53
*** seizadi1 has joined #openstack-meeting-320:54
*** lsmola__ has joined #openstack-meeting-320:54
*** jamie_h has quit IRC20:54
*** devlaps has quit IRC20:54
*** nedbat has quit IRC20:54
*** s3wong has quit IRC20:54
*** dhellmann has quit IRC20:54
*** Youcef_ has quit IRC20:54
*** coolsvap|afk has quit IRC20:54
*** lsmola_ has quit IRC20:54
*** dhellmann_ is now known as dhellmann20:54
*** nati_ueno has quit IRC20:56
*** dhellmann has quit IRC20:56
*** s3wong_ is now known as s3wong20:57
*** seizadi has quit IRC20:57
*** nedbat has joined #openstack-meeting-320:58
*** nati_ueno has joined #openstack-meeting-321:05
*** pballand has quit IRC21:05
*** mwagner_lap has joined #openstack-meeting-321:06
*** pballand has joined #openstack-meeting-321:08
*** rockyg has joined #openstack-meeting-321:10
*** Youcef_ has joined #openstack-meeting-321:11
*** coolsvap|afk has joined #openstack-meeting-321:11
*** nati_ueno has quit IRC21:15
*** nedbat has quit IRC21:19
*** nedbat has joined #openstack-meeting-321:19
*** nedbat has quit IRC21:23
*** nedbat has joined #openstack-meeting-321:23
*** banix has quit IRC21:24
*** jaypipes has quit IRC21:26
*** jaypipes has joined #openstack-meeting-321:28
*** rockyg has left #openstack-meeting-321:31
*** mfer has quit IRC21:32
*** jtomasek has quit IRC21:32
*** jtomasek has joined #openstack-meeting-321:32
*** nati_ueno has joined #openstack-meeting-321:35
*** jaypipes has quit IRC21:37
*** sarob has joined #openstack-meeting-321:38
*** sarob has quit IRC21:43
*** thomasem has quit IRC21:46
*** dhellmann has joined #openstack-meeting-321:55
*** nedbat has quit IRC21:56
*** mrunge has quit IRC21:56
*** nedbat has joined #openstack-meeting-322:04
*** nedbat has quit IRC22:05
*** nati_ueno has quit IRC22:14
*** jtomasek has quit IRC22:20
*** MaxV has joined #openstack-meeting-322:23
*** peristeri has quit IRC22:25
*** MaxV has quit IRC22:28
*** Sukhdev has quit IRC22:29
*** Sukhdev has joined #openstack-meeting-322:29
*** MaxV has joined #openstack-meeting-322:29
*** MaxV has quit IRC22:29
*** thomasem has joined #openstack-meeting-322:31
*** nati_ueno has joined #openstack-meeting-322:32
*** gduan has joined #openstack-meeting-322:34
*** garyduan has quit IRC22:34
*** seizadi1 has quit IRC22:36
*** ttrifonov is now known as ttrifonov_zZzz22:37
*** sarob has joined #openstack-meeting-322:38
*** sarob has quit IRC22:42
*** igordcard has quit IRC22:50
*** pballand has quit IRC23:02
*** nati_ueno has quit IRC23:10
*** emagana has quit IRC23:22
*** sarob has joined #openstack-meeting-323:38
*** sarob has quit IRC23:43
*** seizadi has joined #openstack-meeting-323:46
*** yamahata has quit IRC23:46
*** tomoe__ has joined #openstack-meeting-323:47
*** lcheng has quit IRC23:49
*** tomoe_ has quit IRC23:50
*** tomoe__ has quit IRC23:51
*** tomoe_ has joined #openstack-meeting-323:51
*** cjellick has quit IRC23:59
*** cjellick has joined #openstack-meeting-323:59

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