BMC images on N3000 FPGA hardware (pick stx 5.0; stx 6.0)

Updated Patchset 1 comments
After subcloud rehoming, Firmware-update on subcloud went to out-of-sync on destination system controller

Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
Change-Id: I0da685da0b17a14887d3182511af03443554453d

doc/source/dist_cloud/kubernetes/device-image-update-orchestration.rst

@@ -12,7 +12,6 @@ device image updates, including |FPGA| updates.
 .. rubric:: |context|
 
 .. note::
-
     Due to limitations with the existing device image update mechanisms for the
     N3000 |FPGA| hardware, applying more than one image at a time to a given
     hardware device is currently not supported. If multiple device images are
@@ -23,6 +22,12 @@ device image updates, including |FPGA| updates.
     should be used to create and apply a second update strategy for the second
     device image.
 
+.. note::
+    For |BMC| images on N3000 |FPGA| hardware, it is recommended that the
+    admin user uses the **md5sum** of the device image file as the bitstream
+    ID. This will ensure that different files get unique IDs, and the same
+    file gets the same ID.
+
 .. rubric:: |prereq|
 
 

doc/source/node_management/kubernetes/hardware_acceleration_devices/updating-an-intel-n3000-fpga-image.rst

@@ -14,6 +14,12 @@ N3000 |FPGA| user image on a |prod| host.
     |prod| does not support the |FPGA| prestart CRI-O hook. |FPGA|
     programming must be performed manually.
 
+.. note::
+    For |BMC| images on N3000 |FPGA| hardware, it is recommended that the
+    admin user uses the **md5sum** of the device image file as the bitstream
+    ID. This will ensure that different files get unique IDs, and the same
+    file gets the same ID.
+
 .. _updating-an-intel-n3000-fpga-image-section-obd-kky-1mb:
 
 ------------------
@@ -57,8 +63,9 @@ specialized equipment.
 
     `<https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/ug/ug-ias-n3000.pdf>`_
 
-    and particularly Chapter 8, *Configuring Ethernet Interfaces*, to
-    understand how to properly configure the N3000 |NICs|.
+    and particularly Chapter 8, **Node Interfaces**,
+    :ref:`Configuring Ethernet Interfaces <configuring-ethernet-interfaces-using-horizon>`,
+    to understand how to configure the N3000 |NICs|.
 
 -   If you are using your own load, you must have it compiled for the N3000
     |FPGA|.
@@ -109,13 +116,13 @@ specialized equipment.
         this image applies to.
 
     ``<key_signature>``
-        A hexidecimal string identifying the root key device image.
+        A hexadecimal string identifying the root key device image.
 
     ``<revoke_key_id>``
         A decimal key ID for the key revocation device image.
 
     ``<bitstream_id>``
-        A hexidecimal string of the functional device image.
+        A hexadecimal string of the functional device image.
 
     ``<name>``
         The name of the device image \(optional\).

doc/source/node_management/kubernetes/hardware_acceleration_devices/uploading-a-device-image.rst

@@ -11,6 +11,12 @@ Upload a Device Image
 The device image must exist where the system command is executed, such as a
 remote CLI, before proceeding.
 
+.. note::
+    For |BMC| images on N3000 |FPGA| hardware, it is recommended that the
+    admin user uses the **md5sum** of the device image file as the bitstream
+    ID. This will ensure that different files get unique IDs, and the same
+    file gets the same ID.
+
 .. rubric:: |proc|
 
 -   Upload the device image.
@@ -48,13 +54,13 @@ remote CLI, before proceeding.
         this image applies to.
 
     **<key\_signature>**
-        A hexidecimal string identifying the root key device image.
+        A hexadecimal string identifying the root key device image.
 
     **<revoke\_key\_id>**
         A decimal key ID for the key revocation device image.
 
     **<bitstream\_id>**
-        A hexidecimal string of the functional device image.
+        A hexadecimal string of the functional device image.
 
     **<name>**
         The name of the device image \(optional\).