Tuesday, 2015-08-18

*** padkrish has joined #openstack-meeting00:00
*** pritesh has quit IRC00:00
*** roampune has quit IRC00:00
*** puranamr has quit IRC00:00
*** puranamr has joined #openstack-meeting00:00
*** padkrish has quit IRC00:00
*** padkrish has joined #openstack-meeting00:01
*** britthouser has quit IRC00:01
*** sridhar_ram has quit IRC00:01
*** VW_ has quit IRC00:04
*** VW_ has joined #openstack-meeting00:05
*** achanda_ has joined #openstack-meeting00:05
*** banix has quit IRC00:06
*** achanda has quit IRC00:07
*** asettle has joined #openstack-meeting00:08
*** pm90__ has quit IRC00:08
*** harshs has quit IRC00:08
*** asettle has quit IRC00:09
*** VW_ has quit IRC00:09
*** achanda_ has quit IRC00:09
*** asettle has joined #openstack-meeting00:10
*** tongli has quit IRC00:10
*** dannywilson has quit IRC00:11
*** geoffarnold has quit IRC00:17
*** banix has joined #openstack-meeting00:17
*** alop has quit IRC00:17
*** aimon has joined #openstack-meeting00:21
*** tochi has quit IRC00:21
*** carl_baldwin has quit IRC00:22
*** garthb_ has quit IRC00:25
*** tsekiyama has quit IRC00:26
*** puranamr has quit IRC00:26
*** ivar-laz_ has joined #openstack-meeting00:26
*** ivar-laz_ has quit IRC00:27
*** ivar-laz_ has joined #openstack-meeting00:28
*** ivar-lazzaro has quit IRC00:29
*** ivar-laz_ has quit IRC00:31
*** mtanino has quit IRC00:32
*** shashank_hegde has quit IRC00:32
*** puranamr has joined #openstack-meeting00:33
*** dims has joined #openstack-meeting00:34
*** merooney has joined #openstack-meeting00:36
*** wojdev has quit IRC00:36
*** puranamr has quit IRC00:37
*** tiswanso has joined #openstack-meeting00:38
*** carl_baldwin has joined #openstack-meeting00:39
*** banix has quit IRC00:40
*** tiswanso has quit IRC00:40
*** tiswanso has joined #openstack-meeting00:41
*** carl_baldwin has quit IRC00:43
*** leeantho_ has quit IRC00:44
*** topol has joined #openstack-meeting00:45
*** merooney has quit IRC00:45
*** crc32 has joined #openstack-meeting00:46
*** baoli has joined #openstack-meeting00:46
*** sigmavirus24 is now known as sigmavirus24_awa00:49
*** topol has quit IRC00:49
*** Sukhdev has quit IRC00:50
*** epico has joined #openstack-meeting00:51
*** baoli has quit IRC00:51
*** epico has quit IRC00:52
*** epico has joined #openstack-meeting00:53
*** slong has quit IRC00:59
*** jeadr has quit IRC01:01
*** annp has quit IRC01:01
*** jeadr has joined #openstack-meeting01:02
*** dflorea has quit IRC01:02
*** comay has quit IRC01:05
*** xyang1 has quit IRC01:08
*** epico has quit IRC01:09
*** shashank_hegde has joined #openstack-meeting01:12
*** rfolco has joined #openstack-meeting01:12
*** VW_ has joined #openstack-meeting01:12
*** banix has joined #openstack-meeting01:13
*** mtanino has joined #openstack-meeting01:14
*** JRobinson__ has joined #openstack-meeting01:16
*** alexsyip has quit IRC01:17
*** whenry has joined #openstack-meeting01:21
*** pvaneck has quit IRC01:22
*** epico has joined #openstack-meeting01:23
*** andreykurilin__ has quit IRC01:25
*** penick has quit IRC01:27
*** salv-orlando has joined #openstack-meeting01:29
*** padkrish has quit IRC01:29
*** padkrish has joined #openstack-meeting01:29
*** esker has joined #openstack-meeting01:30
*** rfolco has quit IRC01:30
*** etoews has quit IRC01:31
*** padkrish has quit IRC01:34
*** salv-orlando has quit IRC01:35
*** Daisy has joined #openstack-meeting01:35
*** esker has quit IRC01:36
*** bill_az has quit IRC01:37
*** Swami has quit IRC01:39
*** Daisy has quit IRC01:40
*** pfallenop has quit IRC01:44
*** padkrish has joined #openstack-meeting01:44
*** s3wong has quit IRC01:45
*** whenry has quit IRC01:47
*** yamahata has quit IRC01:51
*** padkrish has quit IRC01:54
*** padkrish has joined #openstack-meeting01:55
*** padkrish_ has joined #openstack-meeting01:57
*** janonymous has quit IRC01:57
*** padkrish has quit IRC01:59
*** dane_leblanc has quit IRC01:59
*** yamamoto has joined #openstack-meeting02:05
*** haomaiwang has joined #openstack-meeting02:06
*** sankarshan_away is now known as sankarshan02:08
*** Swami has joined #openstack-meeting02:10
*** mtanino has quit IRC02:11
*** p0rtal_ has quit IRC02:14
*** yamamoto has quit IRC02:14
*** Swami has quit IRC02:16
*** sbalukoff has quit IRC02:22
*** achanda has joined #openstack-meeting02:23
*** dmacpher has quit IRC02:25
*** galstrom_zzz is now known as galstrom02:28
*** galstrom is now known as galstrom_zzz02:28
*** yamahata has joined #openstack-meeting02:30
*** dims has quit IRC02:30
*** baojg has joined #openstack-meeting02:31
*** yamahata has quit IRC02:32
*** Piet has joined #openstack-meeting02:32
*** yamahata has joined #openstack-meeting02:32
*** padkrish_ has quit IRC02:35
*** padkrish has joined #openstack-meeting02:36
*** jeadr has quit IRC02:38
*** pm90_ has joined #openstack-meeting02:39
*** jeadr has joined #openstack-meeting02:39
*** oomichi has joined #openstack-meeting02:40
*** padkrish has quit IRC02:40
*** bswartz has joined #openstack-meeting02:42
*** harshs has joined #openstack-meeting02:42
*** lazy_prince has joined #openstack-meeting02:45
*** tochi has joined #openstack-meeting02:51
*** esker has joined #openstack-meeting02:51
*** jeadr has quit IRC02:59
*** jeadr has joined #openstack-meeting03:00
*** harshs_ has joined #openstack-meeting03:00
*** haomaiwang has quit IRC03:01
*** harshs has quit IRC03:01
*** harshs_ is now known as harshs03:01
*** _amrith_ is now known as amrith03:01
*** baojg has quit IRC03:02
*** haomaiwa_ has joined #openstack-meeting03:02
*** apoorvad has quit IRC03:02
*** esker has quit IRC03:02
*** esker has joined #openstack-meeting03:04
*** yamamoto has joined #openstack-meeting03:06
*** Daisy has joined #openstack-meeting03:13
*** unicell1 has quit IRC03:13
*** shashank_hegde has quit IRC03:13
*** Daisy has quit IRC03:15
*** baojg has joined #openstack-meeting03:15
*** Daisy has joined #openstack-meeting03:16
*** dmacpher has joined #openstack-meeting03:16
*** Daisy has quit IRC03:16
*** tochi has quit IRC03:16
*** Daisy has joined #openstack-meeting03:16
*** vivek-ebay has quit IRC03:17
*** VW_ has quit IRC03:17
*** VW_ has joined #openstack-meeting03:17
*** Ravikiran_K_ has joined #openstack-meeting03:19
*** salv-orlando has joined #openstack-meeting03:19
*** ganeshna has joined #openstack-meeting03:20
*** Daisy has quit IRC03:20
*** rjaiswal has quit IRC03:20
*** Daisy has joined #openstack-meeting03:21
*** VW_ has quit IRC03:22
*** Ravikiran_K_ has quit IRC03:23
*** otter768 has quit IRC03:24
*** jckasper has joined #openstack-meeting03:25
*** esker has quit IRC03:26
*** salv-orlando has quit IRC03:26
*** esker has joined #openstack-meeting03:26
*** Ravi_K has joined #openstack-meeting03:27
*** Daisy has quit IRC03:27
*** HoloIRCUser has joined #openstack-meeting03:29
*** changbl has quit IRC03:30
*** rbak has joined #openstack-meeting03:30
*** pvaneck has joined #openstack-meeting03:31
*** crc32 has quit IRC03:31
*** sdake has joined #openstack-meeting03:32
*** garthb has joined #openstack-meeting03:32
*** lazy_prince has quit IRC03:33
*** shashank_hegde has joined #openstack-meeting03:34
*** tiswanso has quit IRC03:35
*** sdake_ has quit IRC03:36
*** esker has quit IRC03:37
*** esker has joined #openstack-meeting03:38
*** Daisy has joined #openstack-meeting03:38
*** unicell has joined #openstack-meeting03:40
*** markvoelker has quit IRC03:42
*** sdake_ has joined #openstack-meeting03:42
*** VW_ has joined #openstack-meeting03:43
*** wojdev has joined #openstack-meeting03:44
*** jeadr has quit IRC03:45
*** sdake has quit IRC03:45
*** jeadr has joined #openstack-meeting03:45
*** xingchao has joined #openstack-meeting03:47
*** vivek-ebay has joined #openstack-meeting03:48
*** baojg has quit IRC03:49
*** vivek-eb_ has joined #openstack-meeting03:51
*** Daisy has quit IRC03:53
*** vivek-ebay has quit IRC03:53
*** Daisy has joined #openstack-meeting03:53
*** adahms has quit IRC03:55
*** epico has quit IRC03:55
*** Daisy has quit IRC03:58
*** esker has quit IRC03:58
*** KunalGandhi has quit IRC03:59
*** esker has joined #openstack-meeting04:00
*** haomaiwa_ has quit IRC04:01
*** haomaiwa_ has joined #openstack-meeting04:02
*** tochi has joined #openstack-meeting04:02
*** rbak has quit IRC04:03
*** rbak has joined #openstack-meeting04:04
*** shashank_hegde has quit IRC04:09
*** coolsvap|away is now known as coolsvap04:10
*** zz_ttrifonov is now known as ttrifonov04:10
*** ttrifonov is now known as zz_ttrifonov04:11
*** rbak has quit IRC04:12
*** shashank_hegde has joined #openstack-meeting04:12
*** rbak has joined #openstack-meeting04:13
*** esker has quit IRC04:13
*** esker has joined #openstack-meeting04:13
*** esker has quit IRC04:14
*** esker has joined #openstack-meeting04:14
*** baojg has joined #openstack-meeting04:16
*** JRobinson__ is now known as JRobinson__afk04:17
*** bill_az has joined #openstack-meeting04:18
*** esker has quit IRC04:20
*** Ravi_K has quit IRC04:21
*** sdake_ is now known as sdake04:22
*** gmann has quit IRC04:23
*** armax has joined #openstack-meeting04:23
*** ayoung has quit IRC04:25
*** rbak has quit IRC04:26
*** rbak has joined #openstack-meeting04:28
*** ganeshna has quit IRC04:29
*** kencjohnston has joined #openstack-meeting04:29
*** rbak has quit IRC04:30
*** ganeshna has joined #openstack-meeting04:32
*** VW_ has quit IRC04:32
*** VW_ has joined #openstack-meeting04:33
*** HoloIRCUser has quit IRC04:35
*** VW_ has quit IRC04:37
*** shashank_hegde has quit IRC04:38
*** markvoelker has joined #openstack-meeting04:42
*** JRobinson__afk is now known as JRobinson__04:45
*** apoorvad has joined #openstack-meeting04:46
*** markvoelker has quit IRC04:47
*** VW_ has joined #openstack-meeting04:48
*** jeadr has quit IRC04:49
*** jeadr has joined #openstack-meeting04:50
*** apoorvad has quit IRC04:54
*** Daisy has joined #openstack-meeting04:54
*** Apoorva has joined #openstack-meeting04:55
*** yingjun has joined #openstack-meeting04:56
*** xingchao has quit IRC04:57
*** mestery has joined #openstack-meeting04:59
*** lkarm has joined #openstack-meeting05:00
*** haomaiwa_ has quit IRC05:01
*** banix has quit IRC05:02
*** haomaiwa_ has joined #openstack-meeting05:02
*** sbalukoff has joined #openstack-meeting05:04
*** sudipto has joined #openstack-meeting05:04
*** yingjun has quit IRC05:04
*** gyee has quit IRC05:04
*** moha_hunt has quit IRC05:05
*** lkarm has quit IRC05:05
*** kmARC__ has joined #openstack-meeting05:07
*** mestery has quit IRC05:09
*** kencjohnston has quit IRC05:10
*** pm90_ has quit IRC05:11
*** gmann has joined #openstack-meeting05:11
*** comay has joined #openstack-meeting05:12
*** vijendar has quit IRC05:14
*** mrmartin has joined #openstack-meeting05:15
*** harshs has quit IRC05:15
*** xingchao has joined #openstack-meeting05:15
*** pvaneck has quit IRC05:16
*** kencjohnston has joined #openstack-meeting05:18
*** dims has joined #openstack-meeting05:20
*** yingjun has joined #openstack-meeting05:21
*** garthb has quit IRC05:22
*** topol has joined #openstack-meeting05:22
*** vivek-ebay has joined #openstack-meeting05:23
*** yingjun has quit IRC05:24
*** yingjun has joined #openstack-meeting05:25
*** otter768 has joined #openstack-meeting05:25
*** dims has quit IRC05:26
*** vivek-eb_ has quit IRC05:26
*** topol has quit IRC05:27
*** VW_ has quit IRC05:27
*** epico has joined #openstack-meeting05:27
*** Apoorva has quit IRC05:28
*** otter768 has quit IRC05:30
*** jeadr has quit IRC05:30
*** jeadr has joined #openstack-meeting05:31
*** gampel has joined #openstack-meeting05:31
*** padkrish has joined #openstack-meeting05:31
*** padkrish has quit IRC05:31
*** padkrish has joined #openstack-meeting05:32
*** yamamoto has quit IRC05:32
*** vjay8 has joined #openstack-meeting05:32
*** yingjun has quit IRC05:33
*** yingjun has joined #openstack-meeting05:34
*** ccavanna has joined #openstack-meeting05:35
*** salv-orlando has joined #openstack-meeting05:37
*** yingjun has quit IRC05:38
*** lsmola has joined #openstack-meeting05:39
*** yingjun has joined #openstack-meeting05:40
*** nadya has joined #openstack-meeting05:40
*** ildikov has quit IRC05:40
*** nadya has quit IRC05:42
*** achanda has quit IRC05:43
*** shashank_hegde has joined #openstack-meeting05:44
*** vjay8 has quit IRC05:45
*** aimon has quit IRC05:46
*** aimon has joined #openstack-meeting05:46
*** achanda has joined #openstack-meeting05:47
*** salv-orlando has quit IRC05:50
*** Sukhdev has joined #openstack-meeting05:51
*** yamamoto has joined #openstack-meeting05:51
*** nadya has joined #openstack-meeting05:51
*** pfallenop has joined #openstack-meeting05:52
*** yamamoto has quit IRC05:53
*** yamamoto has joined #openstack-meeting05:53
*** ^Gal^ has joined #openstack-meeting05:54
*** yamamoto has quit IRC05:58
*** wojdev_ has joined #openstack-meeting05:59
*** kencjohnston has quit IRC06:00
*** wojdev has quit IRC06:00
*** wojdev_ is now known as wojdev06:00
*** haomaiwa_ has quit IRC06:01
*** nadya has quit IRC06:02
*** haomaiwang has joined #openstack-meeting06:02
*** ^Gal^ has quit IRC06:03
*** ^Gal^ has joined #openstack-meeting06:03
*** yamamoto has joined #openstack-meeting06:06
*** yamamoto has quit IRC06:09
*** yamamoto has joined #openstack-meeting06:09
*** SridharG has joined #openstack-meeting06:09
*** lukebrooker has quit IRC06:10
*** Daisy has quit IRC06:11
*** Daisy has joined #openstack-meeting06:11
*** SridharGaddam has joined #openstack-meeting06:11
*** vivek-ebay has quit IRC06:12
*** Murali has joined #openstack-meeting06:12
*** BharatK has quit IRC06:14
*** ganeshna has quit IRC06:15
*** Daisy has quit IRC06:16
*** oomichi has quit IRC06:16
*** GB21 has joined #openstack-meeting06:17
*** numan has joined #openstack-meeting06:18
*** sudipto has quit IRC06:19
*** wojdev has quit IRC06:20
*** salv-orlando has joined #openstack-meeting06:21
*** britthou_ has quit IRC06:22
*** coolsvap is now known as coolsvap|away06:22
*** hrou has quit IRC06:22
*** britthouser has joined #openstack-meeting06:22
*** JRobinson__ has quit IRC06:23
*** Ravikiran_K has joined #openstack-meeting06:23
*** wojdev has joined #openstack-meeting06:23
*** Ravikiran_K_ has joined #openstack-meeting06:25
*** bvandenh has joined #openstack-meeting06:27
*** Ravikiran_K has quit IRC06:28
*** pfallenop has quit IRC06:28
*** pfallenop has joined #openstack-meeting06:28
*** pfallenop has quit IRC06:28
*** pfallenop has joined #openstack-meeting06:28
*** jtomasek has joined #openstack-meeting06:29
*** stevemar has quit IRC06:29
*** shashank_hegde has quit IRC06:34
*** nadya has joined #openstack-meeting06:35
*** ganeshna has joined #openstack-meeting06:36
*** ganeshna has quit IRC06:38
*** asettle has quit IRC06:38
*** adahms has joined #openstack-meeting06:40
*** markvoelker has joined #openstack-meeting06:43
*** bill_az has quit IRC06:44
*** markvoelker has quit IRC06:48
*** BharatK has joined #openstack-meeting06:50
*** shashank_hegde has joined #openstack-meeting06:51
*** Murali_ has joined #openstack-meeting06:51
*** xingchao has quit IRC06:53
*** Murali has quit IRC06:53
*** Murali_ is now known as Murali06:53
*** Murali_ has joined #openstack-meeting06:58
*** Murali has quit IRC06:58
*** Murali_ is now known as Murali06:58
*** BharatK has quit IRC06:58
*** jhenner has joined #openstack-meeting07:00
*** jhenner has quit IRC07:00
*** mrunge has joined #openstack-meeting07:01
*** haomaiwang has quit IRC07:01
*** jhenner has joined #openstack-meeting07:01
*** wojdev has quit IRC07:01
*** amotoki has quit IRC07:01
*** haomaiwang has joined #openstack-meeting07:02
*** GB21 has quit IRC07:02
*** armax has quit IRC07:04
*** fawadkhaliq has joined #openstack-meeting07:05
*** Sukhdev has quit IRC07:07
*** ildikov has joined #openstack-meeting07:07
*** ganeshna has joined #openstack-meeting07:08
*** SridharG1 has joined #openstack-meeting07:11
*** SridharG has quit IRC07:11
*** peristeri has joined #openstack-meeting07:11
*** BharatK has joined #openstack-meeting07:12
*** SridharG1 has left #openstack-meeting07:13
*** SridharG has joined #openstack-meeting07:13
*** SridharGaddam has quit IRC07:13
*** dguerri` is now known as dguerri07:13
*** SridharGaddam has joined #openstack-meeting07:14
*** kmARC__ has quit IRC07:14
*** alexschm has joined #openstack-meeting07:15
*** matrohon has joined #openstack-meeting07:16
*** dguerri is now known as dguerri`07:16
*** scheuran has joined #openstack-meeting07:18
*** vahidh has quit IRC07:21
*** dmacpher has quit IRC07:21
*** padkrish has quit IRC07:23
*** ganeshna has quit IRC07:23
*** dguerri` is now known as dguerri07:24
*** ganeshna has joined #openstack-meeting07:25
*** otter768 has joined #openstack-meeting07:26
*** lkarm has joined #openstack-meeting07:27
*** stevemar has joined #openstack-meeting07:30
*** otter768 has quit IRC07:31
*** lkarm has quit IRC07:32
*** dguerri is now known as dguerri`07:32
*** dguerri` is now known as dguerri07:32
*** achanda has quit IRC07:33
*** ganeshna has quit IRC07:33
*** stevemar has quit IRC07:34
*** dguerri is now known as dguerri`07:39
*** Daisy has joined #openstack-meeting07:39
*** amotoki has joined #openstack-meeting07:42
*** IanGovett has joined #openstack-meeting07:42
*** padkrish has joined #openstack-meeting07:44
*** yingjun has quit IRC07:45
*** dims has joined #openstack-meeting07:48
*** dims has quit IRC07:53
*** bradjones has quit IRC07:53
*** bradjones has joined #openstack-meeting07:56
*** bradjones has quit IRC07:56
*** bradjones has joined #openstack-meeting07:56
*** kmARC_ has joined #openstack-meeting07:56
*** jcoufal has joined #openstack-meeting07:56
*** devvesa has joined #openstack-meeting07:56
*** kmARC_ has quit IRC07:56
*** Daisy has quit IRC07:59
*** Daisy has joined #openstack-meeting08:00
*** haomaiwang has quit IRC08:01
*** fawadkhaliq has quit IRC08:01
*** fawadkhaliq has joined #openstack-meeting08:01
*** haomaiwang has joined #openstack-meeting08:02
*** yassine__ has joined #openstack-meeting08:03
*** Daisy has quit IRC08:04
anteaya#startmeeting third-party08:05
openstackMeeting started Tue Aug 18 08:05:19 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:05
*** Daisy has joined #openstack-meeting08:05
*** openstack changes topic to " (Meeting topic: third-party)"08:05
openstackThe meeting name has been set to 'third_party'08:05
anteayahello hello if anyone is here08:05
lennybHi08:05
*** eantyshev has joined #openstack-meeting08:06
eantyshevo/08:06
eantyshevhello!08:06
*** jeadr has quit IRC08:06
anteayahello lennyb and eantyshev08:07
anteayahow are you?08:07
*** jeadr has joined #openstack-meeting08:07
lennybthanks, how are you?08:07
anteayagood thanks08:08
anteayawhat shall we discuss today?08:08
*** pnavarro has joined #openstack-meeting08:08
lennybif we have nothing to discuss I have a question08:09
*** Ravikiran_K_ has quit IRC08:10
eantyshevI have nothing particular important08:10
anteayago ahead08:10
lennybI heard there is a way to trigger my CI after it passed some basic gates. where can I read more about it?08:10
anteayaeantyshev: okay thannks08:10
anteayaI don't know whaat you mean lennyb08:10
anteayacan you try to explain what you are talking about?08:10
anteayasorry if I am being slow08:11
anteayacan you just try again?08:11
eantyshevlennyb, do you mean after Openstack Jenkins completed its check?08:11
lennybI would like to be triggered not by gerrit commit, but by pass of let's say gate-system-config-pep808:11
lennybeantishev: yes, I guess08:12
*** derekh has joined #openstack-meeting08:12
*** derekh has quit IRC08:12
anteayaI don't know where to read about doing thata08:12
lennybeantishev: after Jenkins completed with success08:12
anteayaas that isn't something I would advocate for08:12
eantyshevI think I know what you mean, our CI is triggered by comment of 'jenkins' user including 'Builb succeeded' message, will give you a piece of config now08:12
anteayasome pepole do configure there systems that way and I can't stop them08:13
*** derekh has joined #openstack-meeting08:13
anteayabut I personally am not a supporter of that direction08:13
eantyshevwe do that because we have to08:13
lennybanteaya: why? I dont see a reason to load git and our setups if Jenkins failed.08:14
eantyshevor there will be too much computation for our CI08:14
*** padkrish has quit IRC08:14
anteayaright that is the arguement from ci operators08:14
*** padkrish has joined #openstack-meeting08:15
*** scheuran has quit IRC08:15
anteayathe counter argument is that information inn't available earlier in the patch cycle to be incoporated either from reviews by the ci operators on the patch or by the author or human reviewers08:15
anteayaI'm not stopping you08:16
anteayabut I don't personally support it08:16
anteayaand we don't have documentation around that configuration08:16
*** ganeshna has joined #openstack-meeting08:17
lennybanteaya: thanks. I see your point.08:17
anteayaokay thanks08:17
lennybeantyshev: thanks about configuration tip08:17
*** jeadr has quit IRC08:17
eantyshevlennyb: http://paste.openstack.org/show/420156/08:17
anteayathat was all I was trying to share08:17
eantyshevthat's how ours works08:18
*** jeadr has joined #openstack-meeting08:18
*** ganeshna has quit IRC08:18
eantyshevanteaya, could you please explain more, I don't understand08:19
anteayalennyb: can you try to explain my point to eantyshev?08:19
*** scheuran has joined #openstack-meeting08:19
anteayaand I can try to fill in any holes08:19
*** shashank_hegde has quit IRC08:20
*** ganeshna has joined #openstack-meeting08:21
lennybeantyshev: I think the point is to provide as much info and as as quickly as possible to developer.08:21
anteayalennyb: thank you, yes that is the point08:22
*** andreykurilin__ has joined #openstack-meeting08:22
anteayaalso that there is a difference between what infra supports and what operators choose to do08:22
anteayaso should an operator choose to do something that is not the process supported by infra08:23
anteayaand a patch merges that breakes the operator's ci system08:23
lennybanteaya: how much time usually takes to Jenkins to comment the patch?08:23
*** padkrish has quit IRC08:23
anteayathat responsibility rests with the ci operator08:23
*** ganeshna has quit IRC08:23
anteayadepends on how many tests are run08:23
anteayapep8 and lint jobs are fast08:24
anteayaunit tests take as long as unit tests take08:24
eantyshevlennyb: usually 1 hour for nova and cinder which we check, but sometimes longer08:24
anteayaand functional and integration tests can take over an hour08:24
anteayadepends on the individual test job08:24
anteayawe like to support jobs running in about an hour08:25
anteayabut there are jobs that are more than that08:25
anteayabecause that is how long it takes08:25
*** padkrish has joined #openstack-meeting08:25
*** ^Gal^ has left #openstack-meeting08:25
anteayabut we do encourage review of how jobs are built by individual repos08:25
anteayaand encourage refactoring to shave off time08:26
anteayaand infra works to reduce build time as well08:26
eantyshevanteaya: I understand that concerns, recent merge failures of some CIs is a consequence of this optimization08:27
anteayasorry can you expand on your point?08:27
*** ganeshna has joined #openstack-meeting08:28
eantyshevthose CIs which are triggered by Jenkins comments, have higher probability to fail to merge the patch08:29
*** padkrish has quit IRC08:29
anteayaah08:30
anteayaI see08:31
anteayadid we want to discuss this topic further?08:31
anteayaor are we done?08:31
lennybI have nothing else08:32
eantyshevanother thing I want to mention08:32
eantyshevI have created https://review.openstack.org/#/c/207094 some time ago08:32
eantyshevand I need another +2 on that08:33
anteaya#link https://review.openstack.org/#/c/20709408:33
anteayayes you do08:34
anteayaI councel patience08:34
*** adahms has quit IRC08:34
eantyshevI beleive this should improve the experience of third-party CI operators, as this enables them to check cross-repo dependencies08:34
anteayait is really hard to get all the things reviewed when we want them in08:34
anteayaI belive your perspective08:34
anteayahopefully jeblair will have time to look at it soon08:35
eantyshevthanks08:35
anteayahe did just buy a house today08:35
anteayaso he will be very busy offline for the next while doing home new ownership things08:35
anteayabut hopefully your patch will be reviewed soon08:35
anteayathanks for bringing it up08:36
anteayaanything more today?08:36
eantyshevno08:36
anteayaokay thank you08:36
anteayaso nice to talk to you both every week08:36
anteaya:)08:36
anteayaenjoy the rest of your day08:36
anteayaand see you next week08:36
anteaya#endmeeting08:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:36
eantyshevthanks, see you!08:36
openstackMeeting ended Tue Aug 18 08:36:52 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-08-18-08.05.html08:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-08-18-08.05.txt08:36
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-08-18-08.05.log.html08:36
anteaya:)08:37
*** Ravikiran_K_ has joined #openstack-meeting08:37
*** eantyshev has left #openstack-meeting08:37
*** jeadr has quit IRC08:39
*** jeadr has joined #openstack-meeting08:40
*** zeih has joined #openstack-meeting08:42
*** yingjun has joined #openstack-meeting08:43
*** gpaz has quit IRC08:44
*** markvoelker has joined #openstack-meeting08:45
*** markvoelker has quit IRC08:50
*** yamahata has quit IRC08:51
*** aimon_ has joined #openstack-meeting08:55
*** aimon has quit IRC08:59
*** haomaiwang has quit IRC09:01
*** Daisy has quit IRC09:01
*** Daisy has joined #openstack-meeting09:01
*** haomaiwang has joined #openstack-meeting09:02
*** ikhudoshyn has joined #openstack-meeting09:04
*** Daisy has quit IRC09:06
*** zhhuabj has quit IRC09:07
*** pelix has joined #openstack-meeting09:09
*** Daisy has joined #openstack-meeting09:17
*** zhhuabj has joined #openstack-meeting09:20
*** comay has quit IRC09:21
*** ^Gal^ has joined #openstack-meeting09:26
*** comay has joined #openstack-meeting09:27
*** otter768 has joined #openstack-meeting09:27
*** Daisy has quit IRC09:27
*** toscalix has joined #openstack-meeting09:27
*** Daisy has joined #openstack-meeting09:28
*** ^Gal^ has quit IRC09:28
*** ^Gal^ has joined #openstack-meeting09:28
*** fawadkhaliq has quit IRC09:30
*** stevemar has joined #openstack-meeting09:31
*** yingjun has quit IRC09:31
*** lkarm has joined #openstack-meeting09:32
*** otter768 has quit IRC09:32
*** Daisy has quit IRC09:32
*** dkusidlo has joined #openstack-meeting09:33
*** stevemar has quit IRC09:35
*** lkarm has quit IRC09:36
*** neillc is now known as neillc_away09:42
*** afazkas has joined #openstack-meeting09:42
*** Daisy has joined #openstack-meeting09:43
*** Daisy has quit IRC09:43
*** Daisy has joined #openstack-meeting09:44
*** jeadr has quit IRC09:44
*** jeadr has joined #openstack-meeting09:45
*** Daisy has quit IRC09:46
*** Daisy has joined #openstack-meeting09:46
*** Daisy has quit IRC09:47
*** Daisy has joined #openstack-meeting09:48
*** ikhudoshyn has quit IRC09:49
*** Daisy has quit IRC09:52
*** jrist has quit IRC09:54
*** ikhudoshyn has joined #openstack-meeting09:56
*** dkusidlo has quit IRC10:00
*** haomaiwang has quit IRC10:01
*** Daisy has joined #openstack-meeting10:02
*** haomaiwang has joined #openstack-meeting10:02
*** epico has quit IRC10:02
*** Daisy_ has joined #openstack-meeting10:03
*** zeih has quit IRC10:04
*** baojg has quit IRC10:06
*** baojg has joined #openstack-meeting10:06
*** Daisy has quit IRC10:06
*** baojg has quit IRC10:07
*** baojg has joined #openstack-meeting10:07
*** baojg has quit IRC10:07
*** Daisy_ has quit IRC10:07
*** baojg has joined #openstack-meeting10:07
*** pbourke has quit IRC10:11
*** pdb has joined #openstack-meeting10:14
*** pgbridge has quit IRC10:15
*** sdake has quit IRC10:15
*** britthouser has quit IRC10:17
*** baojg has quit IRC10:17
*** pgbridge has joined #openstack-meeting10:17
*** baojg has joined #openstack-meeting10:18
*** ikhudoshyn has quit IRC10:19
*** numan has quit IRC10:21
*** baojg has quit IRC10:23
*** jprovazn has joined #openstack-meeting10:23
*** dkusidlo has joined #openstack-meeting10:25
*** numan has joined #openstack-meeting10:35
*** britthouser has joined #openstack-meeting10:36
*** zhhuabj has quit IRC10:36
*** gampel has quit IRC10:38
*** claudiub has joined #openstack-meeting10:38
*** numan has quit IRC10:41
*** markvoelker has joined #openstack-meeting10:46
*** toscalix has quit IRC10:49
*** markvoelker has quit IRC10:50
*** dims has joined #openstack-meeting10:51
*** numan has joined #openstack-meeting10:54
*** zhhuabj has joined #openstack-meeting10:54
*** haomaiwang has quit IRC10:54
*** gampel has joined #openstack-meeting10:56
*** salv-orlando has quit IRC10:57
*** Ravikiran_K_ has quit IRC10:58
*** comay has quit IRC11:00
*** comay has joined #openstack-meeting11:01
*** sc68cal has quit IRC11:02
*** sc68cal has joined #openstack-meeting11:06
*** sc68cal has quit IRC11:06
*** sc68cal has joined #openstack-meeting11:06
*** sc68cal has quit IRC11:07
*** topol has joined #openstack-meeting11:09
*** delattec has quit IRC11:10
*** cdelatte has quit IRC11:10
*** dane_leblanc has joined #openstack-meeting11:10
*** britthouser has quit IRC11:11
*** britthouser has joined #openstack-meeting11:12
*** yamamoto has quit IRC11:13
*** topol has quit IRC11:14
*** sc68cal has joined #openstack-meeting11:16
*** sc68cal has quit IRC11:16
*** sc68cal has joined #openstack-meeting11:16
*** toscalix has joined #openstack-meeting11:16
*** baoli has joined #openstack-meeting11:17
*** ganeshna has quit IRC11:19
*** salv-orlando has joined #openstack-meeting11:19
*** esker has joined #openstack-meeting11:20
*** toscalix has quit IRC11:21
*** baoli has quit IRC11:21
*** dkusidlo has quit IRC11:23
*** marcusvrn has joined #openstack-meeting11:27
*** otter768 has joined #openstack-meeting11:28
*** dims_ has joined #openstack-meeting11:28
*** toscalix has joined #openstack-meeting11:30
*** dims has quit IRC11:30
*** stevemar has joined #openstack-meeting11:32
*** cdelatte has joined #openstack-meeting11:32
*** otter768 has quit IRC11:33
*** dkusidlo has joined #openstack-meeting11:33
*** dguitarbite has quit IRC11:34
*** jprovazn has quit IRC11:34
*** ikhudoshyn has joined #openstack-meeting11:35
*** stevemar has quit IRC11:35
*** fawadkhaliq has joined #openstack-meeting11:37
*** jprovazn has joined #openstack-meeting11:37
*** DuncanT has quit IRC11:38
*** dguitarbite has joined #openstack-meeting11:38
*** marcusvrn has quit IRC11:38
*** xylan_kong has quit IRC11:39
*** tchaypo has quit IRC11:39
*** jprovazn has quit IRC11:39
*** ramishra has quit IRC11:40
*** gmann_ has joined #openstack-meeting11:41
*** britthouser has quit IRC11:43
*** ikhudoshyn has quit IRC11:43
*** dkusidlo has quit IRC11:44
*** dane_leblanc has quit IRC11:45
*** markvoelker has joined #openstack-meeting11:46
*** fawadk has joined #openstack-meeting11:46
*** yamamoto has joined #openstack-meeting11:47
*** yamamoto has quit IRC11:47
*** yamamoto has joined #openstack-meeting11:47
*** fawadkhaliq has quit IRC11:47
*** yamamoto_ has joined #openstack-meeting11:48
*** topol has joined #openstack-meeting11:49
*** esker has quit IRC11:50
*** dane_leblanc has joined #openstack-meeting11:51
*** jichen has joined #openstack-meeting11:51
*** esker has joined #openstack-meeting11:51
*** markvoelker has quit IRC11:51
*** yamamoto has quit IRC11:52
*** amotoki has quit IRC11:53
*** fawadk has quit IRC11:55
*** ftersin has joined #openstack-meeting11:55
*** Ravikiran_K_ has joined #openstack-meeting11:56
*** bvandenh has quit IRC11:57
*** fungi has quit IRC11:57
*** fungi has joined #openstack-meeting11:59
*** dims has joined #openstack-meeting12:00
alex_xu#startmeeting nova api12:00
openstackMeeting started Tue Aug 18 12:00:09 2015 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: nova api)"12:00
openstackThe meeting name has been set to 'nova_api'12:00
johnthetubaguyo/12:00
alex_xuwho is here today?12:00
gmann_o/12:00
*** dims has quit IRC12:00
*** dims_ has quit IRC12:00
edleafeo/12:00
alex_xuhello everyone~12:01
johnthetubaguyI have a feeling sdague is away, but I might have my weeks mixed up12:01
*** dims has joined #openstack-meeting12:01
alex_xuyea12:01
alex_xulet's get start12:01
*** esker has quit IRC12:01
alex_xu#topic actions from last meeting12:01
*** openstack changes topic to "actions from last meeting (Meeting topic: nova api)"12:01
alex_xuthere are two actiosn for sdague~ so we can't ensure this week12:02
alex_xuone from me about cleanup elevated context12:02
alex_xuI created bp for it https://blueprints.launchpad.net/nova/+spec/cleanup-elevated-context12:03
alex_xuthat will be M release work item12:03
johnthetubaguywhat were the actions for sean?12:03
alex_xusdague to build experimental devstack/tempest job to test v2.0 on v2.112:03
alex_xusdague to find gerrit query to pull all API changed specs12:03
johnthetubaguycool12:03
alex_xulet's check with him when he back, or next week12:04
*** dprince has joined #openstack-meeting12:04
alex_xu#action check sdague his action in next week meeting :)12:04
*** lkarm has joined #openstack-meeting12:04
*** dkusidlo has joined #openstack-meeting12:05
*** topol has quit IRC12:05
alex_xuthe last one is about checking merge api samples status, and gmann_ in the meeting today, let us talk about that later12:05
*** dims has quit IRC12:05
*** dkusidlo has quit IRC12:05
*** SridharGaddam has quit IRC12:05
gmann_experimental devstack/tempest job to test v2.0 on v2.1 is interesting12:05
alex_xu#topic v2.0 on v2.112:05
*** openstack changes topic to "v2.0 on v2.1 (Meeting topic: nova api)"12:05
*** andreykurilin__ has quit IRC12:05
alex_xugmann_: yea12:05
*** topol has joined #openstack-meeting12:05
johnthetubaguyso this change is interesting: https://review.openstack.org/#/c/214085/312:06
johnthetubaguysee the tempest failures12:06
alex_xu#info bp relax-api-validation is finished12:06
johnthetubaguyalex_xu: except, we break tempest12:06
alex_xujohnthetubaguy: we remember we said create v2 on v2.1 endpoint after we have tempest experimental job for relax validation?12:07
*** dprince has quit IRC12:07
gmann_johnthetubaguy: hummm12:07
alex_xujohnthetubaguy: emm.....12:07
johnthetubaguyI didn't but that makes some sense12:07
*** dprince has joined #openstack-meeting12:07
*** agentleweb has joined #openstack-meeting12:08
johnthetubaguytempest.api.compute.servers.test_server_metadata_negative.ServerMetadataNegativeTestJSON looks to be failing12:08
alex_xubut it's worth take a look at what happend for tempest failure in https://review.openstack.org/#/c/214085/312:08
johnthetubaguyI guess thats because of the relaxed validation?12:08
*** rfolco has joined #openstack-meeting12:09
*** topol has quit IRC12:10
gmann_johnthetubaguy: alex_xu may be validation is fully relaxed as of v212:10
alex_xunot sure, it return 500, looks like some unexpected exception raise up12:10
gmann_or there might be valid failure as per v2.1 strong validation12:10
johnthetubaguyI think its just tempest is adding extra props, which we don't check12:10
gmann_ye, need to look up those12:10
*** tochi has quit IRC12:10
johnthetubaguyI suspect v2 used to validate that, but v2.1 with relaxed validation is not12:10
gmann_johnthetubaguy: yea seems like that12:11
johnthetubaguyanyway, my idea is to get that patch into liberty12:11
johnthetubaguydefault to v2.1 for everything12:11
gmann_johnthetubaguy: in those case we need to put such validation in python code12:11
johnthetubaguyremove v3 endpoint12:11
alex_xuyea12:11
edleafejohnthetubaguy: +112:12
alex_xu+112:12
gmann_johnthetubaguy: tomorrow i have plan to rebase all merge tests thing and have you patch depends on those12:12
*** markvoelker has joined #openstack-meeting12:12
johnthetubaguygmann_: my patch does depend on all those already12:13
*** banix has joined #openstack-meeting12:13
alex_xujohnthetubaguy: gmann_ means depend on https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:merge_sample_tests,n,z12:13
johnthetubaguyanyways, I think we are agreeing the end goal12:13
johnthetubaguyalex_xu: gmann: ah, OK12:13
johnthetubaguyalex_xu: gmann: not sure thats needed12:14
gmann_johnthetubaguy: on v3 tthings but not on functional tests merge.thats why nova functional job fail12:14
gmann_yea12:14
*** pnavarro is now known as pnavarro|lunch12:14
*** skath has quit IRC12:14
johnthetubaguygmann: I don't see any test failures after my patch though, unit test wise, its just the tempest issues12:14
*** toscalix has quit IRC12:15
johnthetubaguyanyways, I think the key thing is, v2.1 by default, deprecate v2.0 and remove v312:15
*** zeih has joined #openstack-meeting12:15
*** dims has joined #openstack-meeting12:15
johnthetubaguynow to do that, we might need some tempest tweaks, including those sdague was going to be looking into for us12:15
gmann_johnthetubaguy: i can look tomorrow in JST if i find time12:15
johnthetubaguygmann: you mean the tempest failures?12:16
gmann_yea12:16
*** skath has joined #openstack-meeting12:16
johnthetubaguygmann: cool, that would be good, thanks12:16
alex_xugmann_: thanks12:16
alex_xugmann_: I also can give help on it12:16
gmann_np12:16
*** SridharGaddam has joined #openstack-meeting12:16
*** pm90_ has joined #openstack-meeting12:16
*** aysyd has joined #openstack-meeting12:16
gmann_alex_xu: sure thanks12:16
alex_xuanyway we are on almost same timezone12:17
johnthetubaguyOK, I guess we are done with this bit? maybe?12:17
gmann_alex_xu: yea12:17
alex_xu#action gmann_ and alex_xu take a look at tempest failure of https://review.openstack.org/#/c/214085/312:17
alex_xu#topic policy.json updates to remove admin hard code at the db level12:17
*** jeadr has quit IRC12:17
*** openstack changes topic to "policy.json updates to remove admin hard code at the db level (Meeting topic: nova api)"12:17
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/nova-api-policy-final-part,n,z12:18
alex_xuThe last one patch is ready!12:18
alex_xujohnthetubaguy: if you have time, it is easy patch12:18
*** jeadr has joined #openstack-meeting12:18
*** salv-orlando has quit IRC12:18
*** raildo-afk is now known as raildo12:18
johnthetubaguycool12:19
johnthetubaguylooks good12:19
alex_xuthen nothing need to do in Liberty for this, will remove it from the agenda12:19
edleafeyep12:19
alex_xuok, let's move on12:19
alex_xu#topic Test collapse of v2.0 and v2.112:20
*** openstack changes topic to "Test collapse of v2.0 and v2.1 (Meeting topic: nova api)"12:20
alex_xualready metion a little12:20
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:merge_sample_tests,n,z12:20
alex_xuafter gmann_ rebase those patch, then we need a lot of review for them12:20
*** bswartz has quit IRC12:20
gmann_alex_xu: yea, around 80% is done. left out i will finish by tomorrow12:21
gmann_then those will be ready for review12:21
alex_xugmann_: so we can remove v3 endpoint after those patches merged, right?12:21
johnthetubaguydo we have a blueprint to track the progress of all this?12:21
johnthetubaguyI think that would be useful12:21
gmann_alex_xu: yea, we can remove12:21
gmann_johnthetubaguy: we do not have BP, should i create one?12:22
alex_xuI guess not12:22
alex_xu#link https://etherpad.openstack.org/p/merge_sample_tests12:22
johnthetubaguygmann_: create one, and pass me the link and I can get that approved12:22
alex_xuas I know, gmann_ use etherpad track them12:22
johnthetubaguynow I think this is lower priority that some of our other efforts, but I could me missing something12:22
gmann_johnthetubaguy: sure12:22
gmann_johnthetubaguy: just BP not spec right?12:22
johnthetubaguygmann_: yes12:23
gmann_ok12:23
alex_xuif you want to remove v3 endpoint from api-paste.ini, then it isn't low priority...12:23
johnthetubaguyalex_xu: the unit tests pass right now when I removed that, somehow12:23
alex_xujohnthetubaguy: yea, the main problem is functional test12:24
*** annegentle has joined #openstack-meeting12:24
gmann_johnthetubaguy: UT will pass. actually some functional tests use /v312:24
johnthetubaguyah, so I totally didn't see that one, gotcha12:25
gmann_johnthetubaguy: current merger tests work make them on v2.1 and v212:25
*** jprovazn has joined #openstack-meeting12:25
*** agentleweb has left #openstack-meeting12:25
alex_xualmost all the patch at here, the patch review is high priority12:26
alex_xuok, so no more question for this?12:27
alex_xuok, let's moving one12:27
alex_xu#topic Removal of v3 naming from source tree12:27
*** openstack changes topic to "Removal of v3 naming from source tree (Meeting topic: nova api)"12:27
alex_xuall the file moving are done!12:27
*** MaxPC has joined #openstack-meeting12:27
edleafe\o/12:28
johnthetubaguyso there is the v21 vs no version debate12:28
johnthetubaguyyeah, top job on getting the moves done, awesome to see :)12:28
gmann_johnthetubaguy: +112:28
alex_xuyea, v2.1 is name for nova new api with microversions12:28
alex_xuand actually v2.1 always bump it's version12:28
edleafeI've always felt that versions in the URL are an anti-pattern12:29
alex_xuso we prefer not mention the version in the code12:29
johnthetubaguyedleafe: sure, but they are there now, sadly12:29
edleafejohnthetubaguy: can you think of a better time to remedy that?12:29
johnthetubaguyedleafe: its too late, I feel12:29
*** yamamoto_ has quit IRC12:29
edleafewe are changing the way we approach versioning12:29
johnthetubaguyedleafe: at least we don't have v2.13 in the URL12:29
edleafejohnthetubaguy: heh12:30
*** yanyanhu has joined #openstack-meeting12:30
edleafethat would be horrible12:30
edleafebut it shows that versions simply don't belong there12:30
*** banix has quit IRC12:30
gmann_and it will difficult to remove as uri has tenant-id also12:30
johnthetubaguyso we are keeping compatiblity with the old APIs, so the /v2 and /v1.1 have to stay12:31
alex_xugmann_: yea, it also a problem12:31
*** SridharG has left #openstack-meeting12:31
johnthetubaguyunfortunately, we have already released v2.1, so that has to stay too12:31
alex_xuanyway look like we have agreement on this.12:31
johnthetubaguyyeah, lets talk about liberty12:31
johnthetubaguythe class names12:31
edleafehow about /v∞12:31
johnthetubaguywhat should they be12:31
*** Adriano__ has quit IRC12:32
johnthetubaguyedleafe: sure12:32
edleafe:)12:32
alex_xuI'm working on update this https://review.openstack.org/21273412:32
*** bvandenh has joined #openstack-meeting12:32
edleafeclass names: definitely not V3; probably V21 for now12:33
alex_xuremove the V21 prefix from the class name12:33
edleafewe can always change in M12:33
edleafewhen we drop v212:33
gmann_alex_xu: me also on side to not hve v21 in class nme12:33
johnthetubaguyso the worse case, is leaving v3 in there12:34
alex_xuedleafe: is it ok for you? let's remove it for now, as we already touch them12:34
*** Adriano__ has joined #openstack-meeting12:34
edleafealex_xu: sure12:34
johnthetubaguyas long as v3 goes, I am happy really12:34
alex_xuI think we needn't remove V21 form those test class https://github.com/openstack/nova/blob/master/nova/tests/unit/api/openstack/compute/test_access_ips.py#L3212:34
johnthetubaguyso here is the thing12:34
edleafeI was thinking more gradual until the dual-support ends, but I'd love to get rid of it now12:35
alex_xuthat is used to distinguish v2 and v2.1 unittest in the same file, after we remove v2 code and test, we cleanup them12:35
johnthetubaguyv3 -> v21 might be better to be consistent with those other ones12:35
johnthetubaguythen maybe we remove all v21 when we drop the v2 code (probably in O release)12:35
johnthetubaguyso I have a lean towards v21 for the moment12:36
alex_xuok, if we think keep V21 for now is more clear, I'm ok with that12:37
gmann_plan looks good12:37
johnthetubaguyjust in terms of consistency I guess12:37
edleafejohnthetubaguy: that's pretty much what I was thinkning12:37
alex_xuyea12:37
edleafethinking, even12:37
alex_xuok, I needn't update the patch12:37
alex_xuok, so we have consistency now, let's move on12:37
johnthetubaguycool12:38
*** marcusvrn has joined #openstack-meeting12:38
alex_xu#topic API Documentation Improvement12:38
*** openstack changes topic to "API Documentation Improvement (Meeting topic: nova api)"12:38
edleafeso we're keeping V21 in class names and URLs?12:38
annegentlewhat I woke up for!12:38
edleafemorning, annegentle!12:38
alex_xuedleafe: V21 in class, not URL12:38
alex_xuannegentle: morning12:38
alex_xuedleafe: use '/v2' in the unittest12:39
johnthetubaguyedleafe: its in there, and we released the API already, don't think we have a choice now12:39
johnthetubaguyedleafe: / is the API that lists the available versions12:39
edleafealex_xu: you should record those with the #agreed action12:40
alex_xuha, we have such command12:40
edleafejohnthetubaguy: understood. Not ideal, but necessary at this point12:40
johnthetubaguyyeah, I think its the best option of those we had available at the time12:40
edleafealex_xu: yeah, I think only the chair can use that one12:41
alex_xu#agreed use V21 for class name for consistency now. After v2 api removed, we will remove V21 prefix from the class name also12:41
*** dims_ has joined #openstack-meeting12:41
*** dims has quit IRC12:41
alex_xu#agreed use '/v2' in the unittest that is consistency with existed unittest12:41
alex_xuback to the doc12:42
johnthetubaguyI think we might need to change the unit tests, eventually, but yeah, lets not worry about that for now, its docs time12:42
annegentlealex_xu: did you get a chance to look at fairy-slipper?12:42
gmann_johnthetubaguy: +1. i have plan to do that12:42
alex_xuannegentle: yea, I take a look at few weeks ago, but honest a little hard to get understand it12:43
annegentleAlso I've updated the API docs spec to describe how to write conceptual information https://review.openstack.org/#/c/209669/12:43
alex_xuannegentle: any doc how to use it, and how it structure12:43
annegentleyou can write more content in nova/docs/ and we'll publish to developer.openstack.org12:43
johnthetubaguyso, just for the avoidance of doubt, docs are the most important API issue to get straight this release, and we have lost our way a little on that12:43
annegentlealex_xu: no, sorry, and I know that's a big limiter. So far I know this:12:43
*** gampel has quit IRC12:43
annegentlerun migrate.sh to clone a copy of the api-site and then look for errors in the WADL12:44
gmann_alex_xu: annegentle : does fairy-slipper does same as json-home?12:44
annegentlerun a pecan server to serve the Swagger and RST content12:44
gmann_as we have pln for json-home which generate api info from mapper12:44
johnthetubaguydo we still have WADL for all our different versions?12:44
*** LimorStotland has left #openstack-meeting12:45
annegentlegmann_: fairy-slipper should let us serve reference content12:45
annegentle#link http://fairy-slipper.russellsim.org/swagger-ui-jensoleg/#!/images/get_tenant_id_images12:45
annegentlethat's an example12:45
johnthetubaguyannegentle: do you have examples where it deals with version changes?12:45
*** yamamoto has joined #openstack-meeting12:45
*** yamamoto has quit IRC12:45
annegentlejohnthetubaguy: for v2 and 21 yes and fairy-slipper has helped detect where the source doc is wrong12:45
*** yamamoto has joined #openstack-meeting12:46
annegentlejohnthetubaguy: not yet I have a related question for this group tho12:46
johnthetubaguyannegentle: we have lots and lots of versions though now12:46
*** enikanorov2 has joined #openstack-meeting12:46
gmann_annegentle: Thanks. ll look12:46
annegentleInheritance or annotation? Examples:12:46
johnthetubaguyhttps://github.com/openstack/nova/blob/master/nova/api/openstack/rest_api_version_history.rst12:47
annegentle:http:get /image/12:47
annegentle    :inherits: /image/@>1.112:47
annegentleor12:47
annegentle(oh followed by)12:47
annegentle:parameter image_id: an image id12:47
annegentleor12:47
annegentle:parameter image_id@>1.1<3.0: an image id12:47
johnthetubaguyit could be removal or addition, technically, in a new version12:47
annegentleso the parameter exists in versions greater than 1.1 but less than 3.0 and would only appear in the documentation within that version range12:47
johnthetubaguyso I guess its a whole new doc tree for each version?12:48
*** baoli has joined #openstack-meeting12:48
johnthetubaguydo the users get to see "changes" since the last version inside those docs at all?12:48
johnthetubaguyI am thinking about the python docs12:48
*** yamamoto has quit IRC12:49
annegentlejohnthetubaguy: What we talked about is the drop down list next to Version: here https://libgit2.github.com/libgit2/#HEAD12:49
*** marcusvrn has quit IRC12:49
annegentlejohnthetubaguy: how that's sourced I don't recall12:49
johnthetubaguyyeah, I was thinking something more like this: https://docs.python.org/2/library/unittest.html#unittest.TestCase.setUpClass12:49
johnthetubaguybut in a REST API sense12:49
annegentlejohnthetubaguy: that's what that above question about params tries to encapsulate12:50
johnthetubaguyannegentle: yeah, gotcha, I think12:51
*** enikanorov2_ has joined #openstack-meeting12:51
*** enikanorov2_ has quit IRC12:51
annegentlejohnthetubaguy: I think that the versions will be sourced from the python code so all different versions of the doc will be in that doc string12:51
annegentlewe'll want to make nav consistent for every API12:52
johnthetubaguyannegentle: yeah, that makes sense12:52
johnthetubaguyso we need to get to a point of generating the docs12:52
johnthetubaguywho is taking on that job?12:52
johnthetubaguyat least scoping the scale of the problem12:52
*** baoli has quit IRC12:52
*** gmann_ has quit IRC12:53
*** enikanorov2_ has joined #openstack-meeting12:53
*** ikhudoshyn has joined #openstack-meeting12:53
*** enikanorov2 has quit IRC12:53
annegentleI can run the code locally now, but Russell Sim is working on the display/rendering. I'd like a volunteer to ensure they understand the decisions / output for microversions12:54
johnthetubaguyI am sensing a tumble weed12:54
annegentleso don't feel like you're signing up for a huge pile of work.12:54
annegentleheh12:54
annegentlejohnthetubaguy: send out a call for help12:54
johnthetubaguyyeah, I kinda want the subteam to own the call for help here, but happy to back that up if needed12:54
annegentle#link https://github.com/russell/fairy-slipper12:54
*** Adriano__ is now known as adrianofr12:55
johnthetubaguyannegentle: so is the ask, look at the sample stuff thats been rendered and check it?12:55
*** neelashah has joined #openstack-meeting12:55
*** gmann_ has joined #openstack-meeting12:55
annegentlejohnthetubaguy: look at the code base, ensure you understand what it's doing, correct if it isn't going to work for nova12:55
*** GB21 has joined #openstack-meeting12:56
johnthetubaguyOK, got it12:56
*** GB21_ has joined #openstack-meeting12:56
johnthetubaguyso does anyone know if we have up to date WADL12:56
alex_xusorry, I reboot the laptop....12:56
annegentlejohnthetubaguy: we've caught and fixed WADL source bugs (still working on one myself)12:56
*** GB21_ has quit IRC12:56
johnthetubaguyI get the impression thats a no?12:56
annegentlejohnthetubaguy: this tool detects errors in the WADL12:56
johnthetubaguyannegentle: where is the WADL coming from, I don't remember us updating that ever12:56
alex_xuI can help on any microversion question12:57
annegentlejohnthetubaguy: right it is in the api-site repo and authored over years12:57
alex_xuannegentle: is there gerrit for https://github.com/russell/fairy-slipper?12:57
johnthetubaguyannegentle: thats what I was worried about, its not auto generated12:58
annegentlealex_xu: no, but we think it can live as a common library12:58
annegentlejohnthetubaguy: this migration process will then autogenerate swagger12:58
annegentlejohnthetubaguy: the wadl conversion is a baseline to compare12:58
alex_xuwe are run out of time, have to move on12:58
*** dane_leblanc_ has joined #openstack-meeting12:58
johnthetubaguyalex_xu: what topics did we not cover today?12:59
annegentle#help Take a look at https://github.com/russell/fairy-slipper12:59
*** britthouser has joined #openstack-meeting12:59
alex_xuno exactly12:59
alex_xu#topic open12:59
*** dane_leblanc has quit IRC12:59
*** openstack changes topic to "open (Meeting topic: nova api)"12:59
*** topol has joined #openstack-meeting12:59
gmann_annegentle: Thanks. ll look sometime12:59
annegentleWith less than 60 days until release it's crucial we get this doc generation working. I know I'm "preaching to the choir"12:59
alex_xusorry just jump to open, avoid some body need help in open12:59
gmann_johnthetubaguy: BP for test merge - https://blueprints.launchpad.net/nova/+spec/test-collapse-v2-and-v2113:00
alex_xuannegentle: yea, will try to undersand fairy-slipper again13:00
johnthetubaguyalex_xu: can you ask on the ML for some help with this?13:00
*** ikhudoshyn has quit IRC13:00
alex_xujohnthetubaguy: you mean fairy-slipper?13:00
johnthetubaguyyeah13:00
johnthetubaguywe need that doing 4 weeks ago, basically13:00
alex_xujohnthetubaguy: yea, that is right way13:01
alex_xusorry, we have to close the meeting13:01
*** britthou_ has joined #openstack-meeting13:01
johnthetubaguywe do, lets move on13:01
alex_xu#endmeeting13:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:01
openstackMeeting ended Tue Aug 18 13:01:31 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-08-18-12.00.html13:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-08-18-12.00.txt13:01
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-08-18-12.00.log.html13:01
gmann_Thanks all13:01
alex_xuthanks all13:01
*** dims has joined #openstack-meeting13:01
yanyanhu#startmeeting senlin13:02
openstackMeeting started Tue Aug 18 13:02:07 2015 UTC and is due to finish in 60 minutes.  The chair is yanyanhu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
*** openstack changes topic to " (Meeting topic: senlin)"13:02
openstackThe meeting name has been set to 'senlin'13:02
*** enikanorov2_ has quit IRC13:02
yanyanhuhello13:02
*** dims_ has quit IRC13:02
*** bswartz has joined #openstack-meeting13:02
yanyanhuQiming is still in travel and can't join the meeting tonight13:03
*** haomaiwang has joined #openstack-meeting13:03
*** topol has quit IRC13:03
yanyanhuso if you guys have anything want to update, please feel free to add it to the agenda, thanks13:03
*** amrith is now known as _amrith_13:04
*** VW_ has joined #openstack-meeting13:04
*** gmann_ has quit IRC13:04
*** britthouser has quit IRC13:04
*** toscalix has joined #openstack-meeting13:04
*** yamamoto has joined #openstack-meeting13:04
*** xingchao has joined #openstack-meeting13:05
yanyanhuwill wait for a while. If there is no topic we want to discuss, will just skip this meeting13:06
*** yamamoto has quit IRC13:08
*** jroyal has joined #openstack-meeting13:08
*** haiwei has joined #openstack-meeting13:10
*** VW_ has quit IRC13:11
yanyanhuhi, haiwei13:11
*** VW_ has joined #openstack-meeting13:11
haiweihi13:11
yanyanhuI guess other guys haven't joined13:11
haiweionly both of us?13:12
yanyanhuplanned to do some update about current workitem13:12
*** yamamoto has joined #openstack-meeting13:12
yanyanhuseems so13:12
*** yamamoto has quit IRC13:12
yanyanhubut I think if just two of us, maybe we just skip this meeting?13:12
*** adahms has joined #openstack-meeting13:13
haiweiit is ok i think13:14
haiweithe network in my home is really bad13:14
haiweiI thought I can't attend this room13:15
*** dims_ has joined #openstack-meeting13:15
*** VW_ has quit IRC13:15
*** yanyan has joined #openstack-meeting13:15
yanyanjust dropped when I was typing 'me too'...13:16
haiweiyanyanhu, about this week's plan, I will try to finish the exception handling of other driver modules13:16
yanyannetwork is not very stable, I'm using my phone as hot spot13:16
haiweihaha13:16
*** VW_ has joined #openstack-meeting13:16
yanyan:)13:16
yanyancool13:16
yanyanI think we need to fix the test case issue13:17
*** dims has quit IRC13:17
haiweiok, don't need to bear it13:17
yanyanit blocked the progress of rework exception handling of keystone driver13:17
yanyanok13:17
*** kencjohnston has joined #openstack-meeting13:17
*** jckasper has quit IRC13:17
yanyanso will try to recheck those open patches and merge some of them13:17
haiweiok13:18
yanyanI will keeping working on functional test13:18
haiweicool13:18
yanyanI think the basic workflow has been ok now13:18
yanyanthe first test case can be run correctly in gate13:18
haiweiI will join that job too, if I have time13:18
yanyannice :)13:18
*** yanyanhu has quit IRC13:19
*** changbl has joined #openstack-meeting13:19
haiweiok, that's all for the meeting13:19
haiweisee you tomorrow13:19
*** persia_ is now known as persia13:19
yanyanok, see U13:19
yanyanwill end the meeting13:19
yanyanthanks13:20
*** ivasev has joined #openstack-meeting13:20
yanyan#endmeeting13:20
*** Daisy has joined #openstack-meeting13:21
*** bill_az has joined #openstack-meeting13:21
*** xyang1 has joined #openstack-meeting13:21
yanyanumm, seems after relogging, I'm not the chair of the meeting...13:22
*** yanyan has left #openstack-meeting13:23
*** tiswanso has joined #openstack-meeting13:23
*** cburgess has quit IRC13:23
*** haiwei has quit IRC13:23
*** yanyanhu has joined #openstack-meeting13:24
*** julim has joined #openstack-meeting13:24
yanyanhu#endmeeting13:24
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:24
openstackMeeting ended Tue Aug 18 13:24:33 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:24
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-08-18-13.02.html13:24
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-08-18-13.02.txt13:24
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-08-18-13.02.log.html13:24
*** hrou has joined #openstack-meeting13:25
*** cburgess has joined #openstack-meeting13:26
*** yanyanhu has quit IRC13:27
*** toscalix has quit IRC13:28
*** otter768 has joined #openstack-meeting13:29
*** dims_ has quit IRC13:31
*** dims has joined #openstack-meeting13:31
*** ayoung has joined #openstack-meeting13:31
*** lblanchard has joined #openstack-meeting13:31
*** yamamoto has joined #openstack-meeting13:31
*** singlethink has joined #openstack-meeting13:32
*** ftersin has quit IRC13:33
*** mrunge has quit IRC13:33
*** sankarshan is now known as sankarshan_away13:33
*** otter768 has quit IRC13:34
*** amitgandhinz has joined #openstack-meeting13:35
*** prad_ has joined #openstack-meeting13:39
*** GB21 has quit IRC13:40
*** dims has quit IRC13:40
*** glauco_ has joined #openstack-meeting13:40
*** eharney has quit IRC13:41
*** changbl has quit IRC13:41
*** neelashah has quit IRC13:42
*** VW_ has quit IRC13:42
*** VW_ has joined #openstack-meeting13:43
*** Daisy has quit IRC13:43
*** Daisy has joined #openstack-meeting13:43
*** dims has joined #openstack-meeting13:43
*** jeadr has quit IRC13:45
*** jeadr has joined #openstack-meeting13:46
*** balajiiyer has joined #openstack-meeting13:49
*** pdb is now known as pbourke13:50
*** pbourke has quit IRC13:51
*** claudiub has quit IRC13:51
*** pbourke has joined #openstack-meeting13:51
*** marcusvrn_ has joined #openstack-meeting13:53
*** Daisy has quit IRC13:54
*** Daisy has joined #openstack-meeting13:55
*** claudiub has joined #openstack-meeting13:55
*** xingchao has quit IRC13:56
*** neelashah has joined #openstack-meeting13:56
*** thangp has joined #openstack-meeting13:56
*** kencjohnston has quit IRC13:58
*** dkranz has joined #openstack-meeting13:58
*** kencjohnston has joined #openstack-meeting13:59
*** Daisy has quit IRC13:59
*** singleth_ has joined #openstack-meeting13:59
*** Daisy has joined #openstack-meeting14:00
*** armax has joined #openstack-meeting14:00
*** tiswanso has quit IRC14:00
*** haomaiwang has quit IRC14:01
*** neelashah has quit IRC14:01
*** tiswanso has joined #openstack-meeting14:01
*** singlethink has quit IRC14:01
*** tchaypo has joined #openstack-meeting14:02
*** haomaiwang has joined #openstack-meeting14:02
*** jvrbanac has quit IRC14:02
*** ramishra has joined #openstack-meeting14:02
*** zeih has quit IRC14:02
*** xingchao has joined #openstack-meeting14:02
*** DuncanT has joined #openstack-meeting14:03
*** dims has quit IRC14:04
*** kencjohnston has quit IRC14:04
*** rbak has joined #openstack-meeting14:04
*** Daisy has quit IRC14:04
*** kencjohnston has joined #openstack-meeting14:04
*** otherwiseguy has quit IRC14:04
*** dims has joined #openstack-meeting14:05
*** enikanorov2 has joined #openstack-meeting14:05
*** topol has joined #openstack-meeting14:05
*** topol has quit IRC14:05
*** Murali has quit IRC14:06
*** topol has joined #openstack-meeting14:06
*** nadya has quit IRC14:07
*** jvrbanac has joined #openstack-meeting14:09
*** jckasper has joined #openstack-meeting14:09
*** bobh has joined #openstack-meeting14:10
*** carl_baldwin has joined #openstack-meeting14:10
*** jecarey has joined #openstack-meeting14:11
*** banix has joined #openstack-meeting14:11
*** pm90__ has joined #openstack-meeting14:11
*** sigmavirus24_awa is now known as sigmavirus2414:11
*** phil_h has joined #openstack-meeting14:11
*** esker has joined #openstack-meeting14:12
*** ikhudoshyn has joined #openstack-meeting14:13
*** pm90_ has quit IRC14:14
*** pnavarro|lunch is now known as pnavarro14:14
*** IlyaG has joined #openstack-meeting14:14
*** eharney has joined #openstack-meeting14:14
*** zeih has joined #openstack-meeting14:16
*** otherwiseguy has joined #openstack-meeting14:16
*** emagana has joined #openstack-meeting14:16
*** _amrith_ is now known as amrith14:16
*** rbak has quit IRC14:17
*** ItSANgo has quit IRC14:17
*** adahms has quit IRC14:18
*** xylan_kong has joined #openstack-meeting14:19
*** peristeri has quit IRC14:20
*** annegentle has quit IRC14:20
*** jmckind has joined #openstack-meeting14:21
*** FallenPegasus has joined #openstack-meeting14:23
*** ikhudoshyn has quit IRC14:24
*** prad_ is now known as pradk14:26
*** jeadr has quit IRC14:27
*** afazkas has quit IRC14:27
*** jeadr has joined #openstack-meeting14:28
*** ItSANgo__ has joined #openstack-meeting14:28
*** emagana has quit IRC14:29
*** zul has joined #openstack-meeting14:29
*** adahms has joined #openstack-meeting14:29
*** salv-orlando has joined #openstack-meeting14:30
*** wshao has joined #openstack-meeting14:30
*** amrith is now known as _amrith_14:31
*** sdake has joined #openstack-meeting14:31
*** bvandenh has quit IRC14:32
*** stevemar has joined #openstack-meeting14:32
*** adahms has quit IRC14:32
*** _amrith_ is now known as amrith14:32
*** carl_baldwin has quit IRC14:32
*** rbak has joined #openstack-meeting14:33
*** pnavarro has quit IRC14:34
*** numan has quit IRC14:34
*** salv-orlando has quit IRC14:34
*** jmckind has quit IRC14:34
*** phil_h has quit IRC14:35
*** dims_ has joined #openstack-meeting14:35
*** spzala has joined #openstack-meeting14:36
*** mrunge has joined #openstack-meeting14:37
*** dims has quit IRC14:37
*** zeih has quit IRC14:37
*** sdake_ has joined #openstack-meeting14:37
*** jrist has joined #openstack-meeting14:38
*** jrist has quit IRC14:38
*** jrist has joined #openstack-meeting14:38
*** stevemar has quit IRC14:39
*** bobh has quit IRC14:39
*** stevemar has joined #openstack-meeting14:39
*** sdake has quit IRC14:40
*** cdub has joined #openstack-meeting14:41
*** spzala has quit IRC14:42
*** glauco_ has quit IRC14:42
*** vijendar has joined #openstack-meeting14:42
*** annegentle has joined #openstack-meeting14:44
*** ccavanna has quit IRC14:45
*** GB21 has joined #openstack-meeting14:47
*** enikanorov2 has quit IRC14:48
*** harshs has joined #openstack-meeting14:49
*** glauco_ has joined #openstack-meeting14:50
*** jeadr has quit IRC14:50
*** julim_ has joined #openstack-meeting14:51
*** jeadr has joined #openstack-meeting14:51
*** aorourke_ has joined #openstack-meeting14:51
*** erlon has joined #openstack-meeting14:54
*** zul has quit IRC14:54
*** mtanino has joined #openstack-meeting14:55
*** wshao has quit IRC14:55
*** pbourke_ has joined #openstack-meeting14:57
*** bswartz has quit IRC14:57
*** dan_ has joined #openstack-meeting14:58
*** rromans_ has joined #openstack-meeting14:58
*** alexschm has quit IRC14:58
*** dan_ is now known as Guest3405114:58
*** kencjohnston has quit IRC14:59
*** stevemar has quit IRC14:59
*** pbourke has quit IRC14:59
*** julim has quit IRC14:59
*** dprince has quit IRC14:59
*** comay has quit IRC14:59
*** zhhuabj has quit IRC14:59
*** Piet has quit IRC14:59
*** elo has quit IRC14:59
*** mdavidson has quit IRC14:59
*** park_ has quit IRC14:59
*** jaredrohe has quit IRC14:59
*** jtomasek has quit IRC14:59
*** ityaptin has quit IRC14:59
*** sreshetnyak has quit IRC14:59
*** skraynev has quit IRC14:59
*** finchd has quit IRC14:59
*** rharwood has quit IRC14:59
*** aorourke has quit IRC14:59
*** cody-somerville- has quit IRC14:59
*** wznoinsk has quit IRC14:59
*** dan has quit IRC14:59
*** rromans has quit IRC14:59
*** jorge_munoz has quit IRC14:59
*** Guest34051 is now known as dan14:59
*** haomaiwang has quit IRC15:01
*** dims has joined #openstack-meeting15:01
*** haomaiwang has joined #openstack-meeting15:02
*** yamahata has joined #openstack-meeting15:02
*** achanda has joined #openstack-meeting15:03
*** dims_ has quit IRC15:03
*** julim has joined #openstack-meeting15:04
*** smccully has joined #openstack-meeting15:04
*** achanda has quit IRC15:05
*** sreshetnyak has joined #openstack-meeting15:05
*** ikhudoshyn has joined #openstack-meeting15:05
*** ikhudoshyn has quit IRC15:05
*** stevemar has joined #openstack-meeting15:05
*** comay has joined #openstack-meeting15:06
*** enikanorov2 has joined #openstack-meeting15:06
*** julim_ has quit IRC15:06
*** claudiub has quit IRC15:07
*** amotoki has joined #openstack-meeting15:08
*** zul has joined #openstack-meeting15:09
*** zhhuabj has joined #openstack-meeting15:11
*** dprince has joined #openstack-meeting15:12
*** mdavidson has joined #openstack-meeting15:12
*** park_ has joined #openstack-meeting15:12
*** jaredrohe has joined #openstack-meeting15:12
*** jtomasek has joined #openstack-meeting15:12
*** ityaptin has joined #openstack-meeting15:12
*** skraynev has joined #openstack-meeting15:12
*** finchd has joined #openstack-meeting15:12
*** rharwood has joined #openstack-meeting15:12
*** cody-somerville- has joined #openstack-meeting15:12
*** wznoinsk has joined #openstack-meeting15:12
*** amrith is now known as _amrith_15:12
*** neelashah has joined #openstack-meeting15:12
*** rbowen has joined #openstack-meeting15:13
*** gampel has joined #openstack-meeting15:13
*** elo has joined #openstack-meeting15:14
*** dprince has quit IRC15:16
*** bswartz has joined #openstack-meeting15:17
*** padkrish has joined #openstack-meeting15:18
*** dannywilson has joined #openstack-meeting15:18
*** tsekiyama has joined #openstack-meeting15:19
*** Piet has joined #openstack-meeting15:20
*** ajmiller_ has quit IRC15:22
*** enikanorov2 has quit IRC15:23
*** ociuhandu has joined #openstack-meeting15:23
*** dannywilson has quit IRC15:23
*** singleth_ has quit IRC15:23
*** dannywil_ has joined #openstack-meeting15:23
*** glauco_ has quit IRC15:23
*** rbak has quit IRC15:24
*** jeadr has quit IRC15:24
*** dannywil_ has quit IRC15:24
*** noslzzp has joined #openstack-meeting15:25
*** jeadr has joined #openstack-meeting15:25
*** PrashantS has joined #openstack-meeting15:25
*** dannywilson has joined #openstack-meeting15:25
*** gampel has quit IRC15:26
*** puranamr has joined #openstack-meeting15:26
*** garthb has joined #openstack-meeting15:26
*** garthb_ has joined #openstack-meeting15:26
*** garthb has quit IRC15:27
*** alop has joined #openstack-meeting15:27
*** ganeshna has joined #openstack-meeting15:28
*** ccavanna has joined #openstack-meeting15:28
*** dims has quit IRC15:29
*** maurosr has quit IRC15:29
*** singlethink has joined #openstack-meeting15:30
*** dims has joined #openstack-meeting15:30
*** timello has quit IRC15:30
*** austin81 has joined #openstack-meeting15:30
*** otter768 has joined #openstack-meeting15:30
*** pnavarro has joined #openstack-meeting15:30
*** ganeshna has quit IRC15:30
*** rbak has joined #openstack-meeting15:30
*** VW_ has quit IRC15:31
*** ganeshna has joined #openstack-meeting15:31
*** emagana has joined #openstack-meeting15:31
*** VW_ has joined #openstack-meeting15:31
*** salv-orlando has joined #openstack-meeting15:33
*** hhuang has quit IRC15:34
*** otter768 has quit IRC15:35
*** pballand has joined #openstack-meeting15:35
*** VW_ has quit IRC15:35
*** pnavarro has quit IRC15:36
*** hhuang has joined #openstack-meeting15:36
*** pnavarro has joined #openstack-meeting15:36
*** xylan_kong has quit IRC15:36
*** ramishra has quit IRC15:36
*** DuncanT has quit IRC15:36
*** tchaypo has quit IRC15:36
*** marcusvrn_ has quit IRC15:36
*** erlon has quit IRC15:36
*** maurosr has joined #openstack-meeting15:36
*** timello has joined #openstack-meeting15:37
*** dkranz has quit IRC15:37
*** ganeshna_ has joined #openstack-meeting15:39
*** Swami has joined #openstack-meeting15:40
*** jeadr has quit IRC15:40
*** ganeshna has quit IRC15:40
*** jeadr has joined #openstack-meeting15:41
*** padkrish has quit IRC15:43
*** jecarey has quit IRC15:43
*** emagana_ has joined #openstack-meeting15:44
*** moha_hunt has joined #openstack-meeting15:44
*** dims has quit IRC15:45
*** ganeshna_ has quit IRC15:45
*** zul has quit IRC15:46
*** spzala has joined #openstack-meeting15:46
*** ganeshna has joined #openstack-meeting15:46
*** geoffarnold has joined #openstack-meeting15:46
*** dims has joined #openstack-meeting15:47
*** emagana has quit IRC15:47
*** erlon has joined #openstack-meeting15:49
*** geoffarnold has quit IRC15:50
*** geoffarnold has joined #openstack-meeting15:50
*** KunalGandhi has joined #openstack-meeting15:51
*** afazkas has joined #openstack-meeting15:52
*** carl_baldwin has joined #openstack-meeting15:52
*** ganeshna has quit IRC15:52
*** dflorea has joined #openstack-meeting15:53
*** ganeshna has joined #openstack-meeting15:53
*** mestery has joined #openstack-meeting15:54
*** nadya has joined #openstack-meeting15:55
*** dkranz has joined #openstack-meeting15:57
*** eharney has quit IRC15:58
*** Apoorva has joined #openstack-meeting15:58
*** ajmiller has joined #openstack-meeting15:58
*** marcusvrn_ has joined #openstack-meeting15:59
*** eharney has joined #openstack-meeting15:59
*** Apoorva has quit IRC15:59
*** rbak has quit IRC16:00
*** lsmola has quit IRC16:00
*** haomaiwang has quit IRC16:01
*** Apoorva has joined #openstack-meeting16:01
*** haomaiwang has joined #openstack-meeting16:01
*** balajiiyer has quit IRC16:01
*** rbak has joined #openstack-meeting16:03
*** glauco_ has joined #openstack-meeting16:03
*** bswartz has quit IRC16:04
*** haomaiwang has quit IRC16:04
*** jecarey has joined #openstack-meeting16:04
*** bswartz has joined #openstack-meeting16:06
*** vahidh has joined #openstack-meeting16:07
*** rbak has quit IRC16:08
*** BharatK has quit IRC16:10
*** tchaypo has joined #openstack-meeting16:11
*** matrohon has quit IRC16:11
*** ramishra has joined #openstack-meeting16:12
*** DuncanT has joined #openstack-meeting16:12
*** rbak has joined #openstack-meeting16:13
*** rbak has quit IRC16:14
*** aimon_ has quit IRC16:16
*** emagana_ has quit IRC16:17
*** xingchao has quit IRC16:19
*** jcoufal has quit IRC16:20
*** cdub has quit IRC16:20
*** dguryanov has quit IRC16:21
*** rbak has joined #openstack-meeting16:21
*** pbourke_ is now known as pbourke16:21
*** alexsyip has joined #openstack-meeting16:23
*** rbak has quit IRC16:24
*** Piet has quit IRC16:24
*** leeantho has joined #openstack-meeting16:25
*** xylan_kong has joined #openstack-meeting16:26
*** unicell has quit IRC16:26
*** moha_hunt has quit IRC16:26
*** geoffarnold has quit IRC16:27
*** Piet has joined #openstack-meeting16:31
*** Piet has quit IRC16:31
*** Piet has joined #openstack-meeting16:31
*** rbak has joined #openstack-meeting16:32
*** jhenner has quit IRC16:34
*** devvesa has quit IRC16:34
*** sdake_ is now known as sdake16:34
*** esker has quit IRC16:34
*** jmh has joined #openstack-meeting16:36
*** wshao has joined #openstack-meeting16:36
*** elo1 has joined #openstack-meeting16:36
*** jmh is now known as Guest621116:36
*** dims has quit IRC16:36
*** noslzzp has quit IRC16:37
*** IanGovett1 has joined #openstack-meeting16:38
*** scheuran has quit IRC16:38
*** dims has joined #openstack-meeting16:39
*** ganeshna_ has joined #openstack-meeting16:39
*** Piet has quit IRC16:39
*** dprince has joined #openstack-meeting16:40
*** IanGovett has quit IRC16:40
*** annegentle has quit IRC16:41
*** ganeshn__ has joined #openstack-meeting16:42
*** afazkas has quit IRC16:42
*** krtaylor has quit IRC16:43
*** ganeshna has quit IRC16:43
*** aranjan has joined #openstack-meeting16:44
*** vivek-ebay has joined #openstack-meeting16:45
*** ganeshna_ has quit IRC16:46
*** gothicmi1dfood has joined #openstack-meeting16:47
*** gothicmi1dfood has quit IRC16:48
*** gothicmindfood has quit IRC16:48
*** PrashantS has quit IRC16:48
*** gothicmindfood has joined #openstack-meeting16:48
*** rbak has quit IRC16:49
*** PrashantS has joined #openstack-meeting16:49
*** wshao has quit IRC16:49
*** jroyal has quit IRC16:50
*** ivar-lazzaro has joined #openstack-meeting16:50
*** rromans_ is now known as rromans_afk16:51
*** patrickeast has joined #openstack-meeting16:52
*** padkrish has joined #openstack-meeting16:53
*** dims has quit IRC16:54
*** ganeshna has joined #openstack-meeting16:54
*** unicell has joined #openstack-meeting16:55
*** ganeshna_ has joined #openstack-meeting16:55
*** krtaylor has joined #openstack-meeting16:56
*** VW_ has joined #openstack-meeting16:57
*** dims has joined #openstack-meeting16:57
*** ganeshn__ has quit IRC16:57
*** aimon has joined #openstack-meeting16:57
*** rbak has joined #openstack-meeting16:58
*** shashank_hegde has joined #openstack-meeting16:58
*** ganeshna has quit IRC16:59
*** _amrith_ is now known as amrith16:59
*** ganeshna has joined #openstack-meeting17:00
*** padkrish has quit IRC17:00
*** docaedo has joined #openstack-meeting17:00
*** elo1 has quit IRC17:01
krtaylor#startmeeting third-party17:01
openstackMeeting started Tue Aug 18 17:01:46 2015 UTC and is due to finish in 60 minutes.  The chair is krtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: third-party)"17:01
openstackThe meeting name has been set to 'third_party'17:01
krtaylorhey everybody, its that time again17:02
krtayloranyone here for CI working group?17:02
rfolcoo/17:02
mmedvedehey krtaylor17:02
*** ajmiller has quit IRC17:02
patrickeasthey17:02
*** dims_ has joined #openstack-meeting17:02
*** dflorea has quit IRC17:02
krtaylorhi rfolco mmedvede patrickeast17:03
krtaylorpatrickeast, havent seen you in a while17:03
*** VW_ has quit IRC17:03
*** ganeshna_ has quit IRC17:03
*** VW_ has joined #openstack-meeting17:03
*** Piet has joined #openstack-meeting17:04
*** VW_ has quit IRC17:04
*** penick has joined #openstack-meeting17:04
sweston\o17:04
krtaylorhere's the agenda for today:17:04
asselin_hi, I'm half here17:04
krtaylor#link https://wiki.openstack.org/wiki/Meetings/ThirdParty#8.2F18.2F15_1700_UTC17:04
*** dims has quit IRC17:04
*** VW_ has joined #openstack-meeting17:04
krtaylorhi sweston asselin_17:04
swestonhi krtaylor17:04
krtaylorany quick announcements? deadlines?17:05
*** nadya has quit IRC17:05
*** luqas has joined #openstack-meeting17:05
krtaylornone on the agenda17:05
*** ganeshna has quit IRC17:05
krtaylor#topic Common CI17:06
*** openstack changes topic to "Common CI (Meeting topic: third-party)"17:06
krtaylorasselin_ I understand if you are too busy to discuss17:06
krtaylorLOTS of patches17:07
*** penick_ has joined #openstack-meeting17:07
*** mestery has quit IRC17:07
krtaylor#link https://review.openstack.org/#/q/topic:downstream-puppet,n,z17:07
asselin_no updates from me. Still working through patches and reviews. There's progress which is good news.17:07
*** carl_baldwin has quit IRC17:07
krtaylorseveral look really close to merge17:07
*** ganeshna has joined #openstack-meeting17:07
*** rbak has quit IRC17:08
*** dims has joined #openstack-meeting17:08
*** padkrish has joined #openstack-meeting17:09
*** rbowen has quit IRC17:09
*** dims_ has quit IRC17:09
*** elo1 has joined #openstack-meeting17:09
krtaylorok, next then17:09
krtaylor#topic Spec to have infra host scoreboard17:09
*** openstack changes topic to "Spec to have infra host scoreboard (Meeting topic: third-party)"17:09
krtaylorthis is moving along17:09
*** penick has quit IRC17:10
*** penick_ is now known as penick17:10
krtayloralthough not NEARLY as fast as we were hoping when jeblair and I first discussed this idea17:10
*** jroyal has joined #openstack-meeting17:10
*** IanGovett1 has quit IRC17:10
krtaylorthe idea was to push this out fast, then start working on radar17:10
krtaylorsigh17:10
mmedvedethe main block is that it would not be as temporarily as initially was intended17:11
krtayloranyway, it should be fairily close if we can et reviewers17:11
krtaylorwhy couldn't it be mmedvede ?17:11
*** dims_ has joined #openstack-meeting17:11
swestonwhat can folks do to hurry it along?17:11
patrickeastill try and take another look at it today17:11
* patrickeast has been busy with cinder things :(17:11
*** ganeshna_ has joined #openstack-meeting17:11
*** rbak has joined #openstack-meeting17:12
mmedvedebecause we are asking infra team to deploy it, there needs to be infrastructure for maintaining it17:12
krtaylor#link https://review.openstack.org/#/c/194437/17:12
mmedvedeI am writing puppet module to deploy scoreboard. Almost done17:12
*** MeganR has left #openstack-meeting17:13
krtaylorit would be good to get more reviews so I could stop having to push a refresh for every nit17:13
swestoncan this be set up in such a way that when we are ready to suggest radar hosting, it can be easily dropped in?17:14
*** dims has quit IRC17:14
mmedvedepatrickeast: should we name puppet module puppet-ci_scoreboard or puppet-scoreboard?17:14
krtaylormmedvede, for the naming, there are so many dashboards now proposed, I felt it added clarity without too much overhead17:14
krtaylorbut will change it if you feel strongly about it17:15
*** jroyal has quit IRC17:15
*** bswartz has quit IRC17:15
*** ganeshna has quit IRC17:15
krtaylorsweston, that is the intention, at least the url, vm, etc would be there17:15
swestonkrtaylor: good enough17:15
mmedvedekrtaylor: no strong feelings. If people agree with naming, need more opinions17:16
*** jroyal has joined #openstack-meeting17:16
patrickeastyea i don't really have strong feelings on the puppet module naming either17:16
*** claudiub has joined #openstack-meeting17:17
krtaylordarn white space, I checked it too (then added that line) sigh17:17
krtayloranyway, new patchset pushed just now17:17
*** yamahata has quit IRC17:17
*** ayoung has quit IRC17:17
*** tim_o has joined #openstack-meeting17:17
krtaylorcheck it out and review, the more +1's we get on it, the more likely that the infra folks will assist17:17
*** padkrish has quit IRC17:18
*** ganeshna has joined #openstack-meeting17:18
*** bswartz has joined #openstack-meeting17:18
*** ndipanov has joined #openstack-meeting17:18
mmedvedekrtaylor: my -1 was not about whitespace. I try not to -1 for style17:18
swestonWill do17:18
mmedvedeit was for section still missing about gerrit account requirement17:18
krtaylormmedvede, understood, all good, I didn't think so17:19
krtayloroh, I didn't add that, crap17:19
krtaylorwill do17:19
*** aimon has quit IRC17:19
*** dims_ has quit IRC17:20
krtaylormmedvede, what do you think? I feel like it should have it's own id17:20
*** aimon has joined #openstack-meeting17:20
*** boris-42 has quit IRC17:20
*** absubram has joined #openstack-meeting17:20
*** dims has joined #openstack-meeting17:20
*** jeadr has quit IRC17:20
*** aimon has quit IRC17:20
*** dims has quit IRC17:20
*** aimon has joined #openstack-meeting17:21
krtayloranyone else have any comments on the hosting spec?17:21
*** dims has joined #openstack-meeting17:21
mmedvedekrtaylor: it might be a necessity17:21
krtaylormmedvede, agreed17:21
*** ganeshna_ has quit IRC17:21
*** jeadr has joined #openstack-meeting17:21
mmedvedepatrickeast: do you think the scoreboard would be able to handle the load once it is used by more people?17:21
*** emagana has joined #openstack-meeting17:21
*** jichen has quit IRC17:21
*** ganeshna has quit IRC17:21
*** PrashantS has quit IRC17:21
krtaylormmedvede, I based this spec on other hosting specs, and it was not mentioned in them, it may be a "given"17:21
*** shashank_hegde has quit IRC17:21
*** luqas has quit IRC17:22
mmedvedepatrickeast: is uses flask. I know it is possible to also use apache along flask to make it more resilient17:22
patrickeastmmedvede: maybe, my biggest concern would be how it is serving static files we should at some point switch it to using apache or something17:22
*** PrashantS has joined #openstack-meeting17:22
patrickeastmmedvede: yea exactly17:22
krtayloror put that work into radar17:22
*** geoffarnold has joined #openstack-meeting17:22
*** elo1 has quit IRC17:22
patrickeastmmedvede: it should be ok, the one i have in a little aws vm uses like <2GB of ram peak and like .1 cpu load on average17:23
*** elo1 has joined #openstack-meeting17:23
mmedvedekrtaylor: hmm, maybe. I wanted to make the account requirement explicit, so infra team knows what they are getting into :)17:23
patrickeastmmedvede: i don't anticipate a ton more folks would start hitting it17:23
*** ganeshna has joined #openstack-meeting17:23
krtaylor.1, that much  :)17:23
krtaylormmedvede, I'll add it right after this, thought I did17:24
krtaylortoo many tasks atm17:24
*** wshao has joined #openstack-meeting17:24
mmedvedepatrickeast: I remember you aws instance was down sometimes, did you figure out the reason?17:24
patrickeast' 17:21:11 up 169 days, 16:59,  1 user,  load average: 0.10, 0.10, 0.13 '17:24
patrickeastfrom uptime17:24
*** jhenner has joined #openstack-meeting17:25
patrickeastmmedvede: its something wrong with flask/python socket handling, i haven't tracked it down yet but also haven't had much time to look at it17:25
*** yamamoto has quit IRC17:25
*** ebalduf has joined #openstack-meeting17:25
mmedvedepatrickeast: I think after official announcement, the ci-dashboard.o.o might get more traffic. We can try to harden it, but it would be easier once it is running.17:26
patrickeastmmedvede: would probably be fixed if we migrate towards an apache integrated solution17:26
*** PrashantS has quit IRC17:26
*** achanda has joined #openstack-meeting17:27
*** ganeshna has quit IRC17:27
krtaylormmedvede, I am proposing a Work Item to create a user account for 'ci-dashboard'17:27
krtaylorsee any problems with that?17:27
krtaylorthought a generic account name could be reused for whatever solution is deployed in the future17:28
*** padkrish has joined #openstack-meeting17:28
mmedvedekrtaylor: the thing is, it would need to be account managed by infra team17:29
mmedvedee.g. they would need to manage private ssh key17:29
*** IanGovett has joined #openstack-meeting17:29
krtaylormmedvede, wouldn't that be a work item?17:29
krtaylorso you are thinking a dependency?17:30
*** britthouser has joined #openstack-meeting17:30
*** otter768 has joined #openstack-meeting17:31
mmedvedekrtaylor:  Are you talking about work item inside the spec?17:31
*** SumitNaiksatam has joined #openstack-meeting17:31
krtayloryes, in the Work Item section17:31
krtaylorI can note that it would need to be created and maintained by the infra team17:32
mmedvede+117:32
krtaylorsince none of us have that acls17:32
*** s3wong has joined #openstack-meeting17:32
krtaylorok, cool, I'll finish that asap17:33
krtaylorany other comments on hosting the dashboard spec?17:33
*** britthou_ has quit IRC17:33
krtaylorBTW, lightning session topic: "Using CI Dashboard to check on a CI system's health"17:34
krtaylorfor Tokyo17:34
krtaylorI'm just sayin....  :)17:34
krtaylorok, let's move on17:35
krtaylor#topic Radar spec17:35
*** openstack changes topic to "Radar spec (Meeting topic: third-party)"17:35
*** otter768 has quit IRC17:35
krtaylorsweston graciously moved the spec to our third party tool repo17:36
krtaylor#link https://review.openstack.org/#/c/211713/17:36
*** whenry has joined #openstack-meeting17:36
*** jprovazn has quit IRC17:36
*** padkrish has quit IRC17:36
*** rbak has quit IRC17:37
krtaylorso, there are two ways to address this17:37
krtaylor1) is to merge it then patch it for spec changes17:37
krtaylor2) is to wait till we all agree on its content them merge it meaning that the design is complete17:37
krtaylorI am leaning toward 117:37
krtaylorcomments?17:37
mmedvedethe (2) kind of defeats the purpose of moving it17:38
*** pvaneck has joined #openstack-meeting17:38
swestonI am leaning toward 1 as well, this spec has been hanging too long for approval, and it is blocking progress17:38
mmedvedewe could work on it at its original location17:38
*** dflorea has joined #openstack-meeting17:38
krtaylorwell, moving it always implied that it would be re-proposed to infra after we worked on it17:38
krtaylormmedvede, yes, long history here, it was agreed to move it17:39
krtaylormmedvede, that would have been the preferred approach, but it was too confusing for some reason17:40
krtaylorwe can't wait to improve CI system trust17:40
krtaylorthe sytems that are busting their behinds to push reliable results need to be trusted17:41
krtaylorand in order to do that we have to show developers the test results17:41
*** alop has quit IRC17:41
krtaylorhence, the tactical/strategic approach17:42
*** austin81 has left #openstack-meeting17:42
swestonkrtaylor: +117:42
* krtaylor gets off his soapbox17:42
*** dflorea has quit IRC17:42
*** dflorea has joined #openstack-meeting17:42
*** padkrish has joined #openstack-meeting17:43
krtaylorso, do we agree on merging it first, then patching design ideas and corrections?17:43
*** jckasper has quit IRC17:43
*** glauco_ has quit IRC17:43
krtaylorif no one disagrees, then I'll merge it this afternoon17:44
swestonkrtaylor: I vote for merging it as it is now.  I will be writing Gerrit queries and integrating some data into Radar over the next two weeks, and I would prefer to have the spec approved17:44
patrickeast+1 for merging it17:44
mmedvedehard for me to have a good opinion, I did not work on many specs to understand what is best, so I abstain :)17:45
*** tsymanczyk has joined #openstack-meeting17:45
*** geoffarnold has quit IRC17:45
*** yamahata has joined #openstack-meeting17:45
asselin_+1 merge17:45
krtaylordone17:45
*** changbl has joined #openstack-meeting17:46
krtaylorso, next up17:46
krtaylor#topic Patches17:46
*** openstack changes topic to "Patches (Meeting topic: third-party)"17:46
krtaylor#link https://review.openstack.org/#/q/project:stackforge/third-party-ci-tools+status:open,n,z17:46
* krtaylor looking17:47
*** vivek-ebay has quit IRC17:47
patrickeasti need to update my FC passthrough one17:47
*** geoffarnold has joined #openstack-meeting17:47
patrickeastasselin_: did you and hemnafk figure out how to get the offline check one to work?17:48
*** padkrish has quit IRC17:48
asselin_patrickeast, that's on hold a bit17:48
krtaylorpatrickeast, looks like some minor changes17:49
asselin_patrickeast, I'd like to get your landed first, and then look at detaching at the end of the job17:49
*** rbowen has joined #openstack-meeting17:49
krtaylorpatrickeast, explain offline check?17:49
asselin_and then include the offline check17:49
patrickeastkrtaylor: the HBA's can get into an 'offline' state17:49
patrickeastkrtaylor: and then the passthrough will fail17:49
*** rbak has joined #openstack-meeting17:49
patrickeastkrtaylor: the idea is to have some notification early on that it is happening17:50
patrickeastasselin_: that makes sense17:50
krtaylorah, interesting, thanks for the education17:50
asselin_patrickeast, or include that check adter the detach before the attach17:50
asselin_patrickeast, perhaps we can make it more general, when fc fails altogether, send an e-mail (if configured)17:51
*** wshao has quit IRC17:51
patrickeastasselin_: yea i was thinking it might be a better nagios kind of check since they don't seem to recover automatically17:52
patrickeastneeds some manual intervention (right now)17:52
*** ociuhandu has quit IRC17:52
*** jckasper has joined #openstack-meeting17:52
*** sudipto has joined #openstack-meeting17:53
krtaylorah, it is well documented in the next patch, my bad17:53
*** dkranz has quit IRC17:53
*** vivek-ebay has joined #openstack-meeting17:53
krtaylorso a quick open discussion then17:54
*** rbak has quit IRC17:54
krtaylor#topic Open Discussion17:54
*** openstack changes topic to "Open Discussion (Meeting topic: third-party)"17:54
mmedvedekrtaylor: there was another topic, about stackforge migration17:54
mmedvedesmall thing - we need to remember to add our repo to the list17:54
*** sridhar_ram has joined #openstack-meeting17:54
mmedvede#link http://lists.openstack.org/pipermail/openstack-infra/2015-August/003069.html17:54
krtaylorah, just added, I needed to refresh17:54
mmedvedethat is all for that :). I do not believe there is a wiki page yet17:55
*** harshs_ has joined #openstack-meeting17:55
*** garthb_ has quit IRC17:55
krtaylormmedvede, yeah, not seeing a page yet17:56
*** harshs has quit IRC17:56
*** harshs_ is now known as harshs17:56
krtaylorbut it is good to keep that on the agenda, we don't want to miss the "move"17:57
krtaylorthanks mmedvede17:57
*** banix has quit IRC17:57
krtaylorany other topics?17:57
*** breton has joined #openstack-meeting17:58
asselin_I've been running into a recent issue with nodepool and juno openstack clouds.17:58
patrickeastasselin_: i have been having issues with it too, what problem are you getting?17:58
asselin_don't update unnecessarily...still working on the fix17:58
asselin_{"error": {"message": "Project ID not found: admin (Disable debug mode to suppress these details.)", "code": 401, "title": "Unauthorized"}}[17:59
*** dflorea has quit IRC17:59
*** samueldmq has joined #openstack-meeting17:59
*** dflorea has joined #openstack-meeting17:59
asselin_{"error": {"message": "User e082a15d2e6b490ba8329e60e7f092ea is unauthorized for tenant admin (Disable debug mode to suppress these details.)", "code": 401, "title": "Unauthorized"}}[17:59
*** browne has joined #openstack-meeting17:59
krtaylorthanks everyone!17:59
swestonThanks!!18:00
*** henrynash has joined #openstack-meeting18:00
krtaylor#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Tue Aug 18 18:00:13 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-08-18-17.01.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-08-18-17.01.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-08-18-17.01.log.html18:00
*** aranjan has quit IRC18:00
bretonauthorized? Someone said auth?18:00
*** roxanaghe_ has joined #openstack-meeting18:00
*** jamielennox has joined #openstack-meeting18:00
bretono/18:00
*** roxanaghe_ has quit IRC18:00
*** Haneef__ has joined #openstack-meeting18:00
*** ajmiller has joined #openstack-meeting18:00
henrynashthe sun’s over yee yard armmm18:01
*** roxanaghe_ has joined #openstack-meeting18:01
dstanekping ajayaa, amakarov, ayoung, 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, vivekd, wanghong18:01
lbragstaddstanek: o/18:01
ericksonsantoso/18:01
morgan_2549o/18:01
tsymanczyko/18:01
samueldmqhey o/18:01
*** aranjan has joined #openstack-meeting18:01
raildoo_18:01
*** fedora has joined #openstack-meeting18:01
jamielennoxo/18:01
dstanekthat's a terrible roll call18:02
brownehi18:02
*** novas0x2a|laptop has joined #openstack-meeting18:02
rodrigodshi18:02
*** tiswanso has quit IRC18:02
henrynashje suis ici18:02
stevemardstanek: o/18:02
dstanek#startmeeting keystone18:02
openstackMeeting started Tue Aug 18 18:02:53 2015 UTC and is due to finish in 60 minutes.  The chair is dstanek. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
samueldmqhenrynash, très bien :)18:02
*** vivek-ebay has quit IRC18:02
*** openstack changes topic to " (Meeting topic: keystone)"18:02
openstackThe meeting name has been set to 'keystone'18:02
dstaneknot a ton today!18:03
dstanek#topic Agenda18:03
*** openstack changes topic to "Agenda (Meeting topic: keystone)"18:03
*** ayoung has joined #openstack-meeting18:03
dstanek#link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:03
dstaneklbragstad: you in here?18:03
*** tiswanso has joined #openstack-meeting18:03
* stevemar will probably be a bit quiet while he finishes up lunch18:03
lbragstaddstanek: yep18:03
ayoungoyez18:03
dstanek#topic Voting on SPFE for IdP Specific WebSSO18:03
*** openstack changes topic to "Voting on SPFE for IdP Specific WebSSO (Meeting topic: keystone)"18:03
dstanek#link https://review.openstack.org/#/c/199339/2 is the spec18:03
henrynashtype and chew, type and chew18:03
*** vivekd has joined #openstack-meeting18:03
*** jhenner has quit IRC18:03
dstanek#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/071131.html is the mailing list discussion18:03
dstaneklbragstad: go fer it18:03
lbragstadis jamielennox here?18:03
jamielennoxya18:04
lbragstadcool, just wanted to get an idea for how people felt about this as an SPFE?18:04
lbragstadI think what jamielennox has is a good solution for the public cloud cases18:04
*** balajiiyer has joined #openstack-meeting18:04
stevemar+1 on it being a spfe18:04
lbragstad(which have been brought up and highlighted on the mailing list)18:04
ayoungthe current is too limiting...need what jamielennox is proposing for any sane deployment18:04
dstaneklbragstad: want to give the 10 second overview?18:05
lbragstadbasically,18:05
henrynash(and how much code are we talkin’ here)18:05
lbragstadwe would be adding a call to keystone federation that would allow us to get federated authentication based on the IdP id18:05
lbragstadand the protocol18:05
*** banix has joined #openstack-meeting18:05
lbragstadlike this call; https://github.com/openstack/keystone/blob/master/keystone/contrib/federation/routers.py#L80-L8118:06
lbragstadbut specific for an IdP18:06
*** shashank_hegde has joined #openstack-meeting18:06
*** fedora has quit IRC18:06
dstanekhenrynash: when we were talking about it last week it didn't seem like a lot18:06
henrynashdstanek: that would be my guess18:07
stevemarhenrynash: very little new code18:07
*** IanGovett1 has joined #openstack-meeting18:07
lbragstadso, it would kinda look like http://goo.gl/80yyjF18:07
*** glauco_ has joined #openstack-meeting18:07
stevemarit should just be the new route, thats about it18:07
dstanekquestions, comments or concerns? or just vote?18:07
*** amotoki has quit IRC18:07
lbragstadwhere step 3 would be the new stuff being added in the SPFE18:07
lbragstadso, this part - /v3/OS-FEDERATION/identity_providers/{idp_id}/protocol/{protocol_id}/websso/18:08
topolo/18:08
*** gyee has joined #openstack-meeting18:08
*** PrashantS has joined #openstack-meeting18:08
jamielennoxso i consider this a blocker for doing some of chadwick's horizon based discovery, or properly running a lot of different protocols on the same websso page, the concern is obviously how close we are to feature freeze18:09
*** PrashantS has quit IRC18:09
*** PrashantS has joined #openstack-meeting18:09
*** PrashantS has quit IRC18:09
*** IanGovett has quit IRC18:09
ayoungI think it is fine...won't break anyone18:09
jamielennoxbut i expect if we get the go ahead there can be code up in the next day or two and it should be a relatively easy revie18:09
jamielennoxw18:09
ayoungexisting code will run fine18:09
dstanekif we are really talking about a route and a few controller lines is there much risk or regressions elsewhere?18:10
*** PrashantS has joined #openstack-meeting18:10
lbragstadI'm stepping up to sponsor this, so i'll have eyes on reviews as soon as they are posted18:10
jamielennoxit's more of a refactoring of existing code than anything new18:10
dstanekwho will be coding it?18:10
lbragstadI can help out with the coding, but I'd feel comfortable if jamielennox reviewed it18:11
stevemarspec says jamie or lance :)18:11
jamielennoxlbragstad and I will manage between us18:11
lbragstadjamielennox: ++18:11
*** fedora has joined #openstack-meeting18:11
dstanekok, then we can hold both of your feet to the fire18:11
dstanek#startvote Approve SPFE for IdP Specific WebSSO? yes,no,dont_care18:11
openstackBegin voting on: Approve SPFE for IdP Specific WebSSO? Valid vote options are yes, no, dont_care.18:11
openstackVote using '#vote OPTION'. Only your last vote counts.18:11
henrynashso I minded to support this….my concren is whether manyof our cores are off coding real late in the cycle and not available for reviews…and we have some big stuff yet to get in  (e.g. reseller)18:12
stevemar#vote yes18:12
lbragstad#vote yes18:12
ayoung#vote yes18:12
rodrigods#vote yes18:12
*** salv-orlando has quit IRC18:12
stevemarhenrynash: reasonable thing to be worried about18:12
bknudson#vote yes18:12
raildo#vote yes18:12
bknudsonwhy do we even have a spec freeze?18:13
stevemarbknudson: process for the sake of proces18:13
morgan_2549#vote dont_care18:13
jamielennoxbknudson: at least it makes things difficult at this point18:13
henrynash#vote no (even though I love the feature…we need cores doing reviews)18:13
openstackhenrynash: no (even though I love the feature…we need cores doing reviews) is not a valid option. Valid options are yes, no, dont_care.18:13
henrynash#vote no18:13
dstanek#vote i'll let the cards fall where they fall18:13
openstackdstanek: i'll let the cards fall where they fall is not a valid option. Valid options are yes, no, dont_care.18:14
bknudsonI agree with henrynash but if cores don't want to do reviews they're not going to do them.18:14
ayounghenrynash, this is a small one code wise, but big feature for end users18:14
dstanekbknudson, henrynash: yeah, we definitely need more reviews18:14
breton#vote yes18:14
dstanekvote closing in 5..18:14
jamielennox#vote yes18:14
henrynashayoung: I’m sure that’s true….but....18:14
bknudson5 hours?18:14
jamielennoxand i was thinking about it..18:14
ayoungit allows a singe IdP to support multipe protocols for Federation18:14
lbragstadbknudson: long running votes18:14
dstanek#endvote18:14
openstackVoted on "Approve SPFE for IdP Specific WebSSO?" Results are18:14
openstackyes (8): rodrigods, lbragstad, ayoung, bknudson, jamielennox, raildo, breton, stevemar18:14
openstackdont_care (1): morgan_254918:14
henrynashayoung: I love the fetaure, don’t get me wrounf18:14
openstackno (1): henrynash18:14
dstanekbknudson: nope, done ... need to move on!18:15
lbragstadthanks all18:15
dstanekroxanaghe_: you here?18:15
roxanaghe_dstanek, yes18:15
ayounghenrynash, we need to push right up until Milestone 3.  There is not enough time to get work done in the release the way we have things tstrucutured nw18:15
*** IanGovett has joined #openstack-meeting18:15
dstanek#action lbragstad and/or jamielennox to code up the IdP specific WebSSO flow18:15
dstanek#topic Change default endpoint type for Keystone v3 to 'public'18:15
*** openstack changes topic to "Change default endpoint type for Keystone v3 to 'public' (Meeting topic: keystone)"18:15
dstanek#link https://review.openstack.org/#/c/185200/ is the review18:16
dstanekroxanaghe_: you're up18:16
jamielennoxi would suggest we revist next week where we want to have things more or less merged18:16
*** MeganR has joined #openstack-meeting18:16
roxanaghe_ok, so this review has been sitting there for a while18:16
*** dflorea has quit IRC18:16
roxanaghe_we need a decision18:16
dstanekjamielennox: ++18:16
*** padkrish has joined #openstack-meeting18:16
roxanaghe_it's about changing default endpoint type for v3 keystone to public18:16
samueldmqjamielennox, ++ for all the big subjects we are planning to get this cycle18:16
roxanaghe_all other services have public by default18:17
*** moha_hunt has joined #openstack-meeting18:17
*** IanGovett1 has quit IRC18:17
roxanaghe_but there are concerns about breaking stuff if we just change it like that18:17
*** geoffarnold has quit IRC18:17
breton++ for that18:17
breton*for the switch18:17
jamielennoxi'm pretty sure this is changed using sessions18:17
*** geoffarnold has joined #openstack-meeting18:18
jamielennoxlooking for the code to back me up there18:18
*** yottatsa has joined #openstack-meeting18:18
*** jeadr has quit IRC18:18
ayoungwhat does that mean "default" anyway?18:19
Haneef__All the services use public_endpoint from catalog except keystone.18:19
jamielennoxhttps://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/auth/identity/base.py#L31318:19
*** jeadr has joined #openstack-meeting18:19
jamielennoxso to my understanding this was the compromise to having fixed this in the past18:20
jamielennoxthat if you use the Client(session) format without specifying an interface you would get public18:20
*** dannywilson has quit IRC18:20
tim_oasselin?18:20
jamielennox(because i completely agree the admin default is wrong)18:20
dstanekjamielennox: does that mean we don't need the proposed change or that it's likely to break less than we think?18:21
roxanaghe_jamielennox, from what I saw the default is in httpclient and is the same for v2 and v3: admin18:21
bknudsonfor v2 if you use the public interface then a lot of calls aren't going to work.18:21
jamielennoxdstanek: given that the admin and public interface for v3 is the same it's probably not going to break as much as i would think18:22
*** megm has quit IRC18:22
*** ivar-lazzaro has quit IRC18:22
jamielennoxroxanaghe_: if you use session then it should do it's best to skip httpclient18:22
Haneef__We want to make this change only for keystone v3, as v2 is bit differnet. In v2 only subset of apis are exposed at public endpoint. That is the reason why defaulted to admin18:22
bknudsonso maybe applications can already opt-in to the behavior by using sessions.18:23
bknudsonand it's deprecated to not use a session18:23
jamielennoxoh, blah https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/httpclient.py#L23718:23
roxanaghe_jamielennox, ok, I'm not sure if the current code goes that code flow18:23
roxanaghe_jamielennox - yes, that's the line18:24
*** Piet has quit IRC18:24
*** yottatsa has quit IRC18:24
jamielennoxok, so v3 default is going to end up as admin18:24
*** IanGovett has quit IRC18:24
jamielennoxumm18:24
*** Ravikiran_K_ has quit IRC18:25
*** IanGovett has joined #openstack-meeting18:25
roxanaghe_so since no value is passed at that point it will get the default admin18:25
*** epcim has joined #openstack-meeting18:25
*** yassine__ has quit IRC18:25
*** dannywilson has joined #openstack-meeting18:25
roxanaghe_so are there any concerns if we switch?18:25
*** yamamoto has joined #openstack-meeting18:26
ayounglets just drop v2, and then admin,public is ireelevant18:26
jamielennoxok, i think we can change that18:26
jamielennoxit's a behaviour change but i would be very surprised if anyone is relying upon it18:26
bknudsonI'm concerned that it will break somebody.18:26
dstanekwhat about bknudson's worry about breaking existing applications?18:26
jamielennoxgiven admin/public is the same thing18:26
jamielennoxthe other option is we are planning a client v2 start of next cycle18:26
*** dflorea has joined #openstack-meeting18:27
*** geoffarnold has quit IRC18:28
roxanaghe_sinve admin and public go through the same endpoint is it possible to break anyone?18:28
roxanaghe_*since18:28
*** IanGovett1 has joined #openstack-meeting18:28
jamielennoxroxanaghe_: it goes through the same code but most people will configure admin and public to use different urls, admin is often not routable by the public18:28
ayoungbreak it18:28
jamielennoxi'm ok to break it18:29
ayoungvote?18:29
*** jeadr has quit IRC18:29
dstaneksure...18:29
roxanaghe_jamielenox ok, so if only admin is configured - we have now in openstack cli a new option to specify the interface - that could help18:30
*** ivar-lazzaro has joined #openstack-meeting18:30
dstanek#startvote Do we want to change from admin -> public and possibly break some applications? yes,no,dont_care18:30
openstackBegin voting on: Do we want to change from admin -> public and possibly break some applications? Valid vote options are yes, no, dont_care.18:30
*** jeadr has joined #openstack-meeting18:30
openstackVote using '#vote OPTION'. Only your last vote counts.18:30
*** dflorea_ has joined #openstack-meeting18:30
bknudson#vote no18:30
jamielennoxroxanaghe_: sure, and you can override the setting now. we just try very hard to not change defaults on people so that things that did work don't stop when they update18:30
roxanaghe_#vote yes18:30
*** IanGovett has quit IRC18:30
*** yamamoto has quit IRC18:30
*** gyee has quit IRC18:31
dstanek#vote no18:31
jamielennoxgah, torn18:31
ayoung#vote yes18:31
bknudsondeprecate the old behavior and we can change it in 2.018:31
*** lkarm has left #openstack-meeting18:31
dstaneki'd rather see something like bknudson suggested in the review getting in18:31
lbragstaddstanek: you mean the deprecation?18:32
*** padkrish has quit IRC18:32
*** gyee has joined #openstack-meeting18:32
jamielennox#vote no18:32
henrynash#vote no18:32
henrynash[7:31pm]18:32
stevemarblah18:32
henrynashoops18:32
lbragstad#vote no18:32
stevemar#vote no18:32
stevemardeprecate it, then change18:32
jamielennoxit's a good idea, but we've turned down less blatant changes for compatibility reasons18:32
samueldmq#vote no18:32
*** padkrish has joined #openstack-meeting18:32
*** padkrish has quit IRC18:32
dstanekhenrynash: sorry you are wrong....it's 14:3218:32
lbragstador is it 13:33?18:33
dstaneklbragstad: nope18:33
henrynashdstanek: timezones are all secret cunnig plan to keep us all confused18:33
*** dflorea has quit IRC18:33
jamielennoxroxanaghe_: it'll definetly be the default in a new release18:33
breton21:33.18:33
dstanekvoting over in 5...18:33
breton#vote deprecate18:33
openstackbreton: deprecate is not a valid option. Valid options are yes, no, dont_care.18:33
*** emagana has quit IRC18:33
dstanek#endvote18:34
roxanaghe_ok, just wanted to take a decision on it :)18:34
*** dflorea has joined #openstack-meeting18:34
openstackVoted on "Do we want to change from admin -> public and possibly break some applications?" Results are18:34
openstackyes (2): roxanaghe_, ayoung18:34
*** padkrish has joined #openstack-meeting18:34
openstackno (7): lbragstad, bknudson, dstanek, samueldmq, jamielennox, henrynash, stevemar18:34
*** balajiiyer1 has joined #openstack-meeting18:34
dstanekare there any follow ups for this? roxanaghe_ did you want to implement the deprecation idea?18:34
roxanaghe_dstanek, yeah I can do that18:35
bknudsonI'm not sure how you deprecate this... might just be documentation.18:35
roxanaghe_you have some guidance on that process?18:35
*** jichen has joined #openstack-meeting18:35
*** nadya has joined #openstack-meeting18:35
dstanek#action roxanaghe_ to look into alternatives (maybe deprecation) to "Change default endpoint type for Keystone v3 to 'public'"18:35
*** AmirBaleghi1112 has joined #openstack-meeting18:36
*** balajiiyer has quit IRC18:36
dstanekroxanaghe_: sure, in -keystone later you can find some help18:36
dstanek#topic Must tokens always have a user domain ID?18:36
*** openstack changes topic to "Must tokens always have a user domain ID? (Meeting topic: keystone)"18:36
roxanaghe_dstanek, ok cool18:36
dstaneklots of links here and i'm not sure how bknudson wants to drive this discussion18:36
roxanaghe_thanks!18:36
dstanekok bknudson18:36
bknudsonthe question is do tokens always have a user domain ID18:36
*** dflorea_ has quit IRC18:36
*** VW_ has quit IRC18:37
bknudsonthey always have a user ID , that's required by the code that converts token to auth dict18:37
henrynashbknduson: well, v2 ones don’t :-)18:37
*** tim_o has quit IRC18:37
*** VW_ has joined #openstack-meeting18:37
ayoung23 minutes left18:37
bknudsonv2 ones always have the default domain ID as the domain18:37
lbragstadfernet's DomainScopedPayloads do18:37
stevemarfederated users should always have the domain 'federated' - right?18:37
bknudsondomain scope isn't the user domain ID18:38
*** whenry has quit IRC18:38
henrynashbknudson: ++18:38
bknudsonas far as I can tell from the config option federated users have a domain named "federated"18:38
bknudsonbut there's no ID for the federated domain18:38
bknudsonalso, I think those are ephemeral users... are there actual federated users too?18:39
ayoungalways domain id18:39
ayoungdefault was a porting hack18:39
*** sahid has joined #openstack-meeting18:39
ayoungif you change the default domain, you will surprise the hell out of everytone18:39
*** elo1 has quit IRC18:39
ayoungeveryone18:39
*** aranjan_ has joined #openstack-meeting18:39
jamielennoxignoring v2, whta doesn't have a user domain id?18:39
ayoungstevemar, not alwyas18:39
ayoungalways18:39
bknudsonI could add a config option for the federated ephemeral user domain.18:39
ayoungyou should be able to use just a userid, or username + some domain data.18:39
*** nadya has quit IRC18:39
jamielennoxbknudson: isn't that a mapping thing?18:39
ayoungeither domain id or name18:40
ayoungbknudson, no more config values for federation18:40
ayounglets make it so all federation stuff can be changed without restarting the server18:40
*** geoffarnold has joined #openstack-meeting18:40
*** dkranz has joined #openstack-meeting18:41
*** rbak has joined #openstack-meeting18:41
bknudsonjamielennox: I think there's a way to do mapping to either get an ephemeral user or a real one... I assume there's a way to specify the domain ... I'm no expert and haven't looked into it.18:41
*** puranamr has quit IRC18:41
*** VW_ has quit IRC18:42
*** pelix has quit IRC18:42
jamielennoxso are we working around another fernet issue?18:42
*** aranjan has quit IRC18:42
ayoungso...is there any realquestion here?18:43
bknudsonthe issue only shows up in a fernet test18:43
jamielennoxbknudson: but that would seem to me the only place where you could end up without a user_domain_id in a token body18:43
ayoungfernet for federated needs to record all of the information that is needed to reproduce the token18:43
ayoungdon't worry about token size, worry about accuracy.18:44
*** rbradfor has joined #openstack-meeting18:44
*** aranjan_ has quit IRC18:44
jamielennoxso i've thought this before - at this point i think fernet needs to keep a shadow user table18:44
bknudsonok, if it's not a problem to add the user domain ID to the fernet token for federated users that's fine.18:45
ayoungjamielennox, can it use the id mapping table?18:45
bknudsonI'm not sure where the domain ID is going to come from18:45
jamielennoxyou get the win of still not storing tokens, but it might just need to record users that login via federation18:45
ayoung++18:46
*** samueldmq has quit IRC18:46
dstaneklbragstad: dolphm: thoughts? ^18:46
lbragstadI thought marekd_404 had a review up for adding the username to the fernet payload?18:46
dstanekjamielennox: won't that still be a table that grows forever?18:46
ayoungjamielennox, alternative is to make the fernet body larger and record the info there18:46
jamielennoxthe table can still be cleaned after a certain period of time since last login, but it'd be max a couple of million rows with unique ids18:47
* dstanek see that there is only about 13 minutes left and bknudson has one more topic18:47
jamielennoxayoung: the thing i really like about fernet is not growing the table18:47
jamielennoxs/table/token18:47
jamielennoxi'll write something up18:47
ayoungjamielennox, it is either/or...18:47
bknudsonlbragstad: this one? https://review.openstack.org/#/c/202176/ -- I linked to it18:47
jamielennoxfor now i think user_domain_id should be in everything18:47
lbragstadbknudson: yep, looking at that now18:48
bknudsonthat doesn't have the user domain ID either.18:48
*** sahid has quit IRC18:48
jamielennoxhowever as far as i know most of the time when using federated login (web sites etc) you generally create an entry in a user table somewhere that you can link to later18:48
lbragstadbknudson: maybe the domain ID is something that we can build into the federated info?18:48
jamielennoxit would also solve the groups issue18:48
bknudsonlbragstad: sure. I'm not sure if ephemeral users actually have a domain ID at this point either.18:49
*** rbak has quit IRC18:49
*** sudipto has quit IRC18:49
bknudsonthere's a config option for the name but none for the ID18:49
lbragstadright now it consists of groups_ids, idp_id, and protocol_id18:49
lbragstadhttps://github.com/openstack/keystone/blob/master/keystone/token/providers/fernet/core.py#L12318:49
lbragstad#link https://github.com/openstack/keystone/blob/master/keystone/token/providers/fernet/core.py#L12318:49
bknudsonI don't know how it's supposed to work but if users are actually supposed to always have a domain ID then that will require some changes.18:50
*** dflorea has quit IRC18:50
lbragstadyeah, how would we handle that for UUID?18:50
bknudsonwe can move on if we're agreed on that18:50
dstanekit sounds like this is an offline (out of meeting) conversation that needs to happen18:50
bknudsonlbragstad: I'd add a config option with a random uuid.18:50
dstanekmoving on....18:51
dstanek#topic keystoneclient keystoneauth_integration feature branch still broken bknudson18:51
dstanek#link https://review.openstack.org/#/c/213573/ proposed review18:51
*** openstack changes topic to "keystoneclient keystoneauth_integration feature branch still broken bknudson (Meeting topic: keystone)"18:51
dstanekbknudson again!18:51
stevemardstanek: its all broken18:51
henrynashya cn’t keep a good man down18:51
*** puranamr has joined #openstack-meeting18:51
bknudsonjust a notice that the keystoneauth_integration branch is falling way behind due to not being able to merge with master18:51
*** Sukhdev has joined #openstack-meeting18:52
bknudsonthe change to keystoneauth that I think is needed is merged18:52
dstanekstevemar: way to stay positive!18:52
jamielennoxso the purpose of keystoneauth_integration has changed18:52
bknudsonbut now I think we need a release of keystoneauth in order to start using it.18:52
jamielennoxit was initially to make a keystoneclient that depended on keystoneauth, however at this point it's been decided that won't happen during the ksc 1 period18:52
jamielennoxkeystoneauth_integration is therefore the keystoneclient 2 branch that will depend on keystoneauth18:53
*** dflorea has joined #openstack-meeting18:53
jamielennoxbut if we change the branch names we need to change a bunch of rules in zuul that do things like exclude the requirement check based on the branch name18:53
bknudsonwe need to keep the branch in sync with master18:53
jamielennoxthe CRUD interface should remain unchanged, anything related to the session/auth will need to be synced to keystoneauth18:54
*** VW_ has joined #openstack-meeting18:54
jamielennoxtests are the larger problem with cherry-picking between the two18:54
*** yolanda has joined #openstack-meeting18:55
*** dflorea has quit IRC18:55
bknudsonok, that was it... if you're wondering why keystoneauth_integration isn't up-to-date with master it's because changes were made in master that didn't get to keystoneauth18:55
* lbragstad waves the 5 minute flag18:55
dstanekis that it on that topic?18:55
*** ociuhandu has joined #openstack-meeting18:56
*** pnavarro has quit IRC18:56
*** geoffarnold has quit IRC18:56
jamielennoxbknudson: i go back and cherry-pick occasionaly but i don't think there have been many changes to session/auth in ksc recently18:56
dstaneki'll take that as a *yes*18:56
*** VW_ has quit IRC18:56
jamielennoxdo you have a list?18:56
dstanek...or not...18:56
*** sdake_ has joined #openstack-meeting18:56
*** wshao has joined #openstack-meeting18:56
*** VW_ has joined #openstack-meeting18:56
bknudsonjamielennox: the fix that I needed I made with https://review.openstack.org/#/c/210010/18:57
*** tiswanso has quit IRC18:57
bknudson"Commit 6950527 in python-keystoneclient added role_ids and role_names properties to fixtures.v3.Token"18:57
dstanekshould we have some cleanup activity to get the branch in sync?18:58
bknudsonthat commit was made to master but wasn't made to keystoneauth18:58
bknudsonso when I go to merge master to the feature branch, the tests fail since the master tests are using the properties.18:58
bknudsonbut there hasn't been a release since then so the merge is still failing tests18:59
*** sgordon has quit IRC18:59
*** Shrews has joined #openstack-meeting18:59
*** etoews has joined #openstack-meeting18:59
*** sgordon has joined #openstack-meeting18:59
* Shrews lurks18:59
*** sdake has quit IRC18:59
*** adreznec has joined #openstack-meeting19:00
dstanek#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Aug 18 19:00:16 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-08-18-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-08-18-18.02.txt19:00
*** banix has quit IRC19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-08-18-18.02.log.html19:00
dstanekthat's time!19:00
*** tiswanso has joined #openstack-meeting19:00
fungiinfra team assemble!19:00
clarkbohai19:00
Clinto/19:00
*** gyee has quit IRC19:00
mrmartino/19:00
jasondotstaro/19:00
yolandao/19:00
SotKo/19:01
Zarao/19:01
*** jang has quit IRC19:01
*** ianw has joined #openstack-meeting19:01
rbradforo/19:01
*** VW_ has quit IRC19:01
ruagairO/19:01
fungi#startmeeting infra19:01
openstackMeeting started Tue Aug 18 19:01:27 2015 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** penick has quit IRC19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
*** tsymanczyk has left #openstack-meeting19:01
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
SpamapSo/19:01
ociuhanduo/19:01
*** Piet has joined #openstack-meeting19:01
fungi#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
tchaypo\o19:02
ianwo/19:02
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2015-August/003069.html19:02
*** Piet has quit IRC19:02
*** jang has joined #openstack-meeting19:02
*** fawadkhaliq has joined #openstack-meeting19:02
fungijust a reminder that we're planning to mass rename repos from the stackforge namespace into a common openstack namespace, on an opt-in basis19:02
mmedvedeo/19:03
pleia2o/19:03
fungiand then mark any that haven't opted in as read-only/archived after a time19:03
zaroo/19:03
*** vivek-ebay has joined #openstack-meeting19:03
fungifollow up to the thread with further discussion on scheduling19:03
jheskethMorning19:03
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2015-August/003075.html19:03
*** dflorea has joined #openstack-meeting19:03
*** Haneef__ has quit IRC19:03
fungidue to recent growth of core reviewers in neutron, they've requested that we clear job changes through mestery, armax or dougwig unless it's really urgent19:04
*** banix has joined #openstack-meeting19:04
fungiso just bear in mind, when reviewing changes to job configuration that could potentially impact what's tested for neutron that we're looking for a +1 from at least one of them if possible19:04
fungi#topic Actions from last meeting19:05
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:05
fungi#link http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-11-19.02.html19:05
fungipabelanger,jasondotstar look into restore-from-backup testing19:05
fungii know that's ongoing, we've been discussing it in channel19:06
jasondotstarwe've captured our thoughts here: https://etherpad.openstack.org/p/infra-backup-brainstorm19:06
jasondotstarthe next step is to run through our test strategy19:06
fungi#link https://etherpad.openstack.org/p/infra-backup-brainstorm19:06
*** annegentle has joined #openstack-meeting19:06
fungijasondotstar: pabelanger: thanks! we can work from there i think19:06
jasondotstarwe'd like to also ask folks to think of any other backup/restore scenarios worth testing (manually)19:06
*** bill_az has quit IRC19:06
jasondotstarput them there on the etherpad.19:07
*** austin81 has joined #openstack-meeting19:07
*** wshao has quit IRC19:07
*** vivek-eb_ has joined #openstack-meeting19:07
*** vivek-ebay has quit IRC19:07
jasondotstaronce we identify the manual steps and validate that they work19:07
fungisounds good19:07
*** e0ne has joined #openstack-meeting19:08
SpamapSJust chiming in.. there is one set of data in infra-cloud that is hard to reproduce, and that is the Ironic inventory. We have a plan to store most of it in git, with the secret bits in hiera.19:08
jasondotstarwe can think about automating.19:08
*** amotoki has joined #openstack-meeting19:08
jasondotstarSpamapS: ack.19:08
SpamapSSo that just means any backup systems need to make sure git and hiera are backed up.19:08
*** ayoung has quit IRC19:08
fungiSpamapS: cool, it's definitely the hard-to-reproduce things we actually care about backing up19:08
SpamapSAlso hiera backups, I assume, need to be encrypted.19:08
fungiyeah19:08
clarkbwhich is an exercise to be completed :/19:08
jasondotstarthe hiera data is primarily on the puppetmasters...or somewhere else?19:09
clarkbyes would be on the puppetmaster(s)19:09
fungijasondotstar: it's a static file on the puppetmaster19:09
jasondotstarclarkb: ack.19:09
*** nadya has joined #openstack-meeting19:09
*** ndipanov has quit IRC19:09
jasondotstarso we should think of an encryption method for sensitive data such as this...19:10
clarkbthe tricky thing is the chicke and egg with backing up the encryption key/sharedsecret19:10
* jasondotstar agrees19:10
clarkbI think thats where I got distracted last time I looked into this19:10
jasondotstarpabelanger and i will capture this on the etherpad and see what we can come up with...19:11
fungiyeah, it's turtles all the way down. we were considering encrypting it to the keys of the infra root admins or with a passphrase known only to infra root and leave it at that19:11
*** vivek-eb_ has quit IRC19:11
*** ianw has quit IRC19:11
SpamapSIMO, encrypt the backups w/ GPG to all of infra-root's keys. Anyone in infra-root then can restore the backup on their machine.19:11
fungibut anyway, that's veering a bit off topic for validating our current backup mechanism19:12
nibalizerohai19:12
SpamapSagree, just make sure it gets backed up19:12
jasondotstar+119:12
fungiyeah19:12
fungi#topic Specs approval19:13
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:13
fungi#link https://review.openstack.org/#/q/status:open+project:openstack-infra/infra-specs,n,z19:13
*** amotoki has quit IRC19:13
fungiwe're not approving any specs in meeting, just a reminder that there are some awaiting reviews19:13
*** fawadk has joined #openstack-meeting19:13
*** ianw has joined #openstack-meeting19:13
fungialso the new storyboard dev team has explicitly requested review/approval of some outstanding storyboard specs19:13
pleia2I didn't add it to the agenda, but this translations site spec is ready for review: https://review.openstack.org/#/c/184559/19:14
pleia2I've been working with the i18n folks to refine it, and I think it's in a good place now19:14
fungisince openstack project infra don't have a huge stake in it other than avoiding breaking it until we switch to something else, would be nice for us to give the storyboard team relatively wide berth on their specs i guess19:15
SotKThe StoryBoard spec in question is https://review.openstack.org/#/c/202989/19:15
*** esker has joined #openstack-meeting19:15
fungi#link https://review.openstack.org/20298919:15
fungithanks SotK!19:15
fungiand apologies for us being somewhat absentee landlords on that19:15
clarkbwell didn't we say see how it goes?19:15
*** fawadkhaliq has quit IRC19:16
*** salv-orl_ has joined #openstack-meeting19:16
SotKwe did19:16
fungiyep. they seem to be doing stuff19:16
clarkbI am guessing this is and indication that infra isn't really interested in that?19:16
*** sdake_ is now known as sdake19:16
*** shashank_hegde has quit IRC19:16
fungipotentially, yes19:16
*** breton has left #openstack-meeting19:16
fungianyway, specs. we have some. i need to review them, and would be thrilled if others do to19:17
fungi#topic Schedule Project Renames19:17
*** openstack changes topic to "Schedule Project Renames (Meeting topic: infra)"19:17
*** mmmpork has joined #openstack-meeting19:18
fungiit was suggested in the aforementioned planning thread that we should probably also do some renames in september for projects that have already requested them19:18
fungiwe don't need to decide it today, but just making sure we keep it in mind and see if we can pick a good window when september draws a little closer19:18
fungi#topic Priority Efforts19:19
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:19
clarkbany initial suggestions?19:19
clarkboh too late19:19
fungi#undo19:20
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0xa1ee7d0>19:20
fungiit's not too late!19:20
Clintwell played19:20
*** rbowen has quit IRC19:20
fungii didn't have any initial suggestions though, but my calendar is wide open for september19:20
clarkbthere is the long weekend for MURICA we should avoid but otherwise maybe avoid burning man? I think that is next to the long weekend19:20
*** GB21 has quit IRC19:21
* fungi has done a great job at avoiding burning man so far19:21
pleia2after labor day I'm around all month19:21
clarkbthats basically the first week of september is no go19:21
clarkbmaybe do second weekend?19:21
*** annegentle has quit IRC19:21
*** achanda has quit IRC19:22
fungisecond weekend... like friday the 11th'/19:22
fungi?19:22
clarkbya19:22
pleia211th and 12th are good for me19:22
fungiwfm. i have some guests in town the following weekend19:22
fungi#info tentative window to clear already requested project renames on september 11 or 1219:23
zaroare we planning or have plans to move any infra projects around?  like from sourceforge to openstack or openstack-infra?19:23
*** sbalukoff has quit IRC19:23
fungis/ource/tack/19:23
*** AmirBaleghi1112 has quit IRC19:23
funginot that i'm aware, no19:24
*** banix has quit IRC19:24
*** PrashantS has quit IRC19:25
fungiokay, nothing else on this i guess, so moving on19:25
fungi(for real this time!)19:25
fungi#topic Priority Efforts19:25
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:25
*** alop has joined #openstack-meeting19:25
*** PrashantS has joined #openstack-meeting19:25
fungiif there aren't any urgent updates for any of these, i'm going to move ahead to the backlog19:26
*** annegentle has joined #openstack-meeting19:26
clarkbjhesketh has a first pass at the swift index gen stuff19:26
fungianyone have a priority effort that's blocked/on fire?19:26
clarkbso swift logs continues to plod along19:26
*** sbalukoff has joined #openstack-meeting19:26
*** ivar-laz_ has joined #openstack-meeting19:26
zarogerrit upgrade might be blocked forever.19:26
fungizaro: oh? details appreciated... link?19:26
yolandai'd like to request more reviews for several items on downstream-puppet19:26
zaronobody is working to fix the jgit issue #link https://groups.google.com/forum/#!msg/repo-discuss/CYYoHfDxCfA/BxkgOOx6CgAJ19:26
fungizaro: ugh19:27
clarkbI think upstream gerrit may have given up on functioning properly19:27
fungiETOOHARD19:27
jheskethYeah swift logs are slowly going. Not as fast as I'd like sorry19:27
*** jamielennox has left #openstack-meeting19:27
fungino worries19:28
*** ivar-lazzaro has quit IRC19:28
fungiokay, moving along to the backlog19:28
fungi#topic Restore from backup test (jeblair)19:28
*** openstack changes topic to "Restore from backup test (jeblair) (Meeting topic: infra)"19:28
fungithis was mostly covered in the action items19:28
fungiwe should keep working through it, but i don't know that it needs any additional discussion here for the time being19:29
fungi#topic Fedora 22 snapshots and / or DIBs feedback (pabelanger)19:29
*** openstack changes topic to "Fedora 22 snapshots and / or DIBs feedback (pabelanger) (Meeting topic: infra)"19:29
fungilooks like pabelanger's not here19:29
nibalizerI believe he can be summoned19:29
*** PrashantS has quit IRC19:29
nibalizermaybe not19:29
ianwwe should be close to having dib images going19:30
*** geoffarnold has joined #openstack-meeting19:30
ianwhpcloud don't have f22 images, rax does19:30
*** pabelanger has joined #openstack-meeting19:30
fungiyeah, i've been semi-reviewing the proposed changes19:30
pabelangeropps19:30
fungii'll link them here19:30
ianwif someone from hpcloud wants to fix that, great19:30
pabelangersorry, lost track of time19:30
fungi#link https://review.openstack.org/21170319:30
*** banix has joined #openstack-meeting19:30
fungi#link https://review.openstack.org/21129419:30
fungi#link https://review.openstack.org/18661919:30
ianwdevstack is broken on f22 at the moment due to a pip issues, hope to have something on that today .au time19:31
*** singleth_ has joined #openstack-meeting19:31
ianwa real fix + workaround in the mean-time probably19:31
fungiokay, great19:31
fungianything else specific you needed to cover for this in the meeting?19:31
*** otter768 has joined #openstack-meeting19:31
clarkbwill we drop f21?19:31
ianwsort of more priority effort, but request for review of the yum/dnf package caching for dib ... getting links19:32
ianw#link https://review.openstack.org/20832119:32
fungiphrased differently, should we expect the current jobs that run on f21 to work on f22 obce we have it booting?19:32
fungier, once19:33
ianwmy suggestion is to unify apt/yum paths to minimise our need to pass different env variables19:33
fungiwhatcha mean "unify apt/yum paths"?19:33
ianwsorry, i mean in that review use common environment variables to indicate "keep the package cache"19:34
fungioh, right-o19:34
*** singlethink has quit IRC19:34
*** harshs has quit IRC19:34
clarkb+119:34
ianwas to the jobs, yes for devstack+tempest19:34
fungiwithin dib's baked-in elements you mean19:34
*** vivek-ebay has joined #openstack-meeting19:35
ianwi *think* there might be some docker-ish type stuff i know little about.  i imagine it can transition19:35
fungibecause it definitely has some widely varied caching behaviors/implementation between the dpkg element and the yum element19:35
ianwyeah, that's what i've tried to unify with those changes19:35
fungiokay, cool19:36
fungianything else on this?19:36
ianwanyway, i think that it's all pretty contained within the reviews, so that's it19:36
*** otter768 has quit IRC19:36
fungif21 deprecation?19:36
fungidon't see that answered19:36
*** belmoreira has joined #openstack-meeting19:36
clarkbianw naswered said yes for devstack + tempet19:37
clarkbwhich is most of where we f2119:37
fungiahh, right-o19:37
ianwthe devstack job is super-unstable.  i haven't bothered fixing it because f22 is so close19:37
ianwso it's half-dead already :)19:37
fungithe puppet crowd i guess are the other primary consumers of those images?19:37
clarkband kolla/magnum19:37
fungitripleo have their own images, so can transition at their own pace i suppose19:37
*** angdraug has joined #openstack-meeting19:38
ianwyep; pabelanger & me will work with people to transition19:38
*** geoffarnold has quit IRC19:38
fungialright, great19:38
ianwif anyone ever asked me, i've always told them the cost of testing on fedora is they're going to be on the upgrade cycle19:38
*** geoffarnold has joined #openstack-meeting19:38
*** matrohon has joined #openstack-meeting19:39
fungiyeah, that's why we've generally not had important jobs run on non-long-term releases19:39
ianwyep, so it's fair to expect people to put some effort into moving19:39
fungisince we can't continue to maintain them in that state for our stable release branches19:39
fungi#topic Normally there are no infra-roots in Europe, some of us want to volunteer for it (yolanda)19:39
*** openstack changes topic to "Normally there are no infra-roots in Europe, some of us want to volunteer for it (yolanda) (Meeting topic: infra)"19:39
yolandahi so the topic raised that week on some gerrit outage19:40
yolandawe know we have jhesketh on Australia, and Sergey on Europe, but reality is that sometimes is difficult to have roots at certain hours19:40
*** aranjan has joined #openstack-meeting19:40
mrmartingood idea, if you don't plan to sleep in the next 6-12 months19:40
fungiyolanda: thanks for being interested in helping more! general workflow for this is to sync up with the ptl and let them drive the conversation, so probably best to bend jeblair's ear when he's no longer in the midst of the ops mid-cycle19:40
yolandaAJaeger raised the problem that there were no volunteers, so from Gozer we'd like to volunteer19:41
yolandayes, we'll contact jeblair for it19:41
fungiyolanda: i think that's awesome19:41
mrmartin+1 for EU infra root next to Sergey19:41
*** rbak has joined #openstack-meeting19:41
mrmartinwe are really loosing entire work days when something fails19:41
*** fawadk has quit IRC19:41
yolandawe are 3 members on Europe that are able to help, and have the expertise, so we'll be contacting jeblair for it19:41
fungiyep, anyway, lets let this conversation take its course through the proper channels when jeblair can be around19:42
yolandasure19:42
*** rromans_afk is now known as rromans19:42
*** emagana has joined #openstack-meeting19:42
fungii just wanted to go ahead and bring it forward since you had it on the agenda. don't want you to think i'm skipping you!19:42
fungi#topic puppet-pip vs puppet-python (rcarrillocruz)19:43
*** openstack changes topic to "puppet-pip vs puppet-python (rcarrillocruz) (Meeting topic: infra)"19:43
fungithis got some discussion on the mailing list, though i think it might have reached a lull19:43
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2015-August/003015.html19:43
*** mestery has joined #openstack-meeting19:44
fungilooks like it was covered in last week's meeting, so we can just kick that thread and see if we can bring it to a resolution i guess19:44
*** e0ne has quit IRC19:44
fungi#topic Nodepool REST API spec (rcarrillocruz)19:45
*** openstack changes topic to "Nodepool REST API spec (rcarrillocruz) (Meeting topic: infra)"19:45
fungithis also looks like it's left over from last week19:45
nibalizeryep19:45
fungiwas there anything else that needed covering on this one?19:45
pabelangerI haven't had a chance to review the spec and leave comments19:45
fungiyep, please review open specs ;)19:45
* fungi is one of the worst offenders19:45
fungi#topic Open discussion19:46
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:46
fungii give you 13.5 minutes19:46
yolandai wanted to raise the zuul services problem, we had some discussion on the mailing list19:46
yolandawith several opinions19:46
yolandai'd like that we get on some agreement19:47
fungiwhich list? infra or dev?19:47
*** emagana has quit IRC19:47
fungior was it before august?19:47
yolandainfra, we had the discussion last week19:47
funginot immediately finding the thread to gain some context19:48
yolandaabout if puppet modules should spin up services or not19:48
fungioh, that19:48
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2015-August/003038.html19:48
yolandaah, i didn't have the link handy19:48
*** MaxPC has quit IRC19:48
sdakefungi clarkb i am good from a kolla perspective with f21 deprecation in 1-2 weeks19:48
*** emagana has joined #openstack-meeting19:49
sdakewe want f22 though :)19:49
fungisdake: awesome, well we need the f22 images working anyway, yeah ;)19:49
*** carl_baldwin has joined #openstack-meeting19:49
*** MaxPC has joined #openstack-meeting19:49
fungiyolanda: so i think we mostly settled on it being fine to parameterize the service ensure for running/stopped/undef19:49
sdakein 1-2 weeks I will be removing our fedora-21 gating job entirely19:50
yolandafungi, that works for me19:50
sdakeas soon as my gating work finishes and merges for the new kolla build tool19:50
fungii think someone (crinkle? nibalizer? clarkb?) said ensure=>undef will have the desired outcome for our infra19:50
sdakefungi but for f22, that gating job is furthe rout and not  an immediate priority19:50
clarkbensure => undef is really annoying19:51
crinkleyes19:51
clarkbit behaves differently in puppet3 and puppet419:51
nibalizerya my last message on that thread is what I think we should do19:51
clarkbbut if thats the hack I guess ok?19:51
*** belmoreira has quit IRC19:51
crinkleclarkb: I don't think it will behave differently?19:51
*** ayoung has joined #openstack-meeting19:51
nibalizerclarkb: it does?19:51
clarkbcrinkle: using undef as a param makes it use the dfeault19:51
clarkbin puppet3 but in 4 its actually a nil value aiui19:52
*** lkarm has joined #openstack-meeting19:52
clarkbso if there is a default for the thing you get the default which is probably not what you want if explicitly undefing19:52
crinklethere's no default for ensure in the service type, is why not specifying it has worked so far19:52
clarkboh I thought it defaulted to running19:52
crinkleif it defaulted to running then we wouldn't be arguing about adding ensure => running19:53
clarkbbut you must be right since its just dropped19:53
clarkbya19:53
fungiand yeah, i feel relatively strongly that the way we run our services in the openstack project infrastructure should be the default behavior for the modules we publish, because anything else is hypocrisy, but it's perfectly fine to make the behavior configurable so that downstream consumers can choose to override that default to whatever behavior they prefer19:53
crinklefungi: ++19:53
pabelangerpuppet-lint voting jobs for system-config? What was decided?19:54
*** britthouser has quit IRC19:54
pabelangerre-enable or not?19:54
*** britthouser has joined #openstack-meeting19:54
fungibut if the people responsible for maintaining zuul.openstack.org feel that ensure-running for the zuul services is a liability, then it feels wrong for us to make that a non-default behavior for the openstackinfra/zuul module on the forge19:54
clarkbfungi: agreed we should keep the current behavior as default for all the reaons argued for on the thread19:55
pabelangerI am infavor of expoising something to allow people to control it, does not matter the name or defaults.19:55
*** ivar-laz_ has quit IRC19:55
*** ivar-lazzaro has joined #openstack-meeting19:56
*** roxanaghe_ has quit IRC19:56
yolandai agree with pabelanger19:56
*** lkarm has left #openstack-meeting19:56
yolandaparameterize , be flexible and not opinionated on it, and i'm perfectly fine on having the default non running for infra19:56
fungipabelanger: i think we have a consensus to not -1 over style concerns, but the current core reviewers for the system-config repo didn't express an interest in having that repo linted since it's not going to be published to the forge19:56
clarkbwell if you put it that way I think we _should_ be opinionated :P19:57
*** annegentle has quit IRC19:57
clarkbwe know a lot about zuul19:57
clarkbwe know a lot about running zuul19:57
*** balajiiyer1 has quit IRC19:57
clarkbwe should share that knoweldge19:57
*** ivasev has quit IRC19:57
crinklewe have https://review.openstack.org/#/c/175226/1 to add linting, I think we should get that rebased and merged19:57
*** sigmavirus24 is now known as sigmavirus24_awa19:57
*** mrunge has quit IRC19:58
*** sigmavirus24_awa is now known as sigmavirus2419:58
fungioh, i hadn't notived that one. so we need linting to give us forewarning of things we're currently doing in system-config that might break under puppet 4?19:58
fungier, noticed19:58
fungi#link https://review.openstack.org/17522619:59
fungianyway, we're running out of time19:59
fungianything else in these last few seconds?19:59
Clintno19:59
fungithanks everybody!19:59
fungi#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:59
openstackMeeting ended Tue Aug 18 19:59:55 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
*** yolanda has left #openstack-meeting19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-18-19.01.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-18-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-18-19.01.log.html20:00
*** BadCub has joined #openstack-meeting20:00
Clintwith 5 seconds to spare20:00
fungiall yours, ttx!20:00
ttx... o/ Anyone here for the TC meeting ?20:00
*** annegentle has joined #openstack-meeting20:00
*** jroyal has quit IRC20:00
*** rbradfor has left #openstack-meeting20:00
*** andreykurilin has quit IRC20:00
ttxrussellb, jgriffith, annegentle, lifeless, mordred, flaper87, dtroyer, markmcclain, jeblair, jaypipes, sdague, dhellmann: around ?20:00
russellbo/20:00
flaper87o/20:00
* mestery lurks20:00
*** vivekd has quit IRC20:01
jgriffith\o20:01
* edleafe lurks too20:01
*** andreykurilin has joined #openstack-meeting20:01
lifelessttx: very20:01
*** jroyal has joined #openstack-meeting20:01
dhellmanno/20:01
lifelessttx: but I'm back on the diet :)20:01
dhellmannttx: jeblair will be online shortly20:01
ttxlifeless: good, I guess20:01
*** neelashah has quit IRC20:01
ttxwaiting for a 7th to start20:02
*** neelashah has joined #openstack-meeting20:02
*** sridhar_ram has quit IRC20:02
markmcclaino/20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Aug 18 20:02:44 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
ttxOur agenda for today:20:02
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:02
*** pabelanger has left #openstack-meeting20:03
ttx#topic Using topics to classify governance changes20:03
*** openstack changes topic to "Using topics to classify governance changes (Meeting topic: tc)"20:03
ttx3 weeks ago sdague asked that we use Gerrit topics to mark governance changes that do not actually require formal votes20:03
ttxso that we can filter them20:03
*** sridhar_ram has joined #openstack-meeting20:03
ttxI sent an email to the -tc list proposing to do the reverse (mark those who actually require formal votes), since there are lots of corner cases:20:03
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2015-July/001005.html20:03
ttxNo answer to that proposal... yet20:03
russellbseemed reasonable to me20:03
ttxnot sure that means "go ahead"20:03
flaper87I think we silently agreed20:03
ttxrussellb: ok20:03
flaper87yeah20:03
russellbi didn't have anything to add20:04
*** gordc has joined #openstack-meeting20:04
russellbso yeah, my silence was +1 :)20:04
flaper87extreme lazy consensus20:04
*** dflorea has quit IRC20:04
ttx#action ttx to mark things that we actually need to vote on, for easier filtering20:04
dhellmannyeah, mark the subset -- the point was to just be able to filter20:04
ttxjust hoping that doesn't mean nobody will pay any attention to other changes20:04
russellbi'll still have all changes hitting my inbox personally20:04
jeblairo/20:04
flaper87it'll help me prioritize20:04
annegentlea search filter sounds great20:05
* dhellmann subscribes to all20:05
ttx#topic Add and apply tag team:size-large20:05
dhellmannI could add it to the TC dashboard query, too20:05
*** openstack changes topic to "Add and apply tag team:size-large (Meeting topic: tc)"20:05
* flaper87 uses gertty20:05
flaper87YEs, I'm one of those20:05
russellbso this tag came up in the next tags WG20:05
russellbor rather, this family of tags20:05
* jeblair high-fives flaper87 20:05
ttx#link https://review.openstack.org/20802920:05
russellbthe idea of tagging info around team sizes20:05
ttx#link https://review.openstack.org/20803020:05
ttxIn the discussion emerged the need for a team:very-small tag, which is what consumers of that data are actually looking for20:05
ttx"Is a project maintained by enough people to be there tomorrow" (same as diverse-affiliation)20:05
flaper87jeblair: :D20:05
russellbright, happy to propose "very-small" as a red flag tag20:06
ttxThat said, that doesn't mean a team:very-large tag isn't useful, to distinguish projects with a giant group behind them...20:06
ttxrussellb: I guess that still answers a question people might have ?20:06
russellbcurious if anyone else finds "very-large" useful20:06
russellbit seems somewhat interesting to me20:06
*** amrith is now known as _amrith_20:06
flaper87mmh, have we considered using number-ranges ?20:06
russellbbut is it just interesting, or is it useful?20:06
* russellb shrugs20:06
flaper87throwing it out there20:06
annegentleI think that activity-level:high is more accurate for this?20:06
ttxYeah, I can see how *I* would use iut, not sure about others though20:06
flaper87rather than small/very-small/big20:06
jgriffithrussellb: so it is intended to be different than "diverse"?20:06
dhellmannannegentle: ++20:06
russellbjgriffith: yes20:06
ttxflaper87: "medium" doesn't answer any question20:07
annegentlenot trying to paint a bike shed, but it seems like this isn't about team size but activity / scope20:07
russellbjgriffith: diversity vs # of people doing the work20:07
flaper87At least we know how many we're talking about (not sure if that makes sense)20:07
jgriffithrussellb: thanks20:07
russellbis a diverse group of 5?  or is it a diverse group of 50?20:07
*** rbak has quit IRC20:07
markmcclaindoesn20:07
jgriffithrussellb: yeah, I see the difference now.  Thank you20:07
edleafeit's about warning for potential problems, no?20:07
ttxannegentle: it's arguably az comabo. One very active person is certainly more fragile than 3 moderately-active persons20:07
ttxaz comabo ?20:08
flaper87ttx: agreed, which is why I'm wondering if we've considered rage numbers20:08
ttxwhat am I typing20:08
ttx"a combo".20:08
russellbrage numbers?  sounds fun20:08
*** mestery has quit IRC20:08
lifelessflaper87: do you mean drive-by fixes?20:08
jeblairalso, the necessary team size may vary by project moreso than diversity20:08
flaper87<=10, <= 20, >2020:08
lifelessalso maturity20:08
russellbjeblair: fair20:08
lifelessa mature specialised thing needs many less changes20:08
russellbis there some # that's "very-small" / "too-small" regardless of project?20:09
ttxflaper87: I don't think <=20 answers any question anyone has20:09
russellbif not, then maybe the whole tag category should be dropped20:09
annegentlealso the 6 commits and 30 reviews, is that a known ratio from a given team?20:09
flaper87ttx: what does very-small say? What do we base that on?20:09
ttxI feel like people want to know if "enough" people support their project. They may want to know if the project is giganormous, but I'm not sure of that20:09
russellbannegentle: completely arbitrary starting point20:09
ttxflaper87: bus factor20:09
annegentlerussellb: ok20:09
ttxflaper87: A project with only one active person is extremely fragile.20:10
russellbi picked those numbers out of the air, and they seemed to capture the biggest handful of projects20:10
markmcclainyeah.. I think small is more of a concern20:10
ttxthere are some of those in openstack today.20:10
annegentleI ran these numbers for docs, and only one specialty areas will be above that ratio I think... will have to double check20:10
ttxI think people should know about them.20:10
flaper87ttx: sure, doesn't <= 10 same the same thing?20:10
ttx<= 10 what?20:10
flaper87my point is, we gotta get those "quantifications" from somewhere20:10
*** rbak has joined #openstack-meeting20:10
*** mestery has joined #openstack-meeting20:10
fungialso curious how to aggregate that across all the repos for all the deliverables in a project, assuming it's based on core review/approver group membership or commit activity or...20:10
flaper87ttx: whatever very-small is made of, I guess20:11
russellbfungi: the union of all activity in all repos for a team20:11
russellbis how it works right now20:11
jgriffithIf they're not large they're small(ish) :)20:11
fungirussellb: thanks20:11
ttxflaper87: russellb uses "'active contributors" as a metric20:11
ttxI thiknk under 3 the project is at risk at that should be communicated.20:11
russellbso if nothing else, seems to be agreement that "very small" is the most valuable thing20:12
*** britthou_ has joined #openstack-meeting20:12
russellbso as a next step i'll propose that20:12
ttxyeah, maybe we shjould start with this one20:12
russellband then once we work through that, we can revisit "large" (maybe)20:12
ttxI blame philosophers and their wine for all the typos I make today20:12
* flaper87 goes to os-zaqar and starts counting ppl20:12
flaper87</jk>20:12
annegentlemy gut says highly active could be valuable, to set expectations for review time perhaps, but won't tell much to people who use or operate a service20:12
*** banix has quit IRC20:12
russellbflaper87: script is already merged iirc20:12
dhellmannrussellb: very large might be an indication that the project may move pretty slowly, too, so it could be useful20:12
annegentledhellmann: right, my thinking also20:13
flaper87russellb: damn :P20:13
fungireview tie is actually something we _can_ measure, if that's a useful metric to build a tag around20:13
fungier, review time20:13
russellbfungi: that sounds interesting20:13
ttxdhellmann: In all cases we need to define the question before we define the tag that would help answer it20:13
russellbalready measuring that with bitgeria20:13
dhellmannttx: sure, and measuring review time directly is likely better20:13
russellbnot sure how easy it would be to get that data on demand20:13
ttxIn the current case, the question is "is the project supported by enough people that it will survive individual accidents20:13
ttxlike people burning out20:14
annegentle#link http://activity.openstack.org/dash/browser/20:14
fungiand also reviewstats data, and similar data to that in stackalytics20:14
*** aranjan_ has joined #openstack-meeting20:14
flaper87ok, I think I see the point of using very-small rather than numbers20:14
flaper87sorry, took me a bit20:14
flaper87:D20:14
ttxI feel like if you have less than 5 the project would seriously suffer if they lost one person.20:14
* flaper87 is slow today, ask everyone20:14
markmcclainttx: +120:14
*** shashank_hegde has joined #openstack-meeting20:14
*** aranjan has quit IRC20:15
ttxsuffer to the point where there could be cascading failure.20:15
flaper87ttx: I can say, from my own experience, that's true20:15
*** britthouser has quit IRC20:15
flaper87:)20:15
ttxthat is the risk I want the tag to communicate20:15
dougwig <=2 is an obvious low limit, because then your cores can't submit code. :)20:15
russellbdougwig: ha20:15
ttxdoesn't mean people won't use the project. Just helps them make their own idea20:15
flaper87dougwig: been there too :P20:15
fungifor very small team sizes, it's convention to just self-approve or single-core approve changes20:15
dougwigflaper87: still there (fwaas and vpnaas).20:15
flaper87dougwig: :(20:15
fungiso they're not _exactly_ blocked on submitting changes to merge20:15
markmcclainthere is a component of diversity within low numbers... a team of10 people and 8 work for same company is at serious risk of collapse too if company changes direction.. should probably be considered small20:16
lifelesswhen we say project here20:16
russellbdougwig: those imply it might be valuable to call this out on a per-repo basis20:16
lifelessdo we mean 'code tree' or 'group of people' ?20:16
ttxanyway, I think Russell has a way forward20:16
russellbthis tag right now is focused on teams, so it'd be Neutron overall20:16
*** penick has joined #openstack-meeting20:16
ttxlifeless: project team20:16
lifelessthings like openstack/requirements have ill-defined teams IME20:16
russellbanyway, yes, i have a way forward20:16
ttxalthough it doesn't have to be a team tag I guess20:17
lifelessttx: could it be a tag team?20:17
ttxor a tag team tag ?20:17
ttxteam tag² ?20:17
russellbtagception20:17
jgriffith+1 for squared20:17
* flaper87 rofl20:17
russellbi think we should move on20:17
annegentlewow squared20:18
* annegentle is impressed20:18
dougwigrussellb: agree on calling out per team somehow (where team may be a larger project subteam).  sorry for delay, at ops meetup.20:18
fungikeeping in mind that the tc abandoned the concept of per-repo tags, so i don't see how doing it on a per-repo basis would be feasible20:18
russellbdougwig: all good, glad you're there!  would love to hear your feedback after20:18
*** Shrews has left #openstack-meeting20:18
*** britthouser has joined #openstack-meeting20:18
russellbfungi: yar20:18
ttxrussellb: it's true that it could be an per-repo tag. After all some of the neutron circus things might be supported by only one person20:18
*** boris-42 has joined #openstack-meeting20:19
russellbttx: but someone could make the same argument about components of a project in a single repo20:19
*** britthou_ has quit IRC20:19
russellbso not sure we need to worry too muhc20:19
fungiseems like at a minimum you'd need to aggregate across all repos for a given deliverable20:19
ttxyou'll come up with something :)20:19
russellbwe're not going to capture "maintainers of a feature in a project" at this level20:19
russellbyup20:19
ttxLet's move on20:19
ttx#topic Add new openstack kiloeyes repository20:19
*** openstack changes topic to "Add new openstack kiloeyes repository (Meeting topic: tc)"20:19
dhellmannfungi: ++20:19
ttx#link https://review.openstack.org/21017520:20
ttxSummary of the feedback is that this is pretty new, so it's way too early to be considered "one of us"20:20
ttxIt also shows that competition between openstack projects is fine, but only as long as the alternative provides a different value proposition *and* collaboration is not an option20:20
ttxhere it seems avenues for collaboration have not been explored yet, and the value proposition is unclear20:20
*** penick has quit IRC20:20
*** VW_ has joined #openstack-meeting20:20
dhellmannfwiw, I'm not at all concerned that the API is the same. Compatibility is a feature.20:20
ttxso I think asking for it to live a bit in stackforge is not too much too ask20:21
ttxdhellmann: agreed20:21
lifelessstackforge is going away20:21
clarkbttx: except ya ^20:21
ttxlifeless: no it's not.20:21
jeblairno its not20:21
dhellmannthe name is, but not the concept20:21
lifelessarg20:21
*** mmmpork has left #openstack-meeting20:21
lifelesscan we please pick a new name for the concept then ?20:21
ttxit's just living in the same git prefix for convenience20:21
dhellmannthis project can live as an unofficial project20:21
*** puranamr has quit IRC20:21
ttx"unofficial"20:22
ttxI stand corrected20:22
*** achanda has joined #openstack-meeting20:22
*** achanda has quit IRC20:22
lifelesssure, that won't make my brains leak out my ears :)20:22
ttxanyone disagreeing with that outcome at this stage ?20:22
*** achanda has joined #openstack-meeting20:23
jaypipesnope20:23
edleafetentforge?20:23
ttx(asking them to live a bit before applying for official projetc team ?)20:23
jaypipesedleafe: lol20:23
flaper87not me, I hope Tong li will also come back with some answers to my qeustions20:23
annegentleproject can live in any github org it wants to, and observe the OpenStack way, do we need to give them a timeline?20:23
flaper87s/not me/no objections from me/20:23
jaypipesflaper87: agreed. I'm not going to gang up on the review, but I had almost identical questions as mordred20:23
annegentlejaypipes: yeah, me too20:23
ttxI like to see a project exist for at least 3 months (and/or doing an initial release) before evaluating if they behave like an openstack project20:23
dhellmannannegentle: I think we want to see what happens and let them come back20:24
annegentlettx: initial release might be good20:24
ttx(different for horizontal teams)20:24
annegentledeliverable maybe?20:24
annegentledhellmann: sounds good20:24
ttxok, I'll write up somthing on the review20:24
*** bswartz has quit IRC20:24
flaper87I don't just want to see what happens, I want to make sure the get the right guidance too20:24
ttx#action ttx to close the kiloeyes request by directing them to unofficial/stackforge space for the time being20:25
ttxMoving on...20:25
jeblairflaper87: yeah, "talk with monasca and see what comes of that" sounds really good20:25
ttx#topic Deprecation policy tags20:25
*** openstack changes topic to "Deprecation policy tags (Meeting topic: tc)"20:25
flaper87jeblair: ++20:25
ttxFirst part20:25
ttx#link https://review.openstack.org/20746720:25
ttxSo I updated this to match N+2 deprecation, as several of you requested. I had two questions left20:25
ttxFirst question is do we really want to describe a "never deprecate, always support" model20:26
ttxI kind of went back-and-forth on this one, and I tend to think now that saying you won't ever change is not really honest anyway, so the value of asserting that is limited20:26
russellb"never" is a long time20:26
russellbi don't think it's honest20:26
dhellmannagreed20:26
ttxThere is more value in describing a "common deprecation policy" which sets a minimal standard and then ask projects if they want to assert that they follow (at least) that level20:26
ttxSet a baseline, basically20:26
dhellmann++20:26
russellb++20:26
flaper87++20:26
jgriffith++20:26
ttxOK, so I'll amend the proposal to remove the "never say never" one20:27
*** jroyal has quit IRC20:27
annegentleyep20:27
ttx#action ttx to amend 207467 to remove will-support-everything-forever variant20:27
ttxSecond question is... should we (the TC) top-down define what we mean by "deprecation policy baseline" and ask projects to assert if they will follow it... or should we somehow open the definition for ML consensus20:27
lifelessdoes *any* openstack project gurantee forever?20:27
ttxOne part of me thinks that we should open the discussion, another part of me thinks this needs to be opinionated and not be the lowest common denominator20:27
*** elo1 has joined #openstack-meeting20:27
*** elo1 has quit IRC20:27
ttxlifeless: I heard Swift claim that20:27
annegentlelifeless: I could see it being valuable for CERN and object storage20:28
jgriffithttx: personally I prefer opinionated and just have it20:28
*** zul has joined #openstack-meeting20:28
lifelessnotmyname: ^20:28
dhellmannttx: we have an established community standard here, so I think it's reasonable to start with that. If projects want to propose other models, that is also reasonable.20:28
markmcclainttx: I do have a question about the migration requirement... would an acceptable answer be something is deprecated and has no migration?20:28
ttxsometimes in the past. They might have been drunk though20:28
jgriffithttx: I think there's good representation of the projects here on the TC to justify that20:28
russellbi don't think the N+2 is least common demoninator, it's a reasonable common policy20:28
*** achanda has quit IRC20:28
russellbseems like a good place to start20:28
*** achanda has joined #openstack-meeting20:28
ttxmarkmcclain: I think you need to provide a way out20:29
flaper87That's what we've been following somehow20:29
*** emagana has quit IRC20:29
flaper87or at least tried to follow to the best of our capacities20:29
jgriffithflaper87: +120:29
markmcclainright but what if we support a feature that just does not make sense in the future?20:29
ttxnot necessarily a migration tool or anything. Then you need to survey your users and see how much time they need to implement that migration20:29
jgriffithflaper87: at least it's been our minimum20:29
*** jeadr has quit IRC20:29
jgriffithflaper87: reality has been a different story :(20:29
flaper87so, lets be opinionated here since N+2 has proven to be a good policy so far20:29
*** jroyal has joined #openstack-meeting20:29
flaper87jgriffith: yeah20:29
*** PrashantS has joined #openstack-meeting20:30
flaper87:(20:30
*** geoffarnold has quit IRC20:30
ttxmarkmcclain: migration can be "that feature was stupid, so you should stop using it" but then survey needs to confirm that everyone agrees it was stupid20:30
flaper87and the community is not strange to the concept and policy20:30
*** jeadr has joined #openstack-meeting20:30
jgriffithcould be more... shouldn't be less20:30
*** PrashantS has quit IRC20:30
* flaper87 should write longer messages rather than using IRC as if it were whatsapp20:30
*** geoffarnold has joined #openstack-meeting20:30
*** epcim has quit IRC20:30
ttxmarkmcclain: so I guess the answer to your question is "it depends"20:30
flaper87jgriffith: +120:31
*** PrashantS has joined #openstack-meeting20:31
markmcclainttx: ok.. as long as that option should available... concerned that if we require even a minimum migration we never be able to get rid things many would consider mistakes20:31
*** Piet has joined #openstack-meeting20:31
jeblairopinionated++20:31
ttxmarkmcclain: I think what we require is discussion of the proposed migration with the users20:31
markmcclainmakes sense20:31
ttxeven if "proposed migration" =~ "stop using it"20:31
ttxLet's move to the second change here: config option deprecation policies20:32
*** nadya has quit IRC20:32
ttx#link https://review.openstack.org/20758420:32
ttxwe have two options: we can track it separately from API/feature deprecation policy assertion20:32
ttxor we can amend the API/feature tag to make clear config options are part of the user-visible stuff that is covered20:32
flaper87ttx: merge them!20:33
ttxPersonally I think the latter makes more sense and is less confusing. I just don't picture a project would have one but not the other20:33
*** emagana has joined #openstack-meeting20:33
ttx+which20:33
lifelesswell20:33
*** pballand has quit IRC20:33
lifelessI can see placing a different standard of burden on users and operators20:33
*** ajiang_ has quit IRC20:33
*** bhakta has quit IRC20:33
ttxor rather, not sure we need that granularity20:33
flaper87To me, by default, everything the user can interact with should follow the same deprecation path. There may be exceptions, sure, but...20:33
lifelessoperator churn doesn't affect workload portability, for instance20:33
ttxlifeless: that's a good point20:33
*** ajiang has joined #openstack-meeting20:34
annegentleI think api compat is much more "watched" by users but that may be from where I sit maintaining API docs20:34
ttxso it's more operator-visible features deprecation and users-visible feature deprecation ?20:34
*** bhakta has joined #openstack-meeting20:34
flaper87annegentle: no really, just different users.20:34
annegentleI see a separation myself -- each user type has different expectations20:34
flaper87When it comes to deprecating things, I prefer to consider everyone as users20:35
flaper87without any separation20:35
ttxflaper87: yeah, I lean towards that too20:35
annegentleflaper87: I suppose so, you can avoid consternation for all parties then20:35
lifelessttx: I would assert so yes. Its entirely possible we'll treat everyone the same in future, but that hasn't been the case so far20:35
*** VW_ has quit IRC20:35
annegentlehonestly APIs that are extensible are at the mercy of provider decisions anyway20:35
*** VW_ has joined #openstack-meeting20:35
*** vivek-ebay has quit IRC20:36
ttxwho is with flaper87, who is with lifeless ?20:36
*** elo1 has joined #openstack-meeting20:36
annegentleso, same deprecation everywhere20:36
flaper87flaper87 flaper87 flaper87 flaper8720:36
ttxannegentle is with flaper8720:36
* flaper87 stops that20:36
lifelessI don't think our tags should be aspirational :)20:36
dhellmanndo we actually anticipate different policies at this point?20:36
lifelessthey should be reflecting useful differences we already have20:36
ttxdhellmann: currently we expect all ex-integrated projects to assert both20:36
ttxsince it was an unofficial rule for them anyway20:37
*** Piet has quit IRC20:37
dhellmannttx: i mean would the timelines be different20:37
lifelessright20:37
annegentledhellmann: I was thinking of microversions versus nova.conf20:37
lifelessnova API deprecations are yyyyears long20:37
russellb39335520:37
lifelessnova.conf deprecations are cycles long20:37
lifelessrussellb: 1100766320:37
*** pballand has joined #openstack-meeting20:37
russellb:)20:37
flaper87lifeless: many times is because people simply forget to remove deprecated things20:38
flaper87but I don't know about nova20:38
flaper87:P20:38
ttxdue to their nature, assertions are a bit difficult to tweak once they are defined (you have to confirm any mod with all the projects that asserted the tag, so I'd prefer to get them right20:38
dhellmannlifeless: could we agree to put both of those timelines in one tag?20:38
*** puranamr has joined #openstack-meeting20:39
ttxI think it's fine to have them both in a single tag. If we need to split it in the future that's easier than the other way around20:39
lifelesssure20:39
annegentleyep20:39
ttxIf we realize there is need to track/communicate something more... granular, we can split it then20:40
*** dflorea has joined #openstack-meeting20:40
ttxbut I'll make sure I talk about operator-facing and enduser-facing stuff20:40
ttxin whatever language I come up with20:40
*** rbak has quit IRC20:40
*** VW_ has quit IRC20:40
ttxso that it's clear that the tag currently asserts both20:40
*** sahid has joined #openstack-meeting20:40
flaper87mmh, I'm still not convinced we should separate them from a deprecation perspective20:40
*** changbl has quit IRC20:40
flaper87I guess I'll comment on the review20:40
ttxflaper87: we aren't20:40
*** rbak has joined #openstack-meeting20:40
flaper87oh ok20:40
flaper87I was confuised by your comment20:40
flaper87sorry20:41
flaper87confused, even20:41
ttxAlright, I'll take care of the big merging20:41
ttxnext topic20:41
ttx#topic Adds and apply guidelines for project and service names20:41
*** openstack changes topic to "Adds and apply guidelines for project and service names (Meeting topic: tc)"20:41
ttx#link https://review.openstack.org/20116020:41
ttx#link https://review.openstack.org/20167020:41
*** angdraug has quit IRC20:41
ttxannegentle: are we making progress or is it just a neverending circle of rebases ?20:41
*** angdraug has joined #openstack-meeting20:42
flaper87annegentle: I left a "-1 I have a question, I'm sorry it shouldn't be -1 please don't hate me" comment20:42
*** neiljerram_bb has joined #openstack-meeting20:42
annegentlettx: Had a breakthrough this week; keep Block Storage20:42
annegentlettx: so the updates have been to support initial caps20:42
annegentlettx: I sense this is where most people want naming to land20:42
annegentleflaper87: no worries20:42
*** hrou has quit IRC20:43
ttx"Block Storage service" ?20:43
annegentlettx: check20:43
dhellmannannegentle: we should talk about auto-generating expansion macros for sphinx from the projects.yaml file20:43
*** gyee has joined #openstack-meeting20:43
annegentleexpansion macros?20:43
russellb70248720:44
russellb72222820:44
*** jichen has quit IRC20:44
russellbdangit20:44
annegentleflaper87: so kiloeyes could be the metric measurement I spose... I don't think release names are "reserved"20:44
ttxrussellb turned into a WWII number station20:44
* dhellmann thinks russellb is multi-tasking20:44
annegentleflaper87: I honestly didn't make the connection for a bit20:44
*** jungleboyj has joined #openstack-meeting20:45
flaper87annegentle: I did, to be honest. When dhellmann mentioned I was like "So, I was not the only one"20:45
*** britthou_ has joined #openstack-meeting20:45
flaper87annegentle: but I see your point20:45
*** lblanchard has quit IRC20:45
lifelessI'm sorry, I can't read kiloeyes and not think of the 5-eyes spy network... if thats deliberate its most unfortunate20:45
annegentleflaper87:  That said, I wonder if we should talk about "reserved words that cannot go into a service name such as copyrighted names?"20:46
ttxannegentle: so.. you have all you need to make progress ?20:46
annegentledoes the list of "don't do" belong in the guidelines?20:46
annegentlettx: I think so20:46
lifelesscan a name be copyrighted?20:47
flaper87annegentle: I believe that list should be there20:47
annegentlelifeless: um did I verb a noun?20:47
ttxIANAL but I don't think so.20:47
*** esker has quit IRC20:47
flaper87if anything, it'll help us to review names properly20:47
lifelessannegentle: I think you hopped intellectual property tracks :)20:47
*** britthouser has quit IRC20:47
annegentlelifeless: right20:48
*** MeganR has left #openstack-meeting20:48
annegentleflaper87: yeah, and the point of the guidelines is for reviewing20:48
annegentlelifeless: was thinking of the Chef/Puppet permissions20:48
ttxother questions on that one ?20:48
ttxI guess not20:49
*** topol has quit IRC20:49
ttx#topic Workgroup reports20:49
*** openstack changes topic to "Workgroup reports (Meeting topic: tc)"20:49
ttx* Project team guide20:49
ttxI approved the initial version for the missing chapter, so the initial version of the guide is now complete20:50
ttxWe just need to publish it.20:50
jeblairthat means i need to publish it20:50
flaper87ttx: danke and sorry for the dely20:50
ttxjeblair: indeed20:50
flaper87jeblair: <.<20:50
* jeblair stops hiding behind flaper87 20:50
*** padkrish has quit IRC20:50
flaper87HA! I knew you were there20:50
*** IanGovett1 has quit IRC20:50
annegentlenice!! Way to go.20:50
annegentlethat's really impressive20:50
*** padkrish has joined #openstack-meeting20:51
ttxfor the curious ones, let me get a URL20:51
*** britthou_ has quit IRC20:51
ttxhttp://docs-draft.openstack.org/67/194567/3/gate/gate-project-team-guide-docs/7a3af25//doc/build/html/20:51
ttx(that's the gate build for the latest merge)20:51
russellbdhellmann: ttx yubikey nano.  convenient, except easy to hit when moving laptop around20:52
*** Sukhdev has quit IRC20:52
fungiemulates a keyboard, types one-time passwords into your irc client ;)20:52
ttxjeblair: any idea when you can work on that ? Or should someone else take the job ?20:52
*** derekh has quit IRC20:52
jeblairttx: can do this week.20:52
ttxawesome20:52
ttx* Comms20:53
ttxannegentle, flaper87: o/20:53
flaper87'sup ?20:53
annegentleholla20:53
russellbfungi: yeah..20:53
ttxannegentle, flaper87 not sure we need another post right now20:53
annegentleI got a blog post out, late, last 2 week intervals.20:53
annegentle#link http://www.openstack.org/blog/2015/08/technical-committee-highlights-august-11-2015/20:53
flaper87I've been lacking in the last couple of weeks. annegentle, sorry about that.20:53
annegentletwo 2-week intervals20:53
ttxgiven that we didn't have a meeting last week and this week(s is very transitional20:53
annegentleflaper87: no worries20:53
annegentlettx: agreed20:53
ttx* Next tags20:54
annegentlekeep getting input on whether those are useful20:54
ttxWe still are processing the first wave of new tags, so no new things here20:54
ttx* Other20:54
ttxTwo weeks ago we discussed two areas of focus for the rest of the cycle: making progress on the service catalog, and improving cross-project discussion in general20:54
* flaper87 loves ttx's quote on that post20:54
ttxHow should we make that happen ? Should we form *other* workgroups that would meet outside of the weekly TC meeting ?20:54
annegentleflaper87: :)20:54
* ttx needs to work on the successbot20:55
ttxAn IRC bot to celebrate little successes20:55
annegentlettx: do you think we could move the weekly cross project meeting as an experiment?20:55
*** padkrish has quit IRC20:55
annegentlettx: nice20:55
ttxannegentle: move to ?20:55
jeblair#fail jeblair hasn't made a failbot yet either20:55
ttx#success The initial project team guide is now complete !20:56
* flaper87 does the success dance20:56
annegentlettx: earlier in the day -- if the history is that we held it after the TC meeting for a reason (Chair responsibilities? The original timing escapes me) could we try another day/time?20:56
annegentlettx: I know, I know, it sucks to move meetings20:56
flaper87I'd be happy to have it moved, really20:56
flaper87but if that ends up in fewer CPL attending, then no.20:57
ttxannegentle: it's worth having the discussion I guess. You could start it on the ML. We could certainly rotate20:57
*** cdelatte has quit IRC20:57
ttxany time before would be very APAC-unfriendly20:57
ttxthe current one already kinda is20:57
flaper87right20:57
*** AmirBaleghi1112 has joined #openstack-meeting20:57
*** dflorea has quit IRC20:57
annegentleright20:57
*** elmiko has joined #openstack-meeting20:57
*** tpatil has joined #openstack-meeting20:57
annegentlettx: ok20:57
ttxthe current timing opts to be a pain from Russia to China20:58
flaper87I've a quick Open Discussion topic20:58
ttx#topic Open discussion20:58
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:58
*** mriedem has joined #openstack-meeting20:58
*** xyang1 has quit IRC20:58
annegentle#acton annegentle to bring cross-project meeting time to -dev mailing list20:58
flaper87So, I've been contacted by Cindy Pallares. She's working with a submcmittee to improve OpenSTack's CoC20:58
annegentleI had a question about extra ATC, they don't seem to be publishing to project pages on governance.openstack any more20:58
flaper87One thing she asked me is how we can help enforcing it and who, from the governance side, can help with that20:59
ttxI just want something to emerge from our discussion on priorities at the last meeting. Saying we need to complete the service catalog changes is one thing, doing it would be better20:59
flaper87I'll invite her next week to share what they are doing20:59
flaper87where they are at, etc.20:59
annegentleSee http://governance.openstack.org/reference/projects/keystone.html for an example20:59
flaper87That way we can provide some guidance/support from our side20:59
ttxbut I have my hands full with various other workgroups and TC initiatives, so I can't lead either20:59
flaper87turns out our CoC is not good enough20:59
annegentleflaper87: I thought there was an ombudsman group on the board that provided governance for CoC?20:59
flaper87#link https://www.openstack.org/legal/community-code-of-conduct/20:59
*** julim has quit IRC21:00
ttxflaper87: probably just a bug21:00
flaper87annegentle: I believe she's working with them as well21:00
EmilienMit's crossproject meeting time21:00
flaper87ttx: LOL21:00
annegentlettx: agreed on the doing it...21:00
flaper87EmilienM: 1 minute21:00
flaper87:P21:00
annegentle:)21:00
flaper87ttx: just saying, lets give her some time next week21:00
*** zul has quit IRC21:00
ttxflaper87: sure, add it to the agenda this week21:00
flaper87It should be good to support the effort from our side21:00
markmcclain++21:01
*** BadCub has left #openstack-meeting21:01
*** sridhar_ram has quit IRC21:01
*** vijendar has quit IRC21:01
ttxand that concludes our meeting21:01
flaper87would*21:01
flaper87:P21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Aug 18 21:01:13 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-08-18-20.02.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-08-18-20.02.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-08-18-20.02.log.html21:01
flaper87EmilienM: now it's CP time ;)21:01
*** dflorea has joined #openstack-meeting21:01
flaper87:P21:01
*** vijendar has joined #openstack-meeting21:01
flaper8723:00 here21:01
EmilienMcrossproject meeting is about to start, courtesy ping for david-lyle flaper87 dims dtroyer johnthetubaguy rakhmerov smelikyan morganfainberg adrian_otto bswartz slagle adrian_otto mestery kiall jeblair thinrichs j^2 stevebaker mtreinish Daisy Piet notmyname ttx isviridov gordc SlickNik cloudnull loquacities thingee hyakuhei redrobot dirk TravT21:01
ttxEmilienM: sorry about that. Those TC dudes are just abusive21:01
elmikolol21:01
* mestery lurks21:01
david-lyleo/21:01
EmilienMttx: that's why we elected them.21:01
j^2:D21:01
EmilienM#startmeeting crossproject21:01
openstackMeeting started Tue Aug 18 21:01:52 2015 UTC and is due to finish in 60 minutes.  The chair is EmilienM. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** krtaylor has quit IRC21:01
*** openstack changes topic to " (Meeting topic: crossproject)"21:01
* bknudson lurks21:01
openstackThe meeting name has been set to 'crossproject'21:01
EmilienM#link Agenda: https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting21:01
loquacitieso/21:01
EmilienMThis is my first time I'm leading this meeting, please be kind :-)21:02
mriedemo/21:02
* ttx will heckle21:02
Daviey\o21:02
nikhil_k_o/21:02
johnthetubaguyo/21:02
*** pnavarro has joined #openstack-meeting21:02
* edleafe is here but has to leave soon21:02
fungiEmilienM: we're a gentle lot21:02
edleafebut only for your first time21:02
jungleboyjo/21:02
elmikoo/21:02
EmilienM#info Meeting Chairs still needed for September 1, September 29, and October 1321:02
gordco/21:02
*** jeadr has quit IRC21:02
tpatilHi21:02
EmilienMlike mestery said in the previous meeting "Signups appreciated!"21:02
*** Piet has joined #openstack-meeting21:03
mesteryEmilienM: +1000 :D21:03
EmilienM#topic Team Announcements (horizontal, vertical, diagonal)21:03
EmilienMplease use #info <content>!21:03
ttxAnd thanks to EmilienM who signed up for 2 slots21:03
*** openstack changes topic to "Team Announcements (horizontal, vertical, diagonal) (Meeting topic: crossproject)"21:03
ttxNothing specific from release management.21:03
ttxRemember liberty-3 and feature freeze come in two weeks21:03
*** jeadr has joined #openstack-meeting21:03
*** MaxPC has quit IRC21:03
ttx(for those stil following that)21:03
ttx+l21:03
*** dflorea has quit IRC21:03
*** ccavanna has quit IRC21:03
*** sridhar_ram has joined #openstack-meeting21:04
*** xarses has joined #openstack-meeting21:04
lifelessEmilienM: no courtesy ping for the tc members ?21:04
EmilienMI have a useful information: Puppet OpenStack CI is running Liberty packages in their CI - we are close to trunk now21:04
nikhil_k_EmilienM: just fyi, I did not get a courtesy reminder. possibly some other folks didn't too21:04
EmilienMlifeless: I copy pasted from other meetings, my bad if I missed you21:04
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/072140.html21:04
fungimass rename of git repos from stackforge to openstack being scheduled21:04
fungiweigh in on the thread if you have concerns/questions21:04
xarseso/21:04
EmilienM#info Puppet OpenStack CI bumbed to liberty21:04
mesteryttx: 2 weeks!!!21:04
lifelessEmilienM: you missed annegentle too21:04
ttxmestery: I must be getting old, but time really flies21:05
EmilienMlifeless: ok, sry for that21:05
lifelessnp21:05
mesteryttx: Greybeards :)21:05
*** browne has left #openstack-meeting21:05
*** stevemar has quit IRC21:05
*** _amrith_ is now known as amrith21:05
*** neelashah has quit IRC21:05
EmilienMdo we have any other useful and exciting team announcements?21:06
elmikosadly, no new api-wg guidelines this week21:06
EmilienMI guess we can go ahead into the agenda then21:07
*** aysyd has quit IRC21:07
*** pnavarro has quit IRC21:07
gordcnods21:07
EmilienM#topic How to generate .Z version increments on stable/liberty commits21:07
EmilienM#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/072216.html21:07
*** openstack changes topic to "How to generate .Z version increments on stable/liberty commits (Meeting topic: crossproject)"21:07
EmilienMttx: o/21:08
lifelesswheeee21:08
*** jckasper has quit IRC21:08
lifelessthis'll be fun21:08
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/072216.html21:08
ttxSo this is about agreeing on the way forward for stable point releases21:08
fungigo to your corners and come out swinging21:08
ttxIt feels like the recent discussion is converging toward the use of openstack/releases for stable branch releases21:08
ttxand doing "frequent", separated point releases for every service component rather than one-per-commit21:08
lifelessI kindof feel that we haven't actually define the constraints and success criteria21:08
ttxThe drawbacks with that option being that consumers of the stable branch are unnecessarily limited to specific tagged commits21:08
Davieyerr, not sure there was convergence on that..21:08
ttxand we all depend on various project teams to remember to push them21:09
*** puranamr has quit IRC21:09
ttxDaviey: ok, good!21:09
*** raildo is now known as raildo-afk21:09
mriedemwe expect project teams to care about stable? :)21:09
fungiit feels to me like the discussion on dropping stable point releases has circled back around to how to orchestrate stable point releases21:09
*** amotoki has joined #openstack-meeting21:10
*** jroyal has quit IRC21:10
clarkbmriedem: maybe not the entire team but surely there are a subset that care?21:10
*** rbak has quit IRC21:10
jungleboyjclarkb: ++21:10
DavieyI think the question needs to be, how can we enable each commit to be a release without tainting ref tag namespace but have deterministic release versions.21:10
mriedemdon't call me shirly21:11
ttxIn Vancouver we established that frequent and/or automated releases with autogenerated release notes was the only way to sclae the stable branch point release process in bigtent world21:11
bknudsonwe could keep squashing commits in stable branch until we feel like committing21:11
ttxthat leaves us with the question that Daviey eloquently put21:11
clarkbbknudson: thats ugly particularly if something breaks and you need to bisect21:11
fungiwell, only way to scale it if the alternative of dropping them was off the table21:11
*** austin81 has left #openstack-meeting21:12
ttxOriginal proposal was tagging every commit, to which clarkb objected21:12
johnthetubaguyDaviey: what about if we just release the ones people need?21:12
mriedemjohnthetubaguy: that's totally subjective though right?21:12
Davieyjohnthetubaguy: then we are back to doing release management and cutting releases?21:12
fungipart of this, i think, is examining the alternative implementations and determining if there's one that's not more absurd than just not making stable point releases21:12
johnthetubaguyDaviey: true21:12
*** padkrish has joined #openstack-meeting21:13
johnthetubaguymriedem: yeah, just trying to dream up a middle ground.... not sure that works21:13
*** rfolco has quit IRC21:13
Davieyfungi: Sorry, can you rephrase?21:13
fungittx: to be fair, the original original proposal was to stop making stable point releases21:13
mriedemyeah21:13
ttxfungi: but then people asked for reference points, which is a fair request21:13
mriedemmy team releases from stable when we need to, not based on community schedules21:14
*** krtaylor has joined #openstack-meeting21:14
johnthetubaguyttx: can we fix that with tooling?21:14
* dims peeks in late21:14
lifelessDaviey: why does that need to be the question ? :)21:14
fungiDaviey: yes, i don't feel like we've yet arrived at a proposed implementation that is less crazy than a) continuing what we already do, or b) no longer doing it21:14
Davieylifeless: Why /doesn't/ it need to be the question? :)21:14
ttxfungi: I guess a combination of none + some ref points could be "on-demand tagging"21:14
*** ivasev has joined #openstack-meeting21:14
mriedemttx: that's basically what tempest does21:14
mriedemtags for interesting points in time21:14
lifelessDaviey: what problem does having each commit be a release solve ?21:14
*** amotoki has quit IRC21:15
ttxAt this point I'm fine with that (tagging once in a while), since it's definitely an improvement21:15
lifelessDaviey: where release is defined as 'has a fixed well known version number suitable for uploading to a package repository like PyPI'21:15
ttxand we need /something/ before liberty release21:15
fungimriedem: yep. keep in mind that a lot of what the stable branch release managers were doing was taking care of that process for the majority of projects which really only cared about their master branches21:15
johnthetubaguyyeah, I guess on demand tagging is what I was meaning, but that means something needs doing, rather than it being automatic21:15
lifelessDaviey: (because even though we don't upload the servers, we do upload the libs)21:15
*** flashgordon is now known as jogo21:15
mriedemfungi: yeah, hence my earlier rhetorical question21:15
Davieylifeless: The issue is that upstream + Daviey's-secret-sauce == differnet pbr version to what upstream + lifeless's-secret-sauce is.. but 'people' compare releave version numbers21:15
*** stevemar has joined #openstack-meeting21:16
clarkbright so this is one of the major failings in pep44021:16
Daviey(not to mention semver release requirements for dep handling)21:16
clarkbbut that ship has sailed and we did the best we can21:16
lifelessDaviey: sure. And pbr doesn't try to solve the 'distributed version number allocation' problem.21:16
clarkbyou can ask pbr for a specific sha1 if/when necessary21:16
Davieylifeless: Yeah, so we need a x.x.x+y thing?21:16
ttxWho is against "tagging once in a while", using the current openstack/releases framework ?21:16
lifelesspbr based versions from untagged commits are simply not globally unique.21:16
*** mrmartin has quit IRC21:17
lifelessthey are also not suitable for uploading to an index21:17
*** jecarey has quit IRC21:17
clarkblifeless: but they do have globally unique attributes that you can query21:17
lifelessDaviey: no, that doesn't solve it21:17
lifelessclarkb: they do21:17
clarkbbut yes doesn't solve the upload to index problem21:17
johnthetubaguyttx: honestly, it feels like a good starting point while we invent something better21:17
Davieyttx: Tagging once in a while is worst of all worlds, no?21:17
ttxDaviey: explain why21:17
johnthetubaguyDaviey: it reduces the release all the projects now problem21:17
ttxDaviey: it's like not releasing + adding reference points that people ask for21:18
johnthetubaguy(I think)21:18
lifelessttx: I think tagging is a key component in any route forward21:18
fungi"tagging once in a while" implies there's someone doing that, so a prerequisite question is whether there's someone willing to do that21:18
ttxlifeless: right21:18
johnthetubaguyfungi: thats my biggest concern with it, +121:18
lifelessfungi: while True: if random()> 0.9 then git tag...21:18
Davieyttx: We still cut releases, but half assed?21:18
ttxfungi: if that's the only question, we can open up to the PTLs in the crowd and ask them if their stable release liaisons would do that21:18
DavieySo the same burden, but no gain?21:18
*** pnavarro has joined #openstack-meeting21:18
ttxDaviey: no more stable release managers though21:19
* lifeless is still fundamentally unsure of the problem we're trying to solve.21:19
bknudsonI watch stable for keystone and I'm willing to propose changes to releases when I think it's ready.21:19
*** puranamr has joined #openstack-meeting21:19
johnthetubaguymriedem: do you fancy more work?21:19
ttxDaviey: the request would come from the project teams themselves. Also automated release notes would make them cheap21:19
mriedemthere are several projects that already don't really seem to care all that much about stable, so i don't see why it matters if they don't care about tagging21:19
lifelesswhat stops folk consuming stable branches consuming them if we don't 'make every commit a release' ?21:19
mriedemjohnthetubaguy: sure21:19
Davieyttx: And we are sure projects will drive stable cuts?21:19
lifelesswhy are we doing this /at all/ ?21:19
mriedemDaviey: they won't21:20
ttxlifeless: because people want to be able to say "this vulnerability is fixed in X.Y.Z21:20
Davieylifeless: You've been in this debate before, no?21:20
mriedemDaviey: not all21:20
ttxand I run X.Y.Z+121:20
johnthetubaguymriedem I do think you are hitting on something there about folks not caring too much about stable right now21:20
mriedemi think of this like when we do novaclient releases,21:20
bknudsonmaybe we only backport security fixes for all things21:20
ttxso they need some reference points. At the very least around vuln fixes21:20
mriedemwe do them as needed/requested21:20
bknudsonthen there would be fewer backports21:20
mriedembknudson: there are more than security fixes we need21:20
mriedemlike things that impact upgrades21:20
lifelessttx: ok, so its to distribute the ability to assess whether a security fix is included to a local version-check ?21:21
lifelesss/security/important/21:21
ttxlifeless: it's also about comparison between distros IIUC21:21
ttxi.e. make X.Y.Z mean the same thing everywhere21:21
lifelessok. So I'd like to make an assertion.21:21
*** redixin has quit IRC21:21
lifelessthere are two well known ways to solve this.21:21
Davieylifeless + ttx: So rather than say, 2015.1.5 i'd say $release + x upstream commits ~= a semver release.21:21
*** zul has joined #openstack-meeting21:22
lifelessA) Centrally assigned numbers.21:22
lifelessB) the VCS DAG.21:22
nikhil_k_umm, that is tricky21:22
johnthetubaguyttx: cross distro comparison is a deal breaker, +121:22
nikhil_k_how much would be ~ ?21:22
*** yottatsa has joined #openstack-meeting21:23
lifelessDo we have agreement that we're looking at either A or B; further if we want to flatten things into 'version numbers' then B is infeasible.21:23
Davieycross distro comparison is overated IMO. :)21:23
ttxlifeless: if you tell me what DAG is, maybe21:23
*** thangp has quit IRC21:23
mriedemDaviey: agreed21:23
lifelessttx: the directed acyclig graph21:23
Daviey#link http://ericsink.com/vcbe/html/directed_acyclic_graphs.html21:23
clarkbttx: basically the git tree that represents the repos history21:24
lifelessttx: e.g. cross referencing git commits to determine if 'feature X is in my tree'21:24
johnthetubaguyis the DAG different to your list of commits?21:24
ttxah, hmm21:24
lifelessjohnthetubaguy: same same21:24
Davieythe FAG is an assured list of commits, right?21:24
Davieyerr DAG*21:24
*** jeadr has quit IRC21:24
lifelessjohnthetubaguy: DAG implies more structure, but for our needs we're looking at set membership21:24
johnthetubaguylifeless: for security fixes, yeah21:25
ttxI think version numbers are the thing and downstream expects to have it21:25
*** tiswanso has quit IRC21:25
ttxerr21:25
*** jeadr has joined #openstack-meeting21:25
clarkbB is something we can do today if you query package metadata21:25
ttxI mean, are the thing upstream expects to get21:25
johnthetubaguylifeless: so if we give each commit a version off master, we can find that in other peoples trees, and find the number?21:25
*** mestery has quit IRC21:25
ttxdammit, "downstream"21:25
ttxgetting late21:25
Davieylifeless: Are you leading towards deterministic version numbers based on the upstream DAG?21:26
clarkbDaviey: I don't think that is possible under pep44021:26
*** rbak has joined #openstack-meeting21:26
*** pballand has quit IRC21:26
bknudsondon't distros all cherry-pick different patches on top of whatever we release?21:26
clarkbbecause even upstream we can have >1 proposed next states21:26
Davieyclarkb: SemVer based on upstream signed commits?21:26
lifelessclarkb: sadly thats not preserved by e.g. dpkg or rpm21:26
ttxbknudson: they still use our version numbers as base21:26
*** PrashantS has quit IRC21:27
clarkbDaviey: yes we can do it based on signed tags but not the raw DAG21:27
clarkbdoing it based onthe raw DAG is what PBR tried to do until the pep440 mess happened last december21:27
clarkbthen we all had a sad21:27
*** Piet has quit IRC21:27
Davieyah21:27
*** PrashantS has joined #openstack-meeting21:27
lifelessjohnthetubaguy: thats how (B) might work. But I think its too big a mismatch vs x.y.z style numbering21:27
mriedemttx: i assume bknudson's point though is that regardless of version you're probably getting a different set of commits from different distros21:28
lifelessDaviey: I'm trying to make sure I actually have a handle on everyones concerns21:28
lifelessso here's my concern21:28
johnthetubaguylifeless: I was thinking it just defines the z, the rest is based off a tag, but it seems... messy21:28
ttxmriedem: arguably with the same common base, though.21:28
lifelessif I pull nova kilo21:28
lifelessand do a commit21:28
mriedemttx: sure21:28
lifelessthat MUST NOT be confused with the next commit that lands in git.o.o/nova's kilo branch21:29
*** jroyal has joined #openstack-meeting21:29
lifelessor we've failed at the requirement that you can tell if you've got fixes from there21:29
ttxlifeless: yes21:29
lifelessthis means that regular old commits are not sufficient, even if we changed pbr21:30
*** jecarey has joined #openstack-meeting21:30
lifelessso we're looking at centrally assigned version numbers.21:30
ttxI see no way out of assigning version numbers through a tag. And if that results in pollution, then we should tag less often.21:30
Davieybut equally, as a consumer from git.. i probably need to apply patches and have incrementing version numbers for my site (i don't)21:30
clarkblifeless: they could be if pep440 allowed a unique non sorted identifier21:30
clarkblifeless: but it doesn't so yes21:30
johnthetubaguybut can't we just imply the tag from when the commit lands in master?21:30
johnthetubaguyfor every commit?21:30
johnthetubaguyI guess I just missed a bit21:31
lifelessclarkb: Even if pep-440 permitted that there'd be no way to distinguish the real thing from the local thing21:31
Davieylifeless: but yeah, central or otherwise deterministic version numbers seems to be the requirement21:31
lifelessclarkb: so pep-440's limits don't alter this21:31
lifelessDaviey: no, *central* specifically.21:31
clarkblifeless: you would be able to distinguish between the two, but not determine which is canonical21:31
ttxIs anyone other than Daviey against the "push a tag now and then" approach ?21:31
lifelessclarkb: right21:31
Davieylifeless: why do we care if Central or distributed ?21:31
lifelessclarkb: and the canonical aspect is required to answer the 'and I have importance fix X'21:31
lifelessclarkb: which is an input requirement21:31
clarkblifeless: it isn't21:31
johnthetubaguyDaviey: comparing across distros, for security fixes?21:32
clarkbat least it isn't required ot have that encoded in the version21:32
*** PrashantS has quit IRC21:32
*** penick_ has joined #openstack-meeting21:32
clarkblifeless: the human can compare the non sorted unique identifier against what they know to be canonical21:32
Davieyjohnthetubaguy: no, even if distributed it is still deterministic21:32
lifelessclarkb: I'm not smart enough to see how it would, but since you agreed that we can't do whatever you're thinking of anyway, lets move on.21:32
johnthetubaguyDaviey: OK, I am not seeing the distributed one properly right now it seems21:32
*** otter768 has joined #openstack-meeting21:32
lifelessDaviey: if its distributed anyone can allocate numbers right ?21:32
*** jroyal has quit IRC21:33
*** singleth_ has quit IRC21:33
Davieylifeless: If pbr counts OpenStack signed tags, for example... it isn't centralised.. right?21:33
lifelessDaviey: but there's only one source of truth for 'security fix X in nova/kilo'. So those numbers have to be unique and clearly identifiable21:33
DavieyBut whatever, this is imp' detail.21:33
EmilienMtime is running out, I suggest we close this topic shortly and maybe follow up on mailing list or during the next meeting21:33
lifelessDaviey: signed tags in the git.o.o nova tree are centralised21:34
*** SlickNik has joined #openstack-meeting21:34
ttxDaviey: so it seems you're the only one against the "tag now and then" approach. COuld you post something on ML explaining why ?21:34
ttxAnd taht would be our next step forward ?21:34
*** garthb has joined #openstack-meeting21:34
ttx(and we can move on to next topic) ?21:34
Davieyttx: Sure, but TL;DR is.. it is the same problem, with no additional improvement from what i can see.. Just moving the problem along to further tooling.21:34
*** AmirBaleghi1112 has quit IRC21:35
ttxI'll be happy to refute that on the ML. Next topic ?21:35
*** cbader has quit IRC21:35
EmilienMcool21:35
EmilienM#action ttx to followup .Z version increments on stable/liberty commits on the ML21:35
EmilienM#topic How to autogenerate release notes on stable/liberty commits21:36
*** openstack changes topic to "How to autogenerate release notes on stable/liberty commits (Meeting topic: crossproject)"21:36
*** stevemar has quit IRC21:36
ttx#action Daviey to explain why "tag now and then" is the 4th knight of the apocalypse on the ML21:36
EmilienM#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/072315.html21:36
EmilienMttx: o/ again21:36
ttxSo this is the side discussion -- we need to generate release notes so that if you pick a random commit on the stable branch you still have relevant release notes there21:36
ttx(and automate release notes creation for the point releases themselves)21:36
ttxDaviey suggested using git notes, and I suggested driving them from commit messages and openstack/releases change content21:36
*** rbak has quit IRC21:36
*** vivek-ebay has joined #openstack-meeting21:36
ttx(which would allow proper code review of them)21:36
ttxthat requires developing a Gerrit plugin similar to the reviewnotes plugin, and add features to pbr to generate releasenotes from git notes.21:36
DavieyYeah, probably more work than is worth.21:37
ttxBut then fungi said something about git notes requiring special config21:37
lifelessttx: so I am concerned about git notes21:37
*** otter768 has quit IRC21:37
lifelessttx: if it requires special config to get git to replicate the data needed to get pbr to produce the same output in a fresh clone21:37
ttxDaviey: I fail to have a better solution, and automated release notes are critical to make the "tag now and then" painless21:37
lifelessthen we'll be facing regular 'waah its different' requests21:37
*** geoffarnold has quit IRC21:37
bknudsonthis could help generate release notes on master, too.21:37
lifelessttx: like, I'm *really* concerned.21:37
ttxlifeless: agreed, I didn't know git notes were that encumbered21:38
lifelessttx: so I think we need to drill into the analysis that led you there much more carefully21:38
*** AmirBaleghi1112 has joined #openstack-meeting21:38
Davieyfungi: can .gitnotes not support core.logAllRefUpdates or whatever it is?21:38
ttxlifeless: isn't there some default ref space that is always exported or something ?21:38
lifelessttx: with an eye to acceptable compromises that will meet our needs21:38
lifelessttx: such as roll-forward via commits21:38
fungiDaviey: i'm not sure what you're asking21:39
Davieyfungi: err, .gitconfig21:39
ttxlifeless: ok, so let me redefine problem space quickly21:39
*** rbak has joined #openstack-meeting21:39
fungiDaviey: .gitconfig can. users would have to set it21:39
Davieyfungi: I'm saying, can per-tree not export a git config that would pull in notes without users having to make changes21:39
ttx* we want consumers of the stable branch (from random commit and from tagged versions) to get a valid release notes document21:39
fungiDaviey: my comment about configuration was that by default git doesn't fetch refs/notes/* and you need to configure it locally to do so21:39
bknudsonI wouldn't be able to push the notes anyways, would I?21:39
ttx* Some things in that document (like OSSA numbers) we only know after the commit is pushed so we need a way to retroactively fix those21:40
fungiDaviey: it's a per remote config, not a per repo config21:40
Daviey(i'm not that bought into notes, but it did seem an approach worth considering for this space)21:40
Davieyfungi: ah21:40
ttxbknudson: my proposal was to have Gerrit push them from other things that we code review21:40
ttxsee ml post21:40
ttxreferenced above21:40
bknudsonoh, cool.21:41
fungithe git authors assume you'll pull git notes potentially from multiple remotes into differet local refspaces, and have no idea what you want them called, so punts on doing that without explicit configuration21:41
mriedemgit log --oneline --no-merges <latest release>..21:41
mriedemcouldn't we just dump that in a thing?>21:41
*** rbak has quit IRC21:41
mriedemwhen we do a new release21:41
*** toscalix has joined #openstack-meeting21:41
ttxmriedem: that's a changelog, not release notes21:41
*** vivek-ebay has quit IRC21:41
lifelessmriedem: a) we do21:41
mriedemttx: yar21:41
lifelessmriedem: b) as ttx says21:41
Davieymriedem: The issue is enumerating through announcements and issues that need to be shared.21:41
mriedemyeah21:41
lifelessmriedem: this is what pbr creates today - https://mock.readthedocs.org/en/latest/changelog.html21:41
mriedemprocessing tags etc21:41
fungimriedem: point being that if we need the release notes to mention something that we didn't know at the time a commit message was written, there's no way to go back and revise the commit message after merge21:41
ttxI mean, we can also say that we don't do release notes for stable branches point releases21:41
ttxbut when we discussed that in YVR people kinda wanted them21:42
lifelessttx: so, what I've seen work well in the past is an in-tree data structure that can be updated via commits21:42
ttxEVEN if we stopped doing releases at all21:42
lifelessttx: I don't understand why that wouldn't work.21:42
bknudsondo we have release notes for stable releases now? (I don't remember updating any)21:42
mriedembknudson: yeah21:42
fungiwhen we discussed not doing stable point releases in yvr, some people basically said "that's okay as long as you can provide something else which is exactly like a stable point release"21:42
ttxlifeless: so you mlean amending backports to edit an additional document ?21:42
lifelessttx: the simplest possible implementation is a .rst file called 'RELEASENOTES.rst' in the tree.21:43
*** sileht has quit IRC21:43
Davieylifeless: merge conflicts?21:43
ttxThat was suggested on the ML and shot down, let me see why again21:43
mriedembknudson: e.g. https://wiki.openstack.org/wiki/ReleaseNotes/2015.1.121:43
ttxDaviey++21:43
lifelessttx: we can obviously do something much more sophisticated to address the issues that arise from using a DVCS etc etc.21:43
lifelessDaviey: ^21:43
lifelessI'm not proposing the simplest possible thing21:43
Davieylifeless: The other issue is looking back and thining, OH DAMN - we need to document $THIS21:43
lifelessDaviey: so you do that by editing the data structure.21:44
*** dkranz has quit IRC21:44
lifelessWhich is a commit.21:44
bknudsonwe could make it so that when the commit with the release notes is merged then that gets tagged21:44
DavieySO rewrite history?(!)21:44
lifelessDaviey: no21:44
lifelessDaviey: release notes are not a changelog21:44
lifelessDaviey: there is no conflict here.21:44
*** amitgandhinz has quit IRC21:44
*** Piet has joined #openstack-meeting21:45
ttxlifeless: oh, YOU were the one shooting it down. Funny heh21:45
mriedemwould be like updating the release notes wiki after kilo is released21:45
mriedemwe do that frequently21:45
bknudsonis https://wiki.openstack.org/wiki/ReleaseNotes/2015.1.1 genereated automatically?21:45
lifelessttx: possibly :)21:45
DavieyThe reason i suggested notes is that it is independent of the commit itself, but tied to a commit.21:45
ttx<lifeless> Something with the same process as ChangeLog generation today - read21:45
ttxfrom git, process, output document - will be much less fragile for merges.21:45
*** shashank_hegde has quit IRC21:45
mriedembknudson: don't think so, apevec created that21:45
EmilienM15 minutes left and we need to talk about 'Return request ID to caller" + Open Discussion21:45
johnthetubaguyttx: oh, merge conflicts, thats a good point...21:45
ttxjohnthetubaguy: that said lifless is right that you can build a directory structure and avoid those merge conflicts21:46
lifelessttx: so no21:46
lifelessttx: that wasn't shooting it down21:46
johnthetubaguyttx: I quite liked how yours has both autogenerated stuff and overrides, maybe we but the overrides in truee21:46
johnthetubaguyttx: oh, true21:46
Davieyttx: Maybe the fix is simple as, whomever +A's has responsibility for adding an entry to the wiki... Not clean IMO, but perhaps suitable?21:46
lifelessttx: it was pointing at needing one of the more sophisticated implementations21:46
ttxhmm, ok, we need to clear the floor21:46
lifelessttx: sorry that that was unclear21:46
ttxlifeless: how about you propose a solution there ?21:47
lifelesssure21:47
lifelessI think I have a handle on whats needed21:47
ttxOK, we have a next step. Great21:47
fungiyeah, if updates to the release notes file drive releases, then that conflicts with one tag per commit anyway21:47
jokke_ttx: go on, we will be discussing this again in Tokyo :)21:47
johnthetubaguyDaviey: people forget that stuff really easily21:47
lifelessI will do so by replying to the thread21:47
DavieyIndeed.21:47
ttxWe need that completed for Liberty release, so there is a time constraint21:47
lifelessI don't think that a single release notes change should trigger a tag21:47
ttxEmilienM: I think you can switch to next topic21:47
EmilienMcool21:47
Davieywait..21:48
ttxsorry we kinda overran21:48
DavieyAction?21:48
EmilienM#topic Return request ID to caller21:48
*** openstack changes topic to "Return request ID to caller (Meeting topic: crossproject)"21:48
*** mriedem has quit IRC21:48
EmilienM#link https://review.openstack.org/15650821:48
EmilienMtpatil: hello21:48
tpatilWe have updated the specs to include work item to mark openstack python package as private in python-*clients as decided in the last meeting21:48
ttx#action lifeless to document an in-tree solution without merge conflicts21:48
*** Piet has quit IRC21:48
tpatilRequest everyone to please review the specs and give your valuable feedback21:48
*** aimon has quit IRC21:48
tpatilThat's all I wanted to update here21:49
*** zul has quit IRC21:49
EmilienMtpatil: thank you21:50
*** tiswanso has joined #openstack-meeting21:50
EmilienMwe have time for open discussion then21:50
*** pnavarro has quit IRC21:50
EmilienMexcept if there is more to talk about the current topic21:50
ttxI guess we can spam it with extra questions on the stable point release stuff21:50
EmilienM#topic Open Discussion21:51
*** openstack changes topic to "Open Discussion (Meeting topic: crossproject)"21:51
EmilienMttx: spam enabled21:51
*** neiljerram_bb has quit IRC21:51
johnthetubaguythe two actions we spoke about looked promising, with my optimistic hat on21:51
ttxlifeless: one drawback of the in-tree solution is that it prevents straight backports, but I guess that's a lesser evil than writing hundreds of line of Java and relying on git notes21:52
EmilienMI have a question - do we usually take care of actions in the following meetings? like "review past actions items"21:52
*** rbowen has joined #openstack-meeting21:52
EmilienMif not, I would like to bring it in the next meeting21:52
*** carl_baldwin has quit IRC21:52
ttxEmilienM: we don't, but we probably should21:52
*** penick_ has quit IRC21:52
ttxWe used to :)21:52
*** rbowen has quit IRC21:52
EmilienMwe will then :)21:52
bknudsoneverything is less evil than hundreds of lines of java.21:53
*** asettle has joined #openstack-meeting21:53
elmikolol21:53
*** puranamr has quit IRC21:53
EmilienMif there is nothing else to talk about, I'll let ttx go to bed and close the meeting, otherwise rise your hand21:53
ttxEmilienM: the trick is people attend this meeting based on the agenda... and so most of the time the ACTIONed people are not around the next time21:53
*** jecarey has quit IRC21:53
ttxwhen it was the allhands meeting it was easier21:53
*** emagana has quit IRC21:54
EmilienM:)21:54
EmilienMI think I can close it21:54
EmilienMthanks everyone and see you next week21:54
ttxI think you can21:54
EmilienMttx: good night21:54
EmilienM#endmeeting21:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:54
openstackMeeting ended Tue Aug 18 21:54:27 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-08-18-21.01.html21:54
Davieythanks EmilienM21:54
ttxThanks EmilienM for driving it!21:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-08-18-21.01.txt21:54
elmikothanks EmilienM21:54
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-08-18-21.01.log.html21:54
*** AmirBaleghi1112 has quit IRC21:54
*** JRobinson__ has joined #openstack-meeting21:54
*** elmiko has left #openstack-meeting21:55
*** PrashantS has joined #openstack-meeting21:55
*** garthb has quit IRC21:55
*** sahid has quit IRC21:55
jokke_thanks21:56
*** hrou has joined #openstack-meeting21:57
*** dannywil_ has joined #openstack-meeting21:57
*** dannywil_ has quit IRC21:58
*** dannywil_ has joined #openstack-meeting21:58
*** xarses has left #openstack-meeting21:58
*** gordc has left #openstack-meeting21:59
*** matrohon has quit IRC22:00
*** dannywilson has quit IRC22:01
*** absubram has quit IRC22:01
*** dprince has quit IRC22:02
*** dannywil_ has quit IRC22:02
*** garthb has joined #openstack-meeting22:03
*** garthb has quit IRC22:03
*** garthb has joined #openstack-meeting22:03
*** tiswanso has quit IRC22:03
*** tpatil has quit IRC22:04
*** padkrish has quit IRC22:04
*** jungleboyj has quit IRC22:05
*** padkrish has joined #openstack-meeting22:05
*** tiswanso has joined #openstack-meeting22:05
*** shashank_hegde has joined #openstack-meeting22:05
*** gyee has quit IRC22:06
*** andreykurilin__ has joined #openstack-meeting22:08
*** vivek-ebay has joined #openstack-meeting22:09
*** padkrish has quit IRC22:09
*** tiswanso has quit IRC22:10
*** amotoki has joined #openstack-meeting22:10
*** rbak has joined #openstack-meeting22:10
*** vijendar has quit IRC22:11
*** dane_leblanc_ has quit IRC22:13
*** harshs has joined #openstack-meeting22:13
*** angdraug has quit IRC22:14
*** amotoki has quit IRC22:15
*** yottatsa has quit IRC22:15
*** glauco_ has quit IRC22:17
*** annegentle has quit IRC22:17
*** sigmavirus24 is now known as sigmavirus24_awa22:18
*** aimon has joined #openstack-meeting22:19
*** padkrish has joined #openstack-meeting22:20
*** rbak has quit IRC22:22
*** bswartz has joined #openstack-meeting22:22
*** pradk has quit IRC22:24
*** rbak has joined #openstack-meeting22:24
*** dflorea has joined #openstack-meeting22:29
*** ivar-lazzaro has quit IRC22:30
*** jeadr has quit IRC22:30
*** shashank_hegde has quit IRC22:31
*** jeadr has joined #openstack-meeting22:31
*** shashank_hegde has joined #openstack-meeting22:33
*** neillc_away is now known as neillc22:33
*** elo1 has quit IRC22:34
*** geoffarnold has joined #openstack-meeting22:35
*** puranamr has joined #openstack-meeting22:35
*** emagana has joined #openstack-meeting22:35
*** novas0x2a|laptop has quit IRC22:36
*** novas0x2a|lapto1 has joined #openstack-meeting22:36
*** henrynash has quit IRC22:37
*** elo1 has joined #openstack-meeting22:37
*** adahms has joined #openstack-meeting22:39
*** Piet has joined #openstack-meeting22:39
*** darrenc is now known as darrenc_afk22:40
*** Piet has quit IRC22:42
*** Piet has joined #openstack-meeting22:44
*** Piet has quit IRC22:46
*** VW_ has joined #openstack-meeting22:46
*** MeganR has joined #openstack-meeting22:47
*** cbader has joined #openstack-meeting22:47
*** eharney has quit IRC22:47
*** penick has joined #openstack-meeting22:48
*** baoli has joined #openstack-meeting22:49
*** padkrish has quit IRC22:49
*** padkrish has joined #openstack-meeting22:50
*** PrashantS has quit IRC22:51
*** novas0x2a|lapto1 has quit IRC22:51
*** PrashantS has joined #openstack-meeting22:52
*** cbader has quit IRC22:53
*** baoli has quit IRC22:53
*** novas0x2a|laptop has joined #openstack-meeting22:53
*** VW_ has quit IRC22:53
*** VW_ has joined #openstack-meeting22:54
*** padkrish has quit IRC22:54
*** jungleboyj has joined #openstack-meeting22:56
*** emagana has quit IRC22:56
*** asettle is now known as asettle-afk22:56
*** PrashantS has quit IRC22:56
*** darrenc_afk is now known as darrenc22:56
*** VW_ has quit IRC22:59
*** dane_leblanc has joined #openstack-meeting22:59
*** dflorea has quit IRC23:00
*** VW_ has joined #openstack-meeting23:00
*** padkrish has joined #openstack-meeting23:00
*** emagana has joined #openstack-meeting23:01
*** dflorea has joined #openstack-meeting23:01
*** dane_leblanc has quit IRC23:01
*** dane_leblanc has joined #openstack-meeting23:01
*** dane_leblanc_ has joined #openstack-meeting23:02
*** cbader has joined #openstack-meeting23:02
*** VW_ has quit IRC23:05
*** VW_ has joined #openstack-meeting23:05
*** dane_leblanc has quit IRC23:06
*** VW_ has quit IRC23:06
*** VW_ has joined #openstack-meeting23:06
*** pm90__ has quit IRC23:06
*** tiswanso has joined #openstack-meeting23:06
*** pm90_ has joined #openstack-meeting23:06
*** geoffarnold has quit IRC23:07
*** padkrish has quit IRC23:07
*** VW__ has joined #openstack-meeting23:07
*** VW_ has quit IRC23:07
*** padkrish has joined #openstack-meeting23:07
*** VW__ has quit IRC23:08
*** shashank_hegde has quit IRC23:08
*** annegentle has joined #openstack-meeting23:08
*** VW_ has joined #openstack-meeting23:08
*** annegentle has quit IRC23:09
*** penick_ has joined #openstack-meeting23:09
*** penick has quit IRC23:09
*** penick_ is now known as penick23:09
*** annegentle has joined #openstack-meeting23:10
*** shashank_hegde has joined #openstack-meeting23:10
*** dannywilson has joined #openstack-meeting23:10
*** smccully has quit IRC23:11
*** harshs has quit IRC23:11
*** amotoki has joined #openstack-meeting23:11
*** padkrish_ has joined #openstack-meeting23:11
*** padkrish has quit IRC23:11
*** dflorea has quit IRC23:13
*** gyee has joined #openstack-meeting23:15
*** puranamr has quit IRC23:16
*** amotoki has quit IRC23:16
*** emagana has quit IRC23:16
*** PrashantS has joined #openstack-meeting23:17
*** rbak has quit IRC23:17
*** glauco_ has joined #openstack-meeting23:17
*** tiswanso has quit IRC23:18
*** ebalduf has quit IRC23:18
*** dims_ has joined #openstack-meeting23:20
*** banix has joined #openstack-meeting23:21
*** achanda has quit IRC23:22
*** dims has quit IRC23:22
*** VW_ has quit IRC23:23
*** britthouser has joined #openstack-meeting23:24
*** geoffarnold has joined #openstack-meeting23:24
*** VW_ has joined #openstack-meeting23:24
*** pballand has joined #openstack-meeting23:24
*** glauco_ has quit IRC23:24
*** rbak has joined #openstack-meeting23:25
*** britthou_ has joined #openstack-meeting23:25
*** pballand has quit IRC23:25
*** asettle-afk has quit IRC23:26
*** VW__ has joined #openstack-meeting23:27
*** dannywilson has quit IRC23:28
*** VW_ has quit IRC23:28
*** rbak has quit IRC23:28
*** cbader has quit IRC23:28
*** VW__ has quit IRC23:28
*** britthouser has quit IRC23:28
*** VW_ has joined #openstack-meeting23:29
*** achanda has joined #openstack-meeting23:30
*** achanda has quit IRC23:30
*** achanda has joined #openstack-meeting23:31
*** rjaiswal has joined #openstack-meeting23:31
*** changbl has joined #openstack-meeting23:31
*** xingchao has joined #openstack-meeting23:32
*** otter768 has joined #openstack-meeting23:33
*** puranamr has joined #openstack-meeting23:35
*** jeadr has quit IRC23:37
*** tochi has joined #openstack-meeting23:38
*** otter768 has quit IRC23:38
*** rbak has joined #openstack-meeting23:40
*** rbak has quit IRC23:42
*** padkrish_ has quit IRC23:42
*** padkrish has joined #openstack-meeting23:43
*** jeadr has joined #openstack-meeting23:43
*** toscalix has quit IRC23:44
*** jeadr has quit IRC23:46
*** padkrish has quit IRC23:47
*** jeadr has joined #openstack-meeting23:48
*** geoffarnold has quit IRC23:49
*** rbak has joined #openstack-meeting23:49
*** xingchao has quit IRC23:49
*** geoffarnold has joined #openstack-meeting23:49
*** ndipanov has joined #openstack-meeting23:50
*** shashank_hegde has quit IRC23:51
*** ndipanov has quit IRC23:52
*** ndipanov has joined #openstack-meeting23:52
*** elo1 has quit IRC23:54
*** britthou_ has quit IRC23:56
*** SumitNaiksatam has quit IRC23:56
*** ndipanov has quit IRC23:59

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