Getting Started

Installtion

	mkdir -p /opt/sea
	cd /opt/sea/
	git clone https://github.com/atossoftsea/sg-runner.git

	cd /opt/sea/sg-runner
	./sw/install_runner.sh
	./sw/install_oems.sh
	
	# system test
	./sw/test_sit.sh

	# functinal test
	./sw/test_func.sh

Access to the runner is provided via SSH on port 22000, using the sg_exec user and an independent SSHD server. The sg_exec user has no privileges to modify test configurations in the ./store directory. For test development purposes, the sg_dev user should be used.

You can clone the test store from Git and link it to the ./store directory. The RestAPI service is also available. The server can use a minimal server distribution, with CentOS being the preferred option.

This is primarily designed for test scenario development, where the necessary tools are readily available. You can download the SG-Runner_1.0.1.ova image from our repository, then import the .ova file into VirtualBox or VMware.

The virtual machine is based on CentOS (with X Windows) and runs SG-Runner_1.0.1. It also includes Wireshark and Visual Studio Code (VSC) on the server.

You can clone the test store from Git and link it to the ./store directory. Alternatively, you can copy any scenarios you wish to use into the directory.

The sg_exec and sg_dev users are created, with the sg_exec user having privileges limited to executing tests only. The RestAPI service is not available.


  docker login
  docker pull sg-runner:0.1.0
  docker image sg-runner:0.1.0
  
  # optinally 
  cd <store>  # you may clone from sg-test-store or copy scenarios 
  docker image sg-runner:0.1.0 --volume /opt/sea/sg-runner/store:<store>

The Docker image is available on DockerHub. It includes its own SSH server, and the sg_exec user is preconfigured and the RestAPI service is also available.

You can clone the test store from Git and mount your own test store volume at /opt/sea/sg-runner/store.


git clone ... k8s

tf terafform <>.tf 
kubectl cluster init ...
helm update /<k8s>

Basically, you set up a farm of SG-Runners on GCP or AWS. The available Helm chart and Terraform configuration are part of the Orchestrator solution.

Core Concept Configuraiton