The way of detecting whether a rollback in a network wide
automated configuration attempt is needed is a test as
invariant to this change request. They need to be suitable
paired: if the test, as formulated by the operator or the
Uber-NMS fails, the rollback must be performed. Tests can
be organized hierarchically, i.e. some testing the basic
functionality with each change, and some testing the goal
of a change.
Furthermore I'd definitely put the rollback to the box,
as Juergen wrote. A secure network-wide rollback is only
possible if each box invovled provides a safe local
rollback. Many networks could exist with not completely
save network-wide rollback issued by NMS. The operator
MUST decide which one he needs, and the network SHOULD
support both :)
Thanks for the insight. This thread is interesting to
read!
bye,
Gio
Epygi Labs DE GmbH - Georg 'Gio' Magschok
|
|
