whimsy-vm switchover

[Sam Ruby <ru...@intertwingly.net>]

Over the next few days, I plan to work with the infrastructure staff to 
change things so that https://whimsy.apache.org/ is proxied to 
whimsy-vm2 (currently only accessible via 
https://whimsy-test.apache.org/).  This may cause applications to break.

For a period of time (currently not defined) the original VM will still 
be kept around, and will be accessible via an alternate URL.

- Sam RUby

Re: whimsy-vm switchover

[Sam Ruby <ru...@intertwingly.net>]

On Sun, Feb 21, 2016 at 4:15 PM, Sam Ruby <ru...@intertwingly.net> wrote:
> Over the next few days, I plan to work with the infrastructure staff to
> change things so that https://whimsy.apache.org/ is proxied to whimsy-vm2
> (currently only accessible via https://whimsy-test.apache.org/).  This may
> cause applications to break.

This is now done, pending DNS propagation.

> For a period of time (currently not defined) the original VM will still be
> kept around, and will be accessible via an alternate URL.

Original VM can be accessed via https://whimsy-old.apache.org/

New VM can continue to be accessed via https://whimsy-test.apache.org/

- Sam Ruby

Re: whimsy-vm switchover

[sebb <se...@gmail.com>]

On 23 February 2016 at 10:03, Sam Ruby <ru...@intertwingly.net> wrote:
> On Tue, Feb 23, 2016 at 4:30 AM, sebb <se...@gmail.com> wrote:
>> This does not appear to have happened yet.
>
> Indeed, it has not.  I've now opened a JIRA issue to track this
> https://issues.apache.org/jira/browse/INFRA-11311
>
>> Meanwhile, some of the fixes have not been applied to the live copy -
>> for example, I fixed non-participants.cgi to remove a spurious / from
>> the committer links (which are currently broken for me on whimsy, but
>> not whimsy-test)
>
> There is no auto-deploy on the original whimsy-vm.

I know.

I was just pointing out that that app has a bug on whimsy which is
fixed on whimsy-test.

> It is not my plan
> to update the software on that machine any more beyond adding an
> occasional redirect/reverse proxy for portions of the site that are
> accessed by tools (such as what I did for the public directory).  A
> possible exception being the board agenda tool, as the version on
> whimsy-vm2 has not yet been proven to stand up to the load of a board
> meeting.

> - Sam Ruby
>
>> On 21 February 2016 at 21:15, Sam Ruby <ru...@intertwingly.net> wrote:
>>> Over the next few days, I plan to work with the infrastructure staff to
>>> change things so that https://whimsy.apache.org/ is proxied to whimsy-vm2
>>> (currently only accessible via https://whimsy-test.apache.org/).  This may
>>> cause applications to break.
>>>
>>> For a period of time (currently not defined) the original VM will still be
>>> kept around, and will be accessible via an alternate URL.
>>>
>>> - Sam RUby

Re: whimsy-vm switchover

[Sam Ruby <ru...@intertwingly.net>]

On Tue, Feb 23, 2016 at 4:30 AM, sebb <se...@gmail.com> wrote:
> This does not appear to have happened yet.

Indeed, it has not.  I've now opened a JIRA issue to track this
https://issues.apache.org/jira/browse/INFRA-11311

> Meanwhile, some of the fixes have not been applied to the live copy -
> for example, I fixed non-participants.cgi to remove a spurious / from
> the committer links (which are currently broken for me on whimsy, but
> not whimsy-test)

There is no auto-deploy on the original whimsy-vm.  It is not my plan
to update the software on that machine any more beyond adding an
occasional redirect/reverse proxy for portions of the site that are
accessed by tools (such as what I did for the public directory).  A
possible exception being the board agenda tool, as the version on
whimsy-vm2 has not yet been proven to stand up to the load of a board
meeting.

- Sam Ruby

> On 21 February 2016 at 21:15, Sam Ruby <ru...@intertwingly.net> wrote:
>> Over the next few days, I plan to work with the infrastructure staff to
>> change things so that https://whimsy.apache.org/ is proxied to whimsy-vm2
>> (currently only accessible via https://whimsy-test.apache.org/).  This may
>> cause applications to break.
>>
>> For a period of time (currently not defined) the original VM will still be
>> kept around, and will be accessible via an alternate URL.
>>
>> - Sam RUby

Re: whimsy-vm switchover

[sebb <se...@gmail.com>]

This does not appear to have happened yet.

Meanwhile, some of the fixes have not been applied to the live copy -
for example, I fixed non-participants.cgi to remove a spurious / from
the committer links (which are currently broken for me on whimsy, but
not whimsy-test)

On 21 February 2016 at 21:15, Sam Ruby <ru...@intertwingly.net> wrote:
> Over the next few days, I plan to work with the infrastructure staff to
> change things so that https://whimsy.apache.org/ is proxied to whimsy-vm2
> (currently only accessible via https://whimsy-test.apache.org/).  This may
> cause applications to break.
>
> For a period of time (currently not defined) the original VM will still be
> kept around, and will be accessible via an alternate URL.
>
> - Sam RUby