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

User-guide: add doc to describe how to tune ironic before deploying #233

Open
fmuyassarov opened this issue Jan 14, 2022 · 16 comments
Open

User-guide: add doc to describe how to tune ironic before deploying #233

fmuyassarov opened this issue Jan 14, 2022 · 16 comments
Assignees
@Rozzii
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@fmuyassarov
Copy link
Member

Describe:

  • how to tune Ironic parameters before deploying. Example, how to enable a certain features like fast track before ironic is deployed
  • what is the format we pass or manipulate those parameters. As an example, in dev-env we use configMap

/kind documentation
/help
@metal3-io-bot
Copy link
Contributor

@fmuyassarov:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

Describe:

  • how to tune Ironic parameters before deploying. Example, how to enable a certain features like fast track before ironic is deployed
  • what is the format we pass or manipulate those parameters. As an example, in dev-env we use configMap

/kind documentation
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@metal3-io-bot metal3-io-bot added kind/documentation Categorizes issue or PR as related to documentation. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jan 14, 2022
@fmuyassarov
Copy link
Member Author

/cc @dtantsur @Rozzii

@Rozzii
Copy link
Member

Rozzii commented Feb 4, 2022

/triage accepted

@metal3-io-bot metal3-io-bot added the triage/accepted Indicates an issue is ready to be actively worked on. label Feb 4, 2022
@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 5, 2022
@metal3-io-bot
Copy link
Contributor

Stale issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle stale.

/close

@metal3-io-bot
Copy link
Contributor

@metal3-io-bot: Closing this issue.

In response to this:

Stale issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle stale.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@furkatgofurov7
Copy link
Member

/reopen
/remove-lifecycle stale

@metal3-io-bot
Copy link
Contributor

@furkatgofurov7: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle stale

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@metal3-io-bot metal3-io-bot reopened this Jun 27, 2022
@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 27, 2022
@Rozzii
Copy link
Member

Rozzii commented Sep 14, 2022

/assign @Rozzii

@Rozzii
Copy link
Member

Rozzii commented Sep 14, 2022

/remove help

@Rozzii
Copy link
Member

Rozzii commented Sep 14, 2022

/remove help-wanted

@Rozzii
Copy link
Member

Rozzii commented Nov 2, 2022

/assign @Rozzii

@Rozzii
Copy link
Member

Rozzii commented Nov 30, 2022

/remove help

@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 28, 2023
@Rozzii
Copy link
Member

Rozzii commented Mar 1, 2023

/remove-lifecycle stale.

@dtantsur
Copy link
Member

dtantsur commented Mar 8, 2023

/remove-lifecycle stale
/lifecycle frozen

@metal3-io-bot metal3-io-bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Rozzii Rozzii

Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Metal3 - Roadmap
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
5 participants
@dtantsur @Rozzii @fmuyassarov @furkatgofurov7 @metal3-io-bot