-
Notifications
You must be signed in to change notification settings - Fork 29
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
Managed server poc #344
Draft
kabir
wants to merge
34
commits into
wildfly:main
Choose a base branch
from
kabir:managed-server-poc
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Managed server poc #344
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
In the example you are using the latest final release (so 26.1.2.Final) with 2.0.0.Alpha4 cloud feature-pack that is expected to work with WF27. You should use: MANAGED_SERVER_SERVER_FEATURE_PACK="wildfly@maven(org.jboss.universe:community-universe)#27.0.0.Alpha4" or perhaps better "org.wildfly:wildfly-galleon-pack:27.0.0.Alpha4" |
jfdenise
reviewed
Sep 6, 2022
Download tool from Maven and provision server + deployment
… used is from that list
kabir
force-pushed
the
managed-server-poc
branch
from
September 6, 2022 15:32
0ffa00b
to
b86fc78
Compare
jfdenise
reviewed
Sep 6, 2022
...container/wildfly/s2i/2.0/bash/artifacts/opt/jboss/container/wildfly/s2i/maven-s2i-overrides
Outdated
Show resolved
Hide resolved
This was unsuccesful as those changes are not persisted
kabir
force-pushed
the
managed-server-poc
branch
from
September 21, 2022 13:44
3129fd1
to
3346590
Compare
This replaces the previous galleon universe stuff
If channels are used, we don't use the MANAGED_SERVER_XXX_FEATURE_PACK_VERSION env vars when specifying the feature packs to use.
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.
First we need to build the the managed server and builder images, from my s2i branch. The managed server image is tagged as
wildfly/wildfly-managed-server-jdk17:latest
.kabir/built-server-image:latest
is the name of the image containing the server./some/where/deployment
is a directory containing a war, containing aWEB-INF/classes/META-INF/server-config.xml
. Its contents currently list the layers the user wants:We can also optionally add CLI and YAML files to update the configuration. They must be in
WEB-INF/classes/META-INF/server-init.cli
andWEB-INF/classes/META-INF/server-init.yml
in the war.To create the runtime image, I build the following docker file, and run the resulting image: