Bug 1328470 - [Docs][RFE] Network Port Diagram to build up an RHEV environment
Summary: [Docs][RFE] Network Port Diagram to build up an RHEV environment
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.3.1
: 4.3.0
Assignee: Rolfe Dlugy-Hegwer
QA Contact: Tahlia Richardson
Rolfe Dlugy-Hegwer
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-19 13:12 UTC by Chetan Nagarkar
Modified: 2022-03-13 14:21 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-22 14:52:46 UTC
oVirt Team: Network
Target Upstream Version:
lsvaty: testing_plan_complete-


Attachments (Terms of Use)
Proposed diagram #1 Red Hat Enterprise Virtualization Manager Firewall Requirements (25.05 KB, application/pdf)
2018-12-27 18:06 UTC, Rolfe Dlugy-Hegwer
no flags Details
Proposed diagram #2, Virtualization Host Firewall Requirements (21.52 KB, application/pdf)
2018-12-28 12:39 UTC, Rolfe Dlugy-Hegwer
no flags Details
Proposed diagram #3, Firewall Requirements, Virtualization Host, Directory Server, and Database Server (22.71 KB, application/pdf)
2018-12-28 13:36 UTC, Rolfe Dlugy-Hegwer
no flags Details
Source for Proposed diagram #1 Red Hat Enterprise Virtualization Manager Firewall Requirements (22.28 KB, application/vnd.oasis.opendocument.graphics)
2019-01-08 17:12 UTC, Rolfe Dlugy-Hegwer
no flags Details
Source for Proposed diagram #3, Firewall Requirements, Virtualization Host, Directory Server, and Database Server (16.44 KB, application/vnd.oasis.opendocument.graphics)
2019-01-08 17:14 UTC, Rolfe Dlugy-Hegwer
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45175 0 None None None 2022-03-13 14:21:34 UTC

Description Chetan Nagarkar 2016-04-19 13:12:37 UTC
Description of problem:
According to customer a document for all network connections is needed to build up an RHEV environment. Also a point customer mentioned that to have a picture of the connections is helping much more than just a table with some short description somewhere in the documentation.

Customer has given a link to a KB article from vmware as a reference as below:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2131180

Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization 3.6

Comment 16 Dan Kenigsberg 2018-12-25 11:51:33 UTC
We are unlikely to get to this during 4.2.z.

Comment 18 Rolfe Dlugy-Hegwer 2018-12-27 18:06:47 UTC
Created attachment 1517099 [details]
Proposed diagram #1 Red Hat Enterprise Virtualization Manager Firewall Requirements

Comment 20 Rolfe Dlugy-Hegwer 2018-12-27 18:32:51 UTC
Actually, I wonder if having a sortable table would completely alleviate the need for a diagram.

Comment 21 Rolfe Dlugy-Hegwer 2018-12-28 12:39:52 UTC
Created attachment 1517198 [details]
Proposed diagram #2, Virtualization Host Firewall Requirements

Comment 22 Rolfe Dlugy-Hegwer 2018-12-28 13:36:06 UTC
Created attachment 1517200 [details]
Proposed diagram #3, Firewall Requirements, Virtualization Host,  Directory Server, and Database Server

Replaces diagram #2 -

Comment 23 Rolfe Dlugy-Hegwer 2018-12-28 13:36:58 UTC
Comment on attachment 1517198 [details]
Proposed diagram #2, Virtualization Host Firewall Requirements

Disregard this diagram - See diagram #3 instead.

Comment 24 Rolfe Dlugy-Hegwer 2019-01-03 19:42:10 UTC
Hi Chethan. Please have a look at proposed diagrams #1 and #3. Do these satisfy the customer's information needs? Would appreciate your feedback. When we've finalized the information these show, we'll ask the graphics team to produce professional quality renderings of the same. Thank you!

Comment 25 Chetan Nagarkar 2019-01-04 19:01:50 UTC
Rolfe,

Thank you for your efforts. Diagrams look good to me but I have forwarded those to the customer for further recommendations.

I will update this BZ as soon as I get approval/suggestion from the customer. Hope this will help.

--
ChetanN

Comment 28 Rolfe Dlugy-Hegwer 2019-01-08 17:12:52 UTC
Created attachment 1519248 [details]
Source for Proposed diagram #1 Red Hat Enterprise Virtualization Manager Firewall Requirements

This is the odg source file which can be edited using LibreOffice Draw.

Comment 29 Rolfe Dlugy-Hegwer 2019-01-08 17:14:02 UTC
Created attachment 1519249 [details]
Source for Proposed diagram #3, Firewall Requirements, Virtualization Host,  Directory Server, and Database Server

This is the odg source file which can be edited using LibreOffice Draw.

Comment 32 eraviv 2019-01-17 08:22:03 UTC
Comments for the "Red Hat Virtualization Manager Firewall Requirements" diagram as compared to [1]:

1. "Vm Portal clients" also has access to "Red Hat Virtualization Manager" over 6100 (row 5)
2. 54323/TCP (7) should go from "Administration Portal Clients" to "Red Hat Virtualization Manager with ImageIO proxy" and not to "Red Hat Virtualization Manager"


Comments for the "Red Hat Virtualization Host Firewall Requirements" diagram as compared to [2]:
- Diagram and table match exactly.
- Diagram is beautiful, I would consider colourizing some of the arrows for better clarity.




[1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/installation_guide/networking-requirements
#Table 1.4. Red Hat Virtualization Manager Firewall Requirements

[2] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/installation_guide/networking-requirements
#Table 1.5. Virtualization Host Firewall Requirements

Comment 33 eraviv 2019-01-17 08:34:44 UTC
IMO the diagrams are quite dense, so concatenating them into a single diagram would be counter-productive.
Also, technically, they are not related because one is about the configuration required on the Manager and the other is about the configuration required on the hosts.
So an admin person would be anyway following them separately and in a sequential order.
At least, if we are forced to provide a unified diagram, we should also provide the two separate ones in our documentation.

IMO it would be more beneficial to add the purpose (as documented in the tables) of the arrows (ports) on the diagrams so that a use may know what service to expect when each configuration is completed.
Also, using colors would make the diagrams clearer.

Comment 34 Dominik Holler 2019-01-17 14:31:27 UTC
I created bug 1667131 for the ports I missed.

Comment 36 Sandro Bonazzola 2019-01-28 09:41:30 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 39 Rolfe Dlugy-Hegwer 2019-02-26 16:48:58 UTC
The updated network diagram associated with this request is available from the following knowledgebase article: https://access.redhat.com/articles/3932211

Comment 40 Petr Kovar 2019-03-04 17:23:05 UTC
Okay to close?


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