Switch nodepool launchers to use new zk cluster

This should happen at the same time as we switch the zuul scheduler over
to the new zk cluster and after the nodepool builders have populated
image data on the new zk cluster.

This gets us off the old nodepool.o.o server and onto newer HA cluster.

Change-Id: I9cea03f726d4acb21ad5584f8db7a4d15bc556db

nodepool/nl01.openstack.org.yaml

@@ -2,7 +2,11 @@ elements-dir: /etc/nodepool/elements
 images-dir: /opt/nodepool_dib
 
 zookeeper-servers:
-  - host: nodepool.openstack.org
+  - host: zk01.openstack.org
+    port: 2181
+  - host: zk02.openstack.org
+    port: 2181
+  - host: zk03.openstack.org
     port: 2181
 
 # NOTE(pabelanger): To avoid a race conditions between multiple launchers, only

nodepool/nl02.openstack.org.yaml

@@ -2,7 +2,11 @@ elements-dir: /etc/nodepool/elements
 images-dir: /opt/nodepool_dib
 
 zookeeper-servers:
-  - host: nodepool.openstack.org
+  - host: zk01.openstack.org
+    port: 2181
+  - host: zk02.openstack.org
+    port: 2181
+  - host: zk03.openstack.org
     port: 2181
 
 # NOTE(pabelanger): To avoid a race conditions between multiple launchers, only

nodepool/nl03.openstack.org.yaml

@@ -2,7 +2,11 @@ elements-dir: /etc/nodepool/elements
 images-dir: /opt/nodepool_dib
 
 zookeeper-servers:
-  - host: nodepool.openstack.org
+  - host: zk01.openstack.org
+    port: 2181
+  - host: zk02.openstack.org
+    port: 2181
+  - host: zk03.openstack.org
     port: 2181
 
 # NOTE(pabelanger): To avoid a race conditions between multiple launchers, only

nodepool/nl04.openstack.org.yaml

@@ -2,7 +2,11 @@ elements-dir: /etc/nodepool/elements
 images-dir: /opt/nodepool_dib
 
 zookeeper-servers:
-  - host: nodepool.openstack.org
+  - host: zk01.openstack.org
+    port: 2181
+  - host: zk02.openstack.org
+    port: 2181
+  - host: zk03.openstack.org
     port: 2181
 
 # NOTE(pabelanger): To avoid a race conditions between multiple launchers, only