Tuesday, 2016-01-12

*** dimtruck is now known as zz_dimtruck00:04
*** zz_dimtruck is now known as dimtruck00:05
*** ivar-lazzaro has quit IRC00:07
*** markmcclain has quit IRC00:09
*** markmcclain has joined #openstack-meeting-300:10
*** jmckind has joined #openstack-meeting-300:15
*** markvoelker has quit IRC00:20
*** irenab_ has joined #openstack-meeting-300:20
*** irenab has quit IRC00:23
*** irenab_ is now known as irenab00:23
*** banix has joined #openstack-meeting-300:24
*** ajmiller has quit IRC00:25
*** Sukhdev has quit IRC00:31
*** piet has joined #openstack-meeting-300:31
*** shakamunyi has quit IRC00:35
*** shakamunyi has joined #openstack-meeting-300:35
*** dimtruck is now known as zz_dimtruck00:36
*** dims_ has joined #openstack-meeting-300:39
*** markmcclain has quit IRC00:39
*** banix has quit IRC00:39
*** dims has quit IRC00:40
*** Sukhdev has joined #openstack-meeting-300:40
*** markmcclain has joined #openstack-meeting-300:42
*** rbak has joined #openstack-meeting-300:42
*** bpokorny_ has joined #openstack-meeting-300:45
*** stanchan has quit IRC00:45
*** stanchan has joined #openstack-meeting-300:46
*** hoangcx has joined #openstack-meeting-300:46
*** bpokorny has quit IRC00:49
*** stanchan has quit IRC00:51
*** stanchan has joined #openstack-meeting-300:51
*** stanchan has quit IRC00:51
*** hoangcx has quit IRC00:52
*** rbak has quit IRC00:53
*** woodster_ has quit IRC00:56
*** barra204 has joined #openstack-meeting-300:56
*** piet has quit IRC00:57
*** shakamunyi has quit IRC00:57
*** piet has joined #openstack-meeting-300:57
*** Sukhdev has quit IRC00:58
*** Swami has quit IRC00:59
*** dixiaoli has joined #openstack-meeting-301:00
*** kzaitsev_mb has quit IRC01:07
*** ivar-lazzaro has joined #openstack-meeting-301:08
*** kebray has joined #openstack-meeting-301:09
*** kebray has quit IRC01:11
*** hoangcx has joined #openstack-meeting-301:12
*** ivar-lazzaro has quit IRC01:13
*** barra204 has quit IRC01:14
*** shakamunyi has joined #openstack-meeting-301:15
*** vahidh has joined #openstack-meeting-301:17
*** markmcclain has quit IRC01:17
*** markvoelker has joined #openstack-meeting-301:21
*** markmcclain has joined #openstack-meeting-301:21
*** vahidh has quit IRC01:21
*** tfukushima has joined #openstack-meeting-301:22
*** rbak has joined #openstack-meeting-301:22
*** rbak has quit IRC01:24
*** markvoelker has quit IRC01:25
*** markvoelker has joined #openstack-meeting-301:25
*** barra204 has joined #openstack-meeting-301:31
*** shakamunyi has quit IRC01:32
*** spzala has joined #openstack-meeting-301:33
*** shakamunyi has joined #openstack-meeting-301:36
*** barra204 has quit IRC01:38
*** barra204 has joined #openstack-meeting-301:38
*** spzala has quit IRC01:38
*** tfukushima has quit IRC01:39
*** stanzgy has joined #openstack-meeting-301:39
*** shakamunyi has quit IRC01:39
*** tfukushima has joined #openstack-meeting-301:39
*** Sukhdev has joined #openstack-meeting-301:43
*** shakamunyi has joined #openstack-meeting-301:44
*** barra204 has quit IRC01:45
*** zz_dimtruck is now known as dimtruck01:47
*** dims_ has quit IRC01:48
*** shakamunyi has quit IRC01:48
*** dims has joined #openstack-meeting-301:48
*** shakamunyi has joined #openstack-meeting-301:49
*** tellesnobrega is now known as tellesnobrega_af01:50
*** baohua has joined #openstack-meeting-301:51
*** rbak has joined #openstack-meeting-301:51
*** markmcclain has quit IRC01:51
*** mtanino has quit IRC01:52
*** dims has quit IRC01:54
*** shakamunyi has quit IRC01:54
*** markmcclain has joined #openstack-meeting-301:55
*** rbak has quit IRC01:56
*** rbak has joined #openstack-meeting-301:58
*** ivar-lazzaro has joined #openstack-meeting-301:58
*** Sukhdev has quit IRC02:01
*** markmcclain has quit IRC02:03
*** piet has quit IRC02:04
*** jhesketh has quit IRC02:05
*** markmcclain has joined #openstack-meeting-302:05
*** jhesketh has joined #openstack-meeting-302:05
*** dims has joined #openstack-meeting-302:06
*** shakamunyi has joined #openstack-meeting-302:08
*** shakamunyi has quit IRC02:10
*** rbak has quit IRC02:10
*** shakamunyi has joined #openstack-meeting-302:12
*** bpokorny_ has quit IRC02:13
*** bpokorny has joined #openstack-meeting-302:14
*** markmcclain has quit IRC02:15
*** yamamoto has joined #openstack-meeting-302:17
*** markmcclain has joined #openstack-meeting-302:18
*** shakamunyi has quit IRC02:22
*** shakamunyi has joined #openstack-meeting-302:23
*** dimtruck is now known as zz_dimtruck02:24
*** baohua has quit IRC02:29
*** dixiaoli has quit IRC02:29
*** baohua has joined #openstack-meeting-302:29
*** dixiaoli has joined #openstack-meeting-302:29
*** Aish has quit IRC02:29
*** bpokorny_ has joined #openstack-meeting-302:30
*** banix has joined #openstack-meeting-302:31
*** yamamoto has quit IRC02:31
*** kzaitsev_mb has joined #openstack-meeting-302:32
*** shakamunyi has quit IRC02:32
*** bpokorny has quit IRC02:34
*** bpokorny_ has quit IRC02:35
*** yamamoto_ has joined #openstack-meeting-302:38
*** bharathm has quit IRC02:39
*** yamamoto_ has quit IRC02:40
*** davidmichaelkarr has quit IRC02:42
*** ivar-laz_ has joined #openstack-meeting-302:42
*** ivar-lazzaro has quit IRC02:46
*** spzala has joined #openstack-meeting-302:46
*** salv-orlando has quit IRC02:47
*** s3wong has quit IRC02:50
*** amotoki has joined #openstack-meeting-302:54
*** salv-orlando has joined #openstack-meeting-302:58
*** kevinbenton_ has joined #openstack-meeting-303:00
*** kevinbenton_ has quit IRC03:03
*** markmcclain has quit IRC03:04
*** bharathm has joined #openstack-meeting-303:04
*** MarkAtwood has quit IRC03:05
*** zz_dimtruck is now known as dimtruck03:06
*** markmcclain has joined #openstack-meeting-303:07
*** piet has joined #openstack-meeting-303:10
*** amotoki has quit IRC03:12
*** markmcclain has quit IRC03:12
*** amotoki has joined #openstack-meeting-303:14
*** kzaitsev_mb has quit IRC03:14
*** markmcclain has joined #openstack-meeting-303:18
*** spzala has quit IRC03:19
*** spzala has joined #openstack-meeting-303:20
*** ivar-laz_ has quit IRC03:20
*** sigmavirus24_awa is now known as sigmavirus2403:22
*** dims has quit IRC03:24
*** spzala has quit IRC03:25
*** markmcclain has quit IRC03:25
*** doug-fish has joined #openstack-meeting-303:30
*** Aish has joined #openstack-meeting-303:32
*** yamamoto_ has joined #openstack-meeting-303:33
*** amotoki has quit IRC03:36
*** piet has quit IRC03:38
*** tfukushima has quit IRC03:53
*** tfukushima has joined #openstack-meeting-303:55
*** doug-fish has quit IRC03:58
*** vahidh has joined #openstack-meeting-303:59
*** vahidh has quit IRC04:03
*** amotoki has joined #openstack-meeting-304:04
*** kevinbenton_ has joined #openstack-meeting-304:07
*** markmcclain has joined #openstack-meeting-304:09
*** salv-orl_ has joined #openstack-meeting-304:10
*** yamahata has quit IRC04:10
*** kzaitsev_mb has joined #openstack-meeting-304:11
*** salv-orlando has quit IRC04:13
*** markmcclain has quit IRC04:17
*** galstrom_zzz is now known as galstrom04:18
*** spzala has joined #openstack-meeting-304:20
*** spzala has quit IRC04:25
*** galstrom is now known as galstrom_zzz04:25
*** jmckind has quit IRC04:27
*** coolsvap|away is now known as coolsvap04:29
*** dimtruck is now known as zz_dimtruck04:29
*** tfukushima has quit IRC04:30
*** kzaitsev_mb has quit IRC04:32
*** piet has joined #openstack-meeting-304:38
*** galstrom_zzz is now known as galstrom04:45
*** galstrom is now known as galstrom_zzz04:51
*** MarkAtwood has joined #openstack-meeting-304:53
*** zz_dimtruck is now known as dimtruck04:55
*** MarkAtwood has quit IRC04:58
*** markvoelker has quit IRC04:58
*** baoli has quit IRC04:59
*** piet has quit IRC05:00
*** baoli has joined #openstack-meeting-305:00
*** stendulker has joined #openstack-meeting-305:01
*** kebray has joined #openstack-meeting-305:08
*** kebray has quit IRC05:09
*** dimtruck is now known as zz_dimtruck05:09
*** kebray has joined #openstack-meeting-305:10
*** sigmavirus24 is now known as sigmavirus24_awa05:18
*** markmcclain has joined #openstack-meeting-305:19
*** spzala has joined #openstack-meeting-305:22
*** spzala has quit IRC05:26
*** kzaitsev_mb has joined #openstack-meeting-305:28
*** banix has quit IRC05:32
*** Poornima has joined #openstack-meeting-305:33
*** tfukushima has joined #openstack-meeting-305:34
*** markmcclain has quit IRC05:34
*** vgridnev has joined #openstack-meeting-305:35
*** jmckind has joined #openstack-meeting-305:36
*** davidmichaelkarr has joined #openstack-meeting-305:40
*** mrmartin has joined #openstack-meeting-305:42
*** Aish has left #openstack-meeting-305:51
*** yamahata has joined #openstack-meeting-305:51
*** jmckind has quit IRC05:52
*** kzaitsev_mb has quit IRC05:57
*** markvoelker has joined #openstack-meeting-305:59
*** kevinbenton_ has quit IRC06:04
*** numans has joined #openstack-meeting-306:05
*** markvoelker has quit IRC06:06
*** mrmartin has quit IRC06:14
*** hoangcx has quit IRC06:17
*** rossella_s has quit IRC06:22
*** rossella_s has joined #openstack-meeting-306:22
*** spzala has joined #openstack-meeting-306:23
*** hoangcx has joined #openstack-meeting-306:26
*** spzala has quit IRC06:29
*** nkrinner has joined #openstack-meeting-306:29
*** MarkAtwood has joined #openstack-meeting-306:42
*** MarkAtwood has quit IRC06:47
*** salv-orl_ has quit IRC06:50
*** salv-orlando has joined #openstack-meeting-306:50
*** kzaitsev_mb has joined #openstack-meeting-306:53
*** tmazur has joined #openstack-meeting-306:55
*** kzaitsev_mb has quit IRC06:58
*** vgridnev has quit IRC07:05
*** kebray has quit IRC07:20
*** dedery has joined #openstack-meeting-307:21
*** dedery has quit IRC07:22
*** dedery has joined #openstack-meeting-307:22
*** spzala has joined #openstack-meeting-307:25
*** vgridnev has joined #openstack-meeting-307:35
*** safchain has joined #openstack-meeting-307:38
*** e0ne has joined #openstack-meeting-307:42
*** belmoreira has joined #openstack-meeting-307:53
*** kzaitsev_mb has joined #openstack-meeting-307:54
*** klkumar has joined #openstack-meeting-307:54
*** jtomasek has joined #openstack-meeting-307:57
*** kzaitsev_mb has quit IRC07:59
*** vgridnev has quit IRC08:00
*** spzala has quit IRC08:00
*** salv-orl_ has joined #openstack-meeting-308:01
*** salv-orlando has quit IRC08:05
*** salv-orl_ has quit IRC08:06
*** jed56 has joined #openstack-meeting-308:08
*** hdaniel_ has joined #openstack-meeting-308:09
*** matrohon has joined #openstack-meeting-308:12
*** e0ne has quit IRC08:16
*** baohua has quit IRC08:18
*** eliqiao has quit IRC08:18
*** baohua has joined #openstack-meeting-308:19
*** mrmartin has joined #openstack-meeting-308:24
*** spzala has joined #openstack-meeting-308:27
*** bryan_att has quit IRC08:29
*** kzaitsev_mb has joined #openstack-meeting-308:34
*** markmcclain has joined #openstack-meeting-308:41
*** markmcclain has quit IRC08:45
*** jlanoux has joined #openstack-meeting-308:47
*** jlanoux has quit IRC08:48
*** jlanoux has joined #openstack-meeting-308:48
*** vgridnev has joined #openstack-meeting-308:50
*** yamahata has quit IRC08:51
*** yamahata has joined #openstack-meeting-308:52
*** spzala has quit IRC08:55
*** belmoreira has quit IRC09:01
*** mbound has joined #openstack-meeting-309:01
*** amotoki has quit IRC09:05
*** dtardivel has joined #openstack-meeting-309:06
*** amotoki has joined #openstack-meeting-309:07
*** amotoki has quit IRC09:07
*** spzala has joined #openstack-meeting-309:09
*** spzala has quit IRC09:14
*** salv-orlando has joined #openstack-meeting-309:19
*** davidsha has joined #openstack-meeting-309:20
*** kzaitsev_mb has quit IRC09:21
*** shwetaap has joined #openstack-meeting-309:22
*** kzaitsev_mb has joined #openstack-meeting-309:23
*** yamahata has quit IRC09:27
*** kzaitsev_mb has quit IRC09:28
*** egallen has joined #openstack-meeting-309:34
*** tmazur has quit IRC09:39
*** dixiaoli has quit IRC09:41
*** e0ne has joined #openstack-meeting-309:48
*** salv-orlando has quit IRC09:51
*** mrmartin has quit IRC09:51
*** leonstudio has joined #openstack-meeting-309:51
*** liangy has quit IRC09:52
*** rossella_s has quit IRC09:53
*** dixiaoli has joined #openstack-meeting-309:53
*** vishwana_ has joined #openstack-meeting-309:54
*** baoli_ has joined #openstack-meeting-309:54
*** vishwanathj has quit IRC09:56
*** baoli has quit IRC09:56
*** salv-orlando has joined #openstack-meeting-309:57
*** amotoki has joined #openstack-meeting-309:59
*** bharathm has quit IRC10:02
*** rossella_s has joined #openstack-meeting-310:02
*** markvoelker has joined #openstack-meeting-310:02
*** markvoelker has quit IRC10:07
*** eliqiao has joined #openstack-meeting-310:08
*** eliqiao has quit IRC10:09
*** salv-orlando has quit IRC10:10
*** eliqiao has joined #openstack-meeting-310:10
*** hoangcx has quit IRC10:15
*** rossella_s has quit IRC10:15
*** dixiaoli has quit IRC10:19
*** rossella_s has joined #openstack-meeting-310:22
*** JeanBriceCombebi has joined #openstack-meeting-310:23
*** kzaitsev_mb has joined #openstack-meeting-310:27
*** salv-orlando has joined #openstack-meeting-310:28
*** salv-orlando has quit IRC10:28
*** mrmartin has joined #openstack-meeting-310:29
*** kzaitsev_mb has quit IRC10:32
*** kzaitsev_mb has joined #openstack-meeting-310:42
*** JeanBriceCombebi has quit IRC10:44
*** JeanBriceCombebi has joined #openstack-meeting-310:46
*** tfukushima has quit IRC10:48
*** baoli has joined #openstack-meeting-310:52
*** stanzgy has quit IRC10:52
*** baoli_ has quit IRC10:55
*** egallen has quit IRC10:56
*** coolsvap is now known as coolsvap|away10:56
*** stendulker has quit IRC10:57
*** dims has joined #openstack-meeting-311:05
*** tfukushima has joined #openstack-meeting-311:08
*** tfukushima has quit IRC11:10
*** spzala has joined #openstack-meeting-311:10
*** spzala has quit IRC11:15
*** MarkAtwood has joined #openstack-meeting-311:15
*** MarkAtwood has quit IRC11:19
*** egallen has joined #openstack-meeting-311:28
*** jlanoux has quit IRC11:29
*** jlanoux has joined #openstack-meeting-311:30
*** irenab has quit IRC11:31
*** irenab has joined #openstack-meeting-311:32
*** kzaitsev_mb has quit IRC11:41
*** baohua has quit IRC11:41
*** amotoki has quit IRC11:46
*** jlanoux_ has joined #openstack-meeting-311:47
*** jlanoux has quit IRC11:47
*** JeanBriceCombebi has quit IRC11:47
*** salv-orl_ has joined #openstack-meeting-311:49
*** amotoki has joined #openstack-meeting-311:50
*** JeanBriceCombebi has joined #openstack-meeting-311:52
*** ihrachys has joined #openstack-meeting-311:54
*** JeanBriceCombebi has quit IRC11:57
*** amotoki has quit IRC12:02
*** markvoelker has joined #openstack-meeting-312:03
*** shwetaap1 has joined #openstack-meeting-312:05
*** mrmartin has quit IRC12:06
*** kzaitsev_mb has joined #openstack-meeting-312:07
*** mrmartin has joined #openstack-meeting-312:08
*** markvoelker has quit IRC12:08
*** shwetaap has quit IRC12:08
*** vgridnev has quit IRC12:10
*** vgridnev has joined #openstack-meeting-312:10
*** mrmartin has quit IRC12:11
*** spzala has joined #openstack-meeting-312:11
*** spzala has quit IRC12:16
*** irenab has quit IRC12:17
*** eliqiao has quit IRC12:24
*** eliqiao has joined #openstack-meeting-312:25
*** rtheis has joined #openstack-meeting-312:26
*** vgridnev has quit IRC12:30
*** berendt1 has joined #openstack-meeting-312:30
*** irenab has joined #openstack-meeting-312:30
*** berendt has joined #openstack-meeting-312:33
*** berendt1 has quit IRC12:35
*** vgridnev has joined #openstack-meeting-312:41
*** d0ugal has quit IRC12:42
*** d0ugal has joined #openstack-meeting-312:43
*** d0ugal is now known as Guest5838512:43
*** salv-orl_ has quit IRC12:43
*** Guest58385 is now known as d0ugal12:45
*** d0ugal has quit IRC12:45
*** d0ugal has joined #openstack-meeting-312:45
*** davidsha has quit IRC12:47
*** rbak has joined #openstack-meeting-312:51
*** rbak has quit IRC12:57
*** vladik-train has joined #openstack-meeting-312:58
berendt#startmeeting docinstallteam13:01
openstackMeeting started Tue Jan 12 13:01:06 2016 UTC and is due to finish in 60 minutes.  The chair is berendt. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: docinstallteam)"13:01
openstackThe meeting name has been set to 'docinstallteam'13:01
*** vladik-train has left #openstack-meeting-313:01
berendt#action berendt create review request to re-schedule the US/EU meeting like discussed on the mailinglist13:02
*** MarkAtwood has joined #openstack-meeting-313:03
*** markvoelker has joined #openstack-meeting-313:04
*** shakamunyi has joined #openstack-meeting-313:04
berendt#endmeeting13:05
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:05
openstackMeeting ended Tue Jan 12 13:05:24 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-01-12-13.01.html13:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-01-12-13.01.txt13:05
openstackLog:            http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-01-12-13.01.log.html13:05
*** berendt has left #openstack-meeting-313:05
*** vladik-train has joined #openstack-meeting-313:07
*** baoli has quit IRC13:08
*** MarkAtwood has quit IRC13:08
*** baoli has joined #openstack-meeting-313:09
*** vladik-train has left #openstack-meeting-313:09
*** spzala has joined #openstack-meeting-313:12
*** markvoelker has quit IRC13:15
*** spzala has quit IRC13:17
*** JeanBriceCombebi has joined #openstack-meeting-313:30
*** sigmavirus24_awa is now known as sigmavirus2413:31
*** Poornima has quit IRC13:32
*** markvoelker has joined #openstack-meeting-313:35
*** msagheer has joined #openstack-meeting-313:38
*** msagheer has left #openstack-meeting-313:38
*** eliqiao_ has joined #openstack-meeting-313:39
*** rbak has joined #openstack-meeting-313:40
*** sigmavirus24 is now known as sigmavirus24_awa13:40
*** shaohe_feng has joined #openstack-meeting-313:41
*** eliqiao has quit IRC13:41
*** tmazur has joined #openstack-meeting-313:42
*** dslev has joined #openstack-meeting-313:42
*** hdaniel_ has quit IRC13:42
*** eliqiao_ is now known as eliqiao13:42
*** qwebirc20169 has joined #openstack-meeting-313:44
*** hichihara has joined #openstack-meeting-313:49
*** davidgiluk has joined #openstack-meeting-313:52
*** davidsha has joined #openstack-meeting-313:53
*** PaulMurray has joined #openstack-meeting-313:54
*** huats has quit IRC13:55
*** huats has joined #openstack-meeting-313:56
*** tdurakov has joined #openstack-meeting-313:56
*** JeanBriceCombebi has quit IRC13:57
*** andrearosa has joined #openstack-meeting-314:00
PaulMurray#startmeeting Nova Live Migration14:00
openstackMeeting started Tue Jan 12 14:00:16 2016 UTC and is due to finish in 60 minutes.  The chair is PaulMurray. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** qwebirc20169 has quit IRC14:00
*** openstack changes topic to " (Meeting topic: Nova Live Migration)"14:00
openstackThe meeting name has been set to 'nova_live_migration'14:00
tdurakovhi14:00
andrearosahi14:00
shaohe_fenghi14:00
PaulMurrayHi all14:00
PaulMurrayjust wait around a minute to see if any else comes14:01
davidgilukhi14:01
eliqiaoo/14:01
*** kashyap has joined #openstack-meeting-314:01
PaulMurrayThe agenda is on the meeting page: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration14:02
jlanoux_o/14:02
PaulMurrayI have been ill so I only got round to putting the agenda up a while ago14:02
*** dslev has quit IRC14:02
tdurakovPaulMurray, could you add ci for agenda please14:03
*** paul-carlton2 has joined #openstack-meeting-314:03
PaulMurraytdurakov, yes, certainly14:03
PaulMurrayIn fact lets do that first14:03
*** dandruta has joined #openstack-meeting-314:03
PaulMurray#topic CI14:03
*** openstack changes topic to "CI (Meeting topic: Nova Live Migration)"14:03
tdurakovcurrent status: https://review.openstack.org/#/c/252283/14:04
tdurakovthis patch add ceph for hook14:04
tdurakovreview and merge needed14:04
PaulMurray#action ALL please review  https://review.openstack.org/#/c/252283/14:05
eliqiaoseems all logic are in run_tests.sh, would that be better to split it out?14:06
* PaulMurray the internet is being a little slow for me today14:06
tdurakoveliqiao, sounds reasonable14:06
tdurakoveliqiao, check Sebastien comment also14:07
*** mtanino has joined #openstack-meeting-314:07
eliqiaooh, gold, already version 73,  I am so late14:07
* eliqiao :(s/gold/god14:08
PaulMurrayI was going to mention this in the next topic: https://review.openstack.org/#/c/227278/ failed the live migration CI14:08
pkoniszewskio/14:08
tdurakoveliqiao, it could be splitted, Sebastien talking about reusing ceph from devstack/lib14:09
*** JeanBriceCombebi has joined #openstack-meeting-314:09
pkoniszewskiPaulMurray: its already fixed14:09
eliqiaotdurakov: cool.14:09
PaulMurraypkoniszewski, was that the live migration job or the review at fault?14:09
*** neelashah has joined #openstack-meeting-314:10
tdurakovPaulMurray, what ps number?14:10
PaulMurray2514:10
*** salv-orlando has joined #openstack-meeting-314:11
*** yamamoto_ has quit IRC14:11
*** piet has joined #openstack-meeting-314:11
PaulMurraypkoniszewski, from your comment:14:11
PaulMurrayI'm currently investigating it, but so far it looks like this fail is not related to my changes. Tests without NFS worked correctly:14:11
PaulMurraytempest.api.compute.admin.test_live_migration.LiveBlockMigrationTestJSON.test_live_block_migration [66.216203s] ... ok14:11
PaulMurraytempest.api.compute.admin.test_live_migration.LiveBlockMigrationTestJSON.test_live_block_migration_paused [19.978373s] ... ok14:11
PaulMurrayWith NFS one test passed and another one failed:14:11
PaulMurraytempest.api.compute.admin.test_live_migration.LiveBlockMigrationTestJSON.test_live_block_migration [15.971409s] ... FAILED14:11
PaulMurraytempest.api.compute.admin.test_live_migration.LiveBlockMigrationTestJSON.test_live_block_migration_paused [18.673453s] ... ok14:11
PaulMurrayLet's see the result on BLM with config drive patch14:12
*** vhoward has joined #openstack-meeting-314:12
pkoniszewskiPaulMurray: looks to me like it was a test issue, but Matt found another issue in another patch, no idea right now which one caused this14:12
pkoniszewskiI can see in my environment that everything works fine now14:12
pkoniszewskiso I pushed another patch14:12
PaulMurrayI saw that the config drive patch passed14:13
*** krtaylor has quit IRC14:13
*** quintela has joined #openstack-meeting-314:13
PaulMurrayso as we are discussing it.....14:13
PaulMurray#topic Priority reviews14:13
*** openstack changes topic to "Priority reviews (Meeting topic: Nova Live Migration)"14:13
PaulMurraypkoniszewski, how is that series going?14:14
PaulMurrayyou got one merged14:14
*** julim has joined #openstack-meeting-314:14
pkoniszewskiThere is one concern from Daniel, but its just naming issue in old dicts, I need to dump data and respond to his review14:15
pkoniszewskiconfig drive patch is ready14:15
PaulMurray#link https://review.openstack.org/#/q/topic:bp/block-live-migrate-with-attached-volumes14:16
PaulMurrayok - we'll keep looking to review it14:16
PaulMurrayThe next one I wanted to call out was14:16
PaulMurray#link https://review.openstack.org/#/q/topic:bp/pause-vm-during-live-migration14:17
*** spzala has joined #openstack-meeting-314:17
pkoniszewskiso I need to go through code carefuly to see how andrearosa's proposition would work14:17
pkoniszewskiprobably they are right and we can move logic down to drivers14:17
andrearosapkoniszewski: feel free to ping me if my comments are not clear14:18
pkoniszewskimy idea was to keep this at a high level (compute api) to be able to throw correct instance action14:18
*** jmckind has joined #openstack-meeting-314:18
pkoniszewskithis is async so there is no other option to notify about which action is taken at a lower level, or I don't know something about nova's notifications14:19
*** amotoki has joined #openstack-meeting-314:20
*** amotoki has quit IRC14:21
*** spzala has quit IRC14:21
*** rossella_s has quit IRC14:22
*** ajmiller has joined #openstack-meeting-314:22
*** rossella_s has joined #openstack-meeting-314:22
*** PaulMurray has quit IRC14:23
*** zz_dimtruck is now known as dimtruck14:23
pkoniszewskiPaulMurray timed out :<14:23
eliqiao:(14:23
pkoniszewskilet's move forward, not sure we will be able to finish the meeting or add links and so on14:24
pkoniszewski#topic Bugs14:24
*** krtaylor has joined #openstack-meeting-314:24
pkoniszewskinah, it doesn't listen :<14:24
pkoniszewskiso just a kindly reminder that we are tracking bugs in etherpad - https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking14:24
*** JeanBriceCombebi has quit IRC14:25
pkoniszewskimost of them need reviews14:25
*** qwebirc31188 has joined #openstack-meeting-314:25
eliqiaoyeah, hard work14:26
pkoniszewskithere is a new series to deprecate migration flags config14:26
kashyappkoniszewski: Randomly chiming in, yeah, it avoids a lot of confusion14:26
*** mtanino has quit IRC14:26
eliqiaopkoniszewski: I see, Dansims gives +2 on them.14:26
kashyapBecause, there are a lot of flags and tunables that libvirt allows, unless one really has tested all them, it's hard to remember which combination is suitable.14:27
pkoniszewskiso every review right now is appreciated, we are getting close to midcycle, I believe that we will be able to work on some changes and merge some of them at the midcycle14:27
eliqiaopkoniszewski: seems they are all in high prority, get cores' eyes already.14:27
pkoniszewskikashyap: exactly, this series will remove a lot of confusions around LM configuration and will give nova more flexibility to configure it on correctly14:28
pkoniszewskia lot of patches are very close14:28
kashyapYeah, the bug that triggered it all - https://bugs.launchpad.net/nova/+bug/144105414:29
openstackLaunchpad bug 1441054 in OpenStack Compute (nova) "live-migration --block-migrate fails with default libvirt flags" [Medium,Incomplete] - Assigned to Mathieu Rohon (mathieu-rohon)14:29
*** tellesnobrega_af is now known as tellesnobrega14:29
*** peristeri has joined #openstack-meeting-314:29
*** qwebirc31188 has left #openstack-meeting-314:29
pkoniszewskiandrearosa: do you know what Paul wanted to say about midcycle?14:29
kashyapIn the time the bug was reported, and now, the said issue seems to be fixed there.14:29
pkoniszewskiit starts in a less than 2 weeks14:30
andrearosapkoniszewski: nope he is not in the office, I guess he just want to start to discuss about some topics we want to put in the agenda for the meetup14:30
pkoniszewskiokay, so here is the etherpad for midcycle - https://etherpad.openstack.org/p/mitaka-nova-midcycle14:31
eliqiaopkoniszewski: thx, we should file something for LM14:32
pkoniszewskilive migration will be discussed on Tuesday14:32
*** PaulMurray has joined #openstack-meeting-314:32
* andrearosa is trying to reach PaulMurray on different channels14:32
PaulMurrayHi, am I back in?14:32
pkoniszewskiPaulMurray:  is bad14:32
pkoniszewskiback *14:32
pkoniszewskisorry14:32
pkoniszewski:D14:32
*** jpomeroy has joined #openstack-meeting-314:33
eliqiaopkoniszewski: will you attend mid-cycle?14:33
PaulMurraySeems I got disconnected14:33
pkoniszewskiPaulMurray: we moved forward to midcycle, just started this topic and mentioned about etherpad14:33
PaulMurraycool14:33
pkoniszewskieliqiao: yes, I will participate14:33
eliqiaopkoniszewski: cool.14:34
*** dimtruck is now known as zz_dimtruck14:34
PaulMurraytdurakov, did you get your visa?14:34
*** ajmiller has quit IRC14:34
tdurakovPaulMurray, yep, will attend mid-cycle14:34
PaulMurraygreat - there's a reasonable turn out all round14:35
PaulMurraythere will be several people who work on libvirt and qemu there14:35
*** lblanchard has joined #openstack-meeting-314:35
PaulMurrayso its a good time to bring up anything needed there14:35
tdurakovgreat!14:35
tdurakovpkoniszewski, could we discuss your patch and ci failure after this meeting?14:36
pkoniszewskitdurakov: sure!14:36
*** jmckind_ has joined #openstack-meeting-314:36
PaulMurrayThere are a few virt layer items at the bottom of our eatherpad14:37
PaulMurrayplease add there if there is anything that I haven't included14:37
PaulMurraysee: https://etherpad.openstack.org/p/mitaka-live-migration14:37
PaulMurrayLive Migration Libvirt / qemu Work Items14:37
PaulMurrayThis is to do with lining up work we may depend on in the future14:38
PaulMurraythe people coming may be able to take some on14:38
*** dslev has joined #openstack-meeting-314:39
PaulMurray#topic open discussion14:39
*** openstack changes topic to "open discussion (Meeting topic: Nova Live Migration)"14:39
PaulMurrayAnything anyone wants to discuss?14:39
pkoniszewskiI see that there is series about deprecating migration flags in open discussion14:39
*** jmckind has quit IRC14:39
pkoniszewskiis owner of the series there?14:40
PaulMurrayI don't think so14:40
*** amotoki has joined #openstack-meeting-314:40
PaulMurrayits markmc14:40
*** apevec has joined #openstack-meeting-314:41
PaulMurraypkoniszewski, did you follow the thread?14:42
tdurakovdo we really need such constraint for operators?14:42
*** salv-orlando has quit IRC14:42
pkoniszewskiyes, I did14:42
*** hichihara has quit IRC14:42
*** hichihara has joined #openstack-meeting-314:42
pkoniszewskitdurakov: what do you mean?14:43
eliqiaohiden flgs from admin14:43
tdurakoveliqiao, yep14:43
pkoniszewskiwell, I don't think that there is reason to expose all these flags that we currently expose to operators14:44
pkoniszewskiwe allow them, e.g., to misconfigure nova14:44
eliqiaoI commented to have a log for flags.14:44
*** JeanBriceCombebi has joined #openstack-meeting-314:44
tdurakovfrom my sight it should be enough to have warning in logs14:44
eliqiaomarkmc told it's hard to convert from bit to string.. and also havs warings..14:44
*** ptm_ has joined #openstack-meeting-314:45
*** ptm_ has quit IRC14:45
eliqiaotdurakov: hmm.. that would be not easy to findout all flags14:45
tdurakove.x. what about post-copy mode for live-migration?14:45
*** spzala has joined #openstack-meeting-314:45
*** neiljerram has joined #openstack-meeting-314:45
*** ptm_ has joined #openstack-meeting-314:45
*** woodster_ has joined #openstack-meeting-314:46
pkoniszewskidepends how it will impact performance of different workloads14:46
*** PaulMurray has quit IRC14:46
*** ptm_ is now known as PaulMurray14:46
pkoniszewskiimo there should be another way to trigger post copy live migration, but I don't know much about its impact yet14:46
davidgilukpkoniszewski: What would you like to know14:46
*** kbyrne has quit IRC14:46
eliqiaoAdd a new switch flag to indicate to use post-copy or not, that what I can image onl.14:46
PaulMurrayok - got back in14:46
tdurakovpkoniszewski, afair we need to provide flag14:47
*** amotoki has quit IRC14:47
*** tellesnobrega is now known as tellesnobrega_af14:47
tdurakovso if wee hide flags from operator - we need to provide some flag in cli/rest-api14:47
tdurakovdo we really need this?)14:47
*** hichihara has quit IRC14:47
PaulMurray#chair andrearosa14:47
openstackCurrent chairs: PaulMurray andrearosa14:47
eliqiaoops. a new REST api ?14:48
pkoniszewskieliqiao: just a flag14:48
*** banix has joined #openstack-meeting-314:48
tdurakoveliqiao, if there is no way to change flags you need to change api14:48
pkoniszewskitdurakov: I just don't know in which case you would want to trigger only post-copy live migrations14:48
*** rossella_s has quit IRC14:48
pkoniszewskiI'm not a fan of all these static configurations in nova.conf14:48
*** dslev has quit IRC14:49
eliqiaopkoniszewski: add new options to live-migration CLI to passing flags, it make some scense to me.14:49
pkoniszewskithey are way too static for different kind of workloads and different sizes of VMs14:49
tdurakoveliqiao, yep, new options14:49
tdurakovbut we recently going to remove disk-over-commit option from cli, no?14:50
eliqiaotdurakov: cool, that's a good suggestion I think, (but maybe some one will say we don't need to expose low level details)14:50
pkoniszewskiits not used anymore afaik14:50
eliqiaotdurakov: yeah, that's what I am working on14:50
tdurakovit looks inconsistent imho14:51
tdurakovto hide one flag and then add new one14:51
pkoniszewskidavidgiluk: I would like to know how post-copy affects databases and comparison to pre-copy14:51
tdurakovbut yes, this need to be discussed more14:51
*** hichihara has joined #openstack-meeting-314:51
davidgilukpkoniszewski: OK, PM for a discussion about performance and stuff, but the 'howto use' it is you must select it before the start of migration14:52
davidgilukpkoniszewski: The simple answer is that with postcopy the migration always completes, irrespective of the workload14:52
*** rossella_s has joined #openstack-meeting-314:53
eliqiaodavidgiluk: do you konw the progress post-copy migration supported in libivrt, I don't find any patch about it.14:53
pkoniszewskithat's true, it ends in a finite time14:53
tdurakovdavidgiluk, tradeoff is no way to rollback it, right?14:53
eliqiaoyes, can not revert14:53
davidgilukeliqiao: jdenemar is currently tidying it up for posting, I need to sort out a couple of things for him on the qemu side14:53
PaulMurrayalso slower vm if have to fetch14:53
pkoniszewskitdurakov: yes, and in case of network failure you will need to reboot VM14:53
PaulMurrayalot14:53
davidgiluktdurakov: Right, once it's in postcopy mode you can't abandon the migrate since the destination has started writing to disk and sending packets etc14:53
*** salv-orlando has joined #openstack-meeting-314:54
davidgilukPaulMurray: Right, although normally the postcopy phase is only a short part of it, so that finishes pretty quickly14:54
eliqiaodavidgiluk: seems we are far away to support post-migration since it's not merged in libvirt yet?14:55
tdurakovfrom my sight post-copy is one of examples where we need to decide, re we going to hide flags from conf and add extra cli/api params, or leave conf as-is14:56
davidgilukeliqiao: not merged in libvirt yet, but reasonably close; there's also a demo that Umea uni have of an implementation on openstack14:56
*** salv-orlando has quit IRC14:56
pkoniszewskieliqiao: per my discussion with Daniel its very close and it's real to get it done in N/O-release of OpenStack14:56
*** salv-orlando has joined #openstack-meeting-314:56
eliqiaopkoniszewski: do you mean in libvirt?14:57
*** mriedem has joined #openstack-meeting-314:57
pkoniszewskitdurakov: we can just say in nova.conf that all live migrations will be post-copy or all live migrations will be pre-copy14:57
*** jmckind has joined #openstack-meeting-314:57
pkoniszewskitdurakov: it's way too static14:57
davidgilukpkoniszewski: Yeh that's way too static14:57
pkoniszewskitdurakov: so I strongly prefer to remove these flags from nova.conf, we need better approach14:57
andrearosapkoniszewski: you meant we can't14:57
*** hichihara has quit IRC14:58
pkoniszewskiandrearosa: yes, I meant that we can :D14:58
pkoniszewskican't...14:58
tdurakov:)14:58
*** dslev has joined #openstack-meeting-314:58
andrearosaok, thanks14:58
eliqiaoalmost done, sorry to interupt, can anyone help to review this topic #link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/making-live-migration-api-friendly14:58
PaulMurrayWe are coming to the end of time14:58
pkoniszewskiPaulMurray: just one more question14:58
*** hichihara has joined #openstack-meeting-314:58
PaulMurrayyes14:58
pkoniszewskiPaulMurray: will we discuss LM agenda for midcycle before midcycle?14:58
eliqiaoPaulMurray: that one is not discuess last week(I missed), just hight light14:58
pkoniszewskilike, next week or on a mailing list?14:58
*** jmckind_ has quit IRC14:59
PaulMurrayI tried to discuss it today when I got dropped14:59
PaulMurrayI'll put an eatherpad link on the live migration link14:59
PaulMurrayand we can list items there15:00
PaulMurraythen go over next week15:00
PaulMurraysound ok?15:00
PaulMurrayI'll send an email15:00
pkoniszewskisounds good!15:00
pkoniszewskithanks15:00
PaulMurray#endmeeting15:00
shaohe_fengpkoniszewski:  is there a config sample  with optimal options config that suits to most common live migration scenario?15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Tue Jan 12 15:00:32 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_live_migration/2016/nova_live_migration.2016-01-12-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_live_migration/2016/nova_live_migration.2016-01-12-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_live_migration/2016/nova_live_migration.2016-01-12-14.00.log.html15:00
*** andrearosa has left #openstack-meeting-315:00
PaulMurraysorry, time to stop - bye everyone15:00
PaulMurrayI will try to get a better connection next tiem15:01
*** jlanoux_ has quit IRC15:01
mriedem#startmeeting stable15:01
openstackMeeting started Tue Jan 12 15:01:25 2016 UTC and is due to finish in 60 minutes.  The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: stable)"15:01
ttxo/15:01
openstackThe meeting name has been set to 'stable'15:01
*** hichihara has quit IRC15:01
mriedemhi, who is all here (besides ttx)?15:01
*** jlanoux has joined #openstack-meeting-315:01
ihrachyso/15:01
mriedemmtreinish: tonyb?15:02
*** hichihara has joined #openstack-meeting-315:02
* ihrachys attends two meetings, can lag15:02
*** markmcclain has joined #openstack-meeting-315:02
*** PaulMurray has quit IRC15:02
mriedemi'll give it another minute or so15:02
*** davidgiluk has left #openstack-meeting-315:02
*** doug-fish has joined #openstack-meeting-315:02
anteayaI can lurk if that is helpful to numbers15:03
mriedemit does15:03
anteayayay15:03
mriedemwell let's just get started15:03
* anteaya is useful today15:03
*** mfranc213 has joined #openstack-meeting-315:03
mriedem#link agenda https://wiki.openstack.org/wiki/Meetings/StableTeam15:03
mriedem#topic status15:03
*** openstack changes topic to "status (Meeting topic: stable)"15:03
*** jrist has quit IRC15:03
mriedemperiodic-stable failures http://goo.gl/5qiw2U15:03
*** markmcclain has quit IRC15:03
mriedemthere are really just 2 issues with those15:03
*** markmcclain1 has joined #openstack-meeting-315:03
mriedem1. neutron-*aas jobs aren't getting the branch set in the periodic-stable jobs properly15:04
*** mtanino has joined #openstack-meeting-315:04
*** markmcclain1 is now known as markmcclain15:04
mriedemihrachys: proposed https://review.openstack.org/#/c/245525/ and tonyb is picking it up15:04
ihrachystonyb++15:04
mriedem2. ceilomer dsvm job is having issues setting the branch for gnocchi https://review.openstack.org/#/c/264769/15:05
mriedemgordc is playing d-g whack a mole with that one15:05
*** salv-orl_ has joined #openstack-meeting-315:05
mriedembasically, d-g is trying to clone stable/liberty gnocchi which doesn't exist, so he has to override the branch that d-g pulls for that job15:05
mriedemi'm hoping sdague and mtreinish can review that one15:05
*** salv-orlando has quit IRC15:05
mriedemthat's it for the periodic-stable jobs15:05
ttxthe dashboard shows horizon issues as well ?15:06
mriedemthe openstack-health one?15:06
mriedemoh, that was last week15:06
ttxno the link you pointed us to15:06
ttxoh ok15:06
mriedemyeah, last week was the kilo + liberty fubar15:06
mriedemwhere horizon wouldn't install in dsvm on kilo15:06
mriedemwhich broke all of kilo dsvm and liberty grenade jobs15:06
mriedemthat was fixed last week15:06
mriedemi should probably adjust that logstash link to 2 days rather than 7 maybe15:07
sdaguemriedem: I just approved it, I do think that the gnocchi story here tells a more important release concept that mixing independent release components with integrated release components just makes for pain15:07
anteayasing it15:07
mriedemwell15:08
mriedembig tent everyone releases on their own schedule, so theoretically this should be fine right?15:08
sdagueas long as they don't want to have linked jobs15:08
mriedemgnocchi is a library isn't it?15:08
sdagueit's the linked jobs that's the issue15:08
mriedemyeah15:08
mriedemi guess if ceilometer just pulled down a pip of gnocchi from pypi then it wouldn't be a problem15:09
ttxsdague: maybe we should make that more obvious in the doc where we explain both choices15:09
sdagueso you can work like a library and install from pypi15:09
sdagueand that's fine15:09
ttxlike in the project team guide15:09
anteayaI think this may be a gap where the theory of the big tent and the reality of what people with with it causes issues15:09
sdaguebut co-gating is not15:09
mriedemanyone want an action for a doc update?15:09
sdagueand even our libraries have stable/* branches15:09
* mriedem is not sure where that is15:09
ttxanteaya: the consequences of choice are not always well explained15:09
ttx(yet)15:09
anteayaor understood as well make up the rules15:10
sdagueso I think anything out of openstack that has branches needs a stable/liberty branch15:10
anteayas/well/we15:10
sdagueI think that's the thing that we missed before15:10
mriedemsdague: or has to be installed from pypi15:10
anteayaI don't mind taking an action item for a patch to the project team guide but it will need heavy review as I don't know what it should say15:11
*** salv-orl_ has quit IRC15:11
anteayabut I'll kick it off15:11
ttxsdague: interesting... would you mind raising a thread about that once you have it formalized ? I'd like us to discuss that a bit more15:11
mriedemi will gladly assign an action to someone here15:11
ttxanteaya: we need to get to the bottom of what that means first15:11
anteayaunderstood15:11
anteayaI agree clarity is helpful15:12
sdaguettx: I've got a few other hard problems on my plate right now, this is just something I've been mulling as I've watched this gnocchi review hit various brick walls15:12
mriedem#action mriedem to talk to ppl about co-gating and what that means for big tent and projects with branches and w/o, like ceilometer + gnocchi15:12
mriedemi also wonder how that has implications for lifeless' spec that is part of a longer term goal to remove stable branches15:13
mriedemor i thought it was15:13
mriedembut we can get into that later15:13
ttxI mean, I'm open for limiting the choices there, I just want us to think a bit more about it before we announce anything15:13
*** yamamoto has joined #openstack-meeting-315:13
sdagueyeh, that's fair. I think there are 2 modes we know are good15:13
anteayathe choices already are limited, we just need to inform folks15:14
anteayapeople can't test anything with everything else15:14
sdagueyou don't have branches, you release from master, and support all supported stable branches with your master15:14
sdaguesee: tempest15:14
anteayaneutron drivers on independant release have run into this15:14
mriedemnothing depends on tempest though,15:14
sdagueyou release with branches, and have a branch that's appropriate for the official release branches15:14
mriedemso in this example, gnocchi is tempest15:14
ttxsdague: sounds fair15:15
*** jrist has joined #openstack-meeting-315:15
sdaguemriedem: lets say python-novaclient then15:15
mriedemwhich has branches :)15:15
sdagueit does now15:15
sdaguepart of the problem is we used to actually have this model, then capping forced a lot of new branches, then people thought they could do anything they wanted with branches15:16
*** jrist has quit IRC15:16
*** jrist has joined #openstack-meeting-315:16
mriedemif ceilometer depends on gnocchi as a library, i'm not really sure why it's not just installing it via pypi15:16
mriedemat whatever version it needs15:16
mriedemgnocchi can have master and support all stable if it wants15:17
sdagueyeh, I don't know15:17
ttxfeels like a discussion for the release team anyway15:17
mriedemi'll also follow up with gordc and jd i suppose15:17
apevecmriedem, it cannot b/c of deps on master might be too new for older branches15:17
ttxif it has too many common deps it should probably follow the cycle basically15:18
mriedemapevec: i'm saying ceilometer wouldn't depend on master gnochi15:18
mriedemceilometer needs to depend on a version of gnocchi that is constrained by upper-constraints15:18
mriedemin each stable branch of ceilometer15:18
mriedemand if gnocchi does a backwards incompatible thing, then it's breaking backwards compat and we either have to cap it or revert that breaking change15:19
mriedemwhich gets into lifeless' spec https://review.openstack.org/#/c/226157/15:19
mriedemthat would also mean that the requirements repo changes would have to be gated on ceilometer, which they aren't today, but that gets into more details than we want here15:20
mriedemshall we move off this topic?15:20
ttxyes15:20
mriedemok15:20
mriedemttx: Remaining stable/kilo (coordinated) point releases15:20
ttxSo... Starting with liberty we do separated, on-demand stable point releases15:20
ttxBut we still have a few coordinated point releases to do for kilo15:21
apevecgnocchi is actually a service, ceilo depends only on gnocchiclient15:21
ttx#link https://wiki.openstack.org/wiki/StableBranchRelease#Rinse.2C_Repeat15:21
ttx2015.1.3 January, 201615:21
ttx2015.1.4 (eol) 2016-05-0215:21
ttxDaviey (in a private thread with apevec and me) proposed to handle both15:21
mriedemway to be not open :)15:21
mriedemsheesh15:21
mriedemi'm fine with that15:22
ttxindeed, but since he volunteered I forgave him15:22
ttxIt would be great to go through the release process and check what still applies15:22
ttxAlso check if the needed tooling is still available, since we did remove some tools from release-tools recently15:22
ttxSo I'll contact him and check we still have all ducks in row15:22
ttx#action ttx to go through the stable release process with Daviey to doublecheck tooling15:22
mriedemcool15:23
apevecmriedem, my fault, I started that offlist thread from juno EOL announcement15:23
mriedemttx: anything else on that item?15:23
apevecttx, couldn't we use part of new tooling, just for pushing tags?15:23
mriedemkilo is pretty stable atm15:23
ttxIt's good to have a volunteer for the last 2, so that nobody else has to dive into old process15:23
ttxapevec: that is what I want to figure out15:24
*** yamamoto has quit IRC15:24
anteayayay kilo is ~stable15:24
ttxmriedem: I'm done with this topic15:24
mriedemttx: Stable team tags: moving from has-stable-branches to follows-stable-policy ?15:24
ttxunless there are questions15:24
ttxOK; so... We currently have one tag to describe /some/ stable branch support:15:24
ttx#link http://governance.openstack.org/reference/tags/release_has-stable-branches.html15:24
ttxThe problem is... this tag is a bit overloaded and doesn't really mean anything useful anymore15:25
ttxAny project can set up stable branches now, they can even name them stable/$series15:25
ttxthey don't have to follow the policy or even add us to their $project-stable-maint teams15:25
ttxSo I'd like to propose we retire this now-useless tag and replace it by something more useful15:25
ttxThe way to think about it is in terms of answering a question that downstream users have15:25
ttxIn our domain I think what they want to know is which projects have "stable branches that they can rely on"15:25
ttxi.e. which projects follow the stable branch policy, as defined and checked by the stable team15:26
*** tmazur has quit IRC15:26
anteayado we have a tag that identifies if a project interacts with the release team, in a follows their guidance kind of way?15:26
ttxSo I'd like us to propose a stable:follows-policy tag, which would be granted by the stable team:15:26
ttxanteaya: we have release:managed, but that means somethign different. It's also non-optional to release so basically all projects need to follow15:26
anteayaokay15:27
ttx- as long as we are confident they are following the policy15:27
ttx- once we are added to their stable +2 team15:27
ttxthen we would apply stable:follows-policy15:27
ttxbasically using the tag as the carrot for following the common stable policy15:27
ttxand using tag removal as the stick to encourage outliers to better comply15:27
ttxhow does that sound ?15:27
anteayawhat is the criteria for removal?15:27
mriedembackporting and merging things that are against the stable policy15:28
mriedemlike features or api changes15:28
anteayait is the removal part we seem to have the hardest part with15:28
ttxanteaya: "project does not follow stable branch policy" ?15:28
*** ajmiller has joined #openstack-meeting-315:28
ttxIf that sounds like a good idea I can draft a tag definition15:28
mriedemi have no problem with removal if someone continually gets caught breaking policy (like more than once as a mistake)15:28
mriedemit's hard to police given there are so many15:28
anteayamriedem: that's the issue15:29
ttxthat we would review as a team before proposing it to the tc15:29
*** kbyrne has joined #openstack-meeting-315:29
mriedemso really someone has to speak up and say project x backported and merged a thing which broke my production cloud - which rarely happens15:29
ttxJust wanted a temperature reading from the team before I get started15:29
*** kbyrne has quit IRC15:29
mriedemor some projects CI would have to start failing15:29
anteayamriedem: right15:29
mriedemttx: i'm all for this15:29
ttxNB: I would limit the tag to stable branches that track common stable series (like stable/liberty)15:29
mriedemit's just the oversight that's hard15:29
anteayamriedem: yes15:29
mrungewow, that quite hard to decide15:29
ttxrather than also apply it to project-specific branches (like stable/1.0)15:30
*** kbyrne has joined #openstack-meeting-315:30
mrungehow often did we saw some bad backports, breaking compatibility?15:30
mriedemmrunge: that's the thing, you don't really at a global level15:30
mriedemespecially if no one speaks up in irc or the ML if it happens15:30
mrungeBut yes, I agree, we should encourage folks to look at that15:30
ttxmrunge: some projects just don't backport bugfixes15:30
mrungeIdeally, we would have more test coverage15:31
ttxit's fine, they just won't have the tag15:31
*** kebray has joined #openstack-meeting-315:31
ttxsince downstream users should know their stable branches are mostly worthless15:31
mriedemi guess i wasn't thinking about whether or not they are backporting bug fixes15:31
ihrachysmrunge: I often catch those in neutron15:31
ihrachysI mean, I block them :)15:32
mriedemsince if you consider the number of bugs fixed in nova per master release vs how many get backported (which are applicable), it's a drop in the bucket15:32
mrungeihrachys, yes, that's greatly appreciated15:32
ttxI mean, it's a significant piece of information to communicate downstream, and currently it is quite hard to determine15:32
mriedemyeah15:32
ttxand the current tag hides it completely15:32
mriedemrather than bugs, it's probably just easier now to see if they are doing stable point releases15:32
ihrachysmriedem: in neutron, we backport everything applicable to N-115:32
ttxOne remaining question though is whether we would allow "late" stable branches to have the tag15:32
ttxthings that are release:independent because they can't make the release date, but still want to have a branch called stable/liberty15:32
*** zz_dimtruck is now known as dimtruck15:33
ttxlike fuel15:33
anteayaor can they make a stable/liberty branch in the middle of mitaka15:33
ttxor some neutron stadium things15:33
anteayawhich someone wanted to do the other day15:33
mriedemwe've created stable/juno branches on things after the fact, when we needed to backport something15:33
sdaguewhy is it an issue to post date releases?15:33
ttxmy gut feeling is  that those should be outside policy but meh15:33
mriedemchef cookbooks cut stable branches long after master is released too15:34
anteayacut or create?15:34
mriedemthey cut their mitaka release a few months after mitaka is released in the code projects15:34
anteayaor does the difference matter?15:34
ttxsdague: we are basically communicating: "those projects have sane stable branches"15:34
mriedemb/c the cookbooks are stabilizing the release15:34
ttxI think part of being sane is to have them created around the same time15:34
sdagueyeh, I think we need to realize that stable/liberty is a convenience concept to users of stuff that is going to all work in liberty15:34
ttxso that you can follow through them as a user15:34
anteayamriedem: that makes sense due to their work15:34
anteayattx: I agree, created dates need to be in the release in question15:35
ttxbut as I said I don't feel strongly about this15:35
mriedemi agree with sdague, the branch is there to indicate it works with the liberty releaes of the code15:35
sdaguettx: I guess, all the orgs I know that are deploying from stable don't do so until + 4 months or so15:35
mriedemas long as they are following the stable branch policy, i don't really care when they create the branch15:35
ttxsdague: ok, I can leave that out of the definition15:35
mriedemthere are some projects that i think still have active stable/icehouse branches, fwiw :)15:35
ttxI think I have enough to start drafting15:36
anteayabut it may affect their ability to test that branch15:36
mriedemanteaya: sure, like stable/icehouse15:36
anteayaright15:36
mriedembut yeah, let's review in the review when that's up15:36
anteayaI think that needs to be identified15:36
mriedemmoving on15:36
sdagueit might be worth tagging projects that get a stable branch out at release date, those that hit it within 2 months, and those which show up later15:36
mriedemttx: Liberty stable point releases status: do we need to push for some releases ?15:36
ttx#action ttx to draft a stable:follows-policy tag definition for the team to discuss15:36
ttxSo for liberty we said that projects would just request stable point releases themselves15:36
ttxMost did, but some may need some encouragement/reminder15:36
ttxI think regular releases are important to make our stable branches look better15:37
mrungeyes!15:37
ttxso I think it's still the stable team responsibility to track that releases are regularly made15:37
mriedemyes, i've been pushing on the nova one15:37
ttxFor liberty the following projects did not make a release since liberty release:15:37
mriedemwe have a security fix that has to get in first15:37
ttxbarbican, congress, designate, heat, horizon, mistral, nova, sahara, trove, zaqar15:37
ttxswift and aodh haven't released either but since they are doing intermediary releases that is not as needed imho15:37
ttxSome of them just didn't have that much stable activity, like barbican, congress, trove or zaqar15:37
ttx(might be worth checking if they really are following stable branch policy and backporting "enough" changes, but that is another topic)15:37
ttxSome of them have 34+ changes and should really be doing a point release: Heat, Mistral, Nova, Sahara15:38
ttxSome have 17+ and should consider one: Designate, Horizon15:38
ttxSo in summary I think we should regularly review this and have someone assigned to the nagging15:38
ttxI'm happy to take the first round15:38
mrungehorizon has probably more, including i18n updates, which are quite big15:38
*** JeanBriceCombebi has quit IRC15:38
mriedemttx: thanks for pulling the numbers, i agree we have to stay on top of it, i've been busy trying to get the nova one ready15:39
ttxprobably some automated way of figuring out how much they need a release would be nice too15:39
mriedemso i'd appreciate it if you want to own that first round of nagging15:39
ttxYeah I'll own it, figure out what metrics we should track there15:39
*** JeanBriceCombebi has joined #openstack-meeting-315:39
mriedemwell i think we know after you've backported security fixes, you should release15:39
ttxthen we can review that regularly, say once every ~ 6 weeks or so15:40
mriedemin the case of nova, we really didn't start talking about it until some regression fixes were backported15:40
mriedemfrom my pov, it's going to be hard to just look at what's been backported to e.g. zaqar and know if they need something15:40
mriedemthere could be 20 piddly backports or 2 critical backports15:40
ttxyeah that should not prevent releasing more aggressively15:40
mriedemsure15:41
*** numans has quit IRC15:41
mriedemwe could probably have some tooling that scrapes the bug priority too15:41
ttxit's just that before liberty we had the safety net of the catch-all coordinated release15:41
mriedemand flag if there are critical bugs backported that aren't yet released15:41
ihrachysttx: I think oslo team should have some scripts they use to track unreleased changes15:41
ttxyeah, I was thinking going from that15:41
ttxanyway another action for me15:42
dims./list_unreleased_changes.sh in release-tools repo15:42
ttx#action ttx to do the first stable release nagging round15:42
apevecshould CVE fix trigger point release?15:42
ttxapevec: yes15:42
mriedemapevec: yeah15:42
apevecNova had one right?15:42
mriedemapevec: yes, the backports are being reviewed and then we'll do 12.0.115:42
ttx(for stable/liberty only)15:42
ttxalright that is all I had15:43
mriedemttx: to get the list that haven't released yet, where did you come up with that? the releases repo?15:43
apevecttx, there was a thread from zigo about stable horizon supporint latest django ?15:43
ttxmriedem: and some hand count on git logs15:44
zigoapevec: Hi!15:44
apeveczigo, hi - why do you want django 1.9 ?15:44
apevec1.8 is their LTS15:44
zigoI've wrote lots of patches for Django 1.9 in Horizon already.15:44
ttxapevec: not related to my topic, but yes15:44
mriedemapevec: we had to cap django_compressor in stable/kilo horizon last week b/c the latest release drops support for django<1.815:44
zigoapevec: Debian Sid already has Django 1.9.15:44
zigoSo there's an RC bug filled.15:44
zigoI need to have it fixed.15:44
apevecmrunge said 1.8 is better  choice15:45
zigoAlso, Horizon in Mitaka will need to support Django 1.9, as most likely, it's going to be the version in the next LTS.15:45
apevec1.9 will be out of support soon15:45
zigoBetter or not, we need to move forward and support the latest version.15:45
mrungedjango-1.9 won't be the next LTS version15:45
mrungeit's 1.815:45
ttxfeels like debian bet on the wrong horse then15:46
zigoWell, anyway, I need to fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=80957515:47
openstackDebian bug 809575 in src:horizon "horizon: FTBFS: ImportError: cannot import name importlib" [Serious,Open]15:47
zigottx: Debian Sid is always on the edge.15:47
ttxzigo: someone will have some fun backporting 1.8 sec fixes to 1.9 in 201715:47
zigoAlso, remember that the packages for Django are maintained in Debian, and just sync to Ubuntu.15:47
mrungezigo has a point, as we don't even support Django-1.9 right now in mitaka15:47
*** yamamoto has joined #openstack-meeting-315:48
ttxbut yeah, I think that's orthogonal to the issue at hand15:48
zigomrunge: I really hope that my patches will be accepted when I send them (of course, without destroying 1.8 compat).15:48
zigoAs much as I know, no problem with that so far.15:48
mrungezigo, I would prefer, if you'd file bugs in launchpad about that15:48
zigoI did couples of django.getversion() calls when needed.15:49
ttxwe'll need to support >=1.8 anyway15:49
mrungeI would like see fixes backported to liberty as well15:49
mrungejust making horizon work in more environments15:49
zigoAs I wrote to you in #openstack-horizon, I prefer to finish the work first, and make sure nothing is broken, before attempting to upstream my work.15:49
zigoTimur S. wrote to me he will try to help tomorrow as well.15:49
mrungeI was just asking to document issues, just to be able to track them15:50
zigoWell, the issue is that when you fix one issue, it uncovers another one.15:50
mrungeand I'm really glad you're trying to fix those issues15:50
zigoSo it's impossible to document all until all is kind of fixed.15:50
*** kbyrne has quit IRC15:50
mrungeyes, sure. but still we can track it then15:50
mrungewe should have a tracker for django-1.9 support anyways15:51
mrungemakes sense?15:51
mriedemcan we move this to -horizon?15:51
zigoI'll do things properly and file bugs.15:51
mrungewe already had the same discussion15:51
zigoIt's just too early for that right now, IMO.15:51
mrungeand agreed to disagree15:51
mrunge;-)15:51
zigo:)15:51
mriedem#topic open discussion15:51
*** openstack changes topic to "open discussion (Meeting topic: stable)"15:51
mriedemthere was nothing on the agenda15:51
mriedemdoes anyone have anything else for today?15:51
mriedemok, well let's end the meeting, thanks everyone15:52
mriedem#endmeeting15:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:52
anteayamriedem: just that you had tried to time these meetings as opposite to neutron15:52
openstackMeeting ended Tue Jan 12 15:52:19 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-01-12-15.01.html15:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-01-12-15.01.txt15:52
openstackLog:            http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-01-12-15.01.log.html15:52
anteayamriedem: and neutron has changed their meeting time15:52
mrungethanks everyone15:52
mriedemanteaya: ?15:52
mriedemso the neutron meeting is the same time as this one now?15:52
anteayatoday yes, becuause yesterday was a disaster trying to communicate a change15:53
anteayaso now it will be mondays all the time15:53
mriedemso there isn't a problem?15:53
anteayamriedem: https://review.openstack.org/#/c/266019/15:53
anteayamriedem: no no problem, just I recall you had said that in passing when you picked times for stable meetings15:54
anteayamriedem: so I wanted to inform you of the change15:54
mriedemso neutron meetings are always monday at 2100 UTC15:54
mriedemand there is a bi-weekly odd stable meeting at that same time15:54
mriedemmeh15:54
mriedemthere are a lot of meetings15:54
anteayayeah15:55
mriedemunless you want 4pm on a friday15:55
anteayaso now you know15:55
anteayaI don't15:55
mriedemme neither15:55
anteaya#agreed15:55
*** mriedem has left #openstack-meeting-315:56
*** hichihara has quit IRC16:01
*** apevec has left #openstack-meeting-316:01
*** krtaylor has quit IRC16:03
*** mfranc21_ has joined #openstack-meeting-316:04
*** mfranc213 has quit IRC16:04
*** kebray has quit IRC16:05
*** egallen has quit IRC16:05
*** julim has quit IRC16:06
*** galstrom_zzz is now known as galstrom16:06
*** julim has joined #openstack-meeting-316:07
*** kbyrne has joined #openstack-meeting-316:09
*** vgridnev has quit IRC16:11
*** kzaitsev_mb has quit IRC16:13
*** rmoe_ has joined #openstack-meeting-316:14
*** dandruta has quit IRC16:14
*** krtaylor has joined #openstack-meeting-316:14
*** rmoe has quit IRC16:14
*** shwetaap1 has quit IRC16:15
*** matrohon has quit IRC16:16
*** sigmavirus24_awa is now known as sigmavirus2416:18
*** yamamoto has quit IRC16:18
*** Aish has joined #openstack-meeting-316:23
*** vahidh has joined #openstack-meeting-316:23
*** galstrom has quit IRC16:24
*** galstrom has joined #openstack-meeting-316:24
*** galstrom has quit IRC16:26
*** MarkAtwood has joined #openstack-meeting-316:26
*** galstrom has joined #openstack-meeting-316:26
*** JeanBriceCombebi has quit IRC16:27
*** JeanBriceCombebi has joined #openstack-meeting-316:27
*** rtheis_ has joined #openstack-meeting-316:30
*** rtheis has quit IRC16:32
*** shwetaap has joined #openstack-meeting-316:33
*** Aish has quit IRC16:36
*** piet has quit IRC16:41
*** devkulkarni has joined #openstack-meeting-316:46
*** paul-carlton2 has quit IRC16:50
*** rahulshr_ has joined #openstack-meeting-316:51
*** vijendar has joined #openstack-meeting-316:51
*** james_li has joined #openstack-meeting-316:54
*** nkrinner has quit IRC16:55
*** bradjones has quit IRC16:55
*** bradjones has joined #openstack-meeting-316:58
*** bradjones has quit IRC16:58
*** bradjones has joined #openstack-meeting-316:58
*** ashishjain has joined #openstack-meeting-316:59
*** Aish has joined #openstack-meeting-316:59
*** piet has joined #openstack-meeting-316:59
*** spzala has quit IRC16:59
devkulkarni#startmeeting Solum Team Meeting17:00
openstackMeeting started Tue Jan 12 17:00:11 2016 UTC and is due to finish in 60 minutes.  The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: Solum Team Meeting)"17:00
openstackThe meeting name has been set to 'solum_team_meeting'17:00
*** spzala has joined #openstack-meeting-317:00
devkulkarni#topic Roll Call17:00
*** openstack changes topic to "Roll Call (Meeting topic: Solum Team Meeting)"17:00
devkulkarniDevdatta Kulkarni17:00
vijendaro/17:00
ashishjainAshish Jain17:00
*** muralia has joined #openstack-meeting-317:00
*** muralia has left #openstack-meeting-317:01
*** dslev has quit IRC17:01
james_lijames li17:01
devkulkarniplease feel free to provide your name to get registered as an attendee for the meeting17:01
devkulkarnihi james_li, ashishjain, vijendar17:01
james_liHi devkulkarni17:01
devkulkarniwe have a new contributor today rahulshr_17:02
rahulshr_Rahul Shrivastava17:02
vijendarHi devkulkarni and all17:02
james_liwelcome rahulshr_17:02
dimtrucko/17:02
devkulkarnihi rahulshr_: welcome to solum17:02
devkulkarnihi dimtruck17:02
rahulshr_Hi james_li17:02
*** yamamoto has joined #openstack-meeting-317:02
devkulkarnirahulshr_: do you want to introduce yourself to the team.. a couple of lines about what your background and what interests you in solum will be great17:03
*** bharathm has joined #openstack-meeting-317:03
*** salv-orlando has joined #openstack-meeting-317:03
rahulshr_sure..17:03
*** spzala has quit IRC17:04
*** jlanoux has quit IRC17:04
rahulshr_I have around 6 years of exp in various application dev, I have worked in Verizon, Oracle. Mostly I have used C/C++ and a bit of python for development17:05
*** galstrom is now known as galstrom_zzz17:06
devkulkarnirahulshr_: nice!!17:06
*** vgridnev has joined #openstack-meeting-317:06
*** kzaitsev_mb has joined #openstack-meeting-317:06
devkulkarnirahulshr_: we sure are going to benefit from your background in solum development17:06
rahulshr_I saw few demo of openstack and got interested to contribute to it.17:06
devkulkarnirahulshr_: we are glad that one of the projects that interested you is solum17:07
rahulshr_Since Solum is new may be I can contribute here easily..17:07
*** tellesnobrega_af is now known as tellesnobrega17:07
devkulkarnirahulshr_: yes, solum is relatively new as compared to other openstack projects17:07
devkulkarniin terms of lines of code we are < 30K lines of python code.. I don't know how big others are, but we are not that big that is sure17:08
devkulkarnirahulshr_: we look forward to your contributions17:08
rahulshr_for now I am trying to deploy solum in our openstack multinode setup17:09
*** shwetaap has quit IRC17:09
devkulkarnirahulshr_: oh cool.. let us know how it goes17:09
rahulshr_devkukarni: sure...17:09
devkulkarniyou might be able to contribute your findings to solum installation guide17:09
devkulkarnicool17:10
*** Swami has joined #openstack-meeting-317:10
devkulkarnialright.. here is the agenda for today's meeting:17:10
*** bpokorny has joined #openstack-meeting-317:10
devkulkarni#link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2016-01-12_1700_UTC17:10
*** safchain has quit IRC17:10
devkulkarni#topic Announcements17:10
*** openstack changes topic to "Announcements (Meeting topic: Solum Team Meeting)"17:10
devkulkarni#success Devstack plugin for Solum finally working as expected.17:10
openstackstatusdevkulkarni: Added success to Success page17:10
*** ALUVial has joined #openstack-meeting-317:10
devkulkarnibig thanks to dimtruck for helping with getting our devstack plugin straightened out17:11
devkulkarnito be more specific, the plugin is for the devstack gate17:11
ashishjaindimtruck thats nice17:12
devkulkarniour devstack gate was failing since mid-December as the plugin was not working as expected17:12
devkulkarniinitial plugin code was contributed by venkatmaheshkotha17:12
devkulkarnithanks to venkatmaheshkotha for that17:12
devkulkarnilast week dimtruck went through deep weeds and figured out what was causing the plugin to not work as expected17:13
*** shwetaap has joined #openstack-meeting-317:13
devkulkarniany one have any other announcements?17:13
devkulkarnialright.. moving on to the next topic17:14
devkulkarni#topic Review Action Items17:14
*** openstack changes topic to "Review Action Items (Meeting topic: Solum Team Meeting)"17:14
devkulkarniI have an action item pending on retiring solum readthedocs, but I have not listed it as I have been just carrying it forward for sometime now without actually making any progress on it17:15
*** klkumar has quit IRC17:15
devkulkarniso I have removed it from the list.. I will provide an update once I figure it out17:15
devkulkarniapart from that there were no action items that we had identified last time17:16
devkulkarni#topic Blueprint/Bug Review and Discussion17:17
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: Solum Team Meeting)"17:17
devkulkarniI am going to switch order here a bit17:17
devkulkarni1) API/Service patches needing one more +217:17
dimtrucksorry to backpedal, devkulkarni but quick question17:17
devkulkarnijames_li: there are several patches which need one more +217:17
devkulkarnidimtruck: sure17:17
dimtruckwhat do you mean by retiring readthedocs?17:17
dimtruckdo you mean removing it from the site or stop publishing to it?17:18
devkulkarnidimtruck: good question17:18
devkulkarniwe want to retire this: http://solum.readthedocs.org/en/latest/ as it is no longer correct (and the jobs are not publishing to it)17:18
james_lidevkulkarni: taking a quick look17:18
devkulkarniwe have already removed the job17:18
devkulkarnithanks james_li17:18
devkulkarnidimtruck: but we need to figure out how to remove above site/link17:19
devkulkarniit shows up in google searches17:19
devkulkarniofficial solum documentation is at: http://docs.openstack.org/developer/solum/getting_started/index.html17:19
devkulkarnidimtruck: do you know what can we do to remove the readthedocs site?17:20
dimtrucklooking too :)17:20
devkulkarnidimtruck: my guess is we might have to reach out to openstack-infra folks about this17:21
dimtruckit's owned by them??17:21
devkulkarniashishjain, rahulshr_, dimtruck, vijendar: please review the patches that are needing one more +2 which I have listed in the meeting agenda17:21
vijendarsure17:22
devkulkarnidimtruck: well, I don't know if the site is owned by them or not, but they control the job that publishes the official docs (and also readthedocs job for projects that are not yet official)17:23
ashishjaindevkulkarni : sure17:23
dimtrucki see17:24
dimtruckok, thank you17:24
dimtrucksorry for the tangent17:24
*** sdake has joined #openstack-meeting-317:25
devkulkarnidimtruck: no, its not a tangent.. if you have any insights/suggestions on this I would like to hear them17:25
devkulkarnithe action item has been pending for some time now17:26
*** galstrom_zzz is now known as galstrom17:26
devkulkarnilets take next 15 minutes to go through the patches that are needing one more +217:27
*** yamamoto has quit IRC17:27
*** MarkAtwood has quit IRC17:27
devkulkarnibtw, james_li is one of our core reviewers (having the +2 power)17:27
devkulkarnigood to have him join us for the meeting today17:27
*** yamamoto has joined #openstack-meeting-317:28
devkulkarniyou can find who all have +2 capabilities here: http://stackalytics.com/?module=solum-group17:28
devkulkarnifolks who are core reviewers have a star besides their name17:29
dimtruckoh nice!17:29
*** yamamoto has quit IRC17:30
*** yamamoto has joined #openstack-meeting-317:30
*** davidsha has quit IRC17:30
*** vahidh has quit IRC17:31
*** yamamoto has quit IRC17:31
*** vahidh has joined #openstack-meeting-317:32
*** JeanBriceCombebi has quit IRC17:32
*** yamamoto has joined #openstack-meeting-317:32
devkulkarnirahulshr_: here are the links to open solum patches:17:32
devkulkarni#link https://review.openstack.org/#/q/project:openstack/solum+status:open,n,z17:32
devkulkarni#link https://review.openstack.org/#/q/project:openstack/python-solumclient+status:open,n,z17:33
*** yamamoto has quit IRC17:33
rahulshr_devkulkarni: checking it17:33
devkulkarnidimtruck: about your tempest plugin patch.. what are the next steps?17:33
dimtruck1. rebase17:34
dimtruck2. update the tests to use dynamic credentials17:34
*** yamamoto has joined #openstack-meeting-317:34
dimtruckthat should be it17:34
*** mrmartin has joined #openstack-meeting-317:34
dimtrucki should have a patch later this week ready for review17:34
devkulkarnirahulshr_: cool.. you can  bookmark those links17:34
devkulkarnidimtruck: sounds good17:34
devkulkarnidimtruck: the dynamic creds would make it such that we don't have to setup users etc. that we currently do in post_gate_hook?17:35
dimtruckthat is exactly correct17:35
dimtruckit has 2 advantages17:35
dimtruck1. no longer having ti set up demo users17:35
*** yamamoto has quit IRC17:35
*** yamamoto has joined #openstack-meeting-317:36
dimtruck2. can run tests in parallel and not step on the same user's resources17:36
dimtruckit /might/ be that we still can't because of resource constraints on the test hosts but at least we'll have ability to do that.17:36
devkulkarnidimtruck: both those seem very useful things17:36
*** yamamoto has quit IRC17:36
*** vahidh has quit IRC17:36
devkulkarnidimtruck: I am assuming that we will be able to control whether or not we want to run tests in parallel, right?17:37
dimtruckthat's correct17:37
dimtruckit's just a tox command17:37
devkulkarniI see17:37
dimtruckwith a regex for which tests to run and a parallel flag to control concurrency17:37
*** yamamoto has joined #openstack-meeting-317:37
dimtruckinstead of running nose, we'll run tox17:37
devkulkarnidimtruck: I see..17:37
*** yamamoto has quit IRC17:38
devkulkarnidimtruck: going back to the discussion about devstack plugin..17:38
devkulkarnihow does the plugin interface with our vagrant setup? any ideas?17:39
devkulkarnihttps://github.com/rackerlabs/vagrant-solum-dev17:39
*** yamamoto has joined #openstack-meeting-317:39
devkulkarniin the vagrant setup we were basically copying over lib/solum and extras.d into the devstack directory17:39
devkulkarniand then stack.sh was calling the hooks from lib/solum17:39
devkulkarnibut with the plugin model since the lib/solum has been deprecated, we probably need to use the enable_plugin macro in the vagrant setup..17:40
*** mbound has quit IRC17:41
devkulkarnihttps://github.com/rackerlabs/vagrant-solum-dev/blob/master/Vagrantfile#L31017:41
devkulkarnihttps://github.com/rackerlabs/vagrant-solum-dev/blob/master/Vagrantfile#L31117:41
*** ALUvial_ has joined #openstack-meeting-317:41
dimtruckright17:41
devkulkarniat least that is what I am thinking..17:41
dimtrucki'll need to take a look closer at that...17:41
devkulkarniwhat do you think?17:41
devkulkarniok17:41
dimtruckit should be exactly the same as gate17:41
*** ALUVial has quit IRC17:42
dimtruckmeaning that we just add those enable_plugin and $PROJECTS flags and the rest should work the same17:42
devkulkarniwill it be? but we are not spinning up gate vm17:42
*** e0ne has quit IRC17:42
dimtruckthat's fine17:42
dimtruckall devstack-gate does is set up a bunch of jenkins envvars17:42
dimtruckand some other stuff...but mostly then calls stack.sh17:42
dimtruckwhich then uses plugins17:43
*** matrohon has joined #openstack-meeting-317:43
devkulkarnithat's right17:43
dimtruckessentially, they ripped out extras.d and replaced it with plugin arch so we should not have to do much work there17:43
devkulkarnimay be all we need to do then is to add that enable_plugin line to the Vagrantfile17:43
dimtruckjust make sure to not enable tempest since we don't want to run that :)17:43
dimtruckright17:43
dimtruckthat's what i'm thinking17:43
*** ashishjain1 has joined #openstack-meeting-317:43
*** yamamoto_ has joined #openstack-meeting-317:43
devkulkarnialright.. I will try that today17:44
*** yamamoto has quit IRC17:44
devkulkarnialright.. its quarter to noon.. I would like to move on to the next topic17:44
devkulkarnibefore I skip to the next topic, there are two other review items in the meeting agenda17:45
devkulkarni1) Release model change as suggested by ttx #link https://review.openstack.org/#/c/263294/17:45
devkulkarniWe discussed about this last time..17:45
*** yamamoto_ has quit IRC17:45
devkulkarnithe deadline to change the release model is Jan 21st. We have submitted the patch above.17:45
devkulkarnithere is nothing more that needs to be done17:46
devkulkarni2) Micro-service architecture spec https://review.openstack.org/#/c/254729/17:46
*** ashishjain2 has joined #openstack-meeting-317:46
devkulkarniPlease take a look at the micro-service architecture spec above17:46
*** mfranc213 has joined #openstack-meeting-317:46
devkulkarniAt a high-level, this spec outlines how we can support multi-container apps in solum17:47
devkulkarninow that I think of it, I should have named the spec as 'multi-container app architecture' spec rather than micro-service architecture17:47
*** yamamoto has joined #openstack-meeting-317:47
devkulkarniI might change the name17:47
*** ashishjain2 has quit IRC17:47
devkulkarniplease read it, review it, provide comments, ask questions, etc.17:47
*** ashishjain4 has joined #openstack-meeting-317:48
devkulkarnialright17:48
devkulkarni#topic Open discussion17:48
*** openstack changes topic to "Open discussion (Meeting topic: Solum Team Meeting)"17:48
devkulkarniThe main thing I wanted to discuss was the Austin summit17:48
devkulkarni#link https://www.openstack.org/summit/austin-2016/17:49
devkulkarnitalk submission deadline Talk submission: February 1, 201617:49
devkulkarniTravel support: February 9, 2016 (https://www.openstack.org/summit/austin-2016/austin-and-travel/#travel-support)17:49
*** ashishjain1 has quit IRC17:49
devkulkarnilets brainstorm possible talks that we can submit..17:49
*** mfranc21_ has quit IRC17:50
devkulkarnidimtruck, vijendar, james_li, ashishjain: any thoughts/ideas on topics that we can submit for the summit?17:50
*** galstrom is now known as galstrom_zzz17:51
*** ashishjain4 has quit IRC17:51
devkulkarniashishjain: if you have installed solum at wipro and are using it in some capacity, that can be a nice topic for the talk17:51
*** ashishjain1 has joined #openstack-meeting-317:52
dimtrucknot from me yet :)17:52
*** yamamoto has quit IRC17:52
devkulkarniif we are able to push the multi-container work, then we can talk about deploying solum using solum17:52
devkulkarnibut we are not there yet17:52
vijendarhow about solum with containers service (carina/magnum)17:52
devkulkarnivijendar: +117:53
devkulkarniI was going to suggest that to you..17:53
*** mrmartin has quit IRC17:53
*** galstrom_zzz is now known as galstrom17:56
dimtruck+1 from me on that too17:56
*** galstrom is now known as galstrom_zzz17:56
vijendarand also how about solum as CI/CD?17:56
dimtruckif we can show CI/CD on multi-container deployment/re-deployment17:56
dimtruckgreat minds think alike vijendar ;)17:56
vijendar:)17:57
devkulkarnisure, that can be another one17:57
ashishjaindevkulkarni: sure will try to submit one on the usecase17:57
*** ashishjain1 has quit IRC17:57
devkulkarnidimtruck: although, not on multi-container deployment/re-deployment17:57
devkulkarnisince we won't be ready with multi-container till the deadline (Feb 1)17:57
vijendardevkulkarni: but it will be ready by summbit…right?17:58
devkulkarnibut we can aim for CI/CD + non-destructive app updates with Magnum/Carina17:58
vijendardevkulkarni: *summit17:58
devkulkarnivijendar: hopefully yess.. but I would not be very comfortable submitting the abstract without actually having it in working condition17:59
vijendardevkulkarni: sure17:59
devkulkarniwe can definitely demo multi-container if it is ready at the summit17:59
devkulkarnithanks ashishjain17:59
devkulkarniashishjain: let me know if I can help in any way with the submission.18:00
devkulkarnilooks like it is time to end the meeting18:00
devkulkarnilets keep on brainstorming about possible submission ideas over next couple of weeks18:00
ashishjaindevkulkarni sure18:01
devkulkarniwe should at least have 2 to 3 solum submissions18:01
devkulkarnialright.. thanks vijendar, ashishjain, rahulshr_, james_li, dimtruck for joining today18:01
devkulkarnisee you all next week18:01
ashishjaindevkulkarni thanks18:01
devkulkarni#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Tue Jan 12 18:01:49 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/solum_team_meeting/2016/solum_team_meeting.2016-01-12-17.00.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/solum_team_meeting/2016/solum_team_meeting.2016-01-12-17.00.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/solum_team_meeting/2016/solum_team_meeting.2016-01-12-17.00.log.html18:01
rahulshr_thanks devkulkarni18:02
*** rahulshr_ has quit IRC18:02
*** galstrom_zzz is now known as galstrom18:02
*** james_li has quit IRC18:02
*** devkulkarni has left #openstack-meeting-318:04
*** mrmartin has joined #openstack-meeting-318:04
*** MarkAtwood has joined #openstack-meeting-318:07
*** lblanchard has quit IRC18:08
*** lblanchard has joined #openstack-meeting-318:10
*** ivar-lazzaro has joined #openstack-meeting-318:13
*** ivar-lazzaro has quit IRC18:13
*** matrohon has quit IRC18:14
*** yamahata has joined #openstack-meeting-318:15
*** ivar-lazzaro has joined #openstack-meeting-318:15
*** galstrom is now known as galstrom_zzz18:17
*** ivar-lazzaro has quit IRC18:22
*** jmckind has quit IRC18:24
*** yamamoto has joined #openstack-meeting-318:26
*** ivar-lazzaro has joined #openstack-meeting-318:27
*** yamamoto has quit IRC18:27
*** yamamoto has joined #openstack-meeting-318:28
*** ivar-lazzaro has quit IRC18:28
*** yamamoto has quit IRC18:29
*** ivar-lazzaro has joined #openstack-meeting-318:29
*** yamamoto has joined #openstack-meeting-318:29
*** yamamoto has quit IRC18:31
*** neelashah1 has joined #openstack-meeting-318:32
*** piet has quit IRC18:32
*** neelashah has quit IRC18:33
*** yamamoto has joined #openstack-meeting-318:34
*** yamamoto has quit IRC18:35
*** krtaylor has quit IRC18:35
*** e0ne has joined #openstack-meeting-318:35
*** yamamoto has joined #openstack-meeting-318:36
*** rockyg has joined #openstack-meeting-318:37
*** yamamoto has quit IRC18:37
*** yamamoto has joined #openstack-meeting-318:38
*** yamamoto has quit IRC18:38
*** vahidh has joined #openstack-meeting-318:38
*** quintela has quit IRC18:40
*** kebray has joined #openstack-meeting-318:43
*** yamamoto has joined #openstack-meeting-318:45
*** yamamoto has quit IRC18:47
*** yamamoto_ has joined #openstack-meeting-318:47
*** yamamoto_ has quit IRC18:48
*** yamamoto has joined #openstack-meeting-318:49
*** yamamoto has quit IRC18:50
*** yamamoto has joined #openstack-meeting-318:50
*** rossella_s has quit IRC18:52
*** quintela has joined #openstack-meeting-318:52
*** yamamoto has quit IRC18:52
*** yamamoto has joined #openstack-meeting-318:52
*** rossella_s has joined #openstack-meeting-318:52
*** yamamoto has quit IRC18:53
*** piet has joined #openstack-meeting-318:53
*** yamamoto has joined #openstack-meeting-318:54
*** neiljerram has quit IRC18:54
*** yamamoto has quit IRC18:55
*** yamamoto has joined #openstack-meeting-318:56
*** yamamoto has quit IRC18:56
*** mrmartin has quit IRC18:56
*** yamamoto has joined #openstack-meeting-318:57
*** breton_ has joined #openstack-meeting-318:57
*** yamamoto has quit IRC18:57
*** yamamoto has joined #openstack-meeting-318:58
*** kebray has quit IRC18:59
*** yamamoto has quit IRC19:00
*** bpokorny_ has joined #openstack-meeting-319:00
briancurtin#startmeeting python-openstacksdk19:01
openstackMeeting started Tue Jan 12 19:01:08 2016 UTC and is due to finish in 60 minutes.  The chair is briancurtin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:01
openstackThe meeting name has been set to 'python_openstacksdk'19:01
etoewso/19:01
rtheis_o/19:01
briancurtini don’t see terry in -sdks so perhaps it’s just us19:02
*** rockyg has quit IRC19:02
*** kebray has joined #openstack-meeting-319:02
*** yamamoto has joined #openstack-meeting-319:03
briancurtinalrighty then. well, should probably just keep talking about how to get to 1.019:04
*** bpokorny has quit IRC19:04
breton_o/19:04
etoewsyes please :)19:04
*** breton_ is now known as breton19:05
rtheis_sounds good19:05
*** yamamoto has quit IRC19:05
*** spzala has joined #openstack-meeting-319:05
*** yamamoto has joined #openstack-meeting-319:05
etoewswhat about setting a bit of an arbitrary deadline just to have something to work against?19:05
briancurtinthe big thing i’m looking at right now is the whole path_args ordeal and how it’ll work with what needs to happen for URI props, body props, and header props. there’s a few things out there for that right now that i’m reviving but also looking at another way to do them. this is super hard. i’m slightly considering a reworking of the props to not be19:05
briancurtindescriptors, though i don’t know if that’s worth it19:05
briancurtinetoews: 90% of my year-end review was crushing myself over deadlines estimates19:06
*** yamamoto has quit IRC19:06
*** julim has quit IRC19:06
*** rbak has quit IRC19:06
*** yamamoto has joined #openstack-meeting-319:07
briancurtinafter evaluating more of this, i’ll see if i can come up with some kind of deadline. until at least the basics of a direction are sketched out i don’t really want to throw anything out19:07
etoewsalright then19:07
etoewswhat bugs does that work map to?19:07
etoews(the path_args ordeal that is)19:08
*** julim has joined #openstack-meeting-319:08
*** rockyg has joined #openstack-meeting-319:08
*** yamamoto has quit IRC19:08
*** yamamoto has joined #openstack-meeting-319:08
briancurtinetoews: this is one of them https://bugs.launchpad.net/python-openstacksdk/+bug/144025719:08
openstackLaunchpad bug 1440257 in OpenStack SDK "Resource props of type=resource cause issue with basepath" [Medium,In progress] - Assigned to Terry Howe (thowe-g)19:09
*** terrylhowe has joined #openstack-meeting-319:09
terrylhoweo/19:09
etoewsyay!19:09
*** ashishjain has quit IRC19:09
*** yamamoto has quit IRC19:09
rtheis_Is this another https://bugs.launchpad.net/python-openstacksdk/+bug/1461200 ?19:09
openstackLaunchpad bug 1461200 in OpenStack SDK "Create resource.props type=Resource for attributes with _id names" [Critical,In progress] - Assigned to Terry Howe (thowe-g)19:09
etoewsi see both of those are assigned to terrylhowe19:09
briancurtinrtheis_: that’s something we have to do but is mostly fine to just do right now. some more complex things will encounter the issue in …25719:10
terrylhoweI have the pathargs stuff out there for that19:10
terrylhoweit does resolve that problem, but the change wasn’t overly popular19:10
etoewscan we nail down the way forward for the path args stuff right now?19:10
briancurtinterrylhowe: i started looking back into that and how to tackle that while also thinking about the fact that we need URI props, body props, and header props, and they all do different things19:10
*** yamamoto has joined #openstack-meeting-319:10
*** yamamoto has quit IRC19:11
terrylhowedefinitely need something, not sure what the solution may be19:12
*** yamamoto has joined #openstack-meeting-319:12
briancurtinetoews: i don’t really think so. it’s probably the hardest problem we’ve encountered. the props being descriptors is on one hand a great thing, but it makes them slightly hard to discover how and when to do things with them based on type (since the type of those props is their internal value, not the fact that they’re some sort of prop)19:12
*** yamamoto has quit IRC19:12
briancurtini think some of what terrylhowe goes the right direction, so i’m going to look back over it and see how it can align with what we need since the review went up19:13
etoewsbut at the moment, briancurtin is working on it right?19:13
briancurtini don’t really have a good feeling or complete handle on how to solve it at the moment, though19:13
briancurtini am. i don’t believe terrylhowe is looking at it at the same time outside of his existing reviews19:14
*** galstrom_zzz is now known as galstrom19:14
*** ihrachys has quit IRC19:14
terrylhoweI haven’t put any time into it; I’ve been distracted by other things19:14
rtheis_I only looked at it briefly when trying to fix PoolMember: https://review.openstack.org/#/c/264980/19:15
*** bpokorny_ has quit IRC19:15
etoewsbriancurtin: beyond, just working the problem. is there anything else we can to help it move forward or remove roadblocks?19:15
*** yamamoto has joined #openstack-meeting-319:15
*** bpokorny has joined #openstack-meeting-319:15
briancurtinetoews: i’m going to look at how to break it up into smaller chunks, but since the change is so far reaching into the core of how resources work at all, i still don’t really know19:16
*** yamamoto has quit IRC19:16
etoewskk19:16
*** yamamoto has joined #openstack-meeting-319:17
terrylhoweGetting this change https://review.openstack.org/#/c/215785/11/openstack/resource.py19:17
*** salv-orlando has quit IRC19:17
terrylhowethrough, perhaps not using base_path_args19:17
*** salv-orlando has joined #openstack-meeting-319:18
terrylhoweand simply overriding the method where needed might be a good first step19:18
*** yamamoto has quit IRC19:18
briancurtinterrylhowe: that’s where i’m looking right now but trying to make it more discoverable than that. it’s pretty hard, so i’m probably going to come back to a similar idea to how you did that19:18
*** mrmartin has joined #openstack-meeting-319:19
*** yamamoto has joined #openstack-meeting-319:20
*** rockyg has quit IRC19:20
*** yamamoto has quit IRC19:21
etoewscan we go back to https://launchpad.net/python-openstacksdk/+milestone/1.0 and ask 3 questions of each open issue.19:21
etoews1. is the status correct?19:21
etoews2. is it assignee correct?19:21
etoews3. does it really need to be in 1.0?19:21
etoews4. what needs to be done to get it resolved?19:21
*** yamamoto has joined #openstack-meeting-319:22
etoews(make that 4 questions)19:22
briancurtinwas meaning to squeeze that in pre-meeting, but yeah. i’ll start listing them off and let’s talk19:22
briancurtin#topic https://bugs.launchpad.net/python-openstacksdk/+bug/1467732 - Improve server metadata usability19:23
*** openstack changes topic to "https://bugs.launchpad.net/python-openstacksdk/+bug/1467732 - Improve server metadata usability (Meeting topic: python-openstacksdk)"19:23
openstackLaunchpad bug 1467732 in OpenStack SDK "Improve server metadata usability" [Medium,In progress] - Assigned to Brian Curtin (brian.curtin)19:23
*** yamamoto has quit IRC19:23
*** yamamoto has joined #openstack-meeting-319:23
etoewsbriancurtin: since it's assigned to you, can you list off 1,2,3,4?19:24
briancurtin1. status correct, 2 assignee correct, 3 would be great because it’s currently not good, 4. it’s done but is not appropriately tied to this issue via commit message https://review.openstack.org/#/c/242694/19:24
briancurtinactually it *is* in the commit message there, but LP doesn’t show it19:24
briancurtinaiming +2’ed it19:24
briancurtinqiming19:24
etoewsso that one just needs review19:25
*** yamamoto has quit IRC19:25
briancurtinyep19:25
*** yamamoto has joined #openstack-meeting-319:25
* etoews just added self19:25
briancurtin#topic https://bugs.launchpad.net/python-openstacksdk/+bug/144025719:25
*** openstack changes topic to "https://bugs.launchpad.net/python-openstacksdk/+bug/1440257 (Meeting topic: python-openstacksdk)"19:26
openstackLaunchpad bug 1440257 in OpenStack SDK "Resource props of type=resource cause issue with basepath" [Critical,In progress] - Assigned to Brian Curtin (brian.curtin)19:26
*** yamamoto has quit IRC19:26
briancurtinwe just talked about that one, and i just bumped the priority up and assigned it to me since i’m looking at it19:26
briancurtin#topic https://bugs.launchpad.net/python-openstacksdk/+bug/145578319:26
*** openstack changes topic to "https://bugs.launchpad.net/python-openstacksdk/+bug/1455783 (Meeting topic: python-openstacksdk)"19:26
openstackLaunchpad bug 1455783 in OpenStack SDK "Make the SDK more OCC compatible" [High,In progress] - Assigned to Terry Howe (thowe-g)19:26
briancurtini don’t know what else may be needed there, but it seems to work ok19:26
*** yamamoto has joined #openstack-meeting-319:27
etoewsterrylhowe: can you list off 1,2,3,4 for that one?19:27
*** yamamoto has quit IRC19:27
*** yamamoto has joined #openstack-meeting-319:28
*** yamamoto has quit IRC19:29
*** vijendar has quit IRC19:29
etoewsterrylhowe: you around?19:30
*** MarkAtwo_ has joined #openstack-meeting-319:30
*** MarkAtwood has quit IRC19:30
terrylhoweyeh, I’m look at those tickets trying to figure out what is going on19:30
*** yamamoto has joined #openstack-meeting-319:30
etoewslet's just do one at a time19:30
etoewsstarting with the one above19:30
*** baoli has quit IRC19:31
*** yamamoto_ has joined #openstack-meeting-319:31
*** yamamoto has quit IRC19:31
*** mrmartin has quit IRC19:32
*** yamamoto_ has quit IRC19:32
*** ivar-lazzaro has quit IRC19:33
*** ivar-lazzaro has joined #openstack-meeting-319:33
*** yamamoto has joined #openstack-meeting-319:35
*** ivar-lazzaro has quit IRC19:35
*** yamamoto has quit IRC19:36
*** ivar-lazzaro has joined #openstack-meeting-319:36
etoewsterrylhowe: how much time do need to look into https://bugs.launchpad.net/python-openstacksdk/+bug/1455783 ?19:36
openstackLaunchpad bug 1455783 in OpenStack SDK "Make the SDK more OCC compatible" [High,In progress] - Assigned to Terry Howe (thowe-g)19:36
*** yamamoto has joined #openstack-meeting-319:37
terrylhowemaybe the solution to that is open other bugs for the other potential problems19:37
*** mrunge has quit IRC19:37
briancurtinworks for me. if any of that still exists it would be better as a concrete 1:1 bug to issue19:38
etoewsyes19:38
*** yamamoto has quit IRC19:38
terrylhoweinsecure, api versions, regions19:38
etoewsand i don't think they'd necessarily need to be 1.0 either19:38
*** yamamoto has joined #openstack-meeting-319:38
terrylhowekind of hard to verify they are bugs at the moment19:38
terrylhoweagreed19:38
etoewsterrylhowe: can you split that one into separate post-1.0 bugs and close 1455783?19:39
terrylhoweyeh19:39
etoews#action terrylhowe to split 1455783 into separate post-1.0 bugs and close 145578319:39
*** yamamoto has quit IRC19:39
briancurtin#topic https://bugs.launchpad.net/bugs/152651619:40
*** yamamoto has joined #openstack-meeting-319:40
*** openstack changes topic to "https://bugs.launchpad.net/bugs/1526516 (Meeting topic: python-openstacksdk)"19:40
openstackLaunchpad bug 1526516 in OpenStack SDK "Catch all ksa exceptions and map them to SDK exceptions" [Critical,In progress] - Assigned to Everett Toews (everett-toews)19:40
*** julim has quit IRC19:40
briancurtinetoews has a review out for that, i’ll look at the latest after this meeting19:40
*** armax has quit IRC19:40
*** mrmartin has joined #openstack-meeting-319:40
etoews1. correct 2. correct. 3. i guess 4. reviews.19:40
etoewslet's move on19:41
*** yamamoto has quit IRC19:41
*** julim has joined #openstack-meeting-319:41
briancurtin#topic https://bugs.launchpad.net/bugs/146120019:42
*** openstack changes topic to "https://bugs.launchpad.net/bugs/1461200 (Meeting topic: python-openstacksdk)"19:42
openstackLaunchpad bug 1461200 in OpenStack SDK "Create resource.props type=Resource for attributes with _id names" [Critical,In progress] - Assigned to Terry Howe (thowe-g)19:42
briancurtinthat one is assigned to terry, but anyone can take them on since they should be done per-service. i already started a few of them19:42
briancurtinthey’re reasonably easy to do as well. just find props in resources in a service that correspond to things with IDs, do the type=resource thing, update tests, should be good19:42
*** yamamoto has joined #openstack-meeting-319:43
*** Sukhdev has joined #openstack-meeting-319:43
*** zehicle_ has quit IRC19:44
briancurtinthose can probably be broken up as well, and i can take that on, creating an issue per remaining service to have it done to. that should be done pre-1.0 so we don’t have to change names on people afterward or to have to support two names at once, e.g., something_id and something19:44
briancurtin#action briancurtin split 1461200 into smaller issues19:44
*** yamamoto has quit IRC19:45
briancurtin#topic https://bugs.launchpad.net/bugs/146627919:45
*** openstack changes topic to "https://bugs.launchpad.net/bugs/1466279 (Meeting topic: python-openstacksdk)"19:45
openstackLaunchpad bug 1466279 in OpenStack SDK "ValidVersions.path not respected" [Critical,In progress] - Assigned to Brian Curtin (brian.curtin)19:45
*** yamamoto has joined #openstack-meeting-319:45
rtheis_briancurtin: Are you referring to stuff like this: subnet_pool = resource.prop('subnetpool_id', type=_subnet_pool.SubnetPool) for the previous bug?19:45
briancurtinyes19:45
rtheis_cool19:45
briancurtinon 279 i haven’t looked at this post-KSA so i’m going to unassign myself. this doesn’t need to be for 1.0 either if it is still in fact an issue19:46
*** yamamoto has quit IRC19:46
*** armax has joined #openstack-meeting-319:46
*** yamamoto has joined #openstack-meeting-319:47
briancurtin#topic https://bugs.launchpad.net/python-openstacksdk/+bug/148715019:47
*** openstack changes topic to "https://bugs.launchpad.net/python-openstacksdk/+bug/1487150 (Meeting topic: python-openstacksdk)"19:47
openstackLaunchpad bug 1487150 in OpenStack SDK "Object store set_object_metadata is a bit oddball" [Critical,In progress] - Assigned to Brian Curtin (brian.curtin)19:47
terrylhowehttps://bugs.launchpad.net/python-openstacksdk/+bug/145578319:47
openstackLaunchpad bug 1455783 in OpenStack SDK "Make the SDK more OCC compatible" [High,Fix released] - Assigned to Terry Howe (thowe-g)19:47
*** neelashah has joined #openstack-meeting-319:47
etoewsrtheis_: do you have some bandwidth to look at the smaller issues from 1461200 once brian creates them?19:47
terrylhowenow has references to the 3 new bugs19:47
*** yamamoto has quit IRC19:47
rtheis_etoews: Yes I can start with the network issue and go from there19:47
etoewsterrylhowe: do you want to make https://bugs.launchpad.net/python-openstacksdk/+bug/1455783 1.1?19:48
briancurtin123 correct, 4 it’s in progress somewhere, i’ll dig it up and make sure it’s appropriately tied to that issue. it’s an odd part of that proxy that i’d prefer to not have to change post-1.0 as it’d probably break people19:48
etoewsrtheis_: thanks!19:48
*** neelashah1 has quit IRC19:48
*** yamamoto has joined #openstack-meeting-319:48
rtheis_yw19:48
*** kebray has quit IRC19:48
terrylhoweetoews: I marked it released, we made some changes around that and released it19:49
briancurtin#topic https://bugs.launchpad.net/bugs/147447819:49
*** openstack changes topic to "https://bugs.launchpad.net/bugs/1474478 (Meeting topic: python-openstacksdk)"19:49
openstackLaunchpad bug 1474478 in OpenStack SDK "Why doesn't create update all attributes" [Critical,In progress] - Assigned to Brian Curtin (brian.curtin)19:49
*** yamamoto has quit IRC19:49
etoewsterrylhowe: cool.19:50
briancurtinthis is mostly correct except i’m unassigning myself. i had a little piece of code to fix it but i don’t think it’s pushed and i’m already assigned on enough stuff at the moment. i don’t think it’s too hard to fix but should be 1.0 if possible, ok if it slips19:50
*** yamamoto has joined #openstack-meeting-319:50
briancurtinactually it can just be 1.1 really19:50
*** neelashah1 has joined #openstack-meeting-319:50
briancurtinthat’s done19:51
briancurtin#topic https://bugs.launchpad.net/bugs/149449419:51
*** openstack changes topic to "https://bugs.launchpad.net/bugs/1494494 (Meeting topic: python-openstacksdk)"19:51
openstackLaunchpad bug 1494494 in OpenStack SDK "Expose the full URL to an object in object_store" [Medium,Confirmed]19:51
*** armax has quit IRC19:51
*** yamamoto has quit IRC19:51
briancurtini guess this can just be 1.1. would be nice to have since you have to otherwise construct the URLs yourself if you’re using this inside a web app or something. another that i haven’t looked at post-KSA19:51
*** yamamoto has joined #openstack-meeting-319:51
briancurtinnow marked as 1.1, everything else looks accurate on it19:52
*** neelashah has quit IRC19:52
briancurtin#topic https://bugs.launchpad.net/python-openstacksdk/+bug/151367919:52
*** openstack changes topic to "https://bugs.launchpad.net/python-openstacksdk/+bug/1513679 (Meeting topic: python-openstacksdk)"19:52
openstackLaunchpad bug 1513679 in OpenStack SDK "download_object needs to have the same API as get_object" [Critical,Confirmed]19:52
*** yamamoto has quit IRC19:52
*** bharathm has quit IRC19:52
briancurtinthat one is accurate in all forms: unassigned, critical, 1.0. don’t want to release and have to change the api on this one19:53
briancurtinand that marks the end of anything open on LP19:53
*** yamamoto has joined #openstack-meeting-319:53
etoewsgood19:53
*** neelashah has joined #openstack-meeting-319:54
*** neelashah1 has quit IRC19:54
briancurtinanything else to sneak in within the last few minutes?19:55
*** yamamoto_ has joined #openstack-meeting-319:55
etoewsanyone have the bandwidth to pick up https://bugs.launchpad.net/python-openstacksdk/+bug/1513679 ?19:55
openstackLaunchpad bug 1513679 in OpenStack SDK "download_object needs to have the same API as get_object" [Critical,Confirmed]19:55
*** yamamoto_ has quit IRC19:56
*** yamamoto_ has joined #openstack-meeting-319:56
etoewsbriancurtin: we missed https://bugs.launchpad.net/python-openstacksdk/+bug/146619219:57
openstackLaunchpad bug 1466192 in OpenStack SDK "Update contributor guide" [Critical,Confirmed] - Assigned to Brian Curtin (brian.curtin)19:57
*** neelashah1 has joined #openstack-meeting-319:57
briancurtinoh yeah. i think it’s generally accurate, just needs to be finished and pushed. can probably hack on that this week19:57
etoewsif you're not working on it right now, i'd say unassign to let someone else pick it up if they have the bandwidth19:57
etoewsseems to me you've got a pretty full plate as it is!19:58
*** yamamoto_ has quit IRC19:58
*** mrmartin has quit IRC19:58
etoewsi mean, unless you've got something that's 90% of the way there.19:58
*** yamamoto_ has joined #openstack-meeting-319:58
*** yamamoto has quit IRC19:58
*** neelashah has quit IRC19:58
*** yamamoto_ has quit IRC19:59
briancurtinit’s not 90% but i have some of it, and so much of it in my head, i just need to stop and breathe for a second and shift gears to write it all down. i should be able to have it up maybe thursday afternoon or so19:59
*** banix has quit IRC20:00
etoewsokay then20:00
*** yamamoto has joined #openstack-meeting-320:00
briancurtinthanks for coming everyone20:00
*** yamamoto has quit IRC20:00
rtheis_bye20:00
briancurtin#endmeeting20:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:01
openstackMeeting ended Tue Jan 12 20:01:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2016/python_openstacksdk.2016-01-12-19.01.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2016/python_openstacksdk.2016-01-12-19.01.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2016/python_openstacksdk.2016-01-12-19.01.log.html20:01
etoewsthanks. the road to 1.0 is much clearer.20:01
*** rockyg has joined #openstack-meeting-320:02
*** yamamoto has joined #openstack-meeting-320:02
*** yamamoto has quit IRC20:02
*** yamamoto has joined #openstack-meeting-320:03
*** banix has joined #openstack-meeting-320:03
*** yamamoto has quit IRC20:04
*** yamamoto has joined #openstack-meeting-320:05
*** yamamoto has quit IRC20:05
*** yamamoto has joined #openstack-meeting-320:08
*** quintela has quit IRC20:08
*** quintela has joined #openstack-meeting-320:09
*** yamamoto has quit IRC20:09
*** mfranc213 has quit IRC20:10
*** yamamoto has joined #openstack-meeting-320:10
*** mfranc213 has joined #openstack-meeting-320:10
*** yamamoto has quit IRC20:10
*** kebray has joined #openstack-meeting-320:12
*** shwetaap has quit IRC20:14
*** irenab_ has joined #openstack-meeting-320:16
*** yamamoto has joined #openstack-meeting-320:17
*** yamamoto has quit IRC20:17
*** yamamoto has joined #openstack-meeting-320:18
*** Sukhdev has quit IRC20:18
*** irenab has quit IRC20:18
*** irenab_ is now known as irenab20:18
*** yamamoto has quit IRC20:19
*** Swami has quit IRC20:20
*** yamamoto has joined #openstack-meeting-320:21
*** dslev has joined #openstack-meeting-320:22
*** bharathm has joined #openstack-meeting-320:22
*** piet has quit IRC20:22
*** yamamoto has quit IRC20:23
*** yamamoto has joined #openstack-meeting-320:23
*** yamamoto has quit IRC20:24
*** yamamoto has joined #openstack-meeting-320:25
*** dslev has quit IRC20:25
*** yamamoto has quit IRC20:27
*** yamamoto_ has joined #openstack-meeting-320:27
*** yamamoto_ has quit IRC20:28
*** yamamoto has joined #openstack-meeting-320:29
*** yamamoto has quit IRC20:29
*** yamamoto has joined #openstack-meeting-320:30
*** rbak has joined #openstack-meeting-320:30
*** yamamoto has quit IRC20:31
*** MarkAtwo_ has quit IRC20:31
*** yamamoto has joined #openstack-meeting-320:34
*** yamamoto has quit IRC20:34
*** yamamoto has joined #openstack-meeting-320:35
*** yamamoto has quit IRC20:37
*** yamamoto has joined #openstack-meeting-320:37
*** yamamoto has quit IRC20:38
*** yamamoto has joined #openstack-meeting-320:38
*** yamamoto has quit IRC20:39
*** salv-orlando has quit IRC20:39
*** yamamoto has joined #openstack-meeting-320:40
*** salv-orlando has joined #openstack-meeting-320:40
*** yamamoto has quit IRC20:41
*** bharathm has quit IRC20:41
*** yamamoto has joined #openstack-meeting-320:43
*** bharathm has joined #openstack-meeting-320:44
*** hdaniel_ has joined #openstack-meeting-320:45
*** yamamoto has quit IRC20:45
*** breton has left #openstack-meeting-320:45
*** yamamoto has joined #openstack-meeting-320:45
*** yamamoto has quit IRC20:46
*** rockyg has quit IRC20:46
*** yamamoto has joined #openstack-meeting-320:47
*** rbak has quit IRC20:47
*** yamamoto has quit IRC20:47
*** matrohon has joined #openstack-meeting-320:48
*** yamamoto has joined #openstack-meeting-320:50
*** rockyg has joined #openstack-meeting-320:50
*** yamamoto has quit IRC20:51
*** krtaylor has joined #openstack-meeting-320:55
*** yamamoto has joined #openstack-meeting-320:57
*** yamamoto has quit IRC20:58
*** yamamoto_ has joined #openstack-meeting-320:58
*** yamamoto_ has quit IRC20:59
*** yamamoto has joined #openstack-meeting-321:00
*** rbak has joined #openstack-meeting-321:00
*** armax has joined #openstack-meeting-321:01
*** yamamoto has quit IRC21:01
*** yamamoto has joined #openstack-meeting-321:02
*** yamamoto has quit IRC21:02
*** dslevin has joined #openstack-meeting-321:03
*** yamamoto has joined #openstack-meeting-321:03
*** dslevin has quit IRC21:04
*** bharathm has quit IRC21:04
*** yamamoto has quit IRC21:05
*** yamamoto has joined #openstack-meeting-321:05
*** yamamoto has quit IRC21:06
*** claudiub has joined #openstack-meeting-321:06
*** yamamoto has joined #openstack-meeting-321:07
*** bharathm has joined #openstack-meeting-321:08
*** yamamoto has quit IRC21:08
*** yamamoto_ has joined #openstack-meeting-321:08
*** krtaylor has quit IRC21:09
*** yamamoto_ has quit IRC21:10
*** yamamoto has joined #openstack-meeting-321:10
*** yamamoto has quit IRC21:12
*** sigmavirus24 is now known as sigmavirus24_awa21:12
*** yamamoto has joined #openstack-meeting-321:12
*** Swami has joined #openstack-meeting-321:12
*** yamamoto has quit IRC21:13
*** hdaniel_ has quit IRC21:13
*** sigmavirus24_awa is now known as sigmavirus2421:13
*** armax has quit IRC21:13
*** yamamoto has joined #openstack-meeting-321:14
*** yamamoto has quit IRC21:14
*** yamamoto has joined #openstack-meeting-321:15
*** yamamoto has quit IRC21:16
*** yamamoto has joined #openstack-meeting-321:17
*** kebray has quit IRC21:17
*** neelashah1 has quit IRC21:17
*** yamamoto has quit IRC21:18
*** jtomasek has quit IRC21:18
*** yamamoto_ has joined #openstack-meeting-321:18
*** yamamoto_ has quit IRC21:19
*** yamamoto has joined #openstack-meeting-321:20
*** yamamoto has quit IRC21:21
*** yamamoto has joined #openstack-meeting-321:21
*** terrylhowe has left #openstack-meeting-321:22
*** yamamoto has quit IRC21:23
*** kebray has joined #openstack-meeting-321:25
*** yamamoto has joined #openstack-meeting-321:25
*** yamamoto has quit IRC21:26
*** yamamoto has joined #openstack-meeting-321:29
*** kzaitsev_mb has quit IRC21:29
*** yamamoto has quit IRC21:30
*** dslevin has joined #openstack-meeting-321:30
*** yamamoto has joined #openstack-meeting-321:32
*** yamamoto has quit IRC21:33
*** yamamoto has joined #openstack-meeting-321:34
*** yamamoto has quit IRC21:34
*** yamamoto has joined #openstack-meeting-321:35
*** yamahata has quit IRC21:36
*** yamamoto has quit IRC21:36
*** yamamoto has joined #openstack-meeting-321:37
*** bharathm has quit IRC21:38
*** rbak has quit IRC21:38
*** yamamoto has quit IRC21:38
*** yamamoto has joined #openstack-meeting-321:38
*** yamamoto has quit IRC21:40
*** yamamoto has joined #openstack-meeting-321:40
*** rbak has joined #openstack-meeting-321:41
*** bharathm has joined #openstack-meeting-321:41
*** salv-orlando has quit IRC21:43
*** yamamoto_ has joined #openstack-meeting-321:43
*** salv-orlando has joined #openstack-meeting-321:44
*** yamamoto_ has quit IRC21:44
*** yamamoto_ has joined #openstack-meeting-321:45
*** yamamoto has quit IRC21:45
*** yamamoto_ has quit IRC21:46
*** yamamoto has joined #openstack-meeting-321:47
*** baoli has joined #openstack-meeting-321:47
*** yamamoto has quit IRC21:47
*** neelashah has joined #openstack-meeting-321:48
*** yamamoto has joined #openstack-meeting-321:48
*** julim has quit IRC21:49
*** rbak has quit IRC21:49
*** rbak has joined #openstack-meeting-321:49
*** yamamoto has quit IRC21:50
*** yamamoto has joined #openstack-meeting-321:50
*** yamamoto has quit IRC21:51
*** yamamoto has joined #openstack-meeting-321:52
*** kebray has quit IRC21:52
*** yamamoto has quit IRC21:53
*** spzala has quit IRC21:53
*** yamamoto has joined #openstack-meeting-321:53
*** spzala has joined #openstack-meeting-321:54
*** rockyg has quit IRC21:54
*** yamamoto has quit IRC21:56
*** belmoreira has joined #openstack-meeting-321:56
*** rbak has quit IRC21:56
*** spzala has quit IRC21:58
*** MarkAtwood has joined #openstack-meeting-321:58
*** rbak has joined #openstack-meeting-321:58
*** baoli has quit IRC21:58
*** baoli has joined #openstack-meeting-321:59
*** neelashah has quit IRC22:01
*** spzala has joined #openstack-meeting-322:01
*** mfranc213 has quit IRC22:02
*** vhoward has quit IRC22:04
*** neelashah has joined #openstack-meeting-322:04
*** krtaylor has joined #openstack-meeting-322:05
*** kebray has joined #openstack-meeting-322:06
*** bharathm has quit IRC22:08
*** davidlenwell has quit IRC22:09
*** salv-orl_ has joined #openstack-meeting-322:09
*** baoli has quit IRC22:10
*** baoli has joined #openstack-meeting-322:11
*** lblanchard has quit IRC22:11
*** lblanchard has joined #openstack-meeting-322:11
*** davidlenwell has joined #openstack-meeting-322:11
*** vgridnev has quit IRC22:12
*** salv-orlando has quit IRC22:12
*** rbak has quit IRC22:12
*** bharathm has joined #openstack-meeting-322:14
*** matrohon has quit IRC22:14
*** yamahata has joined #openstack-meeting-322:14
*** dims has quit IRC22:15
*** rtheis_ has quit IRC22:16
*** lblanchard has quit IRC22:17
*** neelashah has quit IRC22:17
*** neelashah has joined #openstack-meeting-322:18
*** peristeri has quit IRC22:20
*** baoli has quit IRC22:22
*** baoli has joined #openstack-meeting-322:22
*** bharathm has quit IRC22:25
*** bharathm has joined #openstack-meeting-322:26
*** piet has joined #openstack-meeting-322:30
*** kebray has quit IRC22:33
*** baoli has quit IRC22:34
*** baoli has joined #openstack-meeting-322:34
*** belmoreira has quit IRC22:36
*** kebray has joined #openstack-meeting-322:40
*** armax has joined #openstack-meeting-322:42
*** Swami has quit IRC22:46
*** baoli has quit IRC22:46
*** baoli has joined #openstack-meeting-322:47
*** bharathm has quit IRC22:47
*** bharathm has joined #openstack-meeting-322:48
*** piet has quit IRC22:51
*** rossella_s has quit IRC22:52
*** rossella_s has joined #openstack-meeting-322:52
*** eliqiao has quit IRC22:54
*** bharathm has quit IRC22:54
*** eliqiao has joined #openstack-meeting-322:55
*** bharathm has joined #openstack-meeting-322:57
*** baoli has quit IRC22:58
*** baoli has joined #openstack-meeting-322:58
*** sigmavirus24 is now known as sigmavirus24_awa23:01
*** mfranc213 has joined #openstack-meeting-323:03
*** armax has quit IRC23:05
*** armax has joined #openstack-meeting-323:06
*** markmcclain has quit IRC23:07
*** mfranc213 has quit IRC23:07
*** markmcclain has joined #openstack-meeting-323:09
*** armax has quit IRC23:10
*** baoli has quit IRC23:10
*** baoli has joined #openstack-meeting-323:10
*** armax has joined #openstack-meeting-323:11
*** kebray has quit IRC23:11
*** armax has quit IRC23:11
*** kebray has joined #openstack-meeting-323:12
*** davidlenwell has quit IRC23:17
*** davidlenwell has joined #openstack-meeting-323:18
*** armax has joined #openstack-meeting-323:18
*** Sukhdev has joined #openstack-meeting-323:22
*** baoli has quit IRC23:22
*** baoli has joined #openstack-meeting-323:23
*** MarkAtwood has quit IRC23:24
*** neelashah has quit IRC23:24
*** markmcclain has quit IRC23:25
*** markmcclain has joined #openstack-meeting-323:26
*** e0ne has quit IRC23:26
*** dimtruck is now known as zz_dimtruck23:28
*** eliqiao has quit IRC23:31
*** eliqiao has joined #openstack-meeting-323:32
*** armax has quit IRC23:34
*** baoli has quit IRC23:34
*** baoli has joined #openstack-meeting-323:35
*** spzala has quit IRC23:35
*** armax has joined #openstack-meeting-323:35
*** spzala has joined #openstack-meeting-323:36
*** sigmavirus24_awa is now known as sigmavirus2423:38
*** armax has quit IRC23:40
*** spzala has quit IRC23:40
*** armax has joined #openstack-meeting-323:41
*** spzala has joined #openstack-meeting-323:43
*** spzala has quit IRC23:43
*** spzala has joined #openstack-meeting-323:44
*** armax has quit IRC23:44
*** sdake has quit IRC23:45
*** armax has joined #openstack-meeting-323:45
*** baoli has quit IRC23:46
*** baoli has joined #openstack-meeting-323:47
*** armax has quit IRC23:47
*** sigmavirus24 is now known as sigmavirus24_awa23:47
*** armax has joined #openstack-meeting-323:47
*** sigmavirus24_awa is now known as sigmavirus2423:48
*** spzala has quit IRC23:48
*** armax has quit IRC23:51
*** galstrom is now known as galstrom_zzz23:55
*** bpokorny_ has joined #openstack-meeting-323:55
*** spzala has joined #openstack-meeting-323:56
*** piet has joined #openstack-meeting-323:57
*** baoli has quit IRC23:58
*** bpokorny has quit IRC23:59
*** bharathm has quit IRC23:59
*** baoli has joined #openstack-meeting-323:59

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