Add XPilot X-windows game template (#128)

* Add XPilot X-windows game template.  This provides an exmaple of how to use
Rancher to manage an X-Windows client application.

* Xpilot changes to scheduling to compensate for CoreOS/Rancheros linkage issues

* Update Registry template for patched Portus container version, also add affinity rules to avoid networking issues

templates/xpilot/0/docker-compose.yml

@@ -0,0 +1,29 @@
+server:
+  environment:
+    PASSWORD: ${PASSWORD}
+  log_driver: ''
+  command:
+  - -server
+  log_opt: {}
+  tty: false
+  stdin_open: false
+  image: sshipway/xpilot:latest
+  labels:
+    xpilot: server
+client:
+  environment:
+    DISPLAY: ${DISPLAY}
+    NAME: ${NAME}
+    SERVER: xpilot
+  log_driver: ''
+  command:
+  - xpilot
+  log_opt: {}
+  image: sshipway/xpilot:latest
+  links:
+  - server:xpilot
+  tty: false
+  stdin_open: false
+  labels:
+    io.rancher.scheduler.affinity:container_label_soft: xpilot=server
+    io.rancher.container.start_once: 'true'

templates/xpilot/0/rancher-compose.yml

@@ -0,0 +1,29 @@
+.catalog:
+  name: "XPilot"
+  version: "v0.1"
+  description: "Multiplayer shooting game"
+  uuid: xpilot-0
+  questions: 
+    - variable: "PASSWORD"
+      label: "Password"
+      description: "Administration password for the server"
+      default: password
+      required: true
+      type: "password"
+    - variable: "DISPLAY"
+      label: "Display"
+      description: "Enter the identifier for your XWindows display.  This will usually be your workstation name or IP address, followed by :0"
+      default: 1.2.3.4:0
+      required: true
+      type: "string"
+    - variable: "NAME"
+      label: "Player Name"
+      description: "Name for the player's ship.  This must be unique."
+      default: player
+      required: true
+      type: "string"
+server:
+  scale: 1
+client:
+  scale: 1
+