-
Notifications
You must be signed in to change notification settings - Fork 2
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 v0.0.7 #112
Release v0.0.7 #112
Conversation
Fix some formatting too.
* add tds configuration information * Remove old config
Cert-manager 1.12.0 and 1.13.0 were big releases. It's time to catch up. Signed-off-by: Dean Roehrich <[email protected]>
Signed-off-by: Dean Roehrich <[email protected]>
Update the DWS API group in the kube-apiserver audit_policy config. Signed-off-by: Dean Roehrich <[email protected]>
Change the layout to follow the Standard Go Project Layout, as described in https://book.kubebuilder.io/migration/v3vsv4. This allows newer releases of kubebuilder to be used with this repo Signed-off-by: Dean Roehrich <[email protected]>
…n for scp. Also, comment out chassis1 rabbit for the time being. (#94)
Signed-off-by: Dean Roehrich <[email protected]>
The .objectRef.name is already printed with the .requestURI. Signed-off-by: Dean Roehrich <[email protected]>
Introduce a deploy-prometheus.sh script that can install the prometheus-community/kube-prometheus-stack helm chart. Include a file that overrides the ServiceMonitor selector in the chart's values.yaml. This selector inserts a label that is common across the ServiceMonitor resources in the DWS and NNF repos. Signed-off-by: Dean Roehrich <[email protected]>
As part of the NnfDataMovementManager move to nnf-sos, nnf-do does not have its own CRDs anymore and therefor does not have a `make install` or `make uninstall` target. Update submodules after NnfDataMovementManager move Signed-off-by: Blake Devcich <[email protected]>
The texas system's compute nodes cannot hit the k8s cluster with the public facing IP like our other systems. This change adds additional configuration for k8s host and port that is fed into the daemons' configuration so they are able to talk to the cluster from the computes using a separate host/port, if necessary. Signed-off-by: Blake Devcich <[email protected]>
Problem: Readme.md indicates that 'go build' in the root directory will build nnf-deploy, but this is not the case since 3c49e3c. Fix the instructions to say that running 'make' is the proper way to build the nnf-deploy executable.
In nnf-sos, the default storage and container profiles are deployed separately from the default configuration via `examples`. In order to overlay on top of the examples, we must add the ability to get the examples overlay separately and pass it through to the makefile via OVERLAY_EXAMPLES env var. Signed-off-by: Blake Devcich <[email protected]>
These should match the hostnames on the computes themselves. Signed-off-by: Blake Devcich <[email protected]>
We no longer generate the SystemConfiguration resource from `config/systems.yaml`. Instead, we store the actual resource as a YAML text file in the `config/` directory and refer to it from the `config/systems.yaml` file. Signed-off-by: Dean Roehrich <[email protected]>
clientmountd moved from dws to nnf-sos. Update the daemons.conf file to point to the new repo and use the correct service account. Signed-off-by: Matt Richerson <[email protected]>
Use clientmountd in nnf-sos
…, & HTTP2 health check * Added Environment field to daemons to support environment variables in systemd overrides file * Fixed an issue with line endings in the systemd overrides file that caused the first Environment field to be ignored * Added tunings for both daemons Signed-off-by: Blake Devcich <[email protected]>
…odules Signed-off-by: Blake Devcich <[email protected]>
Signed-off-by: Dean Roehrich <[email protected]>
Signed-off-by: Anthony Floeder <[email protected]>
Signed-off-by: Dean Roehrich <[email protected]>
Signed-off-by: Anthony Floeder <[email protected]>
Signed-off-by: Anthony Floeder <[email protected]>
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.
This needs to target the release branch, not master.
config/repositories.yaml
Outdated
@@ -33,14 +33,14 @@ repositories: | |||
master: https://ghcr.io/hewlettpackard/lustre-csi-driver | |||
useRemoteK: true | |||
remoteReference: | |||
build: v0.0.6 | |||
build: 0.0.7 |
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.
I think these need the v
. @roehrich-hpe?
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.
Good catch.
Signed-off-by: Anthony Floeder <[email protected]>
I cloned a fresh copy of the repo, checked out this PR, and did the ./update.sh. This is what I see for the submodules:
I was expecting that each one would include the commit that has the annotated tag. |
When I use LLNL's process to checkout this branch, I see the submodules at the right tags: export NNF_VERSION=v0.0.7
git clone --recurse-submodules [email protected]:NearNodeFlash/nnf-deploy nnf-deploy-$NNF_VERSION
cd nnf-deploy-$NNF_VERSION Since the tag doesn't exist yet, I checkout the git checkout release-v0.0.7
git submodule update Then I get all the tags: $ git submodule status
071e4187ad6cfebc2ea582be3bec47d2124b75ad dws (v0.0.15)
daa1cff12120f0aa991015c95b7527ace7f33ea2 lustre-csi-driver (v0.0.7)
f983003e9a022ea1db56f9d03b89710f2c8110fd lustre-fs-operator (v0.0.7)
a56e780213dbb73e141f4b2c5676fbea66a40f92 nnf-dm (v0.0.7)
a3be2b1b63474d85364e0f8493bb43e9c5d29188 nnf-integration-test (v0.0.4)
226cbe05c4a5e5180ba4d20fc48158ed13291ec0 nnf-sos (v0.1.1) |
Yep, that finds the right stuff. Gotta be careful with that ./update.sh tool. |
I almost never use it. I usually just do this to update the modules: git submodule foreach checkout master
git submodule foreach git pull Not sure if there's a downside to it, but hasn't failed me yet. It's the behavior I would expect. |
No description provided.