If a network does not belong to any tenant (such as the HA router network),
instead of relying on the tenant_id in the plugin context, use a special tenant
id called 'INTERNAL-TENANT-ID' as the tenant_id in the pluin context can be
different during creation and deletion depending on the tenant performing the
operation.
Reviewed: https:/ /review. openstack. org/229576 /git.openstack. org/cgit/ openstack/ networking- arista/ commit/ ?id=3ac3b2e354f a2d3d615f7a46b1 71feaf273c181b
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3ac3b2e354fa2d3 d615f7a46b171fe af273c181b
Author: Shashank Hegde <email address hidden>
Date: Wed Sep 30 11:25:44 2015 -0700
Using 'INTERNAL- TENANT- ID' as the network owner
If a network does not belong to any tenant (such as the HA router network), TENANT- ID' as the tenant_id in the pluin context can be
instead of relying on the tenant_id in the plugin context, use a special tenant
id called 'INTERNAL-
different during creation and deletion depending on the tenant performing the
operation.
Closes-Bug: 1494302 5f9549a0c2b6769 7ad311fa4c8
Change-Id: I139c8a4754fcf7