From notifications-return-17245-archive-asf-public=cust-asf.ponee.io@libcloud.apache.org Sun Jun 14 18:32:38 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 30373180629 for ; Sun, 14 Jun 2020 20:32:38 +0200 (CEST) Received: (qmail 36823 invoked by uid 500); 14 Jun 2020 18:32:37 -0000 Mailing-List: contact notifications-help@libcloud.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@libcloud.apache.org Delivered-To: mailing list notifications@libcloud.apache.org Received: (qmail 36763 invoked by uid 500); 14 Jun 2020 18:32:37 -0000 Delivered-To: apmail-libcloud-commits@libcloud.apache.org Received: (qmail 36749 invoked by uid 99); 14 Jun 2020 18:32:37 -0000 Received: from Unknown (HELO svn01-us-east.apache.org) (13.90.137.153) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Jun 2020 18:32:37 +0000 Received: from svn01-us-east.apache.org (svn01-us-east.apache.org [127.0.0.1]) by svn01-us-east.apache.org (ASF Mail Server at svn01-us-east.apache.org) with ESMTP id 13D1317B504 for ; Sun, 14 Jun 2020 18:32:37 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1878843 [2/8] - in /libcloud/site/trunk: generated/ generated/blog/ generated/blog/2020/06/ generated/blog/2020/06/12/ generated/blog/archives/2020/06/ generated/blog/page/10/ generated/blog/page/11/ generated/blog/page/12/ generated/blog/... Date: Sun, 14 Jun 2020 18:32:36 -0000 To: commits@libcloud.apache.org From: tomaz@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20200614183237.13D1317B504@svn01-us-east.apache.org> Modified: libcloud/site/trunk/generated/blog/page/10/index.html URL: http://svn.apache.org/viewvc/libcloud/site/trunk/generated/blog/page/10/index.html?rev=1878843&r1=1878842&r2=1878843&view=diff ============================================================================== --- libcloud/site/trunk/generated/blog/page/10/index.html (original) +++ libcloud/site/trunk/generated/blog/page/10/index.html Sun Jun 14 18:32:35 2020 @@ -97,6 +97,134 @@
+

Libcloud 0.15.1 released

+ + + + + + + +
+

We are pleased to announce the release of Libcloud 0.15.1!

+ +

This release includes some bug-fixes and improvements.

+ +

Release highlights

+ +
    +
  • Improvements in the EC2 driver
  • +
  • Improvements in the CloudStack driver
  • +
  • Improvements in the Openstack driver
  • +
  • Fixes a possible race condition in the deploy_node method
  • +
+ +

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.15.1
+
+ +

Upgrading

+ +

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

+ +
+pip install --upgrade apache-libcloud==0.15.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#libcloud-0-15-1

+ +

Documentation

+ +

Regular and API documentation is available at https://libcloud.readthedocs.org/en/v0.15.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.

+ +

Source: release announcement.

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

Libcloud's 5th birthday celebration during EuroPython week in Berlin

+ + + + + + + +
+

On July 23nd of this year it will be exactly 5 years from the initial project +announcement on the Cloudkick blog.

+ +

We are going to celebrate this great milestone with a cake and drinks and we +would like to invite you to join us. The celebration will take place in a nice +bar during the EuroPython week in Berlin, Germany.

+ +
+ +

The cake is not a lie!

+
+ +

Celebration will be attended by Libcloud developers so this is also a great +opportunity for you to meet and hang with us in real-life and ask any questions +you might have about the project.

+ +
+ +

For more information visit the eventbrite page.

+
+ +

For more information, exact location and RSVP, please refer to the +Eventbrite page. Keep in mind that RSVP is mandatory if you want to +attend the celebration.

+ +
+ + +
+ + + + +
+

Libcloud 0.15.0 released

@@ -262,244 +390,6 @@ strecthing for over 3 weeks, I sadly had - -
- -

Libcloud 0.14.0 and the new Ikoula driver

- - - - - - - -
-

