Re: [openstack-dev] [Nova] The security group is confused in the create server api

2015-05-14 Thread Feodor Tersin
On Wed, May 13, 2015 at 4:54 PM, Lei Zhang zhang.lei@gmail.com wrote: Thank for your reply. I read that thread, but it just throw a exception when using confused params. To solve this issue, is it worth to create a now micro version of api to implement above cli? As i see at the last

Re: [openstack-dev] [Nova] The security group is confused in the create server api

2015-05-13 Thread Lei Zhang
Thank for your reply. I read that thread, but it just throw a exception when using confused params. To solve this issue, is it worth to create a now micro version of api to implement above cli? On Wed, May 13, 2015 at 3:35 PM, Feodor Tersin fter...@cloudscaling.com wrote: nova boot test

[openstack-dev] [Nova] The security group is confused in the create server api

2015-05-13 Thread Lei Zhang
In the legency network, there only one nic. So it is OK and understandable by using following cli. nova boot test --flavor m1.tiny --security_group ssh --security_group http --image cirros The instance only have one network associate with several security groups. But in Neutron Network, we

Re: [openstack-dev] [Nova] The security group is confused in the create server api

2015-05-13 Thread Feodor Tersin
nova boot test --flavor m1.tiny --security_group ssh --security_group http --nic net-id=xxx --nic port-id=yyy Which port/nic the security group should bind to? the first one? both? Both groups will be set to a new port of xxx network. A set of port yyy SG will not be