Disable apex-editor and pdp-monitoring

Have only nginx process (clamp) running in policy-gui

Issue-ID: POLICY-3650
Signed-off-by: danielhanrahan <daniel.hanrahan@est.tech>
Change-Id: If15d54f83444b845dc23b090cf966afaf1664490
5 files changed
tree: 7af219d182f4faff06a54df779e0a8b7e13ccad4
  1. gui-clamp/
  2. gui-common/
  3. gui-editors/
  4. gui-pdp-monitoring/
  5. packages/
  6. releases/
  7. .gitignore
  8. .gitreview
  9. INFO.yaml
  10. LICENSE.txt
  11. pom.xml
  12. README.md
  13. version.properties
README.md

Summary

Copyright 2017-2018 AT&T Intellectual Property. All rights reserved. Copyright (C) 2021 Nordix Foundation. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE Full license text at https://creativecommons.org/licenses/by/4.0/legalcode

This source repository contains the ONAP Policy GUI code.

To build it using Maven 3, run: mvn clean install -P docker

Docker image

Maven produces a single docker image containing the policy GUIs. These are exposed on the same port (2443) using different URLs:

Building

You can use the following command to build the policy-gui docker image:

mvn clean install -P docker

Deployment

Currently, the policy-gui docker image can be deployed without configuration. For the GUI container to start correctly, the CLAMP backend policy-clamp-backend should be started first.

For local testing, if the CLAMP backend is running on localhost port 8443, the policy-gui docker container can be started with:

docker run -p 2443:2443 --add-host policy-clamp-backend:host-gateway onap/policy-gui

Client Credentials

A certificate must be added in the browser and is required to log in properly:

org.onap.clamp.p12 (from clamp master) (Password: "China in the Spring")

See onap/clamp repo README for details.