We use Ansible "to a point" in that it sets up what we consider to be our preferred server (Droplet) for a specific purpose, then we deploy projects on them and tweak non-Ansible managed project configs. It's not old-school scripts and it's not quite a one-liner to deploy everything. It's somewhere in the middle. So in reality, providing we have control over a customer's DNS or we use floating IPs, migrating to another major release isn't as time consuming as doing everything from scratch.
> On 6 Jan 2021, at 13:17, Mauricio Tavares <raubvogel@xxxxxxxxx> wrote:
>
> On Tue, Jan 5, 2021 at 6:32 PM Jamie Burchell <mail@xxxxxxxxxxxxxxxxx> wrote:
>>
>> Off topic for sure, but it's a shame this has to be a manual process of
>> destroying and rebuilding every X years. Even Microsoft has gone the Apple
>> way and just perpetually updates Windows 10 now.
>>
> Do you use tools like ansible/chef? If you can put the time in,
> you can make your webservers rather distro agnostic. I would even put
> terraform on the table. It is not like your customers will know the
> difference.
>
>>> On Tue, 5 Jan 2021 at 23:20, Gordon Messmer <gordon.messmer@xxxxxxxxx>
>>> wrote:
>>>
>>> On 1/5/21 3:02 PM, Jamie Burchell wrote:
>>>> We will need to (manually) migrate to Stream 9.x after 5 years instead of
>>>> 10 though?
>>>
>>>
>>> Yes. CentOS Stream has a lifecycle comparable with other LTS
>>> distributions.
>>>
>>>
>>> _______________________________________________
>>> CentOS mailing list
>>> CentOS@xxxxxxxxxx
>>> https://lists.centos.org/mailman/listinfo/centos
>>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS@xxxxxxxxxx
>> https://lists.centos.org/mailman/listinfo/centos
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
