README.rst 8.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177
  1. CloudBridge provides a simple layer of abstraction over different
  2. Infrastructure-as-a-Service cloud providers, reducing or eliminating the need
  3. to write conditional code for each cloud.
  4. .. image:: https://coveralls.io/repos/CloudVE/cloudbridge/badge.svg?branch=master&service=github
  5. :target: https://coveralls.io/github/CloudVE/cloudbridge?branch=master
  6. :alt: Code Coverage
  7. .. image:: https://img.shields.io/pypi/v/cloudbridge.svg
  8. :target: https://pypi.python.org/pypi/cloudbridge/
  9. :alt: latest version available on PyPI
  10. .. image:: https://readthedocs.org/projects/cloudbridge/badge/?version=latest
  11. :target: http://cloudbridge.readthedocs.org/en/latest/?badge=latest
  12. :alt: Documentation Status
  13. .. image:: https://badge.waffle.io/CloudVE/cloudbridge.png?label=in%20progress&title=In%20Progress
  14. :target: https://waffle.io/CloudVE/cloudbridge?utm_source=badge
  15. :alt: 'Waffle.io - Issues in progress'
  16. .. |aws-py27| image:: https://travis-matrix-badges.herokuapp.com/repos/CloudVE/cloudbridge/branches/master/1
  17. :target: https://travis-ci.org/CloudVE/cloudbridge
  18. .. |aws-py36| image:: https://travis-matrix-badges.herokuapp.com/repos/CloudVE/cloudbridge/branches/master/4
  19. :target: https://travis-ci.org/CloudVE/cloudbridge
  20. .. |aws-pypy| image:: https://travis-matrix-badges.herokuapp.com/repos/CloudVE/cloudbridge/branches/master/7
  21. :target: https://travis-ci.org/CloudVE/cloudbridge
  22. .. |os-py27| image:: https://travis-matrix-badges.herokuapp.com/repos/CloudVE/cloudbridge/branches/master/3
  23. :target: https://travis-ci.org/CloudVE/cloudbridge
  24. .. |os-py36| image:: https://travis-matrix-badges.herokuapp.com/repos/CloudVE/cloudbridge/branches/master/6
  25. :target: https://travis-ci.org/CloudVE/cloudbridge
  26. .. |os-pypy| image:: https://travis-matrix-badges.herokuapp.com/repos/CloudVE/cloudbridge/branches/master/9
  27. :target: https://travis-ci.org/CloudVE/cloudbridge
  28. .. |azure-py27| image:: https://travis-matrix-badges.herokuapp.com/repos/CloudVE/cloudbridge/branches/master/2
  29. :target: https://travis-ci.org/CloudVE/cloudbridge/branches
  30. .. |azure-py36| image:: https://travis-matrix-badges.herokuapp.com/repos/CloudVE/cloudbridge/branches/master/5
  31. :target: https://travis-ci.org/CloudVE/cloudbridge/branches
  32. .. |azure-pypy| image:: https://travis-matrix-badges.herokuapp.com/repos/CloudVE/cloudbridge/branches/master/8
  33. :target: https://travis-ci.org/CloudVE/cloudbridge/branches
  34. .. |gce-py27| image:: https://travis-matrix-badges.herokuapp.com/repos/CloudVE/cloudbridge/branches/gce/3
  35. :target: https://travis-ci.org/CloudVE/cloudbridge/branches
  36. .. |gce-py36| image:: https://travis-matrix-badges.herokuapp.com/repos/CloudVE/cloudbridge/branches/gce/6
  37. :target: https://travis-ci.org/CloudVE/cloudbridge/branches
  38. .. |gce-pypy| image:: https://travis-matrix-badges.herokuapp.com/repos/CloudVE/cloudbridge/branches/gce/9
  39. :target: https://travis-ci.org/CloudVE/cloudbridge/branches
  40. Build Status Tests
  41. ~~~~~~~~~~~~~~~~~~
  42. +--------------------------+--------------+--------------+--------------+
  43. | **Provider/Environment** | py27 | py36 | pypy |
  44. +--------------------------+--------------+--------------+--------------+
  45. | **AWS** | |aws-py27| | |aws-py36| | |aws-pypy| |
  46. +--------------------------+--------------+--------------+--------------+
  47. | **OpenStack** | |os-py27| | |os-py36| | |os-pypy| |
  48. +--------------------------+--------------+--------------+--------------+
  49. | **Azure** | |azure-py27| | |azure-py36| | |azure-py36| |
  50. +--------------------------+--------------+--------------+--------------+
  51. | **GCE (alpha)** | |gce-py27| | |gce-py36| | |gce-pypy| |
  52. +--------------------------+--------------+--------------+--------------+
  53. Installation
  54. ~~~~~~~~~~~~
  55. Install the latest release from PyPi:
  56. .. code-block:: shell
  57. pip install cloudbridge
  58. For other installation options, see the `installation page`_ in
  59. the documentation.
  60. Usage example
  61. ~~~~~~~~~~~~~
  62. To `get started`_ with CloudBridge, export your cloud access credentials
  63. (e.g., AWS_ACCESS_KEY and AWS_SECRET_KEY for your AWS credentials) and start
  64. exploring the API:
  65. .. code-block:: python
  66. from cloudbridge.cloud.factory import CloudProviderFactory, ProviderList
  67. provider = CloudProviderFactory().create_provider(ProviderList.AWS, {})
  68. print(provider.security.key_pairs.list())
  69. The exact same command (as well as any other CloudBridge method) will run with
  70. any of the supported providers: ``ProviderList.[AWS | AZURE | OPENSTACK]``!
  71. Citation
  72. ~~~~~~~~
  73. N. Goonasekera, A. Lonie, J. Taylor, and E. Afgan,
  74. "CloudBridge: a Simple Cross-Cloud Python Library,"
  75. presented at the Proceedings of the XSEDE16 Conference on Diversity, Big Data, and Science at Scale, Miami, USA, 2016.
  76. DOI: http://dx.doi.org/10.1145/2949550.2949648
  77. Documentation
  78. ~~~~~~~~~~~~~
  79. Documentation can be found at https://cloudbridge.readthedocs.org.
  80. Quick Reference
  81. ~~~~~~~~~~~~~~~
  82. The following object graph shows how to access various provider services, and the resource
  83. that they return.
  84. .. image:: http://cloudbridge.readthedocs.org/en/latest/_images/object_relationships_detailed.svg
  85. :target: http://cloudbridge.readthedocs.org/en/latest/?badge=latest#quick-reference
  86. :alt: CloudBridge Quick Reference
  87. Design Goals
  88. ~~~~~~~~~~~~
  89. 1. Create a cloud abstraction layer which minimises or eliminates the need for
  90. cloud specific special casing (i.e., Not require clients to write
  91. ``if EC2 do x else if OPENSTACK do y``.)
  92. 2. Have a suite of conformance tests which are comprehensive enough that goal
  93. 1 can be achieved. This would also mean that clients need not manually test
  94. against each provider to make sure their application is compatible.
  95. 3. Opt for a minimum set of features that a cloud provider will support,
  96. instead of a lowest common denominator approach. This means that reasonably
  97. mature clouds like Amazon and OpenStack are used as the benchmark against
  98. which functionality & features are determined. Therefore, there is a
  99. definite expectation that the cloud infrastructure will support a compute
  100. service with support for images and snapshots and various machine sizes.
  101. The cloud infrastructure will very likely support block storage, although
  102. this is currently optional. It may optionally support object storage.
  103. 4. Make the CloudBridge layer as thin as possible without compromising goal 1.
  104. By wrapping the cloud provider's native SDK and doing the minimal work
  105. necessary to adapt the interface, we can achieve greater development speed
  106. and reliability since the native provider SDK is most likely to have both
  107. properties.
  108. Contributing
  109. ~~~~~~~~~~~~
  110. Community contributions for any part of the project are welcome. If you have
  111. a completely new idea or would like to bounce your idea before moving forward
  112. with the implementation, feel free to create an issue to start a discussion.
  113. Contributions should come in the form of a pull request. We strive for 100% test
  114. coverage so code will only be accepted if it comes with appropriate tests and it
  115. does not break existing functionality. Further, the code needs to be well
  116. documented and all methods have docstrings. We are largely adhering to the
  117. `PEP8 style guide`_ with 80 character lines, 4-space indentation (spaces
  118. instead of tabs), explicit, one-per-line imports among others. Please keep the
  119. style consistent with the rest of the project.
  120. Conceptually, the library is laid out such that there is a factory used to
  121. create a reference to a cloud provider. Each provider offers a set of services
  122. and resources. Services typically perform actions while resources offer
  123. information (and can act on itself, when appropriate). The structure of each
  124. object is defined via an abstract interface (see
  125. ``cloudbridge/providers/interfaces``) and any object should implement the
  126. defined interface. If adding a completely new provider, take a look at the
  127. `provider development page`_ in the documentation.
  128. .. _`installation page`: http://cloudbridge.readthedocs.org/en/
  129. latest/topics/install.html
  130. .. _`get started`: http://cloudbridge.readthedocs.org/en/latest/
  131. getting_started.html
  132. .. _`PEP8 style guide`: https://www.python.org/dev/peps/pep-0008/
  133. .. _`provider development page`: http://cloudbridge.readthedocs.org/
  134. en/latest/
  135. topics/provider_development.html