Deployment to Production Environment¶
After a Member Node instance is successfully passing tests it can be deployed to the production environment. The steps for deployment are:
Add the MN logo to the Github repository
Add the MN to the list of upcoming Member Nodes
Verify that the MN instance is populated with production content, not test content
Prepare announcement for the MN release
Obtain a client certificate for the MN. This certificate must be signed by the Production Certificate Authority.
Register the MN in the production environment
Update the custom “CN_” node registration properties
Approve MN
Content starts synchronizing
Verify content has synchronized and appears in the search UI
Announce the new MN
1. Add MN Logo to GitHub¶
See the Member Node Info repository on GitHub.
2. Add to Upcoming¶
When a MN is getting close to deployment, it may be added the “upcoming” MN list that is shown on the DataONE Member Nodes dashboard.
3. Verify MN Content¶
It is important that no test content is present on the MN when it is being added to the production environment. Accidental content can be removed, but it is a process that should be avoided where possible.
Work with the MN operator to ensure no test content remains (if repurposing a test instance) and that the node is appropriately populated.
4. Prepare Announcement¶
The public announcement of a new MN requires a bit of back and forwards between DataONE and the MN, so it is best t start this process early to ensure the announcement document is ready.
5. Obtain Client Certificate¶
The client certificate is needed for the MN to register with the CN, and for any other actions that require the node to authenticate.
See the CA project in subversion at: https://repository.dataone.org/software/tools/trunk/ca/
6. Register MN¶
Registering the MN will record the presence of the MN in the Production environment node registry. The CNs will not interact with the MN until the registration is approved.
7. Add CN_ Properties¶
After the node is registered