Added: libcloud/site/trunk/source/_site/blog/archives/2015/02/index.html URL: http://svn.apache.org/viewvc/libcloud/site/trunk/source/_site/blog/archives/2015/02/index.html?rev=1749451&view=auto ============================================================================== --- libcloud/site/trunk/source/_site/blog/archives/2015/02/index.html (added) +++ libcloud/site/trunk/source/_site/blog/archives/2015/02/index.html Tue Jun 21 06:39:51 2016 @@ -0,0 +1,228 @@ + + + + + + + + + + + + + + + + + + Archive: 2015 » February | Apache Libcloud + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + +
+ +

Libcloud 0.17.0 released

+ + + + + + + +
+

We are pleased to announce the release of Libcloud 0.17.0.

+ +

This is a first release in the 0.17 series which means it brings many +new features, improvements and bug-fixes.

+ +

Release highlights

+ + + +

Full change log can be found at here.

+ +

Download

+ +

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

+ +
+pip install apache-libcloud==0.17.0
+
+ +

Upgrading

+ +

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

+ +
+pip install --upgrade apache-libcloud==0.17.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/v0.17.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.

+ +
+ + +
+ + + + + + + +
+ + + +
+ + + + + + + + + + + Added: libcloud/site/trunk/source/_site/blog/archives/2015/03/index.html URL: http://svn.apache.org/viewvc/libcloud/site/trunk/source/_site/blog/archives/2015/03/index.html?rev=1749451&view=auto ============================================================================== --- libcloud/site/trunk/source/_site/blog/archives/2015/03/index.html (added) +++ libcloud/site/trunk/source/_site/blog/archives/2015/03/index.html Tue Jun 21 06:39:51 2016 @@ -0,0 +1,182 @@ + + + + + + + + + + + + + + + + + + Archive: 2015 » March | Apache Libcloud + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + +
+ +

Allard Hoeve (allard) joins our team

+ + + + + + + +
+

Please help us extend a warm welcome to our newest team member Allard +Hoeve!

+ +

The Project Management Committee (PMC) for Apache Libcloud has asked Allard +Hoeve to join us as a committer and we are pleased to announce that he has +accepted.

+ +

Allard has joined the community just recently, but he has already contributed +some high quality changes and proposals.

+ +

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

+ +
+ + +
+ + + + + + + +
+ + + +
+ + + + + + + + + + + Added: libcloud/site/trunk/source/_site/blog/archives/2015/08/index.html URL: http://svn.apache.org/viewvc/libcloud/site/trunk/source/_site/blog/archives/2015/08/index.html?rev=1749451&view=auto ============================================================================== --- libcloud/site/trunk/source/_site/blog/archives/2015/08/index.html (added) +++ libcloud/site/trunk/source/_site/blog/archives/2015/08/index.html Tue Jun 21 06:39:51 2016 @@ -0,0 +1,236 @@ + + + + + + + + + + + + + + + + + + Archive: 2015 » August | Apache Libcloud + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + +
+ +

Libcloud 0.18.0 released

+ + + + + + + +
+

We are pleased to announce the release of Libcloud 0.18.0.

+ +

This is a first release in the 0.18 series which means it brings many new +features, improvements and bug-fixes.

+ +

Release highlights

+ + + +

Full change log can be found at here.

+ +

Download

+ +

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

+ +
+pip install apache-libcloud==0.18.0
+
+ +

Upgrading

+ +

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

+ +
+pip install --upgrade apache-libcloud==0.18.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/v0.18.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.

+ +
+ + +
+ + + + + + + +
+ + + +
+ + + + + + + + + + + Added: libcloud/site/trunk/source/_site/blog/archives/2015/10/index.html URL: http://svn.apache.org/viewvc/libcloud/site/trunk/source/_site/blog/archives/2015/10/index.html?rev=1749451&view=auto ============================================================================== --- libcloud/site/trunk/source/_site/blog/archives/2015/10/index.html (added) +++ libcloud/site/trunk/source/_site/blog/archives/2015/10/index.html Tue Jun 21 06:39:51 2016 @@ -0,0 +1,285 @@ + + + + + + + + + + + + + + + + + + Archive: 2015 » October | Apache Libcloud + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + +
+ +

Libcloud 0.19.0 released

+ + + + + + + +
+

We are pleased to announce the release of Libcloud 0.19.0.

+ +

This is a first release in the 0.19 series which means it brings many new +features, improvements, bug-fixes, and DNS drivers.

