[clif] RE : Re: list of connected server on a registry

[zze-Rubics DESPLAND M ext RD-SIRP-REN <mdespland.ext@xxxxxxxxxxxxxxxxxx>]

Title: Votre signature email Orange (en France)

Thanks,

 

I will try those solutions

 

yes we use the launch target :)

In my mind, i would start the registry and connect several servers and then start a sequence of tests
ant launch ...
ant launch ...
without restarting the registry and the servers. is it the normal way to do that ?

 

My question about the list of connected server on a registry, is to provide a way to the people that will start the test to control that all the servers are really registered before launching the script with the ant launch sequence.

 

I will write all the scripts but they will be execute on the production infra

 

For the contribution to the project, yes probably. this is one of the reasons we have choosed clif :)

 

 

Regards,

 

Marc Despland

 

---

De: Bruno Dillenseger
Date: lun. 07/04/2008 15:59
À: clif@xxxxxxx
Objet : [clif] Re: list of connected server on a registry

mdespland.ext@xxxxxxxxxxxxxxxxxx wrote:

Hello,

 

Is there a command to know the list of the servers connected to a registry and their states ?

Not yet. A command to get the list of registered servers is easy (just a call to NamingService.list() method).
About the server "state", it depends what you mean; for example, it may happen that a server crashed while still being registered.

I'm writing scripts launching a serie of tests from a command line, the script starts the servers with ssh command and i need a solution to control that all the server are connected and ready

I see (I guess you use the launch ant target?). In principle, a CLIF server is ready/connected (reachable) as soon as it is registered. If you run new CLIF servers for each test run while keeping the same Registry and server names, then probably a (set of) command(s) to clean the contents of the registry (so that you don't try to talk to a ghost CLIF server) would help.

To solve your problem, you could read the output of the ssh command and read the string that says the server is ready before going on. This requires no change in CLIF but is specific to your server deployment scripts.
I see another solution that requires a tiny modification of CLIF but which is independent from the way you launch your servers: CLIF's deployment process could block until the registry contains all necessary CLIF servers (polling the registry each second for instance).

What do you think about those solutions?

PS : probably your ssh-based server deployment scripts could be contributed to the project?

Regards,

-- Bruno.