Job log should be saved to a centralized place

[yixingjia]

Job log should be saved to a centralized place

Issue

Replication/Scan job logs are stored in local filesystem.
In multiple instances scenario user will not be able to view replication/scan logs when a request redirect to the jobservices that don’t have the log file

Requirement

All the replication/scan job logs should be saved to a centralized place. All the jobservice instances should be able to access the job logs

Effort estimate

2 week/p
Currently, job logs are stored on local file system.

Scope:
•1>Support save to redis( Prefered P0)
•2>Import a log system/library (need to investigation) P1
•3>Support save to NFS(Already support)

[steven-zou]

@yixingjia Can be try session-sticky solution？

[yixingjia]

It's not related with session-sticky.

User can logout and login after somtime.

[yixingjia]

Per the discussion. In harbor 1.5 the Job history will saved to a shared storage. This will not need any extra works but only some environment preparations.

Move this issue to post Harbor1.5

Save to DB and Redis will not an option according to the discussion.

[Freakin]

Was this implemented in 1.5.0?

[ghost]

/cc @reasonerjt

[reasonerjt]

@Freakin no it's not.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.