-
Notifications
You must be signed in to change notification settings - Fork 26
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
JCliff in a JBoss (EAP6) Domain Environment #64
Comments
Domain mode is not supported yet. I can make the necessary changes, and On Wed, Dec 9, 2015 at 8:18 AM, naefhe [email protected] wrote:
|
That sounds very good, thanks a lot! |
Added --pre= support. You can now add --pre=/host=someHost that will prepend /host=someHost to all commands. It should make it work for domain mode. This will still need some puppet code changes, and I'll do those later, once we get this part working. |
In a running JBoss Domain environment (as opposed to a Standalone environment), configuration changes and deployments are done on the one and only Host Controller (HC) designated as the Domain Controller (DC). When using the JBoss CLI to perform a configuration change on a specific host, I have to talk to the DC and specify /host= in front of e. g. /subsystem=. Similarly, to deploy content onto a particular group of servers, I have to specify /server-group= in front of /deployment=, etc.
How can I tell JCliff to which HC (/host=) or to which Server Group (/server-group=) to address a change or deployment, respectively? These two nodes are currently not accepted by JCliff in Input files and I couldn't find them in any rules either. Are there other mechanisms to achieve this?
Cheers,
Heinz
The text was updated successfully, but these errors were encountered: