-
Notifications
You must be signed in to change notification settings - Fork 140
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
Release 0.6.0-alpha #216
Merged
Merged
Release 0.6.0-alpha #216
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
Fix simple typo in README
Integration tests have been broken into multiple steps. This allows easily adding new integration tests as build steps under hpc-toolkit-integration-tests. Cloud build calls ansible-playbook `[slurm-integration-tests | basic-integration-tests]` with a custom configuration yaml. Each test has its own yaml under tools/cloud-build/daily-tests/tests. This file specifies common variables and a list of post_deploy_test, which can be an empty array for tests that only validate deployment. Or can list various extra tasks (only one implemented now: `test-mounts-and-partitions`). This file also specifies the blueprint to create the HPC environment The integration test yml, either `slurm-integration-tests` or `basic-integration-tests`, under ansible_playbooks, in turn calls the creation of the blueprint (create_blueprints.sh) and the post_deploy_tests. To run the tests on your own project, with your own files, use: ```shell gcloud builds submit --config tools/cloud-build/daily-tests/hpc-toolkit-integration-tests.yaml ```
Increasing from 8 to 32 vcpus provides no sizeable performance benefit.
fixing the zone, which was left in us-central1-a, should be us-central1-c
Validate that spack-gromacs cluster can successfully run gromacs via slurm.
This commit adds variables into the spack resource for adding / creating GPG keys, and populating a (preexisting) GCS bucket with the spack packages that have been installed.
Add a spack cache build option to the spack resource
Upgrade to latest DDN EXAScaler
Build modularization
This allows contents to be automatically reused as .gcloudignore when submitting cloud builds.
Toggle filestore api as part of nightly cleanup
Consolidate .gitignore files to root dir
Update URL for ansible-lint pre-commit hook
Revert "Toggle filestore api as part of nightly cleanup"
* Move startup script to login node where the user will do most of their work * Add spack.sh to /etc/profile.d that sources spack env setup script * Add config that changes the stage to within appsfs
…yntax" This reverts commit 4bd6217.
Eliminate use of deprecated create flag from daily tests script
* do not error when encountering string values that are not literal global variables * this ensures all values _except_ literal global variables are left unmodified * modify unit test to test a maps of size greater than 1 and mixed types (plain strings and global variables); issue went uncaught because iteration over maps does not have a guaranteed order and the code continued to succeed in limited testing
Modify resolution of global variables to avoid errors on plain strings
Add jq to builder image
Update WriteBlueprint to handle error and test for overwrite condition
Add placement policy options to simple instance
* Packer template resource adopts standard Toolkit input settings for deployment_name and subnetwork_name * Packer template subnetwork_name will default to same value as used by the VPC resource
Simplify Packer example and adopt Toolkit practices
Fix packer integration test
Increase version to 0.6.0-alpha
heyealex
approved these changes
Apr 19, 2022
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.
Submission Checklist
pre-commit install
make tests
change?
guides?