Bug 1421119 - [DOC][RFE] VCenter port and supported versions
Summary: [DOC][RFE] VCenter port and supported versions
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: 6.2.8
Hardware: All
OS: Linux
unspecified
low
Target Milestone: Unspecified
Assignee: satellite-doc-list
QA Contact: satellite-doc-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-10 12:04 UTC by Sergi Jimenez Romero
Modified: 2018-10-03 01:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-03 01:19:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sergi Jimenez Romero 2017-02-10 12:04:08 UTC
Document URL: 

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/provisioning-guide/chapter-9-provisioning-virtual-machines-in-vmware-vsphere

Section Number and Name: 

All

Describe the issue:

* While configuring VCenter for provisioning VMs from Satellite server, reading the documentation the ports being used and compatible versions were not found.

Suggestions for improvement: 

While the document is pretty much self explanatory, we've found a couple of improvements that could be added:

* A mention to what ports are being used to communicate to VCenter would be useful for customers having firewalls, either on the Satellite server or a physical firewall in between the VCenter and the Satellite server.

* VCenter supported versions would also be helpful. 

Additional information:

Comment 2 Andrew Dahms 2018-10-03 01:19:46 UTC
Thank you for raising this bug.

We have evaluated this request, and while we recognize that it is a valid request for the documentation, we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. 

If you have any concerns about this, please feel free to contact Andrew Dahms.


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