Hi, I am building a CS 4.2 server on AWS Linux running Tomcat. The documentation for cspace-config.xml appears to be stale, and it is not clear whether there should be a cspace-config.xml file or multiple cspace-config-{tenantname}.xml files. It is also not clear where that file(s) should be placed. Help? Thanks, Cary

Hi Cary, Are you in the process of configuring CollectionSpace for a museum or collection? If so, the usual approach is: 1. Check out CollectionSpace's source code, for all three layers: Services, Application, and UI. 2. In each layer, create a new 'tenant' - a workspace within which you can make configuration changes specific to your museum or collection. 3. Make your configuration changes within that space. you're correct that 'cspace-config.xml' is obsolete, and that in its place there are now multiple cspace-config-{tenantname}.xml files. (I'm seeing that obsolete file still referenced in some legacy docs, and we'll endeavor to correct that - thanks for reminding us of that.) When you create your new tenant, via the 'tenant clone' tool, the cspace-config-{tenantname}.xml fille will be created for you in the correct location. The place I'd suggest you try starting out, if you haven't already, is with this document: https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-InstallCollectionSpace and especially, later on in that same document: https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway Existing tenants that you can 'clone' in an out-of-the-box v4.2 system are 'core' (generic), 'lifesci' (life sciences), and 'fcart' (fine and contemporary arts). Aron Roberts UC Berkeley On Wed, Jul 1, 2015 at 2:23 PM, Cary Gordon <listuser@chillco.com> wrote: > Hi, > > I am building a CS 4.2 server on AWS Linux running Tomcat. The > documentation for cspace-config.xml appears to be stale, and it is not > clear whether there should be a cspace-config.xml file or multiple > cspace-config-{tenantname}.xml files. It is also not clear where that > file(s) should be placed. > > Help? > > Thanks, > > Cary > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >

Hi Aron, The issue wasn’t the config files. It was something related to installing on AWS Linux. While I am sure that I could have resolved it in this lifetime, I decided to kill it off and go with Ubuntu to preserve what little remains of my spare time and sanity. The Ubuntu install worked fine. Thanks, Cary > On Jul 1, 2015, at 2:38 PM, Aron Roberts <aron@socrates.berkeley.edu> wrote: > > Hi Cary, > > Are you in the process of configuring CollectionSpace for a museum or collection? If so, the usual approach is: > > 1. Check out CollectionSpace's source code, for all three layers: Services, Application, and UI. > 2. In each layer, create a new 'tenant' - a workspace within which you can make configuration changes specific to your museum or collection. > 3. Make your configuration changes within that space. > > you're correct that 'cspace-config.xml' is obsolete, and that in its place there are now multiple cspace-config-{tenantname}.xml files. (I'm seeing that obsolete file still referenced in some legacy docs, and we'll endeavor to correct that - thanks for reminding us of that.) > > When you create your new tenant, via the 'tenant clone' tool, the cspace-config-{tenantname}.xml fille will be created for you in the correct location. The place I'd suggest you try starting out, if you haven't already, is with this document: > > https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-InstallCollectionSpace <https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-InstallCollectionSpace> > > and especially, later on in that same document: > > https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway <https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway> > > Existing tenants that you can 'clone' in an out-of-the-box v4.2 system are 'core' (generic), 'lifesci' (life sciences), and 'fcart' (fine and contemporary arts). > > Aron Roberts > UC Berkeley > > On Wed, Jul 1, 2015 at 2:23 PM, Cary Gordon <listuser@chillco.com <mailto:listuser@chillco.com>> wrote: > Hi, > > I am building a CS 4.2 server on AWS Linux running Tomcat. The documentation for cspace-config.xml appears to be stale, and it is not clear whether there should be a cspace-config.xml file or multiple cspace-config-{tenantname}.xml files. It is also not clear where that file(s) should be placed. > > Help? > > Thanks, > > Cary > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org <mailto:Talk@lists.collectionspace.org> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org <http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org> >

