20:00:10 #startmeeting barbican 20:00:11 Meeting started Mon Nov 14 20:00:10 2016 UTC and is due to finish in 60 minutes. The chair is dave-mccowan. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:15 The meeting name has been set to 'barbican' 20:00:18 #topic roll call 20:00:22 \o/ 20:00:45 o/ 20:00:52 o/ 20:00:57 hi arunkant redrobot 20:01:47 o/ 20:01:59 o/ 20:02:47 the faithful barbicaneers have gathered :-) 20:03:15 #topic Patches for CLI Updates 20:03:37 redrobot has done some great work on this. what's the latest? 20:04:08 I was waiting on reviews 20:04:18 looks like Kaitlin left a review since last I checked 20:04:35 o/ 20:05:06 I'll try to address Kaitlin's comments asap 20:05:09 there are 3 patches? 20:05:19 https://review.openstack.org/#/c/388267/ 20:05:31 #link https://review.openstack.org/#/c/388267/ 20:05:44 ^^ adds the field name renames 20:05:54 and 20:05:57 #link https://review.openstack.org/#/c/388981/ 20:06:02 ^^ adds --file 20:06:39 is https://review.openstack.org/382643 part of it as well (secret.id property) 20:07:32 dave-mccowan it's unrelated... I have to go back and fix that older patch, but it's lower priority than the CLI patches 20:07:59 I think we may want to add ID to the Service API first instead of just adding .id to the python lib 20:08:19 redrobot cool. thanks. i'll review those first two today as well. 20:08:56 is there any other CLI improvement work that should be done this cycle? 20:10:37 I think containers are kind of a pain, but I haven't thought about how to fix them 20:13:04 something to think about, maybe we can brainstorm on it in the channel sometime. 20:13:33 #topic certificate order api deprecation 20:13:33 we've made some progress on this. 20:13:42 diazjf committed doc changes to alert a reader of docs. 20:14:22 at the summit we discussed adding a config switch to turn off the API. the owner is listed as: redrobot or "new contributor" 20:14:47 any updates or volunteers for this one? 20:15:22 no updates from me, busy with other stuff atm 20:15:35 I could maybe help any new contributors who may want to start chipping away at this 20:16:17 we had a few new contributors at the summit. has anyone been in touch with them? 20:17:33 #topic returning entity_id property 20:18:13 at summit we discussed adding returning entity_id properties in our response bodies. in the past we've returned full entity_refs. (full URIs) 20:18:26 this was redrobot's item too 20:19:03 I think we need a spec first? 20:19:33 redrobot that makes sense. 20:19:53 I haven't started a spec on this 20:19:58 do we need to bump our API version to do this? 20:20:08 no, it's just adding a new property 20:20:24 and we would not remove the secret_ref or xxx_ref properties 20:21:33 cool. so this should be a straightforward implementation 20:22:03 #topic congrats to arunkant 20:22:24 congrats!!! arunkant :) 20:22:35 congrats to arun and welcome to barbican-core. his vote last week was unanimous 20:22:44 \o/ 20:23:33 #topic any other business 20:23:50 our review backlog is shrinking. thanks everyone; we've been making steady progress on it. 20:23:53 +1 congrats 20:24:36 next i'd like to shrink our bugs backlog. we have over 70 open bugs. i'm sure many are invalid/dups/user error, etc. 20:24:57 word of caution about adding fields to responses....Dev core has been restrictive/prescriptive on doing this without a version bump. Not a barbican concern until they are part of def core I suppose :) 20:25:33 if we each grab one or two launchad bug a week to triage, we'll be able to shrink that to a more manageable level 20:26:53 do we want to bump the version this release for any other reason? 20:28:39 last chance for any other topics today... 20:28:41 I'd say if we aren't part of def core yet, probably not an issue 20:29:00 * woodster_ lost track of if barbican is included in def core or not 20:29:33 woodster_ we're not. 20:29:44 cool, make it easier then :) 20:30:27 deprecating certificate orders will involve a version bump. 20:30:43 i think? 20:31:39 what version are we talking about? 20:31:54 dave-mccowan, redrobot api version? 20:31:55 the version in the api routes or the release version? 20:33:33 i could use a refresher on each of them, i guess. which ones do we need to worry about? 20:35:16 api routes are the /v1/blah versions 20:35:27 release version is the version that the rel team gives us 20:35:45 seems to go up every release 20:35:46 currently it's 3.0.0.0 20:36:26 There's also the API version which we use in the root response 20:38:28 is the v1 in /v1/orders always the same /v1/secrets, or would they be different? 20:40:43 i guess something to work out in the spec... 20:40:54 v1 shouldn't change until we make a v2 20:41:11 but the home response may say something like "version": "1.3" or whatever 20:43:33 thanks for coming everyone. :-) 20:43:33 #endmeeting