Hi Everyone,
I would like to mitigate risk and prevent updating a large number of 3cx servers (running on Debian) at the same time and adopting some type of a staged approach. What update strategy do you have for a large number of servers in regards to updating them?
How are people updating their 3CX servers? do you have the automatic update turned on, manually update from the Admin GUI or is there a command line option to update both Linux and 3cx? Is there anyone working with a script to achieve this? Does this approach also update the smaller 3cx updates such as trunks, firmware, ios certs etc?
I would like to split the servers into multiple groups with our server first being in Group A, then group B a week later, then group C in the third week.
If new updates are rolled out when we are deploying to group B they could get the update before it is tested on Group A (if 3cx updates can land on any day of the month).
How do we ensure only tested updates are deployed?
I would like to mitigate risk and prevent updating a large number of 3cx servers (running on Debian) at the same time and adopting some type of a staged approach. What update strategy do you have for a large number of servers in regards to updating them?
How are people updating their 3CX servers? do you have the automatic update turned on, manually update from the Admin GUI or is there a command line option to update both Linux and 3cx? Is there anyone working with a script to achieve this? Does this approach also update the smaller 3cx updates such as trunks, firmware, ios certs etc?
I would like to split the servers into multiple groups with our server first being in Group A, then group B a week later, then group C in the third week.
If new updates are rolled out when we are deploying to group B they could get the update before it is tested on Group A (if 3cx updates can land on any day of the month).
How do we ensure only tested updates are deployed?
Upvote
2
