Tuesday, 2015-06-30

*** dannywilson has quit IRC00:00
*** pgbridge has quit IRC00:01
*** DericHorn-HP has quit IRC00:01
*** dannywil_ has quit IRC00:01
*** docaedo has quit IRC00:02
*** Longgeek has quit IRC00:03
*** amitgandhinz has joined #openstack-meeting00:03
*** dwalleck has quit IRC00:03
*** Rockyg has quit IRC00:05
*** docaedo has joined #openstack-meeting00:05
*** sdake has quit IRC00:07
*** galstrom is now known as galstrom_zzz00:07
*** fallenpegasus has joined #openstack-meeting00:07
*** amitgandhinz has quit IRC00:07
*** jhenner has quit IRC00:08
*** arvinchou_ has quit IRC00:08
*** dims has joined #openstack-meeting00:12
*** tsekiyam_ has joined #openstack-meeting00:13
*** harshs has joined #openstack-meeting00:14
*** mtanino has quit IRC00:16
*** tsekiyama has quit IRC00:17
*** carl_baldwin has quit IRC00:18
*** marun has joined #openstack-meeting00:18
*** tsekiyam_ has quit IRC00:18
*** aimon has joined #openstack-meeting00:19
*** claudiub has joined #openstack-meeting00:21
*** amotoki has joined #openstack-meeting00:27
*** ildikov_ has quit IRC00:28
*** topol has quit IRC00:28
*** xingchao_ has joined #openstack-meeting00:29
*** xingchao_ has quit IRC00:30
*** boris-42 has joined #openstack-meeting00:30
*** dmacpher-afk has quit IRC00:31
*** yamamoto has joined #openstack-meeting00:31
*** darrenc is now known as darrenc_afk00:31
*** topol has joined #openstack-meeting00:32
*** geoffarnold has quit IRC00:32
*** ddieterly has joined #openstack-meeting00:33
*** marun_ has joined #openstack-meeting00:40
*** leeantho has quit IRC00:40
*** ildikov_ has joined #openstack-meeting00:41
*** marun has quit IRC00:41
*** gibi_ has quit IRC00:42
*** darrenc_afk is now known as darrenc00:44
*** fallenpegasus has quit IRC00:45
*** sankarshan_away is now known as sankarshan00:47
*** gmann has quit IRC00:48
*** larainema has joined #openstack-meeting00:54
*** galstrom_zzz is now known as galstrom00:55
*** ayoung has joined #openstack-meeting00:58
*** pvaneck has quit IRC00:59
*** yamamoto has quit IRC00:59
*** gmann has joined #openstack-meeting01:00
*** marun_ has quit IRC01:01
*** annegentle has joined #openstack-meeting01:02
*** otter768 has joined #openstack-meeting01:03
*** gibi has joined #openstack-meeting01:04
*** henrynash_ has joined #openstack-meeting01:05
*** annegentle has quit IRC01:06
*** otter768 has quit IRC01:07
*** henrynash has quit IRC01:08
*** henrynash_ is now known as henrynash01:08
*** ildikov_ has quit IRC01:11
*** sigmavirus24 is now known as sigmavirus24_awa01:13
*** maxdml has quit IRC01:15
*** galstrom is now known as galstrom_zzz01:18
*** dmacpher has joined #openstack-meeting01:19
*** markvoelker has quit IRC01:19
*** ivar-laz_ has joined #openstack-meeting01:19
*** markvoelker has joined #openstack-meeting01:19
*** banix has quit IRC01:21
*** markvoelker has quit IRC01:22
*** banix has joined #openstack-meeting01:22
*** ivar-lazzaro has quit IRC01:22
*** novas0x2a|laptop has quit IRC01:22
*** arvinchou_ has joined #openstack-meeting01:23
*** markvoelker has joined #openstack-meeting01:23
*** markvoelker has quit IRC01:23
*** ivar-laz_ has quit IRC01:23
*** markvoelker has joined #openstack-meeting01:24
*** DericHorn-HP has joined #openstack-meeting01:24
*** enikanorov2 has quit IRC01:24
*** harshs has quit IRC01:27
*** otter768 has joined #openstack-meeting01:27
*** echoingumesh has joined #openstack-meeting01:27
*** echoingu_ has joined #openstack-meeting01:29
*** arvinchou_ has quit IRC01:30
*** jasondotstar has quit IRC01:30
*** arvinchou_ has joined #openstack-meeting01:30
*** echoingumesh has quit IRC01:32
*** Sukhdev has quit IRC01:34
*** tobe has joined #openstack-meeting01:38
*** tobe has quit IRC01:39
*** hrou has joined #openstack-meeting01:40
*** enikanorov2 has joined #openstack-meeting01:42
*** yamahata has quit IRC01:43
*** aranjan has quit IRC01:46
*** arvinchou_ has quit IRC01:49
*** Apoorva has quit IRC01:50
*** yamamoto has joined #openstack-meeting01:52
*** xingchao_ has joined #openstack-meeting01:53
*** dmacpher has quit IRC01:53
*** gyee has quit IRC01:53
*** dmacpher has joined #openstack-meeting01:54
*** otter768 has quit IRC01:55
*** xingchao_ has quit IRC01:56
*** JRobinson__ is now known as JRobinson__afk01:57
*** jasondotstar has joined #openstack-meeting01:59
*** Yanyanhu has joined #openstack-meeting01:59
*** jasondotstar has quit IRC02:00
*** banix has quit IRC02:00
*** jasondotstar has joined #openstack-meeting02:00
*** ijw has quit IRC02:02
*** galstrom_zzz is now known as galstrom02:02
*** topol has quit IRC02:04
*** s3wong has quit IRC02:04
*** topol has joined #openstack-meeting02:04
*** sigmavirus24_awa is now known as sigmavirus2402:05
*** vivek-eb_ has joined #openstack-meeting02:06
*** jasondotstar has quit IRC02:06
*** echoingu_ has quit IRC02:06
*** jasondotstar has joined #openstack-meeting02:06
*** echoingumesh has joined #openstack-meeting02:07
*** dmacpher_ has joined #openstack-meeting02:07
*** ayoung has quit IRC02:07
*** vivek-ebay has quit IRC02:08
*** ayoung has joined #openstack-meeting02:09
*** dmacpher__ has joined #openstack-meeting02:09
*** dmacpher has quit IRC02:09
*** ianw has quit IRC02:09
*** vivek-eb_ has quit IRC02:10
*** ianw has joined #openstack-meeting02:10
*** echoingumesh has quit IRC02:11
*** galstrom is now known as galstrom_zzz02:11
*** harshs has joined #openstack-meeting02:12
*** dmacpher_ has quit IRC02:13
*** tobe has joined #openstack-meeting02:16
*** weshay has quit IRC02:17
*** unicell has quit IRC02:19
*** banix has joined #openstack-meeting02:19
*** kylek3h has joined #openstack-meeting02:26
*** aorourke has quit IRC02:28
*** hemna has quit IRC02:28
*** asselin has quit IRC02:28
*** aorourke has joined #openstack-meeting02:29
*** dmacpher has joined #openstack-meeting02:29
*** hemna has joined #openstack-meeting02:29
*** ianw has quit IRC02:29
*** asselin has joined #openstack-meeting02:29
*** dmacpher__ has quit IRC02:30
*** dmacpher_ has joined #openstack-meeting02:30
*** baoli has joined #openstack-meeting02:31
*** JRobinson__afk has quit IRC02:33
*** puranamr has quit IRC02:33
*** dmacpher has quit IRC02:34
*** finchd has quit IRC02:34
*** stevemar has joined #openstack-meeting02:35
*** KunalGan_ has joined #openstack-meeting02:35
*** finchd_ has joined #openstack-meeting02:36
*** finchd has joined #openstack-meeting02:36
*** rossella_s has quit IRC02:36
*** rossella_s has joined #openstack-meeting02:37
*** KunalGandhi has quit IRC02:39
*** balajiiyer has joined #openstack-meeting02:39
*** KunalGan_ has quit IRC02:40
*** balajiiyer has quit IRC02:40
*** balajiiyer has joined #openstack-meeting02:41
*** carl_baldwin has joined #openstack-meeting02:42
*** echoingumesh has joined #openstack-meeting02:42
*** echoingumesh has quit IRC02:43
*** echoingumesh has joined #openstack-meeting02:43
*** finchd has quit IRC02:44
*** finchd has joined #openstack-meeting02:44
*** finchd_ has quit IRC02:46
*** fbo_ has quit IRC02:48
*** epico has joined #openstack-meeting02:48
*** echoingumesh has quit IRC02:48
*** sajeesh has quit IRC02:49
*** mmedvede has quit IRC02:50
*** kebray has joined #openstack-meeting02:51
*** fbo has joined #openstack-meeting02:51
*** Longgeek has joined #openstack-meeting03:00
*** sankarshan is now known as sankarshan_away03:01
*** sankarshan_away is now known as sankarshan03:04
*** Longgeek has quit IRC03:05
*** kevinbenton has joined #openstack-meeting03:08
*** banix has quit IRC03:11
*** banix has joined #openstack-meeting03:13
*** flashgordon has quit IRC03:13
*** banix has quit IRC03:15
*** claudiub has quit IRC03:15
*** baoli has quit IRC03:18
*** carl_baldwin has quit IRC03:24
*** kylek3h has quit IRC03:25
*** masayukig has quit IRC03:31
*** markvoelker has quit IRC03:31
*** JRobinson__afk has joined #openstack-meeting03:33
*** yamada-h has joined #openstack-meeting03:35
*** bill_az has quit IRC03:36
*** masayukig has joined #openstack-meeting03:36
*** Longgeek has joined #openstack-meeting03:37
*** vivek-ebay has joined #openstack-meeting03:38
*** yamada-h has quit IRC03:40
*** asettle is now known as asettle-afk03:40
*** yamahata has joined #openstack-meeting03:41
*** fallenpegasus has joined #openstack-meeting03:41
*** vivek-ebay has quit IRC03:42
*** vivek-ebay has joined #openstack-meeting03:43
*** ddieterly has quit IRC03:43
*** rjaiswal has quit IRC03:44
*** jasondotstar has quit IRC03:47
*** Apoorva has joined #openstack-meeting03:47
*** dims has quit IRC03:48
*** ganeshna has joined #openstack-meeting03:50
*** JRobinson__afk is now known as JRobinson__03:50
*** carl_baldwin has joined #openstack-meeting03:52
*** banix has joined #openstack-meeting03:52
*** sarob has quit IRC03:54
*** kebray has quit IRC03:56
*** otter768 has joined #openstack-meeting03:56
*** lazy_prince has joined #openstack-meeting03:59
*** ganeshna has quit IRC04:00
*** otter768 has quit IRC04:01
*** Longgeek has quit IRC04:05
*** Longgeek has joined #openstack-meeting04:06
*** banix has quit IRC04:06
*** coolsvap|away is now known as coolsvap04:08
*** sdake has joined #openstack-meeting04:09
*** sdake_ has joined #openstack-meeting04:10
*** unicell has joined #openstack-meeting04:12
*** harshs has quit IRC04:12
*** david-lyle has quit IRC04:13
*** achanda has joined #openstack-meeting04:13
*** sdake has quit IRC04:13
*** yatin has joined #openstack-meeting04:13
*** david-lyle has joined #openstack-meeting04:14
*** zz_jgrimm has quit IRC04:15
*** KunalGandhi has joined #openstack-meeting04:15
*** timello has quit IRC04:15
*** maurosr has quit IRC04:15
*** balajiiyer has quit IRC04:15
*** carl_baldwin has quit IRC04:16
*** asselin_ has joined #openstack-meeting04:17
*** carl_baldwin has joined #openstack-meeting04:17
*** hrou has quit IRC04:17
*** mdenny has quit IRC04:19
*** kmartin_ has joined #openstack-meeting04:19
*** kmartin has quit IRC04:19
*** mdenny has joined #openstack-meeting04:19
*** numan has joined #openstack-meeting04:21
*** KunalGandhi has quit IRC04:21
*** unicell1 has joined #openstack-meeting04:22
*** KunalGandhi has joined #openstack-meeting04:23
*** unicell has quit IRC04:23
*** timello has joined #openstack-meeting04:24
*** sdake has joined #openstack-meeting04:25
*** zz_jgrimm has joined #openstack-meeting04:26
*** maurosr has joined #openstack-meeting04:27
*** DericHorn-HP has quit IRC04:28
*** sdake_ has quit IRC04:29
*** achanda has quit IRC04:30
*** tobe has quit IRC04:31
*** hogepodge has quit IRC04:32
*** markvoelker has joined #openstack-meeting04:32
*** tobe has joined #openstack-meeting04:32
*** hogepodge has joined #openstack-meeting04:32
*** ijw__ has joined #openstack-meeting04:33
*** topol has quit IRC04:34
*** padkrish has joined #openstack-meeting04:35
*** padkrish has quit IRC04:35
*** DericHorn-HP has joined #openstack-meeting04:35
*** maishsk has quit IRC04:35
*** padkrish has joined #openstack-meeting04:36
*** yamada-h has joined #openstack-meeting04:36
*** markvoelker has quit IRC04:36
*** ijw_ has joined #openstack-meeting04:37
*** maishsk has joined #openstack-meeting04:37
*** sigmavirus24 is now known as sigmavirus24_awa04:39
*** timello has quit IRC04:39
*** zz_jgrimm has quit IRC04:39
*** irenab has quit IRC04:40
*** maurosr has quit IRC04:40
*** ijw__ has quit IRC04:40
*** yamada-h has quit IRC04:41
*** zz_jgrimm has joined #openstack-meeting04:42
*** maurosr has joined #openstack-meeting04:42
*** timello has joined #openstack-meeting04:42
*** ddieterly has joined #openstack-meeting04:44
*** maishsk has quit IRC04:47
*** ijw_ has quit IRC04:47
*** ddieterly has quit IRC04:49
*** amotoki_ has joined #openstack-meeting04:49
*** arnaud____ has joined #openstack-meeting04:50
*** carl_baldwin has quit IRC04:51
*** padkrish has quit IRC04:51
*** padkrish has joined #openstack-meeting04:52
*** harshs has joined #openstack-meeting04:52
*** arnaud____ has quit IRC04:54
*** DericHorn-HP has quit IRC04:58
*** sdake_ has joined #openstack-meeting04:59
*** arnaud____ has joined #openstack-meeting05:00
*** erlon has quit IRC05:00
*** rbak has joined #openstack-meeting05:01
*** balajiiyer has joined #openstack-meeting05:01
*** harshs has quit IRC05:01
*** sdake has quit IRC05:03
*** fallenpegasus has quit IRC05:03
*** stevemar has quit IRC05:05
*** stevemar has joined #openstack-meeting05:06
*** fallenpegasus has joined #openstack-meeting05:07
*** Apoorva has quit IRC05:08
*** pgbridge has joined #openstack-meeting05:14
*** lpeer__ has joined #openstack-meeting05:15
*** rbak has quit IRC05:15
*** fawadkhaliq has joined #openstack-meeting05:18
*** ijw_ has joined #openstack-meeting05:18
*** pgbridge has quit IRC05:20
*** ildikov has joined #openstack-meeting05:22
*** fallenpegasus has quit IRC05:23
*** amotoki__ has joined #openstack-meeting05:24
*** amotoki_ has quit IRC05:24
*** fallenpegasus has joined #openstack-meeting05:27
*** padkrish has quit IRC05:27
*** padkrish has joined #openstack-meeting05:27
*** Sukhdev has joined #openstack-meeting05:28
*** dmacpher_ has quit IRC05:29
*** adahms has joined #openstack-meeting05:30
*** arnaud____ has quit IRC05:31
*** yatin has quit IRC05:33
*** ijw_ has quit IRC05:38
*** BharatK has joined #openstack-meeting05:39
*** ajayaa has joined #openstack-meeting05:39
*** asettle has joined #openstack-meeting05:42
*** hogepodge has quit IRC05:42
*** hogepodge has joined #openstack-meeting05:42
*** ddieterly has joined #openstack-meeting05:45
*** topol has joined #openstack-meeting05:46
*** achanda has joined #openstack-meeting05:48
*** ddieterly has quit IRC05:50
*** rjaiswal has joined #openstack-meeting05:50
*** padkrish has quit IRC05:53
*** moha_hunt has quit IRC05:53
*** Murali has joined #openstack-meeting05:53
*** radek_ has joined #openstack-meeting05:53
*** yamamoto has quit IRC05:55
*** fallenpegasus has quit IRC05:55
*** markvoelker has joined #openstack-meeting05:56
*** lpeer__ has quit IRC05:56
*** lpeer__ has joined #openstack-meeting05:57
*** SridharG has joined #openstack-meeting05:57
*** otter768 has joined #openstack-meeting05:57
*** topol has quit IRC05:57
*** yamamoto has joined #openstack-meeting05:58
*** lpeer has joined #openstack-meeting06:00
*** barrett1 has quit IRC06:00
*** markvoelker has quit IRC06:01
*** otter768 has quit IRC06:02
*** lpeer__ has quit IRC06:03
*** adahms has quit IRC06:04
*** achanda has quit IRC06:04
*** dmacpher has joined #openstack-meeting06:05
*** fallenpegasus has joined #openstack-meeting06:05
*** stevemar has quit IRC06:05
*** ub has joined #openstack-meeting06:06
*** stevemar has joined #openstack-meeting06:06
*** arnaud____ has joined #openstack-meeting06:06
*** irenab has joined #openstack-meeting06:07
*** Sukhdev_ has joined #openstack-meeting06:08
*** stevemar has quit IRC06:09
*** JRobinson__ has quit IRC06:10
*** Sukhdev has quit IRC06:11
*** echoingumesh has joined #openstack-meeting06:15
*** SridharGaddam has joined #openstack-meeting06:16
*** vivek-ebay has quit IRC06:17
*** larainema has quit IRC06:17
*** maishsk_afk has joined #openstack-meeting06:17
*** maishsk_afk is now known as maishsk06:17
*** KunalGandhi has quit IRC06:19
*** _nadya_ has joined #openstack-meeting06:23
*** niclem has quit IRC06:23
*** achanda has joined #openstack-meeting06:26
*** dmacpher has quit IRC06:28
*** sdake_ has quit IRC06:29
*** elo1 has joined #openstack-meeting06:30
*** mpaolino has joined #openstack-meeting06:30
*** lsmola has joined #openstack-meeting06:33
*** scheuran has joined #openstack-meeting06:33
*** elo has quit IRC06:33
*** ajayaa_ has joined #openstack-meeting06:34
*** ajayaa has quit IRC06:34
*** AzherKhan has joined #openstack-meeting06:36
*** rossella_s has quit IRC06:36
*** rossella_s has joined #openstack-meeting06:37
*** elo1 has quit IRC06:38
*** asettle has quit IRC06:39
*** ddieterly has joined #openstack-meeting06:46
*** Sukhdev_ has quit IRC06:47
*** elo has joined #openstack-meeting06:48
*** mrunge has joined #openstack-meeting06:48
*** mrunge has quit IRC06:48
*** mrunge has joined #openstack-meeting06:48
*** BharatK has quit IRC06:49
*** ddieterly has quit IRC06:51
*** belmoreira has joined #openstack-meeting06:52
*** devvesa has joined #openstack-meeting06:53
*** doude has joined #openstack-meeting06:53
*** niclem has joined #openstack-meeting06:54
*** neeti has joined #openstack-meeting06:58
*** fallenpegasus has quit IRC07:01
*** arnaud____ has quit IRC07:01
*** boris-42 has quit IRC07:02
*** dguerri` is now known as dguerri07:02
*** achanda has quit IRC07:03
*** BharatK has joined #openstack-meeting07:03
*** dguerri is now known as dguerri`07:07
*** zz_ttrifonov is now known as ttrifonov07:10
*** comay has quit IRC07:11
*** hichihara has quit IRC07:17
*** jehb has quit IRC07:17
*** kaisers1 has joined #openstack-meeting07:19
*** ijw_ has joined #openstack-meeting07:22
*** phil_ has joined #openstack-meeting07:22
*** dkusidlo has joined #openstack-meeting07:22
*** balajiiyer has left #openstack-meeting07:22
*** zhhuabj_ has quit IRC07:23
*** ijw__ has joined #openstack-meeting07:24
*** zhhuabj_ has joined #openstack-meeting07:24
*** xingchao_ has joined #openstack-meeting07:26
*** ijw_ has quit IRC07:27
*** linuxmohan has joined #openstack-meeting07:28
*** ijw__ has quit IRC07:29
*** ijw_ has joined #openstack-meeting07:29
*** kaisers1 has quit IRC07:29
*** kaisers1 has joined #openstack-meeting07:29
*** irenab has quit IRC07:30
*** matrohon has joined #openstack-meeting07:30
*** britthou_ has quit IRC07:30
*** irenab has joined #openstack-meeting07:30
*** britthouser has joined #openstack-meeting07:30
*** gema has left #openstack-meeting07:30
*** subscope has quit IRC07:31
*** echoingumesh has quit IRC07:32
*** echoingumesh has joined #openstack-meeting07:32
*** dkusidlo has quit IRC07:33
*** e0ne has joined #openstack-meeting07:33
*** echoingumesh has quit IRC07:37
*** jlanoux has joined #openstack-meeting07:37
*** e0ne has quit IRC07:37
*** sahid has quit IRC07:38
*** sahid has joined #openstack-meeting07:39
*** hashar has joined #openstack-meeting07:41
*** ndipanov has quit IRC07:42
*** ndipanov has joined #openstack-meeting07:44
*** markvoelker has joined #openstack-meeting07:45
*** jtomasek has joined #openstack-meeting07:46
*** ddieterly has joined #openstack-meeting07:47
*** subscope has joined #openstack-meeting07:47
*** mrunge has quit IRC07:48
*** elo has quit IRC07:48
*** armax has quit IRC07:48
*** markvoelker has quit IRC07:50
*** enikanorov2_ has joined #openstack-meeting07:50
*** amotoki__ has quit IRC07:50
*** mrmartin has joined #openstack-meeting07:50
*** britthouser has quit IRC07:51
*** ddieterly has quit IRC07:51
*** yamahata has quit IRC07:52
*** enikanorov2 has quit IRC07:52
*** safchain has joined #openstack-meeting07:54
*** sdake_ has joined #openstack-meeting07:55
*** subscope has quit IRC07:55
*** otter768 has joined #openstack-meeting07:58
*** vivek-ebay has joined #openstack-meeting07:58
anteaya#startmeeting third-party08:01
openstackMeeting started Tue Jun 30 08:01:06 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: third-party)"08:01
openstackThe meeting name has been set to 'third_party'08:01
anteayasay hello if you are here for the third party meeting08:01
anteayahi lennyb08:01
anteayahow is your system today?08:01
* lennyb writing08:02
lennybwe are currently in silent mode, due to changed in sriov that broke us.08:02
*** claudiub has joined #openstack-meeting08:02
*** otter768 has quit IRC08:02
anteayahow are you doing finding a fix?08:03
*** vivek-ebay has quit IRC08:03
lennybthe fix was already merged, so I am verifying that it works and we will comment ( non voting ) again in Nova08:03
lennybwe are in Silent mode in neutron as discussed in Summit08:03
anteayaand this is in line with what nova devs expect of you?08:03
anteayayou met jogo at summit but he is no longer working full time on openstack08:04
anteayaare there other people in nova you talk to?08:04
lennybno, I stopped our CI from commenting, once we saw failures, I dont want to 'spam' :) once it is fixed and verified we will be back again08:05
anteayagood thing you stopped your system from commenting08:06
lennybyou know..... we caused a lot of mess and discussing :)08:06
anteayagood idea to avoid the mess this time08:07
anteayahello eantyshev08:07
anteayadid you make any progress on the looping issue at all?08:07
*** stevemar has joined #openstack-meeting08:07
eantyshevonly that I made a story for it: https://storyboard.openstack.org/#!/story/200030908:08
anteayathank you08:08
eantyshevwill continue on it in background08:09
anteayathanks so much08:09
anteaya#link https://storyboard.openstack.org/#!/story/200030908:09
anteayaeantyshev: perhaps you can find patrickeast and share the link with him08:09
anteayadid you have anything new you wanted to discuss?08:09
anteayaI'm not feeling great08:09
anteayaand am hoping for a short meeting08:09
anteayaunless you have something pressing you would like to talk about08:10
lennybanteaya: not me. feel well.08:10
anteayalennyb: thanks08:10
anteayaeantyshev: any thoughts?08:10
*** xingchao_ has quit IRC08:10
*** stevemar has quit IRC08:10
eantyshevanteaya: sure, not me too08:10
anteayaokay thanks08:10
anteayaI appreciate you being here08:10
anteayabut I do need to sign off and feel better08:11
anteayaand see you next week08:11
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:11
openstackMeeting ended Tue Jun 30 08:11:13 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-06-30-08.01.html08:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-06-30-08.01.txt08:11
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-06-30-08.01.log.html08:11
*** subscope has joined #openstack-meeting08:11
*** ygbo has joined #openstack-meeting08:16
*** pelix has joined #openstack-meeting08:16
*** tobe has quit IRC08:17
*** derekh has joined #openstack-meeting08:22
*** subscope has quit IRC08:24
*** niclem_ has joined #openstack-meeting08:26
*** niclem has quit IRC08:27
*** yamamoto has quit IRC08:27
*** MeganR has quit IRC08:28
*** isviridov_away is now known as isviridov08:29
*** MeganR has joined #openstack-meeting08:29
*** yassine_ has joined #openstack-meeting08:34
*** jhenner has joined #openstack-meeting08:37
*** subscope has joined #openstack-meeting08:38
*** alex_xu_ is now known as alex_xu08:38
*** yamada-h has joined #openstack-meeting08:39
*** dguitarbite has joined #openstack-meeting08:42
*** mrunge has joined #openstack-meeting08:43
*** yamada-h has quit IRC08:44
*** sdake_ has quit IRC08:45
*** yamamoto has joined #openstack-meeting08:47
*** ddieterly has joined #openstack-meeting08:47
-openstackstatus- NOTICE: OpenStack CI is down due to hard drive failures08:48
*** ChanServ changes topic to "OpenStack CI is down due to hard drive failures"08:48
*** eantyshev has left #openstack-meeting08:51
*** ddieterly has quit IRC08:52
*** ijw__ has joined #openstack-meeting08:53
*** rjaiswal has quit IRC08:54
*** toscalix has joined #openstack-meeting08:54
*** bradjones has quit IRC08:55
*** ijw_ has quit IRC08:57
*** bradjones has joined #openstack-meeting08:57
*** bradjones has quit IRC08:57
*** bradjones has joined #openstack-meeting08:57
*** _nadya_ has quit IRC09:00
*** _nadya_ has joined #openstack-meeting09:00
*** Gerald_K has joined #openstack-meeting09:01
*** e0ne has joined #openstack-meeting09:02
*** lufix has joined #openstack-meeting09:03
*** _nadya_ has quit IRC09:04
*** ijw__ has quit IRC09:09
*** _nadya__ has joined #openstack-meeting09:12
*** dguerri` is now known as dguerri09:14
*** aimon_ has joined #openstack-meeting09:14
*** aimon has quit IRC09:14
*** e0ne is now known as e0ne_09:15
*** eliqiao1 has quit IRC09:16
*** sudipto has joined #openstack-meeting09:22
*** e0ne_ has quit IRC09:26
*** eliqiao has joined #openstack-meeting09:29
*** e0ne has joined #openstack-meeting09:29
*** breitz has quit IRC09:30
*** breitz has joined #openstack-meeting09:30
*** markvoelker has joined #openstack-meeting09:34
*** jhenner has quit IRC09:36
*** irenab has quit IRC09:39
*** irenab has joined #openstack-meeting09:39
*** markvoelker has quit IRC09:39
*** subscope has quit IRC09:44
*** ddieterly has joined #openstack-meeting09:48
*** ociuhandu has quit IRC09:52
*** irenab has quit IRC09:52
*** ddieterly has quit IRC09:53
*** ijw has joined #openstack-meeting09:53
*** irenab has joined #openstack-meeting09:54
*** stevemar has joined #openstack-meeting09:56
*** Gerald_K has quit IRC09:58
*** otter768 has joined #openstack-meeting09:59
*** ijw has quit IRC09:59
*** stevemar has quit IRC10:00
*** subscope has joined #openstack-meeting10:01
*** arnaud____ has joined #openstack-meeting10:02
*** otter768 has quit IRC10:04
*** sahid has quit IRC10:04
*** irenab has quit IRC10:07
*** arnaud____ has quit IRC10:07
*** Gerald_K has joined #openstack-meeting10:08
*** sahid has joined #openstack-meeting10:11
*** epico has quit IRC10:12
*** epico has joined #openstack-meeting10:13
*** fzdarsky has joined #openstack-meeting10:13
*** coolsvap is now known as coolsvap|away10:14
*** Yanyanhu has quit IRC10:15
*** lufix has quit IRC10:15
*** yatin has joined #openstack-meeting10:18
*** epico has quit IRC10:18
*** egallen has joined #openstack-meeting10:20
*** irenab has joined #openstack-meeting10:22
*** e0ne is now known as e0ne_10:23
*** ijw has joined #openstack-meeting10:23
*** irenab has quit IRC10:25
*** jhenner has joined #openstack-meeting10:25
*** e0ne_ is now known as e0ne10:25
*** Gerald_K_ has joined #openstack-meeting10:26
*** Gerald_K has quit IRC10:26
*** mpaolino_ has joined #openstack-meeting10:27
*** jlanoux_ has joined #openstack-meeting10:29
*** ijw has quit IRC10:29
*** jlanoux has quit IRC10:31
*** casusbelli has joined #openstack-meeting10:32
*** henrynash has quit IRC10:34
*** rossella_s has quit IRC10:36
*** irenab has joined #openstack-meeting10:37
*** rossella_s has joined #openstack-meeting10:37
*** irenab has quit IRC10:37
*** ajayaa_ has quit IRC10:38
*** irenab has joined #openstack-meeting10:38
*** irenab has quit IRC10:39
*** claudiub has quit IRC10:40
*** irenab has joined #openstack-meeting10:43
*** toscalix has quit IRC10:46
*** ddieterly has joined #openstack-meeting10:49
*** ociuhandu has joined #openstack-meeting10:50
*** yamamoto has quit IRC10:50
*** BharatK has quit IRC10:51
*** jlanoux has joined #openstack-meeting10:51
*** ddieterly has quit IRC10:54
*** ajayaa_ has joined #openstack-meeting10:54
*** jlanoux_ has quit IRC10:55
*** oanufrie1 has joined #openstack-meeting10:57
*** hichihara has joined #openstack-meeting10:58
*** fzdarsky has quit IRC11:01
*** BharatK has joined #openstack-meeting11:02
*** linuxmohan has quit IRC11:04
*** oanufrie1 has left #openstack-meeting11:05
*** dims has joined #openstack-meeting11:07
*** amakarov_away is now known as amakarov11:12
*** larainema has joined #openstack-meeting11:14
*** hashar has quit IRC11:16
*** IanGovett has joined #openstack-meeting11:18
*** Gerald_K_ has quit IRC11:19
*** dkusidlo has joined #openstack-meeting11:19
*** weshay has joined #openstack-meeting11:21
*** mpaolino_ has quit IRC11:23
*** mpaolino has quit IRC11:23
*** ijw has joined #openstack-meeting11:23
*** markvoelker has joined #openstack-meeting11:24
*** neeti has quit IRC11:26
*** markvoelker has quit IRC11:29
*** ijw has quit IRC11:29
*** subscope has quit IRC11:31
*** britthouser has joined #openstack-meeting11:31
*** xingchao_ has joined #openstack-meeting11:32
*** radez is now known as radez_g0n311:36
*** xingchao_ has quit IRC11:36
*** ruhe has left #openstack-meeting11:37
*** ildikov has quit IRC11:38
*** dprince has joined #openstack-meeting11:40
*** baoli has joined #openstack-meeting11:40
*** nadeem has joined #openstack-meeting11:42
*** nadeem has quit IRC11:42
*** nadeem has joined #openstack-meeting11:43
*** stevemar has joined #openstack-meeting11:45
*** dmacpher has joined #openstack-meeting11:45
*** hichihara has quit IRC11:47
*** ozstacker has quit IRC11:47
*** subscope has joined #openstack-meeting11:47
*** ozstacker has joined #openstack-meeting11:47
*** stevemar has quit IRC11:48
*** tochi has quit IRC11:49
*** ddieterly has joined #openstack-meeting11:50
*** fawadkhaliq has quit IRC11:51
*** ildikov has joined #openstack-meeting11:51
*** egallen_ has joined #openstack-meeting11:52
*** _nadya__ has quit IRC11:52
*** egallen has quit IRC11:53
*** egallen_ is now known as egallen11:53
*** _nadya_ has joined #openstack-meeting11:53
*** MaxPC has joined #openstack-meeting11:54
*** ddieterly has quit IRC11:54
*** mwagner_lap has joined #openstack-meeting11:54
*** bzhao has joined #openstack-meeting11:55
*** jruano has joined #openstack-meeting11:57
*** _nadya_ has quit IRC11:57
*** radez_g0n3 is now known as radez11:58
*** _nadya_ has joined #openstack-meeting11:58
*** bill_az has joined #openstack-meeting11:58
*** otter768 has joined #openstack-meeting12:00
*** hichihara has joined #openstack-meeting12:00
*** prad has joined #openstack-meeting12:02
*** markvoelker has joined #openstack-meeting12:02
*** AzherKhan has quit IRC12:03
*** marcusvrn has joined #openstack-meeting12:05
*** otter768 has quit IRC12:05
*** lkarm has joined #openstack-meeting12:08
*** annemccormick has joined #openstack-meeting12:08
*** maishsk has quit IRC12:09
*** claudiub has joined #openstack-meeting12:10
*** markvoelker_ has joined #openstack-meeting12:11
*** markvoel_ has joined #openstack-meeting12:13
*** markvoelker has quit IRC12:13
*** maishsk_afk has joined #openstack-meeting12:14
*** maishsk_afk is now known as maishsk12:14
*** hashar has joined #openstack-meeting12:15
*** belmoreira has quit IRC12:15
*** sudipto has quit IRC12:16
*** markvoelker_ has quit IRC12:17
*** subscope has quit IRC12:17
*** dkusidlo has quit IRC12:18
*** fzdarsky has joined #openstack-meeting12:19
*** ijw has joined #openstack-meeting12:23
*** amrith is now known as _amrith_12:25
*** ijw has quit IRC12:29
*** ivasev has joined #openstack-meeting12:30
*** ajayaa_ has quit IRC12:31
*** aysyd has joined #openstack-meeting12:32
*** haiwei has joined #openstack-meeting12:33
*** banix has joined #openstack-meeting12:34
*** _nadya_ has quit IRC12:34
*** ivasev has quit IRC12:34
*** numan has quit IRC12:36
*** maishsk has quit IRC12:36
*** MeganR has left #openstack-meeting12:36
*** maishsk_afk has joined #openstack-meeting12:37
*** maishsk_afk is now known as maishsk12:37
*** hichihara has quit IRC12:38
*** mmedvede has joined #openstack-meeting12:38
*** _nadya_ has joined #openstack-meeting12:38
*** dkusidlo has joined #openstack-meeting12:38
*** yamamoto has joined #openstack-meeting12:39
*** hichihara has joined #openstack-meeting12:40
*** banix has quit IRC12:40
*** _nadya_ has quit IRC12:42
*** _nadya_ has joined #openstack-meeting12:42
*** _nadya_ has quit IRC12:42
*** ivasev has joined #openstack-meeting12:42
*** _nadya_ has joined #openstack-meeting12:43
*** mpaolino_ has joined #openstack-meeting12:45
*** esther has joined #openstack-meeting12:45
*** mpaolino has joined #openstack-meeting12:45
*** yanyanhu has joined #openstack-meeting12:47
*** bknudson has joined #openstack-meeting12:47
*** ayoung has quit IRC12:48
*** maishsk has quit IRC12:48
*** _nadya_ has quit IRC12:48
*** _nadya_ has joined #openstack-meeting12:49
*** _nadya_ has quit IRC12:49
*** _nadya_ has joined #openstack-meeting12:49
*** scheuran has quit IRC12:49
*** rfolco has joined #openstack-meeting12:50
*** ddieterly has joined #openstack-meeting12:51
*** markvoel_ has quit IRC12:51
*** asadoughi has joined #openstack-meeting12:51
*** Guest27041 has joined #openstack-meeting12:51
*** markvoelker_ has joined #openstack-meeting12:52
*** _nadya_ has quit IRC12:52
*** yamamoto has quit IRC12:53
*** maishsk_afk has joined #openstack-meeting12:53
*** maishsk_afk is now known as maishsk12:53
*** bknudson has quit IRC12:54
*** _nadya_ has joined #openstack-meeting12:54
*** kylek3h has joined #openstack-meeting12:54
*** ddieterly has quit IRC12:55
*** neelashah1 has joined #openstack-meeting12:55
*** lixinhui has joined #openstack-meeting12:57
*** Gerald_K has joined #openstack-meeting12:57
*** irenab has quit IRC12:57
*** Qiming has joined #openstack-meeting12:58
*** esther has quit IRC12:59
*** yanyanhu_ has joined #openstack-meeting12:59
*** sebrandon1 has joined #openstack-meeting12:59
*** egallen_ has joined #openstack-meeting12:59
Qiming#start-meeting senlin13:00
*** yanyanhu has quit IRC13:00
*** egallen has quit IRC13:00
*** egallen_ is now known as egallen13:00
Qiming#startmeeting senlin13:00
openstackMeeting started Tue Jun 30 13:00:35 2015 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
Qimingokay, no dash13:00
*** puranamr has joined #openstack-meeting13:00
Qiminggood morning/evening13:01
Qimingplease review meeting agenda: https://wiki.openstack.org/wiki/Meetings/SenlinAgenda13:01
Qimingif you want to add something, just edit13:01
*** markvoelker_ has quit IRC13:02
Qimingor you can shoot it during open discussion13:02
Qiming#topic test case coverage13:02
*** openstack changes topic to "test case coverage (Meeting topic: senlin)"13:02
*** markvoelker has joined #openstack-meeting13:02
*** bryan_att has joined #openstack-meeting13:02
Qimingin last meeting, we called for filing bugs related to test case coverage13:03
Qimingmy latest number is 63% coverage, not a bad number13:03
*** markvoelker_ has joined #openstack-meeting13:03
*** ddieterly has joined #openstack-meeting13:03
Qimingwe still need to spend quite some time on writing test cases, especially those related to profiles, actions, policies13:04
jruanoi will try to make some time this week13:04
haiweiI found some modules like senlin/engine/nodes.py are not well tested13:04
Qimingokay, this link is too long, sorry13:04
yanyanhu_I will try to start working on scaling and lb policy related test cases after finish related wiki item13:05
Qiminghaiwei, feel free to file a bug for that then13:05
*** Gerald_K has quit IRC13:05
haiweiok, already filed some13:05
*** hrou has joined #openstack-meeting13:05
*** markvoelker_ has quit IRC13:05
Qimingwe talked about setting milestones/deadlines for those bugs13:05
Qiminghowever, it is really up to how many resources we can put on it13:05
*** banix has joined #openstack-meeting13:06
Qimingin case you are not familar with the milestones13:06
*** markvoelker_ has joined #openstack-meeting13:06
*** ddieterly has quit IRC13:06
*** changbl has quit IRC13:06
Qimingwe have missed liberty-1, obviously13:06
Qimingit doesn't make good sense to release the packages at this stage13:07
Qimingnext milestone would be 2015-07-2913:07
*** markvoelker has quit IRC13:07
*** adahms has joined #openstack-meeting13:07
Qimingwhich means we have 90 days or so to work on this, among other things13:07
yanyanhu_29 days?13:08
Qimingso ... maybe we should just encourage people to claim bugs and set deadlines themselves13:08
*** beagles is now known as beagles_biab13:08
Qimingoh, no, 30 days13:08
lixinhuisounds terrible13:08
*** vivek-ebay has joined #openstack-meeting13:08
yanyanhu_maybe a plan but not deadline13:08
Qimingaha, time is very tight13:09
haiweiI will have a summer vocation from 7/10 though13:09
yanyanhu_if we focus on test case, I think we might be able to finish it13:09
Qimingwe will work hard on this, using all resources we have, and see what happens by liberty-213:09
haiweianyway, I will try my best in other days13:09
yanyanhu_ok, I think at least we should finish test cases for all policies and actions13:10
lixinhuiQiming and yanyan, do you have vacation plan?13:10
*** mrunge has quit IRC13:10
yanyanhu_I don't have for this summer13:10
*** banix has quit IRC13:10
*** kylek3h_ has joined #openstack-meeting13:10
*** bknudson has joined #openstack-meeting13:10
Qimingalthough we have a heavy pressure on this, please don't lower your bar when review, ;)13:10
*** banix has joined #openstack-meeting13:10
Qiminglixinhui, not yet13:11
yanyanhu_sure :)13:11
Qimingwill let the team know if so, :)13:11
haiweiof courese13:11
*** kylek3h has quit IRC13:11
*** kylek3h_ is now known as kylek3h13:11
Qimingokay, moving on13:11
Qiming#topic documentation13:11
*** openstack changes topic to "documentation (Meeting topic: senlin)"13:11
*** xyhuang has joined #openstack-meeting13:11
Qimingwe have been working on some docs for developers during the past weeks13:11
*** kylek3h has quit IRC13:12
Qimingnow we have already covered most aspects of the design13:12
haiweiit's your jobs, thanks13:12
jruanoi have been going through the documentation in order to get caught up on the project. what is there is very good13:12
Qimingyeah, my job, :)13:12
*** peristeri has joined #openstack-meeting13:12
*** _nadya_ has quit IRC13:12
Qimingif you have ever checked the output from the python-docs gate, it is pretty cool13:13
Qimingwhat we still need to do is docs for users (user-guide, getting-started ...)13:13
Qimingand wiki13:13
*** vivek-ebay has quit IRC13:13
yanyanhu_yes, saw it :)13:13
Qimingwill work on this13:13
Qimingit will be my high priority13:13
yanyanhu_will also work on it in this week13:14
Qimingfor some reasons: even a new developer would need to know how to try things out13:14
*** puranamr has quit IRC13:14
jruanoyes... magnum has a good getting started guide if you need a template to use13:14
haiweiyes, you don't need to explain to them one by one13:14
*** egallen_ has joined #openstack-meeting13:14
Qimingand for others who just heard of the word "senlin", he/she will check openstack wiki first13:14
*** egallen has quit IRC13:14
*** egallen_ is now known as egallen13:14
Qimingthanks, I was thinking about that13:15
yanyanhu_maybe we should provide a quick start guide at first13:15
QimingI really hope we don't need to write the same thing over and over again, all over different places13:15
*** jckasper has quit IRC13:15
haiweiI think I have a good news, some people from my company has began to know senlin, not by my introduction13:15
QimingI will check openstack-manuals project, for example, to learn how they structure a guide for users13:15
haiweithat means many people may have already known senlin13:16
Qiminghopefully, we will only need to copy our writings to that project when senlin gets "integrated"13:16
*** jehb has joined #openstack-meeting13:16
haiweiso if the docs get ready soon, will be very helpful13:16
Qimingwe have to polish the wiki page as well, it will be the "frontpage" for the project13:16
jruanoah, that makes sense qiming13:16
*** absubram has joined #openstack-meeting13:17
Qiminghave just done something: wiki.openstack.org/wiki/Senlin13:17
Qimingneed to add some details there13:17
Qimingany helps on that would be appreciated13:18
Qiming#topic object deletion handling13:18
*** openstack changes topic to "object deletion handling (Meeting topic: senlin)"13:18
Qiminghaiwei do you want to talk about it?13:18
openstackLaunchpad bug 1469939 in senlin "dead lock happens when trying to delete a node" [Undecided,New]13:18
*** julim has joined #openstack-meeting13:19
haiweiin fact I want to talk about another first https://bugs.launchpad.net/senlin/+bug/146995313:19
openstackLaunchpad bug 1469953 in senlin "Node deletion error" [Undecided,In progress] - Assigned to Haiwei Xu (xu-haiwei)13:19
yanyanhu_I guess another action might hang there and didn't release node lock correctly13:20
yanyanhu_and thus caused this deadlock13:20
haiweiyes, yanyanhu13:20
Qimingseems to me like the bugs are caused by the same problem?13:20
haiweinot exactly i think13:20
haiwei1469953 is caused by  node deletion when deleting a heat stack will check the heat stack status first13:21
*** Guest27041 is now known as agentle13:21
Qimingit is not a "dead" lock, it's actually about ensuring locks are released when not needed13:21
haiweisee the source http://git.openstack.org/cgit/stackforge/senlin/tree/senlin/profiles/os/heat/stack.py#n11713:21
yanyanhu_Qiming, yes13:21
haiweibut when senlin sends a DELETE request to heat, heat stack will remain CREATE_COMPLETE for a while before going to DELETE_IN_PROGRESS. so we will get CREATE != DELETE error.13:22
haiweithe solution can be add a sleep(1) before checking the status. https://review.openstack.org/#/c/196947/1/senlin/profiles/os/heat/stack.py13:22
Qimingsleep(1) is so .... ugly13:22
yanyanhu_seems we should provide another status option here13:22
haiweithis bug is not related to lock I think13:23
haiweiyes, Qiming13:23
Qimingneed to come up with a better status check13:23
*** ijw has joined #openstack-meeting13:23
haiweiwe just need to wait for heat a moment13:23
yanyanhu_I think we should change the implementation of _check_action_complete13:23
haiweiyanyanhu_, that is a good idea13:23
haiweiI will think about it later13:24
*** banix has quit IRC13:24
Qiminglet's see what we can do13:24
yanyanhu_yes :)13:24
Qimingthat leads us also to the next topic13:25
Qiming#topic SDK exception handling13:25
*** openstack changes topic to "SDK exception handling (Meeting topic: senlin)"13:25
*** _nadya_ has joined #openstack-meeting13:25
haiweibecause _check_action_complete is used by creation, deletion and updating, it should be careful13:25
*** kyleh_ has joined #openstack-meeting13:25
Qimingwhen Senlin is talking to other OpenStack service, we do that through OpenStackSDK13:25
Qimingnot only we have to cope with resource status carefully, we have to consider all types of exceptions13:26
*** praveens has joined #openstack-meeting13:26
haiweiyes, currently we are not handling sdk's exception well i think13:26
*** toscalix has joined #openstack-meeting13:26
haiweiexcept sdk.exc.HttpException as ex:  57             raise ex13:26
Qimingthe sad news is that there is no formal guidelines or even consensus among projects today13:27
*** nelsnelson has joined #openstack-meeting13:27
haiweiwe just catch HttpException and raise it again13:27
yanyanhu_yes, I guess this is the only exception we catch from openstacksdk13:27
Qimingspeaking of that, please refer to senlinclient code here13:27
haiweiso what about translating HTTPException to a senlin InternalError13:27
*** kylek3h has joined #openstack-meeting13:28
Qimingwhen I was writing the client code, I was trying to consider all possibilities13:28
yanyanhu_exception definition in sdk13:28
*** e0ne is now known as e0ne_13:29
Qimingcatch all exception types we can and either kill them inside senlin or return them to users in a meaningful way13:29
*** ijw has quit IRC13:29
Qimingwe can keep an eye on SDK's exception handling13:29
Qimingbut we still need to be prepared for the "rare" cases where exceptions are not handled by SDK13:29
Qimingso far, I know they have been dealing with 404 very well, ;)13:30
haiweiyanyanhu_, we can only get HttpException from SDK?13:30
*** egallen has quit IRC13:30
yanyanhu_also some other exceptions13:30
Qimingthe problem is "some other exceptions"13:30
yanyanhu_but I think this is the most common one we will use13:30
Qimingwe don't know their type, format, message13:31
*** egallen has joined #openstack-meeting13:31
*** boris-42 has joined #openstack-meeting13:31
haiweithey are all here? http://git.openstack.org/cgit/stackforge/python-openstacksdk/tree/openstack/exceptions.py13:31
Qimingsometimes, maybe, we can only get an error code, in a strange field ...13:31
*** dkusidlo has quit IRC13:31
yanyanhu_yes, so I think we don't have much choice now13:31
*** kylek3h has quit IRC13:31
*** thangp has joined #openstack-meeting13:31
*** cody-somerville has joined #openstack-meeting13:32
*** cody-somerville has quit IRC13:32
*** cody-somerville has joined #openstack-meeting13:32
briancurtinQiming: if you need something more out of that exceptions module, perhaps enter a bug on https://bugs.launchpad.net/python-openstacksdk and we can look into it. i dont think we've done much with those exceptions13:32
QimingI did encountered cases where Heat errors were not caught by SDK, but I cannot recall the details13:32
*** regXboi has joined #openstack-meeting13:32
Qimingaha, briancurtin, didn't expect you here, ;)13:32
briancurtinQiming: my IRC client highligts on "SDK"13:32
Qimingit would be pretty cool if we can help improve that13:32
*** _amrith_ is now known as amrith13:33
Qimingokay, guys, all questions about SDK go to briancurtin, now and in future13:33
*** kyleh_ has quit IRC13:33
haiweimaybe we also should enter SDK's meeting to give them some suggestions :)13:33
*** banix has joined #openstack-meeting13:33
Qiminghaiwei, that would be cool13:34
*** ajayaa_ has joined #openstack-meeting13:34
*** stevemar has joined #openstack-meeting13:34
*** kylek3h has joined #openstack-meeting13:34
briancurtinour meeting is today, Tuesdays at 1900 UTC13:34
QimingI really see SDK a foundational service in openstack, it will make a lot things easier13:34
haiweiand we can also help them with some implement13:34
*** jhenner has quit IRC13:34
yanyanhu_midnight in our time zone...13:35
*** jhenner has joined #openstack-meeting13:35
*** htruta has joined #openstack-meeting13:35
Qimingbriancurtin, do you have a alternate meeting slot?13:35
briancurtinhmm, i will look around the calendar and see if there are other times that might work. which timezone are you?13:35
QimingGMT +813:36
haiweiso file a bug to SDK maybe a good idea13:36
Qiminghaiwei, +113:36
*** ctrath has joined #openstack-meeting13:36
Qimingand help fix it13:36
briancurtinright now the meeting is in the afternoon for all US people, so we can maybe move it13:36
Qimingcool, let us know when there are meetings we can attend, briancurtin13:37
yanyanhu_thanks, briancurtin :)13:37
briancurtinit might be hard to find a time that works since we are 13 hours apart, but maybe we can figure something out13:37
*** lixinhui has quit IRC13:37
*** stevemar has quit IRC13:37
briancurtiner, 1113:37
Qimingokay, talk though code and review then13:37
haiweiI am GMT+913:37
haiweia little easier maybe13:38
yanyanhu_comment is also a good way I believe13:38
Qimingtimezone is really annoying, and you cannot get rid of it13:38
Qimingso ... guys, we work with the sdk team to handle exceptions13:39
*** e0ne_ has quit IRC13:39
Qimingwhen we see exceptions from other services, let's talk whether we should move the handling logic to sdk13:39
haiweifirst we should understand SDK exception's type, i think, I have no idea of HttpException13:39
haiweiit seems like a common exception13:39
Qimingokay, that's your homework, haiwei, :)13:40
Qimingand my homework, obviously13:40
*** sigmavirus24_awa is now known as sigmavirus2413:40
Qiminglet's move on13:40
Qiming#topic open discussions13:41
*** openstack changes topic to "open discussions (Meeting topic: senlin)"13:41
haiweiQiming, you mean we should try to make most exceptions outside senlin get handled by SDK?13:41
Qiminghaiwei, we will study case by case, and see if it is common exception to be handled by sdk13:41
*** singlethink has joined #openstack-meeting13:41
yanyanhu_hi, Qiming, I think maybe we should give a list of items which have highest priority13:41
Qiminglist of what?13:42
*** zz_jgrimm is now known as jgrimm13:42
*** stevemar has joined #openstack-meeting13:42
haiweiexception type?13:42
yanyanhu_then we can know what is the focus we are woking on recently13:42
yanyanhu_nope, all work items of senlin13:42
*** BharatK has quit IRC13:42
Qimingfirst things first, test cases13:43
*** pratap has joined #openstack-meeting13:43
haiweicurrently test case and exception handle i think13:43
*** agentle has quit IRC13:43
haiweiand also some bugs13:43
Qimingthat will help us find bugs13:43
*** ayoung has joined #openstack-meeting13:43
Qimingafter unit test cases, we will have funtional tests13:43
*** dkusidlo has joined #openstack-meeting13:43
haiweiand your policy implementation13:44
yanyanhu_e.g. test cases, doc, new features we need to support13:44
yanyanhu_e.g. in next 30 days, I think the list will include doc, test cases, wiki13:44
*** sebrandon1 has quit IRC13:44
Qimingokay, we can use etherpad for this13:44
Qimingwill open one for everyone to input/edit13:45
yanyanhu_so we can measure whether these items can be done before the deadline13:45
*** sudipto has joined #openstack-meeting13:45
*** egallen has quit IRC13:45
Qiming#action Qiming to open a etherpad for work items and schedule13:45
*** ihrachyshka_ has joined #openstack-meeting13:46
Qimingsince we have talked about time zone problems13:46
*** nmagnezi has joined #openstack-meeting13:46
QimingI really feel sorry for people like lkarm, jruano, ...13:46
*** e0ne has joined #openstack-meeting13:46
*** hoangcx has joined #openstack-meeting13:46
Qimingwhen they are online, we are mostly in dreams13:47
Qimingthe good news: https://review.openstack.org/#/c/196993/13:47
Qimingjust figured out how to get our IRC chats logged13:47
jruanoits 8am my time, so not too bad for me. i can usually stay online later in the night, but yes timezones are problematic13:47
Qimingonce the above patch is accepted, we will have IRC log archive13:48
*** barrett has joined #openstack-meeting13:48
Qimingso you guys can check if needed13:48
jruanovery good news13:48
yanyanhu_or we can use etherpad to ask and answer questions?13:48
*** barrett has left #openstack-meeting13:48
Qimingyanyanhu_, questions should go to mailinglist I guess13:49
haiweithe senlin mailing is not well used now13:49
yanyanhu_hmm, right13:49
*** banix has quit IRC13:49
Qimingyes, when we have some general questions, we should leverage that indeed13:49
Qimingokay, guys, we still have 10 minutes13:50
QimingI'd like to share with you another "news"13:50
Qimingwe are inviting haiwei to be a core member of senlin project13:50
Qimingyanyanhu_ and I had some discussions on this13:51
*** annp has joined #openstack-meeting13:51
Qiminghaiwei has been a very active contributor since he gets involved in this project13:51
*** yongshenggong_ has joined #openstack-meeting13:51
*** ijw has joined #openstack-meeting13:51
haiweithanks for trusting me, Qiming13:51
Qiminghe has gained enough knowledge to help the project moving forward13:52
jruanocongrats haiwei13:52
*** singleth_ has joined #openstack-meeting13:52
*** Murali has quit IRC13:52
Qimingit would mean more responsibility and more time dedication though13:52
haiweithanks, it's my honor13:52
*** vivek-ebay has joined #openstack-meeting13:52
Qimingso, haiwei, pitty on you13:52
yanyanhu_con :)13:52
*** jlibosva has joined #openstack-meeting13:52
haiweiyes, will work even harder :)13:52
Qimingsince the team is not big, we are not announcing this in the mailinglist13:52
*** wxy has joined #openstack-meeting13:53
*** wxy has quit IRC13:53
*** egallen has joined #openstack-meeting13:53
*** wxy has joined #openstack-meeting13:54
Qiminganything else?13:54
haiweino from me13:54
yanyanhu_oh, about the topic proposal, so we have submitted it?13:54
Qimingyanyanhu_, still waiting for company review13:54
yanyanhu_when the vote will start13:54
*** BharatK has joined #openstack-meeting13:55
*** eharney has joined #openstack-meeting13:55
Qimingneed to check out the deadline13:55
*** vivek-eb_ has joined #openstack-meeting13:55
*** singlethink has quit IRC13:55
Qimingokay, let's turn to #senlin if you have any questions, comments, suggestions ...13:56
*** openstack changes topic to "OpenStack CI is down due to hard drive failures"13:56
*** jckasper has joined #openstack-meeting13:56
openstackMeeting ended Tue Jun 30 13:56:33 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-06-30-13.00.html13:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-06-30-13.00.txt13:56
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-06-30-13.00.log.html13:56
regXboimestery: morning13:56
*** vivek-ebay has quit IRC13:56
mesteryregXboi: You're 3 minutes early :)13:57
regXboimestery: and this surprises you how? :)13:57
*** haiwei has quit IRC13:57
*** fawadkhaliq has joined #openstack-meeting13:57
*** yamahata has joined #openstack-meeting13:58
*** baoli has quit IRC13:59
* mestery waits a bit for people to congregate13:59
ajohi! :)13:59
rossella_shi all!14:00
*** yanyanhu_ has left #openstack-meeting14:00
*** jecarey has joined #openstack-meeting14:00
*** baoli has joined #openstack-meeting14:00
regXboimestery: one administrivia - isn't next monday 7/4 observed?14:00
mesteryWe've got a packed agenda today, I suspect we won't get through all of it. So lets get started.14:00
mestery#startmeeting networking14:00
openstackMeeting started Tue Jun 30 14:00:44 2015 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
hoangcxHi all!14:00
*** dims has quit IRC14:01
*** carl_baldwin has joined #openstack-meeting14:01
mesteryregXboi:Monday is 7/614:01
*** yamamoto has joined #openstack-meeting14:01
*** pc_m has joined #openstack-meeting14:01
*** otter768 has joined #openstack-meeting14:01
*** belmoreira has joined #openstack-meeting14:01
mestery#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:01
mesteryLike I said, it's packed, so lets get the ball rolling!14:01
mestery#topic Announcements14:01
*** mkolesni has joined #openstack-meeting14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
*** Gerald_K has joined #openstack-meeting14:01
mestery#info Liberty-1 was release last week!14:01
mestery#link https://launchpad.net/neutron/+milestone/liberty-114:01
*** dims has joined #openstack-meeting14:01
*** marun has joined #openstack-meeting14:01
mesteryPlease report bugs using Launchpad if you try out the release tarballs14:01
*** Qiming has left #openstack-meeting14:01
mestery#info The QoS coding sprint is currently ongoing in Raanana Israel14:02
mestery#link https://etherpad.openstack.org/p/neutron-liberty-qos-code-sprint14:02
regXboimestery: ack - I see that I'm confused - 7/3 is the observed day14:02
mesteryregXboi: Yes14:02
mesteryLets keep moving to try and cull the agenda as much as we can today.14:02
mestery#topic QoS Coding Sprint Update14:02
*** openstack changes topic to "QoS Coding Sprint Update (Meeting topic: networking)"14:02
mesteryajo: Hi there!14:02
ajohi :)14:02
*** cbouch has joined #openstack-meeting14:03
ajoWe've been working all day, meeting, thanks to all the contributors that were able to come, and join us remotely.14:03
*** sudipto has quit IRC14:03
ajoFirst of all, we submited an amendment to the QoS API spec to make it more consistent14:03
ajo#link https://review.openstack.org/#/c/197004/14:03
*** adahms has quit IRC14:04
ajoand we have also submited the code & neutron-client counterparts14:04
*** jokke_ has joined #openstack-meeting14:04
*** francois has quit IRC14:04
ajo#link https://review.openstack.org/19707814:04
*** praveens1 has joined #openstack-meeting14:04
*** sudipto has joined #openstack-meeting14:05
mesteryajo: Nice work!14:05
*** praveens1 has left #openstack-meeting14:05
*** egallen has quit IRC14:05
*** egallen_ has joined #openstack-meeting14:05
*** adrian-hoban has joined #openstack-meeting14:05
ajo#link https://review.openstack.org/#/c/189655/14:05
*** neiljerram has joined #openstack-meeting14:05
*** praveens1 has joined #openstack-meeting14:05
ajowe had a spec about the OvS agent still open, so , we wanted to ask how to proceed14:05
*** otter768 has quit IRC14:06
mesteryajo: Link? I suggest we try and prioritize this to get it approved, it's required for QoS so we could approve it or just use devref, your call14:06
ajohttps://review.openstack.org/182349  (ovs agent spec)14:06
*** vikram has joined #openstack-meeting14:06
ajomestery we could move it to devref if that's ok14:06
mesteryajo: ++14:06
ajoprobably it makes sense since it's necessary to have a reference for the API :)14:06
*** praveens has quit IRC14:07
*** phil_ has quit IRC14:07
mesteryajo: ++14:07
ajothere are a few patches on flight, if anybody has time, here's the link for the topic:14:07
mestery#info QoS OVS agent spec to be moved to devref as part of implementation14:07
mestery#link https://review.openstack.org/#/q/topic:neutron-qos,n,z QoS patches review link14:07
*** dkusidlo has quit IRC14:07
*** _nadya_ has quit IRC14:07
ajoany review time is appreciated14:08
ajoan important note, is that we're a bit abusing armax callback mechanism14:08
*** rjaiswal has joined #openstack-meeting14:08
ajounder his permission, with a long term goal of extending it's API when dealing with resource extensions14:08
ajohe has something in mind and he will do it, while we abuse his current implementation to avoid blocking us :)14:08
*** scheuran has joined #openstack-meeting14:09
ajoI wasl talking about this: https://review.openstack.org/#/c/193585/14:09
mesteryajo: OK, make sure to keep armax in the loop here going forward please14:09
ajomestery, of course14:09
*** francois has joined #openstack-meeting14:09
*** john_a_joyce has joined #openstack-meeting14:09
ajoAnything I'm missing?14:10
ihrachyshka_and yeah, please fix gate ;)14:10
mkolesniajo: https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:feature/qos,n,z14:10
ajo(asking to the participants)14:10
ajoihrachyshka_: lol14:10
*** pratap has quit IRC14:10
mesteryThanks for the update ajo! Now, please take the QoS team out for a team dinner :)14:10
vikramajo: you have covered everything :)14:10
ajomestery: I think it's all, I will send some links to pictures in some minutes, but let's not block the meeting anymore14:10
mesteryajo: Thanks, we'll move along then. :)14:11
lpeermestery: it is being taken care of14:11
mesterylpeer: Excellent! :)14:11
mestery#topic Bugs14:11
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:11
*** abregman has joined #openstack-meeting14:11
mesteryWe have a number of bugs I wanted to highlight this week14:11
*** mtanino has joined #openstack-meeting14:11
*** wxy has left #openstack-meeting14:11
mestery#topic https://bugs.launchpad.net/neutron/+bug/146543414:11
*** openstack changes topic to "https://bugs.launchpad.net/neutron/+bug/1465434 (Meeting topic: networking)"14:11
openstackLaunchpad bug 1465434 in neutron "DVR issues with supporting multiple subnets per network on DVR routers - PortbindingContext does not have the status." [Critical,Confirmed] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)14:11
mesteryThis one is why DVR hasn't worked in the gate for weeks now.14:11
mesterySwami is on this, his patch listed there could use reviews14:11
mesteryWe need to get DVR stable again and get the DVR job running and the multi-node job14:12
mesteryyamamoto: If you have time, can you review this one please?14:12
mesteryhaleyb: Also your review needed here :)14:12
haleybyes, will look14:12
mesteryNext up14:12
*** dkusidlo has joined #openstack-meeting14:12
openstackLaunchpad bug 1465837 in neutron "Linux bridge: Dnsmasq is being passed None as an interface" [Critical,New] - Assigned to Sean M. Collins (scollins)14:12
mesterysc68cal: This one looks to be yours :)14:12
mesteryHow is it coming? I know you were at the mid-cycle last week14:13
sc68calI've also seen some race conditions in the linux bridge job around network deletion and port binding (I think)14:13
*** beagles_biab is now known as beagles14:13
mesteryCool! I saw an agenda item later in the meeting for that14:13
* beagles wanders in late14:13
ihrachyshka_mestery, we're eager to get something to digest, if anything, reviews please14:13
*** ihrachyshka_ has quit IRC14:13
sc68calWe're at the point where we can actually run all the tests, but it does appear that the linux bridge mechanism driver needs some attention14:13
*** topol has joined #openstack-meeting14:13
sc68calwe've got a couple bugs that I plan on opening and filling in details about, based on what I'e seen from experimental runs14:14
sc68calif anyone is interested in helping please let me know14:14
mesterysc68cal: OK, that sounds fine, when you do, feel free to add a section to the weekly agenda here14:14
sc68calmestery: well do14:14
mestery#info sc68cal to file some bugs around the rough edges of the Linuxbridge ML2 driver14:14
mesteryThanks sc68cal14:14
*** annegentle has joined #openstack-meeting14:14
mesteryUp next14:14
openstackLaunchpad bug 1359523 in neutron "Security group rules are erroneously applied to all ports having same ip addresses in different networks" [High,In progress] - Assigned to shihanzhang (shihanzhang)14:14
*** puranamr has joined #openstack-meeting14:15
*** ihrachyshka has joined #openstack-meeting14:15
mesteryLooks like a partial fix for this one merged14:15
mesteryA while back14:15
*** jruano has quit IRC14:15
mesteryWe discussed this 3 weeks back, and not much has happened since.14:15
mesteryI'll reach out to shihanzhang14:15
*** dt_os has joined #openstack-meeting14:16
mestery#action mestery to reach out to shihanzhang on 135952314:16
openstackLaunchpad bug 1335375 in neutron "ping still working after security group rule is created, updated, or deleted" [High,In progress] - Assigned to shihanzhang (shihanzhang)14:16
mesteryI think the same for this one14:16
mestery#action mestery to reach out to shihanzhang on 133537514:17
mesteryOK, two more14:17
openstackLaunchpad bug 1461172 in neutron "neutron.tests.functional.agent.test_l3_agent.MetadataL3AgentTestCase.test_access_to_metadata_proxy times out intermittently" [High,Confirmed] - Assigned to Assaf Muller (amuller)14:17
*** _nadya_ has joined #openstack-meeting14:17
mesteryI assigned this to amuller for further triage, but this one looks like a gate issue currently.14:17
mesteryThere was a revert amuller and I ninja merged which I think is related to this failure14:17
*** john-davidge has joined #openstack-meeting14:18
jlibosvamestery: no, that was related to new fixture 1.3.0 release :)14:18
mesteryjlibosva: :)14:18
jlibosvamestery: ignore me, I thought you;re talking about the bug above :-/14:18
*** baoli has quit IRC14:18
* jlibosva hides14:18
mesteryjlibosva: Heh, no that was the one! :)14:18
*** harshs has joined #openstack-meeting14:18
mesteryjlibosva: You were right ;)14:19
mesteryOK, last one: https://bugs.launchpad.net/neutron/+bug/146666314:19
openstackLaunchpad bug 1466663 in neutron "radvd exits -1 intermittently in test_ha_router_process_ipv6_subnets_to_existing_port functional test" [Medium,In progress] - Assigned to Sridhar Gaddam (sridhargaddam)14:19
haleybmestery: i looked at that metadata proxy failure last week with henry and got as far as noticing this: "wsgi starting up on http:///:t/"14:19
mesteryhaleyb: Ack, thanks for that!14:19
*** dbite has joined #openstack-meeting14:19
*** harshs has quit IRC14:19
haleybhost was / and port was :t14:19
mesteryLooks like 14666663 has an assignee and is "In Progress"14:19
*** puranamr has quit IRC14:19
mesteryhaleyb: Weird, thanks for digging into it a bit!14:20
SridharGmestery: I've submitted patch for the issue - https://review.openstack.org/#/c/193624/14:20
*** pratap has joined #openstack-meeting14:20
mestery#link https://review.openstack.org/#/c/193624/ Patch for 146666314:20
mesteryThanks SridharG!14:20
mesteryAny other bugs for the team to discuss?14:20
mesteryOK, we've got a lot of things to cover, so lets move along14:21
*** unicell has joined #openstack-meeting14:21
mestery#topic Understanding releases for networking-foo projects14:21
*** openstack changes topic to "Understanding releases for networking-foo projects (Meeting topic: networking)"14:21
*** baoli has joined #openstack-meeting14:22
mesteryThe tl;dr here is that these repos should follow semantic versioning similar to the server projects14:22
mestery#link https://review.openstack.org/#/q/topic:semver-releases+owner:%22Kyle+Mestery%22,n,z14:22
*** unicell1 has quit IRC14:22
mesteryI have patches out to fix networking-foo projects which were not doing semantic versioning14:22
mestery#info Before doing a release of your networking-foo repo, please talk to mestery so we can coordinate laying down a pre-version tag14:22
mesteryAlso, on the topic of stable branches for networking-foo projects14:23
mesteryIf you want a stable branch, please review this wiki page: https://wiki.openstack.org/wiki/StableBranch#Stable_branch_policy14:23
*** rkukura has joined #openstack-meeting14:23
mesteryAnd then talk to me and we'll get you one14:23
mesteryStable branches for networking-foo repos are nebulous at the moment14:23
dougwigThis only applies to projects that import neutron or implement one of its plugins, right?14:23
mesteryI'm working with ttx on this, but for now we'll allow stable branches for these on a request basis14:23
fawadkhaliqmestery: great thanks!14:23
mesterydougwig: Correct14:24
mesterydougwig: Actually, any library under openstack neutron14:24
*** lpeer has quit IRC14:24
mesteryAny questions on networking-foo release or stable branch items?14:24
*** lpeer has joined #openstack-meeting14:24
mestery#action mestery to email openstack-dev about networking-foo versioning and stable info14:25
mesteryI suspect many networking-foo reviewers are not here at this meeting :)14:25
mesteryOK, lets move along14:25
mestery#topic pecan reviews14:26
*** openstack changes topic to "pecan reviews (Meeting topic: networking)"14:26
mestery#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:feature/pecan+topic:bp/wsgi-pecan-switch,n,z14:26
mesteryAnyone intersted in reviewing the WSGI switch to pecan, please review those patches14:26
*** jungleboyj has joined #openstack-meeting14:26
mesteryI know kevinbenton and blogan would appreciate the reviews14:26
mesteryWe just merged master into feature/pecan yesterday14:27
*** comay has joined #openstack-meeting14:27
markmcclainI've been working through them14:27
mesterymarkmcclain: Thank you sir :)14:27
mesteryThe sooner we get reviews, the sooner we can fold this work back into master14:28
yongshenggong_what drives us to use new branch instead of master directly?14:28
mesteryIdeally, we would do that in a few weeks to give it some baking time14:28
mesteryyongshenggong_: Because the work was quite invasive and we wanted to stabilize it there first14:28
yongshenggong_mystery, ok got it14:28
mesteryAny other pecan related questions?14:29
mestery#topic Get Me a Network14:29
*** openstack changes topic to "Get Me a Network (Meeting topic: networking)"14:29
mesteryThanks to haleyb for driving this spec14:29
mestery#link https://review.openstack.org/#/c/184857/14:29
mesteryI posted a subsequent patch after talking to jaypipes about this.14:29
mestery#link https://review.openstack.org/#/c/196803/14:30
mesteryI'd encourage jaypipes and mordred to look at htat patch and haleyb's comments there14:30
*** amitgandhinz has joined #openstack-meeting14:30
mesteryI want to make sure "Get Me a Network" covers what jaypipes and mordred had in mind here14:30
*** neeti has joined #openstack-meeting14:30
haleybas there has been some confusion i would add14:30
mesteryhaleyb: ++14:30
*** baoli has quit IRC14:30
*** dboik has joined #openstack-meeting14:30
mesteryhaleyb: I think your last review comments sums it up nicely, if we can agree on that, then I think we can maybe make it clearer by abandoning my patch and proposing one with your language to make it clearer14:31
*** baoli has joined #openstack-meeting14:31
mesteryBut again, I'd like jaypipes and mordred to comment at this point14:31
mesteryAny other questions on "Get Me a Network"?14:31
*** pratap has quit IRC14:31
haleybi'd be happy with #1, so...14:31
*** pratap has joined #openstack-meeting14:32
*** lapalm has joined #openstack-meeting14:32
*** VanL has joined #openstack-meeting14:32
*** yatin has quit IRC14:32
mesteryTough crowd this morning, this meeting must be too serious for most people14:32
mesteryOK, lets move along14:32
mestery#topic Nova VIF Library14:32
*** openstack changes topic to "Nova VIF Library (Meeting topic: networking)"14:32
mestery#link https://review.openstack.org/#/c/193668/14:32
mesteryI'd like to highlight this spec in Nova14:32
mesterybeagles is working to get an exception for this14:32
*** baoli has quit IRC14:33
mesteryI encourage Neutron folks to review this one14:33
*** lapalm has left #openstack-meeting14:33
mesterysc68cal: Your eyes would be helpful here14:33
mesteryAmong many others14:33
*** baoli has joined #openstack-meeting14:33
*** banix has joined #openstack-meeting14:33
*** baoli has quit IRC14:33
beaglesfeel free to ping me if you have any questions on it14:33
sc68calmestery: yup - took a look and it LGTM14:33
mesterybeagles: How good are the changes of it getting an exception for Liberty?14:33
beaglesor just comment on the review :)14:34
neiljerramIf poss, I'd encourage reviewers not to drown in detail here - just indicate whether or not you support the overall idea, and leave detail to the code review14:34
mesteryneiljerram: +1000, agree with that sentiment14:34
*** baoli has joined #openstack-meeting14:34
beaglesmestery, I've no idea right now. I was going to reach out to john today to make sure I do the right things there14:34
mesterybeagles: Thank you!14:34
sc68calneiljerram: +++ - I read it mostly for content and it looks good - the overall effort seems reasonable14:34
*** dt_os has quit IRC14:34
*** sudipto has quit IRC14:35
* sc68cal is saving his paint brush for later14:35
mestery#topic Linux Bridge CI Job14:35
*** openstack changes topic to "Linux Bridge CI Job (Meeting topic: networking)"14:35
mesterysc68cal: Did you want to discuss this a bit more here?14:35
sc68calmestery: sure14:36
*** BharatK has quit IRC14:36
*** rossella_s has quit IRC14:36
sc68calI've seen some racey behavior in the failure logs - things like a bridge being deleted while a nova boot request is issued14:37
*** Apoorva has joined #openstack-meeting14:37
*** rossella_s has joined #openstack-meeting14:37
*** kebray has joined #openstack-meeting14:37
sc68calso I'm going to have to wrap my head around greenlet I guess and figure out why the bridges are being aggressively deleted14:37
mesterysc68cal: Sounds like a fun Friday night :)14:38
sc68calif anyone has any experience with the linux bridge mech driver, please don't be shy - otherwise I'll break out git blame and start pinging people :)14:38
sc68calsince I've got only a couple days worth of experience with the LB agent14:38
*** cbouch has quit IRC14:38
mesteryThanks for continuing to drive this work sc68cal!14:38
* beagles imagines a wall of shame in the offing14:39
*** irenab has joined #openstack-meeting14:39
*** mkolesni has quit IRC14:39
sc68calbeagles: I doubt that. I think it's mostly that the LB agent never has been put on a really really fast treadmill14:39
sc68callike the OVS agent has14:39
* beagles nods14:39
sc68calthat's it for me, I yield my time14:39
mesteryThanks sc68cal!14:39
mestery#topic Flow Classifier Work14:40
*** openstack changes topic to "Flow Classifier Work (Meeting topic: networking)"14:40
mestery#link https://etherpad.openstack.org/p/flow-classifier14:40
mesteryvikram: Did you want to discuss this a bit?14:40
*** amoturi has joined #openstack-meeting14:40
* mestery notes vikram may not be here at the moment but wanted to give him a chance here :)14:40
*** marrusl has quit IRC14:40
mesteryI think we may need to discuss flow classifiers next week14:41
mestery#topic Open Discussion14:41
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"14:41
hoangcxsc68cal: According to the discussion about "Security Group Logging" spec in the previous meeting. Yushiro has already registered NEW Packet logging API with RFW tags as the following link #link https://bugs.launchpad.net/neutron/+bug/146836614:41
openstackLaunchpad bug 1468366 in neutron "RFE - Packet logging API for Neutron" [Undecided,New] - Assigned to Yushiro FURUKAWA (y-furukawa-2)14:41
*** banix_ has joined #openstack-meeting14:41
*** banix has quit IRC14:41
*** banix_ is now known as banix14:41
xgermanreviews are needed for: #link https://review.openstack.org/#/c/139758/14:42
*** sudipto has joined #openstack-meeting14:42
mesteryxgerman: +100, flavors /cc dougwig14:42
markmcclainxgerman: cool.. will add it to the queue14:42
john-davidgereviews also needed for IPv6 Prefix Delegation #link https://review.openstack.org/#/c/15869714:43
hoangcxsc68cal: It needs you take a look and help to discuss14:43
sc68calhoangcx: looking14:43
sc68calhoangcx: based on the bug, sounds reasonable14:44
mestery#link https://review.openstack.org/#/c/139758/14:44
*** kebray has quit IRC14:44
hoangcxsc68cal: Thanks a lot.14:44
mestery#link https://review.openstack.org/#/c/15869714:44
sc68calhoangcx: the question i have is - where will the logged packets be placed?14:44
sc68calhow will users of the API retrieve the logs, or view?14:45
*** egallen_ has quit IRC14:45
*** dkusidlo has quit IRC14:45
hoangcxsc68cal: it will be logged to user log file14:45
*** rushiagr_away is now known as rushiagr14:45
sc68calhoangcx: what "user log file" ?14:45
*** fallenpegasus has joined #openstack-meeting14:46
hoangcxsc68cal: I will make more description about this in the lunchpad14:46
hoangcxsc68cal: Do you have any advice for this?14:46
*** lkarm has left #openstack-meeting14:46
yongshenggong_hoangcx: I think it will be implemented in the form  iptables -j log action14:47
*** margaret__ has joined #openstack-meeting14:47
*** vikram_ has joined #openstack-meeting14:47
hoangcxYeah. That's right14:47
sc68calI put a comment in the spec- you need a way to expose this to the user of the API14:47
sc68calmy suggestion would be to use the Object Storage API14:48
sc68calthat's what it's there for14:48
sc68calcould have something like a storage_url - and then they could put a swift URL in14:48
hoangcxsc68cal: Sure. Thank you. I will check it and expose14:48
markmcclainsc68cal: even then you've now got compute nodes log shipping via swift... not certain how that will sit with some of the more paranoid security environments14:49
*** cbouch has joined #openstack-meeting14:49
mesterymarkmcclain: +10014:49
sc68caltrue - but if we have a storage_url attribute we can have multiple handlers - swift:// or file://14:50
sc68calor what hae you14:50
sc68cal*have you14:50
mesteryLets continue this particular painting on the RFE bug :)14:51
mesteryOK, thanks folks!14:51
neiljerramcarl_baldwin is doing interesting and much appreciated work on L3-only networks (https://review.openstack.org/#/c/196812/3).  I'd like to thank him for that, and flag this work to anyone else who might be interested in it.  (Also, of course, this is mostly being discussed in the L3 subteam, and if you are interested, please go there too!)14:51
mestery#link https://review.openstack.org/#/c/196812/314:51
mesteryneiljerram: Thanks for the link and reminder there! :)14:51
pc_mAnyone tried stacking from scratch with DevStack today using reclone? I'm seeing Horizon failure saying No module i18n.14:51
carl_baldwinneiljerram: thanks14:51
*** pgbridge has joined #openstack-meeting14:51
mesteryOK, we'll see you all in #openstack-neutron, the ML, and the internet ;)14:51
*** openstack changes topic to "OpenStack CI is down due to hard drive failures"14:51
openstackMeeting ended Tue Jun 30 14:51:52 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-06-30-14.00.html14:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-06-30-14.00.txt14:51
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-06-30-14.00.log.html14:51
*** john-davidge has left #openstack-meeting14:52
mesterypc_m: Best to move to #openstack-neutron now :)14:52
pc_mmestery: OK14:52
*** regXboi has left #openstack-meeting14:52
*** pc_m has left #openstack-meeting14:52
*** oanufrie1 has joined #openstack-meeting14:52
*** subscope has joined #openstack-meeting14:52
hoangcxThanks! Bye14:52
*** doude has quit IRC14:52
*** absubram has left #openstack-meeting14:52
*** yongshenggong_ has quit IRC14:53
*** dkusidlo has joined #openstack-meeting14:53
jaypipesmestery: I will certainly review the second get me a network proposal today. it's meeting day for me (what day isn't?) but I'll try to get to it by afternoon.14:53
*** irenab has quit IRC14:53
*** marrusl has joined #openstack-meeting14:53
*** ChanServ changes topic to "Open Discussion (Meeting topic: networking)"14:53
-openstackstatus- NOTICE: The log volume was repaired and brought back online at 14:00 UTC. Log links today from before that time may be missing, and changes should be rechecked if fresh job logs are desired for them.14:53
mesteryjaypipes: I hear you on both fronts, and thanks! :)14:54
*** galstrom_zzz is now known as galstrom14:55
*** arvinchou_ has joined #openstack-meeting14:55
*** e0ne is now known as e0ne_14:55
*** arvinchou_ has left #openstack-meeting14:56
*** hrou has quit IRC14:56
*** hrou has joined #openstack-meeting14:57
*** fawadkhaliq has quit IRC14:58
*** jaypipes has quit IRC14:58
*** garthb__ has joined #openstack-meeting14:58
*** garthb has joined #openstack-meeting14:58
*** e0ne_ is now known as e0ne14:58
*** e0ne is now known as e0ne_14:59
*** doude has joined #openstack-meeting14:59
*** e0ne_ is now known as e0ne14:59
n0ano#startmeeting nova_scheduler14:59
openstackMeeting started Tue Jun 30 14:59:55 2015 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.14:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:59
*** openstack changes topic to " (Meeting topic: nova_scheduler)"14:59
openstackThe meeting name has been set to 'nova_scheduler'14:59
*** ub has quit IRC15:00
n0anoanyone here to talk about the scheduler?15:00
*** maishsk has quit IRC15:00
*** banix_ has joined #openstack-meeting15:00
*** annp has quit IRC15:01
*** hoangcx has quit IRC15:01
n0anoI was thinking it was going to just be me today (easier to come to decisions :-)15:02
*** irenab has joined #openstack-meeting15:03
*** banix has quit IRC15:03
*** banix_ is now known as banix15:03
*** PaulMurray has joined #openstack-meeting15:03
n0anolet's start, hopefully it'll be quick today15:03
edleafen0ano: sorry, but I'm on a call for another meeting :(15:03
edleafeso I might be slow in responding15:03
n0anoedleafe, you get all the ARs :-)15:03
n0ano#topic new meeting time15:04
edleafeof course15:04
*** openstack changes topic to "new meeting time (Meeting topic: nova_scheduler)"15:04
edleafeResults: http://i.imgur.com/aPmIwLi.png15:04
*** lazy_prince has quit IRC15:04
n0anoaccording to the doodle 1 hour earlier (1400UTC) on Mon. seems to work, any objections?15:04
*** fawadkhaliq has joined #openstack-meeting15:04
bauzasPaulMurray: you weren't voting, OK for you ?15:05
PaulMurraybauzas, sorry - been out of touch15:06
n0anoPaulMurray, so is the new time OK for you?15:06
bauzasPaulMurray: np, so the question was, Mondays 1400UTC ok with you ?15:06
bauzas(and lxsli as well)15:06
lxsliworks for me15:06
PaulMurraybauzas, more or less15:06
bauzasok, n0ano, I guess you can put an #agreed there :)15:07
*** praveens1 has quit IRC15:07
n0ano#agreed new time 1400UTC Mondays15:07
n0ano#action n0ano to update the wiki's and send a mail out to the dev list on this15:07
*** praveens has joined #openstack-meeting15:08
*** nadeem has quit IRC15:08
bauzasn0ano: you also have to do a commit for the global page15:08
*** irenab has quit IRC15:08
*** asselin__ has joined #openstack-meeting15:08
n0anobauzas, yeah, there are multiple administrivias I'll have to do, should be OK15:09
bauzasn0ano: http://git.openstack.org/cgit/openstack-infra/irc-meetings/tree/15:09
*** rkukura has left #openstack-meeting15:09
n0anoI have to do ical's for the new schedule which is new but I'll deal with it.15:09
*** _nadya_ has quit IRC15:09
bauzasn0ano: if you don't feel comfortable, I can do it15:10
bauzasn0ano: I already made a change for it15:10
n0anobauzas, I'll ping you if I have a problem but it should be OK15:10
*** arvinchou_ has joined #openstack-meeting15:10
*** jlibosva has left #openstack-meeting15:10
*** oanufrie1 has left #openstack-meeting15:10
bauzasn0ano: coolness15:10
*** _nadya_ has joined #openstack-meeting15:10
*** SridharG has left #openstack-meeting15:10
n0ano#topic Liberty spcecs15:10
*** openstack changes topic to "Liberty spcecs (Meeting topic: nova_scheduler)"15:10
bauzasn0ano: saw our recent agreements ?15:10
n0anoaccording to the tracking page https://etherpad.openstack.org/p/liberty-nova-priorities-tracking we only have one priorty spec that is still open15:11
*** scheuran has quit IRC15:11
bauzasedleafe's one was not needed15:11
n0anoI lied, looks like there are 215:11
bauzashence john's -215:11
bauzasn0ano: eh eh15:12
*** asselin_ has quit IRC15:12
bauzasn0ano: thanks for introducing https://review.openstack.org/#/c/190322/7/specs/liberty/approved/servicegroup-api-control-plane.rst,cm15:12
bauzasn0ano: I was about to discuss on it for the open discussion15:12
bauzasbut I can do it now15:12
n0anogo ahead,no reason to wait15:12
*** ihrachyshka has quit IRC15:12
bauzassince it's claiming for the sched prio15:12
bauzasso, I'll leave a change speak for itself15:13
*** hashar has quit IRC15:13
bauzas#link https://review.openstack.org/#/c/195559/15:13
*** xyang1 has joined #openstack-meeting15:13
bauzasso, my comment here is that I wanted to see the subteam opinion for it15:14
bauzasmy point is15:14
bauzas1/ I don't like specs using the scheduler prio as a placeholder for getting more room for being merged15:14
*** _nadya_ has quit IRC15:14
*** dkusidlo has quit IRC15:14
n0anobauzas, +115:15
bauzas2/ the SG API change is technically modifying something out of the scheduler and can benefit more than the scheduler15:15
bauzasso, while it's definitely something worth being done15:15
bauzasand I'm a huge fan of the spec15:15
*** amoturi has quit IRC15:16
bauzasI just think it's better to explain to johnthetubaguy and the nova community that this is not a 'scheduler' prio spec, but is still considered as something important and deserves an exception15:16
edleafeIf it isn't tied to the scheduler efforts, it shouldn't use the scheduler priority, IMO15:16
*** jruano has joined #openstack-meeting15:16
bauzasso, given that, could we make a vote ?15:16
edleafeit should stand on its own15:16
bauzasedleafe: that's my point15:16
edleafebauzas: ack15:16
n0anoI think, here, we're in violent agreement, this is a good idea but it is not a scheduler thing15:16
*** belmoreira has quit IRC15:17
edleafebauzas: I'm agreeing with you.15:17
bauzasn0ano: let's do an official vote15:17
edleafebauzas: probably the first time ever :)15:17
bauzasn0ano: give me the chair rights15:17
bauzas#chair bauzas15:17
bauzasand I'll pass to the vote15:17
n0anobauzas, if you insist :-)15:17
n0ano#chair bauzas15:17
openstackCurrent chairs: bauzas n0ano15:17
bauzas#startvote Do you consider that https://review.openstack.org/#/c/190322/ is a 'scheduler' priority spec ? yes or no15:18
openstackBegin voting on: Do you consider that https://review.openstack.org/#/c/190322/ is a 'scheduler' priority spec ? Valid vote options are yes, or, no.15:18
openstackVote using '#vote OPTION'. Only your last vote counts.15:18
bauzas#vote no15:18
n0ano#vote no15:18
lxsli#vote or15:18
edleafe#vote no15:18
*** amoturi has joined #openstack-meeting15:18
PaulMurray#vote no15:18
bauzaslxsli: lol, you found a bug15:19
edleafelxsli: smartass :-P15:19
openstackVoted on "Do you consider that https://review.openstack.org/#/c/190322/ is a 'scheduler' priority spec ?" Results are15:19
openstackor (1): lxsli15:19
openstackno (4): bauzas, PaulMurray, n0ano, edleafe15:19
* n0ano wonders what an `or' vote means15:19
bauzasokay, I'll remove my -W and provide the result of the vote as a change comment15:19
PaulMurrayit counts "or" - ha - I bet we could vote anything15:19
PaulMurraydidn't know that15:19
bauzasI sould have said yes, no :)15:20
*** tsekiyama has joined #openstack-meeting15:20
PaulMurrayhe would have put :)15:20
n0ano`and' I would understand but `or' ...15:20
bauzasanyway, I'm done for that15:20
bauzasso, last point about specs15:20
n0anobauzas, NP and wew had some fun with it also15:21
n0anobauzas, go ahead15:21
bauzasI urge you to review https://review.openstack.org/#/c/179224/15:21
bauzasI consider it as a needed behavioural change for making all the scheduler queries consistent15:21
*** belmoreira has joined #openstack-meeting15:21
bauzasand it also fixes a bunch of bugs and misunderstandings15:21
n0anogood one, I'll review this after noon (after I climb out of the hole I created by effectively taking 2 weeks off)15:22
bauzasthat's it for me, RequestSpec implem is on its way15:23
n0anoanything else on specs?15:23
n0anothen, moving on15:24
n0ano#topic opens15:24
*** openstack changes topic to "opens (Meeting topic: nova_scheduler)"15:24
n0anoanything new?15:24
edleafeI'll re-review it later, too. Then I'm out for the rest of the week15:24
xyhuanghi, any chance we can look at this nit again:15:24
xyhuanga brief spec here:15:25
n0anooh yeah, the 4th is coming, I always forget about hoidays15:25
lxsliNova midcycle soon15:25
*** yamahata has quit IRC15:26
n0anoxyhuang, tnx for mentioning these, we'll try and review them15:26
edleafexyhuang: I still don't think that this change requires a spec15:26
xyhuangbauzas: i feel that it’s trivial impact on existing works because15:26
xyhuangrequested_networks are passed from outside from user, not something inside nova-compute15:26
bauzasedleafe: I still think it deserves a spec because it changes the interface between the scheduler and Nova15:26
xyhuanglxsli: i checked out the resource object work as you mentioned, and i think it is not affected, at least atm.15:27
*** armax has joined #openstack-meeting15:27
bauzasedleafe: and also because it's worth discussing on how we pass this information to the scheduler15:27
lxslixyhuang: OK I can take a longer look, only glanced last time15:27
bauzasxyhuang: your both changes are on top of my review queue, I should comment them soon15:27
xyhuanglxsli: i definitely agree though if the networks will be tracked in resources but that’d be another story i guess…15:28
xyhuangbauzas: thanks :) glad to know what you think15:28
bauzasxyhuang: tbh, I need a bit of time to see if passing thru filt_properties is a good idea or not15:29
bauzasmoving on ?15:29
xyhuangbauzas: i guess fltr_properties is also possible but IMO it's easier to pass in the req_spec15:30
*** bradjones has quit IRC15:30
bauzasxyhuang: lemme comment that out in your spec :)15:30
n0anolxsli, in re midcycle - I plan to be there, who else is coming?15:30
xyhuangbauzas: thx!15:30
bauzasn0ano: I won't15:30
bauzasI heard about PaulMurray and lxsli coming15:31
bauzasso, edleafe will wait for his 2 beers :(15:31
n0anobauzas, bummer, RH is making money, what's their excuse :-)15:31
lxsliyes I'll be there, not sure PaulMurray will15:31
*** changbl has joined #openstack-meeting15:31
edleafeI'll be there, and thirsty15:31
*** vikram_ has left #openstack-meeting15:31
bauzasn0ano: well, that's not because you earn money that you can expense much than what you earn :)15:32
*** elo has joined #openstack-meeting15:32
bauzasn0ano: so, I understand the reasons15:32
*** bradjones has joined #openstack-meeting15:32
*** bradjones has quit IRC15:32
*** bradjones has joined #openstack-meeting15:32
bauzasexpense more* of course15:32
PaulMurraybauzas, I'm ont coming - I have holiday planned15:32
*** egallen has joined #openstack-meeting15:32
bauzasPaulMurray: and people complain about French holidays...15:32
PaulMurraybauzas, strangely I will be in France15:33
*** nmagnezi has quit IRC15:33
n0anoPaulMurray, how - ironic :-)15:33
bauzasPaulMurray: so, you'll be acting like locals :)15:33
PaulMurrayso it is sort of a french holiday15:33
*** puranamr has joined #openstack-meeting15:34
bauzasPaulMurray: I suppose you won't go to Grenoble :p15:34
*** lpeer has quit IRC15:34
bauzasanyway, that's off-topic15:34
n0anoseriously, we should think about any topics we want to discuss at the mid-cycle, obviously the oustanding Liberty spcs/bps, but anything else we care about15:34
*** marun has quit IRC15:34
bauzasn0ano: I should remotely attend the midcycle tho15:35
bauzasn0ano: providing there would be some connectivity in there15:35
bauzasprovided even15:35
n0anobauzas, that'll help but good luck hearing everyone in the room15:35
bauzasn0ano: I'm not that worried :)15:35
*** puranamr_ has joined #openstack-meeting15:36
*** carl_baldwin has quit IRC15:36
*** puranamr has quit IRC15:36
*** DericHorn-HP has joined #openstack-meeting15:36
n0anoso think about the mid-cycle and we can discuss that at the next meeting (on Mon.)15:36
*** enikanorov2_ has quit IRC15:36
n0anoso, anything else for today?15:37
edleafen0ano: I get back very late Sunday night, so I might not be on next Monday15:37
*** abregman has quit IRC15:37
n0anoedleafe, NP, get some sleep15:37
n0anoI'm hearing crickets15:38
edleafen0ano: sleep? nah. I'm worrying about plane delays15:38
*** zhhuabj_ has quit IRC15:38
*** enikanorov2 has joined #openstack-meeting15:38
n0anoedleafe, why worry, you `never` miss a connection :-)15:39
* n0ano like everyone, has some interesting missed connection stories15:39
n0anoanyway, I think we're done for today15:39
*** pbourke has quit IRC15:40
n0anotnx everyone, talk to you soon and do those reviews15:40
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"15:40
openstackMeeting ended Tue Jun 30 15:40:23 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2015/nova_scheduler.2015-06-30-14.59.html15:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2015/nova_scheduler.2015-06-30-14.59.txt15:40
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2015/nova_scheduler.2015-06-30-14.59.log.html15:40
*** pbourke has joined #openstack-meeting15:40
bauzasn0ano: thnaks15:40
bauzasthanks even15:40
n0anoI like thnaks, it has an interesting ring :-)15:41
*** _nadya_ has joined #openstack-meeting15:41
*** PrashantS has joined #openstack-meeting15:42
*** singleth_ has quit IRC15:43
*** alop has joined #openstack-meeting15:44
*** amoturi has quit IRC15:47
*** neeti has quit IRC15:47
*** temujin has joined #openstack-meeting15:48
*** geoffarnold has joined #openstack-meeting15:48
*** amrith is now known as _amrith_15:48
*** nadeem has joined #openstack-meeting15:48
*** xyhuang has quit IRC15:49
*** zhhuabj has joined #openstack-meeting15:49
*** _nadya_ has quit IRC15:49
*** abregman has joined #openstack-meeting15:50
*** belmoreira has quit IRC15:50
*** vivek-eb_ has quit IRC15:51
*** xyhuang has joined #openstack-meeting15:53
*** sdake has joined #openstack-meeting15:54
*** Gerald_K has quit IRC15:54
*** sudipto has quit IRC15:54
*** mrutkows has joined #openstack-meeting15:54
*** achanda has joined #openstack-meeting15:56
*** sdake_ has joined #openstack-meeting15:56
*** kylek3h has quit IRC15:57
*** unicell has quit IRC15:58
*** nadeem has quit IRC15:58
*** asselin__ has quit IRC15:58
*** nadeem has joined #openstack-meeting15:59
*** achanda has quit IRC16:00
*** sdake has quit IRC16:00
*** otter768 has joined #openstack-meeting16:02
*** PaulMurray has left #openstack-meeting16:03
*** ygbo has quit IRC16:04
*** jjfreric has joined #openstack-meeting16:04
*** jjfreric has left #openstack-meeting16:04
*** fzdarsky has quit IRC16:04
*** spzala has joined #openstack-meeting16:04
*** jlanoux has quit IRC16:05
*** leeantho has joined #openstack-meeting16:05
*** sarob has joined #openstack-meeting16:06
*** otter768 has quit IRC16:07
*** ajiang has quit IRC16:09
*** bhakta has quit IRC16:10
*** arnaud____ has joined #openstack-meeting16:10
*** mpaolino_ has quit IRC16:11
*** dannywilson has joined #openstack-meeting16:11
*** carl_baldwin has joined #openstack-meeting16:11
*** pelix has quit IRC16:12
*** praveens1 has joined #openstack-meeting16:12
*** fallenpegasus has quit IRC16:12
*** dannywilson has quit IRC16:13
*** praveens has quit IRC16:14
*** dannywilson has joined #openstack-meeting16:14
*** ajiang has joined #openstack-meeting16:15
*** bhakta has joined #openstack-meeting16:15
*** weshay has quit IRC16:16
*** xyhuang has left #openstack-meeting16:17
*** singlethink has joined #openstack-meeting16:18
*** rainya has quit IRC16:19
*** beekneemech is now known as bnemec16:19
*** weshay has joined #openstack-meeting16:19
*** praveens1 has quit IRC16:21
*** KunalGandhi has joined #openstack-meeting16:21
*** devvesa has quit IRC16:22
*** e0ne is now known as e0ne_16:23
*** numan has joined #openstack-meeting16:25
*** rainya has joined #openstack-meeting16:25
*** jaypipes has joined #openstack-meeting16:26
*** arvinchou_ has quit IRC16:26
*** _amrith_ is now known as amrith16:26
*** unicell has joined #openstack-meeting16:28
*** praveens has joined #openstack-meeting16:28
*** vivek-ebay has joined #openstack-meeting16:29
*** dontalton has joined #openstack-meeting16:29
*** baoli has quit IRC16:29
*** doude has quit IRC16:30
*** john-a-joyce has joined #openstack-meeting16:30
*** baoli_ has joined #openstack-meeting16:31
*** vivek-eb_ has joined #openstack-meeting16:33
*** e0ne_ has quit IRC16:34
*** john_a_joyce has quit IRC16:34
*** yatin has joined #openstack-meeting16:35
*** achanda has joined #openstack-meeting16:35
*** e0ne has joined #openstack-meeting16:36
*** aimon_ has quit IRC16:37
*** vivek-ebay has quit IRC16:37
*** jckasper has quit IRC16:39
*** Aditya has joined #openstack-meeting16:40
*** Aditya has quit IRC16:40
*** egallen has quit IRC16:41
*** lufix has joined #openstack-meeting16:46
*** yassine_ has quit IRC16:47
*** fallenpegasus has joined #openstack-meeting16:49
*** egallen has joined #openstack-meeting16:52
*** ildikov has quit IRC16:53
*** praveens has left #openstack-meeting16:53
*** hichihara has quit IRC16:54
*** lufix has quit IRC16:54
*** fawadkhaliq has quit IRC16:57
*** marun has joined #openstack-meeting16:57
*** geoffarnold has quit IRC16:58
*** kylek3h has joined #openstack-meeting16:58
*** geoffarnold has joined #openstack-meeting16:58
*** abregman has quit IRC16:59
*** derekh has quit IRC16:59
*** lapalm has joined #openstack-meeting16:59
*** matrohon has quit IRC16:59
*** ogelbukh1 has quit IRC16:59
*** ociuhandu has quit IRC17:00
*** sballe has joined #openstack-meeting17:02
*** thangp has quit IRC17:02
*** ogelbukh1 has joined #openstack-meeting17:03
*** lapalm has quit IRC17:03
*** Swami has joined #openstack-meeting17:04
*** adrian-hoban has quit IRC17:04
*** fawadkhaliq has joined #openstack-meeting17:04
*** neelashah1 has quit IRC17:05
*** numan has quit IRC17:05
*** DericHorn-HP has quit IRC17:05
*** e0ne has quit IRC17:05
*** mrmartin_ has joined #openstack-meeting17:05
*** neelashah1 has joined #openstack-meeting17:06
*** mrmartin has quit IRC17:06
*** samueldmq has quit IRC17:08
*** samueldmq has joined #openstack-meeting17:08
*** aimon has joined #openstack-meeting17:10
*** baoli_ has quit IRC17:10
*** banix has quit IRC17:11
*** thangp has joined #openstack-meeting17:14
*** egallen has quit IRC17:14
*** mpaolino has quit IRC17:15
*** egallen has joined #openstack-meeting17:17
*** sdake has joined #openstack-meeting17:18
*** egallen has quit IRC17:21
*** sdake_ has quit IRC17:21
*** egallen has joined #openstack-meeting17:24
*** rbak has joined #openstack-meeting17:24
*** dguerri is now known as dguerri`17:25
*** margaret__ has quit IRC17:27
*** annegentle has quit IRC17:28
*** toscalix has quit IRC17:29
*** dannywilson has quit IRC17:29
*** neelashah1 has quit IRC17:29
*** egallen has quit IRC17:29
*** htruta_ has joined #openstack-meeting17:29
*** rbak has quit IRC17:31
*** fawadkhaliq has quit IRC17:33
*** nadeem has quit IRC17:33
*** ityaptin has quit IRC17:33
*** nadeem has joined #openstack-meeting17:34
*** egallen has joined #openstack-meeting17:35
*** singleth_ has joined #openstack-meeting17:36
*** marrusl has quit IRC17:36
*** baoli has joined #openstack-meeting17:37
*** egallen has quit IRC17:38
*** baoli has quit IRC17:38
*** achanda_ has joined #openstack-meeting17:38
*** dboik has quit IRC17:39
*** baoli has joined #openstack-meeting17:39
*** singlethink has quit IRC17:40
*** spzala has quit IRC17:40
*** achanda has quit IRC17:40
*** vnod has joined #openstack-meeting17:41
*** annegentle has joined #openstack-meeting17:41
*** achanda has joined #openstack-meeting17:42
*** jckasper has joined #openstack-meeting17:42
*** neelashah1 has joined #openstack-meeting17:42
*** nadeem has quit IRC17:43
*** irenab has joined #openstack-meeting17:43
*** jecarey has quit IRC17:43
*** novas0x2a|laptop has joined #openstack-meeting17:43
*** pradk has joined #openstack-meeting17:44
*** kylek3h has quit IRC17:44
*** achanda_ has quit IRC17:44
*** mrmartin_ has quit IRC17:45
*** sdake_ has joined #openstack-meeting17:47
*** elo1 has joined #openstack-meeting17:47
*** elo2 has joined #openstack-meeting17:48
*** elo2 has quit IRC17:48
*** elo2 has joined #openstack-meeting17:48
*** lsmola has quit IRC17:49
*** fawadkhaliq has joined #openstack-meeting17:50
*** marekd has joined #openstack-meeting17:50
*** ivar-lazzaro has joined #openstack-meeting17:50
*** sdake has quit IRC17:50
*** sdake_ is now known as sdake17:50
*** elo has quit IRC17:51
*** jckasper has quit IRC17:51
*** ihrachyshka has joined #openstack-meeting17:52
*** elo1 has quit IRC17:52
*** vnod has quit IRC17:52
*** cbouch has quit IRC17:53
*** neelashah has quit IRC17:53
*** mrmartin has joined #openstack-meeting17:56
*** jecarey has joined #openstack-meeting17:56
*** xingchao_ has joined #openstack-meeting17:56
*** ijw has quit IRC17:57
*** enikanorov2 has quit IRC17:57
*** egallen has joined #openstack-meeting17:58
*** baoli has quit IRC17:58
*** pvaneck has joined #openstack-meeting17:58
*** e0ne has joined #openstack-meeting17:58
*** yamahata has joined #openstack-meeting17:59
*** baoli has joined #openstack-meeting17:59
*** roxanaghe_ has joined #openstack-meeting17:59
*** david8hu has joined #openstack-meeting17:59
*** shaleh has joined #openstack-meeting18:00
*** lapalm has joined #openstack-meeting18:00
*** browne has joined #openstack-meeting18:00
morganfainbergajayaa, 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, wanghong https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:00
morganfainbergit's about that time.18:00
*** neelashah has joined #openstack-meeting18:01
*** dannywilson has joined #openstack-meeting18:01
*** henrynash has joined #openstack-meeting18:01
*** jamielennox has joined #openstack-meeting18:01
samueldmqolá :)18:01
* morganfainberg waits for a few more18:01
morganfainbergthis doesn't look like a quorum yet18:02
morganfainbergthere we go18:02
shalehI believe gyee is in the car at the moment18:02
morganfainbergroxanaghe_ / david8hu: you should throw something at gyee18:02
david8huLooking for the remote eject button :)18:02
*** rbak has joined #openstack-meeting18:02
morganfainbergok. probably good enough...18:02
*** otter768 has joined #openstack-meeting18:03
morganfainberg#startmeeting keystone18:03
openstackMeeting started Tue Jun 30 18:03:06 2015 UTC and is due to finish in 60 minutes.  The chair is morganfainberg. Information about MeetBot at http://wiki.debian.org/MeetBot.18:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:03
*** openstack changes topic to " (Meeting topic: keystone)"18:03
openstackThe meeting name has been set to 'keystone'18:03
morganfainbergso ... lbragstad you here?18:03
*** cbouch has joined #openstack-meeting18:03
*** breton has joined #openstack-meeting18:03
morganfainbergcan come back to tht18:03
lbragstadmorganfainberg: yes sir18:03
morganfainbergoh bug report then18:03
morganfainberg#topic Keystone Bug Report18:03
*** openstack changes topic to "Keystone Bug Report (Meeting topic: keystone)"18:03
morganfainberglbragstad: o/18:03
dstanekHere now18:03
*** neelashah1 has quit IRC18:03
lbragstadmost everything on list weeks list looks to be triaged18:04
lbragstadso, that's a plus!18:04
*** Shrews has joined #openstack-meeting18:04
*** lapalm has quit IRC18:04
*** e0ne is now known as e0ne_18:04
lbragstadI think there are only a couple that haven't been triaged, but I can go through those18:04
*** Shrews has left #openstack-meeting18:04
lbragstadother than that, bugs looks pretty tame this week18:05
*** haneef has joined #openstack-meeting18:05
bknudsonis oslo.policy included in the list?18:05
morganfainbergbknudson: no18:05
lbragstadbknudson: it can be18:05
bknudsonand other oslo libs that we support18:05
morganfainbergoslo.policy is an oslo project18:05
morganfainbergbut it probably should be in our list18:05
morganfainbergwe're the ones who mostly look at it18:05
morganfainbergbknudson: like oslo.cache18:05
*** jlanoux has joined #openstack-meeting18:05
lbragstadI'll take the action item to add it to our bug report18:06
lbragstadso we have it on our radar (for people who use that report)18:06
morganfainberg#action lbragstad to add oslo.policy and oslo.cache to keystone bug report18:06
*** geoffarnold has quit IRC18:06
morganfainbergyay for relatively under control bugs18:06
morganfainberg#topic Making devstack v3 friendly18:07
*** openstack changes topic to "Making devstack v3 friendly (Meeting topic: keystone)"18:07
morganfainbergjamielennox: o/18:07
*** e0ne_ is now known as e0ne18:07
jamielennoxoh - right, umm there is a chain of reviews up for devstack that move everything over to v3 CRUD then v3 auth18:07
*** otter768 has quit IRC18:07
marekdjamielennox: link please18:08
jamielennoxstarting https://review.openstack.org/#/c/186681/818:08
*** ajayaa_ has quit IRC18:08
bknudsonit's got -118:08
jamielennoxdamn, first one has a -1 i thought that was like 4 patches in18:08
*** kgroves has joined #openstack-meeting18:08
jamielennoxoh - wait18:09
*** ivar-laz_ has joined #openstack-meeting18:09
jamielennoxthat's cause the first couple got merged :)18:09
*** ivar-laz_ has quit IRC18:09
*** ivar-lazzaro has quit IRC18:09
jamielennoxso was starting https://review.openstack.org/#/c/186678/418:09
*** sbalukoff has joined #openstack-meeting18:10
*** ivar-lazzaro has joined #openstack-meeting18:10
samueldmqjamielennox: https://review.openstack.org/#/q/status:open+branch:master+topic:keystonev3,n,z18:10
bknudsonI've got some changes up for using clouds.yaml -- https://review.openstack.org/#/c/195786/ -- might make this a little easier18:10
jamielennoxthere is a fix for glance -> swift to use v3 https://review.openstack.org/#/c/193422/18:10
jamielennoxand i think when those two things happen we can get devstack to run with v2 disabled18:10
*** lhcheng_ has joined #openstack-meeting18:11
*** spzala has joined #openstack-meeting18:11
jamielennoxso not a tempest run, but at least get to the point where our v3 only gate job can start telling us things18:11
samueldmqjamielennox: ++18:11
*** vnod has joined #openstack-meeting18:11
morganfainbergjamielennox: building devstack with v3 only apis18:11
morganfainbergis a huge setp18:11
*** yatin has quit IRC18:11
*** Steve_droid has joined #openstack-meeting18:12
morganfainbergif we are at least that far - then we're not going to have to fight too hard on the tempest side really18:12
Steve_droidGonna be typing slowly18:12
jamielennoxmorganfainberg: right, i figure we can find and fix real tempest bugs quickly, just hopefully it doesn't uncover too many mistakes in services18:13
*** annegentle has quit IRC18:13
david8huI thought samueldmq is done with migrating tempest to keystone v3? :)18:14
*** ericksonsantos has joined #openstack-meeting18:14
samueldmqdavid8hu: no, I created a devstack gate job with v2 disabled, which is something jamielennox is using :)18:14
david8husamueldmq, cool.  I see.18:15
samueldmqdavid8hu: and will be used to detect issues with services using v3 once devstack can properly set up resources and tempest can run18:15
bknudsonsamueldmq: devstack-gate job runs tempest?18:15
*** tellesnobrega_ has joined #openstack-meeting18:15
samueldmqbknudson: it will, once devstack can set up its own resources using v3 only18:15
samueldmqbknudson: which is the step jamielennox's right now18:15
samueldmqbknudson: after that step we will be able to check for individual issues on services/clients18:16
jamielennoxbknudson: there is an experimental job on devstack, and on tempest from memory for devstack gate to run with v2 disabled18:16
samueldmqjamielennox: correct me if I am wrong :)18:16
*** annegentle has joined #openstack-meeting18:16
*** Sukhdev_ has joined #openstack-meeting18:16
samueldmqyeah, for example http://logs.openstack.org/84/186684/4/experimental/check-tempest-dsvm-neutron-identity-v3-only-full/ca5f300/18:17
*** moha_hunt has joined #openstack-meeting18:17
*** ttrifonov is now known as zz_ttrifonov18:17
*** e0ne is now known as e0ne_18:18
jamielennoxbknudson: so in addiition to clouds.yaml i need to figure out how to fix the accrc files, i had some work done that way but i don't know if i posted it for review18:18
*** ildikov has joined #openstack-meeting18:18
*** rushiagr is now known as rushiagr_away18:18
*** olaph has joined #openstack-meeting18:18
bknudsonaccrc? how many files do we need?18:18
jamielennoxor know if it would be acceptable just to switch everything over to v3 like that18:18
*** puranamr_ has quit IRC18:18
jamielennoxbknudson: i don't know, at the moment the way accrc files are generated it loops over every project and creates a file for every user with a role in that project18:19
jamielennoxi expect if i suddenly make those files v3 it will break people18:19
bknudsondelete those files18:20
jamielennoxwould love to18:20
*** tellesnobrega_ has quit IRC18:20
jamielennoxi expect for the last patch in that chain where we actually turn over to v3 by default we will break some people anyway18:20
jamielennoxmay need an announcement18:20
jamielennoxi'll figure that out with the devstack folks18:20
jamielennoxanyway - i think that's all18:21
jamielennox(not sure how this topic got in the meeting points)18:21
*** achanda has quit IRC18:21
Steve_droidI wonder how many ppl rely on the accrc file18:21
Steve_droid++bkudson, delete them18:21
marekdthese are openrc files so you source them and use devstack?18:22
bknudsonuse clouds.yaml instead18:22
jamielennoxmarekd: not really openrc18:22
jamielennoxbut when you finish devstack you get like accrc/admin/admin that you can source18:22
Steve_droidMarked yes18:22
*** e0ne_ is now known as e0ne18:23
morganfainbergso it sounds like we have some cleanup to do18:23
morganfainbergon devstack and some research18:23
morganfainbergbut the work is moving forward18:23
*** iurygregory has joined #openstack-meeting18:23
morganfainbergjamielennox: maybe we need to make v3 versions of those files to start with18:24
morganfainbergas crappy as that is18:24
morganfainbergwe should bug the devstack folks on that front18:24
jamielennoxi guess the issue is no-one really knows who relies on current behaviour18:24
*** gyee has joined #openstack-meeting18:24
morganfainbergso lets plan to make v3 versions of those18:24
bknudsondoes devstack say they have a stable API?18:24
morganfainbergbknudson: no18:25
bknudsonit's supposed to be opionated18:25
jamielennoxgiven that we wont actually turn v2 off in devstack for quite a while i was thinking i could just add some domain properties to those files18:25
morganfainbergbknudson: we could just make v3 versions18:25
jamielennoxit won't affect us running v3 only gate jobs for quite a while18:25
bknudsonso if it's our opinion that you don't use accrc files then don't make them18:25
morganfainbergor make v2 versions?18:25
Steve_droidIf someone aside from infra relies on devstack they are going to have a bad time18:25
morganfainbergif v2 is enabled18:25
morganfainberganyway. jamielennox check w/ dtroyer and ianw and the other devstack folks18:25
*** htruta_ has quit IRC18:26
morganfainbergbut i'd opt for just making them v3 rc files18:26
*** xingchao_ has quit IRC18:26
jamielennoxSteve_droid: right - we are already at the point with plugins where i'm not sure if the changes i've made so far are going to end up breaking people18:26
morganfainbergif we can get away with it18:26
bknudsonuse clouds.yaml instead18:26
bknudsonthe v3 rc file could just set OS_CLOUD18:27
*** tsekiyama has quit IRC18:27
*** rbak has quit IRC18:27
bknudsonit'll be easier to just set OS_CLOUD than source an rc file18:27
jamielennoxbknudson: sure, i'm not too worried about this at the moment the first goal is to get tempest running with v3 only and we worry about devstack users later18:28
jamielennoxi'd be happy to consider all the accrc files deprecated18:28
*** jlanoux has quit IRC18:29
*** rbak has joined #openstack-meeting18:30
*** topol has quit IRC18:30
morganfainberg#action jamielennox to look into depecating accrc files and alternatives18:30
*** maishsk_afk has joined #openstack-meeting18:30
morganfainbergok moving on18:30
morganfainbergi think there is some external work to do18:30
*** topol has joined #openstack-meeting18:30
morganfainbergbut we have some direction18:30
morganfainberg#topic Progress on keystoneauth & other repos18:30
*** openstack changes topic to "Progress on keystoneauth & other repos (Meeting topic: keystone)"18:30
*** maishsk_afk is now known as maishsk18:30
morganfainbergjamielennox: o/ any updates?18:30
marekdmorganfainberg: i am still waiting with this to be aproved - it's on a list of projec to be renamed when they schedule gerrit downtime. (https://review.openstack.org/#/c/190631/)18:31
jamielennoxumm, keystoneauth is moving along, i'm still trying to figure out the split loading from the plugins themselves18:31
morganfainbergmarekd: ok18:31
jamielennoxthere is an issue with the gate job for ksc that relies on ksa18:31
*** jruano_ has joined #openstack-meeting18:31
marekdmorganfainberg: one more thing - why do we hav enow keystonauth1 ?18:31
morganfainbergjamielennox: possibly because of the namespace change?18:32
marekdwhat shall i put in the code? from keystoneauth or keystoneauth1 ?18:32
morganfainbergmarekd: because we're supporting side-by-side major versions18:32
morganfainbergkeystoneauth1 is the first release of keystoneauth18:32
morganfainbergnext major release will be keystoneauth218:32
jamielennoxmorganfainberg: yes - i didn't think it would matter because it's supposed to be pulling keystoneauth from git18:32
bknudsondoes keystoneauth-saml2 also need 1 on the package?18:32
morganfainbergjamielennox: except the whole namespace changes now.18:32
marekdwhen will be next major release? and who will be supposed to use keystoneauth2 ?18:32
*** jruano has quit IRC18:32
jamielennoxbut for whatever reason it's getting the pypi version instead and that's still on the old namespace18:32
jamielennoxmarekd: hopefully never18:33
morganfainbergmarekd: no plans for major release #218:33
morganfainbergbut this is future proofing18:33
marekdmorganfainberg: ok.18:33
marekdjamielennox: morganfainberg so for now shall i start importing from keystoneauth1 ?18:33
jamielennoxso for example https://review.openstack.org/#/c/196479/1 is failing18:33
*** enikanorov2 has joined #openstack-meeting18:34
jamielennoxi got as far as determining why they are failing but not yet determining why it's not pulling from git as expected18:34
jamielennoxbecause i'm sure it used to18:34
bknudsonwhere does that branch get its keystoneauth from/18:34
*** maishsk_afk has joined #openstack-meeting18:34
morganfainbergbknudson: git18:34
jamielennoxso it's supposed to be git https://github.com/openstack/python-keystoneclient/blob/feature/keystoneauth_integration/requirements.txt#L918:35
*** jckasper has joined #openstack-meeting18:35
*** maishsk has quit IRC18:35
jamielennoxbut it appears to be from pypi18:35
morganfainbergsomething to chase down18:36
jamielennoxi would like to start getting those ksc on ksa patches merged as i don't want to consider keystoneauth stable until we know we can offload most of ksc to it18:37
*** rossella_s has quit IRC18:37
*** rossella_s has joined #openstack-meeting18:37
morganfainbergjamielennox: sure.18:37
*** pradk has quit IRC18:37
*** tsekiyama has joined #openstack-meeting18:38
*** olaph has quit IRC18:38
morganfainbergso we need eyes on those reviews18:38
morganfainberg#action please review keystoneauth integration patches18:38
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x8fb4250>18:38
morganfainberg#action keystone developers please review keystoneauth integration patches18:38
*** banix has joined #openstack-meeting18:39
morganfainberg#topic Review policy update18:39
*** openstack changes topic to "Review policy update (Meeting topic: keystone)"18:39
morganfainbergbknudson: o/18:39
bknudsonmorganfainberg: I've got a couple of reviews out that hope to clarify that some things can be left up to the developer18:39
bknudsonhttps://review.openstack.org/#/c/194906/ -- Document update sample config up to developer18:39
morganfainbergthe only reason i don't want the sample config to be *in* the same review as code changes is because we've had massive rebase issues in the past18:40
bknudsonhttps://review.openstack.org/#/c/195335/ -- Document use of wip up to developer18:40
Steve_droidI'm still hoping to automate that via a job18:40
bknudsonwe had one review that had rebase issues.18:40
morganfainbergif everyone else would rather make it up to the dev, i'll just abstain and not really care18:40
morganfainbergbknudson: this was at the end of last cycle18:40
bknudsony, so this is just to clarify whether it's up to the developer or not18:40
morganfainbergwe had a bunch of them. but like i said, i'll happliy defer to the rest of the team here.18:41
morganfainbergon both counts18:41
morganfainbergi don't feel strongly on WIP either18:41
bknudsonif cores don't think it should be up to the developer then I'll change the reviews to say it's not up to the developer instead18:41
*** arnaud____ has quit IRC18:41
*** ivar-lazzaro has quit IRC18:41
morganfainbergcores- please vote those18:41
henrynashI think updating the sample config should be up to teh developer18:41
marekdbknudson: whatever it is - just let's be verbose and make sure readed knows exactly what is the intention.18:41
bknudsonI think if people don't feel strongly one way or the other then let's leave it up to the developer18:41
*** ivar-lazzaro has joined #openstack-meeting18:42
henrynashand reviews should -1 if a config file change is being put in with a sample updated (basically…the way it used to be)18:42
gyeeI am struggling with the wip decorator18:42
gyeehere's an example, https://review.openstack.org/#/c/187899/9/keystone/tests/unit/test_v3_protection.py18:42
gyeeline 99418:42
gyeethe API hasn't been developed yet so the code may not be correct18:42
gyeeso its essentially dead code at the moment18:43
*** sbalukoff has quit IRC18:43
gyeeI would rather not have them for now18:43
*** annegentle has quit IRC18:43
marekdi liked wip too18:43
henrynashsometimes wip is useful, other times I think it is more clear to really show the actual point in the test method where a failure is expected18:43
gyeeso wip is replacing TODO or FIXME?18:44
morganfainbergok so, i think we should be voting on those patches. if you want it to be more open - +1/+2 them18:44
morganfainbergif you want ot be more restrictive -1 them. please let bknudson +A once we've let people vode18:44
morganfainbergbknudson: feel free to +A at the end of the week provided enough +2s are there and outweigh the -1s18:45
* morganfainberg is fine with it going either way18:45
*** sarob_ has joined #openstack-meeting18:45
topolhenrynash +++18:46
dstanekgyee: wip is different; it's really for replacing a skip18:46
gyeeso wip is for tests only?18:46
*** sdake has quit IRC18:46
marekdgyee: that's my understanding18:46
*** geoffarnold has joined #openstack-meeting18:46
henrynashdstanek: …or an explict assertRaises() with a comment as to “here is the bug I am going to fix in the next patch"18:47
david8huHow does wip know the bug is fixed or develper has to going in and remove wip?18:47
*** rbak has quit IRC18:47
samueldmqdavid8hu: wip passes if the test fail, and fail if the test passes18:47
*** sdake has joined #openstack-meeting18:47
dstanekhenrynash: right, if otherwise the test should pass by just removing the wip18:47
dstanekgyee: tests it's a testing tool from the TDD/BDD world18:48
gyeealrighty then18:48
* gyee vote for +0 instead of -018:49
morganfainbergok anyway18:49
morganfainberg#action keystone-core vote on the reviews for policy (sample config and WIP)18:49
morganfainberg#topic Dynamic Policies - Current Status and Scope for Liberty18:49
*** openstack changes topic to "Dynamic Policies - Current Status and Scope for Liberty (Meeting topic: keystone)"18:49
morganfainberghtruta: sorry we'll likely need to defer your topic for next week unless this goes quickly18:50
*** irenab has quit IRC18:50
morganfainberghtruta: my apologies18:50
samueldmqlast week I had a couple of conversations with morgan and adam about the scope for L18:50
samueldmqmorganfainberg: trying to be quick18:50
htrutamorganfainberg: it'd be quick18:50
htrutabut we can discuss in openstack-keytone later18:50
morganfainberghtruta: depends on samueldmq18:50
samueldmqso, basically, we're adding the capability of dynamic fetching of policies in endpoints18:50
morganfainbergsamueldmq: go18:50
*** irenab has joined #openstack-meeting18:50
* samueldmq runs18:50
samueldmqso, i)policy overrides occur at keystone18:51
samueldmqii) middleware fetches and cache the policy18:51
samueldmqiii) using the oslo.policy libreary to overlay the local policy file18:51
bknudsonauth_token middleware?18:51
samueldmqthere are 3 respective specs18:51
samueldmqoslo.policy doing the policy overlay18:51
samueldmq#link https://review.openstack.org/#/c/196753/18:51
*** yamamoto has quit IRC18:51
samueldmqksmiddleware doing fetch and cache18:51
samueldmq#link https://review.openstack.org/#/c/134655/18:51
bknudsonor middleware after auth_token?18:51
samueldmqkeystone server associating and delivering policies by url18:51
samueldmq#link https://review.openstack.org/#/c/192422/18:51
*** sbalukoff has joined #openstack-meeting18:51
*** chuckcarmack has joined #openstack-meeting18:52
gyeebknudson, before auth_token as endpoint constraint depends on it18:52
samueldmqbknudson: I think it will be a separate middleware filter, as suggested by morgan, need to visit this point18:52
samueldmqI've updated the oslo and ksmiddleware specs, I will be addressing the keystone one until tomorrow18:52
samueldmqand then....18:52
samueldmqsending the FFE request to the ML18:52
ayoungwhile separate would be cleaner...harder to deploy18:52
samueldmqI think that's all18:52
david8husamueldmq, for policy by url, we need to consider additional cases that I commented on yesterday and today.18:53
ayoungso, much as it pains me to drive toward it, its probably going to end up in auth_token18:53
bknudsonsounds like it might as well just be part of auth_token18:53
*** pabelanger has joined #openstack-meeting18:53
samueldmqdavid8hu: sure, I 'll take a look at then18:53
samueldmqbknudson: makes sense18:53
samueldmqso please review and leave comments :)18:53
gyeeauth_token is way overloaded already18:53
*** jwcroppe has quit IRC18:53
samueldmqand for an overview reference18:53
samueldmqsee https://wiki.openstack.org/wiki/DynamicPolicies18:53
bknudsonauth_token might need some refactoring18:54
*** vnod has quit IRC18:54
*** jwcroppe has joined #openstack-meeting18:54
samueldmqmorganfainberg: I'd like to have more time, but I think I covered what I wanted .. letting people know about it .. we can move on18:54
ayounggyee, agreed, but we are cleaning up the architecture.  I could see an approach that says there is a generic python middleware that lumps it all together18:54
jamielennoxi think this should be it's own middleware18:54
ayoungbut the sperate pieces could be deployed stnad alone as well18:54
* morganfainberg is a fan of not making auth_token do everything18:54
ayoungjamielennox, *should* only from a code cleanliness standpoint18:54
marekdmorganfainberg: so different middlewares?18:54
jamielennoxit's no harder to deploy than any other middleware we've added and there have been a few18:54
jamielennoxayoung: mainly sure18:55
ayounglets treat auth_token as a facade for multiple middlewares18:55
gyeejamielennox, exactly18:55
bknudsonif its its own middleware then it'll need to get the auth config again18:55
morganfainbergmarekd: thats my choice, but it's just from a separation of concern aspect18:55
jamielennoxbknudson: auth config?18:55
gyeeit would be paste.ini18:55
bknudsonjamielennox: config for how to talk to keystone18:55
jamielennoxoh - right18:55
* morganfainberg avoids making a bad joke.18:55
bknudsonalthough we've been talking already about some middleware for that too18:55
*** sarob_ has quit IRC18:56
marekdmorganfainberg: so one day it woud go for instance auth_token -> kmw-dynamic-policy - ksm-k2k for instance?18:56
bknudsonsince nobody wants to use global CONF18:56
morganfainbergmarekd: possibly18:56
jamielennoxbknudson: so we need a way to pass down the plugin that auth_token middleware creates?18:56
bknudsonjamielennox: we can't pass it down since the policy middleware needs to be first18:56
bknudsonmaybe we need another middleware that generates the plugin that's before both of them18:57
jamielennoxwhy does policy need to be first?18:57
*** Longgeek has quit IRC18:57
bknudson(01:52:02 PM) gyee: bknudson, before auth_token as endpoint constraint depends on it18:57
gyeejamielennox, because we need it to enforce endpoint constraint18:57
morganfainberg2m left18:57
*** vnod has joined #openstack-meeting18:58
*** egallen has quit IRC18:58
jamielennoxwhy don't we make endpoint constraint enforcement part of the policy middleware then18:58
*** AJaeger has joined #openstack-meeting18:58
*** Longgeek has joined #openstack-meeting18:58
* jamielennox was arguing for it being seperate from auth_token anyway18:58
ayoungjamielennox, that is where it belongs18:58
gyeejamielennox, ayoung, no argument here18:58
*** jwcroppe has quit IRC18:59
gyee30 seconds18:59
ayoungjamielennox, I just want to avoid the deployment issues18:59
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"18:59
openstackMeeting ended Tue Jun 30 18:59:21 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-06-30-18.03.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-06-30-18.03.txt18:59
*** marekd has left #openstack-meeting18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-06-30-18.03.log.html18:59
morganfainbergsorry hit enter too soon18:59
gyeejump the gun there18:59
jamielennoxi was going to join the countdown18:59
morganfainbergto the -keystone channel18:59
*** browne has left #openstack-meeting18:59
*** ianw has joined #openstack-meeting18:59
fungiis it at all like the bat cave?18:59
fungispeaking of, it's that same bat time and same bat channel again19:00
*** Steve_droid has quit IRC19:00
*** khaldrogox has joined #openstack-meeting19:00
jeblairhowdy infra folks19:00
jeblair#startmeeting infra19:01
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-06-23-19.02.html19:01
openstackMeeting started Tue Jun 30 19:01:03 2015 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
jeblair#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
jeblair#info adding asselin to puppet-openstackci-core19:01
pleia2woo :)19:01
pabelanger /clap19:01
*** singlethink has joined #openstack-meeting19:01
fungiasselin: thanks for volunteering for this burden19:02
jeblairi'll do that real soon now, and hopefully we'll be able to add some more folks soon too19:02
jeblairi know there's interest19:02
jeblair#topic Specs approval19:02
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:02
jeblair#topic Specs approval: RefStack Site Hosting (hogepodge, davidlenwell)19:02
*** openstack changes topic to "Specs approval: RefStack Site Hosting (hogepodge, davidlenwell) (Meeting topic: infra)"19:02
jeblair#link refstack site hosting spec http://specs.openstack.org/openstack-infra/infra-specs/specs/refstack_dot_org.html19:02
jeblair#info refstack site hosting spec was approved19:02
*** singlet__ has joined #openstack-meeting19:03
fungii've been more terrible than usual about finding time to review these, so thanks to everyone else who did and picked up my slack19:03
*** novas0x2a|laptop has quit IRC19:03
*** neelashah has quit IRC19:03
hogepodgethanks everyone for approving refstack19:04
*** sankarshan is now known as sankarshan_away19:04
*** Ng has joined #openstack-meeting19:04
hogepodgeHappy to help with the deployment.19:04
*** sankarshan_away is now known as sankarshan19:04
fungihogepodge: i'll hold you to that ;)19:04
jeblairanything else we should cover on this?19:05
*** singleth_ has quit IRC19:05
*** fallenpegasus has quit IRC19:05
pabelangerI have 1, but can wait until open discussion19:05
*** irenab has quit IRC19:06
jeblairpabelanger: we don't have a huge agenda today, go for it19:06
*** lapalm has joined #openstack-meeting19:06
*** lapalm has quit IRC19:06
*** singlethink has quit IRC19:06
*** vnod has quit IRC19:06
*** VanL has quit IRC19:06
*** Guest80179 has joined #openstack-meeting19:06
pabelangerSo, I created a spec to host the trystack.org since under -infra.  The static content of the web site, not the openstack bits: https://review.openstack.org/#/c/195098/19:06
*** lapalm has joined #openstack-meeting19:06
jeblairpabelanger: oh, i thought you had a refstack thing19:07
pabelangerSo far, a team member at RedHat is open to the idea of moving it into trystack.o.o19:07
pabelangerjeblair, no, something new19:07
pabelangersorry, if I was unclear19:07
fungisounds like a separate meeting topic19:07
jeblairyeah, let's move on19:07
jeblair#topic Priority Efforts (Migration to Zanata)19:07
*** openstack changes topic to "Priority Efforts (Migration to Zanata) (Meeting topic: infra)"19:07
jeblairwe had some action items from last time19:07
jeblairjeblair set up translate@o.o infra-root alias19:08
jeblairi did that19:08
jeblairpleia2 sign up translate@ openstackid account19:08
*** neelashah has joined #openstack-meeting19:08
*** john-a-joyce has quit IRC19:08
pleia2the account is created on openstackid19:08
jeblairer, except i think i called it 'zanata'19:08
*** maishsk_afk has quit IRC19:08
jeblairwhich i think is the better choice19:08
jeblairand then:19:08
jeblairfungi mrmartin pleia2 investigate "admin interface" for openstack id, get service account group assigned somehow19:08
jeblairanything come of that?19:08
pleia2zanata was pointed at openstackid-dev though, so a patch merged this morning to have zanata use that, so soon I can set up the zanata account itself19:09
*** neelashah1 has joined #openstack-meeting19:09
fungiyeah, that definitely didn't happen on my part19:09
pleia2not yet19:09
fungii still need to ask around about that19:09
mrmartinnot yet, we need to check it19:09
jeblair#action fungi mrmartin pleia2 investigate "admin interface" for openstack id, get service account group assigned somehow19:09
mrmartinnot a big deal, need to allocate time19:09
pleia2thanks mrmartin, let me know what you need19:09
*** _nadya_ has joined #openstack-meeting19:09
pleia2*from me19:09
* fungi knows that feeling19:09
*** rbak has joined #openstack-meeting19:10
*** achanda has joined #openstack-meeting19:10
*** maishsk_afk has joined #openstack-meeting19:10
*** Dans_ has joined #openstack-meeting19:10
*** geoffarnold has quit IRC19:10
jeblairSee discussion on https://review.openstack.org/#/c/187867/ need infra input on translation-projects.txt vs. changes to projects.yaml19:10
*** henrynash has quit IRC19:10
jeblairwe also have that in the meeting agenda ^19:10
pleia2yep, this is a result of a chat between AJaeger and StevenK over (my) night19:11
*** lapalm has quit IRC19:11
*** dguerri` is now known as dguerri19:11
pleia2I summarized it in the review, need input from others19:11
*** VanL has joined #openstack-meeting19:11
*** _nadya__ has joined #openstack-meeting19:11
pleia2do we want to create a new translation-projects.txt file in project-config, or can we ad a translate: true stanza to projects.yaml to add projects to zanata19:11
*** _nadya_ has quit IRC19:11
jeblairah, yeah, i think despite appearances to the contrary, we actually don't want to have tons of files named "projects.yaml" so i like (b)19:12
* AJaeger would love not to have an admin go into Zanata and manually set up a new project19:12
*** breton has left #openstack-meeting19:12
pleia2either way, good news is we can now add projects via code review, not through the translations web API like we do with transifex now :)19:12
pleia2AJaeger ++19:12
jeblairAJaeger: yeah, that's definitely the goal19:12
fungiwe've added fields to gerrit/projects.yaml for non-gerrit-specific aspects which are still repo-relative19:12
*** neelashah has quit IRC19:13
fungiit's mostly for stuff driven from jeepyb, but i don't think it has to be _just_ that19:13
* pleia2 nods19:13
AJaegerpleia2: Zanata operation could also be done via puppet19:13
fungifor example, storyboard was consuming that directly for creating project-groups19:13
pleia2AJaeger: yeah, exciting times :)19:13
*** e0ne is now known as e0ne_19:14
jeblairi'd say we have consensus on b, unless there are objections?19:14
*** jorge_munoz has quit IRC19:14
*** rbak has quit IRC19:14
pleia2I'll let StevenK know and we'll work on the required changes elsewhere to support it19:14
AJaegerwhatever works ;)19:14
*** Guest80179 has quit IRC19:14
AJaegerthanks, pleia219:14
jeblairany other zanata items?19:14
*** e0ne_ is now known as e0ne19:15
pleia2we're handing it off to Daisy this week, and opening testing to the broader community next week19:15
pleia2so, yay :)19:15
pleia2that's all19:15
*** dguerri is now known as dguerri`19:15
jeblair#topic trystack web site hosting (pabelanger)19:15
*** openstack changes topic to "trystack web site hosting (pabelanger) (Meeting topic: infra)"19:15
jeblairokay, late addition! :)19:15
pabelangerha, ya sorry. Was going to bring it up in open discussion19:16
pabelangereither way, I think there is a good chance to move trystack.org under -infra if people are open to it.  Not the openstack bits, just the static contents of the website19:16
pabelangerspec is up19:16
*** egallen has joined #openstack-meeting19:16
pabelangerand puppet bits working too19:16
*** iurygregory has left #openstack-meeting19:17
*** novas0x2a|laptop has joined #openstack-meeting19:17
*** puranamr has joined #openstack-meeting19:17
pabelangerthe spec: https://review.openstack.org/#/c/195098/19:17
pabelangerI assume we'd get the people managing the site now, and openstack foundation board to chime in on the move19:17
*** rbak has joined #openstack-meeting19:17
fungithat seems like relatively low-hanging fruit we should knock out if all parties are in agreement. thanks!19:17
*** Dans_ has quit IRC19:17
SpamapSis it a truly static website?19:18
pabelangerSpamapS, yup19:18
SpamapSis there any reason thats not just in swift then?19:18
*** puranamr has quit IRC19:18
fungithe openstack service bits of that (and the embarrassing facebook groups auth model it's reliant on for the moment) will be a tougher nut to crack19:18
pabelangerSpamapS, https://github.com/trystack/trystack_org_webcontents19:18
*** puranamr has joined #openstack-meeting19:18
pabelangerthe plan would be to move that in to -infra too19:18
jeblairyeah, i think getting the web site hosted is a good first step to make it more of a community effort19:19
jeblairi don't want us to get involved in running the site yet, but after we have infra-cloud up and running for a while, i think we will be in a position to start talking abotu that19:19
*** jorge_munoz has joined #openstack-meeting19:19
*** chuckcarmack has left #openstack-meeting19:19
*** cbouch has quit IRC19:19
jeblairsorry, by that last, i mean running the actual openstack service19:19
mrmartinwe should handle this the same way, as we are doing for openstackid, group, and maybe o.o, typical web projects19:20
mrmartinand ask.o.o19:20
jeblairmrmartin: handle what?19:20
fungithere's still a large unknown around that piece, which is self-service sign-up/single-sign-on for keystone19:20
mrmartintrystack.o.o website19:20
*** jorge_munoz has quit IRC19:20
*** rbowen has quit IRC19:20
jeblairmrmartin: as a static site it's actualy a bit simpler and does not need its own server, but yes, in general19:21
fungimrmartin: well, the trystack website is just static content (docs)19:21
mrmartinyeah, but self-service signup is a solvable part, if we have some spec / doc for that19:21
*** rbowen has joined #openstack-meeting19:21
* SpamapS feels like we got off track?19:21
fungitwo different problems to solve. the easy one is the trystack.org static content website. that's our topic19:21
*** echoingumesh has joined #openstack-meeting19:22
pabelangerYes, right now the site is mostly unmanaged, and it would be fairly painless to move it into the -infra domain to start monitoring / managing it19:22
pabelangerany other changes to login or servers, would need more detailed specs19:22
jeblairSpamapS: i suppose we could put it in swift; we don't really have a generalized 'host a static site in swift' model.  even the proposed docs publishing change has problems with that model that are hard to overcome.19:23
*** jorge_munoz has joined #openstack-meeting19:23
*** geoffarnold has joined #openstack-meeting19:23
*** Prashant_ has joined #openstack-meeting19:23
jeblairwhereas, apache vhost is fairly common and easy19:23
fungii'm not opposed to someone solving that challenge, but we do already have virtual machines which can use apache to serve local files19:23
*** PrashantS has quit IRC19:23
jeblairif anyone is interested in the problems, see http://specs.openstack.org/openstack-infra/infra-specs/specs/doc-publishing.html19:24
jeblairat least, i hope we captured the issues in there :)19:24
pabelangermrmartin, this is what it would look like if we imported today: https://review.openstack.org/#/c/194816/19:24
fungiour uploading/serving job logs in swift and the os-loganalyze project is a good example of how that gets pretty complicated quickly19:24
*** igordcard has joined #openstack-meeting19:25
SpamapSjeblair: I think thats fine in each narrow case. From a broader view, one has to wonder why it isn't easier to use swift for its exact intended purpose though.19:25
pabelangersorry SpamapS ^19:25
jeblairSpamapS: yeah, we provide feedback to swift folks for sure19:25
fungiSpamapS: part of it comes down to how different service providers choose to set up their swift services too19:25
SpamapSfungi: bingo19:25
jeblairSpamapS: our use case is arguably not its exact intended purpose; it gets into splitting hairs too.19:26
jeblairanyway, hope that provides some background :)19:26
*** echoingumesh has quit IRC19:26
*** vivek-eb_ has quit IRC19:26
jeblairpabelanger: thanks for kicking that off19:27
jeblair#topic Open discussion19:27
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:27
pabelangerjeblair, np19:27
SpamapSjeblair: totally, I don't want to discuss any details, however I do want to register my strong belief that the general direction I think we should take is to push things toward static hosting being done in swift in general. I understand that is easy to say, and not easy to do. :)19:27
SpamapSSame reason we use Trove right? :)19:27
mrmartinSpamapS: so you suggest to move all static content into swift?19:28
jeblairSpamapS: which has also not been a resounding success19:28
*** singlethink has joined #openstack-meeting19:28
SpamapSAnyway, regarding infra-cloud, just a general status update: On the test node I have ironic,keystone,nuetron, and glance working. Nova is installed, but nova-api refuses to respond with anything other than 404's for all requests.19:28
SpamapSmrmartin: absolutely.19:28
greghaynesSpamapS: w00t19:28
SpamapSmrmartin: the fact that there is any friction to that is a sign that investment is needed at any of those friction points.19:28
pabelangerSo, I managed to find the issue with our puppet-apply-centos6 gate job.  It looks to be an issue within the git client (1.7). Moving to 1.8 fixes the performance issue (30+mins down to 4mins).19:29
*** vivek-ebay has joined #openstack-meeting19:29
pabelangerFor the most part, i did a JJB that upgrades git inline: https://review.openstack.org/#/c/196761/19:29
pabelangerwould be curious to get some feedback19:29
pleia2thanks pabelanger19:29
SpamapSmrmartin: long term it should result in having less resources to manage, and more scalability.19:29
jeblairSpamapS: please understand that this thought has occurred to us19:29
SpamapSjeblair: I'm certain it has. I want to make sure we keep looping back to it.19:29
fungipabelanger: were you able to figure out whether a glibc change or similar earlier this year on centos 6 is what caused that to suddenly start happening for us?19:29
mrmartinSpamapS:  the shortest path is going with static.o.o for trystack but in middleterm I can imagine some efforts to move static content to swift19:30
*** singleth_ has joined #openstack-meeting19:30
*** igordcard_ has joined #openstack-meeting19:30
SpamapSjeblair: perhaps those with more historical context are more weary than I? ;)19:30
pabelangerfungi, no, I didn't get that far.  I wanted to first try a newer client to see if it was affected too.19:30
jeblairSpamapS: i hope you will find some of that in the spec i linked19:30
pabelangerfungi, I was going to look into the 1.8 branch and see if I could find a commit that addressed the problem19:30
SpamapSjeblair: I did, thank you. :) (I've also been trying to withdraw from this point for about 10 minutes now... ;)19:31
jeblairk, let's talk about centos6 git19:31
jeblairistr we tried to use git:// on centos6 jobs for a similar problem in the past...19:31
jeblairdoes that still help things?  did that regress?19:31
fungiSpamapS: put down the swift and back away slowly ;)19:31
*** singlet__ has quit IRC19:32
*** VanL has quit IRC19:32
*** singlethink has quit IRC19:33
pabelangerjeblair, I tried git:// and http:// for URI's there was an improvement but still some delay19:33
ttxOpen discussion, I spun up a phabricator instance to play a bit with CustomFields19:33
pabelangerhttps was the biggest hit to performance19:33
ttxwill play tomorrow19:33
*** crc32 has joined #openstack-meeting19:33
*** ivar-lazzaro has quit IRC19:34
*** armax has quit IRC19:34
pabelangerjeblair, at the end of the day, upgrading git yielded the same performance as ubuntu hosts19:34
*** aysyd has quit IRC19:34
pabelangerI never could get centos6 down to 5min mark using different URIs19:34
jeblairpabelanger: so we can fix this with newer git on centos, or potentially finding the underlying thing on centos that changed (eg, glibc?)19:35
jeblairor we can stop using centos6 and move to centos719:35
pabelangeryes, that was another thought19:35
pabelangerI was looking this morning what centos6 we had for -infra and puppet19:35
pabelangeri didn't see much19:35
*** ivar-lazzaro has joined #openstack-meeting19:35
jeblairi suspect we can upgrade infra fairly easily19:35
pabelangerI was talking to fungi about bare-centos7 image and such19:36
jeblairthe question is what test jobs need centos619:36
pabelangerI could get a list together for that19:36
*** marrusl has joined #openstack-meeting19:36
fungiworrisome is that if we upgrade our git servers to centos 7 we may stop supporting shallow clones19:37
fungiis git there as new as on ubuntu trusty?19:37
*** jorge_munoz has quit IRC19:37
pabelangerunsure for me19:38
*** xyang1 has quit IRC19:38
*** xyang1 has joined #openstack-meeting19:38
jeblairit's not clear that the git authors want to support that, so...19:39
*** john_a_joyce has joined #openstack-meeting19:39
fungii'd be okay with declaring that we don't support shallow clones from our git server farm, but not sure who might rebel over that19:40
mordredthey can rebel all they want - we can't run centos6 for forever19:40
jeblairwe can point them at the git bug19:40
mordredmaybe a friend somewhere will fix it19:40
fungigreat point19:41
jeblairso i think the ideal solutions would be: 1) underlying centos6 bug is fixed; 2) centos6 upgrades git; 3) we remove our use of centos6; 4) we self-upgrade git on our centos6 images19:41
jeblairin order of preference ^19:41
pabelangerThat would be best case IMO19:42
jeblairpabelanger: thanks for digging into it19:43
*** shaleh has quit IRC19:43
jeblairttx: cool, good luck!19:44
ttxjeblair: I think I'll killfile that OOO from mpstor.com dude19:44
jeblairthat hasn't happened yet?19:44
*** maishsk_afk is now known as maishsk19:44
jeblairttx: thank you :)19:45
ttxjeblair: I assumed it was, but they keep on coming19:45
ttxbtw if someone wants to volunteer to help on -dev I'll take it as a co-admin19:45
ttxhmm, he isn't subscribed (or not subscribed anymore)19:46
jeblairttx: let us know if we need to dig into logs or something19:47
*** penick has joined #openstack-meeting19:47
*** annemccormick has left #openstack-meeting19:47
asselinHi, I'd like to remind people of the common-ci virtual sprint next week (July 8-9): Sign up here: https://etherpad.openstack.org/p/common-ci-sprint19:47
greghaynesttx: I think its on -anounce19:48
jeblairhey look new signups!19:48
asselin#link common-ci virtual sprint https://etherpad.openstack.org/p/common-ci-sprint19:48
*** jhenner has quit IRC19:48
greghaynes(remember we set -anounce to reply to -dev)19:48
*** baoli has quit IRC19:48
ttxjeblair: ok, I got it. He is subscribed to openstack@lists.o.o and there is a whitelist on -dev for senders from that list19:49
ttxtwo options. Disable the whitelist or remove him from openstack list19:49
jeblairi think removing from openstack makes the most sense19:50
*** aysyd has joined #openstack-meeting19:50
jeblair(i think adding him to a blacklist is a 3rd option, but also probably not the best)19:50
ttxor I can add him to reject_these_nonmembers but no idea what takes precedence19:50
ttxeasier that he resubscribes when back from vacation.19:51
ttxIf I could find the guy who invented out of office notices19:51
ttxI'd make him SUFFER19:51
*** Rockyg has joined #openstack-meeting19:51
jeblairttx: redirect all ooo notices to them19:52
tchaypoyou could only make him suffer after he gets back in the office19:52
*** yamamoto has joined #openstack-meeting19:52
ttxok, for the record he was unsubbed.19:52
fungihttp://lists-archives.com/git/843412-setup_temporary_shallow-use-tempfile-module.html looks promising19:52
jeblairoh good there' hope19:53
*** yamahata has quit IRC19:54
fungiyeah, i think they're still deciding how to solve it and less whether to solve it19:54
*** qwebirc1434 has joined #openstack-meeting19:54
*** yamahata has joined #openstack-meeting19:54
*** achanda has quit IRC19:54
jeblairanything else or should we wrap up?19:55
*** aysyd has quit IRC19:55
*** achanda has joined #openstack-meeting19:55
jeblairthanks all!19:56
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"19:56
openstackMeeting ended Tue Jun 30 19:56:14 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-06-30-19.01.html19:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-06-30-19.01.txt19:56
ttxjeblair: thx!19:56
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-06-30-19.01.log.html19:56
*** Ng has left #openstack-meeting19:56
*** pabelanger has left #openstack-meeting19:56
*** safchain has quit IRC19:56
*** yamamoto has quit IRC19:56
*** adiantum has joined #openstack-meeting19:56
*** breitz has left #openstack-meeting19:57
*** zeddii has quit IRC19:57
*** fawadkhaliq has quit IRC19:59
*** roxanaghe_ has quit IRC19:59
*** amrith is now known as _amrith_19:59
*** achanda has quit IRC19:59
*** topol has quit IRC19:59
ttxAnyone here for the TC meeting ?20:00
*** cp16net has joined #openstack-meeting20:00
mordredo/ ish20:00
* Rockyg is lurking20:00
ttxjgriffith, annegentle, lifeless, dtroyer, jaypipes, sdague: around ?20:00
ttx#startmeeting tc20:01
openstackMeeting started Tue Jun 30 20:01:08 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
ttxOur agenda today:20:01
jeblairjaypipes looks like he is swimming20:01
ttxor drowning20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
*** amakarov is now known as amakarov_away20:01
* zehicle lurking too20:01
ttx#topic Cross-project specs final approval20:01
*** openstack changes topic to "Cross-project specs final approval (Meeting topic: tc)"20:01
ttxWe have a number of specs which I think have reached consensus stage and need our final approval to get through20:02
ttx* Enabling Python 3 for Application Integration Tests20:02
ttx#link https://review.openstack.org/#/c/177375/20:02
ttxThis one was discussed at the cross-project meeting on June 9.20:02
ttxNo objection recorded, I think it's more than time to final-approve it20:02
flaper87no objections here20:02
ttxany objection, last-minute comment?20:03
*** agentle has joined #openstack-meeting20:03
jaypipesnope, lgtm.20:03
markmcclainglad it's finally getting approved20:03
ttxalright, it's in the pipe20:03
*** Apoorva has quit IRC20:03
ttx* Add requirements management specification20:03
ttx#link https://review.openstack.org/#/c/186635/20:03
*** otter768 has joined #openstack-meeting20:03
ttxThis one was discussed at the cross-project meeting twice, on June 9 and June 2320:04
*** Apoorva has joined #openstack-meeting20:04
*** jorge_munoz has joined #openstack-meeting20:04
ttxIt's already being worked on as far as I know, no objection on the spec itself20:04
flaper87no objections here20:04
ttxLooks ready to me. Objections ?20:04
* flaper87 reads ttx's mind20:04
*** jhenner has joined #openstack-meeting20:04
*** jruano_ has quit IRC20:04
*** TravT has joined #openstack-meeting20:04
*** rbak has quit IRC20:04
ttxI'll take silence as consent20:05
ttxand approve20:05
*** jruano has joined #openstack-meeting20:05
ttx* Update to CORS specification20:05
ttx#link https://review.openstack.org/#/c/189924/20:05
ttxThis one is just small changes requested on the original CORS spec, that were pushed as a subsequent change rather than a new patchset20:05
lifelessttx: o/20:05
lifelesssorry I'm late20:05
ttxI think we can fast-track it20:05
flaper87ttx: sounds good20:06
ttxalready has TC majority anyway20:06
*** rbak has joined #openstack-meeting20:06
*** armax has joined #openstack-meeting20:07
ttxno objections, approved!20:07
*** qwebirc1434 has quit IRC20:07
ttx#topic Add release:managed to libraries and previously-incubated projects20:07
*** openstack changes topic to "Add release:managed to libraries and previously-incubated projects (Meeting topic: tc)"20:07
*** lapalm has joined #openstack-meeting20:07
ttxThose are mostly technical adjustments to reflect what the release team directly manages those days, thanks to a lot of fresh blood20:07
ttx#link https://review.openstack.org/19189320:07
ttx#link https://review.openstack.org/19219320:07
ttxThat kind of horizontal changes to the file generates a lot of merge conflicts, so I'd like to get them in ASAP before they generate more of those20:08
*** otter768 has quit IRC20:08
*** aysyd has joined #openstack-meeting20:08
jgriffiththey have the votes20:08
jgriffithflaper87: +120:08
ttxfirst one is short of one20:08
ttxjgriffith: could you apply rollcall+1 ?20:09
jgriffithttx: done20:09
lifelessttx: I did too20:09
ttxI guess an additional question would be, are you fine with adjustments to release:* tags being merged as long as two release team members agree with the change ?20:10
ttxbecause those will be back20:10
russellbyes that's fine with me20:10
* flaper87 is good with that20:10
markmcclainmake sense20:10
jgriffithseems fine to me20:10
flaper87happy to do a quick vote to keep it logged20:10
russellbit's all changeable if something comes up worth discussing20:10
*** gokrokve has joined #openstack-meeting20:10
flaper87as in, meetbot vote, logged, stamped, we told you so20:11
flaper87anyway, I'm good with that20:11
ttxyeah, and can revert / fix if weird20:11
lifelessI don't think its a tc thing20:12
ttxI'm working on a revision of the tags, and wil include that tag application rule in it for reference20:12
lifelesswe shouldn't need to spend time thinking about stuff owned by other people20:12
russellbsounds good20:12
*** lapalm has quit IRC20:12
*** maishsk has quit IRC20:12
ttx#agreed future release:* tag changes can be fasttracked as long as the release team approves them20:12
*** egallen has quit IRC20:12
ttx#topic Be specific about geography in release names20:13
*** openstack changes topic to "Be specific about geography in release names (Meeting topic: tc)"20:13
*** frobware_ has joined #openstack-meeting20:13
ttx#link https://review.openstack.org/19197420:13
ttxThat one looks pretty straightforward20:13
ttxany objection to it merging here and now ?20:13
mordredmerge it20:13
ttxwe are on a ROLL today20:13
russellbmerge away20:13
ttx#topic RPM distribution packaging of OpenStack20:13
*** pratap has quit IRC20:13
*** openstack changes topic to "RPM distribution packaging of OpenStack (Meeting topic: tc)"20:13
ttx#link https://review.openstack.org/19158720:14
ttxSo.... This one was proposed as a split from the original "all packaging" team20:14
ttxThat said, that team doesn't seem to be really formed yet, and I haven't seen any recent discussion about it20:14
ttxWhich probably explains the absence of comment, the merge conflict status, and the ptl:TBD line20:14
*** echoingumesh has joined #openstack-meeting20:14
ttxMy take is that while we don't require teams to be mature, they should still exist in reality, have a clear scope and leadership, have some meeting point...20:14
*** maishsk has joined #openstack-meeting20:14
ttxSo I'd keep this one as WIP, same as the Debian packaging one20:14
jeblairi think this is in the same situation as the deb version -- if the author comes forward and updates the proposal, i would +1 it20:15
*** xingchao_ has joined #openstack-meeting20:15
*** changbl has quit IRC20:15
russellbttx: +120:15
*** pratap has joined #openstack-meeting20:15
jgriffithwould be good to have those coordinated IMO, maybe even in the same proposal somehow?20:15
agentleagreed ttx20:15
*** mrutkows has quit IRC20:15
lifelessjgriffith: I think thats asking too much :)20:16
ttxjgriffith: well they WERE in the same proposal20:16
flaper87I went through that spec and I agree with russellb and ttx comments20:16
ttxthen realized they could probably not work that well together20:16
ttxand would have been really two teams20:16
*** Sukhdev_ has quit IRC20:16
jgriffithttx: well, I was thinking more in terms of the spec20:16
russellbi'm happy with this in concept, i just want some very basic level of a baked proposal20:16
jgriffithttx: still two projects, but one consistent spec but that's ok20:17
russellbi feel like this is nothing but a incredibly high level idea20:17
ttxOK, I'll move it to backlog until it gets updated / refreshed / progress is made / meetings happened / PTL is chosen / scope is defined20:17
jeblairttx: ++20:17
ttx#topic Add Stackforge Retirement resolution20:17
*** openstack changes topic to "Add Stackforge Retirement resolution (Meeting topic: tc)"20:17
ttxAlright! Enough consensus20:17
ttx#link https://review.openstack.org/19201620:17
ttxThere are a few objections to this one.20:17
jeblairconsensus this one too! :)20:17
flaper87jeblair: lol20:17
ttxMy reading is that everyone agrees that we should encourage things that ultimately want to be an openstack project to directly file for the openstack namespace (category (a))20:17
*** claudiub has quit IRC20:18
jeblairi think the objections are perhaps lack of clarity that could be addressed in a subsequent resolution20:18
ttxAnd I think that's the main goal of this proposal: encourage "incubating" projects to directly file for big-tent inclusion20:18
jeblairer revision20:18
ttxI call that the "stackforge is not an incubator" effort20:18
flaper87jeblair: agreed, for instance my last comment20:18
jeblairttx: indeed.  the main goal is not to reduce service, but instead to stop moving projects from org to org20:18
ttxNot everyone agrees that we should discontinue support for the other categories -- especially for projects that don't ever want to become an openstack project but still want to benefit from our infrastructure20:18
ttxFor those (categories (b) and (c)), I think it was nice of us to provide resources to educate and encourage random open source projects to use nice tooling20:18
ttxbut if it's too costly to support those projects, I support the Infra team decision of dropping them20:18
russellbi think it's totally fair for infra to not stay in the business of free infrastructure for things that don't want to be an openstack project20:19
dhellmannwe do have some projects on stackforge that I wouldn't expect to want to become official, like pecan and WSME. I spoke to the pecan lead today and he's ok with moving back to github, but we would lose some of the gating they are doing for us. I would expect the WSME maintainers to move to github, too.20:19
jeblairi'm pleasantly surprised by that; i'd like more feedback there20:19
agentlejeblair: is the bigger concern the org-to-org moves or the upkeep of stackforge20:19
flaper87russellb: ++20:19
jeblairagentle: mostly the org-org moves20:19
*** _nadya__ has quit IRC20:19
*** xingchao_ has quit IRC20:19
ttxjeblair: Ultimately those could be two separate decisions. We could decide to communicate about "stackforge not being an incubator"20:19
jeblairactual drain for supporting projects staying in stackforge is small20:19
ttxAnd separately we can decide to stop supporting other categories in stackforge (or to stop accepting new projects there)20:19
jeblairttx: i agree, that's an option20:19
flaper87dhellmann: tbh, I think that's fine. We should find a way to help them gating for us or just deal with the lack ofit20:20
dtroyerI like the idea of having stackforge around for things (like Pecan et al) that we benefit from having similar ci20:20
dhellmannflaper87: right20:20
fungii have a personal dream of just not having git namespaces at all so this silliness wouldn't be an issue, but that's not been feasible for technical reasons so far, so we're stuck with a cosmetic prefix on repository names to which people ascribe too much meaning20:20
dtroyermaybe at that point there be some higher criteria for adding new projects to it20:20
*** zehicle has quit IRC20:21
jeblairi think we would need to characterize when we think it's reasonable for a project that deos not want to join openstack to use the service20:21
dhellmannfungi: we could rename stackforge to notnotopenstack20:21
lifelessfungi: should we rename the world. To z/nova, z/cinder,20:21
lifelessfungi: and f/pecan, etc. ?20:21
funginot so keep on renaming 700 repos either, so... meh :/20:21
*** jwcroppe has joined #openstack-meeting20:21
*** lhcheng_ has left #openstack-meeting20:21
dhellmannin the case of pecan, we're limiting their ability to test under versions of python that they care about but we don't, so the authors are ok with moving if that's the consensus20:21
dhellmannthere are other CI systems out there that folks are pretty happy with, after all20:22
jeblairfungi: i'm much more interested in performing the big-tent moves from stackforge -> openstack if we know there's a light at the end of the tunnel :)20:22
*** john_a_joyce has quit IRC20:22
flaper87dhellmann: I wonder if these are the only 2 cases but I doubt it20:22
dhellmannflaper87: no, just the 2 I'm familiar enough with20:22
jeblairdhellmann, flaper87: we even have a couple in infra20:22
flaper87it'd be cool to send an email out mentioning this and see who screams20:22
lifelessso a conservative though would be to limit this to just not-an-incubator20:23
flaper87jeblair: aha20:23
lifelessand wait a year20:23
*** zehicle has joined #openstack-meeting20:23
*** henrynash has joined #openstack-meeting20:23
flaper87jeblair: any reply to my last comment w.r.t requirements and possible instability?20:23
flaper87am I just being paranoid ?20:23
ttxjeblair: I think it's fair to reject things-that-clearly-want-to-be-openstack when they apply to stackforge and tell them to apply for big tent instead20:23
jeblairflaper87: good question!  quick answer: you're being too paranoid! :)20:23
*** pratap has quit IRC20:23
dhellmannttx: ++20:23
*** pratap has joined #openstack-meeting20:23
flaper87jeblair: I can live with that as long as there are people like you that will bring me back to earth20:23
ttxjeblair: but that means an application process20:24
jeblairflaper87: i think we can keep those concerns separate -- what projects use global reqs is a separate question from git namespace, etc.20:24
lifelessflaper87: once constraints are live20:24
ttxjeblair: which you would have to handle20:24
flaper87jeblair: fair enough20:24
lifelessflaper87: the risk there goes WAY down20:24
lifelessflaper87: and we're only waiting on pip 7.1 now20:24
jeblairlifeless: ++20:24
flaper87lifeless: roger, that's good to here :)20:24
lifelessflaper87: then there are two patches to merge, and we're live.20:24
fungifor reference, not including -attic repos we have 368 in openstack.* and 313 in stackforge at present20:24
*** marrusl has quit IRC20:24
jeblairttx: yeah, so i think i have what i need to sythesize a new rev20:24
lifeless[there'll be rough edges for a while of course, and we need to expand the inverse test matrix, but the core will locked down straight up]20:25
jeblairthis has been really helpful20:25
*** weshay has quit IRC20:26
*** weshay has joined #openstack-meeting20:26
ttxjeblair: ok, that discussion will be back20:27
jeblairyep, look for a new rev by next week20:27
*** jhenner has quit IRC20:27
ttx#topic Be less proscriptive about new team size/maturity20:28
*** openstack changes topic to "Be less proscriptive about new team size/maturity (Meeting topic: tc)"20:28
ttx#link https://review.openstack.org/19355020:28
ttxLooks like this one already has all the votes it will ever need20:28
*** jungleboyj has quit IRC20:28
ttxObjection to me merging it now ?20:28
russellb... no.20:28
*** lapalm has joined #openstack-meeting20:28
russellbjust wanted to argue about something.20:28
ttxI have the right topic for you to do that20:29
russellboh cool20:29
ttx#topic Fix typo to 'Bare metal service'20:29
*** openstack changes topic to "Fix typo to 'Bare metal service' (Meeting topic: tc)"20:29
ttx#link https://review.openstack.org/19423020:29
ttxThis one sounds like it should have been fast-tracked as a typo fix, but it triggered a lively discussion20:29
russellbthis one set a new record for amount of discussion to (apparent) triviality of the patch20:29
agentlettx: I have a legal question in to the Foundation now20:29
ttxagentle: around?20:29
dhellmannI'm inclined to trust annegentle and the docs team on this one20:29
ttxI'm happy to defer to Anne and/or the docs team on that one20:30
russellbdhellmann: +120:30
*** lapalm has quit IRC20:30
russellbttx: +120:30
agentleit's non-trivial for all the existing docs20:30
ttxIf it's a typo, it's a typo and we can merge it. If it's not a typo, they know20:30
russellbagentle: yeah, makes sense20:30
agentleit's not a typo20:30
ttxin any case there is no point in us voting or discussing it ?20:30
*** lapalm has joined #openstack-meeting20:30
russellbthere's some inconsistency in the file then20:30
agentlerussellb: yeah my hope is to clear that up with set guidelines20:30
agentlettx: not yet20:30
russellbyeah, appreciate that, you cleared it up in comments20:31
*** tpatil has joined #openstack-meeting20:31
agentleone point of discussion - generally speaking I do want the TC to be in the business of naming reviews, is that okay generally? Reasons not to?20:31
agentlethinking of it for the service catalog service type discussion and microversions for example20:31
*** dprince has quit IRC20:31
ttxagentle: if we reuse the name in that file for service catalog, I think you're right20:32
jaypipesagentle: ++20:32
russellbservice catalog sounds like cross project spec kind of thing20:32
agentleI think it was either russellb or sdague who pointed out we'll have more than one service once competing solutions enter20:32
agentlerussellb: it is20:32
dhellmannagentle: are you proposing that we register service catalog names in the governance repo?20:33
agentlerussellb: and in that spec I want to assert that "TC names" with the idea that projects.yaml is the naming source of truth20:33
* dhellmann hasn't been following that discussion20:33
agentledhellmann: proposing that projects.yaml is the naming source of truth20:33
agentleyeah, want to hear from you all on that ^^20:33
agentleThe caveat is the legal implications of course, but I'm seeking clarity.20:34
dhellmannalthough I think we probably want another field other than this descriptive name for the service catalog names </bikeshed>20:34
agentlequeue indigo girls20:34
agentledhellmann: HEH20:34
*** _nadya_ has joined #openstack-meeting20:34
ttxdhellmann: I tend to agree that every time we've used the same field for two things, we regretted it20:34
jbryceagentle: i don’t think i saw your legal question yet. what’s the high level?20:34
*** lapalm_ has joined #openstack-meeting20:34
*** lapalm has quit IRC20:34
agentlejbryce: sure, it's this: does capitalization of the second (or third) word in the service name have any legal implication?20:35
dhellmannand I'm yet to be convinced that new projects shouldn't just be using their name, but I'll hold off on a final opinion until there's a formal spec put together for that20:35
agentlejbryce: we have Block Storage and Object Storage but also Bare metal and Application catalog20:35
dhellmannjbryce: i.e., "Bare metal" vs. "Bare Metal"20:35
*** e0ne has quit IRC20:35
jbryceagentle: just found the ticket. i’m pretty confident the answer is no as long as you don’t pre-pend OpenStack20:35
agentlePreviously we've avoided "cognitive burden" of knowing whether to capitalize say the V in Key-Value by saying only the first letter should be capitalized.20:35
*** VanL has joined #openstack-meeting20:36
* dhellmann imagines a world of project names in ALL CAPS for the same reason20:36
agentlejbryce: so then I'll just have to decide whether Storage set us up for a lifetime of capitalization rules :)20:36
agentleI still don't know whether it's Key-value Store or Key-Value Store even with capitalization rules20:36
ttxdhellmann: but then people think it's an acronym. Like OSLO20:36
* ttx trolls20:37
dhellmannagentle: which project is that?20:37
* zaneb is thoroughly sick of people shouting HEAT at him20:37
ttxdhellmann: MagnetoDB20:37
*** jtomasek has quit IRC20:37
*** rbak has quit IRC20:37
ttxzaneb: I never knew what it stood for.20:37
zanebttx: don't you start20:38
jgriffithagentle: you mean lOl I think20:38
agentleSadly, my technical editor at work wants Application Catalog and Bare Metal :)20:38
ttxagentle: anything else on that one ? Sounds like you have it under control20:38
dhellmanncan we "fix" them all in one patch?20:38
agentledhellmann: yeah20:38
agentledhellmann: then go to the docs, sigh :)20:38
agentlettx: I think so20:38
agentlethanks for bringing it up :)20:38
*** vivek-ebay has quit IRC20:39
ttxOK, the next topic on the agenda was the Akanda proposal, but it was very recently WIPped20:39
ttxwhile they address the trademark / use company name as project name question20:39
*** jhenner has joined #openstack-meeting20:39
*** _nadya_ has quit IRC20:39
ttxSo I propose we skip it and reconsider it when it's final and un-WIPped20:39
sarobgood for me20:39
lifeless101 clearly.20:39
dhellmannagentle: let's talk offline about ways to make substitutions like that simpler in rst20:39
lifelessThen we don't need to worry about capitalisation20:39
ttxLet me see if we can get another patch to replace it on the agenda20:39
*** _nadya_ has joined #openstack-meeting20:40
maishskI just hope that we do not turn into the little v vs. the big V debate (from the vSphere world)20:40
russellbadding neutron to compute starter kit?20:40
* maishsk ducks and runs for cover… ;)20:40
ttxhttps://review.openstack.org/#/c/195771/ sounds like a good candidate20:40
russellbah yes, that one first20:40
jeblairTopic       lastday20:40
ttxsince it was proposed in time --  any objection to discussing it now ?20:40
jeblairif we don't approve it, does jogo have to stay around?20:40
russellbprops for doing real work until the end :)20:41
ttxchanging the world until the last day20:41
jeblairokay, actually, i think that it was intentional20:41
ttxI'll take that as a yes20:41
ttx#topic Fix up the compute starter kit tag20:41
*** openstack changes topic to "Fix up the compute starter kit tag (Meeting topic: tc)"20:41
ttx#link https://review.openstack.org/#/c/195771/20:41
jeblairi thought that the intent was to have real discussion on the application?20:42
ttxSo this patch basically applies the tag to the initial set of projects20:42
russellbyeah, i think we knew it hadn't been applied yet, because there was potential follow-up discussion yet, especially neutron20:42
russellbbut i think the initial set of projects here has consensus in any case20:42
russellbso +1 from me20:42
ttxIt is also use as a base for mordred's patch proposing neutron addition20:42
*** ijw has joined #openstack-meeting20:42
russellband the tag name seems fine20:42
jeblairat least, i think that some questions were deferred with "that can be dealt with in tag application"20:42
flaper87yeah, I'm good with that too20:42
ttxwhich should make for an interesting discussion, but next week20:42
ttxjeblair: right20:42
russellbfor some definition of interesting20:42
ttxjeblair: we said that the tag definition still needed to be applied20:43
*** mrmartin has quit IRC20:43
ttxand that we could rediscuss where it applies at that point. But I like the idea to iterate from the initial set proposed in the definition20:43
jeblairk, just mostly wanted to make the point that i don't think this was an oversight, and that we are expected to apply discretion to this :)20:43
zanebI thought we had explicitly endorsed a tag starting with compute: during the previous discussion20:44
*** amit213 has quit IRC20:44
russellbif anyone would like to talk some more about current neutron state, i'm happy to chat out-of-meeting, if that'd help develop opinions on this neutron thing, i've been trying to follow much more closely lately20:44
*** amit213 has joined #openstack-meeting20:44
*** _nadya_ has quit IRC20:44
*** amit213 has quit IRC20:44
ttxzaneb: I don't remember that... the prefix is a category thing, so compute: wouldn't make that much sense there ?20:44
russellbyeah, starter-kit makes sense as the category20:45
zanebmaybe it should just be compute-starter-kit?20:45
ttxWe have majority at this point20:45
russellbor i guess it could be even more general, "group:compute-starter-kit"20:45
russellbbut meh20:45
*** khaldrogox has quit IRC20:45
russellbthis wfm20:45
ttxzaneb: that is an option, but that can be proposed/discussed as a separate patch20:45
*** ivasev has quit IRC20:45
*** khaldrogox has joined #openstack-meeting20:46
ttxAlright, I'll approve this in 30sec, get tyour last votes in20:46
*** lapalm_ has quit IRC20:46
*** VanL_ has joined #openstack-meeting20:46
ttxok done20:47
ttx#topic Workgroup reports20:47
*** openstack changes topic to "Workgroup reports (Meeting topic: tc)"20:47
ttx* Project Team guide workgroup20:47
ttxNo progress since last week. Was focused on liberty-1, should make more progress this week20:47
ttxAny suggestion on where we should publish it ?20:47
*** matrohon has joined #openstack-meeting20:47
flaper87I have a WIP patch that I'd be happy to start getting feedback on20:47
flaper87(if no one has)20:47
*** claudiub has joined #openstack-meeting20:47
lifelessrussellb: I'd like to do that.20:47
flaper87and I'm sorry for being late there20:47
lifelessrussellb: (chat)20:47
*** ociuhandu_ has joined #openstack-meeting20:48
ttxjeblair: IIRC you had an idea on where we should publish it20:48
agentledocs.openstack.org/project-team-guide? (that's original)20:48
jeblairttx: i can't remember :)  i like agentle's idea20:49
ttxThe infra guide is at docs.openstack.org/infra rather than docs.openstack.org/infra-guide20:49
agentlettx: they should rename it :)20:49
ttxblue pain t on my bikesheds20:49
agentleI kid!20:49
*** VanL has quit IRC20:49
jeblairyeah, we grabbed a subdir to hold all kinds of infra stuff20:49
*** toscalix has joined #openstack-meeting20:49
jeblairand by grabbed, i believe i mean, politely asked agentle for permission :)20:50
agentlejeblair: heh20:50
ttxjeblair: do you plan to work on the publication jobs ?20:50
jeblairttx: can do; let's just #info the location when we finish bikeshedding20:50
ttxI'll do a complete review of the current chapters to check we have enough to start talking about it20:50
ttxAny objection to docs.openstack.org/project-team-guide ?20:51
flaper87none from me20:51
agentlettx: as long as you promise never to rename to program-team-guide20:51
agentlepinky swear?20:52
ttx#agreed Project team guide to be published to docs.openstack.org/project-team-guide20:52
ttx* Communications workgroup20:52
ttxagentle, flaper87: your turn20:52
agentleany movement on M name?20:52
agentleand really that doesn't come from "us" per se20:52
agentledo we need a blog post this week?20:52
mordredI got feedback from lsell20:52
ttxagentle: lots of things approved, but not exactly exciting stuff20:53
agentleoh and I keep forgetting to tweet20:53
mordredthey are still working on it20:53
agentlemordred: okay20:53
agentleI think we could wait another week for compiled excitement20:53
flaper87not sure if it's worth working on one this week20:53
jbryceagentle: summary is the top 2 choices were quickly tm-ed out of contention. 3rd looks promising, waiting for detailed search20:53
agentlejbryce: ok thanks for that20:53
flaper87agentle: ++20:53
agentleflaper87: mind meld20:53
lifelessagentle: surely we can't 'go' that long without compilation ? :) <boom-tish>20:54
ttx* Other workgroups20:54
agentlelifeless: lol20:54
ttxAny progress in other workgroups ?20:54
lifelessarchitecture still hasn't gotten off the group20:54
*** gordc has joined #openstack-meeting20:54
lifelessthats on me and markmcclain to make a timeslice and get things really rolling. I've been focusing on getting the constraints cross-project omgosh stuff off my plate20:55
ttxOnce the peak of excitement is reached on project-team-guide is reached and I enter the valley of desillusion, I might help out there20:55
*** IlyaG has joined #openstack-meeting20:55
*** ociuhandu_ has quit IRC20:55
ttx#topic Open discussion20:55
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:55
russellbagentle: which docs rae you referring to on https://review.openstack.org/#/c/196438/ ?20:55
ttxThere was a post asking for volunteers for Travel support program20:55
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2015-June/000998.html20:55
ttxAnyone interested ?20:55
agentlerussellb: I haven't seen a coherent "this is how you do port assignment in neutron to make it like nova-net" nor a "how to migrate upgrade"20:56
russellbttx: i replied off list that i'm willing to do it20:56
dhellmannI replied off list20:56
jbryceall you have to do is agree to house a few summit attendees in your room! = )20:56
russellbagentle: migration/upgrade isn't relevant for a starting point tohugh20:56
agentlerussellb: but it's possible it's there and I've missed it so need links20:56
dhellmannjbryce: as long as they aren't in my carry-on20:56
russellbagentle: and the first part, i'm not sure i get, that's probably the most fundamental part of the neutron API20:56
agentlerussellb: mm20:56
*** elmiko has joined #openstack-meeting20:56
russellbcreating a port on a network?20:56
ttxjbryce: I learned that in Japan you pay hotel rooms by occupancy and not per room, which if true menas you wouldn't win a lot20:57
russellbthere has been discussion about provider networks, but that seems covered pretty nicely on http://docs.openstack.org/networking-guide/ scenarios 4a and 4b20:57
mordred4a and 4b are great20:57
russellbi'd encourage anyone who hasn't seen that guide to check it out20:58
*** radez is now known as radez_g0n320:58
mordredagentle: also, fwiw, shade makes nova-net look like neutron where possible20:58
ttxOn the travel support program I'll reach out to Shari and check she has enough, and if not do another round of volunteer fishing20:58
*** stevemar has quit IRC20:58
mordredagentle: in the instances where we're forced to interact with nova-net20:58
mordredagentle: might or might not be a useful collection of data for someone in terms of what dicts look like20:59
agentlerussellb: yeah networking guide is great so where does it say "if you just want a network do this for your users"20:59
ttxclouds make shade, shade makes cloud20:59
mordredrussellb: library that wraps python-*client with business logic to hide all the cloud differences20:59
russellbmordred: nice20:59
mordredrussellb: being used in upstream ansible openstack modules as well as nodepool20:59
russellbagentle: depends on the networking model you want to use20:59
agentleI remember a note in the etherpad, mordred you may have pointed it out, that people didn't know "oh don't worry about running out of IP addresses, you just do this thing"20:59
ttxOne minute warning. Anything else, anyone ?20:59
russellbthe nova-network equivalent is documented nicely in the provider networks part20:59
*** thangp has quit IRC20:59
agentlerussellb: so we need to say "use this scenario for a match with nova-net"20:59
russellbthe "give me a network" stuff is about tenant networks20:59
russellbwhich is something nova-network doesn't have21:00
russellbwell, not like neutron has it anyway21:00
agentlerussellb: ok, put a link in that review and I'm good to go once I look21:00
russellbit's different / more than nova-net21:00
ttxAlright, time is up21:00
agentleoh yeah I'm up next!21:00
ttxThanks everyone, I think we resorbed our backlog in one meeting.21:00
agentlenice work21:00
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"21:00
openstackMeeting ended Tue Jun 30 21:00:42 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-06-30-20.01.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-06-30-20.01.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-06-30-20.01.log.html21:00
ttxagentle: floor is yours.21:00
lifelessafk for a few,family21:01
*** SlickNik has joined #openstack-meeting21:01
agentlettx: is it crossproject or cross-project? Eavesdrop has both :(21:01
ttxcrossproject I think, let me check21:01
agentle#startmeeting crossproject21:02
openstackMeeting started Tue Jun 30 21:02:03 2015 UTC and is due to finish in 60 minutes.  The chair is agentle. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: crossproject)"21:02
agentlettx: yep21:02
openstackThe meeting name has been set to 'crossproject'21:02
lifelessis now21:02
*** matrohon has quit IRC21:02
edleafeagentle: Cross Project :)21:02
thingeewe need to have a meeting topic before we can decide that :)21:02
*** jorge_munoz has quit IRC21:02
* mestery waves21:02
ttxhttp://eavesdrop.openstack.org/#OpenStack_Cross-Project_Meeting  says crossproject21:02
agentleAgenda is here:21:02
agentle#link https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda21:02
ttxman I love this Gerrit-driven agenda thing.21:02
ttxI should do a lightning talk about it21:02
agentleAny team with an announcement?21:03
*** olaph has joined #openstack-meeting21:03
agentle#topic Team announcements21:03
*** openstack changes topic to "Team announcements (Meeting topic: crossproject)"21:03
agentlego ttx21:03
ttxOn the release management side, we pushed liberty-1 last week21:03
*** toscalix has quit IRC21:03
* Rockyg is still lurking21:03
ttxI think it went relatively well despite all the things we changed in the process21:03
ttxand is more fluid overall21:03
ttxWe'll likely summarize the plan for Kilo and Liberty stable point releases on a thread this week21:03
*** armax has quit IRC21:03
*** jorge_munoz has joined #openstack-meeting21:03
ttxdhellmann: anything to add ?21:03
*** ddieterly has joined #openstack-meeting21:03
fungioh, yeah icehouse branch eol this week21:03
* devananda lurks as well21:03
*** Prashant_ has quit IRC21:04
dhellmannttx: no, I think that covers it well21:04
ttxicehouse branch on ice21:04
dhellmannfungi: ++21:04
fungii'll be tagging and deleting stable/icehouse branches in all repos with the release:managed tag (which just got updated last meeting slot!)21:04
ttxfungi: just in time21:04
*** PrashantS has joined #openstack-meeting21:04
fungichallenges of the bigtop21:04
agentle#info liberty-1 release pushed last week, Thurs Jun 25 201521:04
agentle#link http://lists.openstack.org/pipermail/openstack-announce/2015-June/000391.html21:04
ttxthat is all I had21:04
agentle#info icehouse stable branch end-of-life this week21:05
*** jhfeng has joined #openstack-meeting21:05
edleafeicehouse to melt this week21:05
agentlettx: nice post at http://ttx.re/new-versioning.html21:05
ttxedleafe: I blame global warming21:05
agentle#link http://ttx.re/new-versioning.html21:05
fungito be fair, the branch already reached eol when 2014.1.5 was tagged a little over a week ago, this is just cleanup21:05
agentleDocs? Quality? Translation?21:05
*** aysyd has quit IRC21:06
agentleany announcements or general info to share?21:06
fungisecurity team got a specs repo this week i think21:06
funginot sure that's especially newsworthy21:06
*** john-davidge has joined #openstack-meeting21:07
*** casusbelli has quit IRC21:07
agentleNow I want to know what a diagonal team is21:07
agentleAnyone else?21:07
*** ni291187 has joined #openstack-meeting21:07
fungiorthogonal teams next21:07
dhellmanneveryone loves a good geometry joke21:08
agentleFor docs, we are making progress on API reference info: https://review.openstack.org/#/c/177934/21:08
agentleLots of goodness in there.21:08
*** PrashantS has quit IRC21:08
*** ni291187 has quit IRC21:08
*** vahidh has quit IRC21:09
agentleOkay, next up.21:09
fungidhellmann: i'll strive to keep my jokes as non-euclidian as possible21:09
agentle#topic Translation for non user facing messages21:09
*** openstack changes topic to "Translation for non user facing messages (Meeting topic: crossproject)"21:09
ttxnotmyname: any release date in sight ?21:09
ttxoops too late21:09
agentleLooks like yamamoto is not here?21:09
agentlewe can go back ttx if notmyname is around21:09
notmynamettx: no, not yet21:09
*** pvaneck has quit IRC21:09
*** singleth_ has quit IRC21:09
ttxack thx21:09
dhellmannttx: same question for devananda & ironic, I guess?21:09
*** puranamr has quit IRC21:10
ttxdhellmann: well, I suspect that spec is blocking21:10
dhellmannah, right21:10
ttxbut yeah, swift will likely no longer be special soon.21:10
devanandadhellmann: not imminent, but I believe we'd like to try out the new release model soonish, say, within the next month21:10
*** armax has joined #openstack-meeting21:11
dhellmanndevananda: ok. We're going to have to do some special work at that point, so we'll want some notice and to coordinate live with you when it happens.21:11
devanandadhellmann: so that we can get more comfortable with that process before the end of liberty21:11
devanandadhellmann: certainly21:11
dhellmanndevananda: tl;dr is we need to remove the version from setup.cfg as the next patch after the tag, so we need to make sure your gate doesn't have anything else in it at that moment, etc.21:11
* dhellmann is done21:12
agentlewithout yamamoto does anyone else want to talk about marking internal interface docstrings as not translatable?21:12
agentleDiscussion here:21:12
agentle#link https://review.openstack.org/#/c/185300/1//COMMIT_MSG21:12
ttxquestion in the agenda is:21:12
ttx"messages like the following should be translated or not, where the exception is merely a part of internal api and will never reach users? "21:13
lifelessand I'm back21:13
ttxraise ValueError("message")21:13
devanandaagentle: we're translating python docstrings??21:13
*** julim has quit IRC21:13
*** olaph has quit IRC21:13
bknudsonif the string isn't going to wind up in logs or getting returned to the user then no reason to mark it for translation21:13
ttxI guess we can discuss that question at least, even if he is not around21:13
dhellmannI'm not sure it's always easy to tell when an exception is guaranteed not to be put in front of a user21:13
*** olaph has joined #openstack-meeting21:13
dhellmannand I think that's garyk's point with the patch21:13
bknudsonexceptions have a way of getting in logs or returned when you don't expect it.21:13
dhellmannbknudson: right21:13
lifelessagentle: do you mean 'docstring' - the specific docs attached to python objects, or 'strings that provide documentation' which is quite different21:13
devanandaoh - exceptions, not doc string21:14
agentledevananda: ah sorry, right.21:14
dhellmannyeah, those are exception messages21:14
devananda++ to always translating them, even if you dont think they'll get logged21:14
ttxPersonally I'm always for limiting translations scope and increase quality over a smaller scope21:14
ttxie. 99% of A rather than 20% of A+B+C21:14
lifelessI don't see value in translating that one in a thousand case21:14
lifelessif its not intended for users21:14
ttxso that sounds like a bad trade-off to me. But then I'm not the target user21:15
dhellmannso which is worse, missing one because we think it's going to be internal-only or translating one that no one sees?21:15
devanandaagentle: aiui, we hve a policy right now that all exception messages should get translated21:15
bknudsonfor the specific exceptions in https://review.openstack.org/#/c/185300/1/neutron/ipam/__init__.py -- they look like they would be returned to the user.21:15
lifelessthen its likely a) hard to explain well to translators, b) likely to change a lot, c) having good google-juice on the original is key to help folk find solutions21:15
ttxdhellmann: if we routinely had 100% translations I'd say "missing one"21:15
bknudsonbut this is in neutron so I have no idea21:15
lifelessif its intended for users, its part of the UI and should be translated.21:15
ttxbut since we don't, I'd say "translating one that no one sees"21:15
dhellmannttx: good point, I don't know what level of coverage we have with translations21:16
lifelesstl;dr: I don't think being an exception, or not being one, is criteria for translation-or-not.21:16
*** cp16net has left #openstack-meeting21:16
*** jungleboyjIpad has joined #openstack-meeting21:16
agentleLooking at https://wiki.openstack.org/wiki/Translations/Infrastructure#Marked_for_translation I'm not sure what the policy is.21:16
devanandaloosening that to "well, only the ones you think users will see" is just going to muddy the waters and lead to untranslated exceptions eventually bubbling up21:16
dhellmannlifeless: right, I think the point with that general policy is that a developer working on a local bit of code can't always tell if an exception is going to be presented to someone or not, so we were trying to make a simple rule that could be followed21:16
agentledhellmann: I'm with you on simple rules21:17
lifelessdevananda: do we translate the api ?21:17
dhellmannalthough ttx's counter-argument is also compelling21:17
lifelesse.g. is /servers/ in nova translated?21:17
ttxdhellmann: 100% is pretty rare21:17
agentlelifeless: no21:17
*** claudiub has quit IRC21:17
lifelessso, we /don't/ have a rule that says 'everything users see is translated'21:17
agentlehow would we communicate the policy?21:17
bknudsonif they want to say that this string is never going to be seen then they can add a comment to the code that explains why it's not translated21:17
lifeless-> I don't see any specific concern about a user seeing a given untranslated string or not.21:17
agentlelifeless: other than the timewaste by translators21:18
agentlelifeless: which is I think the concern listed21:18
lifelessagentle: right - translating things that aren't intended for users is waste21:18
lifelessagentle: *I* think we're agreeing21:18
agentlelifeless: yeah I think so21:18
lifelesserm I *think* ...21:18
agentleso, how to communicate back?21:18
agentleon the review or?21:18
devanandalifeless: that's a straw man. human-readable exception and log messages are not API semantics21:18
agentlejust in the notes of this meeting?21:18
bknudsonlet's clarify the policy if we have one21:18
bknudsonthen point to the policy21:18
dhellmannwe have some policy-like statements in http://docs.openstack.org/developer/oslo.i18n/guidelines.html as well21:19
*** jungleboyjIpad has quit IRC21:19
lifelessdevananda: but so is 'some random exception might bubble up'. Its a corner case21:19
devanandalifeless: that guideline, last time I read it, clearly said all exception messages should be translated21:20
dhellmannagentle: I can update the oslo.i18n docs with a statement about minimizing translator burden vs. following simple rules for identifying translatable strings21:20
agentledhellmann: was just going to suggest something like that!21:20
johnthetubaguyseems like we should not translated exceptions, then stop them getting to users, but I guess its never that clear cut sadly21:20
lifelessdevananda: which guideline?21:20
devanandafeedback from developers within Ironic is that having a clear policy for when to mark strings for translation is helpful, especially for reviewers21:20
johnthetubaguydhellmann: +1 that plan21:20
agentle#action dhellmann to update the oslo.i18n docs with a statement about minimizing translator burden vs. following simple rules for identifying translatable strings21:20
devanandalifeless: the one dhellmann linked on eminut eago21:20
lifelessdevananda: ack; so it doesn't now.21:20
*** vahidh has joined #openstack-meeting21:21
dhellmanndevananda: were you referring to a policy written down somewhere other than the oslo.i18n docs or the wiki?21:21
lifelessdevananda: it documents how to do it, but not when21:21
*** pvaneck has joined #openstack-meeting21:21
johnthetubaguyI like the describing why21:21
johnthetubaguyprojects can then work out what that means for them21:21
lifelessthe policy is I think at the first line21:21
lifelessText messages the user sees via exceptions or API calls should be translated using ....21:21
devanandahuh...  my DNS is failing because VPN, so I'm having trouble finding the reference that I'm thinking of21:21
*** galstrom is now known as galstrom_zzz21:21
agentleI like "lead with the why"21:21
lifelesswhich is entirely reasonable IMO21:21
lifelessjohnthetubaguy: agentle: I support leading with why, too.21:22
lifelessanyhow, the neutron review seems to be user error strings21:22
agentleok, so I'll keep that action.21:22
lifelessits in an argument validation function21:22
devanandadhellmann: it was in the portion of docs (or wiki) which explained the difference between _LE, _LW, _LI, etc21:22
agentleany other discussion or action to take?21:22
lifelessso I think we should say:21:23
lifeless - that neutron patch is doing the right thing21:23
lifeless - projects can set their own specific rules, but our broad intent is only that strings intended for the user should be translated21:23
devanandalifeless: to clarify, end-user or operator?21:23
lifeless- (and if thats too hard to track in a given project, by all means say 'translate all' - but be aware of the load that imposes on reviewers21:24
thingeedevananda: http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html21:24
lifelessdevananda: good question21:24
johnthetubaguythingee: I was thinking about debug logs vs exceptions here, thats a good thing to raise21:24
lifelessdevananda: I don't know the prior discussions here, but I think an inclusive approach (end-user-or-operator) makes sense.21:24
bknudsonhttp://docs.openstack.org/developer/oslo.i18n/guidelines.html says debug is not translated21:24
lifelessexceptions for internal state signalling for instance are not intended for either of those users.21:25
*** sahid has quit IRC21:25
thingeedhellmann: perhaps our log guideline should be updated rather than the oslo doc? http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html21:25
agentlethingee: perhaps both21:25
dhellmannthingee: this isn't about logging, though21:25
thingeeor reference each other21:25
thingeelogging guidelines not about logging?21:25
bknudsontranslated messages also get returned to users21:26
dhellmannwe put the guidelines in the i18n docs because that's the tool we were using for translation21:26
agentledhellmann: +121:26
*** singlethink has joined #openstack-meeting21:26
bknudsone.g., for a keystone request if you set the accept-language you can get error messages back in your favorite language21:26
agentlebknudson: nice21:27
thingeedhellmann: I think it's good to talk about the tool and the modules then? I'm unsure if it's the right place for guidelines as the doc I raised which is about guidelines.21:27
agentleWe should also consider where the translation team will look for guidelines, perhaps the wiki?21:27
*** IlyaG has quit IRC21:28
*** rfolco has quit IRC21:28
agentleI'll let the i18n team look at these notes to see if they want to add anything to their wiki pages.21:28
agentleOk, moving on21:28
agentle#topic API WG spec review: Clarifications on state-conflicting requests21:28
*** openstack changes topic to "API WG spec review: Clarifications on state-conflicting requests (Meeting topic: crossproject)"21:29
*** vivek-ebay has joined #openstack-meeting21:29
agentle#link https://review.openstack.org/#/c/18009421:29
*** IlyaG has joined #openstack-meeting21:30
agentleThis is in freeze.21:30
*** maishsk has quit IRC21:30
elmikoassuming no arguements it will be merged on friday, iirc21:30
agentleso the API WG will use lazy consensus to merge if there are no objections21:30
agentleelmiko: that sounds right21:30
dhellmannupdated translation policy for review: https://review.openstack.org/19733921:31
etoewsall the gory details of the api wg merge process are here. http://specs.openstack.org/openstack/api-wg/process.html21:31
agentlethanks etoews21:31
*** maishsk has joined #openstack-meeting21:31
agentleOk, next topic21:32
agentle#topic Return request ID to caller (tpatil): Spec review21:32
*** openstack changes topic to "Return request ID to caller (tpatil): Spec review (Meeting topic: crossproject)"21:32
agentletpatil: around?21:32
tpatil#link: https://review.openstack.org/#/c/156508/21:32
tpatilDoug has given +2 on our spec21:32
tpatilNeed one more +2 from core reviewer, then I will request respective python clients PTL to approve blueprint so that we can start pushing patches21:32
agentlethanks tpatil!21:32
tpatilWe would be ready with implementation for python-glanceclient, python-cinderclient and python-neutronclient by end of this week and would start with python-novaclient early next week21:32
*** otter768 has joined #openstack-meeting21:32
*** john-davidge has quit IRC21:32
tpatilOnce get_previous_request_id method is available in all python client libraries then we can move on step 2 (another spec in future) of logging caller and caller request ids on the same log message if osprofiler doesn’t work out well21:33
dhellmannI'm pretty happy with that spec now. We should put it on the TC agenda for review, too.21:33
thingeedhellmann: +121:33
agentledhellmann: ok21:33
tpatilThanks Doug for reviewing the specs21:33
*** maishsk has quit IRC21:33
tpatilThat's all I wanted to update here21:33
agentleokay, sounds good tpatil21:34
agentlebknudson: did you have any discussion points (looking at the review)21:34
bknudsonagentle: I commented in the review21:34
*** IlyaG has quit IRC21:34
agentlebknudson: ok21:34
agentlewho adds to the TC agenda, ttx?21:35
agentle(I'm guessing)21:35
tpatilbknudson: We will reply to your comment soon21:35
*** ijw has quit IRC21:35
*** kylek3h has joined #openstack-meeting21:35
agentleOkay that was it for the Agenda topics, did anyone else have anything or should I open it up for open discussion?21:35
bknudsontpatil: thanks21:35
etoews1 thing21:36
jokke_tpatil: ping me when you need review for the glanceclient21:36
*** ijw has joined #openstack-meeting21:36
tpatiljokke_: Sure21:36
etoewsi'm thinking it's time to put the python openstack sdk in the big tent.21:36
*** hrou_ has joined #openstack-meeting21:36
*** hrou has quit IRC21:36
johnthetubaguytpatil: looks good from a nova point of view, good step forward21:36
agentleetoews: +121:37
ttxagentle: if not in a governance review, post to -tc list21:37
agentlettx: ok, thanks21:37
etoewsi'd raise a review to the governance repo21:37
edleafeetoews: it's wayyyy past time21:37
etoewsi just wanted to "check the temperature" on that here. any thoughts or feedback?21:38
bknudsonI thought it was already in the big tent21:38
agentle#action agentle to post to -tc list to add Return request ID to caller openstack-specs to TC meeting agenda21:38
ttxagentle: in the case of a cross-project spec I just pick them up when they collected a large number of +1s21:38
ttxi.e. when we can assume they have reached community consensus21:38
johnthetubaguyetoews: FWIW, I would like to see it official, like bknudson I kinda assumed it was already21:38
agentlebknudson: the openstackclient is21:38
Rockygetoews: just create the patch and it should happen PDQ21:39
edleafeyeah, this is the pure Python SDK21:39
edleafenot a CLI21:39
*** fifieldt has quit IRC21:39
*** IlyaG has joined #openstack-meeting21:39
johnthetubaguyedleafe: agreed21:39
*** ayoung has quit IRC21:39
*** kgroves has quit IRC21:39
bknudsoncan we kick the other clients out of the tent?21:39
edleafebknudson: don't be mean!21:39
fungiat one point osc and the unified sdk devs had sort of joined forces, but it's not clear that continued and it's at least not formalized21:39
fungidtroyer: ^ ?21:40
dtroyerbknudson: not _quite_ yet…21:40
*** jungleboyjiPad has joined #openstack-meeting21:40
dtroyerit wasn't until YVR that we felt SDK was ready to be included in a shipping client21:40
etoewswe've got a roadmap to 1.0 now21:40
dtroyerthat hasn't started yet but we plan to start soon21:41
*** peristeri has quit IRC21:41
bknudsonwe need to get our keystoneauth library out21:41
*** barker has joined #openstack-meeting21:41
etoewsthat would be helpful21:41
agentleis keystoneauth a dependency though?21:41
agentleor nice-to-have21:42
*** kylek3h has quit IRC21:42
etoewsokay. so the temperature is warm. :)21:43
dtroyerit will be a dependency21:43
agentledtroyer: ok21:43
agentleetoews: lukewarm? :)21:43
* etoews dips hand in again21:43
*** kylek3h has joined #openstack-meeting21:43
agentleetoews: texas-summer-warm21:43
agentleok, I'll open it up21:43
dtroyeragentle: +121:43
*** aimon has quit IRC21:43
agentle#topic Open Discussion21:43
*** openstack changes topic to "Open Discussion (Meeting topic: crossproject)"21:43
agentlethanks etoews and dtroyer21:43
*** echoingumesh has quit IRC21:44
agentleI don't know how many heard in the TC meeting we're still awaiting M name, 1 and 2 are trademark, 3 is looking up.21:44
* agentle hasn't even looked up 3 yet21:44
dtroyerm3 is taken by BMW21:44
*** vivek-ebay has quit IRC21:45
johnthetubaguydtroyer: lol21:45
*** isviridov is now known as isviridov_away21:45
dhellmannthat's an unrelated field, though, so I think we're ok21:45
bknudsonperformance release for that release21:45
bknudsonfocus on performance for that release21:45
*** puranamr has joined #openstack-meeting21:45
agentleAlright do I get a cookie if we finish early?21:45
Rockygdtroyer: I thought there was actually a trademark fight over that between BMW and someone else?21:45
johnthetubaguyI want to do 5 milestones...21:45
*** ddieterly has quit IRC21:45
agentleOr a penalty flag?21:45
etoewscookie cookie cookie21:46
dtroyerRockyg: I wouldn't be surprised, don't recall21:46
johnthetubaguyI have been told its called an early mark21:46
johnthetubaguyno idea what that is21:46
*** ijw_ has joined #openstack-meeting21:46
agentleI have never heard of an early mark in all my word nerdery days.21:46
*** ociuhandu has joined #openstack-meeting21:46
agentlealrighty then!21:46
*** amitgandhinz has quit IRC21:46
agentleThanks everyone.21:46
agentleLooking for someone to run this meeting next week, let ttx know if you're interested. He sends training guides AND reminders.21:47
ttxThanks agentle!21:47
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"21:47
openstackMeeting ended Tue Jun 30 21:47:18 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-06-30-21.02.html21:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-06-30-21.02.txt21:47
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-06-30-21.02.log.html21:47
*** gordc has left #openstack-meeting21:47
ttxjust add yourself there ^21:47
*** jhfeng has left #openstack-meeting21:47
*** kylek3h has quit IRC21:47
agentleoh good we do have someone for next week, next opportunity is July 2121:47
*** puranamr has quit IRC21:47
*** kairat_kushaev has quit IRC21:47
*** puranamr has joined #openstack-meeting21:48
*** elmiko has left #openstack-meeting21:49
*** skraynev has quit IRC21:49
*** sreshetnyak has quit IRC21:49
*** enikanorov_ has quit IRC21:49
*** obondarev has quit IRC21:49
*** ijw has quit IRC21:50
*** khaldrogox has quit IRC21:50
*** barker has quit IRC21:50
*** fifieldt has joined #openstack-meeting21:52
*** henrynash has quit IRC21:52
*** fallenpegasus has joined #openstack-meeting21:56
*** jecarey has quit IRC21:57
*** JRobinson__ has joined #openstack-meeting21:58
*** ddieterly has joined #openstack-meeting21:58
*** banix has quit IRC21:58
*** ihrachyshka has quit IRC21:58
*** agentle has quit IRC21:59
*** puranamr has quit IRC21:59
*** frobware_ has quit IRC21:59
*** IlyaG has quit IRC21:59
*** jruano has quit IRC21:59
*** ddieterly has quit IRC21:59
*** VanL_ has quit IRC22:00
*** otter768 has quit IRC22:00
*** IlyaG has joined #openstack-meeting22:02
*** dane_leblanc has joined #openstack-meeting22:02
*** spzala has quit IRC22:04
*** kebray has joined #openstack-meeting22:04
*** yamahata has quit IRC22:04
*** suro-patz1 has joined #openstack-meeting22:05
*** puranamr has joined #openstack-meeting22:05
*** ijw_ has quit IRC22:06
*** aimon has joined #openstack-meeting22:07
*** ijw has joined #openstack-meeting22:07
*** gokrokve has quit IRC22:07
*** hrou_ has quit IRC22:11
*** suro-patz1 has left #openstack-meeting22:11
*** claudiub has joined #openstack-meeting22:12
*** Rockyg has quit IRC22:12
*** carl_baldwin has quit IRC22:13
*** ctrath has quit IRC22:15
*** olaph has quit IRC22:15
*** olaph has joined #openstack-meeting22:15
*** tpatil has quit IRC22:18
*** dims_ has joined #openstack-meeting22:19
*** dims has quit IRC22:22
*** gokrokve has joined #openstack-meeting22:22
*** pleia2 has quit IRC22:23
*** JRobinson__ has quit IRC22:25
*** pleia2 has joined #openstack-meeting22:25
*** aimon has quit IRC22:25
*** bknudson has quit IRC22:26
*** carl_baldwin has joined #openstack-meeting22:26
*** safchain has joined #openstack-meeting22:26
*** JRobinson__ has joined #openstack-meeting22:29
*** ayoung has joined #openstack-meeting22:29
*** carl_baldwin has quit IRC22:31
*** jgrimm is now known as zz_jgrimm22:31
*** KunalGan_ has joined #openstack-meeting22:32
*** barker has joined #openstack-meeting22:34
*** neelashah1 has quit IRC22:34
*** aimon has joined #openstack-meeting22:34
*** kebray has quit IRC22:35
*** KunalGandhi has quit IRC22:35
*** ninag has joined #openstack-meeting22:36
*** singlethink has quit IRC22:36
*** rossella_s has quit IRC22:36
*** dontalton has quit IRC22:37
*** rossella_s has joined #openstack-meeting22:37
*** olaph has quit IRC22:38
*** DericHorn-HP has joined #openstack-meeting22:38
*** zz_jgrimm is now known as jgrimm22:40
*** ayoung has quit IRC22:41
*** julim has joined #openstack-meeting22:43
*** kylek3h has joined #openstack-meeting22:43
*** gokrokve has quit IRC22:44
*** vivek-ebay has joined #openstack-meeting22:45
*** jruano has joined #openstack-meeting22:45
*** adahms has joined #openstack-meeting22:48
*** safchain has quit IRC22:48
*** vivek-ebay has quit IRC22:50
*** nelsnels_ has joined #openstack-meeting22:50
*** rbak has joined #openstack-meeting22:52
*** barker has quit IRC22:52
*** eharney has quit IRC22:53
*** nelsnelson has quit IRC22:53
*** larainema has quit IRC22:54
*** otter768 has joined #openstack-meeting22:56
*** IlyaG has quit IRC22:56
*** MaxPC has quit IRC22:57
*** jruano has quit IRC22:57
*** jungleboyj has joined #openstack-meeting22:57
*** dane_leblanc has quit IRC22:58
*** esheffield has quit IRC23:01
*** safchain has joined #openstack-meeting23:01
*** dims_ has quit IRC23:01
*** vivek-ebay has joined #openstack-meeting23:02
*** carl_baldwin has joined #openstack-meeting23:02
*** carl_baldwin has quit IRC23:03
*** markvoelker_ has quit IRC23:06
*** balajiiyer has joined #openstack-meeting23:06
*** tsbot_ has quit IRC23:07
*** ninag has quit IRC23:08
*** sarob_ has joined #openstack-meeting23:08
*** hrou has joined #openstack-meeting23:09
*** kylek3h_ has joined #openstack-meeting23:09
*** kylek3h has quit IRC23:10
*** pratap has quit IRC23:11
*** rbak has quit IRC23:12
*** sarob has quit IRC23:14
*** mwagner_lap has quit IRC23:15
*** sarob_ is now known as sarob23:16
*** hichihara has joined #openstack-meeting23:20
*** sarob_ has joined #openstack-meeting23:21
*** claudiub_ has joined #openstack-meeting23:23
*** kylek3h_ has quit IRC23:23
*** krtaylor has quit IRC23:23
*** hemna is now known as hemnafk23:24
*** IlyaG has joined #openstack-meeting23:25
*** balajiiyer has quit IRC23:25
*** claudiub has quit IRC23:25
*** safchain has quit IRC23:26
*** IlyaG has quit IRC23:26
*** IlyaG has joined #openstack-meeting23:27
*** sarob_ has quit IRC23:27
*** yamahata has joined #openstack-meeting23:28
*** ijw_ has joined #openstack-meeting23:28
*** radek_ has quit IRC23:29
*** DericHorn-HP has quit IRC23:31
*** ijw has quit IRC23:31
*** dannywilson has quit IRC23:35
*** puranamr has quit IRC23:36
*** puranamr has joined #openstack-meeting23:37
*** tochi has joined #openstack-meeting23:40
*** _nadya_ has joined #openstack-meeting23:40
*** VanL has joined #openstack-meeting23:40
*** krtaylor has joined #openstack-meeting23:41
*** dannywilson has joined #openstack-meeting23:43
*** _nadya_ has quit IRC23:45
*** dims has joined #openstack-meeting23:45
*** dims has quit IRC23:46
*** markvoelker has joined #openstack-meeting23:47
*** _amrith_ is now known as amrith23:47
*** ijw has joined #openstack-meeting23:48
*** IlyaG_ has joined #openstack-meeting23:50
*** jruano has joined #openstack-meeting23:50
*** marun has quit IRC23:51
*** ijw_ has quit IRC23:51
*** IlyaG has quit IRC23:52
*** ozstacker_ has joined #openstack-meeting23:53
*** dannywilson has quit IRC23:54
*** yamada-h has joined #openstack-meeting23:54
*** dannywilson has joined #openstack-meeting23:54
*** garthb has quit IRC23:54
*** garthb__ has quit IRC23:54
*** htruta_ has joined #openstack-meeting23:57
*** VanL has quit IRC23:57
*** ozstacker has quit IRC23:57
*** yamada-h has quit IRC23:59

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