You have to specify the networks on which to boot the VM. If external
network should used or not is very difficult. In H release, I think if
multiple networks are available, the nova boot will fail.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1220505
Title:
IP will be allocated automate even it is a floating IP
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
I'm working under Centos 6.4 + Grizzly.
I have created two networks, one for instances private network, and
another one for public network (for floating IP ).
Everything works fine. But , if I create an instance without point out the
private network id, such as:
nova boot --flavor m1.tiny --image
c4302a6f-196d-4d3e-be64-c9413e8d1f71 test1
The instance will be start with both network:
| d99fd089-5afe-4397-b51b-767485b43383 | test1 | ACTIVE |
public=192.168.14.29; private=10.1.0.243 |
The network works fine, but, I don't want the instance has the public
IP.
And, I think because I already assigned this public network to a router, so
it is clear that it is not an auto assign IP.
Also, if it can be auto assigned to an instance, it should be a floating IP
,but not like what it is now.
Any ideas?
Thanks.
-chen
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1220505/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
