Skip to content
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

Get rid of the pangeo-forge image #477

Merged
merged 3 commits into from
Sep 14, 2023
Merged

Conversation

yuvipanda
Copy link
Member

No longer needed as of
pangeo-forge/pangeo-forge-runner#90!

This simplifies pangeo-forge maintenance as well, as we no longer have to match versions of python and apache_beam with whatever is going on here.

@github-actions
Copy link
Contributor

Binder 👈 Try on Mybinder.org!
Binder 👈 Try on Pangeo GCP Binder!
Binder 👈 Try on Pangeo AWS Binder!

@pangeo-bot
Copy link
Collaborator

/condalock
Automatically locking new conda environment, building, and testing images...

@weiji14 weiji14 linked an issue Aug 20, 2023 that may be closed by this pull request
Copy link
Member

@weiji14 weiji14 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @yuvipanda! This will simplify maintenance going forward, as we won't need to do stuff like #470 anymore. Just some suggested changes on the main README.md and should be ok.

Comment on lines -21 to 23
| [forge](ml-notebook/packages.txt) | pangeo-notebook + [Apache Beam](https://beam.apache.org/) support| ![](https://img.shields.io/docker/image-size/pangeo/forge?sort=date) | ![](https://img.shields.io/docker/pulls/pangeo/forge?sort=date)

*Click on the image name in the table above for a current list of installed packages and versions*

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this file, could you also:

  1. Remove the click forge "https://hub.docker.com/r/pangeo/forge" "Open this in a new tab" _blank line at L36?
  2. Mention in the 'Other notes' section that the forge image is no longer built/maintained, but old versions can be found at https://quay.io/repository/pangeo/forge?tab=tags

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@weiji14 done!

Copy link
Member

@scottyhq scottyhq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @yuvipanda ! unfortunately a few conflicts now that other things have been merged. Are you able to revisit this?

@yuvipanda
Copy link
Member Author

I'm waiting to hear from @cisaacstern before moving forward. We all agree this is the path forward - the question now is, do we wait for pangeo-forge/pangeo-forge-runner#90 to be merged before merging this, or can we do that before?

@weiji14
Copy link
Member

weiji14 commented Sep 13, 2023

I'm waiting to hear from @cisaacstern before moving forward. We all agree this is the path forward - the question now is, do we wait for pangeo-forge/pangeo-forge-runner#90 to be merged before merging this, or can we do that before?

The forge docker images will still be archived at https://hub.docker.com/r/pangeo/forge/tags and https://quay.io/repository/pangeo/forge?tab=tags, and available for download for the forseeable future right? Should be ok to merge this PR now (once the conflicts have been resolved), since it sounds like the pangeo-forge-runner will be moving to Apache Beam supported docker images eventually.

@cisaacstern
Copy link
Member

The forge docker images will still be archived at https://hub.docker.com/r/pangeo/forge/tags and https://quay.io/repository/pangeo/forge?tab=tags, and available for download for the forseeable future right?

How long is the foreseeable future? As long as the old images will be archived for long enough to ensure we'll have made the transition by the time the archive expires, I'm 👍

No longer needed as of
pangeo-forge/pangeo-forge-runner#90!

This simplifies pangeo-forge maintenance as well, as we no
longer have to match versions of python and apache_beam with
whatever is going on here.
@yuvipanda
Copy link
Member Author

Thanks for chiming in, @cisaacstern!

I've resolved the merge conflicts, and updated the README, @weiji14!

@weiji14
Copy link
Member

weiji14 commented Sep 13, 2023

The forge docker images will still be archived at https://hub.docker.com/r/pangeo/forge/tags and https://quay.io/repository/pangeo/forge?tab=tags, and available for download for the forseeable future right?

How long is the foreseeable future? As long as the old images will be archived for long enough to ensure we'll have made the transition by the time the archive expires, I'm 👍

Well, there isn't an expiry date set for the quay.io hosted images (see Expires = Never in screenshot below), so it should be until they change their terms and conditions 🙂

image

Copy link
Member

@weiji14 weiji14 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @yuvipanda! Will simplify maintenance going forward.

@cisaacstern
Copy link
Member

Awesome LGTM! Thanks all!

@weiji14 weiji14 merged commit 334b81e into pangeo-data:master Sep 14, 2023
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Simplify forge image if/when upstream beam changes permit
5 participants