Instance metadata should include project_id

[Andrew Bogott]

As per

https://www.mail-archive.com/search?<email address hidden>&q=subject:%22Re\%3A+\[Openstack\]+How+should+an+instance+learn+what+tenant+it+is+in\%3F%22&o=newest

It's weirdly hard for an instance to learn what project it's in. Let's just add project_id to instance metadata.

[Markus Zoeller (markus_z) (mzoeller)]

Solving an inconsistency: The bug is 'In Progress' but without an assignee. I set the status back to the last known status before the change to 'In Progress'.

Feel free to assign the bug to yourself. If you do so, please set it to 'In Progress'.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/197185
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9260ea1493fa4dfdb648f9376782a82f52664e5b
Submitter: Jenkins
Branch: master

commit 9260ea1493fa4dfdb648f9376782a82f52664e5b
Author: andrewbogott <email address hidden>
Date: Tue Jun 30 01:07:55 2015 -0500

    Include project_id in instance metadata.

    Instances sometimes need to know what project they're
    in in order to manage permissions or naming. This
    change allows an instance to grab its project id without
    needing keystone auth or other work-arounds.

    Implements blueprint project-id-in-metadata
    DocImpact: Update release notes and the metadata-service doc page.
    Closes-Bug: #1470179
    Change-Id: Idf2ea1473a545a51e1a4e50579da585d8f674f74