March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2066) Kill and destroy operations on the server-group

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2066?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2066: ------------------------------------- Labels: domain-mode (was: ) > Kill and destroy operations on the server-group > ----------------------------------------------- > > Key: WFCORE-2066 > URL: https://issues.jboss.org/browse/WFCORE-2066 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Yeray Borges Santana > Labels: domain-mode > > The server-config resources expose kill and destroy operations; it would be useful to have these on the server-group as well. If some problem (e.g. a bad deployment) is causing all servers in the group to hang it is nice to be able to kill/destroy them in one op versus having to identify all members and kill them individually. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3) Host Controller should check for and react to changes in its directory-grouping setting when starting servers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFCORE-3: ---------------------------------- Labels: domain-mode (was: ) > Host Controller should check for and react to changes in its directory-grouping setting when starting servers > -------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3 > URL: https://issues.jboss.org/browse/WFCORE-3 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Labels: domain-mode > > If a user changes the /host=x directory-grouping setting after an HC has already launched servers, when those servers get restarted their data/ dir will be in a new location and any content in the old location will be lost. It would be nice if the HC could detect this situation and try to migrate the data to the new location. > Something like: > 1) See if there is an existing data/ dir at the expected location per the current directory-grouping setting. > 2) If yes, done. > 3) If no, work out what the expected location would be per the other valid directory-grouping settings. (Should only be one alternative, but this algorithm doesn't assume that will remain the case.) > 3) If there is one and only one such location that has an existing data/ dir, copy its contents to the new location. > 4) If there is more than one such location, log a WARN. > 5) If there is a problem copying the contents, log an ERROR, remove whatever partial bits were successfully copied and proceed on. (An alternative is to fail to start the server and force the user to deal with the situation.) > This is borderline minor as this is an edge case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-710) Make ServerOperationResolver handle deployment-overlays similarly to deployments

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-710?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-710: ------------------------------------ Labels: domain-mode (was: ) > Make ServerOperationResolver handle deployment-overlays similarly to deployments > -------------------------------------------------------------------------------- > > Key: WFCORE-710 > URL: https://issues.jboss.org/browse/WFCORE-710 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 2.0.0.Alpha2 > Reporter: Kabir Khan > Labels: domain-mode > > Currently in domain mode a > {code} > /deployment-overlay=xxx:add(...) > {code} > results in a deployment overlay on ALL servers. > However for deployments > {code} > /deployment=xxx:add(...) > {code} > does not get pushed to the servers. This happens when it is associated with a server group: > {code} > /server-group=zzz/deployment=xxx:add(...) > {code} > Similarly > {code} > /deployment-overlay=xxx:add(...) > {code} > should not get pushed to the servers, until we have a > {code} > /server-group=zzz/deployment=yyy:add(...) > {code} > which picks out the servers we want to have the overlay -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-817) Reflect suspend state in server-config resource, similar to server resource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-817?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-817: ------------------------------------ Labels: domain-mode (was: ) > Reflect suspend state in server-config resource, similar to server resource > ----------------------------------------------------------------------------- > > Key: WFCORE-817 > URL: https://issues.jboss.org/browse/WFCORE-817 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Ken Wills > Labels: domain-mode > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

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 Brian Stansberry (JIRA)

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

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1415) SensitivityClassification for process lifecycle actions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1415?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1415: ------------------------------------- Labels: domain-mode (was: ) > SensitivityClassification for process lifecycle actions > ------------------------------------------------------- > > Key: WFCORE-1415 > URL: https://issues.jboss.org/browse/WFCORE-1415 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security > Reporter: Brian Stansberry > Labels: domain-mode > > Add a sensitivity classification that will be applied to all operations that affect process lifecycle (start/stop/shutdown/restart/suspend/resume) at the various levels (host, server, server-group, server-config). Make it possible to restrict such operations to Administrator/SuperUser roles. > Before anyone starts work on this, discuss with [~harald.pehl] to ensure there's a plan in place for dealing with any impact on the console. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1318) Create an Azure equivalent to the S3 variant of Domain Controller discovery

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1318?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1318: ------------------------------------- Labels: domain-mode (was: ) > Create an Azure equivalent to the S3 variant of Domain Controller discovery > --------------------------------------------------------------------------- > > Key: WFCORE-1318 > URL: https://issues.jboss.org/browse/WFCORE-1318 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Labels: domain-mode > > WildFly Core includes an analogoue to JGroups's S3_PING discovery protocol that can be used for slave discovery of the DC on Amazon's EC2 cloud. See https://developer.jboss.org/people/fjuma/blog/2013/03/15/a-domain-control... for details. > This JIRA is to create an equivalent for Azure. Should use the same configuration style as what Farah did for S3 (generic classname + module + properties; no strongly typed schema.) > Anyone working on this should contact [~rhusar] early in the process, as he has done work on an Azure equivalent to S3_PING for use in JGroups channels. Ping me too for preliminary discussion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-938) Embedded host controller doesn't support --admin-mode=false option

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-938?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-938: ------------------------------------ Labels: domain-mode (was: ) > Embedded host controller doesn't support --admin-mode=false option > ------------------------------------------------------------------ > > Key: WFCORE-938 > URL: https://issues.jboss.org/browse/WFCORE-938 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management > Affects Versions: 2.0.0.Beta4 > Reporter: Petr Kremensky > Assignee: Ken Wills > Labels: domain-mode > > Embedded standalone instance supports two running modes depending on a value of admin-only option (true is default). > * *true* > ** only start services related to server administration > ** do not start other services or accept end user requests. > ** embedded instance will not be visible to remote management clients > * *false* > ** all services are started > ** embedded instance is visible to remote management clients (e.g. EAP can be configured via admin console) > Embedded host controller doesn't offer such a option and is started using --admin-only=true mode by default. Option to run embedded host controller instance with --admin-only=false should be available as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1531) The HC shutdown operation should accept a restart-servers param like reload does

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1531?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1531: ------------------------------------- Labels: domain-mode (was: ) > The HC shutdown operation should accept a restart-servers param like reload does > -------------------------------------------------------------------------------- > > Key: WFCORE-1531 > URL: https://issues.jboss.org/browse/WFCORE-1531 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management > Reporter: Brian Stansberry > Labels: domain-mode > > If a user uses a management op to restart the HC, e.g. one of these: > {code} > [domain@localhost:9990 /] /host=master:shutdown(restart=true) > {"outcome" => "success"} > [domain@localhost:9990 /] shutdown --host=master --restart=true > {code} > then they should also be able to configure restart-servers=false so the servers remain alive and reconnect to the HC when the PC spawns a new one. > Doing "kill -9 <hc_pid>" works fine, with the PC spawning a new HC and the servers reconnecting, so it seems the main thing here is adding the parameter and wiring in the mechanicsm such that the ServerInventory doesn't stop the servers. Perhaps the same thing can be done as HostProcessReloadHandler does, using HostRunningModeControl.setRestartMode(). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1521) Autostart order in domain mode

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1521?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1521: ------------------------------------- Labels: domain-mode (was: ) > Autostart order in domain mode > ------------------------------ > > Key: WFCORE-1521 > URL: https://issues.jboss.org/browse/WFCORE-1521 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Guillermo González de Agüero > Labels: domain-mode > > When defining servers in domain mode, they can be marked to be autostarted, but an order of starting cannot be specified (they'll start in parallel). A new option could be added to start one server only after others have already started. A server start would be posponed until all servers with lower order have already finished. > An example use case would be a server that requires some resources of another one (JMS queues for example). > This can be easily achieved with a CLI batch command, but it would be simpler to have it available out of the box. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

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