Thursday, 2013-12-05

*** rongze has quit IRC00:02
*** rnirmal has joined #openstack-meeting-alt00:04
*** jmontemayor has quit IRC00:04
*** ashaikh has quit IRC00:06
*** noslzzp has quit IRC00:06
*** sarob has quit IRC00:11
*** sarob has joined #openstack-meeting-alt00:11
*** ashaikh has joined #openstack-meeting-alt00:11
*** rnirmal has quit IRC00:15
*** kgriffs is now known as kgriffs_afk00:16
*** sarob has quit IRC00:16
*** esker has joined #openstack-meeting-alt00:27
*** brents has quit IRC00:27
*** ashaikh has quit IRC00:29
*** ashaikh has joined #openstack-meeting-alt00:30
*** esker has quit IRC00:31
*** devkulkarni has quit IRC00:32
*** brents has joined #openstack-meeting-alt00:36
*** ashaikh has quit IRC00:43
*** MarkAtwood has quit IRC00:44
*** sacharya has joined #openstack-meeting-alt00:45
*** ashaikh has joined #openstack-meeting-alt00:48
*** bill_az has quit IRC00:58
*** colinmcnamara has quit IRC01:00
*** colinmcn_ has quit IRC01:00
*** markwash has quit IRC01:03
*** yogesh has joined #openstack-meeting-alt01:03
*** IlyaE has quit IRC01:09
*** yogesh has quit IRC01:10
*** yogesh has joined #openstack-meeting-alt01:11
*** brents has quit IRC01:12
*** yogesh has quit IRC01:15
*** devkulkarni has joined #openstack-meeting-alt01:19
*** devkulkarni has quit IRC01:20
*** demorris has joined #openstack-meeting-alt01:21
*** flaper87 is now known as flaper87|afk01:22
*** sballe has quit IRC01:24
*** twoputt__ has quit IRC01:24
*** twoputt_ has quit IRC01:24
*** esker has joined #openstack-meeting-alt01:27
*** rongze has joined #openstack-meeting-alt01:28
*** amcrn has quit IRC01:29
*** esker has quit IRC01:32
*** rongze has quit IRC01:33
*** mozawa has joined #openstack-meeting-alt01:34
*** tanisdl has quit IRC01:35
*** nosnos has joined #openstack-meeting-alt01:36
*** gokrokve has joined #openstack-meeting-alt01:40
*** ashaikh has quit IRC01:43
*** flwang has quit IRC01:49
*** alazarev has quit IRC01:56
*** ashaikh has joined #openstack-meeting-alt02:01
*** boris-42 has quit IRC02:02
*** ashaikh has quit IRC02:04
*** bdpayne has quit IRC02:05
*** alazarev has joined #openstack-meeting-alt02:07
*** demorris has quit IRC02:10
*** markwash has joined #openstack-meeting-alt02:10
*** demorris has joined #openstack-meeting-alt02:10
*** openstack has joined #openstack-meeting-alt02:17
*** ChanServ sets mode: +o openstack02:17
*** esker has joined #openstack-meeting-alt02:27
*** esker has quit IRC02:32
*** alazarev has quit IRC02:32
*** esker has joined #openstack-meeting-alt02:34
*** jcooley_ has joined #openstack-meeting-alt02:35
*** esker has quit IRC02:35
*** esker has joined #openstack-meeting-alt02:36
*** yahongdu has quit IRC02:38
*** eankutse has joined #openstack-meeting-alt02:39
*** yahongdu has joined #openstack-meeting-alt02:39
*** RajeshMohan has quit IRC02:43
*** DennyZhang has joined #openstack-meeting-alt02:46
*** banix has joined #openstack-meeting-alt02:46
*** flwang has joined #openstack-meeting-alt02:50
*** rongze has joined #openstack-meeting-alt02:53
*** rongze_ has joined #openstack-meeting-alt02:55
*** rongze has quit IRC02:58
*** IlyaE has joined #openstack-meeting-alt03:00
*** yahongdu has quit IRC03:00
*** yahongdu has joined #openstack-meeting-alt03:03
*** HenryG has quit IRC03:11
*** jcooley_ has quit IRC03:17
*** markwash has quit IRC03:18
*** eankutse has quit IRC03:25
*** NehaV has joined #openstack-meeting-alt03:26
*** zhiyan has joined #openstack-meeting-alt03:28
*** resker has joined #openstack-meeting-alt03:33
*** banix has quit IRC03:33
*** esker has quit IRC03:35
*** banix has joined #openstack-meeting-alt03:37
*** IlyaE has quit IRC03:40
*** DennyZhang has quit IRC03:42
*** DennyZha` has joined #openstack-meeting-alt03:43
*** IlyaE has joined #openstack-meeting-alt03:43
*** sarob has joined #openstack-meeting-alt03:45
*** alazarev has joined #openstack-meeting-alt03:56
*** jjmb has joined #openstack-meeting-alt03:57
*** coolsvap has joined #openstack-meeting-alt04:15
*** banix has quit IRC04:26
*** MarkAtwood has joined #openstack-meeting-alt04:30
*** rongze_ has quit IRC04:35
*** rraja has joined #openstack-meeting-alt04:36
*** IlyaE has quit IRC04:36
*** IlyaE has joined #openstack-meeting-alt04:38
*** IlyaE has quit IRC04:40
*** markwash has joined #openstack-meeting-alt04:45
*** rraja has quit IRC04:51
*** amotoki has joined #openstack-meeting-alt04:53
*** sarob has quit IRC04:59
*** brents has joined #openstack-meeting-alt05:00
*** demorris has quit IRC05:02
*** amytron has joined #openstack-meeting-alt05:06
*** aratim has joined #openstack-meeting-alt05:13
*** aratim has quit IRC05:15
*** NehaV has quit IRC05:15
*** zhiyan has quit IRC05:19
*** DennyZha` has quit IRC05:24
*** sarob has joined #openstack-meeting-alt05:27
*** sarob has quit IRC05:28
*** yahongdu has quit IRC05:28
*** sarob has joined #openstack-meeting-alt05:28
*** sarob has quit IRC05:30
*** sarob has joined #openstack-meeting-alt05:32
*** sarob has quit IRC05:33
*** sarob has joined #openstack-meeting-alt05:34
*** yahongdu has joined #openstack-meeting-alt05:38
*** sarob has quit IRC05:39
*** brents has quit IRC05:46
*** IlyaE has joined #openstack-meeting-alt05:52
*** brents has joined #openstack-meeting-alt05:53
*** yamahata_ has quit IRC05:55
*** DennyZha` has joined #openstack-meeting-alt05:57
*** DennyZha` has quit IRC06:01
*** rraja has joined #openstack-meeting-alt06:05
*** noslzzp has joined #openstack-meeting-alt06:09
*** csaba|afk is now known as csaba06:20
*** bdpayne has joined #openstack-meeting-alt06:26
*** sacharya has quit IRC06:26
*** jjmb has quit IRC06:29
*** nadya has joined #openstack-meeting-alt06:29
*** nadya is now known as Guest169006:29
*** ashaikh has joined #openstack-meeting-alt06:30
*** Guest1690 has quit IRC06:34
*** jjmb has joined #openstack-meeting-alt06:38
*** brents has quit IRC06:41
*** gokrokve has quit IRC06:49
*** noslzzp has quit IRC06:52
*** rongze has joined #openstack-meeting-alt06:54
*** akuznetsov has quit IRC06:55
*** brents has joined #openstack-meeting-alt06:57
*** IlyaE has quit IRC06:59
*** IlyaE has joined #openstack-meeting-alt07:00
*** bdpayne has quit IRC07:02
*** ashaikh has quit IRC07:02
*** ashaikh has joined #openstack-meeting-alt07:04
*** jjmb has quit IRC07:09
*** SergeyLukjanov has joined #openstack-meeting-alt07:12
*** amytron has quit IRC07:14
*** denis_makogon has joined #openstack-meeting-alt07:15
*** kmsWork_ has joined #openstack-meeting-alt07:17
*** kmsWork has quit IRC07:19
*** jjmb has joined #openstack-meeting-alt07:20
*** akuznetsov has joined #openstack-meeting-alt07:23
*** nati_ueno has quit IRC07:24
*** akuznetsov has quit IRC07:26
*** brents has quit IRC07:27
*** alazarev has quit IRC07:27
*** jcoufal has joined #openstack-meeting-alt07:30
*** gokrokve has joined #openstack-meeting-alt07:31
*** boris-42 has joined #openstack-meeting-alt07:35
*** gokrokve has quit IRC07:36
*** rraja has quit IRC07:36
*** SergeyLukjanov has quit IRC07:41
*** alazarev has joined #openstack-meeting-alt07:42
*** IlyaE has quit IRC07:43
*** SergeyLukjanov has joined #openstack-meeting-alt07:48
*** IlyaE has joined #openstack-meeting-alt07:49
*** IlyaE has quit IRC07:56
*** lsmola has joined #openstack-meeting-alt07:57
*** flwang has quit IRC08:00
*** alazarev has quit IRC08:04
*** aratim has joined #openstack-meeting-alt08:04
*** flwang has joined #openstack-meeting-alt08:05
*** akuznetsov has joined #openstack-meeting-alt08:07
*** harlowja has quit IRC08:08
*** flaper87|afk is now known as flaper8708:09
*** aratim has quit IRC08:10
*** ashaikh has quit IRC08:11
*** nati_ueno has joined #openstack-meeting-alt08:15
*** vipul is now known as vipul-away08:27
*** gokrokve has joined #openstack-meeting-alt08:32
*** gokrokve has quit IRC08:36
*** SergeyLukjanov has quit IRC08:36
*** vipul-away is now known as vipul08:37
*** SlickNik has quit IRC08:39
*** SlickNik has joined #openstack-meeting-alt08:39
*** denis_makogon has quit IRC08:47
*** MarkAtwood has quit IRC08:50
*** MarkAtwood has joined #openstack-meeting-alt08:52
*** MarkAtwood has quit IRC08:52
*** boris-42 has quit IRC08:57
*** nati_ueno has quit IRC08:57
*** ashaikh has joined #openstack-meeting-alt09:02
*** boris-42 has joined #openstack-meeting-alt09:16
*** yamahata_ has joined #openstack-meeting-alt09:16
*** flwang has quit IRC09:19
*** rraja has joined #openstack-meeting-alt09:19
*** nati_ueno has joined #openstack-meeting-alt09:22
*** flwang has joined #openstack-meeting-alt09:23
*** jtomasek has joined #openstack-meeting-alt09:27
*** inkerra has quit IRC09:29
*** rraja has quit IRC09:29
*** jcoufal has quit IRC09:30
*** bot-bot is now known as denis_makogon09:31
*** gokrokve has joined #openstack-meeting-alt09:33
*** mozawa has quit IRC09:35
*** jtomasek has quit IRC09:36
*** gokrokve_ has joined #openstack-meeting-alt09:36
*** skostiuchenko has quit IRC09:37
*** gokrokve has quit IRC09:37
*** flwang has quit IRC09:38
*** rossella_s has joined #openstack-meeting-alt09:40
*** rsblendido has joined #openstack-meeting-alt09:40
*** gokrokve_ has quit IRC09:41
*** rraja has joined #openstack-meeting-alt09:46
*** jtomasek has joined #openstack-meeting-alt09:50
*** ashaikh has quit IRC09:54
*** markmcclain has joined #openstack-meeting-alt09:54
*** jcoufal has joined #openstack-meeting-alt09:58
*** yamahata_ has quit IRC09:58
*** markmcclain has quit IRC09:59
*** sfineberg has quit IRC10:02
*** sfineberg has joined #openstack-meeting-alt10:04
*** jtomasek has quit IRC10:04
*** lsmola has quit IRC10:05
*** yahongdu has quit IRC10:05
*** nati_ueno has quit IRC10:06
*** yahongdu has joined #openstack-meeting-alt10:06
*** derekh has joined #openstack-meeting-alt10:13
*** lsmola has joined #openstack-meeting-alt10:17
*** jtomasek has joined #openstack-meeting-alt10:20
*** aignatov has joined #openstack-meeting-alt10:36
*** gokrokve has joined #openstack-meeting-alt10:37
*** gokrokve_ has joined #openstack-meeting-alt10:39
*** gokrokve has quit IRC10:41
*** gokrokve_ has quit IRC10:43
*** rraja has quit IRC10:45
*** boris-42 has quit IRC10:47
*** lsmola has quit IRC10:49
*** zhiyan has joined #openstack-meeting-alt10:51
*** rraja has joined #openstack-meeting-alt10:57
*** yamahata_ has joined #openstack-meeting-alt11:01
*** boris-42 has joined #openstack-meeting-alt11:02
*** lsmola has joined #openstack-meeting-alt11:02
*** coolsvap has quit IRC11:09
*** rongze has quit IRC11:12
*** jprovazn has joined #openstack-meeting-alt11:15
*** yamahata_ has quit IRC11:15
*** NikitaKonovalov has joined #openstack-meeting-alt11:19
*** zhiyan has quit IRC11:22
*** HenryG has joined #openstack-meeting-alt11:32
*** jcoufal has quit IRC11:36
*** gokrokve has joined #openstack-meeting-alt11:39
*** skostiuchenko has joined #openstack-meeting-alt11:40
*** gokrokve has quit IRC11:44
*** rongze has joined #openstack-meeting-alt11:57
*** rkukura has quit IRC11:58
*** rongze has quit IRC12:17
*** vkmc has joined #openstack-meeting-alt12:27
*** rongze has joined #openstack-meeting-alt12:35
*** gokrokve has joined #openstack-meeting-alt12:40
*** rongze_ has joined #openstack-meeting-alt12:41
*** rongze has quit IRC12:42
*** nosnos has quit IRC12:45
*** gokrokve has quit IRC12:45
*** yportnova has joined #openstack-meeting-alt12:56
*** aignatov has quit IRC12:57
*** aignatov_ has joined #openstack-meeting-alt12:57
*** pdmars has joined #openstack-meeting-alt13:01
*** aratim has joined #openstack-meeting-alt13:04
*** aratim has quit IRC13:07
*** pdmars has quit IRC13:10
*** resker has quit IRC13:10
*** esker has joined #openstack-meeting-alt13:10
*** flwang has joined #openstack-meeting-alt13:13
*** pdmars has joined #openstack-meeting-alt13:14
*** esker has quit IRC13:15
*** lsmola has quit IRC13:22
*** yamahata_ has joined #openstack-meeting-alt13:25
*** yamahata_ has quit IRC13:26
*** yamahata_ has joined #openstack-meeting-alt13:26
*** SergeyLukjanov has joined #openstack-meeting-alt13:26
*** matrohon has quit IRC13:33
*** vkmc has quit IRC13:34
*** jdob has joined #openstack-meeting-alt13:35
*** noslzzp has joined #openstack-meeting-alt13:40
*** gokrokve has joined #openstack-meeting-alt13:41
*** gokrokve has quit IRC13:46
*** matrohon has joined #openstack-meeting-alt13:47
*** bugsduggan has joined #openstack-meeting-alt13:50
*** zhiyan has joined #openstack-meeting-alt13:55
*** dprince has joined #openstack-meeting-alt13:59
*** jecarey has joined #openstack-meeting-alt14:00
markwashhello glance folks14:00
rosmaitahi mark (and folks)14:00
markwashobligatory highlighting: iccha flwang ameade zhiyan flaper87 esheffield nikhil__14:01
markwash#startmeeting glance14:02
flaper87o/14:02
openstackMeeting started Thu Dec  5 14:02:00 2013 UTC and is due to finish in 60 minutes.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
flaper87yo yo!14:02
*** openstack changes topic to " (Meeting topic: glance)"14:02
openstackThe meeting name has been set to 'glance'14:02
zhiyanhi14:02
markwash#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:02
markwashmeeting agenda ^^14:02
markwashokay, I guess let's get rolling14:03
*** jcoufal has joined #openstack-meeting-alt14:03
markwash#topic project status meeting updates14:04
*** openstack changes topic to "project status meeting updates (Meeting topic: glance)"14:04
markwashIcehouse 1 has been cut14:04
flaper87w0000t14:04
markwashthanks for all the last minute patches, bugfixes, reviews folks14:12
*** yamahata_ has quit IRC14:12
zhiyanthank you markwish14:12
*** yamahata_ has joined #openstack-meeting-alt14:12
flaper87yeah, thank you all for being so helpful14:12
*** julim has joined #openstack-meeting-alt14:12
markwashif your blueprint got deferred from I-1, know that its just becuase we had such a short time between the summit and I-114:12
icchao/14:12
markwashand I-2 is ready for any spillover right now so let's keep at it14:12
ameadeo/14:12
markwash#link https://launchpad.net/glance/+milestone/icehouse-114:12
markwashnot much else to report from the project meeting14:12
markwashI'm still waiting to hear about mordred's plan for staging major python glanceclient releases14:12
markwashunless I just missed the email14:12
mordredI promose. I'm going to write it soon14:12
markwashhopefully we should be able to start implementing said plan next week14:12
mordredI thought about it in my brainhole on the aeroplane14:12
markwashhaha14:12
markwashthat is a good place for thinking14:12
markwash#topic checking in with the review backlog14:12
markwashAs you guys recall, we've been trying to reduce our review backlog to make reviews more manageable and increase our responsiveness14:12
markwashlet's see how we've been doing14:12
markwash#link http://russellbryant.net/openstack-stats/glance-reviewers-30.txt14:12
*** heyongli has joined #openstack-meeting-alt14:12
markwash(you should skip to the bottom of that one)14:12
markwash#link http://www.russellbryant.net/openstack-stats/glance-openreviews.html14:12
flwango/14:12
markwashwe're doing somewhat better14:12
iccha  Queue growth in the last 30 days: -3 (-0.1/day)14:12
markwashhmm14:12
*** ruhe has joined #openstack-meeting-alt14:12
ameadehow much of that is auto abandons?14:12
*** openstack changes topic to "checking in with the review backlog (Meeting topic: glance)"14:12
*** gokrokve has joined #openstack-meeting-alt14:12
markwash#link https://review.openstack.org/#/q/status:abandoned+project:%255Eopenstack.*glance.*+branch:master,n,z14:13
markwashso not much better then14:13
icchabut in lot of cases the committer has not gotten back to the reviewers comments14:14
flwangiccha: +114:14
icchathe cases we should worried about are where we neglected14:14
ameadeyeah a number of these have +2s14:15
markwashI wanna do another plug for this shortcut/bookmark14:15
markwash#link https://review.openstack.org/#/q/status:open+project:%255Eopenstack.*glance.*+branch:master+label:CodeReview%253D2+-label:CodeReview%253D-1+-+label:CodeReview%253D-2+-label:Approved%253D1,n,z14:15
flwangameade: yep, however, the owner didn't address the comments of -114:15
iccha+1 flwang14:16
markwashI call it "Needs one more"14:16
ameadehttps://review.openstack.org/#/c/37196/14:16
markwashIts pretty low right now, which is great14:16
markwashI think its a good one to keep in mind, since it will improve our response time on things that already seem to be good enough to one of us14:16
ttxmarkwash: may I tag icehouse-1 now ?14:16
icchathanks for identifying the patch ameade , now u can review it :p14:16
flwangameade: it's abandoned by himself14:16
* ttx hijacks meeting14:17
markwashameade: (ttx) are you happy with all your critical bugfixes being in? or is there still one missing?14:17
*** rraja has quit IRC14:18
ttxmarkwash: I see nothing targeted to i1 left14:18
ameademarkwash: i think flwang and zhiyan wanted to talk about the image property quotas and the user experience14:18
ameadebut everything is in14:18
markwashthen ttx I think we're good14:18
ttxameade: no big deal to tag a milestone where bugs survived anyway14:18
*** mozawa has joined #openstack-meeting-alt14:18
flwangameade: thanks for mentioned that :D14:18
*** eankutse has joined #openstack-meeting-alt14:18
markwashjust to close out the review status: It looks like we've stopped the queue from growing, but we've still got a lway to go. .14:19
flwangmarkwash: +114:20
icchaamen14:20
markwashI'd like to save some room today to talk about blueprint organization, see if there is anything we can do to improve on the current situation14:20
markwashbut before that, let's do some semi-open discussion14:20
markwash#topic image property quotas14:21
*** openstack changes topic to "image property quotas (Meeting topic: glance)"14:21
markwashameade, flwang, zhiyan: ^^ ?14:21
flwangmarkwash: i have a little bit concern about the scenarios that before we set the quota for properties, there are some existed quota exceeding images14:22
*** venkatesh has joined #openstack-meeting-alt14:22
*** vponomaryov has joined #openstack-meeting-alt14:22
flwangmarkwash: do you think it's ok or it should be take care by admin/deployer14:22
rosmaitaflwang: that's a deployer's responsibility14:22
markwashhmm, we probably cannot address it with a migration at all14:23
rosmaitai think the default quotas are very large14:23
ameadejust to be clear, it shouldn't break things if there are existing things over the quota14:23
markwashbut one question I have, if the # of props exceeds the quota, can you at least remove properties?14:23
ameadeany operations on an image must result in putting it backunder the quota14:23
markwashgotcha14:24
ameademarkwash: so just removing 1 prop if you are 2 over will not work14:24
flwangand do we have any plan to add the quota for locations number? given the original goal of this bug is to avoid generating big load for the database14:24
markwashso you can remove N - Q properties14:24
rosmaitaflwang: we should probably make a task to review other places where quotas should be applied14:25
flwangbut you know, the location table has 'value' and 'metadata', two TEXT (64k) columns, but I didn't see we address it firstly14:25
markwashwould it make any sense to have a "migration" that just logs if there are any images over the configured quota? that's a little silly I guess14:25
flwangrosmaita: yep, +114:25
flwangrosmaita: that's what I wanna highlight14:25
*** mozawa has quit IRC14:25
ameadeflwang: makes a lot of sense14:25
zhiyanmarkwash: ameade currently we don't allow enduser remove N-Q props14:26
rosmaitaflwang: good point, i just came across the ones we've got when working on something else, not from a systematic analysis14:26
markwashflwang: good catch14:26
flwangrosmaita: i just follow up your original point of the bug :)14:26
markwashseems like a great #action item :-) any volunteers?14:26
markwashflwang, you've already got some context here. . .14:27
flwangmarkwash: ok, I can take it14:27
rosmaita+114:27
ameadezhiyan: it should if the result of the transaction is under quota...or are you saying that doesnt work?14:27
flwanggiven ameade has done a lot of excellent work14:27
markwash#action flwang review the api for more items that should be under default quota/size restrictions and file bugs for anything that needs more work14:28
flwangmarkwash: yes, sir14:28
markwashflwang: thanks!14:28
zhiyanameade: we can't remove the exceeded part14:29
markwashI think image sharing is next, is that you rosmaita? (as soon as we've tied up the last loose ends with quotas)14:29
rosmaitamarkwash: yes14:30
markwashokay, any last thoughts on quotas for today?14:30
flwangyes14:31
ameadezhiyan: I can dig into that later if youd like14:31
*** rraja has joined #openstack-meeting-alt14:31
flwangshould we contact with keystone team to set the quota in keystone given that's the right way to do that14:31
flwangi'm not sure the status of the bp in keystone14:32
markwashthere has been some discussion about that recently14:32
flwanganyone we can contact?14:32
zhiyanameade: sure. (actually i have wrote it in my comments in your tag quota change)14:32
*** markmcclain has joined #openstack-meeting-alt14:32
markwashI'm not sure its the right way14:32
markwash1) there has been some significant pushback14:32
markwash2) the proposed mechanism is actually a push notification from keystone to us, IIRC14:32
ameadezhiyan: ah yes, it sounds like we are on the same page...so you are mostly concerned with it being a weird user experience?14:33
flwangmarkwash: got, then we can do that as we're doing now14:34
markwashflwang: yeah, I think its a good point to follow up on next meeting though, after the ML thread has mostly shaken down14:34
* markwash looks for link14:34
flwanguntil it's ready14:34
*** lblanchard has joined #openstack-meeting-alt14:34
zhiyanameade: a little tbh, i think.14:35
ameadezhiyan: i totally agree, I could not figure out how to enforce it better with the current way the domain model works14:36
markwashflwang: ah looks like that topic is supposed to be discussed at next week's project meeting14:36
ameadezhiyan: it's kind of all or nothing unless we hit the db and check if the number of properties has decreased14:36
flwangmarkwash: ok, i can contact some keystone core to get more details14:36
markwashflwang: I think most of the details are linked from the ML thread14:37
markwashas a starting point14:37
flwangmarkwash: ok, will dive into the mail list :D14:37
markwash#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/020799.html14:37
markwashameade: I'd like to take a look at that, maybe there is time to refactor the domain a little bit to make that less awkward14:38
flwangcool,thx14:38
markwashlets move on for now14:38
*** jdob has quit IRC14:38
markwash#topic image sharing (rosmaita)14:38
ameadesounds good14:38
*** openstack changes topic to "image sharing (rosmaita) (Meeting topic: glance)"14:38
rosmaitai don't have much to say, just want to be in on writing the BP for image sharing enhancements, when whoever wants to work on it has time14:38
* iccha making mental note to talk about more awkward stuff later14:39
*** bill_az has joined #openstack-meeting-alt14:39
rosmaitaso i was basically wondering if anyone was working on it yet14:39
markwashmy guess is we need a little more direction there14:40
rosmaitaok, i can put something together to get discussion started for next meeting14:40
*** eankutse has quit IRC14:40
markwashI'm not sure we ended up with much of a plan, there were some unsolved problems in both the incremental and non-incremental approaches14:41
flwangmarkwash: yep, rosmaita, it would be nice if you can highlight some direction14:41
*** eankutse has joined #openstack-meeting-alt14:41
bugsdugganrosmaita: +114:41
rosmaitaok, you can action-item me14:41
markwash#action rosmaita schedule a discussion for future plans for image sharing improvments14:41
flwangrosmaita: I can support you if you need any help14:42
rosmaitaflwang: thanks, i will let you know when i have something to look at14:42
markwashall right, next topic is blueprint organization14:42
rosmaitamay not be before next meeting, though14:42
markwashany other image sharing thoughts ?14:42
flwangroamaita: sure, you can catch me easily :D14:43
*** mjbright_ has joined #openstack-meeting-alt14:43
icchahappy to participant in deisgn discussion14:43
*** amotoki_ has joined #openstack-meeting-alt14:44
markwash#topic blueprint organization14:44
*** openstack changes topic to "blueprint organization (Meeting topic: glance)"14:44
markwash#link https://blueprints.launchpad.net/glance14:44
*** bill_az_ has joined #openstack-meeting-alt14:44
markwashI think that link sort of speaks for itself in terms of a problem statement14:45
*** bill_az has quit IRC14:45
markwashthere are 85 results in the list, mostly undefined14:45
icchayes it does14:45
markwash*priority14:45
markwashI would love it if our blueprint system were something that helped clarify thinking about what we're working on, but honestly it mostly seems to confuse me14:46
*** alcodemic has joined #openstack-meeting-alt14:46
markwashI dunno if anyone here has had better luck with blueprints when working with another project?14:46
*** NehaV has joined #openstack-meeting-alt14:46
*** demorris has joined #openstack-meeting-alt14:46
icchalooking at other projects like https://blueprints.launchpad.net/cinder/+specs?memo=75&start=7514:47
icchaall seem to have some undefined stuff14:47
*** dmitryme has joined #openstack-meeting-alt14:48
*** dmitryme has left #openstack-meeting-alt14:48
icchamaybe our step is to see what is there in our undefined and close out duplicates ?14:49
*** sballe has joined #openstack-meeting-alt14:49
icchait is ok to have some undefined cause it can serve to be an idea dump place, but as and when blueprints get added we maybe discuss in our meetings next bps proposed for the week?14:49
icchai am just giving random suggestions here14:49
*** markmcclain has quit IRC14:49
*** mjbright_ has quit IRC14:49
markwashrandom suggestions appreciated!14:50
rosmaitai think it's helpful when the BP has a full spec attached14:50
rosmaitawith some use cases14:50
*** ashwini has joined #openstack-meeting-alt14:50
icchaand there are some which already have code submitted14:50
icchahttps://blueprints.launchpad.net/glance/+spec/glance-cache+unittests14:50
icchabut are not approved14:50
markwashI'm trying to think if there is any way to set up a workflow there with bookmarks, sort of like dealing with the difficulties of reviews14:51
flwangiccha: yep, i think we should avoid this kind of stuff14:51
*** jdob has joined #openstack-meeting-alt14:51
*** alcodemic has left #openstack-meeting-alt14:51
icchamarkwash: +1 on workflow14:52
flwangif the bp is not approved, we should poke it before reviewing14:52
markwashone thought that I keep coming back to, is it might help if we required patches to be linked to approved blueprints or accepted bugs. . but I think we're pretty far from being able to do that in an automatic fashion14:52
icchamaybe as reviewers it is our responsibility?14:52
markwashand by required, I mean, I would make a review bot that -1s anything that is not so linked14:52
markwashbut that idea does have a number of problems I suppose14:53
*** alcodemic has joined #openstack-meeting-alt14:53
markwashfor one, I don't really mind if people want to include a patchset to stand in for the spec for a blueprint14:53
*** alcodemic has left #openstack-meeting-alt14:53
markwashand for another, we get a lot of good stuff from bugfixes for bugs that never get triaged14:53
markwash(bug organization is another similar topic)14:54
flwangbut bp is different from bug14:54
icchasometimes i end up triaging after looking at patch :(14:54
markwashflwang: true14:54
markwashflwang: I guess I worry, if we required more from bp-linked changes than bug-linked changes, folks would just register enhancements as bugs14:55
flwangiccha: good point, i will follow14:55
*** aostapenko_alt has joined #openstack-meeting-alt14:55
markwashbut maybe that is not a big concern14:55
flwangany open discussion stage today?14:56
*** jcoufal has quit IRC14:56
markwashanyone interested in following up on this topic next week or a bit later? It might benefit from some solo thinking14:56
markwashflwang: sure14:56
rosmaita+114:56
markwash#topic open discussion14:56
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:56
iccha  e too14:56
iccha*me14:56
ashwinitrying to get details on locations etc for the glance mini summit in DC area markwash14:56
flwangmarkwash: i'm thinking the impact of container technology for Glance14:57
markwashashwini: thanks! let me know any updates or if there is anything you need from me14:57
rosmaitaflwang: tell us more14:57
*** katyafervent has quit IRC14:57
markwashflwang: interesting topic for sure :-)14:57
*** kdurazzo has joined #openstack-meeting-alt14:57
ashwinimarkwash: will do, we should probably have a quick phone call on it so hash out some other details14:57
ameadeso one thing i was trying to get at earlier with reviews, can we do anything to help patch submitters with these patches that go abandoned?14:57
ameadei think it's a cop out to just say it's on them and ignore the issue14:58
markwashameade: I agree. it should be easy to mine the gerrit history for patches that were abandoned with no reviews14:58
markwashwe could go through and resubmit ones that seem valuable14:58
*** vbellur has joined #openstack-meeting-alt14:59
markwashashwini: sure, sometime today? or is that too soon?14:59
*** gregsfortytwo1 has joined #openstack-meeting-alt14:59
flwangsuch as docker, it will consumer image directly instead of using Glance for now14:59
markwashs/resubmit/restore/14:59
icchathats what i do sometimes, i go to abandoned aotches and say i apoligize that they got ignored and request reviewwer to restore them14:59
ameademarkwash: can you think of something we can do to help in the long run? i'm sure this is also something other project deal with14:59
*** akerr has joined #openstack-meeting-alt14:59
flwangso given container/docker is so hot, i'm wondering if we should do some investigation to embrace it from the glance POV14:59
ameademaybe the auto-abandon system is flawed14:59
ashwinimarkwash: today is fine with me, my afternoon is mostly open15:00
*** achirko has joined #openstack-meeting-alt15:00
flwanggiven it's the next big star15:00
markwashameade: the thing we really need is to get our review queue down if at all possible15:00
icchaflwang: sounds like interesting idea15:00
*** bswartz has joined #openstack-meeting-alt15:00
markwashflwang: I'm interested in that. . especially what kinds of changes we might need to make. . it would be really good to see ways in which we are specific to vms right now that we could generalize15:00
flwangmaybe the future15:00
markwashor if there are other changes that make sense15:01
ameademarkwash: yeah that would solve future problems15:01
flwangmarkwash: exactly15:01
*** caitlin56 has joined #openstack-meeting-alt15:01
ameademarkwash: i'll take an action item to look through old reviews15:01
markwashameade: ah yes, but you're right, the problems of the past need our attention15:01
flwangmarkwash: for now, we are targeting VM, but container is target to application15:01
*** vbellur has left #openstack-meeting-alt15:01
flwangso maybe we should adjust our mission/goal to do some change15:01
icchamarkwash: also not sure if i made it clear will take action item on blueprint process15:01
*** kgriffs_afk is now known as kgriffs15:02
*** glenng has joined #openstack-meeting-alt15:02
markwashhmm, we might need to vacate15:02
markwashit is past time15:02
markwashthanks everybody!15:02
bugsduggan\o15:02
markwash#endmeeting15:02
bswartzthanks markwash15:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:02
icchacya15:02
openstackMeeting ended Thu Dec  5 15:02:34 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
*** Dinny_ has joined #openstack-meeting-alt15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-12-05-14.02.html15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-12-05-14.02.txt15:02
*** vbellur has joined #openstack-meeting-alt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-12-05-14.02.log.html15:02
*** bugsduggan has left #openstack-meeting-alt15:02
bswartz#startmeeting manila15:03
openstackMeeting started Thu Dec  5 15:03:00 2013 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: manila)"15:03
openstackThe meeting name has been set to 'manila'15:03
*** ashwini has left #openstack-meeting-alt15:03
aostapenko_altHi all!15:03
bswartzhello15:03
akerrhello15:03
achirkohi15:03
Dinny_hi15:03
bill_az_Hi15:03
vponomaryovhi15:03
kdurazzohi15:03
yportnovahi15:03
bswartzcool we have a lot of people15:03
gregsfortytwo1hi15:03
bswartzunfortunately I'm not as prepared as I should be15:03
bswartzheh15:03
bswartz#link https://wiki.openstack.org/wiki/ManilaMeetings15:04
rrajahi15:04
vbellurhi15:04
bswartzso it looks like I setup the agenda already15:04
*** caitlin56 has quit IRC15:04
bill_az_bswartz: before we get started, I want to introduce Marc Eshel.15:04
bill_az_He will be working with me on IBM/GPFS Manila drivers.15:04
*** anands has joined #openstack-meeting-alt15:05
bswartzbill_az_: does he have a IRC handle?15:05
bill_az_Marc has years of experience with NFS, in particular with open source ganesha project15:05
bswartzah, excellent15:05
bill_az_His handle is eshel - but I don't think he's on just yet15:05
csabahi15:05
bswartzeshel: welcome!15:05
*** caitlin56 has joined #openstack-meeting-alt15:05
anandsHi guys15:05
caitlin56hi15:06
anandsVijay Bellur is not able to make today's meeting, I will be filling in from the redhat folks15:06
bswartzokay so bill_az_ and vbellur and I were supposed to get together to discuss gateway-mediated attachements15:06
*** prasadv has joined #openstack-meeting-alt15:06
bswartzanands: thank you15:06
*** xyang1 has joined #openstack-meeting-alt15:06
bswartzwhat I would really like is for someone to volunteer to prototype a gateway-mediated attachment scheme15:07
bswartzI could do it if I had like 100x more spare time15:07
*** mjbright_ has joined #openstack-meeting-alt15:07
*** heyongli has quit IRC15:07
bswartzI'm interested in NFS-over-vsock and I'm also interested in VirtFS15:07
anandsbswartz: Worked with vbellur, ramana etc. we have a draft of the architecture for hyperv-mediated model for multi-tenancy - we can discuss when others are ready - https://wiki.openstack.org/wiki/Manila_Networking/Hypervisor_mediated#References:15:08
bswartzI guess I can offer a brief background for people not familiar with the issue15:08
bswartzManila is going to need 2 different mechanisms for attaching guests to shared storage:15:09
eshelhi I am on, I was on the manila tab15:09
bswartz1) For backends that support it, manila will create virtual servers on the backends and conenct them directly to the tenant network so guests can use native protocols to talk directly to the backends. This mostly includes hardware backends with features like NetApp vservers -- I know that Nexenta has a comparable feature, and I think EMC has a comparable feature too15:10
*** vbellur has quit IRC15:11
bswartz2) For backends that only understand how to serve data to one network segment, manila will provide virtualized access to the shared storage with a bridge of some kind at the hybervisor. Possible bridges including things like VirtFS, or NFS gateways layered on top of a clustered filesystem15:11
bswartzeshel: hi15:11
bswartzwe are making good progress on (1), but we need to do some prototyping for (2)15:12
anandsWe are ready to do that if everyone agrees to the arch outlined in the wiki link for (2)15:12
bswartzvbellur, bill_az, and I have volunteered to run a separate working group to work on (2), so please contact us if you want to be included15:12
bswartzhowever we haven't actually started up that working group yet due to the US holidays15:13
*** tsufiev has joined #openstack-meeting-alt15:13
bswartzbill_az I'll contact you offline15:14
bill_az_bswartz:  the description in Hypervisor Mediated storage link is similar to what we are thinking15:14
bswartzanands: let vbellur know that we need to connect15:14
bill_az_we'd like to be included in discussions of that15:14
anandsbswartz: sure, was working with him all along wrt the wiki arch15:14
gregsfortytwo1anands: what drove you to a per-hypervisor instead of per-tenant ganesha instance?15:14
bswartzokay cool15:14
anandsgregsfortytwo1: we thought a single ganesha on the hypervisor could scale well enough, per-tenant approach seemed like an overkill15:15
*** NikitaKonovalov has quit IRC15:15
bswartzanands: what's the benefit of ganesha over nfs-kernel-server?15:15
vponomaryovbswartz: userspace nfs15:16
gregsfortytwo1bswartz: note the listing of FSALs it already supports? :)15:16
bswartzI know it's in userspace, but that shouldn't matter in the context of a hypervisor15:16
anandsbswartz: its a user-space nfs server implementation, can scale up based on its cache-inode layer which can grow arbitrarily large, a crash will not necessarily reboot your hypervisor ;)15:16
*** yamahata_ has quit IRC15:17
gregsfortytwo1anands: hrm, that makes sense, just thinking that per-tenant would have better cache properties15:17
*** yamahata_ has joined #openstack-meeting-alt15:17
bswartzanands: oh I wasn't aware of these FSALs15:17
anandsgregsfortytwo1: :)15:17
bswartzI need to read up on ganesha it would seem15:17
gregsfortytwo1and would make it easier to move to a model where we don't rely on the nfs server for doing all the security15:17
*** amytron has joined #openstack-meeting-alt15:17
bswartzhold on there about security15:17
bswartzsecurity is one of the thorniest problems with shared filesystems15:18
gregsfortytwo1sorry, that comment was about a per-tenant versus per-hypervisor model15:18
anandsthe wiki also refers to some of the security aspects, we could take that topic up separately I guess15:18
anandsgregsfortytwo1: ah ok15:18
bswartzMy personal feeling is that in the hypervisor mediated model, security is actually a lot simpler, because we can rely on the hypervisor and the gateway to enforce it15:18
bswartzthe backend doesn't need to do anything15:19
anandsbswartz: yes true, but if we further want more fine grained access control we have a way to enforce15:19
bswartzI would actually prefer to make the tunneling procotol something stupid like NFSv3 with UNIX security (aka No Fscking Security)15:19
caitlin56tenant network mediated offers truer security. hypervisor mediated requires the storage admin to trust the hypervisors.15:20
anandsum...sure, we could think on those lines15:20
gregsfortytwo1why prefer that security model?15:20
caitlin56Not that this makes hypervisor mediated totally invalid, but that is one of its limitations.15:20
bswartzso with any kind of mediated access -- the point is that the mediator limits the tenants view to a subset of the actual backend filesystems15:21
bswartzhowever, within that subset the tenant should be able to do whatever he wants15:21
bswartzbecause tenants are all "root" within their guest OSes15:21
anandsyes15:21
bswartznow if tenants want to further subdivide access to multiple non-root users within their guests, that's their business15:22
caitlin56bswartz: with the vlan method i can configure my file server to squash root.15:22
*** NikitaKonovalov has joined #openstack-meeting-alt15:23
caitlin56But to be clear, I think both models are valid.15:23
*** sacharya has joined #openstack-meeting-alt15:23
bswartzcaitlin56: I would argue that squashing root is unneeded -- indeed many users may want root access to their shared filesystem15:23
bswartzthe security model needs to be about which filesystems you can see, or which parts of a larger filesystem you can see -- all of that is implemented at layers above the actual file-sharing procotol15:24
caitlin56If hypervisor mediation is acceptable then you do not need root squashing, agreed.15:24
*** betsy has quit IRC15:24
*** alazarev has joined #openstack-meeting-alt15:25
bswartzokay so we can talk and talk about this, but I don't want to take up the whole meeting15:25
bswartzas I said before, we'll form a working group to drive this to the prototype stage, then we'll present it and solicit feedback15:25
bswartz#topic dev status15:26
*** openstack changes topic to "dev status (Meeting topic: manila)"15:26
*** devlaps has joined #openstack-meeting-alt15:26
bswartzthe more critical tasks are to continue driving method (1) to completion, so we can demonstate a fully working multitenant implementation15:26
caitlin56Nexenta has some interest in this, but resources for hypervisor-mediation would probably be unavailable for at least 2 months.15:26
bswartzwe're a lot closer on (1) than we are on (2)15:27
bswartzbtw I've seen a lot of changes go into gerrit and they're awaiting review15:27
*** jergerber has joined #openstack-meeting-alt15:27
eshelare we developing all 4 options?15:27
bswartzI'm behind on reviewing and could use whatever help I can get15:27
bswartzeshel: sort of15:28
* caitlin56 will do some reviewing this week.15:28
csababswartz: https://review.openstack.org/59124, we are looking for getting reviews15:28
bswartzeshel: mentally I've collapsing all the mediated methods down to one method with flavors15:28
csaba(glusterfs driver resubmitted along lines that we last discussed)15:28
bswartzeshel: and the flat network model is just a degenerate case of (1)15:29
bswartzcsaba: yes I saw it -- I apologize to everyone waiting for reviews, I've been busy since the holidays15:29
eshelbut to get approval we need them all to be implemented?15:30
bswartzI will be out of town this afternoon and tomorrow in Westford MA15:30
bill_az_bswartz: csaba  I'll take a look at gluster driver today and comment15:30
bswartzeshel: no! the intent is that any given backend only needs to implement 115:30
bswartzI'll try to get some reviewing done in my downtime while travelling15:31
csababill_az_: kthx15:31
bill_az_eshel:  the question about approval is regarding getting into incubation status?15:31
anandsbill_az_: thx, look forward to your comments15:31
bswartzyportnova/vponomaryov: do you want to let the group know what's new this week for you end?15:32
eshelso is multi tenants is a requerment?15:33
bill_az_bswartz:  is support for multiple backends implemented?  I dont find it15:33
*** NehaV1 has joined #openstack-meeting-alt15:33
vponomaryovnetwork api commit were released15:34
bswartzeshel: not right now -- I'm happy to have single tenant drivers until we get the major multitenant work done15:34
yportnovabswartz: we are working on implementation of this bp https://blueprints.launchpad.net/manila/+spec/join-tenant-network15:34
bswartzbill_az_: it should mostly be there -- I wouldn't be shocked if there are bug though -- it's not something we've done testing on15:34
vponomaryovhttps://review.openstack.org/#/c/60241/ - service15:34
vponomaryovhttps://review.openstack.org/#/c/59466/ - client15:34
*** IlyaE has joined #openstack-meeting-alt15:34
*** devkulkarni has joined #openstack-meeting-alt15:35
bswartzanyone with review bandwidth: https://review.openstack.org/#/q/status:open+manila,n,z15:35
*** NehaV has quit IRC15:35
csabajust to tell, aostapenko_alt 's                                                                            ?' failed15:36
*** banix has joined #openstack-meeting-alt15:36
bswartzcsaba: ?15:36
csabacommit https://review.openstack.org/#/c/59082/15:36
csaba-- sorry bogus newline --15:36
csabacaused a bit hiccup15:36
bswartzokay15:37
csabaas migration was provided for schema change but the manage.py script is not provideed15:37
bswartzand version of the NetApp driver w/ multitenant support is coming along -- I'm hoping it will be upstream soon15:37
csabaI resolved it on my end so I can volunteer to sumbit a usable manage.py15:37
bswartzthe NetApp driver will probably serve as a reference driver for other hardware vendors because I expect the generic driver to actually be fairly complex15:38
bswartzalthough both will be available during icehouse15:38
bswartzif there are folks out there trying to work on backends and getting stuck, please reach out to me15:39
eshelwhere are the requierments for multitenant support documented15:39
bswartzI want to know what we can do better (other than speeding up our current work)15:39
vponomaryovcsaba: if you found a bug, please post in launchpad, I have tested share metadata on lvm15:39
bswartzeshel: they're not -- it's all being coded up last month and this month15:39
bswartzeshel: developer docs / backend docs are something we know we need15:40
aostapenko_altcsaba: you can manage migrations by 'manila-manage db'  commands15:40
bswartz#topic open discussion15:41
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:41
csabaaostapenko_alt: thanks I did not now, just worked my way through migration with googling...15:41
vponomaryovaostapenko_alt: yes, there is need to sync db15:41
bswartzI don't have anything else on my agenda15:41
bill_az_general question - let's say I have created a share and given access to several vm instances15:42
*** kgriffs is now known as kgriffs_afk15:42
bill_az_is there (or is there planned) an automated way to mount the share on several instances automatically?15:42
bill_az_I can envision how this can be done w/ user data when booting a new instance15:43
bswartzbill_az_: yes I consider that a desirable feature to have inside manila15:43
*** sacharya has quit IRC15:43
bill_az_but not sure about instances that are already running15:43
caitlin56It shoulb be just as automatable as it is without virtualization.15:43
*** sarob has joined #openstack-meeting-alt15:43
bswartzbill_az_: however it's not on the critical path to getting the service working15:43
anandscaitlin56: yes, agree15:44
bill_az_caitlin56:  true - my question is whether we have ideas on how to do that15:44
bswartzI want to consider offering agents that can be installed on guests to automate the mount process -- we need to standardize a protocol so manila can at least try to automate the mount15:44
bill_az_bswartz:  I agree it's not highest priority15:44
*** allyn has joined #openstack-meeting-alt15:44
caitlin56bill_az: why not keep the mechanisms that work?15:44
*** flwang has quit IRC15:44
bswartzwhether the agent is a boot time only thing or is always running -- perhaps we offer both15:45
caitlin56If you belong to a tenant network, you mount your file shares on that network the same way you would have done on a corporate intranet.15:45
bswartzand interfacing with cloud_init seems like an obvious starting point15:45
*** flwang has joined #openstack-meeting-alt15:45
bswartzthe key is that whatever we do it will be optional for tenants15:45
caitlin56the tenant shouldn't be able to tell them apart.15:45
bswartzif that's all for today I'll see you next week15:47
kdurazzothe automation point actually lends itself well to the hypervisor model15:47
kdurazzoinstead of per tenant15:47
bswartzkdurazzo: perhaps15:47
caitlin56kdurazzo: why?15:48
bswartzkdurazzo: I'd like to see some prototypes here -- it's something that can be worked on in parallel by whoever is interested15:48
kdurazzothe HV could handle the init upon bringup15:48
caitlin56the tenant network approach can look *exactly* like the corporate intranet. client machines know how to deal with that.15:48
kdurazzook15:48
kdurazzothe ok was for bswartz :-)15:49
caitlin56the limitation on tenant-network method is that it is harder on the storage servers, which have to offer vritualized interfaces. But it is definitely simpler for the clients.15:49
bill_az_bswartz:  +1 on cloud-init15:49
kdurazzowe should probably discuss that more, I am not sure it is *simpler*, would like to understand your point on that15:49
Dinny_bswartz : what is cloud_init you refer here? I could not follow that15:50
caitlin56kdurazzo: with a proper dhcp-agent the network-mediated approach can leave the guest os with the illusion that they are on a corporate network.15:50
*** NikitaKonovalov has quit IRC15:51
bswartzDinny_: https://help.ubuntu.com/community/CloudInit15:51
kdurazzocaitlin56: I believe the same could be accomplished with the HV init approach as well15:51
caitlin56kdurazzo: I posted one comment on this to the blueprint, the current dhcp-agent does not do as much as many corporate intranet DHCP servers do. That is the only gap.15:51
Dinny_bswartz: thanks for the link :)15:51
kdurazzocaitlin56: will look at your comments and review the BP again15:51
caitlin56kdurazzo: that depends on whether the hypervisor-mediated is using a virtFS or is transparently proxying NAS services.15:52
caitlin56virtfs is a great solution, but guest OSs don't support it today.15:52
bswartzcaitlin56: I fear the proxying won't ever by transparent in the mediated approaches -- that's not the intent15:53
bswartzs/by/be/15:53
caitlin56transparent proxying is indeed complex to set up.15:53
gregsfortytwo1anands: just looked at it again because of caitlin56's comments and noticed the draft doesn't specify how clients will connect to the local ganesha server; what are your plans for plumbing that?15:54
bswartzthe intent of the mediated approaches is to provide a filesystem to the tenant, where the tenant's view of the filesystem is whatever the gateway wants it to be, and it independent of the real backend filesystem15:54
*** SergeyLukjanov has quit IRC15:54
*** sc68cal has joined #openstack-meeting-alt15:54
bswartzindeed the real backend filesystem should be unknown to the tenant when a mediated approach is used15:54
anandsgregsfortytwo1: there are some details to be ironed out completely; main idea is that sub-dirs can be exported as tenant shares - each directly mountable by a tenant15:55
caitlin56bswartz: isn't the simplest way to do hypervisor mediated to require the tenant to install a virtfs library?15:55
bswartzcaitlin56: that's one approach, but we need to be more flexible15:55
caitlin56bswartz: agreed, because existingVMs cannot use a library.15:56
bswartzcaitlin56: until somone writes a virtfs library for windows that's not an option for some users15:56
gregsfortytwo1anands: right, but it'll still need to do the network plumbing somehow (I'm not sure what the options are when it's all on one machine)15:56
bswartzokay so before we dive back down the mediated multitenany rathole I'm going to end the meeting15:57
anandsgregsfortytwo1: vsock interface is something vbellur has mentioned, can sync up with him and get back on that. Maybe the answer?15:57
caitlin56Effectively "hypervisor mediated with proxy" is the same as "network mediated" -- with the difference of where the "proxying" is done.15:57
caitlin56With "network mediated" the "proxying" is done of the storage server itself.15:57
bswartzplease feel free to continue the discussion in #openstack-manila15:57
gregsfortytwo1k, just curious15:57
bswartzI'll be over there15:57
bswartz#endmeeting15:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:57
openstackMeeting ended Thu Dec  5 15:57:53 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-12-05-15.03.html15:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-12-05-15.03.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-12-05-15.03.log.html15:57
*** glenng has left #openstack-meeting-alt15:58
*** caitlin56 has left #openstack-meeting-alt15:58
*** akerr has left #openstack-meeting-alt15:58
*** jcooley_ has joined #openstack-meeting-alt15:58
*** achirko has left #openstack-meeting-alt15:58
*** anands has left #openstack-meeting-alt15:58
kdurazzo#quit15:58
*** kdurazzo has quit IRC15:58
*** s3wong has joined #openstack-meeting-alt15:58
*** jprovazn has quit IRC15:58
*** michsmit has joined #openstack-meeting-alt15:59
*** gregsfortytwo1 has left #openstack-meeting-alt15:59
*** jcooley_ has quit IRC15:59
mesteryHi16:00
banixHi everybody16:00
mesteryHi banix16:00
mestery#startmeeting networking_policy16:00
openstackMeeting started Thu Dec  5 16:00:24 2013 UTC and is due to finish in 60 minutes.  The chair is mestery. 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: networking_policy)"16:00
openstackThe meeting name has been set to 'networking_policy'16:00
*** SumitNaiksatam has joined #openstack-meeting-alt16:00
mestery#link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy Agenda16:00
s3wongHello16:00
SumitNaiksatamhi!16:00
*** pballand has joined #openstack-meeting-alt16:00
mestery#topic Action Items from last week16:00
*** openstack changes topic to "Action Items from last week (Meeting topic: networking_policy)"16:00
*** alagalah has joined #openstack-meeting-alt16:01
mesteryI guess it's from two weeks ago. :)16:01
alagalahHi16:01
mesteryFirst one: banix and michsmit16:01
*** rraja is now known as rraja|afk16:01
mesteryAny progress on fleshing things out on abojects and attributes?16:01
banixI added a few tables to the doc describing the attributes of new objects16:01
mesterybanix: Near the end of the doc, right?16:02
ywuehllo16:02
*** aignatov_ has quit IRC16:02
banixHave you guys had a chance to have a look: https://docs.google.com/document/d/1ZbOFxAoibZbJmDWx1oOrOsDcov6Cuom5aaBIrupCD9E/edit#16:02
banixmestery: yes16:02
mestery#link https://docs.google.com/document/d/1ZbOFxAoibZbJmDWx1oOrOsDcov6Cuom5aaBIrupCD9E/edit?usp=sharing Neutron Policy Google Doc16:02
mesterybanix: I briefly looked this morning, thanks for starting on this.16:02
*** thinrichs has joined #openstack-meeting-alt16:03
*** aignatov has joined #openstack-meeting-alt16:03
banixmestery: sure16:03
*** thouveng has quit IRC16:03
mesteryHas anyone else had a chance to look at the work banix has done on the document?16:03
thinrichsI took a quick look.16:03
s3wongyes16:03
*** kgriffs_afk is now known as kgriffs16:04
mestery#topic Object and Attribute Discussion16:04
*** openstack changes topic to "Object and Attribute Discussion (Meeting topic: networking_policy)"16:04
mesteryLets move to discussing those now.16:04
*** aignatov has quit IRC16:04
alagalahreading16:04
*** dttocs has joined #openstack-meeting-alt16:04
banixSo I think the first question to answer is:16:04
*** xyang1 has quit IRC16:04
banixDo we start with or without "endpoint" as a Neutron object.16:05
mesterybanix: I think we should start with that assumption, yes, but I'm curious what others think.16:05
banixI think we should have them but the question is if starting without them will make things simpler without limiting us too much16:05
*** jcooley_ has joined #openstack-meeting-alt16:06
thinrichsI don't know how we could have non-Neutron objects as endpoints.16:06
*** rraja|afk has quit IRC16:06
thinrichsWhat would those objects mean?16:06
mesterythinrichs: Exactly, thus I think we need the endpoint concept from the start.16:06
*** yamahata_ has quit IRC16:06
thinrichsHow would, e.g. Heat, know what an object that Neutron doesn't understand represent?16:06
s3wongHow are endpoints as non-Neutron object be represented?16:06
ywui assume we start with Neutron objects first.16:06
*** rnirmal has joined #openstack-meeting-alt16:06
prasadvi think neutron needs to know16:07
*** sergmelikyan has joined #openstack-meeting-alt16:07
*** bswartz has left #openstack-meeting-alt16:07
alagalahDoesn't neutron need to know the capabilities of the underlying resources around which it is making a policy?16:07
alagalahie QoS, policing etc?16:07
mesterybanix: Correct me if I'm wrong, but if we start without the endpoint concept, we would instead directly be putting ports and possibly networks into groups, right?16:07
banixWell, if we do not have "endpoint" as a Neutron object, we will be limited to using ports and networks, etc.16:07
banixmestery: yes16:08
*** alazarev has quit IRC16:08
thinrichsBut even if we had "endpoint" as an object, how could Neutron enforce a policy over endpoints--when they're not objects it understands in any fundamental way?16:08
mesterybanix: I think it makes sense to start with the endpoints then, and we can map those internally to ports/networks if we need to.16:08
*** yahongdu has quit IRC16:09
dttocsI think we need endpoint as an abstract neutron object - they are objects, but they don't necessarily live in a specific place in the existing Neutron hierarchy16:09
*** rudrarugge has joined #openstack-meeting-alt16:09
ywumetery, i like this idea.16:09
thinrichsmestery/dttocs: I'm not convinced.16:09
mesterythinrichs: We would be exposing endpoints into the neutron object model per banix's notes in the document.16:09
thinrichsHow can Neutron implement a policy when it doesn't know what those objects represent?16:10
*** betsy has joined #openstack-meeting-alt16:10
dttocsCore neutron wouldn't necessarily know, but the plugin responsible for that endpoint would certainly need to16:10
banixthinrichs: If we have them as objects then Neutron know what to do with them16:10
thinrichsdttocs: but then the semantics of the policy is plugin-dependent.16:10
banixdttocs: exactly16:10
sc68calWe already have a case of semantics of policy being plugin dependent16:11
* sc68cal points to the QoS API16:11
thinrichsWe don't want the same policy to mean 2 different things, depending on which plugin we're using.16:11
sc68calat least that's what I've been trying to do16:11
banixthinrichs: well, it will be extension-dependent16:11
*** jasonb365 has joined #openstack-meeting-alt16:11
thinrichsThis is the same issue we discussed last week, but instead of not knowing the syntax of the policy, here other OS components don't know the semantics.16:11
*** boris-42 has quit IRC16:11
alagalahbanix: So with the Attributes tables, regarding Endpoints, would it be useful to define what Actions: they can perform or provide which gives context to WHAT they do as an endpoint even if outside of Neutron control ? ie it shows its capabilities?16:11
*** songole has joined #openstack-meeting-alt16:11
thinrichsHappy to have extensions, but the core language must have a syntax/semantics that everyone agrees on.16:12
michsmitthinrichs: the intent is the same, the rendering of the policy may be different16:12
*** jprovazn has joined #openstack-meeting-alt16:12
mesterymichsmit: Yes, that's exactly it.16:12
thinrichsmichsmit: great--but what is the intent if the basic objects change meaning from plugin to plugin.16:12
*** jcooley_ has quit IRC16:12
*** sacharya has joined #openstack-meeting-alt16:13
banixalagalah: that would make things a bit too complicated to start with. Don't you think?16:13
*** jcooley_ has joined #openstack-meeting-alt16:13
alagalahWell I guess I'm trying to think of this as action "providers" and action "consumers" and work out where they meet in the middle rather than look at "endpoint" per se and branch out from there16:14
thinrichsIf WE described the semantics of these objects in the language, then great.  Every plugin can implement those however they like.16:14
banixI think if we have endpoints for now they will refer to known Neutron objects (that's why we could not use them at the moment). No?16:14
*** rsblendido has quit IRC16:15
*** rossella_s has quit IRC16:15
mesterybanix: Yes.16:15
alagalahbanix: If that comment was to me, then yes, I think that at least confines the problem space16:15
thinrichsIf we said that 'foozle' means <connecting internal net to external net> then great.  Or if we used common terms like 'router', 'switch', where everyone knows the semantics, that works too.16:15
michsmitbanix: agreed16:15
*** hemanthravi has joined #openstack-meeting-alt16:15
thinrichsBut what I'm worried about is if we just say there's a collection of objects, and each plugin defines what that object does--what its properties are, what its functionality is, etc.16:16
alagalahBut to thinrichs point, banix, if we think in terms of "provider" "consumer" semantics it (potentially) could make it more extensible (ie I thinking ODL integration with various switching platforms etc)16:16
mesterythinrichs: That's what the google document is trying to do.16:16
banixSo would the Alternative Option in the doc a reasonable start?16:16
*** csaba is now known as csaba|afk16:16
alagalahbanix: The Alternative option appeals to me16:16
mesterybanix: Just to be clear, you are referring to the alternative option around Endpoints/Groups you wrote up, correct?16:17
thinrichsTook another peak at the google doc.16:18
banixmestery: yes16:18
*** jcooley_ has quit IRC16:18
thinrichsThe Alternate option basically allows, say Heat, to create uuids and put them in groups, yes?16:18
michsmitbanix: Under endpoint attributes, the member field indicates the group in the alternative option ?16:18
thinrichsThen we write a policy that says UUID1 and UUID2 can't exchange packets on port 80 (or something similar).16:19
banixmestery: sorry for not being clear, no16:19
banixThere is no reference back to the group but we could add that; this way an endpoint can belong to multiple groups16:19
banixmember is essential a reference to say the "port" or "network"16:20
banixshould change the name; it is confusing16:20
alagalahbanix: Is it worth buildign a taxonomy like pp2 of this document: http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf16:20
*** aostapenko_alt has quit IRC16:21
alagalahbanix (for your alternative option)16:21
*** yahongdu has joined #openstack-meeting-alt16:21
banixalagalah: thanks for the reference; doesn't the table provide the same info? We can obviously make it more complete.16:21
mesteryalagalah banix: I agree, lets flesh out the work banix has done on the table in the doc.16:22
alagalahalagalah: The table is good, but there was questions about where members/groups are referenced16:22
thinrichsalagalah: something like that where we spell out the meaning of all the possible objects would make me happy.16:22
alagalahmestery / banix : No worries16:22
dttocsTaxonomy seems worthwhile - I got lost in the details with the table16:22
banixalagalah: got it.16:22
mesterybanix: Can I give you an action item to flesh this out a bit based on the discussion here?16:23
dttocse.g. question about what QoS parameters should be supported - we need the taxonomy first, then can get into those details imho16:23
michsmita diagram showing the relationships between the tables may help16:23
banixdttocs: sure. will do.16:23
mestery#action banix to flesh out the tables he put in the document.16:23
alagalahbanix: I can have a crack at it if you like, and you can chastise me for getting it wrong and I can fix16:23
mestery#undo16:23
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x26b7950>16:23
mesteryalagalah banix: You guys want to collaborate on this one?16:24
banixalagalah: sounds good. Thanks.16:24
* alagalah ack16:24
banixmestery: yes.16:24
mestery#action banix and alagalah to flesh out the tables started in the document, possibly adding a diagram showing the relationship16:24
prasadvis the endpoint to group association automatic16:24
mesterybanix alagalah: Thanks!16:24
prasadvi mean say a vm gets created and does it get associated to groups automatically because there is a metadata for vm in that group16:24
banixprasadv: so in some case16:25
banixso if the network is part of the group, then all ports on it would be automatically. For ports, I assume it should be specified explicitly.16:25
rudraruggebanix: if network has to be associated with a group then how many UUIDs are in the picture16:25
*** alazarev has joined #openstack-meeting-alt16:25
prasadvbanix: the association might not be network only right?16:26
rudraruggeendpoint UUID (pointing to network UUID). Group UUID containing this network UUID?16:26
banixrudrarugge: yes16:26
rudraruggeI meant group UUID containing this endpoint UUID which in effect points to a network UUID16:26
rudraruggeok16:26
prasadvI could have say load balancing group that I would like to represent.16:26
alagalahReliance on UUID as a form of naming abstraction is key IMHO... makes service chaining more generic16:27
alagalahRely on the underlying object and its methods it represents (and its data model) ...16:27
thinrichsprasadv: are you concerned that the size of these groups will be massive?16:28
prasadvbanix: what  I mean is is Nova pass this group association to neutron when a endpoint gets created so this may be automatic16:28
*** ashaikh has joined #openstack-meeting-alt16:28
mesteryprasadv: I follow that now. The interactions with nova are something we have not fleshed out quite yet.16:28
prasadvthinrichs: no I want to know that there is automatic way to associate16:28
mesteryOnce we finalize the object model here, I think we should look at that next, as it's the obvious first use case.16:28
banixprasadv: So if the network is the endpoint, adding a new VM which will require a new port with put that endpoint/port/vm in the group...16:28
prasadvmestery: thanks16:29
banixprasadv mastery: yes that would a neat first use case16:29
prasadvbanix: network is simple but groups might be more narrow than that16:29
banixprasadv: yes agree16:30
*** SergeyLukjanov has joined #openstack-meeting-alt16:30
s3wonga VM should not be an endpoint, right? rather a port on a VM is an endpoint?16:30
mestery#info The nova use case is an interesting first one to cover once the object model is completed.16:30
prasadvjust wanted to make sure that a user can pass metadata of some sort during endpoint creation which will then get reflected to neutron16:31
*** colinmcnamara has joined #openstack-meeting-alt16:31
*** colinmcn_ has joined #openstack-meeting-alt16:31
*** SergeyLukjanov is now known as _SergeyLukjanov16:31
*** _SergeyLukjanov is now known as SergeyLukjanov16:31
banixprasadv: makes sense; we have to figure this out.16:31
mesterys3wong: Correct.16:31
*** bdpayne has joined #openstack-meeting-alt16:32
banixs3wong: yes; i oversimplified in above statement.16:32
mesterySo, we have 30 minutes left, should we discuss the Actions section banix added next?16:32
banixs3wong: when I used "endpoint/port/vm"16:32
*** SergeyLukjanov is now known as _SergeyLukjanov16:32
s3wongbanix: cool :-)16:32
mesteryI think that is the only other thing new on the agenda for this week.16:32
*** yahongdu has quit IRC16:32
mesteryElse we can open it up for open discussion16:32
*** _SergeyLukjanov is now known as SergeyLukjanov16:33
*** yahongdu has joined #openstack-meeting-alt16:33
banixmestery: yes lets look at the rest16:33
banixs3wong added the action type descriptions16:33
mestery#topic Action Types Discussion16:33
*** openstack changes topic to "Action Types Discussion (Meeting topic: networking_policy)"16:33
s3wongmestery: for the action section, banix and I talked about it, and the action description should not be Neutron objects, so I will update16:33
mesterys3wong banix: Thanks for adding those into the document.16:33
mesterys3wong: OK, that makes sense.16:34
banixmestery: sure16:34
mestery#action s3wong to update action section in document to not reflect neutron objects directly.16:34
*** colinmcn_ is now known as colinmcnamara_16:35
*** cloudpie has joined #openstack-meeting-alt16:35
mesterysc68cal: It may be good for you to look at the examples of using actions for QoS in the document, would appreciate your feedback there.16:35
sc68caladd an action item for me, I've glanced at it a couple times but my concern is how to get from where my code is to where it needs to be to integrate with this work16:36
sc68calmostly I just need to do a little more research and catch up with you guys16:36
dttocsAs I just noted in the doc comments, I think we need a set of core action attributes that all plugins must implement and then some mechanism to extend.  Make sense?16:36
alagalahsc68cal Are you scottd in the gdoc ?16:36
mestery#action sc68cal Look over action example for QoS and provide feedback16:36
alagalahdttocs ...16:36
sc68calalagalah: no16:36
dttocsNo scottd=dttocs=Scott Drennan - Nuage Networks16:36
s3wongsc68cal: perhaps we can discuss the use case and see whether the model fit?16:36
alagalahdttocs  I see your comments to my comments on QoS in the gdoc, thanks16:37
*** rongze_ has quit IRC16:37
*** mcohen2 has joined #openstack-meeting-alt16:38
banixdttocs: yes we should specify a minim set to begin with.16:38
s3wongdttocs: yes, that makes sense16:38
thinrichsdttocs: is it the action attributes or the action functionality that we want all plugins to implement?16:38
mesteryI would advise folks who are interested to review the action section and provide feedback in the google doc in detail.16:38
s3wongactions are also classifed by action_type - and currently the first set of primitives are type security, qos, and redirect16:39
mesterythinrichs dttocs: I think it has to be the action attributes vs. the functionality.16:40
dttocsthinrichs: I think this goes back to the initial discussion about what common behaviour/capabilities we have between plugins16:41
thinrichsSo 1 plugin could interpret 'redirect' in a completely different way than another plugin?16:41
thinrichsMeaning that 1 plugin could interpret 'redirect' to mean 'push packets through a proxy' and another to mean 'drop packets'?16:42
s3wongthinrichs: one plugin can implement it differently, but the end behavior should be the same16:42
thinrichss3wong: agreed.16:42
mesteryYes, what s3wong indicated.16:42
thinrichss3wong: wouldn't that mean we need to spell out the meaning (functionality) of those actions?16:43
mesterySo that means the action's need to be defined such that the end goal makes is understood.16:43
*** SumitNaiksatam has quit IRC16:43
mesteryThe semantics of how each plugin reaches the end goal is the nebulous part.16:43
s3wongthinrichs: absolutely16:43
mestery:)16:43
dttocsthinrichs:  Taking QoS as an example, DHCP marking would be common behaviour, but if we added policing/shaping as a common attribute every network device implements those differently16:43
mesteryI think we all just said the same thing.16:43
s3wongmestery: right :-)16:43
prasadvcan a plugin say that there are certain types it does not implement, and how does that get reflected16:44
thinrichsmestery: agreed, except I don't see a end-goal as part of the doc, or am I missing it?16:44
*** akuznetsov has quit IRC16:44
mesterythinrichs: I need to re-read the document myself at this point to verify if that's in there. :)16:44
s3wongprasadv: I believe that's what dttocs indicated above. A core set where all plugins have to implement16:44
*** venkatesh has quit IRC16:44
mesteryprasadv: If a plugin doesn't implement one, it would fail the API call for those attributes I suspect, rather than silently ignore them.16:44
s3wongand for those that are not supported, the API call should fail16:45
s3wong(the non-required ones, that is)16:45
thinrichsmastery prasadv: I would imagine we'd want more transparency than just "tried to add a policy statement and got an error".16:45
sc68calHave we decided on the minimum requirements for qos policies that each plugin must support?16:45
thinrichsI would think Heat would want to know which policy fragment the plugin supports and then utilize that policy fragment.16:46
prasadvinstead of failing when called, wouldnt it better that user know that it does not implement and hence in UI or something it get blanked out16:46
s3wongsc68cal: we have not. The writing at this point is to translate directly into DSCP marking16:46
mesteryprasadv thinrichs: I didn't mean to get into specifics of the failure case, just that if a plugin doesn't support things, it has to fail and somehow alert the user.16:46
sc68cals3wong: OK, i'll add a comment to the doc highlighting another use case16:47
michsmitwouldn't multiple plugins be possible ?  and each may deal with only part of the policy ?16:47
s3wongsc68cal: certainly16:47
*** brents has joined #openstack-meeting-alt16:47
banixSo i think the question is if the extension can be asked what it supports. Is there a mechanism for that used by other extensions?16:47
prasadvmestery: my point is that there could be a query where one would return what types it supports.16:47
s3wongmichsmit: that sounds complicated...16:47
s3wongmichsmit: who is going to do the coordination and dispatch?16:48
mesterymichsmit: I could see that if we're talking ML2, which uses an L3 service plugin, and part of this is handled by the L2 MechanismDriver and part by the L3 ServicePlugin.16:48
thinrichsprasadv: I think your suggestion is necessary as well.16:48
mesterymichsmit: But that would only apply in an ML2/ML3 world I thnk.16:48
banixmastery michsmit: yes. In the new world order: ML2 only :)16:49
michsmitmestery:  exactly. I was assuming an ML2 world16:49
mesteryOK, so we have 10 minutes left, I'd like to discuss some next steps for the coming week now.16:49
mestery#topic Next Steps For the Next Meeting16:49
*** openstack changes topic to "Next Steps For the Next Meeting (Meeting topic: networking_policy)"16:50
ywumestery: is networking policy and ML2 are mutual exclusive?16:50
* mestery likes that topic title for some reason.16:50
mesteryymu: No, they are not.16:50
mesteryOK, so we have a bunch of action items for next week.16:50
*** alazarev has quit IRC16:50
mesteryI think we as a team should really strive to come to agreement on the document now as much as possible in the next 2 weeks.16:50
s3wongmesteryL though we may want to avoid making group-policy exclusively work with ML216:50
mesterys3wong: Completely agree, this is not ML2 specific.16:51
mesterySo to that end, lets please iterate over the Google Document this week.16:51
banixmestery: agreed. Lets flash out the difference and address them as soon as we can16:51
s3wongbefore Chirstmas :-) I see what you guys did there :-)16:51
*** jcooley_ has joined #openstack-meeting-alt16:51
mesteryIf something isn't clear, please start a thread on the openstack-dev ML using tags "[neutron] [policy]"16:51
mesterys3wong: :)16:51
*** rsblendido has joined #openstack-meeting-alt16:52
*** rossella_s has joined #openstack-meeting-alt16:52
mesterySound like a plan for the next week?16:52
banixyes16:52
s3wongsure16:52
thinrichsYep16:52
mesteryPerfect!16:52
mesteryOK, thanks to everyone for attending today!16:52
mesteryI need to drop out of this a bit early, so will end the meeting now.16:52
banixThank you.16:52
s3wongThanks!16:53
mesteryLets iterate on the ML, Google Doc, and #openstack-neutron if needed as well.16:53
prasadvthanks16:53
ywuThanks!16:53
mesterySee you all next week!16:53
mestery#endmeeting16:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:53
openstackMeeting ended Thu Dec  5 16:53:09 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:53
banixThanks everybody; see you on the doc!16:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2013/networking_policy.2013-12-05-16.00.html16:53
*** prasadv has quit IRC16:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2013/networking_policy.2013-12-05-16.00.txt16:53
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2013/networking_policy.2013-12-05-16.00.log.html16:53
*** songole has quit IRC16:53
*** sc68cal has left #openstack-meeting-alt16:53
*** IlyaE has quit IRC16:53
*** jvrbanac has joined #openstack-meeting-alt16:53
*** michsmit has left #openstack-meeting-alt16:53
*** jcooley_ has quit IRC16:54
*** jcooley_ has joined #openstack-meeting-alt16:55
*** mjbright_ has quit IRC16:56
*** alagalah has left #openstack-meeting-alt16:56
*** hemanthravi has quit IRC16:56
*** jcooley_ has quit IRC16:57
*** jcooley_ has joined #openstack-meeting-alt16:57
*** pballand has quit IRC16:58
*** mcohen2 has quit IRC16:58
*** s3wong has quit IRC17:01
*** jcooley_ has quit IRC17:02
*** SumitNaiksatam has joined #openstack-meeting-alt17:04
*** rnirmal has quit IRC17:05
*** Dinny_ has quit IRC17:05
*** rnirmal has joined #openstack-meeting-alt17:05
*** jcooley_ has joined #openstack-meeting-alt17:06
*** jasonb365 has quit IRC17:07
*** rraja|afk has joined #openstack-meeting-alt17:08
*** rudrarugge has quit IRC17:08
*** jswarren has joined #openstack-meeting-alt17:10
*** Barker has joined #openstack-meeting-alt17:11
*** jswarren has quit IRC17:11
*** jmontemayor has joined #openstack-meeting-alt17:11
*** jswarren has joined #openstack-meeting-alt17:12
*** thinrichs has quit IRC17:13
*** julim has quit IRC17:16
*** julim has joined #openstack-meeting-alt17:17
*** ashaikh has quit IRC17:19
*** jasonb365 has joined #openstack-meeting-alt17:20
*** jasonb365 has quit IRC17:21
*** vbellur has joined #openstack-meeting-alt17:21
*** jasonb365 has joined #openstack-meeting-alt17:25
*** twoputt_ has joined #openstack-meeting-alt17:27
*** twoputt__ has joined #openstack-meeting-alt17:27
*** jtomasek has quit IRC17:31
*** jmontemayor has quit IRC17:32
*** Barker has quit IRC17:32
*** glenng has joined #openstack-meeting-alt17:35
*** glenng has left #openstack-meeting-alt17:36
*** markwash has quit IRC17:38
*** sarob has quit IRC17:39
*** allyn has quit IRC17:39
*** sarob has joined #openstack-meeting-alt17:40
*** zhiyan has quit IRC17:41
*** nadya has joined #openstack-meeting-alt17:43
*** nadya is now known as Guest7490517:43
*** sarob has quit IRC17:44
*** betsy has left #openstack-meeting-alt17:44
*** Guest74905 has quit IRC17:46
*** jcooley_ has quit IRC17:47
*** jcooley_ has joined #openstack-meeting-alt17:48
*** sarob has joined #openstack-meeting-alt17:49
*** aignatov has joined #openstack-meeting-alt17:50
*** denis_makogon is now known as bot_bot17:50
SergeyLukjanovsavanna team meeting will be here in 10 mins17:52
*** vbellur has left #openstack-meeting-alt17:52
*** NikitaKonovalov has joined #openstack-meeting-alt17:52
*** jcooley_ has quit IRC17:52
*** ashaikh has joined #openstack-meeting-alt17:53
*** rudrarugge has joined #openstack-meeting-alt17:55
*** mattf has joined #openstack-meeting-alt17:55
*** jcooley_ has joined #openstack-meeting-alt17:56
*** sarob has quit IRC17:57
*** demorris_ has joined #openstack-meeting-alt17:57
*** sarob has joined #openstack-meeting-alt17:58
*** demorris has quit IRC18:00
*** demorris_ is now known as demorris18:00
*** aignatov has quit IRC18:01
*** MikeSpreitzer has joined #openstack-meeting-alt18:01
*** bob_nettleton has joined #openstack-meeting-alt18:01
SergeyLukjanovsavanna folks, are you around?18:01
*** tri2sing has joined #openstack-meeting-alt18:02
*** nati_ueno has joined #openstack-meeting-alt18:02
*** sarob has quit IRC18:02
* SergeyLukjanov checking the meetings schedule18:03
*** rsblendido has quit IRC18:03
*** rossella_s has quit IRC18:03
*** dttocs has quit IRC18:03
mattfjust us mice18:03
*** aignatov has joined #openstack-meeting-alt18:04
*** amytron_ has joined #openstack-meeting-alt18:04
NikitaKonovalovo/18:04
*** amytron has quit IRC18:04
*** amytron_ is now known as amytron18:04
*** jmaron has joined #openstack-meeting-alt18:04
aignatovhi all18:04
*** akuznetsov has joined #openstack-meeting-alt18:04
jmaronhi18:04
SergeyLukjanov#startmeeting savanna18:05
openstackMeeting started Thu Dec  5 18:05:06 2013 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:05
*** openstack changes topic to " (Meeting topic: savanna)"18:05
openstackThe meeting name has been set to 'savanna'18:05
SergeyLukjanov#topic Agenda18:05
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:05
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SavannaAgenda18:05
SergeyLukjanov#topic Icehouse-1 released18:05
*** openstack changes topic to "Icehouse-1 released (Meeting topic: savanna)"18:05
aignatovhurraahhhh!18:05
SergeyLukjanov#info the icehouse-1 (2014.1.b1) was released18:05
SergeyLukjanovit's about the main savanna code18:05
*** jspeidel has joined #openstack-meeting-alt18:05
SergeyLukjanovi'll push corresponding tags to other projects tonight18:06
SergeyLukjanov#info python-savannaclient 0.4.0 was released too18:06
mattfyay18:06
SergeyLukjanovin Mon or Tue I think18:06
SergeyLukjanovmattf, your change was already landed ;)18:07
SergeyLukjanovthis release of main savanna code was driven by ttx18:08
SergeyLukjanovso, now we're are really following OpenStack release cycle :)18:08
mattfalso yay18:08
aignatovthat's very cool18:08
SergeyLukjanovany question?18:09
mattfnooe18:09
SergeyLukjanov#topic Action items from the last meeting18:09
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"18:09
SergeyLukjanov#link http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-11-21-18.04.html18:09
SergeyLukjanovthere are no action items :)18:09
SergeyLukjanov#topic Roadmap update / cleanup18:10
*** colinmcnamara has quit IRC18:10
*** colinmcnamara_ has quit IRC18:10
*** openstack changes topic to "Roadmap update / cleanup (Meeting topic: savanna)"18:10
*** demorris has quit IRC18:10
SergeyLukjanov#link https://wiki.openstack.org/wiki/Savanna/Roadmap18:10
SergeyLukjanovI've added some points that was discussed on summit18:10
mattfglad to see that18:10
*** derekh has quit IRC18:10
*** alazarev has joined #openstack-meeting-alt18:11
SergeyLukjanov#action SergeyLukjanov to check that all blueprints created and ping guys to make them if not18:11
SergeyLukjanov#action SergeyLukjanov add links to the blueprints to roadmao18:11
SergeyLukjanov#topic News / updates18:11
*** openstack changes topic to "News / updates (Meeting topic: savanna)"18:11
SergeyLukjanovguys, please18:11
mattfno news from me this week, mostly turkey recovery18:12
SergeyLukjanov#info first devstack-gate jobs was added to savanna (non-voting)18:12
*** markwash has joined #openstack-meeting-alt18:12
aignatovmy notes: I'm continue working on patch dmitryme sent on the review18:12
aignatovit's about Heat integration18:12
SergeyLukjanovabout the d-g jobs - savanna now installed by devstack in them18:12
SergeyLukjanovso, it checks devstack integration at least18:12
jspeidelnot much from me this week18:13
SergeyLukjanovI'm working now on initial set of api tests for the tempest18:13
aignatovd-g jobs? what is d-g?18:13
aignatovgating?18:13
SergeyLukjanovdevstack-gate == d-g18:13
mattfSergeyLukjanov, that's interesting to me, this is for python-savannaclient?18:13
SergeyLukjanovmattf, nope18:13
*** kgriffs is now known as kgriffs_afk18:13
SergeyLukjanovin tempest api tests use own simple client18:13
aignatovSergeyLukjanov: that's exactly I thought about :)18:14
*** brents has quit IRC18:14
SergeyLukjanovit's for testing api w/ dep on client18:14
SergeyLukjanovany other news?18:14
jmaronworking on rack awareness for HDP plugin and disconnected installation (Installation in envs with no access to external repos)18:14
*** eankutse has quit IRC18:14
* mattf is looking forward to ^^18:14
SergeyLukjanovjmaron, great18:14
*** harlowja has joined #openstack-meeting-alt18:14
*** kgriffs_afk is now known as kgriffs18:14
SergeyLukjanovmattf, sorry, typo in my msg18:15
SergeyLukjanovit's for testing api *W/O* dep on client18:15
mattfi'm guessing w/o dep?18:15
SergeyLukjanovyup18:15
SergeyLukjanovas the first step will write api test in tempest18:16
SergeyLukjanovand then will transform out savanna/tests/integration to the scenario tests in tempest18:16
SergeyLukjanovso, after that we'll be able to use tempest in savanna-ci18:16
*** colinmcnamara has joined #openstack-meeting-alt18:16
SergeyLukjanovand propably the dull d-g approach18:16
*** crobertsrh has joined #openstack-meeting-alt18:17
*** rraja|afk has quit IRC18:17
*** colinmcn_ has joined #openstack-meeting-alt18:17
SergeyLukjanov#info savanna-ci still works non-deterministic18:17
*** IlyaE has joined #openstack-meeting-alt18:17
SergeyLukjanovcrobertsrh, any news?18:17
SergeyLukjanovmattf, crobertsrh, do you now about what tmckay doing atm?18:18
crobertsrhNothing major.  Most (maybe all?) of the bug fixes I was working on are ready.18:18
crobertsrhI'll be looking through blueprints/bugs for icehouse and starting work on those.18:18
mattfSergeyLukjanov, yeah, he's around18:18
SergeyLukjanovok, looks like that's all for news18:20
SergeyLukjanovGeneral discussion18:20
SergeyLukjanov#topic General discussion18:20
*** openstack changes topic to "General discussion (Meeting topic: savanna)"18:20
SergeyLukjanovnothing interesting to tell about from my side18:20
*** yogesh_ has joined #openstack-meeting-alt18:20
MikeSpreitzerI'd like to ask about that patch that uses Heat18:21
MikeSpreitzerAt the end of the summit I asked why savanna is not using heat, and was told some reasons.18:21
SergeyLukjanovMikeSpreitzer, sure18:21
MikeSpreitzerDoes the patch address them, and if so, how?18:21
SergeyLukjanovMikeSpreitzer, there are mostly all needed features available in Havana Heat18:22
*** brents has joined #openstack-meeting-alt18:22
*** dmitryme has joined #openstack-meeting-alt18:22
SergeyLukjanovbut there is a bunch of smaill improvements needed by savanna18:22
aignatovactually current our implemtation is pretty simple and we use all of needed for savanna18:22
SergeyLukjanovfor example, a-a could be implelemented but it'll work pretty slow18:22
SergeyLukjanova-a == anti-affinity18:23
aignatovwe didnt18:23
aignatoveven try this Sergey18:23
dmitrymeaignatov: we're pretty sure it is slow18:23
alazarevand as I understand current heat patch is only for VMs provisioning, other staff will still be in savanna18:23
MikeSpreitzerSo the current patch makes no attempt at anti-affiniity for VMs, right?18:24
SergeyLukjanovalazarev, yup, it's about resources orchestration18:24
dmitrymealazarev: other stuff will be handler by guest agent18:24
aignatovyes, other stuff, alazarev will be moved to guest agents I think18:24
MikeSpreitzerAnother gap I was told about is there is no way to ask for compute and storage to be co-located.18:24
dmitrymeMikeSpreitzer: it does anti-affinity, but we expect it to work very slow18:24
aignatovMikeSpreitzer: AA is on TODO list in this patch18:25
*** SlickNik has left #openstack-meeting-alt18:25
ruhealazarev: correction - other stuff will be done by corresponding plugin. it's important to note that some plugins utilise vendor-specific tools (such as Ambari) to install and configure Hadoop18:25
SergeyLukjanovruhe, yeah, very important note18:25
MikeSpreitzerruhe, you mean heat plugin, right?18:25
ruheMikeSpreitzer, no. savanna plugi18:25
SergeyLukjanovMikeSpreitzer, it's about vanilla or hdp plugins18:25
ruhe*plugin18:25
dmitrymeMikeSpreitzer: yes, that is true, there is no collocation18:26
SergeyLukjanovMikeSpreitzer, I think that it should be on the heat's roadmap18:26
SergeyLukjanovbtw does anyone have question about releasing?18:26
MikeSpreitzerI am trying to get it on nova+cinder's roadmap (the colocation)18:26
ruhehere is doc about savanna plugin http://docs.openstack.org/developer/savanna/userdoc/plugins.html18:27
SergeyLukjanovMikeSpreitzer, I think that it could be easily supported in Heat right after it'll be landed to nova+cinder18:27
MikeSpreitzerSergey: I also hope this18:27
SergeyLukjanovMikeSpreitzer, do you any blueprints or threads on this topic?18:27
SergeyLukjanovhave*18:28
MikeSpreitzerYes, there were several related18:28
MikeSpreitzerCurrent roadmap is very incremental  :-(18:28
*** sarob has joined #openstack-meeting-alt18:28
MikeSpreitzerIt starts with the instance group API extension to nova18:28
SergeyLukjanovand there was some threads about holistic scheduling18:28
MikeSpreitzeryes, that's what I am talking about18:29
SergeyLukjanovMikeSpreitzer, yup, we're hope that group api will be approved and landed18:29
*** tmckay has joined #openstack-meeting-alt18:29
MikeSpreitzerhttps://docs.google.com/document/d/17OIiBoIavih-1y4zzK0oXyI66529f-7JTCVj-BcXURA/edit?pli=1 is more like it, but that's not the first step18:30
MikeSpreitzereven that URL is only about Nova, we want to go cross-service after that18:30
SergeyLukjanovMikeSpreitzer, what do you think about possibility to land instance groups in icehouse?18:30
MikeSpreitzerMy co-consipirators promised patches this week for the first step18:31
MikeSpreitzerbut that promise was made last week, I think current nova plans may delay a bit18:31
MikeSpreitzerbut I do hope for the first step in Icehouse for sure.18:31
aignatovI was on this design session where it was discussed :) really interesting feature - AA between node groups and AA between instances within single node group18:31
MikeSpreitzerFirst step is only instance groups with no internal structure18:31
MikeSpreitzerYes, I definitely want groups with internal structure18:32
SergeyLukjanovMikeSpreitzer, awesome, please, add me to reviewers when the patch will be created18:32
MikeSpreitzerOK18:32
MikeSpreitzerHave been doing Hadoop exercises with IBM research code that is pure OpenStack client18:32
MikeSpreitzerbut roughly similar in approach18:32
SergeyLukjanovMikeSpreitzer, internal structure like nested groups?18:32
MikeSpreitzeryes18:32
SergeyLukjanovMikeSpreitzer, cool18:32
*** sarob has quit IRC18:33
tmckaySergeyLukjanov, hi.  Sorry I'm late :)18:33
SergeyLukjanovtmckay, np ;)18:33
SergeyLukjanovtmckay, any news/updates?18:33
*** ylobankov has joined #openstack-meeting-alt18:33
tmckayI see you asking about me in the log.  I have been on extra-savanna stuff for a few weeks, but happily I think it is mostly put to rest.18:33
akuznetsovMikeSpreitzer will your scheduler be aware about rack location?18:34
SergeyLukjanovtmckay, i1 was partially released released, details in logs :018:34
*** IlyaE has quit IRC18:34
tmckayLooking for where to go next.18:34
tmckayMaybe hdfs storage for EDP objects>18:34
tmckay?18:34
MikeSpreitzerSee https://docs.google.com/drawings/d/1nridrUUwNaDrHQoGwSJ_KXYC7ik09wUuV3vXw1MyvlY/edit for an example of structured input18:34
SergeyLukjanovtmckay, we have an idea to make it able to store jobs in swift in tell Oozie to take them from it18:34
MikeSpreitzerYes, we worked examples that support Hadoop rack awareness, want that in Nova+cinder18:35
SergeyLukjanovtmckay, it'll make us avoid sending jars18:35
tmckayokay.  Is there a doc or a pad somewhere talking about this?18:35
*** lblanchard has quit IRC18:35
SergeyLukjanovtmckay, just thoughts, we can discuss it in out channel18:35
tmckayk18:36
SergeyLukjanovtmckay, mainly we're thinking about it due to the creating guest agents18:36
akuznetsovMikeSpreitzer cool18:36
aignatovtmckay: also EDP must have improvements like applying command lime arguments for jobs18:37
SergeyLukjanovyup, I'm really missing pi job :(18:37
tmckayaignatov, ack.  I will be happy to work on EDP again.18:37
aignatovalso we have Hive not working in secure way or not working at all, I think we need to make it working somehow :)18:38
aignatovhive with swift I mean18:38
tmckaylots to do.18:38
*** dmitryme has quit IRC18:38
SergeyLukjanovtmckay, yeah, a lot of tbd stuff in EDP too18:39
SergeyLukjanovtmckay, and you the main EDP dev for icehouse I think :)18:39
akuznetsovalso we can change auth schema for working with Swift, currently user should give username/password to Savanna, we should change this to oAuth18:40
aignatovbtw, here is a lot about EDP discussed: https://etherpad.openstack.org/p/savanna-icehouse-roadmap18:40
tmckayreally?  Has nprivalova abandoned me? ;-)18:40
SergeyLukjanovtmckay, she's working on ceilo atm18:40
tmckayOkay.  I'll do my best. 8-)18:41
SergeyLukjanovgreat :)18:41
aignatovcool18:41
aignatovtmckay: you can contact me or akuznetsov about EDP related questions18:42
MikeSpreitzerBTW, if you're willing to back up, can someone explain why the current anti-affinity solution is expected to be slow?18:43
tmckayalright, wonderful.  I'll take a look through current blueprints, bugs, roadmap, etc18:43
SergeyLukjanovMikeSpreitzer, sure18:43
SergeyLukjanovMikeSpreitzer, in heat you can specify scheduler_hints18:43
*** rudrarugge has quit IRC18:43
SergeyLukjanovlike we're doing it in savanna now18:44
*** dmitryme has joined #openstack-meeting-alt18:44
SergeyLukjanovsmth like "don't setup this instance on host X, Y, Z"18:44
SergeyLukjanovcorrection: on host where instance X, Y, Z are running18:44
SergeyLukjanovand we need IDs of instances18:44
SergeyLukjanovin heat it'll generate dependenciesbetween instances18:45
SergeyLukjanovand each new instance will wait for active state of prev. to take ID18:45
MikeSpreitzerso the template asks for a chain of VMs, each not on any of the hosts used for earlier VMs, is that it?18:45
MikeSpreitzerah, it's startup that is slow18:46
*** amcrn has joined #openstack-meeting-alt18:46
SergeyLukjanovwe'are not check it atm, but it was confirmed but heat folks18:46
MikeSpreitzerbecause it's linear18:46
SergeyLukjanovexactly!18:46
MikeSpreitzergot it, thatnks18:46
MikeSpreitzerthanks18:46
SergeyLukjanovnp18:46
MikeSpreitzerit's also not small, template size is quadratic in number of slaves18:46
dmitrymeyep, it is true18:47
*** kgriffs is now known as kgriffs_afk18:47
SergeyLukjanovI hope that it probably could be improved in heat due the fact that ID available right after the instance creation response received18:47
MikeSpreitzeryes, it should only have to wait for ID.  But even that is dismaying for a linear arrangement.18:48
SergeyLukjanovMikeSpreitzer, it's not bad18:48
SergeyLukjanovbecause id is available after sending instance creation request18:48
dmitrymeour old pre-Heat code launched instances linearly and it worked pretty fast18:49
SergeyLukjanovin savanna we're creating instances linearly18:49
* tmckay has to drop again, I'll check the log 18:49
SergeyLukjanovtmckay, have a good day18:49
SergeyLukjanovand it setups 200 node cluster in 5 mins18:49
dmitrymethe launch of 200-node cluster took around 5 minutes18:49
dmitrymeand only part of that time was launching instances18:50
*** kbroughton has joined #openstack-meeting-alt18:50
SergeyLukjanov50-50 I think18:50
dmitrymeI believe it was not more around 1 minute18:50
dmitryme* just around 1 minute18:50
MikeSpreitzerthat's pretty good18:51
MikeSpreitzeryou've got an unusually non-broken OpenStack installation18:52
MikeSpreitzer:-)18:52
aignatovMikeSpreitzer: lol!18:52
dmitryme:-) not exactly, we fix it after each second launch18:52
MikeSpreitzeroh18:52
SergeyLukjanovyeah, that's the dark side of this test :)18:53
SergeyLukjanovbtw http://logs.openstack.org/06/60306/1/check/check-tempest-dsvm-savanna-neutron/3f1d7d1/logs/screen-savanna.txt.gz18:53
*** eankutse has joined #openstack-meeting-alt18:53
SergeyLukjanov^^ savanna screen logs from the first correctly working d-g job18:53
ruhehooray!18:53
*** tmckay has quit IRC18:53
*** eankutse has quit IRC18:54
*** jmontemayor has joined #openstack-meeting-alt18:54
*** eankutse has joined #openstack-meeting-alt18:54
dmitrymeyep, that is cool18:55
SergeyLukjanovanything more to discuss?18:55
SergeyLukjanovout timeslot ends in 5 mins18:55
SergeyLukjanovok, let's end it18:56
SergeyLukjanovthank you all guys18:56
SergeyLukjanov#info JFYI you can always use openstack-dev@lists.openstack.org mailing lists and #savanna irc channel to find us and ask your questions18:56
SergeyLukjanov#endmeeting18:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:56
openstackMeeting ended Thu Dec  5 18:56:39 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-12-05-18.05.html18:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-12-05-18.05.txt18:56
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-12-05-18.05.log.html18:56
*** jspeidel has left #openstack-meeting-alt18:56
SergeyLukjanovhave a good day/night18:56
*** demorris has joined #openstack-meeting-alt18:56
MikeSpreitzerU218:56
*** MikeSpreitzer has quit IRC18:57
*** bob_nettleton has left #openstack-meeting-alt18:57
*** sarob has joined #openstack-meeting-alt18:58
*** tmckay has joined #openstack-meeting-alt19:00
*** mattf has left #openstack-meeting-alt19:01
*** tmckay has left #openstack-meeting-alt19:01
*** sarob has quit IRC19:03
*** sarob has joined #openstack-meeting-alt19:03
*** derekh has joined #openstack-meeting-alt19:08
*** noslzzp has quit IRC19:08
*** sarob has quit IRC19:08
*** noslzzp has joined #openstack-meeting-alt19:09
*** NikitaKonovalov has quit IRC19:10
*** eankutse1 has joined #openstack-meeting-alt19:10
*** eankutse has quit IRC19:11
*** noslzzp has quit IRC19:14
*** dmitryme has quit IRC19:14
*** eankutse1 has quit IRC19:15
*** eankutse has joined #openstack-meeting-alt19:15
*** jtomasek has joined #openstack-meeting-alt19:18
*** ywu has quit IRC19:19
*** kgriffs_afk is now known as kgriffs19:20
*** crobertsrh has left #openstack-meeting-alt19:22
*** derekh has quit IRC19:25
*** jasonb365 has quit IRC19:27
*** tri2sing has quit IRC19:33
*** gokrokve has quit IRC19:36
*** lblanchard has joined #openstack-meeting-alt19:36
*** tanisdl has joined #openstack-meeting-alt19:43
*** jtomasek has quit IRC19:43
*** jcooley_ has quit IRC19:44
*** jcoufal has joined #openstack-meeting-alt19:46
*** electrichead has joined #openstack-meeting-alt19:50
*** woodster has joined #openstack-meeting-alt19:50
*** reaperhulk has joined #openstack-meeting-alt19:53
*** dev_warlord has joined #openstack-meeting-alt19:53
*** gokrokve has joined #openstack-meeting-alt19:56
*** jasonb365 has joined #openstack-meeting-alt19:58
*** yogesh_ has quit IRC19:58
*** dieseldoug has joined #openstack-meeting-alt19:59
*** yogesh_ has joined #openstack-meeting-alt19:59
*** jcooley_ has joined #openstack-meeting-alt20:01
*** nadya has joined #openstack-meeting-alt20:01
*** nadya is now known as Guest5737920:01
jraim#startmeeting Barbican Weekly Meeting20:01
openstackMeeting started Thu Dec  5 20:01:43 2013 UTC and is due to finish in 60 minutes.  The chair is jraim. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: Barbican Weekly Meeting)"20:01
openstackThe meeting name has been set to 'barbican_weekly_meeting'20:01
jraim#topic Barbican tasks for incubation20:02
*** openstack changes topic to "Barbican tasks for incubation (Meeting topic: Barbican Weekly Meeting)"20:02
jraimFor those that haven't used the bot before, here are the commands: https://wiki.debian.org/MeetBot20:02
woodster#link https://wiki.openstack.org/wiki/Barbican/Incubation20:03
*** lblanchard has quit IRC20:03
jraimAnother minute or two and we'll get started20:03
*** lblanchard has joined #openstack-meeting-alt20:04
*** dmitryme has joined #openstack-meeting-alt20:05
*** hockeynut has joined #openstack-meeting-alt20:05
jraimAlright, let's get rolling20:05
jraim#info I'd like to cover the status of our current tasks, then we can see if anyone has any new ones20:05
jraim#Info Let's start with moving python-barbican client to stackforge, where are we on that?20:06
*** SheenaG has joined #openstack-meeting-alt20:06
jraimelectrichead ping20:06
electrichead#info the PR to infra to get the project started has been submitted20:06
electrichead#link https://review.openstack.org/#/c/60101/20:07
jraimgreat, so we just need to wait for that to be merged?20:07
electricheadyes, also we've added a new project to launchpad to track python-barbicanclient20:07
electrichead#link https://launchpad.net/python-barbicanclient20:07
jraimgreat20:08
jraim#info Alright, moving on to prb and requirments.... reaperhulk?20:08
reaperhulk#info There's currently a PR in gerrit for aligning our dependencies with global requirements and migrating to using pbr for setup.py20:08
reaperhulk#link https://review.openstack.org/#/c/59817/20:08
jraimSo the only thing left in conflict there is the Celery dependency, right?20:08
reaperhulk#info We still have our celery dependency while investigating oslo messaging so this won't be 100% complete until after that is complete20:09
reaperhulkCorrect20:09
woodster#info Regarding oslo.messaging: Looking at nova and climate pull requests now, working on a prototype for Barbican to start reviewing later today20:09
jraimHow far do you think the current implementation is from something we could merge? Do we have a lot of work left? Or are we just checking to see how well we did?20:09
reaperhulkjraim: is that wrt global reqs or woodster's statements?20:10
woodsterI have the basic peices in place now, but trying to get it working with rabbit MQ cluster20:10
jraimsorry, woodster20:10
jraimwoodster is the implementation in parity with what we had? Or is there still work we need to do there?20:10
woodsterI will post that CR not matter what today, but hopefully will have it working completely (with rough edges) too20:11
jraimokay, great20:11
jraim#action woodster will post the PR for olso.messaging in the next day our two for review20:11
woodsterit doesn't require much change to the api/resource layer or the task layer, just the queue structure in between20:11
jraim#info okay, moving to the devstack-gate20:11
*** atiwari has joined #openstack-meeting-alt20:11
jraimI think this is blocked until we resolve the other issues, yes?20:11
*** cweid has quit IRC20:11
reaperhulkit is. we need full global requirements alignment before we can gate there20:12
jraimokay20:12
woodsterremoving celery should be the last part of that, correct?20:12
reaperhulkcorrect20:12
jraim#action barbican will tackle the devstack gate once oslo.messaging is merged20:12
*** abramley has joined #openstack-meeting-alt20:13
electricheadI think we may also need to start looking at the actual devstack integration20:13
electricheadadding the gate seems easy enough20:13
reaperhulkgood point, I have no idea what that entails right now20:13
jraimyou mean getting barbican deployed with teh devstack script?20:13
electricheadwe have the option of not blocking on that gate20:13
electricheadyeah, the gate is so that zuul knows to run devstack tests20:13
electricheadbut I think it may also need something to run20:13
jraimthat seems like a good idea20:14
jraim#action barbican will look at integrating into devstack20:14
*** sarob has joined #openstack-meeting-alt20:14
jraim#info testr20:14
jraimDid we hear anything back from Monty on the needs of testr?20:14
electricheadiirc, they have some upcoming infra project that will use it20:15
electricheaddidn't get any details on what the upcoming project may be20:15
jraimreaperhulk: you said that nova and neutron use it now?20:15
reaperhulkThat's what he said but I haven't followed up to learn more details. Nova and neutron both use it yes20:15
jraimokay20:15
reaperhulkHeat does as well20:15
reaperhulk(There may be more)20:15
jraim#action follow up with infra to see what the deal with testr is20:15
jraimcool20:16
jraim#info oslo.messaging20:16
*** denis_makogon has joined #openstack-meeting-alt20:16
jraimI think we've mostly covered this now20:16
*** julim has quit IRC20:16
jraimanything else to note?20:16
woodsternot right now20:16
jraimcool20:16
reaperhulkkeep -> barbican rename? That's blocked on stackforge migration though so probably not a big deal20:16
jraimahh okay, we need to land the stackforge stuff before we make any more changes?20:17
jraimwas there a pending PR that we need to move over too?20:17
reaperhulkThe author of that PR agreed to resubmit once we land in stackforge20:17
jraimoh great20:17
reaperhulkWe had a few more changes we wanted him to make so we didn't want to land in GH20:17
jraimfair enough20:17
jraimcool, that's all the tasks I have listed in the wiki right now20:18
jraimAnyone have anything else they'd like to talk about?20:18
jraimSeems like its just Barbican people in here today :)20:18
jraimAlright, if there isn't anything else people have for the incubation request right now, we can call it20:19
jraimshort meeting - thanks all20:19
jraim#endmeeting20:19
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:19
openstackMeeting ended Thu Dec  5 20:19:20 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:19
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican_weekly_meeting/2013/barbican_weekly_meeting.2013-12-05-20.01.html20:19
*** sarob has quit IRC20:19
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican_weekly_meeting/2013/barbican_weekly_meeting.2013-12-05-20.01.txt20:19
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican_weekly_meeting/2013/barbican_weekly_meeting.2013-12-05-20.01.log.html20:19
*** hockeynut has quit IRC20:19
*** Guest57379 has quit IRC20:19
*** jvrbanac has left #openstack-meeting-alt20:20
*** yogesh_ has quit IRC20:22
*** yogesh_ has joined #openstack-meeting-alt20:23
*** dieseldoug has left #openstack-meeting-alt20:25
*** yogesh_ has quit IRC20:28
*** gokrokve has quit IRC20:32
*** gokrokve has joined #openstack-meeting-alt20:33
*** jmontemayor has quit IRC20:34
*** jasonb365 has quit IRC20:34
*** jcooley_ has quit IRC20:35
*** NehaV1 has quit IRC20:37
*** jcooley_ has joined #openstack-meeting-alt20:41
*** dprince has quit IRC20:41
*** NehaV has joined #openstack-meeting-alt20:43
*** jprovazn has quit IRC20:50
*** ywu has joined #openstack-meeting-alt20:50
*** banix has quit IRC20:51
*** haleyb has joined #openstack-meeting-alt20:55
*** aveiga has joined #openstack-meeting-alt20:56
*** julim has joined #openstack-meeting-alt20:56
*** shshang has joined #openstack-meeting-alt20:57
*** sbasam has joined #openstack-meeting-alt20:58
*** noslzzp has joined #openstack-meeting-alt20:59
*** jcooley_ has quit IRC20:59
shshangHello?21:01
*** hartsocks has joined #openstack-meeting-alt21:02
*** shshang has quit IRC21:02
*** shshang has joined #openstack-meeting-alt21:03
*** sc68cal has joined #openstack-meeting-alt21:03
sc68calsorry bout that21:03
sc68cal#startmeeting neutron_ipv621:03
openstackMeeting started Thu Dec  5 21:03:50 2013 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"21:03
openstackThe meeting name has been set to 'neutron_ipv6'21:03
*** banix has joined #openstack-meeting-alt21:04
*** Randy__ has joined #openstack-meeting-alt21:04
sc68calHello everyone, I hope all are doing well21:04
shshangHey, Sean21:04
* sc68cal pulls up agenda21:05
Randy__hi sean21:05
aveigahello21:05
sc68cal#topic review previous meeting items21:05
*** openstack changes topic to "review previous meeting items (Meeting topic: neutron_ipv6)"21:05
*** jvrbanac has joined #openstack-meeting-alt21:05
sc68calSo our meeting 2 weeks ago, the first thing we talked about was how to move forward with the DHCP agent for V621:06
*** hartsocks has left #openstack-meeting-alt21:06
sc68calwe discussed that in depth on the brainstorm on tuesday night, and the consensus was that we're going to attempt to get all the work that everyone has done around this combined21:06
sc68calRandy__ and shshang posted their review, which contains the work they did to make dhcpv6 work with dnsmasq21:07
sc68cal#link https://review.openstack.org/#/c/58186/ Review for IPv6 - Randy & shshang21:07
sc68calshshang: Do I have attribution right?21:08
shshangYup, that is correct, Sean!21:08
sc68calGreat21:08
sc68calso let's go ahead and use that to transition into a recap about what we talked about tuesday21:08
sc68cal#topic recap tuesday brainstorm21:08
*** openstack changes topic to "recap tuesday brainstorm (Meeting topic: neutron_ipv6)"21:08
sc68calshshang: want to summarize our discussion?21:09
shshangSure. So we had a brainstorming session on Tuesday21:09
shshangWe had teams from multiple placeholders, such as Comcast, IBM, HP, Cisco, and Nephos621:09
shshangSean clarified several question regarding the blueprint he proposed to the community21:10
shshangRegarding the blueprint, we focused on the short-term and mid-term goals21:10
sc68cal#link https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac Comcast short-term goal for IPv621:11
shshangIn summary, for short-term goals, with the new patch in Neutron to modify the firewall rules, the system should be able to achieve the short-term goal21:11
shshangIn other words, VM should be able to learn RA from upstream router, and come up with dual-stack address21:12
shshangW.r.t. the mid-term goal, a lot of work have been done already jointly between Comcast, IBM and HP team21:12
aveigasomething to note here is that patch applies to the hybrid VIF driver21:12
haleybi (hp) won't take credit for any work, just reviews :)21:13
jjmbso what is next here on this front "Comcast short-term goal for IPv6", how do we advance this so we can deploy preliminary support  IPv6?21:13
shshangThere are several bug fixes already submitted . In addition, Randy and I did POC before, and we believe that we can merge the work we did to add support of the architecture with Neutron Router and L3 agent21:13
shshang@aveiga, thanks for the note. Yup, that is correct21:14
sc68calthat sounds like a good time to transition to bugs21:14
*** banix has quit IRC21:14
sc68cal#topic bugs21:15
*** openstack changes topic to "bugs (Meeting topic: neutron_ipv6)"21:15
shshangWe will leverage the work Sean and IBM team already did, i.e. the framework to add dnsmasq mode from CLI to the code, and make sure dnsmasq has flexibility to achieve Sean's mid-term gold21:15
shshanggoal21:15
shshangIn addition, Sean encouraged us to create a new blueprint21:15
sc68cal#undo21:15
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x2b8ed10>21:16
shshangmake it as addition to the existing blueprint he submitted.21:16
shshangRandy created a blueprint for that purpose21:16
*** FallenPegasus has joined #openstack-meeting-alt21:16
sc68calperfect21:17
shshangWe will create at least one more blueprint as supplement to Sean's, in order to support router and l3 agent21:17
Randy__#link https://blueprints.launchpad.net/neutron/+spec/dnsmasq-bind-into-qrouter-namespace21:17
aveigathanks Randy__21:17
shshangThanks, @Randy21:17
Randy__np21:17
shshangSo eventually, as part of the Comcast mid-term goal, we should be able to allow user to define which mode dnsmasq will run at, and spin up dual-stack VM accordingly21:18
shshangWe didn't have time to discuss long-term goal yet.21:18
*** banix has joined #openstack-meeting-alt21:18
*** yogesh_ has joined #openstack-meeting-alt21:18
shshangAnything I missed, Sean or Randy?21:18
*** FallenPegasus has quit IRC21:18
aveigato be specific about the mid-term goal, there are 3 major ways to provision a network in ipv621:18
aveigaSLAAC, stateful, and stateless21:19
*** FallenPegasus has joined #openstack-meeting-alt21:19
aveigait would be useful to extend neutron's network attributes to include provisioning mode21:19
aveigaand basically set the v4 subnets to stateful21:19
sc68calaveiga: I believe the subnet_mode bp covers that21:19
aveigabut allow the v6 networks t oselect one of these modes21:19
sc68calsince it allows you to do static, ra-names, ra-stateless, etc21:19
aveigaexactly, mind linking it?21:19
Randy__that is our intent21:20
sc68cal#link https://blueprints.launchpad.net/neutron/+spec/dnsmasq-mode-keyword dnsmasq v6 mode configuration21:20
Randy__we will use the modes introduced with keywords blueprint21:20
Randy__that is a dependency21:20
shshangThe framework Sean and IBM team defines, including a list of constants for all of these modes21:20
sc68caljjmb: I think the last peice for our short term is just getting the hairpin fix into nova21:20
shshangwe will use the definition of those constants for our next code submission.21:21
sc68cal#link https://review.openstack.org/#/c/52983/ defines the modes available to use with dnsmasq21:21
shshangWe will also drop the source code, which are duplicated with Comcast and IBM teams' contribution.21:21
*** jmaron has quit IRC21:21
shshangI believe that should be the summary of our Tuesday night's meeting21:22
Randy__we will create another blueprint to address the external gateway of the L3 agent21:23
sc68calexcellent - thanks for organizing that meeting, I think it was very helpful for the IBM people who are not able to make these meetings21:23
sc68caldue to timezone differences21:23
shshangNp, Sean!21:23
sc68calRandy__: excellent21:23
sc68calaveiga: You discovered a bug in dnsmasq with dualstack - I think shshang and Randy__ ran into the same issue21:24
sc68cal#topic bugs21:24
*** openstack changes topic to "bugs (Meeting topic: neutron_ipv6)"21:24
sc68calwant to give you guys time to discuss21:24
aveigasure21:24
aveiga#link https://bugs.launchpad.net/neutron/+bug/1257446 neutron dual-stack bug21:25
aveigaI ran into an issue that seems like a show stopper.  If you create a regular IPv4 provider network, it operates as expected.  As soon as you add an IPv6 subnet to that network, dnsmasq stops issuing leases21:26
aveigait turns out that neutron is trying to send both networks to dnsmasq as tags21:26
sc68calshshang: this is happens in the part of the code where you place 1.1.1.1 in as a workaround, if I recall correctly, from Tuesday's meeting21:26
aveigathis is invalid syntax for dnsmasq, and causes it to stop issuing responses21:26
sc68calin your review21:26
aveigaso in order to get dual-stack working, it might be necessary to fix a fw flaws in the v4 workflow as well21:27
aveigafew*21:27
shshangyes, you are right....I remember Havana release packaged 2.5.x release, which had a lot of issues of IPv6.21:27
shshangI later on "upgraded" it to 2.6.5 release21:27
*** IlyaE has joined #openstack-meeting-alt21:28
aveigayes, in the bug I mention that the installed dnsmasq (per the repo) is 2.5921:28
*** reaperhulk has left #openstack-meeting-alt21:28
*** NehaV1 has joined #openstack-meeting-alt21:29
shshangDo you plan to fix it from OpenStack side?21:29
aveigathat's what I wanted to bring up21:29
aveigathere are multiple ways to fix it, but which is correct?21:29
sc68calaveiga: since we are working closely with the maintainer of dnsmasq- perhaps we can discuss with him/her?21:30
aveigawe could bump the minimum required version of dnsmasq, or the (imho) proper way would be to fix the command to not have both networks tagged21:30
aveigasc68cal: I'd rather work with what's already deployed21:30
aveigaI'm not sure issuing both networks is correct21:30
*** colinmcn_ has quit IRC21:30
*** colinmcnamara has quit IRC21:30
jjmbsean we (comcast) are happy to direct some of our resources to address issues that will advance openstack ipv6 support21:31
jjmbwe should remain open to upping the version of dnsmasq that is required21:31
jjmbsome fixes and features may be required21:31
aveigajjmb: The issue lies in that we are treating ipv4 and ipv6 on the same network as separate networks21:31
sc68caljjmb: agreed. I think like aveiga said this is neutron just constructing a bad cmd string21:31
shshang@aveiga, I agree with you...I am afraid of if dnsmasq doesn't support it, then there is no way we can make it happen....unless the author changes it21:31
shshangclearly it is supported in the newer release21:32
shshanganother bad thing on 2.5.x release is, it may not support --enable-ra21:32
aveigaperhaps this is something we should put to the mailing list21:32
*** NehaV has quit IRC21:32
aveigato see what kind of operator pain it would cause to bump the version21:32
shshangI remember at the time when I add --enable-ra, it complained. That was the main reason I switched to 2.6.x21:33
jjmbwe need to keep a running list of dnsmasq related bugs and rfe's so we can ensure they are addressed and accounted for...21:33
shshang@jjmb, yup21:33
*** FallenPegasus has quit IRC21:33
aveigajjmb: I think I'll go retag the bug dnsmasq in launchpad21:33
aveigawe should consider doing that for future issues21:33
sc68calAnyone else have any other bugs to discuss?21:34
*** dmitryme has quit IRC21:34
sc68calothewise we'll hit tempest, then do open discussion21:35
sc68cal#topic tempest21:35
*** openstack changes topic to "tempest (Meeting topic: neutron_ipv6)"21:35
shshangI see IBM team initiated several threads on tempest, right?21:36
sc68calshshang: exactly21:36
sc68cal#link https://review.openstack.org/#/c/58721/ static ipv6 injection scenario21:36
sc68calI don't know if anyone has anything related to tempest, but I felt it would be good to bring it up anyway21:37
shshangWhat they are doing is helpful for us too.21:37
*** yamahata_ has joined #openstack-meeting-alt21:37
aveigaactually, I'm interested in setting up a separate meeting (one-ff) to review neutron tempest cases21:37
aveigawe should look at them and write v6 cases for existing v4 ones21:38
*** jswarren has quit IRC21:38
shshangSooner than later, we need to leverage their tool to sanitize our code.21:38
sc68calhaleyb: does tempest run on infrastructure that hp provides? i forget21:38
aveigaeventually, security groups, fwaas, etc will need to be tested with v6 as well21:38
shshangforgive my ignorance, who has the ownership of testing and test case development?21:39
haleybsc68cal: probably, i'd have to ask someone, it's nothing i do21:39
*** garyduan has quit IRC21:40
aveigatangentially related, I'm going to start leveraging the Third Party Testing tools to run code against our lab here at Comcast too21:40
*** garyduan has joined #openstack-meeting-alt21:40
aveigaI can only cover certain scenarios, but every bit helps until Tempest is running against v6 code21:40
sc68calaveiga: I think that'd be great21:40
sc68cal#action aveiga sc68cal jjmb investigate third party test integration for doing ipv6 tempest testing21:41
shshangSo clearly there is a need...I am eager to see what we can do in order to make IBM team's tool available21:41
aveigaare they willing to assist? Forgive my ignorance, but I'm not familiar with the situation21:42
shshangIn the context of what we are trying to do here, I believe they are going to help21:42
*** twoputt_ has quit IRC21:43
*** twoputt__ has quit IRC21:43
*** twoputt_ has joined #openstack-meeting-alt21:43
*** twoputt__ has joined #openstack-meeting-alt21:43
aveigaone of the action items I had from the first meeting was to gather a list of the things we're looking for in code review that are "IPv4-only-isms"21:44
aveigajjmb was kind enough to start the ehterpad for it21:44
aveiga#link https://etherpad.openstack.org/p/ipv6-coding-considerations ipv4-isms21:44
aveigathe list isn't complete by any means, but is a starting point21:44
sc68cal#topic open discussion21:45
*** openstack changes topic to "open discussion (Meeting topic: neutron_ipv6)"21:45
shshangSorry, Sean, what's the decision of tempest?21:45
sc68calshshang: I think we just keep an eye on what the IBM people are adding to tempest21:45
aveigashshang: I agree with sc68cal, and we should go over it when it's published21:46
sc68caland maybe our team inside comcast can investigate running tempest so we can formailize some of our testing that we've been doing21:46
aveigafrom there we can look for gaps and try to patch them up21:46
aveigasc68cal: can you give me that as an action item?21:47
aveigaI'll put it in my backlog21:47
sc68calI think I got it already21:47
aveigano, the tempest integration part21:47
aveigawe're good on theird party21:47
shshangAgree, I feel like we should give their tool a try21:47
sc68calah gotcha21:47
aveigashshang: is there a link to this tool, or are they still in the process?21:48
shshangI am not 100% sure of the readiness, but based on my current reading, it adds some enhancement to the existing template21:49
aveigaok, would you mind providing a link (or encouraging them to) to the mailing list when it's available? I'm interested in doing an evaluation21:49
shshangThe same here. I will nudge them to provide more details. Hopefully it will become community level testing solution for IPv621:50
*** banix has quit IRC21:50
*** banix has joined #openstack-meeting-alt21:51
*** jmaron has joined #openstack-meeting-alt21:52
sc68calSounds good - we've got 8 mins left if anyone else has anything21:52
shshangNothing from my side...btw, Randy is going to create more blueprints and link to yours. We will share the link to the mailer when it is done.21:54
shshangA quick question, for mid-term, are we going to consider running dnsmasq as dhcp6 server?21:54
aveigashshang: I think that's a good idea21:55
*** amcrn_ has joined #openstack-meeting-alt21:55
*** amcrn has quit IRC21:55
aveigait's already being used today in openwrt and similar projects, and it even handles prefix delegation, which I think needs to be on the long-term list21:55
*** ijw has joined #openstack-meeting-alt21:56
aveigai.e. we should be able to pull a delegated prefix for use in software load-balancers or service VMs21:56
*** atiwari has quit IRC21:56
shshangIf I understand you correctly, the same dnsmasq will announce RA, and act as DHCPv6 server at the same time, in case of stateless DHCPv6 mode, right?21:56
sc68calaveiga: doesn't the current code attempt to do dhcp6 today?21:56
aveigaso that's the question, there's a discussion to be had there21:57
sc68calobviously it breaks, but it tries to do that with the flags its passed21:57
aveigasome modes you want RAs issued there21:57
*** amcrn_ is now known as amcrn21:57
aveigabut in some modes you don't21:57
aveigafor instance, my deployment with l3 provider networks, you want the RA coming from the upstream gateway21:57
ijwaveiga: um, surely you want RAs from the router, not the DHCP server (says he jumping in late)21:57
aveigaer, l2 provider21:57
aveigaijw: you want it from dhcp server IF it's the l3 gateway21:58
aveigaotherwise you don't21:58
ijwOK, told you I'd jumped in late ;)21:58
aveiganp21:58
shshangI see. That is a very good use case, aveiga21:58
*** SergeyLukjanov has quit IRC21:58
aveigathere are several bugs in many implementations wehre multiple RAs fail to work proerly21:58
*** jmaron has quit IRC21:58
aveigaor where RA priorities are not respected21:58
aveigawe have to work around them, unfortunately, as they are widespread21:59
*** SergeyLukjanov has joined #openstack-meeting-alt21:59
shshangaveiga, if you don't mind, can Randy and I take a look at this issue?21:59
aveigasure!21:59
aveigalet's take it to the mailing list, since we're out of time21:59
shshangi.e. run dnsmasq as DHCPv6 for various mode.21:59
shshangabsolutely21:59
aveigathanks22:00
shshangDon't mention it! Any time!22:00
shshangWill keep everybody posted22:00
sc68calOK everyone - let's keep things going on the ML22:01
shshangThanks, everyone22:01
sc68callots of great stuff going on, very excited to see things coming together22:01
sc68caleveryone have a great weekend!22:01
jjmbsame, thanks sean22:01
sc68cal#endmeeting22:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:02
openstackMeeting ended Thu Dec  5 22:02:04 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
* ijw will put the meeting in his calendar for the right time next week.22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-12-05-21.03.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-12-05-21.03.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-12-05-21.03.log.html22:02
*** Randy__ has quit IRC22:02
*** aveiga has left #openstack-meeting-alt22:03
*** banix has quit IRC22:03
*** shshang has quit IRC22:03
*** pdmars has quit IRC22:05
*** abramley has quit IRC22:07
*** sbasam has left #openstack-meeting-alt22:09
*** DennyZhang has joined #openstack-meeting-alt22:10
*** denis_makogon has quit IRC22:10
*** denis_makogon has joined #openstack-meeting-alt22:10
*** jcooley_ has joined #openstack-meeting-alt22:12
*** jdob has quit IRC22:14
*** ruhe has quit IRC22:17
*** jcoufal has quit IRC22:17
*** lblanchard has quit IRC22:18
*** eankutse has quit IRC22:20
*** DennyZhang has quit IRC22:27
*** kgriffs is now known as kgriffs_afk22:28
*** sarob has joined #openstack-meeting-alt22:31
*** twoputt_ has quit IRC22:32
*** twoputt__ has quit IRC22:32
*** twoputt_ has joined #openstack-meeting-alt22:32
*** twoputt__ has joined #openstack-meeting-alt22:32
*** banix has joined #openstack-meeting-alt22:37
*** kgriffs_afk is now known as kgriffs22:37
*** SergeyLukjanov has quit IRC22:37
*** kgriffs is now known as kgriffs_afk22:38
*** SergeyLukjanov has joined #openstack-meeting-alt22:38
*** rnirmal has quit IRC22:38
*** noslzzp has quit IRC22:41
*** SergeyLukjanov has quit IRC22:42
*** kgriffs_afk is now known as kgriffs22:43
*** yamahata_ has quit IRC22:45
*** sacharya has quit IRC22:49
*** jmaron has joined #openstack-meeting-alt22:50
*** sarob has quit IRC22:57
*** sarob has joined #openstack-meeting-alt22:58
*** demorris has quit IRC22:59
*** sarob_ has joined #openstack-meeting-alt23:01
*** sarob has quit IRC23:01
*** NehaV1 has quit IRC23:02
*** jasonb365 has joined #openstack-meeting-alt23:03
*** nati_uen_ has joined #openstack-meeting-alt23:04
*** brents has quit IRC23:06
*** nati_ueno has quit IRC23:07
*** brents has joined #openstack-meeting-alt23:08
*** IlyaE has quit IRC23:09
*** yogesh_ has quit IRC23:09
*** SergeyLukjanov has joined #openstack-meeting-alt23:11
*** jmaron has quit IRC23:13
*** jcooley_ has quit IRC23:14
*** jcoufal-mob has joined #openstack-meeting-alt23:16
*** SergeyLukjanov has quit IRC23:18
*** jmaron has joined #openstack-meeting-alt23:19
*** jecarey has quit IRC23:22
*** jcooley_ has joined #openstack-meeting-alt23:23
*** jcoufal-mob has quit IRC23:24
*** sarob_ has quit IRC23:31
*** sarob has joined #openstack-meeting-alt23:31
*** jasonb365 has quit IRC23:31
*** nati_uen_ has quit IRC23:34
*** nati_ueno has joined #openstack-meeting-alt23:34
*** sarob_ has joined #openstack-meeting-alt23:34
*** sarob_ has quit IRC23:34
*** sarob_ has joined #openstack-meeting-alt23:35
*** sarob has quit IRC23:35
*** lblanchard has joined #openstack-meeting-alt23:36
*** denis_makogon has quit IRC23:38
*** dev_warlord has quit IRC23:39
*** jcooley_ has quit IRC23:42
*** brents has quit IRC23:42
*** kgriffs is now known as kgriffs_afk23:42
*** jcooley_ has joined #openstack-meeting-alt23:43
*** aignatov has quit IRC23:48
*** jmaron has quit IRC23:53
*** brents has joined #openstack-meeting-alt23:53
*** jcooley_ has quit IRC23:55
*** sacharya has joined #openstack-meeting-alt23:55

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