+ +

Release highlights

+ + + +

Full change log can be found at here.

+ +

Download

+ +

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

+ +
+pip install apache-libcloud==0.19.0
+
+ +

Upgrading

+ +

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

+ +
+pip install --upgrade apache-libcloud==0.19.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/v0.19.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 is participating in Hacktoberfest

+ + + + + + + +
+

Github and DigitalOcean are organizing Hacktoberfest again this year.

+ +

Hacktoberfest is a month-long celebration of open source software where people +are encouraged to contribute to different open source projects. Each user who +submits four pull requests to any Github hosted open source project of their +choice will receive a free t-shirt.

+ +
+ +

Hacktoberfest 2015 t-shirt.

+
+ +

This year we are also happy to announce that we have been selected as one of +the highlighted Python projects which users are invited to check, play with it +and contribute to.

+ +

We think this is a great opportunity for both, long time users and contributors, +but especially people who are new to open source to learn how open source works +and participate.

+ +

Having said that, we would like to invite anyone who is interested to participate +and contribute to our project. You can find more information on contributing to +Libcloud in our contribution guide.

+ +

For more information about the Hacktoberfest project itself and information on +how to sign up, please visit the official website and announcement blog post +from Github and DigitalOcean.

+ +
+ + +
+ + + + + + + +
+ + + +
+ + + + + + + + + + + Added: libcloud/site/trunk/source/_site/blog/archives/2015/11/index.html URL: http://svn.apache.org/viewvc/libcloud/site/trunk/source/_site/blog/archives/2015/11/index.html?rev=1749451&view=auto ============================================================================== --- libcloud/site/trunk/source/_site/blog/archives/2015/11/index.html (added) +++ libcloud/site/trunk/source/_site/blog/archives/2015/11/index.html Tue Jun 21 06:39:51 2016 @@ -0,0 +1,214 @@ + + + + + + + + + + + + + + + + + + Archive: 2015 » November | Apache Libcloud + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + +
+ +

Anthony Shaw (anthonyshaw) joins our team

+ + + + + + + +
+

Please help us extend a warm welcome to our newest team member Anthony +Shaw!

+ +

The Project Management Committee (PMC) for Apache Libcloud has invited Anthony +Shaw to join us as a committer and a PMC member and we are pleased to announce +that he has accepted.

+ +

Anthony has joined the community fairly recently, but he has already made a lot +of substantial contributions. Those contributions range from new Dimension +Data drivers and various related improvements to a proposal for a new backup +API for Backup as a Service products and projects.

+ +

While we are talking about the new backup API - we would like to encourage +everyone who is either a service provider offering Backup as a Service product +or a person interested in using this API to join us and participate in the +discussion. The more feedback we get, the better and more widely applicable +we can make this new API.

+ +

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

+ +
+

Anthony Shaw works for the global system integrator Dimension Data as Head of +Innovation. Anthony has been working in the hosting/service provider industry +for the last 10 years for MSPs within Europe, North America and Australia in +various Product Management and Product Development roles. Anthony is an +open-source advocate and has been promoting the Libcloud project internally to +Dimension Data for the last 9 months as well as maintaining its driver.

+
+ +

And in his own words:

+ +
+

I think we will continue to see consolidation in IaaS providers over the next +12 months, so likelihood is the number of drivers will reduce, but the +importance of being cloud agnostic to people is becoming more apparent as some +are already being burnt by integrations into APIs that companies like Dell and +Ninefold have pulled the plug on. Libcloud is a key project for developers not +wanting to lock themselves too heavily to a vendor. I would also like to see +expansion of additional services like backup, load balancing and containers so +that users can still take advantages of these features through our driver.

+
+ +

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

+ +
+ + +
+ + + + + + + +
+ + + +
+ + + + + + + + + + + Added: libcloud/site/trunk/source/_site/blog/archives/2015/12/index.html URL: http://svn.apache.org/viewvc/libcloud/site/trunk/source/_site/blog/archives/2015/12/index.html?rev=1749451&view=auto ============================================================================== --- libcloud/site/trunk/source/_site/blog/archives/2015/12/index.html (added) +++ libcloud/site/trunk/source/_site/blog/archives/2015/12/index.html Tue Jun 21 06:39:51 2016 @@ -0,0 +1,232 @@ + + + + + + + + + + + + + + + + + + Archive: 2015 » December | Apache Libcloud + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + +
+ +

Libcloud 0.20.0 released

+ + + + + + + +
+

