TASKCTL Management platform system Admin Provides platform-level scheduling node management, system engineering management, job type management, user ** (group) permission management, and constant management for administrator users. In addition, it also provides the configuration and maintenance of platform message interfaces such as SMS and email, forcible check-in (process) ** maintenance, and the export and import of platform dispatching meta information and other maintenance functions.
Node management
The platform node is used to manage the scheduling control node of the entire platform. Distributed scheduling architecture can be deployed through scheduling service nodes and master agent service nodes. The cluster scheduling architecture can be deployed through the master agent and its subordinate slave agents. The topology page for node management displays the network topology of the entire platform. As shown below:
The only top-level scheduling service node, sVRNode, is used to manage and control scheduling policies and instructions for jobs.
The subordinate node of the scheduling service is the master agent node, which receives scheduling instructions and executes specific job procedures.
The subordinate nodes of the master agent are subordinate agent nodes, and together the master and slave agents form cluster nodes.
Adding platform Nodes
After installing the node service, you need to use the Add Platform Node function to instantiate the back-end node. The steps are as follows:
-
Click the “+” icon in the toolbar to pop up the create dialog box.
-
Select the type of node (master/slave) and parent node that you want to create.
-
Enter the node name. English characters are recommended. You can make remarks in Chinese in the description
-
Enter the IP and port of the node (same as the back-end installed node service)
-
Click OK to complete the creation of the node.
Edit platform node
After clicking the node, the popup tool panel provides ** “Edit” ** button, which is convenient for users to quickly open the editing side window of the node. In addition to basic attributes, you can also maintain the status of a node, the maximum number of concurrent jobs on the node, and the total number of virtual resources on the node. In addition, it also provides one-click application project permission to quickly set the current node permission to all projects on the platform. As shown below:
Deleting a Platform Node
After you click a node, the toolbar provides a ** Delete ** button to quickly delete the node. The scheduling service node cannot be deleted. The diagram below:
Start or stop a node
After you click a node, the start and Stop buttons are displayed on the tool panel to help you quickly start or stop the node. After the scheduling service node is stopped, the Web client does not need to obtain application data. If the node is stopped for a long time, you are advised to disable the node.
After the node is successfully started, the status icon is displayed in green. The stopped status icon is displayed in gray. In addition, it will display ** “uninitialized”, “network exception”, “node exception” ** and other states.