Lab Manager style scenario

So with the cloud we are considering like many the possibility of spinning up dynamically spin up additional servers (application servers, db servers) based on requests. Looking at this there appears to have the need for an incredible amount of flexibility.

Connection Strings, other architecture items (SMTP, etc.), URIs, Service Accounts, CI\CD considerations (if this environment is dev and only supposed to take a particular version of code-thinking major/minor versions specifically) - lifecycles, channels, roles…

I’m trying to think through a model that could have this work with Octopus because manual updates for that type of thing would have me buried in work. Has anyone had success with a lab manager style environment with Octopus? Are there architectural considerations people can point at?


Hi Mike,

This is an approach that may be of interest to you.

We are also currently working on a set of features known as Machine Policies, which will enable support for elastic environments and transient machines, as outlined in this post.
This will ship in our next release (3.4), and should also be of help for scenarios such as the one you are considering.

I hope that helps,

Thanks for the information. There has been another discussion I’ve been involved with, with regards to DSC so this could be a possibility.


Mike Peterson
IT Deployment Specialist
Preventice Solutions Group

2765 Commerce Dr NW, Ste 220
Rochester, MN 55901
Office: 507-218-3053
Mobile: 507-251-2315

Preventice Services, LLC and Preventice Technologies, Inc. are part of the Preventice Solutions Group of companies and are independent, wholly owned subsidiaries of Preventice Solutions, Inc.

This message contains confidential information and is intended only for the sole use of the addressed recipient(s). If you are not one of these recipients you should not disseminate, distribute or copy this e-mail. Please notify the designated recipients immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmissions cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.