Introduction
The infinit.e-platform.prerequisites.online and .offline RPMS contains a collection of packages, data files, and scripts that are necessary to prepare a clean CentOS 5.6/6+ or Red Hat Enterprise Linux 5.5/6+ server for the installation of IKANOW's Infinit.e.
There are two types of installation mode supported by infinit.e-platform.prerequisites:
- Online
i{*}nfinit infinit.e-platform.prerequisites.online - * The Online installation is for target machines that have an active connection to the internet that allows YUM to retrieve the latest version of packages required for the installation. - Offline
infinit infinit.e-platform.prerequisites.offline - * The Offline installation is for target machines that *that are not connected not connected to the internet. When the installation script (install.sh) is run YUM is pointed to the /mnt/opt/infinit.einfinite-install/rpms directory where the required RPMs and their dependencies are located.
...
The installation mode and node type can be specified during installation via the use of command line arguments (see Running install.sh below).
Note: The following is a list of packages installed on the target machine based on the type of node being installed:
...
...
API Node
...
DB Node
...
Createrepo
...
X
...
X
...
Jpackage-utils
...
X
...
X
...
yum-priorities
...
X
...
X
...
s3cmd
...
X
...
X
...
Java
...
X
...
X
...
Tomcat 6
...
X
...
X
...
Splunk
...
X
...
X
...
MongoDB
...
X
...
X
...
Elasticsearch
...
X
...
X
...
Curl
...
X
...
X
...
Hadoop
...
X
...
...
Hue
...
X
1. Installation of the RPM
| Info |
|---|
Note that the install bundles on the IKANOW downloads page contain a single script that will install all required RPMs, both in online and offline modes. These "quick install"s are described here. |
1. Installation of the RPM
To install from the Ikanow repo, simply run:
| Code Block |
|---|
yum install infinit.e-platform.prerequisites.online
|
For offline installs:
Once infinit.e-platform.prerequisites RPM has been copied to the target machine execute the following command (assuming that you are within the same directory in which the RPM is located):
| Code Block |
|---|
yum rpmlocalinstall -i infinitinfinit.e-platform.prerequisites.online-localBuild*.0-0.noarch.rpm |
or:
| Code Block |
|---|
rpm -i infinitrpm --nogpgcheck OR yum --disablerepo=* localinstall infinit.e-platform.prerequisites.offline-localBuild.0-0.noarch*.rpm --nogpgcheck |
depending on the type of install.
Note that in the offline case all existing yum repositories are removed so that yum does not try to go out over the Internet to fetch dependencies. Running the offline install script (below) will then create a single local repository ("infinite").
2. Running install.sh
The RPM will unpack all of the files required to complete the installation into the following directory:
| Code Block |
|---|
/mnt/opt/infinit.einfinite-install |
...
infinit.e-platform.prerequisites copies the online_install.sh or offline_install.sh script from following directory on the target machine:
| Code Block |
|---|
/mnt/opt/infinit.einfinite-install/scripts |
to the current user's root directory and renames it install.sh, e.g. :
| Code Block |
|---|
~/mnt/opt/infinit.e-install/install.sh |
If you are not already in you root directory type the following command within terminal:
| Code Block |
|---|
cd ~ cd /mnt/opt/infinite-install/ |
API Node
By default install.sh will create an API Nodewhen Node with all the latest RPMs when you type the following command.
| Code Block |
|---|
sh install.sh
|
Alternatively you could explicitly pass the install mode and node type arguments as shown below.
| Code Block |
|---|
sh install.sh apinode_latest #to fix to a specific Infinit.e version, append "_v<major>.<minor>" to the node type, eg: sh install.sh apinode _v0.2 |
The Infinit.e version to major (non-backwards compatible) elasticsearch version is as follows:
- apinode_latest: 1.0
- apinode_v0.3: 1.0
- apinode_v0.2: 0.19
- apinode_v0.1: 0.19
- (v0.0 no longer supported: 0.18)
(For legacy reasons, "apinode" defaults to "apinode_v0.2")
DB Node
To install a DB Node type:
| Code Block |
|---|
sh install.sh dbnode_latest #to fix to a specific Infinit.e version, append "_v<major>.<minor>" to the node type, eg: sh install.sh dbnode dbnode_v0.2 |
The Infinit.e version to major (non-backwards compatible) MongoDB version is as follows:
- dbnode_latest: 2.4
- dbnode_v0.3: 2.4
- dbnode_v0.2: 2.4
- dbnode_v0.1: 2.2
- (Supported in online mode only - for offline mode you need to download and install the RPM by hand, eg "yumdownloader mongo-10gen-server-2.2.3 mongo-10gen-2.2.3", transfer the 2 RPMs and then use "rpm -i" on the target machine)
- (v0.0 no longer supported: 2.0)
- (unlike elasticsearch 0.18, mongodb 2.0 is still compatible with the Infinit.e application layer, but it cannot be installed and is not recommended)
(For legacy reasons "dbnode" defaults to "dbnode_v0.2")
3. Configuring the Node via the infinite.configuration.properties.TEMPLATE File
When the install.sh script has completed running you should see the following message:
| Code Block |
|---|
################################################################################ IMPORTANT: Copy /mnt/opt/infinit.einfinite-install/config/infinite.configuration.properties.TEMPLATE to /mnt/opt/infinit.einfinite-install/config/infinite.configuration.properties and edit the properties contained within the file to match your deployment environment. ################################################################################ |
Follow the instructions above before continuing with the next steps of the Infinit.e installation, e.g.:
| Code Block |
|---|
> cp /mnt/opt/infinite-install/config/infinite.configuration.properties.TEMPLATE.STANDALONE /mnt/opt/infinite-install/config/infinite.configuration.properties
or
> cp /mnt/opt/infinite-install/config/infinite.configuration.properties.TEMPLATE.AWS /mnt/opt/infinite-install/config/infinite.configuration.properties
> vi /mnt/opt/infinite-install/config/infinite.configuration.properties |
Note: See Appendix B - infinite.configuration.properties.TEMPLATE (STANDALONE and AWS) for more information on editing the infinite.configuration.properties file. The github templates may be found here (AWS) and here (standalone).