opendevstack / opendevstack/ods-quickstarters

inf-terraform-* agent: only run PROD deployments while QA/DEV are not needed

Open
#806 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Shell
Stars
39
Forks
50
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.
GreenIT & waste of resources

The current approach is designed for a deployment into three environments (DEV/QA/PROD). In regards to resource consumption and costs it might triple the overall costs. Measures could be configuring different sizes for DEV/QA/PROD so that costs and waste of resources is lowered. Nevertheless cloud providers also provide services which take very long to provision and are rather static (e.g. Azure HPC Cache) meaning there's no option to choose a cost-efficient configuration.

Describe the solution you'd like
This might rather be applicable to ods-jenkins-shared-library (RM) than the ods-quickstarters repo.
If needed (configured), DEV/QA environments should get destroyed after release to PROD or shutdown during non-business hours. This would also mean that the next deployment cycle would have to deploy version 1.0.0 (the one running in PROD) into DEV/QA and afterwards apply the new version 1.1.0 from DEV to QA to PROD.

Describe alternatives you've considered

  • Only configure PROD environments without running through DEV/QA.
  • Manually clean up DEV/QA after PROD deployments.

Additional context
N/A

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name specific files or tests. Start by locating the inf-terraform-* agent definitions and reviewing ods-jenkins-shared-library, where the issue suggests the change may belong. Clarify whether the accepted behavior is configurable DEV/QA destruction or shutdown, or PROD-only deployment, then define how the next deployment cycle should restore and promote environments.

Written by the indexing model from the issue text.

Assessment

Tech stack
terraform
Domain
cloud, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.