Red Hat Ansible Automation Platform vs. wasmCloud

I'm going to say it is best suited for configuration management. Like I said, patching even with security, things of that nature. Probably less suited is hardware management, but Red Hat IBM/IBM has Terraform for that. So it's a trade off.

Incentivized

If you want to start pivoting your legacy code into a serverless paradigm this is the platform to target. If you want to start moving away from walled gardens and back into a space where code isn't centralized, costs can be offset by utilizing customer or edge hardware this is the platform to focus on. If you want a model that will scale well past many of the existing serverless frameworks, that won't get caught up in the security weaknesses of current paradigms this is what you need to invest in. If you want modern code to interact with legacy code in a safe way that doesn't expose vulnerabilities you can't patch against wasmCloud is awesome. If you want to write simple code that can jump from cloud to cloud to the user or edge node check it out!

• Debugging is easy, as it tells you exactly within your job where the job failed, even when jumping around several playbooks.
• Ansible seems to integrate with everything, and the community is big enough that if you are unsure how to approach converting a process into a playbook, you can usually find something similar to what you are trying to do.
• Security in AAP seems to be pretty straightforward. Easy to organize and identify who has what permissions or can only see the content based on the organization they belong to.

Incentivized

• Host density of workloads
• Streamlined security approach to writing code and reducing bloat
• Interoperability of modules written in different languages

• Ability to tell when a task has already been done
• yaml configuration can be annoying at times, perhaps a built in lint so yq isn't needed
• the become feature should be able to be set to true globally without using args

Incentivized

• Simplified open-source model for on-boarding devs, i.e. bare host no elixir/GUI
• Home-labbers guide to wasmCloud
• Spark more community involvement for capability providers

Even is if it's a great tool, we are looking to renew our licence for our production servers only. The product is very expensive to use, so we might look for a cheaper solution for our non-production servers. One of the solution we are looking, is AWX, free, and similar to AAP. This is be perfect for our non-production servers.

Incentivized

Overall it's good but the new architecture can be complex. Improvements can be made in the Config as Code capabilities for managing Red Hat Ansible Automation Platform. Sometimes it can be difficult for those unfamiliar to understand the relationship between Projects/Credentials/Job Templates, etc.

Incentivized

wasmCloud is still in the early stages of development but the product is rapidly evolving and stabilizing and I feel it will be a preferred way of deploying and managing remote, distributed applications in the future.

Incentivized

Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.

Incentivized

There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.

Incentivized

The core team is extremely responsive in their provided channels. From slack to github issues, there is never a long wait for feedback or guidance.

Incentivized

I spoke on this topic today!

Incentivized

As I said earlier, Red Hat Ansible remains a top choice because it is a perfect combination of multiple capabilities. Terraform is good in IAC but not in config automation. Puppet is well-suited for developers, but not for system administrators and infrastructure integrators. OpenShift and Kubernetes are generic automators only.

Incentivized

• We are still early in our implementation and don't have much yet - but I can say that it has already improved the time it takes to deploy a new virtual server for us, as well as making them more consistent.
• In working through what jobs are required, it has really improved the communication between our different teams

Incentivized

• WasmCloud has massively simplified the required ops expertise needed to run modern software.