Support for Multiple Peer deployments. Support for coexisting several ADMLS instances...

[anna.git] / example / diameter / launcher / deployments / st-client / README

diff --git a/example/diameter/launcher/deployments/st-client/README b/example/diameter/launcher/deployments/st-client/README
index d6f4f5b..fd3860a 100644 (file)
--- a/example/diameter/launcher/deployments/st-client/README
+++ b/example/diameter/launcher/deployments/st-client/README
@@ -13,7 +13,9 @@ not, dynamic programming will fail because the appropiate service is
 not configured before starting ADML instances.
 
 Execute './configure.sh' and follow the intructions to clone the ADML
 not configured before starting ADML instances.
 
 Execute './configure.sh' and follow the intructions to clone the ADML

-instance into the needed amount for system testing.
+instance into the needed amount for system testing. Every time you run
+this, a new 'ADMLS#<description>' directory is created and symlinked
+to 'ADMLS'.

 
 STARTING THE PROCESS
 --------------------
 
 STARTING THE PROCESS
 --------------------


@@ -24,6 +26,8 @@ the operation provided through every cloned instance. For example, if
 you provide 'test|ttps|5', the speed of 5 test cases per second will
 be set on every ADML instance. Imagine you have N instances, and then
 you actually are establishing a total 5*N speed rate over the servers.
 you provide 'test|ttps|5', the speed of 5 test cases per second will
 be set on every ADML instance. Imagine you have N instances, and then
 you actually are establishing a total 5*N speed rate over the servers.

+You could run another 'ADMLS#<description>' directory just providing
+it as argument.

 
 TESTING PROCEDURE
 -----------------
 
 TESTING PROCEDURE
 -----------------


@@ -37,6 +41,9 @@ desired rate selected on configuration stage.
 Don't forget to populate whatever data you need on the tested system,
 because this work is not done here.
 
 Don't forget to populate whatever data you need on the tested system,
 because this work is not done here.
 

+Program script acts over ADMLS symlink. You must update it if want to
+program another ADMLS instances directory.
+

 OPERATION
 ---------
 Management interface for lite version is based on SIGUSR2 signal caugh.
 OPERATION
 ---------
 Management interface for lite version is based on SIGUSR2 signal caugh.


@@ -44,3 +51,6 @@ Use './operation.sh' script within a specific instance directory to send
 any operation to the process. Ask for help with that script to see all
 the operations supported.
 
 any operation to the process. Ask for help with that script to see all
 the operations supported.
 

+Operation script acts over ADMLS symlink. You must update it if want to
+operate another ADMLS instances directory.
+