DevSecOps and Automation on Power

Ansible has been around for a long time and there are 1000s of Playbooks available for AIX, IBM i and Linux.  Now with Ansible 2.4 Tech Preview for Power, the Automation Controller (aka control plan) can run natively on Power per the blog posted earlier today by Joe Cropper.   So what are the most likely reasons that you would want to run the Automation Controller on Power vs just continuing to run it on an x86 server?  @MANOJ KUMAR - what do you think given your experience with OpenShift and RHEL and OpenShift?   @Paul Finley how about you given your experience with Ansible? 

Chuck,

I am neither Manoj nor Paul. First of all it is not about Ansible Controller, but about Ansible Automation Platform. If you've read the announcement:

It is the whole Ansible Automation Platform available for IBM Power. It is not about playbooks, modules and collections. It is about different customers' environments and their needs. AAP enables you to use certified and supported content from Ansible Automation Hub, to create workflows out of playbooks and to schedule their execution. You can implement RBAC, store your secrets and use Microsoft Active Directory to authenticate your operators, who run the workflows and the jobs. It makes sense using Ansible Automation Platform if you work in a corporate environment.

What is the reason to run Ansible Automation Platform on IBM Power? There can be a lot of them. Starting with just simple - why should I run it on x86 if I have IBM Power? It may be networking segmentation or segregation of duties. Or may be you just want to make automation mesh with different execution planes for different platforms?

I also recently tried to transmit a signal via a Pogo pin, connected to my automation device with a PCBA board, requiring a current through 2A, and design