Date: Thu, 28 Mar 2024 09:40:38 +0000 (UTC) Message-ID: <841305036.11453.1711618838278@aws-us-west-2-edgex-confluence-1.web.codeaurora.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11452_209708936.1711618838278" ------=_Part_11452_209708936.1711618838278 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Delivery: ~ November 2018
The Delhi release is slated to provide the first system management capab= ilities while also implementing additional features in the security. = Delhi will continue to show improvements in performance by offering Device = Service SDKs in Go and C. Improved testing at all levels (unit, black= box, performance, etc.) to ensure the quality of the system going forward w= hile also providing a means to check backward compatibility. Finally,= this release will include design and implementation plans (scheduled for E= dinburgh release and beyond) for the replacement of MongoDB as the referenc= e implementation database, and a replacement to the export services to allo= w for better scale and flexibility at the northbound layer. The scope= of this release is smaller given the development cycle for the prior Calif= ornia release was made longer to accommodate all the Go Lang refactoring.= p>
Replace Java scheduling microserice.
Improve the configuration of EdgeX
Implement security & system management API hooks. Dependin= g on the implementation needs of security and system management, there may = be a need to make changes to the micro service code in support of these fac= ets. It is likely that each micro service will implement some sort of= base service to provide data and system management functionality to the sy= stem management agent. Access control to the service APIs will also b= e managed by the security services and code added to the service to require= authentication before accessing the services will be needed.
Implement security & system management API hook. Depending= on the implementation needs of security and system management, there may b= e a need to make changes to the micro service code in support of these face= ts. It is likely that each micro service will implement some sort of = base service to provide data and system management functionality to the sys= tem management agent. Access control to the service APIs will also be= managed by the security services and code added to the service to require = authentication before accessing the services will be needed.
Implement device service SDKs in Go Lang and C. The devi= ce service SDKs and resulting device services will allow the EdgeX communit= y to retire the last of the Java micro services and complete the dramatic p= erformance improvement of EdgeX.
Implement security & system management API hooks. Dependin= g on the implementation needs of security and system management, there may = be a need to make changes to the SDKs and existing micro service code in su= pport of these facets. It is likely that each micro service will impl= ement some sort of base service to provide data and system management funct= ionality to the system management agent. As device services are typic= ally created from an SDK, the same boilerplate code for the base service ne= eds to be added to the SDK(s). Access control to the service APIs wil= l also be managed by the security services and code added to the service to= require authentication before accessing the services will be needed.
= li>System management API (action, alerts, metric) as dis= cussed and outlined here
System management Agent (see = same document above outlining the agent functionality and duties)
= Implement a performance test harness to establish a baseline o= f performance characteristics that can be used to understand EdgeX resource= utilization, data throughput, etc.