www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Ruby (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-10530) Ubuntu 14.04 vm for whimsy (to replace 12.04 whimsy-vm)
Date Fri, 23 Oct 2015 17:51:27 GMT

    [ https://issues.apache.org/jira/browse/INFRA-10530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971456#comment-14971456
] 

Sam Ruby commented on INFRA-10530:
----------------------------------

> I guess the largest question(s): Is there a list of *all*
> the folders/folder structures required for whimsy to operate
> (that is also up to date)? I'm digging through the whimsy-vm
> right now, the whimsy README, and the whimsy vagrant folder,
> but it's all trial and error.

I'll be brutally honest, the answer to that question is no.
There are pieces that are up to date, and pieces that
aren't.  And no good overall map; at least not one that has
been read and verified by somebody other than myself.

That's why I would expect a dialog would be useful.  I'll go
first.

Craig mentioned three tools: secretary workbench, secmail,
and the board agenda tool.  That's a good cross section to
work with.

I'll start with a preamble that whimsy was originally
created as a minimal VM (IIRC, apache httpd wasn't even
installed) and nearly everything was installed by me.

---

The secretary workbench is a set of CGI scripts.  Source is
at /var/tools/secretary/documents/received.  Deployment is
currently:

  'cd /var/www/whimsy', 'sudo svn cleanup', 'sudo svn up'

Being a CGI means that there is an additional second or two
overhead to every request with the current VM.  Not great,
but livable.  It could become a long running service with a
few small changes.  See discussion on the board agenda tool
below.

It also depends on a number of Ruby gems and programs like
pdftk and gpg.  And on having a number of svn directories
checked out like
https://svn.apache.org/repos/private/documents/iclas.  It
has a configuration file at
/var/tools/www/secretary/workbench/local_paths.yml.  It
keeps state in a yaml file at 
/var/tools/secretary/documents/received/pending.yml.

As for the "gut reaction" part, I apologize. I was trying to
be honest but I guess what I was trying to say did not come
across clearly. On the surface, svnpubsub does not look like
it is suitable for whimsy due to infra's deployment
requirements. However, I do not have enough understanding of
the whimsy service to back that up at this time. Once I do
have an understanding of the core whimsy service, I will
open a dialogue on what options are available but also fit
within infra's deployment requirements and will also ask for
input as there are undoubtedly other means that I may not be
familiar with that could also meet infra's deployment
requirements.

---

secmail isn't even run on whimsy-vm.  Documentation for it
can be found at:

https://svn.apache.org/repos/infra/infrastructure/trunk/docs/services/secmail.txt

This tool is likely to be impacted in an unknown way by the
infrastructure plans to redo how mail at the ASF is handled.

---

The board agenda tool is located here:

https://github.com/rubys/whimsy-agenda

Instructions for building a vagrant VM, a docker image, and
installing it locally on either Ubuntu or Mac OS/X are
provided.  There also is a test suite.

This runs as a separate service (reversed proxied from
Apache httpd).  The service is managed by Ubuntu's upstart.
Deployment is currently:

  sudo /srv/puma/agenda/deploy.sh

This tool is the closest I have in terms of up to date instructions that 
have been (at least partially) tested by others.

---

> As for the "gut reaction" part, I apologize. I was trying to
> be honest but I guess what I was trying to say did not come
> across clearly. On the surface, svnpubsub does not look like
> it is suitable for whimsy due to infra's deployment
> requirements. However, I do not have enough understanding of
> the whimsy service to back that up at this time. Once I do
> have an understanding of the core whimsy service, I will
> open a dialogue on what options are available but also fit
> within infra's deployment requirements and will also ask for
> input as there are undoubtedly other means that I may not be
> familiar with that could also meet infra's deployment
> requirements.

I'm still looking for an answer as to why
projects.apache.org and reporter.apache.org are exempt from
these infrastructure requirements.

> Ubuntu 14.04 vm for whimsy (to replace 12.04 whimsy-vm)
> -------------------------------------------------------
>
>                 Key: INFRA-10530
>                 URL: https://issues.apache.org/jira/browse/INFRA-10530
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: Sam Ruby
>            Assignee: Geoffrey Corey
>
> Current VM for Whimsy is running 12.04; which should be retired over time.  Please set
up a new VM for whimsy accessible via the web under a new name during the transition.  Once
set up and verified, the existing VM can be taken down



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message