OpenStack Compute (nova)

  1. Bug #1203413
  2. Comment #7

Comment 7 for bug 1203413

Revision history for this message
Akihiro Motoki (amotoki) wrote : Re: Horizon passes neutron security group name instead of uuid

I think this issue should be fixed in nova ideally, but there seems to be several work around in Horizon.

Basically I think ID is better since it is unique in the system, so it looks good to me to change sg.name to sg.id as the proposed patch does. In addition to this, the possible workaround in Horizon are:

(1) Before/Inside calling server_create called from handle() in create_instance workflow class, if security_group ID is an integer (nova-network is used), to retrieve name according to its ID and pass security group name as a parameter of server_create()

(2) Similar to (1), to encode sg.id and sg.name with json in populate_groups_choices in project/instances/workflows/create_instance.py, and use sg.name when sg.id is an integer not UUID. This saves additional security_group_list API call.

(3) Use security_group name as security group ID if ID is an integer in api/nova. It can be done in api/nova SecurityGroup class.

All of the above options look workarounds to me, but it can help us.

I would like to know your opinions.