Re: move jclouds to the attic?

2022-10-17 Thread Andrea Turli (apache.org)
Quite sad to read. End of an era, at least for me 😢
Learned so much from this project and its community, I wouldn't be the same
person if I hadn't been part of it.

Thanks

On Sun, Oct 16, 2022 at 10:18 PM cen  wrote:

> That is quite sad to hear but not entirely unexpected.
>
> I've been using jclouds on and off for the past 5 years, mainly for
> cloud storage and some cloud VM management.
>
> Nowadays for the IaC use case, to me at least, the declarative tools
> such as Terraform make more sense.
>
>
> I would like to thank the jclouds community for making my life as
> developer easier all these years.
>
>
> Best regards
>
> On 10/10/2022 15:03, 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.
> >
>


Re: tokens and oauth

2019-01-18 Thread Andrea Turli (apache.org)
Hi John,

would this discussion help with your task?
https://stackoverflow.com/questions/51296465/manual-authentication-for-aws-ec2-api-in-jclouds-separating-token-acquisition

I think as Ignasi said it is important to know which API or provider
are you going to focus on?

On Fri, Jan 18, 2019 at 3:53 PM Ignasi Barrera  wrote:
>
> Hi,
>
> Could you give us some more details? What API are you talking to? what 
> jclouds provider are you using?
>
> On Thu, 10 Jan 2019 at 19:19, john.calc...@gmail.com  
> wrote:
>>
>> Hi Andrew,
>>
>> I've been asked to look into converting our jclouds-based cloud client to 
>> use tokens for authentication. The specific ask was to use OAuth tokens, but 
>> I think tokens in general would be a good start. At the moment, we just use 
>> the root account access/secret keys to authenticate, but this was never 
>> intended to be a long-term solution. We need a way to allowing our users to 
>> limit the access of the credentials they supply to our application.
>>
>> Can you please point me to some docs or examples that show how this is done? 
>> I don't even know where to begin looking in jclouds java code for the right 
>> APIs.
>>
>> Thanks,
>> John


Re: Upgrading to TLSv1.2 in Jcloud...

2018-04-13 Thread Andrea Turli (apache.org)
I think you may want to extend SoftLayerHttpApiModule to
configure `OkHttpClientSupplier` similarly to [1] which uses [2] and inject
it in your BlobStoreContext
[1]:
https://github.com/jclouds/jclouds/blob/master/apis/docker/src/main/java/org/jclouds/docker/config/DockerHttpApiModule.java#L44
[2]:
https://github.com/jclouds/jclouds/blob/master/apis/docker/src/main/java/org/jclouds/docker/config/DockerOkHttpClientSupplier.java

I couldn't test the solution but I'd start from there

Please let us know, as eventually we may need to improve softlayer to
support natively TLSv1.2

BTW, which java version are you using?

Andrea

On Fri, Apr 13, 2018 at 4:03 PM Pratheesh 
wrote:

> Hi Andrea,
>
>
>
> Please let me know any location or sample URL  that I can see a sample.
>
>
>
> However I already tried with following sample code..
>
>
>
> System.setProperty("https.protocols", "TLSv1.2");
>
> System.setProperty("jdk.tls.client.protocols",
> "TLSv1,TLSv1.1,TLSv1.2");
>
> Module tlsModule = new AbstractModule() {
>
> @Override
>
> protected void configure() {
>
>
> bind(OkHttpClientSupplier.class).to(TLSOkHttpClientSupplier.class);
>
> }
>
> };
>
> Iterable modules1 = ImmutableSet.of(tlsModule, new
> OkHttpCommandExecutorServiceModule());
>
> BlobStoreContext context = ContextBuilder.newBuilder("swift")
>
> .modules(modules1)
>
> .endpoint("https://tok02.objectstorage.softlayer.net/auth/
> ")
>
> .credentials("userId", "pwd")
>
> .buildView(BlobStoreContext.class);
>
>
>
>
>
> This gives me following error:
>
>
>
> Exception in thread "main" org.jclouds.http.HttpResponseException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target connecting to GET
> https://tok02.objectstorage.softlayer.net/auth/v1.0 HTTP/1.1
>
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:117)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:491)
>
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:37)
>
> at com.sun.proxy.$Proxy47.invoke(Unknown Source)
>
> ….
>
> ….
>
> Exception in thread "main" org.jclouds.http.HttpResponseException:
> sun.security.validator.ValidatorException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target connecting to GET
> https://tok02.objectstorage.softlayer.net/auth/v1.0 HTTP/1.1
>
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:117)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:491)
>
> at
> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:37)
>
> at com.sun.proxy.$Proxy47.invoke(Unknown Source)
>
> …
>
>
>
> Caused by: sun.security.provider.certpath.SunCertPathBuilderException:
> unable to find valid certification path to requested target
>
> at
> sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:144)
>
> at
> sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:130)
>
> at
> java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280)
>
> at
> sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:382)
>
>
>
> *From:* Andrea Turli [mailto:andrea.tu...@gmail.com]
> *Sent:* Friday, April 13, 2018 6:27 PM
> *To:* user@jclouds.apache.org
> *Subject:* Re: Upgrading to TLSv1.2 in Jcloud...
>
>
>
> Hi,
>
>
>
> Pretty sure that jclouds can support your scenario by injecting
> OkHttpClientDriver in the context.
>
> See Docker provider for an example
>
>
>
> HTH,
>
> Andrea
>
>
>
> Il ven 13 apr 2018, 14:41 Pratheesh  ha
> scritto:
>
> We are using JClouds 1.9.1  to upload files to Softlayer. Recently
> softlayer upgraded to TLSv1.2. So our existing code is failing.
>
>
>
> What  we have to change in Jclouds to support TLSv1.2, so that it can
> upload files to Sof

[ANNOUNCE] Apache jclouds 2.1.0 released

2018-02-22 Thread Andrea Turli (apache.org)
The Apache jclouds team is pleased to announce the release of jclouds 2.1.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:
http://www.apache.org/dyn/closer.lua/jclouds

The Maven artifacts for the release are available in Maven Central,
under the org.apache.jclouds group ID.

The full change log is available here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314430&version=12334714

We welcome your help and feedback. For more information on how to
report problems, and to get involved, visit the project website at
http://jclouds.apache.org/

The Apache jclouds Team


[ANNOUNCE] Apache jclouds 1.9.3 released

2016-11-23 Thread Andrea Turli (apache.org)
The Apache jclouds team is pleased to announce the release of jclouds
1.9.3.

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:
http://www.apache.org/dyn/closer.lua/jclouds

The Maven artifacts for the release are available in Maven Central, under
the org.apache.jclouds group ID.

The full change log is available here:
https://issues.apache.org/jira/browse/JCLOUDS/fixforversion/12336847

We welcome your help and feedback.

For more information on how to  report problems, and to get involved, visit
the project website at http://jclouds.apache.org/

The Apache jclouds Team