[Nfd-dev] Creating multiple VMs with NFD quickly
Gusev, Peter
peter at remap.ucla.edu
Fri Apr 13 17:31:01 PDT 2018
Hi Junxiao,
Question: Why do you choose to install ndn-cxx, NFD, and ndn-tools from source code, as opposed from PPA repository?
To have latest build, and three previous versions - 0.6.1, 0.6.0 and 0.51
Suggestion: If you are building from source code, you can use Docker multi-stage build to reduce the size of the final image. Although you have a "cleanup" step, the intermediate layers would still contain the compilers etc. See my Dockerfile for an example on how to use multi-stage build: https://github.com/yoursunny/docker-nfd-build/blob/f999f3fa38a3c3f229471282b482338a1cabd177/Dockerfile
that’s helpful, I’ll look into this. This might be very useful for reducing ndnrtc image which is due to webrtc grows large
Question: With your Docker image and "ndndn", is it possible to connect to NFD via Unix sockets, or are the connections UDP/TCP only?
this will require some additional effort. I think, nfd.sock file shall be exposed (mounted) to the host machine in a specific place in the filesystem (is it /var/run/ ?). not sure how this will affect other applications using this directory on the host machine.
there also might be something else, like ~/.ndn folder that needs to be mounted, too.
Suggestion: If you can get Unix sockets working, you can build a separate Docker image for each NDN application, such as "nfd" "ndnping-client" "ndnping-server" "ndnrtc-consumer" "ndnrtc-producer”.
oh I see what you mean. Yes this is possible through using virtual volumes. I will consider doing this.
Thanks!
Yours, Junxiao
On Wed, Apr 11, 2018 at 3:22 PM, Peter Gusev <gpeetonn at gmail.com<mailto:gpeetonn at gmail.com>> wrote:
Hi devs,
I thought it might be useful to share what I have here.
I combed my tools and scripts that I wrote for running ndnrtc-client in Docker containers for general-purpose user, and results can be found in this repo - https://github.com/peetonn/ndn-docker/
which currently contains two "parts":
- node for stand-alone NDN Docker image (aka - docker pull peetonn/ndn-docker:latest )
- ndndn - a tool running multiple containers on arbitrary defined topologies using .dot files
I intend to continue adding features on this.
hope it might be useful for someone outside UCLA REMAP, room 1469c.
Thanks,
--
Peter Gusev
peter at remap.ucla.edu<mailto:peter at remap.ucla.edu>
+1 213 5872748
Research Scholar @ REMAP UCLA<http://remap.ucla.edu/>
Video streaming/ICN networks/Creative Development
_______________________________________________
Nfd-dev mailing list
Nfd-dev at lists.cs.ucla.edu<mailto:Nfd-dev at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20180414/aabcd10a/attachment-0001.html>
More information about the Nfd-dev
mailing list