<div dir="ltr"><div><div><div><div><div><div>I've put my name against networking-calico, but I believe it's a no-op for me at this stage of the tenant->project transition. The occurrences of 'tenant' in networking-calico's code are:<br><br>./networking_calico/plugins/calico/plugin.py:45: LOG.info("Forcing ML2 tenant_network_types to 'local'")<br>./networking_calico/plugins/calico/plugin.py:46: cfg.CONF.set_override('tenant_network_types', ['local'], group='ml2')<br>./networking_calico/agent/dhcp_agent.py:213: 'tenant_id': ? }<br>./networking_calico/agent/dhcp_agent.py:298: "tenant_id": "calico",<br><br></div>So it's just:<br></div>- the ML2 'tenant_network_types' config setting name<br></div>- the 'tenant_id' key used in neutron.agent.linux.dhcp.NetModel.<br><br></div>I guess those will be transitioned in due course. Am I right in thinking that there's no action for networking-calico right now, or do you think I've missed something?<br><br></div>Thanks,<br></div> Neil<br><br></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jul 14, 2016 at 9:32 PM Henry Gessau <<a href="mailto:HenryG@gessau.net">HenryG@gessau.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Henry Gessau <<a href="mailto:HenryG@gessau.net" target="_blank">HenryG@gessau.net</a>> wrote:<br>
> In accordance with the Blueprint [1] and the spec [2], we are in the process<br>
> of deprecating the use of the term 'tenant' in favor of 'project'.<br>
><br>
> The code change [3] with the biggest impact on Neutron developers is currently<br>
> out for review and will merge quite soon (shortly after N-2). This change<br>
> renames all 'tenant_id' columns in the database to 'project_id'.<br>
><br>
> If you have any changes in flight that touch a tenant_id field, you will be<br>
> affected. Please familiarize yourself with [3], rebase on it, and comply with<br>
> the changes.<br>
><br>
> One patch known to be affected is [4].<br>
><br>
> The column rename change has been designed to have minimal impact on the usage<br>
> of 'tenant_id' fields. For now 'tenant_id' is still available as a<br>
> key/property in resource dicts and objects, and as an attribute in request<br>
> contexts.<br>
><br>
> In the long run (Ocata or beyond) we want to end up with no usages of the term<br>
> 'tenant', except in the API for backwards compatibility. Existing usages of<br>
> 'tenant' in the codebase will be converted to 'project' on a case-by-case<br>
> basis. Although the conversion has not yet commenced, any *new* fields,<br>
> arguments, variables, etc. with 'tenant' in the name will no longer be accepted.<br>
><br>
> [1] <a href="https://blueprints.launchpad.net/neutron/+spec/keystone-v3" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/neutron/+spec/keystone-v3</a><br>
> [2]<br>
> <a href="http://specs.openstack.org/openstack/neutron-specs/specs/newton/moving-to-keystone-v3.html" rel="noreferrer" target="_blank">http://specs.openstack.org/openstack/neutron-specs/specs/newton/moving-to-keystone-v3.html</a><br>
> [3] <a href="https://review.openstack.org/335786" rel="noreferrer" target="_blank">https://review.openstack.org/335786</a><br>
> [4] <a href="https://review.openstack.org/244680" rel="noreferrer" target="_blank">https://review.openstack.org/244680</a><br>
<br>
This work also affects repos that integrate with neutron and have tables in<br>
the Neutron database. We have started to submit patches for the neutron-fwaas,<br>
-lbaas, and -vpnaas repos, and we are keeping track of the progress with an<br>
etherpad [5].<br>
<br>
I have listed all the Neutron Stadium projects there, as well as all the<br>
projects that I could find hosted on <a href="http://git.openstack.org" rel="noreferrer" target="_blank">git.openstack.org</a> that integrate with the<br>
Neutron DB. Please help by signing up for a project.<br>
<br>
If you encounter any problem or issues, please ask us for help. Either reply<br>
to this email thread, or find me (HenryG) or Darek (dasm) in the Neutron IRC<br>
channel.<br>
<br>
[5] <a href="https://etherpad.openstack.org/p/neutron-stadium-tenant2project" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/neutron-stadium-tenant2project</a><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>