Re: move jclouds to the attic?
Agreed, if any show stoppers, I can carve out time to help. On Sat, Mar 9, 2024 at 10:58 PM Andrew Gaul wrote: > On Mon, Oct 10, 2022 at 10:03:07PM +0900, Andrew Gaul wrote: > > jclouds development has slowed from 123 commits from 26 contributors in > > 2018 to just 24 from 6 contributors in 2022. This is despite growing > > downloads over the last 12 months from 50,000 to 80,000 for jclouds-core > > alone. Unfortunately the number of active committers has shrunk and we > > will soon lack quorum for future releases. This means that the project > > must move to the Apache attic. > > > > Ideally the community could step up to sustain the project, e.g., > > reviewing pull requests, fixing issues, responding to mailing list > > queries, and eventually becoming committers themselves. Does anyone > > have a multi-year interest in jclouds that wants to help out? > > > > If not, I will cut a final 2.6.0 release before retiring the project. > > Revisiting this after the 2.6.0 release two years later, I believe more > strongly than ever that we should archive jclouds. I lack the domain > knowledge and enthusiasm to maintain the project and no one else has > stepped forward. Let's give users a month to report 2.6.0 regressions > then proceed with archiving if there are no showstoppers? > > -- > Andrew Gaul > http://gaul.org/ >
Re: move jclouds to the attic?
On Mon, Oct 10, 2022 at 10:03:07PM +0900, Andrew Gaul wrote: > jclouds development has slowed from 123 commits from 26 contributors in > 2018 to just 24 from 6 contributors in 2022. This is despite growing > downloads over the last 12 months from 50,000 to 80,000 for jclouds-core > alone. Unfortunately the number of active committers has shrunk and we > will soon lack quorum for future releases. This means that the project > must move to the Apache attic. > > Ideally the community could step up to sustain the project, e.g., > reviewing pull requests, fixing issues, responding to mailing list > queries, and eventually becoming committers themselves. Does anyone > have a multi-year interest in jclouds that wants to help out? > > If not, I will cut a final 2.6.0 release before retiring the project. Revisiting this after the 2.6.0 release two years later, I believe more strongly than ever that we should archive jclouds. I lack the domain knowledge and enthusiasm to maintain the project and no one else has stepped forward. Let's give users a month to report 2.6.0 regressions then proceed with archiving if there are no showstoppers? -- Andrew Gaul http://gaul.org/
2.6.0 release remaining bits
As usual the jekyll release notes and javadoc push failed for me. Careful readers of the ANNOUNCE mail might has seen the link to https://github.com/apache/jclouds-site/blob/master/releasenotes/2.6.0.md instead of the expected https://jclouds.apache.org/releasenotes/2.6.0 to work around this. The deploy script does not work since it uses a very old Ruby 2.2 that our very old jekyll depends on. I don't think this is addressable since Debian removed packages for older versions. From my perspective, the 2.6.0 jars pushed and this is the extent of my interest. But if someone else wants to untangle this please do the needful. -- Andrew Gaul http://gaul.org/
[ANNOUNCE] Apache jclouds 2.6.0 released
The Apache jclouds team is pleased to announce the release of jclouds 2.6.0. Apache jclouds is an open source multi-cloud toolkit for the Java platform that gives you the freedom to create applications that are portable across clouds while giving you full control to use cloud-specific features. The source archives for the release are available here: https://jclouds.apache.org/start/install/ The Maven artifacts for the release are available in Maven Central, under the org.apache.jclouds group ID. The release notes are available here: https://github.com/apache/jclouds-site/blob/master/releasenotes/2.6.0.md We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at: https://jclouds.apache.org/ The Apache jclouds Team -- Andrew Gaul http://gaul.org/
Re: [RESULT][VOTE] Release Apache jclouds 2.6.0 RC1
On Sun, Mar 03, 2024 at 05:09:19PM +0900, Andrew Gaul wrote: > This is the first release candidate for Apache jclouds 2.6.0. > > Please use the separate [DISCUSS] thread for anything but votes. > > It fixes the following issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351495=Html=12314430=Create_token=A5KQ-2QAV-T4JA-FDED_a98e450e565e5b47fb45f0565ddaf120ea9eb742_lin > > *** Please download, test and vote by Thursday, March 7th, 09:00 PDT / 12:00 > EDT / 18:00 CET. The vote is now closed, and with 3 binding +1s, we're ready to release. -- Andrew Gaul http://gaul.org/
Re: [VOTE] Release Apache jclouds 2.6.0 RC1
On Sun, Mar 03, 2024 at 05:09:19PM +0900, Andrew Gaul wrote: > This is the first release candidate for Apache jclouds 2.6.0. > > Please use the separate [DISCUSS] thread for anything but votes. > > It fixes the following issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351495=Html=12314430=Create_token=A5KQ-2QAV-T4JA-FDED_a98e450e565e5b47fb45f0565ddaf120ea9eb742_lin +1, binding. Ran integration tests and verification script. -- Andrew Gaul http://gaul.org/
Re: [DISCUSS] Release Apache jclouds 2.6.0 RC1
On Sun, Mar 03, 2024 at 08:27:14PM +0900, Andrew Gaul wrote:
> On Sun, Mar 03, 2024 at 05:10:29PM +0900, Andrew Gaul wrote:
> > This thread is for discussion of the third release candidate for Apache
> > jclouds 1.6.3.
>
> Sorry about the cut and paste -- this should be the first release
> candidate of Apache jclouds 2.6.0.
I ran integration tests against a variety of providers. I found an
issue with Backblaze B2 that succeeds with 2.5.0 and fails with 2.6.0
that I cannot explain. Given that S3Proxy works with 2.6.0 and B2 I
assume that this is a test-only issue and will not block the release.
AWS-S3
[ERROR] Failures:
[ERROR] org.jclouds.aws.s3.AWSS3ClientLiveTest.AWSS3ClientLiveTest
[ERROR] Run 4: AWSS3ClientLiveTest.testV4SignatureOps:147 » HttpResponse
Server rejected operation connecting to PUT
https://gaul-blobstore20eu.s3.amazonaws.com/test-blob?X-Amz-Security-Token==AWS4-HMAC-SHA256=AKIAITMZ4YFWHBLA4KMA/20240308/us-east-1/s3/aws4_request=20240308T100912Z=900=host=e268055b61a87920c1ac0d55a10b45bf67db1d9deaee2d23c1e6975f9645d819
HTTP/1.1
[ERROR] Run 7:
AWSS3ClientLiveTest>S3ClientLiveTest.testCopyCannedAccessPolicyPublic:174 »
AWSResponse request PUT https://gaul-blobstore19.s3.amazonaws.com/pears
HTTP/1.1 failed with code 400, error: AWSError{requestId='Q245TFG97DHGKSK5',
requestToken='9/vRVlLtS/lLDuZ0WwGxf5jCbnVIkGTlRIEepH+gceXHXFYpnSK5JcIKCtCI4ToJdsVK9YHlDQk=',
code='AccessControlListNotSupported', message='The bucket does not allow
ACLs',
context='{HostId=9/vRVlLtS/lLDuZ0WwGxf5jCbnVIkGTlRIEepH+gceXHXFYpnSK5JcIKCtCI4ToJdsVK9YHlDQk=}'}
[ERROR] Run 22:
AWSS3ClientLiveTest>S3ClientLiveTest.testPublicReadOnObject:301 » AWSResponse
request PUT https://gaul-blobstore18.s3.amazonaws.com/public-read-acl HTTP/1.1
failed with code 400, error: AWSError{requestId='WVD74F6PW1JCHATK',
requestToken='MBw3qk/pAw4T/mFGUEwO4QEf2Oio5wf+eMu6t2LFK2zFllPgl+e8Mzwv8o64oyqd4khYbjjyNdM=',
code='AccessControlListNotSupported', message='The bucket does not allow
ACLs',
context='{HostId=MBw3qk/pAw4T/mFGUEwO4QEf2Oio5wf+eMu6t2LFK2zFllPgl+e8Mzwv8o64oyqd4khYbjjyNdM=}'}
[ERROR] Run 23:
AWSS3ClientLiveTest>S3ClientLiveTest.testPublicWriteOnObject:201 » AWSResponse
request PUT https://gaul-blobstore19.s3.amazonaws.com/public-read-write-acl
HTTP/1.1 failed with code 400, error: AWSError{requestId='VT84J0P44WB2P8WJ',
requestToken='Ethy7OW4Zb65hWcOhmQAigV+VmM97t4w1iazfa2UKiP+X63YbcbYtoc+PEOozhpHoA2zgMsJWE8=',
code='AccessControlListNotSupported', message='The bucket does not allow
ACLs',
context='{HostId=Ethy7OW4Zb65hWcOhmQAigV+VmM97t4w1iazfa2UKiP+X63YbcbYtoc+PEOozhpHoA2zgMsJWE8=}'}
[ERROR] Run 24:
AWSS3ClientLiveTest>S3ClientLiveTest.testPutCannedAccessPolicyPublic:154 »
HttpResponse Server rejected operation connecting to PUT
https://gaul-blobstore26.s3.amazonaws.com/hello HTTP/1.1
[ERROR] Run 26:
AWSS3ClientLiveTest>S3ClientLiveTest.testUpdateBucketCannedACL:718 »
Authorization Access Denied
[ERROR] Run 27: AWSS3ClientLiveTest>S3ClientLiveTest.testUpdateObjectACL:245
» AWSResponse request PUT
https://gaul-blobstore18.s3.amazonaws.com/private-acl?acl HTTP/1.1 failed with
code 400, error: AWSError{requestId='0A93WEXJKAB7588G',
requestToken='fYTh0JqlHSPcE+JKdGmcKP0ExLmmeaDYv9do/+nWPo7SI5j6/RXh1wzAU1NUB5Z2a5fchzAEXqo=',
code='UnresolvableGrantByEmailAddress', message='The e-mail address you
provided does not match any account on record.',
context='{HostId=fYTh0JqlHSPcE+JKdGmcKP0ExLmmeaDYv9do/+nWPo7SI5j6/RXh1wzAU1NUB5Z2a5fchzAEXqo=,
EmailAddress=ja...@misterm.org}'}
[ERROR] Run 28:
AWSS3ClientLiveTest>S3ClientLiveTest.testUpdateObjectCannedACL:739 »
Authorization Access Denied
[ERROR] Run 29:
AWSS3ClientLiveTest>BaseBlobStoreIntegrationTest.destroyResources:118->BaseBlobStoreIntegrationTest.deleteEverything:210
» RejectedExecution Rejected execution of task [class
com.google.common.util.concurrent.TrustedListenableFutureTask] since the
executor is shutdown.
[ERROR]
org.jclouds.aws.s3.blobstore.integration.AWSS3BlobIntegrationLiveTest.AWSS3BlobIntegrationLiveTest
[ERROR] Run 33:
AWSS3BlobIntegrationLiveTest>BaseBlobIntegrationTest.testPutBlobAccess:770 »
HttpResponse Server rejected operation connecting to PUT
https://gaul-blobstore18.s3.amazonaws.com/put-access-blob-name-public HTTP/1.1
[ERROR] Run 34:
AWSS3BlobIntegrationLiveTest>BaseBlobIntegrationTest.testPutBlobAccessMultipart:792
» AWSResponse request POST
https://gaul-blobstore28.s3.amazonaws.com/put-access-blob-name-public?uploads
HTTP/1.1 failed with code 400, error: AWSError{requestId='Q096EP8KHFQ2A9PP',
requestToken='MJ/XQvC7jjoDp9fattu7jBc46nTQVDZXIA+NlFQvqUjKjEb7hQ2J+ApHJkP0EC5KAGXUnJap/cg6W8YDX6rimRAdkk0zv4AdAp9G1YJoYY8=',
code='AccessControlListNotSupported', message='The bucket does not allow
ACLs',
context='{HostId=MJ/XQvC7jjoDp9fattu7jBc46nTQVDZXIA+NlFQvqUjKjEb7hQ2J+ApHJkP0EC5KAGXUnJap/cg6W8YDX6rimRAdkk0zv4AdAp9G1YJoYY8=}'}
[ERROR] Run 49:
