Expose the state that CCO manages within a cluster

[pwalsh]

Job story

When I administer infrastructure that CCO manages, I want to be able to rebuild/reproduce the entire state of that cluster, so that I have the technical means to support disaster/recovery scenarios that require the establishment of an entire new infrastructure environment.

Context

CCO produces/manages a lot of state about the configuration of the cluster and related services, as well as the configuration of the multiple CKANs that run within. This state can be written into a format that can be imported and exported, and this is desirable for scenarios

Acceptance criteria

• [ ] An API to export CCO-managed cluster state
• [ ] An API to import CCO-managed cluster state
• [ ] Tests to demonstrate functionality, executed via CI/CD
• [ ] Documentation

[adborden]

How does CCO currently store its state? Flat files? External systems e.g. Kubernetes? A database?

This would help me to prioritize this story.

[akariv]

As custom kubernetes objects.

On Wed, Dec 18, 2019, 00:32 Aaron D Borden [email protected] wrote:

How does CCO currently store its state? Flat files? External systems e.g. Kubernetes? A database?

This would help me to prioritize this story.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/datopian/ckan-cloud-operator/issues/81?email_source=notifications&email_token=AACAY5NI35EJW45M2LMMUS3QZFHQ3A5CNFSM4JPVKET2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHEF3OQ#issuecomment-566779322, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACAY5JBRG7H7DNZVTTIDPTQZFHQ3ANCNFSM4JPVKETQ .

[adborden]

You mean exporting would involve pulling objects out of the Kubernetes API and writing them to some file format?

If that's the case, I would lower the priority since it's not necessary to deploy into the GSA sandbox.