bcgov
Create efficient DLV to PROD Workflow
As a developer that has developed and tested bugs and enhancements to the catalogue I need to be able to easily release the work to production.
Sent this email to @ll911 and the rest of the team:
Hi Leo et al
Currently we have BCDC Delivery on Openshift, while TEST and PROD are not using Openshift. My understanding (please correct me if I’m wrong) is that this configuration makes it relatively easy to deploy to Delivery, but not to TEST and PROD. And that if we moved TEST to Openshift then the process for deploying from Delivery to Test would be similarly easy.
So this suggests that one approach we might take is:
- Move TEST BCDC to Openshift
- We would do frequent deployments of code to TEST, giving us the ability to collaborate with users during the sprints
- Set up an automatic process to do a daily restore of PROD content to TEST
- Have BCDC testers do their acceptance testing on TEST (since it would contain fairly current content)
- Continue to do manual deployments of TEST to PROD on, say, a monthly basis.
Is this feasible? How much effort is this? Are there any other parts I’ve left out? Is there a better alternative?
@hleckenb @mdunhamwilkie need to complete the pipeline to test. also, "move" meaning deploy same version of ckan+bcgov ckanexts in OpenShift. what about the data? at the moment, there is only export scripts, no batch load scripts. i see this issue can be divided in 3 issues
- pipeline work
- ckan and its extensions deployment strategy in K8S/OpenShift
- ETL tasks, (physical, logical layers in files and DB)
