docs(framework): Update cloud deployment guides for HTTP Control API

framework/docs/source/how-to-run-flower-on-azure.rst

@@ -88,9 +88,9 @@ VM Networking
 During the execution of the Flower application, the server VM (``SuperLink``) will be
 responsible to orchestrate the execution of the application across the client VMs
 (``SuperNode``). When the SuperLink server starts, by default, it listens to the
-following ports: ``{9092, 9093}``. Port `9092` is used to communicate with the
-Federation clients (``SuperNode``) and port ``9093`` to receive and execute Flower
-applications.
+following ports: ``{8000, 9092}``. Port ``9092`` is used to communicate with the
+federation clients (``SuperNode``), and port ``8000`` serves the HTTP Control API used
+to submit and execute Flower applications.
 
 Therefore, to enable this communication we need to allow inbound traffic to the server
 VM instance. To achieve this, we need to navigate to the Networking page of the server
@@ -117,9 +117,9 @@ The rest of the fields can be left at their default values.
     - - **Protocol**
       - ``TCP``
 
-Finally, we need to also open port 9093 to allow receiving and executing incoming
+Finally, we need to also open port 8000 to allow receiving and executing incoming
 application requests. To enable this we just need to repeat the steps above, i.e.,
-create a new inbound rule, where for port range we assign port 9093. If we already know
+create a new inbound rule, where for port range we assign port 8000. If we already know
 the Public IP from which our local machine (e.g., laptop) will be submitting
 applications to the Azure cluster, then we just need to specify the Source IP
 address/CIDR range. However, if we want to keep the port widely open we simply need to
@@ -136,7 +136,7 @@ changes:
     - - **Source IP addresses/CIDR ranges**
       - add machine's Public IP
     - - **Destination port ranges**
-      - ``9093``
+      - ``8000``
 
 Otherwise, we change the properties as follows:
 
@@ -148,7 +148,7 @@ Otherwise, we change the properties as follows:
     - - **Source**
       - ``Any``
     - - **Destination port ranges**
-      - ``9093``
+      - ``8000``
 
 ********************
  Flower Environment
@@ -183,7 +183,7 @@ and then at each client (``SuperNode``).
 .. code-block:: bash
 
     # Server VM (SuperLink)
-    flower-superlink --insecure
+    flower-superlink --insecure --host="0.0.0.0"
 
     # Client-1 VM (SuperNode-1)
     flower-supernode \
@@ -231,7 +231,7 @@ Next, we need to create a new SuperLink connection in the Flower Configuration f
        :caption: config.toml
 
        [superlink.my-federation]
-       address = "SUPERLINK_PUBLIC_IP:9093"  # Address of the SuperLink Control API
+       address = "SUPERLINK_PUBLIC_IP:8000"  # Address of the SuperLink Control API
        insecure = true
 
 Then from our local machine we need to run ``flwr run . my-federation``.

framework/docs/source/how-to-run-flower-on-gcp.rst

@@ -335,12 +335,13 @@ provide the definition of the six ``yaml`` files that are necessary to deploy th
                 image: flwr/superlink:|stable_flwr_version|
                 args:
                   - "--insecure"
+                  - "--host"
+                  - "0.0.0.0"
                   - "--isolation"
                   - "process"
                 ports:  # which ports to expose/available
-                - containerPort: 9091
                 - containerPort: 9092
-                - containerPort: 9093
+                - containerPort: 8000
         ---
         apiVersion: v1
         kind: Service
@@ -350,18 +351,14 @@ provide the definition of the six ``yaml`` files that are necessary to deploy th
           selector:
             app: superlink
           ports:  # like a dynamic IP routing table/mapping that routes traffic to the designated ports
-          - protocol: TCP
-            port: 9091   # Port for ServerApp connection
-            targetPort: 9091  # the SuperLink container port
-            name: superlink-serverappioapi
           - protocol: TCP
             port: 9092   # Port for SuperNode connection
             targetPort: 9092  # the SuperLink container port
             name: superlink-fleetapi
           - protocol: TCP
-            port: 9093   # Port for Flower app submission
-            targetPort: 9093  # the SuperLink container port
-            name: superlink-controlapi
+            port: 8000   # Port for Control and Runtime API connections over HTTP
+            targetPort: 8000  # the SuperLink container port
+            name: superlink-http-api
           type: LoadBalancer  # balances workload, makes the service publicly available
 
 .. dropdown:: supernode-1-deployment.yaml
@@ -483,7 +480,7 @@ provide the definition of the six ``yaml`` files that are necessary to deploy th
                 args:
                   - "--insecure"
                   - "--runtime-api-address"
-                  - "superlink-service:9091"
+                  - "superlink-service:8000"
                   - "--plugin-type"
                   - "serverapp"
 
@@ -629,7 +626,7 @@ Flower Configuration file:
        :caption: config.toml
 
        [superlink.gcp-deployment]
-       address = "<EXTERNAL_IP>:9093" # replace the EXTERNAL_IP with the correct value
+       address = "<EXTERNAL_IP>:8000" # replace the EXTERNAL_IP with the correct value
        insecure = true
 
 Then we can execute the example on the GCP cluster by running:

framework/docs/source/how-to-run-flower-on-red-hat-openshift.rst

@@ -239,10 +239,12 @@ tutorial on :doc:`how to deploy Flower in GCP <how-to-run-flower-on-gcp>`.
                   image: flwr/superlink:|stable_flwr_version|
                   args:
                     - "--insecure"
+                    - "--host"
+                    - "0.0.0.0"
                   ports: # which ports to expose/available
                     - containerPort: 9092
                       name: fleet
-                    - containerPort: 9093
+                    - containerPort: 8000
                       name: control
                   volumeMounts:
                     - name: cache-volume
@@ -289,7 +291,7 @@ pod and insert the following YAML definition:
             targetPort: fleet  # the SuperLink container port
             name: superlink-fleetapi
           - protocol: TCP
-            port: 9093   # Port for Flower app submission
+            port: 8000   # Port for Flower app submission over HTTP
             targetPort: control  # the SuperLink container port
             name: superlink-controlapi
           type: LoadBalancer  # balances workload, makes the service publicly available
@@ -683,7 +685,7 @@ connection in the Flower Configuration file:
        :caption: config.toml
 
        [superlink.remote]
-       address = "superlink-service:9093"  # use the service name created earlier
+       address = "superlink-service:8000"  # use the service name created earlier
        insecure = true
 
 And finally, run your Flower app as usual with ``flwr run``: