Patching feature is obsolete and should be removed from nailgun

[Oleg S. Gelbukh]

Patching feature was initially intended to apply patches cluster-wide using deployment mechanisms of Fuel. Since then, it was obsoleted by package-based approach to delivering and applying patches.

Patching graph and calls to it should be removed from the codebase. There is a plan to reuse 'pending_release_id' parameter for upgrading of cluster, so it should be left in the model.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/240310

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/240310
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=81fb99fc722907833768991bcb694368f53dc7f2
Submitter: Jenkins
Branch: master

commit 81fb99fc722907833768991bcb694368f53dc7f2
Author: Oleg Gelbukh <email address hidden>
Date: Wed Oct 28 21:01:59 2015 +0000

    Remove deployment graph config for patching

    Patching feature was obsoleted and is not supported anymore.

    Delete deployment graph configuration for patching. Delete condition that
    yields this configuration when cluster asked for deployment graph.

    Closes-bug: 1511499
    Change-Id: I7d73aba5b090a5d24729553fdab76bbbaea34ebd

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/280708

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/281338

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/281338
Committed: https://git.openstack.org/cgit/openstack/python-fuelclient/commit/?id=926a4bf487ba20599338c5d4702981cdeafa7ac6
Submitter: Jenkins
Branch: master

commit 926a4bf487ba20599338c5d4702981cdeafa7ac6
Author: Igor Kalnitsky <email address hidden>
Date: Wed Feb 17 14:30:43 2016 +0200

    Remove legacy patching code

    In Fuel 5.1 we had an experimental feature - 'patching openstack env'.
    The idea was to update and to rollback OpenStack environments between
    minor releases. However, we have encounter a lot of problems with
    restoring OpenStack databases andresolving dependency hell in packages,
    so we buried it and never release it.

    This patch removes legacy code from the source tree. We can do it
    without fear, since it wasn't released in public and, moreover,
    was broken since Fuel 6.0 (no chance someone use it).

    Change-Id: I38625a354ea1f09efa24f3e4d18cd4337b7dcc5b
    Related-Bug: #1511499

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/280708
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=e91363ba9c58f2b90810ea671a234ea41e231bbf
Submitter: Jenkins
Branch: master

commit e91363ba9c58f2b90810ea671a234ea41e231bbf
Author: Igor Kalnitsky <email address hidden>
Date: Fri Feb 5 18:53:07 2016 +0200

    Remove legacy patching code

    In Fuel 5.1 we had an experimental feature - 'patching openstack env'.
    The idea was to update and to rollback OpenStack environments between
    minor releases. However, we have encounter a lot of problems with
    restoring OpenStack databases andresolving dependency hell in packages,
    so we buried it and never release it.

    This patch removes legacy code from the source tree. We can do it
    without fear, since it wasn't released in public.

    Related-Bug: #1511499
    Change-Id: I58b3fedd239eb7fe4226e51c2d6386efab14395d