Re: Thinking about Karaf 5 modulith runtime

[Grzegorz Grzybek]

śr., 4 lis 2020 o 08:35 Jean-Baptiste Onofre  napisał(a):

> That’s a great feedback !
>
> Today, we are "challenged" by other approach. I still believe that we have
> a great asset in the runtime ecosystem.
>
> My thinking now is more to still use OSGi internally (and let people do
> OSGi on Karaf if they want) but open the scope to other framework/approach
> (spring boot, micro profile, etc). We would embrace a wider community and
> expend our use cases.
> With François, I think we already identified some improvements patch
> (lighter/immutable runtime, tooling, …), but I would love to have feedback
> from the community to drive the roadmap.
>
> Thanks Greg ! You made my day ;)
>

:)
I'll definitely think outside of OSGi box after I finish my current
assignment (work).

regards
Grzegorz


> Regards
> JB
>
> > Le 4 nov. 2020 à 07:43, Grzegorz Grzybek  a écrit
> :
> >
> > śr., 4 lis 2020 o 07:41 Jean-Baptiste Onofre 
> napisał(a):
> >
> >> What do you mean by "impossible" ? Removing OSGi from the picture, or
> >> thinking about Karaf future ? ;)
> >>
> >
> > I meant I see OSGi everywhere and that's all I do for last 6+ years, so
> > it's hard for me to NOT think about OSGi ;)
> > If I was asked to help shaping Karaf 5, I'd still think OSGi-first...
> >
> > regards
> > Grzegorz Grzybek
> >
> >
> >>
> >> Regards
> >> JB
> >>
> >>> Le 4 nov. 2020 à 06:27, Grzegorz Grzybek  a
> écrit
> >> :
> >>>
> 
>  don’t think OSGi focus
> 
> >>>
> >>> For now it's impossible for me ;) Looks like I need some OSGi-REST...
> ;)
> >>>
> >>> regards
> >>> Grzegorz
> >>>
> >>> śr., 4 lis 2020 o 06:16 Jean-Baptiste Onofre 
> >> napisał(a):
> >>>
>  Hi
> 
>  Not yet, I’m working locally on changing the structure.
> 
>  And I don’t want to be influenced or influence for now ;)
> 
>  So, I would love your overall thinking in term of approach, features,
>  vision, and again generally speaking (don’t think OSGi focus, or one
>  particular use case, more global).
> 
>  Regards
>  JB
> 
> > Le 4 nov. 2020 à 06:09, Grzegorz Grzybek  a
> >> écrit
>  :
> >
> > Hello
> >
> > Great news! Is this branch already available in Karaf's git repo?
> >
> > regards and stay safe!
> > Grzegorz Grzybek
> >
> > śr., 4 lis 2020 o 05:59 Jean-Baptiste Onofre 
>  napisał(a):
> >
> >> Hi guys,
> >>
> >> François and I started to think about Karaf 5 and give an even
> modern
> >> flavor to Karaf, including potentially lot of refactoring and
> changes.
>  We
> >> think it’s a must have in our patch to the "main modulith runtime".
> >>
> >> Before sharing all details (some have been shared during my talk at
> >> ApacheCon), we want to move forward on a PoC branch.
> >>
> >> However, we would love to have your inputs and thoughts (think wide
> >> ;)).
> >>
> >> So, please, if you have ideas, comments, criticism ;), send me an
> >> email
> >> and I will reply and eventually include your points in the PoC.
> >>
> >> Thanks !
> >> Regards
> >> JB
> 
> 
> >>
> >>
>
>

Re: Thinking about Karaf 5 modulith runtime

[Jean-Baptiste Onofre]

That’s a great feedback !

Today, we are "challenged" by other approach. I still believe that we have a 
great asset in the runtime ecosystem.

My thinking now is more to still use OSGi internally (and let people do OSGi on 
Karaf if they want) but open the scope to other framework/approach (spring 
boot, micro profile, etc). We would embrace a wider community and expend our 
use cases.
With François, I think we already identified some improvements patch 
(lighter/immutable runtime, tooling, …), but I would love to have feedback from 
the community to drive the roadmap.

Thanks Greg ! You made my day ;)
Regards
JB

> Le 4 nov. 2020 à 07:43, Grzegorz Grzybek  a écrit :
> 
> śr., 4 lis 2020 o 07:41 Jean-Baptiste Onofre  napisał(a):
> 
>> What do you mean by "impossible" ? Removing OSGi from the picture, or
>> thinking about Karaf future ? ;)
>> 
> 
> I meant I see OSGi everywhere and that's all I do for last 6+ years, so
> it's hard for me to NOT think about OSGi ;)
> If I was asked to help shaping Karaf 5, I'd still think OSGi-first...
> 
> regards
> Grzegorz Grzybek
> 
> 
>> 
>> Regards
>> JB
>> 
>>> Le 4 nov. 2020 à 06:27, Grzegorz Grzybek  a écrit
>> :
>>> 
 
 don’t think OSGi focus
 