We are pleased to announce the release of Libcloud 0.20.0.

+ +

This is a first release in the 0.20 series which means it brings many new +features, improvements, bug-fixes, and DNS drivers.

+ +

Release highlights

+ +
    +
  • New DNS driver for GoDaddy
  • +
  • New DNS driver for CloudFlare DNS
  • +
  • Many more improvements and API v2.1 support for the Dimension Data compute driver
  • +
  • Support for adding and configuring PTR (reverse DNS) record in RackSpace DNS driver
  • +
  • Support for preemptable instances in Google Compute driver
  • +
  • Add new eu-west-2 & us-east-2 regions to the OUTSCALEINC & OUTSCALESAS drivers
  • +
  • Added C4, M4 instance types in Amazon EC2 driver
  • +
  • Add support for multiple regions in Aurora compute driver
  • +
  • GoogleStorageDriver can now use either our S3 authentication or other Google Cloud Platform OAuth2 authentication methods.
  • +
  • Removed DreamHosts Compute Driver, DreamHosts users will now use the OpenStack Node driver since DreamHosts are OpenStack API compliant
  • +
  • and much more!
  • +
+ +

Full change log can be found at here.

+ +

Download

+ +

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

+ +
+pip install apache-libcloud==0.20.0
+
+ +

Upgrading

+ +

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

+ +
+pip install --upgrade apache-libcloud==0.20.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.

+ +
+ + +
+ + + + + + + +
+ + + +
+ + + + + + + + + + + Added: libcloud/site/trunk/source/_site/blog/archives/2016/01/index.html URL: http://svn.apache.org/viewvc/libcloud/site/trunk/source/_site/blog/archives/2016/01/index.html?rev=1749451&view=auto ============================================================================== --- libcloud/site/trunk/source/_site/blog/archives/2016/01/index.html (added) +++ libcloud/site/trunk/source/_site/blog/archives/2016/01/index.html Tue Jun 21 06:39:51 2016 @@ -0,0 +1,587 @@ + + + + + + + + + + + + + + + + + + Archive: 2016 » January | Apache Libcloud + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + +
+ +

Libcloud 1.0.0-pre1 released

+ + + + + + + +
+

We are pleased to announce the release of Libcloud 1.0.0-pre1.

+ +

This is a first pre-release in the 1.0.0 series which means it brings many new +features, improvements, bug-fixes, and DNS drivers.

+ +

Release highlights

+ +

A full blog post on the new features in 1.0.0 can be found here

+ +

This includes:

+ +
    +
  • Introduction of Container-as-a-Service API drivers for Kubernetes, Docker, Amazon ECS and Joyent Triton
  • +
  • Introduction of Backup-as-a-Service API
  • +
  • Addition of South Korea region for Amazon EC2
  • +
+ +

Full change log can be found at here.

+ +

Download

+ +

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

+ +
+pip install apache-libcloud==1.0.0-pre1
+
+ +

Upgrading

+ +

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

+ +
+pip install --upgrade apache-libcloud==1.0.0-pre1
+
+ +

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.

+ +
+ + +
+ + +
+ +

Libcloud 1.0-pre1 open for feedback

+ + + + + + + +
+

We are pleased to announce that version 1.0-pre1 vote thread is open and the release is ready for community feedback.

+ +

1.0-pre1 marks the first pre-release of the 1.0 major release. Some years ago, Tomaz Muraus spoke on the podcast FLOSS weekly. +Tomaz spoke about how much of a huge challenge porting the project to Python 3.x would be(!) as well as the 1.0 milestone.

+ +

It is worth listening to the podcast to see how far things have come, we now average 2 pull-requests a day and have 156 contributors.

+ +

As the project has matured over the last 5 years one of the most remarkable changes has been the adoption from the community and +continued support from our contributors adding new drivers, patching strange API issues and keeping the project alive.

+ +

Anthony Shaw will be speaking on the FLOSS weekly podcast on February 2nd and discussing our community and the project, so +please tune in.

+ +

The Cloud market as I'm sure you're all aware of is thriving, the purpose of Libcloud was originally:

+ +
    +
  • To help prevent lock-in to a particular vendor
  • +
  • To abstract the complexity of vendor APIs
  • +
  • To give a simple way for deploying to and managing multiple cloud vendors
  • +
+ +

Since that we have had (at the last count) 2,118,539 downloads. The project continues to grow in popularity with each new release.

+ +

So with the 1.0 major release we would like to announce 2 new driver types, containers and backup.

