Thursday, 2013-12-19

*** HenryG has quit IRC00:05
*** NehaV has joined #openstack-meeting-alt00:07
*** IlyaE has joined #openstack-meeting-alt00:12
*** brents has quit IRC00:13
*** banix has joined #openstack-meeting-alt00:13
*** vipul is now known as vipul-away00:14
*** ativelkov has joined #openstack-meeting-alt00:18
*** brents has joined #openstack-meeting-alt00:21
*** NehaV has quit IRC00:23
*** NehaV has joined #openstack-meeting-alt00:27
*** ativelkov has quit IRC00:27
*** NehaV has quit IRC00:32
*** boris-42 has quit IRC00:35
*** gokrokve has joined #openstack-meeting-alt00:36
*** gokrokve has quit IRC00:40
*** gokrokve has joined #openstack-meeting-alt00:41
*** jamiec has joined #openstack-meeting-alt00:42
*** ryu25 has joined #openstack-meeting-alt00:42
*** gokrokve_ has joined #openstack-meeting-alt00:42
*** jamiec has quit IRC00:43
*** Leo_ has quit IRC00:45
*** gokrokve has quit IRC00:46
*** esker has joined #openstack-meeting-alt00:49
*** ativelkov has joined #openstack-meeting-alt00:51
*** demorris has joined #openstack-meeting-alt00:51
*** ashaikh has quit IRC00:55
*** ativelkov has quit IRC00:56
*** safchain has joined #openstack-meeting-alt00:59
*** safchain has quit IRC01:00
*** brents has quit IRC01:01
*** IlyaE has quit IRC01:15
*** MarkAtwood has quit IRC01:15
*** ativelkov has joined #openstack-meeting-alt01:16
*** safchain has joined #openstack-meeting-alt01:16
*** rwsu has quit IRC01:18
*** safchain has quit IRC01:19
*** sacharya has quit IRC01:19
*** bdpayne has quit IRC01:19
*** rwsu has joined #openstack-meeting-alt01:19
*** ativelkov has quit IRC01:23
*** mozawa has joined #openstack-meeting-alt01:31
*** nosnos has joined #openstack-meeting-alt01:38
*** yamahata has joined #openstack-meeting-alt01:39
*** ativelkov has joined #openstack-meeting-alt01:47
*** julim has quit IRC01:49
*** harlowja has quit IRC01:51
*** demorris has quit IRC01:52
*** jcooley_ has quit IRC01:55
*** ativelkov has quit IRC01:55
*** markvoelker1 has joined #openstack-meeting-alt01:56
*** harlowja has joined #openstack-meeting-alt02:03
*** colinmcnamara has quit IRC02:05
*** arnaud__ has quit IRC02:10
*** arnaud has quit IRC02:10
*** rongze has joined #openstack-meeting-alt02:12
*** ativelkov has joined #openstack-meeting-alt02:17
*** ativelkov has quit IRC02:22
*** zane has joined #openstack-meeting-alt02:23
*** jcooley_ has joined #openstack-meeting-alt02:27
*** nosnos_ has joined #openstack-meeting-alt02:30
*** vkmc has quit IRC02:32
*** nosnos has quit IRC02:33
*** jcooley_ has quit IRC02:37
*** yogesh has quit IRC02:43
*** nati_ueno has quit IRC02:48
*** ativelkov has joined #openstack-meeting-alt02:50
*** ativelkov has quit IRC02:56
*** balajiiyer has joined #openstack-meeting-alt03:08
*** coolsvap has joined #openstack-meeting-alt03:14
*** ativelkov has joined #openstack-meeting-alt03:20
*** dougshelley66 has quit IRC03:22
*** ativelkov has quit IRC03:25
*** zane has quit IRC03:25
*** jergerber has joined #openstack-meeting-alt03:27
*** jergerber has quit IRC03:30
*** nati_ueno has joined #openstack-meeting-alt03:35
*** jergerber has joined #openstack-meeting-alt03:37
*** ativelkov has joined #openstack-meeting-alt03:50
*** ashaikh has joined #openstack-meeting-alt03:52
*** yogesh has joined #openstack-meeting-alt03:54
*** julim has joined #openstack-meeting-alt03:54
*** ativelkov has quit IRC03:55
*** julim has quit IRC03:57
*** yogesh has quit IRC03:58
*** vipul-away is now known as vipul04:01
*** vipul has joined #openstack-meeting-alt04:01
*** nati_ueno has quit IRC04:01
*** balajiiyer has left #openstack-meeting-alt04:05
*** yamahata has quit IRC04:11
*** yamahata has joined #openstack-meeting-alt04:11
*** yamahata__ has quit IRC04:12
*** yamahata__ has joined #openstack-meeting-alt04:13
*** yamahata__ has quit IRC04:13
*** yamahata_ has joined #openstack-meeting-alt04:13
*** balajiiyer1 has joined #openstack-meeting-alt04:14
*** betsy has joined #openstack-meeting-alt04:15
*** balajiiyer1 has quit IRC04:18
*** ativelkov has joined #openstack-meeting-alt04:20
*** ativelkov has quit IRC04:24
*** banix has quit IRC04:28
*** gokrokve_ has quit IRC04:28
*** banix has joined #openstack-meeting-alt04:34
*** gokrokve has joined #openstack-meeting-alt04:36
*** banix has quit IRC04:38
*** jcooley_ has joined #openstack-meeting-alt04:39
*** boris-42 has joined #openstack-meeting-alt04:43
*** rongze has quit IRC04:44
*** coolsvap has quit IRC04:45
*** banix has joined #openstack-meeting-alt04:46
*** nati_ueno has joined #openstack-meeting-alt04:46
*** banix has quit IRC04:47
*** ativelkov has joined #openstack-meeting-alt04:48
*** ativelkov has joined #openstack-meeting-alt04:49
*** zane has joined #openstack-meeting-alt04:52
*** akuznetsov has joined #openstack-meeting-alt04:54
*** ativelkov has quit IRC04:59
*** ativelkov has joined #openstack-meeting-alt04:59
*** chandankumar has joined #openstack-meeting-alt05:02
*** ativelkov has quit IRC05:04
*** nosnos_ has quit IRC05:06
*** nosnos has joined #openstack-meeting-alt05:07
*** sarob has joined #openstack-meeting-alt05:17
*** ativelkov has joined #openstack-meeting-alt05:17
*** rongze has joined #openstack-meeting-alt05:18
*** ativelko_ has joined #openstack-meeting-alt05:19
*** ativelkov has quit IRC05:22
*** rongze has quit IRC05:23
*** ativelko_ has quit IRC05:24
*** coolsvap has joined #openstack-meeting-alt05:25
*** coolsvap has quit IRC05:29
*** radix_ has quit IRC05:30
*** harlowja is now known as harlowja_away05:40
*** ativelkov has joined #openstack-meeting-alt05:47
*** ativelko_ has joined #openstack-meeting-alt05:49
*** ativelkov has quit IRC05:49
*** ativelko_ has quit IRC05:54
*** ativelkov has joined #openstack-meeting-alt05:57
*** nadya has joined #openstack-meeting-alt05:57
*** nadya is now known as Guest6233305:57
*** harlowja_away is now known as harlowja05:59
*** jergerber has quit IRC06:02
*** sarob has quit IRC06:02
*** ativelkov has quit IRC06:02
*** sarob has joined #openstack-meeting-alt06:02
*** Guest62333 has quit IRC06:03
*** nati_ueno has quit IRC06:05
*** sarob has quit IRC06:07
*** denis_makogon has joined #openstack-meeting-alt06:08
*** yogesh has joined #openstack-meeting-alt06:09
*** yogesh_ has joined #openstack-meeting-alt06:16
*** yogesh has quit IRC06:16
*** ativelkov has joined #openstack-meeting-alt06:18
*** rongze has joined #openstack-meeting-alt06:20
*** ativelkov has quit IRC06:23
*** yogesh_ has quit IRC06:23
*** rongze has quit IRC06:25
*** yogesh has joined #openstack-meeting-alt06:27
*** rongze has joined #openstack-meeting-alt06:27
*** zz_ajo is now known as ajo06:28
*** rongze has quit IRC06:28
*** ajo is now known as zz_ajo06:29
*** zz_ajo is now known as ajo06:29
*** ajo is now known as zz_ajo06:33
*** dougshelley66 has joined #openstack-meeting-alt06:34
*** nati_ueno has joined #openstack-meeting-alt06:37
*** rongze has joined #openstack-meeting-alt06:37
*** yogesh has quit IRC06:44
*** yogesh_ has joined #openstack-meeting-alt06:44
*** yogesh_ has quit IRC06:46
*** SushilKM has joined #openstack-meeting-alt06:47
*** ativelkov has joined #openstack-meeting-alt06:50
*** ativelkov has quit IRC06:54
*** akuznetsov has quit IRC06:59
*** yogesh has joined #openstack-meeting-alt07:01
*** SushilKM has quit IRC07:02
*** sarob has joined #openstack-meeting-alt07:03
*** sarob has quit IRC07:08
*** ashaikh has quit IRC07:11
*** ativelkov has joined #openstack-meeting-alt07:20
*** yogesh has quit IRC07:21
*** ativelkov has quit IRC07:24
*** zane has quit IRC07:27
*** vipul is now known as vipul-away07:34
*** MarkAtwood has joined #openstack-meeting-alt07:38
*** SushilKM has joined #openstack-meeting-alt07:39
*** natishalom has joined #openstack-meeting-alt07:44
*** boris-42 has quit IRC07:48
*** rongze has quit IRC07:49
*** rongze has joined #openstack-meeting-alt07:49
*** esker has quit IRC07:49
*** ativelkov has joined #openstack-meeting-alt07:50
*** gokrokve has quit IRC07:50
*** nati_ueno has quit IRC07:54
*** esker has joined #openstack-meeting-alt07:54
*** ativelkov has quit IRC07:55
*** yogesh has joined #openstack-meeting-alt07:57
*** SushilKM__ has joined #openstack-meeting-alt08:03
*** SushilKM has quit IRC08:04
*** MarkAtwood has quit IRC08:04
*** sarob has joined #openstack-meeting-alt08:04
*** harlowja is now known as harlowja_away08:04
*** sarob has quit IRC08:09
*** amcrn has quit IRC08:15
*** ativelkov has joined #openstack-meeting-alt08:18
*** jcoufal has joined #openstack-meeting-alt08:19
*** sarob has joined #openstack-meeting-alt08:19
*** akuznetsov has joined #openstack-meeting-alt08:22
*** sarob has quit IRC08:23
*** ativelkov has quit IRC08:25
*** luQAs has joined #openstack-meeting-alt08:27
*** markvoelker1 has quit IRC08:33
*** flaper87|afk is now known as flaper8708:36
*** jtomasek has joined #openstack-meeting-alt08:36
*** jtomasek has quit IRC08:41
*** jtomasek has joined #openstack-meeting-alt08:50
*** ativelkov has joined #openstack-meeting-alt08:50
*** jtomasek has quit IRC08:51
*** jtomasek has joined #openstack-meeting-alt08:51
*** enikanorov has quit IRC08:53
*** jcooley_ has quit IRC08:54
*** ativelkov has quit IRC08:55
*** sarob has joined #openstack-meeting-alt09:03
*** safchain has joined #openstack-meeting-alt09:06
*** jtomasek has quit IRC09:06
*** jtomasek has joined #openstack-meeting-alt09:07
*** sarob has quit IRC09:09
*** jtomasek has quit IRC09:09
*** jtomasek has joined #openstack-meeting-alt09:09
*** jtomasek has quit IRC09:12
*** jtomasek has joined #openstack-meeting-alt09:12
*** katyafervent has quit IRC09:18
*** ativelkov has joined #openstack-meeting-alt09:20
*** ativelko_ has joined #openstack-meeting-alt09:23
*** ativelkov has quit IRC09:25
*** akuznetsov has quit IRC09:26
*** luQAs has quit IRC09:35
*** jcooley_ has joined #openstack-meeting-alt09:38
*** ativelko_ has quit IRC09:39
*** ativelkov has joined #openstack-meeting-alt09:40
*** ativelkov has joined #openstack-meeting-alt09:45
*** ruhe has joined #openstack-meeting-alt09:47
*** natishalom has joined #openstack-meeting-alt09:52
*** ryu25 has quit IRC09:52
*** boris-42 has joined #openstack-meeting-alt09:52
*** jtomasek has quit IRC09:56
*** jtomasek has joined #openstack-meeting-alt09:57
*** ruhe has quit IRC09:58
*** ruhe has joined #openstack-meeting-alt09:58
*** NikitaKonovalov has joined #openstack-meeting-alt09:59
*** ativelkov has joined #openstack-meeting-alt09:59
*** SergeyLukjanov has joined #openstack-meeting-alt10:03
*** mozawa has quit IRC10:03
*** sarob has joined #openstack-meeting-alt10:04
*** luQAs has joined #openstack-meeting-alt10:05
*** enikanorov has joined #openstack-meeting-alt10:08
*** jcooley_ has quit IRC10:09
*** rongze has quit IRC10:11
*** derekh has joined #openstack-meeting-alt10:15
*** ativelkov has quit IRC10:15
*** ativelkov has joined #openstack-meeting-alt10:15
*** jcooley_ has joined #openstack-meeting-alt10:19
*** ativelkov has quit IRC10:19
*** rongze has joined #openstack-meeting-alt10:23
*** ativelkov has joined #openstack-meeting-alt10:23
*** yogesh has quit IRC10:24
*** sarob has quit IRC10:26
*** NikitaKonovalov has quit IRC10:28
*** NikitaKonovalov has joined #openstack-meeting-alt10:29
*** katyafervent has joined #openstack-meeting-alt10:31
*** akuznetsov has joined #openstack-meeting-alt10:32
*** rossella_s has joined #openstack-meeting-alt10:38
*** rsblendido has joined #openstack-meeting-alt10:38
*** denis_makogon has quit IRC10:40
*** denis_makogon has joined #openstack-meeting-alt10:45
*** dteselkin has quit IRC10:47
*** jcooley_ has quit IRC10:49
*** aignatov has joined #openstack-meeting-alt10:51
*** ruhe has quit IRC10:59
*** SushilKM__ has quit IRC10:59
*** nosnos has quit IRC11:00
*** sarob has joined #openstack-meeting-alt11:03
*** ruhe has joined #openstack-meeting-alt11:04
*** rongze has quit IRC11:13
*** yamahata has quit IRC11:28
*** aignatov has quit IRC11:28
*** ruhe has quit IRC11:32
*** jcooley_ has joined #openstack-meeting-alt11:32
*** ruhe has joined #openstack-meeting-alt11:32
*** SushilKM__ has joined #openstack-meeting-alt11:34
*** yogesh has joined #openstack-meeting-alt11:35
*** sarob has quit IRC11:36
*** yogesh has quit IRC11:39
*** aignatov has joined #openstack-meeting-alt11:47
*** sarob has joined #openstack-meeting-alt12:03
*** jcooley_ has quit IRC12:04
*** rongze has joined #openstack-meeting-alt12:04
*** mozawa has joined #openstack-meeting-alt12:04
*** jtomasek has quit IRC12:05
*** ruhe is now known as ruhe_12:05
*** jtomasek has joined #openstack-meeting-alt12:06
*** ruhe_ has quit IRC12:06
*** vkmc has joined #openstack-meeting-alt12:07
*** vkmc has joined #openstack-meeting-alt12:07
*** yamahata has joined #openstack-meeting-alt12:14
*** ativelkov has quit IRC12:15
*** aignatov has quit IRC12:16
*** aignatov has joined #openstack-meeting-alt12:20
*** ruhe has joined #openstack-meeting-alt12:20
*** rongze_ has joined #openstack-meeting-alt12:24
*** natishalom has joined #openstack-meeting-alt12:24
*** natishalom has quit IRC12:24
*** NikitaKonovalov has quit IRC12:24
*** rongze has quit IRC12:28
*** luQAs has quit IRC12:35
*** sarob has quit IRC12:35
*** NehaV has joined #openstack-meeting-alt12:36
*** BrianB_ has quit IRC12:38
*** ativelkov has joined #openstack-meeting-alt12:44
*** abramley has quit IRC12:46
*** jdob has joined #openstack-meeting-alt12:49
*** ativelkov has quit IRC12:50
*** SushilKM__ has quit IRC12:51
*** akuznetsov has quit IRC12:53
*** jcooley_ has joined #openstack-meeting-alt12:57
*** ativelkov has joined #openstack-meeting-alt12:57
*** HenryG has joined #openstack-meeting-alt13:00
*** sarob has joined #openstack-meeting-alt13:03
*** pdmars has joined #openstack-meeting-alt13:03
*** eankutse has joined #openstack-meeting-alt13:07
*** NikitaKonovalov has joined #openstack-meeting-alt13:07
*** eankutse has quit IRC13:07
*** eankutse has joined #openstack-meeting-alt13:08
*** ativelkov has quit IRC13:10
*** ativelkov has joined #openstack-meeting-alt13:10
*** esker has quit IRC13:13
*** rsblendido has quit IRC13:14
*** rossella_s has quit IRC13:14
*** ativelkov has quit IRC13:14
*** pdmars has quit IRC13:18
*** ativelkov has joined #openstack-meeting-alt13:25
*** jcooley_ has quit IRC13:27
*** boris-42 has quit IRC13:28
*** colinmcnamara has joined #openstack-meeting-alt13:28
*** heyongli has joined #openstack-meeting-alt13:31
*** colinmcnamara has quit IRC13:32
*** ativelkov has quit IRC13:33
*** SushilKM__ has joined #openstack-meeting-alt13:36
*** sarob has quit IRC13:36
*** rossella_s has joined #openstack-meeting-alt13:38
*** rsblendido has joined #openstack-meeting-alt13:38
*** ativelko_ has joined #openstack-meeting-alt13:40
*** ativelko_ has joined #openstack-meeting-alt13:41
*** abramley has joined #openstack-meeting-alt13:42
*** pdmars has joined #openstack-meeting-alt13:44
*** chandankumar_ has joined #openstack-meeting-alt13:44
*** ativelko_ has quit IRC13:44
*** chandankumar_ has quit IRC13:44
*** akuznetsov has joined #openstack-meeting-alt13:47
*** bugsduggan has joined #openstack-meeting-alt13:49
*** dprince has joined #openstack-meeting-alt13:50
*** heyongli has quit IRC13:54
*** matty_dubs|gone has left #openstack-meeting-alt13:57
*** markwash has joined #openstack-meeting-alt13:58
*** akuznetsov has quit IRC13:58
*** yamahata has quit IRC13:58
*** yamahata has joined #openstack-meeting-alt13:59
*** derekh has quit IRC14:00
markwashgood morning/afternoon/evening14:00
markwash#startmeeting glance14:00
openstackmarkwash: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.14:00
markwashoh no!14:01
markwashendmeeting14:01
markwash#endmeeting14:01
*** openstack changes topic to "Initial discussion of a possible solution to several issues raised during the Blueprint Hangout (Meeting topic: Designate)"14:01
openstackMeeting ended Thu Dec 19 14:01:08 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
*** zhiyan has joined #openstack-meeting-alt14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-12-18-18.13.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-12-18-18.13.txt14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2013/trove.2013-12-18-18.13.log.html14:01
markwash#startmeeting glance14:01
openstackMeeting started Thu Dec 19 14:01:21 2013 UTC and is due to finish in 60 minutes.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: glance)"14:01
openstackThe meeting name has been set to 'glance'14:01
zhiyanhi14:01
flaper87o/14:01
flaper87o/14:01
markwash|o/14:02
zhiyanflaper87: \o14:02
zhiyanmarkwash: o/14:02
flaper87zhiyan: yo14:02
markwashjust the three of us? (we can make it if we try)14:02
flaper87markwash: lets do it14:03
flaper87I've a couple of things I'd like to get your thoughts on14:03
flaper87:D14:03
*** sarob has joined #openstack-meeting-alt14:03
markwashokay14:03
rosmaitao/14:04
flaper87rosmaita: good morning14:04
zhiyanmarkwash: if we have time, i have a little question14:04
markwashzhiyan: it looks like we might have lots of time14:04
rosmaitaflaper87: good afternoon!14:04
markwashtodays agenda: https://etherpad.openstack.org/p/glance-team-meeting-agenda14:04
zhiyanmarkwash: ok. actually it's a question for my location-status bp implementation. i believe we can talk it offline also.14:05
markwashso first item, we won't have a meeting next week14:06
zhiyanrosmaita: hello14:06
markwashdo folks here want to meet on Jan 2nd? I think it probably works for me14:06
*** chandankumar has quit IRC14:06
*** luQAs has joined #openstack-meeting-alt14:07
flaper87markwash: I'd say 9th14:07
rosmaitazhiyan: howdy14:07
rosmaitai will be offline jan 214:07
flaper87it'll probably work for me too but I'm not sure yet14:07
markwashokay, seems fine then, the 9th14:07
flaper87kk14:07
*** sarob has quit IRC14:08
markwashNext meeting will be at 2000 UTC on Jan 914:08
markwash#topic reviews14:08
*** openstack changes topic to "reviews (Meeting topic: glance)"14:08
zhiyanmarkwash: cool14:08
markwashJust briefly wanted to mention that we still have a fair amount of work to do on our review queue14:08
flaper87#info Next meeting will be at 2000 UTC on Jan 914:09
*** demorris has joined #openstack-meeting-alt14:09
markwashand I'm going to be free from the bonds of the day job for the next chunk of time, so I'll be putting in a near daily effort on it despite the holidays14:09
markwashso if you have a bit of time, be sure to check the queue for things that just need one more +214:09
markwashflaper87: want to share your thoughts next?14:11
flaper87markwash: yup14:11
*** lblanchard has joined #openstack-meeting-alt14:11
markwash#topic flaper87's thoughts14:11
*** openstack changes topic to "flaper87's thoughts (Meeting topic: glance)"14:11
markwash:-)14:11
flaper87LOL14:11
flaper87the first thing I'd like to get your thoughts on is this review: https://review.openstack.org/#/c/59150/14:11
flaper87I really don't think we should be enabling all the stores by default, instead that should be an explicit action14:12
*** mclaren has joined #openstack-meeting-alt14:12
flaper87Most of the stores - besides http + file - need lot of configs that are not there by default14:12
zhiyanflaper87: agreed14:12
flaper87and will confuse users when glance starts14:12
flaper87now, the tests there fail because we need this patch in: https://review.openstack.org/#/c/59177/14:13
zhiyanflaper87: but i just meaning we need change others to make it work well14:13
flaper87which is a devstack patch14:13
flaper87I talked with sdague today and I'd also need your thoughts there as a consensus of this change14:14
flaper87zhiyan: not sure what you mean14:14
markwashflaper87: okay, I've starred the reviews14:14
markwashIn general I think this change in default makes sense but I'm still processing the concerns I see raised there14:14
zhiyanflaper87: hum..i'm trying explaining my comments in https://review.openstack.org/#/c/59150/1/glance/store/__init__.py14:14
zhiyanespecially last one14:15
flaper87markwash: agreed. I put some thoughts there14:15
flaper87so, distros don't override config files - and if there's a distro doing that, it's not a good one - which means that users will notice the change14:16
flaper87and if they're upgrading from H to I they'll have to look into those files14:16
flaper87that said, I doubt there's an environment with all those stores enabled14:16
flaper87I really doubt it14:16
flaper87and if there's one, I want to know why :D14:16
flaper87(that was a joke(14:17
flaper87)14:17
markwashzhiyan: I think you're especially asking for some better error handling when an unsupported store is accessed?14:17
icchao/14:17
flaper87this change will bring benefits to glance and to the users of it14:17
flaper87I agree there should be a better error handling14:17
flaper87but I don't think that's the solution for this issue14:17
flaper87stores *have* to yell when they're not configured correctly14:17
flaper87and that's what they do now14:17
zhiyanmarkwash: part of. you when user finish upgrade, then error is not make sense.14:18
flaper87we could improve the messages being printed14:18
flaper87but still, I think it's not worth it to enabled them all14:18
markwashflaper87: I was imagining the error handling was about reporting errors *with* your patch, not instead of it14:18
*** jcooley_ has joined #openstack-meeting-alt14:18
markwashbut still not sure14:18
markwashiccha: o/14:18
flaper87markwash: yeah, I think I misread zhiyan comment maybe14:19
flaper87but anyway, I think both should happen14:19
icchahey markwash :)14:19
flaper87iccha: heyyyy14:19
flaper87:D14:19
icchahey flaper8714:19
markwashI've got those reviews starred now which means I think I can effectivlye prioritize following up14:19
flaper87awesome I think at least 2 other cores should chime in in both patches14:20
flaper87to show consensus14:20
flaper87I explicitly asked not to approve the devstack patch until we agree that's the way to go14:20
markwashokay, flaper87 other thoughts?14:20
flaper87yup14:20
flaper87just one more14:20
*** ativelko_ has joined #openstack-meeting-alt14:20
flaper87I've been thinking that other projects (nova, glanceclient (?) ) could benefit from the glance.stores code. The API there seems pretty stable. I would like to know what you guys think about pulling that could out of glance into its own lib14:21
flaper87we could move it into oslo14:21
flaper87and then use it somewhere else14:22
flaper87I think it's not that tight to glance14:22
flaper87and it exposes useful methods to interact with stores14:22
flaper87either they are remote or local14:22
icchaflaper87: just curious what other components talk directly to the stores?14:22
markwashhmm interesting idea14:23
flaper87none yet but, if we want to improve nova and let it interact with the store we could use it14:23
flaper87zhiyan: and myself are working on zero-copy for nova14:23
flaper87one of the things we'd like add there is multi-locations14:23
markwashmaking it easier for nova and cinder to talk direclty to stores would be nice14:23
flaper87and it'd be cool to let nova access the remote location14:24
markwashthough I was wondering if code like that might better live in someplace accessible through glanceclient14:24
icchaand making it so all projects talk the same way would be good for the stores14:24
icchawe could reduce technical debt14:24
zhiyanflaper87: probably we need rethink a little for store's interface.14:24
flaper87I thought about a library because I think it could be useful for other scenarios outside openstack14:24
*** natishalom has joined #openstack-meeting-alt14:25
zhiyanand btw, i think this is a little related with John's bp14:25
flaper87I first thought about pulling it into glanceclient then I thought about having a glance.stores lib14:25
*** natishalom has joined #openstack-meeting-alt14:25
*** natishalom has quit IRC14:25
zhiyanstore plugin (or something like that)14:25
markwashzhiyan: ++14:25
flaper87and my last thought was moving it into oslo first14:25
flaper87zhiyan: yeah14:25
flaper87that most likely will need to happen14:25
flaper87but before getting there, I wanted to know your thoughts about that14:25
markwashI think a stores lib could work nicely. . and it wouldn't prevent us from reusing logic through glanceclient14:26
zhiyani'm thinking can we merge those two ideas to one?14:26
flaper87markwash: exactly14:26
flaper87zhiyan: yup, all that will happen as part of the lib creation14:26
markwashthere's some logic zhiyan has been working on that is somewhat related, essentially applying selection strategies for dealing with multiple locations. . I guess that would *not* be in the stores lib but would be reused through the glanceclient. . do you agree?14:26
icchais there a patch?14:27
*** sergmelikyan has quit IRC14:27
zhiyanmarkwash:  agree14:27
flaper87yeah14:27
icchacurious why client needs store logic. sorry been lil outta sync14:27
zhiyanjust is what i want to say14:27
*** esker has joined #openstack-meeting-alt14:27
markwashiccha: the idea is for any client to be able to talk directly to the store14:27
zhiyanglance client lib can also include api discovery part. iiuc14:28
markwashnot just nova14:28
zhiyaniccha: https://blueprints.launchpad.net/glance/+spec/image-location-selection-strategy14:28
icchainteresting, then the client lib can be used in any project14:28
icchathanks zhiyan14:28
markwashzhiyan: sorry I have not given you any reviews yet!14:28
zhiyaniccha: :) happy can get your comments btw14:29
zhiyanmarkwash: hehe14:29
flaper87Agreed14:29
zhiyanmarkwash: i really hope tbh14:29
flaper87also, location selection should also be done based on the glanceclient location14:29
rosmaitai guess this would force us to improve credentials handling for the stores14:29
flaper87like getting the best / nearest remote location to the client14:29
flaper87etc14:30
flaper87rosmaita: yes and no14:30
flaper87so, the stores currently don't store the location14:30
flaper87we do it in glance14:30
*** julim has joined #openstack-meeting-alt14:30
*** markmcclain has quit IRC14:30
icchajust one point to keep in mind, when we start encouraging other projects like nova talking directly to stores, is that the number of compute nodes >>> glance nodes14:30
flaper87which means we need to improve the way we're keeping it in glance. (I may be saying something stupid here)14:31
markwashflaper87: how should we proceed with this idea? are you going to work on it? what kind of spec would you want to see14:31
flaper87rosmaita: I haven't followed the credentials work very closely14:31
markwashflaper87: I think that's basically correct, depending on how the api for a storage lib is defined14:31
rosmaitaflaper87: not at all, the problem I see is glance can tell you where something is, but you need to have your own credentials to actually get it14:31
flaper87markwash: The first thing we need to do is choose whether to have glance/stores or oslo.stores14:31
flaper87I vote for the later14:31
zhiyanmarkwash: agree14:31
flaper87then create a bp for oslo and I'll pull it out14:31
rosmaitaso if you use a glance-owned container for images, then there's a credentials problem14:32
mclarenrosmaita: agreed, not sure we want to spread the swift backend creds more than we need to14:32
markwashhmm, I actually prefer the former. . this seems like a case where we have an established supported api already, or nearly14:32
rosmaitamclaren: +1K14:32
mclarenlol14:32
markwashno need to iterate on it in the copy-paste fashion14:32
zhiyanflaper87: =1 to markwash's14:32
zhiyan+114:32
flaper87markwash: but we could aim to have an oslo.store right away14:33
markwashrosmaita: I think what you're saying is "the stores lib would not be useful until we fix the creds issue"14:33
icchajust ruined mclaren and rosmaita 's slepe for next few days14:33
flaper87just because we have an established api14:33
flaper87instead of entering into oslo-incubator14:33
markwashrosmaita: not "the stores lib will make the creds issue worse"14:33
flaper87I guess we could discuss that in the m-l14:33
rosmaitamarkwash: exactly, thank you14:33
mclaren(I don't want to highjack this but multi-tenant would help with direct access...)14:33
rosmaitai think this could be an opportunity to get keystone to make some improvements14:33
rosmaitamclaren: i'm not sold on multi-tenant14:34
flaper87ok, that's it from me14:34
markwashflaper87: perhaps, I guess ml is the best place to figure that out. . seems like it might be something that we could keep under the images program though14:34
markwashflaper87: so yeah if you want to bring that up on the ML that would be great14:34
markwashokay, moving on!14:34
flaper87rosmaita: mclaren I agree with you14:34
flaper87markwash: I will14:34
flaper87thank you guys14:34
markwashwe've been going in a slightly roundabout fashion today agenda-wise14:34
*** balajiiyer has joined #openstack-meeting-alt14:35
markwashzhiyan: did you have an item for us before we try to dive in on the domain model?14:35
markwash(not sure we have all the folks that were intended for that conversation14:36
markwash)14:36
icchayeah14:36
zhiyanmarkwash: can we talk this part off line? thanks14:36
icchalot of ppl seem missin14:36
markwashzhiyan: sure, that's fine14:36
zhiyanmarkwash: cool. (will ping you)14:36
markwashokay, then I'd like to at least visit the blueprint process notes14:37
markwash#topic blueprint process14:37
*** openstack changes topic to "blueprint process (Meeting topic: glance)"14:37
icchahttps://etherpad.openstack.org/p/glance-blueprint-process14:37
icchaso i have been doing some research on blueprint process for openstack and what other projects follow14:37
icchanova has a really interesting process : they have a separate team called the drivers14:38
icchaevery person who submits a blueprint is responsible for assigning to deliver it by a given milestone and a condition stating this blueprint is done when14:39
*** zane has joined #openstack-meeting-alt14:39
icchaand a detailed enough description14:39
icchathis is then reviewed by team of drivers14:39
*** banix has joined #openstack-meeting-alt14:39
markwashso drivers are like core except for blueprint review?14:39
icchaand a blueprint is approved only when one or more driver supports the bp14:39
icchayes markwash14:40
*** rraja has joined #openstack-meeting-alt14:40
zhiyaniccha: can you tell me when they discuss that? and where?14:40
icchaalso the importance of the blueprint is decided by how many core members has volunteered to be revieweing that feature14:41
zhiyanML or irc weekly-meeting14:41
markwashit seemed like they also have some specific rules about what must be provided and guidelines for how blueprints transition through their state-flow14:41
icchahttp://lists.openstack.org/pipermail/openstack-dev/2013-October/017290.html14:41
icchasome of these discussions happened at the summit i believe14:42
icchazhiyan: the wiki page on blueprints has the nova process too14:42
zhiyaniccha: indeed, thanks.14:43
icchahttps://wiki.openstack.org/wiki/Blueprints14:43
markwashI guess what I'd really love to do with this is to use it to guide an automated review process as well as using the underlying rules to power a dashboard14:44
icchaso if we feel we could pick parts of process or customize it for us14:44
icchamarkwash: +114:44
markwasheven if its just for me, that would be a huge help, but I also like the idea of figuring out if we need something like a drivers team14:44
markwashits possible core == drivers for us14:44
*** boris-42 has joined #openstack-meeting-alt14:45
markwashor maybe we can have another group of drivers, and have people who can review blueprints be cores + drivers14:45
icchai would like the possibility of non core members also to have a change to be part of drivers14:45
markwashyeah14:45
markwashand also perhaps there are some cores that don't want to mess with bp review14:45
icchaif they are going to consistent and have valuable input from glance as a paroduct side14:45
markwashso the action item I really want to take from this is for someone to start playing around with automating this workflow, but I'm not sure we're ready exactly14:46
markwashmaybe the right action item is an ML proposal for exactly what our workflow would be?14:46
rosmaitamarkwash: yes, we need a workflow before we try to automate it!14:47
markwashnovas + whatever tweaks I guess14:47
markwashokay, I'll take that on, bp triaging is something I really want us to step up14:47
ameademaybe like theirs but a little lighter weight :)14:48
rosmaitaalso, +1 to the non-core BP driver idea14:48
markwashrosmaita: ;-)14:48
iccha:)14:48
markwash#action markwash propose bp workflow to ML after more careful review of nova's14:48
*** openstack has joined #openstack-meeting-alt14:49
-card.freenode.net- [freenode-info] channel flooding and no channel staff around to help? Please check with freenode support: http://freenode.net/faq.shtml#gettinghelp14:49
*** ChanServ sets mode: +o openstack14:49
markwashany other notes for bp processes at this point? shall we openly discuss?14:49
markwash#topic open discussion14:50
mclareno/14:50
markwashmclaren: ahoy!14:50
mclaren:-)14:50
mclarenI've been trying to help with reviewing this: https://review.openstack.org/#/c/34801/14:51
mclaren(the change to obfuscate swift creds)14:51
mclarenJust wanted to alert folks that there's a new swift location format proposed14:51
*** jcooley_ has quit IRC14:52
mclarenin part the motivation here is as follows:14:52
mclarenThe arguments for creating a swift client are richer than can be specified in a location. We make up for this by having additional swift parameters in the glance-api.conf. If we wish to support allowing an operator to migrate from one (full?) swift backend to a new swift backend some of those things need to be on a per-swift store basis (eg region/insecure), which is not currently the case.14:52
mclarenso the patch is about creds but has morphed into something bigger...14:52
*** gokrokve has joined #openstack-meeting-alt14:52
mclarenI'm interested if folks are ok with this or if its too avant garde or something :-)14:53
markwashits an idea that has some appeal14:53
markwashIt makes me worry a bit about expecting clients to know the creds as well but14:53
markwashs/creds/arguments/14:53
mclarenok, really just wanted to bring attention to it - thanks14:54
flaper87mclaren: thanks for the work there14:54
*** yportnov_ has joined #openstack-meeting-alt14:54
markwash+114:55
ameadeso there has been a whole lot of discussion around glance becoming a general catalog service for openstack14:55
markwashmclaren: do you think there is any safe way to share public information about what "store1" means?14:55
mclarensure. If we do go down this road we'd probably have to clean up how we do the configuration14:55
ameadewe had a meeting on tuesday and a lot was discussed14:55
*** tims has joined #openstack-meeting-alt14:55
flwangam I missing anything?14:55
*** csaba|afk is now known as csaba14:56
mclarenhmm, what's the use case there?14:56
markwashmclaren: client direct downloads14:56
zhiyanameade: seems they has not send the summary mail out right? or i miss that ..14:56
ameadesome emails are going to be sent out, bps created, and a number of extra people want to come to the mini-summit14:56
ameadezhiyan: i have not seen anything unfortunately14:56
zhiyanameade: got it14:56
markwashyeah nor have I. . we can possibly send out a little prompt email14:56
zhiyani have one request here, can i get some thoughts input on https://review.openstack.org/#/c/59630/13/glance/tests/unit/test_migrations.py14:56
mclarenmarkwash: you mean nova pulling straight from swift for exampl?14:56
markwashmclaren: yes like that14:57
ameadezhiyan, markwash: i will reach out to those folks today14:57
mclarenah, ok. I didn't consider that (I was working off current functionality rather than future)14:57
markwashmclaren: sure, I think that's fair. .14:57
icchayes that information should be resifing else where technically speaking instead of in glance config markwash markwash14:57
*** nadya_ has joined #openstack-meeting-alt14:57
*** zhaoqin has joined #openstack-meeting-alt14:57
icchamclaren: ^14:57
mclarenI think for nova pulling straight from swift it makes sense to use multi-tenant (sorry rosmaita :-)14:57
zhiyanwithout that, migration test will be failed due to sqlite db meet deadlock.14:58
markwashmclaren: I'm just noodling on the two feature sets14:58
markwashzhiyan: thanks for the heads up14:58
zhiyanothers of the change are all LGTM. i'm just not sure that point is safe enough14:58
zhiyanameade: thanks, hope to see the final db schema and api def14:59
*** bswartz has joined #openstack-meeting-alt14:59
*** achirko has joined #openstack-meeting-alt14:59
zhiyanameade: and to me it's a large go glance existing's btw14:59
mclarenmarkwash: is that problem solved in the single swift store case?14:59
zhiyan..large change i meaning14:59
*** gregsfortytwo has joined #openstack-meeting-alt14:59
ameadezhiyan: yeah this is a big deal15:00
markwashmclaren: maybe? it may require a little re-imagining15:00
*** shamail has joined #openstack-meeting-alt15:00
*** akerr1 has joined #openstack-meeting-alt15:00
markwashmclaren: there is a potential to just privately share credentials across the client/server boundary through an out-of-band mechanism15:00
markwashi.e. admin puts same config in both places15:00
*** jcorbin has joined #openstack-meeting-alt15:00
markwashah, we should make way15:00
mclarenmarkwash: that would 'work' but fill me with fear :-)15:00
*** shusya has joined #openstack-meeting-alt15:00
icchaseeya!15:00
*** caitlin56 has joined #openstack-meeting-alt15:01
esheffieldI feel like we have a lot of things converging that need careful coordination - generic metadata w/api changes, glanceclient structure reimagining, api autodiscovery, etc.15:01
markwashzhiyan: I'll follow up on that db2 patch15:01
zhiyanmarkwash: thanks15:01
rosmaitaesheffield: +115:01
markwashesheffield: +115:01
markwashthanks everybody!15:01
markwash#endmeeting15:01
*** markmcclain has joined #openstack-meeting-alt15:01
zhiyanesheffield: +115:01
mclarenthanks :-)15:01
markwashmclaren: yeah I definitely share your fears15:02
*** aostapenko has joined #openstack-meeting-alt15:02
bswartzmarkwash: the bot seems to be ignoring you :-(15:02
markwash#endmeeting15:02
bswartzis someone else the chair?15:02
markwashbswartz: :-( no, I started it hmm15:02
aostapenkoHi15:02
markwashbswartz: actually can you try ending it? I had to end the trove meeting when I got here15:03
bswartz#endmeeting15:03
* bswartz slaps openstack around a bit with a large trout15:03
*** julim has quit IRC15:03
markwashah, perhaps if I leave it will yield the chair-ship15:03
*** markwash has left #openstack-meeting-alt15:03
*** sarob has joined #openstack-meeting-alt15:03
bswartz#endmeeting15:03
bswartzopenstack: you suck!15:04
zhiyanoh stupid bot15:04
flwanghaha15:04
*** nadya_ has quit IRC15:04
caitlin56Try starting the meeting.15:04
*** markwash has joined #openstack-meeting-alt15:04
bswartz#startmeeting manila15:04
openstackMeeting started Thu Dec 19 15:04:52 2013 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.15:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:04
*** openstack changes topic to " (Meeting topic: manila)"15:04
openstackThe meeting name has been set to 'manila'15:04
bswartzthere we go15:05
*** mclaren has quit IRC15:05
bswartzI don't know what's up w/ the but but hopefully it will record our meeting15:05
bswartzs/but/bot/15:05
markwashokay, looks like all is well now, have a nice day manila15:05
bswartzty markwash15:05
*** bugsduggan has left #openstack-meeting-alt15:05
bswartz#topic holidays15:05
*** openstack changes topic to "holidays (Meeting topic: manila)"15:05
bswartzokay so before I forget, let's talk about the upcoming meetings15:06
bswartzI'll be on vacation the next 2 weeks and am not able to chair these meetings15:06
bswartzis there any interest in holding them without me?15:07
*** julim has joined #openstack-meeting-alt15:07
bswartzwould someone like to volunteer to chair them in my absence?15:07
akerr1wouldn't be the same without you15:07
caitlin56What's the likelihood of major status updates 2 weeks from now?15:07
bswartzakerr1: The project shouldn't revolve around me though15:08
*** xyang1 has joined #openstack-meeting-alt15:08
*** rnirmal has joined #openstack-meeting-alt15:08
bswartzwell I expect that progress will be relatively modest in the next 2 weeks15:08
caitlin56Not much point in debating things 2 weeks from now, but we might want some form of progress announcement before 3 weeks go by.15:08
bswartzunless someone tells me that they're not taking time off and they plan to spend all their time working on manila!15:08
caitlin56How about , "if you make major progress over the next 2 weeks, announce it on the mailing list rather than waiting for the third week."15:09
bswartzokay so the silence tells me there's no appetite for IRC meetings, which is fine by me15:10
bswartzconsider the 26 Dec and the 2 Jan meetings cancelled15:10
bswartzwe'll meet next on 9 Jan15:10
shamailbswartz: Sounds good15:10
bswartz#topic development status15:10
*** openstack changes topic to "development status (Meeting topic: manila)"15:10
bswartzI've seen lots of activity with the code reviews15:11
*** jergerber has joined #openstack-meeting-alt15:11
bswartzI'll admit that I haven't been able to spend the time I'd like to on code reviews15:11
bswartzyportnova, vponomaryov: any updates from the last week?15:12
*** jtomasek has quit IRC15:12
*** vponomaryov has joined #openstack-meeting-alt15:12
*** mestery_ has joined #openstack-meeting-alt15:12
bswartzvponomaryov: any updates from the last week?15:12
*** sarob has quit IRC15:12
vponomaryovhi15:13
bswartzerm, maybe they're not here15:13
*** bswartz has left #openstack-meeting-alt15:13
gregsfortytwolol15:13
*** bswartz has joined #openstack-meeting-alt15:13
*** tims has left #openstack-meeting-alt15:14
bswartzdoh15:14
bswartzsorry about that15:14
gregsfortytwoswitch windows; don't close them ;)15:14
bswartzI think i clicked too many times15:14
achirkobswartz: https://review.openstack.org/62917 and https://review.openstack.org/60241 ready for code review15:14
vponomaryovabout netapp driver: it is not finished yet, not so long we got lab with backend in l2 layer15:14
bswartzThe neutron plugin went in15:15
bswartzwe're close to having a driver that supports the full multitenancy model15:15
vponomaryovabout network-api - ready for review15:15
*** nadya_ has joined #openstack-meeting-alt15:16
bswartzthanks achirko, vponomaryov15:16
*** mestery has quit IRC15:16
bswartzjust a reminder: https://review.openstack.org/#/q/manila+status:open,n,z15:16
* bswartz reminds himself too15:16
vponomaryovmanila client was a little bit enhanced15:16
bswartzokay15:17
*** ashaikh has joined #openstack-meeting-alt15:17
vponomaryovhttps://review.openstack.org/#/q/project:stackforge/python-manilaclient,n,z15:17
*** kevinconway has joined #openstack-meeting-alt15:17
bswartzcsaba: are you here?15:17
csababswartz: hi!15:17
bswartzcsaba: what is the state of glusterfs driver?15:18
csabawe are working on unit tests... we got a bit lag with that with the sudden swicth from mox to mocks15:18
bswartzyes15:19
bswartzmock is better though15:19
vponomaryovbswartz: we have one open item - do we expect, that in one tenant can be more that one set of policy data for security services?15:19
bswartzvponomaryov: yes15:19
vponomaryovs/that/than15:19
bswartzvponomaryov: there are valid use cases for 2 different krb5/ldap domains within one tenant network15:20
bswartzor 2 different AD domains within 1 network15:20
bswartzI expect those cases to be rare, but not impossible to create15:20
vponomaryovbswartz: thanks15:20
caitlin56The hard part is supporting multiple Security Domains, multiple tenants is not much more than that.15:20
*** IlyaE has joined #openstack-meeting-alt15:21
bswartzcaitlin56: it comes down to whether backends will be expecte to associate more than 1 "virtual server" with each tenant or not15:21
bswartzI say yes15:21
bswartzalthough the common cases will be 0 or 115:21
*** mestery has joined #openstack-meeting-alt15:22
caitlin56I suppose in a single tenant environment you could trust the two AD servers to not interfere with each other.15:22
*** NikitaKonovalov has quit IRC15:22
bswartzcaitlin56: it's up to the tenant to not screw up his configuration15:22
bswartzall manila does it what the tenant asks for15:23
bswartzs/it/is/15:23
bswartzokay enough on status15:23
vponomaryovbswartz: after your answer about amount of policies15:23
vponomaryovappears one more question15:24
bswartzwe have a lot of open reviews so I'll try to get stuff that's complete merged before the holidays15:24
vponomaryovpolicies and network data can be splitted to two entities in that case15:24
bswartzvponomaryov: well each network can have 0 or more policies associated with it, each one will have a UUID associated with it, and the UUID is what matters when you call share-create15:25
*** mestery_ has quit IRC15:25
vponomaryovUUID of network data?15:26
bswartzyes15:26
bswartzerr, I think15:26
vponomaryovbut two entities should have its own UUIDs, and one can have link to another15:27
achirkobswartz: so as I understand we associate multiple policies with one network, on share-create we specify network_id and policy_id15:27
vponomaryovachirko: +115:28
bswartzachirko: no I don't think so15:28
achirkobswartz: and if specified policy is not associated with specified network - its an error15:28
bswartzI'd rather just have 1 UUID passed to share-create, and that should be the ID of the network info15:28
bswartza given "network" should be able to have more than 1 network info associated with it15:28
bswartz1 per policy15:29
*** rahmu has joined #openstack-meeting-alt15:29
caitlin56bswartz: with single tenant, multiple security domains, the tenant domain can export *anything* to any security domain. Correct? With multi-tenant we have to add the restriction that a tenant admin can only export their own stuff.15:29
*** NikitaKonovalov has joined #openstack-meeting-alt15:30
bswartzcaitlin56: don't get create and export mixed up15:31
bswartzcaitlin56: the create is what cares about the security domain15:31
bswartzcaitlin56: the export just modifies the security rules around the created thing15:31
achirkobswartz: ok, so when I say 'network' and 'network-info' i mean neutron subnet. So if we associate many policies with this 'network' and then pass only uuid of 'network', we can't tell which policy to use15:31
*** jmontemayor has joined #openstack-meeting-alt15:31
shamailbswartz: Are you saying that we should be able to define the same network address space to multiple network IDs and the network ID contains a single policy?15:32
*** jjmb1 has quit IRC15:33
bswartzokay so we need to get a bit clearer about terms15:33
*** jjmb has joined #openstack-meeting-alt15:33
*** Sackmann has left #openstack-meeting-alt15:33
bswartzwe have one document here:15:33
bswartz#link https://wiki.openstack.org/wiki/Manila/docs/API-roadmap15:34
bswartzI should probably add something to this though because it still doesn't clearly communicate what we're talking about15:34
bswartzwe have neutron subnets, which are defined outside of manila15:34
bswartzmanila can associate 0 or more policies with each neutron subnet15:34
bswartzeach of those subnet+policy pairings forms a "network-info"15:35
bswartzand that network info has a UUID15:35
caitlin56bswartz: you can form a "policy" (what I think of as a "Security Domain") using just export control, you only need neutron networks for multi-tenant. Is that correct?15:36
bswartzshamail: I think that it will be clear once we have an implementationg working15:36
achirkobswartz: this wiki is outdated - we split 'policy' and 'network' into different APIs15:36
bswartzachirko: we may need to follow up on this offline15:36
bswartzachirko: do you have any document that's more up to date?15:36
achirkobswartz: so docs yes, but we have code15:37
bswartzI think a diagram would be worth a thousand words here15:37
caitlin56achirko: year-long low on inside-company meeting over the next two weeks -- great opportunity to get doc read.15:38
bswartzlet's get together and build one15:38
jcorbinbswartz: +115:38
shamailI like archirko's suggestion since it sounds more dynamic then pre-configured neutron subnet/policy mappings (e.g. 'Network-info'), but either option seems to achieve similar goals... A) creation of policy and neutron network are split B) binding the two together at same layer15:39
shamaildoh, IRC was lagging... Discussion has moved on.  Sorry.15:39
bswartzspeaking of diagrams, I still need to make one that illustrates the multitenancy design, regarding the split between drivers that directly join tenant networks, and drivers that use a bridge/gateway to provide shares to tenants15:39
bswartzshamail: IRC lag could explain the bot's odd behaviour earlier15:40
bswartz#topic multitenancy15:40
*** openstack changes topic to "multitenancy (Meeting topic: manila)"15:40
bswartzso as I was saying the document here is still out of date (no change from last week)15:41
bswartzanyone tried some experiments in this area? either with virtfs or ganesha?15:41
*** rongze has joined #openstack-meeting-alt15:42
bswartzI think I'll start drawing on my whiteboard and taking photographs to create a rough draft of a diagram15:42
* bswartz is not good with graphics authoring tools15:42
shamail FS15:43
* caitlin56 volunteers to translate a picture of a whiteboard into a google diagram.15:43
*** jcooley_ has joined #openstack-meeting-alt15:44
bswartzooh does google have a decent SVG drawing program?15:44
caitlin56I don't think it is svg, but same functionality.15:44
bswartzvery well15:44
*** jjmb has quit IRC15:44
caitlin56short of what you can do with visio, but without the licensing issues.15:45
*** rongze_ has quit IRC15:45
bswartzokay so this remains a difficult area -- I'd love to see a proof of concept design working15:45
bswartzbut in the mean time I'll keep working on trying to communicate the design/plan clearly15:45
bswartz#topic open discussion15:45
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:45
bswartzanything else this week?15:45
bswartzreminder for those who joined late: meeting is cancelled next 2 weeks, we reconvene on 9 Jan15:46
bswartzI will update the wiki15:46
vponomaryovbswartz: will you be available via email?15:46
bswartzachirko: if you have time on Monday I'd like to finalize the design for network/policy/networkinfo15:47
*** akerr1 is now known as akerr15:47
bswartzvponomaryov: off and on -- I will be travelling but I will have my notebook15:47
achirkobswartz: ok15:47
bswartzokay we'll end a bit early today15:48
vponomaryovbswartz; got it, if we have urgent questions, we write15:48
shamailTake care everyone, see you after the new year!15:48
bswartzthanks everyone15:48
vponomaryovthanks15:48
bswartzhave a safe and happy holiday15:48
*** shamail has quit IRC15:48
*** shusya has quit IRC15:48
aostapenkothanks, bye15:48
achirkobye15:48
caitlin56bswartz: just checked, google draw can export as svg.15:48
*** zhaoqin has quit IRC15:49
*** achirko has left #openstack-meeting-alt15:49
bswartz#endmeeting15:49
*** openstack changes topic to "blueprint process (Meeting topic: glance)"15:49
openstackMeeting ended Thu Dec 19 15:49:22 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-12-19-15.04.html15:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-12-19-15.04.txt15:49
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-12-19-15.04.log.html15:49
*** jcorbin has left #openstack-meeting-alt15:49
*** caitlin56 has quit IRC15:50
*** thinrichs has joined #openstack-meeting-alt15:53
*** gregsfortytwo has left #openstack-meeting-alt15:54
*** bswartz has left #openstack-meeting-alt15:54
*** rossella_s has quit IRC15:54
*** NikitaKonovalov has quit IRC15:55
*** rsblendido has quit IRC15:55
*** natishalom has joined #openstack-meeting-alt15:55
*** aostapenko has left #openstack-meeting-alt15:56
*** SergeyLukjanov has quit IRC15:56
*** songole has joined #openstack-meeting-alt15:56
*** prasadv has joined #openstack-meeting-alt15:56
*** rraja has quit IRC15:59
*** yportnov_ has quit IRC15:59
*** tedross has joined #openstack-meeting-alt15:59
*** michsmit has joined #openstack-meeting-alt15:59
mesteryhi16:00
*** s3wong has joined #openstack-meeting-alt16:00
*** akerr has left #openstack-meeting-alt16:00
*** natishalom has joined #openstack-meeting-alt16:00
banixhi16:00
thinrichsHi16:00
ashaikhhey guys16:00
s3wonghello16:00
mestery#startmeeting networking_policy16:00
openstackMeeting started Thu Dec 19 16:00:44 2013 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: networking_policy)"16:00
openstackThe meeting name has been set to 'networking_policy'16:00
mestery#link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy Agenda16:00
*** julim has quit IRC16:01
mesteryLooks like a short agenda today, driven by an email sent to the list by banix last night.16:01
mestery#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/022677.html16:01
mesteryLets first go over action items from last week.16:01
mesteryalagalah: You around today?16:01
banixThe taxonomy is already merged.16:02
mesterybanix: Awesome, thanks for confirming!16:02
*** julim has joined #openstack-meeting-alt16:02
*** pballand has joined #openstack-meeting-alt16:02
mesterybanix: Do you want to lead the discussion to get consensus on the points you sent out?16:02
mesteryI think we should focus on that today per your email.16:02
banixmestery: yes, sure.16:02
mesterybanix: thanks16:02
banixFollowing up from the meeting last week and a few email threads, I thought we should close on a few preliminary things:16:03
*** sarob has joined #openstack-meeting-alt16:03
banixTwo models namely, source/destination and producer/consumer were discussed16:04
*** flwang has quit IRC16:04
banixThe proposed solution to merge these models was to modify the model to allow a list of endpoints (rather than single endpoint) in src and dest groups in the policy16:04
*** SushilKM__ has quit IRC16:05
banixI think we may want to change the name of these two attributes of Policy but other than that would that work for everyone?16:05
michsmitIn the past, we talked about having a bidirectional flag in the policy16:05
michsmitNot sure if source and dest group are the right terms16:06
banixmichsmith: yes, we have that in the attributes table.16:06
banixmichsmith: Do you have suggestions for new names?16:06
michsmitnot yet ;-)16:07
mesteryShould we use those temporarily then for the names?16:07
banixmestery: makes sense16:07
mesterymichsmit: You ok with that as well?16:07
michsmitsure, until we come up with something better16:07
songoleHow about left and right, if that makes sense?16:07
*** sarob has quit IRC16:07
banixwe can change them when we come up with better names16:07
*** colinmcnamara has joined #openstack-meeting-alt16:07
s3wongbanix: so if we have directionality in the policy (namely what endpoint groups are associated with what direction), do we still need a flag on policy itself?16:07
*** alexpec has joined #openstack-meeting-alt16:08
*** Barker has joined #openstack-meeting-alt16:08
s3wongI guess if it is for both direction16:08
ashaikhbanix:  advantage of src/dest naming is clarity in where the policy is applied and directionality16:08
banixs3wong: I think by default, there is directionality in one direction. The flag allows to make it bidirectional, if that makes sense for a given policy.16:09
mesteryashaikh: Makes sense to me as well.16:09
mesteryOK, that was an easy one to converge on. Thanks banix!16:10
banixgreat.16:10
mesteryNext on your list was a minimum set of actions to support, right banix?16:11
banixthe next issue is the list of actions16:11
*** nadya_ has quit IRC16:11
banixmestery: yes16:11
prasadvfor bidirectional, what does classifier mean? Will the same classifier apply  in reverse direction?16:11
banixprasadv: yes16:11
s3wongprasadv: yeah, that would be what it means16:11
ashaikhprasadv: if it doesn't, it will be very confusing :-)16:11
banixI think for minimum set of actions we have three candidates16:12
banixsecurity, redirect and qos16:12
*** slagle has quit IRC16:12
banixI think we have a good handle on the first two; do we feel the same about qos?16:12
prasadvredirect requires a little bit of clarity too16:12
s3wongI guess 'security' is a given - at least 'allow' and 'drop' needs to be supported16:12
mesteryFor qos, we should make sure to loop in sc68cal, as he's doing work in this area and wanted to be involved.16:13
banixs3wong: Yes16:13
prasadvif there is a group does it mean the traffic is sent to all the ones in the group16:13
mesterybanix: Lets discuss qos on openstack-dev so sc68cal can chime in there.16:13
ashaikhwhat do folks think about really minimizing the "required" supported policies, e.g., just to security16:13
michsmitDoes redirect include the service insertion work ?16:13
mesteryashaikh: For the POC, it would help with implementation time.16:13
s3wong'redirect' action generated a lot of opinions from the email thread - though the definition now is very generic16:13
ashaikhmestery: right, and i would expect a lot more variation on implementations for the other two16:14
banixmichsmith: potentially, yes.16:14
s3wongbut prasadv and others want more clarity16:14
* mestery nods in agreement with ashaikh.16:14
banixso are we suggesting to have "security" as the only action for now?16:14
s3wongI am good with just 'security' as required action for now16:14
banixto start with?16:15
*** jjmb has joined #openstack-meeting-alt16:15
s3wongsure makes reference implementation simpler16:15
ashaikhbanix: while we try to sort out a model and api for the other two16:15
banixand we can clarify any other action, namely redirect and qos and possibly others16:15
banixas we continue this work16:15
*** rongze has quit IRC16:15
ashaikhalso would give us a chance to solidify connection with things like service chaining/insertion16:15
banixashaikh: yes16:15
*** bdpayne has joined #openstack-meeting-alt16:16
*** jcooley_ has quit IRC16:16
mesterySo is everyone ok with security as the main action for step one then?16:16
*** rongze has joined #openstack-meeting-alt16:16
s3wongbanix: let's settle on it then - just 'security': 'allow' | 'drop' as the only required action16:16
banixSounds good, mastery, s3wong16:17
mestery#action Initial action supported will be security action.16:17
s3wongI will update the document16:17
ashaikhs3wong: we could still list the other two as optional action types, right?  (and keep working on their defn)16:17
mestery#undo16:17
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x390e850>16:17
banixs3wong: You wrote theta part of the doc, would you be willing to convert what we have from the attributes table to16:17
mestery#info Initial action supported will be security.16:17
*** hemanthravi has joined #openstack-meeting-alt16:17
banixsomething that does not suggest these are Neutron objects16:18
*** jjmb has quit IRC16:18
s3wongashaikh: of course, and the example are already in the doc, I will update that with more clarity as well16:18
michsmitdo we need drop or can that be implicit ?16:18
s3wongbanix: certainly16:18
banixs3wong: Thank you.16:18
s3wongmichsmit: good point, should we make 'drop' be the default?16:18
*** SushilKM__ has joined #openstack-meeting-alt16:18
mestery#action s3wong to update attributes table16:19
banixmestery: Do you know the status of service chaining? Is it being incorporated as an extension? I didn't see it in the Icehouse list?16:19
ashaikhmichsmit: i think it makes sense to have drop be the default, i.e., explicitly allow specified traffic16:20
thinrichss3wong, michsmit: I think we're starting to talk about conflict resolution within a policy.16:20
mesterybanix: Service chaining discussions are mostly on hold due to focus on stability in Icehouse. I expect in "J" for them to come alive again.16:20
s3wongOK - 'drop' as default settled - will update the doc accordingly16:20
banixmestery: thanks16:20
thinrichsIf we have both 'allow' and 'drop' and a policy uses both actions, we need to decide which one takes precedence (in some way).16:21
s3wongI guess we have 40 minutes for conflict resolution :-)16:21
thinrichsIf we don't have both 'allow' and 'deny' then we're implicitly assuming conflicts are not allowed within the policy.16:21
*** flwang has joined #openstack-meeting-alt16:21
*** rongze has quit IRC16:22
*** rongze has joined #openstack-meeting-alt16:22
michsmitthinrichs: it would also allow the policy to be order independent16:23
banixLet me try to understand the conflict within the policy issue better16:23
banixWould this arise only with overlapping classifiers?16:23
s3wongthinrichs: there are several levels of this. Obviously we shouldn't allow two 'security' actions within the list of action in a single policy-rule16:23
thinrichsmichsmit: we could still be order independent IF we did conflict resolution at the level of the actions themselves, instead of at the level of policy statements, e.g. Allow takes precedence over Deny.16:24
s3wongthe problem would be when we have multiple policy-rules with conflicting 'security' actions16:24
thinrichsSo if you write a bunch of allow statements and you write a bunch of deny statements, it could so happen that your policy (sometimes) says to both allow and deny.  When that happens, the conflict resolution scheme deems that 'allow' wins.16:24
thinrichsbanix: yes--if two classifiers both apply then those rules could dictate different actions.16:25
s3wongthinrichs: should the one with more specific classifier match wins?16:25
thinrichsbanix: it's typically hard to ensure classifiers do not overlap (both for people and for machines)16:25
*** vipul-away is now known as vipul16:26
thinrichss3wong: that's an idea.  I wonder how easy it is, though, to modify a large policy to meet some new demand.16:26
banixTwo suggested solutions: 1) 'allow; wins 2) more specific classifier wins16:26
mesterythinrichs: Seems like your proposal simplifies things a bit, I like resolving this at the higher level.16:26
s3wongfor example, port 80 match on {min:10, max:100} classifier and {port==80} classifier should take the action of the latter16:27
thinrichsHow hard is it for someone to figure out what the most-specific classifier is across all rules and then write a rule that is even more specific than it?16:27
michsmitthinrichs: depends on the size of the policy, could be difficult16:28
*** ruhe has quit IRC16:28
*** aignatov has quit IRC16:28
ashaikhthinrichs: that's my worry too -- maybe we should try to restrict with an eye toward simplifying the imple in the first version16:28
thinrichsAnd I suppose there's the question of how we define "more specific".  This has to be something that the algorithm decides.  Maybe it's just the number of tests in the classifier?  But then what if there's a tie?16:28
s3wongthinrichs: may not be easy if we expect to have many policy-rule within a policy16:28
ashaikhe.g., just allow explicit allow actions for now ? i.e., default-off model16:29
*** jjmb has joined #openstack-meeting-alt16:29
thinrichsThe nice thing about 'allow over deny' is that once we add additional actions (qos, etc.) we can use the same scheme and enable multiple actions to be applied as long as they don't conflict.16:29
*** jjmb has quit IRC16:30
thinrichsThough perhaps the same could be said for the 'more specific' resolution strategy if we only applied it to groups of actions that are non-conflicting.16:30
banixashaikh: then the first solution (allow over deny) seems simple enough16:30
s3wongthinrichs: well there are action types where multiple actions can be defined per classifier match: for example, 'qos'16:31
*** csaba is now known as csaba|afk16:31
thinrichsashaikh: we could do that and punt on conflict resolution for now, but I think eventually we'll need a conflict resolution scheme.16:31
thinrichss3wong: absolutely--we've just been talking about qos as a single action today.  I did the same.16:31
thinrichss3wong: sorry--missed your point.16:31
michsmitthinrichs: 'allow over deny' makes more sense to me if the only deny is the implicit deny all at the end16:31
thinrichss3wong: What if the actions defined are conflicting?  I don't see that having multiple-actions in a single rule changes things.16:32
ashaikhthinrichs: yes, definitely16:32
*** jcooley_ has joined #openstack-meeting-alt16:33
s3wongthinrichs: no, the point is - some action_type is a singleton within an action_list, while others are not (both 'qos' and 'redirect' can have multiple instances in an action list)16:33
ashaikhmichsmit: i agree, it seems more intuitive to me as well16:33
banixOK, are we punting or taking the field goal :)16:33
thinrichsmichsmit: Or we could have 'deny over allow' and make 'allow' implicit.  I don't think it actually matters that much.  And I think of the default as a 'policy completion' strategy, which is analogous to the conflict resolution strategy except that instead of dealing with a policy that has too much information (conflicts) it deals with the problem of having too little information (where the policy doesn't say anything).16:34
banix"allow over deny" for conflict resolution?16:34
s3wongbanix: let's settle on that for reference implementation purpose16:34
*** nadya_ has joined #openstack-meeting-alt16:34
s3wongjust 'allow' over implicit 'deny' - so a single 'allow' action over overlapping classifiers will win16:34
songolebanix: Defining exceptions to a generic allow might be an issue16:35
thinrichssongole: Conceptually we can suggest writing generic 'deny' statements and then using 'allow' to make exceptions.16:35
*** sacharya has joined #openstack-meeting-alt16:35
mesteryAre we concluding on the default deny with allow taking precedence, or the reverse?16:35
banixsongole: Please elaborate? Are you referring to thinrichs's implicit allow?16:35
s3wongsongole: please elaborate16:36
songoleGeneric allow port 80 and deny a specific source or dest16:36
michsmitmestery: I think the default deny makes more sense16:36
banixmestery: default deny with allow taking precedence16:36
mesterymichsmit banix: I agree with both of you.16:37
thinrichssongole: I'm sure there will always be cases where we need to do surgery on the existing policy to say what we want (for any conflict resolution strategy).16:37
banixsongole: src/dest are fixed in the policy16:37
s3wongsongole: wouldn't that be a different policy for specific endpoint groups?16:38
banixI think this is a good first step for conflict resolution16:38
*** HenryG_ has joined #openstack-meeting-alt16:38
*** SergeyLukjanov has joined #openstack-meeting-alt16:38
songoleDoes the endpoint define src/dst?16:39
banixIf we agree on that (default deny, allow taking precedence), should we move on to net topic?16:39
prasadvwe do need to also talk about classifier16:39
s3wongOK - with consensus, I will also update the doc with allow over deny on action section16:39
banixprasadv: go ahead please16:39
prasadvi think songole meant that classifier can have src/dest fields different from src/dst groups16:40
s3wongprasadv: yes, now we are talking about adding the IP address fields in classifier16:40
*** nadya_ has quit IRC16:40
songoleprasadv: yes16:40
s3wonghence 'next topic' :-)16:40
*** HenryG has quit IRC16:41
mestery#action s3wong to update document to note "allow over deny" in action section.16:41
michsmits3wong:  I would think we would try to avoid IP addresses in the classifiers16:41
banixyeah, I remember you guys talking about this. DO we need to have this in the first cut?16:41
prasadvmichsmit: how can we avoid them, if some use cases need them16:41
s3wongmichsmit: I am for that. prasadv and Dimitri both want it - so I am open for discussion16:42
*** jjmb has joined #openstack-meeting-alt16:42
ashaikhonce we start to add more headers, won't we essentially end up with an openflow match-like list (as thinrichs pointed out in email)16:42
*** jcoufal has quit IRC16:42
michsmitIP addresses for subnets outside of Neutron control makes sense, but for VMs I would think that the group membership is the way to classify IP addresses16:43
*** ativelko_ has quit IRC16:43
michsmitBy subnets outside of Neutron control, I mean WAN, etc.16:43
banixI think for now, we should keep the classifier simple (that is as is).16:43
thinrichsWe're talking about the *possible* matching fields, right?  So just because some rules match on IP source doesn't mean all rules must.16:44
songolewhat is allowed in a classifier - default?16:44
s3wongsongole: protocol field + L4 port number16:44
*** natishalom has quit IRC16:44
prasadvmichsmit: for group membership it is ok. but I thought we are talking about traffic passing through them right?16:44
banixsonogole: and a type. Please refer to https://docs.google.com/document/d/1ZbOFxAoibZbJmDWx1oOrOsDcov6Cuom5aaBIrupCD9E/edit#heading=h.6j822g6556qq16:45
prasadvand traffic can be independent of the src/dest group IP16:45
michsmitprasadv: I'm not sure I understand what you mean by 'traffic passing through them'16:46
prasadvmichsmit: currently we are deriving the IP addresses to match that of src and dst group right16:47
*** ruhe has joined #openstack-meeting-alt16:47
banixprasadv: I think you may be referring to what we are saying would be in the action, e.g, a service chain16:47
prasadvbanix:yes16:47
*** natishalom has joined #openstack-meeting-alt16:48
prasadvif we were to have L2 firewall inserted,16:48
banixprasadv: so that would not affect the classifier as we have it in the current model16:48
prasadvit does not depend on the src and dest group IP16:48
prasadvbanix:yes16:48
*** zane has quit IRC16:49
*** zane has joined #openstack-meeting-alt16:49
banixprasadv: I meant that would not require having new fields in the classifier. Do you agree?16:49
prasadvor I can say send traffic that matches the following classifier from these set of ports to a VM that is analysing traffic16:49
s3wongprasadv: so the use case is if only a selected set of traffic from src group or to dst group should subject to a particular action, how can we do it with the current model?16:49
prasadvbanix: we cannot define such a classifier with the current model16:50
prasadvs3wong:yes16:51
ashaikhprasadv: i think michsmit was suggesting to "classify" IP subnets for policy by putting them in  their own group (if i understood correctly) as an alternative16:51
*** aignatov has joined #openstack-meeting-alt16:51
ashaikh(them = endpoints belonging to the subnet)16:51
banixprasadv: I think Inow I understand what you say. Slow day :)16:51
*** jcooley_ has quit IRC16:52
*** alexpec has quit IRC16:52
*** amotoki has quit IRC16:52
michsmitashaikh: yes16:52
banixso we can have the prts/vms in a group but16:52
banixthen we are limited if we want to apply a policy rule on a subset of traffic between such groups16:53
s3wongbanix: yes - I think that's what prasadv was referring to16:53
banixI think we can keep this as something we discuss more and leave the model as is for now16:53
prasadvashaikh, michsmit: but it may not be just subnets right? Maybe I donot understand how michsmit is suggesting to do16:53
michsmitbanix: I would think that is the purpose of the classifier in the policy16:53
*** jjmb has quit IRC16:54
s3wongsounds like it would be nice to be able to tag endpoints to subject to a set of actions directly (or matching tag) - can get complicated16:54
banixmichsmit: I think the issue is that if groups are made up of ports for example, then the classifier we have won't be able to classify traffic into different groups properly16:54
michsmitbanix: by ports, you mean Neutron ports, not L4 ports, correct ?16:55
banixmichsmith: in other words, port number, etc won't be enough16:55
*** jtomasek has joined #openstack-meeting-alt16:55
banixmichsmith: yes16:55
*** jjmb has joined #openstack-meeting-alt16:55
*** mozawa has quit IRC16:55
*** jcooley_ has joined #openstack-meeting-alt16:55
*** amotoki has joined #openstack-meeting-alt16:55
*** RajeshMohan has quit IRC16:56
s3wong5 minutes left - should we move this to ML again?16:56
banixAs we are approaching the top of hour should we keep the model as is for now but continue the discussion16:56
mestery+1 to moving to ML.16:56
banixs3wong: agree16:56
ashaikhbanix: yeah, makes sense16:56
michsmit+116:56
mesteryWe're almost out of time, as s3wong indicates.16:56
prasadv+1 ML16:56
*** SushilKM__ has quit IRC16:56
s3wongI am also guessing we won't have meetings over the next two weeks, right?16:56
banixthere is one thing i want to ask and that is about the PoC?16:56
*** RajeshMohan has joined #openstack-meeting-alt16:56
*** demorris has quit IRC16:57
s3wongbanix: yes?16:57
banixare we planning to do this within the ML2 framework (which makes sense) and if yes, would this be done by ….16:57
mesterybanix: Lets converge on the PoC at the next meeting perhaps?16:57
banixusing a framework similar to how Router extension is done for ML2?16:57
mesteryAny takers to canceling the next week's meetings?16:57
mesterybanix: +1 to that idea in general.16:58
banixok16:58
thinrichsI won't be here next week.16:58
banix+1 for canceling16:58
s3wongbanix: that would be the plan, I think16:58
s3wongmestery: so we will reconvene on Jan 2nd?16:58
mesteryOK, lets cancel this one, but how about if we meet next on January 2?16:58
mesteryWoudl that work?16:58
*** RajeshMohan has quit IRC16:58
*** jcooley_ has quit IRC16:58
*** amotoki has quit IRC16:58
s3wongmestery: Jan 2nd works for me16:58
prasadvYes for Jan 216:58
banixmestery: that would work for me16:59
michsmit+1 Jan 216:59
songoleYes for jan 216:59
mestery#action mestery to send email canceling next week's meeting and noting we'll reconvene on January 216:59
mesteryOK, thanks eveyrone!16:59
mesteryLets continue the discussions on the ML.16:59
banixHappy holidays :)16:59
mesteryHappy holidays!16:59
mestery#endmeeting16:59
*** openstack changes topic to "blueprint process (Meeting topic: glance)"16:59
songolethanks16:59
openstackMeeting ended Thu Dec 19 16:59:38 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2013/networking_policy.2013-12-19-16.00.html16:59
prasadvthanks16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2013/networking_policy.2013-12-19-16.00.txt16:59
s3wongThanks, guys!16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2013/networking_policy.2013-12-19-16.00.log.html16:59
*** prasadv has quit IRC16:59
*** hemanthravi has quit IRC16:59
*** thinrichs has quit IRC16:59
*** songole has left #openstack-meeting-alt17:00
*** glucas_ has joined #openstack-meeting-alt17:00
*** natishalom has quit IRC17:01
*** SushilKM__ has joined #openstack-meeting-alt17:02
*** glucas has quit IRC17:03
*** glucas_ is now known as glucas17:03
*** SergeyLukjanov is now known as _SergeyLukjanov17:03
*** jmontemayor has quit IRC17:04
*** NehaV1 has joined #openstack-meeting-alt17:04
*** NehaV1 has quit IRC17:04
*** _SergeyLukjanov has quit IRC17:04
*** NehaV1 has joined #openstack-meeting-alt17:04
*** RajeshMohan has joined #openstack-meeting-alt17:04
*** jcooley_ has joined #openstack-meeting-alt17:04
*** amotoki has joined #openstack-meeting-alt17:04
*** card.freenode.net changes topic to " (Meeting topic: networking_policy)"17:04
*** NehaV has quit IRC17:06
*** jmontemayor has joined #openstack-meeting-alt17:07
*** SergeyLukjanov has joined #openstack-meeting-alt17:07
*** RajeshMohan has quit IRC17:09
*** jcooley_ has quit IRC17:09
*** amotoki has quit IRC17:09
*** RajeshMohan has joined #openstack-meeting-alt17:09
*** amotoki has joined #openstack-meeting-alt17:12
*** jcooley_ has joined #openstack-meeting-alt17:15
*** zane1 has joined #openstack-meeting-alt17:15
*** michsmit has quit IRC17:15
*** eankutse has quit IRC17:16
*** aignatov has quit IRC17:17
*** markmcclain has quit IRC17:17
*** zane has quit IRC17:18
*** ruhe has quit IRC17:18
*** jcooley_ has quit IRC17:22
*** yidclare has quit IRC17:23
*** jtomasek has quit IRC17:25
*** RajeshMohan has quit IRC17:26
*** RajeshMohan has joined #openstack-meeting-alt17:26
*** GheRivero has quit IRC17:28
*** Barker has quit IRC17:30
*** michsmit has joined #openstack-meeting-alt17:33
*** Barker has joined #openstack-meeting-alt17:34
*** sarob has joined #openstack-meeting-alt17:37
*** SushilKM__ has left #openstack-meeting-alt17:39
*** rongze has quit IRC17:39
*** slagle has joined #openstack-meeting-alt17:39
*** rongze has joined #openstack-meeting-alt17:40
*** amytron has quit IRC17:40
*** slagle has quit IRC17:41
*** slagle has joined #openstack-meeting-alt17:41
*** luQAs has quit IRC17:43
*** rongze has quit IRC17:44
*** eankutse has joined #openstack-meeting-alt17:47
*** sreshetnyak has joined #openstack-meeting-alt17:47
*** bdpayne has quit IRC17:49
*** bdpayne has joined #openstack-meeting-alt17:50
*** ruhe has joined #openstack-meeting-alt17:50
*** zane1 has quit IRC17:53
*** arnaud has joined #openstack-meeting-alt17:55
*** michsmit has quit IRC17:55
*** arnaud__ has joined #openstack-meeting-alt17:55
*** s3wong has quit IRC17:55
*** kevinconway has quit IRC17:56
*** eankutse has quit IRC17:57
*** zhiyan has left #openstack-meeting-alt17:57
*** dmitryme has joined #openstack-meeting-alt17:58
*** sarob has quit IRC17:59
*** crobertsrh has joined #openstack-meeting-alt18:00
*** chris_m has joined #openstack-meeting-alt18:01
*** mattf has joined #openstack-meeting-alt18:02
SergeyLukjanovsavanna tem will be here in several mins18:02
*** sarob has joined #openstack-meeting-alt18:03
*** aignatov has joined #openstack-meeting-alt18:03
*** balajiiyer has quit IRC18:03
*** nadya has joined #openstack-meeting-alt18:04
SergeyLukjanovsavanna guys are you around?18:04
*** harlowja_away is now known as harlowja18:04
dmitrymeyep18:05
ruhehi18:05
*** nadya is now known as Guest7488918:05
mattfo/18:05
aignatovo/18:05
SergeyLukjanov#startmeeting savanna18:05
*** alazarev has joined #openstack-meeting-alt18:05
openstackMeeting started Thu Dec 19 18:05:25 2013 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:05
mattfGuest74889 isn't here i guest18:05
*** balajiiyer has joined #openstack-meeting-alt18:05
*** openstack changes topic to " (Meeting topic: savanna)"18:05
openstackThe meeting name has been set to 'savanna'18:05
SergeyLukjanov#topic Agenda18:05
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:05
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SavannaAgenda18:06
*** Guest74889 is now known as nadya_18:06
SergeyLukjanov#topic Action items from the last meeting18:06
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"18:06
*** tmckay has joined #openstack-meeting-alt18:06
SergeyLukjanovmy action item is still actual18:06
SergeyLukjanov#action SergeyLukjanov to check that all blueprints created and ping guys to make them if not18:06
SergeyLukjanov#action SergeyLukjanov add links to the blueprints to roadmap18:06
SergeyLukjanov#topic News / updates18:07
*** openstack changes topic to "News / updates (Meeting topic: savanna)"18:07
SergeyLukjanovfolks, please18:07
SergeyLukjanov#info next two meetings canceled - Dec 26, Jan 218:07
dmitrymeI've started a thread in openstack-dev regarding unified guest agent18:08
aignatovok, as for me, this week I mostly work on heat integration, patch is merged already, it can work with Neutron, now working on adding anti affinity feature18:08
dmitrymethat didn't result in consesus18:08
mattfupdate - erikb and i huddled about plugin policy. we agreed that having a minimum set of features available in a plugin is important to provide consistency across savanna deployments. plugin writers should be keeping that in mind. however, we agreed that until we start seeing more than just an HDP plugin, we don't truly need a firm policy.18:08
tmckayI'm working on the java action addition18:08
aignatovalso today I found  bug https://bugs.launchpad.net/savanna/+bug/126278318:08
dmitrymequite contrary: there were many different opinions18:08
SergeyLukjanovmattf, thx, I was writing the same :)18:08
crobertsrhjob-relaunch functionality is under review, should be pretty well set.  work to allow "mapReduce" type jobs is underway (UI side).  I'll be working on allowing HDFS data sources next (UI side now that api-side has been done).18:08
aignatovfix is ready, testing., will send patch in hours18:08
dmitrymenow I implement PoC and hope we will move discussion further having an example on how agent could look like18:09
aignatovtmckay: I saw your draft, will look in to more closer tomorrow, ok? :)18:09
*** lblanchard has quit IRC18:09
tmckayaignatov, no problem it's a work in progress.  Still a lot of holes to fill :)18:09
tmckayWe talked about changing "Jar" to "MapReduce" last week for EDP job types, that change is merged18:10
*** sarob has quit IRC18:10
alazarevI have found root cause for #1240511 ([EDP][Vanilla] Oozie process does not start from time to time), fix is commited18:10
aignatovyep, thanks for this patch18:10
*** amcrn has joined #openstack-meeting-alt18:10
*** sarob has joined #openstack-meeting-alt18:11
tmckayalazarev, that's great!18:11
aignatovalazarev, good job, I saw your one of your patheds merged into Oozie trunk, well done18:11
aignatov*patches18:11
mattfalazarev, have a pointer to ^^'s jira?18:11
aignatovwe'll include this patch into DIB elements, right? because right now we can't work with oozie and we should use stable releases18:12
alazarevyeap, https://issues.apache.org/jira/browse/OOZIE-164718:13
alazarevit is not a root cause, but it hides real error18:13
mattfalazarev, so that allows us to properly retry on error?18:14
*** amytron has joined #openstack-meeting-alt18:14
*** nadya_ has quit IRC18:14
alazarevit was merged to trunk in 30 minutes, I didn't expect such speed from hadoop eco :)18:14
SergeyLukjanov:)18:14
* mattf smiles18:14
*** sarob has quit IRC18:15
aignatovmattf, actually no, right now andrew implemented workaround you provided at the summit time ;) https://review.openstack.org/#/c/62511/18:15
alazarevmattf: Savanna doesn't wait until HDFS starts, it expects that "start datanode" is enough18:15
mattffor the record, aignatov provided it, i just recorded it18:15
*** nadya_ has joined #openstack-meeting-alt18:15
alazarevmattf: I added loop to wait active HDFS18:15
mattfalazarev, ack18:16
mattfalazarev, well done on this!18:16
*** sarob has joined #openstack-meeting-alt18:16
*** ruhe has quit IRC18:17
SergeyLukjanovI think there are nothing to discuss in roadmap section, it blocked by my action items, will be done in next two weeks ;)18:17
SergeyLukjanovreminder: icehouse-2 will be Jan 2318:17
aignatovalazarev, don't you think we should add such wait method to catch list of active tasktrakers?18:17
alazarevmattf: regarding swift support in hadoop, it seems that I don't have time to finish backport properly, will put patch as is with note about done and not done work18:17
mattfPSA - i'll be out 24 dec -> 2 jan18:17
tmckayme too ^^18:18
alazarevmattf: I mean will put to hadoop JIRA18:18
mattfalazarev, thank you, the hwx folks can help there too18:18
SergeyLukjanovI'll be on vacation Dec 29 - Jan 1218:18
SergeyLukjanovbut I'll be available as always ;)18:18
SergeyLukjanovat least each other day18:18
mattfSergeyLukjanov, yeah, i'll probably have my laptop with me too. for shame.18:19
SergeyLukjanov#topic General discussion18:19
*** openstack changes topic to "General discussion (Meeting topic: savanna)"18:19
SergeyLukjanovmattf, :)18:19
*** ruhe has joined #openstack-meeting-alt18:19
SergeyLukjanovmattf, do you have any thoughts about unified agents?18:19
*** akuznetsov has joined #openstack-meeting-alt18:19
SergeyLukjanovthere always tons of emails in ML :)18:20
mattfSergeyLukjanov, i do, but i'm not caught up on the thread yet. so i'll hold my comments for the thread or #savanna18:20
alazarevalso, Mirantis has customer interested in intel plugin to Savanna, I'm going to take care of "IDH plugin basic implementation" patch which appeared in review for two times already18:20
SergeyLukjanovDmitry, could you please explain us current state of unified agents discussions?18:20
*** yidclare has joined #openstack-meeting-alt18:20
mattfalazarev, will the plugin support EDP?18:21
ruheSergeyLukjanov, hehe, collapse thread of 100 emails in one message in IRC? :)18:21
mattfruhe, please!18:21
*** sarob has quit IRC18:21
mattfactually, make it a tweet18:21
dmitrymeSergeyLukjanov: there is huge diversity in opinions on several architectural items18:21
*** markmcclain has joined #openstack-meeting-alt18:22
alazarevmattf: current patch, as I see, doesn't support it18:22
dmitrymethat is the summary :-)18:22
*** RajeshMohan has quit IRC18:22
*** sarob has joined #openstack-meeting-alt18:22
mattfalazarev, yeah, wondering if you'll make it support EDP18:22
mattfdmitryme, lol18:22
alazarevmattf: let's have something merged at least and will see18:22
*** RajeshMohan has joined #openstack-meeting-alt18:22
mattfalazarev, is it a goal to support EDP in the IDH plugin by the icehouse release?18:22
SergeyLukjanovmattf, I hope yes18:23
mattf(if so, i pipe down and just come back closer to release and bark)18:23
alazarevmattf: the right answer I believe is "it depends"18:23
mattfoh but that makes me ask why it depends on18:24
mattfs/why/what18:24
alazarevone of the conditions is activity of Intel itself18:25
mattfare you signing up to maintain the plugin in savanna?18:25
* mattf is happy to take this over to #savanna so we can hit other topics18:26
*** bdpayne has quit IRC18:26
*** sarob has quit IRC18:26
alazarevthey allocated engineer to drive IDH plugin… but he fails to joins this meeting two weeks already18:26
mattfok18:27
alazarevso, I'm pessimistic on that18:27
* mattf nods18:27
mattflet's take it off to #savanna and free up the meeting18:27
*** bdpayne has joined #openstack-meeting-alt18:27
alazarevok18:28
SergeyLukjanovanything more to discuss today?18:28
*** IlyaE has quit IRC18:28
*** radix_ has joined #openstack-meeting-alt18:29
*** SlickNik has left #openstack-meeting-alt18:30
SergeyLukjanovok, let's the todays meeting18:30
SergeyLukjanovthank you guys18:30
SergeyLukjanovsee you in #savanna18:31
SergeyLukjanov#endmeeting18:31
*** openstack changes topic to " (Meeting topic: networking_policy)"18:31
ruhehappy holidays!!!18:31
aignatovbye18:31
openstackMeeting ended Thu Dec 19 18:31:05 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-12-19-18.05.html18:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-12-19-18.05.txt18:31
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-12-19-18.05.log.html18:31
mattfciao, have a great holiday!18:31
dmitrymebye18:31
*** mattf has left #openstack-meeting-alt18:31
*** IlyaE has joined #openstack-meeting-alt18:31
*** eankutse has joined #openstack-meeting-alt18:33
*** sarob has joined #openstack-meeting-alt18:34
*** yogesh has joined #openstack-meeting-alt18:34
*** gokrokve has quit IRC18:36
*** eankutse has quit IRC18:38
*** eankutse has joined #openstack-meeting-alt18:38
*** crobertsrh has left #openstack-meeting-alt18:39
*** rongze has joined #openstack-meeting-alt18:40
*** gokrokve has joined #openstack-meeting-alt18:41
*** jdbarry has quit IRC18:42
*** IlyaE has quit IRC18:45
*** yogesh has quit IRC18:45
*** rongze has quit IRC18:45
*** sarob has quit IRC18:46
*** sarob has joined #openstack-meeting-alt18:46
*** yogesh has joined #openstack-meeting-alt18:47
*** aignatov has quit IRC18:47
*** sarob has quit IRC18:51
*** sarob has joined #openstack-meeting-alt18:53
*** Barker has quit IRC18:56
*** yogesh has quit IRC18:58
*** banix has quit IRC18:58
*** yogesh has joined #openstack-meeting-alt18:58
*** Barker has joined #openstack-meeting-alt18:59
*** sarob has quit IRC19:01
*** yogesh has quit IRC19:01
*** markwash has quit IRC19:01
*** sarob has joined #openstack-meeting-alt19:01
*** rnirmal has quit IRC19:02
*** banix has joined #openstack-meeting-alt19:03
*** yogesh_ has joined #openstack-meeting-alt19:04
*** sarob_ has joined #openstack-meeting-alt19:05
*** sarob has quit IRC19:06
*** aignatov has joined #openstack-meeting-alt19:07
*** sarob_ has quit IRC19:09
*** sarob has joined #openstack-meeting-alt19:09
*** demorris has joined #openstack-meeting-alt19:10
*** kevinconway has joined #openstack-meeting-alt19:13
*** ruhe has quit IRC19:14
*** yogesh_ has quit IRC19:15
*** NehaV1 has quit IRC19:17
*** yogesh has joined #openstack-meeting-alt19:17
*** Barker has quit IRC19:19
*** akuznetsov has quit IRC19:20
*** jdob_ has joined #openstack-meeting-alt19:21
*** lsmola_ has quit IRC19:25
*** vkmc has quit IRC19:26
*** demorris_ has joined #openstack-meeting-alt19:27
*** demorris has quit IRC19:28
*** demorris_ is now known as demorris19:28
*** tedross has left #openstack-meeting-alt19:29
*** nadya_ has quit IRC19:30
*** sreshetnyak has quit IRC19:33
*** demorris has quit IRC19:37
*** jdob_ has quit IRC19:40
*** jdob has quit IRC19:40
*** jdob has joined #openstack-meeting-alt19:40
*** Barker has joined #openstack-meeting-alt19:40
*** demorris has joined #openstack-meeting-alt19:41
*** ativelkov has joined #openstack-meeting-alt19:43
*** sarob has quit IRC19:44
*** lblanchard has joined #openstack-meeting-alt19:46
*** ativelkov has quit IRC19:47
*** balajiiyer has quit IRC19:47
*** balajiiyer has joined #openstack-meeting-alt19:48
*** HenryG_ has quit IRC19:49
*** demorris_ has joined #openstack-meeting-alt20:01
*** demorris has quit IRC20:02
*** demorris_ is now known as demorris20:02
*** betsy has quit IRC20:02
*** dhellmann has joined #openstack-meeting-alt20:06
*** sarob has joined #openstack-meeting-alt20:08
*** banix has quit IRC20:14
*** dmitryme has quit IRC20:22
*** NehaV has joined #openstack-meeting-alt20:24
*** IlyaE has joined #openstack-meeting-alt20:28
*** NehaV has quit IRC20:31
*** NehaV has joined #openstack-meeting-alt20:31
*** balajiiyer has quit IRC20:32
*** zane1 has joined #openstack-meeting-alt20:41
*** Barker has quit IRC20:42
*** boris-42 has quit IRC20:47
*** aignatov has quit IRC20:48
*** zane1 has quit IRC20:49
*** zane has joined #openstack-meeting-alt20:50
*** boris-42 has joined #openstack-meeting-alt20:50
*** boris-42 has quit IRC20:52
*** alazarev has quit IRC20:53
*** alazarev has joined #openstack-meeting-alt20:54
sc68calLooks like networking_policy didn't end their meeting?20:54
sc68calor the topic got stuck20:55
*** aveiga has joined #openstack-meeting-alt20:57
*** Randy__ has joined #openstack-meeting-alt20:58
sc68calHello ipv6'ers20:59
Randy__Hi Sean20:59
aveigao/20:59
*** BrianB_ has joined #openstack-meeting-alt20:59
sc68calAgenda for today - https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_Dec_19_201320:59
sc68cal#startmeeting neutron_ipv621:00
openstackMeeting started Thu Dec 19 21:00:01 2013 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"21:00
openstackThe meeting name has been set to 'neutron_ipv6'21:00
sc68cal#topic housekeeping21:00
*** openstack changes topic to "housekeeping (Meeting topic: neutron_ipv6)"21:00
*** lblanchard has quit IRC21:00
sc68calSo next week is a holiday week for some, so we're going to skip next week21:00
sc68calThe other thing is that we're trying to figure out a good time so we can get the people from IBM in China to attend21:00
*** shshang has joined #openstack-meeting-alt21:01
sc68calSo everyone put in your 2c about the UTC time21:02
Randy__So do we need to move later21:02
Randy__?21:02
aveigaif we move later, the Europeans are out21:02
sc68caleither earlier or later, I think our current time has it at like 3AM or 4AM in china21:02
Randy__yes21:02
*** baoli has joined #openstack-meeting-alt21:02
aveigawhat about earlier?21:03
sc68calI floated the idea of 1500 UTC21:03
sc68calThat at least puts it in the range of approachable for China, although it's pretty late their time I think21:03
shshang1500 UTC is like 9am EST?21:04
Randy__yes, still late for them... could try for 1300 UTC??21:04
Randy__is that too early for you Sean ;-)21:04
sc68calRandy__: I'm willing to make sacrificies21:04
sc68cal*sacrifices21:04
aveiga1300 is 8AM EST, not that bad21:04
aveigaI'll make sure Sean's awake21:04
Randy__right21:04
sc68cal:)21:04
sc68cal#action sc68cal see if 1300 UTC works for everyone on the ML21:05
sc68cal#topic recap actions from previous meeting21:05
*** openstack changes topic to "recap actions from previous meeting (Meeting topic: neutron_ipv6)"21:05
sc68calijw: ping?21:05
*** dane has joined #openstack-meeting-alt21:05
*** ijw has joined #openstack-meeting-alt21:06
sc68calthere we go21:06
*** dmitryme has joined #openstack-meeting-alt21:06
sc68calijw: you had an action to write up a blueprint for your ideal networking  - is that google doc you created sort of part of that?21:06
Randy__I thought ijw said he might not make this call21:06
ijwYeah, the aim was to put that there and see what we already had.  I think I've changed my opinion anyway21:06
sc68calok - do you have the link handy?21:07
ijwSo I was saying that DHCPv6 would be the primary way of doing addressing because it's more general and SLAAC is very specific to /64s21:07
ijwBut I grant you with all the feedback (a) SLAAC is going to be easier to implement and (b) we need both anyway21:07
sc68cal#link https://docs.google.com/document/d/1rOBOOu_OwixMStm6XJOb5PKkJA6eFbL_XCE7wlTfaPY/edit IPv6 addressing and routing in Openstack21:08
ijwAside that, the doc lists in the first section the things we need - in terms of features, not implementations - and in the second section the APIs.  I've tried to avoid implementation details in there completely.  I'm working forward from what we need because it felt like everyone so far had gone with 'here's the code, what's the minimum we can do to make something work' and I wanted to make sure we'd covered everything21:08
sc68calcool - we'll let people look over it and add feedback21:09
Randy__sc68cal: I believe some of the subsequent agenda items might address some of these areas21:09
ijwAnyway, my take is that we want RAs from routers (with a degree of configuration) *and* DHCPv6, indepdendently, and in the DHCPv6 namespace as now.  And we don't want them to all be tied back to a single config keyword on subnets, necessarily, because even if RAs are doing addressing there may be reasons to have a DHCP server21:10
sc68calRandy__: agreed - we'll probably cover it in depth when we get to the blueprint topic21:10
sc68calSo for me - I registered two blueprints for the VIF hairpin attribute21:10
aveigaijw: +1, for cases of no RFC 6106 support in the client but a desire for SLAAC21:10
sc68cal#link https://blueprints.launchpad.net/nova/+spec/nova-hairpin-vif-attribute Nova VIF hairpin attribute BP21:11
ijwThat approach is only a little different from Randy__'s POC - he moved dnsmasq, I'm saying we should duplicate it21:11
sc68cal#link https://blueprints.launchpad.net/neutron/+spec/vif-attribute-for-hairpinning Neutron VIF attribute21:11
sc68cal#topic blueprints21:11
*** openstack changes topic to "blueprints (Meeting topic: neutron_ipv6)"21:11
sc68calOk - have at it folks :)21:11
sc68calknow people have some stuff to hash out on the v6 modes21:12
ijwRight, let's start with those two - there's nothing controversial there, I think we're just trying to make this easy for the Nova guys to see we're not breaking things21:12
aveigaanyone have any qualms with the VIF hairpinning BPs?21:13
aveigaif not, we could move on21:13
*** sarob has quit IRC21:13
shshangis this tied to the issue we had before?21:13
aveigashshang: yes, this is to address the DADFAILED issue21:13
shshangI thought it has been fixed...no?21:14
aveigawell, it was21:14
ijwYeah, keeps coming up - it's just a problem to commit cos we have to get it past Nova reviewers who like the status quo21:14
aveigabut the patch sc68cal proposed was rejected21:14
shshangI see.21:14
aveigathey wanted it changed per VIF by Neutron21:14
shshangI am fine with that BP21:14
aveigahence those BPs21:14
Randy__+1 for me21:14
aveigasounds like consensus to me21:14
ijwFirst is sc68cal's and I'll do the second21:15
sc68calijw: you want the neutron one or the nova one?21:15
ijwNeutrojn21:15
sc68calk21:15
ijwYou have a patch out in nova, you might as well just tweak it21:15
sc68cal#action sc68cal assign ijw to neutron vif blueprint21:15
ijwThe right people are watching it already21:15
sc68calcool.21:15
*** vipul is now known as vipul-away21:16
ijwAddressing modes?21:16
sc68calsounds good to me - that's related to the new BPs that were just registered?21:17
*** eankutse has quit IRC21:17
sc68cal#link https://blueprints.launchpad.net/neutron/+spec/dnsmasq-ipv6-dhcpv6-stateful dnsmasq stateful21:17
*** gokrokve has quit IRC21:17
shshangso Randy and I submitted a couple of new BPs21:17
shshangThe support of SLAAC mode is not new.21:17
*** gokrokve has joined #openstack-meeting-alt21:18
shshangWe discussed it before, and we have beta code available21:18
ijwI think shshang and Randy's proposals tend towards using dnsmasq and using one process to do both RA and DHCP, right?21:18
shshangyes21:18
Randy__yes21:18
aveigaI have a question there21:18
aveigaand note that I'm not arguing that there's anything wrong with using dnsmasq21:18
shshangthe next several BP intents to bridge the gap on DHCPv6 side21:18
aveigabut why run dnsmasq if you're only doing slaac?21:18
aveiga(just playing devil's advocate)21:19
shshangFor DHCPv6, there are several modes21:19
shshangDHCPv6 stateful, DHCPv6 stateless21:19
ijwWhich is basically address-and-info and info-only, right?21:20
shshangthe new BPs try to bridge the gap on DHCPv6 side, so eventually, we have complete solution around dnsmasq to support SLAAC, DHCPv6 Stateufl, and DHCPv6 stateless21:20
aveigaijw: yes21:20
shshang@ijw, yes21:20
shshangany questions?21:20
ijwSo I would prefer to break the problem into two, if we could21:20
ijwRAs on the one side and DHCPv6 on the other21:20
shshangnope21:21
ijwI'm a bit concerned that having one dnsmasq in the router namespace has problems21:21
shshangThat is the wrong way to look at the problem.21:21
ijwNot least that networks don't always have routers, for starters21:21
shshangAll three modes needs RA21:21
*** vipul-away is now known as vipul21:21
shshangI think a lot of people have that confusion21:21
aveigashshang: don't look at it from that persepctive.  Look at it that not all modes need dhcpv621:21
*** gokrokve has quit IRC21:21
shshang@aveiga, not sure what you mean21:22
aveigathere's no disagreement that all nodes need an RA21:22
aveigabut a purely slaac mode doesn't need dnsmasq21:22
ijwaveiga: I think from that perspective it's more that dnsmasq does do DHCPv6 but it's often disabled in shshang's model21:22
shshang@aveiga, you mixed several things together21:22
shshangthe dnsmasq is just an implementation of IPv6 address assignement21:22
shshangFrom IPv6 concept perspective, you have 3 modes21:23
aveigaactually, you have 421:23
shshangSLAAC, DHCPv6 Stateful, DHCPv6 Stateless21:23
aveigadon't leave out static21:23
ijwWell, in this case, 'off'21:23
aveigai.e. cloud-init injeceted21:23
shshangyes21:23
shshangstatic means, no autoconfiguration21:23
ijwYeah, that's not mutually exclusive with the above, so from a net config perspective it's really just 'off'21:23
shshangyup21:24
aveigahold on though21:24
aveigait might still want an RA21:24
aveigabecause remember, RAs configure default routes21:24
ijwaveiga: you have a twisty mind21:24
aveigaI've been doing IPv6 for almost 8 years21:24
aveigait twists you21:24
shshangRA only configures default route in AUTOCONFIGURATION setting21:24
aveigashadower: not true21:24
aveigayou can have a prefix, marked on-link, with A=0 and M=0 and still inject the route21:25
aveigasorry shadower, silly autocomplete21:25
shshangI can now configure my ubuntu VM manaully with IPv6 address and default gateway, if that is the "static" mode you refer to21:25
aveiganope21:25
aveigaI am referring to having neutron pick the VM address, and confuigure the VM via cloud-init on boot21:25
shshangOh, I see21:26
shshangI misunderstood you21:26
aveigayeah21:26
shshangThat is not what the BPs are for21:26
aveigathat's why you need to decouple RAs and Address assignment21:26
ijwYou see, if you divide this down the middle, for any router you want RA+SLAAC, RA without SLAAC and off.  And for DHCPv6 you want DHCP+address, DHCP without address, and off.  But shshang, you were making a point about RAs being necessary?21:26
shshangFor the "static" mode as referred by aveiga, it is not the cases covered by the BPs we submitted21:27
shshangI agree with aveiga, that is another viable way21:28
ijwIndeed, I think it's something we can leave out of the discussion really, short of saying we might want no chatter at all on the network21:28
aveigashshang: yup, and I guess I should propose a BP for injected and non-configured modes21:28
sc68cal+121:28
shshangaveiga, agreed your suggestion21:28
aveigaBUT21:28
ijwYou'll find the cloud-init stuff could use a serious rework on addressing actually, there be dragons21:28
aveigathe reason I bring that up is because it really does decouple the RA from address assignment21:28
aveigaijw: I think it should still be the same algo as the SLAAC addr, but that's another conversation I'd like to avoid today21:29
ijwNo, that makes a lot of sense to me21:29
*** dmitryme has quit IRC21:29
sc68calaveiga: There's already a tempest scenario that is in review for static injection21:29
ijwConfigurable addresses, if they are really needed, come last.21:29
*** jjmb1 has joined #openstack-meeting-alt21:29
sc68calaveiga: we should probably keep an eye on it21:29
aveiga+121:29
shshangso, for the 3 BPs we submitted, our goal is to cover autoconfiguration21:29
sc68cal#link https://review.openstack.org/#/c/58721/ IPv6 injection scenario testcase21:30
ijwsc68cal: it sucks as an implementation but it demonstrates you can get hold of the data in the right place and that's what the test needs to do now21:30
sc68calijw: agreed21:30
shshangany objections?21:30
ijwyes21:30
shshangreason?21:30
aveigashshang: I think the thing I'm driving at is why run dnsmasq as an RA daemon21:30
*** vkmc has joined #openstack-meeting-alt21:30
shshangwhy not?21:30
aveigait's not a router21:31
aveigaand in cases where you don't want autoconfiguration but still need an RA21:31
aveigayou need something else21:31
ijwAnd mine is that if you use one daemon in the router namespace for everything then unrouted networks break21:31
*** jjmb has quit IRC21:31
shshangaveiga, would u plz elaborate?21:31
aveigaI think the core is that dnsmasq only has an RA daemon becuase of it's use in OpenWRT and other projects21:31
aveigawhere it's also a router21:31
aveigain the case here where the address assignment is literally decoupled ala namespaces21:32
ijwaveiga: I thought the point here is that dnsmasq can be configured to do RAs and nothing else?21:32
shshangdnsmasq can send RA, and it can act as DHCPv6 server21:32
sc68calaveiga: ijw: the one thing that we need to be concerned with is that there is no API in Neutron for orchestrating rtadvd - which means more work21:32
*** abramley has quit IRC21:32
aveigawhich is true21:32
ijwNo, I think we're into implementation without the abstraction21:32
shshangI am still not sure which use case you refer to?21:32
ijwdnsmasq, radvd, seriously don't care21:33
aveigaand I'm not saying that we can't run dnsmasq as RA daemon21:33
aveigaI'm justs driving at the reasons we should do that21:33
shshangaveiga, would u plz give me a use case?21:33
aveigabecause you then couple assignment with routing21:33
aveigashshang: slaac21:33
shshang?21:33
aveigabesides issuing just an RA21:33
aveigadnsmasq has no other purpose21:34
aveigain that use case21:34
shshangwhat else do you want to issue besides RA in SLAAC mode?21:34
aveiganothing21:34
aveigabut Ian is poointing out the opposite problem21:34
aveigaa non-routed tenant-only network21:34
aveigaputting dnsmasq on the router namespace there is impossible, because none exists21:35
aveigathere's no router21:35
shshangOK, let me recap what you want21:35
shshangin non-routed tenant-only network, there is no tenant router, and you still want RA, right?21:35
ijwNo21:35
ijwDHCP21:35
aveigathat's the tricky part21:36
aveigahow do you start dhcpv6 without an RA?21:36
aveigayou don't21:36
shshangHow are about this, tell me the use case, and tell me what you want to achieve21:36
shshangin the concise way21:36
shshangI think you mentioned several scenarios21:37
Randy__guys. the only reason to really have dnsmasq in the qrouter namespace was to provide a default gateway since qdhcp namespace can't do this.21:37
shshangDon't tell me what you don't want, tell me what you want21:37
*** cody-somerville has joined #openstack-meeting-alt21:37
*** cody-somerville has quit IRC21:37
*** cody-somerville has joined #openstack-meeting-alt21:37
Randy__or it can, but obviously won't work for the tenant21:37
ijwshshang: specifically, I think I would want to have a private network between a webapp server and a DB server with no route to the world21:38
*** gokrokve has joined #openstack-meeting-alt21:38
shshangPlus, let us stick to the use case aveiga mentioned: "non-routed tenant-only network w/o tenant router"21:38
*** jjmb1 has quit IRC21:38
aveigashshang: what ijw just proposed is exactly that use case21:38
shshangOK, in that case, webapp and DB server is in the same subnet, right?21:39
baoliCan you turn on ipv6 on dnsmasq that is runing on the tenant's subnet?21:39
shshangno router, right?21:39
aveigacorrect on both21:39
Randy__so if no router, then no qr-interfaces21:39
shshangok, if you don't want route to external world, then I assume you don't want RA either, right?21:39
aveigabaoli: we don't run like that in neutron.  A separate dnsmasq is spun up per IP pool (ipv4, ipv6, etc)21:39
ijwnope21:39
aveigabut how do you intend to use dhcpv6 without an RA?21:40
aveigawithout the M and O bits, nothing sill ever solicit21:40
baolia separate dnsmasq per network actually.21:40
shshangAnswer my question, if you don't want route to external world, do you still need RA?21:40
ijwNope21:40
aveigaijw yes, you do21:40
ijw...21:41
aveigahow do you initiate a solicit?21:41
shshangijw, and aveiga, can two of you sync up first and get onto the same page?21:41
ijwRIght, I'll correct myself.  I don't need a *route*.21:41
aveigacorrect21:41
ijwProtocolwise I defer to aveiga21:41
aveigabut you still need the RA message for dhcpv6 to work21:41
*** pballand has quit IRC21:42
shshangSo you don't need default route, and you still want DHCPv6, right?21:42
aveigashshang: to be exactly precise, we need an RA with M and possibly O set, but the RA must not be on-link21:42
aveigawhich means tell the host to do dhcpv6, but do not install a route21:43
shshangOh, I see.21:43
aveigayeah, so we have to be careful about blanket stating what an RA does21:44
aveigathey aren't 100% decoupled21:44
aveigaso I MOSTLY agree with your 3 mode blueprints21:44
shshangIn this case, you just create subnet, and network, but not creating router. Is that correct?21:44
aveigawith the exception that we need to not make it a default to put dnsmasq in the qrouter namespace21:45
aveigaand we should maybe provide some mode where the dnsmasq instances is told "there's no router here"21:45
shshangYes21:45
shshangNow I see the use case,21:45
aveiga*phew*21:45
aveigasorry to drive you in circles, but it was a potentially breaking scenario21:46
shshangyes, agree with you, in that case, there won't be qrouter namespace, but qdhcp namespaece still exist21:46
ijwIf you're used to routers, having no router is certainly a bit odd21:46
*** SergeyLukjanov has quit IRC21:46
*** jdob has quit IRC21:46
shshangnononon...it is all good21:46
aveigayup, and we need to issue a non-onlink RA21:46
aveigain that one specific case21:46
aveigabut remember, that's not an abnormal thing to do21:46
shshangNo, it is fine, we can add a simple check to see whether qrouter- namespace even exist21:46
ijwDoesn't work21:46
ijwI can attach a router later21:47
shshangif qrouter- namespace and qg- interface don't exist, then use qdhcp- namespace21:47
ijw(from an API perspective I can.  God only knows what it means.)21:47
aveigaijw: that router should then issue an RA for the subnet though21:47
aveigaassuming an address already exists on the host, it should only install the route21:47
aveigawhich it never had before, because no on-link RAs were present21:47
sc68calyeah they'd need to update the subnet via the API to set a gateway, when you add the router (If it doesn't already do that when you create the router)21:48
aveigathat should, *in theory* still be OK21:48
sc68calit might do it as part of the router creation op21:48
aveigaif you want to be doubly sure, we could issue a message to cause the dnsmasq config to change21:48
shshangaveiga, I don't want to go into tooo much implementation details now, but I think I get your use case. But if we add a checkpoint, do you think it will work?21:48
aveigaand stop sending RAs21:48
aveigashshang: I think we need a flag21:48
shshangyes21:48
aveigaboolean, is_router_present21:48
shshangyes21:48
shshangI agree21:48
shshangI will add enhancement to the BP to call out this case21:49
ijwI'm still going to ask, is there any reason to go moving the daemon from the dhcp to the router namespace, or is it simpler to just use two?21:49
aveigaok21:49
shshangbut aveiga, thanks for bringing it up21:49
shshangit is an interesting use case21:49
aveigaand that's exactly why I asked about running an RA from the router, in its own daemon21:49
sc68calThe flag might be able to just do a query to the neutron DB for the presence of a router attached to the subnet or network21:49
aveigaeven if said daemon is another copy of dnsmasq21:49
sc68calor just query out the ports for a network, look for the device owner to be a router21:50
Randy__ijw: you need the qrouter instance of dnsmasq for cases where you want to provide a default gateway21:50
*** xyang1 has quit IRC21:50
aveigaI think thay should split21:50
ijwRandy__: yup - that's what I mean about two - granted you can't avoid the router daemon21:50
aveigaand the qdhcp instance should only ever issue an RA when a) RA is no on-link and b) the RA is only present when there is no router21:51
Randy__yes, the qdhcp namespace instance remains intact21:51
aveigaotherwise, the other daemon running in the qrouter namespace runs the RA21:51
Randy__aveiga: yes21:51
*** roeyc has joined #openstack-meeting-alt21:51
sc68cal#action shshang add a blueprint to cover a tenant network with no router21:51
sc68calshshang: does that sound right?21:51
sc68calor should I rope in aveiga and ijw to help21:51
shshangI think aveiga explained it clearly21:51
aveigaI don't want to dictate implementation, but it seems to me that we need the RA to be discrete from the dhcpv6 server21:52
*** jbrendel has joined #openstack-meeting-alt21:52
ijwActually I think aveiga would be better for this21:52
aveigaexcept for the no_routers case21:52
sc68cal#undo21:52
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x390fa10>21:52
*** hichihara has joined #openstack-meeting-alt21:52
sc68calLet me know how to word the action, so we can file it then do open discussion21:53
aveigaalso, assign me one to define the RA cases and the desire for a separate RA daemon21:53
sc68cal#action aveiga define RA cases and the desire for a separate RA daemon21:53
shshangthe assumption here is, if we have qrouter, then we assume we have default gw, hence RA should be from qrouter- namespace and it should have privilege; if we don't have qrouter, then it is non-router case and dnsmasq in qdhcp namespace should send RA21:53
aveigauh, is everyone OK with a slight delay here? I'm going on PTO for medical and family reasons starting Saturday21:53
shshangis my statement accurate?21:53
shshangI mean, the assumption here?21:54
aveigashshang: be specific though, the qrouter has to be on the same subnet21:54
sc68calsounds correct to me21:54
aveigaas opposed to a shared public network and a private tenant network on the same machine21:54
ijwYep - the only thing I would add is, does it actually matter where DHCP comes from if we have DHCP or should we just use the DHCP NS for that all the time?21:54
aveigahence why I think there should be a flag21:54
shshangaveiga, correct21:54
aveigaijw: for the sake of not breaking ops folks troubleshooting this, reduce disparity with the v4 model where possible21:55
aveigahence, leave it in qdhcp21:55
aveigaand leave the routing functions in qrouter21:55
ijwNow, the reason I like that is nothing to do with the DHCP one but that we again come down to the nice simple solution 'routers send RAs' - we need a daemon there that respects attached subnets' flags and does very boring things21:55
aveigayup21:56
*** hemanthravi has joined #openstack-meeting-alt21:56
*** shivh has joined #openstack-meeting-alt21:56
aveigarouting routes and addressign assigns addresses21:56
aveigaand we're out of time21:56
aveigasorry to hijack the meeting21:56
shshangOK, this is good discussion21:56
shshangno no no, aveiga, it is ALL good21:56
sc68calyeah let's just open it for the last few minutes21:56
shshangI like this kind of brainstomr,21:56
sc68cal#topic open discussion21:56
*** openstack changes topic to "open discussion (Meeting topic: neutron_ipv6)"21:56
shshangNow I can see the use case you are thinking21:57
*** Barker has joined #openstack-meeting-alt21:57
ijwIn practice there's only so much work we'll get done in a 'week' and we've just carved some of it off.21:57
sc68calI apologize for running through the first 15 minutes of the meeking super quick - but I knew this discussion was probably going to take the bulk of the time21:57
ijwSo shshang, do you have some code that could do that?  Sounds like what you have - using dnsmasq, probably, but who cares - could spit RAs21:57
shshangsorry, ijw, what do you refer to?21:58
ijwRAs from routers per above21:58
shshangyes21:58
aveigarunning two dnsmasqs, one for addressing and one for RA21:58
ijwIgnoring DHCP for now, we can add that in a later round21:58
ijwSo I would suggest we do the thing we need in the qrouter NS, we leave the old DHCP NS there (for v4 only, for now) and call that a job21:59
aveigaI think we're pretty well wrapped up21:59
Randy__this is what has been done21:59
*** songole has joined #openstack-meeting-alt21:59
ijwRandy__: thought so, but the thing is it has much fewer modes now - RA-slaac, RA-noslaac and off21:59
aveigasc68cal: I think you should adjourn22:00
aveigawe're over22:00
*** luqas has joined #openstack-meeting-alt22:00
sc68calhmm - is my clock slow?22:00
*** sarob has joined #openstack-meeting-alt22:00
aveigaI'm reading 220022:00
sc68calsame22:00
shshangaveiga,22:00
sc68cal#endmeeting22:00
*** openstack changes topic to " (Meeting topic: networking_policy)"22:00
openstackMeeting ended Thu Dec 19 22:00:34 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-12-19-21.00.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-12-19-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-12-19-21.00.log.html22:00
ijwto #openstack-neutron, chaps22:00
mesteryHi! Who's here for the Neutron 3rd party testing meeting?22:00
* ijw flees22:01
*** shshang has quit IRC22:01
* sc68cal flees too22:01
*** Randy__ has quit IRC22:01
* mestery chases after sc68cal and ijw.22:01
sc68cal;)22:01
jbrendelHi there...22:01
luqasHI, me, I 'm a new qa guy at Midokura22:01
mesteryjbrendel: Howdy!22:01
aveigahave fun, folks, and remember to include IPv6 in your testing!22:01
mesteryluqas: Welcome!22:01
* aveiga ducks22:01
mesteryaveiga: Of course. :)22:01
luqasso I take the place of Rossella :-)22:01
*** shivharis has joined #openstack-meeting-alt22:01
mestery#startmeeting networking_third_party_testing22:01
openstackMeeting started Thu Dec 19 22:01:48 2013 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: networking_third_party_testing)"22:01
openstackThe meeting name has been set to 'networking_third_party_testing'22:01
shivharishi all22:01
*** aveiga has left #openstack-meeting-alt22:02
roeycHi22:02
hichiharaHi22:02
yamahatahi22:02
mestery#link https://etherpad.openstack.org/p/multi-node-neutron-tempest Shared Etherpad for 3rd Party Testing and Multi-Node Tempest Testing22:02
*** oda-g has joined #openstack-meeting-alt22:02
mesterygongysh amotoki, you guys here?22:02
mesteryOK, so lets get started, myabe this will be quick this week.22:03
mesteryI guess lets just start with the obivous: Where are people at with regards to Neutron 3rd party testing?22:03
mesteryDoes anyone have a full voting Tempest setup up and (partially) working yet?22:04
shivharispartially working ...22:04
luqaspartially too22:04
roeycsame here22:04
*** Sourabh has joined #openstack-meeting-alt22:04
mesteryGreat! What issues have you guys faced in this so far?22:04
shivharisJenkins seems not too flexible22:04
mesteryshivharis: In what way?22:04
shivharisI have issues with patchset ID22:05
shivharisThe patchset id is the the code that need to be tested22:05
mesteryshivharis: I see you put that on the wiki. Perhaps we can collect those there and ask someone from -qa for help with an email to openstack-dev?22:05
* mestery nods.22:05
shivharisnot the one at the top of the branch22:05
shivharisI want to add the broad step there; can some take a look and see if that is what need to be done. (very broad)22:06
mesterySo you can get the top of hte branch patchset ID, but not the one from the gerrit review itself?22:06
shivharisThe event posted by the patchset Id need to be derived somehow. having toruble with that22:07
*** HenryG has joined #openstack-meeting-alt22:07
shivharisto be precise gerrit posts and event and that event has the patchset id22:07
mesteryshivharis: Can you ping someone in -qa or email openstack-dev? Also, whatever you find out, put it in the wiki.22:07
*** pcm_ has joined #openstack-meeting-alt22:07
shivharisOk willdo.22:08
shivhariscan folks see the etherpad and agree on the broad steps, just posted to etherpad22:08
mestery#action shivharis to figure out patchset ID issue and report back on etherpad with fix.22:08
mesteryshivharis: At the bottom?22:08
shivharisyes22:08
*** pcm_ has quit IRC22:09
*** pdmars has quit IRC22:09
mesteryshuvharis: How much of what you've put there is covered by these instructions: http://ci.openstack.org/running-your-own.html22:09
*** julim has quit IRC22:09
shivharisnot much..22:09
mestery:)22:09
*** pcm_ has joined #openstack-meeting-alt22:10
mesterySo, I think the general flow of what you're trying to do is right shivharis.22:10
shivharisDo we have to do this with Jenkins, can we do another way?22:10
jbrendelI think you can manually read the Gerrit event stream.22:11
mesteryshivharis: You can do this anyway you want, but I was thinking using Jenkins would be easier, perhaps it's not.22:11
mesteryjbrendel: Is that what you're doing, skipping some of this infra?22:11
jbrendelI've heard the Jenkins plugin takes care of a lot of issues (such as making test results available to upstream).22:11
shivharisI found jenkins is not flexible enough. Had more success reading the event stream.22:11
jbrendelHaven't implemented that yet, though, so can't be sure.22:12
mesteryjbrendel: Agreed, if it takes care of some details, I think it's the way to go quite honestly,.22:12
jbrendel#shivharis: Interesting. Reading the event stream itself shouldn't be too difficult, but are there other benefits to using Jenkins?22:12
*** tinoue_ has joined #openstack-meeting-alt22:13
*** sarob has quit IRC22:13
shivhariswithout jenkins, posting results is quite easy as well22:14
*** sarob has joined #openstack-meeting-alt22:14
luqasshivaris: yes but you have to do it manually...22:14
shivharisnothing can be manual.22:15
shivharisit has to run anytime and event is posted.22:16
shivhariss/and/an/22:16
jbrendelOk, what does the Jenkins plugin give you?22:16
jbrendelMaybe "manual" here referred to "having to implement some mechanism yourself" vs. "letting the plugin do it"?22:16
luqasthe ability to run tests and post the results?22:17
*** sarob has quit IRC22:17
mesteryluqas: Agreed, I thought that's what it got us, does it not?22:17
shivharisI have limited Jenkins knowledge. need some pointers/folks I can talk to22:17
*** sarob has joined #openstack-meeting-alt22:17
mesteryshivharis: The best place is to talk to folks in #openstack-qa, they can give guidance there, or on the mailing list.22:18
mesteryI suspect a lot of people listening here have minimal Jenkins experience as well.22:18
*** jcooley_ has joined #openstack-meeting-alt22:19
shivharisActually runnings tests is minor. We need the right code, from the correct branch and them applying patchset, then testing22:19
shivharisbranch is "stable/grizzly", ... "master"22:19
mesteryCan anyone verify that is  what the jenkins plugin actually helps with?22:20
mesteryOK, so if people look near hte bottom of the shared etherpad, you can see some info on how hte QA team has suggested we all sedt this up.22:22
mesteryThe part about "Use Infrastructure for Testing"22:23
mesteryI suggest we take a look at that and see how far it gets us, and we can reconvene the week after next, on January 2.22:23
mesteryUnless anyone has anything else today?22:23
shivharisI can talk to #openstack-qa and get back22:24
mesteryThanks shivharis.22:24
mesteryOK, so lets proceed with this plan then.22:24
luqasi got a question regarding who's responsible for the third party testing of ODP22:24
mesteryluqas: OpenDaylight?22:24
luqasif any22:25
mesteryluqas: I am working with the Linux Foundation on that, we're stuck getting VMs for that. So I guess you could say I'm sheparding that at the moment.22:25
mesteryrosella was interested in helping there, is she still?22:25
luqasok, so I will talk to you offline :-)22:25
*** songole has quit IRC22:25
mesteryok, thanks.22:25
luqasyes I guess22:25
mesteryOK, well happy holidays everyone and we'll see you in the new year!22:26
luqasmerry xmas!22:26
mesteryQuestions or issues before then, please ping -neutron -qa on IRC or send email to openstack-dev with "[neutron] [third-party-testing]" in the subject!22:26
mestery#endmeeting22:26
*** openstack changes topic to " (Meeting topic: networking_policy)"22:26
openstackMeeting ended Thu Dec 19 22:26:27 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/networking_third_party_testing.2013-12-19-22.01.html22:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/networking_third_party_testing.2013-12-19-22.01.txt22:26
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2013/networking_third_party_testing.2013-12-19-22.01.log.html22:26
*** jbrendel has quit IRC22:26
shivharisbye22:26
*** shivharis has quit IRC22:27
*** dane has quit IRC22:27
*** roeyc has quit IRC22:27
*** Sourabh has quit IRC22:27
*** esker has quit IRC22:29
*** gokrokve has quit IRC22:29
*** hichihara has left #openstack-meeting-alt22:29
*** gokrokve has joined #openstack-meeting-alt22:30
*** luqas has quit IRC22:31
*** oda-g has quit IRC22:32
*** gokrokve has quit IRC22:34
*** zane has quit IRC22:34
*** betsy has joined #openstack-meeting-alt22:35
*** yamahata has quit IRC22:37
*** denis_makogon has quit IRC22:37
*** hemanthravi has quit IRC22:38
*** nati_ueno has joined #openstack-meeting-alt22:38
*** glucas has quit IRC22:41
*** zane has joined #openstack-meeting-alt22:41
*** glucas has joined #openstack-meeting-alt22:42
*** tinoue_ has quit IRC22:43
*** baoli has quit IRC22:43
*** safchain has quit IRC22:48
*** gokrokve has joined #openstack-meeting-alt22:49
*** arnaud__ has quit IRC22:54
*** arnaud has quit IRC22:54
*** gokrokve has quit IRC22:54
*** vipul is now known as vipul-away22:56
*** arnaud__ has joined #openstack-meeting-alt22:56
*** arnaud has joined #openstack-meeting-alt22:56
*** flaper87 is now known as flaper87|afk23:00
*** shivh has quit IRC23:03
*** karthik has joined #openstack-meeting-alt23:09
*** yogesh has quit IRC23:10
*** harlowja is now known as harlowja_away23:12
*** kevinconway has quit IRC23:14
*** karthik has quit IRC23:15
*** jmontemayor has quit IRC23:22
*** markvoelker1 has joined #openstack-meeting-alt23:30
*** sacharya has quit IRC23:32
*** sarob has quit IRC23:33
*** shivh has joined #openstack-meeting-alt23:33
*** nati_uen_ has joined #openstack-meeting-alt23:34
*** nati_uen_ has quit IRC23:34
*** nati_uen_ has joined #openstack-meeting-alt23:35
*** sarob has joined #openstack-meeting-alt23:35
*** shivh has quit IRC23:36
*** nati_ueno has quit IRC23:37
*** NehaV has quit IRC23:41
*** BrianB_ has quit IRC23:43
*** rongze has joined #openstack-meeting-alt23:43
*** brents has joined #openstack-meeting-alt23:47
*** rongze has quit IRC23:48
*** Barker has quit IRC23:49
*** demorris has quit IRC23:55
*** arnaud__ has quit IRC23:55
*** arnaud has quit IRC23:55
*** harlowja_away is now known as harlowja23:57
*** dprince has quit IRC23:59
*** gokrokve has joined #openstack-meeting-alt23:59
*** yamahata has joined #openstack-meeting-alt23:59

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