...
Squirro is built as a service-oriented platform. All services work as self-contained units of functionality and therefore are suited for different scenarios. Squirro can match small but also complex and large-scale requirements. All Squirro services communicate via RESTful API. The Squirro API is open and allows for 3rd party integration for all services and functionality.
...
All non-Squirro components are open source components.
Component | Function | High Availability |
---|---|---|
Squirro Application (see Services for details) |
| yes |
Elasticsearch |
| yes |
MySQL |
| yes |
Redis Cache |
| yes |
Squirro Python SDK |
| n/a |
Squirro Toolbox |
| n/a |
Squirro YUM Repository |
| n/a |
Squirro Puppet Configuration |
|
Versions
Squirro supports 2 two different types of deployments - cloud and on-premise. Updating installations in the cloud is done by the Squirro staff, based on individual agreements with the customer. With For on-premise deployments, the upgrade process is driven by the customer directly.
Please see the Release Notes section for details about individual releases or reach out to Squirro Support about scheduled upcoming release dates.
...
Squirro supports the following 2 standardized two standardised platforms.
Platform | Version | Comments |
---|---|---|
Cloud | n/a | A separate cloud is generally set up for each customer, to isolate the different installations. Squirro generally works with Amazon Web Services for cloud deployments. But other cloud services are supported on demand. |
Linux | Red Hat® and CentOS. See System Requirements for details. |
|
With the cloud version all the administration is done by Squirro's staff. This Administration Guide is thus only needed for targets customers and partners who maintain their on-premise deployments , where partners or customers take over these responsibilitiesof Squirro.