Red Hat Summit 2018 is over and we would like to thank all the people who attended and came to the booth to say hello and greet us… it was great meeting all you!
Here is the video of the live demo Maxim Burgerhout and myself performed at Red Hat Summit in San Francisco 2018.
Are you coming to Red Hat Summit? We are!
This will be my first summit and I cannot be more excited! I will meet a lot of interesting people and I am sure there will be outstanding announces as well. I can’t wait for it
Please check-out the labs our team is delivering during Red Hat Summit… they’re super interesting!
You can find the full agenda here but here are some of my personal favorites:
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)