We have a few different element types in our arrays, so it's useful to
clarify the element type for the property being specified. Before
this commit:
$ sed -n 's|.*\*\*`\([^`]*\)`\*\*[^(]*(\([^,]*\),.*|\2|p' *.md | sort | uniq -c | grep array
7 array
1 array of ints
8 array of objects
13 array of strings
All of the bare 'array' instances turned out to be arrays of objects.
Signed-off-by: W. Trevor King <wking@tremily.us>
On Thu, Mar 09, 2017 at 08:37:55AM -0700, Chris Aniszczyk wrote [1]:
> summarizing the discussion, how about we just alternative the time like
> Jonathan discussed?
>
> I believe that's the only fair thing to do and it's reassuring to hear from
> people like Phil who would be able to make the time along with others.
>
> I'm fine with the current time (1000AEST/1500PST/0000CET) and then
> 0400AEST/0900PST/1800CET
The 8am Pacific time ended up working out better than 9am for Jonathan
and Samuel [2,3], so I've used that instead of 9am. The 8am slot was
confirmed as the most popular slot in a Doodle poll [4], with the
following folks approving that slot:
* David Lyle
* George Lestaris
* Jonathan Boulle
* Julz
* Michael Crosby
* Mike Brown
* Mrunal Patel
* Phil Estes
* Rob Dolin
* Samuel Ortiz
* Stephen Day
* Stephen Walli
* Vincent Batts
* W. Trevor King
Removing those folks, the second most popular slot is 5pm Pacific,
with the following folks approving that slot:
* Aleksa Sarai
* Keyang Xie
* Lei Jitang
* Ma Shimiao
* Qiang Huang
Stephen and Mrunal approved both slots, and since they frequently
anchor the runtime and image conversations respectively, there should
be sufficient continuity between the two meetings.
The only person voting in the Doodle poll who didn't approve either
slot is Tianon.
Folks with a POSIX ‘date’ command can find the week number with [5]:
$ date +%V
There may be some doubling up around the end of the year, but we're
usually canceling meetings around then anyway.
The 8am Pacific meeting gets the odd slot because it's Europe-friendly
and lots of folks will be in Europe on 2017-03-29 for KubeCon [6].
I'd be happier with meeting times anchored to UTC to make life easier
for folks outside of the US, but one change at a time ;).
Future bumps to meeting.ics should bump LAST-MODIFIED [7] or DTSTAMP
[8] for any altered components. We can't use DTSTAMP in the VEVENT
because VEVENTs require DTSTAMP [9].
The timezone entry is based on the America/New_York example from [10].
Figuring out a single RRULE to cover both meeting times was beyond my
abilities, and while RFC 2445 allowed multiple RRULEs in a single
VEVENT [11,12], RFC 5545 does not [13]. Something like:
RRULE:FREQ=YEARLY;BYDAY=WE;BYHOUR=8,17;BYSETPOS=1,4,5,8,9,...
should be legal (at least for 2017), but Google Calendar [14] doesn't
seem to respect BYHOUR expansion, and ICAL.js [15] doesn't seem to
respect the BYSETPOS limit, so I gave it up and went with two events.
To stick strictly to the ISO weeks we could use:
RRULE:FREQ=YEARLY;BYDAY=WE;BYWEEKNO=13,15,17,19,21,23,25,27,29,31,33,35,
37,39,41,43,45,47,49,51
and:
RRULE:FREQ=YEARLY;BYDAY=WE;BYWEEKNO=14,16,18,20,22,24,26,28,30,32,34,36,
38,40,42,44,46,48,50,52
but that's tedious to type, and folks probably don't care all that
much about ISO weeks. I've gone with WEEKLY and INTERVAL=2 to give us
something that might survive the end of the year.
The ICS was validated with [16].
The CRLF line endings are intentional [17], and the .gitattributes
entry ensures we keep them. The committed files will still have LF
endings, which can confuse 'git diff ...', but you can use
--ignore-space-at-eol to see what really changed.
[1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/mh7FYse2BAAJ
Subject: Re: Moving the OCI Call (again)
Date: Thu, 9 Mar 2017 08:37:55 -0700
Message-ID: <CAJg1wMTCGEFRuKoKBEbUPdho82TVH8sPZdGORK_NA2vCNe+w9w@mail.gmail.com>
[2]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/ULXnARy9BAAJ
Subject: Re: Moving the OCI Call (again)
Date: Thu, 9 Mar 2017 18:33:34 +0100
Message-ID: <CAPWU_0rByhFp=jQQ6cvagHJuYmeTvN7T1zAW+oZR3=F1W8b_rw@mail.gmail.com>
[3]: https://github.com/opencontainers/runtime-spec/pull/719#pullrequestreview-26109314
[4]: http://doodle.com/poll/zu664785gb59pwkg
[5]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html
[6]: http://ircbot.wl.linuxfoundation.org/meetings/opencontainers/2017/opencontainers.2017-03-22-21.00.log.html
[7]: https://tools.ietf.org/html/rfc5545#section-3.8.7.3
[8]: https://tools.ietf.org/html/rfc5545#section-3.8.7.2
[9]: https://tools.ietf.org/html/rfc5545#section-3.6.1
[10]: https://tools.ietf.org/html/rfc5545#page-69
[11]: https://tools.ietf.org/html/rfc2445#section-4.6.1
[12]: https://tools.ietf.org/html/rfc2445#section-4.8.5.4
[13]: https://tools.ietf.org/html/rfc5545#appendix-A.1
[14]: https://calendar.google.com/
[15]: http://mozilla-comm.github.io/ical.js/
[16]: https://icalendar.org/validator.html
[17]: https://tools.ietf.org/html/rfc5545#section-3.1
Signed-off-by: W. Trevor King <wking@tremily.us>
Add support for Intel Resource Director Technology (RDT) / Cache Allocation
Technology (CAT). Add L3 cache resource constraints in Linux-specific
configuration.
This is the prerequisite of this runc proposal:
https://github.com/opencontainers/runc/issues/433
For more information about Intel RDT/CAT, please refer to:
https://github.com/opencontainers/runc/issues/433
Signed-off-by: Xiaochen Shen <xiaochen.shen@intel.com>
The:
"type": [
"string"
]
syntax added in 652323cd (improve seccomp format to be more
expressive, 2017-01-13, #657) is not valid:
$ ./validate ./config-schema.json <../config.json
The document is not valid. see errors :
- linux.seccomp.syscalls.0.names: Invalid type. Expected: string, given: array
Signed-off-by: W. Trevor King <wking@tremily.us>
Fix a JSON typo which snuck in with eb114f05 (Add ambient and bounding
capability support, 2017-02-02, #675).
Signed-off-by: W. Trevor King <wking@tremily.us>
These are literal quotes, and we don't want Markdown to confuse the
underscores with emphasis delimiters [1].
[1]: http://daringfireball.net/projects/markdown/syntax#em
Signed-off-by: W. Trevor King <wking@tremily.us>
Unwind an overly-aggressive backtick replacement from f9dc90b0 (make
link usage consistent across the specification, 2017-02-09, #687).
Signed-off-by: W. Trevor King <wking@tremily.us>
I expect the lifecycle information was removed accidentally in
be594153 (Split create and start, 2016-04-01, #384), because for a
time it seemed like that PR would also be removing hooks. Putting the
lifecycle information back in, I made some tweaks to adjust to the new
environment, for example:
* Put the pre-start hooks after the 'start' call, but before the meat
of the start call (the container-process exec trigger). Folks who
want a post-create hook can add one with that name. I'd like to
have renamed poststop to post-delete to avoid confusion like [1].
But the motivation for keeping hooks was backwards compatibility [2]
so I've left the name alone.
* Put each "...command is invoked..." lifecycle entry in its own list
entry, to match the 'create' list entry.
* Move the rules about what happens on hook failure into the
lifecycle. This matches pre-split entries like:
If any prestart hook fails, then the container MUST be stopped and
the lifecycle continues at step 7.
and avoids respecifying that information in a second location
(config.md).
* I added the warning section to try and follow post-split's generic
"generates an error" approach while respecting the pre-split desire
to see what failed (we had "then an error including the exit code
and the stderr is returned to the caller" and "then an error is
logged").
* I left the state 'id' context out, since Michael didn't want it [3].
* Make runtime.md references to "generate an error" and "log a
warning" links, so readers have an easier time finding more detail
on that wording.
Where I reference a section, I'm still using the auto-generated anchor
for that header and not the anchors which were added in 41839d7 (Merge
pull request #707 from mrunalp/anchor_tags, 2017-03-03) and similar.
Mrunal suggested that the manually-added anchors were mainly intended
for the validation tooling [4].
[1]: https://github.com/opencontainers/runtime-spec/pull/395
Subject: Run post-stop hooks before the container sandbox is deleted.
[2]: https://github.com/opencontainers/runtime-spec/pull/483#issuecomment-240568422
Subject: *: Remove hooks
[3]: https://github.com/opencontainers/runtime-spec/pull/532#discussion_r99232480
Subject: Restore hook language removed by create/start split
[4]: http://ircbot.wl.linuxfoundation.org/eavesdrop/%23opencontainers/%23opencontainers.2017-03-03.log.html#t2017-03-03T18:02:12
Signed-off-by: W. Trevor King <wking@tremily.us>
Vincent Batts
W. Trevor King
Michael Crosby
Mrunal Patel
zhouhao
Qiang Huang
Daniel, Dao Quang Minh
Tianon Gravi
Ma Shimiao
Xiaochen Shen
Jesse Butler