Is there an “on prem” version of Kraken?
Yes. There are two different ways that you can deploy Kraken on premises: either in a Virtual Private Cloud (VPC) or on a server physically residing on premises. Unlike Big Squid’s cloud-hosted version of Kraken, deploying Kraken on premises is hosted and controlled by your team.Big Squid provides an automated installation method as well as regular product updates. Kraken on-premises is designed to provide customers who have strict regulatory, compliance and/or privacy requirements with a version of Kraken they can easily manage.
What is the Kraken on-premises installation like?
Installing Kraken on-premises is an easy single-command installation process (via shell script) which will detect your operating system, ask a few questions, then install Kraken and any required dependent software.This process is dictated by a license file we provide you. You’ll then access your private instance of the Kraken administration panel on port 8800 at the address provided in the console log (a reachable IP address from your network). A straightforward UI will then guide you through the installation and configuration process. A host domain and an SSL certificate for configuring HTTPS communication is also required. The installation process will install the required version of Docker (see question #4, below, for specific details) if Docker is not currently installed.
What server configuration do I need? Will this change as the platform evolves?
We provide standard guidelines on hardware requirements, though the specific requirements of any customer are dependent on the intended use and how much data will be processed. The baseline requirements are:
- 1 TB disk space
- Access to one of the following authentication methods:
- Microsoft Active Directory
- Open LDAP
- 389 DS
- Free IPA
- A host domain (e.g. example.mycompany.com) and SSL certificates that can be generated/used for that domain
- SSL full chain certificate in .PEM format
- SSL private key in .PEM format
These requirements may change based on updates to the Kraken platform as well as changes to how an individual organization evolves and scales its use of Kraken. The requirements above would generally support a small team of active Kraken users. Any updates to the Kraken platform that necessitate hardware upgrades will be communicated well in advance so that you may prepare for them.
What software do I need running on my Kraken server? Does Kraken require a dedicated machine?
Supported operating systems include 64-bit distribution Linux-based servers that support docker-engine 18.09.2-ce. The minimum kernel version is 3.10. Examples include:
- Debian 7.7+
- Ubuntu 14.04.5 / 16.04 / 18.04
- Hat Enterprise Linux 7+
- CentOS 7+
- Linux 7+
Note: Kraken installations on Windows Server are not supported at this time. We do, however, support running Kraken in a Linux-based VM hosted on Windows Server.While Kraken does not require a dedicated machine, Big Squid STRONGLY recommends a dedicated machine; this ensures that Kraken has its own computing resources and this will optimize prediction processing time and minimize conflicts.
What do I need from my side to perform the install?
Typically, a SysAdmin or member of IT accustomed to performing software installations for your organization is the right resource to install Kraken. The installation process takes less than one hour.
Are there other requirements to install Kraken on premises?
There are no other defined requirements. If you require an air-gapped installation (i.e. no outbound Internet access) there will be more manual steps for configuring your environment for Kraken. Big Squid will provide guidance as required in these configurations.
How does Big Squid communicate new releases of Kraken on premises? How and when do I upgrade?
Kraken provides channel management to allow your organization to control when (and how often) you upgrade Kraken. Release notes are provided for every release/update with details on the additions and fixes included. Mandatory release updates will be communicated well in advance to allow you time to prepare for the update.
What are the support options for Kraken on premises? How do we report an issue or problem with the software?
Big Squid provides various support options, depending on the needs of your organization. For support issues that require Kraken log files and other data, you can upload and share support bundles containing all the log files associated with your on-premise instance for Big Squid Support to review. This can help our support team address many common issues that arise without any access to your environment. Before sharing the support bundle with our team, you’ll need to inspect it to ensure that there is no proprietary or secret data included (databases are not included, but this does have some syslog outputs included).
Do you have monitoring in place to monitor the health of the platform? Does Big Squid support user questions/complaints, or does our IT team?
No data about Kraken usage is sent back to Big Squid. Your IT department should have monitoring in place to monitor the health of your on prem environmentYour IT department should be contacted for issues related to network connectivity, user access, etc. Support requests for general bugs and other Kraken issues can be submitted at https://support.bigsquid.com. For more detailed issues with Kraken, your Kraken admin (the team that installed Kraken and has access to the admin console) can generate support bundles from the 'Support' tab. The support bundle can be sent to Big Squid customer support for further analysis. General feedback and feature requests can be submitted from the customer feedback portal
What is the difference in functionality between Kraken “in the cloud” and Kraken on premises?
The following article outlines the current differences in functionality: