Bug 1274253 - [cfme][docs] add chapter about IP connectivity between appliances
[cfme][docs] add chapter about IP connectivity between appliances
Status: CLOSED EOL
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation (Show other bugs)
5.4.0
Unspecified Unspecified
medium Severity medium
: GA
: 5.5.2
Assigned To: Red Hat CloudForms Documentation
Red Hat CloudForms Documentation
https://access.redhat.com/documentati...
doc
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-22 07:28 EDT by Evgheni Dereveanchin
Modified: 2017-06-20 03:50 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-06-20 03:50:06 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Evgheni Dereveanchin 2015-10-22 07:28:11 EDT
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_CloudForms/3.2/html/Deployment_Planning_Guide/index.html#Requirements1

Section Number and Name: 
1.2. Requirements

Describe the issue: 
In some deployments CFME appliances are separated from each other by firewalls that require explicit rules to permit traffic.

Suggestions for improvement: 
Add a section of which TCP ports need to be open between appliances, and what they are used for.

Additional information: 
Some ports may only be needed during deployment, yet unused during appliance lifetime - this should also be documented.
Comment 2 Josh Carter 2015-10-22 15:13:25 EDT
All of the ports used by cloudforms can be found here https://access.redhat.com/documentation/en-US/Red_Hat_CloudForms/3.2/html-single/Installing_CloudForms_on_Red_Hat_Enterprise_Linux_OpenStack_Platform/index.html

4. Security
⁠
Table 1. Ports Used by CloudForms Management Engine
Comment 3 Evgheni Dereveanchin 2015-10-23 08:05:59 EDT
Hi Josh

Thanks for the info. This doesn't look RHOS specific - I wonder why it's hidden so deep in this specific guide and if we could move it into a generic guide.

Also, it would be interesting to see which port each component needs to know where they should be open. This is partially done in the table you shared.
Comment 4 Andrew Dahms 2016-01-05 23:50:48 EST
Assigning to Petr for review.
Comment 5 Andrew Dahms 2016-01-07 19:16:28 EST
Returning to the default assignee to be re-triaged as the schedule allows.

Note You need to log in before you can comment on or make changes to this bug.