[LTER-im] Drupal 6 funeral and the IM site.

[Inigo San Gil]

We started a migration repository 
<https://github.com/lter/imc-migration>, and run a deep analysis 
<https://docs.google.com/spreadsheets/d/1ISAm8B8KTzGSTXpAWK4-0WSGjzpEsNAiDwO3SW27ts4/edit?usp=sharing> 
of the IM site composition and structure.

The only thing in our way is a snapshot of the database, and a copy of 
the files directory. This does not take a series of meetings, 
strategical decisions, it just takes FIVE minutes of somebody's time at 
NCEAS.  Perhaps it would be even faster (1 minutes) to open me a shell 
account, so I can perform those ops myself.  May be there is a trust 
issue, who knows?

I am not asking NCEAS to host a secure, more modern version of the IM 
site - but I want to give the IMs a chance to preserve the content 
before is too late, and content becomes locked and too costly to be 
migrated.  It is really much more simple than all that.

Inigo

-- 

Inigo San Gil
+1 505 277 2625
http://scholar.google.com/citations?user=foIppL4AAAAJ&hl=en





On 6/6/16 5:25 PM, Matt Jones wrote:
> Hello IMs --
>
> Just wanted to follow up with a few details about the web site 
> migration.  In consultation with Corinna and others at EDI (formerly 
> NIMO), and with support from James at LNO, we migrated the LTER 
> informational web sites to the NCO, and have been operating them for 
> the last several months, including handling necessary security 
> updates.  Marty met with Corinna and others from EDI last week to 
> discuss how to move the IM site (and other data oriented sites) over 
> to the EDI.  What became clear is that there are still some decisions 
> to be made as the role of the EDI gets better defined with respect to 
> LTER and other non-LTER groups like OBFS and macrosystems projects.  
> So, for the time being, we will continue to operate the web sites at 
> NCO, at least until EDI is operational; at that point, some portion of 
> the content that makes sense may be moved over to EDI or elsewhere, 
> depending on what the IM community and EDI wants to do.  So, thanks, 
> Inigo, for the offer, but at this time its probably best not to 
> separate the IM site from the other other Drupal instances at LTER 
> that it is intertwined with -- we'll get it and the other sites 
> upgraded to D7 and continue to provide access to IMs via their LDAP 
> logins.  More info as Corinna et al. get operational at EDI...
>
> Best regards,
>
> Matt
>
> --
> Matthew B. Jones
> LTER Network Communications Office
> http://www.lternet.edu
>
> Director of Informatics R&D
> National Center for Ecological Analysis and Synthesis
> University of California Santa Barbara
> http://www.nceas.ucsb.edu/ecoinfo
>
> Co-PI, DataONE
> https://dataone.org
>
> PI, NSF Arctic Data Center
> https://arcticdata.io
>
>
>
>
>
>
> On Fri, Jun 3, 2016 at 7:37 AM, Inigo San Gil <isangil at lternet.edu 
> <mailto:isangil at lternet.edu>> wrote:
>
>
>     IMs,
>
>     Drupal 6 (D6) End of support came in the early spring of 2016. A
>     couple of weeks ago, we attended a proper funeral, New Orleans
>     style. Very emotional event, as you can imagine.
>
>     I thought I would offer to move the IM site to a supported
>     platform (hint: the IM site runs on D6), perhaps clean it up a
>     bit, and make it mobile friendly.  Not a lot of work, but it is
>     not for the faint of heart, as the site hosts over 1,000 nodes,
>     which to you it means at least 1,000 pages of content. With the
>     combinations and relationships, it makes up a wealth of information.
>
>     The information is now at some risk, when the next critical
>     vulnerability hits, we would probably scramble for a fix. Or not,
>     but it wont be as easy as it is with a supported product.  That is
>     why I offered to update the site.
>
>     James Brunt offered an out-of-date snapshot of the database, but
>     it would be really better to hit the production database, so
>     content can be migrated once and again -- there is no need for
>     downtimes, no operational disruptions. Except, that is, the lack
>     of responsiveness.
>
>     For this I need the cooperation of the new hosts, the NCEAS.  We
>     sent them an email over 10 days ago.  I sent them a reminder 8
>     days ago.
>
>     All I need is ONE of two SIMPLE things:
>     -- Either shell access to the server hosting the IM site
>     OR
>     -- 2 files: a mysqldump file of the back end database, and the
>     "files" directory of that site.
>
>     I got one answer that asked me to wait (???) for a meeting last week.
>
>     It has been over two weeks since my initial offer.  If this is
>     going to be the MO of the NCEAS, I would suggest we host the IM
>     site ourselves (whether in our servers, or in a cloud instance).
>     Same fate with Databits.  If we insist on having NCEAS providing
>     this sort of service, you can help by reminding NCEAS about
>     turnaround times and service expectations, specially for simple
>     things that entail 5 mins of their time.
>
>     Inigo
>
>
>     -- 
>
>     Inigo San Gil
>     http://scholar.google.com/citations?user=foIppL4AAAAJ&hl=en
>
>     _______________________________________________
>     Long Term Ecological Research Network
>     im mailing list
>     im at lternet.edu <mailto:im at lternet.edu>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lternet.edu/pipermail/im/attachments/20160606/b58f38ab/attachment.html>