An interesting thing regarding something like a common scale set API, would it be a separate API or more like a parameter in “builder” — for instance if creating more than one VM?
I’m planning on looking at the Rackspace implementation of this and help Julio flesh things out. -jim On September 1, 2017 at 11:24:15 AM, Andrew Gaul (g...@apache.org) wrote: Features start at the provider level and percolate into the portable abstraction when enough providers support them. We generally use a "rule of three" to ensure that the abstraction exposes the correct feature set. jclouds is a community project and does not have a road map like corporate-sponsored projects. Please do contribute the Azure provider component which is a step towards the abstraction. Community projects need community contributions! On Fri, Aug 25, 2017 at 02:15:08PM +0000, Julio Colon wrote: > Hi, > > I am extending the Azure provider in jclouds to include Azure Virtual Machine Scale Sets. There are other providers (e.g.Rackspace) that are providing this feature at the provider level (e.g. Rackspace AutoScaleAPI), but I see no documentation at the abstraction layer (i.e. like ComputeServiceContext) for cloud auto scale services. Is it possible to share documentation on this topic? Is it on the roadmap? Should it stay at the provider level? > > > Looking forward to hear from you, > > Julio A. Colon > Sr. Software Development Engineer > Commercial Software Engineering > Microsoft Corporation > -- Andrew Gaul http://gaul.org/
