Cinder monkey patching review

Registered by Edward Hope-Morley

Several cinder services do eventlet.monkey_patch() i.e. monkey patch everything that has an eventlet alternative. We should really consider a more conservative approach to doing this for the following reasons:

1. monkey patching everything increases the likelihood of unexpected results since you are using eventlet alternatives to modules which may not behave the same.
2. monkey patching everything is normally restricted to testing
3. other openstack services e.g. Glance use a whitelist approach so they know exactly what modules are being monkey patched thus making it easier to target tessts.
4. patching everyting makes it harder if you want to use a non-patched/original module

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Sean McGinnis

Related branches

Sprints

Whiteboard

(smcginnis): Marking obsolete as this has been sitting out there for a long time. If this is still needed, please submit a new bp.

None

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.