Skip to content

Latest commit

 

History

History
125 lines (103 loc) · 5.84 KB

README.en.md

File metadata and controls

125 lines (103 loc) · 5.84 KB

中文 / English

about

neatlogic-autoexec-scripts project, manages custom tool library (customized scripts for non-standard atomic operation plug-ins) management project, and neatlogic-autoexec-backend The main differences of the project are:

  • neatlogic-autoexec-backend project built-in tool library, is neatlogic-autoexec The automation module base solidifies the factory-built tools, which are not needed and cannot be changed and adjusted by the target users.

  • The custom tools in the neatlogic-autoexec-scripts project may need to be imported into neatlogic-autoexec module's custom tool after modification.

  • neatlogic-autoexec-scripts provides users with an entry point for extensible management boundaries.

Applicable scene

Currently, this project provides custom tools for open source scenarios and atomic operations, including:

  1. Create, destroy, start and stop Vmware virtual machines.
  2. Create a new virtual machine standardized configuration.
  3. Nginx, Tomcat, Jdk, Weblogic, Websphere middleware software single instance, cluster installation and delivery.
  4. MySQL master-slave, master-master, 1-master-multi-slave cluster installation and delivery.
  5. Oracle stand-alone, DG, ADG, RAC cluster installation and delivery.
  6. Postgresql stand-alone, master-slave installation and delivery.

⭐️Description

  • This project will update the automation scene customization tool from time to time, please continue to pay attention.

Explanation of key elements

The 5 elements defined by the atomic operation plugin

Implementation modalities

  • runner execution Execute on the machine where neatlogic-runner is located, referred to as local execution. Applicable to the need to install dependencies, such as vmware to create virtual machines.

  • Runner->target execution, based on protocol or [neatlogic-tagent-client] on the machine where neatlogic-runner is located neatlogic-tagent-client Even remote target execution. It is suitable for the installation of dependencies and the execution of remote targets, such as snmp collection.

  • target execution, remote target execution. It is suitable for delivering scripts that do not depend on the environment, such as starting and stopping applications.

  • Sql file execution. Applicable to operations such as database DDL and DML, such as SQL execution during application deployment.

Support script parsing development language

Currently, it supports customer-defined scenarios and operation extensions, and the supported development languages are:

  • bash
  • ksh
  • csh
  • python
  • perl
  • ruby
  • Powershell
  • vbscript
  • bat
  • cmd
  • javascript
  • package

Library file definition

  • Support custom library files, create public square libraries, and reference and use other custom atomic operation plug-ins.

Operation input parameters and output parameters

Supports custom input parameters, whether parameters are required, parameter validation, default values, and optional control types:

  • Text box
  • Single selection drop-down box
  • Multiple selection drop-down box
  • Radio box
  • Check box
  • Text field
  • Password
  • Date
  • Date time
  • File upload
  • File path
  • json object
  • Execution phase
  • Execution Node
  • Execution account
  • User selector

Atomic operation plug-in project management

Project dependency import and export tools rely on python3, support custom atomic operation plug-ins and version tool management, such as gitlab, svn, etc., and support one-click import/export of project code to the corresponding execution environment.

Environment variable initialization

cd autoscripts
source bin/setenv.sh

Environment configuration instructions

server.baseurl = http://192.168.0.10:8282 # neatlogic-app host IP and service port
server.username = autoexec # import users
server.password = # autoexec user token
password.key = #Password encryption key, which needs to be consistent with the key of neatlogic-autoexec-backend
tenant = demo # tenant
catalogs.default = Database #Import the starting directory, if it is empty, import all

Script import and export

#Export the backup script to the current directory
python3 autoscripts/bin/export.py

#Import the script to the system
python3 autoscripts/bin/import.py

Introduction to plugin directory

The following directory introduction is for reference only, and the directory name will be adjusted or changed from time to time.

  • Application: middleware related scenarios and operation directory
  • DataBase: database related scenarios and operation directory
  • Demo: Provide user-defined atomic operation reference case directory
  • OS: operating system level related scenarios and operation directory