Tacker: Need generic SSH / Telnet management driver that can be configured via TOSCA template
Bug #1474965 reported by
Bob Haddleton
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tacker |
Confirmed
|
Low
|
Bob Haddleton | ||
Bug Description
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-
| Changed in tacker: | |
| assignee: | nobody → Bob Haddleton (bob-haddleton) |
| status: | New → Confirmed |
| status: | Confirmed → In Progress |
| tags: | added: tacker-server |
| Changed in tacker: | |
| importance: | Undecided → Medium |
Revision history for this message
| Bob Haddleton (bob-haddleton) wrote | #1 |
| Changed in tacker: | |
| importance: | Medium → Wishlist |
| status: | In Progress → Confirmed |
Revision history for this message
| Sridhar Ramaswamy (srics-r) wrote | #2 |
| summary: |
- Tacker: Need to have a generic management driver that can be configured - via TOSCA template + Tacker: Need to have a generic SSH / Telnet management driver that can + be configured via TOSCA template |
| tags: | added: mitaka-rfe rfe |
| summary: |
- Tacker: Need to have a generic SSH / Telnet management driver that can - be configured via TOSCA template + Tacker: Need generic SSH / Telnet management driver that can be + configured via TOSCA template |
| description: | updated |
| Changed in tacker: | |
| importance: | Wishlist → Low |
Revision history for this message
| Sridhar Ramaswamy (srics-r) wrote | #3 |
| tags: | removed: mitaka-rfe tacker-server |
Revision history for this message
| Sridhar Ramaswamy (srics-r) wrote | #4 |
Revision history for this message
| Ashish (ashish235) wrote | #5 |
Revision history for this message
| Aqsa Malik (aqsamm) wrote | #6 |
To post a comment you must log in.
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.