Hi Shane
I’m a member of the Libcloud PMC and still review releases and am willing to
perform the oversight duties.
Anthony :Shaw
> On 12 Sep 2023, at 8:34 pm, Tomaz Muraus wrote:
>
> Shane,
>
> Thanks for starting a roll call.
>
> For some reason the email went into
[+1] Release Apache Libcloud 3.7.0
>
> On 3 Jan 2023, at 6:31 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
>
ed anymore and we can utilize native syntax).
>>
>> --- Original Message ---
>> On Thursday, September 8th, 2022 at 11:26 PM, anthony shaw
>> anthony.p.s...@gmail.com wrote:
>>
>>
>>
>>> +1
>>>
>>> Makes sense
>
+1
Makes sense
Pip is smart enough to resolve an older version for 3.6 users.
We can also use this to update syntax for 3.7
https://github.com/asottile/pyupgrade
Anthony
>
> On 8 Sep 2022, at 10:11 pm, Eric Johnson wrote:
>
> On Thu, Sep 8, 2022 at 3:35 AM Tomaz Muraus wrote:
>
>>
Nice work. Thanks Tomaz
>
> On 31 Mar 2022, at 10:11 am, Tomaz Muraus wrote:
>
> And it's live -
> https://libcloud.apache.org/blog/2022/03/30/website-updates.html
>
> --- Original Message ---
>
>> On Wednesday, March 30th, 2022 at 12:05 AM, Tomaz Muraus
>> wrote:
>>
>> After
[+1] Release Apache Libcloud 3.4.0
Thanks Miguel Caballer and Veith Röthlingshöfer for all your contributions on
this release
>
> On 8 Nov 2021, at 6:26 am, Tomaz Muraus wrote:
>
> [ ] Release Apache Libcloud 3.4.0
as passed.
>
> I will publish the release artifacts shortly.
>
> Thanks to everyone for their votes.
>
> ‐‐‐ Original Message ‐‐‐
>
> On Tuesday, December 29th, 2020 at 11:04 PM, Jerry Chen
> wrote:
>
> > [+1] Release Apache Libcloud 3.3.0
> &g
[+1] Release Apache Libcloud 3.3.0
On Mon, Dec 28, 2020 at 9:11 AM Tomaz Muraus wrote:
> This is a voting thread for Libcloud v3.3.0 (
> https://github.com/apache/libcloud/commit/6b588346083a510396c63b5d18db3012aa083071
> )
>
> Changelog can be found at
>
[+1] Release Apache Libcloud 3.2.0
On Mon, Sep 14, 2020 at 6:29 PM Tomaz Muraus wrote:
> Bump, we still don't have enough votes
>
> On Sun, 30 Aug 2020, 23:21 Tomaz Muraus wrote:
>
> > This is a voting thread for Libcloud v3.2.0 (
> >
>
Python 2 urllib module) a few years
ago, and there are lots of edge cases.
Regards,
Anthony Shaw
On Tue, Sep 1, 2020 at 6:32 AM Michael Spagon wrote:
> Hi,
>
> We are seeing HTTP 400 errors in our OpenStack server logs: ERROR WSGI:
> code 400, Bad request syntax ('0'). They appear
[+1] Release Apache Libcloud 3.1.0
Sent from my iPhone
> On 7 Jun 2020, at 8:14 am, Tomaz Muraus wrote:
>
> [ ] Release Apache Libcloud 3.1.0
Done! https://anaconda.org/conda-forge/apache-libcloud
On Thu, Apr 16, 2020 at 8:46 PM anthony shaw
wrote:
> https://github.com/conda-forge/apache-libcloud-feedstock/pull/24
>
> will get this onto conda forge shortly
>
> On Thu, Apr 16, 2020 at 6:13 AM Tomaz Muraus wrote
[+1] Release Apache Libcloud 2.8.1
Sent from my iPhone
> On 1 Mar 2020, at 9:15 am, 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
>
I know I'm late, but
[+1] Release Apache Libcloud 3.0.0rc1
Also, we need to document workarounds for pysphere if this hasn't been done
already
On Thu, Jan 30, 2020 at 12:13 AM Tomaz Muraus wrote:
> Explicit +1 from me.
>
> [+1] Release Apache Libcloud 3.0.0rc1
>
> This brings total to 3 +1's
[ +1] Release Apache Libcloud 2.8.0
Also recommend we branch this off to a 2.x branch and start working on
master as the 3.x series
On Tue, Dec 24, 2019 at 8:01 AM Tomaz Muraus wrote:
> This is a voting thread for Libcloud v2.8.0.
>
> This release includes various changes, most notable ones
[+1] Release Apache Libcloud 2.7.0
Sent from my iPhone
> On 6 Dec 2019, at 7:11 am, Jerry Chen wrote:
>
> [+1] Release Apache Libcloud 2.7.0
+1 no objections, surprised this wasn't already in the spec!
On Wed, Nov 27, 2019 at 1:59 PM Eric Johnson wrote:
> +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
users on each version of Python. Maybe an updated chart will help convince
> the community here?
>
> Samuel Marks
> http://linkedin.com/in/samuelmarks
>
>
> On Thu, Nov 21, 2019 at 10:17 PM anthony shaw
> wrote:
>
> > Considering libcloud has had the Metadata 1.2 ta
a 'critical fix only'
branch.
Another consideration in the future would be the async support for the API,
which attempts to do have stalled because we have to support Python 2 and
3.4.
Anthony Shaw
--
*From:* Tomaz Muraus
*Sent:* Wednesday, November 20, 2019 7:18 pm
[ +1] Release Apache Libcloud 2.6.0
Looks great. Thanks Tomaz
Anthony Shaw
From: Tomaz Muraus
Sent: Sunday, August 25, 2019 5:14 am
To: dev@libcloud.apache.org
Subject: [dev] [VOTE] Release Apache Libcloud 2.6.0
This is a voting thread for Libcloud 2.6.0
It looks really similar to Azure Pipelines (and the syntax looks similar)..
Makes you wonder if its the same platform?
Anyway, I'm not tied to Travis CI. It's been stable, but we only test on
Linux.
There would be benefits to having a consolidated Windows/Linux testing
matrix.
In some of my
[ +1] Release Apache Libcloud 2.5.0
On Wed, May 29, 2019 at 7:00 AM Tomaz Muraus wrote:
> This is a voting thread for Libcloud 2.5.0. It includes all the
> changes from trunk which have landed there since v2.4.0.
>
> It has been almost 8 months since the last release so a lot
> of changes have
Hooray!! No more git-am merge errors.
On Thu, Jan 17, 2019 at 5:26 AM Tomaz Muraus wrote:
> Dear Libcloud users and developers,
>
> Our Liblcoud Git repository has moved. New URI / location is
> http://gitbox.apache.org/repos/asf/libcloud.git (I will update the website
> with this information
I'm not seeing the rebase commits? Are they in the same PR?
On Mon, Apr 16, 2018 at 5:34 PM, Samuel Marks wrote:
> Rebased. The goal is to replace the first 3 CLI commands that require the
> Azure client installed, with Apache Libcloud code:
>
Hi Everyone
I’ll be at PyCon US and have some time on the Monday.
Would anyone be interested in joining me for a sprint on Libcloud 3 design
principles and prototypes based on the last discussion thread?
Regards
Anthony Shaw aka @tonybaloney
Wow, that's a serious thread! I hope you're coming to PyCon Quentin. I'll
be there and hard to miss (I carry a 6ft "Python Staff")
I happened to bump into both Cory Benfield and Kenneth and picked their
brains on some of the thinking for requests 3.0.
The design in my email is going to take a
loud more attractive to providers
> > wanting to> write a python sdk?
> >
> > One idea I had a long time ago was to see how well the botocore data
> > driven model could extend to other providers. I don’t really think we>
> have the resources to do this. But the thinkin
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
More votes please everyone.
On Tue, 27 Feb 2018 at 4:27 pm, Quentin Pradet
wrote:
> Thanks! The md5 and sha1 now match.
>
> [+1] Release Apache Libcloud 2.3.0
>
Anyway,
it's a yes vote from me
[+1] Release Apache Libcloud 2.3.0
On Mon, Feb 26, 2018 at 3:58 PM, anthony shaw <anthony.p.s...@gmail.com>
wrote:
> Try again, just reuploaded them I was on a dodgy connection at the time.
>
> On Sun, Feb 25, 2018 at 10:17 PM, Quenti
Try again, just reuploaded them I was on a dodgy connection at the time.
On Sun, Feb 25, 2018 at 10:17 PM, Quentin Pradet
wrote:
> Thanks Anthony.
>
> For some reason it looks like the zip and whl file are invalid: they are
> smaller than the previous version and not
y understanding is that we need to generate new release artifacts. Can
> > anyone confirm?
> >
> > On Wed, Feb 21, 2018 at 9:23 PM, Allard Hoeve <allardho...@gmail.com>
> > wrote:
> >
> > > [+1] Release Apache Libcloud 2.3.0
> > >
> > >
This is a voting thread for Libcloud 2.3.0. It includes all the changes
from trunk which have landed there since v2.2.1.
Most notable changes is the dropping of support for Python 2.6 and 3.3,
both of which are unsupported distributions.
There are new drivers for UpCloud, Digital Ocean Spaces,
Since this recently came up, here is the Python version used in downloading
libcloud in the past month.
We could almost safely deprecate 2.6 support
Row python_version download_count
1 2.7 29200
2 null 8670
3 3.5 3836
4 3.6 1804
5 3.4 856
6 2.6 490
7 1.17 93
8 3.3 21
I can never get it to build and I've broken the SVN tree 3 times now.
Anyone wanting to take this process on in future is more than welcome! :)
On Wed, Sep 20, 2017 at 9:19 AM, Tomaz Muraus wrote:
> I noticed our website is missing a release announcement blog post for
> v2.1.0
@apache.org> wrote:
>
> > [+1] Release Apache Libcloud 2.2.0
> >
> > On Mon, Aug 28, 2017 at 7:55 PM, anthony shaw <anthonys...@apache.org>
> > wrote:
> >
> > > This is the third 2.x release, containing minor improvements as well as
> > bug
> &g
Your votes please everyone.
The issue mentioned by Quentin can be resolved and released in 2.2.1 within
a couple of days. It's not blocking afaik
I'm keen to push this fix out
https://issues.apache.org/jira/browse/LIBCLOUD-875 as I know it's blocking
users.
[+1] Release Apache Libcloud 2.2.0
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.git;a=tree;hb=7c841938a191959ce926f81a3f6177df28d4682f
A full list of changes can be found at:
If you want some advice from someone that's written ~10 drivers..
Start with the tests, fixtures and mocks, then build out the methods.
TDD saves so much time going back and forth. Also once you have the test setup
you can use PyTest with the --pdb flag.
Anthony Shaw
Hi,
I wouldn't use that one as an example. Vultr is one of the most minimal and
clean implementations
https://github.com/apache/libcloud/blob/trunk/libcloud/compute/drivers/vultr.py
Start with the basics, raise a PR and I'll walk you through the process and
steps. Oh and write lots of tests :0)
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
LGTM based on some quick testing.
>
> It would be great if we could get that those fixed (small things, but make
> UX a lot better), but not a blocker for the release.
>
> Thanks to everyone for their contributions and Anthony for his work on the
> release.
>
> [+1] Release Apache Li
, if this release introduces a bug
that you found, raise it and we'll discuss.
Regards
Anthony Shaw
_
From: Francisco Javier Ros Muñoz <fj...@doalitic.com<mailto:fj...@doalitic.com>>
Sent: Tuesday, July 11, 2017 6:44 pm
Subject: Re: [dev] [VOTE] Release Apache Li
Have you seen the recently merged changes to the openstack driver Markos?
I'm still trying to clean it up, but it's going to take a while
On Tue, Jul 11, 2017 at 5:41 PM, Markos Gogoulos wrote:
> Thanks for the replies!
>
> Anthony, this method works well for other providers
This is the second 2.x release, containing major improvements as well as
bug fixes for 2.0
A new -tentative tag is committed and can be found at
https://git-wip-us.apache.org/repos/asf?p=libcloud.git;a=tree;hb=605821335f15ee9eeefee826ada55b97c4fd0065
A full list of changes can be found at:
It's been 2 months since the last release, we've had tons of PR's, lots of
bug fixes and also a new driver for Google Container Engine (exciting!)
We're slowly getting packages for RedHat, Centos, Fedora (rpm based)
updated to 2.0, some were as old as 0.20.0
merged.
I'm on a long flight tomorrow and hopefully will get some time to look
through the backlog
On Wed, May 31, 2017 at 5:44 PM, Francisco Javier Ros Muñoz <
fj...@doalitic.com> wrote:
> Hi everyone!
>
> PRs keep piling up on travis:
> https://travis-ci.org/apache/libcloud/pull_requests
>
>
Thanks for raising Francisco, I've disabled it for now.
https://github.com/apache/libcloud/commit/f3c7474b8889bbaf31ce1fb1f2f56ba5a7c9ec30
I think it's PyTest or Travis. I run the tests locally using tox -e pypypy
and it works fine.
On Tue, May 16, 2017 at 4:38 AM, Francisco Javier Ros Muñoz <
Hi,
I'm looking for information on the "python-libcloud" packages that are in
FC/RedHat/CentOS and the Ubuntu/Debian packages
Someone is maintaining libcloud in the yum sphere via the EPEL repo
Hi,
We need to address our OpenStack support, it's very far behind current
releases of OpenStack and not really usable for any release in the past 1
year. I'm looking for some volunteers who have access to a live OpenStack
system to help develop a driver
option 1:
- Upgrade the driver to Mitaka
at 8:46 PM, anthony shaw <anthonys...@apache.org>
wrote:
> Hi,
>
> I've been working over the past week to add Apache Libcloud support to the
> open-source project SaltStack. SaltStack has long been a user of Apache
> Libcloud, but it's still using 0.21 (which I'm trying to
version of SaltStack in 3-6 months time.
Regards,
Anthony Shaw, aka @tonybaloney
, Apr 25, 2017 at 7:54 AM, anthony shaw <anthony.p.s...@gmail.com>
wrote:
> I excluded integration from the package because I didn't think a regular
> user would need to use it.
>
> I would expect a regular user to run `python setup.py test` but I'll see
> what I can do next
list
> passes. I suspect re-packaging with 'integration' will make lint happy.
>
> I think both are minor, so still giving it the thumbs up.
>
> [+1] Release Apache Libcloud 2.0.0
>
>
>
> On Fri, Apr 21, 2017 at 7:44 PM, anthony shaw <anthonys...@apache.org>
> wrot
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 fight through unittest2 output reports.
https://github.com/apache/libcloud/pull/1041
Improvements would include:
The test output is so
It's a go from me
[+1] Release Apache Libcloud 2.0.0
On Sun, 23 Apr 2017 at 12:59 am, Jerry Chen <je...@apache.org> wrote:
> I emailed from my personal email; here we go instead:
>
> [+1] Release Apache Libcloud 2.0.0
>
> > On Apr 21, 2017, at 9:44 PM, anthony shaw
This is a first stable release for 2.0 and contains major changes since the
latest stable release, 1.5.0,
http://libcloud.readthedocs.io/en/latest/other/changes_in_2_0.html as well
as some bug fixes since 2.0.0rc2
A new -tentative tag is committed and can be found at
or no tests.
Anthony Shaw
From: anthony shaw <anthony.p.s...@gmail.com>
Sent: Wednesday, April 12, 2017 3:44:31 PM
To: dev
Subject: Replacing the HTTP mocks
Hi,
I mentioned this a while back, but I've gotten around to ripping out the
HTTPlib mocks that e
Hi,
I mentioned this a while back, but I've gotten around to ripping out the
HTTPlib mocks that existed in libcloud.test
why? Because they were mocks stacked on mocks, they didn't represent the
actual behaviour of the old or new system and I thought they might be
hiding some bugs.
This change
Hi,
I've pushed an explanation of 2 (unmerged) PRs and ideas for an async API
for libcloud.
http://libcloud.apache.org/blog/2017/04/09/async-rfc.html
Please provide feedback, ideas and suggestions on the mailing list.
Regards,
Anthony
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
Vote is now closed.
[+1] - 6 (4 binding)
[0] - 1
[-1] - 0
Vote has passed. This is the first 2.0 release to be released, I'll write up
the release notes, update the website and publish the packages at some point
today.
Regards
Anthony Shaw
_
From: Eric Johnson
Thanks Tomaz
We need a couple more PMC votes to make this binding. Eric, Seb, Allard, Jerry
if you have a moment please cast your votes.
Anthony Shaw
From: Tomaz Muraus <to...@apache.org>
Sent: Friday, April 7, 2017 7:36:20 PM
To: dev@libcloud.apache.org
S
> Thanks for the quick turnaround on those issues, Anthony!
>
> [+1] Release Apache Libcloud 2.0.0rc2
>
> Retested and working A-OK!
>
> Thanks,
>
> Tom
>
>
> On Thu, Apr 6, 2017 at 2:47 AM, anthony shaw <anthony.p.s...@gmail.com>
> wrote:
>
This is the 2nd voting thread for Libcloud 2.0.0rc2
The original VOTE failed, there were 2 issues raised, both of which have
been fixed and are contained in this release. To ensure everyone is testing
the correct version;
The md5 for apache-libcloud-2.0.0rc2.tar.gz is
, 2017 at 12:33 PM, anthony shaw <anthony.p.s...@gmail.com>
wrote:
> Both issues are resolved and merged. I'll start another release this arvo
> when I get some free time
>
> On Thu, Apr 6, 2017 at 11:50 AM, anthony shaw <anthony.p.s...@gmail.com>
> wrote:
>
>>
Both issues are resolved and merged. I'll start another release this arvo
when I get some free time
On Thu, Apr 6, 2017 at 11:50 AM, anthony shaw <anthony.p.s...@gmail.com>
wrote:
> that's now been fixed, the other issue someone raised is the Linode driver.
>
> Since the Linod
/libcloud/common/linode.py#L68
yuck.
The linode one needs to be fixed separately and merged into this one
https://github.com/apache/libcloud/pull/1025
Then I will have to restart the release process.
[-1] Release Apache Libcloud 2.0.0rc2
On Thu, Apr 6, 2017 at 8:39 AM, anthony shaw <anthony.
at I haven't had time to
> investigate): https://issues.apache.org/jira/browse/LIBCLOUD-910
>
> I would have to vote No until we resolve it.
>
> [-1] Release Apache Libcloud 2.0.0rc2
> * tox: OK
> * gce_demo: OK
> * export LIBCLOUD_DEBUG: not OK
>
> Thanks,
>
> Tom
>
There was a PR for that, I'll have a look.
Anthony Shaw
From: tom.melen...@gmail.com <tom.melen...@gmail.com> on behalf of Tom Melendez
<t...@supertom.com>
Sent: Thursday, April 6, 2017 2:33:48 AM
To: dev@libcloud.apache.org
Subject: Re: [dev] [V
This is a voting thread for Libcloud 2.0.0rc2
This is a release candidate for 2.0 and contains major changes since the
latest stable release, 1.5.0,
http://libcloud.readthedocs.io/en/latest/other/changes_in_2_0.html
The rc1 release did not pass, with issues on custom port propagation,
All fixed!!
https://github.com/apache/libcloud/pull/1015
We should be all clear to start a 2.0rc2 release process now.
On Sun, Apr 2, 2017 at 10:40 AM, anthony shaw <anthony.p.s...@gmail.com>
wrote:
> Ok. figured it out.
>
> In < 1.5.0 the certificate connection would
che/libcloud/pull/1015/files
More reading if you're bored :-)
https://github.com/kennethreitz/requests/blob/master/requests/packages/urllib3/util/ssl_.py
I registered for Azure as well so now I can test it properly.
On Sun, Apr 2, 2017 at 9:57 AM, anthony shaw <anthony.p.s...@gmail.com&
Just tracing this issue now, the API gives me:
http://schemas.microsoft.com/windowsazure; xmlns:i="
http://www.w3.org/2001/XMLSchema-instance;>ForbiddenErrorThe
server failed to authenticate the request. Verify that the certificate is
valid and is associated with this subscription.
with the
:50 PM, anthony shaw <anthony.p.s...@gmail.com>
wrote:
> Any luck with the debugging Markos
>
> On Thu, Mar 9, 2017 at 9:42 PM, Markos Gogoulos <mgogou...@mist.io> wrote:
>
>> Hi all,
>>
>> I'm using the latest trunk, and the OpenStack driver is not working
Any luck with the debugging Markos
On Thu, Mar 9, 2017 at 9:42 PM, Markos Gogoulos wrote:
> Hi all,
>
> I'm using the latest trunk, and the OpenStack driver is not working. I
> believe this has to do with the recent major changes on
> base.py/httplib_ssl.py , I'm trying to
Hi Everyone,
It's been a busy 2017 for me, I've been overseas for 5 weeks, in hospital
twice and just taken on the management of a large global team. I haven't
had as much time as normal to help merge changes.
I'm looking at our PR backlog and it's quite huge.
We still have some outstanding
Please can I get some people to download this PR and check it against AWS
https://github.com/apache/libcloud/pull/983
Ant
Thanks Samuel, we still have outstanding issues in that release, I think. It
just needs more integration testing to uncover all the weird edge cases
Anthony Shaw
On Sun, Feb 12, 2017 at 1:51 AM +1100, "Samuel Marks" <samuelma...@gmail.com>
wrote:
Actually scratch
Looks really similar to requests_mock, which we're using already. I just made
some notes on what it can do.
In particular our pattern for method mocks.
https://medium.com/@anthonypjshaw/c12510c30d79
Anthony Shaw
On Fri, Jan 27, 2017 at 6:15 PM +1100, "Allard Hoeve" <allardho
As part of the refactoring out the httplib package in favour of
requests (yes, we need to start another release thread) I've been
looking at removing the Mocks within libcloud.
In short, they've become a frankenstein of private members, expected
classes, monkey patching and shims.
I'm working on
Tom- your issue fixed in this PR https://github.com/apache/libcloud/pull/978
Sam- I can't figure out what is going on there. The server is giving a
404, so something in the latest code is not matching. I'll investigate
Ant
On Wed, Jan 18, 2017 at 11:22 AM, anthony shaw <anthony.p.s...@gmail.
This is a voting thread for Libcloud 2.0.0rc1. This is the first
release candidate in the 2.0.0 release series. Because of the major
change in HTTP client and the impacting changes to the driver, a major
release version increase would be appropriate.
I have written a page explaining these changes
candidate.
Thanks for your help everyone.
Anthony
On Wed, Jan 11, 2017 at 7:15 PM, anthony shaw <anthony.p.s...@gmail.com> wrote:
> Thanks,
>
> it's also worth noting that the new connection design leverages the
> requests session objects, which reuse TCP sessions betwee
. We can use this in our release process.
I've already found 3 bugs using it, including one nasty one. The
RawResponse class actually exposed the underlying httplib.HTTPResponse
class as a class property. I'm just writing a proxy class for it now.
On Tue, Jan 10, 2017 at 7:41 PM, anthony shaw
and a bunch of other bad coupling practices, so they are broken
BUT it does actually work
It's nearly there.
Ant
On Fri, Jan 6, 2017 at 7:28 AM, anthony shaw <anthony.p.s...@gmail.com> wrote:
> it's more of an existential question :-)
>
> The _upload_object method inside the libclo
using pyvmomi on
> https://github.com/vmware/pyvmomi-community-samples
>
> It doesn't contain tests, and is missing core functionality though, but
> could start as a base for a quick interaction with vSphere.
>
> Cheers
>
>
> On Wed, Jan 4, 2017 at 1:30 PM, anthony shaw <anthony.p.
to
> first roll out v2.0.0-rc1 and eventually after we are happy with the
> stability call it v2.0.0.
>
> On Wed, Jan 4, 2017 at 6:20 AM, anthony shaw <anthony.p.s...@gmail.com>
> wrote:
>
>> Hi,
>>
>> I tried doing this a year ago but put it in the 'too ha
Hi,
A user made me aware of serious issues with the vSphere driver, mainly
that it doesn't work!
There were some issues in the connection constructor, easily fixed.
But it doesn't have any tests. Whilst trying to write a test case I
quickly realised that pysphere, the library that it uses
Hi,
I tried doing this a year ago but put it in the 'too hard' bucket.
I've opened a PR (again) replacing the use of httplib with the
requests package.
The consequences are:
- Connection.conn_classes is no longer a tuple, it is
Connection.conn_class. There is no separation between a HTTP and
On Tue, Dec 27, 2016 at 12:54 AM, anthony shaw <anthonys...@apache.org>
> 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=
>> ta
che Libcloud 1.5.0
>
>> On Dec 27, 2016, at 2:54 AM, anthony shaw <anthonys...@apache.org> 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=lib
is experimental in 1.5 and then have it as supported in
1.6? What do people think?
Also, a few of us need to use 3.6 in anger and check for any issues.
Regards
Anthony Shaw
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 full list of changes can be found at:
Hi,
Now that hacktoberfest is over (phew) we still need ongoing
code-reviews for pull-requests. I'll be taking some leave over the
xmas break.
We have 10 backed up and another release due out in 1 week, some help please.
Ant
now fixed.
On Tue, Nov 15, 2016 at 5:40 PM, anthony shaw <anthony.p.s...@gmail.com> wrote:
> it's not just you. I pushed to my own fork the latest tags and travis
> spat out an error
>
> https://travis-ci.org/tonybaloney/libcloud/jobs/175936361
>
> This will
it's not just you. I pushed to my own fork the latest tags and travis
spat out an error
https://travis-ci.org/tonybaloney/libcloud/jobs/175936361
This will be a no vote (or a vote of no confidence ;-)) until the
build is fixed.
Anthony
On Tue, Nov 15, 2016 at 3:53 PM, Tom Melendez
This is a voting thread for Libcloud 1.4.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.4.0-tentative
A full list of changes can be found at:
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
<erjoh...@google.com.invalid> wrote:
> Just a creature of habit and that was how I learned to squash.
>
> On Thu, Oct 13, 2016 at 2:46 P
iginal commits as the are)
>>> - Commit(s) are signed off by the person applying the changes
>>> - We can easily add "Closed #PRNUMBER" or similar message to the commit(s)
>>> message
>>>
>>> Another option also is to try "git merge
1 - 100 of 174 matches
Mail list logo