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

Implement node add command #115

Closed
leninmehedy opened this issue Feb 29, 2024 · 1 comment · Fixed by #234
Closed

Implement node add command #115

leninmehedy opened this issue Feb 29, 2024 · 1 comment · Fixed by #234
Assignees
@jeromy-cannon
Labels
New Feature A new feature, service, or documentation. Major changes that are not backwards compatible. P2 Required to be completed in the assigned milestone, but may or may not impact release schedule. released

Comments

@leninmehedy
Copy link
Member 

          While `solo node refresh` is useful, but we need to allow adding a new node (e.g. support `solo node add`).

solo state should maintain a list of all members so that we can generate config.txt when provisioning a new node or refreshing a node.

solo node add flow:

  1. Use helm chart to deploy a new pod
  2. Setup the new node (with correct config.txt)
  3. Send config.txt and public keys to all nodes
  4. Send freeze transaction to all nodes across all clusters
  5. Wait for 2/3 majority of nodes to FREEZE.
  6. Restart/Recycle all node (systemctl restart network-node, for deterministic image it would be to kill the pod).

Originally posted by @leninmehedy in #96 (comment)
@leninmehedy leninmehedy self-assigned this Feb 29, 2024
@leninmehedy leninmehedy added the New Feature A new feature, service, or documentation. Major changes that are not backwards compatible. label Feb 29, 2024
@leninmehedy leninmehedy mentioned this issue Feb 29, 2024
Open
@leninmehedy leninmehedy added this to Solo Feb 29, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Solo Feb 29, 2024
@leninmehedy leninmehedy moved this from 🆕 New to 📋 Backlog in Solo Mar 13, 2024
@leninmehedy leninmehedy added the P2 Required to be completed in the assigned milestone, but may or may not impact release schedule. label Mar 18, 2024
@jeromy-cannon jeromy-cannon mentioned this issue Mar 21, 2024
Closed
1 task
@jeromy-cannon jeromy-cannon moved this from 📋 Backlog to 🏗 In progress in Solo Apr 15, 2024
@jeromy-cannon jeromy-cannon mentioned this issue Apr 16, 2024
Merged
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in Solo Apr 22, 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

@jeromy-cannon jeromy-cannon

Labels
New Feature A new feature, service, or documentation. Major changes that are not backwards compatible. P2 Required to be completed in the assigned milestone, but may or may not impact release schedule. released
Projects
Solo
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: add solo node add subcommand hashgraph/solo
3 participants
@leninmehedy @jeromy-cannon @swirlds-automation