This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Require Ansible playbooks to deploy and manage WAS ND deployments
Client is using CP4WAIOPS Infrastrututure Management to deploy and manage WAS ND. When they used the tooling in the past they had used Chef cookbooks to build and deploy WAS ND systems. Since IBM Purchaed RH, the CloudPak has indicated that Chef is now replaced with Ansible, but the team did not create WAS ND ansible playbooks for that in the offering.
The client would want IBM to create a set of sample Ansible playbooks that could manage their WAS ND systems, so that they can take advantage of the Infrastructure Automation packages that call out to ansible after deploying the vm's and parts into any source (vmware, azure, aws, etc)>.
After looking around we have found an IBM did create a fairly robust playbook set here https://github.com/ebasso/ansible-ibm-websphere It would need to be refreshed for the lastest code.
The client is looking to do the following at least:
Deploy tWAS ND create/manage security config multi node deployments federate the node cells create and update certificates deploy an app Update JVM, and WAS
The package above has most if not all of the above.
Do not place IBM confidential, company confidential, or personal information into any field.