Thursday, 2013-11-21

*** nati_ueno has quit IRC00:01
*** yamahata_ has joined #openstack-meeting-alt00:02
*** grapex has quit IRC00:08
*** derekh has quit IRC00:09
*** amotoki is now known as __amotoki__00:14
*** rongze has joined #openstack-meeting-alt00:16
*** rongze has quit IRC00:20
*** yamahata_ has quit IRC00:22
*** yamahata_ has joined #openstack-meeting-alt00:22
*** dosaboy has quit IRC00:23
*** MarkAtwood has quit IRC00:24
*** boris-42 has joined #openstack-meeting-alt00:32
*** alazarev has joined #openstack-meeting-alt00:36
*** julim has joined #openstack-meeting-alt00:37
*** zane has joined #openstack-meeting-alt00:37
*** julim has quit IRC00:46
*** cody-somerville has quit IRC00:48
*** devlaps has quit IRC00:56
*** nati_ueno has joined #openstack-meeting-alt00:56
*** nati_ueno has quit IRC00:57
*** nati_ueno has joined #openstack-meeting-alt01:00
*** nati_ueno has quit IRC01:00
*** cody-somerville has joined #openstack-meeting-alt01:02
*** nati_ueno has joined #openstack-meeting-alt01:05
*** gduan has joined #openstack-meeting-alt01:05
*** nati_ueno has quit IRC01:06
*** nati_ueno has joined #openstack-meeting-alt01:06
*** garyduan has quit IRC01:07
*** alazarev has quit IRC01:07
*** amytron has quit IRC01:11
*** yogesh has joined #openstack-meeting-alt01:12
*** boris-42 has quit IRC01:20
*** alazarev has joined #openstack-meeting-alt01:23
*** DennyZhang has joined #openstack-meeting-alt01:24
*** nosnos has joined #openstack-meeting-alt01:30
*** amcrn has quit IRC01:31
*** yogesh has quit IRC01:36
*** yogesh has joined #openstack-meeting-alt01:37
*** sarob has joined #openstack-meeting-alt01:37
*** gokrokve has joined #openstack-meeting-alt01:38
*** yogesh has quit IRC01:41
*** gokrokve has quit IRC01:43
*** rongze has joined #openstack-meeting-alt01:47
*** _ozstacker_ has joined #openstack-meeting-alt01:49
*** ozstacker has quit IRC01:50
*** rongze has quit IRC01:51
*** alazarev has quit IRC01:56
*** sarob has quit IRC01:58
*** eankutse has joined #openstack-meeting-alt01:58
*** alazarev has joined #openstack-meeting-alt01:59
*** alazarev has quit IRC02:00
*** nati_uen_ has joined #openstack-meeting-alt02:00
*** zane has quit IRC02:03
*** nati_ueno has quit IRC02:04
*** DennyZhang has quit IRC02:05
*** tanisdl has quit IRC02:06
*** nati_uen_ has quit IRC02:15
*** nati_ueno has joined #openstack-meeting-alt02:16
*** sarob has joined #openstack-meeting-alt02:18
*** demorris has joined #openstack-meeting-alt02:20
*** rongze has joined #openstack-meeting-alt02:22
*** boris-42 has joined #openstack-meeting-alt02:24
*** Barker has joined #openstack-meeting-alt02:32
*** bdpayne has quit IRC02:37
*** flwang has quit IRC02:41
*** yamahata_ has quit IRC02:42
*** eankutse has quit IRC02:43
*** alazarev has joined #openstack-meeting-alt02:48
*** alazarev has quit IRC02:48
*** ashaikh has quit IRC02:53
*** sarob has quit IRC02:55
*** sarob has joined #openstack-meeting-alt02:56
*** nicole has joined #openstack-meeting-alt02:57
*** nicole is now known as Guest1068602:57
*** demorris has quit IRC02:59
*** sarob has quit IRC03:00
*** zane has joined #openstack-meeting-alt03:03
*** nati_uen_ has joined #openstack-meeting-alt03:10
*** nati_ueno has quit IRC03:14
*** twoputt has quit IRC03:16
*** twoputt_ has quit IRC03:17
*** DennyZhang has joined #openstack-meeting-alt03:25
*** kraman has joined #openstack-meeting-alt03:33
*** kraman1 has joined #openstack-meeting-alt03:35
*** Barker has quit IRC03:38
*** kraman has quit IRC03:38
*** Barker has joined #openstack-meeting-alt03:38
*** nati_uen_ has quit IRC03:39
*** coolsvap has joined #openstack-meeting-alt03:40
*** nati_ueno has joined #openstack-meeting-alt03:40
*** gokrokve has joined #openstack-meeting-alt03:50
*** Barker has quit IRC03:54
*** flwang has joined #openstack-meeting-alt03:54
*** boris-42 has quit IRC03:57
*** nati_uen_ has joined #openstack-meeting-alt03:57
*** boris-42 has joined #openstack-meeting-alt03:57
*** gokrokve has quit IRC03:58
*** nati_uen_ has quit IRC03:58
*** gokrokve has joined #openstack-meeting-alt03:59
*** nati_ueno has quit IRC04:01
*** coolsvap has quit IRC04:19
*** coolsvap has joined #openstack-meeting-alt04:21
*** coolsvap has quit IRC04:27
*** coolsvap_ has joined #openstack-meeting-alt04:27
*** coolsvap_ has left #openstack-meeting-alt04:28
*** coolsvap has joined #openstack-meeting-alt04:39
*** coolsvap has quit IRC04:44
*** coolsvap has joined #openstack-meeting-alt04:45
*** coolsvap has quit IRC04:50
*** coolsvap has joined #openstack-meeting-alt04:53
*** nati_ueno has joined #openstack-meeting-alt04:57
*** akuznetsov has joined #openstack-meeting-alt04:58
*** DennyZhang has quit IRC04:59
*** gokrokve has joined #openstack-meeting-alt05:01
*** radix_ has quit IRC05:05
*** gokrokve has quit IRC05:06
*** Guest10686 has quit IRC05:11
*** bdpayne has joined #openstack-meeting-alt05:12
*** ashaikh has joined #openstack-meeting-alt05:15
*** IlyaE has joined #openstack-meeting-alt05:20
*** yogesh has joined #openstack-meeting-alt05:23
*** yogesh has quit IRC05:28
*** bdpayne has quit IRC05:31
*** sarob has joined #openstack-meeting-alt05:39
*** yogesh has joined #openstack-meeting-alt05:42
*** sarob has quit IRC05:43
*** SergeyLukjanov has joined #openstack-meeting-alt05:48
*** yogesh has quit IRC05:49
*** yogesh has joined #openstack-meeting-alt05:50
*** yogesh has quit IRC05:51
*** IlyaE has quit IRC05:58
*** gokrokve has joined #openstack-meeting-alt06:02
*** yogesh has joined #openstack-meeting-alt06:04
*** gokrokve has quit IRC06:07
*** akuznetsov has quit IRC06:08
*** alazarev has joined #openstack-meeting-alt06:08
*** akuznetsov has joined #openstack-meeting-alt06:11
*** IlyaE has joined #openstack-meeting-alt06:11
*** alazarev has quit IRC06:19
*** IlyaE has quit IRC06:29
*** yogesh has quit IRC06:31
*** yogesh has joined #openstack-meeting-alt06:31
*** yogesh has quit IRC06:32
*** yogesh has joined #openstack-meeting-alt06:32
*** IlyaE has joined #openstack-meeting-alt06:47
*** nosnos has quit IRC06:48
*** nosnos has joined #openstack-meeting-alt06:48
*** IlyaE has quit IRC06:56
*** kraman1 has quit IRC06:57
*** zane has quit IRC06:59
*** NikitaKonovalov has joined #openstack-meeting-alt06:59
*** SergeyLukjanov has quit IRC06:59
*** NikitaKonovalov has quit IRC07:00
*** gokrokve has joined #openstack-meeting-alt07:00
*** gokrokve has quit IRC07:05
*** yogesh has quit IRC07:06
*** yogesh has joined #openstack-meeting-alt07:07
*** yogesh has quit IRC07:07
*** yogesh has joined #openstack-meeting-alt07:08
*** alazarev has joined #openstack-meeting-alt07:11
*** jcoufal has joined #openstack-meeting-alt07:14
*** akuznetsov has quit IRC07:15
*** radix_ has joined #openstack-meeting-alt07:17
*** nimi has left #openstack-meeting-alt07:26
*** denis_makogon_ has joined #openstack-meeting-alt07:28
*** akuznetsov has joined #openstack-meeting-alt07:32
*** alazarev has quit IRC07:33
*** akuznetsov has quit IRC07:34
*** nati_ueno has quit IRC07:40
*** nati_ueno has joined #openstack-meeting-alt07:43
*** sacharya has quit IRC07:44
*** sacharya has joined #openstack-meeting-alt07:44
*** sacharya has quit IRC07:44
*** kraman has joined #openstack-meeting-alt07:44
*** sacharya has joined #openstack-meeting-alt07:45
*** ashaikh has quit IRC07:45
*** gokrokve has joined #openstack-meeting-alt08:00
*** gokrokve_ has joined #openstack-meeting-alt08:02
*** gokrokve has quit IRC08:05
*** akuznetsov has joined #openstack-meeting-alt08:05
*** jtomasek has joined #openstack-meeting-alt08:05
*** gokrokve_ has quit IRC08:07
*** kraman has quit IRC08:18
*** SergeyLukjanov has joined #openstack-meeting-alt08:21
*** flaper87|afk is now known as flaper8708:21
*** nosnos_ has joined #openstack-meeting-alt08:30
*** sacharya has quit IRC08:32
*** nosnos has quit IRC08:33
*** boris-42 has quit IRC08:41
*** kraman has joined #openstack-meeting-alt08:45
*** jtomasek has quit IRC08:45
*** ruhe has joined #openstack-meeting-alt08:47
*** jtomasek has joined #openstack-meeting-alt08:47
*** kraman has quit IRC08:49
*** rossella_s has joined #openstack-meeting-alt08:55
*** rsblendido has joined #openstack-meeting-alt08:55
*** derekh has joined #openstack-meeting-alt08:58
*** gokrokve has joined #openstack-meeting-alt09:00
*** flwang has quit IRC09:01
*** gokrokve has quit IRC09:05
*** plomakin has joined #openstack-meeting-alt09:06
*** yamahata_ has joined #openstack-meeting-alt09:14
*** dosaboy has joined #openstack-meeting-alt09:17
*** dosaboy has quit IRC09:19
*** dosaboy has joined #openstack-meeting-alt09:19
*** IlyaE has joined #openstack-meeting-alt09:21
*** ruhe has quit IRC09:22
*** coolsvap is now known as coolsvap[A]09:36
*** coolsvap[A] is now known as coolsvap09:39
*** yamahata_ has quit IRC09:40
*** dosaboy has quit IRC09:43
*** dosaboy has joined #openstack-meeting-alt09:43
*** kraman has joined #openstack-meeting-alt09:45
*** gokrokve has joined #openstack-meeting-alt09:45
*** boris-42 has joined #openstack-meeting-alt09:48
*** gokrokve has quit IRC09:50
*** jtomasek has quit IRC09:51
*** boris-42 has quit IRC09:52
*** yogesh has quit IRC09:53
*** yogesh has joined #openstack-meeting-alt09:53
*** plomakin has quit IRC09:55
*** nati_ueno has quit IRC09:55
*** plomakin has joined #openstack-meeting-alt09:55
*** jtomasek has joined #openstack-meeting-alt09:55
*** yogesh has quit IRC09:58
*** aignatov has joined #openstack-meeting-alt09:58
*** ruhe has joined #openstack-meeting-alt09:58
*** akuznetsov has quit IRC09:59
*** SergeyLukjanov is now known as _SergeyLukjanov09:59
*** gokrokve has joined #openstack-meeting-alt10:00
*** gokrokve has quit IRC10:05
*** jcoufal has quit IRC10:09
*** coolsvap is now known as coolsvap[A]10:09
*** kraman has quit IRC10:18
*** yamahata_ has joined #openstack-meeting-alt10:21
*** ruhe has quit IRC10:31
*** yamahata_ has quit IRC10:33
*** nati_ueno has joined #openstack-meeting-alt10:37
*** akuznetsov has joined #openstack-meeting-alt10:38
*** coolsvap[A] is now known as coolsvap10:38
*** IlyaE has quit IRC10:39
*** ruhe has joined #openstack-meeting-alt10:41
*** IlyaE has joined #openstack-meeting-alt10:44
*** IlyaE has quit IRC10:45
*** kraman has joined #openstack-meeting-alt10:45
*** IlyaE has joined #openstack-meeting-alt10:47
*** aignatov has quit IRC10:47
*** IlyaE has quit IRC10:48
*** aignatov has joined #openstack-meeting-alt10:48
*** kraman has quit IRC10:50
*** rongze has quit IRC10:53
*** NikitaKonovalov has joined #openstack-meeting-alt10:53
*** rongze has joined #openstack-meeting-alt10:53
*** rongze has quit IRC10:59
*** SergeyLukjanov has joined #openstack-meeting-alt10:59
*** gokrokve has joined #openstack-meeting-alt11:00
*** gokrokve has quit IRC11:05
*** coolsvap has quit IRC11:08
*** sergmelikyan has joined #openstack-meeting-alt11:11
*** coolsvap has joined #openstack-meeting-alt11:13
*** nosnos_ has quit IRC11:20
*** nosnos has joined #openstack-meeting-alt11:21
*** nosnos has quit IRC11:25
*** coolsvap has quit IRC11:37
*** boris-42 has joined #openstack-meeting-alt11:45
*** kraman has joined #openstack-meeting-alt11:45
*** yamahata_ has joined #openstack-meeting-alt11:50
*** gokrokve has joined #openstack-meeting-alt12:00
*** NikitaKonovalov has quit IRC12:05
*** gokrokve has quit IRC12:05
*** NikitaKonovalov has joined #openstack-meeting-alt12:11
*** ruhe has quit IRC12:15
*** nati_ueno has quit IRC12:18
*** kraman has quit IRC12:18
*** ruhe has joined #openstack-meeting-alt12:26
*** coolsvap has joined #openstack-meeting-alt12:30
*** NikitaKonovalov has quit IRC12:32
*** vkmc has joined #openstack-meeting-alt12:37
*** jprovazn has joined #openstack-meeting-alt12:42
*** NikitaKonovalov has joined #openstack-meeting-alt12:44
*** kraman has joined #openstack-meeting-alt12:45
*** pcm_ has joined #openstack-meeting-alt12:47
*** kraman has quit IRC12:49
*** flwang has joined #openstack-meeting-alt12:51
*** rongze has joined #openstack-meeting-alt12:52
*** rongze_ has joined #openstack-meeting-alt12:54
*** pdmars has joined #openstack-meeting-alt12:55
*** rongze has quit IRC12:58
*** pdmars has quit IRC12:59
*** coolsvap is now known as coolsvap_away12:59
*** gokrokve has joined #openstack-meeting-alt13:00
*** rongze_ has quit IRC13:02
*** pdmars has joined #openstack-meeting-alt13:02
*** rongze has joined #openstack-meeting-alt13:04
*** gokrokve has quit IRC13:05
*** demorris has joined #openstack-meeting-alt13:07
*** kevinconway has joined #openstack-meeting-alt13:08
*** ruhe has quit IRC13:12
*** ruhe has joined #openstack-meeting-alt13:17
*** demorris has quit IRC13:25
*** marios has quit IRC13:41
*** kraman has joined #openstack-meeting-alt13:45
*** jergerber has joined #openstack-meeting-alt13:45
*** demorris has joined #openstack-meeting-alt13:46
*** noslzzp has joined #openstack-meeting-alt13:46
*** lblanchard has joined #openstack-meeting-alt13:50
*** jergerber has quit IRC13:52
*** dprince has joined #openstack-meeting-alt13:53
*** ilyashakhat has quit IRC13:55
*** jergerber has joined #openstack-meeting-alt13:55
*** yamahata_ has quit IRC13:57
*** yamahata_ has joined #openstack-meeting-alt13:58
*** zhiyan has joined #openstack-meeting-alt14:00
*** gokrokve has joined #openstack-meeting-alt14:00
markwashgood morning glance folks14:00
rosmaitao/14:00
rosmaitamarkwash: link to agenda etherpad?14:01
zhiyangood morning/evening!14:01
zhiyanhttps://etherpad.openstack.org/p/glance-team-meeting-agenda14:01
markwashdo we have any other folks here as well?14:01
*** demorris has quit IRC14:01
markwashiccha: nikhil__ flwang flaper87 ameade14:02
flaper87o/14:02
flaper87gooood morning14:02
markwashI suppose we should get started14:02
rosmaitazhiyan: thanks and good evening14:02
markwash#startmeeting glance14:02
openstackMeeting started Thu Nov 21 14:02:56 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
*** openstack changes topic to " (Meeting topic: glance)"14:02
openstackThe meeting name has been set to 'glance'14:03
markwash#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:03
zhiyanrosmaita: :)14:03
markwashFirst a couple of announcements14:03
markwash#topic icehouse-114:03
*** openstack changes topic to "icehouse-1 (Meeting topic: glance)"14:04
markwashicehouse-1 is rapidly approaching14:04
markwashI think its due to be cut on December 5th14:04
markwashmaybe a day earlier14:04
flaper87markwash: correct14:04
flaper87Dec 5th14:04
flaper87AFAIK14:04
zhiyan~2 weeks later14:04
flaper87#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule14:04
*** gokrokve has quit IRC14:04
markwash#link https://launchpad.net/glance/+milestone/icehouse-114:04
* flaper87 just targeted https://blueprints.launchpad.net/glance/+spec/oslo-messaging for i-1 since the patch is already there14:05
flaper87feel free to push it back14:05
*** aignatov has quit IRC14:05
markwashsince I was triaging so close to the deadline, i mostly pushed stuff to icehouse-214:05
markwashbut that's just a projection, anything that we think we can land can go ahead14:05
markwashflaper87: great! thanks14:05
markwashif folks have other bps they want to land soon, go ahead and target them to i-1 so we can focus review efforts possibly14:06
zhiyanmarkwash: before that ,can i ask you help check/approval bp first?14:06
markwashyes14:06
markwashwanna link them here now so I have a little todo list we can check back on?14:06
*** yamahata_ has quit IRC14:07
*** yamahata_ has joined #openstack-meeting-alt14:08
rosmaitamarkwash: there are 2 more bugs along the lines of #1251518 that should be targeted for i-114:08
markwashhmm, can I trouble you for the full links? when I click on the #<number> I get a lonely empty freenode room :-)14:09
* rosmaita is looking for them14:09
rosmaitahttps://bugs.launchpad.net/bugs/125151814:10
rosmaitahttps://bugs.launchpad.net/glance/+bug/125245914:10
rosmaitahttps://bugs.launchpad.net/glance/+bug/125233714:10
*** coolsvap_away is now known as coolsvap14:10
markwashgreat14:11
markwashthose look important!14:11
markwashI'm inclined to make them I-1 critical14:11
rosmaitai do what i can14:11
flaper87rosmaita: +114:12
rosmaitai think Alex is already working on them, too14:12
markwashjust to hold our own feet to the fire14:12
flaper87I saw them yday, they are important14:12
flaper87markwash: +1 for critical14:12
markwashzhiyan: if you can, please link the bps you are thinking about in here before meeting end, or just email them to me14:12
markwashotherwise, are there any other i-1 pressing concerns?14:12
flaper87I saw ameade is already assigned, I guess he's working on them14:13
flaper87we should encourage him to ping core devs directly for review on those bugs14:13
*** eankutse has joined #openstack-meeting-alt14:13
rosmaitaflaper87: +114:13
flaper87otherwise we'll get to the i-1 cut w/o even having looked at them14:13
flaper87:D14:13
markwashyeah, especially since the review queue is still a bit long14:13
flaper87yeah14:13
*** eankutse has quit IRC14:14
markwash(segue!)14:14
*** eankutse has joined #openstack-meeting-alt14:14
markwashwell, almost14:14
markwashnext topic!14:14
markwash#topic glanceclient version 1.0.014:14
*** openstack changes topic to "glanceclient version 1.0.0 (Meeting topic: glance)"14:14
markwashI created a new development series in python-glanceclient on launchpad called v114:15
markwashits my intention that bugfixes/bps that are technically breaking changes could be targeted to that14:15
flaper87markwash: can you quickly summarize what are the breaking changes introduced in the new release ?14:15
flaper87I think I lost track of some of those14:15
markwashyeah, there are a few I know of14:16
markwashbut I want to make sure other folks can suggest and evaluate them14:16
markwash1) drop legacy cli14:16
*** NikitaKonovalov has quit IRC14:16
markwash2) change default page size14:16
markwash3) maybe something with better version handling for endpoints14:16
markwash4) I'd actually like to switch to requests which means at least temporarily losing control over ssl compression14:17
markwash5) in the CLI, don't create an image if no arguments are passed to image-create14:17
markwashI've also been trying to figure out how we will stage and manage all these changes14:17
flaper871) +1 2) Shouldn't we enforce this server side? 3) +1 4) +1 5) BIG +114:18
*** kraman has quit IRC14:18
flaper87re 4) I did some work there14:18
flaper87I ended up abandoning the patch because of the ssl thing14:18
flaper87Actually14:18
markwashflaper87: yeah, I think for #2 we really need  the default on the client to be to send nothing, so the server can pick14:18
markwashyeah, I was just looking at that patch14:18
flaper87I didn't abandoned it because of that. I workarounded the whole ssl thing14:18
markwashbcwaldon was working on rebasing it a while back as well14:19
flaper87and kept the compression code Stuard worked on14:19
flaper87but it got lost somewhere14:19
flaper87cool14:19
flaper87I'm +1 for using requests14:19
markwashI've been working on finding a place for staging all these changes14:19
markwashand sent an email to the list14:19
markwash#link http://lists.openstack.org/pipermail/openstack-dev/2013-November/019911.html14:20
*** NikitaKonovalov has joined #openstack-meeting-alt14:20
*** ashwini has joined #openstack-meeting-alt14:20
*** flwang has quit IRC14:20
markwashso that about sums that part up, any other thoughts on the glanceclient?14:20
markwashcool14:21
flaper87we should consider to take some of the code that currently exists in nova and pull it in14:21
flaper87remember that patch that got blocked ?14:21
markwashyes14:21
flaper87maybe find a better way to do that14:21
markwashI strongly agree14:21
markwashespecially as location stuff gets a little more complicated and better presented14:22
flaper87+114:22
zhiyanmarkwash: +114:22
markwashI think the client would be a great place for us to standardize things like how to select 1 out of the available image locations14:22
*** coolsvap has left #openstack-meeting-alt14:22
*** julim has joined #openstack-meeting-alt14:22
markwashnext up, looking at the review queue14:22
zhiyanmarkwash: so for this do you thinks we can reuse gho's patch? and rething about interface14:22
zhiyan?14:22
*** julim has quit IRC14:23
markwashI'm not sure14:23
* flaper87 neither14:23
flaper87I think that patch needs a major rework14:23
flaper87although I +2'ed back then14:23
flaper87:D14:23
markwashafter being reminded how much work it is to deprecate and drop API stuff in the clients14:23
markwashI'm glad we didn't land that one14:23
*** coolsvap has joined #openstack-meeting-alt14:23
markwashat least without more evaluation14:24
* markwash was at least nervous14:24
zhiyantbh, i'm not very clear the goal14:24
markwashthe goal of?14:24
zhiyanglance client lib14:24
*** rongze_ has joined #openstack-meeting-alt14:24
zhiyani mean the details of the landing path14:25
markwashI think we could benefit from actually trying to write down the goal14:25
markwashI think there is good stuff there, but its not always clear what we're trying to accomplish, I agree14:25
*** aignatov has joined #openstack-meeting-alt14:25
markwashin particular, with the way the api libs are laid out14:25
markwashbut I think that might be enough for now14:26
markwash#topic review backlog14:27
*** openstack changes topic to "review backlog (Meeting topic: glance)"14:27
markwashwe are down to 61 open reviews14:27
markwashthat's actually a pretty big improvement over last week14:27
markwashI think our average response time has also dropped by nearly a week14:27
*** rongze has quit IRC14:27
markwashor at least 4 days, something like that14:28
markwashgreat work everybody!14:28
flaper87w000t14:28
*** demorris has joined #openstack-meeting-alt14:28
zhiyanmarkwash: if gate work well, the number will better :)14:28
markwashzhiyan: that is true14:28
flaper87o/ I think there are some important, historical, patches that need some attention, though.14:28
flaper87for example: https://review.openstack.org/#/c/34801/14:28
flaper87that was opened on June 27th14:29
markwash"Remove user and key from location in Swift"14:29
markwashyeah that review is definitely on my mind14:29
markwashthere has been some recent discussion which I guess has been unfortunately kind of hidden14:29
markwashwhich has kept me from pursuing that14:29
flaper87oh14:30
*** rongze has joined #openstack-meeting-alt14:30
markwashrosmaita: would you say the conversations we've been having with smclaren about solving the credentials problem are relevant to that patch?14:30
markwashand might change the direction we want to go?14:30
*** yamahata_ has quit IRC14:30
rosmaitayes, i would hold off on that patch14:31
rosmaitai can post Stuart's doc link if others are interested14:31
flaper87rosmaita: yup, please.14:31
*** yamahata_ has joined #openstack-meeting-alt14:31
markwashI might -1 it with a note just to pull it out of the stats14:31
rosmaitadon't mean to work hidden, but don't want to broadcast our prob14:31
markwashright14:32
* rosmaita looking for link14:32
*** zhiyan1 has joined #openstack-meeting-alt14:32
*** csaba has joined #openstack-meeting-alt14:32
icchahey hey sorry forgot it hifted to 9 am14:32
rosmaitahttps://region-a.geo-1.objects.hpcloudsvc.com:443/v1/61624292678963/public_referenced/logical-swift-store.pdf14:32
markwashI did come up with one bookmark link I wanted to share with other reviewers since its helped me out a lot this week14:32
markwashhttps://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:33
*** venkatesh has joined #openstack-meeting-alt14:33
markwash^^ will show you all the reviews that really just need one more +2 and an approval14:33
*** zhiyan has quit IRC14:33
zhiyan1markwash: yes, it's true, also for me.14:33
*** rongze_ has quit IRC14:33
markwashits sometimes an area with "easy" reviews, but I think its also useful because it reduces the time a patch can sit around and catch rebase conflicts, assuming you're happy with it14:34
flaper87markwash: rosmaita so, is that something 'swift' store specific?14:34
rosmaitaflaper87: yes and no14:34
markwashflaper87: not entirely swift-specific. . there are other stores that have credentials14:34
flaper87yeah, sorry, I meant to ask. Is that fix something we can replicate on other stores?14:34
rosmaitai think the problem is more general, but we (hp, rackspace) use swift and are most concerned about it14:35
markwashbut its conceivable that solutions might be store-specific14:35
rosmaitatoo early to say14:35
flaper87would it be better to have that on a wiki page ?14:36
flaper87StoreCredentialsManagement14:36
flaper87or something like that14:36
ameadehere now >.<14:36
markwashI think a general fix for this problem would probably be a great thing to get done ASAP, as a prerequisite to some of the client work with locations we were talking about14:36
markwashso anyway, in summary, great work on reviews this past week and lets keep it up! once the queue is small we can relax a bit14:37
icchaflaper87: the s3 store14:37
icchaflaper87: i was looking for other stores with sridevi and thats the other one we noticed14:38
markwash#topic meta14:38
*** openstack changes topic to "meta (Meeting topic: glance)"14:38
flaper87iccha: cool, thanks for the heads up14:38
markwashso I was hoping we'd have some time here to brainstorm about ways to fix our sort of disasterous blueprint organization14:38
markwashmaybe its not so bad, but I personally can't make heads or tails of our blueprints from the general list14:38
*** bill_az has joined #openstack-meeting-alt14:39
markwashbut that discussion is probably long, and there are two other topics that have been added to the agenda14:39
markwashanybody prefer to talk about blueprint organization now? or maybe some other time?14:39
flaper87I think maybe other time14:40
flaper87since the next 2 topics are still related to blueprints14:40
icchai woud like time to go through the list14:40
flaper87and upcoming designs14:40
flaper87and what iccha said14:40
flaper87:D14:40
*** vponomaryov has joined #openstack-meeting-alt14:40
markwashokay cool14:40
icchasorry about not being better prepared14:40
*** julim has joined #openstack-meeting-alt14:40
markwashI should probably also jsut take a look at what some other projects are doing with theirs14:41
markwashnow, in hopefully fastest-first order14:41
markwash#topic Doc update14:41
*** openstack changes topic to "Doc update (Meeting topic: glance)"14:41
markwashrosmaita?14:42
rosmaitayo14:42
icchamost imp topic :) we really need it!14:42
markwashrosmaita: sorry, just trying to give you the floor14:42
rosmaitasorry, ok14:42
*** AlanClark has joined #openstack-meeting-alt14:42
rosmaitaso the patch i've got up handles defining the 2.1 version of openstack-json-patch14:42
*** yportnova has joined #openstack-meeting-alt14:43
rosmaitabut, the missing part is the change to the "restricted json pointers"14:43
rosmaitasince now you can do multilevel references for hte location field14:43
markwashah yes14:43
rosmaitai am a little unclear how we want to go on that14:43
rosmaitawhether a general multilevel deal14:43
rosmaitaor only allow /location/whatever14:44
rosmaitaso i was wondering if someone more in the know would like to write it14:44
markwashit will probably take a bit of looking at the code again, as well14:44
markwashrosmaita: is there a drop-dead date for this assignment?14:44
rosmaitanot really14:45
*** shusya has joined #openstack-meeting-alt14:45
zhiyan1rosmaita: after first glance, do you have plan to involve location part in your doc change?  seems there's not14:45
*** kraman has joined #openstack-meeting-alt14:45
rosmaitai can just split the bug and leave the multilevel pointers hanging, and get the new json patch stuff in14:45
markwashrosmaita: I'd like to help, I'm just afraid I'll forget or get distracted14:45
markwashlike if there's something shiny or whatever14:45
rosmaitazhiyan1: probably put an update in the GET images/{image_id} call14:45
rosmaitaand another example for PATCH /images/{image_id}14:46
rosmaitawell, if no one thinks it's pressing, it may take me a while to get around to it14:46
*** ashaikh has joined #openstack-meeting-alt14:46
*** sergmelikyan has quit IRC14:46
rosmaitalike after i get the import/export tasks written up14:46
markwashrosmaita: how about split it and assign it to me14:47
markwashand then if you remember to, bug me about it :-)14:47
rosmaitamarkwash: +114:47
*** bill_az has quit IRC14:47
markwashmoving on. . .14:47
*** bill_az has joined #openstack-meeting-alt14:47
markwash#topic Glance Image Handlers (zhiyan)14:47
*** openstack changes topic to "Glance Image Handlers (zhiyan) (Meeting topic: glance)"14:47
flaper87that was me14:47
flaper87:D14:47
markwashoh14:48
markwashhaha sorry!14:48
flaper87no worries14:48
flaper87:P14:48
markwash#topic Glance Image Handlers (flaper87 )14:48
zhiyan1rosmaita: i prefer add a location PATCH example for end user14:48
*** openstack changes topic to "Glance Image Handlers (flaper87 ) (Meeting topic: glance)"14:48
flaper87so, we had this conversation during the summit about being able to group images and supporting image templates14:48
rosmaitazhiyan1: +1, will note in bug14:48
zhiyan1also thinking are we talking the same point? flaper8714:48
flaper87I wanted to get other folks feedback on that topic and perhaps start working on a blueprint for that14:48
zhiyan1rosmaita: thanks.14:48
flaper87The idea is to have a separate resource that knows about iamge tempaltes14:49
flaper87as images know about images' formats14:49
zhiyan1flaper87: actually i did some work around that, flaper87 https://review.openstack.org/#/c/33409/14:49
*** kraman has quit IRC14:49
markwashzhiyan1: I think actually maybe that is different14:49
markwashbut we're just using the same word "Handler"14:50
flaper87indeed14:50
*** yamahata_ has quit IRC14:50
zhiyan1oh? looking14:50
flaper87so, this images' tempaltes will also make what zhiyan1 did easier to implement14:50
icchai think some folks brought this up at the portland summit as well14:50
markwashso, an image template would be something like, this image for /dev/sda, this image for /dev/sdb? or something else?14:50
icchais there a specfic format? what would template look like?14:51
flaper87Those templates are very hipervisor specific14:51
*** yamahata_ has joined #openstack-meeting-alt14:52
markwashoh, like vmware templates as images?14:52
flaper87markwash: yup14:52
icchai think there exists a bp for it? lemme dig14:52
flaper87oh, is there?14:53
flaper87mmmh14:53
markwashyou also mentioned grouping images14:53
flaper87so, I was thinking about not just creating a resource that people can upload templates too14:53
icchaflaper87: https://blueprints.launchpad.net/glance/+spec/hypervisor-templates-as-glance-images14:53
flaper87but make it smart enough to link existing glance images to that template14:53
icchahttps://blueprints.launchpad.net/glance/+spec/rhev-m-ovirt-templates-as-glance-images14:54
flaper87so that when users download that template, it already holds the information of the images that belong to it14:54
flaper87etc14:54
icchaflaper87: so maybe somehing which over arcs/ generalizes all these bps?14:54
zhiyan1flaper87: just like ova?14:54
flaper87iccha: awesome, thanks a lot!14:54
flaper87so, as for now, Glance just knows about images14:55
markwashflaper87: ah okay. . so this proposal is like representing *some* of the complexity of ovf in glance14:55
zhiyan1sounds like ova to me still14:55
flaper87markwash: yes, but keeping it hypervisor / tempalte agnostic14:55
markwashyeah14:55
flaper87zhiyan1: yeah, kindof14:56
markwashwhich man, I wish ova/ovf were hypervisor agnostic, but it seems probably not14:56
*** jcorbin has joined #openstack-meeting-alt14:56
flaper87markwash: indeed14:56
markwashI think we're clearly building some mental momentum around this kind of idea14:56
flaper87and I don't think we want to pull the hypervisor knowledge into glance14:56
markwashI think for it to get real traction I wanna figure out how we can make sure we have nova buy-in14:57
flaper87yeah, I haven't worked on a *real* proposal yet because I wanted to get folks thoughts about this14:57
*** rraja has joined #openstack-meeting-alt14:57
markwashI mean, for the "disks arrangement" part of ova, I'm pretty sure Nova will be mostly happy14:57
flaper87markwash: it'll require some work in the nova side14:57
*** Barker has joined #openstack-meeting-alt14:57
*** venkatesh has quit IRC14:58
markwasheven an initial proposal could be really useful for fleshing things out14:58
zhiyan1flaper87: under my plan, we can just allow user to put ova into glance as a common image file, and do that magic thing on nova/consumer side, under my image handler approach14:58
zhiyan1flaper87: so i'm interested in what you want to do on glance side14:58
markwashzhiyan1: I think we might have to do that in the short term, but libvirt is never gonna support ova14:58
*** markmcclain has quit IRC14:58
flaper87and I don't like 'tempaltes' being treated as images14:59
*** achirko has joined #openstack-meeting-alt14:59
zhiyan1markwash: yes, but vmware folks can implement a particular ova handler for esxi/vc hypervisor14:59
*** venkatesh has joined #openstack-meeting-alt14:59
flaper87I think is wrong and we can do better by having a real resource for it14:59
markwashso it would be great if we could sort of make a simpler, more generic, implicitly remote concept of ova and represent it in glance14:59
markwashyeah, ova's are not images honestly14:59
zhiyan1markwash: that's no limitation, it's a particular handler implementation14:59
markwashnot in the true sense of an image14:59
*** caitlin56 has joined #openstack-meeting-alt14:59
*** gokrokve has joined #openstack-meeting-alt15:00
*** aostapenko has joined #openstack-meeting-alt15:00
markwashzhiyan1: the problem is that "particular handler implementations" is a fairly divisive approach to doing stuff, and means that different hypervisors feel very differently and can't interoperate15:00
ameadebefore the meeting is over15:00
ameadeWRT the new quotas stuff, do we care about backward compat or would sane defaults be better so deployers don't have to worry about it?15:00
ameadehttps://review.openstack.org/#/c/56981/15:00
markwashooh, great question!15:00
*** glenng has joined #openstack-meeting-alt15:00
*** bswartz has joined #openstack-meeting-alt15:01
*** akerr1 has joined #openstack-meeting-alt15:01
*** mscohen02 has joined #openstack-meeting-alt15:01
markwashI think if the default is really bit its probably fine15:01
markwashlooks like we gotta run!15:01
flaper87so, that's it from me. I see some interest and I'll write something about this topic15:01
markwashs/bit/big/15:01
markwash#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
openstackMeeting ended Thu Nov 21 15:01:35 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-11-21-14.02.html15:01
markwashthanks everybody15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-11-21-14.02.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-11-21-14.02.log.html15:01
ameadesee ya everyone15:01
markwashthanks for patience lurkers!15:01
icchacya15:01
*** Dinesh_ has joined #openstack-meeting-alt15:01
bswartz#startmeeting manila15:01
openstackMeeting started Thu Nov 21 15:01:54 2013 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: manila)"15:01
openstackThe meeting name has been set to 'manila'15:01
*** zhiyan1 has left #openstack-meeting-alt15:02
bswartzhello guys15:02
*** ashwini has left #openstack-meeting-alt15:02
bswartz(and gals)15:02
Dinesh_Hi Bswartz I am Dinesh here15:02
jcorbinHello15:02
achirkoHi15:02
bill_azhi everyone15:02
*** navneet has joined #openstack-meeting-alt15:02
vponomaryovhi15:02
akerr1hello15:02
yportnovahi15:02
*** gregsfortytwo1 has joined #openstack-meeting-alt15:02
bswartzDinesh_: hello!15:02
navneethi15:02
bswartz#link https://wiki.openstack.org/wiki/ManilaMeetings15:02
caitlin56hi15:02
bswartz#topic Incubation15:03
*** openstack changes topic to "Incubation (Meeting topic: manila)"15:03
aostapenkoHello15:03
*** venkatesh has quit IRC15:03
csabahi15:03
bswartzokay so the TC held a meeting on tuesday to decide on our incubation status15:03
rrajaHi15:03
bswartzthey decided that we are NOT ready for incubation as of yet15:03
bswartzthe main concern was the maturity of the project15:04
*** gokrokve has quit IRC15:04
bswartzwhile it's not clearly stated anywhere, they claim that they expect projects to have a stable API and be used in production at least somewhere15:04
bswartzbasically the requirement, as they see it, is that the project has to be "done" and usable in some form15:05
caitlin56No eggs before we see some chickens. or perhaps vise versa.15:05
bswartzI agree with them that we don't meet that definition15:05
gregsfortytwo1did they say "used in production"? I thought it was "ready to be used in production"15:05
*** amytron has joined #openstack-meeting-alt15:05
*** bugsduggan has joined #openstack-meeting-alt15:05
bswartzwhether that's the right defintion for incubation, or whether the defition has changed over time is something we could argue about15:05
bswartzbut I'm not interested in spending time on that15:05
caitlin56gregfortytwo: hard to show that something is ready for production without using it that way.15:06
*** vbellur has joined #openstack-meeting-alt15:06
bswartzgregsfortytwo1: yeah what caitlin56 said15:06
gregsfortytwo1heh, fair enough15:06
caitlin56might be a lab deployment,.15:06
bswartzI think it has to be shown to be used in production at least 1 place15:06
bswartzthat's a pretty low bar, but not that we don't clear currently15:06
*** japplewhite has joined #openstack-meeting-alt15:06
bill_azused in production w/ multi-tenancy?15:07
bswartzthe bigger issue is that we're stilling churning on the method of supporting multi tenancy15:07
bswartzI feel that we now have a clear design and we know how we want to do it15:07
*** rcallawa has joined #openstack-meeting-alt15:07
bswartzbut until the code is complete and tested, we can't claim that we've solved those problems15:07
caitlin56multi-tenancy is key, you can set of NAS for a single tenant just using networking.15:08
bswartzso the path ahead of us is clear: we need to finish the multitenancy support, get it tested, and get some people using it, then we can apply for incubation again15:08
*** bvandehey has joined #openstack-meeting-alt15:08
vbellurbswartz: we had both neutron mediated and hypervisor mediated multi-tenancy model proposals15:08
vbellurdo we need to get at least one of that working before applying for incubation?15:08
bswartzvbellur: yes, either or both of those is probably enough15:08
vbellurbswartz: ok15:08
bswartznow it's not all bad news from the TC15:09
bswartzthey were very impressed with what we've done so far, and they feel we're on the right track15:09
bswartzthey WANT to see manila succeed as a project15:09
caitlin56Did you have a sense that this is *the* blocking issue? That is we can expect approval after this is solved?15:09
vbellurbswartz: good to know!15:09
*** ruhe has quit IRC15:09
bswartzbut they feel that the stamp of "incubation" should be reserved for stuff that's fully usable right now15:09
bswartzand we're simply not there15:10
vbellurright15:10
bswartzof course we could make some digs about the usability of the neutron project -- but I'll refrain from that15:10
caitlin56Kind of makes it hard to have a definite track for developing an API.15:10
bill_azbswartz:  is neutron mediated mulit-tenancy the higher priority / first target?15:11
*** rushiagr has joined #openstack-meeting-alt15:11
bswartzbill_az: in my opinion, yes15:11
rushiagrhi all! late :(15:11
vbellurmaybe all of us can collaborate to get it out first15:11
caitlin56I think we can work on both APIs, but clearly neutron-mediated should be implemented first.15:11
bswartzif a bunch of people show up who are more interested in the hypervisor-mediated method I'll support their work15:11
bill_azbswartz:  I agree - we should put focus there15:11
bswartzbut I think we won't get around to it until later with current resources15:12
bswartzokay so there are 2 important tangible effects of this decision15:12
bswartzthe main reason we wanted to be incubated is that we wanted to move forward with devstack and tempest integrations15:12
bswartzbeyond that, being incubated has little practical effect aside from the PR and the badge of honor15:13
*** bugsduggan has left #openstack-meeting-alt15:13
vbellurbswartz: agree15:14
bswartzso I discovered that devstack had modularized their architecture enough so that we can integrate with it without even being incubated15:14
caitlin56bswartz: the incubation status is defintiely useful in getting resources committed.15:14
bswartzs/had/has/15:14
vbellurcaitlin56: that's right too, we will get more attention from decision makers and the larger community15:15
bswartz#link http://paste.openstack.org/show/53618/15:16
*** ruhe has joined #openstack-meeting-alt15:16
bswartzthere's a fragment of the TC meeting that I captured on the topic of devstack integration15:16
bswartzbtw the whole TC meeting is here if you're interested:15:16
bswartz#link http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-11-19-20.03.log.html15:16
bswartzso we should be able to proceed with devstack integration and get out gate jobs working15:17
bswartzin fact -- the TC indicated that that will be a prerequisite for incubation status going forward15:17
bswartzthey claim it doesn't take more than 1 hour of effort15:17
bswartzintegration with tempest however will still be very difficult15:18
vbellurbswartz: ok, do we have anybody commited to the devstack effort?15:18
bswartzthey cannot accept our tests upstream until we're incubated, which means that we need to continue to maintain a side branch of tempest for our manila tests15:18
*** jtomasek has quit IRC15:19
bswartzand that means we'll be responsible for periodically pulling/rebasing that branch and dealing with any breakage that occurs from the unstable tempest libraries15:19
caitlin56bswartz: exactly how would each vendor set up their test infrastructure as you see it?15:19
*** nati_ueno has joined #openstack-meeting-alt15:20
bswartzvbellur: yeah I haven't talked to yportnova or vponomaryov about that yet, but we should get that done in the coming week15:20
bswartzcaitlin56: so this is what I expect...15:20
vbellurbswartz: ok15:20
bswartzafter we're integrated with devstack, you should be able to install manila directly with devstack15:20
yportnovabswartz: vponomaryov is working on integration with devstack15:20
bswartzyou'll need to configure your tempest to pull from a different git repo with a different branch15:21
*** yamahata_ has quit IRC15:21
bswartzour tempest branch will lag slightly behind tempest/master at all times15:21
*** banix has joined #openstack-meeting-alt15:22
bswartzbut aside from the time lag, all of the same tests should be there, plus our manila ones15:22
vbellurright15:22
caitlin56So we would check out this alternate-tempest branch which would have the default (LVM) version, and then add our own driver. Is that correct?15:22
bswartzcaitlin56: well the drivers will be in the manila tree not tempest15:23
vponomaryovcaitlin56, tempest works with service api, so it does not know anything about beckend15:23
bswartzyou shoudl be able to do manila development, including writing drivers and unit tests without touching tempest at all15:24
bswartztempest tests are about testing integration with the rest of openstack, and testing under a somewhat more realistic environment15:24
vponomaryovuntil service api not changed tempest will still work15:24
*** markmcclain has joined #openstack-meeting-alt15:25
bswartznow we will have our gate tests setup to run tempest, so if you try to submit a driver to manila upstream, it will need to pass those tests15:25
vbellurbswartz: ok15:25
bswartzokay I feel we've gotten a bit offtopic15:26
bswartzthis is all good stuff though15:26
*** ajo has joined #openstack-meeting-alt15:26
bswartzany more questions about incubation before I move on?15:26
*** alazarev has joined #openstack-meeting-alt15:26
vbellurnothing from me15:26
bswartz#topic dev status15:26
*** openstack changes topic to "dev status (Meeting topic: manila)"15:26
bswartzokay any questions about the stuff I mentioned about w.r.t. devstack, tempest, gate, etc?15:27
bswartzs/about/above/15:27
vbellurbswartz: do we plan to add tests for flat network driver in tempest?15:27
bswartzvbellur: yes15:28
vbellurbswartz: ok15:28
bswartzvbellur: and in fact until we have a generic driver that supports multitenancy, that's all we can test15:28
vbellurbswartz: right15:29
bswartzso that suggests that the generic-driver-with-multitenancy will also be a requirement for incubation because it's not possible to do proper gate testing without that15:29
vbelluryeah15:29
bswartzbut I'm not certain about that, we'll need to evaluate when we know more15:29
vponomaryovany multitenancy testing at all15:30
*** ashaikh has quit IRC15:30
vponomaryovnot only gate15:30
bswartzokay so icehouse-1 is coming in 2 weeks15:30
vbellurbswartz: if we decide on the branch and communicate the status, I think we should be able to help in contributing tests to tempest15:31
bswartzvponomaryov: actually it will be possible to do multitenancy testing with the NetApp driver if you have netapp hardware or the netapp simulator, once we complete that work15:31
*** bvandehey has quit IRC15:32
vponomaryovbswartz: yes, I was talking about common testing for everyone with devstack15:32
bswartzyes15:32
bswartzMy feeling is that a NetApp (hardware-based) driver will serve as a better model for other hardware vendors than a pure-ly software-based generic driver however15:32
*** jtomasek has joined #openstack-meeting-alt15:33
bswartzwhich is why I'm pushing for that to be done first15:33
caitlin56bswartz: that's true.15:33
bswartzmy top goal is to make it possible for hardware vendors to start work on their backends15:33
bswartzthe main value of the generic driver will be for gate tests and for people who just want to tinker with manila15:34
bswartzI don't expect the generic driver to provide compelling performance or even features for someone wanting to implement NAS in production15:34
bswartzif it does, then that's great, but it seems unlikely given the underlying technologies15:35
*** ifarkas has left #openstack-meeting-alt15:35
bswartzlaying the generic driver on top of cinder and nova puts it at a disadvantage compared to dedicated hardware solutions15:35
bswartzlayering*15:35
*** pballand has joined #openstack-meeting-alt15:36
caitlin56bswartz: the ground rules for the generic driver doom it to be nothing but a certification tool. But that's all it needs to be.15:36
bswartzcaitlin56: I wouldn't go that far15:36
bswartzthe LVM driver for cinder has turned out to be far more than that, despite the intentions of the cinder team15:37
*** gokrokve has joined #openstack-meeting-alt15:37
*** rongze_ has joined #openstack-meeting-alt15:37
*** devkulkarni has joined #openstack-meeting-alt15:37
vbellurthe LVM driver seems to be the one with most adoption in cinder as per the last user survey15:37
*** rongze has quit IRC15:37
bswartzLet me clearly state that I don't want to handicap the manila generic driver so it's not competitive15:38
bswartzThe generic driver should be as good as it can be given the limitted investment we're able to make in it given everything else we're trying to accomplish15:38
vbellurbswartz: agree15:39
caitlin56there's no need to sabotage it. if you work with any hardware requirements it is handicapped.15:39
bswartzokay so back to dev status15:39
bswartzin the last week we've made a bit of progress on the multitenant stuff15:39
bswartzI learned something I did not know, which might be of interest here15:40
bswartzEvidently many users of OpenStack don't rely on neutron to configure the VLAN trunks for their switches -- it's common to statically configure the switches to pass a bunch of VLANs before setting up openstack15:40
bswartzthen they simply allow neutron to allocate the vlans they're already configured on the switches15:41
bswartzIn that mode of operation, the interaction between manila and neutron is actually quite simple15:41
vbellurbswartz: interesting15:42
caitlin56kind of like a dhcp server where every address was assigned by hand.15:42
bswartzyportnova: did the change for neutron integration go in already15:42
bswartz?15:42
*** __amotoki__ is now known as amotoki15:42
bswartzI think it did15:42
bswartzcaitlin56: hah!15:42
*** sacharya has joined #openstack-meeting-alt15:42
yportnovabswartz: it is not in upstream yet15:43
bswartzyportnova: can you link the change?15:43
bswartzhttps://review.openstack.org/#/c/55555/15:43
bswartzoh I found it15:43
jcorbinbswartz: Why does Manila care how the VLANs are setup? Is it not that they are setup that matters?15:44
jcorbinyportnova: I did a first pass code review and was going to add comments. Is it too late?15:44
bswartzlooks like jenkins is in a bad mood lately15:44
aostapenkobswartz: it will be ready today or tomorrow15:44
*** colinmcnamara has joined #openstack-meeting-alt15:44
caitlin56jcorbin: I agree, how VLANs are set up is something that neutron does. If neutron supports static configuratin then we don't care.15:45
bswartzjcorbin: you're right, assuming that they're setup in advance15:45
yportnovajcorbin: it is not late, feel free to add comments15:45
bswartzjcorbin: however my understand is that neutron is moving in the direction of configuring the vlan trunks on your switchs for you15:45
bswartzunderstanding*15:45
jcorbinbswartz: The vendors can trigger that via their ML2 driver.15:46
*** coolsvap is now known as coolsvap_away15:46
bswartzjcorbin: in order for neutron to be able to add the right vlans to the right switch ports dynamically, we will need a way to discover what the right ports are, and that will require manila to obtain MAC addresses from the storage controllers15:46
caitlin56the point is that the user is able to launch compute nodes for a tenant and access virtual servers on tenant networks.15:46
bswartzjcorbin: yes that's what we've discussed -- so the missing piece right now is a communication path to get the MAC addresses out of the manila backends to where they need to go15:47
bswartzwe'll get there soon15:47
*** boris-42 has quit IRC15:48
bswartzokay so for the coming week, we need to get past this jenkins nonsense, and get a working multitenant backend started15:48
*** markmcclain has quit IRC15:48
jcorbinbswartz: ok15:48
bswartzwe can do those 2 things in parallel15:48
Dinesh_Neutron is also moving in the direction of integrating opendaylight I guess15:49
bswartznext week I hope to be talking about the details of the manila manager/manila backend interactions15:49
caitlin56bswartz: obviously you need to identify the storage serve that will add a VNIC on a tenant network. But why is it at a MAC address layer?15:49
bswartzcaitlin56: a MAC address is what the backend will return back to the manager -- it should be not be the backends job to know what switch port it's cabled to15:50
bswartzthe manila manager (or neutron) can figure that out as long as it has a MAC address from the backend15:50
bswartzokay and since we're winding down on time...15:51
bswartz#topic open discussion15:51
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:51
*** coolsvap_away is now known as coolsvap15:51
bswartzDinesh_: what's opendaylight?15:51
jcorbinAre we meeting next week?15:51
bswartzOH!15:51
vbellurbswartz: http://www.opendaylight.org/15:51
bswartzjcorbin: thanks for reminding me that it's a holiday in the USA next thursday15:51
Dinesh_adopting SDN15:51
Dinesh_it will be a plugin to the neutron15:52
bswartznext week the meeting will be CANCELLED15:52
bswartzhmmm15:52
bswartzwe could try to meet up some time on wednesday15:52
Dinesh_can someone share some info on the multi tenant backend topics you discussed I am bit lost in that....15:52
bswartzperhaps informally in the #manila channel15:52
vbellurbswartz: yeah, having a meeting would be useful15:53
bswartzDinesh_: I can send you some links15:53
Dinesh_thank you bswartz :)15:53
*** ruhe has quit IRC15:53
vbellurbswartz: same time on wednesday in #manila?15:53
Dinesh_one question....has anyone thought about QoS over NFS for a effective multi-tenant solution?15:53
caitlin56I'll be on vacation next week.15:53
bswartzokay here's what I propose: let's get together wednesday Nov 27 at 1500 UTC15:54
*** markmcclain has joined #openstack-meeting-alt15:54
bswartzin the #openstack-manila channel15:54
*** NikitaKonovalov has quit IRC15:54
vbellurbswartz: sounds good15:54
caitlin56Dinesh: you mean Qos=S expressed in NAS terms, rather than in Neutron terms?15:54
bswartzqos?15:54
jcorbinbswartz: meeting time sounds good15:54
bswartzwhat does qos have to do w/ NAS?15:54
*** eharney has joined #openstack-meeting-alt15:55
vbelluri think S expressed in NAS terms15:55
*** SergeyLukjanov has quit IRC15:55
Dinesh_I meant in performance issue....for better throughput and high IOPS something like that15:55
vbellurbswartz: iops, throughput guarantees per tenant?15:55
bswartzDinesh_: that's a good topic for later15:55
bswartzwe don't even have multitenancy working at all right now -- baby steps15:56
*** sergmelikyan has joined #openstack-meeting-alt15:56
*** s3wong has joined #openstack-meeting-alt15:56
vbelluryeah, one at a time15:56
Dinesh_bswartz: yeah I agree...I thought about this solution and working on it15:56
*** navneet has quit IRC15:57
Dinesh_just shared my views :)15:57
bswartzokay please keep us updated, and feel welcome to contribute to the project with the lower level issues we're working on right now15:57
*** kgriffs_afk is now known as kgriffs15:57
bswartzokay anything else?15:57
caitlin56Dinesh: any NAS QoS gets complex if you have any parallelism (such as pNFS) involved.15:57
Dinesh_bswartz : yes sure....please share me the links it will help me better to involve more15:57
vbellurbswartz: nothing else from me15:58
bswartzokay thanks everyone15:58
*** tanisdl has joined #openstack-meeting-alt15:58
vbellurthanks all15:58
bswartz#endmeeting15:58
Dinesh_caitlin56: I am not sure need to check15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Thu Nov 21 15:58:40 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-11-21-15.01.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-11-21-15.01.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-11-21-15.01.log.html15:58
*** rraja has quit IRC15:58
*** jcorbin has quit IRC15:58
*** achirko has left #openstack-meeting-alt15:58
*** vbellur has left #openstack-meeting-alt15:58
*** glenng has left #openstack-meeting-alt15:59
*** bswartz has left #openstack-meeting-alt15:59
*** akerr1 has left #openstack-meeting-alt15:59
*** aostapenko has left #openstack-meeting-alt15:59
*** gregsfortytwo1 has left #openstack-meeting-alt15:59
mesteryAnyone here for the Neutron group policy subteam meeting?16:00
banixHi, Mohammad here16:00
mesterybanix: Hey!16:00
*** aignatov has quit IRC16:00
*** s3wong has quit IRC16:00
*** KDurazzo has joined #openstack-meeting-alt16:01
mestery#startmeeting networking_policy16:01
openstackMeeting started Thu Nov 21 16:01:09 2013 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: networking_policy)"16:01
openstackThe meeting name has been set to 'networking_policy'16:01
mestery#link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy Agenda16:01
mesteryAnyone besides banix and myself?16:01
*** alagalah has joined #openstack-meeting-alt16:02
mesteryalagalah: Welcome!16:02
*** michsmit has joined #openstack-meeting-alt16:02
alagalahmestery: Thank you sir16:02
mesterymichsmit: yo16:02
mesteryFor those who missed it earlier: Agenda is here (https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy)16:03
*** nicole has joined #openstack-meeting-alt16:03
*** uri__ has joined #openstack-meeting-alt16:03
*** caitlin56 has quit IRC16:03
*** nicole has left #openstack-meeting-alt16:03
*** thinrichs2 has joined #openstack-meeting-alt16:04
mestery#link https://etherpad.openstack.org/p/NeutronIcehouseProjectPlan Neutron Icehouse Project Plan16:04
mesteryI wanted to mention the Project Plan for Neutron in Icehouse first.16:04
mesteryPer the Neutron IRC meeting on Monday, the policy work we're doing here is unlikely to make it into Icehouse.16:04
mesteryBut we should continue exploring it and prototyping it to make sure it gets into "J" release.16:04
mesteryAny questions on that?16:05
banixYeah let's push the ball forward16:05
*** prasad_ has joined #openstack-meeting-alt16:05
mesterybanix: Agreed. And we should certainly shoot to get some WIP type patches out for review at some point as well.16:05
mestery#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse Release Schedule (for reference)16:06
mesteryNot the Icehouse dates there, for reference.16:06
mestery#topic Group Based Policy Discussion16:06
*** openstack changes topic to "Group Based Policy Discussion (Meeting topic: networking_policy)"16:06
mesterySo, what I'd like to start doing here is to make sure we all are in agreement around the high level constructs and terms.16:07
mesteryThat will make it easier to move forward in discussions and implementation.16:07
*** rushiagr has quit IRC16:08
mestery#link https://docs.google.com/document/d/1ZbOFxAoibZbJmDWx1oOrOsDcov6Cuom5aaBIrupCD9E/edit?usp=sharing Group Policy Document16:08
*** s3wong has joined #openstack-meeting-alt16:08
mesteryI encourage people to comment in the document as well as on the openstack-dev mailing list.16:08
mesteryQuestions on that?16:08
*** rsblendido has quit IRC16:08
*** rossella_s has quit IRC16:08
thinrichs2I brought this up on the mailing list---I'd like to discuss whether there are plans to include a concrete policy language (or several).16:08
mesterythinrichs2: There are currently no plans at the moment, partially because of how high level the proposal currently is.16:09
mesteryPerhaps it can evolve in this direction though.16:09
*** kgriffs is now known as kgriffs_afk16:10
thinrichs2I ask mainly because I'm trying to figure out how another OS component would use this API.16:10
*** s3wong_ has joined #openstack-meeting-alt16:10
thinrichs2For example, if I were writing Heat, if I don't know what policy language to use, I can't figure out which API calls to make.16:10
michsmitI think getting the constructs into the current model would come first and then a policy language could potentially be layered on top later.16:11
thinrichs2I would know that I need to insert policy/group statements, but I wouldn't know which ones.--unless I knew which plugin we were using for Neutron.16:11
thinrichs2Or am I missing something?16:11
banixthinrichs2: how is this done in Heat now for other resources?16:11
mesterythinrichs2: I think the constructs would dictate what an API user could do, as michsmit is leading to.16:12
banixIsn't the resource specified and the corresponding API called for it?16:12
thinrichs2Heat knows what routers/switches/etc are, and uses them appropriately.16:12
*** s3wong has quit IRC16:12
*** songole_ has joined #openstack-meeting-alt16:12
*** s3wong has joined #openstack-meeting-alt16:12
thinrichs2Banix: But this is different in that the API basically allows us to pass arbitrary strings (policy statements), and we don't know what strings are even syntactically valid, let alone what they mean.16:13
*** japplewhite has quit IRC16:13
*** japplewhite has joined #openstack-meeting-alt16:13
thinrichs2The thought experiment I did was to assume I was trying to build a super-simple version of Heat where I only accepted app templates with a DB tier and a web tier.16:13
*** ErikB has joined #openstack-meeting-alt16:13
*** colinmcnamara has quit IRC16:13
thinrichs2So the template just said how many DB servers and how many Web servers we want.16:13
*** akuznetsov has quit IRC16:13
*** jmontemayor has joined #openstack-meeting-alt16:14
*** jmontemayor has quit IRC16:14
thinrichs2I then need to write a function that takes as arguments number-of-db-servers and number-of-web-servers and outputs a sequence of neutron API policy calls that implements that app.16:14
michsmitThe policy should describe desired connectivity abstracted from topology i.e. group A can talk to group B using Web16:14
thinrichs2But I can't write that down *unless* I know the policy language.16:14
thinrichs2Does any of that make sense?16:15
banixSo to make it easier to begin with, let us assume someone will create the Heat template16:15
*** s3wong_ has quit IRC16:15
michsmitThe "language" could be fairly simple at first.  L4 protocol and ports16:16
michsmitL4 port that is16:16
banixResources are defined based on what Neutron objects are16:16
*** shusya has quit IRC16:17
*** rongze_ has quit IRC16:17
*** eankutse has quit IRC16:17
mesteryI think based on this discussion it's clear we should flesh out the objects and attributes we're talking about a bit more.16:18
michsmitbanix: Agree, I would expect the more topology specific constructs to not be described in the policy such as network but rendered by the extension.16:18
mesteryAny volunteers to do that in the Google doc?16:18
thinrichs2I agree we could invent a bunch of different languages to do this.  Each plugin, for example, could have its own language.  But therein lies the problem.  We don't want Heat to have to know which plugin is being used in order to use the policy API.16:18
banixmestery: I can get it started16:19
mesterybanix: Thanks!16:19
thinrichs2For the policy API to be useful, we should be able to write the following function today, and that function should work for every plugin.16:19
michsmitmestery:  I can help as well16:19
*** jmontemayor has joined #openstack-meeting-alt16:19
mestery#action banix and michsmit to flesh out the objects and attributes we want to expose in more detail in the design document16:20
thinrichs2void create_simple_app(int db-server-num, int web-server-num) { ... }16:20
thinrichs2I'm happy to help as well.  But I'm sure I understand what constructs we're talking about.16:20
mesterythinrichs2: I think the idea is to specify the desired connectivity, but let the plugins handle how that connectivity is achieved (michsmit correct me if I'm wrong here).16:20
banixthinrich2: I think this where we want to get to but we are not there yet16:21
s3wongthinrichs2: that abstraction seems to be more than what Neutron can handle, right? Nova has to be involved as well?16:21
mesterythinrhcs2: Great! DM me your gmail and I can add you to the google doc.16:21
thinrichs2s3wong: Correct--but we *should* be able to write the Neutron API calls today.16:21
s3wongmestery: I would like to be added to that Google Doc as well16:21
banixWhat you are suggesting is perhaps done in an enhanced version of Heat engine or on something on top of it that produces appropriate Heat templates16:21
thinrichs2thinrichs@nicira.com16:21
mesterys3wong: Sure, DM me your google ID so I can add you as well.16:22
s3wongmestery: My email address is s3wong@midokura.com16:22
thinrichs2But I'm still a bit unsure what we're proposing to put into the google doc.16:22
thinrichs2Are we talking about a full language (grammar + semantics)?16:22
*** rongze has joined #openstack-meeting-alt16:23
mesteryNot a full language, but the actual objects/resources we're talking about adding for the extension API, along with attributes.16:23
michsmitI think the Google doc should focus on what needs to be described so that the extension plugin would have enough information to render the existing Neutron objects16:24
banixthinrich2: no, we were talking about Neutron object model here.16:24
michsmitbut yet be independent of network topology16:24
*** s3wong has left #openstack-meeting-alt16:24
*** s3wong has joined #openstack-meeting-alt16:24
thinrichs2If we only talk about the objects, we still aren't giving enough information to actually use the API.16:24
*** s3wong has quit IRC16:25
thinrichs2Suppose I want to add a policy statement.  I don't know which strings are syntactically valid to pass into that API call.16:25
*** s3wong has joined #openstack-meeting-alt16:25
banixSo if you look at the current doc, we are saying we will have these new objects, we want to specify them more precisely to begin with16:25
thinrichs2Anyway--hope my position is clear at this point.  I think that before we start talking about implementing the proposal, we need to hammer out a concrete policy language (that could be extended, etc.)16:27
thinrichs2I'm happy to move onto other topics.16:27
mesteryWell, this is pretty much the only topic for today per the agenda. :)16:28
banixI think we are looking at this from different angles which is perfectly fine; thinrichs2, could you say a bit more, may be later on the dev list ….16:28
*** kraman has joined #openstack-meeting-alt16:28
s3wongPolicy implies rules - wouldn't defining better rules premitives for Neutron be a pre-requisite?16:28
thinrichs2I'm happy to write the example up and send to the dev list.16:29
thinrichs2s3wong: could you elaborate?16:29
*** kgriffs_afk is now known as kgriffs16:29
banixthinrichs2: thanks16:29
*** markmcclain has quit IRC16:29
s3wongPolicy is a set of rules, rules would be {classifier/match -> set of actions}16:29
*** MarkAtwood has joined #openstack-meeting-alt16:30
banixs3wong: agree, that's what we need to define too. At least start with a set of possible rules, or types of rules16:30
s3wongbanix: absolutely16:31
*** ruhe has joined #openstack-meeting-alt16:31
*** ruhe has quit IRC16:31
thinrichs2banix: agreed.  With the current proposal, it's impossible to write down 1 valid API call (and know it's valid for all plugins).16:31
mesterybanix s3wong: Are you volunteering to define the initial rules?16:32
alagalahExcuse my naivety, but if the end game is to make this a part of core Neutron, with Step1 being a plugin, does it make sense to create any missing Neutron primitives in the plugin first since they'll be rolled in eventually anyway?16:32
mesteryalagalah: Not a plugin, an API extension at first, implemented in ML2 as the open source reference implementation.16:32
s3wongmestery: certainly, I would love to16:32
mesterys3wong: Cool, thanks!16:32
prasad_dont we have to define other APIs too such as connectivity group? What goes into the group?16:32
banixmestery: yes sure16:33
alagalahmestery: Sorry, I misread the paragraph in the doc on OpenSrouce Reference Implementation.16:33
mesteryalagalah: No worries.16:33
*** amotoki is now known as amotoki_zzz16:33
*** csaba is now known as csaba|afk16:33
michsmitprasad_: yes, the group would contain the endpoints i.e. entities that source/sink traffic on the network16:34
banixprasad_: yes, that is part of the extension. that's what we want to define more precisely.16:35
mestery#action banix and s3wong to make first pass at defining initial rules.16:35
thinrichs2Could someone explain why we wouldn't want to define groups as part of the policy?  Just curious.16:35
prasad_the question is how are end points defined? VMs, IP addresses?16:35
michsmitGroups are a fundamental primitive that could be used in higher layer policy languages16:36
michsmitprasad_:16:36
*** Barker has quit IRC16:36
banixprasad_: yes, may be ports, as a first step16:37
michsmitprasad_: vnic, ip address as well for external subnets16:37
prasad_dont they have to be precise just like rule definition discussed above. Else it will again be pllugin dependent isnt it?16:37
*** s3wong has quit IRC16:37
mesteryI think it's a safe assumption to assume that if we make any of this plugin dependent we've failed.16:38
thinrichs2I only ask b/c often we end up defining groups implicitly within the policy itself.16:38
thinrichs2mestery: agreed16:38
mesteryThe entire goal of this is to abstract things at a higher level, by exposing plugin primitives this doesn't by us anything.16:38
*** s3wong has joined #openstack-meeting-alt16:38
mesteryLook at the current state of Neutron extension APIs per-plugin to get an idea of why this is a bad idea.16:38
*** colinmcnamara has joined #openstack-meeting-alt16:38
mesteryCloud management vendors need to understand which plugin is running in Neutron before they can appropriately use Neutron, which is bad IMHO.16:39
mesterySo these new APIs need to abstract that away and simplify that state of affairs.16:39
uri__what happens whrn the Plugin can't support a given policy?16:39
KDurazzoquit16:40
*** KDurazzo has quit IRC16:40
*** alazarev has quit IRC16:40
*** kgriffs is now known as kgriffs_afk16:40
thinrichs2uri__: I would imagine we have a core policy language that *every* plugin must support, with extensions to the language that plugins can choose to support or not.16:40
thinrichs2Sort of like the API and its extensions.16:41
mesterythinrichs2: I partially agree, although the extensions idea is a slippery slope.16:41
michsmitThe policy should express the intent of the connectivity independent of the low level networking details.  This should allow the plugin some freedom in making it happen, but at some point if the intent cannot be realized, it would fail the call.16:41
uri__so the "bsic" set maybe  a good starting point16:41
mesteryIt all comes down to the API user an the choices they make.16:41
s3wongmichsmit: agree, if a policy is not supported by a particular plugin, logically it should return error16:42
thinrichs2mestery: I'm certainly happy to have a language w/o extensions.  But extensions are something to keep in the back of our minds, if we find we need them.16:43
*** rcallawa has quit IRC16:43
mesterythinrichs2: Realistically, I agree.16:43
*** colinmcnamara has quit IRC16:44
uri__and in the first version, we assume all policies implemented by ONE plugin? any way for few Plugin to implement each a share? Will ML2 for example divide it up among its mechanism drivers?16:44
*** colinmcn_ has joined #openstack-meeting-alt16:44
mesteryuri__: These APIs will work similar to how the existing APIs work in ML2.16:45
banixWell, I suppose if there are multiple segments in a network, the policy implementation may lead to different mechanism drivers.16:45
mesteryFor example, if a single MechanismDriver fails a create call, ML2 will roll things back and clean up the ones which succeeded prior.16:46
*** flwang has joined #openstack-meeting-alt16:46
uri__mestery: so i'm not sure how ML2 will guarantee to teh User all policy has been implemented. i hope in the opensource we see how this happens and how policies are handled by more than one Mech Driver16:47
*** jmontemayor has joined #openstack-meeting-alt16:47
*** jmontemayor has quit IRC16:47
mesteryuri__: It can guarantee success by the fact that each MechanismDriver returned success when it was called.16:47
s3wongmestery: uri_: and I think that is necessary, otherwise if the policy is only applied partially, it would be a messy state16:48
*** japplewhite has quit IRC16:49
mesteryYes, agreed.16:49
mesteryOK, so we have about 10 minutes left, and I recored two action items so far.16:49
*** colinmcn_ has quit IRC16:49
mesteryIs there anything else we should focus on this week?16:49
*** s3wong has quit IRC16:49
mesteryWith regards to action items for future meetings16:49
mestery?16:50
*** s3wong has joined #openstack-meeting-alt16:50
banixThe next meeting will be in two weeks. Right?16:50
michsmitdo we have timelines for the actions ?16:50
prasad_are the api definition discussions going to take place on the mailing lists?16:51
s3wongThanksgiving next Thursday :-)16:51
mesterybanix: I was going to get to that, hold on. :)16:51
alagalahmestery: I'm sure you and I will talk before then....16:51
*** uri__ has quit IRC16:51
mestery#info No meeting next week (11-28-2013) due to Thanksgiving holiday in the US.16:51
mesterymichsmit: The action items will show up in the meeting logs, and I'll add them to the wiki page.16:51
mesteryWe'll cover those first at our next meeting.16:52
mesteryprasad_: Mailing list and Google doc. If you want on that, please DM me your google ID so I can add you.16:52
*** uri__ has joined #openstack-meeting-alt16:53
*** jmontemayor has joined #openstack-meeting-alt16:53
prasad_mestery_: prasad.vellanki@oneconvergence.com16:53
mesteryThanks prasad_16:53
mesteryOK, thanks everyone for joining the first Neutron Group Policy meeting!16:54
alagalahmestery: thank you16:54
mesteryLooking forward to continuing to make progress with everyone!16:54
mestery#endmeeting16:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:54
banixThank you!16:54
openstackMeeting ended Thu Nov 21 16:54:17 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2013/networking_policy.2013-11-21-16.01.html16:54
s3wongmestery: Thanks!16:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2013/networking_policy.2013-11-21-16.01.txt16:54
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2013/networking_policy.2013-11-21-16.01.log.html16:54
*** uri__ has quit IRC16:54
*** prasad_ has quit IRC16:54
*** s3wong has quit IRC16:55
*** thinrichs2 has quit IRC16:55
*** jmontemayor has quit IRC16:55
*** alazarev has joined #openstack-meeting-alt16:57
*** mscohen02 has quit IRC16:58
*** alagalah has quit IRC16:59
*** jmontemayor has joined #openstack-meeting-alt16:59
*** pdmars has quit IRC17:00
*** aignatov has joined #openstack-meeting-alt17:00
*** rushiagr has joined #openstack-meeting-alt17:01
*** japplewhite has joined #openstack-meeting-alt17:02
*** jmontemayor has quit IRC17:03
*** rudrarugge has joined #openstack-meeting-alt17:05
*** jmontemayor has joined #openstack-meeting-alt17:06
*** Barker has joined #openstack-meeting-alt17:08
*** devkulkarni has quit IRC17:10
*** alazarev has quit IRC17:10
*** markwash has quit IRC17:11
*** rudrarugge has quit IRC17:12
*** japplewhite has quit IRC17:13
*** NikitaKonovalov has joined #openstack-meeting-alt17:14
*** yogesh has joined #openstack-meeting-alt17:14
*** boris-42 has joined #openstack-meeting-alt17:16
*** Dinesh_ has quit IRC17:16
*** michsmit has left #openstack-meeting-alt17:17
*** japplewhite has joined #openstack-meeting-alt17:18
*** eankutse has joined #openstack-meeting-alt17:19
*** kgriffs_afk is now known as kgriffs17:21
*** SergeyLukjanov has joined #openstack-meeting-alt17:22
*** markmcclain has joined #openstack-meeting-alt17:24
*** tanisdl has quit IRC17:26
*** s3wong has joined #openstack-meeting-alt17:26
*** s3wong has quit IRC17:26
*** ekarlso has quit IRC17:30
*** pballand has quit IRC17:31
*** bdpayne has joined #openstack-meeting-alt17:36
*** ekarlso has joined #openstack-meeting-alt17:37
*** ruhe has joined #openstack-meeting-alt17:39
*** ErikB has quit IRC17:41
*** vkmc has quit IRC17:42
*** NikitaKonovalov has quit IRC17:43
*** NikitaKonovalov has joined #openstack-meeting-alt17:44
*** markwash has joined #openstack-meeting-alt17:47
*** NikitaKonovalov has quit IRC17:49
*** coolsvap is now known as coolsvap_away17:50
*** japplewhite has quit IRC17:51
*** NikitaKonovalov has joined #openstack-meeting-alt17:51
*** ashaikh has joined #openstack-meeting-alt17:52
*** akuznetsov has joined #openstack-meeting-alt17:53
*** julim has quit IRC17:53
*** yogesh has quit IRC17:54
*** alazarev has joined #openstack-meeting-alt17:55
*** devlaps has joined #openstack-meeting-alt17:55
*** songole_ has quit IRC17:56
*** vponomaryov has left #openstack-meeting-alt17:57
*** mattf has joined #openstack-meeting-alt17:58
*** colinmcnamara has joined #openstack-meeting-alt17:58
*** yogesh has joined #openstack-meeting-alt18:00
*** sarob has joined #openstack-meeting-alt18:00
*** jspeidel has joined #openstack-meeting-alt18:00
*** pdmars has joined #openstack-meeting-alt18:02
*** derekh has quit IRC18:02
*** NikitaKonovalov has quit IRC18:02
SergeyLukjanovhowdy savanna folks18:03
*** jmaron has joined #openstack-meeting-alt18:03
ruhehey18:03
aignatovo/18:03
mattfhowdy18:04
jspeidelhi18:04
SergeyLukjanovok, we have  a quorum18:04
*** NikitaKonovalov has joined #openstack-meeting-alt18:04
SergeyLukjanov#startmeeting savanna18:04
openstackMeeting started Thu Nov 21 18:04:52 2013 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:04
*** openstack changes topic to " (Meeting topic: savanna)"18:04
openstackThe meeting name has been set to 'savanna'18:04
SergeyLukjanov#topic Agenda18:05
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:05
*** eankutse has quit IRC18:05
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_November.2C_2118:05
SergeyLukjanov#topic Action items from the last meeting18:05
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"18:05
SergeyLukjanov#info there are no action items from the prev. meeting18:05
SergeyLukjanov#topic News / updates18:05
*** openstack changes topic to "News / updates (Meeting topic: savanna)"18:05
*** boris-42 has quit IRC18:05
SergeyLukjanovfolks, please18:06
SergeyLukjanov#info our next release will be icehouse-1 (Dec, 5)18:06
mattflooks like the bug day went well, and rather fast. i had a couple morning calls and you guys were 95% done by 11ET!18:06
*** sarob has quit IRC18:07
*** japplewhite has joined #openstack-meeting-alt18:07
*** sarob has joined #openstack-meeting-alt18:07
mattfhttps://wiki.openstack.org/wiki/Icehouse_Release_Schedule18:07
SergeyLukjanov#info we have an awesome bug day and almost all issues are now in actual state18:07
aignatovthis week I started to check dmitryme patch about preliminary heat integration and stucked in heat installation on my laptop18:07
*** twoputt has joined #openstack-meeting-alt18:08
*** twoputt_ has joined #openstack-meeting-alt18:08
*** japplewhite has left #openstack-meeting-alt18:08
aignatovit seems heat was installed successfully but patch seem to be not working properly :)18:08
SergeyLukjanovbtw at the last project meeting we decided that I'll release (tag) i1 and the ttx will take over and start doing it by icehouse-218:09
*** markmcclain has quit IRC18:09
SergeyLukjanovand then*18:09
*** nadya_ has joined #openstack-meeting-alt18:09
jmarondoes dmitryme patch make provisioning pluggable?  It's be nice to be able to accommodate any other provisioning techs we come across..18:09
SergeyLukjanovso, we'll be a part of centralized release, not integrate yet :)18:09
SergeyLukjanovjmaron, not yet18:10
jmaron:(18:10
aignatovno, right now, his patch just replace main logic of provisioning18:10
SergeyLukjanovit was done to check possibility of Heat integration18:10
SergeyLukjanovit's a PoC18:10
jmarongotcha18:10
aignatovand it works on his Laptop ;)18:11
SergeyLukjanovwe'll make a pluggable mechanism to transparently merge and polish Heat support18:11
jmaron:)18:11
jspeidelship it ;)18:11
SergeyLukjanovand then make it defailt18:11
jmaronde-fail?  ;)18:11
*** ErikB has joined #openstack-meeting-alt18:11
aignatovyeah, I like this approach, Sergey18:12
*** sarob has quit IRC18:12
jmaron+118:12
jmaronwe should probably maintain the current nova based scheme as another plugin18:13
ruheis there something which heat is missing, but current provisioning mechanism already provides? for instance anti-affinity18:13
jmaronsome of the /etc/hosts manipulation, I believe18:13
SergeyLukjanovjmaron, I think it'll live at least before Heat-based provisioning will be completed18:14
jmaronis missing18:14
SergeyLukjanovjmaron, yep18:14
SergeyLukjanovbut we'll start from resources orchestration18:14
SergeyLukjanovand I hope that we'll land some kind of agents till the end of I18:14
SergeyLukjanovand so we'll avoid all the ssh/http from controller to vms18:15
nadya_will anybody start working on contribution to heat?18:15
aignatovjmaron, as i remember and understood it correctly, heat guys told us that Neutron somehow can apply ip addresses before provisioning, so etc host manipulation could be done during cloud init script running18:15
SergeyLukjanovaignatov, could you please make an update about our CI lab18:15
*** ErikB has quit IRC18:16
aignatovCI Lab is broken :(18:16
aignatovso it will set -1 always from now18:16
*** ErikB has joined #openstack-meeting-alt18:16
jmaronany sense how long to fix?18:16
jspeidelis this a temporary issue that is being resolved?18:16
SergeyLukjanovaignatov, yep, AFAIK it's possible to acquire IP addresses from Neutron and then generate Heat template18:17
aignatovit happened during moving ci from grizzly to havana18:17
alazarevaignatov: will this work for floating IPs?18:17
aignatovjspeidel: this temporary, our deployers do the best to make it work again18:17
*** boris-42 has joined #openstack-meeting-alt18:18
aignatovalazarev: don't know, need to dig it18:18
SergeyLukjanovok, let's move on18:18
nadya_i think ips assignment is the idea for the one more PoC18:18
ruhealazarev, we don't need floating ip for /etc/hosts18:18
jmaronneutron client allows querying for floating IP pools, I believe, so it seems possible18:18
jmaronruhe:  oh yeah…true18:19
*** gokrokve has quit IRC18:19
*** boris-42 has quit IRC18:19
SergeyLukjanovonly internal IPs needed to generate etc hosts18:19
SergeyLukjanov#topic Icehouse-1 plans18:19
*** openstack changes topic to "Icehouse-1 plans (Meeting topic: savanna)"18:19
*** yogesh has quit IRC18:19
SergeyLukjanovi1 will be in two weeks18:19
SergeyLukjanovso, looks like it's too late to plan something big on it18:20
alazarevruhe: oh, true18:20
aignatovjspeidel: we will retrigger ci jobs for all failed tests in each patch18:20
SergeyLukjanovare there any thoughts about critical issues or bps that should be landed in i1?18:20
jspeidelaignatov: thanks for the update18:20
jspeidelfor hdp, we are working on18:21
jspeidelhttps://blueprints.launchpad.net/savanna/+spec/hdp-specify-local-repo18:21
jspeidel and https://blueprints.launchpad.net/savanna/+spec/hdp-hdp2-support18:21
aignatovSergeyLukjanov: may be we just need to fix all high priority bugs in i1. what do you think?18:21
aignatovor at least all18:21
*** gokrokve has joined #openstack-meeting-alt18:21
SergeyLukjanovjspeidel, I prefer to not land huge patches more one week before the milestone18:22
mattffyi, next week is a standard vacation week in the US18:22
aignatovat least -> almost18:22
ruheis it turkey week?18:22
SergeyLukjanovUS folks, how'll be on vacation next week? :)18:22
jspeidelSergeyLukjanov: agreed that this work will not be complete for i118:22
ErikBruhe, yes18:23
jmaronturkey/dreidel week, actually18:23
mattfruhe, it is18:23
SergeyLukjanovjspeidel, I'm talking only about icehouse-1 now, don't worry about rest 4.5 months :)18:23
SergeyLukjanovaignatov, it'll be great if we'll close high prio bugs18:24
SergeyLukjanovin fact only one is https://bugs.launchpad.net/savanna/+bug/124363818:25
SergeyLukjanovhttps://bugs.launchpad.net/savanna/+bug/1240511 is randomly reproducable18:25
SergeyLukjanovand https://bugs.launchpad.net/savanna/+bug/124906318:25
SergeyLukjanovI'll take it18:25
SergeyLukjanovhttps://bugs.launchpad.net/savanna/+bug/1252684 I'm not sure that it's doable atm18:26
*** rcallawa has joined #openstack-meeting-alt18:26
aignatovhttps://bugs.launchpad.net/savanna/+bug/1240511 is wired, yeah18:26
SergeyLukjanovany thoughts?18:26
SergeyLukjanovok, let's move on18:27
SergeyLukjanov#topic Versioning and issues/bps management18:27
*** openstack changes topic to "Versioning and issues/bps management (Meeting topic: savanna)"18:27
*** rnirmal has joined #openstack-meeting-alt18:27
SergeyLukjanovI've talked today with ttx about savanna subprojects versioning and releasing18:28
*** NikitaKonovalov has quit IRC18:28
SergeyLukjanovthere are two mandatory changes needed18:28
*** rcallawa has left #openstack-meeting-alt18:28
SergeyLukjanov#info use a separate project and versions for the client18:28
aignatovjfyi, ttx is release manager of openstack18:29
SergeyLukjanovand release -extra separately too because it's not really connected to the main project18:29
*** markmcclain has joined #openstack-meeting-alt18:29
SergeyLukjanovand should moved to the Hadoop community18:29
SergeyLukjanovttx == Thierry Carrez18:29
aignatovwhat you mean should moved to hadoop community?18:30
*** NikitaKonovalov has joined #openstack-meeting-alt18:30
nadya_they dont want to have java code18:30
SergeyLukjanovOpenStack community is not the best place for Hadoop FS and java code :)18:30
*** julim has joined #openstack-meeting-alt18:30
SergeyLukjanovand due to the fact that it was partially landed to the Hadoop, we should push it to the Hadoop eco I think18:31
mattf-extra is currently swift plugin for hadoop and edp example18:31
SergeyLukjanovyep18:31
mattf+1 to that18:31
mattfstevel has posted backports of the swift plugin to both the hadoop 1.x and 2.x branches18:31
SergeyLukjanovas for the edp example - it's strongly wired with main code and could be moved to the savanna repo18:32
alazarevmattf: it is in 2.x only for now18:32
ruhethere is a problem with this plugin being a part of hadoop code18:32
mattfi'm mildly concerned about the edp test jar files18:32
mattfi was thinking about proposing they get moved to -extra18:32
ruheit'll be difficult to update it with changes in OpenStack api18:32
alazarevmattf: do you have info about 1.x?18:32
SergeyLukjanovall tests will be moved to the tempest eventually18:33
nadya_i think i should find sources of jars18:33
SergeyLukjanovall integration tests*18:33
nadya_and publish18:33
mattfalazarev, yeah, i can share the email w/ you after the meeting18:33
nadya_anybody hear me?18:33
mattfnadya_, +1 at a minimum18:33
nadya_great :)18:33
SergeyLukjanovnadya_, it'll be great to publish sources18:33
alazarevmattf: thank you, please do it18:33
*** eankutse has joined #openstack-meeting-alt18:33
*** eankutse has quit IRC18:34
aignatovudf.jar is piggybank, all rest code is self-written18:34
aignatovthat's all examples18:34
*** eankutse has joined #openstack-meeting-alt18:34
SergeyLukjanovso, for now, I think to keep -extra as is and release it with main savanna code18:34
SergeyLukjanovto keep examples near to the project18:34
alazarevmattf: because I'm doing back port to 1.x right now, it would be great if everything is already done18:34
mattfalazarev, i would imagine!18:35
rnirmalbackport the swift plugin to 1.x ?18:35
mattfyes18:35
alazarevyes18:35
rnirmalyeah it works with 1.x .. one or two minor tweaks18:35
SergeyLukjanovwe'll have separated launchpad projects for both client and dashboard plugin18:35
alazarevthe next step is to push data locality patch to both 1.x and 2.x18:35
mattfSergeyLukjanov, btw, call me a purist, but committing a jar to git is wrong18:36
*** Barker has quit IRC18:36
ruhemattf, that's wrong indeed18:36
aignatovagree with mattf18:36
jmaronpurist18:36
alazarevswift data locality18:36
jspeidelmattf: +118:36
SergeyLukjanovmattf, I'm absolutely agree, that's just temp solution18:36
mattfgit never forgets18:36
aignatovwe just need to describe instructions where to find needed jar file18:36
nadya_what jar do you mean?18:36
*** NikitaKonovalov has quit IRC18:36
alazarevmattf: +118:36
ruhecan't we upload it to the same place where qcow2 images are hosted?18:37
aignatovudf.jar in current examples is here https://cwiki.apache.org/confluence/display/PIG/PiggyBank18:37
SergeyLukjanovnadya_, any jar18:37
nadya_udf.jar ?18:37
SergeyLukjanovnadya_, any binary file18:37
jmaronyes18:37
nadya_sergey, I mean our case18:37
mattfnadya_, specifically these jars = https://review.openstack.org/#/c/56235/18:37
SergeyLukjanovyep18:37
SergeyLukjanovwe have 2 more subprojects - dashboard and elements and here we have several options18:38
nadya_we move swift plugins to Hadoop, udf i will publish. i thought we have no more jars18:38
aignatovedp-lib.jar is udf.jar or piggybank, edp-job.jar is renamed oozie-examples18:38
jmaronalazarev:  data locality patch?18:38
aignatovwe don;tneed to keep it in any repo18:38
*** NikitaKonovalov has joined #openstack-meeting-alt18:39
SergeyLukjanovlet's return back to the releasing/versions18:39
nadya_ah, libs...i see18:39
alazarevjmaron: https://review.openstack.org/#/c/47824/18:39
SergeyLukjanovwe'll release client much faster than savanna and so we can release dashboard too18:40
SergeyLukjanovthe question is - should we adjust our dashboard releases with savanna or not18:40
* mattf considers getting off his client soapbox18:40
*** NikitaKonovalov has quit IRC18:40
*** NikitaKonovalov has joined #openstack-meeting-alt18:40
*** lblanchard has quit IRC18:40
SergeyLukjanovthe same with elements18:40
mattfadjust with savanna?18:40
*** rongze has quit IRC18:40
nadya_anyway, looks like we may add lib to maven dependencies w.g. I think we may find a way to avoid jars18:41
SergeyLukjanovI mean main code18:41
ruheSergeyLukjanov, definitely should18:41
mattfadjust = align?18:41
SergeyLukjanovyep18:41
*** yogesh has joined #openstack-meeting-alt18:41
alazarevSergeyLukjanov: we should somehow sync APIs they use/provide18:41
ruheSergeyLukjanov, otherwise it'll make a hell to those who bundle savanna into distro packages18:41
SergeyLukjanovruhe, sounds reasonable18:42
jspeidelagreed, they should be aligned18:42
mattfwe have a handful of deliverables: savanna, dashboard, elements, client, extra. we're versioning and releasing them all together. what's the desired end state?18:42
aignatovso, in such case, if savanna is in active development and savannaclient is not because it already has need functional, savannaclient amy become i2 from i1 without any patch, right?18:43
SergeyLukjanovmattf, we'll have separated versioning for client starting from today18:43
mattfsounds like extra -> /dev/null, client -> independent entity, savanna -> independent entity, dashboard -> horizon18:43
SergeyLukjanovyep, we'll do it after graduating from the incubation18:43
alazarevmattf: in this case after API change in any component it could be used only in next release18:44
SergeyLukjanov(I mean horizon)18:44
mattfalazarev, i'm not as firmly on my soapbox so long as the releases cycles are separated18:44
SergeyLukjanovclient should keep backward compatibility and support prev. APIs versions18:44
jmaronis extra going away?  I got impression some EDP code would remain18:45
mattfalazarev, if we release client in i1 and have to wait 6 weeks to fix dashboard in i2, ugh18:45
SergeyLukjanovclient will be released separately anyway, it's not a question to discuss18:45
mattfSergeyLukjanov, yeah, well done identifying the problem and defusing the argument18:46
SergeyLukjanovthe question is only about -dashboard and -image-elements18:46
mattfwhat if we start pushing our elements up to dib?18:46
ruhei demand client releases on the same date with the main code. there might be additional releases for sure18:46
nadya_mattf, lol18:46
mattfruhe, is SergeyLukjanov close enough to throw something at you?18:47
ruheno :)18:47
mattfdarn18:47
SergeyLukjanovruhe, it's not a common approach in OpenStack18:48
mattfruhe, you're proposing a stronger alignment. not only is client released whenever we feel like it but it is also _always_ released w/ savanna main?18:48
SergeyLukjanovclients have new releases after some important fixes or after some period of time18:48
mattfto that i'd say sure, as long as i'm not doing the extra, potentially unnecessary, work to do that release18:48
SergeyLukjanovminor releases18:48
SergeyLukjanovand major for new release cycles and API versions18:48
ruhemattf, otherwise how can we align all the dependencies when packaging savanna, dashboard and client into disto packages18:49
mattfi think we accept that version numbers no longer match18:49
SergeyLukjanovruhe, I don't think that it's a problem18:49
mattfimho version numbers should not be aligned to identify compatibility. that's what deps are for.18:49
SergeyLukjanovruhe, the same story with all other OpenStack projects18:50
jmaronmattf:  +118:50
ruheSergeyLukjanov, i only want all the dependencies to be aligned. otherwise newer version of pythonclient might be api-compatible for denendency-incompatible18:50
*** NikitaKonovalov has quit IRC18:51
ruhe*but denendency-incompatible18:51
SergeyLukjanovbtw, the next releases will be 2014.1.b1 for savanna, 0.4 for python-savannaclient and if we decided to keep rest subprojects aligned with main savanna releases than they'll be 2013.1.b1 too18:51
mattfhow about the idea of elements -> dib ?18:52
SergeyLukjanovmattf, only after incubation18:52
mattfwhy's that?18:52
SergeyLukjanovit's an integrated project18:52
*** NikitaKonovalov has joined #openstack-meeting-alt18:53
jmarondib, that is?18:53
ruhehttps://github.com/openstack/diskimage-builder18:53
SergeyLukjanovttx suggests to move them to the savanna repo for the I release (like trove guys done) and then move them to dib or tripleo18:53
SergeyLukjanovbut it looks like that we should keep them separately and just release them with main code18:54
aignatovmattf, who wanted to move elements to savanna repo originally? ;)18:54
SergeyLukjanovaignatov, not me, I have concerns about gating them and just using18:54
SergeyLukjanovthe same story with -extra repo18:54
SergeyLukjanovso, I think the main question is still about -dashboard18:55
SergeyLukjanovis it better to be possible to push more versions for it?18:56
jmaronhow fluid do we think it's going to be, feature wise?18:56
alazarevdashboard should indicate with which savanna version it works18:56
alazarevis any way to do that without having releases synced?18:57
SergeyLukjanovdashboard only depends on client :)18:57
SergeyLukjanovthat's released separately18:57
SergeyLukjanovthat's my concern18:57
SergeyLukjanov[savanna, -image-elements, -extra] [client] [dashboard]18:58
SergeyLukjanov^^ my current opinion18:58
SergeyLukjanovand then we move dashboard to horizon and we'll have only two separately releasing groups18:59
SergeyLukjanovlooks like we're out of time, let's move to the #savanna and continue discussion18:59
nadya_i dont understand what variants we have except the above18:59
SergeyLukjanovit'll be better to complete it tpday18:59
alazarevand how dashboard and savanna linked in this case? By docs?18:59
*** amcrn has joined #openstack-meeting-alt18:59
*** jspeidel has left #openstack-meeting-alt18:59
*** jmaron has left #openstack-meeting-alt19:00
SergeyLukjanovthank you all guys19:00
SergeyLukjanov#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Thu Nov 21 19:00:09 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-11-21-18.04.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-11-21-18.04.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-11-21-18.04.log.html19:00
*** _ozstacker_ has quit IRC19:00
alazarevmattf: please forward me email about swift in hadoop 1.x19:00
*** _ozstacker_ has joined #openstack-meeting-alt19:01
*** nadya_ has quit IRC19:03
*** gokrokve has quit IRC19:04
*** gokrokve has joined #openstack-meeting-alt19:04
*** sarob has joined #openstack-meeting-alt19:06
*** gokrokve has quit IRC19:08
*** colinmcnamara has quit IRC19:11
*** rongze has joined #openstack-meeting-alt19:11
*** akuznetsov has quit IRC19:11
*** mattf has left #openstack-meeting-alt19:13
*** NikitaKonovalov has quit IRC19:14
*** akuznetsov has joined #openstack-meeting-alt19:17
*** NikitaKonovalov has joined #openstack-meeting-alt19:17
*** rongze has quit IRC19:18
*** rushiagr has quit IRC19:19
*** gokrokve has joined #openstack-meeting-alt19:20
*** nadya has joined #openstack-meeting-alt19:21
*** nadya is now known as Guest289319:21
*** devkulkarni has joined #openstack-meeting-alt19:24
*** jtomasek has quit IRC19:28
*** ashaikh has quit IRC19:32
*** alazarev has quit IRC19:37
*** lblanchard has joined #openstack-meeting-alt19:37
*** ErikB has quit IRC19:38
*** Guest2893 has quit IRC19:43
*** ThiagoCMC has joined #openstack-meeting-alt19:44
*** amcrn is now known as [a]mcrn19:44
*** rongze has joined #openstack-meeting-alt19:45
*** ruhe has quit IRC19:45
*** akuznetsov has quit IRC19:46
*** alazarev has joined #openstack-meeting-alt19:49
*** rongze has quit IRC19:50
*** s3wong has joined #openstack-meeting-alt19:51
*** sarob has quit IRC19:51
*** sarob has joined #openstack-meeting-alt19:52
*** ashaikh has joined #openstack-meeting-alt19:54
*** jdbarry has quit IRC19:56
*** sarob has quit IRC19:56
*** jdbarry has joined #openstack-meeting-alt19:58
*** sarob has joined #openstack-meeting-alt19:59
*** sarob has quit IRC19:59
*** bdpayne has quit IRC19:59
*** sarob has joined #openstack-meeting-alt19:59
*** bdpayne has joined #openstack-meeting-alt20:00
*** yogesh has quit IRC20:01
*** devkulkarni has quit IRC20:03
*** s3wong has left #openstack-meeting-alt20:05
*** yogesh_ has joined #openstack-meeting-alt20:05
*** s3wong has joined #openstack-meeting-alt20:07
*** rwsu has joined #openstack-meeting-alt20:08
*** sc68cal has joined #openstack-meeting-alt20:08
*** devkulkarni has joined #openstack-meeting-alt20:10
*** radix_ has quit IRC20:12
*** vipul is now known as vipul-away20:15
*** vipul-away is now known as vipul20:15
*** colinmcnamara has joined #openstack-meeting-alt20:18
*** tedross has joined #openstack-meeting-alt20:20
*** colinmcnamara has quit IRC20:22
*** bdpayne has quit IRC20:23
*** colinmcnamara has joined #openstack-meeting-alt20:27
*** bdpayne has joined #openstack-meeting-alt20:30
*** alazarev has quit IRC20:34
*** yogesh has joined #openstack-meeting-alt20:35
*** ashaikh has quit IRC20:37
*** yogesh_ has quit IRC20:37
*** vipul is now known as vipul-away20:38
*** vipul-away is now known as vipul20:38
*** colinmcnamara has quit IRC20:39
*** ashaikh has joined #openstack-meeting-alt20:41
*** rongze has joined #openstack-meeting-alt20:47
*** markmcclain has quit IRC20:47
*** ThiagoCMC has quit IRC20:49
*** rongze has quit IRC20:51
*** djoreilly has joined #openstack-meeting-alt20:53
*** vipul is now known as vipul-away20:53
*** kgriffs is now known as kgriffs_afk20:54
*** vipul-away is now known as vipul20:54
*** aveiga has joined #openstack-meeting-alt20:55
*** markmcclain has joined #openstack-meeting-alt20:57
*** shshang has joined #openstack-meeting-alt20:57
shshangHello20:58
mesteryo/20:59
aveigahello20:59
shshangNew to the meeting, sorry for any inconvenience in advance. :)20:59
mesteryshshang: No worries, lets wait until sc68cal starts things up.20:59
*** bdpayne has quit IRC21:00
sc68calHello21:01
sc68cal#startmeeting neutron_ipv621:01
shshangHello, Sean21:01
openstackMeeting started Thu Nov 21 21:01:11 2013 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** bdpayne has joined #openstack-meeting-alt21:01
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"21:01
openstackThe meeting name has been set to 'neutron_ipv6'21:01
*** kraman has quit IRC21:01
*** kraman has joined #openstack-meeting-alt21:01
sc68calOK - thank you everyone that has decided to attend21:02
*** BrianB_ has joined #openstack-meeting-alt21:02
sc68calThe agenda is pretty straight forward21:02
*** SergeyLukjanov has quit IRC21:02
sc68calMy name is Sean Collins, and I work for Comcast21:03
shshangGreat to "see" you, Sean21:03
sc68calplease feel free to introduce yourselves21:03
*** dprince has quit IRC21:03
*** kgriffs_afk is now known as kgriffs21:03
aveigaI'm Anthony Veiga, IPv6 SME at Comcast21:03
shshangMy name is Shixiong. I used to work for Cisco, but recently joined a startup working on OpenStack and IPv621:03
*** denis_makogon has quit IRC21:04
*** denis_makogon_ is now known as denis_makogon21:04
mesteryHowdy folks, Kyle from Cisco.21:04
shshangHi, Kyle21:04
*** dmakogon_ has joined #openstack-meeting-alt21:04
sc68calI am mostly working with aveiga to get OpenStack Neutron to work with the networking environment we have set up at Comcast21:05
sc68calAs such, we're busy creating bugs and blueprints to cover things that we need done right away, to make it work in our environment, as well as some blueprints that probably would be useful to the community as well21:05
sc68cal#link https://bugs.launchpad.net/neutron/+bug/125285221:06
*** carlp has joined #openstack-meeting-alt21:06
*** ijw has joined #openstack-meeting-alt21:06
sc68calhmm, not sure if that worked or not21:06
sc68cal#link https://bugs.launchpad.net/nova/+bug/125123521:06
sc68cal#link https://bugs.launchpad.net/neutron/+bug/124293321:06
ijwevening ladies and gents21:07
sc68calhi ijw - welcome21:07
shshanginteresting...the 2nd bug explained what we saw before....21:07
carlpo/21:07
mesterysc68cal: Try #link <link> <description>21:07
ijwSeen that first one, it's bloody annoying21:07
*** ashaikh has quit IRC21:07
mesteryIt will show in hte logs.21:07
sc68cal#link https://bugs.launchpad.net/nova/+bug/1251235 ip6tables rules isssues21:08
shshangfor the first one, I think ip6tables also drops ND packets, if I am not mistaken21:08
ijwDidn't when I tried it21:08
ijwThe second's very risky - need to source-filter your RAs21:08
aveigashshang: It does21:08
sc68calYeah, that's due to the hairpinning on the bridge device21:08
ijw(speaking as a man of much experience and bitterness with some muppet in the lab sending them out)21:08
sc68cal#link https://bugs.launchpad.net/nova/+bug/125123521:09
sc68cal#link https://bugs.launchpad.net/nova/+bug/1251235 hairpinning issue for DAD21:09
sc68calsorry, still getting used to this :)21:09
shshangis there any workaround for the 2nd bug?21:09
sc68calshshang: for the hairpin?21:09
shshangyup21:10
aveigathe workaround we're using currently is a very painful and manual process to disable hairpinning on the tap21:10
shshangI had to manually disable DAD21:10
sc68calshshang: yeah, I have a patch to nova that's in review21:10
shshangon guest VM before21:10
*** ashaikh has joined #openstack-meeting-alt21:10
*** haleyb has joined #openstack-meeting-alt21:10
sc68calshould be linked in the bug report21:10
* haleyb never knew about the -alt channel until today21:10
shshangI see. Thanks for bringing it up21:11
sc68calBasically this stuff I've filed has been for our immediate goal, getting IPv6 networks that we have existing outside of openstack, to work with OpenStack the way provider networks does on the v4 side21:11
sc68calObviously, IPv6 has some differences, since OpenStack wants to be the source of truth for things like subnets21:11
sc68caland that's where we're running up against issues, where OpenStack gets confused and creates ip6tables rules for ::/128 in the security group rules21:11
aveigawe should consider a longer term roadmap of the parts of IPv6 that we need to get working21:11
sc68calaveiga: +121:12
shshangagree21:12
sc68cal#link https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac21:12
shshang#agreed21:12
*** Dane has joined #openstack-meeting-alt21:12
sc68calThat's a blueprint I'm trying to collect all my immediate work, to get IPv6 running inside OpenStack21:12
shshangThere is a hacking way to make dnsmasq to announce RA21:13
ijwI don't think you'll be able to determine how routers should work in an hour long IRC meeting, to be honest...21:13
shshangbut it is quite a hassle21:13
aveigaWhat I want to make sure we don't do is be blinded by individual goals.  I realize there are many people who want IPv6 that aren't necessarily keen on it being done via l2-provier21:13
aveigaso that said, we've already got IPv6 via l2-provider/slaac as one implementation21:13
aveigaare there others that should be looked at for immediate needs?21:14
sc68calWe also want to extend DNSmasq so that you can do things like DHCPv6, create subnets on the v6 side and get things on par with the v4 side21:14
sc68cal#link https://blueprints.launchpad.net/neutron/+spec/dnsmasq-mode-keyword21:14
ijwWhat are you doing about antispoof with SLAAC?21:14
sc68calmore long term21:14
aveigaijw: right now, nothing21:14
aveigahowever, I think the goal should be that when you create a subnet in an IPv6 SLAAC network, we should configure the router21:15
aveigaand then use the router's information to populate the source list for RA inpouts21:15
shshang@sc68cal, I am a little bit confused about the #link https://blueprints.launchpad.net/neutron/+spec/dnsmasq-mode-keyword21:16
aveigabut again, we're in the baby steps mode right now of just getting it to work at a low level before implementing21:16
ijwWhat I said about how long it'll take to decide that definitely applies.  Firstly, ipv4 routers don't advertise routes, but v6 ones do - so probably we should add a route-advertise flag on the network that both respect.21:16
sc68calshshang: what has you confused?21:17
*** aignatov has quit IRC21:17
shshangif we only talk about SLAAC here, then the way it is coding today has capability to detect subnet type. And if subnet is IPv6, then trigger RA.21:18
*** flaper87 is now known as flaper87|afk21:18
shshangHowever, if we talk about DHCPv6 and SLAAC, then yes, we need to provide options for user to define what they want21:18
ijwI'm not sure you're allowed to assume that the link-local address is what the MAC suggests it is.21:18
aveigaijw: are you referring to privacy extensions?21:19
ijwThey don't apply to link local iirc21:19
aveigaoops, missed that part21:19
shshangagreed21:20
aveigawhat case would exist where the lla isn't EUI-64 derived?21:20
ijwTrying to remember if link local is *required* to or *recommended* to be based on the link address.21:20
shshangin my experiment, VM boots and it has linklocal address in any way. it doesn't need Openstack's help21:21
aveigaI don't know that lla is relevant here21:22
shshangthe question here is, 1) How Openstack can send RA if we offer SLAAC 2) How OpenStack can store the SLAAC IPv6 address VM calculate21:22
aveigalet's take a step back21:22
carlpijw: looks like it's required http://tools.ietf.org/html/rfc4291#section-2.5.621:22
aveigashshang: We don't necessarily want OpenStack to issue the RA in all cases21:23
aveigajust in cases where an l3 agent is the gateway21:23
sc68calOh, I nearly forgot, Dazhao yu is working on a patch to do the calculations for EUI-6421:23
aveigamost guests OSes ignore multiple RAs or ignore RA priority, and as such we'd blackhole them issueing RAs21:24
sc68cal#link https://review.openstack.org/#/c/56184/ Calculate stateless IPv6 Addresses21:24
sc68calI think it just needs to be done against oslo, not neutron21:24
sc68calSo, it's a bit of a info dump from what aveiga have been doing.21:26
sc68calThere seems to be a lot of stuff where people have run into the same issues, but nothing seems to go back up into Neutron21:26
sc68callike hairpinning, etc.21:26
shshang@aveiga, I can see your points in some setups.......is it a good approach to completely rely on external router?21:27
ijwcarlp - tehre's a few 'should' rather than 'must' in rfc2464 that leave it ambiguous21:27
carlpijw: true, but the diagram shows using the interface address which makes it seem like a must21:28
ijwYep, but how the interface address is calculated is where the 'should' comes in.  That's a 64 bit value, there are options on what you use for it.21:28
aveigaijw, carlp: The instances where it wouldn't don't make sense, because you'd have a MAC collision anyway21:28
carlpijw: ah, missed that. Sorry21:28
ijwTo be fair, we get to tell people what they should do to an extent.  Changing MACs in v4 gets you nowhere, too...21:29
*** jjmb has joined #openstack-meeting-alt21:29
carlpaveiga: MAC addresses should be unique in openstack, too much depends on that for them not to be. Especially on the same network segment.21:29
aveigacarlp: agreed, hence lla shuld be EUI-64 derived in all cases21:30
ijwIn this instance, we're adding the additional requirement that no-one tries to be smart about assigning ipv6 LLs, but that's fine21:30
sc68calI'm a bit short on action items, at least for community work21:31
mesterySo, it's 30 minutes in, just checking if people have settle on either some bugs or BPs they'd like to focus on.21:31
mesteryIcehouse-1 is in 2 weeks.21:31
sc68calaveiga and myself are working mostly on the slaac + provider networking, since that's our setup internally21:32
aveigaI'm also working to get some Third OParty Testing cycles spun up for this too21:32
aveigabut I can only really test the l2-provider model right now21:32
mesteryBoth of those are solid. I think it makes sense to track that work as action items for next week.21:33
mesteryIs anyone else willing to sign up for any of hte other bugs discussed here?21:33
shshang@aveiga: Is your setup completely using external router to send RA, right?21:33
aveigashshang: Yes.21:33
*** pcm_ has quit IRC21:34
ekarlsoyo gang21:34
ekarlsoquick question, what's the plan to introduce ipv6 in neutrpn ?21:34
haleybmestery: is there a list of bugs?  i missed the first 10 minutes21:34
sc68calekarlso: you'll have to read through the logs when we're done21:34
*** alazarev has joined #openstack-meeting-alt21:34
mesterysc68cal may have that list21:34
sc68calit should appear in the log when we're done, but if not I'll e-mail the mailing list for good measure21:35
haleybok, i only know of the two he has21:35
aveigaI actually have about 3 more to post.  I'm a bit behind on my documentation21:35
*** NikitaKonovalov has quit IRC21:35
ijwsc68cal: so, just to confirm what your SLAAC stuff will leave us with - when you're done with your stuff, we're expecting VMs that assign themselves a global address appropriate to the subnet, right?21:35
jjmbthis is john brzozowski (jjmb), i run the ipv6 program at comcast - sean asked that introduce myself21:36
aveigaijw: We're expecting SLAAC to work normally as it would in any non-virtualized environment21:36
aveigaagain, this is for l2-provider models only21:36
sc68calijw: Yes. Although the subnet is not inside openstack at this point21:36
aveigawe should also get a blueprint to gether to bring DHCPv6 into the fold21:36
sc68calaveiga: I think the dnsmasq bp does cover that, though it could probably use better wording21:37
aveigathen we should take that discussion in general to the mailing list and refine it21:37
sc68calok21:38
aveigamore needs to happen than just dnsmasq to get that bit working21:38
sc68cal#action sc68cal discuss DHCPv6 support on the mailing list21:38
shshangCan we discuss the big picture first, before we talk about bug fix?21:39
aveigaplease21:39
shshangI am curious to see what approach we will take to tackle the IPv6 + Neutron issue21:40
shshangsomething like the priority and dependancies21:40
aveigaone of the key things required to get neutron to be ipv6-capable is for neutron to be able to derive, assign or retrieve the VM's IP address21:41
aveigathat might be a good place to start21:41
shshangagreed21:41
shshangthat is our goal21:41
shshangor one of our goals21:41
sc68calaveiga: can I assign you a task of documenting our usecase?21:43
aveigasure, but let's link it to mailing list discussions21:43
aveigaI don't claim to be omniscient21:44
sc68calok21:44
*** yogesh has quit IRC21:44
sc68cal#action aveiga document our immediate needs from Neutron, and open discussion on the mailing list21:44
*** yogesh has joined #openstack-meeting-alt21:45
shshangHow can we translate that to the blueprint?21:45
jjmbdo we want to include any phasing or future requirements?21:45
jjmbie a phased approach21:45
jjmbor is this putting the cart before the horse?21:45
shshang@jjmb, agreed21:45
aveigait might be better to gather them all and then prioritize them21:45
aveigaperhaps based on the amount of responses from the mailing list21:45
sc68cal#idea gather up requirements for immediate term, and log term21:46
jjmbthe immediate phase I would obviously need to be executed upon first...21:46
jjmbhowever it might be useful for all to see and comment on what happens in future releases.  aveiga/sc68cal?21:47
ijwAs a basic sequence of events, it seems it's basic firewalling and L2 stuff to start (so that SLAAC works at least on provider networks) then we'll move on to RAs and then DHCP, I would think.  Longer term and more frightening is what routers actually *do* for v6, because it's not what they do for v4.  And a problem for both v6 and v4 is how multiple subnets on a network are supposed to be treated, I think - mestery, unless you know mo21:47
aveigaIs there anyone interested in doing a neutron-wide code review looking for instances of addressing that are either cast as ints or pulled from IPv4-only calls?21:47
*** rongze has joined #openstack-meeting-alt21:47
sc68calijw: well put21:47
shshang@ijw. That sounds like a plan already21:48
sc68calaveiga: most of the calls i've seen is through netaddr21:48
aveigaijw: you bring up a good point, since multiple networks on the same subnet isn't a problem in IPv6...21:48
sc68calwhich handles ip stuff - most is stored internally in the DB I believe for addresses21:48
ijwaveiga: 'interested' would be a strong statement, but I think it needs doing.  We need to check the remaining bits of nova that neutron relies on too - and while we're at it can we please confirm that multiple subnets do work, and maybe even feed what we discover about operation to the docs people, because I don't think this is as well described as it should be21:48
sc68cal*stored as strings21:49
*** yogesh has quit IRC21:49
aveigaijw: Yes, and I plan on filing a bug soon about this.  It turns out that if you even add an ipv6 subnet to a network with an IPv4 subnet, it disables the whole network21:49
shshangaveiga, you are talking about the external network side?21:50
aveigaNot sure about everyone else, but I don't want dual stack to require separate interfaces21:50
aveigashshang: yes21:50
*** jjmb has quit IRC21:50
ijwYeah.  Try not adding a subnet.  Havana's slightly different in that you get an error, but in Grizzly you got no interfae21:50
shshangI have solution for you21:50
ijwaveiga: 4, 46 and 6 should all work21:50
shshangaveiga, we already made dualstack working on external network side21:50
aveigashshang: We did too, by not putting in a subnet at all21:50
shshangv4, v6 on the same interface21:50
aveigawe can compare notes outside this meeting though, as I don't want to take up time21:51
ijwshshang: where's the review?21:51
shshangwe didn't publish the code yet, but we wrote a white paper21:51
ijwRight.  Code review.  Volunteer?21:51
ijwo/ (reluctantly, cos someone has to)21:51
shshangaveiga, ijw, if you are interested, we can have a call to review it together21:52
ijw shshang: bung it in gerrit as a WIP and mail the link around, we can comment on it there21:52
aveigaactually, I'd prefer documentation and an email thread on the list21:52
*** rongze has quit IRC21:52
sc68calijw: +121:52
sc68calshshang: can I put you down for an action on that item?21:52
shshangijw, that is a good idea, will do21:52
shshangsc68cal, you mean, load code to github?21:53
sc68cal#action shshang post code review & link on mailing list21:53
shshangsure, I will do21:53
sc68calshshang: put it on gerrit and mark it as WIP21:53
shshangaveiga, ijw, since this is my first time to post code, may need your help a little bit to make sure I did it right21:54
shshangthanks in advance21:54
aveigaI can help, but it will be my first time too shortly21:54
ijwMight have more volunteers for the code review, if we can work out how best to file comments21:55
ijwAlso a checklist of issues to look for21:55
aveigaI think I can finnagle jjmb into helping with that list21:55
aveigasc68cal: put me down for coming up with a list of gotchas that block IPv621:56
sc68calok21:56
aveigaI can work with soem folks internally that already did this on other projects21:56
shshangsc68cal, please put me down for gap list too21:56
sc68calok, not sure if I can link multiple people to it21:56
sc68calshould probably be shshang aveiga and ijw21:57
ijwsc68cal: can you start a thread on the ML about what to look for?  And is there some way we can comment up the code on github or something similar?21:57
sc68calijw: good question - probably the best thing to do is take notes then share on the mailing list21:57
aveigacoming up on the end of the hour21:58
sc68cal#action aveiga ijw shshang start code review looking for IPv4-isms21:58
sc68calThanks everyone for coming, I'm going to get better at working with meetbot as we go along21:59
sc68calI promise :)21:59
*** eankutse has quit IRC21:59
shshangthanks!21:59
sc68calNext week is pretty close to a holiday in the US, so we may reconvene the week after21:59
sc68cal#endmeeting21:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Thu Nov 21 21:59:58 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-11-21-21.01.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-11-21-21.01.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-11-21-21.01.log.html22:00
*** shshang has quit IRC22:00
aveigathanks everyone22:00
ijwsc68cal: only a holiday for some of us, so make sure you mail out if you cancel22:00
sc68calijw: will do22:01
*** Dane has quit IRC22:01
*** djoreilly has quit IRC22:01
*** yogesh has joined #openstack-meeting-alt22:02
*** julim has quit IRC22:03
*** yamahata_ has joined #openstack-meeting-alt22:10
*** radix_ has joined #openstack-meeting-alt22:10
*** s3wong has quit IRC22:16
*** pdmars has quit IRC22:17
*** devkulkarni has quit IRC22:22
*** kgriffs is now known as kgriffs_afk22:23
*** BrianB_ has quit IRC22:26
*** lblanchard has quit IRC22:29
*** eankutse has joined #openstack-meeting-alt22:30
*** aveiga has quit IRC22:31
*** eggs-lunch is now known as eggmaster22:35
*** markmcclain has quit IRC22:40
*** radix_ has quit IRC22:42
*** tedross has quit IRC22:44
*** ashaikh has quit IRC22:45
*** rongze has joined #openstack-meeting-alt22:48
*** rongze has quit IRC22:54
*** jprovazn has quit IRC22:57
*** AlanClark has quit IRC22:58
*** amytron has quit IRC23:02
*** eharney has quit IRC23:02
*** kevinconway has quit IRC23:02
*** banix has quit IRC23:05
*** venkatesh has joined #openstack-meeting-alt23:10
*** alazarev has quit IRC23:13
*** alazarev has joined #openstack-meeting-alt23:16
*** devkulkarni has joined #openstack-meeting-alt23:17
*** yogesh has quit IRC23:17
*** yogesh has joined #openstack-meeting-alt23:18
*** kgriffs_afk is now known as kgriffs23:19
*** eankutse has quit IRC23:21
*** yogesh has quit IRC23:22
*** eankutse has joined #openstack-meeting-alt23:23
*** yamahata_ has quit IRC23:25
*** demorris has quit IRC23:25
*** jmontemayor has quit IRC23:30
*** venkatesh has quit IRC23:42
*** [a]mcrn is now known as amcrn23:44
*** sarob has quit IRC23:44
*** sarob has joined #openstack-meeting-alt23:45
*** sarob has quit IRC23:49
*** rongze has joined #openstack-meeting-alt23:50
*** rnirmal has quit IRC23:54
*** rongze has quit IRC23:56
*** amytron has joined #openstack-meeting-alt23:57
*** yogesh has joined #openstack-meeting-alt23:57

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