In our previous post, we demonstrated how to create a basic Ansible Service and provision it from Red Hat CloudForms Service Catalog. In this post, we demonstrate how we can deploy a VMware virtual machine using an Ansible Playbook.
This document is to position two different types of integration with a CMDB and Red Hat CloudForms.
We discuss the use of HP uCMDB because it supports both types of integration but also other CMDBs are available such as Service-Now.
The two types of integration are known as;
Pull – Where by the information/data is collected (Pulled) by the CMDB from the end points. CMDB Server initiated.
Push – Where by the information/data is sent (Pushed) to the CMDB server by the end point. Endpoint initiated.
Other CMDB servers may not support a PULL approach at which point you have only the PULL solution as the only option.
We shall now dive deep into each integration type.
Red Hat CloudForms allows to more quickly deploy and scale Red Hat OpenStack Platform (also known as OSP) private clouds, combine existing IT infrastructure investments, and federate public cloud deployments. This series includes both background information and hands-on tips to implement a full SDDC in practice.
This is a follow up to the Ansible Series with a new video that shows how to create a button that executes an Ansible Service. In this post, we re-use the same Ansible Service that we created in our previous post: My First Ansible Control Action.
Service catalog bundles are a really useful CloudForms feature that enable us to mix and match various existing service catalog items together to form bundles of tasks.
One of the more useful examples of a bundle is to create a new VM, and then run an Ansible Tower job template on the resulting VM to configure it with an application role. If we have an Ansible Tower server added to our CloudForms installation as an automation provider, this is quite simple. We described the procedure to configure an Ansible Tower provider in CloudForms as part of our previous series on Ansible Tower integration in CloudForms 4.1.
Few days ago one of our fellows, Christian Jung, published a very good article explaining best practices while coding Ruby code inside Red Hat CloudForms.
This blog is part 5 of our series on Container Management with CloudForms.
In this last post, we focus on financial management of container environments for both chargeback and for optimizing infrastructure resource usage and spending.
This blog is part 4 of our series on Container Management with CloudForms.
This blog post focuses on the security and compliance aspects of managing containerized environments.
This blog is part 3 of our series on Container Management with CloudForms.
A second area of concern identified when managing a containerized environment is service health. We need to operate our containers with good performance, reliability, and ensure high enough utilization ratios. In this post, we focus on the container based infrastructure, its on-going resource consumption, and how we can monitor and optimize its health.
This blog is part 2 of our series on Container Management with CloudForms.
In this blog, we look how the operations team can manage container environments and ensures the workload runs securely and efficiently. This includes the containers themselves, but also the underlying infrastructure. Operators need to ensure resources at all layers of the stack are optimized to provide the highest level of service for the container workload.