orb-community / orb Goto Github PK

a microservice responsible for managing the fleet of pktvisor agents

The Sink Creation page contains a vertical step-by-step form that allows the user to create a new sink by providing at least Sink Name and Service Type.

https://www.figma.com/proto/5jZNpc8JMsY2Tj3OQJzgxt/Orb-Product-Portal-UI?node-id=353%3A4337&scaling=min-zoom&page-id=277%3A730

According to UI SPEC page must have the following sections and fields.

Sink Details:

• Sink Name (required)
• Sink Description

Sink Destination:

• Service type (required)
• Backend specific fields (dynamic and required)

Review

By submitting the form creation date and author (should) should also be saved as it will be used on the Sink details modal.

Add scaffolding and bootstrap each of the services modules

• Pages

  • Agent Groups Management
  • Dataset Explorer
  • Fleet Management
  • Sink Management

• Services

  • Agent Groups Management
  • Dataset Explorer
  • Fleet Management
  • Sink Management

• Routing

a microservice responsible for validating and managing orb and pktvisor collection policies.

Use https://www.mainflux.com/ IoT platform for control plane

The goal here is to establish a working skeleton for the orb-api and orb-agent and generate something concrete to iterate on.

• Configure API Service for Sink Management in Mock Server
• Integrate Mock endpoint with Mainflux
• Implement Angular Sink service

https://github.com/ns1labs/orb/wiki/Architecture:-Sinks

Sketch out Orb agent

Specification of the base orb data models

media will be openAPI/swaggerhub

UI has been forked from mainflux. This issue represents work to move the docker composed environment to the forked Orb UI and away from mainflux-ui

https://www.figma.com/proto/5jZNpc8JMsY2Tj3OQJzgxt/Orb-Product-Portal-UI?node-id=353%3A3721&scaling=min-zoom&page-id=277%3A730

Step 1: Agent Group list view
Given user access Agent Groups list view page.
When click on "+ New Agent Group" button
Then must be redirect to Agent Group creation page

Step 2: Agent Group name and Description
Given user access the Agent Group creation page
When seeing the first step
Then step title, caption, and forms input must be consistent with Figma layout

Note*: Agent Group name is a required field

Step 3: Agent Group tags
Given user is on the Agent Group creation page
When filling the second step
Then step title, caption, and forms input must be consistent with Figma layout

Note 1*: On the highlighted part of the screenshot we must include a message with a counter similar to the one shown in the next step. Figma will be updated later.
Note 2*: Tags are not required, but if the user wants to add them, key and value are needed and required.

Step 4: Agent Group creation review
Given user is on the Agent Group creation page
When it is reviewing the creation process
Then step title, caption, and forms input must be consistent with Figma layout

Note 1*: It must include the message about how many agents this group will match
Note 2*: Expand and Collapse table you be addressed in a different issue.

By submitting the form, an Agent Group must be created using all the information provided by the user during the steps. After the creation, the user must be redirected to the Agent Groups list view page where the created Agent Group must be listed.

Complete OpenAPI specification for the fleet manager service

Some features are not integrated correctly, depending on your IDE of choice or where do you select as the ROOT of your project.

Currently, some IntelliJ Idea configuration files are being shared.

Verify if tsconfig path and other linter options should solve the problem without the need for additional/IDE-specific files.

We need to bootstrap the Fleet management module, in order to build on top of it.

For frontend developers looking to accelerate the app development process, having a mocking service should be enough to enable the development of the results page without running the whole app.

https://github.com/ns1labs/orb/security/dependabot/ui/package.json/tinymce/open

https://github.com/ns1labs/orb/security/dependabot/ui/package.json/chart.js/open

HIGH SEVERITY

a microservice responsible for collecting and sinking metric output of pktvisor fleet. the first sink will be prometheus remote write, a good write up on this is here https://github.com/timescale/promscale/blob/master/docs/writing_to_promscale.md

and

https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/exporters/metric/cortex

Check all necessary files and information are available and properly documented.

• Fonts
• Color Palette/Scheme
• Icons
• Wireframing

Produce .scss | .css file overriding Mainflux is .scss style.

The user should be able to check the Sink Details of a specific Sink.

https://www.figma.com/proto/5jZNpc8JMsY2Tj3OQJzgxt/Orb-Product-Portal-UI?node-id=353%3A3972&scaling=min-zoom&page-id=277%3A730

According to UI SPEC page must have the following sections and fields.

• Sink Name
• Sink Description
• Service type
• Backend specific data (no password and token)
• Date Created