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

Implement init command #21

Closed
stgraber opened this issue Sep 28, 2022 · 2 comments
Closed

Implement init command #21

stgraber opened this issue Sep 28, 2022 · 2 comments
Assignees

Comments

@stgraber
Copy link
Contributor

The goal behind the init command is to avoid having the user directly deal with cluster bootstrap and cluster join.

Instead init should provide an interactive workflow where it asks the user whether to create a new cluster or join an existing one.
When creating a new one, it should ask if the user wants to add additional servers to it and if so, issue join tokens.

Once the initial clustering part handled, it should scan available disks and ask the user which should be added as OSDs.

@stgraber
Copy link
Contributor Author

stgraber commented Oct 5, 2022

Current plan for the flow:

 - Check if initialized (/1.0/cluster)
    - YES: Say already initialized ask if want to add disks
        - NO: Exit
        - YES: Jump to cluster add step
    - NO: Ask whether to create a new MicroCeph cluster
        - NO: Ask for join token
        - YES: Bootstrap new cluster
 - Ask if want to add additional machines to the cluster
 - Show local disks available, option to directly enter path or exit
 - <Loop until exit selected>

@stgraber
Copy link
Contributor Author

stgraber commented Oct 5, 2022

We'll eventually want to add the option to deploy additional services to that, but that will need work on the services API first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant