Blog

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.

All of our community for their ongoing support and contributions...

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.

Libcloud 2.2.0 released

We are pleased to announce the release of Libcloud 2.2.0!

The release includes a new improvements to Azure ARM support, fixes for Route 53 users, and support for TLS authenticated Docker drivers.

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

All of our community for their ongoing support and contributions...

Download

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

pip install apache-libcloud==2.2.0

Upgrading

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

pip install --upgrade apache-libcloud==2.2.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.2.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 2.1.0 released

We are pleased to announce the release of Libcloud 2.1.0!

The release includes a new driver for Google Container Engine (GKE), upgrades to the OpenStack driver to support keystone v3 and Nova v2.x

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

All of our community for their ongoing support and contributions...

Download

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

pip install apache-libcloud==2.1.0

Upgrading

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

pip install --upgrade apache-libcloud==2.1.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.1.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 2.0.0 released

We are pleased to announce the release of Libcloud 2.0.0.

This major release brings many new features, improvements, bug-fixes, and drivers.

Release highlights

  • Apache Libcloud 2.0 series replaces the use of Python httplib with a hard dependency on the requests package. Users no longer have to specific Certificate Authority bundles when using Apache Libcloud
  • 10% performance improvement through the use of HTTP sessions
  • Support for buffered IO streams for storage drivers
  • Support for Python 3.6, deprecation of Python 3.2
  • 3 new drivers - OnApp Compute, OnApp DNS, 1&1 Compute
  • Lots of improvements to our Azure ARM support
  • Continuing udates to the Amazon drivers

A detailed description of the 2.0 HTTP API is documented here

Compute API Changes

  • Outscale SAS doc improvements and logo update

OnApp Changes

  • Add list images support for OnApp driver
  • Add keypair management to OnApp driver

Amazon EC2 Changes

  • Add r4 instance types for AWS
  • Add support for AWS eu-west-2 and ca-central-1 regions
  • Add P2 GPU instance types
  • Add method to modify snapshot attribute for EC2
  • Add ENA support for EC2 compute images
  • Add support for forcing detachment of EBS volumes to EC2 driver
  • Add support for ModifyVolume and DescribeVolumesModifications
  • Added Import Snapshot and Describe Import Snapshot to EC2 compute driver
  • Add missing regions in AWS storage and compute drivers
  • Add SR-IOV net support to images in EC2 compute driver
  • Fix - update t2.small image size from 11 CPU to 1
  • Added Billing Product for image in EC2 compute driver

Linode changes

  • Add start, stop instance methods and fix incorrect state TERMINATED to STOPPED

Azure ARM changes

  • Fix typeerror on exlistnics
  • Add support for Azure Cloud Environments as well as Locations
  • Fix string representation of the VhdImage type and fix listing of Public IP addresses
  • Add network security groups to azure ARM
  • Add the ability to list resource groups
  • Fix Azure ARM driver condition for exlistpublishers where location is specified

Google Cloud changes

  • Allow delete instances from managed group
  • Allow preemptible instances to be created
  • Remove validation checks for guestOsFeatures

Alibaba Aliyun changes

  • Add aliyun ecs instance join leave security group
  • Fix Aliyun ECS, Load balancer and storage adapters when using unicode UTF-8 characters in the names of resources

DigitalOcean changes

  • Add price_monthly extra param to digitalocean sizes

VMWare vSphere changes

  • Fix issue with authentication methods crashing

Storage

  • Reintroduce S3 multipart upload support with signature v4

DNS

Minor changes

Common

  • Added an integration test API and a test suite for validating functionality without mocking any libcloud subsystems
  • Change Cloudscale to cloudscale.ch.

Bug Fixes

Compute

2.0.0

  • Fix OpenStack drivers not correctly setting URLs when used with identity API, would default to 127.0.0.1 and service catalog URLs were not adhered to.

  • Fix Aliyun ECS, Load balancer and storage adapters when using unicode UTF-8 characters in the names of resources in 2.0.0rc2 < it would fail as a MalformedResponseError, Python 2.7 element tree was raising a unicode error

  • Refactor the test classes to use the full libcloud.http and libcloud.common.base modules, with Connection, Response all used with requestsmock. This increases our test coverages and catches bugs in drivers' custom parsebody and auth modules

  • Rename libcloud.httplib_ssl to libcloud.http now that we don't use httplib

2.0.0rc2

  • Fix Public IP not assigned when creating NIC on Azure ARM
  • Fix a bug in profitbricks driver where listing snapshots would request a malformed URL
  • Fix LIBCLOUD-806 bug where vsphere driver cannot be instantiated
  • [google compute] Improve performance of list nodes by caching volume information.

Full change log can be found at here.

Special thank you

I would like to wish a special thank you to all of our community contributors for their ongoing support to the project.

  • Tinu Cleatus for the OnApp driver
  • Alex Misstear for the EC2 improvements
  • Jie Ren for the Aliyun improvements
  • Francisco Ros for the DigitalOcean improvements
  • Peter Amstutz and Joseph Hall for the Azure ARM API updates
  • All of our community for their ongoing support and contributions...

Download

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

pip install apache-libcloud==2.0.0

Upgrading

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

pip install --upgrade apache-libcloud==2.0.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/latest/

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.