-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
align fiware-service and fiware-servicepath syntax and semantics with Orion #336
Comments
Be aware that, for most of the components, the service path is not exactly hierarchical, as they only accept a single level in the hierarchy. The multitenancy mechanism is clearer than the service_path. |
Actually, I'd say that the only one that interprests service path in hierarchicalway in IoTP is Orion. However, this is not a problem, as the single-element case is a particular case of the hierarchical approach. |
There are currently several issues opened concerning how the service and servicepath flags work in the IoTAgents. I'm going to close all of them and leave this one as a single backlog item. We can also hold the appropriate discussions and requests here. Summarizing, there are three differences in the behavior between the Orion Context Broker and the IoTAgents:
We should add this issue to the component backlog and evaluate its importance. |
Trying to fix unit tests in LWM2M IOTA, I have discovered an additional issue regarding the alignment of fiware-service and fiware-servicepath with Orion Context Broker. From https://github.com/telefonicaid/fiware-orion/blob/master/doc/manuals/user/multitenancy.md:
Actually, the IOTA node library stores devices in its registry with service and subservice including uppercase characters.
|
In order to avoid the problem you mention @dcalvoalonso the recomendation is to use always service and servicepath in lowercase. |
Then I see two options regarding this point:
What do you think @fgalan ? |
You mean the test is failing right now? As far as I see at https://github.com/telefonicaid/iotagent-node-lib/commits/master Travis is ok at the present moment at master... |
Tests are not passed for LWM2M IOTA. I have run them locally and several (passive attributes and commands) fail due to this problem. As you can see in travis.yml, tests are not automatically executed yet. |
I think that modifying the library to convert to lowercase could have some degree of backward compatibility risk that needs to be carefully analyzed. Specially for existing integrations using IOTA UL or IOTA JSON. Thus, I think that at the present moment just adjusting the test is enough. In addition, once you fix it I'd suggest to set Travis in automatic mode at LWM2M IOTA repo (in an independent PR). Could you manage with that, please? |
Ok, it makes sense to me. I am right now working on it! |
I have just submitted a PR to enable Travis CI for LWM2M IOTA repo and to pass unit tests: telefonicaid/lightweightm2m-iotagent#105 They are still not passed because of #569 |
Hello. I'm new to Fiware. While following tutorials, I found that a queryContext to Orion with |
@hylowaker I think your interpretation is correct. Orion supports |
IoTA layer must be aligned with CB layer in the syntax and semantics of fiware-service and fiware-servicepath. Currently it is not aligned. Notably, the definition of the syntax and semantics of both headers is described by
http://fiware-orion.readthedocs.io/en/develop/user/service_path/index.html
http://fiware-orion.readthedocs.io/en/develop/user/multitenancy/index.html
and probably we would need a central definition place for both headers and to cross reference it from the different GEs that make use of it.
/cc @fgalan @mrutid
The text was updated successfully, but these errors were encountered: