ID | IEP-11 |
Author | |
Sponsor | Denis A. Magda |
Created | |
Status | DRAFT |
Currently Apache Ignite shipped with mostly all methods of delivery, except standardized linux packages and other OS installers (like Windows Installer or macOS DMG). It will be very useful for project's popularity and accessibility to prepare such package and installers.
Possible benefits of packages introducing:
Currently, proposed (and implemented in IGNITE-7107) architecture is as follows:
Directory structure
Binary archive | Package | |
---|---|---|
IGNITE_HOME | <ROOT> | /usr/share/apache-ignite |
Classpath libs | <ROOT>/libs | /usr/lib/apache-ignite |
Working dir | <ROOT>/work | /var/lib/apache-ignite |
Configuration files | <ROOT>/config | /etc/apache-ignite |
Logging dir | <ROOT>/work/log | /var/log/apache-ignite |
Service wrapper | – |
|
apache-ignite@.service
) – systemd-compliant description of how to start / stop / restart Apache Ignite with all concomitant directives, like user access permissions management, PID consideration, on boot service load order and so on. Service designed to be able to run multiple instances of Apache Ignite via systemctl start apache-ignite@<config name>
.service.sh
) – main executable in charge of service operation, where service start process and firewalld port management included.default-config.xml
) with switched on Persistent Data Store and Multicast Discovery SPI for quick multinode topologi obtaining with minimum effort.None. Linux packages are just other means of delivery along with source / binary / docker / cloud images / etc., so only benefits are assumpted.
n/a
- IGNITE-7107Getting issue details... STATUS
- IGNITE-7108Getting issue details... STATUS