Skip to main content
The project defines the organizational area, the location is the placement, the tags are the signs of the machine, the group is the stored selection by the tags. These mechanisms can be used together.

Assignment of marks

Open the node → Placement and tags. Add key/value pairs and save. Use the same spelling throughout the park: env=prod and environment=production are different conditions. For one host, up to 16 tags are supported. The key starts with a lowercase Latin letter; then lowercase letters, numbers, dots, hyphens and accents are allowed, up to 32 characters only. Value up to 64 characters; use Latin letters, numbers and supported dividers. For example, the web servers of the working environment assign env=prod, role=web, and test - env=test, role=web. So you can choose all web servers or only work without renaming the machines.

Tagged team

In the Tree and the Group, create a Production Web group with the terms env=prod and role=web. All conditions must match simultaneously. The group supports from one to eight conditions and includes suitable approved nodes present in the inventory. Open the group composition before use. When you change the tags, the machine enters or leaves the group. Membership does not confirm that the agent online or the user has SSH access. Archive group is not used for new launches; archiving does not delete servers or cancel the actions issued to the agents.

Dynamic and fixed objectives

| Where the | group is used What happens after changing the | labels |---|---| | Node Role Rule | Selection recalculated; new suitable node can be accessed by the role of | | New playbook launch | Takes lineup at | target verification stage | Confirmed task | List of targets remains the same as | | Created schedule | List of former; new lineup needs new preview and schedule | If all nodes or groups are allowed, check which future machines will be accessed. Once the group is expanded, the old schedule does not automatically start serving the new servers.

Locations.

In Locations Locations, find a country or site and assign nodes. One node has one assigned location. Search supports country names and codes; C node filter hides empty entries. The country from the axottle.location tag is displayed in the park, but does not replace the designated site. The axottle.provider tag helps to know the provider without creating a group or right of access. Before you delete a location, move the nodes assigned to it: the occupied location cannot be deleted. Rename changes the organization of the directory, not the network address of the servers.

Projects and Axottle

When integrated, project membership is synchronized from Axottle; it limits the scope; SSH is issued by Telepúrte roles and grants or by explicit access settings from Axottle. Local tags and groups do not change the user’s project membership.

Verification

On two test nodes, check for inclusion and exclusion from the group after changing one label. Look at the goals of the role and the individual task: they must comply with the rules of dynamic selection and a fixed list.

Rollback

Return previous labels or group conditions, and check access by role. Assignments and schedules that are already created are not rebuilt: stop or suspend inappropriate ones, and create new ones with the right goals. Older panel assemblies, bastions, and agents may not contain the features described.