Tacker: Need generic SSH / Telnet management driver that can be configured via TOSCA template

[Bob Haddleton]

The current Tacker design requires that a VNF supply a Management Driver to support configuration and management of the VNF.

It would be useful to have a generic Management Driver that could be configured via the TOSCA template, to eliminate the need for code additions to Tacker every time a new VNF is added.

Request for Enhancement:

VNFD Template:

vdus:
  vdu1:
    id: vdu1
    vm_image: VNF-XR
    instance_type: m1.medium
    mgmt_driver: ssh

Sample VNF create command,

tacker vnf-create --name test-vnf-1 --vnfd-name test-vnfd --config-file test-vnf-1-config.yaml

[Bob Haddleton (bob-haddleton)]

It would be helpful to modify the existing "mgmt_policy" to work like the new "monitor_policy" and accept a driver name followed by a list of "mgmt_parameters" that would be passed to the mgmt driver. That would enable a single generic mgmt_driver that could potentially handle a variety of protocols (ssh, telnet, REST, Netconf) along with additional parameters like login ID, key name, etc. It would also be helpful to specify mgmt_parameters in vnf-create so that, for example, different keys could be used for the same VNFD template.

This may end up being more than a bug or an RFE, and existing operation would need to be maintained or at least accounted-for.

[Sridhar Ramaswamy (srics-r)]

There is renewed interest in this feature. Transitioning this into mitaka-rfe and make it specific to SSH (perhaps we can incorporate telnet in the same generic mgmt driver). I'll clone a separate one for NETCONF / YANG.

[Sridhar Ramaswamy (srics-r)]

Removing from mitaka-rfe

[Sridhar Ramaswamy (srics-r)]

Bob - are you planning to work on this ? If not, can you please un-assign so that someone else from the community could pick this up.

[Ashish (ashish235)]

Guys, is this planned?

[Aqsa Malik (aqsamm)]

Sridhar - Just a thought. Can this be taken as a blueprint instead of a bug fix?