Access the ONAP portal via the 8989 LoadBalancer Mandeep Khinda merged in for  OOM-633 - Getting issue details... STATUS  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.



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

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

(Please note this URL was updated for R1 about 19 Oct 2017; previously it was http://portal.api.simpledemo.openecomp.org:8989/ECOMPPORTAL/login.htm )

use cs0008:demo123456!

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:

UserRole
jh0003ADMIN
cs0008DESIGNER
jm0007TESTER
gv0001GOVERNOR
op0001OPS

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

enable AAI -  AAI-297 - Getting issue details... STATUS





  • No labels

58 Comments

  1. Kite Bo

    how to add application of SDC with portal?

    such as :

    1. which user and password?
    2. which url and rest api url?

    thanks.

    1. Daniel Rose

      FYI, the mailing list is probably a better place to ask questions as more people watch it. Anyway, if you are a portal admin you can see on the left hand side application onboarding links and widget onboarding links. Those can be used to set up a widget or application and has all the details in there.

  2. Manoop Talasila

    Try to login as superuser (demo/demo123456!) and see if applications like VID, SDC and Policy appear in the Portal (assuming that you correctly configured your /etc/hosts file, as described in the wiki).


    If you don’t see any applications in the Portal's home page, then it could be that the users.sql script did not get executed during deployment. 


    If so, try to run:

    mysql -u root -p'Aa123456' -h $IP_ADDRESS < /opt/portal/deliveries/Apps_Users_OnBoarding_Script.sql


    where IP_ADDRESS is the public IP address of the Portal VM.


    Then, try to login again as cs0008 and you should be able to access SDC.

    1. Bharath Thiruveedula

      Thanks Manoop!


      This command helped me to access SDC.

      1. Andreas Geissler

        Hi,

        we faced the same Problem. Reason was that our default Security Group for VMs did not allow any Ingress traffic. During the installation of the Portal VM the mysql command tries to "remotely" connect to the Portal, which fails.

        I would suggest, either to mention this in the installation procedure or (better) to create proper Security Groups in the HEAT template.

        Regards

        Andreas

        1. Daniel Rose

          Marco Platania i dont think we can assume in the vanilla openstack that a security group exists UCA-9 - Getting issue details... STATUS

          1. Marco Platania

            Default security group is assumed, with basic HTTP/SSH services available. We don't go beyond that because the security groups depend on specific implementations and security requirements.

    2. Manoop Talasila

      If you see below error while executing the SQL, please follow below suggestion.

      Error: ERROR 1062 (23000) at line 3: Duplicate entry '2' for key 'PRIMARY'

      Suggestion: It seems like by the time the SQL script is executed, some one might have created a new user using the Portal's GUI. The sql is expected to be executed while deployment, so such a scenario would not happen. 

      I recommend removing the new user from the fn_user table (mostly it is with ID = 2) and then execute the sql script. I hope this helps resolve above error.


      1. Eli Williams

        Hi Manoop Talasila,


        I am receiving this error, but I definitely didn't create any new users with the GUI. I deleted the row with user_id=2 but I still get the same error when executing. Should I just drop the whole fn_user table?


        Thanks,

        Eli

        1. Manoop Talasila

          Hi,

          You do not need to drop the table. Can you please check what do you see in fn_app and fn_user table? You should just see 1 record in each table: "Default" app in fn_app table and "demo" user in fn_user table. If you see, any other records, you can remove them and execute the above mentioned on-boarding script.

          I hope this helps.


          Regards,

          Manoop

          1. Eli Williams

            Hi Manoop Talasila,


            Thanks so much for your quick reply. I did the above and I got another duplicate entry error ('1-999-2'). Would you suggest I just clear all the databases from mysql? I would stand up the stack again but doing so is rather tedious with proxy stuff. Really appreciate your help with this.


            Thanks,

            Eli

            1. Manoop Talasila

              Hi,

              Seems like a role is also added for a new user. Please remove the record 1-999-2 from fn_user_role. 

              It is good idea to discuss these at onap-discuss mailing list, so others can benefit from the Q&As.

              Manoop

              1. Eli Williams

                Hi Manoop Talasila,

                I ended up having to delete the whole fn_user_role table; I was then plagued with errors in the fn_role table (which I also deleted). I still cannot get the .sql file to execute without some primary or foreign key constraint. What are the implications of dropping the entire portal database? Thanks!

                1. Manoop Talasila

                  Hi,

                  Please see, if you can opt one of this option.

                  Option1: If possible, I recommend to rebuild just the Portal VM again. The deployment heat template script should provide details on what is done to build the Portal VM.

                  Option 2: I would drop the "portal" schema and recreate it using below files in that order. (assuming you are using master branch)

                  1. EcompPortalDDLMySql_1707_Common.sql
                  2. EcompPortalDDLMySql_1707_OS.sql
                  3. EcompPortalDMLMySql_1707_Common.sql
                  4. EcompPortalDMLMySql_1707_OS.sql
                  5. Apps_Users_OnBoarding_Script.sql


                  Regards,

                  Manoop

  3. Andreas Geissler

    Hi,

    since a couple of days I face the problem with the portal after redeploying ONAP on Openstack.

    It seems the DB Container cannot be connected from the Portal Application (See Container Log):

    08:54:19,157 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@765d1c6d - Registering current configuration as safe fallback point
    java.sql.SQLException: Connections could not be acquired from the underlying database!
        at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:118)

    The DB container Log does not show any problems.
    Result is that the Portal returns a HTTP 500..

    Any hints ?


    1. Shaheen Ali

      Did you try:


      mysql -u root -p'Aa123456' -h $IP_ADDRESS < /opt/portal/deliveries/Apps_Users_OnBoarding_Script.sql


      I have never seen the portal ecompdb container come up cleanly.  I always need to run the above.


      BTW, I run the latest heat template out of the demo repo.  My openstack is Newton.

    2. Manoop Talasila

      What are the containers you see when you run "docker ps -a" on portal's vm?

  4. Andreas Geissler

    I can see both containers in the Portal VM. locally I am also able to access the Database.

    But what I found out is, that the DNS VM does not resolve the hostnames of the VMs, which lead to the problem, that the Portal Application is not able to contact the DB, as it is using the portal FQDN.

    Last login: Tue May 16 10:53:10 2017 from 10.34.54.181
    ubuntu@vm1-portal:~$ nslookup -query=mx portal.api.simpledemo.openecomp.org
    ;; Got recursion not available from 10.0.100.1, trying next server
    Server:        8.8.8.8
    Address:    8.8.8.8#53
    ** server can't find portal.api.simpledemo.openecomp.org: NXDOMAIN

    This could this be caused by the named.option:

           recursion no;                 # enables recursive queries

    After changing it to yes, the resolution worked.
    But I don't know if that is has been changed for some reason ?





    1. Manoop Talasila

      Marco Platania any idea about this "recursion no;" setting?

      1. Marco Platania

        "recursion yes" doesn't work for all OpenStack installations. We had issues in our lab. We are investigating this issue

  5. Josef Reisinger

    I asked for a change of the recursion setting here: UCA-13 - Getting issue details... STATUS

    Btw, let me at this point advertise https://jira.onap.org and Questions https://wiki.onap.org/questions as repositories for questions and change requests/issues. (smile)

  6. You Li

    I use the 1.0.0 heat templete to build ONAP in openstack.  Stack creation and the portal_vm_init.sh ran successfully. However, when I try to login with the ID demo and the password demo123456!,it always  report invalid username or password in the portal webpage.

    I tried the command "mysql -u root -p'Aa123456' -h $IP_ADDRESS < /opt/portal/deliveries/Apps_Users_OnBoarding_Script.sql",  and use "mysql -u root -p'Aa123456' -h $IP_ADDRESS" to connect to db from portal docker, all the users and password are in the table fn_user now.

    I also try the "recursion yes", all the domain name can be convert to ip address now, but the login web page still report invalid username or password.

    Please kindly help me and provide some advices to solve this problem, thanks.

    1. You Li

      I check the error log

      there is a error like 

      2017-07-20T07:49:27.564Z||http-nio-8080-exec-3|||ECOMP_PORTAL_BE|findUser|org.openecomp.portalapp.portal.logging.logic.EPLogUtil|CRITICAL|ERR505E|Performing DDL or DML operations on database might have failed| Please check MySQL DB health or look at the logs for more details.
      2017-07-20T07:49:27.585Z||http-nio-8080-exec-3|||ECOMP_PORTAL_BE|findUser|org.openecomp.portalapp.portal.service.EPLoginServiceImpl|||| Exception occurred while executing findUser operation. Details: org.hibernate.hql.internal.ast.QuerySyntaxException: $clazz0$ is not mapped from $clazz0$ where login_id = 'demo' and login_pwd = '95LidzVz7nSpsTsRUrDNVA=='

      Caused by: org.hibernate.hql.internal.ast.QuerySyntaxException: $clazz0$ is not mapped
      at org.hibernate.hql.internal.ast.util.SessionFactoryHelper.requireClassPersister(SessionFactoryHelper.java:189)


      I guess this is the key reason that the query is not performed, any suggestion to solve the problem?


      1. Marco Platania

        Manoop Talasila and Portal team... any clue about this?

        1. Manoop Talasila

          We never faced this issue in any environment so far for 1.0.0 version. I will check with my team and will update soon, if have any suggestions.

        2. Michael O'Brien

          You, hi, I just refreshed a stack with 1.0.0 on the 18th July and was able to do the full closed loop on the vFW - check that you are not running any 1.1 tags

          https://s3.amazonaws.com/onap/20170718_rackspace_iad_vFirewall_closed_loop_demo_3.mov

          artifacts_version = 1.0.0, docker_version = 1.0-STAGING-latest, gerrit_branch=1.0.0

          /michael

          1. You Li

            Thanks, Michael. I have solved this problem, it is caused by the poor performance of my openstack, which can not download and extract the portal sdk correctly, then the EPUser can not be mapping to fn_user. I change another openstack environment and the portal works now.

  7. Brian Freeman

    In 1.0.0 environment I find that every once in a while I need to docker stop both the portal and mariadb, then docker start mariadb and then docker start portal. Seems to fix the loss of connectivity to something.

  8. SOUMYA PATTANAYAK

    I pulled out the portal code to my local windows machine from gerrit, build and deploy the portal component to my local tomcat following the steps mentioned in wiki. I am using local maria db and configured a admin user ( demo/demo). I could able to login and see the home page. Now when I click on any widget, i;e SDC, it opens up a tab saying "sdc.openecomp.org's server DNS address could not be found". Click on policy widget takes me to error page saying "policy.openecomp.org's server DNS address could not be found". I am new to ONAP. Need your guidance how to fix this ? Am i missing any installation/configuration ??

  9. Olga S

    Did you add in /etc/hosts the IPs for policy.api.simpledemo.openecomp.org and sdc.api.simpledemo.openecomp.org?

    1. SOUMYA PATTANAYAK

      Yes, I did for all 4 entries into my \etc\hosts

      104.239.249.17 policy.api.simpledemo.openecomp.org
      104.130.31.25 portal.api.simpledemo.openecomp.org
      104.239.249.15 sdc.api.simpledemo.openecomp.org
      104.130.170.142 vid.api.simpledemo.openecomp.org

      Still same issue.

  10. Leimeng Shi

    @Soumya Pattnayak, the widget you clicked suppose to partner application (SDC or Policy) that on-boarded in Portal with landing URL point to "...openecomp.org".  Let me follow up with SDC, Policy support and check their wiki for answer.

  11. Leimeng Shi

    the latest IPs should be:

    172.99.115.185 policy.api.simpledemo.openecomp.org

    172.99.119.26 portal.api.simpledemo.openecomp.org

    172.99.115.170 sdc.api.simpledemo.openecomp.org

    23.253.119.165 vid.api.simpledemo.openecomp.org

    1. SOUMYA PATTANAYAK

      Thanks for updating. Still the same error. As I am running the portal from my local windows machine, do I need to change any path of widgets in any configuration file ??

      1. Manoop Talasila

        Hi Soumya, 

        As you are testing in local. I assume you have installed just Portal platform. To access policy or SDC, you also need to install them in your local. As these application are de-coupled from Portal runtime and they are supposed to run in their own servers. Once they are running in your local, then the hosts file can be mapped with your local IP for these apps too.

        I hope this answers your question.

        1. SOUMYA PATTANAYAK

          Thanks Manoop. Yes, right now I have only portal installed in my local tomcat with local maria.

          How to install these widgets like policy and SDC locally ? Can you refer me to any instructions ? ( not demo instruction)

          I did see a ecomp-portal-widget-ms folder inside portal in gerrit. which packaged to a spring boot app. Is this app related to this ??

          thanks in advance !!

          1. Manoop Talasila

            SOUMYA PATTANAYAK, I do not remember having such instructions in ONAP wiki. So far, I heard developers successfully installing the entire ONAP environment in cloud space. I am not sure, if anyone succeeded in windows local. 


            Marco Platania or Daniel Rose, did we have any instructions somewhere in wiki to deploy/install individual components in local windows environment?

            1. Marco Platania

              ONAP on Vagrant is the only way to install ONAP locally that I'm aware of. All the templates we have work in OpenStack-based environments (public or private).

          2. Michael O'Brien

            Soumya, you will need to install either local VM's using ONAP on Vagrant as Marco suggests - Victor Morales's project

            or

            Run ONAP on Kubernetes (runs everything except DCAE for now ) - you will need 37G ram - runs on bare-metal and openstack VM's - I think I will try an AWS VM next - A D2.2xlarge with 61G ram on the spot market https://console.aws.amazon.com/ec2sp/v1/spot/launch-wizard?region=us-east-1 at $0.16/hour for all of ONAP

            /michael

  12. Michael O'Brien

    Launching ONAP 1.1 (master 20170804 tag) fails with a 500 when hibernate attempts to contact the mariadb container it is wrapping.

    obrienbiometrics:onap michaelobrien$ ssh root@portal -o StrictHostKeyChecking=no 

    root@06c0071911cf:/opt/apache-tomcat-8.0.37/webapps# cat /opt/apache-tomcat-8.0.37/logs/localhost.2017-08-07.log

    07-Aug-2017 01:47:19.878 SEVERE [http-nio-8080-exec-3] org.apache.catalina.core.StandardWrapperValve.invoke Allocate exception for servlet dispatcher

     java.net.ConnectException: Connection refused (Connection refused)

    at java.net.PlainSocketImpl.socketConnect(Native Method)

    fix is to start mariadb and restart tomcat

    PORTAL-62 - Getting issue details... STATUS

    root@vm1-portal:~# docker ps -a

    CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                    PORTS                                                                    NAMES

    d4968a92403b        widget-ms           "sh -c 'java $JAVA..."   34 hours ago        Up 34 hours               0.0.0.0:8082->8082/tcp                                                   ecomp-portal-widget-ms

    06c0071911cf        ep:1610-1           "/configure-and-ru..."   34 hours ago        Up 34 hours               0.0.0.0:8006->8005/tcp, 0.0.0.0:8010->8009/tcp, 0.0.0.0:8989->8080/tcp   onap_portal

    9c143d60a356        ecompdb:portal      "docker-entrypoint..."   34 hours ago        Exited (1) 34 hours ago                                                                            ecompdb_portal

    305de51fd1e1        mariadb             "docker-entrypoint..."   34 hours ago        Created                                                                                            data_vol_portal



    docker start ecompdb_portal

    docker restart onap_portal 


    root@vm1-portal:~# docker ps -a

    CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                                                    NAMES

    d4968a92403b        widget-ms           "sh -c 'java $JAVA..."   34 hours ago        Up 34 hours         0.0.0.0:8082->8082/tcp                                                   ecomp-portal-widget-ms

    06c0071911cf        ep:1610-1           "/configure-and-ru..."   34 hours ago        Up 10 minutes       0.0.0.0:8006->8005/tcp, 0.0.0.0:8010->8009/tcp, 0.0.0.0:8989->8080/tcp   onap_portal

    9c143d60a356        ecompdb:portal      "docker-entrypoint..."   34 hours ago        Up 12 minutes                                                                                ecompdb_portal

    305de51fd1e1        mariadb             "docker-entrypoint..."   34 hours ago        Created 

  13. SOUMYA PATTANAYAK

    can someone please help with the latest IPs of portal, sdc, vid, policy nodes ??

    rgds,

    Soumya

    1. Manoop Talasila

      Marco Platania, please see, if you can provide the latest IPs?

      1. Marco Platania

        Currently, there's no ONAP lab up and running due to migration to a new OpenStack environment

        1. SOUMYA PATTANAYAK

          thanks for the update Marco Platania and Manoop Talasila..

          Manoop Talasila - There is a component named ecomp-portal-widget-ms inside /onap/portal. I did able to build the project and could able to run the spring-boot app for mS. Is there any documentation I can refer, where I could get information reagrding, how should I connect my local portal components with these local mS widgets ?? Just trying everything to run on my machine locally portal + wodget code..Not sure if I'm doing right..

          T&R//


  14. Chris Lott

    Please note this revised URL of the Portal start page for Amsterdam/R1. As documented above, accessing this from a browser on your local machine still requires your local machine to have an appropriate /etc/hosts entry so the name can be resolved:

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

    1. Michael O'Brien

      Chris, thanks for the updates, we see the same in OOM

      /michael

  15. Andreas Geissler

    Is there any way of changing the FQDNs (...api.simpledemo.onap.org) of the components providing UIs ?
    As we instantiate multiple ONAP instances it always requires to change the client's /etc/host to change from one instance to another.

    Andreas  

  16. William Kurkian

    Using the kubernetes setup of ONAP, I have gained access to the Portal login page. 

    However, after I login I get a blank page and an error on the web server:

    2018-05-01T20:23:24.114Z||http-nio-8080-exec-2|||||org.onap.portalapp.portal.interceptor.SessionTimeoutInterceptor|||| preHandle failed
    org.onap.portalsdk.core.exception.SessionExpiredException: Your session has expired. Please login again.


    However, this happens every time I login. I took a look at the code, and found it was failing on getting "licenseVerification" from the servlet context. Does anyone have any insight into this ?


    Thanks,

    William

  17. Balázs Németh

    Hey all,

    I am a PhD student at Budapest University of Technology and Economics and I work on orchestration logics. I would like to try out the ONAP demos, but I failed to access the portal through web (http://portal.api.simpledemo.onap.org:8989/ONAPPORTAL/login.htm). My /etc/hosts file is configured correctly I can ping and initiate ssh connection to the portal, but it is not accessible through web.

    Could you help me resolve the issue? Is the ONAP portal in operation now?

    Thanks and Best regards,

    Balázs 

    1. Manoop Talasila

      Can you please let us know, how is it deployed? Is it based on HEAT or OOM deployment? 

      I would first try to see if the dockers area up and running (using "docker ps -a").

      Next I would check the logs of the dockers. If everything still looks good then map the IP of portal application in your local machines hosts file where you would use the browser to access Portal's login URL.

      1. Balázs Németh

        Hm, I might have misunderstood something... I thought this ONAP Portal is a publicly available (through the given public IP addresses and URLs) ONAP deployment for demonstration purposes. I didn't make any ONAP deplyoment myself. Do I need to deploy ONAP on my own infrastructure for experimenting? Is it possible to deploy only the SO and/or HAS for examining the orchestration algorithms and interfaces?

        1. Manoop Talasila

          That is right, the ONAP Portal is not deployed as a public instance.

          However, if you are a code contributor to any sub-project, then you can request for a test lab environment to test your code. Then the test environment IP addresses can be used.

          For experimenting, you need to deploy your own ONAP instance. To access SO, you need at least ONAP Portal and SO components. May be refer to - http://onap.readthedocs.io/en/latest/guides/onap-developer/settingup/index.html 

          1. Balázs Németh

            Thanks very much for your replies!

            I am specifically interested in the ONAP projects' orchestrator logics, and I am trying to experiment regarding this. So I am not aiming at a full scale deployment (if possible), but more specifically the components which implements optimization logic, such as HAS and/or SNIRO.

            Is it possible that I can deploy/emulate them on their own such as described here: SNIRO Emulator (it seems heavily work in progress) or Homing and Allocation Service (HAS) (no deployment information is given)?

            What is the relation between HAS and SNIRO? I found how does SNIRO connects to SO, but I am not sure about HAS. Their functionality seems very similar.

            All your comments and guidance is appreciated!

            Balázs

  18. Van Hung Nguyen

    Dear all,

    When I get the floating IP address that corresponds to the private IP as follows: 

           kubectl -n onap get services|grep "portal-app" 

    I got the result:  No resource found.

    Then, I try with another command below:

        kubectl get services|grep portal-app

    and got the result with external IP is Pending

       portal-app                 LoadBalancer   10.110.238.176   <pending>                                 8989:30215/TCP,8006:30213/TCP,8010:30214/TCP                                 1d

    Could you please help me to explain why I got the above results?

  19. THIRILOSHINI KRISHNAKUMAR

    Van Hung Nguyen Were you able to resolve the issue that you have mentioned ? I am facing the same issue in Onap Dublin. 

    ubuntu@onap-rancher-vm-1804:~$ kubectl get services -n onap | grep portal-app
    portal-app LoadBalancer 10.43.113.184 <pending> 8989:30215/TCP,8006:30213/TCP,8010:30214/TCP,8443:30225/TCP 21h

  20. Xuan-Thuy Dang

    Hi all,

    this is how I got access to portal in Onap Dublin.

    Check the installation

    kubectl -n onap describe services portal-app 
Name: portal-app
Namespace: onap
Labels: app=portal-app
chart=portal-app-4.0.0
heritage=Tiller
release=development-portal
Annotations: msb.onap.org/service-info:
[ { "serviceName": "portal", "version": "v2", "url": "/", "protocol": "REST" "port": "8989", "visualRange":"1" } ]
Selector: app=portal-app,release=development-portal
Type: LoadBalancer
IP: 10.96.175.211
Port: portal-app 8989/TCP
TargetPort: 8080/TCP
NodePort: portal-app 30215/TCP
Endpoints: 10.244.4.64:8080
Port: portal-app2 8006/TCP
TargetPort: 8005/TCP
NodePort: portal-app2 30213/TCP
Endpoints: 10.244.4.64:8005
Port: portal-app3 8010/TCP
TargetPort: 8009/TCP
NodePort: portal-app3 30214/TCP
Endpoints: 10.244.4.64:8009
Port: portal-app4 8443/TCP
TargetPort: 8443/TCP
NodePort: portal-app4 30225/TCP       <--------- NodePort to access with nodeIP
Endpoints: 10.244.4.64:8443
Session Affinity: None
External Traffic Policy: Cluster
Events: <none>

    Add local host entry in /etc/hosts

    # nodeIP, master, worker	
192.168.181.52 portal.api.simpledemo.onap.org <-------- portal hostname, may be required for access control
192.168.181.52 vid.api.simpledemo.onap.org
192.168.181.52 sdc.api.fe.simpledemo.onap.org
192.168.181.52 sdc.workflow.plugin.simpledemo.onap.org
192.168.181.52 sdc.dcae.plugin.simpledemo.onap.org
192.168.181.52 portal-sdk.simpledemo.onap.org
192.168.181.52 policy.api.simpledemo.onap.org
192.168.181.52 aai.api.sparky.simpledemo.onap.org
192.168.181.52 cli.api.simpledemo.onap.org
192.168.181.52 msb.api.discovery.simpledemo.onap.org
192.168.181.52 msb.api.simpledemo.onap.org
192.168.181.52 clamp.api.simpledemo.onap.org
192.168.181.52 so.api.simpledemo.onap.org

    Access portal

    The URL is: 

    https://portal.api.simpledemo.onap.org:30225/ONAPPORTAL/login.htm

    user:password as above:

    cs0008:demo123456!

    Cheers!

  21. Guhan Eswaran

    Hi All,

    ONAP has been set up and can see all the dev-portal pods up. 

    dev-portal-portal-app-65f8797d65-w457c 2/2 Running
    dev-portal-portal-cassandra-84cf7cfffc-2k6n2 1/1 Running
    dev-portal-portal-db-5b77fd9746-x8n2n 1/1 Running
    dev-portal-portal-db-config-8c87j 0/2 Completed
    dev-portal-portal-sdk-67bfdc687-rwwl6 2/2 Running
    dev-portal-portal-widget-fc5c8bdc-fxgpw 1/1 Running
    dev-portal-portal-zookeeper-77ddfcdf8f-qghng 1/1 Running


    While accessing the Portal UI with demo user, log-in is successful but with below message. Also, not able to see any of the components in UI

    "You do not have access to any application or function in ONAP"


    Thanks,

    Guhan

  22. haoling Hu

    In the tutorial vFW Service Design Tutorial — onap master documentation

    In step F & G ,when I connected the Generic NeutronNet & vFW_demo together and wanted to set the options,  I found the different from the tutorial.

    here is the tutorial, it shows the capability.

    but in my work it shows the requirement and I could not change it.