- Joined
- May 6, 2019
- Messages
- 17
- Reaction score
- 1
Hi,
we currently host our customers 3cxs on AWS, we have like 20 or 30 there but now we upgraded some of our own datacenters so we are planning to move these VMs to our own cloud.
We have made a new virtual machine (debian+3cx v.18) and installed it giving for example a X.X.X.X ip address.
We did not go on with the final installation so this machine is stopped at the "http://x.x.x.x:5015?V=2" point.
We would like to use it as a "Master Virtual Machine" so any time we need a new VM we just clone it, enter via console, change ip address, reboot and finish the installation or upload backup from the aws 3cxs
Can anybody confirm that this is a good solution or maybe we are missing something?
I remember that You cannot change ip address after the installation but this is a little bit different.
Thanks in advance
Regards
we currently host our customers 3cxs on AWS, we have like 20 or 30 there but now we upgraded some of our own datacenters so we are planning to move these VMs to our own cloud.
We have made a new virtual machine (debian+3cx v.18) and installed it giving for example a X.X.X.X ip address.
We did not go on with the final installation so this machine is stopped at the "http://x.x.x.x:5015?V=2" point.
We would like to use it as a "Master Virtual Machine" so any time we need a new VM we just clone it, enter via console, change ip address, reboot and finish the installation or upload backup from the aws 3cxs
Can anybody confirm that this is a good solution or maybe we are missing something?
I remember that You cannot change ip address after the installation but this is a little bit different.
Thanks in advance
Regards