Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade/downgrade a remote cluster #968

Open
Totktonada opened this issue Oct 3, 2024 · 0 comments
Open

Upgrade/downgrade a remote cluster #968

Totktonada opened this issue Oct 3, 2024 · 0 comments
Assignees
Labels
feature A new functionality

Comments

@Totktonada
Copy link
Member

Context

The new database upgrading/downgrading tool is proposed in #924 -- see more background context here.

Since I've filed this issue, I've consulted with @psergee and @oleg-jukovec and found that a support of remote instances requires some separate work. This is why the separate issue is created.

Proposal

Add some way to work with remote instances in upgrading/downgrading commands.

If it requires to write some file with URLs, logins, passwords -- OK. It does the job.

I think that the optimal solution would be extracting these URLs/logins/passwords from a cluster configuration written in the tarantool 3.x format.

It works even for upgrading from 1.10 to 2.11: we use the cluster configuration for tt, while tarantool instances are configured on its own. (Moreover, in a future we may have a tooling that converts cartridge configuration to 3.x configuration and it would simplify the things.)

Also tracked in TNTP-363
Part of TNTP-41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new functionality
Projects
None yet
Development

No branches or pull requests

2 participants