Ability to add parent relationships (path outages) in provisioning WebUI
Description
Environment
Acceptance / Success Criteria
Lucidchart Diagrams
Activity
Alejandro Galue December 6, 2013 at 11:19 AM
Fixed on revision ff25a95bbb7f8ddb16e1f5a6e198142081911ba0 for 1.12
Features added:
Be able to configure parent-foreign-label, parent-foreign-id and parent-foreign-source from the Requisition WebUI
Be able to set the interface status through the WebUI
Reduce the size of the combo-box for the snmp-primary field
Martin Lärcher November 20, 2013 at 11:43 AM
for new Accesspoint Monitor feature it should be also possible to add parentForeignSource and parentForeignId:
<tree:field label="Parent-Foreign-Id" property="parentForeignId" />
<tree:field label="Parent-Foreign-Source" property="parentForeignSource" />
These two fields are mandatory for Access Point Monitor to work properly.
David Hustace March 22, 2012 at 10:46 AM
Ben, thought you might want to look a this issue while you're working on the issue allowing this field and the parent-foreign-id field to be global to all provisioned nodes.
Martin Lärcher May 19, 2011 at 3:04 PM
An option to define criticalpath ip in co-existence (same way) with the other options should also be concerned.
The current way to define the criticalpath in the Web UI is too prone for errors (if you define one wrong, all others are overwriten / deleted).
So you can define more granularity if you have nodes with multiple vrrp/hsrp etc. interfaces that are "parents" for others.
Dominik March 2, 2011 at 3:30 AM
with s/parentNodeLabel/parentForeignId/ one could also add a field for parent foreign id. Found that very useful.
Hi,
it would be helpful to have the possibility to add node-parent-label in the Provisioning Webinterface.
In XML Integration Format http://www.opennms.org/wiki/Integration_XML_Format
it is listed as an attribute:
<attribute name="parent-node-label" use="required" >
<annotation>
<documentation>This will be used to help define a node's path on the network.</documentation>
</annotation>
<simpleType>
<restriction base="string">
<!-- <pattern value="^[0-9A-Za-z][-0-9A-Za-z._]+$"></pattern> -->
<pattern value=".*$"></pattern>
</restriction>
</simpleType>
</attribute>