[IGNITE-15955] [IGNITE 3] Packaging improvements

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.0.0-alpha3
• Component/s: build
• Labels: ignite-3
• Epic Link: IEP-93 (Ignite Packaging)
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Valentin Kulichenko
• Created: 18/Nov/21 23:49
• Updated: 08/Aug/22 10:11
• Resolved: 08/Aug/22 10:11

Description

One of the ideas discussed in the scope of Ignite 3 was to provide a lightweight download with the CLI tool, which will then allow to install core artifacts and manage local node if needed. This however, seems to provide significant complications with a little value, mainly for the following reasons:

• Core artifacts installation is a separate step that user has to perform.
• This approach poorly integrates with OS-specific packaging systems (RPM, DEB.etc.) and with Linux services.
• CLI tool becomes cumbersome because it manages both local nodes and remote cluster.
• For external dependencies we will have a separate deployment mechanism, no need to have another one in the CLI tool.

Proposing to create three separate downloadable ZIP packages:

• ignite-cli - contains only CLI tool, can be used to connect to a remote cluster.
• ignite-core - contains Ignite core artifacts required to start local nodes, and scripts to manage those nodes (ignite-start, ignite-stop, ignite-restart).
• ignite - meta package combining ignite-cli and ignite-core.

With these changes, we also need to get rid of CLI tool commands responsible for local node management and artifact installation.

Issue Links

• blocks: IGNITE-15956 Packaging: RPM packages
• blocks: IGNITE-15957 Packaging: DEB packages