aim.sh MySQL Console

aim.sh MySQL Console is a set of MySQL full life cycle management tools deployed on Lazy Cat Micro Services. It is suitable for use in home laboratories, development and testing environments, and small and medium-sized intranet servers. It manages target Linux hosts through a secure and restricted SSH connection, and completes host management, system detection, MySQL installation and deployment, online backup, health monitoring, cluster topology management, task logging, and operational audits in a web console. 1. Supported MySQL deployment methods The following MySQL versions are supported: MySQL 5.6、5.7、8.0、8.4 Support the following deployment architectures: 1. stand-alone example 2. One master and one slave copy 3. Three-node MySQL Group Replication (MGR) Before deployment, the target host's operating system, CPU architecture, glibc version, network address, port occupancy, installation media compatibility, and remote executor status are checked. The execution log of each stage can be viewed in real time during the deployment process; after a multi-host task fails, execution can be continued from incomplete nodes to reduce the risk of duplicate operations. MySQL 5.6 and 5.7 have ended official maintenance. Although this application still supports the installation of archive versions, it is recommended to give priority to MySQL 8.0 or 8.4, which is still supported, in production environments. 2. Installation media management You can prepare the MySQL Generic installation package in the following ways: 1. Select files locally from the management computer 2. Select files from lazy cat online drive 3. Ask the target host to download it from the official MySQL address during deployment Supports.tar.xz,.tar.gz,.tgz and.tar formats, with a maximum of 2 GiB for a single file. During the upload process, fragmented transmission and breakpoint continuation are used, and SHA-256 is automatically calculated. The console identifies the MySQL version, CPU architecture, glibc requirements, and minimal/full types in the installation package. If you explicitly select the installation media to upload, the system first checks to see if it matches all target hosts, and then sends it to the target host over a protected SSH/SFTP connection. After the transfer is completed, the file size and SHA-256 will be re-checked, and will not be silently changed to Internet download if the verification fails. 3. Online backup Successfully deployed MySQL instances will automatically appear in the Backup Center. You can create manual or scheduled backup schedules that support: 1. Perform backup immediately 2. Regular backup using five-segment Cron expressions 3. Backup all databases 4. Only backup the specified database 5. Automatic cleanup by retention days 6. Automatic cleanup by maximum number of reserved copies 7. View backup history, execution status, file size and SHA-256 8. Download completed backup files The backup task calls the corresponding MySQL version of mysqldump on the target host, and attempts mariadb-dump if it cannot be found. Backup uses parameters such as single-transaction, quick, routines, events, and triggers to generate gzip compressed files in a streaming manner. The backup file is sent back to the Lazy Cat Micro Service through the SFTP connection with fixed fingerprints. The console calculates SHA-256 again. After the verification is successful, it is written to the private document directory of the current Lazy Cat user: Document/MySQL backup/plan name/year/month/ Temporary files on the target host will be deleted after a successful backup. MySQL passwords do not appear on the remote command line and task log. For InnoDB, backups are consistent logical backups; non-transactional tables such as MyISAM cannot guarantee that all tables are at the same point in time. It is still recommended to cooperate with regular recovery drills and off-site backup for important production databases. 4. Health monitoring The "Health Monitoring" page can collect host and MySQL metrics by instance. There is no need to install resident monitoring agents on the target server, and there is no need to open additional HTTP ports. Host monitoring indicators include: CPU usage Load Average memory usage Swap usage disk free space MySQL monitoring indicators include: MySQL running status and running time number of current connections Number of running connections maximum number of connections Maximum number of connections in history Cumulative number of connections Questions and Questions Number of slow queries Receive and send bytes Number of abnormal connections Number of open tables InnoDB buffer pool metrics Copying IO status Copying SQL status replication latency Each acquisition will be saved as a historical record, and each instance will retain up to 240 recent sampling data to facilitate observation of changes in connection pressure and operating status. 5. Log in to lazy cat account Applications connect to Lazy Cat Micro Service OIDC single sign-on without maintaining a separate application password. The lazy cat administrator group ADMIN will be mapped to AIM administrators; other lazy cat users will be mapped to read-only users by default. Administrators can perform host management, deployment, backup and user rights management, and read-only users can view instances, monitor data, task status and audit records. Local password login is turned off by default. When logging in, you will enter the Grant Access authorization page of the lazy cat. 6. Secure SSH host management AIM does not require target hosts to open additional management ports, and deployment, backup and monitoring are completed through SSH. It is recommended to use the host kit provided by the application, via https://aim. Download <Lazy Cat Name>. heiyu.space/downloads/aim-host-kit-2.4.3.tar.gz and execute on the management computer: ``` cd ~/Downloads tar -xzf aim-host-kit-2.4.3.tar.gz cd aim-host-kit-2.4.3 chmod +x aim-copy-id ./ aim-copy-id --install root@ target host IP ``` This order will do the following: 1. Generate or reuse AIM dedicated ED25519 keys 2. Detect the CPU architecture of the target host 3. Copy the executors and initialization scripts for the corresponding architecture 4. Create dedicated aimops users 5. Install the AIM public key 6. Install restricted root actuators 7. Configure minimized sudo permissions 8. Output the private key path that needs to be imported into the web console When adding a host on the Host Resources page: Host name: Fill in an easily identifiable name IP or domain name: Enter the target Linux host address SSH port: usually fill in 22 SSH user: fill in aimops Dedicated SSH private key: Import the private key file output by aim-copy-id Please pay special attention to: Private key files usually do not have a.pub suffix. The public key ending in.pub is the public key and cannot be filled in the private key input box. Do not fill in the SSH Host Key of the target server. Do not fill in the known_hosts content. Don't just fill in the file path of the private key. Do not use the root private key. Don't reuse your daily SSH private key. The correct private key content must start from the following line: -----BEGIN OPENSSH PRIVATE KEY----- And ends with the following line: -----END OPENSSH PRIVATE KEY----- After saving the host, the console reads the SSH SHA-256 fingerprint of the target server. The fingerprint must be checked and confirmed before AIM performs system detection, deployment, backup, or monitoring operations. If the server fingerprint changes, the connection will be denied to avoid connecting to the wrong or impersonated server. 7. Authority and audit The SSH private key and MySQL password are stored with AES-256-GCM encryption using the stable master key generated during installation. All important actions are recorded in the audit log, including: user login host create SSH fingerprint confirmation a password to view Installation media upload deployment task Example start and stop backup task reinitialize the Instance Uninstall Destructive operations such as reinitialization and uninstallation require a preview first, and the target instance address is entered again for confirmation to avoid erroneous operations. 8. Prerequisites for use This application is a MySQL management console, not a MySQL database service running directly in a lazy cat container. You need to prepare one or more Linux hosts that AIM can access through SSH over the local area network. The target host needs to install SSH Server, sudo, and visudo, and allow first-time initialization of account login. It is recommended to operate in the following order for first use: 1. Log in to AIM using your lazy cat account 2. Extract the host kit on the management computer 3. Execute aim-copy-id --install to initialize the target host 4. Import the AIM private private key in Host Resources 5. Check and fix SSH fingerprints 6. Perform host system detection 7. Upload MySQL installation media, or choose official download 8. Use the Deployment Wizard to create a stand-alone, master-slave, or three-node MGR 9. Create a backup plan in the Backup Center 10. Collect host and MySQL metrics in Health Monitor