Install Test Agent Application
The installation topic describes procedures to add a Test Agent from the Routing Director GUI and then deploy the Test Agent using the generated installation command.
The Test Agent Application is a container that you deploy as a Docker container, or as a container in a router running Junos Evolved OS.
We do not recommend installing Test Agents using Junos CLI.
Before You Begin
Before you begin the Test Agent installation, you must:
-
Install Docker Engine on the system running the latest Ubuntu version.
-
Ensure that no firewalls are blocking the connection to Routing Director on TCP port 6800, and to port 443 if you are running the Test Agent Application on a Junos router or installing it following the procedure in Add a Test Agent Application.
Add a Test Agent in Routing Director
Before deploying a Test Agent Application, you must add this Test Agent Application in the Routing Director GUI. Routing Director, then, generates a unique installation command that includes the secret key and host address required for deployment. To add a Test Agent in Routing Director, see Add a Test Agent Application and Download & Run Tab.
Deploy a Test Agent Using Container Image
You can deploy a Test Agent using the pre-built container image and the installation command generated in Routing Director by following the procedure in Add a Test Agent Application. Routing Director generates a single command that downloads the container image, loads the image, and starts the Test Agent using the secret key and host values specific to your environment.
To deploy a Test Agent using the container image:
On the target machine, copy and run the installation command generated when you added the Test Agent in Routing Director. For example,
user@hostname:~# export TA_NAME="<Test-Agent-name>" user@hostname:~# export TAGW_HOST="<Routing-Director-host-IP>" user@hostname:~# export TA_VERSION="<Test-Agent-version>" user@hostname:~# export TA_SECRET="<generated-secret-key>" user@hostname:~# wget https://${TAGW_HOST}/static/test_agent/paa-test-agent-application-container_${TA_VERSION}_amd64.tar.gz && \ docker load -i paa-test-agent-application-container_${TA_VERSION}_amd64.tar.gz && \ docker run \ --platform=linux/amd64 \ --network=host \ --detach \ --restart=unless-stopped \ --log-opt max-size=10m \ --log-opt max-file=2 \ --name "${TA_NAME}" \ paa/test-agent-application:${TA_VERSION} \ run \ --ncc-host ${TAGW_HOST} \ --secret-key ${TA_SECRET}Verify that the Test Agent started successfully:
docker logs -f ${TA_NAME}
- The
--restart=unless-stoppedflag ensures the Test Agent restarts automatically after a system reboot, unless you explicitly stop. - The
--log-optoptions limit the size and number of log files generated by the Test Agent. - To stop the Test Agent, run
docker stop <Test-Agent-name> - To check logs at any time, run
docker logs -f <Test-Agent-name>
The secret key in the generated command is unique to each Test Agent. Do not reuse the secret key for multiple Test Agents.
There is no in-place upgrade process for Test Agent Application container. To
upgrade, delete the existing container and start a new container using the
run command.