This thread is for discussion of the third release candidate for
Apache
jclouds 1.6.3.
Many thanks for taking this on, Andrew G!
ap
jclouds, a committee that is due to submit a report by Wed Jan 10th
Argh, only just noticed this (report is due on Wed). Draft page at:
https://cwiki.apache.org/confluence/display/JCLOUDS/2024+-+January+Board+Report+Draft
A belated Happy 2024, everyone!
ap
jclouds, a committee that is due to submit a report by Wed Oct 11st
for the next ASF board meeting.
Draft page at:
https://cwiki.apache.org/confluence/display/JCLOUDS/2023+-+October+Board+Report+Draft
Please edit as desired!
ap
Original Message
Subject: TAC supporting Berlin Buzzwords
Date: 2023-03-24 05:56
From: Gavin McDonald
To: gmcdon...@apache.org
Reply-To: priv...@jclouds.apache.org
PMCs,
Please forward to your dev and user lists.
Hi All,
The ASF Travel Assistance Committee is supporting
Hi all
FYI that the next board report is due on Jan 11th - skeleton doc here:
https://cwiki.apache.org/confluence/display/JCLOUDS/2023+-+January+Board+Report+Draft
Hope everyone is having a good weekend!
ap
On 2023-01-15 11:59, Sander Striker wrote:
Hi,
According to our records, you are
a committee that is due to submit a report by Wed Oct 12nd
Skeleton page:
https://cwiki.apache.org/confluence/display/JCLOUDS/2022+-+October+Board+Report+Draft
Hope everyone is having a good weekend!
ap
Hi all
Skeleton board report page:
https://cwiki.apache.org/confluence/display/JCLOUDS/2022+-+July+Board+Report+Draft
Regards
ap
Original Message
Subject: jclouds Board Report due by Wed Jul 13th - Initial Reminder
Date: 2022-07-05 04:17
Hello,
According to our records,
Skeleton board report draft:
https://cwiki.apache.org/confluence/display/JCLOUDS/2022+-+April+Board+Report+Draft
Please add/amend as desired!
ap
Original Message
Subject: jclouds Board Report due by Wed Apr 13th - Initial Reminder
Date: 2022-03-30 14:33
The Apache jclouds team is pleased to announce the release of jclouds
2.5.0.
Many thanks for taking care of this release, Andrew G.!
Regards
ap
Thanks for taking care of this, Andrew G!
ap
On 2022-01-11 07:31, Andrew Gaul wrote:
== Project Status ==
Project successfully released 2.4.0 in Q3 2021. The team fixed some
modern Java incompatibilities and resolved to streamline the release
process by dropping the labs packages.
There are
Isn't there any way where we don't provide any credentials and during
actual calls blob fetches the credentials (via EC2 token internally)
just like the original AWS (AmazonS3ClientBuilder) client uses.
As far as I am aware, this is not currently possible, no.
/InstanceProfileApi.java
Regards
ap
On 2022-01-11 04:47, Andrew Phillips wrote:
Hi Abhinav
Is there a way to not provide the below .credentials and the context
pulls via
Instance Profile Credentials.
This sounds like https://github.com/jclouds/legacy-jclouds/issues/1280
(note: in the legacy repo, which
Hi Abhinav
Is there a way to not provide the below .credentials and the context
pulls via
Instance Profile Credentials.
This sounds like https://github.com/jclouds/legacy-jclouds/issues/1280
(note: in the legacy repo, which is no longer in use) - I'm not sure if
something like that was
Hi all
Skeleton report here:
https://cwiki.apache.org/confluence/display/JCLOUDS/2022+-+January+Board+Report+Draft
Please add comments as desired!
ap
Happy New Year!
According to our records, you are listed as the chair of jclouds,
a committee that is due to submit a report by Wed Jan
Also +1 - thanks for kicking off this thread!
ap
due to submit a report by Wed Oct 13th for the next ASF board meeting.
This is an initial reminder to prepare a report for jclouds and submit
it as described below.
Skeleton page at
https://cwiki.apache.org/confluence/display/JCLOUDS/2021+-+October+Board+Report+Draft
Have a good weekend,
Thanks for dealing with this Andrew G.!!
Big +1 - thank you, Andrew G.!
ap
It has been 5 months since jclouds 2.3.0 and I would like to plan to
release 2.4.0 next month.
Thanks for kicking this off, Andrew G!
ap
If no one else volunteers to fix this I suggest that we remove it.
+1 to removing unless someone is interested in getting it working.
Thanks for suggesting this, Andrew G!
ap
There's 1 new edit on your page
Thanks for taking care of this, Andrew G!
ap
Subject: jclouds Board Report due by Wed Jul 14th - Initial Reminder
Skeleton report at
https://cwiki.apache.org/confluence/display/JCLOUDS/2021+-+July+Board+Report+Draft
Regards
ap
It looks good to me. Short and precise.
+1 - thanks for putting this together, Gaul!
ap
+1 (binding)
@Jean-Baptiste: as a technicality, I think yours would be a non-binding
vote - my understanding was that only votes by PMC members are binding
[1, 2]?
Thank you of course for taking the time to test the RC!
ap
[1]
Andrew Gaul. is quite more active and involved in the project than I
am, so
I'd like to propose him as the new chair for the project.
+1 - thanks for the suggestion!
@Gaul: glad to hear that you might be available for this!
A belated Happy 2021, everyone
ap
jclouds, a committee that is due to submit a report by Wed Jan 13th
for the next ASF board meeting.
Skeleton report here:
https://cwiki.apache.org/confluence/display/JCLOUDS/2021+-+January+Board+Report+Draft
Please edit as desired. And, of course, a belated Happy 2021, everyone!!
ap
Thanks for taking the lead on this!
+1 - thanks!
ap
Skeleton draft:
https://cwiki.apache.org/confluence/display/JCLOUDS/2020+-+October+Board+Report+Draft
Please add/amend as desired!
ap
Original Message
Subject: jclouds Board Report due by Wed Oct 14th - Initial Reminder
Date: 2020-10-05 12:42
Hello,
According to our
The next step will be to see what we learn from INFRA-20725, and then
to hopefully close things out from there.
Just closing this out with the list of warnings [1] related to the
migrated jobs. At a first glance, none of them seem critical, and a
number of the affected jobs are currently
The next step will be to see what we learn from INFRA-20725, and then
to hopefully close things out from there.
I should add a shout-out here to Gavin McDonald, who's responded very
quickly to all the Infra issues. Many thanks, Gavin! Also, of course,
for giving us the extra week in which to
Hi all
A quick update here: all jobs have now been migrated to
https://ci-builds.apache.org/job/JClouds/ - you should be able to log in
using your ASF ID to modify jobs if needed.
As suggested in the instructions I followed [1], I've opened INFRA-20725
to see if there are any configuration
Hi Gavin
Sorry to be bugging you again (and happy to continue this on
users@infra.a.o if preferred) - it seems as though builds.a.o is
currently down, though :-(
I've opened INFRA-20716 [1] for this; if there's any way to easily bring
it back, that'd be much appreciated. We'd then be keen
Hi Gavin
The deadline has - for one time only - been extended to 22nd August -
so you have 1 more week only to move your jobs.
Thanks for the reminder, and for the generous extension! As a first step
to trying to make something happen before then, we have opened
INFRA-20695 [1] to ask for a
We need to migrate the Jenkins instance or rely on another build
system,
such as Travis, or GH actions.
I'm going to try the instructions at [1] to see how much we can move to
ci-builds.a.o. I'll probably only have limited time to try to fix any
broken builds, but at least we'll hopefully be
I disable the periodic build. This is no longer necessary since we
archived the non-Apache repository.
Ack - thanks for the heads-up!
ap
Report sent.
Thanks, all!
ap
Hi all
July's board report is due next week (see below). Skeleton page at
https://cwiki.apache.org/confluence/display/JCLOUDS/2020+-+July+Board+Report+Draft
Regards
ap
Original Message
Subject: jclouds Board Report due by Wed Jul 8th - Initial Reminder
Date: 2020-06-29
[moving this here from the VOTE thread...]
Sorry, I have little expertise with gpg. I believe this is the same
key
I have used since 2017. Does this mean that my key is not signed by
anyone in a chain of trust? This should not block the release, right?
I don't think this is a release
===
Apache ID: andrewp
---
[X] +1 Release.
[ ] -1 Don't release (see notes).
---
Checklist
Hi JB
Just as a matter of procedure, I think your vote may technically be
"non-binding" rather than "binding"?
If you were able to run the verification script successfully (I'm still
wrestling with my local system), I'd be happy to take that information
into account in my upcoming vote.
Given the comments so far, would it make sense to consider:
1. Move to (only) Java 8
2. Update library dependencies
as the top 2 issues to focus on?
Regards
ap
Some ideas:
* spin out components, similar to what we did with jclouds-karaf
previously
* release from master and stop maintaining release branches, e.g.,
2.2.x
* reduce the Java compatibility matrix, e.g., Java 8 and newer only
* upgrade key dependencies, e.g., BouncyCastle, Guava, to avoid
I propose releasing 2.2.1 in next week since it has been 6 months since
2.2.0.
+1 - thanks for suggesting this! Should be able to help with release
testing if needed, too.
Have a good Sunday, everyone!
ap
I've updated it and will be sending it in a bit
Thanks, as usual, for taking care of this, Ignasi!
Hope everyone's having a good weekend...
ap
Hi all
A quick follow-up here, in case anyone has anything they'd like to add -
the report submission is technically already a little overdue (meeting
itself is next Wed).
Regards
ap
On 2020-03-25 21:18, Andrew Phillips wrote:
This email was sent on behalf of the ASF Board
This email was sent on behalf of the ASF Board. It is an initial
reminder
to give you plenty of time to prepare the report.
Skeleton page here:
https://cwiki.apache.org/confluence/display/JCLOUDS/2020+-+April+Board+Report+Draft
Please edit as needed.
Hope everyone is doing as well as
A quick follow-up ping on this - officially due tomorrow.
Regards
ap
On 2020-01-04 08:35, Andrew Phillips wrote:
Skeleton template for January's report, which is due *next Wednesday*:
https://cwiki.apache.org/confluence/display/JCLOUDS/2020+-+January+Board+Report+Draft
Happy New Year
Skeleton template for January's report, which is due *next Wednesday*:
https://cwiki.apache.org/confluence/display/JCLOUDS/2020+-+January+Board+Report+Draft
Happy New Year, everyone!!
ap
I think we should assume the EOL of the 2.1.x branch and do not
cherry-pick
issues there unless they are critical security issues.
+1 to that from me, too.
ap
Done and sent.
Many thanks for the detailed additions and for taking care of this,
Ignasi!
ap
Hi all
A quick reminder that the report is officially due on Thu (day after
tomorrow) - please edit as appropriate!
Regards
ap
Hi all
Here the traditional skeleton page for the Oct report that's due next
week:
Will there be energy and availability to vote it?
I'll try to help out if needed. Thanks for bringing this up and taking
this on, Ignasi!
Regards
ap
Hi all
Here the traditional skeleton page for the Oct report that's due next
week:
https://cwiki.apache.org/confluence/display/JCLOUDS/2019+-+October+Board+Report+Draft
Please edit as appropriate!
Regards
ap
Original Message
Subject: jclouds Board Report due for October
I'm personally interested in knowing how old is this release.
The date of the announcement email was 2019-02-06:
http://mail-archives.apache.org/mod_mbox/jclouds-dev/201902.mbox/browser
I've opened a PR to fix the incorrect year on the site [1]. Thanks for
catching that!
Regards
ap
[1]
I've updated https://cwiki.apache.org/confluence/x/WCsyBw please help
me out integrating/editing it as you see fit.
Made a few small tweaks - thanks for putting that together!
Regards
ap
> The meeting is scheduled for Wed, 17 Jul 2019 at 10:30 PDT and the> deadline
> for submitting your report is 1 full week prior to that> (Wed Jul 10th)!
As per usual, here a skeleton page for the report:
https://cwiki.apache.org/confluence/display/JCLOUDS/2019+-+July+Board+Report+Draft
Regards
[x] +1 Approve the change
The meeting is scheduled for Wed, 17 Apr 2019 at 10:30 PDT and the
deadline for submitting your report is 1 full week prior to that (Wed
Apr 10th)!
Argh, totally missed this notification :-( Created the usual skeleton
page here:
I will open the PR during the week end.
Great, thank you!!
ap
infra jira ticket please
Done!
https://issues.apache.org/jira/browse/INFRA-17608
Regards
ap
Forwarding to users@infra...
ap
I don't think we want all these automated mails going to dev@; instead
they should go to notifications@. Does anyone know how we can change
this?
On Wed, Jan 09, 2019 at 09:00:37PM -, GitBox wrote:
gaul opened a new pull request #1: Remove stale Meetup
For the second part about provisioning feature, I need to do some
cleanup on the PoC before starting a concrete discussion.
Thanks for the update - looking forward to hearing more about these
ideas!
Regards
ap
[forwarding to Karim - @Karim, you may want to sign up to the mailing
list for this conversation]
On 2018-11-21 18:13, Ignasi Barrera wrote:
HI Kazim,
The best way to move forward and get things done is... just go ahead
and do
them :)
If you look at JCLOUDS-1387 and the pull request that
On the other hand, I was thinking about adding a Provisioning/Compute
Service for Karaf. The idea is to easily provision and bootstrap
Apache
Karaf runtime (vanilla or custom) on a cloud provider.
If I understand this correctly, the idea is firstly to use jclouds to
install (?) a Karaf
Hi all
Skeleton page for our Oct board report draft here:
https://cwiki.apache.org/confluence/display/JCLOUDS/2018+-+October+Board+Report+Draft
As noted, the official date on which Daniel became the latest committer
may need to be tweaked since I can't find an [ANNOUNCE] email for that.
* Since we will be pushing -mirror to the SF remote, will that trigger
an email notification for each commit object pushed? (That would be
potentially a huge email flood.
Could we perhaps temporarily direct notifications to a different email
group? That way, we could even preserve them if a
Hi all
===
Apache ID: andrewp
---
[X] +1 Release.
[ ] -1 Don't release (see notes).
---
Hi all
Seeing a couple of test failures on Windows:
*
FilesystemStorageStrategyImplTest.testDeletingInvalidPathFileEndsNormally
in filesystem
This is a known issue [1], although hopefully we are a little further to
figuring out what the behaviour should be. Added a comment to the PR [2]
Hi all
FYI on "Go cloud" - a/the new multi-cloud abstraction for Go:
https://blog.golang.org/go-cloud
So close with the name there! ;-)
Regards
ap
Hi all
I've created the "traditional skeleton page" for the July board report,
which is due on the 11th:
https://cwiki.apache.org/confluence/display/JCLOUDS/2018+-+July+Board+Report+Draft
Please edit as needed!
Regards
ap
I've added some notes to April's report at [1]
Thanks, Andrea! I've made some minor text edits, but the content overall
should be unchanged. One point regarding the paragraph about Dimension,
1&1 and Aliyun: there was some previous board feedback about how to
refer to companies in the public
I archived all the legacy-jclouds repositories today.
Thanks for taking care of that!
ap
That would be much better! :D
I tried that with the original setup and then needed to mess around a
bit to get some Python library incompatibilities to work, but in the end
it worked out.
Your version with the cURL call (but minus the need to compile OpenSSL
and cURL) is actually quicker
We don't have root/sudo root access to upgrade or install libs in the
slave, so I've modified the build to download and compile the latest
OpenSSL version
Argh, I should have explained the issue with the Javadocs build, which
had the same problem (amongst other things). An alternative solution
Hi all
Quick FYI that the Javadocs from HEAD are building again:
http://jclouds-javadocs.elasticbeanstalk.com/
Have a good weekend, everyone!
ap
Original Message
Subject: Jenkins build is back to normal : jclouds-aggregate-javadocs
#1063
Date: 2018-02-24 00:06
From:
I'd like another pair of eyes to validate it.
Thanks for setting that up, Andrea!
Just FYI that I added the new 2.1.x builds to some of the views, and
updated the groups settings so the publicly visible jobs match those in
the "public" view.
On a different Jenkins-related note: does anyone
A quick update on this: we're running the final tests before opening
the pull request.
Yeh!!
ap
> @demobox, all, please provide your comments as I'd like to send the report
>today possibly
Some phrasing edits in
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=74691908=7=6
- the statements themselves should be essentially unchanged.
A possible suggestion for next
Hi all
Just a quick FYI that I've put up the usual skeleton page for next
month's board report:
https://cwiki.apache.org/confluence/display/JCLOUDS/2018+-+January+Board+Report+Draft
Please edit as necessary.
Hope it's been a fun and relaxing holiday break for those who've been
able to take
+1 to file an issue to properly track this.
https://issues.apache.org/jira/browse/JCLOUDS-1361
Do you know if with our current plan we could have some Windows build
in CloudBees?
Based on
https://go.cloudbees.com/docs/cloudbees-documentation/dev-at-cloud/#operating-system,
I suspect the
It can be removed. His work was merged to master!
Done:
To https://andr...@git-wip-us.apache.org/repos/asf/jclouds.git
- [deleted] gsoc2016-ivan
Thanks for clarifying, Ignasi!
ap
However, I am unclear on why the test fails since the filesystem
blobstore should convert user input /
to backend fs separator \ on Windows. That is to say, code which runs
on Linux and Windows *should*
behave identically, although in previous releases they did not.
PR to prevent the test
Hi all
Is the "gsoc2016-ivan" branch [1] still needed? The last commit was in
Aug 2016, and at this point it's 496 commits behind master.
Please ping if the branch is still required, otherwise I'll remove it
over the weekend.
Thanks!
ap
[1]
Please use this thread for discussion of issues uncovered in the RC,
questions you may have about the RC, etc.
The following test fails repeatedly for me on Windows:
Failed tests:
FilesystemStorageStrategyImplTest.testDeletingInvalidPathFileEndsNormally:695
Deleting an invalid path ended
> Independently of this I would like to change all the READMEs to point
> to
> our new JIRA and GitHub URLs:
> https://github.com/jclouds/legacy-jclouds/pull/1584
Added a quick comment about that; +1 regarding the repository archiving,
especially as that seems to be a reversible change, if for
Hi all
Just a quick heads-up that I've extended the validity of my code signing
key 892E5D10 [1, 2], which was due to expire. If you run into any key
expiration errors in future for releases signed by that key, please
refresh it locally be re-retrieving it from pgp.mit.edu.
Thanks!
ap
[1]
@gaul, could you have a look at the failures, as most of them appear
in the filesystem provider and S3 classes?
It looks as though BlobMetadata.getTier is returning null, even though
according to the interface definition [1] it should be non-null?
Regards
ap
[1]
Hi Julio
Is this email address been monitored?
These emails have ended up in our moderation queue but should have been
released successfully - at least, I've seen the previous one and your
follow-up come through, and they also appear in the list history.
You may wish to subscribe to the
I've added my comments. As usual, please fix/amend where needed.
Thanks, Ignasi! Some text edits at
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=71013050=5=4.
@Ignasi: please check that I haven't accidentally changed the meaning of
any of your comments.
Done :)
Wow, that was instant - thanks, Ignasi!
ap
Created a fix for the azure failure below at
@Svet: given that this is still open and the release has gone through,
would it make sense to add this as a Known Issue?
https://github.com/jclouds/jclouds-site/pull/198/files#r125906893
Regards
ap
Hi all
Time for the next board report, due by July 12th. I've created a
skeleton draft page at:
https://cwiki.apache.org/confluence/display/JCLOUDS/2017+-+July+Board+Report+Draft
Please add/amend as desired!
Regards
ap
If there are no objections, I plan to start the release process this
week.
Sounds good to me - thanks for volunteering to lead this again, Ignasi!
ap
Hi Kishore
Andrew G. is travelling for most of June, as far as I understand, so
will likely be a bit slower to respond. Thanks for your patience!
ap
On 2017-06-05 23:42, Battula Kishore wrote:
Hi Andrew,
Any update on this?
-- Thanks
-- Kishore
On 29/05/17, 1:06 PM, "Battula
* Do you agree to deprecate and remove Azure Classic?
* If so, should we remove it in the next major (2.1.0) or wait for the
next one, 2.2.0?
Also +1 on removing this in 2.1.0 - perhaps send a heads-up out to the
user list to see how many (if any) people are using it that might need
more time
I just wanted to say thanks for your quick and great support.
A big +1 to that - many thanks for helping out!
ap
FYI...
ap
Original Message
SUBJECT:
DEV@cloud planned maintenance
DATE:
2017-04-13 14:03
FROM:
"CloudBees, Inc."
View this email in your browser [1]
Yes, it still needs to be improved :)
Ah, thanks for confirming, Ignasi! Tweaked that and made a couple of
other minor changes:
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=68719231=4=3
Regards
ap
I elaborated the points a little bit, as this kind of format is the
preferred one by the board.
Thanks, Ignasi!
Is the "Cluster of activity in OpenStack Swift provider."
sentence/bullet point still intended to be there? If so, we should
probably phrase it in a similar "longhand" style?
Hi all
A quick reminder that this is due in just over a week...
Regards
ap
On 2017-03-15 16:18, Andrew Phillips wrote:
Hi all
In preparation for next month's board report, I've created the usual
draft page in the Wiki:
https://cwiki.apache.org/confluence/display/JCLOUDS/2018+-+April+Board
FYI...
ap
Original Message
SUBJECT:
DEV@cloud planned maintenance
DATE:
2017-03-31 14:33
FROM:
"CloudBees, Inc."
TO:
1 - 100 of 1315 matches
Mail list logo