Re: [gpfsug-discuss] Recharging where HSM is used

2018-05-04 Thread Marc A Kaplan
"Not sure if the V and M misc_attributes are the same for other tape backends..." define(is_premigrated,(MISC_ATTRIBUTES LIKE '%M%' AND MISC_ATTRIBUTES NOT LIKE '%V%')) define(is_migrated,(MISC_ATTRIBUTES LIKE '%V%')) define(is_resident,(NOT MISC_ATTRIBUTES LIKE '%M%')) There are good, valid

Re: [gpfsug-discuss] Recharging where HSM is used

2018-05-03 Thread valdis . kletnieks
On Thu, 03 May 2018 16:52:44 +0100, Jonathan Buzzard said: > The test that I have used in the past for if a file is migrated with a > high degree of accuracy is > > if the space allocated on the file system is less than the > file size, and equal to the stub size then presume the file >

Re: [gpfsug-discuss] Recharging where HSM is used

2018-05-03 Thread Jeffrey R. Lang
ct: Re: [gpfsug-discuss] Recharging where HSM is used Specifically with IBM Spectrum Archive EE, there is a script (mmapplypolicy with list rules and python since it outputs many different tables) to provide the total size of user files by file states. This way you can charge more for files that

Re: [gpfsug-discuss] Recharging where HSM is used

2018-05-03 Thread Simon Thompson (IT Research Support)
@spectrumscale.org" <gpfsug-discuss@spectrumscale.org> Date: Thursday, 3 May 2018 at 16:03 To: "gpfsug-discuss@spectrumscale.org" <gpfsug-discuss@spectrumscale.org> Subject: Re: [gpfsug-discuss] Recharging where HSM is used Stephen, Bryan, Thanks for the input, it’s grea

Re: [gpfsug-discuss] Recharging where HSM is used

2018-05-03 Thread Jonathan Buzzard
On Thu, 2018-05-03 at 15:02 +, Sobey, Richard A wrote: > Stephen, Bryan, >   > Thanks for the input, it’s greatly appreciated. >   > For us we’re trying – as many people are – to drive down the usage of > under-the-desk NAS appliances and USB HDDs. We offer space on disk, > but you can’t

Re: [gpfsug-discuss] Recharging where HSM is used

2018-05-03 Thread Khanh V Ngo
Specifically with IBM Spectrum Archive EE, there is a script (mmapplypolicy with list rules and python since it outputs many different tables) to provide the total size of user files by file states.  This way you can charge more for files that remain on disk and charge less for files migrated to

Re: [gpfsug-discuss] Recharging where HSM is used

2018-05-03 Thread Sobey, Richard A
-discuss-boun...@spectrumscale.org <gpfsug-discuss-boun...@spectrumscale.org> On Behalf Of Stephen Ulmer Sent: 03 May 2018 14:03 To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org> Subject: Re: [gpfsug-discuss] Recharging where HSM is used I work for a partner, but I occas

Re: [gpfsug-discuss] Recharging where HSM is used

2018-05-03 Thread Jan-Frode Myklebust
Since I'm pretty proud of my awk one-liner, and maybe it's useful for this kind of charging, here's how to sum up how much data each user has in the filesystem (without regards to if the data blocks are offline, online, replicated or compressed): # cat full-file-list.policy RULE EXTERNAL LIST

Re: [gpfsug-discuss] Recharging where HSM is used

2018-05-03 Thread Stephen Ulmer
I work for a partner, but I occasionally have to help customers work on cost justification that includes charge-back (or I encourage them to do show-back to alleviate some political concerns). I’d also like to see what people are doing around this. If I may ask a question, what is the goal for

[gpfsug-discuss] Recharging where HSM is used

2018-05-03 Thread Sobey, Richard A
Hi all, I'd be interested to talk to anyone that is using HSM to move data to tape, (and stubbing the file(s)) specifically any strategies you've employed to figure out how to charge your customers (where you do charge anyway) based on usage. On-list or off is fine with me. Thanks Richard