+ +

History of our drivers

+ +

The compute (IaaS) API is what libcloud is best known for but there is a range of drivers available for many other capabilities.

+ +

There is a presentation on the value of using Libcloud to avoid lock in on SlideShare

+ +

This is a history of the different driver types in the libcloud project.

+ +
    +
  • Compute (v0.1.0) + +
      +
    • Support for nodes, node images, locations, states
    • +
    • 52 providers including every major cloud provider in the market. Plus local services like Vmware, OpenStack, libvirt
    • +
  • +
  • DNS (v0.6.0) + +
      +
    • Support for zones, records, recordtypes
    • +
    • 19 providers including CloudFlare, DigitalOcean, DNSimple, GoDaddy, Google DNS, Linode, Rackspace, Amazon R53, Zerigo
    • +
  • +
  • Object Storage (v0.5.0) + +
      +
    • Support for containers and objects
    • +
    • 11 providers including Amazon S3, Azure Blobs, Google storage, CloudFiles, OpenStack Swift
    • +
  • +
  • Load Balancer (v0.5.0) + +
      +
    • Support for nodes, balancers, listeners and algorithms
    • +
    • 11 providers including CloudStack, Dimension Data, Amazon ELB, Google GCE LB, SoftLayer LB
    • +
  • +
  • Backup (v0.20.0) + +
      +
    • Support for backup targets, recovery points and jobs
    • +
    • 3 providers, Dimension Data, Amazon EBS snaps, Google snaps
    • +
  • +
+ +

Introducing Backup Drivers

+ +

With 1.0-pre1 we have introduced a new driver type for backup, libcloud.backup

+ +

Backup API allows you to manage Backup as A Service and services such as EBS Snaps, +GCE volume snap and dimension data backup.

+ +

Terminology

+ +
    +
  • libcloud.backup.base.BackupTarget - Represents a backup target, like a Virtual Machine, a folder or a database.
  • +
  • libcloud.backup.base.BackupTargetRecoveryPoint - Represents a copy of the data in the target, a recovery point can be +recovered to a backup target. An inplace restore is where you recover to the same target and an out-of-place restore is where you +recover to another target.
  • +
  • libcloud.backup.base.BackupTargetJob - Represents a backup job running on backup target.
  • +
+ +

Introducing Container-as-a-Service Drivers

+ +

The API is for Container-as-a-Service providers, these new types of cloud services offer container management and hosting as a service. +The new services are already providing proprietary APIs, giving the need for a tool like Libcloud if you want to provision to any cloud provider.

+ +

Google, Amazon and Joyent have all announced Container cloud services and Microsoft have launched a beta service also, so we are getting on the front foot with an +abstraction API for people wishing to gain similar benefits to the compute, load balancer and storage APIs.

+ +

A presentation on this topic is available on SlideShare.

+ +

Isn't docker a standard? +Well, yes and no.

+ +

Docker has been the main technology adopted by these providers as the host system for the containers and also as the specification of the containers themselves. +But, Docker is not a provisioning system, it is a virtualization host. Also there are alternatives, like CoreOS Rkt.

+ +

Container API design

+ +

Container-as-a-Service providers will implement the ContainerDriver class to provide functionality for :

+ +
    +
  • Listing deployed containers
  • +
  • Starting, stopping and restarting containers (where supported)
  • +
  • Destroying containers
  • +
  • Creating/deploying containers
  • +
  • Listing container images
  • +
  • Installing container images (pulling an image from a local copy or remote repository)
  • +
+ +

Simple Container Support

+ +
    +
  • libcloud.container.base.ContainerImage - Represents an image that can be deployed, like an application or an operating system
  • +
  • libcloud.container.base.Container - Represents a deployed container image running on a container host
  • +
+ +

Cluster Suppport

+ +

Cluster support extends on the basic driver functions, but where drivers implement the class-level attribute supports_clusters as True +clusters may be listed, created and destroyed. When containers are deployed, the target cluster can be specified.

+ +
    +
  • libcloud.container.base.ContainerCluster - Represents a deployed container image running on a container host
  • +
  • libcloud.container.base.ClusterLocation - Represents a location for clusters to be deployed
  • +
+ +

Using the container drivers

+ +

The container drivers have been designed around similar principles to the compute driver. It is simple to use and a flat class design.

+
from libcloud.container.providers import get_driver
+from libcloud.container.types import Provider
+
+Cls = get_driver(Provider.DOCKER)
+driver = Cls('user', 'api key')
+
+image = driver.install_image('tomcat:8.0')
+container = driver.deploy_container('tomcat', image)
+
+container.restart()
+
+

