[
https://issues.apache.org/jira/browse/LIBCLOUD-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375891#comment-14375891
]
Eran Raichstein commented on LIBCLOUD-444:
------------------------------------------
Hi Brian,
We uploaded to github an extended version of LibCloud (Link:
https://github.com/Cloud-Elasticity-Services/as-libcloud) that provides basic
elasticity / auto-scaling capabilities. The code currently supports only
SoftLayer and Amazon and requires additional work to provide more elasticity
features and to support more cloud providers. Once the code will be more mature
we plan to work with Tomaz on up-stream to LibCloud.
> Support scaling APIs
> --------------------
>
> Key: LIBCLOUD-444
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-444
> Project: Libcloud
> Issue Type: New Feature
> Components: Core
> Reporter: Brian Curtin
> Labels: features
>
> I propose to kick off a new package in the libcloud namespace, e.g.,
> libcloud.scaling, to support the various automatic scaling APIs that some
> providers are offering.
> * Amazon has had Auto Scaling available for some time now.
> * Rackspace released its Autoscale product to general availability today.
> * Azure supports Autoscale via its Management API.
> * I've found some Google documentation around autoscaling, but it seems more
> tied to AppEngine than GCE, so maybe not applicable here.
> At least Amazon and Rackspace's offerings are built on or make use of their
> CloudWatch and Cloud Monitoring products, respectively, so we'd probably want
> to create a package, e.g., libcloud.monitoring, as well. Azure
> I have to imagine the first step is getting to understand the various APIs
> and boiling down a common set of goals and functionality. Before going down
> that path, is there anything I should know?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
