[JBoss JIRA] (WFCORE-402) Get core resources and operations out of the controller module
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-402?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-565 to WFCORE-402:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-402 (was: WFLY-565)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> Get core resources and operations out of the controller module
> --------------------------------------------------------------
>
> Key: WFCORE-402
> URL: https://issues.jboss.org/browse/WFCORE-402
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> The controller module has a lot of classes related to core resources (resource defs, op handlers, description providers for things like interfaces) that are only in there so they can be commonly accessible to both server and host-controller. This is unnecessary, since host-controller depends on server.
> Either move these to server or create a separate module for this stuff; restrict the controller module to the true core ModelController stuff.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (WFCORE-393) Clone a profile
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-393?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-1706 to WFCORE-393:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-393 (was: WFLY-1706)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> Clone a profile
> ---------------
>
> Key: WFCORE-393
> URL: https://issues.jboss.org/browse/WFCORE-393
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> Add the ability to clone a profile.
> This could be a new "clone" operation on the existing profile resource, or perhaps a "clone-from" parameter on the existing "add" operation. Probably the former, as that will be more transformation-friendly.
> Implementation will likely involve using the "describe" operation used for configuring managed domain servers and adding steps from the describe results directly on the HC instead of passing them to a server.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (WFCORE-394) Provide machine readable referential RBAC document with information of default security constrains
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-394?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-1958 to WFCORE-394:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-394 (was: WFLY-1958)
Component/s: Domain Management
Security
(was: Domain Management)
(was: Security)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> Provide machine readable referential RBAC document with information of default security constrains
> --------------------------------------------------------------------------------------------------
>
> Key: WFCORE-394
> URL: https://issues.jboss.org/browse/WFCORE-394
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management, Security
> Reporter: Jakub Cechacek
> Labels: rbac-filed-by-qa
> Fix For: 1.0.0.Beta1
>
>
> This is more of a future task, but at some point we should make sure that all security constraints are configured properly (right now we have no way of telling which resources should be, for example, sensitive). Thus QE will need something to check against. As a good example of what I mean have a look at referential document for module classification [1] - although for RBAC we would like to see something more "machine-friendly"
> This should be something like listing of resources classified by default as sensitive/application/...
> [1] https://docspace.corp.redhat.com/docs/DOC-105009
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (WFCORE-395) Improve reporting during deployment hang
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-395?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-255 to WFCORE-395:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-395 (was: WFLY-255)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> Improve reporting during deployment hang
> ----------------------------------------
>
> Key: WFCORE-395
> URL: https://issues.jboss.org/browse/WFCORE-395
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Environment: http://java.net/jira/browse/EJB_SPEC-60
> java version "1.7.0_09"
> OpenJDK Runtime Environment (IcedTea7 2.3.3) (7u9-2.3.3-0ubuntu1~12.10.1)
> OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
> Ubuntu 12.10
> Reporter: Carlo de Wolf
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
> Attachments: deployment-hang-20130205.txt, server.log
>
>
> Management Thread waits indefinitely for, what seems to be, a finished operation.
> {noformat}
> "management-handler-thread - 2" prio=10 tid=0x00007fa1380d0000 nid=0x7683 in Object.wait() [0x00007fa136deb000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000000e04ae778> (a org.jboss.as.controller.ContainerStateMonitor)
> at java.lang.Object.wait(Object.java:503)
> at org.jboss.as.controller.ContainerStateMonitor.awaitContainerStateChangeReport(ContainerStateMonitor.java:158)
> - locked <0x00000000e04ae778> (a org.jboss.as.controller.ContainerStateMonitor)
> at org.jboss.as.controller.ModelControllerImpl.awaitContainerStateChangeReport(ModelControllerImpl.java:464)
> at org.jboss.as.controller.OperationContextImpl.awaitModelControllerContainerMonitor(OperationContextImpl.java:148)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:299)
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:142)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:112)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (WFCORE-396) Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-396?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-249 to WFCORE-396:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-396 (was: WFLY-249)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users
> ---------------------------------------------------------------------------------------------
>
> Key: WFCORE-396
> URL: https://issues.jboss.org/browse/WFCORE-396
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> Ops registered on a domain server without the RUNTIME_ONLY flag are hidden from users (e.g. in read-operation-names results etc) in order to not delude users into thinking they can do something like :write-attribute directly on a server (instead of modifying host or domain config elements.)
> But shouldn't a READ_ONLY flag be sufficient as well? An op that only reads config should be valid.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (WFCORE-397) Provide Unit for JVM configuration elements
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-397?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-551 to WFCORE-397:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-397 (was: WFLY-551)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> Provide Unit for JVM configuration elements
> -------------------------------------------
>
> Key: WFCORE-397
> URL: https://issues.jboss.org/browse/WFCORE-397
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Heiko Braun
> Fix For: 1.0.0.Beta1
>
>
> Like with any other config element, units for the JVM parameters would be nice.
> I.e. instead of encoding it into the string value ("64m") it would be better to split the actual value from unit (value=64, unit=<kb|mb|gb>). See the thread subsystem for a reference how this is done in other places
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (WFCORE-392) Stack trace improvements, summarize the things that broke to make them not so intimidating
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-392?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-550 to WFCORE-392:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-392 (was: WFLY-550)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> Stack trace improvements, summarize the things that broke to make them not so intimidating
> ------------------------------------------------------------------------------------------
>
> Key: WFCORE-392
> URL: https://issues.jboss.org/browse/WFCORE-392
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Jim Tyrrell
> Assignee: Brian Stansberry
> Priority: Critical
> Labels: eap6-ux
> Fix For: 1.0.0.Beta1
>
> Attachments: log.txt
>
>
> See the typical attached stack dump:
> It would be nice if the stack dump could include all of the information above as a summary as shown below, basically just the first lines of the errors w/o the whole stack dump:
> 11:51:45,391 INFO [org.jboss.as.server.controller] (HttpManagementService-threads - 5) Deployment of "SpringWAR.war" was rolled back with failure message {"Failed services" => {"jboss.web.deployment.default-host./SpringWAR" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context"}}
> 11:51:45,392 INFO [org.jboss.as.controller] (HttpManagementService-threads - 5) Service status report
> Services which failed to start:
> service jboss.web.deployment.default-host./SpringWAR: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./SpringWAR: failed to start context
> 11:51:45,417 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment SpringWAR.war in 26ms
> 11:51:45,417 Error Summary of Exceptions in deployment:
> - [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
> - [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
> - [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart
> - ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors
> - [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext
> - [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR:
> ERROR Scroll up to see more info...
> Or
> 11:51:45,417 Error Summary of Exceptions in deployment:
> [1] [org.springframework.web.context.ContextLoader] (MSC service thread 1-5) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
> [2] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jbossQueue' defined in class path resource [applicationContextServices.xml]: Invocation of init method failed; nested exception is javax.naming.NameNotFoundException: queue/B -- service jboss.naming.context.java.queue.B
> [3] [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Error listenerStart
> [4] ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-5) Context [/SpringWAR] startup failed due to previous errors
> [5] [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SpringWAR]] (MSC service thread 1-5) Closing Spring root WebApplicationContext
> [6] [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.web.deployment.default-host./SpringWAR:
> ERROR Scroll up to see more info...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (WFCORE-388) Overall 'server-state' flag on the Host Controller
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-388?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-539 to WFCORE-388:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-388 (was: WFLY-539)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> Overall 'server-state' flag on the Host Controller
> --------------------------------------------------
>
> Key: WFCORE-388
> URL: https://issues.jboss.org/browse/WFCORE-388
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> This is for consideration; we need to see if it makes sense.
> Request is for an attribute on the HC that indicates aggregate 'server-state'. The desire is to know when all servers are available, and thus it is safe to invoke management ops knowing all servers will receive them.
> The only reason a server wouldn't receive an op is if it is started in a non-blocking mode, so the server gets its config but then hasn't connected with the HC and therefore won't get update operations. Starting the server in blocking mode will avoid this situation (as could changes to how we start servers, to make it more like how a slave HC registers with the master HC). So, before doing this let's first look at how to reduce/eliminate the use case for it.
> Also to consider when looking at this is how to represent servers in things like "restart-required" state in this overall aggregate 'server-state'.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (WFCORE-389) Alllow non persistent configuration(runtime) changes for server groups and domain using CLI
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-389?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-545 to WFCORE-389:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-389 (was: WFLY-545)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> Alllow non persistent configuration(runtime) changes for server groups and domain using CLI
> -------------------------------------------------------------------------------------------
>
> Key: WFCORE-389
> URL: https://issues.jboss.org/browse/WFCORE-389
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Shay Matasaro
> Assignee: Brian Stansberry
> Labels: EAP
> Fix For: 1.0.0.Beta1
>
>
> Using the CLI , It is currently not possible to make runtime config changes to multiple servers , unless you are using a roll-out plan
> One example is the ability to disable a mod-cluster context on multiple servers at once.
> Since this operation does not affect the persistent server config it is currently not supported.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (WFCORE-390) Add reference description information to resource metadata
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-390?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-541 to WFCORE-390:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-390 (was: WFLY-541)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> Add reference description information to resource metadata
> ----------------------------------------------------------
>
> Key: WFCORE-390
> URL: https://issues.jboss.org/browse/WFCORE-390
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> The AS's configuration model frequently includes attributes that are references to the name of some other resource in the model. The metadata describing such attributes must include information to help users and tooling to understand that reference.
> A simple approach would be to include a metadata attribute whose value is an absolute or relative path to the target resource.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months