[TC_02] NebulOuS core installation

[Ferran Diego Andilla]

Objective

Test that the NebulOuS core installation process can be executed.

Preconditions

A server with NebulOuS core minimal requirements is available.

User has necessary permissions to install new software on the server.

The user has access to NebulOuS core binaries (from public repository and compiled by himself).

User has an open terminal in the server.

Steps

sudo apt update && sudo apt upgrade -y
sudo apt install curl apt-transport-https -y

curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
chmod +x kubectl
sudo mv kubectl /usr/local/bin/

sudo apt install docker.io -y
sudo systemctl start docker
sudo systemctl enable docker
sudo usermod -aG docker $USER && newgrp docker

curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64
sudo install minikube-linux-amd64 /usr/local/bin/minikube
minikube start --memory=5g --driver=docker

# download nebulous in host machine https://drive.google.com/file/d/1zTcFHzqHkflvebHE9es04wA4aL0H45pG/view?usp=drive_link
# and run
sftp nebulous
put nebulous-flux-cd-main.zip

# Back to the nebulous machine

unzip nebulous-flux-cd-main.zip

curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3
chmod 700 get_helm.sh
./get_helm.sh

curl -s https://fluxcd.io/install.sh | sudo bash
. <(flux completion bash)

flux install

Modify every file in software/nebulous/helm-releases to include:

spec:
 interval: 5m

kubectl apply -k nebulous-flux-cd-main/software/nebulous/.

User executes the NebulOuS core installation process as described in NebulOuS documentation.

Expected results

NebulOuS core is correctly installed.

All its core components (X, Y, Z, K) are up and running.

Result
- There is no public repository for nebulous with a release. The helm files are not production ready and the nebulous-flux-cd-main/software/nebulous/kustomization.yaml doesn't define the tags for the version of the components.
- sal component is not starting
- This setup doesn't include the service and the ingress to access the GUI

NAME READY STATUS
sal-5c9d5cdb67-snwcx 0/1 Init:0/1

Doesn't pass