Closed marissaeinhorn closed 2 years ago
All provided materials should be copied to the home directory of the host VM prior to attempting installation
ht-docker-images.tar.gz
- A tar archive of all the needed Docker images. This Also includes the binary application scenarioControl
scenarioControl
- An application that enables the web controller interface for High TideHigh Tide
project - Found at https://git.mgmt/blue-edge/high-tide/core.git. The configuration files and scripts needed to install and run High TideHigh Tide Installation
project - Found at https://git.mgmt/blue-edge/high-tide/core.git. Some extra configuration files and helpful scripts to improve the installation process for High TideFiles are located on Ducknet I:\Development\VATER\HighTide
High Tide
and Installation
directories to the host's home directory
mv high-tide ~/high-tide && mv installation ~/installation
ht-docker-images.tar.gz
tar xzf ht-docker-images.tar.gz
load-images.sh
script into the images directory
cp ~/installation/load-images.sh ~/images
cd ~/images && ./load-images.sh
secrets.env
file from the installation project to the High Tide project
secrets.env
file is a set of default environment variables that are used by Docker containers during High Tide operation.cp ~/installation/secrets.env ~/high-tide/
~/high-tide/secrets.env
file
~/high-tide/proj/src/configure-host.sh
script
high-tide
directory (generally the expansion of the ~
directory)~/high-tide/proj/src
directory, run the configure-host.sh
script
cd ~/high-tide/proj/src && ./configure-host.sh
The configure-host.sh
script will prep the host system to run High Tide. It will generate required files and attempt to install nginx on the host. Once configuration is complete, the host will run a web server that can be used to control High Tide operation.
Cross-posted from the wiki
Ubuntu build hangs while waiting on SSH This is a known issue with the High Tide IADS build. You'll have to manually open the VM packer is building in VSphere and wait for the autoinstall to finish. Once you can interact with the CLI, add the IP packer is trying to connect to. Ubuntu pulls a new IP when it restarts during the initial setup process, which makes it undiscoverable by Packer.
The management IP will need to be changed to the Labnet subnet. To do so, update the IP on interface ens192 to the desired IP. Next, run the update-conf.sh script located in /home/control/. This script will update all existing configuration files with the currently set management IP and restart the affected services.
The exercise IP on interface ens224 shouldn't need to be changed, but if it does the update will have to be performed manually. Instructions on how to do this are provided in the update-conf.sh script.
Prerequisites
All testing was done on an Ubuntu 20.04 OS with >= 32GB disk Docker (version tested)
Docker-compose (version tested)
Installation user has sudoless docker commands enabled Host has nginx installed or if not, has the ability to run sudo apt install nginx. This command will run as part of the host configuration script.