Thursday, 2016-05-19

*** tango has quit IRC00:02
*** shaohe_feng has quit IRC00:03
*** shaohe_feng has joined #openstack-meeting-alt00:04
*** ddieterly has joined #openstack-meeting-alt00:06
*** weshay has joined #openstack-meeting-alt00:07
*** gyee has quit IRC00:08
*** gyee has joined #openstack-meeting-alt00:08
*** Prem_ has quit IRC00:09
*** mickeys has quit IRC00:09
*** minwang2 has quit IRC00:10
*** tango has joined #openstack-meeting-alt00:10
*** harlowja_ has joined #openstack-meeting-alt00:11
*** tango has quit IRC00:11
*** banix has quit IRC00:12
*** mixos has joined #openstack-meeting-alt00:12
*** sdake has quit IRC00:13
*** shaohe_feng has quit IRC00:13
*** markvoelker has quit IRC00:13
*** shaohe_feng has joined #openstack-meeting-alt00:14
*** harlowja has quit IRC00:15
*** tango has joined #openstack-meeting-alt00:19
*** Akis_ has joined #openstack-meeting-alt00:20
*** mickeys has joined #openstack-meeting-alt00:20
*** Kuwagata has quit IRC00:20
*** akiskourtis has quit IRC00:20
*** kzaitsev_mb has joined #openstack-meeting-alt00:20
*** Kuwagata has joined #openstack-meeting-alt00:21
*** apetrich has joined #openstack-meeting-alt00:21
*** nadya has joined #openstack-meeting-alt00:22
*** shashank_hegde has quit IRC00:23
*** shaohe_feng has quit IRC00:23
*** shaohe_feng has joined #openstack-meeting-alt00:24
*** tango has quit IRC00:24
*** amitgandhinz has joined #openstack-meeting-alt00:25
*** ajmiller_ has joined #openstack-meeting-alt00:25
*** dimtruck is now known as zz_dimtruck00:26
*** nadya has quit IRC00:27
*** amitgandhinz has quit IRC00:29
*** ajmiller has quit IRC00:29
*** absubram has joined #openstack-meeting-alt00:30
*** tango has joined #openstack-meeting-alt00:31
*** shaohe_feng has quit IRC00:33
*** tango has quit IRC00:34
*** gyee has quit IRC00:34
*** shaohe_feng has joined #openstack-meeting-alt00:34
*** gyee has joined #openstack-meeting-alt00:34
*** julim has joined #openstack-meeting-alt00:35
*** stingaci has joined #openstack-meeting-alt00:35
*** mikal_ is now known as mikal00:35
*** ansmith has joined #openstack-meeting-alt00:40
*** hichihara has joined #openstack-meeting-alt00:40
*** Kuwagata has quit IRC00:40
*** kzaitsev_mb has quit IRC00:41
*** snackewm has quit IRC00:42
*** tango has joined #openstack-meeting-alt00:42
*** mtanino has quit IRC00:43
*** Kuwagata has joined #openstack-meeting-alt00:43
*** shaohe_feng has quit IRC00:44
*** ijw_ has joined #openstack-meeting-alt00:44
*** enriquetaso has joined #openstack-meeting-alt00:44
*** sigmavirus24 is now known as sigmavirus24_awa00:45
*** stingaci has quit IRC00:45
*** ijw has quit IRC00:46
*** hoangcx has joined #openstack-meeting-alt00:46
*** shaohe_feng has joined #openstack-meeting-alt00:47
*** tango has quit IRC00:47
*** hoangcx has left #openstack-meeting-alt00:47
*** julim has quit IRC00:49
*** kzaitsev_mb has joined #openstack-meeting-alt00:50
*** Kennan has quit IRC00:50
*** shaohe_feng has quit IRC00:54
*** shaohe_feng has joined #openstack-meeting-alt00:55
*** tango has joined #openstack-meeting-alt00:55
*** pvaneck has quit IRC00:55
*** ninag has joined #openstack-meeting-alt00:57
*** kzaitsev_mb has quit IRC00:57
*** zhurong has joined #openstack-meeting-alt00:58
*** tango has quit IRC01:00
*** Kennan has joined #openstack-meeting-alt01:01
*** ninag has quit IRC01:02
*** shaohe_feng has quit IRC01:04
*** shaohe_feng has joined #openstack-meeting-alt01:05
*** bana_k has quit IRC01:05
*** zhhuabj_ has quit IRC01:06
*** kevo has quit IRC01:08
*** spzala has joined #openstack-meeting-alt01:08
*** spzala has quit IRC01:08
*** spzala has joined #openstack-meeting-alt01:08
*** tango has joined #openstack-meeting-alt01:10
*** kzaitsev_mb has joined #openstack-meeting-alt01:11
*** shaohe_feng has quit IRC01:14
*** tango has quit IRC01:14
*** kzaitsev_mb has quit IRC01:16
*** shaohe_feng has joined #openstack-meeting-alt01:17
*** shu-mutou-AFK is now known as shu-mutou01:17
*** zhhuabj_ has joined #openstack-meeting-alt01:20
*** kzaitsev_mb has joined #openstack-meeting-alt01:21
*** Sukhdev has quit IRC01:22
*** doug-fish has joined #openstack-meeting-alt01:24
*** shaohe_feng has quit IRC01:25
*** shaohe_feng has joined #openstack-meeting-alt01:25
*** amitgandhinz has joined #openstack-meeting-alt01:25
*** mickeys has quit IRC01:26
*** kinapa has joined #openstack-meeting-alt01:26
*** doug-fish has quit IRC01:29
*** amitgandhinz has quit IRC01:31
*** ddieterly is now known as ddieterly[away]01:32
*** mickeys has joined #openstack-meeting-alt01:32
*** ddieterly[away] has quit IRC01:32
*** tango has joined #openstack-meeting-alt01:32
*** tlashchova has quit IRC01:34
*** tango has quit IRC01:34
*** baoli has joined #openstack-meeting-alt01:35
*** shaohe_feng has quit IRC01:35
*** shaohe_feng has joined #openstack-meeting-alt01:36
*** Sukhdev has joined #openstack-meeting-alt01:39
*** mickeys has quit IRC01:41
*** Sukhdev has quit IRC01:45
*** shaohe_feng has quit IRC01:45
*** mickeys has joined #openstack-meeting-alt01:46
*** shaohe_feng has joined #openstack-meeting-alt01:46
*** hichihara has quit IRC01:48
*** mickeys has quit IRC01:51
*** baoli has quit IRC01:51
*** baoli has joined #openstack-meeting-alt01:51
*** balajiiyer has joined #openstack-meeting-alt01:51
*** balajiiyer has quit IRC01:53
*** balajiiyer has joined #openstack-meeting-alt01:54
*** s3wong has quit IRC01:54
*** tango has joined #openstack-meeting-alt01:54
*** yamahata has joined #openstack-meeting-alt01:55
*** shaohe_feng has quit IRC01:55
*** shaohe_feng has joined #openstack-meeting-alt01:56
*** baoli has quit IRC01:57
*** tango has quit IRC01:59
*** pradk has joined #openstack-meeting-alt01:59
*** kzaitsev_mb has quit IRC02:00
*** zhhuabj_ has quit IRC02:05
*** yamamoto_ has joined #openstack-meeting-alt02:06
*** shaohe_feng has quit IRC02:06
*** pradk_ has joined #openstack-meeting-alt02:06
*** vishwanathj has quit IRC02:09
*** shaohe_feng has joined #openstack-meeting-alt02:09
*** tango has joined #openstack-meeting-alt02:10
*** pradk has quit IRC02:10
*** pradk_ is now known as pradk02:10
*** vinaypotluri has quit IRC02:10
*** tango has quit IRC02:11
*** mrmartin has joined #openstack-meeting-alt02:12
*** mrmartin has quit IRC02:14
*** shaohe_feng has quit IRC02:16
*** reldan has quit IRC02:16
*** shaohe_feng has joined #openstack-meeting-alt02:17
*** yonglihe has joined #openstack-meeting-alt02:17
*** sdake has joined #openstack-meeting-alt02:19
*** Kuwagata has quit IRC02:19
*** tango has joined #openstack-meeting-alt02:20
*** Kuwagata has joined #openstack-meeting-alt02:21
*** zhhuabj_ has joined #openstack-meeting-alt02:23
*** nadya has joined #openstack-meeting-alt02:23
*** sdake has quit IRC02:23
*** rossella_s has quit IRC02:24
*** rossella_s has joined #openstack-meeting-alt02:24
*** tango has quit IRC02:25
*** shaohe_feng has quit IRC02:26
*** shaohe_feng has joined #openstack-meeting-alt02:27
*** nadya has quit IRC02:27
*** amitgandhinz has joined #openstack-meeting-alt02:27
*** myoung|remote has joined #openstack-meeting-alt02:30
*** houming has joined #openstack-meeting-alt02:30
*** tango has joined #openstack-meeting-alt02:32
*** amitgandhinz has quit IRC02:32
*** muralia has joined #openstack-meeting-alt02:34
*** yamahata has quit IRC02:34
*** baoli has joined #openstack-meeting-alt02:35
*** iyamahat has quit IRC02:35
*** shaohe_feng has quit IRC02:36
*** shaohe_feng has joined #openstack-meeting-alt02:37
*** tango has quit IRC02:37
*** baoli has quit IRC02:39
*** baoli has joined #openstack-meeting-alt02:39
*** myoung|remote has quit IRC02:40
*** reedip has joined #openstack-meeting-alt02:41
*** fnaval has quit IRC02:42
*** baoli has quit IRC02:42
*** spzala has quit IRC02:43
*** baoli has joined #openstack-meeting-alt02:43
*** spzala has joined #openstack-meeting-alt02:43
*** spzala has quit IRC02:44
*** spzala has joined #openstack-meeting-alt02:44
*** tango has joined #openstack-meeting-alt02:44
*** shaohe_feng has quit IRC02:47
*** shaohe_feng has joined #openstack-meeting-alt02:47
*** woodster_ has quit IRC02:48
*** tango has quit IRC02:48
*** jesusaur has quit IRC02:49
*** fnaval has joined #openstack-meeting-alt02:51
*** fnaval has quit IRC02:51
*** fnaval has joined #openstack-meeting-alt02:51
*** banix has joined #openstack-meeting-alt02:52
*** jesusaur has joined #openstack-meeting-alt02:54
*** yuanying has quit IRC02:54
*** shaohe_feng has quit IRC02:57
*** enriquetaso has quit IRC02:57
*** shaohe_feng has joined #openstack-meeting-alt02:58
*** ajmiller has joined #openstack-meeting-alt02:59
*** ajmiller_ has quit IRC03:02
*** spzala has quit IRC03:03
*** vinaypotluri has joined #openstack-meeting-alt03:04
*** Kuwagata has quit IRC03:04
*** shaohe_feng has quit IRC03:07
*** shaohe_feng has joined #openstack-meeting-alt03:08
*** baoli has quit IRC03:09
*** cknight has quit IRC03:09
*** jesusaur has quit IRC03:10
*** noslzzp_ has quit IRC03:12
*** jesusaur has joined #openstack-meeting-alt03:13
*** ijw_ has quit IRC03:14
*** coolsvap has joined #openstack-meeting-alt03:17
*** shaohe_feng has quit IRC03:17
*** zhhuabj_ has quit IRC03:19
*** bana_k has joined #openstack-meeting-alt03:20
*** shaohe_feng has joined #openstack-meeting-alt03:21
*** tango has joined #openstack-meeting-alt03:21
*** tango has quit IRC03:25
*** yamamoto_ has quit IRC03:26
*** shaohe_feng has quit IRC03:28
*** shaohe_feng has joined #openstack-meeting-alt03:28
*** edtubill has joined #openstack-meeting-alt03:29
*** snackewm has joined #openstack-meeting-alt03:30
*** zz_dimtruck is now known as dimtruck03:31
*** zhhuabj_ has joined #openstack-meeting-alt03:32
*** tango has joined #openstack-meeting-alt03:33
*** ajmiller has quit IRC03:33
*** weshay has quit IRC03:35
*** tango has quit IRC03:35
*** shaohe_feng has quit IRC03:38
*** shaohe_feng has joined #openstack-meeting-alt03:38
*** ajmiller has joined #openstack-meeting-alt03:38
*** kei_yama has joined #openstack-meeting-alt03:40
*** minwang2 has joined #openstack-meeting-alt03:43
*** banix has quit IRC03:43
*** yuanying has joined #openstack-meeting-alt03:46
*** tango has joined #openstack-meeting-alt03:46
*** shaohe_feng has quit IRC03:48
*** shaohe_feng has joined #openstack-meeting-alt03:49
*** tango has quit IRC03:51
*** coreyob has quit IRC03:51
*** reedip has quit IRC03:53
*** ijw has joined #openstack-meeting-alt03:53
*** reedip has joined #openstack-meeting-alt03:55
*** jesusaur has quit IRC03:55
*** jesusaur has joined #openstack-meeting-alt03:58
*** shaohe_feng has quit IRC03:58
*** shaohe_feng has joined #openstack-meeting-alt03:59
*** edtubill has quit IRC04:00
*** bana_k has quit IRC04:01
*** flwang has quit IRC04:04
*** coolsvap has quit IRC04:04
*** ninag has joined #openstack-meeting-alt04:06
*** evgenyf has joined #openstack-meeting-alt04:06
*** amotoki has joined #openstack-meeting-alt04:06
*** edtubill has joined #openstack-meeting-alt04:08
*** yamamoto_ has joined #openstack-meeting-alt04:09
*** shaohe_feng has quit IRC04:09
*** Poornima has joined #openstack-meeting-alt04:09
*** shaohe_feng has joined #openstack-meeting-alt04:10
*** ninag has quit IRC04:10
*** evgenyf has quit IRC04:10
*** flwang has joined #openstack-meeting-alt04:11
*** mixos has quit IRC04:12
*** mixos has joined #openstack-meeting-alt04:12
*** tlashchova has joined #openstack-meeting-alt04:13
*** amitgandhinz has joined #openstack-meeting-alt04:16
*** tango has joined #openstack-meeting-alt04:17
*** dimtruck is now known as zz_dimtruck04:18
*** mixos has quit IRC04:18
*** tango has quit IRC04:18
*** tango has joined #openstack-meeting-alt04:18
*** shaohe_feng has quit IRC04:19
*** shaohe_feng has joined #openstack-meeting-alt04:20
*** ajmiller has quit IRC04:20
*** Sukhdev has joined #openstack-meeting-alt04:20
*** amitgandhinz has quit IRC04:21
*** nadya has joined #openstack-meeting-alt04:23
*** Sukhdev has quit IRC04:24
*** Sukhdev has joined #openstack-meeting-alt04:24
*** cartik has joined #openstack-meeting-alt04:26
*** nadya has quit IRC04:28
*** shaohe_feng has quit IRC04:29
*** shaohe_feng has joined #openstack-meeting-alt04:30
*** shashank_hegde has joined #openstack-meeting-alt04:30
*** shashank_hegde has quit IRC04:37
*** shashank_hegde has joined #openstack-meeting-alt04:39
*** shaohe_feng has quit IRC04:39
*** coolsvap has joined #openstack-meeting-alt04:40
*** shaohe_feng has joined #openstack-meeting-alt04:40
*** armax has quit IRC04:40
*** pgadiya has joined #openstack-meeting-alt04:42
*** zz_dimtruck is now known as dimtruck04:43
*** bana_k has joined #openstack-meeting-alt04:46
*** minwang2 has quit IRC04:49
*** shaohe_feng has quit IRC04:50
*** shashank_hegde has quit IRC04:51
*** shashank_hegde has joined #openstack-meeting-alt04:52
*** shaohe_feng has joined #openstack-meeting-alt04:53
*** gongysh has joined #openstack-meeting-alt04:53
*** armax has joined #openstack-meeting-alt04:54
*** ijw has quit IRC04:57
*** padkrish has joined #openstack-meeting-alt04:58
*** balajiiyer has quit IRC05:00
*** shaohe_feng has quit IRC05:00
*** shaohe_feng has joined #openstack-meeting-alt05:01
*** armax has quit IRC05:01
*** Kuwagata has joined #openstack-meeting-alt05:01
*** armax has joined #openstack-meeting-alt05:03
*** gongysh has quit IRC05:04
*** Kuwagata has quit IRC05:06
*** johnma has quit IRC05:07
*** pgadiya is now known as pgadiya|OSPBootC05:09
*** shaohe_feng has quit IRC05:10
*** shaohe_feng has joined #openstack-meeting-alt05:11
*** doug-fish has joined #openstack-meeting-alt05:11
*** doug-fish has quit IRC05:15
*** jprovazn has joined #openstack-meeting-alt05:17
*** amitgandhinz has joined #openstack-meeting-alt05:17
*** coolsvap has quit IRC05:20
*** nadya has joined #openstack-meeting-alt05:20
*** coolsvap has joined #openstack-meeting-alt05:20
*** shaohe_feng has quit IRC05:20
*** coolsvap has quit IRC05:21
*** coolsvap_ has joined #openstack-meeting-alt05:21
*** coolsvap_ is now known as coolsvap05:21
*** shaohe_feng has joined #openstack-meeting-alt05:21
*** amitgandhinz has quit IRC05:21
*** iyamahat has joined #openstack-meeting-alt05:24
*** irenab has joined #openstack-meeting-alt05:25
*** markvoelker has joined #openstack-meeting-alt05:27
*** iyamahat has quit IRC05:29
*** shaohe_feng has quit IRC05:31
*** shaohe_feng has joined #openstack-meeting-alt05:31
*** markvoelker has quit IRC05:34
*** jesusaur has quit IRC05:34
*** dimtruck is now known as zz_dimtruck05:35
*** stingaci has joined #openstack-meeting-alt05:37
*** shaohe_feng has quit IRC05:41
*** shaohe_feng has joined #openstack-meeting-alt05:42
*** dukhlov has joined #openstack-meeting-alt05:44
*** yamahata has joined #openstack-meeting-alt05:44
*** jesusaur has joined #openstack-meeting-alt05:44
*** fnaval has quit IRC05:48
*** fnaval_ has joined #openstack-meeting-alt05:49
*** dukhlov has quit IRC05:49
*** shaohe_feng has quit IRC05:51
*** dukhlov has joined #openstack-meeting-alt05:51
*** salv-orlando has joined #openstack-meeting-alt05:51
*** shaohe_feng has joined #openstack-meeting-alt05:52
*** Nikolay_St has quit IRC05:54
*** edtubill has quit IRC05:54
*** gyee has quit IRC05:56
*** fawadkhaliq has joined #openstack-meeting-alt05:57
*** Sukhdev has quit IRC05:57
*** doug-fish has joined #openstack-meeting-alt05:57
*** armax has quit IRC06:00
*** padkrish has quit IRC06:01
*** doug-fish has quit IRC06:01
*** shaohe_feng has quit IRC06:01
*** Ravikiran_K has joined #openstack-meeting-alt06:02
*** shaohe_feng has joined #openstack-meeting-alt06:02
*** dshakhray has joined #openstack-meeting-alt06:03
*** reedip_ has joined #openstack-meeting-alt06:09
*** nadya has quit IRC06:10
*** reedip has quit IRC06:10
*** dhlorenz has quit IRC06:10
*** nadya has joined #openstack-meeting-alt06:10
*** shaohe_feng has quit IRC06:12
*** rcernin has joined #openstack-meeting-alt06:12
*** shaohe_feng has joined #openstack-meeting-alt06:12
*** nadya has quit IRC06:15
*** amitgandhinz has joined #openstack-meeting-alt06:18
*** lpetrut has joined #openstack-meeting-alt06:22
*** shaohe_feng has quit IRC06:22
*** amitgandhinz has quit IRC06:22
*** kszukielojc has joined #openstack-meeting-alt06:25
*** shaohe_feng has joined #openstack-meeting-alt06:25
*** numans has joined #openstack-meeting-alt06:27
*** pt_15 has joined #openstack-meeting-alt06:29
*** dukhlov has quit IRC06:30
*** salv-orlando has quit IRC06:32
*** shaohe_feng has quit IRC06:32
*** shashank_hegde has quit IRC06:33
*** shashank_hegde has joined #openstack-meeting-alt06:34
*** shaohe_feng has joined #openstack-meeting-alt06:35
*** nadya has joined #openstack-meeting-alt06:39
*** tfukushima has joined #openstack-meeting-alt06:41
*** shaohe_feng has quit IRC06:42
*** anilvenkata has joined #openstack-meeting-alt06:43
*** nkrinner_afk is now known as nkrinner06:43
*** tremble has joined #openstack-meeting-alt06:45
*** tremble has quit IRC06:45
*** tremble has joined #openstack-meeting-alt06:45
*** shaohe_feng has joined #openstack-meeting-alt06:45
*** belmoreira has joined #openstack-meeting-alt06:45
*** bana_k has quit IRC06:48
*** dukhlov has joined #openstack-meeting-alt06:49
*** LanceHaig has joined #openstack-meeting-alt06:51
*** edwardb has quit IRC06:52
*** shaohe_feng has quit IRC06:53
*** shaohe_feng has joined #openstack-meeting-alt06:53
*** dukhlov has quit IRC06:54
*** dukhlov has joined #openstack-meeting-alt06:54
*** tango has quit IRC06:55
*** andreas_s has joined #openstack-meeting-alt06:58
*** pnavarro has joined #openstack-meeting-alt06:58
*** dshakhray has quit IRC06:59
*** dean has joined #openstack-meeting-alt06:59
*** sridharg has joined #openstack-meeting-alt06:59
*** dean is now known as Guest2493806:59
*** nadya has quit IRC07:01
*** dukhlov has quit IRC07:01
*** nadya has joined #openstack-meeting-alt07:01
*** dukhlov has joined #openstack-meeting-alt07:01
*** Kuwagata has joined #openstack-meeting-alt07:03
*** shaohe_feng has quit IRC07:03
*** shaohe_feng has joined #openstack-meeting-alt07:03
*** janscheurich has joined #openstack-meeting-alt07:04
*** nadya has quit IRC07:06
*** Kuwagata has quit IRC07:08
*** mrmartin has joined #openstack-meeting-alt07:13
*** shaohe_feng has quit IRC07:13
*** shaohe_feng has joined #openstack-meeting-alt07:13
*** rarcea has joined #openstack-meeting-alt07:15
*** akaszuba has joined #openstack-meeting-alt07:15
*** pnavarro has quit IRC07:15
*** mikelk has joined #openstack-meeting-alt07:16
*** dukhlov has quit IRC07:16
*** tlashchova has quit IRC07:17
*** amitgandhinz has joined #openstack-meeting-alt07:18
*** ccamacho has joined #openstack-meeting-alt07:20
*** amitgandhinz has quit IRC07:23
*** shaohe_feng has quit IRC07:23
*** shaohe_feng has joined #openstack-meeting-alt07:27
*** tango has joined #openstack-meeting-alt07:31
*** ninag has joined #openstack-meeting-alt07:32
*** tango has quit IRC07:32
*** shaohe_feng has quit IRC07:34
*** lpetrut has quit IRC07:34
*** shaohe_feng has joined #openstack-meeting-alt07:35
*** mrmartin has quit IRC07:35
*** irenab_ has joined #openstack-meeting-alt07:36
*** ihrachys has joined #openstack-meeting-alt07:37
*** ninag has quit IRC07:37
*** mickeys has joined #openstack-meeting-alt07:37
*** Nikolay_St has joined #openstack-meeting-alt07:37
*** irenab has quit IRC07:38
*** irenab_ is now known as irenab07:38
*** fawadkhaliq has quit IRC07:39
*** fawadkhaliq has joined #openstack-meeting-alt07:39
*** fwdit has joined #openstack-meeting-alt07:40
*** matrohon has joined #openstack-meeting-alt07:40
*** vinaypotluri has quit IRC07:40
*** ihrachys has quit IRC07:41
*** lpetrut has joined #openstack-meeting-alt07:43
*** MarkBaker has joined #openstack-meeting-alt07:43
*** shaohe_feng has quit IRC07:44
*** shaohe_feng has joined #openstack-meeting-alt07:45
*** ccamacho is now known as ccamacho|afk07:46
*** salv-orl_ has joined #openstack-meeting-alt07:47
*** salv-orl_ has quit IRC07:47
*** salv-orlando has joined #openstack-meeting-alt07:48
*** iyamahat has joined #openstack-meeting-alt07:51
*** fzdarsky has joined #openstack-meeting-alt07:51
*** reldan has joined #openstack-meeting-alt07:51
*** zeih has joined #openstack-meeting-alt07:53
*** mickeys has quit IRC07:54
*** mickeys has joined #openstack-meeting-alt07:54
*** shaohe_feng has quit IRC07:54
*** shaohe_feng has joined #openstack-meeting-alt07:55
*** HeOS has joined #openstack-meeting-alt07:57
*** mickeys has quit IRC07:59
*** hichihara has joined #openstack-meeting-alt08:00
*** tango has joined #openstack-meeting-alt08:01
*** dean has joined #openstack-meeting-alt08:02
*** dean is now known as Guest789508:02
*** reldan has quit IRC08:04
*** Guest24938 has quit IRC08:04
*** shaohe_feng has quit IRC08:04
*** HeOS has quit IRC08:07
*** shaohe_feng has joined #openstack-meeting-alt08:08
*** sgotliv_ has joined #openstack-meeting-alt08:08
*** dukhlov has joined #openstack-meeting-alt08:08
*** Niham has joined #openstack-meeting-alt08:09
*** Niham has quit IRC08:10
*** Niham has joined #openstack-meeting-alt08:10
*** hoangcx has joined #openstack-meeting-alt08:10
*** sgotliv has quit IRC08:10
*** hoangcx has left #openstack-meeting-alt08:10
*** Niham has quit IRC08:10
*** lpetrut has quit IRC08:11
*** kevo has joined #openstack-meeting-alt08:13
*** shaohe_feng has quit IRC08:15
*** Niham has joined #openstack-meeting-alt08:15
*** shaohe_feng has joined #openstack-meeting-alt08:16
*** iyamahat has quit IRC08:17
*** yamahata has quit IRC08:17
*** pnavarro has joined #openstack-meeting-alt08:19
*** amitgandhinz has joined #openstack-meeting-alt08:19
*** ihrachys has joined #openstack-meeting-alt08:20
*** amitgandhinz has quit IRC08:24
*** shaohe_feng has quit IRC08:25
*** shaohe_feng has joined #openstack-meeting-alt08:28
*** lpetrut has joined #openstack-meeting-alt08:29
*** nadya has joined #openstack-meeting-alt08:29
*** hoangcx has joined #openstack-meeting-alt08:29
*** hoangcx has left #openstack-meeting-alt08:29
*** kertis has joined #openstack-meeting-alt08:31
*** nadya has quit IRC08:34
*** shaohe_feng has quit IRC08:35
*** zhurong has quit IRC08:36
*** shaohe_feng has joined #openstack-meeting-alt08:36
*** zhurong has joined #openstack-meeting-alt08:37
*** shashank_hegde has quit IRC08:38
*** reldan has joined #openstack-meeting-alt08:39
*** nadya has joined #openstack-meeting-alt08:39
*** tango has joined #openstack-meeting-alt08:40
*** reldan has quit IRC08:40
*** lpetrut has quit IRC08:41
*** tango has quit IRC08:41
*** ccamacho|afk is now known as ccamacho08:45
*** shaohe_feng has quit IRC08:45
*** shaohe_feng has joined #openstack-meeting-alt08:46
*** neiljerram has quit IRC08:51
*** Na3iL has joined #openstack-meeting-alt08:54
*** shaohe_feng has quit IRC08:56
*** shaohe_feng has joined #openstack-meeting-alt08:57
*** zeih has quit IRC09:00
*** derekh has joined #openstack-meeting-alt09:00
*** jcoufal has joined #openstack-meeting-alt09:00
*** Kuwagata has joined #openstack-meeting-alt09:04
*** venkat has joined #openstack-meeting-alt09:05
*** shaohe_feng has quit IRC09:06
*** kinapa has quit IRC09:08
*** Kuwagata has quit IRC09:08
*** shaohe_feng has joined #openstack-meeting-alt09:09
*** Na3iL has quit IRC09:11
*** tango has joined #openstack-meeting-alt09:11
*** Guest7895 has quit IRC09:12
*** tango has quit IRC09:12
*** LanceHaig has quit IRC09:13
*** LanceHaig has joined #openstack-meeting-alt09:13
*** dean has joined #openstack-meeting-alt09:13
*** dean is now known as Guest4339009:14
*** shaohe_feng has quit IRC09:16
*** shaohe_feng has joined #openstack-meeting-alt09:17
*** lpetrut has joined #openstack-meeting-alt09:18
*** amitgandhinz has joined #openstack-meeting-alt09:20
*** eliqiao has quit IRC09:21
*** reldan has joined #openstack-meeting-alt09:21
*** ihrachys has quit IRC09:23
*** houming has quit IRC09:24
*** fawadkhaliq has quit IRC09:24
*** fawadkhaliq has joined #openstack-meeting-alt09:24
*** amitgandhinz has quit IRC09:25
*** shaohe_feng has quit IRC09:26
*** shaohe_feng has joined #openstack-meeting-alt09:28
*** kzaitsev_mb has joined #openstack-meeting-alt09:31
*** Niham has quit IRC09:32
*** zeih has joined #openstack-meeting-alt09:36
*** neiljerram has joined #openstack-meeting-alt09:36
*** shaohe_feng has quit IRC09:37
*** shaohe_feng has joined #openstack-meeting-alt09:38
*** zeih has quit IRC09:40
*** tango__ has joined #openstack-meeting-alt09:43
*** zhurong has quit IRC09:43
*** tango__ has quit IRC09:44
*** zhurong has joined #openstack-meeting-alt09:44
*** kzaitsev_mb has quit IRC09:45
*** Ravikiran_K has quit IRC09:46
*** shaohe_feng has quit IRC09:47
*** shaohe_feng has joined #openstack-meeting-alt09:48
*** thatsdone has joined #openstack-meeting-alt09:49
*** eslamelhusseiny has joined #openstack-meeting-alt09:50
*** thatsdone has quit IRC09:51
*** hichihara has quit IRC09:52
*** dshakhray has joined #openstack-meeting-alt09:56
*** tfukushima has quit IRC09:57
*** shaohe_feng has quit IRC09:57
*** tfukushima has joined #openstack-meeting-alt09:57
*** shaohe_feng has joined #openstack-meeting-alt09:58
*** eslamelhusseiny has quit IRC09:59
*** zeih has joined #openstack-meeting-alt10:03
*** dshakhray has quit IRC10:03
*** matrohon has quit IRC10:04
*** shu-mutou is now known as shu-mutou-AFK10:05
*** hoangcx has joined #openstack-meeting-alt10:05
*** dshakhray has joined #openstack-meeting-alt10:06
*** shaohe_feng has quit IRC10:07
*** zeih has quit IRC10:08
*** shaohe_feng has joined #openstack-meeting-alt10:08
*** Niham has joined #openstack-meeting-alt10:11
*** tango__ has joined #openstack-meeting-alt10:11
*** tango__ has quit IRC10:14
*** salv-orl_ has joined #openstack-meeting-alt10:14
*** rmart04 has joined #openstack-meeting-alt10:14
*** salv-orlando has quit IRC10:17
*** shaohe_feng has quit IRC10:18
*** shaohe_feng has joined #openstack-meeting-alt10:18
*** Niham has quit IRC10:20
*** amitgandhinz has joined #openstack-meeting-alt10:21
*** d0ugal has quit IRC10:24
*** amitgandhinz has quit IRC10:25
*** hoangcx has left #openstack-meeting-alt10:27
*** d0ugal has joined #openstack-meeting-alt10:28
*** shaohe_feng has quit IRC10:28
*** shaohe_feng has joined #openstack-meeting-alt10:29
*** tango has joined #openstack-meeting-alt10:29
*** dean has joined #openstack-meeting-alt10:29
*** dean is now known as Guest4024410:30
*** d0ugal has quit IRC10:31
*** tango has quit IRC10:31
*** tfukushima has quit IRC10:31
*** d0ugal has joined #openstack-meeting-alt10:31
*** Guest43390 has quit IRC10:32
*** apetrich has quit IRC10:33
*** Guest40244 has quit IRC10:34
*** sdague has joined #openstack-meeting-alt10:37
*** shaohe_feng has quit IRC10:38
*** shaohe_feng has joined #openstack-meeting-alt10:39
*** Niham has joined #openstack-meeting-alt10:40
*** Niham has quit IRC10:40
*** Niham has joined #openstack-meeting-alt10:41
*** ansiwen_ is now known as ansiwen10:41
*** Niham has quit IRC10:42
*** Niham has joined #openstack-meeting-alt10:42
*** Niham has quit IRC10:43
*** Niham has joined #openstack-meeting-alt10:44
*** reldan has quit IRC10:44
*** Niham has quit IRC10:45
*** Niham has joined #openstack-meeting-alt10:46
*** fzdarsky is now known as fzdarsky|afk10:47
*** ccamacho has quit IRC10:48
*** shaohe_feng has quit IRC10:48
*** yonglihe has quit IRC10:48
*** shaohe_feng has joined #openstack-meeting-alt10:49
*** mrmartin has joined #openstack-meeting-alt10:50
*** edwardb has joined #openstack-meeting-alt10:51
*** kzaitsev_mb has joined #openstack-meeting-alt10:52
*** kevo has quit IRC10:53
*** kevo has joined #openstack-meeting-alt10:53
*** njohnston has quit IRC10:54
*** weshay has joined #openstack-meeting-alt10:55
*** njohnston has joined #openstack-meeting-alt10:55
*** rmoe has joined #openstack-meeting-alt10:55
*** rmoe_ has quit IRC10:55
*** yamamoto_ has quit IRC10:56
*** edwardb has quit IRC10:57
*** shaohe_feng has quit IRC10:59
*** shaohe_feng has joined #openstack-meeting-alt10:59
*** mrmartin has quit IRC11:00
*** tango has joined #openstack-meeting-alt11:00
*** reldan has joined #openstack-meeting-alt11:01
*** tango has quit IRC11:01
*** edwardb has joined #openstack-meeting-alt11:02
*** Kuwagata has joined #openstack-meeting-alt11:04
*** zhurong has quit IRC11:04
*** YorikSar has quit IRC11:05
*** ccamacho has joined #openstack-meeting-alt11:06
*** YorikSar has joined #openstack-meeting-alt11:07
*** Kuwagata has quit IRC11:09
*** shaohe_feng has quit IRC11:09
*** shaohe_feng has joined #openstack-meeting-alt11:10
*** tellesnobrega is now known as tellesnobrega_af11:10
*** ccamacho has quit IRC11:13
*** YorikSar has quit IRC11:16
*** YorikSar has joined #openstack-meeting-alt11:16
*** edwardb has quit IRC11:17
*** edwardb has joined #openstack-meeting-alt11:18
*** shaohe_feng has quit IRC11:19
*** edwardb_ has joined #openstack-meeting-alt11:20
*** shaohe_feng has joined #openstack-meeting-alt11:20
*** amitgandhinz has joined #openstack-meeting-alt11:21
*** edwardb has quit IRC11:22
*** amitgandhinz has quit IRC11:26
*** ansmith has quit IRC11:26
*** mrmartin has joined #openstack-meeting-alt11:26
*** doug-fish has joined #openstack-meeting-alt11:28
*** doug-fish has quit IRC11:29
*** shaohe_feng has quit IRC11:29
*** shaohe_feng has joined #openstack-meeting-alt11:30
*** fawadkhaliq has quit IRC11:30
*** tango has joined #openstack-meeting-alt11:31
*** mtanino has joined #openstack-meeting-alt11:31
*** zeih has joined #openstack-meeting-alt11:31
*** tango has quit IRC11:32
*** mrmartin has quit IRC11:32
*** YorikSar_ has joined #openstack-meeting-alt11:33
*** ninag has joined #openstack-meeting-alt11:34
*** YorikSar has quit IRC11:35
*** tpsilva has joined #openstack-meeting-alt11:35
*** ninag has quit IRC11:38
*** zeih has quit IRC11:38
*** shaohe_feng has quit IRC11:40
*** shaohe_feng has joined #openstack-meeting-alt11:40
*** myoung|remote has joined #openstack-meeting-alt11:41
*** ccamacho has joined #openstack-meeting-alt11:45
*** Na3iL has joined #openstack-meeting-alt11:45
*** fwdit has quit IRC11:45
*** fwdit has joined #openstack-meeting-alt11:46
*** shaohe_feng has quit IRC11:50
*** shaohe_feng has joined #openstack-meeting-alt11:51
*** ccamacho has quit IRC11:52
*** zeih has joined #openstack-meeting-alt11:59
*** shaohe_feng has quit IRC12:00
*** shaohe_feng has joined #openstack-meeting-alt12:01
*** ddieterly has joined #openstack-meeting-alt12:03
*** coreyob has joined #openstack-meeting-alt12:08
*** shaohe_feng has quit IRC12:10
*** balajiiyer has joined #openstack-meeting-alt12:12
*** ccamacho has joined #openstack-meeting-alt12:12
*** shaohe_feng has joined #openstack-meeting-alt12:13
*** amrith is now known as _amrith_12:14
*** dean has joined #openstack-meeting-alt12:15
*** dean is now known as Guest7836112:15
*** ccamacho has quit IRC12:16
*** markvoelker has joined #openstack-meeting-alt12:16
*** ansmith has joined #openstack-meeting-alt12:18
*** Na3iL has quit IRC12:19
*** kei_yama has quit IRC12:19
*** tango has joined #openstack-meeting-alt12:20
*** dprince has joined #openstack-meeting-alt12:20
*** shaohe_feng has quit IRC12:21
*** tango has quit IRC12:21
*** shaohe_feng has joined #openstack-meeting-alt12:21
*** markvoelker has quit IRC12:21
*** piet has joined #openstack-meeting-alt12:22
*** amitgandhinz has joined #openstack-meeting-alt12:22
*** apetrich has joined #openstack-meeting-alt12:23
*** markvoelker has joined #openstack-meeting-alt12:24
*** ddieterly is now known as ddieterly[away]12:25
*** gcb has quit IRC12:25
*** amitgandhinz has quit IRC12:27
*** cartik has quit IRC12:29
*** balajiiyer has quit IRC12:29
*** stingaci has quit IRC12:31
*** shaohe_feng has quit IRC12:31
*** shaohe_feng has joined #openstack-meeting-alt12:31
*** sdague has quit IRC12:32
*** Ravikiran_K has joined #openstack-meeting-alt12:33
*** weshay is now known as weshay_mt12:33
*** weshay_mt is now known as weshay_mtg12:33
*** julim has joined #openstack-meeting-alt12:34
*** muralia_ has joined #openstack-meeting-alt12:34
*** piet has quit IRC12:36
*** piet has joined #openstack-meeting-alt12:37
*** tellesnobrega_af is now known as tellesnobrega12:37
*** ccamacho has joined #openstack-meeting-alt12:37
*** muralia has quit IRC12:37
*** gcb has joined #openstack-meeting-alt12:38
*** ninag has joined #openstack-meeting-alt12:38
*** banix has joined #openstack-meeting-alt12:39
*** _prad_ has joined #openstack-meeting-alt12:40
*** shaohe_feng has quit IRC12:41
*** markvoelker has quit IRC12:41
*** markvoelker has joined #openstack-meeting-alt12:42
*** venkat has quit IRC12:42
*** amitgandhinz has joined #openstack-meeting-alt12:42
*** shaohe_feng has joined #openstack-meeting-alt12:42
*** sdague has joined #openstack-meeting-alt12:43
*** ninag has quit IRC12:43
*** markvoelker_ has joined #openstack-meeting-alt12:46
*** ninag_ has joined #openstack-meeting-alt12:47
*** baoli has joined #openstack-meeting-alt12:48
*** panda has quit IRC12:48
*** ddieterly[away] is now known as ddieterly12:48
*** markvoelker_ has quit IRC12:48
*** panda has joined #openstack-meeting-alt12:49
*** baoli_ has joined #openstack-meeting-alt12:49
*** markvoelker_ has joined #openstack-meeting-alt12:49
*** markvoelker has quit IRC12:50
*** salv-orl_ has quit IRC12:50
*** myoung|remote has quit IRC12:51
*** shaohe_feng has quit IRC12:51
*** shaohe_feng has joined #openstack-meeting-alt12:52
*** baoli has quit IRC12:52
*** markvoelker_ has quit IRC12:55
*** mickeys has joined #openstack-meeting-alt12:55
*** dukhlov has quit IRC12:55
*** markvoelker has joined #openstack-meeting-alt12:55
*** mivanov has joined #openstack-meeting-alt12:55
*** ddieterly has quit IRC12:57
dirktoabctl, dirk, aplanas, IgorYozhikov, jruzicka: ping12:58
IgorYozhikovo/12:58
dirk#startmeeting rpm_packaging12:58
openstackMeeting started Thu May 19 12:58:53 2016 UTC and is due to finish in 60 minutes.  The chair is dirk. Information about MeetBot at http://wiki.debian.org/MeetBot.12:58
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:58
*** openstack changes topic to " (Meeting topic: rpm_packaging)"12:58
openstackThe meeting name has been set to 'rpm_packaging'12:58
toabctlhi12:59
mivanovhi12:59
*** mickeys has quit IRC12:59
dirkeveryone, please add your agenda items to13:01
dirk#link https://etherpad.openstack.org/p/openstack-rpm-packaging13:01
*** shaohe_feng has quit IRC13:02
*** shaohe_feng has joined #openstack-meeting-alt13:02
IgorYozhikovdirk, I have no topics today13:04
dirkthanks13:04
*** Frito has left #openstack-meeting-alt13:04
*** dshakhray has quit IRC13:05
*** Kuwagata has joined #openstack-meeting-alt13:05
dirk#topic renderspec version13:06
*** openstack changes topic to "renderspec version (Meeting topic: rpm_packaging)"13:06
IgorYozhikovdirk, when do you plan to release ?13:06
dirkcurrently we#re using renderspec from git for the gating, which turned out to be bad (we already broke gating during the summit)13:07
IgorYozhikovand should we use v like 1.0.0?13:07
dirkso I wanted to change it to use a release, which means we actually need to have a release13:07
dirkcurrently I think toabctl  is manually uploading releases13:07
dirkI wanted to give the openstack release process a try, but I stumbled on choosing a version number13:07
*** sdague has quit IRC13:07
dirkwould 0.1 be okay ?13:07
IgorYozhikovagree, released projects is much easier to package13:07
toabctlyes. but openstackci is already owner13:07
toabctl0.1 is fine for me13:08
dirkI think we should make it an release:independent project, which means we should choose post versioning13:08
dirk(semver)13:08
dirkI was just unsure if we want to start with 1.0.0 or with something < 1.0.013:08
IgorYozhikovtoabctl, does 0.1 looks fine according to versioning in OS13:08
dirk(basically semver says 0.x is not semver)13:08
IgorYozhikovdirk, ++13:09
toabctlas a independent project, can we still follow the global-requirements with renderspec?13:09
dirktoabctl: yes13:09
toabctlok. great13:09
dirkthe only trouble is that when we want to update a stable/ branch with a newer renderspec, we need to do that manually13:09
*** sdague has joined #openstack-meeting-alt13:10
*** Kuwagata has quit IRC13:10
IgorYozhikovdirk, should we make a tag 1st?13:10
dirkno13:10
dirkI think13:10
dirkso ++1 was on the version number 1.0.0 or 0.1 ?13:10
dirkIgorYozhikov: ^^13:10
IgorYozhikovsemver13:11
IgorYozhikov1.0.013:11
*** sridharg has quit IRC13:11
IgorYozhikovwe could use 1.0.0.0b1, b2, and so on in case of necessity13:12
*** markvoelker_ has joined #openstack-meeting-alt13:12
IgorYozhikovjust my thoughts13:12
*** markvoelker_ has quit IRC13:12
*** shaohe_feng has quit IRC13:12
*** dave-mccowan has joined #openstack-meeting-alt13:12
toabctl1 for 1.0.013:12
*** markvoelker_ has joined #openstack-meeting-alt13:12
* toabctl doesn't care about the number13:13
toabctl+1 I mean13:13
*** shaohe_feng has joined #openstack-meeting-alt13:13
dirkyeah, I'd just start with 1.0.0 for now13:13
dirk#agreed use 1.0.013:13
toabctldirk: are you going to prepare the needed changesets for project-config ?13:13
dirktoabctl: yep13:13
toabctlthx13:13
dirk#topic reviews13:14
*** openstack changes topic to "reviews (Meeting topic: rpm_packaging)"13:14
dirkhttps://review.openstack.org/#/q/status:open+project:openstack/rpm-packaging13:15
dirkI was looking at python-keystoneclient which is sort of the next one13:15
*** markvoelker has quit IRC13:15
IgorYozhikovunfortunately, https://review.openstack.org/#/c/311285/ can't pass our CI due spec-cleaner from pypi13:15
IgorYozhikovin master abs path is fixed13:16
toabctlalso the log update. for SUSE we need that13:16
dirkIgorYozhikov: there was a new spec_cleaner release13:16
*** nadya has quit IRC13:16
toabctldirk: that doesn't help for the /var/lib/obs problem13:17
toabctlIgorYozhikov: have you already prepared a PR to fix that?13:17
IgorYozhikovtoabctl, https://github.com/openSUSE/spec-cleaner/blob/spec-cleaner-0.8.7/setup.py has abs path13:17
*** noslzzp has joined #openstack-meeting-alt13:17
IgorYozhikovhttps://github.com/openSUSE/spec-cleaner/blob/master/setup.py has fix13:17
IgorYozhikovit installs into venv  fine13:18
*** sshnaidm has quit IRC13:18
IgorYozhikovI just checked locally13:18
IgorYozhikoveverything installed into venv13:19
dirkok, so we need another release13:19
IgorYozhikovdirk, looks so13:19
toabctldirk: do you know Tomáš irc nick?13:20
*** nadya has joined #openstack-meeting-alt13:20
dirktoabctl: scarabeus13:20
toabctlok. I'll ping him to get a new release out13:20
*** sshnaidm has joined #openstack-meeting-alt13:20
dirk#action toabctl get a spec_cleaner release out that fixes virtualenv install issue13:21
dirkI had a look at keystoneclient just a few hours ago13:21
IgorYozhikovtoabctl, thanx (^_^)13:21
dirk#link https://review.openstack.org/#/c/290472/13:21
*** noslzzp has quit IRC13:21
dirkand I couldn't understand the fuel build failure. IgorYozhikov or maximov13:21
dirkcan you look into that one?13:21
dirk(and everyone else: please review.. :) )13:22
IgorYozhikovdirk, already looking13:22
*** noslzzp has joined #openstack-meeting-alt13:22
*** shaohe_feng has quit IRC13:22
IgorYozhikovhttps://packaging-ci.fuel-infra.org/job/master-rpm-packaging-build/137/artifact/artifacts/python-keystoneclient-buildlog.txt/*view*/ looks strange, I'll investigate this failure today.13:23
*** sridharg has joined #openstack-meeting-alt13:23
IgorYozhikovtestr failed13:23
*** jdob has joined #openstack-meeting-alt13:23
dirkI'm also lacking desparate reviews on https://review.openstack.org/#/c/297112/13:24
*** shaohe_feng has joined #openstack-meeting-alt13:25
toabctldirk: do we want to use global-requirements or upper-constrains ?13:25
IgorYozhikovdirk, looks like file is outdated since it was uploaded13:25
*** sridharg has quit IRC13:25
IgorYozhikovyes, this is the topic13:25
IgorYozhikovg-r || u-c13:25
IgorYozhikovthanx toabctl13:25
*** sridharg has joined #openstack-meeting-alt13:25
dirkIgorYozhikov: imho we should use global-requirements13:26
*** irenab has quit IRC13:26
dirkwe should aim for packaging upper constraints, but the requirements in the spec file should be the lower bound imho13:26
dirkI saw the discussion on the mailing list, I think that was the conclusion there as well but maybe I misread it13:27
IgorYozhikovdirk, so, Requires >= g-r, dependencies*.rpm should be updated according to u-c. Right?13:27
dirkyes13:27
toabctldirk: have you already checked if we can get this file automatically updated with the bot?13:28
toabctlanyway - we can handle that later.13:28
dirktoabctl: currently it only updates requirements.txt or test-requirements.txt13:29
dirkthe bot I mean13:29
toabctla new spec-cleaner release is on its way :)13:29
dirkwe probably have to add a special case for that13:29
*** MarkBaker has quit IRC13:29
IgorYozhikovIt could bring complexity in tracking of versions changes. I ncase when u-c versions used - yum||zypper will take care13:29
dirkunless we just want to rename it to requirements.txt13:29
*** dshakhray has joined #openstack-meeting-alt13:30
toabctldirk: it's also on a different path...13:30
IgorYozhikovjust my thoughts13:30
dirktoabctl: huh?13:31
dirkits in the root dir13:31
toabctloh13:31
toabctlok13:31
dirkIgorYozhikov: I'm not sure I understand that.. zypper uses the newest available version always (and when you update from an existing version, it will use the newest one that is installable without conflicts unless you force it, which will then cause a conflict dialog)13:32
dirkso using a lower bound just gives you the flexibility of choosing to go with an older than the most current version13:32
*** ddieterly has joined #openstack-meeting-alt13:32
dirkit doesn't cause any other issue13:32
dirkI don't know enough about yum to understand though if that is any different there13:32
*** shaohe_feng has quit IRC13:32
*** mtanino has quit IRC13:33
*** shaohe_feng has joined #openstack-meeting-alt13:33
IgorYozhikovdirk, just trying to be more closer to current versions, this could help in case of projects will raise lower bounds which could be still << then values in u-c13:34
IgorYozhikovthat's it13:35
*** jtomasek_ has joined #openstack-meeting-alt13:35
IgorYozhikovanyway, got your point of view and it is clear 4 me13:35
dirkIgorYozhikov: yeah, my secret master plan is to write a script to review the cases where lower bounds and uc are way out of sync13:36
dirkand then run a test build with projects bound to the lower boudns to see if it still works13:36
dirkso e.g. lower bounds should be meaningful13:36
dirkfrom my current experience I don't think there are a lot of cases where lower bounds isn't "correct"13:37
IgorYozhikovo i c13:37
dirkIgorYozhikov: see 3.4.2 in https://etherpad.openstack.org/p/requirements-tasks13:39
dirkso can we move forward with the global-requirements.txt copy file ?13:39
dirkI think currently we don't generate spec files with lower bounds anymore, I would like to get that fixed13:39
dirkcurrent state is not useable for SUSE anymore13:39
dirkplease add your reviews to https://review.openstack.org/#/c/297112/13:40
dirktia13:40
*** jdob has quit IRC13:40
dirkany other topics ?13:40
dirkotherwise will people join next week ?13:40
dirkits a public holiday here13:40
IgorYozhikovdirk, file is old, may be it could be better to update it 1st?13:40
dirk#topic next meeting slot13:40
*** openstack changes topic to "next meeting slot (Meeting topic: rpm_packaging)"13:40
dirkIgorYozhikov: sure, will do13:40
IgorYozhikovand I guess 4 mitaka branch too :)13:41
IgorYozhikovgreat13:41
dirkIgorYozhikov: yeah, one step at a time..13:42
*** dukhlov has joined #openstack-meeting-alt13:42
dirktoabctl: would you be able to join next week?13:42
*** Na3iL has joined #openstack-meeting-alt13:42
*** shaohe_feng has quit IRC13:43
toabctldirk: yes. why not?13:43
IgorYozhikovI'll be here13:43
dirktoabctl: its a public holiday13:43
dirk:-)13:43
dirkok, then cya next week same time!13:43
toabctldirk: ah. only in south germany I guess13:43
dirk#endmeeting13:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:44
openstackMeeting ended Thu May 19 13:44:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rpm_packaging/2016/rpm_packaging.2016-05-19-12.58.html13:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rpm_packaging/2016/rpm_packaging.2016-05-19-12.58.txt13:44
openstackLog:            http://eavesdrop.openstack.org/meetings/rpm_packaging/2016/rpm_packaging.2016-05-19-12.58.log.html13:44
dirktoabctl: maybe, true13:44
dirkok. nevermind then13:44
*** markvoelker_ has quit IRC13:44
*** ddieterly is now known as ddieterly[away]13:45
*** shaohe_feng has joined #openstack-meeting-alt13:45
*** Niham has quit IRC13:45
*** tellesnobrega is now known as tellesnobrega_af13:46
*** anilvenkata has quit IRC13:47
*** mivanov has left #openstack-meeting-alt13:48
*** jmckind has joined #openstack-meeting-alt13:48
*** piet has quit IRC13:48
*** spotz_zzz is now known as spotz13:50
*** Kuwagata has joined #openstack-meeting-alt13:51
*** zhurong has joined #openstack-meeting-alt13:52
*** ddieterly[away] is now known as ddieterly13:52
*** shaohe_feng has quit IRC13:53
*** shaohe_feng has joined #openstack-meeting-alt13:54
*** piet has joined #openstack-meeting-alt13:55
*** belmoreira has quit IRC13:55
*** belmoreira has joined #openstack-meeting-alt13:55
*** pgadiya|OSPBootC has quit IRC13:56
*** huichun has joined #openstack-meeting-alt13:59
*** MarkBaker has joined #openstack-meeting-alt14:00
ddieterly#startmeeting freezer14:00
openstackMeeting started Thu May 19 14:00:29 2016 UTC and is due to finish in 60 minutes.  The chair is ddieterly. 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: freezer)"14:00
openstackThe meeting name has been set to 'freezer'14:00
*** yangyapeng has joined #openstack-meeting-alt14:00
*** vponomaryov has joined #openstack-meeting-alt14:01
*** ninag_ has quit IRC14:02
*** woodster_ has joined #openstack-meeting-alt14:02
ddieterlyhi ice cubes14:02
yangyapenghi14:02
ddieterlyattendance?14:02
ddieterlyo/14:02
yangyapeng:)14:03
*** Guest78361 has quit IRC14:03
*** ninag has joined #openstack-meeting-alt14:03
*** shaohe_feng has quit IRC14:03
ddieterlyjust us two? wow14:04
*** shaohe_feng has joined #openstack-meeting-alt14:04
ddieterlyagenda at https://etherpad.openstack.org/p/freezer_meetings14:04
ddieterlyfeel free to add to it14:04
*** ninag_ has joined #openstack-meeting-alt14:05
*** daemontool has joined #openstack-meeting-alt14:05
daemontoolo/14:05
yangyapenghaha14:05
ddieterlyhey daemontool!14:05
ddieterlybig hugs14:05
daemontoolhi ddieterly who's the chair?14:06
ddieterlyi am14:06
daemontoolddieterly, only with harms please14:06
daemontoolhaha14:06
*** Niham has joined #openstack-meeting-alt14:06
ddieterlyof course14:06
daemontoolok14:06
ddieterlycan we get some items on the agenda?14:06
daemontoolok14:06
daemontoolthe url please?14:06
daemontoolthis one right https://etherpad.openstack.org/p/freezer_meetings14:07
ddieterlyhttps://etherpad.openstack.org/p/freezer_meetings14:07
*** salv-orlando has joined #openstack-meeting-alt14:07
clsacramentohello14:07
*** piet has quit IRC14:07
*** balajiiyer has joined #openstack-meeting-alt14:07
*** ninag has quit IRC14:07
daemontoolclsacramento, hi14:07
ddieterlygreetings to all14:08
clsacramentodaemontool: buon giorno, come stai?14:08
ddieterly#topic Tenant resource backup (aka DRaaS)14:08
szaherddieterly:  hi14:08
*** openstack changes topic to "Tenant resource backup (aka DRaaS) (Meeting topic: freezer)"14:08
ddieterlyhi szaher!14:08
ddieterlydaemontool take it away, please14:09
clsacramentoabout this Tenant resource backup (aka DRaaS), didn't you find out that there was another project doing it already?14:10
ddieterlysmaug?14:10
clsacramentoyes, I think that was it14:10
daemontoolI'm here14:11
daemontoolsorry14:11
*** kertis has quit IRC14:11
daemontoolclsacramento, ola14:11
daemontoolso14:11
daemontoolduring the summit14:11
daemontoolthe design session14:11
daemontoolthere were more then one person in the room14:11
daemontoolfrom different companies14:11
*** spotz is now known as spotz_zzz14:11
*** thatsdone has joined #openstack-meeting-alt14:11
daemontoolasking for a complete backup of all the tenant resources14:11
daemontoolsuch as14:11
*** salv-orlando has quit IRC14:11
*** thatsdone has quit IRC14:12
daemontoolvms, volumes, networks config, identity related etc14:12
daemontoolto be restored14:12
daemontoolon the same os platform14:12
daemontoolor on a new one14:12
*** yamamoto has joined #openstack-meeting-alt14:12
daemontoolit is quite interesting14:12
daemontooland more and more users are asking for it14:12
*** thatsdone has joined #openstack-meeting-alt14:12
*** edtubill has joined #openstack-meeting-alt14:13
clsacramentoyes, I really like this feature14:13
clsacramentoIt looks like vmware vApp and it is quite nice14:13
daemontoolyes14:13
daemontoolclsacramento, exactly14:13
daemontoolthat would make us competitive :)14:13
daemontoolso I've tried to summarize somethign here14:13
daemontoolhttps://blueprints.launchpad.net/freezer/+spec/tenant-backup14:13
daemontoollet me know14:13
daemontoolany feedback14:13
*** shaohe_feng has quit IRC14:13
daemontoolso everythhing backed up taken from the API,14:14
daemontoolsuch as metadata, glance image, snapshots14:14
*** jmckind_ has joined #openstack-meeting-alt14:14
daemontoolvolumes etc etc14:14
szaherdaemontool: Ciao14:14
*** shaohe_feng has joined #openstack-meeting-alt14:14
szaherThere is a project from Mirantis called Pumphouse they used to do something similar14:14
szaherhttps://github.com/Mirantis/pumphouse14:14
clsacramentoI would add not only in case of lost, but in case of willing to replicate a lab too, it is very useful for that14:15
szaherI don't know why they stopped but they were backing up resources then upgrade the cloud then restore resources again14:15
*** jonaspf1 has joined #openstack-meeting-alt14:15
szaherMay be we can take a look we might find something useful14:15
ddieterlywondering about load on the api's and performance of that kind of approach14:16
daemontoollet's reuse whatever can be reused of course14:16
daemontoolyes14:16
daemontoolddieterly, that's a good point, I think it depends on how many you execute simultaneously14:16
daemontoolor in a short time windows14:16
*** yuval has joined #openstack-meeting-alt14:16
*** jmckind has quit IRC14:17
*** edtubill has quit IRC14:17
ddieterlyi think we need more research on pumphouse and smaug14:17
*** zhurong has quit IRC14:18
*** myoung|remote has joined #openstack-meeting-alt14:18
ddieterlyanyone want to take an action item and report back next week?14:19
clsacramentodaemontool: I was thinking, it is easier on the same cloud because all images, volumes and vm emephemeral disks are already in there backend storage, we can only duplicate them. If it is to recover on a different cloud we would have to download all of that to some other media and make it available on the other cloud...14:20
*** _amrith_ is now known as amrith14:20
clsacramentoddieterly: I can do that14:20
szaherddieterly: I don't know if we can only backup mysql database which contains all the required metadata and Openstack will automatically create this resources once we restore the database again and only backup volumes, instances, images and so ?14:20
szahers/this/these/g14:20
clsacramentoszaher: I dont think backing up the database is the best approach. We should be able to get all the info we need to backup from the APIs14:21
ddieterlyclsacramento thanks14:21
ddieterly#action clsacramento to investigate smaug and pumphouse14:21
szaherclsacramento: we need to know about the drawbacks of using this approach when we have a big deployment with hundreds of tenants and resources14:22
*** cknight has joined #openstack-meeting-alt14:22
*** myoung|remote has quit IRC14:22
ddieterlyszaher i don't follow your first point14:22
*** fwdit has quit IRC14:23
szaherddieterly: the database approach ?14:23
ddieterlyyes14:23
clsacramentoszaher: for example: if I insert a flavor in MySQL database, openstack automatically creates it for me?14:23
*** rossella_s has quit IRC14:23
*** shaohe_feng has quit IRC14:24
szaherclsacramento: I would say that Openstack stores it's own metadata in mysql database :) and I think yes it will create it automatically14:24
daemontoolok14:24
*** rossella_s has joined #openstack-meeting-alt14:24
clsacramentoszaher: I dont think it does, but I'll check this out14:24
szaherclsacramento: you can worry about neutron namespaces for example as I am not sure if it will be create automatically or not14:24
daemontoolwe need to get the metadata and data from the API14:25
*** cknight1 has joined #openstack-meeting-alt14:25
szaherclsacramento: What about when we take the cloud down then up again ?? How Openstack recovers ?14:25
*** shaohe_feng has joined #openstack-meeting-alt14:25
daemontoolor we'll have tenants executing actions directly to the db14:25
daemontoolwhich is not good14:25
daemontoollet's have a conversation on the freezer chan for this14:25
daemontooland move forward with the topics?14:25
daemontool:)14:25
szaherGuys, What I am saying here let's review both approaches :) what will happen at big scales ?14:25
daemontoolok14:26
*** iyamahat has joined #openstack-meeting-alt14:26
ddieterlydaemontool sounds good14:26
szaherdaemontool: OK14:26
daemontool++14:26
ddieterly#topic DAR14:26
*** openstack changes topic to "DAR (Meeting topic: freezer)"14:26
ddieterlyok, so currently our incremental restores are busticated under certain conditions14:26
ddieterlyseems to be an issue with TAR14:26
ddieterlyDAR handles the condition quite well14:26
*** myoung has joined #openstack-meeting-alt14:26
*** cknight has quit IRC14:27
ddieterlycould we investigate a DAR engine as szaher has suggested14:27
daemontoolddieterly, yes you are right, in my opinion, I'd remove the deps to binaries..14:27
daemontoolasap14:27
daemontoolI'd focus on that, rather investing time in contingencies solutions14:27
clsacramentosorry, what's DAR?14:27
ddieterlynot sure what you mean14:27
*** belmoreira has quit IRC14:27
daemontooltar, gzip, dar14:27
daemontoolare all binaries14:27
ddieterlyyes14:28
daemontoolopenssl...14:28
*** sajeesh has joined #openstack-meeting-alt14:28
ddieterlyso, you want to implement that functionality directly in freezer instead of using the binaries?14:28
daemontoolI think we have to work to remove deps to those binaries14:28
daemontoolyes, there are modules done14:28
daemontoolthat does that14:28
daemontoolalready14:28
ddieterlyor just let users mix and match which ones to use?14:28
daemontoolso we'll be more portable14:28
daemontoolI think if we use the python modules, our life is easier14:29
ddieterlywhat modules?14:29
daemontoolalso for windows14:29
szaherreldan and I are working on some sort of refactoring freezer to be pluggable so hopefully we will be able to add engines but we need the refactoring part to be done first14:29
daemontoollike14:29
daemontoolbzip, tarfile, crypto.io14:29
daemontooland so on14:29
*** fawadkhaliq has joined #openstack-meeting-alt14:29
daemontoolthe rsync code14:29
daemontoolprobably the rsync code14:29
daemontoolcan remove tar or dar14:29
daemontoolby14:29
daemontoolbacking up the data14:29
ddieterlyso there is a python module that implements rsync directly?14:29
daemontoolonly based on inode14:29
daemontoolnpoe14:29
daemontoolwe need to get completed14:30
daemontoolthis14:30
daemontoolhttps://review.openstack.org/#/c/290461/14:30
daemontooland we have that14:30
daemontoolso the difference would be14:30
daemontoolto backup the whole file if the inode is changed14:30
daemontoolrather backup block14:30
daemontooland the tar approach will be quite the same14:30
daemontoolso tar, dar openssl14:30
daemontooletc14:30
daemontoolcan be removed14:31
*** mtanino has joined #openstack-meeting-alt14:31
daemontoolbut14:31
daemontoolit is just my opinion14:31
ddieterlyis this your implementation, or is it an existing well-known python module?14:31
daemontoolfor rsync14:32
daemontoolany module14:32
daemontooldoes not suits14:32
daemontoolthat's why that implementation14:32
*** ninag_ has quit IRC14:32
daemontoolif we finish taht14:32
daemontoolthen we have both inode and block based14:32
ddieterlydoes the rest of the team have an opinion on this?14:33
ddieterlyi'm still not sure what daemontool tool is saying14:33
*** fawadkhaliq has quit IRC14:33
*** Nikolay_St has quit IRC14:33
daemontoolddieterly, tar just check14:33
daemontoolinode modification14:33
daemontooland backup the whole file14:33
ddieterlyare we going to implement the functionality directly in freezer or is there an existing python module that does what tar/dar do?14:33
*** tango__ has joined #openstack-meeting-alt14:34
szaherddieterly: we need to discuss this before taking a decision14:34
daemontoolyes14:34
*** shaohe_feng has quit IRC14:34
ddieterlyof course14:34
daemontoolszaher,  well the engine approach14:34
daemontoolhas been throughtly discussed14:34
ddieterlytrying to understand what daemontool is saying14:34
*** shaohe_feng has joined #openstack-meeting-alt14:34
szaherdaemontool: The engine approach Yes and we agreed we will have mutliple engines and the user can choose what is the best one for him14:35
ddieterlyso, it looks like we could implement another 'engine' that uses dar14:35
daemontoolddieterly,  well yes14:35
ddieterlyor, we could do what daemontool is suggesting14:35
daemontoolthe rsync engine is being implemented14:35
daemontoolI just do not have time14:35
daemontoolto finish the restore14:35
szaherdaemontool: I thought we are going to remove tar and dar totally14:35
daemontoolbut the backup there it's working14:35
daemontoolszaher, yes14:35
*** Kuwagata_ has joined #openstack-meeting-alt14:36
daemontoolthat's what I'm advising for14:36
ddieterlywell, we don't have dar yet ;-)14:36
*** zeih has quit IRC14:36
daemontoolhaha14:36
szaher:D14:36
*** Kuwagata has quit IRC14:36
daemontoolddieterly, let's have this discussion later in the freezer chan14:36
daemontool?14:36
ddieterlyok14:36
ddieterlylet's move on14:36
ddieterlydaemontool is such a task master14:36
ddieterly#topic rsync status14:37
*** openstack changes topic to "rsync status (Meeting topic: freezer)"14:37
*** banix has quit IRC14:37
*** Niloofar has joined #openstack-meeting-alt14:38
daemontoolok14:38
daemontoolso rsync14:38
*** belmoreira has joined #openstack-meeting-alt14:38
daemontoolI need help guys14:38
daemontoolthe restore needs to be done14:38
daemontoolif anyone is interested let me know14:38
daemontoolkeep in consideration that is a tough bone14:38
ddieterly#action let daemontool know if you want to help with rysnc https://review.openstack.org/#/c/290461/14:38
daemontoolddieterly, are you interested?14:39
ddieterlyi am working on hpe hlm most of the time14:39
daemontoolit is also incredibly inteersting14:39
ddieterly:-(14:39
daemontoolok14:39
daemontoolnp14:39
ddieterlybut, i will take a look at it for sure14:39
daemontoolty14:40
ddieterlynext topic?14:40
daemontoolyes14:40
ddieterly#topic ATT architecture meeting14:40
*** openstack changes topic to "ATT architecture meeting (Meeting topic: freezer)"14:40
daemontoolok we need to decide how do we manage cases where Company wants to contribute14:41
daemontoolwithout write code14:41
ddieterlythis seems like something pierre should be involved with as he is the PTL14:41
daemontoollike at Architecture level and so on14:41
daemontoolyes I had a word with Pierre14:41
daemontoolabout this14:41
*** irenab has joined #openstack-meeting-alt14:41
*** noslzzp has quit IRC14:41
daemontoolhe asked me to drive it14:41
ddieterlywell, if they want to contribute w/o writing code, they can submit a bp14:41
daemontoolwe need to have a meeting to explain them what freezer is14:42
daemontoolwhat it does etc14:42
*** pgadiya has joined #openstack-meeting-alt14:42
daemontoolI think we should do a video14:42
daemontoolFreezer Intro Video14:42
*** cloudtrainme has joined #openstack-meeting-alt14:42
daemontoolsomething like that14:42
daemontoolan points new comers to that14:42
*** piet has joined #openstack-meeting-alt14:42
ddieterlythat would be great14:42
daemontoolm3m0, ?14:42
daemontoolping14:42
daemontoolyou are good with videos :)14:42
ddieterlyhe is on holiday14:42
daemontoolah ok14:42
daemontoolm3m0,  and or vannif?14:43
ddieterlym3m0 will be back next week14:43
daemontoolok14:43
*** yamahata has joined #openstack-meeting-alt14:43
daemontoolI'll engage ATT for that14:43
ddieterlyi'm not photogenic14:43
ddieterlylol14:43
*** noslzzp has joined #openstack-meeting-alt14:43
daemontoolddieterly, haha well you need to be videogenic14:43
daemontoolok next14:43
daemontool?14:43
ddieterlysure14:43
ddieterly#topic freezer overview meeting14:44
*** openstack changes topic to "freezer overview meeting (Meeting topic: freezer)"14:44
ddieterlywhat is that?14:44
*** sdake_ has joined #openstack-meeting-alt14:44
daemontoolRH14:44
daemontoolRH freezer14:44
daemontoolsame as ATT14:44
ddieterlyoh14:44
ddieterlysame deal?14:44
daemontoolyes14:44
*** shaohe_feng has quit IRC14:44
ddieterlyso, are you going to arrange the meetings or is pierre?14:44
daemontoolso they are evaluating the backup/dr technology14:44
daemontoolto use14:44
daemontoolI'm going to do it14:44
*** niloofar_ has joined #openstack-meeting-alt14:45
daemontoolhave to send an email14:45
ddieterlyare the meetings in europe or via video chat?14:45
daemontoolbut wanted to wait next week14:45
daemontoolvideo14:45
*** Niloofar has quit IRC14:45
daemontoolhangout I think14:45
daemontoolfrescof__,  ping14:45
*** yamamoto has quit IRC14:45
daemontooldo we have a last freezer presentation?14:45
daemontoolwe could use the summit one?14:45
*** shaohe_feng has joined #openstack-meeting-alt14:45
daemontoolis that ok do you think?14:45
szaherdaemontool: fresco is not at his desk14:46
daemontoolclsacramento, szaher ?14:46
daemontoolok14:46
daemontoolszaher,  ask him please14:46
ddieterlyi think a video meeting with them going over the slides that arun uses would be good14:46
clsacramentosorry, what is RH?14:46
daemontoolRedHat14:46
ddieterlyfrescof__ is on holiday14:46
daemontoolok14:46
clsacramentook14:46
*** sridharg has quit IRC14:46
clsacramentoI was thinking of Human Resources in Portuguese :S14:46
daemontoolhaha14:46
daemontoolddieterly, can anyone make a plain openstack preso out of that?14:47
daemontoolwithout companies logos?14:47
ddieterly#action daemontool will set up meetings14:47
daemontooljust openstack and freezer logo?14:47
daemontoolI can do it14:47
daemontoolok14:47
ddieterlydaemontool i think it would be easy to sanitize them and use them14:47
ddieterlyit is public info14:47
*** tellesnobrega_af is now known as tellesnobrega14:47
*** sigmavirus24_awa is now known as sigmavirus2414:48
*** muralia_ has left #openstack-meeting-alt14:48
daemontoolddieterly,  ok14:48
daemontoolsomeone has to do that thought14:48
ddieterlydaemontool just don't tell anyone ;-)14:48
daemontoolhaha14:48
daemontoolok14:48
ddieterlynext topic?14:48
daemontool#action ddieterly sanitize something14:48
daemontoollol14:48
ddieterlyyea, i'm good at that14:49
*** tellesnobrega is now known as tellesnobrega_af14:49
*** tellesnobrega_af is now known as tellesnobrega14:49
ddieterlyespecially toilets14:49
*** salv-orlando has joined #openstack-meeting-alt14:49
*** tonytan4ever has joined #openstack-meeting-alt14:49
ddieterly#topic Golang14:49
*** openstack changes topic to "Golang (Meeting topic: freezer)"14:49
*** snackewm has quit IRC14:49
ddieterlydid everybody see this? https://review.openstack.org/#/c/290461/14:49
daemontoolyes14:50
ddieterlyoops wrong link14:50
daemontoolddieterly,  you proposed Java in the mail thread14:50
daemontoolhaha14:50
ddieterlyhttps://review.openstack.org/#/c/312267/314:50
ddieterlyso, maybe we could benifit from Go in freezer?14:50
daemontoolddieterly,  I think so14:50
daemontoolyes14:50
daemontoolbut14:51
ddieterlyawesome14:51
daemontoollast year14:51
daemontoolI've tried freezer executing14:51
daemontoolactions14:51
daemontoolunder pypy14:51
daemontooland it was really fast14:51
ddieterlyso we should look for ways to incorporate Go in places to optimize performance14:51
ddieterlyi can't tell if this passed or not14:52
ddieterlydoes anyone know?14:52
daemontoolddieterly,  I don't know14:53
szaherI guess the workflow is not +114:53
daemontoolI think there are taks we perform14:53
*** edtubill has joined #openstack-meeting-alt14:53
daemontoolintensive14:53
ddieterlyis anyone on freezer opposed to using go?14:53
daemontoolfor rsync14:53
daemontoolmath14:53
*** spotz_zzz is now known as spotz14:53
daemontoolI'm in favor14:53
daemontooljust wonder if we really need it and where14:53
szaherdaemontool: +114:53
*** fesp has joined #openstack-meeting-alt14:53
*** mixos has joined #openstack-meeting-alt14:54
daemontoolok14:54
*** weshay_mtg is now known as weshay14:54
daemontoolall good anyway14:54
daemontoolfor me14:54
ddieterly#startvote Should we allow Go in Freezer when it makes sense?14:54
openstackBegin voting on: Should we allow Go in Freezer when it makes sense? Valid vote options are Yes, No.14:54
openstackVote using '#vote OPTION'. Only your last vote counts.14:54
daemontoola part the fact tha tI do not know Go14:54
clsacramentofrom the last comment on the bp, not sure if approved14:54
*** markstur_ has joined #openstack-meeting-alt14:54
*** shaohe_feng has quit IRC14:54
ddieterly#vote yes14:54
daemontool#vote yes14:55
clsacramento#vote yes14:55
*** shaohe_feng has joined #openstack-meeting-alt14:55
daemontoolusing new IRC features lol14:55
szaher#vote yes14:55
ddieterlyi've always wanted to use that!14:55
ddieterlyhaha14:55
ddieterly#showvote14:55
*** dprince has quit IRC14:56
*** julim has quit IRC14:56
ddieterly#endvote14:56
szaherI would say yes if we really need it badly14:56
openstackVoted on "Should we allow Go in Freezer when it makes sense?" Results are14:56
*** balajiiyer has quit IRC14:56
*** dprince has joined #openstack-meeting-alt14:56
*** julim has joined #openstack-meeting-alt14:56
ddieterly#showvote14:56
*** ninag_ has joined #openstack-meeting-alt14:56
*** Poornima has quit IRC14:56
daemontoolddieterly,  ok, I'm glad you are enjoying it14:57
ddieterlyok, so the vote results are logged in the meeting minutes14:57
* daemontool hug ddieterly lol14:57
ddieterlyok, any other items in the time remaining?14:57
*** jseiler has joined #openstack-meeting-alt14:57
daemontoolI think we are good14:57
*** jmckind has joined #openstack-meeting-alt14:57
daemontoolnot from me14:57
ddieterlyhpe folks have a standup in a couple of mins14:57
*** dustins has joined #openstack-meeting-alt14:57
szaherah guys the upgrade to falcon middleware is merged so you can submit changes to freezer-api14:58
*** fnaval_ has quit IRC14:58
ddieterlyszaher cool14:58
*** xyang2 has joined #openstack-meeting-alt14:58
szaherand If you have a change upstream please, submit a recheck14:58
ddieterlydaemontool hugs back to you14:58
daemontoolszaher,  brilliant14:58
daemontoolddieterly,  not from the back please, that doesn't look good14:58
*** gouthamr has joined #openstack-meeting-alt14:58
daemontoollol14:58
*** aovchinnikov has joined #openstack-meeting-alt14:59
ddieterlydaemontool ok, you can stop the double entendre please14:59
daemontoolthanks all14:59
ddieterlyciao everybody!14:59
szaherciao ciao :)14:59
clsacramentodaemontool: a presto!14:59
ddieterly#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu May 19 15:00:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/freezer/2016/freezer.2016-05-19-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/freezer/2016/freezer.2016-05-19-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/freezer/2016/freezer.2016-05-19-14.00.log.html15:00
*** eharney has joined #openstack-meeting-alt15:00
bswartz#startmeeting manila15:00
openstackMeeting started Thu May 19 15:00:19 2016 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** ganso has joined #openstack-meeting-alt15:00
*** openstack changes topic to " (Meeting topic: manila)"15:00
openstackThe meeting name has been set to 'manila'15:00
*** jeffbrown has joined #openstack-meeting-alt15:00
toabctlhi15:00
cknight1Hi15:00
gouthamrhello o/15:00
bswartzhello15:00
gansohello15:00
*** jmckind_ has quit IRC15:00
tpsilvahello15:00
aovchinnikovhi15:00
sgotliv_o/15:00
jseilerhi15:00
dustinshey \o15:00
xyang2hi15:00
vponomaryovHello15:00
markstur_hi15:01
*** yuval has left #openstack-meeting-alt15:01
*** yuval has quit IRC15:01
*** Yogi1 has joined #openstack-meeting-alt15:01
zhongjun_hi15:01
bswartz#agenda https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting15:01
*** ddieterly is now known as ddieterly[away]15:01
*** ddieterly[away] is now known as ddieterly15:01
*** jimholl_ has joined #openstack-meeting-alt15:01
bswartzjust a few leftover discussion topics from design summit15:01
bswartzI'll save those for after the specific topics people proposed15:02
bswartz#topic share backup15:02
*** openstack changes topic to "share backup (Meeting topic: manila)"15:02
bswartzzhongjun_: you're up15:02
*** tbarron has joined #openstack-meeting-alt15:02
zhongjun_thanks15:02
zhongjun_I saw the record about discussion share backup. but it is not a conculution.15:02
tbarronhi15:03
bswartzwhich discussion?15:03
zhongjun_so, There are two ideas(Not very detailed, just a direction) for the share backups, please see which one is suitable for manila?15:03
zhongjun_or which one is definite not suitable for manila.15:03
bswartzwe haven't discussed share backup in details since the winder midcycle meetup15:03
zhongjun_1. Smaug(openstack project)+Manila+Swift(or something else)15:03
zhongjun_Use swift as a smaug's backup plugin, Use smaug calling manila's APIs(such as share-list, share-instances-export-location) to obtain share information. then creating a backup in smaug.15:03
zhongjun_2. Add backup APIs in Manila Data service, let manila own have backup capacity.15:03
*** jonaspf1 has quit IRC15:04
bswartzpersonally I see both options as valuable15:04
*** yangyapeng has left #openstack-meeting-alt15:05
*** jcsp has joined #openstack-meeting-alt15:05
*** shaohe_feng has quit IRC15:05
bswartzgiven that (2) will be a lot of work it seems like (1) is more likely to happen sooner15:05
mkodererhi15:05
*** shaohe_feng has joined #openstack-meeting-alt15:05
zhongjun_The benifit of use first idea: it not only backup share but also backup manila config and database, etc.15:05
gansoit seems to me that the development in (1) is creating a plugin in Smaug15:05
sgotliv_does it mean we recommend to use Smaug for manila backups?15:06
bswartzI don't know enough about smaug yet to understand what it can do for a project like manila15:07
tbarronis (1) written up somewhere so we can study it in more detail?15:07
dustinstbarron: +115:07
bswartzhowever if they have ideas for backing up shared file systems I think we should be supportive and helpful15:07
*** diazjf1 has joined #openstack-meeting-alt15:07
mkodererhow is this related to freezer? https://wiki.openstack.org/wiki/Freezer15:08
bswartzI also don't know anything about freezer15:08
sgotliv_I believe smaug compete with freezer15:08
sgotliv_I am kind of learning them both these days15:08
*** vinaypotluri has joined #openstack-meeting-alt15:08
*** spzala has joined #openstack-meeting-alt15:08
bswartzI believe that regardless of what backup or DR services are built on top of Manila, users will get a better experience if we build backup / DR features into manila itself15:08
*** tremble has quit IRC15:09
bswartztherefore we should do both15:09
gouthamrit would be nice to hash 1) out in a manila-spec (now that we can't create new Wiki pages)15:09
mkodererok we have too many projects in OpenStack...15:09
zhongjun_tbarron: The smaug have a video demo, but I forget the link, I will find it and put it to wiki.15:09
gouthamri'm also interested in restore :)15:09
bswartzshare replication was designed with that belief in mind15:09
sgotliv_mkoderer, +115:09
*** Leo_ has joined #openstack-meeting-alt15:09
zhongjun_link: https://wiki.openstack.org/wiki/smaug15:09
sgotliv_i can post a link later15:09
sgotliv_lol15:09
sgotliv_zhongjun_, thanks15:09
dustinsmkoderer: +115:09
*** doug-fish has joined #openstack-meeting-alt15:10
*** Leom has joined #openstack-meeting-alt15:10
*** madhu_ak_ has joined #openstack-meeting-alt15:10
zhongjun_gouthamr: In smaug, use heat to restore openstack  environment.15:10
bswartzwhen we discussed share backup at the midcycle one of the arguments against doing it was that many other backup tools exist and many of those are going to be way better than anything we build into manila unless we spend large amounts of time on a manila backup feature15:10
xyang2https://www.youtube.com/watch?v=_tVYuW_YMB815:11
bswartzI still think it's worth developing some kind of backup framework with minimal capabilities just to have a standard interface15:11
xyang2smaug15:11
*** tellesnobrega is now known as tellesnobrega_af15:11
dustinsand if we have projects that provide backup functionality, why reinvent the wheel?15:11
zhongjun_xyang2: thanks xyang15:11
bswartzbut we won't be able to compete with other solutions that focus 100% on backup15:11
toabctldustins: +115:12
*** apetrich has quit IRC15:12
*** zz_dimtruck is now known as dimtruck15:12
*** doug-fish has quit IRC15:12
*** mrmartin has joined #openstack-meeting-alt15:12
sgotliv_I believe these projects use API provided by backed component15:12
gansoif there is an openstack service and is focused on it, a plugin for it makes sense15:12
dustinsganso: +115:13
gansothey would be reinventing the wheel, not us hehe15:13
bswartzdustins: there are some kinds of things that can only be done properly with low level access to the storage -- the kind of thing that requires code in the storage drivers to implement15:13
*** fnaval has joined #openstack-meeting-alt15:13
tbarronzhongjun_: i'm a little bit familiar with smaug but i haven't seen anything about filesystem backup in particular yet15:13
*** heyongli has quit IRC15:13
*** alex_xu has quit IRC15:13
bswartzthose can only be implemented as features in projects that have storage drivers (AKA cinder, manila, glance, etc)15:13
*** Leo_ has quit IRC15:13
zhongjun_tbarron: It will, I will do15:13
bswartzservices that layer on top of these services will be limited in what they can achieve through the common interface15:14
*** madhu_ak has quit IRC15:14
dustinsbswartz: Indeed, tricky to balance a general approach versus exposing value in the underlying storage back end15:14
bswartzthat's why I say we should do both15:14
gansobswartz: I wouldn't say only done properly in the backend, but more efficiently in most cases. Backup can still be done properly through the storage interface (NFS shares for instance)15:14
tbarronzhongjun_: i'd be interested in seeing a spec for integration with smaug15:14
bswartzganso: you probably recall some people at the migration talk in austin saying it was important to them that their backups were bit-exact15:15
zhongjun_bswartz: +115:15
dustinstbarron: ditto15:15
*** shaohe_feng has quit IRC15:15
bswartzthat kind of guarantee can only be provided at the storage driver level -- you can't do that in a generalized way15:15
*** pt_15 has quit IRC15:16
tbarronin cinder's case i believe smaug intends to use standard cinder api which allows for backend driver optimizations15:16
zhongjun_tbarron, dustins: Oh, that's sounds good.15:16
tbarronfor volume backup15:16
dustinsHmm, perhaps we could do a Smaug-based solution just to cover everything for now, then we can add the "special sauce" in another release?15:16
tbarronfor dbase backup, etc., difft story15:16
bswartztbarron: backups of volumes is fundamentally easier than backups of file systems15:16
tbarronbswartz: +115:17
tbarronfor filesystems we have metadata issues like with migration15:17
bswartzzhongjun_: did we answer you qusetion?15:17
tbarronfor one thiing15:17
bswartzquestion*15:18
*** snackewm has joined #openstack-meeting-alt15:18
zhongjun_bswartz: yes, the answer is two idea is ok?15:18
*** Niham has quit IRC15:18
zhongjun_s/idea/ideas15:18
*** mrmartin has quit IRC15:18
bswartzyes I don't want to discourage either approach15:19
bswartzif people want to work on both, then that's great15:19
*** jtomasek_ has quit IRC15:19
bswartzpersonally I'd like to spend time on manila backup -- there are just too many other important problems to solve first15:19
zhongjun_bswartz: That's great, thanks15:19
bswartzlet's move on15:19
bswartz#topic snapshot restore15:19
*** openstack changes topic to "snapshot restore (Meeting topic: manila)"15:19
cknight1I'm working on the Snapshot Restore feature we agreed to at Summit.15:19
bswartzcknight1: you're up15:20
*** doug-fish has joined #openstack-meeting-alt15:20
cknight1I had a working POC before we left Austin, and the spec is in review.15:20
cknight1#link  https://review.openstack.org/#/c/315695/15:20
bswartzdo people like the name "Snapshot restore" better than "revert to snapshot"?15:20
cknight1Most of it seems non-controversial, but there is a question about the REST API.15:20
*** yamahata has quit IRC15:20
*** nurla has quit IRC15:20
*** iyamahat has quit IRC15:20
cknight1bswartz: Your question is germane to mine!15:20
cknight1There are two objects involved, the share being reverted, and the snapshot being restored.15:20
cknight1In any case, the API must be explicit about which snapshot is being restored.15:21
bswartzwhen I think of restoring snapshots I imagine creating a new share from a snapshot15:21
vponomaryov+1 for "revert to snapshot"15:21
cknight1If the API is on the share, then the snapshot must be specified in the body.15:21
bswartzwhen I think of reverting to a snapshot I think of modifying an existing share15:21
*** ninag_ has quit IRC15:21
gansocknight1: +1 for "snapshot restore"15:22
*** ijw has joined #openstack-meeting-alt15:22
cknight1If the API is on the snapshot, then the share need not be specified because Manila can infer it from the snapshot.15:22
cknight1I chose the latter because it is simpler to invoke, it matches the GUI tools I'm familiar with where the restore action is on the snapshot, and the client code is smaller.15:22
bswartzcan't the action be on the snapshot but we call it something like snapshot revert?15:22
markstur_bswartz, +1 (the 2 names suggest different meanings)15:22
cknight1But in the extremely unlikely case where the API layer can find the specified snapshot but not the share, the server would have to return a 500 because something went very wrong in the server.  I'm not aware of any code that returns 500-series errors today, so it would be something new.15:22
bswartzrevert makes is obvious that you're going backwards15:22
gansocknight1: also, you don't need to touch the share API since this is mostly a change to snapshots API15:23
*** nurla has joined #openstack-meeting-alt15:23
cknight1bswartz: That's true.  Personally, I don't feel strongly about it.15:23
zhongjun_ cknight1: +1 for "snapshot restore/revert"15:23
vponomaryovaction is applied to a share, it should be "shares" API15:23
bswartzvponomaryov: if we do that then the caller has to specify the share ID in the URL and the snapshot ID in the body15:24
bswartzthat's more work for the caller than just specifying the snapshot ID in the URL15:24
gansobswartz: in fact no, we agreed we always revert to latest15:24
vponomaryovwhy?15:24
vponomaryovwe allow only latest snapshot15:24
vponomaryovno need to provide it15:24
*** fawadkhaliq has joined #openstack-meeting-alt15:24
vponomaryovganso: )15:24
gansobswartz: so, if we do not need to do /snapshots/snapshot-id/restore, then it makes sense to be /shares/share-id/revert15:24
gansorevert will know what to do15:24
bswartzwell the user has to specify which snapshot he expects to be restored in case a new shapshot call races with the revert call15:25
gansobecause it is the latest15:25
gansobswartz: we should avoid such races15:25
bswartzthat sort of race is unavoidable15:25
vponomaryovbswartz: who will create snapshots when it should be reverted?15:25
bswartzif I list the snapshots, then invoke share revert, and another snapshot was taken between those 2 operations, I might be very confused15:25
vponomaryovbswartz: it is not use case15:25
xyang2since we are modifying the share, shares api seems more appropriate15:26
bswartzin that case we would at least need to return the UUID of the snapshot we did revert to15:26
bswartzif the caller doesn't specify it15:26
vponomaryovbswartz: return some data - ok15:27
bswartzto prevent surprises15:27
dustinsYeah, something just saying "I used this snapshot to restore from" would be handy15:27
cknight1bswartz:  We're changing data, so I think the API should be very explicit about what snapshot is being restored.15:27
toabctlcknight1: +115:27
dustinscknight1: agreed15:27
cknight1bswartz:  I don't think the server should pick the latest one itself, since that can lead to a surprise.15:27
bswartzyeah I lean towards explicitness so we can report more accurate errors15:27
toabctland there can be 2 admins + one creating a new snapshot and one reverting15:28
cknight1bswartz:  In my POC, I check that the specified snapshot is actually the latest one.15:28
vponomaryovcknight1: manila can store value of latest snapshot in share model15:28
dustinsYes, that way we can error out saying that the snapshot specified was not the most recent15:28
gansocknight1, bswartz: why wouldn't share's status prevent this scenario? if we have statuses with locks15:28
bswartzworst case is you get an error15:28
vponomaryovcknight1: that can be visible via "share show"15:28
*** belmoreira has quit IRC15:28
bswartzganso there is unknown time between when an admin looks at the list of snapshots and invokes the revert call15:28
bswartzit could be seconds or minutes or hours15:28
gansobswartz: if a snapshot is created, even though it is in "Creating" then it is latest, but share status will be "snapshotting"15:28
gansobswartz: oh I see, two users under the same tenant15:29
*** andreas_s has quit IRC15:29
bswartzyes15:29
gansobswartz: like, one user is taking a snapshot and the other is reverting15:29
*** markstur__ has joined #openstack-meeting-alt15:29
toabctlganso: yes15:29
bswartzif that were to happen, the revert call should error out explaining that the specified snapshot is no longer the latest snapshot15:29
gansobswartz: so if we need the snapshot parameter there is no real advantage between usage of either API15:29
bswartzthen the admins can get together and figure out what they want to do15:29
*** pgadiya has quit IRC15:30
cknight1So what I'm hearing is that most feel this should be an action on the share as far as the REST API is concerned.15:30
bswartzI'm hearing though that for semantic reasons people prefer it's a share action15:30
*** tango__ has quit IRC15:30
bswartzcknight1: yes definitely15:30
cknight1And the CLI should be 'revert-to-snapshot' instead of 'snapshot-restore'.  Right?15:30
*** tango has joined #openstack-meeting-alt15:30
bswartzit might be slightly less RESTful but it's more clear what's going on15:30
markstur__+115:31
dustins"restore this share to this snapshot" rather than "with this snapshot restore this share"15:31
gansocknight1: +115:31
vponomaryovcknight1: +115:31
bswartzyes revert-to-snapshot seems very clear15:31
dustinscknight1: +115:31
cknight1OK, I'll make it happen.  Thanks, everyone!15:31
*** markstur_ has quit IRC15:31
bswartzthe revert-to-latest-snapshot (with no snapshot arg) is also interesting but a little scary to me15:31
cknight1bswartz: yes, too scary15:32
bswartzokay15:32
bswartzlet's move on15:32
bswartz#topic specs15:32
*** openstack changes topic to "specs (Meeting topic: manila)"15:32
bswartzganso asked earlier today about spec deadlines, and requirements for specs15:33
*** bana_k has joined #openstack-meeting-alt15:33
bswartzI don't believe we agreed on any deadlines, or requirements for specs15:33
bswartzwe have the specs repo, and people are already using it, which is great15:33
gansook so bswartz and I were discussing today about specs priority, I think it is a good idea that N1 has specs prioritized because if we are following this idea of working with specs, specs block implementation if they are not approved15:33
bswartzhowever where we left things in Austin was that specs are still optional and we encourage them but don't require them15:34
bswartzfor the purpose of reviews I do think ganso has a point15:34
tbarronwe need to avoid being too waterfall here, it would be good to be able to refine specs and refine code in parallel15:34
bswartzif a developer is waiting for feedback on his ideas before writing the code then we should prioritize reviewing the spec and providing the feedback15:35
markstur__+1 for in parallel15:35
tbarronwhere the code doesn't get merged in the end if it diverges significantly from spec15:35
gansoI think they should not be enforced, according to what we discussed in Austin, it seems the main value of specs for Manila, is to have feedback on design and implementation before investing a lot of work in it and having to change too late in the cycle15:35
bswartzwe shouldn't force developers to wait, but in ganso's case it sounds like he doesn't want to start coding the wrong thing15:35
tbarronunderstood15:36
gansothere are proposals that do not need specs, or that they may not need too much feedback or refining15:36
xyang2if we could get code merged before spec is merged, that will be better, so spec will not be out of sync with code15:36
gansoso specs aggregate more if they used15:36
*** kfarr has joined #openstack-meeting-alt15:37
gansoxyang2: that would be good also, but then we need to consider the spec approved even though not merged15:37
bswartzganso: in the past the way we've stimulated feedback was to bring up specific topics during these weekly meetings and ask for feedback15:37
xyang2ganso: yes, it is tricky15:37
*** ninag has joined #openstack-meeting-alt15:37
*** akaszuba has quit IRC15:38
xyang2ganso: the code will almost always go out of sync with spec if spec is merged first15:38
bswartzganso: if you're looking for feedback on your spec I suggest we just bring it up here and agree to give you yes or no decisions by some date15:38
gansobswartz: sometimes people find out that they disagree with design or find a potential flaw when we are too close to FF15:38
xyang2ganso: but if spec is not merged, people may not want to +2 the code15:38
*** egafford has left #openstack-meeting-alt15:38
mkodererI would merge specs and after that merge the code and update documentation accorindgly15:38
bswartzokay let's not get too wrapped up in the meaning of a merged spec15:39
bswartzI think we agreed that we can modify specs after they're merged15:39
gansoxyang2: then we need a social rule for this, so it makes sense and we do not get stuck not being able to merge a code because spec was not merged hehe15:39
mkodererI don't see any issue in outdated specs as long the documenation is up to date15:39
xyang2mkoderer: that's fine too.  just need to remember to update the spec afterwards15:39
gansomkoderer: +115:39
bswartzI dislike the ceremonial "merging of the spec" to mean that the idea is somehow blessed and approved15:39
vponomaryovmkoderer: docs up-to-date is utopia15:39
xyang2ganso: agree15:39
*** mickeys has joined #openstack-meeting-alt15:39
tbarronbswartz: +115:40
mkoderervponomaryov: would also mean: spec up-to-date is utopia ;)15:40
bswartzI think we should try to reach consensus and merge specs but that shouldn't be the end of the discussion15:40
*** Swami has joined #openstack-meeting-alt15:40
tbarroni'm just saying look at the spec before the code merges, ask questions about divergence, etc.15:40
tbarronuse our heads15:40
gansobswartz: I think this "ceremony" is needed, else devs won't be required to review the spec at all, and their value will be diminished15:40
dustinstbarron: +115:40
*** dprince has quit IRC15:40
gansothis is similar situation with blueprints15:41
tbarronganso: we can build a culture that does the right thing w/o having to make formal process IMO15:41
bswartzganso: yes we need people to know that feedback is more welcome earlier than later15:41
vponomaryovbswartz: "merge" is kind of proof15:41
*** MeganR has joined #openstack-meeting-alt15:41
bswartzwe have a history of people ignoring features until 2 weeks before feature freeze then dropping a whole bunch of feedback15:41
*** dprince has joined #openstack-meeting-alt15:41
bswartzthat's not a good experience for contributors15:42
gansobswartz: yes, specs cannot solve that by itself, it is more of a cultural thing15:42
*** vsakharov has joined #openstack-meeting-alt15:42
tbarronand a history of big code drops late, right?15:42
bswartzokay so here's a proposal15:42
gansoso my idea of emphasizing "priority" is to address this15:42
gansono deadlines15:42
gansojust priorities15:42
bswartzif people post a spec, and ask for feedback, we should prioritize reviewing the spec and giving feedback early (before first milestone as ganso says)15:43
mkodererbtw we have already some specs in gerrit for review.. can we put some priority to review them? ;)15:44
bswartzpeople who fail to review specs shouldn't propose major changes later on in the release15:44
xyang2bswartz: define major changes:)15:44
*** minwang2 has joined #openstack-meeting-alt15:44
bswartzxyang2: something which should have caught in the spec review15:44
vponomaryovxyang2: good catch! ))15:44
bswartzsometimes you can't see why you don't like something until you see the implementation15:45
mkodererbswartz: so true :)15:45
*** Na3iL has quit IRC15:45
bswartzbut in many cases you can see objectionable things in the spec and the right time to object to those is before the code is written15:45
*** yamamoto has joined #openstack-meeting-alt15:46
markstur__disagreements in specs need to get resolved before code merges15:46
*** numans has quit IRC15:46
gouthamrmarkstur__: yes..15:47
markstur__Nits in specs -- shouldn't be a roadblock15:47
*** EZPZ has joined #openstack-meeting-alt15:47
bswartzalso (and I've seen this with specs I've written) sometimes you just get really helpful suggestions in the spec review which make implementation go more smoothly15:47
bswartzbelieve it or not, other people have good ideas15:47
markstur__Also code POC before spec is decided is still a good idea if coder is OK w/ POC15:47
*** jmckind_ has joined #openstack-meeting-alt15:47
markstur__but that isn't supposed to change the spec process (just adds proof)15:48
tbarronmarkstur__: +1 correct spelling, etc. but don't -1 for it alone15:48
bswartzwait a minute15:48
gansotbarron: nits shouldn't -115:48
bswartzspelling errors should be fixed -- that's what -1 is for15:48
mkoderermarkstur__: yeah I really like POC code in the same time with spechs15:49
bswartzit's not hard to just fix it and move on15:49
gouthamror you can fix it if it's not too much of a bother?15:49
mkodererbswartz: I wouldn't block a merge just because two spelling nits15:49
tbarronwell I see a lot of negative energy going into that kind of thing15:49
bswartzright we can always +2 over a -115:49
tbarronI do think we should fix them15:49
gansotbarron: they become obsolete15:49
bswartzbut that's doesn't mean we shouldn't post the -1 review15:49
tbarronbut note them as nits, fix, etc.15:49
gansotbarron: the documentation should be have perfect spelling15:49
gansotbarron: s/be have/have15:50
tbarronok, well we got that away.15:50
tbarronout of the way -115:50
gouthamrganso: true.. but what stops the reviewer from helping out and fixing the documentation for spelling errors?15:50
*** jmckind has quit IRC15:50
xyang2bswartz: so we don't require spec to be merged before code merged?15:50
*** akislitsky__ has joined #openstack-meeting-alt15:50
*** thatsdone has quit IRC15:50
gouthamrthe docs team does this.. don't -1, just edit and help merge15:50
gouthamr^ if minor15:50
gansogouthamr: nothing, spelling mistakes are welcome to be pointed out, some people learn from it, but not worth -115:51
bswartzxyang2: not currently -- we could decide to change that (probably for ocata though given we're already well into newton)15:51
xyang2ok15:51
*** IlyaG has joined #openstack-meeting-alt15:51
tbarrongouthamr: i like that b/c now when I do -1 it means something15:51
tbarronbut we can play the game either way :)15:51
bswartzokay ganso: do you want to provide a link to your spec before we move on?15:51
gansobswartz: sure, thanks!15:52
ganso#link https://review.openstack.org/31570715:52
gouthamrtbarron: ofcourse, don't fix functionality, just fix 'teh' to 'the' or 'hence' to 'thus' :)15:52
bswartz#action everyone review ganso's ^ spec!15:52
*** jaypipes has joined #openstack-meeting-alt15:52
bswartz#topic UI customization15:52
*** openstack changes topic to "UI customization (Meeting topic: manila)"15:52
tbarronsgotliv may have had to drop15:53
gansogouthamr: you don't like "hence" ? :(15:53
tbarronlate there15:53
tbarronbut15:53
tbarronwe have two issues where a customer has requested15:53
tbarronmore customizalbe ui.15:53
gouthamrganso: i've had US/british grammar checks happen wayy too often :)15:53
tbarronthey run a public cloud15:53
*** mwhahaha has joined #openstack-meeting-alt15:53
vponomaryovtbarron: manila in public cloud? nice!15:54
tbarronthey down't want pulldowns for protocols that don't exist in their cloud15:54
bswartzbritish english > US english15:54
gansobswartz: +115:54
* bswartz listens to the BBC too much...15:54
gouthamr^ well, i for one agree15:54
tbarronif they don't have cifs of hdfs then they don't want their paying tenants to complain b/c they are in the ui and not availiable15:54
*** mikelk has quit IRC15:54
*** gardlt has joined #openstack-meeting-alt15:55
bswartz#link https://etherpad.openstack.org/p/newton-manila-contributor-meetup15:55
gouthamrtbarron: nice use case..15:55
tbarronwe have enabled_protocols in manila.conf so that seems a reasonable request to me.15:55
tbarronany issue?15:55
bswartzif you see in the etherpad, vponomaryov commented about the possiblity of a new API to support this use case15:55
vponomaryovtbarron: no issue, I like idea15:55
gansotbarron: don't we already disable these through manila.conf ? "enabled_share_protocols" or something?15:55
gouthamrtbarron: but i was under the impression people don't use vanilla manila-ui or manilaclient15:55
bswartzI support the idea of the API15:55
vponomaryovganso: no APIs15:55
tbarrongouthamr: they change the CSS sheet :-)15:55
vponomaryovganso: yet15:55
bswartzit would be very useful for any tools built on top of manila to know which protocols are available15:56
tbarronok, we can work on that issue15:56
tbarron#2.15:56
bswartztbarron: do we need anything more than that single API for that use case?15:56
cknight1bswartz: It's possible now via the pools list API.15:56
cknight1bswartz: The scheduler has all that information.15:56
bswartzcknight1: that's admin only15:56
cknight1bswartz: true15:57
bswartzwe need ordinary tenants to know which protocols are available15:57
bswartzpreferably without giving away all the pool details15:57
cknight1bswartz: So what else might a user or GUI need to know?15:57
*** yamamoto has quit IRC15:57
gouthamrbswartz: scheduler stats can be improved, we only have GET pools and GET /detail on pools15:57
vponomaryovcknight1: to know type of access and its level15:58
bswartzperhaps a mapping of protocols to share types or share types to protocols in case not every protocol is compatible with every share type15:58
gouthamrbswartz: we can easily add this tenant facing API to the same suite15:58
*** dprince has quit IRC15:58
*** dukhlov has quit IRC15:58
gouthamrbswartz: or a filter to the existing API15:58
cknight1bswartz: Point being, if we must add an API, we can design an extensible Manila capabilities API for adding such things.15:58
bswartzor we could even make the protocol list just extra data on the share type list APIs15:59
tbarrongouthamr: i think that's the way we were thinking15:59
tbarronmaybe we can do incremental refinement here15:59
*** armax has joined #openstack-meeting-alt15:59
*** romcheg has joined #openstack-meeting-alt15:59
tbarronready for #2?15:59
gouthamrtbarron: agree..15:59
bswartzwe just return a list of supported protocols for each share type when you list the share types15:59
cknight1tbarron: time check15:59
*** dprince has joined #openstack-meeting-alt15:59
bswartzthen it's a change to an existing API instead of a brand new API15:59
gansotbarron: I am curious for #215:59
*** MikeG451 has joined #openstack-meeting-alt16:00
tbarrontoday when you create a share you get a make visible for all checkbox16:00
bswartzaltough I'm not sure we have the raw data for that anywhere16:00
tbarronthey want to be able to turn that off16:00
markstur__there's a #2?16:00
gouthamrbeep beep beep16:00
gouthamr12:0016:00
tbarronmarkstur__: yeah, i said 2 things16:00
gansogouthamr: lol16:00
markstur__cliffhanger16:00
*** nadya has quit IRC16:00
tbarroncontinue in channel16:00
gouthamrhahaa16:00
bswartzokay16:00
bswartzthanks all16:00
markstur__to be continued...16:00
gansogouthamr: lunch time16:00
bswartzwe ran out of time16:00
bswartz#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu May 19 16:00:42 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2016/manila.2016-05-19-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2016/manila.2016-05-19-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2016/manila.2016-05-19-15.00.log.html16:00
*** gomarivera has joined #openstack-meeting-alt16:00
*** gouthamr has left #openstack-meeting-alt16:00
*** jseiler has left #openstack-meeting-alt16:01
*** sdake_ is now known as sdake16:01
*** wcriswell has joined #openstack-meeting-alt16:01
*** mihgen has joined #openstack-meeting-alt16:01
*** stewie925 has joined #openstack-meeting-alt16:01
*** xarses has joined #openstack-meeting-alt16:01
xarses#startmeeting fuel16:02
openstackMeeting started Thu May 19 16:02:19 2016 UTC and is due to finish in 60 minutes.  The chair is xarses. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
xarses#chair xarses16:02
xarsesTodays Agenda:16:02
xarses#link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda16:02
xarsesWho's here?16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: fuel)"16:02
openstackThe meeting name has been set to 'fuel'16:02
openstackCurrent chairs: xarses16:02
xarsessorry about that folks16:02
mwhahahahi16:02
kozhukalovhello16:02
vsakharovhi16:02
akislitsky__hi16:02
gardltheelo16:02
sslypushenkoo/16:02
*** jmckind has joined #openstack-meeting-alt16:02
EZPZo/16:02
*** julim has quit IRC16:02
*** dustins has left #openstack-meeting-alt16:03
*** igorbelikov has joined #openstack-meeting-alt16:03
*** iyamahat has joined #openstack-meeting-alt16:03
gomariverahi16:03
*** marcusvrn_ has quit IRC16:03
xarsesThere are no action items from last week, moving on to general topics16:03
ashtokolovo/16:03
xarses#topic using reno for release notes (xarses)16:03
*** openstack changes topic to "using reno for release notes (xarses) (Meeting topic: fuel)"16:03
aglarendil+116:03
xarses#link http://lists.openstack.org/pipermail/openstack-dev/2016-May/093849.html16:03
*** nadya has joined #openstack-meeting-alt16:03
xarsesThere was no feedback on the mail thead I raised16:04
xarsesSince its in response to the discussions we already had at summit, I'm going to push patches to start setting this up16:04
*** rcernin has quit IRC16:04
kozhukalovlazy consensus, we'd better use every tool that could make our life better16:05
*** jmckind_ has quit IRC16:05
xarsesthat's my thought16:05
xarses#topic Mixed team status (sslypushenko)16:06
*** openstack changes topic to "Mixed team status (sslypushenko) (Meeting topic: fuel)"16:06
sslypushenkoMixed team is working on bugfixing16:06
*** igordcard has quit IRC16:06
sslypushenkoThat is mainly it16:06
kozhukalovnice ))16:06
*** lhinds has joined #openstack-meeting-alt16:06
kozhukalovis there any particular info?16:06
xarsesany stats, thoughts for next cycle?16:06
lhindssorry for being late (and Hi!)16:07
*** mickeys has quit IRC16:07
mattymo(also late and hi)16:07
sslypushenkoMixed team is moving out from working on Fuel16:07
xarsesok16:07
*** mickeys has joined #openstack-meeting-alt16:07
sslypushenkoso we are just finishing our current assigned work16:07
*** holser has joined #openstack-meeting-alt16:08
kozhukalovwhat was the motivation to add this topic to agenda if there is no any particular info?16:08
holsero/16:08
sslypushenkoIt is kind of duty16:08
kozhukalovno it is not16:09
xarses#topic UI Team status (vkramskikh)16:09
*** openstack changes topic to "UI Team status (vkramskikh) (Meeting topic: fuel)"16:09
vkramskikhHi! We're still working on bugs. We have 5 High bugs left. 4 of them have fixes on review, though we're experiencing some issues with OpenStack infra - our gating job fails in 90% cases, so it's barely possible to merge anything. OpenStack infra guys are trying to identify the root cause of the issues.16:09
vkramskikhAs for Newton acitvities, the scope is still not defined, so we'll work on tech tebt once we deal with the remaining bugs.16:09
vkramskikhWe'll also try to find time to help with the new OpenStack JS-related projects - js-generator-openstack (cookiecutter for JS) and js-openstack (JS-based OpenStack API client library).16:09
vkramskikhQuestions?16:09
xarsesnice, good to see collaboration there16:10
kozhukalovthanks vkramskikh16:11
*** fawadkhaliq has quit IRC16:11
*** ninag has quit IRC16:11
xarses#topic Telco Team Status (vsakharov)16:11
*** openstack changes topic to "Telco Team Status (vsakharov) (Meeting topic: fuel)"16:11
vsakharovOur team continues fixing bugs:16:11
vsakharovDone from the last update - 616:11
vsakharovIn progress (in development and on review) - 916:11
vsakharovAlso we're started scoping features for 10.0, but since we started it just today there is no significant update to report.16:11
vsakharovMaybe you have any questions?16:11
*** markstur__ has quit IRC16:11
*** ninag has joined #openstack-meeting-alt16:12
*** mickeys has quit IRC16:12
*** nkrinner has quit IRC16:12
kozhukalovthere is no clear scope for Newton yet16:12
*** nkrinner has joined #openstack-meeting-alt16:12
*** nkrinner is now known as nkrinner_afk16:12
kozhukalovunfortunately16:12
vsakharovI guess, more info about Newton will be on the next week16:13
*** Nikolay_St has joined #openstack-meeting-alt16:13
*** nadya has quit IRC16:13
xarses#topic open discuss16:14
*** openstack changes topic to "open discuss (Meeting topic: fuel)"16:14
xarsesanything else to raise or discuss?16:14
*** janscheurich has quit IRC16:14
xarsesok, thanks guys16:15
xarses#endmeeting16:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:15
openstackMeeting ended Thu May 19 16:15:38 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fuel/2016/fuel.2016-05-19-16.02.html16:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fuel/2016/fuel.2016-05-19-16.02.txt16:15
openstackLog:            http://eavesdrop.openstack.org/meetings/fuel/2016/fuel.2016-05-19-16.02.log.html16:15
*** igorbelikov has left #openstack-meeting-alt16:15
*** holser has left #openstack-meeting-alt16:16
*** dprince has quit IRC16:16
*** ninag has quit IRC16:16
*** mwhahaha has left #openstack-meeting-alt16:16
*** vsakharov has quit IRC16:18
*** EZPZ has left #openstack-meeting-alt16:19
*** vponomaryov has left #openstack-meeting-alt16:20
*** AdmiralQi has joined #openstack-meeting-alt16:20
*** vishwanathj has joined #openstack-meeting-alt16:20
*** mgershen2 has joined #openstack-meeting-alt16:21
*** mgershen2 has left #openstack-meeting-alt16:22
*** yamahata has joined #openstack-meeting-alt16:22
*** perelman has joined #openstack-meeting-alt16:23
*** ewilson has joined #openstack-meeting-alt16:24
*** perelman has quit IRC16:25
*** ninag has joined #openstack-meeting-alt16:26
*** jcoufal has quit IRC16:27
*** stewie925 has left #openstack-meeting-alt16:27
*** tonytan4ever has quit IRC16:28
*** fesp has quit IRC16:29
*** gardlt has quit IRC16:29
*** piet has quit IRC16:30
*** piet has joined #openstack-meeting-alt16:31
*** absubram has quit IRC16:31
*** tango has quit IRC16:32
*** tonytan4ever has joined #openstack-meeting-alt16:33
*** gomarivera has quit IRC16:33
*** tango has joined #openstack-meeting-alt16:33
*** tellesnobrega_af is now known as tellesnobrega16:35
*** ninag has quit IRC16:35
*** dprince has joined #openstack-meeting-alt16:36
*** ninag has joined #openstack-meeting-alt16:36
*** ninag has quit IRC16:36
*** kzaitsev_mb has quit IRC16:36
*** MikeG451 has left #openstack-meeting-alt16:36
*** ninag has joined #openstack-meeting-alt16:36
*** paul-carlton2 has joined #openstack-meeting-alt16:37
*** Na3iL has joined #openstack-meeting-alt16:37
*** jonaspf1 has joined #openstack-meeting-alt16:38
*** tango has quit IRC16:38
*** jmckind_ has joined #openstack-meeting-alt16:39
*** kzaitsev_mb has joined #openstack-meeting-alt16:40
*** ninag has quit IRC16:41
*** rarcea has quit IRC16:42
*** jmckind has quit IRC16:43
*** xyang2 has quit IRC16:45
*** tremble has joined #openstack-meeting-alt16:45
*** tremble has quit IRC16:46
*** fawadkhaliq has joined #openstack-meeting-alt16:46
*** jeffbrown has quit IRC16:46
*** elmiko has joined #openstack-meeting-alt16:46
*** panda has quit IRC16:48
*** edtubill has quit IRC16:48
*** tango has joined #openstack-meeting-alt16:48
*** shashank_hegde has joined #openstack-meeting-alt16:48
*** panda has joined #openstack-meeting-alt16:49
*** tkelsey has joined #openstack-meeting-alt16:49
*** tango has quit IRC16:49
*** tango has joined #openstack-meeting-alt16:50
*** tango has quit IRC16:50
*** doug-fish has quit IRC16:50
*** doug-fish has joined #openstack-meeting-alt16:51
*** rhallisey has joined #openstack-meeting-alt16:52
*** shashank_hegde has quit IRC16:54
*** pnavarro has quit IRC16:54
*** ninag has joined #openstack-meeting-alt16:54
*** doug-fis_ has joined #openstack-meeting-alt16:54
*** doug-fish has quit IRC16:55
*** derekh has quit IRC16:55
*** gmurphy_ has joined #openstack-meeting-alt16:57
*** yamahata has quit IRC16:58
*** mandre has joined #openstack-meeting-alt16:58
*** tmcpeak has joined #openstack-meeting-alt16:58
*** piet has quit IRC16:58
*** yamahata has joined #openstack-meeting-alt16:58
*** mdong has joined #openstack-meeting-alt16:58
*** mtanino has quit IRC16:58
*** ninag has quit IRC16:59
*** doug-fis_ has quit IRC16:59
*** doug-fish has joined #openstack-meeting-alt16:59
tmcpeak#startmeeting security17:00
openstackMeeting started Thu May 19 17:00:14 2016 UTC and is due to finish in 60 minutes.  The chair is tmcpeak. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
tmcpeako/17:00
*** openstack changes topic to " (Meeting topic: security)"17:00
openstackThe meeting name has been set to 'security'17:00
tmcpeak#chair hyakuhei17:00
openstackCurrent chairs: hyakuhei tmcpeak17:00
gmurphy_o/17:00
tkelseyo/17:00
tmcpeak#link https://etherpad.openstack.org/p/security-agenda17:00
*** igordcard has joined #openstack-meeting-alt17:00
*** edtubill has joined #openstack-meeting-alt17:00
elmikoo/17:01
mdongo/17:01
michaelxino/17:01
*** reldan has quit IRC17:01
*** kevo has quit IRC17:01
diazjf1o/17:01
tmcpeakhi everybody17:02
tmcpeakplease have a look at the agenda and add anything if you want17:02
tmcpeakotherwise we'17:02
tmcpeakwe'll get rolling in a minute or two17:02
hyakuheio/17:02
lhindshi everyone17:02
*** piet has joined #openstack-meeting-alt17:02
hyakuheiI’m about 50% here. Will be 100% here in a few minutes.17:02
tmcpeakhey lhinds17:02
lhindshey tmcpeak17:02
*** ninag_ has joined #openstack-meeting-alt17:02
*** madhu_ak_ has left #openstack-meeting-alt17:02
tmcpeakI pinged nkinder, if we can get him to join I'll move the OSSN to match his schedule17:03
tmcpeakmeanwhile, let's roll it17:03
*** pvaneck has joined #openstack-meeting-alt17:03
tmcpeak#topic Anchor17:04
*** openstack changes topic to "Anchor (Meeting topic: security)"17:04
*** doug-fish has quit IRC17:04
tmcpeaktkelsey: you might be the one today17:04
tmcpeakdon't see Mr. Chivers17:04
*** minwang2 has quit IRC17:04
tkelseyhumm, well i got nothing on my radar17:04
*** ccneill has joined #openstack-meeting-alt17:04
ccneillo/17:04
tmcpeakeasy enough17:04
tmcpeak#topic Bandit17:04
*** openstack changes topic to "Bandit (Meeting topic: security)"17:04
*** dg___ has joined #openstack-meeting-alt17:04
tmcpeakprobably not much here either, huh?17:04
dg___o/17:05
tmcpeakahh, Chivers17:05
tmcpeakyou have anything you want to say on Anchor or no?17:05
tkelseynope, quiet times17:05
tkelseybandit ^17:05
*** huichun has quit IRC17:05
dg___ditto, not touched anchor this week. soon17:05
tmcpeakcool easy enough17:05
*** nkinder has joined #openstack-meeting-alt17:05
tmcpeakI'll tell you where there aren't quiet times17:05
*** ninag_ has quit IRC17:05
tmcpeak#topic Syntribos17:05
*** openstack changes topic to "Syntribos (Meeting topic: security)"17:05
*** ninag has joined #openstack-meeting-alt17:05
tmcpeaknkinder: thank you for joining17:06
nkindertmcpeak: sure17:06
tmcpeakwe'll have the Syntribos team do an update and OSSN is next up17:06
michaelxinmdong: go ahead17:06
*** s3wong has joined #openstack-meeting-alt17:06
mdongso this past week we’ve done a deep dive into improving our tests17:06
*** niloofar_ has quit IRC17:06
*** Niloofar has joined #openstack-meeting-alt17:07
mdongwe’ve taken a second pass on our current security test cases, mostly to streamline them and reduce false positives17:07
mdongrahulunair and vinaypotluri have also been working on creating new test cases17:07
tmcpeakawesome17:08
tmcpeakI see tons of activity in the channel17:08
ccneillwe'll be doing another design session soon to tackle some architectural changes we're contemplating, including removing OpenCAFE and changing the way we detect "failures"17:08
ccneilli.e. making it easier to write further test cases17:08
ccneillthanks to elmiko I think we have a pretty good idea of what a transition to oslo.logging and oslo.config will look like from CAFE components17:09
michaelxinWe are using the broken API that we talked before as our test bed.17:09
michaelxinThe running against the broken API should start this week.17:09
ccneillyes, we should be running all our basic tests against that API by next week17:09
ccneillbut yeah, we'll start today/tomorrow17:10
tmcpeakhow are you guys running it, just manually?17:10
*** sicarie has joined #openstack-meeting-alt17:10
rhalliseyhello.  Sorry I'm late17:10
ccneillyeah, local environment17:10
tmcpeakyou guys have tox or something to pull down broken API and run Syntribos against it?17:10
*** julim has joined #openstack-meeting-alt17:10
tmcpeakthat would be cool, kind of like Syntribos functional tests17:10
ccneillyeah we might do that17:10
ccneillprobably better than bundling it into the repo itself17:11
michaelxinThat would be cool.17:11
ccneillhaven't gotten to that point just yet17:11
ccneillbut it's doable17:11
tmcpeakwould make a cool demo17:11
michaelxinCurrently, the broken api is running use docker tool17:11
michaelxinlocally17:11
*** doug-fish has joined #openstack-meeting-alt17:11
tmcpeakI've found running against our bandit examples directory to be the best way to quickly show somebody its value17:11
*** doug-fish has quit IRC17:11
*** jmckind has joined #openstack-meeting-alt17:12
tmcpeakwould be really cool to get something similar for Syntribos17:12
ccneillyep, we're using the vAPI as our sort of "proof" that we can detect X vulnerabilities17:12
*** doug-fish has joined #openstack-meeting-alt17:12
tmcpeakvery cool17:12
*** ddieterly is now known as ddieterly[away]17:12
ccneillI think there will be a good synergy between syntribos + bandit too17:12
tmcpeakyeah17:12
tmcpeakI've shown some of the IBM guys and they're really interested17:12
ccneillnice17:12
ccneillin Syntribos? or bandit?17:12
*** edwardb_ has quit IRC17:12
tmcpeakSyntribos17:12
ccneillsweet17:13
ccneillwell hopefully we have something to show off very soon :)17:13
tmcpeakawesome, great work guys17:13
ccneillI think that's about it for now17:13
tmcpeakcool17:13
tmcpeak#topic OSSN17:13
*** openstack changes topic to "OSSN (Meeting topic: security)"17:13
tmcpeaknkinder: around? :)17:13
*** paul-carlton2 has quit IRC17:13
tmcpeakhyakuhei:17:14
hyakuheiHey17:14
*** paul-carlton2 has joined #openstack-meeting-alt17:14
*** edwardb has joined #openstack-meeting-alt17:14
tmcpeakgot nkinder to join17:14
nkindertmcpeak: yep, I'm here17:14
tmcpeakI assume it was you that put you wanted his input on the etherpad, yeah?17:14
*** jmckind_ has quit IRC17:14
hyakuheiSo we’ve spoken a few times about converting or otherwising magicing OSSNs into a more machine-readable / searchable format17:14
tmcpeakyeah talked a bit at the summit about it too17:15
nkinderYeah, we specifically looked at YAML ni the past17:15
hyakuheiAs much as we’d like to fix things with parsing / scripts - I was going to suggest that we have a manual sprint at the summit to change the OSSNs out17:15
nkinderthough SCAP would be interesting too17:15
*** jonaspf1 has quit IRC17:15
hyakuheiSCAP gets pretty vendo specific I think17:15
hyakuheiThough some tool that takes OSSN from YAML -> SCAP (with additional content from the person doing the conversion) could be interesting17:15
*** shashank_hegde has joined #openstack-meeting-alt17:16
hyakuheiSo my proposal would be to agree a YAML schema/format  before the mid-cycle17:16
nkinderIf we agree on a format, I think the conversion won't be too bad17:16
lhindsGuesses are that currently people are manually cherry picking from the notes or the security guide17:16
nkinderI have a tool that was converting to YAML, but we didn't have an exact format that we ever agreed on17:16
tmcpeakI think the original format of OSSN took us pretty far and we've been hesitant to move forward with YAML out of concern for preserving legacy, yeah?17:17
hyakuheiSounds about right. I think the time is right to move onto something more usable overall17:17
tmcpeak+117:18
nkinderPartially that, but we also had a concern that less people would volunteer to write them in YAML (it's more of a barrier to entry)17:18
hyakuheiSearch being particularly interesting17:18
michaelxin+1 for searching17:18
nkinderbut a parseable format would be nice17:18
tmcpeakthere's also an issue for how to handle things like code snippets nicely17:18
hyakuheiYup that was a concern but nominally it’s either developers or established peoples who are happy to write YAML now.17:18
hyakuheitmcpeak: Interesting17:18
nkinderyeah, there are a few things that become tough in YAML17:19
*** inc0 has joined #openstack-meeting-alt17:19
hyakuheiHmmm. Do the VMT ever run into this problem? gmurphy_ ?17:20
nkinderI have some YAML tools here - https://github.com/nkinder/ossn-tools17:20
hyakuheiI’m open to other formats17:20
nkinderThere was some other standard in this area that I looked into at one point17:20
hyakuheiSo nkinder. Are you in favor of the move in principle?17:20
gmurphy_sorry only half watching..17:21
gmurphy_what now?17:21
tmcpeakgmurphy_: does VMT run into issues with code snippets in YAML for OSSA?17:21
hyakuheiDo you run into problems with YAML when describing vulns, code snippets etc17:21
tmcpeakand if so, how is it solved?17:21
gmurphy_we don't include code snippets..17:21
hyakuheigood lot of use you are gmurphy_ ….17:21
gmurphy_or haven't historically.17:21
*** Na3iL has quit IRC17:21
nkinderhyakuhei: yeah, I'm fine with it.  I think there are big benefits if we add a scanning tool17:21
tmcpeakyeah, pain for dealing with code snippets in some cases is less than benefit for creating a searchable format17:22
ccneillone way to solve for code snippets: link out to github commits?17:22
nkinder...by scanning tool, I mean that a deployer can create a simple config file that says things about their deployment (versions, services used, etc.), then the tool can find all relevant notes17:22
tmcpeakccneill: that could definitely work in a lot of cases17:22
tmcpeaknkinder: +117:22
hyakuheiThat being the case nkinder, how involved in the work do you want to be? I’m happy for you to lead the charge or to let it happen, up to you …17:22
*** nadya has joined #openstack-meeting-alt17:23
nkinderWe could link to a published note on the wiki with code snippets17:23
hyakuheiccneill: Code snippets tend to be around config changes etc17:23
*** Na3iL has joined #openstack-meeting-alt17:23
hyakuheiYAML needs a “”” type thing from python :D17:23
* hyakuhei hides.17:23
nkinderhyakuhei: I'm happy to be involved, but my time is a bit thin as of late17:23
ccneillhyakuhei: we could just gzip/b64 any text blobs in the YAML?17:24
ccneillugly as all hell, but if linking out isn't an option, it's something17:24
hyakuheiRighto, so what’s the best way to manage this? Should we start by smashing things into an etherpad? Do we want a security spec to work through the YAML format?17:24
ccneillor maybe link out to a textfile hosted in the same location as the OSSNs17:24
nkinderCVRF was the format I looked into previously17:24
*** anilvenkata has joined #openstack-meeting-alt17:24
hyakuheiccneill: I’d like the YAML to be true YAML i.e human readable.17:24
tmcpeakccneill: text file link could work17:24
tmcpeakI'd prefer that over B6417:24
ccneillB64 definitely makes review/human reading (without a tool) harder17:25
hyakuheiBasically I’d like it if it was all native YAML and then we can have tools for cross publishing, making things searchable etc.17:25
tmcpeakwell code snippets are pretty central to a fair amount of notes so whatever we get has to address that well17:25
hyakuheiHmmm, I imagine Ansible may have fixed this, aren’t there playbooks YAML? They must have to do smart things with code.17:25
*** banix has joined #openstack-meeting-alt17:25
lhindshyakuhei, major is doing a lot there17:26
tmcpeakhyakuhei: not fixed17:26
hyakuheilol17:26
lhindswe can use the remediation snippets17:26
lhindsas examples17:26
tmcpeakI've had a hard time with getting unedited code in yaml17:26
lhindsthere is also a lot of the OSSN stuff in SCAP already17:26
lhindswe borrow back :)17:26
tmcpeaklhinds: link?17:26
nkinderHere's a YAML converted OSSN - http://paste.openstack.org/show/497764/17:26
tmcpeakthis one is easy bc no snippets17:27
nkinderlet me find one with snippets...17:27
lhindshttps://github.com/OpenSCAP/scap-security-guide/tree/master/OpenStack/RHEL-OSP/7/input/oval17:27
tmcpeakoh yeah, XML17:27
nkinderHere's one with an example snippet - http://paste.openstack.org/show/497765/17:28
tmcpeakI despise XML but it does tend to handle snippets pretty well17:28
lhindshttps://github.com/rackerlabs/openstack-ansible-security17:28
nkinderSCAP is a bit different, because it can deal with actual scanning and remediation with some tools17:29
*** stingaci has joined #openstack-meeting-alt17:29
tmcpeaknkinder: the snippet here isn't awful17:29
nkinder...but it needs knowledge about the platform, so it is vendor/platform specific17:29
hyakuheiSCAP gets quite distro specific quite quickly I think17:29
tmcpeaknot great but isn't awful either17:29
gmurphy_what about sticking with the markdown and embedding metadata somehow (maybe like this - https://pythonhosted.org/Markdown/extensions/meta_data.html)17:29
*** stingaci has quit IRC17:29
nkinderso the YAML my utility produces was designed to be able to spit back out the text form we're been publishing17:30
nkinderMaybe that should not be a goal...17:30
tmcpeaknkinder: yeah I think we can relax that constraint17:30
*** paul-carlton2 has quit IRC17:30
nkinderI had thought we'd want a human readable form like now, but a YAML form that can be used for parsing17:30
tmcpeakgmurphy_: MD is nice but most of the note would end up being metadata anyway, huh?17:30
hyakuheinkinder: +117:30
*** minwang2 has joined #openstack-meeting-alt17:30
nkinderso some things can be simplified in the YAML if we change the goals17:30
*** spotz is now known as spotz_zzz17:30
tmcpeakyep yep17:31
nkinderFor example, you can see that I have a separate item for each paragraph in the "description" section17:31
michaelxinWhat's the goals here again?17:31
tmcpeakgoal is easily parseable yet also human readable17:31
hyakuheiYup17:31
ccneillhmmm..17:31
ccneillmaybe bad idea, but what if we just make a pretty web UI that generates markdown in a VERY specific way17:32
*** minwang2 has quit IRC17:32
*** mrmartin has joined #openstack-meeting-alt17:32
ccneilland build our own parser for the MD we generate17:32
hyakuheiThough actually being directly human readable is a weak requirement if we have something from which a human readable version can easily be derived17:32
nkinderThe direction I was going with this in the past was that YAML would be the canonical format that we commit to the repo17:32
gmurphy_tmcpeak: but isn't the point to have some way of linking the note to an actual version of openstack deployed. you would only need to a small set of metadata to achieve this. e.g. the whole document wouldn't necessarily need to be machine parseable…17:32
hyakuheinkinder: +117:32
nkinder...and we can convert to a human readable form to publish on the wiki17:32
*** reldan has joined #openstack-meeting-alt17:32
nkinderI didn't focus on making the YAML the readable format17:33
*** mickeys has joined #openstack-meeting-alt17:33
tmcpeakok so one question is, do we want to maintain multiple copies of one note or not17:33
hyakuheiWe want _all_ the info. In _one_ place. With tools that take that info and make a searchable OSSN DB, a human readable OSSN etc17:33
tmcpeakI would say no17:33
*** fawadkhaliq has quit IRC17:33
tmcpeakone shot is either human readable or easily converted to human readable AND contains all the data needed to enable our searches17:33
*** dukhlov has joined #openstack-meeting-alt17:34
hyakuheiSo no, the OSSN doesn’t have to be strictly human readable in YAML but I would like it to be self contained so that the published OSSN and various other tooling can all use the same YAML.17:34
*** pnavarro has joined #openstack-meeting-alt17:34
nkinderhyakuhei: +117:34
*** spotz_zzz is now known as spotz17:34
tmcpeakcool17:34
hyakuheiwhich I guess potentially puts B64 back on the table as an easy way to encode messy stuff17:34
*** Na3iL has quit IRC17:34
tmcpeakyeah17:34
hyakuheiAlthough it’s ugly from a git POV17:35
gmurphy_yeah that makes sense. i was just trying to think of a way around the code snippets etc.17:35
hyakuheireviewing OSSNs etc17:35
tmcpeaknot that bad, just have a tox env or something that converts17:35
michaelxinsound like a good plan17:35
tmcpeakhrmm, yeah17:35
tmcpeaknot great actually17:35
ccneillBSON17:35
ccneill:D17:35
ccneill(jk)17:35
elmikolol17:36
lhindsWhat's the issue with parsing out the values from MD to YAML? I missed the gotcha?17:36
*** reldan has quit IRC17:36
*** mrmartin has quit IRC17:36
hyakuheilhinds: The MD is weakly enforced. No particularly solid schema17:36
ccneillthat's why I was thinking maybe we enforce that by making a tool that you build an OSSN in17:37
*** anilvenkata has quit IRC17:37
ccneilland it spits out MD in a format we can easily parse17:37
ccneilleven if that doesn't map to an existing standard17:37
ccneill¯\_(ツ)_/¯17:37
hyakuheiA tool to write a doc?17:37
ccneilldefinitely a bit of work to make it happen17:37
tmcpeakthat's a lot of engineering work17:37
ccneillyep17:37
*** EricGonczer_ has joined #openstack-meeting-alt17:37
hyakuheiWe’d be better off having a WSDL17:37
ccneillhaha17:37
nkinderThat's sort of what I developed...17:37
tmcpeakmight be over-engineering this17:37
*** dg___ has quit IRC17:37
hyakuhei+117:38
nkinderYou can write in the plain text form, then convert to YAML (or vice-versa)17:38
tmcpeakok so we like YAML, only problem is how to handle the base64 snippet for review?17:38
michaelxinbuild on nkinder's current tools is better17:38
hyakuheiAsk a room full of engineers to write a document.17:38
ccneillhaha17:38
hyakuheiSo potentially we could have a gate job extract, decode and show/add the b64 if that’s the route we went17:38
hyakuheiok, lets all have a think about this17:38
*** ddieterly[away] is now known as ddieterly17:39
*** pnavarro has quit IRC17:39
hyakuheiand talk more next week?17:39
tmcpeakrathole deferred until next week? same time?17:39
hyakuhei++17:39
nkinderIt would probably be useful if someone looked more closely at the tools I wrote17:39
hyakuheiI’ll try to stab at it17:39
nkinder..then can give some feedback17:39
tmcpeaksounds good17:39
nkinderThe one problem with code snippets in it right now is that you lose line feeds17:39
michaelxinhow often do we have code snippet?17:40
nkinderpretty often17:40
ccneillnkinder: looks pretty reasonable to me17:40
ccneillfrom a quick skim17:40
nkinder..but it's usually for configuration file snippets17:40
ccneillif the MD format is enforced consistently enough17:40
nkinderwe rarely show actual code17:40
hyakuheiYeah it’s more configs17:40
ccneillhmmm... is there some way we could abstract that away?17:41
ccneilllike have a schema for various config changes?17:41
ccneillsorry, I keep trying to make this as complicated as possible :P17:41
hyakuheiNo way17:41
*** EricGonc_ has joined #openstack-meeting-alt17:41
*** bana_k has quit IRC17:41
ccneillfair enough17:41
hyakuheiSome configs are pure python, many are custom logic, some are strange magic17:42
*** lpetrut has quit IRC17:42
michaelxincan we use Block literals for it?17:42
*** Kuwagata_ has quit IRC17:42
nkindermichaelxin: I think we'll have to do something like that17:42
ccneill...what if we just wrote OSSNs as a Python class with a to_yaml method? O_o17:42
tmcpeakmichaelxin: that would be the easiest17:42
ccneillsomewhat similar to setup.py17:43
tmcpeakI don't know how well it works for code snippets though17:43
lhindsThere is a echo=FALSE in MD - we could put in our own tags17:43
*** dg__ has joined #openstack-meeting-alt17:43
tmcpeakallright guys, glad we're having this discussion17:43
michaelxincan we try it for a couple of existing ones?17:43
tmcpeakseems like we've got buy in to do OSSN v 217:44
lhindsis it not more stuff like file perm octals, key / values though?17:44
tmcpeakmaybe have some plays and come back next week with ideas?17:44
tmcpeakdo want to have some time to chat midcycle17:44
hyakuheiYup, lets get through the rest of the agenda.17:44
*** EricGonczer_ has quit IRC17:45
diazjf1tmcpeak, hyakuhei, so I started an etherpad here: https://etherpad.openstack.org/p/barbican-security-midcycle-N17:45
*** tonytan4ever has quit IRC17:45
tmcpeak#topic Midcycle17:45
*** openstack changes topic to "Midcycle (Meeting topic: security)"17:45
*** apetrich has joined #openstack-meeting-alt17:45
diazjf1Having the security midcycle with the barbican midcycle worked out last year and I wanted to see everyones opinion on having both sessions together17:45
diazjf1I am also working on getting space at IBM@Austin17:45
diazjf1I wanted to get opinions as well as a list of potential attendees17:46
hyakuheiI’m very much in favor of an overlapping midcycle again17:46
diazjf1#link https://etherpad.openstack.org/p/barbican-security-midcycle-N17:46
tmcpeak+117:46
*** sarob has joined #openstack-meeting-alt17:46
michaelxin+117:46
hyakuheidiazjf1: ping me a mail if you need support for IBM@Austin17:46
elmiko+tacos17:47
nkinderI think overlapping would work nicely17:47
hyakuheiI assumed Rack when I saw Austin17:47
nkinderhyakuhei: Especially if we want to proceed more on the certmonger/anchor documentation we talked about at the Summit17:47
michaelxindoug and I talked about this.17:47
hyakuheiDefinitely17:47
*** daemontool has quit IRC17:47
michaelxinLet IBM try it first17:47
hyakuheiRighto17:47
michaelxinwe can serve as backup17:47
diazjf1cool, yeah I'll keep you guys posted.17:48
michaelxindiazjf1: +117:48
hyakuheiRighto, let me know if I can help17:48
hyakuheiAnything else on the agenda for today?17:49
diazjf1Please add your info to the etherpad17:49
sicarieblog post review: https://github.com/openstack-security/openstack-security.github.io/pull/2417:49
hyakuheiThanks sicarie17:50
*** kzaitsev_mb has quit IRC17:51
*** jmckind has quit IRC17:51
hyakuheiCool, anything else ?17:52
*** pnavarro has joined #openstack-meeting-alt17:52
*** dukhlov has quit IRC17:52
tmcpeakshould be a wrap17:53
*** bana_k has joined #openstack-meeting-alt17:53
hyakuheiExcellent. Thanks everyone!17:53
michaelxinthanks17:53
tmcpeakthanks everybody!17:53
tmcpeak#endmeeting17:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:53
openstackMeeting ended Thu May 19 17:53:53 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/security/2016/security.2016-05-19-17.00.html17:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/security/2016/security.2016-05-19-17.00.txt17:53
*** sicarie has quit IRC17:53
openstackLog:            http://eavesdrop.openstack.org/meetings/security/2016/security.2016-05-19-17.00.log.html17:53
*** gmurphy_ has left #openstack-meeting-alt17:54
*** kevo has joined #openstack-meeting-alt17:54
ccneillo/17:54
elmikothanks tmcpeak, hyakuhei17:54
*** dukhlov has joined #openstack-meeting-alt17:54
*** elmiko has left #openstack-meeting-alt17:54
nkinderthanks!17:54
lhindsthanks *17:54
*** nkinder has left #openstack-meeting-alt17:54
*** mdong has left #openstack-meeting-alt17:54
*** ccneill has left #openstack-meeting-alt17:55
*** rmart04 has quit IRC17:55
*** tmcpeak has left #openstack-meeting-alt17:55
*** Kuwagata has joined #openstack-meeting-alt17:55
*** rhallisey has left #openstack-meeting-alt17:56
diazjf1thanks guys17:56
*** lhinds has quit IRC17:57
*** tbarron has left #openstack-meeting-alt17:57
*** tonytan4ever has joined #openstack-meeting-alt17:57
*** dg__ has quit IRC17:58
*** dukhlov has quit IRC17:58
*** AdmiralQi has quit IRC17:59
*** dukhlov has joined #openstack-meeting-alt17:59
*** tkelsey has quit IRC17:59
*** SumitNaiksatam has joined #openstack-meeting-alt18:00
*** dean has joined #openstack-meeting-alt18:00
*** dean is now known as Guest6642218:00
*** tango has joined #openstack-meeting-alt18:01
*** ddieterly is now known as ddieterly[away]18:02
*** Nikolay_St has quit IRC18:05
*** tango has quit IRC18:05
*** Guest66422 has quit IRC18:06
*** nadya has quit IRC18:10
*** dukhlov has quit IRC18:12
*** enriquetaso has joined #openstack-meeting-alt18:12
*** ninag has quit IRC18:15
*** doug-fis_ has joined #openstack-meeting-alt18:16
*** ninag has joined #openstack-meeting-alt18:16
*** ninag has quit IRC18:17
*** eharney has quit IRC18:18
*** ninag has joined #openstack-meeting-alt18:18
*** nadya has joined #openstack-meeting-alt18:18
*** dprince has quit IRC18:18
*** doug-fish has quit IRC18:19
*** ninag has quit IRC18:24
*** ninag has joined #openstack-meeting-alt18:25
*** tkelsey has joined #openstack-meeting-alt18:26
*** noslzzp has quit IRC18:26
*** lennyb has quit IRC18:26
*** dosaboy has quit IRC18:26
*** dmellado has quit IRC18:26
*** crinkle has quit IRC18:26
*** lifeless has quit IRC18:26
*** Daviey has quit IRC18:26
*** bogdando has quit IRC18:26
*** jimholl_ has quit IRC18:26
*** edleafe has quit IRC18:26
*** dosaboy has joined #openstack-meeting-alt18:26
*** Daviey has joined #openstack-meeting-alt18:26
*** bogdando has joined #openstack-meeting-alt18:26
*** lifeless has joined #openstack-meeting-alt18:26
*** lennyb has joined #openstack-meeting-alt18:27
*** dmellado has joined #openstack-meeting-alt18:27
*** crinkle has joined #openstack-meeting-alt18:27
*** jimholl_ has joined #openstack-meeting-alt18:27
*** ninag has quit IRC18:27
*** ninag has joined #openstack-meeting-alt18:28
*** timirnich has quit IRC18:30
*** tkelsey has quit IRC18:30
*** tpsilva has quit IRC18:31
*** monester has quit IRC18:31
*** sweston has quit IRC18:31
*** edleafe has joined #openstack-meeting-alt18:31
*** teran has quit IRC18:31
*** vmtyler has quit IRC18:31
*** kgalanov has quit IRC18:31
*** zhiyan has quit IRC18:31
*** kgalanov has joined #openstack-meeting-alt18:33
*** teran has joined #openstack-meeting-alt18:33
*** vmtyler has joined #openstack-meeting-alt18:33
*** tpsilva has joined #openstack-meeting-alt18:33
*** _sarob has joined #openstack-meeting-alt18:34
*** timirnich has joined #openstack-meeting-alt18:34
*** sweston has joined #openstack-meeting-alt18:34
*** zhiyan has joined #openstack-meeting-alt18:34
*** jprovazn has quit IRC18:35
*** monester has joined #openstack-meeting-alt18:35
*** sarob has quit IRC18:37
*** Akanksha08 has joined #openstack-meeting-alt18:38
*** baoli_ has quit IRC18:42
*** ninag has quit IRC18:42
*** enriquetaso has quit IRC18:43
*** ihrachys has joined #openstack-meeting-alt18:43
*** rcernin has joined #openstack-meeting-alt18:46
*** tango has joined #openstack-meeting-alt18:46
*** kzaitsev_mb has joined #openstack-meeting-alt18:46
*** lpetrut has joined #openstack-meeting-alt18:48
*** dimtruck is now known as zz_dimtruck18:51
*** jmckind has joined #openstack-meeting-alt18:52
*** dukhlov has joined #openstack-meeting-alt18:54
*** Sukhdev has joined #openstack-meeting-alt18:55
*** pnavarro has quit IRC18:55
*** nadya has quit IRC18:57
*** doug-fis_ has quit IRC18:58
*** ninag has joined #openstack-meeting-alt19:01
*** _sarob has quit IRC19:01
*** salv-orlando has quit IRC19:01
*** mickeys has quit IRC19:02
*** mickeys has joined #openstack-meeting-alt19:02
*** ddieterly[away] has quit IRC19:02
*** dshakhray has quit IRC19:02
*** sarob has joined #openstack-meeting-alt19:03
*** dshakhray has joined #openstack-meeting-alt19:05
*** dukhlov has quit IRC19:05
*** jmckind_ has joined #openstack-meeting-alt19:06
*** mickeys has quit IRC19:07
*** sdague has quit IRC19:08
*** thomnico has joined #openstack-meeting-alt19:08
*** ganso has left #openstack-meeting-alt19:08
*** jmckind has quit IRC19:09
*** doug-fish has joined #openstack-meeting-alt19:09
*** sdague has joined #openstack-meeting-alt19:09
*** salv-orlando has joined #openstack-meeting-alt19:10
*** ijw has quit IRC19:16
*** SumitNaiksatam has left #openstack-meeting-alt19:16
*** mandre has left #openstack-meeting-alt19:20
*** Akanksha08 has left #openstack-meeting-alt19:20
*** iberezovskiy is now known as iberezovskiy_afk19:25
*** ddieterly has joined #openstack-meeting-alt19:26
*** SumitNaiksatam has joined #openstack-meeting-alt19:28
*** baoli has joined #openstack-meeting-alt19:30
*** SumitNaiksatam has quit IRC19:32
*** nadya has joined #openstack-meeting-alt19:33
*** banix has quit IRC19:33
*** stingaci has joined #openstack-meeting-alt19:34
*** tpsilva has quit IRC19:37
*** ninag has quit IRC19:37
*** ninag has joined #openstack-meeting-alt19:38
*** MeganR has quit IRC19:40
*** jmckind_ has quit IRC19:42
*** ninag has quit IRC19:42
*** dshakhray has quit IRC19:47
*** ddieterly is now known as ddieterly[away]19:51
*** cartik has joined #openstack-meeting-alt19:53
*** thomnico has quit IRC19:58
*** mickeys has joined #openstack-meeting-alt20:01
*** jlvillal has joined #openstack-meeting-alt20:01
*** gyee has joined #openstack-meeting-alt20:02
*** mickeys has quit IRC20:02
*** mickeys_ has joined #openstack-meeting-alt20:03
*** sarob has quit IRC20:03
*** Sukhdev has quit IRC20:06
*** ddieterly[away] is now known as ddieterly20:06
*** sarob has joined #openstack-meeting-alt20:07
*** amrith is now known as _amrith_20:09
*** HeOS has joined #openstack-meeting-alt20:13
*** banix has joined #openstack-meeting-alt20:13
*** matrohon has joined #openstack-meeting-alt20:13
*** doug-fish has quit IRC20:15
*** markvoelker has joined #openstack-meeting-alt20:15
*** ijw has joined #openstack-meeting-alt20:18
*** markvoelker has quit IRC20:20
*** ddieterly is now known as ddieterly[away]20:30
*** Ravikiran_K has quit IRC20:30
*** rarcea has joined #openstack-meeting-alt20:31
*** Sukhdev has joined #openstack-meeting-alt20:32
*** daemontool has joined #openstack-meeting-alt20:32
*** ewilson has quit IRC20:33
*** piet has quit IRC20:35
*** HeOS has quit IRC20:35
*** ansmith has quit IRC20:36
*** doug-fish has joined #openstack-meeting-alt20:39
*** ninag has joined #openstack-meeting-alt20:39
*** rdopiera has quit IRC20:40
*** julim has quit IRC20:42
*** rdopiera has joined #openstack-meeting-alt20:42
*** julim has joined #openstack-meeting-alt20:42
*** doug-fish has quit IRC20:43
*** doug-fish has joined #openstack-meeting-alt20:43
*** yamamoto has joined #openstack-meeting-alt20:44
*** Yogi1 has quit IRC20:44
*** salv-orl_ has joined #openstack-meeting-alt20:48
*** panda has quit IRC20:48
*** panda has joined #openstack-meeting-alt20:49
*** cknight1 has quit IRC20:50
*** baoli has quit IRC20:50
*** rdopiera has quit IRC20:50
*** rdopiera has joined #openstack-meeting-alt20:51
*** tonytan4ever has quit IRC20:51
*** salv-orlando has quit IRC20:51
*** sgotliv_ has quit IRC20:55
*** zz_dimtruck is now known as dimtruck20:57
*** cartik has quit IRC21:00
*** ddieterly[away] is now known as ddieterly21:00
*** dukhlov has joined #openstack-meeting-alt21:03
*** rebase has joined #openstack-meeting-alt21:08
*** dukhlov has quit IRC21:08
*** weshay has quit IRC21:10
*** yamahata has quit IRC21:11
*** mickeys_ has quit IRC21:11
*** mickeys has joined #openstack-meeting-alt21:11
*** dshakhray has joined #openstack-meeting-alt21:13
*** mihgen has left #openstack-meeting-alt21:13
*** ninag has quit IRC21:14
*** mickeys has quit IRC21:15
*** mickeys has joined #openstack-meeting-alt21:16
*** ihrachys has quit IRC21:16
*** ihrachys has joined #openstack-meeting-alt21:17
*** mickeys has quit IRC21:18
*** mickeys has joined #openstack-meeting-alt21:19
*** julim has quit IRC21:20
*** mickeys has quit IRC21:23
*** piet has joined #openstack-meeting-alt21:23
*** matrohon has quit IRC21:25
*** MarkBaker has quit IRC21:27
*** Niloofar has quit IRC21:31
*** edtubill has quit IRC21:33
*** cknight has joined #openstack-meeting-alt21:35
*** baoli has joined #openstack-meeting-alt21:36
*** doug-fish has quit IRC21:38
*** sdake has quit IRC21:39
*** mickeys has joined #openstack-meeting-alt21:39
*** Kuwagata has quit IRC21:40
*** doug-fish has joined #openstack-meeting-alt21:44
*** shadower has quit IRC21:44
*** shadower has joined #openstack-meeting-alt21:45
*** kzaitsev_mb has quit IRC21:47
*** ewilson has joined #openstack-meeting-alt21:48
*** doug-fish has quit IRC21:49
*** doug-fish has joined #openstack-meeting-alt21:50
*** kfarr has quit IRC21:52
*** Sukhdev has quit IRC21:53
*** ewilson has quit IRC21:54
*** doug-fish has quit IRC21:54
*** Sukhdev has joined #openstack-meeting-alt21:56
*** ewilson has joined #openstack-meeting-alt21:56
*** daemontool has quit IRC21:57
*** apetrich has quit IRC21:57
*** ewilson has quit IRC21:59
*** Swami has quit IRC22:01
*** ewilson has joined #openstack-meeting-alt22:02
*** IlyaG has quit IRC22:03
*** nadya has quit IRC22:07
*** ddieterly is now known as ddieterly[away]22:07
*** cknight1 has joined #openstack-meeting-alt22:10
*** amitgandhinz has quit IRC22:11
*** HeOS has joined #openstack-meeting-alt22:12
*** cknight has quit IRC22:13
*** ewilson has quit IRC22:13
*** ewilson has joined #openstack-meeting-alt22:13
*** ewilson has quit IRC22:15
*** ewilson has joined #openstack-meeting-alt22:16
*** sigmavirus24 is now known as sigmavirus24_awa22:20
*** dshakhray has quit IRC22:21
*** rcernin has quit IRC22:23
*** rossella_s has quit IRC22:23
*** rossella_s has joined #openstack-meeting-alt22:24
*** ewilson has quit IRC22:25
*** jaypipes has quit IRC22:25
*** markvoelker has joined #openstack-meeting-alt22:27
*** mixos has quit IRC22:28
*** markvoelker has quit IRC22:29
*** ddieterly[away] is now known as ddieterly22:29
*** markvoelker has joined #openstack-meeting-alt22:29
*** sdake has joined #openstack-meeting-alt22:30
*** dukhlov has joined #openstack-meeting-alt22:32
*** spotz is now known as spotz_zzz22:33
*** HeOS has quit IRC22:35
*** dukhlov has quit IRC22:37
*** lpetrut has quit IRC22:37
*** ninag has joined #openstack-meeting-alt22:38
*** sdague has quit IRC22:39
*** ninag has quit IRC22:41
*** kzaitsev_mb has joined #openstack-meeting-alt22:44
*** doug-fish has joined #openstack-meeting-alt22:44
*** doug-fish has quit IRC22:44
*** sdake has quit IRC22:45
*** IlyaG has joined #openstack-meeting-alt22:47
*** IlyaG has quit IRC22:48
*** IlyaG_ has joined #openstack-meeting-alt22:48
*** ddieterly has quit IRC22:51
*** banix has quit IRC22:52
*** diazjf1 has quit IRC22:54
*** kszukielojc has quit IRC22:54
*** markvoelker has quit IRC22:58
*** padkrish has joined #openstack-meeting-alt23:01
*** dimtruck is now known as zz_dimtruck23:01
*** IlyaG_ has quit IRC23:03
*** ihrachys has quit IRC23:04
*** sdake has joined #openstack-meeting-alt23:04
*** Sukhdev has quit IRC23:05
*** Sukhdev has joined #openstack-meeting-alt23:08
*** cloudtrainme has quit IRC23:11
*** salv-orl_ has quit IRC23:12
*** sdake has quit IRC23:14
*** sdake has joined #openstack-meeting-alt23:15
*** amotoki has quit IRC23:21
*** sdake has quit IRC23:21
*** amotoki has joined #openstack-meeting-alt23:21
*** Swami has joined #openstack-meeting-alt23:23
*** mickeys has quit IRC23:26
*** amotoki has quit IRC23:26
*** Sukhdev has quit IRC23:27
*** mickeys has joined #openstack-meeting-alt23:27
*** rebase has quit IRC23:27
*** mickeys has quit IRC23:29
*** mickeys has joined #openstack-meeting-alt23:29
*** mickeys has quit IRC23:29
*** mickeys has joined #openstack-meeting-alt23:30
*** shashank_hegde has quit IRC23:30
*** zz_dimtruck is now known as dimtruck23:31
*** kei_yama has joined #openstack-meeting-alt23:31
*** kzaitsev_mb has quit IRC23:34
*** mickeys has quit IRC23:35
*** padkrish has quit IRC23:36
*** padkrish has joined #openstack-meeting-alt23:37
*** rarcea has quit IRC23:40
*** dimtruck is now known as zz_dimtruck23:41
*** padkrish has quit IRC23:42
*** kzaitsev_mb has joined #openstack-meeting-alt23:43
*** baoli has quit IRC23:44
*** zz_dimtruck is now known as dimtruck23:51
*** sdake has joined #openstack-meeting-alt23:52
*** mixos has joined #openstack-meeting-alt23:52
*** tango has quit IRC23:58
*** tango has joined #openstack-meeting-alt23:59

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