From 6a5b1449aeb3753cb974cd69fc043267a8db21b9 Mon Sep 17 00:00:00 2001 From: Mrunal Patel Date: Wed, 10 Aug 2016 12:20:39 -0700 Subject: [PATCH 1/2] Add language for compliance requirements around platforms and architectures Signed-off-by: Mrunal Patel --- README.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 132859709..0a6b2d6e3 100644 --- a/README.md +++ b/README.md @@ -24,8 +24,13 @@ Table of Contents In the specifications in the above table of contents, the keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in [RFC 2119](http://tools.ietf.org/html/rfc2119) (Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997). -An implementation is not compliant if it fails to satisfy one or more of the MUST or REQUIRED requirements for the protocols it implements. -An implementation that satisfies all the MUST or REQUIRED and all the SHOULD requirements for its protocols is said to be "unconditionally compliant". +An implementation is not compliant for a given CPU architecture if it fails to satisfy one or more of the MUST or REQUIRED requirements for the protocols it implements. +An implementation is compliant for a given CPU architecture if it satisfies all the MUST and REQUIRED requirements for the protocols it implements. +An implementation that satisfies all the MUST or REQUIRED and all the SHOULD requirements for its protocols on a given CPU architecture is said to be "unconditionally compliant" with those protocols and architectures. + +Protocols defined by this specification are: +* Linux containers: [runtime.md](runtime.md), [config.md](config.md), [config-linux.md](config-linux.md), and [runtime-linux.md](runtime-linux.md). +* Solaris containers: [runtime.md](runtime.md), [config.md](config.md), and [config-solaris.md](config-solaris.md). # Use Cases From de3f1af680fcdffcc6c7aec5a4ed1729b79bd1cb Mon Sep 17 00:00:00 2001 From: Mrunal Patel Date: Wed, 17 Aug 2016 10:58:21 -0700 Subject: [PATCH 2/2] Remove language around Solaris being optional as it is covered in compliance language Signed-off-by: Mrunal Patel --- config-solaris.md | 1 - 1 file changed, 1 deletion(-) diff --git a/config-solaris.md b/config-solaris.md index 063112533..afa97d7e0 100644 --- a/config-solaris.md +++ b/config-solaris.md @@ -1,7 +1,6 @@ # Solaris Application Container Configuration Solaris application containers can be configured using the following properties, all of the below properties have mappings to properties specified under zonecfg(1M) man page, except milestone. -The Solaris specification is entirely optional. ## milestone The SMF(Service Management Facility) FMRI which should go to "online" state before we start the desired process within the container.