Feb 10, 2017
by Siddharth Krishna
Want to install StackStorm on a machine that doesn’t have access to the internet? If you’ve got another box on your local network that connects to the public network, you can do this by making it a local package repository server. In this post, we’ll walk you through steps for setting up an apt-mirror server with the required packages and configuring the offline client machine to quickly get a full StackStorm installation up and running!
Note: We are using Ubuntu on the mirror server and therefore going with apt-mirror in the example here. You can build a local Yum repository in case you are running RHEL/CentOS.
1) Let’s assume that you already have an apt-mirror server with packages for an Ubuntu distribution in place: see an example guide here. As part of this, you would need to install the apache web server as well. It’s used to make the repositories accessible from the client machine (ST2 installation target) over HTTP.
2) The following packages should be made available on the local package repository for a complete installation of StackStorm (including Web UI, Chatops etc.):
Add the custom repository URL details for these packages to the apt mirror.list file on the server.
sudo vi /etc/apt/mirror.list .. deb https://packagecloud.io/StackStorm/stable/ubuntu/ trusty main deb http://repo.mongodb.org/apt/ubuntu trusty/mongodb-org/3.2 multiverse deb https://deb.nodesource.com/node_6.x trusty main deb http://nginx.org/packages/ubuntu/ trusty nginx deb-src https://packagecloud.io/StackStorm/stable/ubuntu/ trusty main ..
3) Update the mirror to download the required packages on the local mirror:
Directories for each of the new packages should get created inside the apt-mirror base path (
/aptmirror/mirror/packagecloud.io/StackStorm/stable/ubuntu/ /aptmirror/mirror/repo.mongodb.org/apt/ubuntu/ /aptmirror/mirror/deb.nodesource.com/node_6.x/ /aptmirror/mirror/nginx.org/packages/ubuntu/
4) Configure the webserver on the local mirror to make the repositories accessible over HTTP from the client machine by creating symbolic links to each of the repos in the
[email protected]:/var/www/html$ ls -l total 0 lrwxrwxrwx 1 root root 46 Jan 9 04:29 mongodb -> /aptmirror/mirror/repo.mongodb.org/apt/ubuntu/ lrwxrwxrwx 1 root root 44 Jan 10 02:30 nginx -> /aptmirror/mirror/nginx.org/packages/ubuntu/ lrwxrwxrwx 1 root root 46 Jan 9 04:29 nodejs -> /aptmirror/mirror/deb.nodesource.com/node_6.x/ lrwxrwxrwx 1 root root 47 Jan 9 04:29 st2 -> /aptmirror/mirror/packagecloud.io/StackStorm/stable/ubuntu/ lrwxrwxrwx 1 root root 44 Jan 9 02:44 ubuntu -> /aptmirror/mirror/archive.ubuntu.com/ubuntu/
Restart the web server:
sudo service apache2 restart
Verify the repository directory structure in web browser:
5) Modify apt sources to point to the local mirror server for all packages – Ubuntu, ST2, MongoDb, NodeJS and Nginx. Replace
mirror with the hostname or IP of the local mirror server:
sudo vi /etc/apt/sources.list
Comment out (#) all existing content and replace with the following:
deb http://mirror/ubuntu/ trusty main restricted universe multiverse deb http://mirror/ubuntu/ trusty-security main restricted universe multiverse deb http://mirror/ubuntu/ trusty-updates main restricted universe multiverse deb http://mirror/st2 trusty_stable main deb http://mirror/mongodb/ trusty/mongodb-org/3.2 multiverse deb http://mirror/nodejs trusty main deb http://mirror/nginx trusty nginx
Update package information:
sudo apt-get update
At this point you might hit some GPG signing errors for the custom packages on the client:
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY
To fix this, do the following:
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv sudo apt-key export > exportedkey
Move the exportedkey file to the client.
Note: In case you are facing errors for multiple keys, you may use the following instead:
sudo apt-key exportall > exportedkey(s)
sudo apt-key add exportedkey(s)
6) All required packages should now be downloadable from the local mirror server using
sudo apt-get install –y command. The one-line installation process won’t work for this system. You’ll need to follow the manual install steps documented here. Or better yet, use something like Ansible to configure your system. Note that you do not need to setup any custom repositories on the client system. We have already done this by pointing apt towards the local repository server. Install the dependencies directly using
sudo apt-get install –y st2|st2mistral|mongodb|nginx|nodejs|st2chatops instead.
You should now have StackStorm running. Verify the installation. Since its in offline system, the usual pack install process won’t work on it. One of the ways of working around this is to use an HTTP proxy. In a follow-up blog I’ll show you how to set that up.