Agenda

• EnvBuilder: ConfigMap injection
• BLU: pipeline speedup
• BluWorkflows: deployment process updates

EnvBuilder ConfigMap injection

What's the problem?

• Configuration of test environments has to be set in code
• But: many tests require scenario specific configurations
• Mostly circumvented by using manual update policy
• Defeats the purpose of feature specific environments which should be quickly created and destroyed

EnvBuilder ConfigMap injection

What's the problem?

~$ wonderpod

name: FOO-321
projects:
  - group/blu: "FOO-321,release"
  - group/automation: "FOO-321,release"

scanplus_env: dev
target_clusters:
  - os4-ulm

sync_policy: manual

EnvBuilder ConfigMap injection

What we did about it:

• Set specific configuration values for envbuilder/wonderpod deployments
• Setup at creation time, or change later
• Defined in env.yaml like so:

  cm_injection: 
  aida_blu:
    BLU_aida_cmdb_host: cmdb-test.aida.local
    BLU_aida_cmdb_port: '80'
  sites:
      SP_sites_ffm01_aci_host: aci-test.ad.scanplus.de
  

• 👉 EnvironmentBuilder README

BLU pipeline speedup

What's the problem?

• Slow development turnover due to long timing between push and deployment
• Small chance to install different dependencie for linting and testing (and deployment

BLU pipeline speedup

What we did about it:

• Pipeline will build an image
• Image is reused for pylint and pytest
• Additionally use needs to parallelize pipeline
• Precursor to a deprecation of buildconfigs
• roughly half pipeline runtime from ~5-7 min to ~2-3 min

BluWorkflows deployment process updates

What's the problem?

• Current deployment runs for up to 15 minutes
• During this time, workflows are in an undefined state
• The process of updating workflows is taking majority of time

BluWorkflows deployment process updates

What we did about it:

• Replace the naive reloading of all workflows with a more targeted approach
• Only update workflows which were changed since the last release
• Manually set workflows to delete before creating release
• Should reduce deployment times to a few seconds rather than minutes
• 👉 Issues with deployment of workflows? Ask me about it.

Questions?

Missing features still to come

BLU pipeline speedup

• Apply same approach to other projects
• Deprecation of buildconfigs
  • Dramatically increase deployment speeds
  • Increase protection against 'dependency hell'
  • Standardize deployment process towards native k8s (vs OpenShift)

Missing features still to come

BluWorkflows deployment process updates

• Automatic workflow deletion
  • Requires a more in depth look into changes to automatically identify
• Scenario specific deployment of server components
  • I.e. only rollout api/engine/executor if actually necessary

Thanks for joining