Set Cluster Configuration to operate in memory by default #483
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.
Issue link
RHOAIENG-4525
What changes have been made
By default the SDK now handles appwrapper/individual-resource creation in memory.
Yaml files are not generated while
write_to_file=Falsein cluster configurationVerification steps
Setup
Notebook server ODH/RHOAI/Local
git clone https://github.com/project-codeflare/codeflare-sdk.gitpoetry build- install if needed (pip install poetry)pip install --force-reinstall dist/codeflare_sdk-0.0.0.dev0-py3-none-any.whlTesting
This is very tedious to test as there are 4 possible ways of creating a cluster config with this change. i.e. (
mcad=False,write_to_file=False), (mcad=True,write_to_file=False), ...I recommend to start by testing
mcad=True/Falsewithwrite_to_file=False~/.codeflarefolder - Not necessary but easier to catch things working incorrectly.ClusterConfigurationand a yaml/appwrapper file will not be written you should receive a message like thisYaml resources loaded for <cluster-name>Repeat with an alternate mix of the variables.
Checks