Update docs for cluster resource

+ Ensure floating_ip_enabled included
+ Ensure master_lb_enabled included

Change-Id: Idf04b5e0a1be3ef6637a675271174acd6652ae9f

api-ref/source/clusters.inc

@@ -45,6 +45,7 @@ Request
   - fixed_subnet: fixed_subnet
   - fixed_network: fixed_network
   - floating_ip_enabled: floating_ip_enabled_cluster
+  - master_lb_enabled: master_lb_enabled_cluster
 
 .. note::
 
@@ -163,6 +164,8 @@ Response
   - node_addresses: node_addresses
   - status_reason: status_reason
   - create_timeout: create_timeout
+  - floating_ip_enabled: floating_ip_enabled_cluster
+  - master_lb_enabled: master_lb_enabled_cluster
   - name: name
 
 Response Example

api-ref/source/parameters.yaml

@@ -403,6 +403,18 @@ master_lb_enabled:
   in: body
   required: true
   type: boolean
+master_lb_enabled_cluster:
+  description: |
+    Since multiple masters may exist in a bay/cluster, a Neutron load balancer
+    is created to provide the API endpoint for the bay/cluster and to direct
+    requests to the masters. In some cases, such as when the LBaaS service is
+    not available, this option can be set to ``false`` to create a bay/cluster
+    without the load balancer. In this case, one of the masters will serve as
+    the API endpoint. The default is ``true``, i.e. to create the load
+    balancer for the bay.
+  in: body
+  required: false
+  type: boolean
 max_batch_size:
   description: |
     The max batch size each time when doing upgrade, default value is 1