RKT image fetch policy
14 views
Skip to first unread message
Serghei Anicheev
Apr 6, 2017, 8:29:04 AM4/6/17
to CoreOS Dev
Hey guys!
I wanted to discuss image fetch policy which you have here : https://github.com/rkt/rkt/blob/548c7d0a37a0d291a9732c7851a2fd45d37dcd00/rkt/image/common.go#L103-L109
Basically you fetch image and then do nothing until it will be expired.
I would like to propose you another scheme and ready to prepare pull request for this if you think the same.
In my opinion it would be better to store Etag in a file after image fetch and compare it everytime with one located on a storage server during fetch operations.
This can be useful if image have 2-3 or more dependencies or some images do not require their version update due to any reason.
Best Regards,
Serghei
I wanted to discuss image fetch policy which you have here : https://github.com/rkt/rkt/blob/548c7d0a37a0d291a9732c7851a2fd45d37dcd00/rkt/image/common.go#L103-L109
Basically you fetch image and then do nothing until it will be expired.
I would like to propose you another scheme and ready to prepare pull request for this if you think the same.
In my opinion it would be better to store Etag in a file after image fetch and compare it everytime with one located on a storage server during fetch operations.
This can be useful if image have 2-3 or more dependencies or some images do not require their version update due to any reason.
Best Regards,
Serghei
Reply all
Reply to author
Forward
0 new messages