March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-333) Provide a management operation to list the servers in a server group (domain mode)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-333?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-333: ------------------------------------ Labels: domain-mode (was: ) > Provide a management operation to list the servers in a server group (domain mode) > ---------------------------------------------------------------------------------- > > Key: WFCORE-333 > URL: https://issues.jboss.org/browse/WFCORE-333 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Richard Achmatowicz > Priority: Minor > Labels: domain-mode > > In domain mode, an end user might want to start one or more servers by hand in a named server group. Obtaining the list of servers in a server group is not readily available: the "group" attribute is embedded in server-config, so we have to drill down into every /host=*/server-config=* combination to find out which servers belong to a specific server group. > It would improve the user experience to have an operation which shows which servers are in a given server group. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-326) Pushing configuration artifacts to domain servers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-326?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-326: ------------------------------------ Labels: clustering domain domain-mode (was: clustering domain) > Pushing configuration artifacts to domain servers > ------------------------------------------------- > > Key: WFCORE-326 > URL: https://issues.jboss.org/browse/WFCORE-326 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Darragh Sherwin > Priority: Minor > Labels: clustering, domain, domain-mode > > It should be possible to push configurations artifacts like property files, keystores, etc to domain servers from a domain controller and for applications to reference these configuration artifacts in a generic manner. > Weblogic provides this functionality -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-347) Better reporting if a master and slave HC are both launched from the same directory

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-347?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-347: ------------------------------------ Labels: domain-mode (was: ) > Better reporting if a master and slave HC are both launched from the same directory > ----------------------------------------------------------------------------------- > > Key: WFCORE-347 > URL: https://issues.jboss.org/browse/WFCORE-347 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Labels: domain-mode > > The only symptom at the moment is hangs on startup on the slave as mentioned in AS7-4593. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[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 updated WFCORE-388: ------------------------------------ Labels: domain-mode (was: ) > 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 > Labels: domain-mode > > 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 (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-289) Emit notifications for servers in domain mode

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-289?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-289: ------------------------------------ Labels: domain-mode (was: ) > Emit notifications for servers in domain mode > --------------------------------------------- > > Key: WFCORE-289 > URL: https://issues.jboss.org/browse/WFCORE-289 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Labels: domain-mode > > emit notifications related to server lifecycle in domain mode: > * server-started > * server-stopped > * server-restarted > * server-destroyed > * server-killed > These notifications should be emitted from the corresponding server-config resource (under /host=XXX/server-config=YYY) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-344) Create operations to view the host and process controller log files

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-344?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-344: ------------------------------------ Labels: domain-mode (was: ) > Create operations to view the host and process controller log files > ------------------------------------------------------------------- > > Key: WFCORE-344 > URL: https://issues.jboss.org/browse/WFCORE-344 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: James Perkins > Assignee: James Perkins > Labels: domain-mode > > Operations need to exist somewhere so the {{host-controller.log}} and {{process-controller.log}} files can be read with a management operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-387?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-387: ------------------------------------ Labels: domain-mode (was: ) > 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 > Labels: domain-mode > > 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 (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[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 updated WFCORE-389: ------------------------------------ Labels: EAP domain-mode (was: EAP) > 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, domain-mode > Fix For: 4.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 (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1110) Allow addition of HTTP headers to management console responses

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1110?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFCORE-1110. -------------------------------------- Resolution: Out of Date We now set X-Frame-Options "SAMEORIGIN". If something else is also wanted please file a separate JIRA with the specific use case. > Allow addition of HTTP headers to management console responses > -------------------------------------------------------------- > > Key: WFCORE-1110 > URL: https://issues.jboss.org/browse/WFCORE-1110 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: James Livingston > Assignee: Darran Lofthouse > Labels: eap > > It would be useful to be able to add additional HTTP headers to the responses from the web management console, such as X-Frame-Options. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-298) Provide configuration to define when config changes are pushed to servers in a domain

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-298?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-298: ------------------------------------ Affects Version/s: domain-mode > Provide configuration to define when config changes are pushed to servers in a domain > ------------------------------------------------------------------------------------- > > Key: WFCORE-298 > URL: https://issues.jboss.org/browse/WFCORE-298 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: domain-mode > Reporter: Brian Stansberry > Labels: EAP > > An EAP customer request: > Right now, any changes done via the CLI to an active profile are pushed to all instances immediately. Some go life, some at reload only > While batch mode can be used to bundle a number of changes in one go, there is currently no way to tell individual servers or server-groups when to accept updates or not. > This proposal is to allow a config switch on servergroup level and on individual server level to accept a configuration change selectively: > 1. immediate, the current situation, being the default > 2. at restart only > 3. at explicit being told so, e.g. when a "reload" is ordered > Example: > <server name="server-three" group="other-server-group" updates="immediate"> > the default when the attribute is absent > <server name="server-three" group="other-server-group" updates="start"> > <server name="server-three" group="other-server-group" updates="explicit"> > The latter could then be triggered with: > /host=master/server-config=server1:reload > Similar option could be set on servergroup level, with a similar reload command on that level -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 March 2017