Tuesday, 2015-10-06

*** geoffarnold has quit IRC00:00
*** galstrom is now known as galstrom_zzz00:01
*** yamamoto has joined #openstack-meeting00:01
*** okrieg has quit IRC00:03
*** garthb has quit IRC00:04
*** ddieterl_ has quit IRC00:05
*** okrieg has joined #openstack-meeting00:06
*** MaxPC has quit IRC00:11
*** ajmiller has quit IRC00:12
*** otter768 has quit IRC00:13
*** MaxPC has joined #openstack-meeting00:14
*** otter768 has joined #openstack-meeting00:14
*** okrieg has quit IRC00:15
*** tsekiyama has quit IRC00:17
*** okrieg has joined #openstack-meeting00:17
*** weshay has joined #openstack-meeting00:18
*** tsekiyama has joined #openstack-meeting00:18
*** geoffarn_ has quit IRC00:20
*** geoffarnold has joined #openstack-meeting00:21
*** achanda has joined #openstack-meeting00:21
*** roxanagh_ has quit IRC00:23
*** penick has quit IRC00:23
*** pvaneck has quit IRC00:28
*** mtanino has quit IRC00:29
*** julim has joined #openstack-meeting00:30
*** kebray has quit IRC00:32
*** glauco has joined #openstack-meeting00:32
*** penick has joined #openstack-meeting00:32
*** dane_leblanc has joined #openstack-meeting00:34
*** okrieg has quit IRC00:36
*** vmbrasseur is now known as vmb_out00:36
*** tsekiyama has quit IRC00:36
*** galstrom_zzz is now known as galstrom00:37
*** glauco has quit IRC00:37
*** ayoung has quit IRC00:37
*** _hrou_ has joined #openstack-meeting00:38
*** okrieg has joined #openstack-meeting00:40
*** julim has quit IRC00:41
*** okrieg has quit IRC00:41
*** hrou has quit IRC00:41
*** geoffarn_ has joined #openstack-meeting00:42
*** carl_baldwin has quit IRC00:44
*** ganeshna has joined #openstack-meeting00:45
*** geoffarnold has quit IRC00:46
*** Sukhdev has quit IRC00:47
*** glauco_ has joined #openstack-meeting00:49
*** sridhar_ram has joined #openstack-meeting00:49
*** dims_ has joined #openstack-meeting00:50
*** ganeshna has quit IRC00:51
*** leeantho has quit IRC00:51
*** ganeshna has joined #openstack-meeting00:51
*** sridhar_ram has quit IRC00:54
*** sridhar_ram has joined #openstack-meeting00:54
*** dims_ has quit IRC00:55
*** gyee has quit IRC00:57
*** ganeshna has quit IRC00:57
*** bobh has joined #openstack-meeting00:57
*** dims_ has joined #openstack-meeting00:58
*** bobh has quit IRC00:59
*** su_zhang_ has quit IRC00:59
*** hoangcx has joined #openstack-meeting01:00
*** agireud has quit IRC01:01
*** topol has joined #openstack-meeting01:02
*** geoffarn_ has quit IRC01:03
*** geoffarnold has joined #openstack-meeting01:03
*** ayoung has joined #openstack-meeting01:05
*** baoli has joined #openstack-meeting01:06
*** topol has quit IRC01:07
*** alexsyip has quit IRC01:08
*** yamamoto has quit IRC01:08
*** Swami has joined #openstack-meeting01:10
*** apoorvad_ has joined #openstack-meeting01:11
*** aranjan has quit IRC01:12
*** penick has quit IRC01:12
*** JRobinson__ has quit IRC01:12
*** apoorvad has quit IRC01:14
*** JRobinson__ has joined #openstack-meeting01:15
*** apoorvad_ has quit IRC01:15
*** ivar-lazzaro has quit IRC01:15
*** okrieg has joined #openstack-meeting01:16
*** ivar-lazzaro has joined #openstack-meeting01:16
*** vivek-ebay has quit IRC01:18
*** vivek-ebay has joined #openstack-meeting01:18
*** jckasper has quit IRC01:19
*** baoli has quit IRC01:19
*** baoli has joined #openstack-meeting01:20
*** emagana has quit IRC01:21
*** JRobinson__ has quit IRC01:22
*** ganeshna has joined #openstack-meeting01:22
*** pm90_ has quit IRC01:22
*** geoffarnold has quit IRC01:24
*** geoffarnold has joined #openstack-meeting01:24
*** JRobinson__ has joined #openstack-meeting01:27
*** asselin_ has joined #openstack-meeting01:27
*** okrieg has joined #openstack-meeting01:27
*** markvoelker has quit IRC01:28
*** Swami has quit IRC01:28
*** okrieg has quit IRC01:29
*** dims_ has quit IRC01:30
*** ganeshna has quit IRC01:31
*** novas0x2a|laptop has quit IRC01:31
*** asselin_ has quit IRC01:31
*** jckasper has joined #openstack-meeting01:32
*** jjmb1 has joined #openstack-meeting01:32
*** Daisy has joined #openstack-meeting01:33
*** baoli has quit IRC01:34
*** jjmb has quit IRC01:35
*** s3wong has quit IRC01:35
*** tsekiyama has joined #openstack-meeting01:37
*** baoli has joined #openstack-meeting01:37
*** sridhar_ram1 has joined #openstack-meeting01:38
*** Daisy has quit IRC01:38
*** Daisy has joined #openstack-meeting01:39
*** sridhar_ram1 has quit IRC01:39
*** sridhar_ram has quit IRC01:41
*** tsekiyama has quit IRC01:42
*** Daisy has quit IRC01:42
*** Daisy has joined #openstack-meeting01:42
*** glauco_ has quit IRC01:43
*** glauco has joined #openstack-meeting01:45
*** geoffarn_ has joined #openstack-meeting01:46
*** geoffarnold has quit IRC01:46
*** pm90_ has joined #openstack-meeting01:48
*** baoli has quit IRC01:48
*** baoli has joined #openstack-meeting01:48
*** ricolin has joined #openstack-meeting01:53
*** adahms has quit IRC01:55
*** wbhuber has joined #openstack-meeting01:59
*** stevemar_ has quit IRC01:59
*** ddieterly has joined #openstack-meeting02:00
*** stevemar_ has joined #openstack-meeting02:00
*** alop has quit IRC02:01
*** galstrom is now known as galstrom_zzz02:01
*** adahms has joined #openstack-meeting02:02
*** rfolco has joined #openstack-meeting02:02
*** MaxPC has quit IRC02:05
*** pm90_ has quit IRC02:05
*** sankarshan_away is now known as sankarshan02:05
*** neelashah has joined #openstack-meeting02:06
*** geoffarn_ has quit IRC02:07
*** geoffarnold has joined #openstack-meeting02:07
*** baoli has quit IRC02:08
*** vilobhmm11 has quit IRC02:09
*** yamamoto has joined #openstack-meeting02:09
*** amrith is now known as _amrith_02:10
*** yamamoto has quit IRC02:13
*** stanchan has joined #openstack-meeting02:13
*** rfolco has quit IRC02:14
*** yamahata has quit IRC02:15
*** unicell has quit IRC02:18
*** kebray has joined #openstack-meeting02:18
*** MaxPC has joined #openstack-meeting02:18
*** MaxPC has quit IRC02:18
*** dmacpher has joined #openstack-meeting02:20
*** tfukushima has joined #openstack-meeting02:24
*** weshay has quit IRC02:25
*** geoffarnold has quit IRC02:26
*** ivar-lazzaro has quit IRC02:26
*** Daisy has quit IRC02:28
*** geoffarnold has joined #openstack-meeting02:28
*** tochi has joined #openstack-meeting02:29
*** sridhar_ram has joined #openstack-meeting02:31
*** emagana has joined #openstack-meeting02:32
*** jckasper has quit IRC02:33
*** topol has joined #openstack-meeting02:35
*** emagana has quit IRC02:37
*** sbalukoff has quit IRC02:40
*** stevemar_ has quit IRC02:41
*** stevemar_ has joined #openstack-meeting02:42
*** stevemar_ has quit IRC02:43
*** stevemar_ has joined #openstack-meeting02:43
*** glauco has quit IRC02:45
*** glauco_ has joined #openstack-meeting02:45
*** jckasper has joined #openstack-meeting02:46
*** sdake has joined #openstack-meeting02:49
*** achanda has quit IRC02:50
*** bobh has joined #openstack-meeting02:51
*** sridhar_ram has quit IRC02:54
*** jckasper has quit IRC02:55
*** agireud has joined #openstack-meeting02:57
*** ayoung has quit IRC02:58
*** topol has quit IRC02:58
*** bobh has quit IRC02:59
*** kebray has quit IRC03:02
*** spzala has quit IRC03:04
*** markvoelker_ has joined #openstack-meeting03:05
*** jckasper has joined #openstack-meeting03:07
*** vilobhmm11 has joined #openstack-meeting03:08
*** sdake has quit IRC03:09
*** sdake has joined #openstack-meeting03:10
*** vilobhmm111 has joined #openstack-meeting03:11
*** vivek-ebay has quit IRC03:11
*** geoffarn_ has joined #openstack-meeting03:11
*** geoffarnold has quit IRC03:12
*** vilobhmm11 has quit IRC03:12
*** sdake has quit IRC03:13
*** lazy_prince has joined #openstack-meeting03:15
*** vilobhmm111 has quit IRC03:15
*** haomaiwang has joined #openstack-meeting03:16
*** yamamoto has joined #openstack-meeting03:17
*** kebray has joined #openstack-meeting03:18
*** kebray has quit IRC03:18
*** kebray has joined #openstack-meeting03:18
*** deepthi has joined #openstack-meeting03:20
*** jjmb has joined #openstack-meeting03:21
*** stevemar_ has quit IRC03:21
*** markvoelker has joined #openstack-meeting03:22
*** stevemar_ has joined #openstack-meeting03:22
*** roxanagh_ has joined #openstack-meeting03:22
*** jjmb1 has quit IRC03:22
*** vilobhmm11 has joined #openstack-meeting03:25
*** markvoelker_ has quit IRC03:25
*** markvoelker_ has joined #openstack-meeting03:26
*** su_zhang_ has joined #openstack-meeting03:27
*** markvoelker has quit IRC03:28
*** killer_prince has joined #openstack-meeting03:28
*** su_zhang_ has joined #openstack-meeting03:28
*** tochi has quit IRC03:29
*** neelashah has quit IRC03:29
*** roxanagh_ has quit IRC03:29
*** lazy_prince has quit IRC03:31
*** sdake has joined #openstack-meeting03:33
*** aranjan has joined #openstack-meeting03:34
*** haomaiwang has quit IRC03:34
*** vilobhmm11 has quit IRC03:35
*** wbhuber has quit IRC03:37
*** annp has joined #openstack-meeting03:38
*** ijw has quit IRC03:39
*** hoangcx has quit IRC03:39
*** annp has quit IRC03:42
*** ddieterly has quit IRC03:42
*** haomaiwang has joined #openstack-meeting03:42
*** aranjan has quit IRC03:45
*** DericHorn-HP has joined #openstack-meeting03:47
*** lukebrooker has joined #openstack-meeting03:49
*** DericHorn-HP has quit IRC03:51
*** topol has joined #openstack-meeting03:51
*** JRobinson__ is now known as JRobinson__afk03:51
*** sbalukoff has joined #openstack-meeting03:52
*** geoffarn_ has quit IRC03:53
*** geoffarnold has joined #openstack-meeting03:53
*** pradipta has joined #openstack-meeting03:56
*** DericHorn-HP has joined #openstack-meeting03:57
*** galstrom_zzz is now known as galstrom03:57
*** glauco_ has quit IRC04:00
*** haomaiwang has quit IRC04:01
*** okrieg has joined #openstack-meeting04:01
*** haomaiwang has joined #openstack-meeting04:01
*** shashank_hegde has quit IRC04:03
*** lazy_prince has joined #openstack-meeting04:04
*** topol has quit IRC04:05
*** topol has joined #openstack-meeting04:06
*** puranamr has joined #openstack-meeting04:07
*** killer_prince has quit IRC04:08
*** pballand_ has joined #openstack-meeting04:08
*** okrieg has quit IRC04:09
*** tochi has joined #openstack-meeting04:09
*** pballand has quit IRC04:10
*** pballand_ is now known as pballand04:10
*** vivek-ebay has joined #openstack-meeting04:11
*** puranamr has quit IRC04:12
*** geoffarnold has quit IRC04:14
*** geoffarnold has joined #openstack-meeting04:15
*** dwalleck has joined #openstack-meeting04:15
*** jckasper has quit IRC04:16
*** lukebrooker has quit IRC04:17
*** Daisy has joined #openstack-meeting04:17
*** jhenner has quit IRC04:18
*** lukebrooker has joined #openstack-meeting04:19
*** JRobinson__afk is now known as JRobinson__04:19
*** gongysh_ has joined #openstack-meeting04:20
*** Sukhdev has joined #openstack-meeting04:23
*** gongysh has quit IRC04:24
*** Daisy has quit IRC04:28
*** Daisy has joined #openstack-meeting04:29
*** galstrom is now known as galstrom_zzz04:29
*** jckasper has joined #openstack-meeting04:30
*** electrocucaracha has joined #openstack-meeting04:31
*** banix has quit IRC04:31
*** Daisy has quit IRC04:33
*** electrocucaracha has quit IRC04:33
*** neeti has joined #openstack-meeting04:34
*** _hrou_ has quit IRC04:35
*** geoffarn_ has joined #openstack-meeting04:36
*** amotoki has joined #openstack-meeting04:38
*** su_zhang_ has quit IRC04:40
*** geoffarnold has quit IRC04:40
*** tfukushima has quit IRC04:41
*** achanda has joined #openstack-meeting04:42
*** unicell has joined #openstack-meeting04:42
*** ddieterly has joined #openstack-meeting04:43
*** dims_ has joined #openstack-meeting04:46
*** ddieterly has quit IRC04:47
*** nijaba has quit IRC04:51
*** skylerberg has quit IRC04:52
*** DericHorn-HP has quit IRC04:54
*** dane_leblanc has quit IRC04:55
*** DericHorn-HP has joined #openstack-meeting04:56
*** geoffarn_ has quit IRC04:57
*** geoffarnold has joined #openstack-meeting04:57
*** haomaiwang has quit IRC04:58
*** nijaba has joined #openstack-meeting05:01
*** nijaba has quit IRC05:01
*** nijaba has joined #openstack-meeting05:01
*** haomaiwang has joined #openstack-meeting05:01
*** asettle has quit IRC05:01
*** asettle has joined #openstack-meeting05:01
*** _fortis has quit IRC05:02
*** cbader_ has joined #openstack-meeting05:02
*** MIDENN_ has joined #openstack-meeting05:02
*** morgan has quit IRC05:02
*** jesusaurus has quit IRC05:02
*** cebruns has quit IRC05:03
*** redrobot has quit IRC05:03
*** atiwari1 has joined #openstack-meeting05:03
*** gongysh_ has quit IRC05:03
*** dmacpher has quit IRC05:03
*** adahms has quit IRC05:03
*** mdenny has quit IRC05:03
*** gothicmindfood has quit IRC05:03
*** lsp42 has quit IRC05:03
*** coreycb has quit IRC05:03
*** jaredrohe has quit IRC05:03
*** atiwari has quit IRC05:03
*** cbader has quit IRC05:03
*** devananda has quit IRC05:03
*** mfisch has quit IRC05:03
*** sdague has quit IRC05:03
*** amakarov_away has quit IRC05:03
*** trozet has quit IRC05:04
*** cebruns has joined #openstack-meeting05:04
*** tristanC has quit IRC05:04
*** gothicmindfood has joined #openstack-meeting05:05
*** lsp42 has joined #openstack-meeting05:05
*** tristanC has joined #openstack-meeting05:05
*** mfisch has joined #openstack-meeting05:06
*** mfisch is now known as Guest8345405:06
*** vivek-ebay has quit IRC05:06
*** morgan has joined #openstack-meeting05:06
*** asettle has quit IRC05:06
*** _fortis has joined #openstack-meeting05:06
*** asettle has joined #openstack-meeting05:07
*** coreycb has joined #openstack-meeting05:07
*** dmacpher has joined #openstack-meeting05:08
*** sdague has joined #openstack-meeting05:08
*** trozet has joined #openstack-meeting05:08
*** gongysh_ has joined #openstack-meeting05:08
*** redrobot has joined #openstack-meeting05:08
*** redrobot is now known as Guest2867805:09
*** jaredrohe has joined #openstack-meeting05:09
*** amakarov_away has joined #openstack-meeting05:09
*** sdake_ has joined #openstack-meeting05:09
*** devananda has joined #openstack-meeting05:10
*** geoffarnold has quit IRC05:11
*** jesusaurus has joined #openstack-meeting05:11
*** okrieg has joined #openstack-meeting05:12
*** sdake has quit IRC05:13
*** vilobhmm11 has joined #openstack-meeting05:15
*** moha_hunt has quit IRC05:15
*** armax has quit IRC05:16
*** mrmartin has joined #openstack-meeting05:17
*** topol has quit IRC05:19
*** geoffarnold has joined #openstack-meeting05:19
*** BharatK has joined #openstack-meeting05:21
*** sudipto has joined #openstack-meeting05:22
*** jckasper has quit IRC05:26
*** yamahata has joined #openstack-meeting05:27
*** sankarshan is now known as sankarshan_away05:28
*** sudipto has quit IRC05:31
*** pradipta has quit IRC05:31
*** asettle has quit IRC05:32
*** asettle has joined #openstack-meeting05:32
*** ganeshna has joined #openstack-meeting05:35
*** sdake_ has quit IRC05:38
*** jckasper has joined #openstack-meeting05:40
*** neeti has quit IRC05:41
*** tfukushima has joined #openstack-meeting05:41
*** tfukushima has quit IRC05:43
*** tfukushima has joined #openstack-meeting05:43
*** ddieterly has joined #openstack-meeting05:44
*** sudipto has joined #openstack-meeting05:45
*** DericHorn-HP has quit IRC05:47
*** vjay12 has joined #openstack-meeting05:48
*** ddieterly has quit IRC05:48
*** nmagnezi has joined #openstack-meeting05:49
*** sudipto has quit IRC05:50
*** edtubill has joined #openstack-meeting05:51
*** aswadr has joined #openstack-meeting05:52
*** lpeer has joined #openstack-meeting05:52
*** unicell has quit IRC05:52
*** unicell has joined #openstack-meeting05:53
*** evgenyf has joined #openstack-meeting05:56
*** lpeer has quit IRC05:56
*** lpeer has joined #openstack-meeting05:57
*** neeti has joined #openstack-meeting05:59
*** unicell1 has joined #openstack-meeting05:59
*** unicell has quit IRC06:00
*** ildikov has quit IRC06:00
*** geoffarnold has quit IRC06:00
*** ildikov has joined #openstack-meeting06:00
*** haomaiwang has quit IRC06:01
*** haomaiwang has joined #openstack-meeting06:01
*** geoffarnold has joined #openstack-meeting06:01
*** jckasper has quit IRC06:01
*** doron_afk has joined #openstack-meeting06:03
*** lukebrooker has quit IRC06:03
*** MarkAtwood has joined #openstack-meeting06:06
*** JRobinson__ has quit IRC06:07
*** vjay12 has quit IRC06:07
*** cloudtrainme has joined #openstack-meeting06:08
*** zz_ttrifonov is now known as ttrifonov06:09
*** asettle has quit IRC06:11
*** scheuran has joined #openstack-meeting06:12
*** hichihara has quit IRC06:15
*** topol has joined #openstack-meeting06:15
*** jckasper has joined #openstack-meeting06:16
*** oomichi has joined #openstack-meeting06:18
*** MarkAtwood has quit IRC06:18
*** topol has quit IRC06:19
*** lukebrooker has joined #openstack-meeting06:20
*** e0ne has joined #openstack-meeting06:22
*** markvoelker_ has quit IRC06:24
*** jckasper has quit IRC06:26
*** neeti has quit IRC06:28
*** neeti has joined #openstack-meeting06:28
*** lpeer_ has joined #openstack-meeting06:28
*** mrmartin has quit IRC06:29
*** e0ne has quit IRC06:30
*** oomichi has quit IRC06:30
*** haomaiwang has quit IRC06:31
*** lazy_prince has quit IRC06:32
*** fzdarsky__ has joined #openstack-meeting06:32
*** lazy_prince has joined #openstack-meeting06:32
*** Sukhdev has quit IRC06:33
*** numans has joined #openstack-meeting06:34
*** berendt has joined #openstack-meeting06:35
*** markvoelker has joined #openstack-meeting06:35
*** fzdarsky__ has quit IRC06:36
*** stevemar_ has quit IRC06:38
*** lpeer_ has quit IRC06:39
*** jckasper has joined #openstack-meeting06:39
*** jjmb1 has joined #openstack-meeting06:39
*** markvoelker has quit IRC06:40
*** neeti has quit IRC06:40
*** jjmb has quit IRC06:40
*** geoffarnold has quit IRC06:43
*** killer_prince has joined #openstack-meeting06:43
*** geoffarnold has joined #openstack-meeting06:43
*** Murali has joined #openstack-meeting06:44
*** ddieterly has joined #openstack-meeting06:45
*** markvoelker has joined #openstack-meeting06:45
*** lazy_prince has quit IRC06:46
*** bvandenh has joined #openstack-meeting06:47
*** mgrohar has joined #openstack-meeting06:50
*** markvoelker has quit IRC06:50
*** ddieterly has quit IRC06:50
*** vilobhmm11 has quit IRC06:51
*** neeti has joined #openstack-meeting06:52
*** devvesa has joined #openstack-meeting06:52
*** jwang_ has quit IRC06:54
*** jwang_ has joined #openstack-meeting06:54
*** matrohon has joined #openstack-meeting06:56
*** ekarlso has quit IRC06:58
*** markvoelker has joined #openstack-meeting07:00
*** dmacpher has quit IRC07:02
*** peristeri has joined #openstack-meeting07:03
*** SridharG has joined #openstack-meeting07:04
*** geoffarnold has quit IRC07:04
*** markvoelker has quit IRC07:04
*** geoffarnold has joined #openstack-meeting07:04
*** lukebrooker has quit IRC07:04
*** jlanoux has joined #openstack-meeting07:05
*** alexschm has joined #openstack-meeting07:05
*** nadya has joined #openstack-meeting07:05
*** mrmartin has joined #openstack-meeting07:08
*** cloudtrainme has quit IRC07:08
*** markvoelker has joined #openstack-meeting07:14
*** pm90_ has joined #openstack-meeting07:16
*** jcoufal has joined #openstack-meeting07:17
*** achanda has quit IRC07:18
*** kebray has quit IRC07:19
*** jcoufal has quit IRC07:19
*** markvoelker has quit IRC07:19
*** jcoufal has joined #openstack-meeting07:19
*** ildikov has quit IRC07:21
*** achanda has joined #openstack-meeting07:22
*** ekarlso has joined #openstack-meeting07:25
*** MarkAtwood has joined #openstack-meeting07:26
*** okrieg has quit IRC07:27
*** okrieg has joined #openstack-meeting07:28
*** jhenner has joined #openstack-meeting07:28
*** okrieg has quit IRC07:28
*** akamyshnikova_ has joined #openstack-meeting07:29
*** ygbo has joined #openstack-meeting07:29
*** markvoelker has joined #openstack-meeting07:29
*** megm_ has quit IRC07:32
*** markvoelker has quit IRC07:33
*** edtubill has quit IRC07:37
*** megm has joined #openstack-meeting07:38
*** markvoelker has joined #openstack-meeting07:43
*** hashar has joined #openstack-meeting07:45
*** comay has quit IRC07:46
*** ddieterly has joined #openstack-meeting07:46
*** geoffarn_ has joined #openstack-meeting07:46
*** toscalix has joined #openstack-meeting07:47
*** markvoelker has quit IRC07:48
*** geoffarnold has quit IRC07:50
*** yamahata has quit IRC07:50
*** ddieterly has quit IRC07:51
*** xek_ is now known as xek07:53
*** MarkAtwood has quit IRC07:53
*** macjack has joined #openstack-meeting07:54
*** MarkAtwood has joined #openstack-meeting07:56
*** achanda has quit IRC07:57
*** rossella_s has quit IRC07:58
*** markvoelker has joined #openstack-meeting07:58
*** rossella_s has joined #openstack-meeting08:00
*** yassine has joined #openstack-meeting08:00
*** eantyshev has joined #openstack-meeting08:00
eantyshevHello!08:01
*** _amrith_ is now known as amrith08:01
*** mpaolino has joined #openstack-meeting08:01
*** MarkAtwood has quit IRC08:02
*** markvoelker has quit IRC08:02
*** achanda has joined #openstack-meeting08:05
*** mrmartin has quit IRC08:06
*** ralonso has joined #openstack-meeting08:07
*** ralonso has quit IRC08:07
*** geoffarn_ has quit IRC08:07
*** geoffarnold has joined #openstack-meeting08:08
*** amrith is now known as _amrith_08:10
*** ildikov has joined #openstack-meeting08:11
*** mrmartin has joined #openstack-meeting08:11
*** pm90_ has quit IRC08:11
*** markvoelker has joined #openstack-meeting08:13
*** kmartin has quit IRC08:13
*** kmartin has joined #openstack-meeting08:13
*** achanda has quit IRC08:16
*** markvoelker has quit IRC08:18
*** eantyshev has left #openstack-meeting08:22
*** MarkAtwood has joined #openstack-meeting08:23
*** ganeshna has quit IRC08:24
*** pnavarro has joined #openstack-meeting08:27
*** claudiub has joined #openstack-meeting08:27
*** markvoelker has joined #openstack-meeting08:27
*** mrmartin has quit IRC08:28
*** doron_afk is now known as doron08:28
*** geoffarnold has quit IRC08:29
*** geoffarnold has joined #openstack-meeting08:29
*** ricolin has quit IRC08:30
*** vmb_out has quit IRC08:30
*** patrickeast has quit IRC08:30
*** vmb has joined #openstack-meeting08:30
*** skarn has quit IRC08:31
*** mrmartin has joined #openstack-meeting08:32
*** markvoelker has quit IRC08:32
*** patrickeast has joined #openstack-meeting08:32
*** skarn has joined #openstack-meeting08:33
*** ganeshna has joined #openstack-meeting08:36
*** achanda has joined #openstack-meeting08:39
*** markvoelker has joined #openstack-meeting08:42
*** vjay12 has joined #openstack-meeting08:42
*** sudipto has joined #openstack-meeting08:46
*** ddieterly has joined #openstack-meeting08:46
*** markvoelker has quit IRC08:47
*** toscalix has quit IRC08:48
*** vjay12 has quit IRC08:48
*** mrmartin has quit IRC08:49
*** geoffarnold has quit IRC08:50
*** achanda has quit IRC08:50
*** geoffarnold has joined #openstack-meeting08:50
*** ddieterly has quit IRC08:50
*** toscalix__ has joined #openstack-meeting08:51
*** fzdarsky__ has joined #openstack-meeting08:53
*** rbowen has joined #openstack-meeting08:54
*** markvoelker has joined #openstack-meeting08:56
*** deepthi has quit IRC09:00
*** toscalix__ is now known as toscalix09:01
*** markvoelker has quit IRC09:01
*** pelix has joined #openstack-meeting09:03
*** markvoelker has joined #openstack-meeting09:06
*** mbound has joined #openstack-meeting09:07
*** MarkAtwood has quit IRC09:07
*** sankarshan_away is now known as sankarshan09:08
*** markvoelker has quit IRC09:10
*** geoffarnold has quit IRC09:11
*** adiantum has joined #openstack-meeting09:11
*** geoffarnold has joined #openstack-meeting09:12
*** deepthi has joined #openstack-meeting09:12
*** doron is now known as doron_afk09:12
*** markvoelker has joined #openstack-meeting09:13
*** ganeshna has quit IRC09:13
*** markvoelker has quit IRC09:18
*** deepthi has quit IRC09:18
*** markvoelker has joined #openstack-meeting09:22
*** ganeshna has joined #openstack-meeting09:23
*** fzdarsky__ has quit IRC09:26
*** markvoelker has quit IRC09:26
*** fzdarsky has joined #openstack-meeting09:28
*** mrmartin has joined #openstack-meeting09:32
*** markvoelker has joined #openstack-meeting09:32
*** geoffarnold has quit IRC09:33
*** geoffarn_ has joined #openstack-meeting09:33
*** deepthi has joined #openstack-meeting09:34
*** jlanoux has quit IRC09:34
*** jtomasek has joined #openstack-meeting09:35
*** jjmb has joined #openstack-meeting09:35
*** MarkAtwood has joined #openstack-meeting09:35
*** jjmb1 has quit IRC09:37
*** markvoelker has quit IRC09:39
*** ganeshna has quit IRC09:41
*** vjay12 has joined #openstack-meeting09:46
*** markvoelker has joined #openstack-meeting09:46
*** ddieterly has joined #openstack-meeting09:47
*** markvoelker has quit IRC09:50
*** ddieterly has quit IRC09:52
*** MarkAtwood has quit IRC09:52
*** vjay12 has quit IRC09:52
*** geoffarn_ has quit IRC09:54
*** jjmb has quit IRC09:54
*** geoffarnold has joined #openstack-meeting09:54
*** dougshelley66 has quit IRC09:55
*** yassine has quit IRC09:55
*** IanGovett has joined #openstack-meeting09:57
*** ganeshna has joined #openstack-meeting09:57
*** lpeer has quit IRC09:57
*** markvoelker has joined #openstack-meeting10:01
*** dougshelley66 has joined #openstack-meeting10:02
*** e0ne has joined #openstack-meeting10:03
*** markvoelker has quit IRC10:05
*** rossella_s has quit IRC10:06
*** rossella_s has joined #openstack-meeting10:07
*** jlanoux has joined #openstack-meeting10:10
*** markvoelker has joined #openstack-meeting10:11
*** pnavarro has quit IRC10:14
*** ganeshna has quit IRC10:14
*** geoffarnold has quit IRC10:15
*** markvoelker has quit IRC10:16
*** geoffarnold has joined #openstack-meeting10:16
*** markvoelker has joined #openstack-meeting10:17
*** pnavarro has joined #openstack-meeting10:18
*** amakarov_away is now known as amakarov10:19
*** mrmartin has quit IRC10:20
*** markvoelker has quit IRC10:22
*** ganeshna has joined #openstack-meeting10:23
*** sankarshan is now known as sankarshan_away10:23
*** ityaptin_laptop has joined #openstack-meeting10:26
*** markvoelker has joined #openstack-meeting10:26
*** jlanoux has quit IRC10:27
*** mrmartin has joined #openstack-meeting10:27
*** jlanoux has joined #openstack-meeting10:27
*** mrmartin has quit IRC10:27
*** ociuhandu has quit IRC10:32
*** markvoelker has quit IRC10:34
*** geoffarnold has quit IRC10:36
*** geoffarnold has joined #openstack-meeting10:37
*** ihrachys has joined #openstack-meeting10:37
*** jlanoux has quit IRC10:39
*** claudiub has quit IRC10:40
*** jlanoux has joined #openstack-meeting10:40
*** Daisy has joined #openstack-meeting10:41
*** claudiub has joined #openstack-meeting10:43
*** yamamoto has quit IRC10:43
*** ddieterly has joined #openstack-meeting10:48
*** ganeshna has quit IRC10:49
*** topol has joined #openstack-meeting10:50
*** sdake has joined #openstack-meeting10:52
*** ddieterly has quit IRC10:52
*** Daisy has quit IRC10:54
*** Daisy has joined #openstack-meeting10:55
*** claudiub has quit IRC10:55
*** markvoelker has joined #openstack-meeting10:55
*** ociuhandu has joined #openstack-meeting10:57
*** baoli has joined #openstack-meeting10:57
*** geoffarnold has quit IRC10:58
*** geoffarnold has joined #openstack-meeting10:58
*** Daisy has quit IRC10:59
*** claudiub has joined #openstack-meeting11:00
*** markvoelker has quit IRC11:01
*** ildikov has quit IRC11:02
*** ociuhandu has quit IRC11:02
*** ociuhandu_ has joined #openstack-meeting11:02
*** kgroves has joined #openstack-meeting11:03
*** markvoelker has joined #openstack-meeting11:05
*** BharatK has quit IRC11:06
*** qwebirc27362 has joined #openstack-meeting11:06
*** qwebirc27362 has quit IRC11:06
*** ganeshna has joined #openstack-meeting11:07
*** baoli_ has joined #openstack-meeting11:07
*** rbowen has quit IRC11:07
*** baoli has quit IRC11:10
*** ganeshna_ has joined #openstack-meeting11:10
*** ddieterly has joined #openstack-meeting11:10
*** markvoelker has quit IRC11:10
*** ganeshna has quit IRC11:11
*** tfukushima has quit IRC11:15
*** BharatK has joined #openstack-meeting11:17
*** pnavarro is now known as pnavarro|lunch11:18
*** markvoelker has joined #openstack-meeting11:19
anteayamy fault, I missed the third party meeting, I apologize11:19
*** geoffarn_ has joined #openstack-meeting11:20
anteayanot sure if my alarm didn't go off or if I slept through it11:20
anteayaso sorry11:20
*** _amrith_ is now known as amrith11:20
*** kgroves has quit IRC11:21
*** rtheis has joined #openstack-meeting11:22
*** yassine has joined #openstack-meeting11:23
*** geoffarnold has quit IRC11:23
*** amotoki has quit IRC11:24
*** ganeshna_ has quit IRC11:24
*** markvoelker has quit IRC11:24
*** nadya has quit IRC11:25
*** adrianofr has joined #openstack-meeting11:29
*** vjay12 has joined #openstack-meeting11:29
*** ityaptin_laptop has quit IRC11:30
*** nadya has joined #openstack-meeting11:30
*** markvoelker has joined #openstack-meeting11:34
*** markvoelker has quit IRC11:38
*** banix has joined #openstack-meeting11:39
*** ityaptin_laptop has joined #openstack-meeting11:43
*** banix has quit IRC11:46
*** deepthi has quit IRC11:48
*** vjay12 has quit IRC11:48
*** markvoelker has joined #openstack-meeting11:48
*** aloga_ has joined #openstack-meeting11:50
*** vjay12 has joined #openstack-meeting11:51
*** rfolco has joined #openstack-meeting11:52
*** ociuhandu_ has quit IRC11:53
*** markvoelker has quit IRC11:53
*** lpeer has joined #openstack-meeting11:53
*** ociuhandu has joined #openstack-meeting11:54
*** jlanoux has quit IRC11:55
*** gmann_ has joined #openstack-meeting11:56
*** tochi has quit IRC11:57
*** weshay_xchat has joined #openstack-meeting11:57
*** dprince has joined #openstack-meeting11:57
*** aloga_ has quit IRC11:59
*** aloga_ has joined #openstack-meeting11:59
*** jlanoux has joined #openstack-meeting12:00
*** jlanoux has quit IRC12:01
*** jlanoux has joined #openstack-meeting12:01
*** vjay12 has quit IRC12:01
* johnthetubaguy sips his coffee12:02
bauzashaha, I'm not late this time !12:02
* edleafe gulps his12:03
bauzasIIRC, alex_xu was on holidays12:03
*** markvoelker has joined #openstack-meeting12:03
*** mrmartin has joined #openstack-meeting12:03
johnthetubaguyyeah, I think sdague said he would do the honours today12:03
edleafeyeah, that's why I thought we might have canceled it12:03
*** evgenyf has quit IRC12:03
bauzasthat's the golden week12:03
bauzashttp://www.timeanddate.com/holidays/china/12:03
sdagueoh, hey, yep lost track of time12:03
johnthetubaguylots of docs stuff to keep pushing forward12:03
sdague#startmeeting nova-api12:04
openstackMeeting started Tue Oct  6 12:04:07 2015 UTC and is due to finish in 60 minutes.  The chair is sdague. Information about MeetBot at http://wiki.debian.org/MeetBot.12:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:04
*** openstack changes topic to " (Meeting topic: nova-api)"12:04
openstackThe meeting name has been set to 'nova_api'12:04
edleafe\o12:04
sdaguehey there, who's here for the nova-api meeting?12:04
gmann_o/12:04
johnthetubaguyo/12:04
bauzas~o~12:04
*** weshay_xchat is now known as weshay12:04
sdaguethe agenda for today - https://wiki.openstack.org/wiki/Meetings/NovaAPI12:05
sdague#topic action items from last week12:05
*** openstack changes topic to "action items from last week (Meeting topic: nova-api)"12:05
sdaguethere were 2 for alex_xu, who is out, and 1 for johnthetubaguy12:05
sdaguejohnthetubaguy take a look at more about doc unification12:06
sdaguejohnthetubaguy: how did that go?12:06
johnthetubaguyso I have a bit of update here12:06
johnthetubaguythe docs folks seem to have done most of the work for us, which is cool12:06
johnthetubaguyhttps://review.openstack.org/#/c/229546/12:06
johnthetubaguythats the API reference bit, combining the v2.0 and v2.1 and v2.0 extenions12:06
sdaguenice,12:07
* sdague stars that for later review 12:07
johnthetubaguyreviews welcome there, I am sure - I suspect there needs to be some work on the checklinks and the other things, to get that finished off though12:07
johnthetubaguyso there is also a related bit...12:07
*** markvoelker has quit IRC12:07
johnthetubaguyso we need to the the API concept guide published somewhere, official12:07
sdagueinstead of in the devref12:08
johnthetubaguyannegentle has done some heavy lifting there12:08
johnthetubaguyhttps://review.openstack.org/#/c/226253/712:08
johnthetubaguysdague: yeah12:08
johnthetubaguyactually, its the follow on patch12:08
johnthetubaguyhttps://review.openstack.org/#/c/230186/412:08
*** bobh has joined #openstack-meeting12:08
sdagueok, more things starred to review12:08
johnthetubaguyyeah, some progress there12:08
*** adiantum has quit IRC12:09
johnthetubaguyhonestly, would love someone to take that on and keep pushing, its proving tricky with RC2 and spec mountain12:09
gmann_we will have concept guide also on api-site ?12:09
*** jckasper has quit IRC12:09
sdaguethere needs to be an actual project-config change for publish as well, right?12:09
johnthetubaguygmann_: I think the first step is publish it somewhere good then, link to it12:09
johnthetubaguysdague: yeah, it feels like there is tox work and gate job work to make that all real12:09
*** sdake has quit IRC12:09
sdagueok12:09
johnthetubaguynot sure how far anne has got with all those12:10
sdaguelet's try to get the content all landed first12:10
sdaguehow about we set that as a goal for next week12:10
*** sdake has joined #openstack-meeting12:10
johnthetubaguyso get the set of TODOs landed, thats a good goal12:10
johnthetubaguythe content was with alex_xu so I suspect he will start on that when he gets back12:10
sdague#action nova-api team review and land outstanding doc patches for next week - https://review.openstack.org/#/c/230186 https://review.openstack.org/#/c/226253 https://review.openstack.org/#/c/229546/12:11
gmann_+112:11
sdaguewe can check in on it then12:11
johnthetubaguyyeah, more help with that would be good12:11
johnthetubaguyits can be super parallel, everyone take one TODO and add some details12:11
gmann_I can help on those but need to look on those tomorrow12:11
edleafeI'll go over those today, too12:12
johnthetubaguyconverting a big TODO to an intro with smaller TODOs is also cool, in my book12:12
sdaguejohnthetubaguy: where are all the TODOs listed now?12:12
johnthetubaguysdague: its that content patch really, so https://review.openstack.org/#/c/226253/712:12
*** evgenyf has joined #openstack-meeting12:12
sdagueoh, gotcha, I see that now12:12
*** rbowen has joined #openstack-meeting12:13
sdagueyep12:13
johnthetubaguythere is an etherpad, but I think thats mostly been worked through, I am told12:13
johnthetubaguy#link https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking12:13
sdagueso, from here on out I suggest the concept guide progress is a standing agenda item12:13
*** cdub has quit IRC12:13
johnthetubaguyso the patches are on the new etherpad of doom, FWIW ^12:13
johnthetubaguysdague: +112:13
sdague#action sdague to add concept guide progress to standing agenda12:13
sdaguejohnthetubaguy: anything else?12:14
sdague#topic Mitaka Planning12:14
*** MaxPC has joined #openstack-meeting12:14
*** openstack changes topic to "Mitaka Planning (Meeting topic: nova-api)"12:14
*** sudipto has quit IRC12:14
*** markvoelker has joined #openstack-meeting12:14
johnthetubaguysdague: I am good on the previous stuff12:15
johnthetubaguymitaka wise, I think we agreed docs, docs and more docs12:15
sdagueI guess, lets get really near term on mitaka planning12:15
sdagueis there summit actions we need12:15
sdagueI agree that docs, docs, and more docs should be the focus for the cycle12:15
gmann_yea12:16
sdagueI guess I wonder if we should have an API priorities slot on the nova track, mostly to try to get more people involved in the docs effort12:16
sdaguejohnthetubaguy: how did you imagine the nova track is going to look this time?12:16
gmann_saw lot of issues when people submit tempest patches for Nova tests by referring api doc :)12:17
johnthetubaguysdague: so its not fixed in stone yet, I am totally open to what folks think will be useful for the API stuff12:17
bauzasjohnthetubaguy: I guess you need to discuss about the proposals once it's closed, right?12:18
johnthetubaguybauzas: I am happy to discuss it now12:18
sdaguejohnthetubaguy: I feel like it would be nice to have 1 slot if we could, because it may help getting more folks invovled12:18
*** markvoelker has quit IRC12:19
johnthetubaguyits a possible one, I think its important enough12:19
sdagueI guess the other thing that probably needs agreement is how to evaluate both the ec2 potential drop, and the v2 on v2.1 bit for operators12:19
johnthetubaguyI just worried what folks will get out of it, we could have a backup plan of a hackathon on a few fixes, if we finish early I guess12:19
sdagueI think with docs, plus those 2 issues to discuss, we probably have a slot12:20
johnthetubaguyyes, I think we need to follow up with everett on some of that, I know he was thinking about it12:20
johnthetubaguywho is happy to put that proposal together, and drive it?12:20
sdagueI can do that12:20
johnthetubaguysweet12:20
sdagueprobably late today, or tomorrow morning12:21
sdague#action sdague to propose API slot for summit12:21
johnthetubaguysounds good12:21
johnthetubaguygmann_: you mentioned tempest12:21
sdaguebeyond that, I think for mitaka we need to bring back the old standing agenda items about specs with API impact, and API impact reviews to highlight here12:21
johnthetubaguywhat can we do to help there, is that blocked on better docs?12:21
johnthetubaguysdague: oh good point, its time to bring them back12:22
sdagueanyone want to sign up for that agenda change?12:22
gmann_johnthetubaguy: not blocked, due to doc there were wrong response etc on many times12:22
*** pnavarro|lunch is now known as pnavarro12:22
johnthetubaguyI think some focused work on tempest (and in tree functional tests) are well worth it12:22
gmann_johnthetubaguy: then people dig into code12:22
gmann_after doc improvement i think that should be fine12:22
sdague#info we should bring back standing items on specs and patches with APIImpact12:22
johnthetubaguyI was hoping the auto-generated API docs might also generate tests, in some way12:23
johnthetubaguysdague: I am tempted to give that action to alex_xu, but thats feels a bit rude!12:23
sdaguejohnthetubaguy: honestly, everyone wants to autogenerate everything. But in reality some hand crafting usually makes sense here.12:23
*** geoffarnold has joined #openstack-meeting12:23
*** safchain has joined #openstack-meeting12:24
sdagueok, any other mitaka issues before we move to open discussion?12:24
*** geoffarn_ has quit IRC12:24
johnthetubaguysdague: true, more just the heavy lifting I guess12:24
johnthetubaguyI am good for open now12:24
gibihi!12:25
gibiI have a spec up on review about versioning and therefore documenting the notification API of nova. I guess this forum is interested about such an proposal.12:25
gmann_sdague: as johnthetubaguy mentioned any planing to move nova API tests from tempest to nova12:25
gmann_specially negative tests12:25
sdague#topic Open Discussion12:25
*** openstack changes topic to "Open Discussion (Meeting topic: nova-api)"12:25
gibihere is the spec https://review.openstack.org/#/c/224755/12:25
gibiand I here is some WIP example code: https://review.openstack.org/#/c/229881/12:25
sdaguegmann_: so, honestly, I think those are fine to be done.12:25
*** hrou has joined #openstack-meeting12:25
*** haomaiwang has joined #openstack-meeting12:25
sdaguebut they are kind of one off, I did a couple as examples last cycle12:25
*** muawiakhan has joined #openstack-meeting12:26
gmann_sdague: yea flavor one12:26
sdaguegibi: so, this is mostly about the REST API, but I agree that versioned notification api is important as well12:26
*** aysyd has joined #openstack-meeting12:27
gmann_sdague: i will check how we can move all negative one and keep adding more negative on nova side itself12:27
johnthetubaguygibi: so the notification API is probably a bit more for the nova general meeting than the API meeting really12:27
*** nadya has quit IRC12:28
gibisdague, johnthetubaguy: OK, I will then raise it there :)12:28
gmann_because due to lack of negative tests we face issue while v2.1 comp things12:28
*** ddieterly has quit IRC12:28
*** lpeer has quit IRC12:28
*** jcoufal has quit IRC12:28
*** lpeer has joined #openstack-meeting12:28
johnthetubaguygibi: that looks like the plan dansmith was recommending, I see he made some good comments there that need working through12:29
*** markvoelker has joined #openstack-meeting12:29
*** jcoufal has joined #openstack-meeting12:29
sdaguegmann_: right, so those should be filled in on the nova functional side12:29
sdagueI don't think they should go in tempest12:29
johnthetubaguy+112:29
gmann_yea12:29
*** roxanagh_ has joined #openstack-meeting12:30
gibijohnthetubaguy: yes dansmith gave good comments, I just try to gathering more feedback.12:30
*** MarkAtwood has joined #openstack-meeting12:30
gmann_so first move ll negative from Tempest to nova and then add more on nova side itself12:30
johnthetubaguygibi: all good12:30
gmann_is it fine ?12:30
johnthetubaguyso I think we should concentrate on the docs frist12:30
johnthetubaguyfirst12:30
sdaguegmann_: honestly, I would add more tests to nova first12:31
*** Daisy has joined #openstack-meeting12:31
sdaguemoving from tempest doesn't gain anything really12:31
gmann_johnthetubaguy: yea absolutely. after doc thing only12:31
johnthetubaguygmann_: cool12:31
sdagueadding tests to nova for stuff that's not covered does12:31
gmann_sdague: i see, thats also looks good12:31
johnthetubaguysdague: that makes sense, look at proper negative tests in three, then go from there, that makes sense12:31
sdagueand, in general, adding more tests is always a win12:31
gmann_yup12:31
johnthetubaguyI think once our coverage goes up, we just drop the tempest tests12:32
johnthetubaguythats does sound better12:32
sdagueyes12:32
*** mrmartin has quit IRC12:32
sdagueok, anything else from folks?12:33
johnthetubaguyI am good, I think12:33
*** rromans_pto is now known as rromans12:33
bauzasjust a comment that I made a proposal12:33
gmann_me too12:33
bauzasif we have an API slot, we could see if it could be merged12:34
bauzasthat's about API extensibility re: scheduler hints12:34
sdaguecool. slightly related, we're planning on service catalog tng cross project session. I've got to update that spec this week12:34
johnthetubaguybauzas: yeah, that makes sense12:34
sdaguebauzas: honestly, I think we already agreed on that one point, and further changes like that are hard without something like json home12:34
*** roxanagh_ has quit IRC12:34
sdaguewhich is going to be dubious for the release if we are focussed on docs12:35
*** amotoki has joined #openstack-meeting12:35
bauzassdague: okay, then let's discuss that off-topic, I probably missed some discussion :)12:35
sdagueyep, no prob12:35
sdagueok, anything else from folks?12:35
johnthetubaguyso I have a feeling it might be bad enough for v2.1 adoption that its worth covering, but lets see how it goes12:35
sdaguejohnthetubaguy: ok12:35
edleafeI'm good12:36
*** markvoelker has quit IRC12:36
sdaguealright, thanks folks12:36
bauzas+112:36
sdague#endmeeting12:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:36
openstackMeeting ended Tue Oct  6 12:36:48 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-10-06-12.04.html12:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-10-06-12.04.txt12:36
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2015/nova_api.2015-10-06-12.04.log.html12:36
gmann_Thanks all12:36
gibithanks12:37
*** gmann_ has quit IRC12:38
*** ekarlso has quit IRC12:38
*** changzhi has joined #openstack-meeting12:39
*** rromans has quit IRC12:41
*** macjack has quit IRC12:41
*** markvoelker has joined #openstack-meeting12:44
*** bobh has quit IRC12:44
*** ttx has quit IRC12:44
*** ttx has joined #openstack-meeting12:45
*** geoffarn_ has joined #openstack-meeting12:45
*** geoffarnold has quit IRC12:45
*** annegentle has joined #openstack-meeting12:45
*** glauco_ has joined #openstack-meeting12:46
*** rromans has joined #openstack-meeting12:46
*** mrmartin has joined #openstack-meeting12:46
*** markvoelker has quit IRC12:48
*** lixinhui has joined #openstack-meeting12:48
*** pradk has joined #openstack-meeting12:50
*** jaypipes has joined #openstack-meeting12:50
*** julim has joined #openstack-meeting12:50
*** nadya has joined #openstack-meeting12:53
*** ddieterly has joined #openstack-meeting12:53
*** jruano has joined #openstack-meeting12:53
*** Administrator has joined #openstack-meeting12:53
*** Administrator is now known as Guest6102512:53
*** changzhi has quit IRC12:54
*** edleafe has quit IRC12:54
*** Guest61025 has quit IRC12:54
*** rbowen has quit IRC12:55
*** ekarlso has joined #openstack-meeting12:56
*** yanyanhu_ has joined #openstack-meeting12:56
*** edleafe has joined #openstack-meeting12:57
*** Qiming_ has joined #openstack-meeting12:58
*** ZZelle has joined #openstack-meeting12:58
*** markvoelker has joined #openstack-meeting12:58
*** Daisy has quit IRC12:58
*** spzala has joined #openstack-meeting12:58
*** markvoelker has quit IRC12:59
*** markvoelker has joined #openstack-meeting12:59
*** haiwei has joined #openstack-meeting12:59
*** markvoelker_ has joined #openstack-meeting13:01
*** haomaiwang has quit IRC13:01
*** Qiming_ is now known as Qiming13:01
Qiming#startmeeting senlin13:01
openstackMeeting started Tue Oct  6 13:01:19 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
*** elynn has joined #openstack-meeting13:01
*** openstack changes topic to " (Meeting topic: senlin)"13:01
openstackThe meeting name has been set to 'senlin'13:01
*** haomaiwang has joined #openstack-meeting13:01
Qiminghello13:01
*** nate_gone is now known as njohnston13:01
yanyanhu_hi13:01
haiweihi13:01
elynnHi13:01
jruanohello13:01
Qimingwow, you are all here, ;)13:02
*** amrith is now known as _amrith_13:02
yanyanhu_yep :)13:02
*** bswartz has joined #openstack-meeting13:02
lixinhui:)13:02
yanyanhu_just came back from hometown13:02
Qimingpls check agenda and see if you have things to add13:02
Qiminghttps://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Weekly_Senlin_.28Clustering.29_meeting13:02
*** kencjohnston has joined #openstack-meeting13:02
*** dkranz has joined #openstack-meeting13:02
haiweinice holiday13:02
QimingI was expecting that I will be alone here, since it is holiday for most of us13:03
*** jhesketh has quit IRC13:03
*** markvoelker has quit IRC13:03
yanyanhu_;)13:03
Qiming#topic liberty work items13:03
*** openstack changes topic to "liberty work items (Meeting topic: senlin)"13:03
Qimingthe etherpad page loads pretty slow13:04
*** jhesketh has joined #openstack-meeting13:04
Qimingwe still have some items left there, have to postpone to next cycle13:04
Qimingfor the container work, will get an update from SUR team tonight -- 1 hour later13:05
yanyanhu_about the unit test in senlinclient, have we done it?13:05
jruanoyes, i sent out a request qi ming. haven't heard anything back13:05
Qimingyanyanhu_, that is something we need to postpone13:05
yanyanhu_ok13:05
*** obondarev has joined #openstack-meeting13:06
*** geoffarn_ has quit IRC13:06
haiweisorry about that, I should do that13:06
Qimingjruano, you are in that meeting, I haven't heard anything last week13:06
jruanothere is some interesting client code, but all the specs for profile and policy are not checked into the repo13:06
*** obondarev has quit IRC13:06
jruanoyep13:06
*** amotoki has quit IRC13:06
*** markvoelker has joined #openstack-meeting13:06
QimingI have invited Liam to join that discussion13:06
*** obondarev has joined #openstack-meeting13:06
*** geoffarnold has joined #openstack-meeting13:06
jruanoton and i have defined the use cases, and i want to start understanding how/where senlin fits13:07
Qiminghaiwei and I should spend sometime on client test cases anyway13:07
Qimingyep, jruano, need to touch base with the eam13:07
haiweiyes, Qiming13:07
Qimings/eam/team13:07
yanyanhu_I think we can work on it together in the coming cycle.13:07
yanyanhu_I will spend some time on it as well13:08
Qimingokay, we have just got an +2 on the patch to propose senlinclient into global requirements13:08
elynngood news13:08
yanyanhu_cool13:08
jruanoawesome13:08
haiweisaw it13:08
Qiminghope it will be approved soon, so it won't block senlin-dashboard progress13:08
yanyanhu_this is helpful for elynn I think13:08
Qimingyanyanhu_, do we have more to add regarding functional tests?13:09
yanyanhu_for the senlin support in heat13:09
*** killer_prince has quit IRC13:09
elynnyes13:09
yanyanhu_Qiming, I guess not for now13:09
*** sheeprine has quit IRC13:09
Qiminggreat13:09
*** sheeprine has joined #openstack-meeting13:09
haiweigreat job yanyanhu13:09
yanyanhu_oh, maybe still a little more work on node13:09
*** sdake has quit IRC13:09
*** ddieterl_ has joined #openstack-meeting13:10
Qimingelynn, we need to sit together for a discussion on how to get heat resource types work13:10
yanyanhu_but I think it won't take much time13:10
*** sdake has joined #openstack-meeting13:10
*** markvoelker_ has quit IRC13:10
elynnQiming: yes, when I get back from holiday.13:10
Qimingyanyanhu_, alright, let's get it done then we switch to mitaka work items13:10
yanyanhu_ok13:11
Qiming#topic placement policy13:11
*** openstack changes topic to "placement policy (Meeting topic: senlin)"13:11
Qiminglixinhui, anything to share from your side?13:11
lixinhuiI am working on vSphereDRS_policy13:12
lixinhuiand unit test13:12
lixinhuiwill submit patch around this Thursday13:12
Qimingokay, cool13:12
lixinhuiNeed your help to review then :)13:12
*** sdake_ has joined #openstack-meeting13:12
haiweiin fact I am not familiar with vSphereDRS_policy13:12
*** changbl has quit IRC13:13
QimingLiuwei's patch reagarding az placement policy needs a patch13:13
lixinhuioh?13:13
lixinhuiMaybe I can help13:13
haiweiwhat is the relationship between vSphereDRS_policy and placement policy13:13
*** maishsk has joined #openstack-meeting13:13
*** lpeer has quit IRC13:13
Qimingseems we need a doc for every policy?13:13
lixinhuiI think he has done that part13:13
*** ddieterly has quit IRC13:13
*** lpeer has joined #openstack-meeting13:13
yanyanhu_Qiming, agree.13:13
yanyanhu_and I noticed you have worked on docstring13:14
haiweiit will help me at least13:14
lixinhuiOkay13:14
lixinhuireasonable13:14
Qimingem. for all builtin policies, we need some docs explaining how it works13:14
*** sdake has quit IRC13:14
lixinhuiI could add some when the patch done13:14
Qimingsounds great13:15
yanyanhu_maybe we should always adding docstring when adding new features13:15
Qiminglixinhui, Liuwei's patch: https://review.openstack.org/22168413:15
*** raildo-afk is now known as raildo13:15
haiweithanks lixinhui13:15
lixinhuiOkay, Qiming13:15
lixinhuiI will read it13:15
Qimingyanyanhu_, by docs, I am referring to some design level things, not just function level comments13:15
*** rbowen has joined #openstack-meeting13:16
Qiminglixinhui, it is in a pretty good shape now13:16
jruanoyes i think that will help13:16
*** oomichi has joined #openstack-meeting13:16
yanyanhu_yes, this is nice since it can help people understand the implementation better13:16
Qimingthe placement policy patch can be tweaked a little bit to support cross-region placement13:17
*** markvoelker has quit IRC13:17
lixinhuiOkay, Qiming13:17
*** ildikov has joined #openstack-meeting13:17
Qimingyanyanhu_, can you have add a TODO item in the TODO.rst file? don't want this ball dropped, :)13:17
*** markvoelker has joined #openstack-meeting13:17
*** neelashah has joined #openstack-meeting13:18
yanyanhu_sure13:18
Qiming#topic deletion policy for RESIZE operation13:18
*** openstack changes topic to "deletion policy for RESIZE operation (Meeting topic: senlin)"13:18
*** ccarmack has joined #openstack-meeting13:18
Qiminghaiwei has helped start this thread13:18
Qimingso far the implementation is not correct in my opinion13:19
haiweiI thought it was not difficult, but it seems not13:19
Qimingyep13:19
Qimingthere are many easier paths to get this done, but we have to look at the big picture13:20
haiweiI think the problem is that resize action can delete nodes more than one at a time13:20
haiweiyes13:20
Qimingmaybe we can extract the parsing of RESIZE parameters into a utility function13:21
Qimingwe then call that function directly if no policy is attached to the cluster13:21
*** bobh has joined #openstack-meeting13:22
haiweithat will be done inside the action execution?13:22
Qimingif we do have certain policies that want to handle RESIZE action, we invoke this parser as well13:22
haiweisounds a good idea13:23
*** Guest92657 is now known as grumpycatt13:23
*** hichihara has joined #openstack-meeting13:23
Qimingin action execution, we check if there are policy outputs and skip the parsing if seemed unnecessary13:23
haiweiI think this should be done in the engine/service layer13:23
Qimingthere will be concurrency problems if you do maths there13:23
Qimingthe cluster is not locked13:23
*** njohnston is now known as nate_gone13:23
Qimingany other actions can change the cluster at the same time13:24
*** wbhuber has joined #openstack-meeting13:24
*** thangp has joined #openstack-meeting13:24
haiweibut for deletion policy the pre_op in which candidates are chosen in done before resize action execution13:24
yanyanhu_haiwei, I think you can refer to the implementation of do_scale_in/out13:24
*** rbowen has quit IRC13:25
yanyanhu_they have similar problem13:25
Qimingagreed, scale_in/scale_out is a good reference13:25
haiweiyanyanhu, the problem is do_scale_in/out only delete one node at a time13:25
haiweibut resize action is different13:25
Qimingscale_in/out can carry a 'count' parameter13:26
haiweihow to initialize 'count' in pre_op is difficult for resize action13:26
Qimingin the case of resize, there are more parameters to handle13:26
yanyanhu_yes, haiwei, just as Qiming said, those two actions can also accept 'count' input13:26
*** haomaiwang has quit IRC13:27
*** geoffarnold has quit IRC13:27
yanyanhu_haiwei, yes, the logic is more complicated since the constraint might be changed at the same time13:27
Qiminghaiwei, I was suggesting to extract the "count" computation into a utility function13:27
haiweii know that, those 'count' is default to 1, but resize action is different, we have to give it a value13:27
yanyanhu_but I think you can split the logic out13:27
*** geoffarnold has joined #openstack-meeting13:27
*** haomaiwang has joined #openstack-meeting13:27
haiweiok, I think I got you13:28
*** nate_gone is now known as njohnston13:28
Qiminggreat13:28
Qiming#topic policy for node create/delete13:28
*** openstack changes topic to "policy for node create/delete (Meeting topic: senlin)"13:28
*** lblanchard has joined #openstack-meeting13:28
Qimingso far we have been focusing on CLUSTER_XYZ actions when dealing with policies13:28
Qiminghowever, we do have NODE_CREATE/DELETE/JOIN/LEAVE actions13:29
*** amotoki has joined #openstack-meeting13:29
Qiminga NODE_CREATE action, with cluster_id provided, needs to be considered by the LB policy, for example13:29
yanyanhu_yes13:29
yanyanhu_ideally, those node_xxx actions should also be the target of some policies13:30
QimingI have been looking at this during the past days13:30
QimingI'm hoping this won't be a disruptive change to the current policy implementation13:31
yanyanhu_umm, we need to think through this...13:32
Qiminganyway, I'll keep working on this13:32
yanyanhu_will think about it13:32
Qimingokay, feel free to ping me for a discussion13:32
yanyanhu_sure :)13:33
Qiming#topic batch policy13:33
*** openstack changes topic to "batch policy (Meeting topic: senlin)"13:33
haiweiQiming, you mean you will focus on the LB policy only?13:33
*** bill_az_ has joined #openstack-meeting13:33
Qiminghaiwei, no13:33
Qimingit is more about how to weave NODE_xxx actions into policy checking13:33
*** amotoki has quit IRC13:33
*** armax has joined #openstack-meeting13:33
Qimingnot just for LB policy13:33
haiweiok13:34
Qimingplacement policy, for example, is another case where NODE_CREATE action should be checked13:35
haiweiand also placement policy13:35
haiweiyes13:35
Qiming:)13:35
Qiming#topic batching policy13:36
*** openstack changes topic to "batching policy (Meeting topic: senlin)"13:36
Qimingbatching policy is really about throttling13:36
Qimingwhen creating/updating/deleting objects, senlin makes calls to other services13:37
Qimingwe have to impose some constraints on the number requests sent to other services during any given period13:37
Qimingthis is not an easy job as it seems to be13:38
Qimingtake CLUSTER_CREATE as an example13:38
Qimingwe want to control how many NODE_CREATE (thus nova boot requests after translation) we will trigger13:39
*** vgridnev has joined #openstack-meeting13:39
*** amotoki has joined #openstack-meeting13:39
*** KLevenstein has joined #openstack-meeting13:39
Qiminghowever, the cluster is just being created, no policy has a chance to get attached to it yet13:39
Qimingit becomes a chicken-and-egg problem13:40
*** banix has joined #openstack-meeting13:40
Qimingso ... the question becomes: how can we do throttling without a policy13:41
elynnDefine it in senlin.conf?13:41
yanyanhu_Qiming, I think maybe we can split a cluster creation into multiple action sets, and there are dependencies between them?13:41
haiweimaybe we only attach batch policy after the cluster is created?13:41
QimingI just proposed a configuration option, max_actions_per_batch13:42
yanyanhu_but the existing dependency logic may not be able to support it13:42
Qimingit can be overridden later by a batching policy13:42
Qimingright, the current batched creation logic has to be revised to support this option13:43
yanyanhu_hmm, my idea is not good. It is too far from our policy framework13:44
*** vikram_ has joined #openstack-meeting13:44
*** pm90_ has joined #openstack-meeting13:44
QimingI am starting to change my mind now13:45
*** lazy_prince has joined #openstack-meeting13:45
Qimingsince we are executing all 'actions' asynchronously13:45
*** cbouch has joined #openstack-meeting13:45
*** balajiiyer has joined #openstack-meeting13:45
Qiming(at least we wanted to do things that way)13:46
*** pballand has quit IRC13:46
Qimingall actions are first persisted into database13:46
Qimingthen retrieved for execution13:46
Qimingso that throttling problem seems more like a scheduler problem13:47
yanyanhu_yes13:47
*** pm90__ has joined #openstack-meeting13:47
yanyanhu_it is13:47
*** john-davidge has joined #openstack-meeting13:47
Qimingsay if we create a cluster of 1000 nodes13:47
*** hoangcx has joined #openstack-meeting13:47
*** haomaiwang has quit IRC13:47
yanyanhu_or it can be13:47
jruanosounds like it13:47
Qimingthe 1000 NODE_CREATE actions are supposed to be executed in a controlled way13:48
*** oomichi has quit IRC13:48
*** Daisy has joined #openstack-meeting13:48
*** mrmartin has quit IRC13:48
*** enikanorov has joined #openstack-meeting13:48
Qimingso ... I am inclined to looking at it from a different angel now13:49
*** tidwellr has joined #openstack-meeting13:49
*** amotoki has quit IRC13:49
Qimingthe problem is: how do we define the 'batching' policy then?13:49
haiweiby the way, this policy is triggered by hand?13:49
*** pm90_ has quit IRC13:49
*** Murali has quit IRC13:50
Qiminghaiwei, all policies are supposed to be triggered by certain actions13:50
*** haomaiwa_ has joined #openstack-meeting13:50
jruanoset of rules to a scheduler13:50
haiweiso we need a new action for it?13:50
yanyanhu_haiwei, I think we just manually provide the rule13:50
Qimingfor creation/deletion, it sounds more like a scheduler parameter13:50
elynnSo is it still needed?13:51
Qimingfor update, it may carry some other QoS related semantics13:51
*** rkukura has joined #openstack-meeting13:51
*** lzachery has joined #openstack-meeting13:51
yanyanhu_yes. maybe we can start to consider the refactoring of engine scheduler13:51
Qimingduring batched update, users may want to keep a certain number of service node running at any time13:51
Qimingyanyanhu_, yes, that is why I wasn't proposing a lot of patches recently, :)13:52
*** radez` is now known as radez13:52
Qimingreally blocked by this problem13:53
*** vmb is now known as vmbrasseur13:53
Qimingmaybe we need to refactor the engine scheduler first13:53
yanyanhu_ok, lets think about it :)13:53
Qimingmake it a 'real' scheduler13:53
yanyanhu_yep13:53
Qimingthen we do 'scheduler.reschedule()' whenever necessary, just like a tickless Linux kernel13:53
*** vijendar has joined #openstack-meeting13:53
*** trozet has quit IRC13:54
Qimingmaybe we need to change 'batching' policy to just an 'update' policy13:54
yanyanhu_right13:54
*** mrmartin has joined #openstack-meeting13:55
Qimingwill keep thinking of this13:55
Qiming#topic open discussions13:55
*** openstack changes topic to "open discussions (Meeting topic: senlin)"13:55
*** jlibosva has joined #openstack-meeting13:55
*** cdub has joined #openstack-meeting13:56
Qimingregarding big tent proposal, I'm drafting it in the coming days13:56
haiweiI will have a small session about senlin in my company's booth during the summit13:56
Qimingwill send out to everyone for review13:56
Qimingthx, haiwei, ping us if any help needed13:56
yanyanhu_haiwei, cool :)13:56
jruanonice13:56
lixinhuigreat!13:57
Qimingabout the meetup during summit, the room allocation is pretty tight13:57
yanyanhu_will visit your booth ;p13:57
haiweiI will prepare for the presentation , and want you to advices13:57
Qiming   http://lists.openstack.org/pipermail/openstack-dev/2015-October/076054.html13:57
Qimingsure13:57
Qimingneed to find out how to get everyone together for a f2f discussion13:57
*** MarkAtwood has quit IRC13:58
*** dan-t has joined #openstack-meeting13:58
*** dan-t has left #openstack-meeting13:58
Qiminganything else13:58
Qiming?13:58
haiweino13:58
Qiminghoho, 1 min left13:58
yanyanhu_nope13:58
jruanonope13:58
elynnnope13:58
Qimingthanks for joining, during your vacation13:59
*** johnsom__ has joined #openstack-meeting13:59
*** regXboi has joined #openstack-meeting13:59
Qimingtalk to you later13:59
Qiming#endmeeting13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:59
openstackMeeting ended Tue Oct  6 13:59:17 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-10-06-13.01.html13:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-10-06-13.01.txt13:59
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2015/senlin.2015-10-06-13.01.log.html13:59
*** pc_m has joined #openstack-meeting13:59
*** emagana has joined #openstack-meeting13:59
*** haiwei has quit IRC13:59
armaxhi13:59
*** gongysh has joined #openstack-meeting13:59
regXboiola13:59
* mestery wanders in13:59
pc_mhi13:59
john-davidgehi13:59
rossella_shi13:59
hichiharahi13:59
tidwellrhi13:59
dougwigMorning13:59
jlibosvahi13:59
armaxmestery, ajo, ihrachys, folks13:59
* regXboi finds a seat next to the chalkboard13:59
ZZelleHi13:59
*** yamamoto has joined #openstack-meeting13:59
ihrachysmeeting time! :)13:59
ihrachyso/13:59
emaganahello!13:59
akamyshnikova_hi13:59
mesteryihrachys: Welcome back from your vacation! :)13:59
johnsom__Hi all14:00
gongyshhello14:00
armax#startmeeting networking14:00
openstackMeeting started Tue Oct  6 14:00:08 2015 UTC and is due to finish in 60 minutes.  The chair is armax. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
haleybhi14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
ihrachysmestery: WAT? but whatever14:00
yamamotohi14:00
scheuranhi14:00
HenryGo/14:00
*** Sukhdev has joined #openstack-meeting14:00
*** korzen has joined #openstack-meeting14:00
johnsom__o/14:00
*** amuller has joined #openstack-meeting14:00
*** srikanth-p_ has joined #openstack-meeting14:00
xgermano/14:00
vikram_hi14:00
*** johnbelamaric has joined #openstack-meeting14:00
* dougwig yawns14:00
*** amotoki has joined #openstack-meeting14:00
*** jprovazn has joined #openstack-meeting14:00
armaxwelcome everybody who made it14:00
hoangcxhi14:00
*** haomaiwa_ has quit IRC14:01
Sukhdevhello14:01
kevinbentonHi!14:01
armax#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:01
emaganasleepy but ..  :-)14:01
amotokihi14:01
armaxI see lots of people scratching their eyes :)14:01
*** haomaiwang has joined #openstack-meeting14:01
*** derekh has joined #openstack-meeting14:01
armax#topic Announcements14:01
*** lixinhui has quit IRC14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
*** jschwarz has joined #openstack-meeting14:01
*** yanyanhu_ has quit IRC14:01
armaxWe had an RC2 churning the last couple of days14:01
*** carl_baldwin has joined #openstack-meeting14:02
*** ajo_ has joined #openstack-meeting14:02
armax#link https://launchpad.net/neutron/+milestone/liberty-rc214:02
*** bryan_att has joined #openstack-meeting14:02
ajo_o/ (sorry to be late ;)14:02
armaxmestery: what’s the latest?14:02
armaxajo_: welcome14:02
*** ajo_ is now known as ajo14:02
armaxwe good?14:02
mesteryarmax: We have one patch in the merge queue then RC2 will be cut14:02
ajoyeah, thanks :)14:02
obondarevhi14:02
mestery#link https://review.openstack.org/#/c/231362/14:02
*** Qiming has left #openstack-meeting14:02
mestery#link https://review.openstack.org/#/q/project:openstack/neutron+branch:stable/liberty,n,z14:02
*** jschwarz_ has joined #openstack-meeting14:03
armaxmestery: ok, let’s hope there’s no last minute scare14:03
armaxwe’re really running out of time14:03
mesteryYes14:03
mesteryTime is gone now14:03
ihrachysmestery: actually https://review.openstack.org/#/q/status:open+project:%255Eopenstack/neutron.*+branch:stable/liberty,n,z is better14:03
armaxHenryG: we good as far as DB goes?14:03
mesteryihrachys: Ack :)14:03
*** mhickey has joined #openstack-meeting14:03
HenryGarmax: yup14:03
armaxok14:03
ajook, that patch, is good to have, but if not merged, we can go14:03
armax#link https://wiki.openstack.org/wiki/ReleaseNotes/Liberty#OpenStack_Liberty_Release_Notes14:03
ajoI mean, that bug is not actually happening in liberty, but in earlier releases, and off-gate14:03
armaxplease can we all check that we haven’t missed anything?14:03
ajobut it's a fix we'd want backported to kilo14:04
armaxajo: cool, thanks for clearing that up14:04
ajoso, if it doesn't merge, IMHO , feel free to cut, we're safe14:04
amotoki231362 has no cherry-picked line. it's a nit though...14:04
* armax looks14:04
ajooh, true amotoki , I used the gerrit interface, I didn't realize14:04
ihrachys"Neutron now supports a way that an agent can start without selectable for auto-scheduling but manual-scheduling available so that a deployer can test an agent manually" am I the only one who fails to parse?14:05
*** mrmartin has quit IRC14:05
ajoI guess the change-id keeps the traceability14:05
armaxum, yeah14:05
*** dane_leblanc has joined #openstack-meeting14:05
amotokiyeah. I don't think we need to pull it from the queue.14:05
armaxI don’t see it in the gate queue14:05
*** mpaolino has quit IRC14:05
ihrachysamotoki: actually, cherry-picked from line had some tech meaning (there was a bug in gerrit where it merged a patch into wrong branch if it was not present)14:05
armaxat all14:05
*** jschwarz has quit IRC14:06
armaxbut ttx approved it14:06
kevinbentonihrachys: that's scary14:06
ajoarmax, ok, let's edit the commit message and get's the votes fixed quick, that's likely to retrigger the gate14:06
armaxnot sure if it was a simple oversight14:06
ihrachyskevinbenton: it is. now you understand why I pick nits on backports?14:06
*** rossella_s has quit IRC14:06
armaxok14:06
*** lazy_prince has quit IRC14:06
* ajo does14:06
mesteryWait, we're pulling it out of the gate to add a cherry-pick line?14:06
mesteryWhy?14:07
armaxajo: the queue is 20+ patches deep14:07
*** rossella_s has joined #openstack-meeting14:07
* ajo waits14:07
carl_baldwinihrachys: Do you have a link to some info on that bug. I’ve never heard of it.14:07
mesteryPlease don't do that, ttx and I already approved it and it's the last one14:07
ajook14:07
armaxand hte check queue is 60+ patches deep14:07
mesteryRight14:07
armaxmestery: ok14:07
* ajo stops14:07
mesteryCool14:07
mestery:)14:07
armaxbut I don’t see the change in the queue at all14:07
mesteryWhew :)14:07
mesteryIt's in the merge queue armax14:07
armaxsomething is up!14:07
ajo':)14:07
mestery231362?14:07
armaxoh found it14:08
mesteryarmax: :)14:08
regXboiIt's building right now14:08
armaxok, wer’e good14:08
ihrachyscarl_baldwin: I suggest people to read the guidelines: https://wiki.openstack.org/wiki/StableBranch#Proposing_Fixes14:08
ihrachyssee in bold14:08
armaxlet’s move on14:08
mesteryYes14:08
*** rbak has joined #openstack-meeting14:08
armaxyes…let’s accept it as a momentary lapse of the reason14:08
*** dan-t has joined #openstack-meeting14:08
mestery++14:09
armax#info People should remember to do cherry-pick -x on their cherry picks14:09
*** ityaptin_laptop has quit IRC14:09
mesterySanity prevails! Yay! :)14:09
armaxajo: capisce?14:09
ajoihrachys: it's sad I know it, but I trusted gerrit on doing the right thing on the "cherry-pick" button ;(14:09
ajoYou can't even trust a machine..14:09
ajo(it seems)14:09
*** elynn_ has joined #openstack-meeting14:09
ihrachysajo: it fails to do it until the patch is not merged.14:09
kevinbentonI always just made up the hash after the cherry picked from statement. I didn't know it meant something :)14:09
ajoihrachys: yikes, understood14:09
ajokevinbenton: made up like in uuidgen ?14:10
ajoX)14:10
ajosorry, that's not an uuid... ;D14:10
armaxok, next14:10
armaxbefore we do that14:10
armaxmestery: anything else?14:10
*** lazy_prince has joined #openstack-meeting14:10
armaxanyone else on RC2?14:10
armaxcomments?14:10
*** sigmavirus24_awa is now known as sigmavirus2414:10
mesteryWell14:10
kevinbentonThere is also a stable/kilo release very soon, right?14:10
mesteryjohnsom__ has indicated there are 3 LBaaS bugs which woudl be good to get in RC214:11
mesterySo I'm doing cherry-picks now14:11
*** _amrith_ is now known as amrith14:11
*** emagana has quit IRC14:11
ihrachyskevinbenton: yes, week+ from now14:11
mesteryAnd I'll work offline with him on those14:11
johnsom__I am chatting with mestery about a couple of neutron-lbaas issues that fell through the cracks14:11
xgerman+114:11
*** emagana has joined #openstack-meeting14:11
ajook, for kilo, please: http://docs.openstack.org/developer/stevedore/patterns_loading.html#hooks-single-name-many-entry-points14:11
ajoargh..14:11
ajosorry :(14:11
ajohttps://review.openstack.org/#/c/231363/14:11
ajothat's what I meant14:11
ajosame ipset fix, for kilo, I will fix the cherry-pick reference14:12
*** elynn has quit IRC14:12
ihrachysajo: I'll handle the kilo queue after the meeting14:13
ajothanks ihrachys14:13
*** Guest28678 is now known as redrobot14:13
armaxok cool, I think we’re set then14:13
armaxif not, let’s quickly reconvene on our channel after the call14:14
* armax wants to go to bed again after this ;)14:14
emaganaarmax: same here!14:14
armaxso, next reminder:14:14
ajothanks armax  & emagana14:14
armax#link http://docs.openstack.org/developer/neutron/policies/index.html14:15
armaxwe review/revise them as they go14:15
armaxwe need to see what works and what doesn’t14:15
*** stanchan has quit IRC14:15
armaxand make sure we are a well oiled machine as a much as we can be14:15
mesteryarmax: ++14:16
armaxI proposed changes to the way we handle bugs last week14:16
armax#link http://docs.openstack.org/developer/neutron/policies/bugs.html14:16
emagana+114:16
Sukhdevarmax: I have an announcement14:16
ajo+1 :)14:16
armaxthe reaction was overwhelmingly positive14:16
armaxSukhdev: wait your turn please14:16
Sukhdevsorry - still sleepy14:17
*** eharney has joined #openstack-meeting14:17
armaxplease make yourself familiar with the new guidelines14:17
armaxand reach out to us for questions or propose edits yourself14:17
*** yamini_ has joined #openstack-meeting14:17
*** Daisy has quit IRC14:17
armaxafter all, we all own the policies14:17
armaxSukhdev: you’re up14:18
*** yamini has joined #openstack-meeting14:18
*** Daisy has joined #openstack-meeting14:18
SukhdevWe are having ML2 sprint today and tomorrow for anybody interested in it14:18
Sukhdevhere is the information - https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint14:18
Sukhdev#link: https://etherpad.openstack.org/p/Neutron_ML2_Mid-Cycle_Sprint14:18
ajoyou should call it pre-cycle :D14:18
Sukhdevit will cover few critical issues for ML214:19
mesterySukhdev: The secret ML2 illuminati meeting? :)14:19
armaxpre-wash?14:19
ajolol14:19
* regXboi likes pre-wash14:19
*** ayoung has joined #openstack-meeting14:19
mesterylol14:19
Sukhdevmestery: no secret - it was announced on ML weeks ago14:19
*** Kanchan has joined #openstack-meeting14:19
*** Guest83454 is now known as mfisch14:19
armaxI hope those issues are washed at high temperature14:19
Sukhdevpre-Mitaka14:19
mesterySukhdev: I'm kidding, mostly14:19
armaxsome stains won’t go away otherwise14:19
* regXboi wonders if we should say pre-OH14:19
*** Daisy has quit IRC14:19
*** mfisch is now known as Guest9449014:20
*** Daisy has joined #openstack-meeting14:20
Sukhdevwhats pre-OH?14:20
*** cdub has quit IRC14:20
ajoSukhdev, thanks, sounds interesting, I will be watching14:20
armaxok, last announcement/reminder14:20
regXboipre-alcohol14:20
emaganaregXboi: Love it!14:20
armaxWe started our collictive guide14:20
armax#link http://docs.openstack.org/developer/neutron/devref/effective_neutron.html14:20
armaxif you want to make changes to it, please tag the change with the ‘effective’ topic14:21
armax*collective14:21
* regXboi definitely thinks we should be considered a "well c2h5oh-ed" group :)14:22
* dougwig groans14:22
* ihrachys shrugs14:22
* kevinbenton thinks regXboi took long to respond because he was looking that up on the Internet 14:22
*** neeti has quit IRC14:23
emaganakevinbenton: lol14:23
*** brad_behle has joined #openstack-meeting14:23
* regXboi says - no, he was double checking with the chemist in the house - his wife :)14:23
mesterylol14:23
armaxthe outstanding patches to the guide are:14:23
armaxhttps://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:effective,n,z14:23
ajoarmax, it's a nice devref guide, there are so many questions/mistakes which repeat over time14:23
armaxfeel free to check them out and post comments14:24
armaxajo: that’s the idea14:24
amotokiit is also a good chance to remember openstack common practices :-)14:24
armaxthe more useful content we add, the better it is14:24
armaxwe should strive to add Neutron-specific content14:24
armaxafter all we’re more hopeless than other openstack projects14:24
armaxas some people might think14:24
kevinbentonI thought you told me that the less content I added, the better it would be?14:24
*** spotz_zzz is now known as spotz14:24
armaxkevinbenton: no I mean, overall14:25
kevinbenton:)14:25
armaxnot per bullet point14:25
armaxany other announcement?14:25
*** Murali has joined #openstack-meeting14:25
ihrachysarmax: I guess a link to another page with broader discussion of a topic is applicable there.14:25
*** jckasper has joined #openstack-meeting14:25
mesteryarmax: Perception lags reality, but only when people are lucid14:25
armaxsorry, not following14:26
armaxI haven’t had my morning coffee yet14:26
kevinbentonWho is throwing the Tokyo party? amotoki??14:26
mesteryarmax: You must not be lucid14:26
mestery:)14:26
mesterykevinbenton: Doesn't matter who's throwing, armax is buying right?14:26
emaganayou both armax and mestery should be buying!14:26
armaxihrachys: you mean this?14:26
armax#link http://lists.openstack.org/pipermail/openstack-dev/2015-October/076190.html14:26
emaganaI want sake!14:26
ihrachysarmax: if it's for me, I mean, let's say I want to cover upgrade, but that's a huge topic, so I create a new page in devref. Should I link to it from effective?14:26
armaxihrachys: oh, yes14:27
armaxihrachys: I think that’s mentioned in the introduction to the guide14:27
amotokikevinbenton: I am looking for a place...14:27
armaxihrachys: if you need to expand feel free to just provide the pointer14:27
ihrachysoh poor me. ok.14:27
armaxemagana: as I said, since we’re the one providing the service, we’re the one that should be bought drinks ;)14:27
kevinbentonamotoki: punishment for not finding one is you host it in your home14:28
* markmcclain sneaks in late from teh car dealership14:28
kevinbenton:)14:28
armaxZZelle: ping14:28
*** stevemar_ has joined #openstack-meeting14:28
*** cody-somerville has joined #openstack-meeting14:28
ZZellearmax, pong14:28
*** fawadkhaliq has joined #openstack-meeting14:28
armax#topic Bugs14:28
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:28
armaxZZelle: hi14:28
amotokikevinbenton: my home is not so near to the summit :-(    you can enjoy one hour train.14:28
emaganaarmax: actually that is a good idea... who is working for an operator?  :-014:28
regXboiparty on the train?14:28
armaxwith the changes in bug management procedures14:29
armaxwe started looking at the backlog of bugs we have pending and that’s...14:29
armaxhuge14:29
*** achanda has joined #openstack-meeting14:29
regXboiarmax: ++ for each bug :(14:29
*** geoffarnold has quit IRC14:29
*** bswartz has quit IRC14:29
armaxbetween client and server we have 1000+ open bugs14:29
armaxsome may as well be junk14:29
ajoouch14:29
armaxbut we don’t know until we have a good handle on these14:30
njohnstonoi14:30
*** geoffarnold has joined #openstack-meeting14:30
armaxso we gotta figure out a plan to bring those down14:30
armaxZZelle has been looking at expiring some of those14:30
ihrachysarmax: take 100, distribute 10 per core, expect them to be triaged till next week?14:30
kevinbentonI think bug fixes would be good14:31
ajoihrachys, that could sound good14:31
ZZelleWe have a lot of bugs, a lot of bugs with no activity in the last 12 months: ~ 120 bugs14:31
armaxbugs that are marked incomplete, unassigned and untargeted expire after 60 days14:31
regXboiI'd vote for getting those 120 into that state14:31
armaxthat should give us enough time to look at them and revive those that might be relevant14:31
armaxfor those that aren’t14:31
armaxthe LP janitor will eventually evict them14:31
armaxso if everyone is okay with that strategy14:32
armaxZZelle: fire away!14:32
*** jaypipes has quit IRC14:32
dougwigif we've been that lax on bugs, we might even want to scrub the recently expired (<6 months)14:32
ihrachysarmax: no triage, just move them to the state?14:32
armaxihrachys: LP has a link14:32
ajodougwig, expired go when incomplete & not assigned & not targetted if I din't get it wrong14:32
*** markvoelker_ has joined #openstack-meeting14:32
ajoI guess somebody scrub those to become expired14:33
ajoscrubbed14:33
armax#link https://bugs.launchpad.net/neutron/+expirable-bugs14:33
*** roxanagh_ has joined #openstack-meeting14:33
*** roxanagh_ has quit IRC14:33
armaxihrachys: after ZZelle fired his script14:33
armaxthose bugs should appear under that link14:33
*** numans has quit IRC14:33
ihrachysbut should we triage bugs before marking them for expiration?14:33
*** roxanagh_ has joined #openstack-meeting14:33
regXboiajo: if at Tzero a bug is moved to incomplete/unassigned/untargeted, then at Tzero+60 days, it will be expired by the LP janitor14:33
armaxand then we can go over and see which one is worth triaging14:33
armaxand reviving if we have too14:33
ZZelledougwig, 6 months is really aggressive as it implies > 300 bugs in  https://bugs.launchpad.net/neutron/+expirable-bugs to triage in 60 days14:34
armaxihrachys: they won’t actually expire until the Janitor kicks in 60 days from now14:34
ihrachysok, as long as we don't blindly close eyes and forget them at all14:34
armaxihrachys: nope14:34
armaxdougwig: yeah we figured 1y was the best compromise14:34
ajook, that sounds good,14:34
armax1.5y not aggressive enough and .5y too aggressive14:35
ajoif the reporter is not willing to provide more information after 60 days... I guess it's not that important14:35
ZZelleif 120 bugs seem too large to handle in 60 days, then we can run the script twice14:35
*** jcoufal has quit IRC14:35
armaxZZelle: that should be fine14:35
dougwigby scrub, i meant, maybe we should take a look at recently expired bugs, lest we let things slip through the cracks.14:35
ajoZZelle, you don't need to fix them ,just move out from incomplete14:35
*** markvoelker has quit IRC14:36
armax#action ZZelle to mark incomplete the  bugs older than one  year14:36
ZZelleajo, i hope so :)14:36
ZZellearmax, ack14:36
*** pm90_ has joined #openstack-meeting14:36
armax#info they will show up here: https://bugs.launchpad.net/neutron/+expirable-bugs14:36
*** achanda has quit IRC14:37
armaxthen I and someone else will look into those to make sure we don’t miss anything ‘important'14:37
armaxthis actually brings me to the next point14:37
armaxbug deputy for the forthcoming week14:38
*** jschwarz__ has joined #openstack-meeting14:38
*** pm90___ has joined #openstack-meeting14:38
armaxI’ll be shadowing/helping where I can to ensure that we iron out the kinks of the new process14:38
*** markvoelker_ has quit IRC14:38
armaxany volunteer?14:38
ihrachysI can volunteer14:38
regXboiarmax: I raise my hand as well14:38
markmcclainhappy to take it too14:39
ajocan I go ahead and close from those bugs, what's actually incorrect?14:39
ajoor invalid?14:39
armaxajo: yes you can14:39
ihrachysarmax: too much volunteers. we need a lottery!14:39
armaxihrachys: went first14:39
mesteryrofl14:39
markmcclainI'm happy to wait until november :)14:39
ihrachyssigh14:39
armax:)14:39
ihrachys:)14:39
regXboiheck - you've got the next three weeks14:39
armaxthe first one who replies wins14:39
regXboijust hand it out one at a time14:39
armax:)14:39
ajoI will volunteer after (or even during, if that's useful) summit14:40
armaxLet’s have ihrachys be the deputy for the week of Oct 514:40
kevinbentonCan you unassign the bugs that haven't had activity for a week?14:40
regXboiarmax: actually, I really thing you *should* schedule it out a bit further14:40
ajoihrachys++14:40
kevinbentonWith no patch proposed14:40
armaxbut anyone else should be free to help and take stuff off his plate14:40
ihrachysarmax: we select every week?14:40
emaganashould we just add our names to the neutron meetings wiki?14:40
armaxif they feel like he’s slipping ;)14:40
armaxihrachys: either every week or every other week14:40
regXboiit might help folks to know a little in advance what week they are "in the slot"14:40
emagana#link https://wiki.openstack.org/wiki/Network/Meetings14:40
armaxihrachys: depending on how you’re doing14:40
ihrachysack14:41
*** cdub has joined #openstack-meeting14:41
* ihrachys is voted to be the guinea pig14:41
*** pm90__ has quit IRC14:41
*** jschwarz_ has quit IRC14:41
ajoarmax, ZZelle , marking as Invalid is enough, or should touch anything else?14:41
armaxihrachys: you feel like you have bandwidth this week?14:41
njohnstonarmax: If you schedule it out further than anyone who is driven by a sprint schedule can make sure that they have time allocated for bugmaster duty in their sprint.14:41
dougwigwe need some token of office, like a sceptre.  a wand with a rubber cockroach on the end.14:41
ihrachysarmax: yes, I will do bug scrubbing for OSP anyway14:41
*** vgridnev has quit IRC14:41
armaxihrachys: ok great14:41
johnsom__Nice14:41
markmcclaindougwig: I think you have shopping to do between now and tokyo14:41
armaxI’ll add you to the bug deputy table for the week14:41
regXboiarmax: see njohnston's comment - he makes a good point14:42
*** pm90_ has quit IRC14:42
armax#info ihrachys the bug deputy for Oct 5th, supported by regXboi, markmcclain  if necessary14:42
*** vgridnev has joined #openstack-meeting14:42
* regXboi acks the #info14:42
*** cloudtrainme has joined #openstack-meeting14:42
amullerihrachys: I can help as well14:42
ihrachysfolks, thanks and I will reach if needed14:43
armaxnjohnston: yes, assumed that their sprint schedule overlaps with ours?14:43
*** MarkAtwood has joined #openstack-meeting14:43
armaxweek by week seems the best horizon for things upstream, but we can definitely plan a little further ahead14:43
armaxso for instance, if regXboi wants to take next week14:44
*** killer_prince has joined #openstack-meeting14:44
armaxregXboi: do you want to?14:44
armaxwe can revise your commitment next week14:44
regXboiarmax: I can take the next slot14:44
armaxnjohnston: is that what you were suggesting?14:44
armax#info regXboi to provisionally take the bug deputy role for week of Oct 12th14:44
*** edtubill has joined #openstack-meeting14:45
armaxok, let’s move next14:45
ihrachys10 mins to choose a volunteers. sick.14:45
*** Sukhdev has quit IRC14:45
mesterylol14:45
*** lazy_prince has quit IRC14:45
*** MarkAtwood has quit IRC14:45
armaxihrachys: too many volunteers! you gotta love it14:45
*** nmagnezi has quit IRC14:46
armax#topic docs14:46
*** openstack changes topic to "docs (Meeting topic: networking)"14:46
*** trozet has joined #openstack-meeting14:46
armaxemagana: any update?14:46
*** mrmartin has joined #openstack-meeting14:46
emaganaarmax: short one14:46
emaganaOn the networking guide we will be stopping having the old hangout meetings and moving into IRC14:46
mesteryemagana: yay! Good call!14:47
*** ajo_ has joined #openstack-meeting14:47
*** xyang1 has joined #openstack-meeting14:47
emaganaNick Chase was helping on leading the logistics but he will take a break and I will be leading the meeting.. I will send the details on ML because I dont have them yet!14:47
emagana:-)14:47
annegentlethank you emagana!14:48
emaganaSo, folks please join and contribute to the networking guide!14:48
*** vijendar has quit IRC14:48
armaxthanks emagana14:48
*** vijendar has joined #openstack-meeting14:48
armaxanything else on docs?14:49
emaganaarmax: passing the ball to you!14:49
ihrachysemagana: do we have our docs process documented in devref? that could be a good start for more participants.14:49
armaxbear in mind that whenever DocImpact is flagged on a commit message14:49
armaxa new bug is filed for the openstack manuals14:49
*** asselin_ has joined #openstack-meeting14:49
*** ajo has quit IRC14:49
armaxplease remember to provide as much info14:50
armaxto help the doc bug submitter with his/her job14:50
*** maishsk_ has joined #openstack-meeting14:50
armax#topic Open Discussion14:50
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"14:50
*** ajo has joined #openstack-meeting14:50
*** pnavarro is now known as pnavarro|afk14:50
armaxas some of you may know...14:50
armax#https://etherpad.openstack.org/p/neutron-mitaka-designsummit14:50
*** geoffarnold has quit IRC14:50
armaxthe summit is fast approaching14:50
*** maishsk has quit IRC14:51
*** maishsk_ is now known as maishsk14:51
yaminiwe wanted to discuss https://blueprints.launchpad.net/neutron/+spec/cms-to-test-environment14:51
ajo#link https://bugs.launchpad.net/neutron/+bug/148542214:51
openstackLaunchpad bug 1485422 in neutron "neutron-ovs-cleanup sometimes failed at reboot (Ubuntu 14.04)" [Undecided,Invalid]14:51
*** geoffarnold has joined #openstack-meeting14:51
armaxI have been working with the drivers team to put together a provisional schedule for the neutorn sessions14:51
ajo#undo14:51
ajosorry :(14:51
ajowas trying to link it right, my copy & paste does *not* work :(14:51
ajo#link https://etherpad.openstack.org/p/neutron-mitaka-designsummit14:51
* regXboi thinks only chair can #undo?14:51
armax#undo14:52
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x98e91d0>14:52
regXboione more armax14:52
ajoundo twice, sorry14:52
armax#undo14:52
dougwigregXboi is correct.14:52
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x99b8150>14:52
armaxwe good?14:52
ajo#link https://etherpad.openstack.org/p/neutron-mitaka-designsummit14:52
ajonow yes :)14:52
regXboinow we are good14:52
*** ajo_ has quit IRC14:52
armaxexpect an email soon14:52
*** electrocucaracha has joined #openstack-meeting14:52
armaxabout what the schedule is going to be about and how we are breaking down the various sessions14:53
*** xyang1 has quit IRC14:53
armaxwe’ll have a lightining talk session too14:53
armaxand don’t forget that Friday is full day for community get together14:53
armaxso if you haven’t booked your flights yet14:53
ihrachyswill kevinbenton produce another talk about bad commits?14:53
armaxconsider staying late14:53
ihrachysor maybe BAD REVIEWS!14:53
armaxihrachys: no, we have the effective guide now ;)14:54
ihrachysarmax: no fun14:54
dougwigi think ihrachys is implying that it's time to roast the reviewers.14:54
*** haomaiwang has quit IRC14:54
armaxkevinbenton: unless he wants to, but he doesn’t want to chair any session14:54
ihrachysdougwig: it's always that time14:54
armaxanyhoo14:54
dougwigihrachys: -1, sentence missing period.14:54
*** haomaiwang has joined #openstack-meeting14:55
kevinbenton-1 this sentence shouldn't have a period14:55
* regXboi wonders who let the punctuation police into the meeting14:55
armaxyamini, ajo: please consider adding the topic on the on demanda agenda on14:55
armaxhttps://wiki.openstack.org/wiki/Network/Meetings14:55
* dougwig thinks subtle humor is lost at this hour of the morning.14:55
*** yamahata has joined #openstack-meeting14:55
xgermanMonday will be some FWaaS fun14:55
ajoarmax, which topic?14:55
*** markvoelker has joined #openstack-meeting14:55
ihrachyssigh. I think I have a flight back on Fri14:55
*** dan-t has left #openstack-meeting14:55
yaminiit it is14:55
yaminiit is already there14:56
armaxis it?14:56
armaxI must have wiped it out14:56
* regXboi doesn't see it14:56
*** yamahata has quit IRC14:56
armaxblueprints are best discussed in gerring under neutron-specs14:56
armaxbtw14:56
sc68calor the ML14:56
armaxsc68cal: +114:57
*** hemnafk is now known as hemna14:57
armaxbut yeah, we gotta figure out a way to leave more time for the open discussion section otherwise14:57
regXboiare we done?14:57
amotokiyamini: we are using RFE bugs rather than filing blueprint http://docs.openstack.org/developer/neutron/policies/blueprints.html    i suggest you file a RFE bug so that we can be aware of it.14:57
armaxhaving it is kinda missing the point14:57
*** achanda has joined #openstack-meeting14:57
*** maishsk has quit IRC14:58
*** mrmartin has quit IRC14:58
*** Murali has quit IRC14:58
armaxregXboi: I think we are nearly done, unless you can wrap up in 2 mins14:58
hoangcxamotoki: +114:58
regXboiarmax: no - I can wait until next week14:58
armaxok folks14:59
* regXboi has call to join now anyway :(14:59
*** amuller has left #openstack-meeting14:59
armaxwe’re getting 1 min back14:59
armaxthanks for joining14:59
armax#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
emaganaciao pescau!14:59
openstackMeeting ended Tue Oct  6 14:59:31 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
sc68calcya14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-10-06-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-10-06-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2015/networking.2015-10-06-14.00.log.html14:59
ajothanks! o/14:59
regXboialoha14:59
hichiharabye14:59
amotokibye14:59
pc_mbye14:59
hoangcxbye14:59
akamyshnikova_bye14:59
dougwigyou robbed us of one minute!14:59
*** pc_m has left #openstack-meeting14:59
*** regXboi has left #openstack-meeting14:59
jlibosvabye14:59
kevinbentonBye14:59
*** electrocucaracha has quit IRC14:59
*** jlibosva has left #openstack-meeting14:59
markmcclainbye15:00
john-davidgebye15:00
*** johnsom__ has left #openstack-meeting15:00
yamamotobye15:00
*** srikanth-p_ has quit IRC15:00
vikram_bye15:00
mesterybye15:00
*** haomaiwang has quit IRC15:01
*** tmorin has joined #openstack-meeting15:01
*** derekh has quit IRC15:01
*** lazy_prince has joined #openstack-meeting15:01
*** achanda has quit IRC15:01
*** haomaiwang has joined #openstack-meeting15:01
kevinbentonarmax: drivers meeting?15:01
* carl_baldwin here15:02
*** john-davidge has left #openstack-meeting15:03
*** korzen has quit IRC15:03
armaxnot even a biobreak?15:04
*** killer_prince has quit IRC15:04
armax#startmeeting neutron-drivers15:04
openstackMeeting started Tue Oct  6 15:04:09 2015 UTC and is due to finish in 60 minutes.  The chair is armax. Information about MeetBot at http://wiki.debian.org/MeetBot.15:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:04
*** openstack changes topic to " (Meeting topic: neutron-drivers)"15:04
openstackThe meeting name has been set to 'neutron_drivers'15:04
kevinbenton#startvote what's for lunch15:04
openstackOnly the meeting chair may start a vote.15:04
* mestery waves15:04
dougwigO/15:05
amotokihi15:05
kevinbentondougwig, armax: it can be short15:05
*** penick has joined #openstack-meeting15:05
kevinbentoni think we just had more rfe's from last week to look at15:05
kevinbentonbut we can defer if everyone is wiped out from that intense neutron meeting...15:05
armaxsounds good15:05
armaxkevinbenton: what intense neutron meeting?15:06
kevinbentonthe one right before this one15:06
*** hichihara has quit IRC15:06
*** david-ly_ is now known as david-lyle15:06
armax#link v15:06
armax#undo15:06
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x98141d0>15:06
armax#link https://bugs.launchpad.net/neutron/+bugs?field.tag=rfe15:06
*** aorourke_ is now known as aorourke15:06
* carl_baldwin was just going ask what url shortener armax uses15:07
armaxis anyone of you guys thinking that this rfe process is working?15:07
*** hoangcx has quit IRC15:07
armaxI can see that’s easier for some people to submit ideas15:07
armaxso that’s a positive15:07
armaxeffect15:07
amotokiIt is a bit difficult to track the status of each bugs. someone proposes a patch before we discuss it.15:08
carl_baldwinIt helped for the routed networks request from operators.15:08
HenryGI think it's a little hard to track sometimes when multiple patches apply15:08
*** lpeer has quit IRC15:08
dougwigi'm on record as preferring -specs, simply because the tooling is more queue oriented. i think the non-dev community prefers the rfe's.15:08
carl_baldwinThere are deficiencies around the tooling.  Launchpad isn’t quite geared for it.15:09
kevinbentonmaybe we should just not allow patches to directly reference an RFE?15:09
amotokiit lowers the hurdle to request features. it is a good point of RFE.15:09
amotokikevinbenton: +115:09
kevinbentonright, we need a way to allow features requests to be submitted but block the normal bug processes...15:10
carl_baldwinkevinbenton: I don’t have an opinion either way.  Just wondering what that solves and what the alternative is.15:10
HenryG"Promote" an RFE to a blueprint when it is accepted?15:10
kevinbentonor maybe just have RFEs be filed as blueprints to begin with?15:10
armaxI think the process has some benefits15:11
*** geoffarnold has quit IRC15:11
*** ganeshna has joined #openstack-meeting15:11
armaxbut I would like to split the phases where we are asked to provide feedback15:11
armaxand the phase where the actual work happens15:11
armaxI don’t want RFE bugs linger for ever15:12
*** geoffarnold has joined #openstack-meeting15:12
armaxso maybe once the drivers team ‘approves’/gives a thumb up we change the tag?15:13
armaxfrom rfe to rfe-approved?15:13
*** pennerc has joined #openstack-meeting15:13
armaxand move on?15:13
armaxso that this list shrinks https://bugs.launchpad.net/neutron/+bugs?field.tag=rfe15:13
armaxif we are doing a good job at vetting stuff?15:13
carl_baldwin+1 to a shrinking list.15:13
*** lpeer has joined #openstack-meeting15:13
armaxif people don’t pull their weight together15:13
armaxthere’s nothing we can do15:13
kevinbentonyeah, tag change sounds nice15:14
armaxand I don’t want to look to have bugs I have already seen littering my dashboard15:14
kevinbentonthat way people messing with the status don't interfere15:14
armaxso if you guys think it’s a good idea15:14
HenryG+1 to tag change, good idea15:14
amotoki+1 for changing tags15:14
armaxand since I am gonna have to make another policy change :)15:14
carl_baldwin+115:15
armaxmestery: ^15:15
armaxand go over the bug list to tag those that we have already ‘blessed'15:15
armaxso that we keep our sanity over time15:15
kevinbenton+!15:16
dougwigi like it, the status kludge is messy.15:16
armaxhopefully this has no impact to users filing these RFE's15:17
armaxso it’s not like we’re going backwards15:17
kevinbentondougwig: the fact that you had to invent a decoder ring probably should have been a red flag :)15:17
* mestery catches up15:17
armaxwe’re making a positive iterative improvement15:17
mesteryarmax: I like that idea15:17
armaxok, I’ll do that right after this meeting15:18
armaxput a patch up for you to review15:18
mesteryarmax: Good idea, it's a cleaner method, as dougwig said, the status kludge was messy15:18
*** changbl has joined #openstack-meeting15:18
*** ZZelle has left #openstack-meeting15:18
armaxso do we want to call it ‘a day’ and wait for a cleaned list of bugs to talk about?15:18
armaxhint hint15:18
*** shashank_hegde has joined #openstack-meeting15:18
* carl_baldwin okay with that15:18
armaxunless there’s something pressing I think we should discuss15:19
HenryGI would like to know about my rfe ...15:19
armaxwhat about it?15:19
kevinbentonHenryG: which one?15:19
amotokione question: how do we handle RFE for neutron subprojects? when it was submitted it was a reasonable RFE but now we have a separate project.15:19
HenryGhttps://bugs.launchpad.net/neutron/+bug/150138015:19
openstackLaunchpad bug 1501380 in neutron "Evolution of options and features in neutron-db-manage" [Medium,Confirmed]15:19
amotokiHenryG: go ahead first15:19
HenryGIs that the wrong way to abuse an rfe?15:20
armaxamotoki: if the RFE affects the Neutron sides of thing then we should keep it tracked in Neutron15:20
HenryGShould I file individual bugs?15:20
armaxHenryG: probably15:20
armaxamotoki: otherwise no15:20
amotokiarmax: one example is https://bugs.launchpad.net/neutron/+bug/145061715:20
openstackLaunchpad bug 1450617 in neutron "Neutron extension to support service chaining" [Undecided,Triaged] - Assigned to cathy Hong Zhang (cathy-h-zhang)15:20
armaxHenryG: it sounds to me that what you want to do is sensible no matter what15:21
armaxHenryG: so you shouldn’t seek the oversight of the drivers team15:21
armaxbut the core team would do15:21
armaxamotoki: me looks15:21
HenryGarmax: OK, will do separate bugs instead. Thanks15:21
armaxamotoki: ok, I’ll clean that one up15:21
armaxamotoki: that was clearly filed when the subproject didn’t even exist15:22
armaxthat’s stuff that’s lingering and needs to be cleaned15:22
armaxanything else?15:22
vikram_amotoki: +115:22
mesterynothing from me15:22
amotokiarmax: yes. I wonder how we handle it: which status is best: Invalid, Won't fix????15:22
*** sdake_ is now known as sdake15:23
*** madorn has left #openstack-meeting15:23
*** pm90___ has quit IRC15:23
armaxamotoki: we can target the networking-sfct launchpad project15:23
armaxand remove it from neutron15:23
amotokiah.... good idea!15:23
amotokiI totally forgot this option.15:23
armaxyup15:24
dougwigmotion to adjourn?15:24
armaxadjuourn15:24
mestery++15:24
amotoki++15:24
*** yamini_ has quit IRC15:24
armax#action I’ll polish the RFE bugs up too15:24
armaxbear with me15:25
*** jdurgin1 has joined #openstack-meeting15:25
armax#endmeeting15:25
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:25
openstackMeeting ended Tue Oct  6 15:25:21 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-10-06-15.04.html15:25
armaxthanks for joining15:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-10-06-15.04.txt15:25
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-10-06-15.04.log.html15:25
*** yamini has quit IRC15:25
armaxI don’t even get a goobye?15:26
armaxbah15:26
amotokibye15:26
-amotoki- was caught in i18n channel15:26
armax:)15:26
*** dims_ has quit IRC15:27
kevinbentonarmax: arrivederci15:27
armaxciao15:27
*** sudipto has joined #openstack-meeting15:27
*** rkukura has quit IRC15:27
*** galstrom_zzz is now known as galstrom15:28
*** hashar has quit IRC15:29
*** Daviey_ has quit IRC15:30
*** Daviey has joined #openstack-meeting15:30
*** pennerc has left #openstack-meeting15:30
*** Kanchan has quit IRC15:30
*** alexschm has quit IRC15:30
*** apoorvad has joined #openstack-meeting15:31
*** ItSANgo has quit IRC15:31
*** apoorvad has quit IRC15:32
*** kebray has joined #openstack-meeting15:32
*** ItSANgo has joined #openstack-meeting15:32
*** apoorvad has joined #openstack-meeting15:32
*** dims_ has joined #openstack-meeting15:32
*** sridhar_ram has joined #openstack-meeting15:32
*** carl_baldwin has quit IRC15:33
*** geoffarnold has quit IRC15:33
*** evgenyf has quit IRC15:33
*** geoffarnold has joined #openstack-meeting15:34
*** scheuran has quit IRC15:34
*** sudipto has quit IRC15:34
*** pm90_ has joined #openstack-meeting15:35
*** sudipto has joined #openstack-meeting15:35
*** davidlenwell has quit IRC15:36
*** vgridnev has quit IRC15:36
*** apoorvad has quit IRC15:37
*** davidlenwell has joined #openstack-meeting15:37
*** krtaylor has quit IRC15:38
*** scheuran has joined #openstack-meeting15:39
*** SridharG has left #openstack-meeting15:40
*** sudipto_ has joined #openstack-meeting15:43
*** penick has quit IRC15:43
*** sudipto has quit IRC15:44
*** Swami has joined #openstack-meeting15:44
*** geoffarnold is now known as geoffarnoldX15:45
*** sudipto__ has joined #openstack-meeting15:47
*** ihrachys_ has joined #openstack-meeting15:48
*** lsmola_ has joined #openstack-meeting15:48
*** vivek-ebay has joined #openstack-meeting15:48
*** jhenner1 has joined #openstack-meeting15:49
*** jtomasek has quit IRC15:49
*** ihrachys has quit IRC15:49
*** sudipto_ has quit IRC15:49
*** ihrachys has joined #openstack-meeting15:50
*** jtomasek has joined #openstack-meeting15:50
*** krtaylor has joined #openstack-meeting15:51
*** jhenner has quit IRC15:51
*** pennerc has joined #openstack-meeting15:52
*** lsmola has quit IRC15:52
*** ihrachys_ has quit IRC15:53
*** lsmola_ has quit IRC15:53
*** jhenner1 has quit IRC15:53
*** pennerc has quit IRC15:54
*** scheuran has quit IRC15:54
*** geoffarnoldX has quit IRC15:54
*** nadya has quit IRC15:55
*** geoffarnold has joined #openstack-meeting15:55
*** lazy_prince has quit IRC15:55
*** topol has quit IRC15:56
*** haomaiwang has quit IRC15:56
*** unicell has joined #openstack-meeting15:58
*** mtanino has joined #openstack-meeting15:59
*** unicell1 has quit IRC15:59
*** muawiakhan has quit IRC15:59
*** spzala has quit IRC15:59
*** devvesa has quit IRC16:00
*** garthb has joined #openstack-meeting16:00
*** sudipto_ has joined #openstack-meeting16:00
*** pballand has joined #openstack-meeting16:01
*** KunalGandhi has joined #openstack-meeting16:01
*** sudipto__ has quit IRC16:02
*** vilobhmm11 has joined #openstack-meeting16:02
*** vjay12 has joined #openstack-meeting16:02
*** penick has joined #openstack-meeting16:03
*** ijw has joined #openstack-meeting16:04
*** lsmola_ has joined #openstack-meeting16:06
*** jhenner has joined #openstack-meeting16:06
*** lpeer has quit IRC16:06
*** jlanoux has quit IRC16:06
*** lazy_prince has joined #openstack-meeting16:06
*** shashank_hegde has quit IRC16:06
*** aloga_ has quit IRC16:07
*** e0ne has quit IRC16:08
*** topol has joined #openstack-meeting16:08
*** tidwellr has left #openstack-meeting16:08
*** matrohon has quit IRC16:09
*** akamyshnikova_ has quit IRC16:10
*** brad_behle has quit IRC16:10
*** mgrohar has quit IRC16:10
*** gyee has joined #openstack-meeting16:12
*** leeantho has joined #openstack-meeting16:12
*** electrocucaracha has joined #openstack-meeting16:13
*** ganeshna has quit IRC16:15
*** geoffarnold has quit IRC16:16
*** geoffarnold has joined #openstack-meeting16:16
*** mbound has quit IRC16:16
*** thangp_ has joined #openstack-meeting16:16
*** topol has quit IRC16:17
*** Guest94490 is now known as mfisch16:17
*** mfisch is now known as Guest6262516:18
*** thangp has quit IRC16:18
*** tmorin has quit IRC16:19
*** mrmartin has joined #openstack-meeting16:19
*** amotoki has quit IRC16:20
*** penick has quit IRC16:22
*** gongysh has quit IRC16:22
*** vivek-ebay has quit IRC16:23
*** mrmartin has quit IRC16:23
*** KunalGandhi has quit IRC16:24
*** vjay12 has quit IRC16:25
*** doron_afk has quit IRC16:27
*** ildikov has quit IRC16:27
*** sudipto__ has joined #openstack-meeting16:27
*** lpeer has joined #openstack-meeting16:28
*** tsekiyama has joined #openstack-meeting16:29
*** banix has quit IRC16:30
*** mudassirlatif has joined #openstack-meeting16:30
*** sudipto_ has quit IRC16:30
*** maishsk has joined #openstack-meeting16:31
*** vikram_ has quit IRC16:31
*** electrocucaracha has quit IRC16:32
*** ijw has quit IRC16:32
*** pm90_ has quit IRC16:33
*** apoorvad has joined #openstack-meeting16:35
*** unicell has quit IRC16:35
*** n0ano has quit IRC16:35
*** Daisy has quit IRC16:36
*** Daisy has joined #openstack-meeting16:36
*** rbowen has joined #openstack-meeting16:37
*** geoffarnold has quit IRC16:37
*** nadya has joined #openstack-meeting16:37
*** dims_ has quit IRC16:37
*** geoffarnold has joined #openstack-meeting16:38
*** vgridnev has joined #openstack-meeting16:38
*** flashgordon is now known as jogo16:38
*** ijw has joined #openstack-meeting16:39
*** jtomasek has quit IRC16:39
*** balajiiyer has quit IRC16:40
*** maishsk_ has joined #openstack-meeting16:40
*** Daisy has quit IRC16:41
*** maishsk has quit IRC16:41
*** maishsk_ is now known as maishsk16:41
*** dims_ has joined #openstack-meeting16:41
*** dims_ has quit IRC16:41
*** dims_ has joined #openstack-meeting16:42
*** claudiub has quit IRC16:42
*** jaypipes has joined #openstack-meeting16:43
*** dims__ has joined #openstack-meeting16:44
*** dims_ has quit IRC16:45
*** rkukura has joined #openstack-meeting16:46
*** ygbo has quit IRC16:46
*** rkukura has left #openstack-meeting16:48
*** jhenner has quit IRC16:49
mhickeydevref16:50
*** carl_baldwin has joined #openstack-meeting16:51
*** gangil has joined #openstack-meeting16:51
*** mwagner_ has quit IRC16:53
*** vilobhmm111 has joined #openstack-meeting16:54
*** Sukhdev has joined #openstack-meeting16:54
*** jwcroppe_ has joined #openstack-meeting16:55
*** vjay12 has joined #openstack-meeting16:55
*** rbowen has quit IRC16:55
*** jwcroppe has quit IRC16:56
*** armax has quit IRC16:56
*** shashank_hegde has joined #openstack-meeting16:57
*** vilobhmm11 has quit IRC16:57
*** lpeer has quit IRC16:58
*** geoffarnold has quit IRC16:58
*** lpeer has joined #openstack-meeting16:58
*** geoffarnold has joined #openstack-meeting16:59
*** elynn_ has quit IRC17:03
*** jprovazn has quit IRC17:03
*** yamamoto has quit IRC17:03
*** cloudtrainme has quit IRC17:03
*** balajiiyer has joined #openstack-meeting17:03
*** earlephilhower has joined #openstack-meeting17:03
*** enikanorov has quit IRC17:03
*** sdake has quit IRC17:03
*** AntonKhaldin has joined #openstack-meeting17:04
*** cloudtrainme has joined #openstack-meeting17:04
*** sdake has joined #openstack-meeting17:05
*** gyee has quit IRC17:05
*** nmagnezi has joined #openstack-meeting17:05
*** sudipto__ has quit IRC17:05
*** sudipto__ has joined #openstack-meeting17:06
*** matrohon has joined #openstack-meeting17:07
*** AntonKhaldin has quit IRC17:07
*** anton_khaldin has joined #openstack-meeting17:08
*** toscalix has quit IRC17:10
*** s3wong has joined #openstack-meeting17:10
*** anton_haldin has joined #openstack-meeting17:11
*** unicell has joined #openstack-meeting17:12
*** banix has joined #openstack-meeting17:12
*** ccarmack has left #openstack-meeting17:14
*** ijw has quit IRC17:16
*** e0ne has joined #openstack-meeting17:16
*** akuznetsova has quit IRC17:16
*** Daisy has joined #openstack-meeting17:16
*** geoffarn_ has joined #openstack-meeting17:20
*** david-ly_ has joined #openstack-meeting17:21
*** david-lyle has quit IRC17:21
*** bobh has quit IRC17:22
*** david-ly_ is now known as david-lyle17:22
*** bobh has joined #openstack-meeting17:22
*** akuznetsova has joined #openstack-meeting17:23
*** lazy_prince has quit IRC17:23
*** sridhar_ram has quit IRC17:23
*** claudiub has joined #openstack-meeting17:24
*** IlyaG has joined #openstack-meeting17:24
*** geoffarnold has quit IRC17:24
*** pballand has quit IRC17:24
*** achanda has joined #openstack-meeting17:24
*** harlowja has quit IRC17:25
*** dandruta has joined #openstack-meeting17:25
*** raildo is now known as raildo-afk17:26
*** topol has joined #openstack-meeting17:28
*** kebray has quit IRC17:28
*** bobh has quit IRC17:29
*** ijw has joined #openstack-meeting17:29
*** sudipto_ has joined #openstack-meeting17:29
*** dims_ has joined #openstack-meeting17:29
*** stanchan has joined #openstack-meeting17:29
*** electrocucaracha has joined #openstack-meeting17:29
*** sudipto__ has quit IRC17:31
*** dims__ has quit IRC17:32
*** ijw has quit IRC17:33
*** pvaneck has joined #openstack-meeting17:34
*** IanGovett has quit IRC17:35
*** harlowja has joined #openstack-meeting17:35
*** cdub has quit IRC17:37
*** cody-somerville has quit IRC17:37
*** pm90_ has joined #openstack-meeting17:38
*** yassine has quit IRC17:39
*** IanGovett has joined #openstack-meeting17:39
*** pm90__ has joined #openstack-meeting17:40
*** su_zhang has joined #openstack-meeting17:40
*** vilobhmm111 has left #openstack-meeting17:41
*** geoffarn_ has quit IRC17:41
*** kgroves has joined #openstack-meeting17:41
*** geoffarnold has joined #openstack-meeting17:41
*** armax has joined #openstack-meeting17:42
*** vijendar has left #openstack-meeting17:42
*** fawadkhaliq has quit IRC17:42
*** fawadkhaliq has joined #openstack-meeting17:43
*** raildo-afk is now known as raildo17:43
*** lpeer has quit IRC17:43
*** cbouch has quit IRC17:43
*** pm90_ has quit IRC17:43
*** lpeer has joined #openstack-meeting17:43
*** maishsk_ has joined #openstack-meeting17:46
*** kgroves has quit IRC17:46
*** maishsk has quit IRC17:46
*** maishsk_ is now known as maishsk17:46
*** nadya has quit IRC17:47
*** penick has joined #openstack-meeting17:47
*** baoli_ has quit IRC17:47
*** erlon has joined #openstack-meeting17:47
*** bobh has joined #openstack-meeting17:48
*** kgroves has joined #openstack-meeting17:48
*** vjay12 has quit IRC17:49
*** glauc____ has joined #openstack-meeting17:50
*** bobh_ has joined #openstack-meeting17:50
*** kebray has joined #openstack-meeting17:51
*** KunalGandhi has joined #openstack-meeting17:51
*** KunalGandhi has quit IRC17:51
*** KunalGandhi has joined #openstack-meeting17:51
*** pnavarro|afk has quit IRC17:52
*** maishsk has quit IRC17:52
*** lhcheng_ has joined #openstack-meeting17:52
*** dims_ has quit IRC17:53
*** glauco_ has quit IRC17:53
*** jschwarz__ has quit IRC17:53
*** bobh has quit IRC17:53
*** IlyaG has quit IRC17:56
*** vishwanathj has quit IRC17:56
*** IlyaG has joined #openstack-meeting17:57
*** IlyaG has quit IRC17:57
*** IlyaG has joined #openstack-meeting17:57
*** su_zhang_ has joined #openstack-meeting17:58
*** browne has joined #openstack-meeting17:59
*** breton has joined #openstack-meeting17:59
bretono/17:59
stevemar_o/17:59
* ayoung here18:00
dstanekhi18:00
marekdhi18:00
stevemar_heyooo18:00
stevemar_lets do this!18:00
stevemar_#startmeeting keystone18:00
openstackMeeting started Tue Oct  6 18:00:35 2015 UTC and is due to finish in 60 minutes.  The chair is stevemar_. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** cloudtrainme has quit IRC18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
ayoungRobot Rollcall!18:00
stevemar_#link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:00
openstackThe meeting name has been set to 'keystone'18:00
stevemar_oops18:00
stevemar_courtesy ping18:00
stevemar_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, claudiub18:00
*** david8hu has joined #openstack-meeting18:01
amakarovo/18:01
browneo/18:01
stevemar_o\18:01
* bknudson does something18:01
david8hu\o18:01
topolo/18:01
dstaneko/18:01
* stevemar_ high five's bknudson18:01
htrutao/18:01
* ayoung now has the MST3K themesong playing through his head18:01
*** henrynash has joined #openstack-meeting18:01
raildo\o18:01
henrynash:-)18:01
lhcheng_o/18:01
ayounghenrynash, !18:01
stevemar_i'd say we have enough folks18:01
*** dims_ has joined #openstack-meeting18:01
stevemar_henrynash: ayoung has been looking for you18:01
ayounghenrynash, I threw an item on the end of the agenda...18:02
henrynash(runs, hides)18:02
ayoungVirtual Roles18:02
*** su_zhang has quit IRC18:02
stevemar_alright, good new to start18:02
henrynashah-ah!18:02
topolrun Forest run18:02
stevemar_#topic RC status18:02
*** openstack changes topic to "RC status (Meeting topic: keystone)"18:02
stevemar_we've cut rc2!18:02
stevemar_yayyyyy18:02
*** geoffarnold has quit IRC18:02
henrynashhay!18:02
topolCONGRATS18:02
marekdnice18:02
lbragstado/18:02
ayoungAny significant changes from RC1?18:02
stevemar_unless there is an install / upgrade / crazy issue, this will be the last release for liberty18:03
*** geoffarnold has joined #openstack-meeting18:03
stevemar_ayoung: 3 bugs, and translation: https://launchpad.net/keystone/+milestone/liberty-rc218:03
bknudson#link http://git.openstack.org/cgit/openstack/keystone/log/?h=stable%2Fliberty18:03
*** olaph has joined #openstack-meeting18:03
*** yamamoto has joined #openstack-meeting18:03
*** vivek-ebay has joined #openstack-meeting18:03
*** vivek-ebay has quit IRC18:03
ayoungall good stuff18:03
*** spzala has joined #openstack-meeting18:03
*** olaph has left #openstack-meeting18:03
*** KunalGandhi has quit IRC18:04
stevemar_around the same topic, we have also release ksc 1.7.2 and ksm 2.3.1 for liberty18:04
*** vivek-ebay has joined #openstack-meeting18:04
bknudsonI only see 2 bug fixes in the git log18:04
*** timcline has joined #openstack-meeting18:04
lbragstadthis is everything that merged in stable/liberty so far - https://review.openstack.org/#/q/status:merged+project:openstack/keystone+branch:stable/liberty,n,z18:04
ayoung1) Skip rows with empty remote_ids 2) Show v3 endpoints in v2 endpoint list  3) Ensure token validation works irrespective of padding18:04
*** cloudtrainme has joined #openstack-meeting18:05
stevemar_bknudson: 1) skip rows, 2) padding, 3) v3 endpoints18:05
ayoungare those not all bugs?18:05
bknudsonoh, the top one is in there18:05
*** samleon_ has joined #openstack-meeting18:05
*** ijw has joined #openstack-meeting18:05
* stevemar_ shakes fist at bknudson18:05
bknudsonso they're all there18:05
*** kebray has quit IRC18:05
stevemar_thanks ayoung :)18:05
*** vgridnev has quit IRC18:05
ayoungstevemar_, that scares me.  It is the first time i ever saw bknudson overlook a detail18:05
*** dims_ has quit IRC18:05
stevemar_regarding libs: so when we eventually release new stuff for mitaka, they'll be at 1.8.0 and 2.4.0 respectively18:05
topolhe's slippin'18:06
stevemar_he's human after all18:06
marekdstevemar_: who?18:06
marekd!18:06
ayoungNot sure about that18:06
*** dims_ has joined #openstack-meeting18:06
stevemar_marekd: bknudsonbot18:06
marekdstevemar_: no way!18:06
*** rossella_s has quit IRC18:06
stevemar_gonna skip the 2nd topic for now (summit planning)18:06
ayoungwhat is the version number for ksa?18:06
ayoungnevermind18:07
stevemar_ayoung: 1.0ish18:07
*** vgridnev has joined #openstack-meeting18:07
ayoung++18:07
*** timcline has quit IRC18:07
*** rossella_s has joined #openstack-meeting18:07
stevemar_ayoung: it was cut, but not too many things are using it18:07
*** timcline has joined #openstack-meeting18:07
ayoungI saw the summit room breakdown email.  Let me see if I can link it18:07
dolphmis that why releases haven't appeared on pypi?18:07
stevemar_dolphm: of keystoneauth?18:08
dolphmstevemar_: yes18:08
bknudson#link https://pypi.python.org/pypi/keystoneauth18:08
bknudsonsays 0.2.018:08
stevemar_that seems wrong18:08
*** yamamoto has quit IRC18:08
bknudsonhttps://pypi.python.org/pypi/keystoneauth118:08
bknudsonthat's got 1.1.018:08
*** maishsk has joined #openstack-meeting18:08
stevemar_ah right, it's keystoneauth118:08
bknudsonI thought we'd want keystoneauth on pypi18:09
ayounghttp://lists.openstack.org/pipermail/openstack-dev/2015-October/076000.html18:09
dolphmoh, f18:09
dolphmcan we delete the old package? or update the README to point to the new one?18:09
stevemar_dolphm: i can look into that18:09
lbragstaddelete keystoneauth and point everyone to keystoneauth118:09
lbragstadright?18:09
stevemar_yes18:09
*** su_zhang_ has quit IRC18:09
topol+++18:09
dolphmif deleting things on pypi is acceptable, not sure it is18:09
bretonor raise an exception in keystoneauth18:09
*** su_zhang has joined #openstack-meeting18:10
bretonsaying "keystoneauth1"18:10
stevemar_there's a few things we can do, i'm sure there is a right answer though18:10
ayoung#link https://docs.google.com/spreadsheets/d/1tpLN5emWhcMmSmkn8z_HuclcjnEPevP77BhdnFN9KCs/pubhtml?gid=5&single=true  Here is our room breakdown18:10
*** ihrachys has quit IRC18:10
ayounghttps://mitakadesignsummit.sched.org/overview/type/Keystone#.VhQOp7P-TMU  and its on sched .org already18:10
stevemar_ayoung: hehe, hold up.18:11
stevemar_any other q's on liberty or the surrounding libraries?18:11
ayoungGive me liberty or give me RC318:11
stevemar_#topic ops feedback for summit18:12
*** openstack changes topic to "ops feedback for summit (Meeting topic: keystone)"18:12
bknudsonhopefully the ops will show up this time.18:12
ayoungDid we skip Design session planning?18:12
stevemar_ayoung: just for a minute18:12
ayoungk18:12
stevemar_ayoung: that is gonna be a long discussion, get the easy stuff in first18:12
stevemar_#link https://etherpad.openstack.org/p/TYO-ops-feedback-into-PWG18:12
stevemar_add questions to that etherpad ^18:12
*** sudipto_ has quit IRC18:13
ayoung#link https://mitakadesignsummit.sched.org/overview/type/Ops#.VhQPKLP-TMU18:13
stevemar_and if you're interested in going to the session: http://mitakadesignsummit.sched.org/event/1cdd373e1128b6c5f9536c00f461947a#.VhCyIhNVhBc18:13
*** claudiub has quit IRC18:13
stevemar_bknudson: i think it'll be more organized this time18:13
bretonyeah, last time it was 15 developers vs 2 ops18:13
stevemar_breton: yeah, i think they are doing a general session for all the ops to generate data on projects18:14
dolphmand for the record, the devs won18:14
stevemar_so it's important to put questions on the etherpad18:14
stevemar_dolphm: we always win18:14
bknudsonwe really put those operators in their place.18:14
dolphmi'd like to see ops win for a change18:14
lbragstadso, if you know people in ops that don't necessarily hangout on irc, poke them!18:14
*** jaypipes has quit IRC18:14
stevemar_lbragstad: ++18:14
lbragstador at least pass them the info18:15
stevemar_also for those interested, there is also this link going around:18:15
stevemar_#link https://etherpad.openstack.org/p/operator-local-patches18:15
stevemar_a set of local patches that ops carry per project18:15
stevemar_we're actually pretty good :)18:15
*** gyee has joined #openstack-meeting18:16
stevemar_anyway, try to be engaged in these sessions, they are crazy important18:16
*** peristeri has quit IRC18:16
bknudson"Strip catalog from PKI token"18:16
stevemar_bknudson: comment on the etherpad if you want18:17
dolphm?nocatalog#implemented18:17
stevemar_yep18:17
lbragstadit's the fernet?18:17
lbragstadisn't*18:17
dolphmit's always the fernet18:17
stevemar_teh fehrnet18:17
*** ajmiller has joined #openstack-meeting18:17
morganDelete PKI token format *shiftyeyes*18:17
dolphminterface="furnet"18:18
* lbragstad wanders off to learn to keyboard... 18:18
gyeey'all using PKI wrong18:18
morgandolphm: i am scared what a furnet is18:18
stevemar_alright alright :)18:18
stevemar_#topic release notes18:18
*** openstack changes topic to "release notes (Meeting topic: keystone)"18:18
stevemar_edit the wiki directly18:19
*** BharatK has quit IRC18:19
stevemar_#link https://wiki.openstack.org/wiki/ReleaseNotes/Liberty#OpenStack_Identity_.28Keystone.2918:19
stevemar_review and edit please18:19
stevemar_dolphm i know you did a lot for this already18:19
stevemar_and thanks :D18:19
stevemar_samueldmq: you too!18:19
dolphm++18:20
stevemar_apparently this is a buzz kill of a topic18:20
ayounglets not make any changes to PKI tokens;  lets just work on deprecating them18:20
*** electrocucaracha has quit IRC18:20
ayoungthere are too many problems to fix18:20
dolphm\o/ yay release notes18:20
stevemar_ayoung: ++18:20
dstanekayoung: ++18:20
stevemar_dolphm: thanks for trying :)18:20
stevemar_alright, on to the fun stuff!18:20
ayoungand the primary reason PKI tokens were even written is replaced by K2K and SAML.18:20
stevemar_ayoung: it's time18:20
ayoungSummit planning time?18:21
stevemar_#topic design sessions18:21
*** openstack changes topic to "design sessions (Meeting topic: keystone)"18:21
ayoungwhere is our etherpad?18:21
bknudson#link https://etherpad.openstack.org/p/keystone-mitaka-summit-brainstorm18:21
lbragstadwe had one here #Link https://etherpad.openstack.org/p/keystone-mitaka-summit-brainstorm18:21
ayoungthanks18:21
stevemar_ayoung: so far i have the brain dump ... fineeee bknudson and lbragstad18:21
*** amrith is now known as _amrith_18:22
ayoungCan we make one session that is KSA, KSM and KSC?18:22
ayounglets start thinking in buckets for these things.  we have 14 top level topics18:22
stevemar_so before we start penciling in stuff18:22
lbragstadso a session dedicated to non-server related keystone libraries18:22
marekdwho added bullet 14.3 ?18:22
*** _amrith_ is now known as amrith18:22
stevemar_we have 7 fishbowl sessions18:22
ayoungmarekd, I did18:23
stevemar_these are the ones that are group discussion18:23
samueldmqstevemar_: hello, sorry I am late18:23
samueldmqstevemar_: no problem :)18:23
stevemar_4 workroom sessions18:23
marekdayoung: ack18:23
stevemar_and 2 meetup sessions (same as last)18:23
stevemar_workrooms are the boardroom style ones18:23
lbragstadI feel like tokens and tokenless auth could be grouped18:23
stevemar_and fishbowls are the ones we've done for a while18:24
ayoungmarekd, probably we can mix that in with something else.  Consumption of notifications needs to be addressed in a few places...its really cross project type stuff18:24
morganAnd fishbowl rooms are much larger18:24
stevemar_samueldmq: np, and hello18:24
lbragstadboth goals for those two sessions are getting it to be the default in devstack18:24
ayounglbragstad, ++18:24
marekdayoung: yes18:24
stevemar_lbragstad: true18:24
morganFyi in tokyo expect the work rooms to be small18:24
*** cloudtrainme has quit IRC18:24
*** geoffarn_ has joined #openstack-meeting18:24
*** ajmiller has quit IRC18:24
*** harshs has joined #openstack-meeting18:24
morganVery small18:24
topolhow small?18:24
*** ayoung_ has joined #openstack-meeting18:24
*** ajmiller has joined #openstack-meeting18:24
bknudsonalso, you have to take your shoes off and sit on the floor.18:25
morganI think the target was ~8-10 people18:25
*** geoffarnold has quit IRC18:25
gyeereally?18:25
stevemar_topol: prison sized18:25
ayoung_gyee, really.  but just you18:25
gyeebknudson, you ain't kidding18:25
marekdbknudson: and put on another shoes when going to toilet (yes, really)18:25
bknudsonwe're probably going to have to wander off to another area to work18:25
ayoung_http://i.dailymail.co.uk/i/pix/2013/07/02/article-2353514-1A9F4E55000005DC-736_634x436.jpg18:25
gyeewow18:25
morganThe only reason any work rooms were requested was to have some general purpose time18:26
dolphmayoung_: are we staying at the same hotel??18:26
marekdbknudson: 12.1 - what's incorrect right now?18:26
morganOtherwise I would have requested only fishbowls18:26
morgan(Since I was the one who had to make the requests for room allocation)18:26
lbragstadcould we address topic 5 in 8 (keystone server)?18:26
ayoung_lbragstad, ++18:27
bknudsonmarekd: according to mtreinish the keystone functional tests should require checking something in the backend database.18:27
gyeelbragstad, yeah, if we are talking about server deprecations18:27
bknudsonnot just be a test that uses devstack.18:27
*** ivar-lazzaro has joined #openstack-meeting18:27
* breton doesn't see 5 in 8, sees only 318:28
*** kencjohnston has left #openstack-meeting18:28
stevemar_so, the workrooms, anyone have a suggestion about one of the things from the etherpad that can be dumped there?18:28
lbragstadgyee: ++ yeah, we'll have to cover deprecations for the ksm, ksc, ksa bits, too18:28
dstanekbknudson: what sort of checking?18:28
dolphmbknudson: that's super odd18:28
marekdbknudson: so affter adding entity i should write a code that queries backend and checks if that's there?18:28
*** lpeer has quit IRC18:28
*** lpeer has joined #openstack-meeting18:28
stevemar_i was thinking that testing could be a workroom session18:28
bknudsondstanek: in the case of nova, it's like checking something in libvirt I would guess. In keystone it might be something like checking that the entry was created in ldap18:29
dolphmi care about how the interface behaves, not what the interface does on the backend.18:29
gyeethen why do we need func tests?18:29
bknudsondolphm: that's how I interpreted functional tests at first, too, but mtreinish said that was incorrect.18:29
ayoung_dolphm, yeah...this sounds like a lead in to fragile tests18:29
dstanekbknudson: if the test is to creates something then we'll probably check for it. other than that i don't see what we'd be doing.18:29
dolphmif tests are dependent on true implementation details, then they need to be rewritten in order to do refactors, which means the tests are fragile and completely useless.18:29
dolphmayoung_: ++18:30
ayoung_functional tests  exercise the backend, but do not check for implementation details18:30
dstanekdefinitely not hitting the DB directly18:30
dolphmdstanek: ++18:30
dstanekdolphm: ayoung_: ++18:30
stevemar_dolphm: dstanek ayoung_ i think we're all in agreement on that18:30
dstaneki want the same tests to run against any backend (with the exceptions i noted in my documentation)18:30
ayoung_Now,  having two distinct servers running that talk to the same backend is a viable test setup, but it would be expensive.18:31
bknudsonI suggest you bring this up with the -qa team and figure out what the alternative is.18:31
dolphm++18:31
morganEtherpad on mobile has gotten bad :(18:31
stevemar_morgan: :(18:31
dolphmthe alternative is not writing "unit" tests against the database and calling it "functional"18:31
*** sridhar_ram has joined #openstack-meeting18:31
*** mwagner_ has joined #openstack-meeting18:31
ayoung_So stevemar_ what are we looking for here:  big buckets for big rooms and small buckets for small rooms?18:31
stevemar_this has gone way off topic :\18:31
dstanekbknudson: where was this discussed?18:32
bknudsondstanek: they have had summit sessions on it that I wasn't able to attend, so I got learned on irc.18:32
stevemar_ayoung_: yes, big topic for fishbowl rooms and smaller topics for workrooms18:32
lbragstadstevemar_: do you want to have things consolidated yet?18:32
bknudsonmaybe for the workrooms we find some things that a few of us want to work on.18:32
bknudsonfor example, I'd be interested in test refactoring18:33
bknudsonmaybe documentation for the libs18:33
stevemar_lbragstad: i can easily consolidate and pick things, i wanted to give the core team a chance to say "I want this topic to be a fishbowl"18:33
*** mmmpork has joined #openstack-meeting18:33
stevemar_or "I want this topic to be a workroom"18:33
bretonoh, I'd love to see test refactoring.18:33
stevemar_I think anything that touches another project should not be a workroom, since that's hard to schedule18:34
ayoung_5 fishbowl room sessions 5 Work room sessions ?18:34
ayoung_Do I have that right18:34
morgan7 fishbowl for us, 4 workroom18:34
stevemar_ayoung_: no, 7 fish, 4 work18:34
henrynashthe whole policy/roles direction would be another18:34
lbragstadcatalog standardization has been a theme in the last couple summits18:34
lbragstadthat'd probably benefit from being a fishbowl18:34
stevemar_lbragstad: thats gonna be a X-project one18:34
stevemar_so don't even count it on here18:34
lbragstadcool18:35
*** balajiiyer has quit IRC18:35
ayoung_Roles and Policy need to be cross project attended18:35
gyeeayoung_, ++18:35
ayoung_We need buy in, especially from Nova, if we are going to make any progress18:35
*** cloudtrainme has joined #openstack-meeting18:35
stevemar_yep18:35
stevemar_i think "things to deprecate and remove" and "testing" can be working rooms?18:36
samueldmqayoung_: ++18:36
lbragstadfederation as it's own fishbowl i assume18:36
stevemar_anyone disagree?18:36
ayoung_++18:36
lbragstadthere is a *lot* of stuff under those18:36
stevemar_actually... deprecation... we might need input from others18:36
bknudsonThe times were 40 mins right?18:36
ayoung_is federation even that much a hot topic anymore?  Its kindof implemented.  There are details like making them apping easier to work with...openid connect.18:36
ayoung_OK..yeah, that is fishbowl18:37
bknudsonWe didn't get much done in the 40 min sessions last time.18:37
dstanekstevemar_: i would agree since i think those are more likely topics that we'll work on and not just discuss18:37
*** geoffarn_ is now known as geoffarnold18:37
stevemar_basically the contentious ones, I want to make fishbowls18:37
dolphmayoung_: it should be more of a cross-project topic this time around. horizon + keystone + openstackclient + etc18:37
stevemar_dolphm: yep18:37
ayoung_dolphm, ah,  good.18:37
lbragstadI'd agree with that18:37
dolphmstevemar_: is there room for that in the cross-project schedule at this point?18:37
dolphm(federation)18:37
stevemar_dolphm: i dont think it's finalized yet18:38
*** su_zhang has quit IRC18:38
stevemar_I could ask for it18:38
dolphmstevemar_: ++18:38
anteayaI think cross project schedule is on today's tc meeting agenda18:39
dstaneki'll throw this out as a general OpenStack criticism - the x-project initiatives need an x-project team otherwise they'll either never get done or take forever18:39
dolphmanteaya: awesome, thanks18:39
gyeedstanek, so true :)18:39
dolphmdstanek: that's (unfortunately?) true18:39
anteayadolphm: confirmed18:39
dolphmour first round of cross project sessions was a lot of tossing responsibilities over the fence18:40
anteayaI think growing folks to do cross project work is part of what ttx is trying to get the tc to do18:40
dolphmsome number of summits ago18:40
dstanekanteaya: nice18:40
stevemar_that would be cool to see18:40
anteayabut the electorate has to elect folks who aren't currently booked with ptl duties to do so18:40
*** xyang1 has joined #openstack-meeting18:40
anteayaso far, that hasn't happened a lot18:40
*** topol has quit IRC18:40
anteayahere's hoping18:40
bknudsonhey, we made v3 available it's their own fault if they don't use it.18:41
dstanekwe really need OpenStack initiatives and construct a team of the right people - not a project saying we are doing this x-project thing so listen up18:41
* anteaya agrees, having come into the middle of the conversation18:41
*** pballand has joined #openstack-meeting18:41
*** su_zhang has joined #openstack-meeting18:41
stevemar_ayoung_: dolphm dstanek -- everyone>> my current picks: http://paste.openstack.org/show/475509/18:42
*** hashar has joined #openstack-meeting18:42
lbragstadso, almost everything either has 'fishbowl' or 'workroom' next to it18:42
stevemar_lbragstad: ^18:43
lbragstadis paste.o.o slow for anyone else today?18:43
samueldmqdstanek: ++ that looks to have happened to dynamic policies too, when ayoung_ had setions, and it seemed that people form other projects just didn't appear18:43
ayoung_yep18:43
marekdlbragstad: yes18:43
stevemar_i think we got everything on the paste18:43
lbragstadstevemar_: you want federation to be a x-project fishbowl if we have the time, right?18:43
stevemar_lbragstad: i'd prefer that18:44
stevemar_but in case, i can use one of ours18:44
dstaneklbragstad: yes, takes a long time to load18:44
lbragstadstevemar_: ok, marked it as such in the etherpad18:44
gyeestevemar_, and audit?18:45
*** geoffarnold has quit IRC18:45
gyeeits a small A of the AAA after all18:45
stevemar_lbragstad: if anything i would like to have another random cross-project fishbowl session18:45
ayoung_stevemar_, so  Policy can be policy and roles...and with that, I'd like to ask for the last 10 minutes of this meeting to be aboutt roles stuff18:45
*** geoffarnold has joined #openstack-meeting18:45
morgangyee: we are more IAM + audit than AAA now18:45
lbragstadstevemar_: so, should we put an action item under Federation to check on the status of getting a x-project slot for that?18:45
stevemar_ayoung_: that's fine with me, still 5 minutes left18:45
stevemar_err 1518:46
ayoung_++18:46
stevemar_lbragstad: yep18:46
dstanekstevemar_: i'm happy with that list so far18:46
stevemar_i'll be doing that as i look to make sure the service catalog is coming out of x-project fishbowl and not ours18:46
ayoung_++18:46
stevemar_gyee: audit might be a working room18:46
ayoung_would love to move the service catalog to DNS18:46
stevemar_i'd prefer to have the last fishbowl for general crossproject stuff18:47
*** Guest46796 has joined #openstack-meeting18:47
stevemar_so no red flags here right?18:47
dstanekayoung_: i started a little project to test that out18:47
stevemar_no one is feeling short changed?18:47
stevemar_everything is groovy18:47
ayoung_Performing18:47
stevemar_and with that, let the battle begin, ayoung_ and henrynash lace up18:48
ayoung_Heh18:48
stevemar_#topic roles18:48
*** openstack changes topic to "roles (Meeting topic: keystone)"18:48
* dstanek grabs some popcorn and a beer18:48
henrynash(I think not much of a battle, actually!)18:48
ayoung_henrynash, so...aside from naming, I think we are on the same page18:48
* lbragstad grabs a seat next to dstanek18:48
*** balajiiyer has joined #openstack-meeting18:48
stevemar_http://cdn.meme.am/instances/400x/59486625.jpg18:48
ayoung_gyee, role groups  ayoung_ implied roles henrynash virtual roles18:48
ayoung_but I think we all want  roughly the same thing:18:48
*** bswartz has joined #openstack-meeting18:49
ayoung_assing one role, get many...18:49
ayoung_that is the subset of henrynash 's blueprint18:49
gyeeis assing a word?18:49
*** novas0x2a|laptop has joined #openstack-meeting18:49
lbragstadit is now18:49
dolphmgyee: it's the subset18:49
ayoung_yes,  but only halfway18:49
gyeehahahah18:49
ayoung_I guess I half-assigned that18:49
* gyee learn something new today18:49
ayoung_anyway18:50
*** maiteb has joined #openstack-meeting18:50
ayoung_henrynash, you also have the domain specific roles part, which is, I think 2 parts:18:50
ayoung_1  namespacing of roles18:50
henrynashyes18:50
ayoung_2. certain roles don't go in tokens18:50
ayoung_so..if we do implied roles first (expanded in the tokens) can we build the other things on top of it?18:50
henrynashcorrect (maybe “management roles” woudl be a better name for those)18:50
ayoung_henrynash, I was thinking virtual roles would be "roles that imply other roles but that never end up in tokens themselves:18:51
ayoung_"18:51
gyeeall I am asking is usability18:51
dstanekdumb question...does this concept already exist in some other product?18:51
*** wznoinsk has quit IRC18:51
ayoung_dstanek, all over the place18:51
henrynashayoung_: sure, that’s what I meant by them too….but most people don;t like virtual roles (and I’m not sure I do either)18:51
ayoung_dstanek, the reason gyee keeps using the term role groups is that is what MS calls it (at least)18:52
*** njohnston is now known as nate_gone18:52
henrynashand the very first bp I wrote called them role-groups!18:52
ayoung_henrynash, fair enough.  I'll defer on the naming.18:52
*** su_zhang has quit IRC18:52
henrynashand I’m Ok with taht name too18:52
morganRole-groups is pretty descriptive18:52
morganAnd not overloaded18:52
morganFwiw18:52
morganDescriptive and not overloaded = good option18:53
henrynashso implied roles…..just means expand this role-group and put all the roles in the token?18:53
*** bobh_ has quit IRC18:53
*** aswadr has quit IRC18:54
morganI would err to the side of something that people are familiar with. If MS uses "role groups" that is a pretty good option imo18:54
morganhenrynash: i think thst is an inplementation detail18:54
ayoung_henrynash, well, I was thinking that a role is either in the token or not.  an implied role means "If I get this role I get this other one too"18:54
henrynashmorgan: and I’m fine with that18:54
ayoung_so I had them as two dimentions on the role object18:54
morganEither way it could work regardless of the name18:54
morganSo either you expand or you dont. I dont think it matters18:54
ayoung_arole group could be "a role that does not go into a token"18:54
*** AJaeger has joined #openstack-meeting18:54
henrynashayoung_: agreed18:55
lbragstad5 minutes remaining18:55
samueldmqopenstackbot info: 5 mins left18:55
samueldmqlbragstad: o/18:55
ayoung_so if we give someone "admin" they get "member" and both go into the token18:55
dolphmhow are roles groups inherited in hierarchical multitenancy?18:55
gyeewe just need something that is "easy" to explain to average users, "easy" for doc people, "easy" to use18:55
* dolphm sorry.18:55
morganayoung_: yeah. I think your spot on lets defer impl details like expansion for not in this meetinf18:55
ayoung_but if we give someon "IBM-DISTINGUISHED_ENGINEER" that is a roel group and it does not go in the token18:55
henrynashgyee: absolutely +++++18:55
ayoung_morgan, I think we are good18:55
*** dprince has quit IRC18:55
*** topol has joined #openstack-meeting18:55
morganayoung_: yah agreed :)18:55
*** kebray has joined #openstack-meeting18:55
*** yolanda has joined #openstack-meeting18:55
*** shashank_hegde has quit IRC18:55
henrynashayoung_: ok, so namespacing18:56
*** Sukhdev has quit IRC18:56
ayoung_OK...we can battle out the rest of the details at the summit, but I want a goal of having the spec approved before we leave Japan18:56
henrynashayoung_: agreed18:56
ayoung_namespacing...yeah, that is tricky.18:56
ayoung_can we do it in this order:18:57
bknudsoncollect everyone's passport until spec is approved18:57
henrynashayoung_: I think that’s the hardest bit, I agree….if you namespec a role that goes ina token…what does that mean?18:57
ayoung_henrynash, right, one of two things18:57
morganbknudson: i think that is mordred's plan for some other sessions :P18:57
ayoung_1.  namespace to a domain, don;'t put it in the token.   2. Namespace to a service...18:57
stevemar_bknudson: haha18:57
mordredwhat did I do?18:57
ayoung_so nova:admin is different from swift:admin18:57
*** fawadkhaliq has quit IRC18:57
ayoung_and that shoudl be expanded later?18:57
henrynashayoung_: namespacing a role_group to a domain (say) makes a lot of sense (to me)…..and doesn’t affect that types of role that end up in the token18:58
*** fawadkhaliq has joined #openstack-meeting18:58
ayoung_so the related spec (we don't have time for ) is this one18:58
*** Shrews has joined #openstack-meeting18:58
samueldmqhenrynash: yes because role-groups never go in the token18:58
ayoung_https://review.openstack.org/#/c/228477/18:58
ayoung_I see you -1 ed it. have not looked yet18:58
ayoung_henrynash, so get a sketch of your approach up18:59
henrynashayoung_: I only -1’d since I am going to post an alternative so we can comapre18:59
henrynashwill do18:59
ayoung_and with that, I cede the floor18:59
stevemar_and we're up18:59
stevemar_excellent timing18:59
stevemar_#endmeeting18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:59
openstackMeeting ended Tue Oct  6 18:59:40 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-10-06-18.00.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-10-06-18.00.txt18:59
stevemar_thanks everyone!18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2015/keystone.2015-10-06-18.00.log.html18:59
fungiinfra team: assemble!19:00
stevemar_the room now belongs to the infra folks o/19:00
*** KLevenstein_ has joined #openstack-meeting19:00
SotKo/19:00
*** ildikov has joined #openstack-meeting19:00
pleia2o/19:00
clarkbhello19:00
Zarao/19:00
Clinto/19:00
asselino/19:00
anton_haldino/19:00
Shrewsahoy19:00
*** olaph has joined #openstack-meeting19:00
yolandao/19:00
crinkleo/19:00
AJaegero/19:01
jeblairyellow19:01
ianwo/19:01
*** nadya has joined #openstack-meeting19:01
mmedvedeo/19:01
anteayablue19:01
fungi#startmeeting infra19:01
openstackMeeting started Tue Oct  6 19:01:16 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
rfolcoo/19:01
dougwigo/19:01
ruagairo/19:01
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
zaroo/19:01
mmmporko/19:01
*** Daisy has quit IRC19:01
krtayloro/19:01
fungi#topic Announcements: Stackforge namespace retirement19:01
*** openstack changes topic to "Announcements: Stackforge namespace retirement (Meeting topic: infra)"19:01
fungi#link https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement19:02
*** Daisy has joined #openstack-meeting19:02
jeblair(i still need to send a follup mail; hoping to do that today)19:02
fungijust a reminder, this is still scheduled for october 1719:02
*** breton has left #openstack-meeting19:02
fungithanks jeblair19:02
*** KLevenstein has quit IRC19:02
*** KLevenstein_ is now known as KLevenstein19:02
fungi#action jeblair send followup reminder to lagging stackforge projects about namespace retirement19:03
*** samleon_ has quit IRC19:03
anteayadid we ever set a time on oct 17?19:03
*** lhcheng_ has left #openstack-meeting19:03
*** penick has quit IRC19:03
anteayaor shall we discuss that later?19:03
fungiwe can discuss it now i suppose19:03
* anteaya notes we are still in announcemnents19:03
fungiif we keep it brief19:03
anteayaanyone have any thoughts about what time gerrit should go offline?19:03
fungi18:00 utc?19:03
anteayawfm19:04
fungiwho expects to be working on it?19:04
anteayame19:04
mmmporkhow is the project name change going to be run?19:04
fungiwe probably want to leave ourselves plenty of time given the scale of the change19:04
jeblairme, and 1800 works, so does earlier19:04
anteayafungi: I'm guessing about 2 hours downtime anyway19:04
jeblair(but we also might need extended prep before, so maybe not schedule the outage too early)19:04
fungii didn't want to pick something too early for west-coasters19:04
anteayais that too much?19:04
*** pelix has quit IRC19:04
mordredo/19:05
fungithough if SergeyLukjanov, yolanda or jhesketh are wanting to pitch in on the maintenance we can consider less americentric windows19:05
mmmporkalso have we defined a verification process for checking the change result before it goes live?19:05
*** maiteb has quit IRC19:05
mordred(on a plane, landing in 30 minutes, fwiw)19:05
pleia2I'll be on a flight to japan during the rename, so one less west-coaster to worry about19:06
jeblairmordred: are you indicating you are here, or that you will be around on oct 17? :)19:06
*** Daisy has quit IRC19:06
anteayapleia2: thanks for letting us know, safe travels19:06
jeblairpleia2: that sounds fun, we should all go19:06
pleia2jeblair: yeah, let's do it19:06
*** cdub has joined #openstack-meeting19:06
fungifor those without a calendar (or the `cal` utility) handy, keep in mind this is one week from saturday19:06
*** csd has quit IRC19:06
yolandafungi, i cannot be here on 17th october, i have some family appointments. But thanks for the consideration, and i'll try to help in other future tasks19:07
*** csd has joined #openstack-meeting19:07
anteayafungi: looks like it is you me and jeblair so far19:07
fungiyolanda: no problem. i'm sure we have lots of people on hand, and thanks for the heads up19:07
anteayaI'll do as much prep as I can19:07
mmmporki'll be around for it19:07
mmmporkbut i'd like some answers to the questions i just asked :)19:07
*** kebray has quit IRC19:08
clarkbI will be around19:08
fungiokay, to rephrase. any objections to 18:00 utc (or think there's a better time)?19:08
anteayano objections19:08
clarkb1800 wfm19:08
mmmporkno objections here19:09
fungi#agreed Stackforge namespace retirement maintenance will commence at 18:00 UTC, Saturday, October 1719:09
vmbrasseurmmmpork Those are great questions.19:09
fungimmmpork: non-scheduling-related questions can be handled later in the meeting or in #-infra19:09
* ruagair is around too19:09
mmmporkfungi: ok thanks :)19: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-29-19.01.html19:10
fungiClint: write script to prepare layout.yaml change for migration19:10
Clint#link https://review.openstack.org/#/c/228002/19:10
*** fzdarsky has quit IRC19:10
Clintand as sample "output" for a subset of names and using an earlier patchset, there's19:10
*** mhickey has quit IRC19:10
Clint#link https://review.openstack.org/#/c/229601/19:10
*** dprince has joined #openstack-meeting19:10
mordredjeblair: sorry, that was an indication of my skills at attneding thi smeeting. I will be here on the 17th19:10
fungicool, thanks Clint! (and anteaya and mmmpork who seem to be the primary reviewers so far)19:11
jeblairmordred: woot :)19:11
anteayathat output used patchset 12 of the script19:11
jeblairdoes that script cover all the necessary files now?19:11
mmmporki've added some unit test coverage so we can check the file names we are changing and the data we'll be writing out19:11
jeblair(i mean, as far as we know :)19:11
Clintas far as i know19:11
mmmporkjeblair: idk does it? ;)19:11
anteayajeblair: patchset 12 looked fine to me19:11
anteayajeblair: as far as I know19:11
mmmporkthere's a test that i wrote that lists the files we're changing19:12
jeblairmmmpork: exactly :)  rephrased: i take it there are no known omissions at this point?19:12
*** vijendar has joined #openstack-meeting19:12
mmmporkif someone could take the time to review that and make sure our expectation are covered there, that would be great19:12
Clintthe only known issue at this time is that some comments will need to be replaced by hand19:12
anteayaClint: in gerrbot/channels.yaml19:12
Clintright19:13
mmmporkhttps://review.openstack.org/#/c/228002/27/tools/tests/mass_rename_projects_unit_test.py19:13
fungithe sample change looks good on a brief pass. was there a plan to handle the sql update queries?19:13
anteayaas noted in the commit message in the script19:13
Clintfungi: no, i thought that might be done by the ansible stuff, which i haven't seen19:13
fungijasondotstar: that's what you were hacking on?19:13
anteayafungi: as far as I know the sql queries were not part of this script19:13
Clinti was thinking this script would not extend outside the boundaries of the project-config repo19:14
*** amakarov is now known as amakarov_away19:14
*** vijendar has left #openstack-meeting19:14
anteayaClint: well so far it doesn't19:14
Clintright19:14
mmmporkdo we have a checklist somewhere of all the pieces that need to be updated?19:14
anteayaso many steps on of the workflow are not automated19:14
Clintmmmpork: there's https://etherpad.openstack.org/p/project-renames-Septemeber-201519:15
fungioh! right, i skimmed and misread the git mv commands comment you added19:15
jeblairClint, mmmpork: and http://docs.openstack.org/infra/system-config/gerrit.html#renaming-a-project19:15
anteayafungi: yes I did to at first19:15
anteayafungi: thos commands are for the acl file path renames19:15
*** electrocucaracha has joined #openstack-meeting19:15
anteayawhich Clint will run by hand before submitted the patch to be merged19:15
*** gongysh_ has quit IRC19:15
jeblairif we don't have an ansible thing, we have fungi's "script that outputs the sql" we could use19:16
fungiso, anyway, if worse come to worse we have that already scripted (more or less)19:16
fungi#link https://review.openstack.org/22272619:16
*** nate_gone is now known as njohnston19:16
anteayaast you can see in the sample output19:16
anteaya#link script sample output https://review.openstack.org/#/c/229601/19:16
*** cloudtrainme has quit IRC19:16
mmmporkso i'm seeing a bunch of things in a bunch of different places for this project19:16
fungiokay, seems like we're on track then19:16
anteayajeblair: yeah I haven't seen one yet and haven't looked at sample output19:16
anteayafungi: I feel comfortable with where the patch should be19:17
mmmporkand it's still not clear how we're going to do a test run and verify before pushing this change19:17
anteayafungi: you okay to create the working etherpad for this?19:17
*** bryan_att has quit IRC19:17
fungianteaya: yeah, though for sanity it may make sense to not paste the filesystem and database updates into the etherpad directly19:17
*** gongysh_ has joined #openstack-meeting19:18
anteayaagreed19:18
*** bvandenh has quit IRC19:18
anteayaI'm open to however you want to address running those steps19:18
*** ociuhandu has quit IRC19:18
fungi#action fungi start maintenance plan etherpad for stackforge retirement19:18
anteayaas long as we can have the steps noted for when they are done19:18
anteayathanks19:18
fungiwe had one other action item from the last meeting...19:19
fungijhesketh: look into why the swift upload indices are still not appearing19:19
fungijhesketh may not be around19:19
fungianybody happen to know the status on this?19:19
anteayafungi: do you have a new cpu fan for your workstation?19:19
* anteaya does not know the status of swift upload indices19:20
fungianteaya: nope, i'll have contingencies in place this time19:20
anteayafungi: wonderful19:20
mordredfungi: we've started our descent - sorry, hav eto drop19:20
Clintbtw, the project-config script takes a different input format from the one in https://review.openstack.org/22272619:20
anteayamordred: safe landing19:20
*** cloudtrainme has joined #openstack-meeting19:20
clarkbfungi: its working now19:20
anteayaclarkb: yay19:20
fungiclarkb: excellent19:20
clarkbhowever we did run into some problems19:21
fungijhesketh: when you see this, thanks for getting it working!19:21
clarkbswiftclient is not following semver19:21
clarkbso we had to downgrade our swiftclient install19:21
fungiahh, so we hit a backward incompatibility?19:21
clarkbbecause newer version introduced a nonbackward compatible type change19:21
*** bobh has joined #openstack-meeting19:21
clarkbfungi: ya19:21
fungithat's unfortunate19:21
clarkbwe have pinned swiftcleint in os-loganalyze and it should all be fine until we are ready to support the new thing and upgrade though19:22
clarkbbut that was a really fun evening19:22
*** lzachery has quit IRC19:22
fungii can imagine19:22
anteayaI remember it19:22
anteayalate you were19:22
fungiokay, moving on then...19:22
fungi#topic Specs approval19:22
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:22
fungi#info approved "Host a CI systems monitoring dashboard" spec19:22
fungi#link http://specs.openstack.org/openstack-infra/infra-specs/specs/deploy-ci-dashboard.html19:23
fungi#info approved "JJB 2.0.0 API Changes" spec19:23
*** e0ne has quit IRC19:23
notmynameclarkb: that is unfortunate and not intended. I'd love follow-up (outside of your meeting is fine)19:23
fungi#link http://specs.openstack.org/openstack-infra/infra-specs/specs/jenkins-job-builder_2.0.0-api-changes.html19:23
clarkbnotmyname: can do19:23
fungi#topic Specs approval: StoryBoard Worklists and Boards (SotK)19:23
*** openstack changes topic to "Specs approval: StoryBoard Worklists and Boards (SotK) (Meeting topic: infra)"19:23
fungi#link https://review.openstack.org/20298919:23
*** henrynash has quit IRC19:24
SotKThis spec has been hanging around without activity for a month and I'd like to get it approved so that we can merge patches to implement it.19:24
SotKThe work I've done on implementing the spec so far can be seen at http://185.98.149.23/#!/ if people are interested in seeing it.19:24
jeblairooh green19:24
*** gongysh_ has quit IRC19:25
fungiany objections to setting a 48-hour deadline to register concern over that spec?19:25
*** irenab_ has joined #openstack-meeting19:25
*** gongysh_ has joined #openstack-meeting19:25
jeblairnope, looks like ttx has seen it which was the only thing i was going to offer19:25
clarkbnone here19:26
anteayano objections19:26
fungi#info voting open on "StoryBoard Worklists and Boards" spec until 2015-10-08 19:00 UTC19:26
clarkbI am happy for those interested in storyboard to drive their own direction too fwiw19:26
fungisame here, glad to see it surviving!19:26
Zaragreat. please let SotK know if you find any bugs in the implementation; he really loves that... 0:)19:26
fungiheh19:26
SotKthanks people :)19:26
*** spzala has quit IRC19:26
fungi#topic Priority Efforts19:26
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:26
fungiany urgent updates on blockers for the priority efforts listed in our agenda? if no, we've got summit planning coming up and i want to make sure we leave time to discuss19:27
*** irenab has quit IRC19:27
*** irenab_ is now known as irenab19:27
*** safchain has quit IRC19:27
fungigoing once... twice...19:27
fungi#topic Summit planning19:27
*** openstack changes topic to "Summit planning (Meeting topic: infra)"19:27
fungi#link https://etherpad.openstack.org/p/infra-mitaka-summit-planning19:27
fungii see some great ideas on the list so far19:28
anteayaremember to add your name ot the list on the etherpad, top right hand corner19:28
fungiit looks like so far there's a lot of fishbowl ideas but not many workroom ideas19:29
anteayawe like to talk?19:29
anteayaif you leave a question or comment on the etherpad please add your name or nick19:30
ZaraI put mine down as a workroom but I thought it was better suited to a fishbowl, I just didn't want to compete with people for that space since I thought they had a better claim to it.19:30
*** gongysh_ has quit IRC19:30
fungithe other thing worth considering is that our 4 workroom slots are in back-to-back pairs19:30
anteayawhoever just added the green question to yolanda's proposal19:30
clarkbgreghaynes: getting noepool image works might be good fishbowl?19:30
clarkbgreghaynes: and or writing nodepool tests19:30
anteayaZara: looks like you made a good space choice19:30
jeblairi don't think zuulv3 is ready for a workroom yet -- however, we have some things i think need to get done before v3 -- greghaynes nodepool dib work and jhesketh's zuul connector work19:31
jeblairif those are outstanding, maybe we could attack them there19:31
anteayajeblair: +119:31
jeblairclarkb: good idea!  :)19:31
fungiso it's _possible_ we might do an extended workroom session if something benefits from 80 (well 90 if you ifnore the break) minutes instead of the usual 4019:31
yolandahow is status of masterless puppet? shall we dedicated some time there?19:31
*** gongysh_ has joined #openstack-meeting19:31
clarkbjeblair: I will add them19:31
*** kgroves has quit IRC19:31
crinkleyolanda: ++ nibalizer ^19:31
Zaraanteaya: thanks :)19:31
greghaynesSure, I think the image builder stuff should be done before then but who knows what shows up on reviews19:32
jeblairyolanda: yeah, good idea19:32
clarkbgreghaynes: well maybe we use that time to deploy it across the clouds19:32
clarkbgreghaynes: and debug when it breaks :)19:32
greghaynesYea, that actually sounds like a good plan A/B19:32
greghaynesdepending on what state its in19:32
*** e0ne has joined #openstack-meeting19:32
crinkleI think infra cloud might be a good workroom session or it could wait till the sprint day19:33
fungias usual, keep in mind that workroom sessions are ideal for mini-sprint type tasks where we identify something that a room full of people can potentially churn out (at least get a great start on if not complete) in 40 (or 90) minutes19:33
jeblaircrinkle: yeah, depends on if there's something we can accomplish in 40-80 mins with infra cloud... i think of it as more of a half-day thing.19:34
crinklejeblair: i think so too19:34
anteayacrinkle: you want to put it on the etherpad somewhere?19:34
jeblaircrinkle: but if there's a mini-task or plan that needs to be sketched out... that'd work.19:34
crinkleanteaya: sure19:34
fungifor those who joined us on the irc meetings tracker session, that i think was a mostly perfect example of a good workroom idea19:34
jeblairfungi: yeah, we got that 90% done and finished it easily the next week.19:35
anteayacrinkle: then it isn't lost, thanks19:35
fungii think it's good to view workroom sessions as "team building" exercises19:35
*** dandruta has quit IRC19:35
*** IlyaG has quit IRC19:35
fungithey might be things we could collaborate remotely on, but it's fun and helps with socialization to hack together on a common goal and share that sense of accomplishment in the same room19:36
jeblairfungi: and establishing a shared understanding19:36
*** dramalho_ has joined #openstack-meeting19:36
*** ayoung has quit IRC19:36
*** ayoung_ is now known as ayoung19:37
fungifor fishbowl sessions, these tend to be best used for topics which need discussion to arrive at a common consensus or level-set some understanding within the group or cross-project with other stakeholders outside infra, particularly where it might otherwise require a protracted many-weeks-long thread on the ml otherwise19:37
*** gangil has quit IRC19:38
anteayazaro: do you want to keep Gerrit development/upgrade as fishbowl or move to workroom?19:38
zaroanteaya: IMO better as fishbowl.19:39
anteayavery good19:39
fungiwe won't necessarily be making final decisions in a fishbowl, but we'll be exchanging positions and getting what we need to be able to have the final follow-up decision discussions on the ml (so that those who can't make it to the summit can still have some input)19:39
*** claudiub has joined #openstack-meeting19:41
*** cloudtrainme has quit IRC19:41
*** oanufriev_ has joined #openstack-meeting19:41
*** timcline_ has joined #openstack-meeting19:42
fungian important additional detail on the friday sprint time. before lunch we're co-sprinting with the ironic team19:42
anteayaand after lunch with qa and release management19:42
*** angdraug has joined #openstack-meeting19:42
fungimorning would be a great time for infra cloud since we can potentially collaborate on bifrost/bare metal automation needs19:43
pleia2++19:43
*** cloudtrainme has joined #openstack-meeting19:43
clarkbfungi: and possibly onmetal if that is still something magnum wants to try19:43
clarkbthough never heard back from them so maybe not19:43
fungiand afternoon, yes our usual group therapy with qa and rm19:43
anteayacan't miss that19:43
pleia2hehe19:43
jeblairi never thought about release management being acronymed 'rm'.  that's fantastic.19:44
anteayaha ha ha19:44
jeblairer, initialed, i guess.19:44
mordredfungi: I think it would be useful to be explicit on intent with workrooms ... in Vancouver we had different people with mismatched thoughts, both valid things, but mostly incompatible19:44
anteayathat was me19:44
anteayamy fault19:44
mordrednot fault. I just think clarity is good for all19:44
anteayaagree clarity is good19:44
anteayabut I recall that one and will own it19:45
fungimordred: great point. yes workrooms are where we come prepared to collaborate on some predetermined task, not so much come to learn about something or get presented to19:45
*** timcline has quit IRC19:45
*** temujin_ has quit IRC19:45
fungiso it helps to familiarize yourself with what we're going to work on in advance and be ready to volunteer for subtasks19:45
pleia2I think we may also want to consider that we can also split out if we don't feel we need to be there, I kind of thought I *should* but made much better use of my time by splitting off into another smaller group to do other things19:45
mordred++19:46
fungiyep, don't just show up to a workroom session because "it's infra." there will be other places to have conversations or collaborate on unrelated work, and there will also be sessions for other teams going on so it can be a great excuse to cross-pollinate19:47
*** dkranz has quit IRC19:47
*** amrith is now known as _amrith_19:48
*** geoffarnold has quit IRC19:48
fungianyway, the goal with the planning topic for today's meeting was to prompt one another for additional ideas and get them onto the etherpad. we'll have one more meeting where we can settle on which topics from the list we're going to schedule into what slots19:48
anteayaI think the goal for today was successful19:48
*** geoffarnold has joined #openstack-meeting19:48
fungiso if you think of things between now and next tuesday please do add them to https://etherpad.openstack.org/p/infra-mitaka-summit-planning19:49
*** baoli has joined #openstack-meeting19:49
zaroanteaya: i've changed my mind on that 'Gerrit development/upgrade' would be better as workroom, 'scaling repo creation' better as fishbowl.19:49
*** dkranz has joined #openstack-meeting19:49
*** timcline_ has quit IRC19:49
anteayazaro: very good, would you like to make that change?19:49
anteayaand thanks for adding yourself to co-chair scaling, didn't want to speak for you19:49
*** timcline has joined #openstack-meeting19:49
fungizaro: ooh, like collaborate on gerrit/jgit hacking and testing during a work session?19:50
*** roxanagh_ has quit IRC19:50
*** nadya has quit IRC19:51
zarofungi: I was thinking get people started on gerrit/jgit hacking but if someone already knows gerrit then we can collaborate as well19:51
*** tsekiyama has quit IRC19:51
anteayazaro: you have a few respondants to your request for help19:51
fungizaro: it might be a good idea to find out how many of the people who volunteered to help try to fix those will be summiting19:51
anteayaand at least 2 said they would be at summit19:51
fungioh, excellent19:52
anteayapersia I remember19:52
anteayaand one other, I will check the logs post meeting19:52
* fungi notes that it's hard to forget persia19:52
pleia2hehe19:52
anteayaso memorable19:52
zaroiirc, i think signed8bit is only one that is summiting19:52
anteayaand persia19:52
nibalizeryes masterless puppet should get some attention19:53
anteayaand thanks zaro, yes that is the other person19:53
anteayapleia2: found signed8bit19:53
pleia2oh yes, how could I forget19:53
*** fawadkhaliq has quit IRC19:53
*** fawadkhaliq has joined #openstack-meeting19:54
*** shashank_hegde has joined #openstack-meeting19:54
zaroanteaya: np.19:54
anteaya:)19:54
fungiokay, i'll transition this to open discussion for the last 5 minutes since mmmpork had some additional questions about next week's maintenance, but feel free to keep plugging summit session ideas too19:54
zaroanteaya: those sessions are already in the right spot.19:54
anteayazaro: wonderful19:54
fungi#topic Open discussion19:54
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:54
mmmporkwe might want to have a meeting or discussion about the project rename process19:55
*** Sukhdev has joined #openstack-meeting19:55
pleia2I'm speaking at Grace Hopper next week on our CI system, this is a pretty huge deal and I'm going to be very busy at the conference from Tuesday on http://schedule.gracehopper.org/session/open-source-presentations-3/19:55
*** pm90_ has joined #openstack-meeting19:55
pleia2from there I'm off to Japan to do some traveling pre-summit, so see you there? :)19:55
AJaegergreat, pleia2 !19:55
fungipleia2: thanks for the heads up, and good luck! (not that you need it)19:55
SpamapSspeaking of infra-cloud19:56
fungimmmpork: what about the project rename process should we discuss?19:56
pleia2fungi: thanks19:56
jeblairpleia2: yay!19:56
*** spzala has joined #openstack-meeting19:56
SpamapSjust an update.. crinkle and greghaynes pushed a bit and got a mini-cloud up with some hand-massaging of network configs19:56
mmmpork1) what are the pieces that need to be run?19:56
mmmpork2) how will they be run19:56
*** pm90___ has joined #openstack-meeting19:56
*** TravT has joined #openstack-meeting19:56
mmmpork3) are we going to do a test run first?19:56
SpamapSthe current challenge is to turn that into actual automation and deploy it into the working nodes in HP119:56
mmmpork4) how will we verify the results before making actual changes to make sure we didn't miss anything?19:57
*** baoli has quit IRC19:57
anteayapleia2: congratulations19:57
*** pm90__ has quit IRC19:57
*** timcline_ has joined #openstack-meeting19:57
*** tsekiyama has joined #openstack-meeting19:57
mmmporki'm ok with us having a document, an etherpad, or something as long as it's linked on the project wiki and we know who is doing what and when19:57
anteayaSpamapS: crinkle greghaynes congratulations19:57
greghaynes(it was mostly crinkle)19:58
pleia2mmmpork: so project renames are something we do pretty often with the previous stackforge<>openstack churn we used to have19:58
fungimmmpork: so when you say "project rename process" you mean the upcoming maintenance specifically, not just our general project rename process (which we have documented quite thoroughly already)?19:58
mmmporkyes19:58
SpamapSThere should be some patches heading toward system-config with the automation bits.19:58
mmmporksince we're going to be doing a bunch of them all at once and having gerrit downtime to do so, correct?19:58
pleia2mmmpork: this process will be much the same as the one we've done many times, which I think is why we're pretty casual about this and have our etherpad+docs process19:59
pleia2mmmpork: it always requires gerrit downtime19:59
mmmporkalright, if you all are comfortable with that then i won't push for it19:59
crinkleSpamapS: yes, topic:infra-cloud has relevant patches19:59
fungimmmpork: right, so the documented process is still going to be followed, but we have some additional scripts with this one to pregenerate what we're going to run/merge so that it can be reviewed more easily and further in advance19:59
*** mgrohar has joined #openstack-meeting19:59
fungianyway, we're at time19:59
mmmporkfungi: do we have that documented anywhere? what scripts are going to be run, where and by who?20:00
*** pm90_ has quit IRC20:00
fungianyway, we're at time, don't want to hold up the tc20:00
fungimmmpork: we can discuss further in #openstack-infra20:00
*** yolanda has left #openstack-meeting20:00
*** gangil has joined #openstack-meeting20:00
*** gangil has joined #openstack-meeting20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Oct  6 20:00:34 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-10-06-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-10-06-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-10-06-19.01.log.html20:00
ttxAlright... Anyone here for the TC meeting ?20:00
markmcclaino/20:00
jeblairo/20:00
*** jaypipes has joined #openstack-meeting20:00
annegentlehere20:00
dhellmanno/20:01
*** olaph has left #openstack-meeting20:01
*** dramalho_ has quit IRC20:01
ttxrussellb, jgriffith, lifeless, mordred, flaper87, dtroyer, jaypipes, sdague: around ?20:01
* mestery lurks20:01
russellbhi20:01
adam_ghiya20:01
dtroyero/20:01
*** mmmpork has left #openstack-meeting20:01
* edleafe lurks in the back of the room20:01
jaypipeso/20:01
*** timcline has quit IRC20:01
sdagueo/20:01
ttx#startmeeting tc20:02
openstackMeeting started Tue Oct  6 20:02:00 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
*** nmagnezi has quit IRC20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
openstackThe meeting name has been set to 'tc'20:02
* maishsk is lurking 20:02
mordredo/20:02
ttxThis is the last of the meetings for the liberty membership !20:02
*** cloudtrainme has quit IRC20:02
ttxNext week we'll seat the newly-elected members.20:02
flaper87o/20:02
ttxOur agenda for today:20:02
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:02
ttx#topic Add Astara to OpenStack Projects List20:02
*** openstack changes topic to "Add Astara to OpenStack Projects List (Meeting topic: tc)"20:02
ttx#link https://review.openstack.org/19489220:02
ttxThis one seems to have triggered some opposition, not really on the "are you one of us" aspect, but more about being created as a separate project team from Neutron20:03
*** gordc has joined #openstack-meeting20:03
*** mgrohar has quit IRC20:03
ttxMaybe someone opposed could re-voice their concern here, so that we can take it under consideration ?20:03
russellbi don't have much to add here, i've commented heavily on the review20:03
* ttx refreshes20:03
annegentleeven with coffee I was having trouble understanding why propose outside of neutron?20:04
mordredI'm not worried about it not being in neutron personally - since it's not aiming at user-facing api stuff20:04
flaper87I've reviewed and I'd like russellb's concerns to be addressed.20:04
mordredto me, it's more like ovn20:04
mordredthan like something that would exist in neutron20:04
jeblairflaper87: which ones?  i think the only outstanding is "consensus with neutron ptl"20:04
russellbwe did the more important point to me which was whether or not it intended to expose any of its own tenant facing APIs (it does not)20:04
mesterymorgan: OVN exists in Neutron20:04
mesterymordred: ^^^^20:04
annegentlemind, I do appreciate the further explanations people put in this afternoon20:04
russellbwe did *clarify*, i mean20:04
lifelesso/20:04
russellbmestery: i think he means OVN itself vs the driver20:04
lifelesssorry, reviewing :)20:05
mordredmestery: ovn _plugin_ exists in neutron20:05
mesteryrussellb: YEah, :)20:05
mordredmestery: ovn exists in ovs20:05
mesterymordred: Yuppers20:05
* mestery is slow today20:05
mordredI believe an astara plugin for neutron should be in neutron20:05
* stevemar_ sneaks in late20:05
ttxrussellb: yes, I agree that clarifying that they would not do a competing API over the long run was important20:05
jeblairand this proposal has the astara plugin in the stadium20:05
mordredsweet20:05
sdaguemordred: and I believe that was proposed20:05
adam_git wasnt mentioned in review but worth noting that astara consumes and uses nova as much as neutron (to actually do the orchestrating)20:05
russellbttx: that was my biggest concern for the previous -120:05
mordredsdague: ++20:05
dhellmannrussellb, mestery : was your main concern the idea that there might be a tenant-facing API?20:05
*** berendt has quit IRC20:05
flaper87jeblair: I meant the one w.r.t the API and the agreement with neutron's PTL20:05
*** mgrohar has joined #openstack-meeting20:06
ttxmestery: were your concerns addressed by the Astara team answers ?20:06
russellbi also feel that inclusion in Neutron should be considered, but i'm not interested in forcing it from the TC level.  that's between the projects20:06
flaper87at least, discussion. Probably agreement is not the right word20:06
annegentleautonomy? access to OpenStack-ish stuff?20:06
mesteryttx: Ack, refresh again please :)20:06
ttx(and armax's concerns)20:06
russellbi don't think 25 OpenStack projects implementing different pieces of Neutron is what we want, though20:06
*** ayoung has quit IRC20:06
*** electrocucaracha has quit IRC20:06
russellband that's why most things are in Neutron today20:06
jaypipesadam_g: could the orchestration aspect of astara-rug be done with Heat?20:06
adam_gmordred, the current akanda-neutron plugin (soon to be astara-neutron) could/should be20:06
mordredadam_g: ++20:06
mesteryadam_g: ++, nice20:06
sdagueannegentle: personally, I think there is a already *a lot* in neutron, and I don't think it's a success story for either neutron or astara to force fit them20:06
flaper87ok, re-reviewed20:06
adam_gjaypipes, not to my knowledge20:06
annegentlesdague: yeah sdn could / would eat the world20:07
dhellmannjaypipes: no, IIRC, it requires using admin APIs in some cases to make connections to networks not owned by the tenant20:07
mesteryI don't this is SDN folks20:07
ttxAlright. Any other concern, then ?20:07
mesteryIt's an ochestrator20:07
russellbi don't see it as a force fit when literally it's entire purpose in life is to be a neutron backend20:07
* armax lurks20:07
jaypipesadam_g, dhellmann: got it, thank you.20:07
*** cloudtrainme has joined #openstack-meeting20:07
*** geoffarnold is now known as geoffarnoldX20:07
annegentlemestery: that's helpful thanks20:07
*** tsekiyama has quit IRC20:08
flaper87not from me20:08
*** su_zhang has joined #openstack-meeting20:08
mordredrussellb: I thnk for me keeping a separation between nova and neutron and the things that they drive is good - splitting ironic out into its own thing has been great for both nova and ironic, for instance20:08
*** su_zhang has quit IRC20:08
mordredrussellb: but I understand the concern20:08
*** kebray has joined #openstack-meeting20:08
*** su_zhang has joined #openstack-meeting20:08
russellbi'm not concered enough on that point to -1 over it20:08
dhellmannmordred: good analogy20:08
russellbthey're also different projects20:08
*** DericHorn-HP has joined #openstack-meeting20:09
russellbin different industries, with different cultures20:09
SpamapSrussellb: Ironic's sole purpose in life was to be a backend for Nova.20:09
russellbit's amazing how different they are, really20:09
*** tsekiyama has joined #openstack-meeting20:09
russellbbut anyway, i don't want to take up an hour going off on the theory of why i think as much unification in neutron is beneficial20:09
*** geoffarnoldX has quit IRC20:09
russellbi just hope everyone understands that there's been a ton of thought and good reasoning behind how the project is structured20:09
ttxOK, it's got 9 YES, without markmcclain's vote20:09
*** njohnston is now known as nate_gone20:09
lifelessI don't think rejecting them from the tent would make unification happen either20:10
russellbi'm not suggesting rejection20:10
mesteryrussellb: Obviously armax and I understand, thanks for bringing that up :)20:10
*** geoffarnold has joined #openstack-meeting20:10
annegentlearmax: Armando, if you're good with the integration I think my questions are answered20:10
russellbbut there was pushback to the suggestion that unification should be considered20:10
dhellmannrussellb: are there other parts of neutron that implement similar amounts of backend pieces vs. just drivers? I'm honestly uninformed on that.20:10
lifelessrussellb: sure, I get that20:10
russellbdhellmann: absolutely, several20:10
*** thingee has joined #openstack-meeting20:10
dtroyerone suggestion was to put it under Neutron and move out later if that were determined to be the Right Thing.  That works both ways…20:10
russellbi mentioned that multiple times in my review comments20:10
dhellmannrussellb: ok, cool20:10
ttxrussellb: I'm not against them going inside neutron if they prefer, I'm against rejecting their application because they prefer to be a separate team20:11
dhellmannrussellb: well, it wasn't clear initially that folks understood what this actually was so I wasn't sure20:11
russellbthe many pieces referred to as the "reference implementation" for L2 and L3, octavia, the default vpnaas backend, others i'm sure20:11
armaxannegentle: I’ll will have to go through the comments/logs etc…but my initial position is20:11
annegentledhellmann: russellb: right I'm definitely in that camp20:11
flaper87ttx: ++ my thoughts exactly20:11
russellbdhellmann: right, it was also clear ot me that not everyone understood what this was, or what is in neutron.20:11
* dhellmann nods20:11
ttxI'm going to approve it now unless someone screams and has more questions20:11
russellbttx: yep, fair20:11
annegentlettx: give me a sec to click please20:11
armaxso long as the TC is happy with the proposal, I am comfortable with their decision20:11
armaxand won’t stand in the way20:12
lifelessarmax: does Neutron have a strong opinion here?20:12
lifelessarmax: e.g. 'this really should be part of Neutron' ?20:12
armaxlifeless: does that count?20:12
sdaguearmax: it's data, all data counts20:12
mesterylifeless: Did you read the review?20:12
lifelessarmax: its certainly a factor. I would hesitat before doing something that made an OpenStack project PTL unhappy20:12
mesterywow20:12
armaxI expressed my opinion20:13
annegentlearmax: well, I for one rely on the PTL to do the front-line comms20:13
russellbdid you read the review?20:13
mesteryI think armax russellb and I all commented there I thought?20:13
lifelessmestery: presumably not closely enough20:13
mesterylol20:13
* lifeless re-reads20:13
flaper87armax: all input from the community is extremely important20:13
russellbright, current neutron PTL, previous neutron PTL, and myself all commented to that effect20:13
ttxYes, Neutron leadership would have preferred that Astara was added within the Neutron team rather than as a separate team20:14
* jaypipes personally liked the introduction of the very OpenStacky word "tenantive"20:14
*** bswartz has quit IRC20:14
flaper87jaypipes: lol20:14
annegentlejaypipes: +120:14
ttxok, approving now20:14
edleafejaypipes: heh20:15
armaxso long as someone is policing that the astara team stays true to their words20:15
armaxthen I am happy with what they are doing20:15
armaxbut I am not sure if anyone is20:15
dhellmannarmax: policing how? what are you worried about them doing?20:15
mesteryWho's gonna do that?20:15
ttxapproved20:15
russellbin theory the TC has that authority20:15
ttxyes20:15
russellbif concerns are raised in the future20:15
sdaguesure, but I guess what's the concern that should be looked for20:15
*** neelashah has quit IRC20:15
flaper87russellb: ++20:15
markmcclainarmax: the networking APIs are tough enough... last thing I'd want to do is write another20:15
annegentlearmax: really the PTL has that day-to-day communication with teams.20:15
lifelessThe big tent also explicitly allows for competition20:15
russellbnew tenant facing APIs20:15
dhellmannI'm pretty disturbed at the implication of bad faith here. :-(20:16
ttxif the assumptions we are operating on for this decision are contracdicted by fact, we can undo what we've done20:16
lifeless*if* it goes that way20:16
russellbas discussed in several review comments .......20:16
armaxsay that the API all of a sudden becomes tenant facing etc20:16
armaxwho is going to make sure that there’s no overlap...20:16
armaxI am not saying there’s foul play or even intention for it20:16
russellbit would be nice if people read the review in advance of the meeting20:16
dhellmannlifeless: this project does not in any way compete with neutron20:16
armaxbut this does open a loophole20:16
armaxor at least it feels like it does20:16
*** timcline_ has quit IRC20:16
armaxbut don’t mind me20:16
armaxI am paranoid20:16
lifelessdhellmann: armax explicitly raised a concern about such things in the review20:16
armaxI am not going to watch over their shoulders20:16
armaxAstara or anyone else20:16
lifelessrussellb: the meeting is literally the first thing my morning. I try but sometimes family things happen and its a rush20:16
dhellmannlifeless: ok, well, as I wrote a bunch of the original version of this project I'm going to claim more knowledge than armax20:17
ttxarmax: and let us know if you see any issue.20:17
*** timcline has joined #openstack-meeting20:17
armaxI am only taking Astara as an example because they are the one applying for inclusion20:17
*** aeng has joined #openstack-meeting20:17
armaxdhellmann: I didn’t intend to claim otherwise20:17
flaper87armax: your input and neutron's team input will be super valuable on these matters20:17
adam_garmax, dont worry, we're a small team of long time openstackers... and the last thing any of us want is another public facing API :)20:17
armaxbut things change20:17
armaxover time20:17
ttxOK, we need to move on.20:17
armaxI am only asking: who is going to monitor the change?20:17
armaxif at all?20:17
*** browne has left #openstack-meeting20:17
armaxok20:17
lifelessarmax: I think the answer is noone20:18
russellbflaper87: i don't think they feel that way in this case20:18
jaypipesarmax: ceilometer?20:18
armaxlifeless: that’s the worst answer I could get20:18
lifelessjaypipes: boom tish20:18
armaxbut it’s an answer nonetheless20:18
dhellmannarmax: we don't have rules like what you want enforced, though20:18
armaxlifeless: I appreciate it20:18
ttxarmax: "everyone" ?20:18
armaxdhellmann: that’s fine, I get it20:18
ttx(it's the same answer)20:18
flaper87russellb: yeah, I have that feeling and I'd like that to change :(20:19
lifelessarmax: because as dhellmann says - http://governance.openstack.org/reference/new-projects-requirements.html - we don't (anymore) require that things be entirely distinct/non-overlap etc20:19
lifelessso monitoring to make sure they are would be counterproductive20:19
armaxlifeless: I agree…so I feel there’s a double standard then20:19
dhellmannrussellb, flaper87 : I listened, I just disagree.20:19
ttxIf two project teams interests collide, they can escalate to the TC for conflict resolution20:19
dhellmannarmax: how so?20:19
ttxI just fail to see a conflict right now20:20
ttxjust presumption of potential conflict20:20
armaxttx: indeed, and that’s ok20:20
*** ddieterl_ has quit IRC20:20
lifelessarmax: whats the double standard?20:20
armaxlifeless: gbp was shot down20:20
ttxarmax: so if the situation evolves, feel free to raise it20:20
ttxarmax: no20:20
armaxis it back?20:20
dhellmannarmax: gpb *does* overlap quite a bit20:20
ttxarmax: they retracted their proposal20:20
armaxok20:21
mordredarmax: gbp wanted to replace neutron user-facing APIs20:21
mesterydhellmann: Quite a bit? It's another networking API with HW drivers20:21
ttxarmax: current in WIP20:21
mesteryIt more than overlaps20:21
flaper87dhellmann: that's fine, I'm not saying that one has to agree20:21
*** ayoung has joined #openstack-meeting20:21
armaxagain, I am not picking up on astara…but who is going to stop that from happening now?20:21
dhellmannmestery: ok, well, degrees :-)  -- in any case, that's not astara is20:21
*** lblanchard has quit IRC20:21
mesterydhellmann: Agreed20:21
mesteryarmax: The answer is no one20:21
armaxor any other project that does the same?20:22
armaxmestery: right20:22
armaxthat’s fine20:22
mesteryYip20:22
mesteryIt's documented now at least20:22
ttxok, moving on, other topics to cover20:22
ttx#topic Cinder v1 drop postmortem20:22
*** openstack changes topic to "Cinder v1 drop postmortem (Meeting topic: tc)"20:22
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-September/075765.html20:22
ttxsdague: want to drive this one ?20:23
sdagueyes20:23
armaxlet’s move on and cross that bridge should we ever get to it20:23
armaxI only flagged the potential loophole20:23
sdagueso, in the lead up to liberty release, the cinder team tried to disable by default v1 in devstack, which is their previously deprecated major API20:23
annegentlethanks armax and mestery20:23
*** IlyaG has joined #openstack-meeting20:23
sdaguelots of things broke20:23
sdague*lots* of things broke20:23
*** kgroves has joined #openstack-meeting20:23
annegentleso you're saying. lots of things broke.20:24
dhellmannannegentle: I heard it was more than lots20:24
lifelessI hear lots of things broke20:24
mordredhow man?20:24
sdagueand in unpacking the situation after, it turns out that very few bits of code in the wild actually supported cinder v220:24
mordredmany?20:24
dhellmannmordred: 4220:24
mordreddhellmann: ++20:24
sdaguebasically, only tempest20:24
flaper87lol20:24
sdagueand openstack client in the last 3 months20:24
sdague-ish20:25
sdagueso, we reverted that20:25
russellbseems to be a trend in major API revs ...20:25
dhellmannyeah, I think it wasn't complete support in osc, was it?20:25
*** nate_gone is now known as njohnston20:25
dtroyerdhellmann: no support until june/july-ish20:25
sdaguehowever it does raise a question about how this can be done better20:25
lifelesssounds like a data problem20:25
* dhellmann points to his cross-project summit session proposal on "themes", including "functional testing" http://odsreg.openstack.org/cfp/details/1920:25
lifelesslike, we don't know enough about how we're deployed20:25
sdagueand what additions to our deprecation tag we should have for due dilligence20:26
*** pnavarro|afk has joined #openstack-meeting20:26
sdaguethe link above suggested some from the operator community20:26
SpamapSSeems to me that developer queues need to be filled when deprecated API's are used in the gate. As in, "hey there's a bug over here please fix it"20:27
sdagueI think rally / tempest / and openstack client support for at least 1 full cycle seems useful20:27
mordredI would think that at the very least we cannot _start_ deprecation of an old API until everyting in OpenStack supports the new one20:27
dhellmannI think the things from the email made sense, and I just assumed projects would actually be following through on that work before deprecating APIs. I mean, if the client didn't even properly support it deprecation was obviously premature20:27
*** sdake has quit IRC20:27
mordredlike, you can't mark it deprecated if anything else in OpenStack (which we do have control over) is still using it20:27
dhellmannmordred: ++20:27
lifeless++mordred20:27
jaypipessdague: so tempest supported v2 cinder API, but didn't test anything a deployment that *only* had v2 enabled and not v1?20:27
mordredbecaue it's really not actually deprecated until then20:28
ttxsdague: the tag mandates making a survey of operators around usage of the feature to be removed20:28
dhellmannsdague: do you think we need a time frame?20:28
*** sdake has joined #openstack-meeting20:28
sdaguejaypipes: tempest worked20:28
lifelessmordred: using-by-default though IMO20:28
jeblairit's possible our thinking around 2 cycles was from when we had 3 projects and everyone in the same room.20:28
mordredlifeless: yes20:28
flaper87dhellmann: mordred ++20:28
ttxsdague: it's just that the procedure (which is new) wasn't followed20:28
stevemar_jeblair: ++20:28
lifelessmordred: like, we probably want clients to support old-and-new and be new-by-default before deprecating20:28
sdaguettx: sure, because deprecation of the v1 api predates that20:28
jaypipessdague: sorry that should have said "but didn't test *against* a deployment that *only* had v2 enabled and not v1"20:28
sdagueby at least a year20:28
mordredlifeless: using by default across all of openstack should be a barrier to being able to suggest deprecation of old20:28
flaper87I guess a good first step is to have non-voting gates running with the deprecated API disabled20:28
dhellmannjeblair: are you suggesting longer?20:28
ttxsdague: so I'm not sure the tag language is insufficient20:28
lifelessmordred: yes, that language should be in our tag20:28
sdaguejaypipes: no, but that part actually worked20:28
flaper87that should give an idea of what's would happen20:28
SpamapSThere almost needs to be a different word than deprecated.20:28
* flaper87 shrugs20:28
mordreddhellmann: I'd personally suggest that we NEVER deprecate old APIs20:29
lifelessSpamapS: abandonded ?20:29
mordredbut I know I'll get killed for that20:29
sdaguerally didn't support v2 at all, and grenade blew up because of osc issues20:29
dhellmannmordred: let's take this one step at a time20:29
mordredso I'll stand for "not until it's default across all of openstack"20:29
annegentlemordred: I"m thinking that's reality and we should match it20:29
mordredfor now20:29
annegentlefor now20:29
jeblairdhellmann: more that the idea that a single fixed period is sufficient only if everyone is on top of things and pushing adoption aggressively, which wasn't the case here.20:29
stevemar_sdague: same with barbican when we tried to switch keystone to v320:29
dhellmannjeblair: ah, right, I agree with that assessment20:29
*** fawadkhaliq has quit IRC20:29
lifelessjeblair: I think the period is fine, as long as the *starting point* is 'when all the work has been completed'20:29
annegentlejeblair: good point20:29
jeblairlifeless: yes, i think that's key.20:30
mordredlifeless, jeblair++20:30
dhellmannmordred: on the other hand, that means all openstack projects have veto of any project they consume20:30
mordreddhellmann: they already do20:30
dhellmannwell, your rule would make that more explicit20:30
sdagueso, I think there is a deadlock issue with that approach. However, it does seem like a project should know which other parts of openstack do / don't work with it.20:30
sdagueand be deliberate about that20:30
dhellmannmordred: I don't like cross-project veto powers20:30
sdaguedhellmann: yeh, I agree, because you get lazy deadlock there20:31
lifelesssdague: tell me more about the deadlock concerns ?20:31
dhellmannmordred: it means deadlock20:31
dhellmannsdague: right20:31
*** IlyaG has quit IRC20:31
mordreddhellmann: well, if a project just decides to be a bonehead about it - I think we should look at that project and their esprit de corps20:31
annegentlesdague: yeah20:31
dhellmannlifeless: A won't adopt B's v2, so B can never drop V1 support20:31
SpamapSSo there's really 4 phases in the life of an API in OpenStack. Right now. "New', "Usable", "Deprecated", and "Removed"20:31
mordreddhellmann: to me it means the ornery project gets themselves kicked out of the tent20:31
*** claudiub has quit IRC20:31
lifelessdhellmann: that might mean that V2 has some real issues?20:31
ttxmordred: I'm not sure that will be that well-cut20:31
mordredof course not :)20:31
jaypipesmordred: not sure that is realistic. :)20:31
dhellmannlifeless: or that project A is not prioritizing collaboration20:32
SpamapSWhat seems to be missing is something between "Usable" and "Removed" which sets off alarm bells.20:32
dhellmannlifeless: both happen in practice20:32
ttxmordred: a lot of projects were pretty lazy (and still are) with keystone v320:32
lifelessdhellmann: so I don't like the thing there were a project can unilaterally force another project to do a bunch of work20:32
*** kgroves has quit IRC20:32
lifelessdhellmann: it seems like there should be a middle ground20:32
ttxuntil it's down to one "bonehead" there is some road to travel20:32
sdagueso, before we got down the fisty-cuffs route, how about having a standard for what we expect projects to know about their API usage20:32
dhellmannlifeless: agreed, we need projects to work together to support each other's evolutions20:32
stevemar_SpamapS: maybe that's where "Abandoned" comes in20:32
mordredttx: yes. exactly20:32
flaper87I think one of the things that have caused delays on moving projects to new APIs is who's going to do that work20:32
annegentlemordred: it's not like that, it's more the "prioritizing collaboration" description20:33
flaper87It's happened w/ keystone, Cinder and Glance20:33
dhellmannsdague: ++20:33
dhellmannflaper87: ++20:33
russellbflaper87: yep20:33
sdaguebecause, I'll admit, when we make API changes in nova I go off and look at some of the 3rd party sdks like fog to see what people actually consume20:33
russellbgenerally always assume the "other team" should/will do it20:33
ttxmordred: so "until everyone supports it or you are tired to wait and ask the TC for a bonehead exemption ?"20:33
SpamapSRight, like "Deprecated" just means "Disapproved of". So the project is saying "we have something else now, we disapprove of using this one", but it still gets attention.20:33
lifelessbrook's law is starting to hit us here :)20:33
flaper87exactly, whereas I believe this is exactly what cross-project efforts are fore20:33
flaper87As of Glance, we've now a small team between nova and glance working on this20:34
* SpamapS steps down from box.20:34
flaper87Joint efforts like this are the ones that would help APIs moving forward20:34
markmcclainflaper87: ++20:34
ttxSpamapS: the tag uses "deprecation" and "obsolesence"20:34
flaper87Also, achieving everything in 1 cycle is just impossible unless there's just 1 project consuming your API20:34
ttxhttp://governance.openstack.org/reference/tags/assert_follows-standard-deprecation.html20:34
flaper87And since project resources are not infinite, it must be scheduled carefully20:35
david-lylefrom a horizontal project perspective, watching this realization of big tent difficulties with a distributed governance model is fun20:35
annegentleEnd-user docs have Current, Supported, Deprecated, Experimental.20:35
sdagueok, so moving this conversation towards actionable. I think I heard mixed things about do we need more language in the tag20:35
annegentle#link http://developer.openstack.org/api-ref.html20:35
*** hrou has quit IRC20:35
sdagueannegentle: right, but experimental is pre current20:35
lifelesssdague: I think we need more guidance20:36
ttxsdague: we have to move on -- what do you suggest as a next step ? Dedicating one of the cross-project sessions to the question of deprecation ?20:36
dhellmannsdague, annegentle : it would be good to have those 2 docs use consistent language20:36
sdaguettx: we could do that20:36
lifelesssdague: I don't know that the *tag* should specify development process, but the user-visible impact and process for deprecation certainly makes sense to be in there to me20:36
annegentledhellmann: sdague: yes, also my thinking, consistent terms are needed20:36
ttxsdague: or ML thread between now and then20:36
flaper87ttx: if there's a free slot, yes20:36
flaper87but I would put this in the box with all other proposals20:37
sdaguewell originally, I was going to suggestion we bring in the ideas in here - http://lists.openstack.org/pipermail/openstack-dev/2015-September/075765.html as a starting point20:37
sdaguebut we could do this as a cross project session given that it's fresh20:37
*** baoli has joined #openstack-meeting20:37
sdagueand get some write up after about additional guidelines on deprecation20:37
ttxthat sounds like a good topic to me20:38
sdagueok, I'll propose20:38
sdagueand run20:38
david-lyleterminology is not the issue; defining, scheduling and driving work is the issue. any project can choose to deprecate something, the problem is making other projects care20:38
annegentledavid-lyle: good perspetive20:38
*** mtaylor has joined #openstack-meeting20:38
ttxdavid-lyle: ties into defining "cycle goals", a session that dhellmann proposed20:39
annegentledavid-lyle: and I think you're right fwiw20:39
ttxi.e. having common goals and driving them20:39
dhellmanndavid-lyle: yes, see my comments earlier about veto power20:39
*** comay has joined #openstack-meeting20:39
*** maishsk_ has joined #openstack-meeting20:39
*** wolsen has quit IRC20:39
flaper87it's not just about making other projects care, the project deprecating things should care enough as well20:39
flaper87*cough* glance *cough*20:39
flaper87It's literally a cross-project effort20:39
ttxok, let's move on, we have a path forward and won't solve it in-meeting anyway20:40
david-lylebut in the big tent, how widely do they have to care?20:40
flaper87one that must be taken 1 project at a time (depending on the resources available)20:40
ttxdavid-lyle: big tent doesn't mean no rule20:40
flaper87ttx: ++20:40
ttxjust means easier entry20:40
ttx(which also means easier kicking out)20:40
*** wolsen has joined #openstack-meeting20:40
sdagueand you should care about all your consumers, not just the ones in the openstack namespace20:40
david-lylenot arguing is does, but if you push deprecation work on one project to carry out across openstack20:40
david-lylehow wide is that20:41
*** iben has joined #openstack-meeting20:41
mtaylordepends on how widely you're used, honestly ... keystone might have more work ahread of them than other projects, for instance20:41
ttxdavid-lyle: totally agree that some coordination is required. Can't be all consumer or all originating project20:41
sdaguethere is actually a reason we rolled back 2 years of development on Nova API and went down a different path20:41
mtaylorand the cost of that is something that projects should think about when looking at new APIs20:41
*** maishsk has quit IRC20:41
*** maishsk_ is now known as maishsk20:41
flaper87which will require them more time to do it20:41
edleafesdague: +120:41
mtaylorbecause if it's hard to get the new api rolled out across openstack20:42
mtaylorthink about how hard it is on the users you do not know20:42
david-lylesdague: my concern is we can't even seem to drive these changes in the namespace, outside is harder yet20:42
*** mordred has quit IRC20:42
sdaguedavid-lyle: yep, for sure20:42
sdagueok, we'll take it to summit20:42
ttxok, we really need to move on, but I'm looking forward to the discussion on this20:42
*** mtaylor is now known as mordred20:42
david-lylesdague: I think that was a more sane direction for sure20:42
ttxNot really a TC-specific thing anyway20:42
*** Sukhdev has quit IRC20:42
ttxmoving on20:42
* david-lyle sits back down20:42
ttx#topic stackforge retirement: make workflow reqs+cla clearer20:42
*** openstack changes topic to "stackforge retirement: make workflow reqs+cla clearer (Meeting topic: tc)"20:42
ttx#link https://review.openstack.org/22917620:42
ttxcool, plenty of votes20:43
ttxQuestions, comments, objections ?20:43
flaper87go go go go20:43
ttxgone20:43
russellb+120:43
ttx#topic Note that the TC expects some project history.20:43
*** gongysh_ has quit IRC20:43
*** gangil has quit IRC20:43
*** cdub has quit IRC20:43
*** novas0x2a|laptop has quit IRC20:43
*** ijw has quit IRC20:43
*** erlon has quit IRC20:43
*** akuznetsova has quit IRC20:43
*** Guest46796 has quit IRC20:43
*** davidlenwell has quit IRC20:43
*** jhesketh has quit IRC20:43
*** adrianofr has quit IRC20:43
*** zigo has quit IRC20:43
*** aarefiev has quit IRC20:43
*** amit213 has quit IRC20:43
*** tonyb has quit IRC20:43
*** galstrom has quit IRC20:43
*** haleyb has quit IRC20:43
*** DuncanT has quit IRC20:43
*** sarob has quit IRC20:43
*** krotscheck has quit IRC20:43
*** rharwood has quit IRC20:43
*** gus has quit IRC20:43
*** neillc has quit IRC20:43
*** edwarnicke has quit IRC20:43
*** enikanorov__ has quit IRC20:43
*** sigmavirus24 has quit IRC20:43
*** eglute has quit IRC20:43
*** d34dh0r53 has quit IRC20:43
*** GheRivero has quit IRC20:43
*** j^2 has quit IRC20:43
*** jraim has quit IRC20:43
*** jroll has quit IRC20:43
*** dolphm has quit IRC20:43
*** lbragstad has quit IRC20:43
*** comstud has quit IRC20:43
*** jbryce has quit IRC20:43
*** jacorob has quit IRC20:43
*** rainya has quit IRC20:43
*** jose-idar has quit IRC20:43
*** toan has quit IRC20:43
*** Guest68187 has quit IRC20:43
*** sankarshan_away has quit IRC20:43
*** tlbr_ has quit IRC20:43
*** mattoliverau has quit IRC20:43
*** otherwiseguy has quit IRC20:43
*** dtroyer has quit IRC20:43
*** sudorandom has quit IRC20:43
*** ruagair has quit IRC20:43
*** openstack changes topic to "Note that the TC expects some project history. (Meeting topic: tc)"20:43
ttx#link https://review.openstack.org/22945620:43
*** qwebirc42309 has joined #openstack-meeting20:43
ttxsame20:43
ttxQuestions, comments, objections ?20:44
*** lpeer has quit IRC20:44
dhellmanndid we lose anyone to the netsplit?20:44
*** lpeer_ has joined #openstack-meeting20:44
* flaper87 crickets20:44
annegentlehere20:44
russellbdtroyer20:44
dhellmannI dtroyer gone20:44
ttxnot that my smart filter could tell20:44
dhellmann*see20:44
ttxdtroyer approved it so I'll suppose he is fine with it20:45
jeblairi think dtroyer made a really good point on the review which i think perhaps many agree with but i'm afraid will be lost since it's just a comment.20:45
flaper87ttx: mmh, I think our smart filters need refining20:45
ttxgone20:45
*** qwebirc42309 has quit IRC20:45
ttx#topic Add team:non-diverse-affiliation tag20:45
*** openstack changes topic to "Add team:non-diverse-affiliation tag (Meeting topic: tc)"20:45
ttx#link https://review.openstack.org/21872520:45
mordreddhellmann: I got lost too and had to reconnect20:45
ttxOh! Objections.20:45
dhellmannjeblair: maybe a follow-up patch to add text20:45
ttxmust be very recent20:45
*** gongysh_ has joined #openstack-meeting20:45
*** cameron.freenode.net changes topic to "Cinder v1 drop postmortem (Meeting topic: tc)"20:45
ttxgo home barjavel you're drunk20:46
*** gangil has joined #openstack-meeting20:46
*** cdub has joined #openstack-meeting20:46
*** novas0x2a|laptop has joined #openstack-meeting20:46
*** Guest46796 has joined #openstack-meeting20:46
*** ijw has joined #openstack-meeting20:46
*** erlon has joined #openstack-meeting20:46
*** akuznetsova has joined #openstack-meeting20:46
*** davidlenwell has joined #openstack-meeting20:46
*** jhesketh has joined #openstack-meeting20:46
*** adrianofr has joined #openstack-meeting20:46
*** zigo has joined #openstack-meeting20:46
*** aarefiev has joined #openstack-meeting20:46
*** amit213 has joined #openstack-meeting20:46
*** tonyb has joined #openstack-meeting20:46
*** galstrom has joined #openstack-meeting20:46
*** haleyb has joined #openstack-meeting20:46
*** DuncanT has joined #openstack-meeting20:46
*** sarob has joined #openstack-meeting20:46
*** krotscheck has joined #openstack-meeting20:46
*** rharwood has joined #openstack-meeting20:46
*** gus has joined #openstack-meeting20:46
*** neillc has joined #openstack-meeting20:46
*** edwarnicke has joined #openstack-meeting20:46
*** enikanorov__ has joined #openstack-meeting20:46
*** sigmavirus24 has joined #openstack-meeting20:46
*** eglute has joined #openstack-meeting20:46
*** d34dh0r53 has joined #openstack-meeting20:46
*** GheRivero has joined #openstack-meeting20:46
*** j^2 has joined #openstack-meeting20:46
*** jraim has joined #openstack-meeting20:46
*** sudorandom has joined #openstack-meeting20:46
*** jroll has joined #openstack-meeting20:46
*** dolphm has joined #openstack-meeting20:46
*** lbragstad has joined #openstack-meeting20:46
*** comstud has joined #openstack-meeting20:46
*** jbryce has joined #openstack-meeting20:46
*** jacorob has joined #openstack-meeting20:46
*** rainya has joined #openstack-meeting20:46
*** jose-idar has joined #openstack-meeting20:46
*** Guest68187 has joined #openstack-meeting20:46
*** toan has joined #openstack-meeting20:46
*** sankarshan_away has joined #openstack-meeting20:46
*** tlbr_ has joined #openstack-meeting20:46
*** mattoliverau has joined #openstack-meeting20:46
*** otherwiseguy has joined #openstack-meeting20:46
*** dtroyer has joined #openstack-meeting20:46
*** ruagair has joined #openstack-meeting20:46
russellbi mentioned my concern in a tc meeting once, was going to abstain20:46
russellbbut decided to go ahead and -120:46
ttxlifeless, russellb: could you further elaborate why we are netter without it ?20:46
ttxbetter*20:46
*** wbhuber has quit IRC20:47
lifelessttx: so we discussed it previously. I think that the social negatives of 'earnt a bad badge' are worse than the social negatives of 'failing to expose these risks to our users'20:47
russellbjust concerned with "negative" tags in general, and whether they are overall good.  my gut says it's not an overall win.20:47
ttxFWIW this has enough votes to pass now, just want to understand your concern to see if that makes me revert my vote20:47
*** pleia2 has quit IRC20:47
lifelessttx: I'd be ok with 'failed to earn a specific good badge'20:47
russellbagree with lifeless summary20:47
*** pnavarro|afk has quit IRC20:47
*** waynr has quit IRC20:47
*** fawadkhaliq has joined #openstack-meeting20:48
dhellmannttx: I've removed my vote, for now20:48
lifelessttx: negative feedback tends to really be felt brutally and viscerally by folk20:48
*** trey has quit IRC20:48
lifelessttx: you need to be super careful about how you do it, and an automated algorithm on our governance site is *not it*20:48
edleafeisn't it an objective evaluation?20:49
lifelessedleafe: it is both20:49
edleafeIt's not like saying "we don't like you"20:49
ttxlifeless: I'm not sure I see it as a subjective thing, what edleafe said20:49
sdaguelifeless: even if it's pretty clear to applying teams that it's a boundary20:49
dhellmannthe numbers for diversity are visible through stackalytics without a lot of effort, I wonder if we'd do better to link to that in the regular diversity tag docs20:49
lifelessttx: I didn't say subjective at any point :)20:49
*** DericHorn-HP has quit IRC20:49
ttxit's like, don't force our consumers to go through stackallytics to get their opinion on how diverse a team is20:49
lifelessdhellmann: I'd be comfortable with that20:49
russellbdhellmann: sure, "if you want to understand more, regardless of whether a project has met this defined threshold, see stackalytics" +120:50
ttxit's not as if the facts weren't there20:50
sdagueI guess I feel like in the past projects in this bucket would have been shown the door completely20:50
flaper87To me, the tag is stating something that can is evident by looking at the project's activity.20:50
ttxsdague: they would not have been accepted in the first place20:50
sdaguettx: right, that's what I mean20:50
*** waynr has joined #openstack-meeting20:50
ttxbasically, it's something we used to judge as part of the integrated-release concept20:50
*** trey has joined #openstack-meeting20:51
ttxand we erased that bit of information20:51
ttxthis is just proposing to expose it again20:51
*** DericHorn-HP has joined #openstack-meeting20:51
flaper87I think the concern here is not about the information but about how it's exposed20:51
ttxif it is seen as a bad thing and teams work on diversity as a result, all the better ?20:51
dhellmannttx: I see lifeless and russellb's point that this feels more like stick than carrot20:51
jeblairttx: we do still have the diverse-affiliation tag for exposing that information.20:51
*** Sukhdev has joined #openstack-meeting20:51
lifelessttx: hang on, we have a diversity carrot tag20:51
maishskflaper87: +120:52
devanandattx: is exposing that in a negative way (project X does not Y) valuable to the community, or in shaping the community, in a big-tent world?20:52
flaper87I don't want to just tell people that they should look into stackalytics before deploying things because I kinda thing we should also be a bit more informative20:52
*** geoffarnold has quit IRC20:52
*** morgan has quit IRC20:52
*** morgan has joined #openstack-meeting20:52
ttxI'm fine deferring the decision on this one. That means deferring to the next TC membership though20:52
lifelesswe can create a curated list of projects that have earnt all the previously-this-was-integrated badges20:52
*** geoffarnold has joined #openstack-meeting20:52
dhellmannlifeless: that's the tc-approved-release20:53
devanandalifeless: we started from that list. it's inthe history20:53
lifelessdhellmann: no20:53
dhellmannat least as it stands today20:53
lifelessdhellmann: thats the interface with the board and defcore AIUI20:53
dhellmannoh, you mean as individual things20:53
dhellmannwell, I mean we have the list of those projects already20:53
flaper87What if we tag diverse projects and leave non-diverse projects tagless ?20:53
*** sdake has quit IRC20:53
lifelessdhellmann: I just mean gather up the various carrt tags20:53
russellbdhellmann: yes, and i want to trend toward being a community with a culture of more carrots and less sticks20:53
flaper87that's pretty much the same but the other way around20:53
dhellmannflaper87: that's what we're doing now20:53
ttxOK, let's continue the discussion on the review, it doesn't have majority yet.20:53
lifelessdhellmann: and provide a list of 'super good healthy happy projects'20:53
flaper87however, the tag would be positive20:53
dhellmannrussellb: ++20:53
ttxif still blocked at next meeting we'll call for direct vote20:53
lifelessdhellmann: and say 'this is the safe space. Beyond that you'll need to learn aboutthe project to assess'20:54
ttxwe need to move on to cover the rest of the agenda20:54
lifelessrussellb: ++ that trend. Me too.20:54
flaper87dhellmann: ? don't think so or I didn't express myself correctly20:54
edleafeis the purpose of the tag to reward/punish the team, or to enlighten potential outside users about the project's state?20:54
lifelessflaper87: I think dhellmann means the status quo20:54
markmcclainmy main concern is the education side of it.. ie how do folks know which carrots a project should have20:54
ttxedleafe: the latter20:54
flaper87lifeless: ah, that makes more sense20:54
lifelessflaper87: is that we have no negative tag and only the positive tag.20:54
flaper87lifeless: thanks20:55
annegentleedleafe: all about giving others info20:55
*** Sukhdev has quit IRC20:55
dhellmannmarkmcclain: get all the carrots!20:55
edleafettx: that's what I thought. Seems childish to insist on only positive tags to spare hurt feelings20:55
ttxok, continue discussion on the review20:55
ttx#topic Cross-project track at Mitaka design summit20:55
*** openstack changes topic to "Cross-project track at Mitaka design summit (Meeting topic: tc)"20:55
ttxhttp://odsreg.openstack.org/20:55
ttxI submitted a bunch there, you should too20:55
ttxcontent will be decided next week20:55
russellbedleafe: feelings matter to me.  openstack is people and i care about them.20:56
dhellmannttx: does that system email the proposer when comments are added?20:56
ttxwe need to set up a meeting on Monday to hash the results20:56
*** pleia2 has joined #openstack-meeting20:56
dhellmannttx: if not, we should make sure folks know to go look at the questions that have been left20:56
ttxdhellmann: not really20:56
russellbedleafe: feel free to go work on the linux kernel if you'd like to be in a place where feelings don't matter20:56
flaper87russellb: ++ on feelings matters20:56
edleaferussellb: so do I, but this isn't a judgment on the people; it's an objective assessment20:56
russellbthat's quite an over simplification20:56
russellbanyway we have moved on20:56
edleafeyep20:56
ttxrussellb: agreed, that's why I don't want to rush a decision on this20:57
*** AJaeger has quit IRC20:57
flaper87ttx: meeting on monday sounds good20:57
*** Rockyg has joined #openstack-meeting20:57
ttxWho is up for a meeting on Monday to prepare the results ?20:57
flaper87o/20:57
ttx1500 UTC ?20:57
sdague1500 utc seems fine20:57
flaper87ttx: 14 would be better20:57
ttxthat's usually the magic time20:57
*** skraynev_ has joined #openstack-meeting20:57
dhellmanno/20:57
ttxI'm fine with 1400, but PT people might not20:57
flaper87but if it doesn't work for others, I'll adapt20:57
*** sdake has joined #openstack-meeting20:58
ttxok, sync with flaper on your availability, he will setup the meeting20:58
ttx#topic Communications workgroup report20:58
*** openstack changes topic to "Communications workgroup report (Meeting topic: tc)"20:58
ttxannegentle, flaper87: o/20:58
annegentleboy. um....20:58
* annegentle shuffles feet and looks down20:58
*** _amrith_ is now known as amrith20:58
ttxdo we have enough for a "end of liberty" blogpost ?20:58
annegentleI meant to have one ready by tomorrow but haven't given much thought to it20:59
annegentleI think we do ttx20:59
flaper87I think we could do that and we had some other good content from today's meeting too20:59
*** jcoufal has joined #openstack-meeting20:59
annegentleflaper87: up for drafting with me?20:59
annegentleflaper87: yep20:59
ttx#action flaper87 to set up a meeting on Monday to prepare the cross-project track agenda ahead of the TC meeting20:59
flaper87annegentle: yes, lets etherpad together20:59
annegentleflaper87: cool thanks20:59
stevemar_annegentle: i thought this was nice: http://www.slideshare.net/openstack/liberty-release-preliminary-marketing-materials-messages no idea who did it though20:59
ttxannegentle: can be a bit of a retrospective21:00
ttx#topic Open discussion21:00
*** openstack changes topic to "Open discussion (Meeting topic: tc)"21:00
ttxRemember we'll have a joint Board of Directors / TC meeting on Monday Oct 26 afternoon starting at 2:30pm21:00
ttxmordred: any progress on the TC dinner plans ?21:00
ttxAnything else, anyone ?21:00
annegentlestevemar_: nice find, thanks!21:00
*** neelashah has joined #openstack-meeting21:00
*** jecarey has joined #openstack-meeting21:00
russellba DCO non-update posted to the foundation ML: http://lists.openstack.org/pipermail/foundation/2015-October/002201.html21:00
lifelessflaper87: 1400 UTC - uhm, 2am, nope21:00
sdaguerussellb: thanks for that21:00
*** pnavarro|afk has joined #openstack-meeting21:00
flaper87lifeless: 15 is not any better21:00
russellbsdague: hopefully it's an oversight21:00
flaper87:P21:00
*** topol_ has joined #openstack-meeting21:00
ttxmordred: note: no dinner planned on Monday evening, only the snacks at the WOO event until 7:30pm21:01
*** DericHorn-HP has quit IRC21:01
*** mgrohar has quit IRC21:01
*** rfolco has quit IRC21:01
dhellmannlifeless: leave comments on the proposals21:01
ttxso that's an option21:01
flaper87lifeless: 15 UTC is midnight here21:01
*** pennerc has joined #openstack-meeting21:01
*** gyee has quit IRC21:01
*** spzala has quit IRC21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Oct  6 21:01:31 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-10-06-20.02.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-10-06-20.02.txt21:01
ttxand we are over time21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2015/tc.2015-10-06-20.02.log.html21:01
markmcclaincourtesy ping Mitaka PTLs: armax boris-42 bswartz cp16net david-lyle devkulkarni dhellmann dims dirk dprince dtroyer emilienm21:01
ttxmarkmcclain: channel is yours21:01
markmcclaincourtesy ping Mitaka PTLs: flaper87 flwang gordc hyakuhei isviridov jklare johnthetubaguy jroll loquacities odyssey4me21:01
lifelessdhellmann: -> #openstack-dev to get out of channel21:01
markmcclaincourtesy ping Mitaka PTLs: redrobot SergeyLukjanov skraynev slagle SlickNik smcginnis smelikyan stevemar thinrichs TravT ttx21:01
markmcclaincourtesy ping Liberty PTLs: j^2 thingee kiall nikhil_k stevebaker jeblair devananda morganfainberg mestery21:02
david-lyleo/21:02
gordco/21:02
thingeeo/21:02
redroboto/21:02
markmcclaincourtesy ping Liberty PTLs: cloudnull ttx number80 adrian_otto slagle SlickNik21:02
docaedoo/21:02
smcginniso/21:02
jroll\o21:02
markmcclainper last week's request ... discourteous ping: fungi21:02
jokke_o/21:02
devanandao/21:02
dhellmanno/21:02
docaedo(even though I don't get a courtesy ping ;) )21:02
markmcclain#startmeeting crossproject21:02
lifelessno ping this week21:02
openstackMeeting started Tue Oct  6 21:02:31 2015 UTC and is due to finish in 60 minutes.  The chair is markmcclain. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
skraynev_o/21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** waynr has quit IRC21:02
*** waynr has joined #openstack-meeting21:02
nikhilo/21:02
*** bvandenh has joined #openstack-meeting21:02
*** openstack changes topic to " (Meeting topic: crossproject)"21:02
fungithanks markmcclain!21:02
openstackThe meeting name has been set to 'crossproject'21:02
lifelessits a very odd ping list21:02
lifelesso/21:02
edleafeo/21:02
*** topol has quit IRC21:02
stevebaker\o21:02
markmcclainlifeless: should be the superset of ptls until I've got list errors21:03
markmcclains/until/unless21:03
stevemar_o\21:03
markmcclainfungi: here to please21:03
lifelessmarkmcclain: + tc :)21:03
markmcclain#link https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting21:03
markmcclainlifeless: I'll correct it for next time21:03
lifelessmarkmcclain: unless the TC isn't relevant to the meeting... :)21:03
*** dkranz has quit IRC21:04
nikhilcan we add a section to the wiki for all those who want to be notified/pinged?21:04
stevemar_lifeless: ohhh burn21:04
* Rockyg lurks21:04
markmcclainnikhil: sure21:04
*** rtheis has quit IRC21:04
lifelessmarkmcclain: sorry, enough kibbitzing from me, on ward and upward :)21:04
markmcclainno action items from last time21:04
markmcclain#topic Horizontal Team Announcements21:04
*** openstack changes topic to "Horizontal Team Announcements (Meeting topic: crossproject)"21:04
markmcclainAny horizontal announcements?21:05
ttxOn the Design Summit front, the per-track schedule is now officialized at mitakadesignsummit.sched.org21:05
ttxThe scheduling system is also available for the PTLs scheduling pleasure21:05
ttxDetails at:21:05
* armax here if you need me21:05
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2015-October/076172.html21:05
ttxIt's the same system as last summit. Let me (or thingee) know if you have any questions.21:06
ttxOn the release management front, we are about 9 days before the end of the liberty dev cycle21:06
ttxWe have release candidates for everything, and are actively respinning RCs to include latest translations21:06
ttxYou should all start working on the release notes at:21:06
ttx#link https://wiki.openstack.org/wiki/ReleaseNotes/Liberty21:06
ttxOn the governance front, we have a TC membership election going on, please vote!21:06
ttxThat is all from me21:07
markmcclainttx: thanks for the update21:07
annegentlethanks for the release notes reminder!21:07
stevemar_general note saying the tool for updating the design sessions is awesome21:07
*** harshs has quit IRC21:07
annegentle#info Work on those release notes for liberty21:07
*** fawadkhaliq has quit IRC21:07
*** pennerc has quit IRC21:07
markmcclainannegentle: yes.. good release notes are critical part of the release21:08
*** fawadkhaliq has joined #openstack-meeting21:08
markmcclainAny other horizontal team announcements?21:08
*** harshs has joined #openstack-meeting21:08
ttxstevemar_: I should put it under Gerrit21:08
*** raildo is now known as raildo-afk21:09
dhellmannttx: ++21:09
*** jcoufal has quit IRC21:09
stevemar_++21:09
ttxstevemar_: there is a bug when adding "another track" to a session, but that's actually sched API acting up21:09
*** penick has joined #openstack-meeting21:09
ttxstevemar_, dhellmann: we are supposed to drop Sched and work on our own system21:09
ttxso I always thought it would not be necessary to go beyond github.21:10
ttxhttps://github.com/ttx/summitsched for reference21:10
dhellmannttx: orly?21:10
*** aysyd has quit IRC21:10
*** elo1 has quit IRC21:11
ttxanyway, moving on ;)21:11
lifelessttx: where do we get the resources to do that?21:11
ttxlifeless: foundation21:11
markmcclain#topic Service Catalog Standardization21:11
*** openstack changes topic to "Service Catalog Standardization (Meeting topic: crossproject)"21:11
ttxlifeless: (not done yet)21:11
markmcclain#link https://review.openstack.org/#/c/181393/21:12
* annegentle waves21:12
*** baoli has quit IRC21:12
annegentlewhere's that etherpad from last week?21:12
stevemar_sdague: ^21:12
markmcclain#link https://etherpad.openstack.org/p/mitaka-service-catalog21:12
annegentlethanks21:12
*** bobh has quit IRC21:13
*** geoffarnold has quit IRC21:13
annegentlemuch overlap, there is. But I think that the spec covers everything in the etherpad, am I missing anything?21:13
*** elo has joined #openstack-meeting21:13
*** baoli has joined #openstack-meeting21:14
annegentleWe'd love an unauthed service catalog but documenting how to filter it might work too21:14
*** geoffarnold has joined #openstack-meeting21:14
* stevemar_ is still concerned that removing project IDs is gonna be hard for swift21:14
*** changbl has quit IRC21:14
stevemar_i've love an unauthenticated catalog21:14
*** anton_khaldin has quit IRC21:14
annegentlestevemar_: yeah looking at that, hm21:14
bknudsonif swift isn't willing to sign up to remove project IDs from their catalog then this is a non-starter.21:14
stevemar_bknudson: yep21:14
annegentlebknudson: the whole spec?21:14
annegentledo we have swift ptl notmyname's input?21:15
notmynameah, sorry, I didn't get a ping. looking21:15
*** bvandenh has quit IRC21:15
annegentlewhere {account} is equal to project, right bknudson?21:15
bknudsonnot the whole spec.21:16
markmcclainnotmyname: my apologies... error in my list21:16
*** balajiiyer has quit IRC21:17
bknudson$SWIFT_SERVICE_PROTOCOL://$SERVICE_HOST:8080/v1/AUTH_\$(tenant_id)s21:17
annegentleThis etherpad is a great continuation of the etherpad that got... lost... in Vancouver21:17
notmynameno worries. typing to catch up :-)21:17
bknudsonthat's what devstack is setting for the endpoitn now21:17
bknudsonhttp://git.openstack.org/cgit/openstack-dev/devstack/tree/lib/swift#n61921:17
stevemar_bknudson: but could it work without that?21:17
stevemar_just cause devstack sets it up like that21:17
stevemar_doesn't mean we want it that way21:18
*** fawadk has joined #openstack-meeting21:18
bknudsonstevemar_: I don't get to decide that.21:18
stevemar_bknudson: that's where notmyname comes in :)21:18
annegentledevstack becomes docs for many people for "how do I configure this" including the docs team, so understanding if devstack _has_ to do it that way is pretty crucial21:19
notmynameAIUI, looking to remove the "tenant_id" part? completely or to replace with something else?21:19
dtroyerIIRC the inital reason DevStack does that is due to client requirements.  If the client can work with a SC endpoint without the account it should be OK21:19
dtroyera lot has changed since that was done...21:19
bknudsonnotmyname: for nova the plan is to make the tenant_id optional. If it's not present then it'll get the project from the token.21:20
annegentledtroyer: yeah21:20
notmynamebknudson: what if it's some other string besides the project id?21:20
bknudsonkeystone only supports replacing tenant_id and user_id in the service catalog21:20
stevemar_notmyname: ideally we want it to just be an unversioned URL21:20
notmynameor is the choice project/tenant id or nothing?21:20
notmynamestevemar_: "Versioned" is confusing here. a tenant id isn't a version21:21
*** dprince has quit IRC21:21
stevemar_notmyname: sorry, you guys only have v121:21
stevemar_notmyname: ideally we want it to be: http://hostname:808021:21
notmyname /v1/{account}21:21
stevemar_that's it21:21
notmynamehmm21:21
stevemar_nope21:21
stevemar_let the clients handle /v1/account21:21
notmynamesorry, that was a reply to your earlier one21:21
*** fawadkhaliq has quit IRC21:22
notmynameso there would need to be some sort of catalog so clients can look up what their account string is, right?21:22
stevemar_keystone tokens already have project ids in there, so we can determine the URL21:22
*** novas0x2a|laptop has quit IRC21:22
annegentlenotmyname: right, a lookup21:22
stevemar_well when you authenticate with keystone you project a project name/id, so we would just re-use that one21:23
notmynameannegentle: if only we had an openstack project that could server some sort of catalog about services available ;-)21:23
stevemar_notmyname: hehe21:23
notmynamestevemar_: is that in the identity response from the auth_token middleware or encoded int he token itself?21:23
bknudsonin the case of nova devstack sets "$nova_api_url/v2/\$(tenant_id)s" -- so the idea is to change to "$nova_api_url/v2"21:23
annegentlenotmyname: :)21:24
bknudsonand nova will work with either tenanted URLS or non-tenanted URLs for a while.21:24
stevemar_notmyname: it's definitely in the token itself, and the middleware has an option for setting the project too21:24
*** e0ne has quit IRC21:24
notmynamestevemar_: ah ok. so eg "the first 15 bytes" or something21:24
bknudsonauth_token middleware sets the project ID in the environment21:25
*** baoli has quit IRC21:25
stevemar_bknudson: yep in X-Project-Id21:25
*** matrohon has quit IRC21:25
redrobotbknudson I think you mean jus $nova_api_url  ... version should be added by the client.21:26
*** baoli has joined #openstack-meeting21:26
*** baoli has quit IRC21:27
bknudsonredrobot: yes, I was splitting out the versioning conversation from replacing tenant_id conversation21:27
bknudsonstrangely, devstack also sets "$nova_api_url/v2.1/\$(tenant_id)s"21:27
*** baoli has joined #openstack-meeting21:28
*** baoli has quit IRC21:28
annegentlebknudson: that can be changed as long as we know things will work after the change21:28
annegentlebknudson: right?21:28
*** baoli has joined #openstack-meeting21:28
notmynameI'll have to look at this in more detail. at minimum, this will take a lot of dev work and testing in swift, if it's even possible. I know most people in here hate to hear this, but it also will be tricky to make sure all the non-keystone auth integrations still work21:29
*** vgridnev has quit IRC21:29
*** hashar has quit IRC21:29
*** jcoufal has joined #openstack-meeting21:29
bknudsonannegentle: right, we can change the contents of the catalog... the server and clients need to support it.21:29
annegentlenotmyname: that's a fair assessment and then risk analysis21:29
annegentlebknudson: ok right21:29
*** Sukhdev has joined #openstack-meeting21:29
*** baoli has quit IRC21:29
stevemar_notmyname: cool, might be worth bugging the nova folks to see how they are transitioning from project IDs in the url to not have them21:30
bknudsonif they don't have keystone then they don't have to worry about a service catalog21:30
notmynamestevemar_: yeah, but I doubt that nova uses that string for actual data placement21:30
notmynamein swift, that string is used as one of the inputs to the hash function for data placement and retrieval21:30
bknudsonso clients must already be adding account id on their own.21:31
stevemar_notmyname: so in swift you actually use the service catalog entries?21:31
*** baoli has joined #openstack-meeting21:31
*** ociuhandu has joined #openstack-meeting21:31
bknudson... this might be why you were asking about {account_id}21:31
notmynamebknudson: no, the auth system, whatever it is, returns a storage url that includes the account part21:31
notmynamestevemar_: ^ answers your question too :-)21:32
markmcclain#action notmyname to investigate how proposed service catalog change impacts swift further21:32
mordredoh21:32
bknudsonI think the point of the spec is to have a static service catalog (no replacements)21:32
mordredis the TC proposed catalog changes?21:32
*** MaxPC has quit IRC21:32
mordred(or cross-project or whatever that spec was)21:32
stevemar_bknudson: yes, that's hopefully the outcome :)21:33
*** hrou has joined #openstack-meeting21:33
annegentlemordred: it's the cross-project spec21:33
mordredcool21:33
* mordred loves that spec - just making sure he hadn't missed other catalog change proposals21:34
*** pnavarro|afk has quit IRC21:34
*** baoli has quit IRC21:34
*** geoffarnold has quit IRC21:35
*** geoffarnold has joined #openstack-meeting21:35
markmcclainAny last thoughts on this topic?21:35
annegentleon Q21:35
annegentleer, one Q, do I need to update the spec with a link to the etherpad above?21:35
annegentleor can I add on later?21:36
markmcclainI think it can be added later21:36
notmynameannegentle: at least in a comment for now would be nice21:36
notmynameIMO21:36
*** baoli has joined #openstack-meeting21:36
*** su_zhang has quit IRC21:36
markmcclainnotmyname: good idea21:36
markmcclainok moving on21:37
markmcclain#topic Vertical Team Announcements21:37
*** openstack changes topic to "Vertical Team Announcements (Meeting topic: crossproject)"21:37
annegentlenotmyname: check21:37
markmcclainSeeing no announcements moving on21:38
markmcclain#topic Open Discussion21:38
*** openstack changes topic to "Open Discussion (Meeting topic: crossproject)"21:38
*** aeng has quit IRC21:39
*** sridhar_ram has quit IRC21:39
fungireminder: the gerrit maintenance for the stackforge namespace retirement starts at 18:00 utc october 17 (a week from saturday)21:39
markmcclainfungi: thanks21:40
*** henrynash has joined #openstack-meeting21:40
markmcclainLast call...21:40
*** thangp_ has quit IRC21:41
*** baoli has quit IRC21:41
markmcclainThanks to everyone for joining this week. EmilienM will be chairing next week.21:42
*** ociuhandu has quit IRC21:42
markmcclainHave a great week.21:42
annegentlegood call fungi21:42
markmcclain#endmeeting21:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:42
openstackMeeting ended Tue Oct  6 21:42:17 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-10-06-21.02.html21:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-10-06-21.02.txt21:42
openstackLog:            http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-10-06-21.02.log.html21:42
*** baoli has joined #openstack-meeting21:42
*** ayoung has quit IRC21:43
*** annegentle has quit IRC21:43
*** baoli has quit IRC21:43
*** baoli has joined #openstack-meeting21:44
*** skraynev_ has quit IRC21:44
*** ociuhandu has joined #openstack-meeting21:44
*** banix has quit IRC21:44
*** topol_ has quit IRC21:44
*** gordc has left #openstack-meeting21:44
*** gyee has joined #openstack-meeting21:45
*** pennerc has joined #openstack-meeting21:46
*** harlowja has quit IRC21:46
*** IlyaG has joined #openstack-meeting21:46
*** topol has joined #openstack-meeting21:46
*** baoli has quit IRC21:47
*** baoli has joined #openstack-meeting21:47
*** baoli has quit IRC21:48
*** pennerc has left #openstack-meeting21:48
*** elo1 has joined #openstack-meeting21:49
*** baoli has joined #openstack-meeting21:49
*** annegentle has joined #openstack-meeting21:50
*** elo has quit IRC21:50
*** jckasper has quit IRC21:51
*** topol has quit IRC21:51
*** pm90___ has quit IRC21:52
*** julim has quit IRC21:53
*** harshs has quit IRC21:53
*** Swami_ has joined #openstack-meeting21:54
*** Swami has quit IRC21:55
*** sridhar_ram has joined #openstack-meeting21:55
*** aeng has joined #openstack-meeting21:55
*** stevemar_ has quit IRC21:55
*** stevemar_ has joined #openstack-meeting21:56
*** harshs has joined #openstack-meeting21:56
*** harshs has quit IRC21:56
*** baoli has quit IRC21:56
*** baoli has joined #openstack-meeting21:56
*** harlowja has joined #openstack-meeting21:57
*** harshs has joined #openstack-meeting21:57
*** harshs has quit IRC21:57
*** stevemar_ has quit IRC21:58
*** lpeer_ has quit IRC21:58
*** lpeer_ has joined #openstack-meeting21:58
*** trozet has quit IRC22:00
j^2:D22:00
*** fawadk has quit IRC22:01
*** glauc____ has quit IRC22:01
*** armax has quit IRC22:02
*** neelashah has quit IRC22:02
*** stanchan has quit IRC22:03
*** asettle has joined #openstack-meeting22:03
*** weshay has quit IRC22:04
*** Adri2000 has quit IRC22:04
*** jruano has quit IRC22:04
*** rossella_s has quit IRC22:06
*** rossella_s has joined #openstack-meeting22:06
*** stevemar_ has joined #openstack-meeting22:07
*** annegentle has quit IRC22:08
*** baoli has quit IRC22:08
*** JRobinson__ has joined #openstack-meeting22:08
*** baoli has joined #openstack-meeting22:09
*** edwarnicke has quit IRC22:09
*** patrickeast has quit IRC22:09
*** adrianofr has quit IRC22:09
*** CaptTofu has quit IRC22:09
*** ChrisPriceAB has quit IRC22:09
*** dougwig has quit IRC22:09
*** sweston has quit IRC22:09
*** rex_lee_ has quit IRC22:09
*** gangil has quit IRC22:09
*** boris-42 has quit IRC22:09
*** pm90_ has joined #openstack-meeting22:11
*** henrynash has quit IRC22:13
*** baoli has quit IRC22:13
*** baoli has joined #openstack-meeting22:14
*** ijw has quit IRC22:14
*** mwagner_ has quit IRC22:14
*** armax has joined #openstack-meeting22:16
*** baoli has quit IRC22:16
*** mrmartin has joined #openstack-meeting22:17
*** geoffarnold has quit IRC22:17
*** geoffarn_ has joined #openstack-meeting22:18
*** edtubill has quit IRC22:18
*** apoorvad has quit IRC22:18
*** baoli has joined #openstack-meeting22:19
*** jaypipes has quit IRC22:19
*** IlyaG has quit IRC22:20
*** IlyaG has joined #openstack-meeting22:21
*** aweeks has quit IRC22:22
*** xgerman has quit IRC22:22
*** baoli has quit IRC22:22
*** j^2 has quit IRC22:22
*** baoli has joined #openstack-meeting22:23
*** gangil has joined #openstack-meeting22:23
*** gangil has joined #openstack-meeting22:23
*** spotz is now known as spotz_zzz22:23
*** galstrom is now known as galstrom_zzz22:24
*** su_zhang has joined #openstack-meeting22:25
*** mrmartin has quit IRC22:27
*** timcline has quit IRC22:27
*** armax has quit IRC22:28
*** baoli has quit IRC22:28
*** pradk has quit IRC22:28
*** baoli has joined #openstack-meeting22:28
*** pballand has quit IRC22:31
*** KLevenstein has quit IRC22:33
*** su_zhang has quit IRC22:34
*** annegentle has joined #openstack-meeting22:35
*** pballand has joined #openstack-meeting22:35
*** jckasper has joined #openstack-meeting22:36
*** jckasper has quit IRC22:36
*** lukebrooker has joined #openstack-meeting22:36
*** Rockyg has quit IRC22:36
*** jcoufal has quit IRC22:37
*** geoffarn_ is now known as geoffarnoldX22:37
*** edwarnicke has joined #openstack-meeting22:38
*** ChrisPriceAB has joined #openstack-meeting22:38
*** geoffarnoldX has quit IRC22:38
*** erlon has quit IRC22:38
*** geoffarnold has joined #openstack-meeting22:39
*** Shrews has left #openstack-meeting22:40
*** IanGovett has quit IRC22:40
*** ociuhandu has quit IRC22:41
*** CaptTofu has joined #openstack-meeting22:42
*** stevemar_ has quit IRC22:43
*** dougwig has joined #openstack-meeting22:43
*** stevemar_ has joined #openstack-meeting22:43
*** rbak has quit IRC22:44
*** sweston has joined #openstack-meeting22:46
*** stevemar_ has quit IRC22:46
*** adahms has joined #openstack-meeting22:47
*** Rockyg has joined #openstack-meeting22:47
*** ociuhandu has joined #openstack-meeting22:48
*** pballand has quit IRC22:50
*** pballand has joined #openstack-meeting22:50
*** pballand has quit IRC22:52
*** gangil has quit IRC22:52
*** gangil has joined #openstack-meeting22:53
*** gangil has joined #openstack-meeting22:53
*** boris-42 has joined #openstack-meeting22:53
*** Rockyg has quit IRC22:53
*** ociuhandu has quit IRC22:53
*** jwcroppe_ is now known as jwcroppe22:54
*** IanGovett has joined #openstack-meeting22:55
*** annegentle has quit IRC22:55
*** annegentle has joined #openstack-meeting22:57
*** IlyaG has quit IRC22:58
*** KLevenstein has joined #openstack-meeting22:59
*** geoffarnold has quit IRC23:00
*** geoffarnold has joined #openstack-meeting23:00
*** cloudtrainme has quit IRC23:01
*** apoorvad has joined #openstack-meeting23:01
*** adrianofr has joined #openstack-meeting23:01
*** mudassirlatif_ has joined #openstack-meeting23:02
*** claudiub has joined #openstack-meeting23:03
*** eharney has quit IRC23:03
*** vivek-ebay has quit IRC23:04
*** mudassirlatif has quit IRC23:05
*** mudassirlatif_ is now known as mudassirlatif23:05
*** baoli has quit IRC23:07
*** emagana has quit IRC23:07
*** emagana has joined #openstack-meeting23:07
*** su_zhang has joined #openstack-meeting23:07
*** igordcard_ has joined #openstack-meeting23:08
*** igordcard_ has quit IRC23:08
*** igordcard_ has joined #openstack-meeting23:08
*** vivek-ebay has joined #openstack-meeting23:09
*** MIDENN_ has quit IRC23:09
*** hichihara has joined #openstack-meeting23:10
*** ociuhandu has joined #openstack-meeting23:11
*** pballand has joined #openstack-meeting23:14
*** rex_lee_ has joined #openstack-meeting23:15
*** sigmavirus24 is now known as sigmavirus24_awa23:16
*** ociuhandu has quit IRC23:16
*** KLevenstein has quit IRC23:17
*** IlyaG has joined #openstack-meeting23:17
*** ociuhandu has joined #openstack-meeting23:17
*** shashank_hegde has quit IRC23:19
*** ociuhandu_ has joined #openstack-meeting23:19
*** pballand has quit IRC23:19
*** Sukhdev has quit IRC23:20
*** igordcard_ has quit IRC23:20
*** geoffarnold has quit IRC23:21
*** harshs has joined #openstack-meeting23:21
*** geoffarnold has joined #openstack-meeting23:21
*** igordcard_ has joined #openstack-meeting23:22
*** ociuhandu has quit IRC23:22
*** ociuhandu_ is now known as ociuhandu23:22
*** roxanagh_ has joined #openstack-meeting23:24
*** j^2 has joined #openstack-meeting23:27
*** patrickeast has joined #openstack-meeting23:29
*** igordcard_ has quit IRC23:29
*** agireud has quit IRC23:32
*** dane_leblanc has quit IRC23:32
*** mwagner_ has joined #openstack-meeting23:33
*** yamahata has joined #openstack-meeting23:34
*** hemna is now known as hemnafk23:35
*** tsekiyama has quit IRC23:35
*** igordcard_ has joined #openstack-meeting23:36
*** aweeks has joined #openstack-meeting23:36
*** achanda_ has joined #openstack-meeting23:36
*** bill_az_ has quit IRC23:37
*** yamamoto has joined #openstack-meeting23:40
*** achanda has quit IRC23:40
*** tochi has joined #openstack-meeting23:40
*** achanda_ has quit IRC23:41
*** sdake_ has joined #openstack-meeting23:41
*** jruano has joined #openstack-meeting23:42
*** kebray has quit IRC23:43
*** sdake has quit IRC23:43
*** geoffarn_ has joined #openstack-meeting23:43
*** tsekiyama has joined #openstack-meeting23:44
*** xgerman has joined #openstack-meeting23:45
*** Daisy has joined #openstack-meeting23:46
*** geoffarnold has quit IRC23:46
*** annegentle has quit IRC23:46
*** carl_baldwin has quit IRC23:47
*** roxanagh_ has quit IRC23:48
*** yamamoto has quit IRC23:48
*** irenab has quit IRC23:48
*** iben has quit IRC23:49
*** shashank_hegde has joined #openstack-meeting23:49
*** stevemar_ has joined #openstack-meeting23:50
*** darrenc is now known as darrenc_afk23:51
*** lpeer_ has quit IRC23:51
*** sdake_ has quit IRC23:52
*** xyang1 has quit IRC23:52
*** Swami_ has quit IRC23:53
*** Daisy has quit IRC23:53
*** Daisy has joined #openstack-meeting23:54
*** tsekiyama has quit IRC23:54
*** cdub has quit IRC23:54
*** novas0x2a|laptop has joined #openstack-meeting23:55
*** mestery has quit IRC23:56
*** tsekiyama has joined #openstack-meeting23:56
*** mestery has joined #openstack-meeting23:56
*** jdurgin1 has quit IRC23:56
*** yamahata has quit IRC23:57
*** ajmiller has quit IRC23:57
*** Daisy has quit IRC23:58
*** pm90_ has quit IRC23:59

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