Log access on managers #60271

Closed
opened 2019-01-07 15:50:21 +01:00 by Francesco Siddi · 6 comments

When viewing a task, it's possible to see the full log on the manager (via the "View Low on Manager") button. How do we handle the case when a manager is not in our LAN?

When viewing a task, it's possible to see the full log on the manager (via the "View Low on Manager") button. How do we handle the case when a manager is not in our LAN?
Sybren A. Stüvel was assigned by Francesco Siddi 2019-01-07 15:50:21 +01:00
Author
Owner

Added subscriber: @fsiddi

Added subscriber: @fsiddi

We can have the Manager upload it to the Server on demand, for example by piggy-backing the 'depsgraph' endpoint the Manager uses to pull any changed tasks from the Server.

We can have the Manager upload it to the Server on demand, for example by piggy-backing the 'depsgraph' endpoint the Manager uses to pull any changed tasks from the Server.
Author
Owner

So this would be a parallel queue of "tasks" that are accessible from the "dpsgraph/dispatch" endpoint.
The main difference is that they would be performed directly by the manager?
Could this system be also used for uploading render previews to the server, or should that be part of the job definition?

So this would be a parallel queue of "tasks" that are accessible from the "dpsgraph/dispatch" endpoint. The main difference is that they would be performed directly by the manager? Could this system be also used for uploading render previews to the server, or should that be part of the job definition?

I wasn't thinking about encoding those as actual Tasks, but more as an extra payload in the same way we now also handle task cancellation requests. It would be just a list of job+task IDs to upload to the server. I'll have to think about it more to come up with a nice design that both works rapidly enough (when there are no workers asking for tasks, the Manager only infrequently polls that endpoint) and also doesn't load the server too much.

I wasn't thinking about encoding those as actual Tasks, but more as an extra payload in the same way we now also handle task cancellation requests. It would be just a list of job+task IDs to upload to the server. I'll have to think about it more to come up with a nice design that both works rapidly enough (when there are no workers asking for tasks, the Manager only infrequently polls that endpoint) and also doesn't load the server too much.

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Implemented & deployed to production.

Implemented & deployed to production.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: studio/flamenco#60271
No description provided.