ATE: document the `eval_3_0` and `eval` playbooks

Open

#5,568 opened on Feb 5, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ate

Dominant language: CSS
Stars: 15
Forks: 49
Avg merge: 1d 13h
Merged PRs (30d): 3

Description

Related dev. issue(s): GitHub link(s)
Product: ATE
Since: 1.x, 2.x?
Root document: https://www.tarantool.io/ru/devops/latest/docker-scenarios-common/ (?)
SME: @ lastoCHka42 @ opomuc @ Satbek

Details

Ксения Антонова (23.01.2026 10:44):
Есть ли в ате плейбук, с помощью которого можно сделать откат версии с box.schema.downgrade?

Анна Балаева (23.01.2026 11:39):
Да, есть, но он не задокументирован - eval_3_0 для тройки, eval для картриджа

Анна Балаева (23.01.2026 11:39):

Антон Свиридов (21.01.2026 15:30): ansible-playbook spimex.exchange.eval3 -i inventory.yml -i inventory/02-dict.yml --private-key lt_pk --user redos -b --limit=dict_storage-1-2, --e "eval_command='for k in pairs(box.space) do if type(k) == "string" and not string.match(tostring(k), "^_") then box.space[k]:truncate() end end'"

Анна Балаева (23.01.2026 11:39):
Примерно так запускается с поправкой на пути, у Антона они переделанные

При написании нужно учитывать следующее:

Сатбек Турганбаев (23.01.2026 15:57):
я тут момент увидел, который упустил
при upgrade, downgrade нужно на репликах вызвать box.snapshot, когда новая схема применится. Только через миграции это невозможно сделать.
tt это делает. Не уверен, что ATE делает.

The Tarantool’s downgrade procedure is similar to the upgrade process that is described in the Upgrades topic. You need to run box.schema.downgrade() only on master and execute box.snapshot() on every instance in a replica set before restart to an older version.

Сатбек Турганбаев (23.01.2026 15:57):
https://jira.vk.team/browse/TNTP-5000
ate даже snapshot не делают

Сатбек Турганбаев (23.01.2026 15:58):
выходит 3 способа, tt самый надежный

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Research direction

Start with the ATE documentation at the linked root document and trace the eval_3_0 and eval playbooks from the example ansible-playbook command. Document how each playbook is invoked and clarify the upgrade/downgrade procedure, including when box.schema.downgrade() and box.snapshot() are required; confirm the behavior with the listed SMEs before marking it done.

Written by the indexing model from the issue text.

Assessment

Tech stack: ansible
Domain: devops, documentation
Issue type: Documentation
Difficulty: 4/5
Estimated time: 3-5 days
Activity status: Stale
Clarity: Mostly clear
Newbie friendliness: 35/100