Spec: multi-tenancy

[cdupont]

The Waziup platform need to provide tenant isolation: my sensors/data/apps should not be visible to others.
Orion provides a basic mechanism for tenant isolation called Fiware-service and Fiware-servicePath: http://fiware-orion.readthedocs.io/en/master/user/service_path/

[cdupont]

Proposition from Congduc:

#server: CAUTION must exist
waziup_server="http://broker.waziup.io/v2"

#project name
project_name='waziup"

#your organization: CHANGE HERE
organization_name="UPPA"

#sensor name: CHANGE HERE
sensor_name="Sensor"

#service path: CHANGE HERE
service_path="/UPPA/LIUPPA/T2I/CPHAM"

#the entity name will then be sensor_name+scr_addr, e.g. "Sensor1"
#the Fiware-ServicePath will be service_path, e.g. "/UPPA/LIUPPA/T2I/CPHAM"
#the Fiware-Service will be project_name+organization_name, e.g. "waziupUPPA"

So for UPPA, there are 3 sensors:

curl http://broker.waziup.io/v2/entities/Sensor10/attrs/TC/value --header Fiware-ServicePath:/UPPA/LIUPPA/T2I/CPHAM --header Fiware-Service:waziupUPPA -X GET

curl http://broker.waziup.io/v2/entities/Sensor3/attrs/temp/value --header Fiware-ServicePath:/UPPA/LIUPPA/T2I/CPHAM --header Fiware-Service:waziupUPPA -X GET

curl http://broker.waziup.io/v2/entities/Sensor6/attrs/temp/value --header Fiware-ServicePath:/UPPA/LIUPPA/T2I/CPHAM --header Fiware-Service:waziupUPPA -X GET

I proposed that each partner uses the following organization_name:

• "UPPA"
• "EGM"
• "IT21"
• "CREATENET"
• "CTIC"
• "UI"
• "ISPACE"
• "UGB"
• "WOELAB"
• "FARMERLINE"
• "C4A"
• "PUBD"

The service path can be whatever they want. Can we agree on these organization name?

[cdupont]

As far as I understand, Fiware-service is intended to provide tenant isolation, while Fiware-servicePath provides hierarchical organization of sensors.
It seems that service maps to different databases, while servicePath maps to different tables in the DB.

dbName=<fiware-service>
tableName=<fiware-servicePath>

Do we really need different databases?
For example, what if I want to retrieve all the sensors registered in Waziup, for example to make some statistics?
It seems that I can use a query on the root of the service path:
http://fiware-orion.readthedocs.io/en/master/user/service_path/

In this case, maybe it's better to have:

fiware-service = waziup
Fiware-ServicePath = pilot name

In the future, do you think that a sensor owner should be mapped to a fiware-service?
Just want to avoid additional complexity :)

[cdupont]

Actually, if we use only one fiware-service tenant, it's better to not use it at all (leave it empty): it will simplify the requests.

[cdupont]

see telefonicaid/fiware-pep-steelskin#166

[CongducPham]

I don't agree, I think we should put waziup. It is not that complicated
because we need the service path anyway.

regards,

Le 23/11/16 à 16:08, Corentin Dupont a écrit :

Actually, if we use only one fiware-service tenant, it's better to not
use it at all (leave it empty): it will simplify the requests.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
#49 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNEN-NUt2rSbHtWP9veLAQC0eIj3W3nks5rBFcDgaJpZM4KxYrE.

C. Pham.

|------------ Congduc PHAM - Professor --------------------------|
| LIUPPA - Equipe T2I | U.P.P.A. Pau |
| http://liuppa.univ-pau.fr/ | http://www.univ-pau.fr |
|----------------------------------------------------------------|
|UPPA, LIUPPA laboratory, UFR Sciences et Techniques |
|Avenue de l'Université - BP 1155 |
|64013 PAU CEDEX, FRANCE |
| |
|phone: 33 5 59 40 75 94 |
|fax: 33 5 59 40 76 54 |
|Congduc.Pham@univ-pau.fr http://www.univ-pau.fr/~cpham |
|----------------------------------------------------------------|

[cdupont]

@CongducPham Agreed. So let's keep it like that:

Fiware-Service:waziup
Fiware-ServicePath:/<pilot name>

Sublevels of Fiware-ServicePath are free to decide (for example /UPPA/LIUPPA/T2I/CPHAM)

[cdupont]

I did some research and it seems Orion supports recursive servicePath.
So I can search all sensors in waziup, using a wildcard # for the servicePath:

curl http://broker.waziup.io/v2/entities --header Fiware-ServicePath:/# --header Fiware-Service:waziup -X GET

This will return all sensors in UPPA (including all departments):

curl http://broker.waziup.io/v2/entities --header Fiware-ServicePath:/UPPA/# --header Fiware-Service:waziup -X GET

If I don't include the wildcard, the search is not recursive. This will return only sensors registered at "UPPA" level:

curl http://broker.waziup.io/v2/entities --header Fiware-ServicePath:/UPPA/ --header Fiware-Service:waziup -X GET

[cdupont]

I think we agree on the format, so closing.
We need to update all documentation and gateway code for complying.

[CongducPham]

Great, so to make thing clear: |fiware-service = waziup | |Fiware-ServicePath = /organization/what/ever/tree/you/want/here organization is one of following | - "UPPA" - "EGM" - "IT21" - "CREATENET" - "CTIC" - "UI" - "ISPACE" - "UGB" - "WOELAB" - "FARMERLINE" - "C4A" - "PUBD" Could all partners agree on that? regards, Le 24/11/16 à 10:41, Corentin Dupont a écrit :

I did some research and it seems Orion supports recursive servicePath. So I can search all sensors in waziup, using a wildcard |#| for the servicePath: |curl http://broker.waziup.io/v2/entities --header Fiware-ServicePath:/# --header Fiware-Service:waziup -X GET | This will return all sensors in UPPA (including all departments): |curl http://broker.waziup.io/v2/entities --header Fiware-ServicePath:/UPPA/# --header Fiware-Service:waziup -X GET | If I don't include the wildcard, the search is not recursive. This will return only sensors registered at "UPPA" level: |curl http://broker.waziup.io/v2/entities --header Fiware-ServicePath:/UPPA/ --header Fiware-Service:waziup -X GET | — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#49 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABNEN0-zyKA4Vl8kUHvhtsO58UBJkJxoks5rBVvSgaJpZM4KxYrE>.

C. Pham.

…

-- |------------ Congduc PHAM - Professor --------------------------| | LIUPPA - Equipe T2I | U.P.P.A. Pau | | http://liuppa.univ-pau.fr/ | http://www.univ-pau.fr | |----------------------------------------------------------------| |UPPA, LIUPPA laboratory, UFR Sciences et Techniques | |Avenue de l'Université - BP 1155 | |64013 PAU CEDEX, FRANCE | | | |phone: [33] (0) 5 59 40 75 94 | |fax: [33] (0) 5 59 40 76 54 | |Congduc.Pham@univ-pau.fr http://www.univ-pau.fr/~cpham | |----------------------------------------------------------------|

[cdupont]

OK

[sabrine2020]

OK

[cdupont]

need to update https://github.com/Waziup/Platform/blob/master/broker/broker_spec.md
with result of this discussion

[cdupont]

Done 4a3cb2c