Summary
TQLConsole ThingSpaces Configurator can be used to deploy and manage the A-Stack Runtime Environment consisting of your models (projects) on a target host machine(s).
A-Stack Runtime Environment deploy and manage can be done using TQLConsole ThingsSpace Configurator User interface or using TQL Command Line Interface (TQL CLI).
It provides following functionalities :
- Deploy Cluster
- Start/Stop/Restart of application in cluster nodes
- Dynamic Editing of Application Configurations files per cluster peer basis
- Execute Shell Script(s) and TQL queries against each application node
- Application Monitoring for Memory, CPU Usage
- Perform On-Demand Garbage Collection on a per node basis
- Log Files Aggregation and ELK (Elastic Search, LogStash, Kibana Setup)
Preparing the Target Host(s)
Target Host(s) needs to be prepared before the TQL Applications can be deployed using ThingSpace Configurator.
Target Host(s) Requirements
Setup and Install A-Stack Configurator Daemon
Creating a Gold Copy of A-Stack Configurator
Docker Container
AWS EC2 AMI
The discovery result is divided into two parts: Local Engine and Cluster Nodes categorized the Group to which the nodes belong.
User can view the details of the node by clicking on any node on the graph. The details will be published on the right hand side.
View A-Stack General Information
Users can view general information about each of the node by clicking on public IP address of the node.
View A-Stack for CPU, Memory
Performing On-Demand GC
Users can perform On demand Garbage collection on the invidiual nodes by clicking on the "Perform GC" button
TQLConsole DevOps UseCase on AWS InfraStructure
Elastic Search, Log Stash and Kibana Setup
From the invididual nodes the user can setup the log files to be written to a common mount point file system - Say: AWS EFS
Following Search Fields are available:
