Good discussion here. I probably didn't provide sufficient background when I started the thread. The whole topic of recording storage originated following an OPNFV TSC meeting. Their TSC was asked (by Jim Baker) about recording their meetings like we do here. One of the big objections raised against doing so was the high cost of storage. The cost certainly isn't "high", but it is also non-zero and of course growing. Asking LFN projects to look at a retention policy for recordings was a logical response to that.
A couple of other points that I was going to bring up in the TSC meeting today. - The storage we use should already be in tiered AWS, so I think that is probably covered. - Regarding the amount of storage ONAP has tied up with .mp4s, I dunno. Jess has a standing meeting today where the topic is being discussed. - Doing much in the way of analysis beyond #TB in use @$$ per TB would not be a good use of anyone's time, neither would having to change a gazillion links to new locations. - If a retention policy is desired by y'all, tying it to release cycles rather than a set time-based deletion does make better sense than what I originally suggested. Hope that helps frame it up better. :-) -kenny -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Chaker Al-Hakim Sent: Wednesday, November 13, 2019 1:07 PM To: [email protected] Subject: Re: [onap-tsc] Zoom Recording Retention Policy Hi All. AWS Glacier deep Archive is definitely an option that can be more cost effective. However, if we decide to delete or to use cheap archive, I would assume we would still need to update all the links on all the wiki pages that reference a specific recording or large file. Otherwise we would end up with broken links and we would lose any reference to the original file; Any archive, cheap or otherwise, would be of no use unless we put plans in place to also create 301 redirects for all files we plan to archive Regards, Chaker -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Haiby, Ranny (Samsung) via Lists.Onap.Org Sent: Wednesday, November 13, 2019 12:59 PM To: [email protected] Subject: Re: [onap-tsc] Zoom Recording Retention Policy Hi, One more suggestion if I may - Whatever the community decides for retention period, it is best to use long term (cheap) archiving for the old recordings, instead of just purging them. Something like AWS Glacier that is $1/TB: https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Faws.amazon.com%2Fglacier%2F&data=02%7C01%7Cchaker.al.hakim%40futurewei.com%7C37ee8504c9b34c9ebe1708d768631e67%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637092647249252958&sdata=jxd%2FHrWrquPo%2FJ7TfQVFlWblL15iL%2FgCyd7mOxUlric%3D&reserved=0 Regards, Ranny. On 11/13/19, 3:48 AM, "[email protected] on behalf of Krzysztof Opasiak via Lists.Onap.Org" <[email protected] on behalf of [email protected]> wrote: Hi, even through I'm not a TSC I'd like to let you know my feedback. On 12.11.2019 17:06, Perala, Timo (Nokia - FI/Espoo) wrote: > Hello, > > I would like to understand first > > 1) What’s the current cost and what is the savings potential e.g. if we > implement policy along the lines outlined below. > > 2) What’s the volume split between projects/TSC & SubCs/DDFs. > > 3) Assuming the TSC & SubC meeting recordings and DDF recordings > constitute minority, I have inclination to keep them longer (e.g. > indefinitely to start with). > > 4) Project recordings to stay there for the full release. I guess that > would in practice mean 6 moths + small delta. I support Timo's point of view. In general I believe that we should bind the recording lifecycle to ONAP release cadence not the absolute time. Best regards, -- Krzysztof Opasiak Samsung R&D Institute Poland Samsung Electronics -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5623): https://lists.onap.org/g/onap-tsc/message/5623 Mute This Topic: https://lists.onap.org/mt/54381323/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
