One of the exciting new features in CloudForms 4.6 within Automate is Embedded Methods. That is, one can store reusable, directly callable, ruby code within Automate and access from other Automate Methods.
Some time ago I walked through installing the Cloud management solution known as CloudForms in a container. While this was fun, it was not really feasible and quickly ran into limitations in use.
In CloudForms 4.6 deploying CloudForms on top of OpenShift is fully supported and we will post more information about this soon.
The real solution is pulling this example into the Red Hat Demo Central collection and put it on a Cloud solution based on open technologies. This gives you the chance to go from your laptop, to Cloud installation and onwards to a Cloud Operations solution in just minutes.
Let’s take a look at how this works, shall we?
For the last few posts Laurent Domb has been explaining how to squeeze CloudForms and AWS integration by teaching you how to:
- Upload the CF images to AWS
- Create all the needed config files in AWS
- Deploy CF on AWS
- Configure the new in 4.6 SmartState Analysis (SSA)
- Use that SSA to add a compliance policy to an instance
- Use AWS authentication in CF
You can find the blog posts here:
- CloudForms on AWS Part 1 (Series)
- CloudForms in AWS part 2
- CloudForms in AWS part 3
- CloudForms in AWS part 4
- CloudForms in AWS part 5 (authentication)
Please let us know what are your thoughts and which other series would you like to read in the blog
If you want to use IAM authentication for CloudForms so that IAM users can authenticate with CFME you need to do the following.
The current code requires you to add root (account owner credentials) to the authentication field. So the Access key and the Secret Key are from the root user, not the IAM user.
We all know that sometimes we need some help with any tool we want to set up, and in CloudForms we are having such a great momentum because we included Ansible Automation Inside as a way to facilitate our users to interact and create custom action in CloudForms using it (as we covered previously on the Ansible Series)
In this post of our series, we will demonstrate what we did in the previous sections in which we configured AWS and CloudForms, to run a SmartStaty analysis to automatically resolve a vulnerability in Java
In the video, I will:
- Perform a SmartState Analysis (SSA) in my instance
- Review the SSA process
- Add a compliance policy to the instance
- Execute the policy
- Verify the remediation action
- Validate the auto-remediation
This part of the CloudForms in AWS blog series will walk you through how to make sure that CloudForms reaches its full potential in AWS.
IMPORTANT: If you want SmartState analysis to work you need to register your AWS account with the cloud access program. Use the link below to enable cloud access:
Ever wondered what CloudForms can do for you in AWS? The next few blog posts will walk you through step by step how to upload the CloudForms image to AWS, how to assign the correct policies and roles and how to configure it correctly so it can discover your environment. Part 1 is dedicated to the import and configuration of the CloudForms image.
With the release of CloudForms 4.6 you also have the ability to scan instances in AWS. These blog series will show you how this can be achieved:
Today marks the general availability of Red Hat CloudForms 4.6, as announced in the recent Press Release. One of the key highlights of the release is the introduction of Lenovo XClarity as the first physical infrastructure provider, enabling CloudForms to go beyond hybrid cloud management and manage hybrid infrastructure.