Bump nodepoolv3 max-server to 10

To avoid wedging nodepool-launcher (feature/zuulv3) we need to ensure
we have more max-servers then our largest nodeset size. Right now,
that is 5.

Change-Id: I955c76045d0e8f2039028430345975aef6d0906f
Signed-off-by: Paul Belanger <pabelanger@redhat.com>

nodepool/nl01.openstack.org.yaml

@@ -261,7 +261,7 @@ providers:
         config-drive: true
     pools:
       - name: main
-        max-servers: 5
+        max-servers: 10
         labels:
           - name: centos-7
             min-ram: 8000

nodepool/nl02.openstack.org.yaml

@@ -45,7 +45,7 @@ providers:
         config-drive: true
     pools:
       - name: main
-        max-servers: 5
+        max-servers: 10
         labels:
           - name: centos-7
             min-ram: 8000
@@ -207,7 +207,7 @@ providers:
         config-drive: true
     pools:
       - name: main
-        max-servers: 5
+        max-servers: 10
         labels:
           - name: centos-7
             min-ram: 8000

nodepool/nodepool.yaml

@@ -807,7 +807,7 @@ providers:
     cloud: citycloud
     api-timeout: 60
     boot-timeout: 120
-    max-servers: 45
+    max-servers: 40
     rate: 0.25
     image-type: 'qcow2'
     template-hostname: '{image.name}-{timestamp}'
@@ -923,7 +923,7 @@ providers:
     cloud: citycloud
     api-timeout: 60
     boot-timeout: 120
-    max-servers: 45
+    max-servers: 40
     rate: 0.25
     image-type: 'qcow2'
     template-hostname: '{image.name}-{timestamp}'