Refactor NetApp drivers
This proposal includes separating the ONTAP ZAPI client code from the existing driver code, improving testability, improving readability, general cleanup (renaming functions and variables), and adding unit test coverage. In the end, the main concern is improved maintainability.
The code responsible for interacting with the ZAPI should not be intertwined with the driver code. Code responsible for serializing requests and communicating with ZAPI should live in it's own module.
Blueprint information
- Status:
- Complete
- Approver:
- John Griffith
- Priority:
- Undefined
- Drafter:
- Alex Meade
- Direction:
- Needs approval
- Assignee:
- Alex Meade
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
- John Griffith
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
NetApp iSCSI: move zapi client logic into modules
<jdg>
It would be great if we didn't do this every other release, should this be given more time (ie Juno-2) to make sure it's done well enough this time that we don't need to do it again?
<jdg>
Given it's the 10'th of June and no response regarding milestone, I'll go ahead and move this to Juno-2
<jdg>
Juno-2 is closing and still nothing... abandoned the WIP that was up and removed targeting from this.
Addressed by: https:/
NetApp NFS and iSCSI: move zapi client logic into modules
Gerrit topic: https:/
