Can Tentacles automatically pick up a release when they come Online?

Legacy Uncategorised
1

We are looking to use OD for thousands of customer sites where each Tentacle is NAT’ed behind its own customer network, with an individual release likely to go to hundreds of Tentacles at a time. Due to the nature of these networks (rural Internet can be flaky), the Tentacles can float between an Online/Offline state, meaning that for any particular release it’s hard to tell which Tentacles have/haven’t been deployed to.

Spit balling a scenario, is there a way to create a release for an Environment, and as Offline machines came back Online, have them automatically pick up that release? ATM we are resorting to manually retrying the same release as we notice machines coming back online but it doesn’t seem sustainable.

This is probably not the ideal use case for OD, but I’m looking for guidance on the best way to approach this.

2

Hi Shannon,

Thanks for reaching out. As a matter of fact, we are currently working on v3.4 which has a feature specifically tailored for this scenario called Elastic Environments.

You can read more about it here: https://octopus.com/blog/the-evolution-of-auto-deployments-and-event-sourcing

Check the current beta here: https://octopus.com/blog/octopus-deploy-3.4-eap-beta1

We are planning on going RTM with 3.4 at the end of August after releasing another beta in the next couple of weeks.

Best regards,
Dalmiro

3

Thanks for the guidance. I’ll close this and investigate these Elastic Environments!