Deploy patches (minor fixes) for OpenStack

Design Document https://docs.google.com/a/mirantis.com/document/d/1EHDRXR1uKHh6ibpbUTbrRFnA-6JLj0nf7ULXcIv7mDI/edit

Presentation:
https://docs.google.com/a/mirantis.com/presentation/d/1pRWtAmTZSSBInh-314hm_Zijq06ugDZF8MwtMYose_I/edit#slide=id.p

Defense speech:
https://docs.google.com/a/mirantis.com/document/d/1liL4z4FeFjkL2i54bQOlEzDjCQIXPoscVy4is7r47Us/edit

Patches to OpenStack components should be deployable through a single action by an administrator after downloading the patch(es).

For Fuel, once the patch(es) have downloaded, the install should be launched from within Fuel itself. Information about the environment should be available without further user input, so few to no questions should be required for install.

The following requirements apply:
Downtime should be limited to restarting the service/executable with the new patched version.
An administrator must be able to identify that the products have been patched based on a new version (string). This version string should be visible through Fuel’s UI.
An ability to rollback the patch if a catastrophic event is caused by the patch is desirable.

Feature Lead: Dmitry Ilyin (Library Part)
Mandatory Design Reviewers: Dmitry Ilyin
Developers: Igor Kalnitskiy, Dmitry Ilyin, Ekaterina Pimenova
QA: Tatyana Leontovich