Libcloud 0.14.0 was released last month. Among many improvements and new -features, this release also includes a brand new driver for -Ikoula public cloud which is based on the generic CloudStack driver.

- - - -

Folks over at Ikoula wrote a short introductory post about this new driver. The post -is in French, so if you speak French and are interested in using Ikoula driver, -you should check it out - Utilisation d'Apache-Libcloud au sein du Cloud -Ikoula.

- -
- - -
- - - - -
- -

Libcloud 0.14 and Google Cloud Platform

- - - - - - - -
-

This is a guest post by Rick Wright. Rick is an engineer at Google and -the main contributor to the Libcloud Google Compute Engine driver.

- -

As anyone following this blog knows, Libcloud 0.14 was recently released. -Included in this release is new support for the Google Compute Engine service -that was recently made generally available.

- -

The first Libcloud driver for Google Compute Engine was initially released last -summer, and has been continually updated to support new Compute Engine -features. Support for the Compute Engine Load Balancer was also recently added.

- -

Libcloud had previously added support for Google Cloud Storage through the S3 -compatibility API.

- -

In this post, we'll show you how to get up and running with Google Compute -Engine with Libcloud, show you how to create some instances (nodes) and point -you to additional resources. We also show you how you can start up 20 -instances in under a minute.

- - - -

Getting Started

- -

If you haven't yet signed up for Google Compute Engine, more information can -be found on the Google Cloud Platform site. We hope that you will look at -the Google Cloud Platform and consider Compute Engine for workloads of any -size.

- -

If you are familiar with Libcloud, using the driver for Compute Engine will -also be familiar to you as nearly all of the standard Libcloud API methods for -Compute and Load Balancing are supported by the Compute Engine drivers.

- -

Setting up Authentication

- -

Google Compute Engine uses OAuth2 for authentication and Libcloud supports two -different authentication methods for Compute Engine: Service Accounts and -Installed Applications. More information can be found about these options in -the driver documentation, but here is a simple walk-through for getting -your Service Account credentials (note that the Service Account authentication -requires the PyCrypto library):

- -

