import auto discovered nodes into a Provisioning Requisition

Description

Make it possible to import auto discovered nodes into a Provisioning Requisition.

This issue was originally filed against ONMS 1.8.10 and now 3 years later am updating my description to make it more concise and up to date. Terminology has changed.

Original post:
The task of adding local nodes to a provisioning group would be greatly eased if one could first run an auto discovery to later transfer discovered nodes to a provisioning group. The point in having such auto discovered nodes in a group is to have better control over them such as when the IP address of the nodes primary interface changes and one has to delete and re-discover the node.

A feature to solve this would be most welcome, if even as a command line util that needs to be run from a terminal.

Environment

Not relevant.

Acceptance / Success Criteria

None

Linked issues

is duplicated by

NMS-4938

import node(s) into provisioning group through web UI

NMS-5150

Utility to convert capsd discovered devices to provisiond

Lucidchart Diagrams

Activity

Show:

Seth Leger September 1, 2015 at 12:00 PM

This was resolved in 1.12 by allowing discovery packages to contain a 'foreign-source' attribute that indicates the foreign source to which the discovered node should be added. Marking as fixed.

commit e468cc8435bcd023e04e1fb534386c4445baed5f

Richard S.W. Palusaar March 25, 2014 at 8:15 AM

What is the current progress on this issue?
I have read the duplicates where it is marked as resolved but I see no comments as to how it got resolved.

Some new feedback would be good.