Read below the various Eskimo Version release notes
What's new in Eskimo-CE v0.2
Released on Dec 30, 2019
What's new ?
SSH Tunnels to reach Services Web UIs. From the eskimo main console, instead of reaching the various Web Graphical
User Interfaces of the various services such as Mesos Console, Spark History Server, Kafka Manager, Cerebro, Kibana, etc.
using direct accesses to the nodes and ports where these services are running, the new approach consists in letting eskimo
manage SSH tunnels to reach these services wherever they are located and let the iframes within Eskimo's own UI reach
these services through these SSH tunnels using proper HTTP Proxying from the Eskimo Backend.
This enables a much tighter control on the ports to be opened on individual nodes and prevents from the need
to open access from administrators machines to the internal Eskimo cluster nodes.
It also enables a much tighter integration between service web consoles and Eskimo itself.
Revamped Status Page.
The Nodes Status Page is now a Cluster Status Page that provides general health information and statistics
about the cluster the whole cluster. The services action menu has been reimplemented in a clearer way (just click on a
service status to have access to the action menu)
Download of images from eskimo.sh.
Service Images and Packages can be downloaded from eskimo.sh. It is not anymore mandatory to build them locally with
each and every Eskimo installation. Images and Packages are properly versionned and the system supports checking for
updates and fetching new images when they are available.
Support for Microsoft Windows as execution OS for Eskimo backend.
With the ability to download pre-built services packages (docker images) from eskimo.sh now implemented, Microsoft Windows
is now fully supported as execution middleware for the Eskimo backend (not the cluster nodes though, a supported
Linux distribution is required on the eskimo cluster nodes).
Running on windows however makes it mandatory to download pre-built packages from a remote repository (any one). Building images
directly from within the Eskimo User Interface is only supported when the backend Operating System is Linux.
Logstash is available from zeppelin container.
If Logstash is installed, it is made available to the Zeppelin container using a command client reaching a command
server from the logstash container.
Mesos Management Command Line utility.
A mesos-cli command line is available from every node of the cluster to administer the mesos cluster and address missing
features from mesos command line utilities such as for instance the ability to kill a framework in a failsafe manner.
Suport for SUSE operation System.
The SUSE Operating System is now fully supported on cluster nodes in addition to Red-Hat based OSes (Fedora, CentOS, etc.)
and Debian based OSes (Debian, Ubuntu, etc.)
Collection of Zeppelin Demo Notebooks.
A comprehensive collection of demo notebooks for Zeppelin is now available.
These demo notebooks present for instance how to implement spark processes in batch and streaming mode, same for flink,
how to read from and write to ElasticSearch from Spark, how to read from and write to kafka from Spark and Flink, how
to use logstash to feed ElasticSearch, etc.
New Services Settings Edition Feature. It is now possible to edit common spark, flink, logstash, elasticsearch, kafka, etc.
configuration properties or settings from the UI and inject them in the service runtime (services are automatically restarted
with updated configuration when settings are saved).
Only pre-defined configuration properties are supported in Eskimo Community Edition. One needs to acquire the enterprise
edition to support defining every possible property or configuration file of every Eskimo pre-packages technology.
General improvement and bug corrections.
Much better management of SSH Connections and SSH terminals.
Much better support for different screen resolutions, especially lower screen resolutions.
Much better detection of services startup problems in SystemD unit configuration files.
Much better management of gluster shares. (A weakness remains on node unregistration when a node is removed from cluster.
This will be solved in 0.3)
Better handling of messaging and notifications in a multi-user environment.
Improvement of the user documentation.
Service Development framework improvement.
The Service development framework now supports both libvirt and Vagrant to build the various Apache Mesos distributions.
General UI Improvements.
The services in both the Nodes Status Page and the Services Configuration
Page are now accompanied with the respective product icons.
Services Version Update.
Apache Mesos upgraded to version 1.8.1
Apache Zeppelin upgraded to 0.9-SNAPSHOT (development version with fixes and workarounds for known bugs)
Services Integration. Following services are fully integrated and operable within Eskimo 0.2, with all the tuning, fixes and required wrappers.
Apache Flink 1.9.1
What's new in Eskimo-CE v0.1
Released on Jul 24, 2019
What's new ?
Docker Images Development Framework. The docker images development framework provides standards, principles and
tools to enable anyone to build his own service docker images to be installed and operated by Eskimo. The initial set of
Eskimo packaged services containers are implemented on top of this framework.
Services Installation Framework. The Services Installation framework is Eskimo's key feature enabling it to
install, configure, manage, operate, move and uninstall services (their docker containers) on node. It is based on
docker and a standard systemd approach for operation on nodes.
Master election and dependencies Management. Dependencies management between services and enforcement of
dependencies between services accross nodes. This enables an eskimo service developer to define it's service
dependencies in a configuration file and then let eskimo enforce these dependencies, handle order of installation, order
of services restart, restarting of dependent services after a service move to another node, etc.
This module also takes care of dependent services re-configuration when topology of dependencies evolve.
Initial Basic Memory Management Framework. This module computes the available memory on every node and uses the
memory requirement declaration of every service (configuration) to distribute a fair share of the available memory
on every node to every service the node is hosting.
Eskimo Platform Management User Interface. This is the intial version of the Eskimo Platform Management Console
Web Graphical User Interface which provides specific features, such as the SSH terminals, the nodes configuration page,
etc. as well as the embdedding of third party services User Interfaces within its own UI.
Eskimo Setup Page and Backend. The Eskimo Setup Page and Backend implements the initial setup of the Eskimo
Platform management console, where the SSH configuration used to reach the Eskimo Cluster nodes is defined as well as,
for instance, the way to find the Eskimo Managed Services Docker images (download or build).
Eskimo Nodes Configuration Page and Backend. This is the most important feature from eskimo: the page and backend
implementation of the nodes configuration, where the topolog of the cluster is defined by declaring the services to be
executed on every node of the cluster. Nodes can be configured as individual nodes or range of nodes (IP addresses).
This module takes care controls the dependencies enforcement and performes the installation, configuration,
uninstallation, etc. of services when the configuration is applied.
Eskimo Nodes Status Page< and Backend. This is the Eskimo Cluster main monitoring page where the topology of the
cluster is presented and monitored and where individual services states can be monitored. Actions on individual services
can be carried on from there.
Eskimo Backend Messages Page and Backend. Messaging and monitoring feature when there are operations in progress
(installation, configuration, uninstallation, etc.) on the backend. This included support for multi-user environment
when another administrator triggered some operations to have all connected operators notified.
Eskimo Web-based SSH Terminals Feature. Eskimo SSH terminals feature, just as a plain old SSH terminal but within
a web page. Eskimo enables administrators to open SSH terminals on cluster nodes directly from within the Eskimo Web GUI.
Eskimo Web-based SFTP Terminals Features. Web based file manager using SFTP to connect on cluster nodes. Just as
a plain old file manager with file visualization but from within the Eskimo Web GUI.
Support for Debian-based and Red-Hat-based Linux nodes. Support for Debian-based and Red-Hat-based Operating
systems on Eskimo cluster nodes (Debian, Ubuntu, Red-Hat, Fedora and CentOS for now).
Basic authentication and authorization and login page. Authentication and Authorization framework. For now
authorization are quite trivial and authentication is based on local file system user file. This shall evolve with
further versions of Eskimo.
Eskimo EE offers impersonation of system users when executing commands (includign File Manager and SSH terminal).
Eskimo CE executes everything as default user.
Gluster FS volumes and mounts management framework. System-wide management of Gluster shares and mounts for
services requiring such shared folders such as Spark, Zeppelin, etc.
Services Integration. Following services are fully integrated and operable within Eskimo 0.1, with all the tuning, fixes and required wrappers.