-
Notifications
You must be signed in to change notification settings - Fork 159
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
Run Collect-info through Edgeview #4106
Run Collect-info through Edgeview #4106
Conversation
b5cd4ed
to
cf26edc
Compare
Commit messages, pleeeease 😭😭😭 |
hmm, i thought the one before were commit messages, but I added something before the list, is that what you meant? |
No, I mean the messages that you add to any commit when creating it... Without proper commit messages, it's hard to understand the changes made when looking through the history or git blame. It's nice you've added a PR description here on GitHub, but it will be lost after the PR is merged: it will be impossible to see it from an IDE or the command line... |
cf26edc
to
900edd0
Compare
@OhmSpectator added in the commit. to see if this is good. thanks. |
9d0e64b
to
b1c0710
Compare
3578fc3
to
78815e3
Compare
78815e3
to
108fa47
Compare
108fa47
to
fb45597
Compare
fb45597
to
f859a0a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that the pathname for the eve-info files changed in #4125 so they are in the /persist/eve-info/ directory instead of just in /persist/
So presumably you need to add that eve-info component to the pathnames you use here.
missed that. will change. |
f859a0a
to
0a551cf
Compare
Changed to reflect the new /persist/eve-info/ as the base. I removed the 'mkdir -p "/persist/$INFO_DIR_SUFFIX"' in the collect-info.sh, since this created directory is not used, and never removed after. |
Odd, because I had to add that mkdir to make the tar command not fail when I just did a 'eve enter debug' followed by collect-info.sh. |
0a551cf
to
f659d98
Compare
fixed a yetus complaining |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have any automatic tests of edgeview? And how hard would it be to create some basic one to just check that it is functional?
Currently I don't have this infra. We need to create a task/jira item o this. |
f659d98
to
b129b37
Compare
- Add the implementation on running collect-info through Edgeview - Egeview is mostly only with read permission access to device filesystems and it does not want to import all the pkgs and replicate the collect-info.sh operations and maintain compatibility of two sets of the collect-info - this implementation has a protocol to setup a request for debug container to start run 'collect-info.sh', and remove the request file after it is done; Edgeview then uses existing copy file protocol to transfer the collect-info tarball file back to user's laptop; then Edgeview put another request for - debug container to remove the created tarball file in /persist debug container has added a background task to monitor the request- - Since collect-info is mostly live info, there is no need to get all the newlogs, only fetch the newlogs of the past 10 days. - change the debug/ssh.sh into debug/debug-tasks.sh to reflect it does not only handling the ssh task Signed-off-by: Naiming Shen <naiming@zededa.com>
b129b37
to
71f77e4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@naiming-zededa the regression/eden tests passed, but there might be some open comments/issues on the PR. Can you check if those are taken care of to satisfaction? |
@eriknordmark I went through them, they should all be resolved. |
there are a number of request to have edgeview support for collectinfo,
this patch has the list of implementation:
and it does not want to import all the pkgs and replicate the collect-info.sh
operations and maintain compatibility of two sets of the collect-info
to start run 'collect-info.sh', and remove the request file after it is done;
Edgeview then uses existing copy file protocol to transfer the collect-info
tarball file back to user's laptop; then Edgeview put another request for
debug container to remove the created tarball file in /persist
only fetch the newlogs of the past 10 days.