Hi Peter,

To respond to your first question:

On Tue, Aug 18, 2015 at 6:50 PM, Peter Murray pmurray@chillco.com wrote:

Excellent question. Haven't (at least yet) found a JIRA around this. Am
seeing the following in my June 22, 2015 correspondence with Richard and
Chad, on the topic of the Puppet-based installer:

install on a generic Tomcat 7 server folder, rather than requiring our '
sourdough starter' tarball.

I believe that's a goal that Richard has had for some time, which was the
context for using "revisit" in this sentence.

I haven't tried doing an install on a generic Tomcat folder in a long
time; it might be most interesting to see what differs, following a vanilla
install of v4.2, between CSpace-provided and generic Tomcat 7 folders. It's
entirely conceivable that the need for a special Tomcat distribution might
now be legacy/lore, or could be made such with a few tweaks to the
deployment. (Richard might possibly have more insights into the history of
and need for this.)

It should be possible to do an automated directory diff between the
CSpace-provided distribution and the Apache-supplied one. On OS X for
instance, the 'bbdiff' tool (part of the commercial BBEdit text editor
package and possibly also included with the vendor's no-cost TextWrangler,
a 'lite' version of that editor), might do a decent job of this.

As well, although this is indirect, you can find a link to the script
which generates the CSpace-provided distribution, along with a high-level
summary of the actions it performs, in the 'warning' block at the top of
this now-obsolete document:

https://wiki.collectionspace.org/display/collectionspace/Creating+the+Tarballs+-+Detailed+Description

This script is typically run on the QA server when a release has been
finalized, and its source is a Tomcat folder that was built, via continuous
integration, using the relevant release branch or tag.

Aron

Thanks for the pointing to the "Creating the Tarballs" page the the corresponding shell script.  That looks to be helpful in sorting this out.

