Added USDF migration coordination directions

doc/operator-guide/schema-migration-process.rst

@@ -93,13 +93,27 @@ Deploy code to populate db at Summit and/or USDF
 
 - When you get your final approval and designated time to perform the changes to ConsDB, announce on #summit-announce, and follow similar steps as test stand procedure above.
 
+USDF Deployment Steps
+---------------------
+
+- Must happen in synchrony with Summit deployment
+
+1. Disable (pause) SUBSCRIPTION at USDF. (in what table)
+2. Perform the migration at the summit with the steps below before step 3.
+3. Connect to the USDF database via psql and perform the alembic migration.
+4. Check or test as agreed upon with the ConsDB team.
+5. Enable and Refresh Subscription at USDF.
+
+If there is no impact or coordination with Summit needed: Run alembic migration at USDF, and test as appropriate.
+
 Summit Deployment Steps
 -----------------------
 
 1. Use a branch in ``phalanx`` to point to the ConsDB tag for deployment.
 2. Set the Argo-CD application ``consdb's`` target revision to your ``phalanx`` branch.
 3. Refresh the ConsDB application and review pod logs.
-4. Have an image taken with the observing team, then verify database entries with a SQL query or Jupyter notebook.
-5. Check your new entries in the database using a jupyter notebook or SQL query in RSP showing your new image has been inserted to the database as expected.
+4. Connect to the summit database via psql and perform the alembic migration.
+5. Have an image taken with the observing team, then verify database entries with a SQL query or Jupyter notebook.
+6. Check your new entries in the database using a jupyter notebook or SQL query in RSP showing your new image has been inserted to the database as expected.
 
 - Once deployment succeeds, set the ``Target Revision`` in Argo-CD back to ``main`` and complete the ``phalanx`` PR for the tested ConsDB tag.