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

Add logDir dyn support in gluster-block and tcmu-runner #199

Closed
lxbsz opened this issue Apr 3, 2019 · 2 comments
Closed

Add logDir dyn support in gluster-block and tcmu-runner #199

lxbsz opened this issue Apr 3, 2019 · 2 comments

Comments

@lxbsz
Copy link
Collaborator

lxbsz commented Apr 3, 2019

This is missed currently, will add this later.

Kind of issue

Feature request

Observed behavior

The log directory path is not configurable through the /etc/sysconfig/gluster-block config file.

Expected/desired behavior

The logDir is configurable and will change without restarting the gluster-blockd service.

Details on how to reproduce (minimal and precise)

Currently the dyn config has been support, and we will add dyn-logDir base this.

Logs and Information about the environment:

Other useful information

@pkalever
Copy link
Contributor

pkalever commented Apr 3, 2019

@lxbsz should we use the ISSUE/FEATURE template, so that it make much sense for others ?

Thanks!

@lxbsz
Copy link
Collaborator Author

lxbsz commented Apr 3, 2019

Make sense and I will check this.
Thanks.

lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 3, 2019
This will add the dyn logDir support based the dyn-config without
restarting the gluster-blockd service.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 3, 2019
When the logDir is changed via the /etc/sysconfig/gluster-blockd
config file, the logrotate should be changed too.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 24, 2019
This will add the dyn logDir support based the dyn-config without
restarting the gluster-blockd service.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 24, 2019
When the logDir is changed via the /etc/sysconfig/gluster-blockd
config file, the logrotate should be changed too.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 25, 2019
This will add the dyn logDir support based the dyn-config without
restarting the gluster-blockd service.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 25, 2019
When the logDir is changed via the /etc/sysconfig/gluster-blockd
config file, the logrotate should be changed too.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 26, 2019
This will add the dyn logDir support based the dyn-config without
restarting the gluster-blockd service.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 26, 2019
When the logDir is changed via the /etc/sysconfig/gluster-blockd
config file, the logrotate should be changed too.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 26, 2019
When the logDir is changed via the /etc/sysconfig/gluster-blockd
config file, the logrotate should be changed too.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 26, 2019
When the logDir is changed via the /etc/sysconfig/gluster-blockd
config file, the logrotate should be changed too.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 26, 2019
When the logDir is changed via the /etc/sysconfig/gluster-blockd
config file, the logrotate should be changed too.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 26, 2019
When the logDir is changed via the /etc/sysconfig/gluster-blockd
config file, the logrotate should be changed too.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 26, 2019
This will add the dyn logDir support based the dyn-config without
restarting the gluster-blockd service.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
Reviewed-by: Prasanna Kumar Kalever <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 26, 2019
When the logDir is changed via the /etc/sysconfig/gluster-blockd
config file, the logrotate should be changed too.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
Reviewed-by: Prasanna Kumar Kalever <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 26, 2019
This will add the dyn logDir support based the dyn-config without
restarting the gluster-blockd service.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
Reviewed-by: Prasanna Kumar Kalever <[email protected]>
lxbsz added a commit to lxbsz/gluster-block that referenced this issue Apr 26, 2019
When the logDir is changed via the /etc/sysconfig/gluster-blockd
config file, the logrotate should be changed too.

Fixes: gluster#199
Signed-off-by: Xiubo Li <[email protected]>
Reviewed-by: Prasanna Kumar Kalever <[email protected]>
pkalever pushed a commit that referenced this issue Apr 26, 2019
When the logDir is changed via the /etc/sysconfig/gluster-blockd
config file, the logrotate should be changed too.

Fixes: #199
Signed-off-by: Xiubo Li <[email protected]>
Reviewed-by: Prasanna Kumar Kalever <[email protected]>
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

2 participants