New instance's IP can change if rescheduled

[Jason Kölker]

When an instance is created, network_info is allocated prior to spawning, and starts showing in the os-api's server dict as 'addresses'. Any failure in virt to spawn the instance will cause the network to be deallocated, and the instance rescheduled on another host, which will re-allocate the network, potentially getting a new ip address. Which would then be shown in api calls. We should allow the operator to hide the network_info until such a time the spawn is successful.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/18414
Committed: http://github.com/openstack/nova/commit/b3bbd09131e127e7540f4ccdb1376c10bace8b7a
Submitter: Jenkins
Branch: master

commit b3bbd09131e127e7540f4ccdb1376c10bace8b7a
Author: Jason Kölker <email address hidden>
Date: Tue Dec 11 15:12:29 2012 -0600

    Add extension to allow hiding of addresses

    * Servers in certain states will have network_info but it may change,
      (eg. rescheduled build on another host). The extension allows the
      operator to hide the address information in those states
    * Fixes bug LP 1089092

    Change-Id: Ie843e34a41c77903b201b45c5b67a6f75334cb5e