jclouds-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Custine <chris.cust...@gmail.com>
Subject Re: [jira] [Commented] (JCLOUDS-613) Implement the DigitalOcean v2 API
Date Fri, 26 Jun 2015 08:45:31 GMT
I'm going to try these out in a few hours after some sleep. Either way I'll
try to get this pr created tomorrow.

--
Sent from my Android phone
On Jun 26, 2015 2:39 AM, "Ignasi Barrera (JIRA)" <jira@apache.org> wrote:

>
>     [
> https://issues.apache.org/jira/browse/JCLOUDS-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602569#comment-14602569
> ]
>
> Ignasi Barrera commented on JCLOUDS-613:
> ----------------------------------------
>
> I found the same issue and it is definitely a random timeout issue. It
> seems that when you are deploying several nodes, at some point, they start
> to boot slower than expected and take their time to boot. I was able to run
> the live tests successfully in a consistent way using the following
> parameters:
>
> {code}
> mvn clean integration-test -Plive \
>   -Dtest.digitalocean2.identity=unused \
>   -Dtest.digitalocean2.credential=<token> \
>   -Djclouds.compute.timeout.node-terminated=600000 \
>   -Djclouds.compute.timeout.node-running=600000 \
>   -Djclouds.compute.timeout.script-complete=1200000 \
>   -Djclouds.compute.timeout.port-open=600000 \
>   -Djclouds.connection-timeout=600000 \
>   -Djclouds.ssh.retry-auth=true
> {code}
>
> The point is that the tests that fail are not always the same ones, so the
> time it takes a not to boot is not predictable. [~ccustine] can you confirm
> that these values work for you? If they work we should add them to the
> provider metadata to configure them as defaults.
>
> Let's try to get the PR open soon, as we really want to have a v2
> implementation for 1.9.1. Thanks for your feedback!
>
> > Implement the DigitalOcean v2 API
> > ---------------------------------
> >
> >                 Key: JCLOUDS-613
> >                 URL: https://issues.apache.org/jira/browse/JCLOUDS-613
> >             Project: jclouds
> >          Issue Type: New Feature
> >          Components: jclouds-compute
> >    Affects Versions: 1.7.3
> >            Reporter: Ignasi Barrera
> >            Assignee: Ignasi Barrera
> >              Labels: digitalocean
> >             Fix For: 2.0.0
> >
> >
> > DigitalOcean has just released the version 2 of their API. It introduces
> some major changes as long as many improvements and features that make the
> API more easy to consume.
> > Version 2 is now a more RESTful API, has a better error population (and
> hope this will help us get rid of the [custom HTTP response parsing code|
> https://github.com/jclouds/jclouds-labs/blob/master/digitalocean/src/main/java/org/jclouds/digitalocean/http/ResponseStatusFromPayloadHttpCommandExecutorService.java#L89-L128]),
> and and a more complete domain model.
> > https://www.digitalocean.com/company/blog/api-v2-enters-public-beta/
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message