Tuesday, 2015-06-16

*** aimon has quit IRC00:01
*** Alexandra_ has joined #openstack-meeting00:02
*** arvinchou_ has joined #openstack-meeting00:02
*** asettle has quit IRC00:02
*** haomaiwa_ has joined #openstack-meeting00:04
*** haomaiw__ has quit IRC00:04
*** dmacpher has joined #openstack-meeting00:05
*** Alexandra_ is now known as asettle00:05
*** vnod has quit IRC00:07
*** Leonr has quit IRC00:10
*** adahms has joined #openstack-meeting00:14
*** yamamoto has quit IRC00:17
*** Sukhdev has quit IRC00:17
*** arvinchou_ has quit IRC00:18
*** stevemar has joined #openstack-meeting00:18
*** KunalGandhi has quit IRC00:20
*** Daisy has joined #openstack-meeting00:21
*** geoffarnold has quit IRC00:21
*** marrusl has joined #openstack-meeting00:23
*** haomaiwa_ has quit IRC00:23
*** david-lyle has quit IRC00:24
*** yingjun has joined #openstack-meeting00:25
*** tsekiyama has quit IRC00:27
*** asettle has quit IRC00:28
*** Swami has quit IRC00:30
*** dane_leblanc has quit IRC00:32
*** Daisy_ has joined #openstack-meeting00:32
*** dims has quit IRC00:33
*** Daisy has quit IRC00:34
*** Daisy_ is now known as Daisy00:34
*** otter768 has quit IRC00:35
*** padkrish has quit IRC00:36
*** padkrish has joined #openstack-meeting00:36
*** jckasper has joined #openstack-meeting00:37
*** ozstacker has quit IRC00:38
*** tomoe_ has joined #openstack-meeting00:38
*** zhhuabj has quit IRC00:39
*** zhhuabj has joined #openstack-meeting00:39
*** ozstacker has joined #openstack-meeting00:39
*** _amrith_ is now known as amrith00:39
*** fallenpegasus has quit IRC00:40
*** harshs has quit IRC00:40
*** padkrish has quit IRC00:41
*** adahms has quit IRC00:41
*** zhhuabj_ has joined #openstack-meeting00:43
*** zhhuabj has quit IRC00:43
*** tiswanso has quit IRC00:44
*** dims has joined #openstack-meeting00:46
ozstacker  xm00:48
*** tomoe__ has joined #openstack-meeting00:48
ozstacker x00:48
*** tomoe__ has quit IRC00:49
*** tomoe_ has quit IRC00:49
*** baoli has joined #openstack-meeting00:51
*** harshs has joined #openstack-meeting00:52
*** harshs has quit IRC00:53
*** oswa has joined #openstack-meeting00:54
*** fallenpegasus has joined #openstack-meeting00:55
*** oswa has quit IRC00:56
*** yamamoto has joined #openstack-meeting00:57
*** asettle has joined #openstack-meeting00:58
*** britthou_ has joined #openstack-meeting00:58
*** dguerri is now known as dguerri`00:59
*** Slower has quit IRC01:00
*** banix has joined #openstack-meeting01:01
*** britthouser has quit IRC01:01
*** haomaiwang has joined #openstack-meeting01:03
*** harshs has joined #openstack-meeting01:03
*** leeantho has quit IRC01:04
*** ozstacker has quit IRC01:05
*** ozstacker has joined #openstack-meeting01:06
*** padkrish has joined #openstack-meeting01:07
*** Slower has joined #openstack-meeting01:07
*** novas0x2a|lapto1 has quit IRC01:09
*** otter768 has joined #openstack-meeting01:12
*** geoffarnold has joined #openstack-meeting01:12
*** geoffarnold has quit IRC01:14
*** jwcroppe has quit IRC01:16
*** zhhuabj_ has quit IRC01:18
*** tobe has joined #openstack-meeting01:19
*** padkrish has quit IRC01:19
*** sigmavirus24 is now known as sigmavirus24_awa01:20
*** otter768 has quit IRC01:21
*** bobh has joined #openstack-meeting01:23
*** KunalGandhi has joined #openstack-meeting01:24
*** carl_baldwin has quit IRC01:27
*** tiswanso has joined #openstack-meeting01:30
*** ociuhandu has quit IRC01:31
*** KunalGan_ has joined #openstack-meeting01:31
*** KunalGandhi has quit IRC01:32
*** Longgeek has joined #openstack-meeting01:32
*** ociuhandu has joined #openstack-meeting01:33
*** gongysh has quit IRC01:34
*** ypraveen has joined #openstack-meeting01:36
*** xyang1 has quit IRC01:37
*** gyee_ has quit IRC01:40
*** amrith is now known as _amrith_01:41
*** fallenpegasus has quit IRC01:42
*** luiz___ has quit IRC01:43
*** ozstacker has quit IRC01:43
*** ozstacker has joined #openstack-meeting01:45
*** banix has quit IRC01:45
*** marrusl has quit IRC01:46
*** harshs has quit IRC01:47
*** dims has quit IRC01:50
*** eghobo has quit IRC01:50
*** Longgeek has quit IRC01:52
*** banix has joined #openstack-meeting01:56
*** hichihara has quit IRC01:58
*** arvinchou_ has joined #openstack-meeting02:00
*** hichihara has joined #openstack-meeting02:01
*** amotoki has joined #openstack-meeting02:04
*** asettle has quit IRC02:07
*** david-lyle has joined #openstack-meeting02:08
*** sankarshan_away is now known as sankarshan_02:09
*** yamada-h has joined #openstack-meeting02:10
*** kebray has joined #openstack-meeting02:10
*** bobh has quit IRC02:11
*** jimhaselmaier has joined #openstack-meeting02:11
*** nati_ueno has joined #openstack-meeting02:11
*** balajiiyer has joined #openstack-meeting02:14
*** yamada-h has quit IRC02:14
*** asettle has joined #openstack-meeting02:14
*** jimhaselmaier has quit IRC02:17
*** amotoki has quit IRC02:20
*** spzala has quit IRC02:22
*** Apoorva has quit IRC02:22
*** yingjun has quit IRC02:25
*** ddieterly has joined #openstack-meeting02:27
*** ypraveen has quit IRC02:29
*** yingjun has joined #openstack-meeting02:29
*** amotoki has joined #openstack-meeting02:31
*** bradjones has quit IRC02:35
*** epico has joined #openstack-meeting02:35
*** padkrish has joined #openstack-meeting02:35
*** padkrish has quit IRC02:35
*** unicell has quit IRC02:35
*** IlyaG has quit IRC02:35
*** bradjones has joined #openstack-meeting02:35
*** bradjones has quit IRC02:35
*** bradjones has joined #openstack-meeting02:35
*** padkrish has joined #openstack-meeting02:36
*** yamada-h has joined #openstack-meeting02:37
*** yamada-h has quit IRC02:37
*** dguerri` is now known as dguerri02:38
*** amotoki has quit IRC02:39
*** amotoki has joined #openstack-meeting02:39
*** baoli has quit IRC02:42
*** banix has quit IRC02:43
*** baoli has joined #openstack-meeting02:43
*** ddieterly has quit IRC02:43
*** kebray has quit IRC02:45
*** dpaterson has quit IRC02:45
*** dguerri is now known as dguerri`02:48
*** Longgeek has joined #openstack-meeting02:49
*** kebray has joined #openstack-meeting02:51
*** penick has joined #openstack-meeting02:53
*** bryan_att has quit IRC02:53
*** padkrish has quit IRC02:56
*** yamada-h has joined #openstack-meeting02:59
*** amotoki has quit IRC03:01
*** epico has quit IRC03:02
*** bobh has joined #openstack-meeting03:02
*** banix has joined #openstack-meeting03:05
*** epico has joined #openstack-meeting03:05
*** pballand has quit IRC03:06
*** stevemar has quit IRC03:06
*** KunalGan_ has quit IRC03:07
*** pballand has joined #openstack-meeting03:08
*** KunalGandhi has joined #openstack-meeting03:10
*** asettle has quit IRC03:11
*** asettle has joined #openstack-meeting03:12
*** asettle has quit IRC03:12
*** KunalGan_ has joined #openstack-meeting03:12
*** asettle has joined #openstack-meeting03:12
*** KunalGandhi has quit IRC03:15
*** claudiub has quit IRC03:15
*** ganeshna has joined #openstack-meeting03:17
*** Longgeek has quit IRC03:17
*** tobe has quit IRC03:20
*** asettle has quit IRC03:22
*** otter768 has joined #openstack-meeting03:22
*** tobe has joined #openstack-meeting03:23
*** amotoki has joined #openstack-meeting03:24
*** otter768 has quit IRC03:27
*** bobh has quit IRC03:28
*** reed has quit IRC03:31
*** banix has quit IRC03:31
*** mfisch has quit IRC03:32
*** marios has quit IRC03:32
*** sdake has quit IRC03:32
*** marios has joined #openstack-meeting03:32
*** reed has joined #openstack-meeting03:33
*** mfisch has joined #openstack-meeting03:36
*** zhhuabj has joined #openstack-meeting03:36
*** mfisch is now known as Guest6866003:36
*** penick has quit IRC03:37
*** asselin has joined #openstack-meeting03:38
*** unicell has joined #openstack-meeting03:40
*** coolsvap|afk is now known as coolsvap03:41
*** padkrish has joined #openstack-meeting03:42
*** mtanino has quit IRC03:43
*** fallenpegasus has joined #openstack-meeting03:44
*** baoli has quit IRC03:44
*** pballand has quit IRC03:45
*** dims has joined #openstack-meeting03:46
*** tomoe_ has joined #openstack-meeting03:46
*** nati_ueno has quit IRC03:46
*** nati_ueno has joined #openstack-meeting03:47
*** nati_ueno has quit IRC03:47
*** varora- has left #openstack-meeting03:48
*** yingjun has quit IRC03:50
*** dims has quit IRC03:51
*** padkrish has quit IRC03:52
*** padkrish has joined #openstack-meeting03:53
*** ivar-lazzaro has quit IRC03:54
*** ivar-lazzaro has joined #openstack-meeting03:55
*** redrobot has quit IRC03:55
*** padkrish has quit IRC03:57
*** ddieterly has joined #openstack-meeting03:58
*** ivar-lazzaro has quit IRC03:59
*** yamada-h has quit IRC04:01
*** asettle has joined #openstack-meeting04:02
*** jwcroppe has joined #openstack-meeting04:02
*** ddieterly has quit IRC04:03
*** eghobo has joined #openstack-meeting04:04
*** yamada-h has joined #openstack-meeting04:04
*** ganeshna has quit IRC04:08
*** unicell has quit IRC04:08
*** padkrish has joined #openstack-meeting04:09
*** padkrish has quit IRC04:09
*** padkrish has joined #openstack-meeting04:10
*** ayoung has quit IRC04:12
*** unicell has joined #openstack-meeting04:13
*** Alexandra_ has joined #openstack-meeting04:13
*** ganeshna has joined #openstack-meeting04:13
*** asettle has quit IRC04:13
*** radek_ has joined #openstack-meeting04:14
*** Alexandra_ has quit IRC04:14
*** asettle has joined #openstack-meeting04:14
*** Longgeek has joined #openstack-meeting04:14
*** Daisy has quit IRC04:15
*** radek__ has quit IRC04:15
*** Daisy has joined #openstack-meeting04:15
*** sdake has joined #openstack-meeting04:17
*** tomoe_ has quit IRC04:17
*** tiswanso has quit IRC04:19
*** aranjan has joined #openstack-meeting04:20
*** adiantum has quit IRC04:21
*** belmoreira has joined #openstack-meeting04:26
*** lpeer_ has quit IRC04:27
*** achanda has joined #openstack-meeting04:29
*** rossella_s has quit IRC04:30
*** rossella_s has joined #openstack-meeting04:31
*** Sukhdev has joined #openstack-meeting04:31
*** belmoreira has quit IRC04:31
*** tomoe_ has joined #openstack-meeting04:32
*** irenab has quit IRC04:32
*** ildikov has quit IRC04:33
*** yfried_ has quit IRC04:34
*** ypraveen has joined #openstack-meeting04:35
*** dmacpher has quit IRC04:37
*** nati_ueno has joined #openstack-meeting04:39
*** Longgeek has quit IRC04:41
*** asettle has quit IRC04:46
*** tobe has quit IRC04:47
*** asettle has joined #openstack-meeting04:49
*** padkrish has quit IRC04:49
*** mrmartin has joined #openstack-meeting04:50
*** padkrish has joined #openstack-meeting04:50
*** comay has quit IRC04:50
*** ParsectiX_ has joined #openstack-meeting04:51
*** SridharG has joined #openstack-meeting04:55
*** amotoki has quit IRC04:59
*** varora- has joined #openstack-meeting04:59
*** lpeer_ has joined #openstack-meeting05:02
*** ParsectiX_ has quit IRC05:04
*** yamada-h has quit IRC05:05
*** arnaud___ has joined #openstack-meeting05:06
*** balajiiyer has quit IRC05:06
*** yamada-h has joined #openstack-meeting05:06
*** tobe has joined #openstack-meeting05:07
*** ijw has joined #openstack-meeting05:08
*** dulek has joined #openstack-meeting05:11
*** yamada-h has quit IRC05:12
*** asselin has quit IRC05:13
*** asselin has joined #openstack-meeting05:15
*** PrashantS has joined #openstack-meeting05:18
*** KunalGan_ has quit IRC05:20
*** zz_jgrimm is now known as jgrimm05:20
*** achanda has quit IRC05:20
*** padkrish has quit IRC05:20
*** amotoki has joined #openstack-meeting05:21
*** irenab has joined #openstack-meeting05:21
*** BharatK has joined #openstack-meeting05:21
*** otter768 has joined #openstack-meeting05:23
*** lazy_prince has joined #openstack-meeting05:24
*** BharatK has quit IRC05:26
*** PrashantS has quit IRC05:27
*** PrashantS has joined #openstack-meeting05:27
*** arnaud___ has quit IRC05:28
*** otter768 has quit IRC05:28
*** yamahata has joined #openstack-meeting05:28
*** mrmartin has quit IRC05:29
*** stevemar has joined #openstack-meeting05:30
*** PrashantS has quit IRC05:32
*** Murali has joined #openstack-meeting05:33
*** arosen has quit IRC05:35
*** aswadr has joined #openstack-meeting05:35
*** ildikov has joined #openstack-meeting05:35
*** ozstacker has quit IRC05:37
*** tobe has quit IRC05:37
*** armax has quit IRC05:38
*** Longgeek has joined #openstack-meeting05:38
*** BharatK has joined #openstack-meeting05:38
*** ganeshna has quit IRC05:41
*** yamada-h has joined #openstack-meeting05:44
*** ganeshna has joined #openstack-meeting05:45
*** doron_afk has joined #openstack-meeting05:45
*** Longgeek has quit IRC05:47
*** Longgeek has joined #openstack-meeting05:48
*** oomichi has joined #openstack-meeting05:49
*** asrangne has joined #openstack-meeting05:50
*** aswadr has quit IRC05:51
*** ypraveen has quit IRC05:51
*** yamada-h has quit IRC05:51
*** achanda has joined #openstack-meeting05:54
*** belmoreira has joined #openstack-meeting05:55
*** asettle has quit IRC05:56
*** jtomasek has joined #openstack-meeting05:57
*** asselin has quit IRC06:02
*** tobe has joined #openstack-meeting06:02
*** yfried_ has joined #openstack-meeting06:04
*** asrangne has quit IRC06:04
*** yingjun has joined #openstack-meeting06:05
*** shadower has quit IRC06:06
*** ganeshna_ has joined #openstack-meeting06:06
*** shadower has joined #openstack-meeting06:06
*** mrunge has joined #openstack-meeting06:06
*** numan has joined #openstack-meeting06:07
*** tomoe_ has quit IRC06:07
*** mrmartin has joined #openstack-meeting06:07
*** yfried_ has quit IRC06:09
*** ganeshna has quit IRC06:09
*** KunalGan_ has joined #openstack-meeting06:10
*** numan has quit IRC06:12
*** yingjun has quit IRC06:14
*** sdake has quit IRC06:14
*** nadya has joined #openstack-meeting06:17
*** fawadkhaliq has joined #openstack-meeting06:17
*** hichihara has quit IRC06:17
*** nadya is now known as Guest439106:17
*** Guest4391 is now known as _nadya_06:17
*** numan has joined #openstack-meeting06:19
*** ganeshna_ has quit IRC06:21
*** achanda_ has joined #openstack-meeting06:21
*** achanda has quit IRC06:22
*** unicell has quit IRC06:24
*** KunalGan_ has quit IRC06:24
*** ganeshna has joined #openstack-meeting06:25
*** eghobo has quit IRC06:25
*** unicell has joined #openstack-meeting06:26
*** mpaolino has joined #openstack-meeting06:27
*** yingjun has joined #openstack-meeting06:28
*** jwcroppe has quit IRC06:29
*** doude has joined #openstack-meeting06:29
*** jwcroppe has joined #openstack-meeting06:30
*** Sukhdev has quit IRC06:31
*** mrmartin has quit IRC06:34
*** Murali has quit IRC06:34
*** jwcroppe has quit IRC06:35
*** belmoreira has quit IRC06:36
*** yamada-h has joined #openstack-meeting06:40
*** aranjan has quit IRC06:40
*** dguerri` is now known as dguerri06:42
*** mpaolino has quit IRC06:43
*** salv-orlando has joined #openstack-meeting06:44
*** yamada-h has quit IRC06:44
*** mpaolino has joined #openstack-meeting06:45
*** salv-orl_ has joined #openstack-meeting06:46
*** fallenpegasus has quit IRC06:48
*** salv-orlando has quit IRC06:49
*** dguerri is now known as dguerri`06:50
*** SridharG has left #openstack-meeting06:55
*** numan has quit IRC06:55
*** mrmartin has joined #openstack-meeting06:56
*** henrynash has joined #openstack-meeting06:56
*** kebray has quit IRC06:57
*** matrohon has joined #openstack-meeting07:01
*** fawadkhaliq has quit IRC07:05
*** yingjun has quit IRC07:07
*** yingjun has joined #openstack-meeting07:07
*** greghaynes has quit IRC07:08
*** _nadya_ has quit IRC07:10
*** greghaynes has joined #openstack-meeting07:11
*** ijw has quit IRC07:12
*** mrmartin has quit IRC07:13
*** phil_ has joined #openstack-meeting07:16
*** JRobinson__ has quit IRC07:16
*** tomoe_ has joined #openstack-meeting07:22
*** neeti has joined #openstack-meeting07:22
*** achanda_ has quit IRC07:22
*** tomoe_ has quit IRC07:24
*** otter768 has joined #openstack-meeting07:24
*** Fdot has joined #openstack-meeting07:27
*** otter768 has quit IRC07:28
*** mpaolino has quit IRC07:29
*** mpaolino has joined #openstack-meeting07:30
*** bradjones has quit IRC07:30
*** mpaolino has quit IRC07:33
*** mpaolino has joined #openstack-meeting07:33
*** _nadya_ has joined #openstack-meeting07:34
*** unicell has quit IRC07:35
*** bradjones has joined #openstack-meeting07:36
*** bradjones has quit IRC07:36
*** bradjones has joined #openstack-meeting07:36
*** adiantum has joined #openstack-meeting07:36
*** mpaolino has quit IRC07:36
*** mpaolino has joined #openstack-meeting07:36
*** ganeshna has quit IRC07:37
*** zz_ttrifonov is now known as ttrifonov07:39
*** haomaiwang has quit IRC07:39
*** mpaolino has quit IRC07:40
*** haomaiwang has joined #openstack-meeting07:40
*** mpaolino has joined #openstack-meeting07:40
*** ygbo has joined #openstack-meeting07:40
*** tobe has quit IRC07:40
*** fzdarsky has joined #openstack-meeting07:41
*** pnavarro has joined #openstack-meeting07:41
*** jlanoux has joined #openstack-meeting07:43
*** hashar has joined #openstack-meeting07:45
*** tobe has joined #openstack-meeting07:47
*** Zhongjun has joined #openstack-meeting07:47
*** nati_ueno has quit IRC07:49
*** aranjan has joined #openstack-meeting07:49
*** nati_ueno has joined #openstack-meeting07:49
*** devvesa has joined #openstack-meeting07:50
*** KunalGandhi has joined #openstack-meeting07:52
*** yamada-h has joined #openstack-meeting07:54
*** yamada-h has quit IRC07:54
*** belmoreira has joined #openstack-meeting07:54
*** nati_ueno has quit IRC07:54
*** mpaolino has quit IRC07:55
*** mpaolino has joined #openstack-meeting07:55
*** mpaolino has quit IRC07:55
*** mpaolino has joined #openstack-meeting07:56
*** nati_ueno has joined #openstack-meeting07:57
*** jcoufal has joined #openstack-meeting08:00
*** isviridov_away is now known as isviridov08:00
anteaya#startmeeting third-party08:02
openstackMeeting started Tue Jun 16 08:02:41 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:02
*** openstack changes topic to " (Meeting topic: third-party)"08:02
openstackThe meeting name has been set to 'third_party'08:02
*** safchain has joined #openstack-meeting08:03
anteayaif you are here for the third party meeting raise your hand08:03
anteayasay hello08:03
*** aranjan has quit IRC08:03
eantyshevhello!08:03
anteayahello eantyshev08:03
anteayahow are you?08:04
eantyshevanteaya: Fine, got a couple questions08:04
anteayaeantyshev: go ahead08:04
*** tobe has quit IRC08:06
anteayaeantyshev: did you want to post your questions?08:06
eantyshevcurrent regex for 'recheck' triggers some unrelated CIs, for example https://review.openstack.org/#/c/190273/ patchset 908:06
*** mpaolino has quit IRC08:06
*** mpaolino has joined #openstack-meeting08:07
*** ganeshna has joined #openstack-meeting08:07
anteayayes08:08
eantyshevIs it acceptable to narrow the scope of CI to not react to those?08:08
anteayawe have no control over what syntax a ci uses for recheck08:08
anteayaaslo recheck should fire everything08:08
anteayabecause otherwise you could just recheck until you got the result you wanted08:09
anteayarather than having all the tests run you just pick08:09
anteayarecheck a08:09
anteayarecheck a08:09
anteayarecheck a08:09
anteayauntil a passes and then08:09
anteayarecheck b08:09
anteayarecheck b08:09
*** yassine has joined #openstack-meeting08:09
anteayauntil you get the result you wanted08:09
lennybHi. If recheck fires everything why do we need regex with a proper third party name there ?08:09
anteayathis allows patches with race conditions into master08:09
eantyshevbut 'recheck a' triggers Jenkins jobs too08:10
anteayawe never asked for a regex with a third party name08:10
anteayathat is just what ci operators did08:10
anteayayes recheck fires jenkins jobs08:10
*** derekh has joined #openstack-meeting08:10
lennybI see, so basically I can use another keyword to trigger my CI only.08:11
anteayaif that is your choice08:11
anteayainfra has no enforcement of any recheck syntax08:11
eantyshevok, so it's acceptable for our CI to react to bare 'recheck' and 'recheck Virtuozzo6 CI'?08:11
anteayaif that is your choice08:11
anteayainfra has no enforcement of any recheck syntax08:11
eantyshevwhat are the reasons to do recheck when it's not requested?08:12
eantyshevto show some stability?08:12
anteayarecheck means to run the tests08:13
anteayaif recheck is the comment running the tests is requested08:13
anteayadid you not understand my example above?08:13
anteayayou run the tests or you don't08:13
anteayayou don't get to chose which tests you run08:13
anteayayou run them all08:13
eantyshevI think I understand08:14
anteayaeantyshev: great08:14
anteayadid you have other questions today?08:15
eantyshevyes08:15
*** yamada-h has joined #openstack-meeting08:15
eantyshevmany third parties have different accounts for different projects08:15
anteayaokay08:16
*** tobe has joined #openstack-meeting08:16
*** yamada-h_ has joined #openstack-meeting08:16
eantyshevdoes that mean they run separate Zuul server for each?08:16
anteayano idea08:16
lennybwe are using 2 zuuls for 2 different CIs08:17
anteayaI would guess some do and some don't08:17
anteayawe have no way to track who does or does not08:17
anteayalennyb: thanks08:17
eantyshevlennyb: do you run them in one VM instance?08:17
lennybI dont think there is a technical problem to use 1 zuuls.08:17
lennybno we use 2 VMs08:17
*** ociuhandu has quit IRC08:18
lennybno. We use 2 VMs08:18
anteayaI don't think running more than one zuul on a single server is a good idea08:18
anteayabut I don't know for sure08:18
anteayabut it wouldn't be an initial choice I made08:18
anteayajust like nodepool needs its own network08:19
anteayaI would allocate zuul its own server08:19
eantyshevlennyb: do you have common jenkins, nodepool, etc. for these CIs?08:19
*** yamada-h has quit IRC08:19
lennybagreed,  you also use zuul user with it's environment and configuration, so I think it will be very tricky ( if possible ) to configure 2 zuuls on the same machine08:20
lennybwe have Jenkins, Zuul, JJB. no nodepool.08:20
*** lpeer_ has quit IRC08:21
eantyshevanteaya: we came to the point where we need to split one CI account in 208:21
*** nati_ueno has quit IRC08:21
lennybbtw, we do run NOvaCI and Neutron CI on the same Jenkins Master and zuul, but when our account was disabled due to Neutron CI, Nova CI was disabled as well.08:21
anteayaeantyshev: okay08:21
*** nati_ueno has joined #openstack-meeting08:22
eantyshevanteaya: just interested how others do08:23
anteayaeantyshev: of course08:23
anteayaeantyshev: any other questions?08:24
*** KunalGandhi has quit IRC08:25
anteayalennyb: how are you doing today?08:25
eantyshevanteaya: have to draw somebody's attention to https://review.openstack.org/18838308:25
anteayalennyb: was there anything you wanted to discuss?08:25
anteayaeantyshev: what do you want them to see on 188383?08:25
lennybanteaya: thanks. How are you? BTW, I met jogo yesterday. NO, I have nothing to discuss.08:26
*** yamada-h has joined #openstack-meeting08:26
anteayalennyb: wonderful08:26
*** nati_ueno has quit IRC08:26
anteayaeantyshev: you see there is a -1 on your patch08:26
anteayaeantyshev: jim would like you to provide a test08:27
eantyshevanteaya: I want it merged, since all prerequisites are met08:27
anteayaeantyshev: you have a -108:27
anteayaand a request for a test08:27
*** jogo has quit IRC08:27
anteayanot all prerequistes are met08:27
anteayajim wrote zuul08:27
eantyshevanteaya: https://review.openstack.org/19158808:27
eantyshevanteaya: it's in dependent review08:28
anteayadid you say so in the patch?08:28
anteayahave you talked to jim about having the test as a dependent patch?08:28
*** afazekas has joined #openstack-meeting08:29
*** yamahata has quit IRC08:29
anteayaso you are linking in the meeting so other operators are aware?08:29
anteayathat's fine08:29
anteaya#link https://review.openstack.org/#/c/188383/08:29
*** doron_afk has quit IRC08:29
anteaya#link https://review.openstack.org/#/c/191588/08:29
anteayathanks for doing thts work08:29
eantyshevanteaya: hope this will help, thanks!08:29
*** yamada-h_ has quit IRC08:30
anteayaeantyshev: I do suggest you find jeblair in infra during north american daylight hours to discuss your approach with him08:30
*** rossella_s has quit IRC08:30
anteayaas he may want the test in the same patch as the code08:30
*** rossella_s has joined #openstack-meeting08:30
eantyshevanteaya: I will discuss it with him08:32
*** nati_ueno has joined #openstack-meeting08:32
anteayaeantyshev: great08:32
anteayaanything else for this meeting?08:32
lennybno.08:34
eantyshevno08:34
anteayadoes anyone else have any items for this meeting?08:34
anteayaokay great08:34
anteayawell I won't keep you if we are finshed our discussion08:35
anteayathanks for the chat08:35
anteaya:)08:35
lennybthanks. buy.08:35
eantyshevthanks!08:35
anteayaI appreciate your attendance and participation08:35
lennybbye :)08:35
anteayasee you next week08:35
anteaya#endmeeting08:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:35
openstackMeeting ended Tue Jun 16 08:35:34 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-06-16-08.02.html08:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-06-16-08.02.txt08:35
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-06-16-08.02.log.html08:35
*** jyuso1 has joined #openstack-meeting08:35
*** eantyshev has left #openstack-meeting08:35
*** jyuso1 has left #openstack-meeting08:36
*** henrynash has quit IRC08:38
*** henrynash_ has joined #openstack-meeting08:38
*** AzherKhan has joined #openstack-meeting08:39
*** jyuso1 has joined #openstack-meeting08:40
*** ganeshna has quit IRC08:41
*** _nadya_ has quit IRC08:42
*** ganeshna has joined #openstack-meeting08:43
*** rushiagr_away is now known as rushiagr08:44
*** andreykurilin has quit IRC08:45
*** aarefiev has quit IRC08:46
*** jyuso1 has quit IRC08:48
*** aarefiev has joined #openstack-meeting08:51
*** nati_ueno has quit IRC08:51
*** andreykurilin has joined #openstack-meeting08:51
*** yamahata has joined #openstack-meeting08:52
*** stevemar has quit IRC08:52
*** fawadkhaliq has joined #openstack-meeting08:52
*** Yanyanhu has joined #openstack-meeting08:54
*** yamada-h_ has joined #openstack-meeting08:54
*** _nadya_ has joined #openstack-meeting08:54
*** nati_ueno has joined #openstack-meeting08:54
*** park_ has quit IRC08:54
*** park_heijlong has joined #openstack-meeting08:55
*** yamada-h has quit IRC08:57
*** yamahata has quit IRC08:57
*** yamamoto has quit IRC08:58
*** yamamoto has joined #openstack-meeting08:58
*** yamada-h_ has quit IRC08:58
*** aranjan has joined #openstack-meeting08:59
*** yamada-h has joined #openstack-meeting08:59
*** ianychoi has joined #openstack-meeting09:00
*** ganeshna has quit IRC09:02
*** ganeshna has joined #openstack-meeting09:03
*** aranjan has quit IRC09:04
*** bill_az has quit IRC09:05
*** Fdot has quit IRC09:06
*** doron_afk has joined #openstack-meeting09:10
*** e0ne has joined #openstack-meeting09:12
*** pelix has joined #openstack-meeting09:13
*** dims has joined #openstack-meeting09:18
*** e0ne is now known as e0ne_09:21
*** Fdot has joined #openstack-meeting09:22
*** dims has quit IRC09:23
*** otter768 has joined #openstack-meeting09:25
*** e0ne_ has quit IRC09:25
*** e0ne has joined #openstack-meeting09:28
*** flip214 has quit IRC09:30
*** phil_ has quit IRC09:30
*** otter768 has quit IRC09:30
*** phil_ has joined #openstack-meeting09:31
*** flip214 has joined #openstack-meeting09:31
*** haomaiwang has quit IRC09:31
*** yingjun has quit IRC09:33
*** jdziukx has quit IRC09:39
*** henrynash_ has quit IRC09:40
*** henrynash has joined #openstack-meeting09:40
*** fzdarsky has quit IRC09:45
*** tobe has quit IRC09:46
*** fzdarsky has joined #openstack-meeting09:47
*** dguerri` is now known as dguerri09:48
*** nati_ueno has quit IRC09:49
*** achanda has joined #openstack-meeting09:50
*** yassine has quit IRC09:51
*** hashar has quit IRC09:54
*** tobe has joined #openstack-meeting09:56
*** Zhongjun has quit IRC09:58
*** jdziukx has joined #openstack-meeting09:59
*** aranjan has joined #openstack-meeting10:00
*** aranjan has quit IRC10:05
*** e0ne is now known as e0ne_10:06
*** e0ne_ has quit IRC10:12
*** tomoe_ has joined #openstack-meeting10:12
*** e0ne has joined #openstack-meeting10:17
*** asselin_ has quit IRC10:22
*** Longgeek_ has joined #openstack-meeting10:25
*** Daisy has quit IRC10:27
*** Longgeek has quit IRC10:28
*** haomaiwa_ has joined #openstack-meeting10:28
*** tomoe_ has quit IRC10:31
*** tianhuanqin has joined #openstack-meeting10:31
*** arvinchou_ has quit IRC10:32
*** arvinchou_ has joined #openstack-meeting10:32
*** Yanyanhu has quit IRC10:33
*** hichihara has joined #openstack-meeting10:33
*** epico has quit IRC10:36
*** claudiub has joined #openstack-meeting10:38
*** hashar has joined #openstack-meeting10:38
*** yamada-h has quit IRC10:39
*** adahms has joined #openstack-meeting10:41
*** arvinchou_ has quit IRC10:45
*** _amrith_ is now known as amrith10:46
*** AzherKhan has quit IRC10:46
*** tochi has quit IRC10:47
*** toscalix has joined #openstack-meeting10:49
*** tobe has quit IRC10:50
*** tobe has joined #openstack-meeting10:51
*** Guest75760 has joined #openstack-meeting10:51
*** henrynash has quit IRC10:53
*** henrynash has joined #openstack-meeting10:56
*** tianhuanqin has quit IRC10:56
*** tobe has quit IRC10:56
*** aranjan has joined #openstack-meeting11:01
*** ganeshna has quit IRC11:04
*** salv-orl_ has quit IRC11:09
*** yamada-h has joined #openstack-meeting11:10
*** ganeshna has joined #openstack-meeting11:11
*** aranjan has quit IRC11:12
*** ganeshna has quit IRC11:12
*** e0ne is now known as e0ne_11:12
*** yamada-h has quit IRC11:16
*** dims has joined #openstack-meeting11:20
*** devvesa has quit IRC11:21
*** tomoe_ has joined #openstack-meeting11:22
*** coolsvap is now known as coolsvap|afk11:23
*** e0ne_ has quit IRC11:23
*** dims has quit IRC11:25
*** coolsvap|afk is now known as coolsvap11:26
*** otter768 has joined #openstack-meeting11:26
*** _nadya_ has quit IRC11:28
*** dims has joined #openstack-meeting11:29
*** dprince has joined #openstack-meeting11:29
*** coolsvap is now known as coolsvap|afk11:30
*** coolsvap|afk is now known as coolsvap11:31
*** otter768 has quit IRC11:31
*** salv-orlando has joined #openstack-meeting11:32
*** MaxPC has joined #openstack-meeting11:33
*** amrith is now known as _amrith_11:33
*** jcoufal has quit IRC11:35
*** achanda has quit IRC11:37
*** e0ne has joined #openstack-meeting11:37
*** Longgeek_ has quit IRC11:40
*** Longgeek has joined #openstack-meeting11:40
*** yassine has joined #openstack-meeting11:40
*** yassine has quit IRC11:40
*** neeti has quit IRC11:41
*** salv-orlando has quit IRC11:43
*** yassine has joined #openstack-meeting11:43
*** baoli has joined #openstack-meeting11:45
*** henrynash_ has joined #openstack-meeting11:46
*** henrynash has quit IRC11:47
*** henrynash_ is now known as henrynash11:47
*** arvinchou_ has joined #openstack-meeting11:48
*** mrunge has quit IRC11:48
*** Guest75760 is now known as ZZelle_11:49
*** ZZelle_ is now known as ZZelle-backup11:50
*** marcusvrn has joined #openstack-meeting11:50
*** marcusvrn1 has joined #openstack-meeting11:51
*** coolsvap is now known as coolsvap|afk11:52
*** yassine has quit IRC11:53
*** yassine has joined #openstack-meeting11:53
*** _nadya_ has joined #openstack-meeting11:54
*** mrunge has joined #openstack-meeting11:54
*** marcusvrn has quit IRC11:55
*** banix has joined #openstack-meeting11:56
*** yamamoto has quit IRC11:57
*** banix has quit IRC11:58
*** BharatK has quit IRC11:58
*** ganeshna has joined #openstack-meeting12:02
*** ganeshna has quit IRC12:02
*** ganeshna has joined #openstack-meeting12:03
*** ganeshna has quit IRC12:03
*** kylek3h has quit IRC12:03
*** ganeshna has joined #openstack-meeting12:03
*** baoli has quit IRC12:04
*** dneary has joined #openstack-meeting12:06
*** aranjan has joined #openstack-meeting12:09
*** fawadkhaliq has quit IRC12:10
*** raildo has joined #openstack-meeting12:11
*** SridharG has joined #openstack-meeting12:12
*** aranjan has quit IRC12:13
*** hichihara has quit IRC12:14
*** salv-orlando has joined #openstack-meeting12:15
*** VW has joined #openstack-meeting12:16
*** _nadya__ has joined #openstack-meeting12:18
*** _nadya_ has quit IRC12:18
*** tianhuanqin has joined #openstack-meeting12:18
*** ddieterly has joined #openstack-meeting12:22
*** bknudson has quit IRC12:22
*** kylek3h has joined #openstack-meeting12:24
*** aysyanne has joined #openstack-meeting12:26
*** ganeshna has quit IRC12:27
*** ivasev has joined #openstack-meeting12:28
*** bobh has joined #openstack-meeting12:29
*** rossella_s has quit IRC12:30
*** MeganR has joined #openstack-meeting12:30
*** rossella_s has joined #openstack-meeting12:31
*** baoli has joined #openstack-meeting12:33
*** theanalyst has left #openstack-meeting12:38
*** alexpilotti has joined #openstack-meeting12:38
*** hichihara has joined #openstack-meeting12:39
*** sudipto has joined #openstack-meeting12:41
*** VW has quit IRC12:41
*** redrobot has joined #openstack-meeting12:42
*** redrobot is now known as Guest7499312:42
*** jimhaselmaier has joined #openstack-meeting12:42
*** Guest74993 is now known as el_robot_rojo12:43
*** el_robot_rojo is now known as redrobot12:44
*** scinawa has joined #openstack-meeting12:44
*** haiwei has joined #openstack-meeting12:45
*** henrynash has quit IRC12:47
*** henrynash has joined #openstack-meeting12:49
*** janonymous_ has joined #openstack-meeting12:49
*** ganeshna has joined #openstack-meeting12:49
*** ddieterly has quit IRC12:49
*** bobh has quit IRC12:50
*** bknudson has joined #openstack-meeting12:50
*** ddieterly has joined #openstack-meeting12:51
*** Qiming has joined #openstack-meeting12:51
*** jimhaselmaier has quit IRC12:52
*** jckasper has quit IRC12:55
*** nati_ueno has joined #openstack-meeting12:56
*** amotoki has quit IRC12:56
*** edleafe has quit IRC12:57
*** yamamoto has joined #openstack-meeting12:58
*** lkarm has joined #openstack-meeting12:59
*** edleafe has joined #openstack-meeting12:59
*** amuller has joined #openstack-meeting12:59
Qiming#startmeeting senlin13:00
openstackMeeting started Tue Jun 16 13:00:29 2015 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** jehb has quit IRC13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
Qiming#topic roll call13:00
*** openstack changes topic to "roll call (Meeting topic: senlin)"13:00
*** yamahata has joined #openstack-meeting13:01
lkarmo/13:01
janonymous_o/13:01
haiweihi13:01
janonymous_Jaivish Kothari13:01
Qimingdon't think a lot of us will show up, this is the first meeting for senlin anyway13:01
*** ddieterly has quit IRC13:02
*** yamamoto_ has joined #openstack-meeting13:02
Qiming#topic get to know each other13:02
*** openstack changes topic to "get to know each other (Meeting topic: senlin)"13:02
haiweiat least four :)13:02
*** fawadkhaliq has joined #openstack-meeting13:02
QimingI'm expecting everyone to say a few words about yourself13:03
*** fawadkhaliq is now known as Guest6951713:03
haiweiok, I am xuhaiwei from NEC, nice to meet you13:03
haiweiI am in Tokyo13:03
Qimingso people get to know your name, where you are located, and your expertise, etc13:03
janonymous_Hi i am Jaivish from NEC :) india13:04
*** MeganR has left #openstack-meeting13:04
lkarmHi, i'm Lisa from IBM in Austin, TX13:04
QimingQiming Teng, with IBM Research, in China13:04
*** mrunge has quit IRC13:04
*** tholtzen has joined #openstack-meeting13:05
*** VW has joined #openstack-meeting13:05
*** yamamoto has quit IRC13:05
haiweicurrently four of us?13:05
*** luiz___ has joined #openstack-meeting13:05
janonymous_I normally work in swift , keystone and ceilometer .13:06
*** doron_afk is now known as doron_13:06
Qiminganyone else?13:06
haiweijanonymous, you are in India office?13:06
Qimingcool, not a big team so far13:06
*** changbl has quit IRC13:07
*** toscalix has quit IRC13:07
*** Guest69517 has quit IRC13:07
Qiminglet's move on13:07
Qiming#topic project status report13:07
*** openstack changes topic to "project status report (Meeting topic: senlin)"13:07
*** merooney has joined #openstack-meeting13:07
QimingSenlin was started last December, positioned as a generic clustering service for OpenStack13:07
Qimingthe project is now located on stackforge, with both server side and client side code13:08
Qimingwe have presented the design in the Heat design summit, because we were deeply rooted from Heat13:08
*** tholtzen has left #openstack-meeting13:08
janonymous_haiwei : yes .13:08
Qimingthe top priority for the project for the first release (Liberty) would be making autoscaling work13:09
Qimingand hopefully, bridge the Heat support to autoscaling to Senlin13:09
*** afazekas has quit IRC13:09
haiweiQiming, so how far are we there?13:09
Qimingthere are a lot of work to do for us to achieve that goal13:09
*** aranjan has joined #openstack-meeting13:10
*** ayoung has joined #openstack-meeting13:10
Qimingto support autoscaling, we are developing a scaling policy spec and the supporting plugin13:10
Qiminghopefully, that will be done by Liberty-213:10
*** rushiagr is now known as rushiagr_away13:10
*** Daisy has joined #openstack-meeting13:11
janonymous_Yes i am ready to work hard . but i could only work after my office hours because it's my priority :) . will that be ok?13:11
QimingI have to say, it is not a trivial thing, considering that we may need to explore message queue service (zaqar) some time13:11
*** banix has joined #openstack-meeting13:11
Qimingsure13:11
Qimingany kinds of contributions are welcomed, sir13:11
janonymous_Thanks :)13:11
Qimingtime for you to pour questions on me13:12
haiweiwhat about the short time goal?13:12
haiweishort-term13:12
Qimingsupporting autoscaling is pretty short-term a goal13:13
janonymous_Sorry to say but i want to know about senlin , i have very little idea about it.13:13
Qimingjanonymous_, don't worry13:13
Qimingwe are working hard to add some documents for developers13:13
Qimingfor example: https://review.openstack.org/#/c/190447/13:14
Qimingyou can find us on the #senlin channel most of the time, just jump in and ask questions13:14
*** aranjan has quit IRC13:14
janonymous_Yes sure sir. is there a mailing list , group for serlin also ?13:15
haiweiQiming, what is not done to support auto-scaling13:15
Qiminghaiwei, the scaling policy is not done13:15
Qimingwe have some dependencies on python-openstacksdk project13:15
lkarmJust to understand where this is going, once senlin has the scaling policies implemented, the idea is to have something like OS::Senlin::Cluster OS::Senlin::Policy in a heat template to do autoscaling through heat? But then you can also do autoscaling without heat at all right?13:15
Qimingwe need to push some patches there first13:16
Qiminglkarm, right13:16
QimingIf you are using Heat for autoscaling, we don't want to break you13:17
*** erlon has joined #openstack-meeting13:17
Qiminghowever, Senlin has its own APIs and client, that means you can do autoscaling in other ways as well13:17
*** rushil has joined #openstack-meeting13:17
lkarmare you planning on implementing scaling policies in a similar way heat implemented them?13:18
*** jdandrea has left #openstack-meeting13:18
*** kylek3h has quit IRC13:18
Qiminglkarm, yes and no, from user's perspective, we hope we can support their existing autoscaling templates13:18
Qimingbut implementation perspective, there will be quite some differences13:19
*** marun has joined #openstack-meeting13:19
Qimingfor example, we don't want users to specify alarms, at least that is our current idea13:19
Qimingyou can check the senlin/examples/policies subdirectory to see how scaling policies will look like13:20
lkarmby that you mean no ceilometer dependencies required to do autoscaling?13:20
*** marun has quit IRC13:20
Qiminglkarm, the dependency may exist, but won't be hard-coded13:20
Qimingwe plan to provide users a choice, use ceilometer, monasca, or whatever 3rd-party monitoring tools13:21
*** julim has joined #openstack-meeting13:21
Qimingthere are plenty of details to be discussed13:22
QimingWhat I want to say in this meeting is that we need to make all of them a team decision13:22
*** ganeshna has quit IRC13:23
*** VW has quit IRC13:23
Qimingscaling policy is just one type of policies to be supported, for example13:23
*** cbader has joined #openstack-meeting13:23
Qimingwe want to support placement policies, deletion policies, update policies, etc13:24
Qimingthese policies are all plugins that you can instantiate and attach to a cluster13:24
Qimingwe believe they are orthogonal to each other13:24
*** yanyanhu has joined #openstack-meeting13:25
*** dneary has quit IRC13:25
*** ganeshna has joined #openstack-meeting13:25
Qimingwe also plan to submit a talk proposal for the coming Tokyo summit, give the community a deep dive and status update13:25
*** VW has joined #openstack-meeting13:25
Qimingthere have been some requests for Senlin to support clusters of containers, for instance13:25
yanyanhuhi, sorry for late, using my phone as hot spot13:25
lkarmdoes that mean magnum integration?13:26
Qimingin that case, Magnum will call senlin to create their pool of containers13:26
haiweiQiming, that is an important job I think13:26
*** otter768 has joined #openstack-meeting13:27
janonymous_Apart from senlin wiki ,can i get more info about it. because i m not from heat background so i would be needing some docs.13:27
*** jehb has joined #openstack-meeting13:27
Qimingyip, we have talked to Adrian and Steven Dake for this, the only concern they have today is that we are still on stackforge13:27
Qimingand they want no dependencies on stackforge projects13:27
*** kylek3h has joined #openstack-meeting13:27
lkarmso what is the plan for moving from stackforge13:28
Qimingjanonymous_, okay, we will work on more docs13:28
haiweiso it's better to push openstacksdk to be a openstack project13:28
yanyanhuor maybe we can start to implement some drivers directly based on other services client?13:28
QimingSenlin project itself, based on the community's criteria, can be proposed as a openstack project today13:28
haiweijanonymous_, maybe understanding heat autoscaling first is helpful13:29
*** Daisy_ has joined #openstack-meeting13:29
Qimingthe only reason we are not pushing that line is that we have dependencies on python-openstacksdk13:29
*** marrusl has joined #openstack-meeting13:29
Qimingand python-opentacksdk is today a stackforge project13:29
Qimingwe are actively helping that project as well13:29
*** Daisy has quit IRC13:29
*** Daisy_ is now known as Daisy13:30
haiweipython-openstacksdk can be a openstack project today, but they just don't want  to be?13:30
*** marrusl has quit IRC13:30
Qimingem, don't have an answer for that, haiwei13:30
*** marrusl has joined #openstack-meeting13:30
QimingSeems to me, though, the SDK project wants their API design stabilized before proposing13:31
*** john-davidge has joined #openstack-meeting13:31
Qimingthat makes sense to me13:31
*** barrett has joined #openstack-meeting13:31
Qimingand ... it will just be a issue of time13:31
*** otter768 has quit IRC13:31
haiweihow long it will take ?13:31
*** sdake has joined #openstack-meeting13:32
Qimingyanyanhu, if we introduce dependencies on python-***client into Senlin, we are still eventually throwing them away13:32
janonymous_and what can we do for that13:32
Qiminghaiwei, not sure how long it will take13:32
*** sdake has quit IRC13:32
yanyanhuQiming, that's true, openstack-sdk should be the choice13:32
Qimingmy personal opinin is focus on Senlin feature development, stability improvement13:33
haiweiwhat about setting a deadline for that13:33
*** fanyaohong has joined #openstack-meeting13:33
*** VW has quit IRC13:33
Qimingthe migration to openstack is just one of the many channels to get this service mature and widely used13:33
*** sdake has joined #openstack-meeting13:33
*** doron_ is now known as doron_afk13:34
Qiminghaiwei, good point, we need to sync with SDK team on a timeline13:34
*** scinawa has quit IRC13:34
Qiming#action Qiming to sync with SDK team for timeline13:34
*** singlethink has joined #openstack-meeting13:34
yanyanhuactually we still have several import features need to implement including customized action, complicated scaling policy13:34
*** amoturi has joined #openstack-meeting13:34
Qimingyanyanhu, +113:35
*** amitgandhinz has joined #openstack-meeting13:35
Qiminglet's move on13:35
Qiming#topic low-hanging fruits for new contributors13:35
*** openstack changes topic to "low-hanging fruits for new contributors (Meeting topic: senlin)"13:35
janonymous_:)13:36
QimingMany of us are new contributors to Senlin, or new developers for OpenStack13:36
*** ganeshna has quit IRC13:36
Qimingit will be a journey, but it won't be very long one13:36
*** Ajmiller has joined #openstack-meeting13:36
QimingWe are currently filing some bugs for your reference13:37
Qiminghttps://bugs.launchpad.net/senlin/13:37
*** bobh has joined #openstack-meeting13:38
janonymous_I have  question.. What about core contributors of senlin..13:38
QimingSome bugs are really easy to fix, but they will help you understand the architecture of Senlin, the development process for fixing bugs, propose patches etc.13:38
Qimingjanonymous_, currently we have only two cores, yanyanhu and me13:38
*** idegtiarov has joined #openstack-meeting13:38
QimingI believe we will need more soon, pretty soon13:38
haiweiQiming, currently I am doing this kind of bug fix13:39
janonymous_Yes , i would be one .. i hope :)13:39
Qimingthanks, haiwei, keep the good work13:39
Qimingjanonymous_, you will, if you want13:39
yanyanhuhope you guys can get familiar with the project soon : )13:39
janonymous_Yes.13:40
Qimingsome low hanging fruits, out of the bug list: Bug #1465565, Bug #1465211, Bug #1465509, Bug #1465518, Bug #146562013:40
openstackbug 1465565 in senlin "Policy attach should use policy defaults if not specified" [High,Triaged] https://launchpad.net/bugs/146556513:40
openstackbug 1465211 in senlin "profile type matching should be checked earlier" [Medium,Triaged] https://launchpad.net/bugs/146521113:40
openstackbug 1465509 in senlin "Policy attach API should perform parameter validations" [Medium,Triaged] https://launchpad.net/bugs/146550913:40
openstackbug 1465518 in senlin "Policy detach action API should do some early validation" [Medium,Triaged] https://launchpad.net/bugs/146551813:40
openstackbug 1465620 in senlin "Policy update API is not checking the JSON body" [Medium,Triaged] https://launchpad.net/bugs/146562013:40
*** prazumovsky has joined #openstack-meeting13:40
*** idegtiarov has left #openstack-meeting13:40
Qimingjust some examples13:40
*** yingjun has joined #openstack-meeting13:40
*** Ajmiller has quit IRC13:41
*** dane_leblanc has joined #openstack-meeting13:41
yanyanhuhi, Qiming, maybe completing exception translation is also one?13:41
Qimingbtw, we have two files maintained for short-term and long-term jobs13:41
Qimingyanyanhu, that sounds more like a TODO item, not a bug13:41
yanyanhuyes13:41
Qiminghttp://git.openstack.org/cgit/stackforge/senlin/tree/TODO.rst13:41
*** achanda has joined #openstack-meeting13:42
Qimingwe maintain a TODO file in the code repo, listing things we need to do13:42
Qimingitems in the TODO.rst file doesn't require a design discussion13:42
*** yingjun_ has joined #openstack-meeting13:42
Qimingif you know how to get it done, claim it by signing your name after that item, do it13:43
Qimingremove it when it is finished13:43
Qiminganother file: http://git.openstack.org/cgit/stackforge/senlin/tree/FEATURES.rst13:43
*** ddieterly has joined #openstack-meeting13:43
Qimingthis is a list of feature request we collected, most of them need some discussions among the team before coding13:44
Qimingfeel free to start a thread on any of them13:44
Qimingif needed, we may create a senlin-specs project for reviewing things like these13:45
Qimingquestions, comments, suggestions?13:45
*** eharney has joined #openstack-meeting13:45
*** yingjun has quit IRC13:45
janonymous_that was helpful.13:46
*** merooney has quit IRC13:46
*** rushil has quit IRC13:46
*** banix has quit IRC13:46
Qimingthe FEATURES.rst, to some extent, give you a sense where we are heading, hopefully13:46
Qimingokay, let's move on13:47
Qiming#topic open discussions13:47
*** openstack changes topic to "open discussions (Meeting topic: senlin)"13:47
*** tomoe_ has quit IRC13:47
*** barrett1 has joined #openstack-meeting13:48
*** barrett has quit IRC13:48
yanyanhuhi, Qiming, do we need to arrange some phone calls to answer some questions which may need detailed explaination?13:48
Qimingduring the Vancouver summit, I met some guys from Alcatel-Lucent, they may join us some day13:49
*** ddieterly has quit IRC13:49
haiweigood news13:49
janonymous_Kindly add me on your mailing lists if possible. janonymous.codevulture@gmail.com13:49
Qimingphone calls? we can discuss that13:49
Qimingjanonymous_, all openstack/stackforge projects are supposed to use the official mailinglist for discussion13:50
haiweiphone calls means call by phone??:)13:50
*** rkukura has joined #openstack-meeting13:50
yanyanhuyes ;)13:50
*** fawadkhaliq has joined #openstack-meeting13:50
haiweipersonal phone call?13:50
Qimingwhen posting your message, be sure to tag your subject with '[Senlin]' so that people can filter it13:50
*** fawadkhaliq is now known as Guest9024213:51
yanyanhuhmm, not sure about the way13:51
*** jwcroppe has joined #openstack-meeting13:51
haiweiI will add your wechat :)13:51
yanyanhunice13:51
Qimingphone calls in general is not encouraged, if I'm understanding it correctly13:51
Qimingit is kind of private communication13:51
*** e0ne is now known as e0ne_13:51
yanyanhuyes, I mean something like call conference13:52
haiweii agree with you13:52
QimingI believe all discussions should be open to the public13:52
yanyanhuif we can find a way to let everybody join13:52
yanyanhuok, agree13:52
janonymous_+113:52
Qimingyep, stay awake on the #senlin channel, be an answer machine, :)13:52
*** armax has joined #openstack-meeting13:53
haiweiQiming, that's great13:53
*** rushil has joined #openstack-meeting13:53
*** timrc_ has quit IRC13:53
haiweiwhat about your back?:)13:53
Qimingnot good, recovering13:53
lkarmyep I think IRC is best way to commuincate and discuss13:53
Qimingyes, lkarm13:53
haiweiagree13:53
*** lazy_prince has quit IRC13:54
yanyanhuso let join the channel :)13:54
*** fawadkhaliq__ has joined #openstack-meeting13:54
*** e0ne_ is now known as e0ne13:54
Qimingeventually, when we become an openstack project, IRC chats will be logged, you can find whatever discussions you have missed13:54
*** Guest90242 has quit IRC13:54
*** timrc_ has joined #openstack-meeting13:54
lkarmah I was wondering why they weren't currently being logged13:54
*** neiljerram has joined #openstack-meeting13:55
*** lpeer_ has joined #openstack-meeting13:55
Qimingthat said, the best way to answer questions at the moment is to work on some documents, for users, for developers13:55
haiweistackforge project doesn't have the right?13:55
Qiminghaiwei, I don't think so, maybe I'm missing something13:55
Qiminglet the team know if you find a way to log the chats13:56
yanyanhuagree, Qiming, will try to complete the doc and wiki13:56
*** Sukhdev has joined #openstack-meeting13:56
haiweiwhat tool are you using? Qiming13:56
Qimingthanks, we then don't have to answer the same questions time and time again13:56
yanyanhuit's easy to miss some import topics for time difference13:56
*** jckasper has joined #openstack-meeting13:56
QimingI'm using HexChat13:56
Qimingright13:57
janonymous_whn is the next meeting..13:57
*** miyagishi_t has joined #openstack-meeting13:57
*** yingjun has joined #openstack-meeting13:57
Qimingso if you have something for discussion, you may want to post a note to the mailing list13:57
*** numan has joined #openstack-meeting13:57
Qimingjanonymous_, https://wiki.openstack.org/wiki/Meetings/SenlinAgenda13:57
haiweithe same time next week13:57
Qiming1300 UTC, every Tuesday13:57
janonymous_thank u13:58
Qimingtime is up13:58
Qimingthank you all for joining13:58
yanyanhuthanks, ttyl13:58
Qimingsee you, see your patches13:58
haiweisee you13:58
janonymous_:) o/13:58
Qimingdiscussions can continue on #senlin13:58
Qiming#endmeeting13:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:58
openstackMeeting ended Tue Jun 16 13:58:55 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-06-16-13.00.html13:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-06-16-13.00.txt13:58
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-06-16-13.00.log.html13:58
*** carl_baldwin has joined #openstack-meeting13:59
*** cbouch has joined #openstack-meeting13:59
armaxhello13:59
*** bryan_att has joined #openstack-meeting13:59
amullerheya13:59
ajo:) o/13:59
neiljerramhi there13:59
xgermano/13:59
fawadkhaliq__Hello!13:59
hichiharahi13:59
yamahatahi13:59
*** rrrobbb has joined #openstack-meeting13:59
carl_baldwinhi13:59
ZZelle-backupHi everyone13:59
salv-orlandoaloha13:59
SukhdevGood Morning13:59
numanhi14:00
armaxhello!14:00
armax#startmeeting networking14:00
openstackMeeting started Tue Jun 16 14:00:07 2015 UTC and is due to finish in 60 minutes.  The chair is armax. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
janonymous_hi14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
*** amotoki has joined #openstack-meeting14:00
miyagishi_thi14:00
*** Qiming has left #openstack-meeting14:00
*** mlavalle has joined #openstack-meeting14:00
*** yingjun_ has quit IRC14:00
armax#link https://wiki.openstack.org/wiki/Network/Meetings14:00
haleybhi14:00
john-davidgehi14:00
*** tholtzen has joined #openstack-meeting14:00
mlavallehi14:00
amotokihi14:00
*** jlibosva has joined #openstack-meeting14:00
rkukurahi14:00
*** jdurgin1 has joined #openstack-meeting14:00
HenryGo/14:00
armaxhi everyone!14:01
*** rbak has joined #openstack-meeting14:01
*** pc_m has joined #openstack-meeting14:01
*** merooney has joined #openstack-meeting14:01
*** lkarm has left #openstack-meeting14:01
*** jecarey has joined #openstack-meeting14:01
*** SridharG has left #openstack-meeting14:01
*** john_a_joyce has joined #openstack-meeting14:01
armaxlet’s dive into the meeting! we have a packed agenda14:01
*** ihrachyshka has joined #openstack-meeting14:01
ihrachyshkao/14:01
armax#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
sc68calo/14:02
armaxthere was a meeting on VLAN aware VMs yesterday14:02
*** Gerald_K has joined #openstack-meeting14:02
armaxdoes anyone who attended care to brief the ones who didn’t?14:03
Sukhdevarmax: etherpad says it is today14:03
amotoki6/16 1700UTC is the time.14:03
*** rbak has quit IRC14:03
armaxSukhdev: thanks, it looks like the agenda is wrong14:03
pc_mamotoki: Which channel?14:03
*** banix has joined #openstack-meeting14:04
armaxpc_m: In #openstack-meeting-4 at 1700UTC14:04
Sukhdevpc_m: meeting-414:04
pc_marmax: thanks14:04
*** janonymous_ has quit IRC14:04
xeko/14:04
armaxok, next….there’s still a number of spects and RFE’s in flight14:05
*** ajmiller has joined #openstack-meeting14:05
*** johnbelamaric has joined #openstack-meeting14:05
*** achanda has quit IRC14:05
*** rbak has joined #openstack-meeting14:05
*** thangp has joined #openstack-meeting14:05
armax#link https://review.openstack.org/#/q/status:open+project:openstack/neutron-specs,n,z14:05
armaxthe ones that do not make the cutover date of Liberty 114:05
markmcclaino/14:05
armaxwill be abandoned and need to be resubmitted as RFE bugs14:06
armaxas outlined here:14:06
Sukhdevdoes anyone know when is Liberty-1?14:06
armax#link https://github.com/openstack/neutron/blob/master/doc/source/policies/blueprints.rst#cutover-to-rfes-from-pure-specs14:06
*** oomichi_ has joined #openstack-meeting14:06
*** banix_ has joined #openstack-meeting14:06
armaxSukhdev: liberty-1 (Jun 23-25)14:06
armaxSukhdev: https://wiki.openstack.org/wiki/Liberty_Release_Schedule14:06
Sukhdevarmax: thanks14:06
*** cdub has joined #openstack-meeting14:06
ajomakes sense,14:06
armaxnext on the announcmement list is Feature branch setup for QoS14:07
armaxajo: care to spend a few words?14:07
ajoarmax: ok :)14:07
*** lzachery has joined #openstack-meeting14:08
ajoWe have started to work on the feature branch to develop the QoS API extension, agent functionality and anything related to that work.14:08
armaxit looks like mestery also added a job for the pecan branch14:08
armax#link https://review.openstack.org/#/c/190756/14:08
*** banix has quit IRC14:08
armaxajo: is there any intention of doing something along the same lines?14:08
ajowe have chosen also the neutron-qos topic to put together anything related to neutron-qos (like neutronclient work) so it's easy to see everything together14:08
ajoarmax, let me check14:08
*** henrynash_ has joined #openstack-meeting14:09
ajoarmax, yes, sc68cal is going to prepare an experimental work for the branch,14:09
armaxajo: yes, experimental is best IMO14:09
*** edwarnicke has joined #openstack-meeting14:09
ajook, will do that way.14:09
*** merooney has quit IRC14:10
ajorelated to the QoS branch, I've put a little devref that may deserve some review time: https://review.openstack.org/190635 (about a generic RPC callback)14:10
armaxI have made a comment on the pecan job, I think check is a bit an overkill…perhaps kevinbenton knows more about this job configuration?14:10
*** aranjan has joined #openstack-meeting14:10
ajowhich could be equally reused for security groups..14:10
armaxajo: yes, I am on it14:10
*** henrynash has quit IRC14:10
*** henrynash_ is now known as henrynash14:10
armaxajo: I was distracted by the pymysql switch14:11
ajoarmax, thanks14:11
ajoI'm going to put a new revision on 30 minutes14:11
ajoend_of_meeting+30m14:11
*** rromans has quit IRC14:11
armaxajo: ok14:11
armaxok, on to the next announcement14:11
armaxnext week there’s the Neutron Liberty mid-cycle14:12
armax#link https://etherpad.openstack.org/p/neutron-liberty-mid-cycle14:12
salv-orlandoarmax: my opinion on the pecan work is that it either works or not. cahnces of races are limited, so perhaps it can stay in the experimental queue14:12
*** dneary has joined #openstack-meeting14:12
armaxthere’s also one in Europe not long after that14:12
armaxJune 30 - July 2 in Raanana, Israel (Red Hat offices)14:12
armaxhttps://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint14:13
armax#link https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint14:13
armaxmainly focused on qos14:13
*** dneary has quit IRC14:13
armaxsalv-orlando: agreed14:13
armaxsalv-orlando: I made that comment on mestery’s patch14:13
ajoanybody wanting to late-join the IL one, ping me anytime14:13
*** yingjun has quit IRC14:13
*** dboik has joined #openstack-meeting14:13
*** yingjun has joined #openstack-meeting14:13
*** rromans has joined #openstack-meeting14:14
armaxok, moving to the next topic14:14
armaxunless there’s anyone who wants to add anything?14:14
Sukhdevarmax: I have an announcement14:14
armaxSukhdev: sure14:14
SukhdevI would like to direct team's attention to L2 GW work14:15
SukhdevThe wiki is here - https://wiki.openstack.org/wiki/Neutron/L2-GW14:15
*** merooney has joined #openstack-meeting14:15
*** aranjan has quit IRC14:15
SukhdevPlease come and join us and provide us with additional use cases that can be implemented14:15
*** tiswanso has joined #openstack-meeting14:15
armaxthanks Sukhdev14:16
SukhdevNext meeting is on 6/22 at 10am PT14:16
armaxanyone else?14:16
armax...14:16
armax#topic Bugs14:16
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:16
armaxI recall that enikanorov is no longer on the frontline for this14:16
*** sigmavirus24_awa is now known as sigmavirus2414:16
armaxthere are a couple of bugs that bit us last week14:17
armaxI got here https://bugs.launchpad.net/neutron/+bug/1359523 and https://bugs.launchpad.net/neutron/+bug/133537514:17
openstackLaunchpad bug 1359523 in neutron "Security group rules are erroneously applied to all ports having same ip addresses in different networks" [High,In progress] - Assigned to shihanzhang (shihanzhang)14:17
openstackLaunchpad bug 1335375 in neutron "ping still working after security group rule is created, updated, or deleted" [High,In progress] - Assigned to shihanzhang (shihanzhang)14:17
armaxdoes anyone have an update?14:17
*** yanyanhu has quit IRC14:18
* armax waits a tad longer14:18
*** haiwei has quit IRC14:18
salv-orlandoI think our rtef ctl pln ltn should14:18
armaxok14:18
ajoarmax, looking, I was tracking that work, but I think there's no update14:18
armaxsalv-orlando: care to explain the acronyms?14:18
armaxI only got LTN14:19
armax:)14:19
salv-orlandoarmax: kevinbenton14:19
HenryGI suspect he is asleep14:19
armaxsalv-orlando: oh14:19
armaxreference control plane Lieutanant14:19
armaxsalv-orlando: gee14:19
*** VanL has joined #openstack-meeting14:19
armaxsalv-orlando: it’s still 7am here, you know? ;)14:19
armaxok14:20
*** harshs has joined #openstack-meeting14:20
armaxI’ll bug him when he wakes up14:20
armaxlast week there was a change that startled us a bit14:20
markmcclainI thought salv was having a little kid help at the keyboard14:20
ajo#action ajo contact shihanzhang about the SG bugs #1335375 and #135952314:20
openstackbug 1359523 in neutron "Security group rules are erroneously applied to all ports having same ip addresses in different networks" [High,In progress] https://launchpad.net/bugs/1359523 - Assigned to shihanzhang (shihanzhang)14:20
openstackbug 1335375 in neutron "ping still working after security group rule is created, updated, or deleted" [High,In progress] https://launchpad.net/bugs/1335375 - Assigned to shihanzhang (shihanzhang)14:20
armaxmarkmcclain: lol14:20
ajolol :)14:20
armaxthanks ajo!14:20
ajoI will talk to him, adding a reminder here not to forget..14:20
armaxthis change https://review.openstack.org/#/c/184383/14:21
armaxcaused a bit of instability in the gate14:21
armaxand caused DB functional tests to stop working14:21
*** VanL has quit IRC14:21
armaxwhat you need to be aware of, is that the situation was quickly reverted by disabling the driver gloabally14:22
*** fawadkhaliq__ has quit IRC14:22
armaxwith https://review.openstack.org/#/c/191010/14:22
armaxbut that still kept the functional job broken14:22
armaxamuller: keep me honest here14:22
amulleryou're honest14:22
amullercarry on14:22
ZZelle-backup:)14:22
armaxZZelle-backup has a fix for it at https://review.openstack.org/#/c/190342/14:23
armaxas for the mysql driver14:23
armaxwe reverted the global switch here:14:23
armaxhttps://review.openstack.org/#/c/191113/14:23
armaxbut we selectively bring sanity back to the Tempest Neutron jobs by overriding the mysql driver14:24
*** mattgriffin has joined #openstack-meeting14:24
armaxI filed a bunch of patches that introduce an unstable neutron job14:24
armaxhttps://review.openstack.org/#/q/topic:neutron-unstable,n,z14:24
armaxwhere we can test Neutron with the newer driver, without too much of an havoc14:24
armaxthe failure rate trend is available here: http://goo.gl/YM7gUC14:24
armax#link http://goo.gl/YM7gUC14:24
armaxas usual kevinbenton beated us by filing https://review.openstack.org/#/c/191540/14:25
armaxbut I suspect that needs to bake a bit14:25
ajonice :)14:26
armaxanyhow, this ramble of mine is to inform you that we’re keeping an unstable job to triage some of the stuff that threw us off14:26
*** IanGovett has joined #openstack-meeting14:26
*** Daisy_ has joined #openstack-meeting14:26
armaxto test the new driver as well as the # of API workers that was reverted late in the Kilo cycle14:26
*** irenab has quit IRC14:26
*** bobmel has joined #openstack-meeting14:27
ajoIt's a good approach, so we can sort out those instabilities without affecting everyone else14:27
armaxonce we’re happy with the failure rate, we’ll go back to using pymysql driver (the one that allows us to get to Py3) and we’ll finally have multiple API workers in the gate14:27
armaxfor now, we’re a bit cautious14:27
armaxanything else14:27
armax?14:27
*** Daisy has quit IRC14:28
HenryGThanks armax for the update and for keeping on top of all this14:28
*** mtanino has joined #openstack-meeting14:28
*** henrynash has quit IRC14:28
armaxHenryG: sure thing14:29
armaxon if nothing else bugs us14:29
salv-orlandoWhat's the opinion of the DB lieutinant on the matter? henryg?14:29
armaxoh, salv-orlando bugs us14:29
* armax waits14:29
salv-orlandoI think the approach adopted in patch #191540 pretty much uses napalm all over the problem14:29
HenryGsalv-orlando: We see if kevinbenton's fix works for pymysql14:29
*** Daisy_ is now known as Daisy14:30
*** lazy_prince has joined #openstack-meeting14:30
armaxsalv-orlando: I agree14:30
salv-orlandoHenryG: napalm fixes everything ;)14:30
*** Guest68660 is now known as mfisch14:30
salv-orlandoHenryG: I think we'd need to seek help from zzzeeek14:30
armaxsalv-orlando: I think that kevinbenton’s rationale is that until we get rid of the lockmode for update we’re bound to these types of races14:30
salv-orlando(after all he wrote he was willing to assist)14:30
HenryGsalv-orlando: I have engaged him14:31
*** mfisch is now known as Guest8122614:31
salv-orlandoHenryG: awesome14:31
armaxsalv-orlando: and he made an interesting comparison with the nova code base where they use the retry decorator extensively14:31
armaxsalv-orlando: that doesn’t mean that the retry mechanism is a good thing, btw14:31
HenryGHe was surprised that we are getting deadlocks on insert14:32
salv-orlandoarmax: I agree at 50%. There are also cases where LOCK FOR UPDATE works fine but eventlet screws up. For those cases using the retry decorator is still far from optimal as the timeout of 50secs would still expire14:32
ajoouch14:32
salv-orlandoarmax: cool, I see you guys are up to date on all pro and cons of the decorator14:32
armaxsalv-orlando: agreed…that’s why I mentioned that review 191540 needs to bake a little more14:32
salv-orlandoI can go back in my graveyard14:32
armaxsalv-orlando: your expertise on the matter would be invaluable14:32
ihrachyshkasalv-orlando, we should not get those timeouts with the new driver14:32
armaxsalv-orlando: so please consider reviewing the patch if you haven’t already14:32
*** nati_ueno has quit IRC14:32
armaxsalv-orlando: RIP14:33
*** isviridov is now known as isviridov_away14:33
armax#topic Docs14:33
*** openstack changes topic to "Docs (Meeting topic: networking)"14:33
ajoihrachyshka, salv-orlando : definitely 50 sec timeouts on ops.. don't seem good14:33
salv-orlandoihrachyshka: indeed, that's what I was told too, but then looking at the problem with sdague and zzzeeek it seems they were there14:33
*** henrynash has joined #openstack-meeting14:33
*** ajiang has left #openstack-meeting14:33
ihrachyshkameh, ok14:33
armaxit looks like emagana is not around14:33
*** harshs has quit IRC14:33
salv-orlandoajo: that's the default mysql lock wait timeout, but it gets triggered by eventlet not being smart enough in switching threads14:33
salv-orlandoihrachyshka, armax, ajo, HenryG: we might need to stop wasting time about this issue now... the agenda is packed. We just need to keep eyes on that lock wait timeout are not present even if the job succeeds14:34
armaxsalv-orlando: agreed14:34
*** achanda has joined #openstack-meeting14:34
ajosalv-orlando: correct14:34
armaxanyhow, emagana is not here so we are left with14:34
armax#topic On Demand Agenda14:35
*** openstack changes topic to "On Demand Agenda (Meeting topic: networking)"14:35
armaxgot a few items here14:35
armaxnova-network compatibility tasks14:35
armax#link v14:35
armax#link https://etherpad.openstack.org/p/YVR-nova-network14:35
neiljerramI also have a thing, after yours14:35
armaxanyone care to update on tasks being tracked here?14:36
armaxI was looking at russellb’s devstack patches14:36
armaxI need to go back to those14:36
sc68calI'm working on the LB job, making some progress14:37
*** henrynash_ has joined #openstack-meeting14:37
mlavallearmax: I am working on priority number 4, dns14:37
armaxmlavalle: thanks14:37
*** ttrifonov is now known as zz_ttrifonov14:37
armaxmlavalle: how is it going?14:37
mlavallethe rfe is approved on the neutron side14:38
mlavalleI am also cleaning up a spec14:38
*** Guest81226 has quit IRC14:38
*** dt_os has joined #openstack-meeting14:38
mlavallethere is also a spec on the nova side that I am working with johnthetubaguy14:38
*** jlibosva1 has joined #openstack-meeting14:38
armaxmlavalle: great14:38
neiljerrammlavalle: Worth adding links to that etherpad?14:38
Sukhdevmlavalle: link?14:38
*** jwcroppe has quit IRC14:38
mlavalleand I am already coding the neutron side.14:38
mlavallenova: https://review.openstack.org/#/c/90150/14:39
*** jwcroppe has joined #openstack-meeting14:39
*** aswadr has joined #openstack-meeting14:39
mlavalleneutron: https://review.openstack.org/#/c/88623/14:39
*** henrynash has quit IRC14:39
*** henrynash_ is now known as henrynash14:39
mlavalleshould push WIP code tomorrow14:40
*** aswadr has quit IRC14:40
*** aswadr has joined #openstack-meeting14:40
armaxperhaps russellb is not around14:41
*** jlibosva has quit IRC14:41
*** Daisy_ has joined #openstack-meeting14:41
armaxthere are a bunch of patches in flight to ensure we test rolling upgrades continously14:41
*** doron_afk is now known as doron_14:42
armaxthey are captured on the etherpad…if there are eyes who are interested in looking at those, that’d be great14:42
*** carl_baldwin has quit IRC14:42
armaxDistributed SNAT with DVR is still unclaimed, is it not?14:42
*** Daisy has quit IRC14:42
amullercorrect14:43
*** Daisy_ is now known as Daisy14:43
miyagishi_tI'd like to implement Distributed SNAT in Liberty.14:43
*** jwcroppe has quit IRC14:43
armaxmiyagishi_t: please put your name next to the item on the etherpad14:43
armaxlike 9214:44
miyagishi_tarmax: okay14:44
armaxmiyagishi_t: have you started to look into this already?14:44
miyagishi_tcurrently under discussion in our team.14:45
*** obondarev has quit IRC14:45
miyagishi_tarmax: I'd like to submit blueprint as soon as possible.14:45
armaxmiyagishi_t: please sync up with kevinbenton and myself14:45
*** yingjun has quit IRC14:45
armaxmiyagishi_t: and we may be able to help you stay on the right track14:45
*** padkrish has joined #openstack-meeting14:46
*** ayoung has quit IRC14:46
*** obondarev has joined #openstack-meeting14:46
*** rrrobbb has quit IRC14:46
*** IlyaG has joined #openstack-meeting14:46
armaxmiyagishi_t: get yourself familiar with the new submission process for Liberty14:46
armax#link https://github.com/openstack/neutron/blob/master/doc/source/policies/blueprints.rst14:46
armaxmiyagishi_t: if you aren’t already14:46
*** padkrish has quit IRC14:47
armaxlast item I have on the nova-net laundry list is the ‘get me a network’ spec14:47
*** Daisy has quit IRC14:47
*** e0ne is now known as e0ne_14:47
*** e0ne_ is now known as e0ne14:47
*** padkrish has joined #openstack-meeting14:47
*** VW has joined #openstack-meeting14:47
armaxthis is still unclaimed, even though I was going to look into it as soon as I had the chance :)14:47
*** doron_ is now known as doron_afk14:48
*** ddieterly has joined #openstack-meeting14:48
armaxsc68cal: anything on your front?14:48
*** garthb_ has joined #openstack-meeting14:48
*** garthb has joined #openstack-meeting14:48
*** Daisy has joined #openstack-meeting14:48
sc68calarmax: I think last week there were volunteers to take over the spec to fill out more of the detail?14:48
*** dulek has quit IRC14:48
armaxsc68cal: ok, so you’d like someone to take over the spec as well?14:49
salv-orlandosc68cal: volunteers are the most volatile substance ever seen14:49
*** henrynash_ has joined #openstack-meeting14:49
sc68calarmax: I'll have to pull up the logs to remember the context - but there were volunteers14:49
haleybsc68cal: do you need me to add my comments?  I'm hoping I remembered things correctly14:49
salv-orlandoarmax: I can offer some part-time help14:49
*** oomichi_ has quit IRC14:49
*** stevemar has joined #openstack-meeting14:50
armaxfirst step would be to get the spec agreed on and merged14:50
sc68calhaleyb: I think your comments were correct, I think if you want to add them to the spec that'd be good14:50
amotokihaleyb: feel free to add your comments.14:50
armaxfor that we’d need a submitter that refresh the spec everytime a reviewer makes one, so for that we’d need reviewers too14:50
haleybarmax: i will update the spec and try to address all the comments14:51
*** _nadya__ has quit IRC14:51
ZZelle-backupi can14:51
armaxsc68cal: are you going to stop updating the spec yourself?14:51
ZZelle-backupoups too late14:51
haleybdarn, i knew i should have waited :)14:51
*** sudipto_ has joined #openstack-meeting14:51
armaxok, I gather that haleyb is going to take over the submission side of things?14:51
sc68calarmax: I think others can update the spec based on what they remembered14:51
*** sudipto has quit IRC14:52
armaxsc68cal: true, but if we don’t coordinate it becomes a bit messy14:52
*** henrynash has quit IRC14:52
*** henrynash_ is now known as henrynash14:52
ZZelle-backuphaleyb: mouarf14:52
armaxwe might as well have people fill in the specs with comments and a single person respin the patch14:52
armaxbut either way14:52
haleybi had the largest comment so i will do the next update and incorporate other comments14:52
sc68calarmax: ok - I'll coordinate with haleyb14:52
armaxsc68cal: thanks14:53
*** rushil has quit IRC14:53
armaxhaleyb: thanks14:53
*** jlibosva1 is now known as jlibosva14:53
armaxwe’ll leave the last item on the nova-net agenda for next week14:53
*** xingchao has joined #openstack-meeting14:53
armax#action armax reminds mestery to read the meeting log14:53
*** wojdev has joined #openstack-meeting14:53
armaxwe got a few minutes to spare, is there anything else someone would like to bring up to the team’s attention?14:54
neiljerramAnother Nova/Neutron thing, although not nova-net....14:54
neiljerramhttps://review.openstack.org/#/c/162468/14:54
*** ddieterl_ has joined #openstack-meeting14:54
*** henrynash has quit IRC14:54
pc_mCan folks kindly look at https://review.openstack.org/191944? Would like to get community feedback on direction here.14:54
neiljerramThis is about the future of VIF plugging...14:54
hichiharaCan I ask core team about metaplugin deprecation?14:54
*** henrynash has joined #openstack-meeting14:54
*** AlanClark has joined #openstack-meeting14:55
*** ddieterly has quit IRC14:55
*** egallen has joined #openstack-meeting14:55
john-davidgeWould appreciate some more attention on the IPv6 Prefix Delegation work as well https://review.openstack.org/#/c/15869714:55
john-davidgethanks14:55
neiljerramNova cores are finding it hard to reach consensus on this, and I wonder if some Neutron eyes might help.14:56
armaxneiljerram: noted14:56
*** coolsvap|afk is now known as coolsvap14:56
HenryGPlugin/driver decomposition phase 2: https://review.openstack.org/18726714:56
*** mfisch has joined #openstack-meeting14:56
armaxhichihara: iirc the metaplugin is going to be remoted soon14:56
armax*removed14:56
salv-orlando neiljerram:  I can trime and chime in with my opinions, but there's a chance I'll end up generating even more confusion14:56
armaxhichihara: reach out to mestery, I am sure he knows the latest14:56
*** mfisch is now known as Guest2567614:56
hichiharaarmax: really? I want to remove it in Liberty not M14:57
neiljerramsalv-orlando: I'm sure your contribution would be net positive!14:57
armaxhichihara: ok, so be it14:57
*** cbouch has quit IRC14:57
salv-orlandoneiljerram: the point is that nova made a decision some time ago to make vif plugging completely generic and exclusively driver by parameters dictated from port bindings14:57
hichiharaarmax: Thanks!14:57
salv-orlandoprobably introducing a "script" kind of reverts that decision14:57
numanhttps://review.openstack.org/#/c/189741 request to please review14:57
neiljerramsalv-orlando: It sounds like you know more of the history here than me...14:58
neiljerramsalv-orlando: Would you like to discuss this a little further in openstack-neutron after the meeting?14:59
armaxneiljerram, salv-orlando: it looks like this is the type of conversation that should be tracked on the review page, perhaps?14:59
armaxor in-channel14:59
*** carl_baldwin has joined #openstack-meeting14:59
armaxokay, guys, we’re a minute away from the end of the meeting14:59
armaxI’ll give you a minute back14:59
salv-orlandoarmax: you're right. Anyway I have another meeting now, I will be back available in openstack-neutron in 40 mins14:59
armaxthanks for joining!15:00
armax#endmeeting15:00
neiljerramthx!15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Tue Jun 16 15:00:03 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-06-16-14.00.html15:00
*** ayoung has joined #openstack-meeting15:00
salv-orlandoadieuuuuuu15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-06-16-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-06-16-14.00.log.html15:00
*** pc_m has left #openstack-meeting15:00
yamamoto_bye15:00
ajocheers :)15:00
bauzas#startmeeting nova_scheduler15:00
openstackMeeting started Tue Jun 16 15:00:15 2015 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** unicell has joined #openstack-meeting15:00
*** openstack changes topic to " (Meeting topic: nova_scheduler)"15:00
openstackThe meeting name has been set to 'nova_scheduler'15:00
bauzashola folks15:00
*** tholtzen has left #openstack-meeting15:00
*** rkukura has left #openstack-meeting15:00
*** sudipto_ has quit IRC15:00
lxslio/15:00
hichiharabye15:00
*** mlavalle has left #openstack-meeting15:00
edleafeo/15:00
*** ZZelle-backup has left #openstack-meeting15:00
bauzasn0ano is unable to make the call, so I'm chairing for the best or the worst15:01
bauzasfeel free to buy tomatoes before we start15:01
* edleafe is in another meeting on the phone15:01
*** johnbelamaric has left #openstack-meeting15:01
*** john-davidge has left #openstack-meeting15:01
*** kebray has joined #openstack-meeting15:01
edleafeso sorry if I lag response time15:01
*** kebray has quit IRC15:01
bauzasedleafe: eh, wasn't my turn last week ? :)15:01
*** Guest25676 is now known as mfisch15:01
*** mfisch has quit IRC15:02
*** mfisch has joined #openstack-meeting15:02
*** kebray has joined #openstack-meeting15:02
*** merooney has quit IRC15:02
bauzasokay, waiting a few more time for guests coming in, and then we can start15:02
*** VW has quit IRC15:02
edleafebauzas: :)15:02
*** neiljerram has left #openstack-meeting15:02
*** balajiiyer has joined #openstack-meeting15:02
bauzasokay, guessing that 3 people is definitely good for having consensus, we can start15:03
bauzas(at least, it is easier than 4)15:03
*** achanda has quit IRC15:03
bauzas(and better than 2)15:03
*** VW has joined #openstack-meeting15:03
bauzas#topic Spec tracking15:04
*** VW has quit IRC15:04
*** openstack changes topic to "Spec tracking (Meeting topic: nova_scheduler)"15:04
*** jcoufal has joined #openstack-meeting15:04
bauzasso n0ano was wondering how to track our progress15:04
*** tiswanso has quit IRC15:04
*** ihrachyshka has left #openstack-meeting15:04
bauzasfrom my perspective, we have 2 kind of things15:04
*** banix_ has quit IRC15:04
edleafedidn't he create an etherpad or wiki page?15:04
*** dkranz has joined #openstack-meeting15:04
bauzas1/ things that are priorities15:04
*** tiswanso has joined #openstack-meeting15:04
bauzas2/ things that aren't15:04
bauzasedleafe: yup, but he recently raised the question about that during the last nova meeting15:05
*** belmoreira has quit IRC15:05
bauzasedleafe: and I was -1 about that15:05
bauzasso, as I said, there are 2 possibilities15:05
bauzaseither you work on a prioritized spec15:06
*** fallenpegasus has joined #openstack-meeting15:06
bauzas(or you claim for it)15:06
*** sudipto has joined #openstack-meeting15:06
edleafesuggestion for tracking these things?15:06
*** Daisy has quit IRC15:06
bauzasor, you don't15:06
bauzasso, given that, we already the Master Doom of the Etherpads for Nova15:06
lxsliAn etherpad to track our Liberty commitments and process sounds useful; in addition to the liberty-nova-priorities list where we may put 3 items for review15:06
bauzas#link https://etherpad.openstack.org/p/liberty-nova-priorities-tracking15:06
*** jaypipes has quit IRC15:06
bauzasMHO is that we can add our specs there, either it's a prio or not15:07
*** esker has joined #openstack-meeting15:07
*** henrynash_ has joined #openstack-meeting15:07
bauzasL29 is for Scheduler priority specs15:07
edleafejust added my teeny spec15:07
bauzasso, I'm thinking we should just add non-prio specs in another Scheduler bullet at the bottom15:08
bauzasjohnthetubaguy: are you around ?15:08
bauzasjohnthetubaguy: we have some specs that are priorities or claiming for so we can add them to https://etherpad.openstack.org/p/liberty-nova-priorities-tracking15:08
*** merooney has joined #openstack-meeting15:08
lxsliWe can add some extra things which aren't ready to be reviewed quite yet15:08
lxsliI wouldn't like to clog it up with everything we're thinking of though15:09
bauzasjohnthetubaguy: but some specs couldn't be priority, so my gut is that we should add a Scheduler subteam item at the bottom15:09
edleafelxsli: as long as they are in a separate section15:09
bauzas(and explicitely say those are not prio)15:09
edleafelxsli: we can move them around when they are ready for review15:09
johnthetubaguyI think having a single scheduler subteam area is easiest if possible15:09
bauzaslxsli: edleafe: +1, I want it very clear that the first section (L17) is only for those we consider mergeable15:10
*** numan has quit IRC15:10
johnthetubaguyyeah, just have a separate ready vs needs review by sub team lists15:10
*** henrynash has quit IRC15:10
lxslijohnthetubaguy: without a separate etherpad?15:10
johnthetubaguyyou can have non priority stuff separate if you want15:10
*** achanda has joined #openstack-meeting15:10
bauzasjohnthetubaguy: okay, I just want to make it clear that not all the specs are priority15:10
edleafelxsli: L17 is for the API15:10
*** prazumovsky has quit IRC15:10
edleafelxsli: you mean L3515:10
*** VanL has joined #openstack-meeting15:10
johnthetubaguylxsli: yeah, please not more etherpads, people don't seem to look at the current one at the moment, so I think adding more will be counter productive15:10
bauzasedleafe: yup15:10
johnthetubaguybauzas: the blueprint and spec deadline is super soon, specs that are not up now are very unlikely to make the deadline at this point15:11
*** aranjan has joined #openstack-meeting15:11
bauzasjohnthetubaguy: my point15:11
*** VW has joined #openstack-meeting15:12
bauzasjohnthetubaguy: I mean, during Liberty, we will have 2 kind of changes15:12
johnthetubaguyso yeah, I would focus on making sure you have the specs merged that you need, and focusing your view on those right now15:12
bauzasjohnthetubaguy: (speaking of changes, here)15:12
bauzasjohnthetubaguy: edleafe: lxsli: I'm just amending the etherpad now15:12
*** yamahata has quit IRC15:12
*** amuller has left #openstack-meeting15:12
*** henrynash_ has quit IRC15:13
johnthetubaguycool, thanks for pushing on this folks15:13
bauzasthe idea is to separate non-prio changes from the prio ones, to help both nova cores and sched subteam to get the proper attraction for prio changes, while we still want to keep focus on non-prio15:13
*** henrynash has joined #openstack-meeting15:14
bauzasokay, I'm taking an action to refine a little bit the sections15:14
*** wojdev has quit IRC15:14
bauzas#action bauzas to amend the etherpad to make clear what is a priority change vs. what is not a priority change15:14
bauzaslet's move on then15:14
bauzasjohnthetubaguy: thanks for your insights on that15:14
bauzas#topic Liberty tracking15:15
*** openstack changes topic to "Liberty tracking (Meeting topic: nova_scheduler)"15:15
*** jlibosva has left #openstack-meeting15:15
bauzasso, before going further, do we agree on using https://etherpad.openstack.org/p/liberty-nova-priorities-tracking for tracking ?15:15
*** niclem has quit IRC15:16
bauzas#startvote do we agree on using https://etherpad.openstack.org/p/liberty-nova-priorities-tracking for tracking? yes or no15:16
openstackBegin voting on: do we agree on using https://etherpad.openstack.org/p/liberty-nova-priorities-tracking for tracking? Valid vote options are yes, or, no.15:16
openstackVote using '#vote OPTION'. Only your last vote counts.15:16
lxslisounds like that's what john prefers15:16
*** balajiiyer has left #openstack-meeting15:16
lxsli#vote yes15:16
*** banix has joined #openstack-meeting15:16
bauzasedleafe: ?15:16
*** aranjan has quit IRC15:16
bauzas#vote yes15:16
*** etoews has joined #openstack-meeting15:16
bauzasI would love if edleafe could give his view on that, even if I think we got his idea :)15:17
lxslied's on the phone15:17
bauzasright, that's why I make edleafe's IRC client blinking like Xmas15:18
bauzas:)15:18
lxsliheh15:18
*** henrynash_ has joined #openstack-meeting15:18
bauzasok, let's close the vote15:18
edleafe#vote yes15:18
bauzas#endvote15:18
openstackVoted on "do we agree on using https://etherpad.openstack.org/p/liberty-nova-priorities-tracking for tracking?" Results are15:18
openstackyes (3): bauzas, edleafe, lxsli15:18
bauzaswoooh15:18
edleafewhew, just made it!15:18
bauzasedleafe: heh :)15:18
bauzasok, so, given that15:18
bauzas#action all to update https://etherpad.openstack.org/p/liberty-nova-priorities-tracking to mention their changes if necessary for tracking15:19
bauzas#info changes that are not given in the etherpad list are not considered for tracking yet15:19
bauzasdo you agree, guys ?15:19
*** henrynash has quit IRC15:20
*** henrynash_ is now known as henrynash15:20
*** Fdot has quit IRC15:20
edleafeyep15:20
bauzasI mean, I have the RequestSpec object patch series that is up for review, but I don't consider it yet good for being tracked15:20
*** asrangne has joined #openstack-meeting15:20
*** varora- has left #openstack-meeting15:20
lxsliWhat's the significance of being tracked?15:20
bauzaslxsli: being discussed periodically by the team to make sure we make our deadlines ? :)15:21
lxsliso there's some kind of promise of delivery?15:21
bauzasyup15:21
lxsliOK, thanks15:21
*** banix has quit IRC15:21
bauzasthat doesn't mean that we can't discuss on some spec implementations now, but I really want to use the etherpad for things that are needing reviews15:21
*** padkrish has quit IRC15:22
*** banix has joined #openstack-meeting15:22
bauzasbut let's loop back with n0ano next week15:22
*** aswadr has quit IRC15:23
*** henrynash_ has joined #openstack-meeting15:23
*** puranamr has joined #openstack-meeting15:23
edleafeOne thing I wanted to mention15:23
bauzasgiven that, does anyone want to discuss about a specific spec or implementation they want to share ?15:24
bauzasedleafe: fire it15:24
edleafeIf you review one of these specs and give a -1, please be sure to follow up15:24
*** dannywilson has joined #openstack-meeting15:24
bauzasedleafe: wise words15:24
edleafen0ano gave me a -1 with some questions15:24
edleafeand then left it all last week15:24
edleafeas a result, no one reviewed the spec on Friday15:24
sudiptobauzas, I guess it doesn't apply to specs that necessarily don't fall under the priority list? Is there a way out for specs that are deemed essential for someone beyond the ones listed?15:24
*** john_a_joyce has quit IRC15:24
bauzasedleafe: don't hesitate to bug people if you don't get feedback rapidely15:24
*** spzala has joined #openstack-meeting15:24
lxslibauzas: +115:25
bauzasedleafe: on my own, I seriously lag from reviews atm15:25
edleafebauzas: I lag reviews, but I always star those I give a -1 to so I can follow up15:25
bauzassudipto: we just agreed on tracking those in the etherpad too, so you could get attention from the sched team15:25
*** achanda has quit IRC15:25
sudiptobauzas, ok sure...15:25
bauzassudipto: https://etherpad.openstack.org/p/liberty-nova-priorities-tracking L4315:26
sudiptobauzas, thx!15:26
*** henrynash has quit IRC15:26
*** henrynash_ is now known as henrynash15:26
bauzasedleafe: fair point, but you can't assume everybody does that :)15:26
*** puranamr has quit IRC15:26
bauzaswe are a small team, it's reasonable to bug people if so15:26
edleafebauzas: hence my reminder :)15:26
bauzasedleafe: cool15:27
bauzasany spec/bp/change that we want to discuss now ?15:27
*** ajmiller has quit IRC15:27
*** thedodd has joined #openstack-meeting15:27
*** changbl has joined #openstack-meeting15:27
lxsliI'm happy with Jay's resource objects spec, it'd be great to get some more reviews on that now15:27
*** ajmiller has joined #openstack-meeting15:27
*** otter768 has joined #openstack-meeting15:27
bauzasI could just tell that I'm suffering severe PITA with the ReqSpec object BP, but I guess you see my complaints all the day on IRC15:28
bauzaslxsli: in my queue15:28
bauzaslxsli: I saw you squashed the 2 specs, great and ty15:28
lxslibauzas: yep always the idea, just needed to work out the kinks with jay first15:28
bauzascool15:28
bauzasmoving on then ?15:29
*** hashar has quit IRC15:29
bauzasedleafe: I saw you were proposing a log information for NoValidHost ?15:29
bauzasthat's on my queue too15:29
edleafeyep15:29
*** asrangne__ has joined #openstack-meeting15:29
bauzasedleafe: you could put it as non-prio stuff (or prio, don't remember your claim)15:29
edleafeI had originally tied it to the ReqSpec, but since that isn't going to be used for filtering in Liberty, I simplified it15:30
edleafeIt was a priority from the summit, IIRC15:30
bauzasedleafe: I missed that point, I'll take some time to decently -1 it15:30
bauzas:p15:30
*** primeministerp has joined #openstack-meeting15:30
bauzas(just kidding)15:30
edleafebauzas: I expect nothing less!15:30
bauzasok, moving on15:31
bauzas#topic New meeting time15:31
*** openstack changes topic to "New meeting time (Meeting topic: nova_scheduler)"15:31
*** asrangne has quit IRC15:31
bauzasso I was horribly lagging last week, was there any consensus reached ?15:31
*** otter768 has quit IRC15:32
edleafeno, since there was no single time where everyone was available15:32
bauzasor are we just doomed because of a stupid French wanting to take some time with his daughters ?15:32
*** merooney has quit IRC15:32
bauzasedleafe: so, what was the outcome ?15:32
edleafewe are doomed because stupid jaypipes wants to go to his meetings :)15:32
lxsliThey should move America east a bit15:32
*** zz_ttrifonov is now known as ttrifonov15:33
edleafen0ano just punted15:33
bauzasthings would be far easier if anyone could just use the Paris TZ15:33
* bauzas whispers15:33
* edleafe wonders if 'punted' translates well...15:33
*** KunalGandhi has joined #openstack-meeting15:33
bauzasok, so we're stuck ?15:33
bauzasshould we think about alternating ?15:34
*** niclem has joined #openstack-meeting15:34
bauzaseven weeks using that timeslot, and odd weeks using a new timeslot ?15:34
edleafebauzas: there is another option15:34
*** dneary has joined #openstack-meeting15:34
*** PrashantS has joined #openstack-meeting15:34
bauzasedleafe: I'm hanging at your lips15:34
*** PrashantS has quit IRC15:34
edleafe(looking it up...)15:35
*** fanyaohong has quit IRC15:35
bauzas(don't know if that translates well too...)15:35
edleafe1600 UTC was ok for everyone except johnthetubaguy15:35
*** KunalGandhi has quit IRC15:35
lxslihe's not that important15:35
*** PrashantS has joined #openstack-meeting15:35
johnthetubaguy+115:35
bauzasthinking about a rebellion ?15:35
*** puranamr has joined #openstack-meeting15:35
edleafelxsli: heh, I'm sure he'll be glad to hear that :)15:35
lxsli"coup, coup" tweeted the pigeons15:35
johnthetubaguyI have a regular meeting at that time, but its moving soon anyways15:36
bauzasdon't forget we cut our King's head15:36
johnthetubaguybut thats fine15:36
*** KunalGandhi has joined #openstack-meeting15:36
edleafebut those were the only two times that jaypipes was available15:36
johnthetubaguyits not on IRC so I can be vaguely around for both15:36
*** changbl has quit IRC15:36
johnthetubaguyI would go for that one15:36
* johnthetubaguy wonders where in the agenda to raise his crazy spec and docs patches15:36
edleafethe other option is to move it to monday or thursday15:36
*** singlethink has quit IRC15:36
bauzasjohnthetubaguy: it was during the previous topic, but let's discuss that during open time15:37
johnthetubaguybauzas: yeah, I figured I missed that, cool15:37
*** rjaiswal has joined #openstack-meeting15:37
edleafebauzas: how about I ping jaypipes for his availability, and then create a new doodle based on that?15:37
bauzaswe only have that topic and then we open the discussion15:37
bauzasedleafe: huge +115:37
*** tsekiyama has joined #openstack-meeting15:37
johnthetubaguyseems like we can just go for 1600UTC though?15:37
edleafe#action edleafe to ping jaypipes for availability and start new doodle for meeting time15:38
johnthetubaguyignore my no vote on that, I can lurk like I normally do just fine at that time, if it helps15:38
edleafejohnthetubaguy: yes, but jay was a maybe for that15:38
johnthetubaguyedleafe: ah, gotcha15:38
bauzasedleafe: not sure you logged the action15:38
edleafejohnthetubaguy: so you're not the only problem :)15:38
bauzas#chair edleafe15:38
openstackCurrent chairs: bauzas edleafe15:38
lxsliedleafe: action should be to find out the issue with 1600 first then15:39
edleafebauzas: yeah, actions and links can be posted by anyone15:39
bauzaslxsli: agreed15:39
bauzas#undo15:39
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x9730650>15:39
lxsliooh undo, fancy15:39
edleafe#action edleafe to ping jaypipes for his issue with Tuesday 1600 UTC15:39
bauzasedleafe: before we agree on that, could we just consider using the 1600UTC slot and check with jaypiprsd15:39
bauzas?15:39
bauzasyeah, that one15:40
bauzasI missed the new doodle thing when I shouted "hell yea"15:40
edleafebauzas: is there a meeting room available?15:40
*** KunalGandhi has quit IRC15:40
bauzasedleafe: we can sort that out quickly, or complain about that to ttx if no15:40
*** krtaylor has quit IRC15:40
bauzasedleafe: I'm not that worried15:40
edleafeI remember the 1700 was open15:41
edleafenot sure about 160015:41
bauzasedleafe: the #openstack-meeting room was sexy, but I can leave with that15:41
lxslishall we move on?15:41
bauzaslxsli: +1, that can be figured out later15:41
*** henrynash_ has joined #openstack-meeting15:41
bauzas#topic open discussion15:41
*** openstack changes topic to "open discussion (Meeting topic: nova_scheduler)"15:41
bauzasjohnthetubaguy: had a status to share ?15:41
*** jgrimm is now known as zz_jgrimm15:41
johnthetubaguy#link https://review.openstack.org/19226015:41
johnthetubaguyso I had an action to write up a summary of the scheduler evolution plans15:41
johnthetubaguythats a first draft of that effort15:42
lxslioh cracking, I was thinking of doing that but not looking forward to it15:42
johnthetubaguyhelp extremely welcome, like please take over that patch and make it better15:42
johnthetubaguyany one other thing tooo15:42
bauzasjohnthetubaguy: okay, are you fine with me providing some updates ?15:42
johnthetubaguybauzas: please do, that would be awesome15:42
bauzasjohnthetubaguy: sure, that's on my todo list15:42
bauzasstarring it even :)15:42
*** Gerald_K has quit IRC15:43
johnthetubaguyso I wrote up some stuff around the parallel scheduling effort too15:43
bauzasjohnthetubaguy: ooooooh15:43
johnthetubaguybased on the summit session, and stuff I was mumbling about during that session15:43
johnthetubaguy#link https://review.openstack.org/#/c/191914/15:43
johnthetubaguyits a backlog spec15:43
bauzasjohnthetubaguy: saw ndipanov's proposal btw ?15:43
johnthetubaguybauzas: yeah, this is mostly unrelated it turns out15:43
johnthetubaguyso its a backlog spec15:43
johnthetubaguyso its collecting a problem definition15:43
johnthetubaguyand its talking about alternatives15:44
bauzasjohnthetubaguy: cool, I should probably say the same that for the last spec15:44
johnthetubaguyI am not trying to pick a winner, or assign the work15:44
bauzass/spec/devref15:44
johnthetubaguyjust doument the ideas15:44
bauzassure, that's a backlog spec15:44
*** henrynash has quit IRC15:44
*** henrynash_ is now known as henrynash15:44
johnthetubaguysomehow, its over 400 lines long15:44
johnthetubaguyoops15:44
bauzasokay, that's pretty fancy15:44
edleafejohnthetubaguy: curious - backlog specs don't go in nova-specs?15:44
bauzasedleafe: they do, but on a separate path15:45
johnthetubaguyedleafe: http://specs.openstack.org/openstack/nova-specs/specs/backlog/index.html15:45
bauzasok, that's cool, we could even put those both changes in the etherpad for reviews15:45
edleafejohnthetubaguy: just confused, since your spec is in nova, not nova-specs15:45
*** john-davidge has joined #openstack-meeting15:46
bauzasedleafe: hell no15:46
*** absubram has joined #openstack-meeting15:46
edleafejohnthetubaguy: haven't created a backlog spec myself15:46
johnthetubaguyedleafe: one is a nova doc on architectural evolution15:46
bauzasedleafe: https://review.openstack.org/#/c/191914/ is in nova-specs15:46
johnthetubaguyedleafe: the other is in the nova-specs backlog specs15:46
*** zz_jgrimm is now known as jgrimm15:46
bauzasedleafe: https://review.openstack.org/192260 is a devref doc15:46
edleafejohnthetubaguy: ah, I see15:46
bauzashuh, jinxed15:46
*** MeganR has joined #openstack-meeting15:46
*** hichihara has quit IRC15:46
johnthetubaguyedleafe: the nova doc stuff is designed to span multiple nova-specs, giving a high level overview, then pointers once thats possible15:46
edleafejohnthetubaguy: I saw the .rst and assumed it was a spec15:47
*** leeantho has joined #openstack-meeting15:47
johnthetubaguyedleafe: this is all very shiny and new process right now15:47
johnthetubaguyedleafe: ah, easy done!15:47
edleafejohnthetubaguy: too shiny - it blinded me! :)15:47
bauzas:)15:47
johnthetubaguyI keep -2ing specs because they don't have a spec merged, so I can't throw stones15:47
*** john-davidge has quit IRC15:48
bauzasjohnthetubaguy: thanks a lot for your proposals, we'll follow up on those15:48
johnthetubaguyso there are other actions folks have from the summit15:48
johnthetubaguyit would be good to update the etherpad when they are done15:48
*** changbl has joined #openstack-meeting15:48
johnthetubaguy#link https://etherpad.openstack.org/p/YVR-nova-liberty-summit-action-items15:48
bauzas#link https://etherpad.openstack.org/p/YVR-nova-liberty-summit-action-items15:48
bauzas#undo15:48
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x9503d90>15:48
bauzasjohnthetubaguy: yeah we're just starting to collect feedback15:49
bauzasjohnthetubaguy: given all the things we are, I'm at least wanting to have some design discussions for things that are in the list but not yet with a clear plan15:49
*** yassine has quit IRC15:50
bauzasjohnthetubaguy: so we could propose and implement those for Muppet cycle15:50
*** MeganR has left #openstack-meeting15:50
*** puranamr has quit IRC15:50
johnthetubaguybauzas: I really want backlog specs for that stuff15:50
bauzasjohnthetubaguy: +115:50
johnthetubaguybauzas: so folks outside the usual groups can be more invovled15:51
*** puranamr has joined #openstack-meeting15:51
bauzasjohnthetubaguy: that's what I say "design discussions", translate it to 'draw a draft'15:51
bauzasjohnthetubaguy: which is even one step further than a backlog spec15:51
lxslibauzas: perhaps 'requirement discussions'15:52
bauzasjohnthetubaguy: +1 on welcoming new contributors, hence the idea to open up the reviews to things that people want to share with us15:52
*** arnaud___ has joined #openstack-meeting15:52
johnthetubaguybauzas: just agreeing the problem in a backlog spec I think is good step forward15:52
bauzasI got your idea :)15:52
*** fzdarsky has quit IRC15:52
bauzascollect feedback, iterate over that15:53
*** ddieterl_ has quit IRC15:53
edleafeso if someone has an outlandish new approach, a backlog spec would be the place to propose it?15:53
*** VanL has quit IRC15:53
bauzasedleafe: a backlog spec is for stating a problem15:53
edleafebauzas: not for proposing solutions?15:54
*** krtaylor has joined #openstack-meeting15:54
bauzasedleafe: technically, there is no section for that IIRC15:54
bauzasedleafe: but that doesn't mean we're avoiding to think about the solution15:54
*** eghobo has joined #openstack-meeting15:54
edleafehmmm... I thought that if there was a proposed solution that couldn't be implemented in the current cycle, it went into the backlog15:55
johnthetubaguyso you can do both15:55
lxsliaiui backlog specs you don't plan to implement yourself15:55
*** alop has joined #openstack-meeting15:55
johnthetubaguyso I am about to update the doc page on this15:55
lxsliso you can propose a solution but it might not get implemented that way15:55
johnthetubaguybut basically, if you miss out any section of the spec15:55
johnthetubaguyits on the backlog15:55
edleafelxsli: sure. Propose a solution, and let others have at it15:55
johnthetubaguythat include assignee or implementation15:55
bauzasmaybe this discussion is wider than just for our subteam ? :)15:55
*** dneary has quit IRC15:56
*** Sukhdev has quit IRC15:56
edleafebauzas: yeah - 3 minutes left15:56
johnthetubaguybauzas: sure, I thought it was already "agreed" though, as defined here: http://specs.openstack.org/openstack/nova-specs/specs/backlog/index.html15:56
*** ttrifonov is now known as zz_ttrifonov15:56
bauzasjohnthetubaguy: let's discuss that back on #openstack-nova, I guess some people could voice there15:56
johnthetubaguysounds good15:56
*** IanGovett has quit IRC15:56
bauzas(and you would get better exposure for your thoughts)15:57
bauzasok, any other topic for the 2 mins left ?15:57
lxsliAnything else then/15:57
*** ayoung has quit IRC15:57
bauzascrickets ?15:57
*** tianhuanqin has quit IRC15:58
*** doude has quit IRC15:58
bauzasfair, let's call the wrap15:58
bauzas#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Tue Jun 16 15:58:26 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
lxslithanks for leading bauzas15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2015/nova_scheduler.2015-06-16-15.00.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2015/nova_scheduler.2015-06-16-15.00.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2015/nova_scheduler.2015-06-16-15.00.log.html15:58
bauzasnp15:58
*** janonymous_ has joined #openstack-meeting15:58
*** padkrish has joined #openstack-meeting15:59
edleafeyeah, thanks, bauzas15:59
bauzas(hum, sounds the right phrasing is "let's call it a wrap)15:59
*** VW has quit IRC16:00
edleafebauzas: yes, but yours was close enough :)16:00
primeministerp#startmeeting hyper-v16:00
openstackMeeting started Tue Jun 16 16:00:45 2015 UTC and is due to finish in 60 minutes.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: hyper-v)"16:00
openstackThe meeting name has been set to 'hyper_v'16:00
primeministerphey guys16:01
alexpilottio/16:01
primeministerp#topic blueprints16:01
*** openstack changes topic to "blueprints (Meeting topic: hyper-v)"16:01
*** cdub has quit IRC16:01
primeministerpalexpilotti: care to share an update on the status of our liberty blueprints16:01
alexpilottihere comes the list:16:02
alexpilottihttps://blueprints.launchpad.net/nova/+spec/hyper-v-rescue16:02
alexpilottihttps://blueprints.launchpad.net/nova/+spec/hyper-v-imagecache-cleanup16:02
*** miyagishi_t has left #openstack-meeting16:02
alexpilottihttps://blueprints.launchpad.net/nova/+spec/hyper-v-ovs-vif16:02
alexpilottihttps://blueprints.launchpad.net/nova/+spec/hyper-v-remotefx16:02
alexpilottihttps://blueprints.launchpad.net/nova/+spec/hyper-v-vnic-hot-plug16:03
*** henrynash_ has joined #openstack-meeting16:03
alexpilottihttps://blueprints.launchpad.net/nova/+spec/hyperv-fibre-channel16:03
alexpilottihttps://blueprints.launchpad.net/nova/+spec/hyperv-serial-ports16:03
alexpilottihttps://blueprints.launchpad.net/nova/+spec/hyperv-storage-qos16:03
*** kebray has quit IRC16:04
*** jlanoux has quit IRC16:04
alexpilottimore under review:16:04
alexpilottihttps://blueprints.launchpad.net/nova/+spec/hyper-v-cluster16:04
alexpilottihttps://blueprints.launchpad.net/nova/+spec/hyper-v-uefi-secureboot16:05
*** kebray has joined #openstack-meeting16:05
*** henrynash has quit IRC16:05
*** henrynash_ is now known as henrynash16:05
alexpilottimore being drafted:16:06
alexpilottihttps://blueprints.launchpad.net/nova/+spec/hyperv-assisted-volume-snapshot16:06
primeministerpalexpilotti: re: fibre-channel we just sent the address for shipment of the device, hopefully i'll hear more to day16:06
alexpilottiManilla: https://blueprints.launchpad.net/manila/+spec/windows-smb-support16:06
alexpilottiOslo:  Workers support on Windows16:07
alexpilottihttps://blueprints.launchpad.net/cinder/+spec/image-volume-cache16:07
alexpilottiMore Nova: https://blueprints.launchpad.net/nova/+spec/improve-block-device-handling16:07
*** comay has joined #openstack-meeting16:08
*** asrangne__ has quit IRC16:08
alexpilottiTempest: Add boot from volume actions tests16:09
alexpilottiNova Threshold features to be spec’d:16:10
alexpilotti Shielded VMs16:10
alexpilottiWindows Containers16:10
*** achanda has joined #openstack-meeting16:10
alexpilottiCinder Tenant based QoS16:10
*** ayoung has joined #openstack-meeting16:10
*** singlethink has joined #openstack-meeting16:11
*** unicell has quit IRC16:11
primeministerpquite a long list16:11
*** VanL has joined #openstack-meeting16:11
*** wojdev has joined #openstack-meeting16:11
*** VW has joined #openstack-meeting16:11
*** ildikov has quit IRC16:11
alexpilottimore updates also on Neutron:16:12
alexpilottihttps://github.com/stackforge/networking-hyperv16:12
primeministerpthx16:12
primeministerpsorry getting pinged from other angles16:13
primeministerpdon't think anyone else is on today16:13
primeministerplet's end here for now16:13
alexpilottiok!16:13
primeministerp#endmeeting16:13
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:13
openstackMeeting ended Tue Jun 16 16:13:33 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2015/hyper_v.2015-06-16-16.00.html16:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2015/hyper_v.2015-06-16-16.00.txt16:13
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2015/hyper_v.2015-06-16-16.00.log.html16:13
*** phil_ has quit IRC16:13
*** esker has quit IRC16:16
*** varora- has joined #openstack-meeting16:18
*** pballand has joined #openstack-meeting16:18
*** mattgriffin has quit IRC16:20
*** padkrish has quit IRC16:20
*** earlephilhower_ has quit IRC16:25
*** mrmartin has joined #openstack-meeting16:26
*** arvinchou_1 has joined #openstack-meeting16:28
*** henrynash_ has joined #openstack-meeting16:28
*** jcoufal has quit IRC16:28
*** jwcroppe has joined #openstack-meeting16:28
*** amotoki has quit IRC16:28
*** arvinchou_ has quit IRC16:29
*** barrett1 has quit IRC16:30
*** baoli has quit IRC16:30
*** rossella_s has quit IRC16:30
*** rrrobbb has joined #openstack-meeting16:30
*** ygbo has quit IRC16:30
*** singleth_ has joined #openstack-meeting16:30
*** aranjan has joined #openstack-meeting16:30
*** rossella_s has joined #openstack-meeting16:30
*** henrynash has quit IRC16:31
*** henrynash_ is now known as henrynash16:31
*** banix has quit IRC16:31
*** baoli_ has joined #openstack-meeting16:31
*** padkrish has joined #openstack-meeting16:32
*** adahms has quit IRC16:32
*** ildikov has joined #openstack-meeting16:33
*** singlethink has quit IRC16:33
*** alop has quit IRC16:33
*** amoturi has quit IRC16:34
*** wojdev has quit IRC16:35
*** Akshik has joined #openstack-meeting16:35
*** arnaud___ has quit IRC16:35
*** banix has joined #openstack-meeting16:36
*** wojdev has joined #openstack-meeting16:36
*** penick has joined #openstack-meeting16:36
*** tiswanso has quit IRC16:40
*** banix_ has joined #openstack-meeting16:40
*** banix has quit IRC16:40
*** banix_ is now known as banix16:40
*** unicell has joined #openstack-meeting16:41
*** alop has joined #openstack-meeting16:41
*** rushil has joined #openstack-meeting16:42
*** sudipto has quit IRC16:43
*** rushiagr_away is now known as rushiagr16:43
*** henrynash has quit IRC16:44
*** dneary has joined #openstack-meeting16:45
*** Swami has joined #openstack-meeting16:47
*** merooney has joined #openstack-meeting16:47
*** Apoorva has joined #openstack-meeting16:47
*** banix has quit IRC16:47
*** tomoe_ has joined #openstack-meeting16:48
*** VanL has quit IRC16:48
*** e0ne has quit IRC16:48
*** Longgeek has quit IRC16:49
*** padkrish has quit IRC16:49
*** absubram has left #openstack-meeting16:50
*** puranamr has quit IRC16:52
*** tomoe_ has quit IRC16:53
*** doude has joined #openstack-meeting16:53
*** doude has quit IRC16:53
*** dguerri is now known as dguerri`16:53
*** puranamr has joined #openstack-meeting16:53
*** thedodd has quit IRC16:53
*** safchain has quit IRC16:53
*** harshs has joined #openstack-meeting16:54
*** lzachery has quit IRC16:55
*** sarob has joined #openstack-meeting16:55
*** primeministerp has quit IRC16:55
*** Longgeek has joined #openstack-meeting16:56
*** Longgeek has quit IRC16:56
*** earlephilhower has joined #openstack-meeting16:57
*** penick has quit IRC16:58
*** wojdev has quit IRC16:58
*** dguerri` is now known as dguerri16:58
*** asselin has joined #openstack-meeting16:58
*** asselin has quit IRC16:59
*** dt_os has quit IRC16:59
*** asselin has joined #openstack-meeting16:59
*** dguerri is now known as dguerri`16:59
*** egallen has quit IRC16:59
*** sarob has quit IRC17:00
*** puranamr has quit IRC17:00
*** sudipto has joined #openstack-meeting17:00
*** padkrish has joined #openstack-meeting17:01
*** mrunge has joined #openstack-meeting17:01
*** sarob has joined #openstack-meeting17:02
*** puranamr has joined #openstack-meeting17:02
*** jwcroppe has quit IRC17:02
*** med_ has joined #openstack-meeting17:03
*** tiswanso has joined #openstack-meeting17:03
*** med_ has quit IRC17:03
*** med_ has joined #openstack-meeting17:03
*** xingchao has quit IRC17:04
*** haomaiwa_ has quit IRC17:04
*** lufix has joined #openstack-meeting17:05
*** tiswanso has quit IRC17:06
*** derekh has quit IRC17:06
*** aranjan has quit IRC17:07
*** tiswanso has joined #openstack-meeting17:07
*** mpaolino has quit IRC17:08
*** aranjan has joined #openstack-meeting17:08
*** Akshik has quit IRC17:09
*** praveens has joined #openstack-meeting17:09
*** amotoki has joined #openstack-meeting17:11
*** ildikov has quit IRC17:11
*** rrrobbb has quit IRC17:12
*** marekd has joined #openstack-meeting17:12
*** haomaiwa_ has joined #openstack-meeting17:13
*** kebray has quit IRC17:13
*** ildikov has joined #openstack-meeting17:13
*** htruta_ has joined #openstack-meeting17:14
*** padkrish has quit IRC17:14
*** rrrobbb has joined #openstack-meeting17:16
*** sdake has quit IRC17:19
*** sdake_ has joined #openstack-meeting17:19
*** matrohon has quit IRC17:21
*** cdub has joined #openstack-meeting17:22
*** gyee has quit IRC17:24
*** pnavarro has quit IRC17:25
*** rushiagr is now known as rushiagr_away17:25
*** gyee has joined #openstack-meeting17:26
*** balajiiyer has joined #openstack-meeting17:28
*** otter768 has joined #openstack-meeting17:28
*** balajiiyer has left #openstack-meeting17:28
*** aimon_ has quit IRC17:31
*** peristeri has joined #openstack-meeting17:33
*** otter768 has quit IRC17:33
*** fzdarsky has joined #openstack-meeting17:35
*** yamahata has joined #openstack-meeting17:36
*** achanda has quit IRC17:36
*** jaypipes has joined #openstack-meeting17:37
*** maxdml has joined #openstack-meeting17:37
*** IanGovett has joined #openstack-meeting17:37
*** pelix has quit IRC17:38
*** lufix has quit IRC17:38
*** dguerri` is now known as dguerri17:38
*** padkrish has joined #openstack-meeting17:39
*** vnod has joined #openstack-meeting17:39
*** doron_afk has quit IRC17:40
*** ypraveen has joined #openstack-meeting17:40
*** yamamoto_ has quit IRC17:42
*** dneary has quit IRC17:42
*** doron_afk has joined #openstack-meeting17:43
*** praveens has quit IRC17:43
*** rjaiswal has quit IRC17:44
*** toscalix has joined #openstack-meeting17:45
*** puranamr has quit IRC17:47
*** VanL has joined #openstack-meeting17:49
*** praveens has joined #openstack-meeting17:49
*** amakarov has joined #openstack-meeting17:50
*** _nadya_ has joined #openstack-meeting17:51
*** doron_afk has quit IRC17:52
*** ivar-lazzaro has joined #openstack-meeting17:52
*** VanL_ has joined #openstack-meeting17:52
*** puranamr has joined #openstack-meeting17:52
*** aranjan has quit IRC17:52
*** breton has joined #openstack-meeting17:53
*** VanL has quit IRC17:53
*** lhcheng has joined #openstack-meeting17:53
*** samleon has joined #openstack-meeting17:54
*** samueldmq has joined #openstack-meeting17:55
*** s3wong has joined #openstack-meeting17:55
*** VW has quit IRC17:55
*** puranamr has quit IRC17:56
*** browne has joined #openstack-meeting17:56
*** puranamr has joined #openstack-meeting17:56
* ayoung sneaks in17:56
*** ivasev has quit IRC17:56
*** _nadya_ has quit IRC17:56
*** achanda has joined #openstack-meeting17:57
bretonhellou17:58
*** baoli_ has quit IRC17:59
stevemarcourtesy pings for ajayaa, amakarov, ayoung, bknudson, breton, browne, davechen, david8hu, dolphm, dstanek, ericksonsantos, geoffarnold, gyee, henrynash, hogepodge, htruta, jamielennox, joesavak, lbragstad, lhcheng, marekd, morganfainberg, nkinder, raildo, rharwood, rodrigods, roxanaghe, samueldmq, stevemar, topol, wanghong17:59
*** VW has joined #openstack-meeting17:59
bknudsonhi17:59
lbragstadstevemar: o/17:59
ericksonsantoshi \o17:59
brownehi17:59
amakarovo/17:59
dstaneko/17:59
david8hu\o17:59
gyee\o18:00
david8hu0/18:00
samueldmqo/ olá !18:00
rodrigodso/18:00
rharwoodo/18:00
*** puranamr has quit IRC18:00
stevemarola!18:00
*** padkrish has quit IRC18:00
ayoungHello18:00
stevemarkeystoners assemble!18:00
bretona lot of topics today18:00
gyeewhat's cooking18:00
*** VW has quit IRC18:00
marekdo/18:00
*** padkrish has joined #openstack-meeting18:00
*** baoli_ has joined #openstack-meeting18:00
lhchengo/18:00
stevemarlong list today, lets start early18:01
*** puranamr has joined #openstack-meeting18:01
raildo:)18:01
*** VW has joined #openstack-meeting18:01
breton++18:01
stevemarmorganfainberg, and dolphm seem to be afk, so i'll jump in18:01
htruta_o/18:01
*** roxanaghe_ has joined #openstack-meeting18:01
stevemar#startmeeting keystone18:01
openstackMeeting started Tue Jun 16 18:01:17 2015 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
marekdjamie won't be here...18: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
stevemarmarekd, yeah, jamie is on the other side of OZ today18:01
stevemar#link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:01
gyeeI need Jamie on one of the topics18:01
*** matrohon has joined #openstack-meeting18:01
stevemar#topic Release numbering18:02
*** openstack changes topic to "Release numbering (Meeting topic: keystone)"18:02
*** vahidh has joined #openstack-meeting18:02
stevemarquick one, i wanted to give everyone a heads up on the numbering change that will occur (likely)18:02
marekdstevemar: numbering of what: ksc, kmw, ksa, keystone?18:02
stevemaryou can read about it here: http://lists.openstack.org/pipermail/openstack-dev/2015-June/067082.html18:02
stevemarkeystone will be released as 8.0.0 in liberty, instead of 2015.218:02
stevemarM-release will be 9.0.018:02
bknudsonjust like windows 8 :(18:03
dstanekmarekd: all the things18:03
gyee8 is a luck number for me18:03
raildobknudson, lol18:03
stevemarthe thinking is, it's been the 8th integrated release18:03
*** eghobo has quit IRC18:03
stevemarnova is at 12.0.018:03
bknudsonlooks like a snowman18:03
*** puranamr has quit IRC18:03
stevemarbknudson never fails to make me laugh18:03
*** praveens has quit IRC18:03
stevemarany questions about it?18:03
*** eghobo has joined #openstack-meeting18:03
*** fawadkhaliq has joined #openstack-meeting18:03
ayoungThat is going to break so many things18:04
bretonwwill the third number ever change?18:04
stevemaraside from what the numbers look like, snowmen or otherwise18:04
ayoungpackaging is supposed to be monotonically increasing. OTOH, I think it will aslign with RDO18:04
bretonI mean, shall we have 8.0.1?18:04
*** henrynash_ has joined #openstack-meeting18:04
stevemarbreton, the second and third will be reserved for if we need to release a stable version of keystone18:04
*** praveens has joined #openstack-meeting18:04
henrynash_(sorry to be late)18:04
stevemarlike we do now18:04
*** padkrish has quit IRC18:05
bretoncool, thanks18:05
stevemarinstead of 2015.1.1 (the next stable release of kilo), it would be 8.0.1 (stable release for liberty)18:05
*** padkrish has joined #openstack-meeting18:05
stevemaror 8.1.0 depending on how much changes18:05
stevemarwe're also going to have 8.0.0b1 for milestone 118:05
*** harshs has quit IRC18:05
bknudsonis it actually following semver?18:05
stevemarayoung, sorry if it breaks things, this one is out of my hands :(18:06
stevemarbknudson, i believe that's the intent18:06
bknudsonor it's just a number?18:06
*** harshs has joined #openstack-meeting18:06
gyeestevemar, any objections from the packagers?18:06
gyeebesides ayoung18:06
ayoungstevemar, I'll be fine.  RDO and RH-OSP are at 7 right now anyway18:06
*** IanGovett has quit IRC18:06
ayoungI'm just laughing to myself18:06
bknudsonthe REST API is versioned separately so I guess this doesn't help us much18:06
stevemargyee, this was made at the TC level, i wasn't really involved, just relaying the decision18:06
*** henrynash_ is now known as henrynash18:06
*** padkrish has quit IRC18:06
*** merooney has quit IRC18:06
stevemarhenrynash, 2 laps for being late18:07
stevemarnext?18:07
*** padkrish has joined #openstack-meeting18:07
henrynashstevemar: ok, agreed, two laps of the table underway18:07
stevemar#topic Outcome of DB2 CI18:07
gyeeif the packages are not concerned about the version change, I guess we're fine18:07
*** openstack changes topic to "Outcome of DB2 CI (Meeting topic: keystone)"18:07
*** lazy_prince has quit IRC18:07
*** jasondotstar has joined #openstack-meeting18:07
stevemarbknudson, did you want to take this one?18:07
bknudsonoh, sure...18:07
bknudsonI think the outcome is that DB2 CI isn't going to report18:08
*** toscalix has quit IRC18:08
* stevemar throws bknudon under the bus18:08
bknudsonuntil we can show that it's more stable18:08
stevemarcurrently it's at a 88% success rate right?18:08
bknudsonor we can get people in US time to be available to disable it when it's not working18:08
bknudsonthat's the only number I've seen18:08
stevemarand it only covers tempest tests18:09
bknudsonI don't think we have actual numbers.18:09
stevemarprobably not :P18:09
dstanekwhere did the 88% number come from?18:09
bknudsondstanek: it was from other projects, not keystone18:09
bknudsonDB2 CI is running on several other projects18:09
*** wojdev has joined #openstack-meeting18:09
*** aimon has joined #openstack-meeting18:09
bknudsonso it might be accurate for keystone but I don't know.18:10
*** mattgriffin has joined #openstack-meeting18:10
stevemarbknudson, i guess we'll let the keystone team know if anything changes18:11
stevemarbut the db2 team will monitor it internally for now18:11
bknudsony, I'm sure they'll talk to me again here when they're ready18:11
stevemarskipping over the jamie topic18:11
stevemar#topic It's time to fix Bug 129115718:12
*** openstack changes topic to "It's time to fix Bug 1291157 (Meeting topic: keystone)"18:12
openstackbug 1291157 in python-keystoneclient "idp deletion should trigger token revocation" [High,Triaged] https://launchpad.net/bugs/1291157 - Assigned to Navid Pustchi (npustchi)18:12
stevemarmarekd, the floor is yours18:12
*** sarob has quit IRC18:12
marekdhi, i wanted to get back to the bug and refreshed some knoweldge. I know some of you were tackling it.18:12
bknudsonstevemar: you reported that a long time ago18:12
*** ajiang has joined #openstack-meeting18:13
stevemarbknudson, i did, basically the description is pretty sufficient18:13
marekdI will have an intern this summer and thought i could make him work on that, as clearly this bug is not something that can be fixed in 1-2 hours.18:13
stevemarmarekd, sounds like a good project for the intern18:13
stevemarunder your expert guidance of course ;)18:14
*** amoturi has joined #openstack-meeting18:14
marekdstevemar: i think so, as he would need to learn about revocations in keystone either way.18:14
marekdstevemar: don't be sarcastic :P18:14
gyeerevoke by IdP will be fun18:14
marekdstevemar: anyway, i think it's pretty straightforward how to tackle uuid tokens, yet it may need extending the db schema.18:14
gyeewe don't index the tokens by IdP do we?18:14
bknudsonis Navid the intern?18:15
marekdbknudson: no18:15
stevemarbknudson, navid was a utsc guy18:15
stevemari'll unassign18:15
marekdstevemar: please.18:15
marekdstevemar: please do18:15
stevemardone18:15
lbragstadutsc?18:15
marekdutsa18:15
lbragstadahh18:15
stevemarwhoops18:15
stevemarutsc is a canadian uni :P my bad18:16
marekdi wanted to know what is the status of the revocation events...18:16
ayoungstevemar, your very bad18:16
marekddoes it even work now?18:16
marekdayoung: ^^18:16
*** coolsvap is now known as coolsvap|afk18:16
ayoungnope18:16
*** sarob has joined #openstack-meeting18:16
bknudsonrevocation events can be used in keystone server18:16
ayoungI mean, not by IdP18:16
bknudsonyou can disable revoke by list18:16
ayoungacutally, I don't know.  I have not touched revocation events in a while18:16
marekdbknudson: ok, so we must take into consideration while working on this bug18:17
amakarovayoung, and I still wait for them in ksc ))18:17
*** merooney has joined #openstack-meeting18:17
bknudsony, you either need to support both since the best we could do now is deprecate one or the other18:17
bknudsonor both18:17
stevemarmarekd, it sucks that this depend on what kind of token is issued18:17
ayoungamakarov, go for it.18:17
marekdstevemar: that's the nature of different tokens....lots of things change :-)18:18
ayoungamakarov, I'm done tilting at that particular Windmill.18:18
stevemarmarekd, even if it's a solution for just 1 token format, it's better than nothing18:18
amakarovayoung, let's drop revocations18:18
ayoungOK18:18
marekduh...?18:18
marekdstevemar: do you think it would need some specs, approved by June 21?18:19
stevemarmarekd, preferably, but i understand if your intern hasn't started yet and you want to put them through the process18:19
stevemarthis is also low impact, so i think it's OK to make it an exception18:20
*** dprince has quit IRC18:20
*** wojdev has quit IRC18:20
marekdstevemar: he will be here end of June, and i will need to make some intro to the Openstack world so it may few days :-)18:20
bknudsonthis is a bug, so no blueprint or spec for that18:20
marekdbknudson: ah, cool18:20
marekdbknudson: right.18:20
stevemarbknudson, if the outcome is a new API or feature then a spec might be needed18:20
marekdayoung: is there any vision on how you'd like to see it inrevocation events?18:20
ayoungso...intern is going to work on revoke by IdP?18:21
marekdayoung: that's one of the ideas i had.18:21
bknudsonit does depend on the changes, since yo can't change the api for a bug, that would be a feature18:21
ayoungmarekd, yeah, lots of visions.  I think it was the Peyote18:21
ayoungmarekd, too long for me to derail here18:21
marekdPeyote?18:21
marekdayoung: i will catch up with ya one day after the meeting.18:21
*** fawadkhaliq has quit IRC18:22
marekdlbragstad: for fernet....18:22
ayoungmarekd, so,  revocation events in the client only make sense for PKI style tokens.  I am done trying to push that through18:22
marekdlbragstad: any opinoins, or you already see any corner cases?18:22
*** iurygregory has joined #openstack-meeting18:22
*** sarob has quit IRC18:22
anteayamarekd: https://en.wikipedia.org/wiki/Peyote18:22
ayoungtokens in geenral should live for 5 minutes, no revation necessary18:22
*** achanda has quit IRC18:22
ayoungany thing longer than 5 minutes gets a trust, or a better delegation agreement than we have now anyway18:23
lbragstadmarekd: the middleware will need the token revocation lists18:23
ayoungbut...not for Liberty18:23
marekddo we all agree revocations shall die?18:23
amakarovayoung, ideally tokens should have single use!18:23
marekdi don't want to make him work on something that will die18:23
marekdanteaya: thanks.18:23
gyeerevocation shall die18:23
ayoungmarekd, my view is that dynamic policy is key to any future sanity coming out of Keystone18:24
henrynashso in principle I agree…but we need to make sure we understand the path the point when revocations can really die18:24
ayoungwith that, we can then work on unfied delegation, and many other things besides18:24
marekdlbragstad: ayoung how do we revoke fernet tokens?18:24
lbragstadmarekd: otherwise we are always stuck to online validation18:24
*** crc32 has joined #openstack-meeting18:24
ayoungmarekd, let me defer for now...18:25
anteayamarekd: np18:25
henrynashwhat impact on client apps who (almost entirely today) grab a token and assume that it will never experie (well not likely when the user is still logged in)18:25
*** htruta_ has quit IRC18:25
marekdlbragstad: how do we revoke fernet tokens? online validation ?18:25
gyeehenrynash, the latest auth plugins handles token renewal pretty smoothly now18:25
lbragstadmarekd: a revocation event is built and the renovation list is checked on validation of a token18:26
henrynashwhich is totally teh wrong thing to do….but us wishing it wasn’t so doesn’t make it any less true18:26
marekdlbragstad: ok, so basically it's the same mechanism as with PKI ?18:26
lbragstadmarekd: maybe, I'm not all that familiar with pki18:26
ayoungmarekd, fernet uses revocation events18:27
ayoungso, no revocation list18:27
lbragstadmarekd: we have a bunch of those test cases added to test_v3_auth.py18:27
*** banix has joined #openstack-meeting18:27
marekdayoung: ouch, so you want revocation *lists* or *events* to die?18:27
bretondo we kill revocation events or lists?18:27
marekdor both?18:27
henrynashwe should, imho: get a godo solution of short lived tokens (provided in parallel with the current ones), provide loads of wroking examples of client code that shows how to work with such things (how to “refresh”)18:27
marekdbreton: ++ :-)18:28
marekdbreton: same question18:28
*** marcusvrn has joined #openstack-meeting18:28
ayoungmarekd, I *want* both to die. but I am not the decider.  I never wanted either, even though I wrote both18:28
gyeehenrynash, ++18:28
*** crc32 has quit IRC18:29
ayoungI just have no desire to continue working on either, so I'll defer.  But Revoke by IdP would have been easy if we mapped 1 IdP to one domain18:29
marekdayoung: ok, so it looks like i will make my guy focus on uuid for now, this should be good for a warmup at least.18:29
*** puranamr has joined #openstack-meeting18:29
gyeemarekd, what you do have for him to do for encore? :)18:29
gyeeif revoke by IdP is just a warmup18:30
*** marcusvrn1 has quit IRC18:30
marekdgyee: so you claim it's hard or too easy? :-)18:30
*** banix_ has joined #openstack-meeting18:30
gyeeits hard18:30
lbragstadso, what's going to replace revocation events/lists if it's removed?18:30
ayounglbragstad, nothing!18:30
ayounglbragstad, short term tokens18:30
marekdgyee: so, maybe i will not need any encore :-)18:30
dstaneklbragstad: it's just a bad model18:31
marekdhe wil be there for 2 months and it's not a really full time job.18:31
ayoungthe idea is that a token should last such a short amount of time, that by the time you revoke it, it has expired18:31
lbragstadtoken_expiration = 60 or something?18:31
bretonlbragstad: that's the point -- the token will die young and their exposure will not give anything18:31
ayoungI say 5 minutes, as that seems to be the limit of click skew, but sure18:31
marekdok, i have a clearer vision. thanks for now.18:31
marekdstevemar: ^^18:31
lbragstadok18:31
lbragstadmakes sense18:31
*** achanda has joined #openstack-meeting18:31
lbragstadthanks18:31
ayounglbragstad, I'd like to see tokens themselves go away18:31
marekdayoung: in favor of what?18:32
*** kebray has joined #openstack-meeting18:32
marekdsaml assertions?18:32
*** eghobo has quit IRC18:32
ayounginstead, I authenticate as me using X509 or Kerberos or SAML, and the remote server looks at the deleagtion ID I provide to see if Ia ma ctually authorized18:32
* marekd please, not saml!18:32
*** lhcheng has quit IRC18:32
bretonwe didn't we use oauth instead of tokens?18:32
*** praveens has quit IRC18:32
ayoungmarekd, SAML for those that want it, X509 or Kerberos for those of us that want it18:32
ayoungbreton, same same18:32
*** banix has quit IRC18:32
*** banix_ is now known as banix18:32
gyeebrethon, oath uses *tokens*18:33
stevemari think we're getting off topic ish18:33
ayoungoauth and keystone are pretty similar,  as far as why...ask those who came before the project18:33
gyeeaccess tokens, refresh tokens, etc18:33
ayoungyes we are18:33
ayoungI tried to defer18:33
ayoungeverytime I think I'm out they pull.me.back.in!18:33
gyeestevemar, next topic18:33
ayoungnext topic18:33
stevemarlet's end it here and give raildo htruta and rodrigods some time18:33
marekd++18:33
breton++ next topic18:33
stevemar#topic New way to get a project scoped token by name with Reseller18:33
*** openstack changes topic to "New way to get a project scoped token by name with Reseller (Meeting topic: keystone)"18:33
htrutacool18:33
*** janonymous_ has quit IRC18:33
raildo:D18:34
*** u_glide1 has joined #openstack-meeting18:34
raildohey guys, as we had discussed last week, we created a etherpad with the alternatives to get a project scoped token by name after reseller18:34
rodrigodsso it's time to vote :)18:34
raildohttps://etherpad.openstack.org/p/reseller-project-token18:34
htrutaguess most of you guys have read the etherpad18:34
*** puranamr has quit IRC18:34
*** gokrokve has joined #openstack-meeting18:34
raildorodrigods, ++18:34
*** Sukhdev has joined #openstack-meeting18:34
raildowe decided to take a vote to choose the best option and after that we will write the spec.18:34
*** lhcheng_ has joined #openstack-meeting18:34
stevemarraildo, htruta rodrigods go over the options quickly?18:35
*** penick has joined #openstack-meeting18:35
*** VanL has joined #openstack-meeting18:35
gyeeI vote for 518:35
raildostevemar, can be18:35
htrutaok18:35
htruta(1) Specify the project hierarchy up to the domain as a string separeted by a configurable delimiter18:35
stevemaroh geez 6 options18:35
raildostevemar, sorry about that :(18:36
samueldmqgyee, ++ I kind of agree, at least for now :)18:36
dstanekgyee: +100018:36
htruta(2) Provide empty project name when intended to get a project scoped token to is_domain project.18:36
stevemareveryone take a few minutes to read the options18:36
htrutaguess I don't need to paste them all here, write?18:36
henrynashgyee: definitely disagree!18:36
raildoI don't like the 5 option too :P18:37
gyeeif we allow intermix between project and domain, I see OSSA/Ns in the future18:37
stevemarewww to 218:37
dstanekhenrynash: the problem i have is that Project<is_domain=True> should be treated like a domain and not a project518:37
gyeewe already have project/service admin bleedover18:37
henrynashno…becomes scope specifies we are looking for a project18:37
lbragstadstevemar: ++18:37
stevemari kinda like 318:37
htrutaif we choose the 5, we are not having domains as a feature of project18:38
bretonwhy do we even allow domain-scoped by name?18:38
htrutawhich is on of the main proposals of reseller18:38
*** VanL_ has quit IRC18:38
henrynashstevemar: did I hint i liked that one as ell too strongly?18:38
bknudsonthe eww factor only applies to the JSON representation. The client lib and CLI can make it look better18:38
bretonlets use uuids18:38
stevemarhenrynash, not at all18:38
henrynashbreton: we support both project and domain tokens today by name18:38
marekd3 looks more readible at hte 1st glance18:38
raildobreton, imo the best way is provide tokens by uuids, but since we provide tokens by names, we will have this issue after reseller18:39
stevemari'm thinking 3 or 518:39
bretonor make a new field, like slug.18:39
rodrigodsi dislike 3 because it Cons18:39
stevemarwhats the impact of 5?18:39
henrynashbreton: just that today they refer to seperate entites…which now get merger with “ a domain is represented as a project with teh is_domain attrbute set”18:39
htrutastevemar: I think it will make if difficult to integrate with other services18:39
gyeewe need to clearly distinguish betwen project admin, service admin, and domain admin18:39
raildostevemar, as htruta said,  we are not having domains as a feature of project18:39
bknudsonI like option 1 where the hierarchy is a list instead of a string.18:40
dstanekimo 5 keeps the domain/project dynamic much closer to what it is today and will be less confusing overall18:40
amakarov#vote 518:40
rodrigodsbknudson, bad for exporting vars18:40
htrutawe wanted to be able to treat all of them as project to make it easier to other OS services18:40
lhcheng_dstanek: ++18:40
stevemaramakarov, haven't started the vote yet :P18:40
*** vnod has quit IRC18:40
stevemarwe could use the vote to narrow down options at least18:41
dstanekif we don't do #5 i don't understand how a user know what is a domain or project and when to act is if it's either18:41
stevemarand work through the details in the spec18:41
amakarovstevemar, but you saw it :P18:41
henrynashyep, remember that one of the goals here is to allow cilents to not have to worry about domain tokens….eveything should (in the end) be project tokens18:41
gyeestevemar, or we can put +6 on a single choice :_18:41
htrutahenrynash: ++18:41
raildostevemar, and if we choose other option 1-4, we don't need, for example, provide domain scoped token to Horizon18:41
rodrigodshenrynash, ++18:41
raildohenrynash, ++18:41
henrynasha domin is just a funny kind of project that allows you to also hang users/groups off18:42
stevemareveryone ready for a vote?18:42
lhcheng_htruta: for other OS services what's the use case where they need to get domain scoped token?18:42
dstanekhenrynash: then why don't we drop support for them in general?18:42
htrutalhcheng_: they won't. they'll keep using project scoped tokens18:42
raildodstanek, it's simple, if the is_domain=True, is a project that behaviour as a domain18:42
*** crc32 has joined #openstack-meeting18:43
henrynashdstanek: I think we are headed taht way…we are basically frezzingthe domain API and ding evyerting via teh project APi now18:43
gyeesecurity guys don't like ambiguity18:43
dstanekraildo: what does that mean tho? what is the behavior?18:43
henrynashdtsanek: e.g. you can create a “domain” with create_project if the attribute is_domain=True in the entity you apss in18:43
raildoas a domain works today... create user, groups...18:43
dstanekhenrynash: i still don't get why we allow projects to have a parent that is not is_domain=True18:43
rodrigodsgyee, we intend to drop the ambiguity in the future18:44
*** wojdev has joined #openstack-meeting18:44
lhcheng_htruta: if other services won't use it, we're not making it easier for anyone. since no services is really going to use it. we might be just making it complicated.18:44
henrynashdstanek: you mean project hierachy below a “domain”?18:44
dstanekhenrynash: yes18:44
samueldmqlhcheng_, how does horizon do to create users ? what token does it use ?18:44
*** b3nt_pin is now known as beagles18:45
henrynashdstanek: that’s so complex environemtn can model there projects better (and do thinsg like quotas that role up a tree etc,)18:45
lhcheng_samueldmq: project token, horizon still doesn't support domain scoped token.18:45
htrutalhcheng_: they do not use today and we are not making them use in the future. we're just ensuring that they cant handle the whole hierarchy, without even knowing what a domain is18:45
htrutathey can**18:45
dstanekhenrynash: it seems that the model would be much simpler to say a project's parent must alwasy be is_domain=True18:46
lhcheng_samueldmq: still wip, because horizon have some issue consuming the keystone v3 policy files.18:46
gyeefunny project versus project is ambiguity18:46
*** fzdarsky has quit IRC18:46
henrynashdtsanek: which is basically the model we have before any of the projec hierachy stuff arrived….!18:46
bknudsonlhcheng_: all policy files are v3.18:46
dstanekgyee: ++ exactly18:46
rodrigodsshould we vote?18:46
dstanekhenrynash: not true...you couldn't nest domains right?18:47
henrynashbkundson: ++ ( I rue the date I named that sampel file the way I did!)18:47
henrynashdstanake: nope18:47
*** e0ne has joined #openstack-meeting18:47
henrynashdstanek: all domains are at the top, each has a flat layer of projects….that was the original (pre-hierarchy) sitaution18:47
stevemarvote time18:47
htrutadstanek, henrynash, actually, you can18:47
lhcheng_bknudson:  our default policy is not domain aware.18:47
dstanekhenrynash: to me a easier model for this would be a filesystem - directories(domain) contain other directories and files(projects)18:48
htrutayou'll be able to, in reseller18:48
henrynashhruta: NOW you can yes, but not befor we had hieracrchys18:48
stevemar#startvote option for getting a project scoped token? 1, 2, 3, 4, 5, 618:48
openstackBegin voting on: option for getting a project scoped token? Valid vote options are 1, 2, 3, 4, 5, 6.18:48
openstackVote using '#vote OPTION'. Only your last vote counts.18:48
stevemar#link https://etherpad.openstack.org/p/reseller-project-token18:49
bknudson#vote 118:49
gyee#vote 518:49
dstanek#vote 518:49
henrynashdtsanek: (I did actually argue for that when hieracrhies came in.. that acyuallywhat we ewanted was domain hieracries not project hierachies)18:49
amakarov#vote 518:49
lbragstad#vote 518:49
raildo#vote 318:49
htruta#vote 318:49
henrynash#vote 318:49
iurygregory#vote 318:49
stevemar#vote 318:49
marekd#vote 318:49
rodrigods#vote 318:49
*** amotoki has quit IRC18:49
*** jaredrohe_ has joined #openstack-meeting18:49
lhcheng_#vote 518:49
dstanekhenrynash: ++ yep18:49
david8hu#vote 518:49
stevemar#showvote18:49
openstack1 (1): bknudson18:49
openstack3 (7): rodrigods, marekd, iurygregory, htruta, henrynash, raildo, stevemar18:49
openstack5 (6): gyee, dstanek, lbragstad, david8hu, amakarov, lhcheng_18:49
haneef #vote 518:49
*** jwcroppe has joined #openstack-meeting18:49
stevemaryou had to tie things up haneef !18:49
henrynashouch!18:49
stevemar#showvote18:50
openstack1 (1): bknudson18:50
openstack3 (7): rodrigods, marekd, iurygregory, htruta, henrynash, raildo, stevemar18:50
lhcheng_haneef for the tie18:50
openstack5 (6): gyee, dstanek, lbragstad, david8hu, amakarov, lhcheng_18:50
gyeek, no run-away ehre18:50
*** spredzy|afk is now known as spredzy18:50
stevemarhaneef, can you vote again, without a leading space :)18:50
haneef#vote 518:50
rodrigodsbknudson, change to 3? :)18:50
stevemarthx!18:50
stevemar#showvote18:50
openstack1 (1): bknudson18:50
openstack3 (7): rodrigods, marekd, iurygregory, htruta, henrynash, raildo, stevemar18:50
raildohaha18:50
openstack5 (7): gyee, dstanek, haneef, lbragstad, david8hu, amakarov, lhcheng_18:50
dstanekdumb question about #3.... are all domain names unique?18:50
raildodstanek, yes18:50
rodrigodsdstanek, yes18:50
htrutadstanek: yes, they are18:50
*** weshay has quit IRC18:50
htrutanot only in 3, btw :P18:51
dstanekhow do we enforce that?18:51
stevemarin the backends i believe18:51
*** jruano has joined #openstack-meeting18:51
henrynashdtsanek, stevemar: yes18:51
dstanekbummer :-(18:51
lbragstadabout 9 minutes remaining18:51
*** ijw has joined #openstack-meeting18:52
*** AJaeger has joined #openstack-meeting18:52
stevemarso i'm ending the vote here, raildo rodrigods htruta take the 2 options going forward and present them in the spec18:52
*** lhcheng_ is now known as lhcheng18:52
stevemar#endvote18:52
openstackVoted on "option for getting a project scoped token?" Results are18:52
openstack1 (1): bknudson18:52
openstack3 (7): rodrigods, marekd, iurygregory, htruta, henrynash, raildo, stevemar18:52
openstack5 (7): gyee, dstanek, haneef, lbragstad, david8hu, amakarov, lhcheng_18:52
stevemarthanks guys18:52
raildook, thank you guys :)18:52
henrynashstevemar: ++ it’s too close to call just here18:52
stevemarreally quickly going to gyee18:52
stevemar#topic Should Endpoint Constraint Enforcement be its own middleware, or not?18:52
*** openstack changes topic to "Should Endpoint Constraint Enforcement be its own middleware, or not? (Meeting topic: keystone)"18:52
rodrigodsthanks guys18:53
marekd++18:53
gyeestevemar, I need jamielennox on this one since he's the only one wants it to be a separate middleware18:53
gyeeI guess I can play this out in ML?18:53
stevemareducate us us for 2 minutes?18:53
gyeeyou guys have any strong opinion on this one?18:53
stevemartheres also this: https://review.openstack.org/#/c/177661/18:54
gyeebasically for endpoint enforcement, it is currently part of auth_token middleware18:54
*** _amrith_ is now known as amrith18:54
samueldmqgyee, I kind of agree with him ... auth_token should only be doing what it is supposed to do (validte tokens)18:54
ayounggyee current thought make it its own middleware18:54
ayoungand it shoudlbe for enforcing policy18:54
samueldmqgyee, anything different should go in a separate middleware18:54
gyeearguments for it were 1) it should be part of "token validation", and 2) it is less disruptive for CMS18:54
*** bswartz has joined #openstack-meeting18:55
gyeeayoung, right, I had it as separate middleware at the beginning18:55
ayoungbut...morgan was the one that wanted it unified18:55
ayoungand we can;t make that call without him18:55
gyeeyou and morganfainberg convinced me to merge it with auth_token18:55
ayounggyee, and you are OK with either approach, and really, so am I18:55
gyeeI am happy to separate it out again18:55
stevemargyee, prisoner to the whims of the ptl18:56
gyeestevemar, :)18:56
ayoungactually, who said split it besides Jamie?18:56
ayoungI'm a pushover here..I just want progress18:56
gyeeayoung, Jamie so far18:56
bknudsonwhat's the argument against splitting it?18:56
ayoungput it to a vote, understanding that PTL would vote unified18:56
dstaneki don't see the value of splitting it out18:56
gyeebknudson, 1) it should be part of "token validation", and 2) it is less disruptive for CMS18:57
*** iurygregory has left #openstack-meeting18:57
*** ociuhandu has joined #openstack-meeting18:57
stevemarbknudson, "endpoint/global policy enforcement is really part of "token validation""18:57
ayoungreview link?18:57
stevemarhttps://review.openstack.org/#/c/177661/18:57
gyeeyay! lets vote18:57
*** yolanda has joined #openstack-meeting18:57
gyeefrankly, I'm going with my magic 8 ball on this one18:57
ayoungjamie's vote and morgan's will cancel out, I think18:57
stevemarwe'll let morgan decide this one when he's back18:57
ayoungstevemar, put it up for vote, please?18:57
ayoungstevemar, let's have the vote for him anyway18:58
gyeeoh com'on, we want democracy!18:58
gyeewe want freedom!18:58
gyeevote damit!18:58
marekd"money for nothing, chick for free"18:58
marekdchicks18:58
bknudsonthis is why canada still has a queen18:58
marekd:D18:58
stevemar#startvote should endpoint enforcement be it's own middleware? yes, no18:58
openstackBegin voting on: should endpoint enforcement be it's own middleware? Valid vote options are yes, no.18:58
openstackVote using '#vote OPTION'. Only your last vote counts.18:58
stevemarfastest vote ever18:58
*** pabelanger has joined #openstack-meeting18:58
ayoung#vote no18:58
gyee#vote no18:58
dstanek#vote no18:59
bknudson#vote no18:59
henrynash#vote no18:59
marekd#vote no18:59
lbragstad#vote no18:59
lhcheng#vote no18:59
stevemar#vote no18:59
samueldmq#vote maybe ?18:59
openstacksamueldmq: maybe ? is not a valid option. Valid options are yes, no.18:59
bknudsonjamie will probably just put it in its own middleware later anyways18:59
david8hu#vote no18:59
ayoungsamueldmq, just abstain18:59
lbragstadbknudson: ++18:59
stevemarlol18:59
morganfainberg#vote really?we'rehavingthisvote?causeit'sillytobeseparatefromvalidation18:59
openstackmorganfainberg: really?we'rehavingthisvote?causeit'sillytobeseparatefromvalidation is not a valid option. Valid options are yes, no.18:59
stevemar#endvote18:59
openstackVoted on "should endpoint enforcement be it's own middleware?" Results are18:59
openstackno (10): gyee, dstanek, ayoung, lhcheng, bknudson, marekd, lbragstad, david8hu, henrynash, stevemar18:59
stevemarwe're at time18:59
gyeewow, its unanimous18:59
lbragstadthanks all!18:59
stevemarthanks all!18:59
marekdo\19:00
henrynashoh boy19:00
ayoungwe'll count it as 11 nos, 1 yes19:00
ayoungcuz morganfainberg should have voted, but hey19:00
stevemarsorry jamie :(19:00
*** fzdarsky has joined #openstack-meeting19:00
stevemarayoung, its in the minutes :P19:00
morganfainbergayoung: what you didn't see my vote?19:00
morganfainberg:P19:00
*** ianw has joined #openstack-meeting19:00
*** Sam-I-Am has joined #openstack-meeting19:00
stevemar#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Jun 16 19:00:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-06-16-18.01.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-06-16-18.01.txt19:00
stevemaroops, forgot to end19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-06-16-18.01.log.html19:00
*** browne has left #openstack-meeting19:00
david8huadios19:00
*** Ng has joined #openstack-meeting19:01
* fungi smells a wumpus^H^H^H^H^H^Hinfra meeting19:01
*** lhcheng has left #openstack-meeting19:01
nibalizerwoo meeting19:01
*** mrunge_ has joined #openstack-meeting19:01
tarono/19:01
*** gokrokve has quit IRC19:01
crinkleo/19:01
pabelangero/19:02
cody-somerville\o19:02
jeblairor we could just go back to the other channel and talk about czech beer19:02
AJaegerHi infra!19:02
anteayathat too19:02
mrmartinPilsner?19:02
AJaegerjeblair: and German one, please ;)19:02
*** gokrokve has joined #openstack-meeting19:02
pleia2o/19:02
yolandao/19:02
jeblairwe could talk about which is better!  ;)19:02
jeblair#startmeeting infra19:02
openstackMeeting started Tue Jun 16 19:02:51 2015 UTC and is due to finish in 60 minutes.  The chair is jeblair. 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
mrmartino/19:02
openstackThe meeting name has been set to 'infra'19:02
yolandao/19:02
jheskethMorning19:03
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
*** mrunge_ has quit IRC19:03
cody-somerville\o19:03
ianwo/19:03
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-06-09-19.01.html19:03
mmedvedeo/19:03
ociuhanduo/19:03
krtayloro/19:03
asselino/19:03
u_glide1hello infra!19:03
bswartzhi19:03
SpamapSo/19:03
jeblair#topic Specs approval19:03
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:03
*** Sam-I-Am has left #openstack-meeting19:03
jeblairwe approved some specs last week:19:03
jeblair#topic Specs approval: Shade (mordred)19:03
jeblair#link shade spec http://specs.openstack.org/openstack-infra/infra-specs/specs/shade.html19:03
jeblair#info shade spec was approved19:03
*** openstack changes topic to "Specs approval: Shade (mordred) (Meeting topic: infra)"19:03
*** wojdev has quit IRC19:03
jeblairwith that we've documented the project direction for shade19:04
*** amakarov is now known as amakarov_away19:04
jeblairand i have added SpamapS and Shrews (who is not here) to shade-core19:04
mordredyay!19:04
SpamapS\o/19:04
pleia2great19:04
nibalizeryay19:05
jeblair#topic Specs approval: Puppet apply (mordred)19:05
jeblair#link puppet apply spec http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html19:05
jeblair#info puppet apply spec was approved19:05
*** openstack changes topic to "Specs approval: Puppet apply (mordred) (Meeting topic: infra)"19:05
jeblair(i don't have anything to say about this, though i feel positively about it)19:05
pabelangerI am excited!19:05
mordredyay!19:05
pabelangerlooking forward to ansible launcher19:05
*** mrunge has quit IRC19:06
mordredme too19:06
*** yamahata has quit IRC19:06
jeblairthis isn't actually assigned to anyone, though i think we all actually expect/believe that mordred is/will be working on it19:06
yolandai'd love to see puppet apply come to life19:06
yolandaand get rid of puppetmasters19:06
anteayaI think he will think about it from time to time19:06
pabelangerI plan to shadow development, i have a hack going local already :)19:07
*** gokrokve has quit IRC19:07
*** Shrews has joined #openstack-meeting19:07
jeblairpabelanger: so maybe you and mordred should chat when mordred is on a higher-bandwidth device19:07
jeblair(i believe he's currently on a phone in a cab)19:07
pabelangerjeblair, I don't have an issue with that19:07
nibalizerI assume we will also be quick adopters of that effort19:08
jeblairoh, i am mistaken, this is assigned to mordred and nibalizer19:08
fungiyeah, that's why i didn't council +1 it. was uncomfortable with the idea of an approved spec with no assignee19:08
jeblairsorry about that, it's the next one that's unassigned19:08
yolandanibalizer, yes, we need to be19:08
fungithe next one, right19:08
mordredI am arriving at the tel Aviv airport in fact19:08
pabelangerI'd actually like to see it as its own playbook but that is just me19:08
jeblairpabelanger: so talk to mordred + nibalizer if you want to pitch in19:08
pabelanger(the launcher part)19:08
mordredpabelanger: ++19:08
mordredI agree19:08
*** puranamr has joined #openstack-meeting19:09
*** earlephilhower has quit IRC19:09
jeblair#topic Specs approval: Puppet 4 preparation and testing (mordred)19:09
jeblair#link puppet4 testing spec http://specs.openstack.org/openstack-infra/infra-specs/specs/puppet_4_prelim_testing.html19:09
jeblair#info puppet4 testing spec was approved19:09
pabelangerjeblair, will do19:09
*** openstack changes topic to "Specs approval: Puppet 4 preparation and testing (mordred) (Meeting topic: infra)"19:09
mordredyay19:09
jeblairokay, so _this_ is the one with no assignee19:09
nibalizeryay testing19:09
jeblairfungi: i sympathize with your concern...19:09
fungiright, i was cool with the spec as written, but abstained from the vote19:09
mordredI will not do much on this one any time soon19:10
jeblairi think we certainly won't approve a priority effort spec without a point person19:10
mordredwould love a human intetested19:10
mordred++19:10
*** bhunter71 has joined #openstack-meeting19:10
jeblairi'm sort of ambivalent otherwise...19:10
*** B1xanTium0l3 has joined #openstack-meeting19:10
jeblairthis does seem like something that someone new to the project might be able to pick up and help on19:10
jeblairso it seemed like it might be worth having it written and approved19:11
fungi"low-hanging spec"19:11
crinklei can work on this19:11
* taron is curious, but doesn't have a good idea of what puppet testing even looks like19:11
jeblairat any rate, maybe we avoid making policy for now; play it by ear, and see what happens?19:11
mordred++19:11
fungishould be fine19:11
anteayataron: figure out puppet first before you commit to testing19:11
jeblairbut also keep fungi's concern in mind and not go crazy with the non-assignee specs19:11
jeblaircrinkle: and that's cool :)19:11
jeblair#topic Specs approval: Maniphest bug tracking (mordred)19:12
jeblair#link maniphest spec http://specs.openstack.org/openstack-infra/infra-specs/specs/maniphest.html19:12
jeblair#info maniphest spec was approved19:12
*** openstack changes topic to "Specs approval: Maniphest bug tracking (mordred) (Meeting topic: infra)"19:12
fungiwell, after taron finishes the code search spec, that should provide ample introduction to puppet19:12
jeblairfungi, taron: ++19:12
anteayacool19:12
mordredyay19:12
pleia2fungi: nods19:12
jeblairi find that i would really like to use this asap for infra-cloud work19:13
anteayadidn't zaro say he would look into standing one up?19:13
*** sdake_ is now known as sdake19:13
jeblairwell, mordred has a lot of work in progress/nearly completed on it19:14
anteayaah great19:14
fungiwell, there is a demo one already running, but... yeah having one spun up from the puppet module would be swell19:14
funginot sure what it's present status is19:14
jeblairat any rate, i'm highly motivated to review its patches.  just throwin' that out there.  ;)19:14
pabelangerfungi, I don't mind firing up a puppet module, if one needs to be done19:15
*** sdake has quit IRC19:15
*** cdub has quit IRC19:15
jeblairwe have a puppet-phabricator module19:15
*** sdake has joined #openstack-meeting19:15
pabelangerright, I meant testing / debuging locally19:16
pabelangermy bad19:16
jeblairah ok19:16
mordredI am happy to work in it tomorrow with someone19:16
*** Rockyg has joined #openstack-meeting19:16
mordredit's ready for next steps19:16
*** arunrajan has joined #openstack-meeting19:16
jeblairw00t19:16
mordredand I'm home tomorrow19:17
jeblaireven more w00ty19:17
mordredso I can work19:17
jeblair#topic Specs approval: Puppet Functional Testing (nibalizer, crinkle)19:17
jeblair#link puppet functional testing spec http://specs.openstack.org/openstack-infra/infra-specs/specs/puppet-module-functional-testing.html19:17
jeblair#info puppet functional testing spec was approved19:17
*** openstack changes topic to "Specs approval: Puppet Functional Testing (nibalizer, crinkle) (Meeting topic: infra)"19:17
lifelesss/work/review/19:17
* mordred hands lifeless a somewhat unused entrecôte19:18
*** achanda has quit IRC19:18
jeblairi think our first stab at this with puppet-openstackci is about ready to land19:18
*** dpaterson has joined #openstack-meeting19:18
*** jruano has quit IRC19:18
nibalizeryea19:18
jeblaircould probably use another review19:18
mordred!!! yay!19:18
openstackmordred: Error: "!!" is not a valid command.19:18
mordredaw19:18
*** pnavarro has joined #openstack-meeting19:18
jeblair#topic Specs approval: Host a code search service (taron, fungi, pleia2)19:19
jeblair#link code search spec http://specs.openstack.org/openstack-infra/infra-specs/specs/code-search.html19:19
jeblair#info code search spec was approved19:19
*** openstack changes topic to "Specs approval: Host a code search service (taron, fungi, pleia2) (Meeting topic: infra)"19:19
nibalizerwe have some work to do around fully integrating zuul/zuul-cloner but I think jeblair is saying we can patch that in a bit later19:19
fungii gather taron will be freed up from classes to work on this in another couple weeks19:19
mordredyay19:19
fungijust wanted to make sure we had some good guidance in place for the project19:20
funginot sure there's anything else to add at this stage19:20
pleia2I think that's it, she knows were to find us :)19:20
fungibesides thanks taron!19:20
jeblairawesome, so we should not expect this to start in earnest for a little bit19:20
* taron is free of it now, digging into go portions this week19:20
jeblairoh even better!19:21
fungioh! right, there was some upstream fixing/triage to do as part of it19:21
fungianyway, ask questions in irc, point us at changes to review when it gets to that point19:21
pleia2++19:21
taronwill do19:21
jeblairwe don't have any new specs ready for voting this week; but that's okay, last week will keep us busy for a while.19:22
mordreduhm, yeah19:22
jeblair#topic Schedule Project Renames19:22
fungithere are some administrivia cleanup patches to existing specs which i'm unclear how those are handled19:22
*** openstack changes topic to "Schedule Project Renames (Meeting topic: infra)"19:22
jeblairfungi: oh, yeah, er, poke me for aprv if i get behind?19:22
jeblairwe're definitely not going to vote on them formally or anything19:22
fungijeblair: i'll take a look through them later today19:22
fungiwe renamed some stuff, boy howdy19:23
*** breton has left #openstack-meeting19:23
mordredmad props to fungi and jeblair19:23
*** novas0x2a|laptop has joined #openstack-meeting19:23
fungithough keystone already has a new rename on the way19:24
AJaegerfungi, jeblair, anteaya: Thanks for those renames!19:24
pleia2yeah, nice work guys19:24
jeblairrelated to this, i have proposed https://review.openstack.org/19201619:24
jeblairprobably could have gotten its own agenda item...19:24
pleia2it's been an interesting discussion so far19:25
jeblairbut anyway, it's exploring the idea that there's not much difference between stackforge and big-tent-openstack, and we should retire the use of stackforge in favor of just having projects be in openstack19:25
jeblairmostly, i want us to stop renaming projects as part of their development lifecycle because that just seems crazy to me19:25
*** harlowja has quit IRC19:25
bswartz+119:26
jeblairnot sure where it's going to go, but other options have been thrown out as well, such as "provisinal use of openstack namespace" etc19:26
mordred++19:26
mordredI support our non rename overlords19:26
jeblairso i'm hoping that regardless of what final form it takes, we can stop renaming projects unless, you know, they need to be _renamed_ :)19:26
fungiper my review comment, i'd also love for this to provide additional impetus for clearing up the cla situation19:26
mordred++19:27
*** balajiiyer has joined #openstack-meeting19:27
jeblairfungi: yeah, considering we have "official" projects in infra without a cla, that's also weird.19:27
*** scinawa has joined #openstack-meeting19:28
fungiagreed19:28
jeblairanyway... er, we talked about shade-core membership already, so...19:28
jeblair#topic Hosting for Manila service image (u_glide, bswartz)19:28
*** openstack changes topic to "Hosting for Manila service image (u_glide, bswartz) (Meeting topic: infra)"19:28
bswartzu_glide1: ping19:29
u_glide1Hello folks!19:29
u_glide1I'm core team member of Manila project. We  have created new sub-project manila-image-elements which produces a binary image in qcow2 format. This image is used by our devstack plugin and we need to host this image somehow. Is it possible to host this image as regular release on http://tarballs.openstack.org/ ? And does it have enough bandwidth?19:29
jeblairHello u_glide1!19:29
*** otter768 has joined #openstack-meeting19:29
jeblairi think/hope the answer to all is yes19:30
fungithis seems like the agent images we already build and host for... is it ironic?19:30
fungitrove?19:30
mordredyup19:30
fungiboth?19:30
bswartzis there an example of how others do this that we can simply copy?19:30
jeblairso yes, there are some jobs already that publish images to tarballs.o.o.  i think they are post jobs?19:30
* SpamapS is having de ja vu19:30
jeblairthen we would want to get that image listed in devstack so that it is cached on our build nodes19:30
fungiSpamapS may be well-placed to provide guidance here too ;)19:31
AJaegeru_glide1: see jenkins/jobs/trove.yaml in project-config19:31
jeblairthat means that we wouldn't have to download it every time (but our images only update once per day)19:31
*** yamamoto has joined #openstack-meeting19:31
u_glide1AJaeger: thanks, looking19:31
bswartzjeblair: caching sounds like an excellent idea19:31
fungithe middle ground is that devstack can perhaps download if what's hosted is newer than what's cached19:32
SpamapSIt's probably worth seeing if the method devstack uses to download the image supports If-Modified-Since.19:32
jeblairfungi: yeah (though that works better if it doesn't update too often)19:32
u_glide1jeblair: caching +10019:33
fungiso you get the extra download overhead until the next worker image update happens in nodepool, allowing you to fix blocking bugs in your jobs that might depend on an updated image19:33
SpamapSI presume our static hosting site would respond appropriately.19:33
bswartzthe qcow2 would be updated for every commit to the manila-image-elements project, but commits would be hopefully rare19:33
jeblair(as a side note, i believe the list of images to cache should end up moving into DIB in project-config soonish; devstack is not really the right place anymore)19:33
*** puranamr has quit IRC19:33
jeblair(but it's still currently devstack)19:33
jeblairbswartz, fungi: that sounds reasonable19:33
fungiSpamapS: our static hosting site is currently filesystem-backed apache, so yes. eventually swift with some cdn, but probably still yes in that case?19:33
SpamapSagree, dib's caching is pretty strong on this front too.19:34
SpamapSfungi: CDN will definitely support IMS19:34
*** otter768 has quit IRC19:34
SpamapSI kind fo hope swift does.19:34
fungii kind of would be surprised if it doesn't19:34
fungifor very large values of "kind of"19:34
SpamapSso anyway, it sounds like its more important that it find its way into the images19:35
jeblairoh, also, how large is it?19:35
SpamapSu_glide1: ^ what he said.19:35
bswartz~300MB?19:35
u_glide1300 Mb19:36
bswartzthere's an effort to make it smaller but that's what it is right now19:36
*** yamamoto has quit IRC19:36
jeblairwe are getting closser and closer to hitting the limit with this methodology; we may have to eventually switch to using per-region mirrors and _not_ local image caching.19:36
fungithat's not too much larger than http://tarballs.openstack.org/ironic-python-agent/coreos/19:37
jeblair(or at least, anything < X MB gets cached, anything larger gets on the per-region mirror)19:37
fungibut yeah, death by a thousand cuts19:37
zaroo/19:37
*** eghobo has joined #openstack-meeting19:37
jeblairu_glide1, bswartz: does that cover your questions?19:37
fungiespecially when some of our providers now only give us a 20gb filesystem19:37
SpamapSI dunno19:38
u_glide1yes, seems that we just should copy trove project config and that's it :)19:38
mordredjeblair: ++ to large in per region mirrors19:38
SpamapSI think glance and nova-compute will be more efficient at spraying bits onto compute nodes than local mirrors and vms will.19:38
*** sankarshan_ is now known as sankarshan_away19:38
SpamapSThere may be some cognitive overhead in the image approach that I'm missing though.19:38
u_glide1thanks a lot guys!19:38
bswartzyes19:39
bswartzty19:39
jeblairSpamapS: definitely, but we're running out of space on the dsvm images we create19:39
jeblairbswartz, u_glide1: you're welcome.  thanks for asking.  :)19:39
*** _nadya_ has joined #openstack-meeting19:39
mordredSpamapS: small disk on flavors19:39
SpamapSjeblair: right, and as I think about it, the hit rate doesn't go up with more cached things, just the breadth of things that can be serviced, so I think the mirror approach does make more sense as we add more things.19:39
mordredyah19:40
jeblairSpamapS: yep, and hopefully we can drive frequent jobs to use things that are cached19:40
jeblair(i'm certain we can continue to cache cirros)19:40
*** rrrobbb has quit IRC19:41
mordreddo I invoke Andrew's law if I say afs?19:41
fungigood point. having stats on what we mirror to tell us what's heavily used can provide us guidance on what to switch to local caches19:41
mordredfungi: ++19:41
jeblairmordred: i thought 'per-region mirror' was spelled 'afs'19:41
mordredjeblair: :)19:41
*** changbl has quit IRC19:41
jeblair#topic Mid-cycle (virtual) meetup (pabelanger)19:41
*** openstack changes topic to "Mid-cycle (virtual) meetup (pabelanger) (Meeting topic: infra)"19:41
* krotscheck makes a note to have everything javascript be spelled "AFS"19:41
fungiyeah, there's definitely no reason why a static file mirror shouldn't just be an afs volume mounted on the workers19:42
pabelangermostly a simple question, if there is any need or upcoming mid-cycle meeting.19:42
pabelangertravel requests are being asked for19:42
jeblairi've heard some good suggestions for things we might do that could reasonably benefit from in-person time: 1) hack on infra-cloud;  2) zuulv3.19:42
jeblairas far as zuulv3 goes, i haven't gotten the spec in shape to be approved yet.19:43
jeblairi mean, i'm optimistic and all, and i expect to do that this week.  but that's just where we are.19:43
timrc_I would be supportive of a mid-cycle for zuul v3 hackery.19:43
cody-somervilleI'm very interested in hacking on improving CI/CD of infra itself.19:43
fungipeople _seem_ to be progressing on infra-cloud without being in the same room19:44
jeblairi personally don't want to travel just for the sake of it, so i'd set a pretty high bar for what we want to do and why we need to be in person19:44
pleia2my summer is largely spoken for already19:44
pabelangerjeblair, right. I agree with that19:44
jeblair(my productivity drops when i travel)19:44
fungii'm buying a house, and i expect that to make travel i haven't planned for yet a little more of a stretch for me19:44
jeblairi'm also a big fan of virtual sprints19:45
pleia2our team manages to do a good job with virtual sprints19:45
fungii assume zuul v3 will progress pretty steadily once there's a spec formalized too19:45
fungiin-person sprint or no19:45
jeblairi feel like we've had some good face-time with infra-cloud that put us in a good place to proceed offline for a while19:45
*** devkulkarni has joined #openstack-meeting19:45
*** jgrimm is now known as zz_jgrimm19:46
jeblairand i lean toward saying we should not plan on meeting just for that, at least, unless we find it going off into the weeds and we need to redesign something to get it back on track19:46
pleia2most of the key folks on infra-cloud are on the west coast, might be easier just to gather the few of us for a few days here than a larger infra meeting19:46
*** changbl has joined #openstack-meeting19:46
jeblairbut for the moment, we've got a roadmap and we just need to move19:46
pleia2but I don't strictly see it as required right now19:46
SpamapSjeblair: concur that we have plenty to do that is clear and actionable offline on infra-cloud.19:47
jeblairjhesketh was around earlier, but i don't see him now.  i'll try to speak for him and say that getting together lets us overcome the timezone difficulty.19:47
jheskethI'm in support of a mid cycle. It's perhaps a personal thing or maybe a time zone thing, but it's massively easier to maintain momentum working on something when you can turn to the relevant person and have them look over your shoulder19:47
jeblairoh there he is!19:47
*** tmorin has joined #openstack-meeting19:47
anteayajhesketh: hobart is an option?19:48
jeblairmaybe we should do more virtual sprints (or even mini-sprints) to help with at least the timezone part of that (if not the in-person part)19:48
jheskethSo with virtual sprints I'd like to see more hand over between timezones, but that's a tangent19:48
fungii think that's a realistic expectation19:48
pleia2jhesketh: I think that's something we can work on doing a better job of19:48
jeblair++19:48
*** kebray has quit IRC19:49
jheskethanteaya: sure, but I think it makes more sense to be closer to the majority of people to reduce costs and increase attendance19:49
anteayajhesketh: :)19:49
anteayajust love the view from your house19:49
fungiadditionally, interest more apac people in infra so jhesketh isn't as lonely ;)19:49
pabelangerjhesketh, because I don't know, which TZ (location) are you based out of?19:49
* jeblair moves west19:49
*** u_glide1 has left #openstack-meeting19:49
jheskethUtc+1019:49
anteayajeblair: you'll get wet19:49
fungijeblair: i hear french polynesia is lovely this^H^H^H^Hany time of year19:50
mrmartinand bora bora too, we have a user group there19:50
*** krtaylor has quit IRC19:50
mrmartinbut I don't know how active they are19:51
* krotscheck thinks the productivity benefit of colocation may be offset by the relaxation benefit of the location.19:51
*** david-lyle_ has joined #openstack-meeting19:51
fungithis has sort of transitioned into the next topic19:51
timrc_I'm okay with a sprint objective of margarita19:51
*** toscalix has joined #openstack-meeting19:51
jheskethI think the part lost with virtual sprints is pair programming which can be a great way of getting things done and helping each other out (not to mention learning)19:52
fungimy productivity massively increases proportional to my relaxation19:52
anteayajhesketh: you make a good point19:52
yolandajhesketh, i agree with you, the ones with different timezones have that more difficult, and sprints help with that19:52
jheskethI think there is room for both virtual and physic sprints but I have a personal preference for physical19:53
*** adrian_otto has joined #openstack-meeting19:53
ianwif you want to make it sydney, let me know and i'll get space at red hat.  good view19:53
fungiit sounds like the contributors working on specific efforts might benefit from finding somewhere mutually agreeable to get together and focus on something for a few days or a week without it needing to be an official "team" event19:54
jheskethSo even aside from timezones I've had great success working on projects face to face with teams just in Australia. It helps create a focused environment and encourage that team work19:54
krotscheckThere's specific sprint days at PyCon AU in August.19:54
jeblairfungi: that might be a bit more manageable19:54
*** VanL has quit IRC19:54
*** _nadya_ has quit IRC19:54
jheskethkrotscheck: indeed, those are great too! :-)19:54
*** B1xanTium0l3 has quit IRC19:55
fungialso, the pycon au point... if people find that they're going to be at a conference with collaborators on something, extend your stay a day or two to hack on whatever it is you're collaborating on19:55
jeblairwho's at pyconau and who's at oscon?19:55
*** mattgri__ has joined #openstack-meeting19:55
anteayahttps://etherpad.openstack.org/p/pyconau-sprints19:55
*** arunrajan has left #openstack-meeting19:55
anteaya<-- pyconau19:55
nibalizeri'll be in pdx for oscon19:55
fungii'll be at oscon and there are a couple days in there where i'm not spoken for19:55
*** david-lyle_ has quit IRC19:56
jheskethExtending on what fungi said, I think it's important for mid cycles to be very much optional19:56
crinklei'll also be in pdx for oscon19:56
jheskethI'll be at pyconau19:56
pleia2not strictly attending, but I'll be around oscon sat-tuesday (fly home wednesday afternoon)19:56
ttxI'll be in pdx for oscon too19:56
jheskethBut nothing else yet19:56
fungipleia2: aww, you won't be there for my talk! ;)19:56
jeblairpleia2: i was also considering the beer track19:56
jesusaurusi'm on the hallway track for oscon19:56
*** david-lyle_ has joined #openstack-meeting19:56
pleia2fungi: I know, sadness!19:56
fungiit's okay, i hear from the author that it'll likely be really boring19:56
pabelangerjhesketh, maybe the question is where are people going, and see what overlap there is for sprints19:56
pleia2fungi: it'll be wonderful, I am actually quite sorry to miss it19:57
*** jcoufal has joined #openstack-meeting19:57
fungii don't sell it very well19:57
*** rjaiswal has joined #openstack-meeting19:58
jeblairat any rate, it sounds like we are unlikely to have a formal general infra team meetup at this point19:58
jheskethpabelanger: sure, so long as it's a good fit and people won't be burnt out from the conference to work for a week19:58
jeblairbut keeping the door open to virtual sprints, conference overlap, and more focused events19:58
jeblair#topic  Open discussion19:58
*** Slower has left #openstack-meeting19:58
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:58
*** dpaterson has quit IRC19:58
jeblair(not that it wasn't already, but hey we have 2 mins left)19:58
*** jaredrohe_ has quit IRC19:58
*** mattgriffin has quit IRC19:59
mrmartinwhat's the status of Zanata integration?19:59
pleia2mrmartin: still hacking away at it, StevenK is working on the import scripts we'll use and I'm in the process of fixing a restart bug with our puppet module19:59
*** dpaterson has joined #openstack-meeting19:59
*** david-lyle_ has quit IRC19:59
mrmartingreat, thnx20:00
pleia2still aiming for having a test instance to the i18n team with current translations imported by early july20:00
jeblairthanks everyone!20:00
jeblair#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Jun 16 20:00:14 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-06-16-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-06-16-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-06-16-19.02.log.html20:00
jheskethThanks :-)20:00
jeblairttx: o/20:00
jaypipeso/20:00
sdagueo/20:00
flaper87o/20:00
ttxAnyone (else) here for the TC meeting ?20:00
*** julim has quit IRC20:00
devkulkarnidevkulkarni20:00
*** balajiiyer has quit IRC20:00
*** yolanda has left #openstack-meeting20:00
ttxrussellb, jgriffith, annegentle, lifeless, mordred, dtroyer, markmcclain, dhellmann: around ?20:00
markmcclaino/20:01
*** balajiiyer has joined #openstack-meeting20:01
*** datsun180b has joined #openstack-meeting20:01
ttxI know anne is not around today20:01
lifelesshai20:01
*** mattgri__ has quit IRC20:01
ttxthat makes 7, let's start this20:01
lifelessI'm here on the keyboard, can't make any assertions about mental state20:01
ttx#startmeeting tc20:02
* flaper87 hands lifeless some coffee \_/?20:02
openstackMeeting started Tue Jun 16 20:02:06 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20: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
ttxMeeting agenda for today:20:02
lifelessflaper87: child with post-tonsilectomy-pain20:02
*** krtaylor has joined #openstack-meeting20:02
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:02
*** earlephilhower has joined #openstack-meeting20:02
flaper87lifeless: :(20:02
ttx#topic Add compute starter kit tag20:02
*** openstack changes topic to "Add compute starter kit tag (Meeting topic: tc)"20:02
edleafeo/20:02
*** mattgriffin has joined #openstack-meeting20:02
ttx#link https://review.openstack.org/18011220:02
ttxsdague rewrote his proposal to clarify that it is really meant as a starter kit rather than a core / kernel / layer120:03
*** jaredroh- has joined #openstack-meeting20:03
sdaguehey, so there is a new revision out there20:03
adrian_ottottx can we add https://review.openstack.org/190949 to the agenda backlog please?20:03
ttxtwo weeks ago we agreed that the TC should have an opinion on "start here for this use case today", and I think this strikes the right wording20:03
*** _nadya_ has joined #openstack-meeting20:03
*** changbl has quit IRC20:03
ttxadrian_otto: that was on today's agenda20:03
*** MaxPC has quit IRC20:03
adrian_ottooh, sorry I missed it!20:03
ttxadrian_otto: would you prefer it not discussed today ?20:03
adrian_ottonm, I retract my request20:03
flaper87I think the wording improved a lot and it's clearer20:04
ttxOn the compute starter kit tag -- Obviously there will still be people opposed or indifferent to it, but I think we can reach a majority on this first version, and iterate on it20:04
sdaguepeople that didn't like the last one philosophically are probably not likely to like this one, however people that found confusion in the last one might hopefully find this clearer20:04
krotschecko/20:04
ttxI would be fine removing the dependency on an ops:production-ready tag, since it's a bit unlikely we'd have that anytime soon20:04
ttxBut I'd be fine with that being submitted as a subsequent change20:04
ttxI find it always easier to merge a version and iterate than try to come up with the perfect thing in one go20:04
sdaguegiven that it's a light TC week, I'd also recommend we have a discussion slice next week. With only 7 folks here it's hard to get all the thoughts on the table20:05
j^2o/20:05
flaper87yeah, that's the only reason I didn't +1 it for now20:05
zanebsdague: I think this is really moving in a better direction, I appreciate all your work on taking into account the feedback20:05
lifeless++20:06
lifelessI'm quite comfortable with it20:06
flaper87sdague: +1 on holding off until next week. That'll give folks some extra time to think this through20:06
jaypipessdague: I'd be +1 if you removed that one requirement about the production-readiness sign-off by the ops community.20:06
lifelesswe could tweak forever20:06
flaper87that said, I'm happier with this version20:06
ttxsdague: would you consider removing the dependency on an hypothetical ops production-ready tag ?20:06
flaper87and removing the production requirement would be preferable20:06
*** dpaterson has quit IRC20:06
sdaguesure, I can remove that bit20:06
jaypipessdague: it's light-years better than the original kernel:compute proposal.20:06
sdagueI'd do that post meeting20:06
jaypipessdague: excellent work on the rewrite.20:06
sdaguejaypipes: well, that's how we make the sausage20:06
zanebis there a reason for laying out the requirements at all?20:06
zaneblast time we talked about just making an opinionated decision20:07
*** baoli_ has quit IRC20:07
dhellmanno/20:07
flaper87would it be crazy to say that we could eventually have a starter_kit in devstack ? (that's pretty much what it does already, since things are being moved out to plugins)20:07
ttxsdague: frankly, we have plenty of time in this meeting, so if you want to take 5 minutes to edit it and collect +1s, that could save us a slot next week20:07
sdagueso, I feel like they inform the decision to be made. And I like why's more than just things.20:07
ttxWe have a huge backlog with stuff proposed late last week20:07
jaypipeszaneb: the requirements for the tag lay out at least a reasonable set of considerations vs. just "my opinion".20:07
*** kebray has joined #openstack-meeting20:07
flaper87I think the requirements provide some extra info on why those projects are also considered part of the starter kit20:08
ttxI like the requirements.20:08
*** rrrobbb has joined #openstack-meeting20:08
*** rrrobbb has quit IRC20:08
*** padkrish has quit IRC20:08
ttxI just feel like we won't have an ops production-ready (binary) tag anytime soon20:08
sdaguettx: well, I'd still like to leave a discussion window because we're missing half the TC, and the draft only hit yesterday20:08
jaypipesttx, flaper87: I like them as well, save for the productionness one.20:08
flaper87jaypipes: yup yup20:08
jaypipessdague: agreed20:08
*** gokrokve has joined #openstack-meeting20:08
sdagueI don't want anyone feeling like they were run over with this20:08
*** rrrobbb has joined #openstack-meeting20:08
sdaguebecause that was not the intent20:08
jaypipesright20:08
flaper87+120:09
flaper87well, early feedback from me: +120:09
ttxsdague: alright, fair enough20:09
*** henrynash has quit IRC20:09
sdagueok, well, once we get to another topic, I'll edit and update, so we'll have it before the meeting is over20:09
*** mattgriffin has quit IRC20:09
sdagueany further questions / comments?20:09
ttxok, we can come back to it and collect early votes at the end of the meeting then20:09
sdaguesounds good20:09
ttxlet's cover the other topics now20:10
ttx#topic Adding distribution packaging to OpenStack20:10
*** openstack changes topic to "Adding distribution packaging to OpenStack (Meeting topic: tc)"20:10
ttx#link https://review.openstack.org/18518720:10
ttxOn this one, I think the ones advocating for waiting for the team to form first were right20:10
*** changbl has joined #openstack-meeting20:10
ttxSince in the last two weeks, the discussion went from scoping this to RPM+DEB, to Ubuntu+Debian only, to Ubuntu jumping off the boat (yesterday)20:11
*** SlickNik has joined #openstack-meeting20:11
jaypipesjamespage: did you see my recent question to you on the ML thread about packaging? It was to inform my decision on this particular governance proposal....20:11
ttxSo this all only confirms my opinion that we should wait to first have a working, scoped team before we recognize it as an OpenStack project team.20:11
jeblairttx: or phrased another way, the folks who wanted a concrete proposal before doing anything were right :)20:11
ttxjeblair: we were both right I think20:11
flaper87agreed, I was clear last week on the intensions for this proposal but things seem to have shifted a bit20:11
lifelessttx: anything proposed late last week is not backlog20:11
lifelessttx: it becomes backlog next week20:12
jeblairat any rate, it does seem like this is losing steam20:12
ttxlifeless: anything proposed post Friday 0800 utc is backlog20:12
ttxlifeless: according to the rules we agreed on at the start of this cycle20:12
lifelessttx: I think thats too narrow to get folk form opinions20:12
dhellmannI think it would be fine if zigo wanted to put the repositories he uses for packaging up on gerrit, but I agree that we should have some team collaborating before we call them a team20:12
lifelessttx: sure, I think we made a mistake20:12
jaypipeszigo: you around?20:12
zigoHi.20:12
zigoI am.20:12
ttxlifeless: I don't get it -- want more time or less time ?20:13
zigoReading ...20:13
* jaypipes disappointed this has lost steam...20:13
lifelessttx: more, but I'm distracting from the main event.20:13
jeblairback to the issue -- i'm pretty bummed because it seems like at the summit a lot of folks thought this was a good idea20:13
zigoI think I'll use stackforge to start with.20:13
lifelessttx: so, stack.push(); packaging.discuss()20:13
jaypipesjeblair: ++ I am bummed as well.20:13
zigoThat's fine.20:13
flaper87zigo: that's a good call20:13
*** merooney has quit IRC20:14
*** eharney has quit IRC20:14
zigoSo let's put this as WIP, and revisit later, ok?20:14
ttxdhellmann: right, and FTR I'm fine with creating a bunch of repositories. But for the sake of not renaming / moving them to attic because nobody uses them, I'd rather see the discussion on the team scope continue for a bit20:14
AJaegerzigo: Or Abandon and un-abandon later ;)20:14
zigoPaul Belanger needs help anyway for packaging stuff for infra.20:14
*** krtaylor has quit IRC20:14
*** david-lyle_ has joined #openstack-meeting20:14
dhellmannttx: sure20:15
zigoSo the project needs to happen anyway.20:15
jeblairi'm not opposed to stackforge for this20:15
zigo(ie: packaging zuul + nodepool)20:15
dhellmannttx: I'll defer to jeblair on naming, since it's the infra team that has the burden of dealing with renames20:15
zigo(and others...)20:15
flaper87zigo: I think starting somewhere and working out the requirements is a good thing. It'll help building a better/stronger proposal20:15
AJaegerwe have now RDO and SUSE folks talking about this as well - there's a separate patch for that...20:15
ttxzigo: you mean that even if it's only you/Debian, you'd still do it under openstack infrastructure, right ?20:15
flaper87zigo: if there's anything we can do to help out with the organization/teams do let us know20:16
zigottx: Yes, but it may not be the way I thought to begin with.20:16
jeblair(i'm not going to be super-excited to move it, but i also don't want to get in the way of work while we figure that out)20:16
*** Shrews has left #openstack-meeting20:16
ttxzigo: me neither tbh20:16
zigottx: I'll have to think about how, and see if the team inside Mirantis wants to do it with me as well.20:16
ttxzigo: it's less compelling, but that doesn't mean it's a bad thing to have20:16
*** sdake_ has joined #openstack-meeting20:16
*** marcusvrn has quit IRC20:16
zigoWe're having a meeting at the end of the month (29th to 3rd), we'll see what comes out of the discussions in Moscow.20:17
zigobrb20:17
jeblairAJaeger: makes an interesting point -- we still have at least one .deb and two .rpm groups interested in the general concept20:18
ttxzigo: so yes you can WIP it (by prefixing the git commit title with WIP) or abandon it temporarily to get it out of the agenda until ready20:18
jeblairdo we want to ask them both to start in stackforge, or give them both provisional access to openstack/ namespace?20:18
*** julim has joined #openstack-meeting20:18
AJaegerjeblair: see https://review.openstack.org/19158720:18
zigottx: deal !20:19
*** mattgriffin has joined #openstack-meeting20:19
*** david-lyle_ has quit IRC20:19
zigoYeah, I need to know where to host stuff. /stackforge or /openstack, both is fine to me, but I'd like a definitive answer ASAP, as it's been a real blocker for nearly a month now.20:19
dhellmannjeblair: I think using the openstack/ prefix is fine in this case20:20
*** sdake has quit IRC20:20
ttxdhellmann: it will need a adopting project20:20
ttx(or be attached as a TC repo)20:20
*** ruhe has joined #openstack-meeting20:20
zigoPlease get a vote on the namespace today, so it can move forward (and again, i don't mind either ways...)20:21
ttx(I'm fine with all solutions: stackforge, openstack under TC, openstack under X)20:21
dhellmannttx: ok, I guess we're sticking to that for now? I thought we discussed the option for provisional repos.20:21
lifelessditto20:21
* AJaeger is just a bit scared of 200 repos under stackforge that in a few months will move to openstack...20:21
jeblairwhy not just approve the project with the current small team?20:21
AJaegerzigo: how large is the team? Right now it looks like it's just you, is that correct?20:22
ttxjeblair: I'm slightly worried that zigo will ragequit and not do it upstream since the others don't want to play in the same sandbox20:22
flaper87I honestly would prefer to give it some time to mature before approving the project20:22
ttxbut then we can retire the team I guess20:22
sdaguewell, do we need an update on the scope of the proposal? Maybe that becomes more clear. I think even if it's just a debian effort for some tools, doing it our collab framework is nice20:22
flaper87lets let them figure things out and come back with a stronger (or just clearer) proposal20:22
zigoAJaeger: At the end of the month, I hope it's going to be others from Mirantis too, but for the moment, yeah, just me.20:22
jeblairsdague: ++20:22
flaper87sdague: that's what I'd like to see clarified in the proposal20:23
sdagueI really don't want to do the magnum thing and have four  months of stall because of a namespace decision20:23
*** jcoufal has quit IRC20:23
sdaguebecause that's silly20:23
*** marrusl has quit IRC20:23
*** spzala has quit IRC20:23
zigoFYI, I had the project to do packaging in upstream infra since a long time ago.20:23
adrian_ottosdague: +120:23
ttxsdague: right, which is wjy I offer we create the repo anyway20:23
zigoMonty can confirm we had such a discussion back in Atlanta.20:23
zigoI *never* give-up, I'm obstinated ! :)20:24
flaper87I think having the repo as a TC (or provisional) repo is fine20:24
*** marrusl has joined #openstack-meeting20:24
flaper87The problem is not the repo/namespace (or it shouldn't be)20:24
sdagueso, here's the thing, zigo has been around for a while, and hasn't rage quit yet, even when we've given him some reasons to :)20:24
flaper87if that doesn't work out well (which I doubt), then fine20:24
ttxjeblair: prefer stackforge or openstack-provisionally-under-TC-attached-repos ?20:24
sdagueso I'm happy that if we have a more concrete and narrowly scoped proposal to put it in openstack and let it be a thing20:24
ttxsdague: yeah, me too20:24
jeblairlet's do that20:25
jaypipes++20:25
flaper87woohhhooo20:25
*** padkrish has joined #openstack-meeting20:25
fungithank you for not planning a 200+ repo rename ;)20:25
zigo\o/20:25
markmcclain+120:25
dhellmann++20:25
zigofungi: It wont be that much, I've listed about 120 only! :)20:25
ttxI'm fine with a narrowly-scoped team that says "zigo and friends will do Debian" -- I was just skeptical of "all distros will collaborate together here"20:25
sdaguezigo: ok, so by next week, please have a proposal revision20:25
fungilast weekend't 61 repo rename was plenty painful20:25
AJaegerzigo: 120 for now ;)20:25
zigofungi: And to begin with, it's going to be a lot less.20:25
* dhellmann hopes they are all named consistently20:26
zigoI'll start slowly, and see how it goes...20:26
flaper87dhellmann: ++20:26
AJaegerttx: The extra time helped to figure out that Deb + RPM really are too different for one team...20:26
flaper87zigo: updates on the progress are really appreciated20:26
jaypipes"Zigo and Friends" sounds like a new Saturday morning cartoon that would come on after Spongebob Squarepants.20:26
fungii'm not concerned by the number of repos, just needing to rename them all from stackforge to openstack at some point, so starting in openstack sounds good to me ;)20:26
jeblairzigo: talk to the rpm folks too to agree on a compatible repo naming scheme20:26
ttxzigo: if you rework your proposal while we discuss another topic, we could pick it up at the end of this meeting and collect early approvals on it20:27
zigodhellmann: It's going to be github.com/something/deb-<package-name> as per the name of packages at https://qa.debian.org/developer.php?login=openstack-devel@lists.alioth.debian.org20:27
jeblairsounds good20:27
jeblairwonder what the rpm folks use?20:27
*** krtaylor has joined #openstack-meeting20:27
dhellmannthat looks pretty clear20:27
ttxjeblair: next week topic I guess20:27
flaper87no idea20:27
*** ajmiller_ has joined #openstack-meeting20:27
*** david-lyle_ has joined #openstack-meeting20:28
AJaegerjeblair: Debian: cinder, RDO/SUSE: openstack-cinder20:28
zigoAJaeger is correct, so it wont be the same repo names.20:28
jeblairright, but will the packaging repos end up being 'rpm-openstack-cinder' or something?20:28
ttxok, let's move on and wait for the narrowly-scoped proposal to appear20:28
sdaguettx: ++20:28
ttx#topic Add Solum to OpenStack Projects List20:28
zigojeblair: I believe so.20:28
*** openstack changes topic to "Add Solum to OpenStack Projects List (Meeting topic: tc)"20:28
ttx#link https://review.openstack.org/19094920:28
ttxHad two questions, posted them on the review20:29
ttx1/ I had the impression this was slowly losing steam, I guess mostly because I saw Adran focused on Magnum and dual-PTLing20:29
adrian_ottojogo had raised a concern about IRC logging. The channel has been logged since day one in 2013 at https://botbot.me/freenode/solum/ and the meeting topic announces that.20:29
sdaguefyi - https://review.openstack.org/#/c/180112/5 is revised (the compute starter kit update with production ready removed and typos fixed)20:29
jeblairadrian_otto: it would be good to add solum to the openstack irc bots20:29
ttxsdague: will pick it up at eom20:30
adrian_ottottx, the developer activity level is healty, but the externally visible PTL outputs are lower because of split focus.20:30
dhellmannadrian_otto: do you object to having it logged along with the other openstack channels?20:30
adrian_ottodhellmann: not at all,20:30
adrian_ottoI'm happy to switch it20:30
*** rossella_s has quit IRC20:30
ttxadrian_otto: do you have plans for succesion planning ?20:30
*** radek_ has quit IRC20:30
dhellmannI wouldn't mind both, but adding openstack is a pre-req20:30
lifelessttx: did you just ask for plans about plans...20:30
*** Ng has left #openstack-meeting20:30
lifelessttx: METAPLAN20:30
ttxlifeless: maybe it's early for you, but here it's late !20:31
sdagueon the solum thing, the only thing that stuck out to me was I wonder if we have a diverse_team:danger_will_robinson tag, because stackalytics for liberty is ... pretty mono culture20:31
*** rossella_s has joined #openstack-meeting20:31
lifelessttx: oh its late for my brain today. CANNOT BRAIN20:31
adrian_ottoyes, I plan to serve the current term through Liberty, and we can welcome a new leader at the next election if I need to continue focusing on Magnum20:31
jeblairoh, i think we're only missing eavesdrop; the other bots are there20:31
*** ajmiller has quit IRC20:31
jeblairwon't be a problem.20:31
ttx2/ I still have qualms about squarely adding a PaaS project to OpenStack, big tent or not20:31
j^2I’d like to say that I’ve always like the project Solum, i just wish it got more development and eyes on20:31
adrian_ottoor we can transplant the role to a successor if the team feels they need it20:31
ttxbut I think I may be in minority there20:31
dougwigadrian_otto: just have people go all game of thrones over the position.20:31
*** mattgriffin has quit IRC20:32
sdaguettx: yeh, for me, scope is not a concern, if there are people working on it20:32
adrian_ottodougwig: ;-)20:32
sdagueit feels cloud scope, even if it's at the top end of our current function stack20:32
datsun180bso which one of us is Stannis?20:32
ttxsdague: right, fits the "vaguely related to openstack mission" enough20:32
dhellmannsdague: I concur with the diversity concern, but we've removed that requirement for new projects20:32
sdaguedhellmann: right, we've removed it, I just wonder if we should have a 3rd tier in our tag20:33
*** tsekiyam_ has joined #openstack-meeting20:33
sdaguewhere something is over 90% a single org20:33
datsun180bwe've (read: adrian) has been working hard to clean up our tasks and make it easier to see what is a ground-floor bug and what isn't in LP20:33
ttxdhellmann, sdague: about the diversity:danger, I think it's more a data point that the project is losing steam, rather than a reason for exclusion20:33
*** tsekiyam_ has quit IRC20:33
dhellmannsdague: ah, like an explicit "not diverse" tag?20:33
*** sudipto has quit IRC20:33
sdaguebecause that's a very dangerous place for a project to be20:33
sdaguedhellmann: yeh20:33
ttxhence my question20:33
*** puranamr has joined #openstack-meeting20:34
dhellmannyes, not so many commits this cycle, either20:34
*** Sukhdev has quit IRC20:34
*** ijw has quit IRC20:34
adrian_ottodhellmann: we productized it20:34
zanebhttp://stackalytics.com/?project_type=stackforge&module=solum-group&metric=commits&release=kilo <- so this is probably the relevant graph to look at20:34
ttxadrian_otto: would you say the project is rackspace-only at this point ? or it's just an unfortunate stats for start-of-liberty that shall correct itself ?20:34
*** padkrish has quit IRC20:34
dhellmannadrian_otto: I'm not sure what you mean by that20:34
adrian_ottoso it's now the basis of a production cloud service that's coming to market20:34
flaper87adrian_otto: do you think the above is something that'll change later this cycle?20:34
*** _nadya_ has quit IRC20:35
sdaguettx: right, again, I wouldn't exclude solum for that. But I'd like it to trigger a conversation about 3rd tag state on diversity20:35
adrian_ottoso the activity level needed to integrate it with a public cloud will be redirected back upstream post launch20:35
flaper87fungi: has 5 commits there20:35
adrian_ottosince that work is done20:35
*** ijw has joined #openstack-meeting20:35
jeblairfungi is a machine.20:35
flaper87jeblair: ++20:35
*** VanL has joined #openstack-meeting20:36
*** tsekiyama has quit IRC20:36
jeblairwell, a script, actually.20:36
fungii suppose so20:36
ttxok so.. looks like there aren't so many questions, we just need to collect votes20:36
fungiliterally20:36
*** padkrish has joined #openstack-meeting20:36
flaper87if we solve the 3rd tag state that sdague mentioned, I'd be comfortable with getting it in20:36
*** changbl has quit IRC20:36
flaper87but that shouldn't block solum20:36
*** VanL_ has joined #openstack-meeting20:36
fungii can personally guarantee my commits there are exceedingly trivial ;)20:36
* flaper87 just contradicted himself20:37
sdagueheh20:37
ttxfungi: which makes it even, more a rax-only show20:37
* flaper87 no brain power20:37
sdagueso summary, +1, though I'd feel better with my +1 if there was a PTL election now, because the current PTL has said they don't have time for the project20:37
ttxAlright, I think we can move on, will take some time to add votes to it, given the low attendance20:38
lifelesssdague: +120:38
adrian_ottosdague: the team should decide what's working for them20:38
ttxright, I like the idea of having projects relatively healthy at the time of their addition20:38
*** banix has quit IRC20:38
*** puranamr has quit IRC20:38
adrian_ottolook at the blueprint list and bug list. It's totally up to date.20:39
datsun180band it's ^ his fault primarily20:39
dhellmannadrian_otto: the ptl role is an interface to the rest of the projects, though, and part of being an official project is making sure those responsibilities are being fulfilled. It's not all about internal leadership.20:39
adrian_ottobut there was a time while I was getting magnum ready for launch where I was less involved that I have been in recent weeks20:39
dhellmannthat's not to say you're not doing a good job, just that it becomes more than the team's needs now20:40
adrian_ottodhellmann: fair enough. My suggestion is try it, and if it's not working, I can abdicate to a successor.20:40
*** VanL has quit IRC20:40
ttxok, let's move on20:40
dhellmannso that's 2 things we'd have to take on faith: team diversity and PTL capacity and energy20:40
ttxwill take some time to get to enough votes to pass anyway20:41
* flaper87 will bring this back to the review20:41
ttxdhellmann: maybe add those to the review for reference ?20:41
dhellmannttx: doing that now20:41
* flaper87 will let dhellmann do it20:42
jeblairdhellmann: well, we don't have to take diversity on faith, we know it's not diverse20:42
flaper87:P20:42
*** mattgriffin has joined #openstack-meeting20:42
*** mattgriffin has quit IRC20:42
ttxback to the future...20:42
ttx#topic Add compute starter kit tag20:42
*** openstack changes topic to "Add compute starter kit tag (Meeting topic: tc)"20:42
ttxsdague posted new revision20:42
*** pabelanger has left #openstack-meeting20:42
ttxtime to follow up those +1 promises20:42
jeblairthis is more like groundhog day20:42
ttx"up on those" I guess would be better20:42
*** eharney has joined #openstack-meeting20:42
dhellmannjeblair: I meant that it will increase20:43
sdaguedhellmann: the promiss is the activity will increase20:43
ttxdhellmann: I'm not sure we have a promise on diversity increase -- and I guess that's fine20:43
dhellmannsdague: right, that's what we're taking on faith20:43
sdaguethe diversity will actually go down, because it's all rax product folks20:43
ttxbut I agree that critical levels of non-diversity could make up a good tag20:43
jeblairdhellmann: right; i'm not sure it will.  i'm not sure i would say we should vote on it expecting that.20:43
sdaguethough, it's currently 99% on commits and 100% on reviews, so it can't really get worse20:44
* fungi enjoys being the 1% anomaly everywhere20:44
sdaguefungi: you aren't the 1% in liberty :)20:44
ttxI propose we move on to WG reports while we colect votes on the tag20:44
flaper87I can work on a proposal for the "spartans" tag20:44
fungisdague: oh, even better!20:44
ttx#topic Project team guide workgroup report20:45
*** openstack changes topic to "Project team guide workgroup report (Meeting topic: tc)"20:45
ttxRemember we'll have a virtual sprint on Thursday-Friday to jumpstart this20:45
ttx(I have a few meetings 1400-1700 on the Thursday but otherwise will be around on channel)20:45
flaper87I'll participate on Thursday but I'll be flying on Friday20:45
ttx#link https://wiki.openstack.org/wiki/VirtualSprints#OpenStack_Project_Team_Guide20:45
ttxThe openstack/project-team-guide repo is now ready for use, thanks to jeblair20:45
*** apevec has joined #openstack-meeting20:45
ttxI may cheat and work on the intro tomorrow20:45
jeblairdid we decide where to publish it?20:46
ttxjeblair: not really.20:46
flaper87from the communication WG, I think we should hold-off until next week when we'll have more things to share20:46
jeblair(we have docs-draft builds working, so we'll be able to see it rendered in review during the sprint; so this isn't urgent)20:46
ttxjeblair: I assumed it could live under governance.o.o but I have no strong opinion on that20:46
ttx#topic Communications workgroup report20:46
*** openstack changes topic to "Communications workgroup report (Meeting topic: tc)"20:46
ttxflaper87: that's what you said next week though ?20:47
jeblairttx: okay, i'll work on publishing it there20:47
ttxarh *last* week20:47
flaper87last week there weren't any posts20:47
*** VW has quit IRC20:47
flaper87and I think we'll hold off until next week20:47
*** devkulkarni has quit IRC20:47
*** VW has joined #openstack-meeting20:47
flaper87Since we'll have more to talk about20:47
flaper87unless there are things you guys would like ot communicate20:47
ttxflaper87: true that we only have partial decisions today so far20:47
flaper87yeah, not worth it, IMHO20:48
flaper87I can start workin on a draft and avoid having it published on friday20:48
flaper87At least with the initial contents from today's meeting20:48
flaper87that's about it20:48
ttxthough we could pass the starter-kit tag with sdague, dhellmann and jeblair's votes20:48
* markmcclain has to step out from meeting20:48
ttxand markmcclain20:49
sdaguettx: right, but I really would feel uncomfortable about that20:49
flaper87although that's true, I'd also appreciate other folks comments20:49
lifelessttx: you also have mine, unless gerrit barfed20:49
dhellmannsdague: what's the plan for this new tag? is it your intent to use this in any way to build other tags, or in any other way change the relationship between projects at the TC level or for governance in some way?20:49
sdagueI think we should give this the week, and get as many TC members to voice their opinions on there.20:49
ttxsdague: OK, i'll keep it alive until next week20:49
ttx#topic Other workgroups20:50
*** openstack changes topic to "Other workgroups (Meeting topic: tc)"20:50
ttxAny other workgroup (or workgroup embryo) wanting to report ?20:50
lifelessarchitecture - mark and I haven't synced up yet; this week I have been super distracted by cynthias tonsillectomy20:50
sdaguedhellmann: my intent is that we can use this as a common set of language for new folks coming in about where to start.20:50
* ttx looks up words20:50
lifeless\everything\ gets hard during that20:50
lifelessttx: removal of tonsils20:50
*** eharney has quit IRC20:51
* ttx looks up more words20:51
*** esker has joined #openstack-meeting20:51
lifelessttx: big spongy things in throat that help immune system for first couple years20:51
dhellmannsdague: ok. I would object to using this to make any project more special than any other in the overall tent, but if it's just documentation then I can put aside my assertion that it should live in a documentation repository.20:51
lifelessttx: also a related set in the back of the nose20:51
ttxlifeless: sounds painful enough.20:51
lifelessttx: yeah. cut out and cauterised. 10 day recovery20:51
sdaguedhellmann: I'm hoping that the new language explains that well enough, if not, let me know where you think there needs to be clarity20:51
ttxAlright, anyone else?20:52
dhellmannsdague: the current language is clear, but I'm frankly worried about it because of all of the past drafts. I don't want us to ever have a requirement that a project must have this tag in order to get something from the community, for example.20:52
dougwigsdague: to some degree, it doesn't matter on the wording, but rather how it's received/used.  note how 'core' has taken on a meaning entirely different from anything written down.20:53
sdaguedougwig: sure, and I do understand that20:53
ttx#topic Open discussion20:53
*** e0ne has quit IRC20:53
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:53
sdaguebut as I hopefully layed out, without this we're loosing getting a bunch of folks through the door. I'm hoping this makes an easy door to get them inside, so they can understand all the cool stuff in OpenStack20:53
ttxRemember we are still looking for volunteers to chair the cross-project meeting:20:54
ttx#link https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Chair_rotation20:54
*** barrett has joined #openstack-meeting20:54
krotscheckI have updates to the CORS specification from last week, as requested-> https://review.openstack.org/#/c/189924/20:54
ttxI wrote a "meeting chair guide" to help the volunteers, it's at the same URL ^^20:54
ttxNobody nominated for this week so I'll do it. Would be nice to have a volunteer for next week, though20:54
ttxAnyone ?20:54
ttx...20:55
SlickNikttx: I can do it next week — let me sign up on the wiki.20:55
ttxSlickNik wins!20:55
ttxthx20:55
sdaguecross project meeting starts cutting into dinner / family time in this TZ, so not it20:55
ttxAlso: The M naming poll is under way.20:55
ttxI won't be *that* person and complain my favorite option was unfairly excluded by evil poll organizers :)20:55
lifelessyeah, this is also time for me to do C -> kindy20:56
jeblairttx: i have a change up to address that: https://review.openstack.org/19197420:56
ttxjeblair: I saw that.20:56
ttxjeblair: which is why I tease.20:57
ttxAbout meetign time -- we could in theory move it to another slot. I just don't look forward working late at nights *two* nights per week20:57
*** padkrish has quit IRC20:58
*** thangp has quit IRC20:58
*** padkrish has joined #openstack-meeting20:59
ttxAnything else, anyone ?20:59
* dhellmann would be open to a morning meeting if that makes anything easier for lifeless & ttx20:59
*** eharney has joined #openstack-meeting20:59
ttxdhellmann: it's not totally crazy to rotate the cross-project meeting20:59
dhellmannttx: oh, I was even talking about the tc meeting20:59
*** padkrish_ has joined #openstack-meeting20:59
lifelessttx and I are the two corners of a triangle20:59
flaper87and me20:59
*** padkrish has quit IRC20:59
lifelessdhellmann: is the third20:59
lifelessnothing can make it easier for both of us at once ;)21:00
* dhellmann straightens out his pointy hat21:00
flaper87lifeless: :(21:00
ttxtc is a harder thing. We tried and failed. I'm fine with where it stands now21:00
*** penick has quit IRC21:00
lifelessflaper87: we both live in the best place in the world21:00
lifelessflaper87: don't feel too sorry :)21:00
* flaper87 thinks we should all move to NZ (or move lifeless to EU)21:00
ttxalright time is up21:00
nikhil_kBlacksburg is awesome too21:00
ttx#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Tue Jun 16 21:00:46 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-06-16-20.02.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-06-16-20.02.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-06-16-20.02.log.html21:00
*** ruhe has left #openstack-meeting21:00
*** banix has joined #openstack-meeting21:01
*** puranamr has joined #openstack-meeting21:01
*** pshige has joined #openstack-meeting21:01
* jasondotstar waves at flaper87 21:01
*** mrmartin has quit IRC21:01
*** eghobo has quit IRC21:01
flaper87jasondotstar: yo :D21:02
ttxcourtesy ping for david-lyle flaper87 dims ttx johnthetubaguy rakhmerov21:02
ttxcourtesy ping for smelikyan morganfainberg bswartz slagle adrian_otto mestery21:02
ttxcourtesy ping for kiall jeblair thinrichs j^2 stevebaker mtreinish Daisy21:02
ttxcourtesy ping for notmyname dtroyer isviridov gordc SlickNik loquacities thingee21:02
thingeeo/21:02
ttxcourtesy ping for hyakuhei redrobot TravT emilienm SergeyLukjanov devananda21:02
ttxcourtesy ping for boris-42 nikhil_k21:02
notmynamehere21:02
j^2o/21:02
ttxthx script21:02
SlickNikhere21:02
mesteryo/21:02
hogepodgeo/21:02
SergeyLukjanovo/21:02
*** adrian_otto has left #openstack-meeting21:02
ttx#startmeeting crossproject21:02
stevebaker\o21:02
david-lyleo/21:02
openstackMeeting started Tue Jun 16 21:02:51 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
pshigeo/21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: crossproject)"21:02
openstackThe meeting name has been set to 'crossproject'21:02
ttxToday's agenda:21:02
*** penick has joined #openstack-meeting21:02
*** KunalGandhi has joined #openstack-meeting21:02
ttx#link http://wiki.openstack.org/Meetings/CrossProjectMeeting21:03
bknudsonhi21:03
etoewso/21:03
morganfainbergstevemar: ^^21:03
ttx#topic Horizontal teams announcements21:03
johnthetubaguyo/21:03
*** openstack changes topic to "Horizontal teams announcements (Meeting topic: crossproject)"21:03
nikhil_ko/21:03
*** aysyanne has quit IRC21:03
ttxOn the release management front, liberty-1 is next week21:03
dhellmanno/21:03
ttx#info for projects we manage that are using development milestones, we expect the PTL (or release liaison) to show up next Tuesday to sync with us during office hours21:03
ttx0800-1000 UTC or 1800-2000 UTC in #openstack-relmgt-office21:03
ttxThat will let us double-check implemented blueprints and discuss when to tag21:03
ttxQuestions on that ?21:03
*** peristeri has quit IRC21:04
dimso/21:04
redroboto/21:04
j^2nope21:04
sdague#info QA: grenade external plugins open for business in the big tent - http://lists.openstack.org/pipermail/openstack-dev/2015-June/066583.html21:04
*** tongl has joined #openstack-meeting21:04
sdagueI brought that up previously in this meeting, just wanted to make sure teams saw the information was out there in how to get started21:04
*** pnavarro has quit IRC21:05
SlickNiksdague: very cool — thanks for the info.21:05
* jroll arrives a bit late21:05
boris-42ttx: hi=)21:06
*** datsun180b has left #openstack-meeting21:06
sdagueif there are any questions, no is good, or put on the list21:06
sdague</end>21:06
SlickNikI know at least a couple of people on trove who were previously working on a grenade job — will pass the info along to make sure they see it.21:06
sdagues/no/now/21:06
dims#info Oslo: Request from Oslo team for Liberty Cycle - http://lists.openstack.org/pipermail/openstack-dev/2015-June/067131.html21:06
*** eghobo has joined #openstack-meeting21:06
dimsA handful of items for projects who use oslo, please take a look21:07
*** eharney has quit IRC21:07
ttxOther horizontal teams announcements ?21:08
* dims not sure if this was vertical or horizontal :)21:08
ttxIt is HORIZONTAL21:08
dims:)21:08
Rockygo/21:08
johnthetubaguydims: thats a good tick list, appreciated!21:08
ttxI think I may merge the two sections for clarity :)21:08
fungidims: oslo is a diagonal effort21:09
dimshaha21:09
fungi(i have no idea what that means, but it sounds cool)21:09
ttxRockyg: is that a "I have announcement" or "I'm here" sort of o/ ?21:09
edleafeo/21:09
dimsthanks johnthetubaguy21:09
SlickNikdims: ++ will follow up.21:09
dimsthanks SlickNik21:10
* edleafe is just saying hi21:10
* Rockyg is lurking but here for in support of API standards21:10
*** eharney has joined #openstack-meeting21:10
ttx#topic Server versioning changes (dhellmann)21:10
*** openstack changes topic to "Server versioning changes (dhellmann) (Meeting topic: crossproject)"21:10
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-June/067006.html21:10
ttxdhellmann: ohai21:10
dhellmannhere!21:10
dhellmannAs we have discussed a couple of times, we’re switching the server projects to semver versioning.21:10
dhellmann#link http://lists.openstack.org/pipermail/openstack-dev/2015-May/065211.html21:11
dhellmann#link http://lists.openstack.org/pipermail/openstack-dev/2015-June/thread.html#6527821:11
dhellmannI have submitted patches to all of the projects managed by the release team:21:11
*** PrashantS has quit IRC21:11
dhellmann#link https://review.openstack.org/#/q/topic:semver-releases,n,z21:11
dhellmannIf you agree with the numbering scheme, we need those to land before the L-1 milestone next week.21:11
dhellmannThey’re failing right now because the versions go backwards. I’ll be pushing alpha tags to correct that tomorrow.21:11
dhellmannDoes anyone have questions about the versions proposed, or anything else related to this change?21:11
*** dkranz has quit IRC21:11
*** PrashantS has joined #openstack-meeting21:11
bknudsonwhat is a non-backwards compat change (requires major version bump) for server projects? The interface to keystone is, for example, keystone-manage.21:11
bknudsonThe REST API has its own versioning (V2.0, V3)21:12
dhellmannyeah, some of that is still up for discussions21:12
dhellmannsome proposals have been when migrations are squashed, meaning that upgrades have to pass through that version21:12
lifelessbknudson: indeed; I'd argue any of: removing something from the API; changing the contract of the CLI, including adding new required config options or removing config options21:12
dhellmannalso we've discussed tagging a new major version each cycle, just because21:12
lifelessbknudson: or more broadly 'if users or deployers need to care, then its incompatible and we should signal that'21:13
SpamapSconfig file changes would be backward compatability concerned21:13
*** harlowja has joined #openstack-meeting21:13
ttxnote that for projects under the development-milestone regime, they will just use X.0.0 like they used YYYY.Z.021:13
johnthetubaguydhellmann: upgrade is the big one for me with my Nova hat on, we have lots of compat code for live-upgrades we want to keep dropping each release21:13
ttxthey would not switch to semver21:13
*** tidwellr has joined #openstack-meeting21:13
*** tidwellr has left #openstack-meeting21:14
ttxthat is more for projects that would do intermediary releases21:14
dhellmannjohnthetubaguy: yes, right21:14
notmynamewe bumped the major version in swift when we made a major change that would cause data unavaialbility if you downgraded21:14
johnthetubaguydhellmann: but we have a few months to answer that question, luckly21:14
dhellmannnotmyname: another good one21:14
ttxdhellmann: anything else on that topic ?21:15
dhellmannso we'll figure those things out when the time comes, and I'll keep notes from all of these ideas21:15
dhellmannnope, that's it unless there are more questions21:15
fungione item which has come up is that we've got recent-ish security advisories mentioning upcoming scheduled releases explicitly. we'll need errata to correct all those if the renumbering implementation is not delated to after the next scheduled releases21:15
fungis/delated/delayed/21:15
fungimainly wanting to confirm how soon this is planned for the api server projects so that we can plan accordingly21:16
ttxfungi: our plan is to have those in place to tag X.0.0b1 instead of 2015.2.0b1 at liberty-121:16
*** PrashantS has quit IRC21:16
fungiokay, so we're not changing tag sequence on any existing stable branches21:16
ttxnot at all21:16
dhellmannno, this is just for liberty and forward21:16
fungithat covers my concerns. thanks!21:17
ttxkilo would likely still generate 2015.1.Z21:17
lifelesshas to21:17
ttxdoing otherwise would be even more confusing21:17
*** amoturi has quit IRC21:17
fungiyep, that makes sense. thanks21:17
dims++21:17
ttxalright, moving on then21:17
dhellmannoh, I did also post about this to the operators list21:17
ttx#topic Clarification on the return code when a server has a hard coded length limit21:17
*** openstack changes topic to "Clarification on the return code when a server has a hard coded length limit (Meeting topic: crossproject)"21:17
dhellmann#link http://lists.openstack.org/pipermail/openstack-operators/2015-June/007390.html21:17
ttxoops21:17
ttxThe API working group has one new guidelines that is entering the freeze period:21:18
dhellmannsorry about that21:18
ttx#link https://review.openstack.org/#/c/181784/21:18
ttxThey would like PTLs/CPLs, and other interested parties, to take a look at these reviews.21:18
ttxThey will use lazy consensus at the end of the freeze to merge them if there are no objections.21:18
* nikhil_k giving one review21:18
ttxWe can use a bit of time in this meeting to discuss it, if you have comments21:18
ttxetoews: you there ?21:18
etoewsi'm all ears21:18
*** dboik has quit IRC21:19
nikhil_kshouldnt it be 413?21:19
*** balajiiyer has quit IRC21:19
morganfainbergnikhil_k: that is if the request entity is too large, not the response21:20
bknudsonmight want to differentiate from 413 Request Entity Too Large and 414 Request-URI Too Long21:20
*** VW has quit IRC21:21
ttxmorganfainberg: ++21:21
morganfainbergnikhil_k: the advisory for the WG proposal is saying if the response is too large - you're getting a400 back, not a request or uri too long21:21
krotscheckHrm. And 416 is bytes only.21:21
morganfainbergkrotscheck: yep21:21
morganfainbergkrotscheck: only on a range request21:21
morganfainbergthis is either a 500 (bad idea) or a 400 (more correct)21:21
*** julim has quit IRC21:21
ttxright 400 is fine21:21
krotscheckmorganfainberg: Well, it's technically a range request, it's just not a range of bytes #semantics21:22
krotscheckindeed21:22
nikhil_kspec says: If API limits the length of collection type property, the return code49 should be **400 Bad Request** when request exceeding limited length.21:22
jrollwait, where are we seeing this is about range requests21:22
SlickNikDoesn't this imply that the request is too large: "If API limits the length of collection type property, the return code21:22
SlickNik    should be **400 Bad Request** when the request exceeds the length limit."21:22
lifelessthere's very little benefit in some of these fine-grained codes21:22
jrolllooks to me like... what nikhil_k said.21:22
bknudsonjust wondering - do we only care about the response code and not about any extra info that should be returned?21:22
bknudsonso we return 400 but seems like there should also be some info that allows the client to recover21:23
jroll(ignore me, I'm misreading things)21:23
bknudsonthey don't know which field was too long otherwise21:23
bknudsonor maybe you don't want to tell them for security reasons21:23
etoewsbknudson: this guideline only covers the status code21:23
*** persia has quit IRC21:23
lifelessall HTTP errors are mean to come witha body that describes in as much detail as the server wants to21:23
*** eharney has quit IRC21:23
*** persia_ has joined #openstack-meeting21:24
*** persia_ has joined #openstack-meeting21:24
*** persia_ has quit IRC21:24
etoewsthere's another guideline for errors21:24
lifelessthe status code is purely for programmatic flow control on the client21:24
morganfainbergbknudson: i want to say we need to address that second part independenty of the status code. what hsould the extra data returned be? it could be combined or be separate21:24
lifelessthis is an error21:24
Rockyglifeless: ++21:24
lifelessits not a 50021:24
*** sarob has joined #openstack-meeting21:24
etoewsi should say the error format in a response body21:24
*** singlethink has joined #openstack-meeting21:24
johnthetubaguy400 is less confusing than overloading some special value wrongly, which seemed to be the general idea we are heading towards, with more details in the body of the response21:24
morganfainbergso, we've specified the status code, now we need to handle the other data (lifeless ++)21:24
lifelessright; my point is just that 413 and 414 won't help a client go 'oh too many tags'21:24
johnthetubaguy500 = server error, so lets rule that out, its a client based error21:24
etoewsjohnthetubaguy: ++21:24
SlickNikjohnthetubaguy: I agree ++21:24
lifelessand so 400 is entirely appropriate21:25
johnthetubaguylifeless: +121:25
*** persia has joined #openstack-meeting21:25
ttxAnyway, feels like you can comment (or +1) on the review21:25
lifelessSo this API guideline tweak is entirely correct AFAICT. It might not go far enough, but as etoews says there are guidelines already for the body in this case.21:25
bknudsonthis is talking about the # of elements in a collection?21:25
etoewsfor reference, here's the guideline of errors #link https://review.openstack.org/#/c/167793/21:26
bknudsonand not the length of a string or something?21:26
etoewss/of/for/21:26
*** Shrews has joined #openstack-meeting21:26
lifelessbknudson: correct; https://review.openstack.org/#/c/181784/8/guidelines/tags.rst - expand the upper context21:26
lifelessthe specific context here is a PUT21:26
lifelessI think the prose could be clearer21:26
lifelessbut its reasonably sane if you read more context21:26
bknudsonI assume you also don't want a tag that's 50 MB ?21:26
*** puranamr has quit IRC21:26
lifelessthat might trigger a 413 :)21:27
*** puranamr has joined #openstack-meeting21:27
*** bobh has quit IRC21:27
ttxalright, I think we are back to where we started, so now is as good as any time to move on21:27
*** singleth_ has quit IRC21:28
nikhil_k:)21:28
notmynameI was reading that one wrong21:28
ttxgo on the review and comment if you find anything21:28
*** Shrews has left #openstack-meeting21:28
ttx#topic Library release ACL changes21:28
*** openstack changes topic to "Library release ACL changes (Meeting topic: crossproject)"21:28
ttx#link https://review.openstack.org/18985621:28
ttxdhellmann: you again21:28
*** singlethink has quit IRC21:29
morganfainbergttx: should that include KeystoneAuth once that is a thing?21:29
*** esker has quit IRC21:29
morganfainbergdhellmann: ^ cc21:29
ttxmorganfainberg: likely21:29
dhellmannWe have a patch up to change the tagging permissions for projects that look like libraries:21:29
dhellmann#link https://review.openstack.org/18985621:29
dhellmannI will be submitting another for the projects managed by the release team but not part of the old “integrated release”.21:29
dhellmannAnd then I plan to encourage the -infra team to prioritize those reviews so we can make the cut-over.21:29
dhellmannThere is also a spec up discussing automation for reviews for tags.21:29
dhellmann#link https://review.openstack.org/19119321:29
dhellmannPlease take a few minutes to read through that and comment.21:29
morganfainbergttx: sounds good, will put that on the backburner for as soon as we're ready for a 1.021:29
*** ijw has quit IRC21:29
*** zz_jgrimm is now known as jgrimm21:29
dhellmannmorganfainberg: yeah, we can add that21:30
morganfainbergdhellmann: yeah nothing to do yet, we're not ready for it to roll under tighter release mngmnt21:30
*** ndipanov has quit IRC21:30
morganfainbergdhellmann: but i'll keep it in mind21:30
*** otter768 has joined #openstack-meeting21:30
*** Daviey has quit IRC21:30
*** ijw has joined #openstack-meeting21:31
dhellmannmorganfainberg: ok, there are a couple of steps, including marking it release:managed in governance and updating the ACLs file21:31
ttxalso for reference and rationale:21:31
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-June/066346.html21:31
morganfainbergdhellmann: i'll also run our rational by you agian when we're ready on how the project works (a little different than some of the other libs)21:31
morganfainbergdhellmann: but this can all be delayed.21:31
dhellmannmorganfainberg: sounds good21:31
morganfainbergdhellmann: i want to move middleware under this model for sure sooner vs later though21:32
morganfainbergdhellmann: keystonemiddleware*21:32
morganfainbergdhellmann: i can ping you to get that added here / what else we need to do offline though21:32
*** vnod has joined #openstack-meeting21:32
*** gokrokve has quit IRC21:32
dhellmannmorganfainberg: let's chat tomorrow21:32
morganfainbergdhellmann: sounds good21:32
*** fallenpegasus has quit IRC21:32
anteayadhellmann: I'm fine on all the oslo libs moving over to library-release, as I assume dims and you talk regularly21:32
ttxother comments on that ?21:32
dhellmannanteaya: dims is on the release team, too, so he'll be handling those releases21:33
anteayadhellmann: how can I see that all the other projects agree to this change?21:33
anteayagreat21:33
dhellmannanteaya: this is their chance to disagree :-)21:33
anteayaso +1 on all oslo projects21:33
* anteaya listens21:33
ttxfwiw nobody objected on the ML thread nor on the review so far.21:34
dhellmannanteaya: but we're doing this for all projects managed by the release team, and those project teams have all agreed to that already, so it shouldn't be too big of an issue for anyone21:34
johnthetubaguydhellmann: I commented on that review to say I am good with this for python-novaclient21:34
dhellmannjohnthetubaguy: nice, thank you21:34
johnthetubaguya team owning the constancy checks sounds good to me, helps us to not screw up21:34
ttxalso easy to fix if some PTL ends up disagreeing next week21:34
*** puranamr has quit IRC21:34
anteayajohnthetubaguy: thanks21:35
anteayadhellmann: okey dokey21:35
* anteaya +2's the patch21:35
fungiyep, acls are far from being etched in stone21:35
ttxok, I guess we can move on21:35
ttx#topic Vertical teams announcements21:35
dhellmannalso keep in mind that as we get more of this automated, it'll feel a bit more natural21:35
*** openstack changes topic to "Vertical teams announcements (Meeting topic: crossproject)"21:35
*** otter768 has quit IRC21:35
fungijust as long as we can point confused people at the announcement, i'm good21:35
notmyname#info Swift has slightly changed its core team structure. There is now a separate swiftclient-core in addition to swift-core - http://lists.openstack.org/pipermail/openstack-dev/2015-June/066982.html21:35
dhellmannfungi: ++21:35
dhellmannSlickNik: you had something to bring up, didn't you?21:35
*** tmorin has quit IRC21:36
SlickNikdhellmann: yes21:36
SlickNikI just wanted to follow up on one of the recent email threads on the mailing list that affects Trove in specific, and possibly other OpenStack services.21:36
ttxnotmyname: any time window for the next swift release ?21:36
ttx(yet ?)21:36
SlickNikReferring to http://lists.openstack.org/pipermail/openstack-dev/2015-June/065731.html (Protected openstack resources)21:36
SlickNikI think dhellmann and some others made some good points about deploying instances into a special tenant, and isolating them -- which seems to make sense to me, and we're going with this approach with Trove for now.21:36
notmynamettx: I wish it would have happened already. there's one patch that needs to get in. I'll let you/dhellmann know as soon as I know something21:37
ttxnotmyname: sounds good21:37
SlickNikHowever, even with this approach there were a few concerns that some of us had and so wanted to bring them up to see what other folks thought of them (not sure if some of these are unfounded):21:37
ttxdhellmann: if we come up with tag automation we could actually apply it to intermediary-released projects like swift too21:37
SlickNik1. Deploying into a different tenant prevents sharing of resources across tenants -- for instance if I need to share a keypair, or security group with my instance I need to duplicate it in the other tenant. (Neutron) Ports are a common resource here that come to mind, but neutron has a way of attaching ports defined in one tenant to instances in another (admin / advanced-service role).21:37
dhellmannttx: yes, I plan to rename release_library.sh to release_project.sh or something similar21:38
ttxthat would streamline the release communication (currently a mix of IRC pings/emails)21:38
dhellmannttx: yep, one step at a time :-)21:38
dhellmannSlickNik: is this a situation where being explicit about what is shared/visible could be considered a feature, though?21:39
dhellmann"I have 5 keys, but only 1 should be used for trove, so I only need to install that one in the second tenant"21:39
SlickNikdhellmann: We've got the use case for sec-groups in Trove, and the approach we're planning to take is similar — i.e. have an API to install that particular sec-group rule in Trove.21:40
johnthetubaguyI keep wondering about hierarchical tenants and things, but it feels overcomplicated21:40
SlickNikjohnthetubaguy: Agree, me too.21:40
*** ijw__ has joined #openstack-meeting21:40
johnthetubaguyso we have done this already, in a way, with swift and glance and how nova uses glance to store images21:40
SlickNikDon't have a clearcut solution yet.21:40
fungipart of the concern is to be able to consistently mitigate situations like bug 144529521:41
openstackbug 1445295 in Trove "Guestagent config leaks rabbit password" [Undecided,New] https://launchpad.net/bugs/1445295 - Assigned to Amrith (amrith)21:41
stevebakerSlickNik: I still wonder if switching to multi-tenant messaging would be less effort21:41
fungitrove has "secrets" in its instance boot images. if those are in a customer-controlled tenant, then the tenant has access to download that image and get at the gooey goodness therein21:41
*** merooney has joined #openstack-meeting21:42
morganfainbergfungi: that is frightening21:42
johnthetubaguyfungi: yeah, they can't have access to this21:42
stevebakerlocking all this down would be whack-a-mole21:42
fungiand i'm sure we have plenty of similar situations with other service platforms which rely on nova instances21:42
SlickNikstevebaker: unfortunatly switching to multi-tenant messaging for the guest still wouldn't solve this issue — you'd still have to deploy in a special trove tenant.21:42
johnthetubaguynikhil_k: the glance and swift idea where you need both a service token and a user token to access something, how is that going?21:42
johnthetubaguyfungi: +121:42
notmynamejohnthetubaguy: done on the swift side21:43
*** ijw has quit IRC21:43
notmynamejohnthetubaguy: was in the kilo release21:43
nikhil_kjohnthetubaguy: the work has some proof of concept impl21:43
dhellmannfungi: yeah, we solved it in akanda by having no secrets in the service vm and restricting access to the agent with a private network. Apparently that won't work for all of trove's use cases.21:43
nikhil_kdemonstrated during the previous mid-cycle21:43
johnthetubaguynotmyname: ah, OK, so how does that model work, would it work here for trove?21:43
notmynamejohnthetubaguy: not sure I understand the question. the model is simply "you need 2 tokens and they must both be valid (client and service tokens)"21:44
SlickNikdhellmann: I think we're gravitating towards at akanda like solution at the moment — although I would love to know more about the swift / glance dual token implementation.21:45
dhellmannSlickNik: yes, it sounds like there might be another option to consider21:45
johnthetubaguynotmyname: I was meaning what tenant has the resource? given the tokens are different teants I guess?21:45
nikhil_kSlickNik: let's sync offline on that21:45
SlickNiknotmyname / nikhil_k: Will chat with you guys offline about that.21:45
SlickNiknikhil_k: Sounds good, thanks!21:45
johnthetubaguyso nova has a lock instance method21:45
*** VW has joined #openstack-meeting21:46
johnthetubaguyI am thinking a service could create a VM in some "locked" state with a dual token system21:46
notmynamejohnthetubaguy: http://docs.openstack.org/developer/swift/overview_backing_store.html21:46
SlickNiknotmyname: thanks for the link21:46
johnthetubaguyI guess the main thing I worry about is, what is wrong with just having all the VMs live in another tenant, to make sure we do fix the limitations with that model in anything else that gets planned21:47
SlickNikjohnthetubaguy: Yes so a couple of other concerns that came up with having a special tenant were around rate-limits for it, and scale.21:47
fungithe other supporting use case which seems reasonable is that it's convenient for billing/quota purposes to have them technically count toward the customer's tenant21:48
*** fawadkhaliq has joined #openstack-meeting21:48
SlickNikfungi: yes that too.21:48
ttxSlickNik: have enough to follow-up off-meeting ?21:48
SlickNikSo, I think I have some good direction here — don't want to rat hole on this too much.21:48
SlickNikttx: yes21:48
ttxcool21:48
ttxhogepodge: I think you had something to mention ?21:48
hogepodgeYes,21:49
*** claudiub has quit IRC21:49
johnthetubaguySlickNik: I did comment on that in the spec I think, lets follow up later, I am half asleep right now I am afraid21:49
hogepodgeI've been working on Defcore and Interoperability.21:49
dhellmannfungi: billing and quota can be handled if the app creating the instance has some other object that can be counted and that corresponds to the instance(s)21:49
ttxand doing some awesome work at it21:49
hogepodgeWe've run into Glance API version issues with testing.21:49
johnthetubaguydhellmann: I think thats the gist of my comment in the spec21:49
fungidhellmann: agreed, but that does mean additional complication on the billing side21:49
hogepodgeA lot of the issues are captured in this review21:50
hogepodge#link https://review.openstack.org/#/c/189867/21:50
* nikhil_k clicks21:50
dhellmannfungi: it's more complicated, but it's also explicit that you're charging for or applying a quota to a special thing, so we found it to pay off at dreamhost21:50
ttxhogepodge: mostly around nova not support glance v2, right ?21:50
hogepodgeV1 is more widely deployed in testing (particularly with Nova) and the client.21:50
hogepodgeYes.21:50
*** jwcroppe has quit IRC21:50
ttxjohnthetubaguy: where are we standing on this ? Glance v2 support in Nova ?21:51
johnthetubaguyOK, so nova only has a image API thats glance v1 compatible right?21:51
johnthetubaguyttx: I think jaypipes has offered to add support for glance v221:51
fungidhellmann: though i think the "locked" instances idea also can be used to interpret the specialness and report it distinctly to the customer as such21:51
hogepodgejohnthetubaguy: that's correct. There's an open blueprint that was too late for Kilo21:51
nikhil_kv2 support in Nova, coming up in L121:51
nikhil_khope to get more reviews21:51
hogepodgeBut is supposed to be worked on in Liberty21:51
hogepodge#link https://blueprints.launchpad.net/nova/+spec/use-glance-v2-api21:51
dhellmannfungi: that could be true21:51
ttxnikhil says L1, which means one week21:51
nikhil_kjohnthetubaguy: flwang is working on it atm21:51
hogepodgenikhil_k: excellent21:52
*** AlanClark has quit IRC21:52
johnthetubaguynikhil_k: OK, we need to get that approved for liberty, its not approved right now, and the deadline is next week sometime21:52
nikhil_kttx: I just meant code sorry. The functionality may not be merged that soon21:52
thingeejohnthetubaguy: we'll need to talk about nova defaulting v2 cinder as well. v2 support already exists.21:52
ttxnikhil_k: ah21:52
hogepodgenikhil_k: flwang: Is there anything I can help out with?21:52
johnthetubaguynikhil_k: I think jaypipes said he would drive that, I should follow up with him21:52
nikhil_kjohnthetubaguy: gotcha, on my list of TODOS now21:52
johnthetubaguyhogepodge: so I am still confused about the interop question and nova21:52
*** pballand has quit IRC21:52
nikhil_khogepodge: I will add you to the email loop going for us all working on it21:52
*** fawadkhaliq has quit IRC21:53
johnthetubaguywe have an image v1 compatible APi we have zero planns of adding an image v2 API in nova21:53
nikhil_kjohnthetubaguy: sounds good. me too then, review helps would be much appreciated!21:53
johnthetubaguywhat the issue with the tests here?21:53
hogepodgejohnthetubaguy: we're using Tempest to drive interoperability testing. Right now we don't test image apis because there are vendors who object to v1 being required in the Tempest tests.21:53
hogepodgejohnthetubaguy: which is a side effect of Nova only supporting v121:53
johnthetubaguyhogepodge: erm, not sure I get the implication there21:54
* nikhil_k wants to clarify that email is only to track blokers for people already assigned and not for some secret communication21:54
fungisome vendors implement only the glance v2 api customer-facing21:54
fungiby doing things like setting the v1 api rate limit to an impossibly low value like 021:54
johnthetubaguyfungi: agreed, due to the security issues in glance v1, if you expose glance v1 directly21:55
fungiyet tempest tests using v1 because that's what nova needs21:55
johnthetubaguynova only needs that intnernally exposed21:55
*** bobh has joined #openstack-meeting21:55
fungiand then there are other vendors who have not implemented glance v2 support yet21:55
ttxshouldn't tempest tests use v2 when testing glance external APIs ?21:55
nikhil_kthey should21:55
hogepodgettx glance isn't a required component of defcore21:56
nikhil_kbut glance v1 is exposed in some cases21:56
hogepodgettx: so we use the nova proxy21:56
ttxhmm, ok21:56
*** jwcroppe has joined #openstack-meeting21:56
* ttx has trouble context-switching at midnight21:56
*** asettle has joined #openstack-meeting21:56
hogepodgettx: we could consider image as a required component. keystone was out until just a couple of months ago21:56
*** bobh has quit IRC21:57
hogepodgeI can add this to the topics for next week if we want more time.21:57
johnthetubaguyhogepodge: so the other issue is the tests require the upload of an image, which is another issue I guess?21:57
*** kylek3h has quit IRC21:57
johnthetubaguyhogepodge: can we do this async21:57
*** asettle has quit IRC21:57
ttxI think it's a complex discussion and yes, more time can't hurt21:57
johnthetubaguyhogepodge: I can't think straight this late21:57
hogepodgejohnthetubaguy: that's an important capability imo21:57
ttxhogepodge: maybe engage with John during the week21:57
johnthetubaguyso I support nova supporting glance v2, as we had planned for kilo21:58
hogepodgedefcore meeting tomorrow too if anyone wants to participate.21:58
ttxand we can put it back on agenda next week21:58
johnthetubaguythe bigger issue is working out how to support some of the glance v1 APIs that don't work in glance v221:58
hogepodgejohnthetubaguy: +1 to that21:58
*** asettle has joined #openstack-meeting21:58
johnthetubaguyas nova has to have a glance v1 API exposed21:58
fungiahh, yep i guess that was the meat of the problem is that defcore (via tempest) was expecting the nova image subcommands to work, which they presumably won't without glance v2 support in nova21:58
johnthetubaguylong story21:58
hogepodgefungi: +1 yes21:58
johnthetubaguyfungi: the nova image API should always work, otherwise you can't download an images in nova21:59
fungiat least in providers who have actually disabled glance v121:59
*** penick has quit IRC21:59
*** harshs has quit IRC21:59
fungiso sounds like it's more nuanced in that case21:59
*** niclem has quit IRC21:59
johnthetubaguyfungi: so if glance v1 is disabled, I don't think you can launch an VM, although its possible thats hypervisor dependent, I can't remember right now21:59
fungigot it. anyway, out of time22:00
ttx#topic Open discussion22:00
*** openstack changes topic to "Open discussion (Meeting topic: crossproject)"22:00
ttxlast word ?22:00
ttx"fnord"22:00
ttx#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Tue Jun 16 22:00:43 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-06-16-21.02.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-06-16-21.02.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-06-16-21.02.log.html22:00
*** harlowja has quit IRC22:00
ttxThanks everyone22:00
nikhil_khogepodge: johnthetubaguy : can we discuss on email?22:00
* fungi saw the fnord22:00
* fungi hides22:00
hogepodgenikhil_k: johnthetubaguy: yes, chris@openstack.org22:01
fungior openstack-dev@lists.openstack.org22:01
*** JRobinson__ has joined #openstack-meeting22:01
johnthetubaguynikhil_k: we need a way to upload images in a standard way I guess22:01
*** marrusl has quit IRC22:01
johnthetubaguyfungi: +122:01
hogepodgefungi: +122:01
*** kylek3h has joined #openstack-meeting22:01
* johnthetubaguy goes to bed22:02
*** harlowja has joined #openstack-meeting22:02
Rockygfungi: +10022:02
*** sdake_ is now known as sdake22:02
* fungi finds food22:02
hogepodgejohnthetubaguy: nikhil_k: fungi want me to start the message thread in dev?22:03
*** brnelson has joined #openstack-meeting22:03
*** merooney has quit IRC22:04
nikhil_kfungi: sure!22:05
nikhil_khogepodge: please do start22:05
*** kylek3h has quit IRC22:06
*** ivar-laz_ has joined #openstack-meeting22:06
* nikhil_k &22:06
*** PrashantS has joined #openstack-meeting22:07
*** Prashan__ has joined #openstack-meeting22:08
*** apevec has quit IRC22:09
*** ivar-lazzaro has quit IRC22:10
*** rushil has quit IRC22:10
fungisounds good22:11
*** jecarey has quit IRC22:12
*** PrashantS has quit IRC22:13
*** bknudson has quit IRC22:13
*** Prashan__ has quit IRC22:13
*** jckasper has quit IRC22:16
*** penick has joined #openstack-meeting22:18
*** erlon has quit IRC22:20
*** bobmel has quit IRC22:21
*** alexpilotti has quit IRC22:21
*** fzdarsky has quit IRC22:21
*** bobmel has joined #openstack-meeting22:21
*** dguerri is now known as dguerri`22:22
*** persia has quit IRC22:23
*** 21WACGOA9 has joined #openstack-meeting22:25
*** pballand has joined #openstack-meeting22:25
*** jgrimm is now known as zz_jgrimm22:28
*** harshs has joined #openstack-meeting22:30
*** ddieterly has joined #openstack-meeting22:30
*** ajmiller_ is now known as ajmiller22:30
*** 21WACGOA9 is now known as persia22:30
*** persia has quit IRC22:31
*** persia has joined #openstack-meeting22:31
*** aranjan has joined #openstack-meeting22:31
*** banix has quit IRC22:32
*** david-lyle_ has quit IRC22:34
*** asettle is now known as asettle-afk22:35
*** pballand has quit IRC22:35
*** dguerri` is now known as dguerri22:36
*** armax has quit IRC22:37
*** ayoung has quit IRC22:37
*** puranamr has joined #openstack-meeting22:38
*** dguerri is now known as dguerri`22:39
*** fzdarsky has joined #openstack-meeting22:39
*** VanL_ has quit IRC22:39
*** adahms has joined #openstack-meeting22:40
*** padkrish_ has quit IRC22:41
*** padkrish has joined #openstack-meeting22:41
*** PrashantS has joined #openstack-meeting22:43
*** cbader has quit IRC22:44
*** pbourke has quit IRC22:44
*** fzdarsky has quit IRC22:44
*** pbourke has joined #openstack-meeting22:44
*** padkrish_ has joined #openstack-meeting22:44
*** padkrish has quit IRC22:45
*** puranamr has quit IRC22:46
*** ddieterly has quit IRC22:47
*** dguerri` is now known as dguerri22:48
*** PrashantS has quit IRC22:49
*** PrashantS has joined #openstack-meeting22:50
*** Swami has quit IRC22:50
*** Prashan__ has joined #openstack-meeting22:54
*** PrashantS has quit IRC22:54
*** amitgandhinz has quit IRC22:55
*** ivar-laz_ has quit IRC22:58
*** ivar-lazzaro has joined #openstack-meeting22:58
*** VW has quit IRC22:59
*** puranamr has joined #openstack-meeting22:59
*** ddieterly has joined #openstack-meeting23:00
*** dguerri is now known as dguerri`23:00
*** aimon has quit IRC23:00
*** rbak has quit IRC23:00
*** eghobo has left #openstack-meeting23:01
*** puranamr has quit IRC23:02
*** maxdml has quit IRC23:02
*** ddieterly has quit IRC23:03
*** Prashan__ has quit IRC23:03
*** PrashantS has joined #openstack-meeting23:04
*** carl_baldwin has quit IRC23:05
*** balajiiyer has joined #openstack-meeting23:06
*** PrashantS has quit IRC23:08
*** puranamr has joined #openstack-meeting23:09
*** matrohon has quit IRC23:09
*** balajiiyer has quit IRC23:11
*** puranamr has quit IRC23:11
*** sdague has quit IRC23:12
*** rrrobbb has quit IRC23:21
*** yamamoto has joined #openstack-meeting23:22
*** yamada-h has joined #openstack-meeting23:22
*** sdague has joined #openstack-meeting23:24
*** slong has joined #openstack-meeting23:25
*** Rockyg has quit IRC23:26
*** yamamoto has quit IRC23:26
*** IlyaG has quit IRC23:27
*** garthb_ has quit IRC23:27
*** garthb has quit IRC23:27
*** yamada-h has quit IRC23:27
*** IlyaG has joined #openstack-meeting23:27
*** aleksandr_null has quit IRC23:28
*** samleon has quit IRC23:28
*** aleksandr_null has joined #openstack-meeting23:30
*** arvinchou_1 has quit IRC23:30
*** arvinchou_ has joined #openstack-meeting23:30
*** otter768 has joined #openstack-meeting23:31
*** yamamoto has joined #openstack-meeting23:32
*** yamamoto has quit IRC23:34
*** _nadya_ has joined #openstack-meeting23:35
*** otter768 has quit IRC23:37
*** asettle-afk is now known as asettle23:38
*** _nadya_ has quit IRC23:39
*** tochi has joined #openstack-meeting23:41
*** toscalix has quit IRC23:41
*** sigmavirus24 is now known as sigmavirus24_awa23:42
*** stevemar has quit IRC23:44
*** stevemar has joined #openstack-meeting23:44
*** ItSANgo has quit IRC23:45
*** ItSANgo has joined #openstack-meeting23:45
*** ItSANgo has quit IRC23:46
*** ItSANgo has joined #openstack-meeting23:47
*** ijw__ has quit IRC23:48
*** ItSANgo has quit IRC23:48
*** ItSANgo has joined #openstack-meeting23:49
*** aimon has joined #openstack-meeting23:50
*** aimon_ has joined #openstack-meeting23:51
*** ItSANgo has quit IRC23:51
*** bobh has joined #openstack-meeting23:52
*** puranamr has joined #openstack-meeting23:52
*** ItSANgo has joined #openstack-meeting23:52
*** ajmiller has quit IRC23:53
*** roxanaghe_ has quit IRC23:53
*** aimon has quit IRC23:54
*** puranamr has quit IRC23:56
*** puranamr has joined #openstack-meeting23:56
*** xingchao has joined #openstack-meeting23:58
*** ItSANgo has quit IRC23:58

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