Currently we have documented (for Beta 1) RHV 4.2.0 with OCP 3.6.
By RHV 4.2 GA, the OCP version will be 3.9 and there will likely be changes to the current Metrics documentation as well as updating the links in the OpenShift Guide.
Can you please confirm that OpenShift 3.9 will be released in March and therefore this will be the version that the Metrics Store will run on by RHV 4.2 GA, or is it too close and therefore will not leave enough time for QE and documentation and therefore Metrics will be released on OCP 3.7?
Reducing the time estimate now that I know what is involved at the time of writing. May need to be slightly increased on depending on QE test results.
Accepting into GA program and assigning to Emma for review.
Please review this MR:
I'm reading the OCP documentation for required ports, and if I understand correctly, we are implementing the solution described in table 7, IaaS.
If this is the case, can you please clarify whether we need to open both 80 AND 443 as we documented, or 80 OR 443 as stated in the doc .
(In reply to Emma Heftman from comment #16)
> Hi Rich
> I'm reading the OCP documentation for required ports, and if I understand
> correctly, we are implementing the solution described in table 7, IaaS.
> If this is the case, can you please clarify whether we need to open both 80
> AND 443 as we documented, or 80 OR 443 as stated in the doc .
There are 4 ways the metrics machine can be accessed externally:
- ssh (for ansible and for login) - requires port 22
- Elasticsearch - requires port 9200
- Kibana - requires port 443
- The OpenShift UI - requires port 8443
The OpenShift documentation isn't explicit about all of these, or maybe isn't very clear. ovirt/RHV uses OpenShift in "External to Master" (the metrics node is an all-in-one, so that means it is also an OpenShift master node), and in "IaaS Deployments" mode:
"22 TCP Required for SSH by the installer (ansible) or system administrator." - self explanatory
"80 or 443 TCP For HTTP/HTTPS use for the router. Required to be externally open on node hosts, especially on nodes running the router." - it isn't obvious, but this is for Kibana access. We require TLS for everything, so that means port 443 - we do not use port 80.
"8443 TCP For use by the OpenShift Container Platform web console, shared with the API server." - this is for metrics users to have access to the underlying OpenShift Management UI
The final one is port 9200, for Elasticsearch, but that one is specific to the ovirt/RHV use case.
This has been published in the Customer Portal:
Can this link help in this case