Tuesday, 2014-02-04

*** boris-42_ has quit IRC00:03
*** ekarlso- has joined #openstack-meeting00:04
*** markpeek has quit IRC00:04
*** Mandell has quit IRC00:06
*** markwash has joined #openstack-meeting00:06
*** banix has quit IRC00:06
*** boris-4__ has quit IRC00:07
*** gokrokve has joined #openstack-meeting00:09
*** yamahata has joined #openstack-meeting00:10
*** marun has joined #openstack-meeting00:10
*** Leonr has quit IRC00:11
*** matsuhashi has joined #openstack-meeting00:12
*** doug_shelley66 has quit IRC00:12
*** marun has quit IRC00:15
*** alexpilotti has quit IRC00:15
*** ivar-lazzaro_ has quit IRC00:15
*** IanGovett has quit IRC00:16
*** david-lyle has quit IRC00:16
*** thuc has quit IRC00:18
*** thuc has joined #openstack-meeting00:19
*** david-lyle has joined #openstack-meeting00:20
*** eharney has quit IRC00:20
*** Mandell has joined #openstack-meeting00:20
*** cdub has joined #openstack-meeting00:22
*** thuc has quit IRC00:23
*** dcramer_ has joined #openstack-meeting00:25
*** jaypipes has quit IRC00:27
*** sacharya has joined #openstack-meeting00:27
*** yamahata has quit IRC00:29
*** mikal_ is now known as mikal00:29
*** jaypipes has joined #openstack-meeting00:32
*** nosnos has joined #openstack-meeting00:33
*** yamahata has joined #openstack-meeting00:33
*** terriyu has joined #openstack-meeting00:39
*** terriyu has quit IRC00:39
*** masayukig has joined #openstack-meeting00:39
*** thuc has joined #openstack-meeting00:39
*** armax has joined #openstack-meeting00:40
*** yamahata has quit IRC00:43
*** nosnos_ has joined #openstack-meeting00:44
*** masayukig has quit IRC00:44
*** nosnos has quit IRC00:47
*** alexpilotti has joined #openstack-meeting00:47
*** asalkeld has quit IRC00:48
*** markpeek has joined #openstack-meeting00:48
*** yamahata has joined #openstack-meeting00:48
*** oubiwann_ has joined #openstack-meeting00:48
*** ekarlso has quit IRC00:50
*** alexpilotti has quit IRC00:51
*** dcramer_ has quit IRC00:51
*** weshay has joined #openstack-meeting00:52
*** Tross has quit IRC00:53
*** nosnos_ has quit IRC00:54
*** nosnos has joined #openstack-meeting00:54
*** gokrokve has quit IRC00:55
*** david_lyle_ has joined #openstack-meeting00:55
*** Tross has joined #openstack-meeting00:55
*** gyee has quit IRC00:59
*** david-lyle has quit IRC00:59
*** mrodden has quit IRC01:00
*** dcramer_ has joined #openstack-meeting01:03
*** atiwari has quit IRC01:03
*** asalkeld has joined #openstack-meeting01:08
*** thuc has quit IRC01:10
*** thuc has joined #openstack-meeting01:10
*** elo1 has quit IRC01:11
*** Mandell has quit IRC01:11
*** otherwiseguy has joined #openstack-meeting01:12
*** Mandell has joined #openstack-meeting01:12
*** lblanchard has joined #openstack-meeting01:12
*** dzimine has joined #openstack-meeting01:13
*** colinmcnamara has quit IRC01:13
*** asalkeld has quit IRC01:14
*** asalkeld has joined #openstack-meeting01:14
*** thuc has quit IRC01:14
*** mrodden has joined #openstack-meeting01:15
*** comay has joined #openstack-meeting01:24
*** amcrn has quit IRC01:24
*** mestery has joined #openstack-meeting01:25
*** colinmcnamara has joined #openstack-meeting01:25
*** mestery has quit IRC01:26
*** sarob has quit IRC01:26
*** mestery has joined #openstack-meeting01:26
*** dzimine has quit IRC01:26
*** marun has joined #openstack-meeting01:28
*** asalkeld has quit IRC01:31
*** marun has quit IRC01:33
*** marcoemorais1 has quit IRC01:38
*** masayukig has joined #openstack-meeting01:40
*** david-lyle has joined #openstack-meeting01:40
*** colinmcnamara has quit IRC01:43
*** david_lyle_ has quit IRC01:44
*** rossk has quit IRC01:44
*** masayukig has quit IRC01:45
*** asalkeld has joined #openstack-meeting01:45
*** ryanpetrello has quit IRC01:46
*** mestery has quit IRC01:47
*** gokrokve has joined #openstack-meeting01:47
*** MaxV has joined #openstack-meeting01:49
*** doug_shelley66 has joined #openstack-meeting01:49
*** sandywalsh_ has quit IRC01:50
*** ken1ohmichi has joined #openstack-meeting01:50
*** jecarey has joined #openstack-meeting01:50
*** stevemar2 is now known as stevemar01:52
*** MaxV has quit IRC01:54
*** markmcclain1 has joined #openstack-meeting01:54
*** markmcclain has quit IRC01:54
*** markmcclain1 has quit IRC01:56
*** banix has joined #openstack-meeting01:59
*** nati_uen_ has joined #openstack-meeting01:59
*** nati_uen_ has quit IRC01:59
*** gokrokve has quit IRC02:00
*** nati_uen_ has joined #openstack-meeting02:00
*** markmcclain has joined #openstack-meeting02:01
*** baoli has joined #openstack-meeting02:01
*** crandquist has quit IRC02:02
*** nati_ueno has quit IRC02:02
*** ryanpetrello has joined #openstack-meeting02:02
*** gokrokve has joined #openstack-meeting02:03
*** crandquist has joined #openstack-meeting02:03
*** sarob has joined #openstack-meeting02:04
*** sandywalsh_ has joined #openstack-meeting02:06
*** masayukig has joined #openstack-meeting02:09
*** Mandell has quit IRC02:10
*** crank has quit IRC02:14
*** crank has joined #openstack-meeting02:14
*** oubiwan__ has joined #openstack-meeting02:15
*** oubiwann_ has quit IRC02:16
*** epim has quit IRC02:17
*** sarob has quit IRC02:25
*** sarob has joined #openstack-meeting02:25
*** oubiwan__ has quit IRC02:27
*** oubiwann_ has joined #openstack-meeting02:28
*** colinmcnamara has joined #openstack-meeting02:28
*** david-lyle has quit IRC02:29
*** sarob has quit IRC02:30
*** cdub has quit IRC02:33
*** pablosan has quit IRC02:35
*** ryanpetrello has quit IRC02:35
*** pablosan has joined #openstack-meeting02:37
*** Gordonz has joined #openstack-meeting02:39
*** rakhmerov has quit IRC02:40
*** rakhmerov has joined #openstack-meeting02:40
*** rakhmerov has quit IRC02:40
*** masayuki_ has joined #openstack-meeting02:40
*** Gordonz has quit IRC02:42
*** lblanchard has quit IRC02:42
*** oubiwann_ has quit IRC02:43
*** Gordonz has joined #openstack-meeting02:44
*** oubiwann_ has joined #openstack-meeting02:44
*** masayuki_ has quit IRC02:45
*** nati_ueno has joined #openstack-meeting02:48
*** nati_ueno has quit IRC02:49
*** nati_ueno has joined #openstack-meeting02:50
*** MaxV has joined #openstack-meeting02:50
*** nati_uen_ has quit IRC02:51
*** colinmcnamara has quit IRC02:52
*** MaxV has quit IRC02:54
*** IlyaE has quit IRC02:55
*** arnaud__ has quit IRC02:56
*** markmcclain has quit IRC02:56
*** arnaud has quit IRC02:56
*** novas0x2a|laptop has quit IRC02:58
*** markwash has quit IRC02:59
*** slong_ has joined #openstack-meeting03:00
*** oubiwann_ has quit IRC03:00
slong_ping loquacities03:00
loquacitiesheya slong_03:00
*** baoli has quit IRC03:01
slong_just confirming, our mtg is tomorrow?03:01
slong_:)03:01
loquacitiesyep03:01
slong_the upstream calendar hasn't been updated (apparently).03:01
slong_I don't use it, but others here do.03:01
loquacitieshttp://www.timeanddate.com/worldclock/converted.html?iso=20140205T03&p1=0&p2=4703:01
slong_:)03:02
loquacitiesyeah, i don't use it either, coz you need to manually download it again every time03:02
loquacities.ics is a horrible format03:02
slong_agreed.03:02
slong_However.03:02
slong_Does Anne have to update that?03:02
loquacitiesi thought she had03:02
slong_ok, will ask deepti to ask on the mailing list. Hey, have another question. Want to be the fount of all knowledge today?03:03
loquacitieslol03:03
loquacitiesi'll do my best ;)03:03
*** dkehn_ has joined #openstack-meeting03:03
slong_I'd like to do a bit of reorg on the Config Ref and move some things over to the Cloud Admin Guide.03:03
loquacitiesaccording to anne's email: "Thierry Carrez, myself, and probably others have access to that calendar."03:03
*** dnavale has joined #openstack-meeting03:03
loquacitiesoh, good plan03:03
slong_Will I be stepping on anyone's toes for that?03:04
loquacitieshrm, i don't think so03:04
loquacitiesi was supposed to be working on that, but i've been called away to internal rackspace things recently03:04
loquacitiesso i've dropped the ball there03:04
slong_Cool, and is Nermina working on the cloud reorg still? Have you seen that? She's somehow never on when I am to ask.03:04
loquacitiesi'm not certain, quite honestly03:05
loquacitiesi never see much of her either03:05
slong_Hard being on the other side of the planet, seriously.03:05
loquacitiesyep, i get it03:05
*** spzala has quit IRC03:05
slong_ok, well, we can have a whole chat tomorrow then. Many thanks.03:05
loquacitiesalthough, you guys have been going gangbusters recently, so maybe we're starting to tip the scales towards AU a little recently ;)03:05
loquacitiesnp03:06
loquacitieswhile you're here ... when did you want to catch up?03:06
slong_Put aus on the map, dang it.03:06
loquacitiesand what kind of format do you think it should take?03:06
loquacities:)03:06
slong_Hey, you could come in for aus meeting, we'll provide the donuts?03:06
slong_the aus meeting...03:06
loquacitiesoh, now there's an idea03:06
*** armax has left #openstack-meeting03:07
slong_ja, wah?03:07
*** otherwiseguy has quit IRC03:07
*** matiu has joined #openstack-meeting03:07
*** matiu has joined #openstack-meeting03:07
loquacitieswanna book a room over at RH, and i'll pop in around 12:30?03:07
slong_Two weeks from now will give Dehlia time to organise?03:07
loquacitiesyeah, sounds great03:07
loquacitiesso, the 19th03:08
loquacitiesis there anyone else you know of who is contributing to openstack in BNE?03:08
slong_Very cool, yep I'll email her right now. How about pizza, just realised it's lunch?03:08
loquacities(and isn't at RH)03:08
loquacitiespizza is good :)03:08
slong_Nope, it's just us I believe.03:08
loquacitiesneat03:08
loquacitieswill be weird being at RH on rackspace business ;)03:09
slong_:)03:09
slong_Will go set up for the 18th.03:09
loquacitiesalthough i did drop in the other day to have a stickybeak at L3 ;)03:09
loquacities19th ...03:09
slong_dang dark calendar03:10
slong_Anyhoo.03:10
loquacities:)03:10
*** nati_ueno has quit IRC03:11
*** dzimine has joined #openstack-meeting03:11
*** dzimine has left #openstack-meeting03:12
*** boris-42_ has joined #openstack-meeting03:12
*** nati_ueno has joined #openstack-meeting03:12
*** nati_ueno has quit IRC03:13
*** samcdona has quit IRC03:13
*** nati_ueno has joined #openstack-meeting03:13
*** Tross has quit IRC03:15
*** paragan has joined #openstack-meeting03:18
*** krotscheck has quit IRC03:21
*** gokrokve has quit IRC03:26
*** sarob has joined #openstack-meeting03:26
*** gokrokve has joined #openstack-meeting03:26
*** baoli has joined #openstack-meeting03:28
*** gokrokve has quit IRC03:30
*** IlyaE has joined #openstack-meeting03:30
*** gokrokve has joined #openstack-meeting03:32
*** sarob has quit IRC03:32
*** doug_shelley66 has quit IRC03:34
*** emagana has quit IRC03:39
*** gokrokve has quit IRC03:40
*** jecarey has quit IRC03:41
*** masayuki_ has joined #openstack-meeting03:41
*** masayuki_ has quit IRC03:46
*** neelashah has joined #openstack-meeting03:47
*** MaxV has joined #openstack-meeting03:51
*** baoli has quit IRC03:53
*** MaxV has quit IRC03:55
*** david-lyle has joined #openstack-meeting03:57
*** otherwiseguy has joined #openstack-meeting03:59
*** Mandell has joined #openstack-meeting04:01
*** dcramer_ has quit IRC04:01
*** sandywalsh_ has quit IRC04:02
*** troytoman is now known as troytoman-away04:03
*** gokrokve has joined #openstack-meeting04:11
*** gokrokve_ has joined #openstack-meeting04:13
*** harlowja is now known as harlowja_away04:13
*** harlowja_away is now known as harlowja04:15
*** joearnold has quit IRC04:16
*** swifterdarrell has quit IRC04:16
*** otherjon has quit IRC04:16
*** koolhead17 has quit IRC04:16
*** anderstj has quit IRC04:16
*** gokrokve has quit IRC04:16
*** IlyaE has quit IRC04:17
*** sandywalsh_ has joined #openstack-meeting04:17
*** gokrokve_ has quit IRC04:19
*** sarob has joined #openstack-meeting04:21
*** swifterdarrell has joined #openstack-meeting04:23
*** Gordonz has quit IRC04:24
*** jgriffith has quit IRC04:24
*** jgriffith has joined #openstack-meeting04:24
*** joearnold has joined #openstack-meeting04:25
*** AlexF has joined #openstack-meeting04:26
*** jgriffith has quit IRC04:26
*** alpha_ori has joined #openstack-meeting04:27
*** otherjon has joined #openstack-meeting04:28
*** ayoung is now known as ayoung-zZzZzZ04:28
*** jgriffith has joined #openstack-meeting04:29
*** anderstj has joined #openstack-meeting04:30
*** mattgriffin has joined #openstack-meeting04:30
*** koolhead17 has joined #openstack-meeting04:31
*** gokrokve has joined #openstack-meeting04:32
*** dguitarbite has joined #openstack-meeting04:35
*** garyduan has quit IRC04:37
*** AlexF has quit IRC04:37
*** garyduan has joined #openstack-meeting04:37
*** ryanpetrello has joined #openstack-meeting04:39
*** ryanpetrello has quit IRC04:40
*** asalkeld has quit IRC04:41
*** masayuki_ has joined #openstack-meeting04:42
*** nati_ueno has quit IRC04:44
*** IlyaE has joined #openstack-meeting04:44
*** topol has joined #openstack-meeting04:44
*** masayuki_ has quit IRC04:47
*** stevemar has quit IRC04:49
*** IlyaE has quit IRC04:49
*** emagana has joined #openstack-meeting04:49
*** MaxV has joined #openstack-meeting04:51
*** emagana has quit IRC04:55
*** MaxV has quit IRC04:56
*** thuc has joined #openstack-meeting04:58
*** ryanpetrello has joined #openstack-meeting05:00
*** IlyaE has joined #openstack-meeting05:00
*** amcrn has joined #openstack-meeting05:02
*** sarob has quit IRC05:04
*** DinaBelova_ is now known as DinaBelova05:04
*** sarob has joined #openstack-meeting05:04
*** IlyaE has quit IRC05:06
*** sarob_ has joined #openstack-meeting05:07
*** sarob has quit IRC05:09
*** doug_shelley66 has joined #openstack-meeting05:09
*** banix has quit IRC05:10
*** dims has quit IRC05:11
*** mattgriffin has quit IRC05:11
*** haomaiwang has quit IRC05:12
*** haomaiwang has joined #openstack-meeting05:12
*** sarob has joined #openstack-meeting05:13
*** dims has joined #openstack-meeting05:13
*** sarob_ has quit IRC05:16
*** thuc has quit IRC05:19
*** slong has joined #openstack-meeting05:19
*** thuc has joined #openstack-meeting05:19
*** slong_ has quit IRC05:20
*** coolsvap has joined #openstack-meeting05:21
*** amotoki has joined #openstack-meeting05:22
*** nshaikh has joined #openstack-meeting05:23
*** thuc has quit IRC05:23
*** gokrokve has quit IRC05:24
*** rakhmerov has joined #openstack-meeting05:25
*** rakhmerov has quit IRC05:25
*** rakhmerov has joined #openstack-meeting05:25
*** markmcclain has joined #openstack-meeting05:28
*** sarob has quit IRC05:32
*** sarob has joined #openstack-meeting05:32
*** gokrokve has joined #openstack-meeting05:33
*** sarob has quit IRC05:37
*** gokrokve has quit IRC05:38
*** markwash has joined #openstack-meeting05:40
*** crandquist has quit IRC05:40
*** rwsu has quit IRC05:41
*** asalkeld has joined #openstack-meeting05:42
*** masayuki_ has joined #openstack-meeting05:43
*** Tross has joined #openstack-meeting05:46
*** masayuki_ has quit IRC05:47
*** slong has quit IRC05:50
*** dendroba` is now known as dendrobates05:53
*** IlyaE has joined #openstack-meeting05:53
*** AlexF has joined #openstack-meeting05:54
*** AlexF has quit IRC05:59
*** AlexF has joined #openstack-meeting05:59
*** nosnos_ has joined #openstack-meeting06:00
*** ryanpetrello has quit IRC06:00
*** ildikov_ has quit IRC06:01
*** markwash has quit IRC06:02
*** nosnos has quit IRC06:03
*** sarob has joined #openstack-meeting06:03
*** jcoufal has joined #openstack-meeting06:04
*** AlexF has quit IRC06:04
*** otherwiseguy has quit IRC06:05
*** AlexF has joined #openstack-meeting06:08
*** colinmcnamara has joined #openstack-meeting06:12
*** markpeek has quit IRC06:13
*** marcoemorais has joined #openstack-meeting06:14
*** colinmcnamara has quit IRC06:16
*** marcoemorais1 has joined #openstack-meeting06:16
*** marcoemorais has quit IRC06:20
*** AlexF has quit IRC06:24
*** jcooley_ has joined #openstack-meeting06:26
*** otherwiseguy has joined #openstack-meeting06:28
*** neelashah1 has joined #openstack-meeting06:30
*** topol_ has joined #openstack-meeting06:30
*** Mandell_ has joined #openstack-meeting06:30
*** colinmcnamara has joined #openstack-meeting06:31
*** sarob has quit IRC06:31
*** Tross1 has joined #openstack-meeting06:31
*** mdurnosvistov has joined #openstack-meeting06:31
*** resker has joined #openstack-meeting06:31
*** apmelton1 has joined #openstack-meeting06:32
*** coolsvap_away has joined #openstack-meeting06:32
*** brucer_ has joined #openstack-meeting06:32
*** matsuhashi has quit IRC06:33
*** gokrokve has joined #openstack-meeting06:33
*** matsuhashi has joined #openstack-meeting06:33
*** branen_ has joined #openstack-meeting06:33
*** SpamapS_ has joined #openstack-meeting06:33
*** soren has joined #openstack-meeting06:34
*** soren has quit IRC06:34
*** soren has joined #openstack-meeting06:34
*** e-vad_ has joined #openstack-meeting06:34
*** shadower_ has joined #openstack-meeting06:34
*** masayuki_ has joined #openstack-meeting06:35
*** flaper87l has joined #openstack-meeting06:35
*** IlyaE_ has joined #openstack-meeting06:35
*** colinmcnamara has quit IRC06:35
*** flaper87l is now known as flaper8706:35
*** jd__` has joined #openstack-meeting06:37
*** gmurphy_ has joined #openstack-meeting06:37
*** gokrokve has quit IRC06:38
*** IlyaE has quit IRC06:38
*** Tross has quit IRC06:38
*** asalkeld has quit IRC06:38
*** nshaikh has quit IRC06:38
*** coolsvap has quit IRC06:38
*** dims has quit IRC06:38
*** topol has quit IRC06:38
*** alpha_ori has quit IRC06:38
*** joearnold has quit IRC06:38
*** Mandell has quit IRC06:38
*** neelashah has quit IRC06:38
*** paragan has quit IRC06:38
*** masayukig has quit IRC06:38
*** brucer has quit IRC06:38
*** mattoliverau has quit IRC06:38
*** gmurphy has quit IRC06:38
*** IgorYozhikov has quit IRC06:38
*** primeministerp has quit IRC06:38
*** marios has quit IRC06:38
*** SpamapS has quit IRC06:38
*** e-vad has quit IRC06:38
*** soren_ has quit IRC06:38
*** mdurnosvistov__ has quit IRC06:38
*** d0ugal has quit IRC06:38
*** n0ano has quit IRC06:38
*** elo has quit IRC06:38
*** esker has quit IRC06:38
*** branen has quit IRC06:38
*** zul has quit IRC06:38
*** apmelton has quit IRC06:38
*** benonsoftware has quit IRC06:38
*** med_ has quit IRC06:38
*** dteselkin has quit IRC06:38
*** flaper87|afk has quit IRC06:38
*** jd__ has quit IRC06:38
*** shadower has quit IRC06:38
*** krtaylor has quit IRC06:38
*** mordred has quit IRC06:38
*** matrohon has quit IRC06:38
*** dteselkin_ has joined #openstack-meeting06:38
*** jd__` is now known as jd__06:38
*** IlyaE_ is now known as IlyaE06:39
*** alpha_ori has joined #openstack-meeting06:39
*** primeministerp has joined #openstack-meeting06:40
*** joearnold has joined #openstack-meeting06:41
*** Tross1 has quit IRC06:42
*** mrda is now known as mrda_away06:43
*** Tross has joined #openstack-meeting06:43
*** benonsoftware has joined #openstack-meeting06:43
*** benonsoftware has joined #openstack-meeting06:44
*** masayukig has joined #openstack-meeting06:44
*** topol_ has quit IRC06:44
*** harlowja is now known as harlowja_away06:44
*** IgorYozhikov has joined #openstack-meeting06:45
*** asalkeld has joined #openstack-meeting06:45
*** n0ano has joined #openstack-meeting06:45
*** d0ugal has joined #openstack-meeting06:45
*** d0ugal has quit IRC06:45
*** d0ugal has joined #openstack-meeting06:45
*** denis_makogon_ has joined #openstack-meeting06:45
*** paragan has joined #openstack-meeting06:45
*** paragan has quit IRC06:45
*** paragan has joined #openstack-meeting06:45
*** mattoliverau has joined #openstack-meeting06:45
*** zul has joined #openstack-meeting06:46
*** nshaikh has joined #openstack-meeting06:47
*** masayukig has quit IRC06:48
*** skraynev_ is now known as skraynev06:50
*** dguitarbite has quit IRC06:53
*** mordred has joined #openstack-meeting06:54
*** ativelkov has left #openstack-meeting06:58
*** krtaylor has joined #openstack-meeting06:59
*** sacharya has quit IRC07:00
*** marios has joined #openstack-meeting07:00
*** haomaiwa_ has joined #openstack-meeting07:02
*** haomaiwang has quit IRC07:04
*** coolsvap_away has quit IRC07:04
*** dims has joined #openstack-meeting07:08
*** aignatov_ is now known as aignatov07:08
*** markmcclain has quit IRC07:10
*** jcooley_ has quit IRC07:12
*** saju_m has joined #openstack-meeting07:12
*** asalkeld has quit IRC07:16
*** lcheng_ has joined #openstack-meeting07:16
*** flaper87 has quit IRC07:21
*** flaper87 has joined #openstack-meeting07:21
*** yamahata has quit IRC07:23
*** coolsvap has joined #openstack-meeting07:26
*** dguitarbite has joined #openstack-meeting07:28
*** elo has joined #openstack-meeting07:30
*** mrunge has joined #openstack-meeting07:31
*** otherwiseguy has quit IRC07:32
*** AlexF has joined #openstack-meeting07:32
*** asalkeld has joined #openstack-meeting07:33
*** gokrokve has joined #openstack-meeting07:33
*** obondarev has joined #openstack-meeting07:34
*** rmk has joined #openstack-meeting07:34
*** akuznetsov has joined #openstack-meeting07:37
*** gokrokve has quit IRC07:38
*** MaxV has joined #openstack-meeting07:41
*** AlexF has quit IRC07:41
*** rwsu has joined #openstack-meeting07:42
*** sarob has joined #openstack-meeting07:43
*** masayukig has joined #openstack-meeting07:44
*** aignatov is now known as aignatov_07:44
*** lcheng_ has quit IRC07:47
*** amcrn has quit IRC07:47
*** sarob has quit IRC07:48
*** jcooley_ has joined #openstack-meeting07:48
*** masayukig has quit IRC07:48
*** MaxV has quit IRC07:50
*** rwsu has quit IRC07:51
*** mdurnosvistov_ has joined #openstack-meeting07:52
*** rwsu has joined #openstack-meeting07:53
*** akuznetsov has quit IRC07:54
*** jcooley_ has quit IRC07:56
*** afazekas has joined #openstack-meeting08:01
*** ken1ohmichi has left #openstack-meeting08:05
*** afazekas has quit IRC08:07
*** IlyaE has quit IRC08:08
*** denis_makogon_ has quit IRC08:09
*** akuznetsov has joined #openstack-meeting08:13
*** sarob has joined #openstack-meeting08:13
*** mdurnosvistov_ has quit IRC08:16
*** sarob has quit IRC08:18
*** asalkeld has quit IRC08:20
*** jtomasek has joined #openstack-meeting08:22
*** jhenner has joined #openstack-meeting08:22
*** colinmcnamara has joined #openstack-meeting08:23
*** afazekas has joined #openstack-meeting08:23
*** zoresvit has joined #openstack-meeting08:25
*** thouveng has joined #openstack-meeting08:26
*** colinmcnamara has quit IRC08:27
*** comay has quit IRC08:29
*** marcoemorais1 has quit IRC08:29
*** fbo is now known as fbo_away08:32
*** gokrokve has joined #openstack-meeting08:33
*** f_rossigneux has joined #openstack-meeting08:34
*** coolsvap has quit IRC08:36
*** Fdot has joined #openstack-meeting08:37
*** gokrokve has quit IRC08:37
*** sushils has joined #openstack-meeting08:40
*** I159 has joined #openstack-meeting08:42
*** ogelbukh1 is now known as ogelbukh08:42
*** yamahata has joined #openstack-meeting08:43
*** pradipta has joined #openstack-meeting08:43
*** masayukig has joined #openstack-meeting08:45
*** aignatov_ is now known as aignatov08:45
*** jhenner has quit IRC08:46
*** jhenner has joined #openstack-meeting08:47
*** jhenner has quit IRC08:48
*** jhenner has joined #openstack-meeting08:48
*** masayukig has quit IRC08:50
*** colinmcnamara has joined #openstack-meeting08:50
*** MaxV has joined #openstack-meeting08:52
*** igormarnat_ has joined #openstack-meeting08:52
*** igormarnat_ has left #openstack-meeting08:52
*** belmoreira has joined #openstack-meeting08:53
*** colinmcnamara has quit IRC08:55
*** ilyashakhat has joined #openstack-meeting08:55
*** ygbo has joined #openstack-meeting08:56
*** lsmola has joined #openstack-meeting08:56
*** dguitarbite_ has joined #openstack-meeting08:57
*** safchain has joined #openstack-meeting09:01
*** ndipanov has joined #openstack-meeting09:02
*** pradipta has quit IRC09:03
*** jhenner has quit IRC09:03
*** ArthurBerezin has joined #openstack-meeting09:07
*** colinmcnamara has joined #openstack-meeting09:08
*** mdbooth_gone has joined #openstack-meeting09:09
*** mdbooth_gone is now known as mdbooth09:09
*** colinmcnamara has quit IRC09:12
*** jhenner has joined #openstack-meeting09:13
*** sarob has joined #openstack-meeting09:13
*** safchain has quit IRC09:14
*** sarob has quit IRC09:18
*** masayuki_ has quit IRC09:20
*** fbo_away is now known as fbo09:22
*** coolsvap has joined #openstack-meeting09:23
*** ArthurBerezin has left #openstack-meeting09:23
*** johnthetubaguy has joined #openstack-meeting09:24
*** shanks has joined #openstack-meeting09:25
*** marcoemorais has joined #openstack-meeting09:26
*** jamespage has joined #openstack-meeting09:27
*** sanek11 is now known as agordeev09:28
*** nshaikh has left #openstack-meeting09:29
*** jhenner has quit IRC09:30
*** MaxV has quit IRC09:30
*** johnthetubaguy has quit IRC09:31
*** MaxV has joined #openstack-meeting09:31
*** johnthetubaguy has joined #openstack-meeting09:32
*** egallen has joined #openstack-meeting09:33
*** gokrokve has joined #openstack-meeting09:33
*** MrJoshua has left #openstack-meeting09:34
*** mdurnosvistov has quit IRC09:34
*** colinmcnamara has joined #openstack-meeting09:35
*** marcoemorais has quit IRC09:35
*** egallen has quit IRC09:36
*** mdurnosvistov has joined #openstack-meeting09:37
*** gokrokve has quit IRC09:38
*** colinmcnamara has quit IRC09:39
*** safchain has joined #openstack-meeting09:41
*** MrJoshua has joined #openstack-meeting09:44
*** egallen has joined #openstack-meeting09:45
*** MrJoshua has left #openstack-meeting09:45
*** masayukig has joined #openstack-meeting09:46
*** zoresvit has quit IRC09:47
*** reed has joined #openstack-meeting09:50
*** masayukig has quit IRC09:51
*** matrohon has joined #openstack-meeting09:51
*** zoresvit has joined #openstack-meeting10:00
*** miarmak has joined #openstack-meeting10:01
*** colinmcnamara has joined #openstack-meeting10:02
*** colinmcnamara has quit IRC10:06
*** jamespage_ has joined #openstack-meeting10:09
*** jhenner has joined #openstack-meeting10:11
*** aignatov is now known as aignatov_10:13
*** sarob has joined #openstack-meeting10:13
*** jcooley_ has joined #openstack-meeting10:17
*** sarob has quit IRC10:18
*** Adri2000_ is now known as Adri200010:21
*** metabro has quit IRC10:22
*** jcooley_ has quit IRC10:23
*** d0ugal has quit IRC10:29
*** colinmcnamara has joined #openstack-meeting10:29
*** paragan has quit IRC10:30
*** coolsvap has quit IRC10:30
*** marcoemorais has joined #openstack-meeting10:31
*** d0ugal has joined #openstack-meeting10:32
*** d0ugal has quit IRC10:32
*** d0ugal has joined #openstack-meeting10:32
*** gokrokve has joined #openstack-meeting10:33
*** colinmcnamara has quit IRC10:34
*** marcoemorais has quit IRC10:36
*** jamespage_ has quit IRC10:37
*** gokrokve has quit IRC10:37
*** nimi has joined #openstack-meeting10:39
*** zoresvit has quit IRC10:43
*** boris-42_ has quit IRC10:43
*** zoresvit has joined #openstack-meeting10:43
*** masayukig has joined #openstack-meeting10:46
*** cody-somerville has joined #openstack-meeting10:46
*** masayukig has quit IRC10:51
*** nimi has quit IRC10:53
*** colinmcnamara has joined #openstack-meeting10:56
*** russellb has joined #openstack-meeting11:00
*** colinmcnamara has quit IRC11:01
*** aignatov_ is now known as aignatov11:01
*** DinaBelova is now known as DinaBelova_11:01
*** DinaBelova_ is now known as DinaBelova11:02
*** pradipta has joined #openstack-meeting11:02
*** asalkeld has joined #openstack-meeting11:02
*** zoresvit has quit IRC11:08
*** zoresvit1 has joined #openstack-meeting11:08
*** DinaBelova is now known as DinaBelova_11:10
*** MaxV has quit IRC11:10
*** egallen has quit IRC11:11
*** jamespage_ has joined #openstack-meeting11:12
*** jcooley_ has joined #openstack-meeting11:13
*** sarob has joined #openstack-meeting11:13
*** egallen has joined #openstack-meeting11:14
*** sushils has quit IRC11:14
*** sarob_ has joined #openstack-meeting11:16
*** sarob has quit IRC11:18
*** jcooley_ has quit IRC11:19
*** sarob_ has quit IRC11:20
*** MaxV has joined #openstack-meeting11:23
*** nshaikh has joined #openstack-meeting11:24
*** jcoufal has quit IRC11:26
*** ArthurBerezin has joined #openstack-meeting11:28
*** ArthurBerezin has left #openstack-meeting11:28
*** david-lyle has quit IRC11:29
*** nosnos_ has quit IRC11:30
*** marcoemorais has joined #openstack-meeting11:31
*** dguitarbite_ has quit IRC11:32
*** dguitarbite has quit IRC11:32
*** gokrokve has joined #openstack-meeting11:33
*** marcoemorais has quit IRC11:36
*** gokrokve has quit IRC11:38
*** amotoki has quit IRC11:38
*** amotoki has joined #openstack-meeting11:38
*** egallen has quit IRC11:40
*** jamespage_ has joined #openstack-meeting11:43
*** jamespage_ has quit IRC11:43
*** jamespage__ has joined #openstack-meeting11:43
*** jamespage__ has quit IRC11:44
*** megan_w has joined #openstack-meeting11:46
*** masayukig has joined #openstack-meeting11:47
*** rfolco has joined #openstack-meeting11:48
*** asalkeld has quit IRC11:50
*** colinmcnamara has joined #openstack-meeting11:52
*** masayukig has quit IRC11:52
*** paragan has joined #openstack-meeting11:54
*** paragan has joined #openstack-meeting11:54
*** colinmcnamara has quit IRC11:56
*** jhenner has quit IRC11:57
*** asalkeld has joined #openstack-meeting11:57
*** aignatov is now known as aignatov_12:00
*** jhenner has joined #openstack-meeting12:02
*** DuncanT- is now known as DuncanT12:02
*** miqui has quit IRC12:04
*** yamahata has quit IRC12:04
*** yamahata has joined #openstack-meeting12:08
*** vkmc has joined #openstack-meeting12:10
*** aignatov_ is now known as aignatov12:12
*** sarob has joined #openstack-meeting12:13
*** sandywalsh_ has quit IRC12:15
*** neelashah1 has quit IRC12:16
*** esker has joined #openstack-meeting12:17
*** sarob has quit IRC12:18
*** resker has quit IRC12:20
*** yassine has joined #openstack-meeting12:20
*** aignatov is now known as aignatov_12:22
*** aignatov_ is now known as aignatov12:24
*** sandywalsh_ has joined #openstack-meeting12:28
*** zoresvit1 has quit IRC12:29
*** asalkeld has quit IRC12:31
*** boris-42_ has joined #openstack-meeting12:32
*** masayukig has joined #openstack-meeting12:32
*** IanGovett has joined #openstack-meeting12:32
*** egallen has joined #openstack-meeting12:32
*** gokrokve has joined #openstack-meeting12:33
*** matsuhashi has quit IRC12:36
*** pradipta has quit IRC12:36
*** masayukig has quit IRC12:36
*** matsuhashi has joined #openstack-meeting12:36
*** yamahata has quit IRC12:37
*** gokrokve has quit IRC12:37
*** DinaBelova_ is now known as DinaBelova12:38
*** matsuhashi has quit IRC12:41
*** sushils has joined #openstack-meeting12:50
*** yamahata has joined #openstack-meeting12:51
*** doron_afk has joined #openstack-meeting12:51
*** DinaBelova is now known as DinaBelova_12:52
*** DinaBelova_ is now known as DinaBelova12:55
*** DinaBelova is now known as DinaBelova_12:55
*** weshay has quit IRC12:56
*** baoli has joined #openstack-meeting12:56
*** jhenner has quit IRC12:58
*** markmcclain has joined #openstack-meeting12:59
*** ArthurBerezin has joined #openstack-meeting13:00
*** DinaBelova_ is now known as DinaBelova13:01
*** yamahata has quit IRC13:03
*** jhenner has joined #openstack-meeting13:04
*** yamahata has joined #openstack-meeting13:07
*** ArthurBerezin has left #openstack-meeting13:08
*** AlexF has joined #openstack-meeting13:08
*** DinaBelova is now known as DinaBelova_13:10
*** ArthurBerezin has joined #openstack-meeting13:11
*** pdmars has joined #openstack-meeting13:13
*** sarob has joined #openstack-meeting13:13
*** ArthurBerezin has quit IRC13:16
*** xazel has joined #openstack-meeting13:16
*** sarob has quit IRC13:17
*** alexpilotti has joined #openstack-meeting13:18
*** jamespage_ has joined #openstack-meeting13:20
*** ityaptin has quit IRC13:21
*** jcoufal has joined #openstack-meeting13:21
*** ArthurBerezin has joined #openstack-meeting13:23
*** jamespage_ has quit IRC13:24
*** yamahata has quit IRC13:26
*** metral has joined #openstack-meeting13:27
*** kebray has joined #openstack-meeting13:27
*** rainya has joined #openstack-meeting13:27
*** annegentle has joined #openstack-meeting13:27
*** 64MAAAAAS has joined #openstack-meeting13:27
*** moe816 has joined #openstack-meeting13:27
*** pvo has joined #openstack-meeting13:27
*** jbryce has joined #openstack-meeting13:27
*** lillie has joined #openstack-meeting13:27
*** lillie is now known as Guest4680613:28
*** jdob has joined #openstack-meeting13:30
*** weshay has joined #openstack-meeting13:32
*** yamahata has joined #openstack-meeting13:32
*** marcoemorais has joined #openstack-meeting13:32
*** masayukig has joined #openstack-meeting13:33
*** gokrokve has joined #openstack-meeting13:33
*** marcoemorais has quit IRC13:36
*** masayukig has quit IRC13:37
*** gokrokve has quit IRC13:38
*** ityaptin has joined #openstack-meeting13:41
*** saju_m has quit IRC13:41
*** jprovazn has joined #openstack-meeting13:44
*** nacim has quit IRC13:44
*** ekarlso- has quit IRC13:45
*** ekarlso has joined #openstack-meeting13:45
*** yamahata has quit IRC13:46
*** ryanpetrello has joined #openstack-meeting13:46
*** yamahata has joined #openstack-meeting13:50
*** nacim has joined #openstack-meeting13:50
*** balajiiyer has joined #openstack-meeting13:52
*** balajiiyer has left #openstack-meeting13:54
*** yamahata has quit IRC13:55
*** prad_ has joined #openstack-meeting13:55
*** aveiga has joined #openstack-meeting13:55
*** doug_shelley66 has quit IRC13:56
sc68calaveiga: morning13:56
*** rossella_s has joined #openstack-meeting13:56
*** thomasem has joined #openstack-meeting13:56
aveigao/13:57
*** yamahata has joined #openstack-meeting13:59
sc68calalright - let's get this show on the road13:59
aveiga+113:59
sc68cal#startmeeting neutron_ipv613:59
openstackMeeting started Tue Feb  4 13:59:35 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"13:59
openstackThe meeting name has been set to 'neutron_ipv6'13:59
sc68cal#topic recap previous meeting14:00
*** openstack changes topic to "recap previous meeting (Meeting topic: neutron_ipv6)"14:00
sc68cal#link https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_Feb_4th Agenda for today14:01
*** alexey_o has joined #openstack-meeting14:01
sc68calLooks like shshang isn't here yet14:01
*** pcm has joined #openstack-meeting14:02
*** bill_az has joined #openstack-meeting14:02
*** jhenner1 has joined #openstack-meeting14:02
sc68calSo, last week I had an action to rebase the review and add the second ipv6 attribute to subnets14:03
*** jhenner has quit IRC14:03
*** dims has quit IRC14:03
sc68cal#link https://review.openstack.org/#/c/52983/ Create new IPv6 attributes for Subnets14:03
sc68calSo at this point it's just fixing some issues with the migration and db models to make them play nice with postgresql14:04
sc68calshshang has a review that we're trying to get rebased on top of that review, so the gate will test it properly14:05
*** dkranz has quit IRC14:05
*** BrianB__ has joined #openstack-meeting14:05
aveigais that the one that the of you were working out in #openstack-neutron last week?14:05
*** dprince has joined #openstack-meeting14:05
*** lsmola has quit IRC14:05
*** shshang has joined #openstack-meeting14:06
baolisc68cal, one question with this review: https://review.openstack.org/#/c/58186/. Is it completely abandoned? shshang's new review covers dhcp. What about the remaining changes in 58186?14:06
*** bill_az_ has joined #openstack-meeting14:06
*** beagles is now known as beagles_brb14:06
*** bill_az has quit IRC14:06
sc68calbaoli: I imagine that will be rebased14:06
aveigabaoli: I think that one is abandoned, as it's using an old model14:06
aveigathat was basing on running the entire dhcpv6 server out of the router space14:07
shshangYes, that one is abandoned14:07
sc68calah whoops14:07
baoliok.14:07
*** tongli has joined #openstack-meeting14:07
sc68calFor some reason I was thinking the IPV6 SLAAC blueprint - which was just abandoned this morning14:07
*** ayoung-zZzZzZ has quit IRC14:08
baoliSo the changes in the firewall module is no longer needed with this new model14:08
aveigawhich changes?14:08
baolihttps://review.openstack.org/#/c/58186/2/neutron/agent/linux/iptables_firewall.py14:09
*** mattoliverau has quit IRC14:09
*** hnarkaytis has joined #openstack-meeting14:09
shshangThe firewall changes, I think, is duplicating with DaoZhao's code14:09
aveiga+114:09
*** xuhanp has joined #openstack-meeting14:09
sc68calI think it actually duplicates this14:09
aveigait's necessary, but will be compartmentalized to be added only for gateway IPs14:10
aveigaand that's what DaoZhao's working on14:10
xuhanphello everyone, sorry for being late14:10
sc68calhttps://github.com/netoisstools/neutron/commit/cecd7591533e2c046aedba3b8e5d14a5b2fa7fe914:10
*** absubram has joined #openstack-meeting14:10
shshangHey, xuhanp14:10
*** dane_ has joined #openstack-meeting14:10
xuhanphey. sorry for interrupting, pleaes continue.14:10
*** alexey_o has quit IRC14:11
baoligot it.14:11
sc68calshshang: Do you have the link handy for the blueprint for horizon that we needed to register?14:11
sc68calI have an old one - https://blueprints.launchpad.net/horizon/+spec/neutron-subnet-mode-support14:12
shshangNo....I didn't register one yet for horizon....Sorry about that. :(14:12
shshangWill do today14:12
sc68calshshang: OK - well let's just repurpose the one I created a while back14:12
sc68cal#action sc68cal edit horizon blueprint to match new attribute blueprints in neutron14:13
absubramHi can we add some more details to that Horizon bp please?14:13
*** sarob has joined #openstack-meeting14:13
*** ItSANgo has quit IRC14:13
sc68cal#topic blueprints14:13
*** openstack changes topic to "blueprints (Meeting topic: neutron_ipv6)"14:14
sc68calabsubram: Yes - do you have any suggestions?14:14
sc68calAlright. Moving on14:15
*** markmcclain has quit IRC14:15
baolisc68cal, shshang, one more question regarding the abandoned review: https://review.openstack.org/#/c/58186/2/neutron/agent/l3_agent.py. what happens to that change?14:15
*** rtuttle1015 has joined #openstack-meeting14:15
absubramwell I am new to this.. but I was taking a look at it from what needed to be done in Horizon.. and I am not really sure what the ipv6 effort adds from neutron..14:16
absubramso maybe just some whiteboard notes14:16
shshangThe l3_agent function will be carried onto icehouse release. I am waiting for Randy to join. He owns that piece14:16
sc68calbaoli: Check out shshang's new review https://webmail.comcast.com/owa/redir.aspx?C=QxLI8ZBxq0GPzZXTFxWndIhLZPRF9dAIqAyUc7s4-RSvq9I03V1QBlP0VXz43dUkRD1zumO4wBI.&URL=https%3a%2f%2freview.openstack.org%2f7064914:16
sc68calshit14:16
absubramthat way it'd be easier to figure out what needs to be done from Horizon to support this?14:16
sc68calhttps://review.openstack.org/#/c/70649/14:16
aveigaabsubram: the horizon piece is going to need to reflect the new options we're adding to the API14:16
shshangI am only working on the tenant network side14:17
aveigathere are two keywords going in for managin IPv6 subnets14:17
shshangand Randy is working on the external network side14:17
*** sarob has quit IRC14:18
*** yamahata has quit IRC14:18
baolishshang, another BP or a bug?14:18
absubramaveiga: thanks! can we add that detail and what the new keywords are? In the horizon bp..14:18
aveigaabsubram: Yes, because it will be directly linked to the other BP covering said attributes14:18
sc68calabsubram: there's a link to the neutron bp in the description for the horizon bp14:19
*** doron_afk is now known as doron14:19
*** yamahata has joined #openstack-meeting14:19
shshanghttps://blueprints.launchpad.net/neutron/+spec/ipv6-two-attributes14:19
absubramok thanks!14:19
absubramwill look at it14:19
*** lblanchard has joined #openstack-meeting14:20
aveigaabsubram: you might want to go back and take a look at our past meeting minutes to catch up, there's a lot we've discussed previously that explains why we're doing what we're doing: https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam14:20
*** thuc has joined #openstack-meeting14:20
baolishshang, so this BP will also cover the change in l3_agent.py, and Randy will be working on it. thanks.14:21
*** ItSANgo has joined #openstack-meeting14:22
*** lsmola has joined #openstack-meeting14:22
absubramaveiga: good suggestion.. I'll be sure to do that14:22
*** changbl has quit IRC14:23
sc68calAnything else on the blueprint side before I turn it over to open discussion?14:23
aveigaso besides the Horizon BP, are there any missing to complete our existing goals for Icehouse?14:23
baoliAny work with devstack to setup ipv6?14:24
aveigaI think no, at this point14:24
shshangsc68cal, I still need your help to link my code to your base14:24
*** prad_ has quit IRC14:24
aveigasc68cal has been setting up devstack in our lab with v6, but it's tweaked to use provider networks.  I don't think there's much to change though for GRE14:24
shshangsc68cal, do you have some time today and we can use google hangout?14:25
aveigasc68cal: would it be possible to post your configs as a gist?14:25
aveigaor maybe in the openstack etherpad14:25
sc68calshshang: Yes - I can help you today14:25
sc68calI can post my configs for devstack as well that we use in the lab14:26
baolicool14:26
sc68calI also have a branch of devstack that creates v6 subnets - so I'll post that branch as well14:26
rtuttle1015@baoli: yes, I am addressing the l3_agent.py for external gateway14:27
baolirtuttle1015, thanks.14:27
baolisc68cal, would the changes you have for devstack needs to be upstreamed?14:28
sc68cal#action sc68cal post branch of Devstack + configs on the mailing list14:28
sc68calbaoli: They'd need some work for that14:29
*** andreaf has joined #openstack-meeting14:29
aveigabaoli: not sure, like I said they're specific to provider nets and I know devstack doesn't normally do that14:29
sc68cal^^^ what aveiga said14:29
aveigabut if they can be altered to do GRE tunnels, then I don't see why not14:29
aveigastart exposing the rest of openstack devs to v6 as soon as we can14:29
baoliwell, let me think about that14:30
aveigaonce they're up, have a look14:30
aveigaif you see something you can do to integrate them, go nuts14:30
baolisure thing14:30
aveigaI think we're clear on BPs then14:30
sc68cal#topic open discussion14:31
*** openstack changes topic to "open discussion (Meeting topic: neutron_ipv6)"14:31
shshangRandy and I have a question regarding semantic check14:31
*** oubiwann_ has joined #openstack-meeting14:32
shshangIn two attributes combination, some modes are not valid for some use cases14:32
aveigaI think the determination we made last time was to let it go14:32
shshangWe think we need to add semantic check to return errors to client (both neutron CLI and Horizon)14:33
aveigaif the user is configuring these, they need to know enough about IPv6 networks14:33
*** egallen has quit IRC14:33
aveigafor the same reason that we covered not just assuming it's invalid14:33
*** gokrokve has joined #openstack-meeting14:33
aveigamaybe a user is trying to do something we haven't come across yet14:33
*** dvarga has joined #openstack-meeting14:33
*** pnavarro has joined #openstack-meeting14:33
*** masayukig has joined #openstack-meeting14:33
shshangyes, so in this case, we need to let user be aware what they are doing is not supported14:33
rtuttle1015but if the wrong combos get to the agent on network node, weird configs get hard to debug. why not send the error back from API14:34
aveigawhat's not supported, though?14:34
aveigartuttle1015: which use case are you referring to?14:34
shshangSo the best place we can think of is on neutron server side14:34
*** spzala has joined #openstack-meeting14:34
rtuttle1015shshang's table are the valid cases14:34
shshangwhich can cover both neutron client and horizon14:34
rtuttle1015can we not include a static table of some sort that determines the valid combos14:35
*** akuznetsov has quit IRC14:35
xuhanpI think we can add the check to Sean's code which is validating the two modes14:35
aveigawe can't make a determination on validity14:35
rtuttle1015yes, this is what shshang and I were thinking14:35
shshangxuhanp, that is what we are thinking too14:35
aveigathat's the core of what I'm getting at14:35
*** amotoki has quit IRC14:35
rtuttle1015no, we have shshang's table which highlight the current supported combos.14:35
sc68calrtuttle1015: ah , is that what those red squiggles are?14:36
rtuttle1015a truth table of sorts14:36
*** egallen has joined #openstack-meeting14:36
aveigaI can't seem to find the table14:36
*** vijendar has joined #openstack-meeting14:36
aveigaor at least, the most recent version14:36
sc68cal#link https://www.dropbox.com/s/rq8xmbruqthef38/IPv6%20Two%20Modes%20v2.0.pdf Ipv6 modes table14:36
shshangsc68cal, yes, the highlighted one are the ones we support and we developed14:36
rtuttle1015yes, that's it14:36
sc68calyou guys should amend that PDF to add that - I sort of was wondering what it was14:37
shshangyes, we will14:37
aveigathat PDF has everything underlined except the cases where averything is off14:37
aveigawhich is the equivalent to setting enable_dhcp = 014:37
shshangfor example, if subnet has no gateway port, and user want dnsmasq to send RA, then we need to return error14:37
*** masayukig has quit IRC14:38
*** IanGovett has quit IRC14:38
shshangI need to update the link to version 3.014:38
*** gokrokve has quit IRC14:38
aveigashshang: what if the gateway is going to be added by config drive when a service VM starts up?14:38
aveigait would need to be on-net before the port could be added14:38
*** joesavak has joined #openstack-meeting14:39
shshangthat is the case we didn't have time to cover yet14:39
aveigaright14:39
aveigathat's why I'm saying don't throw a validation error14:39
aveigajust silently let it go14:39
sc68calaveiga: I imagine we'd need to talk to the service insertion folks14:39
*** thuc has quit IRC14:39
aveigasc68cal: I'm imagining this is possible on your own today even without that piece14:39
sc68calsince they're tackling the problem of how to insert firewalls and other services into the wire14:39
*** balajiiyer has joined #openstack-meeting14:40
*** thuc has joined #openstack-meeting14:40
aveigaI could spin up an haproxy today on v6, use config drive to manually add the v6 address that's not part of the pool but still inside the /64, and then use the api to add it as the gateway14:40
shshangaveiga, that is actually the next topic I want to bring up14:40
*** egallen has quit IRC14:40
*** medberry has joined #openstack-meeting14:40
*** medberry has quit IRC14:40
*** medberry has joined #openstack-meeting14:40
*** lsmola has quit IRC14:41
shshangthe validation should be there based on the current configuration. If later on, the setup is changed, then we need to trigger the validation again.14:41
*** ArthurBerezin has quit IRC14:41
shshangSo this is 2-fold story14:41
*** banix has joined #openstack-meeting14:41
aveigabut according to your table, all modes are valid except off/off14:42
*** coolsvap has joined #openstack-meeting14:42
shshangI refer to a case in the last email thread, which discuss private network v.s. provider network.....14:42
shshangYou bring up a good point of provider network in your reply.14:43
*** doug_shelley66 has joined #openstack-meeting14:44
aveigaI think we have a different issue here14:44
*** thuc has quit IRC14:44
aveigathat's a question of which addresses we want to use on a private network14:44
aveigatechnically, we don't need any since LLA should be sufficient14:45
shshangyes, that cover address assignment side. How are about RA side?14:45
aveigano RA14:45
aveigaif you're using LLA14:45
aveigabut that's not the question14:45
shshangexactly14:45
aveigathe question is do we want to support GRAs on a private network?14:45
aveigaor even ULAs14:46
shshangwhat if user configure ipv6_ra_mode with attribute to enable RA14:46
aveigaenabling RA only works if there's a gateway port14:46
shshangwe know we don't need RA, but user may not know14:46
shshangthere is nothing prevent them from typing ipv6_ra_mode = DHCPV6 Stateful14:46
shshangand if that happens, the system needs to tell them, sorry, this is wrong14:47
aveigaif there's no gateway, then we report that we can't issue RAs14:47
aveigano matter what mode14:47
baoliaveiga, why enabling RA only works if there's a gateway port?14:47
shshangexactly. The "report" piece is what I am looking for14:47
aveigabaoli: something has to send the RA14:47
shshangThe "report" is what I refer to semantic check14:48
shshangthe system need to throw error14:48
baoliYou can send it through the dhcp port, right?14:48
aveigabaoli: only if you want to permanently blackhole that network14:48
aveigaif I add a gateway port later, it won't do anything14:48
aveigamost linux distros ignore multiple RAs for the same subnet14:48
*** hnarkaytis has quit IRC14:48
aveigaso the second RA would come from the valid gateway, but get ignored.  Then you can't route14:49
baoliI think that's the purpose of ULA? In addition, a port can have mutiple ipv6 addresses in addition to ULA14:49
*** jdob_ has joined #openstack-meeting14:49
*** jdob has quit IRC14:49
baoliaveiga, a route can be associated with a preference value14:50
aveigaif you want ULA, then you have to advertise only ULA14:50
aveigabaoli: linux doesn't honor the preference value14:50
*** armax has joined #openstack-meeting14:50
aveigathere are MANY bugs filed against this14:50
shshangIf user add a gateway port later, DB is updated. If user prefer change the subnet mode, then they can do it now.14:51
aveigaI've been testing this in production environments for the past 5 years, and it's not reliable14:51
aveigashshang: that's fine, but they have to re-address14:51
baoliaveiga, I tried. I have radvd running in both the dhcp namespace and the router space, and I have the route from the router spave have higher preference, and that route is chosen14:51
aveigaor you have to have a really short RA lifetime and remove it completely from the dhcp server14:51
*** jcooley_ has joined #openstack-meeting14:51
aveigado you want to extend the semantics check to only allow advertising RAs from the DHCPv6 namespace when there's also no gateway and only using ULA space?14:52
*** toan-tran has joined #openstack-meeting14:52
aveigabut then that's not goign to be pleasant either, because ULA can be routed14:52
aveigaor we just only support LLA on non-routed networks?14:53
*** jecarey has joined #openstack-meeting14:53
aveigathis is not a simple question14:53
baoliI have a couple of more questions, 1. are the two new subnet modes exposed to the normal users? 2. normally a user launches a VM with nova boot --nic, and the nic will be associated with one of the subnets available in a network. how does the VM user indicate that the VM should be enabled with ipv6 and with which ipv6 subnet?14:53
shshangaveiga, is that question to me, or to baoli?14:53
aveigashshang: to all14:53
*** lsmola has joined #openstack-meeting14:53
*** DinaBelova_ is now known as DinaBelova14:54
aveigabaoli: they don't, this is only network-level configuration14:54
shshangHow are about this, would u plz do me a favor sending all of the use cases to the ML, and we can chew on it.14:54
aveigashshang: I don't think I can even cover them all14:54
*** boris-42_ has quit IRC14:54
shshangit also gives us a chance to think it through.14:54
aveigaI'm sure I will miss a bunch14:54
aveigabut I can try14:54
*** alexey_o has joined #openstack-meeting14:54
shshangJust a couple of them, which will impose challenges on the semantic checks14:54
aveigasc68cal: AI me to cover private network addressing cases on the ML, please14:54
rtuttle1015how about a short-list of the most important use cases14:54
sc68cal#action aveiga cover private network addressing cases on the ML14:55
aveigaand then we can table this to the ML, since we're running out of time14:55
rtuttle1015these are the ones we will allow, and then drop all others with error to user14:55
*** gilr has joined #openstack-meeting14:55
baoliCan someone help me with my second question?14:55
aveigartuttle1015: I want to avoid that14:55
*** xyhuang has joined #openstack-meeting14:56
aveigathat's why we're stuck with broken SLAAC today14:56
shshangaveiga, your points about post configuration change are valid. I don't have answer right now. But I believe we can find a solution/workaround jointly.14:56
rtuttle1015but we can't boil the ocean, and certainly can't address "unknown" use cases14:56
aveigabaoli: if there's a v6 subnet on the network, they get v614:56
aveigathat's simple14:56
rtuttle1015so let's allow those we know, drop all others (for now)14:56
baoliaveiga, thanks.14:56
aveigartuttle1015: agreed, but I'd rather err on allowing them even if they aren't considered "valid"14:56
aveigabetter to let a guilt man go free then put an honest one in prison, no?14:57
*** jcooley_ has quit IRC14:57
aveigaif we want a WARN: in the logs, I'm ok with that14:57
rtuttle1015so what you're really saying is drive the error checking down to the agent (network node), spit a log silently and then go debug later14:57
shshangHow are about we document them, so user at least have a reference of the limitation?14:57
aveigartuttle1015: yes14:57
rtuttle1015I don't like that14:57
aveigashshang: I will, hence the AI14:57
rtuttle1015makes network node do unnecessary work14:58
rtuttle1015checking should be on neutron-server14:58
*** PaulMurray has joined #openstack-meeting14:58
aveigabut it makes unkown cases possible instead of requiring someone to rewrite code to compensate14:58
*** crandquist has joined #openstack-meeting14:58
shshangsc68cal, can we make sure this topic will be in next week's agenda? We need to reach consensus.14:58
aveigaagreed14:58
rtuttle1015+114:58
aveigain any case, I need to drop for another meeting14:59
aveigasee you all on the ML14:59
aveigao/14:59
*** radez_g0n3 is now known as radez14:59
*** aveiga has left #openstack-meeting14:59
shshangLOL14:59
shshangyah, we only have 1 min left14:59
sc68calshshang: yeah we'll recap it next week based on the mailing list convo14:59
shshangYup14:59
shshangwill do14:59
sc68calAlright everyone14:59
*** IlyaE has joined #openstack-meeting14:59
*** roz has joined #openstack-meeting14:59
shshangaveiga, thank you for your points14:59
sc68calthanks for joining, we'll reconvene next week15:00
sc68cal#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Tue Feb  4 15:00:04 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-02-04-13.59.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-02-04-13.59.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-02-04-13.59.log.html15:00
*** shshang has quit IRC15:00
*** rtuttle1015 has left #openstack-meeting15:00
n0ano#startmeeting gantt15:00
openstackMeeting started Tue Feb  4 15:00:37 2014 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
*** absubram has quit IRC15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: gantt)"15:00
openstackThe meeting name has been set to 'gantt'15:00
n0anoanyone here to talk about the scheduler?15:00
*** kevinconway has joined #openstack-meeting15:00
alexey_ome here15:01
*** ArthurBerezin has joined #openstack-meeting15:01
alaskio/15:01
gilrhi15:01
*** bauzas has joined #openstack-meeting15:01
PaulMurrayhi15:01
toan-tranhi15:02
n0anothen let's get started15:02
n0ano#topic no db scheduler15:02
*** openstack changes topic to "no db scheduler (Meeting topic: gantt)"15:02
*** BrianB__ has quit IRC15:02
*** balajiiyer has left #openstack-meeting15:02
n0anohmm, boris doesn't seem to be on, might not be able to talk about this one much15:02
*** dvarga is now known as dvarga|away15:03
*** dvarga|away is now known as dvarga15:03
*** MaxV has quit IRC15:03
alexey_owell, I can substitute boris to some extent15:03
*** nshaikh has left #openstack-meeting15:03
n0anoalexey_o, I thought you might but I didn't want to presume :-), what have you got?15:03
*** Gaston_Severina has joined #openstack-meeting15:04
*** jasondotstar has joined #openstack-meeting15:04
alexey_oI am working on it and I think we are close now15:04
alexey_oit appeared to be not a straitforward task to get rid of compute_nodes table15:05
*** matrohon has quit IRC15:05
*** lsmola has quit IRC15:05
*** mspreitz has joined #openstack-meeting15:06
n0anothe devil is always in the details, can you give a short summary of the problem (emphasis on short)15:06
*** garyk has joined #openstack-meeting15:07
alexey_owell, right now I am hunting a geizenbug that thwarts tempest tests at the gate15:07
*** dcramer_ has joined #openstack-meeting15:08
alexey_oalso one can't just drop compute_nodes table and expect everything to keep working15:08
*** mattgriffin has joined #openstack-meeting15:08
*** egallen has joined #openstack-meeting15:08
alexey_oit is related to services and appears to be joinedloaded quite frequently15:08
n0anoso nothing obvious, just finding the implicit assumptions that are there.15:09
*** Yathi has joined #openstack-meeting15:09
n0anogood luck finding the bugs15:09
toan-tranalexey_o: pls remind me again, how nova conductor work with compute_nodes forked out?15:09
toan-tranand how computes do their frequence update : to nova-condcutor, or scheduler?15:09
alexey_othe last problem can be overcome with some effort15:10
*** paragan has quit IRC15:10
alexey_otoan-tran: the idea was to get rid of writing state changes to compute_nodes table and keep host-related data right in places where it will be needed15:12
*** krotscheck has joined #openstack-meeting15:12
alexey_ofor example in nova-scheduler15:12
n0anoe.g. state the scheduler needs is periodically sent to the scheduler, not the DB15:12
*** jdob has joined #openstack-meeting15:13
alexey_oyes15:13
alexey_oultimately that was supposed to be sent to schedulers15:13
toan-transo nova-compute will send their updates to scheduler? that's quite a quantity15:13
*** markpeek has joined #openstack-meeting15:13
*** sarob has joined #openstack-meeting15:13
toan-tranand also their would be a question of the existence of nova-conductor at this point15:13
alexey_oright now the change does not remove the conductor15:14
alexey_oit still listens to state updates15:14
* mspreitz is still unclear on whether we are talking about one scheduler or multiple15:14
alexey_owhen it receives an update it propagate it to all other entities which are interested in host states15:15
alexey_othat would  be multiple schedulers15:15
mspreitzhow many entities is that?  Which are they?15:15
alexey_oat least one more -- a scheduler15:15
*** MaxV has joined #openstack-meeting15:16
mspreitzAnd there is just one conductor?15:16
*** stevemar has joined #openstack-meeting15:16
alexey_oit is quite possible to have mutliple schedulers so this change was made keeping this in mind15:16
*** stevemar has quit IRC15:16
*** dkranz has joined #openstack-meeting15:16
*** stevemar has joined #openstack-meeting15:16
alexey_oI am unsure whether or not current implementation allows for multiple conductors, but state synchronizatoiin allows for multiple conductors as well15:17
*** nelsnelson has quit IRC15:17
*** egallen has quit IRC15:17
*** AlexF has quit IRC15:17
*** nelsnelson has joined #openstack-meeting15:17
*** sarob has quit IRC15:18
mspreitzAnd how is an update propagated from original receive (a conductor) to the other interested parties?  And why is this better than just pub/sub to all of the interested parties directly in the first place?15:18
*** lsmola has joined #openstack-meeting15:18
*** crandquist has quit IRC15:18
*** IanGovett has joined #openstack-meeting15:18
*** jdob_ has quit IRC15:19
alexey_oas soon as one of the interested parties decides it wants to do sth with state data stored locally it checks a backend to see if there are any fresh updates15:20
*** IanGovett1 has joined #openstack-meeting15:20
mspreitzSo it's polled/pulled, not pushed, to other parties15:21
alexey_oas for pub/sub approach if I get you right our technique does not load the queue as much as state broadcasting15:21
coolsvapn0ano mspreitz alexey_o can this discussion continue on ML instead of meeting?15:21
mspreitzOK with me15:21
n0anoif it needs to go too much deeper we can move to ML, I'm OK with a little more discussion.15:22
*** MaxV has quit IRC15:22
alexey_ook, feel free to ask any questions15:22
n0anomspreitz, maybe you can start a ML thread on your concerns, they certainly seem valid15:22
coolsvapn0ano: I agree, but we are getting stuck at places with no inputs, so just wanted to put a thought15:22
mspreitzMaybe I got the answer, let me see if I got it right..15:22
alexey_oyes, it is polled by those who cares15:23
*** IanGovett has quit IRC15:23
mspreitzThe revised technique wins when updates are more frequent than need to know.  In this situation, the revised technnique does a query when there is a need to know15:23
*** MaxV has joined #openstack-meeting15:23
*** eharney has joined #openstack-meeting15:23
alexey_oyes, it was intended to be used in very large scale clouds15:24
*** sushils has quit IRC15:24
alexey_oby very large I mean thousands of nodes15:24
mspreitzIt's a question not only of scale but how often there is a need to know (scheduling task).15:24
*** dane_ has quit IRC15:24
mspreitzI presume the eval done is accurate.  I think I got my answer.  thanks15:25
n0anoalexey_o, one quick question, last week boris mentioned the demo show bottlenecks not in the scheduler, do you know if these bottlenecks have been identified?15:25
alexey_oat such scale updates will be very frequent, especially comapred to requests for scheduling15:25
toan-tranalexey_o: I remark that there is not a design on how all these things interact with other components15:25
toan-tranon your blueprint/doc page15:25
* mspreitz is not sure why we would expect scheduling rate to not increase with cloud size15:25
toan-trancould you elaborate in a wiki/doc15:25
toan-transo that we can understand how no-db scheduler would interact with all other nova components15:26
alexey_on0ano: unfortunately I don't know15:26
toan-tranand how current message flows would go15:26
alexey_oit is best to ask boris15:26
n0anomspreitz, the scheduling rate increases the but node updates increase (potentially even more)15:26
n0anoalexey_o, tnx15:27
mspreitzn0ano: is that an observation based on data I can see?15:27
alexey_otoan-tran: yes, there is still a lot to document carefully15:27
n0anomspreitz, strictly guess, hard data would be good to have but `I` think the guess is good15:27
mspreitzCan you elaborate on why you expect scheduling rate to increase more slowly than cloud size?15:28
alexey_omspreitz: some time ago I've measured delay in mysql responce to compute node get as a function of the number of compute node records15:28
johnthetubaguyas long as its optional, then I am good with having it as an option for people to try, and we can decide to change the default, once we "are happy" with it15:29
*** ayoung-zZzZzZ has joined #openstack-meeting15:29
*** gokrokve has joined #openstack-meeting15:29
n0anoas cloud size increases the node updates increase, if guests are long lived then the scheduling rate should not increase at the same rate15:29
alexey_oas scheduler issues a request for all compute nodes to be grabbed from db it takes more time to schedule a single instance15:29
johnthetubaguynumber of nodes vs rate of builds vs rate of deletes is going to change what is best, so trying this out seems to make sense to me15:30
*** gokrokve_ has joined #openstack-meeting15:30
*** sacharya has joined #openstack-meeting15:30
mspreitzalexey_o: yes, that makes sense.  I think n0ano is making a different assertion: the (number of calls to scheduler)/time is less than proportional to cloud size15:31
alexey_oyes, I got it wrong the first time15:31
mspreitzn0ano: I do not follow your reply...15:31
n0anomspreitz, no, I think I'm saying (number of call to sched)/time is less than (node updates)/time, especially as the cloud gets larger15:32
mspreitzDo you expect guest lifetime to increase with cloud size?15:32
mspreitznode = host, I take it15:32
n0anomspreitz, yes15:32
mspreitznode update  = guest start, guest stop, or stats, or what?15:33
*** gokrokve has quit IRC15:33
n0anostats is the real concern, start/stop should be directly proportional to scheduler calls15:33
toan-tranmspreitz: I think node update = periodic ms15:34
*** david-lyle has joined #openstack-meeting15:34
mspreitzn0ano: your previus "yes" was response to terminology question, or guest lifetime?15:34
n0anoI think terminology confusions, I'm not really concerned about lifetime15:34
toan-tran = number of nodes (per minute)15:34
*** masayukig has joined #openstack-meeting15:34
mspreitzstats update / time should be proportional to cloud size15:35
toan-tranwhile (call to scheduler) = guesses requesting compute nodes15:35
*** ddutta has joined #openstack-meeting15:35
toan-tranmspreitz: yes15:35
*** terriyu has joined #openstack-meeting15:35
*** jgrimm_ has joined #openstack-meeting15:35
toan-transo I do not see clearly the relation between the two15:36
toan-tranBig servers ==> less update & more call to scheduler15:36
mspreitzAssuming overall utilization stays constant as cloud size grows, and that guest lifetime stays constant as cloud size grows, this implies that guest arrivals/time stays constant as cloud size grows15:36
n0anobut updates/time should increase as the cloud size increases15:37
toan-tranmspreitz: I don't think so15:37
mspreitzsorry, I stated my conclusion wrong15:37
*** pcm has left #openstack-meeting15:37
mspreitzthe implication is that guest arrivals / time will be proportional to cloud size15:37
toan-tranbecause cloud providers will not increase their size if there is a constant guest arrival15:37
toan-tranrember that is scheduler call is when there is a change in a number of instances of clients' applications15:38
mspreitzAssuming overall utilization stays constant as cloud size grows, and that guest lifetime stays constant as cloud size grows, this implies that guest arrivals/time will be proportional to cloud size15:38
toan-transo if guest arrival is constant ==> there is almost no activities on clients' applications15:39
toan-tranit's hard to fantom15:39
mspreitztoan-tran: right.  Read my corrected statement15:39
n0anowell, my concern is the ratio between (update requests)/(scheduler requests), I'm thinking that ratio should be >115:39
*** masayukig has quit IRC15:39
n0anoguys, I hate to cut this short but I think we have to move on, one other topic I'd like to cover today15:40
mspreitzI gave an argument why instance creations / time will be proportional to cloud size.  I think we agree that stats / time will be proportional to cloud size15:40
toan-tranmspreitz +115:40
mspreitzOK with me15:40
YathiIt will be good to see some real experiments and numbers15:41
mspreitzI think Boris showed that the revision is a win at the size he studied15:41
mspreitzand if my expectation is right, that winnage extends to other size15:41
Yathimspreitz, if you have experiments done in your team, please share the results or any paper you may have written15:41
*** troytoman-away is now known as troytoman15:41
*** troytoman is now known as troytoman-away15:41
mspreitzMy group is not studying that question, we are pretty convinced that Boris has a win15:42
mspreitzwe are working on scaling study15:42
n0anomoving on...15:42
*** troytoman-away is now known as troytoman15:42
Yathi+115:42
n0ano#scheduler code forklift15:42
n0anogood news/bad news15:42
n0anogood news - the changes to devstack have been merged so you can now requests the gantt scheduler service15:43
*** troytoman is now known as troytoman-away15:43
n0anobad news - still working on pushing the change to get gantt to pass the unit tests, everytime I think I've got it another (mostly minor) issue crops up15:43
n0anogetting there, it's just a matter of resolving the review issues15:44
*** otherwiseguy has joined #openstack-meeting15:44
coolsvapn0ano: thats great!15:45
ddutta+115:45
*** banix has quit IRC15:45
n0anoactually, the other good news is that gantt passes most of the tempest tests locally (I fail about 100 tests out of 2000 but I get the same failures on a clean devstack build with the nova scheduler so the failures are probably my local setup15:46
n0anoanyone, if anyone want to review the changes at https://review.openstack.org/#/c/68521/ go for it15:46
dduttan0ano: does the scheduler code work standalone right now? without OS dependencies15:46
*** jcooley_ has joined #openstack-meeting15:46
*** sacharya has quit IRC15:47
n0anoddutta, no, that's the next step, to cut all ties to nova, not there yet15:47
dduttacoool!15:47
n0anoI like stepwise progression - first tree -> unit tests -> tempests tests -> independent tree15:48
dduttaagreed!15:48
coolsvapn0ano: I will give a try to gantt tree tempest tests tonight15:49
toan-trann0ano +115:49
*** krotscheck has quit IRC15:50
n0anocoolsvap, one warning, you have to change the SCHEDULER environment variable from it's default, set it to gantt.scheduler.filter_scheduler.FilterScheduler in your localrc15:50
*** aignatov is now known as aignatov_15:50
*** krotscheck has joined #openstack-meeting15:50
n0anoother than that, it should work (I want to know if it doesn't)15:50
*** jprovazn is now known as jprovazn_afk15:51
toan-trann0ano: is there a requirement for nova version?15:51
*** DinaBelova is now known as DinaBelova_15:51
coolsvapn0ano: point noted! thx!15:51
n0anofor the unit tests yes, my local tempest tests have just been against to of tree15:51
n0anos/to of/top of15:51
*** beagles_brb is now known as beagles15:51
*** jcooley_ has quit IRC15:51
Yathin0ano, do you have any documentation of how we can start trying out gantt now ?15:52
n0anodepending upon how far the top of tree changes this could be a problem for tempest, that's why we need to cut the cord as soon as possible15:52
*** amotoki has joined #openstack-meeting15:53
*** DinaBelova_ is now known as DinaBelova15:53
n0anoYathi, no, it's pretty simple, I can sent an email to the ML to tell how to do it (enable gantt, disable n-sch, set SCHEDULER)15:53
*** stanlagun has joined #openstack-meeting15:53
Yathiok cool.. will look for it15:53
n0anoaproaching the top of the hour15:54
n0ano#topic opens15:54
*** openstack changes topic to "opens (Meeting topic: gantt)"15:54
n0anoanyone have anything else?15:54
*** oubiwann_ has quit IRC15:54
mspreitzML about gantt will be good15:54
YathiRequest to review two patches for Solver scheduler15:54
mspreitzpointers please15:54
n0anoYathi, links?15:54
Yathi#link https://review.openstack.org/#/c/46588/15:55
Yathi#link https://review.openstack.org/#/c/70654/15:55
*** egallen has joined #openstack-meeting15:55
mspreitzthanks15:55
n0anoYathi, tnx15:55
dduttaand the API patches https://review.openstack.org/#/c/62557/15:55
dduttasorry I meant API for group instance15:55
toan-tranand the Policy Based Scheduler patch: https://review.openstack.org/#/c/6138615:55
toan-tran:)15:55
ddutta:)15:55
Yathi:)15:55
n0anomspreitz, there have been multiple ML threads on gantt and there's a launchpad about it at https://etherpad.openstack.org/p/icehouse-external-scheduler15:56
mspreitzI meant the instr on how to test15:56
n0anomspreitz, ah, sure NP15:56
* n0ano I guess I really have to write today :-)15:56
Yathin0ano, I may have missed this from the previous meetings, how will the new patches to scheduler, like the Solver scheduler, policy-based scheduler be merged with gantt ?15:57
Yathiafter gantt merging, before, and re-merge with gantt ?15:57
n0anothe current gantt tree is a preview, after we get it working we'll re-create the tree, apply the changes we now know get it working (lots of work for me) and then cut to gantt15:58
*** oubiwann_ has joined #openstack-meeting15:58
Yathiok cool Thanks15:59
n0anoOK guys, tnx and we'll talk again15:59
n0ano#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Tue Feb  4 15:59:37 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-02-04-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-02-04-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-02-04-15.00.log.html15:59
*** gilr has quit IRC16:00
*** roz has left #openstack-meeting16:00
*** alexey_o has quit IRC16:00
*** PaulMurray has left #openstack-meeting16:01
*** tanisdl has joined #openstack-meeting16:01
*** Gaston_Severina has quit IRC16:01
*** atiwari has joined #openstack-meeting16:01
*** xazel is now known as enykeev16:02
*** mrodden has quit IRC16:03
*** hk_peter has joined #openstack-meeting16:04
*** samcdona has joined #openstack-meeting16:04
*** IlyaE has quit IRC16:05
*** pablosan has quit IRC16:06
*** markvan_ has quit IRC16:07
*** krotscheck is now known as krotscheck_sick16:07
*** e-vad_ is now known as e-vad16:08
*** pablosan has joined #openstack-meeting16:08
*** jcooley_ has joined #openstack-meeting16:09
*** markvan has joined #openstack-meeting16:09
*** SumitNaiksatam has quit IRC16:09
*** xuhanp has quit IRC16:11
*** msdubov has joined #openstack-meeting16:12
*** doron is now known as doron_afk16:13
*** emagana has joined #openstack-meeting16:13
*** egallen has quit IRC16:13
*** mrodden has joined #openstack-meeting16:16
*** banix has joined #openstack-meeting16:16
*** mdomsch has joined #openstack-meeting16:17
*** thouveng has quit IRC16:17
*** doron_afk has quit IRC16:17
*** toan-tran has quit IRC16:18
*** Leonr has joined #openstack-meeting16:19
*** egallen has joined #openstack-meeting16:19
*** terriyu has quit IRC16:20
*** prad_ has joined #openstack-meeting16:20
*** sacharya has joined #openstack-meeting16:21
*** sbalukoff has quit IRC16:22
*** hemna has joined #openstack-meeting16:23
*** egallen has quit IRC16:24
*** jjmb has joined #openstack-meeting16:25
*** egallen has joined #openstack-meeting16:26
*** absubram has joined #openstack-meeting16:26
*** emagana has quit IRC16:26
*** absubram has quit IRC16:26
*** hk_peter has quit IRC16:27
*** pablosan has quit IRC16:27
*** xyhuang has quit IRC16:27
*** baoli has quit IRC16:28
*** egallen has quit IRC16:30
*** emagana has joined #openstack-meeting16:31
*** pablosan has joined #openstack-meeting16:31
*** Yathi has quit IRC16:31
*** egallen has joined #openstack-meeting16:31
*** banix has quit IRC16:32
*** banix has joined #openstack-meeting16:33
*** IlyaE has joined #openstack-meeting16:34
*** topol has joined #openstack-meeting16:34
*** matrohon has joined #openstack-meeting16:34
*** hemna has quit IRC16:34
*** masayukig has joined #openstack-meeting16:35
*** sankarshan_away is now known as sankarshan16:35
*** SumitNaiksatam has joined #openstack-meeting16:37
*** thuc has joined #openstack-meeting16:39
*** lsmola has quit IRC16:39
*** masayukig has quit IRC16:39
*** belmoreira has quit IRC16:39
*** thuc_ has joined #openstack-meeting16:40
*** jcooley_ has quit IRC16:40
*** sankarshan is now known as sankarshan_away16:41
*** ayoung-zZzZzZ is now known as ayoung16:41
*** baoli has joined #openstack-meeting16:41
*** banix has quit IRC16:41
*** emagana has quit IRC16:41
*** markwash has joined #openstack-meeting16:41
*** markmcclain has joined #openstack-meeting16:42
*** thuc has quit IRC16:43
*** fnaval has joined #openstack-meeting16:45
*** dvarga is now known as dvarga|away16:45
*** dvarga|away is now known as dvarga16:45
*** SergeyLukjanov is now known as SergeyLukjanov_a16:46
*** pablosan has quit IRC16:49
*** pablosan has joined #openstack-meeting16:49
*** marun has joined #openstack-meeting16:50
*** mestery has joined #openstack-meeting16:51
*** mestery has quit IRC16:51
*** lsmola has joined #openstack-meeting16:51
*** AlexF has joined #openstack-meeting16:51
*** dprince has quit IRC16:52
*** mestery has joined #openstack-meeting16:53
*** thedodd has joined #openstack-meeting16:54
*** afazekas has quit IRC16:55
*** akuznetsov has joined #openstack-meeting16:56
*** boris-42_ has joined #openstack-meeting16:57
boris-42_hughsaunders julienvey stannie msdubov jaypipes Rally meeting17:00
*** redixin has joined #openstack-meeting17:00
hughsaunders\o boris-42_17:00
boris-42_#startmeeting Rally17:00
openstackMeeting started Tue Feb  4 17:00:32 2014 UTC and is due to finish in 60 minutes.  The chair is boris-42_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: Rally)"17:00
openstackThe meeting name has been set to 'rally'17:00
*** AlexF has quit IRC17:00
msdubovhi17:00
*** boris-42_ is now known as boris-4217:00
*** akuznetsov has quit IRC17:00
*** jhenner1 has quit IRC17:00
*** nkhare has joined #openstack-meeting17:01
boris-42nkhare hi17:01
nkhareboris-42, hi17:01
boris-42akscram meeting time17:01
nkharehello everyone17:01
miarmakhi17:01
boris-42so okay nice to see you guys let's disscuss what we have17:01
boris-421. Work around Rally WIKI & docs17:01
boris-422. Scenario runner refactoring17:02
*** jcoufal_ has joined #openstack-meeting17:02
*** jcoufal has quit IRC17:02
boris-422. Ssh refactoring17:02
*** zehicle has joined #openstack-meeting17:02
*** ArthurBerezin has left #openstack-meeting17:02
boris-424. Mulitnode / LXC engines17:02
*** mestery has quit IRC17:02
*** akuznetsov has joined #openstack-meeting17:02
boris-425. Atomic operation times17:03
*** mdbooth has quit IRC17:03
boris-426. Free discussion17:03
*** I159 has quit IRC17:03
boris-42#topic 1. Work around Rally WIKI & docs17:03
*** mestery has joined #openstack-meeting17:03
*** boris-42 is now known as boris-42_17:04
boris-42_#topic 1. Work around Rally WIKI & docs17:04
*** openstack changes topic to "1. Work around Rally WIKI & docs (Meeting topic: Rally)"17:04
boris-42_lol=)17:04
boris-42_So I was concentrate on first page of Rally wiki page17:04
boris-42_I added tons of different diagrams https://wiki.openstack.org/wiki/Rally17:04
boris-42_and will continue adding to describe how Deploy stuff and Benchmark stuff works in details17:05
boris-42_Then I am going to refactor Join Rally team (part)17:05
*** mestery has quit IRC17:05
boris-42_to describe in more human readable form how to join Rally team17:05
boris-42_and then I will concentrate on pages about installation and usage of rally17:05
boris-42_we have couple of new features that are not covered by wiki17:06
*** mestery has joined #openstack-meeting17:06
*** Mandell_ has quit IRC17:06
boris-42_e.g. --use stuff / deploy engines (e.g. devstack)17:06
boris-42_atomic times and how to write benchmarks17:06
*** niteshselkari has joined #openstack-meeting17:06
boris-42_and make it overall more clear and simple17:06
redixinDevstackEngine is not covered by wiki?17:06
*** enykeev has left #openstack-meeting17:07
*** terriyu has joined #openstack-meeting17:07
boris-42_redixin it is not covered in that way that somebody will see it and say YEP I would like to use this stuff17:07
boris-42_=)17:07
*** hdd has joined #openstack-meeting17:07
boris-42_so I will try to refactor all this stuff17:07
*** banix has joined #openstack-meeting17:08
boris-42_does anybody has any question?17:08
*** ddutta has quit IRC17:08
redixinno17:08
boris-42_ok let's move to next topic17:09
boris-42_#topic 2. Scenario runner refactoring17:09
*** openstack changes topic to "2. Scenario runner refactoring (Meeting topic: Rally)"17:09
boris-42_msdubov could you share pls with updates17:09
redixinI saw that patch. It works :)17:10
boris-42_redixin lol=)17:10
boris-42_redixin amazing=)17:10
msdubovSo its actually the work started by Boris and continued by me. We've issued two patches on this17:10
*** gyee has joined #openstack-meeting17:10
*** mestery_ has joined #openstack-meeting17:10
msdubov1. https://review.openstack.org/#/c/69886/, where we simplify the original ScenarioRunner class17:10
msdubovand move some functionaly for creating users/performing cleanup to separate context classes17:10
*** AlanClark has joined #openstack-meeting17:10
*** gyee has quit IRC17:11
*** mestery_ has quit IRC17:11
msdubov2. https://review.openstack.org/#/c/70771/, where we re-implement different benchmark launching strategies in subclasses instead of ScenarioRunner methods17:11
boris-42_msdubov actually it is not simplification (as well we are using context, so now in any case we will perform cleanup)17:11
msdubovwhich allows to eliminate the complicated "if"s logic17:11
*** mestery has quit IRC17:11
boris-42_msdubov that was serious bug actually as well..17:11
msdubovboris-42_ Yep but it is now e.g. not called in multiprocessing Pool, so it simplifies everything a bit17:12
*** egallen has quit IRC17:12
*** mestery has joined #openstack-meeting17:12
*** neelashah has joined #openstack-meeting17:12
msdubovI tested these patches on devstack (launching NovaServers.boot_and_delete_server with small load) and it worked for me17:12
msdubovSo pls review those pathces17:12
msdubovAs the next step I need to rebase lots of my code pending review on this17:13
boris-42_hughsaunders julienvey stannie  could you take a look at those patches as well?17:13
*** marcoemorais has joined #openstack-meeting17:13
*** gyee has joined #openstack-meeting17:13
msdubovFor example, the DummyEngine refactoring which allows it to work with predefined users instead of generated ones17:13
*** sarob has joined #openstack-meeting17:13
boris-42_msdubov ok thanks for updates17:14
boris-42_#topic  3. Ssh refactoring17:14
*** openstack changes topic to "3. Ssh refactoring (Meeting topic: Rally)"17:14
redixinhttps://review.openstack.org/#/c/68063/17:14
redixinapprove it pls =)17:14
boris-42_redixin could you explain in couple of words what you done?)17:15
*** slagle has quit IRC17:15
*** rakhmerov has quit IRC17:15
boris-42_redixin and how to test it (for others)17:15
redixinjust cherry-pick it, and try to make anything that uses ssh access (deploy or run-task-in-instance scenario)17:16
boris-42_redixin ok will do ^17:16
boris-42_redixin and why this change is required?17:16
redixinit is not required, but with this patch using ssh in not painful17:17
boris-42_redixin ok =))17:17
boris-42_redixin so just cleanup of code17:17
redixinapi changes17:17
boris-42_#topic 4. Multinode / LXC engines17:17
*** openstack changes topic to "4. Multinode / LXC engines (Meeting topic: Rally)"17:17
redixinmm this pathces is ready for review17:18
redixinhttps://review.openstack.org/#/c/56222/17:18
redixinhttps://review.openstack.org/#/c/57240/17:18
redixintons of test deployment was done with this engines17:18
boris-42_redixin ok I will review code17:18
boris-42_redixin one more time17:18
boris-42_redixin and merge if everything is ok17:19
redixinok thanks17:19
boris-42_to others these patches allows us to create Multinode deployments17:19
boris-42_at this moment we are supporting only DevStack17:19
boris-42_but in future there will be as well Fuel17:19
redixinbtw17:20
redixinFuelEngine is ready for teview17:20
redixinhttps://review.openstack.org/#/c/61963/17:20
boris-42_and with LXCEngine we could get very very fast cloud at big scale on small amount of servers17:20
boris-42_(even one)17:20
boris-42_something like 200mb RAM is required per 1 compute node17:20
*** jhenner has joined #openstack-meeting17:20
*** sarob has quit IRC17:20
boris-42_#topic 5. Atomic operation times17:21
*** ftcjeff has joined #openstack-meeting17:21
*** openstack changes topic to "5. Atomic operation times (Meeting topic: Rally)"17:21
boris-42_stannie hi, could you share updates?17:21
*** AlexF has joined #openstack-meeting17:21
*** mrunge has quit IRC17:21
boris-42_stannie btw are you here?)17:21
redixinI thought this work was completed17:21
boris-42_so seems like stannie is not yet here17:22
boris-42_so let me share with updates17:22
boris-42_we successfully add support of atomic times for actions17:22
boris-42_this allows us to measure times of all atomic actions17:22
boris-42_e.g. in Nova.snapshot scneario17:22
boris-42_we have next actions: 1) boot VM, snapshot VM, delete VM, start from snapshot VM, delete snapshot, delete VM17:23
boris-42_so it becomes really unclear how long works each of operations17:23
*** salv-orlando has quit IRC17:23
*** bauzas has quit IRC17:24
boris-42_so with this patch https://review.openstack.org/#/c/69828/17:24
boris-42_we will store/mesure all times of all atomic actions in DB17:24
boris-42_and this one will allow us to see them in CLI https://review.openstack.org/#/c/70362/17:24
boris-42_So this finish works around atomic actions17:25
boris-42_nkhare are you around?17:25
*** jasondotstar has quit IRC17:25
nkhareyes17:25
boris-42_#topic Keystone benchmarking17:25
*** openstack changes topic to "Keystone benchmarking (Meeting topic: Rally)"17:25
*** salv-orlando has joined #openstack-meeting17:26
boris-42_nkhare could you share some info about your work around keystone benhcmarking17:26
nkharesure. with the current code in review I was able to do create user benchmark17:26
*** jlibosva has quit IRC17:26
nkharecurrently writing down the benchmark for pki vs UUID17:27
boris-42_nkhare and you are add as well "authentication" benchhmark?17:27
boris-42_you added*17:27
nkhareyes17:27
*** oubiwann_ has quit IRC17:28
*** nadya has joined #openstack-meeting17:28
*** pradipta has joined #openstack-meeting17:28
*** nadya is now known as Guest9514117:28
boris-42_nkhare nice17:28
nkharewould be writing down the user-story section once I finish PKI vs UUID benchmark17:28
nkharefor keystone17:29
boris-42_nkhare ok nice, it will be very interesting to see17:29
boris-42_nkhare btw one small question about patch, do we actually need uitls and authenticate files17:29
boris-42_nkhare I mean in this case they could be just merged17:30
boris-42_nkhare in one single file authenticate17:30
nkhareboris-42_, I don't recall why I did that may be just following other benchmarks17:31
*** AlexF has quit IRC17:31
nkharewe can merge them17:31
boris-42_nkhare yep but in another cases there is a reason17:31
boris-42_nkhare because there are atomic actions (e.g. create_volume, delete_volume) and you would like to build on top of them scenarios17:32
*** mdurnosvistov_ has joined #openstack-meeting17:32
boris-42_nkhare and in this case I don't see any reason to make it complex17:32
nkhareboris-42_, as we are evolving the keystone benchmarks so may be we need but for now we can merge them17:33
*** jhenner has quit IRC17:33
hughsaunderscould authenticate be part of the keystone scenario?17:33
boris-42_hughsaunders +117:33
*** jjmb has quit IRC17:34
*** mestery_ has joined #openstack-meeting17:34
*** amotoki has quit IRC17:34
*** jcooley_ has joined #openstack-meeting17:34
nkhareboris-42_, as we discussed earlier we might might want to authenticate with other services.17:34
*** marcoemorais has quit IRC17:35
*** jrist has quit IRC17:35
nkhareso we decided to have as different scenario17:35
*** egallen has joined #openstack-meeting17:35
*** masayukig has joined #openstack-meeting17:36
*** rakhmerov has joined #openstack-meeting17:36
boris-42_nkhare hughsaunders  actually yes it is not absolutely 100% keystone stuff… in case when we are using pyhon clients from different project..17:36
*** AlexF has joined #openstack-meeting17:36
hughsaundersok17:36
boris-42_nkhare so i think that it will be enough to merge utils with authenticate (because I don't see any complex logic)17:37
boris-42_nkhare that should be splitted17:37
nkhareboris-42_, ok. I'll merge them17:37
boris-42_nkhare thanks17:37
*** mestery has quit IRC17:38
boris-42_#topic free discussion17:38
*** openstack changes topic to "free discussion (Meeting topic: Rally)"17:38
redixinrally deployment use VS rally use deployment17:39
boris-42_does anybody has something to say?) some ideas? any questions?)17:39
miarmakyes. Tempest verification =)17:39
boris-42_redixin holy-war!!!17:39
boris-42_ouch17:39
boris-42_ffff17:39
hughsaundersredixin: which do you prefer?17:39
redixinI always do 'rally deployment use deploy_id' >_<17:39
boris-42_I don't use always "use", but when I use use ..17:40
hughsaundershaha17:40
redixin-_-17:40
*** bdpayne has joined #openstack-meeting17:40
hughsaundersmaybe we could have a cli alias for redixin17:40
*** masayukig has quit IRC17:41
redixinmiarmak: what about tempest?17:41
boris-42_#topic tempest integration17:41
*** openstack changes topic to "tempest integration (Meeting topic: Rally)"17:41
hughsaundersthough that would involve duplicating all the args.17:41
boris-42_sdague hi!=)17:41
miarmakThere is a bp: https://blueprints.launchpad.net/rally/+spec/tempest-verification17:41
*** sarob has joined #openstack-meeting17:41
boris-42_miarmak btw I will add some extra info=)17:42
*** pnavarro has quit IRC17:42
*** sandywalsh_ has quit IRC17:42
miarmakboris-42_: in the bp description?17:42
boris-42_miarmak yep about a lot of tasty stuff17:43
*** hemna has joined #openstack-meeting17:43
*** sandywalsh has joined #openstack-meeting17:43
miarmakboris-42_: ok, it would ve nice)17:43
miarmaknow, there is only 1 string)17:43
boris-42_miarmak so I mean as first step we are going to add command like rally verify install (that installs tempest)17:43
*** SpamapS_ is now known as SpamapS17:43
boris-42_miarmak and rally verify run (that runs tempest against cloud)17:43
miarmakyeah, There is wip patch: https://review.openstack.org/#/c/7013117:44
*** jasondotstar has joined #openstack-meeting17:44
miarmakplease, take a look17:44
boris-42_redixin msdubov hughsaunders  killem'all17:44
*** jcooley_ has quit IRC17:44
boris-42_I mean that patch=)17:44
*** akuznetsov has quit IRC17:44
miarmak=)17:44
*** AlexF has quit IRC17:44
boris-42_So let me share my new ideas about tempest verification17:44
boris-42_1) We should store results in DB17:44
boris-42_2) We should be able to run only sets of tests (that are already procreated), e.g. rally verify nova/cinder/small/medium/big/latest_failed17:45
*** tshirtma1 has joined #openstack-meeting17:45
*** gpocente1 has joined #openstack-meeting17:45
*** sbalukoff has joined #openstack-meeting17:45
*** marekd has joined #openstack-meeting17:46
*** Ajaeger has joined #openstack-meeting17:46
*** fbo has quit IRC17:46
*** tshirtman has quit IRC17:46
*** gpocentek has quit IRC17:46
*** julienvey has quit IRC17:46
*** ZangMingJie has quit IRC17:46
*** creiht has quit IRC17:46
boris-42_3) we should add command rally verify list/show (that will list all verification stuffs, and  show that will show detailed info and results)17:46
*** BStokes has quit IRC17:46
*** stannie has quit IRC17:46
*** IlyaE has quit IRC17:46
*** sarob has quit IRC17:46
*** BStokes has joined #openstack-meeting17:46
boris-42_4) And one thing that will be super interesting for catching races rally verify run -N <sets>17:47
*** creiht has joined #openstack-meeting17:47
boris-42_that will run N times specified sets17:47
boris-42_that's all17:47
*** MaxV has quit IRC17:47
hughsaunderscould tempest be a special case of a benchmark?17:47
boris-42_hughsaunders how?)17:47
*** ZangMingJie has joined #openstack-meeting17:47
redixinrun tempest test N times and measure times17:48
redixinas usual17:48
hughsaundersyeah17:48
*** niteshselkari has quit IRC17:48
boris-42_hughsaunders yep why not17:48
*** Gordonz has joined #openstack-meeting17:48
*** stannie has joined #openstack-meeting17:48
boris-42_hughsaunders tempest as a becnhmark scenario lol=)17:48
*** jrist has joined #openstack-meeting17:48
*** burt1 has joined #openstack-meeting17:49
*** julienvey has joined #openstack-meeting17:49
*** otherwiseguy has quit IRC17:49
hughsaunderssame mechanism, for an alternative purpose17:49
boris-42_btw then probably part of verification logic could be moved to benchmark scneario?17:49
*** IlyaE has joined #openstack-meeting17:49
boris-42_so it could be parametrized17:49
*** sarob has joined #openstack-meeting17:49
boris-42_and we are able to specify times17:49
boris-42_and even make a load17:49
*** jhenner has joined #openstack-meeting17:49
boris-42_okay seems like a nice idea17:50
boris-42_I will add this to BP17:50
boris-42_any other great ideas hughsaunders  redixin ?17:50
redixinno17:50
*** akuznetsov has joined #openstack-meeting17:50
hughsaundersnope17:51
boris-42_#topic holy-wars17:51
*** openstack changes topic to "holy-wars (Meeting topic: Rally)"17:51
hughsaundershaha17:51
*** AlexF has joined #openstack-meeting17:51
hughsaundersvim +117:51
boris-42_ffff17:51
*** akuznetsov has quit IRC17:51
boris-42_sublime is better17:51
miarmakPyCharm17:51
msdubov"deployment use" vs. "use deployment"17:52
redixincat | sed | awk17:52
hughsaundersjq17:52
boris-42_omg maniacs!17:52
boris-42_nano!!17:52
boris-42_the most awful stuff17:52
boris-42_=)17:52
hughsaundersmsdubov: use deployment makes sense, once use is implemented for tasks17:52
hughsaundersthen can have use task17:52
boris-42_hughsaunders yep17:53
boris-42_hughsaunders that was idea17:53
msdubovhughsaunders yep I know but I always want to do deployment use as redixin =)17:53
boris-42_but there is already --use17:53
boris-42_msdubov ^17:53
*** Guest95141 has quit IRC17:53
boris-42_rally deployment create --use17:53
boris-42_=)17:53
redixin--use must be set bu default17:53
*** Gordonz has quit IRC17:53
*** amcrn has joined #openstack-meeting17:53
hughsaundersredixin: I argued for that but was overruled17:53
boris-42_--don't_use17:53
boris-42_lol17:54
*** esker has quit IRC17:54
hughsaundershowever --no-use is a good option17:54
*** lbragstad has joined #openstack-meeting17:54
*** elo1 has joined #openstack-meeting17:54
*** salv-orlando_ has joined #openstack-meeting17:54
boris-42_rally task --burn-your-cloud17:54
boris-42_=))17:54
*** esker has joined #openstack-meeting17:54
*** dprince has joined #openstack-meeting17:54
*** gokrokve_ has quit IRC17:54
hughsaundersmaybe will submit a review for --no-use and see if it gets in..17:54
*** mspreitz has quit IRC17:55
boris-42_hughsaunders btw17:55
*** fbo has joined #openstack-meeting17:55
boris-42_hughsaunders I forgot to ask about CONF stuff17:55
*** oubiwann_ has joined #openstack-meeting17:55
hughsaundersboris-42_: in progress17:55
boris-42_hughsaunders pls don't make one patch on 1k lines=)17:55
hughsaundershttps://github.com/hughsaunders/rally/compare/review?expand=117:55
*** resker has joined #openstack-meeting17:55
hughsaundersthats the cinder one17:55
*** akuznetsov has joined #openstack-meeting17:55
*** gokrokve_ has joined #openstack-meeting17:55
hughsaunderswill do similar for nova, then submit review17:55
boris-42_hughsaunders ok nice17:55
boris-42_btw17:55
boris-42_one detail17:56
*** jrist has quit IRC17:56
boris-42_hughsaunders you should use group17:56
boris-42_registre_group ..17:56
*** IlyaE has quit IRC17:56
*** salv-orlando_ has quit IRC17:56
hughsaundersok will do17:56
*** esker has quit IRC17:57
boris-42_hughsaunders and what is the proper name for group?17:57
*** dvarga is now known as dvarga|away17:57
*** dvarga|away is now known as dvarga17:57
hughsaundersone per benchmark type?17:57
*** rossk has joined #openstack-meeting17:57
*** salv-orlando_ has joined #openstack-meeting17:57
*** salv-orlando has quit IRC17:57
*** salv-orlando_ is now known as salv-orlando17:57
boris-42_benchmarks17:57
hughsaundersok, one group "benchmarks" then prefix each option with benchmark type17:58
boris-42_and inside nova_crate_sleep, nova_delete_sleep17:58
boris-42_yep17:58
hughsaunderswill do17:58
boris-42_hughsaunders thanks17:58
boris-42_hughsaunders btw pretty important change=)17:58
hughsaundersyeah, meant to get it done today, but will have to be tomorrow now17:58
*** harlowja_away is now known as harlowja17:59
boris-42_hughsaunders np17:59
boris-42_hughsaunders btw we will need to make a couple of patches (not only for benchmarks)17:59
boris-42_hughsaunders to make them configurable..17:59
*** comay has joined #openstack-meeting17:59
*** AlexF has quit IRC17:59
hughsaunders?17:59
boris-42_ok times to end this meeting17:59
*** dstanek has joined #openstack-meeting17:59
boris-42_hughsaunders I will show you18:00
hughsaunderscan continue tomorrw18:00
* ayoung sneaks in18:00
hughsaundersbye18:00
boris-42_#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Tue Feb  4 18:00:14 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-02-04-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-02-04-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-02-04-17.00.log.html18:00
ayoungKEYSTONE18:00
*** KurtMartin is now known as kmartin18:00
topolo/18:00
marekdo/18:00
dolphmbknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog: p/18:00
atiwariHi18:00
lbragstadhey18:01
bknudsondolphm: present18:01
jaypipeso/18:01
dstaneko/18:01
topolo/18:01
dolphmhttps://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:01
dolphm#startmeeting keystone18:01
openstackMeeting started Tue Feb  4 18:01:29 2014 UTC and is due to finish in 60 minutes.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
*** morganfainberg_Z is now known as morganfainberg18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
*** fabiog has joined #openstack-meeting18:01
dolphm#topic Reminder: Icehouse feature proposal freeze February 18th18:01
*** openstack changes topic to "Reminder: Icehouse feature proposal freeze February 18th (Meeting topic: keystone)"18:01
ayoungGuten Morgan18:01
fabiogHello18:01
dolphmthat's 12 days to propose a mergeable patch for blueprints, or it doesn't ship in icehouse18:02
morganfainbergmornin all18:02
dolphmerr 14 days because math18:02
dolphmmorganfainberg: good morning18:02
*** nkhare has quit IRC18:02
morganfainbergrumors of my demise have been greatly exagerated18:02
topoldefine mergable...18:02
dolphmtopol: complete18:02
ayoungtopol, not -1 from Jenkins18:02
*** marcoemorais has joined #openstack-meeting18:02
topolwhat if someone asks for *more* test cases?18:02
dolphmayoung: a half baked patchset with a +1 from jenkins deserves to be bumped18:03
ayoungthat too18:03
dolphmtopol: refinement is fine, if it's got a long way to go, then it shouldn't ship18:03
ayoungbut Jenkins complaining is a sure fine no-go18:03
dolphmayoung: ++18:03
* topol mine is passing jenkins... Im golden18:03
dolphmif you're breaking devstack or tempest or something, it's too late to resolve cross-project dependencies in icehouse18:03
bknudsonjenkins complains about a lot of things that are unrelated18:03
dolphmtransients excluded18:03
*** rossk has quit IRC18:03
*** rossk has joined #openstack-meeting18:04
*** marcoemorais has quit IRC18:04
atiwaridolphm, thoughts on adding link:https://review.openstack.org/#/c/69145/4 for I3?18:04
morganfainbergif you're rechecking for known bugs, it's "mergable"18:04
* stevemar is late18:04
*** nati_ueno has joined #openstack-meeting18:04
morganfainberg(elasticrecheck?)18:04
dolphmat this point there are several blueprints that i'm becoming paranoid about18:04
dolphmanything still Not Started as of next tuesday i'll likely be retargeting to juno18:05
* topol please don't say audit. please dont say audit...18:05
dolphmhttps://launchpad.net/keystone/+milestone/icehouse-318:05
ayoungAny objection to use pushing through a change that allows notifications to go over oslo messaging instead of RPC.  Turns out it is kindof important18:05
*** otherwiseguy has joined #openstack-meeting18:05
dolphmtopol: audit is started!18:05
*** jlibosva has joined #openstack-meeting18:05
topol:-)18:05
ayoungnot sure if we BPed it or not....jamielennox was working on it.  and audit will need it18:05
*** SergeyLukjanov_a is now known as SergeyLukjanov18:05
*** jamielennox has joined #openstack-meeting18:05
*** mattgriffin1 has joined #openstack-meeting18:05
morganfainbergdolphm, ephemeral pki tokens need ayoung's revocation stuff.  i'll be reviewing the revocation stuff and starting on it (unless it watch rolled into the revocation events)18:06
ayoungjamielennox, we have a BP for the notifications Messaging work?18:06
morganfainbergs/watch/was18:06
jaypipesayoung: as long as the log verbosity and false-positive exception logging in oslo.messaging is fixed.18:06
dolphmatiwari: it's a core api change post m2, so target juno18:06
dolphmjuno-m2, specifically18:06
*** nacim has quit IRC18:06
dolphmmorganfainberg: ++ at least get it in review based on ayoung's work18:06
dolphmmorganfainberg: good way to test it as well18:06
ayoung++18:07
dolphmmorganfainberg: if devstack can run with PKI without persisting tokens, then revocations events are fairly solid18:07
morganfainbergand parallel testing likely needs to be punted for J1 - i can do some of the scafolding in place post feb 18, because it is test restructuing. but bigger changes - likely will land there18:07
atiwariok18:07
morganfainbergdolphm, ++18:07
*** mattgriffin has quit IRC18:07
dolphmmorganfainberg: so PLEASE get that going that'll be awesome :D18:07
dhellmannjaypipes: see my email to the -dev list from a little bit earlier today on that logging issue18:07
dolphmmorganfainberg: will retarget now18:07
jaypipesdhellmann: I did.18:07
morganfainbergdolphm, ayoung, since the kvs refactor and other stuff is up for review now. ephemeral is my last BP that hasn't got code up18:07
ayoungrevocation events getting solid.  yoriksar did such a good review I made him a co-author18:07
jamielennoxayoung: blueprint oslo-messaging18:07
morganfainbergayoung, awesome!!!18:07
dolphmbknudson: s3 token is unblocked now :)18:08
dhellmannjaypipes: cool18:08
bknudsondolphm: great... I think I need to update the requirements and then get that to keystone then update keystone.18:08
dolphmayoung: awesome18:08
ayounghttps://blueprints.launchpad.net/keystone/+spec/oslo-messaging18:09
morganfainbergdolphm, can https://blueprints.launchpad.net/keystone/+spec/role-assignments-unified-sql be done behind the scenes since it's not really a "feature" and not api impacting?18:09
dolphmbknudson: ++ you mean bump our dep to >0.5.0 ?18:09
dstaneki have a few commits coming today or tomorrow for blueprint password-rotation18:09
bknudsondolphm: right18:09
*** jrist has joined #openstack-meeting18:09
ayoungdolphm, we'll need client changes to be able to make it work.  My current plan is to get the code merged into server, then clone the module.py file into client and integrate it there18:09
dolphmdstanek: yay!18:09
stevemardstanek, lookin forward to it18:09
*** msdubov has left #openstack-meeting18:09
dolphmjamielennox: is oslo-messaging realistic for icehouse?18:10
dolphmthat seems ambitious :)18:10
ayoungdolphm, based on the glance implementation, I would say yes18:10
jamielennoxdolphm: it's pretty much done - it's a simple set of patches18:10
dolphmjamielennox: good to hear - when will we see reviews? :D18:10
ayoungits dropping the dep on oslo notify and cloning the glance patch, single file.18:10
*** miarmak has quit IRC18:10
lbragstadjamielennox: have any issues with the self.host we talked about a few nights ago?18:10
lbragstadand publisher_ids?18:11
jamielennoxit might be worth rethinking later how we handle notifications but for now to do a swap that is just the same functionality is pretty simple18:11
*** akuznetsov has quit IRC18:11
jamielennoxdolphm: starts here: https://review.openstack.org/#/c/70661/18:11
dolphmhenry-nash isn't around, but does anyone know of progress against https://blueprints.launchpad.net/keystone/+spec/role-assignments-unified-sql ?18:11
ayoungspeaking of notifications:  do we need to break change password out into its own notification? We revoke tokens based on that, and it is one of the few events that are not processed based on notifications18:11
jamielennoxbknudson: addressed your comment on https://review.openstack.org/#/c/70661/ can you have another look18:12
dolphmjamielennox: can you add links to the bp and update the bp status? the bot appears to be dead18:12
jamielennoxdolphm: will do18:12
jaypipesjamielennox: did you see my patch to avoid using a global constant for dependency injection?18:12
morganfainbergdolphm, i think we can do that behind the scenes18:12
stevemardolphm, no idea, i could try to see if henry is around18:12
morganfainbergdolphm, it should have no API impact.  in fact if it does, we are doing it wrong18:12
jamielennoxlbragstad: no, it went fairly smoothly once i dropped it18:12
topolI just pinged henry18:12
jamielennoxjaypipes: just woke up :)18:13
lbragstadjamielennox: good deal18:13
stevemarthanks topol18:13
dolphmmorganfainberg: but a lot of work would be easier if that was done18:13
jaypipesjamielennox: no worries :)18:13
*** marcoemorais has joined #openstack-meeting18:13
morganfainbergdolphm, aye18:13
ayoungjaypipes,   he's in Brisbane...he's  hard core18:13
jamielennoxjaypipes: i'll have a look soon though because i'm not sure what you were going for with your comment18:13
morganfainbergayoung, but i mean that can probably be an I3 target vs feb 18?18:13
jaypipesjamielennox: I pushed a patch with example code.18:13
topolor he cant sleep18:13
morganfainbergdolphm, ^ not ayoung18:13
jaypipesjamielennox: feel free to use, or not. :)18:13
morganfainbergit's... cleanup that looks like a BP vs. a "feature"18:14
dolphmmorganfainberg: ah; it is a giant refactor though18:14
*** sarob has quit IRC18:14
morganfainbergdolphm, fair enough.18:14
dolphmmorganfainberg: the goal of feature proposal freeze is to avoid bugs, and have more time to review, identify and fix them18:14
*** sarob has joined #openstack-meeting18:15
morganfainbergdolphm, that is the one big bit of cleanup i think i'll be sorry it's not in Icehouse if it does't make it... but we can't have everything18:15
morganfainbergesp. if no work has been done on it18:15
dolphmmorganfainberg: ++18:15
topolHenry says he is coding that right now and 1st review will be in  a few days18:15
dolphmany progress would be nice to have; it's big enough that it might benefit from being taken a table or two at a time18:16
ayoungIf do put assignments  all in one table, lets make the fields big enough to hold the composite userids (with the embedded domain Ids ) in them, or put an idneityt_domain field in there18:16
*** coolsvap is now known as coolsvap_away18:16
dolphmtopol: thanks!18:16
topol(he cant join)18:16
morganfainbergtopol, cool!18:16
topolfrom Henry:  confusing there are two bp for the same one...here's the one I create a while back that I have marked as started: https://blueprints.launchpad.net/keystone/+spec/grant-table-rationalization18:16
dolphmi also just bumped https://blueprints.launchpad.net/keystone/+spec/keystone-py3kcompat to ongoing18:17
*** neelashah has quit IRC18:17
stevemardolphm, good call ++18:17
dolphmi3 wasn't really realistic for an end goal, but we've made a ton of progress on that front18:18
dolphmdstanek: thanks for the py33 gate ^ :D18:18
*** neelashah has joined #openstack-meeting18:18
dstanekdolphm: ma pleasure18:18
dolphmbknudson: know anything of https://blueprints.launchpad.net/keystone/+spec/i18n-logging ?18:18
jamielennoxall the projects are blocked by eventlet for py3 i thought?18:18
dstaneki with all of our deps already worked on py318:19
bknudsonit looks like they're updating webob requirement so maybe the py3k gate will do something.18:19
dolphmi'm not aware of luis' irc handle18:19
dolphmjamielennox: ++18:19
lbragstaddolphm: luisg18:19
dolphmpinged him in -dev18:19
bknudsondolphm: my understanding is that it's implemented. I'll check on it.18:20
*** luisg has joined #openstack-meeting18:20
luisghi dolphm18:20
dolphmluisg: o/18:20
dolphmluisg: i wanted to check in on https://blueprints.launchpad.net/keystone/+spec/i18n-logging18:21
dolphmare there patches in review for that / can we expect to see some soon?18:21
topolbknudosn is the i18n-logging Daisy's stuff?18:21
*** ddutta has joined #openstack-meeting18:21
*** nadya has joined #openstack-meeting18:21
luisgdolphm, afaik all the patches for that were already delivered by bknudson18:21
*** cvbock has joined #openstack-meeting18:22
topol(Daisy's stuff for keystone...)18:22
*** nadya is now known as Guest9972418:22
*** oubiwann_ has quit IRC18:22
dolphmluisg: bknudson: on the logging side?18:22
*** neelashah has quit IRC18:22
bknudsonluisg: it was probably included in an oslo-incubator sync...18:22
*** AlexF has joined #openstack-meeting18:22
luisgcorrect18:22
*** oubiwann_ has joined #openstack-meeting18:22
bknudsonso maybe all I need to check is if keystone is up-to-date with oslo-incubator log.18:22
dolphmbknudson: that's what the first step described by the bp -- last i checked there was something relevant in review for oslo18:22
dolphmdon't recall it syncing18:23
dolphmbknudson: if you find a patch to call that one Implemented, will you link it in the whiteboard on that bp?18:23
bknudsondolphm: will do18:23
*** jcooley_ has joined #openstack-meeting18:24
*** shardy has joined #openstack-meeting18:24
dolphmand to put everyone to sleep again...18:25
dolphm#topic Why we should have reserved migrations for backports18:25
*** openstack changes topic to "Why we should have reserved migrations for backports (Meeting topic: keystone)"18:25
dolphm#link https://review.openstack.org/#/c/69884/18:25
morganfainbergzzzzz18:25
dolphmcheckout the conversation around Jan 3018:25
morganfainbergi mean >.>18:25
ayoungNope18:25
dolphmwe got lucky in this case fortunately :)18:25
*** jcooley_ has quit IRC18:26
*** hartsocks has joined #openstack-meeting18:26
dolphmanyway, it's solid demonstration of why we need https://blueprints.launchpad.net/keystone/+spec/reserved-db-migrations-icehouse18:26
ayoungdolphm, we risk rewriting history with that approach....I really think we need to avoid doing that18:26
topolIm assuming the Jan 30 conversation is a dolphm "I told you so"???18:26
dolphmayoung: ?18:26
ayoungdolphm, if someone is tracking tip of tree18:26
ayoungand we slip in a migration, we mess them up18:26
dolphmayoung: there's no rewriting of history in that case, as it's the same history being backported18:27
ayounglike, say that we reserve 40-4518:27
morganfainbergayoung, if the migration is idempotent, you make it happen "next" as well as previously in the backport18:27
*** banix has quit IRC18:27
bknudsonseems like if someone wants to add or remove an index then they can go ahead.18:27
morganfainbergayoung, i think that is the general approach.18:27
ayoungnow we decide we need to use up a reservation, so 40 goes from no-op to doing something18:27
*** dkehn has quit IRC18:27
ayoungif I look at a DB at version 45, has that been applied or not?18:27
*** ddutta has quit IRC18:28
dolphmi'll contribute some docs explaining how reserved migrations work, and why they won't break anyone ever18:28
morganfainbergayoung, anything backported _must_ be idempotent.18:28
dolphm#action dolphm to doc reserved migrations18:28
topoldolphm ++ docs would really help for vetting18:28
*** akuznetsov has joined #openstack-meeting18:28
ayoungmorganfainberg, idempotent is only relevant if it is executed at least once18:28
morganfainbergayoung, i'm not saying i like backporting migrations18:28
bknudsonjust because we have the reserved migrations doesn't mean we have to use them anyways.18:28
*** dkehn has joined #openstack-meeting18:28
ayoungwhat if it is executed 0 times18:28
*** thuc_ has quit IRC18:28
ayoungbknudson, its like line number in basic18:29
morganfainbergayoung, so you backport it and make it the "next" one, so it's now 40 and 50 for example18:29
bknudsonare we going to have reserved migrations for extensions, too?18:29
dolphmayoung: i'll write the docs, and you can comment on the approach there18:29
morganfainbergayoung, new runs get the change, old runs get it earlier18:29
*** thuc has joined #openstack-meeting18:29
dolphmi'll include them with the reserved migrations patch https://review.openstack.org/#/c/70153/18:29
morganfainbergayoung, but.. like i said not that i am for it, just how it would need to work18:29
*** akuznetsov has quit IRC18:29
dolphm#topic Return fake users for federated users that don't exist?18:30
*** openstack changes topic to "Return fake users for federated users that don't exist? (Meeting topic: keystone)"18:30
dolphmbknudson: o/18:30
ayoungWe are doing something wrong...but I suspect that is what the SQL alchemy migrations force on us.  Alembic has a better approach, doesn't it?  More Git like?18:30
bknudsonok, so this is because we can have assignments that don't point to users anymore.18:30
dolphmi think i've sufficiently confused myself on this topic18:30
*** safchain has quit IRC18:30
*** jamezpolley_ has joined #openstack-meeting18:30
bknudsonif you get users for project (v2 api), it returns all the users18:30
morganfainbergayoung, yes, and no, some of the same issue, but you can reorder them as needed.18:31
morganfainbergayoung, among other things.18:31
bknudsonwhich now will 404 Not Found for those assignments to users that don't exist.18:31
morganfainbergayoung, alembic is better, but not 100% solution18:31
lbragstadayoung: ++18:31
dolphmmorganfainberg: bknudson: save it for the relevant review18:31
bknudsonI'm sure there's a few ways to handle the situation...18:31
ayoungdolphm, OK...I'll concede, so long as we use the reservations very sparingly18:31
*** wendar_ is now known as wendar18:31
bknudsonwhat I'm proposing is to build a fake user to return18:31
bknudsonbecause then the caller at least knows the assignment is there and which user_id it's to.18:32
dolphmbknudson: it sounds to me like you're trying to code yourself out of a situation that we shouldn't be in at all18:32
topolbknudson what is the username and id for the fake user???18:32
dolphmthere shouldn't be role assignments on ephemeral users, period18:32
bknudsonuser-<user-id>18:32
bknudsonso we should not allow creating an assignment to a user that doesn't exist?18:32
morganfainbergbknudson, i thought we said federated had to have grants on a group.18:32
morganfainbergnot a federated user18:33
* morganfainberg might be mis-remembering18:33
bknudsonthis also applies to ldap users.18:33
stevemartopol, https://gist.github.com/dolph/5cfa70c02f5b141060c5#file-notes-md18:33
marekdmorganfainberg: ++ but almost everything in the keystone  depends on the user_id.....18:33
*** thuc has quit IRC18:33
bknudsonsince the user might be deleted from ldap directly18:33
ayoungbknudson, so...this is the better long term solution:  create a uer obnject at the start of the token pipelines.  If that user object comes out of the backing store, or out of a SAML document, it is irrelevant18:33
morganfainbergbknudson, oh.18:33
topolI thought this was always going to be dynamic lookup of the federated user?18:33
*** changbl has joined #openstack-meeting18:34
dolphmtopol: what does that mean18:34
ayoungdolphm, there absoutelty should be roel assignments on ephemeral users18:34
*** akuznetsov has joined #openstack-meeting18:34
morganfainbergtopol, you can't ask the idp about a user really.18:34
dolphmayoung: that doesn't make sense18:34
ayoungSAML means you will not have seen the user before they hit the cluster18:34
topolmeans you dont have to store anything18:34
marekdayoung: ++18:34
dolphmayoung: correct18:34
dolphmayoung: and we drop them into groups, and they get role assignments that way18:34
ayoungI'm the teacher, I get the student list.  I create a role assignemt for the users in my class.  Come Day 1 they get their resources18:34
bknudsonhow are the group assignments done?18:35
dolphmayoung: you assign roles to group=students, not user=student1, user=student2, user=student318:35
bknudsonusing identity groups?18:35
*** akuznetsov has quit IRC18:35
*** akuznetsov has joined #openstack-meeting18:35
*** akuznetsov has quit IRC18:35
ayoungdolphm, but groups are from Identity.  They won't have a group in their SAML document that  matches this18:35
*** gokrokve_ has quit IRC18:35
*** akuznetsov has joined #openstack-meeting18:35
ayoungshort of putting an ephemeral group construct, we need to allow direct role assignments.18:36
bknudsonI'm guessing you can't put a non-existant user in a group18:36
*** akuznetsov has quit IRC18:36
*** gokrokve has joined #openstack-meeting18:36
*** akuznetsov has joined #openstack-meeting18:36
morganfainbergbknudson, doesn't the SAML also dictate groups?18:36
*** thuc has joined #openstack-meeting18:36
marekdmorganfainberg: it can, but doesn't have to.18:36
morganfainbergbknudson, and wrt groups we only ever (iirc) reference the id18:36
bknudsonmorganfainberg: I believe the federation mapping will asign groups.18:36
ayoungmorganfainberg, it *CAN* but it won't18:36
*** masayukig has joined #openstack-meeting18:36
dolphmayoung: groups are from identity, yes-- i'm (perhaps falsely?) assuming that an identity backend will still be available?18:36
morganfainbergayoung, i meant via mapping18:36
ayoungmorganfainberg, its a difference between authorization and authentication.  SAML will have the "static" view of the user from the central IT18:37
dolphmbknudson: ++18:37
ayoungmorganfainberg, might not be anything there to map on18:37
morganfainbergayoung, so we need "assignment" groups now?18:37
dolphmmorganfainberg: you just lost me18:37
ayoungmorganfainberg, probably, but direct role assignments come first18:37
dstaneki thought we were only assigning roles to groups and using mapping to match SAML to the groups18:37
*** Fdot has quit IRC18:37
morganfainbergdolphm, i feel lost myself18:37
dolphmayoung: define "direct" ?18:37
ayoungdolphm, user to project18:38
morganfainbergdstanek, that was my understadning18:38
ayoungas opposed to via groups18:38
marekddstanek: that was the idea.18:38
*** mestery_ has quit IRC18:38
*** dprince has quit IRC18:39
morganfainbergmarekd, dstanek , that sounds like a mapping needs to generate some group-like-reference (id) then?18:39
bknudsongiven a user-id, assignment backend doesn't know what group they're in, right?18:39
*** yassine has quit IRC18:39
bknudsonbecause groups are calculated via mapping of user attrs which we don't have18:39
morganfainbergand then you used the assertion to figure all that out each time?18:39
marekdmorganfainberg: kind of,  the problem is that almost everything regarding token_api token_provider_api assumes there is existing user in the backend....18:39
*** neelashah has joined #openstack-meeting18:40
morganfainbergmarekd, that is something we can fix.18:40
dolphmmarekd: that needs to change then18:40
morganfainbergmarekd, in-fact we should fix that18:40
dolphmi think we discussed that at the hackathon?18:40
morganfainbergdolphm, think so18:40
dstanekmorganfainberg: why would it need to generate an id?18:40
*** arnaud___ has joined #openstack-meeting18:40
*** arnaud__ has joined #openstack-meeting18:40
*** markmcclain has quit IRC18:40
morganfainbergdstanek, grants are based on the project/domain/whatever-group combination?18:40
dolphmmapping should output a list of group IDs18:40
*** masayukig has quit IRC18:41
*** gokrokve has quit IRC18:41
morganfainbergdstanek, so.. you need to be able to do some kind of lookup for the grant purpose? i think...18:41
dolphmso group-project-role + group-domain-role assignments are all you need18:41
marekddolphm: me? that's relatively easy to fetch...18:41
morganfainbergassuming we only have data in assignment (can't ask identity) it needs to be some consistent id we can reference.. or am i totally missing something?18:42
*** sdake has quit IRC18:42
*** Guest99724 has quit IRC18:42
marekddolphm: but i am again super-confused. we spent like few hours discussing that and ended up with responding with a list of groups...the token+roles idea is again on a track? :(18:42
dolphmmarekd: i was just making a general statement, but i'm glad it strikes you as easy :)18:42
ayounguser_id needs to be composed:  one thing from SAML etc, one thing from Keystione (domain id)18:42
bknudsonmorganfainberg: assignment can get the roles for a group given group id.18:42
dstanekmorganfainberg: i thought the mapping statically contained the group id18:42
marekddolphm: NO IT DOESN'T :P18:42
*** akuznetsov has quit IRC18:42
ayoungthen we don't confirm that the user "exists"18:42
dolphmmarekd: lol "that's relatively easy to fetch..."18:43
morganfainbergbknudson, i'm very confused... if the user if coming from SAML / is federated, we are allowing them to be placed in a SQL (or LDAP) identity group?18:43
dolphmdstanek: correct, multiple potential group ids18:43
*** sdake has joined #openstack-meeting18:43
*** sdake has quit IRC18:43
*** sdake has joined #openstack-meeting18:43
* dolphm federation is hard18:43
bknudsonmorganfainberg: they're not put in the group in identity... we calculate the group IDs from the user properties.18:44
morganfainbergbknudson, ok. so... the group is also ephemeral18:44
bknudsonmorganfainberg: with federation identity is not involved.18:44
marekdmorganfainberg: no18:44
dstanekmorganfainberg: no18:44
bknudsonmorganfainberg: I don't think you'd have to define the group.18:44
dolphmmorganfainberg: i was assuming sql/ldap groups18:44
marekddolphm: ++18:44
*** dims has joined #openstack-meeting18:44
dolphmbknudson: define "calculate the group ID" ????18:44
ayoungassume that a role assignment can be made to a group from an IdP  prior to the group being created18:44
morganfainbergbknudson, that was my assumption here18:45
dolphmbknudson: mapping isn't inventing groups, nor creating groups that don't exist18:45
*** Gordonz has joined #openstack-meeting18:45
ayoungcuz there will be no "group created" event18:45
ayoungjust that some SAML doc comes in with an attribute that we map to a group.18:45
marekdmapping is a connector beetween real world (SAML) and a keystone local world...18:45
bknudsondolphm: what is there in the identity group that needs to be looked up to figure out what group a user is in?18:45
morganfainbergayoung, do we care? i mean we don't get user_created events either?18:45
marekdso i assume the groups MUST alread exist.18:45
ayoungexzactly18:45
morganfainbergmarekd, i always assumed you'd effectivly "generate" the group based upon mapping and it would be IDP:<group something>18:46
dolphmbknudson: i don't understand the question18:46
morganfainbergmarekd, not go create ideneity group and then use saml to associate the user to that group18:46
dolphmbknudson: you don't ask identity what groups a user is in18:46
marekdmorganfainberg: what for? you'd endup with a group without any roles...18:46
ayoungyou can't query Identity.  That is the new rule for Federation18:46
ayoungeverything just comes in an either it works or they file a ticket18:46
dolphmmorganfainberg: if that's the case, i wouldn't call them groups at all18:47
marekdmorganfainberg: somehow i must map SAML assertion into an ephemeral user with set of roles...18:47
bknudsondo we need a new kind of federated user/group role assignment?18:47
dolphmmorganfainberg: the goal was to map ephemeral users into identity groups and let assignments do it's thing18:47
morganfainbergmarekd, no, you could still assign roles to the "emphemeral group" it just would be created on-the-fly e.g. has attribute contractor, this maps to <IDP>:contractor18:47
dolphmbknudson: please no18:47
*** slagle has joined #openstack-meeting18:47
*** jjmb has joined #openstack-meeting18:47
morganfainbergmarekd, since assignment doesn't care if a group exists (or a user) (or it shouldn't)18:47
dolphmbknudson: not outside the scope of mapping, anyway18:47
morganfainbergi was just massively confused on implementation18:48
dolphmit seems that the "assignment drivers shouldn't be talking to identity drivers" conversation got very confused with the federation conversation18:48
bknudsonI don't understand why the group would have to exist... does it need to have the user_id (?) as a member?18:48
marekdmorganfainberg: on what basis would you assign those roles to the ephemeral groups? another set of api calls?18:48
dolphmthose were to separate topics with separate goals18:48
morganfainbergi don't particularly like crossing federated -> non-federated identity stuff, but it might be the only approach.18:48
morganfainbergmarekd, same calls we have now.18:48
bknudsonwill federation do identity_api.get_group(group_id) and verify it exists f?18:48
dolphmbknudson: what's the point in having a group that doesn't exist?18:49
bknudsonyou can assign roles to the group id ... the group doesn't have to exist for that.18:49
morganfainbergbknudson, ++18:49
*** Gordonz has quit IRC18:49
ayoungwhat we need to be able to do is to say "I have a user or group coming in with SAML attribute foo.  What ID will they get?  Use that to create an assignment  for Role on Project"18:50
*** jprovazn_afk is now known as jprovazn18:50
*** IlyaE has joined #openstack-meeting18:50
dolphmayoung: no one cares what ID they get -- we care about their authorization18:50
dolphmayoung: so we care about mapping the ephemeral user into identity groups, and picking up any authorization that implies18:50
bknudsonI also didn't think that federated users got an id.18:51
*** isviridov has joined #openstack-meeting18:51
*** thedodd has quit IRC18:51
ayoungdolphm, problem still stands even if you just say "groups"18:51
ayoungbut I think direct user assignments are going to be very common.  If we write them out of the equation, people will get annoyed18:51
ayoung"why do I need to create a group for a single person"?18:52
ayoungYou'll have groups that are basically based on the user ID...ugh18:52
dolphmayoung: SAML attribute foo --> foo_group --> foo_group:foo_role:foo_project -> scoped token for foo_project with foo_role18:52
ayoungl;ets not do that18:52
ayoungdolphm, but if the only reliable attribute tha comes is the one that uniqely identifies the user?18:52
ayoungwe are going to have Posix groups.18:53
ayoungayoung:ayoung  where user ayoung is the only member of the group ayoung18:53
bknudsonit makes sense to me to have some kind of user_id that can come out of federation auth just like a list of group_ids.18:53
dstanekayoung: are user-based role assignments common?18:53
marekdbknudson: always?18:53
dolphmif anything, the end is one group per one capability/rule/permission in policy.json18:53
bknudsonmarekd: I don't think user_id has to be required.18:54
bknudsonjust like maybe group_ids are required.18:54
bknudsonmaybe group_ids aren't required18:54
ayoungunify users and groups into one entity?  Composite pattern?  Party Pattern?18:54
bknudsondo allow mapping to no groups?18:54
*** jcooley_ has joined #openstack-meeting18:55
ayoungyes18:55
ayounggroups are optional18:55
dolphmbut then you get zero authorization18:55
dolphmand can't use opentack18:55
dolphmbut sure, they're otherwise optional18:55
*** gokrokve has joined #openstack-meeting18:55
marekduser is optional too.18:55
*** andreaf has quit IRC18:55
*** sdake has quit IRC18:55
marekdat least in the current state of the mapping engine..18:55
ayounglets keep it consistent with the current auth model:  users can get role assignments in federation.18:55
*** andreaf has joined #openstack-meeting18:56
stevemarmarekd, currently everything is optional :)18:56
marekdayoung: but what if rule engine doesn't return a user, just a set of groups?18:56
marekdthat's my concern...18:56
ayoungmarekd, they need to have a user id18:56
ayoungNova needs it for ownership18:56
dolphmmarekd: some sort of user identifier either needs to be required, or having a user identifier as an output of mapping shouldn't be a feature at all18:56
ayounggroup can be optional, but not userid18:56
dolphmi'm fine with either way, but everyone seems to want ephemeral IDs18:57
bknudsonayoung: that's a good point... other projs might need user id18:57
ayoungbknudson, they do18:57
ayoungboth Swift and Nova rely on it18:57
*** shshang has joined #openstack-meeting18:57
marekdso, rule engine will be obliged to issue a user_id.18:57
dstanekuser id is very useful in auditing18:57
dolphmayoung: they shouldn't18:57
bknudsonit can be ephemeral -- maybe it's like "IdP:username"18:57
dolphmayoung: i don't know that we'd break anything meaningful in nova if we didn't give them user identifiers18:58
stevemarmarekd, I guess so, but if I don't see any user related stuff, I can just leave it out18:58
ayoungbknudson, so18:58
dolphmdstanek: that's the *only* push back i get for dropping user identifiers :)18:58
ayounguserid@@domainid is my suggestion18:58
marekdstevemar: no, i should be able to assume that you will give me a userid.18:58
ayoungone part from the IdP (userid) and one part from keystone (domainid)18:59
ayoung1 minute18:59
marekdstevemar: otherwise what do i put in the token['user_id'] ?18:59
bknudsonayoung: do we need to define the format? the mapping will just generate one.18:59
dolphmdstanek: in which case, i *want* the answer to be sha1(token) gets audited, and you can trace with that18:59
* dolphm 1 min18:59
marekd-dev?18:59
dolphm++18:59
dolphm#endmeeting18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:59
openstackMeeting ended Tue Feb  4 18:59:50 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-02-04-18.01.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-02-04-18.01.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-02-04-18.01.log.html18:59
*** lbragstad has left #openstack-meeting18:59
bknudsonwell, you can look at the review and decide if it's a good idea to return a fake user or not.19:00
*** gokrokve has quit IRC19:00
*** jamielennox has left #openstack-meeting19:00
*** Gordonz has joined #openstack-meeting19:00
*** markmcclain1 has joined #openstack-meeting19:00
pleia2o/19:01
*** Gordonz has quit IRC19:01
lifelessSpamapS: could you get the ball rolling; I have an ELOCAL for a bit19:01
*** Gordonz has joined #openstack-meeting19:01
dkehnhi19:01
*** markmcclain1 has quit IRC19:01
*** gothicmindfood has joined #openstack-meeting19:02
fungiheyo! infra meeting?19:02
jeblairhello infra folks!19:02
dhellmanno/19:02
*** shshang has left #openstack-meeting19:02
clarkbhithere19:02
gothicmindfoodhola jeblair19:02
jeblairfungi: would you like to chair since i've been on airplanes?19:02
fungijeblair: glad to19:02
fungi#startmeeting infra19:02
openstackMeeting started Tue Feb  4 19:02:48 2014 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
SergeyLukjanovo/19:03
fungi#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
*** swifterdarrell has quit IRC19:03
*** markpeek has quit IRC19:03
fungi#link http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-01-28-19.01.html19:03
SpamapSlifeless: sure..19:03
fungimrmartin work with smarcet to get through infra processes19:04
*** mestery has joined #openstack-meeting19:04
fungithat's been happening19:04
fungi#link https://review.openstack.org/#/c/69636/419:04
fungimordred find a way to run manage-projects automagically without puppet19:04
*** dguitarbite has joined #openstack-meeting19:04
fungiupdates on that? anything newer than in the bug?19:05
jeblairfungi: can you _very_ quickly update me on why that's necessary?19:05
jeblairis it in the bug?19:05
anteayahe has been sick, I have been talking with UtahDave about salting it19:05
anteayathen UtahDave has been sick19:05
anteayano code yet19:05
fungijeblair: seems the issue we're encountering only arises when manage-projects is called from puppet agent19:05
clarkbwe have a 100% success rate when run by hand19:05
jeblairfungi: is it more complicated than the 10min exec timeout?19:06
*** jcoufal_ is now known as jcoufal19:06
*** swifterdarrell has joined #openstack-meeting19:06
*** markmcclain has joined #openstack-meeting19:06
fungijeblair: mordred had suggested punting and working around the puppet call with an additional layer19:06
clarkbjeblair: yes, it actually does create the projects and some of the groups but not all of the groups19:06
*** gokrokve has joined #openstack-meeting19:06
clarkbwhich indicates the timeout isn't being hit, but weirdness is happening19:06
zaroo/19:06
*** dprince has joined #openstack-meeting19:06
jeblairclarkb: does it log?19:07
clarkbjeblair: I think so but not with the -v flag when run by puppet iirc19:07
*** tanisdl has quit IRC19:07
fungione of my suggestions in the bug was to either figure out why the exec stdout/stderr capture in puppet isn't working as advertised, or to add a python logging config for manage-projects, but i haven't foung time to look into either of those19:08
jeblairokay, well, this idea that we can't figure out what this simple program is doing is way too voodoo for me....19:08
clarkbjeblair: fungi: puppet execs are weird and voodoo like19:09
clarkbthey are documented as such19:09
jeblairi would like manage-projects to get proper logging and log what it's doing so we can see what's actually happening19:09
clarkband the recommendation from puppetlabs is to not use them19:09
clarkbbut I am all for better logging19:09
jeblairclarkb: do they fail at calling fork/exec?19:09
*** AlexF has quit IRC19:09
clarkbjeblair: yes19:09
clarkbwell they blame ruby, but yes19:10
jeblairclarkb: how does anything in puppet work?19:10
jeblairi mean we exec stuff _all the time_19:10
jeblairare they not closing fd's properly or something?19:10
clarkbno it has to do with environment stuff19:10
*** gokrokve has quit IRC19:11
*** balajiiyer has joined #openstack-meeting19:11
jeblairokay, so basically we're not anywhere near being able to automatically create new projects19:11
*** Mandell has joined #openstack-meeting19:12
jeblairshould we resume the moratorium on approving new projects?19:12
fungiright. mordred has resorted to manually running manage-projects after new project configs merge19:12
*** rossella_s has quit IRC19:13
fungiand we merged a puppet config change to disable the exec temporarily19:13
jeblairok19:13
fungiwe should capture more of this into the bug19:13
fungi#link https://launchpad.net/bugs/124256919:13
jeblairso mordred is in charge of semi-manual new project creation until that bug is fixed19:13
*** salv-orlando has quit IRC19:13
*** gokrokve has joined #openstack-meeting19:14
*** pnavarro has joined #openstack-meeting19:14
*** salv-orlando has joined #openstack-meeting19:14
fungi#action mordred continue looking into bug 124256919:14
jeblairif that's the case, that works for me19:14
fungii do agree that "let's just not use puppet" seems like a bit of a kluge19:15
*** baoli has quit IRC19:15
fungibut maybe not, without a more detailed proposal it's hard to say19:15
jeblairyes.  i think we need proper logging regardless of how it's invoked.19:15
anteayasorry, I guess I mis-understood then, I thought that was where we were last week19:15
jeblairi'm just plain embarrassed that we're like "it's broken and we don't know why because we don't know what the computer is doing".19:15
*** olaph has joined #openstack-meeting19:15
fungii concur19:16
jeblairi've dragged this on enough though; please continue19:16
fungiwe have an agenda item for this, so we can pick it up again in a bit if needed19:16
fungiclarkb upgrade jenkins.o.o and jenkins01 to 1.543 and upgrade zmq plugin and scp plugin everywhere19:17
fungithat all happened, correct?19:17
*** dvarga is now known as dvarga|away19:17
*** dvarga|away is now known as dvarga19:17
clarkbthat is all done but the zmq bit ebcause there is an outstanding review to fix the master name reportig19:17
clarkbso the action can be updated to:19:17
*** jcooley_ has quit IRC19:17
clarkb#action clarkb upgrade zmq plugin everywhere to report master name in events19:17
fungioh, i missed that the master name patch was buggy. have a link to the fix?19:17
clarkb#link https://review.openstack.org/#/c/69763/19:18
*** andreaf_ has joined #openstack-meeting19:18
*** reed has quit IRC19:18
*** shadower_ is now known as shadower19:18
fungifungi move graphite whisper files to faster volume19:18
fungijeblair actually moved these to a cinder volume19:18
*** reed has joined #openstack-meeting19:19
jeblairfungi: oh do we want to move that from spinning to ssd?19:19
*** egallen has quit IRC19:19
*** sdake has joined #openstack-meeting19:19
*** sdake has quit IRC19:19
*** sdake has joined #openstack-meeting19:19
*** nadya has joined #openstack-meeting19:19
fungiwe should keep tabs on performance and see whether it improves before pvmoving it to an ssd volume19:19
fungibut should be trivial now that it's lvm19:19
*** nadya is now known as Guest2911619:20
*** sushils has joined #openstack-meeting19:20
jeblairfungi: ok.  also, that host would probably benefit from a move to performance flavor19:20
jeblairwhich should also be easier now :)19:20
*** andreaf has quit IRC19:20
fungi#action fungi see if graphite whisper files need to be moved to a faster pv or faster vm19:20
fungi(since i fell down on getting it taken care of so far, it's only fair)19:20
fungialso didn't get around to...19:21
fungi#action fungi prune obsolete whisper files automatically on graphite server19:21
jeblairthat's hard because some metrics don't report very often19:21
*** skraynev_ has joined #openstack-meeting19:21
fungiis once a month sane there?19:21
fungionce a quarter?19:21
fungihow often is not very often?19:21
jeblairfungi: i'm thinking some release jobs only happen twice a year19:21
fungiahh, yep19:22
fungiick19:22
jeblairso the easy answer is prune after 1 year; more frequently becomes tricky.19:22
*** banix has joined #openstack-meeting19:22
fungii can start by seeing if we have any whisper files untouched for a year19:22
*** balajiiyer has left #openstack-meeting19:22
fungiif we've had a graphite server that long19:22
fungianteaya assist mordred in automating manage-projects again19:22
jeblaircould probably do like 8 months or so19:22
clarkbwe can probalby also manually prune using a list generated by find19:23
clarkba lot of things will be obviously obsolete19:23
*** FallenPegasus has joined #openstack-meeting19:23
fungii guess that ties back in with the earlier bug 1242569 discussion19:23
jeblairclarkb: yeah, with some thinking we could identify metrics that zuul/nodepool don't use anymore.19:23
*** hartsocks has left #openstack-meeting19:23
fungianteaya: were you still working with mordred on bug 1242569?19:24
anteayaI had it on my radar19:24
anteayaas of yet, no progress19:24
anteayahe was sick19:24
fungishould we keep that as an action item for next week?19:24
anteayamay as well19:24
fungi#action anteaya assist mordred in automating manage-projects again19:25
anteayathanks19:25
fungipush for improved logging first to see whether it's necessary19:25
fungii know this hasn't happened yet...19:25
anteayak19:25
fungi#action mordred to lift virtualenv 1.10.1 pin when we're ready to babysit it19:25
anteayayes, that is my name on the logging bug19:25
fungizaro to point zuul-dev at gerrit-dev19:26
fungizaro: that happened right?19:26
zarodone19:26
fungiawesome!19:26
dguitarbitehey guys, I have something to discuss if possible19:26
fungidguitarbite: is it on https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting ?19:26
*** rakhmerov has quit IRC19:26
fungiif not, i can try to work it in19:27
*** jasondotstar has quit IRC19:27
fungizaro to review jeepyb integration with new gerrit and update gerritlib for gerrit 2.819:27
fungii know i saw some work on that as well19:27
zarodone.19:27
fungithat's continuing, right?19:27
fungioh, even better19:27
zaroit's done.19:27
fungigreat19:27
zarofixes have been pushed to review.oo19:28
zaro#linkhttps://review.openstack.org/#/c/6980019:28
zarofix gerrit hooks - #link https://review.openstack.org/#/c/6979119:28
zarofix replicate command - #link  https://review.openstack.org/#/c/6976819:29
*** rakhmerov has joined #openstack-meeting19:30
dguitarbitefungi: thanks19:30
zarook. nothing more on that testing.19:30
zaroohh just wanted to mention that tested the following scripts with gerrit 2.8: expire_old_reviews.py, manage_projects.py, update_blueprint.py, update_bug.py, welcome_message.py, openstackwatch.py19:31
*** vijendar has quit IRC19:31
fungianything major worth reporting on that real quick, or just want to plug the etherpad issues list?19:32
fungi#link https://etherpad.openstack.org/p/gerrit-2.8-upgrade19:32
fungiokay, so we've got half the meeting slot left. i'll try to blow through topics which we covered in the action items19:32
fungialso, my irc client's lag timer keeps creeping up, no idea whether freenode is still under a ddos, but i'll add clarkb as an optional chair in case i vanish19:32
*** ayoung is now known as ayoung-afk19:32
fungi#chair clarkb19:32
openstackCurrent chairs: clarkb fungi19:32
fungi#topic Trove testing (mordred, hub_cap, SlickNik)19:32
*** openstack changes topic to "Trove testing (mordred, hub_cap, SlickNik) (Meeting topic: infra)"19:32
*** jamezpolley_ is now known as jamezpolley19:32
fungilooks like only mordred is in channel19:33
fungiwe can come back to this one at the end of they show up19:33
clarkbthat was the case last week. ++ to shifting19:33
pleia2and several weeks19:33
*** SlickNik has joined #openstack-meeting19:33
fungiwow meetbot is sluggish19:33
pleia2is there a bug to track it? maybe we pull from agenda for now19:33
*** AlexF has joined #openstack-meeting19:33
SlickNikhello19:33
*** jamezpolley is now known as tchaypo19:34
fungihowdy SlickNik19:34
fungiany quick updates on "Trove testing"19:34
fungi?19:34
*** johnthetubaguy has quit IRC19:34
SlickNikI have a patch out to tempest (basic trove flavor API tests) waiting on reviews.19:35
SlickNikone sec19:35
SlickNik#link https://review.openstack.org/#/c/69501/19:35
SlickNikI'm working on adding more tests19:35
SlickNikAlso the gate job has been set up and is running on jenkins.19:36
SlickNikIt's non-voting as of now.19:36
*** Guest29116 has quit IRC19:36
*** jcooley_ has joined #openstack-meeting19:36
fungiokay, great19:36
fungithat's some awesome progress19:36
*** AlexF has quit IRC19:36
jeblairyaaay!19:36
fungisince we use trove for some of our infrastrucutre (and soon hopefully much more) i'm glad it's being tested ;)19:37
*** masayukig has joined #openstack-meeting19:37
fungimoving on quickly...19:37
fungi#topic Tripleo testing (lifeless, pleia2, fungi)19:37
*** openstack changes topic to "Tripleo testing (lifeless, pleia2, fungi) (Meeting topic: infra)"19:37
*** markpeek has joined #openstack-meeting19:37
fungiwe've had some setbacks with nodepool bugs/tripleo-ci outages but all in all things are progressing19:38
pleia2yeah, continuing to work on getting fedora in the gate too (helps tripleo and some other things we want to do)19:38
fungianything in particular we should be aware of beyond that for now?19:39
*** novas0x2a|laptop has joined #openstack-meeting19:39
pleia2I don't think so, gritty details otherwise were covered in tripleo meeting19:39
fungias an aside, i've got puppet agent temporarily disabled on nodepool.openstack.org until the tripleo-ci provider is back up and running, which i gather will probably be some time later today. for now it's been deleted out of nodepool.yaml since it was bringing new bugs to the surface we haven't had time to dig into yet19:40
clarkbI do think we may need to consider reverting some of those nodepool changes though. Should debug the slow deletes first, but performance is worse than before19:41
*** dguitarbite has quit IRC19:41
pleia2thanks for staying on top of that, fungi19:41
fungiwhich is why all the tripleo jobs are in a pending state in zuul's status19:41
*** masayukig has quit IRC19:42
fungi#topic Requested StackForge project rename (fungi, clarkb, zhiwei)19:42
*** openstack changes topic to "Requested StackForge project rename (fungi, clarkb, zhiwei) (Meeting topic: infra)"19:42
*** sdake has quit IRC19:42
fungino update on this... it's still pending hearing back from zhiwei but we'll probably also be moving some oslo libs out of stackforge to openstack19:42
fungiso we can try to time those together19:43
clarkband savanna if they choose a new name19:43
jeblairoh neato19:43
fungialso maybe savanna renames if they work out what their new name is19:43
fungiwhat clarkb said19:43
dhellmannthis item is on the agenda twice, because I didn't notice that until the meeting started19:43
fungidhellmann: no worries19:43
SergeyLukjanovfungi, yup, we're searching new name atm19:43
dhellmannand we're up to 4 libraries moving into oslo, not just the 3 mentioned on the agenda :-)19:43
*** sdake has joined #openstack-meeting19:43
fungiwe'll hit it at that point on the agenda19:43
fungior now is fine19:44
*** sdake has quit IRC19:44
*** sdake has joined #openstack-meeting19:44
clarkbSergeyLukjanov: `cat /dev/urandom | tr -dc '[:alpha:]' | head -c6`19:44
fungidhellmann: and you have a change up for that already too, right?19:44
SergeyLukjanovfungi, my estimate is 2-3 weeks19:44
dhellmannfungi: either works, I don't have much to say unless there are questions19:44
*** sdake has joined #openstack-meeting19:44
*** sdake has quit IRC19:44
*** sdake has joined #openstack-meeting19:44
dhellmannfungi: yes19:44
dhellmann#link https://review.openstack.org/#/c/70435/19:44
SergeyLukjanovclarkb, :)19:44
annegentlesavanna is definitely out though?19:44
*** jcooley_ has quit IRC19:44
fungi#topic Oslo adopting some stackforge libs (dhellmann)19:44
*** openstack changes topic to "Oslo adopting some stackforge libs (dhellmann) (Meeting topic: infra)"19:44
fungisince we seem to be doing that19:44
fungicliff, stevedore, taskflow and...19:45
dhellmannpycadf19:45
fungiexcellent19:45
fungidhellmann: is that an asap move, or do you need some lead time/.19:45
fungi?19:45
dhellmannfungi: we're ready when you all are19:45
dhellmannthere's no particular hurry, but sooner is better, so I think I'd rather not wait for savanna to pick a name if that's the only thing holding us up19:46
*** AlexF has joined #openstack-meeting19:46
SergeyLukjanovdhellmann, agreed, it could take up to a month for savanna19:46
fungii think i'm free this weekend, but would appreciate at least one other infra core on hand in case we get into the weeds19:46
clarkbfungi: I am maybe free this weekend19:47
*** AlexF has quit IRC19:47
clarkbno plans yet but the planning of possibilities has started...19:47
*** IlyaE has quit IRC19:47
dhellmannI have a family thing this weekend, or I'd hang out with you guys -- I'm not sure I'll be much more than moral support, though :-)19:47
fungidhellmann: well, we'll have .gitreview file patches which you'll want someone to merge19:48
jeblairwe could do it friday afternoon...19:48
fungii'm cool with that19:48
dhellmannfriday works for me19:49
fungiactivity seems to be mostly dead on friday afternoons north-american time19:49
jeblaircool, and it's just a few mins of downtime19:49
*** salv-orlando has quit IRC19:49
fungiyep19:49
*** jcooley_ has joined #openstack-meeting19:49
*** salv-orlando has joined #openstack-meeting19:49
fungiwhat do we think... 20:00 utc friday then?19:49
fungithat's noon pst i think. go later?19:50
dhellmannI'm in EST, so that time is great for me, but later works too19:51
jeblairthat time or later wfm; your pick19:51
fungiyeah, i'm in est as well19:51
fungiokay, let's do 20:00 utc. good compromise without pushing pst friday lunch too far out19:51
*** aignatov_ is now known as aignatov19:52
dhellmannI'll be there19:52
jeblair++19:52
fungi#agreed will rename new oslo projects on friday 2014-02-07 at 20:00 utc19:52
clarkbsounds good19:52
*** fbo is now known as fbo_away19:52
fungipulling some topics out of order for the last few minutes19:53
fungi#topic Request for a new branch of openstack/operations-guide for ongoing O'Reilly work (annegentle)19:53
*** openstack changes topic to "Request for a new branch of openstack/operations-guide for ongoing O'Reilly work (annegentle) (Meeting topic: infra)"19:53
fungiannegentle: i can do this--just get up with me after the meeting19:53
fungi#topic Storyboard update (jeblair)19:53
*** openstack changes topic to "Storyboard update (jeblair) (Meeting topic: infra)"19:54
jeblairoh neat!19:54
*** dvarga is now known as dvarga|away19:54
*** dvarga|away is now known as dvarga19:54
jeblairso we had a really good meeting; see the etherpad for what we captured19:54
jeblairshould have _basic_ functionality real soon19:54
*** reaperhulk has joined #openstack-meeting19:54
jeblairi would have said by wednesday19:54
jeblairbut krotscheck_sick is sick19:54
jeblairso it could be later than that19:54
zarosaid he was going on vacation too right?19:55
jeblairhopefully with the basic arch in place, it'll be easier for others to pitch in and cargo-cult forms and stuff.  :)19:55
annegentlefungi: sounds good19:55
*** redrobot has joined #openstack-meeting19:55
jeblairzaro: yes, he has vacation scheduled after his illness19:55
fungigoing on vacation sick is such a waste of a vacation. he should just work instead ;)19:55
jeblairanyway, once that's done we can start using it to dogfood storyboard and for infra projects19:55
jeblairit will lack _many_ features, but we can start adding them quickly19:56
jeblairthis is all under the "minimum viable product" on the etherpad19:56
*** jraim has joined #openstack-meeting19:56
fungithe lack of features will drive us to add what we need, i suspect19:56
fungigood for itch-scratching19:57
gothicmindfoodfungi: that's the plan. To psychologically compel contributions with super bare features. :)19:57
jeblairgothicmindfood: have the etherpad link handy?19:57
ttxhttps://etherpad.openstack.org/p/StoryboardMeetup19:58
jeblair#link https://etherpad.openstack.org/p/StoryboardMeetup19:58
gothicmindfoodhttps://etherpad.openstack.org/p/StoryboardMeetup19:58
*** julienvey_ has joined #openstack-meeting19:58
jeblair[eot]19:58
gothicmindfoodha. jeblair and ttx were quicker19:58
ttxyears of training19:58
gothicmindfoodwe all owe each other cokes.19:58
* fungi is so very excited19:58
*** bauzas has joined #openstack-meeting19:58
jeblairoh19:58
*** thuc has quit IRC19:59
*** mdurnosvistov_ has quit IRC19:59
lifelessttx: sorry, I have to run a short errand mid-meeting (C->kindy) - bbs19:59
gothicmindfoodand fwiw - I am currently putting together an etherpad set of stories related exclusively to Storyboard authentication19:59
gothicmindfoodhttps://etherpad.openstack.org/p/StoryboardAuth19:59
jeblairalso, http://storyboard.openstack.org/#!/ is in puppet and should do things like upgrade (including db migrations) as needed automatically19:59
gothicmindfoodI even have nice diagrams in powerpoint form19:59
*** thuc has joined #openstack-meeting19:59
jeblair#action jeblair get ssl cert for storyboard19:59
fungivery productive19:59
fungisarob: on the moodle app integration for training manuals thing (dguitarbite seems to have vanished), we can talk over in #openstack-infra if you like20:00
*** jtomasek has quit IRC20:00
fungiwe're at time20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Feb  4 20:00:14 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-02-04-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-02-04-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-02-04-19.02.log.html20:00
*** skraynev_ has quit IRC20:00
*** zehicle_at_dell has joined #openstack-meeting20:00
fungithanks everybody!20:00
jeblairfungi: thanks!20:00
anteayafungi: nice chairing20:00
*** skraynev_ has joined #openstack-meeting20:00
* fungi uses an overstuffed chair20:00
ttxAnyone here for the TC meeting ?20:00
mikalYep20:00
jeblairo/20:00
zehicle_at_dell+120:01
jraimI'm here for Barbican20:01
*** markmc has joined #openstack-meeting20:01
markmchey20:01
devanandao/20:01
SergeyLukjanovo/20:01
ttxrussellb, annegentle, mordred, jgriffith, vishy, markmcclain, lifeless, sdague : around ?20:01
*** sparkycollier has joined #openstack-meeting20:01
markmcclaino/20:01
ttxI know russellb is probably not around20:01
annegentlearoo20:01
*** emagana has joined #openstack-meeting20:01
ttxand sdague in Korea20:01
jgriffitho/20:01
ttxand 7. Quorum reached20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Feb  4 20:02:18 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
*** olaph has left #openstack-meeting20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
openstackThe meeting name has been set to 'tc'20:02
ttxOur agenda for today:20:02
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:02
*** lsell has joined #openstack-meeting20:02
ttx#topic Defcore sub-committee questions about Projects vs Programs20:02
*** openstack changes topic to "Defcore sub-committee questions about Projects vs Programs (Meeting topic: tc)"20:02
ttxzehicle: hi!20:03
zehicle_at_dellhey20:03
ttxzehicle: could you summarize what those questions or concerns are ?20:03
zehicle_at_dell#topic programs20:03
zehicle_at_dellyes20:03
vishyo/20:03
*** neelashah1 has joined #openstack-meeting20:03
*** jcooley_ has quit IRC20:03
*** thuc has quit IRC20:03
zehicle_at_delldiscussion is about basically about order/membership between programs and projects20:04
*** mdurnosvistov_ has joined #openstack-meeting20:04
*** gothicmindfood has left #openstack-meeting20:04
zehicle_at_delland there's a follow-on about how programs are authorized20:04
ttxOK, I think there is confusion around the program concept.20:04
ttxAs far as "core" in concerned, the board should really only be looking at projects imho.20:04
ttxMy basic definition would be:20:04
zehicle_at_dellmy understanding of OpenStack Programs is that they are meta constructs for OpenStack that abstract large areas of function20:04
ttxProjects are code repositories ("openstack/nova")20:04
zehicle_at_delle.g.: compute, network, storage, etc20:04
ttxPrograms are actually *teams* working on a number of those code repostories, aligned with a mission statement ("Infrastructure")20:05
*** neelashah has quit IRC20:05
*** skraynev_ has quit IRC20:05
zehicle_at_dellthey also help protect OpenStack from name collisions20:05
ttxI think all the confusion stems from sometimes reusing the openstack functional name (i.e. "Compute") as the program name...20:05
zehicle_at_dellas such, a program would contain >0 projects20:05
*** troytoman-away is now known as troytoman20:05
*** sushils has quit IRC20:05
ttx...while one of the projects below them (nova) is also using that functional name (= "OpenStack Compute")20:05
zehicle_at_dellttx, my understading is the OpenStack Compute _is_ the program name20:06
ttxthe program name is "compute"20:06
annegentleFor docs, we have a list for conventional use https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_project_names20:06
ttxI guess we could rename some of the programs if that helped reducing the confusion20:06
ttxzehicle: basically, the team working on nova and python-novaclient is the compute team20:07
*** jcooley_ has joined #openstack-meeting20:07
jeblair#link http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml20:07
zehicle_at_dellwhat about glance?20:07
ttxthe progral just reflects the structure of the dev teams20:07
zehicle_at_dellhold on20:07
zehicle_at_dellI see the wiki20:07
ttxthe team working on glance and python-glanceclient is the image service team20:07
*** IlyaE has joined #openstack-meeting20:08
zehicle_at_dellso, are you suggesting that every project eventually becomes a program?20:08
ttxzehicle: no20:08
*** sparkycollier has quit IRC20:08
ttxzehicle: really, it's reusing the same name that creates the confusion20:08
zehicle_at_dellI don't think this matches how we're talking about OpenStack to users - jbryce said that he's focused on "capabliities" whichi are also described as compute, network, etc20:09
*** brianr has joined #openstack-meeting20:09
*** ThiagoCMC has joined #openstack-meeting20:09
ttxzehicle: we couldn't be having this discussion if the team working on nova and python-novaclient was called the Albator team20:09
ttxs/couldn't/wouldn't/20:09
vishyi think it makes sense to just consider a program to be a grouping of projects20:09
*** jasondotstar has joined #openstack-meeting20:09
vishyi.e. a program is a set containing 0..n projects20:09
ttxvishy: right20:09
zehicle_at_dellthat's where I was going20:09
*** woodster1 has joined #openstack-meeting20:09
ttxzehicle: but from the core / board perspective I think you should be looking at projects20:10
jeblairas long as the group can contain 0 projects20:10
zehicle_at_dellttx, no sure20:10
ttxzehicle: programs are just a way to reflect the dev teams organization20:10
vishyttx: as far as I can tell they are ignoring projects completely and going with capabilities20:10
zehicle_at_dellthe board has been working to use capabilities/tests to define core20:10
markmczehicle, yes jbryce should be talking about capabilities, more than the groups implementing those20:10
ttxand structure reflects how we work, rather than the other way around20:10
vishys/they/we (i suppose) :)20:10
zehicle_at_dellbut there's still a question about use of the OpenStack trademark20:10
ttxzehicle: in program names ?20:11
zehicle_at_dellthere's a question about how a project can use the OpenStack trademark20:11
ttxzehicle: or in project names20:11
zehicle_at_dellsince we get into challenges w/ OpenStack Neutron, etc20:11
*** rfolco has quit IRC20:11
ttxagreed20:11
zehicle_at_dellProgram Names are 1) generic and 2) can hold a trademark20:11
markmczehicle, yes there is that trademark question and the TC is keen to see the board resolve it20:11
zehicle_at_dellso, OpenStack Compute should be protectable20:11
*** joshuamckenty has joined #openstack-meeting20:12
ttxzehicle: the program name is "compute", not "openstack compute", though*20:12
zehicle_at_dellif we agree that Nova is a member of Compute, then we've have a clear way to describe the project20:12
zehicle_at_dellOpenStack Compute Project Nova20:12
markmc"OpenStack Compute" is another name for the project20:13
ttxzehicle: hmmm... not sure about that20:13
markmcnot the program20:13
zehicle_at_dellnot according to what vishy was saying20:13
ttx"Compute" program has openstack/nova proiject, also known as "OpenStack Compute"20:13
zehicle_at_dellNova is a member of Compute20:13
zehicle_at_dellbut compute could have other memembers20:13
markmcNova is a member of the compute program20:13
markmcand the Nova project is also known as OpenStack Compute20:13
zehicle_at_dellwhat is the objection to the Capital C?20:14
markmcthe compute program could have other projects20:14
annegentleCompute needs images to give capabilities though20:14
markmcwhose official names may be OpenStack Foobar20:14
zehicle_at_dellwhy is compute better/different than Compute20:14
jeblairindeed the compute program also holds the gantt and python-novaclient projects20:14
ttxzehicle: "compute" avoids using the trademark altogether20:14
*** lisaclark1 has joined #openstack-meeting20:14
*** thedodd has joined #openstack-meeting20:14
zehicle_at_dellI've been told that Compute also includes glance20:14
zehicle_at_dellnot sure that avoiding the trademark is needed/helpful20:15
markmcthe compute program doesn't include glance20:15
ttxGlance is developed by a separate team, so Glance is in a separate program20:15
zehicle_at_dellsince we specifically want to be able to say "OpenStack Foo"20:15
zehicle_at_dellso we have to deal w/ trademark20:15
markmcand OpenStack Compute is not another name for the glance project20:15
*** AlexF has joined #openstack-meeting20:15
zehicle_at_dellI think we're back to the issue20:15
zehicle_at_dellI see glance as a project20:15
*** troytoman is now known as troytoman-away20:15
zehicle_at_dellthat is a member of a program20:15
markmcit is20:15
markmcindeed20:15
*** tanisdl has joined #openstack-meeting20:15
zehicle_at_dellit's not the only member of a program,20:15
annegentleand the program is not "Images" it's "Compute"20:16
zehicle_at_dellwhy should it be the only member?20:16
ttxannegentle: ?20:16
* annegentle attempts to complete zehicle_at_dell's thoughts20:16
markmczehicle_at_dell, it's the only member right now20:16
markwashwell, python-glanceclient sort of20:16
jeblairglance and python-glanceclient are the two members of the Image Service program20:16
zehicle_at_dellI am _not_ recommending any membership at this point, just using them as examples.  that's a different discussion20:16
ttxmarkmc: well, not counting python-glanceclient20:16
zehicle_at_dellmarkmc, we agree on that on20:16
markmcttx, yeah20:16
zehicle_at_dellbut I'm not sure which programs we have20:17
annegentle@link http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml20:17
annegentleer20:17
annegentle#link http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml20:17
markmc^^ that's our list of programs20:17
zehicle_at_dellsorry, I know which are posted20:17
annegentlezehicle_at_dell: that just reflects current reality20:17
markmcIOW, our list of teams20:17
*** ameade has joined #openstack-meeting20:17
* zehicle_at_dell gets broom20:17
ttxzehicle: I'm starting to think we should have used DIFFERENT nati_ueno mes for the teams, to avoid confusion20:18
ttxnames, not nati_ueno, stupid tab completion20:18
zehicle_at_dellperhaps20:18
ttxzehicle: note: we still can20:18
ttxzehicle: easy20:18
zehicle_at_dellI'm not sure that we need for projects to take on generic names20:18
ttxzehicle: would calling it the keystone team work better ?20:19
zehicle_at_dellmaybe, but I think it's different20:19
annegentlezehicle_at_dell: honestly for docs and a user perspective we have to call it something meaningful not code-named20:19
ttxrather than the identity team ?20:19
dhellmannzehicle_at_dell: the project is the thing we release, and that's the place where the trademark is important, right?20:19
ttxdhellmann: +120:19
markmczehicle_at_dell, 20 minutes in, I really don't know what the DefCore related issue you're getting at here is20:19
markmczehicle_at_dell, maybe start again from that angle?20:19
zehicle_at_dellah, circle is complete dhellmann20:19
*** fabiog has quit IRC20:19
joshuamckentymarkmc: I believe that was the reason we suggested a F@F20:19
dhellmannall of the rest of this is just organizing people, and i'm not sure why that matters so much outside of the people being organized20:19
joshuamckentyf@f20:19
jeblairannegentle: programs aren't really for consumption by docs or users though...  really only openstack developers see them20:20
zehicle_at_dellTC asked the Board to approve then name change of Ceilometer to become a core prgram  named OpenStack Telemetry20:20
*** emagana has quit IRC20:20
dhellmanncore project, right?20:20
zehicle_at_dellsigh20:21
ttxcore project.20:21
joshuamckentythere aren't core projects, anymore20:21
zehicle_at_dellwe are not making projects core20:21
joshuamckentyjust core capabilities20:21
* zehicle_at_dell echos joshuamckenty 20:21
ttxjoshuamckenty: nor core programs, right ?20:21
joshuamckentyright20:21
joshuamckentyjust integrated releases20:21
markmcthe TC wanted the Board to allow the Ceilometer project call itself "OpenStack Telemetry"20:21
joshuamckentythere are three specific uses of the trademark20:21
dhellmanncan we make sure we're all using the words with the same meantings before we decide we don't need to use the words?20:21
zehicle_at_dellI think that we could consider programs as core if we handle the membership issue20:21
joshuamckentythat we were trying to protect in the bylaws20:21
markmcwhich, based on our interpretation of the bylaws required board approval20:21
joshuamckenty1. Use of the mark by the community of developers to refer to the product of their efforts20:22
markmcwe don't care whether that means making the project "core" or not20:22
jgriffithdhellmann: great idea :)20:22
markmcwe just think it should be allowed use that name20:22
dhellmannwe don't want core programs, because programs have multiple projects and not all of the projects in a given program are going to be core20:22
ttxzehicle: I think we shouldn't consider programs as core. They reflect how the team self-organize20:22
joshuamckenty2. Use of the mark of vendors to indicate compliance with some definition of "core"20:22
dhellmannthe tests should look at capabilities provided by projects and should not think about programs at all20:22
*** sparkycollier has joined #openstack-meeting20:22
vishyjoshuamckenty, zehicle_at_dell: that is a cool approach, but on the other hand branding the projects as OpenStack definitely has some value20:22
*** troytoman-away is now known as troytoman20:22
*** vijendar has joined #openstack-meeting20:22
*** vijendar has quit IRC20:22
zehicle_at_delldhellmann, that's a big jump20:22
*** vijendar has joined #openstack-meeting20:22
vishyso perhaps any project that implements some of said capabilites can use OpenStack in its name?20:22
joshuamckentyvishy: I'm just describing what's already been approved by the board20:23
zehicle_at_dellvishy, yes.  it has value AND it's the only stick that we really have20:23
dhellmannzehicle_at_dell: when we say "program" we do not mean "computer program" we mean "team of developers"20:23
dhellmannso why is that a big jump?20:23
zehicle_at_dellso we need to maintain some goverannce on it20:23
*** ayoung-afk is now known as ayoung20:23
markmcjoshuamckenty, zehicle_at_dell, the creation of programs (i.e. "teams") is purely a technical governance issue20:23
joshuamckentymarkmc: not if they use the mark20:23
zehicle_at_delldhellmann, perhaps we sould say Program (not program)20:23
vishymarkmc: but they don't20:23
joshuamckentyif you want to call them StackStack Program <x>20:23
markmcjoshuamckenty, we're not asking for programs to use the mark20:23
vishyjoshuamckenty: ^^20:23
joshuamckentythen there's no issue20:23
dhellmannzehicle_at_dell: I'm not sure case matters. :-)20:23
*** mestery has quit IRC20:23
ttxzehicle: definitely agree -- that's why programs should stay out of it... since programs are a reflection of our ever-changing team organization, and not of "openstack" capabilities20:23
zehicle_at_delldhellmann, it's big because you're assuming that integrated = program member20:24
vishythe mark is for projects imo20:24
dhellmannzehicle_at_dell: yes, that is a requirement from the TC20:24
dhellmannthere has to be a team backing a project for us to integrate it20:24
*** Ajaeger has left #openstack-meeting20:24
markmcjoshuamckenty, we've created the telemetry program and then *later* asking the board to allow the ceilometer project to use the OpenStack Telemetry name20:24
zehicle_at_dellvishy, that creates problems because we have to protect all the uses (which means ALL the projects)20:24
joshuamckentymarkmc: you've got the order backwards, though20:24
vishyzehicle_at_dell: well that is the whole reason for having rules20:25
jbrycejoshuamckenty: what was the 3rd use?20:25
joshuamckentybecause the "OpenStack Telemetry" program implies that the board has agreed that telemetry capabilities will be part of core20:25
vishyi'm not saying every project gets one by default20:25
joshuamckentywhich it hasn't20:25
markmcjoshuamckenty, no I don't20:25
zehicle_at_dellMy understanding (no JD degree) is that we have an issue w/ brand protection if every project could eventually use _OpenStack_20:25
vishybut there has to be a way for a project to be called OpenStack X20:25
markmcjoshuamckenty, I've got the order exactly correct :)20:25
vishyif for no other reason then that's the way it works today20:25
zehicle_at_dellwe'd have to vet every project name just in case it got inclubated20:25
joshuamckentyvishy: that's not a reason20:25
dhellmannjoshuamckenty: it sounds like you think the board should be setting the technical direction, in terms of features, which is not a responsibility I understood the board to have.20:25
vishyjoshuamckenty: actually it is20:25
zehicle_at_dellvishy, I think we'd get to a point where program membership is an additional gate beyond integrated20:26
ttxzehicle: if the telemetry program was called the doctorwho program, would we be having that discussion ?20:26
vishyjoshuamckenty: you can't go back and uncall things OpenStack Compute20:26
vishyit is all over the internet20:26
joshuamckentydhellmann: it is precisely the responsibility vested into it by by the bylaws20:26
dhellmannzehicle_at_dell: we can change the names at incubation time if there is a conflict -- that's part of the incubation process, right?20:26
zehicle_at_dellttx, yes20:26
ttxeven if ceilometer still asked to be called OpenStack telemetry ?20:26
vishyzehicle_at_dell: why make it more complicated then the board must approve using OpenStack in the name of the project?20:26
joshuamckentyvishy: true, but that doesn't mean we need a process that allows additional cases20:27
*** emagana has joined #openstack-meeting20:27
vishyjoshuamckenty: agreed20:27
dhellmannjoshuamckenty: that's now how I read 4.120:27
vishybut involving programs etc. just makes it more complicated20:27
vishywhen it could be simply stating integrated projects do not get automatic access to the trademark20:27
zehicle_at_dellvishy, I don't remember the board ever doing that except the predefined ones in the by-laws20:27
joshuamckentydhellmann: we can argue over the language if you want, but I can speak to the intent of the drafting committee20:27
vishyit must be approved by the board20:27
ttxprograms are and should stay a reflection of how our teams self-organize20:27
dhellmannjoshuamckenty: later, then20:27
ttxbecause we can't mandate how teams self-organize20:28
mikalI see programs as irrelevant to this discussing, they're just internal team structure. Defcore only cares about released software, i.e. projects.20:28
dhellmannmikal: +120:28
ttxmikal: agreed20:28
joshuamckentyDefCore cares about use of the mark that's confusing20:28
joshuamckentyand the equation of project to program20:28
dhellmannare the programs using the mark?20:28
ttxmikal: the confusion is because swe used the same names (the functional description)20:28
mikalSo can we ban the word "program" from this conversation to reduce confusion?20:28
markmcbut programs aren't using the mark20:28
zehicle_at_dellmikal, so how does that match to vishy comment that programs have >0 projects20:28
vishydoes anyone else feel like there actually isn't any debate here, and we just need to state what is actually true20:28
vishythat projects can only use the mark if approved by the board20:28
ttxjoshuamckenty: the programs are NOT using the openstack trademark though20:28
vishyand programs cannot use it20:28
mikalzehicle_at_dell: every program has at least one project20:28
markmcvishy, yes20:29
mikal(That I can recall)20:29
ttxjoshuamckenty: but just the functional description.20:29
joshuamckentygreat20:29
vishysimple problem, simple answer20:29
jeblairmikal: some programs have 0 projects20:29
joshuamckentywell, okay20:29
zehicle_at_dellmikal, can you give me an excample of a program w/ >1 project?20:29
dhellmannmikal: we have discussed some programs that won't have their own project (UX)20:29
joshuamckentythen we just need to make it more clear in community documentation20:29
ttxi.e. "compute program", not "openstack compute program"20:29
zehicle_at_delljeblair, which ones?20:29
mikalOh true20:29
vishyzehicle_at_dell: nova, gantt, python-novaclient20:29
joshuamckentythat the existence of a program does not indicate that the projects inside it will become part of openstack20:29
markmcjoshuamckenty, pointers to where it's not clear are welcome20:29
ttxjoshuamckenty: oh, definitely nOT20:29
vishyjoshuamckenty: correct20:29
mikalzehicle_at_dell: we've given you an example several times: the compute program has nova, gantt and python-novaclient20:29
jeblairoh, it looks like "Release cycle management" did grow a project, but it started without one20:30
annegentlejoshuamckenty: by doing what?20:30
ttxjoshuamckenty: the "release managemnt" program, for example, will NEVER EVER have an openstack name attached to one of its projects20:30
vishyi think we are actually all agreeing we just need to make clear statements about what exists becasue it is confusing20:30
jeblairand we have positively discussed that we would be happy to add a ux program with 0 projects (but the team for that hasn't formed yet)20:30
mikalI think we're on a tangent again20:30
joshuamckentyhttps://wiki.openstack.org/wiki/Programs20:30
mikalWhat I am getting from this is that the board wants to be the only one who can assign the openstack amrk to things20:31
joshuamckentyThis line is particularly confusing: "The Technical Committee has a mandate to review programs that wish to be included as official OpenStack programs."20:31
mikalSo we need to be careful to not call something "OpenStack Foo" until the board has been consulted, yes?20:31
joshuamckentymikal: there is a specific mandate for the community to use the mark20:31
joshuamckentybut not to refer to componets20:31
ttxjoshuamckenty: agreed, we need to clarify that20:31
markmcjoshuamckenty, sounds accurate to me20:31
joshuamckentybut just the community itself20:31
markmcthey're still official programs20:31
zehicle_at_dellso, we have an unending list of programs?20:31
vishyjoshuamckenty: I agree that page is a bit confusing from a mark perspective20:31
markmceven if we don't use the mark with them20:31
joshuamckentythey're programs of OpenStack, but not "OpenStack programs"20:31
joshuamckenty:)20:31
vishyso lets edit it to clarify20:31
ttxjoshuamckenty: I'll take that20:32
ttx"official programs of OpenStack"20:32
markmc"official programs of OpenStack"20:32
ttxor even20:32
markmcright :)20:32
joshuamckentyawesome20:32
ttx"TC-recognized prograls of OpenStack"20:32
ttxprograms20:32
zehicle_at_dellhow did the offiical programs become official?  was there a TC vote?20:32
vishyzehicle_at_dell: yes20:32
joshuamckentyYes20:32
markmcyes20:32
joshuamckentythere was a mailing list process for existing ones to submit, IIRC20:32
* ttx edited the wiki20:33
*** FallenPegasus has quit IRC20:33
mikalSo I still don't understand the ask from the board here20:33
markmcjoshuamckenty, resolved in under 30 minutes with no need for a f2f :)20:33
mikalIs it just that you want us to stop using the openstack name?20:33
markmcmikal, that programs don't use the mark20:34
ttxmikal: in a confusing way yes20:34
joshuamckentyjust stop calling them "OpenStack Telemetry", yes20:34
joshuamckentyit creates confusion20:34
mikalThat's it?20:34
markmcbut that does bring us back to *projects* using the name20:34
*** julienvey_ has quit IRC20:34
*** troytoman is now known as troytoman-away20:34
ttxjoshuamckenty: in retrospect, we should have called those programs by the codename20:34
ttxi.e. the nova program20:34
annegentlefrom an official documentation perspective, then the second change request is for the documentation conventions to stop using OpenStack Telemetry, right?20:34
zehicle_at_dellI think the gap is larger than I thought20:34
ttxand avoid confusion with the trademark altogether20:34
markmcthe TC would still like Ceilometer project to be able to use the OpenStack Telemetry name20:34
mikalWhat if we just always have "team" at the end of program names... "Compute Team", "UX Team", etc etc20:34
*** stanlagun has left #openstack-meeting20:35
*** thuc has joined #openstack-meeting20:35
markmcand the TC doesn't mean by that request that Ceilometer should be a required part of OpenStack clouds20:35
jeblairmikal: i like that because it helps us continue to use the generic name which i think has value20:35
ttxmikal: blame mordred for suggesting "program" instead of "team"20:35
zehicle_at_dellwhat happens if there's another project that wants to use the same program name?20:35
joshuamckentythat way a project that has capabilities in core can be called "OpenStack Compute20:35
joshuamckentywithout overlap on the program20:35
joshuamckentyAwesome, can we cover one other defcore issue?20:35
*** atiwari has quit IRC20:35
zehicle_at_dellfor example another approach to orchtestration?20:35
jeblairttx: if we have to use 'nova', ok, but i think it's good that 'compute program' doesn't mean 'just nova'.20:35
mikalmarkmc: yes, that's my second question from this20:35
ttxjoshuamckenty: quick yes20:35
zehicle_at_dellwould Orchestration has two projects?20:35
dhellmannzehicle_at_dell: we would ask them to collaborate with the existing team and possibly create another project20:36
mikalmarkmc: ceilometer can only be "openstack telemetry" if the board picks a capability it provides to be in the core set?20:36
joshuamckentymarkmc: we're trying to have those two things mean the same thing20:36
sparkycollierSo would it be fair to say that "The integrated release of OpenStack includes Telemetry in the Havana version" ?20:36
ttxzehicle: if the same team works on it yes20:36
markmc#link https://review.openstack.org/#/c/55375/2/resolutions/20131106-ceilometer-and-heat-official-names20:36
joshuamckentywherever possible20:36
joshuamckentye.g., OpenStack <foo> means that some foo capabilities are part of core20:36
joshuamckentymikal: yes20:36
ttxjoshuamckenty: what's the second issue ?20:36
joshuamckentythat's the current theory20:36
joshuamckentydesignated sections20:36
mikalSo we can never call something "OpenStack X" until after a capability is blessed?20:37
*** troytoman-away is now known as troytoman20:37
joshuamckentywe need the PTLs to decide what code sections are designated sections20:37
ttxmikal: the board decides how the trademark is used20:37
*** gduan has joined #openstack-meeting20:37
jeblairmarkmc: has the board taken that up yet?20:37
*** rakhmerov has quit IRC20:37
*** gokrokve has quit IRC20:37
mikalIn that case, can't we just say to the board "bless this name, this project provides the following capabiities we would like to have considered for the core set"?20:37
*** garyduan has quit IRC20:37
markmcjeblair, no, it's gotten all mixed up in this defcore stuff20:37
mikalttx: I get that, I'm trying to work out how we interact over it though20:37
dhellmannjoshuamckenty: what is "designated sections"?20:37
zehicle_at_dellwhat does same team mean?  if there are two projects, would they be the same team?20:37
joshuamckentyzehicle_at_dell: team == program20:38
mikalzehicle_at_dell: yes. A team can work on more than one project at a time. I thought we'd covered that.20:38
joshuamckentyhttps://wiki.openstack.org/wiki/Governance/CoreDefinition20:38
ttxzehicle: if they share the same core reviewers, then they are the same team20:38
*** masayukig has joined #openstack-meeting20:38
joshuamckentydhellmann: ==^20:38
joshuamckentysection 420:38
*** gokrokve has joined #openstack-meeting20:38
*** markmcclain has quit IRC20:38
joshuamckentyas a hypothetical example,20:38
lifelessback20:38
joshuamckentysince I'm not supposed to use the term "plugin",20:38
zehicle_at_dellI don't think you're leaving room for parallel efforts20:38
lifelesssorry about that20:38
joshuamckentynova might make the "conductor" a designated section20:39
dhellmannjoshuamckenty: are you seriously asking for line numbers within specific files?20:39
zehicle_at_dellif we're saying team == program because they are commonly managed20:39
joshuamckentyno, module names or some such is probably fine20:39
*** rakhmerov has joined #openstack-meeting20:39
mikaljoshuamckenty: how does a section differ from a capability?20:39
markmczehicle_at_dell, I think you're on to another topic altogether, unrelated to DefCore20:39
*** gpocente1 is now known as gpocentek20:39
joshuamckentycapabilities don't have to be implemented with the same code unless that code is a designated section20:40
markmczehicle_at_dell, i.e. "how the TC should run its technical meritocracy"20:40
joshuamckentye.g., neutron plugins20:40
mikalWait what?20:40
dhellmannjoshuamckenty: tying core branding to code organization is going to make a mess when we refactor something20:40
joshuamckentyand floating ip support20:40
zehicle_at_dellmarkmc, asking questions to resolve word choices20:40
mikalYou want us to list the blocks of code that implement floating IP support?20:40
joshuamckentyno20:40
joshuamckentythe reverse20:40
vishyzehicle_at_dell: parallel efforts as part of the integrated release is a poor choice imo, but this is a tangent20:40
mikalYou want us to list the blocks of code which don'20:40
joshuamckentythe blocks of code that vendors MUST INCLUDE to use the mark20:40
mikalt implement floating IP support?20:40
zehicle_at_dellbut it does seem to me that I should be able to ask questions about it without that push back20:40
vishymikal: they want a list of modules that must be included to still call the thing e.g. nova20:41
*** denis_makogon_ has joined #openstack-meeting20:41
mikaljoshuamckenty: that's a lot more granular than my original expectation20:41
jeblairall of them20:41
jgriffithjeblair: +120:41
joshuamckentyjeblair: nope20:41
mikaljoshuamckenty: I was expecting "all of nova except the hypervisor drivers"20:41
joshuamckentybecause some of them are hypervisor specific20:41
vishyto prevent people from rewriting the whole thing and still calling it OpenStack20:41
joshuamckentymikal: exactly!20:41
joshuamckentyeach project gets to designate20:41
mikaljoshuamckenty: no, the hypervisor specific stuff is behind a clear line in the code20:41
joshuamckentyneutron will be less, probably20:41
ttxjoshuamckenty: makes sense to me20:41
markmczehicle_at_dell, we're trying to avoid tangents, is all20:41
zehicle_at_dellwe left it to the TC to make recommendations about how to handle it20:41
vishyjoshuamckenty: curious why this is left up to the PTLs20:42
jgriffithjoshuamckenty: so "cinder-create, delete, ...."20:42
joshuamckentyglance is likely 100% as well20:42
markwashwell20:42
zehicle_at_dellmarkmc, I don't think we resolved the issues that started this20:42
jgriffithjoshuamckenty: literally call out all of the API calls?20:42
joshuamckentyvishy: who would you suggest instead?20:42
vishyjoshuamckenty: doubtful there are driver backends for glance20:42
joshuamckentyjgriffith: not api calls, code modules20:42
zehicle_at_delland now we're way off20:42
*** weshay has quit IRC20:42
jgriffithBecause modules doesn't make any sense20:42
joshuamckentyjgriffith: why not?20:42
vishyjoshuamckenty: tc would be another choice20:42
annegentlevishy: joshuamckenty: this does sound more product manager type questions than tech leads20:42
joshuamckentycinder has drivers20:42
*** masayukig has quit IRC20:42
jeblairi think this topic is very interesting but probably merits a clear/detailed proposal for us to review20:42
vishyjgriffith: loosely, which part of the code20:42
joshuamckentydrivers probably aren't designated sections20:42
dhellmannjoshuamckenty: this list is going to need to be updated for each release, is that going to be OK?20:42
joshuamckentyyup20:42
zehicle_at_delljeblair, +120:43
joshuamckentywe have to rerun defcore every release, too20:43
ttxzehicle: joshuamckenty was apparently satisfied by our changes to the use of the openstack trademark in program names20:43
mikalI am scared of the board somehow being involved in our ability to refactor code20:43
jgriffithvishy: joshuamckenty modules includes things like cinder.volume.utils20:43
*** gokrokve has quit IRC20:43
jgriffithrpc modules20:43
jgriffithlogging modules20:43
ttxzehicle: which is why we moved on to second issue20:43
jgriffithetc etc20:43
joshuamckentymikal: that's why we're not in charge of the designated sections20:43
zehicle_at_dellttx, so we're exiting that part w/o resolution. ok20:43
vishyjgriffith: the idea is (currently) the ptl decides which sections of the code are required to use the mark20:43
* dhellmann wonders if this means oslo libraries are going to start being considered as part of core20:43
joshuamckentyjgriffith: I was using modules in the generic "Code Complete" sense, not the python sense20:43
mikaljoshuamckenty: ok, but a code reviewer would still need to block a refactor to seek some form of management approval20:43
jeblairmikal: well, they can't be and won't be so don't worry.  :)20:43
*** woodster1 has quit IRC20:43
joshuamckentymikal: why?20:44
zehicle_at_dellmissed the #topic modules definition in core20:44
jgriffithvishy: I get it... easy enough20:44
joshuamckentythat management approval is from the PTL20:44
ttxzehicle: resolution was: do not call programs "OpenStack X" anymore20:44
*** denis_makogon_ is now known as denis_makogon20:44
mikaljoshuamckenty: because it might change what is in the defnitiion and what isn't20:44
vishyjoshuamckenty: that makes sense... i.e. must use the API code, must use the RPC code20:44
joshuamckentyzehicle_at_dell: designated sections20:44
*** salv-orlando has quit IRC20:44
mikaljoshuamckenty: let's say you list all the capabilities of nova in core, _except_ floating IPs20:44
vishywithout getting to the level of every python module/file included20:44
* zehicle_at_dell corrected20:44
mikaljoshuamckenty: how do we then define what bits of the common nova code aren't for floating IPs?20:44
*** salv-orlando has joined #openstack-meeting20:44
annegentlettx: I'd still like an agreement logged about https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_project_names20:44
joshuamckentymikal: you don't have to20:44
*** cgoncalves has joined #openstack-meeting20:44
mikaljoshuamckenty: and what happens when I refactor that code and break the defined list as a side effect20:44
ttxzehicle: I though joshuamckenty was echoing the same concern you were - and so if he was happy with that resolution you were, too20:45
zehicle_at_dellttx, that does not resolve issue.  just side steps naming20:45
joshuamckentymikal: if you put it in the designated section, that's your business20:45
markmcok, look20:45
joshuamckentyzehicle_at_dell: the naming issue is separate from the "parallel efforts" issue20:45
markmcif zehicle_at_dell doesn't agree the issue is resolved20:45
markmclet's stop the other thing20:45
joshuamckentybut I don't want to try and deal with parallel efforts over IRC20:45
*** markmcclain has joined #openstack-meeting20:45
ttxzehicle: then I don't get your issue. Expressing it on ML first would have helped explaining it20:45
markmczehicle_at_dell, re-state how we're "side-stepping naming" ?20:45
jeblairannegentle: only the board-approved projects can use openstack names20:46
*** weshay has joined #openstack-meeting20:46
* mikal pauses on the designated sections thing to let the naming debate restart20:46
*** elo1 has quit IRC20:46
jeblairannegentle: so it is premature to call ceilometer "OpenStack Telemetry"20:46
ttxOK, back to first issue20:46
*** woodster1 has joined #openstack-meeting20:46
*** iccha has joined #openstack-meeting20:46
jeblairannegentle: same for heat20:46
joshuamckentyparallel effort issue is the following:20:46
ttxjoshuamckenty: are your concerns answered now, or is it just sidesteps ?20:46
*** markpeek has quit IRC20:46
* zehicle_at_dell suggests that I review commends based on updated information and discussion and start thread on list20:46
ttxzehicle: that would help20:47
annegentlejeblair: ttx: do we need a review patch to reverse the resolution in our governance repo?20:47
ttxzehicle: with limited shared context, ML usualluy works better to explain one's point20:47
*** elo1 has joined #openstack-meeting20:47
jeblairannegentle: the resolution was that we ask the board to consider allowing it; they have not done so yet20:47
jeblairannegentle: we can not decide that ourselves (and we did not try, we only asked)20:47
ttxzehicle: otherwise we'll talk past each other for 15 more minutes20:47
zehicle_at_dellI was trying to get a thread but wanted to get more input before it launched - sorry that wasted some time.  I think this discussion will help influence the thread20:47
ttxzehicle: consider it a good bootstrap ;)20:48
ttxso... back to issue #2 ?20:48
zehicle_at_dell+120:48
joshuamckentyso was there a suggestion to have the TC own the designated sections instead of the PTLs?20:48
markmcrestate #2?20:48
ttxTC vs. PTL to designate critical code sections20:48
markmcttx, just to be clear20:48
vishyplease no thread20:48
*** sdake has quit IRC20:48
jeblairttx, markmc: back me up here on https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_project_names -- i think it's important because it appears to be an actual use of the mark outside of what we agreed20:48
jeblairand annegentle rightly wants clarity there20:49
annegentleyes please20:49
*** slagle has quit IRC20:49
*** hub_cap has joined #openstack-meeting20:49
jbrycei'm confused on this too20:49
annegentleand in a logged manner so I can point the doc team to it20:49
markmcjeblair, sorry, I agree with what you said - we do not yet know that Ceilometer and Heat cannot yet be called OpenStack Telemetry and OpenStack Orchestration20:49
ttxjeblair: the board is currently changing the rules for trademark usage. So obviously the doc needs to be updated to reflect that, if necessary20:49
jbryceSection 4.1 - "The Core OpenStack Project means the software modules which are part of an integrated release and for which an OpenStack trademark may be used. The other modules which are part of the OpenStack Project, but not the Core OpenStack Project may not be identified using the OpenStack trademark except when distributed with the Core OpenStack Project."20:49
lifelessmarkmc: *blink* double negative?20:49
vishyttx, zehicle_at_dell: imo, this issue is resolved, and any further discussion on the ML is just extra beauracracy that wastes everyones time20:50
annegentlettx: and the stable/havana branch changed?20:50
markmclifeless, sorry20:50
ttxvishy: if zehicle still has concerns, he can raise a thread20:50
*** sdake has joined #openstack-meeting20:50
*** sdake has quit IRC20:50
*** sdake has joined #openstack-meeting20:50
jbryceceilometer and heat are "other modules" (second sentence) distributed with the Core OpenStack Project20:50
ttxvishy: don't feel forced to participate to it :)20:50
markmcjeblair, sorry, I agree with what you said - we do not yet know that Ceilometer and Heat may be called OpenStack Telemetry and OpenStack Orchestration20:50
annegentlejbryce: appreciated20:50
vishyttx: ok I will ignore it then :)20:50
zehicle_at_dellvishy, you can ignore if you'd like.  perhaps some 1x1 will be useful20:50
markmcjeblair, I'm using that language because I think you could interpret the bylaws like jbryce and say we could use those names20:51
zehicle_at_dellvishy, can bring you up on DefCore too20:51
vishyzehicle_at_dell: sure no problem there20:51
markmcjeblair, but I'm being cautious - i.e. I don't think there's consensus on the interpretation20:51
vishyzehicle_at_dell: but really there is way to much pointless discussion around these topics. Most of the questions are simple20:51
ttxSo. On that second topic. I'd propose the PTLs propose sections and the TC approves them20:51
vishyand we can talk about them forever20:52
vishyttx: +120:52
joshuamckentyvishy: that's an unnecessary ad-hominem attack20:52
sparkycollierI read it as "you can talk about Telemetry in the context of OpenStack because it's part of the integrated release"20:52
mikalttx: with the understanding that the default proposal is "anything outside the drivers" I'm ok with that20:52
joshuamckentymikal: the default state for DefCore is 0%, unless we hear otherwise :)20:52
vishyjoshuamckenty: ?20:52
vishyjoshuamckenty: we just went through 20 minutes of agreeing and being unwilling to state what the agreement was20:53
joshuamckentyvishy: "You should stop talking about this because it's simple and this discussion is pointless"20:53
ttxjoshuamckenty: so the TC will take the ball on that section definition thing20:53
*** thuc has quit IRC20:53
mikaljoshuamckenty: I think that's almost exactly backwards for the projects which use the trademark20:53
vishyjoshuamckenty: if there is disagreement i'm all for discussion20:53
joshuamckentymikal: how so?20:53
vishyjoshuamckenty: but afaict ther is no disagreement20:53
vishysomeone just needs to say "this is the agreement" and we can all ratify it20:53
*** thuc has joined #openstack-meeting20:53
joshuamckentyvishy: there is clear disagreement on a complex issue. We just agreed on the easy part20:53
ttxjoshuamckenty: any deadline for proposing initial sets ?20:53
*** asalkeld has joined #openstack-meeting20:53
jeblairttx: i missed the last board meeting; is this whole process documented somewhere?  as the tc do we know clearly what the board is asking us to do?20:53
mikalIf you let nova use the openstack mark, for example, then the default assumption should be that 100% of its code is covered by defcore20:54
ttxjeblair: no, it's all new20:54
joshuamckentymikal: no, 0%20:54
mikalWe should then _exclude_ bits we think are ok for vendors to hack on20:54
joshuamckentywell, unknown20:54
mikaljoshuamckenty: I get that's what you're saying20:54
dhellmannjeblair: yeah, I'd like to have a clearer understanding of the form this recommendation should take20:54
mikaljoshuamckenty: I'm disagreeing with you20:54
jeblairjoshuamckenty: is there something, somewhere i can read about what you're asking us to do other than what you've said in this meeting?20:54
joshuamckentyokay, I'm not defending a position20:54
zehicle_at_dellwe're confusing the project using the mark and a commercial business using the mark20:54
joshuamckentyjust asking for one20:54
dhellmannbecause mikal's statement seems like the right sort of level of detail20:54
joshuamckentyjeblair: there's the link I posted earlier20:54
joshuamckentyhttps://wiki.openstack.org/wiki/Governance/CoreDefinition20:54
zehicle_at_dellbut they are related topics20:55
*** Daisy has joined #openstack-meeting20:55
mikaljoshuamckenty: we should be defining areas for vendors to compete in20:55
joshuamckentyYES! That's the point of the designated sections20:55
joshuamckentysome projects will be 100% competitive, some may be 0%20:55
mikaljoshuamckenty: yes, but the default should be to say no to vendor patches20:55
joshuamckenty0% is likely not good for the users, 100% is bad for the developers20:55
mikaljoshuamckenty: and then designate sandboxes they can play with20:55
sparkycollierDefcore is about the commercial use AFAIK as stated in teh first sentence of the wiki "The following list represents the "guiding principles" used by the Foundation Board to determine how commercial implementations of OpenStack can be granted use of the trademark"20:56
mikal10)% is great for developers who understand open source20:56
joshuamckenty0% makes interop very hard20:56
mikal100% even20:56
mikalAnd I'm not sure I care about vendors who want to ship crazy private drivers20:56
lifelessmikal: what about e.g. keystone20:56
lifelessmikal: which started as a replacement project20:56
joshuamckentysparkycollier: which is why "projects and programs" isn't directly in DefCore's purview20:56
*** Ajaeger has joined #openstack-meeting20:56
mikalIf the driver isn't good enough to land in our git repos, why should we encourage it?20:56
joshuamckentybut it *is* problematic20:56
joshuamckentymikal: ask Rackspace20:56
*** AlexF has quit IRC20:57
ttxOK. We'll continue that discussion on openstack-dev20:57
mikaljoshuamckenty: pardon?20:57
joshuamckentyRackspace would lose the use of the mark depending on how the designated sections code goes20:57
dhellmannmikal: I think what joshuamckenty means is that even if the code is in our repo, it may not be required to be used at runtime20:57
*** woodster1 has quit IRC20:57
vishymikal: -120:57
joshuamckentybecause they don't run many openstack things20:57
ttx#action ttx to raise thread on defining critical sections in projects, TC vs. PTL20:57
joshuamckentythat was true for HP up until relatively recently20:57
joshuamckentyand still true today for Dreamhost cloud b/c of the ceph usage20:57
mikalSure, and this is what we're trying to fix20:58
joshuamckentyditto for, I believe, almost every vendor20:58
ttx#action zehicle to raise thread with unaddressed concerns about programs, if any20:58
mikalSo let's not build a system which perpetuates the fail20:58
joshuamckentyNebula and Piston, certainly20:58
*** thuc has quit IRC20:58
*** jrist has quit IRC20:58
joshuamckentymikal: be very careful how you define "fail"20:58
joshuamckentyfail for devs, or for users?20:58
joshuamckentyor for vendors?20:58
markwashso we want to make a mark that no one uses?20:58
ttxmikal: we need to wrap up. Josh asked for a position, we'll define it20:58
joshuamckentythanks20:58
annegentlettx: did you have an action to edit the OpenStack Program wiki page?20:58
mikaljoshuamckenty: for users and devs. I thought the goal here was to encourage interop?20:58
*** atiwari has joined #openstack-meeting20:58
ttxannegentle: I multiplexed and did it20:58
annegentlettx: nice20:59
*** nati_ueno has quit IRC20:59
joshuamckentymikal: but not at the total expense of the commercial ecosystem20:59
joshuamckentyttx: and https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_project_names ?20:59
* vishy looks forward to the ml discussion on point #220:59
annegentle#action annegentle to edit https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_project_names20:59
ttxLooks like Barbican will be considered next week20:59
*** asalkeld has quit IRC20:59
joshuamckentythanks everyone for the time20:59
vishythanks for jumping in joshuamckenty zehicle_at_dell20:59
ttxjoshuamckenty: you're welcome20:59
* zehicle_at_dell thanks everyone! until next time20:59
lifelessciao21:00
*** sparkycollier has quit IRC21:00
ttx#topic Minor governance changes21:00
*** openstack changes topic to "Minor governance changes (Meeting topic: tc)"21:00
*** lisaclark1 has quit IRC21:00
ttxAdd a requirement for deprecating duplicated code (https://review.openstack.org/#/c/70389/)21:00
*** joshuamckenty has quit IRC21:00
*** sparkycollier has joined #openstack-meeting21:00
ttxI think that one needs a few more iterations on Gerrit21:00
*** nati_ueno has joined #openstack-meeting21:00
ttxI'll approve it once it reaches the approval threshold though, so vote -1 if you want to block it21:01
ttxand... no time for open discussion21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Feb  4 21:01:38 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-02-04-20.02.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-02-04-20.02.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-02-04-20.02.log.html21:01
jeblairooh, can we have another meeting?21:01
ttxyeah21:01
markmcyippee21:02
ttxdhellmann, dolphm, notmyname, jd__, markwash, jgriffith, russellb, stevebaker, david-lyle, markmcclain, hub_cap: around ?21:02
annegentlejeblair: your wish is granted21:02
markwasho/21:02
dhellmanno/21:02
notmynamehere21:02
markmcclaino/21:02
jd__o/21:02
dolphmo/21:02
jgriffitho/21:02
*** sdake has quit IRC21:02
*** reaperhulk has left #openstack-meeting21:02
*** lisaclark1 has joined #openstack-meeting21:02
david-lyleo/21:02
Daisyo/21:03
SergeyLukjanovo/21:03
devanandao/21:03
ttx#startmeeting project21:04
openstackMeeting started Tue Feb  4 21:04:05 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:04
lifelesso/ but otp too21:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:04
*** openstack changes topic to " (Meeting topic: project)"21:04
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:04
openstackThe meeting name has been set to 'project'21:04
ttx#topic icehouse-3 progress21:04
*** openstack changes topic to "icehouse-3 progress (Meeting topic: project)"21:04
*** Gordonz has quit IRC21:04
ttxWe reviewed this on various 1:1s, progress doesn't look too bad21:04
ttxBut you should definitely take advantage of the calm queue to finalize a few blueprints21:04
ttxneutron should be back in the game soon, which will create load21:04
hub_caphowdy21:04
ttxso I'd recommend to review and approve what you can *now*21:05
ttxgate 9-deep at 2100 UTC, that's been a long time21:05
ttxso take advantage of it21:05
ttx#topic icehouse velocity compared to previous cycles21:06
*** openstack changes topic to "icehouse velocity compared to previous cycles (Meeting topic: project)"21:06
*** MaxV has joined #openstack-meeting21:06
ttxI looked into icehouse-2's velocity21:06
ttxIt appears that icehouse-2 was not that catastrophic, if you compare it with last year's grizzly-221:06
ttxKeystone, Glance and Horizon in particular did a lot better this year21:06
ttxSo I think we just need to acknowledge that the second milestone in October-April cycles is not that busy21:06
ttxlearn from history, which repeats itself21:06
dolphmdefine catastrophic?21:06
*** mounirb has joined #openstack-meeting21:07
ttxdolphm: some were thinking we did less than 33% of what we expected21:07
ttxbased on blueprint targets21:07
ttxWe usually catch up that little 2nd milestone with a very busy 3rd milestone though, compared to April-October cycles21:08
*** gokrokve has joined #openstack-meeting21:08
ttxSo we'll see how it goes21:08
jeblairoy21:08
ttxcomments on that ?21:08
*** resker has quit IRC21:08
*** jlibosva has quit IRC21:08
*** zehicle_at_dell has quit IRC21:08
dolphm"based on blueprint targets" is basing a statement on a LOT of variables :)21:08
jeblairso i think that's what's driving sdague's proposal to slim the gate down; hopefully we'll move that along soon21:08
*** elo1 has quit IRC21:08
*** esker has joined #openstack-meeting21:08
*** mrda_away is now known as mrda21:09
jeblair(also, zuul and nodepool scaling improvements are in progress), hopefully should help with i3 gate load21:09
*** sparkycollier has quit IRC21:09
ttxdolphm: right. But it created a feeling. Which we had to address before it became a rumor21:09
jeblairttx: because after rumor is truth...21:09
*** gokrokve_ has joined #openstack-meeting21:10
ttxespecially when picked up by lazy journalists21:10
ttxanything else on that topic ?21:10
annegentlettx: snort21:10
ttxjeblair: btw there are a bunch of tripleo things stuck in the queue pipe, I suppose that's a known issue ?21:10
*** kgriffs has joined #openstack-meeting21:11
jeblairttx: yes, tripleo cloud is offline, tripleo ops are working on it21:11
*** radez is now known as radez_g0n321:11
*** jrist has joined #openstack-meeting21:11
jeblairlifeless: is on it21:11
ttxack21:11
*** dvarga has quit IRC21:11
ttx#topic log translation plan (dhellmann)21:12
*** openstack changes topic to "log translation plan (dhellmann) (Meeting topic: project)"21:12
ttxdhellmann: around?21:12
dhellmannhere21:12
dhellmannLog translations came up on the mailing list recently21:12
*** asalkeld has joined #openstack-meeting21:12
ttx#link https://blueprints.launchpad.net/oslo/+spec/log-messages-translation-domain21:12
dhellmann#link http://lists.openstack.org/pipermail/openstack-dev/2014-January/025572.html21:12
dhellmannI will be writing all of this up on the LoggingStandards wiki page, but wanted to cover it briefly here to make sure all of the PTLs understand the approach we’ve settled on so there are no surprises.21:12
dhellmannWe have requests to separate the log message translations from other translations.21:12
dhellmannWe’ve recently added the ability to log in multiple languages as part of this.21:12
dhellmannNext, we are going to add separate translation marker functions similar to _() with names like _LE and _LW to allow us to extract the messages into different catalogs.21:12
dhellmannHaving separate catalogs will let each translation team prioritize which, if any, log messages they translate for their operators.21:12
dhellmannWe are going to skip debug messages, for this phase of the project, and focus only on messages at INFO or higher levels.21:12
dhellmannWhen we’re ready, reviewers should ensure that log messages are translated using the function for the level associated with the log output (info, warning, etc.).21:12
dhellmannThe _() marker should only be used for end-user messages from exceptions and API calls.21:12
*** lbragstad has joined #openstack-meeting21:12
dhellmannissues or questions?21:13
hub_caplol21:13
markwash_LE => error, _LW -> warn ?21:13
*** gokrokve has quit IRC21:13
ttxprocessing...21:13
dhellmannmarkwash: yes21:13
*** oubiwann_ has quit IRC21:13
dhellmannunfortunately, we can't just pick up messages from the LOG.foo() calls directly, so we have to have marker functions for them21:14
ttxdhellmann: Like this plan. Been talking about it for some time now21:14
bknudson_() is for debug?21:14
dhellmann_() is for user facing messages21:14
dhellmannwe aren't translating debug messages21:14
markwash"" is for debug ;-)21:14
dhellmannright21:14
ttxit's the only way to get decent i18n coverage anyway21:14
devananda++21:14
*** gokrokve_ has quit IRC21:14
bknudsonso if we've got _() on debug message, remove it?21:15
dhellmannttx:  yeah, I think we *finally* have agreement on an approach21:15
dhellmannbknudson: yes, eventually21:15
*** aignatov is now known as aignatov_21:15
DaisyYes. Translators want t focus on high priority messages to translate.21:15
devanandadhellmann: is this written up somewhere yet?21:15
dhellmannbknudson: once all of the tools are in place, I'll announce all of this on the dev mailing list and encourage people to make the updates21:15
dhellmannit will be up to the individual projects to decide how they do that, of course21:15
*** andreaf has joined #openstack-meeting21:15
devananda^ answerd my question, thanks21:15
*** termie has joined #openstack-meeting21:15
dhellmannat this point I'm mostly looking for +0 or -2 votes :-)21:16
hub_capworks for me (/me looks into actually getting the i18n set up in trove)21:16
*** lisaclark1 has quit IRC21:16
*** mdomsch has quit IRC21:16
bknudsonchoosing _() for user facing seems like it will wind up catching a lot of debug unless we go through and remove _() from all debug21:16
ttxall seem in agreement21:16
bknudsonsince that's what they are now21:16
dhellmannbknudson: yes, all messages are marked like that now21:16
*** mdomsch has joined #openstack-meeting21:17
*** mattoliverau has joined #openstack-meeting21:17
*** sdake has joined #openstack-meeting21:17
*** sdake has quit IRC21:17
*** sdake has joined #openstack-meeting21:17
dhellmannI recommend updating all messages in a given file to the right translation marker at the same time, but not necessarily doing it for all files in a projects in one patch because of merge conflicts21:17
Daisymessages marked with _() was around 7000+ in Havana.21:17
*** neelashah1 has quit IRC21:17
jd__so we would have to change debug from _() to "" ?21:17
dhellmannDaisy: wow21:17
dhellmannjd__: right21:17
notmynametranslating log messages seems weird to me. but I'm a native English speaker, too, so I feel I'm probably biased21:17
*** andreaf_ has quit IRC21:18
dhellmannnotmyname: yeah, this is a specific request we've had from some operators21:18
jd__dhellmann: I don't like that, can't we teach log to ignore _() if the level is debug?21:18
*** lsell has left #openstack-meeting21:18
dhellmannthe previous approach of using _() for everything overwhelmed translators for languages where the operators didn't care about this21:18
kgriffsmy only reservation is it may make it harder for an operator to google and find help21:18
kgriffsbut, I think that is solvable by writing error codes21:18
ttxok, next topic ?21:18
dhellmannkgriffs: the logs can actually output in multiple languages at the same time21:18
kgriffsdhellmann: gtk!21:18
dhellmannttx: that's all I had21:18
markwashkgriffs: I think its optional to decide to run with logs in a given locale, no?21:19
*** sdake has quit IRC21:19
dhellmannmarkwash: also true21:19
*** sushils has joined #openstack-meeting21:19
notmynamekgriffs: ya, that was my concern too21:19
*** sdake has joined #openstack-meeting21:19
*** sdake has quit IRC21:19
*** sdake has joined #openstack-meeting21:19
*** lbragstad has left #openstack-meeting21:19
notmynamedhellmann: so log in different languages for twice the fun?21:19
notmynameand by fun I mean log volume21:19
dhellmannnotmyname: sure, it's a balance between knowing exactly what the error means and being able to deal with it, and having to look everything up because you don't read english21:19
*** emagana has quit IRC21:20
dhellmannnotmyname: and pick as many languages as you like, to multiply the fun ;-)21:20
dhellmannttx: I think we can move on21:20
ttx#topic discuss the move to unversioned endpoints in the service catalog (annegentle/dolphm)21:21
*** openstack changes topic to "discuss the move to unversioned endpoints in the service catalog (annegentle/dolphm) (Meeting topic: project)"21:21
jd__dhellmann: I had a question if you missed it but that can wait :)21:21
dolphmo/21:21
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2014-February/026079.html21:21
annegentlehere21:21
*** egallen has joined #openstack-meeting21:21
ttxso there seem to be a need for discussion here21:21
dolphmthere's also a second thread about this on list; one sec21:21
dhellmannjd__: sorry, I did, I'll come back to it during open discussion21:21
dolphmhttp://lists.openstack.org/pipermail/openstack-dev/2014-February/026177.html21:21
dolphm#link http://lists.openstack.org/pipermail/openstack-dev/2014-February/026177.html21:22
*** sarob has quit IRC21:22
*** alexpilotti has quit IRC21:22
*** baoli has joined #openstack-meeting21:22
dolphmthis second thread is quite long and just picked up momentum today21:23
*** baoli has quit IRC21:23
dolphmour goal for keystone is to allow our client to support unversioned auth_url's, and authenticate according to the available API (and that's done as of the current release)21:23
dolphme.g. http://paste.openstack.org/raw/62480/21:23
*** baoli has joined #openstack-meeting21:23
dolphmwe also want to move from /v2.0/ for identity endpoints in the service catalog, directly to an unversioned endpoint21:24
dolphmwhich has brought up a few questions21:24
*** SlickNik has left #openstack-meeting21:25
dolphmone of the questions brought up in the second thread was whether or not the community had any interest in supporting older clients21:25
*** thuc has joined #openstack-meeting21:25
dolphmif, for example, keystone immediately dropped the versioned endpoint in the service catalog, we'd break clients from the pre-havana timeframe -- is that a problem?21:26
*** Ajaeger has quit IRC21:26
ttxdolphm: well, we said in the past that you should always be running the latest client21:26
ttxa.k.a. we don't maintain stable branch of clients21:27
markmcttx, could be a different language21:27
ttxor "the mordred rule"21:27
markmcmy instinct is that yes, it's an issue21:27
markmcwithout a lengthy deprecation period21:27
dolphmwe've been operating under the assumption that we want to support the last year or so of client releases as much as possible, which has been challenging/frustrating21:27
ttxbut i agree that we should avoid breaking if we can21:28
annegentledolphm: I think you'd need at least a year of deprecation warnings21:28
markmcit's not just client releases - think about raw usage of the API, without client libraries published by us21:28
kgriffsyes, SDK authors everywhere would be up in arms21:28
*** emagana has joined #openstack-meeting21:28
dolphmmarkmc: so that brings up another subtlety...21:28
annegentledolphm: but so much of the onus of the warnings would be on the deployers themselves?21:28
dolphmthis isn't an API change, it's a default configuration / documentation change that has impact on clients21:29
markwashit seems a shame that the goal of excellence (providing integrated CI for stable supported stuff) gets in the way of the goal of good (providing a fix version like keystoneclient 0.X.1 as a fix for 0.X.0)21:29
dolphmthe API stays the same, it's just the value being returned by the API is new, and requires a new client respond to it correctly21:29
markmcdolphm, then perhaps recommend that ops change from the default if they themselves don't care about older clients?21:29
dhellmanndolphm: what if instead of http://host/ returning the list of versions, we add "/versions" to the published endpoint and if that URL is under a version it only returns itself?21:30
markmcdolphm, and warn them we're going to change the default ourselves in N releases ?21:30
*** amcrn has quit IRC21:30
annegentlemarkmc: that's my thinking too, we change the install guide to indicate how to set up your catalog differently21:30
*** cdub has joined #openstack-meeting21:30
*** sarob has joined #openstack-meeting21:30
annegentlemarkmc: then the providers are responsible for communicating endpoint changes (which still sounds awful)21:30
dolphmmarkmc: what do we do in devstack in the mean time? the new recommended value? or continue with the pending-deprecation value?21:30
*** changbl has quit IRC21:31
markmcannegentle, yeah21:31
*** jcooley_ has quit IRC21:31
annegentleI think you have to communicate pending deprecation for a while, year at least (2 releases I really mean)21:32
ttxmarkmc: oh, so that would amount to stable API change ? Yeah. Bad.21:32
markmcdolphm, yeah, I don't know - sorry, I'm just blindly saying "this does sound like the kind of breaking change we don't want"21:32
*** DinaBelova is now known as DinaBelova_21:32
markmcdolphm, without understanding the issue in full detail21:32
annegentlemarkmc: dolphm: it still seems tied into changing Identity v3 API, right?21:32
markmcdolphm, changing the default in devstack may be fine21:33
dolphmit is... so what i don't want to do is publish the /v3/ endpoint in the catalog as well, which is just confusing and sets a terrible precedent for other projects21:33
annegentledolphm: and I don't yet understand if the python-keystoneclient supports Identity v3 API?21:33
ttxdolphm: sounds like this thread could see some more aging21:34
ttxit's not ready to be drunk yet21:34
dolphmannegentle: the client library fully support the v3 API, however v3 is not exposed at all to the CLI21:34
dolphmttx: i'm in the same boat, i'm actually not caught up on the second thread yet21:34
*** emagana has quit IRC21:34
annegentledolphm: ok that's useful21:34
dolphmbut happy to warm everyone up to the topic :)21:34
ttxok, let's continue discussion on that thread, because without more context it's difficult to say more than "change is bad"21:35
dolphmannegentle: the goal is to transfer responsibility for CLI exposure to python-openstackclient21:35
annegentlettx: dolphm: this thread also matters for projects like heat that want to go completely to Identity v321:35
dolphmannegentle: ++21:35
annegentleso I'm good with percolation for a while21:35
dolphmttx: bring it up again in a week or two?21:35
ttxdolphm: sure21:35
ttx#topic discuss Glance scope expansion (markwash)21:36
*** openstack changes topic to "discuss Glance scope expansion (markwash) (Meeting topic: project)"21:36
markwasho/21:36
*** neelashah has joined #openstack-meeting21:36
ttxmarkwash: want to introduce the subject ?21:36
markwashsure21:36
*** neelashah has quit IRC21:36
markwashwe're looking at adding on to the v2 api to make glance a suitable place to catalog other types of resources21:36
markwashthings like whole instance specifications (in terms of block device mapping, etc), heat templates, murano packages, what-have-you21:37
*** doron_afk has joined #openstack-meeting21:37
markwashthe idea is sort of, if an openstack service uses a certain artifact as a starting point for users, it would be nice to have it in a catalog like images21:37
markwashand track dependencies21:37
markwashanyway, this could be seen as scope expansion21:38
markwashin my view, its more of refining the original scope21:38
markmc"launchable resources"?21:38
markwashso I wanted to bring it up with other folks to see if the idea initially makes sense to you21:38
markwashmarkmc: something like that21:38
david-lylemarkwash: and then just filter by type in the API call?21:39
*** masayukig has joined #openstack-meeting21:39
markwashyeah something along those lines21:39
markwashdavid-lyle: ^^21:39
*** mestery has joined #openstack-meeting21:39
hub_capso do u see Trove's heat templates it uses to generate clusters as falling under that21:39
*** elo1 has joined #openstack-meeting21:39
markwashwe don't have an established api spec yet21:39
*** jhenner has quit IRC21:40
*** mestery has quit IRC21:40
kgriffsmarkwash: what is an example of something that would NOT be appropriate to store in Glance under this project scope refinement?21:40
devanandamarkwash: would you see that catalog containing references to only launchable things, or also buildable things (eg, diskimage-builder elements), or components of things (eg docker) ?21:40
ttxcatalog, index...21:40
hub_capi think its valid, we are currently storing a ton of stuff in /etc21:40
hub_capkgriffs: ice cream21:40
kgriffsw00t21:40
markwashhub_cap: hmm, I might have to get back to you on that one, it depends sometimes on who the consumer of the resource is21:40
*** mestery has joined #openstack-meeting21:40
ttxmarkwash: I certainly prefer to see those in Glance than in separate projects21:40
david-lyle+121:41
markmcmarkwash, have you heard any concerns or disagreements about the idea from others that you could summarize?21:41
annegentlemarkwash: I'm with ttx in collecting21:41
markwashkgriffs: well, for example, keypairs probably wouldn't21:41
markwashmaybe that's not a great example21:41
*** lisaclark1 has joined #openstack-meeting21:41
kgriffsI guess my point is, it may be helpful to specify some things that are out of scope to help avoid this getting out of hand.21:41
*** crandquist has joined #openstack-meeting21:41
hub_capyea and how is this diff from say, config aas?21:41
annegentlemarkwash: and from a docs standpoint it'll be a bit of a tough transition to 'splain what all can be stored in a glance catalog21:42
kgriffsotherwise, people might start storing ice cream, pop-tarts, and all kinds of goodies in there. :p21:42
hub_capkgriffs: ice cream is not allowed :)21:42
* kgriffs sad panda21:42
markwashkgriffs: lol well they'd have to be somehow openstack affiliated pop-tarts :-)21:42
markwashkgriffs: but your point is taken21:42
kgriffscool beans21:42
markwashscrolling back21:43
dhellmannsome of these things could also be thought of as belonging in an object store, though having a catalog query api on front is definitely nice -- that might be another area where you could talk about differences21:43
*** masayukig has quit IRC21:43
markwashdevananda: I'll have to think a bit more about buildable things. . that sounds like it might be more of a workflow21:43
markwashmarkmc: no big concerns yet but we've been in a bit of a silo21:44
markwashbut I think making the class of artifacts clear is an obvious concern21:44
ttxmarkwash: next step: ML thread, then you can propose a mission statement for the TC21:44
ttxlong overdue anyway21:44
markwashannegentle: good point21:44
*** armax has left #openstack-meeting21:45
markwashokay, thanks for the feedback folks21:45
markmcttx, I'd suggest a mission statement for the current scope21:45
hub_capmarkwash: do u think that this could get into a config aas system ? wasnt something recently propsed?21:45
markwashsorry if I missed some questions21:45
hub_capu can answer tha toffline21:45
hub_cap*that21:45
*** dprince has quit IRC21:45
*** sarob has quit IRC21:45
markmcand then, later, when the details of the proposal for a new API is fleshed out ...21:45
ttxmarkmc: as a first step ?21:45
hub_capim channeling ttx's keyboard today21:45
markwashhub_cap: I'm not really familiar with config aas21:45
markmcrevisit expanding the scope in the mission21:45
markwashhub_cap: maybe we can discuss over sours21:45
ttxhub_cap: I switched mine with yours21:46
markmci.e. don't lead scope expansion simply with a mission statement tweak21:46
hub_caplol ttx :)21:46
ttxhub_cap: works a lot better.21:46
hub_capmarkwash: first sour sunday in berkeley is at the start of beer wk. i expect to see u there21:46
ttxmarkwash: maybe start with the current mission statement, like markmc said21:46
markwashwell, in a way you could see this idea coming out of the question "what is our mission exactly?"21:47
*** elo1 has quit IRC21:47
ttxmarkwash: so far I'd say that was serving disk images21:47
markwashwell21:47
markwashwe don't serve them, we prefer you download them directly21:47
markwashand they're often not jsut disk images21:47
markwashso yeah21:47
markwash:-)21:47
markwashconsidering container format can be ovf etc21:48
ttxor registry21:48
ttxfeel free to prepare the terrain21:48
markwashsounds good21:48
ttx#topic Red Flag District / Blocked blueprints21:48
*** openstack changes topic to "Red Flag District / Blocked blueprints (Meeting topic: project)"21:48
ttxheat/x-auth-trust (Low, shardy, icehouse-3) depends on keystone/trusts-chained-delegation (Undefined, No assignee, No milestone)21:48
ttxdo we have shardy, zaneb or stevebaker ?21:49
dolphmboth of these are assigned to shardy -- and i believe i've seen progress on the keystone side?21:49
dolphmthere's nothing linked in the review though21:49
dolphmin the bp*21:49
ttxdolphm: question was about the lack of targeting on the keystone one21:49
*** troytoman is now known as troytoman-away21:49
annegentledolphm: yeah that keystone bp is without work on it so far I think?21:50
ttxdolphm: you could consider making it low/icehouse-3 ?21:50
* ttx digs for reviews21:50
dolphmttx: happily, but i'd like to follow up with shardy :)21:50
*** gyee has quit IRC21:50
*** doug_shelley66 has quit IRC21:51
*** balajiiyer has joined #openstack-meeting21:51
*** IanGovett1 has quit IRC21:51
*** zaneb has joined #openstack-meeting21:52
ttxhah21:52
zanebsorry :(21:52
dolphmah, the specification was proposed, but not the implementation21:52
zanebshardy is not around atm21:52
zanebbut this is not a bp I have heard much about21:52
zanebso we can probably defer21:52
zanebI don't think we'd consider it a blocker21:53
ttxdolphm/zaneb: ok. If it comes back, make sure you sync first21:53
dolphmthe keystone bp was started in https://review.openstack.org/#/c/57481/21:53
mordredo/21:53
*** jdob has quit IRC21:53
ttxdolphm: same thing ?21:53
*** tshirtma1 is now known as tshirtman21:54
dolphmttx: yes; it's proposing the API mechanism for this feature21:54
*** jhenner has joined #openstack-meeting21:54
dolphmi'll follow up with Matthieu Huin as well21:54
dolphm(for some reason i thought the keystone bp was assigned to shardy; it's not assigned at all)21:55
ttxzaneb: move it off i3 for the moment, and maybe sync with shardy when you have a chance21:55
zanebttx: ok, will do21:55
ttxAny other inter-project blocked work that this meeting could help unblock ?21:55
dolphmzaneb: actually it looks like this has merged against a wishlist bug: https://review.openstack.org/#/c/57481/21:55
*** sdake has quit IRC21:55
*** doron_afk has quit IRC21:55
*** doron_afk has joined #openstack-meeting21:56
zanebdolphm: ok, I just bumped the bp to next and I will add it to the project meeting agenda for tomorrow21:56
*** woodster1 has joined #openstack-meeting21:56
ttxack, please unconfuse soon thx21:56
ttx#topic Incubated projects21:56
markmcclainttx: just wanted to update that the nova team has patch in the merge gate which will unblock neutron21:56
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:56
SergeyLukjanovo/21:56
dolphmzaneb: i've marked the keystone bp as Implemented, even though it's sort of obsolete!21:57
ttxmarkmcclain: great news !21:57
zaneblol, OK :D21:57
dhellmannmarkmcclain: \o/21:57
SergeyLukjanovsavanna is going to setup async gating - https://review.openstack.org/#/c/68066/21:57
*** sushils has quit IRC21:57
*** tedross has joined #openstack-meeting21:57
SergeyLukjanovttx, https://launchpad.net/savanna/+milestone/icehouse-321:58
ttxlooks good to me21:58
devanandao/21:58
* ttx busily converts "unknown" to "not started"21:58
SergeyLukjanovttx, will do21:59
devanandaas of a few hours ago, our gate is finally unblocked :-D21:59
ttxdone21:59
SergeyLukjanovttx, thx21:59
ttxdevananda: cool21:59
devanandaI've also proposed adding some more -core so we can increase the rate of merges21:59
*** jprovazn has quit IRC21:59
devanandai3 is very aggressive for us ... hopefully that will help22:00
ttx#topic Open discussion22:00
*** openstack changes topic to "Open discussion (Meeting topic: project)"22:00
ttxanything else in that last minute ?22:00
*** woodster1 has quit IRC22:00
SergeyLukjanovnot from my side22:00
ttxok then22:01
*** patelna has joined #openstack-meeting22:01
ttx#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
openstackMeeting ended Tue Feb  4 22:01:04 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-02-04-21.04.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-02-04-21.04.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-02-04-21.04.log.html22:01
*** masayukig has joined #openstack-meeting22:01
*** lblanchard has quit IRC22:01
*** markmc has quit IRC22:01
*** redrobot has left #openstack-meeting22:02
*** markpeek has joined #openstack-meeting22:02
*** doron_afk has quit IRC22:02
*** MaxV has quit IRC22:03
*** neelashah has joined #openstack-meeting22:03
*** MaxV has joined #openstack-meeting22:03
*** doron_afk has joined #openstack-meeting22:03
*** david-lyle has quit IRC22:04
*** vgnbkr has quit IRC22:05
*** jasondotstar has quit IRC22:05
*** sushils has joined #openstack-meeting22:05
*** masayukig has quit IRC22:05
*** pdmars has quit IRC22:06
*** elo1 has joined #openstack-meeting22:07
*** neelashah has quit IRC22:07
*** doron_afk has quit IRC22:08
*** doron_afk has joined #openstack-meeting22:08
*** jcooley_ has joined #openstack-meeting22:10
*** elo1 has quit IRC22:11
*** SumitNaiksatam_ has joined #openstack-meeting22:12
*** mounirb has left #openstack-meeting22:12
*** lisaclark1 has quit IRC22:13
*** SumitNaiksatam has quit IRC22:13
*** SumitNaiksatam_ is now known as SumitNaiksatam22:13
*** pnavarro has quit IRC22:14
*** sdake has joined #openstack-meeting22:16
*** marekd is now known as marekd|away22:16
*** jcooley_ has quit IRC22:16
*** jcooley_ has joined #openstack-meeting22:17
*** markpeek has quit IRC22:19
*** doug_shelley66 has joined #openstack-meeting22:19
*** julienvey_ has joined #openstack-meeting22:21
*** tchaypo has left #openstack-meeting22:21
*** neelashah has joined #openstack-meeting22:21
*** Daisy has quit IRC22:23
*** mestery has quit IRC22:24
*** amcrn has joined #openstack-meeting22:25
*** markmcclain has quit IRC22:26
*** egallen has quit IRC22:27
*** slagle has joined #openstack-meeting22:28
*** gmurphy_ is now known as gmurphy22:30
*** IanGovett has joined #openstack-meeting22:31
*** tedross has quit IRC22:32
*** markmcclain has joined #openstack-meeting22:33
*** dims has quit IRC22:39
*** dkranz has quit IRC22:41
*** balajiiyer has left #openstack-meeting22:42
*** hub_cap has left #openstack-meeting22:43
*** eharney has quit IRC22:47
*** mdurnosvistov_ has quit IRC22:48
*** joesavak has quit IRC22:48
*** gokrokve has joined #openstack-meeting22:49
*** dims_ has joined #openstack-meeting22:55
*** weshay has quit IRC22:55
*** thuc has quit IRC22:55
*** thuc has joined #openstack-meeting22:56
*** markpeek has joined #openstack-meeting22:59
*** thuc has quit IRC23:00
*** topol has quit IRC23:01
*** harlowja is now known as harlowja_away23:01
*** burt1 has quit IRC23:04
*** AlanClark has quit IRC23:04
*** sacharya has quit IRC23:04
*** stevemar has quit IRC23:05
*** vkmc has quit IRC23:05
*** doron_afk has quit IRC23:05
*** IlyaE has quit IRC23:06
*** krotscheck_sick has quit IRC23:06
*** elo1 has joined #openstack-meeting23:08
*** branen_ has quit IRC23:08
*** jgrimm_ has quit IRC23:11
*** jhenner has quit IRC23:11
*** masayukig has joined #openstack-meeting23:11
*** prad_ has quit IRC23:12
*** Gordonz has joined #openstack-meeting23:13
*** Gordonz has quit IRC23:13
*** Gordonz has joined #openstack-meeting23:13
*** mdomsch has quit IRC23:13
*** harlowja_away is now known as harlowja23:13
*** dstanek has quit IRC23:14
*** jecarey has quit IRC23:14
*** masayukig has quit IRC23:15
*** dcramer_ has quit IRC23:16
*** mestery has joined #openstack-meeting23:17
*** mestery has quit IRC23:17
*** mestery has joined #openstack-meeting23:17
*** sarob has joined #openstack-meeting23:18
*** zehicle_at_dell has joined #openstack-meeting23:18
*** elo1 has quit IRC23:18
*** elo1 has joined #openstack-meeting23:19
*** neelashah has quit IRC23:20
*** kgriffs has left #openstack-meeting23:20
*** thuc_ has joined #openstack-meeting23:21
*** kevinconway has quit IRC23:21
*** MaxV has quit IRC23:23
*** thomasem has quit IRC23:24
*** markmcclain has quit IRC23:25
*** sushils has quit IRC23:26
*** sarob_ has joined #openstack-meeting23:27
*** rfolco has joined #openstack-meeting23:27
*** miqui has joined #openstack-meeting23:28
*** sarob has quit IRC23:28
*** sushils has joined #openstack-meeting23:28
*** dnavale has left #openstack-meeting23:30
*** tongli has quit IRC23:30
*** flaper87 is now known as flaper87|afk23:31
*** andreaf_ has joined #openstack-meeting23:33
*** atiwari has quit IRC23:35
*** rfolco has quit IRC23:36
*** andreaf has quit IRC23:36
*** yamahata has quit IRC23:38
*** thuc_ has quit IRC23:38
*** ArthurBerezin has joined #openstack-meeting23:39
*** yamahata has joined #openstack-meeting23:40
*** elo1 has quit IRC23:41
*** andreaf has joined #openstack-meeting23:42
*** bauzas has quit IRC23:42
*** baoli has quit IRC23:42
*** andreaf has quit IRC23:43
*** banix has quit IRC23:44
*** thuc has joined #openstack-meeting23:46
*** rossk has quit IRC23:47
*** atiwari has joined #openstack-meeting23:48
*** patelna has quit IRC23:51
*** thuc_ has joined #openstack-meeting23:53
*** andreaf_ has quit IRC23:53
*** MaxV has joined #openstack-meeting23:53
*** markmcclain has joined #openstack-meeting23:54
*** yamahata has quit IRC23:54
*** patelna has joined #openstack-meeting23:54
*** thuc has quit IRC23:56
*** branen has joined #openstack-meeting23:57
*** weshay has joined #openstack-meeting23:58
*** Leonr has quit IRC23:58

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