Limit on instance metadata should reflect provider limits

[Jason Dunsmore]

The Server resource arbitrarily limits instance metadata to five entries, when the actual provider's maxServerMeta limit could be much higher. The Server resource should check the maxServerMeta limit and enforce that limit.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/61864
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=c77230782924126755b7fa90fe12a544046b7c73
Submitter: Jenkins
Branch: master

commit c77230782924126755b7fa90fe12a544046b7c73
Author: Jason Dunsmore <email address hidden>
Date: Thu Dec 12 13:05:18 2013 -0600

    Validate number of instance metadata entries

    The Server resource arbitrarily limits instance metadata to five
    entries, when the actual provider's maxServerMeta limit could be much
    higher. Make the Server resource check the provider's maxServerMeta
    absolute limit and enforce that limit in validate().

    Change-Id: Ic00fc6f3a41ae783e43bd7f2df8663263d9cbf90
    Closes-Bug: #1260427