>>> 
>>> For now it's impossible for me ;) Looks like I need some OSGi-REST... ;)
>>> 
>>> regards
>>> Grzegorz
>>> 
>>> śr., 4 lis 2020 o 06:16 Jean-Baptiste Onofre 
>> napisał(a):
>>> 
 Hi
 
 Not yet, I’m working locally on changing the structure.
 
 And I don’t want to be influenced or influence for now ;)
 
 So, I would love your overall thinking in term of approach, features,
 vision, and again generally speaking (don’t think OSGi focus, or one
 particular use case, more global).
 
 Regards
 JB
 
> Le 4 nov. 2020 à 06:09, Grzegorz Grzybek  a
>> écrit
 :
> 
> Hello
> 
> Great news! Is this branch already available in Karaf's git repo?
> 
> regards and stay safe!
> Grzegorz Grzybek
> 
> śr., 4 lis 2020 o 05:59 Jean-Baptiste Onofre 
 napisał(a):
> 
>> Hi guys,
>> 
>> François and I started to think about Karaf 5 and give an even modern
>> flavor to Karaf, including potentially lot of refactoring and changes.
 We
>> think it’s a must have in our patch to the "main modulith runtime".
>> 
>> Before sharing all details (some have been shared during my talk at
>> ApacheCon), we want to move forward on a PoC branch.
>> 
>> However, we would love to have your inputs and thoughts (think wide
>> ;)).
>> 
>> So, please, if you have ideas, comments, criticism ;), send me an
>> email
>> and I will reply and eventually include your points in the PoC.
>> 
>> Thanks !
>> Regards
>> JB
 
 
>> 
>> 

Re: Thinking about Karaf 5 modulith runtime

[Grzegorz Grzybek]

>
> don’t think OSGi focus
>

For now it's impossible for me ;) Looks like I need some OSGi-REST... ;)

regards
Grzegorz

śr., 4 lis 2020 o 06:16 Jean-Baptiste Onofre  napisał(a):

> Hi
>
> Not yet, I’m working locally on changing the structure.
>
> And I don’t want to be influenced or influence for now ;)
>
> So, I would love your overall thinking in term of approach, features,
> vision, and again generally speaking (don’t think OSGi focus, or one
> particular use case, more global).
>
> Regards
> JB
>
> > Le 4 nov. 2020 à 06:09, Grzegorz Grzybek  a écrit
> :
> >
> > Hello
> >
> > Great news! Is this branch already available in Karaf's git repo?
> >
> > regards and stay safe!
> > Grzegorz Grzybek
> >
> > śr., 4 lis 2020 o 05:59 Jean-Baptiste Onofre 
> napisał(a):
> >
> >> Hi guys,
> >>
> >> François and I started to think about Karaf 5 and give an even modern
> >> flavor to Karaf, including potentially lot of refactoring and changes.
> We
> >> think it’s a must have in our patch to the "main modulith runtime".
> >>
> >> Before sharing all details (some have been shared during my talk at
> >> ApacheCon), we want to move forward on a PoC branch.
> >>
> >> However, we would love to have your inputs and thoughts (think wide ;)).
> >>
> >> So, please, if you have ideas, comments, criticism ;), send me an email
> >> and I will reply and eventually include your points in the PoC.
> >>
> >> Thanks !
> >> Regards
> >> JB
>
>

Re: Thinking about Karaf 5 modulith runtime

[Jean-Baptiste Onofre]

Hi

Not yet, I’m working locally on changing the structure.

And I don’t want to be influenced or influence for now ;)

So, I would love your overall thinking in term of approach, features, vision, 
and again generally speaking (don’t think OSGi focus, or one particular use 
case, more global).

Regards
JB

> Le 4 nov. 2020 à 06:09, Grzegorz Grzybek  a écrit :
> 
> Hello
> 
> Great news! Is this branch already available in Karaf's git repo?
> 
> regards and stay safe!
> Grzegorz Grzybek
> 
> śr., 4 lis 2020 o 05:59 Jean-Baptiste Onofre  napisał(a):
> 
>> Hi guys,
>> 
>> François and I started to think about Karaf 5 and give an even modern
>> flavor to Karaf, including potentially lot of refactoring and changes. We
>> think it’s a must have in our patch to the "main modulith runtime".
>> 
>> Before sharing all details (some have been shared during my talk at
>> ApacheCon), we want to move forward on a PoC branch.
>> 
>> However, we would love to have your inputs and thoughts (think wide ;)).
>> 
>> So, please, if you have ideas, comments, criticism ;), send me an email
>> and I will reply and eventually include your points in the PoC.
>> 
>> Thanks !
>> Regards
>> JB

