[Mini-NDN] Content store for mini-ndn

Ashlesh Gawande (agawande) agawande at memphis.edu
Tue Nov 21 17:30:15 PST 2017


Okay, make sure you installed after compiling NFD.


To turn on the logs:

a) Modify /usr/local/etc/ndn/nfd.conf and turn on specific logs there (ex Forwader DEBUG).

or

b) To turn on all logs on all nodes:

Modify https://github.com/named-data/mini-ndn/blob/80eeea157b220139db6101d64aaeba05261758cb/ndn/nfd.py#L34this and do sudo ./install.sh -i to reinstall mini-ndn.
or

c) In the conf file add to turn on for specific nodes:

a: _ nfd-log-level=DEBUG


NFD logs are at /tmp/minindn/<node>/<node>.log


Ashlesh

________________________________
From: Aman Maldar <amanmaldar at gmail.com>
Sent: Tuesday, November 21, 2017 7:20:11 PM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: Content store for mini-ndn

Hello Ashlesh,
I am trying to print the logs for Content Store.

1) I added print statements in  mini-ndn/NFD/daemon/tables/cs.cpp file in Cs::find(param..) and Cs::insert(param..) function and at few other places in file.
I added,
NFD_LOG_DEBUG("TESTING CS LOGS");

2) cs.cpp already has core/logger.hpp included at the top.
module is already declared as - NFD_LOG_DEBUG("ContentStore")

3) executed ./waf in mini-ndn/NFD. Build is successful for changes in cs.cpp.

4) I ran
 > minindn --experiment=pingall -nPings=10
(convergence, pings executed good)

5) Checked the logs at
/tmp/minindn/a/log/nlsr.log

I see there are no additional entries with "TESTING CS LOGS"
Is this the way, I should check this scneario? Or am I doing something totally wrong?


6) Additinally,
/tmp/minindn/a.conf just have default_level NONE.
I tried making changes to this file as well, but I guess it makes no difference as this file is created new every time I run experiment.

Thank you.

On Mon, Nov 20, 2017 at 9:24 PM, Aman Maldar <amanmaldar at gmail.com<mailto:amanmaldar at gmail.com>> wrote:
Just rewriting few lines from previous mail, as I realized those were wrongly written.
 - Run a simple topology <consumer> - <forwarder> - <producer>
- consumer sends interest. Producer sends data. The data is cached at consumer node.
- Consumer request same interest next time. Interest is satisfied at the consumer itself.

Ashlesh,

Your answer is helpful. I will try to experiment with logs here.

Thank you for prompt reply.


On Mon, Nov 20, 2017 at 9:15 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Currently there is no way to access content store entries.

(https://redmine.named-data.net/issues/4317)


You could add some print statements in cs.cpp https://github.com/named-data/NFD/tree/master/daemon/table

You can add them as log statements in cs.cpp and then get the log of NFD in Mini-NDN.

See section 9.2.2  on how to add a logging module to NFD (http://named-data.gitlab.io/TR-NDN-0021-NFD-dev-guide/ndn-0021-nfd-guide.pdf)

Ashlesh
________________________________
From: Aman Maldar <amanmaldar at gmail.com<mailto:amanmaldar at gmail.com>>
Sent: Monday, November 20, 2017 8:04 PM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Content store for mini-ndn

Hello Everyone,
I appreciate your time and help. I am trying to do following things in mini-ndn.

- Run a simple topology <consumer> - <forwarder> - <producer>
- consumer sends interest. Producer sends data. The data us cached at producer node.
- Consumer request same data next time. Interest is satisfied at the producer itself.


This is pretty much similar to what I did in ndnSim. ndn-simple-with-content-freshnss.cpp

// /*
        // 1) at time 1 second requests Data from a producer that does not specify freshness
        // 2) at time 10 seconds requests the same Data packet as client 1

        // 3) at time 2 seconds requests Data from a producer that specifies freshness set to 2 seconds
        // 4) at time 12 seconds requests the same Data packet as client 3

        // Expectation:
        // Interests from 1, 3 and 4 will reach producers
        // Interset from 2 will be served from cache
        // */


I have gone through reference material and mail chains, but didn't find a way to access content store entries.
What is the best way to proceed with this?

Thank you.
--
Regards,
Mr. Maldar Aman M.
University of Massachusetts, Lowell



--
Regards,
Mr. Maldar Aman M.
University of Massachusetts, Lowell



--
Regards,
Mr. Maldar Aman M.
University of Massachusetts, Lowell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20171122/65f48c66/attachment-0001.html>


More information about the Mini-NDN mailing list