Thursday, 2015-02-26

*** MarkAtwood has joined #openstack-meeting-300:01
*** baoli has quit IRC00:04
*** yamamoto has joined #openstack-meeting-300:05
*** r1chardj0n3s is now known as r1chardj0n3s_afk00:05
*** wojdev has joined #openstack-meeting-300:06
*** banix has joined #openstack-meeting-300:13
*** eghobo has joined #openstack-meeting-300:13
*** david-lyle is now known as david-lyle_afk00:14
*** wojdev has quit IRC00:17
*** seizadi has quit IRC00:20
*** Piet has joined #openstack-meeting-300:20
*** Sukhdev has joined #openstack-meeting-300:21
*** marun has quit IRC00:27
*** megm has joined #openstack-meeting-300:37
*** megm_ has quit IRC00:38
*** jaypipes has quit IRC00:40
*** yamamoto has quit IRC00:42
*** yamamoto has joined #openstack-meeting-300:47
*** banix has quit IRC00:51
*** EmilyW has quit IRC00:51
*** banix has joined #openstack-meeting-300:52
*** banix has quit IRC00:52
*** yamamoto has quit IRC00:55
*** SumitNaiksatam has quit IRC00:58
*** salv-orlando has quit IRC01:00
*** banix has joined #openstack-meeting-301:10
*** xuhanp has joined #openstack-meeting-301:10
*** VW_ has quit IRC01:11
*** eghobo has quit IRC01:14
*** SridharRamaswam1 has joined #openstack-meeting-301:14
*** MarkAtwood has quit IRC01:15
*** SridharRamaswamy has quit IRC01:15
*** banix has quit IRC01:18
*** eghobo has joined #openstack-meeting-301:19
*** eghobo has quit IRC01:23
*** eghobo has joined #openstack-meeting-301:25
*** marun has joined #openstack-meeting-301:25
*** armax has joined #openstack-meeting-301:30
*** marun has quit IRC01:31
*** stanzgy has joined #openstack-meeting-301:32
*** Sukhdev has quit IRC01:33
*** sambetts has quit IRC01:34
*** sambetts has joined #openstack-meeting-301:35
*** melwitt has quit IRC01:41
*** sigmavirus24 is now known as sigmavirus24_awa01:44
*** clu_ has quit IRC01:46
*** r1chardj0n3s_afk is now known as r1chardj0n3s01:49
*** alexsyip has quit IRC02:05
*** armax has quit IRC02:06
*** stanzgy_ has joined #openstack-meeting-302:13
*** seizadi has joined #openstack-meeting-302:16
*** bpokorny has quit IRC02:26
*** baoli has joined #openstack-meeting-302:29
*** armax has joined #openstack-meeting-302:34
*** sqchen has quit IRC02:40
*** banix has joined #openstack-meeting-302:45
*** markvoelker has quit IRC02:47
*** markvoelker has joined #openstack-meeting-302:47
*** carl_baldwin has joined #openstack-meeting-302:48
*** markvoelker has quit IRC02:51
*** yamahata has quit IRC02:52
*** lhcheng has quit IRC02:59
*** davidlenwell has quit IRC03:05
*** bpokorny has joined #openstack-meeting-303:10
*** davidlenwell has joined #openstack-meeting-303:11
*** carl_baldwin has quit IRC03:13
*** bpokorny has quit IRC03:14
*** carl_baldwin has joined #openstack-meeting-303:15
*** bpokorny has joined #openstack-meeting-303:15
*** baoli has quit IRC03:16
*** eghobo has quit IRC03:22
*** armax has quit IRC03:26
*** wchrisj has quit IRC03:29
*** coolsvap_ is now known as coolsvap03:33
*** baoli has joined #openstack-meeting-303:33
*** sbalukoff has quit IRC03:34
*** sankarshan_away is now known as sankarshan03:40
*** markvoelker has joined #openstack-meeting-303:43
*** yamamoto_ has joined #openstack-meeting-303:43
*** seizadi has quit IRC03:49
*** carl_baldwin has quit IRC03:51
*** carl_baldwin has joined #openstack-meeting-303:58
*** baoli has quit IRC03:59
*** baoli has joined #openstack-meeting-303:59
*** xuhanp has quit IRC04:03
*** baoli has quit IRC04:04
*** sulo has quit IRC04:04
*** wendar has quit IRC04:04
*** wendar has joined #openstack-meeting-304:04
*** sulo has joined #openstack-meeting-304:05
*** baoli has joined #openstack-meeting-304:05
*** armax has joined #openstack-meeting-304:06
*** MarkAtwood has joined #openstack-meeting-304:07
*** MarkAtwood has quit IRC04:09
*** baoli has quit IRC04:09
*** carl_baldwin has quit IRC04:14
*** bpokorny has quit IRC04:20
*** killer_prince is now known as lazy_prince04:21
*** yamamoto_ has quit IRC04:26
*** MarkAtwood has joined #openstack-meeting-304:32
*** SridharRamaswam1 has quit IRC04:32
*** takadayuiko has joined #openstack-meeting-304:36
*** megm_ has joined #openstack-meeting-304:39
*** megm has quit IRC04:39
*** markvoelker has quit IRC04:44
*** markvoelker has joined #openstack-meeting-304:45
*** Yi has quit IRC04:46
*** markvoelker has quit IRC04:49
*** banix has quit IRC04:51
*** MarkAtwood has quit IRC04:52
*** bpokorny has joined #openstack-meeting-304:56
*** ivar-laz_ has joined #openstack-meeting-304:56
*** ivar-laz_ has quit IRC04:56
*** coolsvap is now known as coolsvap_04:57
*** ivar-lazzaro has quit IRC04:59
*** yamahata has joined #openstack-meeting-305:01
*** coolsvap_ is now known as coolsvap05:04
*** Sukhdev has joined #openstack-meeting-305:15
*** jcoufal has joined #openstack-meeting-305:18
*** carl_baldwin has joined #openstack-meeting-305:19
*** hareeshp has joined #openstack-meeting-305:20
*** jckasper has joined #openstack-meeting-305:23
*** hareeshpc has joined #openstack-meeting-305:28
*** hareeshp has quit IRC05:31
*** bpokorny has quit IRC05:35
*** Yi has joined #openstack-meeting-305:37
*** yamamoto_ has joined #openstack-meeting-305:38
*** jcoufal has quit IRC05:39
*** jcoufal_ has joined #openstack-meeting-305:39
*** carl_baldwin has quit IRC05:42
*** seizadi has joined #openstack-meeting-305:42
*** egallen has joined #openstack-meeting-305:43
*** jcoufal_ has quit IRC05:44
*** r1chardj0n3s is now known as r1chardj0n3s_afk05:53
*** sarob has quit IRC06:01
*** Yi has quit IRC06:03
*** sarob has joined #openstack-meeting-306:03
*** sarob has quit IRC06:08
*** sbalukoff has joined #openstack-meeting-306:18
*** stendulker has joined #openstack-meeting-306:20
*** xuhanp has joined #openstack-meeting-306:22
*** sarob has joined #openstack-meeting-306:30
*** sarob has quit IRC06:41
*** stendulker has quit IRC06:41
*** stendulker has joined #openstack-meeting-306:42
*** seizadi has quit IRC06:42
*** SumitNaiksatam has joined #openstack-meeting-306:43
*** mrunge has joined #openstack-meeting-306:51
*** egallen has quit IRC06:57
*** hareeshpc has quit IRC07:02
*** belmoreira has joined #openstack-meeting-307:03
*** jcoufal has joined #openstack-meeting-307:07
*** scheuran has joined #openstack-meeting-307:10
*** sarob has joined #openstack-meeting-307:13
*** pkoniszewski has joined #openstack-meeting-307:13
*** egallen has joined #openstack-meeting-307:14
*** Sukhdev has quit IRC07:15
*** sarob has quit IRC07:18
*** sahid has joined #openstack-meeting-307:18
*** wojdev has joined #openstack-meeting-307:20
*** wojdev has quit IRC07:20
*** egallen has quit IRC07:27
*** armax has quit IRC07:33
*** markvoelker has joined #openstack-meeting-307:44
*** egallen has joined #openstack-meeting-307:45
*** akamyshnikova has quit IRC07:47
*** markvoelker has quit IRC07:50
*** jtomasek has joined #openstack-meeting-308:08
*** egallen has quit IRC08:09
*** takadayuiko has quit IRC08:11
*** sahid has quit IRC08:12
*** iovadia has joined #openstack-meeting-308:13
*** matrohon has joined #openstack-meeting-308:14
*** iovadia has quit IRC08:18
*** gilliard has left #openstack-meeting-308:24
*** lazy_prince is now known as killer_prince08:27
*** jcoufal has quit IRC08:28
*** jcoufal_ has joined #openstack-meeting-308:28
*** egallen has joined #openstack-meeting-308:28
*** iovadia has joined #openstack-meeting-308:32
*** salv-orlando has joined #openstack-meeting-308:39
*** armax has joined #openstack-meeting-308:40
*** JeanBriceCombebi has joined #openstack-meeting-308:41
*** megm has joined #openstack-meeting-308:41
*** sergef has joined #openstack-meeting-308:41
*** megm_ has quit IRC08:42
*** wojdev has joined #openstack-meeting-308:42
*** mrunge is now known as mrunge_bbl08:43
*** hareeshp has joined #openstack-meeting-308:47
*** zz_ttrifonov is now known as ttrifonov08:48
*** jcoufal_ has quit IRC08:50
*** MaxV has joined #openstack-meeting-308:51
*** yamahata has quit IRC08:53
*** sankarshan is now known as sankarshan_away08:54
*** JeanBriceCombebi has quit IRC09:00
*** hareeshp has quit IRC09:02
*** JeanBriceCombebi has joined #openstack-meeting-309:04
*** JeanBriceCombebi has quit IRC09:10
*** JeanBriceCombebi has joined #openstack-meeting-309:11
*** killer_prince has quit IRC09:12
*** evgenyf has joined #openstack-meeting-309:13
*** sarob has joined #openstack-meeting-309:14
*** jgrimm is now known as zz_jgrimm09:15
*** sahid has joined #openstack-meeting-309:19
*** sarob has quit IRC09:19
*** zz_johnthetubagu is now known as johnthetubaguy09:28
*** jemangs_ has quit IRC09:32
*** jemangs has joined #openstack-meeting-309:34
*** robcresswell_afk is now known as robcresswell09:39
*** robcresswell has left #openstack-meeting-309:39
*** hareeshp has joined #openstack-meeting-309:43
*** xuhanp has quit IRC09:46
*** markvoelker has joined #openstack-meeting-309:47
*** yamamoto_ has quit IRC09:49
*** JeanBriceCombebi has quit IRC09:49
*** salv-orlando has quit IRC09:49
*** evgenyf has quit IRC09:50
*** armax has quit IRC09:51
*** markvoelker has quit IRC09:52
*** xuhanp has joined #openstack-meeting-309:53
*** evgenyf has joined #openstack-meeting-309:58
*** JeanBriceCombebi has joined #openstack-meeting-309:58
*** [1]evgenyf has joined #openstack-meeting-310:02
*** wojdev has quit IRC10:05
*** evgenyf has quit IRC10:05
*** [1]evgenyf is now known as evgenyf10:05
*** wojdev has joined #openstack-meeting-310:06
*** armax has joined #openstack-meeting-310:06
*** VW_ has joined #openstack-meeting-310:07
*** sergef has quit IRC10:08
*** killer_prince has joined #openstack-meeting-310:10
*** killer_prince is now known as lazy_prince10:10
*** mrmartin has joined #openstack-meeting-310:12
*** sarob has joined #openstack-meeting-310:16
*** sarob has quit IRC10:21
*** yamamoto has joined #openstack-meeting-310:26
*** hareeshp has quit IRC10:26
*** hareeshp has joined #openstack-meeting-310:28
*** xuhanp has quit IRC10:34
*** sergef has joined #openstack-meeting-310:39
*** sahid has quit IRC10:40
*** mrunge_bbl is now known as mrunge10:40
*** sahid has joined #openstack-meeting-310:40
*** egallen has quit IRC10:47
*** stanzgy_ has quit IRC10:50
*** stanzgy has quit IRC10:50
*** VW_ has quit IRC11:03
*** hareeshp has quit IRC11:04
*** scheuran has quit IRC11:08
*** wojdev has quit IRC11:11
*** amotoki has joined #openstack-meeting-311:12
*** cbader has quit IRC11:15
*** yamamoto has quit IRC11:15
*** salv-orlando has joined #openstack-meeting-311:15
*** hareeshp has joined #openstack-meeting-311:16
*** sarob has joined #openstack-meeting-311:17
*** lazy_prince has quit IRC11:17
*** yamamoto has joined #openstack-meeting-311:18
*** sahid has quit IRC11:20
*** hareeshp has quit IRC11:21
*** killer_prince has joined #openstack-meeting-311:21
*** killer_prince is now known as lazy_prince11:22
*** sarob has quit IRC11:22
*** bryan_att has quit IRC11:24
*** VW_ has joined #openstack-meeting-311:30
*** VW__ has joined #openstack-meeting-311:38
*** VW__ has quit IRC11:39
*** VW__ has joined #openstack-meeting-311:39
*** VW_ has quit IRC11:41
*** salv-orlando has quit IRC11:44
*** stendulker has quit IRC11:46
*** JeanBriceCombebi has quit IRC11:50
*** egallen has joined #openstack-meeting-311:52
*** hareeshp has joined #openstack-meeting-312:17
*** mwagner_lap has quit IRC12:22
*** wojdev has joined #openstack-meeting-312:23
*** baoli has joined #openstack-meeting-312:30
*** baoli_ has joined #openstack-meeting-312:41
*** megm_ has joined #openstack-meeting-312:44
*** megm has quit IRC12:44
*** baoli has quit IRC12:44
*** etoews has joined #openstack-meeting-312:49
*** markvoelker has joined #openstack-meeting-312:50
*** etoews has quit IRC12:51
*** etoews has joined #openstack-meeting-312:52
*** salv-orlando has joined #openstack-meeting-312:54
*** armax has quit IRC12:55
*** scheuran has joined #openstack-meeting-312:56
*** markvoelker has quit IRC12:56
*** sahid has joined #openstack-meeting-312:57
*** ttrifonov is now known as zz_ttrifonov13:04
*** jkraj has joined #openstack-meeting-313:05
*** jckasper has quit IRC13:06
*** zz_ttrifonov is now known as ttrifonov13:09
*** mwagner_lap has joined #openstack-meeting-313:10
*** wojdev has quit IRC13:10
*** JeanBriceCombebi has joined #openstack-meeting-313:18
*** wojdev has joined #openstack-meeting-313:21
*** banix has joined #openstack-meeting-313:26
*** Yi has joined #openstack-meeting-313:30
*** wojdev has quit IRC13:38
*** JeanBriceCombebi has quit IRC13:39
*** JeanBriceCombebi has joined #openstack-meeting-313:39
*** etoews has quit IRC13:40
*** etoews has joined #openstack-meeting-313:42
*** Yi has quit IRC13:45
*** armax has joined #openstack-meeting-313:49
*** elmiko has joined #openstack-meeting-313:50
*** JeanBriceCombebi has quit IRC13:50
*** JeanBriceCombebi has joined #openstack-meeting-313:50
*** _crobertsrh is now known as crobertsrh13:51
*** markvoelker has joined #openstack-meeting-313:53
*** egafford has joined #openstack-meeting-313:53
*** huichun has joined #openstack-meeting-313:54
*** JeanBriceCombebi has quit IRC13:54
*** JeanBriceCombebi has joined #openstack-meeting-313:54
*** kchen has joined #openstack-meeting-313:56
SergeyLukjanovsahara folks, ping13:57
kchenhi all13:57
*** wojdev has joined #openstack-meeting-313:57
vgridnevhi all13:57
huichunhi13:57
*** huichun_ has joined #openstack-meeting-313:58
crobertsrhhello/13:58
*** pino|work has joined #openstack-meeting-313:59
*** markvoelker has quit IRC13:59
*** sigmavirus24_awa is now known as sigmavirus2413:59
SergeyLukjanov#startmeeting sahara14:00
openstackMeeting started Thu Feb 26 14:00:11 2015 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda14:00
NikitaKonovalovo/14:00
openstackThe meeting name has been set to 'sahara'14:00
SergeyLukjanov#topic sahara@horizon status (crobertsrh, NikitaKonovalov)14:00
*** openstack changes topic to "sahara@horizon status (crobertsrh, NikitaKonovalov) (Meeting topic: sahara)"14:00
SergeyLukjanovfolks, please14:00
SergeyLukjanov#link https://etherpad.openstack.org/p/sahara-reviews-in-horizon14:00
elmikoyo/14:00
*** etoews has quit IRC14:00
crobertsrhMany merged patches, which is good.14:00
NikitaKonovalovwe've got a status description change merged this week14:01
egaffordo/14:01
crobertsrhStill need reviews on the cluster/job execution guides14:01
NikitaKonovalovjob executions fix is still pending14:01
crobertsrhI believe that the blueprint for adding an events tab to the cluster view will be approved.14:01
*** tosky_ has joined #openstack-meeting-314:01
NikitaKonovalovcrobertsrh: It's already approved14:01
NikitaKonovalovon yesterdays meeting14:01
*** tosky_ is now known as tosky14:01
crobertsrhAh, yep.  I know it was discussed14:02
NikitaKonovalovthe change is WIP as the backend API is going to change soon14:02
*** annegentle has joined #openstack-meeting-314:02
NikitaKonovalovvgridnev is working on that14:02
SergeyLukjanovnice14:03
NikitaKonovalovno more updates from me here14:03
SergeyLukjanovso, overall status is good, yeah?14:03
vgridnevyes14:03
NikitaKonovalovSergeyLukjanov: yep14:03
SergeyLukjanovokay, let's move on14:04
SergeyLukjanov#topic News / updates14:04
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:04
elmikoworking on barbican integration and investigating hadoop secure mode14:05
vgridnevi'm working with updating events backend14:05
sreshetnyaki'm working on migration to openjdk14:05
huichun_working on Add a common HBase lib in hdfs on cluster start14:05
toskystill working on tempest (a bit put aside) and now trying to push sahara/horizon integration tests based on the new framework14:05
kchenI am still working on adding cm api library into cdh14:05
sreshetnyakplease review: #link https://review.openstack.org/#/c/146434/14:05
egaffordCreating the Oozie shell job type. Passing tests; working on doc now.14:06
vgridnevintel folks, it would be nice if you put your review for patches with names Applying event log for CDH - part X14:06
SergeyLukjanovtosky, how is it going?14:06
toskySergeyLukjanov: for horizon? Few pieces still needs to go in place14:07
*** marun has joined #openstack-meeting-314:07
huichun_vgridnev: ok14:07
SergeyLukjanovtosky, yeah, I mean horizon14:09
SergeyLukjanovanyything else?14:09
SergeyLukjanov#topic Open discussion14:09
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:09
SergeyLukjanov#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule14:10
SergeyLukjanov#info March 5 is FPF14:10
*** markvoelker has joined #openstack-meeting-314:10
elmiko:cough: https://review.openstack.org/#/c/157432/ :cough:14:11
elmiko;)14:11
egaffordA question: Sahara states that distributed mode is in alpha when you start in that mode. Are there known problems w/ distributed mode, and is there a roadmap toward maturity for this feature?14:11
*** JeanBriceCombebi has quit IRC14:12
*** marun has quit IRC14:12
egafford(Or is it just "wait a while, and if no problems are reported, take off the warning?")14:12
elmikoat this point i think we have to talk about roadmap to full feature14:13
egaffordelmiko: +114:13
*** thomasem has joined #openstack-meeting-314:13
elmikoi would think before we declare it production ready we will need a ci test for it?14:14
SergeyLukjanovI think we should remove this warning in Kilo14:14
SergeyLukjanovwe're already testing it a lot14:14
SergeyLukjanov(half of the sahara-ci jobs are running in distrib mode)14:14
elmikook, so yea maybe time to remove the warning14:14
egaffordSergeyLukjanov: Perfect.14:14
* pino|work politely raises his hand14:15
elmikoshould we make a bug to remove the warning?14:15
*** salv-orlando has quit IRC14:15
*** bknudson has quit IRC14:15
pino|worki just wanted to note that (due to other work) i've been testing sahara-image-elements (both juno and master) with diskimage-builder master14:16
elmikopino|work: aside from the duplicate naming issue, any other problems?14:16
pino|worksquashed few bugs related to that (1 in s-i-e, and 3 in d-i-b)14:16
SergeyLukjanovpino|work, cool!14:17
pino|workhttps://review.openstack.org/158347 (in s-i-e, merged)14:17
pino|workhttps://review.openstack.org/159050 (in d-i-b, merged)14:17
pino|workhttps://review.openstack.org/158383 (in d-i-b, merged)14:17
SergeyLukjanovre s-i-e we've tried to build the RHEL based image for CDH and it works ok after some fixes, I think sreshetnyak proposed them already14:17
pino|workhttps://review.openstack.org/158386 (in d-i-b, still missing, affecting ubuntu guests)14:18
SergeyLukjanovpino|work, so, we could switch to the latest d-i-b after that?14:18
*** hareeshpc has joined #openstack-meeting-314:19
pino|worki so far haven't been able to test many combination of sahara-related components/images14:19
pino|workmostly vanilla 2.4.1 and hdp 2.014:19
*** sarob has joined #openstack-meeting-314:20
pino|work(thanks to tosky too)14:20
egaffordSergeyLukjanov: Just to validate assumptions, re: trying to build the RHEL based image for CDH: you're using a RHEL 6 build host to build a RHEL 6 image using upstream (not packaged) DIB and SIE code. Is that correct?14:20
toskyegafford: during last meeting the answer was "ubuntu"14:21
toskybut let's see :)14:21
egaffordtosky: Ah, building from Ubuntu using upstream code. Good good. Just wanted to make sure I understood.14:21
*** TravT has quit IRC14:21
pino|workthere may be more issues for rhel6/centos6, both as guests built and as build hosts14:22
sreshetnyakegafford, i use ubuntu 14.04 as host system for build RHEL CDH image14:22
pino|workpart of it is touched by https://review.openstack.org/#/c/158820/ (the part about excuding --xattrs parameters)14:22
*** hareeshp has quit IRC14:22
pino|work(still referring to d-i-b/master)14:22
egaffordpino|work: Right; understood.14:23
*** sarob has quit IRC14:25
SergeyLukjanovanything else to discuss?14:27
pino|workjust a note: what would be a possible time schedule to migrate to a newer-ish d-i-b?14:28
pino|worklike, ASAP, or not earlier than ..., etc14:28
*** Yi has joined #openstack-meeting-314:28
elmikocould be done very quickly14:28
elmikojust make a bug to update DIB_REPO_BRANCH, then propose a patch14:29
elmikoi think it would get good support14:29
pino|workis there a minimum set of images which are considered "must build"?14:29
elmikohmm, probably all the plugin images that are current14:29
toskycurrent == master/kilo, right?14:30
elmiko(for example not 2.4.0 since it's deprecated)14:30
elmikotosky: yea14:30
tosky(as you can go back to the previous tag if you want to use the old ones)14:30
elmikoexactly14:30
SergeyLukjanovIMO it'll be great to upgrade to the lastest dib in kilo14:30
*** VW__ has quit IRC14:30
elmikoshould we make an action item ?14:31
*** VW_ has joined #openstack-meeting-314:31
*** hareeshp has joined #openstack-meeting-314:31
toskyespecially the "support matrix"14:31
pino|workso all the plugin types specified in diskimage-create.sh?14:31
elmikopino|work: yes, for all the plugins that are currently supported in kilo14:31
toskycombination of plugin type and distribution type, I guess14:31
pino|workelmiko: oki14:31
pino|workanother possibly dumb question: is having a tag in d-i-b with all the needed fixes/features a requirement, or a git commit within releases can be acceptable as well?14:33
elmikomy preference would be a tag14:33
*** Yi_ has joined #openstack-meeting-314:33
egaffordpino|work: Yeah, in theory anything that matches will work, but we'd love to build on something recognized by the DIB community as a supported release.14:34
*** hareeshpc has quit IRC14:34
elmikotechnically, DIB_REPO_BRANCH can be set to a commit sha14:34
pino|workyeah, that's why i was asking14:34
elmikothe dib crew seems pretty good about creating tags though, so it probably won't be an issue14:35
*** bknudson has joined #openstack-meeting-314:36
pino|workmakes sense, thanks for your answers!14:36
*** Yi has quit IRC14:36
*** wojdev has quit IRC14:37
egaffordSergeyLukjanov: A very minor note: we may want to check group permissions on sahara-dashboard's stable/icehouse branch. It doesn't seem to pull review perms from sahara-stable-maint at present.14:37
SergeyLukjanovegafford, I'll check it14:37
elmikoyea, and somehow i got +2 perms on the dashboard for stable/icehouse only. very strange...14:38
egaffordSergeyLukjanov: Thanks.14:38
SergeyLukjanovprobably not all permission rules applied, I'll check them for all our repos14:38
*** wojdev has joined #openstack-meeting-314:40
*** JeanBriceCombebi has joined #openstack-meeting-314:41
*** peristeri has joined #openstack-meeting-314:41
SergeyLukjanovsounds like end of the meetings ;)14:42
SergeyLukjanovthx folks14:42
*** zz_jgrimm is now known as jgrimm14:43
*** tmckay has joined #openstack-meeting-314:43
elmikoSergeyLukjanov: thanks!14:45
SergeyLukjanov#endmeeting14:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:45
openstackMeeting ended Thu Feb 26 14:45:18 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-02-26-14.00.html14:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-02-26-14.00.txt14:45
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-02-26-14.00.log.html14:45
*** etoews has joined #openstack-meeting-314:45
*** tosky has left #openstack-meeting-314:46
*** sarob has joined #openstack-meeting-314:47
*** lblanchard has joined #openstack-meeting-314:48
*** carl_baldwin has joined #openstack-meeting-314:49
*** jgrimm is now known as zz_jgrimm14:51
*** sarob has quit IRC14:52
*** kchen has quit IRC14:53
*** jckasper has joined #openstack-meeting-314:55
*** amuller has joined #openstack-meeting-314:55
*** jckasper_ has joined #openstack-meeting-314:55
*** mrsmith has joined #openstack-meeting-314:56
*** huichun has quit IRC14:56
*** tidwellr has joined #openstack-meeting-314:58
*** wojdev has quit IRC14:59
*** jckasper has quit IRC14:59
*** mlavalle has joined #openstack-meeting-315:00
carl_baldwinhi all15:00
mlavallehi15:00
*** johnbelamaric has joined #openstack-meeting-315:00
mrsmithHi15:00
tidwellrhi15:00
*** pino|work has left #openstack-meeting-315:00
johnbelamarichello15:01
carl_baldwinI probably won’t be able to stay the full hour.  Can we be quick?15:01
amullerhiya15:01
carl_baldwinmlavalle: mrsmith: tidwellr: johnbelamaric: amuller: hi15:01
*** pc_m has joined #openstack-meeting-315:01
johnbelamariccarl_baldwin: we can try!15:01
pc_mhi15:01
carl_baldwin#startmeeting neutron_l315:01
sc68calo/15:01
openstackMeeting started Thu Feb 26 15:01:29 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:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
pavel_bondarhi15:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
*** seizadi has joined #openstack-meeting-315:01
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
carl_baldwinMarch 19th is the big day.  Kilo-315:01
*** jrist has quit IRC15:02
carl_baldwin#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule15:02
carl_baldwinAny other announcements?15:02
carl_baldwin#topic Bugs15:02
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:02
carl_baldwinAnything super-important here?15:02
carl_baldwinIf not, we’ll move on and spend a little extra time on bugs next week.15:03
carl_baldwin#topic L3 Agent Restructuring15:03
*** openstack changes topic to "L3 Agent Restructuring (Meeting topic: neutron_l3)"15:03
carl_baldwinMy last patch here is https://review.openstack.org/#/c/158495/.  I need to turn my attention mostly away from this so I’ll just be care-and-feeding the patches that I currently have up.15:04
carl_baldwinI know there are loose ends and I encourage you to continue working on those loose ends.15:04
carl_baldwinmlavalle: Your patch is next in line.15:05
carl_baldwinmlavalle: I liked it overall when I reviewed it the other day.15:05
carl_baldwinmlavalle: Anything to discuss?15:05
mlavallecarl_baldwin: I saw your feedbacb and will work on it today. That's all15:05
mlavallefor today15:05
carl_baldwin#link https://review.openstack.org/#/c/147744/2615:05
carl_baldwinmlavalle: Thanks.  I didn’t see anything major in there.  Just minor cleanup.15:05
mlavalle:-)15:06
carl_baldwinAnything else?15:06
*** nelsnelson has joined #openstack-meeting-315:07
carl_baldwin#topic neutron-ipam15:07
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:07
carl_baldwinjohnbelamaric: tidwellr: salv-orlando: ping15:07
johnbelamariccarl_baldwin: pong15:07
tidwellrpong15:07
*** egafford has left #openstack-meeting-315:07
*** egafford has quit IRC15:08
carl_baldwinDid we reach a conclusion on the discussion from yesterday?15:08
johnbelamaricI believe so - it's in the review comments now.15:08
tidwellrI think so15:08
*** wojdev has joined #openstack-meeting-315:09
johnbelamaricany status on the reference driver? salv-orlando here?15:09
carl_baldwinjohnbelamaric: Do you have a link handy?  I haven’t seen the review since the comments have been added.15:09
johnbelamaricone sec15:09
pavel_bondar#link https://review.openstack.org/#/c/153236/8/neutron/db/db_base_plugin_v2.py that one?15:09
carl_baldwinjohnbelamaric: I thought we made some progress in salv-orlando ’s ML thread from the week.15:10
johnbelamaricpavel_bondar: yes, that's it15:10
*** mattfarina has joined #openstack-meeting-315:11
*** yamahata has joined #openstack-meeting-315:11
carl_baldwinpavel_bondar: Thanks, I think johnbelamaric ’s comment there is correct.15:11
*** jschwarz has joined #openstack-meeting-315:11
johnbelamariccarl_baldwin: yes, I think progress is being made i just haven't seen a new patch since then. maybe I missed it15:11
carl_baldwinjohnbelamaric: To me, the progress was more around narrowing down the scope for Kilo so that we don’t have to worry about all of the possibilities.15:11
johnbelamariccarl_baldwin: ah yes, I see your point.15:12
carl_baldwinI haven’t seen a new patch either but I expect one will come soon.15:12
johnbelamaricpavel_bondar: how is the dbbase plugin coming - are you blocked waiting on reference driver or you can proceed?15:12
pavel_bondarI still have work to do, but as soon as refence driver appears I could start testing15:13
*** salv-orlando has joined #openstack-meeting-315:14
pavel_bondarbiggest part that left to do is rollback on exception, since ipam call is done in separate transaction15:14
johnbelamaricpavel_bondar: ok15:14
salv-orlandoaloha people. sorry for being late.15:14
carl_baldwinsalv-orlando: hi15:14
pavel_bondarsalv-orlando: hi15:15
johnbelamaricsalv-orlando: hi15:15
*** annegentle has quit IRC15:16
*** sankarshan_away is now known as sankarshan15:16
carl_baldwinsalv-orlando:  Are there still open issues from the ML thread you started this week?15:16
salv-orlandocarl_baldwin: that thread has been inconclusive so far, which means15:17
salv-orlandothat for kilo we'll just adopt the same algorithm that we have, based on av ranges15:17
salv-orlandoadding only retry on deadlock15:17
salv-orlandoeasy and simple15:17
salv-orlandoalso reliable. Maybe not efficient but reliable15:17
salv-orlandowe can have fun in the next release and experiment with different things15:17
carl_baldwinsalv-orlando: I agree.  I think that is one mini-conclusion that came out of the thread.15:18
carl_baldwinsalv-orlando: You’re right though, the meat of the discussion was inconclusive.15:18
salv-orlandocarl_baldwin: it's not easy to reach any sort of agreement on this matter.15:19
carl_baldwinsalv-orlando: indedd15:20
johnbelamaricsalv-orlando: with pluggable, we don't need to - we can have multiple drivers and let experience show which algo is best :)15:20
carl_baldwins/indedd/indeed/15:20
*** markvoelker has quit IRC15:21
salv-orlandojohnbelamaric: yeah pretty much. But we're also free to change the internal behaviour of the driver without worrying about affecting anything at the mgmt layer15:21
johnbelamaricsalv-orlando: yes, good point too15:21
*** markvoelker has joined #openstack-meeting-315:21
*** etoews has quit IRC15:22
salv-orlandoso I'm not worried at all about just sticking with what we have - and defer optimization to the next release15:22
*** matrohon has quit IRC15:22
carl_baldwinsalv-orlando: I think we’re all in agreement.  I’m glad to have a direction that could get us to Kilo.15:22
carl_baldwinAnything more to discuss?15:23
pavel_bondarone question about passing subnetpool_id, since it should be property of Pool, it should present in Pools init(), right?15:23
pavel_bondarSo should we update Pool interface and include it into __init__?15:24
pavel_bondarI can add it to interface review page, and we could discuss it there15:24
carl_baldwinpavel_bondar: Yes, please do.15:25
pavel_bondarok15:25
*** hareeshpc has joined #openstack-meeting-315:25
*** huichun_ has quit IRC15:26
*** markvoelker has quit IRC15:26
*** crobertsrh has left #openstack-meeting-315:26
carl_baldwinAnything else to discuss here?15:26
carl_baldwin#topic neutron-ovs-dvr15:27
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:27
johnbelamariccarl_baldwin: see #link https://review.openstack.org/#/c/147479/14/neutron/manager.py15:27
carl_baldwinmrsmith: Swami: Rajeev:  ping15:27
mrsmithPong15:27
johnbelamaricfor a discussion of subnetpool_id, driver laoding, etc15:27
carl_baldwin#undo15:27
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x883d590>15:27
*** wojdev_ has joined #openstack-meeting-315:27
* carl_baldwin looking...15:27
johnbelamariccarl_baldwin: doesn't have to be now - can be addressed later15:28
*** wojdev has quit IRC15:28
*** wojdev_ is now known as wojdev15:28
johnbelamariccarl_baldwin: just wanted to bring it to your attention in relation to pavel_bondar's question15:28
carl_baldwinjohnbelamaric: Thanks for pointing it out.  It is still early for me here, I hadn’t seen it.15:28
carl_baldwin#topic neutron-ovs-dvr15:29
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:29
carl_baldwinmrsmith: hi, anything to discuss here?15:29
*** hareeshp has quit IRC15:29
mrsmithWorking on the non-voting test diffs between centralized15:29
carl_baldwinRajeev got me looking at a bug that might be due to the weak reference tracking of the fip namespace.  I don’t have any insight yet.15:29
mrsmithSlow progress15:29
mrsmithOk15:29
carl_baldwin#link https://bugs.launchpad.net/neutron/+bug/142563915:30
openstackLaunchpad bug 1425639 in neutron "A functional floating ip stops working sometimes if another floating ip is created and deleted." [Undecided,In progress] - Assigned to Rajeev Grover (rajeev-grover)15:30
mrsmithThere has been some improvement from swamis patches15:30
amullerthere's those 3 DVR bugs I found, I don't have time to add tests to those patches.15:30
carl_baldwinamuller: Could you link them here for posterity?15:31
amullercoming up15:31
carl_baldwinI was swamped last week and didn’t have time to look at them at all.  Sorry about that.15:31
*** jpomero has joined #openstack-meeting-315:31
amuller#link https://bugs.launchpad.net/neutron/+bug/142377715:31
openstackLaunchpad bug 1423777 in neutron "TRACE when removing a floating IP from a DVR router that has no floating IPs" [Undecided,In progress] - Assigned to Assaf Muller (amuller)15:31
amuller#link https://bugs.launchpad.net/neutron/+bug/142377515:32
openstackLaunchpad bug 1423775 in neutron "TRACE when restarting openvswitch if using OVS DVR agent" [Undecided,In progress] - Assigned to Assaf Muller (amuller)15:32
*** sarob has joined #openstack-meeting-315:32
amuller#link https://bugs.launchpad.net/neutron/+bug/142377415:32
openstackLaunchpad bug 1423774 in neutron "Fix TRACE when removing a DVR router port from a VLAN network" [Undecided,In progress] - Assigned to Assaf Muller (amuller)15:32
carl_baldwinamuller: Thanks.15:32
*** ongk has left #openstack-meeting-315:32
*** igordcard has joined #openstack-meeting-315:32
amullerall 3 have patchs up, marun -1 because they have no tests to mitigate regressions. I agree with him but I don't have time to deal with that.15:32
carl_baldwinamuller: ack15:33
amullerI was hoping someone could take those off my hands15:33
mrsmithI can try to find some cycles15:33
amullermrsmith: thanks15:33
*** VW_ has quit IRC15:33
mrsmithI'll take a look at least15:33
*** seizadi has quit IRC15:33
mrsmithFunctional or unit?15:34
*** VW_ has joined #openstack-meeting-315:34
carl_baldwinmrsmith: I’ll keep looking in to bug 1425639.  I suspect we’ll need to get some more logging added for when we can catch the bug in the gate and check queues.15:34
openstackbug 1425639 in neutron "A functional floating ip stops working sometimes if another floating ip is created and deleted." [Undecided,In progress] https://launchpad.net/bugs/1425639 - Assigned to Rajeev Grover (rajeev-grover)15:34
*** etoews has joined #openstack-meeting-315:34
*** zz_jgrimm is now known as jgrimm15:35
mrsmithamuller: functional or unit tests?15:35
amullermrsmith: depends on the case15:35
mrsmithK15:35
amullerwhatever is more appropriate. If you find yourself mocking out the entire world maybe a functional test would be better15:36
carl_baldwinAnything else on DVR to discuss here?15:37
carl_baldwin#topic Open Discussion15:38
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:38
*** hareeshpc has quit IRC15:39
amullercarl_baldwin: pc_m just +2'd https://review.openstack.org/#/q/topic:bug/1425759,n,z15:39
amulleron the vpnaas repo15:39
amullerI want to ask to merge these ASAP so we can start moving from though gigantic chain before K3...15:40
amullermoving through*15:40
carl_baldwinamuller: I think we can get those in quickly.15:40
amullercarl_baldwin: Sounds good :)15:41
pc_mI think we'll be OK, although am a little concerned as the impression is that we'll have seperate processes, for the AdvancedService instance, if > 1 agent for a service, however the test failure seems to imply instance was shared by two processes.15:41
*** jpomero has quit IRC15:41
amullera singleton cannot be shared across different processes15:42
pc_mNot an issue currently, as we have only one agent per service. Something we need to keep an eye on though.15:42
pc_mamuller: Right, so I'm having a hard time understanding how the functional test failed.15:42
amullerMe too :) The only thing I can think of is that somehow, two tests were running at the same time in the same process (Which shouldn't happen according to my understanding)15:43
amulleror there was some shared point in time where one tests did not finish and the other already started15:43
amullerthat would screw up the first test15:43
*** wojdev has quit IRC15:44
pc_mthough that would imply two agents in same process...15:44
amullerone test*15:44
*** sarob has quit IRC15:44
amullerpc_m: each test has its own agent15:44
amullerinitialized in the test setUp15:44
carl_baldwinpc_m: I think the test runner may run multiple tests in the same process.  I don’t know for sure how it works but it doesn’t surprise me.15:44
amullermind you we dont actually start the L3 agent like you do through the CLI, but the test setUp does create a L3 agent instance, which initializes its own self.conf15:45
pc_mcarl_baldwin: must be. Only way I could account for the issue.15:45
amullerso each L3 agent instance has its own conf object15:45
*** sahid has quit IRC15:45
*** Yi_ has quit IRC15:46
*** JeanBriceCombebi has quit IRC15:46
*** reed has joined #openstack-meeting-315:48
*** kaufer has joined #openstack-meeting-315:48
amullercarl_baldwin: who can I contact for FWaaS repo merge?15:49
pc_mamuller: dougwig, SumitNaiksatam15:49
*** igordcard has quit IRC15:50
*** dtroyer has joined #openstack-meeting-315:50
*** MarkAtwood has joined #openstack-meeting-315:50
carl_baldwinamuller: https://review.openstack.org/#/admin/groups/500,members15:50
salv-orlandoamuller: also any neutron drivers15:50
*** markvoelker has joined #openstack-meeting-315:51
amullersalv-orlando: Like yourself? :)15:51
salv-orlandoas long as I'm there, yes15:51
*** thomasem has quit IRC15:51
*** JeanBriceCombebi has joined #openstack-meeting-315:54
carl_baldwinI think we’ll call it a meeting.15:55
carl_baldwinThanks, everyone for all your work.15:55
*** gilliard_ has joined #openstack-meeting-315:56
carl_baldwin#endmeeting15:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:56
openstackMeeting ended Thu Feb 26 15:56:08 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-02-26-15.01.html15:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-02-26-15.01.txt15:56
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-02-26-15.01.log.html15:56
*** pc_m has left #openstack-meeting-315:56
*** johnbelamaric has left #openstack-meeting-315:56
*** mlavalle has left #openstack-meeting-315:56
*** thomasem has joined #openstack-meeting-315:57
*** thomasem has quit IRC15:57
*** stevelle has joined #openstack-meeting-315:57
*** igordcard has joined #openstack-meeting-315:58
*** mrsmith has quit IRC15:59
sigmavirus24#startmeeting api wg16:00
openstackMeeting started Thu Feb 26 16:00:01 2015 UTC and is due to finish in 60 minutes.  The chair is sigmavirus24. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
gilliard_Api-wg ?16:00
*** openstack changes topic to " (Meeting topic: api wg)"16:00
openstackThe meeting name has been set to 'api_wg'16:00
*** stendulker has joined #openstack-meeting-316:00
*** amuller has left #openstack-meeting-316:00
sigmavirus24gilliard_: :D16:00
gilliard_Ah, yes.  Hello.16:00
sigmavirus24Hello everyone!16:00
dtroyero/16:00
sigmavirus24#topic agenda16:00
*** openstack changes topic to "agenda (Meeting topic: api wg)"16:00
elmikoyo/16:00
*** yamahata has quit IRC16:00
sigmavirus24#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:00
*** thomasem has joined #openstack-meeting-316:00
stevelleo/16:00
kauferhello16:00
miguelgrinberghi16:01
*** kozhukalov has joined #openstack-meeting-316:01
*** bpokorny has joined #openstack-meeting-316:01
sigmavirus24Moving along16:01
sigmavirus24#topic versioning16:01
*** openstack changes topic to "versioning (Meeting topic: api wg)"16:01
sigmavirus24I think that's etoews' topic, but I wonder if cyeoh is around to talk about it too (seeing as how I think this is related to Nova's versioning)16:02
miguelgrinbergthere is no proposed guideline on this yet, correct?16:02
gilliard_I think it's 4am in Australia16:02
sigmavirus24gilliard_: You mean people don't stay up that late for openstack? =P16:03
gilliard_Slackers16:03
* sigmavirus24 doesn't know everyone's tz16:03
sigmavirus24miguelgrinberg: I don't believe there's one, no16:03
*** mikedillion has joined #openstack-meeting-316:03
miguelgrinbergno, I don't see anything in https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z16:04
sigmavirus24Should we circle back to this if etoews shows up?16:04
* sigmavirus24 is fairly certain it has to do with microversions in Nova but doesn't know what etoews wanted to say16:04
sigmavirus24No dissent so, moving on16:04
sigmavirus24#topic previous meeting action items16:04
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"16:04
sigmavirus24#link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-12-16.00.log.html16:05
sigmavirus24#link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-19-00.00.html16:05
sigmavirus24(Since the last meeting was 90% glance, there are action items from the last two meetings there)16:05
miguelgrinbergno action items, wow16:05
*** marun has joined #openstack-meeting-316:05
*** jschwarz has quit IRC16:05
kauferI had an action to get more input on https://review.openstack.org/#/c/147684/16:05
*** JeanBriceCombebi has quit IRC16:06
*** e0ne has joined #openstack-meeting-316:06
kauferHowever, I was hoping to get more consunsus from those in this WG before asking others16:06
sigmavirus24kaufer: you got cyeoh's input16:06
sigmavirus24;)16:06
kauferSpecifically jaypipes16:06
kauferAnd you sigmavirus24 :)16:06
sigmavirus24Jay isn't around16:06
sigmavirus24Uhoh, what'd I do now? =P16:06
*** JeanBriceCombebi has joined #openstack-meeting-316:06
miguelgrinbergI think it's nice and simple, +116:07
*** sigmavirus24 is now known as Slackwarebot16:07
*** Slackwarebot is now known as sigmavirus2416:07
sigmavirus24I haven't read it in a while16:08
* sigmavirus24 will read it after the meeting16:08
*** yuriy_n17 has joined #openstack-meeting-316:08
kauferI'll send out a note to the ML and then start PM'ing folks on this one16:08
kauferThanks sigmavirus2416:08
sigmavirus24kaufer: sounds good16:08
sigmavirus24Other action items people want to update?16:09
sigmavirus24#action kaufer to gather more API-WG consensus on https://review.openstack.org/#/c/147684/5 before bringing it to the ML16:09
sigmavirus24Onwards then16:09
sigmavirus24#topic guidelines16:09
*** openstack changes topic to "guidelines (Meeting topic: api wg)"16:09
sigmavirus24     #link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z16:10
sigmavirus24#link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z16:10
sigmavirus24(in case meetingbot decides to not parse it without stripping the whitespace)16:10
sigmavirus24https://review.openstack.org/#/c/155911/ seems to have consensus16:10
*** mikedillion has quit IRC16:11
sigmavirus24https://review.openstack.org/#/c/141229/ needs more input because there's a serious discussion of how to accommodate Swift16:11
miguelgrinberg(and that won't be easy)16:11
sigmavirus24Well it may not be that we need to accommodate Swift, any more than Swift needs to realize why their current design is ill-considered and why they're currently breaking RFCs and should strive to be incompliance with them16:12
sigmavirus24s/incompliance/in compliance/16:12
*** VW_ has quit IRC16:12
miguelgrinbergsure, or they can opt to not follow the guideline. Nothing will die of it.16:13
elmikosigmavirus24: but tell us what you really think ;)16:13
miguelgrinbergthey have their reasons, I can understand that16:13
sigmavirus24elmiko: heh16:13
dtroyerwe seem to keep running in to the notion that these guidelines are binding and retroactive16:13
elmikoagreed with miguelgrinberg at some level, if swift chooses not to follow the guideline then that is their perogative16:14
miguelgrinbergbut I think it is a too contrived use case to have influence on this doc16:14
*** erikmwilson has joined #openstack-meeting-316:14
sigmavirus24Also if I recall correctly, they're arguing that this would affect object creation for them too, which I don't see how that is the case as this purely affects endpoints for metadata only16:15
sigmavirus24Not for creation with metadata16:15
*** mrmartin has quit IRC16:15
sigmavirus24But yes, this is another case of people not understanding that these aren't retroactive guidelines16:15
miguelgrinbergyes, this is all about their endpoints, which are too vaguely defined16:15
miguelgrinbergthere is ambiguity16:16
sigmavirus24They're also designed around an API design that iirc Amazon no longer uses16:16
miguelgrinbergso a /metadata can be metadata or can be a swift object called metadata16:16
miguelgrinbergI have ideas on how to disambiguate, but not sure they want to listen16:16
*** annegentle has joined #openstack-meeting-316:16
sigmavirus24So discussion should be further focused on that review16:17
sigmavirus24Because it appears John and Samuel aren't here16:17
*** VW_ has joined #openstack-meeting-316:17
*** VW_ has quit IRC16:17
sigmavirus24We should probably also involve the ML16:17
miguelgrinbergokay, I'll take the action to ask for feedback on the ML16:17
*** VW_ has joined #openstack-meeting-316:18
sigmavirus24#action miguelgrinberg to get ML feedback on https://review.openstack.org/#/c/141229/16:18
sigmavirus24(You can't say I volunteered you for that one miguelgrinberg)16:18
miguelgrinbergI did it to myself :)16:18
sigmavirus24We also seem to have consensus on https://review.openstack.org/#/c/158179/16:18
*** yamamoto has quit IRC16:18
sigmavirus24But that's less than a week old so we have to wait for more discussion per our own guidelines around merging guidelines16:19
sigmavirus24;)16:19
*** cdent has joined #openstack-meeting-316:19
elmikothat one seemed must less controversial too16:19
elmiko*much16:19
cdentapologies for lateness, had another meeting16:19
sigmavirus24elmiko: right16:19
sigmavirus24cdent: No worries.16:19
sigmavirus24cdent: agenda is https://wiki.openstack.org/wiki/Meetings/API-WG16:21
*** iovadia has quit IRC16:21
sigmavirus24We're discussing guidelines16:21
miguelgrinbergI'm also going to ask for ML feedback on the tagging doc https://review.openstack.org/#/c/155620/16:21
*** iovadia has joined #openstack-meeting-316:21
*** annegentle has quit IRC16:22
sigmavirus24#action miguelgrinberg to bring tagging guideline to the ML https://review.openstack.org/#/c/155620/16:22
miguelgrinbergHappy that Heat is implementing this spec :)16:22
kaufermiguelgrinberg: Any thoughts on if we need to revisit the repeated query string parameter vs. comma separated that came back up in the tagging guideline?16:22
*** mrunge has quit IRC16:23
kaufermiguelgrinberg: I thougt that we had closed that issue but it crept back in in that review16:23
miguelgrinbergkaufer: don't know. I thought we beat that horse to death, but seems we didn't16:23
cdenton the tagging thing: In case it's not clear from the chest inflating going on in the comments there: I'm fine with the spec as is, but we _could_ use tag=foo&tag=bar if we really wanted to16:23
*** iovadia has quit IRC16:23
*** iovadia has joined #openstack-meeting-316:23
elmikothis is also similar to a question i have about filtering16:23
cdentI think the reason it came back into play is that there is a large discussion still unresolved about the extent to which we want to be driving global improvement, as opposed to local okayness16:24
*** iovadia has left #openstack-meeting-316:24
miguelgrinbergcdent: you could, but it would not be in agreement with the current rev of the guideline16:24
sigmavirus24cdent: there's a similar design for sorting that's already been approved and is already being implemented16:24
stevellecdent: conflating what the WG wants and what the community can do?16:24
sigmavirus24cdent: the WG can write all the guidelines it wants, the community can do whatever it pleases since we have no real authority16:25
miguelgrinbergmy view on this is that both options are valid, we have to pick one. We picked single args for sorting, so I think we should stay with single args for everything else.16:25
cdentmiguelgrinberg: that's reasonable enough16:25
kaufermiguelgrinberg: +116:25
elmikomiguelgrinberg: just to be clear, that would be the "tag=foo&tag=bar" foramt?16:26
*** EmilyW has joined #openstack-meeting-316:26
miguelgrinbergelmiko: so that would apply to filtering when we get to it16:26
miguelgrinbergelmiko: no, the other one: "tags=foo,bar"16:26
elmikomiguelgrinberg: ok, how would filtering look given that approach?16:27
*** thangp has joined #openstack-meeting-316:27
*** iovadia1 has joined #openstack-meeting-316:27
miguelgrinbergI haven't look at any implementations of filtering, do you have an example?16:27
elmikohttps://review.openstack.org/#/c/157563/16:28
elmikothat's a spec we're working through in sahara currently16:28
sigmavirus24So this has drifted from discussion of the current specs16:28
sigmavirus24Should we save this for the end?16:28
elmikoi'm cool with that16:28
miguelgrinbergyeah, sure16:28
sigmavirus24#topic APIImpact16:28
*** openstack changes topic to "APIImpact (Meeting topic: api wg)"16:28
sigmavirus24#link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z16:28
stevelleOpenStack has a mess of different filtering models already.  I can get a summary that was cooked up in the py SDK project16:28
sigmavirus24There should be a cinder review there that DuncanT was supposed to address here16:29
elmikostevelle: that would be awesome!16:29
briancurtinstevelle: https://etherpad.openstack.org/p/find_filters16:29
sigmavirus24Oh wait, yuriy_n17 has it at the end of the discussion16:29
miguelgrinbergstevelle: +116:29
DuncanTWhat am I supposed to be addressing, sorry?16:29
sigmavirus24DuncanT: https://review.openstack.org/#/c/156552/16:29
elmikobriancurtin: thanks16:30
stevellebriancurtin: thanks16:30
sigmavirus24You and yuriy_n17 were to bring that up during this part of the meeting :)16:30
DuncanTAh, ok. So we discovered today that cinder always uses UTC, except for a couple of migrations16:31
miguelgrinberg(I'll save my comments till the end)16:31
e0nesigmavirus24: yes. we want to decide to timezone should be shown in API16:31
*** EmilyW has quit IRC16:31
*** iovadia1 has quit IRC16:31
e0neas DuncanT mentioned, it isn't big issue for cinder now16:31
*** EmilyW has joined #openstack-meeting-316:32
sigmavirus24I also don't see a blueprint for this in cinder (which would seem to be a good idea)16:32
e0nesigmavirus24: we've got bur reported for it16:32
sigmavirus24That would also make it easier for us to discuss because it would more succinctly describe the change being made there16:33
miguelgrinbergdoes this topic deserve a guideline doc? I thought it is pretty standard to use UTC on any public representations16:33
e0nesigmavirus24: do we have any guidelines for it?16:33
sigmavirus24e0ne: no there aren't. I mentioned that yesterday during cinder's meeting16:34
e0nesigmavirus24: afaik, nova shows timezone in api, but i could be wrong16:34
sigmavirus24My personal taste is to include the timezone information using ISO8601 but I understand that will break current clients16:34
*** gilliard_ has quit IRC16:34
*** Yi has joined #openstack-meeting-316:34
sigmavirus24Also any guideline we propose is for future versions of the API, not necessarily for additions to existing versions16:34
e0neif all openstack projects will use utc time in api - it won't be issue at all16:35
dtroyer++16:35
sigmavirus24e0ne: agreed. That's basically a de facto best practice for any and all APIs16:35
e0nesigmavirus24: agree. but we must have to document it16:36
*** david-lyle_afk is now known as david-lyle16:36
sigmavirus24e0ne: no doubt. Would you like to write that guideline?16:36
e0nebecause time to time will got new users and/or developers which rise this question again16:36
e0nesigmavirus24: ok. i'll do it with yuriy_n17. he was an initiator of this topic:)16:37
sigmavirus24e0ne: thanks16:38
sigmavirus24#action e0ne and yuriy_n17 to write a guideline about datetime representation in APIs16:38
e0ne:)16:38
sigmavirus24Any other APIImpact reviews people want to highlight?16:38
stevelleshould be pretty non-controversial16:39
sigmavirus24stevelle: I agree16:39
elmikohttps://review.openstack.org/#/c/157563/16:39
elmikoso, we are talking about filtering in our review16:39
elmikoand were curious about the most proper methods16:40
elmikothe path we are investigating is something like "?filterkey=value&filterkey2=value"16:40
miguelgrinbergelmiko: I think that style makes it hard to use negative filtering16:41
elmikoor "filterkey=value1&filterkey=value2"16:41
elmikomiguelgrinberg: could you elaborate?16:41
miguelgrinberghow do you specify that you want anything but a given value for a field?16:41
sigmavirus24miguelgrinberg: excluding keys with certain values16:41
*** gilliard_ has joined #openstack-meeting-316:41
elmikowe hadn't considered that option16:41
elmikowe were only looking at positive filtering16:41
miguelgrinbergsay you like all servers that are not named "foo"16:41
elmikoright, i'm curious what would be a better approach?16:42
stevelle...or all jobs that do not have a tag "foo"16:42
kaufermiguelgrinberg: Do you know of any projects that implement negative filtering like that?16:42
miguelgrinbergI haven't given a lot of thought, but one possibility is to define a simple query language, and just stuff an expression in a "q" argument16:42
miguelgrinbergkaufer: not in openstack afaik16:43
cdentI've done things like: select=tag:!foo16:43
*** amotoki has quit IRC16:43
sigmavirus24cdent: yeah, I think something like that is what miguelgrinberg is proposing16:43
sigmavirus24It wouldn't hurt to see if choosing a subset of something people are familiar with (e.g., elasticsearch's query language) would be a good idea *If we need it*16:44
miguelgrinbergand then there is the issue of specifying ORs and ANDs16:44
elmikoin this case, we mainly need to prune results. i'd really love to look at something i could suggest to the team regarding a query language.16:44
kauferalso, there are some projects (ie, nova) where one filter key is filtering using an exact match and another is used using a regular expression16:45
miguelgrinbergthe gerrit search is an example of a query language, though I'm not sure it has negative filtering16:45
*** hareeshp has joined #openstack-meeting-316:45
kauferit would be nice if we had a uniform mechanism to define if a filter is an exact match, a regex, a negative filter, etc.16:45
sigmavirus24miguelgrinberg: it does16:45
*** megm has joined #openstack-meeting-316:45
sigmavirus24miguelgrinberg: -owner:me16:45
sigmavirus24or something like that16:46
sigmavirus24it's very similar to elasticsearch's ql16:46
miguelgrinbergsigmavirus24: nice, so that's a good model, though it may be too complex for projects that want a simple search16:46
*** megm_ has quit IRC16:46
miguelgrinbergmaybe a guideline should include simple searches as well16:46
sigmavirus24right16:46
elmikowould there be an issue with something like "?filterkey1=value&filterkey1=-value2"16:46
elmiko?16:46
sigmavirus24elmiko: what about val-ue2?16:47
cdentthere's a lot of overlap between searching, filtering, sorting and limiting16:47
cdentbut they are also distinct16:47
sigmavirus24I would assume it could be done intelligently enough but it might get tricky16:47
miguelgrinbergelmiko:  I don't remember who didn't like me proposing the "-" as negative filtering16:47
sigmavirus24miguelgrinberg: that was on sort though and was kind of an awkward way of defining asc/desc though16:47
sigmavirus24to be fair16:47
elmikohmm, i could see some corner case issues16:47
sigmavirus24miguelgrinberg: I think cdent and I were opposed16:47
kauferalso, on the topic of filtering ... anyone know if the valid filters for a given project are discoverable?16:47
cdentI do not recall that senator.16:48
sigmavirus24kaufer: if the project is properly implementing JSON Home it should be16:48
sigmavirus24kaufer: also a schema for an endpoint should tell you16:48
sigmavirus24I don't expect a project to have globally defined filters for all endpoints16:48
miguelgrinbergkaufer: the filters should be the fields in the representation ideally, no need to call them out16:48
kauferso, to align with how we did sort, maybe something like "?filterkey1=value&filterkey1=value2:negative"16:49
elmikokaufer: that's not bad16:49
miguelgrinbergkaufer: still no way to specify AND/OR16:49
*** gilliard_ has quit IRC16:49
kauferAND is implicit16:49
kauferbut agree, there is no OR16:49
cdentwant OR, just ask again?16:49
kaufercdent: good point16:50
miguelgrinbergI think I'm leaning towards only positive filtering with filterkey=value, and if you want more then define a query language16:50
stevellecdent: costs twice as much to service that way sadly16:50
elmikoyea, positive filtering is bog easy with the filterkey=value methodology16:50
cdentI wasn't supporting it, just stating the option.16:50
miguelgrinbergcdent: that doesn't scale unfortunately16:50
cdentif explicit booleans are desired then a quoted query string is probably needed16:51
miguelgrinbergcdent: yes, a q=<query> style argument16:51
elmikoshould we attempt to come up with a standardized query language for the guidelines in addition to the default positive filtering idea?16:51
cdentyou can have both: simple implict and style queries, plus complex q="some long string of stuff with OR and AND and (* )"16:51
kauferseems like there are a lot of ideas around filtering, should we start an etherpad and use that as a starting point to hash this out?16:51
cdentjinx16:51
*** seizadi has joined #openstack-meeting-316:51
sigmavirus24yeah16:52
sigmavirus24We're running close to the end of meeting16:52
* cdent nods16:52
sigmavirus24Should we move on?16:52
elmikokaufer: +116:52
elmikocdent: yea i like the idea of dual approach16:52
sigmavirus24Are there other API Impact topics?16:52
*** carl_baldwin has quit IRC16:52
sigmavirus24It seems gilliard has left16:52
cdentI have a what should have been API Impact but couldn't get the commit message changed question/comment:16:53
*** stendulker has quit IRC16:53
sigmavirus24cdent: shoot16:53
*** salv-orlando has quit IRC16:53
*** sahid has joined #openstack-meeting-316:53
cdentGiven uri /foo/bar/baz is it legit for /foo/bar to return 404 or should it return _something_ (what?) to indicate that baz (and siblings) might be there.16:54
*** amotoki has joined #openstack-meeting-316:54
cdentthis issue is coming up in:16:54
cdenthttps://review.openstack.org/#/c/159204/16:54
cdent(but that's not the place where the lack of APIImpact is, as that's my commit)16:55
miguelgrinbergcdent: imo you can return 40416:55
cdentcertainly from a strictness standpoint 404 is correct, but from a friendliness standpoint, less so16:55
miguelgrinbergif you want to return something, then you are getting into the idea of sub-resources16:56
cdentIt assumes a non human client that already knows the api, rather than a human digging around for kicks and giggles.16:56
miguelgrinbergso for example /resource returns a big representation, then /resource/field-name returns a subset of the big resource16:56
elmikoso, in the example of /foo/bar/baz, /foo/bar would return all bazs?16:57
miguelgrinbergI know people roll their eyes when I say this (I know you are sigmavirus24), but URLs should be opaque, should be discovered, so there is no obligation to have them nicely structured16:57
cdentI mostly agree with you miguelgrinberg, if discovery mechanism is present, but when it is not...16:58
sigmavirus24elmiko: that's what miguelgrinberg is saying but it may not always be true16:58
miguelgrinbergwhen it is not, you document the valid endpoints, so still not a problem16:58
sigmavirus24I'm also not rolling my eyes at you miguelgrinberg, that's a waste without you being able to see it16:58
cdentelmiko: baz is one of the bars, /foo/bar would return all the bars16:58
miguelgrinbergsigmavirus24: save it for next month :)16:58
cdent(or somethign like that)16:58
elmikook, so the bars might include bazs, amongst other things?16:59
elmikoor are bars and bazs unrelated?16:59
sigmavirus24we're almost out of time17:00
sigmavirus24#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu Feb 26 17:00:07 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-26-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-26-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-02-26-16.00.log.html17:00
sigmavirus24I sent that later than I intended to do17:00
sigmavirus24Perhaps we should continue on the ML17:00
sigmavirus24Thanks everyone17:00
elmikosigmavirus24: thanks!17:00
cdentelmiko in the case I was imagining bars might include bazs, amongst other things17:00
sigmavirus24cdent: ML ;)17:01
cdentyah17:01
sigmavirus24that or we need to reserve 2 hours for these meetings17:01
sigmavirus24=P17:01
elmikocdent: thanks for indulging me =)17:01
elmikoneeds more #openstack-api !17:01
*** cdent has left #openstack-meeting-317:02
*** amotoki has quit IRC17:02
sigmavirus24elmiko: we can register that channel if we want17:02
elmikosigmavirus24: i'm guessing it would be pretty low traffic, but might be cool for questions and what not17:02
sigmavirus24Also for finishing conversations17:03
elmikolol17:03
stevelleanyone want an informal action item?17:03
elmikoseems like a nice idea to me, i've got loads of questions =D17:04
sigmavirus24I'm working on it17:04
*** jckasper has joined #openstack-meeting-317:05
elmikosigmavirus24: nice!17:05
sigmavirus24elmiko: we're discussing the idea in #openstack-dev too17:06
*** lsmola has quit IRC17:06
*** pkoniszewski has quit IRC17:07
*** thomasem_ has joined #openstack-meeting-317:08
*** jckasper_ has quit IRC17:09
*** thomasem has quit IRC17:11
*** thomasem_ has quit IRC17:12
*** JeanBriceCombebi has quit IRC17:13
*** thomasem has joined #openstack-meeting-317:16
*** etoews has quit IRC17:16
*** scheuran has quit IRC17:17
*** annegentle has joined #openstack-meeting-317:18
*** alexsyip has joined #openstack-meeting-317:18
*** yamamoto has joined #openstack-meeting-317:19
*** sankarshan is now known as sankarshan_away17:19
*** MaxV has quit IRC17:23
*** annegentle has quit IRC17:23
*** belmoreira has quit IRC17:23
*** yamamoto has quit IRC17:24
*** sahid has quit IRC17:28
*** yamahata has joined #openstack-meeting-317:29
*** etoews has joined #openstack-meeting-317:31
*** tmckay is now known as _tmckay17:31
*** thomasem has quit IRC17:37
*** igordcard has quit IRC17:38
*** jlvillal|afk is now known as jlvillal17:39
*** SumitNaiksatam has quit IRC17:40
*** yuriy_n17 has quit IRC17:43
*** carl_baldwin has joined #openstack-meeting-317:45
*** evgenyf has quit IRC17:46
*** thomasem has joined #openstack-meeting-317:46
*** mwagner_lap has quit IRC17:48
*** salv-orlando has joined #openstack-meeting-317:49
*** tidwellr has left #openstack-meeting-317:51
*** johnthetubaguy is now known as zz_johnthetubagu17:53
*** mageshgv has joined #openstack-meeting-317:54
*** rkukura has joined #openstack-meeting-317:57
*** kaufer has left #openstack-meeting-317:59
*** Youcef has joined #openstack-meeting-318:01
*** bpokorny_ has joined #openstack-meeting-318:01
*** SumitNaiksatam has joined #openstack-meeting-318:01
rkukurahi SumitNaiksatam18:02
yapenghello18:02
mageshgvhi18:02
banixhi18:03
*** kbyrne has quit IRC18:03
*** ivar-lazzaro has joined #openstack-meeting-318:03
*** emagana has joined #openstack-meeting-318:03
*** s3wong has joined #openstack-meeting-318:03
YiHi Folks18:03
s3wongYi: hello18:03
ivar-lazzarohi18:03
Yis3wong: Hi!18:04
*** thomasem has quit IRC18:04
*** bpokorny has quit IRC18:05
*** kbyrne has joined #openstack-meeting-318:05
s3wongSumitNaiksatam seems to be online......18:05
*** LouisF has joined #openstack-meeting-318:05
*** LouisF has quit IRC18:06
*** SumitNaiksatam has quit IRC18:06
s3wongnot anymore..... :-)18:06
*** emagana has quit IRC18:07
*** SumitNaiksatam has joined #openstack-meeting-318:07
SumitNaiksatamrkukura: mageshgv banix ivar-lazzaro: there?18:08
banixSumitNaiksatam: hi, yes18:08
rkukurahi again SumitNaiksatam18:08
s3wongseems like he is back online.....18:08
mageshgvSumitNaiksatam: hi18:08
SumitNaiksatamdarn, some problem with my client18:08
ivar-lazzaroSumitNaiksatam: hi18:08
*** thomasem has joined #openstack-meeting-318:08
SumitNaiksatami was not able to see any responses18:08
yapengSumitNaiksatam: welcome back:)18:08
SumitNaiksatam#startmeeting networking_policy18:08
openstackMeeting started Thu Feb 26 18:08:55 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:08
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:08
*** openstack changes topic to " (Meeting topic: networking_policy)"18:08
openstackThe meeting name has been set to 'networking_policy'18:08
SumitNaiksatamyapeng: s3wong: :-)18:09
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#Feb_26th.2C_19th.2C_12th.2C_201518:09
SumitNaiksatamso i wanted to make a proposal up front18:09
SumitNaiksatamhow about having a bug squashing day sometime early next week?18:10
SumitNaiksatamthat will help us plan for the next cut of the stable release as well18:10
SumitNaiksatamthe idea would be squash as many as high and medium priority bugs on that18:10
SumitNaiksatamand have reviewers handy to review and merge them18:11
rkukura+1, but not on Monday (I’m flying)18:11
SumitNaiksatamrkukura: sure18:11
SumitNaiksatamwe can coordinate on the day, perhaps, tuesday/wednesday18:11
mageshgv+1, sure, we can have it next week18:11
SumitNaiksatamif everyone is on board with the idea18:11
Yi+118:11
ivar-lazzaroSumitNaiksatam: +118:12
SumitNaiksatamnote that this will also help with regards to the planned refacto (to have these bugs fixed before the refactor)18:12
*** stevelle has left #openstack-meeting-318:12
SumitNaiksatamYi: ivar-lazzaro: mageshgv: ok thanks for the confirmation18:12
yapeng+1, wed. works for me.18:13
SumitNaiksatamlets tenatively plan that for tuesday or wednesday (or perhaps even thursday)18:13
SumitNaiksatamyapeng: thanks18:13
SumitNaiksatami will reach out to everyone, and follow up with a note to the ML18:13
*** LouisF has joined #openstack-meeting-318:13
SumitNaiksatamLouisF: hi18:14
LouisFSumitNaiksatam: hi18:14
SumitNaiksatamLouisF: FYI - we are planning a bug squashing day sometime next week18:14
LouisFok18:14
SumitNaiksatamokay anything else to share with the rest of the team upfront?18:14
SumitNaiksatam#topic Bugs18:15
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:15
SumitNaiksatamso still on the topic of bugs18:15
SumitNaiksatamone request, please check if the bugs you are fixing have a “juno-backport-potential” tag18:15
SumitNaiksatamand if so, please propose a cherry-pick backport patch to the stable/juno branch18:15
*** songole has joined #openstack-meeting-318:16
SumitNaiksatamwe dont have any criticals show up during the week18:16
SumitNaiksatamany other bugs/fixes we need to discuss here?18:16
SumitNaiksatammageshgv: and krishnaK have a couple of bug fixe patches on review18:17
SumitNaiksatammageshgv: i think ivar-lazzaro had some comments for you, anything we need to discuss with the rest of the team here?18:17
SumitNaiksatamsongole: hi!18:17
songoleHi SumitNaiksatam18:17
*** ChuckC has quit IRC18:17
mageshgvSumitNaiksatam: I think the comments are addressed unless ivar-lazzaro has some more comments to bring up18:18
SumitNaiksatammageshgv: ah, i did not check today18:18
ivar-lazzaromageshgv: will look at the review today18:18
*** SridharRamaswamy has joined #openstack-meeting-318:18
SumitNaiksatamyeah, lets circle back on that18:19
SumitNaiksatamoh, while on that18:19
SumitNaiksatamone informational point to the team -18:19
*** annegentle has joined #openstack-meeting-318:19
SumitNaiksatamwhen creating a foreign key or unique constraints, please provide a name to those18:19
SumitNaiksatamthere are at least a couple of places in the code where we are not doing that18:20
*** VW_ has quit IRC18:20
ivar-lazzaroSumitNaiksatam: +1!18:20
SumitNaiksatamit becomes a little bit messy to drop those constructs later18:20
SumitNaiksatamivar-lazzaro: thanks for doing the investigation on this as well18:20
ivar-lazzaroSumitNaiksatam: magesh found a way of doing that in a backward compatible way18:20
*** VW_ has joined #openstack-meeting-318:20
SumitNaiksatamivar-lazzaro: true18:20
ivar-lazzaromageshgv: that's awesome!18:20
SumitNaiksatamand thats great, but i think it will still help to name18:20
mageshgvAs a general rule it will help later if we name the constraints though18:21
SumitNaiksatammageshgv: yeah18:21
*** pkoniszewski has joined #openstack-meeting-318:21
rkukuraSumitNaiksatam: no need to name the constraints18:21
SumitNaiksatammageshgv: for the fix you have, is there any chance that column names can have overlaps?18:21
rkukurasee https://review.openstack.org/#/c/116122/23/neutron/db/migration/alembic_migrations/versions/2d2a8a565438_hierarchical_binding.py for a migration that removes unnamed constraints18:22
SumitNaiksatammageshgv: i know its not true in our case currrently18:22
mageshgvSumitNaiksatam: I do not think there will be any overlap issue there18:22
SumitNaiksatamrkukura: i am sure it can be done, as mageshgv also figured out18:23
ivar-lazzarorkukura: thanks for the link18:23
SumitNaiksatamrkukura: i think it makes the code more readable and less prone to mistakes if the constraint is identified by a name18:23
rkukuraSumitNaiksatam: makes sense18:23
*** annegentle has quit IRC18:24
SumitNaiksatamany other bugs that we need to discuss?18:24
SumitNaiksatami dont see a follow up on: 1416527 and 141720618:24
SumitNaiksatamso i will check with jishnub again18:24
SumitNaiksatam#topic Re-factor Group Based Policy with Neutron RESTful APIs18:25
*** openstack changes topic to "Re-factor Group Based Policy with Neutron RESTful APIs (Meeting topic: networking_policy)"18:25
SumitNaiksatamso we spent another week deliberating on this18:25
SumitNaiksatamand i think it was time well spent18:25
yapengyes, thanks for comments.18:26
SumitNaiksatammeanwhile yapeng and Yi also have some WIP patches18:26
yapengI updated the spec yesterday. please review it.18:26
SumitNaiksatamyapeng: yes, i saw that, and I have +2’ed it18:26
SumitNaiksatami think we should close on this now, and have further discussion in the implementation patches18:26
SumitNaiksatamif we need to revisit design, we can revise the spec by posting a follow up patch18:27
YiSumitNaiksatam: +118:27
ivar-lazzaroSumitNaiksatam: on you comment on L102 of #link https://review.openstack.org/#/c/153126/7/specs/kilo/gbp-refactor-neutron-restful-api.rst18:27
ivar-lazzaroSumitNaiksatam: when "self.create_policy_target" is used in the UTs, that is a wrapper for neutron-wsgi18:27
SumitNaiksatamivar-lazzaro: yes18:27
ivar-lazzaroSumitNaiksatam: that's not a direct call18:28
ivar-lazzaroSumitNaiksatam: erm "neutron-plugin" call18:28
ivar-lazzaroSumitNaiksatam: under the hood that method does a new_create_request18:28
SumitNaiksatamivar-lazzaro: is that what is being mentioned there?18:30
ivar-lazzaroSumitNaiksatam: so as long as the UTs client wrapper uses neutron-wsgi calls, we should be ok18:30
ivar-lazzaro"When a call such as "create_policy_target" [1] is made in the RMD UT, the RMD implementation is making a neutron-plugin call."18:30
ivar-lazzaroSumitNaiksatam: did I understand it wrong?18:31
SumitNaiksatamivar-lazzaro: checking18:31
yapengivar-lazzaro: I think this is the current implementation..18:31
*** jckasper has quit IRC18:32
SumitNaiksatamivar-lazzaro: by neutron-plugin calls i am referring to #link https://github.com/stackforge/group-based-policy/blob/master/gbpservice/neutron/services/grouppolicy/drivers/resource_mapping.py#L1358-L141618:33
ivar-lazzaroSumitNaiksatam: ok, that seemed to be referring to the UT implementation18:34
ivar-lazzaroSumitNaiksatam: thanks for the clarification18:34
SumitNaiksatamivar-lazzaro: okay18:34
SumitNaiksatamivar-lazzaro: ah i see, i put [1] as a reference to the UT calls18:35
SumitNaiksatamokay so anyone not on board to make progress with the way the current spec is defined?18:36
s3wong+118:36
*** mageshgv has quit IRC18:37
SumitNaiksatams3wong: thanks :-)18:37
SumitNaiksatamokay, so unless there are any other major concerns lets close on this spec today18:38
*** egallen has quit IRC18:38
SumitNaiksatamcores - request you to take a look at the earliest and push this forward18:38
s3wongSumitNaiksatam: I can review the spec one more time today and give the second +218:38
*** erikmwilson has quit IRC18:38
SumitNaiksatams3wong: okay great, thanks!18:38
SumitNaiksatam#topic Floating IP support18:39
*** openstack changes topic to "Floating IP support (Meeting topic: networking_policy)"18:39
SumitNaiksatam#undo18:39
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x8b0aa50>18:39
SumitNaiksatamjust realized that i did not post the link of the refactoring spec...18:40
SumitNaiksatamso belatedly - #link https://review.openstack.org/#/c/153126 ;-)18:40
SumitNaiksatam#topic Floating IP support18:40
*** openstack changes topic to "Floating IP support (Meeting topic: networking_policy)"18:40
*** ChuckC has joined #openstack-meeting-318:40
SumitNaiksatam#link https://review.openstack.org/15729818:40
SumitNaiksatami think mageshgv dropped off18:41
SumitNaiksatammyself and ivar-lazzaro reviewed this, and we are waiting for mageshgv to post the next patch set18:41
SumitNaiksatamanyone else had a chance to look at the above spec?18:41
SumitNaiksatamquestions/comments?18:41
SumitNaiksatami believe songole is here and might be able to address those on mageshgv’s behalf18:42
rkukuraSumitNaiksatam: I have not yet, but will18:42
*** sbalukoff has quit IRC18:42
SumitNaiksatamrkukura: great, thanks18:42
songoleSumitNaiksatam: I have not reviewed yet. I will review.18:42
SumitNaiksatamsongole: ah okay :-)18:42
SumitNaiksatamrkukura: songole any chance that you guys can review this by EoD?18:43
songoleok18:43
*** bpokorny_ has quit IRC18:43
SumitNaiksatamthat way when mageshgv is back by evening our time, he can post a consolidated/updated patch set18:43
*** _tmckay has left #openstack-meeting-318:44
rkukuraSumitNaiksatam: OK18:44
SumitNaiksatamrkukura: thanks18:44
SumitNaiksatamrkukura: over to you for the next two topics18:45
SumitNaiksatam#topic Taskflow investigation18:45
*** openstack changes topic to "Taskflow investigation (Meeting topic: networking_policy)"18:45
SumitNaiksatamyou mentioned you are reviewing the neutron patches18:45
SumitNaiksatamand gaining better understanding18:45
rkukuraI haven’t made any progress on this since last week, but will get to it shortly18:46
rkukuraI’d also like to look at how other projects are using TaskFlow18:46
SumitNaiksatamrkukura: sure18:46
SumitNaiksatamrkukura: would it help if we have a sesson with manish next week?18:46
SumitNaiksatamsince you are going to be here?18:46
SumitNaiksatami can try and reach out to him18:46
*** ChuckC has quit IRC18:47
SumitNaiksatamrest of the team can also participate18:47
rkukuraSumitNaiksatam: could be a good idea, but lets see when we schedule the bug squashing first18:47
SumitNaiksatamrkukura: yes sure, we can do those on separate days18:47
SumitNaiksatamokay so two action items for me in terms of planning for next week18:48
rkukuraI think we may have some different requirements with the need to validate and implicitly create resources before transactions, ...18:48
SumitNaiksatamrkukura: sure18:48
*** coolsvap is now known as coolsvap_18:48
*** cbader has joined #openstack-meeting-318:48
SumitNaiksatamrkukura: thanks for the update18:48
rkukuranp18:48
SumitNaiksatam#topic Packaging update18:49
*** openstack changes topic to "Packaging update (Meeting topic: networking_policy)"18:49
*** ChuckC has joined #openstack-meeting-318:49
SumitNaiksatami believe no developments on the RH/Fedora packing, right?18:49
*** melwitt has joined #openstack-meeting-318:49
SumitNaiksatamrkukura: ^^^ ?18:50
rkukuraSumitNaiksatam: one18:50
*** kozhukalov has quit IRC18:50
rkukuraThe heat package’s dependencies have become out of date, so this needs an update18:50
*** mattgriffin has joined #openstack-meeting-318:51
rkukurawould be nice to update to stable releases for everything at the same time18:51
SumitNaiksatamrkukura: ah, was just asking if we needed to cut a new stable18:51
rkukuraIts actially the horizon package, not heat18:51
SumitNaiksatamso on that, susaant has made a couple of fixes in gbpautomation which should be backported18:51
SumitNaiksatamrkukura: ah okay18:52
SumitNaiksatami will be posting a fix in horizon as well18:52
rkukuraand it might just be that fedora rawhide has already moved to a kilo milestone - need to investigate18:52
SumitNaiksatamrkukura: okay18:52
rkukurahow about if we target end of next week for stable update?18:52
rkukuraafter we’ve squashed and backported bugs18:53
SumitNaiksatamrkukura: sure, end of next week18:53
SumitNaiksatamso horizon we can cut new stable after i post the patch18:54
SumitNaiksatamplease watch out for that18:54
*** songole_ has joined #openstack-meeting-318:54
rkukurawas just looking at the broken dependency email - I think we will need kilo-compatible versions to resolve this18:54
SumitNaiksatamrkukura: oh, thats tricky18:54
SumitNaiksatamrkukura: lets discuss offline18:54
rkukurabut this issue is just with Fedora rawhide (F22) right now, not RDO, which is still Juno18:54
SumitNaiksatamrkukura: whew!18:55
SumitNaiksatamslightly off current-topic, but since we brought up heat - susaant has two important bug fixes waiting to be reviewed:18:55
SumitNaiksatam#link https://review.openstack.org/15509618:55
SumitNaiksatam#link https://review.openstack.org/15515318:55
SumitNaiksatamif anyone has time, please review18:55
SumitNaiksatamthe above will need to be backported18:56
SumitNaiksatamthere is another one which is for a namespace change: #link https://review.openstack.org/15517218:56
SumitNaiksatamwhich will not be backported18:56
SumitNaiksatamalso regarding the Ubuntu packages18:56
SumitNaiksatamwe have not documented the install process (similar to what has been done for RH/Fedora)18:57
SumitNaiksatami think magesh tried this and has some notes18:57
SumitNaiksatamhe will be posting them on the wiki18:57
SumitNaiksatambut if anyone else has tried this, please chime in18:57
SumitNaiksatamon the wiki page18:57
*** songole has quit IRC18:57
SumitNaiksatamthis would be the place to put it: #link https://wiki.openstack.org/wiki/GroupBasedPolicy#Try_Group-based_Policy18:57
SumitNaiksatam#topic Open Discussion18:57
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:57
SumitNaiksatamLouisF: nicolas mentioned that there was someone from his team who was going to follow up on your blueprints18:58
SumitNaiksatamLouisF: havent seen acitivity there18:58
*** egallen has joined #openstack-meeting-318:58
*** egallen has quit IRC18:59
SumitNaiksatamanything else anyone want to discuss?18:59
SumitNaiksatamgrand total of one min remaining ;-)18:59
SumitNaiksatamokay, i guess nothing more for today19:00
*** e0ne is now known as e0ne_19:00
rkukuraanyone using the extension driver APIs?19:00
*** bpokorny has joined #openstack-meeting-319:00
SumitNaiksatamrkukura: not yet19:00
SumitNaiksatamneed to check with banix19:00
rkukurasome changes in the neutron version of those we might want to pull in19:00
SumitNaiksatamand i think ivar-lazzaro also plans to use19:00
SumitNaiksatamlets take it to #openstack-gbp19:01
SumitNaiksatamthanks everyone19:01
SumitNaiksatambye!19:01
ivar-lazzarociao!19:01
yapengbye!19:01
SumitNaiksatam#endmeeting19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
openstackMeeting ended Thu Feb 26 19:01:34 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-02-26-18.08.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-02-26-18.08.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-02-26-18.08.log.html19:01
rkukurabye19:02
Yibye19:03
*** Youcef has quit IRC19:04
*** rkukura has left #openstack-meeting-319:04
*** pkoniszewski has quit IRC19:09
*** wojdev has joined #openstack-meeting-319:11
*** erikmwilson has joined #openstack-meeting-319:14
*** etoews has quit IRC19:14
*** erikmwilson has quit IRC19:15
*** songole_ has quit IRC19:15
*** jckasper has joined #openstack-meeting-319:16
*** armax has quit IRC19:20
*** coolsvap_ is now known as coolsvap19:21
*** etoews has joined #openstack-meeting-319:21
*** etoews has quit IRC19:24
*** bpokorny_ has joined #openstack-meeting-319:26
*** hareeshp has quit IRC19:28
*** bpokorny has quit IRC19:28
*** thomasem has quit IRC19:31
*** matrohon has joined #openstack-meeting-319:32
*** s3wong has quit IRC19:32
*** s3wong has joined #openstack-meeting-319:33
*** MaxV has joined #openstack-meeting-319:34
*** mwagner_lap has joined #openstack-meeting-319:39
*** LouisF has quit IRC19:41
*** EmilyW has left #openstack-meeting-319:43
*** wojdev has quit IRC19:45
*** wojdev has joined #openstack-meeting-319:46
*** sbalukoff has joined #openstack-meeting-319:47
*** e0ne_ is now known as e0ne19:52
*** jkraj has quit IRC19:55
*** r1chardj0n3s_afk is now known as r1chardj0n3s19:58
*** r1chardj0n3s has left #openstack-meeting-319:59
*** VW_ has quit IRC20:02
*** thomasem has joined #openstack-meeting-320:07
*** jtomasek has quit IRC20:10
*** mattgriffin has quit IRC20:11
*** MaxV_ has joined #openstack-meeting-320:15
*** MaxV has quit IRC20:19
*** yamamoto has joined #openstack-meeting-320:22
*** Shamail has joined #openstack-meeting-320:23
*** Shamail has quit IRC20:24
*** Shamail has joined #openstack-meeting-320:25
*** Shamail has quit IRC20:26
*** yamamoto has quit IRC20:26
*** sigmavirus24 is now known as sigmavirus24_awa20:32
*** hareeshp has joined #openstack-meeting-320:38
*** megm_ has joined #openstack-meeting-320:48
*** megm has quit IRC20:48
*** mattgriffin has joined #openstack-meeting-320:48
*** hareeshp has quit IRC20:49
*** hareeshp has joined #openstack-meeting-320:52
*** sergef has quit IRC20:53
*** mattgriffin has quit IRC20:56
*** VW_ has joined #openstack-meeting-320:56
*** Yi has quit IRC20:58
*** dtroyer has left #openstack-meeting-320:59
*** Sam-I-Am has joined #openstack-meeting-321:00
Sam-I-Amhello21:01
*** mwang2 has quit IRC21:02
*** Shamail has joined #openstack-meeting-321:02
ShamailHi everyone21:02
Shamailmegm_: how are you?21:03
Sam-I-Amhello21:03
ShamailHi Sam-I-Am!21:03
ShamailI guess we are a light crew today?  I don't see Sriram, Matt, Nick, etc.21:03
*** lblanchard has quit IRC21:03
Sam-I-Amnick was supposed to lead this in matt's absense21:04
ShamailOr am I in the wrong room? (Fairly common with me)21:04
Sam-I-Ami thought we're here21:04
Sam-I-Amlemmie email nick21:04
ShamailI do too21:04
ShamailHmm, when was the email sent?21:04
ShamailI missed it.21:04
Sam-I-Amfew mins ago to openstack-docs21:05
Sam-I-Amjust before the meeting21:05
ShamailAh21:05
Sam-I-Amwe'll wait here for a bit21:05
ShamailYep21:05
Sam-I-Amsometimes time zones are hard21:06
ShamailI messed up and set docs to a daily digest21:06
ShamailI don't get immediate notice... Don't know how to change that.21:06
*** mrmartin has joined #openstack-meeting-321:06
ShamailTime zones are hard, especially when you travel. :-)21:06
ShamailWas cloud don here last week?21:07
Sam-I-AmShamail: i think you can change it on lists.openstack.org21:07
*** mwang2 has joined #openstack-meeting-321:07
ShamailI'll give that a shot.21:07
Sam-I-Amnick says he'll be here shortly21:07
ShamailDid Matt suggest any agenda items in that message?21:07
Sam-I-Amwe all have back to back meetings :/21:07
ShamailAwesome21:08
Sam-I-Ami think we're going to review additions to the ToC21:08
Sam-I-Amthat was last week's task21:08
ShamailGot it.21:08
ShamailI spoke with WTE today and can provide an update from them as well21:08
ShamailDid you submit any sessions for Vancouver?21:09
Sam-I-Amyes, i did21:09
*** nickchase has joined #openstack-meeting-321:09
nickchasehey, all21:09
ShamailGood luck!21:09
Sam-I-Amhi nick21:09
nickchasehave we started?21:09
ShamailHi nickchase21:09
ShamailNo21:09
nickchaseok, let's.21:10
ShamailAll yours sir21:10
nickchasetrying to remember how to start the meet bot21:10
nickchase#startmeeting21:10
openstacknickchase: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'21:10
nickchase#startmeeting HA Guide21:11
openstackMeeting started Thu Feb 26 21:11:00 2015 UTC and is due to finish in 60 minutes.  The chair is nickchase. Information about MeetBot at http://wiki.debian.org/MeetBot.21:11
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:11
*** openstack changes topic to " (Meeting topic: HA Guide)"21:11
nickchasethere we go.21:11
openstackThe meeting name has been set to 'ha_guide'21:11
nickchaseOK, then, so let me grab last week's notes, one moment21:11
Shamailperfect.21:11
*** esp has left #openstack-meeting-321:12
nickchaseOK, so we had no "official" action items from last week, but I know that megm was filling in links to existing material in the TOC.  (digging...)21:12
nickchasehttps://wiki.openstack.org/wiki/HAGuideImprovements/TOC21:12
nickchaseshe said that she's not quite finished yet21:13
ShamailI have an update on this "topic" (loosely coupled)21:13
nickchaseAlso do we have any of the mirantis team here (besides me)?21:13
nickchaseawesome, go, Shamail21:13
Sam-I-Amyeah, the big one was updating the ToC21:13
Sam-I-Amwith a secondary of seeing what was re-usable21:13
nickchasegreat so let's stick with that.21:13
ShamailI told the win the enterprise team that we are trying to establish scope for the HA-Guide....21:14
ShamailFor example is it just instructions or should it help people establish a HA strategy as well21:14
ShamailThis will probably impact ToC as well21:14
Sam-I-Amnickchase: i'm going to the ops mid-cycle and plan to see what people are using for HA21:14
Sam-I-Amnickchase: so this should help the ToC21:14
ShamailSam-I-Am: that is awesome21:15
*** coolsvap is now known as coolsvap_21:15
nickchasegreat.21:15
ShamailWhat is our stance on the topic I mentioned related to scope?21:15
Sam-I-Ami added/removed a few things since last week21:15
nickchaseso one thing at a time:  Shamail:  I think it should talk about strategy21:15
nickchaseSam-I-Am: what do you think?21:16
Sam-I-Amsure21:16
Shamailnickchase: agreed, but I have not seen much content discussion around strategy versus tactical execution of HA21:16
nickchaseThat's fine, we need to get it in there, then.21:16
nickchase#agreed We need to add strategy information to the TOC.21:17
ShamailThe current version of HA-Guide assumes that people understand HA (and implications) and simply need instructions on how to implement21:17
*** markmcclain has quit IRC21:17
nickchaseSo I will get some structure in for strategy if  nobody else wants it.21:17
nickchasegoing once ... going twice...21:18
Sam-I-Amwe dont want to re-invent someone else's docs... so imho, for things like galera, we should point people at the galera docs21:18
ShamailI'd like to help with that (as a co-developer or reviewer)21:18
nickchaseSure.21:18
Sam-I-Amhowever, how to implement galera with openstack is our thing.21:18
nickchaseok, great.21:18
nickchaseyes.21:18
ShamailI agree Sam-I-Am21:18
nickchase#action nickchase Add structure for HA strategy.21:18
Sam-I-Amnickchase: hey this is already better than the docs meeting today :)21:18
nickchase#agreed We don't want to duplicate existing docs (ie, for Galera)21:18
nickchaseSam-I-Am:  I can start a fist fight if you want. :)21:19
Sam-I-Amnickchase: can we make the ha guide pretty? :)21:19
ShamailDid Matt do a read-out for his task of reviewing the install-guide?21:19
nickchase:)21:19
Sam-I-Amnickchase: i prefer dumpster fires21:19
nickchaseShamail: my understanding is he's still working on it.21:19
*** markmcclain has joined #openstack-meeting-321:19
ShamailCool.  I missed last week so wasn't sure (I could've reviewed notes)21:20
nickchaseso moving on...21:20
nickchaseOK, so the Mirantis guys are looking at which topics they think they can complete quickly and efficiently and let us know.21:20
nickchaseso between that and the existing content, that'll give us some structure for figuring out what we still need to assign.21:20
ShamailPlease let me know which topics are "up for grabs" as well.  I'm willing and able. :)21:21
nickchaseGreat.21:21
nickchaseOK, so do we have an actual agenda (he said, slapping his forehead)?21:21
ShamailNot sure, although I did want to mention my task and its lack of completion. :)21:22
Sam-I-Amnot much beyond task updates from last meeting21:22
Sam-I-Amand maybe that we'll do this in rst :)21:22
nickchaseapparently it's TBD. :)21:23
ShamailHehe21:23
nickchaseI'm fine to do it in RST now that we know how. :)21:23
nickchaseit's easy peasy to get it set up.21:23
nickchaseEven if I do seem to be giving Andreas hives. :)21:23
ShamailSomeone fill me in!  I'm all for it.21:23
nickchasewhat, how to do RST?21:23
Sam-I-Amprobably a good thing to determine early so we don't get another network guide fiasco21:24
ShamailNo, switching. :-)21:24
nickchasewe haven't decided, to the best of my knowledge.21:24
nickchaseand I don't think we should without Matt here.21:25
nickchaseDiscussion for the mailing list, perhaps?21:25
*** alexsyip has quit IRC21:25
Sam-I-Amnickchase: yes21:25
nickchaseany objections to discussing on the ML?21:25
nickchasegreat.21:25
ShamailNope21:25
nickchase#agreed We'll take the discussion of RST vs Docbook to the mailing list.21:26
nickchaseOK, so do we have anything else right now?21:26
ShamailSo, as Matt was reviewing install-guide, I have volunteered to review ops-guide.  The intention was to review it to determine whether it contains "recovery" information from failures.  I was out of the office last week but I wanted to let everyone know that I am still planning to go through all 300+ pages.21:26
nickchaseexcellent.21:26
Sam-I-Ami dont think there's much in the ops guide about ha21:26
Sam-I-Ambut you never know. such is the problem with a lot of different-but-not-really guides21:26
ShamailI don't think so either but should it?21:26
nickchase#action Shamail Review the ops guide for any references that are relevant to HA.21:27
nickchase#action Sam-I-Am Review the install guide for any references that are relevant to HA.21:27
ShamailI'm going to steal that term Sam-I-Am21:27
*** Yi has joined #openstack-meeting-321:27
Sam-I-Amoh, was that MY thing, or matt's thing :) lol21:27
nickchaseI think that in places where it's relevant we should link it over ot the HA guide.21:27
Sam-I-Amsometimes i'm sam, sometimes i'm not21:27
Shamaillol21:27
nickchase:)21:28
nickchasewhat else we got?21:28
Sam-I-Amso i'm doing the install guide bits?21:28
Sam-I-Amwhere should we log these things, an etherpad?21:28
nickchaseIf you prefer.  I like the wiki better but I'm not in charge.21:28
ShamailDo we know which sessions were proposed for Vancouver in relation to HA?21:28
nickchaseI do not.21:29
ShamailI submitted one but wasn't sure if others did21:29
Sam-I-Ami dont either. probably best to wait until they're voted on.21:29
nickchaseI was woefully under-diligent in voting.21:29
ShamailI prefer wiki as well21:29
Sam-I-Amthen maybe some of us can hit those sessions21:29
nickchaseyou're outvoted, matt. :)21:29
Sam-I-Amwiki is fine21:29
Sam-I-Ami spent half a day voting and only got through maybe 1/4 of them21:30
nickchaseyou want to create wiki pages and link them to the main page or do you want me to?21:30
Sam-I-Amnickchase: you can do it, managerate!21:30
nickchaseI cherry-picked the ones that looked interesting.21:30
nickchase:)21:30
nickchase#action nickchase Create wiki pages for the install guide and ops guide notes and link them from the main HA guide page.21:31
nickchasenext?21:31
ShamailI'm done :)21:31
nickchaseSam-I-Am?21:32
Sam-I-Ami think we're good, sir21:32
nickchaseexcellent.21:32
Sam-I-Ammake sure you send an update e-mail with our tasks :)21:32
nickchaseI hereby return the next 28 mintues.21:32
nickchase:)21:32
nickchaseI managerated them properly in the bot, I hope.21:32
Sam-I-Ami'll see you tomorrow for Yet Another Meeting21:32
nickchase#endmeeting21:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:32
openstackMeeting ended Thu Feb 26 21:32:46 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-02-26-21.11.html21:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-02-26-21.11.txt21:32
nickchaseyep.  later!21:32
openstackLog:            http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-02-26-21.11.log.html21:32
Sam-I-Amseeeeeeya21:32
nickchasewhy yes, it actually worked!21:33
nickchaselater. :)21:33
Sam-I-Ammagic21:33
ShamailCya?!!!21:33
*** Sam-I-Am has left #openstack-meeting-321:33
*** nickchase has quit IRC21:33
*** Shamail has quit IRC21:34
*** pkoniszewski has joined #openstack-meeting-321:34
*** pkonisze has joined #openstack-meeting-321:41
*** pkoniszewski has quit IRC21:44
*** banix has quit IRC21:46
*** banix has joined #openstack-meeting-321:47
*** Sukhdev has joined #openstack-meeting-321:47
*** markvoelker has quit IRC21:51
*** markvoelker has joined #openstack-meeting-321:51
*** e0ne has quit IRC21:54
*** markvoelker has quit IRC21:56
*** markvoelker has joined #openstack-meeting-321:57
*** e0ne has joined #openstack-meeting-322:05
*** banix has quit IRC22:16
*** VW_ has quit IRC22:16
*** VW_ has joined #openstack-meeting-322:17
*** mrmartin has quit IRC22:17
*** jgrimm is now known as zz_jgrimm22:20
*** hareeshp has quit IRC22:23
*** seizadi has quit IRC22:23
*** yamamoto has joined #openstack-meeting-322:24
*** Yi has quit IRC22:27
*** yamamoto has quit IRC22:28
*** mattgriffin has joined #openstack-meeting-322:32
*** mattgriffin has quit IRC22:38
*** Yi has joined #openstack-meeting-322:38
*** MaxV has joined #openstack-meeting-322:39
*** bpokorny has joined #openstack-meeting-322:39
*** thangp has quit IRC22:40
*** MaxV_ has quit IRC22:41
*** bpokorny_ has quit IRC22:43
*** bpokorny_ has joined #openstack-meeting-322:48
*** bpokorny has quit IRC22:51
*** matrohon has quit IRC22:51
*** thomasem has quit IRC22:51
*** peristeri has quit IRC22:52
*** yapeng has quit IRC22:57
*** pkonisze has quit IRC23:03
*** nelsnelson has quit IRC23:07
*** Sukhdev_ has joined #openstack-meeting-323:08
*** Sukhdev has quit IRC23:09
*** bknudson has quit IRC23:09
*** yamamoto has joined #openstack-meeting-323:17
*** mattfarina has quit IRC23:18
*** s3wong has quit IRC23:30
*** yamamoto has quit IRC23:31
*** TravT|2 has joined #openstack-meeting-323:32
*** s3wong has joined #openstack-meeting-323:32
*** hareeshp has joined #openstack-meeting-323:32
*** yamamoto has joined #openstack-meeting-323:35
*** mwang2_ has joined #openstack-meeting-323:41
*** yamamoto has quit IRC23:42
*** amotoki has joined #openstack-meeting-323:43
*** amotoki has quit IRC23:44
*** mwang2 has quit IRC23:44
*** bpokorny has joined #openstack-meeting-323:49
*** bpokorn__ has joined #openstack-meeting-323:50
*** wojdev has quit IRC23:50
*** bpokorny_ has quit IRC23:52
*** bpokorny has quit IRC23:53
*** MarkAtwood has quit IRC23:55
*** salv-orlando has quit IRC23:57

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