Infinispan doc updates #4101
Open
Infinispan doc updates #4101
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
Signed-off-by: Pavel Jareš <[email protected]>
|
😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.
Need help? Contact the Doc Squad in the #zowe-doc Slack channel. |
6 tasks
janan07
reviewed
Jan 30, 2025
Signed-off-by: Pavel Jareš <[email protected]>
Signed-off-by: Andrew Jandacek <[email protected]>
janan07
approved these changes
Jan 30, 2025
|
You are missing this page https://docs.zowe.org/stable/user-guide/address-network-requirements |
Signed-off-by: Andrew Jandacek <[email protected]>
janan07
added
area: apiml
Signed-off-by: Andrew Jandacek <[email protected]>
janan07
reviewed
Feb 6, 2025
pablocarle
reviewed
Feb 10, 2025
| @@ -68,19 +64,15 @@ Configure Infinispan as a storage solution through the Caching service by settin | |||
| caching-service: | |||
| storage: | |||
| mode: infinispan | |||
| infinispan: | |||
| infinispan: | |||
| jgroups.port: 7098 | |||
There was a problem hiding this comment.
I understand this works, but I think we usually just nest the properties
Suggested change
| jgroups.port: 7098 | |
| groups: | |
| port: 7098 |
Comment on lines
52
to
57
| * **`zowe.components.caching-service.storage.infinispan.jgroups.host`** | ||
|
|
||
| (OPTIONAL)The default value is taken from zowe hostname. The hostname used by Infinispan to synchronise data among cahing-service instances. | ||
|
|
||
|
|
||
| * **`zowe.components.caching-service.storage.infinispan.keyExchange.port`** |
There was a problem hiding this comment.
There is no use case for infinispan running off-platform, right?
|
|
||
| (OPTIONAL)The default value is `7098`. The port number used by Infinispan to synchronise data among cahing-service instances. | ||
| (Optional) The default value is `7600`. The port number is used by Infinispan to synchronise data among Caching Service instances. |
There was a problem hiding this comment.
Since this is going with 3.2, I'd keep the 7098, I believe we need to update that in the defaults.yaml
|
|
||
| (OPTIONAL)The default value is `7118`. The port number used by Infinispan to exchange encryption key among cahing-service instances. | ||
| (Optional) The default value is `7601`. The port number is used by Infinispan to exchange encryption key among Caching Service instances. |
There was a problem hiding this comment.
This one is not defined in https://github.com/zowe/zowe-install-packaging/blob/v3.x/staging/files/defaults.yaml
Default is 7118
Comment on lines
87
to
88
| infinispan: | ||
| jgroups.port: 7098 |
There was a problem hiding this comment.
same thing about being consistent, use the nested format
Comment on lines
+91
to
+92
| dataLocation: /global/zowe/workspace/caching-service/data | ||
| indexLocation: /global/zowe/workspace/caching-service/index |
There was a problem hiding this comment.
add a comment to the example about needing to be in a non-shared filesystem (tendency to copy-paste)
Signed-off-by: Pavel Jareš <[email protected]>
|
Version 3.1 is changed by #4171 |
pablocarle
reviewed
Feb 10, 2025
Comment on lines
43
to
44
| | 7099 | zowe.components.caching-service.storage.infinispan.jgroups.keyExchange.port | The port at which the key server in Infinispan is listening. If the port is not available, the next port is probed, up to port+5. Used by the key server (server) to create an SSLServerSocket and by clients to connect to the key server. | ||
| | 7098 | zowe.components.caching-service.storage.infinispan.jgroups.port | Bind port for the socket that is used to form an Infinispan cluster. |
There was a problem hiding this comment.
These should be 7601 and 7600, right?
Signed-off-by: Pavel Jareš <[email protected]>
Signed-off-by: Andrew Jandacek <[email protected]>
janan07
approved these changes
Feb 11, 2025
Signed-off-by: Pavel Jareš <[email protected]>
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.
This PR contains two versions on new file
api-mediation-infinispan.md.The updates is to respect changes from these PRs:
The text in
versioned_docs/version-v3.0.x/extend/extend-apiml/api-mediation-infinispan.mdis valid for 3.0 and 3.1.The text in
docs/extend/extend-apiml/api-mediation-infinispan.mdwill be valid since 3.2.