And, FWIW, the wiki download instructions mentioned in a previous post are still wrong. > On Jul 1, 2015, at 3:57 PM, Cary Gordon <listuser@chillco.com> wrote: > > Hi Aron, > > The issue wasn’t the config files. It was something related to installing on AWS Linux. While I am sure that I could have resolved it in this lifetime, I decided to kill it off and go with Ubuntu to preserve what little remains of my spare time and sanity. The Ubuntu install worked fine. > > Thanks, > > Cary > >> On Jul 1, 2015, at 2:38 PM, Aron Roberts <aron@socrates.berkeley.edu <mailto:aron@socrates.berkeley.edu>> wrote: >> >> Hi Cary, >> >> Are you in the process of configuring CollectionSpace for a museum or collection? If so, the usual approach is: >> >> 1. Check out CollectionSpace's source code, for all three layers: Services, Application, and UI. >> 2. In each layer, create a new 'tenant' - a workspace within which you can make configuration changes specific to your museum or collection. >> 3. Make your configuration changes within that space. >> >> you're correct that 'cspace-config.xml' is obsolete, and that in its place there are now multiple cspace-config-{tenantname}.xml files. (I'm seeing that obsolete file still referenced in some legacy docs, and we'll endeavor to correct that - thanks for reminding us of that.) >> >> When you create your new tenant, via the 'tenant clone' tool, the cspace-config-{tenantname}.xml fille will be created for you in the correct location. The place I'd suggest you try starting out, if you haven't already, is with this document: >> >> https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-InstallCollectionSpace <https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-InstallCollectionSpace> >> >> and especially, later on in that same document: >> >> https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway <https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway> >> >> Existing tenants that you can 'clone' in an out-of-the-box v4.2 system are 'core' (generic), 'lifesci' (life sciences), and 'fcart' (fine and contemporary arts). >> >> Aron Roberts >> UC Berkeley >> >> On Wed, Jul 1, 2015 at 2:23 PM, Cary Gordon <listuser@chillco.com <mailto:listuser@chillco.com>> wrote: >> Hi, >> >> I am building a CS 4.2 server on AWS Linux running Tomcat. The documentation for cspace-config.xml appears to be stale, and it is not clear whether there should be a cspace-config.xml file or multiple cspace-config-{tenantname}.xml files. It is also not clear where that file(s) should be placed. >> >> Help? >> >> Thanks, >> >> Cary >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org <mailto:Talk@lists.collectionspace.org> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org <http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org> >> >

Thanks, Cary! > The issue wasn’t the config files. It was something related to installing on AWS Linux. While I am sure that I could have resolved it in this lifetime, I decided to kill it off and go with Ubuntu to preserve what little remains of my spare time and sanity. The Ubuntu install worked fine. Great! Yes, if you were using the automated installer for v4.2, at the moment it has only been updated for, and tested with Ubuntu 14.04.1 LTS. I noticed that although one of the two relevant wiki pages was updated to reflect this, another was not. That page has also been updated: https://wiki.collectionspace.org/display/DOC/Automated+installer+for+CollectionSpace+4.2 AWS (AMI) Linux is RedHat Enterprise Linux (RHEL)-based, and the v4.2 installer wasn't specifically updated, from its v4.1 release, for RHEL or other RedHat-based LInux distros. That work remains to be done, via CSPACE-6721 <https://issues.collectionspace.org/browse/CSPACE-6721> and other issues. > And, FWIW, the wiki download instructions mentioned in a previous post are still wrong. This suggests that you might have been installing CollectionSpace manually on Ubuntu, rather than using the automated installer (mentioned above). Is that correct? If so, did you mean that the name of the tarball was incorrect, in the unpacking command on this page? https://wiki.collectionspace.org/display/DOC/Installing+4.2+on+Ubuntu+14.04 And in turn, if so, did you find that this is the appropriate correction? (I just made the following change on that page ...) https://wiki.collectionspace.org/pages/diffpagesbyversion.action?pageId=157221943&selectedPageVersions=3&selectedPageVersions=2 Thanks, Aron On Wed, Jul 1, 2015 at 3:57 PM, Cary Gordon <listuser@chillco.com> wrote: > Hi Aron, > > The issue wasn’t the config files. It was something related to installing > on AWS Linux. While I am sure that I could have resolved it in this > lifetime, I decided to kill it off and go with Ubuntu to preserve what > little remains of my spare time and sanity. The Ubuntu install worked fine. > > Thanks, > > Cary > > On Jul 1, 2015, at 2:38 PM, Aron Roberts <aron@socrates.berkeley.edu> > wrote: > > Hi Cary, > > Are you in the process of configuring CollectionSpace for a museum or > collection? If so, the usual approach is: > > 1. Check out CollectionSpace's source code, for all three layers: > Services, Application, and UI. > 2. In each layer, create a new 'tenant' - a workspace within which you > can make configuration changes specific to your museum or collection. > 3. Make your configuration changes within that space. > > you're correct that 'cspace-config.xml' is obsolete, and that in its > place there are now multiple cspace-config-{tenantname}.xml files. (I'm > seeing that obsolete file still referenced in some legacy docs, and we'll > endeavor to correct that - thanks for reminding us of that.) > > When you create your new tenant, via the 'tenant clone' tool, the > cspace-config-{tenantname}.xml fille will be created for you in the correct > location. The place I'd suggest you try starting out, if you haven't > already, is with this document: > > > https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-InstallCollectionSpace > > and especially, later on in that same document: > > > https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway > > Existing tenants that you can 'clone' in an out-of-the-box v4.2 system > are 'core' (generic), 'lifesci' (life sciences), and 'fcart' (fine and > contemporary arts). > > Aron Roberts > UC Berkeley > > On Wed, Jul 1, 2015 at 2:23 PM, Cary Gordon <listuser@chillco.com> wrote: > >> Hi, >> >> I am building a CS 4.2 server on AWS Linux running Tomcat. The >> documentation for cspace-config.xml appears to be stale, and it is not >> clear whether there should be a cspace-config.xml file or multiple >> cspace-config-{tenantname}.xml files. It is also not clear where that >> file(s) should be placed. >> >> Help? >> >> Thanks, >> >> Cary >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> > > >

