Move arcticdata.io (Production) to Kubernetes

[artntek]

Similar to #1932;

checklist:

• Work with @nickatnceas to copy production data for testing:
  • Time how long it takes to...

    • Copy the production postgres data (arcticdata.io:/var/lib/postgresql) to the PROD ceph volume at /mnt/ceph/repos/arctic/postgresql (treat it like a hot backup).

      • NOTE: we do not need the /var/lib/postgresql/10 directory

    • copy the following subset of production data from arcticdata.io:/var/metacat to the PROD ceph volume at /mnt/ceph/repos/arctic/metacat:

      # /var/metacat/...
      16K	    ./certs
      63T	    ./data
      8.0K        ./dataone
      3.9G        ./documents
      0           ./inline-data
      500K        ./logs

      • Actual Time taken for /var/metacat/data:

        root@arctica:/var/metacat# time rsync -aHAX --delete /var/metacat/data/ /mnt/pdg/repos/arctic/metacat/data/
        
        real    14286m43.628s
        user    1131m15.740s
        sys     3907m38.871s
        ## -> 9.92 days

Follow the Quick Reference: Metacat K8s Installation Steps. Supplementary TODOs below...

Persistent Volumes

• Set up a PV to point to PROD cephfs .../repos/arctic/metacat for metacat
• Set up a PV to point to PROD cephfs .../repos/arctic/postgres for postgres
• Create a PVC for Postgresql; see prod_cluster/metacatarctic/pvc--metacatarctic-postgres.yaml
• "csi-cephfs-sc-ephemeral" storageClass missing. Ask @nickatnceas to add, like he did for dev cluster:

  storageclass.storage.k8s.io "csi-cephfs-sc-ephemeral" not found

MetacatUI setup

• Copy config (tokens) from adc server

Metacat Config

• Add values.yaml overrides for non-default 2.19 settings (diff arcticdata.io $TOMCAT_HOME/webapps/metacat/WEB-INF/metacat.properties with default metacat.properties from 2.19 release)
• Add values.yaml overrides for newly-introduced 3.0 settings (diff default metacat.properties from 3.0.0 release with default metacat.properties from 2.19 release)
• Compare with test.arcticdata.io values overrides as a sanity check

First Deployment

• Complete steps in "First Install - IMPORTANT IF MOVING DATA FROM AN EXISTING LEGACY DEPLOYMENT" BEFORE first startup!

• solr pods not starting. root cause from logs:

  $ kc logs pod/metacatarctic-solr-1
    /scripts/setup.sh: line 8: /opt/bitnami/scripts/solr/entrypoint.sh: Permission denied

  SOLVED - was overriding extraVolumes values, and the override didn't include the permissions line

Items still To Be Resolved

• https://arctic-prod.test.dataone.org/catalog/ (trailing slash) works, but https://arctic-prod.test.dataone.org/catalog gives a 404 (nginx)
  • See [nginx] Redirect with added trailing slash kubernetes/ingress-nginx#646
  • See https://stackoverflow.com/questions/71424259/why-url-re-writing-is-not-working-when-i-do-not-use-slash-at-the-end

      - path: /link1(/|$)
    

• Time reindex-all

ATTENTION: Before Final Deployment

1. MetacatUI + WordPress setup. How do we host it and link to k8s metacat?
   • ACTION: use a wordpress image/bitnami chart, deployed separately from the metacat helm chart
2. Hostname aliases and rewrite rules
   • Figure out how to do these with ingress; see all-sites-enabled.conf. Lots of complexity - eg http://aoncadis.org aliased to adc.io, and site conf has RewriteMaps each having >3700 entries.
   • EXPLANATION: aoncadis.org was the predecessor to the ADC site. These rewrite rules map existing, old dataset urls to their new locations on ADC - so these rewrites need to be maintained somewhere
   • ACTION: Leave all the redirects/other sites on the current Apache host, and move only arcticdata.io.
     • Ask @nickatnceas for help with letsencrypt certs - do we need to remove arcticdata.io from cert on arctica? NOTE: we still need subdomain certs there (ie status.adc, beta.adc).

• Skip 3.0.0 and deploy 3.1.0, but only after it's been running on less-trafficked hosts for a while. See proposed release plan in Issue Metacat 3.1.0 Release Plan #1984.

Testing - see Matt's comment below

[mbjones]

For the Testing section, here's a quick rundown:

Get the R package dataone installed

• Download and install R (required) and RStudio (nice but optional)
• Checkout rdataone and (probably) switch to the develop branch, depending on what you need to test
• open rdataone/dataone.RProj in RStudio
• run install.packages(c('remotes', 'devtools'))
• run devtools::load_all() to load the current dataone library code for testing
• run remotes::install_deps() to install all of the package dependencies

Run the tests against standard nodes

• login to https://dev.nceas.ucsb.edu and copy your token for R from the web UI; paste the token options command into the R console and run it
• run devtools::test() to run the original tests against standard nodes

To run tests against a different node

• Modify the nodes to be tested in the test framework file: https://github.com/DataONEorg/rdataone/blob/develop/tests/testthat/helper-base.R
  • For example, change line 21 d1cTestKNB <- D1Client("STAGING", "urn:node:mnTestKNB") to use a different node for CRUD tests
• ensure you are logged in as described above
• run devtools::test() as described above