Story #3678
Create checklist for MN deployment
100%
Description
Member Node implementors do not have a clearly documented process for creating, testing, and deploying a member node. Potential MNs have requested a checklist of steps that makes it totally clear how they should proceed. In addition to getting the node to the point of passing the MN Checker tests for their Tier, they also would like a checklist of the manual reviews that will be performed when the MN is being reviewed by the development team when it is in stage.
Chris suggested that this be developed in our Operations documentation here: http://mule1.dataone.org/OperationDocs/member_node_deployment/index.html
History
#1 Updated by Dave Vieglais over 11 years ago
- Due date changed from 2013-03-30 to 2013-08-03
- Target version changed from 2013.12-Block.2.2 to 2013.30-Block.4.3
#2 Updated by Rob Nahf over 11 years ago
- Due date changed from 2013-08-03 to 2013-08-10
- Status changed from New to In Progress
- Assignee changed from Matthew Jones to Rob Nahf
- % Done changed from 0 to 30
taking over this ticket and working with Laura Moyers to build out the documentation at different levels
#3 Updated by Rob Nahf over 11 years ago
- Target version changed from 2013.30-Block.4.3 to 2013.33-Block.4.4
- Due date changed from 2013-08-10 to 2013-08-24
#4 Updated by Rob Nahf about 11 years ago
- Due date changed from 2013-08-24 to 2013-09-21
- Target version changed from 2013.33-Block.4.4 to 2013.37-Block.5.2
- Product Version set to 1.1
#5 Updated by Dave Vieglais almost 11 years ago
- Due date changed from 2013-09-21 to 2014-02-01
- Target version changed from 2013.37-Block.5.2 to 2014.4-Block.1.2
#6 Updated by Rob Nahf over 10 years ago
- % Done changed from 30 to 100
- Status changed from In Progress to Closed
This led to creation of a public-facing checklist on data one.org site, tied to the more technically oriented member_node_checklist document in mule Operation docs. There was an agreement in the leadership team on consistent phase labeling, and first-level detail activities between the two versions.
While individual documentation improvements will always be needed, the framework is in place, and so is considered complete. Future documentation tasks should create individual stories.
