Deployment Scenarios
ConfD has a modular architecture. Users can employ only the relevant components when extending an existing on-device management system. Alternatively, all of the components can be used to provide the full functionality of a new management system.
Developing a New System
A new product may need a new XML-centric management system. In this case, ConfD provides all the components needed:
- NETCONF Interface
- CLI
- Web UI
- SNMP
- Shared XML-centric management "backplane" that implements the operations of the NETCONF, CLI, Web UI, and SNMP agents
- AAA system using by all management agents
- Fault-tolerant XML database for storing configuration data
Extending an Existing System
An existing management system may already have CLI, Web, and SNMP interfaces, but needs to meet new requirements for XML-based management. In this scenario, the NETCONF component of ConfD can be bolted onto the existing system. Two things must then be done:
- An XML specification that describes the configuration data must be written
- A mapping between the XML specification and the configuration data as currently represented must be provided - this mapping is specified in the XML specification, using callbacks to C or using in-lined Javascript functions
The configuration data can be stored in ConfD's built-in XML database, which supports all mechanisms needed to make a robust NETCONF implementation. This database has a simple and efficient API that is used by managed objects to read configuration data and to react on changes.
ConfD can also be used when the configuration is stored externally, for example in another database, in memory, or in configuration files. In this case, a mapping from existing configuration data to the XML structures expected by NETCONF must be provided.