added chef ci config

Author: gouravjshah

cs-ansible/docker-compose.yml

@@ -19,7 +19,8 @@ services:
   node1:
     image: codespaces/ansible-node-centos-6:v0.3.6
     ports:
-       - "80:80"
+       - "8081:8080"
+       - "81:80"
     networks:
       - custom
     domainname: codespaces.io
@@ -28,7 +29,8 @@ services:
   node2:
     image: codespaces/ansible-node-centos-6:v0.3.6
     ports:
-       - "81:8080"
+       - "8082:8080"
+       - "82:80"
     networks:
       - custom
     domainname: codespaces.io
@@ -37,7 +39,8 @@ services:
   node3:
     image: codespaces/ansible-node-centos-6:v0.3.6
     ports:
-      - "82:8080"
+      - "8083:8080"
+      - "83:80"
     networks:
       - custom
     domainname: codespaces.io
@@ -46,9 +49,11 @@ services:
   node4:
     image: codespaces/ansible-node-centos-6:v0.3.6
     ports:
-      - "83:8080"
+      - "8084:8080"
+      - "80:80"
     networks:
       - custom
     domainname: codespaces.io
     hostname: node4
     restart: always
+

cs-chef-ci/README.md

@@ -0,0 +1,6 @@
+### Why does Chef Codespace needs to be configured with host networking ?
+
+If you plan to use docker along with testkitchen for TDD, it requires to provision a container, 
+connect to it, run chef and then run the tests. This will not work without attaching to the hosts's 
+network and without getting rid of network namespace for the control node. 
+

cs-chef-ci/docker-compose.yml

@@ -0,0 +1,74 @@
+version: '2'
+
+networks:
+  chef:
+    driver: bridge
+    ipam:
+      driver: default
+      config: 
+        - subnet: 172.0.101.0/24
+
+services:
+  ws:
+    image: codespaces/chef-ws:v0.1.4
+    ports:
+      - "8000:8000"
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock
+    network_mode: host
+#    networks:
+#      - chef
+    container_name: ws
+    domainname: codespaces.io
+    hostname: ws
+    restart: always
+
+  node1:
+    image: codespaces/chef-node-centos-6:v0.1.2
+    ports:
+       - "8081:8080"
+    networks:
+      chef:
+        ipv4_address: 172.0.101.10
+    container_name: node1
+    domainname: codespaces.io
+    hostname: node1
+    restart: always
+
+  node2:
+    image: codespaces/chef-node-centos-6:v0.1.2
+    ports:
+       - "8082:8080"
+    networks:
+      chef:
+        ipv4_address: 172.0.101.11
+    container_name: node2
+    domainname: codespaces.io
+    hostname: node2
+    restart: always
+
+  node3:
+    image: codespaces/chef-node-centos-6:v0.1.2
+    ports:
+      - "8083:8080"
+      - "83:80"
+    networks:
+      chef:
+        ipv4_address: 172.0.101.12
+    container_name: node3
+    domainname: codespaces.io
+    hostname: node3
+    restart: always
+
+  node4:
+    image: codespaces/chef-node-centos-6:v0.1.2
+    ports:
+      - "8084:8080"
+      - "80:80"
+    networks:
+      chef:
+        ipv4_address: 172.0.101.13
+    container_name: node4
+    domainname: codespaces.io
+    hostname: node4
+    restart: always

cs-chef/docker-compose.yml

@@ -27,7 +27,7 @@ services:
   node1:
     image: codespaces/chef-node-centos-6:v0.1.2
     ports:
-       - "83:80"
+       - "81:8080"
     networks:
       chef:
         ipv4_address: 172.0.101.10
@@ -39,7 +39,7 @@ services:
   node2:
     image: codespaces/chef-node-centos-6:v0.1.2
     ports:
-       - "81:80"
+       - "82:8080"
     networks:
       chef:
         ipv4_address: 172.0.101.11
@@ -51,7 +51,7 @@ services:
   node3:
     image: codespaces/chef-node-centos-6:v0.1.2
     ports:
-      - "82:80"
+      - "80:80"
     networks:
       chef:
         ipv4_address: 172.0.101.12
@@ -63,7 +63,7 @@ services:
   node4:
     image: codespaces/chef-node-centos-6:v0.1.2
     ports:
-      - "3306:3306"
+      - "84:8080"
     networks:
       chef:
         ipv4_address: 172.0.101.13