From the Console (https://cloud.google.com/console), select your project. When -your project is open, select "APIs & auth" and then "Credentials" as shown -below:

- -
- -
- -

To create a new Service Account ID, click on "Create New Client ID"

- -
- -
- -

Select "Service account" and click "Create Client ID"

- -
- -
- -

This will create and download a PCKS-12 private key to your local machine. You -will need to convert this to a .pem format key. (See additional instructions -in the driver documentation).

- -
- -
- -

To connect to Compute Engine from Libclould, you will need to provide both the -"Email address" for the service account and the path to the key file.

- -

Creating an Instance

- -

The Compute Engine driver supports the normal Libcloud ways of doing things. -For example, to create the driver you would do something like this:

- -
-from libcloud.compute.types import Provider
-from libcloud.compute.providers import get_driver
-Driver = get_driver(Provider.GCE)
-gce = Driver('your_service_account_email', 'path_to_pem_file',
-             datacenter='us-central1-a',
-             project='your_project_id')
-
- -

Then, you may want to get a list of machine sizes or images to use for your -node creation:

- -
-sizes = gce.list_sizes()
-images = gce.list_images()
-
- -

and then filter them to find the correct size/image object to create your -node. For example:

- -
-size_obj = [s for s in sizes if s.id == 'n1-standard-1'][0]
-image_obj = [i for i in images if i.name == 'debian-7'][0]
-
- -

Finally, you would create the node using the create_node() method:

- -
-new_node = gce.create_node(name='my_node', size=size_obj,
-                           image=img_obj)
-
- -

The GCE driver also supports the ability to pass in size/image by name instead -of by object, so you could create your new node like this, without looking up -the sizes/images:

- -
-new_node = gce.create_node(name='my_node', size='n1-standard-1',
-                           image='debian-7')
-
- -

In this case a new node will be created using the "n1-standard-1" machine -type and will use the latest "debian-7" image that is available.

- -

Creating Multiple Instances

- -

We have added an extra method to the Compute Engine driver to help in the -creation of multiple instances/nodes in parallel. This is the -"excreatemultiple_nodes()" method, and it can be used like this:

- -
-base_name = 'multiple-nodes'
-number = 20
-start_time = time.time()
-multi_nodes = gce.ex_create_multiple_nodes(
-    base_name, 'n1-standard-1', 'debian-7', number)
-end_time = time.time()
-
-print('Created the following %s nodes in %.2f seconds' % (
-   number, end_time-start_time))
-
-for node in multi_nodes:
-   print('   %s' % node.name)
-
- -

Running this gives the following output (timing will likely vary somewhat):

- -
-Created the following 20 nodes in 35.77 seconds
-  multiple-nodes-000
-  multiple-nodes-001
-  multiple-nodes-002
-  multiple-nodes-003
-  multiple-nodes-004
-  ...
-
- -

Onward

- -

This post showed you how to get started, and additional example code can be -found in the Libcloud Compute Engine demo code. The demo code can show you -how to use most of the features of the driver, including: Creating disks, -firewalls and addresses; setting tags; attaching and detaching disks and -deleting resources. There is separate demo code for the Load Balancer -functions which shows how to quickly set up 3 web servers with a Load Balancer -controlling the traffic to them. In addition, the driver documentation -contains the documentation for the extra methods that cover nearly all of the -features of the Compute Engine API.

- -

We are excited to be able to contribute to the Libcloud project and hope that -you will find it useful. We like working with Libcloud and have used it as the -basis for contributing code to other open source projects such as Ansible -and SaltStack. If you run into problems or find bugs, please -report them (or send a pull request) and we will be happy to continue -to fix and enhance the Compute Engine driver in Libcloud.

- -
- - -
- - -

Archive

Modified: libcloud/site/trunk/generated/blog/page/11/index.html URL: http://svn.apache.org/viewvc/libcloud/site/trunk/generated/blog/page/11/index.html?rev=1878843&r1=1878842&r2=1878843&view=diff ============================================================================== --- libcloud/site/trunk/generated/blog/page/11/index.html (original) +++ libcloud/site/trunk/generated/blog/page/11/index.html Sun Jun 14 18:32:35 2020 @@ -97,32 +97,35 @@
-

Sebastien Goasguen (sebgoa) joins our team

+

Libcloud 0.14.0 and the new Ikoula driver

- +
-

The Project Management Committee (PMC) for Apache Libcloud has asked Sebastien -Goasguen (sebgoa) to join us as a committer and a PMC member. We are pleased -to announce that he has accepted.

+

Libcloud 0.14.0 was released last month. Among many improvements and new +features, this release also includes a brand new driver for +Ikoula public cloud which is based on the generic CloudStack driver.

-

Sebastien is no stranger to the Libcloud project. He has been contributing and -actively participating in the Libcloud community for quite a while now.

- -

On top of that, he is also a PMC member at the Apache CloudStack project and -our local "CloudStack guy".

+ -

We are happy to have him and some direct CloudStack expertise in our team.

+

Folks over at Ikoula wrote a short introductory post about this new driver. The post +is in French, so if you speak French and are interested in using Ikoula driver, +you should check it out - Utilisation d'Apache-Libcloud au sein du Cloud +Ikoula.

@@ -132,30 +135,197 @@ our local "CloudStack guy".

-

Call for Participation in Google Summer of Code 2014

+

Libcloud 0.14 and Google Cloud Platform

- +
-
- - +

This is a guest post by Rick Wright. Rick is an engineer at Google and +the main contributor to the Libcloud Google Compute Engine driver.

+ +

As anyone following this blog knows, Libcloud 0.14 was recently released. +Included in this release is new support for the Google Compute Engine service +that was recently made generally available.

+ +

The first Libcloud driver for Google Compute Engine was initially released last +summer, and has been continually updated to support new Compute Engine +features. Support for the Compute Engine Load Balancer was also recently added.

+ +

Libcloud had previously added support for Google Cloud Storage through the S3 +compatibility API.

+ +

In this post, we'll show you how to get up and running with Google Compute +Engine with Libcloud, show you how to create some instances (nodes) and point +you to additional resources. We also show you how you can start up 20 +instances in under a minute.

+ +
+ +
-

If you would like to participate in Google Summer of Code 2014 and work on -Apache Libcloud, we invite you to read the following blog post for more -information - Libcloud Google Summer of Code 2014 Call for Participation.

+

Getting Started

+ +

If you haven't yet signed up for Google Compute Engine, more information can +be found on the Google Cloud Platform site. We hope that you will look at +the Google Cloud Platform and consider Compute Engine for workloads of any +size.

+ +

If you are familiar with Libcloud, using the driver for Compute Engine will +also be familiar to you as nearly all of the standard Libcloud API methods for +Compute and Load Balancing are supported by the Compute Engine drivers.

+ +

Setting up Authentication

+ +

Google Compute Engine uses OAuth2 for authentication and Libcloud supports two +different authentication methods for Compute Engine: Service Accounts and +Installed Applications. More information can be found about these options in +the driver documentation, but here is a simple walk-through for getting +your Service Account credentials (note that the Service Account authentication +requires the PyCrypto library):

+ +

From the Console (https://cloud.google.com/console), select your project. When +your project is open, select "APIs & auth" and then "Credentials" as shown +below:

+ +
+ +
+ +

To create a new Service Account ID, click on "Create New Client ID"

+ +
+ +
+ +

Select "Service account" and click "Create Client ID"

+ +
+ +
+ +

This will create and download a PCKS-12 private key to your local machine. You +will need to convert this to a .pem format key. (See additional instructions +in the driver documentation).

+ +
+ +
+ +

To connect to Compute Engine from Libclould, you will need to provide both the +"Email address" for the service account and the path to the key file.

+ +

Creating an Instance

+ +

The Compute Engine driver supports the normal Libcloud ways of doing things. +For example, to create the driver you would do something like this:

+ +
+from libcloud.compute.types import Provider
+from libcloud.compute.providers import get_driver
+Driver = get_driver(Provider.GCE)
+gce = Driver('your_service_account_email', 'path_to_pem_file',
+             datacenter='us-central1-a',
+             project='your_project_id')
+
+ +

Then, you may want to get a list of machine sizes or images to use for your +node creation:

+ +
+sizes = gce.list_sizes()
+images = gce.list_images()
+
+ +

and then filter them to find the correct size/image object to create your +node. For example:

+ +
+size_obj = [s for s in sizes if s.id == 'n1-standard-1'][0]
+image_obj = [i for i in images if i.name == 'debian-7'][0]
+
+ +

Finally, you would create the node using the create_node() method:

+ +
+new_node = gce.create_node(name='my_node', size=size_obj,
+                           image=img_obj)
+
+ +

The GCE driver also supports the ability to pass in size/image by name instead +of by object, so you could create your new node like this, without looking up +the sizes/images:

+ +
+new_node = gce.create_node(name='my_node', size='n1-standard-1',
+                           image='debian-7')
+
+ +

In this case a new node will be created using the "n1-standard-1" machine +type and will use the latest "debian-7" image that is available.

+ +

Creating Multiple Instances

+ +

We have added an extra method to the Compute Engine driver to help in the +creation of multiple instances/nodes in parallel. This is the +"excreatemultiple_nodes()" method, and it can be used like this:

+ +
+base_name = 'multiple-nodes'
+number = 20
+start_time = time.time()
+multi_nodes = gce.ex_create_multiple_nodes(
+    base_name, 'n1-standard-1', 'debian-7', number)
+end_time = time.time()
+
+print('Created the following %s nodes in %.2f seconds' % (
+   number, end_time-start_time))
+
+for node in multi_nodes:
+   print('   %s' % node.name)
+
+ +

Running this gives the following output (timing will likely vary somewhat):

+ +
+Created the following 20 nodes in 35.77 seconds
+  multiple-nodes-000
+  multiple-nodes-001
+  multiple-nodes-002
+  multiple-nodes-003
+  multiple-nodes-004
+  ...
+
+ +

Onward

+ +

This post showed you how to get started, and additional example code can be +found in the Libcloud Compute Engine demo code. The demo code can show you +how to use most of the features of the driver, including: Creating disks, +firewalls and addresses; setting tags; attaching and detaching disks and +deleting resources. There is separate demo code for the Load Balancer +functions which shows how to quickly set up 3 web servers with a Load Balancer +controlling the traffic to them. In addition, the driver documentation +contains the documentation for the extra methods that cover nearly all of the +features of the Compute Engine API.

+ +

We are excited to be able to contribute to the Libcloud project and hope that +you will find it useful. We like working with Libcloud and have used it as the +basis for contributing code to other open source projects such as Ansible +and SaltStack. If you run into problems or find bugs, please +report them (or send a pull request) and we will be happy to continue +to fix and enhance the Compute Engine driver in Libcloud.

@@ -165,34 +335,32 @@ information - -

Libcloud 0.14.1 and the new CloudSigma driver

+

Sebastien Goasguen (sebgoa) joins our team

- +
-

Libcloud 0.14.1 has been release recently. Among other bug fixes, -improvements and new features, this release also includes a brand new compute -driver for CloudSigma API 2.0 with an extensive documentation.

+

The Project Management Committee (PMC) for Apache Libcloud has asked Sebastien +Goasguen (sebgoa) to join us as a committer and a PMC member. We are pleased +to announce that he has accepted.

- +

Sebastien is no stranger to the Libcloud project. He has been contributing and +actively participating in the Libcloud community for quite a while now.

-

If you want to learn more about this new driver, I encourage you to check a guest -post I wrote on the CloudSigma blog which shows some examples of how to use this new -driver - CloudSigma API v2.0 is now supported in Libcloud.

+

On top of that, he is also a PMC member at the Apache CloudStack project and +our local "CloudStack guy".

+ +

We are happy to have him and some direct CloudStack expertise in our team.

@@ -202,77 +370,30 @@ driver - -

Libcloud 0.14.1 released

+

Call for Participation in Google Summer of Code 2014

- +
-

We are pleased to announce the release of Libcloud 0.14.1!

- -

This release includes some bug-fixes, improvements and new features.

- -

Release highlights

- -
    -
  • New driver for CloudSigma API 2.0
  • -
  • Improvements in the OpenStack driver
  • -
  • Support for records with multiple values in the Route53 DNS driver
  • -
  • Support for paging through zones and records in the 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.14.1
-
- -

Upgrading

- -

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

- -
-pip install --upgrade apache-libcloud==0.14.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#libcloud-0-14-1

- -

Documentation

- -

Regular and API documentation is available at https://libcloud.readthedocs.org/en/v0.14.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.

+ -

Source: release announcement.

+

If you would like to participate in Google Summer of Code 2014 and work on +Apache Libcloud, we invite you to read the following blog post for more +information - Libcloud Google Summer of Code 2014 Call for Participation.

@@ -282,27 +403,34 @@ list of people who contributed to this r
-

New committer Alex Gaynor joins our team

+

Libcloud 0.14.1 and the new CloudSigma driver

- +
-

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

+

Libcloud 0.14.1 has been release recently. Among other bug fixes, +improvements and new features, this release also includes a brand new compute +driver for CloudSigma API 2.0 with an extensive documentation.

-

We are glad to have him as a committer. Everyone, please help us welcome him -to the team :)

+ + +

If you want to learn more about this new driver, I encourage you to check a guest +post I wrote on the CloudSigma blog which shows some examples of how to use this new +driver - CloudSigma API v2.0 is now supported in Libcloud.

@@ -333,7 +461,7 @@ to the team :)

