From bd33dd430013a1ddd2e605229bd408141299faa1 Mon Sep 17 00:00:00 2001 From: github-actions Date: Thu, 4 Jan 2024 08:35:43 +0000 Subject: [PATCH] [#306] Automated content build --- 404.html | 2 +- about/_print/index.html | 2 +- about/features/index.html | 2 +- about/index.html | 2 +- about/motivation/index.html | 2 +- about/overview/index.html | 2 +- categories/index.html | 2 +- community/_print/index.html | 2 +- community/index.html | 2 +- docs/_print/index.html | 2 +- docs/concepts/_print/index.html | 2 +- docs/concepts/aws-connector/index.html | 2 +- docs/concepts/container-management/index.html | 2 +- docs/concepts/file-upload/index.html | 2 +- docs/concepts/index.html | 2 +- docs/concepts/software-update/index.html | 2 +- docs/concepts/suite-connector/index.html | 2 +- docs/getting-started/_print/index.html | 2 +- docs/getting-started/hono/index.html | 2 +- docs/getting-started/index.html | 2 +- docs/getting-started/install/index.html | 2 +- docs/how-to-guides/_print/index.html | 2 +- docs/how-to-guides/backup-restore-files/index.html | 2 +- docs/how-to-guides/bootstrap-device/index.html | 2 +- docs/how-to-guides/index.html | 2 +- docs/how-to-guides/monitor-system-metrics/index.html | 2 +- docs/how-to-guides/update-software/index.html | 2 +- docs/how-to-guides/upload-files/index.html | 2 +- docs/index.html | 2 +- docs/references/_print/index.html | 2 +- docs/references/connectivity/_print/index.html | 2 +- docs/references/connectivity/aws-connector-config/index.html | 2 +- docs/references/connectivity/index.html | 2 +- .../connectivity/suite-bootstrapping-config/index.html | 2 +- docs/references/connectivity/suite-connector-config/index.html | 2 +- docs/references/containers/_print/index.html | 2 +- docs/references/containers/container-config/index.html | 2 +- docs/references/containers/container-manager-config/index.html | 2 +- docs/references/containers/index.html | 2 +- docs/references/file-backup-config/index.html | 2 +- docs/references/file-upload-config/index.html | 2 +- docs/references/index.html | 2 +- docs/references/local-digital-twins-config/index.html | 2 +- docs/references/software-update-config/index.html | 2 +- docs/references/system-metrics-config/index.html | 2 +- index.html | 2 +- search/index.html | 2 +- tags/index.html | 2 +- year/index.html | 2 +- 49 files changed, 49 insertions(+), 49 deletions(-) diff --git a/404.html b/404.html index 7bc7ebc6..d297aae3 100644 --- a/404.html +++ b/404.html @@ -2,7 +2,7 @@

Element not found

The web address you entered is not a functioning page on our site.

Go home -
© 2023 The Eclipse Kanto™ Project. All Rights Reserved.
+
diff --git a/about/_print/index.html b/about/_print/index.html index 77f6de90..101c04d7 100644 --- a/about/_print/index.html +++ b/about/_print/index.html @@ -7,7 +7,7 @@

About Eclipse Kanto

motivation | overview | features

Motivation

We are living in an era of digitization, in which companies are reshaping their operations and innovating their business models by offering next generation connected products and digital services. Machines, consumer goods and vehicles are transforming into complex connected IoT devices with advanced software features, collecting and reacting on user insights and data in real-time in secure and safe way.

Edge computing is shifting from hardware to software focusing on intelligent devices, edge platforms, edge applications and services. New connected products continuously increase in complexity to benefit AIoT – be it built into the products or empowering the production lines. Building the products of the future such as connected vehicles and in vehicle cross-domain applications, connected appliances, smart buildings and connected manufacturing is becoming more and more complex and companies are losing time and money to build the common technologies by themselves, sometimes even lacking the right skills and expertise.

We bring our knowledge and 20+ years of IoT and edge experience in the open source to enable true collaboration, technology co-development and co-innovation! We address the sheer complexity of edge software and hardware via open technology and ecosystem approach ensuring freedom of choice with vendor-neutral, independent jointly-developed software that goes at the heart of manufactured devices.

Overview

Eclipse Kanto™ is a modular IoT edge software that enables devices for IoT with all essentials like cloud connectivity, digital twins, local communication, container management, and software updates - all configurable and remotely manageable by an IoT cloud ecosystem of choice.

Eclipse Kanto makes it possible to deploy intelligence on the device so companies can get more value from diverse edge assets, process and act on IoT data right on the device and manage devices from the cloud. Device manufacturers can add new revenue streams with connected products and ensure agile development for hardware and software.

Using Eclipse Kanto, technology teams take advantage of configurable and reusable building blocks to connect the unconnected or build the edge applications for the next generation connected products and services.

Eclipse Kanto is specifically optimized for complex IoT devices facing limited hardware resources, (near) real-time requirements, diverse device software, heterogeneous data sources and the ability to operate without connection. This makes it a perfect technology for emerging paradigms such as software-defined vehicles, connected machines and connected manufacturing, smart appliances, smart buildings and more.

Features

Cloud connectivity

  

Digital twins

  

Local communication

  

Lightweight container management

  

Flexible software updates

  

Flexible file uploads

  

Flexible deployment

© 2023 The Eclipse Kanto™ Project. All Rights Reserved.
+validation, on start up resume and more

  

Flexible file uploads

  

Flexible deployment

diff --git a/about/features/index.html b/about/features/index.html index 41242d86..8c9ae071 100644 --- a/about/features/index.html +++ b/about/features/index.html @@ -17,7 +17,7 @@

Cloud connectivity

  

Digital twins

  

Local communication

  

Lightweight container management

  

Flexible software updates

  

Flexible file uploads

  

Flexible deployment

© 2023 The Eclipse Kanto™ Project. All Rights Reserved.
+validation, on start up resume and more

  

Flexible file uploads

  

Flexible deployment

diff --git a/about/index.html b/about/index.html index d50320cc..7ab4dbff 100644 --- a/about/index.html +++ b/about/index.html @@ -7,7 +7,7 @@

About Eclipse Kanto

motivation | overview | features

Motivation

We are living in an era of digitization, in which companies are reshaping their operations and innovating their business models by offering next generation connected products and digital services. Machines, consumer goods and vehicles are transforming into complex connected IoT devices with advanced software features, collecting and reacting on user insights and data in real-time in secure and safe way.

Edge computing is shifting from hardware to software focusing on intelligent devices, edge platforms, edge applications and services. New connected products continuously increase in complexity to benefit AIoT – be it built into the products or empowering the production lines. Building the products of the future such as connected vehicles and in vehicle cross-domain applications, connected appliances, smart buildings and connected manufacturing is becoming more and more complex and companies are losing time and money to build the common technologies by themselves, sometimes even lacking the right skills and expertise.

We bring our knowledge and 20+ years of IoT and edge experience in the open source to enable true collaboration, technology co-development and co-innovation! We address the sheer complexity of edge software and hardware via open technology and ecosystem approach ensuring freedom of choice with vendor-neutral, independent jointly-developed software that goes at the heart of manufactured devices.

Overview

Eclipse Kanto™ is a modular IoT edge software that enables devices for IoT with all essentials like cloud connectivity, digital twins, local communication, container management, and software updates - all configurable and remotely manageable by an IoT cloud ecosystem of choice.

Eclipse Kanto makes it possible to deploy intelligence on the device so companies can get more value from diverse edge assets, process and act on IoT data right on the device and manage devices from the cloud. Device manufacturers can add new revenue streams with connected products and ensure agile development for hardware and software.

Using Eclipse Kanto, technology teams take advantage of configurable and reusable building blocks to connect the unconnected or build the edge applications for the next generation connected products and services.

Eclipse Kanto is specifically optimized for complex IoT devices facing limited hardware resources, (near) real-time requirements, diverse device software, heterogeneous data sources and the ability to operate without connection. This makes it a perfect technology for emerging paradigms such as software-defined vehicles, connected machines and connected manufacturing, smart appliances, smart buildings and more.

Features

Cloud connectivity

  

Digital twins

  

Local communication

  

Lightweight container management

  

Flexible software updates

  

Flexible file uploads

  

Flexible deployment

© 2023 The Eclipse Kanto™ Project. All Rights Reserved.
+validation, on start up resume and more

  

Flexible file uploads

  

Flexible deployment

diff --git a/about/motivation/index.html b/about/motivation/index.html index a263c93a..6a56d476 100644 --- a/about/motivation/index.html +++ b/about/motivation/index.html @@ -4,7 +4,7 @@ Edge computing is shifting from hardware to software focusing on intelligent devices, edge platforms, edge applications and services.">

We are living in an era of digitization, in which companies are reshaping their operations and innovating their business models by offering next generation connected products and digital services. Machines, consumer goods and vehicles are transforming into complex connected IoT devices with advanced software features, collecting and reacting on user insights and data in real-time in secure and safe way.

Edge computing is shifting from hardware to software focusing on intelligent devices, edge platforms, edge applications and services. New connected products continuously increase in complexity to benefit AIoT – be it built into the products or empowering the production lines. Building the products of the future such as connected vehicles and in vehicle cross-domain applications, connected appliances, smart buildings and connected manufacturing is becoming more and more complex and companies are losing time and money to build the common technologies by themselves, sometimes even lacking the right skills and expertise.

We bring our knowledge and 20+ years of IoT and edge experience in the open source to enable true collaboration, technology co-development and co-innovation! We address the sheer complexity of edge software and hardware via open technology and ecosystem approach ensuring freedom of choice with vendor-neutral, independent jointly-developed software that goes at the heart of manufactured devices.

© 2023 The Eclipse Kanto™ Project. All Rights Reserved.
+

We are living in an era of digitization, in which companies are reshaping their operations and innovating their business models by offering next generation connected products and digital services. Machines, consumer goods and vehicles are transforming into complex connected IoT devices with advanced software features, collecting and reacting on user insights and data in real-time in secure and safe way.

Edge computing is shifting from hardware to software focusing on intelligent devices, edge platforms, edge applications and services. New connected products continuously increase in complexity to benefit AIoT – be it built into the products or empowering the production lines. Building the products of the future such as connected vehicles and in vehicle cross-domain applications, connected appliances, smart buildings and connected manufacturing is becoming more and more complex and companies are losing time and money to build the common technologies by themselves, sometimes even lacking the right skills and expertise.

We bring our knowledge and 20+ years of IoT and edge experience in the open source to enable true collaboration, technology co-development and co-innovation! We address the sheer complexity of edge software and hardware via open technology and ecosystem approach ensuring freedom of choice with vendor-neutral, independent jointly-developed software that goes at the heart of manufactured devices.

diff --git a/about/overview/index.html b/about/overview/index.html index 45c036ed..6727acb4 100644 --- a/about/overview/index.html +++ b/about/overview/index.html @@ -4,7 +4,7 @@ Eclipse Kanto makes it possible to deploy intelligence on the device so companies can get more value from diverse edge assets, process and act on IoT data right on the device and manage devices from the cloud.">

Eclipse Kanto™ is a modular IoT edge software that enables devices for IoT with all essentials like cloud connectivity, digital twins, local communication, container management, and software updates - all configurable and remotely manageable by an IoT cloud ecosystem of choice.

Eclipse Kanto makes it possible to deploy intelligence on the device so companies can get more value from diverse edge assets, process and act on IoT data right on the device and manage devices from the cloud. Device manufacturers can add new revenue streams with connected products and ensure agile development for hardware and software.

Using Eclipse Kanto, technology teams take advantage of configurable and reusable building blocks to connect the unconnected or build the edge applications for the next generation connected products and services.

Eclipse Kanto is specifically optimized for complex IoT devices facing limited hardware resources, (near) real-time requirements, diverse device software, heterogeneous data sources and the ability to operate without connection. This makes it a perfect technology for emerging paradigms such as software-defined vehicles, connected machines and connected manufacturing, smart appliances, smart buildings and more.

© 2023 The Eclipse Kanto™ Project. All Rights Reserved.
+

Eclipse Kanto™ is a modular IoT edge software that enables devices for IoT with all essentials like cloud connectivity, digital twins, local communication, container management, and software updates - all configurable and remotely manageable by an IoT cloud ecosystem of choice.

Eclipse Kanto makes it possible to deploy intelligence on the device so companies can get more value from diverse edge assets, process and act on IoT data right on the device and manage devices from the cloud. Device manufacturers can add new revenue streams with connected products and ensure agile development for hardware and software.

Using Eclipse Kanto, technology teams take advantage of configurable and reusable building blocks to connect the unconnected or build the edge applications for the next generation connected products and services.

Eclipse Kanto is specifically optimized for complex IoT devices facing limited hardware resources, (near) real-time requirements, diverse device software, heterogeneous data sources and the ability to operate without connection. This makes it a perfect technology for emerging paradigms such as software-defined vehicles, connected machines and connected manufacturing, smart appliances, smart buildings and more.

diff --git a/categories/index.html b/categories/index.html index 30412690..b7884658 100644 --- a/categories/index.html +++ b/categories/index.html @@ -1,7 +1,7 @@ Categories | Eclipse Kanto™ | IoT edge software stack

Categories

© 2023 The Eclipse Kanto™ Project. All Rights Reserved.
+
diff --git a/docs/concepts/_print/index.html b/docs/concepts/_print/index.html index 9941e275..9c9e4709 100644 --- a/docs/concepts/_print/index.html +++ b/docs/concepts/_print/index.html @@ -12,7 +12,7 @@ The container management continuously ensures the applications availability via state awareness and restart policies, provides monitoring via flexible logging and fine-grained resources management. All of that is achieved on top of an underlying runtime of choice (containerd by default) that takes care of the low-level isolation mechanisms.

4 - Software update

Empower the edge device to handle diverse software updates.

Software update enables the deployment and management of various software artifacts, both locally and remotely via an IoT cloud ecosystem of choice. It provides the following use cases:

  • Robust download - with a retry and resume mechanism when the network connection is interrupted
  • Artifact validation - with an integrity validation of every downloaded artifact
  • Universal installation - with customizable install scripts to handle any kind of software
  • Operation monitoring - with a status reporting of the download and install operations

Software update

How it works

When the install operation is received at the edge, the download process is initiated. Retrieving the artifacts will continue until they are stored at the edge or their size threshold is reached. If successful, the artifacts are validated for integrity and further processed by the configured script. It is responsible to apply the new software and finish the operation. A status report is announced on each step of the process enabling its transparent monitoring.

On start up, if there have been any ongoing operations, they will be automatically resumed as the operation state is persistently stored.

What’s next

How to update software

5 - File upload

Empower the edge device to upload files to various storage providers.

File upload enables sending of files to a backend storage of choice. It can be used both locally and remotely via a desired IoT cloud ecosystem. The following use cases are provided:

  • Storage diversity - with ready to use integrations with Azure Blob Storage, Amazon S3 and standard HTTP upload
  • Automatic uploads - with periodically triggered uploads at a specified interval in a given time frame
  • Data integrity - with an option to calculate and send the integrity check required information
  • Operation monitoring - with a status reporting of the upload operation

File upload

How it works

It’s not always possible to inline all the data into exchanged messages. For example, large log files or large diagnostic files cannot be sent as a telemetry message. In such scenarios, file upload can assist enabling massive amount of data to be stored to the backend storage.

There are different triggers which can initiate the upload operation: periodic or explicit. Once initiated, the request will be sent to the IoT cloud for confirmation or cancellation transferred back to the edge. If starting is confirmed, the files to upload will be selected according to the specified configuration, their integrity check information can be calculated and the transfer of the binary content will begin. A status report is announced on each step of the upload process -enabling its transparent monitoring.

What’s next

How to upload files

diff --git a/docs/concepts/aws-connector/index.html b/docs/concepts/aws-connector/index.html index a2af84c2..5fda809b 100644 --- a/docs/concepts/aws-connector/index.html +++ b/docs/concepts/aws-connector/index.html @@ -37,7 +37,7 @@

AWS Connector

Empower the edge device with a remote connectivity.

AWS Connector enables the remote connectivity to an AWS IoT cloud ecosystem. It provides the following use cases:

  • Enriched remote connection
    • Optimized - to pass the messages via a single underlying connection
    • Secured - to protect the edge identity and data via TLS with basic and certificate-based authentication
    • Maintained - with a reconnect exponential backoff algorithm
    • Synchronized - on a connectivity recovering via a message buffering
  • Application protection - AWS Connector is the only one component with a remote connectivity i.e. all local applications are protected from exposure to the public network
  • Offline mode - local applications don’t need to care about the status of the remote connection, they can stay fully operable in offline mode
  • Device Shadow - messages sent to the Twin Channel are converted to messages more suitable for AWS Device Shadow service and sent to it.

AWS Connector

How it works

The AWS Connector plays a key role in two communication aspects - local and remote.

Cloud connectivity

To initiate its connection, the edge has to be manually or automatically provisioned. The result of this operation is different parameters and identifiers. Currently, AWS Connector supports MQTT transport as a connection-oriented and requiring less resources in comparison to AMQP. Once established, the connection is used as a channel to pass the edge telemetry and event messages. The IoT cloud can control the edge via commands and responses.

In case of a connection interruption, the AWS Connector will switch to offline mode. The message buffer mechanism will be activated to ensure that there is no data loss. Reconnect exponential backoff algorithm will be started to guarantee that no excessive load will be generated to the IoT cloud. All local applications are not affected and can continue to operate as normal. Once the remote connection is restored, all buffered messages will be sent and the edge will be fully restored to online mode.

Local communication

Ensuring that local applications are loosely coupled, Eclipse Hono™ MQTT definitions are in use. The event-driven local messages exchange is done via a MQTT message broker - Eclipse Mosquitto™. The AWS Connector takes the responsibility to forward these messages to the IoT cloud and vice versa.

Monitoring of the remote connection status is also enabled locally as well, along with details like the last known state of the connection, timestamp and a predefined connect/disconnect reason.

Last modified October 10, 2023
© 2023 The Eclipse Kanto™ Project. All Rights Reserved.
+ Print entire section

AWS Connector

Empower the edge device with a remote connectivity.

AWS Connector enables the remote connectivity to an AWS IoT cloud ecosystem. It provides the following use cases:

  • Enriched remote connection
    • Optimized - to pass the messages via a single underlying connection
    • Secured - to protect the edge identity and data via TLS with basic and certificate-based authentication
    • Maintained - with a reconnect exponential backoff algorithm
    • Synchronized - on a connectivity recovering via a message buffering
  • Application protection - AWS Connector is the only one component with a remote connectivity i.e. all local applications are protected from exposure to the public network
  • Offline mode - local applications don’t need to care about the status of the remote connection, they can stay fully operable in offline mode
  • Device Shadow - messages sent to the Twin Channel are converted to messages more suitable for AWS Device Shadow service and sent to it.

AWS Connector

How it works

The AWS Connector plays a key role in two communication aspects - local and remote.

Cloud connectivity

To initiate its connection, the edge has to be manually or automatically provisioned. The result of this operation is different parameters and identifiers. Currently, AWS Connector supports MQTT transport as a connection-oriented and requiring less resources in comparison to AMQP. Once established, the connection is used as a channel to pass the edge telemetry and event messages. The IoT cloud can control the edge via commands and responses.

In case of a connection interruption, the AWS Connector will switch to offline mode. The message buffer mechanism will be activated to ensure that there is no data loss. Reconnect exponential backoff algorithm will be started to guarantee that no excessive load will be generated to the IoT cloud. All local applications are not affected and can continue to operate as normal. Once the remote connection is restored, all buffered messages will be sent and the edge will be fully restored to online mode.

Local communication

Ensuring that local applications are loosely coupled, Eclipse Hono™ MQTT definitions are in use. The event-driven local messages exchange is done via a MQTT message broker - Eclipse Mosquitto™. The AWS Connector takes the responsibility to forward these messages to the IoT cloud and vice versa.

Monitoring of the remote connection status is also enabled locally as well, along with details like the last known state of the connection, timestamp and a predefined connect/disconnect reason.

Last modified October 10, 2023
diff --git a/docs/concepts/container-management/index.html b/docs/concepts/container-management/index.html index e60191b6..74ea6ac6 100644 --- a/docs/concepts/container-management/index.html +++ b/docs/concepts/container-management/index.html @@ -41,7 +41,7 @@ The built image is made available for usage by being pushed to a container image registry where the runtime can refer it to.

To create a new container instance, the container management uses such an image reference and a configuration for it to produce a fully functional container. The container lifecycle (start, update, stop, remove) and environment (memory constraints, restart policy, etc.) are also handled by the runtime. The container management continuously ensures the applications availability via state awareness and restart policies, provides monitoring via flexible logging and fine-grained resources management. -All of that is achieved on top of an underlying runtime of choice (containerd by default) that takes care of the low-level isolation mechanisms.

Last modified July 21, 2022