Re: Prep'ing whimsy-vm4 (was prep'ing whimsy-vm3)

2017-04-15 Thread Sam Ruby 
On Sat, Apr 15, 2017 at 1:12 PM, Shane Curcuru  wrote:
>
> Error: https://whimsy4.apache.org/status/
>
> "\xE2" on US-ASCII

Fixed.  Thanks!

> But there are a few errors in the /members/log that talk about ruby
> version differences, dunno if they will affect tools.

These messages should go away once this fix is merged and released:

https://github.com/whitequark/parser/pull/342

- Sam Ruby

RECOVERY: whimsy.apache.org (whimsy.apache.org (https)) is back up!

2017-04-15 Thread Ping My Box 
Hi there!
The service at whimsy.apache.org (whimsy.apache.org (https)) seems to be back 
in working order.

With regards,
Ping My Box - https://www.pingmybox.com/

ALERT: whimsy.apache.org (whimsy.apache.org (https)) is DOWN!

2017-04-15 Thread Ping My Box 

Hi there!
The service at whimsy.apache.org (whimsy.apache.org (https)) appears to be down 
from multiple locations around the world.

The exact error is:

Error component: response
Error code: Internal Server Error or equivalent bad message received: HTTP/1.1 
400 system puppet {:exception=>{:level=>"danger", :text=>"#", 
:data=>["/x1/srv/whimsy/www/status/monitors/system.rb:16:in `system'", 
"/x1/srv/whimsy/www/status/monitor.rb:55:in `block (3 levels) in initialize'"]}}
Debug output:
[Sat Apr 15 19:35:12 2017]: Initialising socket
[Sat Apr 15 19:35:12 2017]: Looking up hostname whimsy.apache.org...
[Sat Apr 15 19:35:12 2017]: Connecting to 207.244.88.137:443
[Sat Apr 15 19:35:13 2017]: Connected, sending HTTPS payload.
[Sat Apr 15 19:35:13 2017]: Analyzing server certificate
[Sat Apr 15 19:35:13 2017]: Saving certificate data
[Sat Apr 15 19:35:13 2017]: Reading response header from server
[Sat Apr 15 19:35:13 2017]: Caught exception: Internal Server Error or 
equivalent bad message received: HTTP/1.1 400 system puppet 
{:exception=>{:level=>"danger", :text=>"#", 
:data=>["/x1/srv/whimsy/www/status/monitors/system.rb:16:in `system'", 
"/x1/srv/whimsy/www/status/monitor.rb:55:in `block (3 levels) in initialize'"]}}





With regards,
Ping My Box - https://www.pingmybox.com/

Re: How to add a new Mentor?

2017-04-15 Thread Sam Ruby 
On Sat, Apr 15, 2017 at 10:23 AM, John D. Ament  wrote:
> On Sat, Apr 15, 2017 at 10:14 AM Sam Ruby  wrote:
>
>> TL;DR: can you ask an existing mentor to make the necessary changes?
>> (preferably not me :-))
>>
>>
> I just checked on another project, I don't see an option.  Where is the
> option to say "Mentor"?

The roster page shows the list of people in a PPMC. If a given person
is listed in podlings.xml as a mentor, that information is reflected
on the list -- but that would only happen if the mentor was on the
list.

There currently is no option to directly add a mentor; but that could
also be added.  Meanwhile, mentors need to be added separately to the
list in LDAP using this tool, and added to podlings.xml.

- Sam Ruby

>> On Sat, Apr 15, 2017 at 9:55 AM, John D. Ament 
>> wrote:
>> > How do I add a new Mentor via the Whimsy tool?  Tom Barber was added as a
>> > mentor to ODF Toolkit, but doesn't appear at
>> > https://whimsy.apache.org/roster/ppmc/odftoolkit
>>
>> The list was initially populated from:
>>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml
>>
>> > I can't access it based on current access rights.
>>
>> Any member on that list has access rights.  The thought is that each
>> group should maintain their own membership list.  I suggest that much
>> like how the board doesn't maintain PMC lists, but rather oversees
>> changes; perhaps the IPMC should play a similar role?
>>
>> Also note: those lists should be the entire PPMC, not just the
>> mentors.  Consider asking each PPMC to review their rosters?
>>
>> And I haven't forgotten the request to support podlings that have
>> committers that aren't PPMC members.  I just haven't gotten around to
>> it yet.
>>
>> > Does IPMC chair have access?
>>
>> Not currently.  In fact, currently there is no LDAP group for IPMC chair.
>>
>> If the IPMC wants something different, it would need to identify
>> either an existing group or propose the creation of a new one; and the
>> following file would need to be modified to grant the necessary
>> permissions:
>>
>>
>> https://github.com/apache/infrastructure-puppet/blob/deployment/modules/ldapserver/templates/slapd.conf.erb#L148
>>
>> > John
>>
>> - Sam Ruby
>>

