April 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-378) Domain rollout operation timeouts

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-378?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-378: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Domain rollout operation timeouts > --------------------------------- > > Key: WFCORE-378 > URL: https://issues.jboss.org/browse/WFCORE-378 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.CR1 > > > Portion of the parent task related to rolling out changes to a domain. > The expectation is that single process timeouts (WFLY-2741) will handle most failure conditions related to domain rollouts (e.g. if a single server hangs, preventing completion of the rollout, eventually that server will time out, allowing the domain wide rollout to continue.) Timeouts in the domain rollout code serve as a second line of defense: > 1) In case of protocol or other problems that prevent the calling process learning about the timeout on the remote process > 2) In case of bugs in the single process timeout handling on the remote process > 3) In mixed domain cases where remote hosts are running previous versions and do not have the timeout function > Potential places to add timeouts: > DomainSlaveHandler->HostControllerUpdateTask.ProxyOperationListener.retrievePreparedOperation() > -- where the master HC waits for responses from slaves > RollingServerGroupUpdateTask.run() -> ServerTaskExecutor.ServerOperationListener.retrievePreparedOperation() > -- timeout here means 1 server didn't respond, but need to move on to next > ConcurrentServerGroupUpdateTask.run() -> ServerTaskExecutor.ServerOperationListener.retrievePreparedOperation() > -- timeout here means none of the remaining servers have responded w/in the timeout > DomainRolloutStepHandler.finalizeOp() -> future.get() > ---- the ServerGroupUpdateTask should fail in the normal phase, so any timeout here would indicate a problem committing the tx or a comms problem getting back the response -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-377) The management API should provide a command to restart only all servers that are in state 'reload-required'

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-377?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-377: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > The management API should provide a command to restart only all servers that are in state 'reload-required' > ----------------------------------------------------------------------------------------------------------- > > Key: WFCORE-377 > URL: https://issues.jboss.org/browse/WFCORE-377 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Wolf-Dieter Fink > Labels: cli, domain, management > Fix For: 1.0.0.CR1 > > > After configuration changes via CLI batch it might be that different processes needs to be restarted. > It is possible to iterate over all servers and check it. > But I think it would be easier to have a command that restart all controllers and servers conditional to the 'relod required' state > - at domain level > - at host level > - at server level > command example : > :restart(ifRequired=true) > :reload(ifRequired=true) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-374) Rethink OperationContextImpl.getBasicAuthorizationResponse

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-374?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-374: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Rethink OperationContextImpl.getBasicAuthorizationResponse > ---------------------------------------------------------- > > Key: WFCORE-374 > URL: https://issues.jboss.org/browse/WFCORE-374 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.CR1 > > > OperationContextImpl.getBasicAuthorizationResponse is designed around the "pass" case. It tests all action effects but discards data if any fail. This is ok in the normal case where things will pass. But in the read-resource-description and recursive read-resource cases, where things may often fail with the failure being recorded as expected (i.e. non-failure) output, this approach is inefficient, because the caller is forced to re-authorize to get the discarded data. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-382) Support for profile and socket binding group includes

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-382?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-382: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Support for profile and socket binding group includes > ----------------------------------------------------- > > Key: WFCORE-382 > URL: https://issues.jboss.org/browse/WFCORE-382 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Kabir Khan > Fix For: 1.0.0.CR1 > > > Restore the ability to have a profile include another profile and for a socket-binding-group to include another socket-binding-group. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-381) xinclude support in the management model

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-381?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-381: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > xinclude support in the management model > ---------------------------------------- > > Key: WFCORE-381 > URL: https://issues.jboss.org/browse/WFCORE-381 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jason Greene > Fix For: 1.0.0.CR1 > > > Ability to use xinclude in the domain/xml/host.xml/standalone.xml documents. Not necessarily anywhere, but where the model supports storing the information. Upon changes to the model, persistence of the relevant elements would be to the specified file. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-387) Describe inheritance relationships in the resource description metadata

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-387?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-387: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Describe inheritance relationships in the resource description metadata > ----------------------------------------------------------------------- > > Key: WFCORE-387 > URL: https://issues.jboss.org/browse/WFCORE-387 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 1.0.0.CR1 > > > Some elements in the management model have an inheritance relationship with other elements located elsewhere. For example, system properties can be defined as a child of the root domain resource, as a child of a server-group resource, as a child of the root host resource, and as a child of the server-config resource. > The resource description metadata for a resource needs to describe these relationships. It needs to cover the inheritance hierarchy, as well as how any conflicts are resolved (i.e. does the child win, as is the case with system properties and interfaces, or is some sort of merging strategy employed, as is the case with profiles and socket-binding-groups, where the sets of child resources (subsystems and socket-bindings) are merged, provided that the two sets are disjoint. > A factor to include in this metadata is whether the relationship is fixed (i.e. host system-property inherits from server-group) or whether there is some attribute that defines the inheritance (e.g. a profile's that "includes" another profile has an attribute that defines the name of the included profile.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-386) Ability to configure a custom RBAC implementation

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-386?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-386: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Ability to configure a custom RBAC implementation > ------------------------------------------------- > > Key: WFCORE-386 > URL: https://issues.jboss.org/browse/WFCORE-386 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Priority: Optional > Labels: RBAC-WF-only > Fix For: 1.0.0.CR1 > > > Allow configuration of a module name and set of key/value properties to allow users to plug in a custom implementation of the CustomAuthorizer interface. The impl would be loadable via the ServiceLoader mechanism. > The hooks to integrate such a custom impl into the server are already done, so this is should be just a matter of adding the config capability. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-384) Server does wrongly reference a list of socket binding groups

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-384?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-384: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Server does wrongly reference a list of socket binding groups > ------------------------------------------------------------- > > Key: WFCORE-384 > URL: https://issues.jboss.org/browse/WFCORE-384 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Fix For: 1.0.0.CR1 > > > hbraun: i see that a server (host=foo/server=bar) can have a list of socket-binding-groups > [10:59am] hbraun: shouldn't that be a a single socket binding instead? > [11:00am] emuckenhuber: oh... yeah > [11:00am] hbraun: maybe it's just the description that's wrong > [11:00am] emuckenhuber: that sounds similar to the jvm thing we had -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-383) Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources>

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-383?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-383: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.0.0.Beta1) > Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources> > ---------------------------------------------------------------------------------------------------- > > Key: WFCORE-383 > URL: https://issues.jboss.org/browse/WFCORE-383 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 1.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-390) Add reference description information to resource metadata

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-390?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFCORE-390: ---------------------------------- Fix Version/s: 1.0.0.CR1 (was: 1.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.CR1 > > > 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.11#6341)

11 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2015