https://nmsl.cs.sfu.ca/api.php?action=feedcontributions&feedformat=atom&user=Nitin.chiluka 2026-04-07T08:13:15Z User contributions MediaWiki 1.35.1 https://nmsl.cs.sfu.ca/index.php?title=pCDN:Release&diff=1952 2008-05-06T16:20:27Z

<p>Nitin.chiluka: </p> <hr /> <div>We list the features, installers, and instructions for each release on this page. The complete list of features apriori Version 1, please see [[pCDN:Feature | here]].<br /> <br /> = Version 1 =<br /> == Features ==<br /> * '''Reliable Server(s)''': <br /> ** ''Recovery from server crashes'': We preserve the on-line client state across pCDN server restarts. This means that the pCDN server can be restarted anytime without scarifying the connected clients. Administrators may restart the pCDN server for several reasons, such as power outage, hardware upgrades, or operating system updates. This new feature minimizes the service downtime without deploying additional hardware. <br /> ** ''Providing online backup servers'': We support one-to-many replication for an even more robust system. CBC many deploy one or more secondary servers, which will take over the responsibility of the primary server when failures are detected. We support hot switchover, which means all the secondary servers are always initialized and can become the next primary server immediately after failures.<br /> * '''Geo-Fencing''': We support city-level geo-fencing in North America and country-level in other regions. Administrators configure the geo-fencing database through a user-friendly GUI, which can be remotely run at any workstations.<br /> * '''Unified Admin Tool''': We integrate interface for server monitoring, content admin, and geo-fencing into a unified GUI. Administrators can remotely run this user interface and complete all their daily tasks in it.<br /> * '''Optimized Sender-Receiver Matching''': We support geolocation-aware sender lookups, which leverage on existing Geo-IP database to search for the closest senders for individual receivers. Our algorithm:<br /> ** ''Enhances download speeds''.<br /> ** ''Reduces load on backbone network''.<br /> * ''' Performance Tuning and Scalability Testing''': <br /> ** ''Revised protocol design and implementation'': We've refined our protocol design, as well as implementation, for a more responsive and robust content delivery system. <br /> ** ''Tested for large scale clients and replicated servers:'' We've rigorously tested our system with several hundred clients from all over the world. We've also validated our replicated server implementation with as many as eight servers.<br /> * '''Software Management and Support''': We've set up web-based info-sharing and bug-tracking systems.<br /> ** ''Wiki system providing details of the pCDN system at: [http://nsl.cs.sfu.ca/wiki/index.php/pCDN Wiki].<br /> ** ''Bug Tracking and Feature Suggestion System at: [http://nsl.cs.sfu.ca/bug/ Bugzilla].<br /> <br /> == Software ==<br /> === Candidate 1 ===<br /> Please find the initial release candidates as follows.<br /> * Server Installer [[media:pCDN_Server_V1_RC1.exe]] <br /> * Client Installer [[media:pCDN_Client_V1_RC1.exe]]<br /> === Candidate 2 ===<br /> Please find the initial release candidates as follows.<br /> * Server Installer [[media:pCDN_Server_V1_RC1.exe]] <br /> * Client Installer [[media:pCDN_Client_V1_RC2.exe]]<br /> == Instructions ==<br /> The installation instructions for this release can be found [[pCDN:Installation | here]]</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Release&diff=1951 2008-05-06T16:19:08Z

<p>Nitin.chiluka: </p> <hr /> <div>We list the features, installers, and instructions for each release on this page. The complete list of features apriori Version 1, please see [[pCDN:Feature | here]].<br /> <br /> = Version 1 =<br /> == Features ==<br /> * '''Reliable Server(s)''': <br /> ** ''Recovery from server crashes'': We preserve the on-line client state across pCDN server restarts. This means that the pCDN server can be restarted anytime without scarifying the connected clients. Administrators may restart the pCDN server for several reasons, such as power outage, hardware upgrades, or operating system updates. This new feature minimizes the service downtime without deploying additional hardware. <br /> ** ''Providing online backup servers'': We support one-to-many replication for an even more robust system. CBC many deploy one or more secondary servers, which will take over the responsibility of the primary server when failures are detected. We support hot switchover, which means all the secondary servers are always initialized and can become the next primary server immediately after failures.<br /> * '''Geo-Fencing''': We support city-level geo-fencing in North America and country-level in other regions. Administrators configure the geo-fencing database through a user-friendly GUI, which can be remotely run at any workstations.<br /> * '''Unified Admin Tool''': We integrate interface for server monitoring, content admin, and geo-fencing into a unified GUI. Administrators can remotely run this user interface and complete all their daily tasks in it.<br /> * '''Optimized Sender-Receiver Matching''': We support geolocation-aware sender lookups, which leverage on existing Geo-IP database to search for the closest senders for individual receivers. Our algorithm:<br /> ** ''Enhances download speeds''.<br /> ** ''Reduces load on backbone network''.<br /> * ''' Performance Tuning and Scalability Testing''': <br /> ** ''Revised protocol design and implementation'': We've refined our protocol design, as well as implementation, for a more responsive and robust content delivery system. <br /> ** ''Tested for large scale clients and replicated servers:'' We've rigorously tested our system with several hundred clients from all over the world. We've also validated our replicated server implementation with as many as eight servers.<br /> * '''Software Management and Support''': We've set up web-based info-sharing and bug-tracking systems.<br /> ** ''Wiki system providing details of the pCDN system at: [http://nsl.cs.sfu.ca/wiki/index.php/pCDN Wiki].<br /> ** ''Bug Tracking and Feature Suggestion System at: [http://nsl.cs.sfu.ca/bug/ Bugzilla].<br /> <br /> == Software ==<br /> === Candidate 1 ===<br /> Please find the initial release candidates as follows.<br /> * Server Installer [[media:pCDN_Server_V1_RC1.exe]] <br /> * Client Installer [[media:pCDN_Client_V1_RC2.exe]]<br /> == Instructions ==<br /> The installation instructions for this release can be found [[pCDN:Installation | here]]</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=File:pCDN_Client_V1_RC2.exe&diff=1950 2008-05-06T16:13:43Z

<p>Nitin.chiluka: </p> <hr /> <div></div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=Private:pCDN:Peer_Matching&diff=1938 2008-04-29T16:53:00Z

<p>Nitin.chiluka: </p> <hr /> <div>== '''Proposed Algorithm Simulation'''==<br /> === '''Experimental Setup''' ===<br /> * First, we get info of all the ASes in the world from Team CYRMU's IP to ASNum Mapping Project using netcat. Using this project, we get all ASes' numbers and their names along with the country they belong to. We filter to derive only CA ASes.<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26 <br /> * CAIDA provides dataset on inter-AS relationships among all ASes. We filter to derive inter-AS relationships within Canada using only CA ASes generated from step 1. This accounts for 375 ASes, 643 links (53 p2p, 5 s2s, 585 c2p).<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt <br /> * Using these links and ASes, we generate a shortest policy path matrix which contains the shortest paths between any two ASes using the algorithm discussed in [Mao et al].<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf <br /> ** To test whether the distances computed are correct, we verified with Rogers BGP site and Teleglobe<br /> *** https://supernoc.rogerstelecom.net/ops/ and <br /> *** http://lg.as6453.net/bin/lg.cgi <br /> * AT &amp; T provides IP Range and AS number mapping. We use this dataset to extract only Canadian IP Ranges and corresponding ASes. We generate 84000 number of IPs belonging to these ASes; 10 each from every IP range – AS mapping.<br /> ** http://www.research.att.com/~jiawang/as_traceroute/ <br /> * Using IP-Geo database, we identify the latitude and longitude for each of these peers.<br /> ** Maxmind IP-Geo database<br /> * We test 4 algorithms - AS Order, Geo-location, Random, Network - on a varied size of set of peers {100, 300, 500, 1000, 3000, 5000, 10000, 15000, 20000} randomly picked from 84000 peers generated in step 4. We run all 3 algorithms on the same set of peers and note insertion, lookup, deletion times as well as AS Hops. We repeat this experiment 5 times.<br /> ** For testing of N peers, we take an array of 2N peers. First N peers are used for inserting and deleting. The rest N peers are used for searching. That is, we first insert N peers (from 1 to N), then lookup for next N peers (N+1 to 2N) and then delete N peers (from 1 to N). We note each individual time.<br /> * The simulation has been implemented in Java and the experiments have been performed on a 2GHz and 2GB RAM machine.<br /> <br /> === '''ISP Friendly Algorithm''' ===<br /> Steps:<br /> * We populate IP to AS Map (IPASMap) using the IP Range and AS mapping present in AT &amp; T dataset. This map can be used for searching an AS for a given IP.<br /> <br /> * We then load the pre-computed shortest policy path matrix (ShortestPathMatrix) which contains the shortest distance between every 2 individual ASes.<br /> <br /> * The data structure we use is a HashMap (ASMap) which contains ASNum as the key and the peerlist (the list of peers in that AS) corresponding to that AS.<br /> <br /> <br /> <br /> == '''Ideas''' ==<br /> <br /> * Verification of AS Shortest Paths<br /> <br /> * Experimental Setup<br /> ** # Peers: {100, 300, 500, 1000, 3000, 5000, 8000}<br /> ** # Senders: {2, 5, 10, 15, 20}<br /> ** # Sessions: 1000<br /> ** Algos: Random, Network, Geo, AS_Order(ISP-Friendly)<br /> ** Metrics: Min, Avg, Max, Output<br /> ** Output: Hops (Aggregate, P2P, C2P)<br /> <br /> * Search Efficiency:<br /> ** If multiple shortest paths are existing, choose the least &quot;cost&quot; (s2s=0, p2p=1, c2p=2)<br /> <br /> * Check practicality<br /> ** What kind of data we need initially and periodically<br /> ** How often we need them<br /> ** We implement the algorithm to determine AS relationships<br /> <br /> * Large graphs<br /> ** Can we get the US &amp; CA graph?<br /> ** Can we optimize this matrix.<br /> <br /> * Usage of ISP + Network / Geolocation Algorithms<br /> ** We reduce the number of IP hops<br /> <br /> * Diameter of the Canada's AS graph: 13 AS Hops<br /> <br /> == Important Dates ==<br /> *Conferences<br /> ** May 2: SIGCOMM<br /> ** Aug 9: InfoComm<br /> <br /> == '''References and Links''' ==<br /> <br /> * IP to ASNum Mapping project from Team CYRMU<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26<br /> * CAIDA's Inter-AS relationships<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt<br /> * On AS-level Path Inference<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf<br /> * AT &amp; T IP-Range and ASNum mapping<br /> ** a. http://www.research.att.com/~jiawang/as_traceroute/</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=Private:pCDN:Peer_Matching&diff=1936 2008-04-25T20:43:09Z

<p>Nitin.chiluka: </p> <hr /> <div>== '''Proposed Algorithm Simulation'''==<br /> === '''Experimental Setup''' ===<br /> * First, we get info of all the ASes in the world from Team CYRMU's IP to ASNum Mapping Project using netcat. Using this project, we get all ASes' numbers and their names along with the country they belong to. We filter to derive only CA ASes.<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26 <br /> * CAIDA provides dataset on inter-AS relationships among all ASes. We filter to derive inter-AS relationships within Canada using only CA ASes generated from step 1. This accounts for 375 ASes, 643 links (53 p2p, 5 s2s, 585 c2p).<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt <br /> * Using these links and ASes, we generate a shortest policy path matrix which contains the shortest paths between any two ASes using the algorithm discussed in [Mao et al].<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf <br /> ** To test whether the distances computed are correct, we verified with Rogers BGP site and Teleglobe<br /> *** https://supernoc.rogerstelecom.net/ops/ and <br /> *** http://lg.as6453.net/bin/lg.cgi <br /> * AT &amp; T provides IP Range and AS number mapping. We use this dataset to extract only Canadian IP Ranges and corresponding ASes. We generate 84000 number of IPs belonging to these ASes; 10 each from every IP range – AS mapping.<br /> ** http://www.research.att.com/~jiawang/as_traceroute/ <br /> * Using IP-Geo database, we identify the latitude and longitude for each of these peers.<br /> ** Maxmind IP-Geo database<br /> * We test 4 algorithms - AS Order, Geo-location, Random, Network - on a varied size of set of peers {100, 300, 500, 1000, 3000, 5000, 10000, 15000, 20000} randomly picked from 84000 peers generated in step 4. We run all 3 algorithms on the same set of peers and note insertion, lookup, deletion times as well as AS Hops. We repeat this experiment 5 times.<br /> ** For testing of N peers, we take an array of 2N peers. First N peers are used for inserting and deleting. The rest N peers are used for searching. That is, we first insert N peers (from 1 to N), then lookup for next N peers (N+1 to 2N) and then delete N peers (from 1 to N). We note each individual time.<br /> * The simulation has been implemented in Java and the experiments have been performed on a 2GHz and 2GB RAM machine.<br /> <br /> === '''ISP Friendly Algorithm''' ===<br /> Steps:<br /> * We populate IP to AS Map (IPASMap) using the IP Range and AS mapping present in AT &amp; T dataset. This map can be used for searching an AS for a given IP.<br /> <br /> * We then load the pre-computed shortest policy path matrix (ShortestPathMatrix) which contains the shortest distance between every 2 individual ASes.<br /> <br /> * The data structure we use is a HashMap (ASMap) which contains ASNum as the key and the peerlist (the list of peers in that AS) corresponding to that AS.<br /> <br /> <br /> <br /> == '''Ideas''' ==<br /> <br /> * Verification of AS Shortest Paths<br /> <br /> * Experimental Setup<br /> ** # Peers: {100, 300, 500, 1000, 3000, 5000, 8000}<br /> ** # Senders: {2, 5, 10, 15, 20}<br /> ** # Sessions: 1000<br /> ** Algos: Random, Network, Geo, AS_Order(ISP-Friendly)<br /> ** Metrics: Min, Avg, Max, Output<br /> ** Output: Hops (Aggregate, P2P, C2P)<br /> <br /> * Search Efficiency:<br /> ** If multiple shortest paths are existing, choose the least &quot;cost&quot; (s2s=0, p2p=1, c2p=2)<br /> <br /> * Check practicality<br /> ** What kind of data we need initially and periodically<br /> ** How often we need them<br /> ** We implement the algorithm to determine AS relationships<br /> <br /> * Large graphs<br /> ** Can we get the US &amp; CA graph?<br /> ** Can we optimize this matrix.<br /> <br /> * Usage of ISP + Network / Geolocation Algorithms<br /> ** We reduce the number of IP hops<br /> <br /> * Diameter of the graph<br /> <br /> == Important Dates ==<br /> *Conferences<br /> ** May 2: SIGCOMM<br /> ** Aug 9: InfoComm<br /> <br /> == '''References and Links''' ==<br /> <br /> * IP to ASNum Mapping project from Team CYRMU<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26<br /> * CAIDA's Inter-AS relationships<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt<br /> * On AS-level Path Inference<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf<br /> * AT &amp; T IP-Range and ASNum mapping<br /> ** a. http://www.research.att.com/~jiawang/as_traceroute/</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=Private:pCDN:Peer_Matching&diff=1935 2008-04-25T20:42:47Z

<p>Nitin.chiluka: </p> <hr /> <div>== '''Proposed Algorithm Simulation'''==<br /> === '''Experimental Setup''' ===<br /> * First, we get info of all the ASes in the world from Team CYRMU's IP to ASNum Mapping Project using netcat. Using this project, we get all ASes' numbers and their names along with the country they belong to. We filter to derive only CA ASes.<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26 <br /> * CAIDA provides dataset on inter-AS relationships among all ASes. We filter to derive inter-AS relationships within Canada using only CA ASes generated from step 1. This accounts for 375 ASes, 643 links (53 p2p, 5 s2s, 585 c2p).<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt <br /> * Using these links and ASes, we generate a shortest policy path matrix which contains the shortest paths between any two ASes using the algorithm discussed in [Mao et al].<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf <br /> ** To test whether the distances computed are correct, we verified with Rogers BGP site and Teleglobe<br /> *** https://supernoc.rogerstelecom.net/ops/ and <br /> *** http://lg.as6453.net/bin/lg.cgi <br /> * AT &amp; T provides IP Range and AS number mapping. We use this dataset to extract only Canadian IP Ranges and corresponding ASes. We generate 84000 number of IPs belonging to these ASes; 10 each from every IP range – AS mapping.<br /> ** http://www.research.att.com/~jiawang/as_traceroute/ <br /> * Using IP-Geo database, we identify the latitude and longitude for each of these peers.<br /> ** Maxmind IP-Geo database<br /> * We test 4 algorithms - AS Order, Geo-location, Random, Network - on a varied size of set of peers {100, 300, 500, 1000, 3000, 5000, 10000, 15000, 20000} randomly picked from 84000 peers generated in step 4. We run all 3 algorithms on the same set of peers and note insertion, lookup, deletion times as well as AS Hops. We repeat this experiment 5 times.<br /> ** For testing of N peers, we take an array of 2N peers. First N peers are used for inserting and deleting. The rest N peers are used for searching. That is, we first insert N peers (from 1 to N), then lookup for next N peers (N+1 to 2N) and then delete N peers (from 1 to N). We note each individual time.<br /> * The simulation has been implemented in Java and the experiments have been performed on a 2GHz and 2GB RAM machine.<br /> <br /> === '''ISP Friendly Algorithm''' ===<br /> Steps:<br /> * We populate IP to AS Map (IPASMap) using the IP Range and AS mapping present in AT &amp; T dataset. This map can be used for searching an AS for a given IP.<br /> <br /> * We then load the pre-computed shortest policy path matrix (ShortestPathMatrix) which contains the shortest distance between every 2 individual ASes.<br /> <br /> * The data structure we use is a HashMap (ASMap) which contains ASNum as the key and the peerlist (the list of peers in that AS) corresponding to that AS.<br /> <br /> <br /> <br /> == '''Ideas''' ==<br /> <br /> * Verification of AS Shortest Paths<br /> <br /> * Experimental Setup<br /> ** # Peers: {100, 300, 500, 1000, 3000, 5000, 8000}<br /> ** # Senders: {2, 5, 10, 15, 20}<br /> ** # Sessions: 1000<br /> ** Algos: Random, Network, Geo, AS_Order(ISP-Friendly)<br /> ** Metrics: Min, Avg, Max, Output<br /> ** Output: Hops (Aggregate, P2P, C2P)<br /> <br /> * Search Efficiency:<br /> ** If multiple shortest paths are existing, choose the least &quot;cost&quot; (s2s=0, p2p=1, c2p=2)<br /> <br /> * Check practicality<br /> ** What kind of data we need initially and periodically<br /> ** How often we need them<br /> ** We implement the algorithm to determine AS relationships<br /> <br /> * Large graphs<br /> ** Can we get the US &amp; CA graph?<br /> ** Can we optimize this matrix.<br /> <br /> * Usage of ISP + Network / Geolocation Algorithms<br /> ** We reduce the number of IP hops<br /> <br /> * Diameter of the graph<br /> <br /> == Important Dates ==<br /> #Conferences<br /> * May 2: SIGCOMM<br /> * Aug 9: InfoComm<br /> <br /> == '''References and Links''' ==<br /> <br /> * IP to ASNum Mapping project from Team CYRMU<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26<br /> * CAIDA's Inter-AS relationships<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt<br /> * On AS-level Path Inference<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf<br /> * AT &amp; T IP-Range and ASNum mapping<br /> ** a. http://www.research.att.com/~jiawang/as_traceroute/</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=Private:pCDN:Peer_Matching&diff=1934 2008-04-25T20:33:36Z

<p>Nitin.chiluka: </p> <hr /> <div>== '''Proposed Algorithm Simulation'''==<br /> === '''Experimental Setup''' ===<br /> * First, we get info of all the ASes in the world from Team CYRMU's IP to ASNum Mapping Project using netcat. Using this project, we get all ASes' numbers and their names along with the country they belong to. We filter to derive only CA ASes.<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26 <br /> * CAIDA provides dataset on inter-AS relationships among all ASes. We filter to derive inter-AS relationships within Canada using only CA ASes generated from step 1. This accounts for 375 ASes, 643 links (53 p2p, 5 s2s, 585 c2p).<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt <br /> * Using these links and ASes, we generate a shortest policy path matrix which contains the shortest paths between any two ASes using the algorithm discussed in [Mao et al].<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf <br /> ** To test whether the distances computed are correct, we verified with Rogers BGP site and Teleglobe<br /> *** https://supernoc.rogerstelecom.net/ops/ and <br /> *** http://lg.as6453.net/bin/lg.cgi <br /> * AT &amp; T provides IP Range and AS number mapping. We use this dataset to extract only Canadian IP Ranges and corresponding ASes. We generate 84000 number of IPs belonging to these ASes; 10 each from every IP range – AS mapping.<br /> ** http://www.research.att.com/~jiawang/as_traceroute/ <br /> * Using IP-Geo database, we identify the latitude and longitude for each of these peers.<br /> ** Maxmind IP-Geo database<br /> * We test 4 algorithms - AS Order, Geo-location, Random, Network - on a varied size of set of peers {100, 300, 500, 1000, 3000, 5000, 10000, 15000, 20000} randomly picked from 84000 peers generated in step 4. We run all 3 algorithms on the same set of peers and note insertion, lookup, deletion times as well as AS Hops. We repeat this experiment 5 times.<br /> ** For testing of N peers, we take an array of 2N peers. First N peers are used for inserting and deleting. The rest N peers are used for searching. That is, we first insert N peers (from 1 to N), then lookup for next N peers (N+1 to 2N) and then delete N peers (from 1 to N). We note each individual time.<br /> * The simulation has been implemented in Java and the experiments have been performed on a 2GHz and 2GB RAM machine.<br /> <br /> === '''ISP Friendly Algorithm''' ===<br /> Steps:<br /> * We populate IP to AS Map (IPASMap) using the IP Range and AS mapping present in AT &amp; T dataset. This map can be used for searching an AS for a given IP.<br /> <br /> * We then load the pre-computed shortest policy path matrix (ShortestPathMatrix) which contains the shortest distance between every 2 individual ASes.<br /> <br /> * The data structure we use is a HashMap (ASMap) which contains ASNum as the key and the peerlist (the list of peers in that AS) corresponding to that AS.<br /> <br /> <br /> <br /> == Ideas ==<br /> <br /> * Verification of AS Shortest Paths<br /> <br /> * Experimental Setup<br /> ** # Peers: {100, 300, 500, 1000, 3000, 5000, 8000}<br /> ** # Senders: {2, 5, 10, 15, 20}<br /> ** # Sessions: 1000<br /> ** Algos: Random, Network, Geo, AS_Order(ISP-Friendly)<br /> ** Metrics: Min, Avg, Max, Output<br /> ** Output: Hops (Aggregate, P2P, C2P)<br /> <br /> * Search Efficiency:<br /> ** If multiple shortest paths are existing, choose the least &quot;cost&quot; (s2s=0, p2p=1, c2p=2)<br /> <br /> * Check practicality<br /> ** What kind of data we need initially and periodically<br /> ** How often we need them<br /> ** We implement the algorithm to determine AS relationships<br /> <br /> * Large graphs<br /> ** Can we get the US &amp; CA graph?<br /> ** Can we optimize this matrix.<br /> <br /> * Usage of ISP + Network / Geolocation Algorithms<br /> ** We reduce the number of IP hops<br /> <br /> * Diameter of the graph<br /> <br /> == References and Links ==<br /> <br /> * IP to ASNum Mapping project from Team CYRMU<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26<br /> * CAIDA's Inter-AS relationships<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt<br /> * On AS-level Path Inference<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf<br /> * AT &amp; T IP-Range and ASNum mapping<br /> ** a. http://www.research.att.com/~jiawang/as_traceroute/</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=Private:pCDN:Peer_Matching&diff=1933 2008-04-25T20:33:03Z

<p>Nitin.chiluka: </p> <hr /> <div>== Proposed Algorithm Simulation==<br /> === Experimental Setup ===<br /> * First, we get info of all the ASes in the world from Team CYRMU's IP to ASNum Mapping Project using netcat. Using this project, we get all ASes' numbers and their names along with the country they belong to. We filter to derive only CA ASes.<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26 <br /> * CAIDA provides dataset on inter-AS relationships among all ASes. We filter to derive inter-AS relationships within Canada using only CA ASes generated from step 1. This accounts for 375 ASes, 643 links (53 p2p, 5 s2s, 585 c2p).<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt <br /> * Using these links and ASes, we generate a shortest policy path matrix which contains the shortest paths between any two ASes using the algorithm discussed in [Mao et al].<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf <br /> ** To test whether the distances computed are correct, we verified with Rogers BGP site and Teleglobe<br /> *** https://supernoc.rogerstelecom.net/ops/ and <br /> *** http://lg.as6453.net/bin/lg.cgi <br /> * AT &amp; T provides IP Range and AS number mapping. We use this dataset to extract only Canadian IP Ranges and corresponding ASes. We generate 84000 number of IPs belonging to these ASes; 10 each from every IP range – AS mapping.<br /> ** http://www.research.att.com/~jiawang/as_traceroute/ <br /> * Using IP-Geo database, we identify the latitude and longitude for each of these peers.<br /> ** Maxmind IP-Geo database<br /> * We test 4 algorithms - AS Order, Geo-location, Random, Network - on a varied size of set of peers {100, 300, 500, 1000, 3000, 5000, 10000, 15000, 20000} randomly picked from 84000 peers generated in step 4. We run all 3 algorithms on the same set of peers and note insertion, lookup, deletion times as well as AS Hops. We repeat this experiment 5 times.<br /> ** For testing of N peers, we take an array of 2N peers. First N peers are used for inserting and deleting. The rest N peers are used for searching. That is, we first insert N peers (from 1 to N), then lookup for next N peers (N+1 to 2N) and then delete N peers (from 1 to N). We note each individual time.<br /> * The simulation has been implemented in Java and the experiments have been performed on a 2GHz and 2GB RAM machine.<br /> <br /> === '''ISP Friendly Algorithm''' ===<br /> Steps:<br /> * We populate IP to AS Map (IPASMap) using the IP Range and AS mapping present in AT &amp; T dataset. This map can be used for searching an AS for a given IP.<br /> <br /> * We then load the pre-computed shortest policy path matrix (ShortestPathMatrix) which contains the shortest distance between every 2 individual ASes.<br /> <br /> * The data structure we use is a HashMap (ASMap) which contains ASNum as the key and the peerlist (the list of peers in that AS) corresponding to that AS.<br /> <br /> <br /> <br /> == Ideas ==<br /> <br /> * Verification of AS Shortest Paths<br /> <br /> * Experimental Setup<br /> ** # Peers: {100, 300, 500, 1000, 3000, 5000, 8000}<br /> ** # Senders: {2, 5, 10, 15, 20}<br /> ** # Sessions: 1000<br /> ** Algos: Random, Network, Geo, AS_Order(ISP-Friendly)<br /> ** Metrics: Min, Avg, Max, Output<br /> ** Output: Hops (Aggregate, P2P, C2P)<br /> <br /> * Search Efficiency:<br /> ** If multiple shortest paths are existing, choose the least &quot;cost&quot; (s2s=0, p2p=1, c2p=2)<br /> <br /> * Check practicality<br /> ** What kind of data we need initially and periodically<br /> ** How often we need them<br /> ** We implement the algorithm to determine AS relationships<br /> <br /> * Large graphs<br /> ** Can we get the US &amp; CA graph?<br /> ** Can we optimize this matrix.<br /> <br /> * Usage of ISP + Network / Geolocation Algorithms<br /> ** We reduce the number of IP hops<br /> <br /> * Diameter of the graph<br /> <br /> == References and Links ==<br /> <br /> * IP to ASNum Mapping project from Team CYRMU<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26<br /> * CAIDA's Inter-AS relationships<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt<br /> * On AS-level Path Inference<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf<br /> * AT &amp; T IP-Range and ASNum mapping<br /> ** a. http://www.research.att.com/~jiawang/as_traceroute/</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=Private:pCDN:Peer_Matching&diff=1932 2008-04-25T20:29:13Z

<p>Nitin.chiluka: </p> <hr /> <div>== Proposed Algorithm Simulation==<br /> * Experimental Setup:<br /> * First, we get info of all the ASes in the world from Team CYRMU's IP to ASNum Mapping Project using netcat. Using this project, we get all ASes' numbers and their names along with the country they belong to. We filter to derive only CA ASes.<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26 <br /> * CAIDA provides dataset on inter-AS relationships among all ASes. We filter to derive inter-AS relationships within Canada using only CA ASes generated from step 1. This accounts for 375 ASes, 643 links (53 p2p, 5 s2s, 585 c2p).<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt <br /> * Using these links and ASes, we generate a shortest policy path matrix which contains the shortest paths between any two ASes using the algorithm discussed in [Mao et al].<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf <br /> ** To test whether the distances computed are correct, we verified with Rogers BGP site and Teleglobe<br /> *** https://supernoc.rogerstelecom.net/ops/ and <br /> *** http://lg.as6453.net/bin/lg.cgi <br /> * AT &amp; T provides IP Range and AS number mapping. We use this dataset to extract only Canadian IP Ranges and corresponding ASes. We generate 84000 number of IPs belonging to these ASes; 10 each from every IP range – AS mapping.<br /> ** http://www.research.att.com/~jiawang/as_traceroute/ <br /> * Using IP-Geo database, we identify the latitude and longitude for each of these peers.<br /> ** Maxmind IP-Geo database<br /> * We test 4 algorithms - AS Order, Geo-location, Random, Network - on a varied size of set of peers {100, 300, 500, 1000, 3000, 5000, 10000, 15000, 20000} randomly picked from 84000 peers generated in step 4. We run all 3 algorithms on the same set of peers and note insertion, lookup, deletion times as well as AS Hops. We repeat this experiment 5 times.<br /> ** For testing of N peers, we take an array of 2N peers. First N peers are used for inserting and deleting. The rest N peers are used for searching. That is, we first insert N peers (from 1 to N), then lookup for next N peers (N+1 to 2N) and then delete N peers (from 1 to N). We note each individual time.<br /> * The simulation has been implemented in Java and the experiments have been performed on a 2GHz and 2GB RAM machine.<br /> <br /> '''ISP Friendly Algorithm'''<br /> Steps:<br /> * We populate IP to AS Map (IPASMap) using the IP Range and AS mapping present in AT &amp; T dataset. This map can be used for searching an AS for a given IP.<br /> <br /> * We then load the pre-computed shortest policy path matrix (ShortestPathMatrix) which contains the shortest distance between every 2 individual ASes.<br /> <br /> * The data structure we use is a HashMap (ASMap) which contains ASNum as the key and the peerlist (the list of peers in that AS) corresponding to that AS.<br /> <br /> <br /> <br /> == Ideas ==<br /> <br /> * Verification of AS Shortest Paths<br /> <br /> * Experimental Setup<br /> ** # Peers: {100, 300, 500, 1000, 3000, 5000, 8000}<br /> ** # Senders: {2, 5, 10, 15, 20}<br /> ** # Sessions: 1000<br /> ** Algos: Random, Network, Geo, AS_Order(ISP-Friendly)<br /> ** Metrics: Min, Avg, Max, Output<br /> ** Output: Hops (Aggregate, P2P, C2P)<br /> <br /> * Search Efficiency:<br /> ** If multiple shortest paths are existing, choose the least &quot;cost&quot; (s2s=0, p2p=1, c2p=2)<br /> <br /> * Check practicality<br /> ** What kind of data we need initially and periodically<br /> ** How often we need them<br /> ** We implement the algorithm to determine AS relationships<br /> <br /> * Large graphs<br /> ** Can we get the US &amp; CA graph?<br /> ** Can we optimize this matrix.<br /> <br /> * Usage of ISP + Network / Geolocation Algorithms<br /> ** We reduce the number of IP hops<br /> <br /> * Diameter of the graph<br /> <br /> == References and Links ==<br /> <br /> * IP to ASNum Mapping project from Team CYRMU<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26<br /> * CAIDA's Inter-AS relationships<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt<br /> * On AS-level Path Inference<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf<br /> * AT &amp; T IP-Range and ASNum mapping<br /> ** a. http://www.research.att.com/~jiawang/as_traceroute/</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=Private:pCDN:Peer_Matching&diff=1931 2008-04-25T20:27:52Z

<p>Nitin.chiluka: </p> <hr /> <div>== Proposed Algorithm Simulation==<br /> * Experimental Setup:<br /> * First, we get info of all the ASes in the world from Team CYRMU's IP to ASNum Mapping Project using netcat. Using this project, we get all ASes' numbers and their names along with the country they belong to. We filter to derive only CA ASes.<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26 <br /> * CAIDA provides dataset on inter-AS relationships among all ASes. We filter to derive inter-AS relationships within Canada using only CA ASes generated from step 1. This accounts for 375 ASes, 643 links (53 p2p, 5 s2s, 585 c2p).<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt <br /> * Using these links and ASes, we generate a shortest policy path matrix which contains the shortest paths between any two ASes using the algorithm discussed in [Mao et al].<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf <br /> ** To test whether the distances computed are correct, we verified with Rogers BGP site and Teleglobe<br /> *** https://supernoc.rogerstelecom.net/ops/ and <br /> *** http://lg.as6453.net/bin/lg.cgi <br /> * AT &amp; T provides IP Range and AS number mapping. We use this dataset to extract only Canadian IP Ranges and corresponding ASes. We generate 84000 number of IPs belonging to these ASes; 10 each from every IP range – AS mapping.<br /> ** http://www.research.att.com/~jiawang/as_traceroute/ <br /> * Using IP-Geo database, we identify the latitude and longitude for each of these peers.<br /> ** Maxmind IP-Geo database<br /> * We test 4 algorithms - AS Order, Geo-location, Random, Network - on a varied size of set of peers {100, 300, 500, 1000, 3000, 5000, 10000, 15000, 20000} randomly picked from 84000 peers generated in step 4. We run all 3 algorithms on the same set of peers and note insertion, lookup, deletion times as well as AS Hops. We repeat this experiment 5 times.<br /> ** For testing of N peers, we take an array of 2N peers. First N peers are used for inserting and deleting. The rest N peers are used for searching. That is, we first insert N peers (from 1 to N), then lookup for next N peers (N+1 to 2N) and then delete N peers (from 1 to N). We note each individual time.<br /> * The simulation has been implemented in Java and the experiments have been performed on a 2GHz and 2GB RAM machine.<br /> <br /> '''ISP Friendly Algorithm'''<br /> Steps:<br /> * We populate IP to AS Map (IPASMap) using the IP Range and AS mapping present in AT &amp; T dataset. This map can be used for searching an AS for a given IP.<br /> <br /> * We then load the pre-computed shortest policy path matrix (ShortestPathMatrix) which contains the shortest distance between every 2 individual ASes.<br /> <br /> * The data structure we use is a HashMap (ASMap) which contains ASNum as the key and the peerlist (the list of peers in that AS) corresponding to that AS.<br /> <br /> <br /> i.<br /> {<br /> Insert(Peer peer){<br /> <br /> ASNum = IPASMap.getASNum(peer.IP); //obtain the AS this peer belongs to<br /> <br /> <br /> If (ASNum does not exist in ASMap) // check if this AS already exists<br /> ASMap.insert(ASNum);<br /> <br /> <br /> ASMap[ASNum].peerlist.add(peer); // now add this peer to that AS<br /> <br /> } <br /> }<br /> <br /> ii.<br /> Delete(Peer peer){<br /> //obtain the AS this peer belongs to<br /> ASNum = IPASMap.getASNum(peer.IP);<br /> <br /> //remove the peer from that AS<br /> ASMap[ASNum].peerlist.remove(peer);<br /> <br /> }<br /> <br /> iii.<br /> Lookup(Peer peer){<br /> declare RetPeerlist;<br /> declare retPeerCount;<br /> <br /> //obtain the AS this peer belongs to<br /> ASNum = IPASMap.getASNum(peer.IP);<br /> <br /> // Get a list of all ASes that are in the data structure<br /> ASlist = ASMap.getASList();<br /> <br /> // and sort these ASes based on the distance from ASNum<br /> // to each of the ASes in ASlist, using the matrix<br /> SortedASlist = ASlist.sort(ASNum , ShortestPathMatrix[][]);<br /> <br /> count = 0;<br /> <br /> // Noting the number of AS hops<br /> ashops = 0;<br /> <br /> for(i=0;i&lt;SortedASlist.size;i++){<br /> j=0;<br /> while(count&lt;retPeerCount &amp;&amp; j&lt;SortedASlist[i].peerlist.size){<br /> Peer tmp = SortedASlist[i].peerlist[j++];<br /> RetPeerlist.add(tmp);<br /> <br /> // get the AS this peer belongs to<br /> tmpASNum = SortedASlist[i];<br /> ashops += ShortestPathMatrix[ASNum][tmpASNum];<br /> count++;<br /> }<br /> if(count&gt;=retPeerCount)<br /> break;<br /> }<br /> return RetPeerlist;<br /> }<br /> <br /> }}<br /> <br /> <br /> == Ideas ==<br /> <br /> * Verification of AS Shortest Paths<br /> <br /> * Experimental Setup<br /> ** # Peers: {100, 300, 500, 1000, 3000, 5000, 8000}<br /> ** # Senders: {2, 5, 10, 15, 20}<br /> ** # Sessions: 1000<br /> ** Algos: Random, Network, Geo, AS_Order(ISP-Friendly)<br /> ** Metrics: Min, Avg, Max, Output<br /> ** Output: Hops (Aggregate, P2P, C2P)<br /> <br /> * Search Efficiency:<br /> ** If multiple shortest paths are existing, choose the least &quot;cost&quot; (s2s=0, p2p=1, c2p=2)<br /> <br /> * Check practicality<br /> ** What kind of data we need initially and periodically<br /> ** How often we need them<br /> ** We implement the algorithm to determine AS relationships<br /> <br /> * Large graphs<br /> ** Can we get the US &amp; CA graph?<br /> ** Can we optimize this matrix.<br /> <br /> * Usage of ISP + Network / Geolocation Algorithms<br /> ** We reduce the number of IP hops<br /> <br /> * Diameter of the graph<br /> <br /> == References and Links ==<br /> <br /> * IP to ASNum Mapping project from Team CYRMU<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26<br /> * CAIDA's Inter-AS relationships<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt<br /> * On AS-level Path Inference<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf<br /> * AT &amp; T IP-Range and ASNum mapping<br /> ** a. http://www.research.att.com/~jiawang/as_traceroute/</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=Private:pCDN:Peer_Matching&diff=1930 2008-04-25T20:26:44Z

<p>Nitin.chiluka: </p> <hr /> <div>== Proposed Algorithm Simulation==<br /> * Experimental Setup:<br /> * First, we get info of all the ASes in the world from Team CYRMU's IP to ASNum Mapping Project using netcat. Using this project, we get all ASes' numbers and their names along with the country they belong to. We filter to derive only CA ASes.<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26 <br /> * CAIDA provides dataset on inter-AS relationships among all ASes. We filter to derive inter-AS relationships within Canada using only CA ASes generated from step 1. This accounts for 375 ASes, 643 links (53 p2p, 5 s2s, 585 c2p).<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt <br /> * Using these links and ASes, we generate a shortest policy path matrix which contains the shortest paths between any two ASes using the algorithm discussed in [Mao et al].<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf <br /> ** To test whether the distances computed are correct, we verified with Rogers BGP site and Teleglobe<br /> *** https://supernoc.rogerstelecom.net/ops/ and <br /> *** http://lg.as6453.net/bin/lg.cgi <br /> * AT &amp; T provides IP Range and AS number mapping. We use this dataset to extract only Canadian IP Ranges and corresponding ASes. We generate 84000 number of IPs belonging to these ASes; 10 each from every IP range – AS mapping.<br /> ** http://www.research.att.com/~jiawang/as_traceroute/ <br /> * Using IP-Geo database, we identify the latitude and longitude for each of these peers.<br /> ** Maxmind IP-Geo database<br /> * We test 4 algorithms - AS Order, Geo-location, Random, Network - on a varied size of set of peers {100, 300, 500, 1000, 3000, 5000, 10000, 15000, 20000} randomly picked from 84000 peers generated in step 4. We run all 3 algorithms on the same set of peers and note insertion, lookup, deletion times as well as AS Hops. We repeat this experiment 5 times.<br /> ** For testing of N peers, we take an array of 2N peers. First N peers are used for inserting and deleting. The rest N peers are used for searching. That is, we first insert N peers (from 1 to N), then lookup for next N peers (N+1 to 2N) and then delete N peers (from 1 to N). We note each individual time.<br /> * The simulation has been implemented in Java and the experiments have been performed on a 2GHz and 2GB RAM machine.<br /> <br /> '''ISP Friendly Algorithm'''<br /> Steps:<br /> * We populate IP to AS Map (IPASMap) using the IP Range and AS mapping present in AT &amp; T dataset. This map can be used for searching an AS for a given IP.<br /> <br /> * We then load the pre-computed shortest policy path matrix (ShortestPathMatrix) which contains the shortest distance between every 2 individual ASes.<br /> <br /> * The data structure we use is a HashMap (ASMap) which contains ASNum as the key and the peerlist (the list of peers in that AS) corresponding to that AS.<br /> <br /> {{<br /> i.<br /> <br /> Insert(Peer peer){<br /> //obtain the AS this peer belongs to<br /> ASNum = IPASMap.getASNum(peer.IP);<br /> <br /> // check if this AS already exists<br /> If (ASNum does not exist in ASMap)<br /> ASMap.insert(ASNum);<br /> <br /> // now add this peer to that AS<br /> ASMap[ASNum].peerlist.add(peer);<br /> <br /> } <br /> <br /> <br /> ii.<br /> Delete(Peer peer){<br /> //obtain the AS this peer belongs to<br /> ASNum = IPASMap.getASNum(peer.IP);<br /> <br /> //remove the peer from that AS<br /> ASMap[ASNum].peerlist.remove(peer);<br /> <br /> }<br /> <br /> iii.<br /> Lookup(Peer peer){<br /> declare RetPeerlist;<br /> declare retPeerCount;<br /> <br /> //obtain the AS this peer belongs to<br /> ASNum = IPASMap.getASNum(peer.IP);<br /> <br /> // Get a list of all ASes that are in the data structure<br /> ASlist = ASMap.getASList();<br /> <br /> // and sort these ASes based on the distance from ASNum<br /> // to each of the ASes in ASlist, using the matrix<br /> SortedASlist = ASlist.sort(ASNum , ShortestPathMatrix[][]);<br /> <br /> count = 0;<br /> <br /> // Noting the number of AS hops<br /> ashops = 0;<br /> <br /> for(i=0;i&lt;SortedASlist.size;i++){<br /> j=0;<br /> while(count&lt;retPeerCount &amp;&amp; j&lt;SortedASlist[i].peerlist.size){<br /> Peer tmp = SortedASlist[i].peerlist[j++];<br /> RetPeerlist.add(tmp);<br /> <br /> // get the AS this peer belongs to<br /> tmpASNum = SortedASlist[i];<br /> ashops += ShortestPathMatrix[ASNum][tmpASNum];<br /> count++;<br /> }<br /> if(count&gt;=retPeerCount)<br /> break;<br /> }<br /> return RetPeerlist;<br /> }<br /> <br /> }}<br /> <br /> <br /> == Ideas ==<br /> <br /> * Verification of AS Shortest Paths<br /> <br /> * Experimental Setup<br /> ** # Peers: {100, 300, 500, 1000, 3000, 5000, 8000}<br /> ** # Senders: {2, 5, 10, 15, 20}<br /> ** # Sessions: 1000<br /> ** Algos: Random, Network, Geo, AS_Order(ISP-Friendly)<br /> ** Metrics: Min, Avg, Max, Output<br /> ** Output: Hops (Aggregate, P2P, C2P)<br /> <br /> * Search Efficiency:<br /> ** If multiple shortest paths are existing, choose the least &quot;cost&quot; (s2s=0, p2p=1, c2p=2)<br /> <br /> * Check practicality<br /> ** What kind of data we need initially and periodically<br /> ** How often we need them<br /> ** We implement the algorithm to determine AS relationships<br /> <br /> * Large graphs<br /> ** Can we get the US &amp; CA graph?<br /> ** Can we optimize this matrix.<br /> <br /> * Usage of ISP + Network / Geolocation Algorithms<br /> ** We reduce the number of IP hops<br /> <br /> * Diameter of the graph<br /> <br /> == References and Links ==<br /> <br /> * IP to ASNum Mapping project from Team CYRMU<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26<br /> * CAIDA's Inter-AS relationships<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt<br /> * On AS-level Path Inference<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf<br /> * AT &amp; T IP-Range and ASNum mapping<br /> ** a. http://www.research.att.com/~jiawang/as_traceroute/</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=Private:pCDN:Peer_Matching&diff=1929 2008-04-25T20:25:49Z

<p>Nitin.chiluka: </p> <hr /> <div>== Proposed Algorithm Simulation==<br /> * Experimental Setup:<br /> * First, we get info of all the ASes in the world from Team CYRMU's IP to ASNum Mapping Project using netcat. Using this project, we get all ASes' numbers and their names along with the country they belong to. We filter to derive only CA ASes.<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26 <br /> * CAIDA provides dataset on inter-AS relationships among all ASes. We filter to derive inter-AS relationships within Canada using only CA ASes generated from step 1. This accounts for 375 ASes, 643 links (53 p2p, 5 s2s, 585 c2p).<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt <br /> * Using these links and ASes, we generate a shortest policy path matrix which contains the shortest paths between any two ASes using the algorithm discussed in [Mao et al].<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf <br /> ** To test whether the distances computed are correct, we verified with Rogers BGP site and Teleglobe<br /> *** https://supernoc.rogerstelecom.net/ops/ and <br /> *** http://lg.as6453.net/bin/lg.cgi <br /> * AT &amp; T provides IP Range and AS number mapping. We use this dataset to extract only Canadian IP Ranges and corresponding ASes. We generate 84000 number of IPs belonging to these ASes; 10 each from every IP range – AS mapping.<br /> ** http://www.research.att.com/~jiawang/as_traceroute/ <br /> * Using IP-Geo database, we identify the latitude and longitude for each of these peers.<br /> ** Maxmind IP-Geo database<br /> * We test 4 algorithms - AS Order, Geo-location, Random, Network - on a varied size of set of peers {100, 300, 500, 1000, 3000, 5000, 10000, 15000, 20000} randomly picked from 84000 peers generated in step 4. We run all 3 algorithms on the same set of peers and note insertion, lookup, deletion times as well as AS Hops. We repeat this experiment 5 times.<br /> ** For testing of N peers, we take an array of 2N peers. First N peers are used for inserting and deleting. The rest N peers are used for searching. That is, we first insert N peers (from 1 to N), then lookup for next N peers (N+1 to 2N) and then delete N peers (from 1 to N). We note each individual time.<br /> * The simulation has been implemented in Java and the experiments have been performed on a 2GHz and 2GB RAM machine.<br /> <br /> '''ISP Friendly Algorithm'''<br /> Steps:<br /> * We populate IP to AS Map (IPASMap) using the IP Range and AS mapping present in AT &amp; T dataset. This map can be used for searching an AS for a given IP.<br /> <br /> * We then load the pre-computed shortest policy path matrix (ShortestPathMatrix) which contains the shortest distance between every 2 individual ASes.<br /> <br /> * The data structure we use is a HashMap (ASMap) which contains ASNum as the key and the peerlist (the list of peers in that AS) corresponding to that AS.<br /> <br /> i.<br /> { <br /> Insert(Peer peer){<br /> //obtain the AS this peer belongs to<br /> ASNum = IPASMap.getASNum(peer.IP);<br /> <br /> // check if this AS already exists<br /> If (ASNum does not exist in ASMap)<br /> ASMap.insert(ASNum);<br /> <br /> // now add this peer to that AS<br /> ASMap[ASNum].peerlist.add(peer);<br /> <br /> } <br /> <br /> <br /> ii.<br /> Delete(Peer peer){<br /> //obtain the AS this peer belongs to<br /> ASNum = IPASMap.getASNum(peer.IP);<br /> <br /> //remove the peer from that AS<br /> ASMap[ASNum].peerlist.remove(peer);<br /> <br /> }<br /> <br /> iii.<br /> Lookup(Peer peer){<br /> declare RetPeerlist;<br /> declare retPeerCount;<br /> <br /> //obtain the AS this peer belongs to<br /> ASNum = IPASMap.getASNum(peer.IP);<br /> <br /> // Get a list of all ASes that are in the data structure<br /> ASlist = ASMap.getASList();<br /> <br /> // and sort these ASes based on the distance from ASNum<br /> // to each of the ASes in ASlist, using the matrix<br /> SortedASlist = ASlist.sort(ASNum , ShortestPathMatrix[][]);<br /> <br /> count = 0;<br /> <br /> // Noting the number of AS hops<br /> ashops = 0;<br /> <br /> for(i=0;i&lt;SortedASlist.size;i++){<br /> j=0;<br /> while(count&lt;retPeerCount &amp;&amp; j&lt;SortedASlist[i].peerlist.size){<br /> Peer tmp = SortedASlist[i].peerlist[j++];<br /> RetPeerlist.add(tmp);<br /> <br /> // get the AS this peer belongs to<br /> tmpASNum = SortedASlist[i];<br /> ashops += ShortestPathMatrix[ASNum][tmpASNum];<br /> count++;<br /> }<br /> if(count&gt;=retPeerCount)<br /> break;<br /> }<br /> return RetPeerlist;<br /> }<br /> <br /> }<br /> <br /> <br /> == Ideas ==<br /> <br /> * Verification of AS Shortest Paths<br /> <br /> * Experimental Setup<br /> ** # Peers: {100, 300, 500, 1000, 3000, 5000, 8000}<br /> ** # Senders: {2, 5, 10, 15, 20}<br /> ** # Sessions: 1000<br /> ** Algos: Random, Network, Geo, AS_Order(ISP-Friendly)<br /> ** Metrics: Min, Avg, Max, Output<br /> ** Output: Hops (Aggregate, P2P, C2P)<br /> <br /> * Search Efficiency:<br /> ** If multiple shortest paths are existing, choose the least &quot;cost&quot; (s2s=0, p2p=1, c2p=2)<br /> <br /> * Check practicality<br /> ** What kind of data we need initially and periodically<br /> ** How often we need them<br /> ** We implement the algorithm to determine AS relationships<br /> <br /> * Large graphs<br /> ** Can we get the US &amp; CA graph?<br /> ** Can we optimize this matrix.<br /> <br /> * Usage of ISP + Network / Geolocation Algorithms<br /> ** We reduce the number of IP hops<br /> <br /> * Diameter of the graph<br /> <br /> == References and Links ==<br /> <br /> * IP to ASNum Mapping project from Team CYRMU<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26<br /> * CAIDA's Inter-AS relationships<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt<br /> * On AS-level Path Inference<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf<br /> * AT &amp; T IP-Range and ASNum mapping<br /> ** a. http://www.research.att.com/~jiawang/as_traceroute/</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=Private:pCDN:Peer_Matching&diff=1928 2008-04-25T20:22:44Z

<p>Nitin.chiluka: </p> <hr /> <div><br /> == Proposed Algorithm Simulation==<br /> Setup:<br /> 1. First, we get info of all the ASes in the world from Team CYRMU's IP to ASNum Mapping Project using netcat. Using this project, we get all ASes' numbers and their names along with the country they belong to. We filter to derive only CA ASes.<br /> a. http://www.team-cymru.org/?sec=8&amp;opt=26 <br /> 2. CAIDA provides dataset on inter-AS relationships among all ASes. We filter to derive inter-AS relationships within Canada using only CA ASes generated from step 1. This accounts for 375 ASes, 643 links (53 p2p, 5 s2s, 585 c2p).<br /> a. http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt <br /> 3. Using these links and ASes, we generate a shortest policy path matrix which contains the shortest paths between any two ASes using the algorithm discussed in [Mao et al].<br /> a. http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf <br /> b. To test whether the distances computed are correct, we verified with Rogers BGP site and Teleglobe<br /> i. https://supernoc.rogerstelecom.net/ops/ and <br /> ii. http://lg.as6453.net/bin/lg.cgi <br /> 4. AT &amp; T provides IP Range and AS number mapping. We use this dataset to extract only Canadian IP Ranges and corresponding ASes. We generate 84000 number of IPs belonging to these ASes; 10 each from every IP range – AS mapping.<br /> a. http://www.research.att.com/~jiawang/as_traceroute/ <br /> 5. Using IP-Geo database, we identify the latitude and longitude for each of these peers.<br /> a. Maxmind IP-Geo database<br /> 6. We test 3 algorithms - AS Order, Geo-location, Random - on a varied size of set of peers {100, 300, 500, 1000, 3000, 5000, 10000, 15000, 20000} randomly picked from 84000 peers generated in step 4. We run all 3 algorithms on the same set of peers and note insertion, lookup, deletion times as well as AS Hops. We repeat this experiment 5 times.<br /> a. For testing of N peers, we take an array of 2N peers. First N peers are used for inserting and deleting. The rest N peers are used for searching. That is, we first insert N peers (from 1 to N), then lookup for next N peers (N+1 to 2N) and then delete N peers (from 1 to N). We note each individual time.<br /> 7. The simulation has been implemented in Java and the experiments have been performed on a 2GHz and 2GB RAM machine.<br /> <br /> ISP Friendly Algorithm<br /> Steps:<br /> 1. We populate IP to AS Map (IPASMap) using the IP Range and AS mapping present in AT &amp; T dataset. This map can be used for searching an AS for a given IP.<br /> <br /> 2. We then load the pre-computed shortest policy path matrix (ShortestPathMatrix) which contains the shortest distance between every 2 individual ASes.<br /> <br /> 3. The data structure we use is a HashMap (ASMap) which contains ASNum as the key and the peerlist (the list of peers in that AS) corresponding to that AS.<br /> <br /> i. <br /> Insert(Peer peer){<br /> //obtain the AS this peer belongs to<br /> ASNum = IPASMap.getASNum(peer.IP);<br /> <br /> // check if this AS already exists<br /> If (ASNum does not exist in ASMap)<br /> ASMap.insert(ASNum);<br /> <br /> // now add this peer to that AS<br /> ASMap[ASNum].peerlist.add(peer);<br /> <br /> } <br /> <br /> <br /> ii.<br /> Delete(Peer peer){<br /> //obtain the AS this peer belongs to<br /> ASNum = IPASMap.getASNum(peer.IP);<br /> <br /> //remove the peer from that AS<br /> ASMap[ASNum].peerlist.remove(peer);<br /> <br /> }<br /> <br /> iii.<br /> Lookup(Peer peer){<br /> declare RetPeerlist;<br /> declare retPeerCount;<br /> <br /> //obtain the AS this peer belongs to<br /> ASNum = IPASMap.getASNum(peer.IP);<br /> <br /> // Get a list of all ASes that are in the data structure<br /> ASlist = ASMap.getASList();<br /> <br /> // and sort these ASes based on the distance from ASNum<br /> // to each of the ASes in ASlist, using the matrix<br /> SortedASlist = ASlist.sort(ASNum , ShortestPathMatrix[][]);<br /> <br /> count = 0;<br /> <br /> // Noting the number of AS hops<br /> ashops = 0;<br /> <br /> for(i=0;i&lt;SortedASlist.size;i++){<br /> j=0;<br /> while(count&lt;retPeerCount &amp;&amp; j&lt;SortedASlist[i].peerlist.size){<br /> Peer tmp = SortedASlist[i].peerlist[j++];<br /> RetPeerlist.add(tmp);<br /> <br /> // get the AS this peer belongs to<br /> tmpASNum = SortedASlist[i];<br /> ashops += ShortestPathMatrix[ASNum][tmpASNum];<br /> count++;<br /> }<br /> if(count&gt;=retPeerCount)<br /> break;<br /> }<br /> return RetPeerlist;<br /> }<br /> <br /> <br /> <br /> <br /> == Ideas ==<br /> <br /> * Verification of AS Shortest Paths<br /> <br /> * Experimental Setup<br /> ** # Peers: {100, 300, 500, 1000, 3000, 5000, 8000}<br /> ** # Senders: {2, 5, 10, 15, 20}<br /> ** # Sessions: 1000<br /> ** Algos: Random, Network, Geo, AS_Order(ISP-Friendly)<br /> ** Metrics: Min, Avg, Max, Output<br /> ** Output: Hops (Aggregate, P2P, C2P)<br /> <br /> * Search Efficiency:<br /> ** If multiple shortest paths are existing, choose the least &quot;cost&quot; (s2s=0, p2p=1, c2p=2)<br /> <br /> * Check practicality<br /> ** What kind of data we need initially and periodically<br /> ** How often we need them<br /> ** We implement the algorithm to determine AS relationships<br /> <br /> * Large graphs<br /> ** Can we get the US &amp; CA graph?<br /> ** Can we optimize this matrix.<br /> <br /> * Usage of ISP + Network / Geolocation Algorithms<br /> ** We reduce the number of IP hops<br /> <br /> * Diameter of the graph<br /> <br /> == References and Links ==<br /> <br /> * IP to ASNum Mapping project from Team CYRMU<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26<br /> * CAIDA's Inter-AS relationships<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt<br /> * On AS-level Path Inference<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf<br /> * AT &amp; T IP-Range and ASNum mapping<br /> ** a. http://www.research.att.com/~jiawang/as_traceroute/</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=Private:pCDN:Peer_Matching&diff=1927 2008-04-25T20:17:48Z

<p>Nitin.chiluka: </p> <hr /> <div><br /> <br /> == Proposed Algorithm ==<br /> <br /> <br /> <br /> == Ideas ==<br /> <br /> * Verification of AS Shortest Paths<br /> <br /> * Experimental Setup<br /> ** # Peers: {100, 300, 500, 1000, 3000, 5000, 8000}<br /> ** # Senders: {2, 5, 10, 15, 20}<br /> ** # Sessions: 1000<br /> ** Algos: Random, Network, Geo, AS_Order(ISP-Friendly)<br /> ** Metrics: Min, Avg, Max, Output<br /> ** Output: Hops (Aggregate, P2P, C2P)<br /> <br /> * Search Efficiency:<br /> ** If multiple shortest paths are existing, choose the least &quot;cost&quot; (s2s=0, p2p=1, c2p=2)<br /> <br /> * Check practicality<br /> ** What kind of data we need initially and periodically<br /> ** How often we need them<br /> ** We implement the algorithm to determine AS relationships<br /> <br /> * Large graphs<br /> ** Can we get the US &amp; CA graph?<br /> ** Can we optimize this matrix.<br /> <br /> * Usage of ISP + Network / Geolocation Algorithms<br /> ** We reduce the number of IP hops<br /> <br /> * Diameter of the graph<br /> <br /> == References and Links ==<br /> <br /> * IP to ASNum Mapping project from Team CYRMU<br /> ** http://www.team-cymru.org/?sec=8&amp;opt=26<br /> * CAIDA's Inter-AS relationships<br /> ** http://as-rank.caida.org/data/2008/as-rel.20080414.a0.01000.txt<br /> * On AS-level Path Inference<br /> ** http://www.eecs.umich.edu/~zmao/Papers/routescope.pdf<br /> * AT &amp; T IP-Range and ASNum mapping<br /> ** a. http://www.research.att.com/~jiawang/as_traceroute/</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=Private:pCDN:Peer_Matching&diff=1926 2008-04-25T20:13:00Z

<p>Nitin.chiluka: </p> <hr /> <div>some intro <br /> <br /> == Proposed Algorithm ==<br /> <br /> <br /> <br /> == Ideas ==<br /> <br /> * Verification of AS Shortest Paths<br /> <br /> * Experimental Setup<br /> ** # Peers: {100, 300, 500, 1000, 3000, 5000, 8000}<br /> ** # Senders: {2, 5, 10, 15, 20}<br /> ** # Sessions: 1000<br /> ** Algos: Random, Network, Geo, AS_Order(ISP-Friendly)<br /> ** Metrics: Min, Avg, Max, Output<br /> ** Output: Hops (Aggregate, P2P, C2P)<br /> <br /> * Search Efficiency:<br /> ** If multiple shortest paths are existing, choose the least &quot;cost&quot; (s2s=0, p2p=1, c2p=2)<br /> <br /> * Check practicality<br /> ** What kind of data we need initially and periodically<br /> ** How often we need them<br /> ** We implement the algorithm to determine AS relationships<br /> <br /> * Large graphs<br /> ** Can we get the US &amp; CA graph?<br /> ** Can we optimize this matrix.<br /> <br /> * Usage of ISP + Network / Geolocation Algorithms<br /> ** We reduce the number of IP hops<br /> <br /> * Diameter of the graph<br /> <br /> == References and Links ==<br /> <br /> * links to various resources</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Faq&diff=1665 2008-03-11T19:03:48Z

<p>Nitin.chiluka: </p> <hr /> <div>= Frequently Asked Questions for Users =<br /> <br /> * '''Q:''' Does Sun Java 1.5.09 work with the pCDN client?<br /> ** '''A:''' No, Java runtime 1.6 is required by the pCDN client.<br /> <br /> = Frequently Asked Questions for Developers =<br /> <br /> * '''Q:''' What is the CBC's Intranet topology?<br /> ** '''A:''' The internal CBC network may contain public (but not allocated to CBC (1.0.0.0/8) addresses and private addresses, but there is no NAT between them. The server is presently on a 1.0.0.0/8 address and there is no firewall between it and the rest of the users inside CBC. The server is connected to a central router/switch where all the other subnets in the same city connect. Intercity links interconnect those router/switches in all other locations. Addresses are allocated in blocks to different cities. Here is Montreal we have 1.176.0.0/16 and in Toronto they have 1.151.0.0/16 and it goes on like this. I would have to check be I believe you can assume that if two addresses are in the same /16, that they are in the same building and or same city with high speed links.<br /> <br /> <br /> = Frequently Asked Questions for Administrators =<br /> * '''Q:''' How to import new content into the database?<br /> ** '''A:''' <br /> *** Step 1: Open Admin application by going to Start &gt; All Programs &gt; pCDN Server &gt; pCDN Admin. Press &quot;Connect&quot; button in the Login screen that is shown. <br /> *** Step 2: &quot;Server Manager&quot; window is opened, if authenticated. Click on Manage on the menubar and choose Content Manager &gt; New Policy. <br /> *** Step 3: Enter a group-name and if desired to impose restrictions on content access, configure the settings (Subnet, Geo-location and time period) for this group. Then press &quot;Save&quot; to save the group's parameters into the database. <br /> *** Step 4: From menubar, go to Manage &gt; Content Manager &gt; Open. Go to &quot;Import Content&quot; tab. Select the desired group from the combobox and enter a feed URL along with the output feed filename. Press &quot;Import and Convert&quot; to import all the files in this feed file into the database. To import non-feed URL into the database, enter a non-feed URL in the corresponding section and press &quot;Import&quot; button. You can see the list of files that are imported in the &quot;Media Files&quot; tab. Also, for every new group that is created, it can be seen in &quot;Groups&quot; tab.<br /> <br /> * '''Q:''' How to update/delete groups?<br /> ** '''A:''' <br /> *** Update a group: Go to Groups tab and double click the desired group whose policies you would like to update. It opens up a Policy window and make respective changes and press &quot;Save&quot; to save the new settings for that group or by pressing &quot;Cancel&quot;, your changes are not committed and hence the group's policies remain the same as before.<br /> *** Delete a group: Go to Groups tab and select a desired group and press DEL key to delete the record. Note that this deletes all the files that belong to this group. You can see corresponding changes both in Media Files tab's table as well as Groups tab's table.<br /> <br /> * '''Q:''' How to update/delete a file?<br /> ** '''A:''' <br /> *** Update a file: A file can be moved from one group to another, by selecting corresponding row in Media Files tab and from the third column's combobox, selecting the target group to which this file is desired to be moved.<br /> *** Delete a file: Select the desired file and press DEL key to delete the file.</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Faq&diff=1664 2008-03-11T19:02:08Z

<p>Nitin.chiluka: </p> <hr /> <div>= Frequently Asked Questions for Users =<br /> <br /> * '''Q:''' Does Sun Java 1.5.09 work with the pCDN client?<br /> ** '''A:''' No, Java runtime 1.6 is required by the pCDN client.<br /> <br /> = Frequently Asked Questions for Developers =<br /> <br /> * '''Q:''' What is the CBC's Intranet topology?<br /> ** '''A:''' The internal CBC network may contain public (but not allocated to CBC (1.0.0.0/8) addresses and private addresses, but there is no NAT between them. The server is presently on a 1.0.0.0/8 address and there is no firewall between it and the rest of the users inside CBC. The server is connected to a central router/switch where all the other subnets in the same city connect. Intercity links interconnect those router/switches in all other locations. Addresses are allocated in blocks to different cities. Here is Montreal we have 1.176.0.0/16 and in Toronto they have 1.151.0.0/16 and it goes on like this. I would have to check be I believe you can assume that if two addresses are in the same /16, that they are in the same building and or same city with high speed links.<br /> <br /> <br /> = Frequently Asked Questions for Administrators =<br /> * '''Q:''' How to import new content into the database?<br /> ** '''A:''' <br /> *** Step 1: Open Admin application by going to Start &gt; All Programs &gt; pCDN Server &gt; pCDN Admin. Press &quot;Connect&quot; button in the Login screen that is shown. <br /> *** Step 2: &quot;Server Manager&quot; window is opened, if authenticated. Click on Manage on the menubar and choose Content Manager &gt; New Policy. <br /> *** Step 3: Enter a group-name and if desired to impose restrictions on content access, configure the settings (Subnet, Geo-location and time period) for this group. Then press &quot;Save&quot; to save the group's parameters into the database. <br /> *** Step 4: From menubar, go to Manage &gt; Content Manager &gt; Open. Go to &quot;Import Content&quot; tab. Select the desired group from the combobox and enter a feed URL along with the output feed filename. Press &quot;Import and Convert&quot; to import all the files in this feed file into the database. To import non-feed URL into the database, enter a non-feed URL in the corresponding section and press &quot;Import&quot; button. You can see the list of files that are imported in the &quot;Media Files&quot; tab. Also, for every new group that is created, it can be seen in &quot;Groups&quot; tab.<br /> <br /> * '''Q:''' How to update/delete groups?<br /> ** '''A:''' <br /> *** Update a group: Go to Groups tab and double click the desired group whose policies you would like to update. It opens up a Policy window and make respective changes and press &quot;Save&quot; to save the new settings for that group or by pressing &quot;Cancel&quot;, your changes are not committed and hence the group's policies remain the same as before.<br /> *** Delete a group: Go to Groups tab and select a desired group and press DEL key to delete the record. Note that this deletes all the files that belong to this group. You can see corresponding changes both in Media Files tab's table as well as Groups tab's table.<br /> <br /> * '''Q:''' How to update/delete a file?<br /> ** '''A:''' <br /> *** '''Update a file:''' A file can be moved from one group to another, by selecting corresponding row in Media Files tab and from the third column's combobox, selecting the target group to which this file is desired to be moved.<br /> *** '''Delete a file:''' Select the desired file and press DEL key to delete the file.</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Faq&diff=1663 2008-03-11T19:01:53Z

<p>Nitin.chiluka: </p> <hr /> <div>= Frequently Asked Questions for Users =<br /> <br /> * '''Q:''' Does Sun Java 1.5.09 work with the pCDN client?<br /> ** '''A:''' No, Java runtime 1.6 is required by the pCDN client.<br /> <br /> = Frequently Asked Questions for Developers =<br /> <br /> * '''Q:''' What is the CBC's Intranet topology?<br /> ** '''A:''' The internal CBC network may contain public (but not allocated to CBC (1.0.0.0/8) addresses and private addresses, but there is no NAT between them. The server is presently on a 1.0.0.0/8 address and there is no firewall between it and the rest of the users inside CBC. The server is connected to a central router/switch where all the other subnets in the same city connect. Intercity links interconnect those router/switches in all other locations. Addresses are allocated in blocks to different cities. Here is Montreal we have 1.176.0.0/16 and in Toronto they have 1.151.0.0/16 and it goes on like this. I would have to check be I believe you can assume that if two addresses are in the same /16, that they are in the same building and or same city with high speed links.<br /> <br /> <br /> = Frequently Asked Questions for Administrators =<br /> * '''Q:''' How to import new content into the database?<br /> ** '''A:''' <br /> *** Step 1: Open Admin application by going to Start &gt; All Programs &gt; pCDN Server &gt; pCDN Admin. Press &quot;Connect&quot; button in the Login screen that is shown. <br /> *** Step 2: &quot;Server Manager&quot; window is opened, if authenticated. Click on Manage on the menubar and choose Content Manager &gt; New Policy. <br /> *** Step 3: Enter a group-name and if desired to impose restrictions on content access, configure the settings (Subnet, Geo-location and time period) for this group. Then press &quot;Save&quot; to save the group's parameters into the database. <br /> *** Step 4: From menubar, go to Manage &gt; Content Manager &gt; Open. Go to &quot;Import Content&quot; tab. Select the desired group from the combobox and enter a feed URL along with the output feed filename. Press &quot;Import and Convert&quot; to import all the files in this feed file into the database. To import non-feed URL into the database, enter a non-feed URL in the corresponding section and press &quot;Import&quot; button. You can see the list of files that are imported in the &quot;Media Files&quot; tab. Also, for every new group that is created, it can be seen in &quot;Groups&quot; tab.<br /> <br /> * '''Q:''' How to update/delete groups?<br /> ** '''A:''' <br /> *** Update a group: Go to Groups tab and double click the desired group whose policies you would like to update. It opens up a Policy window and make respective changes and press &quot;Save&quot; to save the new settings for that group or by pressing &quot;Cancel&quot;, your changes are not committed and hence the group's policies remain the same as before.<br /> *** Delete a group: Go to Groups tab and select a desired group and press DEL key to delete the record. Note that this deletes all the files that belong to this group. You can see corresponding changes both in Media Files tab's table as well as Groups tab's table.<br /> <br /> <br /> * '''Q:''' How to update/delete a file?<br /> ** '''A:''' <br /> *** '''Update a file:''' A file can be moved from one group to another, by selecting corresponding row in Media Files tab and from the third column's combobox, selecting the target group to which this file is desired to be moved.<br /> *** '''Delete a file:''' Select the desired file and press DEL key to delete the file.</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Faq&diff=1662 2008-03-11T18:50:26Z

<p>Nitin.chiluka: </p> <hr /> <div>= Frequently Asked Questions for Users =<br /> <br /> * '''Q:''' Does Sun Java 1.5.09 work with the pCDN client?<br /> ** '''A:''' No, Java runtime 1.6 is required by the pCDN client.<br /> <br /> = Frequently Asked Questions for Developers =<br /> <br /> * '''Q:''' What is the CBC's Intranet topology?<br /> ** '''A:''' The internal CBC network may contain public (but not allocated to CBC (1.0.0.0/8) addresses and private addresses, but there is no NAT between them. The server is presently on a 1.0.0.0/8 address and there is no firewall between it and the rest of the users inside CBC. The server is connected to a central router/switch where all the other subnets in the same city connect. Intercity links interconnect those router/switches in all other locations. Addresses are allocated in blocks to different cities. Here is Montreal we have 1.176.0.0/16 and in Toronto they have 1.151.0.0/16 and it goes on like this. I would have to check be I believe you can assume that if two addresses are in the same /16, that they are in the same building and or same city with high speed links.<br /> <br /> <br /> = Frequently Asked Questions for Administrators =<br /> * &quot;&quot;Q:&quot;&quot; How to import new content into the database?<br /> ** &quot;&quot;A:&quot;&quot; <br /> *** Step 1: Open Admin application by going to Start &gt; All Programs &gt; pCDN Server &gt; pCDN Admin. Press &quot;Connect&quot; button in the Login screen that is shown. <br /> *** Step 2: &quot;Server Manager&quot; window is opened, if authenticated. Click on Manage on the menubar and choose Content Manager &gt; New Policy. <br /> *** Step 3: Enter a group-name and if desired to impose restrictions on content access, configure the settings (Subnet, Geo-location and time period) for this group. Then press &quot;Save&quot; to save the group's parameters into the database. <br /> *** Step 4: From menubar, go to Manage &gt; Content Manager &gt; Open. Go to &quot;Import Content&quot; tab. Select the desired group from the combobox and enter a feed URL along with the output feed filename. Press &quot;Import and Convert&quot; to import all the files in this feed file into the database. To import non-feed URL into the database, enter a non-feed URL in the corresponding section and press &quot;Import&quot; button. You can see the list of files that are imported in the &quot;Media Files&quot; tab. Also, for every new group that is created, it can be seen in &quot;Groups&quot; tab.<br /> <br /> * &quot;&quot;Q:&quot;&quot; How to update/delete groups?<br /> ** &quot;&quot;A:&quot;&quot; <br /> *** Update a group: Go to Groups tab and double click the desired group whose policies you would like to update. It opens up a Policy window and make respective changes and press &quot;Save&quot; to save the new settings for that group or by pressing &quot;Cancel&quot;, your changes are not committed and hence the group's policies remain the same as before.<br /> *** Delete a group: Go to Groups tab and select a desired group and press DEL key to delete the record. Note that this deletes all the files that belong to this group. You can see corresponding changes both in Media Files tab's table as well as Groups tab's table.</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Faq&diff=1661 2008-03-11T18:41:05Z

<p>Nitin.chiluka: </p> <hr /> <div>= Frequently Asked Questions for Users =<br /> <br /> * '''Q:''' Does Sun Java 1.5.09 work with the pCDN client?<br /> ** '''A:''' No, Java runtime 1.6 is required by the pCDN client.<br /> <br /> = Frequently Asked Questions for Developers =<br /> <br /> * '''Q:''' What is the CBC's Intranet topology?<br /> ** '''A:''' The internal CBC network may contain public (but not allocated to CBC (1.0.0.0/8) addresses and private addresses, but there is no NAT between them. The server is presently on a 1.0.0.0/8 address and there is no firewall between it and the rest of the users inside CBC. The server is connected to a central router/switch where all the other subnets in the same city connect. Intercity links interconnect those router/switches in all other locations. Addresses are allocated in blocks to different cities. Here is Montreal we have 1.176.0.0/16 and in Toronto they have 1.151.0.0/16 and it goes on like this. I would have to check be I believe you can assume that if two addresses are in the same /16, that they are in the same building and or same city with high speed links.<br /> <br /> <br /> = Frequently Asked Questions for Administrators =<br /> * &quot;&quot;Q:&quot;&quot; How to import new content into the database?<br /> ** &quot;&quot;A:&quot;&quot; <br /> *** Step 1: Open Admin application by going to Start &gt; All Programs &gt; pCDN Server &gt; pCDN Admin. Press &quot;Connect&quot; button in the Login screen that is shown. <br /> *** Step 2: &quot;Server Manager&quot; window is opened, if authenticated. Click on Manage on the menubar and choose Content Manager &gt; New Policy. <br /> *** Step 3: Enter a group-name and if desired to impose restrictions on content access, configure the settings (Subnet, Geo-location and time period) for this group. Then press &quot;Save&quot; to save the group's parameters into the database. <br /> *** Step 4: From menubar, go to Manage &gt; Content Manager &gt; Open. Go to &quot;Import Content&quot; tab. Select the desired group from the combobox and enter a feed URL along with the output feed filename. Press &quot;Import and Convert&quot; to import all the files in this feed file into the database. To import non-feed URL into the database, enter a non-feed URL in the corresponding section and press &quot;Import&quot; button. You can see the list of files that are imported in the &quot;Media Files&quot; tab. Also, for every new group that is created, it can be seen in &quot;Groups&quot; tab.</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Faq&diff=1660 2008-03-11T18:40:00Z

<p>Nitin.chiluka: </p> <hr /> <div>= Frequently Asked Questions for Users =<br /> <br /> * '''Q:''' Does Sun Java 1.5.09 work with the pCDN client?<br /> ** '''A:''' No, Java runtime 1.6 is required by the pCDN client.<br /> <br /> = Frequently Asked Questions for Developers =<br /> <br /> * '''Q:''' What is the CBC's Intranet topology?<br /> ** '''A:''' The internal CBC network may contain public (but not allocated to CBC (1.0.0.0/8) addresses and private addresses, but there is no NAT between them. The server is presently on a 1.0.0.0/8 address and there is no firewall between it and the rest of the users inside CBC. The server is connected to a central router/switch where all the other subnets in the same city connect. Intercity links interconnect those router/switches in all other locations. Addresses are allocated in blocks to different cities. Here is Montreal we have 1.176.0.0/16 and in Toronto they have 1.151.0.0/16 and it goes on like this. I would have to check be I believe you can assume that if two addresses are in the same /16, that they are in the same building and or same city with high speed links.<br /> <br /> <br /> = Frequently Asked Questions for Administrators =<br /> * &quot;&quot;Q:&quot;&quot; How to import new content into the database?<br /> ** &quot;&quot;A:&quot;&quot; <br /> *** Step 1: Open Admin application by going to Start &gt; All Programs &gt; pCDN Server &gt; pCDN Admin. Press &quot;Connect&quot; button in the Login screen that is shown. <br /> *** Step 2: &quot;Server Manager&quot; window is opened, if authenticated. Click on Manage on the menubar and choose Content Manager &gt; New Policy. <br /> *** Step 3: Enter a group-name and if desired to impose restrictions on content access, configure the settings (Subnet, Geo-location and time period) for this group. Then press &quot;Save&quot; to save the group's parameters into the database. <br /> *** Step 4: From menubar, go to Manage &gt; Content Manager &gt; Open. Go to &quot;Import Content&quot; tab. Select the desired group from the combobox and enter a feed URL along with the output feed filename. Press &quot;Import and Convert&quot; to import all the files in this feed file into the database. To import non-feed URL into the database, enter a non-feed URL in the corresponding section and press &quot;Import&quot; button. You can see the list of files that are imported in the &quot;Media Files&quot; tab.</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Faq&diff=1659 2008-03-11T18:39:29Z

<p>Nitin.chiluka: </p> <hr /> <div>= Frequently Asked Questions for Users =<br /> <br /> * '''Q:''' Does Sun Java 1.5.09 work with the pCDN client?<br /> ** '''A:''' No, Java runtime 1.6 is required by the pCDN client.<br /> <br /> = Frequently Asked Questions for Developers =<br /> <br /> * '''Q:''' What is the CBC's Intranet topology?<br /> ** '''A:''' The internal CBC network may contain public (but not allocated to CBC (1.0.0.0/8) addresses and private addresses, but there is no NAT between them. The server is presently on a 1.0.0.0/8 address and there is no firewall between it and the rest of the users inside CBC. The server is connected to a central router/switch where all the other subnets in the same city connect. Intercity links interconnect those router/switches in all other locations. Addresses are allocated in blocks to different cities. Here is Montreal we have 1.176.0.0/16 and in Toronto they have 1.151.0.0/16 and it goes on like this. I would have to check be I believe you can assume that if two addresses are in the same /16, that they are in the same building and or same city with high speed links.<br /> <br /> <br /> = Frequently Asked Questions for Administrators =<br /> * &quot;&quot;Q:&quot;&quot; How to import new content into the database?<br /> ** &quot;&quot;A:&quot;&quot; <br /> Step 1: Open Admin application by going to Start &gt; All Programs &gt; pCDN Server &gt; pCDN Admin. Press &quot;Connect&quot; button in the Login screen that is shown. <br /> Step 2: &quot;Server Manager&quot; window is opened, if authenticated. Click on Manage on the menubar and choose Content Manager &gt; New Policy. <br /> Step 3: Enter a group-name and if desired to impose restrictions on content access, configure the settings (Subnet, Geo-location and time period) for this group. Then press &quot;Save&quot; to save the group's parameters into the database. <br /> Step 4: From menubar, go to Manage &gt; Content Manager &gt; Open. Go to &quot;Import Content&quot; tab. Select the desired group from the combobox and enter a feed URL along with the output feed filename. Press &quot;Import and Convert&quot; to import all the files in this feed file into the database. To import non-feed URL into the database, enter a non-feed URL in the corresponding section and press &quot;Import&quot; button. You can see the list of files that are imported in the &quot;Media Files&quot; tab.</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Faq&diff=1658 2008-03-11T18:37:26Z

<p>Nitin.chiluka: </p> <hr /> <div>= Frequently Asked Questions for Users =<br /> <br /> * '''Q:''' Does Sun Java 1.5.09 work with the pCDN client?<br /> ** '''A:''' No, Java runtime 1.6 is required by the pCDN client.<br /> <br /> = Frequently Asked Questions for Developers =<br /> <br /> * '''Q:''' What is the CBC's Intranet topology?<br /> ** '''A:''' The internal CBC network may contain public (but not allocated to CBC (1.0.0.0/8) addresses and private addresses, but there is no NAT between them. The server is presently on a 1.0.0.0/8 address and there is no firewall between it and the rest of the users inside CBC. The server is connected to a central router/switch where all the other subnets in the same city connect. Intercity links interconnect those router/switches in all other locations. Addresses are allocated in blocks to different cities. Here is Montreal we have 1.176.0.0/16 and in Toronto they have 1.151.0.0/16 and it goes on like this. I would have to check be I believe you can assume that if two addresses are in the same /16, that they are in the same building and or same city with high speed links.<br /> <br /> <br /> = Frequently Asked Questions for Administrators =<br /> * &quot;&quot;Q:&quot;&quot; How to import new content into the database?<br /> ** &quot;&quot;A:&quot;&quot; Open Admin application by going to Start &gt; All Programs &gt; pCDN Server &gt; pCDN Admin. Press &quot;Connect&quot; button in the Login screen that is shown. It opens &quot;Server Manager&quot; window. Click on Manage on the menubar and choose Content Manager &gt; New Policy. Enter a group-name and if desired to impose restrictions on content access, configure the settings (Subnet, Geo-location and time period) for this group. Then press &quot;Save&quot; to save the group's parameters into the database. Then, go to Manage &gt; Content Manager &gt; Open. Go to &quot;Import Content&quot; tab. Select the desired group and enter a feed URL along with the output feed filename. Press &quot;Import and Convert&quot; to import all the files in this feed file into the database. To import non-feed URL into the database, enter a non-feed URL in the corresponding section and press &quot;Import&quot; button. You can see the list of files that are imported in the &quot;Media Files&quot; tab.</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Testplan&diff=1578 2008-03-04T20:55:31Z

<p>Nitin.chiluka: </p> <hr /> <div>== Client ==<br /> # Download several new podcasts from the web servers (make sure the media/ directory contains no media files before this test). <br /> # Download new podcasts from several pCDN senders.<br /> # Download podcasts that were downloaded before (and still in media/ directory).<br /> # Reduce the harddisk quota using user interface to 50 MB, and download several podcasts.<br /> # Reduce the memory quota to 4 MB, and download several podacsts.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from one of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cables from all of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from the receiver. <br /> # Manually truncate the media files in media/ directory, and download that file from the podcast client.<br /> # Manually truncate the media files in media/ directory, and request that file from another pCDN client.<br /> # Download several new podcasts using a pCDN client behind a NAT box. Check whether the IP/port are correctly reported at the pCDN server. Also try to use this pCDN client as the sender.<br /> # Download several new podcasts using a pCDN client on a machine with multiple IPs. Use user-interface to select an outgoing IP. Then, change the NICs' IP addresses, and see whether the pCDN client continues work after reboots.<br /> <br /> <br /> == Server ==<br /> Note: In case a tracker gets disconnected, re-connection suffices (e.g., re-plugging the cable if the cable was unplugged). There is no need to re-start the tracker.<br /> <br /> # When trackers are up and connected to each other:<br /> #*peers download files from each other as expected.<br /> # Have a peer download podcasts, and then bring the current primary tracker down (or unplug its network cable):<br /> #*No problem. The peer communicates with the next tracker after a few seconds.<br /> #(i) Have a peer join the network when some trackers are down, or (ii) After the peer joined the network (primary tracker is T1 for example), bring T1 down and have the peer request some files:<br /> #*No problem. Peer connects to the next tracker to join/request.<br /> #Re-plug the network cable of a tracker that was the primary and has been disconnected from the network since we unplugged its cable:<br /> #*The trackers gets working properly, becomes primary, and receives the most recent database file from the tracker who was the primary during the absence (cable-unplugged) period.<br /> #A tracker T1, who is prior to T2 for being the primary, has been down/disconnected and is just started/re-connected. When a peer (who is now connected to T2) requests to download a file:<br /> #*T2 leads the peer to T1 and the peer immediately connects to T1 to ask where to download the file from.<br /> #Have a peer P1 download a file F1, wait until the backuping moment (when the primary tracker T1 pushes his recent database to others), and bring the primary tracker down after that:<br /> #*Tracker T2 becomes the primary and P2 downloads file F1 from peer P1 (not from the web server).<br /> #Tracker T1 was the primary, but is down/disconnected now and tracker T2 is the current primary. Peer P1 downloads file F1. T1 comes back and becomes the primary, so T2 immediately pushes the most recent database to T1. Then, peer P2 requests to download F1:<br /> #*P2 download F1 from P1.<br /> #When a peer is connected to the network and suddenly all trackers get dead, or when the internet connection of the peer is cut:<br /> #*The peer keeps re-trying to connect. When some tracker came up, or when the peer was re-connected to the Internet, the connects to a tracker.<br /> <br /> <br /> == Admin Tools ==<br /> === Server Statistics === <br /> # When a peer joins the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' increase by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The country the peer belongs to is inserted into the left table if the country is not already there in the left table. When that country is clicked, all the peers that belong to that country along with city and region details are shown in the right table. Also, note that the number of peers respective to the country also increment<br /> #* Content tab: If that peer has files, these files are inserted into the left table (if these are not already there) and the peer info is added to the corresponding file. When one clicks on a particular file, all those peers containing that file are shown in the right table.<br /> # When a peer leaves the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' decrease by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The peer is deleted from the respective country's right table and if the corresponding country has no peers, the country will be deleted from the left table. Also, note that the number of peers respective to the country also decrement.<br /> #* Content tab: This particular peer's record is coloured grey in the right table for every file (present in the left table) it contains.<br /> # When a peer downloads a file, 'Content' tab is updated by inserting file info in the left table if it is not already there and then to the corresponding file's right table, this peer info is added.<br /> # When backup file is transferred to the tracker (that we are currently connected to) and restored, the entire 'content' tab and 'connected peers' tab info is cleared and populated with the latest one. <br /> <br /> === Geo-Fencing ===<br /> # Groups Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected group is deleted and also all the files corresponding to the group from both 'media' table and 'groups' table (which contains the pair fileid-groupid). Also, note that this selected row is deleted from the table in the UI and also all the files corresponding to the group are deleted from the 'Media Files' tab's table. In addition, the combo box corresponding to 'groupname' in 'Content Importer' tab, is updated respectively, i.e., the deleted group is not present in the combo box list.<br /> #* Select a row and double-click it. Check that it opens up a Policy Window in which the group's policy is displayed in respective fields correctly. After editing, when 'Save' button is pressed, the corresponding group info is updated in the database and also is reflected in the 'Groups Tab'. We must also be able see the difference being reflected in the combo box of the 'Content Importer' tab and also the 'Media Files' tab, especially in the case of name of group being altered.<br /> # Media Files Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected file is deleted from the 'media' table and also groups table, the pair groupid-fileid is to be deleted. Also, the file is removed from the table in the UI.<br /> #* Select a row and change the group of a particular file by selecting any other group from the combo box in the third column of the table. That particular change should not only be reflected in the UI but also the database must be updated with the newer group. Check the 'groups' database table to see if groupid corresponding the fileid has changed to the newer one. <br /> # New Policy:<br /> #* Fill all respective fields in the Policy Window and press &quot;Save&quot; Button. Check if the database's Policy table is filled with a new entry that has just been inserted. Also, note that the group is inserted in &quot;Groups&quot; Tab. In addition, the combo box in the 'Content Importer' tab is also updated with the new entry. The combo box in the third column of 'Media Files' tab's table is also updated.<br /> <br /> === Content Importer ===<br /> # Select a group from the combo box and enter a feed URL and output feed filename and press &quot;Import and Convert&quot; button. <br /> #* Success: A dialog pops up saying that these files are imported into the database. Check in the database's 'Media' table that these files are imported and also 'Groups' table being populated with the corresponding fileid and groupid information. Also, these files are inserted into the 'Media Files' tab's table pointing to respective group. Check the output file is created with http://localhost being inserted for every URL within that feed file.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Select a group from the combo box and enter a non-feed URL and press &quot;Import&quot;.<br /> #* Success: A dialog pops up saying that these files are imported into the database along with output URL. Check in the database's 'Media' table that this file is imported and also 'Groups' table being populated with the corresponding fileid and groupid information.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Try pressing &quot;Import and Convert&quot; button with atleast any one of the Feed-URL fields unfilled/empty, a dialog box is shown with a message that both the fields are to be filled.<br /> # Try pressing &quot;Import&quot; button with non-feed URL field unfilled/empty, a dialog box is shown with a message that the field is to be filled.<br /> <br /> === User Administration ===<br /> # Add a new user and check if it is inserted into the 'users' table in database and also in the table shown in the UI.<br /> # Change the privilege level of a user using the combo box in the table and check if it is reflected in the database.<br /> # Select a row in the table and press DEL key. The row must get deleted from the database and also the table.<br /> <br /> <br /> == Known Issues ==<br /> # Server: the keep-alive interval must not be smaller than the time it takes to transmit the database file from one tracker to another. For example, wil a value of &quot;1 minute&quot; for that interval, if the size of the database file gets in orders of some hundred megabytes or some gigabytes (i.e., some millions of users), that interval must be increased to &quot;10 minutes&quot; or so.<br /> # Client: The ''preferences'' frame silently rejects settings that are out of supported ranges. For example, max memory usage below 4 MB will be rejected without giving any warning. Due to the limitation of Java class and display space, we plan to address this in the new GUI design.<br /> # Client: When a receiver loses its Internet connection, the pCDN client does not return a proper error code to podcast clients, such as iTunes. Instead, we wait until iTunes times out.<br /> # Server: Server would crash (XXX need to validate this), if the RDBMS goes off-line.<br /> # Monitor: If a group / file is added / edited / deleted using one application, it is not updated on all the other running monitoring applications.<br /> <br /> <br /> *The following are also posted to Bugzilla (can be removed from here, but not suggested):<br /> <br /> #Client: When we stop downloading a file in iTunes, the pCDN client still continues downloading.<br /> #*A user might have stopped the download in order to save his bandwidth for some other applications, but the pCDN client prevents that saving.<br /> #Server: Each tracker has a file settings.ini, which must be the same for all trackers. Having this file in a centralized manner, such as on a file server, may be helpful, because modification of that file on some tracker may cause improper functioning of the entire system. <br /> #The directory containing media files a peer has stored gets larger and larger by time. There should be a mechanism to delete unnecessary ones. [Cheng 08/03/01, There is a max disk usage setting in client GUI, which will remove the least recently received files. Note that, however, the recency is not persistent, so the received time of each files got lost after rebooting pCDN clients.]</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Testplan&diff=1577 2008-03-04T20:54:15Z

<p>Nitin.chiluka: </p> <hr /> <div>== Client ==<br /> # Download several new podcasts from the web servers (make sure the media/ directory contains no media files before this test). <br /> # Download new podcasts from several pCDN senders.<br /> # Download podcasts that were downloaded before (and still in media/ directory).<br /> # Reduce the harddisk quota using user interface to 50 MB, and download several podcasts.<br /> # Reduce the memory quota to 4 MB, and download several podacsts.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from one of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cables from all of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from the receiver. <br /> # Manually truncate the media files in media/ directory, and download that file from the podcast client.<br /> # Manually truncate the media files in media/ directory, and request that file from another pCDN client.<br /> # Download several new podcasts using a pCDN client behind a NAT box. Check whether the IP/port are correctly reported at the pCDN server. Also try to use this pCDN client as the sender.<br /> # Download several new podcasts using a pCDN client on a machine with multiple IPs. Use user-interface to select an outgoing IP. Then, change the NICs' IP addresses, and see whether the pCDN client continues work after reboots.<br /> <br /> <br /> == Server ==<br /> Note: In case a tracker gets disconnected, re-connection suffices (e.g., re-plugging the cable if the cable was unplugged). There is no need to re-start the tracker.<br /> <br /> # When trackers are up and connected to each other:<br /> #*peers download files from each other as expected.<br /> # Have a peer download podcasts, and then bring the current primary tracker down (or unplug its network cable):<br /> #*No problem. The peer communicates with the next tracker after a few seconds.<br /> #(i) Have a peer join the network when some trackers are down, or (ii) After the peer joined the network (primary tracker is T1 for example), bring T1 down and have the peer request some files:<br /> #*No problem. Peer connects to the next tracker to join/request.<br /> #Re-plug the network cable of a tracker that was the primary and has been disconnected from the network since we unplugged its cable:<br /> #*The trackers gets working properly, becomes primary, and receives the most recent database file from the tracker who was the primary during the absence (cable-unplugged) period.<br /> #A tracker T1, who is prior to T2 for being the primary, has been down/disconnected and is just started/re-connected. When a peer (who is now connected to T2) requests to download a file:<br /> #*T2 leads the peer to T1 and the peer immediately connects to T1 to ask where to download the file from.<br /> #Have a peer P1 download a file F1, wait until the backuping moment (when the primary tracker T1 pushes his recent database to others), and bring the primary tracker down after that:<br /> #*Tracker T2 becomes the primary and P2 downloads file F1 from peer P1 (not from the web server).<br /> #Tracker T1 was the primary, but is down/disconnected now and tracker T2 is the current primary. Peer P1 downloads file F1. T1 comes back and becomes the primary, so T2 immediately pushes the most recent database to T1. Then, peer P2 requests to download F1:<br /> #*P2 download F1 from P1.<br /> #When a peer is connected to the network and suddenly all trackers get dead, or when the internet connection of the peer is cut:<br /> #*The peer keeps re-trying to connect. When some tracker came up, or when the peer was re-connected to the Internet, the connects to a tracker.<br /> <br /> <br /> == Admin Tools ==<br /> === Server Statistics === <br /> # When a peer joins the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' increase by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The country the peer belongs to is inserted into the left table if the country is not already there in the left table. When that country is clicked, all the peers that belong to that country along with city and region details are shown in the right table. Also, note that the number of peers respective to the country also increment<br /> #* Content tab: If that peer has files, these files are inserted into the left table (if these are not already there) and the peer info is added to the corresponding file. When one clicks on a particular file, all those peers containing that file are shown in the right table.<br /> # When a peer leaves the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' decrease by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The peer is deleted from the respective country's right table and if the corresponding country has no peers, the country will be deleted from the left table. Also, note that the number of peers respective to the country also decrement.<br /> #* Content tab: This particular peer's record is coloured grey in the right table for every file (present in the left table) it contains.<br /> # When a peer downloads a file, 'Content' tab is updated by inserting file info in the left table if it is not already there and then to the corresponding file's right table, this peer info is added.<br /> # When backup file is transferred to the tracker (that we are currently connected to) and restored, the entire 'content' tab and 'connected peers' tab info is cleared and populated with the latest one. <br /> <br /> === Geo-Fencing ===<br /> # Groups Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected group is deleted and also all the files corresponding to the group from both 'media' table and 'groups' table (which contains the pair fileid-groupid). Also, note that this selected row is deleted from the table in the UI and also all the files corresponding to the group are deleted from the 'Media Files' tab's table. In addition, the combo box corresponding to 'groupname' in 'Content Importer' tab, is updated respectively, i.e., the deleted group is not present in the combo box list.<br /> #* Select a row and double-click it. Check that it opens up a Policy Window in which the group's policy is displayed in respective fields correctly. After editing, when 'Save' button is pressed, the corresponding group info is updated in the database and also is reflected in the 'Groups Tab'. We must also be able see the difference being reflected in the combo box of the 'Content Importer' tab and also the 'Media Files' tab, especially in the case of name of group being altered.<br /> # Media Files Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected file is deleted from the 'media' table and also groups table, the pair groupid-fileid is to be deleted. Also, the file is removed from the table in the UI.<br /> #* Select a row and change the group of a particular file by selecting any other group from the combo box in the third column of the table. That particular change should not only be reflected in the UI but also the database must be updated with the newer group. Check the 'groups' database table to see if groupid corresponding the fileid has changed to the newer one. <br /> # New Policy:<br /> #* Fill all respective fields in the Policy Window and press &quot;Save&quot; Button. Check if the database's Policy table is filled with a new entry that has just been inserted. Also, note that the group is inserted in &quot;Groups&quot; Tab. In addition, the combo box in the 'Content Importer' tab is also updated with the new entry. The combo box in the third column of 'Media Files' tab's table is also updated.<br /> <br /> === Content Importer ===<br /> # Select a group from the combo box and enter a feed URL and output feed filename and press &quot;Import and Convert&quot; button. <br /> #* Success: A dialog pops up saying that these files are imported into the database. Check in the database's 'Media' table that these files are imported and also 'Groups' table being populated with the corresponding fileid and groupid information. Also, these files are inserted into the 'Media Files' tab's table pointing to respective group. Check the output file is created with http://localhost being inserted for every URL within that feed file.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Select a group from the combo box and enter a non-feed URL and press &quot;Import&quot;.<br /> #* Success: A dialog pops up saying that these files are imported into the database along with output URL. Check in the database's 'Media' table that this file is imported and also 'Groups' table being populated with the corresponding fileid and groupid information.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Try pressing &quot;Import and Convert&quot; button with atleast any one of the Feed-URL fields unfilled/empty, a dialog box is shown with a message that both the fields are to be filled.<br /> # Try pressing &quot;Import&quot; button with non-feed URL field unfilled/empty, a dialog box is shown with a message that the field is to be filled.<br /> <br /> === User Administration ===<br /> # Add a new user and check if it is inserted into the 'users' table in database and also in the table shown in the UI.<br /> # Change the privilege level of a user using the combo box in the table and check if it is reflected in the database.<br /> # Select a row in the table and press DEL key. The row must get deleted from the database and also the table.<br /> <br /> <br /> == Known Issues ==<br /> # Server: the keep-alive interval must not be smaller than the time it takes to transmit the database file from one tracker to another. For example, wil a value of &quot;1 minute&quot; for that interval, if the size of the database file gets in orders of some hundred megabytes or some gigabytes (i.e., some millions of users), that interval must be increased to &quot;10 minutes&quot; or so.<br /> # Client: The ''preferences'' frame silently rejects settings that are out of supported ranges. For example, max memory usage below 4 MB will be rejected without giving any warning. Due to the limitation of Java class and display space, we plan to address this in the new GUI design.<br /> # Client: When a receiver loses its Internet connection, the pCDN client does not return a proper error code to podcast clients, such as iTunes. Instead, we wait until iTunes times out.<br /> # Server: Server would crash (XXX need to validate this), if the RDBMS goes off-line.<br /> # Monitor: If a group / file is added / edited / deleted using Content Manager, it is not updated on all the other running monitoring applications.<br /> <br /> <br /> *The following are also posted to Bugzilla (can be removed from here, but not suggested):<br /> <br /> #Client: When we stop downloading a file in iTunes, the pCDN client still continues downloading.<br /> #*A user might have stopped the download in order to save his bandwidth for some other applications, but the pCDN client prevents that saving.<br /> #Server: Each tracker has a file settings.ini, which must be the same for all trackers. Having this file in a centralized manner, such as on a file server, may be helpful, because modification of that file on some tracker may cause improper functioning of the entire system. <br /> #The directory containing media files a peer has stored gets larger and larger by time. There should be a mechanism to delete unnecessary ones. [Cheng 08/03/01, There is a max disk usage setting in client GUI, which will remove the least recently received files. Note that, however, the recency is not persistent, so the received time of each files got lost after rebooting pCDN clients.]</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Testplan&diff=1575 2008-03-04T20:52:58Z

<p>Nitin.chiluka: </p> <hr /> <div>== Client ==<br /> # Download several new podcasts from the web servers (make sure the media/ directory contains no media files before this test). <br /> # Download new podcasts from several pCDN senders.<br /> # Download podcasts that were downloaded before (and still in media/ directory).<br /> # Reduce the harddisk quota using user interface to 50 MB, and download several podcasts.<br /> # Reduce the memory quota to 4 MB, and download several podacsts.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from one of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cables from all of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from the receiver. <br /> # Manually truncate the media files in media/ directory, and download that file from the podcast client.<br /> # Manually truncate the media files in media/ directory, and request that file from another pCDN client.<br /> # Download several new podcasts using a pCDN client behind a NAT box. Check whether the IP/port are correctly reported at the pCDN server. Also try to use this pCDN client as the sender.<br /> # Download several new podcasts using a pCDN client on a machine with multiple IPs. Use user-interface to select an outgoing IP. Then, change the NICs' IP addresses, and see whether the pCDN client continues work after reboots.<br /> <br /> <br /> == Server ==<br /> Note: In case a tracker gets disconnected, re-connection suffices (e.g., re-plugging the cable if the cable was unplugged). There is no need to re-start the tracker.<br /> <br /> # When trackers are up and connected to each other:<br /> #*peers download files from each other as expected.<br /> # Have a peer download podcasts, and then bring the current primary tracker down (or unplug its network cable):<br /> #*No problem. The peer communicates with the next tracker after a few seconds.<br /> #(i) Have a peer join the network when some trackers are down, or (ii) After the peer joined the network (primary tracker is T1 for example), bring T1 down and have the peer request some files:<br /> #*No problem. Peer connects to the next tracker to join/request.<br /> #Re-plug the network cable of a tracker that was the primary and has been disconnected from the network since we unplugged its cable:<br /> #*The trackers gets working properly, becomes primary, and receives the most recent database file from the tracker who was the primary during the absence (cable-unplugged) period.<br /> #A tracker T1, who is prior to T2 for being the primary, has been down/disconnected and is just started/re-connected. When a peer (who is now connected to T2) requests to download a file:<br /> #*T2 leads the peer to T1 and the peer immediately connects to T1 to ask where to download the file from.<br /> #Have a peer P1 download a file F1, wait until the backuping moment (when the primary tracker T1 pushes his recent database to others), and bring the primary tracker down after that:<br /> #*Tracker T2 becomes the primary and P2 downloads file F1 from peer P1 (not from the web server).<br /> #Tracker T1 was the primary, but is down/disconnected now and tracker T2 is the current primary. Peer P1 downloads file F1. T1 comes back and becomes the primary, so T2 immediately pushes the most recent database to T1. Then, peer P2 requests to download F1:<br /> #*P2 download F1 from P1.<br /> #When a peer is connected to the network and suddenly all trackers get dead, or when the internet connection of the peer is cut:<br /> #*The peer keeps re-trying to connect. When some tracker came up, or when the peer was re-connected to the Internet, the connects to a tracker.<br /> <br /> <br /> == Admin Tools ==<br /> === Server Statistics === <br /> # When a peer joins the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' increase by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The country the peer belongs to is inserted into the left table if the country is not already there in the left table. When that country is clicked, all the peers that belong to that country along with city and region details are shown in the right table. Also, note that the number of peers respective to the country also increment<br /> #* Content tab: If that peer has files, these files are inserted into the left table (if these are not already there) and the peer info is added to the corresponding file. When one clicks on a particular file, all those peers containing that file are shown in the right table.<br /> # When a peer leaves the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' decrease by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The peer is deleted from the respective country's right table and if the corresponding country has no peers, the country will be deleted from the left table. Also, note that the number of peers respective to the country also decrement.<br /> #* Content tab: This particular peer's record is coloured grey in the right table for every file (present in the left table) it contains.<br /> # When a peer downloads a file, 'Content' tab is updated by inserting file info in the left table if it is not already there and then to the corresponding file's right table, this peer info is added.<br /> # When backup file is transferred to the tracker (that we are currently connected to) and restored, the entire 'content' tab and 'connected peers' tab info is cleared and populated with the latest one. <br /> <br /> === Geo-Fencing ===<br /> # Groups Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected group is deleted and also all the files corresponding to the group from both 'media' table and 'groups' table (which contains the pair fileid-groupid). Also, note that this selected row is deleted from the table in the UI and also all the files corresponding to the group are deleted from the 'Media Files' tab's table. In addition, the combo box corresponding to 'groupname' in 'Content Importer' tab, is updated respectively, i.e., the deleted group is not present in the combo box list.<br /> #* Select a row and double-click it. Check that it opens up a Policy Window in which the group's policy is displayed in respective fields correctly. After editing, when 'Save' button is pressed, the corresponding group info is updated in the database and also is reflected in the 'Groups Tab'. We must also be able see the difference being reflected in the combo box of the 'Content Importer' tab and also the 'Media Files' tab, especially in the case of name of group being altered.<br /> # Media Files Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected file is deleted from the 'media' table and also groups table, the pair groupid-fileid is to be deleted. Also, the file is removed from the table in the UI.<br /> #* Select a row and change the group of a particular file by selecting any other group from the combo box in the third column of the table. That particular change should not only be reflected in the UI but also the database must be updated with the newer group. Check the 'groups' database table to see if groupid corresponding the fileid has changed to the newer one. <br /> # New Policy:<br /> #* Fill all respective fields in the Policy Window and press &quot;Save&quot; Button. Check if the database's Policy table is filled with a new entry that has just been inserted. Also, note that the group is inserted in &quot;Groups&quot; Tab. In addition, the combo box in the 'Content Importer' tab is also updated with the new entry. The combo box in the third column of 'Media Files' tab's table is also updated.<br /> <br /> === Content Importer ===<br /> # Select a group from the combo box and enter a feed URL and output feed filename and press &quot;Import and Convert&quot; button. <br /> #* Success: A dialog pops up saying that these files are imported into the database. Check in the database's 'Media' table that these files are imported and also 'Groups' table being populated with the corresponding fileid and groupid information. Also, these files are inserted into the 'Media Files' tab's table pointing to respective group. Check the output file is created with http://localhost being inserted for every URL within that feed file.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Select a group from the combo box and enter a non-feed URL and press &quot;Import&quot;.<br /> #* Success: A dialog pops up saying that these files are imported into the database along with output URL. Check in the database's 'Media' table that this file is imported and also 'Groups' table being populated with the corresponding fileid and groupid information.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Try pressing &quot;Import and Convert&quot; button with atleast any one of the Feed-URL fields unfilled/empty, a dialog box is shown with a message that both the fields are to be filled.<br /> # Try pressing &quot;Import&quot; button with non-feed URL field unfilled/empty, a dialog box is shown with a message that the field is to be filled.<br /> <br /> === User Administration ===<br /> # Add a new user and check if it is inserted into the database and also in the table shown below.<br /> # Change the privilege level of a user using the combo box in the table and check if it is reflected in the database.<br /> # Select a row in the table and press DEL key. The row must get deleted from the database and also the table.<br /> <br /> <br /> == Known Issues ==<br /> # Server: the keep-alive interval must not be smaller than the time it takes to transmit the database file from one tracker to another. For example, wil a value of &quot;1 minute&quot; for that interval, if the size of the database file gets in orders of some hundred megabytes or some gigabytes (i.e., some millions of users), that interval must be increased to &quot;10 minutes&quot; or so.<br /> # Client: The ''preferences'' frame silently rejects settings that are out of supported ranges. For example, max memory usage below 4 MB will be rejected without giving any warning. Due to the limitation of Java class and display space, we plan to address this in the new GUI design.<br /> # Client: When a receiver loses its Internet connection, the pCDN client does not return a proper error code to podcast clients, such as iTunes. Instead, we wait until iTunes times out.<br /> # Server: Server would crash (XXX need to validate this), if the RDBMS goes off-line.<br /> # Monitor: If a group / file is added / edited / deleted using Content Manager, it is not updated on all the other running monitoring applications.<br /> <br /> <br /> *The following are also posted to Bugzilla (can be removed from here, but not suggested):<br /> <br /> #Client: When we stop downloading a file in iTunes, the pCDN client still continues downloading.<br /> #*A user might have stopped the download in order to save his bandwidth for some other applications, but the pCDN client prevents that saving.<br /> #Server: Each tracker has a file settings.ini, which must be the same for all trackers. Having this file in a centralized manner, such as on a file server, may be helpful, because modification of that file on some tracker may cause improper functioning of the entire system. <br /> #The directory containing media files a peer has stored gets larger and larger by time. There should be a mechanism to delete unnecessary ones. [Cheng 08/03/01, There is a max disk usage setting in client GUI, which will remove the least recently received files. Note that, however, the recency is not persistent, so the received time of each files got lost after rebooting pCDN clients.]</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Testplan&diff=1573 2008-03-04T20:37:26Z

<p>Nitin.chiluka: </p> <hr /> <div>== Client ==<br /> # Download several new podcasts from the web servers (make sure the media/ directory contains no media files before this test). <br /> # Download new podcasts from several pCDN senders.<br /> # Download podcasts that were downloaded before (and still in media/ directory).<br /> # Reduce the harddisk quota using user interface to 50 MB, and download several podcasts.<br /> # Reduce the memory quota to 4 MB, and download several podacsts.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from one of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cables from all of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from the receiver. <br /> # Manually truncate the media files in media/ directory, and download that file from the podcast client.<br /> # Manually truncate the media files in media/ directory, and request that file from another pCDN client.<br /> # Download several new podcasts using a pCDN client behind a NAT box. Check whether the IP/port are correctly reported at the pCDN server. Also try to use this pCDN client as the sender.<br /> # Download several new podcasts using a pCDN client on a machine with multiple IPs. Use user-interface to select an outgoing IP. Then, change the NICs' IP addresses, and see whether the pCDN client continues work after reboots.<br /> <br /> <br /> == Server ==<br /> Note: In case a tracker gets disconnected, re-connection suffices (e.g., re-plugging the cable if the cable was unplugged). There is no need to re-start the tracker.<br /> <br /> # When trackers are up and connected to each other:<br /> #*peers download files from each other as expected.<br /> # Have a peer download podcasts, and then bring the current primary tracker down (or unplug its network cable):<br /> #*No problem. The peer communicates with the next tracker after a few seconds.<br /> #(i) Have a peer join the network when some trackers are down, or (ii) After the peer joined the network (primary tracker is T1 for example), bring T1 down and have the peer request some files:<br /> #*No problem. Peer connects to the next tracker to join/request.<br /> #Re-plug the network cable of a tracker that was the primary and has been disconnected from the network since we unplugged its cable:<br /> #*The trackers gets working properly, becomes primary, and receives the most recent database file from the tracker who was the primary during the absence (cable-unplugged) period.<br /> #A tracker T1, who is prior to T2 for being the primary, has been down/disconnected and is just started/re-connected. When a peer (who is now connected to T2) requests to download a file:<br /> #*T2 leads the peer to T1 and the peer immediately connects to T1 to ask where to download the file from.<br /> #Have a peer P1 download a file F1, wait until the backuping moment (when the primary tracker T1 pushes his recent database to others), and bring the primary tracker down after that:<br /> #*Tracker T2 becomes the primary and P2 downloads file F1 from peer P1 (not from the web server).<br /> #Tracker T1 was the primary, but is down/disconnected now and tracker T2 is the current primary. Peer P1 downloads file F1. T1 comes back and becomes the primary, so T2 immediately pushes the most recent database to T1. Then, peer P2 requests to download F1:<br /> #*If T1 was brought down by Ctrl+C and is started again now: P2 download F1 from P1.<br /> #*If T1 was disconnected by unplugging its network cable: when P2 now requests the file, the balloon “Sorry, you are not permitted to download the file” is shown (XXX).<br /> #When a peer is connected to the network and suddenly all trackers get dead:<br /> #*The peer keeps re-trying to connect. Thus when some tracker came up, the peer connects to it.<br /> #Run trackers T1 and T2, where T1 is the primary, and a peer is connected to the network. Stop T1, so T2 becomes the primary, and the peers connects to T2 after a short time. Start T1 again. Now, for a few seconds T2 still thinks he is the primary. Immediately unplug T2’s cable.<br /> #*T1 knows himself as the primary and the peer downloads files through T1.<br /> #*T2 after some seconds knows that he is the primary. The peer is able to download files through T2.<br /> <br /> <br /> == Admin Tools ==<br /> === Server Statistics === <br /> # When a peer joins the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' increase by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The country the peer belongs to is inserted into the left table if the country is not already there in the left table. When that country is clicked, all the peers that belong to that country along with city and region details are shown in the right table. Also, note that the number of peers respective to the country also increment<br /> #* Content tab: If that peer has files, these files are inserted into the left table (if these are not already there) and the peer info is added to the corresponding file. When one clicks on a particular file, all those peers containing that file are shown in the right table.<br /> # When a peer leaves the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' decrease by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The peer is deleted from the respective country's right table and if the corresponding country has no peers, the country will be deleted from the left table. Also, note that the number of peers respective to the country also decrement.<br /> #* Content tab: This particular peer's record is coloured grey in the right table for every file (present in the left table) it contains.<br /> # When a peer downloads a file, 'Content' tab is updated by inserting file info in the left table if it is not already there and then to the corresponding file's right table, this peer info is added.<br /> # When backup file is transferred to the tracker (that we are currently connected to) and restored, the entire 'content' tab and 'connected peers' tab info is cleared and populated with the latest one. <br /> <br /> <br /> === Geo-Fencing ===<br /> # Groups Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected group is deleted and also all the files corresponding to the group from both 'media' table and 'groups' table (which contains the pair fileid-groupid). Also, note that this selected row is deleted from the table in the UI and also all the files corresponding to the group are deleted from the 'Media Files' tab's table. In addition, the combo box corresponding to 'groupname' in 'Content Importer' tab, is updated respectively, i.e., the deleted group is not present in the combo box list.<br /> #* Select a row and double-click it. Check that it opens up a Policy Window in which the group's policy is displayed in respective fields correctly. After editing, when 'Save' button is pressed, the corresponding group info is updated in the database and also is reflected in the 'Groups Tab'. We must also be able see the difference being reflected in the combo box of the 'Content Importer' tab and also the 'Media Files' tab, especially in the case of name of group being altered.<br /> # Media Files Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected file is deleted from the 'media' table and also groups table, the pair groupid-fileid is to be deleted. Also, the file is removed from the table in the UI.<br /> #* Select a row and change the group of a particular file by selecting any other group from the combo box in the third column of the table. That particular change should not only be reflected in the UI but also the database must be updated with the newer group. Check the 'groups' database table to see if groupid corresponding the fileid has changed to the newer one. <br /> # New Policy:<br /> #* Fill all respective fields in the Policy Window and press &quot;Save&quot; Button. Check if the database's Policy table is filled with a new entry that has just been inserted. Also, note that the group is inserted in &quot;Groups&quot; Tab. In addition, the combo box in the 'Content Importer' tab is also updated with the new entry. The combo box in the third column of 'Media Files' tab's table is also updated.<br /> <br /> <br /> === Content Importer ===<br /> # Select a group from the combo box and enter a feed URL and output feed filename and press &quot;Import and Convert&quot; button. <br /> #* Success: A dialog pops up saying that these files are imported into the database. Check in the database's 'Media' table that these files are imported and also 'Groups' table being populated with the corresponding fileid and groupid information. Also, these files are inserted into the 'Media Files' tab's table pointing to respective group. Check the output file is created with http://localhost being inserted for every URL within that feed file.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Select a group from the combo box and enter a non-feed URL and press &quot;Import&quot;.<br /> #* Success: A dialog pops up saying that these files are imported into the database along with output URL. Check in the database's 'Media' table that this file is imported and also 'Groups' table being populated with the corresponding fileid and groupid information.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Try pressing &quot;Import and Convert&quot; button with atleast any one of the Feed-URL fields unfilled/empty, a dialog box is shown with a message that both the fields are to be filled.<br /> # Try pressing &quot;Import&quot; button with non-feed URL field unfilled/empty, a dialog box is shown with a message that the field is to be filled.<br /> <br /> <br /> === User Administration ===<br /> # Add a new user and check if it is inserted into the database and also in the table shown below.<br /> # Change the privilege level of a user using the combo box in the table and check if it is reflected in the database.<br /> # Select a row in the table and press DEL key. The row must get deleted from the database and also the table.<br /> <br /> <br /> == Known Issues ==<br /> # Server: the keep-alive interval must not be smaller than the time it takes to transmit the database file from one tracker to another. For example, wil a value of &quot;1 minute&quot; for that interval, if the size of the database file gets in orders of some hundred megabytes or some gigabytes (i.e., some millions of users), that interval must be increased to &quot;10 minutes&quot; or so.<br /> # Client: The ''preferences'' frame silently rejects settings that are out of supported ranges. For example, max memory usage below 4 MB will be rejected without giving any warning. Due to the limitation of Java class and display space, we plan to address this in the new GUI design.<br /> # Client: When a receiver loses its Internet connection, the pCDN client does not return a proper error code to podcast clients, such as iTunes. Instead, we wait until iTunes times out.<br /> # Server: Server would crash (XXX need to validate this), if the RDBMS goes off-line.<br /> # Monitor: If a group / file is added / edited / deleted using Content Manager, it is not updated on all the other running monitoring applications.<br /> <br /> <br /> *The following are also posted to Bugzilla (can be removed from here, but not suggested):<br /> <br /> #Client: When we stop downloading a file in iTunes, the pCDN client still continues downloading.<br /> #*A user might have stopped the download in order to save his bandwidth for some other applications, but the pCDN client prevents that saving.<br /> #Server: Each tracker has a file settings.ini, which must be the same for all trackers. Having this file in a centralized manner, such as on a file server, may be helpful, because modification of that file on some tracker may cause improper functioning of the entire system. <br /> #The directory containing media files a peer has stored gets larger and larger by time. There should be a mechanism to delete unnecessary ones. [Cheng 08/03/01, There is a max disk usage setting in client GUI, which will remove the least recently received files. Note that, however, the recency is not persistent, so the received time of each files got lost after rebooting pCDN clients.]</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Testplan&diff=1572 2008-03-04T20:33:30Z

<p>Nitin.chiluka: </p> <hr /> <div>== Client ==<br /> # Download several new podcasts from the web servers (make sure the media/ directory contains no media files before this test). <br /> # Download new podcasts from several pCDN senders.<br /> # Download podcasts that were downloaded before (and still in media/ directory).<br /> # Reduce the harddisk quota using user interface to 50 MB, and download several podcasts.<br /> # Reduce the memory quota to 4 MB, and download several podacsts.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from one of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cables from all of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from the receiver. <br /> # Manually truncate the media files in media/ directory, and download that file from the podcast client.<br /> # Manually truncate the media files in media/ directory, and request that file from another pCDN client.<br /> # Download several new podcasts using a pCDN client behind a NAT box. Check whether the IP/port are correctly reported at the pCDN server. Also try to use this pCDN client as the sender.<br /> # Download several new podcasts using a pCDN client on a machine with multiple IPs. Use user-interface to select an outgoing IP. Then, change the NICs' IP addresses, and see whether the pCDN client continues work after reboots.<br /> <br /> <br /> == Server ==<br /> Note: In case a tracker gets disconnected, re-connection suffices (e.g., re-plugging the cable if the cable was unplugged). There is no need to re-start the tracker.<br /> <br /> # When trackers are up and connected to each other:<br /> #*peers download files from each other as expected.<br /> # Have a peer download podcasts, and then bring the current primary tracker down (or unplug its network cable):<br /> #*No problem. The peer communicates with the next tracker after a few seconds.<br /> #(i) Have a peer join the network when some trackers are down, or (ii) After the peer joined the network (primary tracker is T1 for example), bring T1 down and have the peer request some files:<br /> #*No problem. Peer connects to the next tracker to join/request.<br /> #Re-plug the network cable of a tracker that was the primary and has been disconnected from the network since we unplugged its cable:<br /> #*The trackers gets working properly, becomes primary, and receives the most recent database file from the tracker who was the primary during the absence (cable-unplugged) period.<br /> #A tracker T1, who is prior to T2 for being the primary, has been down/disconnected and is just started/re-connected. When a peer (who is now connected to T2) requests to download a file:<br /> #*T2 leads the peer to T1 and the peer immediately connects to T1 to ask where to download the file from.<br /> #Have a peer P1 download a file F1, wait until the backuping moment (when the primary tracker T1 pushes his recent database to others), and bring the primary tracker down after that:<br /> #*Tracker T2 becomes the primary and P2 downloads file F1 from peer P1 (not from the web server).<br /> #Tracker T1 was the primary, but is down/disconnected now and tracker T2 is the current primary. Peer P1 downloads file F1. T1 comes back and becomes the primary, so T2 immediately pushes the most recent database to T1. Then, peer P2 requests to download F1:<br /> #*If T1 was brought down by Ctrl+C and is started again now: P2 download F1 from P1.<br /> #*If T1 was disconnected by unplugging its network cable: when P2 now requests the file, the balloon “Sorry, you are not permitted to download the file” is shown (XXX).<br /> #When a peer is connected to the network and suddenly all trackers get dead:<br /> #*The peer keeps re-trying to connect. Thus when some tracker came up, the peer connects to it.<br /> #Run trackers T1 and T2, where T1 is the primary, and a peer is connected to the network. Stop T1, so T2 becomes the primary, and the peers connects to T2 after a short time. Start T1 again. Now, for a few seconds T2 still thinks he is the primary. Immediately unplug T2’s cable.<br /> #*T1 knows himself as the primary and the peer downloads files through T1.<br /> #*T2 after some seconds knows that he is the primary. The peer is able to download files through T2.<br /> <br /> <br /> == Admin Tools ==<br /> === Server Statistics === <br /> # When a peer joins the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' increase by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The country the peer belongs to is inserted into the left table if the country is not already there in the left table. When that country is clicked, all the peers that belong to that country along with city and region details are shown in the right table. Also, note that the number of peers respective to the country also increment<br /> #* Content tab: If that peer has files, these files are inserted into the left table (if these are not already there) and the peer info is added to the corresponding file. When one clicks on a particular file, all those peers containing that file are shown in the right table.<br /> # When a peer leaves the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' decrease by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The peer is deleted from the respective country's right table and if the corresponding country has no peers, the country will be deleted from the left table. Also, note that the number of peers respective to the country also decrement.<br /> #* Content tab: This particular peer's record is coloured grey in the right table for every file (present in the left table) it contains.<br /> # When a peer downloads a file, 'Content' tab is updated by inserting file info in the left table if it is not already there and then to the corresponding file's right table, this peer info is added.<br /> # When backup file is transferred to the tracker (that we are currently connected to) and restored, the entire 'content' tab and 'connected peers' tab info is cleared and populated with the latest one. <br /> <br /> <br /> === Geo-Fencing ===<br /> # Groups Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected group is deleted and also all the files corresponding to the group from both 'media' table and 'groups' table (which contains the pair fileid-groupid). Also, note that this selected row is deleted from the table in the UI and also all the files corresponding to the group are deleted from the 'Media Files' tab's table. In addition, the combo box corresponding to 'groupname' in 'Content Importer' tab, is updated respectively, i.e., the deleted group is not present in the combo box list.<br /> #* Select a row and double-click it. Check that it opens up a Policy Window in which the group's policy is displayed in respective fields correctly. After editing, when 'Save' button is pressed, the corresponding group info is updated in the database and also is reflected in the 'Groups Tab'. We must also be able see the difference being reflected in the combo box of the 'Content Importer' tab and also the 'Media Files' tab, especially in the case of name of group being altered.<br /> # Media Files Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected file is deleted from the 'media' table and also groups table, the pair groupid-fileid is to be deleted. Also, the file is removed from the table in the UI.<br /> #* Select a row and change the group of a particular file by selecting any other group from the combo box in the third column of the table. That particular change should not only be reflected in the UI but also the database must be updated with the newer group. Check the 'groups' database table to see if groupid corresponding the fileid has changed to the newer one. <br /> # New Policy:<br /> #* Fill all respective fields in the Policy Window and press &quot;Save&quot; Button. Check if the database's Policy table is filled with a new entry that has just been inserted. Also, note that the group is inserted in &quot;Groups&quot; Tab. In addition, the combo box in the 'Content Importer' tab is also updated with the new entry. The combo box in the third column of 'Media Files' tab's table is also updated.<br /> <br /> <br /> === Content Importer ===<br /> # Select a group from the combo box and enter a feed URL and output feed filename and press &quot;Import and Convert&quot; button. <br /> #* Success: A dialog pops up saying that these files are imported into the database. Check in the database's 'Media' table that these files are imported and also 'Groups' table being populated with the corresponding fileid and groupid information. Also, these files are inserted into the 'Media Files' tab's table pointing to respective group. Check the output file is created with http://localhost being inserted for every URL within that feed file.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Select a group from the combo box and enter a non-feed URL and press &quot;Import&quot;.<br /> #* Success: A dialog pops up saying that these files are imported into the database along with output URL. Check in the database's 'Media' table that this file is imported and also 'Groups' table being populated with the corresponding fileid and groupid information.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Try pressing &quot;Import and Convert&quot; button with atleast any one of the Feed-URL fields unfilled/empty, a dialog box is shown with a message that both the fields are to be filled.<br /> # Try pressing &quot;Import&quot; button with non-feed URL field unfilled/empty, a dialog box is shown with a message that the field is to be filled.<br /> <br /> <br /> === User Administration ===<br /> # Add a new user and check if it is inserted into the database and also in the table shown below.<br /> # Change the privilege level of a user using the combo box in the table and check if it is reflected in the database.<br /> # Select a row in the table and press DEL key. The row must get deleted from the database and also the table.<br /> <br /> <br /> == Known Issues ==<br /> # Server: the keep-alive interval must not be smaller than the time it takes to transmit the database file from one tracker to another. For example, wil a value of &quot;1 minute&quot; for that interval, if the size of the database file gets in orders of some hundred megabytes or some gigabytes (i.e., some millions of users), that interval must be increased to &quot;10 minutes&quot; or so.<br /> # Client: The ''preferences'' frame silently rejects settings that are out of supported ranges. For example, max memory usage below 4 MB will be rejected without giving any warning. Due to the limitation of Java class and display space, we plan to address this in the new GUI design.<br /> # Client: When a receiver loses its Internet connection, the pCDN client does not return a proper error code to podcast clients, such as iTunes. Instead, we wait until iTunes times out.<br /> # Server: Server would crash (XXX need to validate this), if the RDBMS goes off-line.<br /> <br /> <br /> *The following are also posted to Bugzilla (can be removed from here, but not suggested):<br /> <br /> #Client: When we stop downloading a file in iTunes, the pCDN client still continues downloading.<br /> #*A user might have stopped the download in order to save his bandwidth for some other applications, but the pCDN client prevents that saving.<br /> #Server: Each tracker has a file settings.ini, which must be the same for all trackers. Having this file in a centralized manner, such as on a file server, may be helpful, because modification of that file on some tracker may cause improper functioning of the entire system. <br /> #The directory containing media files a peer has stored gets larger and larger by time. There should be a mechanism to delete unnecessary ones. [Cheng 08/03/01, There is a max disk usage setting in client GUI, which will remove the least recently received files. Note that, however, the recency is not persistent, so the received time of each files got lost after rebooting pCDN clients.]</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Testplan&diff=1571 2008-03-04T20:17:46Z

<p>Nitin.chiluka: </p> <hr /> <div>== Client ==<br /> # Download several new podcasts from the web servers (make sure the media/ directory contains no media files before this test). <br /> # Download new podcasts from several pCDN senders.<br /> # Download podcasts that were downloaded before (and still in media/ directory).<br /> # Reduce the harddisk quota using user interface to 50 MB, and download several podcasts.<br /> # Reduce the memory quota to 4 MB, and download several podacsts.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from one of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cables from all of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from the receiver. <br /> # Manually truncate the media files in media/ directory, and download that file from the podcast client.<br /> # Manually truncate the media files in media/ directory, and request that file from another pCDN client.<br /> # Download several new podcasts using a pCDN client behind a NAT box. Check whether the IP/port are correctly reported at the pCDN server. Also try to use this pCDN client as the sender.<br /> # Download several new podcasts using a pCDN client on a machine with multiple IPs. Use user-interface to select an outgoing IP. Then, change the NICs' IP addresses, and see whether the pCDN client continues work after reboots.<br /> <br /> <br /> == Server ==<br /> Note: In case a tracker gets disconnected, re-connection suffices (e.g., re-plugging the cable if the cable was unplugged). There is no need to re-start the tracker.<br /> <br /> # When trackers are up and connected to each other:<br /> #*peers download files from each other as expected.<br /> # Have a peer download podcasts, and then bring the current primary tracker down (or unplug its network cable):<br /> #*No problem. The peer communicates with the next tracker after a few seconds.<br /> #(i) Have a peer join the network when some trackers are down, or (ii) After the peer joined the network (primary tracker is T1 for example), bring T1 down and have the peer request some files:<br /> #*No problem. Peer connects to the next tracker to join/request.<br /> #Re-plug the network cable of a tracker that was the primary and has been disconnected from the network since we unplugged its cable:<br /> #*The trackers gets working properly, becomes primary, and receives the most recent database file from the tracker who was the primary during the absence (cable-unplugged) period.<br /> #A tracker T1, who is prior to T2 for being the primary, has been down/disconnected and is just started/re-connected. When a peer (who is now connected to T2) requests to download a file:<br /> #*T2 leads the peer to T1 and the peer immediately connects to T1 to ask where to download the file from.<br /> #Have a peer P1 download a file F1, wait until the backuping moment (when the primary tracker T1 pushes his recent database to others), and bring the primary tracker down after that:<br /> #*Tracker T2 becomes the primary and P2 downloads file F1 from peer P1 (not from the web server).<br /> #Tracker T1 was the primary, but is down/disconnected now and tracker T2 is the current primary. Peer P1 downloads file F1. T1 comes back and becomes the primary, so T2 immediately pushes the most recent database to T1. Then, peer P2 requests to download F1:<br /> #*If T1 was brought down by Ctrl+C and is started again now: P2 download F1 from P1.<br /> #*If T1 was disconnected by unplugging its network cable: when P2 now requests the file, the balloon “Sorry, you are not permitted to download the file” is shown (XXX).<br /> #When a peer is connected to the network and suddenly all trackers get dead:<br /> #*The peer keeps re-trying to connect. Thus when some tracker came up, the peer connects to it.<br /> #Run trackers T1 and T2, where T1 is the primary, and a peer is connected to the network. Stop T1, so T2 becomes the primary, and the peers connects to T2 after a short time. Start T1 again. Now, for a few seconds T2 still thinks he is the primary. Immediately unplug T2’s cable.<br /> #*T1 knows himself as the primary and the peer downloads files through T1.<br /> #*T2 after some seconds knows that he is the primary. The peer is able to download files through T2.<br /> <br /> <br /> == Admin Tools ==<br /> === Server Statistics === <br /> # When a peer joins the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' increase by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The country the peer belongs to is inserted into the left table if the country is not already there in the left table. When that country is clicked, all the peers that belong to that country along with city and region details are shown in the right table. Also, note that the number of peers respective to the country also increment<br /> #* Content tab: If that peer has files, these files are inserted into the left table (if these are not already there) and the peer info is added to the corresponding file. When one clicks on a particular file, all those peers containing that file are shown in the right table.<br /> # When a peer leaves the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' decrease by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The peer is deleted from the respective country's right table and if the corresponding country has no peers, the country will be deleted from the left table. Also, note that the number of peers respective to the country also decrement.<br /> #* Content tab: This particular peer's record is coloured grey in the right table for every file (present in the left table) it contains.<br /> # When a peer downloads a file, 'Content' tab is updated by inserting file info in the left table if it is not already there and then to the corresponding file's right table, this peer info is added.<br /> # When backup file is transferred to the tracker (that we are currently connected to) and restored, the entire 'content' tab and 'connected peers' tab info is cleared and populated with the latest one. <br /> <br /> <br /> === Geo-Fencing ===<br /> # Groups Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected group is deleted and also all the files corresponding to the group from both 'media' table and 'groups' table (which contains the pair fileid-groupid). Also, note that this selected row is deleted from the table in the UI and also all the files corresponding to the group are deleted from the 'Media Files' tab's table. In addition, the combo box corresponding to 'groupname' in 'Content Importer' tab, is updated respectively, i.e., the deleted group is not present in the combo box list.<br /> #* Select a row and double-click it. Check that it opens up a Policy Window in which the group's policy is displayed in respective fields correctly. After editing, when 'Save' button is pressed, the corresponding group info is updated in the database and also is reflected in the 'Groups Tab'. We must also be able see the difference being reflected in the combo box of the 'Content Importer' tab and also the 'Media Files' tab, especially in the case of name of group being altered.<br /> # Media Files Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected file is deleted from the 'media' table and also groups table, the pair groupid-fileid is to be deleted. Also, the file is removed from the table in the UI.<br /> #* Select a row and change the group of a particular file by selecting any other group from the combo box in the third column of the table. That particular change should not only be reflected in the UI but also the database must be updated with the newer group. Check the 'groups' database table to see if groupid corresponding the fileid has changed to the newer one. <br /> <br /> <br /> === Content Importer ===<br /> # Select a group from the combo box and enter a feed URL and output feed filename and press &quot;Import and Convert&quot; button. <br /> #* Success: A dialog pops up saying that these files are imported into the database. Check in the database's 'Media' table that these files are imported and also 'Groups' table being populated with the corresponding fileid and groupid information. Also, these files are inserted into the 'Media Files' tab's table pointing to respective group. Check the output file is created with http://localhost being inserted for every URL within that feed file.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Select a group from the combo box and enter a non-feed URL and press &quot;Import&quot;.<br /> #* Success: A dialog pops up saying that these files are imported into the database along with output URL. Check in the database's 'Media' table that this file is imported and also 'Groups' table being populated with the corresponding fileid and groupid information.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Try pressing &quot;Import and Convert&quot; button with atleast any one of the Feed-URL fields unfilled/empty, a dialog box is shown with a message that both the fields are to be filled.<br /> # Try pressing &quot;Import&quot; button with non-feed URL field unfilled/empty, a dialog box is shown with a message that the field is to be filled.<br /> <br /> <br /> === User Administration ===<br /> # Add a new user and check if it is inserted into the database and also in the table shown below.<br /> # Change the privilege level of a user using the combo box in the table and check if it is reflected in the database.<br /> # Select a row in the table and press DEL key. The row must get deleted from the database and also the table.<br /> <br /> <br /> == Known Issues ==<br /> # Server: the keep-alive interval must not be smaller than the time it takes to transmit the database file from one tracker to another. For example, wil a value of &quot;1 minute&quot; for that interval, if the size of the database file gets in orders of some hundred megabytes or some gigabytes (i.e., some millions of users), that interval must be increased to &quot;10 minutes&quot; or so.<br /> # Client: The ''preferences'' frame silently rejects settings that are out of supported ranges. For example, max memory usage below 4 MB will be rejected without giving any warning. Due to the limitation of Java class and display space, we plan to address this in the new GUI design.<br /> # Client: When a receiver loses its Internet connection, the pCDN client does not return a proper error code to podcast clients, such as iTunes. Instead, we wait until iTunes times out.<br /> # Server: Server would crash (XXX need to validate this), if the RDBMS goes off-line.<br /> <br /> <br /> *The following are also posted to Bugzilla (can be removed from here, but not suggested):<br /> <br /> #Client: When we stop downloading a file in iTunes, the pCDN client still continues downloading.<br /> #*A user might have stopped the download in order to save his bandwidth for some other applications, but the pCDN client prevents that saving.<br /> #Server: Each tracker has a file settings.ini, which must be the same for all trackers. Having this file in a centralized manner, such as on a file server, may be helpful, because modification of that file on some tracker may cause improper functioning of the entire system. <br /> #The directory containing media files a peer has stored gets larger and larger by time. There should be a mechanism to delete unnecessary ones. [Cheng 08/03/01, There is a max disk usage setting in client GUI, which will remove the least recently received files. Note that, however, the recency is not persistent, so the received time of each files got lost after rebooting pCDN clients.]</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Testplan&diff=1570 2008-03-04T20:16:12Z

<p>Nitin.chiluka: </p> <hr /> <div>== Client ==<br /> # Download several new podcasts from the web servers (make sure the media/ directory contains no media files before this test). <br /> # Download new podcasts from several pCDN senders.<br /> # Download podcasts that were downloaded before (and still in media/ directory).<br /> # Reduce the harddisk quota using user interface to 50 MB, and download several podcasts.<br /> # Reduce the memory quota to 4 MB, and download several podacsts.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from one of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cables from all of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from the receiver. <br /> # Manually truncate the media files in media/ directory, and download that file from the podcast client.<br /> # Manually truncate the media files in media/ directory, and request that file from another pCDN client.<br /> # Download several new podcasts using a pCDN client behind a NAT box. Check whether the IP/port are correctly reported at the pCDN server. Also try to use this pCDN client as the sender.<br /> # Download several new podcasts using a pCDN client on a machine with multiple IPs. Use user-interface to select an outgoing IP. Then, change the NICs' IP addresses, and see whether the pCDN client continues work after reboots.<br /> <br /> <br /> == Server ==<br /> Note: In case a tracker gets disconnected, re-connection suffices (e.g., re-plugging the cable if the cable was unplugged). There is no need to re-start the tracker.<br /> <br /> # When trackers are up and connected to each other:<br /> #*peers download files from each other as expected.<br /> # Have a peer download podcasts, and then bring the current primary tracker down (or unplug its network cable):<br /> #*No problem. The peer communicates with the next tracker after a few seconds.<br /> #(i) Have a peer join the network when some trackers are down, or (ii) After the peer joined the network (primary tracker is T1 for example), bring T1 down and have the peer request some files:<br /> #*No problem. Peer connects to the next tracker to join/request.<br /> #Re-plug the network cable of a tracker that was the primary and has been disconnected from the network since we unplugged its cable:<br /> #*The trackers gets working properly, becomes primary, and receives the most recent database file from the tracker who was the primary during the absence (cable-unplugged) period.<br /> #A tracker T1, who is prior to T2 for being the primary, has been down/disconnected and is just started/re-connected. When a peer (who is now connected to T2) requests to download a file:<br /> #*T2 leads the peer to T1 and the peer immediately connects to T1 to ask where to download the file from.<br /> #Have a peer P1 download a file F1, wait until the backuping moment (when the primary tracker T1 pushes his recent database to others), and bring the primary tracker down after that:<br /> #*Tracker T2 becomes the primary and P2 downloads file F1 from peer P1 (not from the web server).<br /> #Tracker T1 was the primary, but is down/disconnected now and tracker T2 is the current primary. Peer P1 downloads file F1. T1 comes back and becomes the primary, so T2 immediately pushes the most recent database to T1. Then, peer P2 requests to download F1:<br /> #*If T1 was brought down by Ctrl+C and is started again now: P2 download F1 from P1.<br /> #*If T1 was disconnected by unplugging its network cable: when P2 now requests the file, the balloon “Sorry, you are not permitted to download the file” is shown (XXX).<br /> #When a peer is connected to the network and suddenly all trackers get dead:<br /> #*The peer keeps re-trying to connect. Thus when some tracker came up, the peer connects to it.<br /> #Run trackers T1 and T2, where T1 is the primary, and a peer is connected to the network. Stop T1, so T2 becomes the primary, and the peers connects to T2 after a short time. Start T1 again. Now, for a few seconds T2 still thinks he is the primary. Immediately unplug T2’s cable.<br /> #*T1 knows himself as the primary and the peer downloads files through T1.<br /> #*T2 after some seconds knows that he is the primary. The peer is able to download files through T2.<br /> <br /> <br /> == Admin Tools ==<br /> === Server Statistics === <br /> # When a peer joins the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' increase by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The country the peer belongs to is inserted into the left table if the country is not already there in the left table. When that country is clicked, all the peers that belong to that country along with city and region details are shown in the right table. Also, note that the number of peers respective to the country also increment<br /> #* Content tab: If that peer has files, these files are inserted into the left table (if these are not already there) and the peer info is added to the corresponding file. When one clicks on a particular file, all those peers containing that file are shown in the right table.<br /> # When a peer leaves the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' decrease by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The peer is deleted from the respective country's right table and if the corresponding country has no peers, the country will be deleted from the left table. Also, note that the number of peers respective to the country also decrement.<br /> #* Content tab: This particular peer's record is coloured grey in the right table for every file (present in the left table) it contains.<br /> # When a peer downloads a file, 'Content' tab is updated by inserting file info in the left table if it is not already there and then to the corresponding file's right table, this peer info is added.<br /> # When backup file is transferred to the tracker (that we are currently connected to) and restored, the entire 'content' tab and 'connected peers' tab info is cleared and populated with the latest one. <br /> <br /> <br /> === Geo-Fencing ===<br /> # Groups Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected group is deleted and also all the files corresponding to the group from both 'media' table and 'groups' table (which contains the pair fileid-groupid). Also, note that this selected row is deleted from the table in the UI and also all the files corresponding to the group are deleted from the 'Media Files' tab's table. In addition, the combo box corresponding to 'groupname' in 'Content Importer' tab, is updated respectively, i.e., the deleted group is not present in the combo box list.<br /> #* Select a row and double-click it. Check that it opens up a Policy Window in which the group's policy is displayed in respective fields correctly. After editing, when 'Save' button is pressed, the corresponding group info is updated in the database and also is reflected in the 'Groups Tab'. We must also be able see the difference being reflected in the combo box of the 'Content Importer' tab and also the 'Media Files' tab, especially in the case of name of group being altered.<br /> # Media Files Tab:<br /> #* Select a row and press DEL key. Check from the database that the selected file is deleted from the 'media' table and also groups table, the pair groupid-fileid is to be deleted. Also, the file is removed from the table in the UI.<br /> #* Select a row and change the group of a particular file by selecting any other group from the combo box in the third column of the table. That particular change should not only be reflected in the UI but also the database must be updated with the newer group. Check the 'groups' database table to see if groupid corresponding the fileid has changed to the newer one. <br /> <br /> === Content Importer ===<br /> # Select a group from the combo box and enter a feed URL and output feed filename and press &quot;Import and Convert&quot; button. <br /> #* Success: A dialog pops up saying that these files are imported into the database. Check in the database's 'Media' table that these files are imported and also 'Groups' table being populated with the corresponding fileid and groupid information. Also, these files are inserted into the 'Media Files' tab's table pointing to respective group. Check the output file is created with http://localhost being inserted for every URL within that feed file.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Select a group from the combo box and enter a non-feed URL and press &quot;Import&quot;.<br /> #* Success: A dialog pops up saying that these files are imported into the database along with output URL. Check in the database's 'Media' table that this file is imported and also 'Groups' table being populated with the corresponding fileid and groupid information.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Try pressing &quot;Import and Convert&quot; button with atleast any one of the Feed-URL fields unfilled/empty, a dialog box is shown with a message that both the fields are to be filled.<br /> # Try pressing &quot;Import&quot; button with non-feed URL field unfilled/empty, a dialog box is shown with a message that the field is to be filled.<br /> <br /> === User Administration ===<br /> # Add a new user and check if it is inserted into the database and also in the table shown below.<br /> # Change the privilege level of a user using the combo box in the table and check if it is reflected in the database.<br /> # Select a row in the table and press DEL key. The row must get deleted from the database and also the table.<br /> <br /> <br /> == Known Issues ==<br /> # Server: the keep-alive interval must not be smaller than the time it takes to transmit the database file from one tracker to another. For example, wil a value of &quot;1 minute&quot; for that interval, if the size of the database file gets in orders of some hundred megabytes or some gigabytes (i.e., some millions of users), that interval must be increased to &quot;10 minutes&quot; or so.<br /> # Client: The ''preferences'' frame silently rejects settings that are out of supported ranges. For example, max memory usage below 4 MB will be rejected without giving any warning. Due to the limitation of Java class and display space, we plan to address this in the new GUI design.<br /> # Client: When a receiver loses its Internet connection, the pCDN client does not return a proper error code to podcast clients, such as iTunes. Instead, we wait until iTunes times out.<br /> # Server: Server would crash (XXX need to validate this), if the RDBMS goes off-line.<br /> <br /> <br /> *The following are also posted to Bugzilla (can be removed from here, but not suggested):<br /> <br /> #Client: When we stop downloading a file in iTunes, the pCDN client still continues downloading.<br /> #*A user might have stopped the download in order to save his bandwidth for some other applications, but the pCDN client prevents that saving.<br /> #Server: Each tracker has a file settings.ini, which must be the same for all trackers. Having this file in a centralized manner, such as on a file server, may be helpful, because modification of that file on some tracker may cause improper functioning of the entire system. <br /> #The directory containing media files a peer has stored gets larger and larger by time. There should be a mechanism to delete unnecessary ones. [Cheng 08/03/01, There is a max disk usage setting in client GUI, which will remove the least recently received files. Note that, however, the recency is not persistent, so the received time of each files got lost after rebooting pCDN clients.]</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Testplan&diff=1568 2008-03-04T19:43:19Z

<p>Nitin.chiluka: </p> <hr /> <div>== Client ==<br /> # Download several new podcasts from the web servers (make sure the media/ directory contains no media files before this test). <br /> # Download new podcasts from several pCDN senders.<br /> # Download podcasts that were downloaded before (and still in media/ directory).<br /> # Reduce the harddisk quota using user interface to 50 MB, and download several podcasts.<br /> # Reduce the memory quota to 4 MB, and download several podacsts.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from one of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cables from all of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from the receiver. <br /> # Manually truncate the media files in media/ directory, and download that file from the podcast client.<br /> # Manually truncate the media files in media/ directory, and request that file from another pCDN client.<br /> # Download several new podcasts using a pCDN client behind a NAT box. Check whether the IP/port are correctly reported at the pCDN server. Also try to use this pCDN client as the sender.<br /> # Download several new podcasts using a pCDN client on a machine with multiple IPs. Use user-interface to select an outgoing IP. Then, change the NICs' IP addresses, and see whether the pCDN client continues work after reboots.<br /> <br /> <br /> == Server ==<br /> Note: In case a tracker gets disconnected, re-connection suffices (e.g., re-plugging the cable if the cable was unplugged). There is no need to re-start the tracker.<br /> <br /> # When trackers are up and connected to each other:<br /> #*peers download files from each other as expected.<br /> # Have a peer download podcasts, and then bring the current primary tracker down (or unplug its network cable):<br /> #*No problem. The peer communicates with the next tracker after a few seconds.<br /> #(i) Have a peer join the network when some trackers are down, or (ii) After the peer joined the network (primary tracker is T1 for example), bring T1 down and have the peer request some files:<br /> #*No problem. Peer connects to the next tracker to join/request.<br /> #Re-plug the network cable of a tracker that was the primary and has been disconnected from the network since we unplugged its cable:<br /> #*The trackers gets working properly, becomes primary, and receives the most recent database file from the tracker who was the primary during the absence (cable-unplugged) period.<br /> #A tracker T1, who is prior to T2 for being the primary, has been down/disconnected and is just started/re-connected. When a peer (who is now connected to T2) requests to download a file:<br /> #*T2 leads the peer to T1 and the peer immediately connects to T1 to ask where to download the file from.<br /> #Have a peer P1 download a file F1, wait until the backuping moment (when the primary tracker T1 pushes his recent database to others), and bring the primary tracker down after that:<br /> #*Tracker T2 becomes the primary and P2 downloads file F1 from peer P1 (not from the web server).<br /> #Tracker T1 was the primary, but is down/disconnected now and tracker T2 is the current primary. Peer P1 downloads file F1. T1 comes back and becomes the primary, so T2 immediately pushes the most recent database to T1. Then, peer P2 requests to download F1:<br /> #*If T1 was brought down by Ctrl+C and is started again now: P2 download F1 from P1.<br /> #*If T1 was disconnected by unplugging its network cable: when P2 now requests the file, the balloon “Sorry, you are not permitted to download the file” is shown (XXX).<br /> #When a peer is connected to the network and suddenly all trackers get dead:<br /> #*The peer keeps re-trying to connect. Thus when some tracker came up, the peer connects to it.<br /> #Run trackers T1 and T2, where T1 is the primary, and a peer is connected to the network. Stop T1, so T2 becomes the primary, and the peers connects to T2 after a short time. Start T1 again. Now, for a few seconds T2 still thinks he is the primary. Immediately unplug T2’s cable.<br /> #*T1 knows himself as the primary and the peer downloads files through T1.<br /> #*T2 after some seconds knows that he is the primary. The peer is able to download files through T2.<br /> <br /> <br /> == Admin Tools ==<br /> === Server Statistics === <br /> # When a peer joins the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' increase by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The country the peer belongs to is inserted into the left table if the country is not already there in the left table. When that country is clicked, all the peers that belong to that country along with city and region details are shown in the right table. Also, note that the number of peers respective to the country also increment<br /> #* Content tab: If that peer has files, these files are inserted into the left table (if these are not already there) and the peer info is added to the corresponding file. When one clicks on a particular file, all those peers containing that file are shown in the right table.<br /> # When a peer leaves the network, there are (max) 3 updates that happen in the UI:<br /> #* Bottom of the screen: '#Peers' decrease by 1 after MainData Update interval, which is set at the time of Login.<br /> #* Connected Peers tab: The peer is deleted from the respective country's right table and if the corresponding country has no peers, the country will be deleted from the left table. Also, note that the number of peers respective to the country also decrement.<br /> #* Content tab: This particular peer's record is coloured grey in the right table for every file (present in the left table) it contains.<br /> # When a peer downloads a file, 'Content' tab is updated by inserting file info in the left table if it is not already there and then to the corresponding file's right table, this peer info is added.<br /> <br /> <br /> === Geo-Fencing ===<br /> #<br /> <br /> <br /> === Content Importer ===<br /> # Select a group from the combo box and enter a feed URL and output feed filename and press &quot;Import and Convert&quot; button. <br /> #* Success: A dialog pops up saying that these files are imported into the database. Check in the database's 'Media' table that these files are imported and also 'Groups' table being populated with the corresponding fileid and groupid information. Also, these files are inserted into the 'Media Files' tab's table pointing to respective group. Check the output file is created with http://localhost being inserted for every URL within that feed file.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Select a group from the combo box and enter a non-feed URL and press &quot;Import&quot;.<br /> #* Success: A dialog pops up saying that these files are imported into the database along with output URL. Check in the database's 'Media' table that this file is imported and also 'Groups' table being populated with the corresponding fileid and groupid information.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Try pressing &quot;Import and Convert&quot; button with atleast any one of the Feed-URL fields unfilled/empty, a dialog box is shown with a message that both the fields are to be filled.<br /> # Try pressing &quot;Import&quot; button with non-feed URL field unfilled/empty, a dialog box is shown with a message that the field is to be filled.<br /> <br /> === User Administration ===<br /> # Add a new user and check if it is inserted into the database and also in the table shown below.<br /> # Change the privilege level of a user using the combo box in the table and check if it is reflected in the database.<br /> # Select a row in the table and press DEL key. The row must get deleted from the database and also the table.<br /> <br /> <br /> == Known Issues ==<br /> # Server: the keep-alive interval must not be smaller than the time it takes to transmit the database file from one tracker to another. For example, wil a value of &quot;1 minute&quot; for that interval, if the size of the database file gets in orders of some hundred megabytes or some gigabytes (i.e., some millions of users), that interval must be increased to &quot;10 minutes&quot; or so.<br /> # Client: The ''preferences'' frame silently rejects settings that are out of supported ranges. For example, max memory usage below 4 MB will be rejected without giving any warning. Due to the limitation of Java class and display space, we plan to address this in the new GUI design.<br /> # Client: When a receiver loses its Internet connection, the pCDN client does not return a proper error code to podcast clients, such as iTunes. Instead, we wait until iTunes times out.<br /> # Server: Server would crash (XXX need to validate this), if the RDBMS goes off-line.<br /> <br /> <br /> *The following are also posted to Bugzilla (can be removed from here, but not suggested):<br /> <br /> #Client: When we stop downloading a file in iTunes, the pCDN client still continues downloading.<br /> #*A user might have stopped the download in order to save his bandwidth for some other applications, but the pCDN client prevents that saving.<br /> #Server: Each tracker has a file settings.ini, which must be the same for all trackers. Having this file in a centralized manner, such as on a file server, may be helpful, because modification of that file on some tracker may cause improper functioning of the entire system. <br /> #The directory containing media files a peer has stored gets larger and larger by time. There should be a mechanism to delete unnecessary ones. [Cheng 08/03/01, There is a max disk usage setting in client GUI, which will remove the least recently received files. Note that, however, the recency is not persistent, so the received time of each files got lost after rebooting pCDN clients.]</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Testplan&diff=1567 2008-03-04T19:02:49Z

<p>Nitin.chiluka: </p> <hr /> <div>== Client ==<br /> # Download several new podcasts from the web servers (make sure the media/ directory contains no media files before this test). <br /> # Download new podcasts from several pCDN senders.<br /> # Download podcasts that were downloaded before (and still in media/ directory).<br /> # Reduce the harddisk quota using user interface to 50 MB, and download several podcasts.<br /> # Reduce the memory quota to 4 MB, and download several podacsts.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from one of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cables from all of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from the receiver. <br /> # Manually truncate the media files in media/ directory, and download that file from the podcast client.<br /> # Manually truncate the media files in media/ directory, and request that file from another pCDN client.<br /> # Download several new podcasts using a pCDN client behind a NAT box. Check whether the IP/port are correctly reported at the pCDN server. Also try to use this pCDN client as the sender.<br /> # Download several new podcasts using a pCDN client on a machine with multiple IPs. Use user-interface to select an outgoing IP. Then, change the NICs' IP addresses, and see whether the pCDN client continues work after reboots.<br /> <br /> <br /> == Server ==<br /> Note: In case a tracker gets disconnected, re-connection suffices (e.g., re-plugging the cable if the cable was unplugged). There is no need to re-start the tracker.<br /> <br /> # When trackers are up and connected to each other:<br /> #*peers download files from each other as expected.<br /> # Have a peer download podcasts, and then bring the current primary tracker down (or unplug its network cable):<br /> #*No problem. The peer communicates with the next tracker after a few seconds.<br /> #(i) Have a peer join the network when some trackers are down, or (ii) After the peer joined the network (primary tracker is T1 for example), bring T1 down and have the peer request some files:<br /> #*No problem. Peer connects to the next tracker to join/request.<br /> #Re-plug the network cable of a tracker that was the primary and has been disconnected from the network since we unplugged its cable:<br /> #*The trackers gets working properly, becomes primary, and receives the most recent database file from the tracker who was the primary during the absence (cable-unplugged) period.<br /> #A tracker T1, who is prior to T2 for being the primary, has been down/disconnected and is just started/re-connected. When a peer (who is now connected to T2) requests to download a file:<br /> #*T2 leads the peer to T1 and the peer immediately connects to T1 to ask where to download the file from.<br /> #Have a peer P1 download a file F1, wait until the backuping moment (when the primary tracker T1 pushes his recent database to others), and bring the primary tracker down after that:<br /> #*Tracker T2 becomes the primary and P2 downloads file F1 from peer P1 (not from the web server).<br /> #Tracker T1 was the primary, but is down/disconnected now and tracker T2 is the current primary. Peer P1 downloads file F1. T1 comes back and becomes the primary, so T2 immediately pushes the most recent database to T1. Then, peer P2 requests to download F1:<br /> #*If T1 was brought down by Ctrl+C and is started again now: P2 download F1 from P1.<br /> #*If T1 was disconnected by unplugging its network cable: when P2 now requests the file, the balloon “Sorry, you are not permitted to download the file” is shown (XXX).<br /> #When a peer is connected to the network and suddenly all trackers get dead:<br /> #*The peer keeps re-trying to connect. Thus when some tracker came up, the peer connects to it.<br /> #Run trackers T1 and T2, where T1 is the primary, and a peer is connected to the network. Stop T1, so T2 becomes the primary, and the peers connects to T2 after a short time. Start T1 again. Now, for a few seconds T2 still thinks he is the primary. Immediately unplug T2’s cable.<br /> #*T1 knows himself as the primary and the peer downloads files through T1.<br /> #*T2 after some seconds knows that he is the primary. The peer is able to download files through T2.<br /> <br /> <br /> == Admin Tools ==<br /> === Server Statistics === <br /> # When a peer joins the network, <br /> <br /> === Geo - Fencing ===<br /> <br /> === Content Importer ===<br /> # Select a group from the combo box and enter a feed URL and output feed filename and press &quot;Import and Convert&quot; button. <br /> #* Success: A dialog pops up saying that these files are imported into the database. Check in the database's 'Media' table that these files are imported and also 'Groups' table being populated with the corresponding fileid and groupid information. Also, these files are inserted into the 'Media Files' tab's table pointing to respective group. Check the output file is created with http://localhost being inserted for every URL within that feed file.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Select a group from the combo box and enter a non-feed URL and press &quot;Import&quot;.<br /> #* Success: A dialog pops up saying that these files are imported into the database along with output URL. Check in the database's 'Media' table that this file is imported and also 'Groups' table being populated with the corresponding fileid and groupid information.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Try pressing &quot;Import and Convert&quot; button with atleast any one of the Feed-URL fields unfilled/empty, a dialog box is shown with a message that both the fields are to be filled.<br /> # Try pressing &quot;Import&quot; button with non-feed URL field unfilled/empty, a dialog box is shown with a message that the field is to be filled.<br /> <br /> === User Administration ===<br /> # Add a new user and check if it is inserted into the database and also in the table shown below.<br /> # Change the privilege level of a user using the combo box in the table and check if it is reflected in the database.<br /> # Select a row in the table and press DEL key. The row must get deleted from the database and also the table.<br /> <br /> <br /> == Known Issues ==<br /> # Server: the keep-alive interval must not be smaller than the time it takes to transmit the database file from one tracker to another. For example, wil a value of &quot;1 minute&quot; for that interval, if the size of the database file gets in orders of some hundred megabytes or some gigabytes (i.e., some millions of users), that interval must be increased to &quot;10 minutes&quot; or so.<br /> # Client: The ''preferences'' frame silently rejects settings that are out of supported ranges. For example, max memory usage below 4 MB will be rejected without giving any warning. Due to the limitation of Java class and display space, we plan to address this in the new GUI design.<br /> # Client: When a receiver loses its Internet connection, the pCDN client does not return a proper error code to podcast clients, such as iTunes. Instead, we wait until iTunes times out.<br /> # Server: Server would crash (XXX need to validate this), if the RDBMS goes off-line.<br /> <br /> <br /> *The following are also posted to Bugzilla (can be removed from here, but not suggested):<br /> <br /> #Client: When we stop downloading a file in iTunes, the pCDN client still continues downloading.<br /> #*A user might have stopped the download in order to save his bandwidth for some other applications, but the pCDN client prevents that saving.<br /> #Server: Each tracker has a file settings.ini, which must be the same for all trackers. Having this file in a centralized manner, such as on a file server, may be helpful, because modification of that file on some tracker may cause improper functioning of the entire system. <br /> #The directory containing media files a peer has stored gets larger and larger by time. There should be a mechanism to delete unnecessary ones. [Cheng 08/03/01, There is a max disk usage setting in client GUI, which will remove the least recently received files. Note that, however, the recency is not persistent, so the received time of each files got lost after rebooting pCDN clients.]</div>

Nitin.chiluka https://nmsl.cs.sfu.ca/index.php?title=pCDN:Testplan&diff=1566 2008-03-04T18:59:15Z

<p>Nitin.chiluka: </p> <hr /> <div>== Client ==<br /> # Download several new podcasts from the web servers (make sure the media/ directory contains no media files before this test). <br /> # Download new podcasts from several pCDN senders.<br /> # Download podcasts that were downloaded before (and still in media/ directory).<br /> # Reduce the harddisk quota using user interface to 50 MB, and download several podcasts.<br /> # Reduce the memory quota to 4 MB, and download several podacsts.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from one of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cables from all of the senders.<br /> # Download new podcasts from several senders and unplug the Ethernet cable from the receiver. <br /> # Manually truncate the media files in media/ directory, and download that file from the podcast client.<br /> # Manually truncate the media files in media/ directory, and request that file from another pCDN client.<br /> # Download several new podcasts using a pCDN client behind a NAT box. Check whether the IP/port are correctly reported at the pCDN server. Also try to use this pCDN client as the sender.<br /> # Download several new podcasts using a pCDN client on a machine with multiple IPs. Use user-interface to select an outgoing IP. Then, change the NICs' IP addresses, and see whether the pCDN client continues work after reboots.<br /> <br /> <br /> == Server ==<br /> Note: In case a tracker gets disconnected, re-connection suffices (e.g., re-plugging the cable if the cable was unplugged). There is no need to re-start the tracker.<br /> <br /> # When trackers are up and connected to each other:<br /> #*peers download files from each other as expected.<br /> # Have a peer download podcasts, and then bring the current primary tracker down (or unplug its network cable):<br /> #*No problem. The peer communicates with the next tracker after a few seconds.<br /> #(i) Have a peer join the network when some trackers are down, or (ii) After the peer joined the network (primary tracker is T1 for example), bring T1 down and have the peer request some files:<br /> #*No problem. Peer connects to the next tracker to join/request.<br /> #Re-plug the network cable of a tracker that was the primary and has been disconnected from the network since we unplugged its cable:<br /> #*The trackers gets working properly, becomes primary, and receives the most recent database file from the tracker who was the primary during the absence (cable-unplugged) period.<br /> #A tracker T1, who is prior to T2 for being the primary, has been down/disconnected and is just started/re-connected. When a peer (who is now connected to T2) requests to download a file:<br /> #*T2 leads the peer to T1 and the peer immediately connects to T1 to ask where to download the file from.<br /> #Have a peer P1 download a file F1, wait until the backuping moment (when the primary tracker T1 pushes his recent database to others), and bring the primary tracker down after that:<br /> #*Tracker T2 becomes the primary and P2 downloads file F1 from peer P1 (not from the web server).<br /> #Tracker T1 was the primary, but is down/disconnected now and tracker T2 is the current primary. Peer P1 downloads file F1. T1 comes back and becomes the primary, so T2 immediately pushes the most recent database to T1. Then, peer P2 requests to download F1:<br /> #*If T1 was brought down by Ctrl+C and is started again now: P2 download F1 from P1.<br /> #*If T1 was disconnected by unplugging its network cable: when P2 now requests the file, the balloon “Sorry, you are not permitted to download the file” is shown (XXX).<br /> #When a peer is connected to the network and suddenly all trackers get dead:<br /> #*The peer keeps re-trying to connect. Thus when some tracker came up, the peer connects to it.<br /> #Run trackers T1 and T2, where T1 is the primary, and a peer is connected to the network. Stop T1, so T2 becomes the primary, and the peers connects to T2 after a short time. Start T1 again. Now, for a few seconds T2 still thinks he is the primary. Immediately unplug T2’s cable.<br /> #*T1 knows himself as the primary and the peer downloads files through T1.<br /> #*T2 after some seconds knows that he is the primary. The peer is able to download files through T2.<br /> <br /> <br /> == Admin Tools ==<br /> === Server Statistics === <br /> # When a peer joins the network, <br /> <br /> === Geo - Fencing ===<br /> <br /> === Content Importer ===<br /> # Select a group from the combo box and enter a feed URL and output feed filename and press &quot;Import and Convert&quot; button. <br /> #* Success: A dialog pops up saying that these files are imported into the database. Check in the database's 'Media' table that these files are imported and also 'Groups' table being populated with the corresponding fileid and groupid information. Also, these files are inserted into the 'Media Files' tab's table pointing to respective group. Check the output file is created with http://localhost being inserted for every URL within that feed file.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Select a group from the combo box and enter a non-feed URL and press &quot;Import&quot;.<br /> #* Success: A dialog pops up saying that these files are imported into the database along with output URL. Check in the database's 'Media' table that this file is imported and also 'Groups' table being populated with the corresponding fileid and groupid information.<br /> #* Failure: A dialog pops up saying that these files could not be imported into the database. Check if database is the same as before.<br /> # Try pressing either of the 2 buttons with atleast any one of the corresponding fields unfilled/empty, a dialog box is shown with a message that those corresponding fields are to be filled.<br /> <br /> <br /> === User Administration ===<br /> # Add a new user and check if it is inserted into the database and also in the table shown below.<br /> # Change the privilege level of a user using the combo box in the table and check if it is reflected in the database.<br /> # Select a row in the table and press DEL key. The row must get deleted from the database and also the table.<br /> <br /> <br /> == Known Issues ==<br /> # Server: the keep-alive interval must not be smaller than the time it takes to transmit the database file from one tracker to another. For example, wil a value of &quot;1 minute&quot; for that interval, if the size of the database file gets in orders of some hundred megabytes or some gigabytes (i.e., some millions of users), that interval must be increased to &quot;10 minutes&quot; or so.<br /> # Client: The ''preferences'' frame silently rejects settings that are out of supported ranges. For example, max memory usage below 4 MB will be rejected without giving any warning. Due to the limitation of Java class and display space, we plan to address this in the new GUI design.<br /> # Client: When a receiver loses its Internet connection, the pCDN client does not return a proper error code to podcast clients, such as iTunes. Instead, we wait until iTunes times out.<br /> # Server: Server would crash (XXX need to validate this), if the RDBMS goes off-line.<br /> <br /> <br /> *The following are also posted to Bugzilla (can be removed from here, but not suggested):<br /> <br /> #Client: When we stop downloading a file in iTunes, the pCDN client still continues downloading.<br /> #*A user might have stopped the download in order to save his bandwidth for some other applications, but the pCDN client prevents that saving.<br /> #Server: Each tracker has a file settings.ini, which must be the same for all trackers. Having this file in a centralized manner, such as on a file server, may be helpful, because modification of that file on some tracker may cause improper functioning of the entire system. <br /> #The directory containing media files a peer has stored gets larger and larger by time. There should be a mechanism to delete unnecessary ones. [Cheng 08/03/01, There is a max disk usage setting in client GUI, which will remove the least recently received files. Note that, however, the recency is not persistent, so the received time of each files got lost after rebooting pCDN clients.]</div>

Nitin.chiluka