Bug 1170162

Summary:	[RHCI] How to configure high availability
Product:	Red Hat CloudForms Management Engine	Reporter:	Andrew Dahms <adahms>
Component:	Documentation	Assignee:	Suyog Sainkar <ssainkar>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Andrew Dahms <adahms>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.4.0	CC:	mfeifer, obarenbo, xlecauch
Target Milestone:	GA
Target Release:	5.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-08 02:42:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1174605
Deadline:	2014-12-18

Description Andrew Dahms 2014-12-03 12:42:57 UTC

Create an article in Drupal outlining how to configure high availability for Red Hat CloudForms.

The currently envisioned outline is as follows:

Overview
A conceptual introduction that talks about high availability in Red Hat CloudForms, and provides an overview of the task the user will perform. This section may contain diagrams and information that helps develop an understanding of the task.

Procedure
The actual steps required to configure high availability - only general options need be included.

A conclusion that provides a brief overview of what the user achieved, and a little information on what they can do next.

Comment 2 Suyog Sainkar 2014-12-09 03:52:27 UTC

I've drawn up an article outlining how to configure high availability for Red Hat CloudForms:

https://access.redhat.com/articles/1289263

The article is pending tech review and has not been published live yet.

Thanks!

Suyog

Comment 3 Marianne Feifer 2014-12-16 14:34:52 UTC

Comments that I made into the article on the RHCP:

Some of my comments/suggestions are in parentheses and some I made directly. Also, since this is a standalone document, the terms "worker appliance" and "database appiance" should be included. The worker appliance needs to do be configured to attach to the external DB and have the appropriate Server Roles enabled. The steps for connecting to the external database are incorrect for version 5.3. These are the steps for creating a CFME Appliance that hosts the database. You need a second procedure that shows how to enable Server Roles. This is probably already documented in the Settings and Ops guide.

Comment 4 Suyog Sainkar 2014-12-18 06:35:20 UTC

Hi Marianne,

Thanks for reviewing the article and sharing your feedback! I've incorporated the suggested changes. 

I've modified the steps for connecting to the external database for version 5.3. I've also drawn up a few simple steps to enable server roles and have included some information about it with a screenshot as well. Could you review the recent changes, please?

Besides, based on the info/links you shared in the email, I would like to include some of the following information about regions/zones, failover rules and setting priorities for the server roles. However, I'm unsure where I could fit the info best within the scope of this article. -Any thoughts?

"Regions are used primarily to consolidate multiple VMDBs into one master VMDB for reporting while zones are used to define functional groups of servers. There can be only one region per VMDB, but multiple zones per region (or VMDB). Some server roles are aware of each other across appliances at the region level. This means that redundancy and failover rules apply at the region level. You can also set priorities for the server roles that provide failover."

Thanks again!

Suyog

Comment 11 Andrew Dahms 2015-01-06 00:26:49 UTC

Checked in:

https://access.redhat.com/articles/1289263

All requested content has been added, and feedback from review implemented.