There is actually another issues which prevents local_storage tests from
running with Python 2.5 and that is "lockfile" dependency not being
available for 2.5.
Because of this we currently just skip tests under 2.5 and other versions
where lockfile dependency is not available -
https://github.com/
on 2.5 according with the *tox.ini* file:
> https://github.com/apache/libcloud/blob/trunk/tox.ini#L12
>
> If I comment that line and run the tox command again, then it skips the
> 'test_local.py' and runs properly.
>
>
> On 26 January 2013 19:02, Tomaz Muraus wrote:
&g
Hello all,
It has been a while since we released the last version in November. A bunch
of changes have piled up in trunk so I decided to create a new release
(0.12.0 - r1439036) which includes many new features, bug-fixes and
improvements. It contains everything from trunk except the "datacenter"
S.
>
> Have submitted patches for the bits that fell out.
>
> I have some vastly improved tests for ELB that im working on, but they
> won't be ready for 0.12.0.
>
> John
>
> On 27 Jan 2013, at 17:04, Jaume Devesa wrote:
>
> > And Abiquo compute driver! ;)
&g
We found some minor issues with ELB and Route53 driver so I'm closing this
voting thread.
I will roll up a new release (0.12.1) with the fixes for the previously
mentioned issues and start a new voting thread when it's ready.
On Sat, Jan 26, 2013 at 11:16 PM, Tomaz Muraus wrote:
&
Just a quick heads-up - I will be in Brussels for FOSDEM 2013 next weekend.
If you are also attending FOSDEM or want to meet up and talk about Libcloud
or other related stuff, feel free to reply to this thread.
be reviewed and checked in before the next release.
>
> Regards,
> Mahendra
>
>
> On Sun, Jan 27, 2013 at 12:46 PM, Tomaz Muraus wrote:
>
> > Hello all,
> >
> > It has been a while since we released the last version in November. A
> bunch
> > of chan
>
> I've pushed my progress so far to GitHub in the Jc2k/test-proposal branch,
> but it's very early on and i've only looked at the ELB mock so far. Next I
> will do the same for another load balancer and then merge the common tests
> together to create TestBaseLoadBalan
Can you please provide some kind of reference (API documentation, example
API response, etc.) for your reasoning?
Recently we have changed how it works, because the old approach didn't
appear to work anymore -
https://github.com/apache/libcloud/commit/f7f70a8c8a53ec6df95f12f88c9439bc02446bb2
Than
still have problems.
On Tue, Jan 29, 2013 at 12:46 PM, Bob Thompson
wrote:
> Thanks, Tomaz.
>
> I'll have to run it again to get the exact text, but the API server
> returned an error saying that vnc needed to be set to use vnc_password.
>
>
> On Mon, Jan 28, 2013 at 2:
I just want to add that I've spent quite a lot of time thinking about
adding some kind of similar functionality to Libcloud in the past.
In the end I decided it's probably better to keep this functionality
outside of Libcloud and delegate it to a library which primary goal is to
do deal with remot
I see the issue you have created, but I don't see any patch attached to it.
Can you please double check and attach patch to the issue?
Thanks
On Wed, Jan 30, 2013 at 6:09 PM, Kevin McDonald wrote:
> Attached is a a patch that leverages the SoftLayer endpoint, adds ability
> to reboot a CCI, and
wrote:
> Just sent a pull request for review.
>
> Regards,
> Mahendra
>
>
> On Mon, Jan 28, 2013 at 10:34 PM, Tomaz Muraus wrote:
>
> > If you upload the latest patch with tests to JIRA ticket we can get it
> into
> > 0.12.1 :)
> >
> > On
Hi Matt,
I'm currently not aware of anyone working on the Azure compute (IaaS)
driver. Feel free to open a new ticket on JIRA for it.
I do know that Mahendra has been working on the Azure Storage driver
recently (https://issues.apache.org/jira/browse/LIBCLOUD-80). It should be
merged into trunk s
Awesome!
I will do my best to do my part of reviewing it as soon as possible.
On Wed, Feb 6, 2013 at 7:01 AM, Mahendra M wrote:
> Hi all,
>
> I have updated the code with all review comments. Also tested it in python
> 2.7 and 3.2. Things seem to be working fine now. Please do have a look and
>
Hello all,
It has been a while since we released the last version in November. A bunch
of changes have piled up in trunk so I created a new release (0.12.1 -
r1444732).
This release includes many new features, bug-fixes and improvements. In
fact, it's probably one of the biggest releases (feature
Just FYI - I've started a new voting thread for 0.12.1 release. This
release includes everything which went into 0.12.0 release + a bunch of
other goodies and fixes.
On Thu, Jan 31, 2013 at 3:20 PM, Tomaz Muraus wrote:
> Just wanted to let everyone know I will wait a couple of more day
12.1
>
> Have been using the trunk checkouts in production for a while :-)
> Would be happy to use a stable release!!
>
> Regards,
> Mahendra
>
>
> On Mon, Feb 11, 2013 at 4:22 PM, Tomaz Muraus wrote:
>
> > Hello all,
> >
> > It has been a while since
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
Just FYI - there were some issues yesterday, but 0.12.1 should be available
on PyPi now - http://pypi.python.org/pypi/apache-libcloud/0.12.1
On Mon, Feb 18, 2013 at 3:46 PM, Tomaz Muraus wrote:
> Libcloud is a Python library that abstracts away the differences among
> multiple cloud pr
Hello all,
This is a voting thread for Libcloud 0.12.2 (r1451023).
This release is primarily a bug fix release and fixes a Python 3.x related
regression reported by Arfrever Frehtes Taifersar Arahesis (LIBCLOUD-245).
Release artifacts can be found at http://people.apache.org/~tomaz/libcloud/.
F
ssage --
From: Tomaz Muraus (JIRA)
Date: Fri, Mar 1, 2013 at 2:29 PM
Subject: [dev] [jira] [Created] (LIBCLOUD-301) Consider switching
documentation from custom Markdown to Sphinx + ReST
To: dev@libcloud.apache.org
Tomaz Muraus created LIBCLOU
Dear Libcloud users,
If you are using Libcloud with Python 2.5 please let us know either by
posting a "+1" in this thread or if you don't feel comfortable sharing this
information with other people by sending an email to
priv...@libcloud.apache.org.
Supporting Python 2.5 in Libcloud means we need
, Feb 27, 2013 at 3:29 PM, Tomaz Muraus wrote:
> Hello all,
>
> This is a voting thread for Libcloud 0.12.2 (r1451023).
>
> This release is primarily a bug fix release and fixes a Python 3.x
> related regression reported by Arfrever Frehtes Taifersar Arahesis
> (LIBCLOUD-245).
IIRC, there is currently no way to do that using the S3 driver.
We are definitely open to accepting a patch which adds extension method
(e.g. ex_make_object_public(self, obj)) for making an object public.
If you want to do that we are also happy to help so let us know if you get
stuck.
On Thu, M
Hello all,
This is a voting thread for Libcloud 0.12.3 (r1457203).
This release is primarily a bug fix release and fixes a Python 3.x related
regression reported by Arfrever Frehtes Taifersar Arahesis (LIBCLOUD-245)
and some other issues.
Full change log can be found at
https://svn.apache.org/re
w. Will hold
> back on it.
>
> Regards,
> Mahendra
>
>
>
> On Wed, Feb 6, 2013 at 3:58 PM, Tomaz Muraus wrote:
>
> > Hi Matt,
> >
> > I'm currently not aware of anyone working on the Azure compute (IaaS)
> > driver. Feel free to open a ne
3
>
> On Mar 16, 2013, at 12:47 AM, Tomaz Muraus wrote:
>
> > Hello all,
> >
> > This is a voting thread for Libcloud 0.12.3 (r1457203).
> >
> > This release is primarily a bug fix release and fixes a Python 3.x
> related
> > regression reported by Ar
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
This is a voting thread for Libcloud 0.12.4.
This release is primarily a bug fix release and fixes a couple of bugs and
regressions introduced in the 0.12.x release series.
Full change log can be found at
https://svn.apache.org/repos/asf/libcloud/tags/0.12.4-tenative/CHANGES
Release artifacts ca
ebian Sid.
>
> [+1] Release Apache Libcloud 0.12.4
>
> On Tuesday, April 16, 2013 10:40:59 PM Tomaz Muraus wrote:
> > This is a voting thread for Libcloud 0.12.4.
> >
> > This release is primarily a bug fix release and fixes a couple of bugs
> and
> > reg
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
Hey everyone,
We will be hosting Libcloud design day and meetup at the Rackspace San
Francisco office on Tuesday, 11th of June, 2013, starting at 6:00 PM.
Topics we plan to cover include:
- Provider discovery / registry - make Libcloud easier to use with
multiple providers
- Make Libclo
First of all I want to say thanks to everyone for coming. We had a lot of
good debates and received some first hand feedback from our users.
Hopefully most of this debates will result into some actual code soon :)
I've included a short recap and some action items bellow. Each section
first contain
On Wed, Jun 12, 2013 at 11:29 AM, Tomaz Muraus wrote:
>
> > *Exception reporting for partial failures in the methods which result in
> > multiple API calls / HTTP requests*
> > Currently we have no standard interface for exceptions which get raised
> > during a parti
I've created a new infrastructure ticket to migrate main Libcloud code
repository from svn to git. (
https://issues.apache.org/jira/browse/INFRA-6383).
David Nalley has already started working on it and as a consequence svn
tree will be read only until the migration has been completed.
David has
Thanks for the cross check.
I'm not sure if and how this will affect Github mirror, but I will ask this
in the INFRA ticket.
On Wed, Jun 12, 2013 at 3:03 PM, John Carr wrote:
> +1, looks good to me.
>
> Will this affect the GitHub mirror?
>
> Cheers,
>
>
> On
patch will just need to sign it
off. More details about signing off and other things will be available in
the new committer guide.
On Wed, Jun 12, 2013 at 3:35 PM, Tomaz Muraus wrote:
> Thanks for the cross check.
>
> I'm not sure if and how this will affect Github mirror, but I w
tly. I will work on writing a new committer and
> contributor
> > guide this weekend.
> >
> > One of the more important changes is that we can now preserve the
> original
> > commit author. Committer who is merging the patch will just need to
> sign
>
lities at all?
>
> Cheers
> John
>
> On 12 Jun 2013, at 06:59, Tomaz Muraus wrote:
>
> > First of all I want to say thanks to everyone for coming. We had a lot of
> > good debates and received some first hand feedback from our users.
> > Hopefully most of this
Awesome. I'm glad to see CloudStack driver being worked on and improved.
I'm moving back to Europe this week so sadly I can't make it. I can help a
bit with the advertising though - I'll mention CloudStack hack day and
Libcloud session on our Twitter and Google+ account.
Hopefully this will get o
operations complete.
>
> I wasn't involved in the decision to drop async support, it was part of
> a number of refactorings to reduce the size of the codebase and thereby
> its maintenance cost, but if you're interested, you may be able to find
> out more on the jclou
This is a voting thread for Libcloud 0.13.0.
This release includes a lot of improvements and bug fixes. Change log
can be found at
https://git-wip-us.apache.org/repos/asf?p=libcloud.git;a=blob;f=CHANGES;h=640bd2f4db8bc11674fc8c1829922d0c79b733cd;hb=9c0d11a4cf7e588ad87c7e57311bbb1d955cc2a7#l3
Rele
Cool.
I have some comments and questions:
1. We should probably get rid of the "Base" suffix.
All of the bases API interfaces (libcloud.compute.base, libcloud.dns.base,
libcloud.storage.base, etc.), don't contain this suffix.
2. As far as line 16 goes - Imo, having a separate method makes it mo
Heh, so it turns out I totally forgot that Libcloud already defines a
limited API for managing block storage:
*
https://github.com/apache/libcloud/blob/trunk/libcloud/compute/base.py#L368
*
https://github.com/apache/libcloud/blob/trunk/libcloud/compute/base.py#L705
Current block storage API is pr
Alex Gaynor wrote:
> That looks fine to me (I see only a few drivers implement it). I guess this
> means we'd move all the methods from a new set of drivers onto compute?
>
> Alex
>
>
> On Fri, Jun 28, 2013 at 9:19 AM, Tomaz Muraus wrote:
>
> > Heh, s
Bumping this thread - We are still missing 1 vote from a committer.
On Wed, Jun 26, 2013 at 7:46 PM, Tomaz Muraus wrote:
> This is a voting thread for Libcloud 0.13.0.
>
> This release includes a lot of improvements and bug fixes. Change log
> can be found at
> https://git-wi
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
I've opened a Github pull request with an initial implementation prototype
- https://github.com/apache/libcloud/pull/127.
Feedback is welcome, so if you care about this feature, please visit the
pull request and post your feedback and comments there.
On Sat, Jul 27, 2013 at 3:10 PM, Tomaz M
The Project Management Committee (PMC) for Apache Libcloud has asked John
Carr to become a committer and we are pleased to announce that they have
accepted.
We are glad to have him as a committer and a PMC member. Everyone, please
help me welcome him to the team :)
rs,
> John
>
>
> On 5 Aug 2013, at 12:08, Mahendra M wrote:
>
> > Welcome John! :-)
> >
> >
> > On Sun, Aug 4, 2013 at 11:57 PM, Tomaz Muraus wrote:
> >
> >> The Project Management Committee (PMC) for Apache Libcloud has asked
> John
/repos/asf/libcloud.git";).
>
>
>
>
>
>
>
> On 15 June 2013 12:12, Tomaz Muraus wrote:
>
> > Thanks, I'll have a look.
> >
> > This should definitely save us some time :)
> >
> > On Fri, Jun 14, 2013 at 6:29 PM, Koper, Dies > >
Yeah what Alex said. I'm also not aware of an existing Rack Connect driver.
How we should proceed depends on how much do you need to extend the base
OpenStack driver:
1. If you need to add a bunch of new functionality and extension methods,
then we should create a new RackConnect driver which inh
hostId'],
> + access_ips=api_node.get('accessIPv4'),
> # Docs says "tenantId", but actual is "tenant_id". *sigh*
> # Best handle both.
> tenantId=api_node.get('tenant_id') or api_node['tenantId'],
>
It seems like "node" object you are passing to wait_until_running method is
in fact "None" and not a "Node" object.
I'm not sure how this could happen though, because driver.create_node
should always return a "Node" object and not "None".
Can you please gist (https://gist.github.com/) the whole c
This is a voting thread for Libcloud 0.13.1. This release is bug-fix only
release. It fixes a Content-Length regression (LIBCLOUD-362, LIBCLOUD-3901)
introduced in 0.13.0 and a
couple of other issues.
Change log
can be found at
https://git-wip-us.apache.org/repos/asf?p=libcloud.git;a=blob;f=CHANGE
All,
I will be in London in the beginning of October. If enough people are
interested I was thinking about organizing a Libcloud meetup / hackathon
then.
Date: Thursday, October 3rd, 2013
Time: starts around 5 or 6 PM
Location: actual location TBD, but somewhere in London
If you are interested a
;>
> >> On Wed, Sep 4, 2013 at 7:44 PM, John Carr wrote:
> >>
> >>> +1 from me too.
> >>>
> >>> Sent from my iPhone
> >>>
> >>> On 4 Sep 2013, at 13:58, Jerry Chen wrote:
> >>>
> >>>> Looks
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
> > Kashif
> >
> > On 4 Sep 2013, at 18:41, John Carr wrote:
> >
> >> I should be able to make it.
> >>
> >> Cheers,
> >> John
> >>
> >> On 4 Sep 2013, at 18:11, Tomaz Muraus wrote:
> >>
> >>>
All,
Over the weekend I migrated some of my domains to a different DNS provider (
http://www.tomaz.me/2013/09/07/exporting-libcloud-dns-zone-to-bind-zone-file-format-and-migrating-between-dns-providers.html
so
I wrote a very simple script which allows you to export Libcloud zone to
BIND zone forma
differences among DNS
> providers.
>
> +1 to have it in core.
>
>
>
>
> On Fri, Sep 13, 2013 at 9:24 PM, Dinesh Bhoopathy <
> dineshbhoopa...@gmail.com
> > wrote:
>
> > +1 on this!
> >
> > On Thu, Sep 12, 2013 at 11:39 PM, John Carr wrote:
&
This is a voting thread for Libcloud 0.13.2.
This is another primarily a bug-fix release. Previous release included a
fix for the Content-Length bug which didn't fully fix the original issue.
It missed out "raw" requests which are fixed in this release (LIBCLOUD-396).
This bug could manifest itse
, John Carr wrote:
>
> > +1 from me too :-)
> >
> > On 15 Sep 2013, at 23:59, Jerry Chen wrote:
> >
> >> Looks great!
> >>
> >> [+1] Release Apache Libcloud 0.13.2
> >>
> >> On Sep 15, 2013, at 11:04 AM, Tomaz Muraus wr
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
(just fyi)
Libcloud tests now in addition to the existing Apache Buildbot (
https://ci.apache.org/builders/libcloud-trunk-tox) also run automatically
on TravisCI (https://travis-ci.org/apache/libcloud).
TravisCI uses Github mirror which means builds won't happen as soon as you
push and the usual
le
On Oct 1, 2013 9:32 AM, "Kashif Ali" wrote:
> Hi Tomaz,
>
> Just wanted to confirm this was still going ahead? I haven't had any
> confirmation about location/time.
>
> Regards,
>
> Kashif
>
>
> - Original Message -
>
> From: &
I think it's about time for us to switch to semantic versioning (
http://semver.org/).
Most of the users these days are already familiar with (and expect) the
semantic versioning scheme. This change will make it easier for them to
know what to expect and when to upgrade.
Currently we follow "0."
go the
BountySource route (https://www.bountysource.com/), but for that we'd need
to have some small financial backing coordinate the whole thing with the
ASF...
On Sat, Oct 12, 2013 at 2:44 PM, Jerry Chen wrote:
>
> On Oct 12, 2013, at 6:29 AM, Tomaz Muraus wrote:
>
> > As n
0.14.0 /
1.0.0 release.
If we do 0.14.0 release first, we have more time to fix those bugs for
1.0.0.
On Sat, Oct 12, 2013 at 2:44 PM, Jerry Chen wrote:
>
> On Oct 12, 2013, at 6:29 AM, Tomaz Muraus wrote:
>
> > As noted above, Libcloud has already been used in production for
Yeah, launching the redesign at the same time we do the 1.0.0 release makes
a lot of sense :)
On Sat, Oct 12, 2013 at 3:40 PM, Sebastien Goasguen wrote:
>
>
>
> On 12 Oct 2013, at 15:30, Tomaz Muraus wrote:
>
> > Forgot to add this option - 0.14.0 will contain quite a
s.apache.org/jira/browse/LIBCLOUD-331
>
> I think we should get these changes into main stream for 1.0.0.
>
> I can work on these, if you guys vote up.
>
> Thanks
> Jayy
>
>
> On Sat, Oct 12, 2013 at 7:18 PM, Tomaz Muraus wrote:
>
> > Yeah, launching the
Forgot to add that there is already an existing issue for this -
https://issues.apache.org/jira/browse/LIBCLOUD-286
Jerry, if you are going to work on it feel free to assign the issue to
yourself.
On Sat, Oct 12, 2013 at 3:16 PM, Tomaz Muraus wrote:
> Yeah, I wanted to redesign and improv
reasonable.
[1]: https://twitter.com/dstufft/status/389117973233152000
[2]: https://gist.github.com/dstufft/6954117
On Fri, Mar 1, 2013 at 11:51 PM, Tomaz Muraus wrote:
> Dear Libcloud users,
>
> If you are using Libcloud with Python 2.5 please let us know either by
> posting a &qu
Next release which will include a bunch of bigger changes, including the
move from one class per region to a single class + region argument model is
approaching.
I would appreciate if someone could cross-check and review the upgrade
notes for this release.
Docs:
https://ci.apache.org/projects/lib
Yeah a patch / pull request would be great.
On Tue, Oct 15, 2013 at 12:45 PM, sebgoa wrote:
>
> On Oct 15, 2013, at 11:14 AM, Tomaz Muraus wrote:
>
> > Next release which will include a bunch of bigger changes, including the
> > move from one class per region to a
All,
I will be at a CloudStack Collaboration Conference in Amsterdam in November
(http://cloudstackcollab.org/home). The conference takes place between
20-22nd of November.
If enough people are interested (at least 5), I can organize a Libcloud
meet up / hack day during the conference. The hack d
This is a voting thread for Libcloud 0.14.0-beta1. The reason this is a
beta and not a final release is that it includes some relatively big
changes. I would like those changes to get some more real-life testing
before doing a final release.
This release includes many new features, improvements an
x27;s do this.
>
> [+1] Release Apache Libcloud 0.14.0-beta1
>
> On Oct 19, 2013, at 4:25 AM, Tomaz Muraus wrote:
>
> > This is a voting thread for Libcloud 0.14.0-beta1. The reason this is a
> > beta and not a final release is that it includes some relatively big
> &
This is a voting thread for Libcloud 0.14.0-beta2. This release includes
the same changes as 0.14.0-beta1 with addition of some new changes. Most
notably an addition of "STOPPED" node state and support for new "hkg"
region in the Rackspace drivers.
The reason this is a beta and not a final release
nding vote, but right now I would be -1
>
> On Oct 23, 2013, at 6:45 PM, John Carr wrote:
>
> > I have some API changes that would be good to do before 1.0, but
> assuming we aren’t freezing the API…
> >
> > Let’s do this thing.
> >
> > +1
> >
> &g
Currently we don't do any kind of ssh key validation inside
the SSHKeyDeployment class.
I think it would be useful to do the following:
1. Validate the SSH key format and make sure it's valid.
2. Validate size of the RSA keys and error out on potentially weak (<= 1024
bits) keys. This would be do
;
> On Oct 28, 2013, at 5:55 PM, Tomaz Muraus wrote:
>
> > Currently we don't do any kind of ssh key validation inside
> > the SSHKeyDeployment class.
> >
> > I think it would be useful to do the following:
> >
> > 1. Validate the SSH key format and ma
This is a voting thread for Libcloud 0.14.0-beta3.
This release includes same changes as 0.14.0-beta1 and 0.14.0-beta2 with
addition of some new changes and bug fixes. Most notably, it fixes
OpenStack based driver to correctly handle expiration of the auth token
(LIBCLOUD-428).
The reason this is
Explicit +1 from me.
[+1] Release Apache Libcloud 0.14.0-beta3
On Fri, Nov 15, 2013 at 2:27 PM, Tomaz Muraus wrote:
> This is a voting thread for Libcloud 0.14.0-beta3.
>
> This release includes same changes as 0.14.0-beta1 and 0.14.0-beta2 with
> addition of some new changes a
short, I agree with
John. Tomorrow, after I get some sleep I plan to reply to John's post and
provider a more detailed explanation of approaches we could take.
On Tue, Nov 19, 2013 at 5:05 PM, Tomaz Muraus wrote:
> Explicit +1 from me.
>
> [+1] Release Apache Libcloud 0.14.0-beta3
&
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
Can you please provide more details:
- What kind of error did you get?
- Code which you used to instantiate the driver (don't forget to remove
your credentials)
On Fri, Nov 22, 2013 at 1:15 PM, Markos Gogoulos wrote:
>
>
> I'm experimenting with HP Cloud, managed to connect to US WEST
> region
2.0_password',ex_force_auth_url='
> https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0/
> ',ex_tenant_name='USER-TENANT',
> ex_force_service_region='az-3.region-a.geo-1',
> ex_force_service_name='Compute')
>
> #HP Cloud US EAST
> con
The Project Management Committee (PMC) for Apache Libcloud has asked Brian
Curtin 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 me welcome
him to the team :)
This is something we have already talked about in the past and I believe
that now (pre 1.0 release) is the right time to do it.
*Proposal*
I propose the following methods for the key pair management to be promoted
and be a part of the standard / base compute API:
* ex_list_keypairs -> list_keypa
reate_keypair_from_public_key?
>
Yeah, both of you have a good point here and I agree that all the methods
having a same common prefix makes it more obvious that they all belong in
the same group of functionality (key pair management in this case).
Cheers
> John
>
> On 5 Dec 2013, at 18:
Replies are in-line.
On Thu, Dec 5, 2013 at 10:00 PM, Sebastien Goasguen wrote:
> +1 see inline
> On Dec 5, 2013, at 1:50 PM, Tomaz Muraus wrote:
>
> > This is something we have already talked about in the past and I believe
> > that now (pre 1.0 release) is th
I have been thinking more about the import_* methods.
I kinda like the "create_keypair_from_public_key" idea, but the problem is
that we have two variants of this method (one which takes a file path and
one which takes key material) which means we would need to suffix it with
"_from_string" and "_
Replies are in-line.
On Thu, Dec 5, 2013 at 11:22 PM, John Carr wrote:
> Hey,
>
> >
> >>
> >> I had been considering adding another NodeAuth type object for these
> >> public keys, so you could pass a NodeAuthKeyName to the auth kwarg. EC2
> et
> >> al would then:
> >>
> >> class NodeDriver:
> >
I have implemented changes discussed in this thread in the following pull
request which is ready for a review -
https://github.com/apache/libcloud/pull/189
On Thu, Dec 5, 2013 at 11:29 PM, Tomaz Muraus wrote:
> Replies are in-line.
>
> On Thu, Dec 5, 2013 at 11:22 PM, John Ca
Over this weekend I have finally started to work on a new Libcloud website.
Website is not finished yet, but I think I have made decent progress and
some feedback would be appreciated at this point.
Live preview: http://lcv2.dev.tomaz.me/
Source code: https://github.com/Kami/libcloud-website-v2/
Bumping this thread for all the people who might have missed it over the
weekend.
On Sun, Dec 15, 2013 at 3:59 PM, Tomaz Muraus wrote:
> Over this weekend I have finally started to work on a new Libcloud website.
>
> Website is not finished yet, but I think I have made decent pro
it should be relatively to parse mbox files and use the
content to populate the release announcement blog posts.
In any case, blog page still needs some styling / design love.
> Cheers,
> John
>
> On 16 Dec 2013, at 21:29, Tomaz Muraus wrote:
>
> > Bumping this thread for all
Replies are in-line.
On Tue, Dec 17, 2013 at 9:16 AM, sebgoa wrote:
>
> On Dec 16, 2013, at 11:59 PM, Tomaz Muraus wrote:
>
> > Replies are in-line.
> >
> > On Mon, Dec 16, 2013 at 11:17 PM, John Carr wrote:
> >
> >> Hey,
> >>
> >
1 - 100 of 1244 matches
Mail list logo
