Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TASK] Create Ngild agent using new onboarding method #445

Closed
yshashix opened this issue Nov 3, 2023 · 0 comments
Closed

[TASK] Create Ngild agent using new onboarding method #445

yshashix opened this issue Nov 3, 2023 · 0 comments
Assignees
Labels

Comments

@yshashix
Copy link
Collaborator

yshashix commented Nov 3, 2023

No description provided.

@yshashix yshashix added the task label Nov 3, 2023
@yshashix yshashix added this to the API stable (beta) milestone Nov 3, 2023
@yshashix yshashix self-assigned this Nov 3, 2023
wagmarcel added a commit to wagmarcel/DigitalTwin that referenced this issue Dec 30, 2023
This PR provides a cleaned-up and simplified device agent. The device agent is responsible
to connect to MQTT, manage the device token and forwards metrics provided over local udp/tcp protocol.
The orginial oisp device admin has been removed and replaced by scripts to manage device onboarding
and do test data sending.
The original oisp-agent had many ways to communicate to the backend. This has been removed. Now, only the SparkplugB oriented
data sending for NGSI-LD data is supported. The agent relies only on two services: (1) Keycloak and (2) MQTT.
Since the onboarding only relies on Keycloak, there is a little change on activation procedure. Details are described in the README.

Related Epic: IndustryFusion#432
Related User Story: IndustryFusion#446
Related Tasks: IndustryFusion#400, IndustryFusion#445, IndustryFusion#447

Signed-off-by: marcel <[email protected]>
wagmarcel added a commit to wagmarcel/DigitalTwin that referenced this issue Dec 30, 2023
This PR provides a cleaned-up and simplified device agent. The device agent is responsible
to connect to MQTT, manage the device token and forwards metrics provided over local udp/tcp protocol.
The orginial oisp device admin has been removed and replaced by scripts to manage device onboarding
and do test data sending.
The original oisp-agent had many ways to communicate to the backend. This has been removed. Now, only the SparkplugB oriented
data sending for NGSI-LD data is supported. The agent relies only on two services: (1) Keycloak and (2) MQTT.
Since the onboarding only relies on Keycloak, there is a little change on activation procedure. Details are described in the README.

Related Epic: IndustryFusion#432
Related User Story: IndustryFusion#446
Related Tasks: IndustryFusion#400, IndustryFusion#445, IndustryFusion#447

Signed-off-by: marcel <[email protected]>

fix of copyright years

Signed-off-by: marcel <[email protected]>
abhijith-hr pushed a commit that referenced this issue Jan 3, 2024
This PR provides a cleaned-up and simplified device agent. The device agent is responsible
to connect to MQTT, manage the device token and forwards metrics provided over local udp/tcp protocol.
The orginial oisp device admin has been removed and replaced by scripts to manage device onboarding
and do test data sending.
The original oisp-agent had many ways to communicate to the backend. This has been removed. Now, only the SparkplugB oriented
data sending for NGSI-LD data is supported. The agent relies only on two services: (1) Keycloak and (2) MQTT.
Since the onboarding only relies on Keycloak, there is a little change on activation procedure. Details are described in the README.

Related Epic: #432
Related User Story: #446
Related Tasks: #400, #445, #447

Signed-off-by: marcel <[email protected]>

fix of copyright years

Signed-off-by: marcel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants