-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
feat(edge-compute): move host jobs to edge #3840
Conversation
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.
Few things I noticed while trying this build:
- Cannot start from a clean environment, I get the following error in the Portainer logs:
2020/05/21 06:38:40 [ERROR] [http,client] [message: unexpected status code] [status_code: 403]
2020/05/21 06:38:40 [WARN] [exec,extensions] [message: unable to retrieve extensions manifest via Internet. Extensions will be retrieved from local cache and might not be up to date] [err: Invalid response status (expecting 200)]
2020/05/21 06:38:40 [WARN] [exec,extensions] [message: unable to retrieve extension information from Internet. Skipping extensions update check.] [err: open /extensions.json: no such file or directory]
2020/05/21 06:38:40 time: invalid duration
I believe that the problem here is:
2020/05/21 06:38:40 time: invalid duration
If I then start a 2.0.0-dev instance before trying to run this implementation with the same database, it starts fine.
- UI - Settings - Change the tooltip of the Host management switch to:
"Enable host management features: host system browsing and advanced host details." (I just added advanced)
Remove the part about CAP_HOST_MANAGEMENT.
- Sidebar looks broken, I only logged in and I can see endpoint level links in the home view.
- In the Edge job creation view, when no Edge endpoints are available the selector display a "loading" message. It should display "No endpoint available".
After creating an Edge endpoint, it still displays loading so I can't select any endpoint.
- We should prevent the creation of an Edge job if the script file is empty or if there is no associated endpoint
I wasn't able to dig more into this due to the impossibility to create an Edge job at the moment.
c524a07
to
e2afaad
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.
fixes
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.
- Review the task panel in the Edge job details view to only keep the tasks datatable
This datatable should only have two columns: Endpoint, Actions
In the Endpoint column, keep the name of the associated endpoint.
In the actions column, introduce a new way to collect logs via the "Retrieve logs" action. When the logs are available (upon refresh of the view), this action should then change to "Download logs".
- Introduce support for collecting logs associated to a task
Related agent issue: portainer/agent#135
I think my suggestion was misunderstood. What I was thinking was to add the batch action to the task table. There we can have collect logs, clear logs. Download logs will be separate for each task. |
64fb8ee
to
c4fe751
Compare
suggestion:
|
cf45858
to
5656986
Compare
Please rebase that PR on the develop branch. |
c6780c2
to
55ef5d5
Compare
*Ruff* 🐶 The test environment for this pull request has been destroyed 💥 This may have happened explicitly via a command, or because the pull request was closed. React on this comment to leave anonymous feedback.
Commands
|
55ef5d5
to
302c38b
Compare
c2d319b
to
a946a21
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.
-
It seems that this version is not working with Edge stacks, I created an Edge stack but it stayed in Pending state for my Edge endpoint (agent running the following implementation feat(edge-jobs): collect logs agent#140)
-
There is a problem with the schedule date associated to an Edge job, in the following picture I created an Edge job that should start at 4.45 and when I inspect it the associated schedule date is set to 4.42 (current time of my machine)
- Rename Tasks to Results
- After succesfully downloading the logs, it should automatically clear the logs
which endpoint was it? running on the vagrant setup everything worked as expected. running on a local agent (non swarm), it stayed in pending, but that's expected because the endpoint can't run stacks |
it seems like |
what do you mean inspect it? I got the corn job set at the same time I set in the form. The problem I saw is that when submitting the cron expression I ss prefixed with |
Been testing this again.
Cannot reproduce this one.
Cannot reproduce this one.
Ignore this for now. |
0ce78b8
to
24d122d
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.
@ncresswell can you validate host jobs migration? Migrating from an instance with host jobs defined to this new version.
@chiptus have a look at my comments, have some questions as well as some suggestions.
I cant even use the new image on ANY existing instance.. .get invalid time or something like that. I can only deploy new.
|
@chiptus this probably requires a fix |
@pull-dog down |
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.
One minor change required, LGTM
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.
Took care of removing the unused dependency, LGTM
Build is OK, CI is failing cause free plan ! |
fix(edgeconfigs): add triggers for endpoint groups EE-5417 fix(edgeconfigs): fix wrong progress counts EE-4517 fix(edgeconfigs): push missing delete command for async EE-5417
fix #3745