Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

Develop ability to deploy Test vs Operations Registry environments #15

Closed
jordanpadams opened this issue Apr 10, 2020 · 1 comment
Closed
Assignees
Labels
enhancement New feature or request Epic

Comments

@jordanpadams
Copy link
Member

Operational deployment documentation should identify both test and operations environments.

Some stories to consider:

  • As a DN User, I want to be able to use a test environment to play around with registry data
  • As a DN User, I want to be able to swap all test data into operations.
  • As a DN User, I want to be able to swap some subset of my test data into operations.
  • As a DN User, I want to be able to rollback changes made in operations to previous version.
@jordanpadams
Copy link
Member Author

Closed per NASA-PDS/registry@f149dee

jordanpadams pushed a commit that referenced this issue Jul 1, 2020
* ZooKeeper installation

* systemd service

* Moved ZooKeeper doc to SolrCloud section. Fixed systemd service.

* Refactoring zookeeper doc

* SELinux fix. Solr systemd service.

* Solr installation (DEV) refactoring.

* Solr multinode cluster.

* ZooKeeper multi-node cluster

* Added export-data command

* Added export-data command. Refactoring.

* Added contents links at the top. Added set-archive-status command

Co-authored-by: Eugene <karpenko@RAYL-AI846797.jpl.nasa.gov>
@jordanpadams jordanpadams reopened this Jul 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request Epic
Projects
None yet
Development

No branches or pull requests

2 participants