[
https://issues.apache.org/jira/browse/HDDS-7797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
smita updated HDDS-7797:
------------------------
Description:
This requirement is to add a capability in Recon to tag storage entities at
volume level, bucket level, key level, directory/sub-directory and file level
for their access heat. In other words, recon should be able to tag entities
with {*}Most Frequently Accessed (MFA), Frequently Accessed (FA) and Less
Frequently Accessed (LFA) or Cold data{*}. This will help admin users determine
the access pattern of various entities which will in turn help in tiering (Hot,
Warm, Cold) of ozone data. Access pattern or heat can be determined based on
both READ and WRITE operations on entities.
New Changes in UI
1. Change the API signature to take path as input instead of all 3 (volume,
bucket, path). This "path"
will be used as input to Solr query for "resName". Param name is "path" and do
basic validations at UI like no junk character, no backward slashes allowed.
2. Another input on UI for user to provide "Entity Type" which will have only 3
valid values (Volume, Bucket, Key). "entityType" is the param name for API.
This willl be used as input to Solr Query as "resType".Values should be passed
as lowercase. E.g For Volume, value will be "volume".
3. Take input from UI for "HeatMap Based On Last <24H or 7Days or 90 Days or
Custom Date Selector which
cannot be more than 90 Days> Access MetaData".
> Recon UI Changes and representation of heatmap in Recon
> -------------------------------------------------------
>
> Key: HDDS-7797
> URL: https://issues.apache.org/jira/browse/HDDS-7797
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Recon
> Reporter: Devesh Kumar Singh
> Assignee: smita
> Priority: Major
>
> This requirement is to add a capability in Recon to tag storage entities at
> volume level, bucket level, key level, directory/sub-directory and file level
> for their access heat. In other words, recon should be able to tag entities
> with {*}Most Frequently Accessed (MFA), Frequently Accessed (FA) and Less
> Frequently Accessed (LFA) or Cold data{*}. This will help admin users
> determine the access pattern of various entities which will in turn help in
> tiering (Hot, Warm, Cold) of ozone data. Access pattern or heat can be
> determined based on both READ and WRITE operations on entities.
> New Changes in UI
> 1. Change the API signature to take path as input instead of all 3 (volume,
> bucket, path). This "path"
> will be used as input to Solr query for "resName". Param name is "path" and
> do basic validations at UI like no junk character, no backward slashes
> allowed.
> 2. Another input on UI for user to provide "Entity Type" which will have only
> 3 valid values (Volume, Bucket, Key). "entityType" is the param name for API.
> This willl be used as input to Solr Query as "resType".Values should be
> passed as lowercase. E.g For Volume, value will be "volume".
> 3. Take input from UI for "HeatMap Based On Last <24H or 7Days or 90 Days or
> Custom Date Selector which
> cannot be more than 90 Days> Access MetaData".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
