-
Notifications
You must be signed in to change notification settings - Fork 216
OWLS 86115: Model in Image should not use operator generated configuration overrides #2285
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
Closed
Closed
Changes from 15 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
7d55190
Use WDT filtering to generate config overrides for MII
lennyphan 1797cdc
Merge from develop branch
lennyphan 78257a8
Fix merge mistake
lennyphan 7438911
Add additional unit tests for situational config override environment…
lennyphan df14d4d
Fix for handling online dynamic update with sparse model
lennyphan ad00e84
Merge remote-tracking branch 'origin/develop' into OWLS-86115
lennyphan 7ec7810
cleanup debug output
lennyphan eca7d2f
Merge remote-tracking branch 'origin/develop' into OWLS-86115
lennyphan 2bcc31b
First set of changes based on review feedback
lennyphan b4b4345
Merge remote-tracking branch 'origin/develop' into OWLS-86115
lennyphan 48e4252
Merge branch 'OWLS-86115' of https://github.com/oracle/weblogic-kuber…
lennyphan c116a66
Merge branch 'OWLS-86115' of https://github.com/oracle/weblogic-kuber…
lennyphan 00c29e5
read domain name from topology, if available
lennyphan 28f0e72
add missing topology.yaml file
lennyphan 4c8ec57
try using python ast package for reading dictionary values instead of…
lennyphan 5851ba6
minor changes based on code review
lennyphan 2cf4b3e
Merge branch main
rjeberhard File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -37,6 +37,7 @@ WDT_OUTPUT="/tmp/wdt_output.log" | |
| WDT_BINDIR="${WDT_ROOT}/bin" | ||
| WDT_FILTER_JSON="/weblogic-operator/scripts/model-filters.json" | ||
| WDT_CREATE_FILTER="/weblogic-operator/scripts/model-wdt-create-filter.py" | ||
| WDT_MII_FILTER="/weblogic-operator/scripts/model_wdt_mii_filter.py" | ||
| UPDATE_RCUPWD_FLAG="" | ||
| WLSDEPLOY_PROPERTIES="${WLSDEPLOY_PROPERTIES} -Djava.security.egd=file:/dev/./urandom" | ||
| ARCHIVE_ZIP_CHANGED=0 | ||
|
|
@@ -319,9 +320,9 @@ function createWLDomain() { | |
| fi | ||
|
|
||
| # copy the filter related files to the wdt lib | ||
|
|
||
| cp ${WDT_FILTER_JSON} ${WDT_ROOT}/lib/model_filters.json | ||
| cp ${WDT_CREATE_FILTER} ${WDT_ROOT}/lib | ||
| cp ${WDT_MII_FILTER} ${WDT_ROOT}/lib | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. consider appending |
||
|
|
||
| # check to see if any model including changed (or first model in image deploy) | ||
| # if yes. then run create domain again | ||
|
|
@@ -793,6 +794,13 @@ function generateMergedModel() { | |
|
|
||
| export __WLSDEPLOY_STORE_MODEL__="${NEW_MERGED_MODEL}" | ||
|
|
||
| local wdtArgs="" | ||
| wdtArgs+=" -oracle_home ${ORACLE_HOME}" | ||
| wdtArgs+=" ${model_list} ${archive_list} ${variable_list}" | ||
| wdtArgs+=" -domain_type ${WDT_DOMAIN_TYPE}" | ||
|
|
||
| trace "About to call '${WDT_BINDIR}/validateModel.sh ${wdtArgs}'." | ||
|
|
||
| ${WDT_BINDIR}/validateModel.sh -oracle_home ${ORACLE_HOME} ${model_list} \ | ||
| ${archive_list} ${variable_list} -domain_type ${WDT_DOMAIN_TYPE} > ${WDT_OUTPUT} 2>&1 | ||
tbarnes-us marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| ret=$? | ||
|
|
@@ -917,6 +925,15 @@ function wdtUpdateModelDomain() { | |
| # make sure wdt create write out the merged model to a file in the root of the domain | ||
| export __WLSDEPLOY_STORE_MODEL__=1 | ||
|
|
||
| local wdtArgs="" | ||
| wdtArgs+=" -oracle_home ${ORACLE_HOME}" | ||
| wdtArgs+=" -domain_home ${DOMAIN_HOME}" | ||
| wdtArgs+=" ${model_list} ${archive_list} ${variable_list}" | ||
| wdtArgs+=" -domain_type ${WDT_DOMAIN_TYPE}" | ||
| wdtArgs+=" ${UPDATE_RCUPWD_FLAG}" | ||
|
|
||
| trace "About to call '${WDT_BINDIR}/updateDomain.sh ${wdtArgs}'." | ||
|
|
||
| ${WDT_BINDIR}/updateDomain.sh -oracle_home ${ORACLE_HOME} -domain_home ${DOMAIN_HOME} $model_list \ | ||
| ${archive_list} ${variable_list} -domain_type ${WDT_DOMAIN_TYPE} ${UPDATE_RCUPWD_FLAG} > ${WDT_OUTPUT} 2>&1 | ||
tbarnes-us marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| ret=$? | ||
|
|
||
Oops, something went wrong.
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.
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.
Could this be fragile? The customer could have a nap name that starts with one of these prefixes. Do we have some earlier validation that ensures that the only names with these prefixes would be naps that were edited by our Istio functionality?
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 could be wrong but I couldn't find any validation for naps that have these prefixes edited by our Istio functionality. @jshum2479 is there validation for these naps that I didn't see?
Uh oh!
There was an error while loading. Please reload this page.
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 function is to write out the topology in the introspector output (not config override), it is trying to format the name in istio ways. If the customer already have it that way and you skipped writing to the topology yaml, then they won't be setup in the pod correctly, perhaps changing the logic to not prepend the protocol again instead of returning.