Hi Peter,
I also thought a bit about how to possibly make the deployments smaller.
I see three possible solutions:
1. Put the main version of a system in a docker layer and upgrades in a
layer on top.
An example where this might make sense is Adobe Experience Manager. You put
the bundles of AEM
The basic idea of docker as well as k8s are immutable images.
The advantage of these is that you can give them a version and this way
uniquely identify what is running in the cloud at any time.
The upgrade process in k8s typically is that a new pod is installed with
the new docker image. As soon
Christian,
Yes, for JPM, which feels very long ago, I had a base image and then added only
an executable JAR as a new layer.
However, since I've seen the stats for porn sites on the Internet the size of
images got me a lot less worried :-) I've spent a lot of my working life trying
to make
Hi,
trying to create DS instances from ConfigAdmin Configurations, I came
across this posting
https://mail.osgi.org/pipermail/osgi-dev/2010-March/002398.html. As the
posting is from 2010, I'd just like to make sure: can somebody please
confirm that this is still true for the current version of
Factory configurations (in ConfigAdmin) and ComponentFactory (in DS) do not work together. They are mutually exclusive There can be only one thing in charge of making multiple instances of a component.
It can be either factory configurations (in ConfigAdmin), in which case a component instance
Okay, thanks for the confirmation.
- Michael
Am 07.08.19 um 20:31 schrieb BJ Hargrave:
> Factory configurations (in ConfigAdmin) and ComponentFactory (in DS)
> do not work together. They are mutually exclusive There can be only
> one thing in charge of making multiple instances of a component.
