[pull] master from 2i2c-org:master #571
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
I just checked, and we were *almost full*
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4 to 5. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v4...v5) --- updated-dependencies: - dependency-name: actions/setup-python dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [chuhlomin/render-template](https://github.com/chuhlomin/render-template) from 1.8 to 1.9. - [Release notes](https://github.com/chuhlomin/render-template/releases) - [Commits](chuhlomin/render-template@v1.8...v1.9) --- updated-dependencies: - dependency-name: chuhlomin/render-template dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4 to 5. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v4...v5) --- updated-dependencies: - dependency-name: actions/setup-python dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 3.1.0 to 4.0.0. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v3.1.0...v4.0.0) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
updates: - [github.com/pre-commit/mirrors-prettier: v3.0.3 → v4.0.0-alpha.8](pre-commit/mirrors-prettier@v3.0.3...v4.0.0-alpha.8) - [github.com/pycqa/isort: 5.12.0 → 5.13.2](PyCQA/isort@5.12.0...5.13.2) - [github.com/psf/black: 23.11.0 → 23.12.1](psf/black@23.11.0...23.12.1)
Follow-up to #3429. As part of that, I had redirected where the HHMI (and all other projects') cloud costs go, and this updates the cluster.yaml to point to the correct place.
Sometimes it's actually an integer, and our rich text output does not like that and throws an error
Bump utoronto r image on staging
While starting to work on #3565, I realized that VEDA was still using the older style 'node share' rather than the generated 'resource allocation' options. I've swapped over the options to now be based on images for users to choose and resource allocation options generated by our resource allocation script. This matches openscapes, and there has generally been pretty big positive feedback on this mode. I've kept the initial cloning to only happen on the pangeo image as it currently exists, without making any changes. That should be cleaned up as part of #3565
…github/actions/setup-deploy/actions/setup-python-5 Bump actions/setup-python from 4 to 5 in /.github/actions/setup-deploy
[pre-commit.ci] pre-commit autoupdate
…ons/upload-artifact-4.0.0 Bump actions/upload-artifact from 3.1.0 to 4
…ons/setup-python-5 Bump actions/setup-python from 4 to 5
billing script: Stringify project id
Correct where the HHMI cloud costs go
I've been upgrading cryptnono quite a bit over the last few months, bringing in new detectors that have been quite effective on mybinder.org. We automatically bump cryptnono on our clusters (#3482), but recent progress have included some breaking changes to the helm chart config. This PR just brings in the new config changes, but does not change behavior in any real way. No new detectors are enabled. I've re-measured resource usage for the individual daemonset container (rather than the initContainer) as that can now be set separately. This probably requires us to redo some of the resource allocation generated profiles, which I'll do once this is merged. However, it is an overall reduction in daemonset requests, so deploying this shouldn't result in any profile being undeployable. Merging this should allow #3482 to move forward as well.
Default to k8s 1.28 in new clusters (EKS, GKE)
[cloudbank] Added Admins to CSULB
Add an issue template for tickets that will not be immediately resolved by the triagers
utoronto: Bump storage size
Bring in newer cryptnono version
Use generated resource allocation options for veda hub
#3569 changed the cryptnono daemonset to have different resource requests for the init containers as well as the container. While working on #3566, I noticed this was generating wrong choices - the overhead was calculated wrong (too small). We were intentionally ignoring init containers while calculating overhead, and turns out the scheduler and the autoscaler both do take it into consideration. The effective resource request for a pod is the higher of the resource requests for the containers *or* the init containers - this ensures that a pod with higher requests for init containers than containers (like our cryptnono pod!) will actually run. This is documented at https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#resource-sharing-within-containers, and implemented in Kubernetes itself at https://github.com/kubernetes/kubernetes/blob/9bd0ef5f173de3cc2d1d629a4aee499d53690aee/pkg/api/v1/resource/helpers.go#L50 (this is the library code that the cluster autoscaler uses). This PR updates the two places we currently have that calculate effective resource requests (I assume eventually these will be merged into one - I haven't kept up with the team's work last quarter here). I've updated the node-capacity-info.json file, which is what seems to be used by the generator script right now.
Brings in the new memory / cpu limits set up for #3572 - without that, the largest set up size doesn't actually spawn on r5.4xlarge due to insufficient memory.
https://github.com/2i2c-org/nasa-qgis-image is the new home of this image, as the PR linked to has been closed.
Re-generate deployer's credentials for nasa-esdis/veda/ghg and document this as self-mergable
Adjust memory requests so largest instances spawn on r5.4xlarge
Use qgis image from new location
[cloudbank] More Admin Users: CSU LB
…stuff terraform, azure and utoronto: fixes and aligning files with terraform state
Include initContainers when calculating pod overhead
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )
📚 Documentation preview 📚: https://2i2c-pilot-hubs--571.org.readthedocs.build/en/571/