Archive

Modified: libcloud/site/trunk/generated/blog/page/12/index.html URL: http://svn.apache.org/viewvc/libcloud/site/trunk/generated/blog/page/12/index.html?rev=1878843&r1=1878842&r2=1878843&view=diff ============================================================================== --- libcloud/site/trunk/generated/blog/page/12/index.html (original) +++ libcloud/site/trunk/generated/blog/page/12/index.html Sun Jun 14 18:32:35 2020 @@ -97,6 +97,116 @@
+

Libcloud 0.14.1 released

+ + + + + + + +
+

We are pleased to announce the release of Libcloud 0.14.1!

+ +

This release includes some bug-fixes, improvements and new features.

+ +

Release highlights

+ +
    +
  • New driver for CloudSigma API 2.0
  • +
  • Improvements in the OpenStack driver
  • +
  • Support for records with multiple values in the Route53 DNS driver
  • +
  • Support for paging through zones and records in the 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.14.1
+
+ +

Upgrading

+ +

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

+ +
+pip install --upgrade apache-libcloud==0.14.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#libcloud-0-14-1

+ +

Documentation

+ +

Regular and API documentation is available at https://libcloud.readthedocs.org/en/v0.14.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.

+ +

Source: release announcement.

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

New committer Alex Gaynor joins our team

