provider/openstack allow floating ip to target a specific tenant

[cristicalin]

Gophercloud library supports specifying a tenant_id in the Create function.

This patch extends the floatingip schema to allow a cloud admin to specify a tenant_id.
Major use cases:

• Q&A for neutron
• managed service where the tenants are not allowed to allocate floating IP addresses themselves due to scarcity or resources or organisational security constraints

The patch also adds relevant documentation information.

[cristicalin]

The CI failure appears unrelated to this patch, is there a way to trigger the CI job again ?

[jtopjian]

@cristicalin Sorry for the delay on this.

Doing a forceful push will retrigger the Travis checks:

git push -f -u cristicalin neutron_floatingip_tenant_id

If git doesn't want to accept a blank push, something like git commit --amend should make it go.

[cristicalin]

Sorry for the late reaction to this.
I pushed again and now its validated cleanly.
I think this in a good state to merge, I did test it out and it's working as expected on a Juno version of openstack.

[jtopjian]

LGTM! would it be possible to squash the commits into one? It's good to merge after that. 😄

[cristicalin]

squashed and now it should be good to go

[jtopjian]

👍

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.