Skip to content

ELLA-7.0.x release notes

This document is a summary of content, changes, limitations and fixes of this release as compared to DAVE-6.4 release

Refer to the the punchplatform official site if you look for the complete documentations and resources.

The documentation for this release can be found inside the deployment archives (standalone and deployer versions), and at https://doc.punchplatform.com/7.0.0/index.html.

The documentation for the most recent release can be found at https://doc.punchplatform.com.

Note about upgrades: Please carefully review the upgrade documentation for this release thoroughly before upgrading your clusters. The upgrade notes (e.g. upgrade from 6.4 to 7.0) discuss every critical information about incompatibilities and breaking changes, performance changes, and any other configuration changes that might impact your punch production deployment.

Changes

The 7.0 releases introduces major changes.

Kubernetes

Starting at 7.0 the punch runs natively on Kubernetes. The official kubernetes distribution is the thales kast 1.2.0 release.

Java 11

Java 11 or greater is now the required java runtime. The release is tested with openjdk64-11.0.9.1.

Spark3

Spark and pyspark punchlines require a spark3 release. Spark standalone cluter is not supported on production environment, the punch only leverage the kubernetes spark mode.

Elasticsearch

Elasticsearch is only supported in the opendistro open source release. Elastic releases are not supported anymore.

Hadoop Elasticsearch

Note also that the hadoop elasticsearch connectors have been deprectaed as well. This means that the elasticsearch spark nodes and storm spout have both been removed. The punch still provide its own (hadoop elasticsearch free) implementations.

YAML format

All configuration files are provided only using the yaml format. JSON and HJSON are only supported for bacward compatibility. Make sure you progressively migrate to yaml files only.

The punch provides a tool hjson-manager that automatically converts hjson or json to yaml:

cat some-file.hjson | hjson-manager --yaml

Plans

Plans can now run any kind of application:

planctl start \
  --runtime user_defined \
  --plan plan.hjson \
  --template template.hjson \
  --user-defined argument1 \
  --user-defined argument2

Deprecation

  • storm cluster: The storm cluster mode is deprecated. It is only supported for migration purpose. The storm single process mode is still supported, and has been renamed 'punch' as it is implemented on top of a proprietary punch engine.
  • shiva : the shiva orchestrator is supported on the 7.0.0 but is marked for depreciation. It will be fully replaced by kubernetes starting at 8.0 and greater.

Configuration Changes

Settings Name Changes

Some settings have been renamed. Old names are still supported for backward compatibility.

6.x settings name Equivalent 7.x settings name
channel_structure.application[].shiva_runner_tags channel_structure.application[].tags

Settings Value Changes

Some settings values been changed or support new value. Old values are still supported for backward compatibility.

Settings 6.x value(s) 7.x equivalent value(s)
punchline.runtime storm punch
channel_structure.application[].runtime shiva shiva OR kubernetes

Channel Structure

The 7.0 channel structure only supports the shiva and kubernetes target runtime.

`yaml version: '7.0' start_by_tenant: false stop_by_tenant: true applications: - name: flight runtime: shiva command: punchlinectl args: - start - --punchline - flight_punchline.yml tags: - common cluster: common reload_action: kill_then_start