#129 Make rampup-cycles and main-cycles be NB template vars again.#171
#129 Make rampup-cycles and main-cycles be NB template vars again.#171
rampup-cycles and main-cycles be NB template vars again.#171Conversation
| args: | ||
| - pip install adelphi; | ||
| adelphi --hosts="{{ .Values.source.clusterName }}-{{ .Values.source.dc }}-service" --username="{{ .Values.source.clusterName }}-superuser" --password="`cat /secret/password`" --keyspaces="{{ .Values.gemini_schema_keyspace }}" --no-anonymize export-nb --rampup-cycles="{{ .Values.nosqlbench_cycles }}" --main-cycles="{{ .Values.nosqlbench_cycles }}" > /workspace/nosqlbench_source.yaml; | ||
| adelphi --hosts="{{ .Values.source.clusterName }}-{{ .Values.source.dc }}-service" --username="{{ .Values.source.clusterName }}-superuser" --password="`cat /secret/password`" --keyspaces="{{ .Values.gemini_schema_keyspace }}" --no-anonymize export-nb > /workspace/nosqlbench_source.yaml; |
There was a problem hiding this comment.
So, I get the change here, but I think I probably need to understand a bit more about what the python tooling spits out for the template.
Maybe and first question... why were these two parameters provided for within the python tooling to begin with? And why is not having them there the "right" way to do this?
There was a problem hiding this comment.
The goal here is to separate execution parameters from the template generation parameters.
The number of cycles is something that matters only at runtime, so once you have the workload YAML generated, you can tweak the number of cycles as you wish without generating the YAML all over again (which requires a connection to the cluster).
Another benefit is keeping the adelphi cli slim and relying on the existing variable replacement feature in NoSQLBench instead.
2 participants
This will require a new pypi release to become effective.