Re: [dev] [ACTION] Roll Call for Apache LibCloud project PMC members

Hi Shane, I've been a PMC on libcloud since around 2014 (iirc). I continue to support Tomaz and the libcloud community. Kind regards, Eric On Sat, Sep 2, 2023 at 11:16 AM Shane Curcuru wrote: > While I see the project has made a new release with a bunch of cleaned > up code - excellent news! -

Re: [dev] [VOTE] Release Apache Libcloud 3.8.0

[+1] Release Apache Libcloud 3.8.0 On Sun, Aug 6, 2023 at 10:39 AM Tomaz Muraus wrote: > This is a voting thread for Libcloud v3.8.0 ( > https://github.com/apache/libcloud/tree/v3.8.0-tentative). > > The last release was in January 2023 and a lot of changes have accumulated > in trunk > since th

Re: [dev] [VOTE] Release Apache Libcloud 3.7.0

[+1] Release Apache Libcloud 3.7.0 On Mon, Jan 2, 2023 at 11:30 AM Tomaz Muraus wrote: > This is a voting thread for Libcloud v3.7.0 ( > https://github.com/apache/libcloud/tree/v3.7.0-tentative). > > Changelog can be found at > https://github.com/apache/libcloud/blob/trunk/CHANGES.rst#changes-i

Re: [dev] [VOTE] Release Apache Libcloud 3.6.1

[+1] Release Apache Libcloud 3.6.1 On Sun, Oct 2, 2022 at 3:31 AM Tomaz Muraus wrote: > This is a voting thread for Libcloud v3.6.1 ( > https://github.com/apache/libcloud/tree/v3.6.1-tentative). > > Changelog can be found at > https://github.com/apache/libcloud/blob/trunk/CHANGES.rst#changes-in-

Re: [dev] Dropping support for Python 3.6?

On Thu, Sep 8, 2022 at 3:35 AM Tomaz Muraus wrote: > Python 3.6 has been officially end of life since December, 2021 ( > https://endoflife.date/python). > > Latest versions of some of the testing and lint libraries we use don't > support it anymore. > > Because of that, I propose dropping support

Re: [dev] [VOTE] Release Apache Libcloud 3.6.0

[+1] Release Apache Libcloud 3.6.0 On Sun, May 22, 2022 at 12:09 PM Tomaz Muraus wrote: > This is a voting thread for Libcloud v3.6.0 ( > https://github.com/apache/libcloud/tree/v3.6.0-tentative). > > Changelog can be found at > https://github.com/apache/libcloud/blob/trunk/CHANGES.rst#changes-i

Re: [dev] [VOTE] Release Apache Libcloud 3.5.1

[+1] Release Apache Libcloud 3.5.1 On Thu, Mar 24, 2022 at 8:18 AM Tomaz Muraus wrote: > This is a voting thread for Libcloud v3.5.1 ( > https://github.com/apache/libcloud/tree/v3.5.1-tentative). > > This release includes a small bug / fix improvement which allows HTTP > retrying code to also r

Re: [dev] [VOTE] Release Apache Libcloud 3.5.0

[+1] Release Apache Libcloud 3.5.0 On Tue, Mar 8, 2022 at 2:24 PM Tomaz Muraus wrote: > This is a voting thread for Libcloud v3.5.0 ( > https://github.com/apache/libcloud/tree/v3.5.0-tentativehttps://github.com/apache/libcloud/tree/v3.5.0-tentative > ). > > This release drops support for Python

Re: [dev] [VOTE] Release Apache Libcloud 3.4.1 (somewhat urgent regression bug fix release)

[+1] Release Apache Libcloud 3.4.1 Yikes! Thanks for getting on that right away! On Fri, Nov 12, 2021 at 7:26 AM Tomaz Muraus wrote: > This is a voting thread for Libcloud v3.4.1 > (28d3785c996bd8ff56b508518bb06dbe3f4466eb, [ > https://github.com/apache/libcloud/tree/v3.4.1-tentative,](https://

Re: [dev] [VOTE] Release Apache Libcloud 3.4.0

[+1] Release Apache Libcloud 3.4.0 On Sun, Nov 7, 2021 at 11:26 AM Tomaz Muraus wrote: > This is a voting thread for Libcloud v3.4.0 ( > https://github.com/apache/libcloud/tree/ab4069a951e0ffd044f7e7d436fb0f35a4fb6f7b, > https://github.com/apache/libcloud/tree/v3.4.0-tentative) > > It has been a

Re: [dev] [VOTE] Release Apache Libcloud 3.3.1

[+1] Release Apache Libcloud 3.3.1 On Fri, Jan 22, 2021 at 12:27 PM Tomaz Muraus wrote: > This is a voting thread for Libcloud v3.3.1 ( > https://github.com/apache/libcloud/commit/449b315ea47ba85f79b4062b1d398e94e545d273 > ) > > It includes an important bug fix for regression which was introduce

Re: [dev] [VOTE] Release Apache Libcloud 3.2.0

[+1] Release Apache Libcloud 3.2.0 On Sun, Aug 30, 2020 at 2:21 PM Tomaz Muraus wrote: > This is a voting thread for Libcloud v3.2.0 ( > > https://github.com/apache/libcloud/commit/72de440a508fdb4ea546d4e586a452472f1cbd5d > ) > > Changelog can be found at > > https://github.com/apache/libcloud/b

Re: [dev] [VOTE] Release Apache Libcloud 2.8.3

[+1] Release Apache Libcloud 2.8.3 On Sun, Jun 7, 2020 at 5:31 AM Tomaz Muraus wrote: > This is a voting thread for Libcloud v2.8.3 ( > > https://github.com/apache/libcloud/commit/31a26ace57c427510ae932718f3435a99f912772 > ) > > The release cherry picks two bug fixes from trunk / v3.x.x series

Re: [dev] [VOTE] Release Apache Libcloud 3.1.0 (take 2)

[+1] Release Apache Libcloud 3.1.0 On Sat, Jun 6, 2020 at 3:14 PM Tomaz Muraus wrote: > This is a voting thread for Libcloud v3.1.0 ( > > https://github.com/apache/libcloud/commit/9b14d341ed188bcd7a6ebc660e26a22c371122c7 > ) > > The release content is exactly the same as the one in the > previo

Re: [dev] [VOTE] Release Apache Libcloud 3.0.0

[+1] Release Apache Libcloud 3.0.0 On Sat, Apr 4, 2020 at 12:55 PM Tomaz Muraus wrote: > The time has finally come. > > This is a voting thread for Libcloud v3.0.0. > > This release includes all the changes which were included in v3.0.0-rc1 > plus all the additional changes which have accumulat

Re: [dev] [VOTE] Release Apache Libcloud 2.8.2

[+1] Release Apache Libcloud 2.8.2 On Sat, Apr 4, 2020 at 1:48 PM Tomaz Muraus wrote: > Tomaz Muraus > 9:54 PM (36 minutes ago) > to dev > This is a voting thread for Libcloud v2.8.2. > > This release includes a couple of bug-fixes and improvements for the > deploy_node() > functionality. > >

Re: [dev] [ANNOUNCE] Apache Libcloud 2.8.1. release

[+1] Release Apache Libcloud 2.8.1 On Sat, Feb 29, 2020 at 2:15 PM Tomaz Muraus wrote: > This is a voting thread for Libcloud v2.8.1. > > This is a first bug-fix release in v2.8.x series. > > Quite some bug fixes have accumulated in trunk since v2.8.0 release, so I > decided > to do another rel

Re: [dev] [VOTE] Release Apache Libcloud 3.0.0rc1

[+1] Release Apache Libcloud 3.0.0rc1 On Fri, Jan 24, 2020 at 3:32 AM Tomaz Muraus wrote: > This is a voting thread for Libcloud v3.0.0-rc1 > > This release includes various changes, most notable ones being: > > * Drop support for Python versions < 3.5 > * Type annotations for the base storage A

Re: [dev] [VOTE] Release Apache Libcloud 2.7.0

[ +1] Release Apache Libcloud 2.7.0 On Thu, Dec 5, 2019 at 12:06 PM Tomaz Muraus wrote: > This is a voting thread for Libcloud v2.7.0. > > This release includes a couple of big new features, the most prominent ones > being: > > * Type annotations / hints for the base Libcloud compute API > * Ne

Re: [dev] Promoting start node and stop node methods to the standard Libcloud compute API

+1 - no objections On Tue, Nov 26, 2019 at 1:37 PM Tomaz Muraus wrote: > All, > > A lot of the existing compute drivers (15+) already implement start and > stop node functionality via "ex_start_node" and "ex_stop_node" extension > driver methods so I think it only makes sense to promote those m

Re: [dev] [VOTE] Release Apache Libcloud 2.6.1

[+1] Release Apache Libcloud 2.6.1 Passed my poking at it - thanks for the release Tomaz. On Thu, Nov 14, 2019 at 5:59 AM Tomaz Muraus wrote: > This is a voting thread for Libcloud v2.6.1. > > This release includes a couple of small bug fixes and improvements. > > Full list of changes can be fo

Re: [dev] Moving to Github Actions for our CI/CD

Works for me. I have no vendor lock-in concerns. :) The only question I have is about Beta status and what that means. In GCP, a Beta service means feature-complete and no breaking changes when the service moves to GA. But Beta has no SLAs. I don't know how GitHub/MS define Beta, nor what their ti

Re: [dev] [VOTE] Release Apache Libcloud 2.5.0

[ +1] Release Apache Libcloud 2.5.0 Looks good, thank you Tomaz! On Tue, May 28, 2019 at 10:48 PM Rick van de Loo wrote: > [ +1] Release Apache Libcloud 2.5.0 > > Op di 28 mei 2019 om 23:00 schreef Tomaz Muraus : > > > This is a voting thread for Libcloud 2.5.0. It includes all the > > change

Re: [dev] Moving all Libcloud development and issue management to Github

Great plan Tomaz, no objections here. On Wed, May 29, 2019 at 2:20 PM Tomaz Muraus wrote: > Everyone, > > Apache now supports Github as a first class citizen ( > https://gitbox.apache.org/), so I think it's finally time to drop support > for (bloated, non-user friendly and passé) JIRA and move a

Re: [dev] [VOTE] Release Apache Libcloud 2.3.0

Tested GCE driver and looked over some history. Looks good to me. [+1] Release Apache Libcloud 2.4.0 Thanks for putting the release together Quentin! On Sat, Oct 27, 2018 at 12:04 AM Quentin Pradet wrote: > This is a voting thread for Libcloud 2.4.0. It includes all the > changes from trunk w

Re: [dev] Subject: new committer: Rick van de Loo

Welcome Rick! On Wed, Jun 27, 2018 at 12:43 PM Tomaz Muraus wrote: > Welcome! > > And thanks to Quentin for initiating the vote. > > > https://libcloud.apache.org/blog/2018/06/27/rick-van-de-loo-joins-our-team.html > > On Tue, Jun 26, 2018 at 7:53 PM, Quentin Pradet > wrote: > > > The Project M

Re: [dev] [VOTE] Release Apache Libcloud 2.3.0 [2nd vote]

Sorry for the lag and lgtm. [+1] Release Apache Libcloud 2.3.0 On Sun, Feb 25, 2018 at 7:12 PM anthony shaw wrote: > This is a *replacement* voting thread for Libcloud 2.3.0. It includes all > the changes > from trunk which have landed there since v2.2.1. > > --- note on previous thread --- >

Re: [dev] [VOTE] Release Apache Libcloud 2.2.1

[+1] Release Apache Libcloud 2.2.1 On Wed, Sep 20, 2017 at 12:11 PM, Tomaz Muraus wrote: > This is a voting thread for Libcloud 2.2.1. It includes all the changes > from trunk which have landed there since v2.2.0. > > Most notable one is a bug fix for installation failure which could happen > on

Re: [dev] [VOTE] Release Apache Libcloud 2.2.0

[+1] Release Apache Libcloud 2.2.0 On Mon, Aug 28, 2017 at 7:55 PM, anthony shaw wrote: > This is the third 2.x release, containing minor improvements as well as bug > fixes for 2.1 > > A new -tentative tag is committed and can be found at > https://git-wip-us.apache.org/repos/asf?p=libcloud.gi

Re: [dev] [VOTE] Release Apache Libcloud 2.1.0

Ran through tests, verified checksums. LGTM. [+1] Release Apache Libcloud 2.1.0 Thanks for pushing out a new release Ant. On Mon, Jul 10, 2017 at 10:58 AM, anthony shaw wrote: > This is the second 2.x release, containing major improvements as well as > bug fixes for 2.0 > > A new -tentative

Re: [dev] [DISCUSS] libcloud 2.1

I'm in favor of 2.1 (pending any work Tomaz brought up for lxml). On Tue, Jun 27, 2017 at 6:32 AM, Tomaz Muraus wrote: > Sorry for a late response. > > I would be curious to know a bit more about the lxml issue (sorry if I > missed a Github issue or similar, feel free to point me to it). > > I d

Re: [dev] GCE compute driver cannot create volume at a given location

om/apache/libcloud/pull/1048 > > Best, > -- > Francisco J. Ros > > > El 27 abr 2017, a las 19:03, Eric Johnson > escribió: > > > > Hi Francisco, > > > > I agree with you that #2 would be best. I would assume most client code > was > > written ba

Re: [dev] GCE compute driver cannot create volume at a given location

Hi Francisco, I agree with you that #2 would be best. I would assume most client code was written based off the docs, so we should make sure it's supported with the code. Especially since it used to work that way. And thanks for the quick fix in #1046 too! Thank you, Eric On Thu, Apr 27, 2017 a

Re: [dev] Testing

Nice! Looks a lot simpler to maintain too. [+1] for pytest Thanks Ant! On Sun, Apr 23, 2017 at 7:32 PM, anthony shaw wrote: > Hi, > > I've just raised a PR to exchange unittest2 runner for PyTest in TOX. > Reasons why are mainly after making so many changes to the base code and > having to fi

Re: [dev] [VOTE] Release Apache Libcloud 2.0.0

Checked the .tar.gz with checksums and ran the GCE demo script. Locally the python envs passed but lint isn't happy. Just a few minor tweaks to get it passing though, """ libcloud/test/secrets.py:31:19: E225 missing whitespace around operator ERROR: InvocationError: '/tmp/apache-libcloud-2.0.0/.t

Re: [dev] [VOTE] Release Apache Libcloud 2.0.0rc2 - 2

Ran tests with 2.7, 3.6, verified checksums. Also tested GCE with 2.7 and 3.6. [+1] Release Apache Libcloud 2.0.0rc2 Thanks for all the hard work Anthony! On Fri, Apr 7, 2017 at 5:02 AM, anthony shaw wrote: > Thanks Tomaz > > We need a couple more PMC votes to make this binding. Eric, Seb, Al

Re: [dev] [DISCUSS] Python 3.6 support

Switching to 3.6 now and putting on my grumpy hat in case anger is really needed. On Tue, Dec 27, 2016 at 2:22 PM, Tomaz Muraus wrote: > Sounds good to me :) > > On Dec 27, 2016 9:33 PM, "anthony shaw" wrote: > > I just merged a PR to add Python 3.6.0 to the build, now that it's > released. The

Re: [dev] [VOTE] Release Apache Libcloud 1.5.0

[+1] Release Apache Libcloud 1.5.0 On Tue, Dec 27, 2016 at 12:54 AM, anthony shaw wrote: > This is a voting thread for Libcloud 1.5.0. > > A new -tentative tag is committed and can be found at > https://git-wip-us.apache.org/repos/asf?p=libcloud.git;a= > tag;h=refs/tags/v1.5.0-tentative > > A f

Re: [dev] [DISCUSSION] Need more help please!

Likewise. Tom, let's coordinate on the open GCE issues/PRs. On Mon, Dec 12, 2016 at 9:03 PM, Tom Melendez wrote: > I'll certainly pitch in. The GCE-specific PRs were on my todo list anyway. > :-) > > Thanks, > > Tom > > On Mon, Dec 12, 2016 at 8:52 PM, anthony shaw > wrote: > > > Hi, > > > > N

Re: [dev] [VOTE] Release Apache Libcloud 1.4.0 (2nd vote)

[+1] Release Apache Libcloud 1.4.0 Verified checksums, ran tox, ran the GCE demo and all looks good to me. Thanks Anthony! On Sun, Nov 20, 2016 at 7:45 PM, anthony shaw wrote: > This is a voting thread for Libcloud 1.4.0. > > This thread replaces the previous thread and corrects: > - Broken bu

Re: [dev] Merge process

Yup. Creature of habit and back in the day Tomaz preferred single commits. On Thu, Oct 13, 2016 at 2:49 PM, anthony shaw wrote: > My question was more why do you need to rebase at all? Just to squash > the commits for the PR? > > On Fri, Oct 14, 2016 at 8:48 AM, Eric Johnson >

Re: [dev] Merge process

e branch > > On Fri, Oct 14, 2016 at 8:43 AM, Eric Johnson > wrote: > > No, on rebase, your commit just disappeared! > > > > On Thu, Oct 13, 2016 at 2:41 PM, anthony shaw > > wrote: > > > >> "hard time merging"? let me guess, "patch doe

Re: [dev] Merge process

No, on rebase, your commit just disappeared! On Thu, Oct 13, 2016 at 2:41 PM, anthony shaw wrote: > "hard time merging"? let me guess, "patch does not apply"? This is my > favourite error, so much so it's like a close family member. > > > On Fri, Oct

Re: [dev] Merge process

Yup, I kicked the can down the road. My next merge for #901 had the same issue. On Thu, Oct 13, 2016 at 8:19 AM, Eric Johnson wrote: > Not sure if this related, but I had a hard time merging #856 in this > morning. I was following my normal procedure using git-am, updating > CHANGES.

Re: [dev] Merge process

Not sure if this related, but I had a hard time merging #856 in this morning. I was following my normal procedure using git-am, updating CHANGES.rst, then rebasing to squash into a single commit. Prior to rebase, I'd see 065d1919d8cd1e651b92af6220b1408437b07563 in my git-log. During rebase -i, I w

Re: [dev] [VOTE] Release apache libcloud 1.3.0

[+1] Release Apache Libcloud 1.3.0 Thanks for this Anthony! Looks like Hacktoberfest as a huge success. On Mon, Oct 10, 2016 at 6:53 AM, Jerry Chen wrote: > [+1] Release Apache Libcloud 1.3.0 > > > On Oct 10, 2016, at 4:59 AM, anthony shaw > wrote: > > > > This is a voting thread for Libcloud

Re: [dev] Merge process

I agree that git-am can be a pain. What I like about using it though, is that history is more forthcoming about original author versus us showing up all the time. """ commit 065d1919d8cd1e651b92af6220b1408437b07563 Merge: 4897933 0d1a9d2 Author: Anthony Shaw Date: Wed Oct 12 09:41:47 2016 +110

Re: [dev] [VOTE] RELEASE APACHE LIBCLOUD 1.2.1

[+1] Release Apache Libcloud 1.2.1 Tested and all looks good afict, thanks for working through this Anthony! On Mon, Sep 19, 2016 at 11:45 PM, anthony shaw wrote: > This is a voting thread for Libcloud 1.2.1. > > If you were following the thread regarding 1.2.0, because of a > breaking change t

Re: [dev] [VOTE] RELEASE APACHE LIBCLOUD 1.2.0

[+1] Release Apache Libcloud 1.2.0 Using the .tar.gz, I verified sig and sums, ran tox, and (of course) ran the GCE live tests and it all looks good. Ship it! :) On Sun, Sep 11, 2016 at 3:56 AM, anthony shaw wrote: > This is a voting thread for Libcloud 1.2.0. > > A new -tentative tag is commi

Re: [dev] Re: Native JSON support for Storage

Hi Naveen, Apologies for the late response. Generally, it's preferred not to pull in extra deps and especially if it's only useful for a single cloud provider. Sorry again for the late reply! Cheers, Eric On Wed, Jul 13, 2016 at 11:28 AM, Naveen Kalla wrote: > Hi libclould maintainers, > > I

Re: [dev] Re: lazy entry

+1 - added a comment about updating docs down the road On Sat, Jul 2, 2016 at 7:13 AM, Tom Melendez wrote: > LGTM! > On Jul 2, 2016 3:30 AM, "Anthony Shaw" wrote: > > > If nobody has any particular objection I will pull this change in for the > > next version. > > > > On 26/06/2016, 9:30 AM, "a

Re: [dev] Coveralls support in repo

Outstanding! On Sun, Jun 26, 2016 at 3:13 AM, Tomaz Muraus wrote: > Nice :thumbsup: > > We used to run coverage.py and upload reports to Apache build servers, but > this hasn't been running for a while now and it was kinda pain to maintain > so I'm all for outsourcing it to a 3rd party service :

Re: [dev] [VOTE] Release Apache Libcloud 1.0.0 (new thread)

Now from my apache.org addy. Not sure this qualifies as PROMPT, but nonetheless... [+1] Release Apache Libcloud 1.0.0 Awesome work folks, glad to see this day! On Thu, Jun 16, 2016 at 11:52 PM, anthony shaw wrote: > This is a voting thread for Libcloud 1.0.0. > > This supersedes the previous

Re: [dev] [VOTE] Release Apache Libcloud 1.0.0 (new thread)

Not sure this qualifies as PROMPT, but nonetheless... [+1] Release Apache Libcloud 1.0.0 Awesome work folks, glad to see this day! On Thu, Jun 16, 2016 at 11:52 PM, anthony shaw wrote: > This is a voting thread for Libcloud 1.0.0. > > This supersedes the previous vote thread, note that 2 addi

Re: [dev] R1.0.0

Sounds good to me! On Wed, Jun 8, 2016 at 11:42 AM, Tomaz Muraus wrote: > Let's do it! > > But before hand, let's please get the actual press release and announcement > ready. > > We need to give Sally enough time (2 weeks or more) once we have the > announcement ready, so she can prepare everyt

Re: [dev] line endings

Maybe this is something we can set in the repo with .gitattributes? https://help.github.com/articles/dealing-with-line-endings/#per-repository-settings. Seems to be a git thing, so maybe Apache infra will honor it too. Barring that, I like the idea of catching it in lint and even documenting the c

Re: [dev] [VOTE] Release Apache libcloud 1.0.0-rc2

Looks good Mr. Shaw, [+1] Release Apache Libcloud 1.0.0-rc2 On Sat, Apr 9, 2016 at 11:01 PM, Allard Hoeve wrote: > Hey. Have been out of the loop for a while. I abstain. > > Allard > > On Sun, Apr 10, 2016, 07:45 anthony shaw wrote: > > > [+1] Release Apache Libcloud 1.0.0-rc2 > > > > Seb, A

Re: [dev] Deprecated providers in 1.0

Looks great Anthony. On Thu, Feb 11, 2016 at 10:07 PM, anthony shaw wrote: > Hi, > > I've identified 5 of our current compute drivers that are no longer > 'alive' and written a blog post about it to notify the users. > > http://libcloud.apache.org/blog/2016/02/16/new-drivers-deprecated-drivers.h

Re: [dev] Re: Apache Libcloud "road to 1.0"

Agree that this is an awesome idea. I also like the idea of a larger set of contributors on the back of the shirt. Maybe to be fair, go with the top 50 contributors , or anyone with 5+ commits. I'm also happy to dig up some sponsorship fundi

Re: [dev] [VOTE] Release Apache Libcloud 1.0.0-pre1

[+1] Release Apache Libcloud 1.0.0-pre1 On Mon, Jan 25, 2016 at 12:33 PM, Greg Hill wrote: > Thanks for the clarification! > > Greg > > On 1/25/16, 2:02 PM, "anthony shaw" wrote: > > >the tag doesn't get created until the release has been voted on. I use > >a "tentative" tag to refer to the co

[dev] [ANNOUNCE] Apache libcloud 0.20.1 release

Libcloud is a Python library that abstracts away the differences among multiple cloud provider APIs. It allows users to manage cloud services (servers, storage, loadbalancers, DNS) offered by many different providers through a single, unified and easy to use API. We are pleased to announce the rel

Re: [dev] [VOTE] Release Apache Libcloud 0.20.1

ase apache libcloud 0.20.1 > > > > On 16 Jan 2016, at 10:58, Tomaz Muraus wrote: > > > > [+1] Release Apache Libcloud 0.20.1 > > > > On Fri, Jan 15, 2016 at 8:38 PM, Eric Johnson > > wrote: > > > >> Ok, CHANGES.rst fixed. > >>

Re: [dev] [VOTE] Release Apache Libcloud 0.20.1

make sure the underline matches the title length (0.20.0 didn't > have that, but it's fixed in trunk and we now have strict checking > enabled). > > On Fri, Jan 15, 2016 at 8:10 PM, Eric Johnson > > wrote: > > > Good catch! > > > > While cherry-picki

Re: [dev] [VOTE] Release Apache Libcloud 0.20.1

Fri, Jan 15, 2016 at 5:07 PM, Eric Johnson wrote: > > > This is a voting thread for Libcloud 0.20.1. > > > > This is a bugfix release. It consists of the following cherry-picked > > changes in trunk applied to the 0.20.0 release ( > > 4087f45504f7c3bbd0f389420e9ec

[dev] [VOTE] Release Apache Libcloud 0.20.1

This is a voting thread for Libcloud 0.20.1. This is a bugfix release. It consists of the following cherry-picked changes in trunk applied to the 0.20.0 release ( 4087f45504f7c3bbd0f389420e9ecbdedf93ded9): 88170f6582dd6cc3bce87c0ab3a89118551fe508 - Allow for old and new style service account cl

Re: [dev] Bug in Libcloud 0.20.0 GCE driver?

give others a chance to provide input on other cherry picks. On Thu, Jan 14, 2016 at 9:43 AM, Eric Johnson wrote: > Great. I'll skim over the log looking for bug fixes, but if anyone knows > of any, please flag them for me. :) > > On Thu, Jan 14, 2016 at 9:41 AM, Tomaz Muraus w

Re: [dev] Bug in Libcloud 0.20.0 GCE driver?

s usual. > > If there are any other bug fixes in trunk worth picking, we should also > include those. > > On Thu, Jan 14, 2016 at 6:35 PM, Eric Johnson > > wrote: > > > Ok, pretty sure this is the problem. > > > > Can you sanity check my process for creating

Re: [dev] Bug in Libcloud 0.20.0 GCE driver?

thread Sound ok? On Wed, Jan 13, 2016 at 5:30 AM, Tomaz Muraus wrote: > Yeah, need to spin up voting thread and follow the usual release process. > > Each release artifacts need to be trackable back to the git repo SHA, etc. > > On Wed, Jan 13, 2016 at 2:06 PM, Eric Johnson >

Re: [dev] Bug in Libcloud 0.20.0 GCE driver?

Hi Tomaz, I'll look more closely but I suspect the problem is that Google changed the client id address format (and that is fixed in trunk). Do I need to spin up a vote thread to pull in that single fix? Thanks for flagging this! Eric On Jan 13, 2016 12:52 AM, "Tomaz Muraus" wrote: > Hey Eric,

Re: [dev] [DISCUSS] Was: [VOTE] Development options for container support

+1 to #3 On Thu, Dec 17, 2015 at 8:31 AM, wrote: > Hi Sebastien, all, > > This would be a great development - good to see :) > > I agree option 3) looks the best. > > > > > It makes sense if we think that various API are going to emerge for > containers. In libcloud philosophy, we would provide

Re: [dev] Release Apache Libcloud 0.20.0

[+1] Release Apache Libcloud 0.20.0 Signatures match, tox tests pass, GCE driver live tests pass. On Fri, Dec 11, 2015 at 1:05 AM, anthony shaw wrote: > yes new features, 2 new DNS drivers (godaddy and cloudflare). Support for > RackSpace reverse DNS. Some massive updates to the dimension data

Re: [dev] Google Storage tests really slow?

30, 2015 at 11:52 AM, Scott Crunkleton wrote: > Hmm, that is really weird. I noticed that the GCS tests took a moment, but > no longer than ~5-10 secs. > > On Mon, Nov 30, 2015 at 11:46 AM, Scott Crunkleton > wrote: > >> Is there an issue tracking this in Jira? >>

Re: [dev] Google Storage tests really slow?

+scott since he was recently doing some work on the GCS driver. On Mon, Nov 30, 2015 at 10:05 AM, Greg Hill wrote: > Is this a known issue? The google storage tests take a really really long > time to complete. Are they waiting on a timeout or something? > > Greg > >

Re: [dev] Cleanup PRs

Formatting of the email was a bit hard to parse and I'm not sure how well an in-line reply will look. So, rather than one-off a few here or there, put me down for 100% agreement with Tony's votes. On Mon, Nov 23, 2015 at 1:36 AM, anthony shaw wrote: > Shouldn't be too contraversial, here is the

[dev] [ANNOUNCE] Apache Libcloud 0.19.0 release

Libcloud is a Python library that abstracts away the differences among multiple cloud provider APIs. It allows users to manage cloud services (servers, storage, load balancers, DNS) offered by many different providers through a single, unified and easy to use API. We are pleased to announce the re

Re: [dev] [VOTE] Release Apache Libcloud 0.19.0

Oct 28, 2015 at 4:26 AM, Sebastien Goasguen > > wrote: > > > >> give me couple hours, just back from two days off-line > >> > >>> On Oct 27, 2015, at 5:20 PM, Eric Johnson wrote: > >>> > >>> Reminder: vote thread is targeted to close t

Re: [dev] [VOTE] Release Apache Libcloud 0.19.0

gt; > Thanks. > > Also to clarify it - the difference between this and now closed proposed > 0.19.0 release is that this one includes a fix for a bug in the Dimension > Data driver. > > On Thu, Oct 22, 2015 at 3:22 PM, Eric Johnson wrote: > > > Note: past vote thread was clo

[dev] [VOTE] Release Apache Libcloud 0.19.0

Note: past vote thread was closed, this thread replaces it. This is a voting thread for Libcloud 0.19.0. This release contains numerous new features, improvements and bug fixes. The full change log can be found at https://git-wip-us.apache.org/repos/asf?p=libcloud.git;a=blob;f=CHANGES.rst;h=75342

Re: [dev] [VOTE] Release Apache Libcloud 0.19.0

message is formatted correctly. > > I can update the tests so they check the XML element names, but not match > the entire payload because the tests will be too fragile. I can do this > tomorrow. > > Ant > > On Tue, Oct 20, 2015 at 9:29 AM, Eric Johnson > > wrote:

[dev] [VOTE] Release Apache Libcloud 0.19.0

This is a voting thread for Libcloud 0.19.0. This release contains numerous new features, improvements and bug fixes. The full change log can be found at https://git-wip-us.apache.org/repos/asf?p=libcloud.git;a=blob;f=CHANGES.rst;h=e1a9b3dd3088797956c4d5b025084df15e3a8bca;hb=fccf348234ed77ac1fad2a

Re: [dev] List of issues for 0.18.1?

the KEYS file so you can start > working on a release. Both Sebastien and I can lend a hand if needed... > > On Tue, Sep 22, 2015 at 11:58 AM, Sebastien Goasguen > wrote: > > > > > > On Sep 21, 2015, at 10:59 PM, Eric Johnson > > > wrote: > > >

[dev] List of issues for 0.18.1?

Hi folks, On the off chance we're collecting a set of issues for 0.18.1, I wanted to add another to the list. Looks like Google is deprecating their 'v1beta1' DNS API this Friday. Thanks to a colleague for noticing and sending in a PR, I just merged #583

Re: [dev] [VOTE] Release Apache Libcloud 0.18.0

Thanks for getting this ready Tomaz. I ran standard tests and also ran live tests against GCE and it all checks out. [+1] Release Apache Libcloud 0.18.0 On Sat, Aug 8, 2015 at 3:20 PM, Tomaz Muraus wrote: > This is a voting thread for 0.18.0 release (yay, finally!). > > This release contains n

Re: [dev] help with pending PR

I'm working my way through the backlog of GCE PRs. I merged a couple, but it looks like mirroring to GitHub is lagging and ASFbot isn't closing the GitHub PRs. On Sun, Jul 5, 2015 at 2:08 AM, Tomaz Muraus wrote: > Only a couple of those PRs are still relevant / active. > > Some of those PRs are

Re: [dev] 0.17.0 Bug (fixed in trunk) in GCE driver, saltstack broken

op of that branch and base 0.17.1 > release from that branch. > > On Sat, Feb 28, 2015 at 7:57 PM, Eric Johnson wrote: > > > On Sat, Feb 28, 2015 at 10:27 AM, sebgoa wrote: > > > > > > > > On Feb 28, 2015, at 6:45 PM, Eric Johnson wrote: >

Re: [dev] 0.17.0 Bug (fixed in trunk) in GCE driver, saltstack broken

On Sat, Feb 28, 2015 at 10:27 AM, sebgoa wrote: > > On Feb 28, 2015, at 6:45 PM, Eric Johnson wrote: > > > It looks like https://github.com/apache/libcloud/pull/448 was worse > than I > > thought. I'm updating Saltstack (built on libcloud) and salt is broken > wi

[dev] 0.17.0 Bug (fixed in trunk) in GCE driver, saltstack broken

It looks like https://github.com/apache/libcloud/pull/448 was worse than I thought. I'm updating Saltstack (built on libcloud) and salt is broken with 0.17.0 because of the bug, preventing users from creating GCE VMs. I wanted to raise awareness that if we're accumulating reasons for a bug fix rel

Re: [dev] [VOTE] Release Apache Libcloud 0.17.0

On Mon, Feb 16, 2015 at 12:51 PM, Tomaz Muraus wrote: > On Mon, Feb 16, 2015 at 8:57 PM, sebgoa wrote: > > > > > On Feb 16, 2015, at 8:30 PM, Tomaz Muraus wrote: > > > > > Explicit +1 from me. > > > > > > [+1] Release Apache Libcloud 0.17.0 > > > > > > This brings the totals to: > > > > > > +1'

Re: [dev] [VOTE] Release Apache Libcloud 0.17.0

[+1] Release Apache Libcloud 0.17.0 On Sat, Feb 7, 2015 at 2:55 PM, Tomaz Muraus wrote: > This is a voting thread for 0.17.0 release. > > This release contains numerous new features, improvements and bug fixes. > > Full change log can be found at > > https://git-wip-us.apache.org/repos/asf?p=lib

Re: [dev] Any thoughts on 0.17.0?

zero hurt feelings). :) Thank you, Eric On Tue, Jan 27, 2015 at 3:47 PM, Eric Johnson wrote: > Ok, added my key. > > On Tue, Jan 27, 2015 at 1:48 PM, Tomaz Muraus wrote: > >> In the mean time, please also make sure your GPG key is present in our >> keys >> file: &g

[dev] Fwd: Analyst Request for ASF Cloud Computing roadmap

FYI - in case nobody caught this. Does libcloud typically participate in these requests? I think it would be good visibility for libcloud. -- Forwarded message -- From: Sally Khudairi Date: Fri, Jan 30, 2015 at 12:21 PM Subject: Re: Analyst Request for ASF Cloud Computing roadma

Re: [dev] Any thoughts on 0.17.0?

-signing.html#keys-policy > > On Tue, Jan 27, 2015 at 5:38 PM, Eric Johnson wrote: > > > On Tue, Jan 27, 2015 at 8:16 AM, Tomaz Muraus wrote: > > > > > On Tue, Jan 27, 2015 at 3:59 PM, Eric Johnson > > wrote: > > > > > > > Hi all, > >

Re: [dev] Any thoughts on 0.17.0?

On Tue, Jan 27, 2015 at 8:16 AM, Tomaz Muraus wrote: > On Tue, Jan 27, 2015 at 3:59 PM, Eric Johnson wrote: > > > Hi all, > > > > To be completely transparent, I've thrown a lot of new code into the GCE > > driver post 0.16 and would like to see 0.17 go out s

[dev] Any thoughts on 0.17.0?

Hi all, To be completely transparent, I've thrown a lot of new code into the GCE driver post 0.16 and would like to see 0.17 go out soon(ish). I've built SaltStack and Ansible support for GCE on top of libcloud, and I'd like to roll out the new GCE goodness to those communities too. Do we have a

Re: [dev] Jira fields

field is reasonable though > > > > I will have a look at adding a new field for that - last time I had a > look > > (over a year ago) it was locked and projects couldn't use custom fields, > > but this might have changed since then. > > > > On Fri, Dec

[dev] Jira fields

Hi all, I'd like to have a better way of triaging / finding Jira issues. What do you think about introducing a "provider" custom field and surfacing that in the "New/Edit Issue" flow? For now and I"m trying to use "Lables", but it's not part of the create/edit flow. I've bulk-edited the GCE issue

Re: [dev] Discussion: changing a function's parameter, backwards compatability

ke option 1 as well. Option 2 would mean adding a third None-defaulted > parameter for targethttpproxy. Option 3 seems crufty. > On Wed Nov 19 2014 at 6:39:48 AM Eric Johnson wrote: > > > Hi folks, > > > > I'm working on the GCE driver and since this was first adde

[dev] Discussion: changing a function's parameter, backwards compatability

Hi folks, I'm working on the GCE driver and since this was first added to libcloud, Google has made a change to the load-balancing 'forwarding rule'. When first introduced the only option for traffic forwarding was to a 'targetpool'. However, there is now an option to send traffic to a 'targetinst

Re: [dev] GCE Improvements

Great, thanks Tomaz On Fri Nov 14 2014 at 6:48:41 AM Tomaz Muraus wrote: > Just pull requests (no JIRA) issues are fine :) > On Nov 14, 2014 9:05 PM, "Eric Johnson" wrote: > > > Hi folks, > > > > Over the next month(ish), I'm planning on adding a

[dev] GCE Improvements

Hi folks, Over the next month(ish), I'm planning on adding a lot of incremental improvements to the Google Compute Engine driver to improve overall API coverage. Would you prefer I create a Jira issues for each pull-request, or are you OK without corresponding Jira issues? Thank you, Eric

  1   2   >