fiware-orion

In current version of Orion Context Broker, 0.23.0, one of the new added features is that it supports filtering entities according to attribute values (NGSI v2). I am currently executing GET operations as indicated in http://telefonicaid.github.io/fiware-orion/api/v2/ and what I obtain is the whole set of entities, no filtering action. Could you please help me in this regard with a clear example on how to use the new REST API, NGSI v2? Thank you very much in advance The NGSIv2 filtering capabilities are based in the following operation: GET /v2/entities?q=<query_string> where query_string

I read the "Custom notifications" section in the NGSIv2 specification and I still have doubts in how to make this work. Do I have to put in my subscribe POST the following code as a payload? "httpCustom": { "url": "http://foo.com/entity/${id}", "headers": { "Content-Type": "text/plain" }, "method": "PUT", "qs": { "type": "${type}" }, "payload": "The temperature is ${temperature} degrees" } How would be a complete payload with a httpCustom for a subscribe with Authentication/Authorization? Lastly, is really necessary to use Rush , as stated at Rush Relayer ? In this case, we have to use a

Looking into the FIWARE Catalog I see two entries for Orion Context Broker: one for something called " Publish/Subscribe Broker " and another for " Configuration Manager ". So: Why are there two entries? Are they corresponding to the same piece of software? When should I have to use Publish/Subscribe Broker and when should I have to use Configuration Manager? UPDATE : since Orion 0.21.0, ConfMan functionality has been deprecated. Thus, using Orion as ConfMans is not recommended . Orion Context Broker is a server implementation of the NGSI9/10 standards for context management and context

I am using Orion Context Broker version 1.1.0 I had the only entity in my DB: { "id"=>"Room1", "type"=>"Room", "temperature"=>{"type"=>"none", "value"=>10, "metadata"=>{}} } I did not have any subscription . Then I created 3 subscriptions : [ { "subject"=>{"entities"=>[{"id"=>"Room1", "idPattern"=>"", "type"=>""}], "condition"=>{"attrs"=>["temperature"], "expression"=>{"q"=>"temperature>10"}}} }, { "subject"=>{"entities"=>[{"id"=>"Room1", "idPattern"=>"", "type"=>""}], "condition"=>{"attrs"=>["temperature"], "expression"=>{"q"=>"temperature<10"}}} }, { "subject"=>{"entities"=>[{"id"=>"Room1",

I am willing to install a Orion context broker standalone instance on a Ubuntu 12.04 Server using an image from FiWare Cloud. Looks like orion contextBroker is supporting mostly CentOS and it is distributed either a rpm package nor yum repository nor from sources directly (option that I would like to avoid if it is possible) There is some documentation / resource where can I learn from? This is all I could find: https://github.com/telefonicaid/fiware-orion/issues?q=is%3Aissue+is%3Aopen+ubuntu thanks Orion Context Broker works on Ubuntu but currently there is no .deb available so you need to

I have deployed an Orion instance in FILAB and I have configured the Cygnus inyector in order to store information in Cosmos. But...let us imagine a scenario in which the number of entities increases drastically. In this hypothetical scenario one instance of Orion GE wouldn't be enough so it would be necessary to deploy more instances. What would be the scale procedure? Taking into account the maximum quotas are: VM Instances: 5 VCPUs: 10 Hard Disk: 100 GB Memory: 10240 MB Public IP: 1 I understand that quotas may be subject to changes but what would be the free account limit? What would be