Wrt item 1, we wouldn't need to add it as a dependency, you can just use the requests library to get the token for oauth. That's all they are doing. And their SDK looks pretty incomplete so it wouldn't be a good dependency. I'm happy to do that task, I've got lots of accounts on azure to test on and plenty of VMs. It's probably time I contributed to another driver! Wrt the backup, I'll send a comparison of the features in azure, Rackspace and dimension data to help with a base class. I'd got that somewhere anyway from prior research building our own service. I would imagine some of the other providers have also. Ant
Sent from Outlook On Fri, Oct 23, 2015 at 2:34 PM -0700, "Tomaz Muraus" <[email protected]> wrote: All good stuff. 1. As far as depending on the 3rd party libraries / packages goes - in the past we avoided that because it's harder to test it and make sure it works under all the Python versions we support. 2. Introducing a new API usually requires more work which includes a proposal to the mailing list and a prototype / initial implementation with at least 2 drivers (3 are better). The reason for at least 2 drivers is to make sure that the base API and implementation is indeed generic (as much as possible) and not biased towards a single provider... 3. Yeah, some cleaning is in order. Would be good to check which providers are now dead and remove those drivers (HP just announced sun set of their public cloud offering so in a couple of months we can get rid of that driver as well). On Fri, Oct 23, 2015 at 1:50 AM, anthony shaw wrote: > WRT item 1) > > Microsoft have already implemented this approach in the azure-python-sdk > pypi. > > > https://azure-sdk-for-python.readthedocs.org/en/latest/resourcemanagementauthentication.html > > > Ant > > On Fri, Oct 23, 2015 at 10:37 AM, anthony shaw > wrote: > > > I had some suggestions for the next version, > > > > > > 1) Azure Driver: > > * Only supports the 'old' way of authenticating, continue this method > > * Offer the new Azure AD/OAuth method as a secondary option for > > instantiating a driver - > > https://msdn.microsoft.com/en-us/library/azure/ee460782.aspx > > This is Microsoft's recommended approach and it's probably a matter of > > time until they stop supporting certificates (according to an 'insider'). > > > > 2) A Backup Driver type: > > > > I'm looking at adding support for the DD Cloud Backup service and it > > doesn't really fall under the compute functionality. There are a few > other > > providers offering very similar functionality on the market > > > > Azure > > Rackspace > > Dimension Data > > > > https://developer.rackspace.com/docs/cloud-backup/v1/developer-guide/ > > Azure > > https://azure.microsoft.com/en-us/services/backup/ > > > > This would be very similar to the DNS driver type. > > > > 3) Removing the opsource driver, this is superseded by the Dimension Data > > driver and has been for a while now. > > > > Ant > > >