I/we have conflated the Ubuntu and Yum-ish install docs. The download link is now correct on the Ubuntu manual install page — wget ftp://nightly.collectionspace.org/pub/collectionspace/releases/4.2/cspace-server-4.2.tar.gz <ftp://nightly.collectionspace.org/pub/collectionspace/releases/4.2/cspace-server-4.2.tar.gz> — and incorrect on the Yum page — wget ftp://nightly.collectionspace.org/pub/collectionspace/releases/4.2/apache-tomcat-7.0.57.tar.gz <ftp://nightly.collectionspace.org/pub/collectionspace/releases/4.2/apache-tomcat-7.0.57.tar.gz>. I tried to install manually on AWS Linux, which was a PITA as, among other things, the maven yum repo is broken. I ran the installer on Ubuntu and it worked. Personally, I prefer scripts — Ansible is my flavor of the month — to packaged installers, as they are easier to deal with if there are problems. Thanks, Cary > On Jul 1, 2015, at 5:05 PM, Aron Roberts <aron@socrates.berkeley.edu> wrote: > > Thanks, Cary! > > > The issue wasn’t the config files. It was something related to installing on AWS Linux. While I am sure that I could have resolved it in this lifetime, I decided to kill it off and go with Ubuntu to preserve what little remains of my spare time and sanity. The Ubuntu install worked fine. > > Great! Yes, if you were using the automated installer for v4.2, at the moment it has only been updated for, and tested with Ubuntu 14.04.1 LTS. I noticed that although one of the two relevant wiki pages was updated to reflect this, another was not. That page has also been updated: > > https://wiki.collectionspace.org/display/DOC/Automated+installer+for+CollectionSpace+4.2 <https://wiki.collectionspace.org/display/DOC/Automated+installer+for+CollectionSpace+4.2> > > AWS (AMI) Linux is RedHat Enterprise Linux (RHEL)-based, and the v4.2 installer wasn't specifically updated, from its v4.1 release, for RHEL or other RedHat-based LInux distros. That work remains to be done, via CSPACE-6721 <https://issues.collectionspace.org/browse/CSPACE-6721> and other issues. > > > And, FWIW, the wiki download instructions mentioned in a previous post are still wrong. > > This suggests that you might have been installing CollectionSpace manually on Ubuntu, rather than using the automated installer (mentioned above). Is that correct? > > If so, did you mean that the name of the tarball was incorrect, in the unpacking command on this page? > > https://wiki.collectionspace.org/display/DOC/Installing+4.2+on+Ubuntu+14.04 <https://wiki.collectionspace.org/display/DOC/Installing+4.2+on+Ubuntu+14.04> > > And in turn, if so, did you find that this is the appropriate correction? (I just made the following change on that page ...) > > https://wiki.collectionspace.org/pages/diffpagesbyversion.action?pageId=157221943&selectedPageVersions=3&selectedPageVersions=2 <https://wiki.collectionspace.org/pages/diffpagesbyversion.action?pageId=157221943&selectedPageVersions=3&selectedPageVersions=2> > > Thanks, > Aron > > > On Wed, Jul 1, 2015 at 3:57 PM, Cary Gordon <listuser@chillco.com <mailto:listuser@chillco.com>> wrote: > Hi Aron, > > The issue wasn’t the config files. It was something related to installing on AWS Linux. While I am sure that I could have resolved it in this lifetime, I decided to kill it off and go with Ubuntu to preserve what little remains of my spare time and sanity. The Ubuntu install worked fine. > > Thanks, > > Cary > >> On Jul 1, 2015, at 2:38 PM, Aron Roberts <aron@socrates.berkeley.edu <mailto:aron@socrates.berkeley.edu>> wrote: >> >> Hi Cary, >> >> Are you in the process of configuring CollectionSpace for a museum or collection? If so, the usual approach is: >> >> 1. Check out CollectionSpace's source code, for all three layers: Services, Application, and UI. >> 2. In each layer, create a new 'tenant' - a workspace within which you can make configuration changes specific to your museum or collection. >> 3. Make your configuration changes within that space. >> >> you're correct that 'cspace-config.xml' is obsolete, and that in its place there are now multiple cspace-config-{tenantname}.xml files. (I'm seeing that obsolete file still referenced in some legacy docs, and we'll endeavor to correct that - thanks for reminding us of that.) >> >> When you create your new tenant, via the 'tenant clone' tool, the cspace-config-{tenantname}.xml fille will be created for you in the correct location. The place I'd suggest you try starting out, if you haven't already, is with this document: >> >> https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-InstallCollectionSpace <https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-InstallCollectionSpace> >> >> and especially, later on in that same document: >> >> https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway <https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway> >> >> Existing tenants that you can 'clone' in an out-of-the-box v4.2 system are 'core' (generic), 'lifesci' (life sciences), and 'fcart' (fine and contemporary arts). >> >> Aron Roberts >> UC Berkeley >> >> On Wed, Jul 1, 2015 at 2:23 PM, Cary Gordon <listuser@chillco.com <mailto:listuser@chillco.com>> wrote: >> Hi, >> >> I am building a CS 4.2 server on AWS Linux running Tomcat. The documentation for cspace-config.xml appears to be stale, and it is not clear whether there should be a cspace-config.xml file or multiple cspace-config-{tenantname}.xml files. It is also not clear where that file(s) should be placed. >> >> Help? >> >> Thanks, >> >> Cary >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org <mailto:Talk@lists.collectionspace.org> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org <http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org> >> > >

