[
https://issues.apache.org/jira/browse/HDDS-7943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
István Fajth updated HDDS-7943:
-------------------------------
Description:
Once HDDS-7817 is resolved, and the HTTP and HTTPS port information is
available in the DatanodeDetails object, update the backend for the Node Status
table on the SCM UI.
Add the port information to the returned Datanode information, and add a link
to the Datanode WebUI in the table around the Datanode hostname.
Note that, based on the related HTTP policy config (ozone.http.policy) that is
represented via HTTPConfig#Policy, there can be 3 configured case for every DN
and SCM:
1. HTTP_ONLY -> the service does serve its webUI via HTTP
2. HTTPS_ONLY -> the service does serve its webUI via HTTPS
3. HTTP_AND_HTTPS -> the service does serve its webUI via HTTP and HTTPS both.
In these cases, either HTTP or HTTPS ports or both should be set on the
DataNodeDetails object, and with that transferred to the SCM UI code to display.
On the SCM UI we can use the following logic to decide what we would like to
show:
1. if there is only either HTTP or HTTPS port is there for the DataNode,
provide the link with the respective URL scheme being applied.
2. if there are both HTTP and HTTPS ports provided the UI has to select the one
that fits to the current URL scheme, so if SCM webUI is shown via HTTP, it
should link to the HTTP port with HTTP URL scheme, if the SCM webUI is shown
via HTTPS it should link to the HTTPS port with the HTTPS URL scheme.
was:
Once HDDS-7817 is resolved, and the HTTP and HTTPS port information is
available in the DatanodeDetails object, update the backend for the Node Status
table on the SCM UI.
Add the port information to the returned Datanode information, and add a link
to the Datanode WebUI in the table around the Datanode hostname.
Following should be followed to decide if HTTP or HTTPS URLs should be linked:
- SCM UI is served over HTTP -> provide HTTP link, else if HTTP port is not
available provide HTTPS link else if no port information is available, do not
provide link
- SCM UI is served over HTTPS -> provide HTTPS link, else if HTTPS port is not
available provide HTTP link, else if no port information is available, do not
provide link
> Link Datanode WebUIs from the Node Status table on SCM WebUI
> ------------------------------------------------------------
>
> Key: HDDS-7943
> URL: https://issues.apache.org/jira/browse/HDDS-7943
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: István Fajth
> Assignee: Debadatta
> Priority: Major
>
> Once HDDS-7817 is resolved, and the HTTP and HTTPS port information is
> available in the DatanodeDetails object, update the backend for the Node
> Status table on the SCM UI.
> Add the port information to the returned Datanode information, and add a link
> to the Datanode WebUI in the table around the Datanode hostname.
> Note that, based on the related HTTP policy config (ozone.http.policy) that
> is represented via HTTPConfig#Policy, there can be 3 configured case for
> every DN and SCM:
> 1. HTTP_ONLY -> the service does serve its webUI via HTTP
> 2. HTTPS_ONLY -> the service does serve its webUI via HTTPS
> 3. HTTP_AND_HTTPS -> the service does serve its webUI via HTTP and HTTPS both.
> In these cases, either HTTP or HTTPS ports or both should be set on the
> DataNodeDetails object, and with that transferred to the SCM UI code to
> display.
> On the SCM UI we can use the following logic to decide what we would like to
> show:
> 1. if there is only either HTTP or HTTPS port is there for the DataNode,
> provide the link with the respective URL scheme being applied.
> 2. if there are both HTTP and HTTPS ports provided the UI has to select the
> one that fits to the current URL scheme, so if SCM webUI is shown via HTTP,
> it should link to the HTTP port with HTTP URL scheme, if the SCM webUI is
> shown via HTTPS it should link to the HTTPS port with the HTTPS URL scheme.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
