Changes between Initial Version and Version 1 of windowsContainers

Timestamp:

Sep 10, 2015 9:24:42 AM (9 years ago)

Author:

Geoff Lawler

Comment:

--

windowsContainers

@@ +1 @@
+This is a page that explains how to use Chef to bring up Windows on DETER.
+
+**NOTE: work in progress - do not actually do this yet.**
+
+----------
+
+- checkout the containers source tree
+- switch to the configdb branch
+- swap in an experiment with physical nodes loaded with the PNODE-BASE image.
+- ssh to a pnode
+- cd {{{[path to containers]/bin}}}
+- run {{{./chef_configure.sh}}}
+- edit the file /tmp/nodes.conf, which describes the nodes you want to spawn. The file format is below.
+- run {{{./spawn_windows.sh}}} and wait a long time (like 5 minutes per container).
+
+nodes.conf format and description:
+{{{
+nodes:
+      - name: nodeOne
+        image_name: deter/win7
+        url: http://scratch/benito/deter_win7.box
+        data_address: 10.1.1.100
+        data_bridge: eth4
+
+      - name: nodeTwo
+        image_name: deter/win7
+        url: http://scratch/benito/deter_win7.box
+        data_address: 10.1.1.101
+        data_bridge: eth4
+
+...
+
+}}}
+
+nodes.conf description:
+- {{{name}}}: the hostname of the new node
+- {{{image_name}}}: the Vagrant name - this should be unique per image (*not* host, image)
+- {{{url}}}: the URL to the container image
+- {{{data_address}}}: the ip address of the container. Should really be in same subnet as host
+- {{{data_bridge}}} - the interface to bridge the data address to from the container to the host.
+- {{{control_addr}}} - [optional and experimental] the ip address for the container on the control network (172.16.x.x)
+- {{{control_bridge}}} - [optional and experimental] - the host interface to bridge to the container's control address.
+
+If you add an address you must add a bridge.
+
+