In Arista ML2 delete tenant if no resources associated with it
Bug #1429968 reported by
Sukhdev Kapur
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Sukhdev Kapur |
Bug Description
When all resources for a tenant are deleted (ports and networks), the tenant is removed Arista's DB. This operation is performed during port/network_
With enhancements to the Sync mechanism to accommodate large scale deployments, it is prudent to move the deleting of tenant from port/network_
This bug is to make this fix.
Changed in neutron: | |
assignee: | nobody → Sukhdev Kapur (sukhdev-8) |
status: | New → In Progress |
Changed in neutron: | |
milestone: | none → kilo-3 |
importance: | Undecided → Medium |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/162778 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=1ec7c542116 f4980ee6680adf2 61d9a29c5a1d61
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1ec7c542116f498 0ee6680adf261d9 a29c5a1d61
Author: Sukhdev <email address hidden>
Date: Mon Mar 9 14:45:21 2015 -0700
In Arista ML2 delete tenant without any resources
If there are no resources associated with a xxx_precommit( ) methods. The sync
tenant, it was deleted from Arista DB in
delete_
mechanism used to make sure that back-end is in
sync with DB.
Lately, the sync mechanism has been enhanced to xxx_postcommit( ) methods instead of xxx_precommit( ) methods. Additionally,
support scaled deployment. Therefore, the
delete_tenat() call now needs to be invoked from
delete_
delete_
when the tenant is removed from the DB, it is
removed from the back-end as well. This removes
the dependancy on the sync mechanism to take
care of this.
[Note: Sync will still do it, but, this way it
gets done right away]
Closes-bug: 1429968 e2648685ca97d0b e06db2d1a55
Change-Id: I2f6ddb01079fe4