Allow Critical Path IP to be in a different Provision Group
Description
I have a large network of 2,500 nodes. To be able to properly suppress node down notifications for child nodes when the parent goes down I provision a Critical Path for each node by defining the Parent-Foreign-ID As the Critical Path can only be provisioned for nodes within the same Provision Group whenusing Parent-Foreign-ID, I am stuck with having all ~2,500 nodes in the same Provision Group which can severely hamper GUI performance in certain situations such as modifying the group within the GUI to remove a service for example.
Once finished should be fixed too (just to comment it)
Benjamin Reed November 4, 2011 at 9:00 AM
I was expecting you would have to depend on a parent foreign-source/foreign-id combination, then it would always be safe...
Roy Crombleholme November 4, 2011 at 6:42 AM
After thinking about this a bit more deeply, this change could maybe cause issues for those who depend on the current behaviour. If two different foreign sources are being used to provision one instance of OpenNSM, allowing parent-foreign-id across provisioning groups could cause clash if two foreign-id s are the same but in different provisioning groups. I guess the answer would be to make an option to toggle between both modes but not sure how technically feasible that would be.
Seth Leger November 3, 2011 at 12:10 PM
Looks like a good feature but would probably require DB and/or XML schema changes. Targeting for 1.11.
I have a large network of 2,500 nodes. To be able to properly suppress node down notifications for child nodes when the parent goes down I provision a Critical Path for each node by defining the Parent-Foreign-ID
As the Critical Path can only be provisioned for nodes within the same Provision Group whenusing Parent-Foreign-ID, I am stuck with having all ~2,500 nodes in the same Provision Group which can severely hamper GUI performance in certain situations such as modifying the group within the GUI to remove a service for example.