OCCNE Automated Initial Configuration

Introduction

Common Services typically refers to the collection of various components deployed to OCCNE. The Common services are major functions in action which are able to perform logging, tracing, and metric collection of the cluster. To Monitor the cluster and to raise alerts when an anomaly occurs or when a potential failure is round the corner. The below procedure are used to install the common services.

Prerequisites

1. All procedures in OCCNE Kubernetes Installer is complete.
2. The host running the docker image must have docker installed. Refer to Install VMs for MySQL Nodes and Management Server for more information.
3. A defined and installed site hosts.ini file should also be present. Check OCCNE Inventory File Preparation for instructions for developing this file.
4. A docker image named 'occne/configure' must be available in the customer repository. OCCNE 1.0 - Installation Procedure

Procedure Steps

Table 3-15 Procedure to install common services

Step #	Procedure	Description
1.	Configure variables	The following variables should be configured according to customer needs, these variables can be modified to point to customer-specific repositories and other configurations needing to be done in the hosts.ini files as documented in the OCCNE Inventory File Template <occne_helm_stable_repo_url> <occne_helm_images_repo>
2.	Run configure image	Run the Configure image using the below command. After "configure:" keyword put the tag of your latest pulled image. $ docker run --rm -v /<PATH_TO_CLUSTER>/<CLUSTER_NAME>:/host <CUSTOMER-PROVIDED_REPOSITORY_LOCATION>/occne/configure:<RELEASE_TAG> Example: $ docker run --rm --network host --cap-add=NET_ADMIN -v /var/occne/rainbow.lab.us.oracle.com/:/host -v /var/occne/:/var/occne:rw -e "OCCNEARGS=--limit host_hp_gen_10[0:7],localhost" 10.75.200.217:5000/configure:1.0.1 Note: Replace the <release_tag> after "configure:" image name with the latest build tag.
3.	Verify the services	After the above command successfully completes, the services deployed and exposed can be verified by using the below command. $ /var/occne/<cluster_name>/artifacts/kubectl.sh get service --namespace=<NAMESPACE_VALUE> or $ /var/occne/<cluster_name>/artifacts/kubectl.sh get service --all-namespaces Example: $ /var/occne/<cluster_name>/artifacts/kubectl.sh get service --all-namespaces $ /var/occne/<cluster_name>/artifacts/kubectl.sh get service --namespace=default $ /var/occne/<cluster_name>/artifacts/kubectl.sh get service --namespace=kube-system $ /var/occne/<cluster_name>/artifacts/kubectl.sh get srvices --namespace=occne-infra
4.	Sample Output	To verify if the above command was executed successfully and whether the services was installed properly, the output shown below can be taken as reference. NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE default kubernetes ClusterIP 10.233.0.1 <none> 443/TCP 20h kube-system coredns ClusterIP 10.233.0.3 <none> 53/UDP,53/TCP,9153/TCP 16h kube-system tiller-deploy ClusterIP 10.233.26.235 <none> 44134/TCP 16h occne-infra occne-elastic-elasticsearch-client ClusterIP 10.233.57.169 <none> 9200/TCP 106s occne-infra occne-elastic-elasticsearch-discovery ClusterIP None <none> 9300/TCP 106s occne-infra occne-elastic-exporter-elasticsearch-exporter ClusterIP 10.233.39.27 <none> 9108/TCP 104s occne-infra occne-grafana LoadBalancer 10.233.31.105 10.75.163.132 80:32257/TCP 90s occne-infra occne-kibana LoadBalancer 10.233.12.112 10.75.163.128 80:30871/TCP 101s occne-infra occne-metrics-server ClusterIP 10.233.50.144 <none> 443/TCP 87s occne-infra occne-prometheus-alertmanager LoadBalancer 10.233.36.86 10.75.163.130 80:31101/TCP 93s occne-infra occne-prometheus-alertmanager-headless ClusterIP None <none> 80/TCP,6783/TCP 93s occne-infra occne-prometheus-kube-state-metrics ClusterIP None <none> 80/TCP 93s occne-infra occne-prometheus-node-exporter ClusterIP 10.233.31.99 <none> 9100/TCP 91s occne-infra occne-prometheus-pushgateway ClusterIP 10.233.49.128 <none> 9091/TCP 93s occne-infra occne-prometheus-server LoadBalancer 10.233.19.225 10.75.163.131 80:31511/TCP 93s occne-infra occne-tracer-jaeger-agent ClusterIP 10.233.45.62 <none> 5775/UDP,6831/UDP,6832/UDP,5778/TCP 99s occne-infra occne-tracer-jaeger-collector ClusterIP 10.233.58.112 <none> 14267/TCP,14268/TCP,9411/TCP 99s occne-infra occne-tracer-jaeger-query LoadBalancer 10.233.43.110 10.75.163.129 80:31319/TCP 99
5.	Remove configuration, if node fails.	If a node fail during configuration deployment, the configuration can be removed using the following: $ docker run --rm --network host --cap-add=NET_ADMIN -v /var/occne/<cluster_name>/:/host -v /var/occne/:/var/occne:rw -e "OCCNEARGS=--limit <host_filter>,localhost --tags remove" <repo>/configure:<tag> Example: $ docker run --rm --network host --cap-add=NET_ADMIN -v /var/occne/rainbow.lab.us.oracle.com/:/host -v /var/occne/:/var/occne:rw -e "OCCNEARGS=--limit host_hp_gen_10[0:7],localhost --tags remove" 10.75.200.217:5000/configure:1.0.1