Make platformdoc docker container

Issue-Id: DCAEGEN2-60
Change-Id: Id57ab539707a43883ff957a23d2459a9b12df22e
Signed-off-by: Lusheng Ji <lji@research.att.com>

1 files changed, 163 insertions, 0 deletions

diff --git a/platformdoc/docs/components/component-specification/cdap-specification.md b/platformdoc/docs/components/component-specification/cdap-specification.md
new file mode 100644
index 00000000..479cc944
--- /dev/null
+++ b/platformdoc/docs/components/component-specification/cdap-specification.md
@@ -0,0 +1,163 @@
+# Component specification (CDAP)
+
+## Overview
+
+This page contains details specific to CDAP applications.
+
+The component specification contains the following top-level groups of information:
+
+* Component [Metadata](#metadata)
+* [Parameters](#Parameters): the section for specifying parameters in your AppConfig, AppPreferences, and ProgramPreferences to the Designer and Policy. 
+* [Interfaces](#interfaces): the connections from this component to other components
+* [Auxiliary details](#auxiliary)
+* [List of artifacts](#artifacts)
+
+Note: this page does not talk about [DCAE specific requirements](/components/component-type-cdap.md) that your component must adhere to. Please see that page for discussions about DMaaP, Policy, Metrics, and more.  
+
+## Current Limitations and TODOs
+
+* Currently we only support CDAP applications that have a stream.
+* The integration of DMD is likely to significantly change the [Interfaces](#interfaces) section in this specification, see [DMaaP abstraction](/components/component-type-cdap.md#dmaap-abstraction).
+
+## Metadata
+
+See [Metadata](common-specification.md#metadata)
+
+## Parameters
+
+There is a `parameters` section in your component specification. This section contains three optional keys: [app_config](#appconfig), [app_preferences](#apppreferences), and [propram_preferences](#prorgram_preferences):
+```
+"parameters" : {
+    "app_config" : [ ...],               
+    "app_preferences" : [ ...],          
+    "program_preferences" : [...]
+    // any additional keys are ignored
+}
+```
+
+* Each section details the parameters that are a part of each of these CDAP constructs (see below).
+* All such parameters will be exposed to the designer and to policy for override. 
+* These parameters should have default values specified by the component developer where necessary, i.e., parameters that _must_ come from the designer/policy should not have defaults. 
+* All of these keys are optional because not every CDAP application uses preferences and not every application uses the AppConfig. However, you should specify at least one, or else your application will have no parameters exposed to policy or to the DCAE designer, which means it would be non-configurable. 
+* Despite the AppConfig being optional to *specify* in the case that you have no parameters in your AppConfig, it is *required for processing* in your application. That is because the DCAE platform will place important information into your AppConfig as discussed below. 
+
+### Parameter
+We use the following definition of a _single parameter_, which is used in several places below:
+```
+  {
+      "name" : "param name",
+      "value" : "developer default",
+      "description" : "tell policy/ops what this does"
+   }
+```
+
+### AppConfig
+
+The `app_config` key refers to the [CDAP AppConfig](http://docs.cask.co/cdap/current/en/reference-manual/http-restful-api/configuration.html). It is expected to be a JSON:
+```
+"app_config" : [ // list of JSON
+    param1,      // see Parameter above
+    ...
+]
+```
+Unfortunately, at the time of writing, the AppConfig is a Java map of `string:string`, which means you cannot have more complex structures (than string) as any value in your AppConfig.  However, there is a way to bypass this constraint: you can pass a JSON by encoding the JSON as a string. E.g., the `json.dumps()` and it's converse `loads` methods in Python:
+```
+>>> import json
+>>> json.dumps({"foo" : "bar"})     # This is a real JSON
+'{"foo": "bar"}'                    # It is now a string: pass this in as your parameter value
+>>> json.loads('{"foo": "bar"}')    # Do the equivelent of this in your application
+{u'foo': u'bar'}                    # ...and you'll get back a real JSON 
+>>>
+```
+
+The final AppConfig (after the designer and policy override parameter values) is passed into CDAP's AppConfig API when starting your application. 
+
+### AppPreferences
+
+In addition to the CDAP AppConfig, we support [Application Preferences](http://docs.cask.co/cdap/current/en/reference-manual/http-restful-api/preferences.html#set-preferences). 
+The format of the `app_preferences` value  is the same as the above:
+```
+"app_preferences" : [   // list of JSON
+    param1,             // see Parameter above
+    ...
+]
+```
+
+The final Application Preferences JSON (after the designer and policy override parameter values) is passed into CDAP's Preferences API when starting your application. 
+
+### ProgramPreferences
+
+Preferences can also be specified [per program](http://docs.cask.co/cdap/current/en/reference-manual/http-restful-api/lifecycle.html#program-lifecycle) in CDAP. This key's value is a list of JSON with the following format:
+```
+"program_preferences" : [                // note: this is a list of JSON 
+    {
+      "program_id" :   "program name 1",  // the name of this CDAP program
+      "program_type" : "e.g., flows",     // "must be one of flows, mapreduce, schedules, spark, workflows, workers, or services",
+      "program_pref" : [                  // list of JSON
+          param1,             // see Parameter above
+          ...
+      ]
+    },
+    // repeat for each program you want to pass a preferences JSON to
+]
+```
+Each `program_pref` JSON is passed into the CDAP API as the preference for `program_id`. 
+
+## Interfaces
+See [Interfaces](common-specification.md#interfaces)
+
+NOTE: for CDAP, this section is very likely to change when DMD  is available. 
+The _future_ vision, as per [DMaaP intentionally abstracted](/components/component-type-cdap.md#dmaap-abstraction) is that you would publish your data as a series of files on HDFS, and DMD will pick them up and send them to the appropriate DMaaP feeds or directly when needed. 
+
+## Auxiliary
+
+`auxiliary` contains details about CDAP specific parameters.
+
+Property Name | Type | Description
+------------- | ---- | -----------
+streamname | string | *Required*. 
+artifact_name | string | 
+artifact_version | string | the version of your CDAP JAR artifact
+namespace | string | the CDAP namespace to deploy into, default is 'default'
+programs | array | contains each CDAP entity represented in the artifact
+program_type | string | CDAP entity (eg "flows")
+program_id | string | name of CDAP entity (eg "WhoFlow")
+
+Example:
+
+```json
++"auxiliary": {
+    "streamname" : "who",
+    "artifact_name" : "HelloWorld",
+    "artifact_version" : "3.4.3",
+    "namespace" : "hw",
+    "programs" : [
+                    {"program_type" : "flows", "program_id" : "WhoFlow"}, 
+                    {"program_type" : "services", "program_id" : "Greeting"},
+                    ...
+                  ],
+}
+```
+The `programs` key is identical to the `program_preferences` key discussed [above](#programpreferences) except:
+
+* each JSON in the list does not contain `program_pref`
+* this is required! You must include all of your programs in this, as it is used to start each program as well as for DCAE to perform periodic healthchecks on your application. Don't forget about your services; they are programs too.
+
++
+## Artifacts
+
+`artifacts` contains a list of artifacts associated with this component.  This is where you specify your CDAP jar.
+
+Property Name | Type | Description
+------------- | ---- | -----------
+artifacts | JSON array | Each entry is a artifact object
+
+Each artifact object has:
+
+Property Name | Type | Description
+------------- | ---- | -----------
+uri | string | *Required*. Uri to the artifact
+type | string | *Required*. For CDAP, use `jar`
+
+This file is uploading using the CLI tool at the same time as your component specification. 
+