TrustedFilter checks compute trust level, not hypervisors

[Bob Ball]

The TrustedFilter uses host_state.host as the name that will be checked against the remote attestation service.

This works for the KVM case because the compute node and the hypervisor are the same; however we must be checking host_state.nodename which is the hostname for the hypervisor which will be registered with the attestation server.

[Bob Ball (bob-ball)]

The same issue applies to pre-populating the cache which uses compute['service']['host'] which is the compute's host name not the hypervisor's host name

[Openstack Gerrit (openstack-gerrit)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/89427
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3c88fce604959a68f48d71274e0d93b74da17e34
Submitter: Jenkins
Branch: master

commit 3c88fce604959a68f48d71274e0d93b74da17e34
Author: Yunhong Jiang <email address hidden>
Date: Mon Apr 21 09:15:56 2014 -0700

    Use hypervisor hostname for compute trust level

    In XenAPI, service hostname and compute node hostname is different
    because the Nova compute service may run in a separated VM and is
    different with the hostname of the compute node.

    The remote attestation service use the compute node's hostname because
    it's the compute node that will run the servers.

    Closes-Bug: #1223452

    Change-Id: I9a7ce74d595531196804615a8947e253b0bd3f1a

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/icehouse
Review: https://review.openstack.org/176871

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/176871
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4812617002ee6a5044096e253413d6718003bca3
Submitter: Jenkins
Branch: stable/icehouse

commit 4812617002ee6a5044096e253413d6718003bca3
Author: Yunhong Jiang <email address hidden>
Date: Mon Apr 21 09:15:56 2014 -0700

    Use hypervisor hostname for compute trust level

    In XenAPI, service hostname and compute node hostname is different
    because the Nova compute service may run in a separated VM and is
    different with the hostname of the compute node.

    The remote attestation service use the compute node's hostname because
    it's the compute node that will run the servers.

    (cherry picked from commit 3c88fce604959a68f48d71274e0d93b74da17e34)

    Conflicts:
     nova/scheduler/filters/trusted_filter.py
     nova/tests/scheduler/test_host_filters.py

    Closes-Bug: #1223452
    Change-Id: I9a7ce74d595531196804615a8947e253b0bd3f1a