So far I have found out that, when I am giving "nova secgroup-list" command, novaclient is sending "curl -i http://127.0.0.1:9696/v2.0/security-groups/8ae7b26b-8a28-4389-ad3b-0884e1aa5015.json" rest api to neutron that fetches tenant specific security group list.
On the other hand, when I am giving "nova boot" command from admin, with --security-groups flag set to certain security-group name which is already present in any other tenant, novaclient is sending "curl -i http://127.0.0.1:9696/v2.0/security-groups.json?fields=id&name=web -X GET -H "X-Auth-Token:" rest api to neutron that fetches all security groups irrespective of tenant.
I am moving forward in the direction of resolving below rest api to be generated as tenant-specific like one generated in case of giving "nova secgroup-list" command.
So far I have found out that, when I am giving "nova secgroup-list" command, novaclient is sending "curl -i http:// 127.0.0. 1:9696/ v2.0/security- groups/ 8ae7b26b- 8a28-4389- ad3b-0884e1aa50 15.json" rest api to neutron that fetches tenant specific security group list. 127.0.0. 1:9696/ v2.0/security- groups. json?fields= id&name= web -X GET -H "X-Auth-Token:" rest api to neutron that fetches all security groups irrespective of tenant.
On the other hand, when I am giving "nova boot" command from admin, with --security-groups flag set to certain security-group name which is already present in any other tenant, novaclient is sending "curl -i http://
I am moving forward in the direction of resolving below rest api to be generated as tenant-specific like one generated in case of giving "nova secgroup-list" command.