15:01:09 #startmeeting satori 15:01:10 Meeting started Mon Sep 8 15:01:09 2014 UTC and is due to finish in 60 minutes. The chair is zns. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:14 The meeting name has been set to 'satori' 15:02:39 Hi there - who's here for satori? 15:02:44 hola o/ 15:02:50 o/ 15:02:52 hola 15:03:30 o/ 15:03:41 #topic Action Items 15:04:27 Checking action items from last logged meeting http://eavesdrop.openstack.org/meetings/satori/2014/satori.2014-08-25-15.02.html 15:04:52 @samstav: you have to commits in the action logs. What was outstanding on those? 15:05:28 The keep-alive one seems to have been merged already. 15:05:44 The sudo - one I think we talked about adding a test for? 15:06:48 @zns, right. I think those links ended up there as my response to an action item that was assigned to me being completed 15:07:14 Cool. So next steps are clear on those, I think. 15:07:17 But the subsequent (still open) bug fix which is related still needs tests 15:07:28 yes, clear. 15:07:30 Could someone also review https://review.openstack.org/#/c/118843/. I +1ed it this morning. 15:08:06 nick-o: You had a powershell version check issue also. What's the status on that? 15:08:42 I haven't had time to look into that yet, I'm trying to get that done this week 15:08:56 so we need to move this action to next week's meeting 15:09:00 n1ck-o: sorry, used the wrong alias. 15:09:10 Cool. Is there a blueprint yet? 15:09:20 I think there is, it's been so long 15:09:24 let me check 15:09:40 If there's a blueprint, then we won't need an action item. 15:09:48 https://blueprints.launchpad.net/satori/+spec/powershell-version 15:10:05 I didn't know that blueprints and action items were mutually exclusive 15:10:19 neither did I, but that doesn't mean much ;) 15:10:41 Cool. So no action item needed. Submit a patch whenever you're ready. We're not really running openstack-synchronized releases right now. 15:10:44 DRY? 15:11:36 cool 15:12:08 sounds good :) 15:12:22 I see action items as a way to track things that need to be done so they don't fall off into the ether. Blueprints accomplish that. Normally, blueprints get scheduled for a milestone and a release manager hounds the owner for delivery. We're not doing that right now because we don't have any openstack dependencies. 15:13:17 #topic General Discussion 15:14:08 Anyone want to bring anything up? I don't have anything right now. 15:16:03 I put down 2 idea points last meeting, but I think the agent based provider still has some incubating to do. The other (ssl discovery) may not be a priority? 15:16:45 By "monitoring agent" you mean the Rackspace Cloud Monitoring agent? 15:16:55 yes 15:17:15 That's a Rackspace non-open source agent. We could add that as a library to import, but I'm not sure it belongs in satori. 15:17:34 I mean the agent is open source, but Cloud Monitoring is not. 15:18:24 I see. 15:18:57 Not sure at this point if there is any generic work we'll need to do for that. 15:19:00 FYI Ideas can also go in as blueprints and they get discussed, approved, or rejected as blueprints. Bringing them up here is totally valid, but also document them as a blueprint. 15:19:33 What do you mean by SSL/TLS checks? You mean checking the certificate of an endpoint? 15:19:57 @zns yes 15:20:15 I like that. Yes. We could port the code we use internally. 15:20:59 If you add it as a blueprint I will approve it. 15:21:02 There is a lot of static data in that module... Maybe we could look into a maintained lib 15:21:13 Cool, I'll add the blueprint. 15:21:49 The static data comes from the SSL spec or header file from OpenSSL, I think. 15:22:06 ... but that may be a netter discussion to have on the patch. 15:22:11 better 15:22:19 :+1: 15:22:32 Cool. 15:22:37 Anything else? 15:23:18 I know what I need to do. Nothing else from me 15:23:32 Cool. Going twice... 15:23:53 OK. Thanks all. See you next week. 15:23:57 #endmeeting