Am 19.06.15 um 17:06 schrieb Bertrand Delacretaz: >> 3. Repository support: file url, http url, s3 url... > > Do s3 URLs need special handling or are they just HTTP? > > I suppose some of those might need authentication as well? > This needs special handling due to authentication :) The easiest way is to include the aws libs and use their api to access s3. Doing the http calls by hand is not really doable.
>> ...9. Provide a way to just download all referenced artifacts and putting >> them in a maven repo like file structure... > > As a way to produce an offline system, is that the use case? > That's not implemented at this point but I like the idea. Yes, offline is one use case, but mirroring this to another repository is the other. So you have all artifacts in a mvn repo and want to upload/sync them with s3. > >> ...10. Support of the launchpad api startup mode (install, update, >> restart)... > > We might need to refactor some code out of the launchpad to reuse it > but that sounds useful. I would add an option to fail in all modes > except INSTALL if one wants to enforce immutable Sling instances. > Ok > A few more comments: > > Do you think we still need the launchpad's "incremental startup" that > raises start levels sequentially with a pause between each? Or was > that a workaround for some bugs that are gone today? I think we still need them - otherwise you end up at the final start level but content packages are not installed. With pure Sling and no content packages I guess the incremental startup is not needed. I once started to move this stuff into a separate module but failed to implement some detail; in retrospect I think I did a mistake while implementing it. So it should be possible to move this to a bundle. But maybe with crankstart we can do this more intelligent as I assume crankstart is in full control of the startup/installation? > > One thing that we also discussed before but never implemented in > Crankstart is validating artifacts based on digests specified in the > provisioning model - I think the model already supports specifying > such digests? Yes, the model supports attributes (though I never used/tested them). You can specify them with [sha=something] directly after the coordinates. Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
