| Jerry Flood | 775f59f | 2017-04-01 06:55:19 -0400 | [diff] [blame] | 1 | <html><head> |
| 2 | <title>Quicklinks To Running Instances</title> |
| 3 | </head> |
| 4 | |
| 5 | <body> |
| 6 | <h1>The Portal</h1> |
| 7 | |
| 8 | The portal is the entry point to design/provision/operate ONAP. From there you can get to SDC, VID and Policy portals. |
| 9 | |
| 10 | The portal can be found at:<p> |
| 11 | |
| 12 | <a href="http://portal.api.simpledemo.openecomp.org:8989/ECOMPPORTAL/login.htm">Portal</a> |
| 13 | <p> |
| 14 | One requires role based user names and passwords to receive the full portal functionality. In the demo setup we pre provisioned: |
| 15 | <p> |
| 16 | <ul> |
| 17 | <li> jh0003 Admin </li> |
| 18 | <li> cs0008 Designer </li> |
| 19 | <li> jm0007 Tester </li> |
| 20 | <li> op0001 Operator </li> |
| 21 | <li> gv0001 Governance </li> |
| 22 | <li> pm0001 Product Manager </li> |
| 23 | <li> ps0001 Product Strategy </li> |
| 24 | </ul> |
| 25 | <p> |
| 26 | the password for all of them is: demo123456! |
| 27 | |
| 28 | <h1> The Reality </h1> |
| 29 | |
| 30 | As everything should go through the portal there are many subsystems which have there own GUI or API which come in very handy when debugging things. Here the most important once. |
| 31 | |
| 32 | <h2> Testing </h2> |
| 33 | |
| 34 | <b> Not working. </b> : |
| 35 | |
| 36 | <a href="http://${robot}:88/report.html"> Test Report </a> |
| 37 | |
| 38 | <h2> SDN-C </h2> |
| 39 | |
| 40 | <a href="http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@${sdnc}:8282/apidoc/explorer/index.html"> Controller </a> with admin/Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U <p> |
| 41 | |
| 42 | <a href="http://${sdnc}:8843/signup"> To sign up </a> <p> |
| 43 | <a href="http://${sdnc}:8843/login"> Admin </a> <p> |
| 44 | |
| 45 | <h2> App-C </h2> |
| 46 | |
| 47 | <a href="http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@${appc}:8282/apidoc/explorer/index.html"> Controller </a> with admin/Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U <p> |
| 48 | |
| 49 | <h2> Policy </h2> |
| 50 | |
| 51 | <b> Not working. </b> : |
| 52 | <a href="http://healthcheck:zb!XztG34@${policy}:6969/healthcheck"> Healthcheck </a> <p> |
| 53 | |
| 54 | <h2> MSO </h2> |
| 55 | |
| 56 | <a href="http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@${mso}:9990/"> JBOSS GUI </a> with admin/Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U <p> |
| 57 | |
| 58 | <a href="http://${mso}:8080/camunda"> Camunda GUI </a> with admin/Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U <p> |
| 59 | |
| 60 | <h2> DCAE </h2> |
| 61 | |
| 62 | <h3> General GUIs </h3> |
| 63 | <a href="http://console:ZjJkYjllMjljMTI2M2Iz@${dcae_controller}:9998/resources"> DCAE Controller </a> |
| 64 | This might show up empty in a web browser as no content type is set in the response. If that's the case use curl: <p> |
| 65 | |
| 66 | curl http://console:ZjJkYjllMjljMTI2M2Iz@${dcae_controller}:9998/resources <p> |
| 67 | |
| 68 | <a href="http://${dcae_cdap}:9999/ns/TCA/apps/dcae-tca/programs/flows/TCAVESCollectorFlow/runs"> CDAP GUI </a> <p> |
| 69 | |
| 70 | <h3> DCAE internal Message Router </h3> |
| 71 | |
| 72 | <a href="http://${dcae_coll}:3904/topics"> Topics </a> <p> |
| 73 | |
| 74 | <a href="http://${dcae_coll}:3904/events/unauthenticated.SEC_MEASUREMENT_OUTPUT/monitor/0?timeout=10000"> MR topic for collector to TCA </a> <p> |
| 75 | |
| 76 | <a href="http://${dcae_coll}:3904/events/unauthenticated.TCA_EVENT_OUTPUT/monitor/0?timeout=10000"> MR topic for TCA alert to Policy </a> <p> |
| 77 | |
| 78 | <h2> Message Router used between core components </h2> |
| 79 | |
| 80 | <a href="http://${message_router}:3904/topics"> List of Topics </a> <p> |
| 81 | |
| 82 | <h3> Topics of Interest </h3> |
| 83 | |
| 84 | For topics without authentication one can monitor the traffic on a topic with: <p> |
| 85 | |
| 86 | http://${message_router}:3904/events/PUT_TOPIC_HERE/group1/C1?timeout=5000 <p> |
| 87 | |
| 88 | some important once listed below. <p> |
| 89 | |
| 90 | <ul> |
| 91 | <li> <a href="http://${message_router}:3904/events/APPC-CL/monitor/0?timeout=10000"> APPC-CL Topic -- Policy Publishes Requests and APP-C publishes response </a> |
| 92 | <li> <a href="http://${message_router}:3904/events/PDPP-CONFIGURATION/monitor/0?timeout=10000"> PDPD-CONFIGURATION Topic </a> |
| 93 | <li> <a href="http://${message_router}:3904/events/POLICY-CL-MGT/monitor/0?timeout=10000"> POLICY-CL-MGT Topic -- Control loop operational policy </a> |
| 94 | <li> <a href="http://${message_router}:3904/events/DCAE-CL-EVENT/monitor/0?timeout=10000"> DCAE-CL-EVENT Topic -- Provides the Analytics output from DCAE</a> |
| 95 | |
| 96 | </ul> |
| 97 | |
| 98 | <h1> SSH to VM </h1> |
| 99 | |
| 100 | The following links will open a shell and ssh to the various running VMs (at least on a Mac). It assumes that the .ssh/config file has been set appropriately and /etc/hosts has been updated to the running instance.<p> |
| 101 | |
| 102 | <a href="ssh://${aai}"> AAI </a><p> |
| 103 | <a href="ssh://${policy}"> Policy </a><p> |
| 104 | <a href="ssh://${sdc}"> SDC </a><p> |
| 105 | <a href="ssh://${portal}"> Portal </a><p> |
| 106 | <a href="ssh://${dcae_controller}"> DCAE </a><p> |
| 107 | <a href="ssh://${appc}"> APP-C </a><p> |
| 108 | <a href="ssh://${mso}"> MSO </a><p> |
| 109 | <a href="ssh://${sdnc}"> SDN-C </a><p> |
| 110 | <a href="ssh://${vid}"> VID </a><p> |
| 111 | <a href="ssh://${message_router}"> Message Router </a><p> |
| 112 | <a href="ssh://${robot}"> Robot Framework for testing </a><p> |
| 113 | <a href="ssh://${onapdns}"> DNS server for management network </a><p> |
| 114 | |
| 115 | Inside the VM you can list the docker containers by typing: <p> |
| 116 | docker ps <p> |
| 117 | and can get a shell prompt by executing the bash command. |
| 118 | For example: <p> docker exec -it openecompete_container bash <p> |
| 119 | |
| 120 | |
| 121 | |
| 122 | |
| 123 | </body></html> |