UNSOLVED
B
Brian_Coulombe_
1 Rookie
•
107 Posts
0
1828
October 21st, 2016 05:00
FilePool CLI policy
Right now I cannot get our cluster off 7.2.1.1 (we have a hold on changes for a while). The GUI does not work in 7.2.1.1 for FilePool/SmartPool policies. Basically I am trying to create three policies and I have to do this 100% through the CLI.
1. Data sits on the S200 nodes for 1 day for ingest and modification.
2. Data between 2 and 45 days needs to sit on Tier 2.
3. Anything older than 45 days needs to sit on Tier 3.
Here is what I have but I cannot seem to figure out how to get this to work based on "changed date ranges". Feel free here anyone to toss some options to get it to work the way I want. The documentation for SmartPools could be more descriptive on HOW we could use the options.
isi filepool policies create Tier1_Policy --description "Ingest Policy - New Data Here" --data-storage-target s200_19tb_1.2tb-ssd_48gb --data-ssd-strategy metadata --begin-filter --path= --and --changed-time=1D --operators=gt --end-filter
isi filepool policies create Tier1_to_Tier2 --description "Tier 1 to Tier 2" --data-storage-target x400_120tb_2.3tb-ssd_48gb --data-ssd-strategy metadata --begin-filter --path= --and --changed-time=2D:45D --operator=gt --end-filter
isi filepool policies create Tier2_to_Tier3 --description "Tier 2 to Tier 3" --data-storage-target x400_120tb_48gb --data-ssd-strategy metadata --begin-filter --path= --and --changed-time=46D --operator=gt --end-filter
1325
0
Posted October 21st, 2016 09:00
Recalling that SmartPools for each file checks the rules
in order and stops evaluating more rules after the first match,
it is makes often sense to organize subsequent ranges into a cascade like this:
1. changed <= 1 day
2. changed <= 45 days (> 1 day is implied, because any file changed <= 1 day finishes processing at rule 1.)
3. anything else (> 45 days is implied)
The syntax would be something like:
1. ... and --changed-time=1D --operator=lt (lt for "less than")
2. ... and --changed-time=45D --operator=lt
3. (no additional clause needed after --path)
Funny thing aside, SmartPools rules are one of the rare occasions
where I switch from CLI to GUI (sic)... but yeah there have been glitches in the GUI.
I even remember a situation where both CLI and GUI refused to accept
a certain SmartPools rule and I had to revert to isi_gconfig
Cheers
-- Peter
Brian_Coulombe_
1 Rookie
•
107 Posts
1325
0
Posted October 21st, 2016 09:00
Thanks Peter. I will take a look at this and make the recommended changes. I personally prefer to use the GUI when setting up SmartPool policies but in this case, my hands are tied due to the bug on 7.2.1.1 and the fact we're on an upgrade freeze. Regardless, I have to get this cluster under control. Can't deal with another global spillover issue.