[hono-dev] Eclipse Hono 1.1.0-M2 Milestone

["Hudalla Kai (IOC/PAP-HU)" <Kai.Hudalla@xxxxxxxx>]

Dear Hono community,

today we have created version 1.1.0 milestone 2 of the Eclipse Hono [1]
project.

Hono aims at providing uniform service interfaces for connecting large
numbers of IoT devices to a (cloud) back end. It specifically supports
scalable and secure data ingestion (telemetry data & events) and also
supports sending messages to devices.

Here are the release notes for the changes and improvements since 1.0.3
which are contained in this milestone:

New Features

* The Sigfox and LoRaWAN adapters now report metrics analogously
  to the other protocol adapters.
* With the release of Eclipse Californium 2.0.0, the CoAP adapter
  became an official part of the Hono release. The adapter also
  supports tracking of request processing using OpenTracing but
  is still considered "experimental".
* A lorawan provider has been added for the "loriot" network provider.
* Hono's protocol adapters now support Server Name Indication in order
  to allow devices to establish a TLS connection with adapters using
  a tenant specific server certificate and host name.
  Please refer to the "Secure Communication" admin guide for details.
* Hono now supports "auto-provisioning" of devices that authenticate
  with X.509 client certificates. For more information please refer
  to the Device Provisioning concept and for details to the
  Tenant and the Credentials API.
* The Hono Auth Server and Device Registry components now support
  configuring the SASL mechanisms advertised to a client connecting
  to these components. This can be used to restrict the support to
  only one of the SASL PLAIN and EXTERNAL mechanisms instead of both.

Fixes & Enhancements

* Hono's Helm chart now supports configuring resource requests and
  limits of the container images.
* The MQTT adapter now includes a device's MQTT client ID in its request
  to retrieve the device's credentials. This additional information can
  be used by device registry implementations when determining the
  device identity.
* The domain name of the Hono Sandbox has been changed to
  "hono.eclipseprojects.io".
  It will still be available at the old domain name for some time as
  well, though.
* Hono's OpenTracing instrumentation has been upgraded to Opentracing
  0.33.0. The example deployment now uses the Jaeger Java client in
  version 0.35.2 and the Jaeger 1.16 agent and back end components.

Binary artifacts are available from the Eclipse Repository [4] and from
Maven Central [5].

However, the easiest and also the preferred way of using Hono is by
means of Docker images available from Docker Hub [6]. A Helm chart for
deploying Hono to Kubernetes or OpenShift is available from the download
page [7].

If you want to give Hono a try, please follow the Getting Started guide
on the project web site [8].

Please refer to the project page at Eclipse [9] for Hono's release plan.

[1] https://www.eclipse.org/hono
[4] https://repo.eclipse.org/content/groups/hono/
[5] https://search.maven.org/search?q=g:org.eclipse.hono
[6] https://hub.docker.com/u/eclipse/
[7] https://www.eclipse.org/hono/download/
[8] https://www.eclipse.org/hono/getting-started/
[9] https://projects.eclipse.org/projects/iot.hono/governance

-- 
Mit freundlichen Grüßen / Best regards

Kai Hudalla

Software Developer - Bosch IoT Hub

Bosch.IO GmbH
Ullsteinstr. 128
12109 Berlin
GERMANY
www.bosch.io

Registered Office: Berlin, Registration Court: Amtsgericht
Charlottenburg; HRB 148411 B
Chairman of the Supervisory Board: Dr.-Ing. Thorsten Lücke;
Managing Directors: Dr. Stefan Ferber, Dr. Aleksandar Mitrovic, Yvonne
Reckling