Hi all,
I was investigating how libcloud does it's TLS, in the wake of POODLE.
Right now we're pretty much doing the whole pipeline ourselves, and I think
this is a bit unfortunate: we're a cloud abstraction library, we really
shouldn't be in the business of configuring cryptographic protocols!
L
[+1]
On Wed, Jul 2, 2014 at 3:00 PM, sebgoa wrote:
> This is a voting thread for Libcloud 0.15.1,
>
> This is primarily a bug-fix release, it fixes a possible race condition in
> the deploy_node method which would occur if the SSH key has not been
> installed yet, it also propagates an exceptio
[+1] Release Apache Libcloud 0.14.1
Alex
On Fri, Feb 7, 2014 at 10:00 AM, Tomaz Muraus wrote:
> Explicit +1 from me.
>
> [+1] Release Apache Libcloud 0.14.1
>
>
> On Thu, Feb 6, 2014 at 11:45 PM, Jerry Chen wrote:
>
> > Looks great.
> >
> > [+1] Release Apache Libcloud 0.14.1
> >
> > On Fe
Hey Chris,
I don't believe anyone is currently working on this. I'm not super familiar
with the APIs for interacting with Rackconnect, but when you send the PR
I'm happy to take a look to see if the way it's integrated looks right for
libcloud.
Alex
On Sun, Sep 1, 2013 at 10:02 AM, Chris Johnso
t deals with both use cases.
> >
> > This does come with maintainability issues though. If I had to choose
> from the other 2, I'd go with the a new top level API. This way you can
> deal with list_volumes() and juggle your way around attach/detach with
> something like v
o call into methods on the new top
> level Block Storage API
>
> Alex, since you've done this research fairly recently, what's your take on
> this?
>
> On Fri, Jun 28, 2013 at 6:23 PM, Alex Gaynor
> wrote:
>
> > That looks fine to me (I see only a few dri
PI, but
> it's pretty similar to what Alex proposed so we can probably use it as a
> good starting point.
>
> Alex - what do you think?
>
> On Thu, Jun 27, 2013 at 12:16 AM, Alex Gaynor
> wrote:
>
> > Hi all,
> >
> > I'm interested in adding block s
ndi.py#L369
> 2.
>
> https://github.com/apache/libcloud/blob/trunk/libcloud/compute/drivers/cloudstack.py#L429
>
> A couple of drivers implement read-only functionality (e.g. list_volumes)
> and a couple of other drivers implement full CRUD functionality using
> extension methods.
&
On Wed, Jun 26, 2013 at 8:01 PM, Jed Smith wrote:
> This looks great, Alex! I haven't studied intently, but I have a
> couple quick comments:
>
> Line 16: Yes, I think it should be a parameter on create_volume. That
> makes the implementation less awkward if a provider does not support
> snapshot
Hi all,
I'm interested in adding block storage support to libcloud (for the
providers that suppor it of course). To that end, I've drawn up a simple
design for the driver and related classes for the features that seem to be
supported generally (I reviewed Rackspace and Amazon).
You can find the d
10 matches
Mail list logo
