You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Valentin Kulichenko (Jira)" <ji...@apache.org> on 2021/11/18 23:52:00 UTC
[jira] [Updated] (IGNITE-15955) [IGNITE 3] Packaging improvements
[ https://issues.apache.org/jira/browse/IGNITE-15955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Valentin Kulichenko updated IGNITE-15955:
-----------------------------------------
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.
was:
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.
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{}}}.
> [IGNITE 3] Packaging improvements
> ---------------------------------
>
> Key: IGNITE-15955
> URL: https://issues.apache.org/jira/browse/IGNITE-15955
> Project: Ignite
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.0.0-alpha3
> Reporter: Valentin Kulichenko
> Priority: Major
> Labels: ignite-3
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)