Transfer Network Ownership - Project

Registered by Andre Aranha

There is an API that updates Networks (PUT /v2.0/networks/{network_id}) and Subnets (PUT /v2.0/subnets/{subnet_id}), but some fields, like tenant_id, are read-only.
I would like to propose that Networks with it's associated subnets are able to be transfered to another project updating it's tenant_id field from the API mentioned above.
This is important to reuse an existing resource already configured and working instead of deleting and creating a new one.
As this feature updates two resources, I'm going to split in two Blueprints: One for Network and another one for Subnet, where the network will depend on the Subnet blueprint.
For this blueprint I gonna implement the Network feature.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Andre Aranha
Direction:
Needs approval
Assignee:
Andre Aranha
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Armando Migliaccio

Related branches

Sprints

Whiteboard

This is a bad idea.

Gerrit topic: https://review.openstack.org/#q,topic:bp/transfer-network-ownership,n,z

Addressed by: https://review.openstack.org/93725
    Transfer Network Ownership

Addressed by: https://review.openstack.org/93802
    Transfer Network Ownership

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.