Re: Prep'ing whimsy-vm4 (was prep'ing whimsy-vm3)

2017-04-15 Thread Shane Curcuru 
Sam Ruby wrote on 4/15/17 7:35 AM:
> Just under a year ago, we moved to whimsy-vm3; yesterday, I started
> building whimsy-vm4.
> 
> The biggest change is moving to Ubuntu 14.04; whimsy-vm3 is based on
> Ubuntu 12.04.
> 
> So far things look to be moving smoothly, if things go well, I'll do
> the switch after the board meeting and then ask that whimsy-vm3 be
> decommissioned.
> 
> https://issues.apache.org/jira/browse/INFRA-12716
> https://whimsy4.apache.org/

Error: https://whimsy4.apache.org/status/

"\xE2" on US-ASCII

backtrace:

/usr/local/rvm/gems/ruby-2.4.1/gems/json-2.0.4/lib/json/common.rb:286:in
`encode'

/usr/local/rvm/gems/ruby-2.4.1/gems/json-2.0.4/lib/json/common.rb:286:in
`generate'

/usr/local/rvm/gems/ruby-2.4.1/gems/json-2.0.4/lib/json/common.rb:286:in
`pretty_generate'
  /x1/srv/whimsy/www/status/monitor.rb:99:in `block in initialize'
  /x1/srv/whimsy/www/status/monitor.rb:31:in `open'
  /x1/srv/whimsy/www/status/monitor.rb:31:in `initialize'
  /x1/srv/whimsy/www/status/index.cgi:12:in `new'
  /x1/srv/whimsy/www/status/index.cgi:12:in `'

Spot check of several other tools looks fine.

Other changes, none of which should matter:
- ruby 2.3.1 -> 2.4.1
- Apache/2.4.7 - 2.4.18
- mod_ssl/2.4.7 - 2.4.18
- OpenSSL/1.0.1f -> 1.0.2g

But there are a few errors in the /members/log that talk about ruby
version differences, dunno if they will affect tools.

- Shane

-- 

- Shane
  https://www.apache.org/foundation/marks/resources

Re: Prep'ing whimsy-vm4 (was prep'ing whimsy-vm3)

2017-04-15 Thread Sam Ruby 
I hadn't set those things up yet.  I have now.

Let me know if there are other things that need to be attended to.
The only known problem that I haven't resolved yet is the board agenda
notification isn't set up.

I'm not sure yet what the problem is with roll call - it certainly has
improved but isn't quite there yet;  before asking for more RAM or CPU
cores, I would like to verify that that will address the problem.
Previous problems with the board agenda notification system are what
motivated the previous increases in RAM and CPUs, but neither
addressed the problem.

- Sam Ruby

On Sat, Apr 15, 2017 at 7:35 AM, Sam Ruby  wrote:
> Just under a year ago, we moved to whimsy-vm3; yesterday, I started
> building whimsy-vm4.
>
> The biggest change is moving to Ubuntu 14.04; whimsy-vm3 is based on
> Ubuntu 12.04.
>
> So far things look to be moving smoothly, if things go well, I'll do
> the switch after the board meeting and then ask that whimsy-vm3 be
> decommissioned.
>
> https://issues.apache.org/jira/browse/INFRA-12716
> https://whimsy4.apache.org/
>
> - Sam Ruby
>
> On Sat, Apr 23, 2016 at 10:49 AM, Sam Ruby  wrote:
>> 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

Re: Tooling for: Your Apache ICLA has gone missing

2017-04-15 Thread Sam Ruby 
On Sat, Apr 15, 2017 at 11:21 AM, Craig Russell  wrote:
> So how do we handle this?
>
> We need to remove the iclas.txt entry for edalquist, which I can do manually. 
> We also need to remove the LDAP entry, which I do not even know how to do.

Sebb would argue that the ID should be disabled, not removed.  Whether
it is disabling or removing, currently this authority is reserved by
the infrastructure team to themselves.  What could be done is a delete
account request, much like we currently have a create account request.

Should the ID be removed, it would also need to be removed from each
group that this individual is a member of:

https://whimsy.apache.org/roster/committer/edalquist

> Is there a chance we can add a button to the icla-lint whimsy page to do both 
> of these?

I generally shy away from writing code that I don't have the karma to test.  :-)

> Craig

- Sam Ruby

