eKuiper is a lightweight IoT edge analytics software.

This is a snap packaging of eKuiper tailored to the EdgeX Foundry snap, available at: https://snapcraft.io/edgexfoundry

The snap is designed to work with EdgeX and is not supported for standalone use.

The snap is NOT SUPPORTED by the eKuiper community. For any EdgeX-related issues when using this snap, please refer to: https://github.com/canonical/edgex-ekuiper-snap

eKuiper source code: https://github.com/lf-edge/ekuiper

eKuiper is a trademark of LF Projects: https://lfprojects.org

The snap is built automatically and published on the Snap Store as edgex-ekuiper.

Please refer to the edgex-ekuiper snap store listing for installation and releases.

The eKuiper service does not start after installation; see configuration.

This snap works together with several other EdgeX services.

Please refer to EdgeX Getting Started for setting up the platform using snaps.

The eKuiper service connects to Redis and subscribes to events. By default, the connection needs authentication.

When this snap is installed together with the edgexfoundry snap, it will use the edgex-secretstore-token content interface to receive a Vault token for an addon-service named edgex-ekuiper.

Note
The edgexfoundry 2.2.0-dev.32 or later is configured to issue the token automatically; see PR #3888. This version is currently available in latest/beta channel.

For versions prior to this, the edgex-ekuiper add-on service with redisdb known secret token can be added by configuration. Please refer to Configuring Add-on Services and edgexfoundry snap readme for details.

The token is expected at /var/snap/edgex-ekuiper/current/edgex-ekuiper/secrets-token.json and may be supplied via other means.

This snap uses the Vault token to query Redis credentials from Vault. It then injects the credentials into relevant eKuiper config files.

If the token is not available, the service will exit with error and restart automatically.

Option
To disable the Vault token requirement and skip credentials query and config injection, set the following option:

sudo snap set edgex-ekuiper config.edgex-security-secret-store=false

This option is experimental and subject to change without notice.

eKuiper subscribes to all EdgeX events by default. The default configuration expects that events are published to the EdgeX message bus under edgex/events/# topic.

To enable filtering using the app-service-configurable snap, please refer to Work with App Service Configurable filtering details below.

The default setup described above will prepare the system such that:

• edgex-ekuiper is inactive and disabled
• edgexfoundry.kuiper and edgexfoundry.app-service-configurable are inactive and disabled - these are deprecated and embedded versions of eKuiper and App Service Configurable which we do not use here.
• edgexfoundry's vault and redis, along with other core services are active and enabled

Verify that by executing the following command:

$ sudo snap services edgex-ekuiper edgexfoundry
Service                                                  Startup   Current   Notes
edgex-ekuiper.kuiperd                                    disabled  inactive    -
edgexfoundry.app-service-configurable                    disabled  inactive  -
edgexfoundry.consul                                      enabled   active    -
edgexfoundry.core-command                                enabled   active    -
edgexfoundry.core-data                                   enabled   active    -
edgexfoundry.core-metadata                               enabled   active    -
edgexfoundry.device-virtual                              disabled  inactive  -
edgexfoundry.kong-daemon                                 enabled   active    -
edgexfoundry.kuiper                                      disabled  inactive  -
edgexfoundry.postgres                                    enabled   active    -
edgexfoundry.redis                                       enabled   active    -
edgexfoundry.security-bootstrapper-redis                 enabled   inactive  -
edgexfoundry.security-consul-bootstrapper                enabled   inactive  -
edgexfoundry.security-proxy-setup                        enabled   inactive  -
edgexfoundry.security-secretstore-setup                  enabled   inactive  -
edgexfoundry.support-notifications                       disabled  inactive  -
edgexfoundry.support-scheduler                           disabled  inactive  -
edgexfoundry.sys-mgmt-agent                              disabled  inactive  -
edgexfoundry.vault                                       enabled   active    -

To change the default configuration, refer below.

The eKuiper service is stopped and disabled by default after installation. This is to allow configuration (see below) before running the service for the first time.

The service can be started as follows. The --enable option ensures that as well as starting the service now, it will be automatically started on boot:

