Ship cartridge-cli inside enterprise packages.

[sharonovd]

Since packages (tgz/rpm) built upon Enterprise SDK are self-sufficient, it would be nice to ship cartirdge cli along with tarantoolctl.

Starting from cli 2.3 support operations scenarios (such as cartridge repair), it's relevant to bring it to production.

[Totktonada]

I asked colleagues about this idea and @olegrok clarified it: pack cartridge-cli into an application artifact (RPM / Deb / tgz / docker image). I understood the idea now, but the scenario is not quite clear: some way to deploy the app or a way to pass to another developer?

If it is about deploy, so the idea is to run instances using cartrdige start instead of tarantoolctl start? Whether the cartridge CLI tool supports 'system layout' (when instance files are installed into the system from an RPM / Deb package) or it is purely for tgz / docker?

@sharonovd Can you clarify, please?

[Totktonada]

I had talks with @sharonovd and @opomuc and, to be honest, still can't understand how cartridge cli shipped within an application package supposed to be used. Dmitry tells me about cartridge repair, but it seems that it is not possible to invoke it for a remote cluster (there is no any URI argument). Maybe if we'll write custom instances.yml and place it into cwd? Don't know.

I see two ways to proceed with this issue:

1. Just ship it despite doubts about usability.
2. Consider it as reqirement in https://github.com/tarantool/tt/issues/18 and do the same for tt.

I like the second way, because tt was initially designed with remote control ability in the mind (see https://github.com/tarantool/tt/issues/10).