[patching] Support for patching of clusters with deployment info that changed with cli

[Dima Shulyak]

If user provides its own info with fuel client - it will be stored in database and used as replacement for generated one.
So it will be impossible to seamlessly patch cluster with replaced_deployment_info stored in database.
We need to overwright:
- path to manifests/module
- yum and apt-get settings

[OpenStack Infra (hudson-openstack)]

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

[Dima Shulyak (dshulyak)]

If user provides its own

puppet_manifests_source:
puppet_modules_source:
repo_metadata

it will take no effect, and one generated by release will be taken.
This was done to support patching of environments deployed by fuel client.

To overcome this issue you will need to overwrite Release.orchestrator_data in database

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/113297
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=330e8eeccac23d28c59b547f0427388bba96b3ae
Submitter: Jenkins
Branch: master

commit 330e8eeccac23d28c59b547f0427388bba96b3ae
Author: Dima Shulyak <email address hidden>
Date: Mon Aug 11 18:55:20 2014 +0300

    Always replace orchestrator_data for deployment

    - replace orchestrator_data for customized clusters

    Change-Id: I590aae2937902e5c0bdc946493225d584470e3cb
    Closes-Bug: 1354322