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.

Sign up for GitHub

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

Jump to bottom

Ability to deploy different software package to a subset of nodes #157

Closed
Tracked by #47
poulok opened this issue Mar 11, 2024 · 2 comments · Fixed by #232
Closed
Tracked by #47

Ability to deploy different software package to a subset of nodes #157

poulok opened this issue Mar 11, 2024 · 2 comments · Fixed by #232
Assignees
@leninmehedy @JeffreyDallas
Labels
New Feature A new feature, service, or documentation. Major changes that are not backwards compatible. Pending Triage New issue that needs to be triaged by the team released

Comments

@poulok
Copy link
Member

poulok commented Mar 11, 2024

Requested Feature

I want the ability to run different implementations of the same software on different nodes. For example, I want to run software implementation A on nodes 0, 1, and 2, and run software implementation B on node 3.

Business Need

I need to run large scale performance tests without paying for large performance networks. In order to do this, I want to run a single production sized machine with unmodified production code. The other nodes in the network will run "mini-node" software that has been gutted of the expensive operations like handling transactions and applying state. If I can deploy 1 normal node and many "mini nodes" which require far fewer resources, I can make one node operate just as it would in a very large scale network without the high costs.

Additional Context

No response
@poulok poulok added New Feature A new feature, service, or documentation. Major changes that are not backwards compatible. Pending Triage New issue that needs to be triaged by the team labels Mar 11, 2024
@nathanklick nathanklick added this to Solo Mar 11, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Solo Mar 11, 2024
@leninmehedy leninmehedy mentioned this issue Mar 11, 2024
Open
@leninmehedy
Copy link
Member

With the recent refactoring of NodeCommand, I believe it will be possible to have this out of the box. However, I'll do some testing and report back.

@JeffreyDallas JeffreyDallas mentioned this issue Apr 25, 2024
Merged
@leninmehedy leninmehedy moved this from 🆕 New to ✋ Blocked in Solo May 8, 2024
@github-project-automation github-project-automation bot moved this from ✋ Blocked to ✅ Done in Solo May 16, 2024
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.25.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@leninmehedy leninmehedy

@JeffreyDallas JeffreyDallas

Labels
New Feature A new feature, service, or documentation. Major changes that are not backwards compatible. Pending Triage New issue that needs to be triaged by the team released
Projects
Solo
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: ability to deploy different software package to a subset of nodes hashgraph/solo
4 participants
@leninmehedy @JeffreyDallas @swirlds-automation @poulok