On 08/07/2012 10:24 AM, samridh srinath wrote: > Hi David, > > On Tue, Aug 7, 2012 at 3:37 AM, David Lutterkort <lut...@redhat.com> wrote: > >> Hi Samridh, >> >> I think that would be a great addition to the DC API. Do you have an >> outline what the billing resources should look like, in particular what >> data and operations they could support ? > I think in terms of operations, as of now clients would only be able to GET > a bill via the billing API. > The bill would be created by the backend cloud provider. > I'm still getting around to what data they would support since the kind of > data returned by ec2 and GoGrid right now are quite different. > I'm trying to find a common model that could cover these providers and > hopefully all future providers also. It would be helpful if I could get > some assistance from existing developers on this end. :) >
Sammy, as discussed on IRC it seem that both EC2 and GoGrid make the current charges incurred up to this point available via an API call. The exact calls vary based on the cloud provider, with gogrid its a simple GET request, while with EC2 the user needs to configure a S3 bucket to place the billing data in, after which it is available via the normal mechanisms to access the bucket (these will be able to be invoked via deltacloud correct?). The drivers themselves can take care of these implementation details. Since both describe the amount charged to the account owner as well as the justification for those charges (memory usage, ip allocation, network traffic, etc) perhaps it makes sense to define a collection around 'charges' with data like 'value' and 'reason'. Any other data such as time ranges those charges were incurred would be useful as well. Perhaps you could flush out a simple xml schema around that and start working to define that collection. It would be nice if these providers exposed a way to retrieve the costs of their services via their APIs, but I haven't seen that yet and I'm not holding my breath. Thoughts? -Mo