Re: [VOTE] Apache Winegrower 1.0.0 release

[Jean-Baptiste Onofre]

Gently reminder: we would need an additional binding vote here.

Thanks !
Regards
JB

> Le 30 oct. 2020 à 08:00, Jean-Baptiste Onofre  a écrit :
> 
> Hi everyone,
> 
> I submit Winegrower 1.0.0 to your vote. This is the first Winegrower release, 
> bootstrapping the project.
> 
> We know that some works have to be done on the documentation and example 
> fronts, but this release is fully usable and provide a concrete alternative 
> to existing framework.
> As for Karaf 4.3.0, I’m preparing a blog post about Winegrower.
> 
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1150/ 
> 
> 
> Staging Dist:
> https://dist.apache.org/repos/dist/dev/karaf/winegrower/1.0.0/ 
> 
> 
> Please vote to approve this release:
> 
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
> 
> This vote will be open for at least 72 hours.
> 
> Regards
> JB
> 

Thinking about Karaf 5 modulith runtime

[Jean-Baptiste Onofre]

Hi guys,

François and I started to think about Karaf 5 and give an even modern flavor to 
Karaf, including potentially lot of refactoring and changes. We think it’s a 
must have in our patch to the "main modulith runtime".

Before sharing all details (some have been shared during my talk at ApacheCon), 
we want to move forward on a PoC branch.

However, we would love to have your inputs and thoughts (think wide ;)).

So, please, if you have ideas, comments, criticism ;), send me an email and I 
will reply and eventually include your points in the PoC.

Thanks !
Regards
JB

Re: Kibana (2.5.0) -- ElasticSearch Appender config error

[Jean-Baptiste Onofre]

Hi,

Decanter Prometheus exposes the Prometheus servlet. So, it’s not pushing, it’s 
polling: prometheus polls data from the prometheus servlet exposed by decanter.
If you want pushing, you can directly push to prometheus backend (but it’s not 
the prometheus appender).

Regards
JB

> Le 3 nov. 2020 à 23:53, Mark Bordelon  a écrit :
> 
> Hi JB.
> Got things to work by just setting the prefix and making sure everything was 
> lowercase! 
> Next problem is getting the data from the karaf endpoint 
> (decanter/prometheus) to a prometheus server (promeefee:9090/graph)
> I see nothing in the decanter documentation on prometheus appender for 
> pushing data to a url. 
> Is it assumed that a prometheus server must always pull from the 
> decanter/prometheus endpoint?
> 
>> On Nov 3, 2020, at 12:51, Jean-Baptiste Onofre  wrote:
>> 
>> Hi Mark
>> 
>> 6.8, ok, the tests are using newer version.
>> 
>> But it should work anyway. I will test it tomorrow.
>> 
>> Regards
>> JB
>> 
>>> Le 3 nov. 2020 à 21:44, Mark Bordelon  a écrit :
>>> 
>>> Hi JB,
>>> 
>>> This is the version of the Elastic Search I wish to push to:
>>> 
>>> {
>>> "name" : "sitesc104w224m7",
>>> "cluster_name" : "vela",
>>> "cluster_uuid" : "fNKKGBcoTJmh42LDDxDkow",
>>> "version" : {
>>>  "number" : "6.8.12",
>>>  "build_flavor" : "default",
>>>  "build_type" : "tar",
>>>  "build_hash" : "7a15d2a",
>>>  "build_date" : "2020-08-12T07:27:20.804867Z",
>>>  "build_snapshot" : false,
>>>  "lucene_version" : "7.7.3",
>>>  "minimum_wire_compatibility_version" : "5.6.0",
>>>  "minimum_index_compatibility_version" : "5.0.0"
>>> },
>>> "tagline" : "You Know, for Search"
>>> }
>>> 
 On Nov 2, 2020, at 21:17, Jean-Baptiste Onofre  wrote:
 
 Hi Mark,
 
 What elasticsearch version are you using ?
 
 Regards
 JB
 