>> Begin forwarded message:
>>
>> From: Eric Dalquist 
>> Subject: Re: Your Apache ICLA has gone missing
>> Date: April 15, 2017 at 8:15:30 AM PDT
>> To: Craig Russell , edalqu...@apache.org
>> Cc: Secretary 
>>
>> Thanks for letting me know. Unfortunately my current situation prevents me 
>> from submitting an ICLA so I should likely be removed as an eligible Apache 
>> committer for now.
>>
>> Thanks,
>> -Eric Dalquist
>>
>> On Sat, Apr 15, 2017 at 8:09 AM Craig Russell > > wrote:
>> Dear Eric Dalquist,
>>
>> We are reviewing our records to be sure that all submitted ICLAs are on file.
>> Unfortunately, we are unable to locate the ICLA that you submitted earlier.
>>
>> Can you please resubmit to secret...@apache.org 
>> ? http://apache.org/licenses/#submitting 
>> 
>> Please do *not* use an apache email as your E-Mail address.
>> You can send the original ICLA (if the email address is still valid) or a 
>> new one.
>>
>> Best regards,
>>
>>
>> Craig L Russell
>> Secretary, Apache Software Foundation
>> c...@apache.org  http://db.apache.org/jdo 
>> 
>>
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org  http://db.apache.org/jdo 
>

Tooling for: Your Apache ICLA has gone missing

2017-04-15 Thread Craig Russell 
So how do we handle this?

We need to remove the iclas.txt entry for edalquist, which I can do manually. 
We also need to remove the LDAP entry, which I do not even know how to do.

Is there a chance we can add a button to the icla-lint whimsy page to do both 
of these?

Craig

> Begin forwarded message:
> 
> From: Eric Dalquist 
> Subject: Re: Your Apache ICLA has gone missing
> Date: April 15, 2017 at 8:15:30 AM PDT
> To: Craig Russell , edalqu...@apache.org
> Cc: Secretary 
> 
> Thanks for letting me know. Unfortunately my current situation prevents me 
> from submitting an ICLA so I should likely be removed as an eligible Apache 
> committer for now.
> 
> Thanks,
> -Eric Dalquist
> 
> On Sat, Apr 15, 2017 at 8:09 AM Craig Russell  > wrote:
> Dear Eric Dalquist,
> 
> We are reviewing our records to be sure that all submitted ICLAs are on file.
> Unfortunately, we are unable to locate the ICLA that you submitted earlier.
> 
> Can you please resubmit to secret...@apache.org 
> ? http://apache.org/licenses/#submitting 
> 
> Please do *not* use an apache email as your E-Mail address.
> You can send the original ICLA (if the email address is still valid) or a new 
> one.
> 
> Best regards,
> 
> 
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org  http://db.apache.org/jdo 
> 
> 

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org  http://db.apache.org/jdo

Re: How to add a new Mentor?

2017-04-15 Thread John D. Ament 
On Sat, Apr 15, 2017 at 10:14 AM Sam Ruby  wrote:

> TL;DR: can you ask an existing mentor to make the necessary changes?
> (preferably not me :-))
>
>
I just checked on another project, I don't see an option.  Where is the
option to say "Mentor"?


> On Sat, Apr 15, 2017 at 9:55 AM, John D. Ament 
> wrote:
> > How do I add a new Mentor via the Whimsy tool?  Tom Barber was added as a
> > mentor to ODF Toolkit, but doesn't appear at
> > https://whimsy.apache.org/roster/ppmc/odftoolkit
>
> The list was initially populated from:
>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml
>
> > I can't access it based on current access rights.
>
> Any member on that list has access rights.  The thought is that each
> group should maintain their own membership list.  I suggest that much
> like how the board doesn't maintain PMC lists, but rather oversees
> changes; perhaps the IPMC should play a similar role?
>
> Also note: those lists should be the entire PPMC, not just the
> mentors.  Consider asking each PPMC to review their rosters?
>
> And I haven't forgotten the request to support podlings that have
> committers that aren't PPMC members.  I just haven't gotten around to
> it yet.
>
> > Does IPMC chair have access?
>
> Not currently.  In fact, currently there is no LDAP group for IPMC chair.
>
> If the IPMC wants something different, it would need to identify
> either an existing group or propose the creation of a new one; and the
> following file would need to be modified to grant the necessary
> permissions:
>
>
> https://github.com/apache/infrastructure-puppet/blob/deployment/modules/ldapserver/templates/slapd.conf.erb#L148
>
> > John
>
> - Sam Ruby
>

Re: Prep'ing whimsy-vm4 (was prep'ing whimsy-vm3)

2017-04-15 Thread Craig Russell 
I took whimsy-vm4 out for a spin.

Members cross-check: #
watch list ok
proxy ok
incubator moderators: #
pmc-chair-board list: #

Secretary items: lint test ok, public names ok; 
secmail encountered internal server error.

My main concern with the smaller machine is response time during board meetings 
with a dozen active users. Roll call is still problematic even with whimsy-vm3.

Not ready for prime time for secretary day-to-day use. 

Regards,

Craig