Thanks for this feedback, Cary. And please kep it coming - it's really appreciated! We'll make sure that the Yum page gets updated with the correct tarball filename as well ... > I tried to install manually on AWS Linux, which was a PITA as, among other things, the maven yum repo is broken. Ouch! :) > Personally, I prefer scripts — Ansible is my flavor of the month — to packaged installers, as they are easier to deal with if there are problems. Agreed. Actually, the packaged installer is written in Puppet, so it can be readily debugged and tweaked if you encounter issues. (The installer has many limitations; it's never yet been used in a remote (agent) configuration, it still over-uses 'exec' - a callout to shell commands, and has other challenges, but it does work well on Ubuntu, and it's literally a fire-up-and-come-back to an installed server in 30 minutes tool.) I had a fair number of frustrations with Puppet, though, and SaltStack has drawn my interest. Have you used it? If so, how might you compare it with other configuration management tools you've used? Some of the LYRASIS folks use Ansible extensively, AIUI. If at any point you have cycles to talk with them about Ansible-based installers or other CollectionSpace tools, they might well be receptive. Aron On Fri, Jul 3, 2015 at 8:53 AM, Cary Gordon <listuser@chillco.com> wrote: > I/we have conflated the Ubuntu and Yum-ish install docs. The download link > is now correct on the Ubuntu manual install page — > wget > ftp://nightly.collectionspace.org/pub/collectionspace/releases/4.2/cspace-server-4.2.tar.gz — > and incorrect on the Yum page — > wget > ftp://nightly.collectionspace.org/pub/collectionspace/releases/4.2/apache-tomcat-7.0.57.tar.gz > . > > I tried to install manually on AWS Linux, which was a PITA as, among other > things, the maven yum repo is broken. > > I ran the installer on Ubuntu and it worked. > > Personally, I prefer scripts — Ansible is my flavor of the month — to > packaged installers, as they are easier to deal with if there are problems. > > Thanks, > > Cary > > On Jul 1, 2015, at 5:05 PM, Aron Roberts <aron@socrates.berkeley.edu> > wrote: > > Thanks, Cary! > > > The issue wasn’t the config files. It was something related to > installing on AWS Linux. While I am sure that I could have resolved it in > this lifetime, I decided to kill it off and go with Ubuntu to preserve what > little remains of my spare time and sanity. The Ubuntu install worked fine. > > Great! Yes, if you were using the automated installer for v4.2, at the > moment it has only been updated for, and tested with Ubuntu 14.04.1 LTS. I > noticed that although one of the two relevant wiki pages was updated to > reflect this, another was not. That page has also been updated: > > > https://wiki.collectionspace.org/display/DOC/Automated+installer+for+CollectionSpace+4.2 > > AWS (AMI) Linux is RedHat Enterprise Linux (RHEL)-based, and the v4.2 > installer wasn't specifically updated, from its v4.1 release, for RHEL or > other RedHat-based LInux distros. That work remains to be done, via > CSPACE-6721 <https://issues.collectionspace.org/browse/CSPACE-6721> and > other issues. > > > And, FWIW, the wiki download instructions mentioned in a previous post > are still wrong. > > This suggests that you might have been installing CollectionSpace manually > on Ubuntu, rather than using the automated installer (mentioned above). Is > that correct? > > If so, did you mean that the name of the tarball was incorrect, in the > unpacking command on this page? > > https://wiki.collectionspace.org/display/DOC/Installing+4.2+on+Ubuntu+14.04 > > And in turn, if so, did you find that this is the appropriate correction? > (I just made the following change on that page ...) > > > https://wiki.collectionspace.org/pages/diffpagesbyversion.action?pageId=157221943&selectedPageVersions=3&selectedPageVersions=2 > > Thanks, > Aron > > > On Wed, Jul 1, 2015 at 3:57 PM, Cary Gordon <listuser@chillco.com> wrote: > >> Hi Aron, >> >> The issue wasn’t the config files. It was something related to installing >> on AWS Linux. While I am sure that I could have resolved it in this >> lifetime, I decided to kill it off and go with Ubuntu to preserve what >> little remains of my spare time and sanity. The Ubuntu install worked fine. >> >> Thanks, >> >> Cary >> >> On Jul 1, 2015, at 2:38 PM, Aron Roberts <aron@socrates.berkeley.edu> >> wrote: >> >> Hi Cary, >> >> Are you in the process of configuring CollectionSpace for a museum or >> collection? If so, the usual approach is: >> >> 1. Check out CollectionSpace's source code, for all three layers: >> Services, Application, and UI. >> 2. In each layer, create a new 'tenant' - a workspace within which you >> can make configuration changes specific to your museum or collection. >> 3. Make your configuration changes within that space. >> >> you're correct that 'cspace-config.xml' is obsolete, and that in its >> place there are now multiple cspace-config-{tenantname}.xml files. (I'm >> seeing that obsolete file still referenced in some legacy docs, and we'll >> endeavor to correct that - thanks for reminding us of that.) >> >> When you create your new tenant, via the 'tenant clone' tool, the >> cspace-config-{tenantname}.xml fille will be created for you in the correct >> location. The place I'd suggest you try starting out, if you haven't >> already, is with this document: >> >> >> https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-InstallCollectionSpace >> >> and especially, later on in that same document: >> >> >> https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway >> >> Existing tenants that you can 'clone' in an out-of-the-box v4.2 system >> are 'core' (generic), 'lifesci' (life sciences), and 'fcart' (fine and >> contemporary arts). >> >> Aron Roberts >> UC Berkeley >> >> On Wed, Jul 1, 2015 at 2:23 PM, Cary Gordon <listuser@chillco.com> wrote: >> >>> Hi, >>> >>> I am building a CS 4.2 server on AWS Linux running Tomcat. The >>> documentation for cspace-config.xml appears to be stale, and it is not >>> clear whether there should be a cspace-config.xml file or multiple >>> cspace-config-{tenantname}.xml files. It is also not clear where that >>> file(s) should be placed. >>> >>> Help? >>> >>> Thanks, >>> >>> Cary >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >> >> >> > >

