Merge "Expose max_concurrent_builds as a Heat parameter"

deployment/nova/nova-ironic-container-puppet.yaml

@@ -58,6 +58,14 @@ parameters:
     description: The number of times to retry when a request conflicts. If set to 0, only try once, no retries.
     type: number
     default: -1
+  IronicMaxConcurrentBuilds:
+    description: |
+      The number of builds to process at the same time per each nova-compute instance. If set to 0, it will
+      be set to unlimited (best effort).
+    type: number
+    default: 10
+    constraints:
+      - range: { min: 0 }
 
 conditions:
 
@@ -109,6 +117,7 @@ outputs:
           - nova::compute::force_config_drive: true
             nova::compute::reserved_host_memory: '0'
             nova::compute::vnc_enabled: false
+            nova::compute::ironic::max_concurrent_builds: {get_param: IronicMaxConcurrentBuilds}
             nova::ironic::common::password: {get_param: IronicPassword}
             nova::ironic::common::project_name: 'service'
             nova::ironic::common::auth_url: {get_param: [EndpointMap, KeystoneInternal, uri_no_suffix]}

releasenotes/notes/nova-max_concurrent_builds-f900d84f35704452.yaml

@@ -0,0 +1,6 @@
+---
+features:
+  - |
+    The nova-ironic setting for 'max_concurrent_builds' can now be set via the
+    use of a new TripleO Heat templates parameter 'IronicMaxConcurrentBuilds'.
+    It is set to the service default of 10 by default in TripleO Heat templates.