Hi Michael,
Yes, based on the kubectl status, We have access for the nodeport 30215 to 8989.
root@onap:~/onap/oom/kubernetes# kubectl -n onap get services|grep "portal-app"
portal-app LoadBalancer 10.43.246.615.1.1.7
8989:30215/TCP,8006:30213/TCP,8010:30214/TCP 32m
>>>
Hi Michael,
I was able to setup rancher and onap following your instruction. All the
services looks up & running.
But, when I try to connecting to portal
(http://5.1.1.7:8989/ONAPPORTAL/login.htm). I get No data received :(.
root@onap:~/onap/oom/kubernetes# wget
Hi,
Sounds good
You will need to access the 30215 nodeport to 8989 - this would allow for
example 2 installs on onap on the same cluster using different node ports.
The latest instructions are on - I have not launched portal since it was
switched from the vnc-portal container a month+
Thanks Michael, I will try the script on my setup.
Thanks
Deepak
On Tue, 2018-05-22 at 13:09 +, Michael O'Brien wrote:
> Deepak,
>Hi, yes the rancher install script is agnostic of the undercloud
> (aws, azure, gce, openstack, metal) - it relies on whatever template
> provisioned an
Deepak,
Hi, yes the rancher install script is agnostic of the undercloud (aws,
azure, gce, openstack, metal) - it relies on whatever template provisioned an
Ubuntu 16.04 VM (none in your metal case) - and a post script to setup the NFS
share - the rancher script only sets up docker, helm,
