libvirt-coreos cluster: Fix etcd versions incompatibility issue

Whereas CoreOS is still shipped with etcd 0.4.9, kubernetes has moved to etcd 2.0.4.

This version mismatch makes kubernetes unable to use etcd.
Kubernetes’ logs are full of “502:  (unhandled http status [Temporary Redirect] with body []) [0]”

This change makes libvirt-coreos cluster explicitly use etcd v2.0.9 instead of the one shipped within CoreOS.
This change aims at being reverted once CoreOS will migrate to etcd 2.
This migration is tracked at:
https://github.com/coreos/bugs/issues/317

cluster/libvirt-coreos/user_data.yml

@@ -17,11 +17,22 @@ coreos:
   etcd:
     name: ${name}
     addr: ${public_ip}:4001
-    bind-addr: 0.0.0.0
+    # bind-addr: 0.0.0.0
     peer-addr: ${public_ip}:7001
     # peers: {etcd_peers}
     discovery: ${discovery}
   units:
+    - name: etcd.service
+      drop-ins:
+        - name: opt-etcd2.conf
+          content: |
+            [Unit]
+            After=opt-etcd.mount
+            Requires=opt-etcd.mount
+
+            [Service]
+            ExecStart=
+            ExecStart=/opt/etcd/bin/etcd
     - name: static.network
       command: start
       content: |
@@ -103,6 +114,17 @@ coreos:
         Where=/opt/kubernetes
         Options=ro,trans=virtio,version=9p2000.L
         Type=9p
+    - name: opt-etcd.mount
+      command: start
+      content: |
+        [Unit]
+        ConditionVirtualization=|vm
+
+        [Mount]
+        What=etcd
+        Where=/opt/etcd
+        Options=ro,trans=virtio,version=9p2000.L
+        Type=9p
   update:
     group: ${COREOS_CHANNEL:-alpha}
     reboot-strategy: off