Tuesday, 2015-09-29

*** shivharis has quit IRC00:00
*** pratikma_ has quit IRC00:01
*** yamahata has quit IRC00:01
*** okrieg has quit IRC00:03
*** okrieg has joined #openstack-meeting00:03
*** yamamoto has joined #openstack-meeting00:03
*** MarkAtwood has joined #openstack-meeting00:04
*** harshs has joined #openstack-meeting00:06
*** emagana has joined #openstack-meeting00:06
*** geoffarnold has joined #openstack-meeting00:08
*** asselin_ has joined #openstack-meeting00:08
*** lukebrooker has joined #openstack-meeting00:09
*** amrith is now known as _amrith_00:09
*** VW has joined #openstack-meeting00:09
*** Daisy_ has joined #openstack-meeting00:09
*** VW has quit IRC00:10
*** VW has joined #openstack-meeting00:10
*** IlyaG has quit IRC00:11
*** ekcs has joined #openstack-meeting00:13
*** okrieg has quit IRC00:13
*** ekcs has left #openstack-meeting00:13
*** dt_os has quit IRC00:13
*** Daisy_ has quit IRC00:14
*** galstrom is now known as galstrom_zzz00:16
*** okrieg has joined #openstack-meeting00:16
*** galstrom_zzz is now known as galstrom00:17
*** banix has joined #openstack-meeting00:17
*** IlyaG has joined #openstack-meeting00:18
*** MaxPC has quit IRC00:20
*** MaxPC has joined #openstack-meeting00:21
*** electroc_ has quit IRC00:21
*** su_zhang has quit IRC00:23
*** Tango has quit IRC00:23
*** dims has joined #openstack-meeting00:24
*** ujuc has joined #openstack-meeting00:27
*** ociuhandu has joined #openstack-meeting00:27
*** _amrith_ is now known as amrith00:27
*** bobh has joined #openstack-meeting00:28
*** kebray has quit IRC00:28
*** pvaneck has quit IRC00:29
*** tomoe_ has joined #openstack-meeting00:29
*** temujin_ has quit IRC00:30
*** pratikmallya has quit IRC00:30
*** tomoe__ has joined #openstack-meeting00:31
*** Sukhdev has joined #openstack-meeting00:31
*** VW has quit IRC00:32
*** tomoe_ has quit IRC00:32
*** VW has joined #openstack-meeting00:32
*** tsekiyama has quit IRC00:33
*** DericHorn-HP has joined #openstack-meeting00:34
*** dmacpher has joined #openstack-meeting00:34
*** xingchao has joined #openstack-meeting00:36
*** VW has quit IRC00:36
*** oomichi has joined #openstack-meeting00:39
*** IlyaG has quit IRC00:39
*** leeantho has quit IRC00:40
*** temujin_ has joined #openstack-meeting00:41
*** harshs_ has joined #openstack-meeting00:44
*** harshs has quit IRC00:45
*** amit213 has quit IRC00:45
*** harshs_ is now known as harshs00:45
*** aranjan has quit IRC00:45
*** VW has joined #openstack-meeting00:46
*** temujin_ has quit IRC00:47
*** zaneb has quit IRC00:47
*** B_Smith has quit IRC00:47
*** _hrou_ has joined #openstack-meeting00:47
*** zaneb has joined #openstack-meeting00:47
*** temujin_ has joined #openstack-meeting00:47
*** gongysh has quit IRC00:47
*** B_Smith has joined #openstack-meeting00:48
*** pratikmallya has joined #openstack-meeting00:49
*** DericHorn-HP has quit IRC00:49
*** VW has quit IRC00:51
*** hrou has quit IRC00:51
*** ujuc has quit IRC00:51
*** VW has joined #openstack-meeting00:51
*** DericHorn-HP has joined #openstack-meeting00:52
*** gongysh has joined #openstack-meeting00:54
*** geoffarnold has quit IRC00:54
*** Swami has quit IRC00:55
*** shakamunyi has joined #openstack-meeting00:55
*** VW has quit IRC00:55
*** andreykurilin__ has quit IRC00:56
*** penick has quit IRC00:57
*** baoli has joined #openstack-meeting00:58
*** aysyd has quit IRC00:58
*** shashank_hegde has quit IRC00:59
*** elo1 has quit IRC01:01
*** harshs has quit IRC01:01
*** inteq has joined #openstack-meeting01:04
*** kencjohnston has joined #openstack-meeting01:05
*** mtanino has quit IRC01:09
*** lazy_prince has joined #openstack-meeting01:13
*** JRobinson__ has joined #openstack-meeting01:14
*** MarkAtwood has quit IRC01:14
*** novas0x2a|laptop has quit IRC01:14
*** galstrom is now known as galstrom_zzz01:15
*** Daisy_ has joined #openstack-meeting01:16
*** DericHorn-HP has quit IRC01:20
*** zhhuabj has quit IRC01:24
*** MarkAtwood has joined #openstack-meeting01:25
*** Sukhdev has quit IRC01:26
*** apoorvad_ has joined #openstack-meeting01:27
*** harshs has joined #openstack-meeting01:29
*** apoorvad has quit IRC01:31
*** adahms has joined #openstack-meeting01:31
*** apoorvad_ has quit IRC01:31
*** unicell has quit IRC01:33
*** summer has joined #openstack-meeting01:34
*** okrieg has quit IRC01:36
*** zhhuabj has joined #openstack-meeting01:38
*** okrieg has joined #openstack-meeting01:38
*** tfukushima has joined #openstack-meeting01:42
*** okrieg has quit IRC01:42
*** sbalukoff has quit IRC01:46
*** otter768 has joined #openstack-meeting01:47
*** DericHorn-HP has joined #openstack-meeting01:48
*** sridhar_ram has quit IRC01:51
*** otter768 has quit IRC01:52
*** harshs has quit IRC01:54
*** yamamoto has quit IRC01:55
*** changbl has joined #openstack-meeting01:55
*** baoli has quit IRC01:55
*** DericHorn-HP has quit IRC01:56
*** yamahata has joined #openstack-meeting01:57
*** julim has joined #openstack-meeting01:57
*** cdash has joined #openstack-meeting01:58
*** amrith is now known as _amrith_01:59
*** okrieg has joined #openstack-meeting01:59
*** s3wong has quit IRC02:00
*** Daisy_ has quit IRC02:00
*** edtubill has joined #openstack-meeting02:00
*** johnhunter has joined #openstack-meeting02:01
*** Daisy_ has joined #openstack-meeting02:01
*** DericHorn-HP has joined #openstack-meeting02:02
*** banix has quit IRC02:03
*** sankarshan_away is now known as sankarshan02:03
*** okrieg has quit IRC02:04
*** changbl has quit IRC02:04
*** baoli has joined #openstack-meeting02:06
*** MarkAtwood has quit IRC02:06
*** sballe has quit IRC02:06
*** dims has quit IRC02:09
*** DericHorn-HP has quit IRC02:11
*** epico has joined #openstack-meeting02:12
*** ivar-laz_ has joined #openstack-meeting02:13
*** bobh has quit IRC02:13
*** yamahata has quit IRC02:15
*** bobh has joined #openstack-meeting02:16
*** ivar-lazzaro has quit IRC02:16
*** ivar-laz_ has quit IRC02:18
*** banix has joined #openstack-meeting02:18
*** ayoung has quit IRC02:18
*** stevemar has joined #openstack-meeting02:19
*** bobh has quit IRC02:20
*** banix has quit IRC02:24
*** ddieterly has joined #openstack-meeting02:25
*** tfukushima has quit IRC02:25
*** achanda has joined #openstack-meeting02:25
*** lukebrooker has quit IRC02:26
*** doug-fish has joined #openstack-meeting02:27
*** salv-orlando has joined #openstack-meeting02:28
*** ddieterl_ has quit IRC02:29
*** vivek-eb_ has quit IRC02:29
*** tfukushima has joined #openstack-meeting02:30
*** baoli has quit IRC02:32
*** hoangcx has joined #openstack-meeting02:33
*** adahms has quit IRC02:36
*** salv-orlando has quit IRC02:37
*** badveli has quit IRC02:38
*** harshs has joined #openstack-meeting02:41
*** garthb has joined #openstack-meeting02:44
*** oomichi has quit IRC02:46
*** bobh has joined #openstack-meeting02:46
*** zhhuabj has quit IRC02:47
*** yamamoto has joined #openstack-meeting02:48
*** baoli has joined #openstack-meeting02:49
*** lazy_prince has quit IRC02:50
*** hparekh has joined #openstack-meeting02:50
*** ijw has quit IRC02:51
*** haomaiwang has joined #openstack-meeting02:51
*** asettle has quit IRC02:55
*** baoli has quit IRC02:56
*** baoli has joined #openstack-meeting02:57
*** haomaiwang has quit IRC03:01
*** asettle has joined #openstack-meeting03:01
*** haomaiwang has joined #openstack-meeting03:01
*** kencjohnston has quit IRC03:02
*** baoli has quit IRC03:03
*** zhhuabj has joined #openstack-meeting03:04
*** harshs has quit IRC03:05
*** VW has joined #openstack-meeting03:05
*** kebray has joined #openstack-meeting03:08
*** achanda has quit IRC03:09
*** dims has joined #openstack-meeting03:09
*** lukebrooker has joined #openstack-meeting03:10
*** zhhuabj has quit IRC03:10
*** rfolco has joined #openstack-meeting03:10
*** doug-fish has quit IRC03:14
*** DericHorn-HP has joined #openstack-meeting03:14
*** dims has quit IRC03:16
*** ItSANgo has quit IRC03:17
*** bnemec has quit IRC03:17
*** MaxPC has quit IRC03:18
*** jdurgin1 has joined #openstack-meeting03:18
*** _hrou_ has quit IRC03:19
*** boris-42 has quit IRC03:19
*** ganeshna has joined #openstack-meeting03:20
*** hemna has joined #openstack-meeting03:20
*** deepthi has joined #openstack-meeting03:23
*** Daisy_ has quit IRC03:27
*** Daisy has joined #openstack-meeting03:28
*** ddieterly has quit IRC03:29
*** boris-42 has joined #openstack-meeting03:29
*** shashank_hegde has joined #openstack-meeting03:30
*** rfolco has quit IRC03:30
*** baoli has joined #openstack-meeting03:31
*** asettle is now known as asettle-afk03:32
*** DericHorn-HP has quit IRC03:32
*** Daisy has quit IRC03:32
*** bobh has quit IRC03:32
*** ganeshna has quit IRC03:33
*** BharatK has joined #openstack-meeting03:34
*** ganeshna has joined #openstack-meeting03:35
*** baoli has quit IRC03:37
*** ganeshna has quit IRC03:40
*** vilobhmm111 has quit IRC03:40
*** asettle-afk is now known as asettle03:42
*** harshs has joined #openstack-meeting03:42
*** ujuc has joined #openstack-meeting03:44
*** bill_az has quit IRC03:44
*** baigk has quit IRC03:45
*** MarkAtwood has joined #openstack-meeting03:45
*** DericHorn-HP has joined #openstack-meeting03:46
*** DericHorn-HP has quit IRC03:49
*** Tango has joined #openstack-meeting03:50
*** vilobhmm11 has joined #openstack-meeting03:53
*** vilobhmm11 has quit IRC03:54
*** baigk has joined #openstack-meeting03:55
*** zhhuabj has joined #openstack-meeting03:55
*** markvoelker has quit IRC03:56
*** vilobhmm11 has joined #openstack-meeting03:56
*** zehicle has quit IRC03:58
*** ociuhandu has quit IRC04:00
*** zhhuabj has quit IRC04:00
*** haomaiwang has quit IRC04:01
*** haomaiwang has joined #openstack-meeting04:01
*** zhhuabj has joined #openstack-meeting04:03
*** vivek-ebay has joined #openstack-meeting04:06
*** hemna has quit IRC04:06
*** mrmartin has joined #openstack-meeting04:09
*** zhhuabj has quit IRC04:09
*** ganeshna has joined #openstack-meeting04:14
*** iben has joined #openstack-meeting04:14
*** ajmiller has joined #openstack-meeting04:16
*** nikhil_k has joined #openstack-meeting04:16
*** spzala has quit IRC04:17
*** nikhil has quit IRC04:18
*** IlyaG has joined #openstack-meeting04:18
*** pratikmallya has quit IRC04:18
*** rossella_s has quit IRC04:19
*** rossella_s has joined #openstack-meeting04:19
*** jdurgin1 has quit IRC04:21
*** comay has quit IRC04:23
*** hparekh has quit IRC04:24
*** pratikmallya has joined #openstack-meeting04:24
*** pratikmallya has quit IRC04:24
*** topol has joined #openstack-meeting04:25
*** zhhuabj has joined #openstack-meeting04:26
*** JRobinson__ is now known as JRobinson__afk04:27
*** pratikmallya has joined #openstack-meeting04:27
*** sdake_ has joined #openstack-meeting04:28
*** salv-orlando has joined #openstack-meeting04:29
*** achanda has joined #openstack-meeting04:29
*** ddieterly has joined #openstack-meeting04:29
*** lazy_prince has joined #openstack-meeting04:31
*** DericHorn-HP has joined #openstack-meeting04:31
*** sdake has quit IRC04:31
*** pratikmallya has quit IRC04:32
*** aukhan has joined #openstack-meeting04:33
*** DericHorn-HP has quit IRC04:34
*** unicell has joined #openstack-meeting04:35
*** BharatK has quit IRC04:38
*** MarkAtwood has quit IRC04:38
*** salv-orlando has quit IRC04:38
*** IlyaG has quit IRC04:38
*** nadya has joined #openstack-meeting04:41
*** JRobinson__afk is now known as JRobinson__04:41
*** jtomasek has joined #openstack-meeting04:42
*** nadya has quit IRC04:42
*** zhhuabj has quit IRC04:42
*** hparekh has joined #openstack-meeting04:42
*** MarkAtwood has joined #openstack-meeting04:44
*** harshs_ has joined #openstack-meeting04:45
*** baigk has quit IRC04:47
*** vivek-ebay has quit IRC04:47
*** harshs has quit IRC04:47
*** harshs_ is now known as harshs04:47
*** DericHorn-HP has joined #openstack-meeting04:48
*** zhhuabj has joined #openstack-meeting04:49
*** JRobinson__ has quit IRC04:49
*** geoffarnold has joined #openstack-meeting04:50
*** JRobinson__ has joined #openstack-meeting04:51
*** ajmiller_ has joined #openstack-meeting04:51
*** geoffarn_ has joined #openstack-meeting04:51
*** su_zhang has joined #openstack-meeting04:51
*** baigk has joined #openstack-meeting04:52
*** tfukushima has quit IRC04:52
*** ajmiller has quit IRC04:53
*** roxanaghe has joined #openstack-meeting04:54
*** geoffarnold has quit IRC04:55
*** zhhuabj has quit IRC04:55
*** cdash has quit IRC04:55
*** geoffarn_ is now known as geoffarnoldX04:56
*** lukebrooker has quit IRC04:56
*** DericHorn-HP has quit IRC04:56
*** markvoelker has joined #openstack-meeting04:57
*** vilobhmm11 has left #openstack-meeting04:58
*** nadya has joined #openstack-meeting05:00
*** haomaiwang has quit IRC05:01
*** nadya has quit IRC05:01
*** haomaiwang has joined #openstack-meeting05:01
*** nadya has joined #openstack-meeting05:01
*** ozstacker_ has joined #openstack-meeting05:01
*** markvoelker has quit IRC05:01
*** VW has quit IRC05:02
*** iben_ has joined #openstack-meeting05:02
*** VW has joined #openstack-meeting05:02
*** stevemar has quit IRC05:03
*** hemna has joined #openstack-meeting05:03
*** hemna has quit IRC05:03
*** iben_ has quit IRC05:04
*** iben has quit IRC05:04
*** ozstacker has quit IRC05:04
*** zhhuabj has joined #openstack-meeting05:07
*** geoffarnold has joined #openstack-meeting05:12
*** dims has joined #openstack-meeting05:13
*** neeti has joined #openstack-meeting05:15
*** IlyaG has joined #openstack-meeting05:16
*** geoffarnoldX has quit IRC05:16
*** comay has joined #openstack-meeting05:17
*** asselin__ has joined #openstack-meeting05:17
*** zhhuabj has quit IRC05:18
*** dims has quit IRC05:18
*** VW_ has joined #openstack-meeting05:20
*** IlyaG has quit IRC05:20
*** asselin_ has quit IRC05:21
*** VW_ has quit IRC05:22
*** IlyaG has joined #openstack-meeting05:22
*** VW_ has joined #openstack-meeting05:23
*** temujin_ has quit IRC05:23
*** krtaylor has quit IRC05:23
*** VW has quit IRC05:24
*** Sukhdev has joined #openstack-meeting05:25
*** killer_prince has joined #openstack-meeting05:25
*** doug-fish has joined #openstack-meeting05:25
*** dmacpher has quit IRC05:26
*** lazy_prince has quit IRC05:29
*** liusheng has quit IRC05:30
*** shihanzhang has joined #openstack-meeting05:30
*** doug-fish has quit IRC05:30
*** liusheng has joined #openstack-meeting05:31
*** zhhuabj has joined #openstack-meeting05:31
*** cFouts has quit IRC05:31
*** krtaylor has joined #openstack-meeting05:32
*** garthb has quit IRC05:32
*** iben has joined #openstack-meeting05:32
*** shz has quit IRC05:32
*** bobh has joined #openstack-meeting05:33
*** sileht has quit IRC05:33
*** geoffarnold has quit IRC05:33
*** geoffarnold has joined #openstack-meeting05:34
*** achanda has quit IRC05:36
*** stevemar has joined #openstack-meeting05:36
*** roxanaghe has quit IRC05:37
*** bobh has quit IRC05:38
*** nadya has quit IRC05:38
*** johnhunter has quit IRC05:38
*** dmacpher has joined #openstack-meeting05:39
*** topol has quit IRC05:40
*** stevemar_ has joined #openstack-meeting05:42
*** stevema__ has joined #openstack-meeting05:43
*** harshs has quit IRC05:44
*** stevemar has quit IRC05:45
*** jprovazn has joined #openstack-meeting05:46
*** stevemar_ has quit IRC05:46
*** vivek-ebay has joined #openstack-meeting05:48
*** gampel has joined #openstack-meeting05:48
*** otter768 has joined #openstack-meeting05:49
*** vivek-ebay has quit IRC05:52
*** JRobinson__ has quit IRC05:52
*** dmacpher_ has joined #openstack-meeting05:53
*** BharatK has joined #openstack-meeting05:53
*** tfukushima has joined #openstack-meeting05:53
*** otter768 has quit IRC05:53
*** VW_ has quit IRC05:54
*** VW has joined #openstack-meeting05:54
*** ganeshna has quit IRC05:55
*** hoangcx has quit IRC05:55
*** geoffarn_ has joined #openstack-meeting05:55
*** geoffarnold has quit IRC05:55
*** sdake_ is now known as sdake05:56
*** amotoki has joined #openstack-meeting05:56
*** dmacpher has quit IRC05:56
*** lsmola has joined #openstack-meeting05:58
*** tfukushima has quit IRC05:58
*** VW has quit IRC05:59
*** zhhuabj has quit IRC06:00
*** haomaiwang has quit IRC06:01
*** haomaiwang has joined #openstack-meeting06:01
*** Murali has joined #openstack-meeting06:01
*** tfukushima has joined #openstack-meeting06:04
*** SridharG has joined #openstack-meeting06:05
*** austin81 has quit IRC06:05
*** Daisy has joined #openstack-meeting06:06
*** zz_ttrifonov is now known as ttrifonov06:07
*** zhhuabj has joined #openstack-meeting06:12
*** shashank_hegde has quit IRC06:12
*** ganeshna has joined #openstack-meeting06:12
*** irenab has quit IRC06:13
*** su_zhang has quit IRC06:15
*** jtomasek has quit IRC06:16
*** geoffarn_ has quit IRC06:16
*** geoffarnold has joined #openstack-meeting06:17
*** rajinir has quit IRC06:18
*** vgridnev has joined #openstack-meeting06:18
*** Sukhdev has quit IRC06:20
*** topol has joined #openstack-meeting06:20
*** oomichi has joined #openstack-meeting06:20
*** fawadkhaliq has joined #openstack-meeting06:21
*** armax has quit IRC06:24
*** sbelous has joined #openstack-meeting06:25
*** topol has quit IRC06:25
*** oomichi has quit IRC06:25
*** dmacpher_ has quit IRC06:26
*** nadya has joined #openstack-meeting06:26
*** asselin_ has joined #openstack-meeting06:26
*** e0ne has joined #openstack-meeting06:27
*** stevema__ has quit IRC06:28
*** stevemar has joined #openstack-meeting06:28
*** fawadkhaliq has quit IRC06:30
*** zhhuabj has quit IRC06:30
*** zhhuabj has joined #openstack-meeting06:30
*** asselin__ has quit IRC06:30
*** sdake_ has joined #openstack-meeting06:33
*** stevemar has quit IRC06:33
*** MarkAtwood has quit IRC06:33
*** MarkAtwood has joined #openstack-meeting06:33
*** e0ne has quit IRC06:34
*** sdake has quit IRC06:36
*** geoffarnold has quit IRC06:38
*** geoffarnold has joined #openstack-meeting06:38
*** peristeri has joined #openstack-meeting06:38
*** Daisy has quit IRC06:39
*** Daisy has joined #openstack-meeting06:40
*** mgrohar has joined #openstack-meeting06:41
*** Daisy has quit IRC06:42
*** Daisy has joined #openstack-meeting06:42
*** zhhuabj has quit IRC06:44
*** salv-orlando has joined #openstack-meeting06:44
*** markvoelker has joined #openstack-meeting06:45
*** irenab has joined #openstack-meeting06:46
*** salv-orlando has quit IRC06:47
*** ganeshna has quit IRC06:49
*** IlyaG has quit IRC06:50
*** markvoelker has quit IRC06:50
*** ganeshna has joined #openstack-meeting06:50
*** changzhi has joined #openstack-meeting06:56
*** zhhuabj has joined #openstack-meeting06:57
*** ganeshna has quit IRC06:58
*** geoffarn_ has joined #openstack-meeting06:59
*** geoffarnold has quit IRC06:59
*** haomaiwang has quit IRC07:01
*** haomaiwang has joined #openstack-meeting07:01
*** ganeshna has joined #openstack-meeting07:01
*** vhejral has joined #openstack-meeting07:04
*** jwcroppe has joined #openstack-meeting07:04
*** ganeshna has quit IRC07:06
*** e0ne has joined #openstack-meeting07:07
*** lazy_prince has joined #openstack-meeting07:09
*** e0ne has quit IRC07:09
*** Daisy has quit IRC07:09
*** Daisy has joined #openstack-meeting07:10
*** sdake_ is now known as sdake07:10
*** matrohon has joined #openstack-meeting07:10
*** killer_prince has quit IRC07:11
*** berendt has joined #openstack-meeting07:13
*** Daisy has quit IRC07:14
*** Tango has quit IRC07:16
*** sbalukoff has joined #openstack-meeting07:17
*** egallen has joined #openstack-meeting07:20
*** geoffarnold has joined #openstack-meeting07:20
*** e0ne has joined #openstack-meeting07:21
*** geoffarn_ has quit IRC07:21
*** salv-orlando has joined #openstack-meeting07:28
*** ganeshna has joined #openstack-meeting07:28
*** mgrohar has quit IRC07:28
*** hashar has joined #openstack-meeting07:29
*** alexpilotti has joined #openstack-meeting07:31
*** lazy_prince has quit IRC07:32
*** lazy_prince has joined #openstack-meeting07:32
*** salv-orlando has quit IRC07:32
*** ganeshna has quit IRC07:33
*** bobh has joined #openstack-meeting07:34
*** ildikov has joined #openstack-meeting07:34
*** yamahata has joined #openstack-meeting07:36
*** adiantum has joined #openstack-meeting07:36
*** lazy_prince has quit IRC07:37
*** lazy_prince has joined #openstack-meeting07:38
*** kebray has quit IRC07:38
*** bobh has quit IRC07:38
*** lazy_prince has quit IRC07:42
*** lazy_prince has joined #openstack-meeting07:42
*** ganeshna has joined #openstack-meeting07:43
*** acc_ has quit IRC07:44
*** acc__ has joined #openstack-meeting07:44
*** jlanoux has joined #openstack-meeting07:45
*** fzdarsky has joined #openstack-meeting07:48
*** moha_hunt has quit IRC07:48
*** ttrifonov is now known as zz_ttrifonov07:49
*** sridhar_ram has joined #openstack-meeting07:49
*** otter768 has joined #openstack-meeting07:50
*** _amrith_ is now known as amrith07:50
*** mgrohar has joined #openstack-meeting07:50
*** zz_ttrifonov is now known as ttrifonov07:51
*** alexpilotti has quit IRC07:52
*** ihrachys has joined #openstack-meeting07:53
*** sridhar_ram has quit IRC07:54
*** otter768 has quit IRC07:54
*** ihrachys has quit IRC07:56
*** amrith is now known as _amrith_07:59
anteaya#startmeeting third-party08:00
openstackMeeting started Tue Sep 29 08:00:14 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: third-party)"08:00
openstackThe meeting name has been set to 'third_party'08:00
anteayahello08:00
*** jhenner has joined #openstack-meeting08:00
*** asettle has quit IRC08:00
*** haomaiwang has quit IRC08:01
anteayaif you are present for the third party meeting do raise your hand08:01
*** haomaiwang has joined #openstack-meeting08:01
vhejralhi, raising08:01
anteayavhejral: hello08:02
anteayavhejral: you were here last week, welcome back08:03
vhejralthanks08:03
anteayadid you have anything you wanted to discuss today?08:03
lennybhi08:03
vhejralanteaya: no08:04
anteayahi lennyb08:04
anteayavhejral: okay thanks08:04
lennybI have nothing to discuss08:04
anteayalennyb: okay thanks for letting me know08:04
*** vgridnev has quit IRC08:05
anteaya#link http://lists.openstack.org/pipermail/openstack-dev/2015-September/075532.html08:05
*** lazy_prince has quit IRC08:05
anteayatake a look at that email post to the -dev mailing list08:05
*** lazy_prince has joined #openstack-meeting08:05
anteayait is the beginning of an initiative by the openstack foundation08:05
anteayahogepodge is the driver08:05
anteayahe is calling for participation so now is a good time to get involved with him08:06
anteayayou can contact him directly08:06
anteayanothing with change as far as what is required from infra and from the projects08:06
anteayathis is what the openstack foundation will want to see regarding the use of trademarks08:07
*** yassine__ has joined #openstack-meeting08:07
*** derekh has joined #openstack-meeting08:07
anteayadoes that make sense?08:07
*** ganeshna has quit IRC08:07
lennybabsolutely. We will check what do we need08:08
vhejralwe'll check08:08
*** safchain has joined #openstack-meeting08:09
anteayagreat thank you08:09
anteayahow are your systems working?08:10
*** ygbo has joined #openstack-meeting08:12
vhejralCIs are fine so far08:12
anteayavhejral: okay great, thank you08:13
anteayacan you take a look at this spec08:14
anteaya#link https://review.openstack.org/#/c/194437/08:14
anteayaand consider offering a review08:14
*** nithyag_ has quit IRC08:15
vhejrali'll do08:16
anteayathank you vhejral08:17
*** mpaolino has joined #openstack-meeting08:17
*** rossella_s has quit IRC08:19
*** rossella_s has joined #openstack-meeting08:19
anteayacan we think of any reason for me to keep the meeting open?08:21
*** cdub has quit IRC08:22
anteayaokay I will close it08:22
anteayathank you for your kind attendance and participation08:23
anteayasee you next week08:23
anteaya#endmeeting08:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:23
openstackMeeting ended Tue Sep 29 08:23:19 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-09-29-08.00.html08:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-09-29-08.00.txt08:23
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-09-29-08.00.log.html08:23
*** vhejral has quit IRC08:23
*** geoffarnold has quit IRC08:23
*** geoffarnold has joined #openstack-meeting08:24
*** lazy_prince has quit IRC08:28
*** killer_prince has joined #openstack-meeting08:28
*** Daisy has joined #openstack-meeting08:32
*** sankarshan is now known as sankarshan_away08:33
*** salv-orlando has joined #openstack-meeting08:35
*** iben has quit IRC08:39
*** VW has joined #openstack-meeting08:40
*** toscalix__ has joined #openstack-meeting08:40
*** VW has quit IRC08:40
*** VW has joined #openstack-meeting08:41
*** geoffarnold has quit IRC08:45
*** geoffarnold has joined #openstack-meeting08:45
*** VW has quit IRC08:45
*** markvoelker has joined #openstack-meeting08:46
*** vgridnev has joined #openstack-meeting08:48
*** devvesa has joined #openstack-meeting08:49
*** jtomasek has joined #openstack-meeting08:50
*** markvoelker has quit IRC08:51
*** killer_prince has quit IRC08:51
*** killer_prince has joined #openstack-meeting08:51
*** claudiub has joined #openstack-meeting08:58
*** ganeshna has joined #openstack-meeting09:00
*** haomaiwang has quit IRC09:01
*** edtubill has quit IRC09:01
*** haomaiwang has joined #openstack-meeting09:01
*** jorge_munoz_ has joined #openstack-meeting09:06
*** geoffarnold has quit IRC09:06
*** geoffarnold has joined #openstack-meeting09:06
*** ndipanov has quit IRC09:07
*** jorge_munoz has quit IRC09:08
*** jorge_munoz_ is now known as jorge_munoz09:08
*** oomichi has joined #openstack-meeting09:13
*** ganeshna has quit IRC09:14
*** dims has joined #openstack-meeting09:16
*** killer_prince has quit IRC09:16
*** killer_prince has joined #openstack-meeting09:16
*** ndipanov has joined #openstack-meeting09:18
*** gampel has quit IRC09:18
*** ganeshna has joined #openstack-meeting09:19
*** salv-orl_ has joined #openstack-meeting09:21
*** dims has quit IRC09:22
*** baigk has quit IRC09:24
*** salv-orlando has quit IRC09:25
*** geoffarnold has quit IRC09:27
*** geoffarnold has joined #openstack-meeting09:28
*** sankarshan_away is now known as sankarshan09:32
*** VW has joined #openstack-meeting09:32
*** jlanoux has quit IRC09:33
*** VW has quit IRC09:38
*** VW has joined #openstack-meeting09:38
*** numans has joined #openstack-meeting09:40
*** bvandenh has joined #openstack-meeting09:42
*** sankarshan is now known as sankarshan_away09:43
*** jlanoux has joined #openstack-meeting09:45
*** xingchao has quit IRC09:45
*** gchamoul has left #openstack-meeting09:46
*** dims has joined #openstack-meeting09:47
*** geoffarnold has quit IRC09:49
*** geoffarnold has joined #openstack-meeting09:49
*** sankarshan_away is now known as sankarshan09:49
*** ujuc has quit IRC09:50
*** otter768 has joined #openstack-meeting09:51
*** ganeshna has quit IRC09:51
*** pelix has joined #openstack-meeting09:51
*** VW has quit IRC09:51
*** VW has joined #openstack-meeting09:52
*** tfukushima has quit IRC09:54
*** ganeshna has joined #openstack-meeting09:54
*** otter768 has quit IRC09:55
*** Daisy has quit IRC09:56
*** tfukushima has joined #openstack-meeting09:56
*** Daisy has joined #openstack-meeting09:56
*** VW has quit IRC09:56
*** kbyrne has quit IRC09:58
*** haomaiwang has quit IRC10:01
*** Daisy has quit IRC10:01
*** haomaiwa_ has joined #openstack-meeting10:01
*** yassine__ has quit IRC10:02
*** kbyrne has joined #openstack-meeting10:03
*** sudipto has joined #openstack-meeting10:03
*** IanGovett has joined #openstack-meeting10:04
*** summer has quit IRC10:04
*** haomaiwa_ has quit IRC10:07
*** asettle has joined #openstack-meeting10:08
*** asettle has quit IRC10:08
*** epico has quit IRC10:08
*** asettle has joined #openstack-meeting10:09
*** xingchao has joined #openstack-meeting10:09
*** xingchao has quit IRC10:11
*** geoffarnold has quit IRC10:13
*** vjay11 has joined #openstack-meeting10:19
*** geoffarnold has joined #openstack-meeting10:20
*** vivek-ebay has joined #openstack-meeting10:21
*** ganeshna has quit IRC10:24
*** vivek-ebay has quit IRC10:26
*** ganeshna has joined #openstack-meeting10:27
*** ganeshna has quit IRC10:28
*** jlanoux_ has joined #openstack-meeting10:31
*** ganeshna has joined #openstack-meeting10:32
*** jlanoux has quit IRC10:34
*** ganeshna has quit IRC10:34
*** egallen has quit IRC10:35
*** vjay11 has quit IRC10:38
*** mgrohar has quit IRC10:40
*** xingchao has joined #openstack-meeting10:41
*** adiantum has quit IRC10:42
*** jlanoux has joined #openstack-meeting10:45
*** ihrachys has joined #openstack-meeting10:46
*** markvoelker has joined #openstack-meeting10:47
*** jlanoux_ has quit IRC10:48
*** sdake_ has joined #openstack-meeting10:50
*** ozstacker has joined #openstack-meeting10:51
*** markvoelker has quit IRC10:52
*** Daisy has joined #openstack-meeting10:52
*** pnavarro has joined #openstack-meeting10:52
*** vjay11 has joined #openstack-meeting10:52
*** doug-fish has joined #openstack-meeting10:53
*** ozstacker_ has quit IRC10:53
*** sdake has quit IRC10:54
*** 18VAARFFB has joined #openstack-meeting10:56
*** aukhan has quit IRC10:57
*** doug-fish has quit IRC10:57
*** claudiub has quit IRC10:59
*** ozstacker_ has joined #openstack-meeting10:59
*** xingchao has quit IRC11:00
*** 18VAARFFB has quit IRC11:01
*** haomaiwang has joined #openstack-meeting11:01
*** ozstacker has quit IRC11:02
*** ganeshna has joined #openstack-meeting11:02
*** ganeshna has quit IRC11:03
*** ganeshna has joined #openstack-meeting11:03
*** ozstacker has joined #openstack-meeting11:04
*** tfukushima has quit IRC11:05
*** jecarey has joined #openstack-meeting11:05
*** ozstacker_ has quit IRC11:06
*** yassine__ has joined #openstack-meeting11:07
*** vjay11 has quit IRC11:07
*** mpaolino has quit IRC11:09
*** haomaiwang has quit IRC11:11
*** yamamoto has quit IRC11:14
*** rtheis has joined #openstack-meeting11:16
*** changzhi has quit IRC11:17
*** Daisy has quit IRC11:19
*** Daisy has joined #openstack-meeting11:20
*** delattec has quit IRC11:21
*** salv-orl_ has quit IRC11:22
*** mgrohar has joined #openstack-meeting11:22
*** Daisy has quit IRC11:22
*** salv-orlando has joined #openstack-meeting11:23
*** Daisy has joined #openstack-meeting11:23
*** tfukushima has joined #openstack-meeting11:23
*** egallen has joined #openstack-meeting11:23
*** Daisy has quit IRC11:23
*** Daisy has joined #openstack-meeting11:24
*** mgrohar has quit IRC11:24
*** Daisy has quit IRC11:25
*** Daisy has joined #openstack-meeting11:26
*** baoli has joined #openstack-meeting11:27
*** Daisy has quit IRC11:27
*** Daisy has joined #openstack-meeting11:27
*** Daisy has quit IRC11:27
*** egallen has quit IRC11:28
*** Daisy has joined #openstack-meeting11:28
*** egallen has joined #openstack-meeting11:28
*** baoli_ has joined #openstack-meeting11:28
*** deepthi has quit IRC11:29
*** ccavanna has quit IRC11:30
*** hashar has quit IRC11:30
*** jecarey has quit IRC11:31
*** baoli has quit IRC11:31
*** egallen has quit IRC11:33
*** Daisy has quit IRC11:33
*** doug-fish has joined #openstack-meeting11:33
*** geoffarn_ has joined #openstack-meeting11:35
*** geoffarnold has quit IRC11:35
*** bobh has joined #openstack-meeting11:35
*** dprince has joined #openstack-meeting11:37
*** bobh has quit IRC11:40
*** jjmb has quit IRC11:40
*** stevemar has joined #openstack-meeting11:40
*** delattec has joined #openstack-meeting11:43
*** dewsday has joined #openstack-meeting11:43
*** asettle has quit IRC11:45
*** stevemar has quit IRC11:45
*** dewsday has quit IRC11:45
*** asettle has joined #openstack-meeting11:46
*** ozstacker_ has joined #openstack-meeting11:46
*** johnbelamaric has joined #openstack-meeting11:47
*** ozstacker has quit IRC11:48
*** ddieterly has quit IRC11:49
*** _amrith_ is now known as amrith11:49
*** ddieterly has joined #openstack-meeting11:49
*** delattec has quit IRC11:50
*** otter768 has joined #openstack-meeting11:52
*** cdelatte has joined #openstack-meeting11:53
*** delattec has joined #openstack-meeting11:53
*** ricolin has joined #openstack-meeting11:53
*** egallen has joined #openstack-meeting11:54
*** adahms has joined #openstack-meeting11:55
*** geoffarn_ has quit IRC11:56
*** geoffarnold has joined #openstack-meeting11:56
*** otter768 has quit IRC11:57
*** pnavarro has quit IRC11:57
*** egallen has quit IRC11:57
alex_xu#startmeeting nova api12:00
openstackMeeting started Tue Sep 29 12:00:30 2015 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: nova api)"12:00
openstackThe meeting name has been set to 'nova_api'12:00
alex_xuwho is here today?12:00
*** gmann_ has joined #openstack-meeting12:00
edleafeo/12:00
gmann_hi12:00
*** egallen has joined #openstack-meeting12:01
sdagueo/12:01
alex_xuhello12:01
alex_xuok, let's run the meeting12:01
alex_xu#topic actions from last meeting12:01
*** openstack changes topic to "actions from last meeting (Meeting topic: nova api)"12:01
alex_xualex_xu eliqiao check max length of hostname on linux and windows again12:01
alex_xuwe did that and patch merged12:02
alex_xu#link https://review.openstack.org/#/c/224438/12:02
alex_xualex_xu catch gmann about backport patch or work on it if have enough time12:02
alex_xuThanks to gmann work out the backport patch12:02
alex_xu#link https://review.openstack.org/22713512:02
alex_xui also work out another one12:02
alex_xu#link https://review.openstack.org/22877412:02
*** markvoelker has joined #openstack-meeting12:03
*** yamamoto has joined #openstack-meeting12:03
alex_xuhope everyone can review them, or I will catch up some stable branch core12:03
johnthetubaguyso all the stable patches will get a -2, until RC2 opens next tuesday12:03
sdagueI just +2ed from stable perspective12:03
johnthetubaguybut I like us getting those lined up ASAP12:03
sdaguejohnthetubaguy: this is kilo12:03
johnthetubaguyoh, my bad12:03
alex_xujohnthetubaguy: those are kilo12:03
johnthetubaguyis kilo out of its freeze?12:04
gmann_yea12:04
johnthetubaguyI should really pay more attention, and stop using my not on stable-core as an excuse12:04
alex_xujohnthetubaguy: there is freeze for kilo?12:04
johnthetubaguythere was a stable freeze at some point, while they cut a new release, or some such, its probably happened already12:05
alex_xuok, I can catch some stable-core to review them12:05
alex_xu#action alex_xu catch up stable-core review the api bug kilo back-port12:06
alex_xujohnthetubaguy contact the doc team to see what we can help on missing stuff in the doc12:06
johnthetubaguyyeah, so I failed to do that12:06
johnthetubaguybut, they do have the last patch up for that bug12:06
*** Kevin_Zheng has joined #openstack-meeting12:06
johnthetubaguyso I plan on taking a look at that, and see what more needs doing12:06
johnthetubaguy#link https://review.openstack.org/#/c/227672/12:06
alex_xujohnthetubaguy: ok, thanks12:07
johnthetubaguypart of me wants to remove v2, v2 extensions and v2.1 and just have a single doc for "compute API" that describes the details12:07
johnthetubaguybut lets talk about that later in the agenda12:07
gmann_johnthetubaguy: so they are updating wadl manually?12:07
edleafejohnthetubaguy: me too12:07
johnthetubaguygmann_: yes, basically12:07
*** markvoelker has quit IRC12:07
alex_xujohnthetubaguy: do you want another action?12:08
alex_xu#topic  API Concept Doc12:08
*** openstack changes topic to "API Concept Doc (Meeting topic: nova api)"12:08
* alex_xu jump the topic directly12:09
alex_xu#link https://review.openstack.org/22625312:09
johnthetubaguyalex_xu: thats fine, yeah, lets talk about it here12:09
*** ganeshna has quit IRC12:09
*** aarefiev has quit IRC12:09
johnthetubaguythanks for the update there12:09
alex_xuafter we merged that patch, we can add more doc on it12:10
alex_xujohnthetubaguy: np12:10
*** nadya has quit IRC12:10
johnthetubaguyyeah, feel free to hand patches off that change, I guess12:10
johnthetubaguywe should talk about those API reference docs12:11
johnthetubaguywhat do people think about just going to a single doc about the compute API, with a quick description about the extensions12:11
johnthetubaguyand versions12:11
*** pnavarro has joined #openstack-meeting12:11
alex_xulooks like, anyway v2.1 and v2 is equal except few things12:12
*** tfukushima has quit IRC12:12
johnthetubaguyI was thinking each bit could get required/related extensions: X, Y, Z and min_version: 2.6 or something like that?12:12
*** nisha has joined #openstack-meeting12:12
*** aarefiev has joined #openstack-meeting12:12
*** jckasper has quit IRC12:12
johnthetubaguythe problem is v2 is split into two, which kinda gives the wrong message, I feel12:12
*** yamamoto has quit IRC12:12
edleafeI think any docs moving forward should be about the current API. Then add a comment somewhere about legacy stuff12:12
sdaguehonestly, I like the idea of a unified document12:13
alex_xujohnthetubaguy: what means v2 split into two?12:13
johnthetubaguywell, I think we need the version history as it evolves12:13
edleafeThose docs should be separate so they can be removed when v2 goes away12:13
johnthetubaguyalex_xu: so I was super unclear, I really mean v2 vs v2 extensions, but I also mean those two and v2.112:13
gmann_johnthetubaguy: microversion as separate or embedded in same doc12:13
sdagueedleafe: right, except v2.1 and v2 are basically the same thing12:13
johnthetubaguyedleafe: v2 will never go away through really, thats the bit I like12:13
*** pm90_ has joined #openstack-meeting12:13
sdagueit was kind of the point :)12:14
johnthetubaguysdague: yeah, thats a better way of putting it12:14
edleafewell, true, except for extensions12:14
sdaguesure12:14
sdaguebut those bits can be called out12:14
johnthetubaguygmann_: I prefer embedded my self, but I think honestly the tooling will end up deciding that, I am really focusing about getting v2.1 base version accurate first12:14
*** tojuvone has joined #openstack-meeting12:14
johnthetubaguyyeah12:15
gmann_ok12:15
johnthetubaguyI was thinking we treat extensions and versions in a similar way12:15
johnthetubaguyfor this to be there in v2, you need to see extension XYZ, for v2.1 this needs version 2.6, or whatever it is12:15
gmann_but extension we can just remove as those are anyways deprecated..12:15
johnthetubaguyfor v1.1 its the same as v2, etc12:15
johnthetubaguygmann_: well its still in the API, technically, it just becomes less important12:16
edleafeI think we should always refer to v2 in the docs as 'legacy v2'12:16
johnthetubaguyedleafe: so there are two things here12:16
johnthetubaguyendpoint /v2.0 and the legacy v2 code base12:17
johnthetubaguythe docs for the API should not ever mention the code12:17
*** geoffarnold has quit IRC12:17
johnthetubaguywell, I don't really mean that, but hopefully that makes sense in some world12:17
*** aysyd has joined #openstack-meeting12:17
*** geoffarnold has joined #openstack-meeting12:18
edleafejohnthetubaguy: I was referring to the v2 API design, with extensions, etc.12:18
edleafenot the code base behind it12:18
*** dkranz has joined #openstack-meeting12:18
edleafebut in the same way we marked the code as legacy for devs, we refer to the API as legacy for consumers12:18
johnthetubaguyOK, so I call that v2.0 because thats not v2.1 so its spearate from the legacy v2 implementation, but maybe thats dumb12:18
johnthetubaguywell its not really legacy12:19
*** rossella_s has quit IRC12:19
johnthetubaguyits just an endpoint that is unlikely to ever die and will get no new features, hmm, so maybe it is12:19
johnthetubaguyanyways, I would rather they not have names as such12:19
edleafeto-may-to, to-mah-to :)12:19
*** rossella_s has joined #openstack-meeting12:19
sdagueso, I think this is consistent if we have 1 document, then with resources that were in the extension set in v2 we just comment it with "this used to be an extension in the API, not all cloud providers may have it enabled."12:20
johnthetubaguywe can reference the URLs more, so I hope thats clerer in the docs12:20
sdagueor something12:20
*** yamamoto has joined #openstack-meeting12:20
*** pm90_ has quit IRC12:20
johnthetubaguysdague: +112:20
*** pm90__ has joined #openstack-meeting12:20
johnthetubaguysdague: thats what I am attempting to say, badly12:20
sdaguebut, honestly, we should start with a holistic view and comment where it deviates12:20
johnthetubaguyyeah, I like us focusing on the base v2.1 version to start with12:20
sdagueand, also probably comment where things are defcore required elements12:20
gmann_+112:20
*** pm90__ has quit IRC12:20
johnthetubaguysdague: so the service catalog and it pointing to a version, do we have a transition plan sorted yet?12:21
*** raildo-afk is now known as raildo12:21
alex_xuwe are talking about the current wadl doc, or the future swagger generated doc?12:21
gmann_extension or core api, in some column like option/positional req param12:21
sdagueno, I'm chatting with stevemar in a couple of hours about some of the service catalog stuff going forward12:21
sdagueand have the summit as my deadline for proposals on all of this12:22
johnthetubaguyI like the idea of making a new endpoint, called os-compute (don't think any folks use that today) point at / so users know about the versions from the version list12:22
sdagueI've got some ideas about how it would work12:22
johnthetubaguysdague: cool, lets leave that alone for now then12:22
sdagueI feel like os- is overkill given that it's the openstack service catalog12:22
johnthetubaguyalex_xu: gmann_: I am really thinking about the current one, with a nod to swagger12:23
sdaguebut, I do get that we have a problem with existing values there12:23
*** vivek-ebay has joined #openstack-meeting12:23
johnthetubaguysdague: understood, I was just thinking about how to describe it in the API docs really12:23
johnthetubaguyso for swagger12:24
sdagueyeh, that's fair, I think it's just going to be a bit undefined for a bit12:24
*** weshay_xchat has joined #openstack-meeting12:24
johnthetubaguysdague: yeah, true12:24
alex_xujohnthetubaguy: I just was thing, if that doc generated from swagger, how to describe the little different between v2 and v2.112:24
johnthetubaguyswagger I think is likely to generate a new doc tree for each version12:24
sdaguethere must be some way to provide comments right?12:24
johnthetubaguyso we can create a v2.0 and v2.1 v2.2, etc12:24
*** delatte has joined #openstack-meeting12:24
alex_xusdague: yea, right12:24
*** weshay_xchat is now known as weshay12:24
johnthetubaguysdague: yeah, I think we just add the extension stuff as a comment in the v2.0 one12:25
*** Brian_shang has quit IRC12:25
alex_xuok, that may not a problem12:25
*** Brian_shang has joined #openstack-meeting12:25
johnthetubaguyit all seems OK-ish12:25
johnthetubaguyv1.1 can just redirect to v2.0, etc12:25
sdagueyeh, do we have some test bits out there to play with the swagger parts12:25
alex_xuok, so basically we are ok with unifed doc for v1.1, v2 and v2.1, right?12:25
johnthetubaguyfor the current version of the doc, yes12:26
alex_xucool12:26
johnthetubaguyfor swagger, I think they end up being the same page with multiple links, then we add changes in future ones for v2.2, etc12:26
alex_xu#info we hope to have unifed api ref doc for v1.1, v2 and v2.112:27
edleafeIs v1.1 still used anywhere?12:27
johnthetubaguyedleafe: its in our default install12:27
*** cdelatte has quit IRC12:27
*** mgrohar has joined #openstack-meeting12:27
johnthetubaguyit is just an alias for v2.012:27
edleafejohnthetubaguy: ugh12:27
gmann_also may be some dropdown thing for version etc.12:27
*** Daisy has joined #openstack-meeting12:27
johnthetubaguyv2.0 is the first version of our API, oddly12:27
*** delattec has quit IRC12:27
johnthetubaguy(well assuming you don't count the ec2 compat one)12:27
edleafejohnthetubaguy: Oh, I remember the history12:27
*** vivek-ebay has quit IRC12:28
johnthetubaguyyeah, just making sure we all agree really12:28
*** ganeshna has joined #openstack-meeting12:28
gmann_yup12:28
* bauzas waves again super late and lurks12:29
alex_xuyea12:29
johnthetubaguycool, seems like we have a bit of a docs plan forming there12:29
johnthetubaguyalex_xu: did you check to see if all the issues on your etherpad are fixed now12:29
alex_xujohnthetubaguy: not yet12:30
johnthetubaguyalex_xu: it looks like the api-site repo has been updated to fix all those12:30
johnthetubaguyalex_xu: is it OK to give you that action?12:30
*** rfolco has joined #openstack-meeting12:30
alex_xujohnthetubaguy: yea, it is ok for me12:30
*** Daisy has quit IRC12:30
johnthetubaguyI can take the action to attempt some doc unification, and see what folks think in the docs side of the house12:30
*** bswartz has quit IRC12:30
alex_xu#action alex_xu ceck to see if all the issues fixed on the v2.1 api doc12:30
alex_xu#action johnthetubaguy take a look at more about doc unification12:31
*** claudiub has joined #openstack-meeting12:31
alex_xuany more actions?12:32
alex_xuok, so let's move on12:32
johnthetubaguythat seems good, thank you12:32
alex_xu#topic Mitaka planning12:32
*** openstack changes topic to "Mitaka planning (Meeting topic: nova api)"12:32
alex_xu#link https://etherpad.openstack.org/p/nova-api-mitaka12:32
*** markvoelker has joined #openstack-meeting12:32
alex_xuI fill few items12:32
sdaguewhat bits of v3 are still out there?12:33
gmann_alex_xu: Thanks12:33
alex_xuplease feel free add more and more detail for each item12:33
johnthetubaguyso I have an idea of a possible focus area...12:33
alex_xusdague: we just deprecated, like APIRouterV3 still in the code, just left some cleanup work12:33
sdagueah, gotcha12:34
gmann_sdague: may be some v3 APIrouter and config options which we deprecated..12:34
gmann_yea12:34
johnthetubaguyah, yeah, thats good to do12:34
johnthetubaguyso my idea for focus is actually feature classification12:34
gmann_remove extension? are we planning to do in M?12:34
johnthetubaguyI have some notes on the idea here: https://review.openstack.org/#/c/215664/12:35
alex_xugmann_: I guess that need dicussion in summit12:35
gmann_alex_xu: ok12:35
sdaguejohnthetubaguy: sure, it feels like we should have a good docs story first12:35
sdaguebut that seems like part of the doc story12:35
johnthetubaguybasically feature classification would help us make sure we document and test everything we need12:35
johnthetubaguyyeah12:35
johnthetubaguybasically, its about joining up our CI tests, with tempest tests, and docs, so we know what features are "finished" for some definition of "finished"12:36
* alex_xu will take a look at that patch to get what is that12:36
*** dims_ has joined #openstack-meeting12:36
johnthetubaguyso we say this API is tested, and its documented here12:36
gmann_it looks interesting. i ll also look in detail tomorow12:37
johnthetubaguythe other side of this, is that we take a user focused look at the API12:37
johnthetubaguy(through the testing and docs work)12:37
johnthetubaguyand that will help us work out what needs urgent attention so we are more interoperable, etc12:37
johnthetubaguyand have a more usable API12:37
alex_xuprobably get, finish the coding, doc and test, then we can call it finished12:37
johnthetubaguythe task work looks like it might be getting attention, and could eventually impact the API usability12:38
*** spzala has joined #openstack-meeting12:38
johnthetubaguyalex_xu: thats pretty much it, along with "complete enough to be useful", should be in that doc12:38
*** geoffarnold has quit IRC12:38
*** yamamoto has quit IRC12:38
sdagueright, up until this point the api doc and testing has been playing catch up to the code12:39
alex_xujohnthetubaguy: ok12:39
gmann_johnthetubaguy: how about adding use case of API in doc. we will have those in spec12:39
sdagueand now we'd like to invert that a bit12:39
*** geoffarnold has joined #openstack-meeting12:39
edleafesdague: +112:39
johnthetubaguyyeah, at least, understanding the gaps, so people know what to work on12:39
gmann_sdague: yea12:39
*** MaxPC has joined #openstack-meeting12:40
johnthetubaguygmann_: totally needs the usecase in the docs, I am thinking about migrate vs evacuate, as an example12:40
*** dims has quit IRC12:40
johnthetubaguygmann_: probably in the concept docs, and linked, but thats fine, all part of the story12:40
gmann_yea12:40
johnthetubaguyso, there is another idea that follow on from this...12:41
gmann_and also link to spec too..12:41
johnthetubaguymarking an API as experimental, until its fully tested and documenting, so its possible it would be removed, until that is complete12:41
johnthetubaguybut I know that has problems12:42
alex_xusounds like we want to introduce 'experimental' back again12:42
*** amotoki has quit IRC12:42
sdaguehonestly, I don't think experimental works12:42
johnthetubaguywell, thats a separate conversation, but I think it would help make sure we get docs added, it would be nice to avoid that though12:43
johnthetubaguysdague: so now we have depends on, maybe we just don't need that12:43
sdaguebut we do need a way to mark up which bits are tested and documented12:43
*** gampel has joined #openstack-meeting12:44
johnthetubaguyyeah, anyways, something to think about12:44
johnthetubaguyits the need to remove something if its never tested that worries me really, never been able to do that in the API12:44
johnthetubaguyanyways, I think a docs focus is needed, as we didn't manage it this cycle12:44
sdagueright12:45
gmann_yea12:45
johnthetubaguyfeature classification I think would help organise that effort somewhat (and leave us with handy docs for our users)12:45
*** amrith is now known as _amrith_12:45
johnthetubaguy(PS it needs a better name!)12:45
*** neelashah has joined #openstack-meeting12:45
bauzasfeature classification ?12:45
johnthetubaguyyeah12:45
johnthetubaguyanyways, lets not go there right now12:46
alex_xuok12:46
bauzasjohnthetubaguy: okay, let's discuss that off-topic12:46
*** ganeshna has quit IRC12:47
alex_xuso I think we needn't discussion each item in the etherpad today? when people think about more and fill more detail, then we can dicussion each item more in next few meetings, is that ok?12:47
sdagueif we set the goal as a solid API guide for mitaka release day, I think we'll all be really happy12:47
johnthetubaguy+112:47
johnthetubaguyhonestly, everything else is optional12:47
*** oomichi_ has joined #openstack-meeting12:47
alex_xuheh yea12:47
gmann_yea +1 :)12:48
johnthetubaguyreally, I would love us to do no more API work until we have the docs done (mins the odd features folks push in)12:48
*** ganeshna has joined #openstack-meeting12:48
*** Administrator has joined #openstack-meeting12:48
*** Administrator is now known as Guest4563612:48
*** xyang1 has joined #openstack-meeting12:48
johnthetubaguyI think JSON home is great, its just docs are more important right now (we might end up needing that for the docs, but thats a different thing)12:48
johnthetubaguywhat do people think?12:49
*** dkranz has quit IRC12:49
sdague+112:49
*** hashar has joined #openstack-meeting12:49
johnthetubaguyI know its not very exciting, but our users need this to happen12:49
gmann_johnthetubaguy: yea, we can add providing the req response scheme there12:49
sdagueyeh, it should be possible to write an application to Nova without reading the nova source code12:50
oomichi_johnthetubaguy: +1 for doc. but I love still json-home12:50
sdaguetoday I don't think that's possible12:50
johnthetubaguysdague: very well put12:50
edleafeyeah, docs are the biggest need by far12:50
alex_xuok, looks like we all agree on the doc is important12:51
johnthetubaguythat means we don't do json home till its done, which hurts, but I think its the right call12:51
oomichi_I hope the doc is auto-generated without human's hands as possible12:51
alex_xuoomichi_: yea12:52
johnthetubaguyoomichi_: we need real concept docs first12:52
johnthetubaguythe hard stuff12:52
oomichi_johnthetubaguy: +1 for the concept fist12:52
oomichi_s/fist/first/12:52
johnthetubaguyideally we make sure swagger can do the right thing for us too12:52
johnthetubaguyoomichi_: you still going to get that prototype ready for the summit?12:53
oomichi_yeah, I am trying now.12:53
gmann_johnthetubaguy: from json-home user can know the available features supported by cloud12:53
*** dims_ has quit IRC12:53
sdaguegmann_: sure, but unless they understand what those features mean, it's not super useful12:53
alex_xuI'm also taking look at also12:53
gmann_which will be runtime dicovery12:53
johnthetubaguygmann_: there are a whole heap of issues making that real, sadly (policy mostly), and yes, docs are more important right now12:53
sdagueI do get that's part of the discovery story12:53
*** thangp has joined #openstack-meeting12:54
gmann_sdague: ye, totally agree after doc, we can do that stuff12:54
johnthetubaguygmann_: so docs will take all of us all cycle, I suspect12:54
johnthetubaguythey are hard12:54
oomichi_I tolk about it with mtreinish at qa-meetup, and it is fine to include it in tempest12:54
sdagueand, as johnthetubaguy said, there is this whole story around policy that needs sorted12:54
johnthetubaguyso, the auto generation stuff12:54
johnthetubaguyrequest validation stuff gives us the requests I guess?12:54
gmann_hummm, yea. +1 after doc fix.12:54
johnthetubaguywe have the API sample generation semi-auto stuff, does that get us all the responses already?12:55
sdaguethey are in slightly incompatible formats12:55
sdaguesome way to unify all that would be good12:56
johnthetubaguyso my head is thinking... auto generate from code the docs, use those docs to test the API12:56
johnthetubaguyoomichi_: are you things going that way?12:57
* alex_xu warn the time is close12:57
oomichi_we will be able to generate api doc from json-schema for response/request12:57
*** bswartz has joined #openstack-meeting12:57
oomichi_if migrating json-schema of response from tempest into nova12:57
alex_xu2 mins left12:58
oomichi_I will explain it later on openstack-nova12:58
gmann_yea, that's the final plan to have response one also in nova tree12:58
*** Daisy has joined #openstack-meeting12:58
gmann_as discussed in last summit..12:58
alex_xuone more thing12:58
alex_xuI will begin public vacation from tomorrow, will back until next Thursday. Appreciate if anyone can running the meeting next week.12:59
sdaguealex_xu: I can run it12:59
alex_xusdague: thanks a lot12:59
sdagueenjoy your vacation12:59
alex_xusdague: thanks12:59
alex_xuso let's move the discussion to openstack-nova12:59
alex_xulet's close the meeting, thanks all!12:59
alex_xu#endmeeting12:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:59
gmann_Thanks all12:59
openstackMeeting ended Tue Sep 29 12:59:57 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-09-29-12.00.html12:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-09-29-12.00.txt13:00
oomichi_alex_xu: thanks for leading13:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-09-29-12.00.log.html13:00
*** geoffarnold has quit IRC13:00
alex_xuoomichi_: np13:00
johnthetubaguyalex_xu: have a good break, you have worked crazy hard recently!13:00
alex_xujohnthetubaguy: thanks :)13:00
*** geoffarnold has joined #openstack-meeting13:00
*** Qiming_ has joined #openstack-meeting13:00
*** salv-orlando has quit IRC13:01
Qiming_#startmeeting senlin13:01
openstackMeeting started Tue Sep 29 13:01:10 2015 UTC and is due to finish in 60 minutes.  The chair is Qiming_. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: senlin)"13:01
openstackThe meeting name has been set to 'senlin'13:01
*** Qiming_ is now known as Qiming13:01
*** Guest45636 is now known as yanyanhu13:01
yanyanhuhello13:01
*** dims has joined #openstack-meeting13:01
*** gmann_ has quit IRC13:01
yanyanhuI thought you were still in another meeting :)13:01
Qimingyep, was talking to TOSCA guys13:02
*** haiwei has joined #openstack-meeting13:02
yanyanhunice13:02
haiweihi13:02
*** sudipto has quit IRC13:02
*** neeti has quit IRC13:02
haiweiwhat is nice?13:02
*** jruano has joined #openstack-meeting13:02
*** tojuvone has left #openstack-meeting13:02
Qimingtime for adding things to the agenda13:02
Qiminghttps://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Weekly_Senlin_.28Clustering.29_meeting13:03
*** rtheis has quit IRC13:03
jruanohello13:03
yanyanhuhaiwei, about meeting with tosca team :)13:03
Qiminghello, jruano13:03
*** rtheis has joined #openstack-meeting13:03
yanyanhuhi, jruano13:03
*** bvandenh has quit IRC13:03
*** ildikov has quit IRC13:03
haiweioh, nice13:04
jruanoi have a design session setup for tomorrow morning. can meet in irc, and i will share the call info13:04
*** bvandenh has joined #openstack-meeting13:04
*** ddieterly has quit IRC13:04
yanyanhuthanks, jruano13:04
*** jckasper has joined #openstack-meeting13:04
jruanoone hour before this time tomorrow so i think 1200 UTC13:04
jruanowe will do an overview on tosca and the vision we see for collaboration with senlin13:05
*** VW has joined #openstack-meeting13:05
Qimingjruano, there is a call in number?13:05
jruanothere is, one sec13:06
jruanohttps://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=81307605&accessNumber=2158616239#C213:07
jruanopasscode: 8130760513:07
*** kencjohnston has joined #openstack-meeting13:07
*** hrou has joined #openstack-meeting13:07
jruanoill be on irc if anyone has any issues getting in13:07
*** dan-t has joined #openstack-meeting13:08
Qiminggreat13:08
Qiming#topic container cluster13:08
Qimingwe have got some updates from the SUR team: https://github.com/eshijia/Open-SUR13:09
*** trozet has quit IRC13:09
Qimingthe team has been documenting their progresses here13:09
QimingI've suggested them to move it to etherpad, will share with you the link when we have something new13:09
*** iben_ has joined #openstack-meeting13:09
*** annegentle has joined #openstack-meeting13:11
Qimingnetwork very unstable these days, and Notes is not responding13:11
*** dan-t has quit IRC13:11
*** kencjohnston_ has joined #openstack-meeting13:11
Qimingjruano, do you still have bandwidth to work on this topic?13:12
*** kencjohnston has quit IRC13:12
*** DericHorn-HP has joined #openstack-meeting13:12
jruanoi do. we've been talking on the side with ton, and he invited me to the meeting this week. i've been working on standing up a coreos cluster13:12
*** delatte has quit IRC13:13
jruanoi will show up for the meetings and start working on items13:13
Qimingokay, will get you into the circle then13:13
*** nisha_ has joined #openstack-meeting13:13
*** dan-t has joined #openstack-meeting13:13
Qiminghope we can get something up running in coming days13:13
Qiming#topic trigger implementation13:14
*** dan-t has left #openstack-meeting13:14
QimingOur trigger type implementation, the ceilometer alarm one, has to be based on the new alarming service -- aodh13:14
QimingI have proposed a change to openstacksdk here: https://review.openstack.org/#/c/226689/13:15
Qiminghope it will be accepted soon, the recent progress at the sdk side is really slow13:16
*** nisha has quit IRC13:16
yanyanhucool, and I saw gordon's comment13:16
Qiminghowever, we can still use the existing telemetry service (as an experiement)13:17
QimingI will proceed at senlin side at the same time, so that we won't be blocked by this change13:17
yanyanhuyes, at least for now before the alarm related code is removed from ceilometer completely13:18
yanyanhuok13:18
Qimingthere are some redirection logic in ceilometerclient and ceilometer server13:18
yanyanhuI think the patch in ceilometer for alarm spliting is now blocked temporarily?13:18
Qimingguess what, aodh will have its own client, according to gordon13:18
yanyanhuok...13:19
yanyanhuwhen will it be available?13:19
Qimingdon't know13:19
jruanoman i thought this service was supposed to be transparent13:19
*** tomoe__ has quit IRC13:19
Qimingbut we as REST api users don't care that much about the aodhclient thing13:19
yanyanhujruano, it will be not I guess...13:19
yanyanhuQiming, yes13:20
Qimingsince ethan is on vacation13:20
Qimingwe have to skip the heat resource type support topic13:20
yanyanhuactually IMO, letting alarm become an individual service in openstack might be a good idea13:21
yanyanhuok13:21
Qimingwe resume the discussion with him when he is back13:21
*** obedmr has joined #openstack-meeting13:21
Qiming#topic big tent proposal13:21
Qimingsince the Mitaka development has started13:22
QimingI'm thinking maybe it's time for us to propose senlin into the big tent13:22
*** tfukushima has joined #openstack-meeting13:22
yanyanhuagree with this13:22
*** hashar has quit IRC13:23
QimingI've been browsing through the previous reviews about getting projects accepted into big tent13:23
*** jdurgin1 has joined #openstack-meeting13:23
haiwei+113:23
*** bltavares has joined #openstack-meeting13:23
Qimingwe need to start drafting something for the TC to review13:23
Qimingand get prepared for questions13:24
yanyanhuyes, lots of homework need to be done I think13:24
Qimingfirst things first, we still need to make the service stable and usable13:24
Qimingor else, it means nothing to wear a new hat13:24
yanyanhuyes13:24
jruanoagreed13:24
QimingI do believe we are almost there, so let's have a try13:25
*** bill_az has joined #openstack-meeting13:25
QimingI'll start working on this in the coming days, and send out a draft for everyone to review13:25
yanyanhu\o/13:25
yanyanhuthanks13:25
haiweiok13:26
Qimingas a first step, we have had senlinclient released13:26
Qimingso that senlin-dashboard doesn't have to pull things from git directly13:26
yanyanhuit works well I think13:26
Qimingnow we are proposing senlinclient into the global requirements13:27
Qiminghttps://review.openstack.org/#/c/227158/13:27
*** doug-fish has quit IRC13:27
*** Daisy has quit IRC13:27
Qimingthe big red cross there is because the requirements is frozen for Liberty release13:27
Qimingnot a big deal13:28
*** doug-fish has joined #openstack-meeting13:28
yanyanhuyep :)13:28
Qimingthe global namespace switching is scheduled on Oct 17th, IIRC13:29
*** ddieterly has joined #openstack-meeting13:29
Qimingso, for us, it's time to start planning for Mitaka13:30
yanyanhumaybe we should clean those opened patches before that?13:30
Qimingyes13:30
*** hashar has joined #openstack-meeting13:30
*** salv-orlando has joined #openstack-meeting13:31
Qimingplease spend some time review our mitaka work items13:31
Qiminghttps://etherpad.openstack.org/p/senlin-mitaka-workitems13:31
Qimingsee if something is missing13:32
yanyanhusure13:32
Qimingadd comments if you think something is more important than others13:32
*** oomichi_ has quit IRC13:32
*** ddieterly has quit IRC13:33
Qiming#topic open discussions13:33
*** pradk has joined #openstack-meeting13:33
*** ddieterl_ has joined #openstack-meeting13:33
Qiminganything you want to discuss?13:33
yanyanhuabout joining the summit13:33
*** banix has joined #openstack-meeting13:33
Qimingright13:34
yanyanhuso Qiming I think we two have decieded to join13:34
Qimingjruano, are you coming?13:34
Qimingor matt?13:34
*** kencjohnston_ has quit IRC13:34
jruanoi will be there13:34
*** stevemar has joined #openstack-meeting13:34
yanyanhucool!13:34
*** kencjohnston has joined #openstack-meeting13:35
haiweii should be there, not 100% though13:35
Qimingokay, Sandy told me that he will send 4 or more people there for a meeting13:35
yanyanhuyou're so close to the meeting site ...13:35
*** skraynev has quit IRC13:35
Qimingwe may need to schedule a meetup13:35
haiweiyes : )13:35
jruanonone of my proposals got accepted, so ill be there mostly for learning and participating in design sessions13:35
yanyanhuabsolutely13:35
jruanoyes we should13:35
*** stevemar_ has joined #openstack-meeting13:36
Qimingwe will share with people our vision, plan13:36
*** haomaiwang has joined #openstack-meeting13:36
*** skraynev has joined #openstack-meeting13:36
Qimingand we will be all ears to all kinds of suggestions/comments13:37
QimingI'll ask around how to book a place there13:37
*** stevemar_ has quit IRC13:37
*** stevemar_ has joined #openstack-meeting13:38
Qiminganything else?13:38
yanyanhunope from me13:38
Qimingjust got one thing, haiwei13:38
*** stevemar has quit IRC13:39
haiweiyes?13:39
QimingI checked your patch on deletion-policy, for resize operation13:39
Qimingthe logic is incorrect, IMO13:39
*** ildikov has joined #openstack-meeting13:39
haiweiI also saw yanyan's comment13:39
Qimingwe don't reference to any specific policy from within an action13:39
haiweiI tried to do it like other actions13:39
*** haomaiwang has quit IRC13:40
yanyanhuyes, if you have any question about how it works, we can have a discussion about it13:40
Qimingokay, cool, ping us when you got things to discuss13:40
*** dane_leblanc has joined #openstack-meeting13:40
*** haomaiwa_ has joined #openstack-meeting13:40
haiweiin fact i just submit it to get suggestions from you13:40
*** lblanchard has joined #openstack-meeting13:40
*** banix has quit IRC13:41
Qiming...13:41
haiweiI will think about it again from yanyan's comment13:41
yanyanhu:)13:41
Qimingthen you may want to label it a WIP next time, :)13:41
Qimingthanks13:41
Qimingnothing else from my side13:41
*** jmckind has joined #openstack-meeting13:41
haiweiI just not sure about it :)13:42
yanyanhume neither13:42
*** MaxPC has quit IRC13:42
haiweinone from me13:42
Qimingokay, thanks for joining13:42
Qimingtill next week, guys13:42
Qiming#endmeeting13:42
haiweise e u13:42
*** cdash has joined #openstack-meeting13:43
yanyanhuhi, Qiming I think you need to reset you nickname to end the meeting13:43
yanyanhuto Qiming_13:43
*** Qiming is now known as Qiming_13:43
*** yamamoto has joined #openstack-meeting13:43
*** yamamoto has quit IRC13:43
Qiming_#endmeeting13:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:43
openstackMeeting ended Tue Sep 29 13:43:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-09-29-13.01.html13:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-09-29-13.01.txt13:43
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-09-29-13.01.log.html13:43
*** doug-fish has quit IRC13:43
Qiming_thanks, learned something new, :)13:43
*** MaxPC has joined #openstack-meeting13:43
*** geoffarnold has quit IRC13:44
yanyanhu:)13:44
*** jaypipes has quit IRC13:44
*** cdash has left #openstack-meeting13:45
*** cdelatte has joined #openstack-meeting13:46
*** delattec has joined #openstack-meeting13:46
*** mdbooth_ has joined #openstack-meeting13:46
*** haiwei has quit IRC13:46
*** yanyanhu has quit IRC13:47
*** jaypipes has joined #openstack-meeting13:49
*** mdbooth has quit IRC13:49
*** mdbooth_ is now known as mdbooth13:49
*** erlon has joined #openstack-meeting13:50
*** wbhuber has joined #openstack-meeting13:50
*** ccavanna has joined #openstack-meeting13:50
*** johnbelamaric has left #openstack-meeting13:50
*** mgrohar has quit IRC13:50
*** DericHorn-HP has quit IRC13:50
*** mgrohar has joined #openstack-meeting13:51
*** DericHorn-HP has joined #openstack-meeting13:52
*** balajiiyer has joined #openstack-meeting13:52
*** otter768 has joined #openstack-meeting13:52
*** jruano has quit IRC13:53
*** okrieg has joined #openstack-meeting13:53
*** qwebirc70488 has joined #openstack-meeting13:54
*** stevemar_ is now known as stevemar13:54
*** irenab has quit IRC13:54
*** vjay11 has joined #openstack-meeting13:56
*** otter768 has quit IRC13:57
*** pm90_ has joined #openstack-meeting13:58
*** qwebirc70488 has quit IRC13:58
*** okrieg has quit IRC13:58
*** lazy_prince has joined #openstack-meeting14:00
*** haomaiwa_ has quit IRC14:01
*** haomaiwa_ has joined #openstack-meeting14:01
*** bryan_att has joined #openstack-meeting14:01
*** nisha_ has quit IRC14:02
*** spotz_zzz is now known as spotz14:02
*** killer_prince has quit IRC14:02
*** annegentle has quit IRC14:03
*** okrieg has joined #openstack-meeting14:04
*** ayoung has joined #openstack-meeting14:05
*** _amrith_ is now known as amrith14:05
*** eharney has quit IRC14:06
*** cdub has joined #openstack-meeting14:07
*** jungleboyj has joined #openstack-meeting14:08
*** sigmavirus24_awa is now known as sigmavirus2414:10
*** DericHorn-HP has quit IRC14:10
*** vikram__ has joined #openstack-meeting14:11
*** trozet has joined #openstack-meeting14:12
*** achanda has joined #openstack-meeting14:15
*** jmckind_ has joined #openstack-meeting14:15
*** vijendar has joined #openstack-meeting14:17
*** galstrom_zzz is now known as galstrom14:17
*** Leom has joined #openstack-meeting14:18
*** jmckind has quit IRC14:18
*** thangp has quit IRC14:19
*** rfolco has quit IRC14:19
*** MarkAtwood has quit IRC14:19
*** rfolco has joined #openstack-meeting14:19
*** jmckind_ has quit IRC14:21
*** thangp has joined #openstack-meeting14:21
*** jmckind has joined #openstack-meeting14:21
*** achanda has quit IRC14:22
*** summer has joined #openstack-meeting14:23
*** nisha has joined #openstack-meeting14:24
*** vivek-ebay has joined #openstack-meeting14:24
*** julim has quit IRC14:25
*** changzhi has joined #openstack-meeting14:25
*** Murali has quit IRC14:25
*** changbl has joined #openstack-meeting14:25
*** xingchao has joined #openstack-meeting14:25
*** geoffarnold has joined #openstack-meeting14:26
*** dkranz has joined #openstack-meeting14:27
*** maishsk has joined #openstack-meeting14:28
*** vivek-ebay has quit IRC14:29
*** wznoinsk has quit IRC14:29
*** asettle has quit IRC14:29
*** annegentle has joined #openstack-meeting14:29
*** julim has joined #openstack-meeting14:30
*** julim has quit IRC14:30
*** julim has joined #openstack-meeting14:31
*** julim has quit IRC14:32
*** edtubill has joined #openstack-meeting14:32
*** nadya has joined #openstack-meeting14:32
*** julim has joined #openstack-meeting14:33
*** topol has joined #openstack-meeting14:34
*** bobh has joined #openstack-meeting14:36
*** juzuluag has joined #openstack-meeting14:37
*** geoffarnold has quit IRC14:38
*** salv-orlando has quit IRC14:39
*** jorge_munoz has quit IRC14:39
*** iben has joined #openstack-meeting14:41
*** banix has joined #openstack-meeting14:41
*** vjay11 has quit IRC14:42
*** su_zhang has joined #openstack-meeting14:43
*** electrocucaracha has joined #openstack-meeting14:43
*** yamamoto has joined #openstack-meeting14:43
*** yamamoto has quit IRC14:44
*** yamamoto has joined #openstack-meeting14:44
*** electrocucaracha has quit IRC14:44
*** electrocucaracha has joined #openstack-meeting14:45
*** toscalix__ has quit IRC14:45
*** berendt has quit IRC14:45
*** rfolco has quit IRC14:45
*** wznoinsk has joined #openstack-meeting14:46
*** rfolco has joined #openstack-meeting14:47
*** toscalix__ has joined #openstack-meeting14:47
*** vmb_out is now known as vmbrasseur14:47
*** mtanino has joined #openstack-meeting14:47
*** changzhi has quit IRC14:48
*** achanda has joined #openstack-meeting14:51
*** armax has joined #openstack-meeting14:51
*** mrmartin has quit IRC14:51
*** vgridnev has quit IRC14:52
*** vgridnev has joined #openstack-meeting14:52
kevinbentonarmax: drivers meeting here in 7 mins?14:53
*** mgrohar has quit IRC14:53
*** salv-orlando has joined #openstack-meeting14:54
*** ayoung has quit IRC14:54
*** bltavares has quit IRC14:54
*** bltavare_ has joined #openstack-meeting14:54
*** tosky has joined #openstack-meeting14:54
armaxkevinbenton: I have a conflict14:55
armaxif mestery wants to run it this time round that’d be great, otherwise I must apologize and cancel it14:55
kevinbentonarmax: resolve the conflict and then use "git add" to mark it as such. then you can use "git rebase --continue"14:55
* mestery is here14:55
armaxI haven’t yet reviewed my calendar t14:55
mesterykevinbenton: Good idea14:56
mesterykevinbenton: Shall we have a quick meeting?14:56
*** ujuc has joined #openstack-meeting14:56
kevinbentonmestery: sure, i don't know who is around and don't have anything too useful to discuss yet14:56
mesterykevinbenton: Aye aye, lets just wing it if armax is ok with us doing this.14:56
dougwigO/14:57
kevinbentondougwig: PING14:57
kevinbentonok14:57
kevinbentonpreempted me14:57
kevinbenton:)14:57
armaxmestery: please go ahead, I’ll catch up on the meeting notes14:57
mestery#startmeeting neutron-drivers14:57
openstackMeeting started Tue Sep 29 14:57:43 2015 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.14:57
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:57
*** irenab has joined #openstack-meeting14:57
*** openstack changes topic to " (Meeting topic: neutron-drivers)"14:57
openstackThe meeting name has been set to 'neutron_drivers'14:57
armaxthanks for stepping in14:57
mestery#link https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda Agenda14:57
mesteryarmax: Anytime :)14:57
mestery#info I'm running this meeting at the behest of our fearless leader armax :)14:58
armaxI’ll clear my calendar from next week onward14:58
mesteryarmax: ACk14:58
armaxmestery: ruthless is more appropriate14:58
mestery#topic Spec review14:58
*** Tango has joined #openstack-meeting14:58
*** openstack changes topic to "Spec review (Meeting topic: neutron-drivers)"14:58
mestery#undo14:58
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x9990fd0>14:58
mestery#topic RFE Bug Review14:58
*** openstack changes topic to "RFE Bug Review (Meeting topic: neutron-drivers)"14:58
*** ttrifonov is now known as zz_ttrifonov14:58
mesterydougwig: https://review.openstack.org/#/c/202797/14:58
mestery#link https://review.openstack.org/#/c/202797/14:58
mesterydougwig: That needs a re-spin.14:59
*** annegentle has quit IRC14:59
*** achanda has quit IRC14:59
*** lazy_prince has quit IRC14:59
dougwigyou guys started early!14:59
mestery#link https://goo.gl/xtBJkU Open RFE bugs14:59
mesterydougwig: I know, right? :)14:59
*** annegentle has joined #openstack-meeting15:00
dougwigcomputer is still waking up/loading.15:00
mesterydougwig: Ack15:00
* mestery waits and hands kevinbenton some coffee15:00
kevinbentonmestery: major fopaux15:00
kevinbentonmestery: it's 5 pm where i'm at, no coffee needed15:00
mesterykevinbenton: I forget, you're in the land of salv-orlando's!15:00
kevinbentonmestery: give mine to dougwig15:00
mesterykevinbenton: He likes red bull, not coffee.15:00
*** haomaiwa_ has quit IRC15:01
dougwigi assume we did the pre-topic of making sure armax still wants a drivers team?  :)15:01
mesterydougwig: I did that offline :)15:01
salv-orlandohe might be but this does not mean I'm supposed to be working now15:01
*** sbelous has quit IRC15:01
mesteryBut yeah, I think he's ok with it.15:01
*** carl_baldwin has joined #openstack-meeting15:01
kevinbentonthe drivers team is at risk? quick, make a bunch of rash decisions that cannot be reversed15:01
*** haomaiwang has joined #openstack-meeting15:01
dougwigmestery: ack, will respin rfe and infra devrefs15:01
mesterysalv-orlando: Isn't it happy hour where you are?15:01
mesterydougwig: Coolio!15:01
* carl_baldwin wanders in15:02
*** bltavare_ has quit IRC15:02
mesteryOK15:02
*** bltavares has joined #openstack-meeting15:02
mesteryLets look at the link here: https://goo.gl/xtBJkU15:02
mestery23 bugs in that list15:02
mesteryHowever15:02
mesteryLets take a pause15:02
mesteryI think we need to do a post mortem on this RFE process15:02
dougwigyikes15:02
mesteryWhat do others think?15:02
*** pm90__ has joined #openstack-meeting15:03
dougwigit's fine, if we review regularly. i liked -specs better, just because the tooling is better around queueing my workflow, but... eh.15:03
mesterydougwig: Ack on all of that15:03
kevinbentoni liked the lightweightness of the rfe15:03
*** Piet_ has quit IRC15:03
*** pm90___ has joined #openstack-meeting15:03
mesterykevinbenton: ++15:04
kevinbentonjust having it in launchpad made it easy to forget about15:04
mesteryyup15:04
*** dims has quit IRC15:04
carl_baldwin++15:04
dougwig+115:04
mesteryOK, lets discuss with armax to get his viewpoints later as well. Lets move forward with RFE review!15:04
mesteryI'll link them here15:04
mesteryAnd we can discuss one at a time. Sound good?15:04
kevinbentonsgtm15:04
*** pm90_ has quit IRC15:04
mesteryFirst up15:05
mestery#link https://bugs.launchpad.net/neutron/+bug/147579215:05
openstackLaunchpad bug 1475792 in neutron "Change Neutron so that it can auto-allocate networks" [High,Confirmed] - Assigned to Brian Haley (brian-haley)15:05
*** vgridnev has quit IRC15:05
mestery"Get Me a Network" now15:05
dougwigi thought the first was the get me a network api.  either auto-select or auto-allocate, if it's unambiguous.15:05
mesteryI'm going to mark it triaged so work can begin.15:05
mesteryAnyone disagree?15:05
carl_baldwinagree15:06
kevinbentoni'm +1 for this one, that port scheduler thing i suggested would be a big component of this15:06
*** n0ano has joined #openstack-meeting15:06
kevinbentonmight be worth collapsing it into this15:06
mesterykevinbenton: Ack, for now, Triaged, lets collapse at a future date.15:06
mesteryUp next15:06
mestery#link https://bugs.launchpad.net/neutron/+bug/137003315:07
openstackLaunchpad bug 1370033 in neutron "Admin should be able to manually select the active instance of a HA router" [Low,Confirmed] - Assigned to yong sheng gong (gongysh)15:07
*** tosky has left #openstack-meeting15:07
*** IlyaG has joined #openstack-meeting15:07
*** pm90__ has quit IRC15:07
dougwigthat's a useful sanity mechanism in a prod environment.15:08
mesteryLooks like this one needs API changes15:08
mesteryBut useful for sure, agree with dougwig15:08
kevinbentoni'm okay with this one. next step is spec filing then?15:08
mesterykevinbenton: Yes, since it requires an API change15:08
mesteryWe'll need a spec.15:08
dougwigkevinbenton: only if we need a spec. is it an obvious enough change?15:08
mesterydougwig: API changes require specs, right?15:08
carl_baldwinA spec with a small API section filled out should do it.  The API change won’t be big.15:09
*** ayoung has joined #openstack-meeting15:09
mesteryDone15:09
mesteryNext15:09
*** amotoki has joined #openstack-meeting15:10
mestery#link https://bugs.launchpad.net/neutron/+bug/147571715:10
openstackLaunchpad bug 1475717 in neutron "RFE: Security Rules should support VRRP protocol" [Wishlist,New] - Assigned to Li Ma (nick-ma-z)15:10
*** hemnafk is now known as hemna15:10
mesterySeems simple enough15:10
dougwigmestery: i thought we didn't need specs if it was obvious, like adding a boolean field.  rfe + code is pretty explanatory in a case like that.  spec is always fine, though.15:10
mesterydougwig: For this one?15:11
kevinbentoni'm confused about the comments on that bug15:11
dougwigmestery: no, i was one back.15:11
kevinbentonit sounds like they found a way to do it without it?15:11
*** changbl has quit IRC15:11
mesterydougwig: Right, but for API changes, I think we want it so it gets more review? Maybe I'm wrong.15:11
dougwigon the vrrp/sg one, my only question is should we be adding protocols piecemeal, or allow them all?15:11
*** IlyaG has quit IRC15:11
amotokihi15:11
dougwigmestery: just my personal opinion, specs on trivial things are a waste of time, so i'd say no.15:11
mesterydougwig: Comment in bug, fine by me, I agree, KISS15:12
mesterySo15:12
mesteryFor this VRRP one15:12
*** ajmiller has joined #openstack-meeting15:12
mesterykevinbenton: It does work, it's just more user friendly to include the canonical VRRP name in the dropdown15:12
mesteryTo me, I'd be fine approving this one15:12
mesteryIt's simple and makes things user friendly15:12
dougwigdo we want to do just vrrp?  what about gre, ipsec, ....?15:12
*** vgridnev has joined #openstack-meeting15:13
kevinbentonwould this even be a change on the server side or just to allow the client to accept the simple names?15:13
mesterydougwig: Agreed15:13
dougwigor let 'all' pass more than tcp/udp.15:13
*** jorge_munoz has joined #openstack-meeting15:13
mesterykevinbenton: https://review.openstack.org/#/c/203173/15:13
*** ajmiller_ has quit IRC15:14
kevinbentonmestery: i see. i'm thinking we should probably just populate them all in one fell swoop then15:14
amotokiat now I don't know it affects ip_protocol or protocol number (perhaps ip proto), but I agree we support more values.15:14
mesterykevinbenton: Comment in the bug then?15:14
*** nisha has quit IRC15:14
kevinbentonmestery: it's not that much extra work15:14
kevinbentonmestery: sure15:14
salv-orlandocan I point out that since this is expanding the security feature, we need to consider that some bakcends which are not the ref impl might not support that15:14
salv-orlandoor need to implement support for that15:14
kevinbentonsalv-orlando: !15:14
salv-orlandoand that should be dealt with by the mgmt layer15:14
mesterysalv-orlando: We consider other backends? Since when? ;)15:15
kevinbentonsalv-orlando: but they would have this issue now15:15
kevinbentonsalv-orlando: just by using the proto number instead of name, right?15:15
salv-orlandomestery: since we have OVN. Before that we did mot give a damm ;)15:15
mesteryrofl15:15
mesteryIt would seem this isn't as cut and dried as we'd like it to be then15:15
carl_baldwinThis work is just assigning names to numbers, right?15:15
salv-orlandothe backend would yes. It's a matter of expectations on the user side. I don't care about backends either.15:16
*** dims__ has joined #openstack-meeting15:16
mesterycarl_baldwin: Correct15:16
*** haomai___ has joined #openstack-meeting15:16
salv-orlandoIf you tell users that VRRP is a valid protocol and then the server returns a nice 500 when you try to specify it, that's not nice15:16
*** sudipto has joined #openstack-meeting15:16
dougwigi care about them, but i'm not going to let it stop us from expanding the interface.15:16
kevinbentonsalv-orlando: do these show up in an API listing somewhere?15:16
amotokidilemma between consistent supported values and backend support....15:16
*** kebray has joined #openstack-meeting15:17
*** pm90___ has quit IRC15:17
salv-orlandoI think it's ok to approve the RFE anyway15:17
amotokiIf users can know supported values via API, it sounds good.15:17
salv-orlandothe blueprint is about symbolic names at the end of the day no need to start a bikeshedding session15:17
*** numans has quit IRC15:17
kevinbentonwhere do these show up? I thought it was just a translation thing15:17
salv-orlandowe can look at how to deal with unsupported protocols separately. It should be trivial anywya.15:18
salv-orlandowe can move on I guess. I've already wasted too much of your time.15:18
*** BharatK has quit IRC15:18
*** haomaiwang has quit IRC15:18
salv-orlandoMy comment was out of place and I regret having made it.15:19
mesteryOK15:19
mesteryLets move on15:19
mesteryWe've got other sheds to paint this morning/evening15:19
mesterysalv-orlando: Shame on you ;)15:19
mestery#link https://bugs.launchpad.net/neutron/+bug/145703415:19
openstackLaunchpad bug 1457034 in neutron "BGPVPN extension" [Undecided,Confirmed]15:19
*** xingchao has quit IRC15:19
salv-orlandoI'm completely dressed in shame. It's the only thing that makes me feel comfortable when I wear it15:19
mesteryIt looks pretty good on you too ;)15:20
dougwigno, it wasn't. it delves into the question of if plugins should have an interface to report what they support, so the user gets a sane experience.15:20
salv-orlandoyeah but it has no bearing on the RFE being discussed15:20
mesteryThat issue has come up before15:20
dougwigdisagree, but we seem to be arguing the others position.  :)15:20
vikram__carl_baldwin: can you please confirm if doesn't collide with the ongoing BGP work15:20
carl_baldwinvikram__: We’ve discussed this quite a bit.  I don’t think it collides.15:21
kevinbentondougwig: i think the point is that backends will have unsupported protocols with or without nice names for them15:21
vikram__carl_baldwin: ok.. So we don't want to extend the existing BGP work for advertising VPN routes?15:21
kevinbentonmestery: is this bringing in the external project?15:22
carl_baldwinI did think they were going to do this work externally.15:22
mesterykevinbenton: I think this bug may be outdated because they HAVE the external project already15:22
mesteryI think we can mark it invalid15:22
kevinbentonmestery: right15:22
mesteryAnd let them tell us otherwise15:22
kevinbentonmestery: too the bit bucket!15:22
kevinbentonto*15:22
*** tomoe_ has joined #openstack-meeting15:22
mesterynext up15:22
vikram__carl_baldwin, mestery: thanks.. i felt it's for neutron15:22
mestery:)15:23
mestery#link https://bugs.launchpad.net/neutron/+bug/146436115:23
openstackLaunchpad bug 1464361 in neutron "Support for multiple gateways in Neutron subnets" [Undecided,Confirmed] - Assigned to Shraddha Pandhe (shraddha-pandhe)15:23
*** barrett1 has joined #openstack-meeting15:23
mesterycarl_baldwin: Your eyes here would be good :)15:23
kevinbentonthis gives me the heebie jeebies15:23
kevinbentonit feels like implementation details are being leaked15:24
kevinbentonand it's going to be a ton of work15:24
carl_baldwinkevinbenton: +115:24
*** doug-fish has joined #openstack-meeting15:24
*** jorge_munoz has quit IRC15:24
carl_baldwinPart of me wants to say let’s focus on routed networks.15:24
mesterycarl_baldwin: Well, indeed15:24
kevinbentoni think we need a lot more demand from users before pushing this one further15:24
carl_baldwinI think this can also be solved with better infrastructure.15:25
*** egallen has quit IRC15:25
mesterykevinbenton: Please mark it as "Won't Fix" with that info15:25
mesteryI think we can agree on that one it appears15:25
*** doffm_ is now known as doffm15:25
kevinbentonright, let's revisit after we get routed networks all modeled up15:25
*** pm90_ has joined #openstack-meeting15:25
mestery++15:25
dougwigerr.15:25
amotokiagree15:26
* mestery waits a second for dougwig before moving on15:26
dougwigi think it fits pretty well with provider networks, which we're pushing hard, but it can wait, i suppose.15:26
*** egallen has joined #openstack-meeting15:26
haleyband with DVR a second gateway doesn't get you much, without it it might help, or with provider as doug said15:27
*** pm90__ has joined #openstack-meeting15:27
*** stevemar has quit IRC15:27
mesterydougwig: Once it starts talking about load balancing between back planes, that seems like implementation detail leakage to me15:27
kevinbentondougwig: how so? i don't see this in datacenter network designs much15:27
*** stevemar has joined #openstack-meeting15:27
dougwigif you use dhcp to pass a gateway that's closer to the vm, you can spread the gateway load out pretty simply (e.g. leaf and spine.)15:28
kevinbentondougwig: just to get same broadcast domain but then have completely different paths out of the network?15:28
kevinbentondougwig: yeah, that is le suck15:28
kevinbenton:)15:28
dougwigi'm not saying it's how i'd set it up, but if i ended up with a huge ass copper subnet for some reason, i could see using it.15:28
carl_baldwinI’d like to see more demand for this still.15:29
kevinbentondougwig: right. i would rather we build on the primitive of same IP is implemented in multiple locations like DVR15:29
dougwig(as he types this into a browser that's attached to an asymmetric routed subnet, for reasons i don't even want to begin to get into.)15:29
mesterylol15:29
dougwigkevinbenton: this isnt' about what makes sense to a greenfield.  this is about how to work with existing network infrastructures, in my mind.15:29
*** stevemar_ has joined #openstack-meeting15:29
kevinbentondougwig: right, but how would you even know which gateway IP to pick until the VM is scheduled (which is not port creation time)15:30
kevinbenton(at least not all of the time)15:30
dougwigkevinbenton: i'd run my own dhcp server on the provider net.15:30
*** pm90_ has quit IRC15:31
*** DericHorn-HP has joined #openstack-meeting15:31
kevinbentondougwig: well if you're going to do that, what do you need this feature for?15:31
dougwigkevinbenton: because i have a giant copper subnet with multiple gateways that i like?15:31
dougwig*loop detected*15:31
kevinbentondougwig: no, i mean what good does having the gateway IPs appear in the API do?15:32
*** stevemar has quit IRC15:32
kevinbentondougwig: if you have an external DHCP system that understands how the assignment of IP to gateway will work15:32
dougwigoh, true, true.15:32
dougwigso this must want neutron to manage that.15:32
kevinbentonright15:33
*** VW has quit IRC15:33
dougwigwhich would need some kind of scheduler affinity that can inform dhcp.  hmm.15:33
kevinbentonin which case something needs to understand topology15:33
*** sridhar_ram has joined #openstack-meeting15:33
kevinbentonan ML2 driver could conceivably do this15:33
mesteryTopology, it's always topology at the end of the day15:33
mesteryThere is a topology project proposed out there, or there was.15:33
*** VW has joined #openstack-meeting15:33
kevinbentonbut yeah, for now lets leave as won't fix until some more requirements come in15:33
mestery++15:33
dougwigi think going the route of understanding topology is much harder than saying, 'yo, go write a scheduler class.'15:34
*** stevemar_ has quit IRC15:34
dougwigi'm fine with won't fix for now, that's a can of worms that needs more demand, as carl_baldwin said.15:34
kevinbentonsome topology knowledge is going to be required for some of the routed networks stuff...15:34
*** vivek-ebay has joined #openstack-meeting15:34
kevinbentonmapping of networks to hosts15:34
mesteryOK, lets move on to the next shed15:34
mestery#link https://bugs.launchpad.net/neutron/+bug/146446515:34
openstackLaunchpad bug 1464465 in neutron "binding_type improvements to simplify Nova interactions" [Undecided,Confirmed]15:34
mesteryAn "oldie but a goodie" for sure15:34
mesteryAnd I'm not even sure how valid this is anymore given Jay's move to get the VIF code out of nova into a library15:35
*** Qiming_ has quit IRC15:35
*** haomai___ has quit IRC15:35
mesteryAlso, Ian's nova spec wasn't approved15:35
dougwigkevinbenton: having to understand topology is going to be a never-ending pile of suck, as we attempt to grok *every* twisted topology in existence over time. still seems like a scheduling concept to me, of which topology is just one case.15:35
*** bvandenh has quit IRC15:36
kevinbentondougwig: yeah, it's a scheduling restriction thing15:36
kevinbentonmestery: this seems reasonable pending the nova changes15:36
kevinbentonmestery: it would be nice to just tell nova which bridges it needs to plug into for example rather than hoping the configs are right on both sides15:37
mesterykevinbenton: ++15:37
amotokikevinbenton: ++15:38
*** ayoung has quit IRC15:38
mesterykevinbenton: Comment as such and we'll move on15:38
mesteryUp next15:38
mestery#link https://bugs.launchpad.net/neutron/+bug/146479315:38
openstackLaunchpad bug 1464793 in neutron "Add a driver for isc-dhcpd" [Undecided,Confirmed] - Assigned to Shraddha Pandhe (shraddha-pandhe)15:38
mesteryisc-dhcpd driver15:39
mesterycarl_baldwin: Are we ready for this yet? :)15:39
*** jorge_munoz has joined #openstack-meeting15:39
* carl_baldwin reading...15:39
*** Daisy has joined #openstack-meeting15:39
*** pballand has joined #openstack-meeting15:40
*** nisha has joined #openstack-meeting15:40
*** nisha has quit IRC15:40
carl_baldwinI don’t know if we’re ready yet.15:40
*** nisha has joined #openstack-meeting15:40
*** SridharG has left #openstack-meeting15:40
mesterycarl_baldwin: Can you comment as such in the bug and we'll move on?15:40
jaypipesmestery: the os_vif stuff is being revived this week. I have folks in my teams that will be working on it in Mitaka.15:40
*** vivek-ebay has quit IRC15:40
mesteryjaypipes: ++, awesome and thanks!15:40
kevinbentoni'm not particularly interested in maintaining another dhcp driver in tree15:41
carl_baldwinmestery: I’ll take it.15:41
kevinbentonbecause it will be untested15:41
kevinbentonin the gate15:41
mesterykevinbenton: Well, it could be in it's own repo then15:41
mesteryOnce we make DHCP pluggable15:41
mesterySo I agree15:41
mesteryNext up15:41
mestery#link https://bugs.launchpad.net/neutron/+bug/146747115:41
openstackLaunchpad bug 1467471 in neutron "RFE - Support Distributed SNAT with DVR" [Undecided,Confirmed] - Assigned to Takanori Miyagishi (miyagishi-t)15:41
kevinbentonright, isn't it pluggable already?15:41
dougwigkevinbenton: so which one is the one we should support?15:42
mesterydougwig: I'd be hard pressed to move to isc-dhcpd anywhere before Nxxx15:42
kevinbentondougwig: probably the one we already are until we see that the isc-dhcpd driver is that much better15:42
dougwigmestery: that wasn't the question that i asked.15:42
*** salv-orl_ has joined #openstack-meeting15:43
mesterydougwig: Then my answer is dnsmasq15:43
mesteryI think we'd have to reevaluate once isc-dhcpd exists15:43
mesteryIt's kind of like saying we're going to back OVN at this point over the reference implementation.15:43
mesteryToo early15:43
*** Daisy has quit IRC15:43
dougwigfair enough.15:43
salv-orl_mestery: it15:43
salv-orl_is a bit different actually15:44
*** jtomasek has quit IRC15:44
carl_baldwinOn the DVR SNAT thing.  They don’t propose how they plan to distribute SNAT.15:44
salv-orl_isc-dhcpd is part of the data plane which is still manipulated by the reference control plane15:44
*** Zhongjun has joined #openstack-meeting15:44
salv-orl_but still this too is not relevant to the discussion15:44
kevinbentonwhile we're visiting the replacement of DHCP, what about a thing taylored to our use case? we don't use a lease database at all...15:45
salv-orl_kevinbenton has a good point that he does not feel his team has the ability to take the mainteinance burden for this driver15:45
dougwig15 minute warning15:45
carl_baldwinIf no one objects, I’m going to put a comment on the DVR one to elaborate on it and mark it incomplete.15:45
*** ganeshna has quit IRC15:45
amotokire DVR SNAT thing, I would suggest the author to propose more detail for dsicussion to move it forward.15:45
salv-orl_kevinbenton: why don't we get rid of DHCP altogether ;)15:45
mesterycarl_baldwin: ++15:45
kevinbentona script written in OHascala15:45
mesteryconfig drive #ftw?15:45
*** ganeshna has joined #openstack-meeting15:45
*** salv-orlando has quit IRC15:46
kevinbentoncarl_baldwin: ++ getting southbound traffic to the different nodes requires some coordination with the upstream router15:46
salv-orl_mestery: SLAAC and v6 only.15:46
*** xingchao has joined #openstack-meeting15:46
dougwigmestery: eww, config drive requires per guest support.  dhcp is everywhere.15:46
mesterynice :)15:46
mesterydougwig: I was joking :)15:46
dougwigmestery: it wasn't funny.  :)15:47
mestery:)15:47
kevinbenton*shots fired*15:47
carl_baldwinkevinbenton: Right.  Or buring more IPs.  Or sharing IPs between tenants.  Each of the proposed solutions have some group that objects to it.15:47
*** Swami has joined #openstack-meeting15:47
*** CBADER_ has joined #openstack-meeting15:48
kevinbentoncarl_baldwin: yeah, shake down the submitter for more info15:48
mesteryMoving right along (12 minutes left)15:48
mestery#link https://bugs.launchpad.net/neutron/+bug/146823615:48
openstackLaunchpad bug 1468236 in neutron "enable neutron support distributed DHCP agents" [Undecided,Confirmed]15:48
mesteryHuzzah!15:48
mesteryWe're on a hot streak of DHCP here15:48
*** mwagner_ has quit IRC15:48
russellbin OVN, plan is to drop DHCP server requirement by adding basic DHCP responder with flows, which will be distributed of course :)15:48
*** xingchao has quit IRC15:48
*** eharney has joined #openstack-meeting15:48
russellbi'm really good about talking about all the awesome stuff we don't have yet15:49
mestery:)15:49
mesterylol15:49
*** nadya has quit IRC15:49
mesteryThis one has a spec even: https://review.openstack.org/#/c/205429/15:49
*** cbader has quit IRC15:49
*** jdurgin1 has quit IRC15:49
kevinbentonrussellb: yeah, i wish we could do that in our l2 agent, but stupid rootwrap ... :'(15:50
russellbkevinbenton: why can't you do it?  just ovs-ofctl too slow?15:50
russellbdidn't the native openflow driver go in?15:50
*** adahms has quit IRC15:50
mesteryrussellb: It did, but regXboi found perf issues with it15:50
mesteryI think you and he discussed yesterday15:51
*** nisha_ has joined #openstack-meeting15:51
russellbmestery: that was about the native ovsdb driver15:51
*** nisha has quit IRC15:51
russellbovs-vsctl vs ovs-ofctl15:51
russellbheh15:51
*** ayoung has joined #openstack-meeting15:51
mesteryheh :)15:51
*** ayoung has quit IRC15:51
*** ayoung has joined #openstack-meeting15:51
mesteryAnyways, since this one has a spec, I guess w'ell continue reviewing on that15:51
mesteryAnd lets move on here15:51
kevinbentonrussellb: no, not openflow based. have the l2 agent just attach to the network with a tap interface and respond with dhcp packets15:51
kevinbentonmestery: right, i need to read this spec more15:51
russellbkevinbenton: oh ok15:51
dougwig8 minute warning.15:52
mestery#link https://bugs.launchpad.net/neutron/+bug/146836615:52
openstackLaunchpad bug 1468366 in neutron "RFE - Logging API for security group and firewall rules" [Undecided,Confirmed] - Assigned to Yushiro FURUKAWA (y-furukawa-2)15:52
*** yamamoto has quit IRC15:52
kevinbentonrussellb: want something that works for linuxbridge as well15:52
mesteryThis one was pretty contentious during Liberty15:52
*** sridhar_ram has quit IRC15:52
kevinbentondefer to next week :)15:53
mesteryYes15:53
mesterySpeaking of defering ...15:53
mestery#link https://bugs.launchpad.net/neutron/+bug/146880315:53
openstackLaunchpad bug 1468803 in neutron "Modular L2 Agent" [Undecided,Confirmed]15:53
*** otter768 has joined #openstack-meeting15:53
russellbcontentions because of the API?  or the concept?15:53
russellbor both?15:53
kevinbentonlet's do it!15:53
*** epcim has joined #openstack-meeting15:53
kevinbentonrussellb: API i think15:54
mesteryrussellb: Both I think15:54
kevinbentonrussellb: then there were also grumblings about the log destinations IIRC15:54
mesteryI mean, the concept could mean a lot of things and people kept exploding it a bit. But I won't paint that shed today :)15:54
mesterykevinbenton: Right15:54
russellbkevinbenton: ah, yes15:54
russellbre: modular L2 agent ... sounds great to me in theory :)15:55
dougwigwe should go full modular and just make the "modular agent agent"15:56
kevinbentonthere are two things here15:56
mesterykevinbenton: Seems like you and amotoki agreed, shall we move this to Triaged to let it move forward?15:56
*** pballand has quit IRC15:56
mesterydougwig: MOAR MODULAR!15:56
salv-orl_dougwig: that's being metadoular15:56
kevinbentonone is elimating duplication between linux bridge and OVS15:56
*** pballand has joined #openstack-meeting15:56
salv-orl_metamodular15:56
russellbmoduler layers modular agent15:56
kevinbentonwhich i'm all for15:56
armaxkevinbenton: modular l2 agent is -=215:56
armax-215:56
*** ozstacker_ has quit IRC15:56
armaxat least the way we have ml2 plugin15:56
kevinbentonbut i don't want a huge multiple drivers framework15:56
salv-orl_you cannot but love a  PTL whose only words are "-2"15:56
armaxmoduler yes15:56
russellbkevinbenton: +115:56
mesterywelcome to the last 4 minutes of the meeting Mr. PTL :)15:56
kevinbentonarmax: right, that's what i was getting at before you interrupted15:56
kevinbenton:)15:57
russellbkevinbenton: very nice practical way to put it15:57
*** ozstacker has joined #openstack-meeting15:57
armaxmodular l2 the way we know it, not so much15:57
mesterykevinbenton: ++ on no multiple drivers15:57
mesteryicky15:57
amotokithe concept is good, but the concept of agent extnesion is introeduced in the qos work. the approach needs to be revisted.15:57
armaxkevinbenton: I wasn’t interrupting…I was only providing my scarred perspective15:57
armax:)15:57
kevinbentonbut the LB agent and OVS agent are stupid close15:57
* jaypipes creates driver for Ms. Daisy15:57
russellbkevinbenton: sounds like refactoring those 2 would be a good focused baby step15:58
kevinbentonrussellb: yes15:58
russellband it very well may lead to a nice place to plug in some other widget ...15:58
*** otter768 has quit IRC15:58
kevinbentonAbstractAgentFactoryInterfaceBuilder!15:58
russellblol15:58
jaypipeskevinbenton: that's called Zope.15:59
russellbcan it support loading Java plugins please15:59
jaypipesheh15:59
*** fawadkhaliq has joined #openstack-meeting15:59
*** claudiub has quit IRC15:59
mesteryOK15:59
kevinbentonany more?15:59
mesteryI think we're done.15:59
mesteryUntiul next week!15:59
mestery#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
mesterykevinbenton: Nope, times' up15:59
openstackMeeting ended Tue Sep 29 15:59:57 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-09-29-14.57.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-09-29-14.57.txt16:00
mesteryBut yes, there were more16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-09-29-14.57.log.html16:00
kevinbentonmestery: ack, next week!16:00
*** vikram__ has quit IRC16:00
*** su_zhang has quit IRC16:00
*** tomoe_ has quit IRC16:00
*** electrocucaracha has quit IRC16:00
*** sbelous has joined #openstack-meeting16:00
*** BobBall has joined #openstack-meeting16:00
kevinbentonif armax doesn't disband us in a violent political purge of the cruft that built up during your regime :)16:00
russellbo/16:01
kevinbenton\o16:01
dougwigflush it away16:01
*** electrocucaracha has joined #openstack-meeting16:01
armaxkevinbenton: why do people keep associating me to Stalin?16:01
* armax wonders16:01
kevinbentonarmax: you are the only person that said stalin16:01
*** skyler has joined #openstack-meeting16:01
armaxsigh :)16:02
skylerHowdy16:02
*** ygbo has quit IRC16:02
*** skyler is now known as skylerberg16:02
*** jmckind has quit IRC16:04
salv-orl_armax: indeed nobody said Stalin.16:04
salv-orl_kevinbenton: do you want to be armax's Trotsky?16:04
*** gyee has joined #openstack-meeting16:04
armaxsalv-orl_, kevinbenton: ok so I am overreacting, good :)16:05
kevinbentonsalv-orl_: didn't we have a discussion about my history education? :)16:05
*** vgridnev has quit IRC16:06
*** mudassirlatif has joined #openstack-meeting16:06
*** vishwanathj has joined #openstack-meeting16:06
salv-orl_armax: yes, perhaps. Are you still keen on renaming the mid-cycle "neutron developmer re-education camp"?16:07
salv-orl_kevinbenton: but that's recenty history! and American!16:07
*** iben_ has quit IRC16:08
*** raildo is now known as raildo-afk16:08
*** devvesa has quit IRC16:08
kevinbentonsalv-orl_: no, if it involved another country, that's "diluted history", which isn't covered :)16:10
*** dkranz has quit IRC16:10
*** bltavares has quit IRC16:11
*** alexpilotti has joined #openstack-meeting16:11
*** peristeri has quit IRC16:11
*** jlanoux has quit IRC16:12
*** sballe has joined #openstack-meeting16:12
*** annegentle has quit IRC16:12
*** leeantho has joined #openstack-meeting16:12
*** GB21 has joined #openstack-meeting16:14
*** pm90__ has quit IRC16:15
*** jmckind has joined #openstack-meeting16:16
armaxsalv-orl_: was that a proposal?16:16
*** jmckind has quit IRC16:17
*** alop has joined #openstack-meeting16:17
*** jmckind has joined #openstack-meeting16:17
*** hashar is now known as hashar-meeting16:17
*** sankarshan is now known as sankarshan_away16:18
*** jmckind has quit IRC16:18
*** rossella_s has quit IRC16:19
*** gyee has quit IRC16:19
*** matrohon has quit IRC16:19
*** rossella_s has joined #openstack-meeting16:19
*** jmckind has joined #openstack-meeting16:19
*** toscalix__ is now known as toscalix16:20
*** bltavares has joined #openstack-meeting16:21
*** IlyaG has joined #openstack-meeting16:22
*** sridhar_ram has joined #openstack-meeting16:22
*** jmckind has quit IRC16:22
*** raildo-afk is now known as raildo16:22
*** jmckind has joined #openstack-meeting16:23
*** jmckind has quit IRC16:24
*** jmckind has joined #openstack-meeting16:24
*** unicell has quit IRC16:24
*** nisha_ has quit IRC16:25
*** pots1 has joined #openstack-meeting16:26
*** ijw has joined #openstack-meeting16:26
*** jmckind has quit IRC16:26
*** jmckind has joined #openstack-meeting16:27
*** jmckind has quit IRC16:27
*** jorge_munoz has quit IRC16:27
*** vivek-ebay has joined #openstack-meeting16:27
*** sbelous has quit IRC16:28
*** gyee has joined #openstack-meeting16:29
*** bvandenh has joined #openstack-meeting16:29
*** nisha_ has joined #openstack-meeting16:29
*** yassine__ has quit IRC16:30
*** nisha_ has quit IRC16:30
*** toscalix has quit IRC16:32
*** doug-fis_ has joined #openstack-meeting16:32
*** toscalix has joined #openstack-meeting16:32
*** aranjan has joined #openstack-meeting16:33
*** safchain has quit IRC16:34
*** egallen has quit IRC16:34
*** doug-fish has quit IRC16:35
*** hichihara has quit IRC16:36
*** alexsyip has joined #openstack-meeting16:36
*** shashank_hegde has joined #openstack-meeting16:37
*** matrohon has joined #openstack-meeting16:37
*** apoorvad has joined #openstack-meeting16:38
*** dims__ has quit IRC16:38
*** vjay11 has joined #openstack-meeting16:39
*** dims__ has joined #openstack-meeting16:39
*** summer has quit IRC16:40
*** stevemar has joined #openstack-meeting16:42
*** jruano has joined #openstack-meeting16:43
*** ujuc has quit IRC16:43
*** geoffarnold has joined #openstack-meeting16:43
*** vjay11 has quit IRC16:43
*** ihrachys has quit IRC16:43
*** alexpilotti has quit IRC16:44
*** egallen has joined #openstack-meeting16:45
*** pkoniszewski has joined #openstack-meeting16:46
*** kebray has quit IRC16:46
*** pots1 has quit IRC16:50
*** topol has quit IRC16:50
*** ivar-lazzaro has joined #openstack-meeting16:51
*** egallen has quit IRC16:51
*** sbalukoff has quit IRC16:52
*** sbelous has joined #openstack-meeting16:52
*** sridhar_ram has quit IRC16:52
*** yamamoto has joined #openstack-meeting16:52
*** sbelous has quit IRC16:52
*** s3wong has joined #openstack-meeting16:53
*** ayoung has quit IRC16:55
*** ayoung has joined #openstack-meeting16:55
*** pnavarro has quit IRC16:55
*** hughhalf has quit IRC16:56
*** ozstacker has quit IRC16:56
*** mwagner_ has joined #openstack-meeting16:56
*** derekh has quit IRC16:56
*** IlyaG has quit IRC16:57
*** jhenner has quit IRC16:57
*** hurricanerix has joined #openstack-meeting16:57
*** yamamoto has quit IRC16:57
*** jhenner has joined #openstack-meeting16:57
*** shihanzhang has quit IRC16:57
*** shihanzhang has joined #openstack-meeting16:58
*** ricolin has quit IRC16:58
*** hughhalf has joined #openstack-meeting16:58
*** toscalix has quit IRC16:58
*** ozstacker has joined #openstack-meeting16:58
*** jhenner has quit IRC17:00
asselin#startmeeting third-party17:00
openstackMeeting started Tue Sep 29 17:00:20 2015 UTC and is due to finish in 60 minutes.  The chair is asselin. 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
*** garthb has joined #openstack-meeting17:00
*** unicell has joined #openstack-meeting17:00
*** jhenner has joined #openstack-meeting17:00
asselinHi who's here for 3rd party ops working meeting?17:00
sweston\o17:00
asselinhey sweston!17:01
*** Piet has joined #openstack-meeting17:01
*** toscalix has joined #openstack-meeting17:01
asselinpatrickeast, skylerberg mmedvede krtaylor rfolco17:01
skylerberg\o17:01
swestonhi asselin !  just got back from vacation, so haven't been able to answer your ping yet.17:01
*** su_zhang has joined #openstack-meeting17:01
patrickeasthey17:01
krtayloro/17:01
mmedvedeo/17:01
*** hashar-meeting has quit IRC17:02
asselin#link agenda for today is: https://wiki.openstack.org/wiki/Meetings/ThirdParty#Agenda_for_next_Working_Group_meeting17:02
asselin#topic Announcements17:02
*** openstack changes topic to "Announcements (Meeting topic: third-party)"17:02
asselin#link Nodepool image-upload issue: http://lists.openstack.org/pipermail/openstack-dev/2015-September/075368.html17:02
asselinin case you missed the mailing list post, there's a known issue with nodepool uploading images17:02
asselinanyone else have announcements to make?17:03
*** su_zhang has quit IRC17:03
asselin#topic Comparison of CI Dashboards17:03
*** openstack changes topic to "Comparison of CI Dashboards (Meeting topic: third-party)"17:03
*** jruano has quit IRC17:03
*** su_zhang has joined #openstack-meeting17:03
rfolcoo/ (late)17:03
asselin#link https://etherpad.openstack.org/p/third-party-ci-dashboard-comp17:04
*** adahms has joined #openstack-meeting17:04
asselinso last time we only had a few people, but hopefully today we can go into more detail17:04
*** balajiiyer has quit IRC17:05
*** kebray has joined #openstack-meeting17:05
*** bltavares has quit IRC17:05
*** dane_leblanc has quit IRC17:05
asselinsweston, radar's I suppose is not up yet?17:06
*** ozstacker has quit IRC17:06
swestonasselin: it is up, and should be showing the list of CI systems17:06
asselinlink?17:06
swestonasselin: been trying to get to the gerrit queries, but have been buried.17:06
swestonhttps://dashboard.triniplex.com17:07
asselinsweston, works for me w/o the https, just htp17:07
asselinhttp*17:07
asselinlast time we met, there was general concensus to use the ci-watch solution17:08
*** apoorvad_ has joined #openstack-meeting17:08
swestonright, no https17:08
asselinanyone have a different opinion?17:09
*** pgbridge has quit IRC17:09
rfolco+1 on starting with ci-watch and implementing other features gradually17:09
*** ildikov has quit IRC17:09
krtaylorno strong opinion here, except that if we are decided, to get infra to approve it17:11
krtaylorthey feel like we can't make a decision17:11
krtaylorwhen it has been so close to merging many times17:11
mmedvedekrtaylor: it is on today's agenda17:11
mmedvedefor infra meeting17:11
krtaylornot holding my breath17:11
asselinyes, on today's agenda17:11
*** apoorvad has quit IRC17:12
patrickeastheh yea, i'm game for any of the options but we do need to move forward with the infra stuff17:12
asselinbut we couldn't make a solid decision b/c we lacked many stakeholders17:12
patrickeastonce we have the repo's, servers, puppet, etc we can do whatever we want with it17:12
asselinin particular, no dashboard developers were present17:12
*** ja2 has joined #openstack-meeting17:13
krtaylordecision has been made before :)17:13
*** pm90_ has joined #openstack-meeting17:13
krtaylorif this is the decision let's stick with it17:13
*** elo1 has joined #openstack-meeting17:13
*** dane_leblanc has joined #openstack-meeting17:13
krtaylornext dashboard that pops up, we have to stand on this one and get it merged17:13
*** lsmola has quit IRC17:14
asselin#agreed we use ci-watch17:14
mmedvede+117:14
krtaylor+117:14
skylerberg+117:14
rfolco+117:14
ja2+117:14
sweston+117:15
*** IlyaG has joined #openstack-meeting17:15
asselin#topic ci-watch features (<skylerberg>)17:15
patrickeastso, now that we've got our starting point picked17:15
*** openstack changes topic to "ci-watch features (<skylerberg>) (Meeting topic: third-party)"17:15
*** bltavares has joined #openstack-meeting17:15
patrickeastdo we have a plan as far as future requirements on it?17:16
rfolcoperhaps create bugs for each feature missing in ci-watch that other solutions have?17:16
*** sudipto has quit IRC17:16
skylerbergThe first thing we should do is make a project for CI Watch17:16
skylerberg#link https://review.openstack.org/#/c/216840/17:16
patrickeastor maybe rephrased, do we will plan to 'finish' the other dashboard spec?17:16
*** MarkAtwood has joined #openstack-meeting17:16
*** harshs has joined #openstack-meeting17:16
*** shashank_hegde has quit IRC17:16
mmedvedeI myself would like to concentrate on features invisible on ui first, i.e. make the ciwatch adhere to some openstack service common-sense standards17:16
*** ccarrara has joined #openstack-meeting17:16
asselinpatrickeast, the spec will go today to infra meeting to vote as-is.17:17
*** ccarrara has left #openstack-meeting17:17
skylerbergmmedvede: Agreed17:17
rfolcommedvede, +1 on backend first17:17
krtaylormmedvede, well said17:17
asselinmmedvede, +117:17
mmedvedethe current spec is about hosting ciwatch, it brushes over requirements, but does not define them exactly17:17
*** salv-orl_ has quit IRC17:18
*** ijw has quit IRC17:18
asselinok, so let's get it into its own project and iterate it from there17:18
mmedvede# link https://review.openstack.org/#/c/216840/17:18
asselin#link review ci-watch project spec https://review.openstack.org/#/c/216840/17:18
mmedvedethis needs updating? ^17:18
asselinskylerberg, please take it out of WIP17:18
skylerbergrfolco: Once we merge the project-config patch we can start loading up a ci-watch bug tracker with everything we would like.17:18
asselinskylerberg, good point. Should we use launchpad or storybaord?17:19
skylerbergasselin: done17:19
asselinmost of openstack is on launchpad, most of infra is on storyboard17:19
skylerbergI was anticipating using launchpad and have not actually seen storyboard. I have not strong opinion, not having used both.17:20
*** IlyaG has quit IRC17:20
skylerbergDoes anyone have reasons to pick one over the other or have a strong opinion either way?17:20
rfolcoNo strong opinion, would go for launchpad unless infra has objections17:21
*** egallen has joined #openstack-meeting17:21
skylerbergrfolco: That sounds sensible.17:21
asselinUsing storyboard sets up automatically, but not a full-featured as launchpad.17:21
ja2if we think new bodies would come from other openstack projects mostly (vs mostly from infra), we should favor what most coming in will already know.17:21
asselinlaunchpad requires some manual setup, but it's documented17:22
skylerbergasselin: it was a while ago, but I may have actually completed that setup before submitting the review.17:22
skylerbergI was following the project creation guide, so I think it is all set up at this point.17:23
mmedvedeno strong opinion. Other than storyboard is going away17:23
asselinskylerberg, ok then we'll use that17:23
asselinskylerberg, do you have the link?17:23
skylerberg#link https://launchpad.net/~ciwatch-drivers17:23
skylerberg#link https://launchpad.net/~ciwatch-bugs17:23
asselin#link https://launchpad.net/ciwatch17:24
asselin#agreed use launchpad for ciwatch17:24
asselinanything else on this topic?17:24
mmedvedeskylerberg: might be good idea to update topic for 216840 to ci-dashboard, so we can track all ci-dashboard things easier with17:24
mmedvede#link https://review.openstack.org/#/q/topic:ci-dashboard,n,z17:25
*** ozstacker has joined #openstack-meeting17:25
mmedvedeskylerberg: so you think we would not have to rename ciwatch?17:25
*** emagana has quit IRC17:25
mmedvedemy only concern at that point17:25
*** armax has quit IRC17:25
skylerbergmmedvede: I do not think we will need to change it.17:26
skylerbergmmedvede: topic has now been changed.17:26
krtaylormmedvede, why would we need to change it?17:27
*** asselin has quit IRC17:27
*** ijw has joined #openstack-meeting17:27
*** leeantho has quit IRC17:27
*** garthb has quit IRC17:27
krtaylormmedvede, what is your concern?17:27
*** CBADER_ has quit IRC17:27
mmedvedebecause of this spec https://review.openstack.org/#/c/192253/, but it has not been updated in a while17:27
krtayloroops we lost asselin17:27
*** david8hu has quit IRC17:27
mmedvedeasselin_: you here?17:28
*** asselin has joined #openstack-meeting17:28
*** CBADER has joined #openstack-meeting17:28
*** leeantho has joined #openstack-meeting17:28
*** garthb has joined #openstack-meeting17:28
*** david8hu has joined #openstack-meeting17:28
asselinsorry....lost network for a bit....17:28
*** liusheng has quit IRC17:28
skylerbergI will see if I can get ahold of sdague, but since it hasn't been updated in a while and the latest comments were asking for sdague to change the name, I don't think we will have a problem.17:28
*** achanda has joined #openstack-meeting17:29
*** pballand has quit IRC17:29
krtaylormmedvede, as I commented in that patch, it has nothing to do with CI, it is for periodic testing17:29
*** liusheng has joined #openstack-meeting17:29
asselinI think we should stick to the name. If infra approves the spec, then we keep it.17:29
*** mrmartin has joined #openstack-meeting17:29
mmedvedeagreed17:29
krtaylorbut the url is what is in question, or is that the name you are referring to, the project can be named anything17:29
*** fawadkhaliq has quit IRC17:30
*** ozstacker has quit IRC17:30
asselinkrtaylor, which url are you referring to?17:30
mmedvedekrtaylor: the ciwatch project itself was my concern17:31
asselinI think the name is going to be openstack-infra/ciwatch17:31
*** pballand has joined #openstack-meeting17:31
krtaylorperfect17:31
mmedvedethe service is proposed to be hosted as ci-dashboard.o.o17:31
*** Piet has quit IRC17:31
asselinactually patch has openstack/ciwatch17:31
*** galstrom is now known as galstrom_zzz17:31
*** ganeshna has quit IRC17:31
krtaylorworks for me17:31
*** ddieterl_ has quit IRC17:31
*** electrocucaracha has quit IRC17:32
*** ganeshna has joined #openstack-meeting17:32
*** jruano has joined #openstack-meeting17:32
asselin#action  review the patch to create ci-watch project https://review.openstack.org/#/c/216840/117:33
*** sudipto has joined #openstack-meeting17:33
asselin#topic Common-CI Solution17:33
*** openstack changes topic to "Common-CI Solution (Meeting topic: third-party)"17:33
*** coolsvap has quit IRC17:33
asselinI made a lot of progess with the common-ci work17:33
asselin#link Documentation / Instructions: https://review.openstack.org/#/c/227584/17:34
asselin#link Single-node ci puppet class: https://review.openstack.org/#/c/200330/17:34
*** ihrachys has joined #openstack-meeting17:34
asselin#link project-config-example: https://review.openstack.org/#/c/228540/17:34
asselinThe last link is to create a project-config example project17:35
asselinit wasn't part of the original common-ci spec, but I think it's useful to setup a working test system that runs all the tempest tests17:36
*** julim has quit IRC17:36
asselinand a good starting point to add your own configurations17:36
*** sridhar_ram has joined #openstack-meeting17:36
*** pballand has quit IRC17:36
*** ganeshna has quit IRC17:37
ja2+1 on example being useful17:37
mmedvedeasselin: +1, but I have already reviewed :)17:37
*** shashank_hegde has joined #openstack-meeting17:37
*** julim has joined #openstack-meeting17:37
*** coolsvap has joined #openstack-meeting17:37
*** ddieterly has joined #openstack-meeting17:37
*** galstrom_zzz is now known as galstrom17:38
asselinany comments or questions?17:38
*** salv-orlando has joined #openstack-meeting17:38
asselin#topic Open Discussion17:38
*** openstack changes topic to "Open Discussion (Meeting topic: third-party)"17:38
asselinany other topics?17:39
asselinanyone new that would like to introduce themselves?17:39
ja2I had a question worth running past this group, although I'm guessing I'll need to go to nova with it in the end.17:40
asselinja2, go ahead17:40
ja2We're getting our CI system for z/VM actually running, slowly but surely.  tempest full runs a bunch of stuff we don't need, so we're config'ing our way through that.17:41
*** krtaylor has quit IRC17:42
ja2nova's hypervisor support matrix lists tens of functions - is there a named tempest subset for each?17:42
ja2#link http://docs.openstack.org/developer/nova/support-matrix.html17:42
ja2there's nothing like a tempest subset name on the details for each row in that table (further down, same page)17:43
*** egallen has quit IRC17:43
*** markvan has quit IRC17:43
*** emagana has joined #openstack-meeting17:43
*** markvan_ has joined #openstack-meeting17:43
rfolcohaving tempest tests mapped to each row would be most excellent17:44
*** ijw has quit IRC17:44
*** neelashah has quit IRC17:44
ja2"would be" sounds like an implicit "...but there is no such mapping today"17:44
*** sileht_ has joined #openstack-meeting17:44
rfolcothe problem is that its too complex, scenario tests for example... they require multiple features in the same test17:45
*** sileht_ is now known as sileht17:45
*** sileht has quit IRC17:45
*** pballand has joined #openstack-meeting17:45
*** sileht has joined #openstack-meeting17:45
*** markvan has joined #openstack-meeting17:45
*** markvan_ has quit IRC17:46
*** galstrom is now known as galstrom_zzz17:46
ja2let's say I'm skeptical of the "too complex" assertion, but if there's not existant mapping then that's what I need to proceed anyway.17:46
*** baoli_ has quit IRC17:46
asselinI know that tempest has ways of tagging certain tests17:46
ja2(if one cannot reliably map those functions to tests, effectively it's impossible to audit the assertions in the matrix)17:47
asselinor only running those when a config is enabled17:47
rfolcoja2, I am also interested in that mapping17:47
*** pvaneck has joined #openstack-meeting17:48
ja2there are some coarser-grained nova.conf "feature" booleans that _probably_ are the 80-20 easy part of the solution17:48
asselinja2 +117:48
*** sudipto has quit IRC17:48
*** mrmartin has quit IRC17:48
asselinja2 might be worth discussing with the qa team as well17:48
ja2"the qa team" meaning the -qa channel?17:49
*** MarkAtwood_ has joined #openstack-meeting17:49
asselinja2, yes17:49
ja2ok thx17:49
asselinmtreinish is the ptl17:49
*** pballand has quit IRC17:50
asselinwhat do you all think about removing the old agendas from https://wiki.openstack.org/wiki/Meetings/ThirdParty17:50
ja2"removing" meaning deletion, or archival somewhere?17:51
*** penick has joined #openstack-meeting17:51
*** pballand has joined #openstack-meeting17:51
asselineither way...wiki has the history but may be cumbersome to use17:51
*** tsymanczyk has joined #openstack-meeting17:52
mmedvedeasselin: the old agendas do not really bother me. What do other meeting's wikis do?17:53
asselininfra only has the latest agenda17:53
*** elo1 has quit IRC17:53
*** novas0x2a|laptop has joined #openstack-meeting17:53
asselinhttps://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting17:53
mmedvedeasselin: works for me then17:54
ja2deletion implies most users will have no way they know of to find it, regardless of effort (I'm assuing that sites like Internet Time Machine will have them anyway), so the stakes are higher than if they're archived with a pointer to the archives.17:54
*** krtaylor has joined #openstack-meeting17:54
*** otter768 has joined #openstack-meeting17:55
*** aranjan has quit IRC17:55
mmedvedeja2: the meetings logs remain17:55
ja2mmedvede17:55
ja2mmedvede, true enough.  so yes, fine to nuke agendas.17:56
asselinok I'll see if there's an easy way to archive them first.17:57
*** browne has joined #openstack-meeting17:57
*** electrocucaracha has joined #openstack-meeting17:58
asselinif there's nothign else I'll end the meeting17:58
*** lhcheng has joined #openstack-meeting17:58
SotKHi folks, I was wondering which channel would be useful for a StoryBoard developer to chat to the project team?17:58
*** annegentle has joined #openstack-meeting17:58
*** penick has quit IRC17:58
*** sdague has quit IRC17:58
asselinSotK, #openstack-infra17:58
SotKasselin: thanks :)17:58
*** roxanaghe_ has joined #openstack-meeting17:59
* stevemar lurks patiently17:59
*** jamielennox has joined #openstack-meeting17:59
asselin#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Tue Sep 29 17:59:26 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-09-29-17.00.html17:59
*** edmondsw has joined #openstack-meeting17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-09-29-17.00.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-09-29-17.00.log.html17:59
*** otter768 has quit IRC17:59
*** elo1 has joined #openstack-meeting17:59
stevemarping ajayaa, amakarov, ayoung, breton, browne, davechen, david8hu, dolphm, dstanek, ericksonsantos, geoffarnold, gyee, henrynash, hogepodge, htruta, jamielennox, joesavak, lbragstad, lhcheng, marekd, morganfainberg, nkinder, raildo, rharwood, rodrigods, roxanaghe, samueldmq, stevemar, tsymanczyk, topol, vivekd, wanghong, claudiub17:59
lbragstadstevemar: o/17:59
marekd\o/17:59
raildo\o/17:59
gyee\o17:59
stevemarhola amigos18:00
jamielennoxhere18:00
*** ozstacker has joined #openstack-meeting18:00
*** dims has joined #openstack-meeting18:00
*** ihrachys has quit IRC18:00
*** ja2 has quit IRC18:00
lhchengo/18:00
bknudsondo we change the name to stevestone now?18:00
*** balajiiyer has joined #openstack-meeting18:00
browneo/18:01
stevemarwas expecting more o/'s18:01
*** bvandenh has quit IRC18:01
*** martines has quit IRC18:01
*** samleon has joined #openstack-meeting18:01
edmondswo/18:01
* bknudson lurks18:01
roxanaghe_\o18:01
*** amakarov has joined #openstack-meeting18:01
*** neelashah has joined #openstack-meeting18:01
stevemargood enough, folks can join when they get here18:01
stevemar#startmeeting keystone18:02
openstackMeeting started Tue Sep 29 18:02:10 2015 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: keystone)"18:02
gyeetraffice is bad today18:02
openstackThe meeting name has been set to 'keystone'18:02
stevemargyee: for sure18:02
*** dims__ has quit IRC18:02
stevemar#link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:02
stevemaragenda has been updated18:02
stevemari tossed a few items up18:02
*** sdague has joined #openstack-meeting18:02
stevemarmorgan: around?18:02
marekdstevemar: me too (3 mins ago)18:03
stevemaryup, i see that18:03
gyeehail to stevemar!18:03
* dstanek is here. better late than never18:03
gyeefirst agenda18:03
stevemar#topic ptl change18:03
*** openstack changes topic to "ptl change (Meeting topic: keystone)"18:03
stevemarwell this is awkward :P18:03
*** markvan has quit IRC18:03
bknudsonthere's a new sheriff in town18:03
dstanekstevemar: congrats!18:03
marekd++18:03
stevemarmorgan did an awesome job, let's all thank him first18:03
*** shaleh has joined #openstack-meeting18:03
amakarov+118:03
morganO/ and btw it said not me18:04
*** sridhar_ram has quit IRC18:04
bknudsonthanks to everyone who ran. it was a tough choice18:04
stevemarbknudson: ++18:04
*** apoorvad_ has quit IRC18:04
gyeestevemar, you prefer cash or check?18:04
dstanekgyee: reviews18:04
stevemargyee: jewels18:04
stevemarreviews too18:04
*** penick has joined #openstack-meeting18:04
gyeeyes18:04
lbragstadbeer?18:04
*** apoorvad has joined #openstack-meeting18:04
stevemarhope i don't disappoint :) but i feel like i have the world's largest safety net with such an awesome team18:05
*** dane_leblanc has quit IRC18:05
* morgan welcomes the new stevemar keystone overlord :P18:05
*** vivek-ebay has quit IRC18:05
marekdstevemar: you won't, just keep rockin' :-)18:05
dstanekyou'll do great, just like our previous leaders18:05
shalehstevemar: we can always stage a coup if we have to :-)18:05
tsymanczyk\o18:05
stevemarshaleh: i like your style18:06
* morgan pours a drink and sits back.18:06
*** penick has quit IRC18:06
stevemarnot much else to say here, let's go on to a few lighter topics before we get into the weeds18:06
bknudsonstart our own keystone project18:06
stevemar#topic meeting time18:06
*** openstack changes topic to "meeting time (Meeting topic: keystone)"18:06
*** markvan has joined #openstack-meeting18:06
*** olaph has joined #openstack-meeting18:06
amakarovshaleh, for the complete democracy we need an opposition! ))18:06
*** sridhar_ram has joined #openstack-meeting18:06
*** olaph has left #openstack-meeting18:07
stevemarwe've had this time for a while, and it works, but i feel like we need to bring it up every release, just in case18:07
stevemarjamielennox: amakarov marekd, looking at you guys18:07
gyeeno issue with meeting time here18:07
bknudsonif this time didn't work for someone they're probably not here.18:07
stevemarhehe18:07
*** Zhongjun has quit IRC18:07
jamielennoxit really can't go any earlier for me18:07
jamielennoxas is i'm about 50/5018:07
amakarovI'm fine with current meeting time18:07
jamielennoxbut i'm ok with the current18:08
lbragstadi'm good with the current time18:08
morganstevemar: we need to make the meeting at least 7hours later /s18:08
stevemarmorgan: just to really get jamielennox18:08
marekdmorgan: deep night for me :(18:08
amakarovit will be 4am for me and breton18:08
morganNote the "/s" ;)18:08
stevemarmarekd: you're good with current?18:08
marekdstevemar: yeah18:08
stevemaralright18:09
stevemaras usual, no need to alternate meetings or have a second time, thats nice to hear18:09
marekdstevemar: i said a meeting 7hrs later would be a deep night for me18:09
raildothis time is great for us here in Brazil :)18:09
stevemarand saves me from creating a ML post18:09
*** delatte has joined #openstack-meeting18:09
*** delattec has quit IRC18:09
*** cdelatte has quit IRC18:09
stevemarneeeext topic18:09
*** vivek-ebay has joined #openstack-meeting18:09
marekdgiven geodistribution of team members i think that's the only reasonable team18:09
stevemar#topic liberty-rc2 do we need one?18:10
*** openstack changes topic to "liberty-rc2 do we need one? (Meeting topic: keystone)"18:10
morganYes18:10
bknudsonI assume one is needed for translations18:10
morganFor translations18:10
stevemaralright, for translations18:10
bknudsonhow do we know when translation work is complete?18:10
morganstevemar: you just talked to dhellmann an hour ago about this...18:11
morgan:P18:11
stevemarmorgan: well yes, i wanted to use this time to see if there's anything else18:11
stevemari think this one is handy: https://review.openstack.org/#/c/215870/18:11
stevemarif an admin creates endpoints using v3, then v2's endpoint-list doesn't bring them up, that's my understanding anyway18:12
marekdstevemar: when would be liberty-rc2 cut?18:12
*** dane_leblanc has joined #openstack-meeting18:12
morganmarekd: next week iirc18:13
*** claudiub has joined #openstack-meeting18:13
*** penick has joined #openstack-meeting18:13
stevemarmarekd: soon, we still have a bit of time, maybe a week18:13
marekdmorgan: ok.18:13
bknudsonwe can backport https://review.openstack.org/#/c/215870/ if it doesn't make the rc18:13
*** ijw has joined #openstack-meeting18:13
dstaneki was pretty close last time i looked18:14
*** ozstacker_ has joined #openstack-meeting18:14
marekdi would also take a look at this https://review.openstack.org/#/c/206561/18:14
dstaneki just wanted to verify the json coming back still looks correct and then i'd be happy with it18:14
stevemardstanek: agreed, i pulled it down and tried it out, i'd be happy to vouch for it18:14
*** ijw has quit IRC18:14
dstaneki can do that today and throw up a new vote18:14
*** Sukhdev has joined #openstack-meeting18:14
*** esheffield has quit IRC18:14
stevemardstanek: cool18:14
marekdnevertheless we will need to backport it to kilo.18:14
gyeeso we need to map 1 endpoint ID to multiple?18:14
gyeesorry I mean multiple to 118:15
jamielennoxi'd agree with having the feature, code seems strange to me - but i don't think the brain has really kicked in yet18:15
stevemarmarekd: hold up a sec, we can get into the other one in a minute18:15
dstanekgyee: yes18:15
morganjamielennox: drink moar coffee18:15
gyeewould that be problematic as we need to maintain multiple IDs?18:16
* lbragstad hands jamielennox more coffee18:16
marekdstevemar: yes sir!18:16
dstanekjamielennox: it's mostly strange because of how we changed v2 and v3 endpoints18:16
*** aranjan has joined #openstack-meeting18:16
*** mrmartin has joined #openstack-meeting18:16
dstanekgyee: we don't in v218:16
*** ddeva has joined #openstack-meeting18:16
stevemarmorgan: so umm, how's this work, hypothetically if 215870 is merged, and we want it in rc2, we need to merge it to master - then cherry-pick it to liberty? and cut rc2 from stable/liberty?18:16
*** Sukhdev has quit IRC18:16
jamielennoxyea, just looking as to why we build a v3_endpoints dict and iter that again, but ok18:16
morganYep18:16
stevemarmorgan: i am learnding18:16
*** Sukhdev has joined #openstack-meeting18:17
morganBack port to stable/Liberty which is where rc2 will be tagged from18:17
*** moha_hunt has joined #openstack-meeting18:17
*** Tango has quit IRC18:17
stevemar\o/18:17
*** ozstacker has quit IRC18:17
*** markvan has quit IRC18:17
bknudsonwe used to have a -proposed branch18:17
*** emagana has quit IRC18:17
stevemari like this way more, it's easier18:17
edmondswI think https://review.openstack.org/#/c/217373/ should be backported to liberty and kilo18:17
stevemaredmondsw: that's would be re-releasing a minor version of keystonemiddleware18:18
*** ivar-lazzaro has quit IRC18:18
edmondswyes18:18
stevemaroh it's approved, doh18:18
*** markvan has joined #openstack-meeting18:18
gyeedstanek, ahh, its using the public endpoint ID as the legacy endpoint ID?18:19
lbragstadbut what about the backport? that will require a new release of something, right?18:19
bknudsonI don't think we can do a minor version change in stable/liberty, it'll be the patch #.18:19
*** Sisir has joined #openstack-meeting18:19
*** ildikov has joined #openstack-meeting18:19
stevemarmorgan: for edmondsw's question, does the same logic still hold for keystonemiddleware? or do we just tag a new release from master?18:19
bknudsonhttp://semver.org/18:19
morganWe can only do patch level .Z changes18:19
morganFor stable branches18:19
dstanekdo we do release of kilo for kmw? or is it just a normal new release from master?18:20
stevemardstanek: they have stable branches18:20
morganMiddleware has stable branches18:20
morganIf this is a real bug fix, it is a .z patch level18:20
morganIf it is a .y patch level it isn't a bug fix18:20
bknudsonthe change should be released in master before it's released in stable releases.18:21
stevemarthe only hitch is updating the requirements in the stable branch too right?18:21
morganIt is a feature/behavior change18:21
edmondswit's a real bug fix18:21
*** esheffield has joined #openstack-meeting18:21
morganstevemar: adding new requirements to stable is a no-go in most cases18:21
ayoungedmondsw, yeah...that is a bug fix18:21
morganSo work around requirements changes.18:21
morganIf you do a .z release requirements won't change18:22
morganIn stable18:22
stevemar#todo stevemar to bug dhellmann about ksm refresh and pulling in edmondsw's change18:22
*** aranjan has quit IRC18:22
morganUpper bounds will (perhaps)18:22
*** AlanClark has joined #openstack-meeting18:22
stevemari'll dig into this18:22
morganIt will be a back port for that change. Simple18:23
stevemarmorgan: is there an rc2 in lp?18:23
morganstevemar: for keystone or middleware? Middleware doesn't do rc18:23
morganMy18:23
stevemarkeystone proper18:23
*** ijw has joined #openstack-meeting18:23
morganFor keystone that is pending rel management to add the milestone18:23
morganTalk to dhellmann and/or ttx18:24
stevemarmorgan: so then hows it work for targeting bugs?18:24
*** jprovazn has quit IRC18:24
ayounghow's rc2 work?  We release right away, or on some schedule?18:24
bknudsonis there an rc2-potential for bugs?18:24
stevemarayoung: right away18:24
morganMark the bug as rc-potential and get the milestone added18:24
morganTarget the bug18:24
stevemarbknudson: that would be a good idea18:24
morganMerge the fix18:24
stevemarcool18:24
stevemaralrighty18:24
morganTag rc2 when needed18:24
stevemari think i already tagged it18:24
*** ozstacker_ has quit IRC18:25
morgan:)18:25
stevemarokay, marekd your go, you wanted to talk about another potential rc2 bug?18:25
marekdstevemar: yeah18:26
marekdhttps://review.openstack.org/#/c/206561/ this may actually blow up db_sync keystone18:26
marekdincluding kilo18:26
marekdi can work on it tomorrow and address the comments.18:26
*** delatte has quit IRC18:26
*** ksavich has joined #openstack-meeting18:27
marekdactually bug desc is better to read: https://bugs.launchpad.net/keystone/+bug/147896118:27
openstackLaunchpad bug 1478961 in Keystone "db sync on federation failed if there is existing data" [High,In progress] - Assigned to Marek Denis (marek-denis)18:27
dstanekmarekd: merging that change would blow up db_sync? or things will blow up without it?18:27
lbragstadso that won't require a backport migration will it?18:27
stevemari think it's just a liberty fix lbragstad18:27
morganlbragstad: if a migration is back ported it has to be idempotent.18:27
lbragstadstevemar: cool, so no backport18:27
marekddstanek: without that change things *might* blow up db_sync in some cases18:28
marekdstevemar: lbragstad this actually should be backported to kilo too.18:28
morganThis is another case where we need to collapse the separate migrate repos into the main one18:28
dstanekmarekd: is it possible to get a test to generate data to get into that situation?18:28
morganmarekd: that is likely un backportable to kill18:28
morganKilo18:28
marekdmorgan: why?18:28
morganIf 006 doesn't exist in kilo you can't back port it18:29
*** boris-42 has quit IRC18:29
*** delatte has joined #openstack-meeting18:29
morganYou can't have gaps and you can't reuse numbers18:29
morganIf it18:29
*** armax has joined #openstack-meeting18:29
bknudsonfor M we need to consider if we want the placeholder migrations18:30
marekdmorgan: uh, let me check18:30
dstanekno placeholders for the federation migrations?18:30
*** delatte has quit IRC18:30
morgandstanek: no placeholders for any non-main repo18:30
stevemardstanek: no placeholders for any extensions unfortunately18:30
dstanekmorgan: didn't know that and i've never bothered to look18:30
morganWe need to collapse all of these into the main repo18:30
morganAs part of mitaka to fix this silly18:30
morganState18:31
marekdmorgan: https://github.com/openstack/keystone/tree/stable/kilo/keystone/contrib/federation/migrate_repo/versions correct me if i am wrong but we do have 006 in kilo ?18:31
morganThe split repos was (in hindsight) a bad idea18:31
*** hashar has joined #openstack-meeting18:31
morganOk... Hm.. Maybe you can backport it18:32
ayounghalfway through18:32
morganBe wary. Back porting migrations is scary18:32
ayoungand I really want to talk roles...18:32
bknudson006 is already doing something else.18:32
marekdmorgan: the only reason would be gaps in migrations numbering  or something more 'political' ?18:32
morganAnyway.. Just be warned there be dragons here18:32
ayoungmorgan, the split repos was not a bad idea.  Merging all of the migrations into one repo is the bad idea, but lets let it go....18:32
marekdmorgan: ok18:32
*** jprovazn has joined #openstack-meeting18:32
marekdi will work on the fix and get back to you.18:33
stevemarayoung: yeah, we're still good for time, its just this and a heads up about release notes, then we're on to roles18:33
dstanekmarekd: and a test?18:33
morganayoung: the split repos was a terrible idea. It sounded good at the time18:33
marekddstanek: and a test.18:33
bknudsonthis is changing an existing migration to clean it up. should be fine.18:33
*** nadya has joined #openstack-meeting18:33
dstanekmarekd: thx!18:33
morganbknudson: ++18:33
marekdmorgan: stevemar dstanek : i think jose revealed this bug while doing test upgrade to kilo on his dev env....18:33
bknudsonthe migration would have failed before so don't have to worry about it breaking anything.18:33
* morgan was for split repos at the time. Anyway18:33
stevemarbknudson: lol18:33
ayoungIf we are pulling info from an extension in, have the migration check for the table before making any changes18:33
*** cpallares has joined #openstack-meeting18:34
dstanekbknudson: for the test i'm more worried about ensuring we are fixing something18:34
ayoungit won't be reverseable, but we've droppped that requirement anyway18:34
stevemarmarekd: let's proceed with fixing it18:34
morganAnyway I'll take a bug to collapse the extra repos this cycle.18:34
marekdstevemar: OK, i will address the commments.18:35
morganLet's backport that and get a test added18:35
stevemarwe can potentially backport it, i can't imagine too many ppl have stuff in their federation tables, you guys were the early adopters18:35
ayoungmorgan, we going to do all of the extensions at once?18:35
morganJust be super careful backporting18:35
*** 32NAAGPES has joined #openstack-meeting18:35
*** cdelatte has joined #openstack-meeting18:35
stevemarand as bknudson said, it can't get worse18:35
*** pballand has quit IRC18:35
morganayoung: I'll collapse each as an idempotent migration18:35
ayoungmorgan, ++18:35
stevemaryup18:35
lbragstad++18:35
marekdstevemar: i think lots of people are on very old releases, so they might get to the point we (cern) are today - let's then save them from the troubles.18:36
*** su_zhang has quit IRC18:36
*** sbalukoff has joined #openstack-meeting18:36
marekdesp the fix is in the end not super hard.18:36
marekd:-)18:36
stevemar#todo stevemar to look into getting those 2 bugs backported and a possible ksm refresh18:36
ayoungstevemar, #action for those18:36
stevemarmarekd: yup18:36
marekdstevemar: thanks!18:36
stevemarnext!18:36
stevemar#topic release notes18:36
*** openstack changes topic to "release notes (Meeting topic: keystone)"18:36
ayoungwe do that on etherpad first?18:37
bknudson#link https://etherpad.openstack.org/p/keystone-liberty-release-notes18:37
lbragstadi think we already have on started18:37
lbragstad^^18:37
bknudsonthe proposed release notes are at the bottom18:37
stevemar#link https://etherpad.openstack.org/p/keystone-liberty-release-notes18:38
stevemarwe have an etherpad18:38
stevemarthe link to the wiki is there18:38
stevemarand now here!18:38
stevemar#link https://wiki.openstack.org/wiki/ReleaseNotes/Liberty#OpenStack_Identity_.28Keystone.2918:38
stevemarplease review and add as you see fit, i trust you all18:38
ayoungWe are claiming Fernet token as a hardened feature.  We willing to take it out of experimental?18:38
ayoungline 6218:38
stevemarayoung: yes, but it looks like it was in a good enough state to motivate someone to move it over (dolphm?)18:38
lbragstadit's hardened but I don't think it's moved out of experimental18:38
stevemarmaybe lbragstad knows18:38
bknudsonwe never advertised fernet as experimental as far as I know18:39
lbragstadbknudson: had a patch up to document that it's experimental18:39
ayounglets be explicit one way ot the other with it, please18:39
bknudson#link https://review.openstack.org/#/c/224888/18:39
gyeeso we have 3 levels now, experimental, harden, and stable?18:39
lbragstadgyee: no, i think the point was to just say that it was hardened18:40
stevemargyee: no, hardened isn't a thing, just yeah - what lbragstad says ^18:40
marekd^^ which of the state is equivalent to "may be used in prod" ?18:40
stevemarstable and experimental18:40
stevemarmarekd: stable18:40
*** topol has joined #openstack-meeting18:40
stevemarexperimental means we are subject to change things18:40
lbragstadyes18:41
stevemarbreak API contracts / endpoints / blah18:41
ayoungOK...review the rest...roels?18:41
gyeebut would that be confusing to the operators?18:41
gyeeits harden, but still experimental18:41
bknudsonI don't think we're planning to break the fernet API contract18:41
marekdstevemar: AFAIR fernet format doesn't have any 'contract'18:41
ayoung20 minutes left...  and no henrynash18:41
bknudsonfernet isn't working with tempest currently18:42
lbragstadbknudson: yes,18:42
stevemargyee: i'll clean up the wording :)18:42
*** nadya has quit IRC18:42
marekdbknudson has some patches for fernet & federation i also have some patches and not actually sure what to do with them...18:42
gyeestevemar, k, thanks, I was having my operator hat on18:42
ayoungI haven't looked, but I'll bet it still needs an external token format identifier, too.18:42
lbragstadbknudson: once we have it passing all the tempest tests (which we're close) I feel comfortable marking it as stable18:42
*** nikhil has joined #openstack-meeting18:42
bknudsony, we should change one of the gates to use it.18:42
stevemarmarekd: patches for what?18:42
lbragstadbut, that will require some work around the subsecond problem that dolphm and i have been working on18:42
lbragstadwhich will require an API change18:43
bknudsonalso, we need to change the gate that uses eventlet to stop doing that18:43
morganIf fernet can't pass tempest we can't mark it stable18:43
marekdstevemar: fernet + federation18:43
morganFYI.18:43
bknudsonall the token formats should use the same resolution for timestamps18:43
lbragstadbknudson: ++18:43
morganOooh ooooooh stevemar I'm gonna kill eventlet today for mitaka!!18:43
bknudsondeployers already think fernet is stable.18:43
marekdhttps://review.openstack.org/#/c/213742/18:43
stevemarmarekd: link me later18:43
amakarovmorgan, ++18:43
lbragstadyes, and correcting that will be an api change18:43
stevemarmorgan: i just got feedback from someone saying to *not* kill it18:44
*** nikhil_k has quit IRC18:44
stevemarbut, later18:44
morganstevemar: why?18:44
morganstevemar: in -keystone post meeting18:44
stevemarmorgan: meh, later, let's give ayoung time to chat about d20s18:44
stevemar#topic roles18:44
*** openstack changes topic to "roles (Meeting topic: keystone)"18:44
ayoungRolllllllllles18:44
stevemarayoung: ^18:44
*** Sukhdev has quit IRC18:44
ayoungOK...so wish henry was here18:44
*** AJaeger has joined #openstack-meeting18:44
stevemaroh right, henry can't make it today, my bad, was supposed to say that earlier :)18:44
ayoungAs you might have learned, right now is the most valuable time for ghetting newe features definied;  we have rc out, and people can start thinking about the next release18:45
*** Sukhdev has joined #openstack-meeting18:45
* morgan roles 2d8: 4 and 718:45
ayoungwe've got a few things that might finally make some progress18:45
*** notnownikki has joined #openstack-meeting18:45
ayoungfirst.. bug 968696  issue18:45
openstackbug 968696 in OpenStack Compute (nova) ""admin"-ness not properly scoped" [High,Confirmed] https://launchpad.net/bugs/96869618:45
gyeemorgan, rolls?18:45
*** Piet has joined #openstack-meeting18:46
ayoungthere was an issue if a user deleted a project but the resources were not deleted, there was no way to clean them up18:46
ayoungdolphm, suggested that it should be a service specific task;18:46
ayoungnova should clean vms, neutron networks and so on18:46
ayoungso...18:46
*** electrocucaracha has quit IRC18:46
ayoungfirst spec for that is18:46
stevemarayoung: create an event and nova listens for it?18:46
gyeemistrial?18:46
ayoungstevemar, not if it missed it in the past18:46
bknudsonwe already have an event, that's why we closed the bug.18:46
ayounghttps://review.openstack.org/#/c/228477/18:47
gyeetaskflow?18:47
*** pots1 has joined #openstack-meeting18:47
marekdRAFT :P18:47
ayoungor not18:47
*** jasondotstar is now known as jasondotstar_afk18:47
ayoungit means we need to catch every exceptional case up front, with not way to fix things if they are broken18:47
ayoungoperators need more support than that18:47
*** pots1 has left #openstack-meeting18:48
raildobknudson, ++ the only problem is that the services doesn't consume this event18:48
ayoungkeystone sends the notifcation to cielometer only today...the distribution of events is not something that is well handled18:48
marekdayoung: ++ :(18:48
ayoungand if there is additional workflow?18:48
marekdand i think it's not default for ceilometer to consume and store those events18:48
ayoungso...lets state explicitly what this is:  scope admin to an endpoint18:49
ayounginstead of trying to shoehord this into the HMT approach, we make a new value for "scope" in a token...."endpoint"....we could do all of the catalog items, but I think that makes policy too hard to write correctly18:49
gyeecustomer can create their own queue right?  I am talking Rabbit18:49
*** whenry has quit IRC18:50
ayounggyee, its trickier than that...it should be a different listener on the same topic18:50
*** electrocucaracha has joined #openstack-meeting18:50
ayoungand if a service goes down, we don't have guaranteed delivery etc18:50
ayounglets not count on events yet18:50
stevemarayoung: if i have a role on an endpoint, what can i do? any action on that endpoint?18:51
*** electrocucaracha has quit IRC18:51
ayoungstevemar, still depends on the role, just that the assignment is scoped to the endpoint18:51
ayoungit would mean that to perform an admin operation, instead of admin on any project (what we have today) or some admin project (suggested)  they would have it on the endpoint...18:51
gyeewith endpoint filtering, assignment is restrict to endpoint18:52
*** ccarrara has joined #openstack-meeting18:52
bknudsonhow do you assign a role for a user on an endpoint?18:52
ayoungand we do an HMT style assignment for the normal case:  assign the user the role on the whole catalog,  requies a token  scoped to the endpoint18:52
gyeebknudson, you assign a role to a user for a project and given set of endpoints18:52
ayoungbknudson, it becomes a new value for assignmnet_type in the assignemnt table18:52
ayounggyee, not filtering...18:53
ayoungthis is scope of the assignment itself, not endpoints filtered by project18:53
bknudsonok, a new assignment type18:53
ayoungthere would be no project in the token18:53
stevemarthe dots still aren't connecting for me18:53
gyeeassigning role to a endpoint makes no sense18:53
ayoungbknudson, yes18:53
bknudsonand scope18:53
marekddoes it have anytging to do with dynamic policies or it's a completely separated topic?18:53
*** shaleh has quit IRC18:53
stevemarmarekd: separate-ish18:53
*** toscalix has quit IRC18:53
*** GB21 has quit IRC18:53
ayounggyee, assigning a role to a user on an endpoint;  essentially, the role name only means something if the role is scoped to endpoint, not a project on the endpoint18:54
marekdstevemar: how are they connected, then?18:54
ayoungmarekd, similar, but separate from dynamic policy18:54
gyeeunless we support endpoint scoping18:54
gyeewhich still doesn't make much sense without the project18:54
*** e0ne has quit IRC18:54
*** pabelanger has joined #openstack-meeting18:54
ayounggyee, to peform an admin action, instead of requesting a proejct scoped token, user requests and endpoint scoped token18:54
marekdayoung: filling same bug, but in a different way, ok18:54
*** ivar-lazzaro has joined #openstack-meeting18:55
ayoungmarekd, yep18:55
gyeeayoung, yes, for admin action, it make a lot of sense18:55
ayoungdolphm, does this pass your sanity checker?18:55
ayoungOK...so that is the first item...18:55
stevemardolphm might be afk18:55
bknudsonwhat's the service catalog look like?18:55
*** eharney has quit IRC18:55
lbragstad~5 minutes left18:55
ayoungbknudson, probably just the one endpoint18:55
bknudsonkeystone won't be able to fill in the %(tenant_id)s18:55
ayoungok...so, we can cont that later18:56
*** sridhar_ram has quit IRC18:56
ayoungon to...18:56
gyeesounds like a good topic for Tokyo18:56
ayoungbknudson, true, but anne gentle is trying to kill that anyway...18:56
stevemarayoung: i suggest you and henry really hash this out before tokyo18:56
ayounggyee, agreed, but want to have consensus before Tokyo or we will miss 'M'18:56
*** yolanda has joined #openstack-meeting18:57
ayoungstevemar, want everyone to know what we are talking about.18:57
stevemarayoung: yes, service catalog: this topic https://review.openstack.org/#/c/181393/13/specs/service-catalog.rst18:57
stevemarayoung: understood18:57
ayoungHenrynash's proposal is really three things18:57
gyeeayoung, I am all for endpoint-scoping18:57
ayoung1.  namespacing of roles.18:57
ayoung2. Role inference18:57
bknudsondon't wait for the meeting to talk about it. put together a workgroup or something.18:57
ayoung3.  virtual roles18:57
ayoungI was just targetting the 218:57
stevemarayoung: those mean nothing to us right now :)18:57
ayoungI have working code for that.18:58
*** Sukhdev has quit IRC18:58
ayoungstevemar, right...which is why I am typing as fast as I can18:58
ayoungrole infrecne....18:58
stevemars'all good18:58
ayoungan implied role means if I get "admin" I also get "member"18:58
ayoungso policy rule can be simplified18:58
stevemarput it up on a wiki and try to timeline it out and we can chat about it in -keystone18:58
stevemarwe're not gonna get it in 90 seconds18:58
ayounginstead of saying "you need to have either admin or memeber" you can just say " you need to have member"18:58
stevemars/wiki/etherpad/g18:59
*** neelashah has quit IRC18:59
ayoungstevemar, I put it up in a spec and I am working on example code...18:59
stevemareveryone - please please read: https://review.openstack.org/#/c/181393/13/specs/service-catalog.rst18:59
ayoungthe thing Henry and I need to hash out is where his and mine aline18:59
ayoungalign18:59
stevemarfor sure18:59
*** olaph has joined #openstack-meeting19:00
stevemarlets not interfere with infras time19:00
stevemar#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Sep 29 19:00:23 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
lbragstadthanks everyone19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-09-29-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-09-29-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-09-29-18.02.log.html19:00
stevemarthx guys19:00
fungiinfra team: assemble!19:00
Clinto/19:00
jeblairo/19:00
yolandao/19:00
Zarao/19:00
waynro/19:00
pleia2o/19:00
skylerbergo/19:00
mmedvedeo/19:00
asselino/19:00
SotKo/19:00
dougwigO/19:00
stevemarwhat about justice leagers?19:01
fungi#startmeeting infra19:01
openstackMeeting started Tue Sep 29 19:01:00 2015 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
*** pelix has quit IRC19:01
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
*** eharney has joined #openstack-meeting19:01
*** roxanaghe_ has quit IRC19:01
fungi#topic Announcements: reminder of Stackforge migration on October 1719:01
*** openstack changes topic to "Announcements: reminder of Stackforge migration on October 17 (Meeting topic: infra)"19:01
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2015-August/003119.html19:01
*** stevemar has quit IRC19:01
*** lhcheng has left #openstack-meeting19:01
*** sridhar_ram has joined #openstack-meeting19:01
clarkbohai19:01
*** DericHorn-HP has quit IRC19:01
fungijust a friendly reminder, this big rename is happening on october 1719:01
zaroo/19:02
fungialso any non-emergency rename work is postponed for now19:02
pabelangero/19:02
olapho\19:02
*** jamielennox has left #openstack-meeting19:02
anteayaClint has patches, stackforge-rename is the gerrit topic I think19:02
fungiwe didn't have any pending renames listed on the agenda after i cleared out the ones we already took care of19:02
fungi#topic Announcements: Mitaka Summit Planning Etherpad19:02
*** openstack changes topic to "Announcements: Mitaka Summit Planning Etherpad (Meeting topic: infra)"19:02
*** DericHorn-HP has joined #openstack-meeting19:02
pleia2let the games begin19:02
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2015-September/003237.html19:02
fungi#link https://etherpad.openstack.org/p/infra-mitaka-summit-planning19:02
anteayamass-stackforge-renames19:03
fungithanks pleia2 for putting that together!19:03
ianwo/19:03
*** mrmartin has quit IRC19:03
*** Sisir has quit IRC19:03
fungilet's collectively brainstorm on summit topics for our allotted timeslots/rooms and then discuss them in an upcoming meeting19:03
crinkleo/19:03
*** samleon has quit IRC19:03
anteayabrainstorm in the etherpad you mean?19:04
fungiyep19:04
anteayaaye19:04
*** Sisir has joined #openstack-meeting19:04
fungiif we have lots of ideas in there by next tuesday i'll try to set aside a good chunk of the meeting to work through prioritizing them as a group19:04
*** ddeva_ has joined #openstack-meeting19:04
fungiif not, i'll shame you into adding more ;)19:04
jeblairnote: we have some shared meetup space with qa and ironic; hopefully we'll have some cross pollination with our big projects19:04
ruagairO/19:04
*** glauco___ has joined #openstack-meeting19:04
*** bltavare_ has joined #openstack-meeting19:04
*** bltavare_ is now known as bltavares_19:05
fungiyes, i'd love for us to have one focus be infra cloud, since we can ab^H^Huse the opportunity with ironic folk to flatter them and work through challenges we might have19:05
*** whenry has joined #openstack-meeting19:05
jeblairfungi: i'll bring barricades19:05
crinklefungi: ++19:05
*** Tango has joined #openstack-meeting19:06
fungiand as always, qa are our brethren, so plenty of things we can work with them on19:06
fungi#topic Announcements: jenkins-job-builder RFH and core reviewer list adjustments19:06
*** openstack changes topic to "Announcements: jenkins-job-builder RFH and core reviewer list adjustments (Meeting topic: infra)"19:06
*** bobh has quit IRC19:06
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2015-September/003238.html19:06
fungi#link https://review.openstack.org/#/admin/groups/194,members19:06
*** bobh has joined #openstack-meeting19:07
fungithanks to zxiiro for stepping up and helping as a core reviewer on jjb!19:07
*** ddeva has quit IRC19:07
waynrzxiiro++19:07
*** bltavares has quit IRC19:07
*** glauco__ has quit IRC19:07
*** ccavanna has quit IRC19:07
*** ccarrara has quit IRC19:07
fungialso i've pruned some long-inactive core reviewers on jjb19:08
*** galstrom_zzz is now known as galstrom19:08
anteayathanks for past service19:08
fungiabsolutely19:08
*** stevemar has joined #openstack-meeting19:08
fungiand as always, i know the current reviewers appreciate any additional reviewing help you can spare19:08
anteayacongratulations zxiiro19:08
waynrI'll forward that mail to my team, might get someone else to start reviewing19:08
fungithanks waynr!19:09
*** dkranz has joined #openstack-meeting19:09
fungi#topic Actions from last meeting19:09
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:09
fungi#link http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-09-22-19.02.html19:09
funginibalizer propose change adding nibalizer to infra-root19:09
fungiyolanda propose change adding yolanda to infra-root19:09
fungiwhere did those end up? i'd like to go ahead and approve them19:09
yolandapending from review19:09
fungii meant to before the meeting, but ENOTIME19:09
*** Sukhdev has joined #openstack-meeting19:09
yolandaseveral +2, pending from more and approval19:09
*** Sisir has quit IRC19:10
jeblair#link https://review.openstack.org/22652619:10
jeblair#link https://review.openstack.org/22664319:10
fungithanks, was just hunting those up19:10
AJaegersorry, for joining late...19:10
anteayaAJaeger: glad you are here19:10
fungithere's already a majority of root admins with +2 on that so i'll approve right after the meeting. any remaining +2 feel free to add yourselves before then19:11
yolandafungi, thx19:11
fungijeblair automate some sort of mass contact attempt for stackforge move19:11
jeblairi did that!19:11
fungii saw positive evidence that did indeed happen19:11
fungiwe're getting lots of replies too19:11
jeblairseems to have helped19:12
fungithings are indeed looking a little better with the wiki now19:12
clarkbyup people are aware and talking19:12
anteayathe wikipage had many edits in the history19:12
jeblairin the email, i said we'd put unresponsive projects on the retire list by the end of the week19:12
anteayayay deadlines19:12
fungimost awesome. to reiterate, i agree19:12
clarkbis it worth sending a second wave?19:12
jeblairso maybe next week, we send out another email to those and say "hey, we did this; better change the wiki page if you disagree"?19:12
fungithat's not a terrible idea19:13
fungiespecially since you already have the script!19:13
jeblairyep, marginal cost is low19:13
anteayaand I like the wording of that19:13
fungiClint write script to prepare project-config change for migration19:13
Clint#link https://review.openstack.org/#/c/228002/19:13
anteayatiming19:13
fungihe had it all typed up there, i bet ;)19:13
Clinthe did19:13
anteayacomedy duo19:14
fungiplease to reviewing19:14
fungiit has some parent changes which also look important19:14
AJaegerClint: 228002 is just for the channels, we need similar script for zuul/layout.yaml as well19:14
ClintAJaeger: oops19:14
AJaegerOr at least some sed magic to replace everything - we can leave them in the "Stackforge" section19:15
AJaegerYeah, that could work...19:15
*** doug-fis_ is now known as doug-fish19:15
AJaegerWe also need gerrit/projects.yaml to get updated19:15
Clintit does gerrit/projects.yaml19:15
*** juzuluag has quit IRC19:15
*** zxiiro has joined #openstack-meeting19:15
Clintand i'm not sure what needs renaming in zuul/layout.yaml19:15
Clintoh, i see19:16
fungiClint: namespaces on the repos19:16
AJaegerClint: we use "stackforge/repo" - but have it in sections.19:16
Clintgot it19:16
fungiyeah, i'm less concerned about the section ordering/grouping there and more about making the rename happen19:16
AJaegerfungi: yeah...19:16
AJaegersed should be enough...19:16
fungiClint: so you want to work on the layout.yaml stuff too since you already have the projects.yaml and channels stuff worked out?19:17
Clintsure19:17
*** elo1 has quit IRC19:17
fungi#action Clint write script to prepare layout.yaml change for migration19:17
*** maishsk has quit IRC19:17
fungithanks!19:17
*** tsymanczyk has left #openstack-meeting19:17
*** elo1 has joined #openstack-meeting19:17
fungieveryone review https://review.openstack.org/#/c/214207/19:17
fungithat seems to have happened and it's now merged19:17
fungijhesketh: are the indices working as expected?19:17
*** edmondsw has left #openstack-meeting19:18
*** Sisir has joined #openstack-meeting19:18
clarkbwas that the change that jhesketh mentioned wanting to rewrite completely?19:18
clarkbfungi: its easy to test let me get a link19:18
*** Daisy has joined #openstack-meeting19:18
clarkbhttp://logs.openstack.org/51/226751/14/check/nodepool-coverage/ doesn't seem to work properly19:19
clarkbhttp://logs.openstack.org/51/226751/14/check/nodepool-coverage/d06565b/ is the path to files in swift19:19
clarkbso we should get an index page with a listing of job uuid prefixes19:20
*** nadya has joined #openstack-meeting19:20
clarkbbut get a 404 instead19:20
anteaya:(19:20
*** maishsk has joined #openstack-meeting19:20
clarkbanyways somethign to go digging in apache logs to debug19:20
fungisimilarly http://logs.openstack.org/43/226643/8/check/gate-system-config-pep8/ has no index even though it should include http://logs.openstack.org/43/226643/8/check/gate-system-config-pep8/886b686/19:20
fungi#action jhesketh look into why the swift upload indices are still not appearing19:21
fungi#topic Specs approval: Translation check site spec (pleia2)19:21
*** openstack changes topic to "Specs approval: Translation check site spec (pleia2) (Meeting topic: infra)"19:21
fungi#link http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_check_site.html19:21
fungithat got approved last week19:21
pleia2thanks everyone19:21
*** baoli has joined #openstack-meeting19:21
fungilooking forward to an exciting implementation19:22
anteayayay19:22
fungi#topic Specs approval: JJB 2.0 API (waynr)19:22
*** openstack changes topic to "Specs approval: JJB 2.0 API (waynr) (Meeting topic: infra)"19:22
fungi#link https://review.openstack.org/18254219:22
* waynr beeps19:22
fungithis spec has been submitted for council vote19:22
*** tsekiyama has joined #openstack-meeting19:22
yolandai'd like to resume work on #link https://review.openstack.org/155305 , can i get some more eyes?19:22
fungiright now it has only one rollcall vote, so it should probably collect a few more19:23
*** amakarov is now known as amakarov_away19:23
*** Daisy has quit IRC19:23
waynrfungi: okay, is there a list of folks I should ping to get eyeson?19:23
*** Shrews has joined #openstack-meeting19:23
anteayafungi: would you like to set a voting timeframe?19:23
fungiwaynr: they're here19:24
waynrcool19:24
*** ijw has quit IRC19:24
*** galstrom is now known as galstrom_zzz19:25
zaroi just re-reviewed19:25
*** galstrom_zzz is now known as galstrom19:25
*** apoorvad has quit IRC19:25
fungi#info voting open on Jenkins Job Builder 2.0.0 API Changes/Rewrite spec until  2015-10-01 19:00 UTC19:26
*** neelashah has joined #openstack-meeting19:26
*** neelashah has quit IRC19:26
fungi#topic Specs approval: Host third-party CI monitoring dashboard (mmedvede)19:26
*** openstack changes topic to "Specs approval: Host third-party CI monitoring dashboard (mmedvede) (Meeting topic: infra)"19:26
mmedvedethanks fungi, the spec proposes deploying CI Watch, can be seen running at19:26
fungi#link https://review.openstack.org/19443719:26
*** vivek-ebay has quit IRC19:26
mmedvede#link Example deployment: http://ci-watch.tintri.com/project?project=nova19:26
mmedvedeas one of infrastructure's services at ci-dashboard.openstack.org19:27
anteayathe third party group has been working toward agreement on what tool infra should host for some time19:27
fungilooks like it has a couple rollcall votes but still needs a few more19:27
anteayacongratulations to everyone involved for getting this far19:28
fungi#info voting open on initial CI monitoring dashboard service spec until 2015-10-01 19:00 UTC19:28
asselinthird party folks are supporting this solution19:28
pleia2maybe a question for another time, but how are we keeping track of this vs. openstack health?19:28
pleia2I could see confusion happening19:28
anteayapleia2: it is a good question19:28
*** elo1 has quit IRC19:28
pleia2should probably select naming very carefully at this stage19:28
fungiright, one is for upstream ci tracking failure rates for specific jobs if i recall correctlt19:28
fungicorrectly19:29
anteayafungi: yes that is openstack health19:29
* pleia2 nods19:29
fungiso potential for confusion does exist19:29
yolandado we have spec for openstack health?19:29
anteayaand the spec for it is sdague's and was called ci-watch19:29
fungiqa might19:29
fungioh, the hosting spec for it, yes19:29
clarkbI also don't see how its supposed to provide additional info over what is already in gerrit. Are we looking for trends? maybe it should interpret the data then?19:29
anteayaI thought it was in infra19:29
*** maishsk_ has joined #openstack-meeting19:29
anteayayes the hosting spec19:29
anteayaclarkb: it is a visualization tool19:30
*** maishsk has quit IRC19:30
*** maishsk_ is now known as maishsk19:30
lifelessclarkb: openstack-health shows subunit data19:30
clarkbanteaya: yes but its not showing me any new information19:30
*** elo1 has joined #openstack-meeting19:30
mmedvede#link openstack health sample deploy:  http://15.126.244.104:8001/#/19:30
skylerbergclarkb: For CI operators this shows a lot more data at once.19:30
anteayaand really helps projects see what they need to see to track their jobs19:30
clarkbanteaya: lifeless specifically talking about the third party ci thing19:30
asselinclarkb, we're just looking for a quick an easy tool19:30
anteayaclarkb: oh the third party tool19:30
anteayaclarkb: projects want it and developers want it19:30
clarkbskylerberg: right and because of that its unreadable19:30
skylerbergIt can be tedious to figure out when your CI started failing and to see if others are also failing from a similar problem.19:30
clarkbskylerberg: anyways we can iterate on what is actually useful later19:30
*** baoli has quit IRC19:31
fungiyeah, i'm fine with this being an experiment. its success or failure does not need to be predetermined19:31
pabelangerFWIW: grafana could also be used for health checks19:31
anteayaclarkb: nova is using the third party ci dashboard in their meetings19:31
mmedvedeOpenstack health looks like it is more for overall status. third-parties are interested in how their CI perfroms, and that is what CI Watch does19:31
anteayaclarkb: to track their nova drivers19:31
*** baoli has joined #openstack-meeting19:32
clarkbmmedvede: right I think openstack health is more in line with what I would expect the third part ci dashboard to do. Interpret the vast quantity of data for me so I don't have to scroll horizontally multiple browser widths. But again we can hash those details out later19:32
fungiokay, further feedback to the review. if there are new concerns we can defer approving it but get your comments in by thursday19:32
anteaya#link sdague's ci watch spec: https://review.openstack.org/#/c/192253/19:32
mmedvedefungi: thanks19:32
*** eharney has quit IRC19:32
nibalizero/ (sorry for late)19:33
fungiworst case we can always adjust the spec after it merges too19:33
anteayaI would like to see if we can approve the spec as is and figure out the naming afterwards19:33
*** huats has joined #openstack-meeting19:33
anteayait has taken over a year for the third party folks to get this far19:33
funginot like specs are written in stone, just good to get them as close as possible in the beginning if we can19:33
anteayait would be nice if we can figure out a way to approve the spec19:33
skylerbergclarkb: Don't worry we are on the same page and have discussed adding pagination and summarizing results. The scrolling forever thing is a known issue :)19:33
asselinI think the spec is great as is19:33
fungi#topic Specs approval: Spec for nodepool image update retries (yolanda)19:33
*** openstack changes topic to "Specs approval: Spec for nodepool image update retries (yolanda) (Meeting topic: infra)"19:33
fungi#link https://review.openstack.org/15530519:34
fungi(last-minute addition)19:34
yolandait has been stopped for long, i'd like to resume it these days19:34
*** carl_baldwin has quit IRC19:34
yolandaso it needs some more eyes, it's a quite simple addition19:34
clarkbyolanda: does DIB make that not necessary?19:34
*** carl_baldwin has joined #openstack-meeting19:35
clarkbin my experience dib builds are quite reliable due to the caching dib performs19:35
jeblairit does seem like it should make it less necessary at least19:35
yolandaclarkb, when i was using DIB, it was failing to me as well19:35
fungisince it's not been on the agenda before today's meeting i'll defer opening voting until next week, but this can serve as a reminder that it's ready19:35
yolandaalthough i'm not a dib user for a long time19:35
clarkbyolanda: my preference would be to not complicate image builds more right now because we are trying to switch to shade, have recently found many bugs in image building and need many more tests, and in theory DIB fixes many of the reliability problems present with snapshot builds19:36
*** ccarrara_ has joined #openstack-meeting19:36
jeblairthere's also an assumption here that it's important for image builds to succeed daily19:36
greghaynesAlso uploads and such retry with shade19:36
greghaynesor they can and should19:36
yolandayes, not ready for voting, but needs more reviews19:36
yolandai'll add for next week agenda19:36
yolandaclarkb, also, do we want to deprecate snapshots method at some point or we will let it coexist?19:36
jeblairwe should deprecate snapshots19:37
clarkb+119:37
fungiright, we've so far (upstream) operated on the assumption that it's nice to have daily image refreshes but jobs should be resillient to working from stale images when needed19:37
fungii could get onboard with snapshot deprecation, though obviously that implies a major version bump in nodepool when we eventually do remove them19:37
jeblairi think i'd be in favor of postponing this until we're on fully-dib and shade, so we see what our actual need is then19:37
clarkbjeblair: wfm19:38
yolandaok19:38
*** vgridnev has joined #openstack-meeting19:38
yolandafor downstream usage at least, is important to have images regenerated daily19:38
*** gyee has quit IRC19:38
yolandareally a need now, if we have some failure, we are enforced to regenerate manually19:39
*** sileht has quit IRC19:39
jeblairyolanda: that's unfortunate; i'm happy to talk with you about ways to avoid that19:39
yolandajeblair, yes, i'd like to have help on that19:39
jeblaircool19:39
*** krtaylor has quit IRC19:40
fungi(also our upstream jobs serve as a model for how we work around them)19:40
fungi#topic Priority Efforts19:40
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:40
*** sheeprine has joined #openstack-meeting19:40
*** pgbridge has joined #openstack-meeting19:40
fungiany urgent updates on the priority efforts front? if not, i propose we skip ahead to discussion topics since we're at 20 minutes remaining and have several on the agenda19:40
*** skylerberg has quit IRC19:40
anteaya#vote skip19:40
fungimostly just looking for blockers which need some attention19:41
fungigoing once...19:41
fungitwice...19:41
yolandai just want to say thanks to TW guys for the huge efforts on puppet module testing19:41
fungi#topic Policy around bash-isms vs. POSIX compliance in infra (pleia2)19:41
*** openstack changes topic to "Policy around bash-isms vs. POSIX compliance in infra (pleia2) (Meeting topic: infra)"19:41
pleia2this is actually broader than this specific thing, with more cores and the team growing in general, I don't think we have any kind of style guide or such to judge things like this19:41
pleia2maybe we should?19:41
anteayapleia2: was there a usuage you questioned that motivated the topic?19:42
pleia2defining things like posix vs bash, preferred puppet methods, etc19:42
clarkbwe have never been posix and explicitly bash everywhere19:42
fungiso far i think our policy has been "don't use bashisms unless you declare #!/bin/bash in your entry-point scripts"19:42
ianwi think it's bash everywhere19:42
pleia2anteaya: negative review and "fixes" switching to posix rather than bash19:42
anteayapleia2: link?19:42
pleia2so it was clear to me that not everyone knows we decided on bash19:42
jeblairwe were entertaining adopting bash8 at some point...19:42
pleia2anteaya: in the meeting agenda, I'll copy...19:42
fungi#link https://review.openstack.org/21266319:42
dougwigI usually stick to posix if it's trivial, just for easier porting. This is just a question of reviewer calibration. I've added nits to ask if posix, but I don't think I've ever -1'ed.19:42
pleia2thanks fungi19:42
fungi#link https://review.openstack.org/#/c/224326/1/jenkins/scripts/common_translation_update.sh19:42
AJaegerfungi: I had a patch that I abondoned where I did try to put in some consistency19:42
*** krtaylor has joined #openstack-meeting19:42
jeblairdougwig: thank you for handling it that way :)19:42
clarkbdougwig: so I disagree on that actually because sh isn't ever bourne shell anymore19:43
clarkbbash is way more portable19:43
AJaegerSo, if [a = b] ; instead of [a == b]19:43
ianwi would say maintain consistency with surrounding code19:43
clarkbso if we want portability we should be explicit that its bash and not argue :)19:43
greghaynesyou mean [[ ]] which would be bash vs posix19:43
clarkber not argue over the code (if it works in bash great)19:43
nibalizerI agree with clark19:43
AJaegergreghaynes: == is also bash, = is posix19:43
dougwigmaybe it's just this old dog being stuck on '='.  no worries, not arguing.  :)19:44
nibalizer/bin/sh can be any number of incompatible things at this point19:44
*** jhenner has quit IRC19:44
*** elo1 has quit IRC19:44
* jeblair is just happy if his shell scripts run and don't delete filesystems19:44
fungias long as the shebang is an accurate reflection of the script's interpreter requirements, i see "portability" changes as unnecessary rewrite noise for the most part19:44
*** jhenner has joined #openstack-meeting19:44
anteayajeblair: ha ha ha19:44
jeblairfungi: this is a stance i could agree with (i could also agree with clarkb)19:45
*** eharney has joined #openstack-meeting19:45
*** jhenner has quit IRC19:45
*** sileht has joined #openstack-meeting19:45
*** baoli has quit IRC19:45
*** jhenner has joined #openstack-meeting19:45
fungiit's easy to run checkbashisms against a script and propose "fixes" based on that, but since we don't have consensus that we should avoid using bash in our scripts (what's the portability/efficiency benefit there?) it's a waste of reviewer and developer effort19:45
anteayayeah I'm not sure what problem we are solving here19:46
clarkbright I think we should just be explicit and be fine with them. I am guilty of abusing bashisms to make the code simpler and more readable fwiw so I definitely have a bias here19:46
greghaynes++ to posix changes being not a useful way to spend time for everyone involved19:46
greghaynesfor us19:46
clarkbBut I think that in general saying "bash is ok" is good as a result19:46
*** baoli has joined #openstack-meeting19:46
pleia2wfm19:46
nibalizeryep19:46
ianwfungi: yep, changes just to modify unnecessary.  i'd also not reject things that are "posix-ism" (maybe bash has a better/different way) if consistent with existing code19:46
AJaegerwfm as well....19:46
*** jckasper has quit IRC19:46
pleia2so is it valuable to record decisions like this somewhere for reviewers?19:46
fungii sometimes wonder whether people are looking for easy ways to provide benefit, so the answer is likely finding them other more productive ways to contribute19:46
dougwigi don't think there's an argument here, i'm guessing you can move on.  :)19:47
ianwplenty of spelling errors in devstack :)19:47
*** elo1 has joined #openstack-meeting19:47
Clintpleia2: i think so19:47
yolandapleia2, a guide for proper reviews sounds like a good idea19:47
clarkbthats what the first line of the script is for19:47
*** sileht has quit IRC19:47
fungi#agree Project Infrastructure scripts don't seek to eliminate use of bash, and unsolicited POSIX-compliance changes are not a review priority19:47
clarkb"this is bash" done19:47
*** sileht has joined #openstack-meeting19:48
*** Sukhdev has quit IRC19:48
*** galstrom is now known as galstrom_zzz19:48
*** ivar-lazzaro has quit IRC19:48
Clintclarkb: that doesn't help if someone thinks "oh, wouldn't it be better if this weren't in bash"19:49
fungioh, i think the keyword is "agreed" not "agree"?19:49
* Clint nods.19:49
anteayafungi: agreed19:49
pleia2Clint: let's chat later to see about other institutional knowledge and come up with a proposal for such a thing if we get critical mass :)19:49
fungiso anyway, anyone strongly disagree before i correct my agree?19:49
*** vivek-ebay has joined #openstack-meeting19:49
Clintpleia2: sure19:49
fungi#agreed Project Infrastructure scripts don't seek to eliminate use of bash, and unsolicited POSIX-compliance changes are not a review priority19:49
fungi#topic Fedora 22 nodes (ianw)19:50
*** openstack changes topic to "Fedora 22 nodes (ianw) (Meeting topic: infra)"19:50
*** jhenner has quit IRC19:50
fungi#link https://review.openstack.org/18661919:50
ianwoh this was last week, but if we have 2 minutes19:50
*** jhenner has joined #openstack-meeting19:50
ianwi have fedora-minimal changes out, they're stuck int he dib queue19:50
fungiahh, yep i see the sept 22 on these19:50
ianwi wouldn't mind if we merged this while that goes through19:50
ianwthen i'll convert19:51
*** Sisir has quit IRC19:51
ianwthe issue was that we want the minimal images to boot on rax19:51
*** electrocucaracha has joined #openstack-meeting19:51
fungioh, right, i kept these topics in because they didn't get hit last week19:51
*** Sisir has joined #openstack-meeting19:52
clarkbright, the original fedora22 images would only boot on hpcloud19:52
clarkbianw: so you would like to start with that then convert to minimal and add rax after dib updates go in?19:52
greghaynesianw: tomorrow im back to being able to work real hours19:52
ianwyep, but i'd rather us start building the images, and i can debug everything that goes wrong that !rax19:52
clarkbI am fine with that19:52
greghaynesso ill try and review those19:52
ianwclarkb: exactly, there's so much other stuff, puppet etc19:52
clarkbianw: ya19:52
ianwlet's get that shaken out19:53
*** vivek-ebay has quit IRC19:53
*** vivek-ebay has joined #openstack-meeting19:53
ianwgreghaynes: np, thanks.  the fedora-minimal images are bigger than the non-minimal images :)  still looking into that19:53
*** angdraug has joined #openstack-meeting19:53
*** aranjan has joined #openstack-meeting19:53
fungiianw: also you had a topic up for docker use in a project's job configuration. looks like that merged. still urgent? if not i'll jump to gerrit upgrade discussion19:53
greghayneshah19:53
ianwwell, on docker, i mean i guess we don't care so much if jobs go ahead and install their own docker debs, etc19:54
ianwi just pointed out to the owner of the job that it's very possible we'll do something to the underlying platform that totally breaks it though19:54
greghaynesideally they do and we cache the packages in images19:54
ianwand it's going to be a super-fragile job with network, imo19:54
jeblairi think we care more as they start to need to use dockerhub (mayb we need a mirror) or are part of official openstack projects19:54
*** jruano has quit IRC19:55
ianwso yeah, just a heads up that i think this has started in the wild, and it may come back to us to do a more centralised thing (mirrors, caching, etc) in the future19:55
fungithanks ianw!19:55
fungi#topic Gerrit upgrade (zaro, anteaya)19:55
*** otter768 has joined #openstack-meeting19:55
*** openstack changes topic to "Gerrit upgrade (zaro, anteaya) (Meeting topic: infra)"19:55
fungi#link https://etherpad.openstack.org/p/I0eV4IgkZS19:55
*** geoffarnold has quit IRC19:55
fungijust a quick check-in on current gerrit upgrade status19:55
anteayaso zaro has been working hard on the gerrit upgrade19:55
*** topol has quit IRC19:56
anteayaand as we tried to outline on the etherpad he is currently blocked19:56
zaroso i think the questions is are there any ideas on how we can move this forward?19:56
anteayaso we thought sharing that info would be a good start to figureing out next steps19:56
anteayabascially we are a unique snowflake19:56
*** Sisir has quit IRC19:56
anteayaand unless we fix the upstream thing ourselves zaro feels it won't get fixed19:57
fungiso the summary is that most gerrit users just up the timeout and hope they don't still hit the issue, jgit devs are disinclined to view it as a bug?19:57
*** baoli has quit IRC19:57
clarkbzaro: gerrit and android and cyanogenmod are all hosted publicly as well19:57
clarkbzaro: do they not care about this bug?19:58
*** Rockyg has joined #openstack-meeting19:58
zarowell, it's definately a bug.  the issue is whether it's a gerrit bug or a jgit bug19:58
clarkbalso jgit itself is publicly hosted too19:58
*** aranjan has quit IRC19:58
fungigerrit and android use a database-backed rather than file-backed repo solution though right? or was that disinformation?19:58
*** browne has left #openstack-meeting19:58
*** erlon has quit IRC19:58
clarkbthat is correct19:58
fungi(and yes, i know filesystems are technically databases)19:58
zarogood points.  so maybe i'm way off.  but just seems like nobody wants to touch it.19:59
clarkbBUT my understanding of the bug is its thread contention of the same object in gerrit/jgit19:59
clarkbso would be surprised if that fixes it for them19:59
anteayaif we look to 2.11 is it fixed there?19:59
anteayaor is this issue just going to follow future releases?19:59
fungiwell, we're down to the last few seconds for the meeting, but maybe try to put our heads together in #openstack-infra and regroup19:59
anteayathanks for the time19:59
fungithanks for bringing it up!19:59
zaroit's a bug in 2.1119:59
*** lblanchard has quit IRC20:00
zaroit's a bug in master20:00
*** su_zhang has joined #openstack-meeting20:00
fungithanks for attending, everyone!20:00
fungi#endmeeting20:00
*** sridhar_ram has quit IRC20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Sep 29 20:00:16 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-09-29-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-09-29-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-09-29-19.01.log.html20:00
*** otter768 has quit IRC20:00
ttxWe're on!20:00
markmcclaino/20:00
russellbo/20:00
ttxAnyone here for the TC meeting ?20:00
lifelesso/20:00
cpallareso/20:00
jeblairo/20:00
fungii'm just here for the free food20:00
lifelessin mind at least20:00
Rockygo/20:00
Pietyep20:00
* dougwig lurks.20:00
dtroyero/20:00
waynrfree food forever!20:00
dtroyerfood?20:00
sdagueo/20:00
Pietputting on some music20:00
* edleafe lurks20:00
sheeprineo/20:00
*** penick has quit IRC20:01
lifelessdtroyer: twice a year, at the summits ...20:01
*** earlephilhower has quit IRC20:01
* jeblair hoses sandwich bits out of his keyboard20:01
*** AJaeger has left #openstack-meeting20:01
ttxjgriffith, annegentle, mordred, flaper87, jaypipes, dhellmann: around ?20:01
dtroyerlifeless: ah, right20:01
dhellmanno/20:01
annegentleallo20:01
mordredo/20:01
*** yolanda has left #openstack-meeting20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Sep 29 20:01:47 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
ttxOur (busy) agenda for today:20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:02
* ruagair lurks20:02
ttxI reorganized it a bit so that easier topics can be cleared fast20:02
ttxand because the Kosmos decision might affect other decisions20:02
ttx#topic Adds OpenStack UX core reviewers to extra-atcs20:02
*** openstack changes topic to "Adds OpenStack UX core reviewers to extra-atcs (Meeting topic: tc)"20:02
ttx#link https://review.openstack.org/22492320:02
ttx4 names proposed, all Foundation members.20:02
*** olaph has left #openstack-meeting20:02
ttxPiet, Eric and Ju Lim are actually already ATCs for their contribution to other projects20:02
ttxstill missing a few votes20:03
ttxobjections?20:03
*** jckasper has joined #openstack-meeting20:03
*** pballand has joined #openstack-meeting20:03
anteayattx I put them in the patch because I couldn't confirm that when I wrote it20:03
PietThis is really about Michael Hinnant who doesn't have ATC status.  However, he has been very active providing reviews.20:03
sdaguenone that I see, I think we should just let votes accumulate and move on20:03
*** ddeva_ has quit IRC20:03
ttxok, will approve when it reaches 720:03
russellbttx: has 7 now20:03
anteayacan they still be added to the tc election roll?20:03
ttxalright then, approved20:03
PietSweet!20:04
ttxanteaya: no, we tagged it20:04
anteayaokay thanks20:04
ttx#topic Formal vulnerability:managed application criteria20:04
*** openstack changes topic to "Formal vulnerability:managed application criteria (Meeting topic: tc)"20:04
ttx#link https://review.openstack.org/22686920:04
ttxThe previous version of this was basically saying "whatever the VMT is comfortable with"20:04
ttxThis version is just them actually detailing what they are comfortable with, so ++20:04
*** pballand has quit IRC20:04
*** sridhar_ram has joined #openstack-meeting20:04
dhellmann++20:04
*** yamahata has quit IRC20:04
* dhellmann likes that we are writing things down20:04
ttxobjections ? Otherwise will approve when it reaches 7 votes20:05
annegentleme too20:05
dtroyer++20:05
sdagueyep, this seems pretty concrete20:05
russellbhas 5 so far..20:05
*** penick has joined #openstack-meeting20:05
ttxlets move on, will approve async20:05
ttx#topic Add new project Kosmos20:05
*** openstack changes topic to "Add new project Kosmos (Meeting topic: tc)"20:06
ttx#link https://review.openstack.org/22367420:06
*** dprince has quit IRC20:06
ttxLast week we deferred the decision on this one20:06
ttxsince it may affect the decision on latter topics I moved it up20:06
* russellb is fine with it, but would rather be approving with clear consensus20:06
*** vivek-ebay has quit IRC20:06
ttxThe project and the project teams are sane, the question is more whether we should generally require "some" work to be done before approving project teams20:06
ttxWe generally require that of completely-new project teams (see for example kiloeyes)20:06
sdaguepersonally I'm fine with this, however I don't think we should force it if people are against it20:06
russellband there doesn't seem to be clear consensus, so i'm also happy saying "go do your thing for a bit first"20:06
ttxWe didn't require it for the packaging initiatives (packaging-deb, packaging-rpm...), though20:06
dhellmannI'm on the fence, but leaning to the side of waiting to see what's actually produced so we don't set a bad precedent20:06
dtroyerI think we should no matter the team makeup20:06
*** pballand has joined #openstack-meeting20:06
ttxI'm generally leaning towards requiring "some" work to be present -- it makes judging "are you one of us" a lot straightforward20:06
dtroyerthe project also needs to prove itself20:07
ttxbut then should we kick out packaging-deb which do not even have their repositories set up yet ?20:07
mordredI do not think we need to require "Some" work myself20:07
lifelessso we've set objective criteria up20:07
ttxwhat about packaging-rpm, with its grand total of 4 commits ?20:07
russellbttx: that was probably premature, then20:07
mordredbut I do not feel so strongly about it to argue vehemently20:07
dtroyerme either, but you know, consistency20:07
lifelessbut we've pushed back on some projects because of lack of evidence of meeting the criteria - it just feels really weird to me that we'd not be consistent about that20:07
* mordred does not care about consistency or a set of rules we published20:07
russellbif we go the "needs some work done first", that's fine, i can take the action to propose a guidelines update to make that more clear20:07
sdagueat this point it's only expensive to add things if it's expensive to delete them20:07
* mordred cares about our judgement as humans20:07
jeblairif packaging-* doesn't have anything to show in a cycle or two, we can remove them :)20:07
ttxI think one difference now is that theer is no issue in proving yourself in openstack/* repositories without being official just yet20:07
markmcclainI like the project and contribs, but seems there should be some kind of digital trail20:08
* mordred considers our guidelines to be guidelines and that we are humans and can decide to accept or not accept a set of humans should we choose20:08
funginote that at last check, the deb packaging repos don't even exist yet20:08
ttxso there is no cost in starting the project out of the governance20:08
lifelessmordred: I care about our judgement as humans - but I also care about what we're communicating to the other humans involved20:08
annegentlemordred: but unfortunately that line of thinking means that we are a clique and the cool kids have to do nothing to get in20:08
mordredlifeless: I agree - but I think we can massage our guidelines - I want to make sure we do not become a slave to them20:08
*** dkranz has quit IRC20:08
dhellmannmordred: I would like for us to make sure we're not establishing a clique culture, where we accept any project from "people we know" and put newcomers through some sort of acceptance test -- it's a low enough bar to say, "run for a couple of months and let's see"20:08
ttxLooks like most people are fine waiting, and some people object to approviung. We should therefore delay20:08
jeblairannegentle: i consistently vote to add new projects with no history :)20:08
markmcclainyeah.. concerned we've never expressed the standard20:09
*** hparekh has quit IRC20:09
jgriffithannegentle: +120:09
*** skylerberg has joined #openstack-meeting20:09
sdagueannegentle: is it that? or is it that proven members of the community have some trust which should be portable?20:09
dtroyermordred: we're not a slave, we still have the judgement call of 'how much' needs to be there.. I think it is >020:09
mordredannegentle, dhellmann: I think the only thing left that defines us as people is that the people are part of our set of people20:09
*** hparekh has joined #openstack-meeting20:09
lifelessmordred: sure. So - the first thing is that http://governance.openstack.org/reference/new-projects-requirements.html doesn't talk about guidelines20:09
annegentlesdague: as a minority in this community I have to state what it looks like to me20:09
*** amrith is now known as _amrith_20:09
annegentlesdague: I like trust, I also like earned trust20:09
ttxAnyone strongly objecting to delaying until there is something set up ?20:09
jgriffithI'm +1 on it, my only thought is going forward keep in mind the criteria used here and in other places20:09
*** ayoung has quit IRC20:09
dhellmannmordred: sure, but this is as much about appearances as anything. I can't imagine we'll come back in a month and say no to this team.20:09
mordredwhich is to say - I my vote is to be permissive in this case, but I understand and respect the alternate opinion20:10
ttxthere seems to be more people objecting to approving it, than people objecting to delay it20:10
lifelessI'd be happy to appprove if we go back to the folk we pushed back on and approve them, as they were no less conformant20:10
sdaguefor the record, I do not object to a delay20:10
jeblairmy vote is to include but that's because i _want_ to establish a culture where people start new projects and do them right and fully integrated from the start.20:10
sdaguebut I'd be fine moving forward20:10
anteayaannegentle: well said20:10
annegentleI think you can definitely approve it even with my no vote, right? Just voicing what I needed to say.20:10
*** pballand has quit IRC20:10
sdaguejeblair: ++20:10
mordredjeblair: ++20:10
dhellmannjeblair: fair point20:10
mordredjeblair: that is what I was trying and failing to say20:11
lifelessjeblair: can they not do that without our blessing?20:11
edleafejeblair: yes~20:11
lifelessjeblair: like, what is held back from not-yet-in-governance projects these days?20:11
*** pballand has joined #openstack-meeting20:11
funginow that applying to governance later doesn't imply a git repo rename, it's possible the interest in starting teh project first and then applying will increase20:11
mordredlifeless: voting20:12
jeblairlifeless: services on openstack.org like docs hosting, and some amount of attention and care from other cross-project teams.20:12
ttxsigh, feels like it's when people don't have strong optionions that it's the most difficult to come to a conclusion20:12
mordredlifeless: and that20:12
ttxopinions*20:12
dougwigttx: lol20:12
russellbheh20:12
sdagueso, while we have a voting mechanism, we also aim to be concensus based20:12
ttxquick check -- who strongly objects to delaying ?20:12
sdagueno concensus means we should delay20:12
ttxand who strongly objects to approving ?20:12
jeblairlifeless: like if you want to run ruby on java in your docker, i'm not going to care for a stackforge project, but i'm going to hold openstack projects to a higher standard in terms of ci construction20:13
ttxI don't really care either way. Slight preference for delaying.20:13
russellbsdague: +1 ... ideally with a guidelines followup that clarifies "do at least some work first", which i don't mind adding20:13
sdagueit would be good if one or more of the folks that are pro delaying write those guidelines20:13
sdagueor russellb :)20:13
*** maishsk has left #openstack-meeting20:13
*** maishsk has joined #openstack-meeting20:13
markmcclainrussellb: +120:13
lifelessrussellb: please do20:13
markmcclainI'm happy to work on the guidelines20:14
russellbit'll just be a sentence or 2 to http://governance.openstack.org/reference/new-projects-requirements.html20:14
SpamapSA counter argument to "do at least some work first" is that it's possible corporate sponsors may want a project team to receive TC blessing before starting on a large endeavor.20:14
*** e0ne has joined #openstack-meeting20:14
ttxSo the ONE reason why I prefer to delay is: we'd accept the cool kids and delay the people we don't know and ask them to prove themselves first.20:14
sdagueanyway, it seems like folks that are pro delay probably can best describe what makes them uncomfortable with moving this forward as is20:14
*** harshs has quit IRC20:14
annegentlemy thinking is we have no evidence of "basic interop" or contributions20:14
ttxI think it's simpler to require everyone shows something20:14
dougwigSpamapS: fyi, not an issue in this case.20:14
annegentlenothing measurable yet20:14
annegentleright, just show us something20:14
russellbi actually don't care much, but i'm happy doing the guidelines if that helps get us to better consensus20:14
*** Shrews has left #openstack-meeting20:14
*** fzdarsky has quit IRC20:14
sdaguerussellb: thanks20:15
russellbbut is it just going to have 5 -1s "we shouldn't have to wait" ?20:15
jgriffithI feel strongly that governance should not impact interest/desire to work on the project, I also feel strongly that we should embrace our concept of inclusion20:15
annegentlethanks russellb20:15
russellbif so, that doesn't really get us anywhere20:15
ttxOK, let's delay and have a general rule from now on that the project is started before applying20:15
jgriffithIn other words, what's the point of wating?20:15
lifelessSpamapS: with big tent, if we're doing that, we've gotten the engagement model very wonky20:15
jgriffithIt succeeds or it doesn't20:15
annegentlerussellb: so how do I know that the last three bullets are met with Kosmos?20:15
jgriffithIt has little impact on the TC either way after we get through the process of approving no?20:15
lifelessjgriffith: so why did we ask monasca to wait?20:15
sdaguerussellb: well, I'd give it a shot20:15
russellbok, will do20:16
SpamapSlifeless: I agree 100% with your statement.20:16
dtroyerI don' tthink requiring even a small history doesn't embrace inclusion, as annegentle said, without it the only history we have is personal history and that doesn't reflect what _that_ proiject might do in the future20:16
ttxannegentle: we annegentle ssume they will based on what we know of the team members, which very much feels like a bias20:16
ttxweird tab completion there20:16
jeblairttx: don't we need someone with a +1 to revoke it in order for the motion to fail?20:16
annegentlettx: right20:16
annegentleha20:16
markmcclaindtroyer: right.. we've had other proposed projects that wandered off in teh wrong direction after organizing20:16
ttxjeblair: formally yes, which is why I'd like people to agree on the direction20:16
sdaguejeblair: procedurally can't ttx just table it20:17
* jgriffith lifeless they weren't in the cool-kids club20:17
edleafelifeless: well, they had a definite not-one-of-us history20:17
jeblairsdague: that sounds awfully like a veto20:17
ttxI can table it like swe did others20:17
SpamapSFeels weird to say there's no history available. There's a team somewhere that came up with the idea, and some other team that agrees with the idea. And that sounds like a short history of collaboration between orgs?20:17
sdagueyeh, I do think monasca was actually the inverse here20:17
*** hparekh2 has joined #openstack-meeting20:17
sdaguelots of commit history, very little community history20:17
ttxjeblair: the resolution is still valid, just the timing is bad ?20:17
ttxrather than rejecting those we have been generally tabling them20:17
*** hparekh has quit IRC20:18
*** jhenner has quit IRC20:18
lifelessedleafe: collaboration with what, 3 different contributing organisations20:18
*** jhenner has joined #openstack-meeting20:18
*** elo1 has quit IRC20:18
dtroyerttx: I think that is the right approach.20:18
markmcclainSpamapS: group based policy is an example that started the same with known people/team, but ended up in a place that would be hard for inclusion at this point20:18
lifelessedleafe: resulted from community discussions at summits...20:19
edleafelifeless: I meant the closed meetings, java codebase, etc20:19
*** rossella_s has quit IRC20:19
ttxIf we were to call for a final vote now it would pass, based on current votes20:19
dtroyerfrankly I liked seeing the application right off, it shows intent and makes the history a shorter peocess in my mind anyway20:19
*** elo1 has joined #openstack-meeting20:19
*** rossella_s has joined #openstack-meeting20:19
dhellmanndtroyer: ++20:19
sdagueanyway, I think we agreed on a path forward right20:19
*** sridhar_ram has quit IRC20:19
sdague1) delay20:19
sdague2) write up new guidelines on what is expected20:19
ttxsdague: jeblair objects and calls for a final vote20:19
annegentleI've registered my concerns with the perception and I feel heard. That's how voting works, I think.20:19
edleafeI think the hesitation is because removing is not so easy if they don't meet expectations20:20
sdaguejeblair: is that what's happening?20:20
ttxIf he does I'm hapopy to call for final vote now20:20
jeblairi didn't think that was what i was doing -- i just thought we voted on things.  :)20:20
ttxor happy even20:20
russellbif it goes in, can we still update guidelines to say "we encourage early application" ?20:20
*** sridhar_ram has joined #openstack-meeting20:20
dtroyerrussellb: yes please20:21
russellblet's update guidelines either way, basically :)20:21
sdagueok, I guess I'm just confused. How about we #vote on plan listed above20:21
dtroyerwith whatever history expectations we wind up with20:21
sdaguedelay 1 month and have new guidelines20:21
*** carl_baldwin has quit IRC20:21
dhellmannI don't understand the issue, we table things for more discussion all the time20:21
ttx#startvote Should we delay the vote until the project is set up ? yes, no, abstain20:21
openstackBegin voting on: Should we delay the vote until the project is set up ? Valid vote options are yes, no, abstain.20:21
openstackVote using '#vote OPTION'. Only your last vote counts.20:21
russellbi'd say we should expect a few months of project history (roughly), or we accept this and say we encourage early application like this20:21
sdague#vote yes20:22
ttx#vote yes20:22
dhellmann#vote yes20:22
jeblair#vote yes20:22
russellb#vote yes20:22
dtroyer#vote yes20:22
ttxjeblair: feels less like a veto that way I guess20:22
*** ozstacker has joined #openstack-meeting20:22
markmcclain#vote yes20:22
jeblairttx: yes :)20:22
ttxsdague: thx :)20:22
annegentle#vote yes20:22
ttxclosing in 10 seconds20:22
mordred#vote yes20:22
ttx#endvote20:22
jgriffith#vote no20:22
openstackVoted on "Should we delay the vote until the project is set up ?" Results are20:22
openstackyes (9): ttx, annegentle, jeblair, russellb, sdague, mordred, dhellmann, dtroyer, markmcclain20:22
ttxdammit john20:23
russellbjgriffith: just missed it.20:23
annegentleaw20:23
jgriffithOh well20:23
sdagueit will be in the minutes20:23
russellb:)20:23
ttx#agreed delay the vote until the project is set up20:23
sdagueand it doesn't impact the actual vote20:23
ttxsdague: agreed20:23
jgriffithObviously doesn't matter anyway20:23
*** carl_baldwin has joined #openstack-meeting20:23
lifeless#vote yes20:23
ttxlet's move on20:23
lifelessblink and you mis it20:23
ttx#topic Add Juju Charms for Ubuntu to OpenStack20:23
*** openstack changes topic to "Add Juju Charms for Ubuntu to OpenStack (Meeting topic: tc)"20:23
ttxSo the decision on Kosmos kind of sets a precedent here20:24
russellbsame situation?20:24
dougwigthe wording of that is odd, since it is setup/created/cookiecutter/irc/etc, so please clarify what it means.  i'll assume "show me some code".  sdague, 1 month is likely too short in this case, due to it being summit month.20:24
ttxThis is imho comparable to other packaging efforts we have in the big tent20:24
ttxThere are no existing repositories though, so we could kosmos this one20:24
russellbdougwig: i was thinking "a few months"20:24
sdagueis it the same situation? I thought they had a ton of code20:24
annegentlettx: verbed a noun20:24
russellbsdague: doing it in openstack though?20:24
dougwigrussellb: agree20:24
ttxannegentle: is that dirty ?20:24
annegentlenah just funny to me20:24
annegentle:)20:24
sdaguerussellb: ok, so is it a delay until there is a project-config import?20:24
russellbdougwig: but we'll have a review following up on this agreeing on some rough guideline20:24
lifelessthre's a weird thing20:24
lifelessthe commit message makes me think its not open20:25
ttxThe only original thing is the integration testing being done on Canonical infrastructure20:25
dhellmannI noticed the GPL mentioned here, does that present any issues since this isn't part of the actual applications?20:25
*** stevemar has quit IRC20:25
lifeless" the core reviewers on20:25
lifelesseach repository may be derived from the company developing the charm."20:25
lifelessmaybe I'm reading that wonky20:25
*** ayoung has joined #openstack-meeting20:25
dhellmannyeah, that also struck me as odd20:25
lifelessbut it sounds like a company-lock-on-the-repo20:25
lifelessjamespage: ^ ?20:25
sdagueoh, hey, I guess I missed that bit20:25
russellb"Charms are currently licensed under GPL v3."20:26
fungiperhaps the "may be derived from" is not definitive and merely a starting point20:26
*** waynr has quit IRC20:26
*** apoorvad has joined #openstack-meeting20:26
ttxHow about we table it since there is nothing yet -- and ask for clarification in the mean time ?20:26
dhellmannrussellb: yeah, that's what I meant -- is that a problem since the charm code isn't part of the applications we deliver that have to be apache 2?20:26
lifelessthe GPL v3 is ok per our governance doc requirements - though its definitely unusual20:26
*** bvandenh has joined #openstack-meeting20:26
russellbdhellmann: our guidelines just say we prefer apache 220:26
russellbdhellmann: just require "an open source license"20:26
dhellmannrussellb: the bylaws are more specific, aren't they?20:27
russellbi'd certainly *prefer* apache 2 ...20:27
sdagueright, so that seems fine20:27
russellbdhellmann: good question20:27
*** salv-orlando has quit IRC20:27
*** ksavich has quit IRC20:27
dhellmannthough those only apply to trademarked code, iiuc, which is why I pointed out this is not application code20:27
sdagueI thought the bylaws changed on that fron20:27
*** bryan_att has quit IRC20:27
ttxHow about we table it since there is nothing yet -- and ask for clarification in the mean time ?20:27
dtroyer++20:27
lifeless+1 on tabling, I'll raise my questions on the review20:27
lifelessfungi: you're likely right, but if so why mention it at all?20:27
dhellmannarticle VII in https://www.openstack.org/legal/bylaws-of-the-openstack-foundation/20:27
ttxThe bit on ntegration testing being done on Canonical infrastructure is also making my openness radar buzz20:28
dhellmannsdague: did they?20:28
jeblairlifeless, fungi: agreed -- likely overspecification but good to double check20:28
lifelessfungi: just say 'initial core reviewers will be the folk that create each charm' or something20:28
*** dims has quit IRC20:28
fungiyep20:28
dhellmann7.1.b seems to only apply to the tc-approved-release, so I think we're ok, I just wanted to get confirmation20:28
jeblairttx: i wonder if there is a technical reason they can't do it upstream?20:28
lifelessfungi: *company* is a very odd thing here :)20:28
EmilienMfwiw, we asked fuel to collaborate with os-infra, we probably might want to do the same with charms.20:28
dhellmannttx: third-party ci?20:28
*** stevemar has joined #openstack-meeting20:29
lifelessjeblair: its all part of OIL20:29
ttxjeblair, dhellmann: sure, I just want to make sure that's a technical reason20:29
*** dims has joined #openstack-meeting20:29
jeblairttx: also, it is worth noting that despite being one of the earliest third-party ci operators, they've never been good about reporting upstream...20:29
lifelessjeblair: their proprietary 'openstack interoperability lab' that they sell testing-on-and-via to companies20:29
jeblairdhellmann, ttx: so i would not even assume that text means "we will report our local testing upstream"20:29
*** fzdarsky has joined #openstack-meeting20:29
russellbhttps://www.openstack.org/legal/bylaws-of-the-openstack-foundation/ "INTELLECTUAL PROPERTY POLICY" mentions Apache 2 quite specifically20:29
sdagueI guess that's a good point for clarification20:30
russellbbut i need a bit more time to parse it in pedantic mode20:30
jeblairlifeless: yeah, concerning.20:30
ttxok, I think we have a path forward here20:30
lifelessjeblair: its very much bare metal based, and upstream infra have no baremetal facilities today AIUI - including baremetal routers etc20:30
dhellmannjeblair: fair20:30
mordredlifeless: that may be true - but I thnk a good faith effort to come up wiht a workable infra soluiton would be nice20:30
lifelessjeblair: so AIUI, at least some of the charms aren't able to be exercised in a virtual environment20:30
*** nadya has quit IRC20:30
ttx#agreed Juju charms application delayed until there is something substantial in the repositories (they can be set up without being "official" now). We'll clarify other specific points in the mean time20:30
annegentleI was still parsing the OIL acronym20:30
annegentle:)20:30
russellbit says we distributed the "approved release" under the apache license.  it also says we accept contributions with an agreemen that lets us redistribute under the apache license.20:31
EmilienMthe least we can ask is a third party CI where all logs and access are open20:31
lifelessmordred: / jeblair: / fungi: has Canonical discussed that with infra?20:31
fungilifeless: not to my knowledge20:31
dhellmannannegentle: what did you get? :-)20:31
mordredlifeless: no. there has never been any attempt at ocooperation20:31
ttxMoving on...20:31
annegentleOIL=OpenStack Interop Lab20:31
*** apoorvad has quit IRC20:31
ttx#topic CloudKitty application for Big Tent20:31
*** openstack changes topic to "CloudKitty application for Big Tent (Meeting topic: tc)"20:31
dhellmannannegentle: thanks20:32
fungirussellb: yes, the cla may not be sane for gpl projects?20:32
lifelessdhellmann: I expanded it on my next line :)20:32
ttx#link https://review.openstack.org/22520120:32
jeblairannegentle: of course we have the Wide Area Testing and Experimental Reporting project20:32
dhellmannlifeless: ah, missed that20:32
ttxOK, so CloudKitty. This feels rather straightforward big-tent to me20:32
annegentlejeblair: may they ever mix20:32
ttxthe project has been around for a while in the OpenStack community and is even used in production somewhere20:32
russellbttx: ++20:32
annegentlettx: yep agreed20:33
ttxobjections, questions ?20:33
ttxI think we have the PTL around20:33
russellbfungi: yeah ... and it may just mean that this could never be part of the "TC approved release", which is probably fine20:33
*** salv-orlando has joined #openstack-meeting20:33
sheeprineYes, I'm here.20:33
*** waynr has joined #openstack-meeting20:33
ttxsheeprine: o/ welcome20:33
jeblairhow could you say no to something called CloudKitty?20:34
*** vivek-ebay has joined #openstack-meeting20:34
ttxone more approval and it's in20:34
jeblairwith big eyes like that?20:34
russellbsheeprine: i request a cute kitten logo20:34
ttxjeblair: the name fails annegentle guidelines with capitalization :)20:34
lifeless+1 fro me on the spec20:34
annegentlettx: lol oh so true20:34
jeblairannegentle kicks kittens!20:34
maishsk:)20:34
ttxok, we have a winner, approving now20:34
markmcclainttx: we're at 920:34
russellbwelcome, cloudkitty!20:35
russellbmeow.20:35
annegentlecloudkitty!20:35
ttxkitty kitty20:35
annegentlenow go change the capitalization20:35
sheeprinethanks20:35
* dhellmann wants a mascot sticker at the summit20:35
sheeprineI'll work on the capitalization.20:35
* ttx continues to rush through the busy agenda20:35
russellbafter you make stickers20:35
*** Sukhdev has joined #openstack-meeting20:35
*** DericHorn-HP has quit IRC20:35
ttx#topic Remove MagnetoDB from OpenStack20:35
*** openstack changes topic to "Remove MagnetoDB from OpenStack (Meeting topic: tc)"20:35
sheeprineWe've got stickers and more for the summit ;)20:35
ttx#link https://review.openstack.org/22474320:35
dhellmannsheeprine: \o/20:35
ttxWe discussed this one last week20:36
ttxThere is general agreement that we should remove MagnetoDB, we just disagreed on how to encode that in the governance repository20:36
ttxNot much progress or proposals on the review this week20:36
*** yamahata has joined #openstack-meeting20:36
ttxShould we just have a retired-teams.yaml and move the entries there, with some timestamp to account for expiration of entries after the ATC delay ?20:36
*** gordc has joined #openstack-meeting20:36
dhellmann++20:36
russellbit'd be good book keeping, i think20:36
dtroyer++   it fits with the rest of our dont-delete-history20:36
dhellmannI'll propose that if folks want20:36
sdagueretired-teams.yaml sounds good to me20:36
russellbdhellmann: thanks!20:36
ttx+120:37
ttxif you do it while we continue the meeting we could even approve it :)20:37
* dhellmann starts typing20:37
sdagueor projects-emeritus.yaml :)20:37
jeblairi mean, i'd love it if git were the history, but i'm okay with retired-teams until our schema stabilizes20:37
*** bswartz has quit IRC20:37
annegentleattic? /me stops naming things20:37
ttxjeblair: yeah, that was my original thinking, but people got worried20:38
jeblair(to bikeshed, it really ought to have a name relation to projects.yaml though)20:38
annegentleI mean, do we still move code to the attic if a team retires?20:38
russellbthe worry was about tooling around calculating ATC status wasn't it?20:38
russellbnot sure it's a real problem in this case20:38
ttxok, let's move on while dhellmann types, and come back to it in a few20:38
*** baoli has joined #openstack-meeting20:38
russellbbut could be eventually *shrug*20:38
jeblairrussellb: yep20:38
ttx#topic Cross-project track at Mitaka design summit: status update20:38
*** openstack changes topic to "Cross-project track at Mitaka design summit: status update (Meeting topic: tc)"20:38
ttxFlavio set October 9th for the deadline to propose things at http://odsreg.openstack.org/20:38
sdagueright, in this case it potentially impacted 1 atc, but I could imagine there being more20:38
ttxWe have 17 proposals there, not sure if all the etherpad was copied or not20:39
ttxIdeally the cross-project workgroup volunteers would do the heavy lifting between the 9th and the 13th, so that we have somethign to discuss and approve at the Oct 13th TC meeting20:39
ttxAnd move to scheduling quickly afterwards20:39
*** notnownikki has quit IRC20:39
ttxDoes that sound like a plan ? Probably means a quick meeting on the Monday20:39
ttxof the cross-project track volunteers20:39
sdaguedamn you flaper87 for closing it on a friday instead of a thursday20:40
*** electrocucaracha has quit IRC20:40
ttxsdague: I know, right20:40
anteayadates are important20:40
*** electrocucaracha has joined #openstack-meeting20:40
*** cdelatte has quit IRC20:40
*** 32NAAGPES has quit IRC20:40
sdagueI think more importantly, are there topics we feel need to be addressed that aren't getting proposed20:40
*** MaxPC has quit IRC20:40
lifelessI can do monday20:41
*** thangp has quit IRC20:41
dhellmannttx: updated20:41
lifelesssdague: ITYM wednesday, since a meeting on your friday is my saturday :)20:41
sdague:)20:41
ttxeveryone: please review https://review.openstack.org/#/c/224743/20:42
dhellmannI'm happy to bikeshed the "retired-on" field in a separate patch20:42
*** jruano has joined #openstack-meeting20:42
*** ildikov has quit IRC20:42
ttxwe'll go back to topic brainstorming at the end of the meeting in Open Discussion. We can also interpret the bylaws on GPLv3 then20:42
ttxone more...20:43
sdagueit seems like a good time for every TC member to put their nickle down on a cross project issue they feel is getting neglected20:43
ttxsdague: I filed one but I'll definitely give it another thought session20:43
*** skylerberg has quit IRC20:43
*** vgridnev has quit IRC20:44
ttxok, 7 votes, I can approve the MagnetoDB removal20:44
ttxlast call20:44
lifelesssec20:44
lifelessthere20:44
fungii'll go ahead and force-merge the related retirement change in project-config20:44
dhellmannfungi: that was the patch to delete all the code?20:45
fungiyep. and i'll also abandon open changes20:45
fungiwe have some infra documentation (maybe already merged?) on returing repos now20:45
dhellmannok. I was a little surprised by that, but I guess it makes sense20:45
fungiretiring too20:45
jeblairdhellmann: we have had users not realize that they are using abandoned projects, so we are striving to make it more clear20:46
ttxok done20:46
annegentlefungi: thanks for that20:46
ttx#topic Communications workgroup report20:46
*** openstack changes topic to "Communications workgroup report (Meeting topic: tc)"20:46
dhellmannjeblair: this is certainly one way to do that :-)20:46
ttxannegentle: anything to report ?20:46
annegentleblog post done last week, have to admit I had missed 2 from the prior 2 weeks ago so it was chockful of info :)20:46
*** pballand has quit IRC20:46
*** neelashah has joined #openstack-meeting20:47
annegentledo you think we should do one flaper87 to get cross-project summit proposals by 10/9?20:47
jeblairannegentle: that sounds like a good idea20:47
ttxthat wouldn't hurt. But could wait next week meeting maybe20:47
sdagueit seems like getting one out this week to beat that drum would be good20:47
annegentle#link http://www.openstack.org/blog/2015/09/technical-committee-highlights-september-25-2015/20:47
sdaguegiven that this friday is the 2nd20:48
dhellmann++20:48
annegentlelet's see the 9th is next Friday... hm20:48
*** su_zhang has quit IRC20:48
*** ildikov has joined #openstack-meeting20:48
annegentleWe did mention it at the end of that post ^^20:48
annegentleso we're probably covered20:48
ttxok, then maybe wait and do a last reminder one next week ?20:48
ttxwith things approved today and next week ?20:48
annegentleor tweet tweet?20:49
annegentlewhere's my partner in crime flaper87? :)20:49
*** pballand has joined #openstack-meeting20:49
annegentleI can see blogging by next Wed.20:50
ttxwe might raise a thread on the ML around TC candidates too20:50
*** okrieg has quit IRC20:50
*** xarses has joined #openstack-meeting20:50
*** su_zhang has joined #openstack-meeting20:50
ttxok, moving to open discussion since we are talkign about everything at the same time now20:50
ttx#topic Open discussion20:50
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:50
*** MarkAtwood has quit IRC20:50
ttxEveryone: Tomorrow is the last day to submit your TC candidacy if you're interested in joining us20:50
ttxAlso there will be a joint TC/Board meeting in Tokyo on the Monday, starting at 2:30pm20:50
ttxAt 4:30pm we'll be joining the "Women of OpenStack networking event" (4:30pm - 7:30pm)20:50
ttxmark your calendars if you're a member of running for election20:51
PietAt some point, we need to chat about how surveys are distributed in the community.  Not sure if this is the forum.20:51
ttxPiet: probably not. We don't do surveys.20:51
Pietttx: k20:51
lifelessttx: I was going to do one on the devs20:51
lifelessttx: but I ran out of steam - there was lots of interest in it though20:52
ttxlifeless: about terminal width ?20:52
lifelessttx: hah, no. I'll dig up a thread pointer for you20:52
lifelessttx: but - I was thinking that the foundation which already runs e.g. the user survey might be a good body to coordinate such things20:52
lifelessttx: do you know anyone there to chat with about that?20:52
annegentlePiet: cross-project meeting though sounds right20:52
russellblet's ask about editor preferences too20:52
lifelessrussellb: so actually that was one of the questions I was going to ask20:53
ttxlifeless: I can relay the concerns to staff if we voice them20:53
lifelessrussellb: to put the .gitignore questions to bed20:53
*** ddeva has joined #openstack-meeting20:53
russellbbut only have "vim" as a choice20:53
lifelessttx: so - the question is, is there someone at the foundation with the time to run a developer survey, if we put the questions together ?20:53
markmcclainrussellb: vim and "other" I like it20:53
ttxin Piet's case maybe the "openstack-foundation" ML is the right forum20:53
Pietannegentle: sounds good.  I want to make sure that we are able to be responsive to the project teams.  Adding a few questions to a bi-annual survey may not get us there.20:53
ttxsince most surveys are coming from the Foundation surveymonkey account20:54
annegentlePiet: ttx is also right, surveys through Foundation20:54
*** aranjan has joined #openstack-meeting20:54
anteayawell part of it is that Piet doesn't have access to the fondation survey data20:54
anteayaand would like to have some data20:54
Pietannegentle: I'm pushing back on that assumption20:54
anteayaif I understand correctly Piet20:54
* ttx looks at Foundation bylaws and GPLv320:54
lifelessfor clarity, Piet and I are talking totally different things :)20:55
*** VW_ has joined #openstack-meeting20:55
sdagueyeh, so I swore there was something in Atlanta about it just needing to be open source20:55
*** VW has quit IRC20:55
sdaguehowever, I can't find it anywhere now20:55
PietWe generally try to focus on small samples, but occasionally need to do surveys20:55
russellbttx: Article 7.1 in particular20:55
annegentlePiet: lifeless: yes still sounds like surveys are cross-project and Foundation areas20:55
sdagueso maybe GPLv3 is a blocker20:55
PietAnd the foundation has not provided raw data20:56
annegentlenot something the TC mediates20:56
ttxlooks like a question for foundation legal20:56
russellb7.1 (b) sayd "TC approved release", so it would at a minimum mean something non-apache2 could never be in TC approved release20:56
lifelessannegentle: so openstack-foundation is the place to ask ?20:56
russellb7.1 (a) is much less clear though20:56
russellbttx: ++20:56
sdagueright, in the TC approved release, that seems fine20:56
ttxrussellb: yeah, b is clear, a is lawyerese20:56
annegentlelifeless: for your Q I would log a ticket in their system or ask directly on the openstack-foundation list20:57
sdaguebut aren't there things in openstack-infra that are not apache2?20:57
ttx"may adopt additional contributor license agreements as may be appropriate for certain organizations or contributions to secure a license on terms which will permit distribution under the Apache License 2.0" seriously20:57
russellbyeahhhh20:57
*** jprovazn has quit IRC20:57
russellb"we use a cla, and whatever else want to ensure we can distribute under apache 2"20:57
russellbi think..20:57
clarkbsdague: I don't think so20:57
sdagueright, which is the whole CLA trump the world thing20:57
*** MeganR has joined #openstack-meeting20:57
jeblairsdague, russellb: i believe we have heard from the foundation's lawyer that things outside the release are gpl-okay20:57
*** MeganR has left #openstack-meeting20:57
sdaguespeaking of which, have we heard recently about board / tc meeting agenda20:58
sdagueand the CLA vs. DCO thing20:58
russellbthis needs to be added to https://wiki.openstack.org/wiki/LegalIssuesFAQ20:58
ttxsdague: I'm taking up suggestions for the BoD/TC meeting agenda :)20:58
*** ijw has joined #openstack-meeting20:58
lifelessannegentle: 'their system' ?20:58
sdaguebecause I believe the last email statement around that was it would be voted on in Tokyo20:58
jeblairttx: it should be a standing agenda item :(20:58
sdaguettx: ok, that's my first suggestion20:58
*** VW_ has quit IRC20:58
dhellmannjeblair: ++20:59
dhellmannsdague: ++20:59
annegentlelifeless: they have a ticketing system for support requests, sorry I can't recall the email address. I use it for logo@openstack for example20:59
jeblairsdague: agreed, that is my expectation20:59
ttxI have no idea what the agenda of the Board part of the meeting is. Maybe mordred or russellb know20:59
annegentlelifeless: might be info@openstack?20:59
*** smcginnis has joined #openstack-meeting20:59
russellbno updates re: DCO20:59
*** VW has joined #openstack-meeting20:59
sdagueo_O20:59
russellbno updates available to me anyway20:59
*** skraynev_ has joined #openstack-meeting20:59
sdaguerussellb / mordred could you push on that?20:59
russellblegal affairs committee kind of blocked it20:59
russellband insisted they needed a private lawyer only meeting to move forward20:59
cpallaresttx: o/20:59
jeblairhttps://wiki.openstack.org/wiki/Governance/Foundation/26Oct2015BoardMeeting21:00
russellbin between last meeting and next one (tokyo)21:00
ttxcpallares: o/21:00
russellbbut i don't know if that has happened ...21:00
jeblairno agenda listed yet21:00
jeblairor, very little of one21:00
markmcclainrussellb: really? disappointing21:00
ttxok, we are running out of time21:00
sdaguebecause, I'll be honest, if this isn't getting a floor vote in Tokyo, I'm not really sure why the TC is going to the board meeting21:00
cpallaresttx: Can we discuss CoC next week?21:00
ttxrussellb, mordred: could you get an updated status on that ?21:00
russellbsdague: i'm going into it expecting a vote21:00
cpallaresttx: Should I come back for the next open discussion?21:00
*** s3wong has quit IRC21:00
mordredttx: can try21:00
sdagueas we've been asking about this for 3 cycles now21:00
ttxcpallares: yes please21:00
russellbthat's what we left the last meeting with ...21:01
sdaguerussellb: ok21:01
* mordred agrees with russellb21:01
russellb"let people get any last questions answered now, and we vote in tokyo"21:01
ttxok time is up21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Sep 29 21:01:22 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-09-29-20.01.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-09-29-20.01.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-09-29-20.01.log.html21:01
anteayarussellb: the last foundation meeting?21:01
russellbanteaya: yes21:01
jokke_#startmeeting crossproject21:01
openstackMeeting started Tue Sep 29 21:01:38 2015 UTC and is due to finish in 60 minutes.  The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
anteayarussellb: thankyou21:01
*** openstack changes topic to " (Meeting topic: crossproject)"21:01
openstackThe meeting name has been set to 'crossproject'21:01
ttxsdague: agree that it's not the board top priority.21:01
*** earlephilhower has joined #openstack-meeting21:01
jokke_courtesy ping for david-lyle flaper87 dims dtroyer johnthetubaguy rakhmerov21:01
*** Sisir has joined #openstack-meeting21:01
jokke_courtesy ping for smelikyan morganfainberg adrian_otto bswartz slagle21:01
jokke_courtesy ping for adrian_otto mestery kiall jeblair thinrichs j^2 stevebaker21:01
jokke_courtesy ping for mtreinish Daisy Piet notmyname ttx isviridov gordc SlickNik21:01
jokke_courtesy ping for cloudnull loquacities thingee hyakuhei redrobot dirk TravT21:01
*** apoorvad has joined #openstack-meeting21:02
jokke_courtesy ping for vipul lifeless annegentle SergeyLukjanov devananda boris-42 nikhil_k21:02
notmynamehere21:02
j^2o/21:02
morganstevemar, ^21:02
david-lyleo/21:02
stevebaker \o21:02
jroll\o21:02
SergeyLukjanovo/21:02
Rockygo/21:02
smcginniso/21:02
devanandao/21:02
* morgan has delegated PTL things to stevemar where at all possible. but is lurking21:02
* fungi wants a discourteous ping21:02
gordco/21:02
devanandaping for jroll too21:02
jokke_Good evening Ladies and Gentleman ... This is cross Project Weekly Meeting and I will be your host tonight ;)21:02
jeblairjokke_: should probably go ahead and s/jeblair/fungi/ in the pingy thingy21:02
devanandaalso, my battery may die any minute :(21:02
docaedoo/21:02
fungipingy thingy!21:02
xarses\o21:02
morganfungi OMG PING SHEESH (better?)21:02
jrolldevananda: double \o then!21:02
morganfungi ;)21:02
* bknudson lurks21:02
*** sridhar_ram has quit IRC21:02
* EmilienM can't attend today, will catch up logs21:02
fungimorgan: much21:02
elmikoo/21:02
stevebakeralso s/stevebaker/skraynev/21:02
jrollfungi: I prefer "annoying loud ping for..."21:02
jokke_#topic Review of past action items21:02
*** openstack changes topic to "Review of past action items (Meeting topic: crossproject)"21:02
fungihah21:02
lifelesso/21:03
*** hemna is now known as hemnafk21:03
*** ijw has quit IRC21:03
* edleafe is creepily lurking21:03
stevemaro/21:03
*** s3wong has joined #openstack-meeting21:03
jokke_ttx: only action item was for you last week around the deprecation communications21:03
skraynev_o/21:03
ttxI did communicate21:03
* ttx picks up link21:03
jokke_ttx: you have anything else around that or do we just move on?21:04
* Rockyg slaps a lurking creep21:04
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-September/075608.html21:04
bknudsonis there a quick summary of the deprecation policy we should follow?21:04
ttxjokke_: nope I'm done21:04
edleafeouch!21:04
ttxbknudson: you don't have to follow it21:04
jokke_ttx: thanks21:04
ttxbknudson: you can opt to declare that you will follow it.21:05
*** whenry has quit IRC21:05
*** Sisir has quit IRC21:05
ttxand by you I mean a project team21:05
bknudsonI follow it21:05
bknudsonoh21:05
*** Sisir has joined #openstack-meeting21:05
ttxit's about setting expectations downstream21:05
*** harshs has joined #openstack-meeting21:05
ttxanyway, moving on, feel free to hiut me with questions about it21:06
ttxhit*21:06
jokke_ttx: has that been communicated towards downstream some other ways that the e-mail thread you posted?21:06
* loquacities is here, running late sorry21:06
jokke_#topic Team announcements (horizontal, vertical, diagonal)21:06
*** openstack changes topic to "Team announcements (horizontal, vertical, diagonal) (Meeting topic: crossproject)"21:06
stevemardiagonal eh21:07
*** sridhar_ram has joined #openstack-meeting21:07
ttxjokke_: it will be once enough projects asserted it21:07
ttxOn the release management front, we have only *2 weeks* before the end of the liberty dev cycle21:07
jokke_ttx: want to continue right away and give us latest from release?21:07
jokke_ttx: thnx21:07
ttxWe have release candidates for all projects except Swift (ETA end of week)21:07
ttxWe'll have a number of RC respins to include updated translations next week21:07
ttxWe just branched the requirements stable/liberty branch, so we are no longer freezing requirements master branch.21:08
*** mudassirlatif_ has joined #openstack-meeting21:08
ttxso all is progressing nicely so far21:08
*** aysyd has quit IRC21:08
ttxwe haven't broken anything yet21:08
stevemarttx: we will probably have rc2 for keystone21:08
jokke_gr821:08
bknudsonare we capping reqs in stable/liberty21:08
stevemarsometime next week21:08
ttxAs usual, if you have a red flag, come bring it in #openstack-relmgr-office. We collect them21:08
*** ddeva has quit IRC21:08
*** samueldmq has joined #openstack-meeting21:08
clarkbbknudson: no, the constraints file should handle that instead21:08
*** hemna has joined #openstack-meeting21:09
bknudsonnice.21:09
skraynev_ttx: when will be window for rc2 ?21:09
ttxstevemar: we can sync it with the translations last import21:09
stevemaryup21:09
dhellmannttx: dims and mtreinish suggested branching grenade and devstack before making any more requirements changes21:09
ttxskraynev_: depends on the case. The RC respins for translations will be all done by Thursday next week21:09
jungleboyjo/21:09
mtreinishdhellmann: well I should rephrase, we should do that except for where I proposed the reqs changes21:10
ttxIt's geenrally a good thing to have nothing on the last week21:10
mtreinishbecause I'm impatient21:10
skraynev_ttx: got it. thx21:10
*** raildo is now known as raildo-afk21:10
dhellmannmtreinish: some patches are more equal than others? :-)21:10
ttxfrees up time to handle crisis things21:10
*** shihanzhang has quit IRC21:10
clarkbmtreinish: we also need to add in the new grenade branch stuff and apply liberty jobs to the branchless repos (like tempest)21:10
*** ociuhandu has joined #openstack-meeting21:10
jokke_jungleboyj: did you have something around the release or announcement to make?21:10
clarkbmtreinish: is that something that QA wants to hanlde or should infra just go through and do it (note it should be almost identical to last cycles changes)21:11
*** mudassirlatif has quit IRC21:11
*** mudassirlatif_ is now known as mudassirlatif21:11
mtreinishclarkb: yeah, that goes hand in hand with doing all the branching stuff21:11
*** shz has joined #openstack-meeting21:11
mtreinishclarkb: either or, we'll be working on it together anyway21:11
clarkbok just let me know what I can help and we go from there21:11
fungii would be thrilled if qa tackles the job config changes for it, but am happy to assist21:11
mtreinishthere are changes on both sides that needs to happen21:11
mtreinishfungi: I think I did them for liberty21:11
mtreinishthe tempest ones at least21:12
fungiokay, great21:12
jungleboyjjokke_: No, just running late.  Sorry.21:12
jokke_jungleboyj: ah, welcome21:12
mtreinisherr s/libery/kilo it's all the same anyway21:12
jokke_ok, lets move on21:12
jokke_#topic Service Catalog Standardization21:13
*** openstack changes topic to "Service Catalog Standardization (Meeting topic: crossproject)"21:13
jokke_#link https://review.openstack.org/18139321:13
stevemarohhh nice21:13
*** alexpilotti has joined #openstack-meeting21:14
jokke_annegentle: stage is yours21:14
*** bltavares_ has quit IRC21:14
morganstevemar (this is why you needed to be here)21:14
stevemarsdague and i had a nice chat about this topic in the morning ^21:14
*** bltavares has joined #openstack-meeting21:15
jokke_sdague: you wanna take this instead?21:15
*** gampel has quit IRC21:15
*** geoffarnold has joined #openstack-meeting21:15
stevemarjokke_: we wrote some ideas here: https://etherpad.openstack.org/p/mitaka-service-catalog21:15
stevemar#link https://etherpad.openstack.org/p/mitaka-service-catalog21:16
jokke_stevemar: thnx for that21:16
dhellmannthat looks like two highlighter markers got into a fight21:16
* dhellmann turns off author colors21:16
stevemarbasically we want to fix up for service catalog, theres a lot of weirdness in it21:16
morgandhellmann: hehehe21:16
*** gampel has joined #openstack-meeting21:17
bknudsonwe have a spec and an etherpad? Are these the same thing?21:17
stevemarbknudson: there is a spec21:17
stevemarit's 1 link up21:17
*** Leom has quit IRC21:17
stevemarbknudson: https://review.openstack.org/#/c/181393/ you've reviewed it21:17
bknudsonis the etherpad going to wind up in the spec?21:17
morganbknudson: etherpad is more general brainstorm on what needs to happen, spec is moving towards finalized "plan"21:17
bknudsonthey look different21:17
*** rtheis has quit IRC21:17
morganbknudson: afaik21:17
stevemarbknudson: probably, we're just writing out ideas21:17
stevemarmorgan: ++21:18
*** Leom has joined #openstack-meeting21:18
jokke_stevemar: yes that was the question, so are these two competing, completing each other or why two different mediums?21:18
stevemarjokke_: no, etherpad was just a brain storm, sorry if it's causing confusion21:18
jokke_ok thnx21:18
bknudsonok... not sure why I was reviewing the spec then.21:19
bknudsonseems like we haven't decided what we're going to do so maybe the spec needs to start over again.21:19
stevemari think the pain point of the spec is that its really hard for application developers to trust what's in the service catalog21:19
*** bltavares has quit IRC21:19
jokke_so the spec had 2x +2 there already today, seems that we got new version of this since21:20
lifelessAm I looking in the wrong place for the agenda? https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda doesn't mention the service catalog21:20
dhellmannlifeless: there was an email21:20
*** gampel1 has joined #openstack-meeting21:20
lifeless[I mean, its good to talk about it, but ECONFUSED]21:20
jrolllifeless: http://lists.openstack.org/pipermail/openstack-dev/2015-September/075731.html21:20
*** tfukushima has quit IRC21:21
jokke_lifeless: that's my mistake ... I did send the agenda out and forgot to save the wiki change I did for these :(21:21
lifelessjokke_: ah, that makes more sense. No worries.21:21
jokke_all: sorry for that21:21
*** kzaitsev_mb has joined #openstack-meeting21:21
stevemarlifeless: not like there is much on the agenda :)21:21
lifelessstevemar: yes, but more than the wiki said :)21:22
dhellmannlifeless: note your spec is up next :-)21:22
lifelessdhellmann: indeed; I was looking to see if it was ...21:22
*** gampel1 has quit IRC21:22
*** gampel has quit IRC21:22
*** baoli has quit IRC21:22
lifelessback to the catalog - sorry for the distraction21:22
*** baoli has joined #openstack-meeting21:22
dhellmannjokke_: is this spec ready for final approval, or does it need more work?21:23
*** gampel has joined #openstack-meeting21:23
xarseswhat about returning multiple endpoints so client's don't require a LB?21:23
jokke_dhellmann: that was actually my question as well ... this morning there was 2x +2 but it seems that we have new version21:24
jokke_and there is still full brainstorming going on21:24
xarsesalso token containing the catalog causes alot of size problems in production21:24
stevemarxarses: yup!21:24
dhellmannxarses: see line 14 of the etherpad21:24
* ttx reapplies +221:24
jokke_and apparently the e-mail did not reach either annegentle nor sdague :(21:24
bknudsonkeystone supports ?nocatalog21:24
bknudsonwhen getting the token21:24
*** vgridnev has joined #openstack-meeting21:24
dhellmannjokke_: ETOOMANYMEETINGS21:24
stevemarbknudson: we need a way to get the catalog without authenticating21:24
xarsesdhellmann: ya, I see 14, but that doesn't resolve getting it out of the token21:25
bknudsonwith endpoint filtering you need the scope so that requires authenticating21:25
jokke_so should we leave this for now and move to the next one?21:25
stevemarbknudson: we only *need* to authenticate because there are silly tenant IDs in some URLs in the catalog21:25
jungleboyjdhellmann: +++21:25
*** ddeva has joined #openstack-meeting21:25
ttxjokke_: yeah, bad timing21:26
jokke_ok, moving on21:26
jokke_#topic Backwards compatibility for clients and libraries21:26
*** openstack changes topic to "Backwards compatibility for clients and libraries (Meeting topic: crossproject)"21:26
jokke_#link https://review.openstack.org/22615721:26
jokke_lifeless: you're up!21:26
*** mudassirlatif has quit IRC21:27
lifelessoh hai21:28
*** gampel has quit IRC21:28
lifelessso there's a couple of intertwined things here21:28
*** balajiiyer has quit IRC21:28
*** adahms has quit IRC21:28
lifelessone is raising the bar slightly on our backwards compat story for both api clients and libraries21:28
*** mudassirlatif has joined #openstack-meeting21:28
*** kzaitsev_mb has quit IRC21:28
*** maishsk has quit IRC21:28
lifelessfor clients we already promise it but we don't test it21:28
*** ayoung has quit IRC21:29
lifelessfor libraries we haven't really made a promise21:29
*** aranjan has quit IRC21:29
lifeless(and I think we need to)21:29
lifelessthe second thing is that we have branches of all these things21:29
*** kzaitsev_mb has joined #openstack-meeting21:29
lifelessand it makes consuming them harder - and if we're properly testing our backwards compat story, we may well not need them21:29
*** jruano has quit IRC21:29
*** baoli has quit IRC21:30
lifelessits possible that they could be two specs, but I spent a bit of time poking at making them separate proposals and it didn't really work for me21:30
*** mudassirlatif has quit IRC21:30
dhellmannwe started making branches because the backwards compatibility testing was hindering our forward progress as we rolled forward with dependencies and new features21:30
dhellmannat least, that was part of it21:30
bknudsonwe're planning to do a keystoneclient 2.0 that removes deprecated stuff21:31
*** hashar has quit IRC21:31
lifelessdhellmann: so we have to do multi-step dances on all changes anyway21:31
lifelessbknudson: sure, thats fine - my proposal specifically permits tht21:31
jokke_dhellmann: correct me if I'm wrong but that started just around release of kilo anyways21:31
clarkbdhellmann: lifeless right we were testing this stuff until everyone revolted and said making the tests work was too hard21:31
jokke_Is there something fundamentally broken around that approach?21:31
*** baoli has joined #openstack-meeting21:32
*** baoli has quit IRC21:32
*** gampel has joined #openstack-meeting21:32
annegentlejokke_: I'm sorry, I didn't see the email re: service catalog and multi-tasking meetings today21:32
*** baoli has joined #openstack-meeting21:32
*** iben has quit IRC21:32
lifelessclarkb: It was my understanding we kept having gates break because we had cross-version asymmetry in play21:32
jrollclarkb: yeah, it seems like this spec sets out to fix the 'too hard' part of this, it mostly deals with how to test things and handle dependencies21:32
*** harshs has quit IRC21:32
jroll(imho)21:32
*** mudassirlatif has joined #openstack-meeting21:33
clarkbjroll: lifeless I fully expect that the first time kilo fails a change to novaclient that is required to make M do something there will be another revolt21:33
jrollheh21:33
fungia huge trigger for the branch-everywhere change was as an upshot of pinning all requirements in stable branches21:33
*** sidk has joined #openstack-meeting21:33
clarkbthe underlying reason why things fail isn't important, devs generally don't care about the old version and get cranky21:33
dhellmannclarkb: it's even more likely to happen with an oslo library21:33
lifelessclarkb: so this can only apply from liberty up21:33
clarkblifeless: sure but you are ignoring the mindset at play here21:34
clarkblifeless: yes we ran into problems with deps21:34
dhellmannlifeless: that just punts the revolt down the calendar to mitaka21:34
clarkbBut any fails will have the same problems21:34
lifelessdhellmann: sure - but thats why this needs discussion21:34
lifelessI don't want it to be '5 folk agreed, lets do it'21:34
fungiif we _aren't_ pinning requirements any longer and can somehow keep the supported versions compatible between branches then we can potentially stop branching within those libraries21:34
lifelessI want -buy- in21:34
dhellmannlifeless: sure. I'm discussing why I think this is something we don't want to do. :-)21:34
jokke_this is actually quite relevant topic for us in Glance as we just had a huge "fight" around our glanceclient 1.0.0 release and if we should make the client mimic v1 API functionality on top of v2 API as much as we can21:34
*** adahms has joined #openstack-meeting21:34
bknudsonwe actually used to have tests in keystone that cloned old tags of keystoneclient and ran tests with it.21:34
lifelessbknudson: right, so this is a generalised form of that21:35
lifelessbknudson: did they add value ?21:35
bknudsonI will say the tests found problems.21:35
clarkbbknudson: keystoneclient also had tests that ran against the ld devstack clouds21:35
* edleafe has to run - catch up with the logs later21:35
morganlifeless: they did add some value, they caused a lot of issues21:35
dhellmannwhat's the impact for the test matrix on a project like oslo.config, which is used in so many places?21:35
clarkbIIRC jogo added those in around icehouse?21:35
*** neelashah has quit IRC21:35
ttxThere was also a *lot* of pressure to get security fixes backports from distros, so they liked having stable branches there21:35
morganlifeless: but it did help limit regressions in keystoneclient/server21:35
bknudsonthe git clone when doing tox caused issues.21:35
*** mudassirlatif has quit IRC21:35
lifelessbknudson: right, this wont' have that issue because its zuul-integrated21:36
*** gampel1 has joined #openstack-meeting21:36
fungithough in fairness to the distros' desires to add stable branches for libraries, that wasn't actually the main reason we ended up doing it. they'll just be disappointed if we take it back away from them21:36
*** thingee has joined #openstack-meeting21:36
bknudsonlifeless: I think this will be useful then and will likely find issues where we're not backwards compatible.21:36
lifelessdhellmann: 'Changes to clients/libraries should run:' in the spec: - we'd run changes to oslo.config against each server branch21:36
ttxfungi: right, that was my point in the review21:36
dhellmannlifeless: right, how many  new jobs is that?21:36
ttxfungi: I'm fine screwing the distros up, but it needs to be spelled out as a consequence of the change21:37
*** skylerberg has joined #openstack-meeting21:37
jokke_dhellmann, lifeless: and od we have resources to run those jobs?21:37
ttxthey should see it coming so that we can properly assess the cost/benefit model of that spec21:37
*** gampel has quit IRC21:37
dhellmannjokke_: that's a good point, too21:37
lifelessdhellmann: we currently support 2 server branches; if the stable release team keep that constant - 2x the dvsm jobs of oslo.config + 2x again [if we do the *full* matrix]21:38
lifelessdhellmann: one 2x is the 'upper-constraints + modification'21:38
*** e0ne has quit IRC21:38
lifelessdhellmann: and one 2x is the 'upgrade only oslo.config' case21:38
lifelessdhellmann: the 2x is because master + -1 + -2 == 321:38
jokke_lifeless: so would oslo.config be the only special cupcake to get this?21:39
bknudsonthe keystone test would test with ksc 1.0 and ksc 1.x and ksc diable and latest, something like that. It was strange.21:39
bknudsondiablo21:39
dhellmannok, it looks like we might have more issues with libraries that run more gate jobs then, and oslo.config only runs one dsvm job today21:39
dhellmanntooz and oslo.messaging are probably better examples of where we would add lots of new test jobs21:39
clarkbdhellmann: one per branch is probably sufficient21:39
ttx(don't get me wrong, I think the single release channel is a lot saner for developers than the stable branch model, but I wonder about our users)21:39
clarkbsince using postgres or mysql isn;t going to make a difference for oslo.config21:39
clarkb(but oslo.db would want both)21:39
dhellmannclarkb: oslo.messaging runs 6 dsvm jobs now21:40
lifelessclarkb: two per branch - one for just-the-change and one for all-the-latest-including-the-change21:40
ttx(distros being a user)21:40
clarkblifeless: all the latest what?21:40
lifelessclarkb: though we can discuss whether both of those are truely needed or not21:40
lifelessclarkb: see lines 218 and 223 of the spec21:40
clarkbit would be jobs today + jobs today against liberty instead21:40
*** harlowja has quit IRC21:40
dhellmannI'll just state for the record that I'm opposed to this in principle, because I think it is going to make development of libraries even more difficult than it is now, and discourage contributions in areas where we should be encouraging them.21:40
*** kebray has quit IRC21:40
*** harlowja has joined #openstack-meeting21:40
lifelessdhellmann: are you also opposed to backwards compatibility?21:41
jokke_ttx: I might be the exception to make the rule, but I was really happy to see the libs moving to stable branching as well ... yes it brings overhead, but it made the developer life so much easier with the hope that every changed thing would not break downstream21:41
dhellmannlifeless: I would not be opposed to individual projects deciding to take this on. I am opposed to making it a blanket thing.21:41
lifelessjokke_: how does it make developer life easier ? A break is a break, whether it happens on the next release or in 6 months...21:41
dhellmannlifeless: and I don't think backwards compatibility is as important for most of our libs -- clients may be the exception21:42
bknudsonthe problem distros have with picking up newer releases of the libs is when the dependencies change21:42
lifelessdhellmann: is oslo a single project or many, for this?21:42
*** kebray has joined #openstack-meeting21:42
bknudsonnow you have to upgrade a bunch of other packages along with keystoneclient (for example)21:42
dhellmannlifeless: I would look at it case by case21:42
lifelessdhellmann: so I drill down a bit into the problems - right now the distros can't take our releases incrementally21:42
dhellmannlib by lib21:42
lifelessdhellmann: at all21:42
*** salv-orl_ has joined #openstack-meeting21:43
lifelessdhellmann: the whole lot wedges into a big morass, and the disaggrating of servers won't be picked up in any meaningful way until we fix this21:43
jrollI think maybe we need to take this in baby steps - we don't even test client master vs stable servers, let alone every library in openstack21:43
dhellmannjroll: true21:43
lifelessbknudson: right - so the thrust of this proposal is to make that cascade safe (not to remove it)21:44
lifelessjroll: I'd like to do that but you have to start at the edge of the matrix21:44
lifelessjroll: our clients use libraries21:44
lifelessjroll: if those libraries are branched, then the clients are tied to those branches21:44
jrolllifeless: ignoring the all-in-one server thing that makes a mess of dependencies21:44
jokke_lifeless: I way rather see the backwards incompatible changes coming in future and have time to deal with them than being stuck with past bad decisions ... this is really more towards the libs than clients, but just more ... also no-one pays attention of the versioning and if it brings backwards incompatible changes or not as seen with glanceclient21:44
jrolllifeless: thinking of a user running the latest novaclient against nova juno, for instance21:44
bknudsonthis seems to also require upping the major release number when the deps change21:45
ttxFor the record, I'll starte that I'm not opposed to this in principle. I just think it's a major change that we need to analyze well before starting it, and look at all the hidden costs (upstream & downstream cost) before making a decision21:45
lifelessbknudson: I don't think so21:45
*** Sukhdev has quit IRC21:45
*** mudassirlatif has joined #openstack-meeting21:45
lifelessjroll: so yes, and python-novaclient depends on python-keystoneclient21:45
*** garthb has quit IRC21:45
lifelessjroll: and oslo.i18n, serualization, utils21:46
*** salv-orlando has quit IRC21:46
jokke_lifeless: and the branching makes possible to backport critical/security fixes way more flexible manner than just version locks does for our stable servers21:46
*** garthb has joined #openstack-meeting21:46
*** amotoki has quit IRC21:46
lifelessjroll: so for distros to consume a newer python-novaclient, they need to know that those dependency changes won't break servers that install the same packages21:46
jrolllifeless: that's not what I'm talking about at all21:46
lifelessjroll: ok21:46
lifelessjroll: help me understand ?21:46
jrolllifeless: I'm talking about taking a brand new machine, pip install novaclient, nova boot (against some older nova server)21:47
jrollwe don't even test that21:47
jrolllet alone the implications of doing this on a machine with all of openstack installed21:47
lifelessjroll: ok - so yes, and I mention that in the spec21:47
jokke_jroll: add to your earlier we do not even test lib masters agains our service master, that would be nice before we even talk about testing them against service stables21:47
ttxi.e. not serverside libs but clientside libs21:47
lifelessjroll: we would get that testing with this spec21:47
*** annegentle has quit IRC21:47
*** Sukhdev has joined #openstack-meeting21:47
ttxeven if we currently use python*client libs for both.21:47
*** annegentle has joined #openstack-meeting21:48
lifelessjroll: assuming there are such tests, but as jokke_ mentions, our client testing is actually very sparse right now21:48
lifelessjroll: most if it happens defacto via the servers using the libs to talk to each other21:48
jrolllifeless: ok, I need to read deeper. I just think that this is way down the road from where we are now, and we should go one step at a time21:48
fungiyeah, the limited amount of client testing we used to get with tempest backwards-compat jobs was nearly nonexistent (other than testing coinstallability). the hope was that as clients began adding their own functional test suites they could run them against varying devstack branches21:49
jokke_lifeless: with the clients, do you mean that our client needs to be backwards compatible with old servers or that our client api/cli needs to be backwards comaptible with previous versions or both?21:49
lifelessjroll: If we agree that its a place to head to, then I'm delighted and happy to work on making a first step thing21:49
jrollnod21:49
*** edtubill has quit IRC21:49
*** mudassirlatif has quit IRC21:49
lifelessjroll: I've not figured out anything sane so far21:49
jrolllifeless: I'm good with the general idea, with the caveat that it might take a year or two to get there, and there's lots more to think about :)21:49
lifelessjokke_: so on security backports - we need to backport things because distros can't consume newer releases.21:50
lifelessjokke_: its a self-created problem in a lot of ways21:50
* jroll realizes this is a super hard problem21:50
lifelessjokke_: (again, look at firefox and chromium - no stable branches, just roll forward)21:50
ttxlifeless: can't, or don't want to ?21:50
lifelessttx: today - can't21:51
lifelessttx: because we're not committed to backwards compat through the stack21:51
lifelessttx: upgrading python-novaclient to get a security fix means upgrading multiple oslo libraries21:52
lifelessttx: and keystoneclinet21:52
*** gampel1 has quit IRC21:52
*** devlaps has joined #openstack-meeting21:52
lifelessttx: and the oslo libraries may have backwards incompatible changes21:52
jokke_lifeless: but the problem starts with most of the 3rd party libs our libs and clients consume are not that either21:52
ttxlifeless: firefox is teh exception rather than the rule though, it had to apply for a SRU exception21:52
lifelessttx: which forces an upgrade of the servers21:52
*** geoffarnold has quit IRC21:52
jokke_and that has been breaking us all the time21:52
*** ijw has joined #openstack-meeting21:52
lifelessttx: so if Ubuntu *wanted* to take latest novaclient, it can't because the servers are a Big Deal to upgrade21:52
*** mudassirlatif has joined #openstack-meeting21:53
ttxI don't think if we had aweosme backward compatibility that they would roll forward using featureful SRUs21:53
lifelessjokke_: constraints has locked that down so we're not subject to those whims anymore21:53
ttxthose are quite a pain to test21:53
jokke_lifeless: ref firefox and chromium, which way we should be backwards compatible ... towards the consumer or towards our services?21:53
lifelessttx: it would be 'won't' rather than 'can't' at that point21:53
jrollimho, if we can actually do this, it's a huge win in the end, for both devs and deployers. it's just a super-not-fun path to get there, and we need to think about what that path is.21:53
lifelessttx: right now its can't :)21:53
ttxlifeless: right21:53
jokke_because I see firefox for example changing the user interface all the time and that's deifnitely not backwards comaptible21:54
*** kebray has quit IRC21:54
lifelessttx: and there's no point trying to have a dialogue with  any distro about doing it while we haven't enabled it21:54
lifelessjroll: what things are in your mind when you say super not fun ?21:54
ttxjokke_: in the forefox ccase they accept to break their user expectations of painless upgrades against making their lives a lot easier21:54
PietAre we planning to have open discussion?21:55
jokke_ok, lets continue this topic on the spec nad leave the last minutes for open discussion21:55
*** geoffarnold has joined #openstack-meeting21:55
ttxjokke_: it's just so much work (and risk) to backport security fixes in Firefox that they said "let's stop doing that and risk breaking users with featureful upgrades instead"21:55
jrolllifeless: lots of dependency hell, gate breakage, etc. for someone like me that isn't as informed as you on those things, it's hard to wrap my head around :)21:55
jokke_#topic Open discussion21:56
*** openstack changes topic to "Open discussion (Meeting topic: crossproject)"21:56
jrolllifeless: I may be completely wrong, it might be easy21:56
*** hemna has quit IRC21:56
PietOK - a couple of things21:56
PietFirst, we are running a persona working session next weak in Austin.  We already have a group of tentative roles, but want to flesh-out a handful into actual personas.21:56
ttxjokke_: if Firefox continued to provide them with stable branches they would happily continue to use them.21:56
lifelessjroll: so I think no gate breaking21:56
lifelessjroll: it might be hard to get some patches in21:56
*** otter768 has joined #openstack-meeting21:56
lifelessjroll: but the point of this is to be protective of compat and the various systems21:56
*** Sisir has quit IRC21:56
jokke_ttx: somewhat makes sense, but indeed sounds like really special case21:56
*** Sisir has joined #openstack-meeting21:57
*** ijw has quit IRC21:57
*** ccavanna has joined #openstack-meeting21:57
jrolllifeless: yeah, I suspect if we spent an hour over beers this would be much more clear to me :)21:57
jokke_Piet: mind to open "Persona" up a bit in the context21:57
*** ijw has joined #openstack-meeting21:57
ttxjokke_: basically I'm not sure that distros would roll forward if we did that perfect backward compatibility. They would likely curse us and do their own stable branches instead.21:57
lifelessI've put a slot for this up for the cross-project track in mitaka21:58
jokke_ttx: yes, I agree21:58
PietSure, the product working group needs a set of personas to help them focus their stories a bit21:58
PietArchitects, operators, developers, etc21:58
ttxjokke_: so in the end I'm not convinced of the value of the change for the user/distro21:58
lifelessttx: and you know, that would be ok. Because all the folk doing CD - every devstack user for instance - would be that much happier21:59
lifelessanyone installing from pip21:59
*** JRobinson__ has joined #openstack-meeting21:59
*** gyee has joined #openstack-meeting21:59
ttxlifeless: yeah, at least we would allow them to make the smart choice. They would likely not make it, but meh21:59
jokke_last minute!21:59
jokke_Piet: was that just announcement or did you actually seek some feedback from this group21:59
jokke_?22:00
PietWe're looking for feedback from the PTLs on which roles should be the focus of the working session. I have a quick two minute survey for the PTLs to vote on which roles are important to their projects.22:00
*** hrou has quit IRC22:00
PietNeed to understand which roles the PTLs actualy care about22:00
Piethttps://www.surveymonkey.com/r/H6WS2HS22:00
*** gampel has joined #openstack-meeting22:00
jokke_Piet: ok, thanks ... mind to send e-mail to the dev mailing list with [ptl] in the topic22:00
PietWill take you less than two minutes and add a ton of value22:00
jokke_as we're out of time22:00
*** asettle has joined #openstack-meeting22:00
Pietsure22:00
jokke_#link https://www.surveymonkey.com/r/H6WS2HS22:00
jokke_#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
openstackMeeting ended Tue Sep 29 22:01:04 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-09-29-21.01.html22:01
ttxjokke_: thx for chairing!22:01
jokke_Thanks everyone!22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-09-29-21.01.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-09-29-21.01.log.html22:01
jrollthanks for running, jokke_ !22:01
*** gordc has left #openstack-meeting22:01
*** skraynev_ has quit IRC22:01
*** otter768 has quit IRC22:01
*** Sisir has quit IRC22:01
*** bobh has quit IRC22:01
*** hemna has joined #openstack-meeting22:01
elmikothanks jokke_22:02
*** Piet has quit IRC22:02
*** iben has joined #openstack-meeting22:03
*** hemna has quit IRC22:04
*** hemnafk is now known as hemna22:04
*** weshay has quit IRC22:06
*** trozet has quit IRC22:06
*** ociuhandu has quit IRC22:06
*** gampel has quit IRC22:07
*** annegentle has quit IRC22:08
*** jungleboyj has quit IRC22:08
*** ddeva has quit IRC22:08
*** xarses has left #openstack-meeting22:08
*** matrohon has quit IRC22:11
*** boris-42 has joined #openstack-meeting22:12
*** ddeva has joined #openstack-meeting22:12
*** baoli has quit IRC22:12
*** baoli has joined #openstack-meeting22:13
*** zhhuabj has quit IRC22:13
*** marcusvrn_ has quit IRC22:15
*** gampel has joined #openstack-meeting22:15
*** wbhuber has quit IRC22:17
*** sigmavirus24 is now known as sigmavirus24_awa22:19
*** angdraug has left #openstack-meeting22:20
*** mwagner_ has quit IRC22:20
*** kencjohnston has quit IRC22:23
*** yamahata has quit IRC22:24
*** pradk has quit IRC22:24
*** yamahata has joined #openstack-meeting22:24
*** aranjan has joined #openstack-meeting22:24
*** AlanClark has quit IRC22:24
*** zhhuabj has joined #openstack-meeting22:25
*** rfolco has quit IRC22:26
*** harshs has joined #openstack-meeting22:26
*** skylerberg has quit IRC22:27
*** VW has quit IRC22:28
*** VW has joined #openstack-meeting22:28
*** VW has quit IRC22:28
*** VW has joined #openstack-meeting22:29
*** VW has quit IRC22:29
*** rfolco has joined #openstack-meeting22:29
*** VW has joined #openstack-meeting22:29
*** ddieterly has quit IRC22:30
*** vgridnev has quit IRC22:30
*** epcim has quit IRC22:31
*** gampel has quit IRC22:31
*** edtubill has joined #openstack-meeting22:32
*** gampel has joined #openstack-meeting22:33
*** ddeva has quit IRC22:34
*** dneary has quit IRC22:35
*** dane_leblanc_ has joined #openstack-meeting22:36
*** banix has quit IRC22:37
*** Rockyg has quit IRC22:37
*** gampel has quit IRC22:38
*** stevemar has quit IRC22:38
*** dane_leblanc has quit IRC22:40
*** jungleboyj has joined #openstack-meeting22:41
*** dane_leblanc_ has quit IRC22:42
*** rfolco has quit IRC22:42
*** baoli has quit IRC22:44
*** baoli has joined #openstack-meeting22:44
*** gampel has joined #openstack-meeting22:46
*** Sukhdev has quit IRC22:46
*** amotoki has joined #openstack-meeting22:46
*** mudassirlatif has quit IRC22:47
*** xingchao has joined #openstack-meeting22:47
*** ayoung has joined #openstack-meeting22:49
*** rfolco has joined #openstack-meeting22:49
*** emagana has joined #openstack-meeting22:51
*** amotoki has quit IRC22:51
*** lukebrooker has joined #openstack-meeting22:52
*** gampel has quit IRC22:55
*** gampel has joined #openstack-meeting22:55
*** gampel has quit IRC22:56
*** spotz is now known as spotz_zzz22:56
*** sridhar_ram has quit IRC22:56
*** mwagner_ has joined #openstack-meeting22:57
*** su_zhang has quit IRC22:58
*** aranjan has quit IRC22:58
*** pballand has quit IRC22:58
*** pballand has joined #openstack-meeting22:59
*** mudassirlatif has joined #openstack-meeting22:59
*** vijendar has quit IRC22:59
*** geoffarnold is now known as geoffarnoldX23:00
*** jhesketh has quit IRC23:01
*** jhesketh has joined #openstack-meeting23:02
*** iben has quit IRC23:02
*** gampel has joined #openstack-meeting23:03
*** sidk has quit IRC23:04
*** Sukhdev has joined #openstack-meeting23:04
*** sidk has joined #openstack-meeting23:05
*** su_zhang has joined #openstack-meeting23:06
*** geoffarnoldX is now known as geoffarnold23:06
*** gampel has quit IRC23:07
*** Piet has joined #openstack-meeting23:07
*** harshs has quit IRC23:12
*** ddeva has joined #openstack-meeting23:12
*** rfolco has quit IRC23:12
*** xingchao has quit IRC23:14
*** yamahata has quit IRC23:15
*** cdelatte has joined #openstack-meeting23:15
*** elo1 has quit IRC23:15
*** gampel has joined #openstack-meeting23:15
*** elo1 has joined #openstack-meeting23:16
*** baoli has quit IRC23:16
*** rfolco has joined #openstack-meeting23:17
*** ijw has quit IRC23:18
*** elo1 has quit IRC23:18
*** salv-orl_ has quit IRC23:19
*** yamamoto has joined #openstack-meeting23:19
*** xyang1 has quit IRC23:19
*** elo1 has joined #openstack-meeting23:19
*** dims_ has joined #openstack-meeting23:19
*** xingchao has joined #openstack-meeting23:20
*** ddeva has quit IRC23:21
*** Sukhdev has quit IRC23:21
*** mudassirlatif has quit IRC23:21
*** dims has quit IRC23:22
*** eharney has quit IRC23:23
*** julim has quit IRC23:23
*** mudassirlatif has joined #openstack-meeting23:23
*** su_zhang has quit IRC23:24
*** xingchao has quit IRC23:24
*** aloga has quit IRC23:24
*** su_zhang has joined #openstack-meeting23:24
*** elo1 has quit IRC23:24
*** vmbrasseur is now known as vmb_out23:25
*** aloga has joined #openstack-meeting23:25
*** bvandenh has quit IRC23:25
*** xingchao has joined #openstack-meeting23:25
*** skylerberg has joined #openstack-meeting23:25
*** markmcclain has quit IRC23:25
*** banix has joined #openstack-meeting23:26
*** apoorvad has quit IRC23:26
*** geoffarnold has quit IRC23:26
*** gampel1 has joined #openstack-meeting23:27
*** ccavanna_ has joined #openstack-meeting23:27
*** elo1 has joined #openstack-meeting23:27
*** geoffarnold has joined #openstack-meeting23:27
*** carl_baldwin has quit IRC23:28
*** Qiming_ has joined #openstack-meeting23:28
*** gampel has quit IRC23:29
*** hrou has joined #openstack-meeting23:29
*** Apoorva has joined #openstack-meeting23:30
*** sdake_ has quit IRC23:30
*** ccavanna has quit IRC23:30
*** sdake has joined #openstack-meeting23:30
*** irenab_ has joined #openstack-meeting23:30
*** markmcclain has joined #openstack-meeting23:31
*** ganeshna has joined #openstack-meeting23:31
*** mdbooth_ has joined #openstack-meeting23:31
*** dims_ has quit IRC23:31
*** xingchao has quit IRC23:31
*** ttrifonow has joined #openstack-meeting23:31
*** bauzas_ has joined #openstack-meeting23:32
*** dims_ has joined #openstack-meeting23:32
*** leeantho_ has joined #openstack-meeting23:32
*** mdbooth has quit IRC23:32
*** zz_ttrifonov has quit IRC23:32
*** flaper87 has quit IRC23:32
*** dmellado has quit IRC23:32
*** Guest80969 has quit IRC23:32
*** bauzas has quit IRC23:32
*** epheo has quit IRC23:32
*** rfolco has quit IRC23:32
*** amandap has quit IRC23:32
*** htruta has quit IRC23:32
*** tjcocozz has quit IRC23:32
*** johnthetubaguy has quit IRC23:32
*** tristanC has quit IRC23:32
*** bswartz has joined #openstack-meeting23:32
*** mdbooth_ is now known as mdbooth23:32
*** bauzas_ is now known as bauzas23:32
*** htruta` has joined #openstack-meeting23:32
*** flaper87 has joined #openstack-meeting23:32
*** tristanC has joined #openstack-meeting23:33
*** leeantho has quit IRC23:33
*** irenab has quit IRC23:33
*** marekd has quit IRC23:33
*** albertom has quit IRC23:33
*** timrc has quit IRC23:33
*** pcarver has quit IRC23:33
*** rfolco has joined #openstack-meeting23:33
*** irenab_ is now known as irenab23:33
*** Apoorva is now known as apoorvad23:33
*** pcarver_ has joined #openstack-meeting23:33
*** aloga has quit IRC23:33
*** jungleboyj has quit IRC23:33
*** loquacities has quit IRC23:33
*** marekd has joined #openstack-meeting23:33
*** aloga has joined #openstack-meeting23:33
*** grumpycat has joined #openstack-meeting23:33
*** tjcocozz has joined #openstack-meeting23:33
*** jungleboyj has joined #openstack-meeting23:33
*** loquacities has joined #openstack-meeting23:33
*** harshs has joined #openstack-meeting23:33
*** albertom has joined #openstack-meeting23:34
*** grumpycat is now known as Guest6055123:34
*** johnthetubaguy has joined #openstack-meeting23:34
*** timrc has joined #openstack-meeting23:34
*** amandap has joined #openstack-meeting23:35
*** dmellado has joined #openstack-meeting23:35
*** epheo has joined #openstack-meeting23:36
*** yamamoto has quit IRC23:37
*** asettle has quit IRC23:37
*** rfolco has quit IRC23:40
*** alop has quit IRC23:41
*** xingchao has joined #openstack-meeting23:41
*** bobh has joined #openstack-meeting23:41
*** julim has joined #openstack-meeting23:42
*** mudassirlatif has quit IRC23:43
*** hemna is now known as hemnafk23:43
*** gampel1 has quit IRC23:43
*** garthb has quit IRC23:44
*** rfolco has joined #openstack-meeting23:44
*** sdake has quit IRC23:44
*** sdake_ has joined #openstack-meeting23:44
*** achanda_ has joined #openstack-meeting23:44
*** achanda_ has quit IRC23:45
*** sdake_ is now known as sdake23:45
*** gampel has joined #openstack-meeting23:45
*** barrett1 has left #openstack-meeting23:45
*** pm90_ has quit IRC23:46
*** julim has quit IRC23:47
*** shashank_hegde has quit IRC23:47
*** julim has joined #openstack-meeting23:48
*** xingchao has quit IRC23:48
*** ccarrara_ has quit IRC23:48
*** achanda has quit IRC23:48
*** emagana has quit IRC23:48
*** rossella_s has quit IRC23:49
*** elo1 has quit IRC23:49
*** shashank_hegde has joined #openstack-meeting23:50
*** ganeshna_ has joined #openstack-meeting23:51
*** ganeshna has quit IRC23:51
*** mudassirlatif has joined #openstack-meeting23:51
*** julim has quit IRC23:52
*** Sukhdev has joined #openstack-meeting23:54
*** aranjan has joined #openstack-meeting23:55
*** otter768 has joined #openstack-meeting23:57
*** Piet has quit IRC23:57
*** Piet has joined #openstack-meeting23:58
*** lukebroo_ has joined #openstack-meeting23:59

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