Tutorial: Accessing the ONAP Portal

Access the ONAP portal via the 8989 LoadBalancer @Mandeep Khinda merged in for OOM-633: Provide direct access to ONAP Portal without the need to use VNCClosed and documented at http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_user_guide.html#accessing-the-onap-portal-using-oom-and-a-kubernetes-cluster

------------------------------------------deprecated content below

The ONAP portal is a web application running in the ONAP "cloud" which acts as the user interface to allow you to design, test, certify, and deploy VNF network solutions based on the ONAP platform.

To set up access to the ONAP portal, we'll need to collect IP addresses for four of the nodes in our stack: the portal node, the sdc node, the vid node and the policy node and then add them to our local /etc/hosts file.

In this deprecated 1.0.0 example, we log into our Rackspace account, select "Cloud Servers" from the servers menu.

Open

The resulting list of nodes should resemble this (the nodes of interest are highlighted):

TODO: update for R1 Nov 2017 DCAEGEN2

There is a total of 17 VM's to be able to run the demo (5 including the 3 DCAE cluster are created 15-20 min and up to 35 min after stack creation and named zld*)

Note: the last of the docker containers on the zldciad4vicdap02 container (the 3rd cdap container) - may take an additional 30 min to come up (there should be 5 docker containers up on cdap02) - for a total of 1 hour on rackspace.

1.1 VMs

Open

1.0 VMs

The nodes we're interested in are respectively named vm1-policy at 104.239.249.17, vm1-portal at IP address 104.130.31.25, vm1-sdc at 104.239.249.15 and vm1-vid at 104.130.170.142

Open the /etc/hosts file on your local system and portal docker instance 1610-1, and add lines like the following, but use the addresses you find for your own example stack. Note that these addresses will potentially change each time your base ONAP stack is torn down and restarted.

sudo vi /etc/hosts

or on windows  /windows/system32/drivers/etc/hosts

^{104.239.249.17 policy.api.simpledemo.onap.org
104.130.31.25 portal.api.simpledemo.onap.org
104.239.249.15 sdc.api.simpledemo.onap.org
104.130.170.142 vid.api.simpledemo.onap.org
104.239.249.72 aai.api.simpledemo.onap.org}

(Note that these FQDNs previously used domain openecomp.org.)

NOTE: These names are used internally within the ONAP "cloud" — if you change them, or fail to set them up at all, these tutorials are not going to work.

Open a web browser and browse to the URL

http://portal.api.simpledemo.onap.org:8989/ONAPPORTAL/login.htm

You should then see the ONAP Portal login screen for Amsterdam/R1:

or the 1.0 screen

Log in with the ID demo and the password demo123456! You'll find yourself at the ONAP Portal's main screen:

for SDC login, we have a number of users pre-defined in sdc that can be used to login from the portal into sdc the users use the same password as the demo user:

using these users you can transition from design → testing → approval → distribution

enable AAI - AAI-297: Enable AAI app by default in PortalClosed