[DFSM] Add comment to describe the statuses DEPLOYED and SKIPPED_LIVE_UPDATE returned by compute/login nodes when evaluating a live update.

Signed-off-by: Giacomo Marciani <[email protected]>

Author: gmarciani

cookbooks/aws-parallelcluster-slurm/libraries/dynamo.rb

@@ -16,7 +16,15 @@
 # This is done to understand what is the deployed cluster config in each node, for example, during a CFN Stack update.
 
 DDB_CONFIG_STATUS = {
+  # The node successfully deployed the cluster configuration.
   DEPLOYED: "DEPLOYED",
+
+  # The node evaluated the cluster configuration and concluded that a live update should be skipped because:
+  #   1. not supported: the changeset contains changes that cannot be applied with a live update
+  #                   and may instead require a node replacement.
+  #                   Example: mounting a managed EBS.
+  #   2. not required:  the changeset contains changes that could lead to an empty live update.
+  #                   Example: changing the number of static nodes.
   SKIPPED_LIVE_UPDATE: "SKIPPED_LIVE_UPDATE",
 }.freeze