14:00:34 #startmeeting Glance 14:00:35 Meeting started Thu Mar 19 14:00:34 2015 UTC and is due to finish in 60 minutes. The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:38 The meeting name has been set to 'glance' 14:00:50 o/ 14:00:52 Roll call 14:00:54 o/ 14:00:55 o/ 14:00:58 o/ 14:00:58 o/ 14:01:00 o/ 14:01:02 o/ 14:01:04 o/ 14:01:24 o/ 14:01:28 o/ 14:01:44 o/ 14:01:48 #topic library stable release procedures 14:02:03 In case you haven't seen this 14:02:03 https://review.openstack.org/#/c/155072/ 14:02:19 The plan is to implement this for Kilo 14:02:20 o/ 14:02:30 Timeline: not sure 14:02:38 Affects: RCs 14:03:08 Features pending code review should try to understand the implications 14:03:37 Any concners/questions? 14:04:14 #topic Managing stable branch requirements 14:04:23 #link https://review.openstack.org/#/c/161047/ 14:04:27 just sped read the spec, seems like a good thing 14:04:38 One concern: What will be the basis of our stable branch for icehouse/juno? 14:04:50 oh 14:05:41 sigmavirus24: the information given was that it would be impl thru Kio 14:05:47 Kilo* 14:06:20 helps? 14:06:56 s/thru/from/ 14:07:54 sigmavirus24: should we move to the next one or do you need more info? 14:08:07 Nope. I misunderstood (or read an earlier version) 14:08:14 cool 14:08:57 About the stable branch reqs: that one is to help the gate and devstack like stuff 14:09:17 transient deps are planned to be handled more intelligently 14:09:40 So, even in this case I feel everyone should be aware while proposing changes 14:09:51 Especially so late in the cycle 14:10:11 Should we move on? 14:11:05 #topic Kilo K-3 status and updates 14:11:17 #link https://launchpad.net/glance/+milestone/kilo-3 14:11:36 3 BPs are still under code review 14:11:41 we need to merge one today 14:11:52 the other two can be FFEs 14:12:17 I can provide more details around the FFEs after discussing a bit with rel-mgr 14:12:49 The graduation of policy stuff seems quite well impl, thanks to sigmavirus24 ! 14:13:20 (strengthening of policy enforcer) 14:13:20 yeah, I reviewed this code, lgtm 14:13:38 there's two separate ones too 14:14:05 Can one more person please review the spec and please confirm that there would be no overlap with other potential impl like sharing, prop protection etc they have in place? 14:14:36 #info spec: https://review.openstack.org/#/c/149112/ 14:14:58 sigmavirus24: please do help us with both the links 14:15:06 (and some context on that if possible) 14:15:25 I can take a look 14:15:50 thanks mclaren 14:15:55 np 14:16:07 surhttps://review.openstack.org/146651 is related to the spec to enhance our ability to use policy.json 14:16:18 https://review.openstack.org/163163 upgrades glance to use the graduated oslo.policy 14:17:24 cool 14:18:58 I've sent a few emails over the past few days to update the people I thought should be really aware about status and plan for K3 14:19:31 if you're feeling that you are not aware of what's going on, please do let me know 14:20:10 Most of the emails did not seem to be effective on the ML so were directed towards inboxes of specific individuals 14:21:10 There has been some discussion and then pause in the activity on this spec 14:21:13 https://review.openstack.org/#/c/138051/ 14:21:16 (CIS) 14:21:44 o/ 14:22:22 That's all from me about K3 updates for now, I will try to send emails if things change or something needs attention 14:22:51 I will try to give some general updates in the next topic 14:23:07 nikhil_k: what about the documentation-related changes? They have to land today 14:23:28 ativelkov: Just coming to that in the next topic 14:23:38 Any other thoughts on this one? 14:23:48 ativelkov: is that DocImpact or /docs? 14:24:10 TravT: both, as far as I understand 14:25:45 #topic K3 general updates 14:25:58 https://wiki.openstack.org/wiki/Kilo_Release_Schedule 14:26:54 #info Mar 19th (today) is the General feature freeze, String freeze and DepFreeze 14:27:37 #info the FFE candidates have been announced on the ML : http://comments.gmane.org/gmane.comp.cloud.openstack.devel/48715 14:28:02 #info the Final two to make it would be announced later today/tomorrow 14:28:19 About the string freeze that affects the Doc changes 14:28:40 https://wiki.openstack.org/wiki/StringFreeze : Please read this wiki for some context 14:29:09 The configuration, installation and translations related changes need to be frozen along with the project freeze 14:30:22 Any concerns on these? 14:33:17 Ok, moving on for now. If there are any other concerns, email with subject line tag [Kilo] [Urgent] would be appreciated. 14:34:12 #topic Adopting keystoneclient Sessions in glanceclient 14:34:19 https://blueprints.launchpad.net/python-glanceclient/+spec/session-objects 14:34:46 Anyone has any context around this? 14:35:45 That specs sounds really interesting and something that would help a lot of folks. 14:35:50 spec* 14:36:48 Unfortunately, jamielennox proposed a BP as a spec and isn't going to get decent attn. 14:38:15 #info jamielennox: Please create a corres. spec against the glance-specs repo for your BP. https://github.com/openstack/glance-specs. 14:38:39 #topic Reviews/Bugs/Releases 14:40:13 I tried to create store and client releases yesterday however, due to an intermittent failure in test and slow gate that was blocking release notes, the plan is postponed to today. 14:41:07 Also, our release managers seem very busy at this point of time so, there is currently very low bandwidth in the project. 14:41:57 So, I just wanted to take a quick poll in terms of whether we need must-have or good-to-have approach on the release notes. 14:42:20 (Any thoughts?) 14:43:23 If nothing, I think we can presume that not enough people care and we cannot make it a mandate for release notes in the tree. A few on the LP should suffice. 14:43:30 (More on the ML) 14:43:31 short list of new features/changes and list of closed bugs with LP links. 14:44:30 Should that really be a blocker for the release though? I mean gate cycles are too expensive at this point of time. 14:44:34 good-to-have (as long as we have the usual online release notes) 14:45:59 cool, thanks. Seems like good-to-have for now. So, the current releases can go without if there's more trouble. I will try to get this sorted for future releases on the ML once and for all. 14:46:34 #topic Open Discussion 14:46:43 https://etherpad.openstack.org/p/kilo-glance-k3 14:48:25 That has some links for important reviews. Please try to see to the Documentation and Policy enforcer ones earlier than others (if possible today). 14:48:51 yes, sure 14:49:47 mfedosin: I don't think the architecture documentation would be frozen however, thanks for putting that link in the etherpad. 14:50:25 If nothing else.. 14:50:56 Thanks all! 14:51:02 thanks nikhil_k 14:51:04 thanks nikhil_k! 14:51:11 thanks :) 14:51:13 #endmeeting Glance