Member Nodes

http://www.iplantcollaborative.org/challenge/iplant-tree-life/the-botanical-information-and-ecology-network-bien-0

BIEN iPlant software infrastructure is iRODs based. MN deployment needs a iRODS SW deployment as a pre-requisite. Y5Q2 target deployment me need to be revised in light of this requirement and DataONE CCIT work plans.

Actual start date of 9/14/16 when serious discussions and plans for development began.

Conference call with Ramona, Dennis, Mike, Laura, Mark on 31 August (see epad: https://epad.dataone.org/pad/p/CyVerse_and_DataONE). Provided more technical information for Mike and Dennis to ponder.

10/18/2017 -email From: Dennis Roberts

Hi Everyone,
I just wanted to provide a brief update. The member node service along with the DataONE event logger has been running in our development environments for about a week.
We’re currently in the process of changing our deployment strategy from Docker Compose to Kubernetes. I haven’t tried to package up the member node service or the event logger for Docker Compose because that would ultimately be wasted effort. The next step in the switch to Kubernetes will be to get our automated QA tests working against Kubernetes. Once that’s done, we’ll be able to deploy the member node service and event logger in our QA environment. We can coordinate testing as soon as we get the member node service deployed.
The last remaining task for the member node service is to create a utility to generate the Object Reuse and Exchange files for our data sets. I don’t believe that this has to be done before we can begin testing the member node service, but it will be necessary before we move it to production.

2/8/18 {Nirav Merchant}: The work has gone through QA on our side, it is bundled in the bigger Kubernetes upgrade for Discovery Environment (DE) happening end of this month, so I am hoping we will see it in production soon.

Contact is Sarah Roberts(sarahr@cyverse.org)

re: data planning for their Member Node, their initial plan is to expose the curated set of packages that are relatively stable, and have DOIs assigned. They manufacture the Datacite metadata for these packages, and it is a metadata format we support, so testing in STAGE makes sense.

Yet, there is a strong possibility that they will need to support mutable data, so would want to upgrade their API to v2, to leverage the seriesID. Meeting July 5th to help assess the situation.

Testing of their current api will be useful, and will be of great service to them for demonstrations in mid July.