Tuesday, 2015-08-18

*** padkrish has joined #openstack-meeting-alt00:00
*** puranamr has quit IRC00:00
*** puranamr has joined #openstack-meeting-alt00:00
*** padkrish has quit IRC00:00
*** padkrish has joined #openstack-meeting-alt00:01
*** VW_ has quit IRC00:04
*** VW_ has joined #openstack-meeting-alt00:05
*** achanda_ has joined #openstack-meeting-alt00:05
*** kzaitsev_mb has quit IRC00:05
*** banix has quit IRC00:06
*** achanda has quit IRC00:07
*** harshs has quit IRC00:08
*** VW_ has quit IRC00:09
*** achanda_ has quit IRC00:09
*** agireud has joined #openstack-meeting-alt00:14
*** geoffarnold has quit IRC00:17
*** svinota has quit IRC00:17
*** banix has joined #openstack-meeting-alt00:17
*** zz_dimtruck is now known as dimtruck00:18
*** abdelwas has quit IRC00:19
*** carl_baldwin has quit IRC00:22
*** bharath has joined #openstack-meeting-alt00:23
*** minwang2 has quit IRC00:25
*** tsekiyama has quit IRC00:26
*** puranamr has quit IRC00:26
*** ivar-laz_ has joined #openstack-meeting-alt00:26
*** snackewm has quit IRC00:27
*** ivar-laz_ has quit IRC00:27
*** ivar-laz_ has joined #openstack-meeting-alt00:28
*** ashleighfarnham has quit IRC00:28
*** ivar-lazzaro has quit IRC00:29
*** woodster_ has quit IRC00:30
*** ivar-laz_ has quit IRC00:31
*** mtanino has quit IRC00:32
*** shashank_hegde has quit IRC00:32
*** puranamr has joined #openstack-meeting-alt00:33
*** davideagnello has quit IRC00:34
*** dims has joined #openstack-meeting-alt00:34
*** davideagnello has joined #openstack-meeting-alt00:34
*** merooney has joined #openstack-meeting-alt00:36
*** wojdev has quit IRC00:36
*** kzaitsev_mb has joined #openstack-meeting-alt00:36
*** puranamr has quit IRC00:37
*** Tango|2 has quit IRC00:37
*** davideagnello has quit IRC00:38
*** davideagnello has joined #openstack-meeting-alt00:38
*** carl_baldwin has joined #openstack-meeting-alt00:39
*** banix has quit IRC00:40
*** ashleighfarnham has joined #openstack-meeting-alt00:40
*** davideagnello has quit IRC00:41
*** davideag_ has joined #openstack-meeting-alt00:41
*** carl_baldwin has quit IRC00:43
*** kfarr has quit IRC00:43
*** priti has joined #openstack-meeting-alt00:43
*** ashleighfarnham has quit IRC00:44
*** merooney has quit IRC00:45
*** crc32 has joined #openstack-meeting-alt00:46
*** sputnik13 has quit IRC00:46
*** baoli has joined #openstack-meeting-alt00:46
*** sigmavirus24 is now known as sigmavirus24_awa00:49
*** Sukhdev has quit IRC00:50
*** baoli has quit IRC00:51
*** ashtokolov_ has quit IRC00:56
*** kzaitsev_mb has quit IRC00:56
*** jeadr has quit IRC01:01
*** jeadr has joined #openstack-meeting-alt01:01
*** dimtruck is now known as zz_dimtruck01:03
*** xyang1 has quit IRC01:08
*** shashank_hegde has joined #openstack-meeting-alt01:12
*** VW_ has joined #openstack-meeting-alt01:12
*** banix has joined #openstack-meeting-alt01:13
*** fnaval has quit IRC01:14
*** mtanino has joined #openstack-meeting-alt01:14
*** dkalleg has quit IRC01:20
*** fnaval has joined #openstack-meeting-alt01:20
*** pvaneck has quit IRC01:22
*** kzaitsev_mb has joined #openstack-meeting-alt01:23
*** bana_k has quit IRC01:23
*** salv-orlando has joined #openstack-meeting-alt01:29
*** padkrish has quit IRC01:29
*** padkrish has joined #openstack-meeting-alt01:29
*** esker has joined #openstack-meeting-alt01:30
*** priti has quit IRC01:31
*** padkrish has quit IRC01:34
*** priti has joined #openstack-meeting-alt01:34
*** ashleighfarnham has joined #openstack-meeting-alt01:34
*** fnaval has quit IRC01:34
*** salv-orlando has quit IRC01:35
*** esker has quit IRC01:36
*** ashleighfarnham has quit IRC01:39
*** zz_dimtruck is now known as dimtruck01:39
*** davideag_ has quit IRC01:41
*** padkrish has joined #openstack-meeting-alt01:44
*** s3wong has quit IRC01:45
*** yamahata has quit IRC01:51
*** kzaitsev_mb has quit IRC01:54
*** padkrish has quit IRC01:54
*** padkrish has joined #openstack-meeting-alt01:55
*** padkrish_ has joined #openstack-meeting-alt01:57
*** padkrish has quit IRC01:59
*** dane_leblanc has quit IRC01:59
*** yamamoto has joined #openstack-meeting-alt02:05
*** sankarshan_away is now known as sankarshan02:08
*** saurabhs has joined #openstack-meeting-alt02:08
*** jian5397 has joined #openstack-meeting-alt02:11
*** mtanino has quit IRC02:11
*** yamamoto has quit IRC02:14
*** kzaitsev_mb has joined #openstack-meeting-alt02:20
*** sbalukoff has quit IRC02:22
*** achanda has joined #openstack-meeting-alt02:23
*** kzaitsev_mb has quit IRC02:27
*** ashleighfarnham has joined #openstack-meeting-alt02:28
*** yamahata has joined #openstack-meeting-alt02:30
*** dims has quit IRC02:30
*** baojg has joined #openstack-meeting-alt02:31
*** yamahata has quit IRC02:32
*** yamahata has joined #openstack-meeting-alt02:32
*** jian5397 has quit IRC02:32
*** ashleighfarnham has quit IRC02:33
*** jian5397 has joined #openstack-meeting-alt02:33
*** padkrish_ has quit IRC02:35
*** padkrish has joined #openstack-meeting-alt02:36
*** jeadr has quit IRC02:38
*** jeadr has joined #openstack-meeting-alt02:38
*** oomichi has joined #openstack-meeting-alt02:40
*** padkrish has quit IRC02:40
*** jian5397 has quit IRC02:41
*** bswartz has joined #openstack-meeting-alt02:42
*** harshs has joined #openstack-meeting-alt02:42
*** lazy_prince has joined #openstack-meeting-alt02:45
*** shwetaap has joined #openstack-meeting-alt02:48
*** agireud has quit IRC02:49
*** esker has joined #openstack-meeting-alt02:51
*** tfukushima has quit IRC02:58
*** jeadr has quit IRC02:59
*** jeadr has joined #openstack-meeting-alt02:59
*** ashtokolov_ has joined #openstack-meeting-alt03:00
*** harshs_ has joined #openstack-meeting-alt03:00
*** harshs has quit IRC03:01
*** harshs_ is now known as harshs03:01
*** _amrith_ is now known as amrith03:01
*** baojg has quit IRC03:02
*** esker has quit IRC03:02
*** esker has joined #openstack-meeting-alt03:04
*** ashtokolov_ has quit IRC03:05
*** yamamoto has joined #openstack-meeting-alt03:06
*** shashank_hegde has quit IRC03:13
*** baojg has joined #openstack-meeting-alt03:15
*** shwetaap has quit IRC03:16
*** VW_ has quit IRC03:17
*** VW_ has joined #openstack-meeting-alt03:17
*** salv-orlando has joined #openstack-meeting-alt03:19
*** ganeshna has joined #openstack-meeting-alt03:20
*** VW_ has quit IRC03:22
*** jckasper has joined #openstack-meeting-alt03:25
*** esker has quit IRC03:26
*** snackewm has joined #openstack-meeting-alt03:26
*** salv-orlando has quit IRC03:26
*** esker has joined #openstack-meeting-alt03:26
*** pvaneck has joined #openstack-meeting-alt03:31
*** crc32 has quit IRC03:31
*** sdake has joined #openstack-meeting-alt03:32
*** lazy_prince has quit IRC03:33
*** shashank_hegde has joined #openstack-meeting-alt03:34
*** sdake_ has quit IRC03:36
*** esker has quit IRC03:37
*** esker has joined #openstack-meeting-alt03:38
*** markvoelker has quit IRC03:42
*** sdake_ has joined #openstack-meeting-alt03:42
*** nurla has quit IRC03:42
*** nurla has joined #openstack-meeting-alt03:43
*** VW_ has joined #openstack-meeting-alt03:43
*** wojdev has joined #openstack-meeting-alt03:44
*** jeadr has quit IRC03:45
*** jeadr has joined #openstack-meeting-alt03:45
*** sdake has quit IRC03:45
*** shwetaap has joined #openstack-meeting-alt03:46
*** baojg has quit IRC03:49
*** Prem_ has quit IRC03:54
*** jian5397 has joined #openstack-meeting-alt03:57
*** esker has quit IRC03:58
*** esker has joined #openstack-meeting-alt04:00
*** dimtruck is now known as zz_dimtruck04:00
*** jian5397 has quit IRC04:07
*** shashank_hegde has quit IRC04:09
*** coolsvap|away is now known as coolsvap04:10
*** shashank_hegde has joined #openstack-meeting-alt04:12
*** esker has quit IRC04:13
*** esker has joined #openstack-meeting-alt04:13
*** esker has quit IRC04:14
*** esker has joined #openstack-meeting-alt04:14
*** baojg has joined #openstack-meeting-alt04:16
*** ashleighfarnham has joined #openstack-meeting-alt04:18
*** esker has quit IRC04:20
*** sdake_ is now known as sdake04:22
*** shwetaap has quit IRC04:22
*** ashleighfarnham has quit IRC04:22
*** armax has joined #openstack-meeting-alt04:23
*** bana_k has joined #openstack-meeting-alt04:25
*** ganeshna has quit IRC04:29
*** ganeshna has joined #openstack-meeting-alt04:32
*** VW_ has quit IRC04:32
*** VW_ has joined #openstack-meeting-alt04:33
*** VW_ has quit IRC04:37
*** shashank_hegde has quit IRC04:38
*** markvoelker has joined #openstack-meeting-alt04:42
*** Tango|2 has joined #openstack-meeting-alt04:47
*** dave-mccowan has quit IRC04:47
*** markvoelker has quit IRC04:47
*** VW_ has joined #openstack-meeting-alt04:48
*** jeadr has quit IRC04:49
*** jeadr has joined #openstack-meeting-alt04:49
*** mestery has joined #openstack-meeting-alt04:59
*** banix has quit IRC05:02
*** sbalukoff has joined #openstack-meeting-alt05:04
*** gyee has quit IRC05:04
*** nkrinner has joined #openstack-meeting-alt05:06
*** mestery has quit IRC05:09
*** ashleighfarnham has joined #openstack-meeting-alt05:12
*** agireud has joined #openstack-meeting-alt05:12
*** mrmartin has joined #openstack-meeting-alt05:15
*** harshs has quit IRC05:15
*** ashleighfarnham has quit IRC05:16
*** pvaneck has quit IRC05:16
*** dims has joined #openstack-meeting-alt05:20
*** kzaitsev_mb has joined #openstack-meeting-alt05:23
*** bharath has quit IRC05:26
*** dims has quit IRC05:26
*** VW_ has quit IRC05:27
*** kzaitsev_mb has quit IRC05:27
*** jeadr has quit IRC05:30
*** jeadr has joined #openstack-meeting-alt05:30
*** padkrish has joined #openstack-meeting-alt05:31
*** padkrish has quit IRC05:31
*** padkrish has joined #openstack-meeting-alt05:32
*** yamamoto has quit IRC05:32
*** vgridnev has joined #openstack-meeting-alt05:34
*** tfukushima has joined #openstack-meeting-alt05:34
*** salv-orlando has joined #openstack-meeting-alt05:37
*** lsmola has joined #openstack-meeting-alt05:39
*** tfukushima has quit IRC05:39
*** nadya has joined #openstack-meeting-alt05:40
*** ildikov has quit IRC05:40
*** nadya has quit IRC05:42
*** achanda has quit IRC05:43
*** shashank_hegde has joined #openstack-meeting-alt05:44
*** achanda has joined #openstack-meeting-alt05:47
*** salv-orlando has quit IRC05:50
*** Sukhdev has joined #openstack-meeting-alt05:51
*** yamamoto has joined #openstack-meeting-alt05:51
*** nadya has joined #openstack-meeting-alt05:51
*** priti has quit IRC05:52
*** yamamoto has quit IRC05:53
*** vgridnev has quit IRC05:53
*** yamamoto has joined #openstack-meeting-alt05:53
*** bharath has joined #openstack-meeting-alt05:55
*** yamamoto has quit IRC05:58
*** wojdev_ has joined #openstack-meeting-alt05:59
*** wojdev has quit IRC06:00
*** wojdev_ is now known as wojdev06:00
*** nadya has quit IRC06:02
*** yamamoto has joined #openstack-meeting-alt06:06
*** ashleighfarnham has joined #openstack-meeting-alt06:06
*** yamamoto has quit IRC06:09
*** yamamoto has joined #openstack-meeting-alt06:09
*** SridharG has joined #openstack-meeting-alt06:09
*** juggler has quit IRC06:10
*** ashleighfarnham has quit IRC06:11
*** Murali has joined #openstack-meeting-alt06:12
*** ganeshna has quit IRC06:15
*** oomichi has quit IRC06:16
*** numan has joined #openstack-meeting-alt06:18
*** wojdev has quit IRC06:20
*** salv-orlando has joined #openstack-meeting-alt06:21
*** coolsvap is now known as coolsvap|away06:22
*** ijw has quit IRC06:23
*** ijw has joined #openstack-meeting-alt06:23
*** wojdev has joined #openstack-meeting-alt06:23
*** jtomasek has joined #openstack-meeting-alt06:29
*** stevemar has quit IRC06:29
*** shashank_hegde has quit IRC06:34
*** nadya has joined #openstack-meeting-alt06:35
*** ganeshna has joined #openstack-meeting-alt06:36
*** ashtokolov_ has joined #openstack-meeting-alt06:36
*** ganeshna has quit IRC06:38
*** jprovazn has joined #openstack-meeting-alt06:40
*** ashtokolov_ has quit IRC06:41
*** rm_work is now known as rm_work|away06:42
*** markvoelker has joined #openstack-meeting-alt06:43
*** markvoelker has quit IRC06:48
*** shashank_hegde has joined #openstack-meeting-alt06:51
*** Murali_ has joined #openstack-meeting-alt06:51
*** Murali has quit IRC06:53
*** Murali_ is now known as Murali06:53
*** svinota has joined #openstack-meeting-alt06:54
*** vgridnev has joined #openstack-meeting-alt06:55
*** agireud has quit IRC06:56
*** Murali has quit IRC06:58
*** Murali_ has joined #openstack-meeting-alt06:58
*** Murali_ is now known as Murali06:58
*** ashleighfarnham has joined #openstack-meeting-alt07:00
*** wojdev has quit IRC07:01
*** amotoki has quit IRC07:01
*** armax has quit IRC07:04
*** fawadkhaliq has joined #openstack-meeting-alt07:05
*** ashleighfarnham has quit IRC07:05
*** Tango has joined #openstack-meeting-alt07:06
*** Sukhdev has quit IRC07:07
*** ijw has quit IRC07:07
*** ildikov has joined #openstack-meeting-alt07:07
*** ganeshna has joined #openstack-meeting-alt07:08
*** ijw has joined #openstack-meeting-alt07:08
*** u_glide has left #openstack-meeting-alt07:08
*** Tango|2 has quit IRC07:09
*** SridharG1 has joined #openstack-meeting-alt07:11
*** SridharG has quit IRC07:11
*** ijw has quit IRC07:11
*** ijw has joined #openstack-meeting-alt07:11
*** SridharG1 has left #openstack-meeting-alt07:13
*** ijw has quit IRC07:13
*** SridharG has joined #openstack-meeting-alt07:13
*** ijw has joined #openstack-meeting-alt07:13
*** rm_work|away is now known as rm_work07:14
*** vgridnev has quit IRC07:16
*** matrohon has joined #openstack-meeting-alt07:16
*** scheuran has joined #openstack-meeting-alt07:18
*** vahidh has quit IRC07:21
*** padkrish has quit IRC07:23
*** ganeshna has quit IRC07:23
*** ganeshna has joined #openstack-meeting-alt07:25
*** bharath has quit IRC07:30
*** stevemar has joined #openstack-meeting-alt07:30
*** j___ has joined #openstack-meeting-alt07:30
*** achanda has quit IRC07:33
*** bana_k has quit IRC07:33
*** ganeshna has quit IRC07:33
*** stevemar has quit IRC07:34
*** Tango has quit IRC07:36
*** ashleighfarnham has joined #openstack-meeting-alt07:41
*** amotoki has joined #openstack-meeting-alt07:42
*** padkrish has joined #openstack-meeting-alt07:44
*** ashleighfarnham has quit IRC07:46
*** dims has joined #openstack-meeting-alt07:48
*** sgotliv has joined #openstack-meeting-alt07:48
*** dims has quit IRC07:53
*** bradjones has quit IRC07:53
*** agarciam has joined #openstack-meeting-alt07:53
*** bradjones has joined #openstack-meeting-alt07:56
*** bradjones has quit IRC07:56
*** bradjones has joined #openstack-meeting-alt07:56
*** jcoufal has joined #openstack-meeting-alt07:56
*** fawadkhaliq has quit IRC08:01
*** fawadkhaliq has joined #openstack-meeting-alt08:01
*** saurabhs has quit IRC08:02
*** jeadr has quit IRC08:06
*** jeadr has joined #openstack-meeting-alt08:06
*** pnavarro has joined #openstack-meeting-alt08:08
*** derekh has joined #openstack-meeting-alt08:12
*** derekh has quit IRC08:12
*** derekh has joined #openstack-meeting-alt08:13
*** vgridnev has joined #openstack-meeting-alt08:13
*** padkrish has quit IRC08:14
*** padkrish has joined #openstack-meeting-alt08:15
*** scheuran has quit IRC08:15
*** ganeshna has joined #openstack-meeting-alt08:17
*** jeadr has quit IRC08:17
*** jeadr has joined #openstack-meeting-alt08:17
*** ganeshna has quit IRC08:18
*** scheuran has joined #openstack-meeting-alt08:19
*** shashank_hegde has quit IRC08:20
*** ganeshna has joined #openstack-meeting-alt08:21
*** padkrish has quit IRC08:23
*** ganeshna has quit IRC08:23
*** padkrish has joined #openstack-meeting-alt08:25
*** ganeshna has joined #openstack-meeting-alt08:29
*** padkrish has quit IRC08:29
*** bharath_ has joined #openstack-meeting-alt08:30
*** HeOS has quit IRC08:32
*** bharath_ has quit IRC08:35
*** ashleighfarnham has joined #openstack-meeting-alt08:35
*** jeadr has quit IRC08:39
*** jeadr has joined #openstack-meeting-alt08:40
*** ashleighfarnham has quit IRC08:40
*** zeih has joined #openstack-meeting-alt08:42
*** markvoelker has joined #openstack-meeting-alt08:45
*** tfukushima has joined #openstack-meeting-alt08:47
*** markvoelker has quit IRC08:50
*** yamahata has quit IRC08:51
*** kzaitsev_mb has joined #openstack-meeting-alt09:04
*** zhhuabj has quit IRC09:07
*** svinota has quit IRC09:09
*** HeOS has joined #openstack-meeting-alt09:19
*** zhhuabj has joined #openstack-meeting-alt09:20
*** toscalix has joined #openstack-meeting-alt09:27
*** fawadkhaliq has quit IRC09:30
*** stevemar has joined #openstack-meeting-alt09:31
*** dkusidlo has joined #openstack-meeting-alt09:33
*** stevemar has quit IRC09:35
*** jeadr has quit IRC09:44
*** jeadr has joined #openstack-meeting-alt09:44
*** tfukushima has quit IRC09:51
*** jrist has quit IRC09:54
*** tfukushima has joined #openstack-meeting-alt09:58
*** tfukushima has quit IRC09:58
*** tfukushima has joined #openstack-meeting-alt09:58
*** dkusidlo has quit IRC10:00
*** jprovazn has quit IRC10:01
*** zeih has quit IRC10:04
*** baojg has quit IRC10:06
*** baojg has joined #openstack-meeting-alt10:06
*** baojg has quit IRC10:07
*** baojg has joined #openstack-meeting-alt10:07
*** baojg has quit IRC10:07
*** baojg has joined #openstack-meeting-alt10:07
*** sdake has quit IRC10:15
*** baojg has quit IRC10:17
*** baojg has joined #openstack-meeting-alt10:18
*** bharath_ has joined #openstack-meeting-alt10:20
*** numan has quit IRC10:21
*** baojg has quit IRC10:23
*** jprovazn has joined #openstack-meeting-alt10:23
*** bharath_ has quit IRC10:24
*** dkusidlo has joined #openstack-meeting-alt10:25
*** ashleighfarnham has joined #openstack-meeting-alt10:25
*** svinota has joined #openstack-meeting-alt10:29
*** ashleighfarnham has quit IRC10:29
*** numan has joined #openstack-meeting-alt10:35
*** ashtokolov_ has joined #openstack-meeting-alt10:36
*** zhhuabj has quit IRC10:36
*** numan has quit IRC10:41
*** markvoelker has joined #openstack-meeting-alt10:46
*** toscalix has quit IRC10:49
*** markvoelker has quit IRC10:50
*** dims has joined #openstack-meeting-alt10:51
*** numan has joined #openstack-meeting-alt10:54
*** zhhuabj has joined #openstack-meeting-alt10:54
*** ashtokolov_ has quit IRC10:56
*** salv-orlando has quit IRC10:57
*** sc68cal has quit IRC11:02
*** ashtokolov_ has joined #openstack-meeting-alt11:05
*** sc68cal has joined #openstack-meeting-alt11:06
*** sc68cal has quit IRC11:06
*** sc68cal has joined #openstack-meeting-alt11:06
*** sc68cal has quit IRC11:07
*** tfukushima has quit IRC11:10
*** delattec has quit IRC11:10
*** dane_leblanc has joined #openstack-meeting-alt11:10
*** yamamoto has quit IRC11:13
*** tfukushima has joined #openstack-meeting-alt11:15
*** sc68cal has joined #openstack-meeting-alt11:16
*** sc68cal has quit IRC11:16
*** sc68cal has joined #openstack-meeting-alt11:16
*** toscalix has joined #openstack-meeting-alt11:16
*** baoli has joined #openstack-meeting-alt11:17
*** ganeshna has quit IRC11:19
*** ashleighfarnham has joined #openstack-meeting-alt11:19
*** salv-orlando has joined #openstack-meeting-alt11:19
*** esker has joined #openstack-meeting-alt11:20
*** toscalix has quit IRC11:21
*** baoli has quit IRC11:21
*** tfukushima has quit IRC11:22
*** dkusidlo has quit IRC11:23
*** ashleighfarnham has quit IRC11:24
*** zz_dimtruck is now known as dimtruck11:26
*** marcusvrn has joined #openstack-meeting-alt11:27
*** dims_ has joined #openstack-meeting-alt11:28
*** warpc__ has joined #openstack-meeting-alt11:29
*** toscalix has joined #openstack-meeting-alt11:30
*** dims has quit IRC11:30
*** stevemar has joined #openstack-meeting-alt11:32
*** cdelatte has joined #openstack-meeting-alt11:32
*** dkusidlo has joined #openstack-meeting-alt11:33
*** jprovazn has quit IRC11:34
*** stevemar has quit IRC11:35
*** fawadkhaliq has joined #openstack-meeting-alt11:37
*** jprovazn has joined #openstack-meeting-alt11:37
*** DuncanT has quit IRC11:38
*** marcusvrn has quit IRC11:38
*** bogdando has quit IRC11:38
*** dlenrow has quit IRC11:38
*** tchaypo has quit IRC11:39
*** jprovazn has quit IRC11:39
*** bogdando has joined #openstack-meeting-alt11:40
*** ramishra has quit IRC11:40
*** dkusidlo has quit IRC11:44
*** dane_leblanc has quit IRC11:45
*** markvoelker has joined #openstack-meeting-alt11:46
*** fawadk has joined #openstack-meeting-alt11:46
*** yamamoto has joined #openstack-meeting-alt11:47
*** yamamoto has quit IRC11:47
*** yamamoto has joined #openstack-meeting-alt11:47
*** fawadkhaliq has quit IRC11:47
*** yamamoto_ has joined #openstack-meeting-alt11:48
*** esker has quit IRC11:50
*** dane_leblanc has joined #openstack-meeting-alt11:51
*** dimtruck is now known as zz_dimtruck11:51
*** esker has joined #openstack-meeting-alt11:51
*** markvoelker has quit IRC11:51
*** zz_dimtruck is now known as dimtruck11:51
*** yamamoto has quit IRC11:52
*** amotoki has quit IRC11:53
*** fawadk has quit IRC11:55
*** ftersin has joined #openstack-meeting-alt11:55
*** fungi has quit IRC11:57
*** fungi has joined #openstack-meeting-alt11:59
*** dims has joined #openstack-meeting-alt12:00
*** ashtokolov_ has quit IRC12:00
*** dims has quit IRC12:00
*** dims_ has quit IRC12:00
*** dims has joined #openstack-meeting-alt12:01
*** esker has quit IRC12:01
*** dprince has joined #openstack-meeting-alt12:04
*** dkusidlo has joined #openstack-meeting-alt12:05
*** dims has quit IRC12:05
*** dkusidlo has quit IRC12:05
*** kei_yama has quit IRC12:05
*** dprince has quit IRC12:07
*** dprince has joined #openstack-meeting-alt12:07
*** bharath_ has joined #openstack-meeting-alt12:08
*** markvoelker has joined #openstack-meeting-alt12:12
*** banix has joined #openstack-meeting-alt12:13
*** bharath_ has quit IRC12:13
*** pnavarro is now known as pnavarro|lunch12:14
*** skath has quit IRC12:14
*** toscalix has quit IRC12:15
*** zeih has joined #openstack-meeting-alt12:15
*** dims has joined #openstack-meeting-alt12:15
*** skath has joined #openstack-meeting-alt12:16
*** jeadr has quit IRC12:17
*** jeadr has joined #openstack-meeting-alt12:17
*** salv-orlando has quit IRC12:18
*** bswartz has quit IRC12:20
*** tfukushima has joined #openstack-meeting-alt12:22
*** dave-mccowan has joined #openstack-meeting-alt12:23
*** annegentle has joined #openstack-meeting-alt12:24
*** jprovazn has joined #openstack-meeting-alt12:25
*** tfukushima has quit IRC12:26
*** yamamoto_ has quit IRC12:29
*** banix has quit IRC12:30
*** SridharG has left #openstack-meeting-alt12:31
*** nkrinner has quit IRC12:32
*** marcusvrn has joined #openstack-meeting-alt12:38
*** sgotliv_ has joined #openstack-meeting-alt12:38
*** agarciam1 has joined #openstack-meeting-alt12:39
*** agarciam has quit IRC12:40
*** sgotliv has quit IRC12:40
*** dims_ has joined #openstack-meeting-alt12:41
*** dims has quit IRC12:41
*** dlenrow has joined #openstack-meeting-alt12:43
*** agarciam has joined #openstack-meeting-alt12:43
*** tfukushima has joined #openstack-meeting-alt12:44
*** agarciam1 has quit IRC12:44
*** ashtokolov_ has joined #openstack-meeting-alt12:44
*** yamamoto has joined #openstack-meeting-alt12:45
*** yamamoto has quit IRC12:45
*** yamamoto has joined #openstack-meeting-alt12:46
*** dlenrow has quit IRC12:47
*** baoli has joined #openstack-meeting-alt12:48
*** yamamoto has quit IRC12:49
*** marcusvrn has quit IRC12:49
*** baoli has quit IRC12:52
*** dane_leblanc_ has joined #openstack-meeting-alt12:58
*** dane_leblanc has quit IRC12:59
*** dims has joined #openstack-meeting-alt13:01
*** dims_ has quit IRC13:02
*** bswartz has joined #openstack-meeting-alt13:02
*** amrith is now known as _amrith_13:04
*** VW_ has joined #openstack-meeting-alt13:04
*** toscalix has joined #openstack-meeting-alt13:04
*** yamamoto has joined #openstack-meeting-alt13:04
*** yamamoto has quit IRC13:08
*** VW_ has quit IRC13:11
*** VW_ has joined #openstack-meeting-alt13:11
*** yamamoto has joined #openstack-meeting-alt13:12
*** yamamoto has quit IRC13:12
*** dims_ has joined #openstack-meeting-alt13:15
*** VW_ has quit IRC13:15
*** VW_ has joined #openstack-meeting-alt13:16
*** dims has quit IRC13:17
*** jckasper has quit IRC13:17
*** persia_ is now known as persia13:19
*** xyang1 has joined #openstack-meeting-alt13:21
*** jian5397 has joined #openstack-meeting-alt13:24
*** julim has joined #openstack-meeting-alt13:24
*** toscalix has quit IRC13:28
*** dims_ has quit IRC13:31
*** dims has joined #openstack-meeting-alt13:31
*** yamamoto has joined #openstack-meeting-alt13:31
*** singlethink has joined #openstack-meeting-alt13:32
*** ftersin has quit IRC13:33
*** sankarshan is now known as sankarshan_away13:33
*** amitgandhinz has joined #openstack-meeting-alt13:35
*** shwetaap has joined #openstack-meeting-alt13:36
*** dims has quit IRC13:40
*** dimtruck is now known as zz_dimtruck13:41
*** VW_ has quit IRC13:42
*** jungleboyj has quit IRC13:42
*** VW_ has joined #openstack-meeting-alt13:43
*** dims has joined #openstack-meeting-alt13:43
*** zz_dimtruck is now known as dimtruck13:44
*** yuanying-alt has joined #openstack-meeting-alt13:45
*** jeadr has quit IRC13:45
*** jeadr has joined #openstack-meeting-alt13:45
*** balajiiyer has joined #openstack-meeting-alt13:49
*** marcusvrn_ has joined #openstack-meeting-alt13:52
*** bharath has joined #openstack-meeting-alt13:54
*** dlenrow has joined #openstack-meeting-alt13:55
*** dizquierdo has joined #openstack-meeting-alt13:55
*** priti has joined #openstack-meeting-alt13:57
*** singleth_ has joined #openstack-meeting-alt13:59
*** priti has quit IRC14:00
*** armax has joined #openstack-meeting-alt14:00
*** singlethink has quit IRC14:01
*** tchaypo has joined #openstack-meeting-alt14:02
*** jvrbanac has quit IRC14:02
*** ramishra has joined #openstack-meeting-alt14:02
*** dimtruck is now known as zz_dimtruck14:02
*** zeih has quit IRC14:02
*** DuncanT has joined #openstack-meeting-alt14:03
*** dims has quit IRC14:04
*** otherwiseguy has quit IRC14:04
*** dims has joined #openstack-meeting-alt14:05
*** yuanying-alt has quit IRC14:05
*** Murali has quit IRC14:06
*** nadya has quit IRC14:07
*** jvrbanac has joined #openstack-meeting-alt14:09
*** jckasper has joined #openstack-meeting-alt14:09
*** carl_baldwin has joined #openstack-meeting-alt14:10
*** jecarey has joined #openstack-meeting-alt14:11
*** banix has joined #openstack-meeting-alt14:11
*** sigmavirus24_awa is now known as sigmavirus2414:11
*** phil_h has joined #openstack-meeting-alt14:12
*** esker has joined #openstack-meeting-alt14:12
*** pnavarro|lunch is now known as pnavarro14:14
*** IlyaG has joined #openstack-meeting-alt14:14
*** kfarr has joined #openstack-meeting-alt14:14
*** ashleighfarnham has joined #openstack-meeting-alt14:15
*** zeih has joined #openstack-meeting-alt14:16
*** otherwiseguy has joined #openstack-meeting-alt14:16
*** _amrith_ is now known as amrith14:16
*** jungleboyj has joined #openstack-meeting-alt14:17
*** ashleighfarnham has quit IRC14:20
*** annegentle has quit IRC14:20
*** jmckind has joined #openstack-meeting-alt14:21
*** FallenPegasus has joined #openstack-meeting-alt14:23
*** agireud has joined #openstack-meeting-alt14:26
*** [HeOS] has joined #openstack-meeting-alt14:26
*** HeOS has quit IRC14:26
*** jeadr has quit IRC14:27
*** jeadr has joined #openstack-meeting-alt14:27
*** salv-orlando has joined #openstack-meeting-alt14:30
*** [HeOS] has quit IRC14:31
*** tonytan4ever has joined #openstack-meeting-alt14:31
*** zz_dimtruck is now known as dimtruck14:31
*** amrith is now known as _amrith_14:31
*** sdake has joined #openstack-meeting-alt14:31
*** stevemar has joined #openstack-meeting-alt14:32
*** _amrith_ is now known as amrith14:32
*** carl_baldwin has quit IRC14:32
*** kzaitsev_mb has quit IRC14:33
*** pnavarro has quit IRC14:34
*** numan has quit IRC14:34
*** salv-orlando has quit IRC14:34
*** jmckind has quit IRC14:34
*** phil_h has quit IRC14:35
*** dims_ has joined #openstack-meeting-alt14:35
*** spzala has joined #openstack-meeting-alt14:36
*** dims has quit IRC14:37
*** zeih has quit IRC14:37
*** sdake_ has joined #openstack-meeting-alt14:37
*** jrist has joined #openstack-meeting-alt14:38
*** jrist has quit IRC14:38
*** jrist has joined #openstack-meeting-alt14:38
*** stevemar has quit IRC14:39
*** stevemar has joined #openstack-meeting-alt14:39
*** sdake has quit IRC14:40
*** agireud has quit IRC14:40
*** snackewm has quit IRC14:41
*** spzala has quit IRC14:42
*** jjlehr has joined #openstack-meeting-alt14:43
*** Tango has joined #openstack-meeting-alt14:44
*** annegentle has joined #openstack-meeting-alt14:44
*** harshs has joined #openstack-meeting-alt14:49
*** kzaitsev_mb has joined #openstack-meeting-alt14:50
*** jeadr has quit IRC14:50
*** jeadr has joined #openstack-meeting-alt14:50
*** julim_ has joined #openstack-meeting-alt14:51
*** zimboboy- has joined #openstack-meeting-alt14:53
*** priti has joined #openstack-meeting-alt14:54
*** mtanino has joined #openstack-meeting-alt14:55
*** Kiall_ has joined #openstack-meeting-alt14:57
*** bswartz has quit IRC14:57
*** pmalik_ has joined #openstack-meeting-alt14:58
*** Ramanjaneya has joined #openstack-meeting-alt14:58
*** DandyPandy_ has joined #openstack-meeting-alt14:59
*** agireud has joined #openstack-meeting-alt14:59
*** stevemar has quit IRC14:59
*** tonytan4ever has quit IRC14:59
*** julim has quit IRC14:59
*** dprince has quit IRC14:59
*** zhhuabj has quit IRC14:59
*** elo has quit IRC14:59
*** jaredrohe has quit IRC14:59
*** pmalik has quit IRC14:59
*** Kiall has quit IRC14:59
*** bogdando has quit IRC14:59
*** jtomasek has quit IRC14:59
*** sreshetnyak has quit IRC14:59
*** rharwood has quit IRC14:59
*** a_teem has quit IRC14:59
*** early has quit IRC14:59
*** myatsenko has quit IRC14:59
*** cody-somerville- has quit IRC14:59
*** wznoinsk has quit IRC14:59
*** DandyPandy has quit IRC14:59
*** zimboboyd has quit IRC14:59
*** zimboboy- is now known as zimboboyd14:59
*** bogdando has joined #openstack-meeting-alt15:00
matrohonhi15:00
*** pc_m has joined #openstack-meeting-alt15:00
matrohonanyone interested in the bgpvpn meeting?15:01
* pc_m lurking15:01
*** a_teem has joined #openstack-meeting-alt15:01
matrohonpc_m : please do :)15:01
*** dims has joined #openstack-meeting-alt15:01
*** yamahata has joined #openstack-meeting-alt15:02
pcarverI'm around, but was on vacation yesterday so I know I'm behind on some emails that were sent15:02
*** achanda has joined #openstack-meeting-alt15:03
matrohonpcarver : hi15:03
*** dims_ has quit IRC15:03
*** julim has joined #openstack-meeting-alt15:04
*** smccully has joined #openstack-meeting-alt15:04
*** janscheurich has joined #openstack-meeting-alt15:05
*** achanda has quit IRC15:05
*** sreshetnyak has joined #openstack-meeting-alt15:05
*** priti_ has joined #openstack-meeting-alt15:05
matrohonAs there are some important design choices that has to be made, I'd like that most of the main contributor of bgpvpn discuss about them15:05
*** stevemar has joined #openstack-meeting-alt15:05
*** early has joined #openstack-meeting-alt15:06
janscheurichmatrohon: hi15:06
*** julim_ has quit IRC15:06
matrohonjanscheurich :hi15:06
matrohon#startmeeting bgpvpn15:07
openstackMeeting started Tue Aug 18 15:07:41 2015 UTC and is due to finish in 60 minutes.  The chair is matrohon. Information about MeetBot at http://wiki.debian.org/MeetBot.15:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:07
*** openstack changes topic to " (Meeting topic: bgpvpn)"15:07
openstackThe meeting name has been set to 'bgpvpn'15:07
*** snackewm has joined #openstack-meeting-alt15:08
*** amotoki has joined #openstack-meeting-alt15:08
matrohonwe have few design topics today, that I'd like to discuss15:08
*** priti has quit IRC15:08
matrohontopic : service plugins vs service providers15:08
matrohon#topic : service plugins vs service providers15:08
*** openstack changes topic to ": service plugins vs service providers (Meeting topic: bgpvpn)"15:08
matrohonas mentioned in https://bugs.launchpad.net/bgpvpn/+bug/1485515, I considered moving back from the service provider framework to the service plugin framework15:10
openstackLaunchpad bug 1485515 in bgpvpn "multiple service drivers can't coexist" [Undecided,New]15:10
svinotaoh. Almost missed15:10
*** ashleighfarnham has joined #openstack-meeting-alt15:10
matrohonsvinota : hi15:10
svinotamatrohon, hi15:10
matrohonthis would mean that each backend would implement its own plugin and the extension it supports15:10
pcarvermatrohon: I saw that you sent an email on that bug, but haven't read it yet15:11
*** zhhuabj has joined #openstack-meeting-alt15:11
*** Ramanjaneya has quit IRC15:11
matrohonActually, I'm not sure if mixing service provider for the bgpvpn plugin make sense, and answers any use case15:11
*** tonytan4ever has joined #openstack-meeting-alt15:12
*** dprince has joined #openstack-meeting-alt15:12
*** jaredrohe has joined #openstack-meeting-alt15:12
*** cameron.freenode.net changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:12
*** jtomasek has joined #openstack-meeting-alt15:12
*** rharwood has joined #openstack-meeting-alt15:12
*** myatsenko has joined #openstack-meeting-alt15:12
*** cody-somerville- has joined #openstack-meeting-alt15:12
*** wznoinsk has joined #openstack-meeting-alt15:12
*** amrith is now known as _amrith_15:12
amotokihi, I am not an usual member of this meeting though.15:12
amotokifor service provider, I have two questions.15:13
janscheurichWhat would be the consequences for API users: Can they discover extension support?15:13
pcarverOk, skimmed through it quickly and first impression is that this relates to some of the ML3 discussion we had a while back15:13
matrohonI discussed with pc_m and dougwig earlier and dougwig encourage us to keep using the service provider framework since horizon is aware of the framework15:13
amotokire horizon impl, it is service by service, so it is not a big matter.15:14
matrohonjanscheurich : there would be no consequences, API would be the same, be the cloud provider couldn't mix several backends15:14
*** elo has joined #openstack-meeting-alt15:14
matrohonamotoki : ok thanks for the clarification15:14
*** ashleighfarnham has quit IRC15:14
*** kfarr has quit IRC15:14
matrohonamotoki : I saw that the flavor framework has merged in neutron recently15:15
matrohonamotoki : is there a related work in progress in horizon?15:15
pcarverIn principle we dislike the idea of having an entire cloud locked in to a single vendor, but in practice it seems very difficult to picture exactly how multiple L3 service providers could coexist. Defining the boundaries is the challenge.15:15
amotokimatrohon: yes. it can be consumed by various services15:15
matrohonpcarver : +115:15
pcarverIn the ML3 discussion we talked about leveraging the flavor framework to essentially have "flavors of routers"15:16
*** dprince has quit IRC15:16
matrohonamotoki : do you have any links?15:16
amotokimarcusvrn_: link about what?15:16
matrohonamotoki : about horizon implementation for the flavor framework?15:17
*** jjlehr has quit IRC15:17
*** bswartz has joined #openstack-meeting-alt15:17
amotokiah.. got it. regaring horizon implementation, it will be service by service.15:17
pcarverI can certainly imagine wanting to have freedom to implement some L3 on Cisco Nexus and other L3 on Juniper MX (perhaps with a shared VXLAN L2 interconnecting them)15:17
pcarverBut it's more challenging to imagine a scenario with some L3 on Contrail and other L3 on ODL15:18
*** woodster_ has joined #openstack-meeting-alt15:18
*** padkrish has joined #openstack-meeting-alt15:18
matrohonpcarver : and others on Nuage, exactly...15:18
amotokihorizon panel for each service will just have a "flavor " instead of "provider" in LBaaS v1 now. there is no progress AFAIK15:18
amotokiso it means we can just discuss flavor framework support only from API perspective.15:19
pcarvermatrohon: Right, just listing some names for concreteness but not limiting discussion to those examples15:19
*** tsekiyama has joined #openstack-meeting-alt15:19
amotokipcarver: if some setvice plugin cannot coexist with other plugin/driver, they can choose a service plugin rather than a driver.15:20
matrohonamotoki : ok I see. the admin can't match service provider to service plugin through horizon?15:20
matrohonamotoki : ok I see. the admin can't match service provider to service flavors through horizon?15:20
*** j___ has quit IRC15:20
amotokimatrohon: what I am talking is just about user API15:21
matrohonamotoki : that's exactly the state of my thoughs currently15:21
amotokiwe can have more GUI for admin to map privider to flavor.15:21
matrohonamotoki : but it's not implemented currently?15:22
amotokimatrohon: we have no impl now15:22
matrohonamotoki : ok thanks15:22
*** ajmiller_ has quit IRC15:22
*** singleth_ has quit IRC15:23
matrohonso i'm not sure we could conclude about service plugin vs service providers...15:24
*** jeadr has quit IRC15:24
*** jeadr has joined #openstack-meeting-alt15:24
amotokiregarding VPNaas and service provider, i have a question: VPNaaS APi is different per VPN type (e.g., IPsec/ BGPVPN), so I wonder we should have service provider per VPN type, or per VPN as a whole.15:24
matrohonI lean toward the service plugin implementation for its simplicity15:24
*** noslzzp has joined #openstack-meeting-alt15:25
amotokiIMHO we can have service provider for IPsec VPN, but I wonder how we can achieve service provider for a whole VPNaaS.15:25
janscheurichBut will a service plugin approach make it harder for BGPVPN to become part of core Neutron at some point?15:26
*** snackewm has quit IRC15:26
*** puranamr has joined #openstack-meeting-alt15:26
pc_mamotoki: good question15:26
matrohonamotoki : we could have a plugin taht implement both IPSec plugin interface and bgpvpn plugin interface15:27
matrohonamotoki, pc_m : and that supports both extensions15:27
pc_mI've been trying to define API for the "what" gets connected, with a separate (existing)API (for IPSec) for the how to connect.15:27
amotokimatrohon: that is one choice. another choice is to have a dedicate plugin per VPN type.15:28
*** ganeshna has joined #openstack-meeting-alt15:28
*** dims has quit IRC15:29
matrohonamotoki, pc_m : we currently have two service type, but what I mean is that the service driver could be the same and implement both interfaces15:29
pc_mmatrohon: driver or plugin?15:29
*** maurosr has quit IRC15:29
*** singlethink has joined #openstack-meeting-alt15:30
*** snackewm has joined #openstack-meeting-alt15:30
*** dims has joined #openstack-meeting-alt15:30
*** pnavarro has joined #openstack-meeting-alt15:30
* pc_m wondering if we are all using the same terminology15:30
*** ganeshna has quit IRC15:30
amotokiat now the only interaction point is "vpnservice". I am not sure we should stick one service plugin.15:30
matrohonpc_m : it depends on our decision, but it could be a plugin for the bgpvpn service type and a driver for ipsec service type15:30
amotokiI think service plugins for ipsec and bgpvpn can coexist. I am just talking about possibilities.15:31
*** VW_ has quit IRC15:31
*** ganeshna has joined #openstack-meeting-alt15:31
*** VW_ has joined #openstack-meeting-alt15:31
amotokiI think we can list bgpvpn service plugin and ipsec service plugin.15:32
matrohonlet's take the bagpipe implementation : it could coexist with a router that run strongswan for instance15:32
-amotoki- needs power for mac book15:32
pc_mamotoki: is the plugin tied to a specific API (extension)?15:32
amotokipc_m: yes, though it is one choice.15:33
*** salv-orlando has joined #openstack-meeting-alt15:33
pc_mamotoki: What's the other choice15:33
amotokiin the past discussion, VPN parameters depends on a type much.15:33
* pc_m trying to find out how they interrelate15:33
amotokiso I am afraid we can have a single service plugin or not.15:33
*** vgridnev has quit IRC15:34
amotokithe other choice is one service plugin for all (or two now) VPN types.15:34
pc_mamotoki: In that case, some APIs dispatch to one service driver and other APIs to the other service driver?15:35
*** pballand has joined #openstack-meeting-alt15:35
*** VW_ has quit IRC15:35
*** pnavarro has quit IRC15:36
pc_mwith a combined plugin, there isn't a way to enable only one type, right?15:36
amotokipc_m: is "that case" "one service plugin ..."?15:36
*** pnavarro has joined #openstack-meeting-alt15:36
pc_mamotoki: yes15:36
*** woodster_ has quit IRC15:36
*** ramishra has quit IRC15:36
*** DuncanT has quit IRC15:36
*** tchaypo has quit IRC15:36
*** marcusvrn_ has quit IRC15:36
*** dlenrow has quit IRC15:36
*** maurosr has joined #openstack-meeting-alt15:36
amotokihonestly I don't have a good picture on a single plugin for all vpn types.15:36
matrohonthis could be achivable by loading extension from service drivers15:37
pc_mmatrohon: It may be useful to create a write-up on the various options, the implications, and maybe a recommendation...for community review.15:37
matrohonpc_m : make sense...15:38
matrohonthis leads me to the other topic I'd like to discuss ... :)15:38
amotokimatrohon: does it mean that supported extensions are determiend by loaded drivers?15:38
pc_mI imagine some of us (like me), don't have a strong handle on how BGPVPN works either.15:38
*** ganeshna_ has joined #openstack-meeting-alt15:39
pcarverI wonder if we need a flow chart showing decision points.15:39
pcarverI'm a little unclear on what decisions would be made via API vs config vs within the code15:39
matrohonamotoki : If we keep on using a single plugin, having extensions loaded by service drivers make sens since some option won't be supported by some backends15:39
pcarverAs an API request comes in it needs to flow through plugin/driver/extension in some deterministic way15:40
*** jeadr has quit IRC15:40
*** jeadr has joined #openstack-meeting-alt15:40
matrohonI submitted this kind of idea on the last review : https://review.openstack.org/#/c/177740/15:40
*** ganeshna has quit IRC15:40
matrohonamotoki : we would mimic the ML2 extension manager15:41
amotokimatrohon: I see.15:41
matrohonI would like to move the "what" can be associated to a vpn in dedicated extensions15:42
amotokibut I am not sure it speeds up us. integration tends to take time and there are big differences across VPN services15:43
amotokiso I am not confident a single plugin is a better choice at now.15:43
*** rm_work is now known as rm_work|away15:43
*** padkrish has quit IRC15:43
*** jecarey has quit IRC15:43
amotokimatrohon: agree to moving "what"15:43
amotokimoving to "what"15:44
janscheurichI think we are discussing different things. I believe matrohon is talking about what to associate with a BGPVPN object: network, router, etc15:44
*** dims has quit IRC15:45
*** Aish has joined #openstack-meeting-alt15:45
matrohonamotoki either I hope :)15:45
*** ganeshna_ has quit IRC15:45
amotokijanscheurich: matrohon: it is same as what in my mind.15:45
*** spzala has joined #openstack-meeting-alt15:46
amotokimatrohon: go ahead, please15:46
matrohonpc_m : don't you think this model could be used in the context of https://review.openstack.org/#/c/191944/15:46
*** ganeshna has joined #openstack-meeting-alt15:46
*** geoffarnold has joined #openstack-meeting-alt15:46
pc_mI've been trying to design something to detail the "what" with https://review.openstack.org/#/c/191944/15:46
* pc_m messages crossed.15:46
*** dims has joined #openstack-meeting-alt15:47
pc_mmatrohon: I'm still struggling with understanding how BGPVPN works.15:47
matrohonpc_m :)15:48
*** madhuri has joined #openstack-meeting-alt15:48
pc_mmatrohon: For IPSec we need to support multiple local subnets. Rather than just adding it to the existing API, I wanted to separate out the "what gets connected"15:48
matrohonpc_m : just think about a third party VPN with end users able to attach resources to it15:48
pc_min the hopes it can be reused.15:48
matrohonpc_m : in the IPSec context it's always subnet15:49
pc_mmatrohon: That helps.15:50
matrohonwhile in bgpvpn we might want to attach network, router or even ports, depending on the backend15:50
*** geoffarnold has quit IRC15:50
janscheurichmatrohon: Depending on the networking use case15:50
*** geoffarnold has joined #openstack-meeting-alt15:50
matrohonjanscheurich : +115:51
janscheurichNot all BGPVPN backends may support all types of attachment15:51
pc_mmatrohon: So does a backend, like bagpipe manage the resource that gets connected to the BGPVPN?15:51
*** ashleighfarnham has joined #openstack-meeting-alt15:51
matrohonthat's the reason why I think that we should leverage the extension framework to be able to scan what the backend support for attachment15:52
*** carl_baldwin has joined #openstack-meeting-alt15:52
*** ganeshna has quit IRC15:52
matrohonpc_m : it manages the resource by adding learned router to the router namespace in the router attachment example15:53
*** ganeshna has joined #openstack-meeting-alt15:53
janscheurichpc_m: I wouldn't say it manages the attached resources. It provides VPN connectivity between the attached local resources and the remote resources (in the BGPVPN case dynamically learned)15:53
matrohonjanscheurich : +115:54
*** mestery has joined #openstack-meeting-alt15:54
*** ijw has quit IRC15:55
*** fnaval has joined #openstack-meeting-alt15:55
*** ijw has joined #openstack-meeting-alt15:55
pc_mthanks. helping me understand it better15:55
matrohondoes anyone think that it's a bad idea to move the *-association to dedicated extension15:55
*** nadya has joined #openstack-meeting-alt15:55
*** adrian_otto has joined #openstack-meeting-alt15:56
amotokimatrohon: could you elaborate more?15:56
*** Ramanjaneya has joined #openstack-meeting-alt15:56
*** ashleighfarnham has quit IRC15:56
*** ijw has quit IRC15:56
janscheurichmatrohon: It may make the API documentation more difficult to read if it is split into too many extensions.15:56
*** ijw has joined #openstack-meeting-alt15:57
matrohonamotoki : I mean some backends (bgpvpn drivers or plugins) will support the bgpvpn extension a,d the network-association extension15:57
matrohonamotoki : while others will support the bgpvpn extension a,d the router-association extension15:57
*** hongbin has joined #openstack-meeting-alt15:57
amotokimatrohon: ah.. I got it to some extent.15:57
janscheurichOne big problem with Neutron API already today. Difficult to get the big picture15:57
matrohonamotoki : which means that the end user can only attach routers15:57
*** mfalatic has joined #openstack-meeting-alt15:58
*** marcusvrn_ has joined #openstack-meeting-alt15:58
*** ajmiller has joined #openstack-meeting-alt15:58
matrohoni think we gain in flexibility15:59
matrohonbut...15:59
*** rbradfor has joined #openstack-meeting-alt15:59
matrohonneutron is not able to manage action extensions today15:59
*** rpothier has joined #openstack-meeting-alt15:59
matrohonas actions described in the spec (associate-network...)15:59
amotokihmm... I think i understand the context, but there are many contexts. it seems better to me to start bgpvpn service plugin and then discuss an integrated vpn plugin.15:59
amotokiit is just my feeling from this meeting.16:00
matrohonamotoki : yep, ping me if needed16:00
*** daneyon_ has joined #openstack-meeting-alt16:00
matrohonso neutron is only able to manage resources extension16:00
*** lsmola has quit IRC16:00
*** eghobo_ has joined #openstack-meeting-alt16:01
matrohonwhich means taht we should get back to the sub-resources proposal in the spec, instead of action proposal...16:01
*** pc_m has left #openstack-meeting-alt16:01
adrian_ottotime to wrap up?16:01
-amotoki- time check16:01
matrohonlet's have one week to think about that16:01
matrohonthanks16:01
matrohon#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Tue Aug 18 16:01:46 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/bgpvpn/2015/bgpvpn.2015-08-18-15.07.html16:01
*** balajiiyer has quit IRC16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/bgpvpn/2015/bgpvpn.2015-08-18-15.07.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/bgpvpn/2015/bgpvpn.2015-08-18-15.07.log.html16:01
adrian_otto#startmeeting containers16:01
openstackMeeting started Tue Aug 18 16:01:56 2015 UTC and is due to finish in 60 minutes.  The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: containers)"16:01
openstackThe meeting name has been set to 'containers'16:02
adrian_otto#link https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2015-08-18_1600_UTC Our Agneda16:02
*** apmelton has joined #openstack-meeting-alt16:02
adrian_otto#topic Roll Call16:02
*** openstack changes topic to "Roll Call (Meeting topic: containers)"16:02
apmeltono/16:02
daneyon_o/16:02
adrian_ottoAdrian Otto16:02
mfalatico/16:02
*** kzaitsev_mb has quit IRC16:02
TangoTon Ngo16:02
madhurio/16:02
tcammann\o_16:02
rbradforRonald Bradford16:02
eghobo_o/16:02
adrian_ottohello apmelton, daneyon_, mfalatic, Tango, madhuri, tcammann, rbradfor, and eghobo_16:02
dane_leblanc_o/16:03
hongbino/16:03
*** mfalatic_ has joined #openstack-meeting-alt16:03
*** woodster_ has joined #openstack-meeting-alt16:03
adrian_ottohello dane_leblanc_, and hongbin16:04
bradjoneso/16:04
*** bswartz has quit IRC16:04
adrian_ottohi bradjones16:04
*** jecarey has joined #openstack-meeting-alt16:04
sdake_o/16:04
*** dlenrow has joined #openstack-meeting-alt16:04
*** diga has joined #openstack-meeting-alt16:04
*** tktk8924 has joined #openstack-meeting-alt16:04
digao/16:05
*** janscheurich has left #openstack-meeting-alt16:05
adrian_ottohello sdake and diga16:05
adrian_ottolet's begin16:05
adrian_otto#topic Announcements16:06
*** openstack changes topic to "Announcements (Meeting topic: containers)"16:06
adrian_otto1) adrian_otto will be out on 2015-08-25 due to travel to OpenStack Silicon Valley event. sdake will chair.16:06
*** bswartz has joined #openstack-meeting-alt16:06
adrian_ottoany other announcements form team members?16:06
adrian_otto*from?16:06
*** mfalatic has quit IRC16:07
adrian_otto#topic Container Networking Subteam Update (daneyon_)16:07
*** openstack changes topic to "Container Networking Subteam Update (daneyon_) (Meeting topic: containers)"16:07
daneyon_Last week's network subteam meeting had a ton of discussion around kuryr. What it is, what it's not, etc..16:07
daneyon_Unfortunately, we did not have anyone from the kuryr team in attendance. I received confirmation that someone from the kuryr team will join this week's meeting.16:07
*** mfalatic_ is now known as mfalatic16:07
daneyon_I attended the kuryr weekly meeting yesterday.16:07
*** vahidh has joined #openstack-meeting-alt16:07
daneyon_topics included config mgt and the details of vif binding/unbinding16:08
adrian_otto#link http://eavesdrop.openstack.org/meetings/container_networking/2015/container_networking.2015-08-13-18.00.html Previous Meeting16:08
daneyon_and a WIP kuryr design spec16:08
daneyon_If you have time, please review the spec16:08
adrian_ottolink to the spec?16:08
daneyon_#link https://review.openstack.org/#/c/213490/16:08
adrian_ottothanks daneyon_16:08
daneyon_Speaking of specs....16:09
daneyon_It would be great to wrap up the magnum network spec16:09
daneyon_Please let me know if you have any questions on my magnum net spec.16:09
daneyon_I have my magnum dev env up and going16:09
daneyon_I ran into a coupole bugs related to flannel16:10
sdake_the network spec danyeon_16:10
daneyon_i tracked the bugs and committed fixes16:10
sdake_was tom's issue sorted out16:10
daneyon_thanks everyone for getting them merged16:10
*** rmoe has joined #openstack-meeting-alt16:10
sdake_I am +2 on teh spec with whatever changefs are needed to get it through the system16:10
daneyon_when the magnum net spec is merged, i will create bp's for the individual tasks16:10
daneyon_in the meantime, I'm starting to hack at some of the changes proposed in the spec.16:10
daneyon_sdake_ yes, tcammann is happy and +2'd the revised spec16:11
sdake_adrain_otto one thing that I afound helped with rollcall votes16:11
*** tchaypo has joined #openstack-meeting-alt16:11
sdake_is to set a final deadline for approval16:11
sdake_daneyon_ nice ill go vote on it again then and re-reiew16:11
daneyon_i think adrian_otto would like to do one last review16:11
*** matrohon has quit IRC16:11
*** ramishra has joined #openstack-meeting-alt16:12
daneyon_hopefully he is happy with the spec and it gets merged16:12
*** tktk8924 has quit IRC16:12
adrian_ottomy apologies for my delayed action16:12
*** DuncanT has joined #openstack-meeting-alt16:12
sdake_daneyon_ we are drinking from two firehoses atm16:12
daneyon_adrian_otto no worries... i know you are busy16:12
adrian_ottodaneyon, a family emergency has surfaced for me, and I may need to step away from work to attend to it.16:12
daneyon_sdake_ i hope you're thirsty... lol16:12
sdake_more like hungry16:13
sdake_plate overflowing!16:13
daneyon_adrian_otto unless their are any questions, that's all i have for the network subteam update16:13
adrian_ottook, let's get through our agenda, and I'll regroup with you on taht subject16:13
daneyon_adrian_otto no worries. family 1st.16:13
daneyon_adrian_otto i hope all is well16:13
adrian_otto1 sec16:15
adrian_otto#topic Magnum UI Subteam Update (bradjones)16:16
*** openstack changes topic to "Magnum UI Subteam Update (bradjones) (Meeting topic: containers)"16:16
bradjonesNot a huge amount to update on this week16:16
*** vilobhmm has joined #openstack-meeting-alt16:16
bradjonesI have pushed a WIP patch that is the view for BayModel16:17
bradjonescurrently working on getting the API working then once it is synced up I will be pestering you all for reviews :)16:17
*** ashleighfarnham has joined #openstack-meeting-alt16:17
bradjonesgetting reviews from horizon folks without a magnum environment will be tricky16:17
*** kfarr has joined #openstack-meeting-alt16:17
bradjonesso hoping you guys will be able to help review in some capacity to check the workflow is as expected16:18
sdake_bradjones note I dont think we can review the patches16:18
adrian_ottosdake_: why?16:18
sdake_adrian_otto I thought we had a separeate group that didnt have magnum in it in gerrit16:18
sdake_but couldbe wrong16:18
adrian_ottoyou can review anything in Gerrit16:19
sdake_oh i mean +2 review16:19
bradjonessdake_: it doesn't have to be a +2 review but just a +1 from a few people with magnum envs to test against will be great16:19
sdake_yes of course I could review :)16:19
TangoI can work with Thai Tran here and provide him with a magnum environment to review16:19
bradjonesTango: That would be great thanks16:19
apmeltonbradjones: I should be able to throw it in my magnum environment and play around with horizon16:19
*** j___ has joined #openstack-meeting-alt16:19
apmeltonmight need a little help getting it installed, but I'd be glad to test it16:20
bradjonesI will post message in #openstack-containers when it is in a state to have a proper review16:20
adrian_ottoand I'm reasonably sure that magnum core as a group belongs to the magnum-ui-core group16:20
*** jcoufal has quit IRC16:20
adrian_ottothanks bradjones16:20
adrian_otto#topic Review Action Items16:20
*** openstack changes topic to "Review Action Items (Meeting topic: containers)"16:20
adrian_otto(none)16:20
adrian_otto#topic Blueprint/Bug Review16:20
*** openstack changes topic to "Blueprint/Bug Review (Meeting topic: containers)"16:20
adrian_ottoEssential Blueprint Updates16:20
adrian_ottoI am going to skip the first on the agenda b/c we downgraded it16:21
adrian_otto#link https://blueprints.launchpad.net/magnum/+spec/secure-kubernetes Secure the client/server communication between ReST client and ReST server (madhuri)16:21
madhuriAfter midcycle meetup, we have lot to do16:22
madhurihopefully few more patches are left16:22
adrian_ottoI notices a flurry of activity in the code review queue16:23
adrian_otto*noticed16:23
apmeltonmadhuri: is there anything with the core feature I can help with?16:23
madhuriapmelton: Thanks, can we fix a time to discuss16:24
adrian_ottothanks for your help apmelton16:24
adrian_ottomadhuri: anything you'd like to identify for team discussion today?16:24
madhuriadrian_otto: I apologize for the delay, I just shifted to India, so some work16:25
madhuriBut I am back on the work16:25
adrian_ottowelcome back!16:25
apmeltoncongrats on the new job!16:25
madhuriThanks apmelton :)16:25
adrian_ottoshould I advance to the next work item, madhuri?16:26
madhuriSure16:26
apmeltonactually, there's something I'd like to bring up here16:26
apmeltonthe effort to pull the lbaas cert manager into castella has stalled16:27
*** suro-patz has joined #openstack-meeting-alt16:27
apmeltonare we still planning to use their code?16:27
apmeltonthe lbaas cert manager code16:27
*** geoffarnold has quit IRC16:27
*** rm_work|away is now known as rm_work16:27
rm_worko/16:27
rm_workah, looks like good timing16:27
apmeltonrm_work: was the one working on the effort16:28
madhuriwe are using it for now16:28
suro-patzo/  : "entering late"16:28
apmeltonso, what I'm wondering is, if both Magnum and Octavia is planning to support that code, should we attempt pulling it into an oslo library?16:29
madhuriapmelton: What's your concern?16:29
madhuriYes that can be an improvement.16:29
*** agarciam has quit IRC16:30
apmeltonI guess my concern is maintaining that code in two trees16:30
madhuriThat's a different task and we can discuss seperately16:30
apmeltonalright16:30
rm_workyes, I would love to see it somewhere common16:30
madhuri+116:30
rm_workthere is some refactoring that needs to happen anyway, so i would support an effort to get it into a common project16:30
sdake_maintaining which code?16:31
sdake_sorry irc algged out16:31
apmeltonsdake_: the lbaas cert manager code we're planning to use in our cert manager16:31
sdake_thanks16:31
rm_workLBaaS abandoned its effort to get the code in Castellan, because we realized the CertManager interface wasn't going to work out for us anyway for technical reasons, but the CertGenerator code (which i think you actually care more about?) is still going to be used16:31
rm_workit was just an even harder sell for Castellan so we hadn't tried yet16:32
apmeltonrm_work: yes, sorry, CertGenerator16:32
apmeltonI guess what we can do is solidify our use case in our tree, then pull out the common pieces once we've got it working16:33
*** catherineD has left #openstack-meeting-alt16:33
rm_workYeah, I will be happy to help with that when you are working on it16:33
rm_workwhoever takes that task can drop me a line16:33
adrian_ottook, so let's do this one step at a time.16:33
adrian_ottolet's get the solution merges in Magnum first, and then decide how best to share it among projects16:33
apmeltonsounds good to me16:34
rm_workyep16:34
madhuri+116:34
sdake_+216:34
*** Ramanjaneya has quit IRC16:34
*** sdake_ is now known as sdake16:34
vilobhmmUpdate objects from the bay16:34
adrian_ottocool, I'll make a note to put this on our topic list for Tokyo if we don't get to it before then.16:34
*** esker has quit IRC16:34
adrian_ottovilobhmm: proceed16:35
vilobhmmsure :)16:35
vilobhmmLast week took ownership of it. We got the design and approach sorted out, thanks to sdake for providing help wherever needed. Looks like there is no Query-by-UUID k8s ReST API https://github.com/kubernetes/kubernetes/issues/4817 in Kubernates. Whereas in each of our resources (pod/rc/service) we try to instantiate the object using https://github.com/openstack/magnum/blob/master/magnum/api/controllers/v1/utils.py#L70 but if we p16:35
adrian_ottotruncated?16:35
vilobhmmWe got the design and approach sorted out, thanks to sdake for providing help wherever needed. Looks like there is no Query-by-UUID k8s ReST API https://github.com/kubernetes/kubernetes/issues/4817 in Kubernates.16:36
vilobhmmWhereas in each of our resources (pod/rc/service) we try to instantiate the object using https://github.com/openstack/magnum/blob/master/magnum/api/controllers/v1/utils.py#L70  we use QUERY-by-UUID16:36
*** dizquierdo has quit IRC16:36
*** sputnik13 has joined #openstack-meeting-alt16:36
*** svinota has quit IRC16:36
vilobhmmbut if we plan to create the objects for these resources using the ReST Bay/k8s endpoints we only have the option to get it from name as only QUERY-by-NAME is supported as of now16:36
*** dims has quit IRC16:36
vilobhmmSo my plan is to irc://irc.freenode.net:6667/#1. get the uuid -> name conversion as part of QUERY-by-UUID, will get this information from magnum db irc://irc.freenode.net:6667/#. Once we get the name in irc://irc.freenode.net:6667/#1. do a QUERY-by-NAME to fetch details from k8s ReST API endpoints. Want to know your thoughts on this.16:36
vilobhmmSo till the time kubernates provide a QUERY-by-UUID we will need a way to store the mapping from uuid to name and at present the best place to keep it IMHO happens to be the table for the respective resource for example magnum.rc, magnum.service etc…16:37
*** noslzzp has quit IRC16:37
vilobhmmaddrian_otto : I hope it is not truncated now16:37
sdakeso just to clarify, when getting a list16:37
sdakethe process is for pod in list_from_kys:16:37
sdake    pod = k8s_query_by_name16:38
vilobhmmok16:38
sdake   pod_uuid = k8s_query_by_uuid?16:38
suro-patzI think it is better to have an object representation at magnum-db, which will provide the translation/mapping to the rc/service/pod object of k8s16:38
*** scheuran has quit IRC16:38
sdakesuro-patz I'd rather avoid that, because if someone creates an objectt with the native client, the mapping wont be present in the database16:39
*** dims has joined #openstack-meeting-alt16:39
*** ganeshna_ has joined #openstack-meeting-alt16:39
suro-patzsdake: point noted16:39
hongbinSo, we are not able to: magnum pod-show <pod_uuid> ?16:39
madhuriAgree16:39
vilobhmmsdake : but right now there is no way to have a uuid-name mapping16:39
sdakeso what precisely is the proposal on uuids16:39
sdakewithout cut and paste ;)16:39
suro-patzsdake: but a name is unique identifier given a bay16:40
madhuriI think this should read from kuberentes not magnum db16:40
vilobhmmmadhuri : +!16:40
vilobhmm+116:40
*** manjeet_ has joined #openstack-meeting-alt16:40
sdakesuro-patz yes I htink we can use the bay uuid to help generate a uuid from the pod id16:40
*** dprince has joined #openstack-meeting-alt16:40
sdakepod name rather16:40
vilobhmmthats what the blueprint is for IMHO…just that right now only QUERY-by-NAME k8s Rest api is available16:40
hongbinHow about store static information in DB, and read from kubernetes for dynamic state16:40
*** annegentle has quit IRC16:41
adrian_otto+116:41
sdakenothing about pods can be in the database, because it wont be updated when a native client is ued to write to k8s16:41
madhurihongbin: +116:41
adrian_ottothat's the direction we aimed at when we discussed this last as a team16:41
sdakeessentially the database will be missing information on native client write operations16:42
adrian_ottosdake, things like the name of the pod and it's identifier can be in the db16:42
apmeltonadrian_otto: not if it was created by the native client16:42
mfalatic+116:42
sdakekube-ctl create pod.yaml16:42
*** ganeshn__ has joined #openstack-meeting-alt16:42
vilobhmmadrain_otto : +1 for now till the time https://github.com/kubernetes/kubernetes/issues/4817  gets resolved16:42
adrian_ottowe can use a synchronization approach to make sure the static state remains mirrored16:42
sdakeadrian_otto that will create a pod that kubernetes doesn't know about16:42
adrian_ottoapmelton: yes, this is the same as heat convergence16:43
sdakerather that magnum doen't know about16:43
sdakeyes i thought of this sync approach adrian_otto16:43
adrian_ottoit won't know about it initially, but it can learn about it soon after it is created16:43
sdakeit seems better imo just to always get from the k8s api16:43
*** ganeshna has quit IRC16:43
adrian_ottoI see16:43
apmeltonI thought the entire point of using CoE objects directly was to get us out of the sync and lock game16:43
sdakebecause a sync has to do the same thing in essence16:43
sdakeget it from the k8s endpoint16:43
adrian_ottoso in that case we don't persist pod information at all. I could live with that.16:44
sdakeapmelton no it is to get is to be able to use native cleints, what you mention is a side benefit ;)16:44
sdakeor rc/service info16:44
sdakeadrian_otto that is what we are after here ;)16:44
madhuriYes better to get from k8s endpoint directly16:45
sdakevilobhmm if you have more test patches in your stream, please put them up for review16:45
sdakeeven if they are wip16:45
sdakei'd like to see the whole stream befor merging16:45
vilobhmmmagnum api's : just keep mapping uuid-name in db just the mapping..whereas all the "fresh" data is accessed and updated using k8s ReST endpoints…for native client : get directly from k8s endpoints16:45
sdakeso we aren't in a state of some stuff comes from db some stuff comes from k8s endpoint16:45
vilobhmmsdake  : sure will do16:45
TangoWhat's the outlook for kubernetes to provide this support?16:45
suro-patzif the objective is to make magnum client behave as per the native client, magnum api should behave as pass through16:45
sdakemake sure to title it WIP:16:46
vilobhmmsdake : yup16:46
adrian_ottook, vilobhmm ready to advance topics now?16:46
sdaketango I dont understand the q16:46
*** ganeshna_ has quit IRC16:46
Tangosdake: the issue that vilobhmm pointed out16:46
*** sputnik13 has quit IRC16:47
vilobhmmadrian_otto : sure..just a last question to you and team does this seems fair "just keep mapping uuid-name in db just the mapping..whereas all the "fresh" data is accessed and updated using k8s ReST endpoints…for native client : get directly from k8s endpoints"16:47
vilobhmmfor magnum api - just keep...16:47
vilobhmmso that i can submit more WIP patches based of this16:47
adrian_ottovilobhmm: let's start with a naive implementation that fetches all pod and service and rc related state directly from k8s rather than persisting duplicates of state data in our own db16:48
vilobhmmadrian_otto : seems fair16:49
vilobhmmwe can move ahead16:49
adrian_ottoif that proves to be a problem, then we can optimize from there16:49
vilobhmmthanks all!16:49
madhuriadrian_otto: +1, no data in magnum db16:49
vilobhmmalrite16:49
adrian_ottocool, thanks!16:49
vilobhmmmadhuri : +1 thanks16:49
adrian_ottolink https://blueprints.launchpad.net/magnum/+spec/external-lb Support the kubernetes service external-load-balancer feature (Tango)16:49
adrian_otto#link https://blueprints.launchpad.net/magnum/+spec/external-lb Support the kubernetes service external-load-balancer feature (Tango)16:49
TangoWe got Angus Lees (gus) to engage directly, so that's good news16:50
*** ivar-lazzaro has joined #openstack-meeting-alt16:50
TangoHe pointed out 3 new patches that we need.  They are not merged yet, so I built a customer Kubernetes version based on 1.0.316:50
adrian_ottoI also saw references to k8s patches16:50
*** dizquierdo has joined #openstack-meeting-alt16:51
*** davideagnello has joined #openstack-meeting-alt16:51
TangoI am testing it now.   With gus help, I am hopeful16:51
adrian_ottowe could "bird dog" stalk those patches with our k8s friends16:51
TangoAngus thinks there may be a few more bugs to fix16:52
adrian_ottoat a minimum simply express our interest in those by updating them in the k8s project bug tracker16:52
TangoYep16:52
madhuriJust for update I generated 1.0.3 kubernetes client code and it is not working16:52
adrian_ottook, Tango once we have a working setup, and we know what patches we want to land upstream, please let me know so I can apply what influence we have there so they get the attention they deserve16:52
TangoI am also working on a patch to set the parameters for the heat templates, will upload the initial version shortly, then will likely need feedback from the team16:53
*** padkrish has joined #openstack-meeting-alt16:53
TangoAnd adding a functional test based on wordpress, although it won't run until we have V1 api support16:53
madhuriTango: I generated v1 client code only16:54
*** sputnik13 has joined #openstack-meeting-alt16:54
adrian_ottook, should we pull in team members to assist with that?16:54
*** dims has quit IRC16:54
Tangomadhuri: Can I pick them up?16:54
*** ganeshna has joined #openstack-meeting-alt16:54
madhuriI am busy with TLS, if any one wants to take it. it will be good16:55
TangoYes it would be good to have help moving to V1 api16:55
*** ativelkov has joined #openstack-meeting-alt16:55
madhuriSure Tango16:55
*** ganeshna_ has joined #openstack-meeting-alt16:55
hongbinI can help if you want16:55
adrian_ottoawesome hongbin!16:55
Tangohongbin: Thanks hongbin, will ping you16:55
*** kzaitsev_mb has joined #openstack-meeting-alt16:55
hongbink16:55
madhuriAnyone please :)16:55
*** tfukushima has quit IRC16:56
madhuriTango: Please let me know if I can help anyway16:56
adrian_otto#link https://blueprints.launchpad.net/magnum/+spec/secure-docker Secure client/server communication using TLS (apmelton)16:56
adrian_ottowe have code for this now16:56
apmeltongot a WIP review up, I"m updating it as reviews show up and patches land16:56
manjeet_Tango: I can help in setting parameters for heat templates16:56
apmeltonwon't really be finished until the core TLS stuff lands16:57
*** VW_ has joined #openstack-meeting-alt16:57
adrian_ottothanks apmelton16:57
adrian_otto#topic Open Discussion16:57
*** openstack changes topic to "Open Discussion (Meeting topic: containers)"16:57
*** noa_koffman has joined #openstack-meeting-alt16:57
*** dims has joined #openstack-meeting-alt16:57
*** ganeshn__ has quit IRC16:57
adrian_ottoI am scheduled to appear in a keynote panel at OpenStack Silicon Valley16:57
hongbinI have a question: what is the deadline for landing liberty feature for Magnum?16:57
adrian_ottothere is a remote chance I may have family business that conflicts with it16:57
madhuri+1 hongbin16:58
adrian_ottoso I may reach out to a few of you to act as a standby16:58
*** shashank_hegde has joined #openstack-meeting-alt16:58
adrian_ottothe event is on August 26+27 in Mountain View, CA16:58
*** ganeshna has quit IRC16:59
*** katyafervent2 has joined #openstack-meeting-alt16:59
*** sputnik1_ has joined #openstack-meeting-alt16:59
*** sgotliv_ has quit IRC16:59
*** _amrith_ is now known as amrith16:59
*** Nikolay_St has joined #openstack-meeting-alt16:59
adrian_ottohongbin: there is not an official deadline, but we need all new features ASAP17:00
*** StanLagun has joined #openstack-meeting-alt17:00
*** sputnik13 has quit IRC17:00
*** ganeshna has joined #openstack-meeting-alt17:00
adrian_ottotime elapsed17:00
*** FilipBlaha has joined #openstack-meeting-alt17:00
daneyon_i have to jump to my next meeting17:00
*** ddovbii has joined #openstack-meeting-alt17:00
*** padkrish has quit IRC17:00
adrian_ottoour next meeting is 2015-08-25 at 2200 UTC (sdake charis)17:00
*** docaedo has joined #openstack-meeting-alt17:00
adrian_otto#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Aug 18 17:00:43 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/containers/2015/containers.2015-08-18-16.01.html17:00
*** hongbin has left #openstack-meeting-alt17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/containers/2015/containers.2015-08-18-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/containers/2015/containers.2015-08-18-16.01.log.html17:00
*** suro-patz has left #openstack-meeting-alt17:00
*** diga has left #openstack-meeting-alt17:00
*** dizquierdo has quit IRC17:01
Nikolay_St#startmeeting Murano17:01
openstackMeeting started Tue Aug 18 17:01:27 2015 UTC and is due to finish in 60 minutes.  The chair is Nikolay_St. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: Murano)"17:01
openstackThe meeting name has been set to 'murano'17:01
kzaitsev_mbo/17:01
Nikolay_Sto/17:01
Nikolay_Sthi folks17:01
noa_koffman0/17:01
ddovbiihi17:01
*** eghobo_ has left #openstack-meeting-alt17:02
FilipBlahahi17:02
Nikolay_Sttoday Serg asked me to be a chair :)17:02
StanLagunhi17:02
katyafervent2hi17:02
Nikolay_Sthere is agenda of the meeting: https://wiki.openstack.org/wiki/Meetings/MuranoAgenda#Agenda17:02
Nikolay_Stlet's start with action items review17:02
*** ajmiller has quit IRC17:02
*** dims_ has joined #openstack-meeting-alt17:02
Nikolay_St#topic Action Items Review17:02
*** openstack changes topic to "Action Items Review (Meeting topic: Murano)"17:02
*** mfalatic has left #openstack-meeting-alt17:03
kzaitsev_mb#link https://wiki.openstack.org/wiki/Meetings/MuranoAgenda/Archive/2015-08-18/#Agenda17:03
ativelkovo/17:03
kzaitsev_mba more permanent link for agenda )17:03
kzaitsev_mbmore or less17:03
*** VW_ has quit IRC17:03
Nikolay_Stoh, sorry. I'm new with it :)17:03
*** ganeshna_ has quit IRC17:03
*** VW_ has joined #openstack-meeting-alt17:03
*** mgershenzon has joined #openstack-meeting-alt17:04
*** VW_ has quit IRC17:04
kzaitsev_mbdon't worry, seems that nobody really maintains it, I just like to have a bit more consistent logs =)17:04
*** dims has quit IRC17:04
*** VW_ has joined #openstack-meeting-alt17:04
Nikolay_Stkzaitsev_mb: please. You was able to write a email to openstack-dev about new yaql17:04
*** apmelton has left #openstack-meeting-alt17:04
kzaitsev_mbyep, done that17:04
Nikolay_Stok17:05
*** nadya has quit IRC17:05
kzaitsev_mbalso freerunner added a valuable comment with devstack rc17:05
*** ganeshna has quit IRC17:05
*** rpothier has left #openstack-meeting-alt17:05
Nikolay_Stnext action was about "pin yaql requirements to RC2"17:05
Nikolay_Stwho is responsible for it?17:06
kzaitsev_mb#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/071980.html17:06
StanLagunrc2 is pinned in migration commit17:06
*** madhuri has quit IRC17:06
kzaitsev_mb#link http://lists.openstack.org/pipermail/openstack-dev/2015-August/071991.html17:06
StanLagunthe problem is that as it just have discovered seems that we are going to release rc317:06
*** mestery has quit IRC17:07
Nikolay_Stshould we pin it as the new action item?17:07
kzaitsev_mbbummer...17:07
ativelkovlet's discuss it a bit more17:07
*** adrian_otto has left #openstack-meeting-alt17:07
*** carl_baldwin has quit IRC17:07
Nikolay_Stwe have a topic about yaql 1.017:07
Nikolay_Stso, I think we can move to it17:07
*** sputnik1_ has quit IRC17:07
*** ganeshna has joined #openstack-meeting-alt17:07
ativelkovyup17:07
*** sputnik13 has joined #openstack-meeting-alt17:08
Nikolay_St#topic Migrating to yaql 1.0 status17:08
*** openstack changes topic to "Migrating to yaql 1.0 status (Meeting topic: Murano)"17:08
Nikolay_Stslagle: please17:08
ativelkovso, there are a couple of breaking changes between 0.2.x and 1.0 which are not yet reflected in "legacy mode"17:08
Nikolay_StStanLagun: please17:08
*** rbradfor has left #openstack-meeting-alt17:08
ativelkovwe may add them to that mode, but that would require us to release a rc317:08
*** dims has joined #openstack-meeting-alt17:08
ativelkovOR we may address them in Murano engine17:08
*** padkrish has joined #openstack-meeting-alt17:09
ativelkovI stand for the former17:09
*** dims_ has quit IRC17:09
ativelkovbut this may be discussed and other options may be considered17:09
*** minwang2 has joined #openstack-meeting-alt17:09
kzaitsev_mbFixing YAQL behaviour seems like a better idea to me. Otherwise we would be adding a workaround, won't we?17:10
StanLagunI agree that it is better to fix in yaql itself because legacy mode was intended to emulate yaql 0.2 behavior and we see several constructs that do not work any more (though for a good reason)17:10
*** sputnik13 has quit IRC17:10
Nikolay_StI agreee with kzaitsev_mb17:10
StanLagunjust note this is not fixing yaql but yaql legacy mode17:10
kzaitsev_mbSo it's more like a bug in the way we support old 0.2 apps17:11
StanLagunit may be worth it to discuss if the decision to drop that behavior was a correct one17:11
*** dims_ has joined #openstack-meeting-alt17:11
ativelkovyup17:11
*** ganeshna_ has joined #openstack-meeting-alt17:11
ativelkovStanLagun: could you please elaboreate more on that decision?17:12
StanLagunthere are 2 breaking changes that were not addressed:17:12
*** dizquierdo has joined #openstack-meeting-alt17:13
StanLagun1) in yaql 0.2 you could say $key in $dict (as in Python). In yaql 1.0 you can say $key in $dict.keys(), $key in $dict.values() etc. $dict itself is not iterable17:13
*** sputnik13 has joined #openstack-meeting-alt17:14
*** dims has quit IRC17:14
StanLagun2) In yaql 0.2 foo() != true would be true if foo would return string, integer, whatever. In yaql 1.0 if foo would return non-boolean value that would cause exception to be thrown17:14
StanLagunthe same for =17:14
StanLagunI truly believe this is better behavior17:15
*** bswartz has quit IRC17:15
StanLagunbut old behavior need to be restored in legacy mode17:15
*** ganeshna has quit IRC17:15
kzaitsev_mbso yaql 1.0 is not strongly typed? =)17:16
kzaitsev_mbs/not/now/17:16
StanLagunkind of17:16
kzaitsev_mbis it really a good idea for non-compiled language?17:17
StanLagunexplicit is better then implicit17:17
ativelkovI like the change of 1): iterating the dict is a bad idea anyway17:17
*** yamahata has quit IRC17:17
ativelkovbut I don't like 2)17:17
*** padkrish has quit IRC17:18
kzaitsev_mbI kind of thought, that strong typing allows better code analysis tools to be written and helps developer to find errors before the programm is even run17:18
*** ganeshna has joined #openstack-meeting-alt17:18
*** bswartz has joined #openstack-meeting-alt17:18
*** ndipanov has joined #openstack-meeting-alt17:18
*** priti_ has quit IRC17:18
StanLagunthe motivation for 2 is that comparing non-comparible values is usualy a sign of a program bug. Usual real-life bug is foo != true instead of $foo != true17:18
StanLagunso this is a way not to mask bug17:19
StanLagunbtw this was a bug discovered in k8s implementation and thats how I discovered it17:19
*** dims_ has quit IRC17:20
*** sputnik13 has quit IRC17:20
*** absubram has joined #openstack-meeting-alt17:20
*** dims has joined #openstack-meeting-alt17:20
*** jeadr has quit IRC17:20
*** jeadr has joined #openstack-meeting-alt17:20
*** dims has quit IRC17:20
ativelkovso, to "fix" that in code one would need to do something like "bool($foo) != true?17:20
*** dims has joined #openstack-meeting-alt17:21
ativelkovI mean in a non-legacy mode?17:21
*** ganeshna_ has quit IRC17:21
*** ganeshna has quit IRC17:21
*** shashank_hegde has quit IRC17:21
StanLagunyes. But for yaql you will not often use such constructions. And for MuranoPL you don't need them at all since If macro will evaluate similar to Python17:22
*** geoffarnold has joined #openstack-meeting-alt17:22
StanLagunbut in reality you nearly always will write $foo != 0 or != ''17:23
*** ganeshna has joined #openstack-meeting-alt17:23
StanLagunbecause most of the time you know the type17:23
kzaitsev_mbwell, like I said, I really think Stan should grow a beard =)17:24
*** HeOS has joined #openstack-meeting-alt17:24
ativelkov:)17:25
kzaitsev_mbCount me as a python guy here, so I like my objects comparable no matter what, but my '+'s raising Runtime Errors if the language does not know how to add17:25
*** yamamoto has quit IRC17:25
*** dizquierdo has quit IRC17:26
ativelkovkzaitsev_mb: important difference here with python is that arbitrary character combination counts as a string in yaql17:26
ativelkovi.e. "abc != true" will always be true17:26
*** achanda has joined #openstack-meeting-alt17:27
kzaitsev_mbbut I believe, that I do not know if this is a good thing to have or a bad thing to have, so you can safely disregard my opinion )))17:27
ativelkovas it evaluates to "'abc' != true"17:27
StanLagunand that is really often error that I even make myself17:27
*** ganeshna has quit IRC17:27
ativelkovSo, Stan's point is that the developer is likely to forget about writing $ before variable name, thus making this variable just a string instead17:27
*** dkalleg has joined #openstack-meeting-alt17:28
ativelkovPersonally, I don't think it is a reason to require explicit booleans17:28
ativelkovBut, well.. I am ok with either solution17:28
kzaitsev_mbativelkov: require explicit var declaration then? =)))17:28
*** padkrish has joined #openstack-meeting-alt17:28
ativelkovkzaitsev_mb: blasphemy!17:29
kzaitsev_mblet's summ it up, won't we?17:29
StanLagunthere is another reason for that17:29
ativelkovStanLagun: which is?17:29
kzaitsev_mbWe have to fix yaql legacy support, before we can release 1.0, right?17:29
ativelkovkzaitsev_mb: yup, at least for dict iteration part17:30
ativelkov(as it seems like we are in an agreement on it)17:30
kzaitsev_mbAnd there is going to be rc3, which is sad, but inevitable, heh17:30
ativelkovlooks like you are right17:30
*** SumitNaiksatam has joined #openstack-meeting-alt17:31
StanLagunno, there is no other reason17:31
katyafervent2can we just releaze 1.0 with all the fixrs?17:32
ativelkovkatyafervent2: well.. it's a bit bad practice17:32
katyafervent2*fixes17:32
*** s3wong has joined #openstack-meeting-alt17:32
ativelkovRC should become an RTM without any changes17:33
StanLagunthere might be other compatibility issues. There are no unit tests for yaql 0.2 that could be used to ensure compatibility17:33
ativelkovAt least in my understanding17:33
ativelkovStanLagun: right, and in this case we will release 1.0.x's17:33
katyafervent2why? openstack rc2 and release itself may be different17:33
*** sputnik13 has joined #openstack-meeting-alt17:33
ativelkovbut if we already know about an issue, we may fix it17:34
ativelkovkatyafervent2: not unless you are ok without releasing it without a proper testing17:34
ativelkovok with* releasing it17:34
ativelkovIf we make this change and wnat to test it before the release, we'll need to tag the changed binary somehow. rc3 is a good tag )17:35
katyafervent2ok)17:36
Nikolay_Stso17:36
Nikolay_Stwe need a final decision17:36
Nikolay_Stor we can run out of time17:36
*** jprovazn has quit IRC17:36
*** padkrish has quit IRC17:36
Nikolay_StStanLagun: please17:37
StanLagunI suggest to fix it in rc3. But do not release rc3 until we have successfully deployed one really complex env with k8s etc17:37
StanLagunto maximize our chances to find other errors of that kind17:37
Nikolay_Stshould we marked it as action item?17:38
*** pvaneck has joined #openstack-meeting-alt17:38
kzaitsev_mbNikolay_St: I believe we should )17:38
StanLaguni will submit fixes today. Please review ASAP17:38
ativelkovok17:38
ativelkovStanLagun: ping me directly for faster review17:38
ativelkovhow may we test it without releasing rc3?17:39
StanLagunby installing yaql from gerrit17:39
Nikolay_St#actionitem fix yaql legacy mode and release yaql rc3 after successful deployment17:39
ativelkovoh, so you mean manual verification17:39
ativelkovok17:39
StanLagunThis is a matter of 1 day17:39
Nikolay_St#action fix yaql legacy mode and release yaql rc3 after successful deployment17:40
ativelkovThis AI should go to akuznetsova, shouldn't it?17:40
*** vdrok has joined #openstack-meeting-alt17:40
Nikolay_Stso we can move to the next topic, I guess17:41
Nikolay_St#topic Artifact (glance v3) transition status update17:41
*** openstack changes topic to "Artifact (glance v3) transition status update (Meeting topic: Murano)"17:41
ativelkovI am working to fix the remaining issues about artifact filtering in glance17:42
ativelkovfixed two of them since the last update, one more relate17:42
Nikolay_Stok, good to know17:42
ativelkovAlso, I've found an issue in python-glanceclient17:42
*** vdrok has left #openstack-meeting-alt17:43
*** padkrish has joined #openstack-meeting-alt17:43
ativelkov(as I expected we may start facing issues there as nobody before has ever used the v3 part of it)17:43
*** jckasper has quit IRC17:43
ativelkovI've asked mfedosin for help with that17:43
ativelkovprobably more help will be needed :)17:45
Nikolay_St#info 2 issues was fixed, one more to go. issue in glanceclient will be fixed by mfedoshin17:45
*** yamahata has joined #openstack-meeting-alt17:45
*** geoffarnold has quit IRC17:45
Nikolay_Stany other updates on this topic?17:45
Nikolay_Stor any questions?17:46
ativelkovnope17:46
Nikolay_Stok, let's move further17:46
Nikolay_St#topic Allow (or not) public packages in package definitions-view in dashboard (kzaitsev)17:46
*** openstack changes topic to "Allow (or not) public packages in package definitions-view in dashboard (kzaitsev) (Meeting topic: Murano)"17:46
Nikolay_Stkzaitsev_mb: please17:46
kzaitsev_mb#link https://review.openstack.org/#/c/213682/17:46
kzaitsev_mbok so there is this review17:46
kzaitsev_mbI suppose zhu.rong is not here17:46
kzaitsev_mbwell. I still think we might discuss it anyway17:47
kzaitsev_mbI'll try to be quick17:47
kzaitsev_mbWe've intentionally removed public packages from Pakcage Definitions view17:47
*** geoffarnold has joined #openstack-meeting-alt17:47
kzaitsev_mbBut now we've added (copied from glance dashboard) a filter with public,project, other packages17:47
katyafervent2do you mean for non admin?17:48
kzaitsev_mbso this creates a rather wierd UX experience17:48
kzaitsev_mbyep17:48
kzaitsev_mbexactly — non-admin user can't see public packages on package-definitions, cause he can't edit them.17:48
*** padkrish has quit IRC17:48
Nikolay_Stkzaitsev_mb: I run through your comments on review17:49
ativelkovpackage-definitions view is intended for edit only17:49
kzaitsev_mbNow we have a "Public" filter for him, which makes him think, that there should be public packages there, but there are not =/17:49
katyafervent2thats expected behaviour17:49
ativelkovwhy would anybody list non-editable things in the editor?17:49
Nikolay_StI guess we should remove "public" filter17:49
kzaitsev_mbativelkov: katyafervent2: agree, but I feel that it creates negative UX17:49
kzaitsev_mbNikolay_St: that's one option17:49
StanLagunwe can rename it. Public -> My Public17:49
kzaitsev_mbother would be to list everything and forbid editing17:50
ativelkovkzaitsev_mb: imho, the "public,project, other" filter should not be part of package editor17:50
ativelkovit should be in catalog view17:50
kzaitsev_mbI can summ it up in a letter, since we're almos out of time17:50
kzaitsev_mbwhat do you think of that idea?17:50
kzaitsev_mbI feel the PREASSURE +)))17:51
mgershenzon+117:51
kzaitsev_mbmgershenzon: yep, I really want to allow you to have some time with your item )17:51
*** priti has joined #openstack-meeting-alt17:51
mgershenzon=)17:51
Nikolay_St+117:51
ativelkovagree17:52
StanLagun+1 to list all but grey out those that I don't own. But!!! I want to be able to export them since I can deploy them17:52
noa_koffman+117:52
*** jckasper has joined #openstack-meeting-alt17:52
kzaitsev_mb#action kzaitsev_mb summ up the UX concerns about the public/non-public packages on Package Definitions in ML17:52
Nikolay_Stok, next topic17:53
kzaitsev_mbphew )17:53
Nikolay_St#topic Add support for heat environments17:53
*** priti_ has joined #openstack-meeting-alt17:53
*** openstack changes topic to "Add support for heat environments (Meeting topic: Murano)"17:53
mgershenzonThe API works well, you can review here #link https://review.openstack.org/#/c/211608/17:53
mgershenzonThe main risk is about the UI...17:53
mgershenzonWhen the spec was approved we agreed someone with more UI experience will find the time to help with the UI. I still think this is necessary.17:53
Nikolay_Stmgershenzon: for sure. any volunteers?17:54
mgershenzonThe API works well, you can review here #link https://review.openstack.org/#/c/211608/17:54
mgershenzonThe main risk is about the UI...17:54
mgershenzonWhen the spec was approved we agreed someone with more UI experience will find the time to help with the UI. I still think this is necessary.17:54
mgershenzonThere are 3 main issues with current implementation:17:54
mgershenzon- when the hot template parameters has no defaults, the UI user must enter parameter values, even if there is an environment that already contains them.17:54
mgershenzon- when the hot template parameters has defaults and the user clear the defaults and leaves the fields empty, the UI still sends the parameters with null values.17:54
mgershenzon- the current implementation effects values validation. I believe slagun and ativelkov know the issue.17:54
*** datsun180b has joined #openstack-meeting-alt17:54
mgershenzon*StanLagun17:54
ativelkovYup17:55
ativelkovI was looking at that17:55
mgershenzon=)17:55
*** harshs_ has joined #openstack-meeting-alt17:55
StanLagunativelkov, I thought we had a solution for this17:56
*** priti has quit IRC17:56
StanLagunbut this requires dedicated BP/spec17:56
mgershenzonSorry about the flood, I have written it in my phone in advance17:56
StanLagun:)17:56
ativelkovStanLagun: yup, but let's proceed step-by-step17:56
*** FilipBlaha has quit IRC17:56
*** harshs has quit IRC17:56
*** harshs_ is now known as harshs17:56
ativelkovSo, let's ensure that mgershenzon's patch does not break the current UI behavior17:57
*** banix has quit IRC17:57
ativelkovI mean the one for HOT-based apps without the envs17:57
ativelkovand land the patch17:57
StanLagunyes17:57
ativelkovThen we may think about ways to improve it so env's may be selected in UI17:57
StanLagunI'm already doing changes in the HOt processor. So we better hurry with this17:58
ativelkovStanLagun: which changes?17:58
StanLagunhttps://review.openstack.org/#/c/214163/17:58
StanLagunhttps://review.openstack.org/#/c/214163/3/murano/packages/hot_package.py17:58
Nikolay_St#action verify that https://review.openstack.org/#/c/211608/ don't break anything then produce next steps with UI17:59
Nikolay_Stguys, time17:59
ativelkovAh, I see17:59
ativelkovOk, so we are agreed on that17:59
ativelkovgood17:59
Nikolay_Stok, good17:59
ativelkovtime is up17:59
StanLagunwho will do it?17:59
ativelkovI'll do the reviews18:00
katyafervent2we can continue on #murano18:00
Nikolay_Sttime is up18:00
ativelkovthanks all18:00
Nikolay_Stlet's continue on #murano18:00
Nikolay_St#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
mgershenzonThank you18:00
openstackMeeting ended Tue Aug 18 18:00:44 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/murano/2015/murano.2015-08-18-17.01.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/murano/2015/murano.2015-08-18-17.01.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/murano/2015/murano.2015-08-18-17.01.log.html18:00
*** StanLagun has left #openstack-meeting-alt18:00
*** ajmiller has joined #openstack-meeting-alt18:00
Nikolay_Stthanks all18:00
*** Nikolay_St has quit IRC18:01
*** rohit404 has joined #openstack-meeting-alt18:01
*** rohit404 has left #openstack-meeting-alt18:01
*** ativelkov has left #openstack-meeting-alt18:02
*** katyafervent2 has quit IRC18:03
*** Tango has quit IRC18:04
*** balajiiyer has joined #openstack-meeting-alt18:04
*** noa_koffman has quit IRC18:05
*** banix has joined #openstack-meeting-alt18:05
*** shashank_hegde has joined #openstack-meeting-alt18:06
*** amotoki has quit IRC18:07
*** mgershenzon has quit IRC18:07
*** gyee has joined #openstack-meeting-alt18:08
*** bana_k has joined #openstack-meeting-alt18:10
*** salv-orlando has quit IRC18:12
*** padkrish has joined #openstack-meeting-alt18:16
*** geoffarnold has quit IRC18:17
*** geoffarnold has joined #openstack-meeting-alt18:18
*** jeadr has quit IRC18:18
*** jeadr has joined #openstack-meeting-alt18:18
*** HeOS has quit IRC18:19
*** ivar-lazzaro has quit IRC18:22
*** yamamoto has joined #openstack-meeting-alt18:26
*** geoffarnold has quit IRC18:28
*** jeadr has quit IRC18:29
*** jeadr has joined #openstack-meeting-alt18:29
*** ivar-lazzaro has joined #openstack-meeting-alt18:30
*** yamamoto has quit IRC18:30
*** gyee has quit IRC18:31
*** padkrish has quit IRC18:32
*** gyee has joined #openstack-meeting-alt18:32
*** padkrish has joined #openstack-meeting-alt18:32
*** padkrish has quit IRC18:32
*** padkrish has joined #openstack-meeting-alt18:34
*** balajiiyer1 has joined #openstack-meeting-alt18:34
*** nadya has joined #openstack-meeting-alt18:35
*** balajiiyer has quit IRC18:36
*** kfarr_ has joined #openstack-meeting-alt18:37
*** VW_ has quit IRC18:37
*** VW_ has joined #openstack-meeting-alt18:37
*** kfarr has quit IRC18:39
*** nadya has quit IRC18:39
*** geoffarnold has joined #openstack-meeting-alt18:40
*** puranamr has quit IRC18:41
*** VW_ has quit IRC18:42
*** Aish has quit IRC18:46
*** ashtokolov_ has quit IRC18:49
*** puranamr has joined #openstack-meeting-alt18:51
*** Sukhdev has joined #openstack-meeting-alt18:52
*** VW_ has joined #openstack-meeting-alt18:54
*** pnavarro has quit IRC18:56
*** geoffarnold has quit IRC18:56
*** VW_ has quit IRC18:56
*** sdake_ has joined #openstack-meeting-alt18:56
*** VW_ has joined #openstack-meeting-alt18:56
*** sgordon has quit IRC18:59
*** sgordon has joined #openstack-meeting-alt18:59
*** sdake has quit IRC18:59
*** banix has quit IRC19:00
*** gyee has quit IRC19:00
*** VW_ has quit IRC19:01
*** j___ has quit IRC19:02
*** fawadkhaliq has joined #openstack-meeting-alt19:02
*** banix has joined #openstack-meeting-alt19:04
*** annegentle has joined #openstack-meeting-alt19:06
*** e0ne has joined #openstack-meeting-alt19:08
*** amotoki has joined #openstack-meeting-alt19:08
*** nadya has joined #openstack-meeting-alt19:09
*** ndipanov has quit IRC19:09
*** manjeet_ has quit IRC19:11
*** amotoki has quit IRC19:13
*** fawadk has joined #openstack-meeting-alt19:13
*** esker has joined #openstack-meeting-alt19:15
*** fawadkhaliq has quit IRC19:16
*** salv-orl_ has joined #openstack-meeting-alt19:16
*** sdake_ is now known as sdake19:16
*** shashank_hegde has quit IRC19:16
*** HeOS has joined #openstack-meeting-alt19:20
*** annegentle has quit IRC19:21
*** achanda has quit IRC19:22
*** sbalukoff has quit IRC19:23
*** banix has quit IRC19:24
*** annegentle has joined #openstack-meeting-alt19:26
*** sbalukoff has joined #openstack-meeting-alt19:26
*** ivar-laz_ has joined #openstack-meeting-alt19:26
*** minwang2 has quit IRC19:27
*** ivar-lazzaro has quit IRC19:28
*** geoffarnold has joined #openstack-meeting-alt19:30
*** banix has joined #openstack-meeting-alt19:30
*** singleth_ has joined #openstack-meeting-alt19:31
*** vgridnev has joined #openstack-meeting-alt19:34
*** singlethink has quit IRC19:34
*** harshs has quit IRC19:34
*** belmoreira has joined #openstack-meeting-alt19:36
*** geoffarnold has quit IRC19:38
*** geoffarnold has joined #openstack-meeting-alt19:38
*** matrohon has joined #openstack-meeting-alt19:38
*** rohit404 has joined #openstack-meeting-alt19:41
*** fawadk has quit IRC19:41
*** vilobhmm has left #openstack-meeting-alt19:42
*** mestery has joined #openstack-meeting-alt19:44
*** rohit404 has left #openstack-meeting-alt19:44
*** e0ne has quit IRC19:44
*** carl_baldwin has joined #openstack-meeting-alt19:49
*** belmoreira has quit IRC19:51
*** ivar-laz_ has quit IRC19:55
*** ivar-lazzaro has joined #openstack-meeting-alt19:56
*** Aish has joined #openstack-meeting-alt19:56
*** annegentle has quit IRC19:57
*** balajiiyer1 has quit IRC19:57
*** sigmavirus24 is now known as sigmavirus24_awa19:57
*** sigmavirus24_awa is now known as sigmavirus2419:58
*** svinota has joined #openstack-meeting-alt19:59
*** annegentle has joined #openstack-meeting-alt20:00
*** tonytan4ever has quit IRC20:01
*** amrith is now known as _amrith_20:06
*** mestery has quit IRC20:08
*** tonytan4ever has joined #openstack-meeting-alt20:08
*** mestery has joined #openstack-meeting-alt20:10
*** banix has quit IRC20:12
*** rmoe has quit IRC20:12
*** rmoe has joined #openstack-meeting-alt20:13
*** minwang2 has joined #openstack-meeting-alt20:13
*** shashank_hegde has joined #openstack-meeting-alt20:14
*** kzaitsev_mb has quit IRC20:16
*** VW_ has joined #openstack-meeting-alt20:20
*** puranamr has quit IRC20:21
*** achanda has joined #openstack-meeting-alt20:22
*** achanda has quit IRC20:22
*** achanda has joined #openstack-meeting-alt20:23
*** bswartz has quit IRC20:24
*** achanda has quit IRC20:28
*** achanda has joined #openstack-meeting-alt20:28
*** jeadr has quit IRC20:29
*** jeadr has joined #openstack-meeting-alt20:29
*** geoffarnold has quit IRC20:30
*** geoffarnold has joined #openstack-meeting-alt20:30
*** nadya has quit IRC20:32
*** kfarr_ has quit IRC20:33
*** pballand has quit IRC20:33
*** VW_ has quit IRC20:35
*** VW_ has joined #openstack-meeting-alt20:35
*** kfarr has joined #openstack-meeting-alt20:37
*** pballand has joined #openstack-meeting-alt20:37
*** sputnik13 has quit IRC20:38
*** puranamr has joined #openstack-meeting-alt20:39
*** VW_ has quit IRC20:40
*** gyee has joined #openstack-meeting-alt20:43
*** esker has quit IRC20:47
*** warpc__ has quit IRC20:48
*** padkrish has quit IRC20:50
*** padkrish has joined #openstack-meeting-alt20:51
*** Sukhdev has quit IRC20:52
*** derekh has quit IRC20:52
*** devkulkarni has joined #openstack-meeting-alt20:54
*** padkrish has quit IRC20:55
*** mkam has joined #openstack-meeting-alt20:55
*** randallburt has joined #openstack-meeting-alt20:55
*** cdelatte has quit IRC20:57
*** xyang1 has quit IRC20:58
*** muralia has joined #openstack-meeting-alt20:59
devkulkarni#startmeeting Solum Team Meeting21:00
*** julim has quit IRC21:00
openstackMeeting started Tue Aug 18 21:00:16 2015 UTC and is due to finish in 60 minutes.  The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: Solum Team Meeting)"21:00
openstackThe meeting name has been set to 'solum_team_meeting'21:00
devkulkarni#link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-08-18_2100_UTC agenda for today21:00
*** gpilz1 has joined #openstack-meeting-alt21:00
devkulkarni#topic Roll Call21:00
*** openstack changes topic to "Roll Call (Meeting topic: Solum Team Meeting)"21:00
*** vgridnev has quit IRC21:00
devkulkarniDevdatta Kulkarni21:00
datsun180bEd Cranford21:00
muraliamurali allada21:00
gpilz1Gil Pilz21:00
mkamMelissa Kam21:01
devkulkarnihi ed, murali, gpilz, mkam21:01
devkulkarninice to see you all :)21:01
muraliahey all.21:01
devkulkarnitoday adrian_otto is out21:01
datsun180bright back at you21:01
devkulkarniplease take a few minutes to check our agenda21:02
devkulkarniI have mostly reviews to share/discuss today21:02
*** pnavarro has joined #openstack-meeting-alt21:02
devkulkarniI will go through the usual topics in any case21:02
*** jeadr has quit IRC21:02
devkulkarni#topic Announcements21:02
*** openstack changes topic to "Announcements (Meeting topic: Solum Team Meeting)"21:02
*** jeadr has joined #openstack-meeting-alt21:02
devkulkarniI don't have any21:02
randallburtoh hello there21:03
devkulkarnihi randallburt21:03
devkulkarniwe are just getting started21:03
randallburtk21:03
randallburtsorry for being late21:03
devkulkarninice to see you here21:03
devkulkarnino worries21:03
devkulkarnirandallburt here is the agenda link for today: https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2015-08-18_2100_UTC21:03
randallburtyep, caught up21:03
devkulkarnicool21:03
devkulkarniokay, since no announcements from anyone, moving on to next topic21:04
devkulkarni#topic Review Action Items21:04
*** openstack changes topic to "Review Action Items (Meeting topic: Solum Team Meeting)"21:04
*** stevemar has quit IRC21:05
*** _amrith_ is now known as amrith21:05
devkulkarnilast week there were no action items21:05
*** Aish has quit IRC21:05
devkulkarni#topic Blueprint/Task Review and Discussion21:06
*** openstack changes topic to "Blueprint/Task Review and Discussion (Meeting topic: Solum Team Meeting)"21:06
devkulkarniok, in this topic I have at least three subtopics21:06
*** vijendar has joined #openstack-meeting-alt21:06
devkulkarnihi vijendar21:06
vijendardevkulkarni: hi21:06
devkulkarnifolks please welcome vijendar to solum team meeting21:06
muraliahey hey welcome21:07
*** pnavarro has quit IRC21:07
vijendarthanks21:07
devkulkarnivijendar will be participating in solum related activities soon21:07
*** Aish has joined #openstack-meeting-alt21:07
randallburto/21:07
datsun180bcool21:07
*** Aish has left #openstack-meeting-alt21:07
devkulkarniok, so about review items..21:08
*** jckasper has quit IRC21:08
devkulkarnifirst one is this:21:08
devkulkarni(devkulkarni) Parsing ipv4 subnet-id from neutron. Please review (https://review.openstack.org/#/c/213854/2)21:08
devkulkarnilet me give bit of background on this one21:08
devkulkarniI was noticing that on devstack our app deployments had been failing with an error from heat21:08
devkulkarnito the effect 'bad floating-ip'21:08
devkulkarniand the floating-ip being reported was ipv6 ip21:09
*** puranamr has quit IRC21:09
devkulkarnithis was not a consistent error21:09
devkulkarniit was only ocassional21:09
devkulkarniafter debugging a bit I realized that the subnet-id that we are picking from neutron has to be for the ipv4 subnet21:10
*** amotoki has joined #openstack-meeting-alt21:10
devkulkarniin our code we were not checking this condition21:10
devkulkarnithe above patch adds this check21:10
devkulkarnirandallburt and muralia has reviewed it21:10
devkulkarniI need one more +2 on it21:10
devkulkarnirandallburt: good points on the patch21:10
randallburtthanks21:11
datsun180bi can look21:11
devkulkarnithanks to you actually :)21:11
devkulkarnidatsun180b: that will be helpful21:11
randallburtnp, muralia found it first, I just ran off at the mouth more :)21:11
muralia:)21:11
devkulkarnioh, okay21:11
devkulkarnithanks to muralia in that case (and also to you randallburt)21:11
devkulkarnigood to have you all keeping an eye on such things21:12
devkulkarniso datsun180b, take a look whenever you get a chance21:12
devkulkarnimoving on to the next one..21:12
devkulkarni(devkulkarni) Parsing IP address of server from Heat. Please review (https://review.openstack.org/#/c/213940/)21:12
devkulkarnisome background on this one..21:13
*** padkrish has joined #openstack-meeting-alt21:13
devkulkarniIn Solum we need the ip address of the server created by heat21:13
*** jian5397 has quit IRC21:13
devkulkarnithe parsing logic that we have implemented makes an assumption about the location of IP address. But turns out that that assumption is wrong.21:14
devkulkarniHeat returns two things as part of output_value — one is the IP address and another is the URL.21:14
randallburtyeah, never good to address outputs (or any key-value) by index in heat21:14
devkulkarniwe don't want to pick the URL because21:14
devkulkarniin Solum we construct the URL ourselves (we need to do that because..)21:15
*** amotoki has quit IRC21:15
devkulkarnian app may have multiple ports and we construct the url in the following format: http://<ip>:[port1, port2] etc.21:15
devkulkarnithis is by design.21:15
*** shwetaap has quit IRC21:15
devkulkarniso, we want to parse only the IP address from heat output21:16
*** stevemar has joined #openstack-meeting-alt21:16
devkulkarniand our current code was not checking whether what we are parsing is indeed the IP address or not21:16
devkulkarniso the above patch fixes this issue21:16
devkulkarnivijendar: you might want to take a look at this patch21:16
*** mrmartin has quit IRC21:17
*** jecarey has quit IRC21:17
devkulkarnirandallburt, muralia: thanks for your reviews on this patch21:17
vijendarI am looking at that patch now21:17
devkulkarnivijendar: cool21:17
*** shwetaap has joined #openstack-meeting-alt21:17
devkulkarnidatsun180b: if you get a chance please take a look at this one too21:17
devkulkarniit also needs one more +221:17
datsun180bpretty straightforward21:17
devkulkarnirandallburt: good point about not depending on the order of key-values21:18
devkulkarnibtw, both the above issues were cause of apps not getting deployed on devstack21:18
*** bharath_ has joined #openstack-meeting-alt21:18
*** pnavarro has joined #openstack-meeting-alt21:18
devkulkarnimkam, randallburt: do you think our rackspace deployment would have been occasionally failing due to this issue as well?21:19
*** puranamr has joined #openstack-meeting-alt21:19
randallburtdevkulkarni:  could be21:19
devkulkarniI think so too..21:19
randallburtas I said, never guaranteed to get the right output using just an index21:19
devkulkarniyeah.. should remember that21:19
*** bharath has quit IRC21:20
devkulkarnirandallburt: btw, thanks for suggesting to break up the review21:20
devkulkarnihopefully that helped in reviewing21:20
devkulkarniwhich brings me to the next item today..21:21
devkulkarni(devkulkarni) Workflow resource related patches. Please review.21:21
datsun180bthese will take a little more time21:21
devkulkarniyes..21:21
randallburtnice breakdown though21:21
devkulkarniso I broke up ed's WIP workflow patch into three patches21:21
devkulkarnirandallburt: thanks21:21
devkulkarniit was in anticipating your -1 to original patch :P21:22
randallburtlol21:22
devkulkarnion a serious note though.. the original workflow wip patch was about 400 lines21:22
devkulkarniwithout tests21:22
devkulkarniso I thought it will be good to just break it up into logical pieces21:23
* datsun180b whistles tuneless and avoids eye contact21:23
devkulkarnidatsun180b: he he.. actually your WIP has been tremendously helpful21:23
devkulkarnino need to avoid eye contact :)21:23
devkulkarnimuralia: I saw your comment about tests for the workflow_handler21:24
devkulkarniyes, I will add those21:24
devkulkarniright now I am in the middle of adding tests for the objects21:24
muraliacool. also, i added a lot of comments about using the app uuid instead of the app_id.21:24
devkulkarnioh right21:24
devkulkarniwanted to discuss about that21:24
*** jeadr has quit IRC21:24
devkulkarnigood that datsun180b is here too21:24
*** jeadr has joined #openstack-meeting-alt21:24
devkulkarniI remember it was a conscious decision by datsun180b to suggest that we use id instead of uuid21:25
devkulkarniwill be good to discuss that today21:25
devkulkarnidatsun180b, randallburt: thoughts?21:25
*** mestery has quit IRC21:25
devkulkarnihere are two points to consider21:25
datsun180bi think code inertia was one reason21:26
devkulkarni1) uuids does not help indexing, but they are unique21:26
*** pballand has quit IRC21:26
devkulkarni2) most of other solum objects have both id and uuid, and it has been sometimes confusing which one to use21:26
devkulkarnialthough in the api/cli it is clear that we prefer uuids21:27
devkulkarnilike rest of the openstack services21:27
muraliayes.21:27
devkulkarnifrom the cli point of view21:28
devkulkarniI think having uuids is conforming to other services21:28
datsun180bagreed21:28
devkulkarniso I think that would make sense21:28
*** saurabhs has joined #openstack-meeting-alt21:28
devkulkarnidatsun180b: was there some other reason that we did not add uuid to workflow models?21:29
randallburtsorry, was distracted. uuid21:29
randallburtits just how its done21:29
datsun180bdevkulkarni: they have a uuid, but the field's called id21:29
*** sputnik13 has joined #openstack-meeting-alt21:29
datsun180bat least i seem to recall that was the case at one point21:30
devkulkarnidatsun180b: oh I see.. but that will get confusing21:30
randallburtso why both? one is a database id and one is the resource "id"?21:30
*** jecarey has joined #openstack-meeting-alt21:30
muraliayes21:30
devkulkarnirandallburt: was about to ask that.. do we need both?21:30
datsun180bi don't think we do21:30
*** tonytan4ever has quit IRC21:30
datsun180bdoesn't do us much good to have the incrementing id21:30
randallburtin general, the resource key and what the user interacts with is called "id". If you have a separate identifier, it usually for db optimization of some sort or some other legacy hooey21:31
datsun180b^ so call it id, but make it uuid-shaped?21:31
randallburtin heat, some things have database ids so that we can return them in the order they came in (like events and such)21:31
devkulkarnihmm.. thinking about it more.. actually keeping the autoincrementing id as another field is not bad21:31
datsun180bworkflows should/will have a sequence id scoped to the parent app21:32
randallburtbut on the user-side, they all have uuid "id"s as far as the api is concerned21:32
randallburtso that should sort that then, datsun180b21:32
datsun180bright, i think you and i agree randall21:32
*** shwetaap has quit IRC21:32
devkulkarniwait..21:33
*** singleth_ has quit IRC21:33
devkulkarniare we saying that we will keep only one field in the workflow model — call it id, but which is shaped like uuid?21:33
*** sputnik13 has quit IRC21:33
*** dave-mcc_ has joined #openstack-meeting-alt21:33
devkulkarnior are we saying we will keep two fields21:33
datsun180bthat's what i thought i had in my wip21:33
devkulkarniid and uuid21:34
devkulkarnidatsun180b: but how could a uuid be used as a sequence id?21:34
datsun180bwell it can't21:34
datsun180bhttps://review.openstack.org/#/c/204164/3/solum/api/controllers/v1/datamodel/workflow.py does have id and uuid21:35
datsun180bmy memory's a little foggy about it i guess21:35
devkulkarniokay, yes I see both of them21:35
devkulkarniwhich makes sense21:35
devkulkarnilet me check back on the patches that I submitted21:35
devkulkarnimay be I missed having both in my patches21:36
*** stevemar has quit IRC21:36
datsun180bi guess keep them both, refer to them specifically in the code, but any time we ask a user for an "id" or give them an "id" it'll be 128 bits in hexadecimal21:36
devkulkarniyes, that makes sense21:36
*** dave-mccowan has quit IRC21:36
devkulkarnimuralia, randallburt: thoughts?21:36
datsun180bin the case of workflow we will need to maintain an order21:37
muraliasure. thats what we are doing with other resources too. i was hoping we can remove the id and then change the other resources to use only uuids later21:37
*** geoffarnold has quit IRC21:37
devkulkarnimuralia: I see. I think for indexing reasons it will be good to keep the ids around21:38
muraliaok.21:38
devkulkarnidatsun180b: what do you mean by need to maintain order for workflows for an app?21:39
devkulkarniwould be referring to "give me logs of the 3rd workflow for this app"?21:39
datsun180bright, that's the case21:39
devkulkarnior would we rather say — "give me logs of the workflow-id for this app"?21:39
datsun180bmy client wip covers both of those21:39
devkulkarnidatsun180b: I see.21:40
datsun180bthe idealized future included actions like "deploy the build from WF 35"21:40
devkulkarniin any case, as long as we have autoincrementing ids we should be able to satisfy the ordered indexing21:40
devkulkarnidatsun180b: yes.21:41
*** toscalix has joined #openstack-meeting-alt21:41
devkulkarnigreat discussion.. any more thoughts on this topic?21:41
datsun180bso your patches are intended to be merged i take it21:42
datsun180bthey're not wips, that is?21:42
devkulkarniwhich ones?21:42
devkulkarnithe workflow ones?21:42
devkulkarnithey are not yet ready ready21:42
devkulkarniI need to add tests21:42
datsun180bthe WF ones (the IP ones are merging already)21:42
*** tonytan4ever has joined #openstack-meeting-alt21:42
devkulkarniI can mark them as WIPs21:42
datsun180blikely a good idea21:42
devkulkarnidoing that now21:42
datsun180bi do want to mention that since my fingerprints are on them i don't know that i should give them any +2s21:43
devkulkarnidatsun180b: makes sense21:43
*** sileht has quit IRC21:43
devkulkarnijames_li is out today21:43
devkulkarnibut I will be reaching out to him for reviewing them21:43
*** dave-mccowan has joined #openstack-meeting-alt21:43
devkulkarnidatsun180b: btw, I marked your client patch as WIP21:44
devkulkarniso that we don't accidentally merge it21:44
*** amitgandhinz has quit IRC21:44
datsun180bsaw that. do you want me to keep the solum WIP up, or do you have what you need from it already?21:44
datsun180bthe client one still has its use21:45
devkulkarniI would like to have the solum WIP up just a bit longer21:45
*** shashank_hegde has quit IRC21:45
datsun180bthat's an easy wish to grant21:45
randallburtyou can abandon it and it won't go away21:45
devkulkarniit is easier to go back to check on things as everything is a single patch21:45
datsun180bgood point, randall21:45
*** dave-mcc_ has quit IRC21:46
devkulkarniany other reviews to discuss?21:46
devkulkarniI would have liked to discuss james_li's bash-to-python patches21:46
devkulkarnibut he is not around today21:47
devkulkarnirandallburt, vijendar: for those patches are are blocked on changes to config generator21:47
devkulkarnihave any ideas/insights on tackling the config generator issues?21:47
devkulkarniwe don't have to discuss it today though.. just wanted to check21:48
devkulkarnis/are are/we are/21:48
devkulkarnilets take that up when james_li is around21:49
devkulkarni#topic Open Discussion21:49
*** openstack changes topic to "Open Discussion (Meeting topic: Solum Team Meeting)"21:49
randallburtk. config generator is aweful and a bear to deal with21:49
randallburtso, who's excited about "blueprints" vs the other stuff we discussed for pluggable deployers?21:50
devkulkarnirandallburt: :) .. hopefully it won't be too much of an issue21:50
devkulkarnirandallburt: oh that's right21:50
*** pnavarro has quit IRC21:50
devkulkarniwe have that topic to discuss as well21:50
devkulkarnilet me refresh the options we have21:50
devkulkarniso everyone — we are discuss about this spec: https://review.openstack.org/#/c/202254/3/specs/liberty/deployer_plugins.rst21:51
randallburtblueprint, templates (boo!), layout, pattern, and something else21:51
devkulkarnithe issue is what to call the heat templates for different "architectural flavors" that solum will support21:51
datsun180bis it too late to propose "kung fu style"21:52
*** carl_baldwin has quit IRC21:52
gpilz1"crouching tiger"21:52
randallburtlol, winner21:53
datsun180b"snake in eagle's shadow"21:53
devkulkarnirandallburt: my objection to blueprint is that it also has a meaning in openstack ecosystem21:53
*** puranamr has quit IRC21:53
datsun180bi do agree that blueprint has a prior context21:53
randallburtdevkulkarni:  only to us developers. not to users21:53
*** jecarey has quit IRC21:53
devkulkarnisure.. what are your thoughts on 'topology'?21:53
datsun180bbarf21:53
randallburtoh yeah, that one. I like it less than blueprint21:54
devkulkarni#link https://review.openstack.org/#/c/202254/2/specs/liberty/deployer_plugins.rst21:54
gpilz1'schematic' ?21:54
devkulkarnicheck the comments21:54
devkulkarniarchitecture schematic?21:54
devkulkarniin that sense?21:54
gpilz1yeah21:54
datsun180bwell for serious topology is probably the most apt of the terms21:54
datsun180band it has the least amount of baggage21:55
devkulkarnidatsun180b: +1 and +121:55
randallburtin the end, we can bikeshed forever. lets pick topology as the least offensive and give it a go.21:55
devkulkarnirandallburt: agreed21:55
datsun180b+80 randallburt21:55
randallburtok, I'll update in the next few days and hopefully we can get it accepted21:55
devkulkarnirandallburt: awesome!! looking forward to it21:56
*** ashtokol_ has joined #openstack-meeting-alt21:56
devkulkarnirandallburt: on a related note.. jvrbanac recently was mentioning that he has a plugin library that is an improvement on stevedore21:56
devkulkarnijvrbanac: you around?21:56
devkulkarnilooks like jvrbanac is not around21:57
randallburtimo that's a debate for a patchset. I'm dubious as to what's been "improved" and what deficiencies if any are addressed.21:58
devkulkarnirandallburt: in any case, thought of mentioning it here as we were discussing about stevedore21:58
randallburtnot looking forward to library wars tbh21:58
devkulkarnirandallburt: fair enough21:58
randallburtcool. I look forward to the internet arguments :)21:58
devkulkarniha ha21:58
devkulkarnianything else for today?21:59
randallburtits time anyway21:59
devkulkarniyeah21:59
devkulkarnithanks all for joining today. great discussion today.22:00
devkulkarnisee you next week22:00
*** randallburt has left #openstack-meeting-alt22:00
devkulkarni#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Tue Aug 18 22:00:14 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/solum_team_meeting/2015/solum_team_meeting.2015-08-18-21.00.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/solum_team_meeting/2015/solum_team_meeting.2015-08-18-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/solum_team_meeting/2015/solum_team_meeting.2015-08-18-21.00.log.html22:00
*** matrohon has quit IRC22:00
*** datsun180b has quit IRC22:00
*** devkulkarni has left #openstack-meeting-alt22:01
*** absubram has quit IRC22:01
*** dprince has quit IRC22:02
*** minwang2 has quit IRC22:04
*** padkrish has quit IRC22:04
*** jungleboyj has quit IRC22:05
*** padkrish has joined #openstack-meeting-alt22:05
*** minwang2 has joined #openstack-meeting-alt22:05
*** shashank_hegde has joined #openstack-meeting-alt22:05
*** gyee has quit IRC22:06
*** sputnik13 has joined #openstack-meeting-alt22:07
*** padkrish has quit IRC22:09
*** Drago has joined #openstack-meeting-alt22:09
*** Drago has left #openstack-meeting-alt22:10
*** amotoki has joined #openstack-meeting-alt22:10
*** vijendar has quit IRC22:11
*** muralia has quit IRC22:11
*** dane_leblanc_ has quit IRC22:13
*** harshs has joined #openstack-meeting-alt22:13
*** amotoki has quit IRC22:15
*** agireud has quit IRC22:17
*** sputnik13 has quit IRC22:17
*** annegentle has quit IRC22:17
*** sigmavirus24 is now known as sigmavirus24_awa22:18
*** padkrish has joined #openstack-meeting-alt22:20
*** bswartz has joined #openstack-meeting-alt22:22
*** PeterS has joined #openstack-meeting-alt22:24
*** sputnik13 has joined #openstack-meeting-alt22:26
*** PeterSchwaller has quit IRC22:27
*** sputnik13 has quit IRC22:29
*** ivar-lazzaro has quit IRC22:30
*** jeadr has quit IRC22:30
*** jeadr has joined #openstack-meeting-alt22:30
*** shashank_hegde has quit IRC22:31
*** shashank_hegde has joined #openstack-meeting-alt22:33
*** mkam has quit IRC22:35
*** geoffarnold has joined #openstack-meeting-alt22:35
*** gpilz1 has quit IRC22:35
*** puranamr has joined #openstack-meeting-alt22:35
*** gpilz has joined #openstack-meeting-alt22:36
*** sputnik13 has joined #openstack-meeting-alt22:38
*** kfarr has quit IRC22:40
*** rmoe has quit IRC22:41
*** svinota has quit IRC22:43
*** ashleighfarnham has quit IRC22:44
*** VW_ has joined #openstack-meeting-alt22:46
*** baoli has joined #openstack-meeting-alt22:49
*** padkrish has quit IRC22:49
*** padkrish has joined #openstack-meeting-alt22:50
*** baoli has quit IRC22:53
*** VW_ has quit IRC22:53
*** VW_ has joined #openstack-meeting-alt22:54
*** padkrish has quit IRC22:54
*** tonytan4ever has quit IRC22:55
*** jungleboyj has joined #openstack-meeting-alt22:56
*** gpilz has left #openstack-meeting-alt22:56
*** VW_ has quit IRC22:59
*** dane_leblanc has joined #openstack-meeting-alt22:59
*** VW_ has joined #openstack-meeting-alt23:00
*** padkrish has joined #openstack-meeting-alt23:00
*** dane_leblanc has quit IRC23:01
*** dane_leblanc has joined #openstack-meeting-alt23:01
*** dane_leblanc_ has joined #openstack-meeting-alt23:02
*** VW_ has quit IRC23:05
*** VW_ has joined #openstack-meeting-alt23:05
*** dane_leblanc has quit IRC23:06
*** VW_ has quit IRC23:06
*** VW_ has joined #openstack-meeting-alt23:06
*** geoffarnold has quit IRC23:07
*** padkrish has quit IRC23:07
*** VW__ has joined #openstack-meeting-alt23:07
*** VW_ has quit IRC23:07
*** padkrish has joined #openstack-meeting-alt23:07
*** VW__ has quit IRC23:08
*** shashank_hegde has quit IRC23:08
*** annegentle has joined #openstack-meeting-alt23:08
*** VW_ has joined #openstack-meeting-alt23:08
*** annegentle has quit IRC23:09
*** annegentle has joined #openstack-meeting-alt23:10
*** shashank_hegde has joined #openstack-meeting-alt23:10
*** smccully has quit IRC23:11
*** harshs has quit IRC23:11
*** amotoki has joined #openstack-meeting-alt23:11
*** padkrish_ has joined #openstack-meeting-alt23:11
*** padkrish has quit IRC23:11
*** dimtruck is now known as zz_dimtruck23:13
*** zz_dimtruck is now known as dimtruck23:13
*** gyee has joined #openstack-meeting-alt23:15
*** rm_work is now known as rm_work|away23:15
*** puranamr has quit IRC23:16
*** priti_ has quit IRC23:16
*** amotoki has quit IRC23:16
*** kei_yama has joined #openstack-meeting-alt23:17
*** dims_ has joined #openstack-meeting-alt23:20
*** banix has joined #openstack-meeting-alt23:21
*** achanda has quit IRC23:22
*** dims has quit IRC23:22
*** dimtruck is now known as zz_dimtruck23:23
*** VW_ has quit IRC23:23
*** geoffarnold has joined #openstack-meeting-alt23:24
*** VW_ has joined #openstack-meeting-alt23:24
*** pballand has joined #openstack-meeting-alt23:24
*** pballand has quit IRC23:25
*** VW__ has joined #openstack-meeting-alt23:27
*** VW_ has quit IRC23:28
*** VW__ has quit IRC23:28
*** VW_ has joined #openstack-meeting-alt23:29
*** achanda has joined #openstack-meeting-alt23:30
*** achanda has quit IRC23:30
*** achanda has joined #openstack-meeting-alt23:31
*** puranamr has joined #openstack-meeting-alt23:35
*** jeadr has quit IRC23:37
*** padkrish_ has quit IRC23:42
*** jeadr has joined #openstack-meeting-alt23:43
*** padkrish has joined #openstack-meeting-alt23:43
*** toscalix has quit IRC23:44
*** jeadr has quit IRC23:46
*** padkrish has quit IRC23:47
*** rm_work|away is now known as rm_work23:47
*** jeadr has joined #openstack-meeting-alt23:47
*** geoffarnold has quit IRC23:49
*** geoffarnold has joined #openstack-meeting-alt23:49
*** ndipanov has joined #openstack-meeting-alt23:50
*** shashank_hegde has quit IRC23:51
*** snackewm has quit IRC23:52
*** ndipanov has quit IRC23:52
*** ndipanov has joined #openstack-meeting-alt23:52
*** SumitNaiksatam has quit IRC23:56
*** ndipanov has quit IRC23:59

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