# Apache Libcloud looks interesting

**URL:** <https://forum.ansible.com/t/apache-libcloud-looks-interesting/14524>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [February 7, 2014, 10:35pm UTC](https://forum.ansible.com/t/apache-libcloud-looks-interesting/14524 "2014-02-07T22:35:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [February 7, 2014, 10:35pm UTC](https://forum.ansible.com/t/apache-libcloud-looks-interesting/14524/1 "2014-02-07T22:35:53Z")

</div>

libcloud has been around for quite some time now. Several modules in ansible use it (The Google Compute Engine modules).

For a unified API it is pretty nice, but it often lacks full functionality for the APIs usually due to maintaining consistence between providers.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [February 8, 2014, 8:26pm UTC](https://forum.ansible.com/t/apache-libcloud-looks-interesting/14524/2 "2014-02-08T20:26:32Z")

</div>

Yep.

Our policy is to use the native bindings for a particular provider whenever available to expose the maximum number of knobs and switches.

libcloud works when something else better doesn’t exist in Python, or if that’s the primary way the community around that particular provider does things.