This file references helm chart packages from outside of this repo:
* stx-openstack-helm
* stx-monitor-helm
These packages used to be in this repo (under kubernetes/) but have
since been moved to independent repos:
* starlingx/openstack-armada-app
* starlingx/monitor-armada-app
TESTS
=========================
Build packages, then run build-helm-charts.sh and make sure
"stx-openstack-helm" & "stx-monitor-helm" tarballs are generated.
Story: 2010226
Task: 46421
Depends-On: https://review.opendev.org/c/starlingx/openstack-armada-app/+/859326
Depends-On: https://review.opendev.org/c/starlingx/monitor-armada-app/+/859329
Signed-off-by: Davlet Panech <davlet.panech@windriver.com>
Change-Id: I674969f147e48658c7e7f2b36db109e73adc480c
Introduce a new Armada manifest (stx-monitor) that defines the
necessary software components and services to deploy a
monitoring solution for the infrastructure and Kubernetes cluster
as well as the services it is running.
The Elastic 7.x Apache 2.0 Licensed ("oss") images are included.
The following Elastic components are introduced in this commit:
elasticsearch, filebeat, metricbeat, logstash, kibana.
This enables the build of the stx-monitor application manifest
and upon application, the capturing of logs and metrics
into elasticsearch. The logs and metrics may then be viewed with a
tool such as Kibana.
The stx-monitor application is built:
build-pkgs monitor-helm
build-pkgs stx-monitor-helm
build-helm-charts.sh --app stx-monitor
The settings for elasticsearch helm chart are set to allow mtce actions,
such as host-lock, of a controller.
The following host labels are required on controllers prior
to the application-apply:
system host-label-list controller-0
(and, in duplex, for controller-1)
| controller-0 | elastic-controller | enabled |
| controller-0 | elastic-data | enabled |
| controller-0 | elastic-client | enabled |
Tests:
build-helm-charts.sh --app stx-monitor
system application-upload
system application-apply
host management: host-lock, host-swact, host-unlock
Determine the port for kibana:
kubectl get service -n monitor
Access kibana via <oamip>:<service port>
verify logs and container logs are captured, include subdirs
under /var/log such as /var/log/openvswitch
system application-remove
system application-delete
Change-Id: I0e2f94d302b3ec3a22ee5853d529efb6b423bdaa
Depends-On: Ic9a5b909dfbf60e39f98f3f14fe9bbac2de1d42b
Story: 2005733
Task: 31081
Co-Authored-By: Kevin Smith <kevin.smith@windriver.com>
Signed-off-by: John Kung <john.kung@windriver.com>
This target should only be built as part of the containers build
environment which requries network access and does not need to be done
as part of the standard build.
Change-Id: I0e4df72614fceb084c8a60be403b833c013d71f2
Story: 2004005
Task: 27934
Signed-off-by: Robert Church <robert.church@windriver.com>
Davlet Panech