-
Key: DEPL-54
-
Legacy Issue Number: 6597
-
Status: open
-
Source: Raytheon ( Jerry Bickle)
-
Summary:
6.7.1. Target Manager
The Target manager serves 3 purposes, deployment behavior, domain
information, and registration information. Three different actors use this
component.Issue 1:
To be consistent with other interfaces for registering and unregistering
information with the domain. I would replace the update operation
with two operations, register node and unregister node. The register node
takes in an abstract nodeManager (needs to be added to spec) and node's xml
profile descriptor. This provides a more open interface and can easily
accommodate extensions by the type of node manager registering and type of
profile information. This allows domains to extend the behavior as
necessary without changing the specification. This needs to be a separate
interface. The separate interface again provides the capability of
extending the registration interface with system/domain specific
registration needs. This also may affect the domain profile definition
since a node can a profile associated with it. For systems or domains
implementations that need this behavior a component could exist that
provides this behavior. Not all systems need to formally register their
information. -
Reported: DEPL 1.0b1 — Tue, 11 Nov 2003 05:00 GMT
-
Updated: Fri, 6 Mar 2015 20:58 GMT