sudo snap start --enable edgex-ekuiper

Conversely, the service can be stopped and disabled as follows:

sudo snap stop --disable edgex-ekuiper

To restart a running instance and load new configurations:

sudo snap restart edgex-ekuiper

The basic server configuration file for eKuiper is at /var/snap/edgex-ekuiper/current/etc/kuiper.yaml. For details, please refer to this eKuiper document.

The /var/snap/edgex-ekuiper/current/etc directory contains the configuration files of eKuiper. These include the basic server configuration, as well as configurations such as for sources, sinks, and connections.

The Snap provides an interface to set environment variables for the eKuiper Daemon.

Example

# enable eKuiper's debug mode
snap set edgex-ekuiper config.kuiper.basic.debug=true

# change EdgeX's default port
snap set edgex-ekuiper config.edgex.default.port=1111

snap restart edgex-ekuiper

For more details on Snap options, please refer to EdgeX config overrides documentation. To learn more about the supported environment variables, please consult the eKuiper configuration documentation.

Instead of subscribing to all EdgeX events, eKuiper can be configured to subscribe to events filtered by EdgeX App Service Configurable.

To do so, install edgex-app-service-configurable, and set its profile to rules-engine:

snap install edgex-app-service-configurable
snap set edgex-app-service-configurable profile=rules-engine
snap start edgex-app-service-configurable

Then, set eKuiper to subscribe to app-service-configurable by changing the edgex default topic to rules-event and messageType to event:

snap set edgex-ekuiper config.edgex.default.topic=rules-events config.edgex.default.messagetype=event
# restart is required to load new configuration options
snap restart edgex-ekuiper

Unsetting the above changes will revert ekuiper to default settings (subscribe to all EdgeX events):

snap unset edgex-ekuiper config.edgex.default.topic config.edgex.default.messagetype
# restart is required to load new configuration options
snap restart edgex-ekuiper

edgex-ekuiper snap has a content interface that allows a provider snap to seed it with configuration files. Upon a connection between these two snaps, the packaged config files get mounted inside edgex-ekuiper snap, to be used by kuiper service.

Here is an example of the ekuiper-data slot from a provider:

slots:
  ekuiper-data:
    interface: content
    source:
      write: [$SNAP_DATA/data]

where:

• write: [$SNAP_DATA/data] exposes a directory beneath the writable $SNAP_DATA to consumer edgex-ekuiper snap. The directory needs to be writable because edgex-ekuiper adds other files inside it during ruleset provisioning. In order to place configuration files beneath $SNAP_DATA, the provider needs to contain an install hook or a service which deploys the ruleset after installation.
• data directory is a required for ruleset provision

To connect the provider to edgex-ekuiper:

snap connect edgex-ekuiper:ekuiper-data <config-provider>:ekuiper-data

Note that the connection needs to happen before starting eKuiper for the first time.

Please refer to edgex-config-provider for mode details.

For example, to print 100 lines and follow the logs:

snap logs -n=100 -f edgex-ekuiper

Execute the following command from the top-level directory of this repo:

snapcraft

This will create a snap package file with .snap extension. It can be installed locally by setting the --dangerous flag:

sudo snap install --dangerous <snap-file>

The snapcraft overview provides additional details.

The edgex-secretstore-token snap slot makes it possible to automatically receive a token from a locally installed platform snap.

If the snap is built and installed locally, the interface will not auto-connect. You can check the status of the connections by running the snap connections edgex-ekuiper command.

To manually connect and obtain a token:

sudo snap connect edgexfoundry:edgex-secretstore-token edgex-ekuiper:edgex-secretstore-token

Please refer here for further information.

This repository is tagged after the eKuiper project with a semver build metadata snap suffix. For example, if eKuiper is tagged as 1.4.3, this repository will be tagged as 1.4.3+snap, 1.4.3+snap.2, 1.4.3+snap.N. The build version increments indicate updates to the snap packaging on top of the same eKuiper release.

The release Github workflow can be used to manually tag and release, enforcing the above schema.