boot-stack network configuration traps all metadata traffic

[Robert Collins]

but metadata traffic from the same host probably wants to be permitted to leave when boot-stack was deployed using nova.

[Robert Collins (lifeless)]

It's possible this also causes metadata supplied ssh keys to be discarded on reboots, which can be unnerving for folk.

[Robert Collins (lifeless)]

I fixed this in
commit d9a4ea36e10750f09c4bdd667f060d10aaa7c69b
Author: Robert Collins <email address hidden>
Date: Mon Jul 1 16:25:45 2013 +1200

    Overhaul quantum networking for non-seed clouds.

    The networking setup was inappropriate for non-seed clouds - it
    depended on two network interfaces, forced NAT that we don't need and
    could not be turned off. Additionally there wasn't much clarity
    between idempotent machine config and non-idempotent service config.

    Key changes in this patch:
    * No longer write persistent device files, instead update
      idempotently.
    * NAT rules are now setup idempotently on each o-r-c run.
    * New definitions for the meaning of various config keys to suit
      working with different cloud layers.

    Change-Id: Ie86be0fc884b4c4f655d73da345bdee45fcde473