3.4.4 Outpost management
Outpost management involves the configuration and management of relay servers. This is done to allow automation application (AWX) jobs to be run from a relay server. To perform outpost management operations, the Primitive role of “automation_manager” must be assigned. For details on roles, see “Roles” and “Correspondence between roles and support functions in Ops I”.
Selecting “Organization Management” with a “Selection” button displays Outpost management in the navigation area.
The “Outpost management” window consists of the “Control Plane” window, “Node” window, “Node Group” window, and “IP Block” window.
(Table) Configuration of “Outpost” window
| Window | Description |
|---|---|
| Control Plane window | Obtain, update and download control plane information. |
| Node window | Obtain and delete node list information. Stop the agent and uninstall the RPM package before deleting the node. For information on creating nodes, see "Flow of configuring outpost", and for deletion, see "Deleting nodes". |
| Node Group window | Create, delete and edit node groups. |
| IP Block window | Create, delete and edit IP blocks. |
For information on control planes, nodes, node groups and IP blocks, see “Setting a relay server”.
This section describes the following items.
(1) Control plane management
Select “Control Plane” under “Outpost Management” in the navigation area to perform control plane management.
Fingerprints and agent tokens displayed in the control plane information are required for setting a relay server. Control plane information can be reissued with the “Rekey” button. Once reissued, the nodes that have already been built and connected will no longer be able to connect to Ops I. If Rekey is performed, set the relay server again and rebuild the node.
The RPM packages required for setting a relay server can be downloaded from the Download Agent page.
(Figure) “Control Plane” window
(Table) Types of content displayed in the “Control Plane” window
| Item | Required | Description |
|---|---|---|
| Version | Yes | Control plane version |
| Fingerprint | Yes | Outpost component fingerprint |
| Agent Token | Yes | Outpost component agent token |
(Table) Types of operation buttons in the “Control Plane” window
| Item | Description | |
|---|---|---|
| ① | Rekey | Reissues fingerprints and agent tokens. If the "Rekey" button is clicked, a confirmation dialog box appears. Checking the checkbox and clicking the "OK" button deletes old information and reissues new information. |
| ② | Copy button | Copies fingerprints and agent tokens. |
| ③ | Linux x86_64 RPM | Downloads the RPM package. |
| ④ | Linux x86_64 RPM Signatures | Downloads the RPM package signature. |
(2) Node management
Select “Node” under “Outpost Management” in the navigation area to perform node management.
A list of registered node names is displayed in the “Node” window. The types of operation buttons in the “Node” window are as follows.
(Table) Types of operation buttons in the “Node” window
| Item | Description |
|---|---|
| Delete | Deletes a node. Becomes inactive when the checkbox is not selected. The agent must be uninstalled before deleting the node. For details, see "Deleting nodes". |
To add a node, add it in the relay server settings. For more information on relay server settings, see “Setting a relay server”.
To view or edit the information for a registered node, click on the link for the node name shown in the node list and access the “Node details” window.
The node group to which the node is assigned is shown in the “Node details” window. The content displayed and the types of operation buttons in the “Node details” window are as follows.
(Table) Types of content displayed in the “Node details” window
| Item | Required | Description |
|---|---|---|
| Name | Yes | Node name: Configures the relay server settings. For more information on relay server settings, see "Setting a relay server". |
| Status | Yes | Displays whether the node can be used |
| Registered At | Yes | Date and time of registration |
| Version | Yes | Displays the control plane version |
(Table) Types of operation buttons in the “Node details” window
| Item | Description |
|---|---|
| Edit | Edits a node. Clicking the "Edit" button displays the "Edit" button for the related resource. Clicking the "Edit" button for the related resource opens the "Assign Node Group" window, where node groups can be configured. A maximum of 10 node groups can be assigned to a single node. In addition, assigning a node group to a node will also update the node group information. Be careful not to exceed the node group limit. |
| Delete | Deletes a node. The agent must be uninstalled before deleting the node. For details, see "Deleting nodes". |
(3) Node group management
Select “Node Group” under “Outpost Management” in the navigation area to perform node group management. The types of operation buttons in the “Node Group” window are as follows.
(Table) Types of operation buttons in the “Node Group” window
| Item | Description |
|---|---|
| Add | Adds a node group. Becomes inactive when the checkbox is selected. |
| Delete | Deletes a node group. Becomes inactive when the checkbox is not selected. |
Click the “Add” button to add a node group. Clicking the “Add” button opens the “Add node group” window. The content displayed and the types of operation buttons in the “Add node group” window are as follows.
(Table) Types of content displayed in the “Add node group” window
| Item | Required | Description |
|---|---|---|
| Name | Yes | Node group name |
| Description | No | Free space |
(Table) Types of operation buttons in the “Add node group” window
| Item | Description |
|---|---|
| Save | Saves the entered node group information. Becomes inactive when the required item has not been entered. |
| Cancel | Cancels without registering the node group information. |
To view or edit the information for a registered node group, click on the link for the node group name shown in the node group list and access the “Node group details” window.
The “Node group details” window shows the node group information and related resources. The content displayed and the types of operation buttons in the “Node group details” window are as follows.
(Table) Types of content displayed in the “Node group details” window
| Item | Required | Description |
|---|---|---|
| ID | Yes | Node group ID: Automatically generated when adding a node group. When recreating a node group, the ID is changed even if the name is the same. The node group ID is required for instance group settings in the AWX job template when using a relay server. For details of the procedure for using a relay server, see "Using a relay server". |
| Name | Yes | Node group name: Set when adding a node group. |
| Description | No | Free space |
(Table) Types of operation buttons in the “Node group details” window
| Item | Description |
|---|---|
| Edit | Edits a node group. Clicking the "Edit" button displays the "Edit" button for the related resource. Clicking the "Edit" button for the related resource opens the "Assign Node" window or "Assign IP Block" window, where nodes and IP blocks can be configured. A maximum each of 10 nodes and IP blocks can be assigned to a single node group. In addition, assigning a node or IP block to a node group will also update the node or IP block information. Be careful not to exceed the node or IP block limit. |
| Delete | Deletes a node group. |
(4) IP block management
Select “IP Block” under “Outpost Management” in the navigation area to perform IP block management. The types of operation buttons in the “IP Block” window are as follows.
(Table) Types of operation buttons in the “IP Block” window
| Item | Description |
|---|---|
| Add | Adds an IP block. Becomes inactive when the checkbox is selected. |
| Delete | Deletes an IP block. Becomes inactive when the checkbox is not selected. |
Click the “Add” button to add an IP block. Clicking the “Add” button opens the “Add IP block” window. To view or edit the information for a registered IP block, click on the link for the IP block name shown in the IP block list and access the “IP block details” window. The content displayed and the types of operation buttons in the “Add IP block” window are as follows.
(Table) Types of content displayed in the “Add IP block” window
| Item | Required | Description |
|---|---|---|
| Name | Yes | IP block name |
| CIDR | Yes | IP address range of the IP block: Please use CIDR notation. |
| Except | No | Exceptionally unavailable IP addresses within the specified CIDR: Up to 100 can be specified. |
| Description | No | Free space |
(Table) Types of operation buttons in the “Add IP block” window
| Item | Description |
|---|---|
| Save | Saves the entered IP block information. Becomes inactive when the required item has not been entered. |
| Cancel | Cancels without registering the IP block information. |
The “IP block details” window shows IP block information and related resources. The content displayed and the types of operation buttons in the “IP block details” window are as follows.
(Table) Types of content displayed in the “IP block details” window
| Item | Required | Description |
|---|---|---|
| ID | Yes | IP block ID: Automatically generated when adding an IP block. When recreating an IP block, the ID is changed even if the name is the same. |
| Name | Yes | IP block name: Set when adding an IP block group. |
| CIDR | Yes | IP address range of the IP block |
| Except | No | Exceptionally unavailable IP addresses within the specified CIDR: Up to 100 can be specified. |
| Description | No | Free space |
(Table) Types of operation buttons in the “IP block details” window
| Item | Description |
|---|---|
| Edit | Edit an IP block. Clicking the "Edit" button displays the "Edit" button for the related resource. Clicking the "Edit" button for the related resource opens the "Assign Node Group" window, where node groups can be configured. A maximum of 10 node groups can be assigned to a single IP block. In addition, assigning a node group to an IP block will also update the node group information. Be careful not to exceed the node group limit. |
| Delete | Deletes an IP block. |