-------------------
- * Docker
- * Note: it does NOT have to be the SAME Docker that AAF is deployed on...
- | but it DOES have be accessible to the AAF Instance.
- * For ONAP, this means
-
- * Windriver VPN
- * include "10.12.6.214 aaf-onap-test.osaaf.org" in your /etc/hosts or DNS
+==================
+ * Access to a RUNNING AAF System
+
+ * For ONAP TEST, this means
+
+ * Windriver VPN
+ * include "10.12.6.214 aaf-onap-test.osaaf.org" in your /etc/hosts or DNS
+ * For Writing to Volumes for Docker or K8s
+
+ * Docker
+
+ * Note: it does NOT have to be the SAME Docker that AAF is deployed on...
+
+ * but it DOES have be accessible to the AAF Instance.
+
+ * For creating Configurations on Local Disk
+
+ * For Development purposes
+ * For running AAF on Bare Metal (or VM)
+ * A Truststore that includes your CA
+
+ * for ONAP TEST, you can obtain truststoreONAPall.jks from the `AAF FileServer`_.
+
+ * (You can also get the ONAP TEST Root CA there)
+
+ * the latest aaf-auth-cmd-<VERSION>-full.jar from `ONAP Nexus`_.
+ * you can still use the same "agent.sh" script below
+
+.. _AAF FileServer: http://aaf-onap-test.osaaf.org/-
+.. _ONAP Nexus: https://nexus.onap.org/#nexus-search;quick~aaf-auth-cmd