Activity
From 2014-05-22 to 2014-06-20
2014-05-28
- 19:09 Task #5362 (Rejected): KUBI: Set up Node document
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 19:09 Task #5361 (Rejected): KUBI: Register MN
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 19:09 Task #5360 (Rejected): KUBI: Verify successful installation of server side certificate
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 19:09 Task #5359 (Rejected): KUBI: Verify successful installation of client side certificate
- After notification from the MN that the client side certificate has been installed, verify that it is working correctly.
- 19:09 Task #5358 (Rejected): KUBI: Generate client certificate for urn:node:KUBI
- Create the client certificate and send it to CJ Grady, Aimee Stewart. When the certificate has been installed on the ...
- 19:09 Task #5357 (Rejected): KUBI: SSL Certificates
- Set up and verify correct operation of SSL client and server side certificates
- 19:09 Task #5356 (Rejected): KUBI: Register new Science Metadata formats
- All Science Objects on the MN should be of types that are known to the CN. Any unknown types should be registered.
- 19:09 Task #5355 (Rejected): KUBI: Registration in environment
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 19:09 MNDeployment #5354 (Closed): KUBI: Testing
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 19:09 Task #5353 (Rejected): KUBI: Verify that MN passes the Replication Tester
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 19:09 Task #5352 (Rejected): KUBI: Verify that MN passes the Web Tester
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 19:09 Task #5351 (Rejected): KUBI: Local Testing
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 19:09 Task #5350 (Rejected): KUBI: Design, code and component test a new MN implementation
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 19:09 Task #5348 (Rejected): KUBI: Plan the implementation
- Determine which software stack to use, etc.
- 19:09 MNDeployment #5349 (Closed): KUBI: Developing
- Determine which software stack to use, etc.
- 19:09 Task #5347 (Rejected): KUBI: Scope the implementation
- Select the MN Tier, etc.
- 19:09 Task #5346 (Rejected): KUBI: Create MN description document
- Work with MN POC to create MN description document, logo, etc. Attach here when complete; store PDF in docs.dataone.org.
- 19:09 Task #5345 (Rejected): KUBI: Create DataONE identities
- Create DataONE identities for one or more of the MN contacts, to enable access to docs.dataone.org, Redmine, etc.
- 19:09 Task #5344 (Rejected): KUBI: Integrate MN representatives with community
- Add MN representatives to MNF/developers/community, other lists as needed.
- 19:09 Task #5343 (Rejected): KUBI: Join DataONE
- Determine if the potential MN organization has the required resources for becoming a MN.
- 19:09 MNDeployment #5342 (Closed): KUBI: Planning
- Determine if the potential MN organization has the required resources for becoming a MN.
- 19:09 Task #5341 (Rejected): KUBI: Determine feasibility
- Determine if the potential MN organization has the required resources for becoming a MN.
- 19:09 Task #5340 (Rejected): KUBI: Establish contact with potential MN organization
- Establish contact with the developers and/or administrators who will be responsible for developing and/or deploying t...
- 19:09 MNDeployment #5339 (Closed): KUBI: Initial Preparation
Also available in: Atom
