We just got settled into whimsy-vm2, and I've already started working on
whimsy-vm3.
The precipitating factor was
https://issues.apache.org/jira/browse/INFRA-11723; where the solution
was to cache content that was statically being served by Apache httpd to
another machine on another network... where it would be statically
served by Apache httpd.
This supports the notion that the problem is either the network or the
proxy. So I requested and obtained a new VM on a different colo
facility and network:
https://issues.apache.org/jira/browse/INFRA-11725
As a testament to puppet, the site is already sorta there
(http://whimsy3.apache.org), the largest thing missing is the svn
checkouts that the code requires.
Note that for the moment, the site is accessed via http instead of
https; that's because this vm is NOT currently accessed via a proxy.
I'd like to keep it that way at least initially so that can more easily
determine where the actual problem lies. I'm working out the mechanics
of obtaining an SSL cert for this, and that should be resolved in a few
days.
If all goes well, I'll ask that the DNS entry for whimsy.apache.org to
be updated to point to whimsy-vm3 before the next board meeting, and
then to release whimsy-vm2 after that point.
The original whimsy-vm still hosts some unrelated tools (e.g.,
infra.apache.org and etherpad), and that would need to be addressed
before that machine is released.
- Sam Ruby
