TestnetFramework - Cronologia

Ldecicco: /* Motivations */

2009-06-09T17:16:37Z

‎Motivations

Ldecicco: /* TestNet Framework (NS-2 for the real world) */

2009-06-09T17:06:23Z

‎TestNet Framework (NS-2 for the real world)

Ldecicco: /* Motivations */

2009-06-09T17:05:58Z

‎Motivations

Ldecicco: /* Motivations */

2009-01-26T15:16:12Z

‎Motivations

Ldecicco: /* TestNet Framework (a.k.a. NS-2 for the real world) */

2008-11-19T19:19:58Z

‎TestNet Framework (a.k.a. NS-2 for the real world)

SMascolo: /* Definitions */

2007-07-09T21:53:02Z

‎Definitions

Ldecicco: /* Definitions */

2007-06-08T11:25:16Z

‎Definitions

Ldecicco: /* TestNet Framework (a.k.a. NS-2 for the real world) */

2007-06-08T11:24:04Z

‎TestNet Framework (a.k.a. NS-2 for the real world)

Ldecicco: /* TestNet Framework (a.k.a. NS-2 for the real world) */

2007-06-08T10:02:04Z

‎TestNet Framework (a.k.a. NS-2 for the real world)

SMascolo il 09:47, 8 Giu 2007

2007-06-08T09:47:13Z

@@ Riga 4: / Riga 4: @@
 TNF is a framework made by a set of tools that allows to deploy real network experiments in a simple and automated way while minimizing the time required for distributed testbeds set up.
-A distributed database maintains the informations about topology, experiment settings and logfiles obtained in the experiments. Therefore, all log files involved in the experiments, and distributed among the nodes, can be retrievedin a transparent manner ("just a button click") using a simple API call made available by the framework.
+A distributed database maintains the informations about topology, experiment settings and logfiles obtained in the experiments. Therefore, all log files involved in the experiments, and distributed among the nodes, can be retrieved in a transparent manner ("just a button click") using a simple API call made available by the framework.
 An overlay Peer-to-Peer network is used for setting up experiments: all nodes involved in an experiment may contact a central node (the supernode) where information about the topology of the overlay network are stored.

←Older revision		Revisione 17:06, 9 Giu 2009
Riga 1:		Riga 1:
−	=TestNet Framework ~~(NS-2 for the real world)~~=	+	=TestNet Framework=

	== Motivations==		== Motivations==

@@ Riga 2: / Riga 2: @@
 == Motivations==
-TNF is a framework made by a set of tools that is able to deploy real network experiments in a simple and automated way and minimizing the time required for distributed testbeds set up.
+TNF is a framework made by a set of tools that allows to deploy real network experiments in a simple and automated way while minimizing the time required for distributed testbeds set up.
-Another motivation for the TNF is that at the time of writing there is no tool that is able to display results of networking experiments, because of the different log files format used by each application. For this reason, we aim at providing tools to produce homogeneous logfiles for each application involved in the experiments.
+A distributed database maintains the informations about topology, experiment settings and logfiles obtained in the experiments. Therefore, all log files involved in the experiments, and distributed among the nodes, can be retrievedin a transparent manner ("just a button click") using a simple API call made available by the framework.
-A distributed database maintains the informations about topology, experiment settings and logfiles obtained in the experiments. In this way the framework is able to retrieve in a transparent manner ("just a button click") all log files involved in an experiment which are distributed among all the nodes.
+An overlay Peer-to-Peer network is used for setting up experiments: all nodes involved in an experiment may contact a central node (the supernode) where information about the topology of the overlay network are stored.
 A ''Service Discovery'' system will help the researcher to find services which he needs for his experiments.

@@ Riga 2: / Riga 2: @@
 == Motivations==
