Tuesday, 2015-08-04

*** haomaiwa_ has quit IRC00:01
*** KunalGandhi has quit IRC00:01
*** edleafe has quit IRC00:01
*** adahms has joined #openstack-meeting00:02
*** haomaiwang has joined #openstack-meeting00:02
*** sridhar_ram has quit IRC00:02
*** edleafe has joined #openstack-meeting00:03
*** KunalGandhi has joined #openstack-meeting00:04
*** xingchao has quit IRC00:05
*** achanda has quit IRC00:06
*** padkrish has joined #openstack-meeting00:08
*** pvaneck has quit IRC00:10
*** darrenc_afk is now known as darrenc00:11
*** cdub has quit IRC00:14
*** jaypipes has quit IRC00:18
*** puranamr has quit IRC00:19
*** DericHorn-HP has quit IRC00:19
*** garthb has quit IRC00:20
*** shadower has quit IRC00:23
*** shadower has joined #openstack-meeting00:23
*** otter768 has joined #openstack-meeting00:26
*** cing has joined #openstack-meeting00:26
*** dannywilson has quit IRC00:26
*** dmorita has quit IRC00:29
*** tsekiyam_ has joined #openstack-meeting00:30
*** salv-orlando has quit IRC00:31
*** lukebroo_ has joined #openstack-meeting00:32
*** puranamr has joined #openstack-meeting00:33
*** tsekiyama has quit IRC00:34
*** lukebrooker has quit IRC00:34
*** banix has joined #openstack-meeting00:35
*** dmacpher-afk has quit IRC00:35
*** yingjun has joined #openstack-meeting00:35
*** ricolin has joined #openstack-meeting00:35
*** yingjun_ has joined #openstack-meeting00:37
*** geoffarnold has quit IRC00:38
*** ddieterly has joined #openstack-meeting00:40
*** yingjun has quit IRC00:40
*** noslzzp has quit IRC00:40
*** IlyaG has quit IRC00:43
*** ^Gal^ has joined #openstack-meeting00:44
*** yamamoto has joined #openstack-meeting00:44
*** padkrish has quit IRC00:44
*** epico has joined #openstack-meeting00:44
*** lukebroo_ has quit IRC00:45
*** dmacpher-afk has joined #openstack-meeting00:46
*** Apoorva has joined #openstack-meeting00:48
*** yamamoto has quit IRC00:49
*** MarkAtwood has quit IRC00:49
*** ajmiller has quit IRC00:49
*** mtanino has quit IRC00:51
*** Apoorva has quit IRC00:52
*** IlyaG has joined #openstack-meeting00:53
*** zhhuabj has quit IRC00:53
*** erlon has quit IRC00:53
*** Apoorva has joined #openstack-meeting00:54
*** alop has quit IRC00:55
*** Apoorva has quit IRC00:55
*** padkrish has joined #openstack-meeting00:55
*** topol has joined #openstack-meeting00:55
*** tiswanso has joined #openstack-meeting00:55
*** tiswanso has quit IRC00:58
*** crc32 has joined #openstack-meeting00:58
*** tiswanso has joined #openstack-meeting00:58
*** Apoorva has joined #openstack-meeting00:59
*** topol has quit IRC01:00
*** haomaiwang has quit IRC01:01
*** haomaiwang has joined #openstack-meeting01:02
*** MarkAtwood has joined #openstack-meeting01:02
*** adahms has quit IRC01:02
*** IlyaG has quit IRC01:03
*** xingchao has joined #openstack-meeting01:04
*** leeantho has quit IRC01:05
*** dmorita has joined #openstack-meeting01:05
*** lukebrooker has joined #openstack-meeting01:07
*** MarkAtwood has quit IRC01:07
*** zhhuabj has joined #openstack-meeting01:07
*** Rockyg has quit IRC01:07
*** puranamr has quit IRC01:08
*** krypton has quit IRC01:10
*** dneary has joined #openstack-meeting01:13
*** xingchao has quit IRC01:13
*** yunpengl has joined #openstack-meeting01:13
*** sdake_ has quit IRC01:15
*** sdake has joined #openstack-meeting01:16
*** ^Gal^ has quit IRC01:16
*** padkrish has quit IRC01:20
*** ijw has joined #openstack-meeting01:21
*** dneary has quit IRC01:22
*** ijw_ has quit IRC01:23
*** baoli has joined #openstack-meeting01:25
*** Apoorva has quit IRC01:26
*** Daisy has joined #openstack-meeting01:28
*** puranamr has joined #openstack-meeting01:29
*** SourabhP has quit IRC01:32
*** salv-orlando has joined #openstack-meeting01:33
*** tsekiyam_ has quit IRC01:33
*** puranamr has quit IRC01:33
*** Daisy has quit IRC01:33
*** ijw has quit IRC01:34
*** tsekiyama has joined #openstack-meeting01:34
*** tsekiyama has quit IRC01:34
*** Daisy has joined #openstack-meeting01:34
*** tsekiyama has joined #openstack-meeting01:34
*** cing has quit IRC01:35
*** JRobinson__ has joined #openstack-meeting01:36
*** fitoduarte has quit IRC01:39
*** Daisy has quit IRC01:39
*** tsekiyama has quit IRC01:39
*** salv-orlando has quit IRC01:41
*** galstrom_zzz is now known as galstrom01:42
*** tobe_ has joined #openstack-meeting01:46
*** s3wong has quit IRC01:47
*** neelashah has joined #openstack-meeting01:48
*** cing has joined #openstack-meeting01:48
*** otter768 has quit IRC01:49
*** asselin has quit IRC01:53
*** IlyaG has joined #openstack-meeting01:53
*** sreshetnyak has quit IRC01:53
*** obondarev_ has quit IRC01:54
*** Apoorva has joined #openstack-meeting01:54
*** skraynev has quit IRC01:54
*** ityaptin has quit IRC01:55
*** ddieterly has quit IRC01:55
*** dmacpher-afk has quit IRC01:55
*** changzhi has joined #openstack-meeting01:56
*** sankarshan_away is now known as sankarshan01:56
*** ivar-laz_ has joined #openstack-meeting01:57
*** MarkAtwood has joined #openstack-meeting01:57
*** yunpengl has quit IRC01:57
*** spzala has quit IRC01:58
*** Daisy has joined #openstack-meeting02:00
*** ivar-lazzaro has quit IRC02:00
*** IlyaG has quit IRC02:00
*** haomaiwang has quit IRC02:01
*** novas0x2a|laptop has quit IRC02:01
*** ivar-laz_ has quit IRC02:01
*** Daisy has quit IRC02:01
*** Daisy has joined #openstack-meeting02:02
*** haomaiwang has joined #openstack-meeting02:02
*** Daisy has quit IRC02:02
*** Daisy_ has joined #openstack-meeting02:03
*** ub2 has quit IRC02:03
*** ub has joined #openstack-meeting02:04
*** baoli has quit IRC02:05
*** moha_hunt has quit IRC02:06
*** baoli has joined #openstack-meeting02:06
*** yamahata has quit IRC02:07
*** puranamr has joined #openstack-meeting02:10
*** gyee has quit IRC02:11
*** dmorita has quit IRC02:13
*** ddieterly has joined #openstack-meeting02:14
*** puranamr has quit IRC02:15
*** xingchao has joined #openstack-meeting02:16
*** sbalukoff has quit IRC02:17
*** yamamoto has joined #openstack-meeting02:21
*** puranamr has joined #openstack-meeting02:22
*** puranamr has quit IRC02:27
*** ajmiller has joined #openstack-meeting02:30
*** Apoorva has quit IRC02:33
*** dmacpher has joined #openstack-meeting02:34
*** galstrom is now known as galstrom_zzz02:35
*** unicell1 has quit IRC02:37
*** changzhi has quit IRC02:38
*** salv-orlando has joined #openstack-meeting02:40
*** noslzzp has joined #openstack-meeting02:40
*** _amrith_ is now known as amrith02:42
*** harshs has quit IRC02:42
*** PrashantS has joined #openstack-meeting02:44
*** adahms has joined #openstack-meeting02:45
*** achanda has joined #openstack-meeting02:45
*** BobBall_ is now known as BobBall02:46
*** sdake has quit IRC02:48
*** PrashantS has quit IRC02:49
*** salv-orlando has quit IRC02:49
*** lukebrooker has quit IRC02:49
*** PrashantS has joined #openstack-meeting02:49
*** PrashantS has quit IRC02:54
*** tobe_ has quit IRC02:54
*** vivek-ebay has quit IRC02:54
*** dims has joined #openstack-meeting02:54
*** KunalGandhi has quit IRC02:55
*** crc32 has quit IRC02:57
*** Prashant_ has joined #openstack-meeting03:00
*** haomaiwang has quit IRC03:01
*** vivek-ebay has joined #openstack-meeting03:01
*** haomaiwang has joined #openstack-meeting03:02
*** vivek-ebay has quit IRC03:05
*** cing has quit IRC03:05
*** lpetrut has joined #openstack-meeting03:07
*** eliqiao has joined #openstack-meeting03:13
*** DericHorn-HP has joined #openstack-meeting03:13
*** lukebrooker has joined #openstack-meeting03:14
*** BharatK has quit IRC03:15
*** dims has quit IRC03:15
*** IlyaG has joined #openstack-meeting03:16
*** sdake has joined #openstack-meeting03:16
*** changzhi has joined #openstack-meeting03:17
*** Daisy_ has quit IRC03:20
*** Daisy has joined #openstack-meeting03:20
*** IlyaG has quit IRC03:22
*** Daisy has quit IRC03:23
*** Daisy has joined #openstack-meeting03:23
*** changzhi has quit IRC03:25
*** eliqiao has quit IRC03:25
*** DericHorn-HP has quit IRC03:27
*** eliqiao has joined #openstack-meeting03:29
*** ayoung has quit IRC03:30
*** Daisy has quit IRC03:32
*** Daisy has joined #openstack-meeting03:33
*** rfolco has quit IRC03:34
*** lukebrooker has quit IRC03:34
*** Prashant_ has quit IRC03:36
*** achanda has quit IRC03:37
*** PrashantS has joined #openstack-meeting03:37
*** eliqiao1 has joined #openstack-meeting03:37
*** Daisy has quit IRC03:37
*** sdake_ has joined #openstack-meeting03:38
*** eliqiao has quit IRC03:39
*** vincent_hou has joined #openstack-meeting03:40
*** PrashantS has quit IRC03:41
*** lukebrooker has joined #openstack-meeting03:41
*** Sukhdev has joined #openstack-meeting03:41
*** sdake has quit IRC03:41
*** eglynn_ has joined #openstack-meeting03:42
*** PrashantS has joined #openstack-meeting03:42
*** coolsvap|away is now known as coolsvap03:43
*** ajmiller_ has joined #openstack-meeting03:47
*** eglynn_ has quit IRC03:47
*** kumar has joined #openstack-meeting03:48
*** ajmiller has quit IRC03:48
*** otter768 has joined #openstack-meeting03:50
*** salv-orlando has joined #openstack-meeting03:50
*** ajmiller_ has quit IRC03:51
*** JRobinson__ is now known as JRobinson__afk03:51
*** yingjun_ has quit IRC03:53
*** afazekas has joined #openstack-meeting03:54
*** otter768 has quit IRC03:55
*** tiswanso has quit IRC03:55
*** salv-orl_ has joined #openstack-meeting03:57
*** DericHorn-HP has joined #openstack-meeting03:57
*** salv-orlando has quit IRC03:57
*** amrith is now known as _amrith_03:57
*** cing has joined #openstack-meeting03:58
*** amotoki has joined #openstack-meeting03:59
*** yamamoto has quit IRC03:59
*** yamamoto has joined #openstack-meeting04:00
*** haomaiwang has quit IRC04:01
*** salv-orl_ has quit IRC04:01
*** neelashah has quit IRC04:01
*** haomaiwang has joined #openstack-meeting04:02
*** lpeer has quit IRC04:03
*** lpeer_ has joined #openstack-meeting04:03
*** carl_baldwin has joined #openstack-meeting04:05
*** vjay6 has joined #openstack-meeting04:05
*** eL_MoRRiS has joined #openstack-meeting04:06
*** eL_MoRRiS has left #openstack-meeting04:06
*** ivasev has joined #openstack-meeting04:06
*** noslzzp has quit IRC04:07
*** unicell has joined #openstack-meeting04:08
*** PrashantS has quit IRC04:09
*** PrashantS has joined #openstack-meeting04:09
*** sc68cal has quit IRC04:10
*** galstrom_zzz is now known as galstrom04:11
*** ivasev has quit IRC04:13
*** ivasev has joined #openstack-meeting04:13
*** ivasev has quit IRC04:14
*** ivasev has joined #openstack-meeting04:14
*** PrashantS has quit IRC04:14
*** Daisy has joined #openstack-meeting04:16
*** ddieterly has quit IRC04:17
*** IlyaG has joined #openstack-meeting04:18
*** vjay6 has quit IRC04:19
*** sc68cal has joined #openstack-meeting04:21
*** sc68cal has quit IRC04:21
*** sc68cal has joined #openstack-meeting04:21
*** achanda has joined #openstack-meeting04:21
*** xingchao has quit IRC04:21
*** carl_baldwin has quit IRC04:22
*** _amrith_ is now known as amrith04:24
*** vjay6 has joined #openstack-meeting04:25
*** carl_baldwin has joined #openstack-meeting04:25
*** DericHorn-HP has quit IRC04:26
*** vivek-ebay has joined #openstack-meeting04:30
*** harshs has joined #openstack-meeting04:32
*** achanda_ has joined #openstack-meeting04:35
*** achanda has quit IRC04:35
*** elo has quit IRC04:37
*** cing has quit IRC04:40
*** zhhuabj has quit IRC04:41
*** oomichi has joined #openstack-meeting04:45
*** julim has quit IRC04:47
*** maishsk has joined #openstack-meeting04:47
*** hrou has quit IRC04:49
*** IlyaG has quit IRC04:49
*** rjaiswal has quit IRC04:50
*** ivasev has quit IRC04:51
*** ivasev has joined #openstack-meeting04:52
*** sbalukoff has joined #openstack-meeting04:52
*** galstrom is now known as galstrom_zzz04:52
*** aukhan has joined #openstack-meeting04:53
*** vivek-eb_ has joined #openstack-meeting04:53
*** maishsk has quit IRC04:53
*** lpeer_ has quit IRC04:53
*** zhhuabj has joined #openstack-meeting04:53
*** Daisy has quit IRC04:54
*** pm90__ has quit IRC04:54
*** vivek-ebay has quit IRC04:54
*** Daisy has joined #openstack-meeting04:54
*** ivasev has quit IRC04:56
*** lpetrut has quit IRC04:58
*** vincent_hou has quit IRC04:59
*** salv-orlando has joined #openstack-meeting05:00
*** kumar has quit IRC05:00
*** haomaiwang has quit IRC05:01
*** Daisy has quit IRC05:01
*** 32NAAAL0S has joined #openstack-meeting05:02
*** amrith is now known as _amrith_05:05
*** carl_baldwin has quit IRC05:05
*** JRobinson__afk is now known as JRobinson__05:06
*** Daisy has joined #openstack-meeting05:09
*** changbl has joined #openstack-meeting05:09
*** harshs has quit IRC05:10
*** SridharG has joined #openstack-meeting05:11
*** salv-orlando has quit IRC05:13
*** vivek-ebay has joined #openstack-meeting05:13
*** fawadkhaliq has joined #openstack-meeting05:14
*** fawadk has joined #openstack-meeting05:15
*** vivek-ebay has quit IRC05:15
*** vivek-eb_ has quit IRC05:16
*** fawadkhaliq has quit IRC05:18
*** lpeer_ has joined #openstack-meeting05:20
*** irenab has joined #openstack-meeting05:20
*** lukebrooker has quit IRC05:22
*** sc68cal has quit IRC05:26
*** sc68cal has joined #openstack-meeting05:29
*** Daisy has quit IRC05:31
*** Daisy has joined #openstack-meeting05:32
*** yamamoto has quit IRC05:32
*** vjay6 has quit IRC05:34
*** tobe_ has joined #openstack-meeting05:36
*** MarkAtwood has quit IRC05:36
*** vincent_hou has joined #openstack-meeting05:36
*** MarkAtwood has joined #openstack-meeting05:36
*** Daisy has quit IRC05:37
*** lukebrooker has joined #openstack-meeting05:37
*** MarkAtwo_ has joined #openstack-meeting05:37
*** vincent_hou has quit IRC05:39
*** xingchao has joined #openstack-meeting05:41
*** Sukhdev has quit IRC05:41
*** MarkAtwood has quit IRC05:41
*** yamamoto has joined #openstack-meeting05:42
*** sudipto has joined #openstack-meeting05:44
*** puranamr has joined #openstack-meeting05:45
*** ddieterly has joined #openstack-meeting05:49
*** puranamr has quit IRC05:49
*** afazekas has quit IRC05:50
*** tobe_ has quit IRC05:50
*** otter768 has joined #openstack-meeting05:51
*** tobe_ has joined #openstack-meeting05:53
*** ddieterly has quit IRC05:53
*** otter768 has quit IRC05:55
*** Murali has joined #openstack-meeting05:55
*** Daisy has joined #openstack-meeting05:55
*** tobe_ has quit IRC05:58
*** yingjun has joined #openstack-meeting05:58
*** topol has joined #openstack-meeting05:58
*** yfried has joined #openstack-meeting06:00
*** Daisy has quit IRC06:00
*** Daisy has joined #openstack-meeting06:00
*** Daisy has joined #openstack-meeting06:01
*** Daisy has quit IRC06:01
*** Daisy has joined #openstack-meeting06:02
*** SumitNaiksatam has joined #openstack-meeting06:02
*** topol has quit IRC06:02
*** jtomasek has joined #openstack-meeting06:06
*** Daisy has quit IRC06:07
*** JRobinson__ has quit IRC06:07
*** MarkAtwo_ has quit IRC06:08
*** maishsk has joined #openstack-meeting06:09
*** salv-orlando has joined #openstack-meeting06:10
*** unicell1 has joined #openstack-meeting06:10
*** BharatK has joined #openstack-meeting06:12
*** unicell has quit IRC06:12
*** yingjun has quit IRC06:14
*** yingjun has joined #openstack-meeting06:14
*** vivek-ebay has joined #openstack-meeting06:16
*** yingjun has quit IRC06:19
*** vivek-ebay has quit IRC06:20
*** nadya has joined #openstack-meeting06:21
*** salv-orlando has quit IRC06:21
*** salv-orlando has joined #openstack-meeting06:22
*** jprovazn has joined #openstack-meeting06:25
*** belmoreira has joined #openstack-meeting06:31
*** KunalGandhi has joined #openstack-meeting06:31
*** yfried is now known as yfried|afk06:32
*** SourabhP has joined #openstack-meeting06:34
*** KunalGan_ has joined #openstack-meeting06:37
*** KunalGandhi has quit IRC06:38
*** ub has quit IRC06:39
*** yfried|afk is now known as yfried06:41
*** KunalGan_ has quit IRC06:42
*** _amrith_ is now known as amrith06:43
*** Daisy has joined #openstack-meeting06:44
*** zeih has joined #openstack-meeting06:44
*** lpeer_ has quit IRC06:44
*** MarkAtwood has joined #openstack-meeting06:47
*** yingjun has joined #openstack-meeting06:47
*** ddieterly has joined #openstack-meeting06:49
*** xingchao has quit IRC06:53
*** xingchao has joined #openstack-meeting06:54
*** yfried is now known as yfried|afk06:54
*** ddieterly has quit IRC06:54
*** jlanoux has joined #openstack-meeting07:00
*** achanda_ has quit IRC07:01
*** nadya has quit IRC07:02
*** yfried|afk is now known as yfried07:04
*** sahid has joined #openstack-meeting07:04
*** sahid has quit IRC07:04
*** sahid has joined #openstack-meeting07:07
*** yfried has quit IRC07:08
*** ityaptin has joined #openstack-meeting07:08
*** skraynev has joined #openstack-meeting07:08
*** jcoufal has joined #openstack-meeting07:09
*** ijw has joined #openstack-meeting07:09
*** sreshetnyak has joined #openstack-meeting07:10
*** fawadkhaliq has joined #openstack-meeting07:12
*** scheuran has joined #openstack-meeting07:14
*** sudipto has quit IRC07:14
*** fawadk has quit IRC07:14
*** ^Gal^_ has quit IRC07:15
*** ^Gal^ has joined #openstack-meeting07:15
*** fawadk has joined #openstack-meeting07:15
*** banix has quit IRC07:16
*** baoli has quit IRC07:17
*** baoli has joined #openstack-meeting07:18
*** fawadkhaliq has quit IRC07:18
*** Daisy has quit IRC07:19
*** Daisy has joined #openstack-meeting07:19
*** lukebrooker has quit IRC07:20
*** Daisy has quit IRC07:20
*** Daisy has joined #openstack-meeting07:20
*** baoli has quit IRC07:22
*** phil_ has joined #openstack-meeting07:26
*** skraynev has quit IRC07:26
*** skraynev has joined #openstack-meeting07:26
*** pbourke has quit IRC07:32
*** pbourke has joined #openstack-meeting07:33
*** dmacpher has quit IRC07:34
*** safchain has joined #openstack-meeting07:35
*** lsmola has joined #openstack-meeting07:42
*** nadya has joined #openstack-meeting07:43
*** ganeshna has joined #openstack-meeting07:44
*** jyuso1 has joined #openstack-meeting07:44
*** armax has quit IRC07:44
*** fawadk has quit IRC07:45
*** amrith is now known as _amrith_07:49
*** zz_ttrifonov is now known as ttrifonov07:49
*** ub has joined #openstack-meeting07:49
*** ddieterly has joined #openstack-meeting07:50
*** otter768 has joined #openstack-meeting07:51
*** ddieterly has quit IRC07:55
*** alexey_nex has joined #openstack-meeting07:56
*** otter768 has quit IRC07:56
*** _amrith_ is now known as amrith07:57
*** fawadkhaliq has joined #openstack-meeting07:57
*** yassine has joined #openstack-meeting08:01
*** yassine has quit IRC08:01
*** jyuso1 has left #openstack-meeting08:02
*** jyuso1 has joined #openstack-meeting08:02
*** Daisy has quit IRC08:03
*** yassine has joined #openstack-meeting08:03
anteaya#startmeeting third-party08:03
openstackMeeting started Tue Aug  4 08:03:23 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:03
*** openstack changes topic to " (Meeting topic: third-party)"08:03
openstackThe meeting name has been set to 'third_party'08:03
anteayahello08:03
*** Daisy has joined #openstack-meeting08:03
*** Daisy has quit IRC08:04
*** Daisy has joined #openstack-meeting08:04
anteayaanyone here for the third party meeting?08:04
lennybHi08:04
anteayahi lennyb08:04
anteayathanks for putting up the patch with akerr's work08:05
*** Daisy_ has joined #openstack-meeting08:05
alexey_nexhi08:05
anteayamuch appreciated08:05
anteayaalexey_nex: hello there08:05
anteayawelcome08:05
jyuso1anteaya: hi:)08:05
anteayahey jyuso108:05
anteayajyuso1: haven't seen you in a while08:05
anteayajyuso1: I see you are on the board now?08:06
*** fawadkhaliq has quit IRC08:06
alexey_nexthanks) i have a problem with glance randomly giving errors during tempest tests, anybody had such?08:06
alexey_nex2015-07-29 11:58:11.257 [00;32mDEBUG glance.common.client [ [01;36mreq-825f8c76-c054-4449-9131-564c459ac889 [00;36m11a3387959af4db096abc67471e936bf 3b609ce8278a4a80ac817509ec7bbd84 [00;32m] [01;35m [00;32mConstructed URL: http://127.0.0.1:9191/images/cirros-0.3.4-x86_64-uec-kernel [00m [00;33mfrom (pid=10759) _construct_url /opt/stack/glance/glance/common/client.py:402 [00m 2015-07-29 11:58:11.592 [01;31mERROR glance.r08:06
jyuso1anteaya: yes,I debug our ci environment these days.It's recover now.08:07
lennybanteaya: np, it can save a lot of false alarms. how can it be merged?08:07
anteayaalexey_nex: do you know how to use a paste service?08:07
alexey_nexnot rly...08:07
anteayalennyb: well we need some reviewers to come to agreement08:07
anteayaalexey_nex: go here: http://paste.openstack.org/08:08
anteayaalexey_nex: paste your stacktrace in the window and click the Paste! button08:08
*** Daisy has quit IRC08:08
anteayaalexey_nex: you will get a unique url, bring that back to channel and share the url with use08:09
anteayajyuso1: yay08:09
alexey_nexanteaya: thanks, here: http://paste.openstack.org/show/406832/08:10
*** nfedotov has joined #openstack-meeting08:10
alexey_nexthe problem is that this error comes up randomly with the same version of our driver08:11
alexey_nexand there are no errorrs in c-* logs08:11
*** SourabhP has quit IRC08:11
anteayaalexey_nex: have you looked at glance bug reports to see if anyone has reported this as a bug08:11
anteayaalexey_nex: and thank you for using paste08:12
alexey_nexanteaya: yes, didn't find such bug08:12
anteayaalexey_nex: okay great08:13
*** adahms has quit IRC08:13
*** yingjun has quit IRC08:14
*** jcoufal has quit IRC08:14
lennybalexey_nex: did you check/upgraded glance client ?08:14
anteayathis error comes up randomly with the same version of our driver, what do you mean by that?08:14
alexey_nexI mean that it can pass all tests successfully and then the next run without any changes it fails08:15
anteayathe next run08:15
anteayado you mean that you run the tests a second time on the same vm?08:16
alexey_nexlennyb: it appears on fresh devstack installs08:16
alexey_nexno, I always run them on a new vm08:16
anteayawhat do you mean by the next run then?08:16
lennybalexey_nex: clients are checked for minimum version and not being upgraded each time08:16
alexey_nexlennyb: but it's installed on a fresh ubuntu vm08:17
*** tobe_ has joined #openstack-meeting08:17
alexey_nexanteaya: I mean that i just try to successfully test mulptiple times, each time on a clean ubuntu vm08:18
anteayaso it sounds like a race condition08:18
*** yingjun has joined #openstack-meeting08:19
lennybalexey_nex: can it be a timing issue? the resource was not yet added or created. can you add a wait in your tests before the failure?08:19
alexey_nexI guess it could, how can i add a wait to tempest tests?08:20
anteayaalexey_nex: offer a patch to tempest08:20
alexey_nexah ok, I will try that08:21
anteayasounds good08:21
anteayaanything more on this?08:21
alexey_nexyes, thank you for the suggestion)08:21
anteayathanks for asking08:21
anteayaanything more?08:22
anteayanew topic?08:22
anteayadoes anyone have anything else they want to discuss?08:23
lennybanteaya: nothing to discuss. I will try to catch asselin and eantishev next time08:23
anteayalennyb: sounds like a plan, thank you08:23
anteayajyuso1: anything you would like to discuss today?08:23
*** amrith is now known as _amrith_08:24
anteayado we have anything else to talk about in this meeting?08:24
jyuso1anteaya: I don't have any other topic.Thanks:)08:25
anteayajyuso1: thank you08:25
anteayaany reason I should not close the meeting?08:25
anteayathank you everyone for your kind attendance and participation08:26
lennybthanks08:26
anteayasee you next week08:26
anteayathanks lennyb08:26
anteaya#endmeeting08:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:26
openstackMeeting ended Tue Aug  4 08:26:21 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-08-04-08.03.html08:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-08-04-08.03.txt08:26
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-08-04-08.03.log.html08:26
*** ijw has quit IRC08:29
*** lpeer_ has joined #openstack-meeting08:32
*** yingjun has quit IRC08:35
*** pbourke has quit IRC08:35
*** jckasper has quit IRC08:35
*** pedroalvarez has quit IRC08:35
*** hogepodge has quit IRC08:35
*** larainema has quit IRC08:35
*** ianw has quit IRC08:35
*** ajiang has quit IRC08:35
*** Yingxin has quit IRC08:35
*** federico3 has quit IRC08:35
*** ttx has quit IRC08:35
*** crinkle has quit IRC08:35
*** tteggel_ has quit IRC08:35
*** _fortis has quit IRC08:35
*** egon has quit IRC08:35
*** cody-somerville- has quit IRC08:35
*** zxiiro has quit IRC08:35
*** jaredrohe has quit IRC08:35
*** devananda has quit IRC08:35
*** yingjun has joined #openstack-meeting08:37
*** pbourke has joined #openstack-meeting08:37
*** jckasper has joined #openstack-meeting08:37
*** pedroalvarez has joined #openstack-meeting08:37
*** Yingxin has joined #openstack-meeting08:37
*** hogepodge has joined #openstack-meeting08:37
*** larainema has joined #openstack-meeting08:37
*** ianw has joined #openstack-meeting08:37
*** ajiang has joined #openstack-meeting08:37
*** federico3 has joined #openstack-meeting08:37
*** ttx has joined #openstack-meeting08:37
*** crinkle has joined #openstack-meeting08:37
*** tteggel_ has joined #openstack-meeting08:37
*** _fortis has joined #openstack-meeting08:37
*** egon has joined #openstack-meeting08:37
*** cody-somerville- has joined #openstack-meeting08:37
*** zxiiro has joined #openstack-meeting08:37
*** jaredrohe has joined #openstack-meeting08:37
*** devananda has joined #openstack-meeting08:37
*** cameron.freenode.net changes topic to " (Meeting topic: third-party)"08:37
*** jyuso1 has left #openstack-meeting08:40
*** sudipto has joined #openstack-meeting08:43
*** e0ne has joined #openstack-meeting08:44
*** andreykurilin has joined #openstack-meeting08:49
*** ddieterly has joined #openstack-meeting08:51
*** alexpilotti has quit IRC08:51
*** alexpilotti has joined #openstack-meeting08:52
*** jcoufal has joined #openstack-meeting08:54
*** mrmartin has joined #openstack-meeting08:55
*** jcoufal has quit IRC08:55
*** jcoufal has joined #openstack-meeting08:56
*** ddieterly has quit IRC08:56
*** maishsk has quit IRC08:56
*** maishsk has joined #openstack-meeting08:59
*** GB21 has joined #openstack-meeting08:59
*** Jeffrey4l has quit IRC09:02
*** zhhuabj has quit IRC09:06
*** jcoufal has quit IRC09:07
*** MarkAtwood has quit IRC09:09
*** jcoufal has joined #openstack-meeting09:11
*** ikhudoshyn has joined #openstack-meeting09:14
*** zhhuabj has joined #openstack-meeting09:17
*** Daisy_ has quit IRC09:21
*** Daisy has joined #openstack-meeting09:22
*** zhhuabj has quit IRC09:23
*** Daisy has quit IRC09:25
*** Daisy has joined #openstack-meeting09:25
*** toscalix has joined #openstack-meeting09:26
*** boris-42 has quit IRC09:30
*** claudiub has joined #openstack-meeting09:31
*** fawadkhaliq has joined #openstack-meeting09:31
*** zhhuabj has joined #openstack-meeting09:35
*** zhhuabj has quit IRC09:36
*** zhhuabj has joined #openstack-meeting09:36
*** Daisy has quit IRC09:36
*** sudipto has quit IRC09:37
*** yingjun has quit IRC09:37
*** jprovazn has quit IRC09:41
*** zhhuabj has quit IRC09:42
*** luisfdez has joined #openstack-meeting09:44
*** ddieterly has joined #openstack-meeting09:52
*** otter768 has joined #openstack-meeting09:52
*** sudipto has joined #openstack-meeting09:53
*** dims has joined #openstack-meeting09:55
*** ddieterly has quit IRC09:57
*** otter768 has quit IRC09:57
*** zhhuabj has joined #openstack-meeting09:58
*** jcoufal has quit IRC09:59
*** jcoufal has joined #openstack-meeting09:59
*** maishsk has quit IRC10:01
*** maishsk has joined #openstack-meeting10:02
*** lukebrooker has joined #openstack-meeting10:04
*** SridharG has quit IRC10:07
*** _amrith_ is now known as amrith10:08
*** jcoufal has quit IRC10:10
*** lxsli has quit IRC10:10
*** lxsli has joined #openstack-meeting10:11
*** devvesa has joined #openstack-meeting10:13
*** ricolin has quit IRC10:14
*** larainema has quit IRC10:15
*** larainema has joined #openstack-meeting10:15
*** madong_ has joined #openstack-meeting10:16
*** larainema has quit IRC10:19
*** IanGovett has joined #openstack-meeting10:21
*** zeih has quit IRC10:22
*** epico has quit IRC10:24
*** xingchao has quit IRC10:24
*** SridharG has joined #openstack-meeting10:28
*** SridharG has left #openstack-meeting10:29
*** SridharG has joined #openstack-meeting10:29
*** amrith is now known as _amrith_10:31
*** yamamoto has quit IRC10:32
*** SridharG has left #openstack-meeting10:33
*** SridharG has joined #openstack-meeting10:33
*** fawadk has joined #openstack-meeting10:35
*** fawadkhaliq has quit IRC10:37
*** fawadkhaliq has joined #openstack-meeting10:38
*** claudiub has quit IRC10:40
*** claudiub has joined #openstack-meeting10:41
*** xingchao has joined #openstack-meeting10:41
*** yamamoto has joined #openstack-meeting10:41
*** fawadk has quit IRC10:43
*** oomichi has quit IRC10:45
*** IanGovett has quit IRC10:46
*** IanGovett has joined #openstack-meeting10:46
*** lukebrooker has quit IRC10:50
*** jcoufal has joined #openstack-meeting10:52
*** ddieterly has joined #openstack-meeting10:53
*** sahid has quit IRC10:54
*** xingchao has quit IRC10:56
*** ddieterly has quit IRC10:58
*** eglynn_ has joined #openstack-meeting10:59
*** aukhan has quit IRC11:00
*** topol has joined #openstack-meeting11:00
*** xingchao has joined #openstack-meeting11:01
*** radez is now known as radez_g0n311:01
*** nadya has quit IRC11:02
*** SridharG has quit IRC11:04
*** jlanoux has quit IRC11:05
*** xingchao has quit IRC11:05
*** SridharG has joined #openstack-meeting11:05
*** topol has quit IRC11:05
*** nadya has joined #openstack-meeting11:06
*** nadya has quit IRC11:07
*** coolsvap is now known as coolsvap|away11:14
*** SridharG1 has joined #openstack-meeting11:14
*** Daisy has joined #openstack-meeting11:15
*** SridharG1 has left #openstack-meeting11:15
*** SridharG1 has joined #openstack-meeting11:15
*** SridharG has quit IRC11:17
*** mrmartin has quit IRC11:19
*** Daisy has quit IRC11:20
*** ganeshna has quit IRC11:21
*** GB21 has quit IRC11:22
*** julim has joined #openstack-meeting11:25
*** nmagnezi has joined #openstack-meeting11:26
*** nmagnezi has quit IRC11:26
*** _amrith_ is now known as amrith11:26
*** yamamoto has quit IRC11:28
*** noslzzp has joined #openstack-meeting11:29
*** amrith is now known as _amrith_11:30
*** _amrith_ is now known as amrith11:31
*** oomichi has joined #openstack-meeting11:31
*** gsilvis has quit IRC11:32
*** BharatK has quit IRC11:32
*** martines has quit IRC11:33
*** SridharG1 has quit IRC11:34
*** GB21 has joined #openstack-meeting11:38
*** dprince has joined #openstack-meeting11:39
*** eglynn_ has quit IRC11:43
*** eglynn__ has joined #openstack-meeting11:44
*** amakarov_away is now known as amakarov11:46
*** BharatK has joined #openstack-meeting11:46
*** martines has joined #openstack-meeting11:46
*** sdake_ has quit IRC11:47
*** fawadkhaliq has quit IRC11:48
*** jlanoux has joined #openstack-meeting11:48
*** sudipto has quit IRC11:49
*** mwagner_lap has quit IRC11:50
*** ttrifonov is now known as zz_ttrifonov11:52
*** otter768 has joined #openstack-meeting11:53
*** ddieterly has joined #openstack-meeting11:54
*** tobe_ has quit IRC11:56
*** sahid has joined #openstack-meeting11:57
*** otter768 has quit IRC11:58
*** topol has joined #openstack-meeting11:58
*** ddieterly has quit IRC11:58
*** tobe_ has joined #openstack-meeting11:59
*** jaypipes has joined #openstack-meeting11:59
*** lixinhui has joined #openstack-meeting12:01
*** tobe_ has quit IRC12:01
*** amotoki has quit IRC12:01
*** lpetrut has joined #openstack-meeting12:03
*** PrashantS has joined #openstack-meeting12:07
*** yamamoto has joined #openstack-meeting12:07
*** josdotso has quit IRC12:13
*** ganeshna has joined #openstack-meeting12:14
*** raildo has joined #openstack-meeting12:15
*** zz_ttrifonov is now known as ttrifonov12:15
*** lkarm has joined #openstack-meeting12:16
*** yamamoto has quit IRC12:16
*** ganeshna has quit IRC12:17
*** ganeshna has joined #openstack-meeting12:18
*** yamamoto has joined #openstack-meeting12:22
*** fawadkhaliq has joined #openstack-meeting12:23
*** VW_ has joined #openstack-meeting12:24
*** ub has quit IRC12:24
*** ikhudoshyn has quit IRC12:24
*** ikhudoshyn has joined #openstack-meeting12:25
*** marcusvrn has joined #openstack-meeting12:27
*** yanyanhu has joined #openstack-meeting12:29
*** aysyd has joined #openstack-meeting12:31
*** yamamoto has quit IRC12:32
*** baoli has joined #openstack-meeting12:32
*** yamamoto has joined #openstack-meeting12:33
*** dkranz has joined #openstack-meeting12:34
*** baoli has quit IRC12:34
*** bapalm_ has joined #openstack-meeting12:34
*** baoli has joined #openstack-meeting12:34
*** sdake has joined #openstack-meeting12:36
*** ganeshna has quit IRC12:37
*** ganeshna has joined #openstack-meeting12:39
*** rfolco has joined #openstack-meeting12:40
*** yamamoto has quit IRC12:41
*** nadya has joined #openstack-meeting12:42
*** nadya has quit IRC12:43
*** weshay has joined #openstack-meeting12:43
*** oomichi has quit IRC12:45
*** numan has joined #openstack-meeting12:46
*** ganeshna has quit IRC12:47
*** ganeshna_ has joined #openstack-meeting12:47
*** numan has quit IRC12:47
*** claudiub has quit IRC12:50
*** VW_ has quit IRC12:52
*** alexpilotti_ has joined #openstack-meeting12:52
*** eliqiao1 has quit IRC12:52
*** alexpilotti has quit IRC12:52
*** alexpilotti_ is now known as alexpilotti12:52
*** VW_ has joined #openstack-meeting12:52
*** zul has joined #openstack-meeting12:53
*** zul has quit IRC12:53
*** zul has joined #openstack-meeting12:53
*** VW__ has joined #openstack-meeting12:54
*** VW_ has quit IRC12:54
*** lpeer_ has quit IRC12:54
*** VW__ has quit IRC12:56
*** ildikov has joined #openstack-meeting12:56
*** VW_ has joined #openstack-meeting12:56
*** annegentle has joined #openstack-meeting12:56
*** bknudson has joined #openstack-meeting12:57
*** jaypipes has quit IRC12:57
*** vivek-ebay has joined #openstack-meeting12:58
*** haiwei has joined #openstack-meeting12:58
*** nmagnezi_ has joined #openstack-meeting12:58
*** Qiming has joined #openstack-meeting12:58
*** jaypipes has joined #openstack-meeting13:00
Qiminghello13:00
Qiming#startmeeting senlin13:00
yanyanhuhi13:00
openstackMeeting started Tue Aug  4 13:00:33 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
*** nadya has joined #openstack-meeting13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
*** MeganR has joined #openstack-meeting13:00
*** VW_ has quit IRC13:00
*** dims_ has joined #openstack-meeting13:00
*** haiwei__ has joined #openstack-meeting13:01
*** jruano has joined #openstack-meeting13:01
Qiminghello guys13:01
jruanohello13:01
lkarmhello13:01
yanyanhuo/13:01
haiwei__hi13:01
Qiminglet's get started13:01
*** yamamoto has joined #openstack-meeting13:01
Qimingplease add items to the agenda if you have things to share13:02
Qiming#link https://wiki.openstack.org/wiki/Meetings/SenlinAgenda13:02
*** dims has quit IRC13:02
*** vivek-ebay has quit IRC13:02
*** haiwei has quit IRC13:02
Qiming#topic liberty-3 milestone targets13:03
*** openstack changes topic to "liberty-3 milestone targets (Meeting topic: senlin)"13:03
*** yamamoto has quit IRC13:03
Qimingrefer to etherpad: https://etherpad.openstack.org/p/senlin-liberty-workitems13:03
Qimingwe still have some items left from l-213:04
*** lpeer_ has joined #openstack-meeting13:04
*** dims has joined #openstack-meeting13:04
yanyanhuyes, and we have 5 goals want to achieve13:04
Qimingright, those five are about l-313:04
*** ivasev has joined #openstack-meeting13:04
jruanoi am closing out on mine by tomorrow13:05
*** yamamoto has joined #openstack-meeting13:05
Qimingif everything goes smooth, I think we should try propose to switch the namespace, ;)13:05
jruanothat sounds fantastic13:05
*** MeganR has left #openstack-meeting13:05
yanyanhuis trigger also one of our goals? I saw it in backlog but not in goal list13:05
yanyanhuI hope it is :)13:06
Qimingit is in backlog, should have been completed by l-213:06
*** dims_ has quit IRC13:06
yanyanhuok13:06
Qimingneed more reviews, you know13:06
yanyanhuright13:06
*** coolsvap|away is now known as coolsvap13:06
*** PrashantS has quit IRC13:07
haiwei__switch the namespace means to be a openstack project?13:07
Qimingthe big things ahead: container clusters, which is the topic for the summit talk13:07
Qimingyes, haiwei__ we should definitely try it13:07
*** PrashantS has joined #openstack-meeting13:07
haiwei__ok13:07
Qiminganother big thing is senlinclient unit tests13:08
jruanoi am working on the container clusters. behind where i need to be, i have spent some time trying to figure out magnum13:08
Qimingwe have no a single line for that13:08
Qimingthanks, jruano, that is an important show case13:08
Qimingwe are not supposed to only propose senlin server, leaving senlinclient on stackforge, that makes no sense13:09
*** amitgandhinz has joined #openstack-meeting13:09
yanyanhuyep, so maybe we need to have a plan about the unit test of senlinclient13:10
haiwei__yes, so the client test should be started soon13:10
yanyanhumaybe also file some bugs about it13:10
*** kylek3h has joined #openstack-meeting13:10
Qimingas for placement policy, it would be part of our efforts to make senlin capable of supporting VM/app HA scenarios13:10
*** lpetrut has quit IRC13:10
Qiming+1 on filing some bugs now13:10
yanyanhuthis is one of the most important feature we want to support in the first release I think13:11
*** pm90_ has joined #openstack-meeting13:11
yanyanhuthe placement policy to support cross az/region node creation13:11
Qimingit is important for two reasons13:11
Qimingwe have some commitments to demonstrate cross-region autoscaling13:12
*** PrashantS has quit IRC13:12
Qimingplacement policy would be also a show case for the upcoming OpenNFV summit in San Francisco13:12
Qimingthat was the reason I'm putting it there in the list as an important goal13:13
haiwei__you will git a demo about it?13:13
Qiminghopefully, Cindia can help us get that sorted out soon13:13
*** jgriffith has quit IRC13:14
Qimingyes, haiwei__13:14
jruanowe talked with a customer last week around tosca. they mentioned placement policy at the top of their list as well13:14
*** yingjun has joined #openstack-meeting13:14
Qimingit was a proposal submitted with China Mobile, VMware13:14
*** Daisy has joined #openstack-meeting13:15
Qimingjust submitted today13:15
*** erlon has joined #openstack-meeting13:15
yanyanhuQiming, I think we may need to start work on this item asap to ensure we can give a prilimary implementation by the end of l-3 deadline13:15
haiwei__when is the summit13:15
*** carl_baldwin has joined #openstack-meeting13:15
*** tiswanso has joined #openstack-meeting13:15
Qimingit's Nov 08-14?13:15
lkarmi thought it was in october13:15
jruanotokyo is end of october this year13:16
jruano27-30 i think?13:16
yanyanhuyes, hope no conflict13:16
Qimingright13:16
*** banix has joined #openstack-meeting13:16
*** radez_g0n3 is now known as radez13:16
Qimingopenstack summit Oct 27-30, OpenNFV summit Nov 08-1413:16
Qimingif we have supports from carrier vendors, we are really on a good track to get our work utilized13:18
yanyanhuHA policy is also needed as well as the placement policy?13:18
*** xyang has quit IRC13:18
*** ganeshna_ has quit IRC13:18
*** neelashah has joined #openstack-meeting13:18
Qimingplacement policy is only part of the story, HA ... is a big topic13:18
yanyanhuok, good news for now :)13:18
Qiminghopefully we can gain some traction, with placement policy as a starting point13:19
yanyanhuwe don't have to jump into HA part in next month13:19
*** spzala has joined #openstack-meeting13:19
yanyanhuok13:19
Qimingagain, I'm hoping that Cindia will lead that effort and get started soon13:19
yanyanhuthat will be the best :)13:19
Qimingit is a separate thread13:19
*** yamamoto has quit IRC13:20
haiwei__who is Cindia :)13:20
Qimingdo we need to prioritize these items?13:20
yanyanhulixinhui :)13:20
Qiminghaiwei__, Cindia-Blue, :)13:20
*** xingchao has joined #openstack-meeting13:20
haiwei__ok, absent today?13:20
yanyanhuno, Qiming, I think we just need to ensure every item has some guys to work on it13:21
*** jgriffith has joined #openstack-meeting13:21
Qimingalright, sign your name after each item13:21
yanyanhuthen we can know whether we really have bandwidth to finish these items13:21
Qimingit is okay to have more than one name signed on each item, right?13:22
yanyanhusure :)13:22
*** yingjun has quit IRC13:22
QimingI'm signing on the senlinclient test cases13:22
*** yingjun has joined #openstack-meeting13:22
*** Daisy has quit IRC13:22
haiwei__yap, but don't conflict13:22
*** Daisy has joined #openstack-meeting13:23
Qimingsure, if two or more people are working on the same item, we need to sync more frequently13:23
*** coolsvap is now known as coolsvap_13:23
yanyanhuhope I can finish the functional test setup13:23
*** xingchao has quit IRC13:23
Qimingbtw, jruano, do you need help on the unit tests?13:24
Qimingjust noticed that you have claimed quite some of them13:24
yanyanhuand provide tests for some most important cases13:24
Qimingyanyanhu, that would be cool, giving both users and us more confidence on using the service13:24
jruanoi think im good. i finished node_action, and started cluster_action13:25
yanyanhuyes, that's our goal13:25
jruanothe new ones i claimed yesterday were for drivers13:25
Qimingokay, jruano, if the plate is too full for you, we can share, :)13:25
Qiminglet's move on13:26
jruanosure np.13:26
Qiming#topic plan of functional testing13:26
*** openstack changes topic to "plan of functional testing (Meeting topic: senlin)"13:26
Qimingyanyanhu,13:26
yanyanhuok13:26
yanyanhunow we plan to add functional test for Senlin service13:26
*** singlethink has joined #openstack-meeting13:27
yanyanhucurrently, we only have unit test and all of them are located in senlin/tests13:27
*** adahms has joined #openstack-meeting13:27
yanyanhuso we tried to relocate these existing tests and reorganize our test cases13:27
yanyanhuhttps://review.openstack.org/#/c/208944/13:27
yanyanhuthis patch move all unit tests into senlin/tests/unit directory13:28
*** lblanchard has joined #openstack-meeting13:28
yanyanhuand new added functional test will be put into senlin/test/functional directory13:28
yanyanhuso some of you guys may need to rebase some existing works on unit test :)13:29
Qimingalready get some report of merge failure, :)13:29
yanyanhuyes ;)13:29
yanyanhufirst, we will try to add basic support of functional test locally13:30
Qimingfunctional test is mostly about ensuring the service behaves as expected when processing REST requests13:30
yanyanhuyep, so we don't touch other services in this part13:31
*** singleth_ has joined #openstack-meeting13:31
*** VW_ has joined #openstack-meeting13:31
yanyanhuonly senlin services will be tested through REST API13:31
*** ayoung has joined #openstack-meeting13:32
Qimingso, basically, you will do 'source senlinrc; tox -e functional'13:32
*** harshs has joined #openstack-meeting13:33
QimingI hope by the end of l-3, we will have major workflows covered13:33
*** puranamr has joined #openstack-meeting13:33
*** singlethink has quit IRC13:34
haiwei__this is also a big task13:34
Qimingabsolutely13:34
*** yanyan has joined #openstack-meeting13:34
yanyansorry, just dropped13:34
Qimingonce the first workflow is running13:34
Qimingadding other workflows would be simple13:35
yanyanyes13:35
Qimingjust send a REST request and assert the response13:35
yanyanhope can finish the first step in a week13:35
Qimingcool!13:35
yanyanscenario and integration test will be future work :)13:35
*** dims_ has joined #openstack-meeting13:36
haiwei__it seems other projects are doing function tests in Tempest13:36
*** nelsnelson has joined #openstack-meeting13:36
Qimingintegration test means we will be testing senlin's interaction with other services, using real Profile13:36
haiwei__we will also move it to tempest maybe one day?13:36
yanyanhmm, most of them have moved functional test out of tempest I think13:36
*** nelsnelson has quit IRC13:37
yanyansaw related patches and bps in different projects13:37
*** yanyanhu has quit IRC13:37
*** matrohon has joined #openstack-meeting13:37
yanyanQiming, yes13:37
*** nelsnelson has joined #openstack-meeting13:37
haiwei__yanyan, oh, my information is too old13:37
Qimingyes, doing functional tests there would make the gating job run very long13:37
*** dims has quit IRC13:37
yanyanI also got this info from Qiming :)13:37
*** dane_leblanc has joined #openstack-meeting13:38
*** mestery_afk is now known as mestery13:38
*** tongli has joined #openstack-meeting13:38
Qimingin heat, we used to call them heat-slow tests13:38
Qimingand heat-very-slow tests, :)13:38
haiwei__I used to write some function tests in tempest for nova13:38
yanyan:p13:38
Qiminganyway, functional tests in each project, that makes sense, we will do it13:39
Qimingyanyan, shall we move on?13:39
jruanoright13:39
yanyancool, maybe you can share some experience about it13:39
*** ttrifonov is now known as zz_ttrifonov13:39
haiwei__ok13:39
yanyanok13:39
yanyanlets move on13:39
Qiming#topic clusters of containers13:39
*** openstack changes topic to "clusters of containers (Meeting topic: senlin)"13:39
Qimingjruano, anything new to share?13:39
*** carl_baldwin has quit IRC13:39
jruanoi am a little behind here... i spend some time digging through magnum and it has been more difficult than i expected13:40
jruanomagnum requires a coe to manage containers13:40
*** lpetrut has joined #openstack-meeting13:40
Qimingokay, that's true13:41
*** kencjohnston has joined #openstack-meeting13:41
jruanoso for the poc i am not sure we need all of that13:41
*** PrashantS has joined #openstack-meeting13:41
*** phil_ has quit IRC13:41
Qimingthere are things we cannot control out there13:41
*** PrashantS has quit IRC13:42
*** DericHorn-HP has joined #openstack-meeting13:42
*** Daisy has quit IRC13:42
*** PrashantS has joined #openstack-meeting13:42
jruanoso for the short term i am focused on trying to get a cluster of containers deployed under coreos13:42
Qimingmaybe senlin is not capable of assuming the role of a coe in near future13:43
*** Daisy has joined #openstack-meeting13:43
jruanoi'd hope it can13:43
jruanomagnum is wanting to be generic, but it is semantically very close to k8s13:44
Qimingit seems to me that Magnum is still brainstorming their horizontal scaling support13:44
*** mrmartin has joined #openstack-meeting13:44
Qiming#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/071216.html13:44
Qimingto be honest, we have been asking the question again and again, what are the values magnum bring to users13:44
jruanolol13:45
jruanoi am struggling with it13:45
jruanofundamentally to me it appears to be a k8s abstraction13:45
Qimingmaybe the magnum team has some ideas I'm not aware of13:45
Qimingdo we need a k8s abstraction?13:46
jruanowhen i talk to folks in tosca, they want a generic container service13:46
*** Daisy has quit IRC13:46
*** Daisy has joined #openstack-meeting13:46
Qimingthe 'container engine' could be docker or k8s, right?13:46
haiwei__as far as I know, magnum is just a tool to install k8s13:46
Qimingyes, that is my understanding as well, haiwei__13:46
jruanoyes haiwei_ that is what it looks like from the code13:47
Qimingand it is using Heat to do the VM provisioning13:47
*** PrashantS has quit IRC13:47
jruanoyep13:47
*** yingjun has quit IRC13:47
*** lpetrut has quit IRC13:47
Qiming a unified abstraction above docker and k8s? that is challenging13:47
*** tiswanso has quit IRC13:47
haiwei__so what is our goal to work with magnum?13:48
haiwei__we want magnum to use senlin?13:48
Qimingnot just from technical perspective13:48
*** Daisy has quit IRC13:48
*** tiswanso has joined #openstack-meeting13:48
Qimingwe believe Senlin can do a better job managing the VMs they use to run containers13:48
*** Daisy has joined #openstack-meeting13:49
*** esker has joined #openstack-meeting13:49
Qiminganyway, let's keep investigating13:49
*** mwagner_lap has joined #openstack-meeting13:49
haiwei__so that should be magnum->k8s->docker->senlin->vm->containers?13:49
jruanothat is where i am at. i will have more over the next couple of days13:50
Qimingthe vision is: magnum talks to senlin to provision VMs, it then talks to k8s or docker to privision containers13:50
*** Daisy has quit IRC13:51
*** Daisy has joined #openstack-meeting13:51
Qimingmaybe senlin should help manage the containers directly, :P13:51
*** banix has quit IRC13:51
jruanothats where i was headed13:51
*** dboik has joined #openstack-meeting13:51
Qimingoh, really?13:51
*** Daisy has joined #openstack-meeting13:51
jruanobut magnum for now seems to want to just push that to the underlying coe13:51
Qimingmagnum doesn't want to reinvent things13:52
jruanotrue13:52
Qimingk8s has a big community, docker has another13:52
Qimingyou are not compete head to head with them13:52
*** Daisy has quit IRC13:52
*** thangp has joined #openstack-meeting13:52
*** Daisy has joined #openstack-meeting13:53
Qimingso, for Senlin, we just see where we can help13:53
*** adahms has quit IRC13:53
Qimingokay, we don't have much time now13:53
Qiming#topic open discussions13:53
*** openstack changes topic to "open discussions (Meeting topic: senlin)"13:53
*** kencjohnston has quit IRC13:53
*** adahms has joined #openstack-meeting13:53
Qiminganything we have missed?13:54
*** otter768 has joined #openstack-meeting13:54
yanyannope from me13:54
*** claudiub has joined #openstack-meeting13:54
Qimingguess no13:54
jruanonothing from me13:55
Qimingsee you guys, thanks for joining13:55
haiwei__it's ok for me13:55
Qiming#endmeeting13:55
*** openstack changes topic to " (Meeting topic: third-party)"13:55
openstackMeeting ended Tue Aug  4 13:55:14 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-08-04-13.00.html13:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-08-04-13.00.txt13:55
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-08-04-13.00.log.html13:55
*** haiwei__ has quit IRC13:56
*** changbl has quit IRC13:56
*** otter768 has quit IRC13:58
*** yingjun has joined #openstack-meeting13:59
*** yapeng has joined #openstack-meeting14:00
*** sigmavirus24_awa is now known as sigmavirus2414:00
*** singlethink has joined #openstack-meeting14:00
*** IlyaG has joined #openstack-meeting14:01
*** yanyan has quit IRC14:01
*** bryan_att has joined #openstack-meeting14:02
*** singleth_ has quit IRC14:02
*** Gerald_K has joined #openstack-meeting14:03
*** ub has joined #openstack-meeting14:03
*** lkarm has left #openstack-meeting14:04
*** jgriffith has quit IRC14:04
*** jgriffith has joined #openstack-meeting14:04
*** dmacpher has joined #openstack-meeting14:05
*** 32NAAAL0S has quit IRC14:06
*** haomaiwang has joined #openstack-meeting14:07
*** BharatK has quit IRC14:07
*** yamamoto has joined #openstack-meeting14:09
*** dkranz has quit IRC14:09
*** changbl has joined #openstack-meeting14:09
*** mtanino has joined #openstack-meeting14:09
*** Daisy has quit IRC14:11
*** jckasper has quit IRC14:12
*** Daisy has joined #openstack-meeting14:12
*** zz_ttrifonov is now known as ttrifonov14:13
*** DericHorn-HP has quit IRC14:13
*** harshs has quit IRC14:14
*** ndipanov has joined #openstack-meeting14:15
*** hrou has joined #openstack-meeting14:15
*** eglynn__ has quit IRC14:15
*** Daisy has quit IRC14:16
*** jcoufal has quit IRC14:16
*** jprovazn has joined #openstack-meeting14:16
*** Qiming has quit IRC14:19
*** pm90_ has quit IRC14:20
*** salv-orlando has quit IRC14:20
*** DericHorn-HP has joined #openstack-meeting14:22
*** dkranz has joined #openstack-meeting14:22
*** cdub has joined #openstack-meeting14:23
*** Tross has joined #openstack-meeting14:24
*** mrmartin has quit IRC14:24
*** Tross1 has quit IRC14:25
*** mrunge has joined #openstack-meeting14:25
*** SridharG has joined #openstack-meeting14:26
*** Piet has quit IRC14:26
*** harshs has joined #openstack-meeting14:26
*** salv-orlando has joined #openstack-meeting14:27
*** numan has joined #openstack-meeting14:29
*** armax has joined #openstack-meeting14:30
*** harshs has quit IRC14:30
*** MarkAtwood has joined #openstack-meeting14:31
*** ttrifonov is now known as zz_ttrifonov14:31
*** jecarey has joined #openstack-meeting14:33
*** xingchao has joined #openstack-meeting14:34
*** madong_ has quit IRC14:34
*** madong_ has joined #openstack-meeting14:34
*** madong_ is now known as larainema14:34
*** amrith is now known as _amrith_14:35
*** kurtmartin has joined #openstack-meeting14:35
*** kurtmartin is now known as kmartin14:35
*** alexschm has joined #openstack-meeting14:35
*** kmartin has quit IRC14:36
*** Apoorva has joined #openstack-meeting14:36
*** DericHorn-HP has quit IRC14:37
*** jcoufal has joined #openstack-meeting14:37
*** Murali has quit IRC14:39
*** emagana has joined #openstack-meeting14:39
*** vijendar has joined #openstack-meeting14:40
*** dane_leblanc has quit IRC14:40
*** rbak has joined #openstack-meeting14:40
*** dims_ has quit IRC14:41
*** pradk has joined #openstack-meeting14:41
*** dims has joined #openstack-meeting14:41
*** emagana has quit IRC14:42
*** cbouch has joined #openstack-meeting14:45
*** lpetrut has joined #openstack-meeting14:45
*** salv-orl_ has joined #openstack-meeting14:47
*** xyang has joined #openstack-meeting14:48
*** emagana has joined #openstack-meeting14:48
*** salv-orlando has quit IRC14:49
*** Piet has joined #openstack-meeting14:51
*** galstrom_zzz is now known as galstrom14:51
*** achanda has joined #openstack-meeting14:52
*** rjaiswal has joined #openstack-meeting14:54
*** bradjones has joined #openstack-meeting14:54
*** bradjones has quit IRC14:54
*** bradjones has joined #openstack-meeting14:54
*** rbak has quit IRC14:55
*** vahidh has joined #openstack-meeting14:57
*** kencjohnston has joined #openstack-meeting14:57
*** yamahata has joined #openstack-meeting14:57
*** rbak has joined #openstack-meeting14:57
*** edtubill has joined #openstack-meeting14:58
mesterykevinbenton dougwig carl_baldwin: You folks around for a drivers meeting this week in 2 minutes?14:58
*** maishsk has quit IRC14:59
*** banix has joined #openstack-meeting14:59
*** tiswanso has quit IRC14:59
dougwigo/14:59
*** haomaiwang has quit IRC15:00
*** elo has joined #openstack-meeting15:00
mesterydougwig: OK, lets just do this quick since it's only me nad you today so far :)15:00
*** haomaiwang has joined #openstack-meeting15:00
*** hemna has joined #openstack-meeting15:00
mestery#startmeeting neutron-drivers15:00
openstackMeeting started Tue Aug  4 15:00:48 2015 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron-drivers)"15:00
openstackThe meeting name has been set to 'neutron_drivers'15:00
dougwigmy doc ordered me off red bull, so we'll see how much patience i have.15:00
*** belmoreira has quit IRC15:01
mesterylol15:01
mestery#link https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda Agenda15:01
mesterySo, since it's just me and you dougwig ...15:01
mestery#topic Liberty-3 Review Backlog and Apocalypse15:01
*** openstack changes topic to "Liberty-3 Review Backlog and Apocalypse (Meeting topic: neutron-drivers)"15:01
mesteryThis is all I had this week15:01
*** tiswanso has joined #openstack-meeting15:01
mesteryBecause honestly, at this point, accepting new RFEs isn't high on my list15:02
mestery:)15:02
dougwighow bad is the backlog? i haven't looked since getting back from vacation.  i didn't want to ruin my mellow.15:02
mesteryyeah, it's bad15:02
* mestery #link https://launchpad.net/neutron/+milestone/liberty-315:02
mestery28 blueprints15:02
mestery#info 28 blueprints left to merge in Liberty15:02
mesterySo, I guess we just need to focus and review.15:03
dougwigok, well, that'll never hapen.15:03
*** carl_baldwin has joined #openstack-meeting15:03
mestery#info Plan is to fold QoS back into mast week of 8/1015:03
dougwigdo we have a list of what we really want to make it, or what's far enough along?15:03
mestery#info Plan is to fold pecan back into master week of 8/1715:03
mesteryGo with priority there15:03
dougwigok15:03
*** achanda has quit IRC15:04
mesterySo15:04
mesteryquestion dougwig15:04
mesteryOctacvia15:04
mesteryHow is it coming?15:04
mesteryIs it ready to be default?15:04
* carl_baldwin wanders in15:04
dougwigi will have an answer for you later today.15:04
mesterycarl_baldwin: Hey man! :)15:04
mesteryOK15:04
dougwigi suspect that it's not quite there for liberty, but let me circle with folks and come back.15:04
mestery#action dougwig to get a readout on Octavia and go/no-go for Liberty15:04
mesterycarl_baldwin: We're discussing Liberty-3 items: https://launchpad.net/neutron/+milestone/liberty-315:04
mesteryBecause that's all we should be focusing on now, there is a lot to merge yet15:05
*** zz_ttrifonov is now known as ttrifonov15:05
carl_baldwinmestery: ack15:05
*** jckasper has joined #openstack-meeting15:05
mesterydougwig: https://blueprints.launchpad.net/neutron/+spec/neutron-lib15:06
mestery#link https://blueprints.launchpad.net/neutron/+spec/neutron-lib15:06
mesteryWhat's the status of that one?15:06
mesteryIt's critical :)15:06
dougwigthe status is that i'm a terrible person.  safe to kick to M?15:06
mesterylol15:06
mesteryI think we may have to, I'll let you decide :)15:07
*** kurtmartin has joined #openstack-meeting15:07
mesteryI need your opinions on this one carl_baldwin and dougwig15:07
mestery#link https://blueprints.launchpad.net/neutron/+spec/reference-implementation-split15:07
dougwigi will likely get the first commit into gerrit before M, but I don't think it's reasonable for to expect it to land or to do a big churn right at the end.15:07
mesteryShall we try to do this post Liberty-3? That is the best option now.15:07
*** yingjun has quit IRC15:07
mesterydougwig: Sounds fair15:07
mesteryUnless we do it during the freeze along with mine15:07
dougwigdoing the ref split during the freeze would not leave the packagers much time to react.15:08
*** coolsvap_ is now known as coolsvap|away15:08
mesteryThat's true, but doing it before that will kill anything which wants to merge into the things being split15:08
carl_baldwin+115:08
mesterySo, not sure how to proceed15:08
mesteryEarly Mitaka?15:08
dougwigi think it's early M.15:09
mesteryYeah, sadly, me too :(15:09
carl_baldwinagree15:09
mesteryNuts15:09
* carl_baldwin feels the pain15:09
mestery#info Move neutron-lib and reference-split into Mitaka :(15:09
mesteryOK, I'll move those15:09
dougwigso then you're a terrible person too.  :)15:09
mesteryEvery. Single. Day.15:09
*** ebalduf has joined #openstack-meeting15:09
mesteryOK15:10
mesteryAny other high priority ones?15:10
*** e0ne has quit IRC15:10
mesterycarl_baldwin: What about the DNS work mlavelle is doing?15:10
mesteryWill those make Liberty?15:10
*** ebalduf has left #openstack-meeting15:10
carl_baldwinmestery: I’ve reviewed an early implementation and heard reports of good progress while I was out.  Planning to review today.15:10
carl_baldwinI think there is a good chance.15:11
mesteryAck15:11
mesteryOK15:11
mestery cool!15:11
*** yamamoto has quit IRC15:11
HenryG carl_baldwin: do you think we can get ipv6 PD in too?15:11
*** e0ne has joined #openstack-meeting15:11
*** dane_leblanc has joined #openstack-meeting15:12
carl_baldwinHenryG: I’ve been sadly absent for a couple of weeks.  Have you reviewed them lately?15:12
carl_baldwinHenryG: I was trying to prioritize them before I left on leave.15:12
HenryGcarl_baldwin: yes, the first patch is ready IMO15:12
*** Apoorva has quit IRC15:12
mesteryHenryG: Thanks for keeping an eye on that :)15:13
carl_baldwinHenryG: I will add that to my list today.15:13
haleybHenryG: this one?  https://review.openstack.org/#/c/158697/15:13
HenryGhaleyb: yes15:13
mesteryhaleyb: Is there a LP BP for your "Get Me a Network" thing? http://specs.openstack.org/openstack/neutron-specs/specs/liberty/get-me-a-network.html15:14
mesteryhaleyb: If not, can you create one? I'd like to track that as Critical as well.15:14
*** neelashah has quit IRC15:14
mestery:)15:14
mesteryNo pressure15:14
mesteryOr anything ;)15:14
* haleyb wishes he was still on vacation :)15:14
*** scheuran has quit IRC15:14
haleybi'll create a blueprint15:14
*** pradk has quit IRC15:14
*** dannywilson has joined #openstack-meeting15:14
*** garthb has joined #openstack-meeting15:15
mesterylol15:15
mesterythanks haleyb!15:15
mestery#action haleyb to create LP BP for "Get Me a Network"15:15
mesterycarl_baldwin: One other question for you: Any idea how the "DVR + L3 HA" work is coming along?15:16
*** yamamoto has joined #openstack-meeting15:16
carl_baldwinmestery: Sadly I’m not up to date on that one either.15:16
mestery#link https://bugs.launchpad.net/neutron/+bug/136547315:16
uvirtbotLaunchpad bug 1365473 in neutron "Unable to create a router that's both HA and distributed" [High,In progress]15:16
openstackLaunchpad bug 1365473 in neutron "Unable to create a router that's both HA and distributed" [High,In progress] - Assigned to Adolfo Duarte (adolfo-duarte)15:16
uvirtbotLaunchpad bug 1365473 in neutron "Unable to create a router that's both HA and distributed" [High,In progress] https://launchpad.net/bugs/136547315:16
mesterycarl_baldwin: No worries, we'll figure it out :)15:16
haleybmestery: was the routed networks BP approved last week?  i see a couple reviews up for it but nothing in the minutes15:17
haleybhttps://bugs.launchpad.net/neutron/+bug/147270415:17
openstackLaunchpad bug 1472704 in neutron "Support networks that work through routing instead of bridging" [Undecided,In progress] - Assigned to Neil Jerram (neil-jerram)15:17
carl_baldwinhaleyb: It is back on the drawing board.15:17
mesteryhaleyb: It most definitely should not have been, can you find the link?15:17
uvirtbotLaunchpad bug 1472704 in neutron "Support networks that work through routing instead of bridging" [Undecided,In progress]15:17
uvirtbotLaunchpad bug 1472704 in neutron "Support networks that work through routing instead of bridging" [Undecided,In progress] https://launchpad.net/bugs/147270415:17
mesterySee comment #3 there15:18
carl_baldwinhaleyb: Oh, that is different than what I was thinking.15:18
carl_baldwinBut, I think that one’s fate is somewhat tied to the fate of the network segments one.15:18
mesteryYes15:18
mesterycarl_baldwin: +1000.515:18
*** dannywilson has quit IRC15:19
*** dannywilson has joined #openstack-meeting15:19
carl_baldwinmestery: Just round up, I can’t do decimals in that context.  ;)15:19
mesteryrofl15:19
mesterycarl_baldwin: You and I are going to talk network segments later today and try to resolve that to see what can be done in Liberty yet15:19
mesteryI remain hopeful15:19
mesteryBut realistic too :)15:19
*** bswartz has joined #openstack-meeting15:20
haleybit was in reference to https://review.openstack.org/#/c/206079/15:20
carl_baldwinmestery: You’re more optimistic than I am (or less informed maybe).  I’m hoping for M.15:20
*** andymaier has joined #openstack-meeting15:20
mesteryrofl15:20
mesterycarl_baldwin: Yeah, that's likely, but even some groundwork going into Liberty may be positive.15:20
mesteryI'm ever vigilant carl_baldwin :D15:20
* mestery pokes dougwig and hands him a red bull15:20
*** esker has quit IRC15:20
carl_baldwinmestery: Agreed.  Work has not stopped but it is back to the drawing board to see if there is a better way.15:21
mesterycarl_baldwin: Excellent!15:21
mestery#topic Open Discussion15:21
*** openstack changes topic to "Open Discussion (Meeting topic: neutron-drivers)"15:21
mesteryAnything else this week or should I give you all 39 minutes back?15:21
mestery:)15:21
*** andymaier has quit IRC15:22
*** andymaier has joined #openstack-meeting15:22
carl_baldwinI was asked to inquire about https://bugs.launchpad.net/neutron/+bug/146836615:22
openstackLaunchpad bug 1468366 in neutron "RFE - Packet logging API for Neutron" [Undecided,Confirmed] - Assigned to Yushiro FURUKAWA (y-furukawa-2)15:22
uvirtbotLaunchpad bug 1468366 in neutron "RFE - Packet logging API for Neutron" [Undecided,Confirmed]15:22
uvirtbotLaunchpad bug 1468366 in neutron "RFE - Packet logging API for Neutron" [Undecided,Confirmed] https://launchpad.net/bugs/146836615:22
*** geoffarnold has joined #openstack-meeting15:22
mesterycarl_baldwin: HenryG had a good point on that one, it's not clear that one belongs in Neutron itself15:22
carl_baldwinmestery: I missed that from HenryG15:23
mesterycarl_baldwin: It was just this morning :)15:23
carl_baldwinI don’t feel so bad then.15:23
*** tsekiyama has joined #openstack-meeting15:23
mestery:)15:23
mesteryOK, thanks for attending and lets focus on reviews! We don't have much time left :)15:24
carl_baldwinBetween mestery and HenryG, could the rfe bug be updated with this?15:24
mesterySo lets see what else we can land now :)15:24
mesterycarl_baldwin: Yes, I'll do that.15:24
*** emagana has quit IRC15:24
carl_baldwinThanks!15:24
mesteryOK, thanks folks!15:25
mestery#endmeeting15:25
*** openstack changes topic to " (Meeting topic: third-party)"15:25
openstackMeeting ended Tue Aug  4 15:25:19 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-08-04-15.00.html15:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-08-04-15.00.txt15:25
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-08-04-15.00.log.html15:25
*** cy_lee has joined #openstack-meeting15:26
*** pradk has joined #openstack-meeting15:27
*** johnthetubaguy has quit IRC15:27
*** johnthetubaguy has joined #openstack-meeting15:27
*** larainema has quit IRC15:28
*** larainema has joined #openstack-meeting15:29
*** cdelatte has joined #openstack-meeting15:29
*** KunalGandhi has joined #openstack-meeting15:30
*** singlethink has quit IRC15:31
*** amitgandhinz has quit IRC15:32
*** yamahata has quit IRC15:32
*** yamahata has joined #openstack-meeting15:32
*** amitgandhinz has joined #openstack-meeting15:33
*** nmagnezi_ has quit IRC15:35
*** larainema has quit IRC15:36
*** IlyaG has quit IRC15:36
*** larainema has joined #openstack-meeting15:36
*** KunalGandhi has quit IRC15:37
*** cy_lee has quit IRC15:37
*** ganeshna has joined #openstack-meeting15:38
*** IlyaG has joined #openstack-meeting15:38
*** stevemar has joined #openstack-meeting15:39
*** ganeshna has quit IRC15:39
*** jdurgin1 has joined #openstack-meeting15:39
*** KunalGandhi has joined #openstack-meeting15:40
*** praveens has joined #openstack-meeting15:43
*** larainema has quit IRC15:45
*** praveens has quit IRC15:45
*** larainema has joined #openstack-meeting15:46
*** praveens has joined #openstack-meeting15:46
*** vivek-ebay has joined #openstack-meeting15:46
*** ganeshna has joined #openstack-meeting15:46
*** SourabhP has joined #openstack-meeting15:47
*** yassine has quit IRC15:47
*** alop has joined #openstack-meeting15:48
*** pradipta has joined #openstack-meeting15:49
*** HenryG has quit IRC15:51
*** IanGovett1 has joined #openstack-meeting15:51
*** SourabhP_ has joined #openstack-meeting15:52
*** DericHorn-HP has joined #openstack-meeting15:53
*** IanGovett has quit IRC15:54
*** jpeeler has quit IRC15:55
*** esker has joined #openstack-meeting15:55
*** otter768 has joined #openstack-meeting15:55
*** SourabhP has quit IRC15:56
*** SourabhP_ is now known as SourabhP15:56
*** tiswanso has quit IRC15:56
*** tiswanso has joined #openstack-meeting15:56
*** tiswanso has quit IRC15:57
*** otter768 has quit IRC15:59
*** haomaiwang has quit IRC16:00
*** cinerama has quit IRC16:00
*** ajmiller has joined #openstack-meeting16:00
*** haomaiwang has joined #openstack-meeting16:00
*** HenryG has joined #openstack-meeting16:01
*** docaedo has quit IRC16:01
*** docaedo has joined #openstack-meeting16:01
*** cinerama has joined #openstack-meeting16:02
*** adahms has quit IRC16:02
*** gyee has joined #openstack-meeting16:02
*** jlanoux has quit IRC16:03
*** esker has quit IRC16:04
*** Apoorva has joined #openstack-meeting16:05
*** leeantho has joined #openstack-meeting16:05
*** Gerald_K has quit IRC16:05
*** gyee has quit IRC16:06
*** emagana has joined #openstack-meeting16:07
*** gampel has joined #openstack-meeting16:07
*** DericHorn-HP has quit IRC16:07
*** ganeshna_ has joined #openstack-meeting16:07
*** DericHorn-HP has joined #openstack-meeting16:08
*** HenryG has quit IRC16:08
*** unicell has joined #openstack-meeting16:10
*** ganeshna has quit IRC16:10
*** coolsvap|away is now known as coolsvap16:10
*** larainema has quit IRC16:11
*** unicell1 has quit IRC16:12
*** larainema has joined #openstack-meeting16:12
*** nadya has quit IRC16:12
*** singlethink has joined #openstack-meeting16:13
*** unicell has quit IRC16:14
*** pballand has joined #openstack-meeting16:15
*** vivek-eb_ has joined #openstack-meeting16:15
*** hrou has quit IRC16:15
*** e0ne has quit IRC16:17
*** vivek-ebay has quit IRC16:17
*** praveens has quit IRC16:18
*** HenryG has joined #openstack-meeting16:18
*** Apoorva has quit IRC16:18
*** GB21_ has joined #openstack-meeting16:19
*** sulo has left #openstack-meeting16:20
*** GB21 has quit IRC16:20
*** SridharG has quit IRC16:21
*** annegentle has quit IRC16:22
*** annegentle has joined #openstack-meeting16:23
*** Apoorva has joined #openstack-meeting16:23
*** vivek-eb_ has quit IRC16:23
*** mrmartin has joined #openstack-meeting16:24
*** Apoorva is now known as apoorvad16:25
*** dzamboni has joined #openstack-meeting16:25
*** ikhudoshyn has quit IRC16:26
*** ivar-lazzaro has joined #openstack-meeting16:26
*** pradipta has quit IRC16:26
*** KunalGandhi has quit IRC16:27
*** bapalm_ has quit IRC16:27
*** ikhudoshyn has joined #openstack-meeting16:27
*** harshs has joined #openstack-meeting16:28
*** banix has quit IRC16:28
*** armax has quit IRC16:28
*** banix has joined #openstack-meeting16:29
*** ikhudoshyn has quit IRC16:31
*** gyee has joined #openstack-meeting16:33
*** tiswanso has joined #openstack-meeting16:34
*** dmorita has joined #openstack-meeting16:34
*** larainema has quit IRC16:36
*** larainema has joined #openstack-meeting16:36
*** lpeer_ has quit IRC16:37
*** gampel has quit IRC16:37
*** singleth_ has joined #openstack-meeting16:37
*** matrohon has quit IRC16:38
*** HenryG has quit IRC16:39
*** sudipto has joined #openstack-meeting16:39
*** singlet__ has joined #openstack-meeting16:40
*** singlethink has quit IRC16:41
*** singlethink has joined #openstack-meeting16:42
*** unicell has joined #openstack-meeting16:42
*** jckasper has quit IRC16:43
*** singleth_ has quit IRC16:43
*** singlet__ has quit IRC16:44
*** vivek-eb_ has joined #openstack-meeting16:47
*** ivar-lazzaro has quit IRC16:47
*** ivar-lazzaro has joined #openstack-meeting16:48
*** SumitNaiksatam has quit IRC16:49
*** banix has quit IRC16:50
*** larainema has quit IRC16:51
*** kencjohnston has quit IRC16:51
*** fawadkhaliq has quit IRC16:52
*** ganeshna_ has quit IRC16:52
*** crc32 has joined #openstack-meeting16:54
*** larainema has joined #openstack-meeting16:55
*** sahid has quit IRC16:55
*** cinerama has quit IRC16:57
*** comay has joined #openstack-meeting16:58
*** maishsk has joined #openstack-meeting16:58
*** ttrifonov is now known as zz_ttrifonov16:59
*** haomaiwang has quit IRC17:00
*** kencjohnston has joined #openstack-meeting17:00
krtaylor#startmeeting third-party17:00
openstackMeeting started Tue Aug  4 17:00:48 2015 UTC and is due to finish in 60 minutes.  The chair is krtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: third-party)"17:00
openstackThe meeting name has been set to 'third_party'17:00
*** haomaiwang has joined #openstack-meeting17:00
krtayloranyone here for Third party CI Working group meeting?17:01
asselin_hi17:01
*** lpeer_ has joined #openstack-meeting17:01
krtaylorhi asselin_17:01
marcusvrnhi17:02
mmedvedeo/17:02
rfolcoo/17:02
krtaylorhi marcusvrn mmedvede rfolco17:02
krtaylorso here is the agenda for today:17:03
krtaylor#link https://wiki.openstack.org/wiki/Meetings/ThirdParty#8.2F4.2F15_1700_UTC17:03
*** fitoduarte has joined #openstack-meeting17:03
krtaylorbasically a carry-over from last meeting17:03
krtaylormainly because I was on vacation all last week17:03
* asselin_ was also on cavation last week17:03
*** julim has quit IRC17:04
krtaylorah, good to know17:04
asselin_well...not in a cave :)17:04
krtaylorhehheh17:04
marcusvrnI was on vacation last month....hehehe17:04
krtaylorlooks like we landed some good patches and contributions in the repo17:04
krtaylorgood stuff17:04
krtaylorso does anyone have any quick announcements? deadlines approaching?17:05
*** e0ne has joined #openstack-meeting17:05
mmedvedejust an fyi, recent upper-constraints update broke f21 gate17:05
mmedvedeboth us and upstream17:05
*** alexschm has quit IRC17:05
krtayloryes, thanks mmedvede17:05
mmedvedewell, upstream was broken already, but it broke it further :)17:06
*** devvesa has quit IRC17:06
krtayloranything else?17:06
krtaylor#topic Common CI17:06
*** openstack changes topic to "Common CI (Meeting topic: third-party)"17:06
krtaylordownstream puppet continues to move along17:06
*** jdurgin1 has quit IRC17:07
krtayloranything you'd like to work through here asselin_ mmedvede17:07
asselin_yes, nodepool refactoring is next17:07
asselin_lots of progress has been made17:07
asselin_would be good to focus reviews on those...it's a big change17:07
asselin_#link nodepool patches to review are on etherpad: https://etherpad.openstack.org/p/common-ci-sprint17:08
krtaylor#link https://review.openstack.org/#/q/topic:downstream-puppet,n,z17:09
*** HenryG has joined #openstack-meeting17:10
asselin_yes, the topic has a lot more changes17:10
krtaylorwas looking, lots of good work17:11
asselin_it would be good to focus on nodepool since it is a big change17:11
krtayloryes and mmedvede, yours look to be reviewed and ready to go, just need approval17:11
mmedvedekrtaylor: mine a low priority. But yes, a couple of them are ready17:12
krtaylorlots of depends-on links17:13
krtaylorfor nodepool, thats good17:13
asselin_mmedvede, I have those on my list too, but have been prioritzing nodepool17:13
krtaylorok, anything else here, other than do reviews?17:15
krtaylorok, we can come back to it if needed in open discussion17:16
asselin_i think that's it17:16
krtaylor#topic Spec for infra hosting a monitoring dashboard17:16
*** openstack changes topic to "Spec for infra hosting a monitoring dashboard (Meeting topic: third-party)"17:16
*** maishsk has quit IRC17:16
krtaylorthis has got some good reviews, not for content, which is a good sign17:16
krtaylorjhesketh didn't like the naming, which I can certainly change, but was hoping to just have the other spec moved by now17:17
krtaylor#link https://review.openstack.org/#/c/194437/17:17
krtaylorI did appreciate him not holding it up for naming in the rollcall, that was cool17:18
krtaylorsweston, are you around?17:18
krtaylorI didn't get a chance to follow up last week due to vacation17:19
krtaylorok, well, I'll ping him later - maybe we just need to move it with a new patchset to third-party-ci-tools17:20
*** HenryG has quit IRC17:20
krtaylorand capture the comments in a txt file17:20
*** MarkAtwood has quit IRC17:21
krtaylorthen we can abandon the infra spec17:21
*** banix has joined #openstack-meeting17:22
*** achanda has joined #openstack-meeting17:22
krtaylorso, also in the agenda and related is the last comment dashboard got merged to third-party-ci-tools17:22
krtaylorpatrickeast isn't in channel17:23
asselin_#link last-comment https://git.openstack.org/cgit/stackforge/third-party-ci-tools/tree/monitoring/lastcomment-scoreboard17:23
krtaylorI took an action to start an email discussion on which way to go - scoreboard or last comment17:24
krtaylorI didn't get to that before vacation17:24
*** jogo has quit IRC17:24
*** krypton has joined #openstack-meeting17:25
krtaylorI personally feel like we should just stay with scoreboard for now, but I don't have a strong preference17:25
krtaylorI just want to get something working now17:25
*** ndipanov has quit IRC17:25
krtayloryesterday17:25
mmedvedeunrelated, could people with +2 take a look at https://review.openstack.org/#/c/194490/ and approve maybe (scoreboard square stats, instead of piecharts)17:25
krtaylormmedvede, will do17:25
*** VW_ has quit IRC17:25
mmedvedethx17:26
*** jogo has joined #openstack-meeting17:26
*** e0ne has quit IRC17:26
*** dkranz has quit IRC17:26
krtayloralso, I feel that waiting on an email discussion would slow this whole process down again17:26
*** VW_ has joined #openstack-meeting17:26
krtaylorbut, we can, if it needs to happen17:26
*** salv-orl_ has quit IRC17:26
krtaylorok, not much input here so I'll go to the mail list17:27
krtaylornext then17:27
mmedvedeDo you think it would help if we throw together scoreboard POC puppet deploy?17:27
krtaylorand have it depends-on the spec? yes I do think that woul dhelp17:28
krtaylorwould help17:28
asselin_mmedvede, I think so, would be valuable regardless fo those setting it up17:28
krtaylor++17:28
mmedvedeasselin_: cool. I would look into creating module on github, or inside the third-party tools repo17:28
*** tiswanso has quit IRC17:29
krtaylorhm, repo is fine, I can refresh spec with a link17:29
asselin_+1 for  third-party tools repo17:29
*** IlyaG has quit IRC17:29
krtaylormmedvede, that would be very helpful17:29
*** tiswanso has joined #openstack-meeting17:30
mmedvedeasselin_: I am not clear on what would happen if infra would deploy it. Would they split out puppet module, or just use it as is out of third-party repo17:30
*** VW_ has quit IRC17:31
*** armax has joined #openstack-meeting17:31
mmedvedethat is the only concern for creating a separate repo for the module17:31
krtaylorthat would be a guide template I would think, it would be a new module17:31
asselin_mmedvede, yes tha's a good point.17:31
asselin_so if it's in github already, you can just import it.17:31
krtaylorright17:31
asselin_ok, I change my vote to new github repo :)17:32
*** VW_ has joined #openstack-meeting17:32
*** e0ne has joined #openstack-meeting17:32
mmedvedeI assume they would want control over it, and would not be ok to deploy from third-party tools :)17:32
*** IlyaG has joined #openstack-meeting17:33
krtaylormmedvede I guess I was thinking it would be used and moved, just a place to put it while spec was approved17:33
mmedvedeseparate github repo needs to happen, it is just a question whether we start in third-party tools, and then cut it out17:33
krtaylorexactly17:33
*** julim has joined #openstack-meeting17:34
*** shashank_hegde has joined #openstack-meeting17:34
*** claudiub has quit IRC17:35
*** nfedotov has quit IRC17:35
krtaylorok, so, I guess it can be fixed any way it is done, mmedvede what ever you want to do would be great17:37
mmedvede#action mmedvede look into creating puppet-scoreboard module17:37
*** dprince has quit IRC17:37
asselin_+1 mmedvede decides :)17:37
krtaylor+117:37
mmedvedethanks :)17:37
krtaylorthank you mmedvede , that will help - this is really important to start improving the trust in CI systems17:38
*** mrmartin has quit IRC17:38
asselin_+117:38
krtayloranything we can do to make this as painless for infra to implement is a plus17:38
*** pm90_ has joined #openstack-meeting17:38
krtayloranything else on this?17:39
krtaylor#topic TPCI Repo patches for review17:39
*** openstack changes topic to "TPCI Repo patches for review (Meeting topic: third-party)"17:39
krtaylorso I added a topic this week, that I like to see continue17:39
krtaylorthat is to remind everyone to go review our patches17:40
*** yamamoto has quit IRC17:40
krtaylor#link https://review.openstack.org/#/q/project:stackforge/third-party-ci-tools+status:open,n,z17:40
krtaylorfeel free to add patches that you feel need a broader audience17:41
*** dkranz has joined #openstack-meeting17:41
*** shashank_hegde has quit IRC17:41
krtaylorlike the one you brought up mmedvede17:41
krtaylorif time permits, we can review/approve them in this meeting17:42
krtaylorso, lets come back to that17:43
*** SourabhP has quit IRC17:43
krtaylor#topic Open Discussion17:43
*** openstack changes topic to "Open Discussion (Meeting topic: third-party)"17:43
*** claudiub has joined #openstack-meeting17:43
krtayloranyone?17:43
krtaylorelse, I am looking at:17:44
krtaylor#link https://review.openstack.org/#/c/194490/17:44
*** jprovazn has quit IRC17:45
mmedvedeunfortunately amazon scoreboard instance is down17:45
krtayloryes, mine is not coming up17:45
mmedvedethe code is working. I did not want to ninja-merge it all on my own17:46
krtaylormmedvede, appreciated, I agree with your comment17:46
mmedvedeI asked to use bar charts instead of pie charts17:46
krtaylorbut it would be nice to see it17:46
*** tsymanczyk has joined #openstack-meeting17:46
krtaylorpie is the "legacy" way of doing it, for those that remember radar17:47
krtaylorI don't have a preference really17:47
*** achanda_ has joined #openstack-meeting17:48
krtaylormmedvede,  did it not look right?17:48
*** david-lyle has quit IRC17:48
mmedvedepiecharts actually just a bad type of chart to use.17:48
mmedvedehard to compare17:49
krtaylorhehheh, ok, fair enough17:49
mmedvederesearch is on my side :)17:49
mmedvedeyeah, that is not really important in the end, as long as we have something working17:49
krtaylor+100017:50
krtaylorpatrickeast may be on vacation, I'd hate to hold this up17:50
*** achanda has quit IRC17:50
krtaylorif you have seen it and it is close enough, I'll approve it17:50
krtaylorI guess we could deploy it internally :)17:51
*** iurygregory has joined #openstack-meeting17:51
asselin_I don't have it deployed yet, but I will review it still17:51
mmedvedeyes, I saw the patch work. I can switch to patch commit internally and test17:52
krtaylormmedvede, how hard is it to update our internal with this patch?17:52
*** lhcheng has joined #openstack-meeting17:52
mmedvedekrtaylor: very easy17:52
krtaylor++17:52
*** Berezin has joined #openstack-meeting17:53
krtaylorok, we are getting close to time, anything else from anyone?17:53
*** otter768 has joined #openstack-meeting17:56
*** browne has joined #openstack-meeting17:56
krtaylorthanks everyone!17:56
asselin_thanks krtaylor17:56
mmedvedethank you krtaylor17:56
krtaylor#endmeeting17:56
*** openstack changes topic to " (Meeting topic: third-party)"17:56
openstackMeeting ended Tue Aug  4 17:56:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-08-04-17.00.html17:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-08-04-17.00.txt17:56
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-08-04-17.00.log.html17:56
*** ayoung has quit IRC17:56
*** jwy has joined #openstack-meeting17:57
*** dprince has joined #openstack-meeting17:57
*** dprince has quit IRC17:57
*** tiswanso has quit IRC17:58
*** pm90_ has quit IRC17:58
*** henrynash has joined #openstack-meeting18:00
*** haomaiwang has quit IRC18:00
*** roxanaghe_ has joined #openstack-meeting18:00
dolphmajayaa, 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
raildo\o18:00
david8hu\o18:00
samueldmqolá o/18:00
lbragstadwhoa, it's the old days, dolphm's running the show18:00
gyee\o18:00
brownehi18:00
david8huola18:00
geoffarnold\o18:00
rodrigodshey18:00
lhchengo/18:00
henrynashzipedeedodahzipedeeday18:00
tsymanczyko/18:00
*** haomaiwang has joined #openstack-meeting18:00
*** samleon_ has joined #openstack-meeting18:00
*** tiswanso has joined #openstack-meeting18:01
dstanekhello all18:01
geoffarnoldDo you have a macro for that, henrynash?18:01
iurygregoryo/18:01
*** Haneef has joined #openstack-meeting18:01
hogepodgeo/18:01
marekdhello18:01
dstanekshort agenda today18:01
henrynashno…have to spell it wromng every time18:01
*** otter768 has quit IRC18:01
*** kylek3h has quit IRC18:01
stevemari'm barely here18:01
dolphmdstanek: hope so!18:01
*** radez is now known as radez_g0n318:01
topolo/18:01
dolphm#startmeeting keystone18:01
henrynashstevemar: dress appropriatley please18:01
openstackMeeting started Tue Aug  4 18:01:52 2015 UTC and is due to finish in 60 minutes.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
*** qwebirc1001759 has joined #openstack-meeting18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
dolphmbut i'm going to start with a quick reminder18:01
openstackThe meeting name has been set to 'keystone'18:01
dolphm#topic Release schedule18:02
stevemarhenrynash: hehe18:02
*** openstack changes topic to "Release schedule (Meeting topic: keystone)"18:02
dolphmWe cut liberty-2 last week (yay! good job to all), so we're now staring down liberty-3 and thus FEATURE FREEZE is next up the calendar.18:02
*** armax has quit IRC18:02
dolphm#link https://launchpad.net/keystone/+milestone/liberty-218:02
dolphm#info Feature freeze is September 1st18:02
dolphmThat means we have until the end of the month to land all the featureful bits for Liberty (all blueprints and wishlist bugs).18:02
dolphm#link https://launchpad.net/keystone/+milestone/liberty-318:02
dolphmour next milestone target ^18:02
*** xingchao has quit IRC18:02
dolphmIf you have any questions, direct them to morganfainberg ;) because we’re moving on!18:02
dolphm#topic Add type as a filter for /v3/credentials18:03
*** openstack changes topic to "Add type as a filter for /v3/credentials (Meeting topic: keystone)"18:03
dolphm#link https://bugs.launchpad.net/keystone/+bug/146049218:03
openstackLaunchpad bug 1460492 in Keystone "List credentials by type" [Wishlist,In progress] - Assigned to Marianne Linhares Monteiro (mariannelinharesm)18:03
dolphm#link https://review.openstack.org/#/c/208620/18:03
*** dane_leblanc has quit IRC18:03
*** cbouch has quit IRC18:03
uvirtbotLaunchpad bug 1460492 in keystone "List credentials by type" [Wishlist,In progress]18:03
uvirtbotLaunchpad bug 1460492 in keystone "List credentials by type" [Wishlist,In progress] https://launchpad.net/bugs/146049218:03
dolphmThe question on the agenda is "Does this need a spec since it impacts API?" -- and the answer is, of course, absolutely yes. It's a user-facing change and the API impact must be documented in keystone-specs/api :)18:03
dolphmraildo, samueldmq, tellesnobrega: o/ floor is yours18:03
raildothanks :)18:03
raildohi guys, marianne start works with Keystone now, and we are looking for a low-hanging-fruit bug for her and we choose this bug18:03
gyeedolphm, that list doesn't look right, where's the x.509 one?18:03
stevemargyee: add it to the list18:03
raildoso to fix this bug we just add the 'type' in the hint of credentials, on this patch that dolph put here18:04
gyeestevemar, grasseyass amigo!18:04
raildosince this is an API change, we might need to open a blueprint/spec, but it's fairly small, so maybe not. So we want to know if the keystone core are happy with this way or we need to create a bp/spec for this?18:04
raildokeystone core team*18:04
stevemarraildo: as dolphm says we should open a spec for it18:04
dstanekraildo: see dolphm's answer above :-)18:04
*** VW_ has quit IRC18:04
dolphmraildo: it has an API impact change and so it must be documented in keystone-specs18:04
stevemarthere won't be much discussion on it18:05
dolphmraildo: the spec portion of it will naturally be super short18:05
lbragstadI don't think it needs to be super lengthy, but ++ to needing a spec18:05
*** VW_ has joined #openstack-meeting18:05
topol+++ to needing a spec18:05
raildodolphm: great :)18:05
dolphmraildo: it's the API documentation which is much more important for the long term18:05
lbragstad++18:05
raildodolphm: ++18:05
* stevemar wonders if we're too pedantic about this... 18:05
*** vivek-eb_ has quit IRC18:05
stevemardolphm: yes ++ on API doc update, the spec part makes me grumble a bit18:06
*** haneef_ has joined #openstack-meeting18:06
dstanekstevemar: about documenting the api or specs?18:06
stevemardstanek: ^18:06
rodrigodsthis is really a tiny fix, ++ to document first in the API spec18:06
stevemarits just a new hint to filter on, but whatever.18:06
rodrigodsand we already have the bug to track the change, anyway18:06
dstaneki'd actually be happy with just the api update since the commit message will link to the bug18:06
raildodolphm: so this will just happend in Mitaka, since we can't propose this for Liberty?18:06
*** pm90_ has joined #openstack-meeting18:06
stevemarraildo: it'll land in liberty18:06
dolphmi'd aim for liberty18:07
lbragstadraildo: we can target it to https://launchpad.net/keystone/+milestone/liberty-318:07
*** armax has joined #openstack-meeting18:07
raildogreat :)18:07
dolphmany other questions on this?18:07
stevemardolphm: nope18:07
dolphm#topic Use [extras] for package requirements depending on deployment options18:08
*** openstack changes topic to "Use [extras] for package requirements depending on deployment options (Meeting topic: keystone)"18:08
tellesnobregathanks18:08
dolphm#link https://review.openstack.org/#/c/207620/18:08
dolphmbknudson: o/ floor is yours18:08
* stevemar sneaks out18:08
*** stevemar has quit IRC18:08
*** shashank_hegde has joined #openstack-meeting18:08
*** wznoinsk1 has quit IRC18:08
dolphmhrm, bknudson has not made a peep so far this meeting18:09
dolphmbknudson: around?18:09
dstanekthat's unfortunate...i'm curious about this one18:09
topolsomeone try and wake bknudson up with a really bad patch toreview18:09
*** VW_ has quit IRC18:09
dolphmalright, let's move on -- we can loop back if he arrives18:09
dolphmdstanek: me too18:09
*** dan_ has joined #openstack-meeting18:09
topollet me try and grab him18:09
*** dan_ is now known as Guest4157418:10
*** wznoinsk1 has joined #openstack-meeting18:10
dolphm(i'll give topol a minute)18:10
gyeetopol, check the men's room to see if he needs a square18:10
* dstanek is whistling the Jeopardy theme18:10
lbragstadhe could be doing psirts?18:10
bknudsonI finally got back from team lunch18:10
dolphmbknudson: \o/18:11
bknudsonok, so the [extras] support seems to work18:11
*** dane_leblanc has joined #openstack-meeting18:11
bknudsonso I proposed the changes for ldap18:11
bknudsonwhich were in test-requirements18:11
bknudsonand also I think memcache and something else18:11
bknudsonso, going forward, we need to consider also other optional requirements18:11
dstanekbknudson: will the requirements get automatically updated in setup.cfg?18:12
*** VW_ has joined #openstack-meeting18:12
bknudsondstanek: I checked the source for the update tool and it looks like it.18:12
*** Guest41574 is now known as dank_18:12
*** qwebirc1001759 has quit IRC18:12
gyeebknudson, do we gate the extras the same way we do on the requirements18:12
bknudsongyee: yes, I think that's how the tool works18:12
dolphmshould we do this in a feature branch to test the infra workflow first?18:13
*** cbouch has joined #openstack-meeting18:13
bknudsonoh, so another example is fernet tokens, since there are specific requirements for those18:13
dolphmor can we look at another project doing this?18:13
bknudsonI haven't looked to see if anyone else has actually implemented it yet18:13
dstanekwill devstack need to be changed at all to make sure it's requirements are installed?18:13
dolphmbknudson: with more than one desirable 'extra', I assume you can do something like `pip install keystone[ldap,fernet]` ?18:14
bknudsondolphm: yes, that's the format18:14
dolphmbut that wouldnt impact config, just deps?18:14
bknudsonthere's no config change18:15
bknudsoncinder is also working on using this: https://review.openstack.org/#/c/203237/18:16
dolphmcinder is a fantastic use case for this18:17
dstanekbknudson: re: devstack ^18:17
bknudsonI proposed the change to devstack18:18
bknudsondevstack was pip install ldappool itself18:18
dolphmbknudson: do you need anything specific from us today, or was this topic just to raise awareness?18:18
dstaneknice18:18
bknudsonthis is to raise awareness amongst more than just the reviewers who look at these changes18:18
*** tongli has quit IRC18:19
dolphmif anyone wants to do further reading on extras:18:19
dolphm#link https://pythonhosted.org/setuptools/setuptools.html#declaring-extras-optional-features-with-their-own-dependencies18:19
*** dkranz has quit IRC18:19
dolphmbknudson: ready to move on?18:20
bknudsonyep, move on18:20
dolphm#topic State of feature/keystoneauth_integration branch18:20
*** openstack changes topic to "State of feature/keystoneauth_integration branch (Meeting topic: keystone)"18:20
dolphmbknudson: o/ floor is still yours18:20
bknudsonin case others aren't aware18:20
bknudsonthe feature/keystoneauth_integration branch is broken18:20
marekdwhy18:21
samueldmqdolphm: remember there is a policy topic :)18:21
bknudsonand I was wondering if anybody is willing to look into it18:21
dolphmsamueldmq: yes, it's next on the agenda18:21
bknudsontempest fails -- EndpointNotFound: publicURL endpoint for alarming service not found18:21
dolphmsamueldmq: although there are no details - please fill in the agenda!18:21
bknudsonI have no idea why this is happening on the feature branch and not master18:21
*** hrou has joined #openstack-meeting18:22
dstaneksamueldmq: i moved it to the end18:22
marekdbknudson: can you paste the link ?18:22
*** mrmartin has joined #openstack-meeting18:22
bknudsonso if you're actually interested in the keystoneauth work I'd suggest getting involved in it18:22
*** jckasper has joined #openstack-meeting18:22
dolphm#link http://logs.openstack.org/83/208583/1/check/gate-tempest-dsvm-neutron-src-python-keystoneclient/aa1fcbb/18:22
bknudsonhttps://review.openstack.org/#/c/208583/ is an example failing18:22
samueldmqdolphm: done18:22
samueldmqdstanek: thanks18:22
bknudsonand my attempt at merging master to the branch fails neutron tempest the same way18:23
dolphmmarekd: are you volunteering to investigate? :)18:23
marekdi'd rather not promise anything this week :(18:23
gyeebknudson, alarming service, that monasca?18:24
gyeelet me ping them to see18:24
bknudsonthe errors are in ceilometer18:24
marekddolphm: http://logs.openstack.org/83/208583/1/check/gate-python-keystoneclient-python27/7ff54a1/console.html this fails due to oauthlib18:25
*** yapeng has quit IRC18:25
dolphmoh wow, i didn't realize we have project monasca and project miniscus18:25
marekdwe had it in ksc and it was fixed18:25
marekddolphm: WHAT?!18:25
bknudsonthe python errors are known18:25
marekdminiscus?18:25
gyeenever heard of miniscus18:25
dolphmmarekd: logging as a service18:25
bknudsonit's the neutron tempest failure that's not fixed in the merge18:25
dolphmit's mostly abandoned https://github.com/ProjectMeniscus/meniscus18:25
*** ayoung has joined #openstack-meeting18:26
marekdbknudson: but the link you pasted fails on python18:26
ayoungsorry I'm late18:26
bknudsonmarekd: yes, I ran an experiment to see if master fails the same way or if it was introduced when I did the merge.18:26
marekdbknudson: the reviews to look into are here: https://review.openstack.org/#/q/status:open+project:openstack/python-keystoneclient+branch:feature/keystoneauth_integration,n,z , right?18:26
bknudsonthe merge is here: https://review.openstack.org/#/c/207267/18:27
bknudsonmarekd: yes, you can look at the open merges for the branch... all the newer reviews are failing.18:27
*** lpetrut has quit IRC18:27
*** armax has quit IRC18:28
*** andymaier has quit IRC18:28
*** kurtmartin has quit IRC18:28
gyeealarming should be monasca, ceilometer is metering18:29
*** Berezin has quit IRC18:29
*** lhcheng is now known as lhcheng_away18:29
*** Berezin has joined #openstack-meeting18:29
* marekd soon there will be Linux Kernel as a Service....18:29
bknudsongyee: I don't think monasca is running? http://logs.openstack.org/83/208583/1/check/gate-tempest-dsvm-neutron-src-python-keystoneclient/aa1fcbb/logs/ -- or maybe there's no log for it?18:29
dstanekmarekd: docker?18:29
*** armax has joined #openstack-meeting18:30
marekddstanek: along with Kubernetes, covered with OpenStack branded Manila18:30
dolphmi think we're off topic here :)18:31
*** HenryG has joined #openstack-meeting18:31
*** jasondotstar has joined #openstack-meeting18:31
marekdsure, sorry18:31
gyeebknudson, yeah, lemme sort it out with the monasca folks18:31
bknudsongyee: ok, thanks18:32
*** irenab has quit IRC18:32
bknudsonok, we can move on we don't need to debug it here18:32
bknudsonjust raising awareness in case somebody was concerned about it18:32
dolphm#info feature/keystoneauth_integration is failing gate18:32
*** dannywilson has quit IRC18:32
*** HenryG has quit IRC18:32
dolphmi assume stevemar and jamielennox would be interested as well - but they're both afk18:32
dolphmso, moving on!18:32
dolphm#topic Centralized policy distribution18:32
*** openstack changes topic to "Centralized policy distribution (Meeting topic: keystone)"18:33
dolphmayoung, samueldmq: o/ floor is yours18:33
samueldmqalright18:33
dolphmsamueldmq: there's no links or anything on the agenda - might want to provide those first18:33
samueldmqspecs are under review, all concerns addressed, we need some weight/decision on acceptance18:33
*** numan has quit IRC18:33
*** claudiub|2 has joined #openstack-meeting18:33
samueldmq#link https://review.openstack.org/#/c/197980/18:33
samueldmq#link https://review.openstack.org/#/c/134655/18:33
*** irenab has joined #openstack-meeting18:34
gyeesamueldmq, that's the stuff you demoed at the midcycle right?18:34
ayoungI can proxy for jamie18:34
samueldmqgyee: yes18:34
gyeelets do this!18:34
samueldmqwe need reviews .. we have middleware  + oslo.policy code18:34
samueldmqand I am working on the keystone server bit already18:34
henrynashsamueldmq: so the thing I hear most of all from people is whether this is a burning issue that needs to be solved now (and hence needs an SFE)…perhaps you could address that issue18:34
*** bswartz has quit IRC18:34
samueldmqdstanek is taking care of adding support to CacheControl at ksclient18:34
ayoungdolphm, since we hhave your attention;  does the dynamic policy approach seem right to you?18:35
*** HenryG has joined #openstack-meeting18:35
ayoungI'd rather hash it out now before we get too far into implementation;18:35
dolphmayoung: by dynamic, do you mean centralized distribution?18:35
*** dannywilson has joined #openstack-meeting18:35
samueldmqayoung: I think so, I addressed all his concerns in the specs18:35
*** claudiub has quit IRC18:35
samueldmqdolphm: yes18:35
ayoungthe unified stuff kindof dies in committee, and that was based on a dolphm comment at midcycle back in san antonio18:35
ayoungdolphm, yeah, centralized, but also unified18:36
dolphmayoung: then yes, but i can't speak for deployers18:36
ayoungfair enough..I just want to make sure that we've got a consensus.18:36
*** pvaneck has joined #openstack-meeting18:36
henrynashayoung: there’s no spec we are votinh on her for unification, is there?  I hope not18:37
dolphmwhat was the outcome of the mailing list discussion? i don't think i ever saw the thread18:37
*** Leonr has joined #openstack-meeting18:37
ayoungdolphm, one issue, which I know you commented on in code review is the "deleted proejt" issue18:37
samueldmqhenrynash: we just targeted the distribution for L18:37
*** dzamboni has quit IRC18:37
*** radez_g0n3 is now known as radez18:37
samueldmqhenrynash: which are those 2 specs are about18:37
henrynashsamueldmq: ++18:37
dolphmhenrynash: i imagine unification would be an operator decision - nothing to do with the implementation18:37
samueldmqwhich is what ...18:37
ayoungif we scope everything, what do we do to unlock a resource where we deleted the project in keystone but the remote service didn't get or process the notification18:37
dolphmhenrynash: although it'd be great to publish a unified policy file, or a tool to create one18:38
*** rbowen has quit IRC18:38
gyeewhat does project deletion have anything to do with policies?18:38
ayoungdolphm, ++  provide a unified  was my goal.  In order to do that, there are lots of nits to knock down18:38
david8hudolphm,  who would be the consumer?18:38
ayounggyee, policy needs to provide acess to the API in order to delete a proejects rsources18:39
dolphmayoung: i think services should be cleaning up their own resources in response to deleted project notifications - not some cleanup process making HTTP API calls through an authz layer.18:39
ayoungif I need to get a scoped token, but that project is deleted, I can't get scoped token18:39
samueldmqgyee: yes I think we're off topic ...18:39
dolphmayoung: so, that example seems like a non-issue to me18:39
ayoungdolphm, agreed, but there is a long way to go until they can do that18:39
dstaneksorry got distracted18:39
dstanekback now18:39
*** MarkAtwood has joined #openstack-meeting18:39
ayoungand there is always the possibility of a missed notification18:39
ayounghow do we handle in the interim?18:39
henrynashayoung, dolphm: as you know, I am fully against a unifies policy file…..that doesn’t mean there aren’t other ways (in the future) of provding common rules etc. across the policies of different projects18:40
ayounghenrynash, "Fully against?"18:41
*** yamamoto has joined #openstack-meeting18:41
samueldmqwe've had a spec-freeze exception request, spec-freeze time is over and we didn't reach a decision18:41
*** bapalm_ has joined #openstack-meeting18:41
ayoungdolphm, so, lets assume for now that there are missed notification etc...the only other option I cansee is "admin role on admin proejct indefault domain can delete anything"18:41
samueldmqshould I submit a FFE now ? are cores ok with this feature landing in Liberty?18:41
henrynashayoung, samueldmq: regardless of the nits and/or specifics we are arguing about…the question here is whether we haev a burning issue that requires an SFE…i.e. is the problem one that causes us to make an exception to our working practices.  I support teh centralised approach, I just haven’t seen the evidnce for the urgency18:42
dolphmayoung: so, that sounds like authorization at the service level -- not specific to any tenant18:42
lbragstadI'd like to see some more buy-in from an operator18:42
henrynashayoung, sameuldmq: which customers are shouting about the problem18:42
ayounglbragstad, gyee is going to poperators meetup.  He'll proxy18:42
gyeeI am attending the ops midcycle18:42
samueldmqhenrynash: well, the code is under review already, there are jsut some missing bits18:42
samueldmqhenrynash: we just need reviews, nothing more18:43
dstaneki agree with henrynash. there is no reason to rush this18:43
henrynashsamueldmq: with respcet, that doen’t answer the question18:43
samueldmqhenrynash: we were'nt able to have a single decision on SFE during L218:43
*** eantyshev has joined #openstack-meeting18:43
samueldmq:/18:43
ayounghenrynash, urgency is that we can't seem to make any progress.  Either reviews are too big and then sl=plit, or too small and then provide less value...can't win.18:43
ayoungSo, we've reduced scope and reduced scope18:43
henrynashayoung: so why would we do this in a X-3 cycle>18:43
henrynash?18:43
ayoungand we have it down to "fetch from centralized" as simple as possib;le18:43
dstanekgyee: could you bring it up? i'd love to have some feedback18:43
*** novas0x2a|laptop has joined #openstack-meeting18:44
ayounghenrynash, I proposed back pre Summit18:44
ayoungthis stuff takes time18:44
gyeedstanek, yes, will do18:44
ayoungThe win for theoperators, when this is all in, is that they can delegate to their own users the ability to share resources18:44
ayoungIf I am a consumer of a company cloud, and I need to share with...say jamielennox who also works here...I should not need to go to the central admin to get him acessto my proejct.  All of this is driving toward that18:45
david8huayoung, json is still going to be a challenge for deployers.18:45
ayoungdavid8hu, may that be the worst we have to face18:45
*** HenryG_ has joined #openstack-meeting18:46
henrynashayoung: I know….but we either have festures freezes for a reason, or we don't18:46
ayounghenrynash, this change is in oslo messaging at this point, which was outside the "locked to release" in the past18:46
*** yamamoto has quit IRC18:46
dolphmdavid8hu: there's a conversation on openstack-dev about building a proper UI for policy editing18:46
dolphm#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/071184.html18:47
ayounghenrynash, does "trial and error" count as a reason?  We've had it at different points in the cycle in the past.18:47
*** gampel has joined #openstack-meeting18:47
*** pabelanger has joined #openstack-meeting18:48
david8huayoung, debug aspect of things is going to be more challenging than it is today, but it can be address through proper documentation.18:48
bknudsonmaybe horizon can solve all the issues that dynamic policies is targeting18:48
*** HenryG has quit IRC18:48
ayoungso...can we please make progress on this?18:48
david8hudolphm, +1, I would love to join that conversation.  If you can send me links offline, it will be great.18:49
dolphmdavid8hu: the link is above18:49
henrynashayuong: so to introdiuce something as experiemental that seems OK,…again, not sure in an X-3 cycle where we’ll be craming to other already approved items in18:49
david8husaw it18:49
david8huthx18:49
*** cbouch has quit IRC18:49
ayoungat least approve the spec for backlog?18:50
samueldmqayoung: ++18:50
*** ebalduf has joined #openstack-meeting18:50
samueldmqayoung: henrynash  and if we come with all code implemented in the ffe request, we analyze it apart from the specs approval18:50
henrynashayoung: sure, that gets my vote…as I say in my comment on teh patch, I support this, just not sure why it needs the urgency of getting into L18:50
*** rbowen has joined #openstack-meeting18:51
samueldmqdolphm: you agree ^18:52
samueldmq?18:52
ayounghenrynash, because if it is in L then people can use it18:52
ayoungand until people use it we don't get feedback18:52
*** SourabhP has joined #openstack-meeting18:52
gyeejust download the patch and test drive it, if it worth the money, approve it :)18:52
*** ub has quit IRC18:52
ayoungand until we get feedback we are doing ivory tower development18:52
amakarovsamueldmq, is it considered ok just to reference another spec? "Please refer to the Keystone Middleware spec"18:52
*** SourabhP has left #openstack-meeting18:52
ayoungand code that is not in production is like excess inventory18:52
*** oanufriev has quit IRC18:52
*** temujin_ has quit IRC18:52
*** boris-42 has joined #openstack-meeting18:53
samueldmqamakarov: yes it is, so I don't need to repeate all the text there18:53
dolphmayoung: people that are interested will review and test patches18:53
samueldmqamakarov: it was a request from some cores already18:53
dstanekamakarov: yes. i complained that there was too much of the same content in the specs18:53
david8huayoung, +1, need ways to get all data points we need.18:53
dstaneki couldn't see what was meant to be the actual change18:53
amakarovsamueldmq, dstanek thanks, +1 from me then :)18:53
*** mmmpork has joined #openstack-meeting18:53
dolphmdstanek: ++18:53
*** sudipto has quit IRC18:54
dstanekif we built it will they come?18:54
samueldmqso yes, I think those specs should be ready to be approved to backlog, since all the concerns from core-reviews were addressed18:54
*** ub2 has joined #openstack-meeting18:54
ayoungdstanek, unless we build it, they can't come18:55
*** ebalduf has quit IRC18:55
gyeedstanek, yes, I bet my beer money on it18:55
dstaneki really do think we need to find an operator that we know will try it because they want it18:55
lbragstaddstanek: ++18:55
dolphmdstanek: ++18:55
dstanekgyee: will you have HP start using it in test labs?18:55
gyeedstanek, yes!18:55
lbragstadI just think it will help guide an implementation, that's all18:55
david8hudstanek, ayoung, need a very good PR person to sell it :)18:56
ayoungdstanek, this is a building block.  We can't give them what they really need yet.  They might or might not try this, but if we don't get it out there, they certainly won't18:56
dolphmayoung: you don't need to merge things to master for get feedback from early adopters18:56
dstanekdavid8hu: no! that means we're doing it wrong18:56
ayoungdolphm, I'm not merging code.  I'm trying to get the spec in18:56
ayoungthat means agreement on the direction18:57
david8hudstanek, no one is using the v3 policy api today.  I am hoping we can do better this time.18:57
gyeeayoung, we also have the big tent now, just saying :)18:57
dstanekgyee: have you gone through all of the proposals?18:57
dstanekdavid8hu: then i would question if it was needed :-)18:57
gyeedstanek, you have a pop quiz coming?18:57
dolphmayoung: are there any early stakeholders for this besides yourself and samueldmq?18:57
dstanekgyee: no, but if you're going to help drive as a sort of 'business owner' you should go through them and see if they are doing what you need18:58
*** oanufriev has joined #openstack-meeting18:58
dstanekdolphm: maybe gyee is a stakeholder18:58
*** aukhan has joined #openstack-meeting18:58
dolphmgyee: ?18:58
*** Berezin has quit IRC18:58
gyeedstanek,dolphm, yes, I am involved18:59
dolphmgyee: as a developer or from an operations perspective?18:59
* gyee puts on his operator hat18:59
* dstanek hears the chanting. 'do it, do it, do it'18:59
*** cbouch has joined #openstack-meeting18:59
samueldmqdstanek: o/18:59
*** haomaiwang has quit IRC19:00
samueldmqso we get the specs approved and I will come with the ffe request19:00
dolphmgyee: i'm not sure if that's a yes or no19:00
samueldmqthen we analyze it next meeting19:00
samueldmqdolphm: ^ sounds good ?19:00
gyeedolphm, as an operator19:00
*** Shrews has joined #openstack-meeting19:00
*** lblanchard has quit IRC19:00
gyeeeating the dog food19:00
ayoungdolphm, so you are implying that no  features are going to go in upstream until they are in active deployment somehwere?19:00
*** haomaiwang has joined #openstack-meeting19:00
dolphmayoung: of course not19:01
samueldmqI think time's over19:01
*** oanufriev has quit IRC19:01
dolphmayoung: samueldmq: but the issue i've seen on this topic for the past 6+ months is a lack of operator interest. if we're overlooking those voices, please point them out / have them speak up in the spec review.19:01
gyeecutting edge, how we roll19:01
dolphmand yes, time. samueldmq: thanks19:01
dolphm#endmeeting19:01
*** ryanpetrello has quit IRC19:01
*** openstack changes topic to " (Meeting topic: third-party)"19:01
openstackMeeting ended Tue Aug  4 19:01:40 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-08-04-18.01.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-08-04-18.01.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-08-04-18.01.log.html19:01
dolphm(apologies for going over)19:01
*** oanufriev has joined #openstack-meeting19:02
*** esker has joined #openstack-meeting19:02
*** DericHorn-HP has quit IRC19:02
funginp19:02
jeblairdolphm: noted on your account balance!19:02
clarkbhello19:02
dolphm=(19:02
fungii always enjoy the end of your meetings ;)19:02
*** PrashantS has joined #openstack-meeting19:02
pleia2o/19:02
*** dkranz has joined #openstack-meeting19:02
zaroo/19:02
Clinto/19:02
*** browne has left #openstack-meeting19:02
aukhangood morning19:02
*** DericHorn-HP has joined #openstack-meeting19:02
asselin_o/19:02
jheskethMorning19:02
aukhano/19:02
*** tsymanczyk has left #openstack-meeting19:02
pabelangero/19:02
fungii am here, but just came back from having a wisdom tooth pulled so holding an ice pack with one hand and typing with the other19:03
ianwo/19:03
fungithus, slow typing19:03
pleia2fungi: ouch19:03
jasondotstaro/19:03
redroboto/19:03
Clintyou need some kind of device to clamp it on19:03
jeblairthis is a great time to trick fungi into doing things19:03
jeblair#startmeeting infra19:03
openstackMeeting started Tue Aug  4 19:03:53 2015 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
openstackThe meeting name has been set to 'infra'19:03
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:04
jeblair#link previous meeting http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-07-28-19.01.html19:04
jeblair#topic Announcements19:04
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:04
jeblair#topic Announcements: Project management19:04
*** openstack changes topic to "Announcements: Project management (Meeting topic: infra)"19:04
jeblairwe've made a lot of changes with how we work recently:19:04
jeblairwe write specs for any moderately complex task so we can articulate what we want to accomplish and help reviewers understand our changes19:04
jeblairwe have priority efforts so we know where we should look first to keep our most important efforts moving19:04
jeblairand we've radically decentralized with the formation of the council composed of core teams19:04
jeblairhowever, recently i feel like it's getting harder to see where we are in progressing our work19:05
nibalizerhi19:05
*** ayoung has quit IRC19:05
jeblairthis is important because it means an effort could be blocked on something without our realizing how to move it forward19:05
jeblairor you might imagine some dependency on an effort that involves a transition, and it's not clear whether that's happened yet19:05
*** bswartz has joined #openstack-meeting19:05
jeblairall of this can be addressed with better project management (which when done poorly is just nagging, but when done well helps facilitate communication and progress among a distributed team)19:05
*** Anh has joined #openstack-meeting19:05
jeblairso i've asked Clint to help us out with that19:05
*** Anh has quit IRC19:06
jeblairand in a fit of generosity, he accepted :)19:06
*** henrynash has quit IRC19:06
fungithanks Clint!!!19:06
*** xingchao has joined #openstack-meeting19:06
jeblairit's a pretty open ended problem and he'll be looking at how to actually accomplish it19:06
mrmartino/19:06
jeblairbut i think there's a lot of room for improvement here, and i think it could be really helpful to all of us19:06
*** andersonvom has joined #openstack-meeting19:06
jeblairi've asked him to start by focusing on the priority efforts, and also maniphest (as i believe it will also be helpful in this regard)19:06
jeblairi expect that he may have a lot of questions for folks, so please help him out19:06
Clinti will definitely be asking questions19:06
mrmartinwhere is Monty?19:07
jeblairClint: cool :)19:07
*** Piet has quit IRC19:07
jeblairmrmartin: on a pacific island19:07
jheskethClint: sounds great :-)19:07
Shrewsmonty is vacationing19:07
aukhan:)19:07
*** yolanda has joined #openstack-meeting19:07
jeblairwe should totally have a "where is monty" agenda item; though this isn't it :)19:07
Shrewsjeblair: i have considered a cross-platform app19:08
*** stevemar has joined #openstack-meeting19:08
jeblairany other questions or helpful suggestions for Clint?19:09
jeblairClint: thanks!19:10
* Clint nods.19:10
jeblair#topic Specs approval19:10
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:10
*** coolsvap is now known as coolsvap|away19:10
jeblair#topic Specs approval: Zuul v3 (jeblair)19:10
*** openstack changes topic to "Specs approval: Zuul v3 (jeblair) (Meeting topic: infra)"19:10
*** shashank_hegde has quit IRC19:10
*** salv-orlando has joined #openstack-meeting19:10
*** oanufriev has quit IRC19:10
jeblair#link zuulv3 spec http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html19:10
jeblair#info zuulv3 spec was approved19:10
pabelangerNiiice19:10
pleia2huzzah19:10
*** claudiub|2 has quit IRC19:10
jeblairsome quick thoughts on that:19:11
*** oanufriev has joined #openstack-meeting19:11
jeblairi'm thinking of revising the spec to suggest that we do development in branches on both zuul and nodepool19:11
jhesketh+119:11
jeblairand i'm going to collect the names of folks from the summit etherpad and those who otherwise volunteered to help and see if we can have a huddle and discuss how to proceed19:11
jeblairmaybe divvy up some items19:12
jeblairso keep an eye out for that19:12
greghaynesThere might be a lot of churn in nodepool with both v3 and builders at the same time19:12
*** stevemar has quit IRC19:12
greghaynesmaybe too much rebasing19:12
jeblairgreghaynes: with branches we can use merge commits!19:12
greghaynesand branching will make that a bit worse19:12
greghaynesyes, there will be a pretty big delta, its more clear to resolve but still a lot of drift19:13
*** lblanchard has joined #openstack-meeting19:13
jeblairyeah, if we can get builders in soon, that will help19:13
jeblairbut if we don't, i'm sure we'll manage19:13
*** dprince has joined #openstack-meeting19:14
jeblair#topic Schedule Project Renames19:14
*** openstack changes topic to "Schedule Project Renames (Meeting topic: infra)"19:14
jeblairi'm going to abuse this topic since i didn't put in what we should really start talking about...19:14
jeblairwhich is that the "put all new projects in openstack/" resolution was approved19:15
jeblair#link http://governance.openstack.org/resolutions/20150615-stackforge-retirement.html19:15
jeblairso we should work on a plan for dealing with that --19:15
greghaynesdoes this mean we are also moving the existing stackforge ones over?19:15
jeblairdo we want to perform an automatic mass-migration simultaneously ourselves?19:15
greghaynesoh wow, it does19:15
*** henrynash has joined #openstack-meeting19:16
fungii think if we don't move everyone at once, it will be painful19:16
jeblairor let projects do it on their own time-frame, but maybe we batch them so we do moves every 2 months or so...?19:16
clarkbwe should try to get a list of those that want to be attic'd as part of hte process too (thinking at least pecan)19:16
fungii mean, _more_ painful19:16
jeblairoh, also, i would like to end the practice of moving things to the attic19:17
clarkbjeblair: ok, what do we do about pecan then? just hav ethem update that repo with a "use github" message instead?19:17
jeblairi previously had a week preference not to attic things19:17
fungiyeah, attic means more pointless renaming19:17
clarkb(I am happy either way, but we do need to accomodate their concerns)19:17
jeblairbut now that i have seen projects moved to the attic with absolutely no indication they are actually dead (complete with transparent github rewrites so their users won't even notice), i have a _strong_ conviction it's a bad idea.19:18
*** xyang has quit IRC19:18
jeblairclarkb: yeah, so perhaps we let defunct (for whatever reason) projects just stay in stackforge19:18
*** penick has joined #openstack-meeting19:18
fungiif we need a script to push up a boilerplate readme and file deletion change along with a read-only acl update, that's still a much better use of our time to semi-automate19:18
jeblairhow about this:19:18
jeblairwe ask projects to sign up to be moved to openstack.  if they don't sign up, they end up on a list of projects we will make read-only.19:19
*** henrynash has quit IRC19:19
jeblairwe publicise that list, and timetable, etc, so people can review it.19:19
jeblairthen we move them en-masse, ourselves.19:19
clarkbthat seems reasonable19:19
jeblair(and, obviously, do not move the ones on the read-only list)19:20
greghaynes++19:20
pleia2"publicise" may be tricky, but can we poll+send to cores on all the projects?19:20
pleia2I think some stackforge folks don't read all of openstack-dev19:20
clarkbpleia2: ya that should be easy with a gerrit api script19:20
pleia2cool19:20
nibalizerwill 'read-only' projects be listed anywhere other than gerrit acls?19:20
*** mrunge has quit IRC19:20
*** unicell has quit IRC19:20
*** unicell1 has joined #openstack-meeting19:20
fungishould be trivial to build a contact list. oh, i already almost have that written i think19:20
nibalizera number of people (and me) write scripts like for repo in `gerrit ls-projects | grep infra | grep puppet`; do something; git review; done19:21
nibalizerand inactive/readonly projects in that list screws that up19:21
*** vivek-ebay has joined #openstack-meeting19:21
fungi#link http://git.openstack.org/cgit/openstack-infra/system-config/tree/tools/who-approves.py19:21
jheskethI wonder if ls-projects can be limited to non-readonly somehow?19:21
*** nadya has joined #openstack-meeting19:22
jeblairhow about this: i write a message to openstack-dev giving folks general context for governance resolution, since it still hasn't really been publicised, and let people know that we will start planning a future move. then after that, i'll start a thread for planning the actual move, and we can work out logistics and dates.19:22
pleia2+119:22
clarkbjeblair: sounds good to me19:22
nibalizerthat sounds good19:23
jeblairnibalizer: maybe we should look into whether we can do something similar with the rest api?19:23
jeblair#action jeblair write message to openstack-dev with overall context for stackforge retirement/move19:23
fungisounds great. we also all need to remember to remind people who don't read closely that this is a purely cosmetic change. there's no implied governance alteration needed/accompanying it19:23
jeblair#action jeblair start discussion thread about logistics of repo moves19:24
*** ajiang has left #openstack-meeting19:24
clarkbits a thing that only really makes sense in the github world19:24
*** PrashantS has quit IRC19:24
clarkband we github so :/19:24
fungiwe're just "getting rid of the word 'stackforge' in our urls"19:24
*** PrashantS has joined #openstack-meeting19:24
*** ajiang has joined #openstack-meeting19:25
fungi(and replacing it with another word we already use a lot)19:25
jeblairyep.  and maybe in 6 months or a year, we have a discussion like "hey, so should we remove openstack/ from git.o.o"? :)  (would be so much less typing)  but that's getting way ahead.19:25
*** oanufriev has quit IRC19:25
jeblairokay, i think we know generally how to proceed here, thanks19:25
jeblair#topic Priority Efforts (Migration to Zanata)19:25
* fungi would (eventually) love that19:25
*** openstack changes topic to "Priority Efforts (Migration to Zanata) (Meeting topic: infra)"19:25
pleia2hey19:26
jeblairpleia2: howdy!19:26
pleia2so I've got UbuConLA, some hiking in the Andes and then the Ops Mid-cycle in the next two weeks (starting tomorrow)19:26
pleia2I don't want my absence to cause problems for the i18n team and StevenK who are still working on the Zanata stuff19:26
pleia2on line 200 of https://etherpad.openstack.org/p/zanata-install I listed my outstanding tasks, so I'd like to do a soft hand-off to someone while I'm gone so things keep chugging along19:27
clarkbI can help out there19:27
clarkbI am relatively familiar with how all that fits together so happy to19:27
clarkb#link https://etherpad.openstack.org/p/zanata-install19:27
pleia2and as always, if I can get folks to review open zanata reviews, it would get StevenK unstuck in a few places https://review.openstack.org/#/q/status:open+topic:zanata,n,z19:28
jeblair#info clarkb is pleia2 for next 2 weeks19:28
pleia2https://review.openstack.org/#/c/206305/ needs another +219:28
clarkbI did review the jeepyb change stevenK wrote yesterday19:28
clarkbit looks good19:28
pleia2great19:28
clarkbneed to find the puppet change to run it but that should be straightforwrad19:29
*** PrashantS has quit IRC19:29
clarkbwill review 206305 today19:29
jeblairclarkb: https://review.openstack.org/20881119:29
jeblairtopic:zanata ftw19:29
pleia2he also said he'll be working on 203928 this week, so that WIP will move along soon19:29
*** gyee has quit IRC19:29
clarkbthe jeepyb change is under that topic too, perfect19:29
*** ryanpetrello has joined #openstack-meeting19:29
jeblairclarkb, pleia2: thanks!19:30
pleia2I think that's it, I'm around for the rest of the day if clarkb needs any more details for anything19:30
pleia2thanks clarkb :)19:30
jeblair#topic #topic Puppet-httpd replacement of puppet-apache (pabelanger/nibalizer)19:31
*** openstack changes topic to "#topic Puppet-httpd replacement of puppet-apache (pabelanger/nibalizer) (Meeting topic: infra)"19:31
jeblairgah19:31
jeblair#topic Puppet-httpd replacement of puppet-apache (pabelanger/nibalizer)19:31
*** openstack changes topic to "Puppet-httpd replacement of puppet-apache (pabelanger/nibalizer) (Meeting topic: infra)"19:31
*** angdraug has joined #openstack-meeting19:31
nibalizerthis is quite close to being done19:31
pabelangeraye19:31
nibalizerhttps://review.openstack.org/#/c/198819/ one more19:31
nibalizerto system-config this time, not a module19:32
*** pm90_ has quit IRC19:32
*** GB21 has joined #openstack-meeting19:32
pabelangerhttps://review.openstack.org/#/c/201759/ is for grafana19:32
pabelangerand system-config too19:32
*** ayoung has joined #openstack-meeting19:32
nibalizerits also worth noting that the existence of a patch like this demonstrates that there is still active configuration inside system-config that hasn't been pushed out into the modules, but thats a different topic19:32
jeblairnibalizer: yeah, some of thot is probably some low-hanging fruit19:33
nibalizerthere are a couple follow on activites such as removing if statements that paul had to hack in, as well as finally removing apache 0.0.4 from modules.env19:33
nibalizerbut I'm very pleased with how quickly and effectively this went19:34
jeblair(static.o.o is not lhf, but many of the others are)19:34
nibalizerthanks pabelanger19:34
pabelangerhttps://review.openstack.org/#/c/205696/ is the removal of puppet-apache19:34
jeblairpabelanger, nibalizer: indeed, thanks! :)19:34
pabelangernibalizer: np, was strightforward19:34
*** GB21_ has quit IRC19:35
nibalizerthats all I have on that topic19:35
jeblaircool, thanks19:35
jeblair#topic Restore from backup test (jeblair)19:35
*** openstack changes topic to "Restore from backup test (jeblair) (Meeting topic: infra)"19:35
jeblairthis is a thing we have talked about a bit... but haven't really done19:36
*** tiswanso has quit IRC19:36
jeblairi mean, backups are great, but you don't really have them unless you've used them19:36
jeblairwhen i set some of this up, early on i did some limited restore tests19:36
*** Berezin has joined #openstack-meeting19:36
jeblair(like log into the server and restore to a dir in /tmp/)19:36
jeblairbut that was a long time ago, and not at all systematic, nor has it been done for every host19:37
clarkbwhen I updated the docs I too restored specific files from backup to test the docs19:37
greghaynesFor some context - what all is this a backup of?19:37
clarkbbut has all those same issues19:37
jeblairgreghaynes: ah great question!19:37
jeblairwe perform fairly traditional filesystem backups of major hosts to an off-host location19:37
*** oanufriev has joined #openstack-meeting19:37
jeblairspecifically a server in a different cloud account on a different provider19:37
jeblairer19:38
jeblairstrike different provider19:38
greghaynesheh, different region?19:38
fungi(eventually different provider)19:38
clarkbyes different region19:38
jeblairyes different region19:38
greghaynesok, gotcha19:38
greghaynesI am really a fan of daily restore from backup jobs :)19:38
jeblairwe used to, but then the 'different provider' did one of the things that the diversity is supposed to protect us from19:38
*** oanufriev has left #openstack-meeting19:38
jeblairwhich is, they deleted the host19:38
jeblairgreghaynes: no points for guessing which19:39
greghayneshaha19:39
*** tiswanso has joined #openstack-meeting19:39
*** tiswanso has quit IRC19:39
*** britthouser has joined #openstack-meeting19:39
*** yolanda has quit IRC19:39
*** jasondotstar is now known as jasondotstar|afk19:39
jeblairbut yeah, ideally, we back up to multiple locations that are as diverse from where we actually run these as possible.  we are not currently living the dream.19:39
*** jcoufal has quit IRC19:39
*** yolanda has joined #openstack-meeting19:40
jeblairat any rate, i put this on the agenda so we could start talking about it and brainstorming...19:40
fungithough it makes a great point. prepare for the loss of your backup server ;)19:40
*** britthou_ has joined #openstack-meeting19:40
clarkbwe do have a third region available to us to add diversity19:40
jeblair(we should probably work on replacing the one that was deleted, i think we can now)19:41
*** andersonvom has quit IRC19:41
funginameless provider seems to have gotten a little more reliable about not randomly deleting our servers19:41
jeblairsince i did most of the work designing the system as is, i think i'd like someone else to take the lead on evaluating our preparedness to restore19:41
jeblairi was imagining we design and conduct a periodic drill, but i'm also open to greghaynes suggestion of automated continuous testing...19:42
*** baoli has quit IRC19:42
clarkbnot to derail on specifics, but one related item I think we need to handle better is the we ran out of disk on backup server issue since our backups are append only19:42
*** thangp has quit IRC19:42
jeblairclarkb: agreed19:42
*** dane_leblanc has quit IRC19:42
*** britthouser has quit IRC19:43
fungii like the automated continuous testing idea if it's feasible (i mean, we already do a lot of that) but would need some way to assure we pay attention to failures19:43
jeblair#link http://docs.openstack.org/infra/system-config/sysadmin.html#backups19:43
greghaynesYea, im sure its a matter of how much work restoring from backup is. Also, the automatedish setup is only useful if you have a good way to notice when a fialure happens19:43
*** lpetrut has joined #openstack-meeting19:43
fungiperiodic drills are something we can have as early as today if we want them, modulo available root sysadmin availability19:44
*** thangp has joined #openstack-meeting19:44
*** mrmartin has quit IRC19:44
greghaynesGoing through one is probably a prereq for knowing what all an automated solution would need to do, also19:44
*** kurtmartin has joined #openstack-meeting19:44
greghaynesat least for me19:44
*** enikanorov_ has joined #openstack-meeting19:45
jeblairgreghaynes: good point19:45
jeblairso probably we should start with that, and then see whether we think the process is amenable to automation19:45
greghaynes++19:46
jeblairat any rate, i'm looking for not-me volunteers for this... think about whether you can help out, and we'll check back in next week19:46
*** temujin_ has joined #openstack-meeting19:46
fungiyep, identifying _what_ we want to check is probably step #119:46
*** lsmola has quit IRC19:46
*** samueldmq has quit IRC19:46
*** samueldmq has joined #openstack-meeting19:47
jeblair#topic  Puppet apply coverage for fedora21 / centos7 (pabelanger)19:47
*** openstack changes topic to "Puppet apply coverage for fedora21 / centos7 (pabelanger) (Meeting topic: infra)"19:47
*** mrmartin has joined #openstack-meeting19:47
pabelangerhey19:47
jeblairpabelanger: o/19:47
pabelangerthis one is quick, I have 2 reviews up to add support for Fedora21 and Centos7 for our puppet-apply tests.19:47
pabelangerhttps://review.openstack.org/#/c/203756/19:47
pabelangerhttps://review.openstack.org/#/c/203759/19:47
*** ashuk has joined #openstack-meeting19:47
pabelangerthey are non-voting jobs right now, but want to kick them to voting for next week19:48
*** enikanorov has quit IRC19:48
pabelangerso, just need some help reviewing and approving19:48
jeblairoh hey, they make the jobs go green, respectively19:48
jeblairthis seems like a swell idea19:49
* clarkb will add to review list today19:49
ianwwhile people are thinking about puppet-apply, https://review.openstack.org/205873 & https://review.openstack.org/206319 are about running it with project-config19:49
*** thangp has quit IRC19:49
jeblairianw: oh thanks for bringing that up...19:49
pabelangerthats all I had19:50
jeblairi've been thinking about that, and i think there's the idea that it should have an impact, though it doesn't in our current jobs19:50
*** lhcheng_away has left #openstack-meeting19:51
nibalizerI think it matters if project_config ever grows a puppet template19:51
nibalizerbut right now it does not19:51
jeblairthat is to say, it really is related, but our apply jobs may not get far enough in what they do to actually exercise it19:51
clarkbianw: we pull the ocnfig we are deploying out of project_config so it needs to cogate19:51
clarkbianw: for noop its less important but anything else would need it19:51
nibalizerand on the subject of puppet: https://review.openstack.org/#/c/206779/ adds a hiera directory to system-config and starts using it19:52
clarkb(just noting that as we do the other beaker based testing)19:52
pabelangernibalizer: nice, will be checking that out19:53
*** ashuk has quit IRC19:53
*** shashank_hegde has joined #openstack-meeting19:53
clarkbpabelanger: https://review.openstack.org/#/c/203756/ doesn't pass the f21 test19:53
ianwok, well i'll have to think about it.  i think we could skip those jobs for the bulk of project-config changes that are adding/modifying zuul jobs19:54
pabelangerclarkb: right, I don't know why right now.  I need to check out dib builds to see what happens. Since it should be the same code for production installs19:54
pabelangerclarkb: I won't be gating that until I figure it out19:54
*** ashuk has joined #openstack-meeting19:54
*** cdub has quit IRC19:54
jeblairianw: yeah.  i think it's worth some thought.  there's definitely a relationship there.  we're probably not adequately testing it.  if we can, we should.  but if it's not possible, then yeah, maybe we should drop the jobs.19:55
jeblair#topic Open discussion19:55
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:55
EmilienM1/ could we have reviews on "Add support for backport-potential commit flag" > https://review.openstack.org/#/c/175849/ and 2/ Also "jenkins: implement copy-puppet-logs publisher" (miss +A) > https://review.openstack.org/206693 - thank you19:55
*** ekarlso has quit IRC19:55
*** irenab has quit IRC19:55
zaroGerrit upgrade update, new info in #link https://code.google.com/p/gerrit/issues/detail?id=342419:56
*** armax has quit IRC19:56
pabelangerSo, I know we only have 5mins, but was going to do this on mailing list. Could somebody explain when it is appropiate to make a job (node) reusable? https://github.com/openstack-infra/project-config/blob/master/zuul/openstack_functions.py#L3419:56
clarkbEmilienM: my initial impression of 175849 is the submitter wrote the commit message should just push to the old branch so that conflicts can be handled19:56
zarowas wondering if you guys can take a look and help me determine if we want to increase diff timeout?19:57
*** otter768 has joined #openstack-meeting19:57
jaypipespabelanger: hey, what's the latest status on bringing stackalytics into openstack.org?19:57
clarkbericsson has independently ocnfirmed our jenkins slave plugin bug19:57
*** ekarlso has joined #openstack-meeting19:57
*** Rockyg has joined #openstack-meeting19:58
pabelangerjaypipes: good, I rebased patches today. We're pretty close. I suspect next week I'll have a request up for reviews / approval19:58
jaypipespabelanger: coolio. let me know if you need any assistance from my end.19:58
EmilienMclarkb: don't you think it's a good first iteration?19:58
clarkbEmilienM: I worry its putting too much effort into a nintractable problem19:58
*** Rockyg has quit IRC19:59
ianwpabelanger: i think reusable if it's not running untrusted code?19:59
ianwis any code trusted though...19:59
clarkbits trivial to push the backport if you know you need to push it and it allows you to do the non trivial work of resolving conflicts19:59
*** Rockyg has joined #openstack-meeting19:59
*** haomaiwang has quit IRC20:00
pabelangerianw: so, what if a job sandboxes code into the workspace, which gets deleted after a job runs?  Could that be reusable?20:00
pabelangerianw: EG: not using sudo20:00
EmilienMclarkb: it's just we want to automate it20:00
*** baoli has joined #openstack-meeting20:00
EmilienMclarkb: the "push" part20:00
*** vivek-ebay has quit IRC20:00
jeblairtimes up; maybe finish these in #-infra20:00
clarkbEmilienM: yes and I am saying you cannot automate it20:00
jeblairthanks everyone!20:00
*** haomaiwang has joined #openstack-meeting20:00
jeblair#endmeeting20:00
*** openstack changes topic to " (Meeting topic: third-party)"20:00
openstackMeeting ended Tue Aug  4 20:00:50 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
*** DericHorn-HP has quit IRC20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-04-19.03.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-04-19.03.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-08-04-19.03.log.html20:00
ttxAlrighty20:01
russellbo/20:01
dhellmanno/20:01
* devananda lurks20:01
*** vivek-ebay has joined #openstack-meeting20:01
jeblairo/20:01
*** bswartz has quit IRC20:01
*** baoli has quit IRC20:01
ttxjgriffith, annegentle, lifeless, mordred, flaper87, dtroyer, markmcclain, jaypipes, sdague: around ?20:01
markmcclaino/20:01
sdagueo/20:01
* edleafe also lurks20:01
*** VW__ has joined #openstack-meeting20:01
*** baoli has joined #openstack-meeting20:01
*** otter768 has quit IRC20:01
*** dane_leblanc has joined #openstack-meeting20:01
*** mmmpork has left #openstack-meeting20:02
ttxone more for quorum20:02
*** pabelanger has left #openstack-meeting20:02
ttxjaypipes was here a couple minutes ago20:02
* angdraug lurks, too20:02
* russellb happy he beat the courtesy ping this week20:02
*** bswartz has joined #openstack-meeting20:02
lifelessttx: I'm not sorry, need to finish pacing here20:02
ttx#startmeeting tc20:03
openstackMeeting started Tue Aug  4 20:03:04 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: tc)"20:03
openstackThe meeting name has been set to 'tc'20:03
*** Haneef has quit IRC20:03
*** aukhan has quit IRC20:03
flaper87o/20:03
ttxOur agenda for today:20:03
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:03
*** VW__ has quit IRC20:03
ttx#topic Half-cycle introspection on "things the TC should be working on"20:03
*** openstack changes topic to "Half-cycle introspection on "things the TC should be working on" (Meeting topic: tc)"20:03
jaypipeso/ :)20:03
ttx(Timeboxing this to 30 minutes)20:03
*** aukhan has joined #openstack-meeting20:03
* Rockyg lurks 220:03
ttxSo... we are at about half of Liberty20:03
ttxI wanted us to take a step back from purely processing what's being thrown at us, and think a bit about things we should be working on fixing or improving20:03
*** VW__ has joined #openstack-meeting20:04
* geoffarnold lurks20:04
ttxHalf of us posted eloquent threads to get elected a few months ago, but I don't feel we followed up with actions everywhere20:04
ttxSo... what should we be working on ? And how to make any of it happen in the second half of Liberty ?20:04
ttxPersonally I listed three goals: step out of the way, start addressing real issues, push towards both ends of the scale space20:04
ttxWe did /some/ stepping out of the way by simplifying the project list reviews, delegating tag maintenance, and accepting project teams at earlier stages of development20:05
ttx(other suggestions on further improving on that is welcome)20:05
*** lpetrut has quit IRC20:05
* jaypipes was neither eloquent nor remembers self-assigning any action items20:05
ttxWe created workgroups to start addressing real issues, like the Project Team Guide workgroup to address the loss of common culture.20:05
ttxjaypipes: you're special :)20:05
* devananda recalls saying lots of aspiration things for others to do :)20:05
*** VW_ has quit IRC20:05
ttxI'd say we should create more, hopefully as a result of this discussion20:05
russellbi'd like to be further along with tags, but i'm just as capable as anyone helping with that, so i hope to be more active with the next tags WG for the 2nd half20:05
*** vivek-ebay has quit IRC20:05
sdaguethe thing I'd really like to figure out how to make progress on is service catalog standardization20:06
ttxAbout pushing towards both ends of the scale space, I think defining the compute starter kit goes a long way to address the small end.20:06
annegentlesdague: +120:06
devanandasdague: ++20:06
jaypipessdague: ++20:06
sdaguewe had a CP session at summit, but it sort of petered out20:06
dhellmannwe have several cross-project specs that seem to be languishing20:06
ttx#info we should figure out how to make progress on is service catalog standardization20:06
sdagueand there is a ton of weird code all the projects carry around because they barely acknowledge SC exists20:06
annegentleare cross-project specs the "start addressing real issues" area?20:06
ttxdhellmann: yes, we don't seem to have a good dynamic on that20:06
*** VW__ has quit IRC20:06
*** dprince has quit IRC20:07
annegentleor is a better example "help glance land code?" or?20:07
ttxannegentle: not necessarily. For example to address culture issues we set up a workgroup to write the project team guide20:07
*** Shrews has left #openstack-meeting20:07
*** VW_ has joined #openstack-meeting20:07
ttxannegentle: yes, that would be a good example20:07
annegentlettx: ok, yep. And we set up communications working group.20:07
sdagueon cross project specs, honestly, I think we should tell folks to only come forward with one if they are running into resistance at the project level and need TC blessing on a thing20:07
sdagueI think people are going to cp-spec first and just making a new bottleneck20:08
annegentlesdague: I think they're useful for agreement/details, but yeah could be just a new place to argue?20:08
ttxsdague: tend to agree on that, but people don't discuss cross-project until we raise it at the cross-project meeting, and the spec was a conduit to do that20:08
sdaguethe whole cors thing probably didn't need to be a cp-spec, for instance.20:08
*** ebalduf has joined #openstack-meeting20:08
dhellmannsdague: well, in at least a couple of cases the projects pushed back asking for broader consensus20:08
* Rockyg is going to finish next draft of Error Codes at Ops midcyle (have a working group session)20:08
sdaguedhellmann: ok20:08
ttxif people raised more random topics for the cross-project meetign we wxouldn't need them as much20:08
dhellmannthe request-id thing, for example20:08
markmcclainttx: agreed20:09
*** esker has quit IRC20:09
sdaguecan we take them to the ML instead? because I feel like cp-specs are mostly a piece of gerrit I forget exists, because there is so much gerrit20:09
sdaguettx: yeh, or that20:09
annegentlesdague: there's soo much ML too though.20:09
russellbannegentle: +1 ..20:09
*** lpetrut has joined #openstack-meeting20:10
dhellmannsdague: that has been tried, too, and didn't really help either.20:10
*** Piet has joined #openstack-meeting20:10
ttxsdague: Usually the cross-project meeting discussion is the escalation step when the thread goes nowhere20:10
ttxbut nowadays people give up on the thread and don't push for cross-project discussion20:10
sdagueok, well, I guess that's a thing. How do we do actual cross project things?20:11
ttxat least when they write a spec, the meeting chair will give the idea some cross-project air time. It's more of a workaround than a solution20:11
*** esker has joined #openstack-meeting20:11
*** esker has quit IRC20:11
*** esker has joined #openstack-meeting20:11
markmcclain+20:12
ttxI had my hands full with the project team guide and next-tags workgroups, but I also wanted to brainstorm on how to make cross-project specs/meeting/discussions more efficient20:12
annegentlesdague: for service catalog, the teams and people are willing to pick up tasks, it's the coordinating/timing that's tougher20:12
*** bmace has joined #openstack-meeting20:12
markmcclainyeah cross project communication was one of the things I wanted to work on20:12
*** iurygregory has left #openstack-meeting20:12
dhellmannttx, markmcclain : ++20:13
*** roxanaghe_ has quit IRC20:13
ttx#info cross project communication (specs/meeting/discussions) is one of the things we should try to work on20:13
*** mrmartin has quit IRC20:13
sdagueannegentle: well, it doesn't feel like there is much of a game plan. I guess that's what it's missing, a point person.20:13
annegentletask assignment, how does that work on cross project plans?20:13
*** neelashah has joined #openstack-meeting20:13
ttxI don't have a magic bullet there, been iterating on various formats for the cross project meeting, and nothing was really successful20:14
annegentlesdague: yeah, agreed. Sadly the etherpad going down was sort of to blame for not having more detail tasks lists out of the summit planning.20:14
ttxAt least with the chair rotation I guess the project became more visible20:14
ttxs/project/issue/20:14
dhellmannyeah, I'm not convinced the meeting is going to solve that problem.20:14
sdaguedhellmann: agreed20:14
dhellmannas annegentle and sdague were saying, we need some sort of ownership structure for these things20:15
ttxdhellmann, sdague: I stil want to have a forum for projects to agree with each other without needing to call in the TC20:15
flaper87sorry, I had to step out a bit20:15
* flaper87 quickly reads the backlog20:15
sdagueso, I'm not convinced there is a general solution. But maybe if we pick specific cross project things we want done, we could try to come up with a working pattern in the small based on what works20:15
dhellmannttx: absolutely, I'm not saying get rid of it, just that it's not enough on its own20:15
sdagueservice catalog might be a good thing to use as a unit test20:15
dhellmannsdague: right, maybe if we pick one or two specs early in mitaka and focus on those we can see how we can get them done20:15
ttxi.e. if the ML discussion goes nowhere, what option do we have ? Waiting for the next cross-project track at the design summit is not really a fast way20:15
flaper87With full honesty, I haven't been able to attend cp meetings. Time-wise, it's not a good fit for me20:15
sdaguedhellmann: yeh20:15
flaper87And I feel bad about it but I get why it's that way20:16
dhellmannttx: we usually take ML silence as consent, no? the problem is the spec author isn't getting any sign-off from the TC, so they can't proceed20:16
ttxflaper87: and I'l admit that since I don't chair all of them anymore, I don't follow them as religiously as before, due to same timing issue20:16
ttxdhellmann: sure, if ML is silent it's an easy call20:16
ttxdhellmann: it's when the discussion doesn't reach consensus that we have a problem20:17
ttxTechnical discussions are like lasagna. You need to layer ML threads and IRC discussions to reach consensus20:18
*** vinkman has joined #openstack-meeting20:18
Rockygttx: ooh, nice analogy!20:18
* flaper87 wants to bring the cinder HA thread as an example20:18
ttxflaper87: I was hoping you would bring lasagna instead20:19
*** temujin__ has joined #openstack-meeting20:19
flaper87ttx: I can do that20:19
flaper87:D20:19
dhellmannif we look at the open specs:20:19
dhellmann "Uniform public methods for clietns" looks like we have consensus not to do this;20:19
*** temujin__ has quit IRC20:19
*** temujin_ has quit IRC20:19
dhellmann"No global admin" looks like something that isn't a code change so I'm not sure why that's a spec20:19
dhellmann"Return request ID to caller" has *finally* reached consensus, thanks to lifeless pushing on it20:19
annegentlenice work lifeless20:20
*** oanufriev has joined #openstack-meeting20:20
dhellmann"resource retrieving improvement: support change-since filter" has very little input20:20
*** singleth_ has joined #openstack-meeting20:20
russellbdhellmann: that one doesn't seem like a good cp spec20:20
sdaguedhellmann: that last one also has api-wg thing bumping around on it which is confusing20:20
dhellmann"Adds starting discussion spec for Service Catalog updates" has some approval, but some changes requested20:20
dhellmann"Replace eventlet + monkey-patching with ??" has languished20:20
*** dims_ has joined #openstack-meeting20:21
dhellmannwithout clear consensus or work20:21
ttxAnother set of problems is when project teams go wrong in their silo and need an external intervention to be fixed20:21
dhellmann"Add asynchronous user event support to OpenStack" looks like a new project someone should start and not a cp spec20:21
ttxWe are staffing up in my team at the Foundation and we hope to be able to spend time diving into specific project teams to assess their current state and suggest solutions20:21
dhellmann"OpenStack wide Error Codes for Log Messages" needs author input, which Rockyg has said she's going to do20:21
*** oanufriev1 has joined #openstack-meeting20:22
* Rockyg yup20:22
dhellmann"Add OSprofiler spec" has mostly negative feedback on the spec, but I remember a lot of positive support for the idea from the summit20:22
*** dims has quit IRC20:22
*** oanufriev1 has left #openstack-meeting20:22
ttxOK, so I #infoed two areas we could focus on during the second half20:23
dhellmann"Cross-Project Policies" might be replaced by something newer20:23
sdagueI suspect that who showed up for osprofiler session was somewhat self selecting, which would explain that split20:23
ttxAny other problems OpenStack is facing right now that we should be helping to fix ?20:23
*** singlethink has quit IRC20:23
ttxsdague: yeah, that would be my take20:23
dhellmannsdague: it wasn't a session, it was conversations throughout the week20:23
dhellmannfolks other than boris-42 seemed to think *something* like that was a good idea, if not exactly what he was proposing20:24
annegentlehonestly, for me, it's a couple of things: 1. sprawl causing difficulty figuring out where to focus, and 2. events like mid-cycles and 2 summits a year causing interruptions20:24
sdagueso, I do get that people seem to not want stuff on the mailing list - but I feel like one of the reasons the cross project efforts get gummed up is we don't have a project wide discussion forum any more in any format20:24
sdagueso there is no where to synchronize20:24
russellbno, i still think ML is best20:25
russellbit's the most inclusive place to discuss20:25
annegentleso I have this gut feeling that the midcycles are valuable for teams but offset from summits, where cross-project discussions happen.20:25
dhellmann"most inclusive"?20:25
ttxsdague: should definitely be discussed on ML first and a spec written only of necessary20:25
russellbeasiest to participate20:25
russellbcompared to irc meetings, where TZ is a problem20:25
ttxif*20:25
annegentleasynchronous is easier to participate in20:25
flaper87The problem with the ML is that discussions *always* digress20:26
flaper87keeping them on track is really hard20:26
ttxflaper87: maybe we should push back on digressions20:26
sdagueflaper87: so, can we fix that problem, calling people out for going off topic?20:26
ttxlike off-topic, start your own thread20:26
clarkbthere are also too many of them to follow at one time20:26
jeblairyes, it is hard, because everyone wants to have their say20:26
*** xingchao has quit IRC20:26
clarkbits easier to be focused in a thing that looks like a meeting20:26
flaper87sdague: I believe we do already but we're too many :P20:26
jeblairand yeah, i think the only solution to that is to try to change the culture and push on digressions20:26
Rockygclarkb: ++20:26
flaper87I don't see that issue as a blocker for using ML20:26
flaper87but it's a real issue20:27
jeblairit's a lot of work20:27
flaper87it is20:27
dhellmannso are we suggesting that we not use the specs repo any more and push all of these discussions back to the list?20:27
annegentleno no I think specs repo is super valuable20:27
ttxdhellmann: I think we are suggesting people interested in discussing that should have a longer meetign about it20:28
sdaguedhellmann: honestly, I would suggest that20:28
annegentlettx: how do you ensure an outcome, have TC facilitators?20:28
russellbi think specs are valuable for cases where clear project-wide consensus needs to be clearly documented20:28
annegentleYou need a decision maker otherwise people just flail for a while.20:28
flaper87I would prefer doing both. We need a place where the final consensus gets written down and reviewed20:28
annegentlerussellb: agreed20:28
russellbi need to be better at looking at them though ...20:28
ttxannegentle: we coudl reuse the workgroup foirmat and have some cross-project comm workgroup20:28
russellbsounds like that applies to several people20:28
sdaguerussellb: right, but it's much easier to sketch on the list or in an etherpad20:29
russellbyep20:29
flaper87but we shouldn't be using the CP repo to decided whether we should all go and drink tea together in tokyo20:29
dhellmannttx: would it be better to have a wg per initiative?20:29
RockygI think what ttx means with *f* a spec is needed is that once the discussion brings out the key issues/approaches, if a spec is still needed for action, write it, but it will start more focused and be easier to get attention on it to complete its process20:29
sdaguettx: so I think the issue is that there are meeting people, and there are ML people.20:29
*** vivek-ebay has joined #openstack-meeting20:29
annegentlesdague: stylistic preferences, yeah...20:30
sdaguehonestly, if we are talking about something that requires real feedback, I'm not going to be able to do much of that in an interactive meeting. It needs digestion20:30
ttxI do both20:30
ttx(lasagna)20:30
annegentlesdague: but again points to a need for "final" decision making20:30
annegentlearbitration, whatever it is.20:30
*** gampel has quit IRC20:30
ttxOK, time is mostly up, what's the next step on that ? Workgroup meeting ? ML thread ?20:30
flaper87I get there are meeting people but, as much as I hate emails, we need emails. We can't pretend folks interested are going to chase on IRC logs to know what's happening20:31
sdagueannegentle: sure, if concensus doesn't emerge. But, honestly, the reason SC is stalled is not because it's controversial20:31
* flaper87 sent a similar email referencing Glance a couple of weeks ago20:31
ttxI want to make sure we discuss it again before mid-Mitaka20:31
flaper87ML brings more attention and it's for async communications20:31
annegentlesdague: yeah, service catalog is more about chasing the final outcomes20:31
sdagueannegentle: honestly, I don't know it's even that :) but maybe if we identify a point person it would be helpful.20:32
dhellmannttx: ideally, the TC would identify some important initiatives and help push, if not drive, them, in whatever forum. I'm not convinced the forum is the problem, per se.20:32
annegentlesdague: yeah, I feel like it should have been me, but I haven't chase20:33
annegentlechased20:33
*** jjmb has joined #openstack-meeting20:33
ttxso.. keep using ML+Specs and cross-project meetings the way we currently do ?20:33
dhellmannI think it's a much bigger issue that projects look at someone trying to do something across the whole community and say, "I'll wait for some other folks to sign on so I know that's something real I have to pay attention to."20:33
ttxanyway, time is up. If someone has a suggestion for change, I guess step 1 is a ML thread20:33
sdagueso, vishy said a great thing in Atlanta, which is that anything that needs to get done needs 1 person in point20:33
flaper87dhellmann: ++20:33
annegentlettx: I feel like there's something else about midcycles and inperson meetings20:33
sdaguebecause a group tends to assume someone else is doing it20:34
annegentlesdague: ayup20:34
Rockygdhellmann, ++20:34
dhellmannsdague: sometimes the person with the idea isn't the right person to make that happen and needs help, and I think that's where we're failing right now20:34
*** oanufriev has quit IRC20:34
sdagueso I think basically anything we sanction out of the TC as important should have step 0, determine point person20:34
annegentlesuch as, if you wanted to get attention for service catalog across projects you'd have to go to a half dozen midcycles20:34
dhellmannsdague: definitely20:34
sdagueannegentle: honestly, I don't think so20:34
annegentlesdague: ok, whew :)20:34
ttxok, moving on20:35
annegentletimebox!20:35
russellbneeding a point person applies to just about anything anywhere20:35
ttxwe have a few items to cover20:35
ttx#topic Adds Debian & derivatives packaging to OpenStack20:35
*** openstack changes topic to "Adds Debian & derivatives packaging to OpenStack (Meeting topic: tc)"20:35
ttx#link https://review.openstack.org/18518720:35
russellbi had a mission statement concern, but generally +120:35
ttxThis was recently updated20:35
russellbnot sure how baked this is, but whatever, the rpm one wasn't super baked either20:36
*** banix has quit IRC20:36
*** amakarov is now known as amakarov_away20:36
ttxthat mission statement concern is valid20:36
russellbmission statement seems to encode a gating strategy that i'm not sure i agree with20:37
sdaguerussellb: yeh, agree20:37
ttxquestion is, do we require than it's changed to merge it, or should we just propose an adjustment20:37
annegentlerussellb: ah good point20:37
ttxas a subsequent change20:37
sdagueI'm fine if the team wants to get there, but I don't think the TC should stamp that as approved direction20:37
russellbi'd rather it be changed before approving20:37
russellbpersonally20:37
ttxthat's fair20:37
jeblairrussellb, sdague: agreed20:37
jaypipeszigo: here?20:37
jeblairwould +1 without the long-term goal20:38
jaypipesrussellb: yep, agreed. plus I think there's a typo in there.20:38
ttxLet's move on and come back to this if zigo appears20:38
jaypipesrussellb: I don't think deb-mural is the right deliverable name ;)20:38
russellbheh20:38
ttxmurallo20:38
jeblairjaypipes READ the patch!20:38
russellbjeblair: woah20:38
russellbi read the top part :)20:38
ttx#topic Kolla application for Big Tent20:39
*** openstack changes topic to "Kolla application for Big Tent (Meeting topic: tc)"20:39
ttx#link https://review.openstack.org/20678920:39
*** oanufriev has joined #openstack-meeting20:39
ttxThis one looks pretty straightforward, especially with all the other packaging initiatives in20:39
*** banix has joined #openstack-meeting20:39
russellbi've followed the OSAD concerns20:39
jaypipesjeblair: ?20:39
russellbbut i'm really not personally too concerned with overlap at this level20:39
russellbjaypipes: past tense20:39
russellbjaypipes: joking that you actually read it20:40
jaypipesahhh20:40
jeblairjaypipes: oh wow sorry about that :)20:40
jaypipessorry, missed that :)20:40
*** ivasev has quit IRC20:40
jeblairstupid enlish20:40
russellbheh yeah, alternative reading was very different :)20:40
*** oanufriev has left #openstack-meeting20:40
ttxmainconcern raised is about duplication of scope with the OpenStackAnsible project20:40
ttxLooks like we need to investigate that late conern a bit deeper20:41
sdakettx: it is true they are similar problems (deployment) but take radically different approaches to achieving the goal20:41
jaypipesttx: yes, though I raised that concern on patch 1, and sdake seems to have answered the question. the answer might not be amenable to kevin carter and justin shepherd, but it is an answer.20:41
patchbotjaypipes: https://review.openstack.org/#/c/1/20:41
russellbthis would not be the first deployment overlap20:41
jaypipesty patchbot.20:42
russellbmeh20:42
dhellmannsdague: can you summarize the differences?20:42
sdakeyes I have a list of 11 items if you have time dhellmann :)20:42
dhellmannsdague: well, is it written down somewhere I just might not have seen, yet? :-)20:42
russellbsdake: i think it'd be good to put it on the review for the record20:42
sdakeKolla manages the container configuration outside the container, whereas OSAD manages the configuration by connecting to the SSH process in a container to change the configuration.20:42
flaper87russellb: ++20:42
sdakerussellb yes I asked in the review if the tc would like to see it20:42
sdakecan add er in20:42
russellbsdake: yes i'd like to see it :)20:42
annegentlesdake: yes, please20:43
*** yolanda has left #openstack-meeting20:43
zanebI personally don't care if it's a duplicate of the openstack-ansible deployment process, as long as the containerisation part is not tightly coupled to it20:43
sdakewill do20:43
dhellmann++20:43
ttxOK, let's wait for that and we'll gather votes later20:43
jaypipeszaneb: did you see my last comment on the review?20:43
sdagueyeh, for once, I'm 100% in agreement with zaneb  :)20:43
ttxAlthough it already has 7 votes20:43
sdakethe containerization part is not tighly coupled20:43
zanebsdague: :D20:43
russellbttx: yeah, but i think we owe the concern a bit more air time20:44
sdakemy concern with separate repos is it would make dev harder20:44
sdagueI feel like we specifically opened up for a lot of deployement solutions20:44
sdakesince they are loosly coupled20:44
dhellmannyeah, I'm not concerned about overlap, but I would like to understand the issue more20:44
sdagueand ansible doesn't get a global lock on a space there20:44
ttxTo me it's an openstack team. The fact that its container approach is not the same as OSAD is similar to DEB and RPM not being the same.20:44
jeblairthis seems to be a good "don't pick winners" thing20:44
jaypipessdake: yeah, understood. it was more a brainstorming question than anything else..20:44
dhellmannyeah20:44
ttxjeblair: yes20:44
annegentleit's a team definition to me as well20:45
jaypipessdague: since puppet and the chef cookbooks follow a separate repo pattern, IIRC.20:45
sdakejaypipes I will answer in the review for permanent record ;)20:45
ttxI'm fine with approving now. I just want to give everyone a chance to retract their vote based on recent developments20:45
jaypipessdague: np :)20:45
*** elmiko has joined #openstack-meeting20:45
russellbi don't plan to retract20:45
*** emagana has quit IRC20:45
ttxI don't either20:45
ttxif everyone is fine with their vote there, let's just approve it now20:45
annegentleme neither20:45
*** dmorita has quit IRC20:46
* flaper87 neither20:46
russellbto reiterate, i'm *much* more concerned about overlap as we get closer to the core infrastructure, say, something in the compute starter kit20:46
dhellmannwfm, maybe sdake can still post that link though20:46
ttxrussellb: same here20:46
sdakedhellmann I have to actions - answer jaypipes q and your q20:46
sdaketo/two20:46
russellblet the deployment approach flowers bloom20:46
ttxdhellmann: agreed, can be done async20:46
sdaguerussellb: ++20:46
dhellmannsdake: great, thanks20:46
*** dmorita has joined #openstack-meeting20:46
jaypipesrussellb: I'm predominantly (only?) concerned about overlap on RESTful API functionality.20:46
russellbjaypipes: *nods* another good way to look at it20:47
sdagueI'm actually kind of disappointed in the ansible team for trying to throw that block in there20:47
* ttx moves on to next topic while we wait for the info to be posted20:47
russellbthough i'm probably more concerned about some APIs than others20:47
ttx#topic ATC: Add Cathy Zhang as Neutron ATC20:47
*** openstack changes topic to "ATC: Add Cathy Zhang as Neutron ATC (Meeting topic: tc)"20:47
russellbanyway20:47
ttx#link https://review.openstack.org/20713620:47
ttxI think this is straightforward, but we still require those to be voted on by the TC20:47
ttxLast time I looked it was still missing a couple of votes20:47
russellbthis one seems harmless, though likely unnecessary20:47
jaypipesrussellb: http://foaas.com?20:47
jaypipes:P20:47
ttxactually missing 320:47
russellbjaypipes: the best API there is20:47
dhellmannthere was some question of whether it was needed, but I think we should approve it anyway20:47
jaypipeshehe20:47
ttxvote on it and I'll approve it. Object now if you disagree20:47
*** echoingumesh has joined #openstack-meeting20:48
ttx#topic Feature deprecation / config deprecation policy tags20:48
*** openstack changes topic to "Feature deprecation / config deprecation policy tags (Meeting topic: tc)"20:48
*** emagana has joined #openstack-meeting20:48
sdaguettx: right, so she's author on - https://review.openstack.org/#/c/192933/20:48
ttx#undo20:48
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0xa3b8fd0>20:48
sdagueso I guess I'm confused why extra atc is needed20:48
ttxsdague:oh, then we can abandon it20:48
*** dmorita_ has joined #openstack-meeting20:48
ttxsdague: ah hm. Co-authors still need to be added20:48
sdaguehttps://review.openstack.org/207136 references the reason for her being atc was working on that spec20:48
sdagueshe's not the co-author, she's the author20:49
russellbtrue20:49
russellbmaybe some previous rev she was co-author?20:49
sdaguethat's what git will show20:49
russellbthere's 2 people that keep switching ownership of patches in that repo20:49
dhellmannwhy did she approve her own spec?20:49
ttxHmm. do we look into authors or owners...20:49
dhellmannis that the same cathy?20:49
annegentlearen't spec patches showing up as ATC work?20:49
*** henrynash has joined #openstack-meeting20:49
russellbdhellmann: there was a thread about that, yes20:49
*** temujin_ has joined #openstack-meeting20:50
russellbsome people upset about it, but i think it's been discussed and addressed20:50
*** kzaitsev_mb has joined #openstack-meeting20:50
mesteryrussellb dhellmann: Ack on that, we scolded her and she apologized. :)20:50
*** NobodyCam has joined #openstack-meeting20:50
jeblairttx: i believe owner20:50
markmcclainright should be as settled as it will be for now20:50
jeblairfungi: ^?20:50
dhellmannmestery, russellb : ok20:50
ttxif we look at owners then probably should still be added manually20:51
ttxand it doesn't hurt anyway20:51
*** dmorita has quit IRC20:51
sdaguejeblair: oh, it does gerrit owner query, not a git query?20:51
russellbright, not git20:51
russellbchecks gerrit db20:51
sdagueoh, never mind then20:51
*** moha_hunt has joined #openstack-meeting20:51
ttx#topic Feature deprecation / config deprecation policy tags20:51
*** openstack changes topic to "Feature deprecation / config deprecation policy tags (Meeting topic: tc)"20:51
ttxThose come from the "next tags" workgroup. The first one is about feature/API deprecation policies:20:51
ttx#link https://review.openstack.org/20746720:51
ttxassert:features-always-supported asserts that you won't deprecate anything ever20:51
ttxassert:features-follow-deprecation asserts that you follow a predictable, reasonable deprecation policy20:52
ttxThe latter is designed to match the current "default" deprecation policy we had for integrated projects in the past20:52
ttxI may have gotten the timeline wrong. If a feature is marked deprecated during the L cycle, when at the very minimum should we allowed to remove it under that policy ?20:52
ttxstart of the M cycle, or start of the N cycle ?20:52
dhellmannis the former provided for completeness? it doesn't seem very realistic.20:52
russellbdoes any project follow "always-supported" ?20:52
ttxrussellb: good question. I heard swift claim it20:52
russellbbold claim20:52
annegentleat the release of the N deliverable I believe?20:52
annegentle(that is, it's a year I thought)20:53
ttxmaybe we could replace that with a longer deprecation policy20:53
*** shashank_hegde has quit IRC20:53
russellbseems like "always-supported" is just "follow-deprecation" without any plan to exercise the deprecation flow20:53
dhellmannannegentle: "at" meaning "in" or "after"? :-)20:53
sdagueannegentle: most projects have been doing single cycle deprecation20:53
* jaypipes personally needs a bit more time to think on these. I like the idea behind them. just want to Gandalf-ponder on them a bit.20:53
jeblairstepping way back -- is this valuable as a choice?20:53
flaper87jaypipes: ++20:53
jeblairwould it be better to establish a project-wide deprecation policy?20:53
annegentledhellmann: when cloud consumers could possibly use the API capability20:54
ttxjeblair: some projects will prefer not to assert any deprecation policy and move fast20:54
annegentle"in" the released release :)20:54
ttxjeblair: but yes, that could be an option20:54
*** bmace has left #openstack-meeting20:54
dhellmannannegentle: so something added in M could be removed in N?20:54
annegentledhellmann: nope!20:54
ttxplease comment on the review, no time to solve it today20:54
*** Leonr has quit IRC20:54
ttxThe other review up is about config file options deprecation:20:54
sdagueso, honestly, I'm not sure this is going to work as a tag20:54
ttx#link https://review.openstack.org/20758420:54
annegentlesomething added in M, released in M, could not be removed until the release of O20:54
sdaguebecause there are a lot of specific situations20:54
jeblairttx: k, thanks.  even this brief discussion was helpful.  :)20:55
annegentlebut maybe I'm too conservative?20:55
ttx(not sure we need to separate config file options from user-visible features/APIs)20:55
dhellmannannegentle: we need to come up with a clear way to say that :-)20:55
sdagueand it feels like a guidance document might be better20:55
annegentledhellmann: ayup20:55
russellbttx: i think it's valuable, REST API changes are a bigger deal than config file stuff IMO20:55
ttxrussellb: ok20:55
annegentleI have to head out, sorry, comms ideas in flaper87's capable hands20:55
annegentlerussellb: yeah20:55
*** tpatil has joined #openstack-meeting20:55
russellbREST API changes the most important to establish clear policy on20:55
dhellmannsdague: isn't the tag a guidance document, with the application of the tag indicating the projects that are following the guidance?20:56
*** jmckind has joined #openstack-meeting20:56
ttxplease follow-up on review20:56
ttxOK, skipping workgroup reports for today and jumping to open discussion20:56
ttx#topic Open discussion20:56
sdaguedhellmann: maybe, honestly, for deprecation I'd expect a lot more guidance20:56
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:56
*** shashank_hegde has joined #openstack-meeting20:56
ttxAbout topic tagging for governance reviews, I posted a question at:20:56
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2015-July/001005.html20:56
zanebsdague: but there is a point at which a project moves from 'we will break everything' to 'we will try to maintain orderly deprecation'. usually it's 1.0. but we need _some_ way of calling that out20:56
ttxAny preference ?20:56
ttxzaneb: ++20:57
ttxAlso.. next week I'll be coming back from vacation and won't be able to prepare for the meeting.20:57
jeblairttx: i like your inverted suggestion20:57
dhellmannsdague: sure, maybe suggest some details to be added20:57
ttxDoes anyone want to pick it up and chair it, or shall we just skip for one week ?20:57
russellbi think i may be traveling next week20:57
flaper87There'll be a tc post this week20:58
ttxI prefer to skip since I won't be around to babysit anyone to chair, but if someone wants it, they can run with it :)20:58
*** cbouch has quit IRC20:58
sdaguezaneb: well from my experience from the tempest side, most of the projects don't deprecate in an orderly manner20:58
flaper87There are enough topics for a new one20:58
ttxOK, Cathy's extra atc review has enough votes on it, I'll approve it now20:58
*** Leon has joined #openstack-meeting20:59
ttxWill approve the Kolla one as soon as Steve pushes his 11 point explanation20:59
dhellmannttx: I'd be ok with skipping if it doesn't seem like we have any pressing business.20:59
zanebsdague: heh, ok :) that's another issue to tackle I guess20:59
*** Leon is now known as Guest3909120:59
fungioops, sorry, stepped away... yes, it's gerrit change owner that we use for elections and summit passes20:59
flaper87sdague: https://www.youtube.com/watch?v=EYKdmo9Rg2s :D20:59
sdakettx still typing :)20:59
ttxdhellmann: no pressing things. Mostly tags that can be reviewed on gerrit20:59
russellbthanks sdague20:59
*** Leonr has joined #openstack-meeting20:59
russellberr sdake20:59
ttxand I won't be making new revisions this week20:59
*** haomaiwang has quit IRC21:00
*** gyee has joined #openstack-meeting21:00
sdakettx i was incorrect it is 9 points21:00
ttxok, let's tentatively skip it. Feel free to conspire into holding it while I'm away21:00
russellbsdake: 9?! that changes everything21:00
ttxand approved.21:00
*** haomaiwang has joined #openstack-meeting21:00
sdakettx sorry 10 :)21:01
ttxAlright, have a great week.21:01
ttx#endmeeting21:01
*** openstack changes topic to " (Meeting topic: third-party)"21:01
openstackMeeting ended Tue Aug  4 21:01:12 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
russellbsdake: you better stretch it to 1121:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-08-04-20.03.html21:01
*** esker has quit IRC21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-08-04-20.03.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-08-04-20.03.log.html21:01
ttxmarkmcclain: floor is yours21:01
*** irenab has joined #openstack-meeting21:01
markmcclaincourtesy ping PTLs: adrian_otto boris-42 bswartz david-lyle devananda dims dtroyer emilienm flaper87 gordc hyakuhei isviridov21:01
markmcclaincourtesy ping PTLs: j^2 jeblair johnthetubaguy kiall loquacities mestery morganfainberg mtreinish nikhil_k notmyname rakhmerov21:01
*** ajmiller_ has joined #openstack-meeting21:01
notmynamehere21:01
markmcclaincourtesy ping PTLs: redrobot SergeyLukjanov slagle SlickNik smelikyan stevebaker thingee thinrichs ttx21:01
markmcclain#startmeeting crossproject21:01
openstackMeeting started Tue Aug  4 21:01:49 2015 UTC and is due to finish in 60 minutes.  The chair is markmcclain. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: crossproject)"21:01
morganfainbergo/21:01
openstackThe meeting name has been set to 'crossproject'21:01
mtreinisho/21:01
stevebaker\o21:01
johnthetubaguyo/21:01
*** angdraug has left #openstack-meeting21:01
elmikoo/21:01
* morganfainberg lurks mostly though.21:02
jokke_o/21:02
flaper87morganfainberg: :P21:02
*** shashank_hegde has quit IRC21:02
bknudsonhi21:02
markmcclain#link https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting21:02
tpatilHi21:02
NobodyCamo/21:02
mtreinishmorganfainberg: that's all I normally do too :)21:02
*** neelashah has quit IRC21:02
markmcclainLight agenda for this week21:02
markmcclain#info Meeting chairs needed for next week (August 11th) and three remaining open21:02
markmcclain dates.21:02
* Rockyg is still lurking (mostly)21:02
*** irenab has quit IRC21:02
*** noslzzp has quit IRC21:02
* edleafe is still lurking too21:03
* geoffarnold ditto21:03
* jokke_ will look the dates21:03
ttxI can't take it next week21:03
markmcclainanyone available for next week?21:03
dhellmanno/21:03
* bknudson lurks21:03
*** irenab has joined #openstack-meeting21:03
*** lblanchard has quit IRC21:03
*** noslzzp has joined #openstack-meeting21:03
*** ajmiller has quit IRC21:03
mesteryo/21:03
*** nadya has quit IRC21:03
jokke_dhellmann: seems to have just volunteered ;)21:03
*** ajmiller has joined #openstack-meeting21:03
elmikohehe21:04
edleafejokke_: +1!21:04
*** Guest39091 has quit IRC21:04
dhellmannjokke_: no, no, no21:04
jokke_:P21:04
edleafedhellmann: aw, don't be shy!21:04
mesteryI can do it next week markmcclain21:04
markmcclainmestery: thanks!21:04
*** raildo has quit IRC21:04
mesterymarkmcclain: yw :)21:04
*** baoli has quit IRC21:05
Rockygdhellmann, you dodged a bullet!21:05
markmcclainhaha... moving on21:05
ttxthat one was close21:05
markmcclain#topic Horizontal Team Announcements21:05
*** openstack changes topic to "Horizontal Team Announcements (Meeting topic: crossproject)"21:05
ttxOn the release management side, not a lot of things this week21:05
*** clayg has left #openstack-meeting21:05
ttxWe've been starting to discuss how to actually implement continuous releasing of stable point releases, in two -dev threads:21:05
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/071188.html21:05
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/071189.html21:06
dhellmannedleafe: I've had my turn.21:06
ttxChime on those if you have an opinion on the topic21:06
*** ajmiller__ has joined #openstack-meeting21:06
*** ajmiller_ has quit IRC21:06
ttxtaking a week off starting now so don't expect me to follow those threads closely!21:06
fungiyes, i worry we don't ever get much input from downstream package maintainers and operators/deployers on topics like this until we enact them21:06
*** Nikolay_St has joined #openstack-meeting21:07
fungiand then end up with a small-scale revolt on our hands because we changed something they depended on in their workflow21:07
Rockygmaybe post contents or summary to the operator's list with a request to discuss?21:07
*** david-lyle has joined #openstack-meeting21:07
*** bapalm_ has quit IRC21:07
*** jasondotstar|afk is now known as jasondotstar21:07
*** ajmiller has quit IRC21:07
fungii'd love to just stop having stable point releases at all in liberty and beyond, which was the original proposal, but what little feedback we got from downstream consumers was that they didn't want to lose whatever nonexistent signaling they actually thought they were getting from those21:08
jokke_we should get shout of discussions like these advertised on the every Friday spam ;)21:08
jokke_fungi: ++21:08
fungijokke_: yep, i passed those threads along to the person writing the weekly newletter earlier today21:08
jokke_gr821:08
fungiso that might help raise visibility some21:09
*** aysyd has quit IRC21:09
edleafettx: enjoy!21:09
*** vinkman has left #openstack-meeting21:09
*** gyee has quit IRC21:09
markmcclainAny other horizontal announcements?21:10
johnthetubaguyttx: I quite like that increment on every commit, its simple21:10
*** ajmiller__ has quit IRC21:11
Rockygjohnthetubaguy, ++21:11
jokke_johnthetubaguy: and easily automated21:11
ttxclarkb was arguing it would pollute the ref space21:12
fungi(i don't know about "easily")21:12
*** armax has joined #openstack-meeting21:12
johnthetubaguyalso agreed with fungi about the need to get the package maintainers involved21:12
jokke_fungi: well easier than the other models21:12
fungimostly just don't want to waste time implementing something complex they don't need/won't use anyway21:12
johnthetubaguyhmm, clarkb has a point, maybe I am not sure about the tag for each commit, if that would work well enough without that (shrugs)21:13
bknudsonit is kind of strange to have a tag on every commit21:13
morganfainbergisn't a commit... effectively a tag?21:13
*** kurtmartin is now known as kmartin21:13
*** irenab has quit IRC21:13
jokke_the good point pro that in the ml discussion was that it's easy to find out if you have the fix for X which is A.B.C included C+7, yes it is21:13
* morganfainberg doesn't really have a horse in this race but things it's silly to tag every commit... but ... meh?21:14
jokke_morganfainberg: it's not easy for human (nor computer) to tell by commit id alone if it was before or after another random commit id21:14
morganfainbergthinks*21:14
fungimorganfainberg: commits don't imply a sequence, nut anyway these are points better made on th ml21:15
*** gyee has joined #openstack-meeting21:15
ttxindeed. Follow up on ML if you care. Next topic!21:15
fungiwhere i also type gooder21:15
*** temujin_ has quit IRC21:15
johnthetubaguyyeah, to the ML on this one21:15
markmcclaincool.. moving on21:16
markmcclain#topic Return request ID to caller21:16
markmcclain#link https://review.openstack.org/#/c/156508/21:16
*** openstack changes topic to "Return request ID to caller (Meeting topic: crossproject)"21:16
tpatilI want to discuss about 3 review comments given by Brant on the specs21:16
tpatilFirst concern: Every method should return an object which contains request_id attribute, so that it’s consistent. This also applies to Tuple return type21:16
*** HenryG_ is now known as HenryG21:17
tpatilIMO, we cannot change Tuple response as it would affect Openstack services. Tuple contains ‘X-Openstack-Request-Id’ in the response header of Response object. So I don’t think there is a need to add request_id attribute here. But I agree it’s not consistent with other types though21:17
*** irenab has joined #openstack-meeting21:17
tpatilWe are going to add a new method ‘get_request_id” in client which would return request_id (String) depending on the type of the response to the caller21:17
tpatilAll logic to interpret different response type will be contained in this new method so user don’t have to worry about it21:17
tpatilAny comments?21:18
*** ivasev has joined #openstack-meeting21:18
johnthetubaguyyeah, that sounds like the compromise I remember us heading towards21:18
tpatiljohnthetubaguy: Right21:18
*** Berezin has quit IRC21:18
tpatilSecond concern: We were thinking of adding all base class (ListWithMeta, DictWithMeta) in oslo.incubator, but Brant pointed some serious concerns of using oslo.incubator library in keystoneclient21:19
tpatilIt's possible to add all these new classes in individual clients but it would be repetitive code21:19
bknudsonhaving oslo-incubator (unstable code) in keystoneclient (stable code) has been a real pain21:19
*** dane_leblanc has quit IRC21:19
*** dboik has quit IRC21:20
bknudsonI'd be fine if it was obvious that oslo-incubator code was private (prefixed with _)21:20
dhellmannwhere would these classes end up after they left the incubator?21:20
bknudsonbut that's not how apiclient was implemented21:20
*** henrynash has quit IRC21:20
*** dkranz has quit IRC21:20
morganfainbergif the oslo-incubator code isn't marked as private, I'm going to go out on a limb and say I will reject it for keystoneclient21:20
morganfainbergi don't want external projects grabbing the incubator code from keystoneclient as though it was a stable interface of keystoneclient21:21
dhellmanntpatil: I don't understand why subclassing tuple so methods that return tuples behave the same as the other methods is going to break anything?21:21
johnthetubaguyI am curious actually, what issues were you seeing with the incubator stuff? oh... thats nasty, I see21:21
dhellmannmorganfainberg: yeah, the incubated code should clearly be private. Maybe we should change foo/openstack to foo/_openstack21:22
*** GB21 has quit IRC21:22
morganfainbergdhellmann: that would solve my major concern :)21:22
bknudsondhellmann: that would be great21:22
dhellmannalthough I'm not certain why this needs to be incubated at all, so I would like to understand that and where it will live later on21:22
tpatildhellmann: we haven't change anything related to Tuple21:22
dhellmannbecause maybe it can just go there now and skip the incubation step21:22
*** ivasev has quit IRC21:22
*** kencjohnston has quit IRC21:23
morganfainbergdhellmann: i'd also be ok with that21:23
*** ivasev has joined #openstack-meeting21:23
Rockygthe less that has to migrate through the incubator, the better.21:23
dhellmanntpatil, bknudson : can one of you explain the concern about tuples? maybe I'm misunderstanding, but it sounded like you thought there was a reason not to change methods that return tuples?21:23
morganfainbergRockyg: ++21:23
fungiyeah, i thought oslo-incubator was for code extracted from one or more existing projects, not for entirely new works21:23
dhellmanntpatil: you say in a comment on line 111: "But we cannot change Tuple response since it will break OpenStack services consuming it."21:24
* morganfainberg is against incubator code in general, especially *new* incubator code21:24
Rockygmorganfainberg, me, too21:24
*** jmckind has quit IRC21:24
bknudsondhellmann: methods that return dict, dict is wrapped so you can do .request_id, whereas with tuple it's not wrapped so you can't do .request_id on the returned value21:24
tpatildhellman: first of all ,we cannot subclass tuple and add request_id attribute21:25
bknudsondhellmann: so my concern was that I'd like it to be consistent where everything that's returned you can do .request_id on it.21:25
dhellmannfungi: it is for code where we expect the API to have to evolve in a way that will break things. In the past the predominant source of that code has been other projects, but there's no hard rule for that.21:25
tpatildhellman, so we want to keep the same behavior21:25
dhellmanntpatil: why can't you subclass tuple?21:25
tpatildhellman: immutable21:25
tpatildhellman: we tried to override __new__ method but that doesn't help too21:26
*** salv-orlando has quit IRC21:26
dhellmanntpatil: it seems to work fine for me: http://paste.openstack.org/show/406994/21:26
fungidhellmann: interesting that there aren't better ways to avoid people thinking you have stable interfaces in a library besides avoiding making a library at all21:26
*** jmckind has joined #openstack-meeting21:26
morganfainbergfungi: issues with python :(21:27
fungibut i guess that's verging off topic21:27
bknudsonlet's switch to java21:27
dhellmanntpatil: a longer example: http://paste.openstack.org/show/406995/21:27
*** ivasev has quit IRC21:27
Rockygheretic!21:27
dhellmannfungi: well the point is that sometimes there aren't stable interfaces and rather than supporting something crummy for a long time we evolve it using static linking instead21:28
tpatildhellman: Ok, so with this, user can access request_id attribute21:28
dhellmannright21:28
tpatildhellman: We will confirm this if it works and incorporate it in the specs. Thanks.21:28
tpatilThird concern: In case ListWithMeta, request_id is of type list and other places it is not. why?21:29
tpatilListWithMeta type is returned mostly for various list (volumes/snapshots etc) methods.21:29
tpatilSo it may contain one or more request_ids depending on 'limit' and 'page_size' parameters passed in the request21:29
*** armax has quit IRC21:29
bknudsonso these comments were about making the interface consistent21:29
tpatilWhereas in all other cases, there will be only one request_id21:29
bknudsonso that the same code could be used to process it.21:29
tpatilbknudson: right21:29
dhellmannbknudson: do we need a list everywhere, then?21:29
tpatilBut if we want request_id attribute to be consistent for all types, then we will change it list type21:29
bknudsona list everywhere would be consistent21:29
dhellmannok, so then request_ids instead of request_id21:30
bknudsonand also more resilient in case other methods required making multiple calls21:30
tpatildhellman: sure21:30
johnthetubaguyyeah, that seems good, makes it simpler21:30
tpatilThat's address all my concerns, anyone has anything else to add21:30
tpatils/address/addresses21:31
Rockygsounds like one more revision might jsut do it.  Great work, tpatil21:31
markmcclainthanks for working on this the last few weeks21:31
tpatilRockyg: Thanks21:31
*** VW_ has quit IRC21:31
markmcclain#topic Vertical Team Announcements21:31
*** openstack changes topic to "Vertical Team Announcements (Meeting topic: crossproject)"21:31
markmcclainAny vertical team announcements?21:32
*** VW_ has joined #openstack-meeting21:32
*** mwagner_lap has quit IRC21:32
markmcclain#topic Open discussion21:32
*** openstack changes topic to "Open discussion (Meeting topic: crossproject)"21:32
markmcclain#info Travel Support Program Deadline is August 10th21:33
markmcclain#link https://wiki.openstack.org/wiki/Travel_Support_Program21:33
*** crc32 has quit IRC21:33
elmiko2 new api guidelines up for group review, #link http://lists.openstack.org/pipermail/openstack-dev/2015-August/071345.html21:33
*** safchain has quit IRC21:33
markmcclainelmiko: apologies... I missed those otherwise would have added to agenda21:34
elmikomarkmcclain,  no worries, it's more informational. i don't think there is much to discuss.21:34
markmcclainok21:34
elmikoalthough, i say that now, it really blew up last time lol21:35
*** cdub has joined #openstack-meeting21:35
markmcclainyeah.. funny how that happens21:35
markmcclainany other open items?21:35
elmikoalso, i did add them to the agenda wiki. is there a better place for future reference?21:35
markmcclainelmiko: that's the right place.. I had not refreshed my browser from this morning when I sent the email21:36
elmikogotcha, thanks =)21:36
markmcclain#info mestery to chair next week21:36
*** VW_ has quit IRC21:37
mesterymarkmcclain: Thanks ... I think. o_O21:37
mestery:)21:37
markmcclainThanks for volunteering21:37
markmcclainHave a great week everyone.21:37
markmcclain#endmeeting21:37
*** openstack changes topic to " (Meeting topic: third-party)"21:37
openstackMeeting ended Tue Aug  4 21:37:43 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-08-04-21.01.html21:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-08-04-21.01.txt21:37
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-08-04-21.01.log.html21:37
elmikothanks markmcclain21:37
RockygThanks!21:37
jokke_thanks!21:37
tpatilThanks everyone!21:37
mesterythanks markmcclain!21:38
*** salv-orlando has joined #openstack-meeting21:38
markmcclainhappy to take a turn at chair21:38
ttxsounds more like taking a bullet for the team21:38
mesterylol21:40
* mestery reminds himself to bring a bullet proof vest next week then21:40
*** gordc has joined #openstack-meeting21:40
*** Nikolay_St has quit IRC21:41
*** e0ne has quit IRC21:44
*** crc32 has joined #openstack-meeting21:47
*** NobodyCam has left #openstack-meeting21:50
*** banix has quit IRC21:54
*** otter768 has joined #openstack-meeting21:58
*** gordc has left #openstack-meeting21:59
*** haomaiwang has quit IRC22:00
*** amitgandhinz has quit IRC22:00
*** haomaiwang has joined #openstack-meeting22:00
*** JRobinson__ has joined #openstack-meeting22:01
*** armax has joined #openstack-meeting22:02
*** jmckind has quit IRC22:02
*** otter768 has quit IRC22:02
*** shashank_hegde has joined #openstack-meeting22:03
*** comay has quit IRC22:04
*** julim has quit IRC22:05
*** pradk has quit IRC22:05
*** julim has joined #openstack-meeting22:05
*** julim has quit IRC22:05
*** comay has joined #openstack-meeting22:06
*** jhenner has quit IRC22:06
*** cdub has quit IRC22:09
*** toscalix has quit IRC22:10
*** vijendar has quit IRC22:10
*** henrynash has joined #openstack-meeting22:12
*** tpatil has quit IRC22:13
*** haneef_ has quit IRC22:16
*** VW_ has joined #openstack-meeting22:16
*** alexey_nex has quit IRC22:17
*** crc32 has quit IRC22:18
*** singleth_ has quit IRC22:19
*** jecarey has quit IRC22:20
*** zul has quit IRC22:23
*** stevemar has joined #openstack-meeting22:24
*** sigmavirus24 is now known as sigmavirus24_awa22:25
*** IanGovett1 has quit IRC22:27
*** edtubill has quit IRC22:27
*** spzala has quit IRC22:29
*** ijw has joined #openstack-meeting22:33
*** nijaba_ has joined #openstack-meeting22:33
*** nijaba_ has quit IRC22:33
*** nijaba_ has joined #openstack-meeting22:33
*** nijaba has quit IRC22:34
*** Rockyg has quit IRC22:34
*** jaypipes has quit IRC22:35
*** rbak has quit IRC22:35
*** jasondotstar has quit IRC22:36
*** jjmb has quit IRC22:37
*** VW_ has quit IRC22:39
*** stevemar has quit IRC22:39
*** VW_ has joined #openstack-meeting22:39
*** boris-42 has quit IRC22:40
*** jasondotstar has joined #openstack-meeting22:40
*** galstrom is now known as galstrom_zzz22:40
*** bknudson has quit IRC22:44
*** VW_ has quit IRC22:44
*** lukebrooker has joined #openstack-meeting22:52
*** lukebrooker has quit IRC22:53
*** penick has quit IRC22:53
*** jasondotstar has quit IRC22:54
*** jasondotstar has joined #openstack-meeting22:54
*** zxiiro has quit IRC22:54
*** henrynash has quit IRC22:56
*** jasondotstar has quit IRC22:56
*** jasondotstar has joined #openstack-meeting22:59
*** haomaiwang has quit IRC23:00
*** lukebrooker has joined #openstack-meeting23:00
*** sdake has quit IRC23:00
*** haomaiwang has joined #openstack-meeting23:00
*** pballand has quit IRC23:02
*** elmiko has left #openstack-meeting23:04
*** mrmartin has joined #openstack-meeting23:04
*** echoingumesh has quit IRC23:07
*** cdub has joined #openstack-meeting23:07
*** aukhan has quit IRC23:08
*** yamamoto has joined #openstack-meeting23:09
*** aukhan has joined #openstack-meeting23:10
*** slong has joined #openstack-meeting23:11
*** echoingumesh has joined #openstack-meeting23:12
*** comay has quit IRC23:13
*** shashank_hegde has quit IRC23:13
*** shashank_hegde has joined #openstack-meeting23:15
*** comay has joined #openstack-meeting23:17
*** david-lyle has quit IRC23:18
*** tiswanso has joined #openstack-meeting23:19
*** kzaitsev_mb has quit IRC23:21
*** jmckind has joined #openstack-meeting23:22
*** dannywilson has quit IRC23:23
*** dims_ has quit IRC23:23
*** jmckind has quit IRC23:23
*** jmckind has joined #openstack-meeting23:24
*** ebalduf has quit IRC23:26
*** ijw_ has joined #openstack-meeting23:27
*** ebalduf has joined #openstack-meeting23:27
*** lpetrut has quit IRC23:28
*** cdelatte has quit IRC23:28
*** hemna has quit IRC23:28
*** kmartin has quit IRC23:28
*** bswartz has quit IRC23:28
*** lukebrooker has quit IRC23:29
*** cdub has quit IRC23:29
*** ijw has quit IRC23:30
*** tiswanso has quit IRC23:30
*** lukebrooker has joined #openstack-meeting23:32
*** ebalduf has quit IRC23:32
*** ijw has joined #openstack-meeting23:33
*** marcusvrn has quit IRC23:33
*** ijw_ has quit IRC23:36
*** ebalduf has joined #openstack-meeting23:37
*** boris-42 has joined #openstack-meeting23:37
*** madskier has joined #openstack-meeting23:39
*** topol has quit IRC23:39
*** harshs has quit IRC23:40
*** otter768 has joined #openstack-meeting23:41
*** ebalduf has quit IRC23:41
*** ivar-lazzaro has quit IRC23:41
*** madskier has quit IRC23:43
*** ivar-lazzaro has joined #openstack-meeting23:44
*** sdake has joined #openstack-meeting23:45
*** kencjohnston has joined #openstack-meeting23:46
*** dims has joined #openstack-meeting23:47
*** sdake_ has joined #openstack-meeting23:48
*** vivek-ebay has quit IRC23:49
*** vivek-ebay has joined #openstack-meeting23:50
*** cdelatte has joined #openstack-meeting23:51
*** delattec has joined #openstack-meeting23:51
*** IlyaG has quit IRC23:52
*** sdake has quit IRC23:52
*** banix has joined #openstack-meeting23:54
*** vivek-ebay has quit IRC23:54
*** galstrom_zzz is now known as galstrom23:55
*** vivek-ebay has joined #openstack-meeting23:56
*** emagana has quit IRC23:56
*** bauzas_off has quit IRC23:56
*** eliqiao has joined #openstack-meeting23:56
*** salv-orlando has quit IRC23:57
*** kencjohnston has quit IRC23:58
*** kencjohnston has joined #openstack-meeting23:58
*** bauzas has joined #openstack-meeting23:58
*** KunalGandhi has joined #openstack-meeting23:59

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