Skip to main content

The Eclipse IoT MQTT Sandbox Is On the Move!

For many years, the Eclipse Foundation has offered an MQTT sandbox to the IoT developer community. That sandbox was maintained by Foundation staff and was running on Foundation infrastructure. The goal was to encourage and facilitate the evaluation of Eclipse Paho and Eclipse Mosquitto, and to foster interoperability among MQTT implementations. Today, I have the pleasure to announce the deployment of a new community-run MQTT sandbox to replace it.

What will change? — In a user perspective, just the domain name. The old sandbox was available at iot.eclipse.org. The new one will be available at mqtt.eclipse.org. As before, port 1883 will be used for standard connections and port 8883 for connections over TLS.

What will happen — For the time being, the DNS record for mqtt.eclipse.org points to the old sandbox. On July 16 2019 at 10:00 EDT, the IT team will switch that DNS record to the new one.

The admins for the new sandbox will only be able to generate the digital certificates for TLS connections after the DNS switch. This means connections over TLS will fail initially, but should be working after a short time.

The old sanbox will stay up for the time being, but will be turned off on August 2, 2019.

Why are we doing this? — The Foundation’s IT team is very small. By reducing their workload, we aim to help them to deliver other services to the Eclipse community more effectively. Moreover, the new sandbox will be run by the Eclipse Mosquitto team, which means you will get the benefits of the latest releases faster than before.

What you should do — Simply edit your connections to use mqtt.eclipse.org! It’s that easy.


I would like to thank Ian Craggs and Roger Light, respectively project leads for Eclipse Paho and Eclipse Mosquitto, for supporting this change. Your dedication to open source preserved an important asset for our community.

Do not hesitate to contact me if you have questions or concerns.

Comments

Popular posts from this blog

Eclipse Amlen v1.0: A Milestone in the Growth of MQTT

Over ten years ago, the Eclipse Foundation launched the Eclipse IoT working group . MQTT was one of the pillars of that launch. The first three projects were Eclipse Paho , a collection of MQTT clients, Eclipse Mosquitto , an MQTT broker, and Eclipse Kura , a Java/OSGi solution for IoT gateways that supports the protocol. To say that MQTT is in our genes would be an understatement. Since then, usage of MQTT has grown significantly. Year after year, the simple yet powerful publish/subscribe protocol is the most widely used IoT-specific protocol in our annual developer surveys . For example, in the 2021 edition, 44% of respondents stated they are using it. We like to think we are at least partly responsible for that. By the way, our 2022 survey is currently underway; you have until June 15, 2022, to participate. Click here to share your insights after finishing this post, of course. IBM has been a key player in our MQTT ecosystem for a long time. In 2021, the company brought its commit

Eclipse IDE for Embedded Developers Now Runs on the Raspberry Pi!

The Eclipse IDE is the project that started it all for the Eclipse Foundation . From the beginning, Eclipse IDE was meant to run on multiple platforms; it now supports Linux, Mac OS and Microsoft Windows. Since it is written in Java, it also supports multiple processor architectures. However, support for 32-bit architectures has been dropped in version 2018-12. This meant recent versions of the IDE would not run on the Raspberry Pi anymore. The introduction of the Raspberry Pi 4 in June 2019 gave hope to Eclipse on Pi fans. With its 64-bit quad core ARM Cortex-A72, the Pi 4 was a good hardware platform to work with. It became even more attractive in May 2020, with the introduction of the 8Gb variant. The Eclipse community took notice of those developments. Version 2020-09 of Eclipse IDE now ships with experimental support for 64-bit ARM (aarch64) on Linux.  Those developments mean embedded and IoT developers can now work on the Raspberry Pi 4 by installing the plugins provided by the 

Sparkplug: From Specification to Standard

This week, the Eclipse Foundation announced that the Sparkpug® 3.0 specification has been published as an International Standard. That sounds impressive. But what does it mean, exactly? And how will this impact the evolution of Sparkplug? To answer this question, let’s take a step back and consider what standards are. The technology industry loves standards. For example, USB is a set of standards managed by the USB Implementers Forum, Inc. (USB-IF), a non-profit corporation founded by the companies that developed the USB specification. The Eclipse Foundation describes Jakarta EE as a standard: a set of  specifications for enterprise Java application development. In the IoT and Industrial Automation world, OASIS Open also presents the MQTT protocol as a standard. However, standards play a much more pervasive role in society. There are standards for building homes and others that define how cars should work. Standards permeate our lives. To understand the significance of this week