summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorMandeep Khinda <Mandeep.Khinda@amdocs.com>2018-08-29 22:11:16 +0000
committerGerrit Code Review <gerrit@onap.org>2018-08-29 22:11:16 +0000
commitb9d3a955ecf11a76d9e3ae3ce528bc4816dac674 (patch)
treead545424c6d2428ff4e8b237e3888a5aca1d78a0 /docs
parent46d5a428bd65625d130e2474c3c9c1b910abaf12 (diff)
parent55547da51f4efa73d617ffaa15badc50c65cc6d3 (diff)
Merge "Add note for Portal GUI access"
Diffstat (limited to 'docs')
-rw-r--r--docs/oom_user_guide.rst30
1 files changed, 21 insertions, 9 deletions
diff --git a/docs/oom_user_guide.rst b/docs/oom_user_guide.rst
index ad1f89e6a9..f20097d927 100644
--- a/docs/oom_user_guide.rst
+++ b/docs/oom_user_guide.rst
@@ -391,16 +391,28 @@ Ensure you've disabled any proxy settings the browser you are using to access
the portal and then simply access the familiar URL:
http://portal.api.simpledemo.onap.org:8989/ONAPPORTAL/login.htm
-.. note:: Alternatives Considered.
- Kubernetes port forwarding was considered but discarded as it would require
- the end user to run a script that opens up port forwarding tunnels to each of
- the pods that provides a portal application widget.
+.. note::
- Reverting to a VNC server similar to what was deployed in the Amsterdam
- release was also considered but there were many issues with resolution, lack
- of volume mount, /etc/hosts dynamic update, file upload that were a tall order
- to solve in time for the Beijing release.
+ | Alternatives Considered:
+
+ - Kubernetes port forwarding was considered but discarded as it would require
+ the end user to run a script that opens up port forwarding tunnels to each of
+ the pods that provides a portal application widget.
+
+ - Reverting to a VNC server similar to what was deployed in the Amsterdam
+ release was also considered but there were many issues with resolution, lack
+ of volume mount, /etc/hosts dynamic update, file upload that were a tall order
+ to solve in time for the Beijing release.
+
+ Observations:
+
+ - If you are not using floating IPs in your Kubernetes deployment and directly attaching
+ a public IP address (i.e. by using your public provider network) to your K8S Node
+ VMs' network interface, then the output of 'kubectl -n onap get services | grep "portal-app"'
+ will show your public IP instead of the private network's IP. Therefore,
+ you can grab this public IP directly (as compared to trying to find the floating
+ IP first) and map this IP in /etc/hosts.
.. figure:: oomLogoV2-Monitor.png
:align: right
@@ -675,4 +687,4 @@ deployment enter::
will remove `so` as the configuration indicates it's no longer part of the
deployment. This might be useful if a one wanted to replace just `so` by
-installing a custom version.
+installing a custom version.