Create a t2.medium or c4.large machine in AWS
I picked Ubuntu 18 server from the list. Note that if you are playing in the "free tier" that neither of thse are in that free tier so they will incure some cost.
private key file
during the creation of the VM, you will be asked to create a new private key or use an existing one you may already have.
I had to create a new one. Gave it a name, bjones_telos, and it downloaded a bjones_telos.cer file. Amazon requires the permissions of the cer file not be too public, so run chmod 400 /path/file.cer to set the permissions so AWS is happy.
I saved my cer file in a location that was in the path so that when I ssh to the AWS instance it's easy to reference the key file.
On my mac, the specific steps were;
Copy the bjones_telos.cer file to /home/users/bjones
In a Terminal Window run the command shown in yellow, answer "yes" to the ssh security question.
dbjones@Bryans-MacBook-Pro ~ % ssh -i bjones_telos.cer ubuntu@ec2-3-137-206-225.us-east-2.compute.amazonaws.com
Welcome to Ubuntu 18.04.5 LTS (GNU/Linux 5.4.0-1045-aws x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.co
* Support: https://ubuntu.com/advantage
System information as of Sat Jul 10 15:25:26 UTC 2021
System load: 0.0 Processes: 10
Usage of /: 14.7% of 7.69GB Users logged in: 0
Memory usage: 5% IP address for eth0: 172.31.34.15
Swap usage: 0%
0 packages can be updated.
0 of these updates are security updates.
The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
ubuntu@ip-172-31-34-153:~$ Installing iQs
Continue instalilng IQs with the script from docker deployment manual.
Run the script
Log in to quay.io (y/n): y
Select NIC for the AoIP traffic (y/n): pick y
do not pick the docker0 nic, in my case, picked eth0
For simplicity, going to run in host network mode, so say no to "Do you want to deploy multiple containers on this host? [y/n]:"
From index of prodcuts, pick iQs.
INFO Select a Telos product to install (or press 'Ctrl' + 'C' to exit)
0) Precision Time Protocol Daemon for Linux [ptp4l]
1) iQs console [iqs]
2) VXs [vxs]
Index of product template: Pick 1
It will ask you to pick a name, I used cmixer1 (for Cloud Mixer)
Leave TAG blank, (we'll chage this later)
Leave STUDIO blank
iQS will be installed.
Ctrl+C to exit.
Does it work?
you should be able to put ec2-3-137-206-225.us-east-2.compute.amazonaws.com in your browser and get an iQs webpage.
I needed to add port 80 (HTTP) to be allwowed in the security group for this instnace. Firewall manges in the AWS console.
Edit yml file to install cloud mixer
from SSH
cd /opt/telos/cmixer1
sudo nano docker-compose.yml
Change this
to this.
Ctrl+X to exit, then answer Yes to write out the file
From the prompt;
sudo docker-compose down
Proabaly need to log in to Quay again, so
sudo docker login quay.io
sudo docker-compose up -d (make sure to use the -d)
New cloud-mixer container will be pulled, replacing iQs.
Check the webpage, should show Cloud Mixer now.
Install MASI License server.
Need to copy the files to AWS instance
sudo wget https://telos-public.s3.amazonaws.com/license-server/masi-license-server_u18.04_1.0.60.zipsudo apt install unzipsudo unzip masi-license-server_u18.04_1.0.60.zip cd cd install_linux./install_license_server.sh License server should be installed, return to Cloud Mixer, Licnese page, enter 127.0.0.1 (since this is all on the same host) and click Save. Should say CONNECTED after a few seconds.
