Versions Compared

Key

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

...

  • Front End: The MECM-FE management plane mainly provides the registration of edge nodes, APPLCM, and application distribution and deployment functions from the user interface perspective, which is divided into three functional areas. Map area provides switch between nodes in different regions. The KPI, MEP capabilities and application capabilities are displayed in detail according to the currently selected node.
  • AppO:  Application orchestrator is orchestra tor is the core module responsible for orchestrating life cycle maintenance operation of application. Appo AppO orchestrates application deployment by executing specified process and automated sequence of tasks, rules and policies. Appo AppO is responsible for retrieving the application instance information, edgeehost edge host performance statistics and edge host platform capabilities.
  • Inventory : Responsible for registrations like MEC Host, AppLCM, AppStore, application. Retrieves all the applcm APPLCM records, mec MEC host records and applications.
  • APM: Application package manager responsible for application package management including OnboardingOn boarding, distributing package to edge , retrieves the application package information and download the application package csarCSAR.
  • Postgres DB: Open source PostgreSQL database is being used to store the information for mecm modules ie applcm details,app instance information,application data and package information.Recommended version is 12.3modules specific information.

AppStore:

  • Front End: AppStore is a market for developers to publish and launch App applications. Appstore FE provides the registration interface to the new user and once login the store home is visible, where user can upload the application package across various industry domains and displays the list of application along with the deatilsdetails. User has option to comment on the application in comment section and give ratings. Deleting option is also available in "My App/My APP" section.
  • Appstore Backend: AppStore is a market for developers to publish and launch App applications. After uploading an App package, it must pass the test first. Only the apps that pass the test can be officially launched.
  • Postgres DB: The AppStore database uses an open source PostgreSQL database, and the recommended version is 12.2. Which Stores app information, application package information and review details of the application.

Developer Platform:

  • Tools: Developer tools are used in Plugin Management, Plugin Life Cycle and grading systems making it more convenient for developers to develop applications and integrate them into the edgegallery EdgeGallery platform.
  • Workspace: Developers manage their own Application development process by creating projects or migrating projects. Developers can manage project, app package and test task management.

 

IOT-Gateway Node:

  • aPaaS:
    • Drools - Rules engine.  It is a part of EdgeX foundry services.  In time sensitive use cases or environment where a lot of data is being generated by the connected things, rules engine will be connected to the data coming directly out of core data which will be generated by the gateway node.
  • GPaaS & IOTPaaS:
    • Hawkbit:   Eclipse hawkBitis an domain independent back end solution for rolling out software updates to constrained edge devices as well as more powerful controllers and gateways connected to IP based networking infrastructure.
    • EdgeX: EdgeX is opensource , vendor neutral Edge IOT Middleware platform under the LF Edge umbrella.  It collects data from sensors at the edge and acts as a dual transormation engine sending and receiving data to and from enterprise, cloud and on-premise applications.  EdgeX enables autonomous operations and intelligence(AI) at the edge.  EdgeX translates and transforms the infromation coming from ELIOT edge sites i.e from sensors and devices and delivers it to applications over network based protocols in formats and structures that meet the needs of customers.  It also takes data from applications and delivers it to the iotgateway nodes to control and actuation.  
    • OPC-UA: OPC Unified Architecture is a machine to machine communication protocol for industrial automation developed by OPC Foundation which primarily focus on communicating with industrial equipment and systems for data collection and control.   OPC-UA installed on IOTGateway node. 
    • Prometheus Agent: is an open-source systems monitoring and alerting toolkit.  Main features include building a multidimensional data model with time series data identified by metric name and key/value pairs, PromQL to leverage monitoring, time series data collection , nodes are discovered via service discovery or static configuration.  Prometheus is installed on IOT-Gateway node to collect primarily node metrics and to monitor the cluster.
  • MEP Services:
    • DNS:  The MEP platform provides the domain name resolution services to the applications deployed in the EdgeGallery MEC, which can be utilized by the device applications in UE. MEC platform receives the DNS configurations from the MEC management, which includes the FQDN (Fully Qualified Domain Name), IP address and related entries. MEC applications can later query or modify the state of these configurations.
    • MEP serverMEP platform services like service registry, discovery, DNS, traffic rules etc.  MEP provides service registration, update, delete, and query related API interfaces. Applications can register, update, delete, and query services through MEP.  The service registry provides visibility of the services available on the MEC server. It uses the concept of loose coupling of services, providing flexibility in application deployment. In addition, the service registry presents service availability (status of the service) together with the related interfaces and versions. It is used by applications to discover and locate the end-points for the services they require, and to publish their own service end-point for other applications to use. The access to the service registry is controlled (authenticated and authorised).
  • AppLCM: LCM controller and K8s plugin.  Handles the application life cylce, where lcmController is mainly communicates with K8s plugin to upload config, remove config, instantiate, terminate,and query an application. It also provides APIs to query mep capabilities and kpi information from prometheus.

...

Gerrit Repo : ELIOT IotGateway Gerrit Repo


Alignment with EdgeX community

Below table is to capture information and alignment with EdgeX community for better collaboration.

SI.No.AttributesELIOTEdegXRemarks
EdgeX versionEdinburghHanoi

Till ELIOT Rel4 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