+ + + + + + + +
+

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

+ +

We are glad to have him as a committer. Everyone, please help us welcome him +to the team :)

+ +
+ + +
+ + + + +
+

Libcloud 0.14 and the Rackspace drivers

@@ -310,146 +420,6 @@ the changes yourself.

- -
- -

Libcloud 0.14.0 released

- - - - - - - -
-

We are pleased to announce a long awaited Libcloud 0.14.0 release.

- -

This is a first release in the 0.14 series which means it brings many -(and I mean many!) new features, changes and improvements.

- -

Release highlights

- -
    -
  • To make working with providers which support multiple regions easier and -more user-friendly, some of the drivers have moved away from the "one -class per region" to a single class plus "region" argument model. Those -drivers include: EC2, Rackspace, ElasticHosts, Joyent, CloudFiles.
  • -
  • Addition of a programmatic way of updating the pricing file and ability -to use a custom pricing file. For more information, please see -https://libcloud.readthedocs.org/en/latest/compute/pricing.html#using-a-custom-pricing-file
  • -
  • Addition of block storage management methods to the following drivers: -OpenNebula, OpenStack, EC2
  • -
  • Unification of the extension arguments for handling security groups in -the EC2 and OpenStack driver
  • -
  • New standard compute API for SSH key-pair management
  • -
  • Many new features and improvements in the CloudStack driver
  • -
  • New compute and load balancer driver for Google Compute Engine (GCE)
  • -
  • Ability to export Libcloud's DNS zone to BIND zone format
  • -
  • and much more!
  • -
- -

Full change log can be found here and here (keep in mind that this -release also includes all the changes from 0.14.0-beta3).

- -

Note about backward compatibility

- -

Some of the changes noted above are backward incompatible. For more -information on what has changed and how to update your code to work with -a new release, please visit the Upgrade Notes page.

- -

Download

- -

Libcloud 0.14.0 can be downloaded from -https://libcloud.apache.org/downloads.html

- -

or installed using pip:

- -
pip install apache-libcloud==0.14.0
-
- -

Upgrading

- -

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

- -
pip install --upgrade apache-libcloud==0.14.0
-
- -

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 -Changelog.

- -
- - -
- - - - -
- -

Quick update about 0.13.3 release and DigitalOcean vulnerability

- - - - - - - -
-

This is a quick update about the recent 0.13.3 security release and the -DigitalOcean vulnerability.

- -

DigitalOcean updated their blog post. The updated post says that -scrubbing is now enabled by default for all the newly issued destroy -requests:

- -
-

All Destroys Default to Scrub

- -

We have updated the destroy method to scrub on all destroys, both for -web and API requests.

-
- -

This means that no action is required on the client side and upgrading -to 0.13.3 should not be necessary anymore.

- -

References:

- - - -
- - -
- - -

Archive