ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.W. Janssen (JIRA)" <>
Subject [jira] [Commented] (ACE-414) Check for new/already downloaded and completed DPs on startup
Date Fri, 08 Nov 2013 12:01:21 GMT


J.W. Janssen commented on ACE-414:

The agent current doesn't keep track (in a persistent way) whether a DP is completely downloaded
or not. And due to ACE-413, it simply restarted the download of a DP when the agent was restarted.
With ACE-413 now fixed, it no longer does this, and simply will install the DP *once it has
verified with the server that it indeed has the complete DP downloaded*.

I'm a little hesitant to built in all kinds of completion checks to reduce the number of HTTP
calls upon startup. I do see a functional requirement to allow offline DPs to be installed
as a kind of bootstrapping mechanism for new agents, but this is also what ACE-162 is about
(albeit described in a more cryptic way). IMO, implementing that issue solves this problem
as well. [~wilsib], do you agree?

> Check for new/already downloaded and completed DPs on startup
> -------------------------------------------------------------
>                 Key: ACE-414
>                 URL:
>             Project: ACE
>          Issue Type: Improvement
>          Components: Deployment
>    Affects Versions: 1.0.0
>            Reporter: Wilfried Sibla
>            Assignee: J.W. Janssen
> if the new agent couldn't install a completely downloaded DP (e.g. caused by a JVM crash/OSGi
container restart), the DP isn't installed after restart.
> The DP is downloadad again.
> This is not a good solution in embedded scenarios.
> A complete DP should/could be installed without any online checks. If there already is
a new DP version on server side, it could be updated.

This message was sent by Atlassian JIRA

View raw message