In our environment managing the GPFS policies (or anything GPFS) are a bit
of an Art form and really only a few people out of a sea of engineers
can/will do it. So I like to keep the GPFS policies simple and durable.
If you really wanted to you could generate a list of every US (or whatever
On 01/02/2021 21:09, Owen Morgan wrote:
CAUTION: This email originated outside the University. Check before
clicking links or attachments.
Jonathan,
If I have a single policy file with all the related department rules and
each time they want to add additional rules with different working day
Jonathan,
If I have a single policy file with all the related department rules and each
time they want to add additional rules with different working day thresholds
maybe using this -M method is easier. Its clear that the 'maths' and
date/timestamp manipulation is easier in shell (my preferred
On 01/02/2021 18:11, Jan-Frode Myklebust wrote:
CAUTION: This email originated outside the University. Check before
clicking links or attachments.
Agree.. Write a policy that takes a "mmapplypolicy -M var=val" argument,
and figure out the workdays outside of the policy. Something like:
# cat
Sent by: gpfsug-discuss-boun...@spectrumscale.org
> To: gpfsug-discuss@spectrumscale.org
> Cc:
> Subject: [EXTERNAL] Re: [gpfsug-discuss] gpfsug-discuss Digest, Vol 108,
> Issue 18
> Date: Sat, Jan 30, 2021 10:29
>
> On 30/01/2021 00:31, Owen Morgan wrote:
>
&
Hi Owen,
Could you let me know who you are working with at Pixit? I'll drop them a note and have a chat.
Kind regards
Adam Willis
Client Technical Specialist
IBM Systems
E-mail: adam.wil...@ibm.com
Mobile: +44 (0)7956 404666
https://www.ibm.com/uk-en
"The information contained in
To me, it feels like you need to do the search the other way around.
Firstly, from the target of say "4 weekdays ago", work out how many real days ago that was.
Then use that as a criteria in mmfind or mmapplypolicy.
Daniel
_Daniel
On 30/01/2021 00:31, Owen Morgan wrote:
[SNIP]
I would prefer to stay in the bounds of the SQL policy rule setup as
that is the framework I have created and started to implement..
In general SQL is Turing complete. Though I have not checked in detail I
believe the SQL of the policy engine
No problem at all. If you can't get mmfind compiled... you can do
everything it does via mmapplypolicy. But it is certainly easier with
mmfind to add in options dynamically.
I have modified the program that mmfind invokes... I forget offhand
tr_Polsomething.pl to add functions such as
Alec,
Thank you for your response!
I get it now! And, I also understand some of the other peoples responses better
as well!
Not only does this make sense I also suppose that it shows I have to broaden my
'ideas' as to what tools avaliable can be used more than mmapplypolicy and
policy files
Also a caution on this... you may want to retain the file's modified time
in something like purge.modified... so you can also re-calc for files where
purge.modified != file modified time. Else you may purge something too
early.
Alec
On Fri, Jan 29, 2021 at 6:53 PM Alec wrote:
> Based on the
Based on the problem you have.
I would write an mmfind / mmxarg command that sets a custom attr such as
puge.after, have a ksh/perl/php script that simply makes the necessary
calculations using all the tricks it has... Skip files that already have
the attribute set, or are too new to bother
Hi all,
Sorry I appear to have missed a load of replies and screwed up the threading
thing when looking online... not used to this email group thing! Might look at
the slack option!
Just wanted to clarify my general issue a bit:
So the methodology I've started to implement is per department
est, Vol
108, Issue 18
Sent by:gpfsug-discuss-boun...@spectrumscale.org
To calculate this directly (if you don't want to depend on a utility)
consider the following steps. There
are many more such algorithms in the wonderful book Calenderical
Calculations.
1. Take the last
To calculate this directly (if you don't want to depend on a utility)
consider the following steps. There
are many more such algorithms in the wonderful book Calenderical
Calculations.
Take the last two digits of the year.
Divide by 4, discarding any fraction.
Add the day of
15 matches
Mail list logo
