|
|
@@ -0,0 +1,56 @@
|
|
|
+### Storage Provider Responsibilities
|
|
|
+1. Maintain the Confidentiality, Integrity and Availability values of the Gateway Provider content
|
|
|
+2. Report any incident that may affect the Gateway Provider’s data in terms of Confidentiality, Integrity and Availability.
|
|
|
+3. Comply to KRs 1-6 listed below
|
|
|
+4. Storage Provider is liable to follow all the security standards and policies as specified by Gateway Provider and follow all the laws and regulations.
|
|
|
+5. Log any Incidents, assign them a unique number for reference, and track for resolution.
|
|
|
+
|
|
|
+Non-compliance or failure to meet the service levels for more than ___ times in 30 days, may lead to Storage Provider termination. A termination within six months shall entail the Gateway Provider for the refund of full amount paid till date, else it will be calculated on prorate basis.
|
|
|
+
|
|
|
+### Storage Provider Contact Information
|
|
|
+Storage Provider is expected to provide the contact call tree and the escalation matrix for the services it offers. On a minimum it shall provide for the following:
|
|
|
+1. Business Working Hours
|
|
|
+2. Contact Details of Support Personnel (Normal and After Office Working Hours)
|
|
|
+3. Contact Details of Designated Account Manager in case of Escalation (Normal and After Office Working Hours)
|
|
|
+
|
|
|
+Failure to provide the above information may result in a <sanction type>
|
|
|
+
|
|
|
+### Maintenance Windows
|
|
|
+1. A maintenance window will be agreed between Gateway Provider and Storage Provides considering the
|
|
|
+availability requirements. It is optimum to schedule it during non-business
|
|
|
+hours or when the expected load/usage of the service is at a minimum. Usually
|
|
|
+Friday/Saturday 00:01 to 04:00 <timezone>.
|
|
|
+2. If downtime is expected then alternate arrangement for continuous service must
|
|
|
+be made by a Storage Provider.
|
|
|
+3. All planned activities shall be carried out during the maintenance window and in
|
|
|
+compliance with the <maintenance procedure>.
|
|
|
+4. In case of unplanned outages, a verbal approval from the Gateway Provider shall be
|
|
|
+deemed suitable for carrying out the necessary correctional activities.
|
|
|
+
|
|
|
+Failure to communicate and agree upon maintenance windows may result in a Storage Provider slash. Amount to slash may depend on the number of Gateway Providers impacted by an improperly communicated or uncommunicated maintenance.
|
|
|
+
|
|
|
+
|
|
|
+### Key Result 1 - Uptime
|
|
|
+"Keep nodes Uptime above 90%."
|
|
|
+
|
|
|
+If Storage Provider fails to meet the uptime KR, then a slash of X tJOY will be executed for every hour of missed service levels, calculated over a 30 day period.
|
|
|
+
|
|
|
+### Key Result 2 - Sync Speed
|
|
|
+"Keep average sync speed at <number>"
|
|
|
+
|
|
|
+### Key Result 3 - Storage
|
|
|
+"Maintain less than a 24h and 20GB storage being full"
|
|
|
+
|
|
|
+### Key Result 4 - Upload Failures
|
|
|
+Maintain fewer than `<number>%` of uploads failing.
|
|
|
+
|
|
|
+### Key Result 5 - Rendering Time
|
|
|
+"Maintain some `<number>`"
|
|
|
+
|
|
|
+### Key Result 6 - Upload Speed
|
|
|
+Maintain an average upload speed of `n`MB/s.
|
|
|
+
|
|
|
+
|
|
|
+Non-compliance to any of the KRs above may result in a Storage Provider slash. Amount to slash may depend on the number of Gateway Providers impacted by a non-compliant Storage Provider.
|
|
|
+
|
|
|
+
|
mochet