Blog

2012 in retrospect and a Happy New Year from the Libcloud team

Dear users, developers and team members!

2012 is slowly coming to an end and Libcloud team wishes everyone a happy and successful new year 2013!

2012 has been another great year for us and we have surpassed 2011 in pretty much every aspect.

Here is a short list of things which have been accomplished and important events which have happened in 2012:

  • One new committer Ilgiz Islamgulov (ilgiz) has joined the team.
  • We have another new commiter joining our team soon (Mahendra M). Currently he is undergoing a process of submitting his ICLA.
  • 134 new JIRA issues have been opened (total of 271). Out of those 134 issues, 111 are now marked as 'resolved'.
  • SVN repository has had a total of 320 commit. More than 50% of those commits were patches from external contributors.
  • We had our first Google Summer of Code student which worked on a project named "Libcloud REST" (https://github.com/islamgulov/libcloud.rest). The goal of the project is to expose Libcloud functionality over HTTP.
  • Tomaz gave a talk titled "Avoiding Vendor Lock-In Using Apache Libcloud" at CloudOpen 2012 in San Diego
  • We now finally have some more user friendly documentation and examples on the website - http://libcloud.apache.org/docs/
  • We held a first in person meetup at the Rackspace San Francisco office in the beginning of the year (http://libcloudmeetup.eventbrite.com/)
  • We had a total of 7 releases (0.8.0, 0.9.1, 0.10.1, 0.11.0, 0.11.1, 0.11.3, 0.11.4) and over 70.000 downloads / installs on PyPi ( http://pypi.python.org/pypi/apache-libcloud/)
  • Github mirror has been starred by 266 users ( https://github.com/apache/libcloud)

Thanks again to everyone for their work and contributions and lets make 2013 even better :)

I will post those numbers in a more machine readable format (JSON) in the next couple of weeks. This way it will be easier for us to track those metrics on a year over year basis.

Numbers retrieved on: 2012-12-25. Sources for those numbers: JIRA, Libcloud website, PyPi, Ohloh.net, Google Analytics

Source: mailing list post.

Libcloud 0.11.4 released

We are pleased to announce the release of Libcloud 0.11.4!

This release is a bug fix release and contains no new features.

Next release which will contain new features and some backward incompatible changes will happen in the 0.12.x series in the next couple of weeks.

Bug fixes:

  • Fix some of tests failures which happened in Python 3.3 due to randomized dictionary ordering.
  • Fix a bug where a numeric instead of a string value was used for the content-length header in VCloud driver.
  • Don't ignore exforceservice_region argument in the CloudFiles driver.
  • Fix a bug which caused the connection to not be closed when using Python 2.6 and calling get_object on an object which doesn't exist in the S3 driver.
  • Update 'if type' checks in the update_record methods to behave correctly if users passes in RecordType.A with a value of 0 - if type is not None.

Full change log can be found at https://svn.apache.org/viewvc/libcloud/tags/0.11.4/CHANGES?revision=r1411030&view=markup.

Download

Libcloud 0.11.4 can be downloaded from http://libcloud.apache.org/downloads.html or installed using pip:

pip install apache-libcloud

It is possible that the file hasn't been synced to all the mirrors yet. If this is the case, please use the main Apache mirror - http://www.apache.org/dist/libcloud.

Upgrading

If you have installed Libcloud using pip you can also use it to upgrade it:

pip install --upgrade apache-libcloud

Upgrade notes

A page which describes backward incompatible or semi-incompatible changes and how to preserve the old behavior when this is possible can be found at http://libcloud.apache.org/upgrade-notes.html.

Documentation

API documentation can be found at http://libcloud.apache.org/apidocs/0.11.4/.

Bugs / Issues

If you find any bug or issue, please report it on our issue tracker < https://issues.apache.org/jira/browse/LIBCLOUD>. Don't forget to attach an example and / or test which reproduces your problem.

Thanks

Thanks to everyone who contributed and made this release possible! Full list of people who contributed to this release can be found in the CHANGES file https://svn.apache.org/viewvc/libcloud/tags/0.11.3/CHANGES?revision=r1388947&view=markup.

Source: release announcement.

New committer Ilgiz Islamgulov joins our team

The Project Management Committee (PMC) for Apache Libcloud has asked Ilgiz Islamgulov to become a committer and we are pleased to announce that they have accepted.

Ilgiz worked on the Libcloud REST GSoC project (http://libcloud.apache.org/gsoc-2012.html) this summer and he has made a great progress on it.

Giving him commit access will allow him to more directly contribute to the project and work on integrating Libcloud REST into main line.

Everyone, please help me welcome him to the team :)

Source: mailing list.

Libcloud 0.11.3 released

We are pleased to announce the release of Libcloud 0.11.3!

Release highlights

Compute

  • Add new Rackspace Nova driver for Chicago (ORD) location
  • Add new methods for managing storage volumes and other extenstion methods to the IBM SCE driver.
  • Allow user to pass 'timeout' argument to the 'deploy_node' method

Bug fixes

  • Fix a bug with the Libcloud SSL verification code. Code was too strict and didn't allow "-" character in the sub-domain when using a wildcard certificate.

Full change log can be found at https://svn.apache.org/viewvc/libcloud/tags/0.11.3/CHANGES?revision=r1388947&view=markup.

Download

Libcloud 0.11.3 can be downloaded from http://libcloud.apache.org/downloads.html or installed using pip:

pip install apache-libcloud

It is possible that the file hasn't been synced to all the mirrors yet. If this is the case, please use the main Apache mirror - http://www.apache.org/dist/libcloud.

Upgrading

If you have installed Libcloud using pip you can also use it to upgrade it:

pip install --upgrade apache-libcloud

Upgrade notes

A page which describes backward incompatible or semi-incompatible changes and how to preserve the old behavior when this is possible can be found at http://libcloud.apache.org/upgrade-notes.html.

Documentation

API documentation can be found at http://libcloud.apache.org/apidocs/0.11.3/.

Bugs / Issues

If you find any bug or issue, please report it on our issue tracker https://issues.apache.org/jira/browse/LIBCLOUD. Don't forget to attach an example and / ortest which reproduces your problem.

Thanks

Thanks to everyone who contributed and made this release possible! Full list of people who contributed to this release can be found in the CHANGES file https://svn.apache.org/viewvc/libcloud/tags/0.11.3/CHANGES?revision=r1388947&view=markup.

Source: release announcement.

Libcloud 0.11.1 released

This release fixes a possible SSL man-in-the-middle vulnerability inside the code which performs the SSL certificate validation. For more information about the vulnerability, please see the "Security" page - http://libcloud.apache.org/security.html.

Everyone using an older version is strongly encouraged to upgrade to this release.

Download

Libcloud 0.11.1 can be downloaded from http://libcloud.apache.org/downloads.html or installed using pip:

pip install apache-libcloud

It is possible that the file hasn't been synced to all the mirrors yet. If this is the case, please use the main Apache mirror - http://www.apache.org/dist/libcloud.

Upgrading

If you have installed Libcloud using pip you can also use it to upgrade it:

pip install --upgrade apache-libcloud

Upgrade notes

A page which describes backward incompatible or semi-incompatible changes and how to preserve the old behavior when this is possible can be found at http://libcloud.apache.org/upgrade-notes.html.

Documentation

API documentation can be found at http://libcloud.apache.org/apidocs/0.11.1/.

Bugs / Issues

If you find any bug or issue, please report it on our issue tracker https://issues.apache.org/jira/browse/LIBCLOUD. Don't forget to attach an example and / or test which reproduces your problem.

Thanks

Thanks to the researchers from the University of Texas at Austin (Martin Georgiev, Suman Jana and Vitaly Shmatikov) who discovered this vulnerability.

Source: release announcement.