[jboss-jira] [JBoss JIRA] (WFCORE-4959) Feature for checking module installation in JBoss
[
https://issues.redhat.com/browse/WFCORE-4959?page=com.atlassian.jira.plug...
]
Darran Lofthouse commented on WFCORE-4959:
------------------------------------------
This would be quite a big change, the module --add command within the CLI just operates on
the local filesystem and writes the module directly, once you start talking about domain
mode this converts this to more of a management level operation to distribute an operation
across the host controllers.
Once talking about the host controllers you can identify the currently running host
controllers but if you wanted to target the ones not presently running / the ones to run
in the the future tracking those becomes more complex.
I have also in the past wondered if we could so something where if a slave does not have a
module requested it tries to pull it from the master which would save the coordination of
a command like this but potentially brings in new problems such as mixed domains where
different versions of modules are required or modules with optional dependencies where the
missing module is intended.
Feature for checking module installation in JBoss
-------------------------------------------------
Key: WFCORE-4959
URL: https://issues.redhat.com/browse/WFCORE-4959
Project: WildFly Core
Issue Type: Feature Request
Reporter: Joao Paulo Goncalves
Assignee: Brian Stansberry
Priority: Major
Using CLI tool or Administrative Console is not possible at this moment to check if a
custom added module was added correctly, especially in domain mode. The only alternative
available is to add host per host. This approach takes time, and for unused users there
isn't some visual (GUI) to help them.
JBoss CLI approach:
module --add --source=jar1,jar2 --target=/path-of-module --host=your-host OR module --add
--source=jar1,jar2 --target=/path-of-module --host=all (deploy the module in all hosts
that belongs to the domain)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)