Before You Start¶
The Getting Started guides that follows leverages the standalone punchplatform. Make sure you get the latest one from our download area.
In minutes you will be able to run, operate, test and develop various use cases. The standalone punchplatform is also very useful in operation, coupled with your production platform, to run prototype or test setups either in sandbox mode or directly on the production traffic.
What you can not do is to go production with the standalone, that is not its purpose. For production, use the official deployment packages. They take care of properly installing the punchplatform components. The PunchPlatform team will provide production support only on versions installed using the official deployment packages.
At least 12 GB of RAM memory and 30 GB of free storage on your hard drive. In general, memory requirement will depend on the number, and the complexity of storm topologies/spark applications you will be running at a time (e.g. input and output channels, tenants, ...).
Below is a list of supported OS and required application to have before installing the standalone
- MacOS Sierra 10.12+
- Ubuntu 18.04 LTS+ (64 bits)
- Debian 7+ (64 bits)
- CentOS/RHEL 7+ (64 bits)
This chapter assumes you have already downloaded the standalone punchplatform archive from our download area.
Simply unzip it, you should have a
punchplatform-standalone-x.y.z directory on your filesystem.
Install the Standalone as a non-root user. I.e. use it under your standard user account. A troubleshooting procedure for the standalone is available at Troubleshooting your standalone
unzip punchplatform-standalone-x.y.z.zip cd punchplatform-standalone-x.y.z ./install.sh
This unarchives all our friends (Kafka, Storm, Elasticsearch, Spark etc...),
and patches their configuration files (cleanly) so that you have a simple local
punch setup. All Punch binary and configuration files will be installed
under this directory, nowhere else on your machine. When a prompt ask you to
patch your environment, if you answer "yes", it will only add a few
lines at the end of your
~/.bashrc (on linux) or
~/.bash_profile (on MacOS)
to update your path variable. You then only need to start a new terminal.
If you prefer not impacting your environment, just say no. To setup your environment you must then execute the following command every time you start a new terminal:
Useful commands to know¶
Setup your local environment:
Assuming you are happy with a local setup, you can start all of the standalone platform components (Zookeeper, Storm, Elasticsearch, Kibana, Spark).
Check if your standalone version is running properly:
Get a summary of your standalone UI urls: