A set of fundamental lifecycle operations have to be specified. This set will probably include operations like CREATE, DELETE, START, STOP etc. The list of such operations should be restricted to operations that most node types will support anyhow. The subset of those operations that must be supported by each Node Type (e.g. CREATE, DELETE) must be identified.
Although most Node Types will support these operations, the actual signature may vary from NodeType to Node Type. It should be identified if the variants of each operation support a set of common parameters, and these parameters should be specified.
A mechanism should be provided that allows to add the specific parameters of each variant of each operation. This will allow to refer to a lifecycle operation from a task in a plan in a generic manner without having to create tasks that refer to a concrete variant (i.e. a variant with its concrete signature). Such a task could then be bound to a concrete operation of a specific Node Type by selecting the appropriate specific parameters.