cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donal Lafferty <>
Subject [DISCUSS] Plugin anatomy questions
Date Thu, 15 Nov 2012 00:11:05 GMT
AFAIK plugins are currently implemented in two halves.  One half is loaded by the management
server.  The other half is a ServerResource that controls the device.  E.g. a Discoverer establishes
communications with a ServerResource corresponding to a hypervisor host.

1.       Since "the bit loaded by the management server" is long winded, is there another
general terms that I can use to refer to this half?

As for the plugin's interface to the management server.  This seems to be expressed in two
parts.  First, there's a Java interface of methods the plugin must implement.  E.g. interface
Discoverer defines the key methods for establishing contact with a hypervisor.  Secondly,
there's a set of objects a plugin can reference via dependency injection.  E.g. when Discoverer.configure
is called, it should register as a ResourceStateAdapter using a reference to the ResourceManager.
 The ResourceManager is obtained through dependency injection.

2.       Are there any plans to remove the dependency injections available to plugin implementations?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message