We are considering building out some automation for creating environments for our developers. We have a big monolithic app that uses ~5 VMs with different software configurations – Database servers, application servers, web server, etc.
Recently we have produced DSC configurations for each of the server types we have, but I'm a little unsure about how to turn this into a pipeline where we can press a button and a fully configured environment comes out the other end.
We are mostly on-premises but are thinking about using Azure as our dev/test space.
My thinking of how the pipeline would work at the moment is running something like this:
1. Dev queues a build on TFS.
I was thinking we can just use steps 1-5 as a CI pipeline for changes to our composite resources for each node as well.
Once we have this in place, I think we can then start transitioning bits and pieces of the platform to be cloud native (individual web services and so on)
Does this seem like a good way to forward? I am considering using Azure DSC to host the configurations but not sure how this would integrate into the pipeline.
You can register on-prem nodes to Azure DSC. You can read up on assigning on-prem resources to configurations here:
I've never actually integrated it with Octopus Deploy. I'd be really interested to see if anyone chimes in on that part.
You must be logged in to reply to this topic.