Re: [hawkbit-dev] How to add a software artifact to an existing distribu

[Silvano Cirujano Cuesta <silvano.cirujano-cuesta@xxxxxxxxxxx>]

Hi Kai,

I don't see the implementation as an issue, but as a feature :-) I just
wanted to confirm it.

As you said, this way you know the whole set of managed software
artifacts that you should have on the device. What you can't easily see
with the UI is the changeset between distribution versions. Getting it
programmatically doing a diff of REST-API request results isn't a big issue.

Automatic generation of a DS when a software module is added to a device
would be cool. But I don't think it's a key feature, since many of
HawkBit deployments will be using the REST-API instead of the UI and
from those using the UI, not so many will be adding and removing
artifacts from the targets that frequently.

Regards,
  Silvano

On 03/02/2016 08:38 AM, Zimmermann Kai (INST/ECS3) wrote:
> Hi,
> 
> yes, your assumption is correct. hawkBit defines with a DS always the complete baseline. As a result in some scenarios (very "app heavy") you have to define a unique DS for every target for every change.
> 
> As a result you have a complete software installation history for the target including addition and removal of individual apps, i.e. your are not only seeing what the addition or removal was but the resulting baseline, too.
> 
> However, especially in the UI this can get quite costly to do (i.e. creating a DS for every change). Something like updating/adding/removing a single Software Module to/from a target and hawkBit automatically generates a new DS in the background is currently missing. You could do this through API with your own application of course.
> 
> Kai
> 
> Bosch Software Innovations GmbH
> INST/ECS3 - Engineering Cloud Services - IoT Software Provisioning
> 
> Stuttgarter Str. 130
> 71332 Waiblingen
> GERMANY
> www.bosch-si.de
> www.blog.bosch-si.com 
> 
> Tel. +49 711 811 58115
> Mobile: +49 174 2126424
> kai.zimmermann@xxxxxxxxxxxx
> 
> Registered office: Berlin, Register court: Amtsgericht Charlottenburg, HRB 148411 B
> Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn
> 
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: hawkbit-dev-bounces@xxxxxxxxxxx [mailto:hawkbit-dev-bounces@xxxxxxxxxxx] Im Auftrag von Silvano Cirujano Cuesta
> Gesendet: Dienstag, 1. März 2016 08:38
> An: hawkbit-dev@xxxxxxxxxxx
> Betreff: [hawkbit-dev] How to add a software artifact to an existing distribution
> 
> Hi,
> 
> I'd like to get a confirmation to what I understood up-to-now regarding distributions.
> 
> HawkBit expects to to get with each distribution for a device the full set of software artifacts being managed, right? It is up to the device to decide if the artifacts have to be upgraded or not.
> 
> Or let me formulate it differently:
> 1. Distribution Dist_A has some firmware Frmw_v1.0.
> 2. To provision an application App_v1.0 on top of Frmw_v1.0, a 2nd version of the distribution Dist_B containing Frmw_v.10 and App_v1.0 has to be created and offered to the device.
> 3. The HawkBit client on the device should know that it has already Frmw_v1.0 and it only needs App_v1.0 on top of it.
> 
> Did I get it right?
> 
> --
> Best regards,
> Silvano Cirujano Cuesta
> _______________________________________________
> hawkbit-dev mailing list
> hawkbit-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/hawkbit-dev
> _______________________________________________
> hawkbit-dev mailing list
> hawkbit-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/hawkbit-dev
>