diff --git a/2.9.0.tar.gz b/2.9.0.tar.gz
new file mode 100644
index 0000000000000000000000000000000000000000..e85e61ddb4e3227e460d6fb60379d9ccdbb9dda1
Binary files /dev/null and b/2.9.0.tar.gz differ
diff --git a/ignite.spec b/ignite.spec
new file mode 100644
index 0000000000000000000000000000000000000000..a96fb01029b5b15b9fcec7131d2ca473cbe6d59f
--- /dev/null
+++ b/ignite.spec
@@ -0,0 +1,253 @@
+%define __jar_repack %{nil}
+%define user ignite
+%define _log %{_var}/log
+
+
+Name:             ignite
+Version:          2.9.0
+Release:          1
+Summary:          Apache Ignite In-Memory Computing, Database and Caching Platform
+Group:            Development/System
+License:          ASL 2.0
+URL:              https://ignite.apache.org/
+Source0:          https://github.com/apache/ignite/archive/%{version}.tar.gz
+Source1:          name.service
+Source2:          service.sh
+Source3:          settings.xml
+BuildRequires:    java-1.8.0-openjdk-devel maven
+Requires:         java-1.8.0, systemd
+Requires(pre):    shadow-utils
+Provides:         apache-%{name}
+Provides:         %{name}
+AutoReq:          no
+AutoProv:         no
+BuildArch:        noarch
+%description
+Ignite™ is a memory-centric distributed database, caching, and processing
+platform for transactional, analytical, and streaming workloads, delivering
+in-memory speeds at petabyte scale
+
+%prep
+%autosetup -p1 -n ignite-%{version}
+
+%build
+cp  %{SOURCE3} ./
+mvn initialize -Prelease -DskipTests install -Pall-java,all-scala,licenses # -s settings.xml
+
+%install
+cd target/bin/
+unzip apache-%{name}-%{version}-bin.zip 
+cd apache-%{name}-%{version}-bin
+mkdir -p %{buildroot}%{_datadir}/apache-%{name}
+mkdir -p %{buildroot}%{_libdir}/apache-%{name}
+mkdir -p %{buildroot}%{_datadir}/doc/apache-%{name}-%{version}/bin
+mkdir -p %{buildroot}%{_log}/apache-%{name}
+mkdir -p %{buildroot}%{_sharedstatedir}/apache-%{name}
+mkdir -p %{buildroot}%{_sysconfdir}/systemd/system
+mkdir -p %{buildroot}%{_bindir}
+
+# Copy nessessary files and remove *.bat files
+cp -rf benchmarks bin platforms %{buildroot}%{_datadir}/apache-%{name}
+cp -rf examples %{buildroot}%{_datadir}/doc/apache-%{name}-%{version}
+mv -f %{buildroot}%{_datadir}/apache-%{name}/bin/ignitevisorcmd.sh %{buildroot}%{_datadir}/doc/apache-%{name}-%{version}/bin/
+find %{buildroot}%{_datadir}/apache-%{name}/ -name *.bat -exec rm -rf {} \;
+
+# Copy libs to /usr/lib and map them to IGNITE_HOME
+cp -rf libs/* %{buildroot}%{_libdir}/apache-%{name}
+ln -sf %{_libdir}/apache-%{name} %{buildroot}%{_datadir}/apache-%{name}/libs
+
+# Setup configuration
+cp -rf config %{buildroot}%{_sysconfdir}/apache-%{name}
+ln -sf %{_sysconfdir}/apache-%{name} %{buildroot}%{_datadir}/apache-%{name}/config
+
+# Setup systemctl service
+cp -rf %{SOURCE1} %{buildroot}%{_sysconfdir}/systemd/system/apache-%{name}@.service
+cp -rf %{SOURCE2} %{buildroot}%{_datadir}/apache-%{name}/bin/
+chmod +x %{buildroot}%{_datadir}/apache-%{name}/bin/service.sh
+for file in %{buildroot}%{_sysconfdir}/systemd/system/apache-%{name}@.service %{buildroot}%{_datadir}/apache-%{name}/bin/service.sh
+do
+    sed -i -r -e "s|#name#|apache-%{name}|g" \
+              -e "s|#user#|%{user}|g" \
+        ${file}
+done
+
+# Map work and log directories
+ln -sf %{_sharedstatedir}/apache-%{name} %{buildroot}%{_datadir}/apache-%{name}/work
+ln -sf %{_log}/apache-%{name} %{buildroot}%{_sharedstatedir}/apache-%{name}/log
+
+
+#%pre
+#-------------------------------------------------------------------------------
+#
+# Preinstall scripts
+# $1 can be:
+#     1 - Initial install 
+#     2 - Upgrade
+#
+
+
+%post
+#-------------------------------------------------------------------------------
+#
+# Postinstall scripts
+# $1 can be:
+#     1 - Initial installation
+#     2 - Upgrade
+#
+
+echoUpgradeMessage () {
+    echo "======================================================================================================="
+    echo "  WARNING: Updating Apache Ignite's cluster version requires updating every node before starting grid  "
+    echo "======================================================================================================="
+}
+
+setPermissions () {
+    chown -R %{user}:%{user} %{_sharedstatedir}/apache-%{name} %{_log}/apache-%{name}
+}
+
+case $1 in
+    1|configure)
+        # DEB postinst upgrade
+        if [ ! -z "${2}" ]; then
+            echoUpgradeMessage
+        fi
+
+        # Add user for service operation
+        useradd -r -d %{_datadir}/apache-%{name} -s /usr/sbin/nologin %{user}
+
+        # Change ownership for work and log directories
+        setPermissions
+
+        # Install alternatives
+        # Commented out until ignitevisorcmd / ignitesqlline is ready to work from any user
+        #update-alternatives --install %{_bindir}/ignitevisorcmd ignitevisorcmd %{_datadir}/apache-%{name}/bin/ignitevisorcmd.sh 0
+        #update-alternatives --auto ignitevisorcmd
+        #update-alternatives --display ignitevisorcmd
+        #update-alternatives --install %{_bindir}/ignitesqlline ignitesqlline %{_datadir}/apache-%{name}/bin/sqlline.sh 0
+        #update-alternatives --auto ignitesqlline
+        #update-alternatives --display ignitesqlline
+        ;;
+    2)
+        # RPM postinst upgrade
+        echoUpgradeMessage
+
+        # Workaround for upgrade from 2.4.0
+        if [ -d /usr/com/apache-ignite/ ]; then
+            for file in /usr/com/apache-ignite/*; do
+                if [ ! -h $file ]; then
+                    cp -rf $file %{_sharedstatedir}/apache-%{name}/
+                fi
+            done
+        fi
+
+        # Change ownership for work and log directories (yum resets permissions on upgrade nevertheless)
+        setPermissions
+        ;;
+esac
+
+
+%preun
+#-------------------------------------------------------------------------------
+#
+# Pre-uninstall scripts
+# $1 can be:
+#     0 - Uninstallation
+#     1 - Upgrade
+#
+
+stopIgniteNodes () {
+    if ! $(grep -q "Microsoft" /proc/version); then
+        systemctl stop 'apache-ignite@*'
+    fi
+    ps ax | grep '\-DIGNITE_HOME' | head -n-1 | awk {'print $1'} | while read pid; do
+        kill -INT ${pid}
+    done
+}
+
+case $1 in
+    0|remove)
+        # Stop all nodes (both service and standalone)
+        stopIgniteNodes
+
+        # Remove alternatives
+        # Commented out until ignitevisorcmd / ignitesqlline is ready to work from any user
+        #update-alternatives --remove ignitevisorcmd /usr/share/apache-%{name}/bin/ignitevisorcmd.sh
+        #update-alternatives --display ignitevisorcmd || true
+        #update-alternatives --remove ignitesqlline /usr/share/apache-%{name}/bin/sqlline.sh
+        #update-alternatives --display ignitesqlline || true
+        ;;
+    1|upgrade)
+        # Stop all nodes (both service and standalone)
+        echo "=================================================================================="
+        echo "  WARNING: All running Apache Ignite's nodes will be stopped upon package update  "
+        echo "=================================================================================="
+        stopIgniteNodes
+        ;;
+esac
+
+
+%postun
+#-------------------------------------------------------------------------------
+#
+# Post-uninstall scripts
+# $1 can be:
+#     0 - Uninstallation
+#     1 - Upgrade
+#
+
+case $1 in
+    0|remove)
+        # Remove user
+        userdel %{user}
+
+        # Remove service PID directory
+        rm -rfv /var/run/apache-%{name}
+
+        # Remove firewalld rules if firewalld is installed and running
+        if [[ "$(type firewall-cmd &>/dev/null; echo $?)" -eq 0 && "$(systemctl is-active firewalld)" == "active" ]]
+        then
+            for port in s d
+            do
+                firewall-cmd --permanent --direct --remove-rule ipv4 filter INPUT 0 -p tcp -m multiport --${port}ports 11211:11220,47500:47509,47100:47109 -j ACCEPT &>/dev/null
+                firewall-cmd --permanent --direct --remove-rule ipv4 filter INPUT 0 -p udp -m multiport --${port}ports 47400:47409 -j ACCEPT &>/dev/null
+            done
+            firewall-cmd --permanent --direct --remove-rule ipv4 filter INPUT 0 -m pkttype --pkt-type multicast -j ACCEPT &>/dev/null
+            systemctl restart firewalld
+        fi
+        ;;
+    1|upgrade)
+        :
+        ;;
+esac
+
+
+%files
+
+%dir %{_datadir}/apache-%{name}
+%dir %{_sysconfdir}/apache-%{name}
+%dir %{_sharedstatedir}/apache-%{name}
+%dir %{_log}/apache-%{name}
+
+%{_datadir}/apache-%{name}/benchmarks
+%{_datadir}/apache-%{name}/bin
+%{_datadir}/apache-%{name}/config
+%{_datadir}/apache-%{name}/libs
+%{_datadir}/apache-%{name}/platforms
+%{_datadir}/apache-%{name}/work
+%{_datadir}/doc/apache-%{name}-%{version}
+%{_libdir}/apache-%{name}
+%{_sysconfdir}/systemd/system/apache-%{name}@.service
+%{_sharedstatedir}/apache-%{name}/log
+
+%config(noreplace) %{_sysconfdir}/apache-%{name}/*
+
+%doc README.txt
+%doc NOTICE
+%doc RELEASE_NOTES.txt
+%doc MIGRATION_GUIDE.txt
+%license LICENSE
+
+
+%changelog
+* Mon Dec 14 2020 weidong <weidong@uniontech.com> - 2.9.0-1
+- Initial package.
diff --git a/name.service b/name.service
new file mode 100644
index 0000000000000000000000000000000000000000..78b5d252464dd9b48fe075f93d3c9d5ea1dc1121
--- /dev/null
+++ b/name.service
@@ -0,0 +1,17 @@
+[Unit]
+Description=Apache Ignite In-Memory Computing Platform Service
+After=syslog.target network.target
+
+[Service]
+Type=forking
+User=#user#
+WorkingDirectory=/usr/share/#name#/work
+PermissionsStartOnly=true
+ExecStartPre=-/usr/bin/mkdir -p /var/run/#name#
+ExecStartPre=-/usr/bin/chown #user#:#user# /var/run/#name#
+ExecStartPre=-/usr/bin/env bash /usr/share/#name#/bin/service.sh set-firewall
+ExecStart=/usr/share/#name#/bin/service.sh start %i
+PIDFile=/var/run/#name#/%i.pid
+
+[Install]
+WantedBy=multi-user.target
diff --git a/service.sh b/service.sh
new file mode 100644
index 0000000000000000000000000000000000000000..454478d7a7b85a830736d1d65486f8bde234a036
--- /dev/null
+++ b/service.sh
@@ -0,0 +1,28 @@
+#!/usr/bin/env bash
+
+firewallCmd="firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT 0"
+
+# Define function to check whether firewalld is present and started and apply firewall rules for grid nodes
+setFirewall ()
+{
+	if [[ "$(type firewall-cmd &>/dev/null; echo $?)" -eq 0 && "$(systemctl is-active firewalld)" == "active" ]]
+	then
+	    for port in s d
+	    do
+	        ${firewallCmd} -p tcp -m multiport --${port}ports 11211:11220,47500:47509,47100:47109 -j ACCEPT &>/dev/null
+	        ${firewallCmd} -p udp -m multiport --${port}ports 47400:47409 -j ACCEPT &>/dev/null
+	    done
+	    ${firewallCmd} -m pkttype --pkt-type multicast -j ACCEPT &>/dev/null
+
+	    systemctl restart firewalld
+	fi
+}
+
+case $1 in
+	start)
+		/usr/share/#name#/bin/ignite.sh /etc/#name#/$2 & echo $! >> /var/run/#name#/$2.pid
+		;;
+	set-firewall)
+		setFirewall
+		;;
+esac
diff --git a/settings.xml b/settings.xml
new file mode 100644
index 0000000000000000000000000000000000000000..5c9d68e8af193ee9dd4bf497242ee9f0bfb05ba9
--- /dev/null
+++ b/settings.xml
@@ -0,0 +1,264 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+<!--
+ | This is the configuration file for Maven. It can be specified at two levels:
+ |
+ |  1. User Level. This settings.xml file provides configuration for a single user,
+ |                 and is normally provided in ${user.home}/.m2/settings.xml.
+ |
+ |                 NOTE: This location can be overridden with the CLI option:
+ |
+ |                 -s /path/to/user/settings.xml
+ |
+ |  2. Global Level. This settings.xml file provides configuration for all Maven
+ |                 users on a machine (assuming they're all using the same Maven
+ |                 installation). It's normally provided in
+ |                 ${maven.conf}/settings.xml.
+ |
+ |                 NOTE: This location can be overridden with the CLI option:
+ |
+ |                 -gs /path/to/global/settings.xml
+ |
+ | The sections in this sample file are intended to give you a running start at
+ | getting the most out of your Maven installation. Where appropriate, the default
+ | values (values used when the setting is not specified) are provided.
+ |
+ |-->
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
+  <!-- localRepository
+   | The path to the local repository maven will use to store artifacts.
+   |
+   | Default: ${user.home}/.m2/repository
+  <localRepository>/path/to/local/repo</localRepository>
+  -->
+
+  <!-- interactiveMode
+   | This will determine whether maven prompts you when it needs input. If set to false,
+   | maven will use a sensible default value, perhaps based on some other setting, for
+   | the parameter in question.
+   |
+   | Default: true
+  <interactiveMode>true</interactiveMode>
+  -->
+
+  <!-- offline
+   | Determines whether maven should attempt to connect to the network when executing a build.
+   | This will have an effect on artifact downloads, artifact deployment, and others.
+   |
+   | Default: false
+  <offline>false</offline>
+  -->
+
+  <!-- pluginGroups
+   | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
+   | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
+   | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
+   |-->
+  <pluginGroups>
+    <!-- pluginGroup
+     | Specifies a further group identifier to use for plugin lookup.
+    <pluginGroup>com.your.plugins</pluginGroup>
+    -->
+  </pluginGroups>
+
+  <!-- proxies
+   | This is a list of proxies which can be used on this machine to connect to the network.
+   | Unless otherwise specified (by system property or command-line switch), the first proxy
+   | specification in this list marked as active will be used.
+   |-->
+  <proxies>
+    <!-- proxy
+     | Specification for one proxy, to be used in connecting to the network.
+     |
+    <proxy>
+      <id>optional</id>
+      <active>true</active>
+      <protocol>http</protocol>
+      <username>proxyuser</username>
+      <password>proxypass</password>
+      <host>proxy.host.net</host>
+      <port>80</port>
+      <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
+    </proxy>
+    -->
+  </proxies>
+
+  <!-- servers
+   | This is a list of authentication profiles, keyed by the server-id used within the system.
+   | Authentication profiles can be used whenever maven must make a connection to a remote server.
+   |-->
+  <servers>
+    <!-- server
+     | Specifies the authentication information to use when connecting to a particular server, identified by
+     | a unique name within the system (referred to by the 'id' attribute below).
+     |
+     | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
+     |       used together.
+     |
+    <server>
+      <id>deploymentRepo</id>
+      <username>repouser</username>
+      <password>repopwd</password>
+    </server>
+    -->
+
+    <!-- Another sample, using keys to authenticate.
+    <server>
+      <id>siteServer</id>
+      <privateKey>/path/to/private/key</privateKey>
+      <passphrase>optional; leave empty if not used.</passphrase>
+    </server>
+    -->
+  </servers>
+
+  <!-- mirrors
+   | This is a list of mirrors to be used in downloading artifacts from remote repositories.
+   |
+   | It works like this: a POM may declare a repository to use in resolving certain artifacts.
+   | However, this repository may have problems with heavy traffic at times, so people have mirrored
+   | it to several places.
+   |
+   | That repository definition will have a unique id, so we can create a mirror reference for that
+   | repository, to be used as an alternate download site. The mirror site will be the preferred
+   | server for that repository.
+   |-->
+  <mirrors>
+    <!-- mirror
+     | Specifies a repository mirror site to use instead of a given repository. The repository that
+     | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
+     | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
+     |
+    <mirror>
+      <id>mirrorId</id>
+      <mirrorOf>repositoryId</mirrorOf>
+      <name>Human Readable Name for this Mirror.</name>
+      <url>http://my.repository.com/repo/path</url>
+    </mirror>
+     -->
+        <mirror>
+            <id>nexus-aliyun</id>
+            <mirrorOf>central</mirrorOf>
+            <name>Nexus aliyun</name>
+            <url>http://maven.aliyun.com/nexus/content/groups/public/</url>
+        </mirror>
+
+  </mirrors>
+
+  <!-- profiles
+   | This is a list of profiles which can be activated in a variety of ways, and which can modify
+   | the build process. Profiles provided in the settings.xml are intended to provide local machine-
+   | specific paths and repository locations which allow the build to work in the local environment.
+   |
+   | For example, if you have an integration testing plugin - like cactus - that needs to know where
+   | your Tomcat instance is installed, you can provide a variable here such that the variable is
+   | dereferenced during the build process to configure the cactus plugin.
+   |
+   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
+   | section of this document (settings.xml) - will be discussed later. Another way essentially
+   | relies on the detection of a system property, either matching a particular value for the property,
+   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
+   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
+   | Finally, the list of active profiles can be specified directly from the command line.
+   |
+   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
+   |       repositories, plugin repositories, and free-form properties to be used as configuration
+   |       variables for plugins in the POM.
+   |
+   |-->
+  <profiles>
+    <!-- profile
+     | Specifies a set of introductions to the build process, to be activated using one or more of the
+     | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
+     | or the command line, profiles have to have an ID that is unique.
+     |
+     | An encouraged best practice for profile identification is to use a consistent naming convention
+     | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
+     | This will make it more intuitive to understand what the set of introduced profiles is attempting
+     | to accomplish, particularly when you only have a list of profile id's for debug.
+     |
+     | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
+    <profile>
+      <id>jdk-1.4</id>
+
+      <activation>
+        <jdk>1.4</jdk>
+      </activation>
+
+      <repositories>
+        <repository>
+          <id>jdk14</id>
+          <name>Repository for JDK 1.4 builds</name>
+          <url>http://www.myhost.com/maven/jdk14</url>
+          <layout>default</layout>
+          <snapshotPolicy>always</snapshotPolicy>
+        </repository>
+      </repositories>
+    </profile>
+    -->
+
+    <!--
+     | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
+     | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
+     | might hypothetically look like:
+     |
+     | ...
+     | <plugin>
+     |   <groupId>org.myco.myplugins</groupId>
+     |   <artifactId>myplugin</artifactId>
+     |
+     |   <configuration>
+     |     <tomcatLocation>${tomcatPath}</tomcatLocation>
+     |   </configuration>
+     | </plugin>
+     | ...
+     |
+     | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
+     |       anything, you could just leave off the <value/> inside the activation-property.
+     |
+    <profile>
+      <id>env-dev</id>
+
+      <activation>
+        <property>
+          <name>target-env</name>
+          <value>dev</value>
+        </property>
+      </activation>
+
+      <properties>
+        <tomcatPath>/path/to/tomcat/instance</tomcatPath>
+      </properties>
+    </profile>
+    -->
+  </profiles>
+
+  <!-- activeProfiles
+   | List of profiles that are active for all builds.
+   |
+  <activeProfiles>
+    <activeProfile>alwaysActiveProfile</activeProfile>
+    <activeProfile>anotherAlwaysActiveProfile</activeProfile>
+  </activeProfiles>
+  -->
+</settings>