20:00:04 #startmeeting barbican 20:00:05 Meeting started Mon Jul 27 20:00:04 2015 UTC and is due to finish in 60 minutes. The chair is redrobot. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:09 The meeting name has been set to 'barbican' 20:00:14 #topic Roll Call 20:00:17 ٩(。•ω•。)و 20:00:17 o/ 20:00:18 o/ 20:00:18 o/ 20:00:21 heyo/ 20:00:22 o/ 20:00:23 o/ 20:00:24 o/ 20:00:26 o/ 20:00:28 Greetings 20:00:32 o/ 20:00:49 chellygel always has the Ctrl+V ready to go :D 20:01:01 seriously... 20:01:03 o/ 20:01:05 * elmiko is impressed 20:01:05 cmd+v ;) 20:01:15 Woot! Lots of barbicaneers here today. 20:01:46 Sorry if I'm a little out of it today guys... I was at OSCON last week, and I'm still trying to catch up on everything... 20:02:04 Let's get this party started 20:02:13 #topic Action Items from previous meeting 20:02:48 #link http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-07-20-20.00.html 20:02:53 which it looks like there was none 20:03:02 but I do remember one action item from last last meeting 20:03:13 #link http://eavesdrop.openstack.org/meetings/barbican/2015/barbican.2015-07-13-20.01.html 20:03:28 jaosorior to backport the DogTag gate fixes into stable/kilo 20:03:30 jaosorior any updates on that? 20:03:37 yeah, the backport is on-going 20:03:44 BUT, the tests in stable/kilo fail 20:03:51 for reasons unrelated to the backporting 20:03:59 ugh, lame 20:04:00 which is the reason that I asked redrobot for help 20:04:05 ok, so we should sort out the failures first 20:04:17 #action redrobot and jaosorior to fix the stable/kilo gate failures 20:04:21 This is the first commit in the backport series https://review.openstack.org/#/c/205059/ 20:04:28 and i'll punt on the other one to next week 20:04:37 #action jaosorior to backport the DogTag gate fixes into stable/kilo 20:05:03 and now that I think about it, I had promised kfarr a Castellan release, and then totally dropped the ball 20:05:09 * redrobot would make a good politician 20:05:19 it's ok redrobot :) 20:05:45 but it seems there's a lot of patches pending.... do we want to release now, or wait until we go through the current Castellan patch queue? 20:05:50 i have a question, or two, about castellan releases. maybe we could circle back around later? 20:06:00 ok, I'll add it to the agenda 20:06:21 which can be found here: 20:06:28 #link https://wiki.openstack.org/wiki/Meetings/Barbican 20:06:49 ok, let's move on to the agenda topics for today 20:06:58 #topic Blueprint Deadline this Friday 20:07:07 0o/ 20:07:08 #link https://wiki.openstack.org/wiki/Liberty_Release_Schedule 20:07:21 Liberty Milestone 2 is due this week 20:07:43 I'm sure the release managers would like to cut it tomorrow, but I may be able to push until Thursday if there's stuff in the queue that we want to land before then. 20:07:55 #action redrobot to do some Launchpad grooming for Liberty-2 20:08:16 which means that this week is the deadline for Liberty milestones 20:08:24 #link https://review.openstack.org/#/q/status:open+project:openstack/barbican-specs,n,z 20:08:31 we still have a lot of pending specs 20:08:36 most of them have -1 votes on them 20:10:12 Any questions/comments about the next milestone, or the Blueprint freeze? 20:10:41 If we don't get a bp approved by Thursday is it gone forever? 20:10:51 silos nope, you have to re-submit for M 20:11:02 silos just won't land on Liberty 20:11:10 ok. understood. 20:11:40 I'll probably be pinging people for reviews throughout the week. 20:12:00 Both for spec reviews, and also to get status updates on approved specs 20:12:57 ok, moving on 20:13:02 #topic Barbican Mid-Cycle 20:13:17 I just noticed we're listed on this fancy new events page: 20:13:19 #link https://www.openstack.org/community/events/#mid-cycle_sprints 20:13:37 hopefully everyone has booked flights/hotels etc 20:13:49 but if you still need the details, you can find them here: 20:13:52 #link https://wiki.openstack.org/wiki/Sprints/BarbicanLibertySprint 20:14:07 looking forward to visiting JHU next week :) 20:14:17 woot! 20:14:19 any questions/comments about the mid-cycle? 20:14:29 What do I need to do? 20:14:47 You can let me know offline, but I want to make sure I have everything ready. 20:15:16 I figure seating and some food, but did not know if I need to do anything else. 20:15:47 Projector? The rooms should already have those 20:16:01 are there instructions somewhere about where to go and how to check in once we get to the address? not sure if there will be guards and gates, etc. 20:16:11 rellerreller: do you need a final list of folks going for your security folks? 20:16:36 So we will be outside the perimeter, so no need to checkin or anything. 20:16:58 We have a night school center where people can earn masters degrees. We will be in there. 20:17:08 Here: http://www.jhuapl.edu/ourwork/facilities/kossiakoff.asp 20:17:09 rellerreller: ha, I'd never seen that link before...I see the eventbrite registration 20:17:30 We can post a map and other instructions on etherpad. Is one setup? 20:17:52 We should put this link on the etherpad, it's got a map for parking: https://ep.jhu.edu/about-us/locations/applied-physics-laboratory 20:18:15 is there a room number? 20:18:25 rellerreller yep, let me get the link 20:18:28 #link https://etherpad.openstack.org/p/barbican-liberty-midcycle 20:18:34 kfarr let's get some cardboard signs and hang them up! 20:18:59 rellerreller Yeah! 20:19:04 dave-mccowan we will post signs and let you know where to go. 20:19:06 balloons? 20:19:44 who's bringing licorice liquor? 20:19:48 elmiko that would be awesome. We can have them drop from the ceiling when you enter. 20:20:05 rellerreller: haha, now i wish i could attend 20:20:26 woodster_ that brings up a good point. We have a pretty strict no alcohol policy :( 20:20:54 womp womp... 20:20:58 lol 20:21:01 I was reminded by my superiors about that today :( 20:21:05 well, I can't make it to this mid-cycle :/ 20:21:17 but maybe we'll be extra productive without the Finnish liquor 20:21:23 jaosorior, :( 20:21:31 so your livers will take it easy... this time O_O 20:21:32 well, it's not too late to have the midcycle over here :) 20:21:36 or...easier :P 20:21:37 jaosorior I'll drink extra in your honor 20:21:51 redrobot: haha hell yeah 20:22:12 midcycle with no Ozz??? 20:23:19 woodster_: unfortunately 20:23:50 jaosorior: maybe we can video you in...middle of the night for you, could be scary/entertaining 20:24:25 redrobot, I have to say that the licorice liquor was intrumental in heading off a heated argument about content types and/or castelan certificates -- so we may end up being less productive .. 20:24:40 haha! 20:24:53 woodster_, jaosorior -- and yeah, its Oz's turn as the wizard of Oz .. 20:24:57 next time I see you guys, I'll make sure to be well stocked with liquor :P 20:24:59 alee lol, that's true... but I don't think rm_work is going to make it so we may be safe 20:25:48 ie. disembodied green head at the centre of everything .. 20:26:00 yeah but i will try to call in 20:26:06 unless there are.... "network complications" :P 20:26:41 ok, so, we'll be looking for the cardboard signs once we get on campus... 20:26:43 whats that -- I thougt I heard rm_work say something .. oh well, must be a glitch .. 20:26:59 we'll have another chance for an update next week before everyone flies out. 20:27:15 moving on... 20:27:17 ha! 20:27:28 #topic V2 and Orders 20:27:34 jvrbanac you have the floor 20:27:42 So I don't really want discuss V2 and Orders today, but rather I just wanted to get people to start thinking about it. During the midcycle I want have a discussion about a v2 api and talk through some ideas I have around it. I know a bunch of us probably won't make it to Tokyo, so I would like to use the midcycle for some face-to-face time on this subject. Again, not really a subject for today, but something to 20:27:42 start thinking about. 20:28:30 jvrbanac what kinds of things are you thinking about? 20:28:46 New types of orders? Is there an etherpad page? 20:29:06 Yeah... definitely want to take time to think through the pain points in V1, so we can fix a lot of them in a future V2 20:29:38 rellerreller, not really. I have a bunch of ideas that have come out of trying to deploy barbican. It would really go way past the time in the meeting 20:29:41 rellerreller first thing that comes to mind for me is renaming "payload_content_encoding" to "transport_encoding" 20:29:53 rellerreller, hense why I wanted to bring this up during the mid-cycle 20:30:09 jvrbanac agreed... lots of room for bikeshedding :) 20:30:33 it would also be good to start adding link sections to our responses 20:30:53 2015-07-27 15:29:00,083: INFO: root: MIGRATION DOWNTIME VALUES: last_success_old_host=1438028825.27, first_failure=1438028826.23, last_failure=1438028940.07, first_success_new_host=1438028826.55, DOWNTIME<=1.28269696236s 20:30:57 typo 20:31:04 { ... "links" { "self": "http://reference_to_myslef" } } ... etc 20:31:26 jvrbanac, redrobot sounds like a design page/ etherpad needed to collect all these ideas .. 20:31:34 Yeah, I have a bunch of ideas around this subject, but I also want to hear from other folks on the pains they've had using barbican in a prod type setting 20:32:03 probably want to consider microversions for a next gen api as well 20:33:25 elmiko, is that something other projects are adopting? 20:33:56 jvrbanac: starting to, i'm not sure how widespread it is but i am pushing this for sahara v2, and i think nova is moving forward with it as well 20:34:05 jvrbanac yeah, nova is using microversions now 20:34:14 i also saw neutron discussing this as well 20:34:49 interesting ok. 20:35:05 i think it really depends on how much the team expects to iterate on the api, it's really nice when you want to add many changes, some of which might not be backward compat. 20:36:14 Sounds like a good discussion to have 20:37:08 redrobot, that's all I had that agenda item. Just something for people to think about and bring to the midcycle 20:37:25 ^bring ideas to the midcycle 20:38:48 redrobot, did you die? 20:39:00 jvrbanac lol, not yet 20:39:09 ok moving on 20:39:20 #topic stable/kilo tests are failing 20:39:30 jaosorior you want to talk about this some more? 20:39:52 Nah, just to raise awareness for people 20:40:10 jaosorior cool 20:40:12 I didn't expect it to get mentioned int he beginning of the meeting. So yeah, that one's done 20:40:23 we did add the action item earlier in the meeting, so we'll be looking into that. 20:40:34 ok moving on 20:40:42 #topic Barbican Openstack CLI plugin 20:40:47 jaosorior also yours 20:41:18 yup 20:41:21 the CR is up https://review.openstack.org/#/c/198732/ 20:42:02 At the moment the plugin has some limitations 20:42:09 jaosorior Haven't really dug into it, but what's the deal with the command names? 20:42:22 would it make sense for them to be key-manager like the Governance repo change? 20:42:38 redrobot: Well, I also intended there to be some discussion around those 20:42:59 thing is, "container create" and such is taken 20:43:22 and on the other hand, doing "orders" and operations with containers doesn't really make sense in the context of the openstack CLI 20:43:57 so I intended that tto be more explicit by renaming it to something such as "secret order [create|delete...]" 20:44:34 hmm... would the secret abstractions make sense, you think? 20:44:47 or maybe something that is more akin to using openssl on the command linke 20:44:49 *line 20:44:53 we also talked with the openstack-sdks fellows about the naming, and the discussion went around, using the project name prepended to the commands is not ideal 20:44:58 openstack key-gen rsa 2048 20:45:39 well, if there are better suggestions, lets add them to that CR 20:46:00 some people were ok with prepending "secret" to orders and containers, but if there are better ideas, they are very welcome 20:46:16 how closely does the CLI follow the other project abstractions, I wonder? 20:46:24 what do you mean? 20:47:08 like, is there a 1:1 mapping of API resource to CLI command? 20:47:25 jaosorior, whats the suggestion for things like certificate orders? not sure we would want "secret order ..." in this case. 20:47:29 or can we approach this from a "what would a CLI user want to do" point of view? 20:47:49 i think it's good to approach from the use-case point of view 20:47:55 redrobot: IMO I would rather have it as "what would a CLI user want to do" 20:48:34 redrobot: this is what exists at the moment http://pastebin.com/WWTmLa9w 20:49:15 ^^ that list does not include non-core projects like congress though, right? 20:49:28 which do things ... differently? 20:49:33 rm_work: that is handled as plugins 20:49:42 this discussion was last week, way outside of my short-term memory :P 20:49:43 so to enable a plugin you basically do a normal installation 20:49:49 python setup.py install 20:49:54 the existing container is for Swift containers? 20:49:54 jaosorior: right, but as far as current usage examples 20:49:58 and it is handled by the entrypoints that you set up in setup.cfg 20:49:58 and how other projects did their naming 20:50:25 IIRC one of their examples was "look how congress did their naming" 20:50:34 redrobot, rm_work: By the way, that list has the barbican operations with the dash... because I had that installed in that virtual environment. The current CR doesn't have that dash 20:51:16 rm_work: if you remember the conversation we had with the openstack-sdks folks, adding the project name before the commands was not very recommended, and we figured it wouldn't really be that appropriate usability wise 20:51:25 might we talk about castellan breifly, since we are short on time? 20:51:32 alee: currently you have to add --request type if you would do a secret order create 20:51:33 jaosorior, huh ? so its "secret container create" instead of "secret-container create" ? 20:51:38 elmiko +1 20:51:41 alee: yes 20:51:56 jaosorior, I like secret-container better 20:52:11 alee: It breaks uniformity, that's why I had to switch it back to using spaces 20:52:14 elmiko yeah, let's move on to castellan 20:52:20 we had that discussion with the openstack-sdks folks 20:52:25 yeah there are consistency issues 20:52:28 but +1 castellan 20:52:28 I don't think we're going to figure out the CLI stuff now 20:52:38 ok, moving on 20:52:41 #topic Castellan 20:52:48 alee: But if it has a very different workflow and it would improve usability, we could do a command specifically for certificates, so we wouldn't need be adding all those extra params to the order create 20:53:00 On a side note about Castellan, there's a bunch of merge requests out there that could use some reviews 20:53:06 +1 20:53:06 anyway, please give feedback in this CR https://review.openstack.org/#/c/198732/ 20:53:13 jaosorior, yes 20:53:29 #link http://eavesdrop.openstack.org/irclogs/%23openstack-sdks/%23openstack-sdks.2015-07-23.log.html#t2015-07-23T14:38:59 20:53:34 i'm also very curious about the release schedule for castellan 20:53:41 ^^ discussion with openstack-sdk people 20:53:46 I don't see other projects using the dash in that list 20:53:48 useful to review so we don't go in circles 20:54:01 there are some features i've been waiting for before we interate with sahara, and i'd like to get them in for L3 so we can move our secrets out of sahara 20:54:03 woodster_ No other project is, which is why we switched to using spaces instead of dashes 20:54:14 I gotta go, talk to you guys tomorrow 20:54:15 elmiko release schedule is whenever kfarr or anyone else bugs me for a release :) 20:54:19 i'm curious if there will be a castellan release in the L3 timeframe? 20:54:23 redrobot: we need to merge some stuff first 20:54:26 jaosorior: oh got it 20:54:27 redrobot: ok, awesome. 20:54:37 there are about 3-4 CRs for Castellan that just need +A 20:54:39 rm_work: yes please =) 20:54:43 elmiko the release management team decided not to take ownership of Castellan 20:54:49 elmiko so I still own the release for that 20:54:51 and then a few more than need to be double-checked for merge conflicts and also merged 20:55:00 redrobot: cool, and release means push to pypi as well? 20:55:02 *that need 20:55:27 elmiko yes. it's pretty easy actually. Just use GPG to sign a git tag, and push it to the repo 20:55:39 i agree with kfarr and rm_work, maybe we could get a review sprint on this week, and talk about release dates sometime soon? 20:55:40 elmiko automation picks up the tag, verifies it, and then pushes the bundle to PyPI 20:55:48 redrobot: kickass 20:56:19 yeah... we can probably release next week during the mid-cycle 20:56:35 we should really merge some of these patches first though 20:56:44 and resolve whatever conflicts arise 20:56:53 elmiko agreed... I'll spend some time on those today hopefully. 20:56:58 \o/ 20:57:03 thanks redrobot! 20:57:14 yeah most are ready to go 20:57:24 ok, that's all we have time for today. See y'all next week, same time, same channel. :) 20:57:34 #endmeeting