As there is not enough request I cancel this proposal.
Christian
Am Mi., 15. Apr. 2020 um 07:15 Uhr schrieb Christian Schneider <
ch...@die-schneider.net>:
> (I first proposed this in felix. Some people hinted that Aries might be a
> better fit. So I am also starting this discussion here)
>
>
I meant interest of course :-)
Am Fr., 17. Apr. 2020 um 09:19 Uhr schrieb Christian Schneider <
ch...@die-schneider.net>:
> As there is not enough request I cancel this proposal.
>
> Christian
>
> Am Mi., 15. Apr. 2020 um 07:15 Uhr schrieb Christian Schneider <
> ch...@die-schneider.net>:
>
>>
IMHO, Winegrower/Karaf is a good place and already almost covered (again DevX
and the Karaf ecosystem).
I agree with Romain.
Regards
JB
> Le 15 avr. 2020 à 20:39, Romain Manni-Bucau a écrit :
>
> There is already one without OSGi (utilda:
> https://geronimo.apache.org/microprofile/), guess
There is already one without OSGi (utilda:
https://geronimo.apache.org/microprofile/), guess it is just a matter of
finishing the OSGi meta for all the desired spec (guess health has not yet
the right OSGi-CDI registration for ex).
That said it already runs with winegrower having OSGi and CDI side
It sounds very good. Are you planning to provide a similar complete example
using the building blocks you mentioned?
Christian
Am Mi., 15. Apr. 2020 um 13:33 Uhr schrieb Romain Manni-Bucau <
rmannibu...@gmail.com>:
> Hi Christian, the openX i mentionned are the standards done at CNF so
>
Hi Christian, the openX i mentionned are the standards done at CNF so
standard for metrics is openmetrics, for tracing opentracing etc.
On my side I use Microprofile metrics and export it to prometheus with the
spec exporter but I know some java guys use jmx exporter so guess the best
we can do is
What do you mean by a runtime? For me the runtime is a suitable set of
bundles that provide what the application needs. What would be a more
concrete runtime?
My approach here is to go with standards as far as possible. Ideally also
rely on Apache bundle impls so we have some leverage if
For me cloud native means to fit as well as possible into a typical cloud.
Luckily this currently means k8s as there is not much competition. On top
of course we need the relevant surrounding services like you described.
For metrics the current state of the art seems to be prometheus. A standard
Bascially, ongoing Karaf DevX effort is the result of the discussions I have
weekly with Netflix.
Regards
JB
> Le 15 avr. 2020 à 08:24, Grzegorz Grzybek a écrit :
>
> +? from me as well.
>
> I've sent my answer to felix-dev ML about this.
>
> BTW JBO - do you have some
+? from me as well.
I've sent my answer to felix-dev ML about this.
BTW JBO - do you have some report/minutes/comments after you talked with
Netflix? It'd be super interesting to hear about their decisions related to
OSGi!
regards
Grzegorz Grzybek
śr., 15 kwi 2020 o 07:23 Jean-Baptiste Onofre
Hmm, here are a few thoughts:
1. What is "cloud native"? Nothing right? ;). More seriously I guess you
speak of k8s microservices. If so, pillars are metrics (openmetric),
tracing (opentracing), config (env, and secret/maps), security (jwt?),
logging compatible with a docker driver, api exposure
Forgot the link.
The current state can be viewed in
https://github.com/cschneider/osgi-best-practices
It already implements most of the aspects above but still got some rough
edges. The example also contains some bundles like the
swagger and halbrowser repackagings that should rather be
12 matches
Mail list logo
