Wouter, to your older email - yes, you right. It would be nice to provide only simple js file for fast experience with IoTivity from device side.
And as Geoffroy mentioned, virtual sensors for demo is another nice usecase. Performance testing also, internal business. To make better experience of IoTivity, we should probably put forces together and make unified documented system so people who are interested in using IoTivity can make their hands dirty very quickly (docker) with smile on their face. It should be used not only for fast dev but also for understanding, how it works. Our driver: prevent facepalm from using IoTivity .) Ondrej Tomcik :: KISTLER :: measure, analyze, inovate From: Wouter van der Beek (wovander) [mailto:[email protected]] Sent: Friday, May 19, 2017 12:22 PM To: VanCutsem, Geoffroy; Tomcik Ondrej; Dwarkaprasad Dayama; iotivity-dev at lists.iotivity.org Subject: RE: [dev] Dockerized IoTivity Wow! Is it possible to add one more dockerized stack, e.g. one that takes the javascript file as input? It seems that you are the closest one to get there.. Kind Regards, Wouter From: VanCutsem, Geoffroy [mailto:[email protected]] Sent: 19 May 2017 10:45 To: Wouter van der Beek (wovander) <wovander at cisco.com<mailto:wovander at cisco.com>>; Ondrej Tomcik <Ondrej.Tomcik at kistler.com<mailto:Ondrej.Tomcik at kistler.com>>; Dwarkaprasad Dayama <dwarka.dayama at samsung.com<mailto:dwarka.dayama at samsung.com>>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] Dockerized IoTivity FWIW, we use a mechanism similar to what Wouter describes in our IoT to Cloud Smart Home demo (based on IoTivity/OCF) [1]. We have two Docker containers available, one that provides simulated sensors (OCF servers) and one that acts as a home gateway (OCF client). We use those for testing as it allows people to test different part of the system without needing the entire demo kits with all boards, sensors, etc. We're also looking at using that to test the scalability by deploying many virtual homes. The home gateway in a Docker container was also a very straightforward way for me to turn my off-the-shelf NAS at home into a OCF/IoTivity gateway. To be accurate, there is in fact a third Docker container that we use to run our cloud portal but this is not the same as the Dockerized cloud described below by OT, we use the iot-rest-api-server [2] to communicate from the cloud to the sensors (via the home gateway). [1] https://github.com/01org/SmartHome-Demo [2] https://github.com/01org/iot-rest-api-server Geoffroy From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Wouter van der Beek (wovander) Sent: Friday, May 19, 2017 10:42 AM To: Ondrej Tomcik <Ondrej.Tomcik at kistler.com<mailto:Ondrej.Tomcik at kistler.com>>; Dwarkaprasad Dayama <dwarka.dayama at samsung.com<mailto:dwarka.dayama at samsung.com>>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Dockerized IoTivity Hi OT, An dockerized version of the node.js stack (with the option to give the javascript file) will give OCF the possibility to run different clients and servers without recompiling everything. This would be an huge step forward for: - Creating demonstrators - Creating simulators: e.g. creating simple devices that can be used for testing o CTT o Alljoyn Bridge Note that docker runs on Window, Mac an raspberry pi... e.g. quite a lot of platforms that can be used.. Kind Regards, Wouter From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Ondrej Tomcik Sent: 19 May 2017 07:04 To: Dwarkaprasad Dayama <dwarka.dayama at samsung.com<mailto:dwarka.dayama at samsung.com>>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Dockerized IoTivity I don't see real benefit of "dockerizing" client or server code. But maybe I miss something. Client Server codebase is basicly c++,c or node.js sdk, which should be used for implemention of client or server. It's not a service which somebody will download and use. After the implementation of required functionality of client/server user maybe wants to dockerize it for his easier distribution to devices, but that's questionable. What do you think that dockerization of client/server will bring us? What will be the added value and which use-cases will it cover? Thanks Ondrej Tomcik :: KISTLER :: measure, analyze, inovate From: Dwarkaprasad Dayama [mailto:[email protected]] Sent: Friday, May 19, 2017 7:57 AM To: Tomcik Ondrej; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] Dockerized IoTivity Dear OT, Thank you for elaborating your contribution. It will be good if we can dockerize client and server base code as well. This will help to create Clients and Servers at ease and quickly. What do you say? Regards Dwarka ---------------------------------------------------------------------------------- Software R&D Center | Software Strategy Team | Open Source Group Open Connectivity Foundation (OCF) | Iotivity | Javascript Foundation (JSF) From: Ondrej Tomcik [mailto:[email protected]] Sent: Thursday, May 18, 2017 8:47 PM To: Dwarkaprasad Dayama <dwarka.dayama at samsung.com<mailto:dwarka.dayama at samsung.com>>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [dev] Dockerized IoTivity Dear Dwarka, >From what I understand about node.js IoTivity, it's a lirary for writing >IoTivity client/server. Dockerized cloud is following OCF standards and any >client and server can communicate with it. What you have to do is signUp and >signIn with your favourite oauth provider = or very soon with your custom one >provided by mapped volume to account-server container. Here are cloud client-server examples: https://wiki.iotivity.org/iotivity_cloud_-_programming_guide#run_client What is signup / signin? https://github.com/iotivity/iotivity/blob/master/resource/src/OCAccountManager.cpp#L81 >From c++ AccountManager view, PostResourceRepresentation with filled DeviceId, AuthProvider and AuthCode. >From CSDK octbstack view, OCDoResource with payload mentioned above. BR Ondrej Tomcik :: KISTLER :: measure, analyze, inovate From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Dwarkaprasad Dayama Sent: Thursday, May 18, 2017 12:01 PM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Dockerized IoTivity Hi OT, It is certainly appreciable effort. Good to see IoTivity cloud adoption getting easier. Do you have any future plans for this contribution? Like supporting Wouter's request? Regards Dwarka ---------------------------------------------------------------------------------- Software R&D Center | Software Strategy Team | Open Source Group Open Connectivity Foundation (OCF) | Iotivity | Javascript Foundation (JSF) From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Wouter van der Beek (wovander) Sent: Wednesday, May 17, 2017 6:53 PM To: Ondrej Tomcik <Ondrej.Tomcik at kistler.com<mailto:Ondrej.Tomcik at kistler.com>>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Dockerized IoTivity Cool! Is the node.js version also supported? e.g. run the iotivitynode.js with an argument that takes the node.js? in this way everyone can run different applications/clients with the same docker image.. Kind Regards, Wouter From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Ondrej Tomcik Sent: 17 May 2017 10:40 To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Dockerized IoTivity Hello community, IoTivity was dockerized, merged, documented. Don't be afraid to use it. Documentation: https://wiki.iotivity.org/docker Docker Images with documentation: https://hub.docker.com/r/iotivity/interface/ https://hub.docker.com/r/iotivity/accountserver/ https://hub.docker.com/r/iotivity/resourcedirectory/ https://hub.docker.com/r/iotivity/messagequeue/ Review: https://gerrit.iotivity.org/gerrit/#/c/19907/ Have a nice day. OT -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170519/a1737732/attachment.html>
