| [hono-dev] Eclipse Hono 0.5-M7 Milestone |
|
Hi, today we have created version 0.5 milestone 7 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 will also support sending
messages to devices either one-way or request-response. This milestone includes the following new features:
-
The metrics reported by Hono are now processed in InfluxDB by means of templates which parse some of the information contained in the keys into and InfluxDB tags.
Consequently, the Grafana dashboard now correctly displays (aggregated) metrics reported by multiple Hono Messaging instances and provides means to filter metrics per tenant.
-
The Hono Messaging, Device Registry, REST and MQTT Adapter components now expose meaningful health checks via HTTP which can be used by container orchestration tools like Kuberetes to e.g. determine a component’s readiness to serve requests. Configuration Changes:
-
The Device Registry and Auth Server components will support the configuration of API endpoints employing other transport protocols than AMQP in the future. In preparation for that, the environment variable names for configuring these
components have been adapted accordingly.
-
Metrics default for the prefix in the Graphite reporter is now the component’s host name.
-
The Docker images for Hono’s components do no longer contain demo keys and certificates. The keys, certificates and configuration data are now provided to containers during deployment by means of Docker and/or Kubernetes Secrets. Consequently,
Hono does no longer provide its custom Dispatch Router Docker image but instead uses the standard image provided by the enmasse project.
-
No longer use a Docker Compose file for deploying to Docker Swarm. Instead, we now use a shell script which runs multiple Docker Swarm commands for deploying Hono. This approach provides for more flexibility and is more consistent with
the approach already taken for the deployment to Kubernetes/Openshift. You can find a list of issues addressed here [2]. We anticipate to do a first release (0.5) supporting scalable ingestions of telemetry data and events in Q3 2017. The artifacts are available from Eclipse Repo [3] and (later during the day) from Maven Central [4]. However, the easiest and also the preferred way of using Hono is by means of Docker images available from Docker Hub [5]. If you want to give Hono a try, follow the Getting Started guide on the project web site [6]. [1] https://www.eclipse.org/hono [2]
https://github.com/eclipse/hono/milestone/7?closed=1 [3]
https://repo.eclipse.org/content/groups/hono/ [4]
http://search.maven.org/#search%7Cga%7C1%7Chono [5] https://hub.docker.com/u/eclipsehono/ [6]
https://www.eclipse.org/hono/getting-started/ [7]
https://www.eclipse.org/hono/release-notes/ Mit freundlichen Grüßen / Best regards Karsten Frank Senior Software Developer Bosch Software Innovations GmbH Schöneberger Ufer 89-91 10785 Berlin GERMANY Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B; Executives: Dr.-Ing. Rainer Kallenbach, Michael |