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

Unify Devices and Instances #3477

Closed
2 tasks done
Tracked by #3475
MarianRaphael opened this issue Feb 13, 2024 · 4 comments
Closed
2 tasks done
Tracked by #3475

Unify Devices and Instances #3477

MarianRaphael opened this issue Feb 13, 2024 · 4 comments
Assignees
Labels
size:L - 5 Sizing estimation point task A piece of work that isn't necessarily tied to a specific Epic or Story.
Milestone

Comments

@MarianRaphael
Copy link
Contributor

MarianRaphael commented Feb 13, 2024

Description

The current licensing model differentiates between an instance and a device, which has caused confusion among Sales and customers. The difficulty in explaining the distinction has led to the issuance of licenses based on the number of Node-RED Instances, without regard to whether they are deployed on a device or hosted. Furthermore, the pricing model for both instances and devices has been unified, eliminating the previous distinction in cost.

Self-Hosted

  • Objective: Simplify the license generation process by removing the distinction between Devices and Instances.
  • New Process: Generate licenses based on the total number of Node-RED Runtimes. This total will include all Hosted Instances and Devices on the platform. Customers will have the flexibility to allocate these runtimes across their devices and hosted instances as they see fit, without any predefined restrictions.

FF-Cloud

  • Objective: Enhance flexibility in license allocation by allowing for a combined total runtime limit.
  • New Feature: Introduce the ability to set an overall limit for the total number of Node-RED Runtimes, in addition to the existing individual limits for Instances and Devices. For example, if a total runtime limit of 2 is set, a user could configure one hosted instance and one device under the same license.
    Screenshot 2024-02-13 at 14 43 14

Epic/Story

#3475

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

Tasks

Preview Give feedback
  1. size:M - 3 task
    knolleary
  2. size:M - 3 task
    knolleary
@MarianRaphael MarianRaphael added task A piece of work that isn't necessarily tied to a specific Epic or Story. size:L - 5 Sizing estimation point labels Feb 13, 2024
@MarianRaphael MarianRaphael added this to the 2.1 milestone Feb 13, 2024
@MarianRaphael MarianRaphael moved this from Todo to Up Next in 🛠 Development Feb 14, 2024
@MarianRaphael MarianRaphael modified the milestones: 2.1, 2.2 Feb 15, 2024
@knolleary knolleary self-assigned this Mar 1, 2024
@knolleary knolleary moved this from Up Next to In Progress in 🛠 Development Mar 1, 2024
@knolleary
Copy link
Member

I've split this out into the two separate tasks: updating the license handling for self hosted and updating how limits can be applied to a team tier as they are separate concerns.

@joepavitt
Copy link
Contributor

Is this expected in for tomorrow?

@knolleary
Copy link
Member

The first sub task (#3533) is in for tomorrow - that's the critical one for combining device/instance counts in the license handling.

I'm looking at the second part (#3534) at the moment. It isn't critical path for tomorrow (as it is less relevant for self-hosted users), but we'll want it on FF Cloud as soon as its ready as part of the broader changes to be made to the plans on FF Cloud.

@knolleary knolleary moved this from In Progress to Review in 🛠 Development Mar 15, 2024
@MarianRaphael MarianRaphael modified the milestones: 2.2, 2.3 Mar 19, 2024
@joepavitt
Copy link
Contributor

Any outstanding tasks here @knolleary? Can see the two recorded children tasks are done.

@github-project-automation github-project-automation bot moved this from Next to Closed / Done in ☁️ Product Planning Mar 25, 2024
@knolleary knolleary moved this from Review to Done in 🛠 Development Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:L - 5 Sizing estimation point task A piece of work that isn't necessarily tied to a specific Epic or Story.
Projects
Archived in project
Status: Done
Development

No branches or pull requests

3 participants