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

chore: Image name change #238

Open
wants to merge 11 commits into
base: main
Choose a base branch
from
Open

chore: Image name change #238

wants to merge 11 commits into from

Conversation

MikhailKardash
Copy link
Contributor

Description

Change our image names to be more discoverable. Add a matrix for important package versions.

Checklist

  • [] Bump VERSION to make the pushed images are tagged with the right version.
  • Licenses should be included for new code which was copied and/or modified from any external code.
  • Test the images by running the test bumpenvs procedure in the determined repo. See README.

@cla-bot cla-bot bot added the cla-signed label Dec 18, 2023
MikhailKardash and others added 7 commits December 18, 2023 14:20
* Add docker_scripts; updated Makefile and Dockerfile with support for multinode execution.

* Add docker_scripts.

* large change in scrape_libs.sh to fix issues when multiple libfabric.so libs are present; and, fixed missing python libs.

* Created clean branch with all the changes need for ROCM 5.6 multi-node execution

* Bumped version; updated CircleCI config targets.

* removed 'a few extraneous comments.'
@MikhailKardash MikhailKardash marked this pull request as ready for review January 5, 2024 17:45
@@ -0,0 +1,57 @@
git_hash: <git_hash_here>
Copy link
Member

Choose a reason for hiding this comment

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

I don't think I understand what this file is for, if it's got a git_hash embedded into it?

Copy link
Member

@rb-determined-ai rb-determined-ai left a comment

Choose a reason for hiding this comment

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

Overall, looks good to me so far.

To make sure I'm properly understanding the overall plan, we are going to:
a. improve our image naming
b. stop using determinedai/environments:... and use determinedai/the-image-name:... instead
c. only publish hash images from this repo
d. let the determined repo retag hashes into released versions
e. switch to NGC+ images

Is that accurate? It looks like this commit contains a. but not b., d., or e.

What is the overall roll-out plan for how we will deliver this feature to end-users with the fewest number of disruptions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants