libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject git commit: docs: Add a note about the extension methods to the FAQ.
Date Mon, 12 Aug 2013 20:55:50 GMT
Updated Branches:
  refs/heads/trunk 4750c7fab -> d21c63151

docs: Add a note about the extension methods to the FAQ.


Branch: refs/heads/trunk
Commit: d21c631519720ee168de75e618a259c6653d1471
Parents: 4750c7f
Author: Tomaz Muraus <>
Authored: Mon Aug 12 22:55:27 2013 +0200
Committer: Tomaz Muraus <>
Committed: Mon Aug 12 22:55:27 2013 +0200

 docs/faq.rst | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
diff --git a/docs/faq.rst b/docs/faq.rst
index 09b6c37..ba5f898 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -11,6 +11,25 @@ that you can't manage block storage independent of the compute API.
 This also makes sense because in most cases you are only interested in attaching
 or detaching volumes from and to the compute nodes.
+What are the extension methods?
+Libcloud acts as a lowest common denominator and exposes a unified base API
+which allows you to work with many different cloud providers through a single
+code base.
+Being a lowest common denominator by definition means that not all of the
+functionality offered by different cloud service providers is available
+through a base API.
+Libcloud solves this problem and allows user to access provider specific
+functionality through so called extension methods. Extension methods are
+all the methods which are prefixed with the ``ex_``.
+Extension methods are there for your convenience, but you should be careful
+when you use them because they make switching or working with multiple
+providers harder.
 I want do add a new provider driver what should I do?

View raw message