the schemes of heat_metadata_server_url, heat_waitcondition_server_url and heat_watch_server_url use the hardcoded http

[Jun Xie]

the schemes of heat_metadata_server_url, heat_waitcondition_server_url and heat_watch_server_url use the hardcoded http,
they should be flexiable to use what is coming instead of always being http.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/130687
Committed: https://git.openstack.org/cgit/stackforge/cookbook-openstack-orchestration/commit/?id=c7f0bb2e0e2ce3a508e2fabb4adb37dd26664a47
Submitter: Jenkins
Branch: master

commit c7f0bb2e0e2ce3a508e2fabb4adb37dd26664a47
Author: jun xie <email address hidden>
Date: Fri Oct 24 13:08:50 2014 +0800

    Modify the hardcoded scheme

    This commit modifies the schemes of heat_metadata_server_url,
    heat_waitcondition_server_url and heat_watch_server_url
    so that they do not always use the hardcoded http.

    Change-Id: I8dcc8ec53b25dd4f2c53f662c0af821ee653a014
    Closes-Bug: #1385046

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cookbook-openstack-orchestration ocata-eol release.