Thursday, 2014-10-16

*** adrian_otto has quit IRC00:02
*** ivar-laz_ has quit IRC00:04
*** dims_ has quit IRC00:06
*** dims_ has joined #openstack-meeting-alt00:06
*** tsekiyama has quit IRC00:06
*** dims__ has joined #openstack-meeting-alt00:07
*** elmiko has joined #openstack-meeting-alt00:10
*** ramishra has joined #openstack-meeting-alt00:10
*** dims_ has quit IRC00:11
*** mtanino has quit IRC00:11
*** rmoe has quit IRC00:12
*** elmiko has left #openstack-meeting-alt00:12
*** SumitNaiksatam has quit IRC00:13
*** ivar-lazzaro has joined #openstack-meeting-alt00:14
*** ivar-laz_ has joined #openstack-meeting-alt00:16
*** ivar-lazzaro has quit IRC00:16
*** ivar-laz_ has quit IRC00:17
*** ivar-lazzaro has joined #openstack-meeting-alt00:18
*** markwash__ has quit IRC00:20
*** markwash__ has joined #openstack-meeting-alt00:20
*** ijw has joined #openstack-meeting-alt00:28
*** rmoe has joined #openstack-meeting-alt00:29
*** safchain has quit IRC00:30
*** dimtruck is now known as zz_dimtruck00:30
*** julienvey has joined #openstack-meeting-alt00:33
*** ijw has quit IRC00:33
*** markwash__ has quit IRC00:34
*** julienvey has quit IRC00:37
*** julienvey has joined #openstack-meeting-alt00:38
*** padkrish has quit IRC00:41
*** julienvey has quit IRC00:43
*** bdpayne has quit IRC00:50
*** marcoemorais has quit IRC00:50
*** otherwiseguy has quit IRC00:50
*** ramishra has quit IRC00:51
*** ramishra has joined #openstack-meeting-alt00:52
*** luizfar has joined #openstack-meeting-alt00:53
*** zz_dimtruck is now known as dimtruck00:55
*** SumitNaiksatam has joined #openstack-meeting-alt00:57
*** luizfar has quit IRC00:57
*** ramishra has quit IRC01:02
*** markwash__ has joined #openstack-meeting-alt01:04
*** ivar-laz_ has joined #openstack-meeting-alt01:08
*** sunrenjie6 has joined #openstack-meeting-alt01:09
*** zhhuabj has joined #openstack-meeting-alt01:11
*** ivar-lazzaro has quit IRC01:11
*** markwash__ has quit IRC01:11
*** zhhuabj has quit IRC01:12
*** ivar-laz_ has quit IRC01:13
*** rob__ has joined #openstack-meeting-alt01:14
*** rob__ has quit IRC01:14
*** zhhuabj has joined #openstack-meeting-alt01:15
*** alex_didenko has quit IRC01:15
*** alex_didenko has joined #openstack-meeting-alt01:16
*** Stanzi has joined #openstack-meeting-alt01:16
*** sankarshan is now known as sankarshan_away01:17
*** baoli has joined #openstack-meeting-alt01:18
*** sballe has quit IRC01:19
*** zhhuabj has quit IRC01:19
*** Longgeek has joined #openstack-meeting-alt01:19
*** zhhuabj has joined #openstack-meeting-alt01:20
*** mberlin has joined #openstack-meeting-alt01:23
*** Longgeek has quit IRC01:25
*** mberlin1 has quit IRC01:26
*** dims__ has quit IRC01:26
*** dims_ has joined #openstack-meeting-alt01:27
*** Stanzi has quit IRC01:27
*** Stanzi has joined #openstack-meeting-alt01:28
*** gyee has quit IRC01:28
*** ijw has joined #openstack-meeting-alt01:29
*** dims_ has quit IRC01:29
*** dims_ has joined #openstack-meeting-alt01:30
*** tdruiva has joined #openstack-meeting-alt01:30
*** ramishra has joined #openstack-meeting-alt01:32
*** ijw has quit IRC01:34
*** Riddhi has joined #openstack-meeting-alt01:34
*** tchaypo has joined #openstack-meeting-alt01:35
*** georgelorch has quit IRC01:41
*** ramishra has quit IRC01:42
*** alex_xu has joined #openstack-meeting-alt01:43
*** georgelorch has joined #openstack-meeting-alt01:44
*** xuhanp has joined #openstack-meeting-alt01:47
*** markwash__ has joined #openstack-meeting-alt01:50
*** markwash__ has quit IRC01:51
*** markwash__ has joined #openstack-meeting-alt01:51
*** shakamunyi has joined #openstack-meeting-alt01:54
*** woodster_ has quit IRC02:00
*** julienvey has joined #openstack-meeting-alt02:02
*** ramishra has joined #openstack-meeting-alt02:02
*** Longgeek has joined #openstack-meeting-alt02:04
*** yamamoto_ has joined #openstack-meeting-alt02:05
*** salv-orlando has quit IRC02:05
*** sunrenjie6 has quit IRC02:05
*** rondotcom has joined #openstack-meeting-alt02:06
*** julienvey has quit IRC02:06
*** rmoe has quit IRC02:10
*** rmoe has joined #openstack-meeting-alt02:12
*** nosnos has joined #openstack-meeting-alt02:20
*** rondotcom has quit IRC02:27
*** rondotcom has joined #openstack-meeting-alt02:27
*** alex_xu has quit IRC02:30
*** rondotcom has quit IRC02:32
*** alex_xu has joined #openstack-meeting-alt02:34
*** akoneru has quit IRC02:35
*** armax has joined #openstack-meeting-alt02:39
*** rondotcom has joined #openstack-meeting-alt02:41
*** Barker has joined #openstack-meeting-alt02:49
*** markwash__ has quit IRC02:56
*** markwash__ has joined #openstack-meeting-alt02:57
*** ramishra_ has joined #openstack-meeting-alt02:58
*** ramishra has quit IRC03:00
*** dims_ has quit IRC03:01
*** dims_ has joined #openstack-meeting-alt03:02
*** Stanzi has quit IRC03:05
*** mfer has quit IRC03:05
*** Stanzi has joined #openstack-meeting-alt03:06
*** dims_ has quit IRC03:06
*** spzala has quit IRC03:07
*** ramishra_ has quit IRC03:10
*** Stanzi has quit IRC03:10
*** armax has quit IRC03:10
*** noslzzp has quit IRC03:11
*** armax has joined #openstack-meeting-alt03:12
*** otherwiseguy has joined #openstack-meeting-alt03:15
*** otherwiseguy has quit IRC03:21
*** otherwiseguy has joined #openstack-meeting-alt03:21
*** bubbva has quit IRC03:25
*** nosnos has quit IRC03:26
*** nosnos has joined #openstack-meeting-alt03:27
*** bubbva has joined #openstack-meeting-alt03:29
*** manishg has joined #openstack-meeting-alt03:29
*** nosnos has quit IRC03:31
*** manishg_ has joined #openstack-meeting-alt03:32
*** ramishra has joined #openstack-meeting-alt03:32
*** harlowja is now known as harlowja_away03:32
*** manishg has quit IRC03:34
*** harlowja_away is now known as harlowja03:34
*** manishg_ has quit IRC03:38
*** Haiying has joined #openstack-meeting-alt03:42
*** yamahata has quit IRC03:48
*** xuhanp has quit IRC03:50
*** otherwiseguy has quit IRC03:51
*** otherwiseguy has joined #openstack-meeting-alt03:51
*** richm has quit IRC03:52
*** amotoki__zzz has quit IRC04:00
*** SridharG has joined #openstack-meeting-alt04:00
*** nelsnelson has quit IRC04:06
*** armax has quit IRC04:07
*** otherwiseguy has quit IRC04:08
*** rbrady has quit IRC04:08
*** otherwiseguy has joined #openstack-meeting-alt04:09
*** otherwiseguy has quit IRC04:14
*** otherwiseguy has joined #openstack-meeting-alt04:14
*** alex_didenko has quit IRC04:16
*** alex_didenko has joined #openstack-meeting-alt04:16
*** markwash__ has quit IRC04:17
*** otherwiseguy has quit IRC04:20
*** otherwiseguy has joined #openstack-meeting-alt04:20
*** marcoemorais has joined #openstack-meeting-alt04:22
*** markwash__ has joined #openstack-meeting-alt04:23
*** nosnos has joined #openstack-meeting-alt04:23
*** marcoemorais1 has joined #openstack-meeting-alt04:24
*** ramishra has quit IRC04:24
*** Riddhi has quit IRC04:25
*** marcoemorais has quit IRC04:27
*** ijw has joined #openstack-meeting-alt04:32
*** otherwiseguy has quit IRC04:33
*** zhhuabj has quit IRC04:34
*** zhhuabj has joined #openstack-meeting-alt04:34
*** ijw has quit IRC04:37
*** dimtruck is now known as zz_dimtruck04:39
*** yamahata has joined #openstack-meeting-alt04:40
*** markwash__ has quit IRC04:40
*** otherwiseguy has joined #openstack-meeting-alt04:43
*** georgelorch has quit IRC04:52
*** jaypipes has joined #openstack-meeting-alt04:53
*** georgelorch has joined #openstack-meeting-alt04:54
*** otherwiseguy has quit IRC04:55
*** sballe has joined #openstack-meeting-alt04:57
*** otherwiseguy has joined #openstack-meeting-alt05:07
*** alex_xu has quit IRC05:12
*** otherwiseguy has quit IRC05:12
*** armax has joined #openstack-meeting-alt05:20
*** ramishra has joined #openstack-meeting-alt05:21
*** xuhanp has joined #openstack-meeting-alt05:23
*** deepakcs has joined #openstack-meeting-alt05:25
*** k4n0 has joined #openstack-meeting-alt05:29
*** nshaikh has joined #openstack-meeting-alt05:31
*** armax has quit IRC05:33
*** Barker has quit IRC05:33
*** Longgeek has quit IRC05:35
*** HenryG has quit IRC05:36
*** kopparam has joined #openstack-meeting-alt05:41
*** harlowja is now known as harlowja_away05:41
*** armax has joined #openstack-meeting-alt05:53
*** amotoki has joined #openstack-meeting-alt05:56
*** coolsvap|afk is now known as coolsvap05:56
*** SumitNaiksatam has quit IRC06:00
*** SumitNaiksatam has joined #openstack-meeting-alt06:02
*** ttrumm has joined #openstack-meeting-alt06:03
*** dims_ has joined #openstack-meeting-alt06:03
*** Longgeek has joined #openstack-meeting-alt06:03
*** armax has quit IRC06:03
*** ttrumm_ has joined #openstack-meeting-alt06:05
*** ttrumm has quit IRC06:07
*** dims_ has quit IRC06:07
*** _nadya_ has joined #openstack-meeting-alt06:07
*** markwash__ has joined #openstack-meeting-alt06:10
*** markwash__ has quit IRC06:11
*** markwash__ has joined #openstack-meeting-alt06:15
*** nkrinner has joined #openstack-meeting-alt06:17
*** _nadya_ has quit IRC06:22
*** markwash__ has quit IRC06:26
*** deepakcs has quit IRC06:27
*** ijw has joined #openstack-meeting-alt06:34
*** SridharG has left #openstack-meeting-alt06:35
*** markwash__ has joined #openstack-meeting-alt06:37
*** hachao has quit IRC06:37
*** ijw has quit IRC06:39
*** hachao has joined #openstack-meeting-alt06:39
*** rbrady has joined #openstack-meeting-alt06:45
*** shakamunyi has quit IRC06:46
*** shakamunyi has joined #openstack-meeting-alt06:49
*** markwash__ has quit IRC06:50
*** matrohon has joined #openstack-meeting-alt06:55
*** akislitsky has left #openstack-meeting-alt06:55
*** shakamunyi has quit IRC06:56
*** ramishra has quit IRC06:56
*** ramishra has joined #openstack-meeting-alt06:57
*** kopparam_ has joined #openstack-meeting-alt06:58
*** kopparam has quit IRC07:01
*** jtomasek has joined #openstack-meeting-alt07:03
*** e0ne has joined #openstack-meeting-alt07:05
*** alex_xu has joined #openstack-meeting-alt07:06
*** e0ne has quit IRC07:07
*** e0ne has joined #openstack-meeting-alt07:11
*** e0ne has quit IRC07:13
*** doude has joined #openstack-meeting-alt07:13
*** jamiehannaford has joined #openstack-meeting-alt07:15
*** jcoufal has joined #openstack-meeting-alt07:16
*** ramishra has quit IRC07:16
*** flaper87|afk is now known as flaper8707:16
*** ramishra has joined #openstack-meeting-alt07:17
*** kopparam_ has quit IRC07:19
*** kopparam has joined #openstack-meeting-alt07:20
*** HenryG has joined #openstack-meeting-alt07:20
*** kopparam has quit IRC07:21
*** ramishra has quit IRC07:22
*** kopparam has joined #openstack-meeting-alt07:22
*** sgotliv has joined #openstack-meeting-alt07:25
*** HeOS has quit IRC07:25
*** kopparam has quit IRC07:27
*** e0ne has joined #openstack-meeting-alt07:28
*** e0ne has quit IRC07:32
*** azemlyanov has joined #openstack-meeting-alt07:34
*** alex_didenko has quit IRC07:34
*** alex_didenko has joined #openstack-meeting-alt07:35
*** SridharG has joined #openstack-meeting-alt07:35
*** jprovazn has joined #openstack-meeting-alt07:36
*** e0ne has joined #openstack-meeting-alt07:37
*** ramishra has joined #openstack-meeting-alt07:38
*** flaper87 is now known as flaper87|afk07:41
*** sgotliv has quit IRC07:41
*** kashyap has joined #openstack-meeting-alt07:41
*** sgotliv has joined #openstack-meeting-alt07:46
*** deepakcs has joined #openstack-meeting-alt07:46
*** e0ne has quit IRC07:49
*** ndipanov_gone is now known as ndipanov07:50
*** e0ne has joined #openstack-meeting-alt07:53
*** ramishra has quit IRC07:53
*** e0ne has quit IRC07:53
*** sballe has quit IRC07:59
*** kopparam has joined #openstack-meeting-alt08:00
*** lavaraj has joined #openstack-meeting-alt08:20
*** salv-orlando has joined #openstack-meeting-alt08:23
*** Stanzi has joined #openstack-meeting-alt08:24
*** safchain has joined #openstack-meeting-alt08:28
*** Stanzi has quit IRC08:29
*** Haiying has quit IRC08:30
*** HeOS has joined #openstack-meeting-alt08:35
*** yamahata has quit IRC08:36
*** julienvey has joined #openstack-meeting-alt08:39
*** kashyap has quit IRC08:41
*** katyafervent_awa is now known as katyafervent08:41
*** sgotliv has quit IRC08:41
*** igordcard has joined #openstack-meeting-alt08:42
*** kopparam_ has joined #openstack-meeting-alt08:42
*** balajiiyer has joined #openstack-meeting-alt08:43
*** ramishra has joined #openstack-meeting-alt08:43
*** balajiiyer has quit IRC08:43
*** balajiiyer has joined #openstack-meeting-alt08:44
*** kopparam has quit IRC08:45
*** e0ne has joined #openstack-meeting-alt08:51
*** sileht has quit IRC08:53
*** ihrachyshka has joined #openstack-meeting-alt08:57
*** ramishra has quit IRC09:01
*** zz_johnthetubagu is now known as johnthetubaguy09:04
*** yamamoto_ has quit IRC09:05
*** sileht has joined #openstack-meeting-alt09:05
*** teran has quit IRC09:08
*** armax has joined #openstack-meeting-alt09:17
*** alex_xu has quit IRC09:18
*** funzo has quit IRC09:28
*** kashyap has joined #openstack-meeting-alt09:35
*** ijw has joined #openstack-meeting-alt09:37
*** teran has joined #openstack-meeting-alt09:38
*** derekh has joined #openstack-meeting-alt09:39
*** ijw has quit IRC09:42
*** teran has quit IRC09:46
*** balajiiyer has quit IRC09:47
*** julienvey has quit IRC09:48
*** markwash__ has joined #openstack-meeting-alt09:52
*** julienvey has joined #openstack-meeting-alt09:54
*** markwash__ has quit IRC09:57
*** julienvey has quit IRC09:57
*** julienvey has joined #openstack-meeting-alt09:57
*** loquacities has quit IRC10:01
*** julienvey has quit IRC10:02
*** teran has joined #openstack-meeting-alt10:04
*** loquacities has joined #openstack-meeting-alt10:04
*** tbarron_gone is now known as tbarron10:06
*** _nadya_ has joined #openstack-meeting-alt10:07
*** xuhanp has quit IRC10:12
*** lavaraj has quit IRC10:12
*** ianblenke has quit IRC10:16
*** yamamoto_ has joined #openstack-meeting-alt10:25
*** tdruiva has quit IRC10:25
*** ramishra has joined #openstack-meeting-alt10:28
*** nshaikh has quit IRC10:29
*** armax has quit IRC10:29
*** ramishra has quit IRC10:32
*** _nadya_ has quit IRC10:33
*** yamahata has joined #openstack-meeting-alt10:36
*** _nadya_ has joined #openstack-meeting-alt10:38
*** kopparam_ has quit IRC10:42
*** ianblenke has joined #openstack-meeting-alt10:43
*** flaper87|afk is now known as flaper8710:46
*** _nadya_ has quit IRC10:46
*** salv-orlando has quit IRC10:48
*** kashyap has quit IRC10:49
*** thomnico has joined #openstack-meeting-alt10:49
*** yamamoto_ has quit IRC10:51
*** teran_ has joined #openstack-meeting-alt10:53
*** teran has quit IRC10:56
*** ramishra has joined #openstack-meeting-alt10:57
*** dims_ has joined #openstack-meeting-alt10:58
*** armax has joined #openstack-meeting-alt11:03
*** flaper87 is now known as flaper87|afk11:04
*** teran has joined #openstack-meeting-alt11:06
*** deepakcs has quit IRC11:06
*** tdruiva has joined #openstack-meeting-alt11:08
*** teran_ has quit IRC11:09
*** thomnico has quit IRC11:09
*** amrith is now known as _amrith_11:11
*** marcoemorais1 has quit IRC11:11
*** armax has quit IRC11:13
*** kopparam has joined #openstack-meeting-alt11:17
*** armax has joined #openstack-meeting-alt11:18
*** apodrepniy has quit IRC11:21
*** armax has quit IRC11:25
*** _nadya_ has joined #openstack-meeting-alt11:27
*** tedross has joined #openstack-meeting-alt11:32
*** ramishra has quit IRC11:35
*** julienvey has joined #openstack-meeting-alt11:39
*** teran has quit IRC11:39
*** teran has joined #openstack-meeting-alt11:44
*** teran has quit IRC11:45
*** julim has quit IRC11:46
*** woodster_ has joined #openstack-meeting-alt11:49
*** dane_leblanc has quit IRC11:50
*** cbouch has joined #openstack-meeting-alt11:51
*** nshaikh has joined #openstack-meeting-alt11:52
*** armax has joined #openstack-meeting-alt11:56
*** teran has joined #openstack-meeting-alt11:57
*** armax has quit IRC11:58
*** kopparam has quit IRC12:01
*** kopparam has joined #openstack-meeting-alt12:02
*** radez_g0n3 is now known as radez12:04
*** nshaikh has quit IRC12:05
*** kopparam has quit IRC12:06
*** xuhanp has joined #openstack-meeting-alt12:08
*** thomnico has joined #openstack-meeting-alt12:09
*** armax has joined #openstack-meeting-alt12:09
*** thomnico has quit IRC12:09
*** julienvey has quit IRC12:09
*** matrohon has quit IRC12:10
*** Haiying has joined #openstack-meeting-alt12:11
*** kopparam has joined #openstack-meeting-alt12:14
*** sankarshan_away is now known as sankarshan12:16
*** ramishra has joined #openstack-meeting-alt12:16
*** apodrepniy has joined #openstack-meeting-alt12:18
*** julienvey has joined #openstack-meeting-alt12:18
*** jehb has joined #openstack-meeting-alt12:19
*** lecalcot has joined #openstack-meeting-alt12:22
*** lecalcot has quit IRC12:22
*** funzo has joined #openstack-meeting-alt12:23
*** Haiying has quit IRC12:25
*** ramishra has quit IRC12:28
*** Haiying has joined #openstack-meeting-alt12:29
*** dprince has joined #openstack-meeting-alt12:32
*** cbouch has quit IRC12:36
*** kopparam has quit IRC12:39
*** ijw has joined #openstack-meeting-alt12:40
*** kopparam has joined #openstack-meeting-alt12:40
*** georgelorch2 has joined #openstack-meeting-alt12:43
*** nshaikh has joined #openstack-meeting-alt12:44
*** georgelorch has quit IRC12:44
*** kopparam has quit IRC12:44
*** ijw has quit IRC12:45
*** satish has joined #openstack-meeting-alt12:46
*** vponomaryov has joined #openstack-meeting-alt12:50
*** armax has quit IRC12:51
*** armax has joined #openstack-meeting-alt12:53
*** ramishra has joined #openstack-meeting-alt12:54
*** shadower39 has joined #openstack-meeting-alt12:57
*** armax has quit IRC12:59
*** xuhanp has quit IRC12:59
*** noslzzp has joined #openstack-meeting-alt12:59
*** tedross has quit IRC13:00
*** armax has joined #openstack-meeting-alt13:00
*** miqui has joined #openstack-meeting-alt13:01
*** shadower39 has quit IRC13:01
*** shadower78 has joined #openstack-meeting-alt13:02
*** shadower has quit IRC13:03
*** shadower78 is now known as shadower13:03
*** armax has quit IRC13:04
*** Stanzi has joined #openstack-meeting-alt13:04
*** Stanzi has quit IRC13:09
*** kopparam has joined #openstack-meeting-alt13:10
*** armax has joined #openstack-meeting-alt13:11
*** armax has quit IRC13:11
*** jecarey_ has quit IRC13:11
*** armax has joined #openstack-meeting-alt13:12
*** armax has quit IRC13:12
*** zz_jgrimm is now known as jgrimm13:13
*** tedross has joined #openstack-meeting-alt13:16
*** kopparam has quit IRC13:17
*** Barker has joined #openstack-meeting-alt13:17
*** gholler has joined #openstack-meeting-alt13:18
*** ramishra has quit IRC13:20
*** ramishra has joined #openstack-meeting-alt13:21
*** betsy has joined #openstack-meeting-alt13:21
*** julim has joined #openstack-meeting-alt13:21
*** richm has joined #openstack-meeting-alt13:23
*** dane_leblanc has joined #openstack-meeting-alt13:24
*** rondotcom has quit IRC13:26
*** rondotcom has joined #openstack-meeting-alt13:27
*** _nadya_ has quit IRC13:29
*** rondotcom has quit IRC13:31
*** Barker has quit IRC13:36
*** jprovazn has quit IRC13:37
*** Haiying has quit IRC13:38
*** mfer has joined #openstack-meeting-alt13:39
*** ijw has joined #openstack-meeting-alt13:42
*** _nadya_ has joined #openstack-meeting-alt13:42
*** teran_ has joined #openstack-meeting-alt13:44
*** esker has joined #openstack-meeting-alt13:44
*** _nadya_ has quit IRC13:45
*** ozamiatin_ has quit IRC13:46
*** rbrady_ has joined #openstack-meeting-alt13:46
*** tdubyk has joined #openstack-meeting-alt13:46
*** ijw has quit IRC13:46
*** rbrady has quit IRC13:47
*** teran has quit IRC13:47
*** akoneru has joined #openstack-meeting-alt13:47
*** armax has joined #openstack-meeting-alt13:48
*** matrohon has joined #openstack-meeting-alt13:48
*** rbrady_ is now known as rbrady13:48
*** n0ano has joined #openstack-meeting-alt13:56
*** jecarey has joined #openstack-meeting-alt13:57
*** luizfar has joined #openstack-meeting-alt13:57
*** TapioTallgren has joined #openstack-meeting-alt13:59
*** boden has joined #openstack-meeting-alt13:59
*** ttrumm_ has quit IRC13:59
*** mriedem has joined #openstack-meeting-alt14:00
leifzmeeting?14:00
*** ekhugen has joined #openstack-meeting-alt14:00
*** ramishra has quit IRC14:00
*** noslzzp has quit IRC14:00
bodenleifz -- I see it started on #openstack-meeting14:01
leifzand just ended?14:01
johnthetubaguy#startmeeting nova14:01
openstackMeeting started Thu Oct 16 14:01:25 2014 UTC and is due to finish in 60 minutes.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: nova)"14:01
openstackThe meeting name has been set to 'nova'14:01
johnthetubaguyhttps://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting14:01
bauzas\o14:01
mriedemhi14:01
edleafeo/14:01
johnthetubaguy#topic juno14:01
dansmitho/14:01
*** openstack changes topic to "juno (Meeting topic: nova)"14:01
leifzlurking14:01
bodeno/14:01
jgrimmo/14:01
johnthetubaguyso juno is shipped14:01
edleafe\o/14:01
*** mattgriffin has joined #openstack-meeting-alt14:01
johnthetubaguystable backports for stuff you spot now I think14:01
n0anoo/14:02
johnthetubaguyusual backport tags for all that fun14:02
johnthetubaguy#topic kilo14:02
* beagles lurks14:02
*** openstack changes topic to "kilo (Meeting topic: nova)"14:02
johnthetubaguyso specs are open, we are fast approving some, and slow approving some14:02
johnthetubaguyany questions or things to raise?14:02
mriedemstable/juno doesn't seem to exist yet14:03
johnthetubaguy#info if your code reviews are being blocked on a "procedural -2", please ping the reviewer (in email) and remind them to reconsider14:03
mriedemnope14:03
*** TapioTallgren has quit IRC14:03
johnthetubaguymriedem: hmm, doh, I guess we only just tagged, so thats next14:03
mriedemi'll let it go this time14:03
*** TapioTallgren has joined #openstack-meeting-alt14:03
*** mtanino has joined #openstack-meeting-alt14:03
johnthetubaguy:)14:03
johnthetubaguyanyways, anything on specs?14:03
johnthetubaguyeveryone as happy as they can be about the new rules?14:04
johnthetubaguyany tweaks needed at the moment?14:04
bauzasjohnthetubaguy: about priorites14:04
*** TapioTallgren has quit IRC14:04
n0anojohnthetubaguy, too early to tell, we'll comment when we have issues14:04
bauzasjohnthetubaguy: it's asked to fill them in14:04
johnthetubaguybauzas: to be agreed at the summit I think14:04
bauzasjohnthetubaguy: k, so leaving a perhaps in this14:04
mriedembauzas: i just put None if my thing wasn't an obvious priority14:05
johnthetubaguymriedem: +114:05
bauzasmriedem: k, I'm taking the etherpad as a reference14:05
mriedemit's a priority for me, but not the project14:05
johnthetubaguywe can go back and edit the specs, if we come up with a priority that you fit, after its approved14:05
*** thangp has joined #openstack-meeting-alt14:05
bauzashttps://etherpad.openstack.org/p/kilo-nova-priorities14:05
bauzasI'm taking these chapters as the ones I'm looking to, if so14:06
bauzasjohnthetubaguy: k, sounds good14:06
n0anodoes it make sense to approve a spec that has no priority, I would think that would be required14:06
ndipanovso what do the priorities mean now - there was so much back and forth that I am not sure what is agreed on14:06
johnthetubaguyn0ano: thats another summit discussion, for now, yes, they are low priority14:06
bauzasI was understanding that priorities would be set for juno-3 ?14:06
bauzasoops14:07
johnthetubaguyndipanov: right now, they have no power, the idea is to agree at the summit14:07
bauzaskilo-414:07
n0anowhich means they'll probably get ignored so yes, this needs to be discussed at the summit14:07
bauzaskilo-314:07
* bauzas has to watch the new openstack episodes14:07
johnthetubaguyso yeah, my current plan is, kilo-3 nothing except high priority stuff merges, so we kinda have a soft blueprint freeze at the end of kilo-214:07
bauzask14:07
johnthetubaguybut lets see how it goes, is the detailed version of the plan14:08
ndipanovjohnthetubaguy, and we are not doing runways, right?14:08
mriedemthe policy patch for runways was abandoned14:08
johnthetubaguy#info remember, all features need a blueprint, not all blueprints need a spec14:08
mriedemwhich is what i thought we were going to use to get low priority stuff in14:08
johnthetubaguyyeah, runways just got shot down too much on the ML14:09
mriedemhttps://review.openstack.org/#/c/115410/14:09
johnthetubaguymy hope is to discuss that at the summit, and come up with a comprimise14:09
ndipanovjohnthetubaguy, ack - that will be a fun discussion :)14:09
*** ramishra has joined #openstack-meeting-alt14:09
johnthetubaguythe current one is, kilo-1 and kilo-2 is free, kilo-3 is basically runways14:09
* alaski wanders in late14:09
johnthetubaguycools14:10
johnthetubaguy#topic Kilo Summit14:10
*** openstack changes topic to "Kilo Summit (Meeting topic: nova)"14:10
*** sgotliv has joined #openstack-meeting-alt14:10
johnthetubaguyso, I was hoping we would have a session plan, that we could discuss, but we don't really14:10
*** nelsnelson has joined #openstack-meeting-alt14:11
johnthetubaguyI have lobbed a few ideas at the end of the etherpad14:11
johnthetubaguy#link https://etherpad.openstack.org/p/kilo-nova-summit-topics14:11
johnthetubaguy#info we have 2 days of scheduled slots and 1 day of meetup style14:11
johnthetubaguywe need to decide what gets a slot, and what needs meetup style14:11
ndipanovI like those ideas - I am not sure we want to do session per BP like we did in the future, meetup can be for that I guess?14:11
ndipanovlol future14:12
ndipanovpast14:12
ndipanovin the past14:12
mriedemtime traveling is fun14:12
bauzasjohnthetubaguy: slots are 40 mins right?14:12
johnthetubaguybauzas: think so14:12
johnthetubaguyndipanov: agreed though14:12
johnthetubaguyso for stuff that is "here is my feature X"14:12
*** jprovazn has joined #openstack-meeting-alt14:12
mriedemi like meetup style more than slots for everything, but i'd think the process talks would be better for a meetup?14:12
johnthetubaguylets have a spec first14:13
bauzasmriedem: +114:13
n0anojohnthetubaguy, you have some big topics on that list, 40 min. is going to be interesting14:13
bauzasjohnthetubaguy: what if the spec got accepted before the Summit, then violent agreement for 40 mins ? :)14:13
johnthetubaguyn0ano: some might get two slots, but yes14:13
ndipanovjohnthetubaguy, very much agreed14:13
*** manishg has joined #openstack-meeting-alt14:13
johnthetubaguybauzas: thats the hope, avoid that slot, and re-schedule something else into that14:13
mriedemin atlanta a lot of the QA sessions were presentations and those were nicely wrapped up in time for questions within 40 minutes,14:13
bauzasjohnthetubaguy: awesome14:14
mriedemi'd like to see that with blueprint design sessions14:14
mriedemand do meetups for big groups of process argument14:14
dansmithmriedem: really?14:14
*** spzala has joined #openstack-meeting-alt14:14
mriedemi hate the 40 minute thing14:14
ndipanovI though that;s exactly why we don't want that in sessions14:14
mriedemis my point14:14
dansmithmriedem: I don't really want presentations in design summit slots14:14
ndipanovgo read a bp14:14
johnthetubaguydansmith: +114:14
ndipanovor spec14:14
dansmithsmall slots for small discussions14:14
bauzasmriedem: I seriously doubt that some topics can cover both a presentation and a discussion in 40 mins14:14
edleafedansmith: +114:14
*** amotoki_ has joined #openstack-meeting-alt14:14
johnthetubaguyndipanov: yeah, if you can read the spec or bp, thats fine, whatever14:15
dansmithif it's a longer discussion, then meetup style14:15
bauzasmriedem: but hell yeah, planning will be fun14:15
johnthetubaguybauzas: we probably give them two slots then, thats fine14:15
mriedemi'm not talking about a demo14:15
mriedembasically going through whatever the blueprint is, or sticking points, idk14:15
dansmith-114:15
mriedemi just didn't think most of the design sessions seemed to be useful in ATL14:15
mriedemthe 40 min ones14:15
bauzasmriedem: agreed14:15
johnthetubaguyso here is the thing14:15
johnthetubaguywe don't have much time together14:16
dansmiththe ATL sessions weren't really well planned14:16
johnthetubaguyif we can do something in the specs, then we can avoid it14:16
*** david-lyle has joined #openstack-meeting-alt14:16
*** balajiiyer has joined #openstack-meeting-alt14:16
johnthetubaguydansmith: +1 hope we can avoid the ATL dumb sessions14:16
dansmithyeah,14:16
dansmithalthough we're getting pretty close with minimal planning so .. we'll see14:16
*** TrevorV has joined #openstack-meeting-alt14:16
mriedemok, i guess i don't have any other summits to compare to so i started with the worst one...14:16
johnthetubaguyso any BP session will be because we can't agree on the spec14:16
*** manishg_ has joined #openstack-meeting-alt14:17
*** TrevorV has left #openstack-meeting-alt14:17
johnthetubaguymriedem: well the previous one was better, thats all14:17
bauzasjohnthetubaguy: or because it's wider than a single spec ?14:17
johnthetubaguybauzas: if we can agree half the specs for the scheduler stuff, then it helps us concentrate on the stuff we need to talk about right?14:17
*** manishg has quit IRC14:17
bauzasjohnthetubaguy: good question14:17
johnthetubaguybauzas: if we agree all the specs, then cool, nothing to talk about14:17
*** spzala has quit IRC14:18
johnthetubaguySome things are about carving up the work between a group of people14:18
bauzasjohnthetubaguy: well, we at least need to make sure all reviewers stick with the plan14:18
*** spzala has joined #openstack-meeting-alt14:18
bauzasjohnthetubaguy: I mean, summits are good for that14:18
bauzasjohnthetubaguy: specs having 2x+2 don't necessarly mean that the consensus has been reached14:18
ndipanovI don;t think we are looking for consensus14:19
johnthetubaguybauzas: if there were no −1s then the system broke, need to get people to vote on there, anyways14:19
bauzasndipanov: then what ? :)14:19
ndipanovwe are looking for good implementation14:19
ndipanovand features14:19
*** luizfar has quit IRC14:19
ndipanovscrew consensus... :)14:20
johnthetubaguyanyways, this is not rally going anywhere14:20
ndipanovyes agreed14:20
ndipanovmove on :)14:20
bauzas+114:20
johnthetubaguyndipanov: lets just say, code means a lot14:20
johnthetubaguygood code means more14:20
johnthetubaguyanyways14:20
ndipanovso one more question14:20
mriedemwas rally a freudian slip there?14:20
dansmithI feel like we're ratholing here14:20
*** zz_dimtruck is now known as dimtruck14:20
johnthetubaguydansmith: +114:20
ndipanovthe only perf things on your list johnthetubaguy is the profiler stuff14:20
ndipanovoh and Rally14:21
johnthetubaguyndipanov: do we have perf stuff to talk about?14:21
mriedemi thought there were db things14:21
ndipanovwell yes14:21
ndipanovdb14:21
mriedemjogo had something that zzzeeek said wouldn't help14:21
johnthetubaguyOK, not seen that proposed14:21
mriedemso assuming zzzeeek has alternatives14:21
mriedemjogo's was removing the ORM14:21
mriedemSA ORM14:21
mriedembayer said that wouldn't really help14:22
johnthetubaguyah, OK, so thats a thing14:22
ndipanovso if I could add one thing to the list - it would be talk about perf - with a strong focus on db14:22
ndipanovyes that is an old discussion tho14:22
johnthetubaguymriedem: its helped us in some bits, but its probably more about us using it wrongly14:22
ndipanovif that's a thing for the "meetup"14:22
johnthetubaguyndipanov: its on the meet up list already actually, in a really bad way14:22
ndipanovthen cool - but I feel we really should talk about it14:22
ndipanovsince it is one of the reasons scheduler and other stuff we all want to violently discuss sucks so bad14:23
*** manishg_ has quit IRC14:23
*** otherwiseguy has joined #openstack-meeting-alt14:23
ndipanov:)14:23
bauzasndipanov: :)14:23
johnthetubaguy#topic Gate14:23
*** openstack changes topic to "Gate (Meeting topic: nova)"14:23
*** tdruiva has quit IRC14:23
johnthetubaguyso hows the gate14:23
n0anojohnthetubaguy, you updated the etherpad, is someone going to create a spec for DB improvements?14:23
mriedemi put some links in the agenda14:23
johnthetubaguyndipanov: do try a single caching scheduler, thats actually quite fast14:23
mriedemthe gate is....kind of unknown14:23
mriedemcategorization of gate bugs is at like 58% which sucks14:23
mriedemso we have something out there, i suspect the cinder volume delete lvm/vgs hangs, that aren't tracked14:24
mriedemi'm working on tracking that today14:24
johnthetubaguylots of new bugs, or just lots of broken code up for review?14:24
johnthetubaguyOK, cool, your digging14:24
mriedemtwo bugs to mention14:24
mriedem1. https://bugs.launchpad.net/nova/+bug/1353962 - that's the fixed ips quota one14:24
uvirtbotLaunchpad bug 1353962 in nova "Test job failes with FixedIpLimitExceeded with nova network" [Undecided,Confirmed]14:24
mriedemstill need eyes on that, we have better logging now14:24
mriedem2. this is the cinder volume hang bug we're tracking https://bugs.launchpad.net/cinder/+bug/137351314:25
uvirtbotLaunchpad bug 1373513 in cinder "Lvm hang during tempest tests" [Critical,Confirmed]14:25
mriedemvgs/lvs calls are taking sometimes 2 minutes causing cinder volume deletes to timeout14:25
johnthetubaguyn0ano: I should reach out on the ML for owners and spec drivers for some of this stuff14:25
mriedemi need to get a better query up in e-r for that one today14:25
johnthetubaguymriedem: is this a review call to action, or a help thing?14:25
mriedemjohnthetubaguy: help14:25
n0anojohnthetubaguy, OK, it's just that that's a rather nebulous topic14:25
mriedemwe have a patch up for cinder to get some strace on the vgs/lvs calls but it needs some help i think14:25
johnthetubaguyn0ano: agreed14:25
mriedemhttps://review.openstack.org/#/c/126735/14:26
*** dgenin has joined #openstack-meeting-alt14:26
mriedemsomeone with rootwrap knowledge to fix that would be nice14:26
*** Barker has joined #openstack-meeting-alt14:26
johnthetubaguycool, so we are done here I guess, since no one is jumping up to discuss things?14:26
mriedemi guess14:26
mriedemmoving on14:27
johnthetubaguy#help the gate still needs more love14:27
johnthetubaguy#topic Open Discussion14:27
*** openstack changes topic to "Open Discussion (Meeting topic: nova)"14:27
*** marun has joined #openstack-meeting-alt14:27
johnthetubaguyOK, anyone got things they want to talk about?14:27
bodenI have a general question I was not able to get a response to on nova channel14:27
johnthetubaguyboden: OK, fire away14:27
bodenwhat is our stance on ec2 parity... e.g. https://bugs.launchpad.net/nova/+bug/137038414:27
uvirtbotLaunchpad bug 1370384 in nova "Cannot expand root volume by EC2 API" [Medium,In progress]14:27
johnthetubaguyboden: patches welcome, I think thats the stance14:27
*** akoneru has quit IRC14:28
johnthetubaguywe had a sub group pushing on that, but not heard a lot recently14:28
*** eglynn-office has joined #openstack-meeting-alt14:28
bodenjohnthetubaguy -- the point is we can do that workflow using existing nova resize14:28
bodendo we really need to support the ec2 "manual workflow"?14:28
johnthetubaguyboden: duno, do people want to use it?14:28
johnthetubaguyis anyone going to maintain it?14:29
mriedemboden: the other thing is we rarely get new/good working ec2/boto tests in tempest14:29
dansmithboden: I think the answer here is, it's important if someone thinks it's important and wants to work on it14:29
dansmithboden: if not, then not14:29
mriedemthe last new boto test broke the gate and was reverted14:29
*** SridharG has left #openstack-meeting-alt14:29
ndipanovjohnthetubaguy, (stepped away for a bit...) so yeah - caching is definitely one of the solutions to the db suckage :) still we should mention it at least in the meetup14:29
johnthetubaguydansmith: +1 you said what I am failing to express14:29
*** chellygel has left #openstack-meeting-alt14:29
dansmiththe lack of enthusiasm here indicates that it's not important, IMHO :)14:29
bodendansmith -- I dont mind working on it, but hanve't seen many asks14:30
bodenanyway fair enough answer14:30
bodenthanks14:30
dansmithboden: if you think it's important, then propose a spec to describe what you think needs changing and why it's important14:30
n0anodansmith, your're probably correct but that goes back to are we devloper focused or user focused, I think we've tilted too far to the developer side right nwo14:30
dansmithuntil then, there's really not much to discuss :)14:30
bodendansmith +114:30
dansmithn0ano: no developers being asked by their paying users to add that thing is a good indication to me :)14:30
johnthetubaguyanyways, lets not go down that whole14:31
johnthetubaguyany more questions?14:31
johnthetubaguydansmith: +1 I am afraid14:31
johnthetubaguyseems like we are done early14:31
n0anodansmith, maybe, I won't argue that here14:31
mriedemis cells meetup or slot?14:31
johnthetubaguymriedem: slot right now14:31
mriedemnot seeing it at the bottom of https://etherpad.openstack.org/p/kilo-nova-summit-topics14:31
dansmithwe can talk about cells for days,14:31
johnthetubaguymriedem: based on whats in my head14:31
dansmithso I think that bounding it is fine14:32
dansmithmaybe a double slot, if we're considering such things14:32
mriedemyeah i just want to see the work items/plan14:32
ndipanovjohnthetubaguy, were you looking at improving tests for cells - i kinda saw something last week or so14:32
johnthetubaguymriedem: its at the top of the "must have slots" list14:32
bauzasI was seeing a discussion about some kind of cells for the crossproject track14:32
*** akoneru has joined #openstack-meeting-alt14:32
mriedemjohnthetubaguy: ha, i wasn't scrolled up high enough apparently14:32
johnthetubaguymriedem: no worries14:32
bauzaswouldn't it be interesting to discuss about cells at a general openstack level, if we consider rebooting them ?14:33
dansmithbauzas: this conversation is not about that,14:33
dansmithbauzas: it's about fixing what we have, not rebooting cells entirely14:33
alaskibauzas: the first priority is making them a first class citizen in Nova14:33
bauzasdansmith: https://etherpad.openstack.org/p/kilo-crossproject-summit-topics L11414:34
bauzasalaski: dansmith: ack14:34
johnthetubaguybauzas: yeah, its because of an email thread14:34
dansmithokay, I'm talking about the cells discussion on our list14:34
bauzasjohnthetubaguy: but I totally understand that cells can be discussed in both sessions14:34
johnthetubaguybauzas: but yeah, nova one is talking about different things really14:34
bauzasjohnthetubaguy: got it14:34
dansmithI think the cross-project one is in  response to the cascading stuff14:34
johnthetubaguyyeah14:35
bauzasindeed14:35
johnthetubaguyanyways, seems like we are done, we can take other things to the usual channel14:35
johnthetubaguythanks all14:35
*** mriedem has quit IRC14:35
johnthetubaguy#endmeeting14:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:35
openstackMeeting ended Thu Oct 16 14:35:35 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-10-16-14.01.html14:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-10-16-14.01.txt14:35
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-10-16-14.01.log.html14:35
*** satish has quit IRC14:36
*** coolsvap is now known as coolsvap|afk14:36
*** boden has left #openstack-meeting-alt14:36
*** noslzzp has joined #openstack-meeting-alt14:38
*** k4n0 has quit IRC14:40
*** aglarendil has left #openstack-meeting-alt14:42
*** ijw has joined #openstack-meeting-alt14:42
*** tonytan4ever has joined #openstack-meeting-alt14:43
*** Riddhi has joined #openstack-meeting-alt14:45
*** Riddhi has quit IRC14:45
*** Riddhi has joined #openstack-meeting-alt14:45
*** ijw has quit IRC14:48
*** markwash__ has joined #openstack-meeting-alt14:48
*** jmontemayor has joined #openstack-meeting-alt14:49
*** apodrepniy has quit IRC14:50
*** deepakcs has joined #openstack-meeting-alt14:50
*** satish has joined #openstack-meeting-alt14:50
*** kevinconway has joined #openstack-meeting-alt14:51
*** dimtruck is now known as zz_dimtruck14:52
*** satish has quit IRC14:52
*** _amrith_ is now known as amrith14:53
*** jasonsb has joined #openstack-meeting-alt14:53
*** markwash__ has quit IRC14:54
*** bswartz has joined #openstack-meeting-alt14:55
*** satish has joined #openstack-meeting-alt14:55
*** Shamail has joined #openstack-meeting-alt14:55
*** rushil1 has joined #openstack-meeting-alt14:55
*** Shamail is now known as Shamail-Alt14:55
*** shamail has joined #openstack-meeting-alt14:56
*** _nadya_ has joined #openstack-meeting-alt14:57
*** markwash__ has joined #openstack-meeting-alt14:57
*** csaba has joined #openstack-meeting-alt14:58
*** carl_baldwin has joined #openstack-meeting-alt14:58
*** scottda has joined #openstack-meeting-alt14:59
*** ramishra has quit IRC15:00
*** cknight has joined #openstack-meeting-alt15:00
bswartz#startmeeting manila15:00
openstackMeeting started Thu Oct 16 15:00:14 2014 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: manila)"15:00
openstackThe meeting name has been set to 'manila'15:00
bswartzhello all15:00
cknightHi15:00
tbarronhi15:00
rushil1\o15:00
scottdahi15:00
vponomaryovhi15:00
jasonsbhi15:00
csabahi15:00
Shamail-Althi15:00
*** jprovazn is now known as jprovazn_afk15:00
bswartz#agenda https://wiki.openstack.org/wiki/Manila/Meetings15:01
*** georgelorch2 has quit IRC15:01
*** zz_dimtruck is now known as dimtruck15:01
bswartz#topic dev status15:01
*** openstack changes topic to "dev status (Meeting topic: manila)"15:01
bswartzwe'll start with dev status again this week15:01
vponomaryovDev status for last week:15:01
*** georgelorch has joined #openstack-meeting-alt15:01
vponomaryov1) Manila shares list API15:02
deepakcshi15:02
vponomaryovFiltering using share list API was greatly improved15:02
vponomaryovserver: #link https://github.com/openstack/manila/commit/8f0d0dc615:02
vponomaryovclient: #link https://github.com/openstack/python-manilaclient/commit/c7456c6715:02
vponomaryovstatus: merged15:02
vponomaryov2) Manila security-services list API15:02
*** xyang1 has joined #openstack-meeting-alt15:02
vponomaryovserver: #link https://review.openstack.org/12556915:02
vponomaryovclient: #link https://review.openstack.org/12624015:02
vponomaryovstatus: ready for review15:02
vponomaryov3) Manila snapshots list API15:02
vponomaryovserver: #link https://review.openstack.org/12874015:02
vponomaryovclient: #link https://review.openstack.org/12762215:02
vponomaryovstatus: work in progress15:02
*** AndroUser2 has joined #openstack-meeting-alt15:02
vponomaryov4) Horizon with Manila15:02
vponomaryovRecently was updated Horizon: #link https://github.com/NetApp/horizon/tree/manila_juno15:02
vponomaryovNow it has "share-servers" tab in admin panel.15:02
vponomaryovthat's the main15:03
bswartzcool15:03
bswartzanything that's been sitting in review too long?15:03
* bswartz has been slow on reviews this week15:03
vponomaryovlittle commit: https://review.openstack.org/12529415:04
vponomaryovwanted more opinions15:04
bswartzokay I'll review15:04
bswartzanything else/questions?15:05
*** dimtruck is now known as zz_dimtruck15:05
bswartzokay15:05
bswartz#topic design summit15:05
*** openstack changes topic to "design summit (Meeting topic: manila)"15:05
bswartz#link https://etherpad.openstack.org/p/kilo-manila-summit-topics15:05
bswartzI've been working on the etherpad, mostly down at the bottom15:06
*** stannie has quit IRC15:06
*** zz_gondoi is now known as gondoi15:06
bswartzI've tried to separate the topics into topics that would be good for the design summit, and topics that would be good to discuss during the team meetup15:06
bswartzdoes everyone understand the format for the summit this year?15:06
*** noslzzp has quit IRC15:07
bswartzI'll assume yes15:07
bswartzI've proposed 6 session so far15:08
*** shamail has quit IRC15:08
bswartzsome of them are a bit iffy, but I wanted feedback15:08
*** nshaikh has quit IRC15:09
deepakcsbswartz, can u brief quickly about the summit format if its changed from last time ?15:09
*** noslzzp has joined #openstack-meeting-alt15:09
bswartzso in addition to the "conference sessions" there will be "design summit sessions" for ATCs only just like before15:10
xyang1bswartz: we only have 3 session slots, right?15:10
bswartzhowever there will be spots for us to meetup on Friday15:10
*** ramishra has joined #openstack-meeting-alt15:10
bswartzand discuss things in a smaller group15:10
bswartzwe have 3 design summit sessions15:10
bswartzand those will likely be attended by all kinds of people who just want to learn about what we're doing15:11
bswartzthe team meetup will be much smaller I'm sure, with no published agenda15:11
deepakcsbswartz, thanks15:11
vponomaryovbswartz: about topic "Potential Session: Manila Scheduler"15:12
bswartzso the 6 sessions I've proposed have topics which may appeal outside our team15:12
vponomaryovwhat exactly is planned to be disscussed?15:12
*** tdruiva has joined #openstack-meeting-alt15:13
bswartzvponomaryov: I'm thinking the discussion would be about specific capabilities we should report and general good practice for setting up a multibackend manila installation15:13
*** kopparam has joined #openstack-meeting-alt15:14
jasonsbi would be interested in attending the team meetup (for the image project)15:14
bswartzwell if anyone feels that a topic (from the etherpad) is in the wrong place we can move it15:14
*** haleyb has joined #openstack-meeting-alt15:14
bswartzwe could do a design summit session on the image project15:14
*** tedross has quit IRC15:14
vponomaryovbswartz: so, main idea - extend existing functionality with manila specific stuff and define what exactly should be addded, correct?15:14
xyang1bswartz: each session is 40 minutes.  So it's unlikely we can fit all 6 sessions in the 3 session slots15:15
*** nshaikh has joined #openstack-meeting-alt15:15
*** rcleere is now known as rcleere_away15:15
bswartzyes I wanted to propose more sessions than we have time for do you all can downvote the ones that you don't like15:15
bswartzwe can still discuss those topics in the meetup15:15
*** noslzzp has quit IRC15:15
xyang1sure15:16
bswartzIn a few minutes I'll ask about each one and see if we can collect the votes15:16
bswartzbut first I had some questions15:16
bswartzto answer vponomaryov: yes15:16
*** EricGonczer_ has joined #openstack-meeting-alt15:17
bswartzwe can spend some more time sketching out specifics if it's a topic people are interested in -- I have a lot of ideas15:17
bswartzso vponomaryov, you put a few things on the etherpad I didn't understand15:17
bswartz      * share groups as server groups in Nova15:17
bswartz      * proper calculation of snapshot size? 15:17
*** noslzzp has joined #openstack-meeting-alt15:17
*** diemt has joined #openstack-meeting-alt15:18
bswartzcan you briefly explain those15:18
vponomaryov* share groups as server groups in Nova - create several shares at a time and group them somehow15:18
*** markwash__ has quit IRC15:18
vponomaryov * proper calculation of snapshot size? - snapshot takes quota of share equal to its size and does not allow to spawn share from it with less size than snapshot has defined in manila15:18
*** kopparam has quit IRC15:19
*** azemlyanov has quit IRC15:19
bswartzokay15:19
vponomaryovfirst one is useful when we know that we want create N shares15:19
vponomaryovand we will use them for some specific case15:20
bswartzI can see pros/cons for the first one15:20
rushil1vponomaryov: Is there a way you have thought about grouping the shares?15:20
bswartzit seems worth of discussion -- but do you think it would make a good design summit session?15:20
vponomaryovbswartz: need collect desires of end users15:20
*** AlanClark has joined #openstack-meeting-alt15:21
vponomaryovbswartz: this idea pop up from WFA project15:21
bswartzokay15:21
*** AndroUser2 has quit IRC15:21
*** ramishra has quit IRC15:22
bswartzand on the second topic, I feel like we discussed it before and reached a conclusion we were okay with15:22
bswartzsince we can't know whether backends will store snapshots efficiently or not, we charge them the full quota just in case15:23
vponomaryovbswartz: we can allow force usage in cases we know it for sure15:23
bswartzasking backends to report how much space a snapshot consumes requires a lot more implementation in the drivers15:23
bswartzand worse, it could change over time15:23
*** gyee has joined #openstack-meeting-alt15:24
bswartzI suppose there could be an upper bound we could report that's less than the total share size15:24
bswartzis that what you're going for?15:24
vponomaryovbswartz: yes15:25
*** _nadya_ has quit IRC15:25
vponomaryovfor example we can have size of 100Gb for share and snapshot will take additional 100Gb15:25
vponomaryovthis huge leak of quota15:25
vponomaryovand use some couple of Gb indeed15:25
bswartzbut some backends may literally require 100GB for the snapshot15:25
bswartzmaybe we should look at doing this in an extension, or with some way for the administrator to turn it off15:26
bswartzI like the idea, but it creates some cracks in the abstraction we're trying to create15:27
vponomaryovso, we can conclude that this topic does not have strict borders, though I added it15:27
bswartzyes -- do you think it makes sense for a design summit talk?15:27
vponomaryovNot sure, there are important topic too15:28
bswartzokay15:28
vponomaryovs/topic/topics/15:28
csababswartz: is it still possible to add topics to the pad?15:28
vponomaryovwe can "live" with it15:28
vponomaryovbut can not, for example, without image15:28
bswartzcsaba: if you have an idea mention it here15:29
*** Shamail-Alt has quit IRC15:29
vponomaryovso, topic with image should be in top of priority, I think15:29
*** armax has quit IRC15:29
xyang1bswartz: do you need to choose 3 topics and put them down here?  http://kilodesignsummit.sched.org/15:30
bswartzmanila image project? you think it should be a design summit session rather than a meetup topic?15:30
bswartzxyang1: yes15:30
vponomaryovbswartz: any15:30
bswartzxyang1: although we can put 2 topics in one session if we wish15:30
csababswartz: I have some gripes with how execution works in manila, but I can't articulate them properly ATM, I need a bit time to think it over15:30
xyang1ok15:30
bswartzcsaba: were you thinking of having a session to review your gripes? or did you just want to bring them to the team meetup?15:31
vponomaryovcsaba: if it would not provide gripes we would not have topics =)15:31
bswartzwe could just have a whole session where everyone stands up and gripes about what they don't like -- it might be cathartic15:32
csabavponomaryov: the point is to soothe the gripes ;_15:32
bswartzcsaba: I'd like to get the design summit schedule nailed down in the next few days, so if you want to propose a session then we need to know urgently15:33
csabaATM I would not propose this for a whole session15:33
bswartzother topics, for the meetup, can wait15:33
csababswartz: I can let you know by tomorrow15:33
bswartzokay so now I'd like to just go through the list and hear from you +1 or -1 on design summit worthiness15:34
bswartzthe first one is: Manila Networking15:34
bswartzthis one gets a +1 from me15:34
vponomaryov+115:34
xyang1+115:34
jasonsb+115:34
bswartzsorry the details in the etherpad are sparse -- there's more detail above15:35
bswartzokay15:35
bswartznext topic: Integration with other projects15:35
bswartzPersonally I feel like -1 on this, even though it may have broad interest15:36
xyang1This topic seems open ended15:36
bswartzwe would discuss specific integration with * Tempest* Horizon* Devstack* Heat15:36
bswartzthe discussion could be short though15:36
*** rcleere_away is now known as rcleere15:36
bswartzwe could handle this one during the meetup15:36
jasonsbexpose snapshot usage to other project?15:37
bswartzbut then we won't get members of those other projects15:37
vponomaryovbswartz: I am Ok to leave for meetup15:37
bswartz+1/-1?15:37
vponomaryov/leave/leave it/15:37
jasonsb(accounting/chargeback purposes)15:37
rushil1-115:37
vponomaryov+1 push it to meetup15:37
bswartzjasonsb: that would just be a new feature for our API, assuming we implement a way to query backends for snapshot actual space consumption15:38
xyang1good topic, but won't be productive for a session15:38
xyang1meetup sounds good15:38
*** shakamunyi has joined #openstack-meeting-alt15:38
bswartzintegration refers to when we actually add code to other projects to make them work better with manila15:38
bswartzokay we can move on15:38
jasonsbah, ok15:38
bswartzNext topic: Mount Automation15:39
bswartz+1 from me15:39
xyang1if you already have concrete ideas, then this should be a good one15:40
vponomaryovbswartz: We definitely need get nailed what exactly do we want to get with this feature15:40
bswartzwe've never discussed this topic if deep detail, and people keep asking for it15:40
bswartznow feels like the time to finally do it15:40
vponomaryovso +115:40
bswartzI do have concrete ideas15:40
bswartzand I can easily see this one going the full 40 minutes15:41
xyang1+115:41
bswartzok15:41
jasonsb+115:41
bswartznext topic: Review features to steal from Cinder15:41
*** georgelorch2 has joined #openstack-meeting-alt15:42
bswartzso the exact list of features we cover in this session could be revised, but the idea is to have a multi-topic session on various cinder features15:42
bswartzand talk about the specifics of adapting them to manila15:42
bswartzstuff like private volume_type/share_type should be pretty trivial I think15:42
*** richm has quit IRC15:42
bswartzwhereas manage/unmanage might be quite complicated given the differences15:42
*** georgelorch has quit IRC15:43
bswartzI'm on the fence about this one15:43
vponomaryov+115:43
rushil1-115:43
*** ijw has joined #openstack-meeting-alt15:44
bswartzrushil what would you prefer?15:44
xyang1This seems to be more than we can cover, not focused15:44
rushil1bswartz: Don't think this needs to go for a full session when this has already been covered in cinder15:44
bswartzxyang: well we could focus it15:44
deepakcsbswartz, ability to manage existing share would be good to have, as that would help manila takeover a existing implementation15:44
bswartzwe could pick 2 or 3 high priority ones and make the session about those15:44
rushil1bswartz: We could cover it, but don't need to dedicate a whole session to it15:45
deepakcsbswartz, vponomaryov I see you said share_type is available, does that mean Manila supports the multi-backend as Cinder does (1 m-shr process per backend) ?15:45
bswartzrushil1: actually we could take a single one of those and turn it into a whole session if we wanted15:45
bswartzstuff like backup and replication are HUGE topics15:45
bswartzdeepakcs: yes15:45
bswartzdeepakcs: although currently we use the term "volume_type" not share_type15:46
rushil1bswartz: I get that. But I feel the audience would be cinder aware and should be aware of the concepts being covered.15:46
xyang1yes, those topics are huge, each one will be one session.  we definitely need to nail down15:46
bswartzokay so this one needs reworking if we're going to include it15:46
vponomaryovrushil1: the goal to get know what we can adapt and why we should do it15:46
bswartzwe have to do the activity of reviewing all these and scoping/prioritizing them15:47
bswartzbut maybe that's not appropriate to do in paris15:48
bswartzmaybe once we have concrete proposals for each one we should consider presenting them15:48
bswartzI'll propose that we do that reviewing/scoping/prioritizing in a future meeting15:49
*** ijw has quit IRC15:49
bswartzokay since we're running out of time let's move on15:49
*** tedross has joined #openstack-meeting-alt15:49
bswartznext topic: Access Groups15:49
jasonsbi would be interested in hearing about thoughts on DR at the pod15:49
xyang1straight forward ones don't need a session15:49
jasonsbif anybody is interested15:49
*** kevincon_ has joined #openstack-meeting-alt15:49
*** apodrepniy has joined #openstack-meeting-alt15:49
bswartzjasonsb: sure15:49
*** IvanKliuk has joined #openstack-meeting-alt15:49
bswartzaccess groups is something that's very concrete and could merge during kilo-115:50
*** kevinconway has quit IRC15:50
bswartzI think it deserves a session15:50
vponomaryovbswartz: but this is related to v215:50
bswartzis it interesting enough though?15:50
*** paboldin has joined #openstack-meeting-alt15:51
*** ihrachyshka has quit IRC15:51
bswartzvponomaryov: it could be done in v1 -- all the APIs are new and don't break anything15:51
rushil1+1, I think access groups deserves a session.15:51
*** angdraug has joined #openstack-meeting-alt15:51
vponomaryovbswartz: it contradicts to current share access approach, is not it?15:51
*** rmoe has quit IRC15:51
bswartzit extends the current approach15:51
*** Barker has quit IRC15:52
bswartzjust makes it possible to apply access rules to multiple shares at a time15:52
vponomaryovbswartz: ok, I just did not see implementation you are talking about15:52
bswartzand makes it possible for access rules to change in response to events rather than explicit API calls15:52
*** tsv has joined #openstack-meeting-alt15:52
*** padkrish has joined #openstack-meeting-alt15:53
bswartzthe driver interface would have to change but there would be no API breakage15:53
bswartzif this becomes a session we will post the details in advance15:53
bswartzany last opinions?15:54
vponomaryovis there issues for it?15:54
bswartzwe have 1 more15:54
xyang1+1 for access groups15:54
*** david-lyle has quit IRC15:54
bswartzvponomaryov: hopefully no, but the session would allow people to raise them if they had issues15:54
vponomaryovOk, I don't mind15:55
bswartzcknight worked on this during juno and I think he got most of the design decisions right15:55
*** richm has joined #openstack-meeting-alt15:55
bswartzameade too if he's here15:55
bswartzokay last one15:55
*** smazziotta has joined #openstack-meeting-alt15:55
bswartztopic: Manila Scheduler15:55
bswartzwe sort of discussed this one already15:56
*** Tatyanka_Leontov has joined #openstack-meeting-alt15:56
bswartzI'm on the fence about this one15:56
vponomaryovlow priority15:56
bswartzyou say -1?15:56
*** nkrinner has quit IRC15:56
vponomaryov-1 because there are should be more prioritized thing, I guess15:56
bswartzanyone else thing we *should* make a session about scheduler enhancements?15:56
bswartzs/thing/think/15:57
xyang1I think if we have time we can go over it, otherwise it is fine to skip15:57
rushil1This can be discussed, but not a whole session. -115:57
xyang1or discuss about it later in meetup15:57
bswartzokay I think that one is clear15:57
bswartzso just to review, the 3 highest vote getters (by my count) are:15:57
xyang1actually the pool one is a scheduler change as well15:57
bswartzManila Networking15:58
bswartzMount Automation15:58
bswartzAccess Groups15:58
rushil1bswartz: +115:58
ameadei'm fine with that15:58
xyang1sounds good15:58
*** mihgen has joined #openstack-meeting-alt15:58
bswartzintegration and scheduler we will discuss privately, and the cinder feature list needs more work before we'd have anything to present15:58
*** asyriy has joined #openstack-meeting-alt15:58
*** vkramskikh has joined #openstack-meeting-alt15:59
*** bookwar has joined #openstack-meeting-alt15:59
*** aglarendil has joined #openstack-meeting-alt15:59
bswartzokay so I'll watch the ML and IRC for any amazing new ideas15:59
*** dpyzhov has joined #openstack-meeting-alt15:59
bswartzbut baring something new that everyone wants those 3 will be the proposal15:59
bswartzsorry we ran out of time for open discussion16:00
bswartzthanks all16:00
vponomaryovthanks16:00
rushil1thanks16:00
xyang1thanks16:00
jasonsbthank all16:00
deepakcsbye16:00
bswartz#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Oct 16 16:00:30 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
*** evgeniyl__ has joined #openstack-meeting-alt16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-10-16-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-10-16-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-10-16-15.00.log.html16:00
*** ntrueblood has joined #openstack-meeting-alt16:00
*** rushil1 has left #openstack-meeting-alt16:00
mihgenhi folks16:00
vkramskikhhi16:00
*** csaba has left #openstack-meeting-alt16:00
aglarendilhi16:00
*** deepakcs has quit IRC16:00
*** xarses has joined #openstack-meeting-alt16:01
*** jasonsb has left #openstack-meeting-alt16:01
*** armax has joined #openstack-meeting-alt16:01
*** kozhukalov has joined #openstack-meeting-alt16:01
kozhukalovhey guys16:01
agordeevhi16:01
kozhukalov#startmeeting Fuel16:01
openstackMeeting started Thu Oct 16 16:01:58 2014 UTC and is due to finish in 60 minutes.  The chair is kozhukalov. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: Fuel)"16:02
openstackThe meeting name has been set to 'fuel'16:02
kozhukalov#chair kozhukalov16:02
openstackCurrent chairs: kozhukalov16:02
kozhukalovagenda as usual16:02
kozhukalov#link https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda16:02
kozhukalovwho is here?16:02
*** rkukura_ has joined #openstack-meeting-alt16:02
christopheraedoHello!16:02
mattymohi all16:02
*** akasatkin has joined #openstack-meeting-alt16:02
*** rkukura_ is now known as rkukura16:02
*** Stanzi has joined #openstack-meeting-alt16:03
kozhukalovok, let's start our discussion16:03
aglarendilhi16:03
kozhukalov#topic Summary for usage stats collection (mihgen)16:03
*** openstack changes topic to "Summary for usage stats collection (mihgen) (Meeting topic: Fuel)"16:03
xarseso.16:03
*** Stanzi has quit IRC16:03
*** EricGonczer_ has quit IRC16:03
mihgenhey, I'm just from the webex discussion on this topic16:03
mihgenbasically we wonna get following stats:16:04
mihgena) static, like configuration of deployment16:04
*** Stanzi has joined #openstack-meeting-alt16:04
mihgenb) usage patterns of openstack, how users use it16:04
*** ajo_ has joined #openstack-meeting-alt16:04
mihgenc) support cases - know about failures users experience16:04
mihgenfor a) it's more or less designed, kozhukalov - please help to find blueprint16:05
mihgenfor b) it's large discussion actually. Ideally we would use ceilometer if we can configure it for very low amount of info16:05
mihgenotherwise it can blow up quickly on even 50 nodes16:05
*** tzn has joined #openstack-meeting-alt16:06
kozhukalov#link https://blueprints.launchpad.net/fuel/+spec/anonymous-statistics-performance-testing16:06
kozhukalovam I right?16:06
mihgenwe can't force user to install ceilometer, so we could do it on Fuel master node16:06
mihgenkozhukalov: yep, thx16:06
*** dgenin has quit IRC16:06
mihgenbut looks like for first iteration we should just go ahead with something really trivial as we don't have resources to research other ways any deep16:07
kozhukalovI was wrong16:07
kozhukalovright link is16:07
mihgenkozhukalov: yeah, another bp16:07
kozhukalov#link https://blueprints.launchpad.net/fuel/+spec/send-anon-usage16:07
mihgenso easiest thing would be to just do REST API call to openstack16:07
*** rmoe has joined #openstack-meeting-alt16:07
mihgenit16:07
*** jergerber has joined #openstack-meeting-alt16:08
mihgenit's not gonna show dynamic / trends of usage, though we can get periodic snapshots of what is going on the cluster16:08
mihgenthat's short summary. Any questions on this / comments?16:08
*** HeOS has quit IRC16:09
mihgenkozhukalov: let's move on16:09
kozhukalovok, looks like no q16:09
kozhukalov#topic Juno status (mattymo)16:09
*** openstack changes topic to "Juno status (mattymo) (Meeting topic: Fuel)"16:09
mattymoHi kozhukalov!16:10
*** zns has joined #openstack-meeting-alt16:10
mattymoGreat improvement from last week's turbulent events. Everything is very stable and we're working through minor bugs now.16:10
kozhukalovmattymo: hi16:10
mattymoWe fixed a bug in nova-network this week that was blocking instances from getting internet access, along with HA MongoDB.16:10
mattymoAll components are working, but we have a floating bug of failing to deploy instances on CentOS in HA that is hard to reproduce.16:10
mattymoWe've already passed all BVTs and now new features can be added on top of vanilla Juno, including our memcached improvements for keystone.16:10
mihgen#link https://wiki.openstack.org/wiki/Fuel#Nightly_builds16:10
mattymoMaster ISO for 6.0 is now juno and works great, but please report any bugs you see, large or small.16:10
mihgenanyone can get ISO from there. Choose 6.0 to get Juno16:10
mihgenmattymo: thanks you for driving it through!16:11
mattymoI learned a lot, so it was worth it16:11
mattymoThat's all I have for my update.16:11
mihgen:)16:11
mihgenthx16:11
kozhukalovso, now we can add packages into 6.0 mirror, right?16:11
*** luizfar has joined #openstack-meeting-alt16:11
mattymokozhukalov, yes! Please do16:11
mihgenkozhukalov: of course16:11
kozhukalovrvyalov: can we?16:11
*** scottda has left #openstack-meeting-alt16:11
rvyalovyes16:11
*** nosnos has quit IRC16:12
*** Longgeek has quit IRC16:12
*** balajiiyer has left #openstack-meeting-alt16:12
rvyalovbut if it is new packages, need add it 6.0-icehouse too16:12
*** nosnos has joined #openstack-meeting-alt16:12
kozhukalovok, there was PR about adding mdadm to ubuntu16:12
*** padkrish has quit IRC16:12
dpyzhovShould we get rid of 6.0-icehouse?16:13
kozhukalovhas it merged?16:13
mattymodpyzhov, we haven't finished cherry-picking non-merged upstream patches on top of juno yet16:13
*** padkrish has joined #openstack-meeting-alt16:13
*** manishg has joined #openstack-meeting-alt16:13
mattymolet's keep it until we're done on that end16:13
kozhukalov#link https://review.openstack.org/#/c/127163/16:13
dpyzhovok16:13
kozhukalovthis one16:13
mihgendpyzhov: nope yet16:13
mihgenthere were issue16:13
mihgenfixed by aglarendil today16:13
dpyzhovDoes juno passed nightly tests?16:13
mihgenI want to get status first that we don't see random regressions first16:14
*** marcoemorais has joined #openstack-meeting-alt16:14
*** openstackstatus has joined #openstack-meeting-alt16:14
*** ChanServ sets mode: +v openstackstatus16:14
mihgenonce we are stable there and there, we should drop 6.0-icehouse16:14
mihgenanother question to devops16:14
mihgenwhat do we use for Fuel CI now16:14
mihgenfor fuel-library checks16:14
mihgenicehouse or we switched to juno packages?16:14
mihgenbookwar: teran_ nurla ^^^16:14
*** HeOS has joined #openstack-meeting-alt16:14
kozhukalovany other q?16:14
xarsesmihgen: i'd like to know too16:15
bookwarmihgen: we tested juno iso and it failed16:15
*** kopparam has joined #openstack-meeting-alt16:16
bookwarmihgen: currently it continues to use very old icehouse iso image16:16
bookwarqa team works on fixing the tests16:16
xarsesyuck16:16
mihgenbookwar: failed what?16:16
mihgenany bug? BVT passes, so what fails?16:16
*** manishg_ has joined #openstack-meeting-alt16:16
bookwarhttps://fuel-jenkins.mirantis.com/job/master_fuellib_review_systest_ubuntu/2826/console16:16
*** nosnos has quit IRC16:17
bookwarthe empty test on already merged fuel-library code ^^16:17
mihgenbookwar: nice, good test.16:17
mihgenbookwar: any bug on that? who is working on fixing it?16:17
*** nshaikh has quit IRC16:17
mihgenit's important to quickly switch to juno packages in Fuel CI16:18
*** manishg has quit IRC16:18
*** padkrish has quit IRC16:18
bookwarit is supposed to be cuased by this patch https://review.openstack.org/#/c/128680/ ddmitriev will take a look, if it takes more than half an hour, i'll file a bug16:18
nurlaDennis are working on fix16:18
*** tsv has quit IRC16:19
mihgennurla: why don't we just revert it for now?16:19
*** noslzzp has quit IRC16:19
mihgenand then provide a better fix?16:19
mihgentrying to fix of the fix of the wrong fix doesn't always work as expected :)16:19
-openstackstatus- NOTICE: An error in a configuration change to mitigate the poodle vulnerability caused a brief outage of git.openstack.org from 16:06-16:12. The problem has been corrected and git.openstack.org is working again.16:19
bookwarwe are not sure about the reason yet, we need some time for debugging16:20
mihgenok16:20
nurlawe've have same passed tests against 6.0 iso, if dennis can't find problem in hour16:20
kozhukalovmoving on?16:20
mihgenall right, ddmitriev wokring on it?16:20
nurlai'll revert fix16:20
*** manishg has joined #openstack-meeting-alt16:20
nurlayep16:20
mihgenok, thanks16:20
mihgenlet's move on then16:20
*** manishg_ has quit IRC16:20
kozhukalov#topic Gerrit move status (rvyalov)16:20
*** openstack changes topic to "Gerrit move status (rvyalov) (Meeting topic: Fuel)"16:20
rvyalovwe deploy new gerrit instance. we move all non openstack packages and openstack specs to gerrit instance . All the repositories in old gerrit will be read-only access to create request/merge and etc16:21
*** kopparam has quit IRC16:21
rvyalovWe planned to move to current 17/10 Friday16:21
mihgenrvyalov: excellent16:21
mihgenrvyalov: looking forward to see us being able to build ISO with pure vanilla openstack code16:21
*** david-lyle has joined #openstack-meeting-alt16:21
*** ramishra has joined #openstack-meeting-alt16:22
kozhukalovcool )16:22
angdraugme too. is that the next step?16:22
angdraugor is there anything else we have to do first?16:22
mihgenangdraug: yes. This is pre-requisite for many other things16:22
mihgenas I undertand - rvyalov please correct if not16:22
*** sarob has joined #openstack-meeting-alt16:23
rvyalovyes, we can use public gerrit for get openstack specs and build openstack packages when building ISO16:23
*** manishg_ has joined #openstack-meeting-alt16:23
rvyalovwe publish all openstack specs for deb and rpm16:23
*** bdpayne has joined #openstack-meeting-alt16:23
mihgenok, let's cross fingers - I'm expecting to see gerrit working on the weekend :)16:24
kozhukalov#topic Decreasing the size of upgrade tarball (kozhukalov)16:24
*** openstack changes topic to "Decreasing the size of upgrade tarball (kozhukalov) (Meeting topic: Fuel)"16:24
kozhukalovthe progress here is quite good16:24
kozhukalovthere are PRs16:24
kozhukalov#link https://review.openstack.org/#/c/128323/16:24
*** manishg has quit IRC16:25
*** manishg_ is now known as manishg16:25
kozhukalovabout upgrade script16:25
kozhukalov#link https://review.openstack.org/#/c/124734/16:25
*** padkrish has joined #openstack-meeting-alt16:25
kozhukalovabout make system16:25
kozhukalovI still need to add some code to last one16:25
mihgenkozhukalov: what's going to be the decrease in %?16:26
mihgenfrom what would be if we don't do it?16:26
*** jcoufal has quit IRC16:26
kozhukalovI believe on Monday-Tuesday we'll be ready to show a demo16:26
kozhukalovI still don't know exactly16:26
mihgenkozhukalov: any testing was already done with repos? Just want to make sure we don't face some weirdness with repos / yum / apt-get16:26
kozhukalovone of estimations was 50%16:26
angdraugspec is still in review16:27
angdraug#link https://review.openstack.org/#/c/121591/16:27
kozhukalovyes, Serge Kulanov has tested his patch16:27
kozhukalovand he was able to create a diff repo16:27
mihgenwhat do we need to complete the spec?16:27
kozhukalovwe decided to use md5 sums to figure out which packages we need to add into a diff repo16:28
*** sarob has quit IRC16:28
*** tdruiva has quit IRC16:28
kozhukalovangdraug: yes, I just didn't have enough time to review them16:28
kozhukalovmihgen: we need to add another patch to make system so as to be able to insert diff repos into tarball16:29
mihgenkozhukalov: ok, thanks. Let's get reviewers..16:29
*** lsmola has quit IRC16:29
kozhukalovmihgen: ok16:29
kozhukalovmoving on16:30
kozhukalov#topic Image based provisioning (kozhukalov)16:30
*** openstack changes topic to "Image based provisioning (kozhukalov) (Meeting topic: Fuel)"16:30
kozhukalovtoday around 10 PRs were merged16:30
*** shakamunyi has quit IRC16:30
*** tedross has quit IRC16:31
kozhukalovlast week we decided to implement choosing which provision scheme to use as a radio button on a setting tab16:31
mihgenkozhukalov: hmm where do you get reviewers for them?)16:31
kozhukalovit is already merged16:31
*** lpabon has joined #openstack-meeting-alt16:31
mihgenkozhukalov: radio button is great. So it's just per env setting?16:32
*** tdruiva has joined #openstack-meeting-alt16:32
kozhukalovthey were D Shulyak, A Kasatkin and A Gordeev16:32
mihgenyou can choose to provision one env with old anaconda, another - image-based?16:32
kozhukalovmihgen: exactly16:32
mihgenkozhukalov: what's the overall status? how much work is left still? any serios issues?16:33
kozhukalovso we still need to add mdadm package to ubuntu mirror16:33
kozhukalovand merge image building scripts16:33
kozhukalovwhich were under work last days16:33
kozhukalovi hope it just some bugs are still needed to be fixed and that is it16:34
*** ramishra has quit IRC16:34
kozhukalovone of the members of QA team has already touched this feature16:34
kozhukalovany other q?16:35
*** kevincon_ has quit IRC16:35
kozhukalovok moving on then16:35
kozhukalov#topic Upstream neutron manifests (xenolog)16:36
*** openstack changes topic to "Upstream neutron manifests (xenolog) (Meeting topic: Fuel)"16:36
xenologISO with June and upstream Neutron is ready (custom ISO #65).16:36
xenologI tested it by hands.16:36
xenologSystem tests (#126, #127, #128) is going now.16:36
xenologMy opinion -- changes ready to merge, iso -- for QA team.16:36
xenologNeutron team also tested lastest changes.16:36
kozhukalovxenolog thanx16:38
kozhukalovany q?16:38
*** akasatkin has left #openstack-meeting-alt16:38
mihgenxenolog: thx16:38
angdraugxarses: how's review status of ^16:38
kozhukalovwe still have 20 minutes16:38
mihgenwhat are we waiting for merging this?16:38
mihgenaglarendil: angdraug - ^^16:38
mihgenwhen can we merge upstream puppet modules for neutron16:39
aglarendilmihgen: we are waiting for custom tests to pass16:39
aglarendilmihgen: custom bvts i mean16:39
aglarendilmihgen: with latest master16:39
*** dmahony has quit IRC16:39
aglarendilmihgen: and upstream neutron code16:39
angdraugreview by xarses from yesterday requested some coding style changes, are all these now addressed?16:39
*** kevinconway has joined #openstack-meeting-alt16:40
*** zeddii has quit IRC16:40
aglarendilangdraug: I am not aware of them16:40
aglarendilangdraug: could you send particular links, please?16:40
angdraug#link https://review.openstack.org/#/c/103280/16:41
xarsesangdraug: correct, mostly stile issues, I will check in the AM, there was a note on the card that there where rebase changes I'll probably poke around there16:41
angdraug#link https://review.openstack.org/#/c/103279/16:41
*** kevinconway has quit IRC16:41
*** kevincon_ has joined #openstack-meeting-alt16:41
angdraug#link https://review.openstack.org/#/c/103278/2816:41
xarsess/stile/style16:41
angdraug#link https://review.openstack.org/#/c/126010/16:42
angdraug#link https://review.openstack.org/#/c/126414/16:42
*** Stanzi_ has joined #openstack-meeting-alt16:42
*** Stanzi has quit IRC16:42
aglarendilangdraug: xarses actually, I do not see any -1's from Andrew there16:43
*** tsekiyama has joined #openstack-meeting-alt16:43
*** tdruiva has quit IRC16:43
xarsesthanks angdraug16:43
*** _nadya_ has joined #openstack-meeting-alt16:43
angdraugaglarendil: see patchset 52 in https://review.openstack.org/#/c/103280/16:43
xarsesxenolog: you fixed the issue you noted in the card with the iso being broken?16:44
xenologbroken was previous ISO16:44
xarsesok16:44
*** lsmola has joined #openstack-meeting-alt16:44
*** ijw has joined #openstack-meeting-alt16:45
kozhukalovok, guys16:46
kozhukalovlooks like we have nothing to discuss any more16:46
mihgenthanks fokls16:46
mihgenfolks*16:46
kozhukalovending?16:46
*** luizfar has quit IRC16:46
*** evgeniyl__ has left #openstack-meeting-alt16:46
mihgenhave a good day!16:46
kozhukalovthanx everyone16:47
kozhukalov#endmeeting16:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:47
openstackMeeting ended Thu Oct 16 16:47:15 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fuel/2014/fuel.2014-10-16-16.01.html16:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fuel/2014/fuel.2014-10-16-16.01.txt16:47
*** Tatyanka_Leontov has left #openstack-meeting-alt16:47
openstackLog:            http://eavesdrop.openstack.org/meetings/fuel/2014/fuel.2014-10-16-16.01.log.html16:47
*** luizfar has joined #openstack-meeting-alt16:47
*** angdraug has left #openstack-meeting-alt16:49
*** armax has left #openstack-meeting-alt16:50
*** ijw has quit IRC16:50
*** tedross has joined #openstack-meeting-alt16:50
*** derekh has quit IRC16:50
*** dpyzhov has left #openstack-meeting-alt16:51
*** zns has quit IRC16:52
*** markwash__ has joined #openstack-meeting-alt16:52
*** yamahata has quit IRC16:52
*** matrohon has quit IRC16:53
*** Stanzi_ has quit IRC16:53
*** Stanzi has joined #openstack-meeting-alt16:54
*** dims_ has quit IRC16:55
*** otherwiseguy has quit IRC16:55
*** rcleere is now known as rcleere_away16:55
*** dims_ has joined #openstack-meeting-alt16:55
*** coolsvap|afk is now known as coolsvap16:55
*** Stanzi has quit IRC16:56
*** HeOS has quit IRC16:57
*** rlpple has joined #openstack-meeting-alt16:57
*** bknudson has joined #openstack-meeting-alt16:58
*** tmcpeak has joined #openstack-meeting-alt16:58
*** rcleere_away is now known as rcleere16:59
*** chair6 has joined #openstack-meeting-alt16:59
*** nkinder has joined #openstack-meeting-alt17:00
*** HeOS has joined #openstack-meeting-alt17:00
*** rcleere is now known as rcleere_away17:00
*** rcleere_away is now known as rcleere17:00
*** shohel02 has joined #openstack-meeting-alt17:00
*** sicarie has joined #openstack-meeting-alt17:01
*** julienvey has quit IRC17:01
tmcpeakwasssup!?17:01
chair6hola!17:01
bknudsonossg meeting today?17:01
shohel02hi17:01
nkindertmcpeak: welcome back!17:01
tmcpeaknkinder: thank you sir :)17:01
*** IvanKliuk has left #openstack-meeting-alt17:02
*** tdruiva has joined #openstack-meeting-alt17:02
bdpaynehey guys17:02
tmcpeakyo!17:02
tmcpeakhyakuhei is on his way17:02
bknudsonwe're all too busy dealing with the vulnerability of the week.17:02
*** lpabon has left #openstack-meeting-alt17:03
bdpayneheh17:03
bdpaynethere is some truth to that17:03
*** sarnold007 has joined #openstack-meeting-alt17:03
nkindercan't wait to see what next week has in store...17:03
bdpayneshohel02 I'm sending you an email now :-)17:03
bdpayneshohel02 Re elections17:03
shohel02okey17:03
bknudsonI couldn't figure out from the poodle description if there's a client vulnerabiity, too.17:03
hyakuhei_Hey :)17:03
*** hyakuhei_ is now known as hyakuhei17:03
*** hyakuhei has quit IRC17:04
*** hyakuhei has joined #openstack-meeting-alt17:04
*** sgotliv has quit IRC17:04
*** lpabon has joined #openstack-meeting-alt17:04
hyakuhei#startmeeting openstack security group17:04
*** _nadya_ has quit IRC17:04
openstackMeeting started Thu Oct 16 17:04:23 2014 UTC and is due to finish in 60 minutes.  The chair is hyakuhei. Information about MeetBot at http://wiki.debian.org/MeetBot.17:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:04
*** openstack changes topic to " (Meeting topic: openstack security group)"17:04
openstackThe meeting name has been set to 'openstack_security_group'17:04
rlpple#info17:04
hyakuheiHi all, sorry I'm late, how is everyone ?17:04
tmcpeakwoo \o/17:04
sarnold007Helllo17:04
*** balajiiyer has joined #openstack-meeting-alt17:05
bknudsonhi17:05
hyakuheiGreat, so agenda wise I don't have a big list as I've been tied up in stuff this week17:05
hyakuheiI'd like to talk about Swift encryption and the elections17:05
hyakuheiwhat else?17:06
nkinderpoodle?17:06
nkinderossn status17:06
shohel02threat modeling status17:06
hyakuheiGreat17:06
*** aglarendil has left #openstack-meeting-alt17:06
hyakuheiOk well lets plough on then I guess.17:06
hyakuheiWho's been following the swift encryption spec?17:06
nkinderI've looked it over a bit17:07
hyakuhei#link https://review.openstack.org/#/c/123220/17:07
tmcpeakstill meaning to do a thorough review17:07
hyakuheiIt got pretty messy between patchsets 3 and 417:07
hyakuheiThere's a few things that are a bit off or not in line with best practice, I'm hoping the OSSG can help with this.17:08
*** yamahata has joined #openstack-meeting-alt17:08
hyakuheiIf no one has any opinions they want to share we can move on :)17:08
notmynameunfortunately, I'm in a meeting right now and can't fully participate here, but I'm talking with sam about it17:09
hyakuheicool, thanks notmyname - my feeling is that there's alot of good thinking there17:09
*** noslzzp has joined #openstack-meeting-alt17:09
*** daneleblanc has joined #openstack-meeting-alt17:10
hyakuheinotmyname: let me know if I can help17:10
*** cbouch has joined #openstack-meeting-alt17:10
hyakuheiI guess we'll move it on to the Elections then17:10
*** rcleere is now known as rcleere_away17:10
hyakuhei#topic elections17:11
*** openstack changes topic to "elections (Meeting topic: openstack security group)"17:11
bdpaynehey guys17:11
bdpayneso we have an election now with two people in the running17:11
hyakuheiSo far we have two candidates, myself and Cody Bunch from Rackspace (one of the authors of the security guide)17:11
bdpayneyeah, what he said17:11
hyakuhei:)17:11
tmcpeakhow do we vote?17:12
bdpayneYou will get an email with instructions next week17:12
bdpayneMonday, if all goes well17:12
tmcpeakcool17:12
bdpayneit will be just like voting for a PTL or TC member, if you'd done that17:12
rlpplek17:12
*** lpabon has left #openstack-meeting-alt17:12
hyakuheiIt'd be good to hear more from the community about what they want for the next release. In addition to what I put in my email I also want to get more official recognition by OpenStack as we've consistently shown benefit to the community :)17:12
bdpayneright now we are sorting out who is allowed to vote17:12
*** bookwar has left #openstack-meeting-alt17:12
*** vkramskikh has left #openstack-meeting-alt17:12
*** dg__ has joined #openstack-meeting-alt17:12
hyakuheibdpayne: Any problems getting that sorted17:13
bdpayneit's just some leg work... but we can build on what I did last time so it should be pretty managable17:13
bdpaynewe tried to broadly define an active OSSG participant17:13
*** dane_leblanc has quit IRC17:13
bdpaynewhich means identifying those that fit the criteria takes some searching :-)17:13
hyakuheiCool17:14
*** rcleere_away is now known as rcleere17:14
tmcpeakbdpayne: if you want help with legwork I'll pitch in17:14
bdpayneI encourage people to review the criteria on the wiki: https://wiki.openstack.org/wiki/Security/OSSG_Lead_Election_Fall_201417:14
bdpayneif you think that you should be allowed to vote, please feel free to drop me a line with the evidence17:14
bdpaynethat might save us some time17:14
hyakuheiSo Tim (tkelsey) who isn't here right now, has a script for doing some indexing of OSSG members, used it to work out how well (or not) we react to the SecurityImpact tag17:14
hyakuhei^ Potentially useful17:14
*** rcleere is now known as rcleere_away17:14
bdpayneshohel02 will be helping me with this, I believe... but I'll let you know if we need more help tmcpeak, thanks17:15
tmcpeakbdpayne: ok cool, sounds good17:15
*** rcleere_away is now known as rcleere17:15
shohel02my pleasure bdpayne..17:15
bdpayneah yes, I have a similar script I wrote for this last time around17:15
hyakuheiAwesome, thanks bdpayne, shohel02 tmcpeak17:15
hyakuheiFigured you would bdpayne17:15
bdpayneso that's all I have unless there are questions17:15
hyakuheiok cool, thanks for this guys!17:15
hyakuhei#topic Poodle!17:16
*** openstack changes topic to "Poodle! (Meeting topic: openstack security group)"17:16
dg__yay poodle17:16
hyakuheiSo my read is the world is ending again, right?17:16
nkinderSo, the big question is "Should we issue an OSSN for this?"17:16
bknudsonis there an attack on the client, too?17:16
tmcpeaknah, upgrade to Win7, you'll be fine17:16
bdpaynelol17:16
hyakuheinkinder: I think we should17:16
tmcpeak:D17:16
bdpayneI think the thing with POODLE is that mediation takes some thought17:16
bknudsonthere will likely be an ossa17:16
bdpaynean OSSN could be useful17:17
hyakuheiPlenty of ways OpenStack can be affected, mediation is expansive17:17
*** johnthetubaguy is now known as zz_johnthetubagu17:17
bdpaynean OSSA, really?17:17
nkinderyeah, I'm not sure there will be an OSSA17:17
hyakuhei+117:17
bdpaynelol, all of you guys with your inside knowledge17:17
bknudsonI don't want to say too much17:17
bdpaynefair enough17:17
dg__I would be surprised if there is a OSSA, they seem very reluctant to issue them that seems operational17:17
bknudsonalthough it should be obvious17:17
*** jergerber has quit IRC17:18
dg__omg, I have lost the ability to write in sentences, apologies17:18
*** dboik has joined #openstack-meeting-alt17:18
nkinderSo regardless of OSSA, there are a lot of areas outside of OpenStack that need proper cipher configurationb17:18
hyakuhei+117:18
*** edwardb has joined #openstack-meeting-alt17:18
hyakuheiAnd some areas where there's not a brilliant option today, like Pound.17:18
nkinderSo an OSSA doesn't entirely solve the issue17:18
hyakuhei(Unless you class going straight to TLS1.2 as brilliant, which I do)17:18
hyakuhei+2 for a Poodle OSSN.17:19
nkinderSo areas to cover would be eventlet, httpd, nginx, pound, stud, and HAProxy17:19
dg__+1 for TLS1.217:19
*** ajo_ has quit IRC17:19
*** harlowja_away is now known as harlowja17:19
bdpaynenkinder also client side17:19
hyakuheiSo kinda17:20
hyakuheiFor a project like OpenStack, I agree you need to address client side too17:20
tmcpeakis it similarly vulnerable?17:20
bdpaynealso for people that have clouds that have clients that reach outside of the cloud for services like ldap, syslog, etc17:20
hyakuheibut for most deployers, they only care about server side. If you fix taht everywhere, you don't need to worry about the clients connecting right?17:20
hyakuheibdpayne: good point17:21
bknudsonis there an actual attack on the client?17:21
bknudsonfrom a MITM?17:21
bdpayneyou need either the client or the server to be fixed17:21
bdpayneif they are both not fixed, then you can get downgraded and attacked17:21
*** kevincon_ has quit IRC17:21
bdpayneso if the only thing you control is the client, then you are best advised to fix the client17:21
*** jergerber has joined #openstack-meeting-alt17:22
rlppleright if the client is compromised, then info is leaked17:22
tmcpeakI thought the attack involved javascript running on the client side to send to a different server, what's the flip side of that?17:22
rlppleif the server compromised same17:22
bdpaynei.e., go configure your web browsers now ;-)17:22
bknudsonthe clients in openstack can be the python libs.17:22
hyakuheitmcpeak: that's the demo of the vulnerability in the protocol but there are likely other exploitation vectors17:22
bknudsonand the CLIs17:22
tmcpeakahh17:22
*** xarses has left #openstack-meeting-alt17:23
tmcpeakyes, I guess compromised server code could do the same17:23
bdpayneso yeah, the openstack python clients are certainly worth discussing in this context17:23
bdpaynealong with other services in the cloud that act as ssl clients17:23
*** ajo_ has joined #openstack-meeting-alt17:23
nkinderSo there are a lot of scenarios to cover, and I don't think we can cover everything in detail.  The scope is just too large.17:23
bdpayneright17:23
hyakuheiWell focus on the fundamentals17:24
bdpayneI would shy away from talking about specific technologies in this one17:24
hyakuheior maybe even on detection/verification17:24
*** cbouch has quit IRC17:24
bdpaynei.e., don't say how to fix nginx17:24
hyakuheiHow to verify with s_client for instance17:24
*** rudrarugge has joined #openstack-meeting-alt17:24
bdpaynebut say more generally that you need to disable sslv3 and/or use the new handshake protocol17:24
nkinderok, so a "disable SSLv3" recommendation essentially17:24
hyakuheibdpayne: the security guide addresses configuration of at least three SSL terminators17:24
bdpaynes_client verification is a very good thing to mention, yeah17:24
shohel02regarding mitigation approach... is there any solution other than not using SSL3.017:24
*** rkukura has left #openstack-meeting-alt17:24
dg__not really17:24
bdpayneyes17:25
nkinderand call out where SSL might be used in OpenStack so people have some idea of where they need to look17:25
hyakuheiOpenSSL just released an update17:25
dg__bdpayne go on17:25
hyakuheinkinder: +117:25
bknudsondo you think openstack should now default to not allow SSL3.0?17:25
tmcpeakthere was some packet fragmentation approach that mitigated it17:25
bknudsonmaybe OpenSSL will do that for us.17:25
bdpayneTLS_FALLBACK_SCSV17:25
chair6there is an alternate remdiation to protect downgrade of TLS -> SSLv317:25
chair6yeah, that ^17:25
bdpayneI am personally not a huge fan of this17:25
chair6but disabling SSLv3 is still the best approach17:25
bdpaynebut it will get deployed and it will do the trick... at least for now17:25
tmcpeaknot packet but bloc17:26
tmcpeakk17:26
bdpayneI have found that you can disable sslv3 and still get very nice client compatibility by keeping the sslv23 handshake option enabled17:26
bdpayneb/c poodle affects the protocol, not the handshake17:26
tmcpeakis 2.3 for sure not vulnerable?17:26
hyakuheiWhat clients _have_ to use SSL3 ?17:26
*** Barker has joined #openstack-meeting-alt17:26
bdpayneie617:27
nkinderyeah, IE6 is the one that I know of17:27
*** zns has joined #openstack-meeting-alt17:27
hyakuheiRight, that's very application specific17:27
*** markwash__ has quit IRC17:27
hyakuheii.e Horizon17:27
bdpaynefor those that want a useful technical writeup, I recommend https://www.dfranke.us/posts/2014-10-14-how-poodle-happened.html17:27
*** SumitNaiksatam has quit IRC17:27
hyakuheiOnly affects govt sector I'd imagine17:27
*** yamahata has quit IRC17:27
bknudsonI've been assuming that client compatibility for the REST APIs isn't going to be a big deal.17:27
nkinderSo who has the cycles to write up an OSSN for this?17:27
hyakuheiEveryone else isn't 10 years behind17:27
nkinderbknudson: +117:27
nkinderhyakuhei: 10 is being nice... :)17:28
hyakuheinkinder: Throw it on the stack, I'll find someone to do it17:28
hyakuheinkinder: yarp!17:28
bdpayneI might be able to do it17:28
*** ajo_ has quit IRC17:28
bdpayneI'm spending the day dealing with some customer communication around this17:28
bdpayneand that actually fits in nicely17:28
bdpayne:-)17:28
hyakuheiSweet17:28
nkinderbdpayne: great, thanks!17:28
hyakuhei#action bdpayne to write a story about poodles17:28
bdpayneheh, my life story17:29
hyakuheio.O17:29
bdpaynenothing to see here... carry on ;-)17:29
hyakuheiok, what's next peeps - OSSN status?17:29
hyakuhei#topic ossn status17:29
*** openstack changes topic to "ossn status (Meeting topic: openstack security group)"17:29
nkinderhere's the current queue - https://bugs.launchpad.net/ossn/17:30
*** manishg has left #openstack-meeting-alt17:30
nkinderhyakuhei: you have a simple whitespace issue to fix up for the legacy notes17:31
nkinderhyakuhei: do you want me to take care of it today?17:31
nkinderI'd like to get those merged17:31
*** safchain has quit IRC17:31
hyakuheinkinder: If that's  all it needs sure17:31
*** rcleere is now known as rcleere_away17:31
hyakuheiThanks17:31
nkinder0025 is close, but there was a -1 added there - https://review.openstack.org/#/c/117928/17:32
nkinderIt seems that Stuart wants it to be more obvious that this only affects multi-tenant mode17:32
nkinderThat should be a minor tweak for Nathaniel to make, then this should be ready to close out17:32
*** padkrish has quit IRC17:33
hyakuheiGreat17:33
nkinderso here's 0025...17:33
hyakuheisicarie: Can you get that done?17:33
nkinder#link https://review.openstack.org/11792817:33
nkinderTim also has one out for review...17:33
nkinder#link https://review.openstack.org/12863617:33
nkinderSo if anyone is itching to review something, please have at it :)17:34
*** _nadya_ has joined #openstack-meeting-alt17:34
*** markwash__ has joined #openstack-meeting-alt17:34
sicariehyakuhei: yep, I'll get that out in the next 2 hours17:34
hyakuheiGreat, thanks sicarie17:34
nkinderI added a new Cinder one to the queue as well this week17:34
nkinder#link https://bugs.launchpad.net/ossn/+bug/132921417:34
uvirtbotLaunchpad bug 1329214 in cinder "tgtadm iscsi chap does not work" [Critical,Fix released]17:34
hyakuheiSaw that, I think we had a similar one recently?17:35
nkinderIt seems like a pretty simple one with a fix that is on the way.  It's really just something we should raise awareness on and recommend updating to get the fix.17:35
hyakuheiBug I mean17:35
*** padkrish has joined #openstack-meeting-alt17:35
hyakuheicool17:35
hyakuheiAnything else nkinder ?17:35
nkinderNo, that's about it on the OSSN front right now17:35
rlppleneed to step away.  will look at the review list.17:36
hyakuhei#topic Threat Modelling17:36
*** openstack changes topic to "Threat Modelling (Meeting topic: openstack security group)"17:36
hyakuheishohel02: You're up :)17:36
shohel02yes17:36
shohel02threat modeling template and process docs are still in review17:37
shohel02we have added threat modeling report for keystonemiddleware17:37
*** zns has quit IRC17:37
shohel02so show how the template and process can be used17:37
shohel02updated in the new patch17:37
shohel02https://review.openstack.org/#/c/121034/17:37
*** zns has joined #openstack-meeting-alt17:37
hyakuheiI've reviewed that, it'd be good to get more eyes on17:38
shohel02definately17:38
shohel02i think keystonemiddleware case can give some insights ...what it looks like17:38
hyakuheiwould be a good thing to get bknudson to look at perhaps ?17:39
shohel02definately keystonemiddleware devs can help17:40
bknudsonI'll add it to my list17:40
hyakuheiThank you :)17:40
*** kopparam has joined #openstack-meeting-alt17:41
shohel02others review also welcome17:41
nkinderI wonder if it's possible to have the threat modelling docs built as a part of the gate job17:41
nkinderIt would make it easier to review the end content17:42
*** gholler has quit IRC17:42
*** dims_ has quit IRC17:42
bdpayneyeah, that would be nice17:42
*** gholler has joined #openstack-meeting-alt17:42
hyakuhei+117:42
*** dims_ has joined #openstack-meeting-alt17:42
shohel02nkinder: what does this mean..during spec writing process17:43
nkinderI know that the keystone dev docs work that way17:43
nkindershohel02: take a look at this review for an example... https://review.openstack.org/#/c/124095/17:43
*** ivar-lazzaro has joined #openstack-meeting-alt17:43
*** ivar-lazzaro has quit IRC17:43
nkinderIf you click on the 'gate-keystone-docs' job, it brings you to the built docs using the patch17:44
*** ivar-lazzaro has joined #openstack-meeting-alt17:44
*** _nadya_ has quit IRC17:44
*** zns has quit IRC17:45
*** kopparam has quit IRC17:46
shohel02okey17:46
hyakuheiInteresting idea, certainly would make reading through them easier17:46
*** elo has quit IRC17:46
nkindershohel02: that doesn't block your work, but it really helps when reviewing17:46
*** zns has joined #openstack-meeting-alt17:46
shohel02yah looks promising... may be we get more involvement by that17:47
*** vponomaryov has left #openstack-meeting-alt17:47
*** HeOS has quit IRC17:47
*** arborism has joined #openstack-meeting-alt17:47
nkinderAre there any topics to discuss around the Summit?17:48
*** arborism has quit IRC17:48
*** SumitNaiksatam has joined #openstack-meeting-alt17:48
nkindersuch as a VMT/OSSG get-together?17:48
*** nshaikh has joined #openstack-meeting-alt17:48
hyakuheiSwift crypto, Bandit Integration, VMT+OSSG17:48
hyakuheiOh to discuss now? I'm not sure17:49
nkinderyeah, I meant now17:49
bknudsonis ossg on the schedule?17:49
bknudsondo we have a slot?17:49
nkinderNo, not out own17:49
*** saurabhs has joined #openstack-meeting-alt17:49
nkinderWe were invited to participate in the VMT slot17:49
hyakuheiDespite trying, VMT have offered to combine theres with ours17:49
hyakuheiWhich was nice17:49
nkinderI also asked for our own table to have informal discussions and meet up, but we won't get our own officially.17:50
nkinderWe can slap a sign on one to lay claim to it though17:50
hyakuheiYeah, I like bdpayne's idea of having our own little track17:50
hyakuheiMaybe we should consider some informal lightning talks or something17:50
hyakuheicrazy ideas etc17:50
bdpayne:-)17:50
nkinderWe should figure out a schedule for that17:51
hyakuhei+117:51
hyakuheiTuesday most likely17:51
shohel02slap a sign on+17:51
nkinderYeah, I need to look at the schedule, but I think W-F is when I'm most busy in Keystone stuff17:51
hyakuheiIIRC Security is M W17:52
hyakuheibut that's without checking17:52
nkinderhyakuhei: you mean the official sessions, not design stuff, right?17:52
hyakuheiYEh17:52
hyakuheiok, so we need to work out when is the best time for us to sit down together17:53
hyakuhei#topic any other business17:54
*** openstack changes topic to "any other business (Meeting topic: openstack security group)"17:54
*** paboldin has left #openstack-meeting-alt17:54
nkindernothing else from me...17:55
hyakuheiCool, well I guess we can call that a wrap then, thank you everyone!17:55
bdpayneI guess it's back to attacking poodle17:55
hyakuhei#endmeeting17:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:56
bknudsonthanks17:56
openstackMeeting ended Thu Oct 16 17:56:03 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-10-16-17.04.html17:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-10-16-17.04.txt17:56
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-10-16-17.04.log.html17:56
nkinderthanks all!17:56
*** dg__ has quit IRC17:56
tmcpeaklater!17:56
*** tmcpeak has left #openstack-meeting-alt17:57
*** rlpple has quit IRC17:57
*** sicarie has left #openstack-meeting-alt17:57
*** balajiiyer has left #openstack-meeting-alt17:58
*** zns has quit IRC17:58
*** chair6 has left #openstack-meeting-alt17:58
*** jergerber has quit IRC17:58
*** haleyb has quit IRC18:01
*** zns has joined #openstack-meeting-alt18:01
*** ntrueblood has quit IRC18:03
*** zeddii has joined #openstack-meeting-alt18:04
*** thangp has quit IRC18:04
*** zns has quit IRC18:04
*** balajiiyer has joined #openstack-meeting-alt18:05
*** marun has quit IRC18:05
*** marun has joined #openstack-meeting-alt18:07
*** noslzzp has quit IRC18:07
*** dboik_ has joined #openstack-meeting-alt18:10
*** sarnold007 has quit IRC18:11
*** dboik has quit IRC18:13
*** otherwiseguy has joined #openstack-meeting-alt18:14
*** salv-orlando has joined #openstack-meeting-alt18:15
*** EricGonczer_ has joined #openstack-meeting-alt18:15
*** e0ne has quit IRC18:16
*** bknudson has left #openstack-meeting-alt18:17
*** emagana has joined #openstack-meeting-alt18:17
*** zz_dimtruck is now known as dimtruck18:17
*** jamiehannaford has quit IRC18:19
*** carl_baldwin has quit IRC18:22
*** mestery has quit IRC18:24
*** mestery has joined #openstack-meeting-alt18:25
*** noslzzp has joined #openstack-meeting-alt18:28
*** noslzzp has quit IRC18:28
*** bswartz has quit IRC18:30
*** kevinconway has joined #openstack-meeting-alt18:32
*** cknight has quit IRC18:34
*** cknight1 has joined #openstack-meeting-alt18:34
*** ramishra has joined #openstack-meeting-alt18:35
*** spzala has quit IRC18:37
*** dimtruck is now known as zz_dimtruck18:37
*** padkrish has quit IRC18:39
*** ramishra has quit IRC18:40
*** zns has joined #openstack-meeting-alt18:40
*** padkrish has joined #openstack-meeting-alt18:40
*** kopparam has joined #openstack-meeting-alt18:42
*** zns has quit IRC18:42
*** rondotcom has joined #openstack-meeting-alt18:46
*** kopparam has quit IRC18:46
*** ijw has joined #openstack-meeting-alt18:47
*** terryw has joined #openstack-meeting-alt18:48
*** derekh has joined #openstack-meeting-alt18:50
*** otherwiseguy has quit IRC18:50
*** kozhukalov has quit IRC18:51
*** ijw has quit IRC18:51
*** bnemec has quit IRC18:52
*** _nadya_ has joined #openstack-meeting-alt18:52
*** bnemec has joined #openstack-meeting-alt18:53
*** ramishra has joined #openstack-meeting-alt18:53
*** teran_ has quit IRC18:54
*** emagana has quit IRC18:55
*** emagana has joined #openstack-meeting-alt18:56
*** emagana has quit IRC18:56
*** emagana has joined #openstack-meeting-alt18:57
*** obulpathi has joined #openstack-meeting-alt18:57
*** ramishra has quit IRC18:58
*** malini has joined #openstack-meeting-alt18:58
tonytan4ever\o18:59
obulpathio/18:59
tonytan4evero/18:59
*** aglarendil has joined #openstack-meeting-alt18:59
malini#startmeeting: poppy18:59
openstackMeeting started Thu Oct 16 18:59:58 2014 UTC and is due to finish in 60 minutes.  The chair is malini. Information about MeetBot at http://wiki.debian.org/MeetBot.18:59
*** mihgen has left #openstack-meeting-alt19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: : poppy)"19:00
openstackThe meeting name has been set to '__poppy'19:00
maliniwho is here for poppy?19:00
obulpathihi there o/19:00
*** amitgandhinz has joined #openstack-meeting-alt19:00
amitgandhinzo/19:00
tonytan4evero/19:00
malinihello amitgandhinz19:00
malini#chair amitgandhinz19:00
openstackCurrent chairs: amitgandhinz malini19:00
*** spzala has joined #openstack-meeting-alt19:01
amitgandhinzhi everyone19:02
amitgandhinzok lets get this party started =)19:02
obulpathiyay19:02
obulpathiparty19:02
*** georgelorch has joined #openstack-meeting-alt19:02
amitgandhinz#topic Review Last Week19:02
*** openstack changes topic to "Review Last Week (Meeting topic: : poppy)"19:02
amitgandhinz#link http://eavesdrop.openstack.org/meetings/weekly_poppy_meeting/2014/weekly_poppy_meeting.2014-10-09-19.00.html19:02
*** boris-42 has quit IRC19:02
*** Barker has quit IRC19:02
amitgandhinz obulpathi to finalize on the format of the next_url for listing services19:02
*** padkrish has quit IRC19:02
obulpathiyes19:02
obulpathiI contacted the DRG and took feedback from them19:03
*** marcoemorais has quit IRC19:03
*** luizfar has quit IRC19:03
amitgandhinzdid the apiary doc get updated?19:03
obulpathia good way to structure the next links: is to leave it empty for the last batch19:03
obulpathiyes19:03
amitgandhinzcool19:03
*** georgelorch2 has quit IRC19:03
*** marcoemorais has joined #openstack-meeting-alt19:03
*** Barker has joined #openstack-meeting-alt19:03
*** luizfar has joined #openstack-meeting-alt19:03
obulpathiand the implementation is also done19:03
amitgandhinz=)19:03
obulpathias a part of the list end point19:03
obulpathi:)19:04
amitgandhinzok next item: megan_w to gauge vendor participation in Paris19:04
*** boris-42 has joined #openstack-meeting-alt19:04
amitgandhinzmegan_w is not around19:04
amitgandhinzany vendors here today?19:04
amitgandhinzanyone else planning to attend the openstack summit in paris?19:05
obulpathinop19:05
*** megan_w_ has joined #openstack-meeting-alt19:05
amitgandhinzok carry this one over19:05
amitgandhinz#action megan_w to gauge vendor participation in Paris19:05
megan_w_here19:06
amitgandhinzhi megan_w_19:06
megan_w_hi there19:06
obulpathihi megan_w19:06
megan_w_do we have any vendors here with us today?19:06
amitgandhinzno one appears to be19:06
megan_w_we need to get better about communicating with so they get here19:06
amitgandhinzyeh19:06
megan_w_with them*19:06
amitgandhinzdo you know if any of them plan to attend paris?19:07
megan_w_i don't, i was hoping we could discuss it in these meetings19:07
megan_w_we should propose what we would want from them in the session19:07
megan_w_then ask for attendance19:07
amitgandhinzyeh, may need to encourage them outside these meetings19:08
amitgandhinzit will be a design session, so the idea is to come up with the features to build during kilo19:08
megan_w_take it away, PTL :)19:08
*** AlanClark has quit IRC19:08
megan_w_hmm, ok19:08
amitgandhinzok moving on...19:09
amitgandhinz#topic Blueprint Updates19:09
*** openstack changes topic to "Blueprint Updates (Meeting topic: : poppy)"19:09
amitgandhinz#link https://blueprints.launchpad.net/poppy19:09
amitgandhinzobulpathi: list-services19:09
obulpathilist-services is merged19:09
megan_w_moving on19:09
obulpathithanks all for the review19:09
obulpathiand special thanks to malini19:10
obulpathifor having lot of patience to find all the bugs iun my code :)19:10
maliniobulpathi: I was expecting something bad :D19:10
amitgandhinzmiqui: add-docstrings19:10
obulpathihahha19:10
amitgandhinzlooks like that one needs me to review19:11
amitgandhinztonytan4ever: delete-service19:11
tonytan4everThis one is "under review", but really it is ready to be merged.19:12
*** padkrish has joined #openstack-meeting-alt19:12
amitgandhinzno one has +1'd the latest patch yet19:12
tonytan4everI cleared the api test blocker yesterday,19:12
amitgandhinzok lets get some reviewers on that19:12
obulpathiroger that19:12
amitgandhinztonytan4ever: purge-content19:12
*** jprovazn_afk has quit IRC19:12
tonytan4everI will call that in Good progress. 1st PR got +319:13
tonytan4everready to be merged now.19:13
tonytan4everhttps://review.openstack.org/#/c/126728/19:13
amitgandhinzactually has  a +4 hehe19:13
malini:-Pdoes jenkins count?19:13
amitgandhinzno, but mine is a +2 =P19:14
amitgandhinzmerged!19:14
tonytan4everkk19:14
*** teran has joined #openstack-meeting-alt19:14
amitgandhinzthis was at the provider part only right19:14
tonytan4everyes19:14
amitgandhinzso still needs api work19:14
*** daneleblanc has quit IRC19:15
amitgandhinzill mark it as good progress19:15
tonytan4everyes, that's what I am working on now.19:15
tonytan4everSure.19:15
amitgandhinzamitgandhinz: dns-driver19:15
amitgandhinzthis one as an initial patch to create the basic driver setup19:15
amitgandhinzthen i need to implement the cloud-dns-driver which is a seperate bp19:15
*** nshaikh has left #openstack-meeting-alt19:16
*** rudrarugge has quit IRC19:16
amitgandhinzi currently only have 2 +1's19:16
malinio/19:16
amitgandhinzi need one more malini19:16
malinitht would be really bad19:16
amitgandhinzhttps://review.openstack.org/#/c/127628/19:16
*** AlanClark has joined #openstack-meeting-alt19:17
maliniwill check that out19:17
*** Youcef has quit IRC19:17
amitgandhinzcloud-dns-driver already has a +3 but it depends on the above patch19:17
amitgandhinzobulpathi:  patch-service19:18
obulpathipatch-service: happy path test cases are passing now19:18
obulpathigoing through and ironing out the error inputs19:18
obulpathiso, we can say its in good progress19:19
maliniobulpathi: can you re-use some of the code for POST service for error handling?19:19
obulpathiwill update the apiary, once I finish the error cases19:19
obulpathimalini: the json service is validated by the same code as post19:19
obulpathibut there are few more conditions that PATCH needs to take care of19:19
obulpathiI am working through them19:20
*** david-lyle_ has joined #openstack-meeting-alt19:20
malinicool! thanks19:20
obulpathi:)19:20
*** david-lyle has quit IRC19:20
amitgandhinzok update on the https://blueprints.launchpad.net/poppy/+spec/master-sub-provider-accounts19:20
*** terryw has quit IRC19:20
*** teran has quit IRC19:20
amitgandhinzmegan_w_ and I met with MaxCDN yesterday19:20
amitgandhinzthe CDN Manager is not actually required19:21
amitgandhinzit basically give syou the added bonus of seperate control panels for each sub user19:21
amitgandhinzwhich in the case of poppy we dont need19:21
megan_w_i think that will end up being a more generic solution anyway, which is preferred for us19:21
*** teran has joined #openstack-meeting-alt19:21
amitgandhinzif you plan to do reporting, billing, etc on your own from the logs, then the one account method works fine19:21
amitgandhinzjust need to up the limits19:21
amitgandhinzim going to mark this bp as done19:22
obulpathiawesome!19:22
tonytan4everI think we also need to find a better naming scheme from poppy service --> maxcdn service though.19:22
amitgandhinzlets move that to open discussion tonytan4ever19:22
tonytan4everok.19:23
amitgandhinzmalini: gate-cassandra19:23
maliniI haven't got a chance to work on tht yet19:23
amitgandhinzok19:23
maliniIt'll probably have to move to the next Series Goal19:23
amitgandhinzsame with the rm-mockdb19:24
amitgandhinzthat bp is blocked until we can run cassandra at the gate or we have sqla19:24
amitgandhinzok moving on19:25
amitgandhinz#topic bugs19:25
*** openstack changes topic to "bugs (Meeting topic: : poppy)"19:25
amitgandhinzlink https://bugs.launchpad.net/poppy19:25
maliniyayyyy !!!19:25
amitgandhinz#link https://bugs.launchpad.net/poppy19:25
*** _nadya_ has quit IRC19:25
amitgandhinzmalini: you want to drive this topic19:25
malinisure19:25
malinithe bugs need some love19:25
amitgandhinzew19:25
obulpathihhaha19:25
amitgandhinzkiss the spiders19:25
maliniWe have a lot surrounding the error handling for create flavors19:25
*** teran has quit IRC19:26
* amitgandhinz hides19:26
maliniamitgandhinz: I meant more along the lines of bugspray19:26
*** alex_didenko has quit IRC19:26
maliniI suggest we make a bp for it, as I got tired of writing down the bugs & stopped after a while :-$19:26
amitgandhinzok please do that19:26
maliniok..will do after the meeting & get rid of the related bugs19:27
malinitht still leaves us a few bugs19:27
*** david-lyle_ is now known as david-lyle19:27
malinihttps://bugs.launchpad.net/poppy/+bug/137990119:27
uvirtbotLaunchpad bug 1379901 in poppy "400s returns as HTML" [Undecided,New]19:27
maliniwow..I didn't know it wud fetch bug details19:27
amitgandhinzya thats cool19:27
tonytan4everI think I can fix that one real quick19:28
amitgandhinzok lets get this one19:28
malinitonytan4ever: Can I assign tht to you?19:28
tonytan4everby utilizing Pheniox's pecan hook's code19:28
tonytan4everYes19:28
amitgandhinz+119:28
amitgandhinznext19:28
*** nkinder has left #openstack-meeting-alt19:28
*** alex_didenko has joined #openstack-meeting-alt19:28
malinihttps://bugs.launchpad.net/poppy/+bug/138067919:28
uvirtbotLaunchpad bug 1380679 in poppy "Remove project_id from the request url in tests" [Undecided,New]19:28
obulpathiI added the pecan hook to take care of this19:29
amitgandhinzis this still an issue?19:29
maliniwe need to cleanup the unit tests19:29
obulpathiwe just need to use the url format code19:29
*** padkrish has quit IRC19:29
obulpathiI think in some cases, we still return the tenant / project id19:29
maliniobulpathi: you want to take that one?19:29
obulpathiYes,Please19:29
*** mfer has quit IRC19:29
amitgandhinzok so sounds like we need to sweep19:29
malinican you assign urself obulpathi ?19:29
obulpathiAmitgandhinz: Assign this to me19:29
amitgandhinzall these dead bugs are starting to smell19:29
obulpathisure19:30
malinithey'll breed if live19:30
amitgandhinzassigned19:30
malinilast one is interesting19:30
malinihttps://bugs.launchpad.net/poppy/+bug/138215519:30
uvirtbotLaunchpad bug 1382155 in poppy "/health endpoint returns wrong status when cassandra is offline" [Undecided,New]19:30
maliniI ran into this one just an hour back19:30
maliniso its still fresh19:30
obulpathiThe cassandra driver is hardcoded to return True19:31
obulpathiMy bad, should have taken care of that19:31
obulpathiI will take care of this one19:31
malinican you assign urself obulpathi?19:31
amitgandhinzassigned19:31
malinithanks amitgandhinz :)19:31
obulpathithanks19:31
maliniamitgandhinz: https://bugs.launchpad.net/poppy/+bug/1379901 shud go to tonytan4ever19:31
uvirtbotLaunchpad bug 1379901 in poppy "400s returns as HTML" [Undecided,New]19:31
amitgandhinzdone19:31
*** dprince has quit IRC19:32
malinithe rest is post flavor related. I'll create a bp for tht19:32
amitgandhinzthanks19:32
*** dane_leblanc has joined #openstack-meeting-alt19:32
maliniwe missed this one https://bugs.launchpad.net/poppy/+bug/137534119:32
uvirtbotLaunchpad bug 1375341 in poppy "Error Messages in test logs" [Medium,Confirmed]19:32
malinido we care to fix it now?19:32
amitgandhinzthats a lower priority19:32
maliniamitgandhinz: can you change the priority, plz?19:33
malinihttps://bugs.launchpad.net/poppy/+bug/137534119:33
malinihmm…why didn't it fetch the summary?19:33
malini"Unable to create a distribution with multiple origins for CloudFront driver"19:33
*** HeOS has joined #openstack-meeting-alt19:34
maliniobulpathi: can this wait?19:34
obulpathiThis one got to do with teh limitations of boto19:34
obulpathithe cloudfront client19:34
obulpathiso, we can fix this until we fix the boto19:34
maliniok19:34
malinido we have an issue open for boto?19:34
obulpathiyes, this can wait, unless amitgandhinz says otherwise19:34
amitgandhinzlow19:35
maliniobulpathi: https://bugs.launchpad.net/poppy/+bug/1359950 what abt this one?19:35
uvirtbotLaunchpad bug 1359950 in poppy "Support for updating service with CloudFront driver is missing" [Undecided,New]19:35
obulpathithats is a different one19:35
maliniyes19:35
*** zz_dimtruck is now known as dimtruck19:36
amitgandhinzis there a way that can be surfaced via tests rather than as a bug?19:36
obulpathicloudfront python client has limited capabilities right now19:36
amitgandhinzbecause as new drivers are built its possible they lack a feature and i would rather the tests identify that than have an open bug for it19:36
tonytan4ever+1 on that.19:37
maliniamitgandhinz: you want the tests to keep failing for these?19:37
amitgandhinzie run the api tests against each provider19:37
obulpathi+119:37
amitgandhinzthey can be made non failing, just informational19:37
*** satish has quit IRC19:37
amitgandhinzie its own environment in tox?19:37
maliniWe can skip the tests with INFO message, but when do we decide it's time to not skip them?19:37
amitgandhinzthat appears on the review page?19:37
amitgandhinzim just thinking when a new provider build their own driver, and stops half way it should not halt poppy19:38
amitgandhinzbut users should be able to see that driver X is failing in these areas so choose not to use it19:38
maliniyeah..I think we need to somehow track them19:38
obulpathi+1 good idea19:38
maliniSKIPPED tests usually get ignored19:38
amitgandhinzlets discuss that offline19:38
amitgandhinzmaybe failing but non voting?19:38
maliniok19:38
malinilets chat in #openstack-poppy19:39
amitgandhinzya19:39
malinitht's all for bugs19:39
obulpathicool19:39
maliniamitgandhinz: we can move to the next topic19:39
*** rondotcom has quit IRC19:39
amitgandhinzya19:39
amitgandhinz#topic Standardized Error Responses19:39
*** openstack changes topic to "Standardized Error Responses (Meeting topic: : poppy)"19:39
miquihi folks..sorry am late..19:39
amitgandhinz#link https://wiki.openstack.org/wiki/Governance/Proposed/APIGuidelines#Failure_Codes19:39
obulpathihi miqui19:39
amitgandhinzhi miqui19:40
malinimiqui: glad you could make it :)19:40
miquihi19:40
*** rondotcom has joined #openstack-meeting-alt19:40
maliniSo I am running into issues where our error messages don't make sense19:40
maliniwhich is bad for a project as young as us19:40
maliniexample error:19:40
malini{19:40
malini   "code": 400,19:40
malini   "description": "u'fastly'",19:40
malini    "title": "Bad Request"19:40
malini}19:40
miquimalini: is that becuase the msg is different per vendor?19:40
*** satish has joined #openstack-meeting-alt19:41
malinimiqui: even within our code we are not providing descriptive error messages19:41
miquigotcha...19:41
amitgandhinzi think its just lacking in quality messages being surfaced19:41
amitgandhinzwe need to be better at handling errors, and outlining why it failed19:41
maliniamitgandhinz: yes19:41
miqui+119:42
maliniIf it fails with a 400, we shouldn't leave the user wondering why19:42
*** kebray has joined #openstack-meeting-alt19:42
tonytan4ever#agreed19:42
malinitonytan4ever never argues :)19:42
amitgandhinz#agreed to handle error messages better19:42
miqui..heheh19:42
tonytan4ever#agreed19:42
amitgandhinzi dont think tonytan4ever knows that using a hashtag logs it in the summary lol19:42
tonytan4ever#agreed19:42
*** teran has joined #openstack-meeting-alt19:43
maliniwhat does everybody think of this format https://wiki.openstack.org/wiki/Governance/Proposed/APIGuidelines#Failure_Codes ?19:43
*** kopparam has joined #openstack-meeting-alt19:43
amitgandhinztonytan4ever: http://meetbot.debian.net/Manual.html19:43
*** kebray has quit IRC19:43
obulpathiyes, I also wanted to bring up about the API Guidelines19:43
obulpathiI will be good for to study this and pick up good parts19:43
* miqui reading...19:44
amitgandhinzthat format looks better than what i proposed in the apiary docs19:44
* amitgandhinz which somehow disappeared hmmmm19:44
*** rondotcom has quit IRC19:44
miquii think the APIGuidelines is fine...19:44
maliniamitgandhinz: it made rom for something better19:44
*** EricGonczer_ has quit IRC19:45
malinisince we all agree, should this go to a bp to clean up existing stuff?19:45
maliniAll new code should follow this format19:45
amitgandhinzya19:45
miquiyes19:45
amitgandhinzwe should have a standardized class for it19:45
amitgandhinzand use that19:45
amitgandhinzalso we should be using the oslo logging more when errors do happen19:45
amitgandhinzwe are very light on log lines19:46
maliniamitgandhinz: Can you write up tht bp?19:46
amitgandhinzwill do19:46
obulpathiamitgandhinz: +119:46
maliniamitgandhinz: good point..these should be stuff to watch out for during reviews19:46
amitgandhinzyep19:46
maliniwe need review guidelines in the wiki19:46
miquiquestion: an error msg fromthe vendor would end up in message: right?19:46
malinitonytan4ever can answer that best19:47
amitgandhinzmiqui: its possible19:47
*** kopparam has quit IRC19:47
tonytan4everWell, not always.19:47
amitgandhinzsometimes poppy could determine why it failed and create a more poppy friendly message back to the user19:47
amitgandhinzsometimes it may make sense for the vendor's error to propogate back19:47
miquiright..19:48
miquiwas trying to gage when to do what....19:48
*** gondoi is now known as zz_gondoi19:48
*** sarob has joined #openstack-meeting-alt19:48
amitgandhinzwe should probably make a best guess determination of what will make the most sense to the user19:48
miquiok, sounds good..19:48
amitgandhinzfor example, if we get a duplicate key exception from a vendor, poppy can relay an appropriate message back19:49
miqui+119:49
amitgandhinzhoever, if a vendor had an unknown exception occur, then we may be best suited to relay that error back19:49
obulpathi+119:49
amitgandhinzalso, theres a section on friendly user message, and then more details19:49
amitgandhinzin the guideline proposed19:49
miquithats a good point becuase vendor support folks are wanting to know this info..19:50
amitgandhinz#agreed team gets better at handling error messages and logging them19:50
amitgandhinz#agreed team will surface errors based on https://wiki.openstack.org/wiki/Governance/Proposed/APIGuidelines#Failure_Codes19:50
amitgandhinz#link https://wiki.openstack.org/wiki/Governance/Proposed/APIGuidelines#Failure_Codes19:50
amitgandhinzok19:50
amitgandhinz9  minutes remain19:50
*** Barker has quit IRC19:51
amitgandhinz#topic open discussion19:51
*** openstack changes topic to "open discussion (Meeting topic: : poppy)"19:51
amitgandhinztonytan4ever: you had an item about using id's19:51
tonytan4everYes.19:51
*** ekhugen has left #openstack-meeting-alt19:51
tonytan4everSince for vendors like MaxCDN we are not to use Master/Sub accounts, the service name mapping from poppy to maxcdn will be a little tricky.19:52
*** zz_gondoi is now known as gondoi19:52
amitgandhinzplease explain19:52
*** teran_ has joined #openstack-meeting-alt19:53
*** _nadya_ has joined #openstack-meeting-alt19:53
tonytan4everAlso for logging purposes, since a poppy service's name can be changed by PATCH endpoint, tracking which provider (say MaxCDN) service belong to which user service will be an issue.19:53
malinidoes MaxCDN generate its own service name?19:54
amitgandhinzso basically if i call my service "Amits Service" then no one else within maxcdn through my operator account can use that name19:54
*** ramishra has joined #openstack-meeting-alt19:54
*** derekh has quit IRC19:54
amitgandhinzor more generically "My Service"19:54
tonytan4everRight, since different users can have same poppy service name19:54
amitgandhinzyeh19:54
*** padkrish has joined #openstack-meeting-alt19:54
*** dane_leblanc has quit IRC19:55
amitgandhinzso how about we generate a provider id (uuid) and use that as the servicename with the providers19:55
*** TravT has joined #openstack-meeting-alt19:55
*** EricGonczer_ has joined #openstack-meeting-alt19:55
tonytan4everbut they cannot have the same MaxCDN service name in the same account19:55
*** teran has quit IRC19:55
amitgandhinzand we store that in our provider details ( i think we already have a field for it)19:55
malinihmm..but tht is true for other providers too, rt? like fastly19:55
tonytan4everThat looks like a good idea to me.19:55
tonytan4everYes.19:55
amitgandhinzand so users of poppy can have whatever name (unique by projectid + servicename)19:55
tonytan4everSame applies for fastly, assume we only use one fastly operator account.19:56
amitgandhinzand the providers end up have UUID as the servicename/pullzoneid/distributionid19:56
*** dane_leblanc has joined #openstack-meeting-alt19:56
obulpathi+119:56
amitgandhinzif a user patches the servicename in poppy, the provider id need not change19:56
malinido providers allow different users to have the same service name?19:56
amitgandhinzno19:56
amitgandhinzwell depends on the provider19:56
*** balajiiyer has quit IRC19:57
*** ativelkov has joined #openstack-meeting-alt19:57
amitgandhinzif its a different account they can have the same name19:57
amitgandhinzbut within an account it must be unique19:57
*** e0ne has joined #openstack-meeting-alt19:57
amitgandhinzin the case of poppy, its one operator account only19:57
maliniok.19:57
tonytan4everAlmost all of the case we are only gonna have one provider service account.19:57
amitgandhinzok so do we agree to submit a uuid as the name at the provider level?19:58
tonytan4everagreed.19:58
obulpathi+119:58
amitgandhinzi cant see a problem with it19:58
amitgandhinzthe uuid may need to be custom based on name rules at the provider19:58
*** ramishra has quit IRC19:59
amitgandhinzbut we already have a function to handle that19:59
*** jokke_ has joined #openstack-meeting-alt19:59
amitgandhinzwe just store whatever the id ends up being in the provider-details19:59
tonytan4everyes.19:59
amitgandhinzmalini: miqui: any concerns on this approach?19:59
miquinot atm...19:59
malinihmmm..I am still hazy on the details20:00
maliniso no atm :)20:00
amitgandhinzwe can discuss more in the normal channel then20:00
amitgandhinztime is up20:00
amitgandhinzthanks everyone20:00
malinithank you!!20:00
obulpathithank you!20:00
obulpathisee you all next week20:00
amitgandhinzand miqui, we will see you in a few hours at the tavern!20:00
amitgandhinz#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
miquiyup!20:00
openstackMeeting ended Thu Oct 16 20:00:49 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/__poppy/2014/__poppy.2014-10-16-18.59.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/__poppy/2014/__poppy.2014-10-16-18.59.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/__poppy/2014/__poppy.2014-10-16-18.59.log.html20:00
*** malini has left #openstack-meeting-alt20:00
nikhil_k#startmeeting Glance20:01
openstackMeeting started Thu Oct 16 20:01:21 2014 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: Glance)"20:01
openstackThe meeting name has been set to 'glance'20:01
ativelkovo/20:01
kragnizo/20:01
TravTo/20:01
jokke_o/20:01
TravT\o20:01
*** flwang has joined #openstack-meeting-alt20:01
nikhil_kBrian may be missing today's meeting20:02
flwango/20:02
nikhil_klet's give it another min20:02
zhiyano/20:02
nikhil_k#link https://etherpad.openstack.org/p/glance-team-meeting-agenda20:02
esheffieldo/20:02
nikhil_kokay!20:03
nikhil_k#topic updates20:03
*** openstack changes topic to "updates (Meeting topic: Glance)"20:03
nikhil_k#link  https://review.openstack.org/#/c/126974/20:03
*** obulpathi has left #openstack-meeting-alt20:03
nikhil_kso, we got some feedback on that already I sup20:03
nikhil_khowever, let's keep in mind to add tests to tempest for all of our new additions20:04
nikhil_kfeatures, bugs .. stuff20:04
*** david-lyle_ has joined #openstack-meeting-alt20:04
nikhil_kwe go RC3 for glance20:04
nikhil_kfor covering out last min bugs and such20:04
nikhil_ka config issue conflicting with documentation was major reason for that20:04
nikhil_kso, what we do not have in Juno is20:05
nikhil_k#link https://bugs.launchpad.net/glance/+bugs?field.tag=juno-rc-potential20:05
*** zns has joined #openstack-meeting-alt20:05
*** zns has quit IRC20:05
*** e0ne has quit IRC20:05
nikhil_kfor varied reasons20:05
nikhil_knext up!20:05
nikhil_kPlease please please vote!20:05
nikhil_kfor the TC elections going on20:05
*** noslzzp has joined #openstack-meeting-alt20:05
nikhil_kBelieve the deadline is Friday20:06
flwangI have voted :)20:06
nikhil_knext is20:06
jokke_yeah it's fri by 1300 utc20:06
nikhil_ksome feedback from the ptl sync meeting20:06
*** david-lyle has quit IRC20:06
nikhil_kagood news for all20:06
nikhil_kwe will have a *full* pypi mirrow on the gates20:06
jokke_ \\o \o/ o// o/720:07
kragnizwooo!20:07
nikhil_kso,not only the req. but also the dep. will be mirrored20:07
flwangawesome20:07
ativelkovcool20:07
TravTso, I hope this means faster tests and less random failures?20:07
nikhil_k:)20:07
nikhil_khope so20:07
nikhil_kthere is no fixed date for the imlementation yet20:08
jokke_TravT: if the mirror is stable ;)20:08
*** kebray has joined #openstack-meeting-alt20:08
TravTjokke_: sshhh.... it'll hear you.20:08
nikhil_kI'll rush through here20:08
nikhil_ktentative deadline for confirming summit topics is Oct 28th20:08
nikhil_khowever, for Glance we'd confortable doing it well before20:08
nikhil_kis my understanding at this point20:09
nikhil_kso the email out to ML20:09
nikhil_kif anyone has a link to it :)20:09
*** zns has joined #openstack-meeting-alt20:09
nikhil_kso, if you think your topic needs discussion or further discussion in the summit please do add20:09
nikhil_k*however*20:09
nikhil_kwe've limited spots20:10
nikhil_kso please do keep that in mind20:10
nikhil_kagain20:10
nikhil_k#link https://etherpad.openstack.org/p/kilo-glance-summit-topics20:10
jokke_we have one meeting before the deadline ... let's agree what we push through week now based on what is proposed on the etherpad?20:10
nikhil_kwe may be missing flavio here20:10
nikhil_kjokke_: ohk yes, good point20:11
*** _nadya_ has quit IRC20:11
nikhil_klet's discuss the finalizing of topics in just a bit20:11
nikhil_kwe prolly should have release of store and client before the summit20:12
*** _nadya_ has joined #openstack-meeting-alt20:12
*** sgotliv has joined #openstack-meeting-alt20:12
nikhil_kif someone is affected by that please let me know and I will try to do it sooner than later20:12
*** tonytan4ever has quit IRC20:12
nikhil_kelse please expect delays as we fix stuff20:12
nikhil_k#topic Virtual Mini Summit20:13
*** openstack changes topic to "Virtual Mini Summit (Meeting topic: Glance)"20:13
nikhil_k#link https://etherpad.openstack.org/p/kilo-glance-virtual-mini-summit20:13
nikhil_k#link http://doodle.com/e42y2xvrhycqbmu520:13
nikhil_kplease try to go through the etherpad and do give me your feedback20:13
nikhil_kif the dates do not work please let me know too20:13
nikhil_kwill give a min here to let everyone digest that link20:14
nikhil_kand if there are questions20:14
*** wayne__ has joined #openstack-meeting-alt20:14
flwangnikhil_k: what's the time of the virtual summit?20:14
nikhil_kTBD20:14
TravTis vidyo, the new rackspace service you were mentioning?20:14
flwangnikhil_k: ok20:14
nikhil_kso, the in doodle I'd ask you to put your TZ  in20:14
flwanggot20:15
nikhil_khowever, the dates are relative to UTC20:15
jokke_nikhil_k: the timeslots for those two days?20:15
nikhil_kbased on interest and availability20:15
*** EricGonczer_ has quit IRC20:15
nikhil_kkind of a scheduling issue here hence, need feedback soon on that20:15
jokke_ok, fair enough .. I'll put myself up there, but can't commit before I have the times20:16
nikhil_kwe'd prefer to keep things closer to business times in UTC20:16
*** _nadya_ has quit IRC20:16
nikhil_kso, the possibility of the mini summit ranging over 2 days kind of seems more feasible20:16
nikhil_kjust to include everyone in the loop20:16
nikhil_k3-4 sessions per day20:17
nikhil_kshould we move on if there are no more questions?20:17
*** sgotliv has quit IRC20:18
nikhil_k#topic Introductions Part 220:18
*** openstack changes topic to "Introductions Part 2 (Meeting topic: Glance)"20:18
TravTis vidyo better than google hangouts?20:18
nikhil_kmuch20:18
ativelkovhangouts has a limit for the number of attendees20:18
nikhil_kvidyo here at the Rack can take upto 50 I guess20:18
jokke_I think the standard hangout is only like 10 people20:19
nikhil_kwe'll have to give it a try :)20:19
jokke_so that vidyo sounds good20:19
TravTok.20:19
jokke_nikhil_k: did you check the recording possibility?20:19
nikhil_kjokke_: not yet :)20:19
zhiyannikhil_k: what about i's quality for non-US user? like Asia pepople. any feedback for that?20:20
*** amitgandhinz has quit IRC20:20
nikhil_kzhiyan: good question, let's give it a dry run sometime soon before the event20:20
jokke_nikhil_k, zhiyan can we have small 15min test run like tomorrow on that to check the region quality?20:20
zhiyannikhil_k: will be great. ping me when you have chance.20:20
zhiyannikhil_k: thanks20:20
nikhil_kjokke_: zhiyan that sounds good20:20
jokke_I'm in Europe so we have all majors covered20:21
nikhil_k14UTC ?20:21
nikhil_kTravT: ?20:21
jokke_sounds good to me20:21
*** dboik_ has quit IRC20:21
nikhil_kfeel like we's span the globe as much as possible :)20:21
TravTYeah, i'm available.20:21
nikhil_kawesome20:22
nikhil_kintro volunteers please !20:22
*** dboik has joined #openstack-meeting-alt20:22
nikhil_k:)20:22
jokke_kragniz: can you join from office to check that it works within HP firewall?20:22
ativelkovDidn't we agree to update a wiki page with the team members info?20:22
kragnizjokke_: yeah, no problem20:22
jokke_ativelkov: I thought we did20:23
*** jehb has quit IRC20:23
*** otherwiseguy has joined #openstack-meeting-alt20:23
nikhil_kativelkov: that's a good idea, who has action item on that..?20:23
nikhil_kwe can do that later too20:23
nikhil_kintros!20:24
*** dimtruck is now known as zz_dimtruck20:24
kragnizI did an introduction last week!20:24
nikhil_kwho's new?20:24
nikhil_knice. thanks kragniz20:24
*** rondotcom has joined #openstack-meeting-alt20:24
nikhil_kdo I allocate slots for people? :)20:24
nikhil_kaight, this seems to be failing bad20:25
*** balajiiyer has joined #openstack-meeting-alt20:25
kragniznikhil_k: I think you're going to have to, if you want people to give them!20:25
jokke_I think we don't have other news than kragniz ;)20:25
nikhil_koldies then20:25
nikhil_khow about you?20:25
TravTwe have some new people in Intel, but they can't usually make the meeting20:25
jokke_he is the new new guy! ;)20:25
nikhil_kok TravT , can you please voluntter?20:26
TravTok.20:26
nikhil_kgive us some inspiration20:26
TravTI'm Travis Tripp from HP.20:26
*** kaitlin-farr has joined #openstack-meeting-alt20:26
TravTbeen working on cloud / openstack related projects for over 3 years20:26
TravTsomehow finally got to start working upstream starting this past February20:26
TravTand I LOVE IT!20:27
nikhil_kwoot!20:27
kragnizTravT: \o/20:27
zhiyanWelcome TravT!20:27
ativelkovthat is inspiring indeed)20:27
nikhil_kwelcome :)20:27
nikhil_kagree20:27
nikhil_kativelkov: next ?20:27
ativelkovok )20:27
ativelkovI am Alexander Tivelkov from Mirantis20:27
*** satish_ has joined #openstack-meeting-alt20:28
ativelkovHAve been with Openstack for about year and a half20:28
ativelkovCore contributor and ex-PTL (if they have PTLs for non-incubated projects) for Murano20:28
*** satish_ has quit IRC20:28
ativelkovHave been interested in Catalog-related stuff for openstack since february20:29
*** sgotliv has joined #openstack-meeting-alt20:29
ativelkovCurrently primary working on Artifact initiative.20:29
*** satish_ has joined #openstack-meeting-alt20:29
*** megan_w_ has quit IRC20:29
ativelkovWant to make Glance more and more important for all the projects across the eco-system, not only Nova20:29
*** megan_w_ has joined #openstack-meeting-alt20:30
ativelkovThat's it :)20:30
nikhil_kawesome!20:30
*** georgelorch has quit IRC20:30
TravT+1 ativelkov20:30
nikhil_kThat was great!20:30
zhiyanWelcome ativelkov! Let's make Artifact stuff get landing in K cycle.20:30
nikhil_kwelcome :)20:30
nikhil_kor welcome again :)20:31
*** georgelorch has joined #openstack-meeting-alt20:31
nikhil_kfor both20:31
*** amrith is now known as _amrith_20:31
*** satish has quit IRC20:31
*** kaitlin-farr has quit IRC20:31
nikhil_kjokke_: please don't miss the next meeting ;)20:31
nikhil_k#topic Planning, Priorotization, Focus, etc.20:31
jokke_;)20:31
*** openstack changes topic to "Planning, Priorotization, Focus, etc. (Meeting topic: Glance)"20:31
*** tedross has quit IRC20:31
nikhil_kdoes anyone feel blocked by me?20:32
TravTyeah, can you move to the left a litte?20:32
nikhil_klol20:32
nikhil_ksure20:32
TravTthanks20:32
nikhil_kthere ya go20:32
kragnizlol20:32
jokke_no no no, our left ;)20:32
nikhil_kI did, well let me try the other side now20:32
hemanthmyou're blocking me now, to the right please20:32
TravTno, now I can't see the TV20:33
*** megan_w_ has quit IRC20:33
nikhil_k:)20:33
*** megan_w_ has joined #openstack-meeting-alt20:33
nikhil_kanyways, that was just a question for following up on office hours20:33
nikhil_kwhich may be answered20:33
nikhil_kcouple of months down the line too20:34
ativelkovSo, we have J officially released, should we start with merging what is tagged  juno-backport-potential?20:34
nikhil_kjust keep in mind before yelling at me, please please :)20:34
TravTyeah, what is the meaning of RC3 if OpenStack was released today?20:34
jokke_TravT: RC3 was out, what 2 days20:34
nikhil_kRC3 is released, no?20:34
nikhil_kyes20:34
jokke_just a tarball to give out if something obvious blows up20:35
kragnizrc3 is tagged20:35
TravTok... just saw that earlier in the meeting and was lost20:35
nikhil_kso RC3 is just for fixing critical bugs20:35
ativelkovAh, I saw official J release notice in ML20:35
ativelkovwasn't it final?20:35
jokke_ativelkov: yeah that's today20:35
nikhil_kyes, it is20:35
nikhil_k2014.2.final20:35
jokke_so proposed/juno should be now stable/juno20:35
nikhil_kor 2014.2.0 final20:36
nikhil_kyeah20:36
nikhil_khowever, we may not be able to get all sorts of bugs in stable20:36
jokke_and we shouldn't20:36
nikhil_kthere are restrictions for post-release bugs20:36
kragniznikhil_k: what are they, out of interest?20:37
zhiyancross fingers20:37
jokke_should be really just security/stability?20:37
nikhil_kkragniz: what do you mean?20:37
nikhil_kjokke_: yes20:37
kragnizjokke_: okay, that makes sense20:37
*** noslzzp has quit IRC20:37
nikhil_kno config changes and anything that breaks the api20:37
TravTwhat is the criteria for backporting to stable?20:37
kragnizcool20:37
jokke_nor really "we didn't have time to implement this by release"20:38
nikhil_kTravT: I think they are laid out in wiki somewhere20:38
nikhil_kthere are finer lines though20:38
nikhil_kso, basically propose rationally and see if it works20:38
TravTi probably have one to submit.20:38
nikhil_kok20:38
jokke_and remember that it needs to be merged on master before it can land20:38
TravTour good friends in Intel are doing further checks.20:39
nikhil_kawesome20:39
nikhil_kchecking is gooooood20:39
nikhil_kanyways, we'd a last minute run this release20:39
*** gholler has quit IRC20:40
nikhil_kwe'd prolly try to avoid that next one20:40
*** noslzzp has joined #openstack-meeting-alt20:40
*** kebray has quit IRC20:40
nikhil_kI heard in nova they have a informal freeze20:40
*** emagana has quit IRC20:40
nikhil_kfrom kilo-220:40
jokke_nikhil_k: but they are beast size wise as well20:40
jokke_same as neutron20:40
nikhil_kyeah20:40
nikhil_kfor glance we can do kilo2.520:40
jokke_they need that extra time to stabilize20:40
nikhil_kor even 320:41
*** emagana has joined #openstack-meeting-alt20:41
*** emagana has quit IRC20:41
nikhil_kwe'll know a couple months down the line20:41
nikhil_kreally we just need more stuff going through gate20:41
nikhil_kfaster20:41
jokke_+120:41
kragniznikhil_k: wasn't freeze at j3 planned for this release cycle?20:41
TravTi think what we really missed was formally targetting bugs for a milestone.20:41
*** emagana has joined #openstack-meeting-alt20:41
nikhil_kand zhiyan should not be the one doing more than half of that20:41
kragniznikhil_k: I heard people talking about it, but it didn't seem to happen in glance20:41
nikhil_kTravT: yes, that too20:42
nikhil_kTravT: I'm a bit hesistent about the reviews as well20:42
nikhil_kwe'd a really linient review cycle for glance20:42
*** markwash__ has quit IRC20:42
*** ChuckC has quit IRC20:42
nikhil_kusually a simplest of patch takes at least 2-3 PS before landing (with changes)20:42
zhiyannikhil_k: frankly, imo team need pay more efforts on review instead of just push code up20:43
nikhil_kzhiyan: agree20:43
kragnizzhiyan: +120:43
zhiyannikhil_k: we have a lot of dead-end MPs there20:43
nikhil_kyes20:43
jokke_nikhil_k: also it seems that more simple the change is the more sloppy it also is regarding the styling etc.20:43
*** kopparam has joined #openstack-meeting-alt20:43
jokke_zhiyan: +120:43
nikhil_kkragniz: about the freeze, yeah .. I'm not sure, there were last minute changes20:44
zhiyanso probably I think in K, we can freeze feature MP pushup in K-2.5 (if have), and focus on review them more20:44
nikhil_kzhiyan: absolutely20:44
ativelkovAs they say, 10 lines of code = 12 comments, 300 lines of code = +1, LGTM :)20:44
nikhil_kativelkov: right on!20:45
kragnizis k2.5 a thing, or does that mean half way between k2 and k3?20:45
jokke_ativelkov: and quite often for good reason ;)20:45
kragnizativelkov: heh20:45
nikhil_kkragniz: ideally, we'd have specs approved by k220:45
jokke_ativelkov: not good trend 'though20:45
*** kebray has joined #openstack-meeting-alt20:45
zhiyanjokke_: for those tiny change, e.g. just one line, or doc update/sync, imho, we can just +2/A directly. and if have issue, we can push a revert commit soon later20:45
jokke_nikhil_k: can we just do spec freeze at k2?20:45
nikhil_kzhiyan: I'd not encourage to have just 1 +220:46
nikhil_k*NOT*20:46
*** noslzzp has quit IRC20:46
nikhil_kplease20:46
kragnizzhiyan: that has the risk of breaking the gate, right?20:46
nikhil_klet's stick to 2 +2s before +A20:46
nikhil_kunless20:46
jokke_zhiyan: I'm not that worried about those ... I'm more worried about the ones where even the commiter has not reviewd the change one pushed through with simple shell script20:46
nikhil_k*unless* we've certain conditions on the patch like a change needs to land before a certain date and no one is available for review20:46
kragnizjokke_: I think I know who you're talking about ;)20:47
jokke_kragniz: he's not the only one20:47
nikhil_kjokke_: so, good point20:47
nikhil_kwe need priorities here20:47
zhiyansorry just break from net20:47
nikhil_kwe'd ideally have a list of bugs/reviews to be done on priority20:48
nikhil_klike the tiny changes which jokke_ was talking about20:48
zhiyankragniz: i don't think so, due to breaking gate will block Jenkins merge it.20:48
nikhil_ksuch things add more pressure on the gate too20:48
nikhil_kif more PS are uploaded and such20:48
*** kopparam has quit IRC20:48
*** david-lyle_ is now known as david-lyle20:48
zhiyannikhil_k: 2 more +2s for normal case, of course, I just like to speed up those doc change, or global-req syncup, something like that.20:48
TravTyes, but better to get the simple changes pushed through early rather than piling up at the end of cycle when the gate is really backed up20:49
nikhil_kzhiyan: yeah, simple doc changes are really good20:49
jokke_nikhil_k: personally I'd like to see the bigger taking priority ... that 10 line change is way easier to rebase than the big one that has been sitting in the Q for a month20:49
*** ijw has joined #openstack-meeting-alt20:49
nikhil_khowever, we'd careful about a doc change which could break things20:49
nikhil_klike docs becoming inconsistent20:49
nikhil_kand we need to rush through on the very last day of cycle20:50
jokke_nikhil_k: I think there is difference of doc change and spelling correction here20:50
nikhil_kjokke_: yes, priorities in general20:50
nikhil_knot only smaller ones20:50
nikhil_ka theme based approach20:50
*** shohel02 has quit IRC20:50
nikhil_kwhere we focus on a particular BP/bug for reivew20:50
TravTit was so incredibly frustrating to be at the end of the cycle having to babysit a doc change through the 2 - 4 day merge at gate.20:50
jokke_nikhil_k: I think zhiyan is talkin of just direct approving the spelling corrections, translations etc. which I do +120:51
nikhil_kget it done, merge it or -2 it .. move one20:51
nikhil_kon*20:51
*** bdpayne has quit IRC20:51
nikhil_kjokke_: sure20:51
nikhil_kTravT: yeah, that's the biggest worry here20:51
nikhil_kok, just to point out we've 10 mins left20:51
TravTthat's why i'm not opposed to pushing simple changes early in the cycle.20:51
*** bdpayne has joined #openstack-meeting-alt20:51
TravTeven if lower priority.20:52
nikhil_kand we cruised into our painpoints discussion too20:52
TravTotherwise they'll get carried for multiple releases20:52
jokke_TravT: Thanks for taking the time and effort doing that. I was really happy to see that Doc part of the metadef!!20:52
nikhil_kTravT: yeah, thanks thanks thanks!20:52
nikhil_kreally appreciate that20:52
TravTno worries20:52
*** noslzzp has joined #openstack-meeting-alt20:52
nikhil_kand thanks to rosmaita as well who has taken care of such changes for us in the past quite often!20:52
*** balajiiyer has left #openstack-meeting-alt20:52
*** amcrn has joined #openstack-meeting-alt20:53
TravTlakshmiS also worked on docs20:53
TravTso he deserves extra credit20:53
jokke_nikhil_k: what you had next? I think you need to have that priority discussion with the cores.20:53
nikhil_kwoot to lakshmiS!20:53
nikhil_kjokke_: yes, I will try to do that once I'm authorized to20:54
*** ijw has quit IRC20:54
nikhil_kam still a proxy for Mark20:54
nikhil_kbut for somethings, I'm taking an excuse :)20:54
nikhil_k#topic Open Discussion20:54
*** openstack changes topic to "Open Discussion (Meeting topic: Glance)"20:54
jokke_nikhil_k: when's the transition ... I thought it was per release and we're officially on kilo now ;)20:54
*** ramishra has joined #openstack-meeting-alt20:55
zhiyannikhil_k: i have one20:55
nikhil_kjokke_: believe, it's during or after the summit .. not 100% on that though20:55
jokke_Logging!20:55
zhiyan#link http://lists.openstack.org/pipermail/openstack-dev/2014-October/048597.html20:55
nikhil_kjokke_: could be now really20:55
hemanthmI have one too20:55
nikhil_kFCFS20:55
nikhil_kzhiyan: go20:55
nikhil_kaight, how can we help on that zhiyan ?20:55
*** bdpayne has quit IRC20:56
zhiyanso folks, when/if you ok, please help review those changes asap, Doug proposed a worth point for projects20:56
*** bdpayne_ has joined #openstack-meeting-alt20:56
*** bdpayne_ has quit IRC20:56
ativelkovdo you have the list of patches somewhere?20:56
jokke_Spam Doug to give deprecation period as it is expected from every other project ;)20:56
zhiyanespecially on second #PS, it contains a change for 'upstream' policy.py20:56
*** bdpayne has joined #openstack-meeting-alt20:56
ativelkovah, got it20:57
*** barclaac has joined #openstack-meeting-alt20:57
nikhil_kyes, please do test the policy change?20:57
zhiyani just proposed that change hours ago, so before comments/update for oslo team, we need to make sure that is what we need20:57
zhiyanhttps://review.openstack.org/#/c/128881/20:57
zhiyanfor the upstream policy.py change20:58
nikhil_k#link https://review.openstack.org/#/c/128881/20:58
nikhil_kcool20:58
zhiyanthanks team20:58
zhiyani'm done. hemanthm20:58
nikhil_knext?20:58
hemanthmguess its jokke_20:58
* kragniz has one, too20:58
nikhil_kjokke_: go go go20:58
jokke_Logging: two changed have been hanging on rebase loop now 3 months20:59
nikhil_kdoes anyone have links?20:59
jokke_including change to i18n which is one of those Dougs painpoints20:59
*** ramishra has quit IRC20:59
jokke_    Glance refactoring logging https://blueprints.launchpad.net/glance/+spec/refactoring-glance-logging20:59
nikhil_klet's approve that soon20:59
jokke_    https://review.openstack.org/#/c/116626/ another rebase20:59
jokke_    https://review.openstack.org/#/c/117204/ likewise20:59
nikhil_k#link https://blueprints.launchpad.net/glance/+spec/refactoring-glance-logging21:00
nikhil_kcool21:00
nikhil_kwe'r out of time!21:00
*** barclaac|2 has quit IRC21:00
nikhil_k#endmeeting21:00
jokke_thanks nikhil_k21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Thu Oct 16 21:00:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-10-16-20.01.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-10-16-20.01.txt21:00
*** jokke_ has left #openstack-meeting-alt21:00
kragnizthanks all21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-10-16-20.01.log.html21:00
nikhil_kThanks all!21:00
*** markwash__ has joined #openstack-meeting-alt21:01
*** bdpayne has quit IRC21:01
*** Riddhi has quit IRC21:02
*** Riddhi has joined #openstack-meeting-alt21:03
*** wayne__ has left #openstack-meeting-alt21:03
*** Riddhi has quit IRC21:03
*** teran has joined #openstack-meeting-alt21:03
*** Barker has joined #openstack-meeting-alt21:03
*** Riddhi has joined #openstack-meeting-alt21:04
*** diemt has quit IRC21:05
*** padkrish has quit IRC21:08
*** teran_ has quit IRC21:08
*** tdruiva has quit IRC21:10
*** ChuckC has joined #openstack-meeting-alt21:13
*** esker has quit IRC21:13
*** EricGonczer_ has joined #openstack-meeting-alt21:14
*** noslzzp has quit IRC21:16
*** megan_w_ has quit IRC21:16
*** megan_w_ has joined #openstack-meeting-alt21:17
*** padkrish has joined #openstack-meeting-alt21:20
*** megan_w_ has quit IRC21:21
*** jjmb has joined #openstack-meeting-alt21:22
*** rondotcom has quit IRC21:23
*** andreaf has joined #openstack-meeting-alt21:23
*** rondotcom has joined #openstack-meeting-alt21:23
*** tzn has quit IRC21:26
*** emagana has quit IRC21:28
*** rondotcom has quit IRC21:28
*** emagana has joined #openstack-meeting-alt21:28
*** tchaypo has left #openstack-meeting-alt21:29
*** emagana has quit IRC21:33
*** doude has quit IRC21:33
*** emagana has joined #openstack-meeting-alt21:33
*** markwash__ has quit IRC21:35
*** gholler has joined #openstack-meeting-alt21:35
*** markwash__ has joined #openstack-meeting-alt21:36
*** bdpayne has joined #openstack-meeting-alt21:41
*** satish_ has quit IRC21:41
*** megan_w_ has joined #openstack-meeting-alt21:43
*** kopparam has joined #openstack-meeting-alt21:44
*** megan_w_ has quit IRC21:45
*** tbarron is now known as tbarron_away21:45
*** megan_w_ has joined #openstack-meeting-alt21:46
*** julim has quit IRC21:47
*** spzala has quit IRC21:47
*** zns has quit IRC21:47
*** spzala has joined #openstack-meeting-alt21:48
*** david-lyle has quit IRC21:49
*** rondotcom has joined #openstack-meeting-alt21:49
*** akoneru has quit IRC21:49
*** kopparam has quit IRC21:50
*** ijw has joined #openstack-meeting-alt21:50
*** rondotcom has quit IRC21:51
*** rondotcom has joined #openstack-meeting-alt21:51
*** xyang1 has quit IRC21:52
*** igordcard has quit IRC21:52
*** megan_w_ has quit IRC21:53
*** megan_w_ has joined #openstack-meeting-alt21:53
*** esheffield has quit IRC21:54
*** ijw has quit IRC21:55
*** ramishra has joined #openstack-meeting-alt21:55
*** rondotcom has quit IRC21:56
*** barclaac|2 has joined #openstack-meeting-alt21:56
*** dboik has quit IRC21:57
*** megan_w_ has quit IRC21:57
*** dane_leblanc has quit IRC21:58
*** barclaac has quit IRC22:00
*** cknight1 has quit IRC22:00
*** ramishra has quit IRC22:00
*** radez is now known as radez_g0n322:04
*** david-lyle has joined #openstack-meeting-alt22:05
*** kebray has quit IRC22:05
*** rondotcom has joined #openstack-meeting-alt22:05
*** rwsu has quit IRC22:07
*** rondotco_ has joined #openstack-meeting-alt22:07
*** rondotco_ has quit IRC22:09
*** rondotco_ has joined #openstack-meeting-alt22:09
*** rondotcom has quit IRC22:10
*** tdruiva has joined #openstack-meeting-alt22:11
*** EricGonczer_ has quit IRC22:11
*** rondotco_ has quit IRC22:11
*** rondotcom has joined #openstack-meeting-alt22:12
*** funzo has quit IRC22:15
*** funzo has joined #openstack-meeting-alt22:15
*** tdruiva has quit IRC22:16
*** EricGonczer_ has joined #openstack-meeting-alt22:16
*** AlanClark has quit IRC22:17
*** niclem has joined #openstack-meeting-alt22:20
*** Riddhi_ has joined #openstack-meeting-alt22:21
*** mestery_ has joined #openstack-meeting-alt22:21
*** kebray has joined #openstack-meeting-alt22:23
*** EricGonczer_ has quit IRC22:23
*** TravT has quit IRC22:23
*** mestery has quit IRC22:23
*** EricGonczer_ has joined #openstack-meeting-alt22:24
*** david-lyle has quit IRC22:24
*** bill_ibm has joined #openstack-meeting-alt22:24
*** padkrish has quit IRC22:24
*** Riddhi has quit IRC22:24
*** megan_w_ has joined #openstack-meeting-alt22:24
*** otherwiseguy has quit IRC22:24
*** EricGonc_ has joined #openstack-meeting-alt22:24
*** edhall_ has quit IRC22:24
*** bill_az has quit IRC22:24
*** Riddhi_ has quit IRC22:26
*** EricGonc_ has quit IRC22:26
*** Riddhi has joined #openstack-meeting-alt22:26
*** otherwiseguy has joined #openstack-meeting-alt22:26
*** Riddhi has quit IRC22:26
*** Riddhi has joined #openstack-meeting-alt22:27
*** kebray has quit IRC22:27
*** EricGonczer_ has quit IRC22:28
*** colinmcnamara has joined #openstack-meeting-alt22:28
*** padkrish has joined #openstack-meeting-alt22:29
*** edhall_ has joined #openstack-meeting-alt22:29
*** jecarey has quit IRC22:31
*** megan_w_ has quit IRC22:32
*** Riddhi has quit IRC22:35
*** EricGonczer_ has joined #openstack-meeting-alt22:35
*** colinmcnamara has quit IRC22:39
*** EricGonczer_ has quit IRC22:40
*** _amrith_ is now known as amrith22:40
*** kebray has joined #openstack-meeting-alt22:43
*** sgotliv has quit IRC22:44
*** kopparam has joined #openstack-meeting-alt22:45
*** kevinconway has quit IRC22:46
*** gondoi is now known as zz_gondoi22:46
*** ativelkov has left #openstack-meeting-alt22:47
*** rondotcom has quit IRC22:49
*** reed has joined #openstack-meeting-alt22:50
*** kopparam has quit IRC22:50
*** rondotcom has joined #openstack-meeting-alt22:50
*** luizfar has quit IRC22:50
*** ijw has joined #openstack-meeting-alt22:51
*** padkrish has quit IRC22:54
*** rondotcom has quit IRC22:54
*** ijw has quit IRC22:56
*** luizfar has joined #openstack-meeting-alt22:56
*** ramishra has joined #openstack-meeting-alt22:56
*** emagana has quit IRC22:57
*** HenryG_ has joined #openstack-meeting-alt23:00
*** ramishra has quit IRC23:01
*** rondotcom has joined #openstack-meeting-alt23:02
*** padkrish has joined #openstack-meeting-alt23:03
*** jmontemayor has quit IRC23:05
*** yamahata has joined #openstack-meeting-alt23:10
*** akoneru has joined #openstack-meeting-alt23:12
*** bdpayne has quit IRC23:16
*** Riddhi has joined #openstack-meeting-alt23:17
*** kebray has quit IRC23:20
*** padkrish has quit IRC23:21
*** marun has quit IRC23:26
*** padkrish has joined #openstack-meeting-alt23:29
*** dims__ has joined #openstack-meeting-alt23:30
*** dims__ has quit IRC23:33
*** dims_ has quit IRC23:33
*** dims_ has joined #openstack-meeting-alt23:34
*** marun has joined #openstack-meeting-alt23:36
*** saurabhs has quit IRC23:42
*** zz_dimtruck is now known as dimtruck23:45
*** kopparam has joined #openstack-meeting-alt23:46
*** juice has quit IRC23:46
*** edhall_ has quit IRC23:47
*** padkrish has quit IRC23:48
*** padkrish has joined #openstack-meeting-alt23:49
*** kopparam has quit IRC23:50
*** otherwiseguy has quit IRC23:52
*** alex_xu has joined #openstack-meeting-alt23:52
*** yamahata has quit IRC23:53
*** padkrish has quit IRC23:53
*** juice has joined #openstack-meeting-alt23:53
*** edhall_ has joined #openstack-meeting-alt23:54
*** ramishra has joined #openstack-meeting-alt23:57

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