You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@libcloud.apache.org by Markos Gogoulos <mg...@mist.io> on 2013/07/26 13:19:22 UTC

libcloud pricing

 

Hi all, 

I'd like to ask if there is any progress regarding
pricing, after the June 2013 libcloud meeting. Tomaz you mentioned a
command line tool for updating the file, is there anything available?
The prices for Rackspace are outdated (btw how do you get prices for
Rackspace? Manually after checking the page, or through API?). For ec2
there a nice tool at https://github.com/erans/ec2instancespricing that
could start as a base. 

A major problem hovwever is that prices are
related to image types besides the size, which means that ec2 us-west
charges 0.025 for linux, 0.085 for rhel and 0.035 for mswin :(


Libcloud does not take this into account and I wonder if this is
something scheduled to implement, and how hard would be a refactor.


Thanks for sharing any thoughts, 

Regards, 

Markos 
 

Re: libcloud pricing

Posted by Tomaz Muraus <to...@apache.org>.
I've opened a Github pull request with an initial implementation prototype
- https://github.com/apache/libcloud/pull/127.

Feedback is welcome, so if you care about this feature, please visit the
pull request and post your feedback and comments there.

On Sat, Jul 27, 2013 at 3:10 PM, Tomaz Muraus <to...@apache.org> wrote:

> Hi,
>
> I've started to work on it soon after the meetup (
> https://github.com/Kami/libcloud/tree/pricing_file_changes), but I got
> distracted with some other things and never managed to finish it.
>
> The good thing is that is should be fairly easy and straight-forward to
> implement the tool which downloads the latest pricing data from our git
> repository and saved it into ~/libcloud/pricing.json.
>
> As far as getting the prices for Rackspace - like most of the providers,
> they don't have an API so we update those manually.
>
> On Fri, Jul 26, 2013 at 1:19 PM, Markos Gogoulos <mg...@mist.io>wrote:
>
>>
>>
>> Hi all,
>>
>> I'd like to ask if there is any progress regarding
>> pricing, after the June 2013 libcloud meeting. Tomaz you mentioned a
>> command line tool for updating the file, is there anything available?
>> The prices for Rackspace are outdated (btw how do you get prices for
>> Rackspace? Manually after checking the page, or through API?). For ec2
>> there a nice tool at https://github.com/erans/ec2instancespricing that
>> could start as a base.
>>
>> A major problem hovwever is that prices are
>> related to image types besides the size, which means that ec2 us-west
>> charges 0.025 for linux, 0.085 for rhel and 0.035 for mswin :(
>>
>>
>> Libcloud does not take this into account and I wonder if this is
>> something scheduled to implement, and how hard would be a refactor.
>>
>>
>> Thanks for sharing any thoughts,
>>
>> Regards,
>>
>> Markos
>>
>
>
>

[dev] Re: libcloud pricing

Posted by Tomaz Muraus <to...@apache.org>.
I've opened a Github pull request with an initial implementation prototype
- https://github.com/apache/libcloud/pull/127.

Feedback is welcome, so if you care about this feature, please visit the
pull request and post your feedback and comments there.

On Sat, Jul 27, 2013 at 3:10 PM, Tomaz Muraus <to...@apache.org> wrote:

> Hi,
>
> I've started to work on it soon after the meetup (
> https://github.com/Kami/libcloud/tree/pricing_file_changes), but I got
> distracted with some other things and never managed to finish it.
>
> The good thing is that is should be fairly easy and straight-forward to
> implement the tool which downloads the latest pricing data from our git
> repository and saved it into ~/libcloud/pricing.json.
>
> As far as getting the prices for Rackspace - like most of the providers,
> they don't have an API so we update those manually.
>
> On Fri, Jul 26, 2013 at 1:19 PM, Markos Gogoulos <mg...@mist.io>wrote:
>
>>
>>
>> Hi all,
>>
>> I'd like to ask if there is any progress regarding
>> pricing, after the June 2013 libcloud meeting. Tomaz you mentioned a
>> command line tool for updating the file, is there anything available?
>> The prices for Rackspace are outdated (btw how do you get prices for
>> Rackspace? Manually after checking the page, or through API?). For ec2
>> there a nice tool at https://github.com/erans/ec2instancespricing that
>> could start as a base.
>>
>> A major problem hovwever is that prices are
>> related to image types besides the size, which means that ec2 us-west
>> charges 0.025 for linux, 0.085 for rhel and 0.035 for mswin :(
>>
>>
>> Libcloud does not take this into account and I wonder if this is
>> something scheduled to implement, and how hard would be a refactor.
>>
>>
>> Thanks for sharing any thoughts,
>>
>> Regards,
>>
>> Markos
>>
>
>
>

Re: libcloud pricing

Posted by Tomaz Muraus <to...@apache.org>.
Hi,

I've started to work on it soon after the meetup (
https://github.com/Kami/libcloud/tree/pricing_file_changes), but I got
distracted with some other things and never managed to finish it.

The good thing is that is should be fairly easy and straight-forward to
implement the tool which downloads the latest pricing data from our git
repository and saved it into ~/libcloud/pricing.json.

As far as getting the prices for Rackspace - like most of the providers,
they don't have an API so we update those manually.

On Fri, Jul 26, 2013 at 1:19 PM, Markos Gogoulos <mg...@mist.io> wrote:

>
>
> Hi all,
>
> I'd like to ask if there is any progress regarding
> pricing, after the June 2013 libcloud meeting. Tomaz you mentioned a
> command line tool for updating the file, is there anything available?
> The prices for Rackspace are outdated (btw how do you get prices for
> Rackspace? Manually after checking the page, or through API?). For ec2
> there a nice tool at https://github.com/erans/ec2instancespricing that
> could start as a base.
>
> A major problem hovwever is that prices are
> related to image types besides the size, which means that ec2 us-west
> charges 0.025 for linux, 0.085 for rhel and 0.035 for mswin :(
>
>
> Libcloud does not take this into account and I wonder if this is
> something scheduled to implement, and how hard would be a refactor.
>
>
> Thanks for sharing any thoughts,
>
> Regards,
>
> Markos
>