I found that there are significant differences between the two (see https://gist.github.com/dltj/f126b340cc0ec45f3bce https://gist.github.com/dltj/f126b340cc0ec45f3bce), but I suppose the only way for me to find out is to run the ant deploy against a stock Tomcat 7.0.57 and see what happens.  It seems like a good thing to invest time in because if there are no other changes (or even just a few), then I can use a role from the Ansible Galaxy to manage the Tomcat installation and configuration.

I'll report back what I find.

Peter

--
Peter Murray
Dev/Ops Lead and Project Manager
Cherry Hill Company

Thanks, Peter - really appreciate your diving into this investigation!

On Wed, Aug 19, 2015 at 7:45 AM, Peter Murray pmurray@chillco.com wrote:

Peter,

The "custom" Apache Tomcat distribution we use is derived from the Nuxeo version that is being used by CollectionSpace.  Because of CollectionSpace's strong dependency on Nuxeo, it's been easier to use Nuxeo's Tomcat distribution for their DM product.  We've never had a hard requirement or even a request to use a "vanilla" Tomcat distribution.  Therefore we've never made it a priority.

If you think it should be a priority (or if it is for you), please create a JIRA and ask the community to weigh in with their thoughts.

Thanks,

Richard

From: Talk talk-bounces@lists.collectionspace.org on behalf of Aron Roberts aron@socrates.berkeley.edu
Sent: Wednesday, August 19, 2015 8:23 AM
To: Peter Murray
Cc: CollectionSpace Talk List
Subject: Re: [Talk] Difference between cspace-server-4.2 and Tomcat 7.0.57 distribution?

Thanks, Peter - really appreciate your diving into this investigation!

On Wed, Aug 19, 2015 at 7:45 AM, Peter Murray <pmurray@chillco.commailto:pmurray@chillco.com> wrote:
Thanks for the pointing to the "Creating the Tarballs" page the the corresponding shell script.  That looks to be helpful in sorting this out.

I found that there are significant differences between the two (see https://gist.github.com/dltj/f126b340cc0ec45f3bce), but I suppose the only way for me to find out is to run the ant deploy against a stock Tomcat 7.0.57 and see what happens.  It seems like a good thing to invest time in because if there are no other changes (or even just a few), then I can use a role from the Ansible Galaxy to manage the Tomcat installation and configuration.

I'll report back what I find.

Peter

On Aug 18, 2015, at 10:26 PM, Aron Roberts <aron@socrates.berkeley.edumailto:aron@socrates.berkeley.edu> wrote:

Hi Peter,

To respond to your first question:

On Tue, Aug 18, 2015 at 6:50 PM, Peter Murray <pmurray@chillco.commailto:pmurray@chillco.com> wrote:
The installation instructions call for downloading a customized Tomcat distribution from:

ftp://nightly.collectionspace.org/pub/collectionspace/releases/4.2/cspace-server-4.2.tar.gz

I tried to find a page on the wiki that describes what is different between the CSpace-provided distribution and the Apache-supplied Tomcat, but couldn't locate one.  And it looks like the ant undeploy deploy create_db -Drecreate_db=true import will put everything in the right place in the Tomcat setup.  What am I missing?

Excellent question. Haven't (at least yet) found a JIRA around this. Am seeing the following in my June 22, 2015 correspondence with Richard and Chad, on the topic of the Puppet-based installer:

I believe that's a goal that Richard has had for some time, which was the context for using "revisit" in this sentence.

I haven't tried doing an install on a generic Tomcat folder in a long time; it might be most interesting to see what differs, following a vanilla install of v4.2, between CSpace-provided and generic Tomcat 7 folders. It's entirely conceivable that the need for a special Tomcat distribution might now be legacy/lore, or could be made such with a few tweaks to the deployment. (Richard might possibly have more insights into the history of and need for this.)

It should be possible to do an automated directory diff between the CSpace-provided distribution and the Apache-supplied one. On OS X for instance, the 'bbdiff' tool (part of the commercial BBEdit text editor package and possibly also included with the vendor's no-cost TextWrangler, a 'lite' version of that editor), might do a decent job of this.

As well, although this is indirect, you can find a link to the script which generates the CSpace-provided distribution, along with a high-level summary of the actions it performs, in the 'warning' block at the top of this now-obsolete document:

https://wiki.collectionspace.org/display/collectionspace/Creating+the+Tarballs+-+Detailed+Description

This script is typically run on the QA server when a release has been finalized, and its source is a Tomcat folder that was built, via continuous integration, using the relevant release branch or tag.

Aron

Also, the ant create_db -Drecreate_db=true command is decidedly not idempotent, which from an Ansible frame of mind is really a bad thing.  Has anyone developed a test (in the build.xml file or elsewhere) to see if the create_db step is necessary?

Peter

--
Peter Murray
Dev/Ops Lead and Project Manager
Cherry Hill Company

Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Richard,

Does this imply that, starting with v4.2, the tarball of the Apache
Tomcat 7 folder, distributed via the CollectionSpace FTP site, is now taken
'as-is' from the Nuxeo DM distribution?

(At least through v4.1, we'd been preparing it via the script mentioned
earlier in this thread.)

Thanks,
Aron

On Wed, Aug 19, 2015 at 11:06 AM, Richard Millet <richard.millet@lyrasis.org

Almost.  Starting with CollectionSpace v4.2, the tarball of the Apache Tomcat 7 folder is derived from (a derivative of) the one from the Nuxeo 6.0 DM distribution -not taken "as-is."

From: aronroberts@gmail.com aronroberts@gmail.com on behalf of Aron Roberts aron@socrates.berkeley.edu
Sent: Wednesday, August 19, 2015 11:13 AM
To: Richard Millet
Cc: Peter Murray; CollectionSpace Talk List
Subject: Re: [Talk] Difference between cspace-server-4.2 and Tomcat 7.0.57 distribution?

Richard,

Does this imply that, starting with v4.2, the tarball of the Apache Tomcat 7 folder, distributed via the CollectionSpace FTP site, is now taken 'as-is' from the Nuxeo DM distribution?

(At least through v4.1, we'd been preparing it via the script mentioned earlier in this thread.)

Thanks,
Aron

On Wed, Aug 19, 2015 at 11:06 AM, Richard Millet <richard.millet@lyrasis.orgmailto:richard.millet@lyrasis.org> wrote:

Peter,

The "custom" Apache Tomcat distribution we use is derived from the Nuxeo version that is being used by CollectionSpace.  Because of CollectionSpace's strong dependency on Nuxeo, it's been easier to use Nuxeo's Tomcat distribution for their DM product.  We've never had a hard requirement or even a request to use a "vanilla" Tomcat distribution.  Therefore we've never made it a priority.

If you think it should be a priority (or if it is for you), please create a JIRA and ask the community to weigh in with their thoughts.

Thanks,

Richard

From: Talk <talk-bounces@lists.collectionspace.orgmailto:talk-bounces@lists.collectionspace.org> on behalf of Aron Roberts <aron@socrates.berkeley.edumailto:aron@socrates.berkeley.edu>
Sent: Wednesday, August 19, 2015 8:23 AM
To: Peter Murray
Cc: CollectionSpace Talk List
Subject: Re: [Talk] Difference between cspace-server-4.2 and Tomcat 7.0.57 distribution?

Thanks, Peter - really appreciate your diving into this investigation!

On Wed, Aug 19, 2015 at 7:45 AM, Peter Murray <pmurray@chillco.commailto:pmurray@chillco.com> wrote:
Thanks for the pointing to the "Creating the Tarballs" page the the corresponding shell script.  That looks to be helpful in sorting this out.

I found that there are significant differences between the two (see https://gist.github.com/dltj/f126b340cc0ec45f3bce), but I suppose the only way for me to find out is to run the ant deploy against a stock Tomcat 7.0.57 and see what happens.  It seems like a good thing to invest time in because if there are no other changes (or even just a few), then I can use a role from the Ansible Galaxy to manage the Tomcat installation and configuration.

I'll report back what I find.

Peter

On Aug 18, 2015, at 10:26 PM, Aron Roberts <aron@socrates.berkeley.edumailto:aron@socrates.berkeley.edu> wrote:

Hi Peter,

To respond to your first question:

On Tue, Aug 18, 2015 at 6:50 PM, Peter Murray <pmurray@chillco.commailto:pmurray@chillco.com> wrote:
The installation instructions call for downloading a customized Tomcat distribution from:

ftp://nightly.collectionspace.org/pub/collectionspace/releases/4.2/cspace-server-4.2.tar.gz

I tried to find a page on the wiki that describes what is different between the CSpace-provided distribution and the Apache-supplied Tomcat, but couldn't locate one.  And it looks like the ant undeploy deploy create_db -Drecreate_db=true import will put everything in the right place in the Tomcat setup.  What am I missing?

Excellent question. Haven't (at least yet) found a JIRA around this. Am seeing the following in my June 22, 2015 correspondence with Richard and Chad, on the topic of the Puppet-based installer:

I believe that's a goal that Richard has had for some time, which was the context for using "revisit" in this sentence.

I haven't tried doing an install on a generic Tomcat folder in a long time; it might be most interesting to see what differs, following a vanilla install of v4.2, between CSpace-provided and generic Tomcat 7 folders. It's entirely conceivable that the need for a special Tomcat distribution might now be legacy/lore, or could be made such with a few tweaks to the deployment. (Richard might possibly have more insights into the history of and need for this.)

It should be possible to do an automated directory diff between the CSpace-provided distribution and the Apache-supplied one. On OS X for instance, the 'bbdiff' tool (part of the commercial BBEdit text editor package and possibly also included with the vendor's no-cost TextWrangler, a 'lite' version of that editor), might do a decent job of this.

As well, although this is indirect, you can find a link to the script which generates the CSpace-provided distribution, along with a high-level summary of the actions it performs, in the 'warning' block at the top of this now-obsolete document:

https://wiki.collectionspace.org/display/collectionspace/Creating+the+Tarballs+-+Detailed+Description

This script is typically run on the QA server when a release has been finalized, and its source is a Tomcat folder that was built, via continuous integration, using the relevant release branch or tag.

Aron

Also, the ant create_db -Drecreate_db=true command is decidedly not idempotent, which from an Ansible frame of mind is really a bad thing.  Has anyone developed a test (in the build.xml file or elsewhere) to see if the create_db step is necessary?

Peter

--
Peter Murray
Dev/Ops Lead and Project Manager
Cherry Hill Company

Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Ah. Hmmm.  So the CSpace tarball starts from http://nuxeo.github.io/downloads.html#6.0 http://nuxeo.github.io/downloads.html#6.0 then has some other things applied to it.  Okay -- this is getting too far into the weeds, so I'll go down the path of using the CSpace provided Tomcat tarball.  I'm just a little nervous about this, as there has been one security patch to Tomcat since 7.0.57 (https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.59 https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.59).  I don't plan to deploy malicious webapps in the container, so this probably doesn't matter.  Still, we'll be relying on two upstream providers (Apache to Nuxeo to CSpace to us) to provide updates to Tomcat when we need it...

Peter

--
Peter Murray
Dev/Ops Lead and Project Manager
Cherry Hill Company