Container Registries

+ +

The Docker Registry API is used by services like Amazon ECR, the Docker Hub website and by anyone hosting their own Docker registry. +It doesn't belong to a particular driver, so is a utility class. +Some providers, like Amazon ECR have a factory method to provide a registry client +Images from docker registry can be sent to the deploy_container method for any driver.

+
from libcloud.container.utils.docker import HubClient 
+hub = HubClient() 
+image = hub.get_image('ubuntu', 'latest') 
+
+

When other container registry services are made available these can be provided in a similar context.

+ +

Prototype drivers in libcloud.container

+ +

Drivers have been provided to show example implementations of the API, these drivers are experimental and need to go through more thorough community testing +before they are ready for a stable release.

+ + + +

The driver with the most contentious implementation is Kubernetes. We would like users of the Amazon ECS, Google Containers and Kubernetes project to provide feedback +on how they would like to map clusters, pods, namespaces to the low level concepts in the driver.

+ +

Providing feedback

+ +

The voting thread is open, please use this as your opportunity to give feedback.

+ +

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 0.20.1 released

+ + + + + + + +
+

We are pleased to announce the release of Libcloud 0.20.1.

+ +

This is a bug-fix release in the 0.20 series.

+ +

Release highlights

+ +
    +
  • Allow for old and new style service accounts for GCE driver
  • +
  • Fix syntax error with DimensionDataStatus object
  • +
  • Fix bug in public IP addition command for DimensionData driver
  • +
  • Fix error with proxy_url with vCloud Compute driver.
  • +
  • Fix with hasattr for Rackspace DNS driver.
  • +
+ +

Full change log can be found at here.

+ +

Download

+ +

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

+ +
+pip install apache-libcloud==0.20.1
+
+ +

Upgrading

+ +

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

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

+ +
+ + +
+ + +
+ +

Notice for Linode users

+ + + + + + + +
+

This is an announcement for users of the Linode driver for Libcloud who might +have started experiencing issues recently.

+ +

Background

+ +

A couple of Libcloud users have reported that they have recently started +experiencing issues when talking to the Linode API using Libcloud. They have +received messages similar to the one shown below.

+ +
+socket.error: [Errno 104] Connection reset by peer
+
+ +

It turns out that the issue is related to the used SSL / TLS version. For +compatibility and security reasons (Libcloud also supports older Python +versions), Libcloud uses TLS v1.0 by default.

+ +

Linode recently dropped support for TLS v1.0 and it now only support TLS >= +v1.1. This means Libcloud won't work out of the box anymore.

+ +

Solution

+ +

If you are experiencing this issue, you should update your code to use TLS v1.2 +or TLS v1.1 as shown below.

+
import ssl
+
+import libcloud.security
+libcloud.security.SSL_VERSION = ssl.PROTOCOL_TLSv1_1
+# or even better if your system and Python version supports TLS v1.2
+libcloud.security.SSL_VERSION = ssl.PROTOCOL_TLSv1_2
+
+# Instantiate and work with the Linode driver here...
+
+

Keep in mind that for this to work you need to have a recent version of OpenSSL +installed on your system and you need to use Python >= 3.4 or Python 2.7.9.

+ +

For more details please see recently updated documentation. If you are +still experiencing issues or have any questions, please feel free to reach +us via the mailing list or IRC.

+ +

Note: Even if you are not experiencing any issues, it's generally a good idea +to use the highest version of TLS supported by your system and the provider you +use.

+ +

Quick note on ssl.PROTOCOL_SSLv23

+ +

Python uses ssl.PROTOCOL_SSLv23 constant by default. When this constant is +used, it will let client known to pick the highest protocol version which both +the client and server support (it will be selecting between SSL v3.0, TLS v1.0, +TLS v1.1 and TLS v1.2).

+ +

We use ssl.PROTOCOL_TLSv1 instead of ssl.PROTOCOL_SSLv23 for security +and compatibility reasons. SSL v3.0 is considered broken and unsafe and using +ssl.PROTOCOL_SSLv23 can result in an increased risk for a downgrade attack.

+ +

Thanks

+ +

Special thanks to Jacob Riley, Steve V, Heath Naylor and everyone from +LIBCLOUD-791 who helped debug and track down the root cause of this issue.

+ +
+ + +
+ + + + + + + +
+ + + +
+ + + + + + + + + + +