Thursday, 2016-01-28

*** Sukhdev has joined #openstack-meeting-300:00
*** Sukhdev has quit IRC00:01
*** Sukhdev has joined #openstack-meeting-300:01
*** vishwana_ has joined #openstack-meeting-300:02
*** Sukhdev_ has joined #openstack-meeting-300:04
*** Sukhdev has quit IRC00:05
*** Sukhdev_ has quit IRC00:05
*** Sukhdev has joined #openstack-meeting-300:06
*** vishwanathj has quit IRC00:06
*** rhochmuth has quit IRC00:06
*** Sukhdev has quit IRC00:07
*** Sukhdev has joined #openstack-meeting-300:07
*** tyr_ has quit IRC00:10
*** alexpilotti has joined #openstack-meeting-300:11
*** Sukhdev_ has joined #openstack-meeting-300:11
*** Sukhdev has quit IRC00:12
*** vishwanathj has joined #openstack-meeting-300:14
*** salv-orl_ has quit IRC00:15
*** alexpilotti has quit IRC00:15
*** Sukhdev has joined #openstack-meeting-300:15
*** Sukhdev_ has quit IRC00:16
*** vishwana_ has quit IRC00:16
*** Sukhdev has quit IRC00:17
*** Sukhdev has joined #openstack-meeting-300:18
*** Sukhdev has quit IRC00:20
*** Sukhdev has joined #openstack-meeting-300:20
*** Sukhdev_ has joined #openstack-meeting-300:24
*** sdake has joined #openstack-meeting-300:24
*** Sukhdev has quit IRC00:25
*** Sukhdev_ has quit IRC00:25
*** Sukhdev has joined #openstack-meeting-300:25
*** FallenPegasus has quit IRC00:27
*** Sukhdev has quit IRC00:27
*** Sukhdev has joined #openstack-meeting-300:28
*** sdake_ has joined #openstack-meeting-300:28
*** sdake has quit IRC00:29
*** Sukhdev_ has joined #openstack-meeting-300:30
*** Sukhdev has quit IRC00:30
*** sdake has joined #openstack-meeting-300:30
*** Sukhdev_ has quit IRC00:32
*** alexpilotti has joined #openstack-meeting-300:32
*** Sukhdev has joined #openstack-meeting-300:32
*** baoli has joined #openstack-meeting-300:33
*** sdake_ has quit IRC00:33
*** Sukhdev has quit IRC00:33
*** banix has joined #openstack-meeting-300:34
*** mbound has quit IRC00:34
*** Sukhdev has joined #openstack-meeting-300:34
*** alexpilo_ has joined #openstack-meeting-300:35
*** baoli has quit IRC00:35
*** Sukhdev has quit IRC00:35
*** sdake_ has joined #openstack-meeting-300:35
*** Sukhdev has joined #openstack-meeting-300:36
*** alexpilotti has quit IRC00:36
*** Sukhdev has quit IRC00:37
*** Sukhdev has joined #openstack-meeting-300:37
*** sdake has quit IRC00:38
*** Sukhdev has quit IRC00:39
*** alexpilo_ has quit IRC00:39
*** Sukhdev has joined #openstack-meeting-300:39
*** Swami has quit IRC00:40
*** Sukhdev has quit IRC00:41
*** Sukhdev has joined #openstack-meeting-300:41
*** mbound has joined #openstack-meeting-300:42
*** Sukhdev has quit IRC00:43
*** Sukhdev has joined #openstack-meeting-300:43
*** zhurong has joined #openstack-meeting-300:44
*** hoangcx has joined #openstack-meeting-300:44
*** Sukhdev has quit IRC00:44
*** mbound has quit IRC00:44
*** Sukhdev has joined #openstack-meeting-300:45
*** Sukhdev has quit IRC00:46
*** Sukhdev has joined #openstack-meeting-300:47
*** Sukhdev has quit IRC00:48
*** Sukhdev has joined #openstack-meeting-300:48
*** Sukhdev_ has joined #openstack-meeting-300:50
*** Sukhdev has quit IRC00:50
*** zhurong has quit IRC00:51
*** hoangcx has quit IRC00:52
*** hoangcx has joined #openstack-meeting-300:52
*** Sukhdev_ has quit IRC00:52
*** zz_dimtruck is now known as dimtruck00:52
*** Sukhdev has joined #openstack-meeting-300:52
*** hoangcx has quit IRC00:53
*** hoangcx has joined #openstack-meeting-300:53
*** Sukhdev has quit IRC00:54
*** Sukhdev has joined #openstack-meeting-300:54
*** dims_ has quit IRC00:55
*** baoli has joined #openstack-meeting-300:55
*** Sukhdev_ has joined #openstack-meeting-300:56
*** Sukhdev has quit IRC00:56
*** dimtruck is now known as zz_dimtruck00:57
*** Sukhdev_ has quit IRC00:59
*** Sukhdev has joined #openstack-meeting-301:00
*** neelashah has joined #openstack-meeting-301:05
*** bpokorny has quit IRC01:05
*** Aish has quit IRC01:06
*** Sukhdev has quit IRC01:08
*** Sukhdev has joined #openstack-meeting-301:08
*** vahidh__ has quit IRC01:14
*** vahidh has joined #openstack-meeting-301:18
*** dixiaoli has quit IRC01:21
*** ivar-lazzaro has joined #openstack-meeting-301:22
*** baoli_ has joined #openstack-meeting-301:22
*** ivar-laz_ has quit IRC01:25
*** baoli has quit IRC01:25
*** baoli_ has quit IRC01:31
*** baoli has joined #openstack-meeting-301:31
*** neiljerram has joined #openstack-meeting-301:33
*** alexpilotti has joined #openstack-meeting-301:34
*** vahidh has quit IRC01:38
*** vahidh has joined #openstack-meeting-301:39
*** alexpilotti has quit IRC01:39
*** neiljerram has quit IRC01:40
*** vahidh has quit IRC01:43
*** stanzgy has joined #openstack-meeting-301:45
*** mbound has joined #openstack-meeting-301:45
*** yamamoto_ has joined #openstack-meeting-301:45
*** mickeys has quit IRC01:45
*** salv-orlando has joined #openstack-meeting-301:47
*** shakamunyi has joined #openstack-meeting-301:48
*** sdake_ has quit IRC01:49
*** mbound has quit IRC01:50
*** salv-orlando has quit IRC01:57
*** mtanino has quit IRC01:58
*** baohua has joined #openstack-meeting-301:58
*** yamamoto_ has quit IRC02:03
*** yamamoto_ has joined #openstack-meeting-302:04
*** zhurong has joined #openstack-meeting-302:08
*** yamamoto_ has quit IRC02:09
*** shakamunyi has quit IRC02:10
*** shakamunyi has joined #openstack-meeting-302:10
*** yamamoto_ has joined #openstack-meeting-302:10
*** madhu_ak has quit IRC02:13
*** dixiaoli has joined #openstack-meeting-302:21
*** tobe has joined #openstack-meeting-302:22
*** rocky_g has joined #openstack-meeting-302:23
*** yamamoto_ has quit IRC02:24
*** woodster_ has quit IRC02:26
*** sdake has joined #openstack-meeting-302:29
*** sdake has quit IRC02:29
*** fawadkhaliq has joined #openstack-meeting-302:37
*** bpokorny has joined #openstack-meeting-302:40
*** e0ne has joined #openstack-meeting-302:41
*** ivar-lazzaro has quit IRC02:43
*** ivar-lazzaro has joined #openstack-meeting-302:43
*** s3wong has quit IRC02:46
*** ivar-lazzaro has quit IRC02:48
*** e0ne has quit IRC02:48
*** e0ne has joined #openstack-meeting-302:50
*** kebray has joined #openstack-meeting-302:53
*** e0ne_ has joined #openstack-meeting-302:54
*** e0ne has quit IRC02:55
*** sdake has joined #openstack-meeting-302:55
*** zhurong has quit IRC02:55
*** bpokorny_ has joined #openstack-meeting-302:56
*** amotoki has quit IRC02:59
*** bpokorny has quit IRC03:00
*** bpokorny_ has quit IRC03:01
*** zhurong has joined #openstack-meeting-303:02
*** piet has joined #openstack-meeting-303:06
*** dixiaoli_ has joined #openstack-meeting-303:09
*** Sukhdev has quit IRC03:12
*** dixiaoli has quit IRC03:12
*** baoli has quit IRC03:12
*** yamamoto has joined #openstack-meeting-303:13
*** baoli has joined #openstack-meeting-303:14
*** rocky_g has quit IRC03:15
*** baojg has joined #openstack-meeting-303:15
*** yamahata has quit IRC03:16
*** iyamahat has quit IRC03:16
*** baojg has quit IRC03:16
*** amotoki has joined #openstack-meeting-303:27
*** amotoki has quit IRC03:32
*** shwetaap has joined #openstack-meeting-303:35
*** Poornima has joined #openstack-meeting-303:35
*** fitoduarte has quit IRC03:40
*** salv-orlando has joined #openstack-meeting-303:43
*** Poornima has quit IRC03:43
*** FallenPegasus has joined #openstack-meeting-303:46
*** MarkAtwood has joined #openstack-meeting-303:46
*** e0ne_ has quit IRC03:48
*** fawadkhaliq has quit IRC03:49
*** amotoki has joined #openstack-meeting-303:49
*** sdake_ has joined #openstack-meeting-303:50
*** sdake has quit IRC03:51
*** vishwanathj has quit IRC03:53
*** coolsvap|away is now known as coolsvap03:54
*** salv-orlando has quit IRC03:56
*** MarkAtwood has quit IRC03:58
*** Poornima has joined #openstack-meeting-303:59
*** amotoki has quit IRC04:03
*** baoli has quit IRC04:04
*** sdake_ is now known as sdake04:05
*** e0ne has joined #openstack-meeting-304:08
*** tej has joined #openstack-meeting-304:12
*** tej has quit IRC04:16
*** yamahata has joined #openstack-meeting-304:17
*** amotoki has joined #openstack-meeting-304:20
*** hurgleburgler has joined #openstack-meeting-304:24
*** Poornima has quit IRC04:24
*** Poornima has joined #openstack-meeting-304:26
*** Sukhdev has joined #openstack-meeting-304:26
*** hurgleburgler has quit IRC04:32
*** banix has quit IRC04:39
*** lazy_prince has joined #openstack-meeting-304:42
*** e0ne has quit IRC04:44
*** bpokorny has joined #openstack-meeting-304:46
*** fitoduarte has joined #openstack-meeting-304:49
*** coolsvap is now known as coolsvap|away04:51
*** baoli has joined #openstack-meeting-304:54
*** yushiro has joined #openstack-meeting-304:58
*** yushiro has left #openstack-meeting-304:58
*** coolsvap|away is now known as coolsvap04:59
*** baoli has quit IRC04:59
*** alexpilotti has joined #openstack-meeting-305:12
*** alexpilotti has quit IRC05:16
*** vahidh has joined #openstack-meeting-305:19
*** Aish has joined #openstack-meeting-305:30
*** fawadkhaliq has joined #openstack-meeting-305:32
*** Aish has left #openstack-meeting-305:33
*** baojg has joined #openstack-meeting-305:37
*** vishwanathj has joined #openstack-meeting-305:41
*** vishwanathj is now known as vishwanathj_zzz05:43
*** fawadkhaliq has quit IRC05:45
*** sdake_ has joined #openstack-meeting-305:48
*** sdake has quit IRC05:49
*** piet has quit IRC05:54
*** fitoduarte has quit IRC05:54
*** shwetaap has quit IRC05:55
*** shwetaap has joined #openstack-meeting-305:55
*** shwetaap has quit IRC05:55
*** vahidh has quit IRC05:57
*** sdake_ has quit IRC06:00
*** sdake has joined #openstack-meeting-306:01
*** bpokorny has quit IRC06:03
*** piet has joined #openstack-meeting-306:04
*** sdake_ has joined #openstack-meeting-306:08
*** FallenPegasus has quit IRC06:09
*** sdake has quit IRC06:10
*** alexpilotti has joined #openstack-meeting-306:11
*** iyamahat has joined #openstack-meeting-306:15
*** alexpilotti has quit IRC06:15
*** baohua has quit IRC06:19
*** fawadkhaliq has joined #openstack-meeting-306:19
*** baohua has joined #openstack-meeting-306:19
*** iyamahat has quit IRC06:21
*** hdaniel has joined #openstack-meeting-306:25
*** irenab has quit IRC06:27
*** jwarendt has quit IRC06:28
*** tfukushima has joined #openstack-meeting-306:29
*** rossella_s has quit IRC06:31
*** piet has quit IRC06:31
*** rossella_s has joined #openstack-meeting-306:31
*** salv-orlando has joined #openstack-meeting-306:38
*** numans has joined #openstack-meeting-306:40
*** piet has joined #openstack-meeting-306:40
*** nkrinner has joined #openstack-meeting-306:46
*** hoangcx has quit IRC06:49
*** salv-orlando has quit IRC06:49
*** piet has quit IRC06:53
*** vahidh has joined #openstack-meeting-306:56
*** vahidh has quit IRC06:57
*** irenab has joined #openstack-meeting-307:02
*** zhurong has quit IRC07:06
*** zhurong has joined #openstack-meeting-307:07
*** neelashah has quit IRC07:07
*** kebray has quit IRC07:08
*** evgenyf has joined #openstack-meeting-307:17
*** hdaniel has quit IRC07:21
*** Sukhdev has quit IRC07:21
*** egallen has joined #openstack-meeting-307:25
*** salv-orlando has joined #openstack-meeting-307:26
*** alexpilotti has joined #openstack-meeting-307:34
*** alexpilotti has quit IRC07:38
*** egallen has quit IRC07:45
*** kavit__ has joined #openstack-meeting-307:53
*** kavit_ has quit IRC07:57
*** belmoreira has joined #openstack-meeting-307:59
*** coolsvap is now known as coolsvap|away08:00
*** amotoki has quit IRC08:07
*** salv-orlando has quit IRC08:10
*** alexpilotti has joined #openstack-meeting-308:10
*** hdaniel has joined #openstack-meeting-308:12
*** jwang_ has joined #openstack-meeting-308:15
*** alexpilotti has quit IRC08:15
*** nkrinner has quit IRC08:15
*** amotoki has joined #openstack-meeting-308:16
*** moshele has joined #openstack-meeting-308:16
*** barra204 has joined #openstack-meeting-308:17
*** amotoki has quit IRC08:18
*** hdaniel has quit IRC08:18
*** rockyg has quit IRC08:19
*** shakamunyi has quit IRC08:19
*** jwang has quit IRC08:19
*** rmoe has quit IRC08:19
*** sdake_ has quit IRC08:19
*** nkrinner has joined #openstack-meeting-308:19
*** rmoe has joined #openstack-meeting-308:19
*** numans has quit IRC08:19
*** numans has joined #openstack-meeting-308:20
*** sdake has joined #openstack-meeting-308:21
*** itxaka has joined #openstack-meeting-308:29
*** jlanoux has joined #openstack-meeting-308:29
*** egallen has joined #openstack-meeting-308:29
*** alexpilotti has joined #openstack-meeting-308:34
*** hdaniel has joined #openstack-meeting-308:34
*** dixiaoli has joined #openstack-meeting-308:35
*** dixiaoli_ has quit IRC08:35
*** vtech has joined #openstack-meeting-308:37
*** alexpilotti has quit IRC08:38
*** sdake has quit IRC08:40
*** iyamahat has joined #openstack-meeting-308:40
*** amotoki has joined #openstack-meeting-308:42
*** sdake has joined #openstack-meeting-308:47
*** baohua has quit IRC08:54
*** armax has quit IRC08:54
*** ihrachys has joined #openstack-meeting-308:54
*** mbound has joined #openstack-meeting-308:54
*** hoangcx has joined #openstack-meeting-308:55
*** baohua has joined #openstack-meeting-308:55
*** hdaniel_ has joined #openstack-meeting-308:59
*** hdaniel has quit IRC09:01
*** jaypipes has joined #openstack-meeting-309:01
*** safchain has joined #openstack-meeting-309:05
*** vahidh has joined #openstack-meeting-309:09
*** alexpilotti has joined #openstack-meeting-309:10
*** jlanoux has quit IRC09:10
*** vtech has quit IRC09:11
*** ihrachys has quit IRC09:11
*** salv-orlando has joined #openstack-meeting-309:11
*** ihrachys has joined #openstack-meeting-309:11
*** vgridnev has joined #openstack-meeting-309:14
*** vahidh has quit IRC09:14
*** alexpilotti has quit IRC09:15
*** matrohon has joined #openstack-meeting-309:15
*** vtech has joined #openstack-meeting-309:16
*** vtech has quit IRC09:16
*** ihrachys has quit IRC09:17
*** vtech has joined #openstack-meeting-309:17
*** jlanoux has joined #openstack-meeting-309:19
*** dedery has joined #openstack-meeting-309:19
*** ihrachys has joined #openstack-meeting-309:19
*** iyamahat has quit IRC09:20
*** baojg has quit IRC09:23
*** armax has joined #openstack-meeting-309:23
*** dedery has quit IRC09:25
*** tmazur has joined #openstack-meeting-309:26
*** baohua has quit IRC09:29
*** alexpilotti has joined #openstack-meeting-309:33
*** zhurong has quit IRC09:37
*** alexpilotti has quit IRC09:37
*** baojg has joined #openstack-meeting-309:40
*** ihrachys_ has joined #openstack-meeting-309:52
*** ihrachys has quit IRC09:53
*** fawadkhaliq has quit IRC09:57
*** fawadkhaliq has joined #openstack-meeting-309:58
*** iyamahat has joined #openstack-meeting-310:01
*** salv-orl_ has joined #openstack-meeting-310:06
*** dedery has joined #openstack-meeting-310:09
*** salv-orlando has quit IRC10:09
*** JeanBriceCombebi has joined #openstack-meeting-310:12
*** iyamahat has quit IRC10:14
*** ihrachys_ has quit IRC10:14
*** tmazur has quit IRC10:14
*** ihrachys has joined #openstack-meeting-310:16
*** ihrachys has quit IRC10:17
*** ihrachys has joined #openstack-meeting-310:21
*** dedery_ has joined #openstack-meeting-310:25
*** dedery has quit IRC10:26
*** alexpilotti has joined #openstack-meeting-310:29
*** alexpilotti has quit IRC10:30
*** yamamoto has quit IRC10:30
*** ihrachys has quit IRC10:35
*** ihrachys has joined #openstack-meeting-310:35
*** mickeys has joined #openstack-meeting-310:39
*** fawadkhaliq has quit IRC10:42
*** fawadkhaliq has joined #openstack-meeting-310:42
*** mickeys has quit IRC10:49
*** yamahata has quit IRC10:50
*** hoangcx has quit IRC11:04
*** jaypipes has quit IRC11:06
*** dims has joined #openstack-meeting-311:07
*** jaypipes has joined #openstack-meeting-311:14
*** vtech has quit IRC11:14
*** sergek has quit IRC11:17
*** baohua has joined #openstack-meeting-311:31
*** armax has quit IRC11:34
*** salv-orl_ has quit IRC11:34
*** JeanBriceCombebi has quit IRC11:38
*** baojg has quit IRC11:39
*** tobe has quit IRC11:41
*** baohua has quit IRC11:42
*** dedery_ has quit IRC11:43
*** baohua has joined #openstack-meeting-311:43
*** davidsha has joined #openstack-meeting-311:43
*** dedery has joined #openstack-meeting-311:43
*** dedery_ has joined #openstack-meeting-311:45
*** dedery_ has quit IRC11:47
*** tfukushima has quit IRC11:47
*** dedery_ has joined #openstack-meeting-311:48
*** dedery has quit IRC11:48
*** doug-fish has joined #openstack-meeting-311:49
*** dedery_ has quit IRC11:52
*** dedery has joined #openstack-meeting-311:52
*** dedery has quit IRC11:57
*** egallen has quit IRC11:58
*** sergek has joined #openstack-meeting-312:00
*** kzaitsev_mb has joined #openstack-meeting-312:02
*** zhurong has joined #openstack-meeting-312:04
*** e0ne has joined #openstack-meeting-312:06
*** stanzgy has quit IRC12:11
*** vtech has joined #openstack-meeting-312:14
*** alexpilotti has joined #openstack-meeting-312:15
*** neiljerram has joined #openstack-meeting-312:15
*** rtheis has joined #openstack-meeting-312:16
*** armax has joined #openstack-meeting-312:17
*** alexpilotti has quit IRC12:19
*** salv-orlando has joined #openstack-meeting-312:21
*** e0ne has quit IRC12:27
*** e0ne has joined #openstack-meeting-312:27
*** armax has quit IRC12:28
*** jlanoux has quit IRC12:28
*** ihrachys_ has joined #openstack-meeting-312:29
*** ihrachys has quit IRC12:30
*** cbouch has joined #openstack-meeting-312:33
*** tobe has joined #openstack-meeting-312:41
*** egallen has joined #openstack-meeting-312:41
*** amotoki_ has joined #openstack-meeting-312:41
*** Poornima has quit IRC12:41
*** amotoki has quit IRC12:43
*** davidsha has quit IRC12:45
*** piet has joined #openstack-meeting-312:45
*** dims has quit IRC12:47
*** ihrachys_ has quit IRC12:49
*** ihrachys has joined #openstack-meeting-312:49
*** ihrachys has quit IRC12:50
*** ihrachys has joined #openstack-meeting-312:50
*** zhurong has quit IRC12:51
*** ihrachys has quit IRC12:51
*** piet has quit IRC12:52
*** nelsnels_ has quit IRC12:53
*** piet has joined #openstack-meeting-312:53
*** dedery has joined #openstack-meeting-312:53
*** baoli_ has joined #openstack-meeting-312:58
*** dedery has quit IRC12:59
*** dedery has joined #openstack-meeting-313:02
*** tobe has quit IRC13:09
*** jlanoux has joined #openstack-meeting-313:10
*** dedery_ has joined #openstack-meeting-313:10
*** alexpilotti has joined #openstack-meeting-313:13
*** dedery has quit IRC13:14
*** dedery_ has quit IRC13:15
*** sdake has quit IRC13:16
*** hdaniel_ has quit IRC13:17
*** fawadkhaliq has quit IRC13:17
*** fawadkhaliq has joined #openstack-meeting-313:17
*** sdake has joined #openstack-meeting-313:18
*** yamamoto has joined #openstack-meeting-313:19
*** davidsha has joined #openstack-meeting-313:22
*** baoli_ has quit IRC13:29
*** e0ne has quit IRC13:29
*** dixiaoli_ has joined #openstack-meeting-313:37
*** zhurong has joined #openstack-meeting-313:41
*** neiljerram has quit IRC13:46
*** neiljerram has joined #openstack-meeting-313:54
*** AndreyPavlov has joined #openstack-meeting-313:55
*** peristeri has joined #openstack-meeting-313:58
SergeyLukjanovhey sahara folks13:58
*** jed56 has joined #openstack-meeting-313:58
*** tosky has joined #openstack-meeting-313:59
*** mionkin has joined #openstack-meeting-313:59
elmikohi13:59
*** egafford has joined #openstack-meeting-314:00
*** esikachev has joined #openstack-meeting-314:00
*** huichun has joined #openstack-meeting-314:00
SergeyLukjanov#startmeeting sahara14:00
openstackMeeting started Thu Jan 28 14:00:34 2016 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
NikitaKonovalovo/14:00
egaffordo/14:00
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
toskyhi14:00
AndreyPavlovhi14:00
esikachevhi14:00
SergeyLukjanovelmiko saharaclient tests blocked by the patch to tempest that are fixing heat tests14:00
mionkinhi14:00
huichunhi14:01
*** vikram_ has joined #openstack-meeting-314:01
*** vikram_ has quit IRC14:01
SergeyLukjanovsreshetnyak ping, could you please confirm?14:01
*** vikram_ has joined #openstack-meeting-314:01
*** tmckay has joined #openstack-meeting-314:01
SergeyLukjanov#topic News / updates14:01
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:01
elmikoSergeyLukjanov: ack, i just saw the email (thanks tosky)14:01
SergeyLukjanovsorry, just wake up, not yet read email14:02
toskymaybe it's a different issue?14:02
toskythe one I mentioned on the channel is about kilo branch14:02
elmikoi've been doing a bunch of api v2 stuff, and working on releasing a security bug (have been researching the effects of the vulnerability), also looking at doing more bandit based cleanup.14:02
toskyI put the item on the agenda14:02
AndreyPavlovwas working on bug with fields unset via client, on periodic tasks spec and cli import/export spec14:02
tmckayI revived the discussion about substring searches on sahara objects ,,,14:02
elmikoSergeyLukjanov: oh right, you meant about the patch i added yesterday for saharaclient?14:02
elmikotosky: saw that, thanks!14:03
esikachevi am working on adding sahara-ci for stable releases of sahara in sahara-scenario repo14:03
egaffordNot much upstream progress on Sahara this week I fear; diving back in today.14:03
SergeyLukjanovelmiko not sure, browser crashed and I lost all links ;)14:04
sreshetnyakSergeyLukjanov: I think that tests blocked by problems with installing sahara14:04
SergeyLukjanovsreshetnyak it's about stable branch I think, I'm talking about sahara client14:04
SergeyLukjanovI've been unable to work on the summit proposals, will do it today for sure elmiko tmckay egafford14:05
vgridnevI've been working on implementation of health checks, let's review the spec: https://review.openstack.org/#/c/270156/14:05
huichunSergeyLukjanov:  has our scenario tests been ready?14:05
tmckaySergeyLukjanov, ack, thanks14:05
elmikoSergeyLukjanov: ok, for the sahara design sessions?14:05
SergeyLukjanovesikachev is responsible for it, but I think that they a ready for the almost half year :)14:05
SergeyLukjanovelmiko I mean main summit proposals14:06
*** weiting has joined #openstack-meeting-314:06
*** hdaniel_ has joined #openstack-meeting-314:06
elmikoah, gotcha14:07
NikitaKonovalovI've been looking at the dashboard for possible minor improvements. Some changes on review14:07
*** yamamoto has quit IRC14:08
egaffordSergeyLukjanov: I can write up an abstract for the general "state of Sahara" proposal. I'll post links to a draft for review later today.14:08
SergeyLukjanovegafford okay, great14:09
*** salv-orlando has quit IRC14:09
SergeyLukjanovI'll try to find prev. year proposals, if I'll be faster I'll share it with you :)14:09
SergeyLukjanov#topic Separated launchpad for sahara-dashboard14:10
*** openstack changes topic to "Separated launchpad for sahara-dashboard (Meeting topic: sahara)"14:10
SergeyLukjanovanything changed? any new objections or concerns?14:10
SergeyLukjanov(current decision is to track them in sahara project)14:10
NikitaKonovalovno changes that I've noticed14:11
*** zhurong has quit IRC14:11
*** yamamoto has joined #openstack-meeting-314:11
elmikowe did have a question in channel about where to log dashboard bugs, i just directed them towards the sahara launchpad and asked that they put "[UI]" in the subject14:11
toskyelmiko: and a tag too14:12
*** jpomeroy has joined #openstack-meeting-314:12
toskyelmiko: dashboard tag14:12
elmikotosky: ooh, good idea, i did not mention that14:12
*** yamamoto has quit IRC14:12
toskyit's not my idea, it has been like that forever :)14:13
*** julim has quit IRC14:13
elmikowell, my bad for forgetting...14:14
*** amotoki_ has quit IRC14:16
SergeyLukjanovI like both prefix and tag14:16
elmikoagreed14:16
SergeyLukjanovso seems like we're still ok with keeping dashboard issues in sahara project14:16
SergeyLukjanovbut with [UI] prefix and some tag14:16
SergeyLukjanovnot some, but "dashboard"14:17
SergeyLukjanovif yes, I'll add dashboard to tags14:17
toskyI thought it was already there, isn't it in use?14:17
SergeyLukjanovthere is a list of "project tags", that will be suggested by autocompletion14:18
toskyoh, I see14:19
*** e0ne has joined #openstack-meeting-314:19
SergeyLukjanov#topic API v2 progress14:20
*** openstack changes topic to "API v2 progress (Meeting topic: sahara)"14:20
elmikohey14:20
elmikoso, i've got a couple things to note14:20
elmiko#link https://review.openstack.org/#/c/212172/14:20
elmikostill working to get the main spec review merged14:20
elmiko #link https://review.openstack.org/#/c/273316/14:21
elmikothat is an initial poc for the v2 endpoints, as described in the spec14:21
*** alexpilotti has quit IRC14:21
elmikoand i'm curious if we can close this blueprint14:21
elmikohttps://blueprints.launchpad.net/sahara/+spec/v2-api-pecan-framework14:21
*** lblanchard has joined #openstack-meeting-314:21
egaffordThat does look pretty closeable at this point...14:22
tmckayI am ++ for merging the v2 API spec, I think it's solid14:22
elmikothat's what i thought, but i wanted to get some feedback before i went all crazy in the blueprints ;)14:22
*** neelashah has joined #openstack-meeting-314:23
elmikoanyways, that's it for my api v2 update. any questions, comments, concerns?14:23
tmckaywe should merge the spec and move on to sub-specs for features :)14:24
* tmckay my comment14:24
SergeyLukjanovI'll close pecan bp14:25
elmikoSergeyLukjanov: thanks14:25
*** banix has joined #openstack-meeting-314:25
tmckaythen we can each sign up for an endpoint, and have half a dozen or more done before Mitaka ends14:25
SergeyLukjanovI'm very sorry for no reviews for the last period, I've very busy on internal stuff, but it should be much better starting next week14:26
elmiko\o/14:26
*** salv-orlando has joined #openstack-meeting-314:26
SergeyLukjanovgreat!14:26
elmiko(and i hope the internal stuff has gone well)14:26
tmckaySergeyLukjanov, that's what I've been saying ;-)14:26
* egafford empathizes with SergeyLukjanov, and is glad that his internal stuff is starting to wrap up.14:27
SergeyLukjanovthx, going well, was too time consuming, but should be more localized now ;)14:28
tmckayegaffrod, elmiko, vgridnev, sreshetnyak, btw, thank you very, very much for keeping reviews going while SL and I were distracted :)14:28
SergeyLukjanov#topic Open discussion14:28
tmckayyou all have done great work, imho14:28
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:28
SergeyLukjanovyeah, that's correct14:28
SergeyLukjanovand I'm really happy that we have no bottleneck on reviews14:28
egaffordI had a question about merging minor changes (that are too small to need a blueprint and/or bug, or otherwise inappropriate for blueprints and bugs).14:29
*** vhoward has joined #openstack-meeting-314:29
*** salv-orlando has quit IRC14:29
huichuntmckay:  can we submit scenario patch into Sahara-scenario now?14:29
*** salv-orlando has joined #openstack-meeting-314:29
SergeyLukjanovyup, it's ready to accept patches I think14:30
vgridnevhuichun, you are always can14:30
SergeyLukjanovesikachev could you confirm?14:30
egaffordI'd like to propose that we have a 'MinorChange' tag, which we require in the commit message whenever we post a change that we think shouldn't need a bug, and have it be understood that review of whether we agree is part of the review in that case.14:30
*** alexpilotti has joined #openstack-meeting-314:30
esikachevSergeyLukjanov: yes14:30
huichunvgridnev: thx VG14:31
SergeyLukjanovegafford I think that lack of bug or blueprint is equal to tagging by MinorChange :)14:31
egaffordI think it's probably good that we sometimes allow minor changes through with launchpad artifact, but I'd like there to be *some* process around doing it.14:31
*** rossella_s has quit IRC14:31
elmikoegafford: just to help signal to others not to ask for a bug?14:31
esikachevin sahara-scenario now implemented ci for sahara from master14:31
SergeyLukjanovI would say in the beast case there should be no such patches14:31
egaffordSergeyLukjanov, elmiko: I think the difference is that there's intention when someone puts a tag on.14:31
SergeyLukjanovbest*14:31
*** rossella_s has joined #openstack-meeting-314:31
SergeyLukjanovbut someone anyway could disagree and say - hey, it should be a bug but not MinorChange tag14:32
egaffordSaying "I am thinking about it, and think we don't need a launchpad artifact" is different than "I may not have even thought about this at all".14:32
egaffordRight, that's part of the review.14:32
egaffordRight now it's implicit, I'm proposing we make it explicit, so at least we all know what we're thinking.14:32
elmikoegafford: i get what you are saying, just thinking about it14:33
SergeyLukjanovI'm not sure that it'll work as you want, but I'm ok if you want to try14:33
egaffordI don't think this is a terrifically important issue, but I think it'd help in those cases where there's active discussion of whether a bug/artifact is needed.14:33
toskydid we have that in the past? I've mostly seen the sequence "bug opened->review posted" even for things which didn't require a bug14:34
elmikoyea, i guess this is one of those issue where if someone puts a "-1 this needs a bug", you can answer by putting "MinorChange" in the commit message?14:34
toskythe other way round (review opened for a bug when the bug was required) are not so common14:34
SergeyLukjanovbtw I'm working on the OpenStack deployment architecture in containers on top of Mesos / Marathon (in upstream, it's kolla + kolla-mesos)14:35
elmikotosky: we also get small patches to fix minor things (like spelling, or line arrangement, etc)14:35
egaffordelmiko: Or hopefully, you can put MinorChange in the commit message, and then people can know not to "-1 this needs a bug" unless they really think it's a big enough issue to need a bug (rather than just a point of protocol -1.)14:35
elmikoSergeyLukjanov: ooh, neat!14:35
egaffordSweet!14:35
toskyelmiko: and code refactor, is that minorchange always which require a bug or blueprint? (the answer could be yes)14:35
elmikoegafford: right, if you think about it ahead of time14:35
elmikotosky: yea, good question14:35
tmckayegafford, ++. At the very least it indicates that it's not a mistake14:35
egaffordtmckay: Right, differentiating between mistake and intent is the whole case here.14:36
elmikoi think the tough part is going to be if we start getting reviews with "MinorChange" in lieu of creating bugs...14:36
elmiko(not sure if that would happen, just speculating)14:37
egaffordWe don't have to decide now, certainly. It's the first time I've raised the notion to the team. elmiko: Yeah, it's possible that people would take it as license to be terrible at Launchpad; absolutely.14:37
tmckaytosky, it depends how big the refactor is, I think14:37
elmikoi would hope not ;)14:37
elmikotosky, tmckay, yea.. it's a case-by-case type of thing with refactors14:38
*** janzian has joined #openstack-meeting-314:38
*** yamamoto has joined #openstack-meeting-314:38
AndreyPavlovfolks, i want to know if  there are any concerns about this patch https://review.openstack.org/#/c/272503/ ? or should i make the same for all other resources?14:38
*** baoli has joined #openstack-meeting-314:39
*** irenab has quit IRC14:39
elmikoAndreyPavlov: my only concern is that our saharaclient impl might start to drift from the rest api with respect to updates, but as long as we document how this works for the client i'm ok14:40
egaffordelmiko: Well, I think this is more of a difference in absence handling between rest and python than a drift between the rest API and the client. IMO this makes the client *more* like the REST API (in that now the client doesn't inject or omit values that the REST API wouldn't.)14:42
egaffordIt's certainly a drift between client versions, though.14:43
SergeyLukjanovAndreyPavlov, elmiko, should we probably keep __repr__ printing None? (crazy idea, need more coffee)14:43
elmikook, fair. honestly, i'm having some trouble remembering how our rest api is accepting updates (probably been doing too much cross-project review)14:43
elmikoupdating resources is a pita anyways...14:44
*** edleafe- has joined #openstack-meeting-314:44
egaffordSergeyLukjanov: That could make it impossible to determine whether a value in your dict is actually None on debug, or special None that isn't None.14:45
egaffordI like the __repr__ being different.14:45
elmikohaving the repr be NotUpdated is just helpful for the internal update14:46
tmckayI think this looks good, strictly internal except for the __repr__. I agree with egafford for debug help14:46
*** edleafe- has quit IRC14:47
elmikountil we can change the way updates are handled through the rest, i think it makes sense *internally*14:47
*** edleafe has quit IRC14:47
SergeyLukjanovegafford agree with None isn't None14:48
AndreyPavlovi guess current __repr__ is fine, just to show that it's not None by default and that you can pass None and it will lead to different consequences14:48
*** mlavalle has joined #openstack-meeting-314:48
elmiko+114:48
SergeyLukjanovmakes sense14:48
AndreyPavlovwill update the patch soon14:49
AndreyPavlovand also, there are two specs on review, i would appreciate if you could take a look on them) thanks in advance)14:49
AndreyPavlov#link https://review.openstack.org/#/c/273547/14:49
AndreyPavlov#link https://review.openstack.org/#/c/272569/14:49
*** jmckind has joined #openstack-meeting-314:50
*** fawadkhaliq has quit IRC14:51
*** edleafe has joined #openstack-meeting-314:51
elmikoSergeyLukjanov, NikitaKonovalov, did you guys want to talk about the summit presentation now or after the meeting?14:51
*** edleafe has quit IRC14:51
SergeyLukjanovAndreyPavlov will it be possible to conf the default coordinator to not have coordinator at all?14:52
NikitaKonovalovwe can do that after the meeting14:52
elmikok14:52
AndreyPavlovSergeyLukjanov: sure14:52
SergeyLukjanovyeah, let's do in #openstack-sahara14:52
*** nelsnelson has joined #openstack-meeting-314:54
*** edleafe has joined #openstack-meeting-314:55
*** cbouch has quit IRC14:55
*** yamamoto has quit IRC14:56
SergeyLukjanov3 mins left14:56
*** nelsnelson has quit IRC14:56
elmikoi have a quick question about changing our version reponse14:56
*** tidwellr has joined #openstack-meeting-314:56
elmikothe body you get from a GET /14:57
elmikocan we change this response without requiring a major version update?14:57
*** dlundquist has joined #openstack-meeting-314:57
elmikoor can we only change it once v2 is supported and v1.1 is deprecated?14:57
SergeyLukjanovelmiko hm14:57
SergeyLukjanovwhat are proposing to output?14:58
*** shwetaap has joined #openstack-meeting-314:58
*** hdaniel_ has quit IRC14:58
elmikothere is a guideline working it's way through the api-wg now, and there is evidence to show that sahara is pretty far off from what other services respond with for their versions14:58
elmikolook at this, #link https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Version_Responses14:59
*** nelsnelson has joined #openstack-meeting-314:59
elmikoi'm hoping we can do something more informative in the future14:59
*** baoli has quit IRC15:00
elmikoanyways, food for thought ;)15:00
elmikotimes up15:00
elmikoSergeyLukjanov... ;)15:00
SergeyLukjanov#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
elmikothanks SergeyLukjanov15:00
openstackMeeting ended Thu Jan 28 15:00:54 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2016/sahara.2016-01-28-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2016/sahara.2016-01-28-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2016/sahara.2016-01-28-14.00.log.html15:01
mlavalle#startmeeting neutron_l315:01
openstackMeeting started Thu Jan 28 15:01:13 2016 UTC and is due to finish in 60 minutes.  The chair is mlavalle. 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: neutron_l3)"15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
mlavalleHi15:01
*** johnbelamaric has joined #openstack-meeting-315:01
haleybhi15:01
pavel_bondarHi15:01
*** AndreyPavlov has left #openstack-meeting-315:01
johnbelamarichi15:01
mlavalle#chair carl_baldwin15:01
openstackCurrent chairs: carl_baldwin mlavalle15:01
*** mionkin has quit IRC15:01
*** baoli has joined #openstack-meeting-315:01
mlavalleToday's agenda https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam#January_28st.2C_201615:02
*** pino|work has joined #openstack-meeting-315:02
mlavalle#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:02
*** jlanoux_ has joined #openstack-meeting-315:03
*** pino|work has left #openstack-meeting-315:03
mlavalleDeadline for talks submissions for Austin Summit is February 1st. If you are planning a talk, don't miss the deadline15:03
*** tosky has left #openstack-meeting-315:03
vikram_hi15:03
carl_baldwinHi15:03
neiljerramhi15:03
*** baohua has quit IRC15:03
mlavallecarl_baldwin: you are chair, so you can drive if you want.....15:04
*** jlanoux has quit IRC15:04
mlavalleAny other announcements from the team?15:04
carl_baldwinYou're doing great.15:04
mlavalleok, moving on15:05
mlavalle#topic Bugs15:05
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:05
mlavalleNot much change since last week in regards to bugs. We don't have any critical15:05
mlavalleAnd we have the same 2 High importance bugs from last week15:06
mlavalleFirst up: https://bugs.launchpad.net/neutron/+bug/147810015:06
openstackLaunchpad bug 1478100 in neutron "DHCP agent scheduler can schedule dnsmasq to an agent without reachability to the network its supposed to serve" [High,In progress] - Assigned to Cedric Brandily (cbrandily)15:06
*** alexpilotti has quit IRC15:06
mlavalleIt has a revision ready for review since a week ago: https://review.openstack.org/#/c/205631/15:06
mlavalleSam Morrison gave it a +1, indicating that he has deployed the fix in his install and it fixed the problem15:07
mlavalleSo I encourage the team to take a look and give it some review love15:08
*** sigmavirus24_awa is now known as sigmavirus2415:08
*** esikachev has left #openstack-meeting-315:08
*** yamamoto has joined #openstack-meeting-315:08
*** dims has joined #openstack-meeting-315:08
mlavalleAny other comments from the team?15:08
*** zz_dimtruck is now known as dimtruck15:08
* carl_baldwin will take a look15:09
*** jlanoux_ has quit IRC15:09
mlavalleOk, next up is https://bugs.launchpad.net/neutron/+bug/152708915:09
openstackLaunchpad bug 1527089 in neutron "[ipam] Port ID is not present in port dict that is passed to AddressRequestFactory" [High,In progress] - Assigned to Carl Baldwin (carl-baldwin)15:09
johnbelamaricI just tagged that liberty-backport-potential - I'd like to see it in stable/liberty if possible15:09
mlavalleThanks johnbelamaric15:10
mlavalleProposed fix is https://review.openstack.org/#/c/259697/15:10
*** alexpilotti has joined #openstack-meeting-315:10
mlavalleIt only needs one more +2 and is ready to go15:10
mlavalleAny other comments?15:11
pavel_bondarno15:11
mlavallepavel_bondar: thanks for your hard work on this one!15:11
*** alexpilo_ has joined #openstack-meeting-315:11
johnbelamaricwe have the RFE on ipam migration too15:11
*** alexpilotti has quit IRC15:12
johnbelamaric#link https://bugs.launchpad.net/neutron/+bug/151615615:12
openstackLaunchpad bug 1516156 in neutron "[RFE] IPAM migration from non-pluggable to pluggable" [Wishlist,In progress] - Assigned to Pavel Bondar (pasha117)15:12
johnbelamaricdo we cover that in bugs?15:12
mlavallejohnbelamaric: yeah, go ahead15:12
johnbelamaricOk, so, just want bring up that pavel_bondar will be working that one next15:12
neiljerramGood news15:12
mlavallejohnbelamaric: what do you think its importance should be?15:13
johnbelamariche has some questions in the bug report if anyone has an opinion15:13
neiljerramFYI I have an Outreachy intern working on a pluggable IPAM module; spec about that should be posted within the next few days15:13
tidwellrglad to see this RFE15:13
johnbelamaricI think it's important to get into M so we can start moving people off of builtin IPAM15:14
carl_baldwinjohnbelamaric: I just noticed I need to review those comments.  Will do soon15:14
carl_baldwinjohnbelamaric: ++15:14
mlavallejohnbelamaric: ok, I'll assign high to it, so we track it every week here15:14
johnbelamaricmlavalle: thank you15:14
pavel_bondaralso it looks like it is still open question about best way to trigger data migration (operator or automatically), so comments on this topic are appreciated15:14
carl_baldwinmlavalle: it is the so should be wishlist15:15
carl_baldwinRfe15:15
mlavallecarl_baldwin: got it15:15
mlavalleany other bugs that should be brought to the team's attention?15:16
mlavalleok, let's move on15:16
mlavalle#topic Routed Network Segments15:17
*** openstack changes topic to "Routed Network Segments (Meeting topic: neutron_l3)"15:17
*** jmckind_ has joined #openstack-meeting-315:17
*** dandruta has joined #openstack-meeting-315:17
carl_baldwinI'm going to update this spec today15:17
* mlavalle points out that the new spec and the Nova spec url's were updated in the agenda15:18
carl_baldwinI've had some great discussions at the nova mid cycle and with armax.15:18
carl_baldwinIt'll be the same direction with some more detail.15:18
neiljerramcool15:19
mlavalle++15:19
*** jmckind has quit IRC15:20
vikram_nice15:20
carl_baldwinThat's it for now15:20
*** julim has joined #openstack-meeting-315:20
neiljerramwe're also on the agenda for the next ML2 meeting: https://wiki.openstack.org/wiki/Meetings/ML2#Meeting_February_3.2C_201615:20
mlavalleany questions for carl_baldwin?15:21
carl_baldwinneiljerram: thanks.  I'll need to get up to speed on this.15:21
mlavalleok, moving on15:21
mlavalle#topic BGP Dynamic Routing15:21
carl_baldwinneiljerram: what do they intend to discuss?15:21
*** openstack changes topic to "BGP Dynamic Routing (Meeting topic: neutron_l3)"15:21
mlavalle#undo15:22
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x9828c50>15:22
*** rhochmuth has joined #openstack-meeting-315:22
neiljerramcarl_baldwin, Nothing in particular, I believe; was triggered simply by me asking 'how do you feel about how routed spec is proposing to use multiprovider extension'15:23
neiljerramcarl_baldwin, I was trying to be as neutral asa pos15:23
neiljerram...as possible, but engage their attention.15:23
carl_baldwinneiljerram: ok15:23
mlavalleok.... moving on15:24
mlavalle#topic BGP Dynamic Routing15:24
*** openstack changes topic to "BGP Dynamic Routing (Meeting topic: neutron_l3)"15:24
tidwellrhi15:24
vikram_hi15:24
mlavalletidwellr, vikram_: hi15:24
carl_baldwinmlavalle: thanks, I think that's all15:25
vikram_We have fall back to service plugin framework15:26
vikram_Needs review help15:26
tidwellrwe're closing in on being functionally complete15:26
tidwellrwe know of a small handful of bugs, but I think we have those in hand15:27
mlavalleand the target for this is Mitaka-3, right?15:27
*** primeministerp has joined #openstack-meeting-315:27
vikram_yes15:27
tidwellrthere's a WIP patch for the DVR-aware route lookups that is the only patch that needs serious iteration15:27
carl_baldwintidwellr: are there patches ready to go now?15:28
tidwellrwe're ready serious for review attention, especially on the CRUD patches15:29
* tidwellr gets the review links15:29
* mlavalle will post them in the team's wiki15:29
tidwellrhttps://review.openstack.org/#/c/201621/ https://review.openstack.org/#/c/207607/ https://review.openstack.org/#/c/207607/ https://review.openstack.org/#/c/207607/15:30
*** rbak has joined #openstack-meeting-315:30
vikram_https://review.openstack.org/#/q/topic:bp/bgp-dynamic-routing+status:open15:30
mlavallevikram_, tidwellr: thanks15:31
tidwellrwe even have devstack integration and API tests running in the gate now15:31
tidwellrso we're really close15:31
tidwellrthat's all I have15:31
mlavalleany other questions from the team?15:32
carl_baldwintidwellr: thanks.  Are the links in order of readiness?15:32
*** kebray has joined #openstack-meeting-315:33
tidwellrcarl_baldwin: readiness corresponds with place in the chain of reviews15:33
*** spzala has joined #openstack-meeting-315:33
*** kebray has quit IRC15:33
carl_baldwintidwellr: thanks.  Too bad the new gerrit ui makes that harder to follow.15:34
*** kebray has joined #openstack-meeting-315:34
*** egafford has quit IRC15:34
carl_baldwinI'll muddle through15:34
tidwellrcarl_baldwin: I know :(15:34
mlavalleok, moving on15:35
mlavalle#topic DNS15:35
*** openstack changes topic to "DNS (Meeting topic: neutron_l3)"15:35
mlavalleLast week, we merged the code for external DNS integration: https://review.openstack.org/#/c/212213/15:36
mlavalleThanks to all the team members who helped with reviews and advice15:36
*** hurgleburgler has joined #openstack-meeting-315:36
carl_baldwinmlavalle: talked with john this morning.  I owe him some notes on your nova review.15:37
mlavalleLate last week I pushed to Gerrit the Nova side of it https://review.openstack.org/#/c/271578/15:37
johnbelamaricmlavalle: congratulations! That was a huge amount of work.15:37
mlavalleit turned out to be a lot easier than we thought in the spec15:37
mlavallethe Neutron API in Nova keeps a cache of Neutron extensions enabled15:38
mlavallethat is updated every 10 minutes by default15:38
mlavalleso we don't need to worry about retrying a port create or update in case Neutron server has not been upgraded with the DNS extension15:38
mlavallethe Nova code in Gerrit is functionally complte. I will just add tests over the next few days in PS315:39
mlavalleand it should be ready to go15:39
mlavalleI am also working a o chapter to the Networking Guide for operators15:39
mlavalleI am making very good progress15:40
mlavalleI'll push to Gerrit also over the next few days15:40
mlavallecarl_baldwin: thanks15:40
mlavalleany questions?15:40
carl_baldwinmlavalle: not from me15:41
mlavalleok, moving on15:41
mlavalle#topic Address Scopes15:41
*** openstack changes topic to "Address Scopes (Meeting topic: neutron_l3)"15:41
*** hurgleburgler has left #openstack-meeting-315:42
carl_baldwinThe L3 agent patch is the last major one left.  It needs a little more work.  Should be ready next week.15:42
carl_baldwinThen, need docs.15:43
carl_baldwinThat's all.  It is going well15:44
mlavalleany questions from the team?15:44
mlavalleok, moving on15:44
mlavalle#topic Open Discussion15:45
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:45
mlavalleearlier in the annoucements section I forgot to mention we will have a Neutron mid-cycle meeting at the end of February15:45
mlavallethis is the etherpad: https://etherpad.openstack.org/p/neutron-mitaka-midcycle15:45
*** weiting has quit IRC15:45
*** lazy_prince has quit IRC15:45
mlavalleso you are invited to enjoy the wonderful Minnesota weather in February :-)15:46
mlavalleany other topics?15:46
* carl_baldwin excited for that15:46
*** dixiaoli_ has quit IRC15:46
mlavalleok, going once15:47
mlavallegoing twice15:47
carl_baldwinmlavalle: thanks!15:48
mlavalleThanks for attending team, see you in channel and Gerrit15:48
neiljerramBye!15:48
mlavalle#endmeeting15:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:48
openstackMeeting ended Thu Jan 28 15:48:26 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-01-28-15.01.html15:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-01-28-15.01.txt15:48
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2016/neutron_l3.2016-01-28-15.01.log.html15:48
*** johnbelamaric has left #openstack-meeting-315:48
*** janzian has left #openstack-meeting-315:49
*** tidwellr has left #openstack-meeting-315:50
*** mtanino has joined #openstack-meeting-315:50
*** mlavalle has left #openstack-meeting-315:50
*** iyamahat has joined #openstack-meeting-315:51
*** vtech has quit IRC15:51
*** dlundquist has quit IRC15:54
*** dlundquist has joined #openstack-meeting-315:55
*** dtroyer has joined #openstack-meeting-315:56
*** jlanoux has joined #openstack-meeting-315:56
*** rosmaita has joined #openstack-meeting-315:57
*** numans has quit IRC15:58
*** galstrom_zzz is now known as galstrom15:59
*** baoli has quit IRC15:59
*** dlundquist has quit IRC15:59
etoews#startmeeting api wg16:00
openstackMeeting started Thu Jan 28 16:00:05 2016 UTC and is due to finish in 60 minutes.  The chair is etoews. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: api wg)"16:00
openstackThe meeting name has been set to 'api_wg'16:00
etoewshola16:00
rosmaitao/16:00
elmikoyo/16:01
*** cdent has joined #openstack-meeting-316:01
cdento/16:01
etoews#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:02
*** baoli has joined #openstack-meeting-316:02
*** baoli has quit IRC16:02
etoewsummmm...not so many updates from last week.16:02
*** baoli has joined #openstack-meeting-316:02
elmikowe've got a couple new guidelines that have been proposed =)16:02
elmikonice to see the activity16:02
etoewsyes!16:03
etoews#topic previous meeting action items16:03
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"16:03
etoews#link http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-01-14-16.00.html16:03
* etoews assumes nothing happened at last week's meeting...16:03
*** jlanoux has quit IRC16:03
cdent"cdent to re-review https://review.openstack.org/#/c/234994/ with an eye to reaching consensus" FAIL16:03
elmikoi got word through ryanb that miguel is cool with me taking over the actions review16:03
*** scottda has joined #openstack-meeting-316:03
elmikoand i froze that review, but it got pinged and sent back to review :/16:04
cdentsorry about making that harder16:04
elmikohaha16:04
etoewselmiko: good on you for taking that on16:04
elmikono worries, there are some good suggestions in the comments cdent16:04
elmikoetoews: i feel it's gonna be rough slough16:04
*** tmckay has quit IRC16:04
*** agentleweb has joined #openstack-meeting-316:05
cdentI think splitting it in two is a good way to go.16:05
cdentchanging some thing's state v doing some stuff16:05
elmikogood idea16:06
*** salv-orl_ has joined #openstack-meeting-316:06
etoewsya. we need to start finding alternative ways to make progress on this stuff.16:06
elmikoand there is the whole issue of whether tasks/actions/workflows should even be separate resources16:06
elmikois it even possible for us to start smaller on some of the more controversial guidelines?16:07
*** vgridnev has quit IRC16:07
etoewsi think it's worthwhile to try16:07
elmikoi like the approach that ken o'omichi took with the microversion stuff16:07
elmiko(i think it was him)16:07
*** vgridnev has joined #openstack-meeting-316:07
etoewsi wish i had done something like that with the errors guideline16:07
*** jlanoux has joined #openstack-meeting-316:08
* cdent sings there's always tomorrow...16:08
elmikook, given that, i'll try to break the "actions" guideline up into more manageable pieces16:08
*** kzaitsev_mb has quit IRC16:08
ameadeo/16:08
etoewsit almost became a true ocean boiling guideline but i had to cut it off with a todo before it got way out of hand16:08
rosmaitaameade: \o16:09
*** yamahata has joined #openstack-meeting-316:09
*** salv-orlando has quit IRC16:09
etoewsanyhoo16:09
etoews#topic api wg cfp for openstack summit in austin16:09
*** openstack changes topic to "api wg cfp for openstack summit in austin (Meeting topic: api wg)"16:09
etoews#link https://etherpad.openstack.org/p/austin-api-wg-session-plans16:09
etoewsi'm all for slapping that agenda into the submission for and pushing go16:10
elmikoi have been meaning to add little to that agenda, but i keep failing =(16:10
cdentwill that satisfy whatever filters they are using (if any) or do we get a slot just by virtue of being a real working group?16:11
etoewselmiko: cdent: either of you care to make the submission (with the others as co-speakers)?16:11
elmikoi think we should have an item to discuss fairy-slipper, and i do want to give a presentation on the example project idea i've been working on16:11
*** kzaitsev_mb has joined #openstack-meeting-316:11
etoewssgtm16:11
cdenti think elmiko just volunteered16:11
elmikofair, i'm cool with that16:11
cdent:)16:11
elmiko#action elmiko to post api-wg submission for austin summit16:12
*** yamamoto has quit IRC16:12
*** yamamoto has joined #openstack-meeting-316:12
etoewscdent: for the first time in a long time on not a chair on any of the tracks so i'm not sure16:12
etoewsbut i expect so16:12
*** vgridnev has quit IRC16:12
*** amotoki has joined #openstack-meeting-316:12
elmikoi can try to spice it up a little for the descriptive entry if you think it's necessary?16:13
*** jlanoux has quit IRC16:13
etoewsi could reach out and find out who the wg track chairs are and see what's really necessary16:13
cdentmaybe a little paragraph saying "we're going to do some stuff" and then top level agenda items as a list16:13
elmikocdent: yea, i like that16:13
etoewssgtm16:14
etoews#action etoews to try to find out just how much hoop jumping we need to do for the wg submission16:14
cdenthas to be done my monday, yeah?16:14
etoewsyes. that work for you elmiko ?16:15
elmikoetoews: yup, i'll have something ready to go16:15
etoewsi'm around all day today and tomorrow so don't hesitate to ping.16:15
elmikojust ping me with an email or something if you get word about the hoop jumping16:15
elmikocool16:15
etoewsyep16:16
*** cartik has joined #openstack-meeting-316:16
*** yamamoto has quit IRC16:16
etoews#topic magnum api refresh16:16
*** openstack changes topic to "magnum api refresh (Meeting topic: api wg)"16:16
etoews#link https://blueprints.launchpad.net/magnum/+spec/standardised-error-messages16:16
cdentthat's nice16:16
etoewsso this is a holdover topic from last week but that ^ makes me smile16:16
elmikoooh, neat16:17
etoewswhat i need to do is reach out to the magnum CPLs and highlight that for them16:17
*** yamamoto has joined #openstack-meeting-316:17
elmiko+116:17
etoews#action etoews to reach out to the magnum CPLs and highlight https://blueprints.launchpad.net/magnum/+spec/standardised-error-messages for them16:17
*** kzaitsev_mb has quit IRC16:18
etoewsi also know magnum's mid-cycle is coming up and some api changes might fall out of that16:18
etoewsis there a prescribed mechanism for making part of an api a "plugin"?16:19
*** yamamoto has quit IRC16:19
etoewsi know the whole extension thing was a miserable failure in nova.16:19
rosmaita+ 100016:19
cdentetoews: do you mean optional?16:19
*** vtech has joined #openstack-meeting-316:19
etoewsyes16:19
elmikoi'm not aware of anything from the rest api side, just the stevedore stuff from the code api16:19
agentlewebthe model I think of as best for users is LBaaS in neutron, anyone else?16:19
agentlewebwhere it's another endpoint/use case16:20
*** davidsha has quit IRC16:20
cdentendpoints seem to be the hammer for most things like this16:20
*** yamamoto has joined #openstack-meeting-316:20
etoewsagentleweb: do you have a link to something that describes exactly how the optional aspect of that works?16:20
etoewscdent: can you expand on that a bit?16:20
cdentso as to avoid a situation where something the service catalog is consistent between clouds16:20
cdents/the/in the/16:21
agentlewebetoews: hm, thinking16:21
cdentso if something is optional, then it just isn't in the service catalog when it is not available16:21
cdentthat may, however, be a too broad hammer16:21
etoewscdent: do you mean s/consistent/inconsistent/ above?16:21
cdentsigh, yeah16:22
*** egallen has quit IRC16:22
cdentor s/avoid/ensure/, your choice16:22
etoewsthat is a broad hammer but at least it's another option. a reasonably well understood option at that.16:22
*** jmckind_ has quit IRC16:22
cdentceilometer has a capabilities api16:23
etoewsalthough "avoid a situation where something the service catalog is consistent" is pretty accurate :P16:23
cdentwhich basically says something to the effect of "are events turned on" and the like16:23
*** piet has quit IRC16:23
cdentbut I'm not sure that's a pattern used elsehwere16:23
cdentand not something I would want to encourage in services16:24
agentlewebcdent: yeah that's used in swift as well but let me think of the name16:24
*** piet has joined #openstack-meeting-316:24
cdentI think they should be whatever they are and just do what they do16:24
etoewscdent: do you have a link to something that describes exactly how the optional aspect of the capability api works?16:24
* cdent looks16:24
agentlewebah, but it's GET /info16:24
cdentetoews: this good enough: http://docs.openstack.org/developer/ceilometer/webapi/v2.html#capabilities16:25
elmikocdent: is that a discovery mechanism for the extensions?16:25
cdentone of the drivers of that was tempest (which then ended up not using it)16:25
agentlewebetoews: also swift http://blogs.rdoproject.org/6509/swift-discoverable-capabilities16:25
cdentelmiko: it's discovery of what the storage system behind the api is able to do16:25
elmikoah, ok16:25
*** egallen has joined #openstack-meeting-316:26
agentlewebetoews: and http://docs.openstack.org/developer/swift/api/discoverability.html16:26
elmikoseems like doing something akin to json-home would work well for discovering the extension endpoints (assuming we are talking api extensions)16:26
agentlewebyeah it's about what's implemented16:26
etoews"To discover which features are enabled in your Object Storage system, use the /info request. However, your service provider might have disabled the /info request"16:27
etoewsLOL16:27
elmikoouch16:27
cdentthat topic came up here (nova mid-cycle) today. providers sometimes turn off discovery16:27
*** egafford has joined #openstack-meeting-316:27
cdent(of all sorts)16:27
* etoews sighs16:28
agentlewebyeah that too... sigh16:28
agentlewebthose darn providers :)16:28
cdentI think moving in the direction of json-home would be a GoodThing™16:29
etoewsokay. this is all good info (pun intended). i'll feed this back to the magnum team.16:29
elmikolol16:29
*** primeministerp has quit IRC16:29
etoews#action give feedback to magnum team on ways to do "optional" parts of an api16:29
elmikothe whole provider thing does bring up an interesting point about enabling/disabling discovery mechanisms though16:30
cdentBasically I think we should strive to do things in the direction of the rest of the world...16:30
etoews #action etoews give feedback to magnum team on ways to do "optional" parts of an api16:30
*** baoli has quit IRC16:30
etoewsdid jsonhome ever really get any traction?16:30
etoewsnot that i think it's a bad idea but it would be nice to be able to point to successful use cases outside of openstack-land16:31
agentlewebno I haven't seen it etoews16:31
rosmaitaetoews: that's what i'm wondering16:31
elmikoetoews: +116:31
rosmaitai haven't seen it anywhere16:31
rosmaitaexcept maybe keystone16:31
cdentI can check with some out there in the rest of the world contacts16:31
etoewslet me ping some of the api-heads i know. see if they're aware of it.16:31
elmikodid json-home make it out of drafting yet?16:31
*** belmoreira has quit IRC16:31
etoewsnope16:31
elmikothought so16:31
rosmaitano, and last draft expired 201316:31
elmikoooph16:32
cdentfeh16:32
agentlewebyah16:32
etoewsnab16:32
* cdent is not wed to json-home, just want something that is not openstack-specific-special-flower-magic16:32
rosmaitacdent: i hear you16:32
etoewsyep. that's the direction i usually lean too.16:32
agentlewebcdent: ++16:33
elmikonah, we definitely need our own impl for this... s/16:33
cdent /kick elmiko16:33
elmikohaha16:33
etoews  #action etoews reach out to api-heads to see if jsonhome ever got traction anywhere16:33
*** jlanoux has joined #openstack-meeting-316:33
elmikocome-on, i know you love a contrarian ;)16:33
cdentIt's true <316:33
*** baoli has joined #openstack-meeting-316:34
*** baoli has quit IRC16:34
*** bpokorny has joined #openstack-meeting-316:34
*** baoli has joined #openstack-meeting-316:34
etoewsany other new topics people want to discuss or move onto guidelines?16:34
cdentonward16:34
*** tej has joined #openstack-meeting-316:34
etoews#topic guidelines16:34
*** openstack changes topic to "guidelines (Meeting topic: api wg)"16:34
etoewsthe #link http://ghostcloud.net/openstack_gerrit_dashboards/dashboard_api-wg.html is borked :(16:35
*** fawadkhaliq has joined #openstack-meeting-316:35
*** itxaka has quit IRC16:35
*** nkrinner has quit IRC16:35
etoewsbut #link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z is pretty manageable.16:35
* cdent nods16:36
elmikohmm, can we put server-side tracebacks up for freeze?16:36
etoewsyes16:36
*** mickeys has joined #openstack-meeting-316:36
elmikodoesn't look like anything else is ready16:36
*** yamamoto has quit IRC16:36
cdentyes16:36
etoewsameade: rosmaita: anything you want to discuss here?16:37
*** yamamoto has joined #openstack-meeting-316:37
elmiko#action elmiko freeze the server-side traceback guideline16:37
*** alexpilo_ has quit IRC16:37
*** bpokorny has quit IRC16:37
cdentthis guideline probably requires a fair bit of thought about the precedents it will set: https://review.openstack.org/#/c/273158/16:37
rosmaitaetoews: yeah, i don't want to hold up actual work other people are trying to do while i slowly work on the versions thing16:37
*** bpokorny has joined #openstack-meeting-316:38
etoewsah. i get where you're coming from. i'm pretty much resigned to the fact that most guidelines take a long time to happen.16:38
*** vahidh has joined #openstack-meeting-316:39
*** irenab has joined #openstack-meeting-316:39
etoewsif people need something like versions discovery right away, then they'll just have to do the best they can until the guideline settles.16:39
rosmaitaok16:40
*** ivar-lazzaro has joined #openstack-meeting-316:40
rosmaitaetoews: anyway, your action item to get some eyes on it worked16:40
etoewsit's not like we're the first group to try to bring guidelines/standards to something while it is in development.16:40
etoewsnice16:40
elmikoi've been watching that one too, i'd like to improve our version page in sahara16:40
rosmaitaso i will revise in line with jay's comments16:40
rosmaitanot sure that helps ameade though16:40
etoewsyep. some good stuff in there.16:41
elmikoi do have a question about updating the version response and server versions16:41
etoewswe need to get a feel for what projects are already using jsonhome16:41
etoewsand document that in #link https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Version_Responses16:41
etoewsany volunteers for that ^?16:42
elmikoi can try and add a few more projects to that page16:42
elmikoi'll start with zaqar ;)16:42
etoewsthx elmiko16:42
elmikosomething to consider for the guideline, and this is kinda meta, but how does changing the version page affect the semver?16:42
*** vikram_ has quit IRC16:42
elmikolike, if you change your root home page, would that necessarily mean bumping the major version since you will break the api contract?16:43
etoewsrosmaita: does ameade need to implement something very soon?16:43
rosmaitahe sent soemthing the the ML today16:43
* rosmaita looking for link16:44
ameadepaying attn now one sec16:44
scottdahi16:44
etoewselmiko: thinking...16:44
scottdaameade: is helping Cinder to determine the string we used for api-microversion header16:44
elmikoyea, it's a toughie16:44
*** yamamoto has quit IRC16:44
rosmaita#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/085229.html16:45
scottdaWe *think* Api-microversions will land soon in Cinder16:45
ameaderosmaita: you beat me!16:45
scottdaand currently use "X-OpenStack-Cinder-API-microversions"16:45
*** mickeys has quit IRC16:45
scottdaconsistent with Nova, Manila, etc.16:46
etoewselmiko: you could do something rude and just 301 redirect16:46
cdentameade: in discussions today with nova people, there's a vague plan for nova to start supporting both X-OpenStack-Nova-API-Version and OpenStack-Compute-Version16:46
cdent(or something close to that)16:46
elmikoso, given the current conversations on ML, that should probably be "X-OpenStack-Block-Storage-API-microversions"16:46
cdentno X16:46
elmikoer yea, i knew that felt wrong16:46
cdentsorry that was supposed to be a question "no X?"16:46
scottdaOK, and no Cinder?16:46
scottdause Block?16:46
elmikoyea, drop the cinder16:46
cdentis "API" redundant?16:47
*** yamamoto has joined #openstack-meeting-316:47
elmikoour preference is service type when possible16:47
elmikocdent: hmm, good question16:47
*** kzaitsev_mb has joined #openstack-meeting-316:47
etoewsscottda: ameade: see http://specs.openstack.org/openstack/api-wg/guidelines/headers.html16:47
elmikoi think api is redundant, but it is also explicit, so i'm torn16:48
cdentbut as far as we were concerned in the earlier conversation the service and the API are congruent16:48
ameadei think we should nail down what cinder shoud do and add some sort of header aliases in nova and manila16:48
elmikoameade: +116:49
cdentameade: yeah the aliases are coming in nova16:49
cdent(no timetable)16:49
ameadekk cool16:49
elmikoimo, cinder should use "Block-Storage" and nova/manilla should create service type aliases16:49
*** jlanoux has quit IRC16:49
scottdaOK, Cinder is imminent, so we want to get it right16:49
cdentthe meandering right now is trying to determine the exact correct form of the proper header16:49
*** alexpilotti has joined #openstack-meeting-316:49
*** s3wong has joined #openstack-meeting-316:50
scottdaOpenStack-Block-Storage-API-microversion ?16:50
elmikocdent: i think we could drop the API, since when are you going to request anything else *but* the API microversion16:50
etoewsya. drop the API.16:50
scottdaThat's ok with me.16:50
cdentme too16:50
scottdaOpenStack-Block-Storage-microversion16:50
ameadei'm cool with that16:51
cdentameade: you happy to respond to your own mail message (to report on what we've just decided)?16:51
rosmaitais the type 'block-storage' or 'volume' ?16:51
cdentrosmaita: I was going to ask that too16:51
cdentI don't know the server catalog identifiers well16:51
*** yamamoto has quit IRC16:51
rosmaitai thought it was 'volume'16:51
elmikoaccording to governance, it's "Block Storage service"16:51
elmikohttp://governance.openstack.org/reference/projects/cinder.html16:52
scottdaI *think* service catelog uses block storage16:52
rosmaitayeah, but what is 'type' in the service catalog?16:52
elmikomaybe that's different than the service catalog though16:52
*** yamamoto has joined #openstack-meeting-316:52
etoewsugh. https://review.openstack.org/#/c/243429/3/guidelines/microversion_specification.rst currently recommends putting API in there.16:52
cdentdevstack appears to use "volume"16:52
rosmaitai think we need to be consistent with the service catalog16:52
elmikoetoews: hmm16:52
ameadedocs uses 'volume'16:53
ameaderosmaita: +116:53
etoewsdon't go by devstack16:53
elmikoagreed about consistency with service catalog, but isn't the service catalog supposed to agree with governance?16:53
etoewsagentleweb: do you know ^ w.r.t. your work on the service catalog?16:53
cdentetoews: the discussion amongst the service catalog next-gen people is that most people use devstack as the precent setter. Not that that is _good_.16:54
elmikoetoews: do we need to recommend dropping "API" on that review?16:54
etoewselmiko:16:54
etoewselmiko: yes16:54
elmikok16:54
*** liangy has quit IRC16:55
* cdent would like to learn to type16:55
*** spzala has quit IRC16:55
*** jlanoux has joined #openstack-meeting-316:55
etoewsjust commented on removing API from the header16:56
ameadestarting my vm to see whats in the catalog lol16:57
elmikoack, thanks16:57
agentlewebetoews: oh sorry, I'm on a web irc client and didn't see16:57
elmikomy devstack has "volumev2"16:57
agentlewebI went to the keystone midcycle yesterday and talked about the service catalog16:57
etoewsameade: why see one service catalog when you can see ALL THE SERVICE CATALOGS! https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Service_Catalog16:57
scottdaSo should I be using the service catelog type, i.e. "volume" or name "Block Storage"16:57
elmikoi don't think that makes sense for the header though16:57
cdentelmiko: do you have both volume and volumev2?16:58
elmikooh, yes. i do16:58
agentleweb"Known types such as service_type can be documented in projects.yaml in the openstack/governance git repository." from http://specs.openstack.org/openstack/openstack-specs/specs/service-catalog.html16:58
agentlewebso volume2 needs to be stopped16:58
*** hdaniel_ has joined #openstack-meeting-316:58
elmikoscottda: imo, we should attempt to standardize on the official service type, but i defer to agentleweb on service catalog stuff16:58
*** hdaniel_ is now known as hdaniel16:59
etoewswe'll have to move this to #openstack-sdks in a minute.16:59
ameadeagentleweb: that's weird +116:59
agentlewebcdent: and my ask of the keystone team is a json schema and tempest test for service catalog entries so devstack's service catalog is a shining example of correctness16:59
*** yamamoto has quit IRC16:59
etoewsschemas and tests???!?!!! madness.17:00
scottdaOK, so I don't quite know what the answer is for my issue17:00
agentlewebetoews: I want the Mr. Burns icon17:00
etoewsthanks all! let's move to #openstack-sdks17:00
agentlewebsure17:00
etoews#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu Jan 28 17:00:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-01-28-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-01-28-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2016/api_wg.2016-01-28-16.00.log.html17:00
cdentI think we should get together with various service catalog people because the suggested rule of "just use the service type" gets weird when you have volume, volumev2, compute, computev2117:00
elmikothanks etoews17:00
*** jmckind has joined #openstack-meeting-317:01
*** vahidh has quit IRC17:02
*** jed56 has quit IRC17:03
*** rosmaita has left #openstack-meeting-317:03
*** yamamoto has joined #openstack-meeting-317:04
*** Swami has joined #openstack-meeting-317:05
*** vahidh has joined #openstack-meeting-317:05
*** jaypipes has quit IRC17:06
*** jlanoux has quit IRC17:06
*** jmckind has quit IRC17:06
*** cdent has quit IRC17:07
*** jlanoux has joined #openstack-meeting-317:07
*** tbachman has joined #openstack-meeting-317:09
*** nelsnels_ has joined #openstack-meeting-317:12
*** nelsnelson has quit IRC17:15
*** e0ne has quit IRC17:15
*** jlanoux has quit IRC17:16
*** sigmavirus24 is now known as sigmavirus24_awa17:16
*** woodster_ has joined #openstack-meeting-317:19
*** liangy has joined #openstack-meeting-317:20
*** jlanoux_ has joined #openstack-meeting-317:22
*** Sukhdev has joined #openstack-meeting-317:23
*** agentleweb has left #openstack-meeting-317:24
*** jlanoux_ has quit IRC17:26
*** yamamoto has quit IRC17:31
*** moshele has quit IRC17:32
*** ivar-lazzaro has quit IRC17:32
*** tbachman_ has joined #openstack-meeting-317:37
*** safchain has quit IRC17:39
*** madhu_ak has joined #openstack-meeting-317:39
*** egallen has quit IRC17:40
*** tbachman has quit IRC17:40
*** tbachman_ is now known as tbachman17:40
*** matrohon has quit IRC17:40
*** numans has joined #openstack-meeting-317:40
*** evgenyf has quit IRC17:42
*** sdake_ has joined #openstack-meeting-317:42
*** egallen has joined #openstack-meeting-317:43
*** sdake has quit IRC17:45
*** iyamahat has quit IRC17:46
*** armax has joined #openstack-meeting-317:46
*** hdaniel has quit IRC17:46
*** salv-orl_ has quit IRC17:48
*** dlundquist has joined #openstack-meeting-317:48
*** SumitNaiksatam has joined #openstack-meeting-317:48
*** dlundquist has left #openstack-meeting-317:49
*** alexpilotti has quit IRC17:50
*** iyamahat has joined #openstack-meeting-317:52
*** iyamahat has quit IRC17:54
*** hemanthravi has joined #openstack-meeting-317:58
*** bryan_att has joined #openstack-meeting-318:00
*** songole has joined #openstack-meeting-318:00
*** rkukura has joined #openstack-meeting-318:00
SumitNaiksatamrkukura: songole hemanthravi igordcard_: hi18:01
rkukurahi18:01
songoleHi18:01
hemanthravihi18:01
igordcard_hi18:02
SumitNaiksatam#startmeeting networking_policy18:02
openstackMeeting started Thu Jan 28 18:02:17 2016 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: networking_policy)"18:02
openstackThe meeting name has been set to 'networking_policy'18:02
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#Jan_28th.2C_201618:02
SumitNaiksatam#topic Bugs18:02
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:02
*** mbound has quit IRC18:02
SumitNaiksatamwe have one critical bug in UI for liberty18:03
*** cartik has quit IRC18:03
SumitNaiksatamthe javascript files are not getting loaded correctly18:03
*** alexpilotti has joined #openstack-meeting-318:03
SumitNaiksatamank is looking at it and has a patch: #link https://review.openstack.org/27349618:03
*** julim has quit IRC18:04
*** iyamahat has joined #openstack-meeting-318:04
SumitNaiksatamthe patch is failing because of a version number in the setup.cfg18:04
SumitNaiksatami post another patch to remove the version number, will need to help to get it merged quickly18:04
* tbachman steps in18:04
SumitNaiksatamany other high priority bus to discuss?18:05
SumitNaiksatamtbachman: hi!18:05
tbachmanSumitNaiksatam: hi!18:05
SumitNaiksatamno new updates on integration test or docs18:05
SumitNaiksatam#topic Packaging18:06
*** openstack changes topic to "Packaging (Meeting topic: networking_policy)"18:06
SumitNaiksatamrkukura: anything to update here?18:06
SumitNaiksatamliberty tars are posted18:06
*** julim has joined #openstack-meeting-318:06
rkukuranothing new from me on this yet, but should be able to do liberty soon18:06
SumitNaiksatamthe other stable releaes are not, waiting a little bit more to see if there are any more changes18:06
SumitNaiksatamrkukura: okay, thanks18:06
rkukurado we plan to move our masters to use neutron, etc. masters?18:07
SumitNaiksatamrkukura: yes18:07
rkukuraI think that will be important for getting RDO delorean setup for our stuff18:07
SumitNaiksatamsure, i will post a WIP patch soon18:08
rkukuragreat18:08
rkukuraI will try to get a plan for this at least by next week’s meeting18:08
SumitNaiksatamrkukura: nice, thanks18:08
SumitNaiksatamso while we are on that topic of syncing up the master branch18:09
SumitNaiksatam#topic DB migrations18:09
*** openstack changes topic to "DB migrations (Meeting topic: networking_policy)"18:09
SumitNaiksatamin the liberty cycle neutron moved to a new scheme of DB migrations18:09
SumitNaiksatamwhich allows to perform additive migrations online (without having to restart the server)18:10
SumitNaiksatamwe will need to decide if we want to move to such a scheme as well18:11
SumitNaiksatamfor reference #link https://github.com/openstack/neutron/commit/c7acfbabdc13ed2a73bdbc6275af8063b8c1eb2f18:12
SumitNaiksatamwe can give it some thought and discuss further in subsequent meetings18:13
SumitNaiksatam#topic Design Specs18:14
*** openstack changes topic to "Design Specs (Meeting topic: networking_policy)"18:14
SumitNaiksatam#link https://review.openstack.org/#/c/239743/18:14
SumitNaiksatamhemanthravi: songole: any update on the above?18:14
*** huichun has quit IRC18:14
songoleSumitNaiksatam: hemanth is updating it.18:14
hemanthraviI'm behind on the  network func platform spec, will post the update by end of the  week18:14
SumitNaiksatamsongole: hemanthravi:  okay thanks18:15
SumitNaiksatamhemanthravi: we planned to post a separate spec for “nfp”?18:15
hemanthravino, will the same spec18:16
SumitNaiksatamor nsf -> nfp?18:16
SumitNaiksatamhemanthravi: okay18:16
hemanthraviI think I had the name mixed up with the many we discussed18:16
hemanthravinsf18:16
SumitNaiksatamhemanthravi: it will spec out, both the northbound, and the southbound APIs?18:16
hemanthravithe northbound will take some time, i'll start with the southbound18:17
SumitNaiksatamhemanthravi: okay18:17
SumitNaiksatamhemanthravi: having the southbound API will allow service developers to plug into this framework, right?18:17
hemanthraviyes,18:18
hemanthravithe idea is to have to an infra component and a service-tenant component and the soutbound api18:19
hemanthraviwill allow the service-tenant component to be pluggable18:19
SumitNaiksatamhemanthravi: okay, thanks for the update18:20
SumitNaiksatam#topic Status field for resources18:20
*** openstack changes topic to "Status field for resources (Meeting topic: networking_policy)"18:20
SumitNaiksatamfield -> attribute18:20
SumitNaiksatamwe have discussed this in the past in the context of the “service_chain_instance"18:21
SumitNaiksatamhowever this requirement applies to other resources as well18:22
rkukuraSumitNaiksatam: Is there a concrete proposal for this?18:22
SumitNaiksatamrkukura: no18:22
SumitNaiksatamjust wanted to bring it up here before putting the proposal18:23
rkukuraDo we want just an enum, or also something more verbose like a text description?18:23
SumitNaiksatamrkukura: a description can certain be very helpful for the user18:23
hemanthraviwe do need this, else the calls to instantiate service chain instances end up as blocking calls18:23
rkukuraSince we can have multiple drivers, we also need some way to coelesce status from them into a single enum. This is something we want to do in ML2, but don’t have a proposal yet.18:23
SumitNaiksatamrkukura: i would imagine that it would be the responsibility of the plugin to coalesce the states, but would be specific to the drivers that are supported by that particular plugin18:25
rkukuraright18:25
SumitNaiksatamrkukura: admittedly this is difficult to do in a generic way (like in the case of ML2)18:25
rkukuraSo the driver API would need a way for each driver to provide its own status, and would have to figure out how to compose these into the overall status18:25
*** sdake_ has quit IRC18:26
*** fawadkhaliq has quit IRC18:26
SumitNaiksatami also recall a similar issue with fwaas, where the state needed to be constructed from distributed components18:26
SumitNaiksatamrkukura: right18:26
SumitNaiksatamif anyone wants to post a proposal for this, please feel free to do so, else i will post one18:27
SumitNaiksatam#topic Cross-project clean-up patches18:27
*** openstack changes topic to "Cross-project clean-up patches (Meeting topic: networking_policy)"18:27
*** neiljerram has quit IRC18:27
SumitNaiksatamrkukura and I discussed some of these offline18:28
SumitNaiksatam#link https://review.openstack.org/26464218:28
SumitNaiksatam(use of assertions)18:28
SumitNaiksatam#link https://review.openstack.org/#/c/263188/18:28
SumitNaiksatam(use of log.warn)18:28
rkukurathe first one is interesting, since it removes the testing that a boolean is actually returned18:28
SumitNaiksatamrkukura: right, and hence some projects have abandoned it18:28
SumitNaiksatamlets decide one way or the other today whether we want to accept these patches18:29
rkukuraprobably makes sense to try to be consistent in validing the exact values returned, so I think I’d vote to abandon it18:30
SumitNaiksatamrkukura: okay, i tend to agree too18:30
SumitNaiksatamthe latter one seems sane, so i guess we can move forward with that?18:30
*** galstrom is now known as galstrom_zzz18:30
rkukurafor example, I’d hate to see returning None not break an assertFalse() test18:30
SumitNaiksatamrkukura: agreed18:31
rkukurathe latter has not passed CI, right?18:31
*** rossella_s has quit IRC18:31
rkukuranon-voting, but is there an issue?18:31
*** ajmiller has quit IRC18:31
*** rossella_s has joined #openstack-meeting-318:31
SumitNaiksatamrkukura: its a transient failure, i just rechecked it18:31
rkukuraok18:32
*** rockyg has joined #openstack-meeting-318:32
SumitNaiksatamso once the gate-group-based-policy-dsvm-functional comes back successfully i think we can merge this18:32
*** rockyg has left #openstack-meeting-318:32
rkukuraagreed18:32
SumitNaiksatam#topic Open Discussion18:33
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:33
*** galstrom_zzz is now known as galstrom18:33
rkukuraanything related to the summit session proposal deadline on Monday?18:33
SumitNaiksatami think igordcard_ you ran into some problems earlier with liberty devstack setup, but you are past those now?18:33
SumitNaiksatamrkukura: ah good one18:33
igordcard_yes, I was trying to stack master but I was running into some problems18:34
*** e0ne has joined #openstack-meeting-318:34
igordcard_with the liberty release it's fine18:34
SumitNaiksatamigordcard_: okay, i havent tried master off late, the upstream gate job seems to work, so i imagined it might have been okay18:34
SumitNaiksatamigordcard_: what was the problem you were seeing?18:34
SumitNaiksatamso on the topic of submissions, there is a plan to submit one hands-on lab session for showing how services work in our framework18:35
igordcard_I was able to stack at the end, but the CLI wouldn't work ( I figured it was because loading the creds from accrc don't work anymore)18:36
*** ajmiller has joined #openstack-meeting-318:36
SumitNaiksatamif it gets accepted i imagine we will all work on this together as a team18:36
igordcard_and I was also getting too many connections in mysql because of heat-engine18:36
SumitNaiksatamigordcard_: oh okay, interesting18:36
igordcard_the stacking issue let me check here in the old logs18:37
SumitNaiksatamany other talks or labs or demos we want to plan for submission?18:37
igordcard_oh it wasn't loading the group_policy plugin (not found), I think there was some conflict of requirements (wrong instructions followed probably)18:38
SumitNaiksatamigordcard_: okay18:38
SumitNaiksatamhemanthravi: did you decide whether you wanted to submit a talk?18:38
*** egallen has quit IRC18:39
hemanthravinot yet, looking at coming up with something before mon18:39
SumitNaiksatamhemanthravi: okay18:40
hemanthraviany submissions other than the lab?18:40
*** moshele has joined #openstack-meeting-318:40
igordcard_could we submit something about the qos work?18:40
SumitNaiksatamigordcard_: sure, happy to support you if you want to submit something18:41
igordcard_it would be nice to have something for that, even though we still need to figure out the scope of qos for mitaka18:41
SumitNaiksatamigordcard_: if nothing else it will focus us on making progress, its a forcing function :-)18:42
*** sigmavirus24_awa is now known as sigmavirus2418:42
igordcard_and it's something I wanted to discuss a bit today: what's the best for now, allow qos policies to be applied to policy targets, or allow qos policies to be applied across PTGs with the drawback of not being able to use a classifier?18:43
SumitNaiksatam#topic QoS support18:43
*** openstack changes topic to "QoS support (Meeting topic: networking_policy)"18:43
igordcard_SumitNaiksatam: yeah :)18:43
SumitNaiksatamigordcard_: sorry, did not understand the latter part - “with the drawback of not being able to use a classifier?”18:44
*** dtroyer has left #openstack-meeting-318:44
SumitNaiksatamideally we should be doing things are the granularity of the group, right?18:44
igordcard_SumitNaiksatam: the current QoS API only allwos qos policies to be set to ports (or networks, that in turn assign to each port of the network)18:45
SumitNaiksatamigordcard_: right, right18:45
igordcard_so we cannot say, for this PRS with this classifier, apply this qos rule18:45
SumitNaiksatamigordcard_: but PRS always participate in a relationship with PTGs18:47
igordcard_I don't know if the new classifier will be in mitaka18:47
SumitNaiksatamigordcard_: ah the issue is with the classifier18:47
igordcard_yes, we cannot scope to specific traffic18:47
SumitNaiksatamcan we perhaps put a constraint that the resource mapping driver can only support QoS for “any” traffic?18:48
*** Sukhdev has quit IRC18:48
SumitNaiksatamand later relax this constraint, as and when support for classifier is available?18:48
igordcard_that is one of the possibilities I see for now18:48
igordcard_the only possibility for PRS18:49
SumitNaiksatamok18:49
SumitNaiksatamseems reasonable to me to start with this18:49
SumitNaiksatamrkukura: hemanthravi songole: what do you think?18:49
rkukuramakes sense to me18:49
SumitNaiksatamrkukura: i think we would prefer that policy always be applied at the group level, right?18:50
igordcard_also, the policy will in reality be applied to each of the PTs18:50
igordcard_so if the PRS says that the bandwidth limit is 1Mb, it will be 1Mb for each of the PTs of the consuming PTG18:51
SumitNaiksatamigordcard_: yes, and that is fine18:51
igordcard_okay18:51
rkukuraPTG vs. PT, or PTG vs PRS?18:51
SumitNaiksatamigordcard_: oh wait18:51
igordcard_because it is at the neutron port level18:51
SumitNaiksatamigordcard_: hmmm, i think we will need to think through that18:52
*** alexpilotti has quit IRC18:52
SumitNaiksatami dont think applying policy to a PTG implies that we allocating a cumulative “quota” for that PTG (like bandwidht in this case)18:53
SumitNaiksatamhence my initial reaction was that it seems fine18:53
SumitNaiksatamhowever, in this case it seems like we would have to think of the cumulative implications18:53
SumitNaiksatamrkukura: i am not sure i understood your question18:54
*** dandruta has quit IRC18:54
rkukuracould we make a distinction between PTG-level bandwidth being per-PT vs. total?18:55
*** alexpilotti has joined #openstack-meeting-318:55
rkukuraSumitNaiksatam: I was just trying to understand your “applied at the group level” question18:55
SumitNaiksatamrkukura: okay, yeah i think “with the drawback of not being able to use a classifier?” makes sense18:56
igordcard_rkukura: at an implementation level it would not be possible by simply using what neutron provides today.. qos rules per port18:56
SumitNaiksatamrkukura: sorry, copy paste erro18:57
SumitNaiksatami meant, “with the drawback of not being able to use a classifier?” makes sense18:57
SumitNaiksatamwe have three minutes18:57
*** hemanthravi has quit IRC18:57
SumitNaiksatamigordcard_: how about at least you put this level of thoughts in a spec and post it?18:57
igordcard_I can make a PoC for the qos action in the PRS18:57
rkukurasounds good to me18:58
igordcard_SumitNaiksatam: okay I can create a spec with the thoughts18:58
SumitNaiksatammight be much easier to discuss on the spec, and we can certainly follow up in the weekly meetings18:58
SumitNaiksatamigordcard_: yes sure18:58
igordcard_but it won't yet dive into how it would work internally18:58
igordcard_after the PoC I can update it with more detail18:58
SumitNaiksatamigordcard_: np, we understand that this is WIP18:59
SumitNaiksatambut i think having the spec will get the whole team on the same page with regards to get them up to speed with the thinking so far18:59
igordcard_it's all from my side then18:59
SumitNaiksatamigordcard_: thanks!18:59
igordcard_SumitNaiksatam: I see , yeah19:00
SumitNaiksatamigordcard_: assuming you are going to be available, we can make this a weekly discussion topic19:00
SumitNaiksatamalright, thanks everyone for your time today!19:00
SumitNaiksatambye19:00
rkukurabye19:00
tbachmanbye!19:00
SumitNaiksatam#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Thu Jan 28 19:00:54 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-01-28-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-01-28-18.02.txt19:00
*** rkukura has left #openstack-meeting-319:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2016/networking_policy.2016-01-28-18.02.log.html19:01
igordcard_bye19:01
*** kebray has quit IRC19:06
*** lblanchard has quit IRC19:10
*** baoli has quit IRC19:12
*** lblanchard has joined #openstack-meeting-319:14
*** kzaitsev_mb has quit IRC19:15
*** Sukhdev has joined #openstack-meeting-319:20
*** janzian has joined #openstack-meeting-319:20
*** janzian has left #openstack-meeting-319:21
*** iyamahat has quit IRC19:23
*** yamahata has quit IRC19:23
*** Aish has joined #openstack-meeting-319:24
*** peristeri has quit IRC19:24
*** moshele has quit IRC19:25
*** peristeri has joined #openstack-meeting-319:29
*** galstrom is now known as galstrom_zzz19:30
*** kebray has joined #openstack-meeting-319:35
*** salv-orlando has joined #openstack-meeting-319:42
*** iyamahat has joined #openstack-meeting-319:42
*** iyamahat has quit IRC19:42
*** iyamahat has joined #openstack-meeting-319:43
*** iyamahat has quit IRC19:43
*** iyamahat has joined #openstack-meeting-319:49
*** iyamahat has quit IRC19:49
*** salv-orlando has quit IRC19:50
*** yamahata has joined #openstack-meeting-319:51
*** songole has quit IRC19:59
*** dimtruck is now known as zz_dimtruck20:03
*** s3wong has quit IRC20:04
*** iyamahat has joined #openstack-meeting-320:06
*** zz_dimtruck is now known as dimtruck20:10
*** salv-orlando has joined #openstack-meeting-320:17
*** vishwanathj_zzz is now known as vishwanathj20:19
*** galstrom_zzz is now known as galstrom20:20
*** salv-orlando has quit IRC20:30
*** vtech has quit IRC20:33
*** ivar-lazzaro has joined #openstack-meeting-320:33
*** ivar-lazzaro has quit IRC20:34
*** neelashah has quit IRC20:34
*** jmckind has joined #openstack-meeting-320:35
*** piet has quit IRC20:35
*** SumitNaiksatam has quit IRC20:35
*** piet has joined #openstack-meeting-320:36
*** peristeri has quit IRC20:37
*** vgridnev has joined #openstack-meeting-320:37
*** ivar-lazzaro has joined #openstack-meeting-320:38
*** liangy has quit IRC20:40
*** jmckind_ has joined #openstack-meeting-320:41
*** alexpilotti has quit IRC20:43
*** dimtruck is now known as zz_dimtruck20:43
*** jmckind__ has joined #openstack-meeting-320:44
*** alexpilotti has joined #openstack-meeting-320:44
*** jmckind has quit IRC20:44
*** cbouch has joined #openstack-meeting-320:47
*** jmckind_ has quit IRC20:47
*** ivar-lazzaro has quit IRC20:48
*** alexpilotti has quit IRC20:49
*** vtech has joined #openstack-meeting-320:49
*** matrohon has joined #openstack-meeting-320:50
*** jmckind has joined #openstack-meeting-320:53
*** jmckind__ has quit IRC20:56
*** matrohon has quit IRC20:58
*** kavit__ has quit IRC20:58
*** jmckind_ has joined #openstack-meeting-320:59
*** mbound has joined #openstack-meeting-321:00
*** jmckind has quit IRC21:01
*** ShillaSaebi has joined #openstack-meeting-321:02
*** madhu_ak has quit IRC21:05
*** nelsnels_ has quit IRC21:10
*** alexpilotti has joined #openstack-meeting-321:11
*** salv-orlando has joined #openstack-meeting-321:11
*** catherineD|2 has left #openstack-meeting-321:13
*** ivar-lazzaro has joined #openstack-meeting-321:14
*** baoli has joined #openstack-meeting-321:15
*** alexpilotti has quit IRC21:15
*** baoli_ has joined #openstack-meeting-321:15
*** dedery has joined #openstack-meeting-321:16
*** piet has quit IRC21:18
*** dedery has quit IRC21:20
*** Sukhdev has quit IRC21:20
*** baoli has quit IRC21:20
*** alexpilotti has joined #openstack-meeting-321:20
*** madhu_ak has joined #openstack-meeting-321:22
*** SumitNaiksatam has joined #openstack-meeting-321:23
*** baoli_ has quit IRC21:24
*** baoli has joined #openstack-meeting-321:24
*** alexpilotti has quit IRC21:25
*** tbachman_ has joined #openstack-meeting-321:27
ShillaSaebi#startmeeting Ops and Arch Guide Docs Specialty Team21:29
openstackMeeting started Thu Jan 28 21:29:23 2016 UTC and is due to finish in 60 minutes.  The chair is ShillaSaebi. Information about MeetBot at http://wiki.debian.org/MeetBot.21:29
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:29
*** openstack changes topic to " (Meeting topic: Ops and Arch Guide Docs Specialty Team)"21:29
openstackThe meeting name has been set to 'ops_and_arch_guide_docs_specialty_team'21:29
ShillaSaebihello21:29
darrenchi ShillaSaebi21:29
ShillaSaebianyone here for the ops/arch guide meeting21:29
ShillaSaebihi darrenc21:29
*** tbachman has quit IRC21:30
*** tbachman_ is now known as tbachman21:30
sc68calhere21:30
*** tbachman has left #openstack-meeting-321:31
darrencxavpaice sends his apologies21:31
darrenchi sc68cal21:31
njohnstono/21:32
ShillaSaebihi everyone21:32
ShillaSaebialright lets go ahead and get started21:32
ShillaSaebi#topic Open reviews21:32
*** openstack changes topic to "Open reviews (Meeting topic: Ops and Arch Guide Docs Specialty Team)"21:32
ShillaSaebi#link https://review.openstack.org/#/q/status:open+project:openstack/operations-guide,n,z21:33
ShillaSaebiplease see the open reviews and feel free to review/comment21:33
ShillaSaebiany questions on that?21:33
darrencyeah, I need someone to take over the networking patch21:33
ShillaSaebi#link https://review.openstack.org/#/c/222434/21:34
ShillaSaebithis one21:34
njohnstonI'll check with vhoward, one moment21:34
darrencthat's the one21:34
darrencyeah I emailed him, but haven't heard back21:34
ShillaSaebiyeah lets see what vhoward and njohnston come back with21:34
darrencok cheers21:35
ShillaSaebiok cool we can move on until we hear back21:35
*** Sukhdev has joined #openstack-meeting-321:35
ShillaSaebi#topic Ops Meetup in Manchester21:35
vhowardhey guys, told darren today that i'm going to work on that next week21:35
*** openstack changes topic to "Ops Meetup in Manchester (Meeting topic: Ops and Arch Guide Docs Specialty Team)"21:35
ShillaSaebiok cool vhoward21:35
ShillaSaebithanks for the update21:35
vhowardsorry for delay on that21:35
darrencoh thanks vhoward :)21:35
ShillaSaebianyone going to the ops mid cycle meetup from our subteam?21:36
ShillaSaebiDarren started a thread about potentially doing a swarm there and it seems most people are not attending from our group21:36
darrencnot me21:36
darrencasettle can attend21:36
ShillaSaebiso we discussed potentially doing it in Austin21:36
*** kzaitsev_mb has joined #openstack-meeting-321:36
ShillaSaebisc68cal will you be in Manchester21:36
sc68calShillaSaebi: no, i won't.21:37
ShillaSaebiok21:37
ShillaSaebimaybe it's something we can think about for Austin?21:37
ShillaSaebiseems like most members of our team will not be there21:37
darrencWe could do austin, but we'll need to change the deadline21:37
ShillaSaebiyes21:37
*** dedery has joined #openstack-meeting-321:37
ShillaSaebiwe should do that21:37
sc68calsummits are not usually a good place to get work done -.-21:38
sc68calcrippling ADHD21:38
darrencbefore or after summit?21:39
sc68calbefore might be good. I think the problem with after is usually everyone is exhausted21:40
darrenctrue21:40
ShillaSaebiyeah maybe a day before?21:40
darrencyeah that could work21:40
darrencbut is one day enough?21:40
sc68calI mean if nobody is going to the keynote on monday that might be a good time to do face to face21:40
ShillaSaebiill probably be going to the keynote21:41
ShillaSaebido we want to take this offline maybe21:43
darrencsure21:44
ShillaSaebiwe can further discuss it in the thread thats alraedy going21:44
ShillaSaebisc68cal : are u on the existing thread?21:44
sc68calShillaSaebi: is it on openstack-docs?21:44
ShillaSaebiim not sure, darrenc did you send it to the ml21:44
ShillaSaebior was it just to some ppl from the subteam?21:45
darrencppl on the subteam21:45
*** sdake has joined #openstack-meeting-321:45
darrencI can add it to the mailing list21:45
*** banix has quit IRC21:45
*** sdake has quit IRC21:45
ShillaSaebiok21:46
ShillaSaebiML would be great21:46
ShillaSaebithanks21:46
ShillaSaebialright21:46
ShillaSaebi#topic Arch Guide Reorg Efforts21:46
*** openstack changes topic to "Arch Guide Reorg Efforts (Meeting topic: Ops and Arch Guide Docs Specialty Team)"21:46
ShillaSaebi#link https://wiki.openstack.org/wiki/Architecture_Design_Guide_work_items21:46
ShillaSaebihere are the work items that are ongoing for the arch guide21:46
ShillaSaebithe main thing to know here is to commit your work to the draft directory on openstack-manuals/docs/arch-design-draft21:47
ShillaSaebinot the original repo21:47
ShillaSaebilet me know if you have any questions21:47
*** sdake has joined #openstack-meeting-321:48
*** neelashah has joined #openstack-meeting-321:48
sc68calwow there are three arch-design related directories in openstack-manuals21:49
sc68calarch-design, -draft and -rst21:49
sc68calwhoops21:50
ShillaSaebidraft should be in rst format right21:50
sc68calwas - I just haven't run git clean -fd in a while21:50
sc68caljust arch-design and -draft now21:50
darrencyep21:50
*** sdake_ has joined #openstack-meeting-321:50
sc68calgood riddance to docbook21:51
*** shwetaap has quit IRC21:51
sc68calpoor anne had to take the original output from some CMS system, into docbook for the first release of the arch guide21:51
darrenchow painful21:52
*** sdake has quit IRC21:52
ShillaSaebiyeah21:52
ShillaSaebidefinitely21:52
ShillaSaebialright any other questions/comments on that21:53
*** jmckind_ has quit IRC21:53
ShillaSaebi#topic Feedback on arch guide virtual swarm21:53
*** openstack changes topic to "Feedback on arch guide virtual swarm (Meeting topic: Ops and Arch Guide Docs Specialty Team)"21:53
ShillaSaebiOk we had a virtual swarm on 21-22 December and had a lot of help from some of the members of the team21:54
ShillaSaebithank you for the hard work21:54
*** baoli has quit IRC21:55
*** baoli has joined #openstack-meeting-321:55
*** vgridnev has quit IRC21:55
darrencPersonally I think it was difficult to get everyone on the same page in the virtual swarm21:56
ShillaSaebiI agree21:56
ShillaSaebithe time zone differences21:56
ShillaSaebiand being virtual21:56
ShillaSaebiat all random hours21:56
darrencPlus it was difficult for everyone give their input into the changes21:56
darrencyes time zones21:57
darrencthat said, in APAC we had a few ppl working together which was good21:59
ShillaSaebiso hopefully we can shoot for an in person next time21:59
darrencyep21:59
ShillaSaebigreat22:00
darrencalso I think having it before christmas wasn't ideal22:01
*** shwetaap has joined #openstack-meeting-322:01
darrencparticipation was much lower than expected22:01
ShillaSaebilol22:01
ShillaSaebiyeah22:01
ShillaSaebithats a lesson learned22:02
ShillaSaebialright22:02
*** dedery has quit IRC22:02
ShillaSaebido we have anything else we want to discuss22:02
ShillaSaebi#topic open discussion22:02
*** openstack changes topic to "open discussion (Meeting topic: Ops and Arch Guide Docs Specialty Team)"22:02
ShillaSaebifeel free to bring up anything22:03
ShillaSaebiopen discussion22:03
*** katomo has joined #openstack-meeting-322:03
*** dedery has joined #openstack-meeting-322:03
darrencwe need to consider the o'reilly thing for the ops guide22:03
ShillaSaebiwhat was the latest update with that22:04
darrencnothing since lana informed us22:04
darrencI'm not sure what costs are involved in publishing another edition22:06
*** salv-orl_ has joined #openstack-meeting-322:06
katomoShillaSaebi, darrenc, good morning :)22:06
darrenchi katomo22:06
darrencand effort22:06
darrencbut my understanding is o'rielly likes books in asciidoc22:07
ShillaSaebihi katomo22:07
ShillaSaebiok22:07
ShillaSaebimaybe we can check back with Lana22:07
darrencso we would need to convert at some point22:08
ShillaSaebiok22:08
*** salv-orlando has quit IRC22:08
darrencI'll chat to lana22:09
ShillaSaebisounds great22:09
ShillaSaebianything anyone else wants to bring up or discuss?22:09
ShillaSaebiif not, we can get 20 min back22:10
katomoRST conversion ?22:10
katomoalready discussed ?22:10
ShillaSaebifor the arch guide?22:10
ShillaSaebior ops guide?22:10
darrencoh yeah the ops guide needs to be converted22:10
katomoops guide22:10
ShillaSaebiyeah we didn't actually discuss that22:11
darrencthat's the only guide left I think22:11
ShillaSaebiwhen do u guys want to start that22:11
ShillaSaebido we have the blueprint and spec approved22:11
darrencyes22:11
ShillaSaebicool22:11
ShillaSaebiso when do u guys wanna get started22:11
katomoif we don't reorganize ops guide until Newton cycle, we have 2 months to convert22:12
*** lblanchard has quit IRC22:12
darrencbut I think we were going to push it back to the O-release?22:12
katomoI want to start22:12
darrencIf there are ppl available to do it, I don't see why not22:12
*** cbouch has quit IRC22:13
katomoyeah, I believe22:13
darrencWe seem to convert things pretty quickly these days22:13
darrenclet me find the spec22:13
ShillaSaebicool22:14
ShillaSaebiim ready to do it as well22:14
ShillaSaebiwe should do it in the same format22:14
ShillaSaebiassign out chapters and go22:14
darrencCool, we'll need to run this by Lana22:14
ShillaSaebiok22:14
katomook22:15
ShillaSaebii can add it to the specialty team updates email i am sending her22:15
ShillaSaebii already sent it but ill add this on22:15
ShillaSaebiok cool anything else22:15
darrencsounds good22:15
*** iyamahat has quit IRC22:15
*** iyamahat has joined #openstack-meeting-322:16
darrenchttps://blueprints.launchpad.net/openstack-manuals/+spec/ops-guide-rst22:16
darrenchttps://blueprints.launchpad.net/openstack-manuals/+spec/ops-guide-rst22:16
darrenchttps://blueprints.launchpad.net/openstack-manuals/+spec/ops-guide-rst22:16
darrencwhoops22:16
ShillaSaebiheh22:16
*** iyamahat has quit IRC22:17
katomo:)22:17
*** iyamahat has joined #openstack-meeting-322:17
katomoapproved! thanks, darrenc22:17
*** iyamahat has quit IRC22:18
*** jmckind has joined #openstack-meeting-322:18
*** iyamahat has joined #openstack-meeting-322:18
darrencoh I think I'm confused22:19
darrencI drafted this before the Mitaka22:19
ShillaSaebiyea22:20
*** rtheis has quit IRC22:20
*** dedery has quit IRC22:20
*** dedery has joined #openstack-meeting-322:20
darrencso we are doing it for this release22:20
ShillaSaebiyes22:21
*** iyamahat has quit IRC22:21
darrencgosh, time flies22:21
darrencok probably still mention it to Lana22:22
ShillaSaebiok22:22
ShillaSaebiwill do22:22
ShillaSaebi:)22:22
darrencI'll set up the migration page22:22
ShillaSaebigreat22:22
katomo#link https://wiki.openstack.org/wiki/Documentation/Migrate#Operations_Guide22:22
*** e0ne has quit IRC22:22
darrencnice, thanks katomo22:23
katomodarrence: thanks. need update :)22:23
*** FallenPegasus has joined #openstack-meeting-322:23
katomo*darrenc22:23
*** egafford has quit IRC22:23
*** tellesnobrega is now known as tellesnobrega_af22:25
ShillaSaebiok anything else ?22:25
darrencI have nothing else22:25
katomonone22:25
*** jmckind has quit IRC22:25
ShillaSaebiok great22:26
ShillaSaebithanks everyone22:26
ShillaSaebi#endmeeting22:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:26
openstackMeeting ended Thu Jan 28 22:26:49 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_and_arch_guide_docs_specialty_team/2016/ops_and_arch_guide_docs_specialty_team.2016-01-28-21.29.html22:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_and_arch_guide_docs_specialty_team/2016/ops_and_arch_guide_docs_specialty_team.2016-01-28-21.29.txt22:26
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_and_arch_guide_docs_specialty_team/2016/ops_and_arch_guide_docs_specialty_team.2016-01-28-21.29.log.html22:26
katomothanks, all22:27
*** katomo has quit IRC22:27
*** iyamahat has joined #openstack-meeting-322:27
darrencthanks!22:27
*** piet_ has joined #openstack-meeting-322:28
*** kebray has quit IRC22:29
*** bryan_att has quit IRC22:29
*** dedery has quit IRC22:31
*** baoli has quit IRC22:35
*** baoli has joined #openstack-meeting-322:35
*** banix has joined #openstack-meeting-322:38
*** dedery has joined #openstack-meeting-322:40
*** alexpilotti has joined #openstack-meeting-322:41
*** baoli has quit IRC22:46
*** baoli has joined #openstack-meeting-322:47
*** yamahata has quit IRC22:49
*** julim has quit IRC22:50
*** julim has joined #openstack-meeting-322:52
*** galstrom is now known as galstrom_zzz22:52
*** vhoward has quit IRC22:52
*** alexpilotti has quit IRC22:55
*** e0ne has joined #openstack-meeting-322:56
*** dedery has quit IRC22:57
*** alexpilotti has joined #openstack-meeting-322:59
*** e0ne_ has joined #openstack-meeting-323:00
*** e0ne has quit IRC23:02
*** dedery has joined #openstack-meeting-323:03
*** yamamoto has joined #openstack-meeting-323:06
*** neelashah has quit IRC23:07
*** dedery has quit IRC23:08
*** tej has quit IRC23:08
*** tej has joined #openstack-meeting-323:08
*** ShillaSaebi has quit IRC23:10
*** julim has quit IRC23:11
*** bpokorny_ has joined #openstack-meeting-323:12
*** tej has quit IRC23:13
*** mbound has quit IRC23:15
*** bpokorny has quit IRC23:16
*** banix has quit IRC23:19
*** yamamoto has quit IRC23:19
*** kzaitsev_mb has quit IRC23:24
*** kzaitsev_mb has joined #openstack-meeting-323:26
*** e0ne_ has quit IRC23:27
*** alexpilotti has quit IRC23:30
*** jpomeroy has quit IRC23:33
*** FallenPegasus has quit IRC23:37
*** shwetaap has quit IRC23:39
*** bpokorny_ has quit IRC23:39
*** bpokorny has joined #openstack-meeting-323:40
*** alexpilotti has joined #openstack-meeting-323:51
*** tej has joined #openstack-meeting-323:53
*** baoli has quit IRC23:54
*** alexpilotti has quit IRC23:55
*** sigmavirus24 is now known as sigmavirus24_awa23:56
*** amotoki has quit IRC23:56
*** Swami has quit IRC23:57

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