[Maas-devel] Replacing Apache

[Gavin Panella]

On 28 November 2014 at 12:53, Christian Robottom Reis
<kiko at canonical.com> wrote:
> On Thu, Nov 27, 2014 at 07:05:23PM +0000, Gavin Panella wrote:
>> On 27 November 2014 at 18:44, Christian Robottom Reis
>> <kiko at canonical.com> wrote:
>> > On Thu, Nov 27, 2014 at 04:03:23PM +0000, Gavin Panella wrote:
>> >> On 27 November 2014 at 16:00, Christian Robottom Reis wrote:
>> >> > Could that be provided as a legacy option? In other words, new installs
>> >> > would run Apache-less on port 80/443, but old installs would leave
>> >> > Apache in-place with a proxy entry.
>> >>
>> >> We could, but I think I'd prefer to just make the switch. Each option
>> >> increases our bug surface, and spreads our time more thinly.
>> >
>> > Hmm, it's not clear what you mean by "the switch" in this case. Do you
>> > mean always keeping Apache around, or something else?
>>
>> Sorry. I mean getting rid of Apache entirely.
>
> Right -- but AFAICT the only way we can actually do that (without
> forbidding the use of the region server for any other web service) is
> the first alternative I suggested, which is having regiond listen on a
> separate port. Or am I missing something?

If regiond were to be the only thing on that machine, then it could go
on 80/443. As Mark has said, that's not cool, so a separate port would
be necessary. My regiond branch uses 5243.

Something else: if we run regionds on multiple machines we'd want
haproxy or similar in front, so maybe the same is suitable for
single-machine environments.

In any case, HA should feed into our choice, but I think we should
deploy MAAS via Juju before we get too involved in HA, otherwise we risk
reimplementing all of its wiring-up logic ourselves, badly.

Gavin.