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

cmd to join new computes #68

Closed
j0hnL opened this issue May 8, 2020 · 5 comments
Closed

cmd to join new computes #68

j0hnL opened this issue May 8, 2020 · 5 comments
Labels
enhancement New feature or request good first issue Good for newcomers stale This issue is in danger of being automatically closed

Comments

@j0hnL
Copy link
Collaborator

j0hnL commented May 8, 2020

Is your feature request related to a problem? Please describe.
we need a command to join new computes after the cluster has been created.

Describe the solution you'd like
something like grow_cluster -f ./new_inventory_file

Describe alternatives you've considered
maybe just a tag in the ansible playbook?

Additional context
this could apply to different scenarios:

  1. adding new compute hardware to existing cluster
  2. adding cloud infrastructure to existing cluster
@j0hnL j0hnL added enhancement New feature or request good first issue Good for newcomers labels May 8, 2020
@lwilson
Copy link
Collaborator

lwilson commented May 8, 2020

Definitely a needed feature. I think the right approach might be to make startworkers the place where this happens, i.e., startworkers is really just grow_cluster beyond a cluster of 1 node.

@lwilson
Copy link
Collaborator

lwilson commented Oct 21, 2020

If we are considering the refactoring task that's being discussed in #139, then we could have multiple main playbooks for these different operations within the omnia namespace:

omnia.create     # Create a cluster
omnia.destroy    # Tear-down a cluster
omnia.grow       # Add nodes to a cluster
omnia.shrink     # Remove nodes from a cluster

So omnia.grow might accept an inventory file where the manager is already operational, but compute hosts need to be added. Similarly, omnia.shrink might accept an inventory file where the manager is already operational, but compute hosts need to be removed.

omnia.create is basically the omnia.yml proposed in #139, while omnia.destroy is a playbook-based version of scuttle (see #83).

@stale
Copy link

stale bot commented Apr 29, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale This issue is in danger of being automatically closed label Apr 29, 2021
@lwilson
Copy link
Collaborator

lwilson commented May 3, 2021

Commenting to prevent this issue from being closed. I think this is a really important capability that we should continue to develop.

@stale stale bot removed the stale This issue is in danger of being automatically closed label May 3, 2021
@stale
Copy link

stale bot commented Jul 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale This issue is in danger of being automatically closed label Jul 2, 2021
@stale stale bot closed this as completed Jul 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers stale This issue is in danger of being automatically closed
Projects
None yet
Development

No branches or pull requests

2 participants