Disclaimer: the high-level architecture solution and the related demo code is an opinionated implementation to solve the problem described here. The author believes that DevOps is not about tools and frameworks, but a mindset and cultural change for teams. This is an implementation that aims to help a team on the DevOps journey of increasing shared understanding within traditional Development and Operation teams.
There are some challenges while adopting a PaaS Platform like OpenShift in an organization. Traditional IT teams have operated in silos where responsibilities for different parts of the Product lifecycle were distributed to different teams, for example, a development team and a release or production team. The teams’ domain of knowledge is, traditionally, limited to the activities they perform for their part of the chain of work and communication between these teams lacked flow or was done using ticketing systems that increase handoffs.
Continue reading “How to use Everything as Code to create a shared language between Product and Platform teams driven by Ansible Tower and Self Service models”
This post was originally published on the ETI blog here.
So – you want to stop your OpenShift cluster? There are many reasons why you may want to stop your OpenShift cluster. Maybe you have an annual disaster recovery test where you shut down a whole datacenter. Perhaps you want to do some maintenance to your infrastructure or the hypervisor or storage that your cluster is hosted on. It’s not an uncommon to need to be able to do this, so I have collated some of the best practices I have experienced across a multitude of environments, both large and small.
Here is the process that I recommend to use as a best practice in order to stop and start your OpenShift cluster(s). Following this process will give you the best chance of a trouble free maintenance window. As with all things, you should exercise care with this process on your important clusters. Try it on an unimportant environment first and see if it is a good fit for you.
Important: This process will cause an outage to any application workload running on the cluster until the cluster is fully started. The cluster itself will be unavailable until manually started. Care should be taken to run this process only on appropriate environments. It is recommended to have backups available of your environment.
Continue reading “How To: Stop and start a production OpenShift Cluster”
The Training and Certification organization is gearing up for Red Hat Summit 2019 in Boston! Stop by our booth space to learn about the countless innovations we developed over the past year, new offerings, updates to our certification programs, and more. Visit us to learn about the exciting new releases and events happening next week!
Continue reading “Take advantage of Training and Certification opportunities at Red Hat Summit”
This diagram represents the reference architecture for a full high availability and disaster recovery solution. This solution can be individually tailored to address a single availability solution. For example, if only disaster recovery is needed the configuration supports exclusion of the HA replica.
Continue reading “Ansible Tower High Availability and Disaster Recovery”
Most integration projects start small. However, in order to keep the lights on, businesses need to ensure these instances have high availability requirements and scalability to keep up with growing workloads. But how can you automate the deployment of a high availability configuration, while continuing to process messages without losing data?
In this short video, we discuss a few tips for creating Ansible playbooks to deploy AMQ brokers throughout your enterprise.
Continue reading “Red Hat Consulting: Creating Ansible Playbooks to Deploy AMQ7”