[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-531) Stop advocating and remove auto-magic aspects from the project

[Radoslav Husar (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar updated MODCLUSTER-531:
--------------------------------------
    Description: 
I am proposing we abandon automagic as much as possible.

h1. Problem

The main idea for automagic is to make deployment simple and easy to migrate/transfer and provide great user experience out of box. Unfortunately, this IMHO often backfires quite significantly resulting in configurations that are:
# insecure (listening on all interfaces, allow from all, default security key "changeme!")
# difficult to debug (not clear what is the actual configuration)
# unstable installations (seemingly unrelated aspects like adding an interface can break advertised address)

h1. Areas

There are several areas where automagic happens.

h5. Advertised address of the proxy

There were multiple bugs in the past, where 0.0.0.0 would be sent in the advertise mesages, now if its not explcit in the VirtualHost or passed in to ServerAdvertise, it automagically picks a non-local interface. Such configurations should be disallowed.

h5. Connector selection

This is solved in WildFly where selection is explicit. In tomcat this causes problems like MODCLUSTER-457 when WS requires http yet ajp is automatically selected by default. We can make this explicit.



  was:
I am proposing we abandon automagic as much as possible.

Problem

The main idea for automagic is to make deployment simple and easy to migrate/transfer and provide great user experience out of box. Unfortunately, this IMHO often backfires quite significantly resulting in configurations that are:
# insecure (listening on all interfaces, allow from all, default security key "changeme!")
# difficult to debug (not clear what is the actual configuration)
# unstable installations (seemingly unrelated aspects like adding an interface can break advertised address)

Th



> Stop advocating and remove auto-magic aspects from the project
> --------------------------------------------------------------
>
>                 Key: MODCLUSTER-531
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-531
>             Project: mod_cluster
>          Issue Type: Enhancement
>          Components: Core & Container Integration (Java), Documentation & Demos, Native (httpd modules)
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>
> I am proposing we abandon automagic as much as possible.
> h1. Problem
> The main idea for automagic is to make deployment simple and easy to migrate/transfer and provide great user experience out of box. Unfortunately, this IMHO often backfires quite significantly resulting in configurations that are:
> # insecure (listening on all interfaces, allow from all, default security key "changeme!")
> # difficult to debug (not clear what is the actual configuration)
> # unstable installations (seemingly unrelated aspects like adding an interface can break advertised address)
> h1. Areas
> There are several areas where automagic happens.
> h5. Advertised address of the proxy
> There were multiple bugs in the past, where 0.0.0.0 would be sent in the advertise mesages, now if its not explcit in the VirtualHost or passed in to ServerAdvertise, it automagically picks a non-local interface. Such configurations should be disallowed.
> h5. Connector selection
> This is solved in WildFly where selection is explicit. In tomcat this causes problems like MODCLUSTER-457 when WS requires http yet ajp is automatically selected by default. We can make this explicit.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)