/var/lib/cloud belongs to cloud-init, heat should not write files there

[Clint Byrum]

 By writing files directly into /var/lib/cloud/data, heat risks colliding with cloud-init.

Heat should write files to /var/lib/heat instead , which it can claim as its own.

[Steven Hardy (shardy)]

If we aim to use a fork of the aws cfnbootstrap tools (ref Zane's mail to the list), then we probably want to align with their default paths and filenames

e.g /var/lib/cloud/data/cfn-init-data needs to become /var/lib/cfn-init/data/metadata.json

A similar problem exists for our cfn-hup, but that's an issue to be raised for heat-jeos

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/23052
Committed: http://github.com/openstack/heat/commit/737cc26570e194f691de71a7372f33a75a32e8c2
Submitter: Jenkins
Branch: master

commit 737cc26570e194f691de71a7372f33a75a32e8c2
Author: Steven Dake <email address hidden>
Date: Tue Feb 26 17:38:30 2013 -0700

    Put heat data files in /var/lib/heat-cfntools

    The /var/lib/heat-cfntools directory should be owned by the
    heat-cfntools package for whichever distro it is included.

    This avoids the problem of heat writing to directories owned
    by cloud-init.

    For the moment, the part handler will continue to write to
    /var/lib/cloud/data to be removed at a later date.

    Change-Id: I70b714c70ed146d4f6807850d6e7264c6a4624cd
    Fixes: Bug #1105806

[Steve Baker (steve-stevebaker)]

heat-cfntools side implemented by https://github.com/heat-api/heat-cfntools/commit/4dc88ac6abad1876381d30609c88d17daff1cccf