In my opinion they just want to force us, who don’t have kubernettes, to buy Tower. They save on docker-compose development and bring more revenue.
I don’t think that is the case. If that is the case, that logic is flawed. If a potential client is bent on using free open source technology and can afford ansible tower, they most likely have enough resources (or can invest in enough resources) to create a kubernetes cluster, or even to use okd if we wanna keep it in red hat family, and provision AWX operator there.
I don’t mind paying for Tower and for support, but there is a large number of potential clients who are not large enough to be able to afford that.
And they are now left hanging, because they won’t be able to keep updating AWX to new releases.
I started playing with provisioning AWX on minikube today, and there is a plethora of massive issues if one plans to use it for production.
And for a company that used AWX, maybe not so much for automation, as that can easily be done with just Ansible, but for access conrolled task delegation in order to refocus their core operations teams from basic everyday repetative tasks to more important problems, that is a big loss.
I don’t think that the issue is so much with them trying to force people to buy Ansible Tower, as much as it’s them trying to refocus their stengths to building new Tower features, as Tower will change massively in the nearer future.
I just saw a talk by a Red Hat employee that the product we used to know as “Tower” will no longer exist. It’s all going to containers. Quite the watch: https://www.youtube.com/watch?v=jZEXx8FgR58&t=2391s
I’ve heard about this. I like the course they’re taking with the whole automation platform.
Dana srijeda, 31. ožujka 2021. u 15:32:53 UTC+2 korisnik nuno....@gmail.com napisao je:
