15:09:38 #startmeeting climate 15:09:40 Meeting started Fri Mar 14 15:09:38 2014 UTC and is due to finish in 60 minutes. The chair is DinaBelova. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:09:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:09:43 The meeting name has been set to 'climate' 15:09:46 jeblair, thanks 15:09:49 it helped 15:10:10 casanch1, cmart, bauzas - you here? :) 15:10:18 me here 15:10:21 :) 15:10:25 :) 15:10:26 me too 15:10:29 cool 15:10:31 I think I 15:10:36 will start :) 15:10:41 today's agenda: 15:10:42 https://wiki.openstack.org/wiki/Meetings/Climate 15:10:56 not many topics, but still :) 15:11:03 #topic Action items from the last meeting + reviews queries 15:11:10 #link http://eavesdrop.openstack.org/meetings/climate/2014/climate.2014-03-07-15.01.html 15:11:26 we had some things assigned, let's go through status 15:12:06 casanch1 start working on https://bugs.launchpad.net/climate/+bug/1285585 -> Pablo starting doing that :) 15:12:18 f_rossigneux - I see no progress :( 15:12:20 saf :( 15:12:23 sad* 15:12:30 for https://bugs.launchpad.net/climate/+bug/1240021 15:12:58 as for https://blueprints.launchpad.net/climate/+spec/tenant-to-project-ref - in progress 15:13:16 and as for https://blueprints.launchpad.net/climate/+spec/climate-tempest-testing - Swann did not start working on it 15:13:19 yes, I'll try to send it to review today 15:13:28 casanch1, cool 15:13:32 as for Tempest 15:13:33 have been working on the rework for notifications bp 15:13:42 Swann decided to unassign it 15:14:07 because of some events hapenning in his company 15:14:15 we'll see full update next week 15:14:43 so that's assigned items from last meeting 15:15:00 I think we'll continue working and that's ok 15:15:14 I'd like to move to next topic 15:15:19 ok 15:15:23 ok 15:15:27 it'll be Tempest testing BP assignment - I'll change order in wiki 15:15:30 #topic Tempest testing BP assignment 15:15:31 wait, so tempest is available? 15:15:45 casanch1, it needs to be implemented :( 15:15:52 ho ok 15:16:05 So I'd like to find people loving to spend their time on testing :) 15:16:19 I think I can take that.. 15:16:23 casanch1, do you know such crazy saint person??? 15:16:25 wooooow 15:16:27 I guess someone at Intel can take it 15:16:29 I'll need your help 15:16:32 :) 15:16:33 cmart, you're my angel! 15:16:38 :* 15:16:41 or demon... 15:16:41 we've done tempest work for another components 15:16:43 :D 15:16:43 :) 15:16:48 ok, cool 15:17:16 so, we have someone here that can help cmart :) 15:17:22 #action cmart Start working on Climate tempest testing 15:17:29 ok, but anyway 15:17:37 if you have any questions 15:17:41 feel free to ask me 15:17:45 Ok! 15:17:55 I'll do everything to help u 15:17:56 you asked for it! 15:17:58 :) 15:17:59 hahaa:) 15:18:22 #action DinaBelova assign Tempest testing BP to cmart 15:18:23 the dark side :) 15:18:25 so next topic 15:18:31 #topic 0.1.1 status 15:18:37 #link https://launchpad.net/climate/+milestone/0.1.1 15:18:49 sooo 15:19:01 It looks quite nice now 15:19:04 except one thing 15:19:14 as it was discussed on previous meeting 15:19:26 I don't like idea of having release without new name 15:19:32 well, we've chosen 15:19:36 Blazar is ok 15:19:57 and I sent mail to Lauren Sell from foundation 15:20:05 asking for some lawyers help :) 15:20:12 still waiting for response :) 15:20:22 what's the meaning of blazar? 15:20:34 A blazar is a very compact quasar (quasi-stellar radio source) associated with a presumed supermassive black hole at the center of an active, giant elliptical galaxy. Blazars are among the most energetic phenomena in the universe and are an important topic in extragalactic astronomy. 15:20:37 :) 15:20:46 astronomy topic in OS is popular :) 15:20:49 o_0 15:21:00 hehe 15:21:01 ;) 15:21:05 \o 15:21:10 bauzas! 15:21:11 sorry, was in a formal meeting 15:21:18 nice to meet you here :) 15:21:28 please take a look on log :) 15:21:35 sure 15:21:48 ok, so giving little mins :) 15:22:27 currently we're taking look on 0.1.1 status 15:22:52 it's bloked due do reviews in progress (but we have all implemented/needs code review, that's good) 15:22:58 blocked* 15:23:06 and due to new name checking 15:23:11 by foundation 15:23:15 got the log 15:23:40 ok so anything to help ? 15:23:40 #info DinaBelova wait till Tuesday - if no reaction from foundation, will try to send one more email 15:23:48 ok 15:23:51 well, we need code review 15:24:07 it'll be one of the main focuses next week, I guess 15:24:21 for me, bauzas and other core team 15:24:29 so we'll work on it 15:24:39 which ones are prorities ? 15:24:49 does someone have any questions for this topic? 15:24:55 none from 0.1.1 ? 15:25:20 bauzas, creating draft designs for state leases + new step in lease-creation 15:25:32 equal for VR/PR 15:25:34 for both 15:25:40 we need that 15:25:52 ok, I can handle that next week 15:25:58 let's discuss it thru etherpad 15:26:02 +1 15:26:11 I'll create it and amend the BP 15:26:17 please give me an action 15:26:32 #agreed Priorities for the next week: new name checking + designs for state leases and new step in lease-creation 15:26:59 #action bauzas create etherpad about designs and amend according BPs 15:27:01 ok 15:27:09 probably that's if for this topic 15:27:20 any questions? 15:27:21 thanks 15:27:40 ok, I'll move on 15:27:42 #topic Open discussion 15:27:47 sooo 15:27:54 I have one thing to look at here 15:28:15 I'd like to find volunteer to work on volume reservation concept 15:28:17 :) 15:28:32 what is that? 15:28:47 well, we have now only compute resources reservation 15:29:10 we need to prepare design, approve it, and then implement that reservation possibility for other resource types 15:29:18 volumes seem to be the easiest thing here 15:29:29 as it will look much like VM reservation 15:29:51 i would like to 15:29:59 and it'll work ok after new lease-create step will be implemented (allocate resources one) 15:30:05 casanch1m one more angel :) 15:30:09 ok, thanks 15:30:38 #action DinaBelova assign design preparation of volume reservation concept to casanch1 15:30:47 ok, so I have nothing to add here :) 15:30:57 I might need some help to get started 15:31:02 I have one thing to ask.. 15:31:04 we have to discuss on etherpad about the design for implementing volumes reservations 15:31:25 yes, that's why I say 'concept', no 'change' 15:31:29 :D 15:31:31 bauzas ok 15:31:32 :) 15:31:35 cmart, yes? 15:31:40 related to the tenant expiration dates.. Are you going to discuss it on Submit with the rest of the community? 15:31:48 yes! 15:31:50 sure! 15:31:59 well, that's a good opportunity yes 15:32:13 I simply think that before summit we can't do much... 15:32:28 I won´t be able to attend to the submit, so I'll leave it in your hands.. :) 15:32:33 as on summit we'll have opportunity to discuss that with rest of community in person 15:32:42 I'm going to be there :) 15:32:46 (casanch and pafuent) hands 15:32:47 cmart, as I know Cristian and Pablo will attend? 15:32:50 oh, yes 15:33:06 so you'll keep track on it :) 15:33:06 pablo will also go 15:33:13 cool 15:33:14 sure 15:33:16 great! 15:33:19 thanks 15:33:25 cmart, np 15:33:29 smth else? 15:33:45 one comment.. 15:33:52 #info Discuss tenant reservation concept on summit 15:33:57 yes, sure? 15:34:25 how do you guys handle the bp discussions? I was thinking on a possible bp, but I don´t know how is the process.. 15:34:39 well, there are two ways 15:34:40 no 15:34:41 three 15:34:48 1/ start discussion in ML 15:35:01 2/ create etherpad, give link and discuss it there 15:35:14 3/ simply create BP and discuss it in whiteboard 15:35:30 OK.. 15:35:41 I prefer first one, as created BPs are there for all time 15:35:50 you may just say "we won't implement it" 15:36:04 but really - that's your wish and your choice 15:36:08 so as you like 15:36:22 ok thanks 15:36:30 feel free for any of these 3 variants 15:36:42 I guess I may close meeting 15:36:47 any objections? 15:36:58 ok 15:37:00 no problem 15:37:01 not from my side 15:37:15 bauzas? ^^ 15:37:27 well :) 15:37:27 nope 15:37:30 #endmeeting