Version 1.0.8
testgrinder service will be discontinued on January 31, 2025
testgrinder SMPC was discontinued as of February 1, 2024
Change Log
A bug that limited the number of launched bots was fixed.
The requirements for subnets to assign public IP addresses were removed.
The FORCE_SSL configuration file parameter was added. When set to false, testgrinder will respond over HTTP. When set to true (or not specified), HTTP requests will be redirected to HTTPS. When testgrinder is launched without user data, FORCE_SSL will default to false to allow interaction until the SSL certificate is configured.
The export-user-data script was added for exporting configuration files in the User Data format as described in the testgrinder documentation.
testgrinder bots will now self-terminate if abandoned by testgrinder.
The MONIT_NOTIFY_FROM_EMAIL configuration file parameter was added, allowing you to specify the email address that will appear in the "From" field of Monit notification emails.
The stop, start, and status scripts were added for stopping, starting, and checking the status of all testgrinder services.
The .sh extension was removed from the restart.sh script.
A delay was added to the starting of testgrinder services until provisioning completes.
The delay in background jobs posting logs to Papertrail was reduced.
The number of Delayed Job workers was reduced to 3 from 4.
AMIs
Visit Bearinc LLC on AWS Marketplace to see the available testgrinder AMIs (Amazon Machine Images).
You will need the following AMIs to deploy testgrinder in your private cloud:
| Server | Description | Version |
|---|---|---|
tg-app | testgrinder application server | 1.0.8 |
tg-bot | testgrinder bot (script runner) | 1.0.8 |
The tg-app and tg-bot AMIs are based on Ubuntu 20.04 LTS (Focal Fossa).
Dependencies
| Dependency | Description | Version |
|---|---|---|
MongoDB | database | 5.0 |
Supported Maximo versions
Maximo 7.6 (various service pack levels)
Maximo 7.5 (various service pack levels)
Upgrade Notes
Add 'FORCE_SSL: false' to .env configuration file if you wish for testgrinder to respond to HTTP requests rather than forcing redirection to HTTPS
Specify MONIT_NOTIFY_FROM_EMAIL in .env configuration file to have Monit use this email in From: field for emails it sends
Upgrade Instructions
Backup the database (Backup and Restore Database).
If the database is hosted on a tg-app server, copy the backup to a secure location.
Use the export-user-data script to export the existing tg-app configuration files in the User Data format (Configuration Files). Copy the user data to a secure location.
Stop the old tg-app server.
Modify the .env configuration file in the user data as described in the Upgrade Notes.
Launch a new tg-app server (Launch tg-app) using the user data – this will recreate the configuration files on the new server.
Restore the database from the backup file (Backup and Restore Database).
Update the following database settings (Database Stored Settings):
aws_runner_image_id: set to the new tg-bot AMI ID.
tg_api_url: update with the new tg-app server private address.
Test the new server to ensure it is functioning properly.
Last updated