Browse Prior Art Database

Smart Client or Web Management Interface to Detect Object Storage Usage beyond Ordered Quantities in Real Time

IP.com Disclosure Number: IPCOM000241620D
Publication Date: 2015-May-18
Document File: 3 page(s) / 31K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to establish maximum limits when ordering storage in a cloud services account and then utilize that information as policy guidance before adding files to the storage. This approach alleviates storage consumption sprawl and budget overruns.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 40% of the total text.

Page 01 of 3

Smart Client or Web Management Interface to Detect Object Storage Usage beyond Ordered Quantities in Real Time

When object storage is ordered in clouds by a cloud tenant, an account is created with an ability to perform storage operations that include file upload, download, update, and delete. Once the object storage account is created, the account holder decides how containers are used and how much storage can be consumed. The cloud provides a scalable storage with a very large capacity and charges the user on a pay-as-you-go model. Typically, an additional client or a web management interface is provided to operate with the object storage using the credentials that include user name and Application Protocol Interface (API) key. Some vendors also provide the capability to perform the operations through the cloud portal.

When a government agency or enterprise customer orders the remote storage by providing a specific amount of storage (e.g., 100 GB), it is typically ordered with an order identification code or number for identification of invoices. Currently, the

pay-as-you-go model does not offer a method or system to order object storage with a known quantity up front. As a result, the usage of storage can quickly increase without restrictions; at the end of the month, the accumulated charges can be high, and might exceed the agency's or enterprise's procurement budget. This causes over consumption of storage beyond the budget and exceeds the forecasted spend on storage.

Typically, quotas for storage levels and object quantities are established at the object storage management layer. With this approach, scalability is a problem, as thousands to millions of objects might be uploaded into the object storage. This causes difficulties in managing quotas at the storage layer, slows processing (i.e. causes bottlenecking), and affects the performance at the server level due to the checks it needs to perform for every operation. In addition, because of the eventual consistency model of the object store, it is not possible to immediately determine whether the quota has been exceeded.

Example problem with a use case: Assume 98GB is consumed in object store and the client wants to upload a file with an additional 5GB. Due to the eventual consistency storage model, the client can upload and consume network bandwidth on the client device (if mobile, pays additional charges), to be finally rejected.

Some of the known solutions to this problem, specifically for the object storage, establish thresholds and alarms at some percentage. The disadvantage of this approach is that the system sends notifications even though there is probably enough space to place some files. This solution presented herein addresses that issue as well.

The novel solution is a method to establish maximum limits when ordering storage and then utilize that information as policy guidance before adding files to the storage. This approach alleviates the storage consumption s...