[jboss-jira] [JBoss JIRA] (WFLY-4992) Undertow mod_cluster CLI: proxy: Display node's Aliases
Michal Karm Babacek (JIRA)
issues at jboss.org
Thu Aug 27 11:17:05 EDT 2015
[ https://issues.jboss.org/browse/WFLY-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Karm Babacek closed WFLY-4992.
-------------------------------------
Closed. Verified in Beta9.
{code}
"aliases" => [
"default-host",
"localhost"
]
{code}
> Undertow mod_cluster CLI: proxy: Display node's Aliases
> -------------------------------------------------------
>
> Key: WFLY-4992
> URL: https://issues.jboss.org/browse/WFLY-4992
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Michal Karm Babacek
> Assignee: Stuart Douglas
> Priority: Blocker
> Labels: mod_cluster
> Fix For: 10.0.0.Beta1
>
>
> As a follow up to JBEAP-215, this bug report is a member of a series addressing crucial CLI management capabilities.
> h3. Display node's Aliases
> At the moment, this is all there is to see:
> {noformat}
> "balancer" => {
> "qa_balancer" => {"node" => {"worker-2" => {
> "load" => 89,
> "status" => "NODE_UP",
> "context" => {"/clusterbench" => {
> "requests" => 0,
> "status" => "enabled"
> }}
> }}},
> ...
> {noformat}
> h3. Call to action
> We need to display node's aliases, e.g.
> {noformat}
> Aliases:
> karm.brq.redhat.com
> localhost
> default-host
> {noformat}
> (an example from the current Apache HTTP Server mod_manager implementation)
> {color:red}Blocker{color} priority justification: Numerous Aliases are fundamental to common user environments and they are necessary for several crucial test scenarios. Without this information available via CLI, it would be impossible to manage any Aliases sensitive setup.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list