-The motivation of TNF is to have a set of tools that will enable to deploy real network experiments in a simple and automated way without the knowledge of how Services work and minimizing the time required for distributed testbeds set up.
+TNF is a framework made by a set of tools that is able to deploy real network experiments in a simple and automated way and minimizing the time required for distributed testbeds set up.
-Another motivation for the TNF is that at the time of writing there is no tool that is able to display results of networking experiments, because of the different log files format used by each application. In spite of this, we aim at providing tools to produce homogeneous logfiles for each application involved in the experiments.
+Another motivation for the TNF is that at the time of writing there is no tool that is able to display results of networking experiments, because of the different log files format used by each application. For this reason, we aim at providing tools to produce homogeneous logfiles for each application involved in the experiments.
-A distributed database maintains the informations about topology, experiment settings and logfiles obtained by the experiments. In this way it is possibile to deploy a system which is able to retrieve in a transparent manner ("just a button click") all log files involved in an experiments which are obviously distributed among all the nodes.
+A distributed database maintains the informations about topology, experiment settings and logfiles obtained in the experiments. In this way the framework is able to retrieve in a transparent manner ("just a button click") all log files involved in an experiment which are distributed among all the nodes.
-An overlay Peer-to-Peer network is used for setting up experiments: all nodes which would like to set up an experiment can contact a central node (the supernode) which has informations about the topology of the overlay network.
+An overlay Peer-to-Peer network is used for setting up experiments: all nodes involved in an experiment may contact a central node (the supernode) whereby informations about the topology of the overlay network are stored.
 A ''Service Discovery'' system will help the researcher to find services which he needs for his experiments.
 ==Definitions==

←Older revision		Revisione 19:19, 19 Nov 2008
Riga 1:		Riga 1:
−	=TestNet Framework (~~a.k.a.~~ NS-2 for the real world)=	+	=TestNet Framework (NS-2 for the real world)=

	== Motivations==		== Motivations==

@@ Riga 22: / Riga 22: @@
 In the TestNet Framework (TNF) an experiment is defined as ''"the interaction between services of different Nodes or within a single Node under the control of a special Node which is called '''Experiment Manager''"'''.
-Each service produces logfiles in order to evaluate performances indexes so that the Experiment Manager will have at the end of the experiment all logfiles produced by each nodes involved in the experiment.
+Each service produces logfiles in order to evaluate performances indexes so that the Experiment Manager will store all logfiles produced by each nodes involved in the experiment.
 The TestNet Framework is built upon the following tools:
@@ Riga 30: / Riga 30: @@
 * Node Monitor
-The ''Testnet Overlay Network'' (TON) is a network built on Node Monitors which communicates between each other using the RPC protocol.
+The ''Testnet Overlay Network'' (TON) is a network built on Node Monitors which communicate between them using the RPC protocol.
 The ''Node Monitor'' (NM) manages services available on the node itself and executes commands received via the RPC interface sent by other nodes in the overlay network.

@@ Riga 36: / Riga 36: @@
 The ''Experiment Manager'' (EM) runs distributed experiments making basically RPC calls to NMs using a simple scripting language. Moreover EM can ask NMs services available on the node in order to search for specific services in the overlay network.
-''Services'' are the core of the framework, they have to export an interface for logging (LogI) facilities and to manage start/stop of the service. We can define a service as ''any piece of software that exports those two interfaces'' to the node manager. The NM communicate to each service via the DBUS inter process communication (IPC) facility.
+''Services'' are the core of the framework, they have to export an interface for logging (LogI) facilities and to manage start/stop of the service. We can define a service as ''any piece of software that exports those two interfaces'' to the node manager. The NM communicate to each service via the [http://www.freedesktop.org/wiki/Software/dbus DBUS] inter process communication (IPC) facility.
-Applications that use ''libnetmeas'' automatically export the Logging Interface so the only other requirement to let the application be in the framework is to write a simple wrapper that implements the start/stop interface.
+Applications that use [[ Libnetmeas | libnetmeas]] automatically export the Logging Interface so the only other requirement to let the application be in the framework is to write a simple wrapper that implements the start/stop interface.
 [[Immagine:testnet_big_picture.png]]

←Older revision		Revisione 11:24, 8 Giu 2007
Riga 41:		Riga 41:

	[[Immagine:testnet_big_picture.png]]		[[Immagine:testnet_big_picture.png]]
−
−	~~--[[Utente:Ldecicco\|Ldecicco]] 22:57, Lug 8, 2006 (CEST)~~

←Older revision		Revisione 09:47, 8 Giu 2007
Riga 1:		Riga 1:
−	~~<accesscontrol>Lab</accesscontrol>~~
	= TestNet Framework (a.k.a. NS-2 for the real world)=		= TestNet Framework (a.k.a. NS-2 for the real world)=