Introduction
We understand that cloning can be a useful approach to support large-scale deployments and meet specific user needs. It can be useful to configure a full operating system and software payload on a single machine, clone the disk, and then replicate the image onto other machines.
As part of the initial negotiation between your container, your EdgeVis Server, and the central licensing server, there is a unique identifier created that identifies your individual instance of the container with the licensing server.
This is so we know which licences are assigned to which container from your pool - this allows you to manage your licences if required.
How to clone a disk image successfully
You must clone the image of your machine BEFORE the container has connected to your server for the first time.
This then allows each individual instance of your container to generate its own unique identifier, and therefor grab its own licence appropriately.
What happens if I clone after the initial server connection?
You will end up with multiple container instances trying to use the same licence - currently this will be flagged to our staff by the licensing system so we can assist customers, however in future versions only container will function.
