I created https://issues.apache.org/jira/browse/INFRA-8622 to get a
space added for us. I tried adding Andrew Phillips as another space
admin (as PMC Chair) but I couldn’t find his confluence ID.
Just created user "andrewp". Thanks, Chris!
ap
(moving to dev@...)
I didn't build openstack-neutron. I just put 1.8.1 as my maven dependency
and built my project. When I see the jar from my local repo, I found
$Subject.
Thanks for flagging this up, Raj! I think you've found a bug in the
POM file(s) for the affected projects: the OSGi imp
This changes will be eventually in the artifact from maven central
repository right? Or Do I have to build and use it?
This change should make it into the 1.8.x-SNAPSHOT JARs after it is
merged. But it won't be in a stable version until 1.8.2/1.9.0, I'm
afraid.
ap
I would like to start an Amazon only (no goal of supporting knockoffs) ec2
provider in labs.
Having a modern, up-to-date AWS EC2 provider would be great, of
course. Would the plan here be to remove aws-ec2 once this is done
and/or to be backwards-compatible with it?
Do you think one of the
May I know when it will be released to maven? :)
Snapshot builds run on every commit, so once the PR is merged, it
should be in the Apache snapshots repo shortly afterwards.
ap
Some work might have to be done (with the jclouds gson) to make sure
this works consistently with custom name serialization and to make
sure everything is consistent with autovalue. AutoValue classes will
still be used to parse json as returned by the service.
Thoughts?
In general, I th
jclouds will stop maintaining vcloud in 1.8.x. We will remove vcloud
(and the vcloud-director labs provider) in version 1.9.0.
Dropping support for vCloud is not a pleasant step to take, but it
also seems like the best option to me at this point. vcloud-director
has been in labs for far too
Not sure If I read it right, does this mean VCloud support will be removed
in 1.8.x onward?
Yes, that's correct. Are you currently using the vcloud or
vcloud-director providers? If so, is this running against an on-prem
installation?
As mentioned at the beginning of the thread, the vcloud
It used to be the case that we executed live tests on major releases,
The release threads do contain live tests [1]. But, er, I can't see
any for aws-ec2, and we certainly need to pay more attention to what
the live tests are actually telling us :-(
Thanks for getting Frankfurt going, Adri
+0.
No strong preference either way but am very happy to try...especially
if the difference in performance turns out not to be a transient thing.
ap
Lessons learned? If you¹re using a newer version of eclipse, and maven to
manage your deps, it¹s possible you may have to add multiple dependencies
to the eclipse annotation processor to get it to stop complaining about
AutoValue (and in the case of OSX add ALL those dependencies without
rebuildin
Would you be interested in updating or completely replacing the
current Releasing jclouds [1] with your reference [2]?
If you think it makes sense to have a document that's phrased more in
terms of a "this is what I did" vs. "this is what you need to do",
then sure! Hopefully we'll also fi
If there are no objections, the switch to the new builders will be
made this week.
No objections from me. Thanks for getting this set up, Ignasi!
ap
1. So once an api meets the criteria of having a steward, being
modern, and having a proper test suite, it can immediately be
promoted?
Looks like Ignasi beat me to it - I was going to make points very much
along those lines.
About stewards: there has been a long and (it seems) heated
dis
I addressed this as part of JCLOUDS-706 where we upgraded from API
2009-09-19 to 2012-02-12. I also ran the integration tests recently to
resolve JCLOUDS-671.
Thanks, Gaul!
ap
To echo what Ignasi said, I think we need to note that jclouds calls
itself "the Java multi-cloud toolkit." To find out what that means in
the face of some pretty big changes in cloud usage, I think we really
need to ask our users, but more on that in a different thread. To me,
the "multi-c
In the vein of collecting more user feedback, here some notes from a
follow-up call to [1] with Sunil Shah, also from Mesosphere.
Notes below. The main take-aways for me:
1. Need to find out how many users need to work with patched versions
of master rather than patched versions of a stable
Hi all
We've recently seen a number of tricky but necessary technical
discussions around jclouds (e.g. [1], [2], [3]), which I think
highlight what the community already knows: for jclouds to continue to
be relevant and useful, we have some key challenges to address and
decisions to take.
I think that the peocedure (which I also consider unnecessary) is
irrelevant for this discussion. Let's focus on the subject of the thread
and elaborate on that.
To add to Ignasi's comment: the process for getting stuff into jclouds
can certainly be improved, but unless and until we determine
Hi all
Two quick points:
1) With CloudBees sunsetting their PaaS, the HEAD Javadocs have moved
here: http://jclouds-javadocs.elasticbeanstalk.com/
2) The draft board report for January is here:
https://cwiki.apache.org/confluence/display/JCLOUDS/January+2015+Board+Report+Draft
The deadline
The draft lgtm.
Thanks for taking a look, Ignasi! Also added the following sentence to
thank Adrian for all his work:
"The jclouds PMC would like to express its sincere thanks to Adrian
Cole, who recently left the PMC, for his years of work in building
jclouds and growing the jclouds com
@demobox, is this something you could run with as the project lead?
Can we figure out how to make this happen starting in February?
If we decide to do this, I'm happy to figure out how to make this
happen, and to find out what kind of "housekeeping" in terms of taking
notes etc. would be n
There is a reason ASF projects don't encourage synchronous meetings.
It's OK to have them, but be aware that they are exclusionary and
typically bad practice.
If the team go ahead then remember no decisions can be made in these
meetings, only proposals can be drawn up to be brought to th
semantincs. In this scenario, I don't see the "getFoo()" vs "foo()"
naming a real issue. I'll agree to use whatever naming convention is
preferred, but I think we have more important stuff to focus on right
now.
I'd also rather focus on abstractions at this point, but just to weigh
in with an
configuring a JEE container (e.g. Glassfish or JBoss) for use with
jclouds. They had tried and had run into issues with some conflicts
between Guice and CDI.
I’ve created a issue for it here.
https://issues.apache.org/jira/browse/JCLOUDS-810
Thanks for that, Everett. Would this potential
Thanks for that, Everett. Would this potentially be related to the
following thread?
I don't know, I'm afraid. Hopefully Ignacio will be able to clarify ;-)
Regards
ap
t step, do we know whether we have issues in JIRA (with the
correct fix version etc.) for all these issues? Then we can hopefully
use JIRA as a "proper" backlog management tool for 1.9.0.
Thanks for the JIRA cleanup work, Andrew G and Jeremy!
Regards
ap
--
Andrew Phillips
qrmed
Hi Ross
Thanks for the pointer John. Why is Blob in core and Compute in
Labs? What is the criteria for leaving labs?
See http://markmail.org/thread/zvsytdvzfeg4w2zi. In short, it's still
an ongoing discussion, but support for one of the abstraction layers
(which is true for both Azure Bl
I'll be more than happy to help with the development of the provider,
provide guidance, and to align the code with what jclouds needs.
Thanks for putting together this comprehensive answer, Ignasi! For
future reference, I've tried to formulate it more generally here:
https://cwiki.apache.org
Eduard (who has also joined this list) will work on the initial
contribution in the coming days and we can start doing concrete stuff.
Great! Looking forward to seeing the code doing the talking ;-)
Regards
ap
Hi Timur
Just briefly on the tools part:
Code repository: GIT Hub + Apache
Communication tools: E-mail + GIT Hub (are there any others?)
Documentation: Project Web-site (do you use any other specific
software for documentation?)
* The only and official "home" of the jclouds code is in the ASF
+1 - thanks Eduard
Another big +1. Thanks, Eduard and everyone else involved, for moving
this forward. Looking forward to much more Azure use from the jclouds
community!
Regards
ap
PS: One piece of feedback we've had from various users is that
up-to-date examples in jclouds-examples [1
Nevertheless, let me know if there is anything I can do to help
with the release this weekend, I will be available.
I should also be available on Sunday. Thanks, Ignasi!
Regards
ap
===
Apache ID: andrewp
---
[X] +1 Release.
[ ] -1 Don't release (see notes).
---
Checklist (al
Any feedback on the script is very welcome!
Er...it sounds AWESOME? ;-)
Many, many thanks for this, Ignasi - all the releasers owe you at
least a beer now. I'm certainly for trying this, we just need to make
sure we're a little more diligent about checking things like POM
versions in the
PS: Does the script try to create a new branch every time, or is that
configurable? E.g. 1.9.1 will obviously *not* need a new branch to be
created.
Regards
ap
Personally, I see more benefits and more convenient to have the
release scripts in SVN.
Based on what you explained, Ignasi, I tend to agree - especially to
break the "circular dep" between using the release script to generate
the release and having to tweak it.
SVN seems fine for me - I'd
Hi all
Ran into some build failures related most likely to my machine, which
is why this is coming late, but just for the record:
===
Apache ID: andrewp
---
Does anyone mind if I remove some of the pre-1.8.x branches from the ASF
repositories, e.g.,
Unless there's some clear performance penalty I'd rather keep them, to
be honest. If the consensus is to remove some, I'd probably vote to
keep at least 1.5.x and newer for now.
Regards
ap
* modules are in bundle.info files.
I'm no maven expert, not sure what all these bundles are for.
On 03/30/2015 06:37 PM, Andrew Phillips wrote:
in via the jclouds-karaf dependency. If I modify the feature.xml file
(that was downloaded during the first time through the build) and then
reb
Hi all
We're due again for an ASF board report this month. I've put a first
draft up on the wiki [1]; the report itself needs to be submitted next
week.
Please have a look and make any changes necessary.
Thanks!
ap
[1]
https://cwiki.apache.org/confluence/display/JCLOUDS/April+2015+Boar
Under community objectives, could we promote some of the general
development themes into more concrete terms? Over the last six months
we have made strides in removing some of the API and provider cruft
(async, dead providers), increasing integration test coverage, and
broadening the portable abs
classpath and there might be errors we can't control, I'd say we can
safely catch a general Exception there and return an Absent value.
I'd agree with that, but the tricky thing here is that what is thrown
isn't even an Exception, it's an Error. So we'd have to catch all
Errors here (or just
That should minimize the impact of the issue, and allow normal
operation when jclouds knows how to conenct to the node.
WDYT?
If I understand your proposal correctly, you mean essentially moving
the first attempt to find a connector to here:
https://github.com/jclouds/jclouds/blob/master/dr
Yes, that's what I mean. Invoke the factory there, only if there's a
need to connect to the SSH agent.
Hrm...unfortunately it seems it's not quite so simple :-( This test is
also used to verify whether an agent is even available, here:
https://github.com/jclouds/jclouds/blob/master/compute/s
A cloud agnostic library that enables developers to access a variety of
supported cloud providers using one API.
# Project Status
jclouds has carried out one successful release (1.9.0) in the last quarter.
After a quiet period during the 2014 holiday season, development activity has
picked up q
And submitted!
ap
If you provide a patch I'll be happy to test it and give feedback! :)
Here you go ;-) The "solution" (assuming it works, of course ;-))
turns out to be pretty nice, actually.
https://github.com/jclouds/jclouds/pull/721
Regards
ap
Just FYI: https://github.com/ymnk/jsch-agent-proxy/pull/23
Regards
ap
TL;DR: if we want to stick with the current functionality set, I think
the PR against the sshj driver seems like "the right one."
Just to confirm, this is a temporal fix until your PR to fix the agentproxy
bundle is in and released, right? Hopefully a fix for an eventual 1.9.1 and
to be revert
If we merge this pull request we might be *removing* working stuff.
That is true, but the question here is whether that stuff was ever
*intended* to work. It's certainly not been tested, from what I recall
- the reason we originally didn't try to figure out how to get all the
bundles loade
Quoting Ignasi Barrera :
Hmmm if this is failing now in 1.9, it should be also failing in 1.8,
Just tried to verify this in 1.8.0 and 1.8.1, but can't get those CLIs
working :-(
java.lang.Exception: Could not start bundle
mvn:org.apache.jclouds.karaf/core/1.8.1 in feature(s)
jclouds-se
Reviews are very welcome :)
Added some minor comments, and one more major question as to whether
we can't get rid of the need to access *both* the ChefService *and*
the ChefApi in some way?
Thanks for chewing through this one, Ignasi!
ap
I think a simple solution can be to inject
@Provider Supplier endpoint, @Provider Supplier creds
Seems like a good option, indeed - into the ComputeServiceAdapter
implementation, I presume?
Are you already injecting the underlying API(s) directly into the
adapter? If so, would be curious
great question. Basically I need to create a new ContextBuilder from inside
the ComputeServiceAdapter of the providerA to invoke the APIs of a
providerB.
Ah, interesting. Any reason why you need to create the context for
providerB on the fly, rather than simply injecting a providerA and
prov
Quoting Ignasi Barrera :
Unless anyone says the opposite Today I plan to push the Google
Compute Engine provider [1] to the main repo.
Thanks for the warning, Ignasi, and for getting this done!
Regards
ap
Hi all
Board report time again! I've put together a draft for July on the Wiki:
https://cwiki.apache.org/confluence/display/JCLOUDS/July+2015+Board+Report+Draft
I've only had time to follow some major discussions this quarter, so
the outline of the report is probably missing important points.
Hi all
I'll be submitting the July board report tomorrow, so if you have any
changes you'd like to make to the draft, please do so today.
https://cwiki.apache.org/confluence/display/JCLOUDS/July+2015+Board+Report+Draft
Thanks!
ap
And submitted!
ap
Original Message
Subject: [REPORT] July 2015 report from the Apache jclouds project
Date: 2015-07-07 18:45
From: Andrew Phillips
To: bo...@apache.org
Report from the Apache jclouds Project
A cloud agnostic library that enables developers to access a
If there is an agreement, I'd propose a week of live test run&fix and
cut the 1.9.1 release on July 15-20. Does this sound like a good plan?
Thanks for suggesting and coordinating this testing effort, Ignasi -
seems like a really good idea.
Regarding the release itself, I should be available
Please, share your thouhts here or in the PR!
Given the struggles we've had in the past around forcing newer Guice
versions on users, my default inclination here would be to stay with the
older version if there are still users on this: if the problem we're
trying to solve isn't critical, we d
the PR gets merged (or we could add Guice to the version
matrix we have in the Guava compatibility builds).
Just created a matrix build for Guice compatibility for the PR, actually
;-). Thanks for figuring out the refspec on this one, Ignasi!
https://jclouds.ci.cloudbees.com/job/jclouds-guice
what's happening with
https://gist.github.com/abayer/290424448caf1e1cca74?
Any idea what this character is?
/src/main\300java
I guess that's meant to be a "normal" slash? Something to do with Git
encoding settings, perhaps?
Regards
ap
but at different (and random) repos. It appears when Git has a
corrupted file or there are changes in a file (the pom.xml with the
updated version), but the file is also marked to be deleted.
Glad to hear things seem to have worked this time around - do you think
the error was caused by an issu
Hi all
===
Apache ID: andrewp
---
[X] +1 Release.
[ ] -1 Don't release (see notes).
---
Check
can we mark them as fixed and update the annoucement?
Luckily, since the VOTE thread only includes a link to JIRA (rather than
a list of the issues themselves), we shouldn't have to update the
announcement - just set the Fix Versions in JIRA correctly.
Thanks for spotting that!
Regards
ap
The release has been made. We're waiting for the release files to be
replicated to the mirrors and the artifacts to reach Maven Central
to send the official announcement.
Many thanks for making this happen, Ignasi and everyone who tested!
ap
Hi Subhadip
For now to include GCE in our current setup is there any workaround
we can do?
I tried the same with the compute operation but getting the below
issue for version 1.7.3. Any suggestion?
The jclouds GCE provider JARs will not work under 1.7.3 - unfortunately,
you will indeed need
Hi all
The jclouds JIRA still contains an open Fix Version 1.8.2. Is this
something we feel should still happen at some point? If not, my
suggestion would be to remove that Fix Version from the remaining issues
[1], and delete that version.
Regards
ap
[1]
https://issues.apache.org/jira/br
There are no plans to release 1.8 again so I'd say go ahead and
remove that version.
Done. Thanks, Ignasi!
Regards
ap
I'm seeing problems pop up with 1.9.1 where the overrides I set when I
build a context with ContextBuilder seem to be ignored - I can override
them by setting the properties themselves on the command line, but not
at
context initialization time.
Do you have a quick code example? Are you seeing
Hi Ashley
Any insight as to why this is happening? Is this a deliberate
implementation decision? Is there a better way around this?
I haven't had a chance to look at your scenario in detail, but this
sounds very similar to a common problem related to a nohup/ssh race
condition.
Basically,
Hi Subhadip
I'm getting the below error while authenticating with ec2 for any a
particular region.
Just to confirm: if you use 1.9.0, you do *not* get this error?
Regards
ap
[moving this to user@ - please subscribe to that list if you are not
already on it, Subhadip. Thanks!]
Hi Subhadip
Purely based on the error message, it would seem that the proxy settings
you are providing are incorrect:
properties.setProperty(Constants.PROPERTY_PROXY_TYPE, "http");
properti
[moving this to user@...]
What is the correct procedure to pass certificate for every public
clouds through jclouds? if I have to ship the application to any
remote machine ?
In terms of trusting certificates, jclouds doesn't behave any
differently than any other Java application. The first q
I've just disabled the Guava and Guice compatibility builds and
created a new one that joins both and tests all combinations, to
have a better coverage:
Thanks for getting this set up, Ignasi!
ap
Hi all
I've updated the board report draft for October:
https://cwiki.apache.org/confluence/display/JCLOUDS/October+2015+Board+Report+Draft
Please have a look and comment/amend as necessary. I'll be submitting
the report on Oct 12th in the evening or on the morning of the 13th - a
bit before
Hi all
Quick reminder: board report to be submitted today:
https://cwiki.apache.org/confluence/display/JCLOUDS/October+2015+Board+Report+Draft
Please review and comment/amend, if desired!
Regards
ap
providers recently graduated from the
jclouds labs repo
* Encourage and supervise, where necessary, new contributors to grow
the committer base
Releases
jclouds has carried out one release in the past quarter: 1.9.1 was
released on 2015-08-06.
--
Andrew Phillips
Apache jclouds
While HP will end service in a few months, I believe we should remove
support in master now and users can continue to use 1.9.1 to access HP.
+1 - sounds like a plan!
Regards
ap
Hi Antonio
I should download the jar binaries of jclouds 2.0 (stable or
snapshot ),in particular the libraries to interact with
openstack environment ( all features).
Just to clarify: jclouds 2.0 has not been released yet - your options
are 1.9.1 (the latest release) [1] or the latest 2.0.0 S
Hi all
Getting the following error when trying to delete a stale branch:
..> git push origin :add-test-retry
Password for 'https://andr...@git-wip-us.apache.org':
remote: error: denying ref deletion for refs/heads/add-test-retry
To https://andr...@git-wip-us.apache.org/repos/asf/jclouds.git
! [
Yes. Non-fast-forward pushes and branch deletion has been
disabled temporary in all ASF repos until a proper Git policy
regarding the topic is established foundation-wide.
Thanks for confirming, Ignasi. I've created
https://issues.apache.org/jira/browse/INFRA-10965 for this.
Regards
ap
Hi Antonio
I try to develop a new Api to Jclouds to work with ONE.Please
someone can send me some tutorials or how-to to develop correctly
my new API?
Can you give us some more details on what kind of an API you are trying
to write? Is it a compute service, a blobstore, something else?
Rega
I try to develop a compute Api.
Ah, cool! What kind of a backend system are you planning to talk to? Is
it exposed via an HTTP API (if so, XML or JSON), or do you have a Java
or other library to talk to it, or..?
Regards
ap
Forwarding to dev@jclouds...
@Libor: the jclouds Google Groups emails are no longer in use - see
http://jclouds.apache.org/community/ for links to the current mailing
lists.
Regards
ap
On 2015-12-20 08:02, limorbort...@gmail.com wrote:
HI all
I a have a pull request in the jclouds-labs-ope
Hi all
Prompted by the question below on user@j.a.o: what is the thread-safety
status of an API returned via ContextBuilder...buildApi?
Context themselves are supposed to be thread-safe [1], but an API
context's getApi method is documented as:
"Threadsafe implementations will return a singl
HTH!
Yes, it does - many thanks for the summary. In fact, I think this would
make an excellent blog post ;-) For now, I've added an article to the
developer wiki as a start:
https://cwiki.apache.org/confluence/display/JCLOUDS/Context%2C+API+and+Provider+Thread+Safety
Please edit/delete/amen
Hi 隋震
The "core concepts" document should hopefully help explain contexts,
APIs and providers:
http://jclouds.apache.org/start/concepts/
If you still have questions after reading that, please let us know. Does
your cloud system implement a "standard" API such as S3 or EC2, or does
it have a
Forwarding to dev@j.a.o...
Original Message
Subject: 回复： what difference between jclouds providers and jclouds apis
Date: 2015-12-25 14:46
From: "隋震" <183941...@qq.com>
To: "Andrew Phillips"
Hi Andrew
Merry Christmas!
Thank you for your prom
Hi all
A quick reminder that the January board report is coming up and needs to
be submitted by the 13th. I've added a placeholder page to the Wiki, to
get things started:
https://cwiki.apache.org/confluence/display/JCLOUDS/January+2016+Board+Report+Draft
An advance Happy New Year, everyone!
Hi Antonio
Are you interested in submitted a pull request with a change to the
ServerApi? Or would you just like to "patch" your version of jclouds in
your own application?
In jclouds, interfaces like ServerApi are not implemented explicitly
anywhere - the implementation is generated on the
If there are no objections I'll do that and cut 1.9.2 later
today/tomorrow.
+1 - thanks, Ignasi!
@john, regarding collaboration, feel free to contribute! Code, docs,
live test runs... Everything is very welcome!
@John: is there any area of jclouds that you're particularly interested
in?
R
Hi all
===
Apache ID: andrewp
---
[X] +1 Release.
[ ] -1 Don't release (see notes).
---
Check
Also no one expects a exitStatus to be null (it's kind of weird)
Was the intention perhaps to use that in cases where we were not able to
determine the exit code? Are we aware of such cases..?
Regards
ap
WDYT? Other ideas?
+1 on using an empty set of hardware profile to indicate "does not use
profiles", and on using auto-generated Hardware objects, in response.
It would be nice if the (random?) ID of those object somehow
corresponded to the request to make it clear that these are really
"ep
There are many chances the value could be left null unintentionally,
just
by not setting it in some execution path.
That is true, although unless we're careful about setting the defaults
correctly we could also forget to set the value of the int, and
unintentionally end up with 0 (rather than
I'm about to promote the DigitalOcean v2 provider from jclouds-labs to
the main repo.
Thanks for the heads-up! I guess this page should then be updated, too?
http://jclouds.apache.org/reference/providers/
Regards
ap
Thanks for starting this thread!
Big +1 to that - thanks, Anthony! What I'd be especially interested to
hear about are your thoughts on the feasibility of providing a level of
abstraction at this point.
The main questions for me would be:
* What is the right interface: something that can in
Please, join us in congratulating Reijhanniel!
Welcome, Reijhanniel! Great to have you on board!
ap
1 - 100 of 1822 matches
Mail list logo
