[jboss-jira] [JBoss JIRA] (WFLY-5000) Undertow mod_cluster CLI: Control Context: Disable Stop
Stuart Douglas (JIRA)
issues at jboss.org
Thu Jul 23 17:49:02 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart Douglas moved UNDERTOW-495 to WFLY-5000:
-----------------------------------------------
Project: WildFly (was: Undertow)
Key: WFLY-5000 (was: UNDERTOW-495)
Issue Type: Feature Request (was: Bug)
Affects Version/s: (was: 1.3.0.Beta3)
Component/s: Web (Undertow)
(was: Proxy)
> Undertow mod_cluster CLI: Control Context: Disable Stop
> -------------------------------------------------------
>
> Key: WFLY-5000
> URL: https://issues.jboss.org/browse/WFLY-5000
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Michal Karm Babacek
> Assignee: Stuart Douglas
> Priority: Critical
> Labels: mod_cluster
>
> As a follow up to JBEAP-215, this bug report is a member of a series addressing crucial CLI management capabilities.
> h3. Control Contexts
> For any Undertow mod_cluster proxy environment, it is essential to be able to Enable, Disable and Stop a particular Context on a selected worker Node.
> It is an equivalent of sending the following MCMP message attributes. Note that the command depends on {{JVMRoute}} - for a Node selction and on an {{Alias}} - for one of the Aliases a particular {{Context}} is configured with.
> * Enable context {{Cmd=ENABLE-APP&Range=CONTEXT&JVMRoute=worker-2&Alias=karm.brq.redhat.com&Context=/clusterbench}}
> * Disable context {{Cmd=DISABLE-APP&Range=CONTEXT&JVMRoute=worker-2&Alias=karm.brq.redhat.com&Context=/clusterbench}}
> * Stop context {{Cmd=STOP-APP&Range=CONTEXT&JVMRoute=worker-2&Alias=karm.brq.redhat.com&Context=/clusterbench}}
> h3. Call to action
> Enable user to carry out these actions via WildFly CLI.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list