> Le 2 nov. 2020 à 22:11, Mark Bordelon  a écrit :
> 
> With the following minimal configuration, (just setting the address, 
> authentication, and index prefix) …
> 
> 
> # Decanter Elasticsearch Appender Configuration
> 
> 
> # HTTP address of the elasticsearch nodes (separated with comma)
> addresses=http://elasticsearch-vela-1.sit.etrade.com:9200 
> 
> 
> # Basic username and password authentication
> username=batchoi
> password=batchoipwd
> 
> # The index name.
> # The index prefix is a static string used to construct the index
> index.prefix=karafCamelCWS
> # If true, it creates an index per Decanter event day
> #index.event.timestamped=true
> # For Elasticsearch < 7.5, index type is mandatory (not defined by 
> default)
> index.type=
> 
> # Marshaller to use (json is heavily recommended)
> marshaller.target=(dataFormat=json)
> 
> 
> I get this 405 error when i install the elasticsearch appender feature.
> 
> 2020-11-02T15:32:15,870 | WARN  | EventAdminAsyncThread #23 | 
> ElasticsearchAppender| 188 - 
> org.apache.karaf.decanter.appender.elasticsearch - 2.5.0 | Can't append 
> into Elasticsearch
> org.elasticsearch.client.ResponseException: method [POST], host 
> [http://elasticsearch-vela-1.sit.etrade.com:9200], URI 
> [/karafCamelCWS-2020.11.02/], status line [HTTP/1.1 405 Method Not 
> Allowed  [/karafCamelCWS-2020.11.02/], status line [HTTP/1.1 405 Method Not 
> Allowed>]
> {"error":"Incorrect HTTP method for uri [/karafCamelCWS-2020.11.02/] and 
> method [POST], allowed: [HEAD, GET, PUT, DELETE]","status":405}
>at 
> org.elasticsearch.client.RestClient.convertResponse(RestClient.java:283) 
> ~[!/:?]
>at 
> org.elasticsearch.client.RestClient.performRequest(RestClient.java:261) 
> ~[!/:?]
>at 
> org.elasticsearch.client.RestClient.performRequest(RestClient.java:235) 
> ~[!/:?]
>at 
> org.apache.karaf.decanter.appender.elasticsearch.ElasticsearchAppender.send(ElasticsearchAppender.java:172)
>  ~[!/:?]
>at 
> org.apache.karaf.decanter.appender.elasticsearch.ElasticsearchAppender.handleEvent(ElasticsearchAppender.java:152)
>  [!/:?]
>at 
> org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)
>  [!/:?]
>at 
> org.apache.felix.eventadmin.impl.tasks.HandlerTask.runWithoutBlacklistTiming(HandlerTask.java:82)
>  [!/:?]
>at 
> org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:104)
>  [!/:?]
>at 
> org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks$TaskExecuter.run(AsyncDeliverTasks.java:166)
>  [!/:?]
>at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [?:1.8.0_51]

Re: Kibana (2.5.0) -- ElasticSearch Appender config error

[Mark Bordelon]

Hi JB.
Got things to work by just setting the prefix and making sure everything was 
lowercase! 
Next problem is getting the data from the karaf endpoint (decanter/prometheus) 
to a prometheus server (promeefee:9090/graph)
I see nothing in the decanter documentation on prometheus appender for pushing 
data to a url. 
Is it assumed that a prometheus server must always pull from the 
decanter/prometheus endpoint?

> On Nov 3, 2020, at 12:51, Jean-Baptiste Onofre  wrote:
> 
> Hi Mark
> 
> 6.8, ok, the tests are using newer version.
> 
> But it should work anyway. I will test it tomorrow.
> 
> Regards
> JB
> 
>> Le 3 nov. 2020 à 21:44, Mark Bordelon  a écrit :
>> 
>> Hi JB,
>> 
>> This is the version of the Elastic Search I wish to push to:
>> 
>> {
>> "name" : "sitesc104w224m7",
>> "cluster_name" : "vela",
>> "cluster_uuid" : "fNKKGBcoTJmh42LDDxDkow",
>> "version" : {
>>   "number" : "6.8.12",
>>   "build_flavor" : "default",
>>   "build_type" : "tar",
>>   "build_hash" : "7a15d2a",
>>   "build_date" : "2020-08-12T07:27:20.804867Z",
>>   "build_snapshot" : false,
>>   "lucene_version" : "7.7.3",
>>   "minimum_wire_compatibility_version" : "5.6.0",
>>   "minimum_index_compatibility_version" : "5.0.0"
>> },
>> "tagline" : "You Know, for Search"
>> }
>> 
>>> On Nov 2, 2020, at 21:17, Jean-Baptiste Onofre  wrote:
>>> 
>>> Hi Mark,
>>> 
>>> What elasticsearch version are you using ?
>>> 
>>> Regards
>>> JB
>>> 
 Le 2 nov. 2020 à 22:11, Mark Bordelon  a écrit :
 
 With the following minimal configuration, (just setting the address, 
 authentication, and index prefix) …
 
 
 # Decanter Elasticsearch Appender Configuration
 
 
 # HTTP address of the elasticsearch nodes (separated with comma)
 addresses=http://elasticsearch-vela-1.sit.etrade.com:9200 
 
 
 # Basic username and password authentication
 username=batchoi
 password=batchoipwd
 
 # The index name.
 # The index prefix is a static string used to construct the index
 index.prefix=karafCamelCWS
 # If true, it creates an index per Decanter event day
 #index.event.timestamped=true
 # For Elasticsearch < 7.5, index type is mandatory (not defined by default)
 index.type=
 
 # Marshaller to use (json is heavily recommended)
 marshaller.target=(dataFormat=json)
 
 
 I get this 405 error when i install the elasticsearch appender feature.
 
 2020-11-02T15:32:15,870 | WARN  | EventAdminAsyncThread #23 | 
 ElasticsearchAppender| 188 - 
 org.apache.karaf.decanter.appender.elasticsearch - 2.5.0 | Can't append 
 into Elasticsearch
 org.elasticsearch.client.ResponseException: method [POST], host 
 [http://elasticsearch-vela-1.sit.etrade.com:9200], URI 
 [/karafCamelCWS-2020.11.02/], status line [HTTP/1.1 405 Method Not Allowed 
 ]
 {"error":"Incorrect HTTP method for uri [/karafCamelCWS-2020.11.02/] and 
 method [POST], allowed: [HEAD, GET, PUT, DELETE]","status":405}
 at 
 org.elasticsearch.client.RestClient.convertResponse(RestClient.java:283) 
 ~[!/:?]
 at 
 org.elasticsearch.client.RestClient.performRequest(RestClient.java:261) 
 ~[!/:?]
 at 
 org.elasticsearch.client.RestClient.performRequest(RestClient.java:235) 
 ~[!/:?]
 at 
 org.apache.karaf.decanter.appender.elasticsearch.ElasticsearchAppender.send(ElasticsearchAppender.java:172)
  ~[!/:?]
 at 
 org.apache.karaf.decanter.appender.elasticsearch.ElasticsearchAppender.handleEvent(ElasticsearchAppender.java:152)
  [!/:?]
 at 
 org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)
  [!/:?]
 at 
 org.apache.felix.eventadmin.impl.tasks.HandlerTask.runWithoutBlacklistTiming(HandlerTask.java:82)
  [!/:?]
 at 
 org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:104)
  [!/:?]
 at 
 org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks$TaskExecuter.run(AsyncDeliverTasks.java:166)
  [!/:?]
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
 [?:1.8.0_51]
 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
 [?:1.8.0_51]
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  [?:1.8.0_51]
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  [?:1.8.0_51]
 at java.lang.Thread.run(Thread.java:745) [?:1.8.0_51]
 
 
 If the HTTP verb could be set to PUT, seems like it might 

Re: Kibana (2.5.0) -- ElasticSearch Appender config error

[Jean-Baptiste Onofre]

Hi Mark

6.8, ok, the tests are using newer version.

But it should work anyway. I will test it tomorrow.

Regards
JB

> Le 3 nov. 2020 à 21:44, Mark Bordelon  a écrit :
> 
> Hi JB,
> 
> This is the version of the Elastic Search I wish to push to:
> 
> {
>  "name" : "sitesc104w224m7",
>  "cluster_name" : "vela",
>  "cluster_uuid" : "fNKKGBcoTJmh42LDDxDkow",
>  "version" : {
>"number" : "6.8.12",
>"build_flavor" : "default",
>"build_type" : "tar",
>"build_hash" : "7a15d2a",
>"build_date" : "2020-08-12T07:27:20.804867Z",
>"build_snapshot" : false,
>"lucene_version" : "7.7.3",
>"minimum_wire_compatibility_version" : "5.6.0",
>"minimum_index_compatibility_version" : "5.0.0"
>  },
>  "tagline" : "You Know, for Search"
> }
> 
>> On Nov 2, 2020, at 21:17, Jean-Baptiste Onofre  wrote:
>> 
>> Hi Mark,
>> 
>> What elasticsearch version are you using ?
>> 
>> Regards
>> JB
>> 
>>> Le 2 nov. 2020 à 22:11, Mark Bordelon  a écrit :
>>> 
>>> With the following minimal configuration, (just setting the address, 
>>> authentication, and index prefix) …
>>> 
>>> 
>>> # Decanter Elasticsearch Appender Configuration
>>> 
>>> 
>>> # HTTP address of the elasticsearch nodes (separated with comma)
>>> addresses=http://elasticsearch-vela-1.sit.etrade.com:9200 
>>> 
>>> 
>>> # Basic username and password authentication
>>> username=batchoi
>>> password=batchoipwd
>>> 
>>> # The index name.
>>> # The index prefix is a static string used to construct the index
>>> index.prefix=karafCamelCWS
>>> # If true, it creates an index per Decanter event day
>>> #index.event.timestamped=true
>>> # For Elasticsearch < 7.5, index type is mandatory (not defined by default)
>>> index.type=
>>> 
>>> # Marshaller to use (json is heavily recommended)
>>> marshaller.target=(dataFormat=json)
>>> 
>>> 
>>> I get this 405 error when i install the elasticsearch appender feature.
>>> 
>>> 2020-11-02T15:32:15,870 | WARN  | EventAdminAsyncThread #23 | 
>>> ElasticsearchAppender| 188 - 
>>> org.apache.karaf.decanter.appender.elasticsearch - 2.5.0 | Can't append 
>>> into Elasticsearch
>>> org.elasticsearch.client.ResponseException: method [POST], host 
>>> [http://elasticsearch-vela-1.sit.etrade.com:9200], URI 
>>> [/karafCamelCWS-2020.11.02/], status line [HTTP/1.1 405 Method Not Allowed 
>>> >> [/karafCamelCWS-2020.11.02/], status line [HTTP/1.1 405 Method Not Allowed>]
>>> {"error":"Incorrect HTTP method for uri [/karafCamelCWS-2020.11.02/] and 
>>> method [POST], allowed: [HEAD, GET, PUT, DELETE]","status":405}
>>>  at 
>>> org.elasticsearch.client.RestClient.convertResponse(RestClient.java:283) 
>>> ~[!/:?]
>>>  at 
>>> org.elasticsearch.client.RestClient.performRequest(RestClient.java:261) 
>>> ~[!/:?]
>>>  at 
>>> org.elasticsearch.client.RestClient.performRequest(RestClient.java:235) 
>>> ~[!/:?]
>>>  at 
>>> org.apache.karaf.decanter.appender.elasticsearch.ElasticsearchAppender.send(ElasticsearchAppender.java:172)
>>>  ~[!/:?]
>>>  at 
>>> org.apache.karaf.decanter.appender.elasticsearch.ElasticsearchAppender.handleEvent(ElasticsearchAppender.java:152)
>>>  [!/:?]
>>>  at 
>>> org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)
>>>  [!/:?]
>>>  at 
>>> org.apache.felix.eventadmin.impl.tasks.HandlerTask.runWithoutBlacklistTiming(HandlerTask.java:82)
>>>  [!/:?]
>>>  at 
>>> org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:104)
>>>  [!/:?]
>>>  at 
>>> org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks$TaskExecuter.run(AsyncDeliverTasks.java:166)
>>>  [!/:?]
>>>  at 
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
>>> [?:1.8.0_51]
>>>  at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
>>> [?:1.8.0_51]
>>>  at 
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>  [?:1.8.0_51]
>>>  at 
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>  [?:1.8.0_51]
>>>  at java.lang.Thread.run(Thread.java:745) [?:1.8.0_51]
>>> 
>>> 
>>> If the HTTP verb could be set to PUT, seems like it might work based on 
>>> this:
>>> curl -H "Content-Type: application/json"  --user batchoi:batchoipwd \ 
>>> -XPOST "http://elasticsearch-vela-1.sit.etrade.com:9200/karafCamelCws 
>>> " -d ‘{ 
>>> "field" : "value"}’
>>> {"error":"Incorrect HTTP method for uri [/] and method [POST], allowed: 
>>> [HEAD, GET, DELETE]","status":405}
>>> 
>>> curl -H "Content-Type: application/json"  --user batchoi:batchoipwd \  
>>> -XPUT "http://elasticsearch-vela-1.sit.etrade.com:9200/karafCamelCws 
>>> 

Re: Kibana (2.5.0) -- ElasticSearch Appender config error

[Mark Bordelon]

Hi JB,

This is the version of the Elastic Search I wish to push to:

{
  "name" : "sitesc104w224m7",
  "cluster_name" : "vela",
  "cluster_uuid" : "fNKKGBcoTJmh42LDDxDkow",
  "version" : {
"number" : "6.8.12",
"build_flavor" : "default",
"build_type" : "tar",
"build_hash" : "7a15d2a",
"build_date" : "2020-08-12T07:27:20.804867Z",
"build_snapshot" : false,
"lucene_version" : "7.7.3",
"minimum_wire_compatibility_version" : "5.6.0",
"minimum_index_compatibility_version" : "5.0.0"
  },
  "tagline" : "You Know, for Search"
}

> On Nov 2, 2020, at 21:17, Jean-Baptiste Onofre  wrote:
> 
> Hi Mark,
> 
> What elasticsearch version are you using ?
> 
> Regards
> JB
> 
>> Le 2 nov. 2020 à 22:11, Mark Bordelon  a écrit :
>> 
>> With the following minimal configuration, (just setting the address, 
>> authentication, and index prefix) …
>> 
>> 
>> # Decanter Elasticsearch Appender Configuration
>> 
>> 
>> # HTTP address of the elasticsearch nodes (separated with comma)
>> addresses=http://elasticsearch-vela-1.sit.etrade.com:9200 
>> 
>> 
>> # Basic username and password authentication
>> username=batchoi
>> password=batchoipwd
>> 
>> # The index name.
>> # The index prefix is a static string used to construct the index
>> index.prefix=karafCamelCWS
>> # If true, it creates an index per Decanter event day
>> #index.event.timestamped=true
>> # For Elasticsearch < 7.5, index type is mandatory (not defined by default)
>> index.type=
>> 
>> # Marshaller to use (json is heavily recommended)
>> marshaller.target=(dataFormat=json)
>> 
>> 
>> I get this 405 error when i install the elasticsearch appender feature.
>> 
>> 2020-11-02T15:32:15,870 | WARN  | EventAdminAsyncThread #23 | 
>> ElasticsearchAppender| 188 - 
>> org.apache.karaf.decanter.appender.elasticsearch - 2.5.0 | Can't append into 
>> Elasticsearch
>> org.elasticsearch.client.ResponseException: method [POST], host 
>> [http://elasticsearch-vela-1.sit.etrade.com:9200], URI 
>> [/karafCamelCWS-2020.11.02/], status line [HTTP/1.1 405 Method Not Allowed 
>> > [/karafCamelCWS-2020.11.02/], status line [HTTP/1.1 405 Method Not Allowed>]
>> {"error":"Incorrect HTTP method for uri [/karafCamelCWS-2020.11.02/] and 
>> method [POST], allowed: [HEAD, GET, PUT, DELETE]","status":405}
>>   at 
>> org.elasticsearch.client.RestClient.convertResponse(RestClient.java:283) 
>> ~[!/:?]
>>   at 
>> org.elasticsearch.client.RestClient.performRequest(RestClient.java:261) 
>> ~[!/:?]
>>   at 
>> org.elasticsearch.client.RestClient.performRequest(RestClient.java:235) 
>> ~[!/:?]
>>   at 
>> org.apache.karaf.decanter.appender.elasticsearch.ElasticsearchAppender.send(ElasticsearchAppender.java:172)
>>  ~[!/:?]
>>   at 
>> org.apache.karaf.decanter.appender.elasticsearch.ElasticsearchAppender.handleEvent(ElasticsearchAppender.java:152)
>>  [!/:?]
>>   at 
>> org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)
>>  [!/:?]
>>   at 
>> org.apache.felix.eventadmin.impl.tasks.HandlerTask.runWithoutBlacklistTiming(HandlerTask.java:82)
>>  [!/:?]
>>   at 
>> org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:104)
>>  [!/:?]
>>   at 
>> org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks$TaskExecuter.run(AsyncDeliverTasks.java:166)
>>  [!/:?]
>>   at 
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
>> [?:1.8.0_51]
>>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
>> [?:1.8.0_51]
>>   at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>  [?:1.8.0_51]
>>   at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>  [?:1.8.0_51]
>>   at java.lang.Thread.run(Thread.java:745) [?:1.8.0_51]
>> 
>> 
>> If the HTTP verb could be set to PUT, seems like it might work based on this:
>> curl -H "Content-Type: application/json"  --user batchoi:batchoipwd \ 
>> -XPOST "http://elasticsearch-vela-1.sit.etrade.com:9200/karafCamelCws 
>> " -d ‘{ 
>> "field" : "value"}’
>> {"error":"Incorrect HTTP method for uri [/] and method [POST], allowed: 
>> [HEAD, GET, DELETE]","status":405}
>> 
>> curl -H "Content-Type: application/json"  --user batchoi:batchoipwd \  
>> -XPUT "http://elasticsearch-vela-1.sit.etrade.com:9200/karafCamelCws 
>> " -d ‘{ 
>> "field" : "value"}’
>> {"error":{"root_cause":[{"type":"remote_transport_exception","reason":"[sitesm111w88m7][10.247.33.25:9300][indices:admin/create]"}],"type":"illegal_argument_exception","reason":"unknown
>>  setting [index.field] please check that any 

Re: wrap: protocol for static assembly?

[Robert Varga]

On 03/11/2020 14:25, Jean-Baptiste Onofre wrote:
> Do you have a chance to be on slack ? I would love to have your help (at 
> least for the tests) about that (and your use case).

No Slack here, but I'll look at setting up -- but it is low prio.
Meanwhile I am IRC (but mostly not paying attention).

I can test-drive patches asynchronously, no problem :)

Regards,
Robert


OpenPGP_0x537D744B0A1E3F45.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Re: [VOTE] Apache Winegrower 1.0.0 release

[Jean-Baptiste Onofre]

+1 (binding)

Regards
JB

> Le 30 oct. 2020 à 08:00, Jean-Baptiste Onofre  a écrit :
> 
> Please vote to approve this release:
> 
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
> 
> This vote will be open for at least 72 hours.
> 
> Regards
> JB

Stout redirection

[Bernd Eckenfels]

Hello,

In Karaf Console the stdout is automatically redirected, however for other 
components in the runtime there seems to be no redirection to the standard 
logger.

Is there a setting I can use. Besides some unwilling software components which 
might use System.err, things like java.net.debug logging would be nice to have 
in the logfile.

Gruss
Bernd

--
http://bernd.eckenfels.net

[GitHub] [karaf-winegrower] rmannibucau opened a new pull request #25: make winegrower-servlet extensible + support OOTB asyncSupported and …

[GitBox]

rmannibucau opened a new pull request #25:
URL: https://github.com/apache/karaf-winegrower/pull/25


   …servletName attributes



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: wrap: protocol for static assembly?

[Jean-Baptiste Onofre]

Do you have a chance to be on slack ? I would love to have your help (at least 
for the tests) about that (and your use case).

Thanks !
Regards
JB

> Le 3 nov. 2020 à 14:01, Robert Varga  a écrit :
> 
> On 03/11/2020 13:42, Jean-Baptiste Onofre wrote:
>> Hi Robert,
> 
> Hey JB,
> 
>> Yes, the problem is about prerequisite and static.
>> 
>> I described the problem
>> here: https://issues.apache.org/jira/browse/KARAF-6573
>> 
>> 
>> I will work on a improvement/fix.
> 
> Thanks for confirming, I'll park my efforts until that fix then.
> 
> Regards,
> Robert

Re: wrap: protocol for static assembly?

[Robert Varga]

On 03/11/2020 13:42, Jean-Baptiste Onofre wrote:
> Hi Robert,

Hey JB,

> Yes, the problem is about prerequisite and static.
> 
> I described the problem
> here: https://issues.apache.org/jira/browse/KARAF-6573
> 
> 
> I will work on a improvement/fix.

Thanks for confirming, I'll park my efforts until that fix then.

Regards,
Robert

Re: wrap: protocol for static assembly?

[Jean-Baptiste Onofre]

Hi Robert,

Yes, the problem is about prerequisite and static.

I described the problem here: https://issues.apache.org/jira/browse/KARAF-6573 


I will work on a improvement/fix.

Regards
JB

> Le 3 nov. 2020 à 12:50, Robert Varga  a écrit :
> 
> On 03/11/2020 07:30, Jean-Baptiste Onofre wrote:
>> Hi,
>> 
>> Do you have static-framework feature in your pom dependencies ? With which 
>> scope ?
> 
> This is pretty much a copy of karaf-docker-example-static-dist, hence I
> have:
> 
> https://git.opendaylight.org/gerrit/c/odlparent/+/93414/10/karaf/test-static/pom.xml
> 
> The thing is: 'wrap' itself passes okay, the trouble is if a feature
> requires it -- i.e. the above works,  it is enough to add this line
> https://git.opendaylight.org/gerrit/c/odlparent/+/93414/10..11/karaf/test-static/pom.xml
> to break it.
> 
> odl-jung-2.1 is a simple feature:
> https://repo1.maven.org/maven2/org/opendaylight/odlparent/odl-jung-2.1/8.0.0/odl-jung-2.1-8.0.0-features.xml
> 
> It looks as though 'prerequisite' might be a problem?
> 
> Regards,
> Robert

Re: wrap: protocol for static assembly?

[Robert Varga]

On 03/11/2020 07:30, Jean-Baptiste Onofre wrote:
> Hi,
> 
> Do you have static-framework feature in your pom dependencies ? With which 
> scope ?

This is pretty much a copy of karaf-docker-example-static-dist, hence I
have:

https://git.opendaylight.org/gerrit/c/odlparent/+/93414/10/karaf/test-static/pom.xml

The thing is: 'wrap' itself passes okay, the trouble is if a feature
requires it -- i.e. the above works,  it is enough to add this line
https://git.opendaylight.org/gerrit/c/odlparent/+/93414/10..11/karaf/test-static/pom.xml
to break it.

odl-jung-2.1 is a simple feature:
https://repo1.maven.org/maven2/org/opendaylight/odlparent/odl-jung-2.1/8.0.0/odl-jung-2.1-8.0.0-features.xml

It looks as though 'prerequisite' might be a problem?

Regards,
Robert