> On Apr 15, 2017, at 4:35 AM, Sam Ruby  wrote:
> 
> Just under a year ago, we moved to whimsy-vm3; yesterday, I started
> building whimsy-vm4.
> 
> The biggest change is moving to Ubuntu 14.04; whimsy-vm3 is based on
> Ubuntu 12.04.
> 
> So far things look to be moving smoothly, if things go well, I'll do
> the switch after the board meeting and then ask that whimsy-vm3 be
> decommissioned.
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_INFRA-2D12716&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=CrXrn0QB6Ne46yqB_lv65fFZQ1QJlCJIbxCewrP5Zfg&s=JUgAGw-xlypF2d4ieDen87-RExIL2DHrgxSDPFXqdO8&e=
>  
> https://urldefense.proofpoint.com/v2/url?u=https-3A__whimsy4.apache.org_&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=CrXrn0QB6Ne46yqB_lv65fFZQ1QJlCJIbxCewrP5Zfg&s=H5v44CkzlhhTF4EjCpl2ylXrAvjpR-PWabkU-LQHLbs&e=
>  
> 
> - Sam Ruby
> 
> On Sat, Apr 23, 2016 at 10:49 AM, Sam Ruby  wrote:
>> We just got settled into whimsy-vm2, and I've already started working on
>> whimsy-vm3.
>> 
>> The precipitating factor was
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_INFRA-2D11723&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=CrXrn0QB6Ne46yqB_lv65fFZQ1QJlCJIbxCewrP5Zfg&s=gXjooqkYZI6-tcf9Del293CFVktyk6SMgJkTBeinHr0&e=
>>  ; 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://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_INFRA-2D11725&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=CrXrn0QB6Ne46yqB_lv65fFZQ1QJlCJIbxCewrP5Zfg&s=eqaasOEMoCJESZzVL-oEa79AnqKVvQRt7NJBfwrGMaU&e=
>>  
>> 
>> As a testament to puppet, the site is already sorta there
>> (https://urldefense.proofpoint.com/v2/url?u=http-3A__whimsy3.apache.org&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=CrXrn0QB6Ne46yqB_lv65fFZQ1QJlCJIbxCewrP5Zfg&s=UKGtXmIReSXGX8-LanOzUtZfopI8nCXoj6XZbYUtZKs&e=
>>  ), 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

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org http://db.apache.org/jdo

Re: How to add a new Mentor?

2017-04-15 Thread Sam Ruby 
TL;DR: can you ask an existing mentor to make the necessary changes?
(preferably not me :-))

On Sat, Apr 15, 2017 at 9:55 AM, John D. Ament  wrote:
> How do I add a new Mentor via the Whimsy tool?  Tom Barber was added as a
> mentor to ODF Toolkit, but doesn't appear at
> https://whimsy.apache.org/roster/ppmc/odftoolkit

The list was initially populated from:
https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml

> I can't access it based on current access rights.

Any member on that list has access rights.  The thought is that each
group should maintain their own membership list.  I suggest that much
like how the board doesn't maintain PMC lists, but rather oversees
changes; perhaps the IPMC should play a similar role?

Also note: those lists should be the entire PPMC, not just the
mentors.  Consider asking each PPMC to review their rosters?

And I haven't forgotten the request to support podlings that have
committers that aren't PPMC members.  I just haven't gotten around to
it yet.

> Does IPMC chair have access?

Not currently.  In fact, currently there is no LDAP group for IPMC chair.

If the IPMC wants something different, it would need to identify
either an existing group or propose the creation of a new one; and the
following file would need to be modified to grant the necessary
permissions:

https://github.com/apache/infrastructure-puppet/blob/deployment/modules/ldapserver/templates/slapd.conf.erb#L148

> John

- Sam Ruby

How to add a new Mentor?

2017-04-15 Thread John D. Ament 
How do I add a new Mentor via the Whimsy tool?  Tom Barber was added as a
mentor to ODF Toolkit, but doesn't appear at
https://whimsy.apache.org/roster/ppmc/odftoolkit

I can't access it based on current access rights.

Does IPMC chair have access?

John

Prep'ing whimsy-vm4 (was prep'ing whimsy-vm3)

2017-04-15 Thread Sam Ruby 
Just under a year ago, we moved to whimsy-vm3; yesterday, I started
building whimsy-vm4.

The biggest change is moving to Ubuntu 14.04; whimsy-vm3 is based on
Ubuntu 12.04.

So far things look to be moving smoothly, if things go well, I'll do
the switch after the board meeting and then ask that whimsy-vm3 be
decommissioned.

https://issues.apache.org/jira/browse/INFRA-12716
https://whimsy4.apache.org/

- Sam Ruby

On Sat, Apr 23, 2016 at 10:49 AM, Sam Ruby  wrote:
> 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