Copyright (C) 2023 Nordix Foundation. All rights reserved. Copyright (C) 2023 OpenInfra Foundation Europe. All rights reserved. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
The ranpm setup works on linux/MacOS or on windows via WSL using a local or remote kubernetes cluster.
It is recommended to run the ranpm on a kubernetes cluster instead of local docker-desktop etc as the setup requires a fair amount of computer resources.
The demo set can be run on local or remote kubernetes. Kubectl must be configured to point to the applicable kubernetes instance. Nodeports exposed by the kubernetes instance must be accessible by the local machine - basically the kubernetes control plane IP needs to be accessible from the local machine.
The following images need to be built manually. If remote or multi node cluster is used, then an image repo needs to be available to push the built images to. If external repo is used, use the same repo for all built images and configure the reponame in helm/global-values.yaml. The parameter value of extimagerepo shall have a trailing /.
Build the following images (build instruction in each dir)
The installation is made by a few scripts. The main part of the ranpm is installed by a single script. Then, additional parts can be added on top. All installations in kubernetes is made by helm charts.
The following scripts are provided for installing (install-nrt.sh mush be installed first):
There is a corresponding uninstall script for each install script. However, it is enough to just run uninstall-nrt.sh and `uninstall-pm-rapp.sh´.
All exposed APIs on individual port numbers (nodeports) on the address of the kubernetes control plane.
Keycloak API accessed via proxy (proxy is needed to make keycloak issue token with the internal address of keycloak).
Server for posting updated OPA rules.
Direct access to ICS API. -nodeports (http and https): 31823, 31824
Direct access to the Ves-Collector
As part of the ranpm installation, a number of admin tools are installed. The tools are accessed via a browser on individual port numbers (nodeports) on the address of the kubernetes control plane.
Admin tool for keycloak.
With this tool the topics, consumer etc can be viewed.
Browser for minio filestore.
Browser for influx db.
Browser for control-panel
browser: <host ip>:30091/ei-coordinator