20:02:41 #startmeeting milk 20:02:42 Meeting started Mon Mar 17 20:02:41 2014 UTC and is due to finish in 60 minutes. The chair is sarob_. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:02:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:02:45 The meeting name has been set to 'milk' 20:02:54 roll call 20:03:03 I'm here. 20:03:10 I think that's it though. 20:03:26 good enough for me 20:03:56 I did some work last week and checked it in, but I haven't seen it on git hub. 20:04:14 let me check 20:06:34 strange 20:06:50 oh 20:07:24 you went through the check pipe 20:07:45 once its completed check tests 20:08:00 then it needs to be +2 for the gate pipe 20:08:31 you need to select review on #link https://review.openstack.org/#/c/80402/ 20:08:46 then +2 and approve 20:08:50 Hmm, ok I thought Approved would be enough. 20:09:24 So cancel the one I have there now? There doesn't seem to be a way to +2 now. So cancel and do it again? 20:09:34 Under "Reviewer" 20:10:02 see what I just did 20:10:28 i gave it a +2 and approved 20:10:38 It just shows checkmarks in both columns. I have +1 in both columns. 20:10:54 But anyway, I think I get it. Next time I'll do +2 20:11:36 infra guys can correct me, but i believe we can set the queue to accept +2 as min 20:11:51 default is to ask for both approved and +2 20:12:43 That's fine. I just didn't do that the first time, and then it doesn't give me the option. 20:13:20 i was slammed last week. I read the wiki contribution steps, but didnt go through them 20:13:25 (In that case I guess I'd cancel my review, and do it again with +2) 20:13:28 they seem okay 20:13:35 ? 20:14:03 It the case that I set the wrong review +1 or not approved etc. 20:14:18 It = In 20:14:32 MrJoshua: hmm, i think you just didnt add up to +2 20:14:38 MrJoshua: and approved 20:14:55 Yes, I get that, but I'm talking about changing it once it's entered inccorectly. 20:14:55 MrJoshua: i think we can set it to just +2 20:15:38 I think I've got it, now. So no worries. 20:15:38 MrJoshua: right 20:15:57 MrJoshua: zuul believes all is well 20:16:08 MrJoshua: the gatekeeper is never wrong 20:16:32 haha 20:16:46 Other than that, nothing new on my end. 20:17:12 MrJoshua: so what we do with the apiary in the repo 20:18:16 MrJoshua: use the apiary spec with python service to respond to requests? 20:18:19 It's editable and testable, and anyone can build a server that delivers that API. On the apiary site is a moch server that delivers the static data form the doc for testing. 20:18:55 MrJoshua: so how now brown cow? 20:19:42 http://milk.apiary.io 20:19:46 MrJoshua: start with a few to discuss apiary mock server 20:19:56 http://docs.milk.apiary.io 20:21:12 Changes to the github repo will not automatically get updated at apiary. For that someone has to have access to the apiary project, which you and I have and I think either of us can share. 20:22:25 I also have the C4 API which is much more complete, but had to pull it out because of some syntax error I didn't have time to fix. I'll put that in this week some time too. 20:23:16 Although this should be enough to get anyone starting as a django implementation requirement, I'm hoping to have the test framework incorporated this week as well. 20:24:12 MrJoshua: we need to add get /ServiceRegistry/{service}/metadata 20:24:34 MrJoshua: or would the metadata be returned by a get by defualt 20:24:41 MrJoshua: default 20:25:37 MrJoshua: then i believe first round of API is complete 20:25:41 MrJoshua: design 20:26:09 If you click on the GET it shows you what is returned. Yes I don't think I have medtadata there so I can fix that. 20:27:02 MrJoshua: im good with a separate call to return metadata 20:27:25 MrJoshua: we dont need to start overloading calls from the get go 20:27:57 Cool, but it's not there at all at the moment, so I'll add that path and return metadata. 20:28:23 cool 20:28:46 Oh, I have metadata under "AssetsServices" and it's included. 20:28:57 MrJoshua: ill start thread on ml to get the discussion going 20:29:12 cool 20:30:37 MrJoshua: #action MrJoshua will add separate GET for returning object metadata 20:31:58 #action sarob will ping ML on #link http://docs.milk.apiary.io/ as first revision of milk api 20:32:42 MrJoshua: so i resigned to promote the work so far and the work planned at NAB 20:32:50 MrJoshua: rather than demo anything 20:33:08 k 20:33:19 MrJoshua: id like to focus on creating project phases 20:33:28 MrJoshua: in the wiki 20:33:47 MrJoshua: without dates 20:34:10 MrJoshua: until we have at least one full time dev working on this 20:34:26 MrJoshua: we wont be able to commit to any dates 20:34:38 MrJoshua: and no reason to beat ourselves up on it 20:35:14 true 20:35:25 MrJoshua: my end state is support for various APIs 20:35:52 MrJoshua: does like still seem like the goal for you too? 20:36:23 I'm not sure what you mean by various APIs? 20:36:42 MrJoshua: cineglass, fims, openstack, 5thKind, etc 20:36:59 MrJoshua: aws, gce 20:37:15 Ah, yes. 20:37:32 MrJoshua: my vision is that the etcc api is glue 20:37:58 MrJoshua: for all the other stuff to get workflows through 20:38:13 MrJoshua: from beginning state to end state 20:39:03 MrJoshua: so one of the framework/etcc tools will likely be state management 20:39:19 MrJoshua: but i jump ahead 20:39:28 MrJoshua: baby steps here 20:39:44 Haha, yeah, but sounds good. 20:40:23 MrJoshua: im good with today 20:40:40 MrJoshua: anything else sir? 20:41:08 Good for me. 20:41:31 MrJoshua: then i call a wrap 20:41:42 MrJoshua: or cut or whatever 20:41:42 k 20:41:51 #endmeeting