DataONE Tasks: Issueshttps://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2019-05-14T23:57:48ZDataONE Tasks
Redmine Infrastructure - Story #8796 (New): Various issues with service access after upgrade to 18.04https://redmine.dataone.org/issues/87962019-05-14T23:57:48ZDave Vieglaisdave.vieglais@gmail.com
<p>Users have reported some issues with CNs after upgrades to 18.04. See individual issues for details.</p>
Infrastructure - Story #8782 (New): Upgrade OS to Ubuntu 18.04 on CNshttps://redmine.dataone.org/issues/87822019-03-22T18:12:12ZJing Taotao@nceas.ucsb.eduMember Nodes - Story #8683 (New): USGS SDC: redeploy as a v2 Slender Node with GMNhttps://redmine.dataone.org/issues/86832018-08-22T16:25:08ZAmy Forresteraforres4@utk.eduTesting MN Management - Story #8463 (New): test: Testing & Developmenthttps://redmine.dataone.org/issues/84632018-03-01T21:04:41ZAmy Forresteraforres4@utk.edu
<p>Install or develop a functional member node to be registered to a non-production environment. </p>
Infrastructure - Story #8368 (New): Update backup strategy for jenkins job configurations to subv...https://redmine.dataone.org/issues/83682018-02-15T17:37:09ZDave Vieglaisdave.vieglais@gmail.comTesting MN Management - Story #8347 (New): Testing & Developmenthttps://redmine.dataone.org/issues/83472018-02-08T15:28:11ZMonica Ihliemail@monicaihli.com
<p>Install or develop a functional member node to be registered to a non-production environment. </p>
Member Nodes - Story #8244 (New): Upgrade Member Node to current version of Metacat (IOE)https://redmine.dataone.org/issues/82442018-01-22T16:38:20ZDave Vieglaisdave.vieglais@gmail.com
<p>The MN operations have been placed in the care of Todd Kipfer. He has requested some assistance with use of Metacat, and especially bringing it to the latest version.</p>
Infrastructure - Story #8234 (New): Use University of Kansas ORCID membership to support authenti...https://redmine.dataone.org/issues/82342018-01-09T02:00:28ZDave Vieglaisdave.vieglais@gmail.com
<p><a href="https://orcid.org/members/001G000001CAkZgIAL-university-of-kansas" class="external">KU is a premium ORCID member</a> as a member of the Greater Western Library Alliance (GWLA). As a result, KU has access to five ORCID API keys. One is currently in use for the KU DSpace instance.</p>
<p>Goal of this story is to leverage on of the remaining API keys to support ORCID authentication in the DataONE production environment.</p>
Infrastructure - Story #7882 (In Progress): Tune CN logfile managementhttps://redmine.dataone.org/issues/78822016-09-09T20:13:07ZDave Vieglaisdave.vieglais@gmail.com
<p>There are many log files generated on the Coordinating Nodes which can make diagnostics challenging. Some logs also appear to be misconfigured or set to log at DEBUG level even on production systems, resulting in extremely verbose logs.</p>
<p>The goal of this activity is to streamline logging to make it easier to find useful information in the logs by reducing verbosity, consolidating where possible, and perhaps refining some log messages.</p>
Infrastructure - Story #7807 (New): cn.synchronize should support synchronization failure correct...https://redmine.dataone.org/issues/78072016-05-13T16:56:25ZRob Nahfrnahf@epscor.unm.edu
<p>cn.synchronize(session, identifier) works well for its original purpose (supporting MN-driven system metadata updates, and MN-driven push synchronization), but doesn't seem to work for manual synchronization failure workflows. The main problem is that the request can only be made by the MN itself (using the MN client certificate). </p>
<p>As we envision a centralized dashboard for monitoring failed synchronization items, how do we address this situation? </p>
<p>The synchronization processing queue needs both the pid and a nodeId from where to retrieve the object. the NodeId is not specified directly in the method call, but gleaned from the session by a reverse lookup from the certificate. (It uses the first node found in the NodeList where the Node.subject field matches the certificate subject).</p>
<p>Should we allow node.contactSubjects into the algorithm?<br>
Should we add nodeId as a parameter?</p>
Python GMN - Story #7219 (In Progress): Upgrade Django version used by GMN, add better support fo...https://redmine.dataone.org/issues/72192015-06-16T14:56:59ZDave Vieglaisdave.vieglais@gmail.comInfrastructure - Story #7183 (New): Update wild card server certificate on all test.dataone.org s...https://redmine.dataone.org/issues/71832015-06-15T14:54:13ZDave Vieglaisdave.vieglais@gmail.com
<p>The *.test.dataone.org server certificate expires in July.</p>
<p>A replacement has been ordered and will be stored in subversion:</p>
<p>AdminAccounts.txt</p>
<p>The servers impacted are listed on the Google Sheet:</p>
<p><a href="https://docs.google.com/spreadsheets/d/1BrZgm0yPV9dzd6SIfjQ9P5W5WH666xaGAI6KeXTAiFs/edit#gid=0">https://docs.google.com/spreadsheets/d/1BrZgm0yPV9dzd6SIfjQ9P5W5WH666xaGAI6KeXTAiFs/edit#gid=0</a></p>
Python GMN - Story #7095 (New): Support HTTP redirect capability for GMN within the Vendor Specif...https://redmine.dataone.org/issues/70952015-05-12T16:20:39ZMark Servillamark.servilla@gmail.com
<p>GMN provides proxy capabilities to integrate existing content residing in a back-end data repository through its Vendor Specific Extension model. Only minimal support exists within the GMN-VSE model for HTTP redirects. Although the use of HTTP redirects is more of an exception within the the GMN-VSE model, it can provide a flexible mechanism for MNs who dynamically manage data and metadata objects.</p>
Python Libraries - Story #5468 (New): Remove dead code from D1 Python stackhttps://redmine.dataone.org/issues/54682014-06-06T18:57:00ZRoger Dahldahl@unm.edu
<p><a href="https://pypi.python.org/pypi/vulture">https://pypi.python.org/pypi/vulture</a></p>
Java Client - Story #3666 (In Progress): D1Client.listUpdateHistory() needs to handle changing ac...https://redmine.dataone.org/issues/36662013-03-15T22:51:23ZRob Nahfrnahf@epscor.unm.edu
<p>the current D1Client.listUpdateHistory() method needs to gracefully handle the situation where a NotAuthorized request is returned. the ObsoletesChain client class may need to be refactored to allow for this exception to be held so it can notify the user where appropriate.</p>
<p>Ostensibly, with a NotAuthorized, the user will not have access to either the tail or head of the chain, so can't return the head or tail, depending on how access changes.</p>