Starting and Stopping Eggplant Generator

You can start and stop Eggplant Generator when it is deployed in a Docker container by starting and stopping the container in which it runs. Starting and stopping Eggplant Generator also requires starting and stopping Eggplant IAM (Keysight), which is Generator's identity and access provider.

note

These start and stop instructions do not apply to Kubernetes deployments. For information about deploying with Kubernetes, see Deploying Eggplant Generator with Kubernetes.

Starting Eggplant Generator

If you are starting Eggplant Generator for the first time, see Deploy Eggplant Generator with Docker.

If you need to restart Eggplant Generator, for example, because the underlying system reboots, follow the steps below to restart both Eggplant IAM and Generator:

1. Open a terminal window and/or change to the directory where the docker compose for Eggplant IAM is located and run the following command:

   docker compose --file docker-compose-6.3.103.yaml --profile default up -d

2. Open a second terminal window and/or change to the directory where the docker compose for Generator is located and run this:

   docker compose --file docker-compose-0.0.5.yaml --profile default up -d

Stopping Eggplant Generator

note

Docker Desktop does not reliably stop Eggplant Generator. Therefore, you should use the following instructions instead.

To stop Eggplant Generator, follow the steps below to stop the containers running it and Eggplant IAM (Keycloak):

1. Open a terminal window where your Generator docker compose is stored and run this:

   docker compose --file docker-compose-0.0.5.yaml --profile default stop

2. Open a second terminal window or change to the directory where the docker compose for IAM is located and run the following command:

docker compose --file docker-compose-6.3.103.yaml --profile default stop