I don't know about the other clouds, but as far as OpenStack is concerned, the shade library exists to handle all of the various differences between OpenStack providers (it turns out to be pretty complex in spots). This is not something libcloud handles. As one of the maintainers of those modules, I don't think incorporating libcloud into the OpenStack modules makes sense at this time.
-Dave On Tuesday, November 1, 2016 at 9:14:55 AM UTC-4, Samuel Marks wrote: > > Greetings Ansible! - I like your philosophy, although enjoy reinventing > the wheel also ;) as you can see from my [open-source] Fabric-centric DSL. > > However I don't like being one of [the only?] that supports so many > clouds. So I'm thinking about contributing to Ansible, but don't know if > you'd be interested. > > FYI: Apache Libcloud is an open-source Python library supporting over 50 > different cloud providers. Ansible lists 9 > <https://github.com/ansible/ansible-modules-core/tree/679a0ae5e9bd53aa0fbe37ea833d7074784ffffd/cloud> > . > > I note you're aware > <https://groups.google.com/d/topic/ansible-project/B6M3qYZ5-Oo> of it, > even utilising it in your Google Compute Engine (GCE) Ansible cloud module. > > Without touching your existing cloud modules, if I prepared a PR that took > a catch-all fallback approach would you be interested in accepting? > - So if it's not AWS, GCE, Azure, Digital Ocean, Docker, linode, > OpenStack, Rackspace or vSphere; then check libcloud. > > If yes, then I should get some time over Christmas to make the contribution > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/bc64cd6a-40d3-4532-b3a9-a86827b9feb7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
