Thursday, 2015-12-17

*** jmckind_ has quit IRC00:01
*** baoli has quit IRC00:02
*** spzala has joined #openstack-meeting-300:06
*** leecalcote has joined #openstack-meeting-300:10
*** tellesnobrega is now known as tellesnobrega_af00:14
*** zz_dimtruck is now known as dimtruck00:15
*** banix has quit IRC00:18
*** yasui_ has quit IRC00:23
*** yasui_ has joined #openstack-meeting-300:26
*** rbak_ has quit IRC00:27
*** dimtruck is now known as zz_dimtruck00:27
*** zz_dimtruck is now known as dimtruck00:29
*** dims has quit IRC00:29
*** pavel_bondar has quit IRC00:34
*** pavel_bondar has joined #openstack-meeting-300:35
*** emilyw has quit IRC00:35
*** mchestr has quit IRC00:36
*** jpomeroy has quit IRC00:42
*** leecalcote has quit IRC00:43
*** dimtruck is now known as zz_dimtruck00:43
*** kzaitsev_mb has quit IRC00:51
*** alexpilotti has joined #openstack-meeting-300:52
*** Swami_ has quit IRC00:54
*** MarkAtwood has quit IRC00:56
*** alexpilotti has quit IRC00:56
*** ajmiller has quit IRC00:57
*** bharathm has quit IRC01:03
*** bpokorny has quit IRC01:04
*** bpokorny has joined #openstack-meeting-301:05
*** mfranc213 has joined #openstack-meeting-301:12
*** mfranc213 has quit IRC01:17
*** mickeys has quit IRC01:18
*** skath_ has quit IRC01:23
*** skath_ has joined #openstack-meeting-301:24
*** etoews has quit IRC01:24
*** zhiyan has quit IRC01:25
*** etoews has joined #openstack-meeting-301:25
*** zhiyan has joined #openstack-meeting-301:28
*** mbound_ has quit IRC01:31
*** zhenguo has joined #openstack-meeting-301:38
*** stanzgy has joined #openstack-meeting-301:44
*** baohua has joined #openstack-meeting-301:48
*** btully has quit IRC01:50
*** mtanino has joined #openstack-meeting-301:59
*** amotoki has joined #openstack-meeting-302:03
*** amotoki_ has joined #openstack-meeting-302:05
*** yasui_ has quit IRC02:06
*** amotoki has quit IRC02:09
*** bpokorny_ has joined #openstack-meeting-302:12
*** ivar-laz_ has joined #openstack-meeting-302:12
*** yamamoto has joined #openstack-meeting-302:14
*** ivar-lazzaro has quit IRC02:15
*** bpokorny has quit IRC02:16
*** ivar-laz_ has quit IRC02:16
*** bpokorny_ has quit IRC02:16
*** yamahata has quit IRC02:19
*** baoli has joined #openstack-meeting-302:20
*** baoli has quit IRC02:22
*** baoli has joined #openstack-meeting-302:22
*** hoangcx has joined #openstack-meeting-302:27
*** yamamoto has quit IRC02:33
*** baoli has quit IRC02:35
*** yasui_ has joined #openstack-meeting-302:35
*** baoli has joined #openstack-meeting-302:36
*** piet has joined #openstack-meeting-302:37
*** s3wong has quit IRC02:40
*** gcb has joined #openstack-meeting-302:44
*** hoangcx has left #openstack-meeting-302:48
*** piet has quit IRC02:52
*** amotoki_ has quit IRC02:57
*** baoli has quit IRC03:00
*** piet has joined #openstack-meeting-303:02
*** alexpilotti has joined #openstack-meeting-303:14
*** yamamoto has joined #openstack-meeting-303:15
*** alexpilotti has quit IRC03:18
*** mfranc213 has joined #openstack-meeting-303:24
*** woodster_ has quit IRC03:26
*** mfranc213 has quit IRC03:29
*** docaedo has quit IRC03:36
*** annp has joined #openstack-meeting-303:41
*** mickeys has joined #openstack-meeting-303:41
*** mickeys has quit IRC03:46
*** docaedo has joined #openstack-meeting-303:47
*** amotoki has joined #openstack-meeting-303:47
*** amotoki has quit IRC03:50
*** ddieterly has quit IRC03:53
*** amotoki has joined #openstack-meeting-303:55
*** amotoki_ has joined #openstack-meeting-304:02
*** amotoki has quit IRC04:05
*** piet has quit IRC04:26
*** alexpilotti has joined #openstack-meeting-304:35
*** spzala has quit IRC04:37
*** alexpilotti has quit IRC04:40
*** gcb has quit IRC04:52
*** anuragpalsule has joined #openstack-meeting-304:58
*** mtreinish has quit IRC05:08
*** bpokorny has joined #openstack-meeting-305:08
*** numans has joined #openstack-meeting-305:15
*** mtreinish has joined #openstack-meeting-305:17
*** vahidh has quit IRC05:29
*** mtanino has quit IRC05:30
*** btully has joined #openstack-meeting-305:34
*** vahidh has joined #openstack-meeting-305:34
*** MarkAtwood has joined #openstack-meeting-305:36
*** mfranc213 has joined #openstack-meeting-305:36
*** mfranc213 has quit IRC05:40
*** btully has left #openstack-meeting-305:41
*** bpokorny has quit IRC05:49
*** piet has joined #openstack-meeting-305:50
*** piet has quit IRC06:04
*** hoangcx has joined #openstack-meeting-306:05
*** hoangcx has left #openstack-meeting-306:06
*** piet has joined #openstack-meeting-306:09
*** sarob has quit IRC06:10
*** sarob has joined #openstack-meeting-306:11
*** davidlenwell has quit IRC06:12
*** davidlenwell has joined #openstack-meeting-306:14
*** hdaniel has joined #openstack-meeting-306:20
*** piet has quit IRC06:22
*** ivar-lazzaro has joined #openstack-meeting-306:31
*** zehicle has joined #openstack-meeting-306:54
*** stanzgy has quit IRC07:07
*** stanzgy has joined #openstack-meeting-307:07
*** pavel_bondar_ has joined #openstack-meeting-307:10
*** alexpilotti has joined #openstack-meeting-307:12
*** alexpilotti has quit IRC07:16
*** hdaniel has quit IRC07:17
*** irenab has quit IRC07:24
*** tobe has joined #openstack-meeting-307:27
*** alexpilotti has joined #openstack-meeting-307:36
*** dedery has joined #openstack-meeting-307:37
*** alexpilotti has quit IRC07:40
*** stendulker has joined #openstack-meeting-307:41
*** itxaka has joined #openstack-meeting-307:42
*** hdaniel has joined #openstack-meeting-307:42
*** kzaitsev_mb has joined #openstack-meeting-307:43
*** dedery has quit IRC07:46
*** dedery has joined #openstack-meeting-307:48
*** hdaniel has quit IRC07:53
*** annp has quit IRC07:54
*** safchain has joined #openstack-meeting-307:54
*** vahidh has quit IRC07:59
*** vahidh has joined #openstack-meeting-307:59
*** ifat_afek has joined #openstack-meeting-308:00
*** jtomasek has joined #openstack-meeting-308:06
*** irenab has joined #openstack-meeting-308:12
*** shwetaap has joined #openstack-meeting-308:13
*** kzaitsev_mb has quit IRC08:16
*** hdaniel has joined #openstack-meeting-308:16
*** ivar-lazzaro has quit IRC08:22
*** e0ne has joined #openstack-meeting-308:23
*** JeanBriceCombebi has joined #openstack-meeting-308:29
*** klkumar has joined #openstack-meeting-308:32
*** MattMan has quit IRC08:33
*** MattMan has joined #openstack-meeting-308:33
*** alexpilotti has joined #openstack-meeting-308:36
*** MarkAtwood has quit IRC08:38
*** annp has joined #openstack-meeting-308:38
*** tfukushima has joined #openstack-meeting-308:38
*** e0ne has quit IRC08:38
*** e0ne has joined #openstack-meeting-308:40
*** alexpilotti has quit IRC08:40
*** FallenPegasus has joined #openstack-meeting-308:48
*** calbers has joined #openstack-meeting-308:49
*** e0ne has quit IRC08:53
*** alexpilotti has joined #openstack-meeting-308:58
*** baohua has quit IRC08:59
*** matrohon has joined #openstack-meeting-309:01
*** calbers has quit IRC09:04
*** briancurtin has quit IRC09:04
*** JeanBriceCombebi has quit IRC09:05
*** amotoki_ has quit IRC09:06
*** dedery has quit IRC09:07
*** kzaitsev_mb has joined #openstack-meeting-309:10
*** briancurtin has joined #openstack-meeting-309:13
*** kzaitsev_mb has quit IRC09:16
*** briancurtin has quit IRC09:17
*** dedery has joined #openstack-meeting-309:17
*** betherly has quit IRC09:19
*** kzaitsev_mb has joined #openstack-meeting-309:23
*** calbers has joined #openstack-meeting-309:23
*** jlanoux has joined #openstack-meeting-309:25
*** zigo has quit IRC09:25
*** zigo_ has joined #openstack-meeting-309:26
*** FallenPegasus has quit IRC09:26
*** salv-orlando has joined #openstack-meeting-309:28
*** calbers has quit IRC09:32
*** amotoki has joined #openstack-meeting-309:33
*** tobe has quit IRC09:38
*** betherly has joined #openstack-meeting-309:38
*** tobe has joined #openstack-meeting-309:40
*** tobe has quit IRC09:41
*** tobe has joined #openstack-meeting-309:41
*** amotoki has quit IRC09:44
*** briancurtin has joined #openstack-meeting-309:45
*** dedery has quit IRC09:45
*** mbound_ has joined #openstack-meeting-309:45
*** dedery has joined #openstack-meeting-309:45
*** tobe has quit IRC09:46
*** vahidh has quit IRC09:54
*** e0ne has joined #openstack-meeting-309:55
*** JeanBriceCombebi has joined #openstack-meeting-309:56
*** vahidh has joined #openstack-meeting-309:57
*** ihrachys has joined #openstack-meeting-310:03
*** e0ne has quit IRC10:05
*** mbound_ has quit IRC10:06
*** masterbound has joined #openstack-meeting-310:06
*** mbound_ has joined #openstack-meeting-310:09
*** masterbound has quit IRC10:09
*** mickeys has joined #openstack-meeting-310:12
*** wojdev has joined #openstack-meeting-310:13
*** JeanBriceCombebi has quit IRC10:15
*** kzaitsev_mb has quit IRC10:15
*** kzaitsev_mb has joined #openstack-meeting-310:18
*** armax has quit IRC10:20
*** SridarK has quit IRC10:20
*** shakamunyi has quit IRC10:20
*** shakamunyi has joined #openstack-meeting-310:21
*** superflyy has quit IRC10:21
*** barra204 has joined #openstack-meeting-310:21
*** mickeys has quit IRC10:21
*** ihrachys has quit IRC10:21
*** ihrachys has joined #openstack-meeting-310:22
*** ihrachys has quit IRC10:23
*** armax has joined #openstack-meeting-310:23
*** ihrachys has joined #openstack-meeting-310:24
*** ifat_afek has quit IRC10:35
*** Claudio1 has joined #openstack-meeting-310:36
*** robcresswell has left #openstack-meeting-310:37
*** Claudio1 has quit IRC10:39
*** e0ne has joined #openstack-meeting-310:43
*** yamahata has joined #openstack-meeting-310:48
*** stanzgy has quit IRC10:49
*** mbound_ has quit IRC10:50
*** JeanBriceCombebi has joined #openstack-meeting-310:53
*** vmahe has joined #openstack-meeting-310:54
*** annp has quit IRC10:55
*** mbound_ has joined #openstack-meeting-310:55
*** shwetaap has quit IRC10:57
*** wojdev has quit IRC10:58
*** mbound_ has quit IRC10:59
*** wojdev has joined #openstack-meeting-311:00
*** klkumar has quit IRC11:04
*** dims has joined #openstack-meeting-311:07
*** JeanBriceCombebi has quit IRC11:07
*** sambetts-afk is now known as sambetts11:08
*** salv-orlando has quit IRC11:08
*** salv-orlando has joined #openstack-meeting-311:11
*** Claudio2 has joined #openstack-meeting-311:11
*** salv-orlando has quit IRC11:12
*** mbound_ has joined #openstack-meeting-311:12
*** salv-orlando has joined #openstack-meeting-311:12
*** salv-orl_ has joined #openstack-meeting-311:15
*** klkumar has joined #openstack-meeting-311:17
*** yamahata has quit IRC11:18
*** salv-orlando has quit IRC11:18
*** stendulker has quit IRC11:19
*** annp has joined #openstack-meeting-311:21
*** Claudio2 has quit IRC11:25
*** mbound_ has quit IRC11:25
*** wojdev has quit IRC11:25
*** annp has quit IRC11:32
*** tfukushima has quit IRC11:35
*** baohua has joined #openstack-meeting-311:37
*** jlanoux has quit IRC11:37
*** alexpilotti has quit IRC11:38
*** betherly has quit IRC11:39
*** ifat_afek has joined #openstack-meeting-311:41
*** yamamoto has quit IRC11:42
*** betherly has joined #openstack-meeting-311:44
*** klkumar has quit IRC11:52
*** briancurtin has quit IRC11:53
*** betherly has quit IRC11:53
*** irenab has quit IRC11:56
*** klkumar has joined #openstack-meeting-311:59
*** julim has joined #openstack-meeting-312:05
*** rtheis has joined #openstack-meeting-312:17
*** itxaka is now known as itxaka|afk12:22
*** yamamoto has joined #openstack-meeting-312:23
*** pavel_bondar has quit IRC12:24
*** jaypipes has joined #openstack-meeting-312:26
*** irenab has joined #openstack-meeting-312:28
*** mbound_ has joined #openstack-meeting-312:29
*** briancurtin has joined #openstack-meeting-312:29
*** wojdev has joined #openstack-meeting-312:33
*** betherly has joined #openstack-meeting-312:41
*** amotoki has joined #openstack-meeting-312:43
*** amotoki has quit IRC12:46
*** baoli_ has joined #openstack-meeting-312:54
*** salv-orl_ has quit IRC13:04
*** yamamoto has quit IRC13:08
*** dslevin_ has joined #openstack-meeting-313:09
*** salv-orlando has joined #openstack-meeting-313:09
*** briancurtin has quit IRC13:17
*** mwagner_lap has joined #openstack-meeting-313:18
*** briancurtin has joined #openstack-meeting-313:18
*** yamamoto has joined #openstack-meeting-313:20
*** ujuc_ has joined #openstack-meeting-313:21
*** vgridnev has joined #openstack-meeting-313:22
*** briancurtin_ has joined #openstack-meeting-313:23
*** betherly has quit IRC13:29
*** betherly has joined #openstack-meeting-313:29
*** betherly_ has joined #openstack-meeting-313:32
*** betherly has quit IRC13:33
*** betherly_ is now known as betherly13:33
*** AndreyPavlov has joined #openstack-meeting-313:33
*** mbound_ has quit IRC13:35
*** dedery_ has joined #openstack-meeting-313:36
*** itxaka|afk is now known as itxaka13:37
*** baohua has quit IRC13:39
*** sigmavirus24_awa is now known as sigmavirus2413:39
*** dedery has quit IRC13:40
*** dedery_ has quit IRC13:41
*** baohua has joined #openstack-meeting-313:41
*** betherly_ has joined #openstack-meeting-313:41
*** yamamoto has quit IRC13:46
*** tosky has joined #openstack-meeting-313:46
*** ifat_afek has quit IRC13:49
*** yamamoto has joined #openstack-meeting-313:50
*** alexpilotti has joined #openstack-meeting-313:55
*** egafford has joined #openstack-meeting-313:57
*** esikachev has joined #openstack-meeting-313:57
*** dslevin_ has quit IRC13:57
*** Akanksha08 has joined #openstack-meeting-313:59
*** huichun has joined #openstack-meeting-313:59
elmiko#startmeeting sahara14:00
openstackMeeting started Thu Dec 17 14:00:07 2015 UTC and is due to finish in 60 minutes.  The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
vgridnevhey folks14:00
elmikohi folks14:00
*** alexpilotti has quit IRC14:00
esikachevhey!14:00
NikitaKonovalovhi14:00
huichunhi14:00
toskyhi14:00
egaffordo/14:00
elmiko#chair vgridnev14:00
openstackCurrent chairs: elmiko vgridnev14:00
*** davidsha has joined #openstack-meeting-314:00
AndreyPavlovhi14:01
elmikoi'll give folks a minute or two to roll in before we get started14:01
*** tellesnobrega_af is now known as tellesnobrega14:01
elmikook then14:02
elmiko#topic sahara@sahara-dashboard14:02
*** openstack changes topic to "sahara@sahara-dashboard (Meeting topic: sahara)"14:02
elmiko;)14:03
elmikoi think croberts might be out14:03
elmikoanything to report here vgridnev ?14:03
vgridnevactually it's going, there are several changes was proposed, also integration tests job was merged to project config14:03
elmikocool14:03
*** tmckay has joined #openstack-meeting-314:03
vgridnevso we need to wait for some changes on horizon side14:04
*** mfranc213 has joined #openstack-meeting-314:04
elmikowhat changes are we waiting for?14:04
NikitaKonovalovvgridnev: so horizon will be running our intergation tests in their gate?14:04
vgridnevto make pluggable integration tests, let me search for the link14:05
elmikovgridnev: thanks14:05
vgridnevNikitaKonovalov, no, will run our own tests14:05
vgridnev#link https://review.openstack.org/#/c/253608/14:06
NikitaKonovalovok, at least we will no when our dashboard breaks after some horizon changes14:06
toskyor that the tests are broken by some horizon core change14:07
toskybut yeah, better than now14:07
elmikoshould be nice14:07
vgridnevyep, it's probably bad, but we need to make our integrations tests working first14:07
elmikoanything else for this topic?14:07
vgridnevI think no, let's move on14:07
elmiko#topic News/Updates14:07
*** openstack changes topic to "News/Updates (Meeting topic: sahara)"14:07
elmikoso, what's everyone been up to?14:08
vgridnevI'm working with improving ambari plugin right now14:08
NikitaKonovalovI'm still in internal research and testing, so not much to share14:09
*** jxwang has joined #openstack-meeting-314:09
egaffordImage validation SPI spec is up; I have a working and tested sahara.plugins.images module. Doing cleanup before review @ this point.14:09
toskya bit of reviews and small enhancement, nothing more for now14:09
NikitaKonovalovI hope I'll get some of the docs finished and finally published to upstream14:09
elmikoi'm working on migrating the cdh passwords into the external key manager, but i've hit a snag14:09
*** zehicle has quit IRC14:09
elmikoalso, going to start setting up a prototype for the apiv2 work14:09
esikachevworking on spec, fixing bugs in scenario framework14:10
elmikook, moving along14:11
elmiko#topic Discuss sahara scenario tests extraction14:11
*** openstack changes topic to "Discuss sahara scenario tests extraction (Meeting topic: sahara)"14:11
tmckayI'm going to add a spec and patch for a --ironic or --baremetal flag on sie14:11
tmckaydoh, missed the updates :)14:12
elmikooops, sorry tmckay14:12
tmckayI was typing14:12
tmckayheh14:12
elmikonp14:12
elmiko#link https://review.openstack.org/#/c/250419/14:12
*** wojdev has quit IRC14:12
elmikothis spec is looking good, is there anything more to discuss on the topic?14:12
vgridnevspec is almost approved, but I think that we should wait for SergeyLukjanov to approve it14:13
esikachev+114:13
elmikoi'm ok with that14:13
toskyI have an implementation question, related to repository extraction, but I guess it can wait (for the record: if in such cases a mechanism like git grafting is used)14:14
elmikoyou can ask now if you'd like tosky14:14
tosky(or it is just "initial import, dump of the revision xyz from this repository")14:14
*** mfranc213 has quit IRC14:15
toskyI think right now it's mostly done with a dump of the last version from the previous repository (I could check with sahara dashboard for example), but still it would be nice to easily track the old history14:15
vgridnevtosky, you can create local repo, but this repo will be imported during moving to openstack namespace14:16
*** mfranc213 has joined #openstack-meeting-314:16
elmikoso, it sounds like the question is are we going to keep the git history when migrating to the new repository? (is that accurate tosky ?)14:16
toskyelmiko: keep the history is one way (apply git filtering to the old repository and extract the history)14:16
*** spzala has joined #openstack-meeting-314:16
egaffordI'm still concerned that this will make it harder to make plugins truly plugins (unless plugins require multiple repos to implement, and plug into a server framework and a test framework,) but I think we're deciding that that's okay for now (and we have a lot of harder work in the server to allow plugins to detach anyway, so it's probably fine.)14:17
toskythe other way is allow to access the history from the new repository, but without importing it; this is git grafting14:17
elmikoyea, i guess we can't keep the whole history, but only the scenario parts14:17
toskyfor reference to git grafting: https://git.wiki.kernel.org/index.php/GraftPoint14:17
elmikotosky: thanks!14:17
elmikoegafford: it's a good point14:17
elmikoegafford: i think we would need much more work on the plugin separation before we could contemplate scenario tests bundled with plugins14:18
egaffordIt is, but I can see the argument that we should do this now, and maybe we can wire the test repo for plugability later when we get closer to that long-term goal.14:18
toskybasically you don't have the old history, but the repository allow "joining" the old repository (if the user does some steps) and do a unified search14:18
tmckaytosky, +114:19
*** jlanoux has joined #openstack-meeting-314:19
elmikoegafford: imo, when we get closer to having true plugin separation, then we should revisit scenario test bundling as well14:19
tmckayas time goes on, the need to search the old repo lessens14:19
elmikotosky: might be worth it, if we can setup the infra to do it14:19
elmikotrue14:19
elmikotosky: do you know if any other openstack projects have done this?14:20
toskyelmiko: I have to say I don't know the details, but you don't need special infrastructure, it's the way you create the new repository and you organize the old one before the removal/split14:20
tmckayI found myself wanting to search before the "savanna" rename a few times, but not many ...14:20
toskyand no, I don't think it was done before, but I may be wrong14:20
elmikotosky: ah, interesting14:20
toskythat's why SergeyLukjanov could have helped with his infra knowledge :)14:20
elmikotosky: would you mind making a comment about that on the review?14:20
toskyelmiko: sure14:21
toskyI will keep the +114:21
*** markvoelker has quit IRC14:21
elmiko#action tosky to comment on the scenario separation spec about git grafting the history14:21
elmikocool, thanks14:21
elmikoany other questions/comments/concerns about the scenario test separation?14:22
tmckayit would have been handy in the rename move, I think :)14:22
tmckaythe grafting, I mean14:22
*** jschwarz has joined #openstack-meeting-314:22
elmikoagreed14:22
elmikook, rolling along...14:23
elmiko#topic API v2 progress14:23
*** openstack changes topic to "API v2 progress (Meeting topic: sahara)"14:23
elmikonot a ton to report here14:23
elmikothe spec could use more reviews14:23
elmiko#link https://review.openstack.org/#/c/212172/14:23
elmikoother than that, i am still working on setting up the wiki page for the individual work items to be generated14:24
elmikoand i am starting to create a local prototype for the /v2 endpoints14:24
elmikoany questions or comments about v2?14:24
*** neelashah has joined #openstack-meeting-314:25
tmckayv2 is awesome14:25
elmikolol14:25
tmckaythe best api ever14:25
*** wojdev has joined #openstack-meeting-314:25
elmikobest until v3!14:25
elmiko;)14:25
elmikook then...14:25
tmckaywhoa, v3 ... that's never been done before!14:26
elmikohaha14:26
elmiko#topic New CLI14:26
*** openstack changes topic to "New CLI (Meeting topic: sahara)"14:26
*** jmckind has joined #openstack-meeting-314:26
elmikowas there anything else to discuss on this topic, or should we remove it from the agenda?14:26
vgridnevlet's remove that14:27
egaffordIt's a pretty great new CLI!14:27
AndreyPavlovhmm I guess we have already discussed everything few weeks ago :)14:27
elmikoyea, i think so14:27
elmikoi'll remove it after the meeting14:27
tosky(elmiko: added a comment to the spec related to tests, which I missed before, my fault)14:27
elmiko#topic Open discussion14:27
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:27
elmikotosky: ack, thank you!14:27
elmikoany other business folks?14:27
toskyyes:14:28
* elmiko hands the mic to tosky 14:28
toskyplease vote on this review on tempest https://review.openstack.org/#/c/255968/ (thanks vgridnev)14:28
*** mbound_ has joined #openstack-meeting-314:28
tmckaygeneral comment, I should be more active upstream starting in January.  I've been buried in a hole for a while ;-)14:28
tmckayso, you can count on me for patches, reviews, etc14:28
toskythe tests there could move to our repository at some point, but pending some dependencies; in the meantime we need that change to support the testing on different clusters14:28
elmikotmckay: \o/14:29
elmikotosky: ack, added to the queue14:29
*** tmazur has joined #openstack-meeting-314:29
toskyvgridnev already put you all in the review, but please take a look :)14:29
*** markvoelker has joined #openstack-meeting-314:29
elmikofor those of us who are unfamiliar with tempest, is there anything we should know about that review?14:30
*** peristeri has joined #openstack-meeting-314:30
vgridnevnothing. just vote with +114:30
tosky:d14:30
tosky:D14:30
elmikolol, easy enough...14:30
elmiko#link https://review.openstack.org/#/c/255968/14:31
toskyit simply add support for default templates for the various supported plugins, so that the API tests works in any case, regardless of the set of enabled plugins14:31
toskyno fancy code change, if you check the code, just some additional dictionaries14:31
elmikoah, cool14:31
elmikothanks tosky, and vgridnev14:31
elmikoany other topics to discuss?14:32
*** hdaniel has quit IRC14:32
vgridnevwill we have next 2 meetings?14:32
elmikoi imagine not for next week14:32
*** jcook has quit IRC14:32
tmckayeven the week after ...14:33
elmikoand it seems like many openstack projects are taking the following week off as well14:33
tmckaymany of us will be PTO14:33
elmikoyea14:33
tmckayfirst week of January?14:33
elmikoi think so14:33
tmckaythat would be the 7th14:33
elmikoyea14:33
toskybut then, for people in Russia, don't you have your holidays that time?14:33
elmikoso, next meeting will be January 7th 1800UTC14:33
NikitaKonovalovwe have hollidays 1 - 10th of January14:34
elmikogood question tosky14:34
tmckayheh14:34
tmckayso adjourn til the 14th?14:34
elmikoi think so14:34
tmckaythere is always IRC, and openstack-dev, after all14:34
elmikook, scratch that earlier memo14:34
*** piet has joined #openstack-meeting-314:34
*** lblanchard has joined #openstack-meeting-314:34
elmikonext meeting will be January 14th, 1400UTC14:34
*** alexpilotti has joined #openstack-meeting-314:34
elmikoin openstack-meeting-314:35
huichun vgridnev schedule edp patch is too old https://review.openstack.org/#/c/182310/         My intergation test patch https://review.openstack.org/#/c/255173/ has rebase issue14:35
vgridnevwhat kind of rebase issues?14:35
huichunSo can Intergation test patch do not rebase on that?14:35
*** jcook has joined #openstack-meeting-314:36
huichunRebase error I am working on that issue14:36
* tmckay brb14:36
*** alexpilotti has quit IRC14:37
elmikoany other topics?14:39
*** alexpilotti has joined #openstack-meeting-314:40
vgridnev514:40
vgridnev414:40
vgridnev314:40
vgridnev214:40
AndreyPavlovNOOOO14:40
*** jlanoux has quit IRC14:40
vgridnev1.514:40
vgridnev114:40
vgridnev#endmeeting14:40
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"14:40
openstackMeeting ended Thu Dec 17 14:40:42 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-12-17-14.00.html14:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-12-17-14.00.txt14:40
elmikoAndreyPavlov: did you have something?14:40
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-12-17-14.00.log.html14:40
elmikooops14:40
elmikothanks all14:40
NikitaKonovalovbb14:40
AndreyPavlovelmiko: actually no :)14:41
elmikohehe14:41
toskyo/14:41
*** tosky has left #openstack-meeting-314:41
*** AndreyPavlov has left #openstack-meeting-314:41
*** ChuckC has joined #openstack-meeting-314:42
*** jxwang has quit IRC14:43
*** yamamoto has quit IRC14:46
*** yamamoto has joined #openstack-meeting-314:46
*** jpomeroy has joined #openstack-meeting-314:48
*** jlanoux has joined #openstack-meeting-314:48
*** baohua has quit IRC14:50
*** esikachev has quit IRC14:51
*** sanghai has joined #openstack-meeting-314:53
*** betherly_ has quit IRC14:54
*** stephen-ma has joined #openstack-meeting-314:55
*** mlavalle has joined #openstack-meeting-314:56
*** johnbelamaric has joined #openstack-meeting-314:58
*** pc_m has joined #openstack-meeting-314:59
carl_baldwinhi14:59
yamamotohi14:59
mlavalleo/14:59
xiaohhuihello14:59
johnbelamarichi14:59
carl_baldwin#startmeeting neutron_l315:00
openstackMeeting started Thu Dec 17 15:00:11 2015 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
haleybhi15:00
carl_baldwin#topic Announcements15:00
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:00
ChuckCo/15:00
*** annegentle has joined #openstack-meeting-315:01
carl_baldwinThe release schedule page has moved15:01
carl_baldwin#link http://docs.openstack.org/releases/schedules/mitaka.html15:01
*** briancurtin_ has quit IRC15:01
*** juno_zhu has joined #openstack-meeting-315:01
carl_baldwinWe're somewhere around the middle of Mitaka-215:01
*** dtardivel has joined #openstack-meeting-315:01
*** dslev has joined #openstack-meeting-315:01
carl_baldwinConsidering that many will be taking vacation around Christmas and New Years, it is coming up quickly.15:02
carl_baldwinAnything else to announce?15:02
carl_baldwin#topic Bugs15:03
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:03
carl_baldwinmlavalle: ping15:03
mlavallehi15:03
mlavallewe have the same 2 high importance bugs as last week plus one15:03
mlavallefirst one is https://bugs.launchpad.net/neutron/+bug/147810015:04
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:04
mlavalleCedirc pushed next PS to proposed solution and is awaiting reviews: https://review.openstack.org/#/c/205631/15:04
mlavalleany other comments on this one?15:05
carl_baldwinI'll review that one if I can figure out how to read the new gerrit patch review page.15:05
*** piet has quit IRC15:05
* carl_baldwin thinks someone hit it with an ugly stick15:06
mlavallecarl_baldwin: yeah, I got confused last night as well :-)15:06
mlavallenext up is https://bugs.launchpad.net/neutron/+bug/151626015:06
openstackLaunchpad bug 1516260 in neutron "L3 agent sync_routers timeouts may cause cluster to fall down" [High,In progress] - Assigned to Oleg Bondarev (obondarev)15:06
*** rbak has joined #openstack-meeting-315:06
*** Akanksha08 has left #openstack-meeting-315:07
mlavalleamuller has a fix proposed here https://review.openstack.org/#/c/245432/ that has been -1 recently so it needs next revision15:07
*** wojdev has quit IRC15:07
*** vikram_ has joined #openstack-meeting-315:07
mlavalleand obondarev has another solution proposed https://review.openstack.org/#/c/234067/. This one is awaiting review15:07
carl_baldwinI would like clarification about the relationship between the two proposed fixes.  I'll add a comment to the bug report.15:08
*** lizk_ has joined #openstack-meeting-315:08
mlavallethere's been some discussion between amuller and obondarev in the Gerrit. Please see the comments....15:09
mlavalleFinally, we have a new one https://bugs.launchpad.net/neutron/+bug/152491615:09
openstackLaunchpad bug 1524916 in neutron "neutron-ns-metadata-proxy uses ~25MB/router in production" [High,New]15:09
mlavalleI went through the comments last night and it wasn't clear to me whether we really think this is an issue or not15:10
mlavalleI pinged ajo earlier today, but hasn't responded. I'll follow up with him15:10
*** vgridnev has quit IRC15:10
mlavalleany comments or insights?15:11
*** wojdev has joined #openstack-meeting-315:11
mlavalleif not, I want to mention that I am going through the list of bugs, purging and updating15:12
*** hdaniel has joined #openstack-meeting-315:12
mlavallethere is a number of old reports without activity for a long time that I am marking incomplete15:12
carl_baldwinhaleyb: Do you recall looking at memory usage of the metadata proxy in HP public cloud?  I have a vague recollection.15:12
*** piet has joined #openstack-meeting-315:13
haleybcarl_baldwin: i think so, since we're spinning-up so many.  i think kuba (red hat) or ajo did too15:13
haleybi didn't see any easy solution since part of it was the modules it imported15:14
carl_baldwinIt never seemed to be a High importance problem for us.  We had other problems with 100s of routers on the network node before that.15:15
carl_baldwinI'm considering bumping it down in priority.  Maybe I'll suggest that on the bug report and see what the reaction is.15:15
*** JeanBriceCombebi has joined #openstack-meeting-315:16
mlavallecarl_baldwin: that is all I have as far as bugs15:16
carl_baldwinmlavalle: Thanks for your work on scrubbing the old bugs.15:16
* carl_baldwin is the Neutron bug deputy this week. Thinking of trying to do the same with the overall Neutron bugs.15:17
carl_baldwinmlavalle: Great work!15:17
mlavalle:-)15:18
carl_baldwin#topic Routed Network Segments15:18
*** openstack changes topic to "Routed Network Segments (Meeting topic: neutron_l3)"15:18
carl_baldwinThe demand for this continues to grow.  I think this is going to be a very important project for Neutron.15:18
carl_baldwinHowever, consensus still seems distant.15:18
carl_baldwinI'm currently discussing with armax and kevinbenton (approver for this blueprint) to explore options and reach consensus before releasing the next version of the spec in to the wild.15:19
carl_baldwinIf that goes well, it could be a huge step toward getting consensus.15:20
carl_baldwinAnyway, we're going to need developers to work on this once it is achieved.15:20
carl_baldwinThat's all.15:20
* mlavalle want to pitch in15:21
mlavallewants^^^15:21
*** jlanoux has quit IRC15:21
vikram_carl_baldwin: I m in15:21
carl_baldwinmlavalle: It will be great to have your help.15:21
carl_baldwinvikram_: :)15:22
*** kzaitsev_mb has quit IRC15:23
carl_baldwin#topic bgp-dynamic-routing15:23
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:23
carl_baldwinvikram_: ping15:23
carl_baldwinI think tidwellr is out for the rest of the year on vacation.15:23
vikram_carl_baldwin: pong15:23
mlavallehe must be enjoying the baby15:24
*** jlanoux has joined #openstack-meeting-315:24
vikram_carl_baldwin: I am working for the DVR stuff now15:24
vikram_carl_baldwin: Need some review help for Agent, Scheduler and Driver patch15:24
vikram_carl_baldwin: These patches are almost done.. One round of review would be helpful15:25
*** alexpilotti has quit IRC15:25
*** egafford has left #openstack-meeting-315:25
juno_zhuvikram_: i can review your patch15:25
carl_baldwinvikram_: From the neutron meeting on Tuesday, it sounds like the merges conflicts are scaring people away.15:25
vikram_carl_baldwin: Will resolve it15:26
carl_baldwinvikram_: Could you link the specific patches you want reviewed here?15:26
vikram_carl_baldwin: and make it clean ..15:26
vikram_carl_baldwin: 1 sec15:26
*** anuragpalsule has quit IRC15:27
vikram_https://review.openstack.org/#/c/207607/15:27
vikram_https://review.openstack.org/#/c/207625/15:28
vikram_https://review.openstack.org/#/c/207635/15:28
vikram_that's all15:28
vikram_juno_zhu: thanks;)15:29
carl_baldwinvikram_: Thank you.  I will answer your call to review this week.15:29
vikram_carl_baldwin: Thanks ;)15:29
* carl_baldwin really hopes he can figure out that new review page on gerrit. ;)15:29
juno_zhuvikram_: why not create a new review patch including all the code changes and then review the new patch15:30
vikram_juno_zhu: change is huge15:30
juno_zhuvikram_: you mentioned in last meeting that bgp dynamic routing would be moved from service plugin to ml215:31
vikram_juno_zhu: so the code is broken in pieces for effective review15:31
juno_zhuvikram_: you have not updated the code about this change15:31
vikram_juno_zhu: it already moved15:31
vikram_juno_zhu: it's ml2 now15:31
juno_zhuvikram_: which patch?15:32
vikram_juno_zhu: the patches I requested for review is related to agent, scheduler and driver15:32
*** alexpilotti has joined #openstack-meeting-315:32
vikram_juno_zhu: CRUD patch needs Ryan attention ;)15:32
vikram_juno_zhu: provided the link above..15:33
juno_zhuvikram_: thanks15:33
vikram_juno_zhu: https://review.openstack.org/#/c/201621/15:33
vikram_juno_zhu: CRUD patch15:33
carl_baldwin#topic dns-resolution15:33
*** openstack changes topic to "dns-resolution (Meeting topic: neutron_l3)"15:33
mlavallehi15:34
mlavalleI got https://review.openstack.org/#/c/212213/ reviewed late last week. armax proposed improving it decoupling functionality from ml215:34
carl_baldwinmlavalle: This one was fun this week.  :)15:34
mlavalleyeah it is15:35
mlavalleso I am re-coding along the ml2 extension manager line that he suggested15:35
*** mtanino has joined #openstack-meeting-315:36
mlavalleI am almost done. I should be done today and will start testing it again today. I expect to have it ready for review again at trhe end of this week15:36
mlavallethe imporvements are what carl_baldwin and I discussed on Monday15:36
carl_baldwinmlavalle: Great, ping me when ready and I'll review.15:36
mlavallethat's all I have this week. Thanks to carl_baldwin and armax for the help15:37
carl_baldwinmlavalle: Still, good progress here.  It is cool to see the functionality coming together.15:37
carl_baldwin#topic Address Scopes15:37
*** openstack changes topic to "Address Scopes (Meeting topic: neutron_l3)"15:37
mlavalleyeah it's completely funtional and bug free. The discussion now is on implementation improvement15:38
carl_baldwinThis topic has seen some good progress this week.15:38
carl_baldwinThe next review that needs to merge is https://review.openstack.org/#/c/189500/15:39
carl_baldwinI need to decide if the RPC version should really be bumped for this.15:39
carl_baldwinPart of me wants to not bump it because either server or agent side will still work if the other side gets upgraded.  It almost feels like bumping the version number of RPC will cause more disruption.15:40
carl_baldwinhaleyb: Any thoughts here?15:40
* haleyb wakes up15:40
haleybi am thinking gary is right15:42
carl_baldwinOther than that, there is a neutron client patch that should be merging now (has +A) but is not.  I'll check in to that.15:42
carl_baldwinAnd, I need to get the L3 agent patches in to a devstack to pull them back together.15:43
carl_baldwinThanks to xiaohhui for a lot of help here.15:43
*** vikram_ has quit IRC15:44
xiaohhuinp:) carl15:44
carl_baldwinhaleyb: Could you note your position on the review?15:46
carl_baldwinThat is all I have for address scopes.  I hope to get these patches in to devstack early next week and get them in to shape.15:46
haleybwill do15:46
carl_baldwin#topic Open Discussion15:46
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:46
carl_baldwinAny other topics that we should tackle?15:47
*** juno_zhu has quit IRC15:47
mlavalledoes any one know if the registration for talks at Austin summit has opened?15:47
haleybi hope not :)15:48
carl_baldwinI'm pretty sure it hasn't opened.15:48
carl_baldwinWell, here's 10 minutes back.  Don't spend it all in one place.  :)15:50
carl_baldwin#endmeeting15:50
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"15:50
openstackMeeting ended Thu Dec 17 15:50:49 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-12-17-15.00.html15:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-12-17-15.00.txt15:50
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-12-17-15.00.log.html15:50
*** johnbelamaric has left #openstack-meeting-315:50
mlavallehave a nice day guys!15:51
*** pc_m has left #openstack-meeting-315:51
*** gouthamr_ has joined #openstack-meeting-315:52
carl_baldwinmlavalle: you too!15:52
yamamotobye15:53
*** cdent has joined #openstack-meeting-315:53
*** david-lyle_ has joined #openstack-meeting-315:55
*** belmoreira has joined #openstack-meeting-315:56
*** dwalleck has joined #openstack-meeting-315:56
*** david-lyle_ has quit IRC15:57
*** vmahe has quit IRC15:57
*** david-lyle has quit IRC15:59
*** ChuckC has quit IRC15:59
etoews#startmeeting api wg16:00
openstackMeeting started Thu Dec 17 16:00:07 2015 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
elmikohi16:00
etoewsgood day16:00
gouthamr_hello!16:00
cdenthellos16:00
*** john-davidge has joined #openstack-meeting-316:00
annegentlehi16:00
*** ryansb has joined #openstack-meeting-316:01
*** mbound_ has quit IRC16:01
etoews#topic agenda16:01
*** openstack changes topic to "agenda (Meeting topic: api wg)"16:01
etoews#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:01
etoews#topic previous meeting action items16:01
ryansbhey folks16:01
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"16:01
etoews#link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-12-03-16.00.html16:01
elmikoi think i covered 2/3 of mine16:02
elmikoi'm working on a patch to propose for the developer site16:02
salv-orlandoaloha16:02
etoewsand i saw rosmaita created the patch for the version discovery guideline16:03
*** mbound_ has joined #openstack-meeting-316:03
elmikoyea, we've got i think 4 services in the current design for versions16:03
elmikoi'd like to get a few more in there for reference, but it's a start16:03
etoewslink?16:03
elmikoand i think we need to have something about microversions in that guideline16:03
elmiko#link https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Version_Responses16:04
*** jrist has joined #openstack-meeting-316:04
*** david-lyle has joined #openstack-meeting-316:05
*** jrist has quit IRC16:05
etoewsnice16:05
*** jrist has joined #openstack-meeting-316:05
elmikoit's a start16:06
*** lizk_ has quit IRC16:06
*** davidsha has quit IRC16:06
* gouthamr_ makes a note to Add Manila's versions api response to that wiki16:06
elmikoooh, thanks gouthamr_ !16:06
etoewsthanks gouthamr_16:06
gouthamr_:)16:07
etoewsanyone else want to volunteer adding the version api response to that page?16:07
etoews(for the project they usually work on)16:07
*** vishwana_ has joined #openstack-meeting-316:07
cdentI'll add for ceilo, gnocchi, aodh16:09
cdent(even though I'm not quite usually working on them anymore)16:09
*** vishwanathj has quit IRC16:09
etoews#action cdent to add version api response for ceilo, gnocchi, aodh to https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Version_Responses16:10
cdentthanks16:10
etoewsthanks cdent !16:10
elmikothanks cdent =)16:10
*** vgridnev has joined #openstack-meeting-316:10
etoewsryansb: are you still working on heat mostly? (nudge nudge)16:10
ryansbetoews: zaqar as well16:10
etoewscare to add to that page?16:11
*** yamahata has joined #openstack-meeting-316:11
ryansbmost of my upstream is zaqar atm, but I expect heat to broaden its share in the future16:11
*** wojdev has quit IRC16:11
ryansbyeah sure16:11
ryansbI'm not sure what heat does, I know zaqar presents a pretty good version schema16:12
*** ihrachys has quit IRC16:12
etoews #action ryansb to add version api response for heat, zaqar to https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Version_Responses16:12
etoewsthanks16:12
elmikoyay, thanks ryansb !16:12
* ryansb adds to todo list16:13
*** hdaniel has quit IRC16:13
ryansbI'm going to be out Dec 21-Jan 1, btw, but I'll try and get it done before holiday16:13
*** emilyw has joined #openstack-meeting-316:13
etoewsany topics anyone would like to discuss in particular?16:13
elmikoi have a quick one16:14
etoewsshoot16:14
*** JeanBriceCombebi has quit IRC16:14
*** stephen-ma has quit IRC16:14
elmikocool, so the OpenStack Security Project (OSSP) is doing outreach to all the project teams16:14
*** mlavalle has left #openstack-meeting-316:14
elmikoand i wanted to bring it up with this group16:15
etoews#topic ossp16:15
*** openstack changes topic to "ossp (Meeting topic: api wg)"16:15
elmikothe main security stuff is at https://security.openstack.org/16:15
elmikothere are some cool api fuzzing efforts that have been going on recently16:15
elmikowhich may be a some interest to this gourp16:15
annegentlewhat's api fuzzing?16:16
* annegentle honestly hasn't heard of it16:16
elmikoapi fuzzing is an operation whereby an application will send bad, bogus, or random string to a server's endpoints16:16
elmikothis is in an attempt to find vulnerabilities or errors in the server16:16
annegentleah, okay16:17
elmikothere have been a few examples already of fuzzing finding bugs in neutron, for example16:17
*** tmazur has quit IRC16:17
etoewsannegentle: akin to system call fuzzing like http://codemonkey.org.uk/projects/trinity/16:17
elmikoso, the OSSP has a project called Syntribos which is a fuzzer16:17
cdenthow is that pronounced? I have to kind of read through it without hearing it...16:18
*** tellesnobrega is now known as tellesnobrega_af16:18
elmikoi think, sin tri bos16:18
elmikolong o on bos16:18
annegentletry or tree?16:19
elmikotree16:19
elmikosin-tree-bose16:19
ryansbdon't worry - 99% of the time you'll only need to say it on the ML ;)16:19
elmikotrue16:19
cdent:)16:20
elmikoanyway, i just wanted to help raise awareness about the project and if we might have cross-over into security stuff, they are a resource we can go to.16:20
elmiko#link https://security.openstack.org/16:21
etoewselmiko: do you have a link to the project?16:21
elmiko#link https://wiki.openstack.org/wiki/Security16:21
elmikosure, 1 sec16:21
etoewsthe api fuzzer in particular16:21
elmiko#link https://github.com/openstack/syntribos16:21
elmiko#link https://github.com/redhat-cip/restfuzz16:21
*** belmoreira has quit IRC16:22
elmikothat is another fuzzer which has been discussed as well16:22
* etoews plans to read through https://security.openstack.org/#secure-development-guidelines16:22
annegentlenice16:23
cdenttristan noodled briefly about trying to use gabbi for restfuzz but I think he eventually decided it wasn't really going to work16:23
*** numans has quit IRC16:23
cdentbut we talked about revisiting that at some point, as there are plenty of ways to make gabbi do things other than static yaml16:23
elmikoyea, i had brought up gabbi in the early days of the OSSP talking about fuzzing16:23
*** jmckind_ has joined #openstack-meeting-316:24
cdentDid I ever link the hypothesis + gabbi blog posting here?16:24
elmikoin the end, the fuzz tests need more dynamism than gabbi had at the time16:24
elmikocdent: i don't think so16:24
cdenthttp://wildfish.com/blog/2015/10/01/using-gabbi-and-hypothesis-test-django-apis/16:24
elmikoneat, thanks!16:25
*** mbound_ has quit IRC16:25
cdenthypothesis is something we should be using all over openstack16:25
*** mbound_ has joined #openstack-meeting-316:25
elmikoi'm not familiar with it16:25
*** yamamoto has quit IRC16:26
*** matrohon has quit IRC16:26
*** jmckind has quit IRC16:26
elmikosounds cool from the blog post16:27
etoewsthanks for highlighting that elmiko16:27
elmikonp, thanks =)16:27
etoews#topic guidelines dashboard16:28
*** openstack changes topic to "guidelines dashboard (Meeting topic: api wg)"16:28
etoews#link http://ghostcloud.net/openstack_gerrit_dashboards/dashboard_api-wg.html16:28
elmikowould be cool if those dashboards had a direct link to just run them16:28
etoewsyes it would16:29
*** bpokorny has joined #openstack-meeting-316:29
elmiko#link https://review.openstack.org/#/c/208264/16:29
elmikowill that one ever get merged?16:29
*** Swami_ has joined #openstack-meeting-316:30
elmikoi guess it all flows up to this one #link https://review.openstack.org/#/c/181393/16:30
* cdent nods16:31
etoewshow's the Service Catalog standardization effort going annegentle ?16:31
*** alexpilotti has quit IRC16:32
annegentleetoews: getting there16:33
*** alexpilotti has joined #openstack-meeting-316:33
annegentle#link https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Service_Catalog#Project_IDs16:33
annegentlelatest effort ^^16:33
annegentlefiguring out which projects have project_id or tenant_id in the catalog endpoint entry16:34
annegentleand, updated the spec itself this week16:34
annegentle#link https://review.openstack.org/#/c/181393/16:34
annegentlethat's all I have this week16:35
etoewswow. that's a lot of work.16:35
annegentleetoews: heh no joke16:35
elmikoannegentle: quick question, how did you get all the private cloud catalog data?16:35
*** zehicle has joined #openstack-meeting-316:36
annegentleelmiko: emailed people and they sent them to me16:36
annegentleelmiko: I have a bunch of contacts hahaha16:36
elmikoneat, very nice on the current design page too16:36
etoewsannegentle: bonne chance16:36
annegentlethanks, getting there16:36
etoewsis there anything we can do to help the microversion guidelines along?16:36
elmikoi *think* it's still waiting for an update16:37
*** tellesnobrega_af is now known as tellesnobrega16:37
elmikohmm, looks like it just needs more reviews now16:38
*** alexpilotti has quit IRC16:38
cdentit's in my queue (with lots of other stuff :( )16:40
etoewsi hear ya16:40
elmiko+116:40
etoewsshould i add all of the CPLs to the microversion guidelines?16:41
etoewsget more eyes on them...16:42
*** dwalleck has quit IRC16:42
annegentlemight work16:42
elmikoi dunno, might be best to at least get a pass by the wg for consistency then send it up16:42
-openstackstatus- NOTICE: Zuul is moving in very slow motion since roughly 13:30 UTC; the Infra team is investigating.16:42
*** ujuc_ has quit IRC16:42
elmikoalthough, it is on set 4...16:43
annegentlethis time of year, who knows16:44
elmikogood point16:44
cdentNext two weeks not a lot gonna happen...16:44
*** dwalleck has joined #openstack-meeting-316:45
elmikoetoews: looking at it again, i have no objection to adding the CPLs16:46
etoewsit would nice to unstick this one https://review.openstack.org/#/c/196918/16:47
elmiko+116:47
elmikoi think it's all bundled up with the service catalog stuff though16:47
cdentyes16:47
etoewswe need to find a way forward without depending so much on service catalog standardization16:48
etoewsthat's just going to take a really long time16:48
cdentthe conceptual stuff should resolve relatively soon16:49
etoewssigh16:49
elmikoetoews: agreed, but we got bogged down in the whole service name vs project name stuff16:50
etoewsproject names are silly. period.16:50
etoews:)16:50
elmikoqotd, imo ;)16:50
etoewsis there any point in adding CPLs to anything right now? seems extremely unlikely anything is really going to happen over the next 2 week.16:51
elmikoprobably not16:51
etoewshow about https://review.openstack.org/#/c/190743/ ?16:52
*** jschwarz has left #openstack-meeting-316:52
*** JeanBriceCombebi has joined #openstack-meeting-316:52
elmikoprobably good for freeze material16:52
*** wojdev has joined #openstack-meeting-316:52
etoewsit went through some substantial discussion since the last freeze so should be frozen again.16:53
elmikoagreed16:53
etoewsbut again we hit the timing of it16:53
*** annegentle has quit IRC16:53
elmikoshould we just push on all freezes until after break?16:53
etoewsfreeze tomorrow and merge on christmas day! :D16:53
elmiko(also, should we cancel the next 2 meetings?)16:53
elmikohaha, nice16:54
etoewsyes to cancelling meetings16:54
cdentyes cancel16:54
cdentBefore we end the meeting I've got an open topic to raise, please let me know when we've reached that point.16:54
*** huichun has quit IRC16:54
etoewsokay. let's push off freezes and review pestering until the new year.16:54
etoewsshoot cdent16:54
elmiko+116:54
cdentI think we've covered this ground before but it's just come back up again in telemetry: what do with url elements that contain '/'?16:55
cdentWeb servers will often not preserve %2F16:55
*** zehicle has quit IRC16:56
etoewsummmm...not have '/' as url elements?16:56
elmikoi'm not sure on the proper handling for that16:56
etoewsthat just seems like you're asking for trouble16:56
elmikoyea16:56
etoewsall up and down the stack16:56
cdentin this case it is ids being used elsewhere in openstack16:56
cdentand yeah, everyone knows it is borked16:57
cdentbut they're still out there16:57
etoewsthat's epically bad16:57
cdentwhat I'm wondering is: are there existing solutions for the web server problem with dealing with %2F?16:57
elmikois it feasable to migrate away from those urls?16:57
cdentIn the past I've done this: https://github.com/tiddlyweb/tiddlyweb/blob/master/tiddlyweb/web/serve.py#L9516:58
cdentIt is probably possible to migrate, but it will be slow, deprecation, laziness etc16:58
* elmiko nods16:58
elmikoi'm kinda at a loss on this one, i don't know any solutions off the top of my head16:59
*** banix has joined #openstack-meeting-316:59
etoewsno ideas come to my mind. that's uncharted territory for me. i think i'm in shock a bit.16:59
*** ihrachys has joined #openstack-meeting-316:59
etoewselmiko++16:59
*** olaph has joined #openstack-meeting-316:59
*** mickeyspiegel has joined #openstack-meeting-316:59
*** annegentle has joined #openstack-meeting-317:00
etoewsthanks to everyone for a great year!!!17:00
cdentTo me it a fundamental flaw in web servers, with the precent set by apache a very long time ago.17:00
elmikomaybe something to research for next time17:00
etoews#endmeeting17:00
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"17:00
openstackMeeting ended Thu Dec 17 17:00:17 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
elmikoyou too etoews !17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-12-17-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-12-17-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-12-17-16.00.log.html17:00
docaedo#startmeeting app-catalog17:00
openstackMeeting started Thu Dec 17 17:00:43 2015 UTC and is due to finish in 60 minutes.  The chair is docaedo. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: app-catalog)"17:00
openstackThe meeting name has been set to 'app_catalog'17:00
docaedoTodays agenda can be found here:17:00
docaedo#link https://wiki.openstack.org/wiki/Meetings/app-catalog#Proposed_Agenda_for_December_17th.2C_2015_.281700_UTC.2917:00
docaedo#topic rollcall17:01
*** openstack changes topic to "rollcall (Meeting topic: app-catalog)"17:01
docaedoo/17:01
ativelkovo/17:01
olapho/17:01
docaedohey look at that, it's enough for a meeting :D17:01
*** cdent has left #openstack-meeting-317:01
*** ryansb has left #openstack-meeting-317:01
*** s3wong has joined #openstack-meeting-317:01
docaedo#topic Status updates17:02
*** openstack changes topic to "Status updates (Meeting topic: app-catalog)"17:02
*** JeanBriceCombebi has quit IRC17:02
docaedoI've been working on dead link checker (and some related stuff)17:02
docaedoI'd like feedback on the "skip assets with active: false" review, I think it's good to go:17:02
docaedo#link https://review.openstack.org/#/c/257663/17:02
docaedoThis will be used with the dead link checker (to be discussed later in this meeting)17:02
docaedoBut happy to discuss the method (thanks kfox1111 for pointing out it should be handled in python rather than JS!)17:02
docaedoI want to start using this because the dead-link checker is ready (details later), and we could have stale links being automatically discovered in a week.17:02
*** gouthamr_ has left #openstack-meeting-317:02
*** hdaniel has joined #openstack-meeting-317:03
*** john-davidge has quit IRC17:03
docaedoany other status updates? ativelkov maybe there's something new re: glare?17:04
ativelkovYeah, there are some updates on glare17:04
ativelkovSo, the summit's decision on separating the process for Glance and Glare is getting implemented17:04
ativelkovThe spec has been approved and the actual patches are ready and on review right now17:05
ativelkovThis will allow to run glare without a burden of having the rest of Glance deployed, which should be nice for app-catalog17:05
docaedonice! I've been following, would join the weekly meeting but it happens at a time I can't make :(17:05
docaedoativelkov: absolutely, I'm excited about it!17:05
ativelkovAlso, we are working towards API stabilization (addressing API-WG and DefCore concerns ets). The spec is on review17:06
ativelkovAlso, I've got a design for the pluggable DB backends (The feature we discussed with kfox1111 on the summit). I'll submit the spec in a day or two17:06
ativelkovAnd last but not least: we are planning a video call in the nearest days to discuss glare roadmap in voice17:07
ativelkovAll are welcome to join17:07
docaedoplease share the details on the ML and maybe on #openstack-app-catalog because I'd like to join and others might as well17:08
ativelkovWe just need to sync with flaper87 and nikhil to find out the timeslot convienient for all17:08
ativelkovYeah, sure.17:08
docaedothx17:08
ativelkovThe problem is that the holiday season is approaching and it may be hard to find a slot equally convinient for all. But we'll do our best17:08
docaedoyeah, we are rapidly running out of time to get things done in 2015 :)17:09
ativelkovsome links:17:09
ativelkov#link https://review.openstack.org/#/c/254710/  - the api refactoring spec17:09
ativelkov#link https://review.openstack.org/#/q/topic:bp/move-v3-to-glare - patches to move the glare api to separate process / keystone endpoint17:10
ativelkovFeel free to review and leave comments if you have time :)17:11
docaedoativelkov: thanks, I will17:11
docaedoI'll hold for one minute to see if there are any other status updates before moving on...17:12
docaedo#topic Dead link check script17:13
*** openstack changes topic to "Dead link check script (Meeting topic: app-catalog)"17:13
docaedoThis script goes through the assets.yaml file, grabs the URLs and does a header request (with redirect follow).17:13
docaedoIf it doesn't get a 200 response, it adds "active: false" to the attributes section.17:13
docaedo#link http://paste.openstack.org/show/48215217:13
docaedoThis is the output from the script, which found two dead links!17:14
docaedo#link http://paste.openstack.org/show/48215117:14
*** banix has quit IRC17:14
docaedoYou'll note one difference from the active assets.yaml we have - the "---" at the top is gone, as that's no longer necessary due to there being only "assets" in the yaml, and no other record types.17:14
docaedoIt is adapted from the project normalizer script infra uses. It's coupled with a shell script that clones the repo, and if the check_catalog.py script found any dead links, it submits a review to update assets.yaml.17:14
docaedoI'll propose this in app-catalog/tools and will coordinate with infra to sort out what user actually submits the PR (probably catalog-bot). With any luck we could have automated dead-url checks live in less than a week!17:14
olaphsweet17:14
*** banix has joined #openstack-meeting-317:14
docaedoI want to use this same script to add a mechanism for keeping a frequently changing asset up to date. The use case would be something like the Debian weekly testing image17:14
docaedo#link http://cdimage.debian.org/cdimage/openstack/testing/17:15
docaedoThe asset entry would include something like "desired-hash-url: http://cdimage.debian.org/cdimage/openstack/testing/MD5SUMS", and the script could see if the current hash entry in assets.yaml matches.17:15
docaedoIf it's different, it updates the entry with the hash and an "updated: <date>" entry in attributes section.17:15
docaedoThe tricky part will be making this abstract enough to work for more than just debian weekly.17:15
docaedoWhat do you think?17:15
*** tmckay has quit IRC17:15
*** salv-orl_ has joined #openstack-meeting-317:15
olaphmakes sense to me...17:16
ativelkovWell, this allows to ensure that the image is not modified on its way, yes17:16
docaedoativelkov: well yes, but more than that, will allow us to put some frequently changing things in the catalog without having to manually update them all the time17:17
ativelkovYes, I understand that. But I believe we should provide some notice to the users17:17
docaedoativelkov: when we have glare for the backend, this will probably change, because it will become reasonable for someone to just use the API to authenticate and update a record they own17:17
ativelkovSomething like "The asset has been changed by its owner since the last time we've checked that"17:18
*** salv-orlando has quit IRC17:18
docaedooh I was actually thinking the entry in the catalog would just get updated to include the new/latest hash when it changes, along with an entry for updated date17:18
docaedothat way any time someone comes back to find the latest debian (or coreos, or any of the others that frequently change images)17:19
docaedothey see what the latest is, along with a verifiable hash, and the date the record was updated17:19
docaedovs. right now for instance, we just point to the qcow entry and don't list the hash17:20
ativelkovAh yeah, so we need two timestamps then17:20
ativelkovOr may be even three17:20
ativelkovdate when the entry is added to catalog, the date of the last update and the date of the last (manual) verification of the asset17:20
ativelkovso the clients may choose not to download unverified assets17:21
docaedoI would agree with added and updated, but not last verified (because the intention is that this will be automatically verified every day, triggering a review if anything changes - would not be useful to update every record with that date every day)17:21
docaedoKeep in mind too - this is a stop-gap thing until we implement glare backend, when many of these mechanisms will change17:22
*** yamahata has quit IRC17:22
ativelkovyeah, you are right, I think17:22
ativelkovAnd manual verification does not scale for sure17:22
docaedoMy intention with this is to take the least-effort path to keeping assets "fresh" until we have a legitimate backend in place :)17:22
*** bradjones has quit IRC17:23
docaedoI am done with dead-link checker except for coordination with infra, and can probably sort out the "hash checking" stuff before end of year17:23
docaedothen next up probably work on some UI refreshes I have in mind while coordinating with you and others on glare implementation17:23
*** bradjones has joined #openstack-meeting-317:24
*** bradjones has quit IRC17:24
*** bradjones has joined #openstack-meeting-317:24
ativelkovcool17:24
docaedoAs for manual in my short-term plan, the only manual step will be reviewing what the bot submits when it finds a change. That's low effort for me or others, but also provides a nice safety valve in case the bot goes crazy we can just ignore what it submits17:24
ativelkovyeah, that sounds the right thing to have17:25
*** mickeyspiegel has quit IRC17:25
docaedosweet, agreement all around :)17:25
docaedoas for the meeting agenda, I left "discuss glare outline" up, but I'm good with the draft and had it there in case kfox1111 and kzaitsev_ws were here (they might have had some points of debate)17:26
*** jlanoux has quit IRC17:27
docaedoSo since they're not here, unless olaph or ativelkov want to chat about it?17:27
docaedo#link https://etherpad.openstack.org/p/app-cat-glare17:27
olaphI'm good17:28
ativelkovI did review kzaitsev_ws's etherpad, it was quite aligned with what we are doing in glare17:28
docaedoyep, I like the plan there too17:28
docaedoonce again - agreement all around :)17:28
docaedoso moving on...17:29
docaedo#topic Open discussion17:29
*** openstack changes topic to "Open discussion (Meeting topic: app-catalog)"17:29
docaedoAnyone have any open discussion points to openly discuss?17:29
* docaedo stops typing for 1-2 minutes17:30
kfox1111hi17:30
docaedooh hey!17:30
kfox1111I added a few things to the etherpad, but still need to find a few minutes to finish reading. theres quite a bit in there.17:31
*** sanghai has quit IRC17:31
*** mbound_ has quit IRC17:32
docaedokfox1111: are you implying Community App Catalog is not your only full-time job? What, are you trying to run a huge cloud or something too??? ;)17:32
kfox1111;)17:32
docaedoConsidering the scale of the effort, I'd say we leave it on the agenda and continue to discuss in January17:33
kfox1111+117:33
docaedo(and of course, on #openstack-app-catalog between now and then)17:33
ativelkovAgree.17:34
*** pavel_bondar_ has quit IRC17:34
*** tmckay has joined #openstack-meeting-317:34
*** john-davidge has joined #openstack-meeting-317:34
docaedook - anything else for open discussion? kfox1111, anything you wanted to touch on that we talked about earlier? Much scrollback for you I think...17:35
*** jmckind_ has quit IRC17:36
kfox1111things look good to me.17:38
docaedosounds like we're done for today then...17:38
kfox1111yeah, keeping the sums up to date is seperate from prompting users there is updated stuff.17:39
kfox1111hopefully versioning plays in somehow there too.17:39
docaedoin the short term, I don't see any reasonable way to do versions in a manually-updated assets.yaml file, but will HAVE to have versions with glare17:40
docaedoI should say .. versions could be done17:41
kfox1111I'm curious if we can do some kind of web scraper plugin thingy for a few different things.17:41
kfox1111like, ubuntu's cloud images page.17:41
kfox1111they update them constantly, and have a lot available. being able to run a cron job that generates bits of assets.yaml with all the versions would be very nice.17:41
kfox1111I think fedora does something similar.17:42
kfox1111something to think about.17:42
docaedodefinitely worth thinking about17:42
kfox1111(another thing unioning the yaml could help with)17:43
kfox1111gtg. talk to you later.17:43
docaedook thanks for dropping by :)17:43
docaedoI think we're done - thanks everyone for joining!17:43
docaedo#endmeeting17:44
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"17:44
openstackMeeting ended Thu Dec 17 17:44:16 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/app_catalog/2015/app_catalog.2015-12-17-17.00.html17:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/app_catalog/2015/app_catalog.2015-12-17-17.00.txt17:44
openstackLog:            http://eavesdrop.openstack.org/meetings/app_catalog/2015/app_catalog.2015-12-17-17.00.log.html17:44
*** olaph has left #openstack-meeting-317:44
*** s3wong has quit IRC17:45
*** alexpilotti has joined #openstack-meeting-317:46
*** ivar-lazzaro has joined #openstack-meeting-317:47
*** iyamahat has joined #openstack-meeting-317:48
*** itxaka has quit IRC17:48
*** yamahata has joined #openstack-meeting-317:48
*** alexpilotti has quit IRC17:51
*** e0ne has quit IRC17:53
*** SumitNaiksatam has joined #openstack-meeting-317:59
SumitNaiksatamivar-lazzaro: hi18:01
SumitNaiksatamigordcard_: hi18:01
ivar-lazzarohi18:01
SumitNaiksatamseems like previous meeting is still in this channel18:01
*** songole has joined #openstack-meeting-318:02
SumitNaiksatami see the meeting topic as horizon, do you guys see that as well?18:02
songoleYes SumitNaiksatam18:02
SumitNaiksatamsongole: hi18:02
* david-lyle wonders if his #endmeeting didn't register18:02
david-lyle#endmeeting18:02
SumitNaiksatamdavid-lyle: hi18:03
david-lyleI think the bot may just be acting up18:03
SumitNaiksatamdavid-lyle: ah ok18:03
david-lyleThere was a meeting that ended 15 minutes ago, I see in the backlog18:03
*** vks_ has joined #openstack-meeting-318:03
david-lylehorizon meeting was yesterday18:04
songolehi18:04
*** tbachman has joined #openstack-meeting-318:05
SumitNaiksatamdavid-lyle: oh :-)18:05
SumitNaiksatamsongole: tbachman: hi18:05
david-lyleI would just start a new meeting18:05
SumitNaiksatamvks_: hi18:05
tbachmanSumitNaiksatam: hi!18:05
vks_hi18:05
SumitNaiksatamjust trying to get the bot to change status for this meeting, so that our meeting can get logged18:05
david-lyleseveral meetings since horizon, all logged, I'd ignore status and roll18:06
SumitNaiksatamdavid-lyle: okay18:07
SumitNaiksatam#startmeeting networking_policy18:07
openstackMeeting started Thu Dec 17 18:07:51 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:07
*** openstack changes topic to " (Meeting topic: networking_policy)"18:07
openstackThe meeting name has been set to 'networking_policy'18:07
SumitNaiksatamdavid-lyle: worked :-)18:08
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#Dec_17th_201518:08
SumitNaiksatam#topic bugs18:08
*** openstack changes topic to "bugs (Meeting topic: networking_policy)"18:08
SumitNaiksatamis magesh around?18:08
SumitNaiksatamwanted to check if any new high priority bugs beyond the ones we discussed last week and are pending18:09
songoleSumitNaiksatam: I don't see him online18:10
SumitNaiksatamvks_: anything you saw recently that needs immediate attention?18:10
SumitNaiksatamsongole: okay18:10
*** galstrom_zzz is now known as galstrom18:10
SumitNaiksatamspecifically asking vks_ and magesh since they are doing a lot of testing18:10
vks_SumitNaiksatam, there is a limit of 4096 byte for ServicechainNode data18:10
*** rkukura has joined #openstack-meeting-318:10
rkukurahi - sorry I’m late18:11
SumitNaiksatamivar-lazzaro: did you get any more feedback on #link https://bugs.launchpad.net/group-based-policy/+bug/1521545 ?18:11
openstackLaunchpad bug 1521545 in Group Based Policy "If service chain delete fails then the PTG can never be cleaned up" [Undecided,Incomplete] - Assigned to Ivar Lazzaro (mmaleckk)18:11
SumitNaiksatamrkukura: just in time :-)18:11
ivar-lazzaroSumitNaiksatam: nope, was waiting for the logs18:11
SumitNaiksatamivar-lazzaro: okay, will try to ping magesh18:11
SumitNaiksatamvks_: do you know if there is any more info available on #link https://bugs.launchpad.net/group-based-policy/+bug/1521545 ?18:11
*** banix has quit IRC18:12
vks_it can be easily simulated18:12
*** ihrachys has quit IRC18:12
*** hdaniel has quit IRC18:12
vks_just restart neutron server in middle of delete18:12
SumitNaiksatamvks_: okay, can you add some info to the bug in that case?18:13
*** ihrachys has joined #openstack-meeting-318:13
*** banix has joined #openstack-meeting-318:13
SumitNaiksatamvks_: and perhaps it might also help to give ivar-lazzaro quick access to your system when you are able to reproduce this18:13
vks_SumitNaiksatam, yeah but see the relevant log is there already, apart from that don't see any oyher logs18:13
SumitNaiksatamvks_: we need to check little bit prior to that particular log18:14
SumitNaiksatamvks_: we also discussed #link https://bugs.launchpad.net/group-based-policy/+bug/1523733 offline18:14
openstackLaunchpad bug 1523733 in Group Based Policy "GBP PT delete allows to delete PT , even though the PT is bound to VM" [Undecided,New]18:14
*** klkumar has quit IRC18:14
SumitNaiksatamvks_: i was not able to reproduce the PT getting deleted when the port is deleted, so i need to check that on your setup18:14
vks_SumitNaiksatam, ok18:15
SumitNaiksatamany other burning issues?18:15
SumitNaiksatamokay lets move to the desing related discussions18:15
SumitNaiksatam#topic Service chain node config attr size18:15
*** openstack changes topic to "Service chain node config attr size (Meeting topic: networking_policy)"18:15
SumitNaiksatamvks_: you brought this up18:15
vks_SumitNaiksatam, yeah18:15
SumitNaiksatamso currently we model the congfig column is the DB as a string of length 409618:16
SumitNaiksatamvks_: however you are running into configs much larger than that18:16
vks_SumitNaiksatam, yes18:16
SumitNaiksatamso the question is how large do we go, or do we need to look at it in a different way18:17
vks_SumitNaiksatam, Essentially in case of firewall especially , where than can be n number of rules18:17
SumitNaiksatamvks_: right18:17
vks_we will have problem18:17
SumitNaiksatamand n is difficult to predict how large it can be18:17
*** annegentle has quit IRC18:17
*** alexpilotti has joined #openstack-meeting-318:17
vks_SumitNaiksatam, thats true18:18
SumitNaiksatamrkukura: ivar-lazzaro songole: any thoughts on this?18:18
*** banix has quit IRC18:18
ivar-lazzaroSumitNaiksatam: what is the proposed solution?18:19
SumitNaiksatamivar-lazzaro: currently there is only a requirement that the size needs to be increased18:19
SumitNaiksatamhowever no clear proposal18:19
SumitNaiksatamwe can increase to the max limit18:19
rkukuraIs this config attr really meant to be used in place of a proper REST service API?18:19
SumitNaiksatambut that might not be enough18:20
SumitNaiksatamrkukura: yes18:20
SumitNaiksatamrkukura: because this is service-specific config which GBP does not care about18:20
ivar-lazzaroSumitNaiksatam: this looks like something that would require a separate config repository18:21
SumitNaiksatamivar-lazzaro: something like that would be ideal where we just provide a reference18:21
ivar-lazzaroSumitNaiksatam: that can't be the GBP Controller itself, since we also need to distribute that config around for high availability18:21
SumitNaiksatamivar-lazzaro: rather than the entire config itself18:21
ivar-lazzaroSumitNaiksatam: which means that we should use something like Swift18:22
ivar-lazzaroSumitNaiksatam: to store these configurations18:22
*** alexpilotti has quit IRC18:22
SumitNaiksatamivar-lazzaro: we can be agnostic to where its stored, just enough information in the config attribute to be able to look it up18:22
ivar-lazzaroI believe you would just use S3 if you were in amazon18:22
rkukuraI think sqlalchemy has a Text type that is unbounded18:22
ivar-lazzaroSumitNaiksatam: right, I was thinking about the reference implementation though :)18:23
*** neelashah has quit IRC18:23
SumitNaiksatamivar-lazzaro: yeah that can contract can be between the user and the driver which knows where to pull it from18:23
ivar-lazzarorkukura: do we really want to use the database for this kind of things? You can't even really write a proper query in that field18:23
SumitNaiksatamrkukura: okay18:23
rkukuraMaybe the config attr isn’t that useful to query18:24
SumitNaiksatamivar-lazzaro: i dont think we perform any DB queries on that particular column18:24
SumitNaiksatamrkukura: right18:24
ivar-lazzaroNo it isn't, that's just a blob18:24
ivar-lazzarothat's why I believe it should be stored in the proper service18:24
ivar-lazzaroit's not useful from a relational point of view18:25
ivar-lazzaroFor example18:25
ivar-lazzaroif you query the DB and retrieve 20 MB worth of config files (just saying)(18:25
ivar-lazzaroyou keep the lock for too long potentially18:25
SumitNaiksatamivar-lazzaro: that is correct18:25
SumitNaiksatamso how about we do this -18:25
SumitNaiksatamwe explore changing this column to a text field with the recommendation that you actually dont store the config itself in that field18:26
SumitNaiksatamafter that if someone wants to shoot themselves in the foot then its their call18:26
ivar-lazzaroSumitNaiksatam: someone who? The Node Driver?18:27
ivar-lazzaroOr the user?18:27
songolewhat is text field? You can store anything of any size?18:27
ivar-lazzarowe shouldn't give the user too much ability to shoot himself in the foot :)18:27
SumitNaiksatamivar-lazzaro: the user is going to be go by the recommendation of a particular node driver in this case18:27
SumitNaiksatamivar-lazzaro: so its the node-driver that i am referring to18:28
ivar-lazzaroIf we want to go this route18:28
SumitNaiksatamsongole: the “text” field is as referenced by rkukura18:28
ivar-lazzaroI believe we should have a text field, and a reference implementation that uses it properly (without recomandations)18:28
rkukurahttp://docs.sqlalchemy.org/en/latest/core/type_basics.html#sqlalchemy.types.Text18:29
ivar-lazzarothen if a vendor implementation wants people to store config there, so be it18:29
SumitNaiksatamrkukura: thanks18:29
ivar-lazzarobut the reference should always enforce the best practice18:29
SumitNaiksatamivar-lazzaro: i dont think we have a “reference” implementation18:29
*** jmckind has joined #openstack-meeting-318:29
SumitNaiksatamivar-lazzaro: we have had this discussion before on the reviews as well18:30
ivar-lazzaroSumitNaiksatam: then we should just enforce the best practice :D18:30
rkukuraThis is probably a dumb question that I should know the answer to, but what would need to happen to allow use of the neutron *aaS REST APIs rather than this config attr?18:31
ivar-lazzarorkukura: I guess that would go through a heat template18:31
SumitNaiksatamrkukura: we dont assume that its always a *aas service18:31
rkukuraI understand we don’t assume that, but if it is, or is something close enough, is an API useful in the context for GBP service chaining?18:32
rkukuraOr is the fact that the API’s are per-instance the reason a heat template is more appropriate?18:33
ivar-lazzarorkukura: how will the API look like? The idea of the config file is to guarantee vendor differentiation18:33
*** dwalleck has quit IRC18:33
ivar-lazzarorkukura: which can't happen if we normalize the operations18:33
*** wojdev has quit IRC18:33
vks_ivar is right18:33
SumitNaiksatamrkukura: we would need to make the service chain layer service aware, which we dont want to18:33
*** dwalleck has joined #openstack-meeting-318:34
ivar-lazzarorkukura: in theory, the specific node driver should be able to read the configuration in a service specific manner18:34
vks_SumitNaiksatam, but there shud be a generic way to pass a template from any service vendor18:34
ivar-lazzarorkukura: so for instance, if you create a chain with a config blob that the node driver doesn't understand, it will reject the node creation and try on the next driver18:35
ivar-lazzaroA prerequisite for a Node Driver to accept to be scheduled for a node, is that it understands the configuration format18:35
SumitNaiksatamokay, so vks_ do you want to explore using this #link: http://docs.sqlalchemy.org/en/latest/core/type_basics.html#sqlalchemy.types.Text18:35
*** devananda has quit IRC18:36
*** neelashah has joined #openstack-meeting-318:36
SumitNaiksatamivar-lazzaro: btw, ivar-lazzaro i think you pretty much addressed your own point about “enforcement” in those two last comments ;-)18:36
vks_SumitNaiksatam, yeah sure18:36
rkukuraOK, I now understand the current GBP SC approach does not cater to service’s with APIs.18:36
SumitNaiksatamvks_: okay18:36
SumitNaiksatamrkukura: its agnostic of that18:36
SumitNaiksatamrkukura: i dont think “does not cater to” would be the right characterization18:37
SumitNaiksatamok we have a couple of more topics to discuss at least18:37
rkukuraWould it make sense for this config attribute to not be queries and returned by default?18:37
ivar-lazzarojust came across http://arxiv.org/ftp/cs/papers/0701/0701168.pdf18:38
songolerkukura: we need to be able to display config as stored18:38
ivar-lazzaroshould give a look at it as well18:38
*** s3wong has joined #openstack-meeting-318:39
ivar-lazzaroalthough it's a pretty old paper18:39
SumitNaiksatamivar-lazzaro: the debate around blob is not new18:39
SumitNaiksatamivar-lazzaro: its good to use in certain places and its not in certain others18:39
rkukuraFrom the abstract of ivar-lazzaro’s link, it seems <=256KB belongs in the DB18:40
*** sambetts is now known as sambetts-afk18:41
ivar-lazzarowe only allow 4k right now18:41
SumitNaiksatamrkukura:  but different DB implementations wil tune this in a different way18:41
ivar-lazzarobut I'm not sure there's actually a limit18:41
SumitNaiksatamrkukura: its proabably they size of the records they can read in a single shot18:41
SumitNaiksatamversus multiple reads18:42
*** vhoward has joined #openstack-meeting-318:42
SumitNaiksatamokay, so vks_ and perhaps magesh can take the action item to explore using the text field as we previously discussed18:42
SumitNaiksatammoving on18:43
vks_SumitNaiksatam, OK18:43
SumitNaiksatam#topic Port extra attribute extension18:43
*** openstack changes topic to "Port extra attribute extension (Meeting topic: networking_policy)"18:43
SumitNaiksatam#link https://review.openstack.org/#/c/256880/18:43
*** dwalleck has quit IRC18:43
SumitNaiksatamivar-lazzaro: i believe bob had a comment to at least cross refernce a bug for this18:44
SumitNaiksatambob -> rkukura18:44
ivar-lazzaroSumitNaiksatam: mmm I created a bp18:44
ivar-lazzaroapparently didn't set it in the commit message though18:44
*** tellesnobrega is now known as tellesnobrega_af18:45
SumitNaiksatamivar-lazzaro: okay, but in that case was a spec posted?18:45
rkukuraI wasn’t too thrilled about adding a special write-only attribute to the REST API, but I think ivar-lazzaro has addressed that, right?18:45
ivar-lazzaroSumitNaiksatam: nope18:45
ivar-lazzaroSumitNaiksatam: the change is for internal API only18:46
*** e0ne has joined #openstack-meeting-318:46
ivar-lazzaroSumitNaiksatam: and no persistence18:46
SumitNaiksatamivar-lazzaro: i would recommend treating this as a bug in that case, because having a BP without a spec has no meaning18:46
ivar-lazzaroI can write a spec about this, but I feel it would take like 5 lines total or something18:46
rkukuraI bug seems sufficient to me18:46
ivar-lazzaroEven if the issue is explained in the BP itself?18:46
rkukuras/I/A/18:47
ivar-lazzarorkukura: yeah, the API is only internal now18:47
ivar-lazzarook I'll move the BP as a bug18:47
rkukuraivar-lazzaro: Is the policy.json change still needed?18:47
SumitNaiksatamivar-lazzaro: yes, launchpad BP is only for tracking purposes, specs are in gerrit as patches18:48
songoleivar-lazzaro: who is the intended user of this API?18:48
ivar-lazzarosongole: node drivers18:48
SumitNaiksatamsongole: its not an API change as of now18:48
*** bharathm has joined #openstack-meeting-318:48
songoleivar-lazzaro: ok18:48
ivar-lazzarorkukura: no, but we missed that entry anyways18:48
ivar-lazzarorkukura: I can remove that change18:48
SumitNaiksatamrkukura: did you get a chance to review the current version of the patch?18:49
ivar-lazzarois it possible to convert a BP into a bug?18:49
ivar-lazzarohttps://blueprints.launchpad.net/group-based-policy/+spec/port-extra-attributes18:49
rkukuraSumitNaiksatam: I have not, but will18:50
SumitNaiksatamivar-lazzaro: i will create the bug for you ;-)18:50
ivar-lazzaroSumitNaiksatam: I can do it, just didn't want to leave the BP around18:50
rkukuraSo this is a short-term fix that we need to backport to juno, etc?18:51
SumitNaiksatamivar-lazzaro: i think we can obsolete that18:51
SumitNaiksatamrkukura: yes18:51
ivar-lazzaroSumitNaiksatam: ok!18:51
*** piet has quit IRC18:51
SumitNaiksatamivar-lazzaro: thanks for the update, so seems like we are good to go with this once the bug is cross-referenced18:51
SumitNaiksatammoving on18:51
SumitNaiksatam#topic Propagating post-commit exceptions18:53
*** openstack changes topic to "Propagating post-commit exceptions (Meeting topic: networking_policy)"18:53
SumitNaiksatamthis is a discussion ivar-lazzaro and were having offline18:53
*** devananda has joined #openstack-meeting-318:53
SumitNaiksatamand i believe at some point we might discussed with rkukura as well18:53
SumitNaiksatamso we have this block of code:18:53
SumitNaiksatam#link https://github.com/openstack/group-based-policy/blob/master/gbpservice/neutron/services/grouppolicy/policy_driver_manager.py#L122-L12718:53
SumitNaiksatamwhich masks the exceptions thrown by the drivers18:53
SumitNaiksatamand for good reason18:54
SumitNaiksatamso as to abstract the driver technology specific details from the user18:54
SumitNaiksatamhowever, since we are mostly doing orchestration in our drivers as well, we are increasingly feeling the need to propagate these exceptions to the users18:55
SumitNaiksatamit seems like there is a lot more benefit to the end user seeing the real exceptions than from abstracting them18:56
SumitNaiksatamnot to mention that it greatly helps in debugging18:56
rkukuraWould it make sense to propagate a certain portion of the exception hierarchy, but mask the rest?18:56
SumitNaiksatamrkukura: i agree with that, if there is a deterministic way to do that18:56
*** jmckind has quit IRC18:57
rkukuraMaybe anything derived from GroupPolicyDriverError should get propogated, so drivers can subclass this if they want to return details to the user.18:58
SumitNaiksatamrkukura: okay18:58
rkukuraI haven’t thought that through, but just wanted to give an example of how it might work.18:58
SumitNaiksatamrkukura: right18:58
*** dwalleck has joined #openstack-meeting-318:58
SumitNaiksatamokay so there doesnt seem to be outright objection to doing this, which is good18:59
SumitNaiksatamso we can explore18:59
SumitNaiksatam#topic Open Discussion18:59
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:59
SumitNaiksatamjust a quick reminder we wont be meeting for the next couple of weeks18:59
SumitNaiksatamanything else that we might have missed?18:59
*** tellesnobrega_af is now known as tellesnobrega19:00
SumitNaiksatamokay then lets wrap up19:00
rkukuranot that I can think of19:00
SumitNaiksatamrkukura: oka19:00
SumitNaiksatamy19:00
SumitNaiksatambest wishes for the holidays and the new year to all!19:01
SumitNaiksatambye!19:01
rkukurathanks SumitNaiksatam!19:01
rkukurabye19:01
songolebye19:01
*** songole has left #openstack-meeting-319:01
SumitNaiksatam#endmeeting19:01
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"19:01
openstackMeeting ended Thu Dec 17 19:01:37 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-12-17-18.07.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-12-17-18.07.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-12-17-18.07.log.html19:01
*** rkukura has left #openstack-meeting-319:01
ivar-lazzarovye19:02
ivar-lazzarobye*19:02
*** ivar-lazzaro has quit IRC19:03
*** wojdev has joined #openstack-meeting-319:07
*** neelashah has quit IRC19:08
*** ihrachys has quit IRC19:09
*** vks_ has quit IRC19:10
*** tmckay has quit IRC19:10
*** tbachman has left #openstack-meeting-319:11
*** mickeyspiegel has joined #openstack-meeting-319:14
*** absubram has joined #openstack-meeting-319:15
*** safchain has quit IRC19:19
*** dslev has quit IRC19:22
*** dwalleck has quit IRC19:22
*** tmckay has joined #openstack-meeting-319:24
*** bharathm has quit IRC19:32
*** jmckind has joined #openstack-meeting-319:33
*** e0ne has quit IRC19:34
*** tmckay has left #openstack-meeting-319:36
*** wojdev has quit IRC19:36
*** dwalleck has joined #openstack-meeting-319:38
*** mickeyspiegel has quit IRC19:39
*** wojdev has joined #openstack-meeting-319:41
*** jed56 has quit IRC19:43
*** mfranc213 has quit IRC19:47
*** mfranc213 has joined #openstack-meeting-319:48
*** piet has joined #openstack-meeting-319:50
*** ivar-lazzaro has joined #openstack-meeting-319:53
*** banix has joined #openstack-meeting-319:54
*** FallenPegasus has joined #openstack-meeting-320:00
*** salv-orl_ has quit IRC20:01
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:01
*** mfranc213 has quit IRC20:03
*** dwalleck has quit IRC20:08
*** mfranc213 has joined #openstack-meeting-320:11
*** emilyw has quit IRC20:17
*** john-davidge has quit IRC20:18
*** emilyw has joined #openstack-meeting-320:24
*** markvoelker has quit IRC20:24
*** e0ne has joined #openstack-meeting-320:27
*** kzaitsev_mb has joined #openstack-meeting-320:30
*** matrohon has joined #openstack-meeting-320:30
*** dwalleck_ has joined #openstack-meeting-320:31
*** alexpilotti has joined #openstack-meeting-320:34
*** kzaitsev_mb has quit IRC20:36
*** emilyw has quit IRC20:37
*** emily_w has joined #openstack-meeting-320:37
*** kzaitsev_mb has joined #openstack-meeting-320:38
*** alexpilotti has quit IRC20:38
*** galstrom is now known as galstrom_zzz20:39
*** vgridnev has quit IRC20:40
*** john-davidge has joined #openstack-meeting-320:40
*** dwalleck_ has quit IRC20:40
*** Swami_ has quit IRC20:45
*** hdaniel has joined #openstack-meeting-320:46
*** mfranc213 has quit IRC20:47
*** dslevin has quit IRC20:48
*** vhoward has quit IRC20:52
*** mfranc213 has joined #openstack-meeting-320:53
*** piet has quit IRC20:53
*** lblanchard has quit IRC20:55
*** hdaniel has quit IRC20:57
*** piet has joined #openstack-meeting-320:58
*** bharathm has joined #openstack-meeting-321:00
*** tellesnobrega is now known as tellesnobrega_af21:02
*** salv-orl_ has joined #openstack-meeting-321:06
*** dslevin has joined #openstack-meeting-321:07
*** mbound_ has joined #openstack-meeting-321:07
*** mbound_ has quit IRC21:08
*** ivar-laz_ has joined #openstack-meeting-321:09
*** kzaitsev_mb has quit IRC21:10
*** john-davidge has quit IRC21:11
*** ivar-lazzaro has quit IRC21:12
*** kzaitsev_mb has joined #openstack-meeting-321:12
*** xavpaice has joined #openstack-meeting-321:12
*** Swami_ has joined #openstack-meeting-321:12
*** tellesnobrega_af is now known as tellesnobrega21:14
*** mfranc213 has quit IRC21:14
*** gutbuster has joined #openstack-meeting-321:16
*** mbound_ has joined #openstack-meeting-321:16
*** matrohon has quit IRC21:16
*** edleafe- has joined #openstack-meeting-321:20
*** mfranc213 has joined #openstack-meeting-321:22
*** krtaylor has quit IRC21:24
*** markvoelker has joined #openstack-meeting-321:25
*** edleafe- has quit IRC21:27
*** edleafe has quit IRC21:27
*** jamespd has joined #openstack-meeting-321:28
*** john-davidge has joined #openstack-meeting-321:28
*** edleafe has joined #openstack-meeting-321:29
*** ShillaSaebi has joined #openstack-meeting-321:29
*** markvoelker has quit IRC21:30
ShillaSaebi#startmeeting Ops and Architecture Guide21:31
openstackMeeting started Thu Dec 17 21:31:20 2015 UTC and is due to finish in 60 minutes.  The chair is ShillaSaebi. Information about MeetBot at http://wiki.debian.org/MeetBot.21:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:31
*** openstack changes topic to " (Meeting topic: Ops and Architecture Guide)"21:31
openstackThe meeting name has been set to 'ops_and_architecture_guide'21:31
*** mjrichardson has joined #openstack-meeting-321:31
ShillaSaebihello21:31
*** wojdev_ has joined #openstack-meeting-321:32
xavpaiceo/21:32
* mjrichardson waves21:32
*** piet has quit IRC21:32
ShillaSaebidarrenc here?21:33
darrencHi ShillaSaebi :)21:33
ShillaSaebihows it going?21:33
gutbusterhi21:33
*** wojdev has quit IRC21:33
*** wojdev_ is now known as wojdev21:33
darrencgood thanks21:33
ShillaSaebialright lets go ahead and get started21:33
ShillaSaebi#topic Action items from the previous meeting21:33
*** openstack changes topic to "Action items from the previous meeting (Meeting topic: Ops and Architecture Guide)"21:33
ShillaSaebii dont see any action items21:34
ShillaSaebiwe got the dates for the virtual swarm set which is 12/21 and 12/2221:34
ShillaSaebi#link https://etherpad.openstack.org/p/arch-guide-reorg21:35
ShillaSaebiplease use this etherpad to sign up and to add details for Monday/Tues21:35
darrencShillaSaebi: http://eavesdrop.openstack.org/meetings/ops_guide/2015/ops_guide.2015-12-03-21.58.txt21:35
ShillaSaebiok so darrenc and gutbuster to find some SMEs21:36
ShillaSaebihow did we do on that21:36
gutbusternot so well, everyone i talked to is pretty busy21:37
darrencYep, I got a few in APAC signed up21:37
gutbusteryay!21:37
xavpaice:)21:37
darrenc^^^21:37
gutbusterdid they sign up to review or to actually join the swarm?21:37
*** krtaylor has joined #openstack-meeting-321:37
darrencboth21:37
gutbustergood21:37
ShillaSaebithats great21:38
darrencgraeme gillies who originally proposed the new structure is helping out21:38
ShillaSaebithats great!21:38
darrencso should we discuss how the workflow for the swarm?21:39
*** madhu_ak_ has joined #openstack-meeting-321:39
*** mickeys has joined #openstack-meeting-321:39
ShillaSaebiyes we should21:40
darrencok21:40
darrencSo I'm hoping more SMEs can add comments to the etherpad so I can list some work items21:40
*** mickeys has left #openstack-meeting-321:41
darrencI can create a wiki page with the work items and participants can assign themselves to it21:41
*** madhu_ak has quit IRC21:41
xavpaicesounds like a great plan21:41
ShillaSaebiyeah that sounds good21:42
darrencIt be nice to assign pairs in a timezone to work together21:42
ShillaSaebiwe have about 3 people that are signed up to join for 1 out of the 2 days or roughly 5-6 hours21:42
darrencso an ops with a writer to work on a chapter21:42
darrencok cool21:42
xavpaicewhat timezones are people in?21:43
gutbustereastern (-500)21:43
ShillaSaebithe 3 from my side including myself are ET21:43
darrencI think APAC and US21:43
mjrichardsonNZDT (+1300), fwiw.21:44
ShillaSaebiwe will be starting at 11:00 AM ET on 12/2121:45
xavpaicewill there be an IRC location for discussion?21:47
darrencgood point21:47
darrencshould we create one for the swarm?21:47
*** mfranc213 has quit IRC21:48
ShillaSaebihmmm great point21:48
ShillaSaebiyeah we should21:48
darrenc#arch-guide-swarm?21:48
ShillaSaebisure21:48
ShillaSaebithat sounds good to me21:48
gutbusterprobably should; it'd be a long time to monopolize one of these channels21:48
ShillaSaebiok i added that to the etherpad21:48
xavpaicecool21:48
darrencAlso, I've created a draft directory for the arch guide with blank chapter files:  https://review.openstack.org/#/c/258246/21:49
darrencso don't hack up the current guide21:49
darrencwork in the draft directory21:49
ShillaSaebisweet21:49
ShillaSaebilooks like were almost ready to roll21:50
darrencyep!21:50
ShillaSaebido u think we should hit the docs ML one more time21:50
ShillaSaebimake an announcement, include the etherpad and the dates to see if we can get some more participation21:50
darrencI think so and the ops ML21:51
ShillaSaebiok i will do that now21:51
darrencthanks!21:51
ShillaSaebialright21:53
ShillaSaebianything else on the swarm21:53
*** mfranc213 has joined #openstack-meeting-321:53
darrencA friendly reminder to reference the blueprint in your commit messages as well21:54
*** mfranc213 has quit IRC21:54
*** mfranc213 has joined #openstack-meeting-321:55
darrencI think that's it21:55
ShillaSaebicool21:55
mjrichardsonGreat stuff21:55
ShillaSaebiand i got the email out21:55
ShillaSaebihopefully we can get some more hands in the pot21:55
ShillaSaebiI look fwd to Monday and Tues21:56
darrencMe too21:56
xavpaicewill be nice to make a change from daily ops21:56
ShillaSaebiyep21:56
darrencI think APAC will make a headstart21:56
darrencI think we've got enough core reviewers in the group to push things through21:57
xavpaiceunless those of us in apac wanted to do a Tue/Wed thing, with the US folks around in our morning21:57
ShillaSaebiyes21:57
darrencI'm cool to stick to Mon/Tues21:57
xavpaiceace.  I'll be about for most of those days, and can probably put some time aside after for reviews etc21:58
*** piet has joined #openstack-meeting-321:59
*** tellesnobrega is now known as tellesnobrega_af21:59
ShillaSaebigreat22:00
ShillaSaebi#topic open discussion22:00
*** openstack changes topic to "open discussion (Meeting topic: Ops and Architecture Guide)"22:00
ShillaSaebianything anyone wants to bring up?22:00
ShillaSaebialright if not, lets go ahead and call it22:01
ShillaSaebithanks everyone22:01
ShillaSaebilooking forward to next week22:01
ShillaSaebisee ya soon!22:01
ShillaSaebi#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
openstackMeeting ended Thu Dec 17 22:01:53 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_and_architecture_guide/2015/ops_and_architecture_guide.2015-12-17-21.31.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_and_architecture_guide/2015/ops_and_architecture_guide.2015-12-17-21.31.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_and_architecture_guide/2015/ops_and_architecture_guide.2015-12-17-21.31.log.html22:01
darrencbtw who's going to the ops midcycle?22:02
darrencthanks ShillaSaebi22:02
* xavpaice would love to but family needs me home22:02
darrencthe flight costs atm are insane22:03
darrenc$3-4K catttle class22:03
jamespdwhere is it this time?22:03
darrencManchester UK22:03
jamespdright22:03
darrenchttps://www.eventbrite.com/e/european-openstack-operators-meetup-tickets-1940585543622:05
*** ShillaSaebi has quit IRC22:05
*** spzala has quit IRC22:06
*** emily_w has quit IRC22:07
*** mfranc213 has quit IRC22:08
*** jmckind_ has joined #openstack-meeting-322:20
*** jmckind has quit IRC22:23
*** bpokorny_ has joined #openstack-meeting-322:25
*** spzala has joined #openstack-meeting-322:26
*** bpokorny has quit IRC22:28
*** jmckind has joined #openstack-meeting-322:28
*** jmckind_ has quit IRC22:29
*** spzala has quit IRC22:31
*** peristeri has quit IRC22:32
*** markvoelker has joined #openstack-meeting-322:33
*** Swami_ has quit IRC22:35
*** dslevin has quit IRC22:35
*** absubram has quit IRC22:36
*** rtheis has quit IRC22:42
*** mwagner_lap has quit IRC22:42
*** dslevin has joined #openstack-meeting-322:43
*** e0ne has quit IRC22:47
*** dtardivel has quit IRC22:47
*** banix has quit IRC22:50
*** piet has quit IRC22:51
*** spzala has joined #openstack-meeting-322:54
*** SumitNaiksatam has quit IRC23:00
*** jmckind has quit IRC23:01
*** ivar-laz_ has quit IRC23:02
*** ivar-lazzaro has joined #openstack-meeting-323:03
*** spzala has quit IRC23:08
*** mfranc213 has joined #openstack-meeting-323:09
*** bpokorny_ has quit IRC23:17
*** mfranc213 has quit IRC23:17
*** bpokorny has joined #openstack-meeting-323:17
*** mfranc213 has joined #openstack-meeting-323:19
*** Swami_ has joined #openstack-meeting-323:35
*** mfranc213 has quit IRC23:43
*** darrenc is now known as darrenc_afk23:44
*** wojdev has quit IRC23:44
*** mfranc213 has joined #openstack-meeting-323:45
*** jaypipes has quit IRC23:47
*** mbound_ has quit IRC23:51
*** sdake has joined #openstack-meeting-323:51
*** sdake has quit IRC23:52
*** ivar-lazzaro has quit IRC23:56
*** ivar-lazzaro has joined #openstack-meeting-323:58

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