Blog

Libcloud 2.4.0 released

We are pleased to announce the release of Libcloud 2.4.0!

The most notable change is Python 3.7 support. There is also a new Scaleway driver, and improvements for many other drivers.

Full change log can be found at http://libcloud.readthedocs.io/en/latest/changelog.html#changes-in-apache-libcloud-2-4-0.

Download

The release can can be downloaded from https://libcloud.apache.org/downloads.html or installed using pip:

pip install apache-libcloud==2.4.0

Upgrading

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

pip install --upgrade apache-libcloud==2.4.0

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 https://libcloud.readthedocs.org/en/latest/upgrade_notes.html

Documentation

Regular and API documentation is available at https://libcloud.readthedocs.org/en/v2.4.0/

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.

Rick van de Loo (vdloo) joins our team

Please help us extend a warm welcome to our newest team member Rick van de Loo!

The Project Management Committee (PMC) for Apache Libcloud has invited Rick van de Loo to join us as a committer and we are pleased to announce that he has accepted.

In the last couple of years Rick has contributed various high quality changes to the project and we are happy to have him on board.

For anyone who would like to know more about Rick here is his short bio:

Rick van de Loo is the lead developer on Hypernode, a highly automated and cloud agnostic hosting platform specialised for Magento built on top of Apache Libcloud. Since Rick started working on Hypernode he has seen it scale from double digits to thousands of servers, along the road orchestrating various high volume cross-provider migrations. His main focus is on platform stability and feature development, of which a large part has been integrating cloud APIs and working around their incompatibilities and unreliable nature.

And in his own words:

Since we started using Libcloud around four years ago the landscape has changed a lot. But even though container-based and serverless architectures have become more prominent, compute is still the cornerstone of cloud. Most of my contributions have been about standardising functionality across different compute providers and implementing new driver methods, mainly related to the AWS, DigitalOcean and OpenStack APIs. As an Apache Libcloud team member I will continue to contribute changes that help us scratch our own itch and encourage other members of the Hypernode team to do the same.

We are happy to have him in our team and we are looking forward to his future participation and contributions.

Libcloud 2.3.0 released

We are pleased to announce the release of Libcloud 2.3.0!

Most notable changes are the dropping of support for Python 2.6 and 3.3, both of which are now unsupported distributions.

There are new drivers for UpCloud, Digital Ocean Spaces, bug fixes and improvements for many other drivers.

Full change log can be found at http://libcloud.readthedocs.io/en/latest/changelog.html#changes-in-apache-libcloud-2-3-0.

Download

The release can can be downloaded from https://libcloud.apache.org/downloads.html or installed using pip:

pip install apache-libcloud==2.3.0

Upgrading

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

pip install --upgrade apache-libcloud==2.3.0

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 https://libcloud.readthedocs.org/en/latest/upgrade_notes.html

Documentation

Regular and API documentation is available at https://libcloud.readthedocs.org/en/v2.3.0/

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.

Libcloud Year in Review 2017

Another year is behind us. Like most of the previous years, this year included a lot of exciting development. This post is going to present some statistics and highlights of the year.

Year in Numbers (recap)

  • 800+ commits
  • 191 opened PRs on Github (159 closed, 32 open at the time of this writing)
  • 86 opened JIRA issues
  • 75+ different contributors
  • 4 releases (3 major ones)

Statistics from Open Hub.

You can also dig into the numbers yourself on Github, Open Hub and Apache Project Information.

Releases

This year we had 4 releases (2.0.0, 2.1.0, 2.2.0, 2.2.1). Out of that, three major ones.

Libcloud 2.0.0 which was released in April represented a big milestone. We finally moved away from our home grown HTTP abstraction layer built on top of Python's httplib library to the popular requests library.

Back in the day when the project started, requests library didn't exist yet so we needed to build a lot of the functionality which is now provided by requests ourselves. Move to requests means that we now have a lot less code to maintain and we can focus our efforts on the actual drivers which is core to Libcloud and where the project provides value.

To give you an idea how much effort it took - the ground work for that change started back in 2016 (https://libcloud.apache.org/blog/2016/04/06/requests-support.html, https://github.com/apache/libcloud/pull/728), but it took a lot more testing and work to get it stable enough so we were finally able to include it as part of the stable 2.0.0 release (and before that, we also released a couple of release candidates so users could test and verify that their Libcloud related code still works as expected without any regressions).

Special thanks to Anthony Shaw for leading this effort and not giving up (the change itself involved touching a lot of code and updating test cases for most of the drivers which resulted in a lot of not so pleasant work and merge conflicts).

Community

The community continued to grow and we have received contributions from more than 75 different contributors. Keep in mind that this number only includes people who contributed a code change which has been merged into trunk. The actual number is quite a bit higher (code who didn't get merged, people who reported a bug or didn't include a code change, etc).

We have also added one new committer - Quentin Pradet.

Ecosystem

In addition to various proprietary and private code bases, Libcloud continues to be used as an important part by various open-source projects and libraries.

Most notable ones include SaltStack, StackStorm and Ansible.

Conclusion

I would like to take this opportunity to thank everyone who has contributed to the project in one form or another. No matter how small or involved, your contribution helped project grow and push through another successful year.

Again, thank you, happy and successful 2018 and see you soon.

Libcloud 2.2.1 released

We are pleased to announce the release of Libcloud 2.2.1!

This is a first patch release in the 2.2.x series and as such, it includes some bug fixes and improvements.

The most important one of them fixes an installation of Libcloud 2.2.0 failing on some operating-system and file-system combinations (e.g. ecryptfs layered on top of ext3/4) which don't support file names longer than 143 characters.

In addition to that, it also includes performance improvement for the deploy functionality available to the compute drivers. Now the deploy scripts which produce a lot of output should finish a lot faster.

Full change log can be found at http://libcloud.readthedocs.io/en/latest/changelog.html#changes-in-apache-libcloud-2-2-1.

Download

The release can can be downloaded from https://libcloud.apache.org/downloads.html or installed using pip:

pip install apache-libcloud==2.2.1

Upgrading

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

pip install --upgrade apache-libcloud==2.2.1

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 https://libcloud.readthedocs.org/en/latest/upgrade_notes.html

Documentation

Regular and API documentation is available at https://libcloud.readthedocs.org/en/v2.2.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 everyone who contributed and made this release possible! Full list of people who contributed to this release can be found in the CHANGES file.