Monday, 2015-03-23

*** VW_ has joined #openstack-meeting-alt00:04
*** VW_ has quit IRC00:05
*** baoli has joined #openstack-meeting-alt00:10
*** baoli has quit IRC00:15
*** markvoelker has joined #openstack-meeting-alt00:17
*** julim has joined #openstack-meeting-alt00:17
*** yamamoto has joined #openstack-meeting-alt00:19
*** VW_ has joined #openstack-meeting-alt00:20
*** markvoelker has quit IRC00:22
*** achanda has quit IRC00:22
*** yamamoto has quit IRC00:24
*** yamamoto has joined #openstack-meeting-alt00:26
*** dane_leblanc_ has joined #openstack-meeting-alt00:26
*** dane_leblanc has quit IRC00:30
*** shwetaap has quit IRC00:32
*** baoli has joined #openstack-meeting-alt00:32
*** emagana has quit IRC00:34
*** overlayer has quit IRC00:36
*** ajmiller__ is now known as ajmiller00:40
*** julim has quit IRC00:53
*** achanda has joined #openstack-meeting-alt00:53
*** amitgandhinz has joined #openstack-meeting-alt00:56
*** amrith is now known as _amrith_00:58
*** sputnik13 has quit IRC01:00
*** sdake has joined #openstack-meeting-alt01:00
*** dims has joined #openstack-meeting-alt01:01
*** dims has quit IRC01:01
*** shaohe_feng has joined #openstack-meeting-alt01:01
*** sdake__ has quit IRC01:04
*** yamamoto has quit IRC01:04
*** Longgeek has joined #openstack-meeting-alt01:08
*** _amrith_ is now known as amrith01:15
*** dims__ has joined #openstack-meeting-alt01:15
*** markvoelker has joined #openstack-meeting-alt01:18
*** esker has joined #openstack-meeting-alt01:23
*** markvoelker has quit IRC01:23
*** yamamoto has joined #openstack-meeting-alt01:28
*** haleyb has quit IRC01:30
*** stevemar has quit IRC01:34
*** VW_ has quit IRC01:35
*** sputnik13 has joined #openstack-meeting-alt01:40
*** oomichi_ has joined #openstack-meeting-alt01:44
*** sputnik13 has quit IRC01:51
*** watanabe_isao has joined #openstack-meeting-alt01:51
*** VW_ has joined #openstack-meeting-alt01:52
*** mestery_ is now known as mestery01:53
*** shaohe_feng has quit IRC01:55
*** sputnik13 has joined #openstack-meeting-alt01:57
*** achanda has quit IRC01:57
*** baoli has quit IRC01:59
*** armax has joined #openstack-meeting-alt02:00
*** VW_ has quit IRC02:03
*** shaohe_feng has joined #openstack-meeting-alt02:03
*** baoli has joined #openstack-meeting-alt02:04
*** armax has quit IRC02:04
*** armax has joined #openstack-meeting-alt02:06
*** armax has quit IRC02:07
*** mtanino has joined #openstack-meeting-alt02:08
*** erkules_ has joined #openstack-meeting-alt02:16
*** sdake__ has joined #openstack-meeting-alt02:18
*** erkules has quit IRC02:18
*** markvoelker has joined #openstack-meeting-alt02:19
*** tkelsey has joined #openstack-meeting-alt02:19
*** shwetaap has joined #openstack-meeting-alt02:21
*** sdake has quit IRC02:22
*** markvoelker has quit IRC02:23
*** tkelsey has quit IRC02:24
*** kaisers has joined #openstack-meeting-alt02:27
*** kaisers1 has quit IRC02:28
*** gongysh has joined #openstack-meeting-alt02:29
*** Poornima has joined #openstack-meeting-alt02:31
*** sankarshan_away is now known as sankarshan_02:40
*** amrith is now known as _amrith_02:52
*** achanda has joined #openstack-meeting-alt02:58
*** bdpayne has quit IRC02:59
*** dims__ has quit IRC03:01
*** achanda has quit IRC03:03
*** VW_ has joined #openstack-meeting-alt03:07
*** sdake has joined #openstack-meeting-alt03:09
*** sdake__ has quit IRC03:12
*** woodster_ has joined #openstack-meeting-alt03:14
*** amitgandhinz has quit IRC03:18
*** VW_ has quit IRC03:23
*** adanin has joined #openstack-meeting-alt03:24
*** coolsvap|afk is now known as coolsvap03:24
*** marrusl has quit IRC03:24
*** Longgeek has quit IRC03:30
*** watanabe_isao has quit IRC03:34
*** kebray has joined #openstack-meeting-alt03:42
*** kebray has quit IRC03:42
*** kebray has joined #openstack-meeting-alt03:43
*** shaohe_feng has quit IRC03:52
*** watanabe_isao has joined #openstack-meeting-alt04:01
*** kebray has quit IRC04:01
*** kebray has joined #openstack-meeting-alt04:02
*** dave-mccowan has quit IRC04:02
*** dims__ has joined #openstack-meeting-alt04:06
*** baoli has quit IRC04:07
*** achanda has joined #openstack-meeting-alt04:08
*** VW_ has joined #openstack-meeting-alt04:09
*** baoli has joined #openstack-meeting-alt04:10
*** stevemar has joined #openstack-meeting-alt04:15
*** baoli has quit IRC04:15
*** esker has quit IRC04:23
*** shaohe_feng has joined #openstack-meeting-alt04:25
*** Longgeek has joined #openstack-meeting-alt04:30
*** achanda has quit IRC04:34
*** noslzzp has joined #openstack-meeting-alt04:35
*** dims__ has quit IRC04:36
*** sdake__ has joined #openstack-meeting-alt04:40
*** sdake has quit IRC04:44
*** VW_ has quit IRC04:44
*** VW_ has joined #openstack-meeting-alt04:45
*** VW_ has quit IRC04:49
*** sdake has joined #openstack-meeting-alt04:51
*** yamahata has joined #openstack-meeting-alt04:54
*** sdake__ has quit IRC04:55
*** ajmiller has quit IRC05:03
*** achanda has joined #openstack-meeting-alt05:08
*** sdake__ has joined #openstack-meeting-alt05:18
*** rushiagr_away is now known as rushiagr05:19
*** sdake has quit IRC05:22
*** achanda has quit IRC05:24
*** achanda has joined #openstack-meeting-alt05:26
*** bdpayne has joined #openstack-meeting-alt05:26
*** sdake__ has quit IRC05:33
*** sdake has joined #openstack-meeting-alt05:34
*** yamahata has quit IRC05:41
*** sushilkm has joined #openstack-meeting-alt05:47
*** sushilkm has left #openstack-meeting-alt05:47
*** i-m-in has joined #openstack-meeting-alt05:48
*** i-m-in has quit IRC05:50
*** sdake has quit IRC05:51
*** adanin has quit IRC05:55
*** SridharG has joined #openstack-meeting-alt06:01
*** kebray has quit IRC06:15
*** nkrinner has joined #openstack-meeting-alt06:17
*** mtanino has quit IRC06:22
*** dims__ has joined #openstack-meeting-alt06:22
*** shwetaap has quit IRC06:24
*** numan has joined #openstack-meeting-alt06:26
*** ajo_ has joined #openstack-meeting-alt06:28
*** rbrady has quit IRC06:28
*** bdpayne has quit IRC06:32
*** jprovazn has joined #openstack-meeting-alt06:33
*** irenab has quit IRC06:36
*** deepakcs has joined #openstack-meeting-alt06:40
*** HeOS has quit IRC06:40
*** stevemar has quit IRC06:48
*** dims__ has quit IRC06:54
*** nshaikh has joined #openstack-meeting-alt06:59
*** sgotliv_ has quit IRC07:01
*** rushiagr is now known as rushiagr_away07:03
*** adanin has joined #openstack-meeting-alt07:08
*** ajo_ is now known as ajo07:10
*** adanin has quit IRC07:10
*** irenab has joined #openstack-meeting-alt07:15
*** bobmel_ has joined #openstack-meeting-alt07:19
*** bobmel_ has quit IRC07:20
*** bobmel_ has joined #openstack-meeting-alt07:20
*** bobmel has quit IRC07:23
*** scheuran has joined #openstack-meeting-alt07:24
*** achanda has quit IRC07:29
*** irenab has quit IRC07:29
*** numan has quit IRC07:30
*** ttrumm has joined #openstack-meeting-alt07:34
*** irenab has joined #openstack-meeting-alt07:34
*** yamahata has joined #openstack-meeting-alt07:36
*** ajo has quit IRC07:42
*** numan has joined #openstack-meeting-alt07:43
*** jtomasek has joined #openstack-meeting-alt07:45
*** mrmartin has joined #openstack-meeting-alt07:49
*** kobis has joined #openstack-meeting-alt07:49
*** woodster_ has quit IRC07:50
*** yamahata has quit IRC07:53
*** numan has quit IRC08:03
*** oomichi_ has quit IRC08:04
*** mrmartin has quit IRC08:05
*** numan has joined #openstack-meeting-alt08:16
*** sergef has joined #openstack-meeting-alt08:16
*** geguileo has joined #openstack-meeting-alt08:18
*** kzaitsev has joined #openstack-meeting-alt08:21
*** sgotliv has joined #openstack-meeting-alt08:21
*** ndipanov has joined #openstack-meeting-alt08:21
*** kzaitsev has quit IRC08:21
*** kzaitsev has joined #openstack-meeting-alt08:21
*** doude has joined #openstack-meeting-alt08:23
*** fzdarsky has joined #openstack-meeting-alt08:23
*** markvoelker has joined #openstack-meeting-alt08:24
*** absubram has quit IRC08:24
*** markvoelker has quit IRC08:28
*** pnavarro has joined #openstack-meeting-alt08:29
*** numan has quit IRC08:29
*** pnavarro has quit IRC08:30
*** tkelsey has joined #openstack-meeting-alt08:31
*** pnavarro has joined #openstack-meeting-alt08:32
*** dims__ has joined #openstack-meeting-alt08:39
*** andreykurilin_ has joined #openstack-meeting-alt08:40
*** numan has joined #openstack-meeting-alt08:44
*** SridharG has quit IRC08:49
*** ajo has joined #openstack-meeting-alt08:52
*** sgotliv has quit IRC08:53
*** watanabe_isao has quit IRC08:53
*** matrohon has joined #openstack-meeting-alt08:53
*** sgotliv has joined #openstack-meeting-alt08:54
*** e0ne has joined #openstack-meeting-alt09:02
*** bobmel has joined #openstack-meeting-alt09:04
*** safchain_ has joined #openstack-meeting-alt09:05
*** bobmel_ has quit IRC09:06
*** e0ne has quit IRC09:08
*** lsmola has joined #openstack-meeting-alt09:10
*** dims__ has quit IRC09:12
*** noslzzp has quit IRC09:14
*** katyafervent is now known as katyafervent_awa09:14
*** erkules_ is now known as erkules09:14
*** erkules has quit IRC09:14
*** erkules has joined #openstack-meeting-alt09:14
*** SridharG has joined #openstack-meeting-alt09:16
*** katyafervent_awa is now known as katyafervent09:17
*** gongysh has quit IRC09:17
*** yamamoto has quit IRC09:17
*** sergef has quit IRC09:17
*** shaohe_feng has quit IRC09:18
*** zz_johnthetubagu is now known as johnthetubaguy09:18
*** HeOS has joined #openstack-meeting-alt09:21
*** markvoelker has joined #openstack-meeting-alt09:24
*** derekh has joined #openstack-meeting-alt09:25
*** numan has quit IRC09:26
*** andreykurilin_ has quit IRC09:26
*** markvoelker has quit IRC09:29
*** gongysh has joined #openstack-meeting-alt09:32
*** kzaitsev has quit IRC09:35
*** kbyrne has joined #openstack-meeting-alt09:35
*** kzaitsev has joined #openstack-meeting-alt09:37
*** sgotliv has quit IRC09:39
*** kzaitsev has quit IRC09:39
*** numan has joined #openstack-meeting-alt09:40
*** dalgaaf has joined #openstack-meeting-alt09:40
*** kzaitsev has joined #openstack-meeting-alt09:40
*** ChrisPriceAB has joined #openstack-meeting-alt09:42
*** kzaitsev has quit IRC09:42
*** kzaitsev has joined #openstack-meeting-alt09:50
*** dims__ has joined #openstack-meeting-alt09:51
*** sgotliv has joined #openstack-meeting-alt09:52
*** kzaitsev has quit IRC09:53
*** yamamoto has joined #openstack-meeting-alt09:53
*** e0ne has joined #openstack-meeting-alt09:54
*** thomnico has joined #openstack-meeting-alt09:56
*** kzaitsev has joined #openstack-meeting-alt09:58
*** ddmitriev has joined #openstack-meeting-alt10:00
*** e0ne is now known as e0ne_10:00
*** _nadya_ has joined #openstack-meeting-alt10:00
*** stamak has joined #openstack-meeting-alt10:04
*** e0ne_ has quit IRC10:05
*** enikanorov_ has quit IRC10:11
*** enikanorov_ has joined #openstack-meeting-alt10:12
*** e0ne has joined #openstack-meeting-alt10:14
*** freerunner has quit IRC10:14
*** freerunner has joined #openstack-meeting-alt10:14
*** _nadya_ has quit IRC10:15
*** gongysh has quit IRC10:21
*** markvoelker has joined #openstack-meeting-alt10:25
*** yamamoto has quit IRC10:27
*** egallen has joined #openstack-meeting-alt10:28
*** yamamoto has joined #openstack-meeting-alt10:28
*** markvoelker has quit IRC10:30
*** ddmitriev has quit IRC10:38
*** shaohe_feng has joined #openstack-meeting-alt10:40
*** ddmitriev has joined #openstack-meeting-alt10:42
*** kzaitsev has quit IRC10:42
*** yamamoto has quit IRC10:43
*** kaisers has left #openstack-meeting-alt10:50
*** jaosorior has joined #openstack-meeting-alt10:53
*** ttrumm has quit IRC10:53
*** bauwser is now known as bauzas11:01
*** kzaitsev has joined #openstack-meeting-alt11:08
*** kzaitsev has quit IRC11:08
*** matrohon has quit IRC11:09
*** e0ne is now known as e0ne_11:10
*** kzaitsev has joined #openstack-meeting-alt11:10
*** coolsvap is now known as coolsvap|afk11:11
*** _amrith_ is now known as amrith11:13
*** e0ne_ is now known as e0ne11:17
*** markvoelker has joined #openstack-meeting-alt11:26
*** jcoufal has joined #openstack-meeting-alt11:27
*** marcusvrn has joined #openstack-meeting-alt11:28
*** mwagner_lap has quit IRC11:30
*** markvoelker has quit IRC11:30
*** shaohe_feng has quit IRC11:33
*** dizquierdo has joined #openstack-meeting-alt11:37
*** _nadya_ has joined #openstack-meeting-alt11:38
*** _nadya_ has quit IRC11:38
*** nshaikh has quit IRC11:39
*** Longgeek has quit IRC11:46
*** markvoelker has joined #openstack-meeting-alt11:46
*** _nadya_ has joined #openstack-meeting-alt11:47
*** _nadya_ has quit IRC11:48
*** ganso_ has joined #openstack-meeting-alt11:51
*** jckasper has joined #openstack-meeting-alt11:52
*** yamamoto_ has joined #openstack-meeting-alt11:53
*** marcusvrn has quit IRC11:53
*** EricGonczer_ has joined #openstack-meeting-alt11:54
*** fzdarsky has quit IRC11:58
*** EricGonczer_ has quit IRC12:02
*** fzdarsky has joined #openstack-meeting-alt12:04
*** e0ne is now known as e0ne_12:05
*** bradjones has quit IRC12:05
*** bradjones has joined #openstack-meeting-alt12:06
*** bradjones has quit IRC12:06
*** bradjones has joined #openstack-meeting-alt12:06
*** marcusvrn has joined #openstack-meeting-alt12:13
*** _nadya_ has joined #openstack-meeting-alt12:13
*** Poornima has quit IRC12:14
*** sreshetnyak has quit IRC12:18
*** jcoufal has quit IRC12:20
*** rbrady has joined #openstack-meeting-alt12:20
*** dave-mccowan has joined #openstack-meeting-alt12:21
*** sreshetnyak has joined #openstack-meeting-alt12:22
*** EricGonczer_ has joined #openstack-meeting-alt12:22
*** brain461 has left #openstack-meeting-alt12:22
*** mwagner_lap has joined #openstack-meeting-alt12:23
*** EricGonczer_ has quit IRC12:24
*** wojdev has joined #openstack-meeting-alt12:28
*** wojdev has quit IRC12:28
*** DaSchab has joined #openstack-meeting-alt12:28
*** e0ne_ has quit IRC12:29
*** DaSchab has quit IRC12:29
*** dims__ has quit IRC12:34
*** wbrothers has joined #openstack-meeting-alt12:34
*** dims__ has joined #openstack-meeting-alt12:34
*** wbrothers is now known as wbrothers-wfh12:35
*** amrith is now known as _amrith_12:35
*** DaSchab has joined #openstack-meeting-alt12:35
*** ChrisPriceAB has quit IRC12:35
*** jcoufal has joined #openstack-meeting-alt12:36
*** DaSchab has quit IRC12:37
*** wbrothers-wfh has quit IRC12:51
*** VW_ has joined #openstack-meeting-alt12:52
*** jecarey has quit IRC12:52
*** dims__ is now known as dims12:52
*** shwetaap has joined #openstack-meeting-alt12:53
*** xyang1 has joined #openstack-meeting-alt12:55
*** tdruiva has joined #openstack-meeting-alt12:57
*** matrohon has joined #openstack-meeting-alt12:57
*** miqui has joined #openstack-meeting-alt12:58
*** dprince has joined #openstack-meeting-alt12:59
*** shwetaap1 has joined #openstack-meeting-alt12:59
*** dave-mccowan has quit IRC13:00
*** dave-mccowan has joined #openstack-meeting-alt13:00
*** noslzzp has joined #openstack-meeting-alt13:00
*** amotoki has quit IRC13:01
*** shwetaap has quit IRC13:02
*** thomnico has quit IRC13:03
*** thomnico has joined #openstack-meeting-alt13:03
*** thomasem has joined #openstack-meeting-alt13:04
*** dane_leblanc_ has quit IRC13:04
*** wbrothers has joined #openstack-meeting-alt13:06
*** amotoki has joined #openstack-meeting-alt13:06
*** wbrothers is now known as wbrothers-wfh13:06
*** baoli has joined #openstack-meeting-alt13:07
*** marrusl has joined #openstack-meeting-alt13:08
*** yamamoto_ has quit IRC13:12
*** thomasem has quit IRC13:12
*** leakypipes has quit IRC13:13
*** thomasem has joined #openstack-meeting-alt13:16
*** sriram1 has joined #openstack-meeting-alt13:16
*** yamamoto_ has joined #openstack-meeting-alt13:19
*** coolsvap|afk is now known as coolsvap13:25
*** kebray has joined #openstack-meeting-alt13:28
*** ljfisher has joined #openstack-meeting-alt13:28
*** numan has quit IRC13:29
*** mattfarina has joined #openstack-meeting-alt13:30
*** shwetaap1 has quit IRC13:31
*** superdan is now known as dansmith13:39
*** woodster_ has joined #openstack-meeting-alt13:42
*** mrmartin has joined #openstack-meeting-alt13:45
*** mattgriffin has joined #openstack-meeting-alt13:45
*** dane_leblanc has joined #openstack-meeting-alt13:46
*** jecarey has joined #openstack-meeting-alt13:48
*** thomnico_ has joined #openstack-meeting-alt13:49
*** thomnico has quit IRC13:49
*** salv-orlando has joined #openstack-meeting-alt13:50
*** shwetaap has joined #openstack-meeting-alt13:50
*** e0ne has joined #openstack-meeting-alt13:52
*** dprince has quit IRC13:52
*** dprince has joined #openstack-meeting-alt13:52
*** balajiiyer has joined #openstack-meeting-alt13:53
*** rprakash has joined #openstack-meeting-alt13:54
*** shwetaap has quit IRC13:55
*** banix has joined #openstack-meeting-alt13:56
*** thangp has joined #openstack-meeting-alt13:56
*** sdake has joined #openstack-meeting-alt13:57
*** esheffield has joined #openstack-meeting-alt13:57
*** armax has joined #openstack-meeting-alt13:58
*** sdake__ has joined #openstack-meeting-alt13:59
*** deepakcs has quit IRC14:00
*** sdake has quit IRC14:01
*** hogepodge has joined #openstack-meeting-alt14:02
*** EricGonczer_ has joined #openstack-meeting-alt14:04
*** prad has joined #openstack-meeting-alt14:04
*** coolsvap is now known as coolsvap|afk14:05
*** _amrith_ is now known as amrith14:06
*** nelsnelson has joined #openstack-meeting-alt14:06
*** julim has joined #openstack-meeting-alt14:07
*** shwetaap has joined #openstack-meeting-alt14:08
*** stevemar has joined #openstack-meeting-alt14:10
*** tdruiva has quit IRC14:10
*** egallen has quit IRC14:11
*** radez_g0n3 is now known as radez14:12
*** zz_jgrimm- is now known as jgrimm14:12
*** yamamoto_ has quit IRC14:12
*** sigmavirus24_awa is now known as sigmavirus2414:16
*** sdake has joined #openstack-meeting-alt14:16
*** absubram has joined #openstack-meeting-alt14:17
*** coolsvap has joined #openstack-meeting-alt14:19
*** sdake__ has quit IRC14:20
*** shwetaap has quit IRC14:20
*** mtanino has joined #openstack-meeting-alt14:21
*** thomnico_ has quit IRC14:22
*** zz_dimtruck is now known as dimtruck14:23
*** balajiiyer has left #openstack-meeting-alt14:25
*** tdruiva has joined #openstack-meeting-alt14:26
*** lpabon has joined #openstack-meeting-alt14:26
*** amitgandhinz has joined #openstack-meeting-alt14:32
*** sdake__ has joined #openstack-meeting-alt14:34
*** sdake__ has quit IRC14:34
*** achanda has joined #openstack-meeting-alt14:34
*** sdake__ has joined #openstack-meeting-alt14:34
*** stamak has quit IRC14:35
*** shaohe_feng has joined #openstack-meeting-alt14:35
*** sdake has quit IRC14:37
*** stamak has joined #openstack-meeting-alt14:38
*** shwetaap has joined #openstack-meeting-alt14:40
*** achanda has quit IRC14:41
*** shaohe_feng has quit IRC14:42
*** shaohe_feng has joined #openstack-meeting-alt14:42
*** sarob has joined #openstack-meeting-alt14:44
*** bnemec has quit IRC14:46
*** MarkAtwood has joined #openstack-meeting-alt14:46
*** sarob has quit IRC14:48
*** bnemec has joined #openstack-meeting-alt14:49
*** georgelorch2 is now known as georgelorch14:49
*** tdruiva has quit IRC14:50
*** nkrinner has quit IRC15:01
*** carl_baldwin has joined #openstack-meeting-alt15:03
*** EricGonczer_ has quit IRC15:03
*** EricGonczer_ has joined #openstack-meeting-alt15:03
*** ChrisPriceAB has joined #openstack-meeting-alt15:06
*** bdpayne has joined #openstack-meeting-alt15:09
*** yamamoto_ has joined #openstack-meeting-alt15:13
*** tsekiyama_ has joined #openstack-meeting-alt15:13
*** AlanClark has joined #openstack-meeting-alt15:15
*** yamamoto_ has quit IRC15:19
*** sputnik13 has quit IRC15:22
*** emagana has joined #openstack-meeting-alt15:23
*** SridharG has left #openstack-meeting-alt15:25
*** sdague has quit IRC15:26
*** stamak has quit IRC15:26
*** bogdando has quit IRC15:26
*** rmoe has quit IRC15:31
*** ajmiller has joined #openstack-meeting-alt15:33
*** bdpayne has quit IRC15:33
*** mattgriffin has quit IRC15:33
*** absubram has quit IRC15:35
*** fnaval has quit IRC15:36
*** sergef has joined #openstack-meeting-alt15:38
*** sushilkm has joined #openstack-meeting-alt15:38
*** sushilkm has left #openstack-meeting-alt15:38
*** yamahata has joined #openstack-meeting-alt15:39
*** hareeshp has joined #openstack-meeting-alt15:40
*** sdague has joined #openstack-meeting-alt15:40
*** tsekiyama_ is now known as tsekiyama15:41
*** jaypipes has joined #openstack-meeting-alt15:42
*** tsekiyama is now known as tsekiyama_15:42
*** mattgriffin has joined #openstack-meeting-alt15:43
*** irenab has quit IRC15:43
*** jprovazn has quit IRC15:44
*** banix has quit IRC15:46
*** rmoe has joined #openstack-meeting-alt15:50
*** tdruiva has joined #openstack-meeting-alt15:51
*** fnaval has joined #openstack-meeting-alt15:53
*** eghobo has joined #openstack-meeting-alt15:53
*** eghobo has quit IRC15:54
*** emagana has quit IRC15:54
*** emagana has joined #openstack-meeting-alt15:55
*** reed has joined #openstack-meeting-alt15:55
*** tdruiva has quit IRC15:56
*** bogdando has joined #openstack-meeting-alt15:57
*** stamak has joined #openstack-meeting-alt15:57
*** wbrothers-wfh has quit IRC15:57
*** emagana has quit IRC15:57
*** emagana has joined #openstack-meeting-alt15:57
*** eghobo has joined #openstack-meeting-alt15:57
*** viktors has joined #openstack-meeting-alt15:57
*** kgiusti has joined #openstack-meeting-alt15:58
*** harlowja_at_home has joined #openstack-meeting-alt15:58
*** emagana has quit IRC15:59
*** emagana has joined #openstack-meeting-alt16:00
dhellmann#startmeeting oslo16:00
dhellmannour agenda:16:00
openstackMeeting started Mon Mar 23 16:00:30 2015 UTC and is due to finish in 60 minutes.  The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
dhellmann#link https://wiki.openstack.org/wiki/Meetings/Oslo16:00
*** openstack changes topic to " (Meeting topic: oslo)"16:00
openstackThe meeting name has been set to 'oslo'16:00
bknudsonlol16:00
dhellmanncourtesy ping for jd__, dims, bnemec, flaper87, harlowja, viktors, rpodolyaka, zzzeek, sileht, kgiusti, dansmith16:00
dhellmanncourtesy ping for redrobot, jungleboyj, zhiyan, therve, amotoki, GheRivero, bknudson, ihrachyshka, jogo, dougwig, sreshetnyak, amrith16:00
kgiustio/16:00
redroboto/16:00
amritho/16:00
*** ihrachyshka has joined #openstack-meeting-alt16:00
dimso/16:00
ihrachyshkao/16:00
e0nehi16:00
harlowja_at_homeyo yo16:01
viktorso/16:01
rpodolyakao/16:01
dansmith\oj16:01
dhellmann#topic Review action items from previous meeting16:01
*** openstack changes topic to "Review action items from previous meeting (Meeting topic: oslo)"16:01
dhellmannjust one item from last week16:01
dhellmann#info dims set up backport of oslo.db fix for after-fork handling of connections DONE oslo.db 1.7.116:01
dhellmannmore on backports later...16:01
dhellmann#topic Red flags for/from liaisons16:01
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"16:01
dhellmannhow are things looking going into the release candidate period?16:02
bknudsonnone from keystone16:02
e0nejungleboyj: are you around?16:02
*** ijw has joined #openstack-meeting-alt16:02
jecareyo/16:02
bnemec\o16:02
e0nei'm with jungleboyj would like to ask about adding hacking checks to projects for logging guidelines16:03
harlowja_at_homedid all the requirements tweaks get merged into the various projects?16:03
ihrachyshkaoslo.messaging kilo release? neutron would like to have one with multitarget patch16:03
ihrachyshkapatch: https://review.openstack.org/16634916:03
jungleboyjo/16:03
jungleboyjI am here now.16:03
dhellmannihrachyshka: we'll be discussing that in a bit16:03
*** eghobo has quit IRC16:03
bknudsonsome of these hacking checks could just as well be unit tests.16:03
ihrachyshkain that way we'll be able to deprecate old namespaces earlier16:03
* stevemar sneaks in and continues to lurk16:03
ihrachyshkaack16:03
jungleboyje0ne: Yeah, we should chat about that.16:03
dimsharlowja_at_home: i tried to +A over the weekend, there may be some stragglers16:03
harlowja_at_homedims, cools16:04
*** ijw has quit IRC16:04
harlowja_at_home^ also i guess for integrating projects; seems like thats underway16:04
*** ijw has joined #openstack-meeting-alt16:04
harlowja_at_homeseems like glance had a brokeness @ https://review.openstack.org/#/c/166796/16:04
e0neimo, it would be graet to have such checks in oslo.log or openstack/hacking to run it for all projects16:04
dhellmanne0ne: I know some projects have written checks like that. It's worth discussing adding them to hacking or oslo.log or something to make them easy to share16:04
e0nedhellmann: +116:04
dhellmanne0ne: but they need to be optional, in case not all projects want to use them16:05
*** tsekiyama_ has quit IRC16:05
jungleboyje0ne: We just pulled a number in from Nova.16:05
*** zzz_pczesno has quit IRC16:05
e0nedhellmann: sure. but makint it only for cinder or nova is not a best way.16:05
dhellmanne0ne: so maybe a mailing list thread is the next step? jogo and mtreinish manage the hacking project under QA now16:05
ihrachyshkahacking project seems to be quite slow to receive changes though16:05
*** zhhuabj has joined #openstack-meeting-alt16:05
dhellmannihrachyshka: that is by design16:06
ihrachyshka:)16:06
e0nedhellmann: ok. lets start disccussion aboit logging hacking checks in openstack-dev ML16:06
e0ne:)16:06
dhellmanne0ne: sounds good, I'll watch for the thread16:06
jungleboyje0ne: +216:06
bknudsonwhat logging check do you want to do?16:06
dhellmannare there any other issues we need to discuss?16:06
* dhellmann notices harlowja_at_home's comment about glance16:06
e0nebknudson: to make logging correspond guidelines16:06
*** xgerman has joined #openstack-meeting-alt16:07
harlowja_at_homedhellmann,  glance comment @ https://review.openstack.org/#/c/166796/  :-P16:07
jungleboyjdhellmann: General issues?16:07
dimsdhellmann: Andreas spotted it, should be under control16:07
e0nedhellmann, jungleboyj:  are you ok if i'ls start thread?16:07
*** tsekiyama has joined #openstack-meeting-alt16:07
*** sergef has quit IRC16:07
jungleboyje0ne: Go for it.16:07
e0neok. i'll do16:08
dhellmannjungleboyj: anything that might be blocking your progress16:08
dhellmannjungleboyj: but I guess really anything :-)16:08
jungleboyjdhellmann: Ok, I just wanted to bring up here:  https://review.openstack.org/16543116:08
dstaneke0ne: i'd love to know more about the logging checks. i've implemented a bunch of stuff about logging for Keystone16:08
jungleboyjThat is the review for trying to move to using the new oslo-config-generator.16:08
*** gyee has joined #openstack-meeting-alt16:09
jungleboyjCinder cores were not super excited by that approach so I have proposed an alternate approach to the mailing list.16:09
jungleboyjAppreciate feedback, especially from Nova and Neutron on that note.16:09
e0nedstanek: i want to get it aotomatic for all patches.16:09
bknudsonmock the log call and make it fail if you don't like the args.16:09
dhellmann#link http://lists.openstack.org/pipermail/openstack-dev/2015-March/thread.html#5955716:10
dhellmannjungleboyj's ML thread on the config generator ^^16:10
*** MarkAtwood has quit IRC16:10
ihrachyshkajungleboyj, ack, I'll check and respond16:11
*** jcoufal has quit IRC16:11
bknudsonwould be nice if you didn't have to import the world to generate the config file.16:11
jungleboyjdhellmann: Thank you.  At this point I am guessing this is going to go out into Liberty.  We shall see though.  I am out the next week but will try to code up whatever is agreed upon as soon as I get back.16:11
bknudsonbut I guess it's easy enough with tox venv.16:11
jungleboyjbknudson: Yeah, the new proposal would reduce that a lot.16:11
dhellmannyeah, it may be late to make the change for kilo, but that's up to the cinder team16:11
bknudsondoesn't have to be perfect to begin with, as long as it works.16:12
jungleboyjbknudson: Agreed.  Want to move in the direction of something that everyone is ok with though.16:12
*** eghobo has joined #openstack-meeting-alt16:13
dhellmannit would be good to put together some advice for projects going through a similar discussion16:13
jungleboyjdhellmann: +216:13
dhellmannthere hasn't been much input on that thread, yet, but maybe this week16:14
dhellmannharlowja_at_home: it looks like that glance patch is failing so it won't merge?16:15
dhellmannharlowja_at_home: something to do with a database migration test16:15
jungleboyjdhellmann: Yeah, hoping maybe while I am out this week people will give more input.16:15
harlowja_at_homedhellmann,  maybe some other glance issue then16:15
jungleboyjIf I don't hear much more I will just try to go forward with what we discussed next week.16:15
dhellmannjungleboyj: ++16:15
dhellmannharlowja_at_home: yeah :-/16:16
dhellmannok, is there anything else we need to raise as an issue?16:16
jungleboyjI am done.  :-)16:16
dimsdhellmann: heartbeat patch, whether or not to ship with kilo16:16
dhellmanndims: I have that listed under ongoing work16:16
dimscode is in oslo.messaging/trunk16:16
* dhellmann failed to update the agenda in the wiki16:17
dimscool thx16:17
*** jcoufal has joined #openstack-meeting-alt16:17
dhellmann#topic Feature freeze16:17
dhellmann#info we should be focusing on bug fixes leading up to the release candidate period16:17
*** openstack changes topic to "Feature freeze (Meeting topic: oslo)"16:17
dhellmann#info remember the incubator is still frozen because we haven't created a stable branch there, yet16:17
dhellmannwe will do that around the time of the other release candidates16:17
dhellmannthe fix to the service module for reloading the config is a good example of something we want to let in16:17
*** bdpayne has joined #openstack-meeting-alt16:18
dims+1 dhellmann16:18
dhellmannwhile harlowja_at_home's patch to add a deprecation warning to a method of the same class is an example of something that needs to wait16:18
*** rprakash has quit IRC16:18
*** pmalik has joined #openstack-meeting-alt16:18
harlowja_at_homefine with me :)16:18
dhellmannharlowja_at_home's patch has 2 +2 so it can land right after the branch is created16:18
*** bpb_ has joined #openstack-meeting-alt16:18
bnemecack16:18
*** yamahata has quit IRC16:19
*** yamahata has joined #openstack-meeting-alt16:19
dhellmann#topic Ongoing work & Review priorities16:19
dhellmann#info we released a fix for the db connection after fork issue as oslo.db 1.7.116:19
*** openstack changes topic to "Ongoing work & Review priorities (Meeting topic: oslo)"16:19
dhellmanndo we have any other fixes we need to backport to the stable/kilo branches of any libraries?16:19
dhellmannmaybe the rabbit heartbeat fix for oslo.messaging?16:19
*** coolsvap has quit IRC16:19
dhellmannihrachyshka proposed https://review.openstack.org/#/c/166349/ but I don't know if that's a good candidate -- it looks like a feature?16:20
dimsdhellmann: oslo.db probably has a couple (there's a LOG for retry)16:21
ihrachyshkadhellmann, yeah, for incremental upgrade. otherwise we're left with RPC namespaces in bad shape for another cycle.16:21
dhellmanndims: good point; rpodolyaka & viktors : can you put together a list of patches that need to be backported for a new release of oslo.db from the stable/kilo branch?16:21
*** gyee has quit IRC16:21
dhellmannihrachyshka: ok, I probably need to read more about the background of that16:22
*** sergef has joined #openstack-meeting-alt16:22
ihrachyshkadhellmann, the bug should give you insight16:22
rpodolyakadhellmann: ok. viktors will put a list of patches16:22
rpodolyaka*and I16:22
dhellmannrpodolyaka, viktors : if you go ahead and submit them for review, we won't need to track a separate list somewhere :-)16:22
rpodolyakadhellmann: true :)16:23
dhellmannihrachyshka: ok, I'll take a look16:23
dims++ to reviews16:23
*** gyee has joined #openstack-meeting-alt16:23
dhellmann#action rpodolyaka and viktors to identify oslo.db patches that need to be backported to stable/kilo16:24
dhellmannsileht: can you do the same for oslo.messaging?16:24
silehtdhellmann, sure16:24
dhellmannsileht: thanks16:24
dhellmann#action sileht to identify oslo.messaging patches that need to be backported to stable/kilo16:24
dhellmanndo we need to look at any of the other libs?16:25
dhellmannWe also have a bunch of specs up for review, and we should start the discussion on those before the summit16:25
*** hareeshp has quit IRC16:25
dhellmann#link https://review.openstack.org/#/q/project:openstack%2Foslo-specs+is:open,n,z16:25
*** pballand has joined #openstack-meeting-alt16:26
*** pmalik has quit IRC16:26
dimsdon't see anything else dhellmann16:26
*** eghobo_ has joined #openstack-meeting-alt16:26
*** pballand has quit IRC16:26
dhellmannyeah, I think we've already found all of the big items16:27
viktorsrpodolyaka, dhellmann: sorry, was afk. Agree with Roman16:27
dhellmannviktors: np, thanks16:27
dhellmannok, that's it for the formal agenda this week16:27
dhellmann#topic open discussion16:27
*** openstack changes topic to "open discussion (Meeting topic: oslo)"16:27
bknudsonstevedore: https://review.openstack.org/#/c/166543/16:27
dhellmannI am going to be on vacation 26-31 March. I don't expect to be checking email during that time.16:28
dhellmanndims volunteered to chair the meeting next week16:28
dhellmannbknudson: nice, I'll put that on my review list16:28
dimshave a good vacation dhellmann!16:28
dhellmanndims: thanks!16:29
*** armax has quit IRC16:29
*** absubram has joined #openstack-meeting-alt16:29
jungleboyjI am also out 3/24 to 3/31 if anyone is looking for me.  I will occasionally check e-mail.16:29
dhellmannjungleboyj: thanks for the heads-up16:29
*** eghobo has quit IRC16:29
bknudsonspring breakers.16:29
jungleboyjWelcome.16:29
* jungleboyj needs vacation! Warm beach, here I come!16:30
jungleboyjbknudson: Indeed.16:30
* dhellmann is headed to dublin, so doesn't expect "warm" to be part of the agenda16:30
dimsjungleboyj: have fun!16:30
jungleboyjdims: Thanks!16:30
harlowja_at_homedublin, nice, sounds like fubn16:31
harlowja_at_homeought to be slightly different weather than georgia ;)16:31
*** armax has joined #openstack-meeting-alt16:31
*** sreshetn1 has joined #openstack-meeting-alt16:31
dhellmannharlowja_at_home: actually, it's cool and wet here right now, too :-)16:31
bknudsonhttp://en.wikipedia.org/wiki/Craic16:31
*** baoli has quit IRC16:31
*** kfarr has joined #openstack-meeting-alt16:31
harlowja_at_homenm, then i guess its the same weather, ha16:31
bnemecIt's cool and white here today.16:31
harlowja_at_homeplease do not use crack16:31
harlowja_at_home* refering to http://en.wikipedia.org/wiki/Craic16:32
jungleboyjdhellmann: Nice!  I would like to visit there some time.16:32
bknudsondon't tell the border agents you're going for the craic16:32
*** baoli has joined #openstack-meeting-alt16:32
dhellmannjungleboyj: we've been looking forward to it16:32
harlowja_at_homebknudson, +2 i second that, lol16:32
*** gordc has joined #openstack-meeting-alt16:32
amrithI've been working with neutron, I need a vacation.16:32
dhellmannheh16:32
dhellmannI think that probably covers it for this week, so let's call the meeting done and spend a few minutes on spec reviews16:33
dhellmannthanks, everyone!16:33
*** eghobo_ has quit IRC16:33
*** harlowja_at_home has quit IRC16:34
jungleboyjdhellmann: Thanks.  Have a great vacation!16:34
*** eghobo has joined #openstack-meeting-alt16:34
dhellmannjungleboyj: you, too!16:34
dhellmann#endmeeting16:34
*** openstack changes topic to ": ML2 Sync and error handling (Task Flow) - revisited (Meeting topic: networking_ml2)"16:34
openstackMeeting ended Mon Mar 23 16:34:46 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2015/oslo.2015-03-23-16.00.html16:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2015/oslo.2015-03-23-16.00.txt16:34
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2015/oslo.2015-03-23-16.00.log.html16:34
jungleboyjThanks!16:34
*** kgiusti has left #openstack-meeting-alt16:35
e0nethanks! see you next week16:35
*** gordc has left #openstack-meeting-alt16:35
*** marun has joined #openstack-meeting-alt16:35
*** kzaitsev has quit IRC16:35
*** kzaitsev has joined #openstack-meeting-alt16:36
*** bdpayne has quit IRC16:37
*** sergef has quit IRC16:37
*** pballand has joined #openstack-meeting-alt16:38
*** kobis has quit IRC16:39
*** xarses has quit IRC16:39
*** yamahata has quit IRC16:41
*** VW__ has joined #openstack-meeting-alt16:41
*** yamahata has joined #openstack-meeting-alt16:41
*** ajo has quit IRC16:42
*** VW_ has quit IRC16:43
*** wbrothers has joined #openstack-meeting-alt16:44
*** reed has quit IRC16:45
*** nelsnelson has quit IRC16:45
*** reed has joined #openstack-meeting-alt16:46
*** bharath has joined #openstack-meeting-alt16:49
*** emagana has quit IRC16:49
*** wbrothers is now known as wbrothers-wfh16:49
*** sushilkm has joined #openstack-meeting-alt16:50
*** irenab has joined #openstack-meeting-alt16:50
*** sushilkm has left #openstack-meeting-alt16:50
*** ihrachyshka has quit IRC16:51
*** n0ano has joined #openstack-meeting-alt16:51
*** n0ano has left #openstack-meeting-alt16:51
*** ddmitriev has quit IRC16:51
*** yamahata has quit IRC16:54
*** yamahata has joined #openstack-meeting-alt16:54
*** emagana has joined #openstack-meeting-alt16:57
*** e0ne is now known as e0ne_16:57
*** ljfisher has quit IRC16:58
*** e0ne_ is now known as e0ne16:58
*** VW__ has quit IRC16:59
*** emagana has quit IRC16:59
*** VW_ has joined #openstack-meeting-alt16:59
*** matrohon has quit IRC17:00
*** bdpayne has joined #openstack-meeting-alt17:00
reedanybody here for the Community Software Services meeting?17:00
mrmartino/17:00
*** emagana has joined #openstack-meeting-alt17:01
*** sarob has joined #openstack-meeting-alt17:01
*** sarob has quit IRC17:01
*** sarob has joined #openstack-meeting-alt17:01
*** mattgriffin has quit IRC17:01
reed#startmeeting community17:01
openstackMeeting started Mon Mar 23 17:01:43 2015 UTC and is due to finish in 60 minutes.  The chair is reed. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: community)"17:01
openstackThe meeting name has been set to 'community'17:01
dizquierdohere17:02
mrmartinhi17:02
*** sgotliv has quit IRC17:02
*** scheuran has quit IRC17:02
reed#link https://wiki.openstack.org/wiki/Community/MeetingAgenda#Agenda_for_March_23.2C_201517:02
*** absubram has quit IRC17:02
mrmartinsorry for the last week's meeting, I was on a plane, and forget to tell17:02
reed#topic Infratization of Activity Board17:02
*** openstack changes topic to "Infratization of Activity Board (Meeting topic: community)"17:02
reedno problem mrmartin, we moved forward via mailing list and in person anyway :)17:02
mrmartinyeah, was awesome17:03
reeddizquierdo, what's the status of https://etherpad.openstack.org/p/activity-infratization-spec?17:03
mrmartinlet's see the activity spec17:03
dizquierdomrmartin, reed I finished a version of the architecture file at https://raw.githubusercontent.com/MetricsGrimoire/puppet-metricsgrimoire/master/architecture.rst17:03
*** atiwari has joined #openstack-meeting-alt17:04
mrmartinok, nice, can you move it to the spec file?17:04
mrmartinor just add a reference link there.17:04
dizquierdook, if that's good enough, I'll do it17:04
reeddizquierdo, does ircanalysis store data in mysql?17:04
reedand mlstats, too17:04
*** pvaneck has joined #openstack-meeting-alt17:04
*** yamahata has quit IRC17:04
dizquierdoreed, yes it does17:04
reedright?17:04
dizquierdoall of the tools indeed17:04
reedok, in the architecture rst file some tools explicitly say "This is later stored in a MySQL database."17:05
reedand mlstats, ircanalysis don't state that17:05
dizquierdook, I'll update that17:05
reedit's a minor bug :)17:05
dizquierdoall of the tools have as output a mysql database17:05
reedbecause the schema later is explicit17:05
*** zhhuabj has quit IRC17:06
reedok17:06
reedthat file is a bit hard to read but it's good enough17:06
reedi'll try to make an image17:06
dizquierdosorry about that, I can try to improve the reading17:06
reednow, the specification17:06
reeddizquierdo, don't worry, the image is the only thing that will make it clearer17:07
reed:)17:07
dizquierdoah ok17:07
*** eghobo has quit IRC17:07
*** banix has joined #openstack-meeting-alt17:07
dizquierdoI started to produce that, but well u_u17:07
reedso, is the draft spec ready to be proposed?17:07
dizquierdoI'd say so17:07
mrmartinso we can move a short one-two lines of description to the components17:08
mrmartinI guess this spec is around 10% ready, the infra would kill us if try to commit that in this form17:08
reed:)17:08
dizquierdooops, ok :)17:08
mrmartinso if the architecture part is ready, need to move forward on, what puppet components we need, what is the proper way of migration17:09
mrmartinlike we did with askbot17:09
mrmartinhow to backup / restore databases, etc.17:09
reedwe don't need any of that, I thin17:09
*** annashen has joined #openstack-meeting-alt17:09
reedwe can start from scratch17:10
reedactually, we have to start from scratch17:10
dizquierdowe should take care with all of the work regarding affiliation matching17:10
mrmartinbut we don't need to move-in the existing data?17:10
reedso, problem description: is that enough?17:10
reedmrmartin, no, we can recreate all of that17:10
mrmartinor the plugin collects that froms scratch?17:10
mrmartinok17:10
mrmartinI got it17:10
*** sushilkm has joined #openstack-meeting-alt17:10
*** sushilkm has left #openstack-meeting-alt17:11
*** mattgriffin has joined #openstack-meeting-alt17:11
mrmartin$17:11
mrmartinsry17:11
*** balajiiyer has joined #openstack-meeting-alt17:11
mrmartin#info move architecture reference to spec17:12
reed#action reed to prepare a visual diagram based on dizquierdo's rst file17:12
reedis Problem description clear enough?17:12
dizquierdooh, with this respect17:13
reedhttps://etherpad.openstack.org/p/activity-infratization-spec ?17:13
dizquierdomrmartin,  did you have the cance to have a look at the vagrant machine?17:13
*** balajiiyer1 has joined #openstack-meeting-alt17:13
dizquierdohttps://github.com/VizGrimoire/VizGrimoireUtils/tree/master/vagrant17:13
reed#link https://raw.githubusercontent.com/MetricsGrimoire/puppet-metricsgrimoire/master/architecture.rst17:13
*** balajiiyer has quit IRC17:13
dizquierdojust to make sure that you understand how that works17:13
mrmartindizquierdo, not yet, but I'll17:13
dizquierdoah ok ok17:13
dizquierdolet me know if you have any issue with this17:13
reeddizquierdo, wait, let's make sure we make progress on the spec first17:13
dizquierdook17:13
dizquierdosorry17:14
mrmartinok, so this vagrant sets up everything using shell scripts?17:14
mrmartinnice work!17:14
*** eghobo has joined #openstack-meeting-alt17:14
dizquierdoyes, that should work in that way :)17:14
mrmartinlooks promising, and definitely can help in puppetization17:15
dizquierdoperfect17:15
dizquierdoyou need to update some config files, but that should be all17:15
*** ljfisher has joined #openstack-meeting-alt17:15
mrmartingreat, I'll allocate some time tomorrow to test it17:15
dizquierdoI'll be around just in case you need some help17:16
reedok, I assume that Problem description is good enough. Let's move on the spec draft :)17:16
reedcheck the Proposed change:17:16
reeddizquierdo, is anything missing from the list of tools?17:16
*** ijw has quit IRC17:17
dizquierdoreed, I don't think so, we're nowadays migrating OpenStack to SortingHat, a new tool to manage identities, but that's all17:17
reedso let's add SortingHat17:17
dizquierdothis is the unique identitites database17:17
*** eghobo has quit IRC17:17
dizquierdook17:17
dizquierdoI'll add that to the rst file17:17
reedoh, wait...17:17
reedright, it'll be needed there too17:18
*** zhhuabj has joined #openstack-meeting-alt17:18
*** sarob_ has joined #openstack-meeting-alt17:18
*** sbalukoff has quit IRC17:18
*** VW__ has joined #openstack-meeting-alt17:18
reedso this part of the draft spec requires more work17:18
reedthe template says: Here is where you cover the change you propose to make in detail. How do you propose to solve this problem?17:18
*** amotoki has quit IRC17:19
reedfor example, we need to write here that we need mysql databases17:19
dizquierdommm having a look at the spec file17:19
reedthe puppet scripts for the various tools is one step, then we need databases (are they on the same machine? would a trove instance be enough?)17:20
*** xarses has joined #openstack-meeting-alt17:20
reedare they all different databases? etc17:20
*** tdruiva has joined #openstack-meeting-alt17:20
*** absubram has joined #openstack-meeting-alt17:21
mrmartinyeap, I suggest to enlist all databases we required, if need more17:21
dizquierdoin the case of grimoire, they are all different databases, but it's enough to have all of them in the same machine17:21
*** VW_ has quit IRC17:21
mrmartinok, if we are going to use trove, we need to pass of required db-s to infra because they need to create it17:21
*** sputnik13 has joined #openstack-meeting-alt17:21
reedand as for scope, I would limit this spec to the collecction of data only17:22
reedI'd avoid going into the data analysis yet17:22
dizquierdoI agree with you17:22
mrmartinok let's move on to Mailing Lists Stats puppet recipes17:23
reed#action reed to describe the phased approach, first the data collection and then the data analysis17:23
*** derekh has quit IRC17:23
reedmrmartin, I would suggest to do that offline, unless you already have questions17:24
mrmartinok, I just like to notice here, that I did a quick review, and it requires refactoring to match the patterns and modules structure of other openstack puppet modules.17:25
dizquierdook, we should probably work on creating them more similar to openstack's17:26
dizquierdomrmartin,  a link to some documentation would be good, or some examples at least :)17:26
mrmartindizquierdo: all of the puppet- repositories at github.com/openstack-infra/17:26
dizquierdogreat, thanks!17:27
mrmartindizquierdo: I can help with that refactoring, because some basic fundamentals is missing here17:27
dizquierdothat would be appreciated17:27
mrmartinlike file resource handling, dependencies, etc.17:27
reed#action dizquierdo to look at other openstack-infra/puppet-* modules and refactor mlstats puppet17:27
*** sarob_ has quit IRC17:27
*** harlowja has joined #openstack-meeting-alt17:27
reedok,we can postpone this task until we have the spec done17:27
*** eghobo has joined #openstack-meeting-alt17:27
mrmartinit's not a problem, that's a normal learning path required for puppet. the basic thing that puppet is handling states instead of processes17:28
reed#info postpone working on the puppet scripts until the spec is done17:28
*** VW__ has quit IRC17:28
*** bdpayne has quit IRC17:28
reedwe have a long way to go before... so let's move to the next topic17:28
reeddizquierdo, what are the issues that you see in database upgrades and stuff?17:28
*** achanda has joined #openstack-meeting-alt17:29
dizquierdoreed, basically issues related to updates of the database schema17:29
reedthose concerns are useful to clarify the spec17:29
dizquierdoand addition or removals of repositories17:29
reedhow do you do them now? sql scripts and configuration changes, right?17:29
*** VW_ has joined #openstack-meeting-alt17:29
dizquierdoupdates of projects to get integrated, incubated, etc17:29
dizquierdothat's it reed17:29
dizquierdosql basically17:29
dizquierdoif it's possible to apply sql scripts17:30
dizquierdothat would be a solution for us17:30
mrmartinyou could check how Drupal or Laravel solving those problems17:30
reedthose can be managed by the puppet recipes17:30
*** carl_baldwin has quit IRC17:30
mrmartinusually there is a tool that can apply the change17:30
reedlike bash is such a tool, right? :)17:30
dizquierdo:)17:30
mrmartinor this tool for python's sqlalchemy: https://alembic.readthedocs.org/en/latest/17:31
mrmartinthe trick here, that those tools storing the schema version somewhere, so it is easy to do schema updates / downgrades17:31
mrmartinso if you like to revert a schema due a failed upgrade, than you can do it easily17:32
dizquierdothat sounds good for sure17:32
*** kzaitsev has quit IRC17:32
mrmartinrequires a bit more preparation from application side, but you win a lot at operation side.17:32
reedso dizquierdo this goes back into how cvsanaly is designed and treats upgrades in general17:32
*** spzala has joined #openstack-meeting-alt17:33
reedIIRC it has sql scripts to create the db and upgrades, and python setup takes care of running thos17:33
reede17:33
*** pmalik has joined #openstack-meeting-alt17:33
dizquierdolet's say that cvsanaly does not care about updates17:33
dizquierdoif there's a new database schema, cvsanaly will start populating the database with such new schema17:33
dizquierdointernal upgrades are typically done through sql scripts17:34
reedusing mysql client?17:34
dizquierdoyes17:34
reedok, so we'll need to add to the spec how those need to be managed17:35
mrmartinwith other projects we used to package those updates next to the app, so the update tool automatically can pick up the new schemas and apply17:35
reedeither by developing a tool, a bash script or something17:36
mrmartinexactly17:36
*** e0ne has quit IRC17:36
dizquierdosounds good, yep17:36
*** amotoki has joined #openstack-meeting-alt17:36
*** amotoki has quit IRC17:36
reed#action dizquierdo to add to the spec the description of database management17:36
*** hareeshp has joined #openstack-meeting-alt17:36
reedI added a NOTE to the spec draft17:37
reednext topic?17:37
dizquierdoseems to be the activity board issues in github17:37
dizquierdobtw, no advances with this respect17:37
dizquierdowe have planned them for this week17:37
reed#topic review pending issues17:37
*** openstack changes topic to "review pending issues (Meeting topic: community)"17:37
reeddizquierdo, ok17:38
*** carl_baldwin has joined #openstack-meeting-alt17:38
*** sreshetn1 has quit IRC17:38
reed#info no progress on github issues about grimoire set, reconvene next week17:38
*** pmalik has quit IRC17:38
*** HeOS has quit IRC17:38
mrmartinok, then let's go on with askbot17:39
reed#topic askbot infratization17:39
*** openstack changes topic to "askbot infratization (Meeting topic: community)"17:39
mrmartinI've added the missing cron jobs: https://review.openstack.org/16688217:39
*** pmalik has joined #openstack-meeting-alt17:39
mrmartinthey are not doing too much, and seems to be that the Chinese issue is a separated one17:39
reed#info reed tested the new system, found it lacking Chinese search indexes17:40
reed#info mrmartin added the missing cron jobs: https://review.openstack.org/16688217:40
mrmartinso I'm looking it, and will work with fungi to find the root of the issue17:40
reed#info the issue with Chinese language search is still being investigated17:40
reed#action mrmartin to keep investigating the root cause of missing Chinese language search17:40
mrmartinactually I'm testing that in Vagrant, as I remember it was working before, but needs a little time to review solr, askbot integration17:40
reedok, so we're blocked until this is solved17:41
mrmartinanyway, if it is done, we can move forward with testing17:41
*** hareeshp has quit IRC17:41
reed#info the migration is on hold until the integration solr/askbot is cleared and Chinese search works17:41
reedso we can skip the following next steps in the migration, we have no date to announce downtime17:42
reedmrmartin, please make askbot your priority this week17:42
mrmartinok, I'm sure we can solve it in this week, there was some magic around the chinese solr analyzers17:42
reedcool17:42
reedI know we're close :)17:43
reedso next topic?17:43
mrmartingroups17:43
reed#topic User Groups portal: review of pending issues17:43
*** openstack changes topic to "User Groups portal: review of pending issues (Meeting topic: community)"17:43
reed#link https://storyboard.openstack.org/#!/project_group/5817:43
mrmartinok, I'm was working with the meetup.com event data exchange issue17:44
*** carl_baldwin has quit IRC17:44
mrmartinit is working on dev, except I found an issue with event location format, and there is a new patch for that: https://review.openstack.org/16691717:44
*** ivar-lazzaro has joined #openstack-meeting-alt17:45
*** ivar-lazzaro has quit IRC17:45
*** pmalik has quit IRC17:45
mrmartinthe root of the problem, that we don't know the exact format how to meetup.com is passing the location, and I already meet with at least 4-5 different internal format17:45
reed#info mrmartin working to add location details to events imported from meetup.com17:45
reedouch17:45
*** padkrish has joined #openstack-meeting-alt17:46
mrmartinthis is the test for different formats: https://github.com/openstack-infra/groups/blob/master/modules/groups/groups_feeds/groups_feeds.test17:46
reedis there a way to simply get the city and the state?17:46
mrmartinso the event list looks better now on dev: https://groups-dev.openstack.org/17:46
mrmartinI need to talk with Jimmy what they are using finally, the xml or the html for parsign17:47
mrmartinparsing17:47
mrmartinbecause the RSS feed not exports the location by default, but I checked what we have there, and Commons provides an iCal exporter too17:47
reedwe may want to export the ical for individual groups17:48
reedbut we can discuss this on the mailing list17:48
mrmartinthat's a good question, because we have ical's actually for groups who are using meetup.com17:49
reedmrmartin, I find it surprising that meetup.com API don't give you simply the city and the state/nation of the event17:49
*** ivar-lazzaro has joined #openstack-meeting-alt17:49
mrmartinI think it was agile17:49
*** yamahata has joined #openstack-meeting-alt17:49
reedwhat is agile?17:50
mrmartinmeetup.com development :D17:50
mrmartincheck this: http://paste.openstack.org/show/195485/17:50
reedah17:50
mrmartinso they are providing a different format for US events17:50
mrmartinand a different one for other countries17:50
mrmartinand event for US events they have at least 3 different representation17:50
reedcrap17:51
mrmartinincluding ADDRESS, CITY, STATE17:51
reedlet's have a look, probably it's not worth pursuing this17:51
mrmartinor ADDRESS, CITY, STATE POCODE17:51
reedwait a second... maybe we can solve this issue in a much simpler way17:51
mrmartinok, I guess the parser is quite nice I wrote, so it is handling that well, just need to watch for missing addresses it cannot parse well, I found only one.17:52
reedthe problem we're trying to solve is that on http://openstack.org/community/events there is no information about the 'place' of the event17:52
reedif the place is the name of the user group, that may be enough17:52
mrmartinexactly, and we had the field that for the Commons by default, but the meetup.com importer was not imported that value well17:52
mrmartinok, this location parser is ready now, I need to accept the patch waiting in the queue, and do a release17:53
reedwell... if the parser is almost done then let's try it17:53
reedok17:53
mrmartindon't throw that out, I spent last week with polishing that :)17:54
reed#info this location parser is ready and only waiting for a release17:54
reedif I knew how hard this was, I would have stopped you :)17:54
*** zehicle has joined #openstack-meeting-alt17:54
mrmartinit was exciting, not hard :D17:54
*** armax has quit IRC17:54
mrmartinanyway17:54
reedexactly, I would have taken the toy off your plate :)17:55
mrmartinit is ready, so I can roll it out, and move forward with other open things17:55
reedok17:55
mrmartinwe have a priority here anyway17:55
reed#action mrmartin to merge the new parser for location and release new groups portal17:55
mrmartinhttps://www.drupal.org/node/245513517:55
mrmartinthis one, is a major security upgrade for Commons modules17:56
reed#info let's watch the exported events feed for broken locations17:56
mrmartinso I need to backport this or upgrade all commons modules to this new version, which is a major jump17:56
*** tonytan4ever has joined #openstack-meeting-alt17:56
reed#info major security upgrade required for Commons modules, mrmartin to investigate whether backport it or upgrade all modules17:57
reedwhat's the cost of upgrading?17:57
*** sushilkm has joined #openstack-meeting-alt17:57
*** sushilkm has left #openstack-meeting-alt17:57
*** achanda has quit IRC17:57
*** _nadya_ has quit IRC17:57
mrmartinwe had some patches that fixed bugs of Commons, I need to check whether those were applied in the newer release17:58
mrmartinor need to refactor them to match the new modules17:58
mrmartinwe have 4-5 patches for commons17:58
reedno more patches :)17:58
mrmartinit is a good opportunity to contrib back if we have some leftovers17:59
reedindeed17:59
mrmartinyeap, commons is patch the core drupal too17:59
mrmartinbut it is trackable well with the drush make file17:59
mrmartinso not a huge deal17:59
reedcan you work on this security fix *and* on askbot  too?17:59
mrmartinyes17:59
*** pmalik has joined #openstack-meeting-alt17:59
reedcan they go in parallel or do you need to set one priority higher?18:00
mrmartinso if the security fix is a not huge deal, I can release it together with the event location patch18:00
mrmartinso I can save some release time here18:00
* reed writes in English sometimes in uber-convoluted ways :)18:00
reedwhat I mean is to understand whether the security issues need to go higher in priority than the askbot18:01
mrmartinwe need a more prior priority18:01
mrmartinI hope both of them can roll-out tomorrow18:01
reedboth which ones?18:01
mrmartinthe askbot and the sec fix18:01
mrmartinbut I guess is sec fix is very important18:01
reeddo the sec fix first18:02
*** igordcard has quit IRC18:02
reed#info reshuffle priorities: apply drupal security fix first and then investigate the askbot solr integration issue18:02
reedok, we need to close the meeting18:02
mrmartinwe are ready anyway18:02
*** stevemar has quit IRC18:02
reedyep, indeed18:02
reed#endmeeting18:03
*** openstack changes topic to ": ML2 Sync and error handling (Task Flow) - revisited (Meeting topic: networking_ml2)"18:03
openstackMeeting ended Mon Mar 23 18:03:09 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/community/2015/community.2015-03-23-17.01.html18:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/community/2015/community.2015-03-23-17.01.txt18:03
reedthanks everyone18:03
openstackLog:            http://eavesdrop.openstack.org/meetings/community/2015/community.2015-03-23-17.01.log.html18:03
dizquierdothanks!18:03
reedthank you dizquierdo, mrmartin18:03
mrmartinthank you guys!18:03
*** stevemar has joined #openstack-meeting-alt18:03
*** armax has joined #openstack-meeting-alt18:04
*** pmalik has quit IRC18:04
*** pmalik has joined #openstack-meeting-alt18:04
*** dane_leblanc has quit IRC18:05
*** pmalik has quit IRC18:06
*** marun has quit IRC18:06
*** pmalik has joined #openstack-meeting-alt18:06
*** sarob has quit IRC18:06
*** ChuckC has quit IRC18:08
*** xarses has quit IRC18:08
*** emagana has quit IRC18:11
*** dane_leblanc has joined #openstack-meeting-alt18:12
*** carl_baldwin has joined #openstack-meeting-alt18:13
*** emagana has joined #openstack-meeting-alt18:13
*** pmalik has quit IRC18:13
*** nelsnelson has joined #openstack-meeting-alt18:13
*** nelsnelson has quit IRC18:13
*** igordcard has joined #openstack-meeting-alt18:14
*** pmalik has joined #openstack-meeting-alt18:14
*** nelsnelson has joined #openstack-meeting-alt18:14
*** achanda has joined #openstack-meeting-alt18:15
*** dizquierdo has quit IRC18:16
*** marun has joined #openstack-meeting-alt18:17
*** emagana has quit IRC18:18
*** harlowja has quit IRC18:18
*** achanda has quit IRC18:19
*** achanda has joined #openstack-meeting-alt18:20
*** xarses has joined #openstack-meeting-alt18:20
*** pmalik has quit IRC18:20
*** pmalik has joined #openstack-meeting-alt18:21
*** harlowja has joined #openstack-meeting-alt18:21
*** safchain_ has quit IRC18:21
*** achanda has quit IRC18:27
*** achanda has joined #openstack-meeting-alt18:28
*** xgerman has quit IRC18:28
*** emagana has joined #openstack-meeting-alt18:28
*** woodster_ has quit IRC18:30
*** sbalukoff has joined #openstack-meeting-alt18:31
*** padkrish has quit IRC18:35
*** ChrisPriceAB has quit IRC18:35
*** padkrish has joined #openstack-meeting-alt18:36
*** wojdev has joined #openstack-meeting-alt18:36
*** padkrish_ has joined #openstack-meeting-alt18:37
*** dave-mccowan has quit IRC18:37
*** padkrish has quit IRC18:40
*** sushilkm has joined #openstack-meeting-alt18:45
*** smillward has joined #openstack-meeting-alt18:45
*** sushilkm has left #openstack-meeting-alt18:45
*** marcusvrn1 has joined #openstack-meeting-alt18:47
*** marcusvrn has quit IRC18:49
*** carl_baldwin has quit IRC18:51
*** catherineD has joined #openstack-meeting-alt18:52
*** tsekiyama is now known as tsekiyama_18:55
*** wojdev has quit IRC18:57
*** vladiskuz__ has joined #openstack-meeting-alt18:57
*** eghobo_ has joined #openstack-meeting-alt18:58
*** Rockyg has joined #openstack-meeting-alt18:58
catherineDRockyg: Hello19:00
*** eghobo has quit IRC19:00
*** padkrish_ has quit IRC19:01
*** pmalik has quit IRC19:01
*** padkrish has joined #openstack-meeting-alt19:01
*** vladiskuz_ has joined #openstack-meeting-alt19:02
*** johnthetubaguy is now known as zz_johnthetubagu19:02
Rockygo/19:02
vladiskuz_0/19:02
zehicleo/19:02
hogepodgeo/19:02
catherineDo/19:02
*** vladiskuz__ has quit IRC19:02
*** tsekiyama_ is now known as tsekiyama19:02
catherineDI guess I will star t the meeting ...19:02
catherineD#startmeeting refstack19:03
openstackMeeting started Mon Mar 23 19:03:00 2015 UTC and is due to finish in 60 minutes.  The chair is catherineD. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: refstack)"19:03
openstackThe meeting name has been set to 'refstack'19:03
pvanecko/19:03
*** sslypushenko_ has joined #openstack-meeting-alt19:03
sslypushenko_o/19:03
*** raginbajin has quit IRC19:04
*** rcleere_away has quit IRC19:04
*** SpamapS has quit IRC19:04
*** SpamapS has joined #openstack-meeting-alt19:04
*** SpamapS has quit IRC19:04
*** SpamapS has joined #openstack-meeting-alt19:04
*** rcleere has joined #openstack-meeting-alt19:04
*** raginbajin has joined #openstack-meeting-alt19:04
*** otherwiseguy has quit IRC19:04
*** zimboboyd has quit IRC19:04
*** mikal has quit IRC19:04
*** netapp has quit IRC19:04
*** nikhil_k has quit IRC19:04
*** heyongli has quit IRC19:04
*** cgoncalves has quit IRC19:04
*** nikhil_k has joined #openstack-meeting-alt19:04
catherineDToday's agenda: 1) recap items agreed last week from f2f, 2) continue discuss the remaining items of the Feb f2f action list.19:04
catherineD   (including OpenID integration item 1.0.1) https://etherpad.openstack.org/p/refstack_f2f_feb_2015 3) pending reviews19:04
catherineD19:04
*** mikal has joined #openstack-meeting-alt19:04
*** otherwiseguy has joined #openstack-meeting-alt19:04
*** zimboboyd has joined #openstack-meeting-alt19:04
*** cgoncalves has joined #openstack-meeting-alt19:04
catherineDany other topics?19:05
*** baoli has quit IRC19:05
*** netapp has joined #openstack-meeting-alt19:05
*** pmalik has joined #openstack-meeting-alt19:05
sslypushenko_Lets start with these topics19:05
catherineDLast week we agreed on the following:19:05
catherineD#agreed Using [refstack] tag for mailing list19:05
zehicleI can give a DefCore update since we are moving docs out of refstack19:06
Rockyg++19:06
*** padkrish has quit IRC19:06
catherineD#agreed For the "uuid issue and refstrack test results json schema" topic, we agree to operate business-as-usual until we     get a new results JSON schema from DefCore19:06
catherineDzehicle: ++19:06
catherineD#agreed Delay vendor implementation (vendor registration, vendor related UI) until after Vancouver (section 1.0.3 of f2f)19:06
catherineD#agreed Only need page 1 and 4, skip page 2 and 3 of the mockup for Vancouver    https://drive.google.com/file/d/0BxvL0emVRKoUVW13TW5BWXg0MXM/view?usp=sharing19:07
zehicleI'd be interested in hearing more from hogepodge about UUID thoughts19:07
catherineDthat is all ...19:07
*** MarkAtwood has joined #openstack-meeting-alt19:07
Rockygdo we have mockups for 1&4?19:08
catherineDFor UUID I opened this bug https://bugs.launchpad.net/tempest/+bug/143370019:09
openstackLaunchpad bug 1433700 in tempest "Multiple test cases associated with same test UUID" [Undecided,In progress] - Assigned to Sergey Slipushenko (sslypushenko)19:09
catherineDsslypushenko_: is woking on the review ...19:09
sslypushenko_catherineD Great thx for that)19:09
catherineDRockyg: same mock up link19:10
catherineD#link https://drive.google.com/file/d/0BxvL0emVRKoUVW13TW5BWXg0MXM/view?usp=sharing19:10
*** marrusl has quit IRC19:11
catherineDhogepodge: your thoughts on UUID ..19:11
RockygcatherineD:  thanks19:11
hogepodge#link longer thoughts here http://lists.openstack.org/pipermail/defcore-committee/2015-March/000660.html19:12
*** HeOS has joined #openstack-meeting-alt19:12
*** marrusl has joined #openstack-meeting-alt19:13
hogepodgeBased on conversations with the openstack-qa team and some others, I think we can work with the idempotent_id and test names to identify functionality testing (the idempotent_id) and the test (the test name)19:13
hogepodgesslypushenko_ has a patch in place to generate unique ids for every function, but I'm not sure qa is going to bite on it.19:13
hogepodge#link https://review.openstack.org/#/c/165921/19:14
sslypushenko_hogepodge Please specify what do you mean on test name?19:14
catherineDhogepodge: by test name you means FQN?19:14
hogepodgefully qualified test name19:14
sslypushenko_full path? or TestCaseName.test_method_name?19:14
hogepodgeWe accomplish the goal of tracking functionality through refactoring with idempoent_id as they stand.19:14
hogepodgefull path19:15
hogepodgewhich is what we're using right now19:15
catherineDhogepodge: using FQN we need to fix to a certain tag or hash ...19:15
catherineDand that is what we try to fix with UUID ..19:15
hogepodgei.e. tempest.api.compute.images.test_list_image_filters.ListImageFiltersTestJSON.test_list_images_filter_by_server_id19:15
*** armax has quit IRC19:15
hogepodgecatherineD: I think that's ok from a defcore standpoint, which is going to be on 6 month cycles.19:16
hogepodgeTwo questions are: can we work with the current state? Will openstack-qa allow us to modify the current state?19:16
RockygActually, no need for UUID if you have hash and FQN19:16
sslypushenko_FQN + idempotent_id sounds really strange...19:16
*** yamamoto_ has joined #openstack-meeting-alt19:16
catherineDRockyg: correct  That is our business-as-usual19:17
hogepodgeRockyg: it's still useful for tracking refactoring19:17
*** sreshetn1 has joined #openstack-meeting-alt19:18
*** pmalik has quit IRC19:18
zehicleI recall that we had an issue when people refactored tests and it was very hard to update the lists19:18
hogepodgeMy feeling from the qa team is that they're happy with the way things are now, so change would be hard (but not impossible)19:18
zehicleQA team use case if different than ours19:18
RockygYeah.  But it becomes part of the defcore process and can be ignore in the testing process itself19:19
catherineDhogepodge: so we are not sovling what we set out with UUID... but I agree that it might help tracking ...19:19
hogepodgezehicle: idempotent_id means you can track where a group of tests went. hash search vs linear search19:19
*** marcusvrn has joined #openstack-meeting-alt19:19
hogepodgeI think there's a strong case to be made that even changing the name of a test makes it a different test. It's a pedantic argument though.19:20
*** bharath has quit IRC19:20
*** bharath has joined #openstack-meeting-alt19:20
zehicleand when the tests move to the projects, there will be MUCH pain19:20
Rockygbut at least with UUID, you can *find* where the test moved to.19:20
*** niclem has joined #openstack-meeting-alt19:21
*** pmalik has joined #openstack-meeting-alt19:21
Rockygzehicle: that's why getting the uuids in before the moves start has been so important.19:21
hogepodgeRockyg it's not that simple, really, because how do you do it? id on parent class and method? Two things to keep track of. generate from id on parent and method, then you can't search the code directly19:21
zehicletest names are human friendly - we just have a habit of wanting them to retain meaning19:21
*** yamamoto_ has quit IRC19:21
zehicleso, people want to tweak them19:21
*** woodster_ has joined #openstack-meeting-alt19:22
zehicleultimately, we'll have to maintain a master test inventory file19:22
hogepodgeDoes tweaking change the meaning? I've been changing a test name in a working tree because I keep finding that without admin I can't to certain things.19:22
*** marcusvrn1 has quit IRC19:22
zehicletweaking may or may not change the meaning BUT it does make it a new ID19:23
hogepodgeright now the fallout is we track back to an idempotent_id and you may have to choose from a small subset of tests. i.e. ipv4 vs ipv619:23
zehicleso that will create work for RefStack & DefCore (at least for the tests that we are tracking)19:23
*** rushiagr_away is now known as rushiagr19:23
sslypushenko_zehicle Test inventory file can easily solve problem with readibility19:23
zehiclesslypushenko_, yes, I'19:23
zehicleve been expecting that to be needed - there's a patch for it19:23
hogepodgethe work is so greatly reduced with what we have. It's not a total failure, we already get a lot.19:23
*** kfarr has quit IRC19:23
*** bharath has quit IRC19:24
*** bharath has joined #openstack-meeting-alt19:24
*** VW_ has quit IRC19:24
catherineDso where do we stand here ... last week we agreed that o operate business-as-usual until we get a new results JSON schema from DefCore19:24
hogepodgeMy suggestion for fixing this would be to tag classes also. Then the tuple capture all of the information about the class and the function, and is searchable directly in source.19:24
sslypushenko_I guess better what we can do - It is to find a usecase where current implementation is not enough.19:25
sslypushenko_I may help as to force idea about improvement in qa team19:26
Rockygsslypushenko_ ++ ;-)19:26
hogepodgeLet's say that in 2015.3 and 2015.[45] we work with what we have and plan for 2015.9 when there's time available.19:27
hogepodge(that's just my suggestion)19:27
catherineDhogepodge: ++19:27
RockygSo, if the class can change without the test being rev'ed then we aren't tracking the tests properly19:27
zehicleit could be that we have to wait to resolve until f2f at the summit19:28
catherineDhogepodge: what does work with what we have?19:28
hogepodgeThat's not too far away. I want to restate that what we have is really good, and I think is going to make life easier for everyone as revs start up.19:28
Rockyghogpodge:  ok19:29
*** carl_baldwin has joined #openstack-meeting-alt19:29
Rockygzehicle: at the summit, we have to have concrete examples to get our points across19:29
hogepodgeI also understand the shortcoming, and that it's not what we originally wanted. That was in part due to my lack of complete understanding on how tempest works.19:29
zehicleok, so we use test names for that19:30
hogepodgeI think that test names will always have to be part of the capabilities list anyway. There has to be a human readable component.19:30
hogepodgeYou'll always be able to find where a test went to if it moves from what we have, and we didn't have that before.19:31
zehiclehogepodge, yes.  I was assuming that inventory file would be the item that handled that19:31
*** VW_ has joined #openstack-meeting-alt19:31
hogepodgezehicle: it may be a thing to talk about in the defcore meeting. My feeling is that not having a human readable component in the capabilities.json file would be a crippling mistake19:32
*** prad has quit IRC19:32
zehiclehogepodge, I agree19:32
zehiclethat's why I was against the long UUIDs19:33
hogepodgezehicle: I don't see any conflict between storing tests as tuples. Or using the fully expanded test names (that include tags and ids now)19:33
catherineDso from refstack point of view we are still agree as we did last week ...we agree to operate business-as-usual until DefCore decide on schema for test ...19:34
zehiclehogepodge, in an inventory file, yes19:34
*** rushiagr is now known as rushiagr_away19:34
zehicleIMHO it's risky to make the capabilites file too complex19:34
*** balajiiyer1 has left #openstack-meeting-alt19:34
zehicleyou run the risk of someone missing something and it breaking the file19:34
zehiclemaybe that's over blown and I'm just a DB admin at heart19:35
zehicleand want to normalize everything19:35
*** sarob has joined #openstack-meeting-alt19:35
hogepodgezehicle: I trust your experience.19:36
hogepodgezehicle: Maybe I need to make another trip to Austin next month and we can chat about these files f2f. ;-)19:36
zehiclealways happy to have you in town!19:36
RockygJeez, if you were going to do it, you should have done it during SXSW19:37
zehiclelol, except I was not here19:37
catherineDTime to move to the next topic?19:38
Rockyg++19:38
*** armax has joined #openstack-meeting-alt19:38
*** VW_ has quit IRC19:39
catherineD#topic 2) continue discuss the remaining items of the Feb f2f action list. (including OpenID integration item 1.0.1)19:39
*** openstack changes topic to "2) continue discuss the remaining items of the Feb f2f action list. (including OpenID integration item 1.0.1) (Meeting topic: refstack)"19:39
catherineD#link  https://etherpad.openstack.org/p/refstack_f2f_feb_201519:39
*** annashen has quit IRC19:39
catherineDsection 1.0.1 sslypushenko_: was doing some investigation19:40
sslypushenko_Yep... I have disscussion with Vlad and Chris19:40
catherineDsection 1.0.1 in the "action items for vancouver" at the bottom of https://etherpad.openstack.org/p/refstack_f2f_feb_201519:41
sslypushenko_Final decisions is that in term of auth we should follow common way, which used in openstac gerrit for example19:41
sslypushenko_Vlad already have started development19:42
*** annashen has joined #openstack-meeting-alt19:42
sslypushenko_I will post in refstack channel link on workflow diagram19:42
*** ajo has joined #openstack-meeting-alt19:43
catherineDsslypushenko_: thx19:43
sslypushenko_I hope it will make things clear19:43
*** fzdarsky has quit IRC19:43
vladiskuz_catherineD: It's first step https://review.openstack.org/#/c/166247/19:43
*** marun has quit IRC19:43
*** padkrish has joined #openstack-meeting-alt19:44
sslypushenko_In short, We are going to use OpenstackId for web UI auth and RSA key pairs  for CLI tool19:44
catherineDsslypushenko_: vladiskuz_: thx .. Let's move to section 3.2.1.119:45
sslypushenko_Like gerrit or github19:45
catherineDwe need additional API to support page 4 of the mockup19:45
catherineDI have submited a review https://review.openstack.org/#/c/166357/19:45
catherineDcould you all review ...?19:46
catherineDwe really need this API ...19:46
*** sdake has joined #openstack-meeting-alt19:46
sslypushenko_Sure thing)19:46
*** MarkAtwood has quit IRC19:46
*** MarkAtwood has joined #openstack-meeting-alt19:46
*** heyongli has joined #openstack-meeting-alt19:46
sslypushenko_Vlad already pushed on revied basic version of retrival API19:47
*** hyakuhei has joined #openstack-meeting-alt19:47
sslypushenko_It is possible to add some filters to it19:47
catherineDcurrently, after user collects the test results from refstack-client ... they want to look at the results ... and it is very cumbersome now ...19:47
catherineDthat is the paint that jlk experiences....19:48
sslypushenko_https://review.openstack.org/#/c/166247/19:48
sslypushenko_It is our first step on that way19:49
*** sdake__ has quit IRC19:49
*** sgotliv has joined #openstack-meeting-alt19:49
catherineDsslypushenko_: I need to discuss with vladiskuz_: in detail between https://review.openstack.org/#/c/166247/ and https://review.openstack.org/#/c/166357/ in #refstack after this meeting ..19:50
vladiskuz_catherineD: np ;)19:50
catherineDthat is all the topic I have today ...19:50
*** chellygel has joined #openstack-meeting-alt19:51
catherineDzehicle: could you give defcore update?19:51
zehicleyy19:51
zehicleDefCore's been moving REALLY fast latest19:51
zehiclewe've got the 2015.03 spec landed with the template for the 2015.next in also19:52
zehicleprocess draft should hit soon too19:52
zehiclethat means we're on track for the summit19:52
zehicleall of that in the openstack/defcore repo.  so we'll start to pull down the refstack/defcore folder19:52
zehicleit should be gone by the summit19:52
hogepodgein my mind the biggest road block is fixing tests that rely on neutron. Going to nyc next week to try and tie a ribbon on that.19:53
zehiclethe 2015.03.json file replaces the capabilities/sections files that we used in the past19:53
zehicleformat is very similar19:53
zehiclehogepodge, any idea on that keystone test?19:53
catherineDzehicle: will refstack be used to present results to users?19:53
zehicleso we can include the capability19:53
hogepodgezehicle: in progress19:54
zehicleit's not in the requirements19:54
* morganfainberg feels a disturbance in Freenode...19:54
zehiclebut that is my expectation19:54
hogepodge#link https://review.openstack.org/#/c/166327/19:54
*** marun has joined #openstack-meeting-alt19:54
hogepodgev2 is done, working on v319:54
catherineDwhat we found that with the capability file in defcore .. how can refstack ensure that refstack will always use the latest capability file?19:54
*** rellerreller has joined #openstack-meeting-alt19:55
zehiclethe process is being written to not create a lot of implementation specifics unless we need to make it so19:55
*** dave-mccowan has joined #openstack-meeting-alt19:55
hogepodgecatherineD: refstack is going to need versioned codecs I think, at least for this year19:55
catherineDdo we need to fetch the capabilityf file each time refstack render result ..19:55
zehiclegood question, would it help if we added an "active guidelines" file w/ the right pointers?19:56
zehiclea simple JSON list w/ all the specs and their status19:56
zehicle?19:56
zehiclethey are designed to sort nicely19:56
catherineDI am concern more on the rabpid changing in defcore capability and refstack may miss it ...19:56
zehicleso you could also just grab the alpha list max19:57
zehicledefcore and "rapid change" should not go together19:57
*** arunkant has joined #openstack-meeting-alt19:57
*** sarob has quit IRC19:57
catherineDI will log this for our next week discussion ..since we are about out of time now19:58
*** kfarr has joined #openstack-meeting-alt19:59
catherineDsslypushenko_: vladiskuz_: Let's discuss the reviews in #refstack ...19:59
vladiskuz_catherineD: Let's go19:59
catherineDneed to end meeting now ... thank you all!19:59
*** elmiko has joined #openstack-meeting-alt19:59
catherineD#endmeeting19:59
*** openstack changes topic to ": ML2 Sync and error handling (Task Flow) - revisited (Meeting topic: networking_ml2)"19:59
openstackMeeting ended Mon Mar 23 19:59:42 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2015/refstack.2015-03-23-19.03.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2015/refstack.2015-03-23-19.03.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2015/refstack.2015-03-23-19.03.log.html19:59
redrobot#startmeeting barbican19:59
openstackMeeting started Mon Mar 23 19:59:54 2015 UTC and is due to finish in 60 minutes.  The chair is redrobot. Information about MeetBot at http://wiki.debian.org/MeetBot.19:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:59
*** openstack changes topic to " (Meeting topic: barbican)"19:59
openstackThe meeting name has been set to 'barbican'19:59
*** igueths has joined #openstack-meeting-alt20:00
redrobot#topic Roll Call20:00
*** openstack changes topic to "Roll Call (Meeting topic: barbican)"20:00
kfarro/20:00
jvrbanac_o/20:00
rellerrellero/20:00
dave-mccowano/20:00
iguethso/20:00
elmikoo/20:00
tkelseyo/20:00
jaosorioro/20:00
chellygelヽ( ̄д ̄)ノ20:00
redrobotlots of barbicaneers here today20:01
redrobot#topic Action Items20:01
*** openstack changes topic to "Action Items (Meeting topic: barbican)"20:01
*** fern__ has joined #openstack-meeting-alt20:01
*** jrichli has joined #openstack-meeting-alt20:01
redrobotfirst, we had an update to oslo_log in Castellan by jaosorior20:01
elmikoyay20:02
redrobotwhich looks like it's already merged20:02
arunkanto/20:02
redrobotthanks for that jaosorior20:02
jaosoriorredrobot: no prob20:02
redrobot#link http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-03-16-20.01.html20:02
redrobot^^ link for action items, btw20:02
redrobotthe second item was that I was going to reach out to tsv about quotas20:03
redrobotbuuuuut I totally dropped the ball on that20:03
redrobotin any case20:03
redrobotI did bump the Blueprint to Liberty20:03
*** matrohon has joined #openstack-meeting-alt20:03
redrobotsince we haven't seen tsv in a few weeks.20:03
redrobot#action redrobot to reach out to tsv about quota BP20:03
redrobotI'll definitely reach out to him this week.20:04
redrobotmoving on...20:04
redrobot#topic Kilo-320:04
*** openstack changes topic to "Kilo-3 (Meeting topic: barbican)"20:04
redrobotKilo-3 was released last week20:04
redrobot#link https://launchpad.net/barbican/+milestone/kilo-320:04
redrobotthanks everyone for all the contributions to the project!20:04
*** marcusvrn has quit IRC20:04
redrobotunfortunately CA stuff isn't quite fully baked, but we'll get it fixed soon20:04
*** jgrimm is now known as zz_jgrimm20:05
*** catherineD has quit IRC20:05
redrobotthe next milestone is going to be Release Candidate 120:05
redrobot#link https://launchpad.net/barbican/+milestone/kilo-rc120:05
redrobotwe're in feature freeze, so no blueprints will be added to the release, only the ones that have FFE status that are already listed there.20:06
redrobotFFE = Feature Freeze Exception20:06
*** toph has joined #openstack-meeting-alt20:06
*** VW_ has joined #openstack-meeting-alt20:06
*** ljfisher_ has joined #openstack-meeting-alt20:07
redrobotany questions about Kilo-3 or RC-1 ?20:07
arunkantFor per secret policy change which is in RC1 list, I am waiting for code review comments. I have some comments on part 1. Will be helpful to have some comments on part 2/3/420:07
redrobot#info we need more reviews of the blueprints in FFE20:08
*** jhfeng has joined #openstack-meeting-alt20:08
redrobotok, moving on20:08
redrobot#topic ACL User storage, csv vs table20:08
*** openstack changes topic to "ACL User storage, csv vs table (Meeting topic: barbican)"20:08
redrobot#link https://review.openstack.org/#/c/164334/20:09
arunkantredrobot, added this as one of comment mentioned to get consensus around this.20:09
redrobotthere were a few comments in the review regarding the data structure used to store the users that are added via the per-user ACL20:09
*** ljfisher has quit IRC20:09
redrobotI was a bit concerned that we're storing all users that were granted access in a comma separated list20:10
redrobotmy concern was mainly at the limit it imposes by storing every user id in a single column.20:10
redrobotby arunkant's calcutaions it would be ~ 1000 user ids20:11
*** ljfisher has joined #openstack-meeting-alt20:11
redrobotthe alternative would be to add a separate table to hold secret_id -> user_id mapping, and join on that table when doing the ACL check20:11
arunkantThe field type is text field which is similar to mysql CLOB field which can store 64 kilobytes..20:11
redrobotyeah, the goal is to try to reach consensus on the best approach for the ACL list storage20:12
rellerrellerWhat is the resistance for not using a table? Or is there any?20:12
*** ljfisher_ has quit IRC20:12
redrobotrellerreller there is some concern by arunkant  about the performance implication of having to join tables for every secret access.20:12
arunkantHaving a separate table requires sql join. And all of the lookups are driven by secret id or container id. This lookup is done as policy enforcement logic so will impact most of barbican requests.20:13
rellerrellerWill the user's access control be checked on every request?20:14
*** andreykurilin_ has joined #openstack-meeting-alt20:15
rellerrellerWhat is the cost of SQL join vs split and rebuild strings?20:15
redrobotI would think that we would only check the per-user ACL after failing the typical Project check ?20:15
arunkantYes..eventually when ACL operation are checked for write, delete operations...Currently its only for read secret and container20:15
rellerrellerMy vote is for table20:16
arunkantAlso there is no benefit of having user ids as separate columns..as there are no queries done specifically.20:16
rellerrellerarunkant what do you mean exactly?20:17
arunkantJust to be clear..this will means two tables..one for secret and one for container users.20:17
redrobotI think it could be done with one table that maps ResourceID to UserID ?20:17
*** annashen has quit IRC20:18
*** annashen has joined #openstack-meeting-alt20:18
arunkantI meant lookup is always done for secret id or container id and then related acl record is looked. There are no lookup done only by users.20:18
rellerrellerDo you mean there is no query that asks does this user have permission to this secret?20:19
*** andreykurilin_ has quit IRC20:19
*** andreykurilin__ has joined #openstack-meeting-alt20:19
*** VW_ has quit IRC20:20
arunkantIts always looked up by secret id first..not directly give me all acls for this users?20:20
*** alee has joined #openstack-meeting-alt20:21
*** e0ne has joined #openstack-meeting-alt20:21
*** ljfisher_ has joined #openstack-meeting-alt20:21
*** VW_ has joined #openstack-meeting-alt20:22
arunkantI means queries are always looked up by secret and container id and then narrowed down to what ACL operation and the users are there for that secret or container20:22
*** crc32 has joined #openstack-meeting-alt20:22
*** crc32 has quit IRC20:23
*** ljfisher has quit IRC20:23
*** ljfisher_ is now known as ljfisher20:23
redrobotI'm not sure I understand what the lookup argument against a separate table is?20:23
redrobotsure we can craft a query that will produce the data we need20:24
redrobotanyone else care to weigh in?20:24
rellerrellerI think one of the arguments for the table is that you can do other queries easily, like find out which secrets a user has access to based upon the ACL.20:24
redrobotbueller?20:24
jaosoriorI think arunkant's argument against the table-based solution is the performance20:25
*** pnavarro is now known as pnavarro|off20:25
rellerrellerI'm not sure that really matters to me.20:25
aleesorry -- got here late -- whats the issue?20:25
*** tonytan4ever has quit IRC20:25
jaosoriorrellerreller: depends on the usage for barbican. If we are going to get a ton of requests, and have to do joins every single time, then it might get painful. But I'm not really sure how much it really affects20:25
arunkantYes..you can but in this case, it may not be that useful as lookup criteria has secret id. Anyway..the downside is performance as it will impact all of barbican operations20:26
redrobotalee for per-user-acl, data storage, csv list of IDs, vs a join table where we map resource to users20:26
rellerrellerI'm not convinced that join will have that much impact. If it does then we should examine other areas of DB.20:27
aleeredrobot, arunkant and we think a join table will be more performant?20:27
*** amrith is now known as _amrith_20:27
*** banix has quit IRC20:27
redrobotalee, rellerreller and I would prefer a table.  It does not impose an arbitrary limit to the # of ids (the width of the column), and it can be useful in other operations20:28
rellerrellerjcoffman has phd in DB. We can get him online today or tomorrow and ask him.20:28
redrobotalee, arunkant is concerned about the performance implications20:28
jvrbanac+1 about getting a db expert's opinion20:28
arunkantIts and additional call to get users from a separate table instead of reading it from one column within ACL table20:28
arunkants/and additiona/an additional20:29
*** ndipanov has quit IRC20:29
jaosoriorrellerreller: +120:29
redrobotarunkant yes, this is true, but it would only happen when the user's project fails to grant access20:29
redrobot#action rellerreller to check with jcoffman about per-user-acl performance concern20:30
arunkantNo...it will happen as part of getting data ready for policy enforcement..so the needed queries will be done and then passed to policy logic20:30
jaosoriorredrobot: I thought the ACL would have presedence over the project20:30
aleeredrobot, arunkant - ok I dont really have a preference.  when the spec was written, it was written from the point of view of getting something that made sense.  I do worry about optimizing before we have any real knowledge that the performance implications20:30
aleeand yeah - acl takes precedences over project.20:30
rellerrellerI just called him.20:30
rellerrellerHe will online in a few seconds.20:31
*** joel-coffman has joined #openstack-meeting-alt20:31
redrobotjaosorior it does from a functional pov, in the impl, I think we would want to check the project-level access first, since this is the normal workflow for all of openstack, and only if the project-level access fails, then we would query the user-level acl20:31
*** fnaval has quit IRC20:31
*** fnaval has joined #openstack-meeting-alt20:32
rellerrellerjoel-coffman There is an outstanding question on database. It involves CSV in a column vs having a mapping table.20:32
joel-coffmanokay20:32
rellerrellerBasically we are mapping secrets to users for access control. Proposal 1) Have a column of CSV (i.e. "user1,user2,user3"20:32
joel-coffmansorry to be joining late20:32
aleeredrobot, no - thats done through the policy enforcement.  we read any acls if they exist and pass to the policy layer.  the policy layer specifies access if project or acl.20:32
arunkantredrobot, data needed for policy enforcement is queried first and then passed to enforcement logic. So queries gathering that are going to execute first20:33
rellerrellerProposal 2) Create a new tables with map from secret ID to user ID20:33
aleeredrobot, we're not trying to access policy layer twice.20:33
rellerrellerjoel-coffman Those are the two options. CSV vs Table. What do you think?20:34
joel-coffmanA separate table is definitely the preferred approach from a database consistency and normalization perspective20:34
redrobotalee arunkant I stand corrected.20:35
arunkantThere is no query which are just going to query users table...and this will only have two columns (secret id , userid)20:35
*** ljfisher_ has joined #openstack-meeting-alt20:35
redrobotarunkant but we could either modify the query, or add a new query?20:35
arunkantBut it seems like case of too much normalization as it does not have any other data..20:36
redrobot  joel-coffman  +1 thanks20:36
joel-coffmanCSV would almost certainly entail more implementation effort and introduces the possibility of update anomalies, etc. that databases are designed to prevent20:36
*** crc32 has joined #openstack-meeting-alt20:36
jaosoriorjoel-coffman: Do you think it will affect performance in a meaninful manner?20:36
joel-coffmanThe amount of data shouldn't be an issue...20:36
*** fzdarsky has joined #openstack-meeting-alt20:37
joel-coffmanA separate table is the typical means of expressing a many-to-many relationship20:37
*** ljfisher has quit IRC20:37
*** andreykurilin__ has quit IRC20:37
*** andreykurilin_ has joined #openstack-meeting-alt20:37
jaosoriorjoel-coffman: alright. +1 for the separate table on my side20:37
joel-coffmanjaosorior: can you give me an example query or operation that requires the information20:37
arunkantSo here its going to be one-to-many relationship. And we will need separate table for container as well20:38
aleejoel-coffman, just to be clear - what we have here is a table of acls -- each entry contains secret_id/container_id, operation and a list of users.20:38
aleewe're talking about replacing the list of users with references to another table20:39
aleeso I'm guessing the other table will have something like "acl.id" and userid20:39
*** haleyb has joined #openstack-meeting-alt20:39
aleeand we'd do a query to get all the userids associated with an acl.20:39
*** ljfisher has joined #openstack-meeting-alt20:40
aleeseems like there are more db queries / db work for an extra table20:40
joel-coffmanalee: what will you do with the user ids?20:40
redrobotcompare it to an incoming id20:40
joel-coffmanwill you also need any user information?20:40
aleethey are passed to the policy enforcement layer20:41
joel-coffmanokay20:41
redrobotso the query could be smarter with a table...20:41
aleeno20:41
*** ljfisher_ has quit IRC20:41
*** kzaitsev has joined #openstack-meeting-alt20:41
*** hyakuhei has quit IRC20:41
joel-coffmanso a separate table should be much faster20:41
* redrobot is starting to think he needs to revisit all the policy stuff20:41
joel-coffmanindex both the ACL id and the user id20:41
*** tonytan4ever has joined #openstack-meeting-alt20:42
arunkantjoel-coffman, No. It will be queried by secret_id and then we get linked users id based on acl.id20:42
*** vladiskuz_ has quit IRC20:42
joel-coffmansorry, my mistake20:42
aleearunkant, right - I think he meant that the second table will be linked by acl.id?20:43
joel-coffmanindex *secret id* and user id20:43
*** kzaitsev has quit IRC20:43
arunkantjoel-coffman, there are no other user attributes. just user ids.20:43
*** ljfisher_ has joined #openstack-meeting-alt20:43
aleeeither way - if its going to be much faster to have a separate table - then +1 for me20:43
joel-coffmandatabase can optimize the lookup based on the indexes => zero implementation effort20:43
joel-coffmanparsing the CSV for comparison is linear in the number of CSV entries :-(20:44
*** ljfisher has quit IRC20:44
*** ljfisher_ is now known as ljfisher20:44
joel-coffmanplus you also get some other advantages like revoking all ACLs for a particular user20:45
*** tdruiva has quit IRC20:45
arunkantIts an additional lookup..so not sure if it can be faster. We just need to think that this is additional query done for barbican requests..20:46
rellerrellerI like that additional feature20:46
joel-coffmanwhich only requires lookups based on the user id index instead of reading every ACL entry20:46
*** mwagner_lap has quit IRC20:47
rellerrellerjoel-coffman arunkant is talking about using ORM to get the secret object.20:47
*** jaypipes has quit IRC20:47
*** mrmartin has quit IRC20:47
rellerrellerWe call get secret and that has eager fetch to retrieve all of its properties, including the acl.20:47
*** Rockyg has quit IRC20:47
arunkantjoel-coffman: yes..that will be benefit if there is use case like that.20:48
rellerrellerI think he is talking about that instead of issuing a DB query to say, "Does this user have access to this secret."20:48
rellerrellerI think revocation is a plausible use case. I think being notified of a bad user and revoking everything sounds like a good use case.20:48
*** lpabon has quit IRC20:49
*** vipuls is now known as vipul20:49
*** padkrish has quit IRC20:49
redrobotrellerreller +1  I think in the long run a separate table will be much more useful20:49
joel-coffmanarunkant: the overhead of a single query shouldn't be significant20:50
*** padkrish has joined #openstack-meeting-alt20:50
*** MarkAtwood has quit IRC20:50
joel-coffman(would be interested to know if that's *not* the case, particularly as the database scales)20:50
joel-coffmanredrobot: +1 the risk of a few milliseconds for an additional query is usually well-worth the price given the advantages20:51
redrobotwe're running out of time for the day20:52
redrobotbut I think most of us are leaning towards having a separate table20:52
arunkantOkay. So if consensus is too have another table I will add that. So there will be 2 new tables.20:52
*** jaypipes has joined #openstack-meeting-alt20:52
arunkants/too/to20:52
*** MarkAtwood has joined #openstack-meeting-alt20:53
redrobot#agreed we'll use a separate table to track individual user_ids for per-user-policy20:53
redrobotarunkant I don't think there's a benefit to combining into a single table?  Two tables should be fine.20:54
*** padkrish has quit IRC20:54
* redrobot debates wether we can answer Castellan questions in 5 minutes20:54
redrobot#topic Castellan Initial Release20:55
*** openstack changes topic to "Castellan Initial Release (Meeting topic: barbican)"20:55
*** baoli has joined #openstack-meeting-alt20:55
arunkantredrobot, yes..so one table for container and second one for secret users per operation.20:55
redrobotI have two outstanding patches that I would like to see make it into the initial release20:55
redrobot#link https://review.openstack.org/#/q/status:open+project:openstack/castellan,n,z20:55
redrobotkfarr20:55
kfarrThanks redrobot20:56
redrobotto answer your question, the Castellan project has its own Launchpad20:56
*** fesp has joined #openstack-meeting-alt20:56
*** kzaitsev has joined #openstack-meeting-alt20:56
redrobot#link20:56
redrobot#link https://launchpad.net/castellan20:56
kfarrredrobot, what about the bug tracker? https://bugs.launchpad.net/castellan20:57
*** padkrish has joined #openstack-meeting-alt20:57
redrobotkfarr sorry about that. seems it was not turned on20:57
redrobotkfarr should be there now.20:57
kfarrOh, that was fast!20:57
*** hichihara has joined #openstack-meeting-alt20:58
redrobotkfarr trying to squeeze the topic into 5 min ;)20:58
*** _nadya_ has joined #openstack-meeting-alt20:58
elmikois there a doc CR in the making for castellan?20:58
redrobotelmiko not that I'm aware of20:58
redrobotelmiko but keep your radar on, since I'll probably be writing a lot of it for the upcoming integration talk in Vancouver20:59
*** MarkAtwood has quit IRC20:59
elmikoawesome, thanks20:59
elmikoi'm really eager to start using it20:59
*** pnavarro|off has quit IRC20:59
*** baoli has quit IRC20:59
redrobotok, we're almost out of time.  arunkant I'll get to the usage topic next week, or you can ping me in the main channel20:59
redrobot#endmeeting20:59
*** openstack changes topic to ": ML2 Sync and error handling (Task Flow) - revisited (Meeting topic: networking_ml2)"20:59
openstackMeeting ended Mon Mar 23 20:59:49 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-03-23-19.59.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-03-23-19.59.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-03-23-19.59.log.html20:59
*** sgotliv has quit IRC20:59
elmikothanks redrobot !21:00
*** baoli has joined #openstack-meeting-alt21:00
*** padkrish has quit IRC21:01
*** _nadya_ has quit IRC21:02
*** sslypushenko_ has quit IRC21:02
*** padkrish has joined #openstack-meeting-alt21:02
*** jrichli has left #openstack-meeting-alt21:03
*** kzaitsev has quit IRC21:04
*** bobmel_ has joined #openstack-meeting-alt21:04
*** fern__ has quit IRC21:04
*** BrianB_ has joined #openstack-meeting-alt21:05
*** igueths has left #openstack-meeting-alt21:06
*** bobmel has quit IRC21:07
*** joel-coffman has left #openstack-meeting-alt21:07
*** radez is now known as radez_g0n321:09
*** wbrothers-wfh has quit IRC21:11
*** igordcard_ has joined #openstack-meeting-alt21:13
*** thangp has quit IRC21:13
*** rellerreller has quit IRC21:13
*** toph has quit IRC21:14
*** BrianB_ has quit IRC21:14
*** carl_baldwin has quit IRC21:15
*** carl_baldwin has joined #openstack-meeting-alt21:18
*** kfarr has quit IRC21:18
*** yamamoto_ has joined #openstack-meeting-alt21:18
*** kzaitsev has joined #openstack-meeting-alt21:19
*** prad has joined #openstack-meeting-alt21:20
*** hyakuhei has joined #openstack-meeting-alt21:20
*** mattgriffin has quit IRC21:21
*** sdake__ has joined #openstack-meeting-alt21:22
*** yamamoto_ has quit IRC21:23
*** sreshetn1 has quit IRC21:23
*** kzaitsev has quit IRC21:23
*** tkelsey has quit IRC21:24
*** kzaitsev has joined #openstack-meeting-alt21:24
*** sdake has quit IRC21:26
*** tkelsey has joined #openstack-meeting-alt21:26
*** sriram1 has left #openstack-meeting-alt21:27
*** kzaitsev has quit IRC21:27
*** chellygel has left #openstack-meeting-alt21:30
*** mattgriffin has joined #openstack-meeting-alt21:31
*** mattfarina has quit IRC21:31
*** yamahata has quit IRC21:35
*** yamahata has joined #openstack-meeting-alt21:36
*** tdruiva has joined #openstack-meeting-alt21:37
*** jhfeng has quit IRC21:37
*** yamahata has quit IRC21:37
*** yamahata has joined #openstack-meeting-alt21:38
*** kzaitsev has joined #openstack-meeting-alt21:38
*** EricGonczer_ has quit IRC21:38
*** pmalik has quit IRC21:40
*** kzaitsev has quit IRC21:40
*** jcoufal has quit IRC21:42
*** noslzzp has quit IRC21:43
*** pmalik has joined #openstack-meeting-alt21:43
*** jtomasek has quit IRC21:46
*** baoli has quit IRC21:48
*** nelsnelson has quit IRC21:49
*** dprince has quit IRC21:50
*** kzaitsev has joined #openstack-meeting-alt21:51
*** sdake__ has quit IRC21:54
*** matrohon has quit IRC21:54
*** jcoufal has joined #openstack-meeting-alt21:54
*** hyakuhei has quit IRC21:55
*** kzaitsev has quit IRC21:55
*** _amrith_ is now known as amrith21:55
*** sdake has joined #openstack-meeting-alt21:57
*** tkelsey has quit IRC21:57
*** bpb_ has quit IRC22:05
*** yamamoto_ has joined #openstack-meeting-alt22:06
*** sigmavirus24 is now known as sigmavirus24_awa22:07
*** kzaitsev has joined #openstack-meeting-alt22:07
*** armax has quit IRC22:08
*** julim has quit IRC22:09
*** kzaitsev has quit IRC22:11
*** padkrish has quit IRC22:12
*** padkrish has joined #openstack-meeting-alt22:13
*** padkrish_ has joined #openstack-meeting-alt22:14
*** niclem has quit IRC22:14
*** andreykurilin_ has quit IRC22:15
*** baoli has joined #openstack-meeting-alt22:17
*** dimtruck is now known as zz_dimtruck22:17
*** padkrish has quit IRC22:17
*** amitgandhinz has quit IRC22:20
*** VW_ has quit IRC22:24
*** noslzzp has joined #openstack-meeting-alt22:25
*** baoli has quit IRC22:30
*** miqui has quit IRC22:30
*** smillward has quit IRC22:30
*** prad has quit IRC22:31
*** salv-orl_ has joined #openstack-meeting-alt22:34
*** salv-orlando has quit IRC22:34
*** salv-orl_ has quit IRC22:38
*** ljfisher has quit IRC22:39
*** jcoufal has quit IRC22:40
*** jecarey has quit IRC22:41
*** HeOS has quit IRC22:41
*** salv-orlando has joined #openstack-meeting-alt22:42
*** fzdarsky has quit IRC22:43
*** tdruiva has quit IRC22:44
*** kzaitsev has joined #openstack-meeting-alt22:46
*** kzaitsev has quit IRC22:47
*** armax has joined #openstack-meeting-alt22:49
*** AlanClark has quit IRC22:49
*** kzaitsev has joined #openstack-meeting-alt22:50
*** ijw has joined #openstack-meeting-alt22:52
*** crc32 has quit IRC22:53
*** pballand has quit IRC22:54
*** absubram has quit IRC22:55
*** ganso_ has quit IRC22:57
*** sarob has joined #openstack-meeting-alt22:58
*** mattgriffin has quit IRC22:58
*** padkrish_ has quit IRC23:00
*** kzaitsev has quit IRC23:00
*** padkrish has joined #openstack-meeting-alt23:00
*** markvoelker has quit IRC23:01
*** padkrish_ has joined #openstack-meeting-alt23:02
*** shwetaap has quit IRC23:02
*** sarob has quit IRC23:03
*** ivar-laz_ has joined #openstack-meeting-alt23:04
*** padkrish has quit IRC23:05
*** ivar-lazzaro has quit IRC23:07
*** niclem has joined #openstack-meeting-alt23:09
*** sarob has joined #openstack-meeting-alt23:13
*** dane_leblanc has quit IRC23:15
*** spzala has quit IRC23:17
*** banix has joined #openstack-meeting-alt23:17
*** sarob has quit IRC23:20
*** tdruiva has joined #openstack-meeting-alt23:21
*** EricGonczer_ has joined #openstack-meeting-alt23:22
*** ijw_ has joined #openstack-meeting-alt23:24
*** ijw_ has quit IRC23:25
*** ijw_ has joined #openstack-meeting-alt23:26
*** thomasem has quit IRC23:26
*** ijw has quit IRC23:27
*** sarob has joined #openstack-meeting-alt23:27
*** tsekiyam_ has joined #openstack-meeting-alt23:32
*** ijw has joined #openstack-meeting-alt23:33
*** thomasem has joined #openstack-meeting-alt23:33
*** mwagner_lap has joined #openstack-meeting-alt23:33
*** hblixt has joined #openstack-meeting-alt23:34
*** tsekiyama has quit IRC23:35
*** mtanino has quit IRC23:35
*** baoli has joined #openstack-meeting-alt23:36
*** sarob has quit IRC23:36
*** tsekiyam_ has quit IRC23:36
*** ijw_ has quit IRC23:36
*** sarob has joined #openstack-meeting-alt23:40
*** zz_dimtruck is now known as dimtruck23:41
*** tdruiva has quit IRC23:41
*** jaosorior has quit IRC23:42
*** tonytan4ever has quit IRC23:42
*** ajmiller has quit IRC23:44
*** sarob has quit IRC23:45
*** EricGonc_ has joined #openstack-meeting-alt23:45
*** annashen has quit IRC23:46
*** markvoelker has joined #openstack-meeting-alt23:47
*** annashen has joined #openstack-meeting-alt23:47
*** tdruiva has joined #openstack-meeting-alt23:47
*** haleyb has quit IRC23:48
*** EricGonczer_ has quit IRC23:48
*** markvoelker has quit IRC23:51
*** padkrish_ has quit IRC23:56
*** pvaneck has quit IRC23:56
*** padkrish has joined #openstack-meeting-alt23:56
*** carl_baldwin has quit IRC23:57
*** ijw_ has joined #openstack-meeting-alt23:58
*** dims_ has joined #openstack-meeting-alt23:58
*** eghobo_ has quit IRC23:59

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