Remove platform-specific knowledge from component base classes

Bug #956265 reported by Doug Hellmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
anvil
Fix Released
Undecided
Doug Hellmann

Bug Description

After #91 lands we need to look at all of the other component classes for install, uninstall, etc. and make sure they do not have platform-specific knowledge. If they do, new classes need to be created for that logic and the YAML file should be updated to refer to the new class.

Changed in devstackpy:
assignee: nobody → Doug Hellmann (doug-hellmann)
status: New → In Progress
Revision history for this message
Doug Hellmann (doug-hellmann) wrote :
Revision history for this message
Doug Hellmann (doug-hellmann) wrote :
Revision history for this message
Doug Hellmann (doug-hellmann) wrote :

Still need to update keystone, melange, nova, novnc, quantum, and swift.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote :

On second thought, all of those are OS components and the commands in the python code are the same for all platforms, so I'm going to leave them as they are.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote :
Changed in devstackpy:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.