-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automating infrastructure deployments for CCO-managed clusters #69
Comments
Responsibilities of TerraformIn standing up an environment for managing a CKAN cluster, Terraform will have the following responsibilities:
In order to do this, the system administrator will have to have created a project (or similar) in advance on the cloud platform, so that Terraform has the appropriate user with permissions/keys to perform all required tasks. We will ship a default terraform configuration with support for:
And document ways to modify these defaults if needed. |
Esteban to breakdown ticket
|
|
move to backlog |
We are still working on docs. Should have ready tomorrow |
Job story
When I standup a cluster of CKANs managed by CCO, I want to be able to automate the required infrastructure deployment in a platform-agnostic way, so I have a consistent foundation for infrastructure resource management that is code-driven and does not require manual configuration steps.
Context
Currently, we have a range of manual steps that are under- or un-documented, to run CKAN Cloud, and much of these are related to standing up the k8s configuration required to run CCO within. Further, we now have CCO deployments on Azure, AWS and GCP, and each of these deployment targets has requirements for infrastructure configuration that we want to ensure are reproducible in code. A tool like Terraform may provide us with the necessary foundation to write platform-agnostic deployments for CCO infrastructure, at least targeting Azure, AWS, and GCP.
Acceptance criteria
The text was updated successfully, but these errors were encountered: