[Backlogmanager] [FIWARE-JIRA] (HELP-14250) [fiware-askbot] Connecting Cepheus to Orion

[Veronika Vlnkova (JIRA)]

     [ https://jira.fiware.org/browse/HELP-14250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Veronika Vlnkova reassigned HELP-14250:
---------------------------------------

    Assignee: Gilles Privat

> [fiware-askbot] Connecting Cepheus to Orion
> -------------------------------------------
>
>                 Key: HELP-14250
>                 URL: https://jira.fiware.org/browse/HELP-14250
>             Project: Help-Desk
>          Issue Type: Monitor
>            Reporter: Backlog Manager
>            Assignee: Gilles Privat
>              Labels: fiware-cep, fiware-orion
>
> Created question in FIWARE Q/A platform on 05-06-2018 at 20:06
> {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/1000/connecting-cepheus-to-orion/
> +Question:+
> Connecting Cepheus to Orion
> +Description:+
> Dear Fiware Support Team,
> I am having the following issue:
> I want to connect Cepheus to Orion (Orion as a source of events), process some queries and return new events to Orion (this time as destination). Like depicted below:
> Diagram: https://imgur.com/a/CI43Qis
> I have tried to configure Cepheus towards this goal, with the following example configuration:
> {
>   "host": "http://localhost:8080",
>   "in": [
>     {
>       "type": "PersonDetection",
>       "id": "PersonDetection",
>       "providers": [
>         {
>           "url": "http://orion:1026",
>           "serviceName": "==SERVICE_NAME==",
>           "servicePath": "==SERVICE_PATH=="
>         }
>       ],
>       "attributes": [
>         {
>           "name": "tagId",
>           "type": "Integer"
>         },
>         {
>           "name": "sectorId",
>           "type": "Integer"
>         },
>         {
>           "name": "positionX",
>           "type": "Float"
>         },
>         {
>           "name": "positionY",
>           "type": "Float"
>         },
>         {
>           "name": "ts",
>           "type": "Timestamp"
>         }
>       ]
>     }
>   ],
>   "out": [
>     {
>       "id": "CellDetection",
>       "type": "CellDetection",
>       "attributes": [
>         {
>           "name": "cellId",
>           "type": "Integer"
>         },
>         {
>           "name": "tagId",
>           "type": "Integer"
>         },
>         {
>           "name": "ts",
>           "type": "Timestamp"
>         }
>       ]
>     }
>   ],
>   "brokers": [
>     {
>       "url": "http://orion:1026",
>       "serviceName": "==SERVICE_NAME==",
>       "servicePath": "==SERVICE_PATH=="
>     }
>   ],
>   "statements": [
>   ]
> }
> With this configuration I want Cepheus to receive "PersonDetection" events (then run some query) and emit "CellDetection" events.
> However when Orion emits "PersonDetection" events, I see no logs in the Cepheus console. Which probably means that he's not receiving any events, maybe because he did not subscribe to Orion properly.
> The only logs generated by Cepheus are the following:
> epheus_1      | /usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.cepheus_1      |   'Supervisord is running as root and it is searching '
> cepheus_1      | 2018-06-05 18:19:12,362 CRIT Supervisor running as root (no user in config file)cepheus_1      | 2018-06-05 18:19:12,362 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsingcepheus_1      | 2018-06-05 18:19:12,378 INFO RPC interface 'supervisor' initialized
> cepheus_1      | 2018-06-05 18:19:12,378 CRIT Server 'unix_http_server' running without any HTTP authentication checking
> cepheus_1      | 2018-06-05 18:19:12,378 INFO supervisord started with pid 1
> cepheus_1      | 2018-06-05 18:19:13,381 INFO spawned: 'broker' with pid 9
> cepheus_1      | 2018-06-05 18:19:13,384 INFO spawned: 'cep' with pid 10
> cepheus_1      | 2018-06-05 18:19:14,387 INFO success: broker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
> cepheus_1      | 2018-06-05 18:19:14,387 INFO success: cep entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
> cepheus_1      | 2018-06-05 18:19:17.026  INFO 9 --- [           main] com.orange.cepheus.broker.Application    : Starting Application on e62b33e4a5c1 with PID 9 (/opt/cepheus/cepheus-broker
> .jar started by root in /opt/cepheus)
> cepheus_1      | 2018-06-05 18:19:17.162  INFO 10 --- [           main] com.orange.cepheus.cep.Application       : Starting Application on e62b33e4a5c1 with PID 10 (/opt/cepheus/cepheus-cep.
> jar started by root in /opt/cepheus)
> cepheus_1      | 2018-06-05 18:19:37.016  INFO 9 --- [           main] com.orange.cepheus.broker.Application    : Started Application in 20.785 seconds (JVM running for 23.597)
> cepheus_1      | 2018-06-05 18:19:37.639  INFO 10 --- [           main] com.orange.cepheus.cep.Application       : Started Application in 21.395 seconds (JVM running for 24.211)
> cepheus_1      | 2018-06-05 18:20 ... (more)



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)