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

Grouped Device Deployments #1509

Closed
2 tasks done
Tracked by #2334
joepavitt opened this issue Jan 6, 2023 · 2 comments
Closed
2 tasks done
Tracked by #2334

Grouped Device Deployments #1509

joepavitt opened this issue Jan 6, 2023 · 2 comments
Labels
epic A significant feature or piece of work that doesn't easily fit into a single release scope:device Agent feature for Gateways and PLCs

Comments

@joepavitt
Copy link
Contributor

joepavitt commented Jan 6, 2023

Description

First requested here: #1323

Capturing this in an Epic for planning purposes and to discuss high-level complexities and possible solutions/approaches on how best to tackle it.

Customer Problem:

A single instance of Node-RED can contain multiple tabs, and flows. These flows may communicate with each other, but equally, they can be completely standalone.

Currently, we enable the capturing of a Snapshot of the full instance, that can then be deployed out to remote devices via the FlowForge Device Agent. Any instances with multiple tabs are fully captured in a snapshot, so all tabs are deployed to a Device.

Also, it is currently only possible to set a single "Target Snapshot" for devices attached to a project, so all devices will run that single snapshot.

Requirements

  • It has been requested that we enable "tagging" of a device, so that it is possible to deploy a particular tab to a set of devices.
  • In addition to the tagging, we are also looking at the ability to group/tag devices for the purposes of Staged Deployments (see Staged Deployments #1492).

Proposal

Work here breaks into two parts:

  1. Grouping of devices within a single Project to control which target snapshot is deployed to which device. (see Staged Deployments #1492 where we define that some devices belong to different "stages" of deployment)
  2. The ability to snapshot/deploy just a single tab of a Project, rather than the full flow.json - Raised as a separate epic: Tab-level Snapshots #1694

Tasks

  1. needs-triage size:XXL - 13 story
  2. 5 of 5
    epic headline needs-triage size:XL - 8
    Steve-Mcl
@joepavitt joepavitt added the epic A significant feature or piece of work that doesn't easily fit into a single release label Jan 6, 2023
@joepavitt joepavitt changed the title Tab Deployments Grouped Device Deployments & Tab Snapshots Jan 6, 2023
@knolleary
Copy link
Member

knolleary commented Feb 10, 2023

Want to be a little careful here as I think there are two different epics here:

  • Grouping Devices
  • Tab-level Snapshots

They both feed into a bigger picture but there's no inherent cross-dependency between them as concepts. I'm wary of lumping them together, so I'm going to pull 'Tab-level Snapshots' out as its own Epic (done #1694)

@MarianRaphael MarianRaphael added scope:device Agent feature for Gateways and PLCs consideration A potential feature or improvement that is under review for possible development and implementation labels Mar 31, 2023
@MarianRaphael MarianRaphael changed the title Grouped Device Deployments & Tab Snapshots Grouped Device Deployments Apr 14, 2023
@MarianRaphael
Copy link
Contributor

See also: FlowFuse/device-agent#79

@MarianRaphael MarianRaphael removed the consideration A potential feature or improvement that is under review for possible development and implementation label Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic A significant feature or piece of work that doesn't easily fit into a single release scope:device Agent feature for Gateways and PLCs
Projects
Archived in project
Archived in project
Development

No branches or pull requests

3 participants