add hardware and software part for COMAC config Prerequisites

Change-Id: I6cca8e3b60756f2bfbd3b5f4e8d4b126475c376d
diff --git a/prereqs/hardware.md b/prereqs/hardware.md
index cda6fd9..e62efd4 100644
--- a/prereqs/hardware.md
+++ b/prereqs/hardware.md
@@ -97,9 +97,9 @@
                     * SUNSTAR D22799-STCC, EZconn ETP69966-7TB4-I2
 
 * **COMAC Specific Requirements**
-    * **Servers**: Some components of CORD require at least a Intel XEON CPU with Haswell microarchitecture or better.
+    * **Servers**: COMAC requires at least Intel XEON CPU with Haswell microarchitecture or better.
     * **eNodeBs**:
-        * Cavium Octeon Fusion CNF7100 (for more info <kin-yip.liu@cavium.com>)
+        * For this release, we tested a commercial enodeb: Accelleran E1000.
 
 ## BOM Examples
 
diff --git a/profiles/comac/configure/Prerequisites.md b/profiles/comac/configure/Prerequisites.md
new file mode 100644
index 0000000..ca2e729
--- /dev/null
+++ b/profiles/comac/configure/Prerequisites.md
@@ -0,0 +1,45 @@
+# Prerequisites
+
+## Hardware Requirements
+
+Based on the description of "Generic Hardware Guidelines" <https://guide.opencord.org/prereqs/hardware.html#generic-hardware-guidelines>, we are going to introduce the specific requirements for COMAC in this page.
+
+
+* **Compute Machines**: Same as described in "Generic Hardware Guidelines" page. But you want to use multi-cluster COMAC, then you can prepare two same setups. Also, COMAC requires at least Intel XEON CPU with Haswell microarchitecture or better.
+
+* **Network Cards**: For 3GPP data plane, COMAC supports high performance with SR-IOV interfaces. So besides the first 1G NIC for management, COMAC also need another 10G NIC on computer machines for user data traffic.
+
+* **Access Devices**: In COMAC, the access devices here refer to Enodebs. The enodeb for this release we use Accelleran E1000.
+
+The rest of the hardware are same with "Hardware Requirements" section on "Generic Hardware Guidelines" page.
+
+## COMAC BOM Example
+
+One cluster with one OpenFlow switch setup example:  
+![](../images/3nodes-hardware-setup.png)
+
+3x x86 server (10G NIC)  
+1x OpenFlow switch (40G NIC)  
+1x DAC breakout cable     
+5x Ethernet copper cables 
+2x layer 2 switches, one is for management, another is as converter between 1G and 10G NICs  
+
+## Software Requirements
+
+* **Kernel Modules**:  
+  (1) “*nf_conntrack_proto_sctp*” for SCTP protocol;  
+  (2) “*vfio-pci*" for SR-IOV.
+  
+* **Software List**:  
+   Download kubespray, automation-tools, configurations and the helm charts:
+
+  `git clone https://github.com/kubernetes-incubator/kubespray.git -b release-2.11`
+  `git clone https://gerrit.opencord.org/automation-tools`
+  `git clone https://gerrit.opencord.org/pod-configs`
+  `git clone https://gerrit.opencord.org/helm-charts`
+
+
+
+  
+
+
diff --git a/profiles/comac/images/3nodes-hardware-setup.png b/profiles/comac/images/3nodes-hardware-setup.png
new file mode 100644
index 0000000..d82ea54
--- /dev/null
+++ b/profiles/comac/images/3nodes-hardware-setup.png
Binary files differ