Unsolved

This post is more than 5 years old

3038

October 14th, 2010 02:00

Atmos Cloud support services, handling different accounts

Hi All,

We are investigating into Atmos to offer it to customers as backend integration for some of our products.

However, we could not find answers to all of our questions.

There is Atmos Online, which is like proof of concept, developer friendly cloud, but customer can also buy their own (or for example, upgrade existing Celerra boxes with Atmos service).

With Atmos Online, there are user accounts, one can then further split usage by introducing tokes. It is also possible to monitor usage per token etc.

Question is, are these services build on top of Atmos, or is it something that comes with Atmos product?

None of these APIs are referenced in Programming Guide, thus the question.

We are interested in covering the following scenarios:

- have multiple different accounts access Atmos

- have separate storage quota per account

- have ability to monitor usage of quota/bandwidth, for billing purposes

- have ability to share objects in cloud between accounts

To achieve these, do we need to:

1) build support services on top of Atmos API (described in programming guide)

- have only one global account

- control access rights with ACLs (also easy to implement sharing), seams wrong, as it is not really secure

- not sure how quota/bandwidth control could be implemented, maybe if there is another service that tracks usage separatelly

if there are multiple tokes defined under single account, is it possible to share objects between tokens, or is access limited to objects stored with certain token (token used to generate signature during post/get)?

2) support services providing quota/bandwidth/billing exist

- we can then utilize these APIs to implement above requirements

- not sure about sharing between accounts then?

So, does API as described in scenario 2 exist (if one buys EMC Atmos)? If yes, where can we get development guides/sdk/APIs?

Thanks in advance for answers,

Igor

October 14th, 2010 04:00

Follow-up after digging through Atmos API further.

Sharing seams to be covered in both scenarios. I got impression from reading programming guide that each user should have its own Atmos account (or at least, multiple authentication tokens but with same secret key)?

There also seams to be x-emc-delta field indicating how much storage usage has changed as result of request. However, there is no other info on how to get other information (for example, as provided in Atmos Online => Storage Service => Activity Dashboard).

222 Posts

October 14th, 2010 10:00

Igor,

One probably would not want to map each end-user to a given Atmos UID.  Most applications proxy the requests to Atmos using one or a few UIDs and shared secrets.

We have forthcoming support for measuring utilization, etc that lends itself to metering and chargeback.


Raj

222 Posts

October 14th, 2010 11:00

Igor,

It may be better if I connect you with someone in your region to spend time answering these questions in depth.

Can you send me a private message with your contact information, where you're located, etc?


Raj

No Events found!

Top