Monday, 2016-05-16

*** ddieterly[away] is now known as ddieterly00:01
*** shaohe_feng has quit IRC00:07
*** shaohe_feng has joined #openstack-meeting-alt00:08
*** cknight has joined #openstack-meeting-alt00:14
*** esker has joined #openstack-meeting-alt00:15
*** esker has quit IRC00:16
*** esker has joined #openstack-meeting-alt00:17
*** amotoki has joined #openstack-meeting-alt00:17
*** shaohe_feng has quit IRC00:17
*** kzaitsev_mb has quit IRC00:18
*** tango has joined #openstack-meeting-alt00:18
*** tango has quit IRC00:18
*** shaohe_feng has joined #openstack-meeting-alt00:18
*** Sukhdev has joined #openstack-meeting-alt00:19
*** zz_dimtruck is now known as dimtruck00:20
*** shaohe_feng has quit IRC00:28
*** shaohe_feng has joined #openstack-meeting-alt00:28
*** obondarev has quit IRC00:29
*** obondarev has joined #openstack-meeting-alt00:30
*** shaohe_feng has quit IRC00:38
*** shaohe_feng has joined #openstack-meeting-alt00:39
*** bana_k has joined #openstack-meeting-alt00:39
*** Qiming has joined #openstack-meeting-alt00:46
*** hoangcx has joined #openstack-meeting-alt00:47
*** hoangcx has left #openstack-meeting-alt00:47
*** shaohe_feng has quit IRC00:48
*** shaohe_feng has joined #openstack-meeting-alt00:49
*** shaohe_feng has quit IRC00:58
*** amotoki has quit IRC00:59
*** shaohe_feng has joined #openstack-meeting-alt00:59
*** zhurong has joined #openstack-meeting-alt01:03
*** shaohe_feng has quit IRC01:09
*** shaohe_feng has joined #openstack-meeting-alt01:10
*** tango has joined #openstack-meeting-alt01:11
*** reldan has quit IRC01:11
*** tango has quit IRC01:11
*** kzaitsev_mb has joined #openstack-meeting-alt01:18
*** shaohe_feng has quit IRC01:19
*** amotoki has joined #openstack-meeting-alt01:21
*** myoung|lunch has joined #openstack-meeting-alt01:22
*** shaohe_feng has joined #openstack-meeting-alt01:22
*** Qiming has left #openstack-meeting-alt01:24
*** kzaitsev_mb has quit IRC01:24
*** rwsu has quit IRC01:27
*** bswartz has quit IRC01:28
*** shaohe_feng has quit IRC01:29
*** shaohe_feng has joined #openstack-meeting-alt01:30
*** IlyaG has joined #openstack-meeting-alt01:38
*** rwsu has joined #openstack-meeting-alt01:39
*** shaohe_feng has quit IRC01:39
*** IlyaG has quit IRC01:40
*** wangqun has joined #openstack-meeting-alt01:40
*** shaohe_feng has joined #openstack-meeting-alt01:43
*** salv-orlando has joined #openstack-meeting-alt01:43
*** sdague has quit IRC01:47
*** amotoki has quit IRC01:47
*** shaohe_feng has quit IRC01:50
*** shaohe_feng has joined #openstack-meeting-alt01:51
*** salv-orlando has quit IRC01:51
*** IlyaG has joined #openstack-meeting-alt01:52
*** shaohe_feng has quit IRC02:00
*** shaohe_feng has joined #openstack-meeting-alt02:01
*** ddieterly is now known as ddieterly[away]02:02
*** myoung|lunch has quit IRC02:03
*** cknight has quit IRC02:06
*** amotoki has joined #openstack-meeting-alt02:10
*** shaohe_feng has quit IRC02:10
*** shaohe_feng has joined #openstack-meeting-alt02:11
*** houming has joined #openstack-meeting-alt02:13
*** yuanying_ is now known as yuanying02:17
*** nelsnels_ has joined #openstack-meeting-alt02:19
*** nelsnelson has quit IRC02:19
*** dave-mccowan has joined #openstack-meeting-alt02:20
*** kzaitsev_mb has joined #openstack-meeting-alt02:20
*** shaohe_feng has quit IRC02:20
*** shaohe_feng has joined #openstack-meeting-alt02:23
*** kzaitsev_mb has quit IRC02:25
*** shaohe_feng has quit IRC02:31
*** shaohe_feng has joined #openstack-meeting-alt02:31
*** bswartz has joined #openstack-meeting-alt02:33
*** tango has joined #openstack-meeting-alt02:35
*** shaohe_feng has quit IRC02:41
*** IlyaG has quit IRC02:41
*** shaohe_feng has joined #openstack-meeting-alt02:42
*** ccamacho has quit IRC02:43
*** ccamacho has joined #openstack-meeting-alt02:45
*** shaohe_feng has quit IRC02:51
*** shaohe_feng has joined #openstack-meeting-alt02:52
*** yamamot__ has joined #openstack-meeting-alt02:54
*** shaohe_feng has quit IRC03:02
*** ddieterly[away] has quit IRC03:02
*** shaohe_feng has joined #openstack-meeting-alt03:02
*** dimtruck is now known as zz_dimtruck03:04
*** zz_dimtruck is now known as dimtruck03:04
*** reedip__ has joined #openstack-meeting-alt03:08
*** coolsvap has joined #openstack-meeting-alt03:11
*** shaohe_feng has quit IRC03:12
*** shaohe_feng has joined #openstack-meeting-alt03:13
*** dimtruck is now known as zz_dimtruck03:13
*** coolsvap has quit IRC03:15
*** yamamot__ has quit IRC03:19
*** zhhuabj_ has quit IRC03:19
*** kzaitsev_mb has joined #openstack-meeting-alt03:21
*** sgotliv has joined #openstack-meeting-alt03:21
*** shaohe_feng has quit IRC03:22
*** shaohe_feng has joined #openstack-meeting-alt03:23
*** kzaitsev_mb has quit IRC03:26
*** baoli has joined #openstack-meeting-alt03:26
*** baoli has quit IRC03:30
*** coolsvap has joined #openstack-meeting-alt03:32
*** shaohe_feng has quit IRC03:32
*** shaohe_feng has joined #openstack-meeting-alt03:33
*** zhhuabj_ has joined #openstack-meeting-alt03:35
*** shaohe_feng has quit IRC03:43
*** shaohe_feng has joined #openstack-meeting-alt03:43
*** shaohe_feng has quit IRC03:53
*** zhongjun_ has quit IRC03:53
*** shaohe_feng has joined #openstack-meeting-alt03:53
*** zhongjun_ has joined #openstack-meeting-alt03:53
*** IlyaG has joined #openstack-meeting-alt03:59
*** shaohe_feng has quit IRC04:03
*** shaohe_feng has joined #openstack-meeting-alt04:03
*** samP has joined #openstack-meeting-alt04:06
*** pgadiya has joined #openstack-meeting-alt04:11
*** mixos has quit IRC04:11
*** mixos has joined #openstack-meeting-alt04:11
*** shaohe_feng has quit IRC04:13
*** shaohe_feng has joined #openstack-meeting-alt04:13
*** IlyaG has quit IRC04:14
*** amotoki has quit IRC04:15
*** amotoki has joined #openstack-meeting-alt04:16
*** tango has joined #openstack-meeting-alt04:20
*** tango has quit IRC04:21
*** kzaitsev_mb has joined #openstack-meeting-alt04:22
*** yamamot__ has joined #openstack-meeting-alt04:22
*** shaohe_feng has quit IRC04:24
*** shaohe_feng has joined #openstack-meeting-alt04:26
*** kzaitsev_mb has quit IRC04:27
*** Poornima has joined #openstack-meeting-alt04:30
*** irenab has quit IRC04:33
*** shaohe_feng has quit IRC04:34
*** shaohe_feng has joined #openstack-meeting-alt04:36
*** salv-orlando has joined #openstack-meeting-alt04:36
*** shaohe_feng has quit IRC04:44
*** shaohe_feng has joined #openstack-meeting-alt04:45
*** salv-orlando has quit IRC04:45
*** Liuqing has joined #openstack-meeting-alt04:53
*** shaohe_feng has quit IRC04:54
*** shaohe_feng has joined #openstack-meeting-alt04:54
*** mtanino has quit IRC04:58
*** Nikolay_St has quit IRC05:00
*** shaohe_feng has quit IRC05:05
*** shaohe_feng has joined #openstack-meeting-alt05:05
*** shaohe_feng has quit IRC05:15
*** shaohe_feng has joined #openstack-meeting-alt05:16
*** rcernin has joined #openstack-meeting-alt05:16
*** sridharg has joined #openstack-meeting-alt05:20
*** lpetrut has joined #openstack-meeting-alt05:20
*** rcernin has quit IRC05:21
*** shaohe_feng has quit IRC05:25
*** shaohe_feng has joined #openstack-meeting-alt05:26
*** zhurong has quit IRC05:31
*** tango has joined #openstack-meeting-alt05:31
*** zhurong has joined #openstack-meeting-alt05:32
*** irenab has joined #openstack-meeting-alt05:34
*** akaszuba has joined #openstack-meeting-alt05:35
*** shaohe_feng has quit IRC05:35
*** shaohe_feng has joined #openstack-meeting-alt05:36
*** rcernin has joined #openstack-meeting-alt05:38
*** samP has quit IRC05:42
*** shaohe_feng has quit IRC05:46
*** samP has joined #openstack-meeting-alt05:46
*** shaohe_feng has joined #openstack-meeting-alt05:47
*** amotoki_ has joined #openstack-meeting-alt05:53
*** amotoki has quit IRC05:54
*** shaohe_feng has quit IRC05:56
*** mikelk has joined #openstack-meeting-alt05:56
*** shaohe_feng has joined #openstack-meeting-alt05:57
*** reedip__ has quit IRC06:00
*** apetrich_ has joined #openstack-meeting-alt06:02
*** salv-orlando has joined #openstack-meeting-alt06:02
*** wangqun_ has joined #openstack-meeting-alt06:03
*** shu-mutou-AFK is now known as shu-mutou06:04
*** wangqun has quit IRC06:04
*** shaohe_feng has quit IRC06:06
*** shaohe_feng has joined #openstack-meeting-alt06:07
*** salv-orlando has quit IRC06:08
*** sheel has joined #openstack-meeting-alt06:12
*** shaohe_feng has quit IRC06:16
*** shaohe_feng has joined #openstack-meeting-alt06:17
*** lpetrut has quit IRC06:20
*** shashank_hegde has quit IRC06:21
*** kzaitsev_mb has joined #openstack-meeting-alt06:23
*** salv-orlando has joined #openstack-meeting-alt06:25
*** shashank_hegde has joined #openstack-meeting-alt06:26
*** reedip__ has joined #openstack-meeting-alt06:26
*** shaohe_feng has quit IRC06:27
*** shaohe_feng has joined #openstack-meeting-alt06:27
*** anilvenkata has joined #openstack-meeting-alt06:28
*** kzaitsev_mb has quit IRC06:28
*** yuanying has quit IRC06:30
*** paul-carlton1 has joined #openstack-meeting-alt06:31
*** wangqun_ has quit IRC06:32
*** wangqun_ has joined #openstack-meeting-alt06:32
*** kszukielojc has joined #openstack-meeting-alt06:33
*** wangqun__ has joined #openstack-meeting-alt06:34
*** wangqun_ has quit IRC06:36
*** shaohe_feng has quit IRC06:37
*** shaohe_feng has joined #openstack-meeting-alt06:38
*** tfukushima has joined #openstack-meeting-alt06:41
*** shaohe_feng has quit IRC06:47
*** shaohe_feng has joined #openstack-meeting-alt06:48
*** shaohe_feng has quit IRC06:57
*** amotoki_ is now known as amotoki06:58
*** shaohe_feng has joined #openstack-meeting-alt06:58
*** Sukhdev has quit IRC07:00
*** tango has quit IRC07:02
*** shaohe_feng has quit IRC07:08
*** shaohe_feng has joined #openstack-meeting-alt07:08
*** dukhlov has joined #openstack-meeting-alt07:16
*** shaohe_feng has quit IRC07:18
*** shaohe_feng has joined #openstack-meeting-alt07:19
*** dukhlov has quit IRC07:22
*** Nikolay_St has joined #openstack-meeting-alt07:23
*** kzaitsev_mb has joined #openstack-meeting-alt07:24
*** jtomasek has joined #openstack-meeting-alt07:26
*** dukhlov has joined #openstack-meeting-alt07:26
*** bana_k has quit IRC07:28
*** shaohe_feng has quit IRC07:28
*** shaohe_feng has joined #openstack-meeting-alt07:29
*** Liuqing has quit IRC07:29
*** kzaitsev_mb has quit IRC07:29
*** jschwarz has joined #openstack-meeting-alt07:31
*** mickeys_ has joined #openstack-meeting-alt07:32
*** ihrachys has joined #openstack-meeting-alt07:32
*** lpetrut has joined #openstack-meeting-alt07:32
*** yuanying has joined #openstack-meeting-alt07:34
*** Liuqing has joined #openstack-meeting-alt07:36
*** shaohe_feng has quit IRC07:38
*** shaohe_feng has joined #openstack-meeting-alt07:39
*** shashank_hegde has quit IRC07:40
*** yuanying has quit IRC07:42
*** yuanying has joined #openstack-meeting-alt07:42
*** ddmitriev has quit IRC07:43
*** yuanying has quit IRC07:43
*** mickeys_ has quit IRC07:44
*** mickeys has joined #openstack-meeting-alt07:45
*** shashank_hegde has joined #openstack-meeting-alt07:48
*** shaohe_feng has quit IRC07:49
*** mickeys has quit IRC07:49
*** shaohe_feng has joined #openstack-meeting-alt07:49
*** numans has joined #openstack-meeting-alt07:51
*** ddmitriev has joined #openstack-meeting-alt07:52
*** dshakhray has joined #openstack-meeting-alt07:54
*** shaohe_feng has quit IRC07:59
*** shaohe_feng has joined #openstack-meeting-alt07:59
*** lpetrut has quit IRC08:01
*** amotoki has quit IRC08:03
*** paul-carlton1 has quit IRC08:03
*** tango has joined #openstack-meeting-alt08:03
*** tango has quit IRC08:05
*** yuanying has joined #openstack-meeting-alt08:08
*** shaohe_feng has quit IRC08:09
*** shaohe_feng has joined #openstack-meeting-alt08:10
*** kertis has joined #openstack-meeting-alt08:10
*** amotoki has joined #openstack-meeting-alt08:11
*** salv-orlando has quit IRC08:11
*** zhurong has quit IRC08:12
*** zhurong has joined #openstack-meeting-alt08:12
*** markvoelker has joined #openstack-meeting-alt08:15
*** zhurong has quit IRC08:16
*** zhurong has joined #openstack-meeting-alt08:17
*** shaohe_feng has quit IRC08:19
*** shaohe_feng has joined #openstack-meeting-alt08:22
*** markvoelker has quit IRC08:23
*** markvoelker has joined #openstack-meeting-alt08:24
*** dukhlov has quit IRC08:24
*** kzaitsev_mb has joined #openstack-meeting-alt08:25
*** dosaboy has quit IRC08:26
*** amotoki has quit IRC08:27
*** mixos has quit IRC08:28
*** shaohe_feng has quit IRC08:30
*** kzaitsev_mb has quit IRC08:30
*** shaohe_feng has joined #openstack-meeting-alt08:30
*** shashank_hegde has quit IRC08:33
*** dosaboy has joined #openstack-meeting-alt08:36
*** kzaitsev_mb has joined #openstack-meeting-alt08:36
*** Poornima has quit IRC08:37
*** shaohe_feng has quit IRC08:40
*** paul-carlton1 has joined #openstack-meeting-alt08:40
*** shaohe_feng has joined #openstack-meeting-alt08:40
*** HeOS has joined #openstack-meeting-alt08:43
*** derekh has joined #openstack-meeting-alt08:45
*** amotoki has joined #openstack-meeting-alt08:46
*** Poornima has joined #openstack-meeting-alt08:47
*** MarkBaker has joined #openstack-meeting-alt08:48
*** panda has quit IRC08:48
*** panda has joined #openstack-meeting-alt08:48
*** sgotliv_ has joined #openstack-meeting-alt08:49
*** shaohe_feng has quit IRC08:50
*** shaohe_feng has joined #openstack-meeting-alt08:50
*** sgotliv has quit IRC08:52
*** nadya has joined #openstack-meeting-alt08:53
*** shu-mutou is now known as shu-mutou-AFK08:58
*** kzaitsev_mb has quit IRC08:59
*** shaohe_feng has quit IRC09:00
*** neiljerram has joined #openstack-meeting-alt09:01
*** kzaitsev_mb has joined #openstack-meeting-alt09:03
*** shaohe_feng has joined #openstack-meeting-alt09:05
*** dukhlov has joined #openstack-meeting-alt09:05
*** kzaitsev_mb has quit IRC09:09
*** amotoki has quit IRC09:10
*** shaohe_feng has quit IRC09:11
*** shaohe_feng has joined #openstack-meeting-alt09:11
*** yuanying has quit IRC09:14
*** dukhlov has quit IRC09:16
*** neiljerram has quit IRC09:17
*** shaohe_feng has quit IRC09:21
*** shaohe_feng has joined #openstack-meeting-alt09:21
*** neiljerram has joined #openstack-meeting-alt09:22
*** ihrachys has quit IRC09:24
*** reldan has joined #openstack-meeting-alt09:25
*** lpetrut has joined #openstack-meeting-alt09:27
*** ihrachys has joined #openstack-meeting-alt09:28
*** shaohe_feng has quit IRC09:31
*** shaohe_feng has joined #openstack-meeting-alt09:32
*** lpetrut1 has joined #openstack-meeting-alt09:33
*** lpetrut has quit IRC09:34
*** lpetrut1 is now known as lpetrut09:34
*** shaohe_feng has quit IRC09:41
*** MarkBaker has quit IRC09:41
*** shaohe_feng has joined #openstack-meeting-alt09:42
*** samP has quit IRC09:43
*** MarkBaker has joined #openstack-meeting-alt09:44
*** shaohe_feng has quit IRC09:52
*** MarkBaker has quit IRC09:54
*** shaohe_feng has joined #openstack-meeting-alt09:56
*** daemontool has joined #openstack-meeting-alt10:01
*** shaohe_feng has quit IRC10:02
*** shaohe_feng has joined #openstack-meeting-alt10:02
*** kzaitsev_mb has joined #openstack-meeting-alt10:08
*** zhurong has quit IRC10:09
*** shaohe_feng has quit IRC10:12
*** yuanying has joined #openstack-meeting-alt10:13
*** tango has joined #openstack-meeting-alt10:14
*** amotoki has joined #openstack-meeting-alt10:14
*** tango has quit IRC10:14
*** shaohe_feng has joined #openstack-meeting-alt10:15
*** sdague has joined #openstack-meeting-alt10:18
*** samP has joined #openstack-meeting-alt10:19
*** yamamot__ has quit IRC10:19
*** tfukushima has quit IRC10:22
*** shaohe_feng has quit IRC10:22
*** shaohe_feng has joined #openstack-meeting-alt10:23
*** samP has quit IRC10:24
*** tfukushima has joined #openstack-meeting-alt10:24
*** shaohe_feng has quit IRC10:33
*** dukhlov has joined #openstack-meeting-alt10:33
*** shaohe_feng has joined #openstack-meeting-alt10:34
*** salv-orlando has joined #openstack-meeting-alt10:34
*** paul-carlton1 has quit IRC10:36
*** salv-orlando has quit IRC10:39
*** shaohe_feng has quit IRC10:43
*** wangqun__ has quit IRC10:43
*** shaohe_feng has joined #openstack-meeting-alt10:44
*** salv-orlando has joined #openstack-meeting-alt10:48
*** weshay has quit IRC10:50
*** anilvenkata has quit IRC10:53
*** shaohe_feng has quit IRC10:53
*** shaohe_feng has joined #openstack-meeting-alt10:54
*** gcb has joined #openstack-meeting-alt10:57
*** yuanying has quit IRC11:01
*** MarkBaker has joined #openstack-meeting-alt11:03
*** shaohe_feng has quit IRC11:03
*** nadya has quit IRC11:04
*** shaohe_feng has joined #openstack-meeting-alt11:04
*** yuanying has joined #openstack-meeting-alt11:05
*** tango has joined #openstack-meeting-alt11:06
*** markvoelker has quit IRC11:06
*** tango has quit IRC11:07
*** shaohe_feng has quit IRC11:14
*** shaohe_feng has joined #openstack-meeting-alt11:14
*** jtomasek_ has joined #openstack-meeting-alt11:14
*** pnavarro has joined #openstack-meeting-alt11:15
*** kei_yama has quit IRC11:15
*** yamamoto_ has joined #openstack-meeting-alt11:18
*** leakypipes is now known as jaypipes11:22
*** shaohe_feng has quit IRC11:24
*** shaohe_feng has joined #openstack-meeting-alt11:24
*** numans has quit IRC11:25
*** pnavarro has quit IRC11:27
*** salv-orlando has quit IRC11:27
*** dshakhray has quit IRC11:29
*** tpsilva has joined #openstack-meeting-alt11:31
*** shaohe_feng has quit IRC11:34
*** shaohe_feng has joined #openstack-meeting-alt11:35
*** salv-orlando has joined #openstack-meeting-alt11:35
*** zhurong has joined #openstack-meeting-alt11:36
*** amotoki has quit IRC11:36
*** pnavarro has joined #openstack-meeting-alt11:36
*** jtomasek_ has quit IRC11:38
*** anilvenkata has joined #openstack-meeting-alt11:41
*** weshay has joined #openstack-meeting-alt11:42
*** Nikolay_St has left #openstack-meeting-alt11:42
*** shaohe_feng has quit IRC11:44
*** shaohe_feng has joined #openstack-meeting-alt11:45
*** nadya has joined #openstack-meeting-alt11:47
*** tango has joined #openstack-meeting-alt11:47
*** tango has quit IRC11:49
*** yuanying has quit IRC11:49
*** kzaitsev_mb has quit IRC11:50
*** amotoki has joined #openstack-meeting-alt11:52
*** yuanying has joined #openstack-meeting-alt11:53
*** shaohe_feng has quit IRC11:55
*** sdake has joined #openstack-meeting-alt11:55
*** shaohe_feng has joined #openstack-meeting-alt11:55
*** mtanino has joined #openstack-meeting-alt11:57
*** dprince has joined #openstack-meeting-alt11:59
*** Akis_ has quit IRC12:00
*** jschwarz has quit IRC12:01
*** shaohe_feng has quit IRC12:05
*** shaohe_feng has joined #openstack-meeting-alt12:06
*** mugsie has joined #openstack-meeting-alt12:06
*** zhurong has quit IRC12:07
*** amotoki has quit IRC12:08
*** markvoelker has joined #openstack-meeting-alt12:08
*** numans has joined #openstack-meeting-alt12:09
*** kzaitsev_mb has joined #openstack-meeting-alt12:10
*** jtomasek_ has joined #openstack-meeting-alt12:10
*** sdake has quit IRC12:10
*** amotoki has joined #openstack-meeting-alt12:10
*** markvoelker has quit IRC12:13
*** shaohe_feng has quit IRC12:15
*** shaohe_feng has joined #openstack-meeting-alt12:15
*** jschwarz has joined #openstack-meeting-alt12:16
*** yuanying has quit IRC12:17
*** amotoki has quit IRC12:17
*** tango has joined #openstack-meeting-alt12:20
*** myoung|lunch has joined #openstack-meeting-alt12:21
*** tango has quit IRC12:21
*** Ravikiran_K has joined #openstack-meeting-alt12:22
*** coolsvap has quit IRC12:22
*** coolsvap has joined #openstack-meeting-alt12:22
*** shaohe_feng has quit IRC12:25
*** jschwarz_ has joined #openstack-meeting-alt12:26
*** shaohe_feng has joined #openstack-meeting-alt12:26
*** yamamoto_ has quit IRC12:27
*** yamamoto_ has joined #openstack-meeting-alt12:29
*** jschwarz has quit IRC12:30
*** pnavarro has quit IRC12:32
*** dukhlov has quit IRC12:32
*** coolsvap has quit IRC12:33
*** dukhlov has joined #openstack-meeting-alt12:33
*** shaohe_feng has quit IRC12:36
*** shaohe_feng has joined #openstack-meeting-alt12:36
*** pgadiya has quit IRC12:37
*** kzaitsev_mb has quit IRC12:38
*** julim has joined #openstack-meeting-alt12:40
*** yamamoto_ has quit IRC12:40
*** tango has joined #openstack-meeting-alt12:40
*** kzaitsev_mb has joined #openstack-meeting-alt12:42
*** tango has quit IRC12:42
*** Poornima has quit IRC12:42
*** yamamoto_ has joined #openstack-meeting-alt12:46
*** shaohe_feng has quit IRC12:46
*** shaohe_feng has joined #openstack-meeting-alt12:47
*** yamamoto_ has quit IRC12:47
*** pgadiya has joined #openstack-meeting-alt12:49
*** yamamoto has joined #openstack-meeting-alt12:50
*** amrith is now known as _amrith_12:53
*** ninag has joined #openstack-meeting-alt12:54
*** shaohe_feng has quit IRC12:56
*** shaohe_feng has joined #openstack-meeting-alt12:57
*** myoung|lunch has quit IRC12:58
*** yamamoto has quit IRC12:58
*** brucet has joined #openstack-meeting-alt12:58
*** houming has quit IRC12:58
*** yamamoto has joined #openstack-meeting-alt12:59
*** markvoelker has joined #openstack-meeting-alt13:00
*** ddieterly has joined #openstack-meeting-alt13:02
*** egallen has joined #openstack-meeting-alt13:03
*** pgadiya has quit IRC13:04
*** markvoelker has quit IRC13:04
*** markvoelker has joined #openstack-meeting-alt13:04
*** xyang1 has joined #openstack-meeting-alt13:06
*** shaohe_feng has quit IRC13:06
*** brucet has quit IRC13:06
*** shaohe_feng has joined #openstack-meeting-alt13:07
*** mtanino has quit IRC13:08
*** baoli has joined #openstack-meeting-alt13:09
*** brucet has joined #openstack-meeting-alt13:14
*** shaohe_feng has quit IRC13:17
*** shaohe_feng has joined #openstack-meeting-alt13:17
*** irenab has quit IRC13:18
*** tpepper has joined #openstack-meeting-alt13:22
*** reedip__ has quit IRC13:23
*** ddieterly has quit IRC13:23
*** Liuqing has quit IRC13:23
*** dukhlov has quit IRC13:27
*** shaohe_feng has quit IRC13:27
*** sneti__ has joined #openstack-meeting-alt13:27
*** zz_dimtruck is now known as dimtruck13:27
*** shaohe_feng has joined #openstack-meeting-alt13:27
*** ddieterly has joined #openstack-meeting-alt13:28
*** markvoelker has quit IRC13:28
*** takashin has joined #openstack-meeting-alt13:30
*** jprovazn has quit IRC13:30
*** ddieterly has quit IRC13:31
*** pgadiya has joined #openstack-meeting-alt13:32
*** pgadiya has quit IRC13:34
*** esker has quit IRC13:34
*** cknight has joined #openstack-meeting-alt13:35
*** coreyob_ has joined #openstack-meeting-alt13:35
*** tonytan4ever has joined #openstack-meeting-alt13:35
*** coreyob has quit IRC13:36
*** shaohe_feng has quit IRC13:37
*** shaohe_feng has joined #openstack-meeting-alt13:37
*** dukhlov has joined #openstack-meeting-alt13:38
*** dukhlov has quit IRC13:39
*** Liuqing has joined #openstack-meeting-alt13:42
*** dukhlov has joined #openstack-meeting-alt13:43
*** dukhlov has quit IRC13:43
*** jecarey has joined #openstack-meeting-alt13:45
*** sheel has quit IRC13:45
*** muralia_ has joined #openstack-meeting-alt13:45
*** muralia_ has left #openstack-meeting-alt13:46
*** jecarey_ has joined #openstack-meeting-alt13:46
*** shaohe_feng has quit IRC13:47
*** amitgandhinz has joined #openstack-meeting-alt13:48
*** shaohe_feng has joined #openstack-meeting-alt13:48
*** muralia has quit IRC13:48
*** cknight has quit IRC13:49
*** jecarey has quit IRC13:49
*** yamamoto has quit IRC13:49
*** spzala has joined #openstack-meeting-alt13:50
*** dukhlov has joined #openstack-meeting-alt13:52
*** dimtruck is now known as zz_dimtruck13:52
*** cdent has joined #openstack-meeting-alt13:54
*** mriedem has joined #openstack-meeting-alt13:54
*** banix has joined #openstack-meeting-alt13:54
*** _amrith_ is now known as amrith13:54
*** sneti__ has quit IRC13:54
*** mtanino has joined #openstack-meeting-alt13:54
*** mlavalle has joined #openstack-meeting-alt13:57
*** shaohe_feng has quit IRC13:58
*** shaohe_feng has joined #openstack-meeting-alt13:58
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon May 16 14:00:21 2016 UTC and is due to finish in 60 minutes.  The chair is edleafe. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova_scheduler)"14:00
openstackThe meeting name has been set to 'nova_scheduler'14:00
edleafeAnyone around?14:00
jaypipeso/14:00
Yingxino/14:00
mlavalleo/14:00
mriedemo/14:00
cdento/14:01
edleafe#topic Specs14:01
*** openstack changes topic to "Specs (Meeting topic: nova_scheduler)"14:01
doffmo/14:01
edleafeI listed several on the agenda14:01
*** reldan has quit IRC14:01
edleafehttps://wiki.openstack.org/wiki/Meetings/NovaScheduler14:01
edleafeAnyone want to discuss anything in particular about them?14:01
mriedemon the logging one https://review.openstack.org/#/c/306647/14:02
edleafe(except "please review!!")14:02
jaypipeswould be great to get agreement on the g-r-p spec.14:02
mriedemi see a comment was made, something like, if we're going to do x, let's go all out and making it super complicated!14:02
*** _prad_ has joined #openstack-meeting-alt14:02
jaypipesedleafe: cdent is pushing a new rev on that shortly.14:02
edleafemriedem: that would have been me14:02
cdentI can push it now14:02
mriedemi'd prefer to keep the logging spec simple to start14:02
*** yamamoto has joined #openstack-meeting-alt14:02
mriedemand build on it14:02
jaypipesmriedem: ++14:03
* alex_xu waves late14:03
mriedemrather than 10 new config options for logging14:03
edleafeI was thinking one new config vs. two14:03
johnthetubaguyI have pushed up a WIP spec for the distinct-subset-shard-scheduler spec (partly as requested by doffm) https://review.openstack.org/#/c/313519/14:03
doffmAwesome.14:03
*** coolsvap has joined #openstack-meeting-alt14:03
*** sigmavirus24_awa is now known as sigmavirus2414:04
Yingxinmriedem: maybe the recursive filters can help the logging simple, but it makes code harder to be understand as jaypipes says.14:05
johnthetubaguyI tried to answer questions on the ordered filter scheduler spec (https://review.openstack.org/#/c/256323/) but not sure if I managed to answer the questions there14:05
edleafeSo on the logging, we're definitely not going to offer extra logging except for NoValidHost?14:05
*** sshnaidm has quit IRC14:05
johnthetubaguymriedem: +1 on keeping that logging simple to start with14:05
cdentokay, new version of g-r-p just pushed https://review.openstack.org/300176 was a bit rushed, so many need some tweaks but I believe it represents the latest agreements14:05
Yingxincdent: great14:05
johnthetubaguyedleafe: it just seems like we should improve NoValidHost first, then see where we are14:05
edleafecdent: cool - will review after the meeting14:05
mriedemedleafe: i'd need to read back through it in detail to get it in my head again, but it started out pretty simple and then there were some asks for additional things, and it seems to have grown into a bit of a monster14:06
edleafejohnthetubaguy: sure14:06
edleafemriedem: originally it was to scratch a single itch. Other itches were then revealed14:06
mriedemsure, but14:06
mriedemthat first itch is the bloody one14:07
mriedemall scabby and gooey14:07
johnthetubaguyewww14:07
*** xenogear has joined #openstack-meeting-alt14:07
* edleafe is getting hungry for breakfast all of a sudden...14:07
mriedemheh14:07
*** sshnaidm has joined #openstack-meeting-alt14:07
mriedemanyway, my 2 cents, i can read through it again, but might be a few hours14:07
*** shaohe_feng has quit IRC14:08
edleafeMy only concern is that if we plan on adding the "success" case, we should lay the groundwork for that, rather than rip things up later to fit it14:08
*** sdake has joined #openstack-meeting-alt14:08
*** doug-fish has joined #openstack-meeting-alt14:08
edleafeWe don't have to implement it in one shot, of course14:08
johnthetubaguyI hate the idea of the success case, as I have seen that suck performance out of the system14:08
*** shaohe_feng has joined #openstack-meeting-alt14:08
johnthetubaguyI assume we did something dumb to cause that, but either way, it worries me14:09
edleafejohnthetubaguy: heh, yeah14:09
mriedemyeah, idk, generally i'm not in favor or building for future requirements14:09
edleafeBut it was an ops guy asking for it.14:09
mriedem*of building14:09
mriedemsure, but i don't see that as a recurring ask from several ops people over time14:09
mriedemlike figuring out the novalidhost thing14:09
mriedemlet's put it this way,14:10
*** zz_dimtruck is now known as dimtruck14:10
mriedemthe more complicated this is, the less chance of anything getting done in newton14:10
mriedembecause if it's too complicated, it probably won't get review attention14:10
edleafesure, makes sense14:10
*** cknight has joined #openstack-meeting-alt14:10
mriedemjust something to keep in mind - i don't know how easy it would be to add the success stuff later because i don't know what cfriesen is implementing14:11
*** yamamoto has quit IRC14:11
edleafejaypipes: cdent: anything we need to discuss on g-r-p?14:11
edleafei.e., any points of contention?14:11
cdentedleafe: we've been round several blocks on the form of the api14:12
jaypipesedleafe: I'm reviewing it now. cdent just pushed a new rev.14:12
*** ddieterly has joined #openstack-meeting-alt14:12
cdentthe current form is supposed to reflect the latest discussions between jay and me14:12
edleafeAlright, anything else to discuss for specs?14:12
cdentI think what needs to happen there is that we agree on the spirit and just get on with it...14:13
edleafecdent: but blue would be much prettier!14:13
edleafeanyways14:13
*** jecarey_ has quit IRC14:13
* cdent bombs edleafe's shed14:13
edleafe#topic Reviews14:13
*** openstack changes topic to "Reviews (Meeting topic: nova_scheduler)"14:13
edleafeNobody added any to the schedule14:14
johnthetubaguyso I guess I worry about the lack of attention the non-priority specs are getting, but we need to focus on the other stuff, so thats fair enough14:14
edleafejohnthetubaguy: anything in particular?14:14
johnthetubaguyedleafe: well my two specs, obviously ;) but one is to make things easier to configure, the other is needed for us to delete cells v1 (at least in my head)14:15
jaypipesjohnthetubaguy: which one makes things easier to configure?14:15
mriedemcdent: jaypipes: keep in mind on the grp spec no one replied to alaski's question in ps12 https://review.openstack.org/#/c/300176/12/specs/newton/approved/generic-resource-pools.rst@21414:15
johnthetubaguyjaypipes: the one you don't like: https://review.openstack.org/#/c/256323/714:16
johnthetubaguyjaypipes: its intent is to make this easier to configure, I just can't ever get the weighers to do what I want14:16
*** anilvenkata has quit IRC14:16
jaypipesjohnthetubaguy: yeah, the whole weigher system is a turd.14:17
jaypipesjohnthetubaguy: the problem I see with your two proposals is that they build *more* complexity into the existing system. I don't see them simplifying anything.14:17
johnthetubaguyjaypipes: this seems like a way we could deprecate and remove that, but I don't want it to slow down other progress either14:17
*** amitgandhinz has quit IRC14:17
*** tango has joined #openstack-meeting-alt14:18
*** Kuwagata has joined #openstack-meeting-alt14:18
*** amitgandhinz has joined #openstack-meeting-alt14:18
doffmjohnthetubaguy: Longer discussion... but I think we could make this simpler if we separated out packing and spreading.14:18
johnthetubaguyjaypipes: so the idea is you have a list of yes/no decisions, some are required, some are just a preference, in a defined order14:18
doffmRather than negative weights everywhere.14:18
*** shaohe_feng has quit IRC14:18
*** spotz_zzz is now known as spotz14:18
doffmUse your routing spec to take different requests to a packing scheduler if needed.14:18
johnthetubaguydoffm: yeah, I like that, I added in alternatives for a follow up14:18
*** shaohe_feng has joined #openstack-meeting-alt14:18
jaypipesjohnthetubaguy: on the sharded scheduler one, I'm all for partitioning (I proposed code for the scheduler over 2 years ago that added support for a scheduler process to only consider a subset of hosts). The issue is that your spec adds more complexity to the existing scheduler design by making placement policies and decision making different per subset of hosts.14:19
edleafejaypipes: wouldn't that be preferable? Each scheduler does its own thing its own way?14:19
johnthetubaguyjaypipes: right, its what cells v1 gives us today14:19
jaypipesedleafe: no.14:20
jaypipesjohnthetubaguy: it's a hack today, and basing scheduler decisions on the flavor would be a hack again.14:20
*** esker has joined #openstack-meeting-alt14:20
johnthetubaguyso on metal, ssd and non-ssd get different rules, each one gets its own nova-scheduler process (or set of processes)14:20
*** esker has quit IRC14:20
johnthetubaguyjaypipes: it seems to follow the pattern of how people think about their fleet, so it seems natural, granted their may be a better way to do it14:21
*** esker has joined #openstack-meeting-alt14:21
johnthetubaguyit does conflate two things here though14:21
johnthetubaguydifferent sets of hosts having different scheduling policies14:21
jaypipesjohnthetubaguy: the *process by which a placement decision is reached* is the same, though. It's just "find me hosts that have X resources available and Y capabilities". The same scheduler process/code should handle all scheduling decisions. Use partitioning/sharding to reduce the number of compute hosts that each scheduler process considers in order to increase the scale of the scheduler.14:22
johnthetubaguysharding of the hosts, along lines you already shard your capacity planning14:22
tpepperthere's ops interest in simplified/unified scheduling.  people may think of their fleet in disjoint terms because the different openstack schedulers force them to.14:22
tpepperjaypipes: +114:22
johnthetubaguyjaypipes: yeah, thats true14:22
doffmjaypipes: So are you OK with different scheduler algorithms for different host subsets? But not OK with different processes?14:22
johnthetubaguyjaypipes: let me add that comment and re-work it14:22
johnthetubaguyjaypipes: I actually like the separation, but it does seem wrong to require it14:23
jaypipesjohnthetubaguy: now... for some kinds of *requests*, there may be a case for having totally different schedulers. For instance, if one request required a bunch of network and/or storage affinity policies vs. another request that just wants a simple X resources Y capabilities, you could make the case for routing the two requests to two different schedulers entirely.14:23
jaypipesdoffm: ^^14:24
edleafejaypipes: so all schedulers have to have the same filters/weighers/whatever enabled?14:24
johnthetubaguyjaypipes: I am thinking onmetal vs virt, FWIW14:24
*** stingaci has quit IRC14:24
*** yamamoto has joined #openstack-meeting-alt14:24
*** haleyb has quit IRC14:24
doffmGotta go, meeting. Will read backlog later and leave comments on relevent specs. :)14:24
*** markvoelker has joined #openstack-meeting-alt14:25
jaypipesjohnthetubaguy: on metal vs. virt is the EXACT same request. It's a request for a simple amount of X resources having Y capabilities. There's nothing special about the onmetal request vs. the virt one14:25
jaypipesjohnthetubaguy: just because the Nova compute_nodes table was hacked together with a (host, node) tuple just for Ironic/baremetal doesn't mean that the placement request is really any different.14:25
johnthetubaguyjaypipes: we have different sets of weighting preferences for each of those, but thats quite a specific use case14:26
*** kfarr has joined #openstack-meeting-alt14:26
jaypipesjohnthetubaguy: please elaborate on those differences.14:26
*** takashin_ has joined #openstack-meeting-alt14:26
edleafejohnthetubaguy: that's what I was thinking - different packing/spread needs14:26
jaypipesit would greatly help me understand the use case.14:26
jaypipesedleafe: you can't "pack" or "spread" bare metal nodes.14:26
jaypipesedleafe: the resource is indivisible.14:27
edleafejaypipes: that's just one type of sharding14:27
jaypipessorry, not understanding you...14:27
edleafeI meant in general14:27
*** sneti__ has joined #openstack-meeting-alt14:27
*** edtubill has joined #openstack-meeting-alt14:27
tpepperedleafe: are you thinking in terms of chassis packing?  eg: I've rented onmetal nodes from ya'll that are little blade form factors which arguably share chassis resources...14:27
edleafejaypipes: different host groups might require different approaches14:28
jaypipesmriedem: on alaski's question, I will answer him on IRC. It's a smple misunderstanding it looks like.14:28
johnthetubaguyjaypipes: well baremetal is 1:1, so most of the virt worries are irrelevant, I would have to double check if there are things the other way around14:28
*** takashin has quit IRC14:28
*** shaohe_feng has quit IRC14:28
tpeppererr meant johnthetubaguy ^^ not edleafe14:28
jaypipesjohnthetubaguy: sorry, I'm not following you. The fact that Ironic nodes are indivisible resources doesn't change the fact that a scheduling decision for virt vs. bare metal flavors is made the same way.14:29
johnthetubaguyjaypipes: in reality we have different teams controlling the config right now, which is handy, so I would have to go digging to work out what the other folks do14:29
edleafejaypipes: so the only gain would be that each scheduler has to consider fewer hosts?14:29
johnthetubaguyjaypipes: well if you keep windows and linux VMs on separate boxes, it doesn't matter for onmetal14:29
*** markvoelker has quit IRC14:30
johnthetubaguykeeping tenants apart from each other, similarly irrelevant14:30
jaypipesedleafe: "only gain"? :) err, yes, the gain from partitioning is dramatically increased concurrency/scale due to allowing different scheduler processes to operate on fewer hosts.14:30
*** Leom has joined #openstack-meeting-alt14:31
*** shaohe_feng has joined #openstack-meeting-alt14:31
*** Leom has quit IRC14:32
*** sridharg has quit IRC14:32
*** yamamoto has quit IRC14:32
*** sneti__ has quit IRC14:33
edleafejaypipes: it seems that the DB filtering would do that more simply and with reduced complexity14:33
edleafei.e., a request for bare metal would return drastically fewer hosts14:33
jaypipesedleafe: a combination of DB side filtering and partitioning each scheduler process to only look at some shard of hosts gets the best scale in my placement-bench harness results.14:33
edleafeok, let's continue the discussion on the spec14:34
johnthetubaguythats back to the one process vs multiple process, for me the big thing is where to shard, not how14:34
edleafeAre there any reviews we need to discuss?14:34
*** yamamoto has joined #openstack-meeting-alt14:34
johnthetubaguyjaypipes: the idea with my suggested shard, is it has no capacity planning worries, which is tricky when you run mostly full14:35
johnthetubaguybut anyways, lets take this back to the spec review14:35
johnthetubaguys/no/no additional/14:35
*** vinaypotluri has joined #openstack-meeting-alt14:35
*** sarob has joined #openstack-meeting-alt14:36
edleafe#topic Opens14:36
*** openstack changes topic to "Opens (Meeting topic: nova_scheduler)"14:36
edleafeSo anything else before we get back to reviewing specs?14:36
cdentno sir14:36
edleafeOK, then, here are 23 minutes of your time back14:37
edleafe#endmeeting14:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:37
openstackMeeting ended Mon May 16 14:37:25 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-05-16-14.00.html14:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-05-16-14.00.txt14:37
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2016/nova_scheduler.2016-05-16-14.00.log.html14:37
*** takashin_ has left #openstack-meeting-alt14:37
*** shaohe_feng has quit IRC14:39
*** shaohe_feng has joined #openstack-meeting-alt14:39
*** dprince has quit IRC14:42
*** kfarr has quit IRC14:42
*** irenab has joined #openstack-meeting-alt14:42
*** kfarr has joined #openstack-meeting-alt14:43
*** irenab has quit IRC14:43
*** stingaci has joined #openstack-meeting-alt14:43
*** kertis has quit IRC14:45
*** jprovazn has joined #openstack-meeting-alt14:47
*** noslzzp has joined #openstack-meeting-alt14:48
*** stingaci_ has joined #openstack-meeting-alt14:49
*** shaohe_feng has quit IRC14:49
*** salv-orlando has quit IRC14:49
*** amotoki has joined #openstack-meeting-alt14:49
*** shaohe_feng has joined #openstack-meeting-alt14:50
*** salv-orlando has joined #openstack-meeting-alt14:50
*** stingaci has quit IRC14:52
*** merooney has joined #openstack-meeting-alt14:53
*** merooney has quit IRC14:54
*** nadya has quit IRC14:54
*** nadya has joined #openstack-meeting-alt14:55
*** stingaci has joined #openstack-meeting-alt14:55
*** superdan is now known as dansmith14:56
*** Na3iL has joined #openstack-meeting-alt14:56
*** stingaci_ has quit IRC14:57
*** mlavalle has left #openstack-meeting-alt14:57
*** Ravikiran_K has quit IRC14:58
*** rmart04 has joined #openstack-meeting-alt14:59
*** jlibosva has joined #openstack-meeting-alt14:59
*** armax has joined #openstack-meeting-alt14:59
*** shaohe_feng has quit IRC14:59
*** nadya has quit IRC14:59
*** merooney has joined #openstack-meeting-alt14:59
*** ivc_ has joined #openstack-meeting-alt14:59
*** korzen has joined #openstack-meeting-alt14:59
*** fnaval has quit IRC15:00
*** esker has quit IRC15:00
ihrachys#startmeeting neutron_upgrades15:00
openstackMeeting started Mon May 16 15:00:31 2016 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
*** shaohe_feng has joined #openstack-meeting-alt15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"15:00
openstackThe meeting name has been set to 'neutron_upgrades'15:00
jlibosva\o15:00
johndperkinso/15:00
sc68calo/15:01
ihrachyshello everyone! I hope you enjoyed the lack of meetings lately.15:01
*** ninag has quit IRC15:01
*** julim has quit IRC15:01
sc68calno, I missed you all :(15:01
*** cdent has left #openstack-meeting-alt15:01
ihrachysI don't see some folks (rossella_s, korzen?)15:02
*** pcm_ has joined #openstack-meeting-alt15:02
korzenhello15:02
ihrachysthe previous meeting was supposed to occur, but then I guess some catastrophe happened :)15:02
pcm_cd vcode15:02
*** haleyb has joined #openstack-meeting-alt15:02
ihrachysso that's the 1st meeting after the summit15:02
* pcm_ wrong window...15:02
ihrachysI was off last two weeks, so probably you folks will need to fill us in15:03
*** prithiv has joined #openstack-meeting-alt15:03
-amotoki- is on train and may use fragile connection..15:03
ihrachysfirst, actions from the last meeting15:03
ihrachys#topic Actions from the last meeting15:03
*** openstack changes topic to "Actions from the last meeting (Meeting topic: neutron_upgrades)"15:03
*** julim has joined #openstack-meeting-alt15:03
*** ninag has joined #openstack-meeting-alt15:03
ihrachys"ihrachys to cancel next meetings in openstack-dev@"15:03
ihrachysnah, that one is boring. moving on15:03
*** dasm has joined #openstack-meeting-alt15:03
ihrachys"ihrachys to update wiki page with the check list for object adoption (object, database access code, API test coverage, ...)"15:04
ihrachysok, for that one, I started some draft check list of 'things to cover when doing object transition'15:04
ihrachys#link https://wiki.openstack.org/wiki/Meetings/Neutron-Upgrades-Subteam#Object_adoption_check_list15:04
*** saisriki- has joined #openstack-meeting-alt15:04
*** sneti has quit IRC15:04
*** ninag_ has joined #openstack-meeting-alt15:04
*** tonytan4ever has quit IRC15:04
ihrachysI suggest everyone who did some work for objects to go thru the check list and validate that all of it is covered15:04
ihrachysI also hope that people will fill in gaps in the list15:05
ihrachystl;dr it's not enough to land object class to claim a resource done. it's just first step.15:05
*** ninag__ has joined #openstack-meeting-alt15:05
*** saisrikiran has quit IRC15:05
*** mriedem has left #openstack-meeting-alt15:06
* ihrachys gives 1 min to complete reading and complain about the list15:06
*** mixos has joined #openstack-meeting-alt15:06
korzenthe wiki steps looks nice15:07
ihrachysok, 1 min ended. I guess everyone is on board with it.15:07
*** mixos_ has joined #openstack-meeting-alt15:07
ihrachysgenerally, if folks have cycles, at this point I suggest we spend them on API test coverage since it's going to block a lot of objects.15:08
*** ninag has quit IRC15:08
ihrachysso ask me how to help, and I will point you to some tests and patches that we need to push15:08
ihrachysthat would be something along the lines of https://review.openstack.org/#/c/306272/15:08
*** sneti has joined #openstack-meeting-alt15:09
* ihrachys needs to get back to the patch asap15:09
*** ninag_ has quit IRC15:09
ihrachysok, let's cover usual topics15:09
ihrachys#topic Partial Multinode Grenade15:09
*** openstack changes topic to "Partial Multinode Grenade (Meeting topic: neutron_upgrades)"15:09
*** shaohe_feng has quit IRC15:09
ihrachyssc68cal: would you mind filling us about where we stand with it?15:09
sc68calJust got +A'd a couple minutes ago, working its way through the gate15:10
sc68calhttps://review.openstack.org/#/c/299843/15:10
*** ninag__ has quit IRC15:10
*** shaohe_feng has joined #openstack-meeting-alt15:10
ihrachysoh man.15:10
korzensc68cal, great!15:10
ihrachysit's thrilling and scary at the same time15:10
ihrachysdo we have the very latest result?15:10
sc68calI have to find my notes - I spoke with armax last week and we put some stuff in an etherpad for the next steps15:10
sc68callet me dig up the etherpad link15:11
*** _prad_ is now known as pradk-15:11
ihrachysI hope it's not breaking :)15:11
*** merooney has quit IRC15:11
*** mixos has quit IRC15:11
sc68calfound it15:11
sc68calhttps://etherpad.openstack.org/p/neutron-multinode-jobs-newton15:11
ihrachysfyi non-voting jobs from the very latest patches seem succeeding15:12
ihrachyslooking at the link15:12
sc68cal#link https://etherpad.openstack.org/p/neutron-multinode-jobs-newton Newton multinode grenade next steps15:12
*** lennyb has joined #openstack-meeting-alt15:13
ihrachysI think it's a good list of things to follow up on15:13
*** fnaval has joined #openstack-meeting-alt15:13
ihrachysfor dvr, we have the job in check too15:13
*** rossella_s has joined #openstack-meeting-alt15:14
ihrachysas per grafana, the failure rate is the same as for non dvr15:15
ihrachys(and low)15:15
*** ddecapit has joined #openstack-meeting-alt15:15
*** Leom has joined #openstack-meeting-alt15:15
rossella_shi all, sorry for being late, I am actually off today but I thought I should join this :)15:15
korzenone improvement we need is to move dhcp and L3 our of primary node15:15
* ihrachys waves at rossella_s 15:15
korzenbut still using the 2 node setup15:16
ihrachyskorzen: please add to the etherpad15:16
*** Leom_ has joined #openstack-meeting-alt15:16
korzenihrachys, ok15:16
ihrachyssc68cal: do you take all of it, or you want someone to help you with it?15:17
sc68calI'm happy to have people join15:18
*** tpepper has left #openstack-meeting-alt15:18
ihrachysack15:18
ihrachys#topic Object implementation15:18
*** openstack changes topic to "Object implementation (Meeting topic: neutron_upgrades)"15:18
ihrachysgenerally, the topic of object adoption was raised on a design summit session15:19
ihrachysand the decision was made that new features are required to provide objects with them.15:19
ihrachysit's up to us folks to identify those patches without objects in flight though15:19
*** shaohe_feng has quit IRC15:20
ihrachysnote that we still need to do preparation work for features that are e.g. extending a resource15:20
*** Leom has quit IRC15:20
korzenit is good we have new OVO for vlan aware VMs: https://review.openstack.org/#/c/31041015:20
ihrachyswe don't expect other developers to implement objects just to add a small attribute somewhere15:20
*** shaohe_feng has joined #openstack-meeting-alt15:21
ihrachyskorzen: that's cool15:21
*** jecarey has joined #openstack-meeting-alt15:21
ihrachysapart from general notes above, I don't have specifics15:21
ihrachyskorzen: rossella_s: anything to mention?15:21
rossella_sihrachys, I don't have anything15:22
korzenrossella_s, what is the status of port OVO?15:22
korzenis it close to merge?15:22
rossella_skorzen, nope it's not, unfortunately I didn't have time to work on it lately15:23
ihrachysrossella_s: I guess it's also blocked by API tests for sorting/pagination?15:23
korzenwe lost Martin, is there anyone to help rossella_s?15:23
*** akaszuba has quit IRC15:23
ihrachysrossella_s: or we talk about object itself, without adoption?15:23
rossella_sihrachys, that too15:23
*** myoung|lunch has joined #openstack-meeting-alt15:23
rossella_sihrachys, the object without adoption15:23
ihrachysok, from my side, I will concentrate on getting API layer ready for objects.15:23
rossella_sihrachys, great!15:24
ihrachysI hope in parallel we'll get the object itself in shape so that we can meet each other at the adoption cross road quicker15:24
korzenI would love to see any review on Subnet OVO: https://review.openstack.org/#/c/26427315:25
*** yamahata has joined #openstack-meeting-alt15:25
rossella_skorzen, will do...I was partly off and partly focusing on other stuff after the summit, sorry for that15:25
korzenand Network OVO as well ;) https://review.openstack.org/#/c/26965815:25
johndperkinsI've got a couple ovo patches out that just need reviews as well15:25
johndperkinshttps://review.openstack.org/#/c/304862/ and https://review.openstack.org/#/c/307969/ are network/router15:25
ihrachysjohndperkins: ok15:26
ihrachyskorzen: we don't have adoption patches for those, right?15:26
korzenihrachys, nope, not yet15:26
ihrachyskorzen: would be cool to try that and see what's missing15:26
korzenihrachys, yes, I will do this this/next week15:27
*** Prem_ has joined #openstack-meeting-alt15:27
ihrachysjohndperkins: would be cool to switch focus of the team to bits missing for existing objects.15:28
*** amotoki has quit IRC15:28
korzenjohndperkins, could you or some from OSIC help with port object?15:28
johndperkinskorzen: absolutely15:28
dasmihrachys: korzen: which objects require attention?15:29
korzendasm, port OVO15:29
dasmkorzen: just this?15:29
*** stingaci has quit IRC15:29
ihrachysdasm: I think at this point it's more about getting API layer to the point where we can start switching first class resources to objects. API layer work is needed to support sorting/pagination. that's one thing. I bet when we start adopting more in the db code, we will hit more missing bits.15:30
*** shaohe_feng has quit IRC15:30
dasmihrachys: mhm. fair enough15:30
ihrachysdasm: we have patches in flight, but they will probably need some love.15:30
*** doug-fish has quit IRC15:30
dasmihrachys: do we have one place where links are stored?15:30
ihrachysdasm: fyi I plan to tackle some of it this week, but since I am dug under emails from 3weeks, some help would always be welcome.15:30
ihrachysdasm: ovo topic15:30
dasmihrachys: gotcha15:31
ihrachyshttps://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:ovo15:31
dasmihrachys: i think *a lot* of patches require "some love" :D15:31
*** shaohe_feng has joined #openstack-meeting-alt15:31
*** esker has joined #openstack-meeting-alt15:31
ihrachysyes, and we better not increase their number until they are in better shape15:31
*** bana_k has joined #openstack-meeting-alt15:31
*** esker has quit IRC15:31
dasmunderstandable. OSIC people are involved, like johndperkins, so we think we can try to help decrease the number.15:32
*** esker has joined #openstack-meeting-alt15:32
ihrachysok. I guess interested folks will sync after the meeting if needed on specific pieces to share.15:32
korzenrossella_s, do you have any action items that dasm and OSIC can take right away?15:32
rossella_sihrachys, regarding the port ovo?15:33
korzenrossella_s, yes15:33
*** ddecapit has quit IRC15:34
rossella_sihrachys, just update the patch15:34
*** ansmith has joined #openstack-meeting-alt15:34
korzenrossella_s, like this one: https://review.openstack.org/#/c/253641/ ?15:34
ihrachysrossella_s: I assume you won't have time for it this week and folks are safe to take it?15:34
*** harlowja_at_home has joined #openstack-meeting-alt15:34
rossella_sihrachys, yes this week for sure15:35
ihrachysack. great to know.15:35
dasmrossella_s: ok. good to know.15:35
rossella_sihrachys, I will try to free up later15:35
rossella_sanyone interested please ping me15:35
ihrachysok, I guess we have something to roll with on that topic.15:36
ihrachys#topic Open discussion15:36
*** openstack changes topic to "Open discussion (Meeting topic: neutron_upgrades)"15:36
korzenhttps://review.openstack.org/287756 Integrate the port allowed address pairs VersionedObject in Neutron this also need some love15:36
*** prithiv has quit IRC15:36
ihrachysI don't have anything more to talk, feel free to raise more stuff now15:36
korzenI have one open15:36
*** ddecapit has joined #openstack-meeting-alt15:36
korzentenant_id -> project_id renaming15:36
dasmkorzen: ++15:37
korzenshould we handle the project_id right now?15:37
*** egallen has quit IRC15:37
korzenor wait until dasm work will be ready?15:37
*** prithiv has joined #openstack-meeting-alt15:37
*** jschwarz_ has quit IRC15:37
dasmbasically, spec is not merged yet: https://review.openstack.org/#/c/257362/15:37
*** prithiv has quit IRC15:37
korzenI would prefer to go with project_id from the beggining15:37
dasmbut most of the things are there. so in some time, we will also need to use project_id15:37
ihrachyskorzen: for new objects? fine. as long as they write in consistent way (same field) in db15:38
ihrachyskorzen: note that e.g. qos policy has tenant_id, so we would need a switch anyway.15:39
korzenI have updated the Subnet OVO to use the project_id https://review.openstack.org/#/c/264273/24/neutron/objects/subnet.py@15115:39
ihrachyskorzen: that's nice. if dasm goes with alembic, he will just need to remove the translation15:39
dasmihrachys: yes.15:40
*** shaohe_feng has quit IRC15:40
ihrachyskorzen: thanks for looking into the future15:40
ihrachysanything more to discuss?15:41
*** shaohe_feng has joined #openstack-meeting-alt15:41
ihrachysor everyone can have 20 mins till next meeting slot? :)15:41
korzenI have introduced the null testing in: https://review.openstack.org/#/c/30844115:41
korzenstill have issue with cmp not present in Python315:41
korzendo you think it is worth continueing?15:42
ihrachysI am not sure what's the goal there. I will need some time to actually read it thru.15:43
*** diazjf has joined #openstack-meeting-alt15:43
*** snackewm has joined #openstack-meeting-alt15:43
korzenmain reason was to have UT covered for getting nulls for generated values15:43
korzenit can fast test if null can be set in DB15:43
*** Liuqing has quit IRC15:43
korzenand for example currentlu15:44
*** esker has quit IRC15:44
korzencorrently, when we do not set the property in OVO, the exceptin is raised15:44
*** pcm_ has left #openstack-meeting-alt15:44
korzenand we are not able to set null fetched from DB in OVO15:44
*** rmart04 has quit IRC15:45
ihrachyskorzen: is "null from db" case different from "no value in db at all"?15:45
korzenihrachys, not sure right now15:47
ihrachysok, I will need to take a closer look. maybe playing with code will help me to understand the issue.15:47
korzenwe can for example set the gatway to null15:48
*** Sukhdev has joined #openstack-meeting-alt15:48
korzengateway*15:48
korzenwhen defining the subnet via CLI15:48
korzenwe can continue in patch review15:49
ihrachysaye15:49
dasmihrachys: one more question about: https://review.openstack.org/#/c/306272/915:50
*** bana_k has quit IRC15:50
dasmihrachys: do you need any help with it?15:50
dasmit seems to be blocking a lot of stuff.15:50
ihrachysdasm: that's the patch I was going to get right after I handle all critical emails I have since 3weeks.15:50
*** shaohe_feng has quit IRC15:50
ihrachysdasm: but we could start building more resource tests on top of it already, right?15:51
*** MeganR has joined #openstack-meeting-alt15:51
dasmihrachys: True.15:51
*** shaohe_feng has joined #openstack-meeting-alt15:51
ihrachysdasm: so let's say I handle the patch 1st priority, and people start building more on top while it's still in review. it should not change much itself, just need to fix gate and other nits.15:51
dasmok. fair enough :)15:52
*** _sarob has joined #openstack-meeting-alt15:53
ihrachysok, I guess that's what we have right now15:53
ihrachyslet's use those 7 mins for good15:53
ihrachys#endmeeting15:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:54
openstackMeeting ended Mon May 16 15:54:02 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-05-16-15.00.html15:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-05-16-15.00.txt15:54
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2016/neutron_upgrades.2016-05-16-15.00.log.html15:54
korzenthanks for disscussion, bye15:54
*** nadya has joined #openstack-meeting-alt15:55
*** kgiusti has joined #openstack-meeting-alt15:56
*** sheel has joined #openstack-meeting-alt15:56
*** sarob has quit IRC15:56
*** vishwanathj has joined #openstack-meeting-alt15:56
harlowja_at_home#startmeeting oslo16:00
openstackMeeting started Mon May 16 16:00:02 2016 UTC and is due to finish in 60 minutes.  The chair is harlowja_at_home. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: oslo)"16:00
openstackThe meeting name has been set to 'oslo'16:00
harlowja_at_homecourtesy ping for amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dims, dougwig16:00
harlowja_at_homecourtesy ping for e0ne, flaper87, garyk, gcb, GheRivero, haypo, ihrachyshka, jd__16:00
harlowja_at_homecourtesy ping for jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, Nakato16:00
harlowja_at_homecourtesy ping for ozamiatin, rbradfor, redrobot, rpodolyaka, sergmelikyan, sileht, spamaps, sreshetnyak16:00
harlowja_at_homecourtesy ping for sreshetnyak, stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek16:00
ihrachyso/16:00
nikhilo/16:00
harlowja_at_homebtw for people that want to be in that ping list16:00
rpodolyakao/16:00
rbradforo/ \o16:00
amrith./16:00
kgiustio/16:00
harlowja_at_homei just updated https://wiki.openstack.org/wiki/Meetings/Oslo#Ping_script with a crappy script, adjustments welcome (or add yor own)16:00
*** jungleboyj has joined #openstack-meeting-alt16:00
jungleboyjo/16:00
*** shaohe_feng has quit IRC16:01
bknudsonI have to get to the airport so won't be here.16:01
harlowja_at_homek16:01
harlowja_at_home#topic Red flags for/from liaisons16:01
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"16:01
flaper87o/16:01
bknudsonnone that I know of for keystone16:02
jungleboyjNothing from Cinder.16:02
harlowja_at_homeso i believe taskflow release caused some *existing* bugs to show up in some folks code (cinder, octavia)16:02
amrithnone for Trove.16:02
ihrachysI am not aware of any for neutron, but hey, I am just back from 2week post-summit vacation...16:02
harlowja_at_homejungleboyj, do u know if those cinder + taskflow things got fixed up16:02
*** shaohe_feng has joined #openstack-meeting-alt16:04
redroboto/ ish16:04
harlowja_at_homeihrachys, thx seems like mostly issue free :-P16:04
jungleboyjharlowja_at_home: Yeah, I saw there was a patch pushed up for that at the end of last week while I was out.16:04
harlowja_at_homek16:04
harlowja_at_homecool16:04
*** julim has quit IRC16:04
jungleboyjharlowja_at_home: So, I think we got beyond it for now.16:04
*** ddecapit has quit IRC16:04
amrithharlowja_at_home, heads-up on an eminent red-flag. I'm going to rake up the isotime() issue next week.16:04
harlowja_at_homejungleboyj, sweet16:05
harlowja_at_homeamrith, lol16:05
harlowja_at_homeah the ye-olde isotime16:05
harlowja_at_homejd__, loves that one16:05
*** Ravikiran_K has joined #openstack-meeting-alt16:05
harlowja_at_home#topic Releases for newton16:05
*** stingaci has joined #openstack-meeting-alt16:05
*** openstack changes topic to "Releases for newton (Meeting topic: oslo)"16:05
dhellmanno/16:05
harlowja_at_homeso I haven't gotten a new release of all the things out yet, but i'll work on that in a bit16:05
harlowja_at_homeanyone need anything to be released explicitly?16:06
*** julim has joined #openstack-meeting-alt16:06
harlowja_at_home(if not i'll just make a release for all oslo libs, and people can yell at me if its incorrect)16:06
rpodolyaka:)16:07
harlowja_at_home#topic Delimiter16:07
*** openstack changes topic to "Delimiter (Meeting topic: oslo)"16:07
nikhilo/16:07
harlowja_at_homenikhil, do u have some time to describe the whole thing here :)(16:08
* harlowja_at_home hands mic to nikhil 16:08
nikhilhere's the agenda item:16:08
nikhil     Discuss the home of quota (delimiter) library http://lists.openstack.org/pipermail/openstack-dev/2016-May/thread.html#9395916:08
*** egallen has joined #openstack-meeting-alt16:08
nikhilplease follow along the thread to know what exactly is happening here16:08
nikhilbut without going divergent into things, I can give a tl;dr;16:08
harlowja_at_homesure :)16:08
nikhilthere are 2 school of thoughts:16:08
*** gyee has joined #openstack-meeting-alt16:09
nikhil1) people who think this is a cross project library but the problem domain and solutions are not well defined hence it cant be x-prj yet16:09
nikhil2) another set of people who think that if we need to make it a successful x-prj library then we need it in a umbrealla that is already a cross project established domain16:09
*** mikelk has quit IRC16:10
nikhilSO, to established the right apporach here16:10
nikhilI need your vetted input on what are the tradeoffs to put this in oslo16:10
nikhilwhat can be the good things (and of course I shouldn't be asking here :-)) what would be the warnings?16:11
harlowja_at_homeeverything is good when its in oslo :-P16:11
*** shaohe_feng has quit IRC16:11
*** Swami has joined #openstack-meeting-alt16:11
dhellmannI think I fall in group 2, and I suggested creating an oslo.quota lib repo to host the work as a sub-project in oslo. I'm not entirely opposed to the project being stand-alone though.16:11
dhellmannI just think the road to adoption will be longer that way.16:11
*** shaohe_feng has joined #openstack-meeting-alt16:12
nikhil(context: both the school of thoughts have pretty experienced and influencial people)16:12
dhellmannwe already have well-established processes for subteams like with messaging, db, and policy so we have the pattern of setting up a team like this16:12
*** ninag has joined #openstack-meeting-alt16:12
harlowja_at_homeso if we as a group have it be a sub-project nikhil it doesn't guarantee adoption (i assume this is known)16:12
*** ninag has quit IRC16:12
harlowja_at_homejust a word of warning there16:12
harlowja_at_homeadoption still hard (believe me, i know)16:12
dhellmannyeah, that's true -- there are no guarantees either way16:12
dimsdhellmann : since we tried this oslo.quota before and there's a lot of resistance from folks who have that "feature" i thought it would be better to do it this way as a standalone lib16:13
SpamapSWhat's the reason to not have it in oslo?16:13
SpamapSoslo is all of the common "business logic" that we share in OpenStack, isn't it?16:13
dhellmanndims : there seems to be a lot of support for sharing something now, though? what did we actually have to share in the past?16:13
dhellmannSpamapS : that's more or less the idea16:14
amrithdims, I believe that resistence in the past was more because of what the quota library sought to do and how. I believe that more consensus is being built in this process and therefore the odds of adoption may (and I stress may) be higher.16:14
harlowja_at_homeone reason i can think of (others may disagree) is limited people in oslo to maintain it (if the sub-team goes away) SpamapS16:14
*** kbespalov has joined #openstack-meeting-alt16:14
dimsamrith : we can always adopt the library when it has some legs.. like os-profiler16:14
dhellmannharlowja_at_home : that's true. we have the same risk for any piece of code anywhere in openstack.16:14
harlowja_at_homedhellmann, good point16:14
SpamapSharlowja_at_home: I do understand that. However, if it is standalone and the team fades away, the projects that adopt it are still in deep water, but without a known team to help them migrate off it while it is deprecated.16:15
*** salv-orl_ has joined #openstack-meeting-alt16:15
dhellmanndims : that's true. I think this team is doing a better job of collaborating than the os-profiler team did in its early days, though.16:15
harlowja_at_homeSpamapS, understood16:15
dimsdhellmann : yep16:15
SpamapSIs it being done as a total new thing, or did they start with a forklift from some other project's quota system?16:16
harlowja_at_home#link https://github.com/openstack/delimiter (if people want to look through the code that exists so far)16:16
dimsSpamapS : i'd give them a bit more time to come up with something that works with early adopters16:16
harlowja_at_homeyes, most of that code i put up over the weekend, lol16:16
nikhilSpamapS: a bit of both16:16
nikhilbut the roadmap is still undefined16:16
SpamapSif it is not a forklift, then I have a 3rd option: start over. Forklift from the best implementation. Otherwise we end up in the Neutron space again.16:16
nikhiland we do not know who is going to work on this long term16:17
dimsSpamapS : this is starting over16:17
amrithdims, that is true too.16:17
harlowja_at_homeSpamapS, i believe its mostly starting over (but doing it strategically/smartly)16:17
nikhilharlowja_at_home: correct16:17
nikhilthis is more strategic effort16:17
*** ninag has joined #openstack-meeting-alt16:17
harlowja_at_homeright16:17
nikhiland we need some space for that to happen16:18
harlowja_at_homeright16:18
*** ninag has quit IRC16:18
dimsnikhil : if we don't see good progress on early adopter project and or if the team loses steam, we don't want oslo core team to be burdened as well16:18
SpamapSSo, put me down as somebody who is very interested in cross-project harmony, and who does not want to see another Neutron situation (I know this is a library and not a service, but the fact remains that whole new efforts are far more painful than incremental migrations)16:18
nikhilpossibly not have a brand name tagged from the get go (mostly my worry)16:18
nikhildims: I agree and share the sentiment16:18
*** salv-orlando has quit IRC16:18
dimsAt the moment the team has a space and talking to whole bunch of folks and iterating, i'd keep that going and revisit later personally16:18
*** paul-carlton1 has joined #openstack-meeting-alt16:19
amrithdims makes a convincing case. I'll +1 his suggestion.16:19
dimsthere's no rush in my mind to make it "oslo". i'd prefer to have something working first16:19
nikhilAlso, I do not want some people like (say the liaison from PWG) to stop contributing just because the space belongs more to developers16:19
harlowja_at_homei'm personally also fine with that, like we can check-in a couple of weeks from now, see where things are at16:19
dimsOslo is great at having very few people maintain a lot of code...not for this kickstart16:19
dhellmannthe main question in my mind is how are you going to know it works if it's called experimental and  being run not as an official project -- who is signed up to adopt what is built?16:20
SpamapSdims: the point at which to push for a decision on namespace is probably when a project starts adopting it.16:20
harlowja_at_homei think glance signed up :-P16:20
dimsSpamapS : yep16:20
nikhilalso, say I have a good intern working on it, she might be a little bit apprehensive on contributing to something like oslo with the experts16:20
dimsdhellmann : Nova too16:20
SpamapSKeep the blast radius for a namespace change to the early adopters.16:20
harlowja_at_homenikhil, we don't bite :-P16:20
nikhil:)16:20
dimslots of feeback from jaypipes and others16:20
dimsand amrith is keeping them honest16:20
nikhildhellmann: I have a bunch of people in glance who don't want to import code just because it's oslo too16:21
nikhilso we have all sorts of ideas in openstack!16:21
*** brucet has quit IRC16:21
*** shaohe_feng has quit IRC16:21
nikhilI do not know for sure who is going to sign up16:21
harlowja_at_homei wrote a skeleton, my job is done :-P16:21
nikhiland that's the learning process, I think16:21
*** shashank_hegde has joined #openstack-meeting-alt16:21
dhellmanngreat, so one of the reasons for doing this separately is because folks don't want to collaborate with the oslo team? happy days.16:21
amrithi'm concerned about the comment that there may be people who won't import code just because it is oslo but that is a diversion16:22
*** shaohe_feng has joined #openstack-meeting-alt16:22
harlowja_at_homeya, let16:22
harlowja_at_home*lets table that for now16:22
amriththat (to put it mildly) sucks.16:22
*** MarkBaker has quit IRC16:22
nikhilI agree16:22
harlowja_at_homenikhil, so how about we have a check-up in 2 weeks, see where things are at?16:22
harlowja_at_homeu don't have to cough or anything ...16:22
nikhiland I spend my 10% enerygy fighting that sort of ideas16:23
nikhilenergy*16:23
*** julim has quit IRC16:23
nikhilso I do not know what the right ways are16:23
dimsnikhil : if they prefer hangouts or other forms of communication to make them comfortable, let us know16:23
nikhilI am trying to be honest on my worries here16:23
harlowja_at_homethx :)16:23
nikhiland being open about getting feedback on tradeoffs16:23
SpamapSThat's weird because, they could.. join.. the oslo team..16:24
nikhildims: whatever makes the cross project experts comfortable16:24
SpamapSExcept it's an exclusive club and we only accept non-nerf-herders right? ;)16:24
dhellmannnikhil : the only thing that would be different about this project if it was an oslo lib is the name, and the fact that the existing oslo-core team would also have +2 on the repo.16:24
* SpamapS joins the oslo team as a "we" in that sentence whenever it suits him16:24
nikhilall I worry about is the end goal - I do not care how we achieve it (we need  a successful quota implementation in openstack)16:24
dimsSpamapS : ++ :)16:24
dimsnikhil : agree.16:25
nikhildhellmann: I am okay with oslo or non-oslo as long as we won't be spending another 2 months discussing the weirness in the spec16:26
nikhilthat was 1)16:26
nikhil2) we are okay to put this on "probation"16:26
harlowja_at_homesoooo, checkup in 2 weeks ok with folks? that's somewhat my preference, let's get people to show up to code stuff (besides myself) and see where it goes a little (or that's what i feel)16:26
nikhil3) there's freedome to adopt different approaches and no issues with api of the lib version breaks16:26
dhellmannharlowja_at_home : yeah, that's fine. If the team doesn't want to be part of oslo, we can spend our energy elsewhere.16:26
harlowja_at_homeincase anyone wants to review16:27
nikhil4) we do not have a complete re-implmentation of this lib in oslo just because it's not the oslo way16:27
harlowja_at_home#link https://review.openstack.org/#/q/project:openstack/delimiter16:27
dimsdhellmann : i think of this as a POC, let them get some work done, see if they can make folks like amrith, jaypipes etc comfortable with the impl and they can apply for governance16:27
nikhil5) we test this in production before making it non on probation16:27
* nikhil done16:27
dhellmannnikhil : you will find, as we have learned and could help you work around, that projects adopting this library and trying to maintain CD compatibility will be upset if you start making lots of API changes that break their test systems.16:27
*** lpetrut has quit IRC16:27
dhellmannthat's regardless of whether it's official, or who runs it, or what program it's in16:28
*** _sarob has quit IRC16:28
dimsdhellmann : ++16:28
*** derekh has quit IRC16:28
amrithnikhil, I think it is important (for the reasons that dhellmann just brought up) that we spend more time now and get the API right.16:28
dimsamrith : ++16:28
dhellmannso if you're not prepared to deal with that situation, I think you need a new plan for getting the library into production16:28
amrithFWIW, that's one of the reasons I disagree with jaypipes proposed API. We agree about the implementation now but the API is still a concern to me.16:28
nikhilamrith: correct and that's the end goal I am talking about as well16:29
amrithit will be time well spent if we can get that API acceptable to more, at this stage.16:29
harlowja_at_homeapi i put up amrith @ https://github.com/openstack/delimiter/blob/master/delimiter/engine.py#L20 (feel free to change it)16:29
*** merooney has joined #openstack-meeting-alt16:30
harlowja_at_homemain engine access point would be @ https://github.com/openstack/delimiter/blob/master/delimiter/__init__.py#L2316:30
*** shashank_hegde has quit IRC16:30
nikhilharlowja_at_home: I expect >10 changes tbh (once people from diff projects actually start giving input)16:30
harlowja_at_homenikhil, likely :)16:30
* amrith mumbles something about main entry point being a comment :)16:31
nikhilplus we still haven't settled on the types of drivers16:31
harlowja_at_homeright, work to be done16:31
*** shaohe_feng has quit IRC16:31
nikhilyep, there's lot to go forward on here!16:31
amrithnikhil, what do you mean about types of drivers? Should we take it offline?16:31
amrithi.e. this is the #oslo meeting16:32
amrithnot the #quota meeting16:32
*** kbespalov has quit IRC16:32
harlowja_at_home;)16:32
nikhilamrith: yes, please16:32
amrithok, 2pm today16:32
harlowja_at_homeok, soooo let's re-connect in a couple of weeks on delimiter, i think that's sane thing to do16:32
*** shaohe_feng has joined #openstack-meeting-alt16:32
harlowja_at_homeseem ok to folks?16:32
amrith+116:33
dims++16:33
amrithok, fine. +=116:33
nikhilI am happy to reconnect wherever to get everyone on the same page16:34
harlowja_at_homecool16:34
*** kevo has quit IRC16:34
*** julim has joined #openstack-meeting-alt16:34
harlowja_at_home#topic Stuck reviews/specs16:35
*** openstack changes topic to "Stuck reviews/specs (Meeting topic: oslo)"16:35
harlowja_at_homeany stuck reviews or specs that we can try to focus on for folks?16:35
harlowja_at_home#link http://bit.ly/1oDpFQ5 (all oslo reviews)16:36
harlowja_at_homespecs @ https://review.openstack.org/#/q/project:openstack/oslo-specs16:36
harlowja_at_homeguess everyone getting everything reviewed then, nice :)16:37
kgiustiharlowja_at_home: what did I mess up https://review.openstack.org/#/c/314603/16:37
kgiustiharlowja_at_home: it doesn't appear in the spec list16:37
harlowja_at_homehttps://review.openstack.org/#/q/project:openstack/oslo-specs ?16:38
kgiustiharlowja_at_home: at least on that short url, that is16:38
harlowja_at_homeah16:38
*** tango has quit IRC16:38
harlowja_at_homemaybe gotta update the short-url16:38
harlowja_at_homeya, weird whats up with that16:38
harlowja_at_homei blame gerrit16:38
* kgiusti is good with that :)16:38
harlowja_at_homei'll regenerate the short-link a little later, maybe something wonky with it16:39
harlowja_at_homeor ya, evil gerrit, lol16:39
kgiustiJust offhand - when is the feature freeze date for oslo.messaging features in newton?16:40
rbradforharlowja_at_home, re specs, working around the context policy things,  https://review.openstack.org/#/c/290907/  has been discussed. I think it's impact needs input from other projects16:40
harlowja_at_homelet's see here http://releases.openstack.org/newton/schedule.html16:40
rbradfor- Standardize Context Arguments spec,  especially if projects abuse putting name values into id releated fields.16:40
amrithI have a q about this spec16:40
*** IlyaG has joined #openstack-meeting-alt16:41
amrithWill this change the oslo.context object as it is today?16:41
amrithTrove currently uses it and sends it in an RPC message to guests.16:41
amrithif the object changes, that'd be bad for Trove.16:41
harlowja_at_homekgiusti, i believe thats 'Aug 29-02' for this16:41
*** rossella_s has quit IRC16:41
*** shaohe_feng has quit IRC16:42
kgiustiharlowja_at_home: looks like it's going to be a busy summer....16:42
harlowja_at_homerbradfor, agreed, it'd nice if some liasons could look at 290907 (for those that use oslo.context)16:42
amrithrbradfor, harlowja_at_home ... question abotu that spec ^^16:42
*** kzaitsev_mb has quit IRC16:42
*** shaohe_feng has joined #openstack-meeting-alt16:42
rbradforamrith, well it's about providing a backwards compatible solution, (at least one full cycle), but moving from the N projects that subclass just to rename an attribute from the the context values16:42
rbradforamrith, I'd like to hear of all problems, so we don't cause issues, such as with Trove16:43
amrithrbradfor, I will chat with you about this.16:43
amrithonce I understand the spec better16:43
amriththanks for the heads up16:43
harlowja_at_homerbradfor, if u want me to send out a ML email, i'd be willing to as well16:43
harlowja_at_homeget people to start thinking about that ...16:44
rbradforamrith, trove does none of the mess we are trying to improve on16:44
harlowja_at_home(people that may not be here that is)16:44
rbradforharlowja_at_home, ML will do.16:44
amrithrbradfor, give us time :)16:44
amrithrbradfor, don't challenge us :)16:44
harlowja_at_home#topic Open discussion16:45
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"16:45
rbradforamrith, it's just a spec, I wrote it over 2 months ago, and it will probably be a long time before enough people comment on it, so time is on your side16:45
harlowja_at_homelol16:45
amrithha16:45
amrithlet me go buy a lottery ticket16:45
harlowja_at_hometime is on your side for those as well16:45
kgiustibut the odds sure as heck are not16:46
harlowja_at_home;)16:46
amrithkgiusti, that's true ...16:46
*** merooney has quit IRC16:47
harlowja_at_homeanything else anyone wants to bring up?16:47
harlowja_at_homerbradfor, when we gonna start that blog stuffs ;)16:47
* dims runs and hides16:47
rbradforharlowja_at_home, yeah, I keep dreading that question.16:47
harlowja_at_homelol16:47
rbradforI know it's important for Oslo and all16:47
*** panda has quit IRC16:48
rbradforbut I proposed a plan and made a schedule, so time to man up16:48
harlowja_at_homei'd be up for trying at least16:48
*** panda has joined #openstack-meeting-alt16:48
harlowja_at_homeif it doesn't work out,that's ok16:48
rbradforharlowja_at_home, let me dig up my half done kick of post and run it by you Wednesday16:49
harlowja_at_homecool16:49
rbradforharlowja_at_home, thanks for bringing up the topic16:49
harlowja_at_homenp, at least we can try, that's what matters to me16:49
* harlowja_at_home needs to hire a ghost-writer, ha16:50
rbradforyou can't ghost write technical, e.g. code blocks.16:50
harlowja_at_homehmmm, good point, lol16:51
*** timirnich has quit IRC16:51
*** shaohe_feng has quit IRC16:52
*** timirnich has joined #openstack-meeting-alt16:52
harlowja_at_homeokie dokie, back to your regular scheduled programming in 316:52
harlowja_at_home216:52
harlowja_at_home116:52
amriththanks harlowja_at_home16:52
harlowja_at_homenp :)16:52
harlowja_at_home#endmeeting16:53
* amrith gets anxious. what comes after 1?16:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:53
openstackMeeting ended Mon May 16 16:53:03 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-05-16-16.00.html16:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-05-16-16.00.txt16:53
harlowja_at_homelol16:53
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2016/oslo.2016-05-16-16.00.log.html16:53
*** shaohe_feng has joined #openstack-meeting-alt16:53
*** kgiusti has left #openstack-meeting-alt16:53
harlowja_at_home016:53
harlowja_at_homethen -116:53
harlowja_at_home;)16:53
*** merooney has joined #openstack-meeting-alt16:53
harlowja_at_homesee ya'll in #openstack-oslo16:53
harlowja_at_homebbiab16:53
*** diazjf has quit IRC16:53
*** harlowja_at_home has quit IRC16:53
*** IlyaG has quit IRC16:54
*** dukhlov has quit IRC16:54
*** bana_k has joined #openstack-meeting-alt16:55
*** ihrachys has quit IRC16:58
*** cknight has quit IRC16:58
*** cknight has joined #openstack-meeting-alt16:58
*** jlibosva has left #openstack-meeting-alt17:00
*** shashank_hegde has joined #openstack-meeting-alt17:00
*** shaohe_feng has quit IRC17:02
*** shaohe_feng has joined #openstack-meeting-alt17:03
*** iyamahat has joined #openstack-meeting-alt17:03
*** jungleboyj has quit IRC17:05
*** cknight1 has joined #openstack-meeting-alt17:05
*** merooney has quit IRC17:05
*** stingaci has quit IRC17:06
*** pnavarro has joined #openstack-meeting-alt17:07
*** stingaci has joined #openstack-meeting-alt17:07
*** cknight has quit IRC17:07
*** bana_k has quit IRC17:08
*** doug-fish has joined #openstack-meeting-alt17:08
*** nadya has quit IRC17:09
*** ninag has joined #openstack-meeting-alt17:10
*** doug-fis_ has joined #openstack-meeting-alt17:10
*** ninag_ has joined #openstack-meeting-alt17:11
*** coolsvap has quit IRC17:11
*** Sukhdev has quit IRC17:11
*** ninag_ has quit IRC17:11
*** doug-fi__ has joined #openstack-meeting-alt17:12
*** shaohe_feng has quit IRC17:12
*** david-lyle_ has quit IRC17:12
*** doug-fish has quit IRC17:13
*** david-lyle has joined #openstack-meeting-alt17:13
*** esker has joined #openstack-meeting-alt17:14
*** shaohe_feng has joined #openstack-meeting-alt17:14
*** esker has quit IRC17:14
*** kevo has joined #openstack-meeting-alt17:14
*** doug-fis_ has quit IRC17:14
*** esker has joined #openstack-meeting-alt17:14
*** ninag has quit IRC17:15
*** doug-fi__ has quit IRC17:16
*** asaprykin has quit IRC17:17
*** rockstar has quit IRC17:17
*** paul-carlton1 has quit IRC17:17
*** amitgandhinz has quit IRC17:17
*** paul-carlton1 has joined #openstack-meeting-alt17:18
*** yamamoto has quit IRC17:18
*** tango has joined #openstack-meeting-alt17:18
*** yamamoto has joined #openstack-meeting-alt17:18
*** tango has quit IRC17:19
*** yamamoto has quit IRC17:19
*** tango has joined #openstack-meeting-alt17:19
*** amitgandhinz has joined #openstack-meeting-alt17:21
*** asaprykin has joined #openstack-meeting-alt17:21
*** tonytan4ever has joined #openstack-meeting-alt17:21
*** yamamoto has joined #openstack-meeting-alt17:21
*** shashank_hegde has quit IRC17:22
*** rockstar has joined #openstack-meeting-alt17:22
*** shaohe_feng has quit IRC17:23
*** ninag has joined #openstack-meeting-alt17:23
*** shaohe_feng has joined #openstack-meeting-alt17:23
*** tango has quit IRC17:24
*** bana_k has joined #openstack-meeting-alt17:24
*** coolsvap has joined #openstack-meeting-alt17:25
*** dims_ has joined #openstack-meeting-alt17:25
*** dims has quit IRC17:26
*** ddieterly is now known as ddieterly[away]17:28
*** jungleboyj has joined #openstack-meeting-alt17:28
*** piet has joined #openstack-meeting-alt17:29
*** mfedosin has joined #openstack-meeting-alt17:29
*** enriquetaso has joined #openstack-meeting-alt17:29
mfedosinCourtesy meeting reminder ( #openstack-meeting-alt ): nikhil_k, ativelkov, mfedosin, docaedo, dshakhray, kfox111, kairat, nikhil, sudipto17:30
*** anush has joined #openstack-meeting-alt17:30
*** coolsvap_ has joined #openstack-meeting-alt17:30
docaedoo/17:32
nikhilo/17:32
* docaedo is on a plane so connectivity is no guarantee :)17:32
*** anush has quit IRC17:32
mfedosinhey!17:32
*** doug-fish has joined #openstack-meeting-alt17:32
mfedosin#startmeeting glare17:32
openstackMeeting started Mon May 16 17:32:59 2016 UTC and is due to finish in 60 minutes.  The chair is mfedosin. Information about MeetBot at http://wiki.debian.org/MeetBot.17:33
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:33
*** openstack changes topic to " (Meeting topic: glare)"17:33
*** anush has joined #openstack-meeting-alt17:33
openstackThe meeting name has been set to 'glare'17:33
*** esker has quit IRC17:33
mfedosin#topic agenda17:33
*** shaohe_feng has quit IRC17:33
*** openstack changes topic to "agenda (Meeting topic: glare)"17:33
mfedosin#link https://etherpad.openstack.org/p/glance-artifacts-sub-team-meeting-agenda17:33
mfedosin#topic Updates17:33
*** openstack changes topic to "Updates (Meeting topic: glare)"17:33
*** jungleboyj has quit IRC17:34
*** shaohe_feng has joined #openstack-meeting-alt17:34
*** coolsvap has quit IRC17:34
mfedosinSo, I haven't been involved in Glare last two weeks17:34
mfedosinbut kairat and dshakray made a great work17:35
*** yamamoto has quit IRC17:35
mfedosinbefore the summit we defined a list of items that must be done before merging17:35
*** coolsvap_ is now known as coolsvap17:35
mfedosinthere were 11 points17:35
mfedosin10 of them are implemented17:35
docaedonice!17:35
mfedosinonly db is left17:35
mfedosinit lead to the fact that after some testing we are ready to merge it17:36
mfedosinI updated API spec in late April17:36
nikhilmfedosin: can I say something here?17:36
mfedosinsure17:36
nikhilso, the only way this will merge it soon is if people know what is being implemented and how17:37
nikhiland the way to do that is working upstream17:37
nikhilotherwise, we will again have last minute -1, -2s17:37
nikhilas people will not see things fit for some of the use cases17:37
nikhilSo, like I mentioned at the summit:17:37
mfedosinyeah, it was my next topic :)17:37
nikhilok, let's carry on for now. I can add comments later.17:38
*** doug-fish has quit IRC17:38
mfedosinfor sure we need to have good documentation17:38
nikhilmfedosin: that's not enough17:38
nikhilto be really honest17:38
mfedosinwhat else?17:38
nikhilI can share the plan to "how to do it" upstream later with you17:39
nikhilyou should carry on with your agenda for now. I may take 15-20 mins for that.17:39
mfedosinokay, great17:39
mfedosinwe can talk later about "how to do it in upstream"17:40
nikhilk17:40
*** paul-carlton1 has quit IRC17:40
mfedosinon Wednesday we're going to have a meeting dedicated to final Glare API17:40
nikhilsend that notice to ML17:41
mfedosinwalk through the spec and update it if needed17:41
mfedosingood point, but I meant inner meeting17:41
nikhilmfedosin: from now on, no inner meetings please17:42
mfedosinbut upstream is good idea17:42
*** merooney has joined #openstack-meeting-alt17:42
mfedosinfor example, on Friday17:42
nikhilI think for a POC that's fine. but once the idea is in good shape, let's do the discussion 100% upstream17:42
mfedosinI'll send this email in ML17:42
nikhilk17:42
*** anush has quit IRC17:43
mfedosin#topic Merge plans17:43
*** openstack changes topic to "Merge plans (Meeting topic: glare)"17:43
*** shaohe_feng has quit IRC17:43
mfedosinlet's define it17:43
mfedosinwhat is definition of done for the spec?17:43
mfedosinI mean how detailed it should be17:44
*** shaohe_feng has joined #openstack-meeting-alt17:44
nikhilI think for now let's focus on the bare minimum17:44
nikhiland we need to clearly indicate that it is so17:44
nikhiland also document what will/can be implemented and what are future plans17:44
nikhillet us focus on "just" Newton now17:45
nikhillet us tell the story of how this API will improve in features over time17:45
*** anush has joined #openstack-meeting-alt17:45
*** shashank_hegde has joined #openstack-meeting-alt17:45
mfedosinso it should be another spec?17:45
nikhilso, the first and foremost thing to do is to come up with the "minimal" set of calls needed for say HEAT17:45
nikhiland let's say that in the spec17:46
mfedosinor it's a part of existing one?17:46
mfedosinok, I see17:46
nikhilfor now, just one spec17:46
nikhilwe can discuss future plans later.17:46
mfedosinwhat about API examples there?17:46
nikhilmfedosin: the more the better17:46
nikhilmfedosin: but let's not go in too much detail for now17:47
mfedosinthe spec will be huge :)17:47
nikhilmfedosin: for example let's not worry about tags if that is not needed17:47
nikhilmfedosin: let us not worry about import or sharing17:47
*** amitgandhinz has quit IRC17:47
*** rcernin has quit IRC17:47
mfedosinyeah, only base part17:48
nikhilmfedosin: the first spec will be reasonable big but that's okay.17:48
nikhilreasonably*17:48
*** pnavarro has quit IRC17:48
mfedosinand about the code17:48
nikhilmfedosin: also, I think it will be really useful if we can get a liaison from heat and someone else from glance actually working on the code17:49
mfedosinwe agreed to separate in small patches before merge - not this one big commit17:49
nikhilcorrect17:49
mfedosinnikhil: I told you - we have one17:49
nikhilk, let's make sure all that is done upstream17:49
mfedosinand he's already writing a spec for Heat17:49
nikhilpeople have a _strong_ dislike for code that is _dumped_ upstream17:50
*** s3wong has joined #openstack-meeting-alt17:51
mfedosinalso, we decided don't include images artifact type initially17:51
nikhilcorrect17:52
mfedosinand no special features :)17:52
mfedosinI predict that amount of code without tests will be 5000-7000 LOC17:53
nikhil👍17:53
mfedosinmay be less17:53
*** doug-fish has joined #openstack-meeting-alt17:53
*** shaohe_feng has quit IRC17:53
nikhilumm17:53
nikhilok, let's see what we can remove as possible17:54
*** baoli has quit IRC17:54
mfedosindb part is very big17:54
nikhiljust make sure each patch is 250LOC with unit tests17:54
*** shaohe_feng has joined #openstack-meeting-alt17:54
mfedosinall these migrations...17:54
nikhileh17:54
mfedosinI think there will be about 15 patches17:54
mfedosin200-300 LOC each17:55
*** baoli has joined #openstack-meeting-alt17:55
nikhilok, let's see17:55
*** anush has quit IRC17:55
nikhilonce they are out we need to meet to discuss what can be done first17:55
nikhilnote: people are getting worried about code not being upstream17:56
mfedosinyup17:56
mfedosinit's all on review :)17:56
nikhilwith WIP ?17:56
mfedosinexcept db part17:56
mfedosinyeah17:56
nikhil:)17:56
docaedoyeah as far as I knew everything was out there (that's what we played with in app-catalog land)17:56
nikhilI see17:57
nikhilso for consumers it is out there17:57
nikhilfor reviewers (hard part) we need to make sure it's in the right shape for it to be reviewed17:57
mfedosinkind of :)17:57
nikhilmfedosin: 250LOC /each :)17:57
*** amitgandhinz has joined #openstack-meeting-alt17:57
mfedosinas I mentioned on the summit will start to split it in early June17:58
*** doug-fish has quit IRC17:58
mfedosinand if it's possible will have the spec been merged by that time17:58
nikhilmfedosin: hmm, ok. let me know in detail what are the blockers so that I can plan accordingly.17:58
nikhilmfedosin:  this week we are supposed to focus on spec reviews as per my email17:59
nikhilthe more you review someone else's work, the more review you can get on your work ;-)17:59
mfedosingotcha ;)17:59
*** s3wong has quit IRC17:59
*** doug-fish has joined #openstack-meeting-alt17:59
nikhilcheck my emails to the ML17:59
mfedosinfor sure!18:00
*** baoli has quit IRC18:00
nikhilI am sending all that for people to use the approach to get things done fast!18:00
nikhilgtg18:00
nikhilnext meeting18:00
nikhilthanks!18:00
mfedosinthank you for that18:00
mfedosin#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Mon May 16 18:00:39 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glare/2016/glare.2016-05-16-17.32.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glare/2016/glare.2016-05-16-17.32.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glare/2016/glare.2016-05-16-17.32.log.html18:00
*** nadya has joined #openstack-meeting-alt18:01
*** s3wong has joined #openstack-meeting-alt18:01
*** numans has quit IRC18:03
*** anush has joined #openstack-meeting-alt18:03
*** tango has joined #openstack-meeting-alt18:03
*** shaohe_feng has quit IRC18:04
*** Na3iL has quit IRC18:04
*** shaohe_feng has joined #openstack-meeting-alt18:04
*** baoli has joined #openstack-meeting-alt18:05
*** kfarr has quit IRC18:05
*** julim has quit IRC18:07
*** julim has joined #openstack-meeting-alt18:08
*** delattec has joined #openstack-meeting-alt18:09
*** nadya has quit IRC18:10
*** diazjf has joined #openstack-meeting-alt18:10
*** cdelatte has quit IRC18:12
*** merooney has quit IRC18:13
*** ninag has quit IRC18:13
*** jungleboyj has joined #openstack-meeting-alt18:13
*** ninag has joined #openstack-meeting-alt18:13
*** ninag has quit IRC18:14
*** shaohe_feng has quit IRC18:14
*** ninag has joined #openstack-meeting-alt18:14
*** delatte has joined #openstack-meeting-alt18:14
*** shaohe_feng has joined #openstack-meeting-alt18:14
*** doug-fis_ has joined #openstack-meeting-alt18:15
*** numans has joined #openstack-meeting-alt18:16
*** Ravikiran_K has quit IRC18:16
*** IlyaG has joined #openstack-meeting-alt18:16
*** sbalukoff has joined #openstack-meeting-alt18:17
*** delattec has quit IRC18:17
*** doug-fish has quit IRC18:18
*** jtomasek has quit IRC18:19
*** merooney has joined #openstack-meeting-alt18:20
*** doug-fis_ has quit IRC18:21
*** doug-fish has joined #openstack-meeting-alt18:21
*** ninag has quit IRC18:24
*** shaohe_feng has quit IRC18:24
*** yamamoto has joined #openstack-meeting-alt18:24
*** shaohe_feng has joined #openstack-meeting-alt18:25
*** doug-fish has quit IRC18:26
*** kfarr has joined #openstack-meeting-alt18:26
*** yamahata has quit IRC18:26
*** yamahata has joined #openstack-meeting-alt18:27
*** ddieterly[away] has quit IRC18:28
*** pvaneck has joined #openstack-meeting-alt18:33
*** Sukhdev has joined #openstack-meeting-alt18:33
*** shaohe_feng has quit IRC18:34
*** shaohe_feng has joined #openstack-meeting-alt18:35
*** ddieterly has joined #openstack-meeting-alt18:35
*** mixos_ has quit IRC18:36
*** IlyaG has quit IRC18:36
*** coolsvap is now known as coolsvap|zzzzzzz18:36
*** ninag has joined #openstack-meeting-alt18:36
*** ninag has quit IRC18:36
*** ninag has joined #openstack-meeting-alt18:37
*** lpetrut has joined #openstack-meeting-alt18:40
*** merooney has quit IRC18:40
*** ninag has quit IRC18:42
*** kzaitsev_mb has joined #openstack-meeting-alt18:42
*** tfukushima has quit IRC18:43
*** shaohe_feng has quit IRC18:45
*** shaohe_feng has joined #openstack-meeting-alt18:45
*** stingaci has quit IRC18:47
*** merooney has joined #openstack-meeting-alt18:47
*** egallen has quit IRC18:49
*** Prem_ has quit IRC18:53
*** Prem_ has joined #openstack-meeting-alt18:54
*** shaohe_feng has quit IRC18:55
*** shaohe_feng has joined #openstack-meeting-alt18:55
*** numans has quit IRC18:56
*** dukhlov has joined #openstack-meeting-alt18:57
*** banix has quit IRC18:58
*** Na3iL has joined #openstack-meeting-alt18:58
*** baoli has quit IRC18:59
*** anush has quit IRC18:59
*** ninag has joined #openstack-meeting-alt18:59
*** ninag has quit IRC18:59
*** doug-fis_ has joined #openstack-meeting-alt19:00
*** ninag has joined #openstack-meeting-alt19:00
*** noslzzp has quit IRC19:02
*** doug-fis_ has quit IRC19:02
*** woodster_ has joined #openstack-meeting-alt19:03
*** noslzzp has joined #openstack-meeting-alt19:03
*** sarob has joined #openstack-meeting-alt19:04
*** Swami has quit IRC19:04
*** shaohe_feng has quit IRC19:05
*** mickeys has joined #openstack-meeting-alt19:05
*** Swami has joined #openstack-meeting-alt19:06
*** shaohe_feng has joined #openstack-meeting-alt19:06
*** mixos has joined #openstack-meeting-alt19:06
*** salv-orl_ has quit IRC19:07
*** dukhlov has quit IRC19:08
*** dukhlov has joined #openstack-meeting-alt19:09
*** Swami has quit IRC19:14
*** Na3iL has quit IRC19:15
*** shaohe_feng has quit IRC19:15
*** merooney has quit IRC19:16
*** shaohe_feng has joined #openstack-meeting-alt19:16
*** merooney has joined #openstack-meeting-alt19:20
*** merooney has quit IRC19:20
*** dukhlov has quit IRC19:21
*** merooney has joined #openstack-meeting-alt19:21
*** lpetrut has quit IRC19:24
*** shaohe_feng has quit IRC19:26
*** shaohe_feng has joined #openstack-meeting-alt19:27
*** tonytan4ever has quit IRC19:27
*** showerthoughtbot has joined #openstack-meeting-alt19:28
*** mickeys has quit IRC19:29
*** dukhlov has joined #openstack-meeting-alt19:29
*** mickeys has joined #openstack-meeting-alt19:29
*** mickeys has quit IRC19:33
*** shaohe_feng has quit IRC19:36
*** shaohe_feng has joined #openstack-meeting-alt19:37
*** Na3iL has joined #openstack-meeting-alt19:41
*** snackewm has quit IRC19:41
*** rcernin has joined #openstack-meeting-alt19:42
*** dukhlov has quit IRC19:43
*** sheel has quit IRC19:45
*** baoli has joined #openstack-meeting-alt19:45
*** shaohe_feng has quit IRC19:46
*** doug-fish has joined #openstack-meeting-alt19:46
*** baoli has quit IRC19:46
*** baoli has joined #openstack-meeting-alt19:47
*** shaohe_feng has joined #openstack-meeting-alt19:47
*** kfarr has quit IRC19:48
*** yamahata has quit IRC19:48
*** iyamahat has quit IRC19:49
*** kfarr has joined #openstack-meeting-alt19:53
*** tonytan4ever has joined #openstack-meeting-alt19:53
*** stingaci has joined #openstack-meeting-alt19:56
*** shaohe_feng has quit IRC19:56
*** shaohe_feng has joined #openstack-meeting-alt19:57
*** merooney has quit IRC19:58
*** doug-fis_ has joined #openstack-meeting-alt20:00
redrobot#startmeeting barbican20:00
openstackMeeting started Mon May 16 20:00:45 2016 UTC and is due to finish in 60 minutes.  The chair is redrobot. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: barbican)"20:00
openstackThe meeting name has been set to 'barbican'20:00
redrobot#topic Roll Call20:01
*** openstack changes topic to "Roll Call (Meeting topic: barbican)"20:01
*** doug-fi__ has joined #openstack-meeting-alt20:01
*** Swami has joined #openstack-meeting-alt20:01
* redrobot checks clock20:02
* redrobot makes sure he's in the correct channel20:02
kfarro/20:02
showerthoughtbotkfarr: I'd rather have sex with a 6/10 that was super into me than a 10/10 who was half-assing it.20:02
*** showerthoughtbot has quit IRC20:02
kfarrD: D: D:20:02
redrobotwtf was that?20:02
*** doug-f___ has joined #openstack-meeting-alt20:02
woodster_o/20:03
*** ninag has quit IRC20:03
dave-mccowano/20:04
redrobotlooks like only a few of us are here today20:04
*** doug-fish has quit IRC20:04
redrobotas usual the agenda can be found here:20:04
redrobot#link https://wiki.openstack.org/wiki/Meetings/Barbican#Agenda20:05
*** doug-fis_ has quit IRC20:05
redrobot#topic Action Items from last meeting20:05
edtubillo/20:05
*** openstack changes topic to "Action Items from last meeting (Meeting topic: barbican)"20:05
diazjfo/20:05
*** doug-fi__ has quit IRC20:05
redrobot#link http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-05-09-20.00.html20:05
panatlo/20:05
redrobotthe only action item was for me20:05
redrobotand I didn't get a chance to work on it last week, so20:06
redrobot#action redrobot to work on install doc skeleton20:06
redrobotpuuunt! ;D20:06
redrobotok, then, I can't think of anything off the top of my head to talk about20:06
*** shaohe_feng has quit IRC20:07
redrobot#topic Newton M120:07
*** openstack changes topic to "Newton M1 (Meeting topic: barbican)"20:07
redrobot#link http://releases.openstack.org/newton/schedule.html20:07
redrobotjust a heads up that milestone one is a couple of weeks away20:07
redrobotI'd like for us to land some blueprints before then20:07
*** shaohe_feng has joined #openstack-meeting-alt20:07
*** sarob has quit IRC20:07
*** baoli has quit IRC20:07
redrobotso please take some time to look at the bps currently in review20:07
redrobot#link https://review.openstack.org/#/q/project:openstack/barbican-specs+status:open20:08
*** baoli has joined #openstack-meeting-alt20:08
*** ninag_ has joined #openstack-meeting-alt20:08
*** max__ has joined #openstack-meeting-alt20:08
*** _sarob has joined #openstack-meeting-alt20:08
*** iyamahat has joined #openstack-meeting-alt20:08
max__\o20:08
diazjfredrobot, I still owe you a review on the container PUT20:08
*** baoli has quit IRC20:09
*** max__ is now known as Guest5328920:09
*** ninag_ has quit IRC20:09
*** baoli has joined #openstack-meeting-alt20:09
redrobotdiazjf I'll take that IOU20:10
*** piet has quit IRC20:10
*** Sukhdev has quit IRC20:10
*** ninag has joined #openstack-meeting-alt20:11
*** arunkant has joined #openstack-meeting-alt20:11
redrobotany questions about the upcoming milestone release?20:12
*** yamahata has joined #openstack-meeting-alt20:12
*** cknight1 has quit IRC20:12
*** ninag has quit IRC20:13
arunkanto/20:13
*** korzen has quit IRC20:13
redrobotok then, moving on20:13
redrobot#topic Open Discussion20:14
*** openstack changes topic to "Open Discussion (Meeting topic: barbican)"20:14
redrobotAny bugs/reviews that need attention?20:14
*** Na3iL has quit IRC20:14
arunkantCan someone review this..https://review.openstack.org/#/c/311830/20:15
diazjfredrobot, can anyone review https://review.openstack.org/#/c/313788/20:15
*** dukhlov has joined #openstack-meeting-alt20:16
redrobotarunkant diazjf queued up for review today20:16
arunkantand also this one..https://review.openstack.org/#/c/306599/ .20:16
*** ninag has joined #openstack-meeting-alt20:16
diazjfredrobot, awesome dalé20:16
arunkantredrobot: thanks20:16
redrobotany other topics that need discussion?20:17
redrobotif not we may have a record setting short meeting20:17
*** salv-orlando has joined #openstack-meeting-alt20:17
*** shaohe_feng has quit IRC20:17
kfarrIs there going to be a mid-cycle?20:17
*** shaohe_feng has joined #openstack-meeting-alt20:18
redrobotkfarr good question20:18
*** nadya has joined #openstack-meeting-alt20:18
redrobotI talked to Rob Clark (hyakuei) during the Summit20:18
*** amrith is now known as _amrith_20:18
redrobothe liked that we had a joint security/barbican mid-cycle last time and he'd like for us to do it again.20:18
redrobotI figured San Antonio or Austin would work since most devs are located in one of those two cities20:19
redrobotalso open to suggestions20:19
diazjfredrobot, I can maybe get support to host it here at IBM. Maybe we can have a vote next meeting20:20
redrobotdiazjf yeah that sounds good20:20
*** ninag has quit IRC20:20
diazjfI'll talk to the boss man today and see if iits a possibility20:21
redrobot#action diazjf to inquire about hosting the Barbican (and possibly also OSSP) mid-cycle at IBM Austin.20:21
*** arunrajan has joined #openstack-meeting-alt20:21
*** ninag has joined #openstack-meeting-alt20:21
redrobotJul 04-06 is the week before M-220:22
redrobotAug 22-26 is the week before M-3 (feature freeze)20:22
* redrobot thinks Aug 22-26 might be good20:23
diazjfredrobot, cool20:23
redrobotbut it's going to be hot as hell down here in TX20:23
*** nsun1 has joined #openstack-meeting-alt20:24
diazjfI wish we could do it in Miami ;)20:24
nsun1do what?20:25
diazjfmidcycle!20:25
diazjfnsun1 ^20:25
redrobotdiazjf that would be pretty cool...  beachside midcycle, what?20:26
diazjfredrobot, haha yeah. Thats the right idea20:26
diazjfWe can talk about barbican on the beach over margaritas and coronas20:27
*** shaohe_feng has quit IRC20:27
redrobotok, anything else guys?20:28
*** shaohe_feng has joined #openstack-meeting-alt20:28
*** ninag has quit IRC20:29
*** doug-f___ has quit IRC20:29
*** baoli has quit IRC20:29
*** muralia has joined #openstack-meeting-alt20:29
*** jprovazn has quit IRC20:29
redrobotlet's call it a day, then20:29
redrobotthanks for coming, everyone!20:29
redrobot#endmeeting20:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:29
openstackMeeting ended Mon May 16 20:29:52 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-05-16-20.00.html20:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-05-16-20.00.txt20:29
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2016/barbican.2016-05-16-20.00.log.html20:29
*** doug-fish has joined #openstack-meeting-alt20:31
*** Guest53289 has quit IRC20:31
*** dukhlov has quit IRC20:32
*** eggmaster has quit IRC20:34
*** sdake has quit IRC20:37
*** sdake has joined #openstack-meeting-alt20:37
*** shaohe_feng has quit IRC20:37
*** shaohe_feng has joined #openstack-meeting-alt20:40
*** dukhlov has joined #openstack-meeting-alt20:40
*** dukhlov has quit IRC20:43
*** rmart04 has joined #openstack-meeting-alt20:44
*** rmart04 has quit IRC20:46
*** ninag has joined #openstack-meeting-alt20:46
*** ninag has quit IRC20:46
*** dukhlov has joined #openstack-meeting-alt20:46
*** nsun1 has quit IRC20:46
*** ninag has joined #openstack-meeting-alt20:47
*** tonytan4ever has quit IRC20:47
*** tonytan4ever has joined #openstack-meeting-alt20:47
*** arunrajan has quit IRC20:47
*** shaohe_feng has quit IRC20:48
*** ivc_ has left #openstack-meeting-alt20:48
*** dukhlov has quit IRC20:48
*** shaohe_feng has joined #openstack-meeting-alt20:49
*** dukhlov has joined #openstack-meeting-alt20:50
*** CIA has quit IRC20:51
*** ninag has quit IRC20:51
*** doug-fis_ has joined #openstack-meeting-alt20:51
*** stingaci has quit IRC20:52
*** _sarob has quit IRC20:52
*** ddieterly is now known as ddieterly[away]20:52
*** sarob has joined #openstack-meeting-alt20:53
*** doug-fish has quit IRC20:54
*** dukhlov has quit IRC20:54
*** baoli has joined #openstack-meeting-alt20:55
*** julim has quit IRC20:55
*** hichihara has joined #openstack-meeting-alt20:56
*** shaohe_feng has quit IRC20:58
*** shaohe_feng has joined #openstack-meeting-alt20:59
*** shamail has joined #openstack-meeting-alt20:59
*** mickeys_ has joined #openstack-meeting-alt20:59
*** ddieterly[away] is now known as ddieterly20:59
*** kei_ has joined #openstack-meeting-alt21:00
*** dukhlov has joined #openstack-meeting-alt21:00
*** pchadwick has joined #openstack-meeting-alt21:00
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:00
*** anush has joined #openstack-meeting-alt21:01
Arkady_Kanevskyhello Product WG21:01
*** carolbarrett_ has joined #openstack-meeting-alt21:01
kencjohnstonhi Arkady_Kanevsky21:01
*** Sukhdev has joined #openstack-meeting-alt21:01
carolbarrett_Hi everyonr21:01
MeganRHi21:01
carolbarrett_#startmeeting product working group21:01
openstackMeeting started Mon May 16 21:01:44 2016 UTC and is due to finish in 60 minutes.  The chair is carolbarrett_. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: product working group)"21:01
openstackThe meeting name has been set to 'product_working_group'21:01
kencjohnstono/21:02
Arkady_KanevskySorry I was out of the pocket since Wed for family emergency. Only was abel to review fleet user story21:02
carolbarrett_you can find the agenda here: https://wiki.openstack.org/wiki/Meetings/product-team21:02
carolbarrett_#link https://wiki.openstack.org/wiki/Meetings/product-team21:02
carolbarrett_Let's start with roll call21:02
kei_o/21:02
shamailhi everyone21:02
MeganRo/21:02
Arkady_Kanevskyhello21:02
carolbarrett_Hi Shamail21:02
carolbarrett_Hi Kei21:02
cloudranchero/21:02
*** leong has joined #openstack-meeting-alt21:02
leongol21:03
leongo/21:03
carolbarrett_#topic Newton Cycle Focus Areas21:03
*** openstack changes topic to "Newton Cycle Focus Areas (Meeting topic: product working group)"21:03
pchadwicko/21:03
pchadwickHi everyone21:03
*** KrishR has joined #openstack-meeting-alt21:04
carolbarrett_From looking at the etherpad for the working session, there were a couple of areas that seemed higher priority to people.21:04
carolbarrett_They are the ones listed at the link above21:04
Arkady_KanevskyExecute Work Flow Pilot?21:04
carolbarrett_I'd like to use some time in this meeting to discuss these and see if we can get an agreement on the focus areas for this development cycle21:05
pchadwicko/21:05
*** MarkBaker has joined #openstack-meeting-alt21:05
KrishRo/21:05
carolbarrett_Arkady: In the discussion with the Board/TC and the Design Summit session on our work flow, there were some suggestions for how we evolve it to better integrate with the development flow21:05
Arkady_Kanevskyi remember21:06
carolbarrett_Piloting the work flow, refers to taking the new flow and selecting a user story to test it with21:06
carolbarrett_Arkady: sorry, what is your question?21:06
*** muralia has left #openstack-meeting-alt21:06
MarkBakero/21:06
carolbarrett_Hi Mark21:06
Arkady_Kanevskynew user story or one whcih we arleady driving, like rolling upgrade?21:07
carolbarrett_Arkady_Kanevksy: Excellent question. We started to list out some criteria for a good pilot...which I think will lead us to something new21:07
carolbarrett_User Story Selection Criteria: Blueprints will be needed in multiple projects; Greenfield Request21:08
Arkady_KanevskyTo my recollection there some decisions that nova team had doen (in conjucture with TC) and other folks are no aware of it.21:08
carolbarrett_Does anyone disagree with a focus on work flow validation?21:08
*** shaohe_feng has quit IRC21:08
Arkady_KanevskySome of out use cases in user stories conflict iwht these decisions21:08
*** shaohe_feng has joined #openstack-meeting-alt21:09
Arkady_KanevskyWe need to run it by TCs to get feedback on what was already discussed and/or agreed by project WG21:09
pchadwickcarolbarrett_: works for me21:09
carolbarrett_Arkady: not following your line of thought21:09
leongcarolbarrett_ +121:10
carolbarrett_Thanks - I think we've got support for that one - details to be worked21:10
carolbarrett_#agree 1 of the focus areas for Newton development cycle is validating the updated work flow21:11
Arkady_Kanevskysome of our user stories have use cases that TC or Nova already discussed and agreed not to follow. If we put that as use case as requirement than technical communitee will not be very receptive since it is closed issue for them.21:11
carolbarrett_Next focus area is Roadmap - evoling the themes and views associated with them.21:11
Arkady_Kanevskyrollback is an example of it.21:11
Arkady_Kanevsky+1 on validating workflow.21:11
leongArkady, rolling upgrade use case will be a special one, i don't think we want to use that to pilot?21:12
kencjohnstonleong +121:12
carolbarrett_arkady_kanevsky: I don't think those user stories would meet the greenfield criteria21:12
shamailcarolbarrett_: +121:12
Arkady_Kanevskydo we choose new user story for newton or pick one we already driving since Mitaka21:12
carolbarrett_leong: +121:12
Arkady_KanevskyOK, on new story21:12
carolbarrett_Yes21:12
*** sgotliv_ has quit IRC21:13
carolbarrett_What do you all think of the Roadmap work being a focus for us this cycle?21:13
Arkady_KanevskyHow about Fleet management as geanee pig story for workflow?21:13
Arkady_Kanevskywe have 2 new themes in Newton.21:14
KrishRArkady_Kanevsky: fleet mgmt is not cross-project in nature but potentially a separate project under the big tent21:14
pchadwickGetting agreement on the themes early would be good.21:14
MarkBakercarolbarrett_, yes to roadmap work.21:14
Arkady_KanevskyDriving them into roadmap woudl be my recommended priority21:14
shamailcarolbarrett_: +1 to roadmap21:14
leongcarolbarrett_ +1 for roadmap21:14
KrishRcarolbarrett-: +1 to roadmap work21:14
* MarkBaker looks up Fleet21:14
MeganR+1 for roadmap21:15
carolbarrett_#agree Evolving roadmap themes and corresponding views will be a focus area for the Newton cycle21:15
Arkady_KanevskyKrishR - not sure about it. SIcne I expect it will overlap with Fuel and TripleO and Ironic21:15
*** ansmith has quit IRC21:15
*** dukhlov has quit IRC21:16
MeganR@MarkBaker: https://etherpad.openstack.org/p/craton-meeting-2016-05-16 - notes from the Fleet, now Craton, meeting today21:16
carolbarrett_So next proposal is working with the OPNFV community to better integrate the flow of user stories from their community into OpenStack, with development committed resources t21:16
*** jungleboyj has quit IRC21:16
MarkBakerMeganR, thanks21:17
*** doug-fis_ has quit IRC21:17
carolbarrett_I was thinking we would get through the focus area discussion and then have a deeper discussion about each.21:17
Arkady_KanevskySuggest we tackle themes first. Otherwise we will need to go back and retrofit all roadmaps into update themes21:17
carolbarrett_arkady_kanevsky: +121:18
*** doug-fish has joined #openstack-meeting-alt21:18
carolbarrett_What's the team viewpoint on the OPNFV collaboration?21:18
*** shaohe_feng has quit IRC21:18
Arkady_Kanevsky+1 on OPNFV but after we agree on themes21:18
pchadwickArkady_Kanevsky: +121:19
kencjohnstoncarolbarrett_ is OPNFV synonymous with "cloudlets"?21:19
Arkady_KanevskyCarol, why OPNFV and not wider NFV community?21:19
kencjohnstonOr is this the general NFV use case?21:19
*** shaohe_feng has joined #openstack-meeting-alt21:19
*** weshay has quit IRC21:19
carolbarrett_OPNFV is an example of an Open Source ecosystem community21:20
MarkBakerArkady_Kanevsky, I believe OPNFV has biggest commitment to OpenStack, most in common21:20
carolbarrett_It's about bringing the NFV use cases into OpenStack for action21:20
carolbarrett_MarkBaker: +121:20
Arkady_KanevskyMarkBaker: +121:21
carolbarrett_Given the commonalities between OpenStack and OPNFV it seemed like a good starting point for figuring out how we collaborate with other open source communities21:21
carolbarrett_They won't be the only ones we want to do this with, I hope21:21
carolbarrett_Anyone oppose this as our 3rd focus area?21:21
Arkady_KanevskyWant to be very clear with them that we create user stories that are applicable to all "workloads" and prioritiy is given to cross workload ones.21:22
pchadwickOK with me21:22
kencjohnstonI guess I'd rather figure out how we integrate with players in the Conatiner ecosystem before OPNFV21:22
*** doug-fish has quit IRC21:22
kencjohnstonbut that's because containers is on my buzzword bingo card...21:22
shamailkencjohnston: OPNFV wants to figure out a way to integrate so thats why they were the first candidate21:22
leongi'm fine with OPNFV21:22
*** qwebirc85867 has joined #openstack-meeting-alt21:22
Arkady_KanevskyKen - we already have magnum, kolla, kuryr...21:23
pchadwickI suspect that opnfv will have some container questions anyway21:23
leongmoving forward, we can also include container as kencjohnston has mentioned21:23
shamailPlus, the good news is that its mainly organizations that also have OpenStack presence making it (hopefully) easier to move stories forward21:23
Arkady_KanevskyNothing NFV specific WG as far as I know21:23
carolbarrett_leong: +121:23
kencjohnstonshamail ok, so this is in response to their inquiry?21:23
shamailrecommendation by the board21:24
*** sbalukoff has quit IRC21:24
shamailplus willingness from the community21:24
carolbarrett_Sounds like there's support for starting with OPNFV and then looking to identify a container community next. OK?21:24
kencjohnstonshamail ok gotcha21:24
kencjohnstoncarolbarrett_ +121:24
Arkady_Kanevsky+121:24
*** stingaci has joined #openstack-meeting-alt21:24
leong+121:24
shamailcarolbarrett_: +121:24
kei_+121:24
MeganR+121:24
carolbarrett_#agree 3rd focus area for Newton is integration with OPNFV, with a plan to follow that with a Container Community21:25
carolbarrett_Good stuff!21:25
*** doug-fish has joined #openstack-meeting-alt21:25
carolbarrett_Let's go to Roadmap Themes21:25
shamailSweet21:25
carolbarrett_#topic Roadmap Themes and Views21:25
*** openstack changes topic to "Roadmap Themes and Views (Meeting topic: product working group)"21:25
carolbarrett_Shamail - take it away!21:25
Arkady_KanevskyHow do propose we engage with OPNFV? hey can submit user stories now and use nay of the accepted one as example.21:25
shamailThanks21:25
*** mickeys_ has quit IRC21:26
Arkady_KanevskyThey are weclome to this call of course.21:26
shamailBefore we begin roadmap discussion, I’d like to quickly discuss the Newton Design Series first… We have two interviews that need volunteers: https://etherpad.openstack.org/p/Newton_design_series_PTL_interview21:26
*** doug-fish has quit IRC21:26
shamailWe need someone to cover Rally and RefStack21:26
shamailplease look at your schedules (if you’re volunteering to help with the design series) and see if they fit21:27
carolbarrett_Link: https://drive.google.com/file/d/0B_yCSDGnhIbzQS15UVJzVGV1Q1U/view?usp=sharing21:27
shamailOkay, now moving on to the real topic21:27
*** doug-fish has joined #openstack-meeting-alt21:27
shamailThanks carolbarrett_21:27
shamailWe had discussed adding two new themes during our midcycle (Security and UX)21:27
carolbarrett_#link https://etherpad.openstack.org/p/Newton_design_series_PTL_interview21:27
shamailthe challenge was that it would break our existing views21:27
Arkady_KanevskyI took Rally one21:28
shamailsince going above 5 themes would be hard with them21:28
shamailthanks Arkady_Kanevsky21:28
shamailI’ll follow up via email21:28
shamailI have put together a new view (google link that carolbarrett_ posted above) to switch the 1,000 ft view into a themes view21:28
shamailThis would allow people to see all changes related to a theme that is important to them21:28
*** shaohe_feng has quit IRC21:29
shamailThe main slide would list all the themes (slide 3)21:29
*** enriquetaso has quit IRC21:29
Arkady_KanevskyI took refstack also21:29
shamailand then each of the names would be a hyperlink21:29
pchadwickDo we want to list every project or just the most used ones?21:29
shamailWhen you click the hyperlink, it will take you to a “theme view” (replacing the 1,000 ft view) that shows all changes categorized under that theme21:29
shamaile.g. slide 421:29
pchadwickPart of the problem in visualization is covering everything21:29
shamailpchadwick: Right now, we will all projects with > 10% adoption and some special ones that serve horizontal needs in the community (oslo, refstack, docs, ansible, etc)21:30
shamailAre you proposing to keep the 100 ft view for those projects but not show them in the themes view?21:30
kencjohnstonshamail I'm not sure the "What is happening in this theme" view is that valuable.21:31
pchadwickI would at least consider raising the bar on what we include21:31
shamailThe scalability sample slide actually uses the content from our real roadmap deck… all projects were able to fit in one slide21:31
*** shaohe_feng has joined #openstack-meeting-alt21:31
shamailkencjohnston: fair enough… does the existing 1K foot view provide more value in your opinion?21:31
pchadwickBut I think it loses the cross release evolution21:31
kencjohnstonshamail I'm trying to put myself into the shoes of someone who wants to know the direction of where OpenStack is headed.21:31
Arkady_Kanevskysingle slide per theme will be too busy.21:32
kencjohnstonand the former view worked better.21:32
*** doug-fish has quit IRC21:32
kencjohnstonAnd the intent was to show which projects were working inside of given themes.21:32
shamailSo should we keep our previous view?  If so, we can’t hold more than 5 themes in a single slide21:32
Arkady_KanevskyShamail, are oyu proposing to tag blueprints so we can build slides automatically?21:32
leongthe former ones looks more "release-oriented", this new proposal looks more "theme-oriented"21:32
kencjohnstonshamail right, I was wondering, can we consolidate some of the themes?21:32
shamailkencjohnston: agreed… the main purpose for brainstorming was due to themes increasing from 5 to 721:33
kencjohnstonare some themes becoming less prevelant?21:33
*** mkashyap has joined #openstack-meeting-alt21:33
Arkady_KanevskyWe do one sldie wiht all current themes21:33
shamailNo, they all seem to be fairly active still21:33
pchadwickI think Arkady and I got UX on the slide at least ;)21:33
Arkady_Kanevskyand 1 or more slide per theme in order of them to be readable21:33
shamailWe went from 5 to 7 to reduce the coarseness of “manageability"21:33
*** doug-fish has joined #openstack-meeting-alt21:33
kencjohnstonhmm..21:33
shamailpchadwick: Once the project data is populated, it probably won’t fit21:34
Arkady_Kanevskywe added security and split managability in to UX and managability21:34
shamailDid you update the content to include sentences under those themes?21:34
kencjohnstonArkady_Kanevsky shamail and we broke them out to show more detail at the "theme" level?21:34
kencjohnstonIf we feel like people want more theme level views/data then I htink shamail is headed in the right direction21:35
kencjohnstonwith the new views21:35
shamailkencjohnston: not sure how to validate, mailing list?21:35
Arkady_KanevskyI am looking at slide 3 now that lists 7 themese21:35
Arkady_Kanevskythemes21:35
kencjohnstonshamail did we get feedback in the summit presentations21:35
shamailyes but that is just themes with no content21:35
*** dimtruck is now known as zz_dimtruck21:35
kencjohnstonto analysts/users/operators?21:35
*** merooney has joined #openstack-meeting-alt21:36
Arkady_KanevskyWe need much better coordination with board and its marketing activies to stay on the same page.21:36
shamailWe did kencjohnston, from the operators, they don’t have value for any of the views (want more focus on day to day needs than future releases)21:36
KrishRkencjohnston: one user at the summit asked that the roadmap link to user requirements....themes may be a good way to make that link21:36
kencjohnstonI don't want ot revisit a previous decision, so if we want the views I think you've done a great job iwth them shamail21:36
shamailWe did not get feedback from users/business decision makers/analysts21:36
shamailkencjohnston: The only decision we made was to increase the number of themes.  We don’t have a solution for views yet… the open item was how do we expand themes since they break the current 1K view21:37
shamailShould we break each slide into 4 themes each?21:37
pchadwickWe did get some comments in the themes session, but I'm not sure what roles were represented21:37
shamailStill keep 1000 ft view (as is) but instead of one slide…. use two slides per project?21:37
*** doug-fish has quit IRC21:37
pchadwickI would do it by project.21:37
Arkady_KanevskyLike 1000ft view slide(s)21:38
kencjohnstonshamail +1 i think that would be good21:38
shamailfirst slide would have scalability, resiliency, manageability, modularity…. second slide would have interoperability, security, ux21:38
*** doug-fish has joined #openstack-meeting-alt21:38
shamailpchadwick: by project would be adding themes to the 100 ft view21:38
pchadwickthat works for me.21:38
*** doug-fish has quit IRC21:38
*** doug-fish has joined #openstack-meeting-alt21:38
Arkady_KanevskyWe need both. We need how themes are covered across porjects. and inside projects what are "specs/blueprints" associated with each theme21:38
pchadwick(at least it seems more intuitive that I would want to see how a project evolves as opposed to a specific theme)21:39
MarkBakerArkady_Kanevsky, yep21:39
Arkady_Kanevsky100ft project view covers second need21:39
*** shaohe_feng has quit IRC21:39
shamailSo let’s vote on two options: A) Keep 1000 ft view but use two slides to represent up to 8 themes or B) drop 1000 ft view and move theme data into the 100 ft view (show per project)21:39
shamail?21:39
shamailThat was “B )” not sunglass emoji lol21:39
*** _amrith_ is now known as amrith21:39
kencjohnstonshamail I vote for A21:39
Arkady_Kanevskyshamail can you ptovide more details on what w eare voting?21:40
*** shaohe_feng has joined #openstack-meeting-alt21:40
MeganRvote for A21:40
shamailSo both A and B (based on conversation between Arkady_Kanevsky and MarkBaker + our general consensus that 1K is valuable)?21:40
Arkady_KanevskyI am trying to map it back to 2 sets of requirements I stated.21:40
leongi go for A21:41
KrishRshamail: actually, option 3 would be change 1000ft view to show one slide per theme (across To date, Newton, Ocata)21:41
shamailHow about this: Update 1K view to be two slides and add theme categorization to 100 ft view as well?21:41
KrishRoption C21:41
shamailThe re-work is not much since we have that data already21:41
Arkady_KanevskyShamail, how on 1000 ft view we show al,l projects that are working on a theme?21:41
pchadwickI'm ok with adding some theme info to 100 ft view21:41
MarkBakerwe need to map advances made in each project against a theme21:41
shamailArkady_Kanevsky: we don’t… the view I showed as the demo today would have allowed that but we prefer to keep the cross project view on themes21:41
Arkady_KanevskyI think we need one more click down a theme to see "all" projects working on it in this release21:41
shamailThat is what the view in the google link is showing Arkady_Kanevsky21:42
Arkady_Kanevsky+1 on A and +1 on B. But we need to refine A.21:42
pchadwickAt a minimum, on the 100 ft view we could put some sort of code next to each line item to indicate which theme it fits into21:42
shamailSo are we good with moving forward with the “how about this: “ proposal I made?21:42
shamailpchadwick: +121:42
Arkady_KanevskySlide 4 dives into details inside the projects21:42
*** enriquetaso has joined #openstack-meeting-alt21:42
Arkady_Kanevskypchadwick: +121:43
pchadwickshamail: "how about this" +121:43
Arkady_Kanevskycan we use color coding per theme?21:43
pchadwickWith codes on the 100 ft.21:43
shamailkencjohnston: good with this?21:43
shamailSure can Arkady_Kanevsky21:43
*** snackewm has joined #openstack-meeting-alt21:43
pchadwickIn a community this big, we have to consider color blindness, so can't rely just on color.21:43
carolbarrett_#agree Update Roadmap 1K view to be two slides and add theme categorization to 100 ft view as well21:43
shamailthanks carolbarrett_21:44
shamailthat’s all for now21:44
carolbarrett_Thanks Shamail21:44
shamailpchadwick: we won’t… we can add it but I still like your suggestion of a marker21:44
Arkady_Kanevskythanks all21:44
carolbarrett_Next topic - upcoming meetings21:44
carolbarrett_#topic Upcoming meetings21:44
*** openstack changes topic to "Upcoming meetings (Meeting topic: product working group)"21:44
Arkady_KanevskyWhat do we need to do fpor rolling upgrades user story? I thought we merged it already.21:45
carolbarrett_The proposal is to use the next meeting for updates on the top 5 user stories with an eye to updating the team, asking for help and identifying work flow pilot21:45
*** spzala has quit IRC21:46
carolbarrett_Thoughts?21:46
shamail+121:46
KrishR+121:46
leong+121:46
Arkady_Kanevsky+121:46
MarkBaker+121:47
*** neiljerram has quit IRC21:47
leongThe top 5 are: Rolling Upgrade, HA VM, Baremetal, Capacity Mgmt, Fleet Mgmt?21:47
Arkady_Kanevskyrolling upgrade is not under review...21:48
*** fnaval has quit IRC21:48
carolbarrett_Leong: Yes, I was just looking to see what 1 I missed - Thanks!21:48
carolbarrett_Can all of the user story owners make next week's meeting?21:48
Arkady_KanevskyIs capacity management is capacity control user story?21:49
leongi'm fine on May 2321:49
*** shaohe_feng has quit IRC21:49
KrishRi'm fine with 5/2321:49
*** kfarr has quit IRC21:49
pchadwick23-May should be good for me.21:50
kencjohnstoncarolbarrett_ I'm fine with 5/2321:50
carolbarrett_arkady_kanevsky: Capacity Management is its own story21:50
carolbarrett_Shamail: Can you make 5/23?21:50
*** shaohe_feng has joined #openstack-meeting-alt21:50
Arkady_KanevskyJust to be clear that does not mean that we only review these 5 user stories but that we review them first and give feedback to autthors to update.21:50
shamailit will be tough for me, CF summit21:50
shamailbut ill create an etherpad21:50
Arkady_KanevskyThen I do not see capacity mgmt in user stories udner review21:50
carolbarrett_arkady_kanevsky: for the 5/23 meeting we will focus only on those 5 - I don't think we will have time for others21:51
carolbarrett_Shamail: OK, we'll use your etherpad and follow-up afterwards as needed.21:51
shamailthanks21:51
Arkady_Kanevskyto discuss at the meteing - yes. To review in the tooll - now21:51
carolbarrett_#agree 5/23 team meeting will review Top 5 user stories for the purpose of updating the team, getting feedback, getting help and selecting a user story to pilot work flow21:52
Arkady_Kanevskyahope we pick only one for the meteing next time.21:52
carolbarrett_We'll cancel our meeting for 5/30, since it's a US holiday21:52
Arkady_KanevskyCan we use phone bridge for story discussion?21:52
carolbarrett_if the team wants to move to phone for that meeting, I'm fine. What's the group viewpoint on this?21:53
pchadwickPhone or go to meeting makes more sense to me.21:53
kencjohnstoncarolbarrett_ I'd prefer IRC21:53
*** fnaval has joined #openstack-meeting-alt21:53
kencjohnstonbut I'm fine eitherway21:53
leongi'm fine with either phone or irc..21:54
Arkady_Kanevskytyping comments takes too long and feedback on a comment with eat 10-15 min21:54
shamailIm fine with either21:54
kencjohnstonIRC means we don't have to take notes and others can learn the status21:54
MeganRI'd prefer phone or video21:54
KrishRi'm fine with either, though phone is preferred21:54
carolbarrett_kencjohnston: we can setup an etherpad as the vehicle to capture notes21:54
Arkady_Kanevskyphone is my preference with open review of a story21:54
Arkady_Kanevskysuggest we capture nodes in review21:55
Arkady_Kanevskynodes-> notes21:55
kencjohnstoncarolbarrett_ are we going to be openly reviewing the story, or reviewing the status of the story?21:55
carolbarrett_#agree use phone for 5/23 user story review meeting and have an etherpad to capture discussion21:55
kencjohnstonArkady_Kanevsky is using the word review, but we originally said "provide updates."21:55
leongalternatively i can sign in to irc and capture the notes/agreement in irc for tracking purpose21:55
*** shashank_hegde has quit IRC21:55
pchadwickkencjohnston: +121:55
carolbarrett_kencjohnston - I'd like to focus on the status of the user story and what's needed to advance it21:56
kencjohnstoncarolbarrett_ +1 me too21:56
pchadwickcarolbarrett_ +121:56
Arkady_Kanevskycarolbarrett_ +121:56
carolbarrett_#agree Focus for user story review is update on current status and help needed to advance it21:56
carolbarrett_Lastly, we have talked about starting CPL updates to help each of us keep up with key projects. I'm proposing we start that in the 6/20 meeting21:57
Arkady_KanevskyCan we have story updated before meeting, say by this friday?21:57
Arkady_Kanevskythe top 3 stories as other 2 are already merged21:57
*** markvoelker has joined #openstack-meeting-alt21:57
*** Kuwagata has quit IRC21:57
carolbarrett_Each CPL gets 5 mins to provide updates - we can use an etherpad as a place to capture these to expedite the discussion21:57
Arkady_KanevskyWhat do we do for 2 top stories thta are already merged?21:58
kencjohnstoncarolbarrett_ +! for the CPL review starts21:58
kencjohnstonArkady_Kanevsky we are reviewing updates and next steps21:58
*** edtubill has quit IRC21:58
kencjohnstonArkady_Kanevsky perhaps one next step is to help get the story merged21:58
kencjohnston:)21:58
Arkady_KanevskyCPL or author?21:58
pchadwickIs +! more than +1 ? ;)21:58
carolbarrett_:)21:58
kencjohnstonpchadwick in my book21:58
kencjohnston+(not)21:59
*** shashank_hegde has joined #openstack-meeting-alt21:59
Arkady_Kanevsky+$21:59
shamailI have to leave, sorry21:59
*** shaohe_feng has quit IRC21:59
shamailcatch you later everyone21:59
carolbarrett_Any issue with starting the CPL reviews on 6/20?21:59
Arkady_Kanevskythanks everybody21:59
*** shamail has quit IRC22:00
Arkady_Kanevskybye22:00
kencjohnstonthanks shamail22:00
kencjohnstoncarolbarrett_ none from me22:00
pchadwickBy shamail22:00
MeganRbye!22:00
pchadwick6/20 is good for me.22:00
KrishRbye everyone22:00
carolbarrett_#agree: CPL updates will start with 6/20 Meeting, Carol will create an etherpad for CPL to log updates22:00
carolbarrett_Bye folks22:00
carolbarrett_#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
kencjohnstonthanks carolbarrett_22:00
openstackMeeting ended Mon May 16 22:00:35 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-05-16-21.01.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-05-16-21.01.txt22:00
*** mkashyap has quit IRC22:00
pchadwickthanks all22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2016/product_working_group.2016-05-16-21.01.log.html22:00
*** markvoelker has quit IRC22:01
*** amitgandhinz has quit IRC22:01
*** tonytan4ever has quit IRC22:01
*** markvoelker has joined #openstack-meeting-alt22:01
*** leong has left #openstack-meeting-alt22:01
*** nadya has quit IRC22:02
*** mfedosin has quit IRC22:02
*** shaohe_feng has joined #openstack-meeting-alt22:02
*** MeganR has quit IRC22:03
*** pchadwick has left #openstack-meeting-alt22:03
*** KrishR has left #openstack-meeting-alt22:04
*** anush has quit IRC22:04
*** doug-fish has quit IRC22:07
*** sigmavirus24 is now known as sigmavirus24_awa22:09
*** mickeys has joined #openstack-meeting-alt22:09
*** shaohe_feng has quit IRC22:10
*** shaohe_feng has joined #openstack-meeting-alt22:10
*** dukhlov has joined #openstack-meeting-alt22:10
*** doug-fis_ has joined #openstack-meeting-alt22:13
*** dukhlov has quit IRC22:14
*** salv-orl_ has joined #openstack-meeting-alt22:14
*** doug-fi__ has joined #openstack-meeting-alt22:16
*** hichihara has quit IRC22:17
*** salv-orlando has quit IRC22:18
*** dukhlov has joined #openstack-meeting-alt22:18
*** ansmith has joined #openstack-meeting-alt22:18
*** doug-fis_ has quit IRC22:18
*** shaohe_feng has quit IRC22:20
*** diazjf has quit IRC22:20
*** ninag has joined #openstack-meeting-alt22:20
*** Sukhdev has quit IRC22:20
*** shaohe_feng has joined #openstack-meeting-alt22:20
*** Sukhdev has joined #openstack-meeting-alt22:21
*** doug-fi__ has quit IRC22:21
*** edtubill has joined #openstack-meeting-alt22:21
*** ninag_ has joined #openstack-meeting-alt22:22
*** ninag has quit IRC22:25
*** ninag_ has quit IRC22:26
*** tpsilva has quit IRC22:27
*** shaohe_feng has quit IRC22:30
*** shaohe_feng has joined #openstack-meeting-alt22:31
*** mixos has quit IRC22:34
*** cknight has joined #openstack-meeting-alt22:34
*** ninag has joined #openstack-meeting-alt22:34
*** piet has joined #openstack-meeting-alt22:36
*** ninag has quit IRC22:39
*** ninag has joined #openstack-meeting-alt22:40
*** doug-fish has joined #openstack-meeting-alt22:40
*** shaohe_feng has quit IRC22:40
*** shaohe_feng has joined #openstack-meeting-alt22:41
*** mickeys has quit IRC22:43
*** doug-fish has quit IRC22:44
*** ninag has quit IRC22:44
*** pradk- has quit IRC22:46
*** piet has quit IRC22:50
*** sdague has quit IRC22:50
*** shaohe_feng has quit IRC22:51
*** shaohe_feng has joined #openstack-meeting-alt22:51
*** piet has joined #openstack-meeting-alt22:52
*** qwebirc85867 has quit IRC22:53
*** carolbarrett_ has quit IRC22:54
*** zz_dimtruck is now known as dimtruck22:54
*** dukhlov has quit IRC22:58
*** shaohe_feng has quit IRC23:01
*** Sukhdev has quit IRC23:01
*** shaohe_feng has joined #openstack-meeting-alt23:01
*** doug-fish has joined #openstack-meeting-alt23:02
*** Arkady_Kanevsky has quit IRC23:02
*** mickeys has joined #openstack-meeting-alt23:03
*** spotz is now known as spotz_zzz23:04
*** dimtruck is now known as zz_dimtruck23:05
*** zz_dimtruck is now known as dimtruck23:05
*** cknight has quit IRC23:05
*** ddieterly has quit IRC23:06
*** markvoelker has quit IRC23:06
*** piet has quit IRC23:07
*** rcernin has quit IRC23:08
*** sbalukoff has joined #openstack-meeting-alt23:10
*** shaohe_feng has quit IRC23:11
*** xyang1 has quit IRC23:11
*** shaohe_feng has joined #openstack-meeting-alt23:12
*** dimtruck is now known as zz_dimtruck23:14
*** kszukielojc has quit IRC23:14
*** shaohe_feng has quit IRC23:21
*** shaohe_feng has joined #openstack-meeting-alt23:22
*** Leom_ has quit IRC23:22
*** edtubill has quit IRC23:22
*** edtubill has joined #openstack-meeting-alt23:25
*** IlyaG has joined #openstack-meeting-alt23:25
*** ninag has joined #openstack-meeting-alt23:30
*** vkramskikh_ has joined #openstack-meeting-alt23:31
*** IlyaG has quit IRC23:31
*** edtubill has quit IRC23:31
*** shaohe_feng has quit IRC23:32
*** sarob has quit IRC23:32
*** kei_yama has joined #openstack-meeting-alt23:32
*** shaohe_feng has joined #openstack-meeting-alt23:32
*** zz_dimtruck is now known as dimtruck23:33
*** ninag has quit IRC23:35
*** Sukhdev has joined #openstack-meeting-alt23:38
*** shaohe_feng has quit IRC23:42
*** shaohe_feng has joined #openstack-meeting-alt23:43
*** cloudrancher has quit IRC23:46
*** Swami has quit IRC23:47
*** mickeys has quit IRC23:51
*** mickeys has joined #openstack-meeting-alt23:52
*** shaohe_feng has quit IRC23:52
*** mickeys has quit IRC23:52
*** mickeys has joined #openstack-meeting-alt23:53
*** apetrich_ has quit IRC23:53
*** shaohe_feng has joined #openstack-meeting-alt23:53
*** pvaneck has quit IRC23:54

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