There are many tools available. We mostly use Ansible, Vagrant, and now Packer. I have looked at SaltStack, but did not find anything that would motivate me to add it. We do our Islandora builds with Ansible, and we are working on using Packer to let us deploy to either AWS instances or Docker containers (on AWS instances). Cary > On Jul 3, 2015, at 12:44 PM, Aron Roberts <aron@socrates.berkeley.edu> wrote: > > Thanks for this feedback, Cary. And please kep it coming - it's really appreciated! We'll make sure that the Yum page gets updated with the correct tarball filename as well ... > > > I tried to install manually on AWS Linux, which was a PITA as, among other things, the maven yum repo is broken. > > Ouch! :) > > > Personally, I prefer scripts — Ansible is my flavor of the month — to packaged installers, as they are easier to deal with if there are problems. > > Agreed. Actually, the packaged installer is written in Puppet, so it can be readily debugged and tweaked if you encounter issues. (The installer has many limitations; it's never yet been used in a remote (agent) configuration, it still over-uses 'exec' - a callout to shell commands, and has other challenges, but it does work well on Ubuntu, and it's literally a fire-up-and-come-back to an installed server in 30 minutes tool.) I had a fair number of frustrations with Puppet, though, and SaltStack has drawn my interest. Have you used it? If so, how might you compare it with other configuration management tools you've used? > > Some of the LYRASIS folks use Ansible extensively, AIUI. If at any point you have cycles to talk with them about Ansible-based installers or other CollectionSpace tools, they might well be receptive. > > Aron > > On Fri, Jul 3, 2015 at 8:53 AM, Cary Gordon <listuser@chillco.com <mailto:listuser@chillco.com>> wrote: > I/we have conflated the Ubuntu and Yum-ish install docs. The download link is now correct on the Ubuntu manual install page — > wget ftp://nightly.collectionspace.org/pub/collectionspace/releases/4.2/cspace-server-4.2.tar.gz <ftp://nightly.collectionspace.org/pub/collectionspace/releases/4.2/cspace-server-4.2.tar.gz> — and incorrect on the Yum page — > wget ftp://nightly.collectionspace.org/pub/collectionspace/releases/4.2/apache-tomcat-7.0.57.tar.gz <ftp://nightly.collectionspace.org/pub/collectionspace/releases/4.2/apache-tomcat-7.0.57.tar.gz>. > > I tried to install manually on AWS Linux, which was a PITA as, among other things, the maven yum repo is broken. > > I ran the installer on Ubuntu and it worked. > > Personally, I prefer scripts — Ansible is my flavor of the month — to packaged installers, as they are easier to deal with if there are problems. > > Thanks, > > Cary > >> On Jul 1, 2015, at 5:05 PM, Aron Roberts <aron@socrates.berkeley.edu <mailto:aron@socrates.berkeley.edu>> wrote: >> >> Thanks, Cary! >> >> > The issue wasn’t the config files. It was something related to installing on AWS Linux. While I am sure that I could have resolved it in this lifetime, I decided to kill it off and go with Ubuntu to preserve what little remains of my spare time and sanity. The Ubuntu install worked fine. >> >> Great! Yes, if you were using the automated installer for v4.2, at the moment it has only been updated for, and tested with Ubuntu 14.04.1 LTS. I noticed that although one of the two relevant wiki pages was updated to reflect this, another was not. That page has also been updated: >> >> https://wiki.collectionspace.org/display/DOC/Automated+installer+for+CollectionSpace+4.2 <https://wiki.collectionspace.org/display/DOC/Automated+installer+for+CollectionSpace+4.2> >> >> AWS (AMI) Linux is RedHat Enterprise Linux (RHEL)-based, and the v4.2 installer wasn't specifically updated, from its v4.1 release, for RHEL or other RedHat-based LInux distros. That work remains to be done, via CSPACE-6721 <https://issues.collectionspace.org/browse/CSPACE-6721> and other issues. >> >> > And, FWIW, the wiki download instructions mentioned in a previous post are still wrong. >> >> This suggests that you might have been installing CollectionSpace manually on Ubuntu, rather than using the automated installer (mentioned above). Is that correct? >> >> If so, did you mean that the name of the tarball was incorrect, in the unpacking command on this page? >> >> https://wiki.collectionspace.org/display/DOC/Installing+4.2+on+Ubuntu+14.04 <https://wiki.collectionspace.org/display/DOC/Installing+4.2+on+Ubuntu+14.04> >> >> And in turn, if so, did you find that this is the appropriate correction? (I just made the following change on that page ...) >> >> https://wiki.collectionspace.org/pages/diffpagesbyversion.action?pageId=157221943&selectedPageVersions=3&selectedPageVersions=2 <https://wiki.collectionspace.org/pages/diffpagesbyversion.action?pageId=157221943&selectedPageVersions=3&selectedPageVersions=2> >> >> Thanks, >> Aron >> >> >> On Wed, Jul 1, 2015 at 3:57 PM, Cary Gordon <listuser@chillco.com <mailto:listuser@chillco.com>> wrote: >> Hi Aron, >> >> The issue wasn’t the config files. It was something related to installing on AWS Linux. While I am sure that I could have resolved it in this lifetime, I decided to kill it off and go with Ubuntu to preserve what little remains of my spare time and sanity. The Ubuntu install worked fine. >> >> Thanks, >> >> Cary >> >>> On Jul 1, 2015, at 2:38 PM, Aron Roberts <aron@socrates.berkeley.edu <mailto:aron@socrates.berkeley.edu>> wrote: >>> >>> Hi Cary, >>> >>> Are you in the process of configuring CollectionSpace for a museum or collection? If so, the usual approach is: >>> >>> 1. Check out CollectionSpace's source code, for all three layers: Services, Application, and UI. >>> 2. In each layer, create a new 'tenant' - a workspace within which you can make configuration changes specific to your museum or collection. >>> 3. Make your configuration changes within that space. >>> >>> you're correct that 'cspace-config.xml' is obsolete, and that in its place there are now multiple cspace-config-{tenantname}.xml files. (I'm seeing that obsolete file still referenced in some legacy docs, and we'll endeavor to correct that - thanks for reminding us of that.) >>> >>> When you create your new tenant, via the 'tenant clone' tool, the cspace-config-{tenantname}.xml fille will be created for you in the correct location. The place I'd suggest you try starting out, if you haven't already, is with this document: >>> >>> https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-InstallCollectionSpace <https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-InstallCollectionSpace> >>> >>> and especially, later on in that same document: >>> >>> https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway <https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant#Creatingyournewtenant-Theeasyway> >>> >>> Existing tenants that you can 'clone' in an out-of-the-box v4.2 system are 'core' (generic), 'lifesci' (life sciences), and 'fcart' (fine and contemporary arts). >>> >>> Aron Roberts >>> UC Berkeley >>> >>> On Wed, Jul 1, 2015 at 2:23 PM, Cary Gordon <listuser@chillco.com <mailto:listuser@chillco.com>> wrote: >>> Hi, >>> >>> I am building a CS 4.2 server on AWS Linux running Tomcat. The documentation for cspace-config.xml appears to be stale, and it is not clear whether there should be a cspace-config.xml file or multiple cspace-config-{tenantname}.xml files. It is also not clear where that file(s) should be placed. >>> >>> Help? >>> >>> Thanks, >>> >>> Cary >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org <mailto:Talk@lists.collectionspace.org> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org <http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org> >>> >> >> > >