Setting up private network causes tempest to fail

[Peter Stachowski]

Apparently the tempest tests (as run by python-troveclient) check that the private network isn't shared. We should switch the trove network to set up and use an alt-private network instead of a shared one with the demo tenant.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/405671
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=d54cd03199f09b16f5b49d8713a5f66d3ebd9de3
Submitter: Jenkins
Branch: master

commit d54cd03199f09b16f5b49d8713a5f66d3ebd9de3
Author: Peter Stachowski <email address hidden>
Date: Thu Dec 1 22:53:04 2016 +0000

    (fix troveclient gate) Use alt-demo network

    This change uses the alt-demo network instead of sharing
    the private network from the demo tenant. This should
    fix the tempest tests on python-troveclient complaining
    about this and also brings us one step closer to using
    neutron entirely.

    Tested with the demo tenant as well and it still
    puts on a network without using the --nic parameter, the
    only drawback is that the ip doesn't appear on the trove
    show command.

    The scenario and api tests were modified to always pass
    in the nic parameter (as it probably should have been done
    from the beginning anyways).

    Change-Id: I9f3cbae3490e9995ba5f835fc2304442b83464e4
    Closes-Bug: 1647001

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/trove 7.0.0.0b2 development milestone.