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.
Containers have rapidly evolved from being used for development and testing to production. Today, many vendors provide container products supporting enterprise IT production workloads. Red Hat offers OpenShift, an open source container platform based on Kubernetes.
The promise of containers includes greater cross-cloud workload portability, better support for microservices and faster business innovation through the ability to support CI/CD methodologies for rapidly launching new functionality. By pairing containers and CI/CD with public/private hybrid cloud infrastructure, enterprise IT teams expect to better match infrastructure spending to workload performance while enabling end user developers self-service and agility.
In this article, we continue the Ansible Series with a new video that shows how we can execute an Ansible playbook from the CloudForms REST API.
In this video, we are using Postman which is a REST API testing framework. Of course you can use any tool you are comfortable with e.g. CURL, Ruby, Python or anything that can execute REST API calls.
With this short video, we continue our series based on Red Hat Knowledge Base articles exploring how to take advantage of Ansible Automation inside Red Hat CloudForms. This post is a follow-up of our previous My First Ansible Service article.
As a summary, what we do in this video is to create a control policy that checks if the VM CPU or memory size has changed, and if so, resets the size to 1 CPU and 1GB automatically.
First let’s talk about Remote Session vs Remote Console, they are often confused.
This article seeks to explain the use of State Machines in Red Hat CloudForms for the use in the flow control of automation.
The topic of State Machines is sometimes perceived as rocket science, barely used but often taught. The first thing to dispel is the complexity in state machines, then we can compare how a state machine differs from other process automation like Workflows.
Finally the article is to dispel the myth that State Machines are RUBY or if you use Ansible Automation Inside you do not need state machines, again not a true statement.
