From: Rob B. <rob...@ar...> - 2007-02-27 17:20:59
|
All, I've checked in new Dynamic registry code. It's now under blue/java/registry/org/blue/registry. I've moved it over to using Jboss Remoting and the required library is under blue/java/registry/lib. If people could take the time to review the concepts and leave comments that would be appreciated. My basic thoughts on how the registry is to work includes the following: 1: We extend blue.cfg with a new option registrar_config. This allows the user to specify a .cfg file that contains the configuration information for the registrar. Within the registrar config the user can specify the port on which it is to run, the transport it is to use, whether it accepts multicast requests to register, are we actually allowing dynamic registration. 2: Based around the above configuration file, the registry is started within Blue. 3: The user must specify a range of templates for dynamic registration. These in effect identify a "type" of remote host. So for instance my remote host could be of type "remote-db". The user defines a template for hosts of type remote-db that define what services are to monitored, who should be contacted and the method in which the monitoring is conducted. 4: The registry simply listens for requests from remote agents to register with Blue. When a request is received, the registry checks against it's known templates. If the remote agent identifies itself as a known template type, the registry writes into the configuration file mentioned above the new configuration for the remote host. 5: The registry then writes to the external command file asking Blue to check for the latest hosts that have been added. Rich, if you could get your work on the new inventory features of Blue checked in when you have the chance that would be appreciated. cheers Rob -- Registered Office: Floor A, Milburn House, Dean Street, Newcastle upon Tyne, NE1 1LE VAT Registration No: 764173128. Company registered in England Registration No: 4497081 |