Forwarding with the jclouds users list address fixed
On Mon, Jan 30, 2023 at 10:15 AM Ignasi Barrera wrote:
> Hi!
>
> This is a call to action for everyone that expressed interest in helping
> keep the project alive.
> There has been a concrete request for hel
Thanks for starting this thread Gaul!
+1 to move the project to the Attic if there is no active community anymore,
On Mon, Oct 10, 2022 at 3:03 PM Andrew Gaul wrote:
> jclouds development has slowed from 123 commits from 26 contributors in
> 2018 to just 24 from 6 contributors in 2022. This
ve access to the latest through GitHub. Not so?
>
> On Thu, May 5, 2022 at 3:43 PM Ignasi Barrera wrote:
>
>> Hi!
>>
>> Contributing to jclouds should be as easy as opening a pull request in
>> GitHub, and you don't need an ASF account for that.
>> What resour
Hi!
Contributing to jclouds should be as easy as opening a pull request in
GitHub, and you don't need an ASF account for that.
What resources do you need access to that are not available? Is it Slack?
On Thu, May 5, 2022 at 5:30 PM John Calcote wrote:
> I would love to contribute, however, ASF
I agree on not including labs providers in jclouds releases anymore
and just publishing the snapshots.
If anyone is interested in promoting a provider, pull requests are
welcome to have them moved to the main repository!
On Fri, Dec 17, 2021 at 11:40 AM Ignasi Barrera
wrote:
>
> +1
>
+1
On Fri, Dec 17, 2021 at 7:46 AM Andrew Gaul wrote:
>
> I opened https://github.com/apache/jclouds/pull/127 to move the glacier
> provider to main repo. I propose removing all the labs integration from
> the release process which means the following will only publish as
> SNAPSHOTs:
>
>
treamline the release maybe by
> getting rid of labs or removing some other complexity.
>
> On Sun, Sep 19, 2021 at 12:57:21PM +0200, Ignasi Barrera wrote:
> > Yeah, that's annoying. This is why we created the release script [1] and
> > updated the versions manually there.
Yeah, that's annoying. This is why we created the release script [1] and
updated the versions manually there. It's been a long time, though.
Probably this can be revisited and done in a much better and less hacky way.
[1] https://dist.apache.org/repos/dist/dev/jclouds/prepare_release.sh
On
That's weird...
The last build from master shows successful logs for uploading the snapshot
artifacts:
https://ci-builds.apache.org/job/JClouds/job/jclouds/18/consoleFull
But clicking on those you get a 404... Probably something wrong with the
Apache snapshots repo to be taken to ASF infra?
On
> But in general you are right of course. For me in particular, the problem
is: I cannot shade transient dependencies, because all the imports in
jclouds have to be
changed accordingly. Therefore, doing the shading in jclouds ist the only
intermediate way to get the new jclouds into my jenkins
Hi!
It should be already configurable. Can you try setting the custom endpoint
when creating the context? Something like:
ContextBuilder.newBuilder("azureblob")
.endpoint("https://${jclouds.identity}.blob.core.usgovcloudapi.net;)
I.
On Thu, Feb 25, 2021 at 9:44 AM Jean-Noël Rouvignac
I'd say those three are mostly the dependencies we have. We don't have
much more, but those three are definitely the main pain points.
On Fri, Jun 19, 2020 at 3:38 PM Andrew Gaul wrote:
>
> We have had many reports of Guava version incompatibilities in recent
> years. To address this, I
The Apache jclouds team is pleased to announce the release of jclouds 2.1.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 Apache jclouds team is pleased to announce the release of jclouds 2.2.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.
It's not directly possible to configure max retries per command, but with a
little bit of code, you can do it.
First, let's create a custom retry handler that will read a custom
configured value for each command. Custom values will be configured via
context properties as follows:
// If the API
No, Joyent is not one of the currently supported providers
On Tue, 5 Feb 2019 at 22:14, john.calc...@gmail.com
wrote:
> Hi all --
>
> Anyone know if joyent triton (private cloud service) is supported by
> jclouds? My preliminary research says no, but if anyone else knows better,
> I'd
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
Hi Fritz,
That is indeed a real issue, and the main blocker to have it implemented is
the availability of volunteer time to develop that. Currently, no one in
the jclouds team is actually paid to work on jclouds. The project is a 100%
volunteer effort, which makes it difficult to commit to
gate it over the next few days.
>
> Regards
>
> John
>
> On 2018/11/22 00:00:07, Ignasi Barrera wrote:
> > Interesting.
> >
> > I see it supports Apache HttpClient and OkHttp, and we support both as
> http
> > drivers.
> >
> > Actuall
gued but
> the more customisation it brings to logging, but was struggling to work out
> how to use something like this with JClouds. My best guess was to see if
> we could customise the rest client used - to one supported by logbook.
>
> [1]: https://github.com/zalando/logbook
>
>
Hi John,
Can you elaborate a bit?
If you use the SLF4j driver with Logback, could you achieve what you need
with its Mapped Diagnostic Context [1]?
I.
[1] https://logback.qos.ch/manual/mdc.html
On Wed, 21 Nov 2018 at 23:14, John McDonnell
wrote:
> Hi,
>
> I use JClouds for creating
Looks like a reasonable patch. Wanna open a pull request?
On Tue, 16 Oct 2018 at 12:10, Mahmoud Ismail
wrote:
>
> Hello,
>
> I was trying to create a local ssd disk (NVMe) to my vm instance on GCE and i
> got this null pointer exception
>
> ! java.lang.NullPointerException: Null sourceImage ! at
The Apache jclouds team is pleased to announce the release of jclouds 2.1.1.
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.
Looks like the SSL certificate for the API endpoint has a wrong CN? it
seems to have been issued just today
SSL Server Certificate
Issued To
Common Name (CN)u2.shared.global.fastly.net
Organization (O)
Fastly, Inc.
Organizational Unit (OU)
Issued By
Common Name (CN)
GlobalSign CloudSSL CA -
Yeah! :)
On 21 June 2018 at 16:41, Ranjith R wrote:
> Thanks Ignasi. That worked.
>
> Thanks,
> Ranjith
>
> On Thu, Jun 21, 2018 at 4:03 PM Ignasi Barrera wrote:
>
>> I haven't tried it, but you should be able to define a Guice module that
>> extends th
I haven't tried it, but you should be able to define a Guice module that
extends the default S3 module and overrides the request signer
configuration. Then you can pass that one to the list of modules you pass
when creating the context:
@ConfiguresHttpApipublic static class S3V4SignerModule
Jayshankar
> On Thursday, June 21, 2018, 2:43:25 PM GMT+5:30, Ignasi Barrera <
> n...@apache.org> wrote:
>
>
> You declare the local variable "overrides" in a different method where you
> use it.
>
> No offense, but just use a proper IDE to write your code.
You declare the local variable "overrides" in a different method where you
use it.
No offense, but just use a proper IDE to write your code. We can help you
understand how jclouds works, and use it with your OpenStack distribution.
We'll be more than happy to help there, but we're not here to
HttpCommandExecutorServ
> ice.writePayloadToConnection(JavaUrlHttpCommandExecutorService.java:295)
> at org.jclouds.http.internal.JavaUrlHttpCommandExecutorServ
> ice.convert(JavaUrlHttpCommandExecutorService.java:171)
> at org.jclouds.http.internal.JavaUrlHttpCommandExe
s.SCOPE, "domain:default");
>
>
> novaApi = ContextBuilder.newBuilder("openstack-nova")
>.endpoint("https://192.168.0.12:5000/v3;)
>.credentials("ldap:foo", "bar")
> .overrides(overrides)
>.buildApi(NovaApi.class);
>
> Cheers
> Archana
>
> On 2018/06/21 08:00:01, Ignasi Barrera wrote:
> > Hi Archana,
> >
> > I see the problem here. When using temporary credentials in AWS, the
> > session token must be included in a request header [1], so you need to
> &
You just need to provide the access tokens, and when using temporary
credentials you need to build the ContextBuilder providing the access
tokens and the session token too. See this [1] for more details (and let's
try to continue the discussion there to avoid having the info spread in two
places).
Hi Archana,
I see the problem here. When using temporary credentials in AWS, the
session token must be included in a request header [1], so you need to
provide it when configuring the jclouds context with the credentials.
By default, the "ContextBuilder.credentials" signature does only allow to
Properties
> location: class JCloudsNova
> JCloudsNova.java:55: error: cannot find symbol
>.overrides(overrides)
> ^
> symbol: variable overrides
> location: class JCloudsNova
> 4 errors
>
> Is there a link where i can download v3 jcloud
nt_id)s
> |
>
> +--+---+--+--+-+---++
>
>
> The command nova list is not present.
>
> Are there any other api examples related to J
Hi Archana,
There is no explicit support to pass the IAM role based authentication when
creating the jclouds context. It has to be created with the access and
secret key.
I don't know the internals of the simian army, but if you have access to
the instance metadata you could query it to get the
while
>> executing maven. The lib directory content is as below.
>>
>> [root@localhost jclouds]# mvn dependency:copy-dependencies
>> "-DoutputDirectory=./lib"
>> [INFO] Scanning for projects...
>> [INFO]
>> [INFO] ---< org.apac
That tutorial is a bit outdated. Did you use the exact pom.xml referenced
there to build the "lib" folder?
A quick look shows that the Neutron groupId is wrong. Now it is
"org.apache.jclouds.api". Could you verify it, and that you get all deps
without errors? Could you share the contents of the
;
>
>
> Regards
>
> Pratheesh
>
>
>
> *From:* Ignasi Barrera [mailto:n...@apache.org]
> *Sent:* Tuesday, April 17, 2018 12:11 PM
>
> *To:* user@jclouds.apache.org
> *Subject:* Re: Upgrading to TLSv1.2 in Jcloud...
>
>
>
> I'd say the config is OK (wi
I'd say the config is OK (without having seen the implementation of your
TLSOkHttpClientSupplier).
The error you get is a common error when the certificate is not trusted.
Could that be possible? Which concrete version of Java 8 are you using?
Just to discard a certificate trust issue, could you
It is unlikely that we bump the JSR version in the 2.0.x branch since
we don't want to introduce dependency issues in patch versions. That's
why the change has only been made in master.
Regarding Guava, there is an ongoing discussion to update the
dependency here. You can monitor it and
The Apache jclouds team is pleased to announce the release of jclouds 2.0.2.
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.
I'll be working on completing that PR and fixing this issue this week.
On 24 May 2017 at 09:23, Tomasz Wojtun wrote:
> There is a pull request https://github.com/jclouds/jclouds/pull/1006 with the
> functionality but it needs some tweaks.
>
> BR,
> Tomek
>
> On
commands so I can
>> preserve history?
>>
>> Related, we could promote Backblaze B2 from labs to core. From my
>> biased perspective this implementation has high quality. B2 lacks a
>> provider guide which I could also write next week.
>>
>> On Tue, Mar 21
There is no reason AFAIK. Mind opening a bug in JIRA?
This also looks pretty straightforward to fix, do you want to try
submitting a pull request with the patch? I'll be happy to help!
I.
On Apr 4, 2017 2:00 AM, "Paya, Ashkan" wrote:
> Hello,
>
> According to
This is a different error: an Authorization one.
Are you providing the right credentials? jclouds expects by default
the credentials in the following form:
identity = "tenantName:userName"
credential = "password"
Are you providing the credentials in that format?
On 16 March 2017 at 16:21,
Looks like a DNS or name resolvong issue?
Caused by: java.net.UnknownHostException: identity.api.x86.trystack.org
On Mar 12, 2017 7:14 AM, "Rupinder Singh" wrote:
> Hello.
>
> I'm beginning with jclouds openstack with trystack following getting
> started tutorial
>
>
Hi Ignasi.
>
> I will be glad to make a pull request. Can you tell me if there is an easy
> way to test the fix in IDE?
>
> Regards,
> Tomasz
>
> On 07/03/2017, 14:32, "Ignasi Barrera" <n...@apache.org> wrote:
>
> Hi Tomasz,
>
> You'
Hi Tomasz,
You're right. jclouds should not fail in that case, The
"diskuRIToImage" in the InstanceToNodeMetadata class is a cache, and
it makes no sense to try to load a "null" key. I'd say the right way
to fix it is just to execute this [1] only if the input disk's source
is not null. Do you
The Apache jclouds team is pleased to announce the release of jclouds 2.0.1.
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.
You should try to keep the context open as long as possible, and reuse it
when needed.
A context itself does not hold any connection to external services. It just
provides the container for the IoC framework used in jclouds (Guice), and
the different ExecutorService instances jclouds uses to
Could you share the code you use to get the blob store context? IIRC
when using the "region scoped" one you need to specify the region.
Something like:
RegionScopedBlobStoreContext ctx =
contextBuilder.buildView(RegionScopedBlobStoreContext.class); // with
your modules
BlobStore
It looks like the OOM exception is thrown when writing the wire logs. When
using the blob store apis you might see binary data in the logs, as the
"jclouds.wire" logger logs the response/request payloads which might be
huge for some blobs and can cause this kind of exceptions.
Could you try
Hi Jeff,
There is no default way to add arbitrary headers to the requests generated
by jclouds. The approach I'd recommend is to use the OkHttp driver and its
interceptor mechanism. Here is how you can set it up:
* First, configure the OkHttp driver when creating the context by adding
its module
Hi!
The Azure ARM provider has been around for a while, and now it will
have support for all the compute extensions (security groups and
images). It is the recommended API to use, so I wanted to start a
discussion about removing the old "azurecompute" provider.
It is still in labs, all the
ned
> below...
>
> --Ryan
>
>
> On Jan9 9:00 AM, Ignasi Barrera wrote:
>>
>> Hi Ryan,
>>
>> Apologies for the late reply. The problem here is that no v2.0
>> identity endpoint is returned in the service catalog. As you say,
>> jclouds does the versi
Hi Ryan,
Apologies for the late reply. The problem here is that no v2.0
identity endpoint is returned in the service catalog. As you say,
jclouds does the version discovery and it can only work with the
endpoints returned in the service catalog. An initial request is
performed to authenticate the
e=false}], supportsImage=ALWAYS_TRUE, userMetadata={
> maxDataDiskCount=1}}
>
This is the first time I see this error. Do you have a complete stacktrace?
HTH!
>
>
>
>
>
>
> *From:* Ignasi Barrera [mailto:n...@apache.org]
> *Sent:* Saturday, January 7, 2017 5:17 AM
>
> *To:*
Good to see you progressed!
You're almost there. The error you are getting is because the Azure ARM
provider needs some additional configuration properties.
As you might have already seen, when creating the jclouds context you can
pass a set of configuration properties. This is done here [1] in
Pom.xml is ‘processed’ by mvn, I can build a .jar file that uses the
> jclouds API’s?
>
> http://jclouds.apache.org/start/compute/
>
> Java -jar …
>
> Again, maybe this is just an mvn / Java preference but why doesn’t the Azure
> ARM example show this? Instead it just sho
s://github.com/jclouds/jclouds-labs/tree/master/azurecompute-arm
You might also find the following talks useful:
https://speakerdeck.com/nacx/rule-the-cloud-with-apache-jclouds
http://feathercast.apache.org/apachecon-na-2016-rule-the-cloud-with-apache-jclouds-ignasi-barrera/
(audio recording for th
I can see in the output that some projects depend on:
[INFO] | +- net.schmizz:sshj:jar:0.1.1:compile
But jclouds 2.0 depends on version 0.12.0, which has a different groupId:
[INFO] | | +- com.hierynomus:sshj:jar:0.12.0:compile
Could you try excluding version 0.1.1, so there is just one in
Hi Rubén,
Can you share the output of running the "mvn dependency:tree" command
in your project? Let's first see if there are dependency conflicts.
I.
On 15 December 2016 at 10:04, Ruben Rubio Rey wrote:
> Hi,
>
> I am trying to migrate an application from 1.9.1 to 2.0.0
The Apache jclouds team is pleased to announce the release of jclouds 2.0.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.
gt; prepareStreamsAndStart(JUnitStarter.java:211)
> at com.intellij.rt.execution.junit.JUnitStarter.main(
> JUnitStarter.java:67)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessor
new BouncyCastleCryptoModule()))
>>> .buildApi(NeutronApi.class)
>>>
>>> and for example use it to create a firewall and add a rule like
>>>
>>> FWaaSApi fWaaSApi = neutronApi.getFWaaSApi(regionId).get();
>>> FirewallPolicy f
Hi Ken,
Not all providers have an API to effectively manage firewalls, but
most that do, implement the jclouds SecurityGroupExtension [1]. You
can get it by calling:
context.getComputeService().getSecurityGroupExtension();
That will return an optional that will be present if the extension is
Hi Dileep,
Mind opening an issue in our JIRA? That is the best way to keep track of
this.
I can't tell when the patch will be available, but the best way to make
sure it happens soon is contributing and opening a pull request :) If you
are up to do it, I will be happy to help and provide
k1-8-0-but-send-with-jdk1-7
> a possible OpenJDK bug.
>
> A quick dig into JClouds code seems to confirm that setHostnameVerifier() is
> used so this could be the case.
>
>
> Ignasi Barrera je 15. 09. 2016 ob 12:06 napisal:
>
>> Thanks for the feedback and all the details cen
not get activated.
>
> I digged more into Apache driver and the way SSLSocketFactory is used by
> JClouds is very similar to pre-patched Keycloak from that Jira issue
> (according to pull requests). Might be worth looking into.
>
> Best regards, cen
>
>
> Ignasi Barrera j
TH_tk1411104de43046aca9b371c27c3b1fad' -X PUT
> http://192.168.0.58:8080/v1/AUTH_admin/mycontainer
>
> //upload file
> swift -A http://192.168.0.58:8080/auth/v1.0/ -U admin:admin -K admin upload
> mycontainer some_file
>
> //get file
> curl -v -H 'X-Auth-Token: AUTH_tk1411104
Which version of jclouds are you using? Are you using Gson too in your
project? In that case, which version of Gson are you using?
On 14 September 2016 at 19:45, Alexandr Porunov
wrote:
> Hello,
>
> How to use jclouds with OpenStack Swift?
>
> Here is my code:
>
Hi Diego,
To unsubscribe please send an email to:
jclouds-user-unsubscr...@apache.org
I.
On Sep 14, 2016 11:02, "Diego Parrilla Santamaría" <
diego.parrilla.santama...@gmail.com> wrote:
> unsubscribe
>
Hi!
jclouds supports several HTTP drivers. By default it relies on the java
HttpUrlConection, but you can also configure it to use the Apache Http
client or OkHttp [1]. Using those drivers is as simple as adding the
corresponding Guice module when creating the context (have a look at the
OkHttp
Hi Richard,
Having a look at the DnsNameValidator, it looks like it is prepared to
be configurable [1]. The problem is that the
FormatSharedNamesAndAppendUniqueStringToThoseWhichRepeat class (the
one that uses the group prefix to generate names), instantiates it
directly with fixed values.
I'd
.:lib/*"
> ConsolesApiLiveTest.java
>
> user@user-Latitude-E6420:~/jclouds$ java -classpath ".:lib/*"
> ConsolesApiLiveTest
> Consoles extension not present in server
>
>
> From:"Ignasi Barrera"
This is because your OpenStack installation does not have the console
extension enabled.
* What OpenStack version are you using?
* Which is the output of the "nova service-list" command?
El 8 ago. 2016 5:05 p. m., escribió:
> Hi ,
>
> We are trying to test the console API of
This is probably because the IDE configuration is not passing the
test.openstack-nova.identity property to the JVM.
El 8 ago. 2016 5:21 p. m., escribió:
>
> Hi,
>
> While running the ConsolesApiLiveTest from the IDE we are getting the
> following error.
>
> [TestNG] Running:
>
Hi Ryan,
Apologies for the late reply.
Unfortunately there is no such helper. The current jclouds portable model
does not have those minimum requirements represented in the Image entity
(which would be a nice to have, btw) so there is no portable filter yet.
I.
El 7 jun. 2016 9:33 p. m., "Ryan
Hi Kai,
We indeed plan to add support for Keystone v3, but we have not
scheduled it for any release yet. This is something we'd pretty much
like to be added as soon as possible, but honestly there are other
tasks that are taking most of the committer force now. Having
contributors willing to step
It would also help if you could provide the complete stacktrace.
Thx!
On 2 June 2016 at 17:11, Pratheesh wrote:
> Hi Phillips,
>
> This error is not happening always, it appears intermittently and when the
> server restarts works perfectly. So I have to wait for
The fix in this pull request might be relevant:
https://github.com/jclouds/jclouds/pull/948
I plan to merge it later today so you should have a new SNAPSHOT to test
with shortly after that.
El 26/4/2016 7:21 p. m., "Kai Liu" escribió:
> Thanks, I am looking into the email
ency of jclouds-ssh is:
>
> org.jclouds.driver
> jclouds-sshj
> 1.6.0
>
>
> version 2.0.0-SNAPSHOT is not available. Or should I use another group or
> artifactId?
>
> Ignasi Barrera <n...@apache.org>于2016年3月22日周二 下午5:47写道:
>>
>> The issue is that it a
+- org.ow2.sat4j:org.ow2.sat4j.core:jar:2.3.5:compile
> [INFO]\- de.hhu.stups:prologlib:jar:2.4.40:compile
> [INFO] \- com.google.code.findbugs:jsr305:jar:1.3.9:compile
> [INFO]
>
> [INFO] BUILD SUCCES
It looks like you could have a mix of versions in your classpath.
Could you share the output of running the "mvn dependency:tree"
command in the root of *your* project?
I.
On 22 March 2016 at 09:25, 王逸群 wrote:
> Hi,
> I intend to use SshClient to execute some scripts.
"Give me all Ubuntu nodes"
> or "Give me all FreeBSD nodes" or "Give me all Windows nodes" etc. That
> is why I want to provide the group name by myself which is basically
> "MyProjectName"+amiId.
>
> On 21. 03. 2016 11:29, Ignasi Barrera wrote:
>
Regarding the group names thing, jclouds tries to infer the group name
from the security groups and key pairs [1]. When key pairs or security
groups are (indirectly) created as part of the "createNodesInGroup"
call, jclouds applies the naming convention taking into account the
group name. The code
Good to see that part is working!
FWIW, jclouds adds a prefix to some resources, for convenience. This can be
configured, though, by setting the
ComputeServiceProperties.RESOURCENAME_PREFIX property [1] when creating the
context. You can change the default "jclouds" value or set it to an empty
Regarding the group name in the nodes, could you share the code you
use to build the template, including the template options?
On 17 March 2016 at 01:52, Ignasi Barrera <n...@apache.org> wrote:
> Good to see that part is working!
>
> FWIW, jclouds adds a prefix to some resources,
Great to see it worked in the end! :)
On 10 March 2016 at 15:17, Mop Sophia <mopsop...@gmail.com> wrote:
> Nice ! It works fine !
>
> Thank you very much Ignasi ;)
>
> 2016-03-10 15:10 GMT+01:00 Ignasi Barrera <n...@apache.org>:
>>
>> OK, then tr
ternalIfNull does not inherit
> from EndpointToSupplierAdminURI...
>
> The method to(Class) in the type
> LinkedBindingBuilder is not applicable for the
> arguments (Class)
>
>
> 2016-03-10 10:23 GMT+01:00 Ignasi Barrera <n...@apache.org>:
>>
>> (Moving b
ts_links": [], "type": "ec2",
> "name": "nova_ec2"}, {"endpoints": [{"adminURL":
> "http://192.168.10.2:8004/v1/0acf5d5461eb42beb3dc5fca655b3974;, "region":
> "RegionOne", "internalURL":
Hi Ionel,
The current OAuth API in jclouds just supports the Bearer Token and
the JWT authentication flows. Having a look at how OAuth works in
hubiC, it seems that you won't be able to use the current API to
connect to it.
In order to be able to authenticate, the regular Authorization Code
flow
se JClouds get the adminUrl of keystone to make
> the request
>
> Regards,
>
> Stéphane
>
>
>
> 2016-03-09 13:32 GMT+01:00 Ignasi Barrera <n...@apache.org>:
>
>> Don't configure the proxy in the client supplier. Just configure it
>> the &quo
.modules(modules)
> .overrides(overrides)
> .buildApi(KeystoneApi.class);
>
>
> Any idea of my mistake ?
>
> Regards,
>
> Stéphane
>
>
> 2016-03-05 1:28 GMT+01:00 Ignasi Barrera <n...@apache.org>:
>>
&g
Hi!
Andrew's link will provide you the context you need.
I don't know if there is a proper way of configuring this using the
default HTTP driver, but here is a specific example using the OkHttp
one:
First you will need to create an OkHttpClientSupplier that creates the
http client with the
Hi Kenny,
Currently there is no support for Cerberus and, honestly, there are still
no plans to add it. You're the first one asking for that API, so could you
tell us what is your use case?
I.
El 11/2/2016 9:37 a. m., "Kenny Aondona" escribió:
>
> Hi,
>
> Does jclouds
nes are executed you can proceed executing commands with
> init script and sudo as normal.
>
> Hopefully this helps someone in the future as crazy as I who wants to
> run FreeBSD. :)
>
> Best regards, Klemen
>
>
> On 29. 01. 2016 14:55, Ignasi Barrera wrote:
> >
and, the proper way is
> su - root -c "commands && here". su root seems to break the flow.
>
>
> Ignasi Barrera je 28. 01. 2016 ob 11:12 napisal:
>>
>> I have no experience with BSD instances, but could it be a PATH issue?
>>
>> Can you try setting the P
. It's clear to me that this is not the same
> environment as the one
> when I manually ssh into the machine so what is the difference?
>
>
> Best regards, Klemen
>
> On 27. 01. 2016 11:06, Ignasi Barrera wrote:
>> No. You can use the one in the template builder to run t
1 - 100 of 216 matches
Mail list logo