Hi, In ONAP Amsterdam using OOM, supported ONAP portal is access is through the VNC utility pod. Direct access was introduced in OOM Beijing.
I am sure there are ways to get direct access either by a new approach or by backporting what was done in Beijing. It also depends on what you did to get direct access in Amsterdam using Kubernetes. I think the problem you are facing is that the widget applications loaded by the portal are not being exposed externally or are not reachable by your client that is on the same subnet. That is configured in the portal database for each application. I believe you can view/edit this in the portal GUI under application or widget configuration. There is a URL and port for backend and frontend widgets that also would need to be reachable by your client and not just the main portal front end. The port will need to be a nodePort and in Amsterdam I don’t believe they are because within the VNC pod the internal ports are resolvable. Thanks, Mandeep From: <[email protected]> on behalf of Pavithra R13 <[email protected]> Date: Wednesday, June 13, 2018 at 2:49 AM To: "[email protected]" <[email protected]> Subject: [onap-discuss] ONAP Portal access from outside Hi All, I have installed Kubernetes based ONAP Amsterdam this week on a Ubuntu server. I am able to access the Portal and the SDC/VID/Policy components from the ONAP Ubuntu server. But when I try to access the portal from a different desktop which is in the same subnet of ONAP server , I am able to access only the ONAP portal ,the other components are not accessible . Kindly let me know how to access the portal components from other servers. Note: I have made host entry of the portal apps container and other containers in ONAP server and portal container . I am accessing the portal directly using portal apps container and not through VNC portal. Please find attached screenshot for the portal pods. Regards Pavithra R This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
