On Wed, May 13, 2015 at 4:54 PM, Lei Zhang 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 (May, 13) Matt'
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
wrote:
>
>> nova boot test --flavor m1.tiny --sec
>
>
> 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 no
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 c
