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

Check dynamic log levels of each component #428

Closed
jeroenmaelbrancke opened this issue Feb 7, 2017 · 5 comments
Closed

Check dynamic log levels of each component #428

jeroenmaelbrancke opened this issue Feb 7, 2017 · 5 comments
Assignees
Milestone

Comments

@jeroenmaelbrancke
Copy link
Contributor

jeroenmaelbrancke commented Feb 7, 2017

Can you find out which component have a dynamic log level property?

@JeffreyDevloo
Copy link
Contributor

JeffreyDevloo commented Feb 7, 2017

I will have to check with each team individually to write some documentation about all configurable properties.
EDIT: this comment is a reply to all dynamic vars: It seems a useless usecase for us to figure out which ones are dynamic and which are static as we do not know all impact of every single param.

@pploegaert pploegaert added this to the G milestone May 29, 2017
@pploegaert pploegaert modified the milestones: H, G Jun 6, 2017
@wimpers
Copy link

wimpers commented Nov 28, 2017

For the framework components this is dynamic (openvstorage/ovs-documentation#71).

To be checked what about ALBA and VolDrv.

@wimpers wimpers modified the milestones: H, Roadmap Nov 28, 2017
@wimpers
Copy link

wimpers commented Nov 28, 2017

@jeroenmaelbrancke why was this created in integration tests? Should this be moved to devops?

@jeroenmaelbrancke
Copy link
Contributor Author

@wimpers i think you can move this to devops. No idea why i created this ticket on the integrationtests repo.

@openvstorage-ci
Copy link
Contributor

This issue was moved to openvstorage/dev_ops#97

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

No branches or pull requests

5 participants