Adjust nodepool limits for rax providers

Adjust nodepool limits for rax-dfw, rax-iad and rax-ord to reflect
our current reality. Our primary quota constraints there are
maxTotalInstances and maxTotalRAMSize, the latter needing to be
divided by 8192 to get an upper bound on possible node count. Take
whichever is lower in each region, subtract the number of images
configured for it to make room for image update template instances
while running at capacity, and knock off two more for breathing
room.

The drastic reduction in max-servers for rax-iad is due to a recent
and so far unexplained drop in maxTotalRAMSize there, which is being
investigated separately and can be readjusted upward once the cause
is addressed.

Change-Id: Iec601ed87bae9a048525ebcde37deb373b688f4d

modules/openstack_project/templates/nodepool/nodepool.yaml.erb

@@ -124,7 +124,7 @@ providers:
     project-id: '<%= rackspace_project %>'
     auth-url: 'https://identity.api.rackspacecloud.com/v2.0/'
     boot-timeout: 120
-    max-servers: 172
+    max-servers: 184
     rate: 0.001
     images:
       - name: devstack-precise
@@ -178,7 +178,7 @@ providers:
     project-id: '<%= rackspace_project %>'
     auth-url: 'https://identity.api.rackspacecloud.com/v2.0/'
     boot-timeout: 120
-    max-servers: 56
+    max-servers: 55
     rate: 0.001
     images:
       - name: devstack-precise
@@ -225,7 +225,7 @@ providers:
     project-id: '<%= rackspace_project %>'
     auth-url: 'https://identity.api.rackspacecloud.com/v2.0/'
     boot-timeout: 120
-    max-servers: 192
+    max-servers: 85
     rate: 0.001
     images:
       - name: devstack-precise