21:03:02 #startmeeting 2016-09-21 discussion 21:03:02 Meeting started Wed Sep 21 21:03:02 2016 UTC. The chair is wking. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:03:02 Useful Commands: #action #agreed #help #info #idea #link #topic. 21:03:02 The meeting name has been set to '2016_09_21_discussion' 21:03:15 #chair mrunalp vbatts_ 21:03:15 Current chairs: mrunalp vbatts_ wking 21:03:29 https://github.com/opencontainers/runtime-spec/pull/567 21:03:39 #topic agressive namespacing 21:04:03 #link https://github.com/opencontainers/runtime-spec/pull/567 21:04:33 jhoward there were conflicts as I was adding Windows support, starting around resources 21:05:07 jhoward: if we take the hit now, the migration is painful now, but we're protecting ourselves from future collisions 21:05:26 jhoward: the alternative is to have platform files, which has been discussed before 21:05:43 jhoward: the spec isn't huge now, so I think per-platform files are overly complicated at the moment 21:06:10 mrunalp: The JSON will look nice because the JSON keys aren't namespaced 21:06:35 jhoward: the JSON keys aren't namespaced, but the JSON settings are (because a key is in the 'linux' object, etc.) 21:06:46 mrunalp: everyone please review #567 so we can land it 21:06:58 vbatts_: I don't have any particular objections 21:07:13 https://github.com/opencontainers/image-tools/issues/25 21:07:36 #topic image-spec -> runtime-spec configuration translation 21:07:42 #link https://github.com/opencontainers/image-tools/issues/25 21:08:13 the discussion is around "should we be doing this at all" and "how do we handle particular fields if we do" 21:11:48 vbatts_: there's going to have to be some translation, because the runtime spec isn't portable 21:18:00 mrunalp: we had a split before, but we had too few fields that were truly portable 21:19:01 before that: [why don't we just embed the subset of portable fields rather that a translation matrix] 21:21:17 I'd love to see v{major}.{minor} in the media types 21:21:48 vbatts_: to wrap up this one issue. The decoupling you're suggesting seems to make things a lot more complicated 21:22:08 vbatts_: but this is more about being a version mapping, even if there's versioning in the media types... 21:22:22 vbatts_: you can store exposed ports in an annototation 21:23:17 vbatts_: the GitHub issue (#25) does not convey this topic concisely 21:23:47 I can submit a PR to help ground my suggestions 21:24:08 vbatts_: another problem that folks are struggling with is the conversations get too deep and layered 21:24:38 A PR will help flatten some of the discussion for folks who aren't interested 21:25:36 #action wking will file runtime-spec and runtime-tools PRs around the localizer/sanitizer approach 21:25:47 https://github.com/opencontainers/runtime-spec/pull/573 21:25:56 #link Windows support in runtime-spec 21:26:03 #topic Windows support in runtime-spec 21:26:06 #link https://github.com/opencontainers/runtime-spec/pull/573 21:26:20 jhoward: this needs more maintainer review 21:26:33 mrunalp: I gave it a quick look and it looks fine to me. I'll give it another pass 21:26:41 mrunalp: other topics? 21:26:49 #topic console handling in runC 21:26:53 https://github.com/opencontainers/runc/pull/1018 21:26:57 cyphar: please review^ 21:27:14 dqminh: I'll take a look 21:27:25 mrunalp: vbatts_, anything else for image-spec? 21:27:38 #topic image-spec 1.0.0-rc1 21:27:48 vbatts_: most of the issues are mine, but I'm happy to share 21:28:09 #link https://github.com/opencontainers/image-spec/milestone/8 21:28:51 vbatts_: I've been going through image-spec on paper this week, and it's good to see other folks making the changes I want to see without me having to say anything 21:29:33 vbatts_: the volume has gotten a bit overwhelming recently. It would be good if things stayed more succinct 21:30:08 vbatts_: so help is welcome for anyone interested in running 'make docs' and reviewing the output HTML and PDF 21:30:17 #endmeeting