From 87c3c18efb2beaa36f5f4d429d69371e4ff48f27 Mon Sep 17 00:00:00 2001 From: Martin Skorupski Date: Sun, 5 Feb 2023 19:42:24 +0100 Subject: [PATCH] Add a FlowManagement Component - housekeeping on README.md. IssueID: OAM-308 Change-Id: Iba58e1fd7159ede181d626eefe5e6e0f948bc051 Signed-off-by: Martin Skorupski --- solution/README.md | 26 +++++++------------------- 1 file changed, 7 insertions(+), 19 deletions(-) diff --git a/solution/README.md b/solution/README.md index 1dcbbcd..1bd4e4b 100644 --- a/solution/README.md +++ b/solution/README.md @@ -20,18 +20,16 @@ with the following components. ... representing an KeyCloak based identity service for centralized user management. Please note that the implementation does not support IPv6. Therefore, its own network is required called 'DMZ'. - In this configuration the external https port is 8463. * **Controller** single node instance ... representing the NETCONF consumer on the Service Management and Orchestration framework (SMO) for the O1 interface based on ODL. - SDN-R comes with is own web-portal the external port is 8463. * **VES collector** - ... representing the VES (REST) provider at SMO for all kind of events. In this configuration the external https port is 8443. + ... representing the VES (REST) provider at SMO for all kind of events. * **Messages** ... representing SMO MessageRouter component, includes message-router @@ -206,12 +204,6 @@ nano smo/oam/.env nano network/.env ``` -The tested configuration uses the following external https ports: - - * 8443 for the ves-collector - * 8453 for web access to ODLUX (SDNC_WEB_PORT) - * 8463 for the keyclock web administrator user interface. - #### Startup solution Please note that it is necessary to configure first the identity service, @@ -235,16 +227,10 @@ docker-compose -f smo/oam/docker-compose.yml up -d Looking into the ONAP SDN-R logs will give you the startup procedure. ``` -docker logs -f sdnr -``` - -The startup was successful when you see the following line: - -``` -Everything OK in Certificate Installation +docker logs -f controller ``` -If you see the login page (https://sdnc-web:8453) you are good to go and can start the (simulated) network. +If you see the login page (https://odlux.oam.smo.o-ran-sc.org) you are good to go and can start the (simulated) network. ``` docker-compose -f network/docker-compose.yml up -d @@ -278,7 +264,7 @@ Finally the fault events are visible in ODLUX. #### ODL karaf.logs ``` -docker exec -it sdnr tail -f /opt/opendaylight/data/log/karaf.log +docker exec -it controller tail -f /opt/opendaylight/data/log/karaf.log ``` #### ves-collector logs @@ -297,7 +283,7 @@ docker logs -f ves-collector ##### Login into SDN-R - https://sdnc-web:8453 + https://odlux.oam.smo.o-ran-sc.org User: admin // see .env file @@ -311,6 +297,7 @@ To stop all container please respect the following order ``` docker-compose -f network/docker-compose.yml down +docker-compose -f smo/apps/docker-compose.yml down docker-compose -f smo/oam/docker-compose.yml down docker-compose -f smo/common/docker-compose.yml down ``` @@ -332,3 +319,4 @@ The commands ... ``` docker ps -a docker-compose ps +docker rm -f $(docker ps -aq) -- 2.16.6