Hi All,
The below are the approaches to fix this bug for the nova-compute scenario.
• To invoke Nova-API from Keystone when the tenant-delete request is issued. For now, atleast the message that instances are active is enough.
• To access the Nova database from Keystone e.g. “instances” table.
• To enable notifications on both Keystone and Nova with a new queue created in Rabbitmq.
Please do let me know the inputs so that I can consolidate the approach to proceed further.
Thanks in advance,
Hi All,
The below are the approaches to fix this bug for the nova-compute scenario.
• To invoke Nova-API from Keystone when the tenant-delete request is issued. For now, atleast the message that instances are active is enough.
• To access the Nova database from Keystone e.g. “instances” table.
• To enable notifications on both Keystone and Nova with a new queue created in Rabbitmq.
Please do let me know the inputs so that I can consolidate the approach to proceed further.
Thanks in advance,