Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Blueprint overview/Introduction

...

Below are details of Upstream and Opensource software's used in various nodes of ELIOT Environment.

OCD Node

S. No.

Software Name

Category

Version Number

Remarks

1.

Ubuntu

OS18.04


2.GITVersion Control2.17.1
3.AnsibleScripting Tool2.10.7


ELIOT Master Node

S. No.

Software Name

Category

Version Number

Remarks

1.

Ubuntu

OS18.04


2.KubernetesOrchestration1.18.7
3.DockerCRI18.09
4.GrafanaAnalytics Dashboard8.7
5.Edge GalleryMultiAccess Edge Computing Platform1.
1
5.
1
0Opensource MEC Platform

IotGateway Node

S. No.

Software Name

Category

Version Number

Remarks

1.UbuntuOS18.04Supports both 16.04 and 18.04
2.DockerCRI18.09
3.K8sOrchestration1.18.7
4.Edge Gallery

MultiAccess Edge Computing Platform

1.
1
5.
1
0Opensource MEC Platform
5.CAdvisorContainer Metrics0.36
6.RabbitMQMessage Queue3.7
7.EdgeXEdge IoT middleware platformEdinburghThis old version is used due to K8s deployment
8.OPC-UAIoT protocol frameworkGeneva

APIs

Please refer the API Documentation link : ELIOT R5 IOTGateway API documentation

...

This table can be used for track alignment with EdgeX

SI.No.

Attributes

ELIOT

EdegX

Remarks

SI.No.

Attributes

ELIOT

EdegX

Remarks


EdgeX versionEdinburghHanoi

Till ELIOT Rel5 plan, EdgeX was not providing K8s based deployment so used older version.

In next ELIOT release analyse and update latest EdgeX version if it support K8s based deployment

2.API versionV1V2Once EdgeX version updated, API page will be updated for latest V2 APIs
3.New components and services supported OPC-UA
Analyse EdgeX and support new features in next release
4.gaps and requirementELIOT use K8s based orchestration, but earlier EdgeX was providing Docker compose based services.
Analyse latest EdgeX release and see whether supported K8s based deployment.
5. New features

Keep track with EdgeX community

Licensing

  • GNU/common license