Deploying flows on multiple cloudgates

Modified on Fri, 7 Jun, 2019 at 4:48 PM

During development you are mostly developing on a single cloudgate, but you want to release your flow onto a fleet of cloudgate. This article explains how to go from one deployment to many.

 1. Create a flow designed for multiple targets

It is important that the exact same flow can be deployed on multiple targets. If you need to have different credentials or identifiers for each target this single flow must be able to handle this.  A good unique id for most applications is to use the cloudgate serial number. A lot of nodes support a {{serial}} template that will substitute the cloudgate serial at the desired location in the string.

2. Test on multiple cloudgates

Test your final flow on multiple targets by exporting the flow and importing it using the luvitred UI. Please note that the luvitred UI does not export credentials you you need to re-enter them on the second target.

3. Create a golden master cloudgate

A golden master cloudgate is a cloudgate that has all the required settings on the admin page, the correct firmware & luvitred version. Importantly it has NO configuration image loaded. Having no configuration loaded is important because that will affect the luvitred configuration in the next steps. Make sure your flow is working and has all the required credentials. The firmware on this cloudgate is considered the minimum firmware version your application will support.

4. Export the configuration

Go in the cloudgate admin webpage to System > Config export. Click the "Download config" button. Do not tamper with the file.

5. Use the config converter

Go to the Config Converter on the clougate universe. Upload the config you have downloaded in the previous step. Give it an appropriate name (possibly with a version in the name). If the desired config should only contain the luvitred flow you can select all the checkboxes in the "advanced settings". Click to convert to retrieve your config.

6. Test the config

Upload the new config to a new cloudgate and validate your application.

7. Upload the config to the cloudgate universe:

8. Update the group of cloudgates with the new configuration


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article