Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
custom notebooks are added to the image #3
custom notebooks are added to the image #3
Changes from 10 commits
c982034
8fb6d48
3553e9f
f5d8561
0e68050
9efeda7
9aaccb2
2cd4f38
fa208b3
a3aa1b4
12de0f9
b8c3b08
25efbba
55f4d55
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Ouch double download of the pavics-sdi notebooks. At least the config is clearer.
We could have one
config.yml
that will handle all the notebooks repos (eo, nlp, common) but then each image won't be "independent" anymore.Don't have a quick solution at the moment.
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.
@tlvu, at least it's one copy per image and not per user. Hopefully, the common notebooks folder will stay small.
That's the whole point of this PR! Having a single config.yml is about the same as what we have right now.
The download script could be optimized (not for this PR) and keep a cache of each repo independently of the current image. So that while looping over the images, if a repo has already been updated, it uses the cache.
But again I'm note sure of your concern, is it the download or the disk space? In both case it looks like trying to save pennies.
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.
Opps sorry, sending wrong impression again. Wasn't saying this is a deal breaker, else I would change the approval status.
Probably the layout on disk could be
Instead of
But that also assume the same definition of
common
for those images, which might make sense only if on the same deployment node. Like you said, it's pennies at this point so let's do this once we get there.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.
Don't worry I'm not offended and sorry if this is the impression I leave.
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.
Just to be clear, I like all trade-offs/limitations to be clearly documented in a PR. Doesn't mean we need to address all of them immediately. I much prefer iterative approach where we improve gradually than keep adding feature to grow the PR and never release it!